Connecting To A Remote Plc Controller; Conveylinx Network Architecture; Understanding Assemblies - Pulseroller ConveyLinx-IO User Manual

Connecting to a Remote PLC Controller

55
C R PLC C
ONNECTING TO A EMOTE ONTROLLER
ConveyLinx-IO is a device that requires a remote PLC controller to connect and transfer data to control its digital
I/O points. This section describes the network architecture utilized for the module and provides the data mapping
details to access I/O for the 3 main protocols that the module recognizes.
C L N A
ONVEY INX ETWORK RCHITECTURE
Each module communicates to its adjacent modules and to any connected PC or PLC via Ethernet physical media.
ConveyLinx modules recognize (3) TCP/IP based protocols: Modbus TCP, Profinet I/O, and EtherNet/IP. Modbus
TCP is the "native" protocol for communications between ConveyLinx modules and the EasyRoll PC software.
When ConveyLinx modules create connections between them, they utilize Modbus TCP for inter-module
communication. EtherNet/IP is recognized by ConveyLinx modules and any given module can be attached to an
EtherNet/IP capable PLC (Allen-Bradley ControlLogix or CompactLogix platforms for example) and be recognized as
a "Generic Ethernet Module" or explicitly as a module by using Insight Automation provided EDS file. Profinet I/O
is recognized by the modules and can be attached to any Profinet I/O capable PLC (applicable Siemens platforms).
All protocols access the same internal data locations on a given module.
Each ConveyLinx-IO module's internal data structure is arranged and addressed as Modbus Holding registers. The
on-board communication and control processes attach logical meanings to each holding register and read and
write data to specific registers to initiate and/or react to events. Certain registers contain information as to how
the module is configured (Inputs, Outputs, polarity etc.) for its local controls.
U A
NDERSTANDING SSEMBLIES
The holding registers described above we will define as Module Register Addresses and are used for the function
of the module regardless of if any remote PLC or PC is connected. There are many Module Register Addresses that
are used for the operation of the module that are not applicable, required, or should even be made available to a
remote PLC. When connecting to a PLC, the module needs to gather certain specific Module Register Addresses
located scattered throughout the entire listing of Module Register Addresses into a concise contiguous group or
Assembly that the PLC can efficiently read from and write to. Figure 32 illustrates this concept.
Publication ERSC-1008 Rev 1.1 – October 2017