- LTE CAT 4 up to 150 MBps
- Configurable Inputs / Outputs
- GNSS positioning
- RS232 / RS485 serial communication interface
- Teltonika Remote Management System
- Dual SIM
The industrial LTE CAT 4 Gateway TRB245 is equipped with a GNSS receiver, Ethernet leg and durable 16 pin connector block. This Gateway contains all essential applications for industry in one: secure energy connector, I / O ports, series communication, fast and reliable internet.
The TRB245 can be used to integrate modern and legacy industrial equipment into one solution and offers a large number of software applications such as SMS control, Firewall, open VPN, IPSec, RMS user can be assured that the data can be reached safely and without compromise.
More information about the Teltonika TRB245
Mobile |
|||
Mobile module |
4F (LTE) - Cat 4 up to 150 Mbps, 3G - Up to 42 Mbps, 2G - Up to 236.8 kbps |
||
SIM switch |
2 SIM cards, auto-switch caes, weak signal, data limit, sms limit, when roaming, not network, network denied, data connection failed |
||
Status |
Signal strength, Connected band, SINR, RSRP, RSRQ, Bytes sent/received |
||
Bridge |
Direct connection (bridge) between mobile ISP and device on LAN |
||
SMS |
SMS status, SMS configuration, SMS send / read via HTTP POST / GET, EMAIL to SMS (scheduled), SMS to EMAIL (scheduled), SMS to HTTP (scheduled), SMS to SMS (scheduled), SMS to SMS (scheduled, scheduled SMS (scheduled), SMS auto reply (scheduled) |
||
Black / White list |
Operator black / white list |
||
Multiple PDN's |
Ability to use different PDNs for multiple network access and services |
||
Bandwidth |
Used band satus display, Band lock (scheduled) |
||
APN |
automatic APN |
||
|
|
||
Ethernet |
|
||
LAN |
1x LAN port 10/100 Mbps, complies with IEEE 802.3, IEEE 802.3u standards, supports auto MDI / MDIX |
||
|
|
||
Network |
|
||
Routing |
Static routing, Dynamic routing (BGP, OSPF, v2, RIP v1 / v2) |
||
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 |
||
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 en ICMP for link inspection |
||
Firewall |
Port Forward, Periodic Reboot, LCP en ICMP for link inspection |
||
QoS (planned) |
priority queue by source/destination, service, protocol or port, WMM, 802.11e |
||
DDNS |
Supports > 25 service providers, others can be configured manually |
||
SSHFS |
Ability to mount external file system via SSH protocol |
||
|
|
||
Security |
|
||
Authentication |
Pre-shared key, digital certificates, X.509-certificates |
||
Firewall |
Preconfigured firewall rules can be used 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-man, NULL flags, FIN scan attacks) |
||
VLAN (planned) |
Tagbased VLAN separation |
||
Mobile quotacontrole |
Custom data limits for both SIM cards | ||
WEB-filter (planned) |
Blacklist for blocking unwanted websites, whitelist for specifying only allowed websites |
||
Access control |
Flexible access control of TCP, UDP, ICMP packets, MAC address filter |
||
|
|
||
VPN |
|
||
Open VPN |
Multiple clients and servers can be run simultaneously, 12 encryption methods |
||
Open VPN-coding |
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) |
||
PPTP, L2TP |
Client / Server services can be activated simultaneously |
||
DMVPN (planned) |
Method for building scalable IPsec VPNs |
||
GRE (planned) |
GRE tunnel |
||
|
|
||
Serial communication Modes |
|||
|
Over iP, Modem (planned), Modbus RTU-master, Modbus-gateway, NTRIP-client (planned) |
||
|
|
||
Modbus TCP Slave |
|
||
ID-filtering |
Respond to one ID in range [1; 255] or any |
||
Allow external access |
Allow access via WAN |
||
Custom registers |
Modbus TCP custom register block, which allows reading/writing to a file in the router and can be used to extend modbus TCP layer functionality |
||
|
|
||
Modbus TCP Master |
|
||
Supported features |
01, 02, 03, 04, 05, 06, 15, 16 |
||
Custom registers |
8 bit: INT, UINT; 16 bit: INT, UINT (MSB or LSB first); 32 bit, float, INT, UINT (ABCD (big-endian), CDAB, BADC) |
||
|
|
||
Modbus RTU Master |
|
||
Supported baud rates |
Van 300 tot 3000000 |
||
Supported features |
01, 02, 03, 04, 15, 16 |
||
Supported file formats |
8 bits: INT, UINT; 16bit: INT, UINT (MSb or LSB first); 32 bit: float, INT, UINT (ABCD (big-edian), DCBA (little-endian), CDAB, BADC) |
||
Number of data bits |
7 of 8 |
||
Number of stop bits |
1 0f 2 |
||
Parity bits |
None, Even, Odd |
||
Pass-through |
None, RTS/CTS (Only for RS232 interface), Xon/Xoff |
||
|
|
||
MCTT Gateway |
|
||
Gateway |
Allows sending commands and receiving data from Modbus Master via MQTT broker |
||
|
|
||
Modbus-data to server |
|||
Protocols |
HTTP(S), MQTT, Azure MQTT (planned |
||
|
|
||
Monitoren & management |
|||
WEB UI |
HTTP / HTTPS, status, configuration, FW update, CLI, troubleshooting, event log, system log, kernel log |
||
FOTA |
Firmware update from server, automatic notification |
||
SSH |
SSH (v1, v2) |
||
SMS |
SMS-status, SMS-configuration, SMS send / read via HTTP POST / GET |
||
Call |
Restart, Status, Mobile date on / off, Output on / off, answer / hang up with a timer |
||
TR-069 |
Open ACS, EasyCwmp, ACSLite, tGem, LibreACS, GenieACS, FreeACS, LibCWMP, friendly technology, AVSystem |
||
MQT |
MQTT Broker, MQTT publisher |
||
SNMP |
SNMP (v1, v2, v3) SNMP Trap |
||
JSON-RPC |
Management API via HTTP/HTTPS |
||
Modbus |
Modbus TCP status/control |
||
RMS |
Teltonika Remote Management Systemen (RMS) |
||
|
|
||
IOT Platforms |
|
||
Cloud of Things |
Enables monitoring of: device data, mobile data, network information, availability |
||
Thingworx |
Enables monitoring of: WAN IP Mobile operator name, Mobile signal strength, Type of mobile network |
||
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 |
Netwok link status, IMEI, ICCID, Model, Manufacturer, Serial, Revision, IMSI, Sim status, PIN status, GSM signal, WCDMA RSCP , WCDMA EC / IO, LTE RSRP, LTE SINR, LTE RSRQ, CELL ID, Operator, Operator number, connection type, Temperature, number of PINs to Azure IoT Hub server. |
||
|
|
||
System features |
|
||
CPU |
Qualcomm QCA9531, MIPS, 24kc, 650 MHz |
||
RAM |
64 MB, DDR2 |
||
Flash memory |
16 MB SPI Flash (4MB available for user) |
||
|
|
||
Firmware / Configuration |
|
||
WEB UI |
Update FW from file, check FW on server, configuration profiles, configuration backup, restore point |
||
FOTA |
Update FW / configuration from server |
||
RMS |
Update FW / configuration for multiple devices |
||
Keep settings |
Update FW without losing current configuration |
||
|
|
||
Firmware modifications |
|
||
Operating system |
RutOS (OpenWRT gebaseerd Linux OS) |
||
Supported languages |
Busybox-shell, lua, C, C ++ |
||
Development tools |
SDK-package with build environment included |
||
|
|
||
Location tracking |
|
||
GNSS |
GPS, GLONASS, BeiDou, Galileo en QZSS |
||
Coordinates |
GNSS-coordinates via WebUI, SMS, TAVL, RMS |
||
NMEA |
NMEA 0183 |
||
NTRIP |
NTRIP protocol (network transport of RTCM via internet protocol) |
||
Server software |
Supported server software TAVL, RMS |
||
Mobile network |
Location without using GPS, obtain an approximate location based on |
||
Geolocalization |
mobile tower on RMS |
||
Geofencing |
Multiple configurable geofence-zones |
||
|
|
||
Input / Output |
|
||
Configurable I / O |
3x configurable inputs/outputs, Digital input 0 - 6 V detected as logic low, 8 - 30 V detected as logic high, Open-collector output, max output 30VV, 300 mAh |
||
Analog input |
1x analog input (0 - 30 V) |
||
Events |
SMS, Email |
||
Output control |
HTTP POST/GET, Schedule |
||
I/O juggles |
Allows you to set certain I/O conditions to start an event |
||
|
|
||
Serial |
|
||
RS232 |
Terminal block connector: TX, RX, RTS, CTS |
||
RS485 |
Terminal block connectorr: D +, D-, R +, R- (2- of 4-wire interface) |
||
Supported baud rates |
from 300 to 3000000 |
||
Number of data bits |
7 of 8 |
||
Number of stop bits |
1 of 2 |
||
Parity |
None, Even, Odd |
||
Flow control |
None, RTS / CTS (only for RS232-interface), Xon / Xoff |
||
|
|
||
Power |
|
||
Connector |
2 pin in 16 pin industrial power socket |
||
Input voltage reach |
9 - 30 VDC, reverse polarity protection, overvoltage protection +/- kV 50 μs max |
||
Power consumption idle |
< 1.2 W, Max |
||
|
|
||
Physical interfaces (ports, LEDs, antennas, button, SIM card) |
|||
Ethernet |
1x RJ45-port, 10/100 Mbps |
||
I/O’s |
3x configurable I / O, 1x analog input in 16-pin terminal block |
||
Status LED’s |
3x connection status LEDs, 3c connection strength LEDs, 1x power LED, 1x Eth port status LED |
||
SIM |
2x SIM slots (Mini SIM - 2FF), 1.8 V / 3 V, double-stacked SIM tray |
||
Power supply |
2 pins in 16-pin terminal block | ||
Antenna |
1x SMA-connector for LTE, 1x SMA-connector for GNSS |
||
RS232 |
4-pin in 16-pin terminal block (TX, RX, RTS, CTS) |
||
RS485 |
4-pin in 16-pin terminal block (D +, D-, R +, R-) |
||
Reset |
Restart, reset to user default (scheduled), restore to factory settings |
||
|
|
||
Physical specifications |
|
||
Enclosure |
aluminium enclosure with DIN-rail mount option |
||
Dimensions |
83 x 25 x 74 mm |
||
Weight |
165 g |
||
Mounting |
DIN rail, wall mounting (additional kits required), placement on a flat surface |
||
|
|
||
Operating environment |
|
||
Operating environment |
-40º to + 75ºC |
||
Operating humidity |
10% to 90% non-condensing |
Teltonika Specification downloads |
---|
Teltonika TRB245 Gateway Data Sheet |
Halderbergselaan 7a
4741 AA Hoeven
The Netherlands
T: 0031 165 380003
info@icmt-antennas.com
To optimize the user-friendliness of our website and services, we use cookies. However, for the placement of some cookies, we do require your consent. If you would like to learn more about the cookies we use and the data we collect with them, please read our privacy statement