10 other plcs and pc-based control packages, Using other ethernet packages with the rmc enet, 11 custom ethernet devices and applications – Delta RMC101 User Manual
Page 427: Using sockets to access the rmc enet, Other plcs and pc-based control packages -177, Custom ethernet devices and applications -177
Ethernet 5.2
Communications
5-177
5.2.6.10 Other PLCs and PC-based Control Packages
5.2.6.10.1 Using Other Ethernet Packages with the RMC ENET
The RMC can emulate a number of Ethernet PLC devices. A list of those supported is described
in RMC Ethernet Module Overview. Any device or PC-based software package that can read and
write registers in devices that the RMC ENET can emulate can most likely also read and write
registers in the RMC. For example, a number of Human-Machine-Interfaces (HMI) can access
registers in Allen-Bradley PLCs over Ethernet. Most of these will also be able to access registers
in the RMC as well.
Similarly, any device that can read or write registers using one of the RMC's application protocols
can also communicate with the RMC. For example, Wonderware's InControl PC-based control
package supports a Modbus/TCP SuiteLink driver and can therefore control an RMC over
Ethernet. Another example is Control Microsystems' SCADAPack PLC with the 5905 Ethernet
Gateway, which supports Modbus/TCP and therefore can also control an RMC over Ethernet.
It is best to contact a Delta Computer Systems, Inc. sales engineer to discuss Ethernet devices
that are not explicitly listed as compatible with the RMC. There may be subtle problems with
using some devices with the RMC. For example, a device that proclaims Modbus/TCP support
may only be a slave. The RMC is also a slave and therefore neither device will initiate transfers,
preventing the devices from being able to work together. By talking with a sales engineer, we
receive feedback on the devices our customers want to communicate with and may lead to
enhancements in our documentation and device support.
5.2.6.11 Custom Ethernet Devices and Applications
5.2.6.11.1 Using the RMCLink ActiveX Control and .Net Assembly Component
There are two main ways to communicate to the RMC over Ethernet from a custom application:
• The RMCLink ActiveX Control and .Net Assembly Component can be used if the application
is running on Windows. See the RMCLink ActiveX Control and .Net Assembly Component topic
for details.
• A TCP/IP API such as BSD Sockets or Winsock can be used to directly write over TCP/IP. This
method is not limited to Windows or even PCs. See Using Sockets to Access the RMC ENET for
details.
5.2.6.11.2 Using Sockets to Access the RMC ENET
There are two main ways to communicate to the RMC over Ethernet from a custom application:
• The RMCLink ActiveX Control and .Net Assembly Component can be used if the application
is running on Windows. See RMCLink topic for details.
• A TCP/IP API such as BSD Sockets or Winsock can be used to directly write over TCP/IP. This