Open search


Four isolated CAN interfaces

Sontheim’s eSys-IDC4E1 allows the connection of different CAN networks over IP networks. The CAN-to-Ethernet gateway provides one LAN connection and four galvanically isolated CAN interfaces.

The CAN manage bit-rates from 50 kbit/s to 1 Mbit/s (Photo: Sontheim)

IN ADDITION, THE MODULE PROVIDES A VARIETY OF MEASUREMENT and diagnostic functions in machine fieldbus systems. The gateway provides one LAN connection to transfer the data to a higher-level computer. For monitoring the CAN network, active resistance measurement and error-frame-detection is implemented. The gateway possesses its own logic for detecting error frames and counting them up in a specific internal memory area. This can be used for finding intermittent errors like the falsified messages of a CAN participant. The gateway offers a 32-bit Freescale Power PC micro-controller and aluminum housing with IP 30. It has an operating temperature of 0 °C to 60 °C.

The company’s pass-thru API is supplied as a standard interface with the device. Thus, the module can be used for applications based on J2534. Further higher level protocols can be implemented on demand. The software architecture of the CAN module consists of a host device structure in which a x86 PC-system as a host uses the module for access to the CAN network. For communication between host and device Ethernet is used. The communication takes place via IP and a proprietary, UDP-based communication protocol.

The methodology provided by TCP to recover lost packets did not meet the performance requirements, which is why high-performing method was developed: For the identification (Discover) of the CAN interfaces over LAN, a process is used which is in accordance to ISO 13400. The firmware of the CAN module is composed of a main thread, which handles the CAN communication and is also able to handle the transport layer communication protocols (e.g. J1939-21/J1939-81, ISO 15765), and a diagnostic thread for self- and CAN-diagnostics. All non-related services to the direct communication of the CAN module, such as the configuration of the bridging or CAN-diagnostics, are handled over to the so-called „toolbox“ protocol. The order of the received message at the host interface is the same order as on the physical bus, regardless of whether the message was sent or received. Thus, a high-performing communication is guaranteed at a low latency.

Publish date



Kvaser Sontheim