TRB255
Overview
TRB255 can be used to integrate modern and legacy industrial equipment into one solution via RS232, RS485 & Ethernet interfaces. This industrial LTE Cat M1 & NB-IoT gateway is backward compatible to EGPRS (2G) networks. It can still be used with 2G network, however in case it gets shut down, there is a possibility to switch to LPWAN connectivity options. TRB255 has a wide range of industrial and networking features such as Modbus, SMS control, Firewall, OpenVPN and more. This product is compatible with the Teltonika Networks Remote Management System (RMS).
Features
|
Mobile
|
|
| Mobile module |
LTE (Cat M1) / NB-IoT / EGPRS |
| SIM switch |
2 SIM cards, auto-switch cases: weak signal, data limit, SMS limit, on roaming, no network, network denied, data connection fail |
| Status |
Signal strength (RSSI), SINR, RSRP, RSRQ, EC/IO, RSCP Bytes sent/received, connected band, IMSI, ICCID. |
| SMS/Call |
SMS status, SMS configuration, send/read SMS via HTTP POST/GET, EMAIL to SMS, SMS to EMAIL, SMS to HTTP, SMS to SMS, scheduled SMS, SMS autoreply, Call utilities |
| USSD |
Supports sending and reading Unstructured Supplementary Service Data messages |
| Black/White list |
Operator black/white list |
| Band management |
Used band status display, Band lock |
| APN |
Auto APN |
| Bridge | Direct connection (bridge) between mobile ISP and device on LAN |
| Multiple PDN |
Possibility to use different PDNs for multiple network access and services |
| Ethernet |
|
| LAN | 1 x LAN port 10/100 Mbps, comply IEEE 802.3, IEEE 802.3u standards, supports auto MDI/MDIX crossover (Configurable to work as WAN port) |
| Network |
|
| Routing | Static routing, Dynamic routing (BGP, OSPF v2, RIP v1/v2) (planned) |
| Network protocols |
TCP, UDP, IPv4, IPv6, ICMP, NTP, DNS, HTTP, HTTPS, FTP, SMTP, SSL v3, TLS, ARP, PPP, SSH, DHCP, Telnet, MQTT, Wake On Lan (WOL) |
| VoIP passthrough support (planned) |
H.323 and SIP-alg protocol NAT helpers, allowing proper routing of VoIP packets |
| Connection monitoring |
Ping Reboot, Periodic Reboot, LCP and ICMP for link inspection |
| Firewall |
Port forward, traffic rules, custom rules |
| DHCP |
Static and dynamic IP allocation, DHCP Relay |
| QoS / Smart Queue Management (SQM) (planned) |
Traffic priority queuing by source/destination, service, protocol or port, WMM, 802.11e |
| DDNS |
Supported >25 service providers, others can be configured manually |
| SSHFS |
Possibility to mount remote file system via SSH protocol |
|
Security
|
|
| Authentication |
Pre-shared key, digital certificates, X.509 certificates |
| Firewall |
Pre-configured firewall rules can be enabled via WebUI, unlimited firewall configuration via CLI; DMZ; NAT; NAT-T |
| Attack prevention |
DDOS prevention (SYN flood protection, SSH attack prevention, HTTP/HTTPS attack prevention), port scan prevention (SYN-FIN, SYN-RST, X-mas, NULL flags, FIN scan attacks) |
| VLAN (planned) |
Tag based VLAN separation |
| Mobile quota control |
Custom data limits for both SIM cards |
| WEB filter (planned) |
Blacklist for blocking out unwanted websites, Whitelist for specifying allowed sites only |
| Access control |
Flexible access control of TCP, UDP, ICMP packets, MAC address filter |
|
VPN
|
|
| OpenVPN |
Multiple clients and server can be running simultaneously, 12 encryption methods |
| OpenVPN Encryption |
DES-CBC, RC2-CBC, DES-EDE-CBC, DES-EDE3-CBC, DESX-CBC, BF-CBC, RC2-40-CBC, CAST5-CBC, RC2-64-CBC, AES-128-CBC, AES-192-CBC, AES-256-CBC |
| IPSec |
IKEv1, IKEv2, with 5 encryption methods (DES, 3DES, AES128, AES192, AES256) |
| GRE |
GRE tunnel |
| Stunnel (planned) |
Proxy designed to add TLS encryption functionality to existing clients and servers without any changes in the program’s code |
| PPTP, L2TP |
Client/Server services can run simultaneously, L2TPv3 support |
| DMVPN (planned) |
Method of building scalable IPsec VPNs |
| SSTP (planned) |
SSTP client instance support |
| ZeroTier |
ZeroTier VPN client support |
| WireGuard |
WireGuard VPN client and server support |
|
Serial Communication Modes
|
|
| Modes |
Console, OverIP, Modem (Full or Partial control), MODBUS RTU master, MODBUS gateway, NTRIP client (planned) |
|
Modbus
|
|
|
Modbus TCP Slave
|
|
| ID filtering |
Respond to one ID in range [1;255] or any |
| Allow remote access |
Allow access through WAN |
| Custom registers |
MODBUS TCP custom register block, which allows to read/write to a file inside the router, and can be used to extend MODBUS TCP slave functionality |
|
Modbus TCP Master
|
|
| Supported functions |
01, 02, 03, 04, 05, 06, 15, 16 |
| Supported data formats |
8 bit: INT, UINT; 16 bit: INT, UINT (MSB or LSB first); 32 bit: float, INT, UINT (ABCD (big-endian), DCBA (little-endian), CDAB, BADC), HEX, ASCII |
|
Modbus RTU Master
|
|
| Supported baud rates |
From 300 to 3000000 |
| Supported functions |
01, 02, 03, 04, 05, 06, 15, 16 |
| Supported data formats |
8 bit: INT, UINT; 16 bit: INT, UINT (MSB or LSB first); 32 bit: float, INT, UINT (ABCD (big-endian), DCBA (little-endian), CDAB, BADC), HEX, ASCII |
| Number of data bits |
7 or 8 |
| Number of stop bits |
1 or 2 |
| Parity bits |
None, Even, Odd |
| Flow control |
None, RTS/CTS (only for RS232 interface), Xon/Xoff |
|
MQTT Gateway
|
|
| Gateway |
Allows sending commands and receiving data from MODBUS Master trough MQTT broker |
|
Data to Server
|
|
| Protocols |
HTTP(S), MQTT, Azure MQTT, Kinesis |
|
Monitoring & Management
|
|
| WEB UI |
HTTP/HTTPS, status, configuration, FW update, CLI, troubleshoot, event log, system log, kernel log |
| FOTA |
Firmware update from server, automatic notification |
| SSH |
SSH (v1, v2) |
| SMS |
SMS status, SMS configuration, send/read SMS via HTTP POST/GET |
| TR-069 |
OpenACS, EasyCwmp, ACSLite, tGem, LibreACS, GenieACS, FreeACS, LibCWMP, Friendly tech, AVSystem |
| MQTT |
MQTT Broker, MQTT publisher |
| SNMP |
SNMP (v1, v2, v3), SNMP Trap |
| JSON-RPC |
Management API over HTTP/HTTPS |
| Modbus |
Modbus TCP status/control |
| RMS |
Teltonika Remote Management Systems (RMS) |
|
IoT Platforms
|
|
| Cloud of Things |
Allows monitoring of: Device data, Mobile data, Network info, Availability |
| ThingWorx |
Allows monitoring of: WAN Type, WAN IP Mobile Operator Name, Mobile Signal Strength, Mobile Network Type |
| Cumulocity |
Allows monitoring of: Device Model, Revision and Serial Number, Mobile Cell ID, ICCID, IMEI, Connection Type, Operator, Signal Strength, WAN Type and IP |
| Azure IoT Hub |
Can send device IP, Number of bytes send/received/ 3G connection state, Network link state, IMEI, ICCID, Model, Manufacturer, Serial, Revision, IMSI, Sim State, PIN state, GSM signal, WCDMA RSCP, WCDMA EC/IO, LTE RSRP, LTE SINR, LTE RSRQ, CELL ID, Operator, Operator number, Connection type, Temperature, PIN count to Azure IoT Hub server |
| System Characteristics |
|
| CPU |
Qualcomm QCA9531, MIPS 24kc, 650 MHz |
| RAM |
64 MB, DDR2 |
| Flash storage |
16MB SPI Flash (4 MB available for user) |
|
Firmware / Configuration
|
|
| WEB UI |
Update FW from file, check FW on server, configuration profiles, configuration backup |
| FOTA |
Update FW/configuration from server |
| RMS |
Update FW/configuration for multiple devices |
| Keep settings |
Update FW without losing current configuration |
|
Firmware Customization
|
|
| Operating system |
RutOS (OpenWrt based Linux OS) |
| Supported languages |
Busybox shell, Lua, C, C++ |
| Development tools |
SDK package with build environment provided |
|
Location Tracking
|
|
| GNSS |
GPS, GLONASS, BeiDou, Galileo and QZSS |
| Coordinates |
GNSS coordinates via WebUI, SMS, TAVL, RMS |
| NMEA |
NMEA 0183 |
| NTRIP (planned) |
NTRIP protocol (Networked Transport of RTCM via Internet Protocol) |
| Server software |
Supported server software TAVL, RMS |
| Geofencing |
Configurable multiple geofence zones |
|
Input/Output
|
|
| Configurable I/O |
3 x Configurable Inputs/Outputs. Digital input 0 - 6 V detected as logic low, 8 - 30 V detected as logic high. Open collector output, max output 30 V, 300 mA |
| Analog input |
1 x Analog input (0 - 30 V) |
| Output control |
HTTP POST/GET, Schedule |
| Events |
SMS, Email |
| I/O juggler |
Allows to set certain I/O conditions to initiate event |
|
Serial
|
|
| RS232 |
Terminal block connector: TX, RX, RTS, CTS |
| RS485 |
Terminal block connector: D+, D-, R+, R- (2 or 4 wire interface) |
| Supported baud rates |
From 300 to 3000000 |
| Number of data bits |
7 or 8 |
| Number of stop bits |
1 or 2 |
| Parity |
None, Even, Odd |
| Flow control |
None, RTS/CTS (only for RS232 interface), Xon/Xoff |
|
Power
|
|
| Connector |
2 pins in 16 pin industrial terminal block |
| Input voltage range |
9 – 30 VDC, reverse polarity protection, surge protection +/-1 kV 50 µs max |
| Power consumption |
Idle: <1.2 W, Max: <5 W |
|
Physical Interfaces (Ports, Led's, Anntenas, Buttons, Sim)
|
|
| Ethernet |
1 x RJ45 port, 10/100 Mbps |
| I/O’s |
3 x Configurable I/O, 1 x Analog input in 16 pin terminal block |
| Status LEDs |
3 x connection status LEDs, 3 x connection strength LEDs, 1 x power LED, 1 x Eth port status LED |
| SIM |
2 x SIM slots (Mini SIM – 2FF), 1.8 V/3 V, double stacked SIM tray |
| Power |
2 pins in 16 pin terminal block |
| Antennas |
1 x SMA connector for LTE, 1 x SMA connector for GNSS |
| RS232 |
4 pins in 16 pin terminal block (TX, RX, RTS, CTS) |
| RS485 |
4 pins in 16 pin terminal block (D+, D-, R+, R-) |
| Reset |
Reboot/User default reset/Factory reset button |
|
Physical Specifications
|
|
| Casing material |
Aluminium housing with DIN rail mounting option |
| Dimensions (W x H x D) |
83 x 25 x 74.2 mm |
| Weight |
165 g |
| Mounting options |
DIN rail, wall mounting (additional kits needed), flat surface placement |
|
Operating Environment
|
|
| Operating temperature |
-40 ℃ to 75 ℃ |
| Operating humidity |
10% to 90% non-condensing |
Resources