4G LTE WiFi Router (RUT200/RUT241)

The router is manufactured by a 3rd party (Teltonika Networks) and is broadly compatible with SIM cards from most data plan providers. However, we recommend that you test the router with your specific SIM and provider well in advance of a field deployment - and that you verify that the frequency bands of your provider match the router variant (see the tech specs).

We are happy to support questions related to using the router with the CANsub or CANedge2 - incl. via our step-by-step guides. For advanced router questions (e.g. RutOS features, carrier-specific settings), we may refer to the Teltonika wiki and support.

The RUT200 is available for Europe, Asia-Pacific and other regions - but not for North America. For USA and Canada, we therefore offer the RUT241 via the dropdown. The RUT241 is the same class of device: Same size, housing, power input, WiFi, Ethernet ports and RutOS features. The North America variant supports the relevant LTE bands (B2, B4, B5, B12, B13, B14, B66, B71) and is FCC/PTCRB certified for use with Verizon, AT&T and T-Mobile.

All information on this page applies equally to the RUT241 unless otherwise stated.

WiFi access: Connect the CANsub's Ethernet port to a LAN port of the router and power the CANsub via USB (or via the PoE adapter). Join the router's WiFi from your laptop, tablet or phone - then enter the device URL shown on the CANsub LCD in your browser to open webCAN. No SIM card is required for this setup.

Remote LTE access: Insert a SIM card and follow the CANsub Intro step-by-step guide. Here, plug & play scripts deploy a WireGuard VPN server on Amazon Lightsail (~5 USD/month) and configure the router as a VPN client - typically in ~30 min. Your PC connects to the same VPN, after which you can access the CANsub via webCAN or the REST/WebSocket API from anywhere. The setup scales to fleets of routers and multiple users. If you already have a VPN server (e.g. an office VPN), you can use that instead.

To connect 2 x CANsub via Ethernet, simply configure the router's WAN port as a LAN port in the RutOS WebUI.

Insert a SIM card in the router and add the router's WiFi SSID/password to the CANedge2 configuration - as with any WiFi access point (see the CANedge2 Intro). With the S3 interface enabled, the CANedge2 will upload log files to your own S3 server via the LTE connection - with TLS encryption enabled.

Alternatively, enable the web server interface to access the CANedge2 SD card from any PC on the router's network - or remotely via the router's VPN. The web server interface does not support TLS, so remote access via the internet must go through a VPN.

No. The router ships with the stock Teltonika RutOS firmware and is configured via its WebUI (login details are printed on the device label). For WiFi access to a CANsub, no configuration is needed beyond joining the router's WiFi. For remote access via LTE, the CANsub Intro provides plug & play scripts that deploy a VPN server and configure the router as a VPN client. For the CANedge2, simply add the router's WiFi SSID/password to the device configuration.

The RUT200 does not support North American frequency bands. Instead, select the RUT241 (North America) variant via the dropdown. It is functionally equivalent (same housing, power, WiFi, Ethernet and RutOS) and is certified for Verizon, AT&T and T-Mobile. For other regions, check the tech specs to verify that the bands of your data plan provider are covered - or contact us.

The router takes a standard mini SIM (2FF) - i.e. the largest of the common SIM formats (most SIMs come in a multi-size frame). Any data SIM from a mobile provider can be used, as the router is unlocked. We recommend that you test your SIM/provider in the router well before deploying in the field. If your SIM has a PIN code, either disable it or enter it in the RutOS WebUI so that the router can connect after a power cycle. APN settings are typically detected automatically, but can be set manually.

The router accepts 9-30 V DC, making it suitable for both 12 V and 24 V vehicles. The simplest option is the included automotive power supply, which plugs into the vehicle's 12/24 V receptacle (cigarette lighter). For permanent installations, the 4-pin connector can be wired directly to the vehicle supply - e.g. via an ignition-switched circuit so the router powers down with the vehicle. The CANsub itself is powered via USB (e.g. from a USB car charger) or via the PoE adapter from a PoE switch - note that the router's own passive PoE is not compatible with the PoE adapter.

Yes. The router has 1 x LAN and 1 x WAN port. When using LTE (or WiFi) as the internet source, the WAN port is not needed and can be configured as a second LAN port in the RutOS WebUI - letting you connect 2 x CANsub via Ethernet. For more devices, add a small Ethernet switch (optionally with PoE to power the CANsubs).

The amount of data used during streaming via the CANsub will depend entirely on your CAN bus load, your CANsub hardware filters and other similar factors. It may be anywhere from a few MB per hour to 1+ GB per hour. The same principle applies to the CANedge2 when it uses the RUT as a WiFi access point for uploading data to S3. Here you can again configure device filters to minimize the data getting sent over the LTE connection. For detailed guidance based on your use case, contact us.

If your goal is to upload CAN data via LTE to your server, the CANedge3 is the simpler choice, as the LTE modem is built into the logger. The router is relevant if you need the CANedge2 web server interface (selective data pull via VPN), if you want to share one LTE connection across multiple devices - or if you combine the CANedge2 with a CANsub for real-time streaming.

The CANsub encrypts all communication via TLS out-of-the-box, and you can optionally enable mTLS so that only clients with a valid certificate can connect - see our secure CAN interface article. The CANedge2 S3 interface also uses TLS. The CANedge2 web server interface does not support TLS, so remote access to it should always go through the router's VPN (never via port forwarding). The router's firewall blocks incoming connections from the internet by default. We recommend VPN + mTLS for all remote deployments - and listen-only mode where possible.