LTE Cat.1 RTU. State of the Art RTU for SCADA applications (IEC 60870-5-104/Modbus - TCP or RTU - mapping). The DinBox RTU Q7 uses IEC 60870-5-104 to communicate as a slave with the SCADA system (master). Other protocols such as MQTT, Modbus RTU, TCP are also implemented. The DinBox RTU SL+ has 8 digital inputs and 2 Analog inputs and 2 digital outputs. Thanks to the Modbus master implementation and the modbus-to-IEC104 slave mapping, the DinBox RTU Q7 can be used as a gateway to connect other Modbus slave IEDs.The DinBox RTU Q7 can be mass managed by a DeMas (Data Management Software) back office tool. The DB RTU Q7 comprises an embedded Linux system based on container technology allowing new SW applications to be integrated. It also contains application SW including e.g. (SCADA) communication protocols, libraries, and lifecycle management logic as well as a bootloader and tools for development, debugging and deployment.
Highlights
- 4G LTE Cat-1
- IEC 60870-5-104/Modbus mapping
- MQTT/Modbus mapping
- 8DI, 2AI, 2DO
- Mass Management by DEMAS
- Ethernet Routing
- TLS Security & VPN IPsec IKE v1
- Powerful processor allowing 'fast routing'
- Supercap ‘Last gasp’
- 'NIS2 proof'
Specifications
- Housing:
Type: Phoenix Dinrail enclosure
Housing material: Reinforced polyamide fiber
Housing type: DINrail housing side element, two pieces necessary to close base element, 1,5mm thick.
DINrail snapslot for easy DINrail mounting
Color: green
Dimensions housing: : 172 mm x 35 mm x 135 mm
Ambient temperature (operation) -40°C +105°C
Inflammability class acc. to UL 94: HB
Power dissipation at 20°C in horizontal mounting position: 8.9W 18.3W
IP51
RAL 5004 - Power Supply:
220-240 AC or DC 24/48 V
Supercap optional - Communication engine:
Sierra Wireless RC7620-1 (CF3 footprint) 4G LTE
Cat-1 GSM module.
SIM card and/or eSIM eUICC possibilities
50 ohm SMA antenna connector - Environmental:
Operating Temperature: -20° C +55° C
Operating Humidity 10-75 % non-condensing - Processors:
NXP i.MX6 Solo
DDR3L 512B dual chip RAM
eMMC 8GB flash
RTC with separate power backup - Interface & Connectors:
RS-232 non-isolated (used for debugging)
RS-485 / 2-wire galvanically isolated (used fo
Modbus connection)
LAN or WAN 10/100Mbit/s
MMC/SD memory card holder
8x DI active 24 Vdc
2x DO optomos 'solid state', 600 Vpeak / 90 mA
2x AI 0-5 Vdc, non-isolated, 12-bit single ended ADC - Firmware:
Software Packages:
Container technology (docker)
Kernel (Linux 5.4 Mainline kernel)
DNS
NTP Server and Client
TCP/IP IPv4 (IPv6 in future possible)
DHCP
IPSec
PPP (Point to Point Protocol)
Telegraf Agent (Server for collecting and reporting of metrics)
Nftables (Firewall)
OpenSSH
OpenSSL
Hardware Watchdog
Container:
Open PLC
Protocol Converter
Modbus RTU Master
Modbus TCP Master
IEC 60870-5-104 Server (Client Optional)
IEC 61850 Client Ed2
MQTT v5 Client - Security:
Dual Boot for fallback on Firmware update failure
The Firmware is a FIT Image and hashed using SHA-256, encrypted using AES-256-CBC and signed with a X.509 Cert, using a 4096 bit RSA key. The cert check and decryption is done by U-Boot, which has the needed AES and Cert Info embedded. U-Boot is on the internal EMMC, so there is no way to easily extract it. Without a proper HAB4 signature you cannot boot another Bootloader from Micro-SD . The FIT Image further has a HAB4 signature, which is tested by the CPU (HAB4 is unknown, closed source by NXP).
The NXP i.MX6 CPU features the HAB4 secure boot. The Cert is programmed into OTP (one time programmable) fuses and then the CPU is closed to boot only Bootloaders signed with the correct Cert.
The fuse burning process is irreversible. On Reset the CPU starts its Bootloader in ROM and loads/verifies the Bootloader U-Boot. U-Boot loads/verifies the Firmware, which is a signed, hashed and encrypted FIT image. - Certification:
CE
-
folderDatasheet
- file_download DB RTU SL+_Product_Letter.pdf
-
foldergeneral
-
foldermanuals
Log in to reply