Using the RMC ENET with Programmable Controllers

Ethernet Compatibility

It is important to understand that the RMC ENET module will not be able to communicate with every device designated as communicating via Ethernet and TCP/IP. These two sets of standards—Ethernet and TCP/IP—specify the electrical specifications and routing protocols, but do not specify the content or format of the data that is transmitted. The data format is called the Application Protocol. For a complete list and diagram of protocols supported by the RMC Ethernet module, see RMC Ethernet Protocols.

This issue is closely analogous to serial ports. Two devices must agree on signal levels, baud rate, and data, stop, and parity bits. However, these serial devices still cannot communicate if they do not understand one another's data. Example: Try connecting a serial cable between a PC running TISOFT and an Allen-Bradley SLC 5/05. TISOFT expects one protocol, while the Allen-Bradley expects another.

It is important to know which devices the RMC supports. We support the following devices, and any other device that communicates with the same protocol as one of these:

It is Delta's goal to support all major Ethernet devices. However, we need your feedback to determine which Ethernet devices are being used, so please call Delta Computer Systems, Inc. to discuss additional Ethernet device support.

PC-Based Control and HMI Packets

Any existing software package that supports reading from or writing to one of the above PLCs should be able to read from and write to the RMC. Most such packages will support at least one of these devices. See Using Other Ethernet Packages with the RMC ENET for further details.

Communicating with Ethernet TCP/IP Masters

For further details on communicating between the RMC and a PLC Ethernet TCP/IP master, select one of the following topics:

 


Copyright (c) 1997-2015 by Delta Computer Systems, Inc.