Uses for the RMC ENET Module
The RMC ENET module allows the RMC to communicate with other Ethernet devices, including many PLCs and PCs. This port can be used in a number of ways, as listed below:
Control or Monitoring from a Third Party PLC or Software Package
This is the most common and powerful use for the RMC ENET module. The RMC can emulate the Ethernet protocols of most major PLCs, including PLCs from the following manufacturers: Allen-Bradley, Automationdirect.com, Modicon, Omron, Siemens, and SoftPLC. As a result, any PLC or PC-based control or HMI package that can access data in one of these PLCs should be able to access data in the RMC. See Using the RMC ENET with Programmable Controllers for details.
Communication with RMCWin
The RMC ENET module allows communication with RMCWin in place of the serial port connection. Using Ethernet in place of a serial cable to communicate between the RMC and RMCWin has the following advantages:
Much higher performance than RS232 in most cases (using low-speed connections such as modems will slow this down).
Longer cable distances are allowed.
Eliminates running the extra serial cable if it would otherwise not be used.
Allows addressing many RMCs from a single PC without switching serial cables or adding more serial ports to the PC.
See Using the RMC ENET with RMCWin for more details.
Control or Monitoring from a Custom Device or Software
Some advanced users will want to write their own control or HMI package on the PC. There are several options available for such users:
For Windows-based applications, the RMC ENET ActiveX Control provides a simple interface for communicating with the RMC over Ethernet. Visual Basic, Java, and Visual C++ all support ActiveX Controls. See the RMCLink topic for details.
For any applications with access to a TCP/IP API (such as Winsock for Windows and BSD Sockets for Unix), any of the protocols supported by the RMC can be used. See Using Sockets to Access the RMC ENET for details.
Note: The RMC ENET does not support any of the native protocols built into Windows. That is, the RMC does not support Web browsers, FTP, e-mail, and browsing through Network Neighborhood.
Configuring the RMC Ethernet Module
Setting up the RMC Ethernet module requires entering only a few TCP/IP parameters: configuration type, IP address, subnet mask, and gateway address. See RMC Ethernet IP Address Setup for details on entering these values. Users who have set up networks before will find it straight-forward to select these values. First-time TCP/IP users will need to read the following topics for suggestions on values to use:
Note: It is not necessary to select the application protocol or device with which you will be communicating. The RMC will automatically respond to all supported devices.
Ethernet Module LEDs
LAN LED
The LAN LED indicates when network traffic is being sent or received:
LINK LED
The LINK LED indicates whether the physical Ethernet link is up or down.
Off: The Ethernet link is down.
Steady Green: The Ethernet link is up.
Ethernet Module Firmware
The RMC Ethernet Protocols are divided into two different firmware files. When updating the RMC100 Ethernet firmware, you must choose the file that contains the protocol you need. The files are called Protocol Group E and Protocol Group F:
New RMC100-ENET modules will be shipped with Protocol Group E. However, both groups are available for download from the Delta website, and both are supported.
RMC ENET Supported Numbers of TCP and CIP Resources
TCP Connections:
4 TCP connections (all inbound)
Examples:
RMCWin
Each EtherNet/IP I/O connection is set up using an EtherNet/IP TCP connection
Any other PLC communication
CIP Connected Messaging:
The RMC ENET limits CIP connections as follows:
Max of 8 total CIP connections
Max of 4 I/O CIP connections
Examples:
EtherNet/IP I/O Data connection with a ControlLogix
EtherNet/IP Input Data connection with a ControlLogix
ControlLogix message to RMC ENET (cache enabled)
Copyright (c) 1997-2015 by Delta Computer Systems, Inc.