open up a variety of connection possibilities
With bridges and gateways CAN or CAN FD systems can be coupled or implemented over a larger area, devices without CAN can be connected to CAN systems or CAN systems can be coupled using different technologies, e.g. Bluetooth, Ethernet or PROFINET.
Expand your system
Bridges and gateways enable larger system expansions and increase the reliability of your system.
Cloud connection
MQTT cloud connection enables remote monitoring and alarms (CAN@net NT). HMS-Hub and OPC UA support (CANnector Bridge/Range).
Save costs
Easier wiring and reduction of cables reduces the cost of your system.
Actions
Execution of various actions using event-triggered rules (CAN@net NT & CANbridge NT) as well as C user code execution and graphical trigger engine (CANnector Bridge/Range).
Data manipulation
Filter and conversion functionality reduces network load and simplifies interconnection of various devices.
Connection-friendly
Bridging of large distances, easy system access and retrofitting of old devices using Bluetooth, Ethernet, PROFINET, CAN and CAN FD.
Learn more about bridges and gateways and see how they work
CAN bridges and CAN gateways are infrastructure components with which complex network structures can be implemented.
A CAN bridge can connect CAN or CAN FD networks of different bit rates or protocols with each other. It is based on the store-(modify)-forward principle where CAN / CAN FD messages are received by a sub-network and then transmitted to the other sub-network. Translation and filter rules can also be used, allowing a protocol adaptation to be carried out between the sub-networks. Unlike the CAN / CAN FD repeater, the CANbridge enables the enlargement of the maximum network size so that the sub-systems are fully self-sufficient with regard to bus arbitration. Independent of each other in terms of their real-time behavior, CAN sub-networks connected by bridges are to be regarded as independent networks.
The bridge function can also be executed with the aid of other transmission systems. For example, the CAN-Ethernet-CAN bridge is connected via two Ethernet-TCP/IP gateways which enable connection to remote CAN / CAN FD networks.
As an extension to the CAN bridges, CAN gateways allow for access to CAN networks via other communication systems. In each case, the protocols of the connected bus systems are mapped to the other communication model.
Application samples:
Compare the bridge / gateway functionality
| CANbridge NT420 | CAN@net NT420 | CANnector Range/Bridge | |
| CAN / CAN FD ports (max) | 4 | 4 | 6 (thereof 2 CAN FD) |
| LIN | 0 | 0 | 2 |
| Digital IOs / Analog inputs | 0 | 0 | 2 / 0 |
| Frame / Signal based configuration | Yes / No | Yes / No | Yes / Yes (DBC, LDF, Fibex, ARXML, ESI) |
| Signal visualization / Web browser | – | – | Web browser / OPC UA / APP |
| Filter | Yes | Yes | Yes |
| Data logger | – | – | Yes* (USB, PC) |
| Programming (C user code) | – | – | Yes with Eclipse IDE and Debugger |
| Matlab / Simulink | – | – | Yes* |
| Further interfaces / Protocols | – | ETH, MQTT | USB, ETH, WLAN*, Bluetooth, EtherCAT slave*, 2 x CAN FD* |