Developers Guide

Version 5.
0
Includes ERSC Firmware
Version 4.25 and Version 5.2
March 2016
Publication ERSC-1500
ConveyLinx module firmware and functionality is protected by U.S. and international patents.
For complete patent information visit www.pulseroller.com/patents
Glossary of Terms 3
GLOSSARY OF TERMS
Conveyor controls architecture based upon modular distributed devices connected via
ConveyLinx
Ethernet network.
Optional functionality available for ConveyLinx systems to provide controlled stop and
ConveyStop
reset of MDR function. Requires software package to configure and enable.
Ethernet Roller Speed Control module - Conveyor control module that is part of the
ERSC
ConveyLinx family. Each ERSC Can accommodate up to 2 MDR conveyor zones
Ethernet/IP (Ethernet Industrial Protocol) is a network communication standard capable
of handling large amounts of data at speeds of 10 Mbps or 100 Mbps, and at up to 1500
bytes per packet. The specification uses an open protocol at the Application layer. It is
especially popular for control applications.
Ethernet/IP typically employs active star network technology. This type of network is
Ethernet I/P easy to set up, operate, maintain, and expand. It allows mixing of 10 Mbps and 100 Mbps
products, and is compatible with most Ethernet switches. Ethernet/IP is used with
personal computers, mainframes, robots, input/output (I/O) devices and adapters,
programmable logic controllers (PLCs), and other devices. The specification is supported
by the Industrial Ethernet Association (IEA), ControlNet International (CI), and the Open
DeviceNet Vendor Association (ODVA).
This is the name of a particular connector manufacturer that produces a specific
JST plug/socket arrangement for MDR connection to control cards. This name is accepted
within the conveyor and MDR industry as a simple description of the particular socket
style used on ERSC hardware.
Carton A separate (usually wrapped or boxed) object to be transported by the conveyor. The
terms tray, tote, or load may also be used interchangeably in this document.
Motorized Drive Roller or Motor Driven Roller - Brushless DC motor and gearbox
MDR
assembly integrated into a single conveyor roller.
Application layer messaging protocol at Level 7 of the OSI Model that provides
client/server communication between devices connected on different types of buses or
networks. The Modbus messaging structure was developed by Modicon in 1979.
Different versions of Modbus used today include Modbus RTU (based on serial
communication like RS485 and RS232), Modbus ASCII and Modbus TCP, which is the
Modbus RTU protocol embedded into TCIP packets. It's an open protocol, meaning the
Modbus TCP specification is available free of charge for download, and there are no licensing fees
required for using Modbus or Modbus TCP/IP protocols.
Modbus TCP/IP specification was developed in 1999 to combining a ubiquitous physical

network (Ethernet) with a universal networking standard (TCP/IP) and a vendor-neutral
data representation. Modbus TCP/IP used the Modbus instruction set and wraps TCP/IP
around it.
A device, mounted near the end of the conveyor zone to sense the presence of a Carton
Photo-sensor
on the zone
Programmable Logic Controller – A wide variety of industrial computing devices that
PLC
control automatic equipment
Publication ERSC-1500 Rev 5.0 – March 2016

PROFINET IO uses traditional Ethernet hardware and software to define a network that
Profinet I/O structures the task of exchanging data, alarms and diagnostics with Programmable
Controllers and other automation controllers.
Registered Jack Style 11 / 12 – Standard connector / receptacle format utilizing 4 or 6 pin
RJ-11 / RJ-12 connections. The typical standard connection for telephones. RJ-11 utilizes 4 pins and
RJ-12 utilizes 6 pins but both styles use the same physical size.
Registered Jack Style 45 – Standard connector / receptacle format utilizing 8 pin
RJ-45
connections. The typical standard for computer network cable connections
Transport Control Protocol / Internet Protocol - IP is the protocol which oversees the
transmission of information packets from device to device on an Ethernet network. TCP
TCP/IP makes sure the packets have arrived and that the message is complete. These two
protocols are the basic language of the Internet and are often referred to together as
TCP/IP.
Conveyor control method for zone configured conveyor that dictates that when a zone is
Train Release
discharging, the upstream zone’s Carton can move in unison with the discharging Carton.
Zone A basic (linear or curved) cell of the conveyor consisting of a set of slave rollers driven by
one or more MDR’s and a single photo-sensor.
Zero Pressure Accumulation – Term that describes the conveyor controls and mechanical
ZPA scheme that will cause Cartons to queue on a conveyor in discrete zones such that
Cartons do not touch each other
SYMBOL CONVENTIONS
This symbol indicates that special attention should be paid in order to ensure correct use
as well as to avoid danger, incorrect application of product, or potential for unexpected
results
This symbol indicates important directions, notes, or other useful information for the
proper use of the products and software described herein.
Important User Information 5
IMPORTANT USER INFORMATION

ConveyLinx ERSC modules contain ESD (Electrostatic Discharge) sensitive parts and
components. Static control precautions are required when installing, testing, servicing or
replacing these modules. Component damage may result if ESD control procedures are not
followed. If you are not familiar with static control procedures, reference any applicable
ESD protection handbook. Basic guidelines are:
• Touch a grounded object to discharge potential static
• Wear an approved grounding wrist strap
• Do not touch connectors or pins on component boards
• Do not touch circuit components inside the equipment
• Use a static-safe workstation, if available
• Store the equipment in appropriate static-safe packaging when not in use
Because of the variety of uses for the products described in this publication, those
responsible for the application and use of this control equipment must satisfy themselves
that all necessary steps have been taken to assure that each application and use meets all
performance and safety requirements, including any applicable laws, regulations, codes,
and standards
The illustrations, charts, sample programs and layout examples shown in this guide are
intended solely for purposes of example. Since there are many variables and requirements
associated with any particular installation, Insight Automation Inc. does not assume
responsibility or liability (to include intellectual property liability) for actual use based on
the examples shown in this publication
Reproduction of the contents of this manual, in whole or in part, without written

permission of Insight Automation Inc. is prohibited.

6 PLC Developer’s Guide
SUMMARY OF CHANGES
The following table summarizes the changes and updates made to this document since the last revision
Revision Date Change / Update

4.0 June 2011 Added functionality to Ethernet I/P Instances.
Added more example applications and Instance items for optional
4.1 February 2012
functionality
General format revisions, changed title to PLC Developer’s Guide, added
4.2 October 2012
Assemblies for Modbus TCP, added examples
4.3 November 2013 Added Servo control registers to Instances 7/8 and Servo Control example
4.4 January 2014 Added Global Contact Information
4.5 April 2014 Updated Global Contact Information
4.6 June 2014 Added ConveyStop registers to instances
4.7 September 2014 Added Profinet I/O to charts, removed Rockwell PLC connect instructions
4.8 February 2015 Updated confusing wording in Instance charts
5.0 January 2016 Major revision for added functionality in firmware 4.25/5.2
GLOBAL CONTACT INFORMATION

Table of Contents 7
TABLE OF CONTENTS
Glossary of Terms....................................................................................................................................................... 3
Symbol Conventions .............................................................................................................................................. 4
Important User Information ........................................................................................................................................ 5
Summary of Changes ................................................................................................................................................. 6
Global Contact Information ........................................................................................................................................ 6
Table of Contents ........................................................................................................................................................ 7
Preface ......................................................................................................................................................................... 9
Who Should Use This Manual? ............................................................................................................................ 9
Not Included in This Manual ................................................................................................................................. 9
Introduction to ConveyLinx® ................................................................................................................................... 11
ConveyLinx® Concept ......................................................................................................................................... 11
ConveyLinx ERSC Operational Modes ............................................................................................................. 13
ZPA Mode .........................................................................................................................................................13
PLC I/O Mode ...................................................................................................................................................13
ConveyLinx Network Architecture .......................................................................................................................... 15
Understanding Assemblies ................................................................................................................................. 15
Modbus Assembly Instance Structure ............................................................................................................... 16
Ethernet I/P Assembly Instance Structure ........................................................................................................ 18
Profinet IO Assembly Instance Structure .......................................................................................................... 19
PLC Controller with ZPA Mode ............................................................................................................................... 21
Notes About Assemblies for ERSC in ZPA Mode ........................................................................................... 21
Register Chart Legend ....................................................................................................................................21
ZPA Mode Assembly Inputs for PLC ................................................................................................................. 22
ZPA Mode Note ① ..........................................................................................................................................24
ZPA Mode Note ② ..........................................................................................................................................25
ZPA Mode Assembly Outputs for PLC .............................................................................................................. 26
ZPA Mode Note ③ ..........................................................................................................................................29
ZPA Mode Note ④ ..........................................................................................................................................29
ZPA Mode Note ⑤ ..........................................................................................................................................29
ZPA Mode Note ⑥ ..........................................................................................................................................30
ZPA Mode Note ⑦ ..........................................................................................................................................30
ZPA Mode Note ⑧ ..........................................................................................................................................31
ZPA Mode Examples ........................................................................................................................................... 32
Example 1 – Basic Accumulate and Release with Tracking Data ............................................................32
Example 2 – Basic Bar Code Reader ...........................................................................................................36
Example 3 – Upstream Accept Interface ......................................................................................................37
Example 4 – Downstream Discharge Interface ...........................................................................................39
Example 5 – Simple Divert Example .............................................................................................................41
Example 6 – Merge onto ZPA Main Line ......................................................................................................43
Reduced Size ZPA Mode Assemblies ............................................................................................................... 45
Reduced Size ZPA Mode Assembly Inputs .................................................................................................45
Reduced Size ZPA Mode Assembly Outputs ..............................................................................................46
PLC Controller with PLC I/O Mode......................................................................................................................... 47
Setting PLC I/O Mode in EasyRoll ..................................................................................................................... 48
Optional “Clear Connections” Choice ............................................................................................................49
Configuring Action for Loss of Communication ...........................................................................................50
PLCI/O Mode Assembly Inputs .......................................................................................................................... 51

PLC I/O Mode Note ① ....................................................................................................................................53

PLC I/O Mode Note ② ....................................................................................................................................53
PLC I/O Mode Note ③ ....................................................................................................................................53
PLC I/O Mode Note ④ ....................................................................................................................................54
PLC I/O Mode Note ⑤ ....................................................................................................................................54
PLC I/O Mode Assembly Outputs ...................................................................................................................... 55
PLC I/O Mode Note ⑥ ....................................................................................................................................59
PLC I/O Mode Note ⑦ ....................................................................................................................................59
Servo Motor Control Example............................................................................................................................. 61
PLC Ladder Diagram .......................................................................................................................................63
Reduced Size PLC I/O Mode Assemblies ........................................................................................................ 65
Reduced Size PLC I/O Mode Assembly Inputs ...........................................................................................65
Reduced Size PLC I/O Mode Assembly Outputs ........................................................................................66
ConveyLogix Interface Assemblies ........................................................................................................................ 67
ConveyLogix Assembly Inputs ........................................................................................................................... 67
ConveyLogix Assembly Outputs ........................................................................................................................ 68
ZPA and PLC I/O Mode Assemblies with Reset Protection ............................................................................... 69
ZPA Mode Assembly Inputs with Reset Protection ......................................................................................... 70
ZPA Mode Assembly Outputs with Reset Protection ...................................................................................... 71
Reduced Size ZPA Mode Assembly Inputs with Reset Protection ............................................................... 72
Reduced Size ZPA Mode Assembly Outputs with Reset Protection ............................................................ 72
PLC I/O Mode Assembly Inputs with Reset Protection ................................................................................... 73
PLC I/O Mode Assembly Outputs with Reset Protection................................................................................ 74
Reduced Size PLC I/O Mode Assembly Inputs with Reset Protection ......................................................... 75
Reduced Size PLC I/O Mode Assembly Outputs with Reset Protection ...................................................... 75
Reset Protection Usage with the PLC ............................................................................................................... 76
Appendix A - Motor Port as Digital I/O ................................................................................................................... 77
Appendix B – ConveyLinx Connections ................................................................................................................ 79
ZPA Mode Register Data Flow ........................................................................................................................... 79
External Controller as ConveyLinx Bridge ........................................................................................................ 80
Appendix C – Modbus Registers for Firmware 5.2 .............................................................................................. 83
ZPA Mode Assembly Inputs................................................................................................................................ 84
ZPA Mode Assembly Outputs............................................................................................................................. 85
Reduced Size ZPA Mode Assembly Inputs ...................................................................................................... 86
Reduced Size ZPA Mode Assembly Outputs ................................................................................................... 87
PLC I/O Mode Assembly Inputs ......................................................................................................................... 88
PLC I/O Mode Assembly Outputs ...................................................................................................................... 89
Reduced Size PLC I/O Mode Assembly Inputs ............................................................................................... 90
Reduced Size PLC I/O Mode Assembly Outputs ............................................................................................ 90
ZPA Mode Assembly Inputs with Reset Protection ......................................................................................... 91
ZPA Mode Assembly Outputs with Reset Protection ...................................................................................... 92
Reduced Size ZPA Mode Assembly Inputs with Reset Protection ............................................................... 93
Reduced Size ZPA Mode Assembly Outputs with Reset Protection ............................................................ 94
PLC I/O Mode Assembly Inputs with Reset Protection ................................................................................... 95
PLC I/O Mode Assembly Outputs with Reset Protection................................................................................ 96
Reduced Size PLC I/O Mode Assembly Inputs with Reset Protection ......................................................... 97
Reduced Size PLC I/O Mode Assembly Outputs with Reset Protection ...................................................... 97
Notes: ......................................................................................................................................................................... 99

Preface 9
PREFACE
WHO SHOULD USE THIS MANUAL?

This manual is intended for users who need to utilize a PLC or PC to connect to ConveyLinx Ethernet network to
access module status and control conveyor operation.
You should have an intermediate to advanced level of understanding of PLC logic and network structures.
Familiarity with at least one of Modbus TCP, Ethernet I/P, or Profinet I/O protocols is also essential.
You should have a basic understanding of electrical circuitry and familiarity with relay logic, conveyor equipment,
photoelectric sensors, etc. in order to follow example scenarios and sample programs included herein. If you do
not, obtain the proper training before using this product.
For basic understanding of ERSC module hardware and simple application and installation guidelines, please refer
to Insight Automation publication ConveyLinx User’s Guide (publication ERSC-1000)
NOT INCLUDED IN THIS MANUAL

Because system applications vary; this manual assumes users and application engineers
have properly sized their power distribution capacity per expected motor loading and
expected operational duty cycle. Please refer to conveyor equipment and/or motor
roller manufacturer’s documentation for power supply sizing recommendations.

Introduction to ConveyLinx® 11
INTRODUCTION TO CONVEYLINX®
CONVEYLINX® CONCEPT
ConveyLinx control system as applied to conveyor control is a series of individual ConveyLinx ERSC modules
interconnected via standard Ethernet cabling to form an integrated solution for MDR (Motorized Drive Roller)
conveyor functionality. Each ConveyLinx ERSC module can accommodate up to 2 MDR’s and 2 photo-sensors to
provide control for up to 2 conveyor zones. Each ERSC also includes convenient connectivity ports for upstream
and downstream Ethernet network cabling as well as connectivity ports for discrete I/O signals with non-
networked controls for local interlock interface functions.
FIGURE 1 - CONVEYLINX® CONCEPT WITH ERSC MODULES
ConveyLinx ERSC modules can be easily automatically configured to operate multiple zones of linear conveyor
“right out of the box” with the push of a button without any special tools or PC software required. However, with
the ConveyLinx EasyRoll software tool and a PC; each ERSC module’s default configuration can be modified to
customize functionality for specific applications.
Please refer to Insight Automation publication ConveyLinx User’s Guide for ConveyLinx
ERSC module hardware details and basic function. The remaining sections of this
document assumes reader if familiar with ConveyLinx ERSC module and EasyRoll software
operation.

Introduction to ConveyLinx® 13
CONVEYLINX ERSC OPERATIONAL MODES

Each and every ERSC module on a conveyor system functions in only one of two possible operational modes:
• Zero Pressure Accumulation (ZPA) Mode

• PLC I/O Mode (with or without ConveyLogix program)
These operational modes dictate which of the modules data registers are valid for use by a networked external
controller.
ZPA MODE
ZPA Mode is the default mode of any ERSC that has been configured by the Auto-Configuration Procedure. In this
mode, each ERSC has established logical connections to its neighboring ERSC modules in order to operate conveyor
with Zero Pressure Accumulation (ZPA) functionality. No external controller is required for the conveyor to
function and operation is as described in ConveyLinx User’s Guide (publication ERSC-1000).
PLC I/O MODE

In PLC I/O Mode, the ERSC suspends all automatic ZPA functionality and its input, output and motor control
functions are explicitly controlled by a networked external logic controller. The external controller reads from and
writes to the ERSC’s internal data registers over the Ethernet network using Ethernet I/P or Modbus TCP protocol
in order to initiate all ERSC functionality.
ERSC module can only be placed in PLC I/O Mode with EasyRoll software
tool and only after it has been through an Auto-Configuration Procedure.
IMPORTANT CONCEPT TO REMEMBER: A PLC or external controller can

connect and interact with any ERSC regardless of whether it is in ZPA or
PLC I/O Mode. PLC I/O Mode requires a PLC or external controller for
operation. ZPA Mode ERSC can interface with a PLC or external controller
to report local module status and provide local zone interaction.

The following chart provides a Quick Reference for the operational modes:
ERSC Control Strategy Quick Reference
•
Any Available to any Modbus TCP, Profinet I/O, or Ethernet I/P networked
device regardless of Module Mode
Read Status •
Mode •
Read Sensor & Control port inputs
Read MDR diagnostics
• Out of the Box

• No PLC required
• Hard-wired connections available to control zone stop/release
Default • Some electrical connections may require RJ-12 to terminal breakout
module for signal compatibility
• See User’s Guide for connection details
• Ethernet I/P, Profinet I/O, or Modbus TCP Networks supported

ZPA • PLC can control over the network: zone accumulate/release, tracking
Interface PLC data read/write, zone speed, monitor sensor & control port inputs
Mode • See page 21 for I/O register details
• See page 32 for Examples
Interface PLC
• All functions available with Default configuration
+ • All functions available with Interface PLC
• Using EasyRoll, allow PLC access to Control Port digital output signal
Port Outputs • See page 32 for Examples
• Requires Mode change to PLC I/O in EasyRoll

• Suspends ALL ZPA functionality
• PLC has complete access and control of Sensor Port Inputs and Control
Port Inputs and Output
• PLC has complete control of both MDR ports (speed, accel/decel,
open/closed loop, braking method, etc.)
Interface PLC • See page 48 for setting PLC I/O Mode
• See page 51 Input register descriptions
PLC I/O • See page 55 for Output register descriptions
• See page 61 for servo movement example
Mode • One or both MDR ports can be changed to provide up to 3 high
powered digital outputs (1A each) per MDR port for a total of 6 digital
outputs available. See page 69 for details
• Requires Mode change to PLC I/O in EasyRoll

• Requires user program download from ConveyLogix software
ConveyLogix • Does NOT require Interface PLC, but does support interface
• See page 67 for details on ConveyLogix interface with PLC

ConveyLinx Network Architecture 15
CONVEYLINX NETWORK ARCHITECTURE

Each ERSC 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 I/P. Modbus
TCP is the “native” protocol for communications between ConveyLinx modules and the EasyRoll PC software.
When ConveyLinx modules are used even for basic ZPA control with no external connections to a PC or PLC, they
utilize Modbus TCP for inter-module communication. Ethernet I/P is recognized by ConveyLinx modules and any
given ERSC can be attached to an Ethernet I/P capable PLC (Allen-Bradley ControlLogix or CompactLogix platforms)
and be recognized as a “Generic Ethernet Module” or explicitly as an ERSC by using Insight Automation provided
EDS file. Profinet I/O is recognized by ERSC 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 ERSC.
Each ERSC’s internal data structure is arranged and addressed as Modbus Holding registers. The on-board ERSC
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 ERSC is
configured (MDR type, speed, direction, etc.) for its local controls. Other registers are used for inter-module
communications for conveyor operation. For example, when an upstream ERSC has a Carton ready to discharge to
its neighboring downstream ERSC, the upstream ERSC will write a specific value to a specific address in the
downstream ERSC’s internal registers. The downstream ERSC’s on board logic monitors these registers and knows
that a specific value means that an upstream Carton is coming and to engage the proper control logic to convey
the Carton.
Because ConveyLinx utilizes an open architecture (Modbus TCP) for inter-module communications; with proper
definition and expected usage of certain register address locations, external control devices (PC’s and PLC’s) can
easily interact with ERSC modules to monitor and control various points along the conveyor path.
UNDERSTANDING ASSEMBLIES
The holding registers described above we will define as Module Register Addresses and are used for the function
of the ERSC regardless of if any remote PLC or PC is connected. There are many Module Register Addresses that
are used for the operation of the ERSC that are not applicable, required, or should even be made available to a
remote PLC. When connecting to a PLC, the ERSC 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 2 illustrates this concept.

FIGURE 2 - PLC ASSEMBLY CONCEPT
So, no matter which of the three connection protocols you use (Modbus TCP, EIP, or Profinet I/O), for any given
assembly, the internal data you are accessing with your PLC is the same.
MODBUS ASSEMBLY INSTANCE STRUCTURE

Each ERSC utilizes Modbus register architecture for remote data access over Ethernet. Modbus TCP is a simple
protocol for data exchange based upon a query/response mechanism. Each ERSC’s memory structure contains a
fixed array of internal data locations that are constructed as Modbus Holding Registers. Each ERSC has a fixed
reserve of Holding Registers with each capable of holding a 16-bit numerical integer value. Modbus TCP protocol
provides for read/write access to any available Holding Register. The structure of these registers allows for
individual ERSC’s to read from and write to specific register address locations to achieve inter-module
communications. Certain registers are read from and written to by the EasyRoll software in order to monitor
and/or change default configuration values such as MDR speed, direction, type, etc.
Modbus TCP addressing convention utilizes a “4:xxxx” notation. The “4:” in Modbus
protocol designates that the address is a Holding Register and the xxxx is a numerical
value representing the offset or index for a specific location. The “xxxx” values used in
this document are to be interpreted as if they are for a Modbus PLC which means that the
first register address is “4:0001” and that there is no “4:0000” register. Some PLC data
structures and PC development environments utilize the “4:0000” designation and their
indexes will be offset by 1. Please refer to your PLC or PC application documentation for
the Modbus convention used on their platforms.

Any Modbus TCP capable PC or PLC can connect to any ERSC visible on its network and access Input and Output
Holding Register Assemblies. The ERSC supports the following Modbus TCP Service Codes:
• Service Code 3 - Read Holding Register (up to 45 registers per instruction)

• Service Code 6 - Write Single Register
• Service Code 16 - Write Multiple Registers (up to 45 registers per instruction)
• Service Code 23 - Read/Write Multiple Registers (up to 45 registers per instruction)
When using Input and Output Assemblies with Modbus TCP PLC, it is important to always
use the first address shown in the assembly group as the beginning register to read or
write regardless of which register in the assembly is needed by the PLC. Trying to access
Input or Output Assemblies starting with any register in the assembly other than the first
register will cause the ERSC to return an error.
For example, for ZPA Mode Assembly Inputs, if you only need to read register 4:1504; your
I/O connection set-up in your PLC must use the starting address of 4:1500 and a sufficient
length of registers to read (in this example at least 5 registers) in order to get to the
desired register. If you set up your PLC to start reading at 4:1504, the ERSC will return an
error.
For more information and open protocol specification, please visit www.modbus.org
All Modbus Addresses in the following Assembly Charts are

valid for Firmware 4.25 and earlier.
For Firmware 5.2 and higher: Modbus register addressing for all
Assemblies are different from firmware 4.25 and previous. Please refer to
Appendix C – Modbus Registers for Firmware 5.2 for firmware 5.2 and
higher assembly addresses.

ETHERNET I/P ASSEMBLY INSTANCE STRUCTURE

When an ERSC is attached to an external Ethernet I/P controller (Logix 5000 based PLC), it is done so as a Generic
Ethernet I/O device or by installing EDS file(s) provided by Insight Automation.
For this manual Ethernet I/P Instances are described using the Generic
Ethernet I/O method of connection. Consult pulseroller.com for more
information on obtaining EDS file(s) for incorporation into your RSLogix5000
development software.
Part of this procedure in the PLC is to instruct the Generic device as to which data configuration or instance of
Ethernet I/P the Generic device is to use to report and respond to data to and from the PLC.
From this point forward, it is assumed the reader is familiar with Allen-Bradley Logix
platform addressing notation:
[ModuleName]:O.Data[Index].Bit
[ModuleName]:I.Data[Index].Bit
Where:
• ModuleName is the user-defined name of the device
• “O.Data” indicates data written by the PLC to the device
• “I.Data” indicates data read by the PLC from the device
• “[Index].Bit” indicates the word and bit within the image. If the bit notation is
absent the notation refers to the entire word data type
These instances essentially group the appropriate Modbus registers into contiguous Input and Output array image
that fit into the Allen-Bradley Logix 5000 controller tags.
Please refer to Connecting ConveyLinx to Rockwell PLC’s –

Insight Automation publication ERSC-1520 for details on how to
connect ConveyLinx to Rockwell Ethernet I/P capable PLCs.

PROFINET IO ASSEMBLY INSTANCE STRUCTURE

Prior to connecting any modules to a Profinet IO capable (Siemens) PLC, a GSDXML configuration file needs to be
installed in your PLC programming software (i.e. STEP 7 or TIA Portal). The GSDXML file contains, among other
things, the definition of memory size required when connecting a module to a Siemens PLC with Profinet IO. When
assigning an individual module to a PLC, you decide what memory address to use. The GSDXML file stipulates that
each module requires 64 bytes of input data from the module to the PLC and 64 bytes of output data from the PLC
to the module. When assigning an individual module to a PLC, you decide what physical PLC memory address to
use as the beginning of these 64 byte blocks.
In all of the charts showing module data registers and their assigned function, for Profinet IO these are indicated as
“Byte 0, Byte 1,...Byte 32”, etc. These are offsets from the starting address in the Siemens PLC memory assigned
by the Siemens programming software when the module was installed into the network. For example, if a
module’s inputs are installed beginning at %IB256, then from our charts, the data for “Byte 6 and Byte 7” would be
at addresses %IB262 and %IB263 respectively.
Please refer to Connecting ConveyLinx to Profinet PLCs – Insight

Automation publication ERSC-1525 for details on how to connect
ConveyLinx to Profinet I/O capable PLCs.

PLC Controller with ZPA Mode 21
PLC CONTROLLER WITH ZPA MODE

When an ERSC is in its default ZPA mode, an external networked PLC or PC controller can connect to the ERSC and
perform the following:
• Instruct either or both the upstream and downstream zone to accumulate the next Carton that arrives
• Receive indication that a new Carton has arrived at either zone
• Receive indication that a Carton has departed from either zone
• Read tracking data associated with Carton at accumulated zone
• Update tracking data associated with Carton at accumulated zone
• Instruct accumulated zone to release Carton and accumulate on next Carton arrival
• Change the MDR speed for either zone
• Remove accumulation control and return zone to normal operation
• Read fault and error status of either zone or motor
• Optionally take over control of either or both Control Ports
NOTES ABOUT ASSEMBLIES FOR ERSC IN ZPA MODE

When an ERSC is in ZPA Mode, its primary task is to operate its local conveyor zones and respond to its immediate
upstream and downstream conditions. External PLC controller interaction with an ERSC in ZPA mode is intended to
be for decision point monitoring and general status data gathering. Upstream and Downstream zones work
exactly the same for zone control, only the register address are different depending on which zone (or both) that
need to be controlled
In general, when utilizing ZPA Mode registers; “upstream” and “downstream” registers
are logically determined by conveyor flow after the system has been Auto-Configured and
will not necessarily be associated with the ERSC’s physical “left” or “right” side’s
connections. For motor and port specific I/O items, register’s description will explicitly
indicate “left” or “right”.
For ERSC modules that are auto-configured as single zone, regardless of whether the left
or right side is physically used as the single zone; external controller must use the
“Upstream” control registers to interface with the single zone.
REGISTER CHART LEGEND

M: 4:1502
Indicates Modbus TCP Addressing Notation
E: I.Data[2]
Indicates Ethernet I/P Addressing Notation
P: Byte 4 (Hi) Byte 5 (Lo)
Indicates Profinet I/O Addressing Notation

ZPA MODE ASSEMBLY INPUTS FOR PLC

This chart shows the data sent to the PLC from the ERSC when connected. All registers in the ERSC are 16-bit
integer data type.
Register Name / Assembled Address

Description
Module Address for PLC
Local Status Upstream M: 4:1500 (Low Byte)
Zone Forward Direction E: I.Data[0] (Low Byte)
4:0116 P: Byte 1
M: 4:1500 (High Byte)

Local Status Upstream E: I.Data[0] (High Byte) Unsigned Value of Byte
Zone Reverse Direction P: Byte 0 0x01 = Zone sensor clear and motor stopped
4:0116
0x02 = Zone sensor clear, motor running, accepting from upstream zone
0x04 = Zone sensor blocked, motor running, discharging to downstream zone
Local Status M: 4:1501 (Low Byte) 0x05 = Zone sensor blocked and motor stopped
Downstream Zone E: I.Data[1] (Low Byte) 0x06 = Busy (state during ConveyStop active mode)
Forward Direction P: Byte 3 See ZPA Mode Note ① on page 24 for further details
4:0196
Local Status M: 4:1501 (High Byte)
Downstream Zone E: I.Data[1] (High Byte)
Reverse Direction P: Byte 2
4:0196
Arrival Count Local M: 4:1502 Unsigned Integer Value
Upstream Zone E: I.Data[2] • Increments by 1 each time a Carton arrives in the zone
4:0106 P: Byte 4 (Hi) Byte 5 (Lo) • Value rolls over from 65,535 back to 0
Departure Count Local M: 4:1503 Unsigned Integer Value
Upstream Zone E: I.Data[3] • Increments by 1 each time a Carton departs the zone
Arrival Count Local M: 4:1504 Unsigned Integer Value
Downstream Zone E: I.Data[4] • Increments by 1 each time a Carton arrives in the zone
Departure Count Local M: 4:1505 Unsigned Integer Value
Downstream Zone E: I.Data[5] • Increments by 1 each time a Carton departs the zone
Bitwise Value - Read only
bit 0 = Module Reset Flag – 1 when module resets, 0 when PLC connected
bit 1 = Reserved
bit 2 = Over-Voltage – Module power supply has exceeded 30V
bit 3 = Left Motor Error – bits 7 thru 15 indicate specific error
bit 4 = Ethernet Connections NOT OK
bit 5 = Upstream Jam Error
M: 4:1506 bit 6 = Left Sensor Error
Module Status Word 1
E: I.Data[6] bit 7 = Low Voltage Error – Module Power Supply less than 18V
4:0088
P: Byte 12 (Hi) Byte 13 (Lo) bit 8 = Left Motor Over-heated – Calculated temperature over 120°C
bit 9 = Left Motor Over-current – Over limit for selected MDR
bit 10 = Left Motor Short Circuit
bit 11 = Left Motor Not Connected
bit 12 = Left Motor Overload – MDR slower than 10% of selected speed
bit 13 = Left Motor Stalled
bit 14 = Left Motor Hall Sensor Error
bit 15 = Left Motor Not Used


Description
bit 0 = Reserved
bit 1 = Reserved
bit 2 = Over-Voltage – Module power supply has exceeded 30V
bit 3 = Right Motor Error
bit 4 = Reserved
bit 5 = Downstream Jam Error
M: 4:1507 bit 6 = Right Sensor Error
Module Status Word 2
E: I.Data[7] bit 7 = Low Voltage Error - Module Power Supply less than 18V
4:0089
P: Byte 14 (Hi) Byte 15 (Lo) bit 8 = Right Motor Over-heated - Calculated temperature over roller’s max
bit 9 = Right Motor Over-current - Over limit for selected MDR
bit 10 = Right Motor Short Circuit
bit 11 = Right Motor Not Connected
bit 12 = Right Motor Overload – MDR slower than 10% of selected speed
bit 13 = Right Motor Stalled
bit 14 = Right Motor Hall Sensor Error
bit 15 = Right Motor Not Used
Current Upstream Zone M: 4:1508 When Carton is accumulated in UPSTREAM zone:
Tracking Word 1 E: I.Data[8] Value = Tracking data word #1 (16 bit integer) for the Carton currently
4:0119 P: Byte 16 (Hi) Byte 17 (Lo) accumulated and stopped in the module’s Upstream zone.
Current Upstream Zone M: 4:1509 When Carton is accumulated in UPSTREAM zone:
Tracking Word 2 E: I.Data[9] Value = Tracking data word #2 (16 bit integer) for the Carton currently
4:0120 P: Byte 18 (Hi) Byte 19 (Lo) accumulated and stopped in the module’s Upstream zone.
Current Downstream M: 4:1510 When Carton is accumulated in DOWNSTREAM zone:
Zone Tracking Word 1 E: I.Data[10] Value = Tracking data word #1 (16 bit integer)for the Carton currently
4:0199 P: Byte 20 (Hi) Byte 21 (Lo) accumulated and stopped in the module’s Downstream zone.
Current Downstream M: 4:1511 When Carton is accumulated in DOWNSTREAM zone:
Zone Tracking Word 2 E: I.Data[11] Value = Tracking data word #2 (16 bit integer) for the Carton currently
4:0200 P: Byte 22 (Hi) Byte 23 (Lo) accumulated and stopped in the module’s Downstream zone.
Current Release Count M: 4:1512 Copy of the current value in the Release Upstream output register which can be
for Upstream Zone E: I.Data[12] used by PLC logic to confirm release count prior to writing new data to the
4:0105 P: Byte 24 (Hi) Byte 25 (Lo) Release Upstream output register
Current Release Count M: 4:1513 Copy of the current value in Release Downstream which can be used by PLC logic
for Downstream Zone E: I.Data[13] to confirm release count prior to writing new data to the output Release
4:0185 P: Byte 26 (Hi) Byte 27 (Lo) Downstream register
When ERSC is discharging to Non-ConveyLinx controlled conveyor:
Get Tracking Forward M: 4:1514
Direction Word 1 E: I.Data[14] Value = Tracking data word #1 (16 bit integer) for the Carton that has just
4:0201 P: Byte 28 (Hi) Byte 29 (Lo) discharged from the local downstream zone when local conveyor is operating in
default or “forward” direction.
When module is discharging to Non-ConveyLinx controlled conveyor:
Get Tracking Forward M: 4:1515
default or “forward” direction.
Get Tracking Reverse M: 4:1516
Direction Word 1 E: I.Data[16] Value = Tracking data word #1 (16 bit integer) for the load that has just
opposite of default or “reverse” direction.


Description
Get Tracking Reverse M: 4:1517
opposite of default or “reverse” direction.
bit 00 = Left Sensor Port - Pin 3
bit 01 = Left Control Port - Pin 3
bit 02 = Right Sensor Port - Pin 3
bit 03 = Right Control Port - Pin 3
Sensor & Control M: 4:1518 bit 04 = Left Sensor Port - Pin 4
Port Inputs E: I.Data[18] bit 05 = Left Control Port - Pin 4
4:0035 P: Byte 36 (Hi) Byte 37 (Lo) bit 06 = Right Sensor Port - Pin 4
bit 08 thru bit 14 = Reserved
bit 15 = 2 sec on / 2 sec off heartbeat
See ZPA Mode Note ② on page 25

M: 4:1519
Reserved E: I.Data[19]
bit 00 – bit04 = Reserved
bit 05 = Stop active on other module in Stop Group
bit 06 = Stop active due to lost communication connection
bit 07 = Stop active due to lost PLC connection
M: 4:1520 bit 08 = Stop active on local module’s Left Control Port
ConveyStop Status
E: I.Data[20] bit 09 = Stop active on local module’s Right Control Port
4:0019
P: Byte 40 (Hi) Byte 41 (Lo) bit 10 = Stop active due to Stop Command from PLC
bit 11- bit 15 = Reserved
Refer to Insight Automation publication ERSC-1800 ConveyStop User’s Guide

for details on using ConveyStop.
ZPA MODE NOTE ①

The values 0xXX01 thru 0xXX06 are shown because these are the possible logical values used for inter-module
communication. External networked devices (PLC or PC) monitoring these registers may; depending on their scan
rate, not actually see each of these values change in sequence as a Carton is conveyed from zone to zone, even
though the inter-module communications and ZPA is functioning normally.
IMPORTANT NOTE: Status register values utilize both the HIGH BYTE and the LOW BYTE of
the 16-Bit integer value. The HIGH BYTE is used for zone status for reversing conveyor
applications and MAY CONTAIN DATA. PLC/PC programmers working with single direction
conveyor applications MUST MASK THE HIGH BYTE or otherwise ignore the high byte in
processing status data from these registers.

For PLC/PC programming purposes, you can only depend on seeing values 0xXX01 and
0xXX05 in program logic for determining zone status. The values 0xXX02 and 0xXX04 may
not always be visible to PLC/PC from inter-module communication depending upon speed
of the conveyor, length of the zone, and/or location of the zone sensors.
ZPA MODE NOTE ②

The values for the signals on the Sensor ports (bit 0, bit 2, bit 4, and bit 6) are determined by the module’s initial
Auto-Configuration results and the bit values are set to a 1 when sensor is blocked and 0 when sensor is clear
regardless of the sensor type used. For example, each Sensor port Pin 4 signal is for the sensor’s output. If the
sensor is light energized, N.O. then the electrical signal on Pin 4 is ON when the sensor is clear and OFF when the
sensor is blocked. However when reading bit 4 or bit 6 in this register, the bit will be a 1 when the sensor is
blocked and 0 when the sensor is clear.

ZPA MODE ASSEMBLY OUTPUTS FOR PLC

These registers are written by the PLC to the ERSC when the module is in ZPA mode. All registers are 16-bit Integer
data type.

Description
Write value for 16 bit integer tracking data word #1 for the Carton accumulated
Set Local Upstream M: 4:1600
in the Upstream Zone.
Zone Tracking Word 1 E: O.Data[0]
4:0132 P: Byte 0 (Hi) Byte 1 (Lo)
See ZPA Mode Note ③ on page 29 for special reserved values
Set Local Upstream M: 4:1601
in the Upstream Zone.
4:0133 P: Byte 2 (Hi) Byte 3 (Lo)
Set Local Downstream M: 4:1602
in the Downstream Zone.
4:0212 P: Byte 4 (Hi) Byte 5 (Lo)
Set Local Downstream M: 4:1603
in the Downstream Zone.
4:0213 P: Byte 6 (Hi) Byte 7 (Lo)
Bitwise Values
bit 0 = Set/Clear Accumulation Mode for Local Zone
bit 8 = Accumulate adjacent upstream zone
bit 9 = Set Arrival Confirmation for adjacent downstream zone
Accumulation Control M: 4:1604
bit 10 = Jog zone in default direction
for Local Upstream Zone E: O.Data[4]
bit 11 = Jog zone in opposite of default direction
4:0104 P: Byte 8 (Hi) Byte 9 (Lo)
bit 12 = Wake up Local Zone
All other bits reserved
See ZPA Mode Note ⑤ on page 29 for further details

Bitwise Values
bit 0 = Set/Clear Accumulation Mode for Local Zone
bit 8 = Accumulate adjacent upstream zone
Accumulation Control bit 9 = Set Arrival Confirmation for adjacent downstream zone
M: 4:1605
for Local Downstream bit 10 = Jog zone in default direction
E: O.Data[5]
Zone bit 11 = Jog zone in opposite of default direction
4:0184 bit 12 = Wake up Local Zone
All other bits reserved
See ZPA Mode Note ⑤ on page 29 for further details

M: 4:1606 Value in % PWM
Set Left MDR Speed
E: O.Data[6] Range: 0 to 1000
4:0040
P: Byte 12 (Hi) Byte 13 (Lo) Example: 400 = 40%
M: 4:1607 0 = Remain at last non zero value entered
Set Right MDR Speed
E: O.Data[7]
4:0064 See ZPA Mode Note ④ on page 29 for further details


Description
Release and Accumulate When bit 0 of Accumulation Control for Local Upstream Zone is set:
M: 4:1608 Changing the value in this register will cause the Carton accumulated in this
on Next Arrival for Local
E: O.Data[8]
Upstream Zone zone to release and the zone will be armed to automatically accumulate the
4:0105 next Carton that arrives
Release and Accumulate When bit 0 of Accumulation Control for Local Downstream Zone is set:
M: 4:1609
on Next Arrival for Local Changing the value in this register will cause the Carton accumulated in this
E: O.Data[9]
Downstream Zone zone to release and the zone will be armed to automatically accumulate the
4:0185 next Carton that arrives
Only used when local module is accepting loads from Non-ConveyLinx controlled
conveyor:
Set Status for Upstream M: 4:1610
Induct E: O.Data[10] Set value to 4 to cause the local upstream zone to run to accept the Carton
4:0134 P: Byte 20 (Hi) Byte 21 (Lo) being delivered by the non-ConveyLinx controlled conveyor. Set value to 1 to
cause the local upstream zone to accept the tracking data written in Set Induct
Tracking Word 1 / Word 2
Only used when local module is discharging loads to Non-ConveyLinx controlled
Set Status for M: 4:1611 conveyor:
Downstream Discharge E: O.Data[11] • Set value to 5 to cause the local downstream zone to accumulate and
4:0232 P: Byte 22 (Hi) Byte 23 (Lo) hold any Carton that arrives.
• Set value to 1 to allow the local downstream zone to release the Carton
Set Induct Tracking
M: 4:1612 conveyor:
Forward Direction Word
E: O.Data[12] Set value for 16 bit integer tracking word #1 for Carton leaving non-ConveyLinx
1
P: Byte 24 (Hi) Byte 25 (Lo) controlled conveyor that is in transit to arrive on the local upstream zone
4:0139
when conveyor is running in default or “forward” direction.
Set Induct Tracking
M: 4:1613 conveyor:
2
4:0140
when conveyor is running in default or “forward” direction.
Set Induct Tracking
M: 4:1614 conveyor:
Reverse Direction Word
1
4:0237
when conveyor is running in opposite of default or “reverse” direction.
Set Induct Tracking
M: 4:1615 conveyor:
2
4:0238
when conveyor is running in opposite of default or “reverse” direction.
Logical 0 or 1
M: 4:1616 0 = Stop Reset
Clear Motor Error
E: O.Data[16] 1 = Send Reset
4:0022
See ZPA Mode Note ⑥ on page 30 for further details
Bitwise Value – “1” Energizes Output
M: 4:1617 bit 1 = Left Control Port
Set Control Port Outputs
E: O.Data[17] bit 3 = Right Control Port
4:0063
See ZPA Mode Note ⑦ on page 30 for further details


Description
M: 4:1618
Reserved E: O.Data[18]
Integer Value
0 = No Command
M: 4:1619 1 = Command local module’s Stop Group to go to Stopped State
ConveyStop Command
E: O.Data[19] 2 = Command local module’s Stop Group to Clear Stopped State
4:0020
Refer to Insight Automation publication ERSC-1800 ConveyStop User’s Guide for
details on using ConveyStop.
Use when PLC has detected a local Upstream jam in Module Status Word #1 Bit
Clear Sensor Jam
M: 4:1620 5:
Command for Local
E: O.Data[20] PLC creates transition from 0 to 1 to send command to local upstream
Upstream Zone
P: Byte 40 (Hi) Byte 41 (Lo) zone to clear the jam condition.
4:0109
See ZPA Mode Note ⑧ on page 31
Use when PLC has detected a local Downstream jam in Module Status Word #2
Clear Sensor Jam
M: 4:1621 Bit 5:
Command for Local
E: O.Data[21] PLC creates transition from 0 to 1 to send command to local downstream
Downstream Zone
P: Byte 42 (Hi) Byte 43 (Lo) zone to clear the jam condition.
4:0189
See ZPA Mode Note ⑧ on page 31
Used to change direction of flow or accumulation mode for a contiguous group
Direction & of zones beginning with the local upstream / downstream zone
Accumulation Mode M: 4:1622
Control for Local E: O.Data[22] Value for Low Byte of Register
Upstream Zone P: Byte 44 (Hi) Byte 45 (Lo) 0 = Normal Function
4:0365 1 = Accumulate Zones
2 = Accumulate Zones
3 = Change Accumulation Release mode
4 = Return Release Mode to Configured Default
10 = Set Direction to Configured Default Direction (Forward)
Direction & 11 = Set Direction to opposite of Configured Direction (Reverse)
Accumulation Mode M: 4:1623
Control for Local E: O.Data[23] Value for High Byte of Register
Upstream Zone P: Byte 46 (Hi) Byte 47 (Lo) Number of ZONES beginning with the local Upstream / Downstream Zone for
4:0375 which the Low Byte value is applied – from 1 to 220. If ALL ZONES in the
subnet need to be controlled then leave the High Byte = “0”.
ONLY AVAILABLE for FIRMWARE 4.25 AND HIGHER
Used to dynamically modify a ConveyMerge configuration already established

with EasyRoll.
Bitwise values:
Bit 15: set to enable PLC modification
Bit 4: set to disable release from Center line
Bit 5: set to disable release from Left line
M: 4:1624
ConveyMerge Interface Bit 6: set to disable release from Right line
E: O.Data[24]
4:0387 Bits 0 thru 3 are interpreted as a numerical value to change the release priority:
Value:
0 = First come, first served release
1 = Center line has priority
2 = Left line has priority
3 = Right line has priority
Please refer to publication ERSC-1005 User’s Guide Supplement for ConveyMerge

for details on configuring merging sections with EasyRoll software.

ZPA MODE NOTE ③

Because the ERSC is connected as I/O, the PLC inherently is always trying to update the Output image on (at least)
RPI intervals. In order to prevent the PLC from inadvertently overwriting the “real” tracking data registers; the
Assembly Output implementation utilizes the holding register locations shown and automatically updates the
“real” tracking registers with this new data only upon release of the Carton from the zone. Included in this
automatic functionality are two special reserved values that can be used for convenience:
• Set both tracking registers shown to 0: This will instruct the ERSC to not modify the existing “real”
tracking data and allow it to continue downstream “as-is” when the Carton is released.
• Set both tracking registers shown to 0xFFFF: This will instruct the ERSC to clear the “real” tracking data
and when the Carton is released, the “real” tracking data will be “0” in both registers.
Both word 1 and word 2 of the tracking data in question must have 0xFFFF written to it in
order to signal the ERSC to clear the tracking data. If only one word has 0xFFFF written to
it and the other does not, the value of 0xFFFF will be the new tracking data for that word.
ZPA MODE NOTE ④

Leaving these registers at “0” will instruct the ERSC to use its configured speed. Any non-zero value will instruct
the ERSC to use this non zero value as the speed reference. The speed will stay at this reference until this register
is changed to a new non zero value or set to “0”. When this register is set to “0”, the ERSC continue to use the last
non zero value it was given. Setting this value to “0” will not cause the motor to run at “0” speed.
ZPA MODE NOTE ⑤

Beginning with ConveyLinx firmware 3.45 and later; the function of this register has been
expanded to include separate bit-wise functionality. Previous to firmware 3.45, only bit 0
function was available.
B IT 8 – A CCUMULATE A DJACENT U PSTREAM Z ONE

Setting this bit will cause the next upstream zone of the local module to accumulate. This next upstream zone can
be either on the local module or the downstream zone of the adjacent upstream module.
B IT 9 – S ET A RRIVAL C ONFIRMATION FOR D OWNSTREAM Z ONE

By default for ZPA operation, ConveyLinx requires a confirmation from the downstream zone when a Carton is
discharged. Without this confirmation, the releasing zone will detect a jam condition. This bit is used in
applications where the Carton is removed from the conveyor (either manually or say by a PLC controlled external
mechanism such as a pusher or diverter) and the PLC needs to “confirm” the removal of the Carton in order to
satisfy the ZPA confirmation logic.

B ITS 10 & 11 – J OG C ONTROLS

These bits can be used by the PLC to jog the local zone for specialized applications when local movement of the
Carton on a zone is required. An example would be once a Carton has arrived in the local zone, the PLC
determines that the Carton needs to be repositioned or perhaps squared up against a PLC controlled pop-up stop.
Jog control bits DO NOT over-ride ZPA logic control and should be used with caution!
Improper usage of jog controls can produce unexpected results and/or damage to product
and equipment.
B IT 12 – W AKE UP L OCAL Z ONE

Setting this bit will cause the local zone to “wake up” and run to accept a carton the same as if it’s upstream ERSC
had written a status value of “4”. This function would be useful for a merge onto a main line of ZPA conveyor.
Bit 12 – Wake up Local Zone functionality available in ERSC firmware versions 4.1 and
higher.
ZPA MODE NOTE ⑥

Errors deemed “fatal” for the ERSC (motor short circuit and Hall Effect sensor fault) require either removal of
power to reset or remote reset by PLC. Setting bit 0 of this register to 1 will initiate this remote error reset from
the PLC to the local ERSC. Setting this bit will reset a fatal error on either (or both) the left or right MDR.
External controller must continuously set bit 0 = 1 in the Clear Motor Error register for at
least 500 msec for the ERSC to recognize the reset command.
ZPA MODE NOTE ⑦

By default in ZPA mode, the PLC does not have control of the local connected module’s Control Port output signals.
The default function of the Control Port output signals is to be energized when the Control Port’s corresponding
zone is occupied.
In certain applications, it may be desired to have the PLC actuate a device along the conveyor (i.e. illuminate a light
or energize a solenoid coil, etc.). With the ConveyLinx network this can be done without installing a separate PLC
I/O system to do this. Using EasyRoll software, one or both Control Ports can have their function switched from
internal ZPA logic control to be controlled by the PLC. See EasyRoll software Advanced Screen|Control Ports|
Checkboxes for Enable PLC Controls.
Please note that the checkboxes in EasyRoll for selecting PLC control of Control Ports is
based upon upstream or downstream configuration of the ERSC determined during Auto-
Configuration and NOT by “left” or “right” Control Port designation.

Please refer to the ConveyLinx User’s Guide for electrical connection details before using
PLC control for Control Port outputs.
ZPA MODE NOTE ⑧

Refer to ConveyLinx User’s Guide and/or EasyRoll software on screen help for description of various jam
conditions. These registers are applicable only to a Sensor Jam condition. By default in ZPA mode, the ERSC will
attempt 3 times to automatically clear a sensor jam and if the sensor is still blocked, the ERSC will stop the zone.
rd
To reset this condition the Carton must be manually removed after the 3 attempt and the sensor cleared before
the zone will return to normal operation.
These registers allow the PLC to remotely attempt another auto-clear cycle in an attempt to clear the jam
condition. Please note that this function requires the PLC to make a transition from 0 to 1 in the register to initiate
another auto-clear cycle. Holding the value to 1 will not cause the retry to continue indefinitely. Each attempt
requires a new transition from 0 to 1

ZPA MODE EXAMPLES

EXAMPLE 1 – BASIC ACCUMULATE AND RELEASE WITH TRACKING DATA
Figure 3 shows a typical arrangement of an upstream or downstream zone on an ERSC in ZPA mode that is not the
most upstream or most downstream zone in a given network. This example will show how to cause a Carton to
accumulate, how to detect a Carton has arrived, how to write tracking data, and finally how to release the Carton.
FIGURE 3 - BASIC ACCUMULATE / RELEASE CONTROL EXAMPLE
For this example, the PLC must establish ZPA Mode Assembly Input/Output connections to ERSC B as shown in
Figure 3.
U PSTREAM Z ONE E XAMPLE

First, let’s assume we want to accumulate any Carton that arrives on the upstream zone of ERSC B. With the PLC:
1. Set bit 0 in Accumulation Control for Local Upstream Zone register to instruct this zone to accumulate any
Carton that arrives.
2. Monitor Arrival Count Local Upstream Zone and Departure Count Local Upstream Zone registers. On the
leading edge when these two values become not equal, the PLC knows there is a new arrival. Note that as
long as a Carton is physically occupying the upstream zone, these two values will not be equal.
3. Upon a successful arrival of a Carton in the upstream zone, then tracking data in Current Upstream Zone
Tracking Word 1 and Current Upstream Zone Tracking Word 2 will be valid for the newly arrived Carton.
4. The PLC may then decide that this tracking data is to be updated. The PLC can then write new tracking
data to registers Set Local Upstream Zone Tracking Word 1 and Set Local Upstream Zone Tracking Word 2.
5. When the PLC is ready to release the Carton in the upstream zone, it should read the value in the Current
Release Count for Upstream Zone register, add 1 to this value, and then write this new value to Release
and Accumulate on Next Arrival for Local Upstream Zone register. When ERSC B sees this new value in

this register, it will release the Carton in the upstream zone and automatically accumulate the next new
Carton that arrives. Please note that if the downstream conditions from ERSC B are full when this new
value is written, ERSC B will remember that it was instructed to release and will release the Carton when
downstream conditions become clear without any further signal from the PLC.
6. The PLC can detect when the Carton has departed the sensor on ERSC B upstream zone by examining the
values in Arrival Count Local Upstream Zone and Departure Count Local Upstream Zone registers. On the
leading edge of when these two values are equal, the PLC will know that the Carton has departed the
zone sensor in ERSC B upstream zone.
If the PLC wants to cancel the accumulation control for ERSC B upstream zone:
PLC can reset bit 0 in Accumulation Control for Local Upstream Zone register. This will signal ERSC B to release
any Carton accumulated and not accumulate the next Carton that arrives at ERSC B upstream zone.
Please note that if any new tracking data has been written to Set Local Upstream Zone
Tracking Word 1 and/or Set Local Upstream Zone Tracking Word 2 and accumulation
control is then canceled by resetting bit 0, this data will NOT be assigned to the Carton
The ONLY way to pass tracking data to a Carton is by
when it is released.
following Step 5 above.

D OWNSTREAM Z ONE E XAMPLE

Downstream Zone example is identical to Upstream Zone example shown above except the registers used are
different. It is repeated below to explicitly show which registers to use.
First, let’s assume we want to accumulate any Carton that arrives on the downstream zone of ERSC B. With the
PLC:
1. Set bit 0 in Accumulation Control for Local Downstream Zone register to instruct this zone to accumulate
any Carton that arrives.
2. Monitor Arrival Count Local Downstream Zone and Departure Count Local Downstream Zone registers. On
the leading edge when these two values become not equal, the PLC knows there is a new arrival. Note
that as long as a Carton is physically occupying the upstream zone, these two values will not be equal.
3. Upon a successful arrival of a Carton in the upstream zone, then tracking data in Current Downstream
Zone Tracking Word 1 and Current Downstream Zone Tracking Word 2 will be valid for the newly arrived
Carton.
4. The PLC may then decide that this tracking data is to be updated. The PLC can then write new tracking
data to registers Set Local Downstream Zone Tracking Word 1 and Set Local Downstream Zone Tracking
Word 2.
5. When the PLC is ready to release the Carton in the upstream zone, it should read the value in the Current
Release Count for Downstream Zone register, add 1 to this value, and then write this new value to Release
and Accumulate on Next Arrival for Local Downstream Zone register. When ERSC B sees this new value in
this register, it will release the Carton in the downstream zone and automatically accumulate the next
new Carton that arrives. Please note that if the downstream conditions from ERSC B are full when this
new value is written, ERSC B will remember that it was instructed to release and will release the Carton
when downstream conditions become clear without any further signal from the PLC.
6. The PLC can detect when the Carton has departed the sensor on ERSC B upstream zone by examining the
values in Arrival Count Local Downstream Zone and Departure Count Local Downstream Zone registers.
On the leading edge of when these two values are equal, the PLC will know that the Carton has departed
the zone sensor in ERSC B downstream zone.

If the PLC wants to cancel the accumulation control for Module B downstream zone:
PLC can reset bit 0 in Accumulation Control for Local Downstream Zone register. This will signal Module B to
release any Carton accumulated and not accumulate the next Carton that arrives at Module B downstream
zone.
Please note that if any new tracking data has been written to Set Local Downstream Zone
Tracking Word 1 and/or Set Local Downstream Zone Tracking Word 2 and accumulation
control is then canceled, this data will NOT be assigned to the Carton when it is released.
The ONLY way to pass tracking data to a Carton is by following Step 5
above.

EXAMPLE 2 – BASIC BAR CODE READER

This example shows how to easily set up the conveyor control to easily singulate cartons through a bar code
scanning region. Figure 4 shows a conveyor and ERSC configuration for a simple barcode scanning example.
FIGURE 4 - SIMPLE BARCODE SCANNER APPLICATION
In this example, ERSC B must be logically configured as a single zone. This can be either a single long zone with one
MDR and one sensor, or a single long zone with 2 MDRs and one sensor. Please refer to the ConveyLinx User’s
Guide for details on single zone operation.
Also for this example to work properly; the discharging zone of ERSC A and the single zone of ERSC B must be in the
default singluation release mode (not Train mode). ERSC A must also not have its Arrival Jam disabled from
EasyRoll main screen. Please refer to the ConveyLinx User’s Guide and/or EasyRoll software on screen help for
details on these items.
Because of built-in ZPA functionality, when a Carton leaves ERSC A discharge zone, ERSC A waits until it receives
confirmation from ERSC B that the Carton arrived. If a new Carton arrives at ERSC A, it will accumulate until this
arrival confirmation occurs. Because ERSC B is a single long zone, the space for what would have been the
upstream zone for ERSC B (if it was configured as two zones) will now essentially be left clear when a Carton is
accumulated on ERSC B. This is the area where the bar code scanner is located. In this configuration, any new
arrival at ERSC B will be assured to be the Carton associated with the last scan from the bar code reader. For this
example, the PLC must establish a connection with ERSC B and then simply follow the zone control as described for
basic accumulate and release.

EXAMPLE 3 – UPSTREAM ACCEPT INTERFACE

This example describes how to use a PLC to control the “wake-up” and passing of tracking data to the most
upstream zone of a ConveyLinx controlled conveyor. Figure 5 shows a typical example configuration.
FIGURE 5 - UPSTREAM ACCEPT INTERLOCK EXAMPLE
For this example, the PLC must establish a connection with ERSC A. When PLC is ready to transfer a Carton from
the PLC controlled conveyor to the Upstream Zone of the MDR Conveyor, the PLC logic must:
1. Write a “4” into Set Status for Upstream Induct register. This will cause the upstream zone of ERSC A to
run to accept Carton.
2. When Carton clears PE-1, write tracking data to Set Induct Tracking Forward Direction Word 1 / 2.
3. When Carton clears PE-1, write a “1” to Set Status for Upstream Induct register. When ERSC A sees this
register change to “1”, it knows that the tracking data written to Set Induct Tracking Forward Word 1 / 2 is
valid and when the Carton reaches the sensor in its upstream zone, the tracking data will be correctly
inducted.
ERSC A must see the Set Status for Upstream Induct register change from 4 to 1 in order
to recognize the tracking data written to Set Induct Tracking Forward Word registers. If
using the clearing of PE-1 to initiate the write of “1” the Set Status for Upstream Induct
register in the PLC logic; the physical length of the Carton must be less that the distance
between PE-1 and ERSC A’s upstream zone sensor because ERSC A inducts the tracking
data upon the Carton arriving at its upstream sensor and if Set Status for Upstream Induct
has not changed from 4 to 1, the tracking data will not be valid.

If a value of “4” is in the Set Status for Upstream Induct register at the same time the
Carton reaches the local upstream zone’s sensor; the local upstream zone will assume the
Carton is physically longer than one zone and will invoke it’s on board Flex Zone logic and
behave accordingly. Please refer to the ConveyLinx User’s Guide for description of Flex
Zone operation. To reliably transfer tracking data and insure single Carton induction to
the local upstream zone, the PLC programmer must insure proper use of the Set Status for
Upstream Induct register.

EXAMPLE 4 – DOWNSTREAM DISCHARGE INTERFACE

This example shows how to control the discharge of a Carton from the most downstream zone of a ConveyLinx
controlled conveyor. This example also shows how to properly accept the tracking data from the ConveyLinx
module. Figure 6 shows a typical example.
FIGURE 6 - DOWNSTREAM DISCHARGE INTERFACE EXAMPLE
For this example, the PLC must establish a connection with ERSC X.
1. To hold any Carton that arrives at ERSC X downstream zone, the PLC writes a “5” to Set Status for
Downstream Discharge register. This tells ERSC X that downstream conditions are “full and stopped” so it
will not try to release any loads downstream.
2. When the PLC controlled conveyor is ready to accept a Carton from the MDR downstream zone, it writes
a “1” to Set Status for Downstream Discharge register. This tells ERSC X that downstream conditions are
clear and if it has a Carton on its downstream zone, it will run to release it downstream.
3. When the Carton clears the local sensor in ERSC X Downstream Zone, the tracking data for that Carton will
be populated in Get Tracking Forward Direction Word 1/2 registers.
4. When Carton arrives at PE-2, the PLC writes a “5” to Set Status for Downstream Discharge register. This
tells ERSC X that the Carton successfully transferred. If this is not done, then Modle X will produce an
Arrival jam condition.
Optional Step:
If the application is such that the PLC would like to inhibit a new Carton from entering ERSC X downstream zone for
whatever reason, there is a way to accumulate the next upstream zone to the ERSC X downstream zone. The PLC
can set bit 8 in the Accumulation Control for Local Downstream Zone and this will cause the adjacent upstream
zone to accumulate (whether this zone is on ERSC X or next adjacent upstream ConveyLinx ERSC). Please note that
if ERSC X is configured as a single zone, then you must set bit 8 in the Accumulation Control for Local Upstream
Zone register.

To return the accumulated upstream zone to normal operation; the PLC simply resets bit 8 in this register
Functionality for Accumulate Upstream using bit 8 is only available in ConveyLinx

firmware versions 3.45 and higher.

EXAMPLE 5 – SIMPLE DIVERT EXAMPLE

This example shows how to use a PLC to control a simple divert mechanism to divert a Carton from a ZPA zone and
capture its tracking. This example also illustrates how to use the set downstream arrival function with the PLC to
keep the discharging ERSC from generating a jam condition when the Carton is moved from the ZPA zone to the
divert lane. Figure 7 shows the layout for this example.
FIGURE 7 - SIMPLE DIVERT EXAMPLE
This example assumes that the tracking data arriving from each new Carton arrival at ERSC B Upstream Zone
contains a value that will indicate to the PLC that a Carton does or does not need to divert. It is not required that
the PLC use Carton tracking data be used to determine when to divert a Carton.
1. Set bit 0 in Accumulation Control for Local Upstream Zone register to instruct this zone to accumulate any
Carton that arrives.
2. Monitor Arrival Count Local Upstream Zone and Departure Count Local Upstream Zone registers. On the
leading edge when these two values become not equal, the PLC knows there is a new arrival. Note that as
long as a Carton is physically occupying the upstream zone, these two values will not be equal.

3. Upon a successful arrival of a Carton in the upstream zone, then tracking data in Current Upstream Zone
Tracking Word 1 and Current Upstream Zone Tracking Word 2) will be valid for the newly arrived Carton.
Assuming the PLC determines that the newly arrived Carton needs to divert:
• Set bit 8 of Accumulation Control for Local Upstream Zone register. This will keep ERSC A from releasing a
Carton to ERSC B while the divert operation is in progress.
• PLC will then initiate it’s divert mechanism.
• When carton reaches PE-1, the PLC will then set bit 9 of the Accumulation Control for Local Upstream
Zone register. This will tell ERSC B that the carton “successfully arrived at its downstream position”.
• Once carton has cleared PE-1, then the PLC should clear bit 9 of the Accumulation Control for Local
Upstream Zone register.
• PLC then can clear bit 8 of the Accumulation Control for Local Upstream Zone register to instruct ERSC A
that it is OK to allow the next carton to enter ERSC B’s upstream zone.
Please note that in this example, the setting of bit 9 in the Accumulation Control for Local
Upstream Zone register can simply be written in the PLC logic based upon block and clear
of PE-1. Care must be taken so that ERSC B’s Upstream zone’s sensor is not blocked at the
same time this bit 9 is set. If this zone’s sensor is blocked at the same time bit 9 is set;
ERSC B will assume that the carton is more than one zone in length and will automatically
initiate Flex Zone operation which may produce unexpected results in carton flow. Please
refer to User’s Guide for complete description of Flex Zone function and how to disable if
needed.
If PLC determines that the Carton needs to go straight and not divert:
The PLC can simply modify Carton’s tracking data if desired and release the Carton as described in section Example
1 – Basic Accumulate and Release with Tracking Data on page 32.

EXAMPLE 6 – MERGE ONTO ZPA MAIN LINE

This example shows how to perform a simple merge with only a single ERSC connection to the PLC. Figure 8
depicts the conveyor layout and ERSC configuration for this example. In the example, ERSC B could be eliminated
by simply making the shaded merging area be 2 extended zones on ERSC C. This example shows how easy it is to
put pieces together with EasyRoll and using the Extensions functionality. Please refer to ConveyLinx User’s Guide
and EasyRoll software on screen directions for more details on creating extension zones.
FIGURE 8 - MERGE ONTO ZPA MAIN LINE EXAMPLE
In this example the PLC only needs to connect to ERSC C and from this connection, the PLC can monitor conditions
on ERSC A as well as “wake-up” ERSC C / ERSC B zone to accept a carton from the merging curve section.
1. With no PLC intervention, as long as cartons arrive into ERSC A they will be conveyed to ERSC C/B and
onto ERSC D in normal ZPA fashion.
2. To verify that ERSC C (and by extension ERSC B) is ready to accept a carton from the merge curve; the PLC
needs to know that ERSC C’s zone is clear and stopped by examining Local Status Upstream Zone register.
When this register equals 1, the zone is clear and stopped.
3. When the PLC needs to convey a carton from the merging curve, the PLC needs to set bit 8 in
Accumulation Control for Local Upstream Zone register to accumulate the adjacent upstream zone, in this
example setting bit 8 will cause ERSC A downstream zone to accumulate any carton that arrives.

4. When the PLC is ready to release a carton from the merging curve conveyor, the PLC sets bit 12 in the
Accumulation Control for Local Upstream Zone register to wake up the ERSC C zone (along with ERSC B’s
zones because ERSC B is an extension of ERSC C).
5. When the PLC sees the Local Status Upstream Zone register change to a value of 4 or 5, the PLC knows
that the carton made it to ERSC C’s zone sensor and must then reset bit 12 in the Accumulation Control for
Local Upstream Zone register. Either of these values will indicate a successful arrival at ERSC C.
6. Once bit 12 of the Accumulation Control for Local Upstream Zone register has been reset, the PLC can
reset bit 8 of the same register to indicate to ERSC A that it is OK to continue normal ZPA function.

REDUCED SIZE ZPA MODE ASSEMBLIES

For some PLC controllers, the data size footprint required for a given assembly can be a limiting factor on how
many devices can connect to a given controller. ConveyLinx includes input/output assemblies with fewer registers
that contain basic functions in applications where the full functionality of the Standard ZPA Mode Assemblies is not
required. The Reduced Size Assemblies provide basic accumulation and release control along with module
diagnostic data while removing the interfaces for reading/writing tracking data.
REDUCED SIZE ZPA MODE ASSEMBLY INPUTS

Please note that the functions provided by this assembly are already included and described in detail in section
ZPA Mode Assembly Inputs for PLC on page 22.
ERSC Assembled
Assembled EIP Assembled Profinet
Internal Register Name Modbus Address
Address for PLC Address for PLC
Address for PLC
4:0105 Local Status Upstream Zone I.Data[0] 4:2900 Byte 0 (Hi) Byte 1 (Lo)
4:0106 Local Status Downstream Zone I.Data[1] 4:2901 Byte 2 (Hi) Byte 3 (Lo)
4:0107 Arrival Count Local Upstream Zone I.Data[2] 4:2902 Byte 4 (Hi) Byte 5 (Lo)
4:0116 Departure Count Local Upstream Zone I.Data[3] 4:2903 Byte 6 (Hi) Byte 7 (Lo)
4:0185 Arrival Count Local Downstream Zone I.Data[4] 4:2904 Byte 8 (Hi) Byte 9 (Lo)
4:0186 Departure Count Local Downstream Zone I.Data[5] 4:2905 Byte 10 (Hi) Byte 11 (Lo)
4:0187 Module Status Word 1 I.Data[6] 4:2906 Byte 12 (Hi) Byte 13 (Lo)
4:0196 Module Status Word 2 I.Data[7] 4:2907 Byte 14 (Hi) Byte 15 (Lo)
4:0035 Current Release Count for Upstream Zone I.Data[8] 4:2908 Byte 16 (Hi) Byte 17 (Lo)
4:0088 Current Release Count for Downstream Zone I.Data[9] 4:2909 Byte 18 (Hi) Byte 19 (Lo)
4:0089 Sensor & Control Port Inputs I.Data[10] 4:2910 Byte 20 (Hi) Byte 21 (Lo)
Reserved I.Data[11] 4:2911 Byte 22 (Hi) Byte 23 (Lo)

REDUCED SIZE ZPA MODE ASSEMBLY OUTPUTS

Please note that the functions provided by this assembly are already included and described in detail in section
ZPA Mode Assembly Outputs for PLC on page 26.
ERSC EIP Modbus

Profinet
Internal Register Name Address Address
Address for PLC
Address for PLC for PLC
4:0104 Accumulation Control for Local Upstream Zone O.Data[0] 4:3000 Byte 0 (Hi) Byte 1 (Lo)
4:0184 Accumulation Control for Local Downstream Zone O.Data[1] 4:3001 Byte 2 (Hi) Byte 3 (Lo)
4:0040 Set Left MDR Speed O.Data[2] 4:3002 Byte 4 (Hi) Byte 5 (Lo)
4:0064 Set Right MDR Speed O.Data[3] 4:3003 Byte 6 (Hi) Byte 7 (Lo)
4:0105 Release and Accumulate on Next Arrival for Local Upstream Zone O.Data[4] 4:3004 Byte 8 (Hi) Byte 9 (Lo)
4:0185 Release and Accumulate on Next Arrival for Local Downstream Zone O.Data[5] 4:3005 Byte 10 (Hi) Byte 11 (Lo)
4:0134 Set Status for Upstream Induct O.Data[6] 4:3006 Byte 12 (Hi) Byte 13 (Lo)
4:0232 Set Status for Downstream Discharge O.Data[7] 4:3007 Byte 14 (Hi) Byte 15 (Lo)
4:0022 Clear Motor Error O.Data[8] 4:3008 Byte 16 (Hi) Byte 17 (Lo)
4:0063 Set Control Port Outputs O.Data[9] 4:3009 Byte 18 (Hi) Byte 19 (Lo)
Reserved O.Data[10] 4:3010 Byte 20 (Hi) Byte 21 (Lo)
4:0109 Clear Sensor Jam Command for Local Upstream Zone O.Data[11] 4:3011 Byte 22 (Hi) Byte 23 (Lo)
4:0189 Clear Sensor Jam Command for Local Downstream Zone O.Data[12] 4:3012 Byte 24 (Hi) Byte 25 (Lo)
4:0365 Direction & Accumulation Mode Control for Local Upstream Zone O.Data[13] 4:3013 Byte 26(Hi) Byte 27 (Lo)
4:0375 Direction & Accumulation Mode Control for Local Upstream Zone O.Data[14] 4:3014 Byte 28 (Hi) Byte 29 (Lo)

PLC Controller with PLC I/O Mode 47
PLC CONTROLLER WITH PLC I/O MODE

When an ERSC is in PLC I/O mode, all automatic functions of detecting loads and running motors are suspended by
the local ERSC on-board logic and the external controller must explicitly read inputs and write data output to cause
motors to run. The following items are available for external controller when ERSC is in PLC I/O Mode:
• Status of all available digital inputs on Sensor and Control ports (8 total inputs)
• Module voltage reading
• Left and Right motor status of frequency, current, and calculated temperature
• Left and Right motor diagnostic error status word
• Control of Control Port digital outputs
• Ability to independently run both Left and Right motors
• Ability to set speed, acceleration, deceleration, PI Mode, and Braking method for Left and Right motors
• Ability to configure one or both motor ports to digital output mode
• Ability to remotely clear fatal motor error condition
• Ability to instruct module to E-Stop motor outputs
Refer to ConveyLinx User’s Guide (publication ERSC-1000) for connection details for
Sensor and Control Port input and output signals.
When an ERSC is placed in PLC I/O mode; it suspends all of its internal ZPA logic control. Any sensors or motors
connected to the ERSC require explicit interaction with an external controller. The external controller will have
typical Ethernet-based remote I/O performance from an ERSC when in PLC I/O mode.

SETTING PLC I/O MODE IN EASYROLL

Individual ERSC’s must be placed into PLC I/O Mode from the EasyRoll software tool. This is done by invoking the
Advanced Dialog and using the Connections tab.
Configuring ERSC for PLC I/O Mode
From the main screen, first enter the correct Subnet into the “Network IP” boxes and the correct Node you want to
connect. Invoke the ConveyLinx Advanced Dialog and select the Connections tab.
Note that the Node is being viewed is in the center and it is greyed out. Select the “PLC I/O Controlled” checkbox.
With this checked the “Clear Connections” checkbox becomes enabled. Check or Uncheck the “Clear
Connections” checkbox depending upon your application. Click “Apply” to initiate the change. The ERSC will
restart and this may take several seconds to complete.

OPTIONAL “CLEAR CONNECTIONS” CHOICE
Refer to Appendix B – ConveyLinx Connections for further details on ConveyLinx

Connections.
The decision to “Clear Connections” is based upon the application. When a string of ERSC modules are Auto-
Configured, each successive ERSC in the string establishes a logical upstream / downstream connection with its
neighbor ERSC’s. These connections provide the basis for the logical flow of inter-module status data for ZPA
functionality. However, if a single ERSC node within a string of ZPA configured nodes needs to be utilized in PLC
I/O mode, these logical connections can remain in place and be used to PLC programmer’s advantage.
By NOT clearing the connections, the ERSC in PLC I/O will maintain its inter-module data exchange. This could be
advantageous for applications where you want to control a specialized conveyor section such as a right angle
transfer or merge conveyor with an ERSC in PLC I/O mode. For example, if the PLC I/O mode ERSC is being either
fed or feeds conveyors controlled by ERSC’s in standard ZPA mode, these ERSC’s will populate PLC I/O configured
module’s registers with their respective status data. Likewise, the PLC can manipulate the PLC I/O configured
module’s zone status registers and these registers will automatically be written to the adjacent ERSC’s by virtue of
these already established connections without requiring the PLC to explicitly perform the messaging.
If you choose the option to “Clear Connections”, this automatic data transfer of status is inhibited. This means that
for an ERSC module in PLC I/O mode whose connections have been cleared; its status registers are not
automatically written to its adjacent neighbors. Clearing the connections could be advantageous when utilizing
several ERSC’s in a row configured as PLC I/O where having this additional inter-module communication is not
required and would only add to unnecessary communication bandwidth usage.
IMPORTANT NOTE: Once a given ERSC has been placed in PLC

I/O mode, the ONLY way to return it to ZPA mode is to perform
an Auto-Configuration procedure or Restore from a backup file
with EasyRoll. There is no “undo” or “reset” function for this
action.

CONFIGURING ACTION FOR L OSS OF COMMUNICATION

When changing the mode of a given ERSC to PLC I/O mode in EastRoll, you are given the option to select the
behavior of the ERSC’s outputs upon loss of communications with the PLC.
Configuring Communication Loss Action for ERSC in PLC I/O Mode
Select “Don’t Change” if you want module’s logical outputs and MDR’s to remain in the state they were in at the
time of the communication loss
Select “All OFF” to instruct the ERSC to turn off all logical outputs and stop all MDR’s at the time of communication
loss.
Upon re-establishing communications with the PLC, the ERSC will automatically resume having its outputs and
MDR’s controlled by PLC command.

PLCI/O MODE ASSEMBLY INPUTS

This chart shows the data sent by an ERSC in PLC I/O mode to the PLC when connected. All registers in the module
are 16-bit integer data type.
Register Name /
Address Data Description
Module Address
bit 00 = Reserved
bit 01 = Reserved
bit 02 = Reserved
bit 03 = Reserved
bit 04 = Reserved
bit 05 = Stop active on other module in Stop Group
bit 06 = Stop active due to lost communication connection
bit 07 = Stop active due to lost PLC connection
M: 4:1700 bit 08 = Stop active on local module’s Left Control Port
ConveyStop Status
E: I.Data[0] bit 09 = Stop active on local module’s Right Control Port
4:0019
P: Byte 0 (Hi) Byte 1 (Lo) bit 10 = Stop active due to Stop Command from PLC
bit 11 = Reserved
bit 12 = Reserved
bit 13 = Reserved
bit 14 = Reserved
bit 15 = Reserved


Sensor & Control M: 4:1701 bit 04 = Left Sensor Port - Pin 4
Port Inputs E: I.Data[1] bit 05 = Left Control Port - Pin 4
4:0035 P: Byte 2 (Hi) Byte 3 (Lo) bit 06 = Right Sensor Port - Pin 4
bit 15 = 2 sec on / 2 sec off heartbeat
See PLC I/O Mode Note ④ on page 54

M: 4:1702
Sensor Detect bit 0 = Device is connected to Right Sensor Port
E: I.Data[2]
4:0036 bit 1 = Device is connected to Left Sensor Port
Value in mV of Module Power Supply

M: 4:1703
Module Voltage Range: 0 to 35000
E: I.Data[3]
4:0024 Example:23500 = 23.5 Volts
M: 4:1704 Integer Value in mA – Current that motor is currently drawing

Left Motor Current
E: I.Data[4] Example: 1900 = 1.9 Amps
4:0055
Integer Value in Hz – Current frequency that motor is currently running
M: 4:1705
Left Motor Frequency Example: 300 = 300 Hz
E: I.Data[5]
4:0056
See PLC I/O Mode Note ② on page 53

Register Name /
Module Address
High Byte / Low Byte Value of temperatures in °C
Left Motor M: 4:1706
High Byte = Calculated motor temperature
Temperature E: I.Data[6]
Low Byte = Temperature reading from on-board sensor
4:0057 P: Byte 12 (Hi) Byte 13 (Lo)
Bitwise Value – See PLC I/O Mode Note ③ on page 53

bit 00 = Motor Status bit 08 = Overheated
bit 01 = Motor Status bit 09 = Over Current
M: 4:1707 bit 02 = Port in Digital Mode bit 10 = Short Circuit
Left Motor Status
E: I.Data[7] bit 03 = Reserved bit 11 = Motor Not Connected
4:0058
P: Byte 14 (Hi) Byte 15 (Lo) bit 04 = Reserved bit 12 = Overloaded
bit 05 = Board Overheat bit 13 = Motor Stalled
bit 06 = Over-Voltage bit 14 = Hall Sensor Error
bit 07 = Low Voltage bit 15 = Motor Not Used
M: 4:1708
Right Motor Current Integer Value in mA – Current that motor is currently drawing
E: I.Data[8]
4:0079 Example: 1900 = 1.9 Amps
Integer Value in Hz – Current frequency that motor is currently running
M: 4:1709
Right Motor Frequency Example: 300 = 300 Hz
E: I.Data[9]
4:0080
See PLC I/O Mode Note ② on page 53
Right Motor M: 4:1710 High Byte / Low Byte Value of temperatures in °C
Temperature E: I.Data[10] High Byte = Calculated motor temperature
4:0081 P: Byte 20 (Hi) Byte 21 (Lo) Low Byte = Temperature reading from on-board sensor
Bitwise Value - See PLC I/O Mode Note ③ on page 53
bit 00 = Motor Status bit 08 = Overheated
bit 01 = Motor Status bit 09 = Over Current
M: 4:1711 bit 02 = Port in Digital Mode bit 10 = Short Circuit
Right Motor Status
E: I.Data[11] bit 03 = Reserved bit 11 = Motor Not Connected
4:0082
P: Byte 22 (Hi) Byte 23 (Lo) bit 04 = Reserved bit 12 = Overloaded
bit 05 = Reserved bit 13 = Motor Stalled
bit 06 = Over-Voltage bit 14 = Hall Sensor Error
bit 07 = Low Voltage bit 15 = Motor Not Used
Left Motor Port Digital M: 4:1712
I/O Status E: I.Data[12] Bitwise Value – Read Only
4:0060 P: Byte 24 (Hi) Byte 25 (Lo) bit 12 = Short Circuit Error on one or more outputs
bit 14 = Over Current – More than 1A detected on one or more outputs
Right Motor Port M: 4:1713
Digital I/O Status E: I.Data[13] See Appendix A - Motor Port as Digital I/O on page 69 for usage details
4:0084 P: Byte 26 (Hi) Byte 27 (Lo)
Integer Value of Low Byte
Upstream Module M: 4:1714 0x01 = Sensor clear and motor stopped
Status E: I.Data[14] 0x02 = Sensor clear, motor running, accepting from upstream
4:0134 P: Byte 28 (Hi) Byte 29 (Lo) 0x03 = Reserved
0x04 = Sensor blocked, motor running, discharging to downstream
0x05 = Sensor blocked and motor stopped
Downstream Module M: 4:1715 0x06 = ERSC Busy
Status E: I.Data[15]
4:0232 P: Byte 30 (Hi) Byte 31 (Lo)
See PLC I/O Mode Note ① on page 53 for details
Current Tracking Word Value = Tracking data word #1 (16 bit integer) for the Carton that has just
M: 4:1716 discharged from the ERSC Adjacent to this local ERSC module.
1 for Adjacent
E: I.Data[16]
Upstream Module
4:0139 See PLC I/O Mode Note ① on page 53 for Details

Register Name /
Module Address
Current Tracking Word Value = Tracking data word #2 (16 bit integer) for the Carton that has just
M: 4:1717
2 for Adjacent discharged from the ERSC Adjacent to this local ERSC module.
E: I.Data[17]
Upstream Module
P: Byte 34 (Hi) Byte 35 (Lo) See PLC I/O Mode Note ① on page 53 for Details
4:0140
M: 4:1718
Reserved E: I.Data[18]
Signed integer value that indicates the current position of the Left Motor in
Left Motor Servo M: 4:1719
relation to its “0” position
Position E: I.Data[19]
4:0062 P: Byte 38 (Hi) Byte 39 (Lo)
See section Servo Motor Control Example on page 61
Signed integer value that indicates the current position of the Right Motor in
Right Motor Servo M: 4:1720
relation to its “0” position
Position E: I.Data[20]
4:0086 P: Byte 40 (Hi) Byte 41 (Lo)
Bit 0: Servo Command Status
1 = Last Servo Run Command Complete
0 = Servo Command in Process
Left Motor Servo M: 4:1721 Bit 1: Servo Reset Status
Status E: I.Data[21] Echoes state of Left Motor Servo Command bit 0
4:0011 P: Byte 42 (Hi) Byte 43 (Lo) Bit 2: Servo Command Status
Echoes state of Left Motor Servo Command bit 1

Bit 0: Servo Command Status
1 = Last Servo Run Command Complete
0 = Servo Command in Process
Right Motor Servo M: 4:1722 Bit 1: Servo Reset Status
Status E: I.Data[22] Echoes state of Right Motor Servo Command bit 0
4:0016 P: Byte 44 (Hi) Byte 45 (Lo) Bit 2: Servo Command Status
Echoes state of Right Motor Servo Command bit 1
PLC I/O MODE NOTE ①

These registers only contain meaningful data if the ConveyLinx connections between upstream and/or
downstream ERSC’s are preserved when placing the local ERSC into PLC I/O mode from within EasyRoll. If
connections are cleared in EasyRoll, these registers will not contain any pertinent data and will not be updated by
adjacent ERSC’s. Refer to section Optional “Clear Connections” Choice on page 49 for further details.
PLC I/O MODE NOTE ②

Motor frequency is determined by a combination of motor RPM and the number of poles the motor contains and
these will be different depending on the particular MDR used. Please consult MDR documentation to determine
meaningful values for motor frequency
PLC I/O MODE NOTE ③

Bits 0 and 1 are used in combination to provide 4 possible states. The following chart defines the bit values for
these states:

Motor Status bit 0 and bit 1

Bit 1 Bit 0 Description
0 0 Motor not running, standard or servo braking applied
0 1 Motor running in CCW Direction
1 0 Motor running in CW Direction
1 1 Motor not running and no braking applied (free to spin)
PLC I/O MODE NOTE ④

The electrical logic state of the signal on the Sensor/Control Port pins are bit-wise exclusive OR (XOR) with the bits
set in the Sensor & Control Port Input Signal Condition Mask register (8-19) to arrive at the bit values seen in the
Sensor & Control Port Inputs (7-1) register. This allows the PLC programmer to control whether an electrically
energized condition results in a logical 1 or a logical 0 in the Sensor & Control Port Inputs (7-1) register. This same
relationship is also mirrored by the state of the input’s corresponding LED indicator.
See PLC I/O Mode Note ⑦ on page 59 for further details.
PLC I/O MODE NOTE ⑤

The data in this register is only valid when a given motor port is placed into Digital I/O mode by the PLC. When a
given motor port is being used as Digital I/O the only meaningful bits are bits 12 and 14 as shown. Other bits in
this register may contain values and should be ignored as valid input data.
Refer to Appendix A - Motor Port as Digital I/O on page 77 for wiring details for using a motor port as digital I/O.

PLC I/O MODE ASSEMBLY OUTPUTS

These registers are written by the PLC to the Module when the module is in PLC I/O mode. All registers are 16-bit
Integer data type.
Register Name PLC Address Data Description

Integer Value
0 = No Command
M: 4:1800 1 = Command local module’s Stop Group to go to Stopped State
ConveyStop Command
E: O.Data[0] 2 = Command local module’s Stop Group to Clear Stopped State
4:0020
Set Left Motor Port M: 4:1801 bit 0 = Motor Port Pin 3
Digital Control E: O.Data[1] bit 1 = Motor Port Pin 4
4:0060 P: Byte 2 (Hi) Byte 3 (Lo) bit 2 = Motor Port Pin 5
bit 6 = Brake Output Pin 9
bit 7 = Enable Brake Pin 9 when Motor Port is NOT in Digital mode
bit 8 = Clear Over-current error
Set Right Motor Port M: 4:1802 bit 9 thru 14 = Reserved
Digital Control E: O.Data[2] bit 15 = Digital Output Enable
4:0084 P: Byte 4 (Hi) Byte 5 (Lo) 0 = Use port as Motor Control
1 = Use port as Digital Output
See Appendix A - Motor Port as Digital I/O on page 77 for connection details.
bit 0 = Reserved
Control Port Digital M: 4:1803
bit 1 = Left Control Port
Output Control E: O.Data[3]
bit 2 = Reserved
4:0037 P: Byte 6 (Hi) Byte 7 (Lo)
bit 3 = Right Control Port
Bit 0:
1 = Run Command
M: 4:1804
Left Motor Run / Reverse 0 = Stop Command
E: O.Data[4]
4:0260 Bit 8:
0 = Run in Configured Direction
1 = Run opposite of Configured Direction
Integer Value
0 = Use Configured Brake Method
Left Motor Brake M: 4:1805
1 = Use Standard Brake Method
Method E: O.Data[5]
2 = Use Free Coast Brake Method
4:0261 P: Byte 10 (Hi) Byte 11 (Lo)
3 = Use Servo 1 Brake Method
Integer Value
Left Motor Speed Control M: 4:1806 0 = Use Configured Speed Control Method
Method E: O.Data[6] 1 = Use Open Loop
4:0262 P: Byte 12 (Hi) Byte 13 (Lo) 2 = Use Closed Loop


Bit 0:
1 = Run Command
Right Motor Run / M: 4:1807
0 = Stop Command
Reverse E: O.Data[7]
Bit 8:
4:0270 P: Byte 14 (Hi) Byte 15 (Lo)
0 = Run in Configured Direction
1 = Run opposite of Configured Direction
Integer Value
0 = Use Configured Brake Method
Right Motor Brake M: 4:1808
1 = Use Standard Brake Method
Method E: O.Data[8]
2 = Use Free Coast Brake Method
4:0271 P: Byte 16 (Hi) Byte 17 (Lo)
Integer Value
Right Motor Speed M: 4:1809 0 = Use Configured Speed Control Method
Control Method E: O.Data[9] 1 = Use Open Loop
4:0272 P: Byte 18 (Hi) Byte 19 (Lo) 2 = Use Closed Loop
Left Motor Speed M: 4:1810

Reference E: O.Data[10] Value in % PWM
4:0040 P: Byte 20 (Hi) Byte 21 (Lo) Range: 0 to 1000
Right Motor Speed M: 4:1811 Example: 400 = 40%
Reference E: O.Data[11] 0 = Remain at last non zero value entered
4:0064 P: Byte 22 (Hi) Byte 22 (Lo)
Left Motor Acceleration M: 4:1812 When Speed Control Method is in Open Loop:
Ramp E: O.Data[12] Value in milliseconds
4:0043 P: Byte 24 (Hi) Byte 25 (Lo) Range: 0 to 10000 (Deceleration)
Range: 30 to 10000 (Acceleration)
Left Motor Deceleration M: 4:1813 Example: 900 = 0.9 sec
Ramp E: O.Data[13]
4:0044 P: Byte 26 (Hi) Byte 27 (Lo) When Speed Control Method is Closed Loop:
Right Motor Acceleration M: 4:1814 Value in motor pulses
Ramp E: O.Data[14] Range: 0 to 10000 (Deceleration)
4:0067 P: Byte 28 (Hi) Byte 29 (Lo) Range: 30 to 10000 (Acceleration)
Right Motor Deceleration M: 4:1815 For Either Open or Closed Loop:

Ramp E: O.Data[15] 0 = Remain at last non-zero value entered
4:0068 P: Byte 30 (Hi) Byte 31 (Lo)
Logical 0 or 1
M: 4:1816 0 = Stop Reset
Clear Motor Error
E: O.Data[16] 1 = Send Reset
4:0022
Refer to ZPA Mode Note ⑥ on page 30 for details.
Used to write ERSC ZPA Status data to downstream ERSC:
4 = Instruct Downstream ERSC to “wake-up” and run its most upstream

Set Status to M: 4:1817 zone
Downstream Module E: O.Data[17] 1 = Instructs Downstream ERSC that carton has exited local zone and to
4:0196 P: Byte 34 (Hi) Byte 35 (Lo) accept any tracking data written in Set Discharge Tracking Word 1 /
Word 2 registers when carton arrives.
See PLC I/O Mode Note ⑥ on page 59


Used to write ERSC ZPA Status data to next upstream ERSC:
5 = Instructs Upstream ERSC’s discharge zone to accumulate and hold any

Set Status to Upstream M: 4:1818 carton that arrives at its discharge zone.
Module E: O.Data[18] 1 = Instructs Upstream ERSC’s discharge zone to release any carton that
4:0116 P: Byte 36 (Hi) Byte 37 (Lo) arrives at its discharge zone.
See PLC I/O Mode Note ⑥ on page 59

Bitwise Value
Sensor Port Input Signal M: 4:1819
Condition Mask E: O.Data[19]
4:0034 P: Byte 38 (Hi) Byte 39 (Lo)
See PLC I/O Mode Note ⑦ on page 59

Set Discharge Tracking M: 4:1820
Word 1 E: O.Data[20] Only used when local PLC I/O Mode ERSC needs to pass tracking data to a
4:0201 P: Byte 40 (Hi) Byte 41 (Lo) downstream connected ERSC. Used in conjunction with Set Status to
Downstream Module register
Set Discharge Tracking M: 4:1821
Word 2 E: O.Data[21] See PLC I/O Mode Note ⑥ on page 59
4:0202 P: Byte 42 (Hi) Byte 42 (Lo)
M: 4:1822
Reserved E: O.Data[22]
Signed integer value in motor pulses of the position to move to on the next Left
Motor Servo Run Command
Left Motor Servo M: 4:1823
Command Pulses E: O.Data[23]
Valid values are from -32767 to +32767
4:0008 P: Byte 46 (Hi) Byte 47 (Lo)
Bit 0: Reset Command
1 = Set Current Pulse Count as “0”
Left Motor Servo M: 4:1824 Bit 1: Servo Run Command
Command Word E: O.Data[24] 1 = Run in Motor from current pulse count to set pulse count in Left Motor
4:0009 P: Byte 48 (Hi) Byte 49 (Lo) Servo Command Pulses Register

Signed integer value in motor pulses of the position to move to on the next Left
Motor Servo Run Command
Right Motor Servo M: 4:1825
Command Pulses E: O.Data[25]
Valid values are from -32767 to +32767
4:0013 P: Byte 50 (Hi) Byte 51 (Lo)
Bit 0: Reset Command
1 = Set Current Pulse Count as “0”
Right Motor Servo M: 4:1826 Bit 1: Servo Run Command
Command Word E: O.Data[26] 1 = Run in Motor from current pulse count to set pulse count in Left Motor
4:0014 P: Byte 52 (Hi) Byte 52 (Lo) Servo Command Pulses Register


PLC I/O MODE NOTE ⑥

For registers involving status and tracking to upstream or downstream ERSC’s in ZPA mode, the connections must
be preserved when placing the ERSC in question into PLC I/O mode from within EasyRoll. Refer to section Optional
“Clear Connections” Choice on page 49 for further details.
PLC I/O MODE NOTE ⑦

For an ERSC in standard ZPA mode, the Auto-Configuration procedure sets values in this register to allow the ERSC
to correctly display the Sensor and Control port Input circuit LEDs to facilitate diagnostics. This is done, for
example, to make visual LED diagnostics the same for “zone blocked” regardless of the sensor type.
For example, suppose the zone photo sensors used are “Light Operate, Normally Open”. This means that the
sensor’s output is energizing the ERSC’s sensor input pin 4 when the zone is clear. The ERSC Sensor port LED
indicator for pin 4 (green) should illuminate when the zone is blocked; so the Auto-Configuration procedure sets a
bit in the Sensor & Control Port Input Signal Condition Mask register to correspond to the pin 4 signal on the
appropriate sensor port. If the sensor is electrically opposite such that its output energizes pin 4 of the sensor port
when the zone is blocked, then the bit corresponding to pin 4 for this sensor port is clear such that the sensor
port’s LED illuminates green when pin 4 is energized.
When an ERSC is placed in PLC I/O mode; the Sensor & Control Port Input Signal Condition Mask register is cleared
of the values set during the Auto-Configure procedure. The Sensor & Control Port Input Signal Condition Mask
register is made available for PLC I/O mode Sensor and Control port inputs to give the PLC programmer the same
flexibility for configuring which electrical state (on or off) of the input will cause a logical 1 to appear in the Sensor
& Control Port Inputs register and illuminate the pin’s corresponding LED. By setting or clearing the corresponding
bit for a given port’s pin 3 or 4 signal, the PLC programmer can determine which physical state (on or off) of the
input signal will cause its corresponding pin’s bit in the Sensor & Control Port Inputs register to be set and its
corresponding LED to illuminate.
The following are two examples that show the bit patterns and signals for one of the ERSC’s inputs. The same
pattern applies to all 8 available ERSC inputs:
Right Sensor Port - Pin 4 Signal

Electrical Sensor & Control Port Input Signal Sensor & Control Port Inputs
LED State
Signal Condition Mask Register bit 6 Register bit 6
OFF 0 0 Green = OFF
ON 0 1 Green = ON
OFF 1 1 Green = ON
ON 1 0 Green = OFF
Left Control Port - Pin 3 Signal

Electrical Sensor & Control Port Input Signal Sensor & Control Port Inputs
LED State
Signal Condition Mask Register bit 1 Register bit 1
OFF 0 0 Red = OFF
ON 0 1 Red = ON
OFF 1 1 Red = ON
ON 1 0 Red = OFF

Be careful when changing the Sensor & Control Port Input Signal Condition Mask in your
Ethernet I/P PLC program. The input bit values in the Sensor & Control Port Inputs register
can show unexpected or opposite values from expected until the PLC has updated the
Sensor & Control Port Input Signal Condition Mask data. This update could take several
program scans depending upon the Ethernet IP RPI settings. Take care to be sure that the
Sensor & Control Port Input Signal Condition Mask data is written to the ERSC Before
acting on any input values in the Sensor & Control Port Inputs register.
Please note that the Sensor/Control Port LEDs are tri-colored. In applications where both
Pin 4 and Pin 3 are used on the same Sensor/Control Port; please note that when the
green and red LEDs are illuminated at the same time, the color will be amber.

SERVO MOTOR CONTROL EXAMPLE
Servo Motor Control requires ConveyLinx firmware 4.14 or later
The Servo Motor Control function allows you to establish a zero or “home” rotational position of the MDR and
then instruct the ERSC to rotate an assigned number of motor pulses in either direction from this zero or “home”
position. PLC I/O Mode Assemblies provide the data registers to allow external PLC control of this function for
both the Left and Right MDR ports.
Servo Control functionality requires that the Closed Loop option be enabled for the motor
port in question. This can be done either by selecting the check box in EasyRoll or using
the PLC to write a value of “2” in the appropriate Motor Speed Control register for the
motor in question.
The Servo Motor Control function utilizes the existing motor speed, acceleration, and deceleration registers. The
existing starting, stopping, and direction control registers are not used and these functions are incorporated into
the Servo Control registers.
Servo Control functionality utilizes motor pulses as generated by the BLDC motor’s Hall
Effect Sensors as the metric for movement and positioning. The quantity of pulses per
revolution of the BLDC motor is based upon the number of motor poles X 3. The actual
number of pulses per revolution of the MDR tube is based upon the gear reduction ratio
of the gearbox in the MDR and the diameter of the tube.
For our example, we want to perform the following cycle using PLC control of the Left MDR on and ERSC:
• Establish a zero or home position by external input to PLC (sensor or operator button)
• Rotate in the CCW direction for 7000 pulses at a speed of 80% PWM with acceleration ramp of 100 pulses
and a deceleration ramp of 50 pulses
• Rotate the CW direction for 9000 pulses at a speed of 100% PWM with acceleration ramp of 50 pulses and
a deceleration ramp of 10 pulses.
• Rotate CCW back to the zero or home position at a speed of 80% PWM with acceleration ramp of 50
pulses and a deceleration ramp of 10 pulses.
• Wait for a cycle dwell time of 4 seconds and then repeat the rotation cycles
Now let’s define some logic names that correspond to actual PLC I/O Mode Assembly tag values to make our
example easier to follow:

Example Tag Data Type Assembly Register (/bit)

ZERO Boolean Left Servo Command Word - bit 0
ZERO_ACK Boolean Left Motor Servo Status - bit 1
RUN Boolean Left Servo Command Word - bit 1
READY Boolean Left Motor Servo Status - bit 0
POSITION Integer Left Servo Command Pulses
SPEED Integer Left Motor Speed Reference
ACCEL Integer Left Motor Acceleration Ramp
DECEL Integer Left Motor Deceleration Ramp
MODE Integer Left Motor Speed Control Method
Step #1: Place Left Motor in Closed Loop Mode by writing a “2” to MODE
Step #2: Upon external signal from sensor or button, set ZERO bit to establish zero or “home” position. When PLC
sees that the ZERO_ACK bit is set, then the PLC resets the ZERO bit.
Step #3: To make the first rotation, we need write the speed, ramp values, and distance to rotate to the
appropriate registers:
• Write 800 to SPEED

• Write 100 to ACCEL
• Write 50 to DECEL
• Write 7000 to POSITION
Step #4: If READY is reset, then the PLC can set the RUN bit to begin the rotation. When the rotation is complete,
the ERSC sets the READY bit. This will be the signal to the PLC to reset the RUN bit. Once the ERSC sees that the
RUN bit has been reset, it will reset the READY bit.
Step #5: For the second rotation, we need to write the speed and ramp values to the appropriate registers:

• Write 50 to ACCEL
• Write 10 to DECEL
Because we want to rotate in the opposite direction, we need to determine the new location based upon the
zero or “home” position. In this case, we know we went 700 pulses “forward” and we want to move 900
pulses “backward”. The position we want to end up is 7000-9000 = -2000.
• Write -2000 to POSITION
Step #6: Repeat Step #4.

rd nd
Step #7: For the 3 rotation, we keep the ramp values from the 2 rotation, but we need to set the speed and the
position to rotate. In this case we want to go to the zero or “home position.

• Write 0 to POSITION

Step #8: Repeat Step #4
Rotation Note: Rotation from 0 to a positive value always causes rotation in CCW
direction and rotation from 0 to a negative value always causes rotation in CW direction.
Servo Motor Control ignores the CW/CCW direction setting in EasyRoll and/or any
configured or default direction that may exist in the ERSC’s configuration.
Values shown in this example are for demonstration purposes only. Actual position,
speeds, acceleration, and deceleration values are highly dependent upon the mechanical
application.
PLC LADDER DIAGRAM


REDUCED SIZE PLC I/O MODE ASSEMBLIES

For some PLC controllers, the data size footprint required for a given assembly can be a limiting factor on how
many devices can connect to a given controller. ConveyLinx includes input/output assemblies with fewer registers
that contain basic functions in applications where the full functionality of the PLC I/O Mode Assemblies is not
required. The Reduced Size Assemblies provide basic I/O and motor control while removing the interfaces for
servo moves, upstream/downstream data, tracking data, etc.
REDUCED SIZE PLC I/O MODE ASSEMBLY INPUTS

Please note that the functions provided by this assembly are selected from and described in detail in section
PLCI/O Mode Assembly Inputs on page 51.
ERSC Internal
Register Name Assembled Address for PLC
Address
M: 4:2700
4:0035 Sensor & Control Port Inputs E: I.Data[0]
M: 4:2701
4:0036 Sensor Detect E: I.Data[1]
M: 4:2702
4:0057 Left Motor Temperature E: I.Data[2]
M: 4:2703
4:0058 Left Motor Status E: I.Data[3]
M: 4:2704
4:0081 Right Motor Temperature E: I.Data[4]
M: 4:2705
4:0082 Right Motor Status E: I.Data[5]
M: 4:2706
4:0060 Left Motor Port Digital I/O Status E: I.Data[6]
M: 4:2707
4:0084 Right Motor Port Digital I/O Status E: I.Data[7]
M: 4:2708
N/A Reserved E: I.Data[8]

REDUCED SIZE PLC I/O MODE ASSEMBLY OUTPUTS

Please note that the functions provided by this assembly are selected from and described in detail in section PLC
I/O Mode Assembly Outputs on page 55.
ERSC Internal
Register Name Assembled Address for PLC
Address
M: 4:2800
4:0060 Set Left Motor Port Digital Control E: O.Data[0]
M: 4:2801
4:0084 Set Right Motor Port Digital Control E: O.Data[1]
M: 4:2802
4:0037 Control Port Digital Output Control E: O.Data[2]
M: 4:2803
4:0260 Left Motor Run / Reverse E: O.Data[3]
M: 4:2804
4:0270 Right Motor Run / Reverse E: O.Data[4]
M: 4:2805
4:0040 Left Motor Speed Reference E: O.Data[5]
M: 4:2806
4:0064 Right Motor Speed Reference E: O.Data[6]
M: 4:2807
4:0022 Clear Motor Error E: O.Data[7]
M: 4:2808
N/A Reserved E: O.Data[8]

ConveyLogix Interface Assemblies 67
CONVEYLOGIX INTERFACE ASSEMBLIES

Please note that ConveyLogix Interface Assemblies are only available for
ERSC firmware 4.25 and later and ERSC firmware 5.2 and later.
ConveyLogix Version 2.2 and later is required for creating ConveyLogix
programs that can make the data available for access by these assemblies.
ERSCs in PLC I/O mode allow for download of a user program generated with the ConveyLogix programming tool.
There may be instances when you would like for an external PLC to be able to interface with an ERSC that is
running a ConveyLogix program. Because a custom user generated program is running in the ERSC, the previously
defined existing Assemblies for ZPA and PLO I/O modes are no longer valid and if used, could produce unexpected
results.
When using ConveyLogix programming software version 2.2 and later, the environment provides predefined
controlled input and output register tags that can be used by the programmer to interface with an external PLC.
The Assemblies described in this section are those that the external PLC would connect and use to access the data
in the ERSC ConveyLogix program.
This data is divided into 16 Integer Input words and 16 Integer output words. It is left to the ConveyLogix
programmer and the PLC programmer to utilize as much or as little of these data blocks as needed for their
particular application.
CONVEYLOGIX ASSEMBLY INPUTS
ERSC ConveyLogix Assembled Modbus PLC

Assembled EIP PLC Tag Assembled Profinet I/O
Controller Tag Register
ToPLCArray[0] E: I.Data[0] M: 4:13100 P: Byte 0 (Hi) Byte 1 (Lo)

CONVEYLOGIX ASSEMBLY OUTPUTS
ERSC ConveyLogix Assembled Modbus PLC

Assembled EIP PLC Tag Assembled Profinet I/O
Controller Tag Register
FromPLCArray[0] E: O.Data[0] M: 4:13200 P: Byte 0 (Hi) Byte 1 (Lo)

ZPA and PLC I/O Mode Assemblies with Reset Protection 69
ZPA AND PLC I/O MODE ASSEMBLIES WITH RESET PROTECTION

Please note that this functionality is only applicable for
Ethernet I/P and Modbus TCP PLCs. Functionality is not
applicable or used with Profinet I/O PLCs.
For control system applications where the Ethernet I/P PLC needs to take specific action to recover from a loss of
communications due to an ERSC module that has had its power cycled off and on; there is an additional set of
instances implemented that provides 2 new registers that allows the PLC to manipulate the function of the ERSC
module for recovery.
When an ERSC in ZPA Mode has lost power and then is powered back up, due to perhaps a system E-stop that
disconnects control power, some of the ERSC’s working register values are reset to 0. Among these are the arrival
counters, departure counters, and the accumulate commands for each configured zone(s) on the ERSC. Upon
power cycle to the ERSC, if the PLC can establish its full Ethernet I/P connection prior to the ZPA task becoming
fully functional, the preceding PLC programming examples would still function as expected. However, because PLC
Ethernet I/P connection time is variable and not fixed; a robust control system design cannot count on the PLC
establishing Ethernet I/P connection prior to the ERSC’s ZPA task commanding the module as if no PLC was
connected. A consequence of this in the previous programming example is that if a load happens to be
accumulated in a PLC controlled zone at the time of power loss, upon powering back up, the load can release
without the PLC commanding it to do so. This release could be caused by the PLC logic detecting a change in
arrival count and thus incrementing the release or it could be caused by the fact that the accumulate command is
cleared in the ERSC due to power cycle and because the PLC has not established communications to set the
accumulate command bit, the ERSC releases the zone because there is no command present to accumulate.
For ERSC’s in PLC I/O mode, Reset Protection may not be as much a concern as for a module in ZPA mode, however
reset protection assemblies are available for PLC I/O mode. Some items such as current servo position, etc. are
reset upon restoration of power and thus the PLC programmer may want to detect this condition and act
accordingly.
Reset Protection assemblies are used for applications where the ERSC remains in a “hold” state until the PLC has
established communications. Otherwise, the register mappings for these assemblies are the same as their non-
protected counterparts.
Please note that the Modbus TCP starting addresses for each assembly with reset protection is different from their
non-protected counterparts.

ZPA MODE ASSEMBLY INPUTS WITH RESET PROTECTION

ERSC Assembled Assembled
Internal Register Name Ethernet I/P Modbus
Address Address for PLC Address for PLC
4:0116 Local Status Upstream Zone E: I.Data[0] M: 4:3500
4:0196 Local Status Downstream Zone E: I.Data[1] M: 4:3501
4:0106 Arrival Count Local Upstream Zone E: I.Data[2] M: 4:3502
4:0107 Departure Count Local Upstream Zone E: I.Data[3] M: 4:3503
4:0186 Arrival Count Local Downstream Zone E: I.Data[4] M: 4:3504
4:0187 Departure Count Local Downstream Zone E: I.Data[5] M: 4:3505
4:0088 Module Status Word 1 E: I.Data[6] M: 4:3506
4:0119 Current Upstream Zone Tracking Word 1 E: I.Data[8] M: 4:3508
4:0120 Current Upstream Zone Tracking Word 2 E: I.Data[9] M: 4:3509
4:0199 Current Downstream Zone Tracking Word 1 E: I.Data[10] M: 4:3510
4:0200 Current Downstream Zone Tracking Word 2 E: I.Data[11] M: 4:3511
4:0105 Current Release Count for Upstream Zone E: I.Data[12] M: 4:3512
4:0185 Current Release Count for Downstream Zone E: I.Data[13] M: 4:3513
4:0201 Get Tracking Forward Direction Word 1 E: I.Data[14] M: 4:3514
4:0202 Get Tracking Forward Direction Word 2 E: I.Data[15] M: 4:3515
4:0237 Get Tracking Reverse Direction Word 1 E: I.Data[16] M: 4:3516
4:0238 Get Tracking Reverse Direction Word 2 E: I.Data[17] M: 4:3517
4:0035 Sensor & Control Port Inputs E: I.Data[18] M: 4:3518
N/A Current Module Reset Count E: I.Data[19] M: 4:3519
4:0019 ConveyStop Status E: I.Data[20] M: 4:3520

ZPA MODE ASSEMBLY OUTPUTS WITH RESET PROTECTION

4:0132 Set Local Upstream Zone Tracking Word 1 E: O.Data[0] M: 4:3600
4:0133 Set Local Upstream Zone Tracking Word 2 E: O.Data[1] M: 4:3601
4:0212 Set Local Downstream Zone Tracking Word 1 E: O.Data[2] M: 4:3602
4:0213 Set Local Downstream Zone Tracking Word 2 E: O.Data[3] M: 4:3603
4:0104 Accumulation Control for Local Upstream Zone E: O.Data[4] M: 4:3604
4:0184 Accumulation Control for Local Downstream Zone E: O.Data[5] M: 4:3605
4:0040 Set Left MDR Speed E: O.Data[6] M: 4:3606
4:0064 Set Right MDR Speed E: O.Data[7] M: 4:3607
4:0105 Release and Accumulate on Next Arrival for Local Upstream Zone E: O.Data[8] M: 4:3608
4:0185 Release and Accumulate on Next Arrival for Local Downstream Zone E: O.Data[9] M: 4:3609
4:0134 Set Status for Upstream Induct E: O.Data[10] M: 4:3610
4:0232 Set Status for Downstream Discharge E: O.Data[11] M: 4:3611
4:0139 Set Induct Tracking Forward Direction Word 1 E: O.Data[12] M: 4:3612
4:0237 Set Induct Tracking Reverse Direction Word 1 E: O.Data[14] M: 4:3614
4:0022 Clear Motor Error E: O.Data[16] M: 4:3616
4:0063 Set Control Port Outputs E: O.Data[17] M: 4:3617
N/A Set Module Reset Counter E: O.Data[18] M: 4:3618
4:0020 ConveyStop Command E: O.Data[19] M: 4:3619
4:0109 Clear Sensor Jam Command for Local Upstream Zone E: O.Data[20] M: 4:3620
4:0189 Clear Sensor Jam Command for Local Downstream Zone E: O.Data[21] M: 4:3621
4:0365 Direction & Accumulation Mode Control for Local Upstream Zone E: O.Data[22] M: 4:3622
4:0387 ConveyMerge Interface E: O.Data[24] M: 4:3624

REDUCED SIZE ZPA MODE ASSEMBLY INPUTS WITH RESET PROTECTION

4:0116 Local Status Upstream Zone Forward Direction E: I.Data[0] M: 4:4900
4:0196 Local Status Downstream Zone Forward Direction E: I.Data[1] M: 4:4901
REDUCED SIZE ZPA MODE ASSEMBLY OUTPUTS WITH RESET PROTECTION

4:0104 Accumulation Control for Local Upstream Zone E: O.Data[0] M: 4:5000
4:0184 Accumulation Control for Local Downstream Zone E: O.Data[1] M: 4:5001
4:0040 Set Left MDR Speed E: O.Data[2] M: 4:5002
4:0064 Set Right MDR Speed E: O.Data[3] M: 4:5003
4:0105 Release and Accumulate on Next Arrival for Local Upstream Zone E: O.Data[4] M: 4:5004
4:0185 Release and Accumulate on Next Arrival for Local Downstream Zone E: O.Data[5] M: 4:5005
4:0134 Set Status for Upstream Induct E: O.Data[6] M: 4:5006
4:0232 Set Status for Downstream Discharge E: O.Data[7] M: 4:5007
4:0063 Set Control Port Outputs E: O.Data[9] M: 4:5009
N/A Set Module Reset Counter E: O.Data[10] M: 4:5010
4:0109 Clear Sensor Jam Command for Local Upstream Zone E: O.Data[11] M: 4:5011
4:0189 Clear Sensor Jam Command for Local Downstream Zone E: O.Data[12] M: 4:5012

PLC I/O MODE ASSEMBLY INPUTS WITH RESET PROTECTION

Assembled Assembled
ERSC Internal
Register Name Ethernet I/P Modbus
Address
4:0019 ConveyStop Status E: I.Data[0] M: 4:3700
4:0036 Sensor Detect E: I.Data[2] M: 4:3702
4:0024 Module Voltage E: I.Data[3] M: 4:3703
4:0055 Left Motor Current E: I.Data[4] M: 4:3704
4:0056 Left Motor Frequency E: I.Data[5] M: 4:3705
4:0057 Left Motor Temperature E: I.Data[6] M: 4:3706
4:0058 Left Motor Status E: I.Data[7] M: 4:3707
4:0079 Right Motor Current E: I.Data[8] M: 4:3708
4:0080 Right Motor Frequency E: I.Data[9] M: 4:3709
4:0081 Right Motor Temperature E: I.Data[10] M: 4:3710
4:0082 Right Motor Status E: I.Data[11] M: 4:3711
4:0060 Left Motor Port Digital I/O Status E: I.Data[12] M: 4:3712
4:0084 Right Motor Port Digital I/O Status E: I.Data[13] M: 4:3713
4:0134 Upstream Module Status E: I.Data[14] M: 4:3714
4:0232 Downstream Module Status E: I.Data[15] M: 4:3715
4:0139 Current Tracking Word 1 for Adjacent Upstream Module E: I.Data[16] M: 4:3716
4:0140 Current Tracking Word 2 for Adjacent Upstream Module E: I.Data[17] M: 4:3717
N/A Current Module Reset Counter E: I.Data[18] M: 4:3718
4:0062 Left Motor Servo Position E: I.Data[19] M: 4:3719
4:0086 Right Motor Servo Position E: I.Data[20] M: 4:3720
4:0011 Left Motor Servo Status E: I.Data[21] M: 4:3721
4:0016 Right Motor Servo Status E: I.Data[22] M: 4:3722

PLC I/O MODE ASSEMBLY OUTPUTS WITH RESET PROTECTION

Assembled Assembled
ERSC Internal
Address
4:0020 ConveyStop Command E: O.Data[0] M: 4:3800
4:0060 Set Left Motor Port Digital Control E: O.Data[1] M: 4:3801
4:0084 Set Right Motor Port Digital Control E: O.Data[2] M: 4:3802
4:0037 Control Port Digital Output Control E: O.Data[3] M: 4:3803
4:0260 Left Motor Run / Reverse E: O.Data[4] M: 4:3804
4:0261 Left Motor Brake Method E: O.Data[5] M: 4:3805
4:0262 Left Motor Speed Control Method E: O.Data[6] M: 4:3806
4:0270 Right Motor Run / Reverse E: O.Data[7] M: 4:3807
4:0271 Right Motor Brake Method E: O.Data[8] M: 4:3808
4:0272 Right Motor Speed Control Method E: O.Data[9] M: 4:3809
4:0040 Left Motor Speed Reference E: O.Data[10] M: 4:3810
4:0064 Right Motor Speed Reference E: O.Data[11] M: 4:3811
4:0043 Left Motor Acceleration Ramp E: O.Data[12] M: 4:3812
4:0044 Left Motor Deceleration Ramp E: O.Data[13] M: 4:3813
4:0067 Right Motor Acceleration Ramp E: O.Data[14] M: 4:3814
4:0068 Right Motor Deceleration Ramp E: O.Data[15] M: 4:3815
4:0196 Set Status to Downstream Module E: O.Data[17] M: 4:3817
4:0116 Set Status to Upstream Module E: O.Data[18] M: 4:3818
4:0034 Sensor Port Input Signal Condition Mask E: O.Data[19] M: 4:3819
4:0201 Set Discharge Tracking Word 1 E: O.Data[20] M: 4:3820
4:0202 Set Discharge Tracking Word 2 E: O.Data[21] M: 4:3821
N/A Set Module Reset Count E: O.Data[22] M: 4:3822
4:0008 Left Motor Servo Command Pulses E: O.Data[23] M: 4:3823
4:0009 Left Motor Servo Command Word E: O.Data[24] M: 4:3824
4:0013 Right Motor Servo Command Pulses E: O.Data[25] M: 4:3825
4:0014 Right Motor Servo Command Word E: O.Data[26] M: 4:3826

REDUCED SIZE PLC I/O MODE ASSEMBLY INPUTS WITH RESET PROTECTION
Assembled Assembled
ERSC Internal
Address
4:0116 Local Status Upstream Zone E: I.Data[0] M: 4:4700
4:0196 Local Status Downstream Zone E: I.Data[1] M: 4:4701
REDUCED SIZE PLC I/O MODE ASSEMBLY OUTPUTS WITH RESET PROTECTION
Assembled Assembled
ERSC Internal
Address
4:0060 Set Left Motor Port Digital Control E: O.Data[0] M: 4:4800
4:0084 Set Right Motor Port Digital Control E: O.Data[1] M: 4:4801
4:0037 Control Port Digital Output Control E: O.Data[2] M: 4:4802
4:0260 Left Motor Run / Reverse E: O.Data[3] M: 4:4803
4:0270 Right Motor Run / Reverse E: O.Data[4] M: 4:4804
4:0040 Left Motor Speed Reference E: O.Data[5] M: 4:4805
4:0064 Right Motor Speed Reference E: O.Data[6] M: 4:4806
N/A Set Module Reset Count E: O.Data[8] M: 4:4808

RESET PROTECTION USAGE WITH THE PLC

When the PLC determines that it has a valid connection to the ERSC in question and is ready for it to respond to
output data being written by the PLC:
• Your PLC program needs to move the value in the Current Module Reset Counter register into the Set
Module Reset Counter register.
• When the ERSC detects that the value in Set Module Reset Counter register is equal to the value in the
Current Module Reset Counter register; the ERSC will respond to data being written by the PLC to the
remaining output assembly registers.
Please note that when the value in Current Module Reset Counter register is not equal to the
value in the Set Module Reset Counter register; the values in the Input registers will updated
by the ERSC and will be valid. In this state, even though the PLC may be writing data to
Output registers, the ERSC will ignore it.
FOR ZPA ZONES: To make sure a given zone accumulates upon power up, use EasyRoll
configuration tool software to set the zone to “Accumulate”. When set from EasyRoll, this
will be retained in the flash memory of the ERSC so that the zone will initially accumulate if
a load happens to be in the zone at the time of power up.
Be sure to click the “Accumulate” switch on the main

EasyRoll screen to cause the zone to accumulate upon
power up
When a ZPA zone is commanded to accumulate with a PLC and you happen to connect to
that ERSC with EasyRoll; the “Accumulate” switch icon on the main screen will visibly
indicate that the zone is accumulated. This visible icon will look the same as if it was clicked
ON from EasyRoll.
Keep in mind that a PLC command to accumulate IS NOT retained upon power loss to the
ERSC. Only if the “Accumulate” switch is toggled “ON” with the EasyRoll is the accumulate
condition for the zone retained in flash memory for use upon power-up.

Appendix A - Motor Port as Digital I/O 77
APPENDIX A - MOTOR PORT AS DIGITAL I/O
Motor port as digital I/O is only applicable for an ERSC in PLC I/O Mode
External controller must first set bit 15 = 1 in the Set Left/Right Motor Port Digital Control register for the motor
port (Left or Right) that is to be used as digital output. If bit 15 = 0, then the ERSC ignores the bit 0 thru bit 2
commands and will not provide meaningful status on bits 12 and 14 in the corresponding Left/Right Motor Port
Digital I/O Status register for the port in question. Bit 0, bit 1, and bit 2 can be independently set and reset by the
PLC and all 3 digital outputs can be energized simultaneously.
Figure 9 shows the wiring diagram for a given motor port configured for digital output. Please note that the ERSC
switches to GND to complete the circuit.
FIGURE 9 - WIRING DIAGRAM FOR MOTOR PORT CONFIGURED FOR DIGITAL OUTPUT
Connection to Pin 1 (GND) as shown is only required if the Output Power Supply is at
different DC common than the ERSC’s power supply. If both power supplies have the
same DC common, then this connection is not required.

Short Circuit Error on bit 12 is classified as a “fatal” error that will require either a cycle of
power on the ERSC or an explicit Motor Fault Reset command from external controller the
same as if the port was being used as a motor port.
External controller must continuously write “1” to the Motor Fault Reset register for at
least 500 msec for reset to occur.
USING THE BRAKE OUTPUT PIN ON THE MOTOR PORT

You can also utilize the Brake Output (Pin 9 on the JST connector) as a +24V output signal controlled from your PLC
program when the ERSC is in PLC I/O mode. This signal sources +24V and is limited to 0.5A load. Unlike the motor
phases (Pins 3, 4, and 5), the Brake Output is available when the motor port is not in digital mode and is actually
running a motor. When using the Brake Output when the port is actually running a motor, you must set bit 7 in
the appropriate left or right “Set Motor Port Digital Control” output word in order to enable the Brake Output
functionality. Once you do this, then bit 6 in the same word controls the on/off state of the digital signal.
If you have enabled the motor port for digital control by setting bit 15, you do not have to also set bit 7 to enable
the Brake Output. It is already enabled when you set bit 15.
FIGURE 10 - BRAKE OUTPUT OPTION FOR MOTOR PORT

Appendix B – ConveyLinx Connections 79
APPENDIX B – CONVEYLINX CONNECTIONS
ZPA MODE REGISTER DATA FLOW

Because each ERSC has read/write access to its adjacent ERSCs and by virtue of the Auto-Configuration procedure
that defines conveyor flow connections; each ERSC knows the I.P. address of its adjacent upstream and
downstream ERSC. In the direction of flow, each ERSC writes its zone’s status values to its next upstream and next
downstream ERSC. The following figure graphically illustrates a simple configuration of three ERSC’s and the
logical connections made by each ERSC to communicate with its adjacent modules and the local register used.
FIGURE 11 - ERSC REGISTER MAPPING FOR NORMAL FLOW
Please note that the following examples in this section assume the High Byte of all zone
status registers have been masked such that only the Low Byte values are used.
From the preceding charts, we can see that all of the Holding Registers in Figure 11 contain integer values
indicating a zone status. In essence, the ZPA control process in each ERSC writes its zone’s status to its adjacent
neighbors and monitors its local registers that are written to by its adjacent ERSC neighbors. The ZPA process acts
upon what is written to it and updates its local status accordingly. For example, the following sequence would be
typical:
• ERSC #1 continually reads register 4:0232 to know the status of ERSC #2’s local upstream zone
• If a Carton arrives at ERSC #1 discharge zone and the value in its register 4:0232 is equal to 4 or 5, then it
will stop the Carton at its downstream discharge zone
• ERSC #1 continues to read register 4:0232. Once the value in its register 4:0232 has changed to a value of
1 or 2; the Carton in its discharge zone can be conveyed to ERSC #2. To initiate this, ERSC #1 writes its
status value of 4 (located in register 4:0196) to register 4:0134 on ERSC #2.

• When ERSC #2 control logic sees its register 4:0134 change to a value of 4, it knows that a Carton is being
discharged onto its upstream zone and thus will energize its upstream zone MDR to run and accept the
Carton from ERSC #1.
There would be a similar sequence for ERSC #2 to convey a Carton to ERSC #3.
EXTERNAL CONTROLLER AS CONVEYLINX BRIDGE

An external controller or PLC can also write valid zone status data to ERSCs that are adjacent to a PLC controlled
non-ConveyLinx conveyor or machine. The PLC simply mimics the ERSC interface to control flow from upstream
ConveyLinx controlled conveyor and to initiate Load transfer to downstream ConveyLinx controlled conveyor.
FIGURE 12 - PLC CONVEYLINX BRIDGE
Figure 12 shows a simple example where a PLC would act as a bridge between two separate ConveyLinx subnets.
In this case, ERSC #1 is at the end of its particular subnet, so when it was configured; it knows that it does not have
a logical downstream connection. Similarly, ERSC #2 is at the beginning of its particular subnet, so when it was
configured it knows that it does not have a logical upstream connection. In order for Loads to flow from ERSC #1
eventually to ERSC #2; the PLC must act as a bridge and “mimic” the writing of register data to ERSC #1 and ERSC
#2 as if it was an ERSC module. This is illustrated in Figure 13.

Appendix B – ConveyLinx Connections 81
FIGURE 13 – DATA FLOW CHART FOR PLC CONVEYLINX BRIDGE EXAMPLE
For example, if the PLC wants to make sure that any Carton stops at the discharge of ERSC #1, it will write a value
of 5 into ERSC #1 register 4:0232. A value of 5 means “zone sensor blocked and motor stopped” and will be
interpreted by ERSC #1 as a reason to stop and hold any Carton that arrives at its discharge zone.
The PLC can monitor the status of ERSC #1 discharge zone by reading ERSC #1 register 4:0196. If this value is 5, the
PLC knows a Carton is present and stopped in ERSC #1’s discharge zone. When the PLC is ready to accept the
Carton, it simply writes a value of 1 to ERSC #1 register 4:0232.
For the discharge from the PLC controlled conveyor or machine, the PLC can monitor the status of the upstream
zone of ERSC #2 by reading ERSC #2 register 4:0116. For example, if a value of 5 is read, the PLC will know that the
ERSC #2 accepting zone is occupied and is not ready to accept a Carton. If the value read is a 1 or 2, then the PLC
knows it can discharge a Carton when ready. In order to discharge a Carton, the PLC will need to write a value of 4
to ERSC #2 register 4:0134 to tell ERSC #2 to run its upstream accepting zone.

Appendix C – Modbus Registers for Firmware 5.2 83
APPENDIX C – MODBUS REGISTERS FOR FIRMWARE 5.2

Firmware 5.2 was developed to be 100% compliant with the ODVA specification for Ethernet I/P. In generating this
firmware, we found that the numbering system we used to identify our Ethernet I/P assembly instances
encroached on reserved values in the ODVA specification. In order for Firmware 5.2 to be ODVA compliant
requires that our previous assembly instance identification numbers be reassigned. In so doing, this also had an
effect on our Modbus addressing for the contiguous blocks of registers used for accessing assembled data over
Modbus TCP.
For Firmware 5.2, the original addresses are no longer valid and this
appendix will show each table with the new ODVA compliant Modbus
register address ranges for each assembly.
All register Assembly tables in this guide show the Modbus addresses with their
original assignments that are still valid for Firmware versions 4.25 and older.
Specific instructions for handling pre-4.25, 4.25, and 5.2 firmware versions for Rockwell
PLCs will be described in the separate document Connecting to Rockwell PLC’s Version
2.0.

ZPA MODE ASSEMBLY INPUTS

ERSC Register Name Assembled Address for Original Assembled
Internal FW 5.2 Address for FW 4.25
Address and earlier
4:0116 Local Status Upstream Zone 4:11500 4:1500
4:0196 Local Status Downstream Zone 4:11501 4:1501
4:0106 Arrival Count Local Upstream Zone 4:11502 4:1502
4:0107 Departure Count Local Upstream Zone 4:11503 4:1503
4:0186 Arrival Count Local Downstream Zone 4:11504 4:1504
4:0187 Departure Count Local Downstream Zone 4:11505 4:1505
4:0088 Module Status Word 1 4:11506 4:1506
4:0119 Current Upstream Zone Tracking Word 1 4:11508 4:1508
4:0199 Current Downstream Zone Tracking Word 1 4:11510 4:1510
4:0105 Current Release Count for Upstream Zone 4:11512 4:1512
4:0185 Current Release Count for Downstream Zone 4:11513 4:1513
4:0201 Get Tracking Forward Direction Word 1 4:11514 4:1514
4:0237 Get Tracking Reverse Direction Word 1 4:11516 4:1516
4:0035 Sensor & Control Port Inputs 4:11518 4:1518
N/A Reserved 4:11519 4:1519
4:0019 ConveyStop Status 4:11520 4:1520

ZPA MODE ASSEMBLY OUTPUTS

Assembled Original
ERSC
Address for FW 5.2 Assembled
Internal Register Name
Address for FW
Address
4.25 and earlier
4:0132 Set Local Upstream Zone Tracking Word 1 4:11600 4:1600
4:0212 Set Local Downstream Zone Tracking Word 1 4:11602 4:1602
4:0104 Accumulation Control for Local Upstream Zone 4:11604 4:1604
4:0184 Accumulation Control for Local Downstream Zone 4:11605 4:1605
4:0040 Set Left MDR Speed 4:11606 4:1606
4:0064 Set Right MDR Speed 4:11607 4:1607
4:0105 Release and Accumulate on Next Arrival for Local Upstream Zone 4:11608 4:1608
4:0185 Release and Accumulate on Next Arrival for Local Downstream Zone 4:11609 4:1609
4:0134 Set Status for Upstream Induct 4:11610 4:1610
4:0232 Set Status for Downstream Discharge 4:11611 4:1611
4:0139 Set Induct Tracking Forward Direction Word 1 4:11612 4:1612
4:0237 Set Induct Tracking Reverse Direction Word 1 4:11614 4:1614
4:0022 Clear Motor Error 4:11616 4:1616
4:0063 Set Control Port Outputs 4:11617 4:1617
N/A Reserved 4:11618 4:1618
4:0020 ConveyStop Command 4:11619 4:1619
4:0109 Clear Sensor Jam Command for Local Upstream Zone 4:11620 4:1620
4:0189 Clear Sensor Jam Command for Local Downstream Zone 4:11621 4:1621
4:0365 Direction & Accumulation Mode Control for Local Upstream Zone 4:11622 4:1622
4:0387 ConveyMerge Interface 4:11624 4:1624

REDUCED SIZE ZPA MODE ASSEMBLY INPUTS

Assembled Original
ERSC
Address for FW 5.2 Assembled
Address for FW
Address
4.25 and earlier
N/A Reserved 4:12911 4:2911

REDUCED SIZE ZPA MODE ASSEMBLY OUTPUTS

Original
ERSC
Assembled Assembled
Address for FW 5.2 Address for FW
Address
4.25 and earlier
N/A Reserved 4:13010 4:3010

PLC I/O MODE ASSEMBLY INPUTS

Original
Assembled
ERSC Internal Assembled
Register Name Address for FW
Address Address for FW
5.2
4.25 and earlier
4:0036 Sensor Detect 4:11702 4:1702
4:0024 Module Voltage 4:11703 4:1703
4:0055 Left Motor Current 4:11704 4:1704
4:0056 Left Motor Frequency 4:11705 4:1705
4:0057 Left Motor Temperature 4:11706 4:1706
4:0058 Left Motor Status 4:11707 4:1707
4:0079 Right Motor Current 4:11708 4:1708
4:0080 Right Motor Frequency 4:11709 4:1709
4:0081 Right Motor Temperature 4:11710 4:1710
4:0082 Right Motor Status 4:11711 4:1711
4:0060 Left Motor Port Digital I/O Status 4:11712 4:1712
4:0084 Right Motor Port Digital I/O Status 4:11713 4:1713
4:0134 Upstream Module Status 4:11714 4:1714
4:0232 Downstream Module Status 4:11715 4:1715
4:0139 Current Tracking Word 1 for Adjacent Upstream Module 4:11716 4:1716
N/A Reserved 4:11718 4:1718
4:0062 Left Motor Servo Position 4:11719 4:1719
4:0086 Right Motor Servo Position 4:11720 4:1720
4:0011 Left Motor Servo Status 4:11721 4:1721
4:0016 Right Motor Servo Status 4:11722 4:1722

PLC I/O MODE ASSEMBLY OUTPUTS

Original
Assembled
5.2
4.25 and earlier
4:0060 Set Left Motor Port Digital Control 4:11801 4:1801
4:0084 Set Right Motor Port Digital Control 4:11802 4:1802
4:0037 Control Port Digital Output Control 4:11803 4:1803
4:0260 Left Motor Run / Reverse 4:11804 4:1804
4:0261 Left Motor Brake Method 4:11805 4:1805
4:0262 Left Motor Speed Control Method 4:11806 4:1806
4:0270 Right Motor Run / Reverse 4:11807 4:1807
4:0271 Right Motor Brake Method 4:11808 4:1808
4:0272 Right Motor Speed Control Method 4:11809 4:1809
4:0040 Left Motor Speed Reference 4:11810 4:1810
4:0064 Right Motor Speed Reference 4:11811 4:1811
4:0043 Left Motor Acceleration Ramp 4:11812 4:1812
4:0044 Left Motor Deceleration Ramp 4:11813 4:1813
4:0067 Right Motor Acceleration Ramp 4:11814 4:1814
4:0068 Right Motor Deceleration Ramp 4:11815 4:1815
4:0196 Set Status to Downstream Module 4:11817 4:1817
4:0116 Set Status to Upstream Module 4:11818 4:1818
4:0034 Sensor Port Input Signal Condition Mask 4:11819 4:1819
4:0201 Set Discharge Tracking Word 1 4:11820 4:1820
N/A Reserved 4:11822 4:1822
4:0008 Left Motor Servo Command Pulses 4:11823 4:1823
4:0009 Left Motor Servo Command Word 4:11824 4:1824
4:0013 Right Motor Servo Command Pulses 4:11825 4:1825
4:0014 Right Motor Servo Command Word 4:11826 4:1826

REDUCED SIZE PLC I/O MODE ASSEMBLY INPUTS

Original
ERSC Assembled
Assembled
Internal Register Name Address for FW
Address for FW
Address 5.2
4.25 and earlier
4:0036 Sensor Detect 4:12701 4:2701
N/A Reserved 4:12708 4:2708
REDUCED SIZE PLC I/O MODE ASSEMBLY OUTPUTS

Original
ERSC Assembled
Assembled
Address for FW
Address 5.2
4.25 and earlier
N/A Reserved 4:12808 4:2808

ZPA MODE ASSEMBLY INPUTS WITH RESET PROTECTION

Original
ERSC Assembled
Assembled
Address for FW
Address 5.2
4.25 and earlier
N/A Current Module Reset Count 4:31519 4:3519

ZPA MODE ASSEMBLY OUTPUTS WITH RESET PROTECTION

Original
ERSC Assembled
Assembled
Address for FW
Address 5.2
4.25 and earlier
4:0237 Set Induct Tracking Reverse Direction Word 1 4:31614 4:3614
N/A Set Module Reset Counter 4:31618 4:3618
4:0387 ConveyMerge Interface 4:31624 4:3624

REDUCED SIZE ZPA MODE ASSEMBLY INPUTS WITH RESET PROTECTION

Original
ERSC Assembled
Assembled
Address for FW
Address 5.2
4.25 and earlier
4:0116 Local Status Upstream Zone Forward Direction 4:32900 4:4900
4:0196 Local Status Downstream Zone Forward Direction 4:32901 4:4901

REDUCED SIZE ZPA MODE ASSEMBLY OUTPUTS WITH RESET PROTECTION

Original
ERSC Assembled
Assembled
Address for FW
Address 5.2
4.25 and earlier
N/A Set Module Reset Counter 4:33010 4:5010

PLC I/O MODE ASSEMBLY INPUTS WITH RESET PROTECTION

Original
Assembled
5.2
4.25 and earlier
4:0036 Sensor Detect 4:31702 4:3702
4:0024 Module Voltage 4:31703 4:3703
4:0055 Left Motor Current 4:31704 4:3704
4:0056 Left Motor Frequency 4:31705 4:3705
4:0079 Right Motor Current 4:31708 4:3708
4:0080 Right Motor Frequency 4:31709 4:3709
4:0134 Upstream Module Status 4:31714 4:3714
4:0232 Downstream Module Status 4:31715 4:3715
N/A Current Module Reset Counter 4:31718 4:3718
4:0062 Left Motor Servo Position 4:31719 4:3719
4:0086 Right Motor Servo Position 4:31720 4:3720
4:0011 Left Motor Servo Status 4:31721 4:3721
4:0016 Right Motor Servo Status 4:31722 4:3722

PLC I/O MODE ASSEMBLY OUTPUTS WITH RESET PROTECTION

Original
Assembled
5.2
4.25 and earlier
4:0261 Left Motor Brake Method 4:31805 4:3805
4:0262 Left Motor Speed Control Method 4:31806 4:3806
4:0271 Right Motor Brake Method 4:31808 4:3808
4:0272 Right Motor Speed Control Method 4:31809 4:3809
4:0043 Left Motor Acceleration Ramp 4:31812 4:3812
4:0044 Left Motor Deceleration Ramp 4:31813 4:3813
4:0067 Right Motor Acceleration Ramp 4:31814 4:3814
4:0068 Right Motor Deceleration Ramp 4:31815 4:3815
4:0196 Set Status to Downstream Module 4:31817 4:3817
4:0116 Set Status to Upstream Module 4:31818 4:3818
4:0034 Sensor Port Input Signal Condition Mask 4:31819 4:3819
N/A Set Module Reset Count 4:31822 4:3822
4:0008 Left Motor Servo Command Pulses 4:31823 4:3823
4:0009 Left Motor Servo Command Word 4:31824 4:3824
4:0013 Right Motor Servo Command Pulses 4:31825 4:3825
4:0014 Right Motor Servo Command Word 4:31826 4:3826

REDUCED SIZE PLC I/O MODE ASSEMBLY INPUTS WITH RESET PROTECTION
Original
Assembled
5.2
4.25 and earlier
REDUCED SIZE PLC I/O MODE ASSEMBLY OUTPUTS WITH RESET PROTECTION
Original
Assembled
5.2
4.25 and earlier
N/A Set Module Reset Count 4:32808 4:4808

Notes: 99
NOTES:


Developers Guide

Uploaded by

Developers Guide

Uploaded by

Version 5.

Modbus TCP/IP specification was developed in 1999 to combining a ubiquitous physical

Publication ERSC-1500 Rev 5.0 – March 2016

IMPORTANT USER INFORMATION

Reproduction of the contents of this manual, in whole or in part, without written

Publication ERSC-1500 Rev 5.0 – March 2016

Revision Date Change / Update

GLOBAL CONTACT INFORMATION

Publication ERSC-1500 Rev 5.0 – March 2016

Publication ERSC-1500 Rev 5.0 – March 2016

PLC I/O Mode Note ① ....................................................................................................................................53

Publication ERSC-1500 Rev 5.0 – March 2016

WHO SHOULD USE THIS MANUAL?

NOT INCLUDED IN THIS MANUAL

Publication ERSC-1500 Rev 5.0 – March 2016

FIGURE 1 - CONVEYLINX® CONCEPT WITH ERSC MODULES

Publication ERSC-1500 Rev 5.0 – March 2016

CONVEYLINX ERSC OPERATIONAL MODES

• Zero Pressure Accumulation (ZPA) Mode

PLC I/O MODE

IMPORTANT CONCEPT TO REMEMBER: A PLC or external controller can

Publication ERSC-1500 Rev 5.0 – March 2016

• Out of the Box

• Ethernet I/P, Profinet I/O, or Modbus TCP Networks supported

• Requires Mode change to PLC I/O in EasyRoll

• Requires Mode change to PLC I/O in EasyRoll

Publication ERSC-1500 Rev 5.0 – March 2016

CONVEYLINX NETWORK ARCHITECTURE

Publication ERSC-1500 Rev 5.0 – March 2016

FIGURE 2 - PLC ASSEMBLY CONCEPT

MODBUS ASSEMBLY INSTANCE STRUCTURE

Publication ERSC-1500 Rev 5.0 – March 2016

• Service Code 3 - Read Holding Register (up to 45 registers per instruction)

All Modbus Addresses in the following Assembly Charts are

Publication ERSC-1500 Rev 5.0 – March 2016

ETHERNET I/P ASSEMBLY INSTANCE STRUCTURE

Please refer to Connecting ConveyLinx to Rockwell PLC’s –

Publication ERSC-1500 Rev 5.0 – March 2016

PROFINET IO ASSEMBLY INSTANCE STRUCTURE

Please refer to Connecting ConveyLinx to Profinet PLCs – Insight

Publication ERSC-1500 Rev 5.0 – March 2016

PLC CONTROLLER WITH ZPA MODE

NOTES ABOUT ASSEMBLIES FOR ERSC IN ZPA MODE

REGISTER CHART LEGEND

Publication ERSC-1500 Rev 5.0 – March 2016

ZPA MODE ASSEMBLY INPUTS FOR PLC

Register Name / Assembled Address

M: 4:1500 (High Byte)

Publication ERSC-1500 Rev 5.0 – March 2016

Register Name / Assembled Address

Publication ERSC-1500 Rev 5.0 – March 2016

Register Name / Assembled Address

See ZPA Mode Note ② on page 25

Refer to Insight Automation publication ERSC-1800 ConveyStop User’s Guide

ZPA MODE NOTE ①

Publication ERSC-1500 Rev 5.0 – March 2016

ZPA MODE NOTE ②

Publication ERSC-1500 Rev 5.0 – March 2016

ZPA MODE ASSEMBLY OUTPUTS FOR PLC

Register Name / Assembled Address

See ZPA Mode Note ⑤ on page 29 for further details

See ZPA Mode Note ⑤ on page 29 for further details

Publication ERSC-1500 Rev 5.0 – March 2016

Register Name / Assembled Address

Publication ERSC-1500 Rev 5.0 – March 2016

Register Name / Assembled Address

Used to dynamically modify a ConveyMerge configuration already established

Please refer to publication ERSC-1005 User’s Guide Supplement for ConveyMerge

Publication ERSC-1500 Rev 5.0 – March 2016

ZPA MODE NOTE ③

ZPA MODE NOTE ④

ZPA MODE NOTE ⑤

B IT 8 – A CCUMULATE A DJACENT U PSTREAM Z ONE

B IT 9 – S ET A RRIVAL C ONFIRMATION FOR D OWNSTREAM Z ONE

Publication ERSC-1500 Rev 5.0 – March 2016

B ITS 10 & 11 – J OG C ONTROLS