Fieldbus and industrial Ethernet, both ways
The SimtoLink protocol converter moves data both ways among Modbus RTU/TCP, OPC UA/DA, Profibus-DP, EtherNet/IP, CANopen, and DeviceNet, covering fieldbus and industrial Ethernet. That is how older machines join a system that was built later.
Pass-through and register mapping cover an equipment upgrade or a system-integration job. Parsing runs on an FPGA or a dedicated chip, and conversion delay stays under 10ms. The converters are already in power, metals, petrochemical, and rail plants, with more than 5000 units deployed, and they sit with mainstream PLC, DCS, and instrument brands.
Protocols it can carry
Models differ by protocol and by how many ports they have. The table is the usual set.
| Protocol family | Typical protocols | Typical use |
|---|---|---|
| Fieldbus | Modbus RTU/TCP, Profibus-DP | PLC, instruments, DCS |
| Industrial Ethernet | EtherNet/IP, OPC UA | Robots, MES, SCADA |
| CAN bus | CANopen, DeviceNet | Vehicles, rail |
| OPC | OPC UA, OPC DA | Host systems, cloud platforms |
Custom parsing can be loaded, and the register map is configurable. Master and slave roles can be swapped. Some models run as a protocol gateway, taking several protocols in and one stream out. A protocol library and configuration templates ship with the unit. Firmware can be updated, and a new protocol can be added over OTA.
Jobs it has already done
Power-plant DCS, line-side MES, and rail integrated monitoring all use the same idea: an old protocol on one side, a newer system on the other.
Mixed robot brands on one line
A line turned EtherNet/IP and Modbus robots from several makers into OPC UA, which the MES then reads.
Old and new rail systems on one network
A metro project converted existing CAN bus vehicle data to Ethernet and brought it into a new integrated monitoring system, so the old cars and the new system run together.
Several protocols on a metals line
A metals plant folded PLC, instrument, and drive data into OPC UA and sent it to SCADA and the production system.
How to configure it
- Name the protocols. Write down the source device and the target system. Map registers and points one to one, and watch byte order and data-type conversion.
- Prove it, then install it. Check the map in the lab before it goes on site. Keep the control network isolated so it is not left open on the plant LAN.
- When a point will not move. If a protocol will not line up, check byte order, data type, and register address. Keep a backup of the configuration so a failed unit can be swapped without rebuilding the map.
- Help on the job. SimtoLink configures the unit, supplies a protocol analyzer, and can work the fault on site. A protocol that is not in the library can be written to order.
From survey to live monitoring
Take the job in this order:
SimtoLink configures the conversion so the two systems can be joined without a long integration cycle.
Support
SimtoLink helps choose and configure the converter, writes custom protocol support when the standard library is not enough, and can analyze a fault on site. Manuals and quotations are available on request.