ConveyLinx ERSC Family Complete Guide
ConveyLinx ERSC Family Complete Guide
Complete Guide
Version 5.1 — 15 April 2022
2. Glossary of T
Ter
erms
ms ................................................................................................................ 12
4. Module Har
Hardwar
dware
e ................................................................................................................. 18
4.1. Identifying Module Components .................................................................................. 19
4.2. Mounting Dimensions .................................................................................................. 21
4.3. Motor Ports ................................................................................................................. 24
4.4. Sensor & Control Ports ................................................................................................ 25
4.5. Ethernet Ports ............................................................................................................. 27
4.6. Module Internal Fusing ................................................................................................ 28
4.7. Over-Voltage Protection............................................................................................... 29
4.8. LED Status Indicators .................................................................................................. 30
4.9. Power and Network Connections ................................................................................. 34
4.10. Power Supply Sizing .................................................................................................. 35
4.11. Technical Specifications............................................................................................. 36
5. Auto
Auto-Configuration
-Configuration...............................................................................................................
............................................................................................................... 41
5.1. Linear Conveyor .......................................................................................................... 42
5.1.1. Device Connections to Modules ...........................................................................43
5.1.2. Examples that will generate errors ......................................................................45
5.1.3. Motor Rotation Definition ..................................................................................... 46
5.2. Procedure.................................................................................................................... 47
5.3. Auto-Configuration Examples ...................................................................................... 50
5.4. Expected Results......................................................................................................... 51
5.5. What to do if things go wrong ..................................................................................... 53
7. SE Br
Break
eakout
out Module ............................................................................................................. 84
7.1. Typical Output Connection........................................................................................... 86
7.2. Typical Input Connections............................................................................................ 87
7.3. Input Circuit Blocking Diode Jumpers...........................................................................88
7.4. Notes on SE Module Revisions ..................................................................................... 90
8. EasyR
EasyRoll
oll Sof
Softwar
tware
e ................................................................................................................ 93
8.1. Installing EasyRoll on your PC ..................................................................................... 94
8.2. ConveyLinx Ethernet Definition ................................................................................... 95
8.3. Connecting your PC to ConveyLinx .............................................................................. 97
8.4. Using Discover Function .............................................................................................. 99
8.5. Main Screen .............................................................................................................. 100
8.5.1. Node Navigation ................................................................................................ 102
8.5.2. Node Identification ............................................................................................ 103
8.5.3. ZPA Upstream/Downstream Zone Settings ......................................................... 104
8.5.3.1. ZPA Release Mode...................................................................................... 105
8.5.3.1.1. Singulation Release ............................................................................ 106
8.5.3.1.2. Train Release ...................................................................................... 107
8.5.3.1.3. GAP Train Release .............................................................................. 108
8.5.3.2. T-Zone Settings.......................................................................................... 109
8.5.3.3. ZPA Error and Information .......................................................................... 112
8.5.3.4. Accumulate Control from Main Screen........................................................ 113
8.5.3.5. Settings Checkboxes .................................................................................. 114
8.5.3.5.1. Disable Reset Delays .......................................................................... 115
8.5.3.5.2. Disable Sensor Jam Auto Clear ........................................................... 116
8.5.3.5.3. Disable Arrival Timeout ...................................................................... 117
8.5.3.5.4. Disable Manual Operation .................................................................. 118
8.5.3.5.5. Dynamic Release................................................................................ 120
8.5.4. Motor Settings ................................................................................................... 122
8.5.4.1. Motor Type ................................................................................................. 123
8.5.4.2. Brake Method............................................................................................. 124
8.5.4.3. Speed Control Method................................................................................ 126
8.5.4.4. Speed ........................................................................................................ 128
8.5.4.5. Rotation Direction ...................................................................................... 130
8.5.4.6. Acceleration/Deceleration .......................................................................... 131
8.5.4.7. Motor Jog and Error Indicators .................................................................... 133
8.5.4.8. Motor Pulse to Distance Calculation ........................................................... 136
8.5.5. Diagnostic Window ............................................................................................ 137
8.6. Advanced Dialog ....................................................................................................... 139
8.6.1. Look Ahead and Timing Tab ............................................................................... 140
8.6.1.1. Look Ahead Slowdown Feature ................................................................... 141
8.6.1.2. Jam Auto Clear Timers................................................................................ 144
8.6.1.3. Run After Time/Distance............................................................................. 145
8.6.1.4. Induct Forward Time/Distance .................................................................... 147
8.6.1.5. Induct Reverse Time/Distance .................................................................... 149
8.6.1.6. Sensor Debounce ....................................................................................... 151
8.6.1.7. Reversing Control in ZPA Mode................................................................... 153
8.6.2. Upgrade Tab ...................................................................................................... 156
8.6.3. Connections Tab ................................................................................................ 159
8.6.4. Network Services Tab ........................................................................................ 162
8.6.4.1. Discover and IP Address Set....................................................................... 163
8.6.4.2. Position and DHCP ..................................................................................... 166
8.6.4.3. Network Lock Feature ................................................................................ 169
8.6.4.4. Backup and Restore ................................................................................... 171
8.6.5. Special Services Tab .......................................................................................... 174
8.6.5.1. Motor Slave Function ................................................................................. 177
8.6.6. Control Ports Tab ............................................................................................... 182
8.6.6.1. Control Port Inputs ..................................................................................... 183
8.6.6.2. Control Port Outputs .................................................................................. 185
8.6.6.3. Upstream/Downstream Accumulation......................................................... 187
8.6.6.4. Lane Full Interface ..................................................................................... 188
8.6.6.5. PLC Control of Control Ports ....................................................................... 189
8.6.7. Flex Zone Tab .................................................................................................... 190
8.6.8. Sensors Tab ....................................................................................................... 193
8.6.9. Extensions Tab................................................................................................... 194
9. ConveyMer
ConveyMerge
ge.....................................................................................................................
..................................................................................................................... 198
9.1. ConveyMerge Prerequisites and Requirements .......................................................... 200
9.2. Network Architecture ................................................................................................ 201
9.3. Sensor Placement ..................................................................................................... 203
9.4. Merge Zone Module .................................................................................................. 205
9.5. Merging Lines............................................................................................................ 208
9.6. Merge Configurations ................................................................................................ 210
9.7. Merge Priority ........................................................................................................... 211
9.8. T-Merge Settings ....................................................................................................... 212
9.9. Configuring Dynamic Priority Release ........................................................................ 214
9.10. Enabling ConveyMerge from EasyRoll ...................................................................... 217
9.11. Conventional Spur Merge Example .......................................................................... 219
9.12. T-Merge Example..................................................................................................... 221
9.13. Merge Line Full Example.......................................................................................... 223
10. ConveyStop ..................................................................................................................... 225
10.1. Benefits of ConveyStop ........................................................................................... 228
10.2. Using ConveyStop in an Integrated Stop System ..................................................... 229
10.3. ConveyStop Architecture ......................................................................................... 233
10.4. ConveyStop Software .............................................................................................. 235
10.4.1. User Accounts ................................................................................................. 236
10.4.2. Creating a New Project .................................................................................... 237
10.4.3. Discovering Modules........................................................................................ 238
10.4.4. Creating Stop Groups....................................................................................... 240
10.4.5. Add Stop and Start Buttons ............................................................................. 243
10.4.6. Commit All Button ........................................................................................... 245
10.4.7. Status Monitoring ............................................................................................ 247
10.5. Issuing a Stop Command ......................................................................................... 248
10.5.1. Other Conditions that cause Stop .................................................................... 250
10.5.2. Indications a Stop is Active .............................................................................. 252
10.5.3. ERSC Functions Affected by Stop Command..................................................... 254
10.5.4. CNIP Functions Affected by Stop Command...................................................... 256
10.6. ConveyLinx Function at Stop Group Boundaries....................................................... 257
10.7. Issuing a Start Command ........................................................................................ 258
10.7.1. Indications Start is Active ................................................................................ 260
10.8. Using a PLC with ConveyStop .................................................................................. 261
10.8.1. ConveyStop Status Register............................................................................. 263
10.8.2. ConveyStop Command Register ....................................................................... 264
10.9. Wiring Examples ..................................................................................................... 265
10.9.1. ERSC with Stop Button..................................................................................... 266
10.9.2. ERSC with Start Button .................................................................................... 267
10.9.3. CNIP with Stop Button...................................................................................... 268
10.9.4. CNIP with Start Button ..................................................................................... 269
13. Connecting to R
Rockwell
ockwell PLCs with Ether
Ethernet
net I/P .................................................................
.................................................................426
426
13.1. Selecting Your Connection Method based upon Assembly ........................................428
13.2. Using Generic Ethernet Module Method ................................................................... 429
13.3. Procedure for Connecting using Generic Ethernet Module........................................431
13.3.1. Parameters for Each Assembly......................................................................... 432
13.4. Procedure for using EDS Method ............................................................................. 435
13.5. Using ERSC Add On Instructions (AOI) with RSLogix 5000 ........................................437
13.5.1. AOI Tag Descriptions ........................................................................................ 439
13.5.1.1. ZPA Mode Inputs ...................................................................................... 440
13.5.1.2. ZPA Mode Outputs ................................................................................... 442
13.5.1.3. PLC I/O Mode Inputs ................................................................................. 445
13.5.1.4. PLC I/O Mode Outputs .............................................................................. 448
13.6. Using Logix 5000 MSG Instruction ........................................................................... 451
13.6.1. Read MSG Instruction ...................................................................................... 452
13.6.2. Write MSG Instruction ...................................................................................... 454
13.6.3. Reading ERSC Input Assembly with MSG Instruction ........................................456
13.7. EDS Module Data Type Cross Reference................................................................... 458
For ConveyLinx-
ConveyLinx-ERSC
ERSC Fir
irmwar
mwaree versions 4.25 / 5.02 please
refer to ConveyLinx ERSC Complete Guide Manual V
Version
ersion
5.0
Products Cover
Covered
ed in this Manual
ConveyLinx-
ConveyLinx-ERSC
ERSC
Article Number
3010-0000
Page 8 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
ConveyLinx-
ConveyLinx-HTF
HTF
Article Number
3010-3000
ConveyLinx-
ConveyLinx-ERSC
ERSC-E
-E
Article Number
3110-0000
ConveyLinx-
ConveyLinx-HTF
HTF-E
-E
Article Number
3110-3000
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
Page 9 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
! 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, Pulseroller
does not assume responsibility or liability (to include intellectual property
liability) for actual use based on the examples shown in this publication
! 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
Page 10 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
How to Contact Us
Technical Support North & South America: [email protected]
Sales Support North & South America: [email protected]
Technical Support Global: [email protected]
Sales Support Global: [email protected]
Web Site: www.pulseroller.com
Page 11 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
2. Glossary of T
Ter
erms
ms
Ter
ermm Definition
Conveyor control module that is part of the ConveyLinx family. Each module
ConveyLinx-Ai / can accommodate up to 2 MDR conveyor zones. The modules allow
ConveyLinx-Ai2 / connection for Senergy-Ai platform motor rollers and gear drives. The term
ConveyLInx-Ai3 Module will be used within this document and will refer to the ConveyLinx-Ai2
device
Ethernet Roller Speed Control module – Conveyor control module that is part
of the ConveyLinx family. Each ERSC can accommodate up to 2 MDR
ERSC
conveyor zones. In this document the term module will be synonymous with
ERSC
Light Emitting Diode – In the context of this document, LED’s are used on the
LED
ConveyLinx-Ai2 to provide visual indication of module status
Page 12 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
This is the type of a connector, which has four connector pins and is used on
M8
the ConveyLinx Ai2 modules for both sensor connectors and MDR connectors
Page 13 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Control logic terminology to define the state of the output of a Boolean “on”
or “off” device. The term specifically describes the state of the output circuit
when the device’s sensing circuit is un-energized. In the context of photo-
sensors; a normally open wired sensor would have its output circuit
Nor
Normally
mally Open /
energized when it detected its reflected light and its output circuit would be
Nor
Normally
mally Closed
de-energized when it did not detect its reflected light. Conversely a photo-
sensor wired normally closed would energize its output circuit when it did not
see its reflected light and it would de-energize its output circuit when it did
detect its reflected light
Electronics term that indicates the type of transistor circuit used for a logical
input or output for controllers. NPN devices will provide a common or ground
NPN / PNP
connection when activated and a PNP device will provide a logic voltage
connection when activated
A device, mounted near the end of the conveyor zone to sense the presence
Photo
Photo-sensor
-sensor
of a carton on the zone
Pulse Width Modulation – a control scheme that utilizes high speed switching
PWM transistors to efficiently deliver power in a controlled fashion from the
ConveyLinx controller to MDR
Page 14 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Conveyor control method for zoned controlled conveyor that dictates that
Singulation when a zone is discharging its carton, the upstream carton waiting to enter
Release must wait until the discharged carton is completely clear before it is allowed
to enter
Conveyor control method for zone configured conveyor that dictates that
Train R
Release
elease when a zone is discharging, the upstream zone’s carton can move in unison
with the discharging carton.
Zero Pressure Accumulation – Term that describes the conveyor controls and
ZP
ZPA
A mechanical scheme that will cause loads to queue on a conveyor in discrete
zones such that loads do not touch each other
Page 15 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
3. Getting Started
Purpose of this Manual
This manual is intended for users who need basic product information and simple application
procedures to implement Modules to control simple linear conveyor.
You should have a basic understanding of electrical circuitry and familiarity with relay logic,
conveyor equipment, photo-sensors, etc. If you do not, obtain the proper training before using
this product.
The Basics
Page 16 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
How to change your Control Port Inputs to match the signals you are using
Page 17 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
4. Module Har
Hardwar
dware
e
ConveyLinx Modules are designed to be installed and integrated into the conveyor’s
mechanical side frame assembly. The ConveyLinx Module is a controller for up to 2 Motorized
Drive Roller (MDR) conveyor zones. Each ConveyLinx Module provides connection points for 2
MDR units with their corresponding 2 photo-sensors as well as upstream and downstream
network and discreet interconnections to form a complete control system for zoned MDR
conveyors.
* The “left” and “right” naming convention for the module ports is based upon
facing the front of the ConveyLinx Module and is not to be confused with
direction of product flow on the conveyor. Product flow will be designated as
“upstream” and “downstream”
Learn more:
Identif
Identifying
ying ConveyLinx Module Components
Mounting Dimensions
Motor P Ports
orts
Sensor & Contr
Control
ol P
Ports
orts
Ether
Ethernet
net PPorts
orts
ConveyLinx Module InterInternal
nal F
Fusing
using
LED Status Indicators
Page 18 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
4.1. Identif
Identifying
ying Module Components
Item Description
& Motor Left and Motor Right 9-pin JST style header for MDR/PGD connection
Left Sensor Port and Right Sensor Port RJ-12 style jack for zone photo-sensor
& connection
Link Left and Link Right RJ-45 style Ethernet network communication
& connection between modules
Left Control Port and Right Control Port RJ-12 style ports for discreet hard-
& wired signal connections for non-networked interface interlocks and zone
control
Page 19 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
& Motor Left LED & Motor Right LED – Motor status indicators
& Control Port Left & Control Port Right Status LED Indicators
Page 20 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Page 21 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
ConveyLinx-
ConveyLinx-HTF
HTF (3010-3000) and ConveyLinxE-
ConveyLinxE-HTF
HTF
(3110-3000)
Conveyor F
Frame
rame P
Prreforations Dimensions
Page 22 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Page 23 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
4.3. Motor P
Ports
orts
Both the Left and the Right Motor Ports utilize a 9-pin JST brand female receptacle. Each
receptacle is mechanically keyed to assure proper orientation upon plugging in. The motor
connector pin-outs are as shown
Pin Description
1 GND
3 Motor Winding U
4 Motor Winding V
5 Motor Winding W
* Please note the JST connector is keyed so you cannot plug it in upside down
Page 24 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Sensor P
Port
ort P
Pin
in Out
Pin Signal Description
1 Not Used
Digital Input for Sensor’s error output – Auto detect for NPN or
3 Sensor Error
PNP
Digital Input for Sensor’s state output – Auto detect for NPN or
4 Sensor State
PNP
6 Not Used
! Shorting Pins 2 & 5 (Vcc and Gnd) may damage the port’s Sensor Detect circuit.
If this circuit is damaged, the module will no longer properly detect a connected
sensor and will not properly Auto-Configure.
Page 25 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Contr
Control
ol P
Port
ort P
Pin
in Out
Pin Signal Description
4 P4 Input Optional Interlock Digital Input – Auto detect for NPN or PNP
! Single output signal flows between Pin 1 and Pin 6. This signal is very low power
(@ 2mA). An SE Breakout Module is recommended when using of this signal.
Page 26 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
4.5. Ether
Ethernet
net P
Ports
orts
Both of these ports are standard RJ-45 jacks conforming to standard Ethernet connection pin-
out.
Page 27 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
! User’s must take care in the types of sensors and devices that need to connect
to a given ConveyLinx Module and assure that the current draw on any Sensor/
Control port pair does not exceed the fuse ratings. If any of the 100 mA fuses
trips, there is no direct indication of this state. An indirect indication could be to
see if a connected sensor is powered when plugged into either port.
! If the 300 mA fuse trips, upon the automatic reset of the fuse, the ConveyLinx
Module should reboot on its own. However, the ConveyLinx Module may require
the power to be cycled manually to fully restart
Page 28 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
4.7. Over
Over-V
-Voltage
oltage P
Prrotection
There are two sources of potential excess voltage:
Power Supply
The ConveyLinx Module utilizes an SMBJ30A “clamp down” chip on the power input to detect
any voltage coming in that is greater than 33.3V. If this is detected, it shorts the +24V to GND
to protect the remaining electronics on the module. This chip serves a dual function as it also
helps filter ESD voltage spikes as well.
Over
Over-Driven
-Driven Motor
The ConveyLinx Module firmware monitors the motor voltage and if it rises above 30V, it
automatically shunts the motor driver transistors together (the same as in normal braking) so
that the energy is contained within the motor coils and away from the controller electronics.
The inherent nature of motor coil geometry and construction allow for this driven state to be
tolerated for several seconds or even minutes before there is any potential damage to the
motor coil circuit. When the voltage drops below 29V, the ConveyLinx Module firmware allows
the motor power transistors to switch back to their normal operation.
Page 29 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
If you need help finding where LED Items are located on the ConveyLinx Module
Communications
Indicator Item LED State Description
Motors
Indicator Item LED State Description
Page 30 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Sensors
Indicator Item LED State Description
Blinking Green/
Sensor Jam
Amber
Page 31 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Page 32 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Contr
Control
ol P
Ports
orts
Indicator Item LED State Description
Special Cases
Indicator Item LED State Description
All Sensor,
Control Port Flashing Red Module in stopped state
& Motor
Left Sensor,
Left Control ZPA zone on left side of module is in
Flashing Green
Port, & Left Maintenance Mode*
Motor
Right
Sensor,
ZPA zone on right side of module is in
Right Control Flashing Green
Maintenance Mode*
Port, & Right
Motor
Page 33 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
! This document assumes the user is aware of MDR power requirements for the
application and that the user and/or installer have properly sized 24VDC power
supplies and wiring based upon all applicable codes and standards. This
document also assumes installation will follow proper equipment grounding
practices. “DC common or -”on all power supplies should always be connected to
ground. Improper power supply sizing and/or improper grounding practices will
produce unexpected results.
Page 34 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
BOOST
ECO BOOST
8
Duration of motor starting period 5.0 sec 1.5 sec 3.0 sec
* Please note that the current values shown are per Motor Port, so if both Motor
Ports are being used on a given ConveyLinx Module, the current load seen by the
power supply for that module will be double the value shown.
* The current values are at rated speed and at rated torque. The current will be
less if rated torque is not required by the motor.
Page 35 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Power Connector
Power connector is included with the ConveyLinx Module when shipped from the factory
Electrical R
Ratings
atings
Power supply voltage 24.0V +/- 10%
Maximum R
Ratings
atings
Page 36 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
*This is the maximum current that will be allowed by the hardware over current protection
circuitry. On board firmware limits the amount of current based on the quantity and motor
types connected
BDS EN 61000-4-5:2007 Electromagnetic compatibility (EMC) Part 4-5 Surge immunity test.
Page 37 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Inputs
Outputs
Minimum ON current 2 mA
Maximum ON current 8 mA
Page 38 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Pin 5 of all RJ-12 ports provides 24V for powering up a photo-eye or for biasing the output
transistor found on the control port. The current that those pins can supply is limited internally.
Each side of the module is fused separately and each side’s control port and sensor port share
a solid-state fuse rated at 100 mA. For example, If there is one photo-eye plugged into the left
sensor port and one photo-eye plugged in the left control port, then the combined consumption
of the two photo eyes must not exceed 100mA.
! Current in excess of 100mA drawn from the sensor port’s 24V pin may cause
permanent damage to the sensor detection circuit. Care should be taken to avoid
excess loads, short circuits and miss-wiring of the sensor port
Motor P
Port
ort
Supported motor types 3 phase BLDC motors with 3 Hall Effect sensors
! *During normal operation as an MDR port, the internal protection circuitry is not
capable of detecting a short-circuit between a BLDC coil output and ground. Such
a short-circuit will cause damage to the high-side bridge transistors. When
operating these outputs as general purpose outputs, the high-side transistors are
disabled, so a pin-to-ground short-circuit is not an issue
Motor P
Ports
orts in Digital IO Mode as Outputs
Motor Coil P
Pins
ins 3, 4, & 5
In certain modes of operation (PLC I/O and ConveyLogix PLC), Pins 3,4, and 5 can each be
independently switched on and off as general purpose digital outputs. Any individual pin can
Page 39 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
sink up to 1A to gr
ground
ound in these modes, but the total for all 3 pins combined cannot e
exxceed
1.5A
1.5A. In general purpose I/O mode, these pins cannot source current.
Brak
Brake
e Output P
Pin
in 9
As of firmware version 4.19 and later, the brake output pin can be configured through remote
PLC to operate as a general purpose output even if an MDR is connected to the port. This
situation requires a special cable or break-out board to be used and the MDR in use cannot
have and internal mechanical brake, as that mechanical brake requires a connection to pin 9
for proper operation. The brake-output pin 9 is a 24V high side switch (PNP) that can source up
to 0.5A continuously and 1A peak.
Ether
Ethernet
net
• 3 port integrated switch ( 2 external ports and 1 port for the on-board processor)
• Automatic speed setup (10Base-T / 100Base-TX)
• Automatic duplex configuration (Full / Half)
• Automatic straight/crossover cable detection ( Auto MDI/MDI-X)
• PAUSE frame support
• Back pressure flow control support
• Maximum segment length: 100m / 328ft
Supported P
Prrotocols
• Modbus/TCP
• EtherNet/IP
• Profinet IO
• CC-Link IE Field Basic (FW 4.27 and later and ODVA FW 5.07 and later)
Page 40 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
5. Auto
Auto-Configuration
-Configuration
The purpose of Auto
Auto-Configuration
-Configuration for networked ConveyLinx controls is to provide a simple
and easy procedure for linear conveyor system commissioning that does not require a PC or PC
based software to implement. The Auto
Auto-Configuration
-Configuration of Linear Conveyor feature of ConveyLinx
requires only the proper interconnection of each module and the press of a button on the most
upstream module to complete.
Lear
earnn about:
Linear Conveyor
Auto
Auto-Configuration
-Configuration Examples
Auto
Auto-Configuration
-Configuration P
Prrocedur
oceduree
Expected Auto
Auto-Configuration
-Configuration RResults
esults
What to do if things go wr
wrong
ong with Auto
Auto-Configuration
-Configuration
Page 41 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Lear
earnn about:
Page 42 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
* The number of Sensors connected will determine the total number of Zones.
Once Auto
Auto-Configuration
-Configuration is complete, this number of Zones cannot be modified
or over-ridden without performing another Auto
Auto-Configuration
-Configuration P
Prrocedur
oceduree.
2 zone contr
controller
oller
with 2 MDR
MDR’s’s and
2 photo
photo-sensors
-sensors
1 zone contr
controller
oller
with 1 MDR and 1
photo
photo-sensor
-sensor on
Lef
eftt or Right Side
Page 43 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
1 zone contr
controller
oller
with 2 MDR
MDR’s’s and
1 photo
photo-sensor
-sensor
with Sensor on
Lef
eftt or Right Side
Page 44 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
* These examples are not necessarily invalid and will not cause the Auto
Configuration P
Prrocedur
oceduree to fail or abort, but they will result in module errors or
cause interruption in the flow of items on the conveyor.
Page 45 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
5.1.3. Motor R
Rotation
otation Definition
The ConveyLinx Module uses a Clock-W
Clock-Wise
ise (CW) and Counter Clock-W
Clock-Wise
ise ((CCW
CCW)) motor rotation
definition. The reference for this distinction is based upon viewing the MDR from the cable exit
end of the roller.
* Auto Configuration will automatically adjust the motor rotation direction based
upon the flow established by the procedure as long as the cable end of the roller
is on the same side of the conveyor as the ConveyLinx Module. If the rotation
direction is not correct after the Auto
Auto-Configuration
-Configuration P
Prrocedur
oceduree completes, you
can change it in EasyR
EasyRoll
oll. How to change the motor rotation direction
Page 46 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
5.2. Procedur
oceduree
The ConveyLinx Auto
Auto-Configuration
-Configuration P
Prrocedur
oceduree routine will detect which photo-sensors are
connected in order to configure a given ConveyLinx Module as a 1 or 2 zone controller. The
physical order of module connections; from upstream to downstream, dictate the MDR direction
and product flow logic.
Befor
Before
eYYou
ou Begin
• All sensors should be clear. Auto
Auto-Configuration
-Configuration assumes tak
takes
es for granted that the state
of each sensor is the “zone empty” state so that the module can auto-learn the block/
clear states for both retro-reflective and diffuse type sensors
• Make sure you have no more than 221 ConveyLinx Modules connected. Auto Auto--
Configuration will not configure past 221 ConveyLinx Modules in one network
• Make sure that there are no other Ethernet devices or switches connected in your string
of ConveyLinx Modules. After Auto
Auto-Configuration
-Configuration is complete and successful, you can
interrupt the Ethernet string with other devices and/or switches as needed.
The direction of flow of the conveyor dictates where to begin the Auto
Auto-Configuration
-Configuration P
Prrocedur
oceduree.
The ConveyLinx Module located at the most upstream or in-feed end of the conveyor is the
module where the procedure must be initiated.. Because of its physical location on the
conveyor path and physical location in the Ethernet connection chain; the most upstream
Page 47 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
ConveyLinx Module will automatically connect to all downstream ConveyLinx Modules and set
their I.P. address for communication. Then the routine automatically sets the direction of flow.
Auto
Auto-Configuration
-Configuration P
Prrocedur
oceduree
1. Press and hold INSTALL button on the most upstream/in-feed end ConveyLinx Module and
keep it held for 5 seconds
2. After 5 seconds the Module Status LED will flash RED
3. Once Module Status LED begins flashing RED, the INSTALL button must be released within
2 seconds. If held for longer than 2 seconds; the procedure is cancelled
4. Once the INSTALL button has been released within the 2 second time window, the
ConveyLinx Module will be initiated as most upstream module and the Auto-Configuration
Procedure routine will begin.
5. Observe that all of the LED’s (with the exception of the Left Link and Right Link LEDs) will
flash on and off RED on all the ConveyLinx Modules in the network string
Page 48 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
https://www.youtube.com/embed/XDJkC8jpZIM?rel=0
! In order for the Auto-Configuration to work properly, all loads, totes, product,
containers, cartons, etc. must be removed from the entire conveyor path and all
photo-sensors must be aligned and adjusted so that none are detecting that their
respective zone is occupied. Failure to meet these conditions will produce
unexpected results.
* Please note that once a network has been configured; pressing and holding the
Install button on any module that has neighboring ConveyLinx Modules on both
sides of it will not initiate a new Auto-Configuration Procedure. The module will
detect that it is not the most upstream unit and abort the procedure. However,
the ConveyLinx Module will perform its local re-booting procedure. This
procedure will take a few seconds to complete
! Please note that pressing and holding the Install button on the most
DOWNSTREAM ConveyLinx Module WILL initiate a new Auto-Configuration
Procedure and attempt to establish the flow in the opposite direction
Page 49 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
5.3. Auto
Auto-Configuration
-Configuration Examples
* Please note that the Flow is based upon the Ethernet cable routing during the
Auto
Auto-Configur
-Configure
ePPrrocedur
oceduree. The Flow direction cannot be changed or over-ridden.
The only way to change the Flow direction is to perform another Auto
Auto--
Configuration P
Prrocedur
oceduree
Lef
eftt to Right
Flow Example
Right to L
Lef
eftt
Flow Example
Lef
eftt to Right
Flow with
Opposite Side
Module Example
Page 50 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
5.4. Expected R
Results
esults
When the Auto
Auto-Configuration
-Configuration P
Prrocedur
oceduree routine is complete, each ConveyLinx Module will
automatically reboot. When a ConveyLinx Module has been successfully configured and
rebooted, its Module and Network Status LEDLED’s
’s will blink on and off green.
How to verif
verifyy success
Conveyor Operation
Place a carton on your empty conveyor so that it blocks the most upstream zone’s sensor. It
should convey all the way to the discharge end and the last most downstream zone should try
to convey it off the end of its zone. If this does not happen, then at the point where the carton
stops, check that module’s motor connection is sound and that the zone’s sensor is properly
aligned. If the sensor was not properly plugged in and powered when the Auto Auto-Configuration
-Configuration
Procedur
oceduree was performed, you will have to perform the procedure again. If the sensor was
powered but is misaligned when the Auto Auto-Configuration
-Configuration PPrrocedur
oceduree was performed, you can
either perform the procedure again or use EasyREasyRoll
oll to change the logical polarity of that
particular sensor.
Page 51 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
flashing on and off red. If this is not the case, then check your Ethernet cables and connections
and power connections.
To verify that all the modules you expected to be configured are in fact configured, with
EasyR
EasyRoll
oll you can connect to your newly configured ConveyLinx Module network and perform a
Discover function. The Discover function will display all modules that it finds and from the list
your most upstream ConveyLinx Module should have the 4th octet of its IP Address as .20 and
you should see each module you configured in the list.
Page 52 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Une
Unexpected
xpected Motor Behavior
• If ConveyLinx Module was previously configured and its motor settings were changed
in EasyRoll including rotation direction, these setting are not changed to default when
a new Auto-Configuration procedure is performed.
• Make sure you have the correct motor type setting in EasyRoll. How to change Motor
Type
• Make sure that there are no motor errors. How to jog motor and look for errors
• Check that all sensors are operational and that all zones are clear then perform
procedure again. How to change block/clear sensor logic without having to perform
another Auto-Configuration
• Check all network and power connections and make sure there is 24V on each
ConveyLinx Module then try the Auto-Configuration procedure again
• Verify that all of the module sensor/motor combinations are valid. Check here to find
out what module set-ups are invalid
• Make sure there are no other Ethernet devices (PC’s, Switches, Scanners, etc.)
connected between any of the module on your network. The Auto-Configuration
procedure aborts when it encounters a non ConveyLinx device along the network path
before reaching the last module. ConveyLinx Module up to that point should be
configured properly but the remaining modules will not.
• When removing a ConveyLinx Module from an existing configured network that is
already operational; be sure to wait 1 or 2 minutes to allow the Ethernet Switches on
the modules to reset their MAC Address ARP table before attempting a new Auto-
Configuration procedure
Page 53 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
If all module and/or Network Status LED’s are blinking green; then to fully verify configuration
is to place a single carton onto the most upstream zone and see that it conveys to the
discharge zone. If it does, then the Auto-Configuration Procedure is successful.
Lear
earnn About:
Singulation R
Release
elease Mode
Fle
Flexx Zone R
Recognition
ecognition
Jam Conditions
Har
Hard-W
d-Wir
ired
ed Interlocks
Automatic Module R Replacement
eplacement
How to R
Reset
eset to F
Factory
actory Defaults
Page 54 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
6.1. Singulation R
Release
elease Mode
Singulation Release is the mode where the ConveyLinx Module requires that its neighboring
downstream zone must be clear before it releases an item.
All 3 Cartons ar
aree accumulated
Carton 1 rreleases
eleases – Cartons 2
and 3 rremain
emain accumulated
Page 55 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
6.2. Fle
Flexx Zone R
Recognition
ecognition
ConveyLinx Modules will automatically detect that a given carton is longer than one zone
length and automatically adjust accumulation control so that the longer carton occupies two
logical zones and will keep the next upstream carton from conveying into the longer carton.
All 3 Cartons ar
aree accumulated and the Zone at PE3 has Fle
Flexx Zone enabled
Carton 1 R
Releases
eleases – Even though PE3 is clear, because it has Fle
Flexx Zone enabled, Carton 2 rremains
emains
accumulated
Page 56 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
! Please note that Flex Zone mode operates for carton lengths up to 2 zone
lengths only. Operating conveyor system with cartons whose lengths are in
excess of 2 zone lengths may produce undesirable results such as excessive
detected jam conditions and faults.
Page 57 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Sensor Jam
Ar
Arrival
rival Jam
* Both of these Jam conditions utilize a single Jam Timer that has to expire in order
for the condition to be active. Once either of these jam conditions becomes
active; they will automatically clear in the logic after the Auto Clear Time has
expired. Both the Jam Time and Auto Clear Time values are 5 seconds each by
default. Please see How to Change Jam and Auto Clear Timers
Page 58 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
6.3.1. Ar
Arrival
rival Jam
When a carton leaves an upstream zone and is conveyed to its next downstream zone, this
upstream zone expects positive confirmation of carton arrival from the downstream zone. This
communication occurs automatically along the ConveyLinx network. If a new carton arrives at
this upstream zone while this upstream zone is waiting for a downstream arrival confirmation,
the new carton will accumulate on this upstream zone. If the upstream zone does not receive
this confirmation within the Jam T
Timer
imer interval, the ConveyLinx Module will produce an Ar
Arrival
rival
Jam fault. Once an Arrival Jam occurs, the ConveyLinx Module will automatically hold any new
carton at the upstream zone for a pre-determined Auto Clear T Time
ime Timer value and then
resume normal ZPA function. By default, the Jam T Timer
imer and the Auto Clear Timer values are set
to 5 seconds for each. This condition will be indicated on the corresponding Sensor LED on the
module
Page 59 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Page 60 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Her
Here
e is what happens when Sensor Jam Auto Clear pr
procedur
ocedure
e occurs
1. Run the zone motor in reverse until the sensor is clear or 1 second has elapsed,
whichever happens first
2. Wait for the Auto Clear Timer to expire
3. Run the zone motor forward to attempt discharge to the downstream zone (Attempt
#1 complete)
4. If sensor is still blocked after discharge attempt, the zone motor runs in reverse until
Page 61 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
* If item is still blocking the sensor after Sensor Jam Auto Clear procedure is
complete you have to physically clear the jam by removing the item or you can
attempt another Auto Clear procedure
* The 5 second Jam Timer and Auto Clear Timer values are default settings. How to
change Jam and Auto Clear Timers in EasyRoll
Page 62 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
6.4. Har
Hard-W
d-Wir
ired
ed Interlocks
Once your linear conveyor has been Auto-Configured and running in ZPA mode; the ConveyLinx
Modules will attempt to convey all items from upstream to downstream in the direction of flow.
The next logical step that you will want to do is Interlock with the most upstream and/or
downstream zones and perhaps interrupt flow in a zone somewhere in the middle.
Contr
Control
ol P
Ports
orts P
Prrovide Interlock F
Function
unction
! Wak
akee Up interlock should only be used on the MOST Upstr
Full interlock should only be used on then MOST Downstr
Downstream
eam zone and the Lane
Upstream
eam zone of any given
subnet.
Lear
earnn About:
Upstr
Upstream
eam Interlock (W
(Wak
akee Up)
Downstr
Downstream
eam Interlock (Lane F Full)
ull)
Local Zone A Accumulate
ccumulate
Interlocks with a Single Zone Module
Interlock Input versus LLocal
ocal A
Accumulate
ccumulate Input
Using a Photoeye for W Wak
ake
e Up
Using a Photoeye for Lane F Full
ull
SE-4 Br
Break
eakout
out Module
Page 63 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
6.4.1. Upstr
Upstream
eam Interlock (W
(Wak
ake
e Up)
Interlock with the most upstream zone to get an input to see if is clear and then turn on an
output (Wak
akee Up) to tell it to run to accept a new item
! For an Upstream Side Control Port the motor will continue to run as long as the
signal is being applied to Pin 4 and the zone sensor remains unblocked. If the
signal is removed, the zone will continue to run for Jam Timer setting (5 seconds
by default) and then stop
Page 64 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Wak
ake
e Up Interlock with Handshak
Handshake
e
Upstr
Upstream
eam Contr
Control
ol P
Port
ort Output is OFF
and PLC signal to Upstr
Upstream
eam Contr
Control
ol
Port P
Pin
in 4 is OFF
OFF.. When Carton 1
reaches PLC connected PEx, the PLC
ener
energizes
gizes its output signal to
Upstr
Upstream
eam Contr
Control
ol P
Port
ort P
Pin
in 4 and
Zone 1 Motor starts to run
Page 65 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Page 66 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
6.4.2. Downstr
Downstream
eam Interlock (Lane F
Full)
ull)
Interlock with the most downstream zone to turn on an output tell it to stop when something shows
up (Lane F
Full
ull) and then get an input to see if the last downstream zone is occupied
On a newly Auto-Configured linear conveyor without any intervention from external signals, if
an item is on the conveyor, it will convey to the last downstream zone and try to continue on.
Whichever Control Port (Left or Right) is on the Downstream Side of the ConveyLinx Module will
accept a Lane F
Full
ull signal input on its interlock input Pin 4. When a digital signal is applied to Pin
4, the zone will still run its motor to accept an item but it will stop and accumulate when the
item reaches the sensor.
Page 67 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
* When Pin 4 is used on a Downstream Control Port the cycling off and on of this
signal generates an “Arrival” in the module logic and thus prevents an Arrival
Jam
* How to add Lane Full to the most Downstream zone with a single sensor
Page 68 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
! If you re-energize the Pin 3 signal while the item is in transit and still blocking
the zone sensor, the item will stop and if left like this, the zone will eventually
generate an Arrival Jam. You can modify the function of the Pin 3 operation by
making it active only upon leading edge of the zone sensor
Page 69 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Page 70 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Page 71 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Suppose you want to control the release of multiple items by toggling the Pin 3 signal. After
you release the first one, you will get an Arrival Jam because the module is looking for the Pin 4
signal to be energized in order to “confirm the downstream arrival” of the item. So, by using
Pin 3 in this case, you will have to wait the Jam Time plus the Auto Clear Time between release
of each item.
Page 72 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Downstr
Downstream
eam Contr
Control
ol Port Pin 3 is ON
Port
and Carton 1 accumulates when it
ar
arrives
rives
Page 73 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Because standar
standardd RJ
RJ-11/12
-11/12
Sensors put their block
blocked/
ed/
clear output on P
Pin
in 4; this
type of Sensor can be
plugged into the Upstr
Upstream
eam
Contr
Controlol P
Port
ort and pr
provide
ovide
the P
Pin
in 4 WWak
akee Up signal
* If you do not have a Sensor with RJ-11/12 connector; you can use an SE-4 module
to wire you sensor to the Control Port
* By default, your Sensor has to energize its output when it is blocked. You can
change Pin 4 to accommodate a Sensor that de-energizes its output when it is
blocked
! If your sensor has an Error or Health Output signal, you need to cut the signal
wire for this on the RJ-12 connector in order to keep this signal from
inadvertently energizing Pin 3
Page 74 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Because standar
standard
d RJ
RJ-11/12
-11/12
Sensors put their block
blocked/
ed/
clear output on PPin
in 4; this
type of Sensor can be
plugged into the
Downstr
Downstreameam Contr
Control
ol P
Port
ort
and pr
provide
ovide the P
Pin
in 4 Lane
Full signal.
* If you do not have a Sensor with RJ-11/12 connector; you can use an SE module
to wire you sensor to the Control Port
* Block and Clear Timer function for the Lane Full Sensor
* By default, your Sensor has to energize its output when it is blocked to make
Lane F
Full
ull operate. You can change Pin 4 to accommodate a Sensor that de-
energizes its output when it is blocked
Page 75 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
! If your sensor has an Error or Health Output signal, you need to cut the signal
wire for this on the RJ-12 connector in order to keep this signal from
inadvertently energizing Pin 3
Page 76 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
6.4.8. SE Br
Break
eakout
out Module
The SE breakout module provides convenient wiring terminals for access to Pin 3 and Pin 4
inputs as well as the Control Port’s output. SE Inputs (Pin 3 and Pin 4) are PNP-NPN auto-
sensing so you can use sourcing or sinking PLC output modules. The terminals P3 and P4 on the
SE-4 correspond to Pin 3 and Pin 4 respectively
PLC Sour
Sourcing
cing Output to P3 or P4
Page 77 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
! Please note that the Control Port output (OUT) signal on the SE is always PNP and
is subject to the power limitations of the module’s internal fusing
Page 78 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Page 79 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Module Auto R
Replacement
eplacement P
Prrocedur
oceduree
2. Connect new module’s motor(s), sensor(s), hardware, and network connections only.
DO NOT CONNECT POWER YET.
3. Press and hold INSTALL button. While holding the INSTALL button pressed; connect
module power.
4. Observe the Module Status LED. About 1 second after applying power; the Module
Status LED will start blinking red. DO NOT RELEASE THE INSTALL BUTTON YET. After
another second, you will see that the Module Status LED will start to blink both RED
and GREEN. This is the indication that the Auto Replace Procedure is starting and you
MUST release the Install Button NOW. Releasing the Install Button before you see the
Module Status LED flashing both red and green will result in cancelling the Auto
Replace Procedure.
Page 80 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
6. Wait for at least 3 minutes before using the system or cycling power or plugging or
unplugging any Ethernet connections. The module being replaced will automatically
upgrade or downgrade its firmware if needed and restore its configuration settings.
This will involve multiple automatic restarts of the module. Do NOT cycle power to the
module during this 3-minute period.
7. When both the Module Status and Network LED’s are blinking green, then the module
replacement has been a success.
! Once the Auto Replacement procedure has started; if power is lost on the
replacing module, it may become inoperable. In this case, you may need to reset
it back to factory default settings before attempting to use it as a replacement
module. If it does not return to factory default settings, you may need to return it
to PULSEROLLER to be repaired. How to reset a module back to factory default
settings
Page 81 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
6.6. Reset to F
Factory
actory Default Settings
There may be instances when you want to return a ConveyLinx Module to its “factory default”
state. The procedure to do this is the following:
1. Unplug all sensors, devices, motors, and network cables such that the only thing
connected is power
2. Press and hold the Install Button until the Module LED begins to flash
3. When the Module Status and Network Status LEDs both blink green, the procedure is
complete
! If the module you wish to reset was installed in a subnet that was subsequently
Locked from EasyRoll; then this module must first be Unlocked using EasyRoll
before you can perform the procedure to reset to factory default setting.
IP: 192.168.202.20
Senergy ECO
Normal Braking
Closed Loop
CW Direction
50 Pulses Deceleration
Page 82 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Page 83 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
7. SE Br
Break
eakout
out Module
The SE Br
Break
eakout
out Module is used to provide convenient screw terminal wiring access to the
RJ-12 ports (Sensor and Control) on the ConveyLinx Module. The SE BrBreak
eakout
out Module utilizes an
RJ-12 to RJ-12 interface cable to connect to the ConveyLinx Module.
Additional F
Functionality
unctionality
Blocking Diodes
In addition to providing simple wiring connectivity to the ConveyLinx Module RJ-12 pins, the SE
Page 84 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Breakout Module also provides blocking diodes for both the Local Zone Accumulate input signal
(Pin 3) and the Interlock input signal (Pin 4). The SE module’s diodes are equipped with user
settable jumpers to allow configurations for both sourcing and sinking solid state PLC output
modules.
The SE Breakout Module also includes an amplifier for the Control Port’s output circuit (Pin 1
and Pin 6) to allow up to 100mA of current load. This feature will allow the Control Port output
to drive a small inductive load such as a relay coil as well as a PLC input. Because of current
restrictions on each pair of Sensor and Control Ports, you can optionally connect an external
+24V power source to the “+24V” terminal on the SE Breakout Module to provide power to
connected devices. The SE Module’s output can accommodate up to 500 mA with this external
power. The SE Module also contains circuitry to prevent a connected external power source
from back-feeding into the ConveyLinx Module’s power bus.
Page 85 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
! If using optional external power supply, this external supply’s DC common MUST
be connected to ERSC power supply DC common
Page 86 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Page 87 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
* Please note that NOT ALL PLC SOLID STATE OUTPUTS present this behavior.
! For relay or dry contact signals to the P3/P4 inputs, leave both jumpers installed
Both the P3 and P4 inputs on the SE Breakout Module has a pair of user removable jumpers to
allow configuration to block a ground path when connecting a PNP input signal and to block a
voltage when connecting an NPN input signal.
Page 88 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
* Please note that if both jumpers remain installed, the ERSC Module will auto
detect PNP/NPN operation and there will be no protection from reverse current
path from Solid State devices
! At least one jumper MUST remain installed. If BOTH jumpers are removed then
there will be NO SIGNAL (PNP nor NPN) connected to the ERSC
Examples
Page 89 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
* PCB revisions greater than SE-4 are functionally equivalent to the SE-4 part
number. As of the date of this publication the current PCB revision is SE-6. This
Page 90 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Revision History
In order to support previous revisions to the SE Breakout Module, the following items describe
the functionality and possible limitations of each revision.
Original design providing bias diodes for the Pin 3 and Pin 4 inputs to allow solid state PLC
output modules to operate without inadvertently triggering the PNP/NPN auto detect feature of
the ERSC. This design also provided the Control Port Output amplifier to allow higher current
devices to be connected to this output. The OUT signal is PNP only.
! Because the Control Port Output is in an indeterminate state upon ERSC boot up;
the OUT signal could possibly momentarily energize upon initial power up or re-
boot of the ERSC. Users must take proper care when using the OUT signal in their
control system logic.
! The 24V terminal on the ERSC-SE2 is directly connected to the ERSC’s Control
port power. If users connect an external power source to the 24V terminal on the
SE2; this will back-feed power into the ERSC. If this is done, when the main
power to the ERSC is disconnected; the ERSC could still power up. User must
take care to not connect external power source to the 24V terminal.
This version contains a modification to block the OUT signal from energizing during the ERSC’s
initial power-up or re-boot sequence. Thus, users no longer have to worry about an inadvertent
OUT signal being energized during initialization or reboot of the ERSC. For convenience; an LED
has been added that illuminates when the OUT signal is being energized.
! The 24V terminal on the ERSC-SE3 is directly connected to the ERSC’s Control
port power. If users connect an external power source to the 24V terminal on the
SE3; this will back-feed power into the ERSC. If this is done, when the main
power to the ERSC is disconnected; the ERSC could still power up. User must
take care to not connect external power source to the 24V terminal.
Page 91 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
This version contains a diode circuit that blocks an external power source from back-feeding
into the ERSC’s Control Port power. Users can now provide external power for devices
connected to the Control Port in cases where these device’s power requirements exceed the
maximum limits of the port.
Page 92 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
8. EasyR
EasyRoll
oll Sof
Softwar
tware
e
The EasyRoll Software Configuration Tool is a PC based application that provides the ability to
change each module’s default parameters that are otherwise not accessible from the module’s
built-in Auto-Configuration routine.
Lear
earnn About:
Page 93 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
! Please note that some anti-virus and/or security updates block the usage of
WinPcap utility which is used by EasyRoll. It is recommended that when you run
“Setup.exe” that you “Run as Administrator”
Page 94 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
* For the purposes of ConveyLinx; the A A A.BBB.CCC portion of the I.P. address
taken together is defined as the Subnet
is defined as the Node
Node.
Subnet. The DDD value of the address minus 19
For example; if a module has an I.P. address of “192.168.25.20” then its Subnet address is
“192.168.25” and its Node is 1 (i.e. 20-19 = 1)
At the factory, each and every module is assigned an I.P. address that is used by automated
testing equipment and fixtures so that every module is verified prior to shipment. When a
module is taken “out of the box” it will still have this I.P. address stored in its memory.
Page 95 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
An Example
Here is a 4-module network with possible I.P. addresses that could have been on the module
from the factory. Note that their Subnets could be different as well as there could be duplicate
addresses.
* The Auto
Auto-Configuration
-Configuration P
Prrocedur
oceduree will assign Nodes up to and including DDD
octet 240. Therefore, each Subnet is limited to 221 module Nodes
Page 96 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
OR
• If you know the Subnet address of you modules, go to the Main Screen and enter in
Page 97 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
If you know the Subnet address of you modules, set your PC’s IP Address withing the same
subnet and subnet mask as your modules. Then go to the Main Screen and enter in the Subnet
address at the top and click Refresh. If you do not know the Subnet address of your modules,
go to the Advanced Dialog and use the Discover function to view all connected modules to see
which Subnet address you want to connect and set you PC’s IP Address within the same subnet
and subnet mask. Then go to the Main Screen and enter the Subnet address at the top and
click Refresh
Go to the Advanced Dialog and use the Discover function to view all connected modules. You
will need to locate the specific module whose address you want to change. Double click this
module from the list and its information will appear to the right side of the dialog. Enter in the
IP Address and Subnet Mask you want to use and then click the Set button
Page 98 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
* Because the Discover function does not use TCP/IP connections to find
ConveyLinx modules, your PC does not have to have its IP address and subnet
mask set to match any ConveyLinx module IP addresses. However, in order to
eventually connect to any module and make any changes with EasyRoll, you will
need to make sure your PC and the ConveyLinx network you want to connect to
are in the same IP address subnet.
• See the IP address, serial number, and firmware version of each connected module
• Change the IP address and Subnet Mask for any module
• Enable/Disable DHCP server for Auto Configuration Master module
Page 99 of 557
PULSEROLLER ConveyLinx ERSC Complete Guide - 5.1_en
Indicator Description
Network IP – This is where you enter the Subnet of the particular ConveyLinx
network you wish to connect
Node No. – This is where you enter a range of Nodes in which to connect.
Entering values here will cause the “Refresh” button to enable. Clicking this
button will cause the rest of the items (3, 4, and 5) to be populated
Left MDR / Right MDR – Selections for MDR type, speed control, acceleration,
deceleration, etc.
Left MDR / Right MDR – Selector to click to jog the MDR, click again to stop
Left MDR / Right MDR – Visual indicators for various MDR status and
diagnostics information
* Please note that some of the detailed information shown in this figure may be
different for your particular system and that most of these fields will be blank
until you actually initiate communications
* Anywhere on the Main Screen where you see a Set All button next to a
parameter or data entry selection, all the nodes in the range entered in the From
Node # and To Node # will be updated with the same parameter or data entry
selection when you click the associated Set All button. A dialog box will appear
to confirm your selection.
* EasyRoll main screen has a feature identified as “Blink & Wink” that allows you
to visually verify the Node you have selected
! Please note that when Blink & Wink is active, the module stops all motors
8.5.3. ZP
ZPA
A Upstr
Upstream/Downstr
eam/Downstream
eam Zone
Settings
On the main screen there are areas to configure the Upstream and Downstream Zone settings.
The Upstream and Downstream settings are set independent of one another so you can
customize your ZPA functionality based upon your specific needs.
ZP
ZPA
A Release Mode
T-Zone Settings
ZP
ZPAA Er
Errror and Infor
Information
mation
Accumulate Contr
Control
ol fr
from
om
Main Scr
Screen
een
Settings Checkbo
Checkbox
xes
8.5.3.1. ZP
ZPA
ARRelease
elease Mode
* Selecting a new setting from the ZPA Mode drop down box immediately changes
the zone’s mode. If you want to set all Upstream zones for the range of nodes
entered in the Node No. text boxes, then click the Set All button. Similarly, you
can do the same operation in the “Downstream Zone” portion of the main
screen.
* Singulation Release Mode is the default setting and it is described in the Default
Settings and Operation section
* Please note that Singulation and Train Release Modes are configurable per Zone
and can be mixed on the same network
8.5.3.1.1. Singulation R
Release
elease
* Singulation Mode is the default setting and it is described in the Default Settings
and Operation section
8.5.3.1.2. Train R
Release
elease
All 3 Cartons ar
aree
Accumulated
When Carton 1
releases –
Cartons 2 and 3
also rrelease
elease at
the same time
Select Train fr
from
om
the pull-down bobox
x
for T
Train
rain Mode
! Please note that starting many zones in Train Release mode particularly with
heavy loads can cause voltage drops on your power supplies. Be sure to take
care in sizing your power supply needs. You should consider GAP Train Release
Mode if power supply sizing is a concern
8.5.3.1.3. GAP T
Train
rain R
Release
elease
All 3 Cartons ar
areeA
Accumulated
ccumulated
! Please note the GAP time does not create a gap or cause any delay when items
are in transportation. The gap timer is only activated when a given zone
accumulates an item and then it is allowed to release
* If more than one consecutive zone is configured as Gap Train; then each of these
zones will in turn require that their respective gap timers expire. If the time value
is long enough, the result may appear to be Singulation Release mode or even
Singluation Release with extra time delay. 0.2 to 0.3 seconds are typical values
used when you want to help balance the loading on your power supplies but still
have the operation be very close to Train Release Mode
! This example assumes both Module A and Module B are in the same Subnet.
Otherwise you will need to use EasyRoll to establish connections between
Module A and Module B.
8.5.3.3. ZP
ZPA
A Er
Errror and Infor
Information
mation
There is an Er
Errror and Infor
Information
mation area in the upper right corner in both the Upstream and
Downstream Zone areas of the Main Scr Screen
een. There is an indicator that shows if a Jam condition
is active (either Ar
Arrival
rival Jam or Sensor Jam). There is a numerical indicator of all occurrences of
any Jam conditions since the last module power cycle. There is also a Clear button to allow you
to clear a Sensor Jam if it is active.
* The Clear button is a convenience so you do not have to go the zone in question
and remove or otherwise clear the item from the zone sensor. If Sensor Jam Auto
Clear is enabled, clicking the Clear button will re-initiate this procedure.
* When you set Accumulate from EasyRoll, this is saved to the module’s flash
memory so that when you cycle power on the module, it will power up in the
accumulated state.
Disable R
Reset
eset Delays
Disable Sensor Jam Auto Clear
Disable Ar
Arrival
rival T
Timeout
imeout
Disable Manual Operation
Dynamic R Release
elease Contr
Control
ol
8.5.3.5.1. Disable R
Reset
eset Delays
Any individual zone or group of zones can be configured to ignore the Auto Clear Time delay for
either or both of the Arrival Jam and Sensor Jam.
! Selecting either of these options will not eliminate the detection of the particular
jam condition; it simply eliminates the default Auto Clear Time delay the logic
utilizes before automatically clearing the condition.
* You can also attempt to clear a Sensor Jam using the Clear button for the Zone
8.5.3.5.3. Disable Ar
Arrival
rival T
Timeout
imeout
Arrival Jam describes how default zone to zone logic utilizes the Jam Time value for the
discharging zone to wait for the accepting zone to indicate successful arrival of the carton into
the accepting zone. In certain applications for a given zone, you may want to disable this
functionality
Carton accumulated in
Upstr
Upstream
eam Zone by L
Local
ocal
Accumulate signal on P Pin
in 3
or e
exter
xternal
nal network signal
If carton is rremoved
emoved fr
from
om
Upstr
Upstream
eam Zone, the
Downstr
Downstream
eam Zone will run
to “find the missing carton
carton”.
”.
Run time is the duration of
the Jam TTimer
imer setting (5
sec. by default)
8.5.3.5.5. Dynamic R
Release
elease
Some conveyor applications may require that you be able to switch a defined quantity of zones
between singulation and train release modes depending on operational conditions. Dynamic
Release allows you to utilize Contr
Control
ol P
Port
ort signals to remotely perform this switching. There are
two zones that require configuration in order to use Dynamic R Release
elease. The most downstream
zone in the range of zones you wish to control is the Dynamic R Release
elease Contr
Control
ol zone and the
most upstream zone in the range of zones you wish to control is the Dynamic R Release
elease
Ter
ermination
mination zone. The Dynamic R Release
elease Contr
Control
ol zone requires you to energize its Contr
Control
ol P
Port
ort
Pin 3 signal to toggle between release modes. If the default release mode for the range is
Singulation, then energizing Pin 3 will switch the range to Train. If the default release mode is
Train, then energizing Pin 3 will switch the range to Singulation.
5 Zone Dynamic R
Release
elease Example
For our example, we want to dynamically switch Zones A through E between Singulation
Release and Train RRelease
elease modes. All Zone’s default setting in our example is Singulation
Release mode. Zone A will be the Dynamic R Release
elease Contr
Control
ol zone and Zone E will be the
Dynamic RRelease
elease T
Ter
ermination
mination zone. We will wire our signal to Zone A Control Port Pin 3 to to
make this work. When we energize the signal, Zones A thru E will operate in Train Release
Mode and when the signal is de-energized, Zones A thru E will operate in Singulation Release
mode.
Change Motor T
Type
ype
Change Brak
Brake
e Method
Change Speed Contr
Control
ol Method
Change Speed Setting
Change R
Rotation
otation Dir
Direction
ection
Change AAcceleration/
cceleration/
Deceleration
* Please note that the Motor Settings grouped by motor plugged into the physical
Left and Right sides of the module and are not based upon Upstream or
Downstream product flow.
8.5.4.1. Motor T
Type
ype
The Motor TType
ype drop-down box lists all motor brand and types whose profiles are available for
the module. Sener
Senergy
gy ECO is the default setting upon completion of the Auto
Auto-Configuration
-Configuration
Procedur
oceduree. The new settings are downloaded to the selected Node upon selecting a new item
from the list.
Selecting a Motor T
Type
ype from the drop
down box immediately makes the
change for the current Node.
Clicking Set All will download the
selected setting to the Left MDR of
all modules entered in the range of
Nodes at the top of the main screen
in the From Node # / T To
o Node #
boxes. In our example, the From
Node # / TTo
o Node # boxes have the
values of 2 and 6. Changing the
selection in the Motor T Type
ype drop
down will change Node 2 and then
by clicking Set All it will change
Nodes 3 thru 12 to the same setting
as Node 2
! Please consult your particular MDR’s documentation and review your application
if you are unsure as to which motor-type setting to use
8.5.4.2. Brak
Brake
e Method
The Brak
Brake
e Method drop-down box lists all the holding brake methods available for the module.
Nor
Normal
mal is the default setting upon completion of the Auto
Auto-Configuration
-Configuration P
Prrocedur
oceduree. The new
settings are downloaded to the selected Node upon selecting a new item from the list.
Selecting a Brak
Brake
e Method from the
drop down box immediately makes
the change for the current Node.
Clicking Set All will download the
selected setting to the Left MDR of
all modules entered in the range of
Nodes at the top of the main screen
in the From Node # / T To
o Node #
boxes. In our example, the From
Node # / TTo
o Node # boxes have the
values of 2 and 6. Changing the
selection in the Brak
Brake e Method drop
down will change Node 2 and then
by clicking Set All it will change
Nodes 3 thru 12 to the same setting
as Node 2
Method >Description
Once the controls have decelerated the rotor to a stop, the motor coil are internally
connected. The permanent magnet forces in the rotor and the mechanical inertia of the
Nor
Normal
mal gearbox holds the rotor in place. This is the MDR industry standard holding brake
method and is often termed short circuit or shunt. Nor
Normal
mal is the default factory setting
for all module zones from the Auto-Configuration Procedure
Once the controls have decelerated the rotor to a stop, the motor coils are internally
Free
disconnected and only the mechanical gearbox inertia holds the rotor in place
When the controls have decelerated the rotor to a stop, the processor notes the Hall
Servo Effect sensor status. If the Hall Effect sensor status changes indicating a change in
Brak
Brake
e 1 position of the rotor, the controls will inject current into 2 of the 3 motor coils in the
proper sequence to move the rotor back to its original stop position
When the controls have decelerated the rotor to a stop, the processor notes the Hall
Servo Effect sensor status. If the Hall Effect sensor status changes indicating a change in
Brak
Brake
e 2 position of the rotor, the controls will inject current into all 3 of the motor coils in the
proper sequence to move the rotor back to its original stop position
! Servo Brake 1 and 2 are functionally equivalent. Servo Brake 2 utilizes more
power and provides more holding torque. Consequently, because Servo 2 uses
more current, the potential for heat build-up is present depending on your
application. If Servo Brake 1 provides enough holding torque for the application,
it is recommended using it in lieu of Servo Brake 2. Servo Brake 2 should only be
used when Servo Brake 1 does not provide enough holding torque for the
application
Closed L
Loop
oop
Closed LLoop
oop speed control utilizes a proportional – integral (PI) algorithm to regulate MDR
speed. When enabled, the module motor control processor accepts the input from the Hall
Effect sensors to measure rotor speed and will adjust the motor output accordingly to attempt
to regulate speed. The value entered is in percent of the motor’s rated speed. Closed L Loop
oop
speed regulation can be used for applications where you need to maintain constant speed with
varying carton weights. The default setting is for Closed LLoop
oop to be enabled.
* Also note that when Closed Loop is enabled; the units for Acceleration and
Deceleration change from time-based (seconds) to distance-based (pulses).
Motor pulses can be converted to linear distance based upon knowing the
particular speed code of your MDR and its tube diameter. Please refer to Motor
Pulse to Distance Calculation for details and an example of calculating this
distance.
! Closed Loop speed control will provide PWM voltage to the MDR up to the limit of
the particular MDR’s selected profile and/or the current limits allowed by the
module’s built in protection algorithms and circuitry. To avoid unexpected results,
please review your particular mechanical application along with the published
MDR performance data prior to implementing Closed Loop speed control
Open L
Loop
oop
Open LLoop
oop speed control does not utilize any such feedback to regulate speed. The value
entered is the percent PWM waveform (or “throttle”) that is output to the motor and the actual
rotor speed will fluctuate depending on the mechanical loading on the motor
8.5.4.4. Speed
The definition of the Speed setting value depends upon the Speed Contr
Control
ol Method and Motor
Type selected:
Closed L
Loop
oop
Closed L
Loop
oop is the default Speed Contr
Control
ol Method and the value entered is in percent of the
motor rated speed based upon the Motor T Type
ype selected. The ConveyLinx module will adjust the
motor output based upon fluctuating motor loading in order to maintain this set speed.
Open L
Loop
oop
Open LLoop
oop value entered is in % of the selected Motor T
Type’s
ype’s rated Pulse Width Modulation
(PWM) voltage. With this Speed Contr
Control
ol Method, the PWM voltage being fed to the motor
remains constant and the actual measured motor speed will fluctuate depending upon motor
load.
* Please note that if you change the Speed and this module goes through another
Auto Configuration procedure, the Speed setting will not reset back to default. It
will remain unchanged at the last selected setting.
! Please consult your particular motor brand and model’s documentation for
determining the actual speed of the MDR’s for your application. The actual
mechanical speed of the MDR is determined by the mechanical gearing attached
to the motor. All Senergy MDR’s have identical motors but will run at very
different speeds and have very different torque characteristics depending on the
mechanical gearing used.
8.5.4.6. Acceleration/Deceleration
Acceleration and Deceleration settings are fields you enter values similar to Speed. The units of
the value you enter are dependent upon which Speed Contr
Control
ol Method you have selected.
When in Closed L
Loop
oop
In Closed L
Loop
oop, the units shown are Motor P
Pulses
ulses which means the control will accelerate and
decelerate in terms of motor rotor distance based upon Hall Effect sensor state change and the
controller’s current limits and the mechanical limits of the connected drive train. Because the
module does not have any data regarding the gear reduction ratio of the installed MDR, you
will need to work with the Motor Pulse to Distance Calculation to find out the amount of linear
distance the particular acceleration or deceleration will take
When in Open L
Loop
oop
Units shown are seconds which means that the control will accelerate and decelerate for the
time specified within the controller’s current limits and the mechanical limits of the connected
drive train
* Please note that if you change either of the Accel/Decel values and this module
goes through another Auto Configuration procedure, the Accel/Decel settings will
not reset back to default. They will remain unchanged at their last selected
settings.
! Please note that very small deceleration values can cause the module to indicate
a Short Circuit Error. This can happen at speeds greater than 75% and
deceleration values less than 0.1 seconds (in Open Loop) or 50 pulses (in Closed
Loop) with Servo Brake 1 or Servo Brake 2 enabled.
Click the R
Run
un icon to tur
turnn on
the motor
When R Run
un is activated the
icon highlights. Click the
icon again to tur
turnn the motor
off
Er
Errror Indicators
In EasyRoll, the Left and Right motors have their own status indicators on the Main Screen.
These are used to provide visual indication of certain conditions. There are also status
indicators for the Sensors connected to the Left and Right sides of the modules.
Indicators ar
aree Gr
Green
een when
the condition does not eexist
xist
and will be R
Red
ed when the
condition does e exist.
xist.
Indicator Description
Sensor Connection Occurs when the particular side of the module was Auto Configured as a
Error zone and the sensor is unplugged or otherwise not drawing power
Occurs when the sensor health/gain signal on pin 3 of the Sensor port
Sensor Gain Error
changes state from its Auto-Configuration state
Voltage drop [<18V] Occurs if the incoming power to the module drops below 18 volts
Motor short circuit Occurs if the module detects a short circuit condition
Occurs when the motor is commanded to run and the rotor is not
Motor Stalled
turning
Occurs if one or more of the 3 Hall Effect Sensors does not produce a
Motor Sensor Error
signal or does not change state when motor is running
Overvoltage [>30V] Occurs when the incoming power to the module exceeds 30V
8.5.4.8. Motor P
Pulse
ulse to Distance Calculation
For the Senergy motor there are 30 pulses per revolution of the motor shaft. The formula to
calculate the linear distance the roller would turn in one pulse is:
* Roller Diameter and Gear Ratio values for specific roller diameters and speed
codes are found in our Pulseroller Global Motor Roller Technologies Product
Catalog available at www.pulseroller.com
For example, we have a standard Senergy roller with a diameter of 48.6 mm (standard 1.9”
tube) and our speed code is 60. From the chart on page 10 (2019 edition of the Catalog)
indicates that the Gear ratio for a 60-speed code is 11. From this information we plug in the
values into our formula:
For this 60-speed code Senergy roller, when you set the Deceleration in Closed Loop mode to
50 pulses; the roller will decelerate for a distance of:
8.5.5. Diagnostic W
Window
indow
Indicator Description
You can navigate to the next or previous module’s Diagnostic Window by clicking
the + and – buttons
Displays the current ZPA status of the zone and the state of the sensor
Displays the status of the upstream and downstream zones to the selected
module. Note that the values depicted below the text (“00 00” in the example)
indicate the contents of the Tracking Registers. Please refer to ConveyLinx ERSC
PLC Developers Guide for details on how to use the Tracking Registers
Displays the current input voltage to the module as well as the count of the
number of times the power supply went below 18 volts but did not completely
shut off. This is useful for diagnosing possible power supply issues
Displays the current state of each Sensor Port and Control Port input signals
Displays current status of each motor. Please note that this data is also shown on
the main screen as well
Accumulation Status
If a carton is accumulated on a particular zone, the Diagnostic Window will indicate a reason for
the accumulated state. Also note that in situations where an external device (PLC or PC
controller) or the Accumulate icon on the Main Screen has been activated; the Sensor LED on
the module for the stopped carton’s zone will be fast blinking green. You can then consult the
Diagnostic Window for more detailed information on the exact reason
As shown in this e
example,
xample,
for the downstr
downstream
eam zone
on the selected Module, it
shows ““PPin3 Contr
Control
ol P
Port
ort
Accumulation
ccumulation”” as the
reason a carton is stopped
at this zone even though
the zone that is
downstr
downstream
eam of this
module is empty
To invoke the ConveyLinx Advanced Dialog you can do any of the following:
The ConveyLinx
Advanced Dialog
pops up over the
Main scr
screen
een
display and
defaults to show
the Look Ahead &
Timing tab
Look Ahead
Jam & Auto Clear TTimers
imers
Run A
Affter & Induct
Sensor Debounce
Debounce*
A carton is
accumulated
and stopped at
Zone 1 and
another carton is
conveying at
nor
normal
mal set
speed
When carton
reaches end of
Zone 3, Zone 2
will wak
wake
e up and
run at the L
Look
ook
Ahead Speed
Click the checkbox to enable the Look Ahead feature for the selected Node.
Clicking the Set buttons will download the setting to the respective zone on the
selected Node. The value entered for the slowdown speed is in percent of the
Node’s normal speed as set on the main screen. In this example, the Look
Ahead speed will be proportional to 80% of 90% PWM current. If the PWM
speed on the main screen was set to 70% PWM, then the slowdown speed
would be “80% of 70% PWM”. Also note there is a Set All button that will apply
the settings to the range of Nodes entered
Fast R
Release
elease T
Time
ime
The Fast R
Release
elease T
Time
ime option allows you to set a delay before the Look Ahead Slowdown speed
is engaged for the slow-down zone
When Zone 2
wak
wakeses up it will
run at nor
normal
mal
set speed until
the FFast
ast R
Release
elease
Time has
expir
xpired,
ed, then it
will switch to run
at the LLook
ook
Ahead Slowdown
speed
8.6.1.3. Run A
Affter T
Time/Distance
ime/Distance
The Run AAffter time value is used by the logic for normal zone discharge. This is the amount of
time the zone’s MDR will continue run after its photo-sensor has been clear when discharging
to the next downstream zone.
* Please note that Run After does not affect throughput rate. A longer Run After
time will not prevent an upstream item from entering the zone.
Run A
Affter T
Time
ime
Run A
Affter Distance
* See Motor Pulse to Distance Calculation for details on figuring out the distance
traveled
8.6.1.4. Induct F
Forwar
orwarddT
Time/Distance
ime/Distance
Induct F
Forwar
orward
d value is used to cause the MDR to continue to run after the zone’s photo-sensor
has been blocked when receiving a carton from upstream.
Induct F
Forwar
orwarddT
Time
ime
Induct F
Forwar
orwardd Distance
* See Motor Pulse to Distance Calculation for details on figuring out the distance
traveled
8.6.1.5. Induct R
Reverse
everse T
Time/Distance
ime/Distance
* Induct R
Reverse
everse is only applicable for Reversing Control in ZPA Mode
Induct R
Reverse
everse value is used in conjunction with Induct Forward when you are setting up
Reversing Conveyor in ZPA Mode to cause the MDR to continue to run after the zone’s photo-
sensor has been blocked when receiving a carton from upstream with reference to the
“reverse” direction.
* Typically for Reversing Control, the Sensor is mounted in the center of the zone
and the Induct RReverse
everse TTime/Distance
ime/Distance is equal to the Induct F
Forwar
orward
dTTime/
ime/
Distance. These are adjusted separately so you can compensate for situations
when you cannot put the Sensor in the center of the zone
Induct R
Reverse
everse T
Time
ime
Induct R
Reverse
everse Distance
* See Motor Pulse to Distance Calculation for details on figuring out the distance
traveled
The module will detect the leading edge of a carton and hold this state for the
Sensor Debounce time period. Similarly, when the trailing edge of the carton
clears the sensor, the logic holds this state for the Sensor Debounce time
period
This checkbox
should only be
checked on the
module that is the
most upstr
upstream
eam in
a subnet
Practical P
Prrer
erequisites
equisites for R
Reversing
eversing ZP
ZPA
A Contr
Control
ol
• Sensors should be located very close to or in the center of each zone
• Length of all products should be identical or very close to identical
• Induct F
Forwar
orward
d and Induct R
Reverse
everse need to be set
Reversing Contr
Control
ol Example
and indicates which signals on which Control Ports will provide the control. Reversing function
applies to all modules in a subnet will work for any number of zones up to the maximum that
can be included in a single subnet.
* Please note that you can utilize reversing control for a portion of a subnet by
utilizing a remote PLC via the Ethernet network. See how to use a PLC for
reversing ZPA control
Sequence of Operation
Forwar
orwardd Dir
Direction
ection
• All signals are OFF on Downstream Control Port – A of the xxx.xxx.xxx.20 module
• You can use the Upstream Control Port to wake up the most upstream zone
• You can use the Downstream Control Port-B to hold and accumulate the most
downstream zone
Switching to R
Reverse
everse Dir
Direction
ection
Energize Pin 3 on Downstream Control Port-A to cause all zones in the subnet to accumulate
Wait for all zones to stop and accumulate (time value dependent upon zone length and speed –
2 or 3 seconds is typical) Energize Pin 4 on Downstream Control Port-A to logically switch the
direction to Reverse De-energize Pin 3 on the Downstream Control Port-A to remove
accumulation for all zones in subnet to start reversing operation Note that the Upstream
Control Port and Downstream Control Port-B have also reversed their respective functions.
Upstream Control Port now provides the Downstream Interlock (lane full) function and the
Downstream Control Port-B provides the Upstream Interlock (wake-up) function
Switching Back to F
Forwar
orwardd Dir
Direction
ection
Energize Pin 3 on Downstream Control Port-A to cause all zones in the subnet to accumulate
Wait for all zones to stop and accumulate (time value dependent upon zone length and speed –
2 or 3 seconds is typical) De-energize Pin 4 on Downstream Control Port-A to logically switch
the direction to Forward De-energize Pin 3 on the Downstream Control Port-A to remove
accumulation for all zones in subnet to start forward operation
8.6.2. Upgrade T
Tab
ab
The Upgrade tab screen gives access to the module firmware utility. Over time, enhancements
and features may be added to the ConveyLinx family of products. These features and
enhancements are typically made available to customers in the form of firmware upgrade files
that need to be uploaded to your modules. These files are available for download from our
website. Once you have downloaded the desired file, the Upgrade utility allows you to browse
for it and then select a single Node or group of Nodes to upload
* VER
VERYY COOL
COOL:: Please note that if you upgrade firmware, all of each module’s
settings (motors, speeds, ZPA options, etc.) are preserved
* Please note that you typically arrive at the Upgrade tab from the Network
Services tab where you select the modules first and click the Upgrade button
there. That will automatically take you to the Upgrade tab and populate the
Selected Devices list box on the Upgrade tab with your selection from the
Network Services tab
8.6.3. Connections T
Tab
ab
The Connections utility uses EasyRoll to instruct a given module to make a logical connection
to another module that it otherwise would not have made during the Auto-Configuration
Procedure. For applications where you have more than one Subnet, this would be the way to
logically connect the most downstream Node of one Subnet to the most upstream Node of
another Subnet
Connecting T
Two
wo Subnets T
Together
ogether
Here is a typical boundary between two Subnets. The most downstream Node
of the first Subnet has an I.P. address of 192.168.25.34 and the most upstream
Node of the second Subnet has an I.P. address of 192.168.26.20.
! If you have more than one module in a Subnet with a First or Last Flag, or if there
is no First or Last module in the Subnet, your network will not properly preserve
its data for Automatic Module Replacement and the Subnet may have problems
negotiating Ethernet switches and routers for PLC connectivity. You MUST
properly Auto-Configure all Subnets so that these position Flags are correct!
DHCP Server
By default, the most upstream module of every Subnet (I.P. Address xxx.xxx.xxx.20) enables a
simple DHCP server as a convenience so that if your PC is set up to receive an IP address from
the network, your ConveyLinx Subnet will issue one. On larger systems with perhaps multiple
Subnets and/or customer managed network infrastructures, this DHCP server may interfere
with the function of the network. You can disable this DHCP server from the Network Services
tab.
8.6.4.3. Network L
Lock
ock F
Featur
eaturee
The Lock FFeatur
eature
e allows you to “lock” a specific Subnet so that no accidental pressing of the
Install button on any of the modules will inadvertently cause an Auto Configuration Procedure
to be activated.
! Please note that this function applies to all the modules within a selected Subnet
and cannot be activated for an individual module
8.6.4.4. Back
Backup
up and R
Restor
estoree
You have the ability to select a Subnet or all Subnets discovered and generate a Back Backup
up file
that will contain all the parameters and settings for each module included in the selection. This
means all motor settings (speed, acceleration, deceleration, braking, etc.), ZPA settings,
Advanced Dialog settings, etc. are captured in this file that can be saved on your PC.
Conversely you can use this Back
Backup
up file to Restor
estoree settings to a Subnet or all Subnets in the
event settings are inadvertently modified or you simply want to return your modules to a
previously known state
Restor
estoree by IP F
Function
unction
the settings by IP address instead of by module Serial Number. To do this you follow the same
restore procedure as previously shown except you click the Restor
estoree by IP button instead of the
Restore button
Back
Backup
up and R
Restor
estoreeR
Recommendations
ecommendations and T
Tips
ips
Sometimes there are situations where just because a software application will allow you to do
something does not always mean that you should. The BackBackup
up and Restor
estore
e functions in
EasyRoll can fall into this scenario. Even though you can technically create a backup file for a
few or even a single module from within a Subnet of many modules, it is not recommended
that you do so. ConveyLinx support engineer’s experience to date has indicated that when
customers perform Back
Backup
up and Restor
estore
e functions for, at a minimum, all modules in a Subnet
Subnet,
you will have fewer or no problems with your ConveyLinx networks. Systems that were once
working and then start producing unexpected results often stem from performing a Restor
estore
e
function to a small portion of modules instead of the entire Subnet and/or starting with a
backup file that did not include all modules in the Subnet
Subnet. So, here is a list of tips:
Touch & Go
! Touch & Go is only applicable for ZPA mode. Do NOT use Touch & Go with Servo
Braking
* If you are using Firmware 4.27 and later or ODVA Firmware 5.07 and later and
EasyRoll version 4.21 or later; there is a Motor Slave function available on this
screen tab
! The functionality in this topic requires Firmware 4.27 and later or ODVA Firmware
5.07 and later as well as EasyRoll version 4.21 or later
* Motor Slave function automatically adjusts slave motor’s speed and performance
in Closed L
Loop
oop mode to properly assist the master motor
Slave F
Function
unction Selections
Selection Description
Left motor becomes the master and the Right motor becomes the slave. Only the
right is
Left motor’s settings are accessible in EasyRoll and the Right motor will utilize all
slaved to left
the settings made to the Left motor
right is in Identical to right is slaved to left except that when the Left motor runs, the Right
opposite motor runs in the opposite direction of the Left motor. This function is used for
direction Dual Drive MDRs
Right motor becomes the master and the Left motor becomes the slave. Only the
left is slaved
Right motor’s settings are accessible in EasyRoll and the Left motor will utilize all
to right
the settings made to the Right motor
left is in Identical to left is slaved to right except that when the Right motor runs, the Left
opposite motor runs in the opposite direction of the Right motor. This function is used for
direction Dual Drive MDRs
Example
8.6.6. Contr
Control
ol P
Ports
orts T
Tab
ab
The Control Ports tab provides you with the ability modify the function of one or both of the
Control Ports. This tab is organized in the following areas:
8.6.6.1. Contr
Control
ol P
Port
ort Inputs
Each of the two Control Ports on the module has a 2 input signals: Local Accumulation and
Infeed/Discharge Interlock. Each of these inputs has a default logical state (on or off) that
enables the function. The Contr
Control
ol P
Port
ort Inputs area contains check boxes to invert the logical
state of these inputs to accommodate your particular needs. Please note that these checkboxes
are for Lef
eftt and Right ports on the module and not the logical Upstr
Upstream
eam or Downstr
Downstream
eam zones
8.6.6.2. Contr
Control
ol P
Port
ort Outputs
! Control Port outputs are very low power. You need to use an SE Module to
connect your external device.
! Please note that if you select the Motor State option on a module that is an
Extension of another module, the Control Port Output will not energize. The
Motor State output only energizes on the module with the zone that is controlling
the Extension. See the Extensions Tab topic for more details.
8.6.6.3. Upstr
Upstream/Downstr
eam/Downstream
eam
Accumulation
One of the Control Port input signals previously mentioned above is the Local Accumulate
signal (Pin 3 on RJ-12 Control Port or P3 on a SE-4). By default, this signal causes the local zone
to accumulate when its zone sensor is blocked. If this signal is removed when a carton is
blocking the sensor, the carton will discharge to the next downstream zone (if of course it is
clear). While the carton is discharging and still blocking the zone sensor, if the Accumulate
signal is re-energized, the zone will stop.
Accumulate on Sensor T
Trigger
rigger
In situations (like an operator workstation) where you for example want every carton to
accumulate upon its arrival, you would leave the Accumulate signal energized all the time and
then have an operator momentarily de-energize the signal to cause the carton to discharge. In
this situation you probably do not want the operator to have to watch and wait for the carton to
fully discharge from the zone in order for them to re-energize the Accumulate signal so that the
next carton will stop at the zone. The Accumulate on Sensor Trigger checkboxes for the
Upstream and Downstream zones allow you to tell either or both the Upstream or Downstream
zones on the module to remember that the Accumulate signal was momentarily de-energized
so the carton will discharge without any further operator intervention and automatically know
to accumulate the zone upon the arrival of the next carton.
8.6.6.4. Lane F
Full
ull Interface
The Control Ports tab provides selection and adjustment to the Pin 4 Interlock Signal on the
most Downstream zone to provide a Lane F Full
ull Interface that is typical in conveyor applications.
With Lane FFull
ull Interface checkbox checked; the Downstream Interlock will change its default
functionality to ignore the confirmation signal from the downstream controls and thus eliminate
the logical Arrival Jam condition. This will allow the downstream zone to continually release as
long as the sensor signal is OFF (default). This option also allows the user to set a block and
clear time for the Pin 4 signal for added flexibility
* The Lane F
Full
ull Interface Block and Clear Timer capability is designed so you can
plug a Sensor direct into the Control Port
8.6.7. Fle
Flexx Zone T
Tab
ab
The Fle
Flex
x Zone feature is enabled by default when you perform the Auto Configure Procedure.
There can be certain situations such as higher speed applications and/or applications where a
large percentage of cartons are at a length very close to the zone length where a “false
triggering” of a flex zone condition can occur. In these situations, when product needs to
accumulate, you may see several zones unoccupied because of this false triggering. For these
applications where accumulation density is paramount, you can disable Flex Zone to eliminate
this false triggering situation.
! Please note that Flex Zone function has to be enabled or disabled for the entire
Subnet. It cannot be disabled or enabled on a per zone basis or for a group of
zones within the same subnet.
Typically there are one or two driven rollers past the sensor in a Zone. If you
have cartons that encroach upon these rollers when accumulated in the
downstream zone, you may want Fle Flex
x Zone to engage so that the next
upstream carton will not enter the zone (Zone A in the example), thus not
running these rollers underneath the accumulated carton.
* Please note this value has nothing to do with speeding up or slowing down the
actual speed of communications between modules
8.6.8. Sensors T
Tab
ab
The Sensors tab displays the status of how the two sensor signals were configured during the
Auto Configuration Procedure. If for some reason one or more of the sensors was not configured
properly during the Auto Configuration Procedure; for example they were not aligned with their
reflector or there was an obstruction blocking the sensor at the time the procedure was
performed, the Sensors Tab will allow you to change the sensor’s configuration without
requiring you to re-perform the Auto Configuration PPrrocedur
oceduree for the entire subnet. For
example, if all the sensors on the system are light energized normally open then the
corresponding zone’s sensor graphic on this tab will show Off Blocked. Similarly, if the sensor is
equipped with a separate health or low gain signal and this signal is on when there is no error,
the graphic on this tab will show Off Gain Error.
8.6.9. Extensions T
Tab
ab
The Extensions Tab allows you to extend or “slave” single or multiple zones to one “master”
zone. An example situation could be that you have for example certain length zones and on a
given conveyor line there is a need for an extra partial zone that is too short to be a functional
zone that accumulates a carton, but at the same time it is long enough that mechanically you
need to have an MDR in that zone. In this situation you would like to provide a module and an
MDR but no sensor and you want this zone to run its MDR when either its adjacent upstream or
downstream zone is also running. In essence you want to make this partial zone a logical
extension to one of its neighbors.
A common use of the Extension mode configuration available from the Connections tab
selection is for a powered lift gate.
In this example the module on the lifting or gate portion of conveyor has an
MDR and no photo-sensors. Normal operation when the gate is down is for the
MDR on the gate to run when its immediate downstream zone runs so as to
create “one long logical zone”. This means that if a carton is accumulated on
the upstream zone of Node 192.168.26.24; a carton arriving at the downstream
zone of Node 192.168.26.22 will stop and accumulate and no loads will ever be
logically accumulated or stopped on the gate portion. In order to accomplish
this, all we need to do is instruct Node 192.168.26.23 to be an Extension of its
downstream neighbor Node 192.168.26.24
9. ConveyMer
ConveyMerge
ge
ConveyMer
ConveyMerge ge is an optional functionality layer built on top of ConveyLinx’s ZP
ZPAA logic. Users can
enable and configure it using EasyR
EasyRoll
oll software. ConveyMer
ConveyMerge
ge behaves the same as ZPA logic,
but allows you to define a special Mer
Mergege Zone that can have up to three upstream zones
connected to it. ConveyMer
ConveyMerge ge also has simple priority schemes for the multiple upstream zones
as well as the ability to dynamically change those priorities on-the-fly by utilizing the Mer
Merge
ge
Line F
Full
ull option. It also takes care of passing tracking information properly and has Jam
Condition detection.
ConveyMer
ConveyMerge
ge Components
ConveyMer
ConveyMergege can accommodate product merge control from one or two conveyor paths onto a
single take-away conveyor path as shown:
Component Description
Powered conveyor section that accepts an item from any one of the 3
Mer
Merge
ge Zone
possible upstream sources
Part of Center Line that is one of three possible sources of items that can flow
into the Mer
Merge
ge Zone. This term is used in the configuration screen of EasyR
EasyRoll
oll
Center Line
to designate the network that serves as the trunk line that contains the
Mer
Merge
ge Zone
One of the three possible conveyor sections that can discharge items into the
Lef
eftt Line
Mer
Merge
ge Zone
One of the three possible conveyor sections that can discharge items into the
Right Line
Mer
Merge
ge Zone
9.1. ConveyMer
ConveyMerge
ge P
Prrer
erequisites
equisites and
Requir
equirements
ements
Please Note – ConveyMer
ConveyMerge
ge works for ALL ConveyLinx
Family Modules
Module Fir
irmwar
mware
e
The following items are the prerequisites and constraints required to provide a fully functioning
automatic conveyor merge:
• EasyR
EasyRoll
oll version 4.19 or greater
• Only (1) one Mer
Merge
ge Zone is allowed for any given single module
• Mer
Merge
ge Zone cannot have any Extension (slaved) zone
• Mer
Merge
ge Zone must be in ZP ZPA
A mode. Lef
eftt Line discharge, Right Line discharge, and Center
Line discharge can be in either ZPZPA
A mode or PLC I/O mode
• Left, Right, and Center Lines discharges cannot also be included in another instance of
ConveyMer
ConveyMerge ge
* If Lef
eftt Line discharge, Right Line discharge, or Center Line discharge modules are
in PLC I/O mode, you are responsible for programming logic to recognize and
respond to ZPA zone status values between the Mer Merge
ge Zone module for proper
jam free singulation control
9.2. Network Ar
Architectur
chitecture
e
All lines (Center, Lef
eftt, and Right) should be on separate subnets of modules, as shown. Each
subnet should be Auto
Auto-Configur
-Configured
ed separately and then connected together with an Ethernet
switch. Keep in mind that the separate subnets will have to be able to communicate with each
other so special care must be taken when setting up the IP Network Mask before performing
the Auto
Auto-Configuration
-Configuration P Prrocedur
oceduree.
* A good starting point is the default mask of 255.255.128.0. With this setting you
can vary the third octet in the ranges 0-127 and 128-254 and all three lines will
be able to communicate with each other as long as the third octets of their IP
addresses are in the same range (either 0-127 or 128-254).
Ar
Architectur
chitecturee Summary
• The Center Line is a separate subnet of modules that have been Auto
Auto-Configur
-Configured
ed. The
Mer
Mergege Zone and the Dischar
Discharge
ge Zone are part of this subnet. The Center Line can consist
of any number of ConveyLinx Modules and the actual position of the Mer Merging
ging Zone can be
on any ConveyLinx Module within the subnet
• The Dischar
Dischargege Zone has to be the zone immediately downstream of the Mer Merge
ge Zone.
However, the Dischar
Discharge
ge Zone can be on either the same ConveyLinx Module as the MerMerge
ge
Zone or on the adjacent downstream ConveyLinx Module from the Mer Merge
ge Zone’s
ConveyLinx Module
• The Lef
eftt Line is a separate subnet of modules and its most downstream zone has to
physically discharge on to the Mer
Merge
ge Zone
• The Right Line is a separate_* subnet*_ of modules and its most downstream zone has to
physically discharge on to the Mer
Merge
ge Zone
• All three subnets must be connected to a common Ethernet switch only after each subnet
has been Auto
Auto-Configur
-Configured
ed.
90° T
T-Mer
-Merge
ge Sensor Placement
9.4. Mer
Merge
ge Zone Module
Depending on the physical arrangement of actual zones on the Center Line, the Mer
Merge
ge Zone
can be assigned to either the Upstream or Downstream zone of its particular ConveyLinx
Module. It can also be assigned to a ConveyLinx Module that is configured as a single zone ZPA
controller.
Mer
Merge
ge Zone on Upstr
Upstream
eam Zone
Mer
Merge
ge Zone on Downstr
Downstream
eam Zone
9.5. Mer
Merging
ging Lines
The Lef
eftt Line and Right Line are set up in a similar fashion to the Center Line. Each of these
lines are in their own separate subnet that is both different from each other and different from
the Center Line. Regardless of whether these merging lines are an Conventional Spur
arrangement or a 90˚ T-Merge arrangement; the conveyor zone that discharges product onto
the Mer
Mergege Zone must be the most downstream zone if its particular subnet. The following
figures illustrate this for an Conventional Spur Left Line and a 90˚ T-Mer
-Merge
ge Left Line
respectively. The same would apply if these were Right Line examples as well.
9.6. Mer
Merge
ge Configurations
The Mer
Merge
ge Configurations available from within in EasyR
EasyRoll
oll are:
• Lef
eftt Line Only with either Conventional (spur discharge) or T-Mer
-Merge
ge (90˚ discharge)
• Right Line Only with either Conventional (spur discharge) or T-Mer
-Merge
ge (90˚ discharge)
• Both Lefeftt and Right Lines with either Conventional (spur discharge) or T-Mer
-Merge
ge (90˚
discharge) for each
9.7. Mer
Merge
ge P
Priority
riority
EasyR
EasyRoll
oll provides the ability to adjust which of the merging lines receives priority.
EasyR
EasyRoll
oll P
Priority
riority
Description
Selection
The logic monitors the arrival status in each of the zones that discharge in to
the Mer
MergeZone
geZone. The first product that arrives at any of these lines will be
First Come FFirst
irst
allowed to convey into the Mer
MergeZone
geZone. When the MerMergeZone
geZone is clear, the
Served
next line that has had a product arrive will be allowed to convey into the
Mer
MergeZone
geZone
The Center Line will be allowed to release as long as product arrives at the
Center Line’s zone sensor prior to the previously released product having not
cleared the Mer
MergeZone
geZone. When the MerMerge
ge Zone is clear and if there is no
Center Line
product sensed on the center line zone; then the Lef eftt and/or Right Lines will
Priority
be allowed to release if product has arrived at their respective sensors. As
long as no product is arriving on the Center Line, if Lef
eftt and Right Lines are
enabled, these will operate as First Come FFirst
irst Served between them
The Lefeftt Line will be allowed to release as long as product arrives at the Lefeftt
Line’s most downstream sensor prior to the previously released product
having not cleared the Mer MergeZone
geZone. When the Mer Merge
ge Zone is clear and if there
is no product sensed on the Lef eftt Line’s most downstream sensor; then the
Lef
eftt Line P
Priority
riority
Center and/or Right Line will be allowed to release if product has arrived at
their respective sensors. As long as no product is arriving on the Lef eftt Line, if
the Right Line is enabled, the Center and Right will operate as First Come
First Served between them
The Right Line will be allowed to release as long as product arrives at the
Right Line’s most downstream sensor prior to the previously released product
having not cleared the Mer MergeZone
geZone. When the Mer Mergege Zone is clear and if there
is no product sensed on the Right Line’s most downstream sensor; then the
Right Line P
Priority
riority
Center and/or Lef eftt Line will be allowed to release if product has arrived at
their respective sensors. As long as no product is arriving on the Right Line, if
the Lef
eftt Line is enabled, the Center and Lef eftt will operate as First Come FFirst
irst
Served between them
9.8. T-Mer
-Merge
ge Settings
For a T-Mer
-Merge
ge, the discharging conveyor is arranged perpendicular to the Mer
Merge
ge Zone and this
discharging conveyor needs to “throw” the product across the Merge Zone’s rollers. In order to
mitigate carton alignment issues, the logic controls need to make sure that it keeps the Mer
Merge
ge
Zone’s rollers stopped until the discharging conveyor has completely finished “throwing” the
product onto the Mer
Mergege Zone. In order to accommodate various conveyor speeds and material
handling situations; EasyR
EasyRoll
oll provides some timer adjustments to facilitate proper T-Mer
-Merge
ge
functionality.
Accept T
Timeout
imeout
Send T
Timeout
imeout
This timer specifies how much time the discharging zone has to wait after the Mer Merge
ge Zone
sensor is clear before it is allowed to release the next product into the Mer
Merge
ge Zone. This timer
helps ensure that the Mer
Mergege Zone is clear when sensor placement cannot guarantee that the
zone is clear.
EasyR
EasyRoll
oll Selection Description
Specified the amount of time the Monitor Zone must be occupied before the
Monitor Zone’s line will receive priority to release into the Mer
Merge
ge Zone. This
Block T
Timeout
imeout timer starts when the Monitor Zone first becomes accumulated (sensor
blocked and motor stopped) and continues to time as long as the Monitor
Zone stays accumulated
Specified amount of time that the priority release will continue to be active
Clear T
Timeout
imeout once the priority release has begun. When this time value expires, the
priority setting will return to its original EasyR
EasyRoll
oll configured setting
expired
Dynamic P
Priority
riority R
Release
elease Example
Please refer to Figure A and Figure B below. In EasyR EasyRoll oll, Node 2 upstream zone of the Center
Line has been selected as the Mer Mergege Zone and the merge type is Up Left. The EasyR EasyRoll
oll setting
for priority is Center Line P Priority
riority. Also in EasyRoll, the MerMerge
ge Line F Full
ull function has been
enabled as assigned to Node 3 downstream zone of the Lef eftt Line.
With the Mer
Merge
ge Line F Full
ull feature enabled on the Lef eftt Line; once Left Line Node 3 downstream
zone remains accumulated for the Block T Timer’s
imer’s timeout (Figure A); priority will dynamically
change to the Lef eftt Line. This Left Line priority will remain in effect until the Clear T Timer’s
imer’s
timeout has expired (Figure B). When this occurs, the priority will automatically revert to the
EasyR
EasyRoll
oll configured priority (Center Line in this example).
Item Description
Display of IP Address for the ConveyLinx Module selected that will contain the Mer
Merge
ge
Zone
User button to cancel any changes made and close the screen
IP Address of the ConveyLinx Module that contains the zone being defined as the
Monitor Zone for the Mer
Merge
ge Line F
Full
ull function
Radio buttons to select whether the upstream or downstream zone of the ConveyLinx
Module identified in Item 9 will be used as the Monitor Zone
Field to enter the IP Address of the Right Line’s most downstream ConveyLinx Module
Graphical representation of the merge. Please note this will update and change as
settings and configuration is modified
Mer
Merge
ge Line F
Full
ull Block T
Timer
imer preset value
Mer
Merge
ge Line F
Full
ull Clear T
Timer
imer preset value
T-Mer
-Merge
ge A
Accept
ccept T
Timer
imer preset value
T-Mer
-Merge
ge Send T
Timer
imer preset value
The Mer
Merge
ge Zone is the upstream zone of the module at 192.168.25.28 and the most
downstream ConveyLinx Module for the Lef eftt Line is at 192.168.24.31. Here is the ConveyMer
ConveyMerge
ge
Configuration Scr
Screen
een with these values entered
The last step is to click the Apply button to send the changes to the affected ConveyLinx
Modules
* Please note that after clicking the “Apply” button, if the configuration has
changed, the affected modules will reboot. It will take a few seconds for the
reboot to finish and some or all of the affected zones may briefly run their
motors
9.12. T-Mer
-Merge
ge Example
In this example we are going to configure the Right Line to be a T-Mer
-Merge
ge onto the Center Line
and we will set the Mer
Merge
ge P
Priority
riority to be First Come F
First
irst Served
The Mer
Merge
ge Zone is the upstream zone of the module at 192.168.25.28 and the most
downstream ConveyLinx Module for the Right Line is at 192.168.26.58. Here is the
ConveyMer
ConveyMerge
ge Configuration Scr
Screen
een with these values entered
9.13. Mer
Merge
ge Line F
Full
ull Example
In this example we have the Lef
eftt Line configured as standard spur angle merge and the Mer
Merge
ge
Priority to be Center Line
The Mer
Merge
ge Zone is the upstream zone of ConveyLinx Module 192.168.25.28 and the Lef eftt Line’s
most downstream node is 192.168.24.31 and we want this line to have the Mer Merge
ge Line F Full
ull
function enabled. On the Lef
eftt Line, we would like for the upstream zone of ConveyLinx Module
192.168.24.25 to be the Merge Line Full function’s Monitor Zone. We would also like that once
the Monitor Zone has been accumulated (or blocked) for 5 seconds, we want the Lef eftt Line to
release for 5 seconds and then return the priority to the Center Line. Here is the ConveyMer
ConveyMerge ge
Configuration Scr
Screen
een with the values entered for this example:
10. ConveyStop
ConveyStop is a ConveyLinx function that establishes a network based means to signal all
ConveyLinx Modules with a Stop Command in order to physically stop their motion and/or
output functions and remain in a stopped state until a separate Start Command network signal
is received to return all connected modules back to their normal function. This is accomplished
by utilizing the built-in Ethernet network that already inter-connects the ConveyLinx control
system
In a similar fashion to how ConveyLinx modules establish logical connections based upon
conveyor flow; ConveyStop, when applied, establishes Stop Gr Group
oup connections between
modules such that only modules within a given Stop Gr Group
oup are affected by STOP and START
network commands. With ConveyStop, any given system can be segregated into as many Stop
Gr
Groups
oups as desired as long as all modules within a Stop Gr
Group
oup are physically connected over
Ethernet.
Each Stop Gr
Group
oup is independent in that a Stop Command or Start Command occurring in one
Stop Gr
Group
oup does not affect the modules in another Stop Gr
Group
oup even if they are on the same
Ethernet network. In fact, modules within the same subnet that have logical conveyor flow
connections can be in different Stop Gr
Groups
oups. This means that a ConveyLinx-ERSC module in a
non-stopped Stop Gr
Group
oup will automatically detect if it is discharging into a stopped Stop Gr
Group
oup
and automatically inhibit product flow.
Provides Mor
MoreeR
Reliable
eliable R
Recovery
ecovery
When any Stop Command is initiated in an ERSC module, not only is all motor commutation
stopped, but the ERSC retains pertinent data on its status at the time the Stop Command was
initiated. The ERSC will remember that it was discharging or accepting a package along with
the packages tracking data. Upon getting a Start Command, the ERSC will pick up where it left
off and attempt to finish what it was doing prior to the Stop Command.
This same scenario applies to situations when power is disconnected to all modules within a
Stop Gr
Group
oup. As part of the power loss procedure in all ERSC modules with ConveyStop enabled;
certain pertinent data regarding module status and package tracking is saved to flash memory
such that upon power-up and subsequent Start Command, each ERSC will attempt to complete
what it was doing at the time of initial power loss.
With all of these variables in play; ConveyStop cannot claim or be advertised as a de facto
“approved” stopping method for all conveyor system stopping situations including an
emergency stop situation. The purpose of this section is to define a recognized standard for
control system stop classifications or categories and describe how ConveyStop can be applied
for each.
It is the responsibility of the integrator of a ConveyLinx equipped system utilizing ConveyStop
to assess all of the aforementioned factors before deeming a ConveyStop generated Stop
Command as being applicable and suited for an emergency stop situation.
NFP
NFPA®
A® 79
The National Fire Protection Association (NFPA®) 79 Electrical Standard for Industrial Machinery
2012 Edition contains accepted definitions for stopping functionality and emergency operations
that are, in general, applicable to the conveyor and material handling industry.
Emer
Emergency
gency Operations
NFPA® 79 section 9.2.5.4 Emergency Operations is as follows:
Stop F
Function
unction
NFPA® 79 section 9.2.2 Stop Functions defines stop functionality as:
This section further defines three (3) Categories for stop functionality:
Category 0 – An uncontr
uncontrolled
olled stop by immediately rremoving
emoving power to the machines actuators
Category 1 – A contr
controlled
olled stop with power to the machine actuators available to achieve the
stop then rremove
emove power when the stop is achieved
Category 2 – A contr
controlled
olled stop with power lef
leftt available to the machine actuators
In general, ConveyStop follows the intent of the Stop Function definition for section 9.2.2. The
manner in which “de-energizing that relevant circuit” it is accomplished differs between the
ERSC and CNIP modules.
Four of the six digital output circuits on the CNIP modules have their control power source
internally wired to a contact relay. When a Stop Command is active, this relay is de-energized
and control power is disconnected. In this state, the digital output circuit is de-energized
regardless of the state of the logical output. This is a common stop circuit design for PLC based
I/O systems.
In situations where a Stop Command is active and control power is maintained to an ERSC, the
de-energizing of the relevant circuit is accomplished by the on board processor. The ERSC
utilizes a single processor and this processor directly controls (among other things) the power
MOSFET transistor gates that commutate the motor. When a Stop Command is active, the
processor places all MOSFET gates in their open or non-conductive state and then by-passes
the task in the processor that produces motor commutation.
Category 2
Both of these categories involve disconnecting power to ConveyLinx modules and either of
these can be implemented on a ConveyLinx system with or without ConveyStop being enabled.
If ConveyStop is implemented, the behavior would essentially be as described in section 0
Power Loss. ERSC modules will retain their state to flash memory as power is being dropped.
When power is restored; each Stop Gr Group
oup affected by the power disconnect will have to receive
a Start Command from either an assigned and enabled button or switch or from a network
source (PLC or PC).
For CNIP modules, each is equipped with separate power terminals. One set of terminals is for
module logic and input bus power and the other set powers only the output bus. In a Category
1 or Category 0 system, the motion producing control power can be disconnected from the
CNIP
CNIP’s
’s output bus while leaving logic and input control power on. This is a typical strategy
applied to PLC I/O systems and can be implemented with CNIP modules with or without
ConveyStop installed and enabled. It must be noted that this strategy requires 2 separate
power systems to be field wired.
Integrator R
Responsibility
esponsibility
By no means is NFPA® 79 the only specification or criteria for defining the stop function of an
automated system. The NFPA® 79 is a general standard for the USA and the descriptions
above are based upon general experience for US installations.
The bottom line is that it is always up to the integrator to understand and adhere to the
applicable specifications, codes, and standards on a per system basis. ConveyStop can be a
valuable tool to achieve desired system stop functionality, enhanced diagnostics, and lower
installed cost.
10.3. ConveyStop Ar
Architectur
chitecturee
The ability to respond to Stop Commands and Start Commands is built in to every ERSC and
CNIP module. The activation of the ConveyStop function requires the ConveyStop PC software
package to first define one or more Stop Gr
Groups
oups of modules and then enable the ConveyStop
functions in these modules. When enabled, the modules create 2 logical network connection
rings within their configured Stop Gr
Group
oup as shown:
These connections create two logical rings. Each module expects to get data and heartbeat
keep-alive messages every 200 ms over both connection rings. If any single module in the
group does not receive data or heartbeat message either of its neighbors; the module will
immediately disable the gates of its MOSFET transistors and sends a message to all other
module over the 2 connection rings to do the same. The disabling of the MOSFET gates
immediately halts any possible commutation and rotation of connected motors.
For ConveyLinx ERSC modules, the ConveyStop Stop Command causes all motor commutation
to immediately stop. For ConveyLinx ConveyNet I/P (CNIP
CNIP)) modules, the _*Stop* Command
causes the CNIP processor to de-energize the output bus relay, thus disconnecting control
power to the affected discrete outputs.
The ConveyStop PC software connects to a ConveyLinx network and shows all available ERSC
and CNIP devices. From this list, the system integrator creates and populates one or more Stop
Gr
Groups
oups. Within each Stop Gr
Group
oup, one or more ERSC’s can be configured to have either its Left
or Right Control Port assigned to contain a hard-wired button or switch to issue a STOP
Command. Similarly, any CNIP module can be similarly assigned a hard-wired button or switch
to a specific dedicated input to issue a STOP Command. Also within each Stop Gr Group
oup, one or
more ERSC’s can be configured to have either its Left or Right Control Port assigned to contain
a hard-wired button or switch to issue a ST
STAR
ART
T Command. Similarly, any CNIP module can be
similarly assigned a hard-wired button or switch to a specific dedicated input to issue a ST
STAR
ARTT
Command.
10.4.1. User A
Accounts
ccounts
Guest
Guest access allows access to ConveyStop software monitoring capabilities only and does not
allow any access to add, delete, or modify any items
Administrator
Only Administrator accounts are allowed to modify any configuration or assignments.
Administrator access is required to:
10.4.2. Cr
Creating
eating a New P
Prroject
Create a new blank project by selecting “New” from the File menu.
After a few seconds depending on the number of devices located, a list of discovered devices
will be displayed in the window on the far left. ConveyStop will also create a graphical image of
its discovery as shown:
10.4.4. Cr
Creating
eating Stop Gr
Groups
oups
In this example, there are 3 subnets – one with 10 ERSC modules, one with 14 ERSC modules,
and one with 2 CNIP modules. We want to create 2 Stop GrGroups
oups – one with the 10 ERSC subnet
and the other one with the 14 ERSC subnet combined with the 2 CNIP subnet.
First Stop Gr
Group
oup
First we use the “Show devices on Subnet” to filter the list for the 10 ERSC subnet. Then we
select all the items in the list as shown:
Then drag the selection into the ConveyStop Groups list window as shown. This creates a Stop
Gr
Group
oup from the selected modules and automatically generates a group name.
Right click on this name to give it as meaningful name for your project. In this example we will
call it “Line A”. You can also expand and collapse the detail of a Stop Gr
Group
oup by clicking the + or
– icon to the left of the group name:
In our example, we want to add a Stop Button to node 8 at address 192.168.26.27 and we want
the button to connect to the Left Control Port. You do this by right clicking on the desired node
and selecting the option from the pop-up menu as shown:
Start Button
In our example we want to add a Start button to the Right Control Port of the same node. Right
click on the node and select the desired option from the pop-up menu as shown:
The process is not complete because we have only configured ConveyStop within the software;
we still need to Commit the functionality to the physical ConveyLinx modules. Clicking the
“Commit All” button sends the current configuration of Stop Gr
Groups
oups, buttons, etc. to the actual
devices. When complete, ConveyStop screen displays the status of the connected devices.
Shown below is what the screen should look like for our example when both Stop Gr Groups
oups are
operational and have no stop conditions active and no stop groups awaiting Start:
Har
Hard-W
d-Wir
ired
ed P
Push-Button
ush-Button
ERSC Module
You can connect Stop Command buttons to either the Left or Right Control Ports on an ERSC in
the Stop Gr
Group
oup. Stop buttons require 2 sets of contacts and connect to the 2 inputs on the
control port. If ANY of these contacts become opened on a given module; it will generate a
STOP Command to ALL modules within the group over the 2 communication rings.
CNIP Module
For the CNIP module, there are dedicated inputs to use to connect a Stop Command button.
See Wiring Examples for details on the inputs reserved for this function
Remote PLC
If a PLC is connected to at least one module in a Stop Gr
Group
oup; it can issue a Stop Command to
that module and all modules within that group will recognize this as a Stop Command. Even if
the PLC is connected to more than one module in a Stop Gr Group
oup, it only has to issue the Stop
Missing Connection
If any single device (ERSC or ConveyNet I/P) is missing from a configured Stop Gr
Group
oup due to for
example unplugged or damaged cable; a Stop Command will be issued to all modules in the
Stop Gr
Group
oup
Missing PLC
If a PLC establishes a structur
structured
ed instance connection to any single device (ERSC or ConveyNet
I/P) within a Stop Gr
Group
oup and that connection is subsequently lost to the PLC, a Stop Command
will be issued to all modules in the Stop Gr
Group
oup
Power L
Loss
oss
If any individual or multiple modules within a Stop Gr
Group
oup has its power disconnected; all
remaining powered modules within that Stop Gr Group
oup will recognize this as a Stop Command
CNIP Indicators
Any powered CNIP modules within a Stop Gr
Group
oup that has an active Stop Command will flash
their Module and Network Status LEDs in Red. All other LEDs will remain unaffected.
PLC Indication
In order for a PLC to be able to either initiate a Stop or Start Command ; it has to establish an
instance connection to at least one ERSC or CNIP within a given Stop GrGroup
oup. Each instance
assembly available for both the ERSC and CNIP provides an input register for ConveyStop
Status and an output register to issue ConveyStop Stop and Start Commands.
If the PLC is connected to multiple ERSC’s or CNIP’s in a given Stop Gr
Group
oup; any connected ERSC
or CNIP can provide ConveyStop status and can accept Stop and Start Commands from the PLC.
10.5.3. ERSC F
Functions
unctions Affected by Stop
Command
Regardless of mode (ZPA, PLC I/O, ConveyLogix program); a Stop Command completely inhibits
any rotation of a motor connected to either Motor Port.
How the module’s digital outputs respond to a Stop Command is dependent upon what mode
the module is in and its settings in EasyR
EasyRoll
oll. When placing a module into PLC I/O Mode from the
Connections tab from the Advanced Dialog; there is a drop down box for the user to select how
to respond when there is a communications loss with the PLC. The choices are to turn off the
outputs of leave them in their last state. This setting also affects how the outputs respond
during a Stop Command
Contr
Control
ol P
Port
ort Outputs
The state of the Control Port digital outputs during a Stop Command depends upon the
following:
The following chart indicates the state of the corresponding Left or Right Control Port digital
output while a Stop Command is Active based upon these factors:
Stop
ERSC Mode Button on Port Output State
Port
Motor P
Ports
orts in Digital I/O Mode
For the Left and Right Motor Ports in Digital Mode, the state of these outputs is determined by
the On PLC Disconnected setting on the Connections Tab in EasyRoll
! WARNING !!! Motor Port in Digital Mode output state upon STOP Command is
determined by On PLC Disconnected setting in EasyRoll and that these outputs
could remain energized during a STOP Command. In any case where output state
is determined by EasyRoll setting; it is up to the Integrator to insure that control
system programming understands that a STOP Command has no effect on these
outputs. It is possible that based upon this setting, any given digital output could
remain energized even though there is STOP Command active.
10.5.4. CNIP F
Functions
unctions Affected by Stop
Command
Upon a Stop Command, the on-board relay is de-energized which in turn disconnects the
control power bus that feeds Outputs O2 through O5. This ensures that Outputs O2 thru O5 de-
energize during a Stop Command regardless of any logic instructing these outputs to remain
energized.
! Outputs O0 and O1 are unaffected by a Stop Command and will still respond to
any logic from either a remote PLC or on-board ConveyLogix program
10.6. ConveyLinx F
Function
unction at Stop Gr
Group
oup
Boundaries
If a given system application utilizes multiple Stop Gr
Groups
oups (or non-ConveyStop configured
modules) that are physically and logically connected such as a conveyor system; ConveyLinx
has built in mechanisms for flow control. If the upstream or in feed end of a Stop Gr
Group
oup is being
fed by the discharge of ConveyLinx controlled conveyor; a Stop Condition will cause the most
upstream module of the Stop GrGroup
oup to indicate to its upstream zone to not allow any item to be
conveyed into the Stop Gr
Group’s
oup’s in feed zone.
Befor
Before
e a Start Command will work you must mak
make
e sur
sure:
e:
• All modules in the Stop Gr
Group
oup must be powered
• All Stop Buttons must be physically reset
• All expected communications between modules must be present
• All expected PLC connections to modules must be present
Har
Hard-W
d-Wir
ired
ed P
Push-Button
ush-Button
ERSC Module
You can connect Start Command buttons to either the Left or Right Control Ports on an ERSC in
the Stop Gr
Group
oup. Start buttons require a single momentary normally open (N.O.) contact. Once
the contact is closed, if all Start Command criteria are met, the Stop Gr
Group
oup will resume its
normal function.
CNIP Module
For the CNIP module, there are dedicated inputs to use to connect a Start Command button.
See Wiring Examples for details on the inputs reserved for this function
Remote PLC
If a PLC is connected to at least one module in a Stop Gr
Group
oup; it can issue a Start Command to
that module and all modules within that group will recognize this as a Start Command. Even if
the PLC is connected to more than one module in a Stop Gr
Group
oup, it only has to issue the Start
Command to only one module in order to Start the whole Stop Gr
Group
oup.
CNIP Indication
There are no active indicators on a CNIP module that ConveyStop has been started. Even for
modules that have a Start Button assigned; there is not default digital output on the module to
indicate a started condition
Ether
Ethernet
net I/P
If a PLC establishes an Ethernet I/P assembly instance connection to at least one ERSC or CNIP
module within a Stop GrGroup
oup, then the ConveyStop control within the Stop GrGroup
oup will expect this
connection to always be present. If this connection is ever lost, then a Stop Condition is
triggered for the Stop Gr
Group
oup. If the PLC has established connections to multiple modules within
a Stop Gr
Group
oup; the loss of connection to any one of these connections will trigger a Stop
Condition for the Stop Gr
Group
oup.
Please Note: ERSC and CNIP modules will also respond to unsolicited MSG instruction requests
from the PLC. This form of communication does not require the ERSC or CNIP to be configured
as a “permanent” Ethernet module on the PLC’s logic Ethernet backplane. If the PLC
establishes communication with an ERSC or CNIP within a Stop Gr Group
oup with a MSG instruction
request; the ConveyStop control does not treat this as an expected connection and does not
generate a Stop Condition for any MSG instruction communication presence or loss.
Modbus TCP
Modbus TCP is a request/response type protocol and each ERSC or CNIP module acts as a
Modbus TCP server and will respond to holding register read/write requests. Holding Register
addresses 4:1000 and above are reserved for assembly instances. If a PLC establishes
communications to at least one module in a Stop Gr Group
oup to read/write to any block of holding
registers at address 4:1000 or above and these read/write communication requests from the
PLC is missing for more than 100 msec; a Stop Condition will be generated.
If a PLC establishes a connection to read/write to Holding Registers whose addresses are in the
range of 4:0001 thru 4:999; a loss of connection for this communication will not result in a Stop
Condition
Profinet I/O
Profinet I/O connection works similarly to Ethernet I/P with ConveyStop. If a PLC establishes a
connection to one or more modules within a Stop Gr Group
oup; then the ConveyStop control within
the Stop Gr
Group
oup will expect all of these connections to always be present. If any one of these
connections is lost, then a Stop Condition is triggered for the Stop Gr
Group
oup
Bit Description
0 thru 4 Reserved
1 = Stop Command issued because Stop Button on local module’s Lef eftt Control Port (or
8 CNIP I0/I1)
0 = Stop button OK on local module’s Left Control Port(or CNIP I0/I1)
1 = Stop Command issued because Stop Button on local module’s Right Control Port
9 (or CNIP I0/I1)
0 = Stop button OK on local module’s Left Control Port(or CNIP I0/I1)
11 thru
Reserved
15
Stop Command
Writing a value of “1” to the ConveyStop Command R
Register
egister will cause a Stop Command to be
issued to the STOP Group. In any module (ERSC or CNIP) that is connected to the PLC, bit10 will
be set in their corresponding ConveyStop Status R
Register
egister.
Start Command
Before issuing a Start Command, the PLC should first verify that the ConveyStop Status
Register is “0” indicating there is not an active STOP condition. One of these conditions is
indicated in Bit 10 of the ConveyStop Status R Register
egister. So the procedure for issuing a Start
Command is:
! Please note that you cannot use an indicator light with RJ-12 pigtail cable. You
must use SE Br
Break
eakout
out Module for an indicator light
! Please note that you cannot use an indicator light with RJ-12 pigtail cable. You
must use SE Br
Break
eakout
out Module for an indicator light
Click Links to L
Lear
earn
n Mor
Moree
Network Ar
Architectur
chitecturee
Understanding Assemblies
ZP
ZPA
A Mode Contr
Control
ol
PLC I/O Mode Contr
Control
ol
ConveyL
ConveyLogix
ogix Interface
Assemblies with R Reset
eset P
Prrotection
Motor PPort
ort as Digital I/O
OD
ODVVA Compliant CrCross-R
oss-Refer
eference
ence
11.1. Network Ar
Architectur
chitecture
e
Each ConveyLinx Module communicates to its adjacent modules and to any connected PC or
PLC via Ethernet physical media. ConveyLinx Modules recognize (3) TCP/IP based protocols:
Modbus TCP CP,, P
Prrofinet I/O, and Ether
Ethernet
net I/P. Modbus TCP is the “native” protocol for
communications between ConveyLinx Modules and the EasyR EasyRoll
oll 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. Ether Ethernet
net I/P is recognized by ConveyLinx
Modules and any given ConveyLinx Module can be attached to an Ethernet I/P capable PLC
(Allen-Bradley ControlLogix or CompactLogix platforms) and be recognized as a Generic
Ether
Ethernet
net Module or explicitly as an ConveyLinx Module by using a Pulseroller provided EDS file.
Profinet I/O is recognized by ConveyLinx Modules and can be attached to any Profinet I/O
capable PLC (applicable Siemens platforms) using a Pulseroller provided GSDXML file.
* All protocols access the same internal data locations on a given ConveyLinx
Module.
Each ConveyLinx Module’s internal data structure is arranged and addressed as Modbus
Holding R
Registers
egisters. The on-board communication and control processes attach logical meanings
to each holding register and read and write data to specific registers to initiate and/or react to
events. Certain registers contain information as to how the ConveyLinx Module 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 ConveyLinx
Module has a Carton ready to discharge to its neighboring downstream ConveyLinx Module, the
upstream ConveyLinx Module will write a specific value to a specific address in the downstream
ConveyLinx Module’s internal registers. The downstream ConveyLinx Module’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 ConveyLinx
Modules to monitor and control various points along the conveyor path.
An Assembly is a grouping of some subset of these 512 Module registers based upon the
relevance of the data. For example, the ZPA Input Assembly groups together 21 Module
registers out of the 512 that are relevant for ZPA Inputs. This relevant data from within the
Module’s 512 registers are not necessarily in consecutive address locations and are scattered
throughout the 512 addresses. The Assembly groups them together so they can be read
efficiently all at once.
Properly A
Addr
ddressing
essing Assembly R
Registers
egisters
In the ConveyLinx Module, the Assembly Registers are “virtual” in that they are not “physical”
Module Register Addresses and as such are not directly addressable. The ConveyLinx Module
firmware intercepts the request and builds the assembly data in order to transmit it to the
requesting device. Because of this, you must always address an Assembly by using the first
address in the assembly in order for the ConveyLinx Module to return any data.
! 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 ConveyLinx
Module 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 ConveyLinx Module will return an error
11.2.2. Ether
Ethernet
net I/P Assembly Instance
Structur
Structuree
When an ConveyLinx Module 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 Pulseroller.
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:
:O
:O.Data[Inde
.Data[Index].Bit
x].Bit
:I.Data[Inde
:I.Data[Index].Bit
x].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
11.2.4. Assembly R
Register
egister Chart L
Legend
egend
All of the Assemblies are organized in charts that show:
The Assembled Addresses are shown in specific notation familiar to the specific protocol per
the following examples:
Indicates P
Prrofinet I/O addr
addressing
essing notation for P
Prrofinet IO memory
P: Byte 0 (Hi) Byte 1 (L
(Lo)
o)
location offset
11.3. ZP
ZPA
A Mode Contr
Control
ol
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
* 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
Assembled
Name /
Addr
ddress
ess for Links
Module
PLC
Addr
ddress
ess
M: 4:1500
Local Status E: I.Data[0]
Upstream P: Byte 0
Local Zone Status
Zone (Hi)
4:0116 Byte 1
(L
(Lo)
o)
M: 4:1501
Local Status E: I.Data[1]
Downstream P: Byte 2
Local Zone Status
Zone (Hi)
4:0196 Byte 3
(L
(Lo)
o)
M: 4:1502
Arrival Count
E: I.Data[2]
Local
P: Byte 4 Ar
Arrival/Departur
rival/Departure
e
Upstream
(Hi) Counts
Zone
Byte 5
4:0106
(L
(Lo)
o)
M: 4:1503
Departure
E: I.Data[3]
Count Local
P: Byte 6 Ar
Arrival/Departur
rival/Departure
e
Upstream
(Hi) Counts
Zone
Byte 7
4:0107
(L
(Lo)
o)
M: 4:1504
Arrival Count
E: I.Data[4]
Local
P: Byte 8 Ar
Arrival/Departur
rival/Departure
e
Downstream
(Hi) Counts
Zone
Byte 9
4:0186
(L
(Lo)
o)
M: 4:1505
Departure
E: I.Data[5]
Count Local
P: Byte 10 Ar
Arrival/Departur
rival/Departure
e
Downstream
(Hi) Counts
Zone
Byte 11
4:0187
(L
(Lo)
o)
M: 4:1506
Module E: I.Data[6]
Status Word P: Byte 12
Module Status
1 (Hi)
4:0088 Byte 13
(L
(Lo)
o)
M: 4:1507
Module E: I.Data[7]
Status Word P: Byte 14
Module Status
2 (Hi)
4:0089 Byte 15
(L
(Lo)
o)
Current M: 4:1508
Upstream E: I.Data[8]
Zone P: Byte 16 Tracking and
Tracking (Hi) Release Counts
Word 1 Byte 17
4:0119 (L
(Lo)
o)
Current M: 4:1509
Upstream E: I.Data[9]
Zone P: Byte 18 Tracking and
Tracking (Hi) Release Counts
Word 2 Byte 19
4:0120 (L
(Lo)
o)
Current M: 4:1510
Downstream E: I.Data[10]
Zone P: Byte 20 Tracking and
Tracking (Hi) Release Counts
Word 1 Byte 21
4:0199 (L
(Lo)
o)
Current M: 4:1511
Downstream E: I.Data[11] Tracking and
Zone P: Byte 22 Release Counts
Tracking (Hi)
Word 2 Byte 23
4:0200 (L
(Lo)
o)
Current M: 4:1512
Release E: I.Data[12]
Count for P: Byte 24 Tracking and
Upstream (Hi) Release Counts
Zone Byte 25
4:0105 (L
(Lo)
o)
Current M: 4:1513
Release E: I.Data[13]
Count for P: Byte 26 Tracking and
Downstream (Hi) Release Counts
Zone Byte 27
4:0185 (L
(Lo)
o)
M: 4:1514
Get Tracking
E: I.Data[14]
Forward
P: Byte 28 Forwar
orwardd and
Direction
(Hi) Reverse T
Tracking
racking
Word 1
Byte 29
4:0201
(L
(Lo)
o)
M: 4:1515
Get Tracking
E: I.Data[15]
Forward
P: Byte 30 Forwar
orwardd and
Direction
(Hi) Reverse T
Tracking
racking
Word 2
Byte 31
4:0202
(L
(Lo)
o)
M: 4:1516
Get Tracking
E: I.Data[16]
Reverse
P: Byte 32 Forwar
orwardd and
Direction
(Hi) Reverse T
Tracking
racking
Word 1
Byte 33
4:0121
(L
(Lo)
o)
M: 4:1517
Get Tracking
E: I.Data[17]
Reverse
P: Byte 34 Forwar
orwardd and
Direction
(Hi) Reverse T
Tracking
racking
Word 2
Byte 35
4:0122
(L
(Lo)
o)
P: Byte 36
Inputs (Hi)
Status
4:0035 Byte 37
(L
(Lo)
o)
M: 4:1519
E: I.Data[19]
Reserved P: Byte 38
N/A (Hi)
Byte 39
(L
(Lo)
o)
M: 4:1520
E: I.Data[20]
ConveyStop Port Inputs and
P: Byte 40
Status ConveyStop
(Hi)
4:0019 Status
Byte 41
(L
(Lo)
o)
Local Status
M: 4:1500 (L(Lo
o Byte)
Upstream Zone
E: I.Data [0] (L
(Loo Byte)
Forward Direction
P: Byte 1
4:0116 Unsigned Value of Byte:
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 who also are working with
the entire 16-bit register data 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.
11.3.1.2. Ar
Arrival/Departur
rival/Departure
e Counts
Register Name / Assembled
Description
Module AAddr
ddress
ess Addr
ddress
ess for PLC
selected MDR
bit 10 = Right Motor Short Circuit
bit 11 = Right Motor Not Connected
bit 12 = Right Motor Overload – Motor has been stalled
for more than 20 seconds
bit 13 = Right Motor Stalled – MDR slower than 10% of
selected speed
bit 14 = Right Motor Hall Sensor Error
bit 15 = Right Motor Not Used
Current Release M: 4:1512 Copy of the current value in the Release Upstream output
Count for E: I.Data [12] register which can be used by PLC logic to confirm
Upstream Zone P: Byte 24 (Hi) release count prior to writing new data to the Release
4:0105 Byte 25 (L
(Lo)
o) Upstream output register
Current Release
M: 4:1513 Copy of the current value in the Release Downstream
Count for
E: I.Data [13] output register which can be used by PLC logic to confirm
Downstream
P: Byte 26 (Hi) release count prior to writing new data to the Release
Zone
Byte 27 (L
(Lo)
o) Downstream output register
4:0185
11.3.1.5. Forwar
orwardd and R
Reverse
everse T
Tracking
racking
Register Name / Assembled
Description
Module AAddr
ddress
ess Addr
ddress
ess for PLC
M: 4:1519
E: I.Data [19]
Reserved
P: Byte 38 (Hi)
Byte 39 (L
(Lo)
o)
* 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
Register
Assembled
Name /
Addr
ddress
ess for Links
Module
PLC
Addr
ddress
ess
Accumulation M: 4:1604
Control for E: OO.Data[4]
.Data[4]
Local P: Byte 8 Accumulation
Upstream (Hi) Contr
Control
ol
Zone Byte 9
4:0104 (L
(Lo)
o)
Accumulation M: 4:1605
Control for E: O
O.Data[5]
.Data[5]
Local P: Byte 10 Accumulation
Downstream (Hi) Contr
Control
ol
Zone Byte 11
4:0184 (L
(Lo)
o)
M: 4:1606
E: O
O.Data[6]
.Data[6]
Set Left MDR
P: Byte 12
Speed Speed Contr
Control
ol
(Hi)
4:0040
Byte 13
(L
(Lo)
o)
M: 4:1607
E: O
O.Data[7]
.Data[7]
Set Right
P: Byte 14
MDR Speed Speed Contr
Control
ol
(Hi)
4:0064
Byte 15
(L
(Lo)
o)
Release and
Accumulate M: 4:1608
on Next E: O
O.Data[8]
.Data[8]
Arrival for P: Byte 16 Release and
Local (Hi) Status
Upstream Byte 17
Zone (L
(Lo)
o)
4:0105
Release and
Accumulate M: 4:1609
on Next E: OO.Data[9]
.Data[9]
Arrival for P: Byte 18 Release and
Local (Hi) Status
Downstream Byte 19
Zone (L
(Lo)
o)
4:0185
M: 4:1610
E:
Set Status for
O.Data[10]
Upstream Release and
P: Byte 20
Induct Status
(Hi)
4:0134
Byte 21
(L
(Lo)
o)
M: 4:1611
E:
Set Status for
O.Data[11]
Downstream Release and
P: Byte 22
Discharge Status
(Hi)
4:0232
Byte 23
(L
(Lo)
o)
M: 4:1612
Set Induct
E:
Tracking
O.Data[12] Induct T
Tracking
racking
Forward
P: Byte 24 Forwar
orwardd and
Direction
(Hi) Reverse
Word 1
Byte 25
4:0139
(L
(Lo)
o)
M: 4:1613
Set Induct
E:
Tracking
O.Data[13] Induct T
Tracking
racking
Forward
P: Byte 26 Forwar
orwardd and
Direction
(Hi) Reverse
Word 2
Byte 27
4:0140
(L
(Lo)
o)
M: 4:1614
Set Induct
E:
Tracking
O.Data[14] Induct T
Tracking
racking
Reverse
P: Byte 28 Forwar
orwardd and
Direction
(Hi) Reverse
Word 1
Byte 29
4:0237
(L
(Lo)
o)
M: 4:1615
Set Induct
E:
Tracking
O.Data[15] Induct T
Tracking
racking
Forward
P: Byte 30 Forwar
orwardd and
Direction
(Hi) Reverse
Word 2
Byte 31
4:0238
(L
(Lo)
o)
M: 4:1616
E:
Clear Motor
O.Data[16] Set Outputs and
Error
P: Byte 32 Motor Clear
4:0022
(Hi)
Byte 33
(L
(Lo)
o)
M: 4:1617
E:
Set Control O.Data[17]
Set Outputs and
Port Outputs P: Byte 34
Motor Clear
4:0063 (Hi)
Byte 35
(L
(Lo)
o)
M: 4:1618
E:
O.Data[18]
Reserved
P: Byte 36
N/A
(Hi)
Byte 37
(L
(Lo)
o)
M: 4:1619
E:
ConveyStop O.Data[19]
ConveyStop and
Command P: Byte 38
Clear Jams
4:0020 (Hi)
Byte 39
(L
(Lo)
o)
Upstream (Hi)
Zone Byte 45
4:0365 (L
(Lo)
o)
M: 4:1624
E:
ConveyMerge O.Data[24]
ConveyMer
ConveyMerge
ge
Interface P: Byte 48
Interface
4:0387 (Hi)
Byte 49
(L
(Lo)
o)
11.3.2.1. Set L
Local
ocal T
Tracking
racking
Register Name / Assembled
Description
Module AAddr
ddress
ess Addr
ddress
ess for PLC
Set Local
M: 4:1602
Downstream
E: O
O.Data
.Data [2] Write value for 16-bit integer tracking data word #1 for
Zone Tracking
P: Byte 4 (Hi) the Carton accumulated in the Downstream Zone
Word 1
Byte 5 (L
(Lo)
o)
4:0212
Set Local
M: 4:1603
Downstream
E: O
O.Data
.Data [3] Write value for 16-bit integer tracking data word #2 for
Zone Tracking
P: Byte 6 (Hi) the Carton accumulated in the Downstream Zone
Word 2
Byte 7 (L
(Lo)
o)
4:0213
Writing T
Tracking
racking Details
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:
! 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.
Notes for A
Accumulation
ccumulation Contr
Control
ol Bits
* 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
Bit 8 – A
Accumulate
ccumulate A
Adjacent
djacent Upstr
Upstream
eam Zone
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.
Bit 9 – Set Ar
Arrival
rival Confir
Confirmation
mation for Downstr
Downstream
eam Zone
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.
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 re-positioned or perhaps
Bit 12 – W
Wak
ake
e Up L
Local
ocal Zone
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.
* Wake up Local Zone functionality available in ERSC firmware versions 4.1 and
higher
Setting this bit will place the local zone in maintenance mode. In this mode the motor will not
run regardless of zone conditions. The zone upstream of this local zone will receive a “busy”
status to inhibit release of any item into this local zone. While in this state, the SEN and Motor
LEDs will flash on and off in green color.
M: 4:1606
Set Left Motor
E: O
O.Data
.Data [6]
Speed
P: Byte 12 (Hi) Value in % PWM:
4:0040
Byte 13 (L
(Lo)
o) Range: 0 to 1000
M: 4:1607 Example: 400 = 40%
Set Right Motor 0 = Remain at last non-zero value entered
E: O
O.Data
.Data [7]
Speed
P: Byte 14 (Hi)
4:0064
Byte 15 (L
(Lo)
o)
* Leaving these registers at “0” will instruct the module to use its configured
speed. Any non-zero value will instruct the nodule 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 module will 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
11.3.2.5. Induct T
Tracking
racking F
Forwar
orwardd and
Reverse
Register Name / Assembled
Description
Module AAddr
ddress
ess Addr
ddress
ess for PLC
M: 4:1616
Logical 1 or 0:
Clear Motor Error E: O
O.Data
.Data [16]
1 = send reset command
4:0022 P: Byte 32 (Hi)
0 = clear reset command
Byte 33 (L
(Lo)
o)
M: 4:1617
Set Control Port Bitwise Value: 1 energizes Output
E: O
O.Data
.Data [17]
Outputs bit 1 = Left Control Port
P: Byte 34 (Hi)
4:0063 bit 3 = Right Control Port
Byte 35 (L
(Lo)
o)
M: 4:1618
E: O
O.Data
.Data [18]
Reserved
P: Byte 36 (Hi)
Byte 37 (L
(Lo)
o)
Clear Motor Er
Errror
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.
! PLC 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
Contr
Control
ol P
Port
ort Outputs
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
Integer Value:
M: 4:1619 0 = No Command
ConveyStop
E: O
O.Data
.Data [19] 1 = Command local module’s Stop Group to
Command Word
P: Byte 38 (Hi) go to Stopped State
4:0020
Byte 39 (L
(Lo)
o) 2 = Command Local Module’s Stop Group to
Clear Stopped State
Clear Sensor Jam M: 4:1620 Use when PLC detects a local Upstream jam in Module
for Local E: O
O.Data
.Data [20] Status Word #1 Bit 5:
Upstream Zone P: Byte 40 (Hi) PLC creates transition from 0 to 1 to send command to
4:0109 Byte 41 (L
(Lo)
o) local upstream zone to clear the jam condition
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. To reset this condition the Carton must be manually removed after
the 3rd 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
11.3.2.8. Dir
Direction
ection and A
Accumulation
ccumulation Mode
Register Name / Assembled
Description
Module AAddr
ddress
ess Addr
ddress
ess for PLC
Notes on A
Accumulate
ccumulate Zones F
Functionality
unctionality
The Accumulate Zones function (Low Byte values 1 or 2) expects all zones to be empty or in
the process of releasing downstream when the function is initiated. Once the Accumulate
Zones function has been initiated, the logic is expecting to see the zone status change from
clear to blocked before the zone accumulates.
However, each
zone needs to
see a transition
fr
from
om empty to
full again for the
function to be
initiated. So in
this case, if
someone
removes a
carton frfrom
om a
zone, the carton
upstr
upstream
eam will
still convey to fill
the empty zone,
as well as any
other upstr
upstream
eam
cartons. If a
given zone was
alr
already
eady empty
when the
function was
initiated; the
ne
nextxt carton that
ar
arrives
rives will
accumulate.
11.3.2.9. ConveyMer
ConveyMerge
ge Interface
Register Name / Assembled
Description
Module AAddr
ddress
ess Addr
ddress
ess for PLC
ONL
ONLY
Y AVAIL
AILABLE
ABLE for FIRMW
FIRMWARE
ARE 4.25 and HIGHER
Bitwise Values:
Value:
11.3.3. ZP
ZPA
A Examples
11.3.3.1. Basic A
Accumulate
ccumulate and R
Release
elease
with T
Tracking
racking Data
Here is 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. For this example, the PLC must establish
ZPA Mode Assembly Input/Output connections to Module B as shown
Upstr
Upstream
eam Zone Example
First, let’s assume we want to accumulate any Carton that arrives on the upstream zone of
Module B. With the PLC:
1. Set bit 0 in Accumulation Contr
Control
ol for L
Local
ocal Upstr
Upstream
eam Zone register to instruct this
zone to accumulate any Carton that arrives.
2. Monitor Ar Arrival
rival Count L
Local
ocal Upstr
Upstream
eam Zone and Departur
Departure
e Count LLocal
ocal Upstr
Upstream
eam
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
Cur
Currrent Upstr
Upstream
eam Zone T Tracking
racking W
Wor
ord
d 1 and Cur
Currrent Upstr
Upstream
eam Zone T Tracking
racking W Wor
ord
d2
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 LLocal
ocal Upstr
Upstream
eam Zone T Tracking
racking W Wor
ord
d 1 and Set
Local Upstr
Upstream
eam Zone T Tracking
racking W
Wor
ord
d2
5. When the PLC is ready to release the Carton in the upstream zone, it should read the
value in the Cur
Currrent R
Release
elease Count for Upstr
Upstream
eam Zone register, add 1 to this value,
and then write this new value to Release and A Accumulate
ccumulate on NeNext
xt Ar
Arrival
rival for L
Local
ocal
Upstr
Upstream
eam Zone register. When Module 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 Module B are
full when this new value is written, Module 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 Module B upstream
zone by examining the values in Ar
Arrival
rival Count L
Local
ocal Upstr
Upstream
eam Zone and Departur
Departuree
Count L
Local
ocal Upstr
Upstream
eam 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 Module
B upstream zone.
If the PLC wants to cancel the accumulation control for Module B upstream zone:
PLC can reset bit 0 in Accumulation Contr
Control
ol for L
Local
ocal Upstr
Upstream
eam Zone register. This will
signal Module B to release any Carton accumulated and not accumulate the next Carton
that arrives at Module B upstream zone.
* Please note that if any new tracking data has been written to Set L
Upstr
Upstream
Wor
ord
eam Zone TTracking
racking W
Wor
ord
d 1 and/or Set LLocal
ocal Upstr
Upstream
eam Zone T
Local
ocal
Tracking
racking
d 2 and accumulation control is then canceled by resetting bit 0, this
data will NOT be assigned to the Carton when it is released. The ONL
ONLY Y way to
pass tracking data to a Carton is by following Step 5 above
Downstr
Downstream
eam Zone Example
First, let’s assume we want to accumulate any Carton that arrives on the upstream zone of
Module B. With the PLC:
1. Set bit 0 in Accumulation Contr
Control
ol for L
Local
ocal Downstr
Downstream
eam Zone register to instruct this
zone to accumulate any Carton that arrives.
2. Monitor Ar Arrival
rival Count L
Local
ocal Downstr
Downstream
eam Zone and Departur
Departure
e Count LLocal
ocal
Downstr
Downstream
eam 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 downstream zone, these two values will not be equal.
3. Upon a successful arrival of a Carton in the downstream zone, then tracking data in
Cur
Currrent Downstr
Downstream
eam Zone T Tracking
racking W
Wor
ord
d 1 and Cur
Currrent Downstr
Downstream
eam Zone T Tracking
racking
Worord
d 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 L Local
ocal Downstr
Downstream
eam Zone T Tracking
racking WWor
ordd 1 and
Set LLocal
ocal Downstr
Downstream
eam Zone T Tracking
racking W
Wor
ord
d 2.
5. When the PLC is ready to release the Carton in the downstream zone, it should read
the value in the Cur
Currrent RRelease
elease Count for Downstr
Downstream
eam Zone register, add 1 to this
value, and then write this new value to Release and A Accumulate
ccumulate on Ne
Next
xt Ar
Arrival
rival for
Local Downstr
Downstream
eam Zone register. When Module 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 Module B
are full when this new value is written, Module 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 Module B
downstream zone by examining the values in Ar Arrival
rival Count L
Local
ocal Downstr
Downstream
eam Zone
and Departur
Departure e Count L Local
ocal Downstr
Downstream
eam 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 Module B downstream zone.
If the PLC wants to cancel the accumulation control for Module B downstream zone:
PLC can reset bit 0 in Accumulation Contr
Control
ol for L
Local
ocal Downstr
Downstream
eam 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 L
Downstr
Downstream
eam Zone T
Tracking WWor
ord
Tracking
racking W
Wor
ordd 1 and/or Set L
Local
ocal Downstr
Downstream
Local
ocal
eam Zone
d 2 and accumulation control is then canceled by resetting bit 0,
this data will NOT be assigned to the Carton when it is released. The ONL
ONLYY
way to pass tracking data to a Carton is by following Step 5 above
In this example, Module 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.
For this example to work properly; the discharging zone of Module A and the single zone of
Module B must be in the default singluation release mode (not Train mode). Module A must also
not have its Arrival Jam disabled
disabled.
Because of built-in ZPA functionality, when a Carton leaves Module A discharge zone, Module A
waits until it receives confirmation from Module B that the Carton arrived. If a new Carton
arrives at Module A, it will accumulate until this arrival confirmation occurs. Because Module B
is a single long zone, the space for what would have been the upstream zone for Module B (if it
was configured as two zones) will now essentially be left clear when a Carton is accumulated
on Module B. This is the area where the bar code scanner is located. In this configuration, any
new arrival at Module 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 Module B and then
simply follow the zone control as described for basic accumulate and release
11.3.3.3. Upstr
Upstream
eam A
Accept
ccept 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
For this example, the PLC must establish a connection with Module A
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:
Wor
ord
Upstream
eam Induct register change from 4 to
1 in order to recognize the tracking data written to Set Induct T Tracking
racking FForwar
orward
d registers. If using the clearing of PE-1 to initiate the write of “1” the Set
d
11.3.3.4. Downstr
Downstream
eam Dischar
Discharge
ge 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. For this example, the PLC must establish a
connection with Module XX.
1. To hold any Carton that arrives at Module X downstream zone, the PLC writes a “5” to Set
Status for Downstr
Downstream
eam Dischar
Discharge
ge register. This tells Module 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 Downstr
Downstream
eam Dischar
Discharge
ge register. This tells Module 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 Module X Downstream Zone, the tracking data
for that Carton will be populated in Get T Tracking
racking FForwar
orwardd Dir
Direction
ection W
Wor
ordd 1 and Get
Tracking FForwar
orwardd Dir
Direction
ection W
Wor
ordd 2 registers.
4. When Carton arrives at PE-2, the PLC writes a “5” to Set Status for Downstr
Downstream
eam Dischar
Discharge
ge
register. This tells Module X that the Carton successfully transferred. If this is not done,
then Module X will produce an ArArrival
rival Jam condition.
Optional Step:
If the application is such that the PLC would like to inhibit a new Carton from entering Module X
downstream zone for whatever reason, there is a way to accumulate the next upstream zone to
the Module X downstream zone. The PLC can set bit 8 in the Accumulation Contr
Control
ol for L
Local
ocal
Downstr
Downstream
eam Zone and this will cause the adjacent upstream zone to accumulate (whether this
zone is on Module X or next adjacent upstream ConveyLinx Module). To return the accumulated
upstream zone to normal operation; the PLC simply resets bit 8 in this register
* This example assumes that the tracking data arriving from each new Carton
arrival at Module B Upstream Zone contains a value that will indicate to the PLC
that a Carton does or does not need to divert. However, it is not required that
the PLC use Carton tracking data be used to determine when to divert a Carton.
The PLC can use whatever criteria it needs to make a divert decision.
Upstr
Upstream
eam Zone TTracking
racking W
Wor
ordd 1 and Cur
Currrent Upstr
Upstream
eam Zone T
Tracking
racking W
Wor
ordd 2 will be valid
for the newly arrived Carton
If the PLC determines that the newly arrived carton needs to divert:
If the PLC determines that the newly arrived carton does not need to divert:
The PLC can simply modify Carton’s tracking data if desired and release the Carton as
described in Basic A
Accumulate
ccumulate and R
Release
elease section
11.3.3.6. Mer
Merge
ge onto ZP
ZPA
A Main Line
This example shows how to perform a simple merge with only a single ERSC connection to the
PLC. In this example the PLC only needs to connect to Module C and from this connection, the
PLC can monitor conditions on Module A as well as “wake-up” Module C / Module B zone to
accept a carton from the merging curve section.
1. With no PLC intervention, as long as cartons arrive into Module A they will be conveyed to
Module C/B and onto Module D in normal ZPA fashion.
2. To verify that Module C (and by extension Module B
B) is ready to accept a carton from the
merge curve; the PLC needs to know that Module C C’s zone is clear and stopped by
examining Local Status Upstr
Upstream
eam Zone F Forwar
orwardd Dir
Direction
ection register (Low Byte). When the
low byte of 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 Contr
Control
ol for L
Local
ocal Upstr
Upstream
eam Zone register to accumulate the adjacent
upstream zone, in this example setting bit 8 will cause Module A downstrdownstream
eam zone to
accumulate any carton that arrives.
4. When the PLC is ready to release a carton from the PLC Contr Controlled
olled Conveyor spur, the PLC
sets bit 12 in the Accumulation Contr
Control
ol for L
Local
ocal Upstr
Upstream
eam Zone register to wake up the
Module C zone (along with Module B’s zones because Module B is an extension of Module
C).
5. When the PLC sees the low byte of the Local Status Upstr
Upstream
eam Zone F
Forwar
orward
d Dir
Direction
ection
register change to a value of 4 or 5, the PLC knows that the carton made it to Module C’s
zone sensor and must then reset bit 12 in the Accumulation Contr
Control
ol for L
Local
ocal Upstr
Upstream
eam
Zone register. Either of these values will indicate a successful arrival at Module C
6. Upon reset of bit 12 of the Accumulation Contr
Control
ol for L
Local
ocal Upstr
Upstream
eam Zone register, the
PLC can reset bit 8 of the same register to indicate to Module A that it is OK to continue
normal ZPA function
ZP
ZPA
A Mode Inputs to PLC
Assembled Assembled Assembled
Module
Register Name Modbus EIP Profinet
Addr
ddress
ess
Addr
ddress
ess Addr
ddress
ess Addr
ddress
ess
Byte 0 (Hi)
4:0116 Local Status Upstream Zone 4:2900 I.Data [0]
Byte 1 (L
(Lo)
o)
Byte 2 (Hi)
4:0196 Local Status Downstream Zone 4:2901 I.Data [1]
Byte 3 (L
(Lo)
o)
Byte 4 (Hi)
4:0106 Arrival Count Local Upstream Zone 4:2902 I.Data [2]
Byte 5 (L
(Lo)
o)
Byte 6 (Hi)
4:0107 Departure Count Local Upstream Zone 4:2903 I.Data [3]
Byte 7 (L
(Lo)
o)
Byte 8 (Hi)
4:0186 Arrival Count Local Downstream Zone 4:2904 I.Data [4]
Byte 9 (L
(Lo)
o)
Byte 10 (Hi)
4:0187 Departure Count Local Downstream Zone 4:2905 I.Data [5]
Byte 11 (L
(Lo)
o)
Byte 12 (Hi)
4:0088 Module Status Word 1 4:2906 I.Data [6]
Byte 13 (L
(Lo)
o)
Byte 14 (Hi)
4:0089 Module Status Word 2 4:2907 I.Data [7]
Byte 15 (L
(Lo)
o)
Byte 16 (Hi)
4:0105 Current Release Count for Upstream Zone 4:2908 I.Data [8]
Byte 17 (L
(Lo)
o)
Byte 18 (Hi)
4:0185 Current Release Count for Downstream Zone 4:2909 I.Data [9]
Byte 19 (L
(Lo)
o)
Byte 20 (Hi)
4:0035 Sensor & Control Port Inputs 4:2910 I.Data [10]
Byte 21 (L
(Lo)
o)
Byte 22 (Hi)
Reserved 4:2911 I.Data [11]
Byte 23 (L
(Lo)
o)
ZP
ZPA
A Mode Outputs fr
from
om PLC
Assembled Assembled Assembled
Module
Register Name Modbus EIP Profinet
Addr
ddress
ess
Addr
ddress
ess Addr
ddress
ess Addr
ddress
ess
Byte 0 (Hi)
4:0104 Accumulation Control for Local Upstream Zone 4:3000 O.Data [0]
Byte 1 (L
(Lo)
o)
Byte 4 (Hi)
4:0040 Set Left MDR Speed 4:3002 O.Data [2]
Byte 5 (L
(Lo)
o)
Byte 6 (Hi)
4:0064 Set Right MDR Speed 4:3003 O.Data [3]
Byte 7 (L
(Lo)
o)
Byte 12 (Hi)
4:0134 Set Status for Upstream Induct 4:3006 O.Data [6]
Byte 13 (L
(Lo)
o)
Byte 14 (Hi)
4:0232 Set Status for Downstream Discharge 4:3007 O.Data [7]
Byte 15 (L
(Lo)
o)
Byte 16 (Hi)
4:0022 Clear Motor Error 4:3008 O.Data [8]
Byte 17 (L
(Lo)
o)
Byte 18 (Hi)
4:0063 Set Control Port Outputs 4:3009 O.Data [9]
Byte 19 (L
(Lo)
o)
4:0365 Direction & Accumulation Mode Control for 4:3013 O.Data Byte 26 (Hi)
• 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 stop motor outputs
• Ability to interface with upstream and downstream ZPA modules for status and tracking
* 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
! 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
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.
11.4.3. Configuring A
Action
ction for L
Loss
oss of
Communication
When changing the mode of a given ConveyLinx Module to PLC I/O mode in EasyRoll, you are
given the option to select the behavior of the ConveyLinx Module’s outputs upon loss of
communications with the PLC.
! Please note the ConveyLogix program file used in this dialog is the compiled
“.bin” file. It will not accept the ConveyLogix native “.clp” format source file.
Clear ConveyL
ConveyLogix
ogix P
Prrogram and k
keep
eep PLC I/O Mode
Register
Assembled
Name /
Addr
ddress
ess for Links
Module
PLC
Addr
ddress
ess
M: 4:1700
E: I.Data[0]
ConveyStop
P: Byte 0 ConveyStop
Status Word
(Hi) Status
4:0019
Byte 1
(L
(Lo)
o)
M: 4:1701
Sensor & E: I.Data[1]
Control Port P: Byte 2 Sensor & Contr
Control
ol
Inputs (Hi) Ports
4:0035 Byte 3
(L
(Lo)
o)
M: 4:1702
E: I.Data[2]
Sensor
P: Byte 4 Sensor & Contr
Control
ol
Detect
(Hi) Ports
4:0036
Byte 5
(L
(Lo)
o)
M: 4:1703
E: I.Data[3]
Module
P: Byte 6 Sensor & Contr
Control
ol
Voltage
(Hi) Ports
4:0024
Byte 7
(L
(Lo)
o)
M: 4:1704
E: I.Data[4]
Left Motor
P: Byte 8
Current Lef
eftt Motor Status
(Hi)
4:0055
Byte 9
(L
(Lo)
o)
M: 4:1705
E: I.Data[5]
Left Motor
P: Byte 10
Frequency Lef
eftt Motor Status
(Hi)
4:0056
Byte 11
(L
(Lo)
o)
M: 4:1706
E: I.Data[6]
Left Motor
P: Byte 12
Temperature Lef
eftt Motor Status
(Hi)
4:0057
Byte 13
(L
(Lo)
o)
M: 4:1707
E: I.Data[7]
Left Motor
P: Byte 14
Status Lef
eftt Motor Status
(Hi)
4:0058
Byte 15
(L
(Lo)
o)
M: 4:1708
E: I.Data[8]
Right Motor
P: Byte 16 Right Motor
Current
(Hi) Status
4:0079
Byte 17
(L
(Lo)
o)
M: 4:1709
E: I.Data[9]
Right Motor
P: Byte 18 Right Motor
Frequency
(Hi) Status
4:0080
Byte 19
(L
(Lo)
o)
M: 4:1710
E: I.Data[10]
Right Motor
P: Byte 20 Right Motor
Temperature
(Hi) Status
4:0081
Byte 21
(L
(Lo)
o)
M: 4:1711
Right Motor
E: I.Data[11] Right Motor
Status
P: Byte 22 Status
4:0082
(Hi)
Byte 23
(L
(Lo)
o)
M: 4:1712
Left Motor E: I.Data[12]
Port Digital I/ P: Byte 24 Motor PPorts
orts
O Status (Hi) Digital Status
4:0060 Byte 25
(L
(Lo)
o)
M: 4:1713
Right Motor E: I.Data[13]
Port Digital I/ P: Byte 26 Motor PPorts
orts
O Status (Hi) Digital Status
4:0084 Byte 27
(L
(Lo)
o)
M: 4:1714
Upstream E: I.Data[14]
Upstr
Upstream
eam /
Module P: Byte 28
Downstr
Downstream
eam
Status (Hi)
Status & T
Tracking
racking
4:0134 Byte 29
(L
(Lo)
o)
M: 4:1715
Downstream E: I.Data[15]
Upstr
Upstream
eam /
Module P: Byte 30
Downstr
Downstream
eam
Status (Hi)
Status & T
Tracking
racking
4:0232 Byte 31
(L
(Lo)
o)
Current
M: 4:1716
Tracking
E: I.Data[16]
Word 1 for Upstr
Upstream
eam /
P: Byte 32
Adjacent Downstr
Downstream
eam
(Hi)
Upstream Status & T
Tracking
racking
Byte 33
Module
(L
(Lo)
o)
4:0139
Current
M: 4:1717
Tracking
E: I.Data[17]
Word 2 for Upstr
Upstream
eam /
P: Byte 34
Adjacent Downstr
Downstream
eam
(Hi)
Upstream Status & T
Tracking
racking
Byte 35
Module
(L
(Lo)
o)
4:0140
M: 4:1718
Current
E: I.Data[18]
Module Upstr
Upstream
eam /
P: Byte 36
Reset Downstr
Downstream
eam
(Hi)
Counter Status & T
Tracking
racking
Byte 37
N/A
(L
(Lo)
o)
M: 4:1719
Left Motor E: I.Data[19]
Servo P: Byte 38 Servo Contr
Control
ol
Position (Hi) Status
4:0062 Byte 39
(L
(Lo)
o)
M: 4:1720
Right Motor E: I.Data[20]
Servo P: Byte 40 Servo Contr
Control
ol
Position (Hi) Status
4:0086 Byte 41
(L
(Lo)
o)
M: 4:1721
E: I.Data[21]
Left Motor
P: Byte 42 Servo Contr
Control
ol
Servo Status
(Hi) Status
4:0011
Byte 43
(L
(Lo)
o)
M: 4:1722
E: I.Data[22]
Right Motor
P: Byte 44 Servo Contr
Control
ol
Servo Status
(Hi) Status
4:0016
Byte 45
(L
(Lo)
o)
M: 4:1702
Bitwise Value – Read Only
Sensor Detect E: I.Data [2]
bit 0 = Device is connected to Right Sensor Port
4:0036 P: Byte 4 (Hi)
bit 1 = Device is connected to Left Sensor Port
Byte 5 (L
(Lo)
o)
M: 4:1703
Value in mV of Module Power Supply
Module Voltage E: I.Data [3]
Range: 0 to 35000
4:0024 P: Byte 6 (Hi)
Example: 23500 = 23.5 Volts
Byte 7 (L
(Lo)
o)
* 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 & Contr
Control
ol P
Port
ort Input Signal
Condition Mask register to arrive at the bit values seen in the Sensor & Contr Control
ol
Port Inputs 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 &
Contr
Control
ol P
Port
ort Inputs register. This same relationship is also mirrored by the state
of the input’s corresponding LED indicator
11.4.6.3. Lef
eftt Motor Status
Register Name /
Assembled A
Addr
ddress
ess for PLC Description
Module AAddr
ddress
ess
M: 4:1704
Left Motor Integer Value in mA for the current the motor is
E: I.Data [4]
Current drawing
P: Byte 8 (Hi)
4:0055 Example: 1900 = 1.9 Amps
Byte 9 (L
(Lo)
o)
M: 4:1705
Left Motor Integer value in Hz for the electrical frequency
E: I.Data [5]
Frequency the motor is running
P: Byte 10 (Hi)
4:0056 Example: 300 = 300 Hz
Byte 11 (L
(Lo)
o)
Motor R
Rotation
otation Status
Bits 0 and 1 are used in combination to provide 4 possible states. The following chart defines
the bit values for these states:
Motor F
Frrequency
This contains the current value of the electrical frequency of the motor if it is running. For
Senergy motors, electrical frequency divided by 5 = mechanical frequency. The mechanical
frequency is the number of motor rotations per second. You can use this value along with the
mechanical gear ratio of the gearbox to calculate the actual running motor RPM. Please consult
your Pulseroller catalog for the gear ratio value for the particular part number you are using.
M: 4:1708
Right Motor
E: I.Data [8] Integer Value in mA for the current the motor is drawing
Current
P: Byte 16 (Hi) Example: 1900 = 1.9 Amps
4:0079
Byte 17 (L
(Lo)
o)
M: 4:1709
Right Motor Integer value in Hz for the electrical frequency the motor
E: I.Data [9]
Frequency is running
P: Byte 18 (Hi)
4:0080 Example: 300 = 300 Hz
Byte 19 (L
(Lo)
o)
Motor R
Rotation
otation Status
Motor F
Frrequency
11.4.6.5. Motor P
Ports
orts Digital Status
Register Name / Assembled
Description
Module AAddr
ddress
ess Addr
ddress
ess for PLC
M: 4:1712
Left Motor Port
E: I.Data [12]
Digital I/O Status Bitwise Value – Read Only:
P: Byte 24 (Hi)
4:0060
Byte 25 (L
(Lo)
o)
bit 12 = Short Circuit Error on one or more outputs
M: 4:1713 bit 14 = Over Current – More than 1A detected on
Right Motor Port
E: I.Data [13] one or more outputs
Digital I/O Status
P: Byte 26 (Hi)
4:0084
Byte 27 (L
(Lo)
o)
11.4.6.6. Upstr
Upstream
eam / Downstr
Downstream
eam Status &
Tracking
Register Name / Assembled
Description
Module AAddr
ddress
ess Addr
ddress
ess for PLC
Current Tracking
M: 4:1716
Word 1 for Value = Tracking data word #1 (16-bit integer) for the
E: I.Data [16]
Adjacent Carton that has just discharged from the ERSC Adjacent
P: Byte 32 (Hi)
Upstream Module to this local ERSC module
Byte 33 (L
(Lo)
o)
4:0139
Current Tracking
M: 4:1717
Word 2 for Value = Tracking data word #2 (16-bit integer) for the
E: I.Data [17]
Adjacent Carton that has just discharged from the ERSC Adjacent
P: Byte 34 (Hi)
Upstream Module to this local ERSC module
Byte 35 (L
(Lo)
o)
4:0140
M: 4:1718
E: I.Data [18]
Reserved
P: Byte 36 (Hi)
Byte 37 (L
(Lo)
o)
Understanding A
Adjacent
djacent Modules
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. Learn about clearing connections.
M: 4:1719
Left Motor Servo
E: I.Data [19] Signed integer value that indicates the current position of
Position
P: Byte 38 (Hi) the Left Motor in relation to its “0” position
4:0062
Byte 39 (L
(Lo)
o)
M: 4:1720
Right Motor Servo
E: I.Data [20] Signed integer value that indicates the current position of
Position
P: Byte 40 (Hi) the Right Motor in relation to its “0” position
4:0086
Byte 41 (L
(Lo)
o)
Register
Assembled
Name /
Addr
ddress
ess for Links
Module
PLC
Addr
ddress
ess
M: 4:1800
E:
ConveyStop O.Data[0] ConveyStop
Command P: Byte 0 Command & Clear
4:0020 (Hi) Motor Er
Errror
Byte 1
(L
(Lo)
o)
M: 4:1801
E:
Set Left Motor
O.Data[1]
Port Digital Motor & Contr
Control
ol P
Port
ort
P: Byte 2
Control Digital Output
(Hi)
4:0060
Byte 3
(L
(Lo)
o)
M: 4:1802
E:
Set Right
O.Data[2]
Motor Port Motor & Contr
Control
ol P
Port
ort
P: Byte 4
Digital Control Digital Output
(Hi)
4:0084
Byte 5
(L
(Lo)
o)
M: 4:1803
E:
Control Port
O.Data[3]
Digital Output Motor & Contr
Control
ol P
Port
ort
P: Byte 6
Control Digital Output
(Hi)
4:0037
Byte 7
(L
(Lo)
o)
P: Byte 8
(Hi)
Byte 9
(L
(Lo)
o)
M: 4:1805
E:
Left Motor O.Data[5]
Brake Method P: Byte 10 Lef
eftt Motor Contr
Control
ol
4:0261 (Hi)
Byte 11
(L
(Lo)
o)
M: 4:1806
E:
Left Motor
O.Data[6]
Speed Control
P: Byte 12 Lef
eftt Motor Contr
Control
ol
Method
(Hi)
4:0262
Byte 13
(L
(Lo)
o)
M: 4:1807
E:
Right Motor O.Data[7]
Run / Reverse P: Byte 14 Right Motor Contr
Control
ol
4:0270 (Hi)
Byte 15
(L
(Lo)
o)
M: 4:1808
E:
Right Motor O.Data[8]
Brake Method P: Byte 16 Right Motor Contr
Control
ol
4:0271 (Hi)
Byte 17
(L
(Lo)
o)
M: 4:1809
E:
Right Motor
O.Data[9]
Speed Control
P: Byte 18 Right Motor Contr
Control
ol
Method
(Hi)
4:0272
Byte 19
(L
(Lo)
o)
E:
O.Data[10]
Speed
P: Byte 20
Reference
(Hi)
4:0040
Byte 21
(L
(Lo)
o)
M: 4:1811
E:
Right Motor
O.Data[11]
Speed
P: Byte 22 Right Motor Contr
Control
ol
Reference
(Hi)
4:0064
Byte 23
(L
(Lo)
o)
M: 4:1812
E:
Left Motor
O.Data[12]
Acceleration
P: Byte 24 Lef
eftt Motor Contr
Control
ol
Ramp
(Hi)
4:0043
Byte 25
(L
(Lo)
o)
M: 4:1813
E:
Left Motor
O.Data[13]
Deceleration
P: Byte 26 Lef
eftt Motor Contr
Control
ol
Ramp
(Hi)
4:0044
Byte 27
(L
(Lo)
o)
M: 4:1814
E:
Right Motor
O.Data[14]
Acceleration
P: Byte 28 Right Motor Contr
Control
ol
Ramp
(Hi)
4:0067
Byte 29
(L
(Lo)
o)
M: 4:1815
E:
Right Motor
O.Data[15]
Deceleration
P: Byte 30 Right Motor Contr
Control
ol
Ramp
(Hi)
4:0068
Byte 31
(L
(Lo)
o)
M: 4:1816
E:
Clear Motor O.Data[16] ConveyStop
Error P: Byte 32 Command & Clear
4:0022 (Hi) Motor Er
Errror
Byte 33
(L
(Lo)
o)
M: 4:1817
E:
Set Status to
O.Data[17]
Downstream
P: Byte 34 Set Status & T
Tracking
racking
Module
(Hi)
4:0196
Byte 35
(L
(Lo)
o)
M: 4:1818
E:
Set Status to
O.Data[18]
Upstream
P: Byte 36 Set Status & T
Tracking
racking
Module
(Hi)
4:0116
Byte 37
(L
(Lo)
o)
M: 4:1819
Sensor Port E:
Input Signal O.Data[19]
Set Sensor & Contr
Control
ol
Condition P: Byte 38
Port Input Mask
Mask (Hi)
4:0034 Byte 39
(L
(Lo)
o)
M: 4:1820
E:
Set Discharge
O.Data[20]
Tracking Word
P: Byte 40 Set Status & T
Tracking
racking
1
(Hi)
4:0201
Byte 41
(L
(Lo)
o)
M: 4:1821
Set Discharge E:
Tracking Word O.Data[21]
Set Status & T
Tracking
racking
2 P: Byte 42
4:0202 (Hi)
Byte 43
(L
(Lo)
o)
M: 4:1822
E:
Set Module O.Data[22]
Reset Count P: Byte 44
N/A (Hi)
Byte 45
(L
(Lo)
o)
M: 4:1823
Left Motor E:
Servo O.Data[23]
Command P: Byte 46 Servo Contr
Control
ol
Pulses (Hi)
4:0008 Byte 47
(L
(Lo)
o)
M: 4:1824
Left Motor E:
Servo O.Data[24]
Command P: Byte 48 Servo Contr
Control
ol
Word (Hi)
4:0009 Byte 49
(L
(Lo)
o)
M: 4:1825
Right Motor E:
Servo O.Data[25]
Command P: Byte 50 Servo Contr
Control
ol
Pulses (Hi)
4:0013 Byte 51
(L
(Lo)
o)
M: 4:1826
Right Motor E:
Servo O.Data[26]
Command P: Byte 52 Servo Contr
Control
ol
Word (Hi)
4:0014 Byte 53
(L
(Lo)
o)
Integer Value
M: 4:1800 0= No Command
ConveyStop
E: O
O.Data
.Data [0] 1 = Command local module’s Stop Group to go to
Command Word
P: Byte 0 (Hi) Stopped State
4:0020
Byte 1 (L
(Lo)
o) 2 = Command local module’s Stop Group to Clear
Stopped State
M: 4:1816
Logical 1 or 0:
Clear Motor Error E: O
O.Data
.Data [16]
1 = send reset command
4:0022 P: Byte 32 (Hi)
0 = clear reset command
Byte 33 (L
(Lo)
o)
11.4.7.3. Lef
eftt Motor Contr
Control
ol
Register Name / Assembled
Description
Module AAddr
ddress
ess Addr
ddress
ess for PLC
Bit 0:
M: 4:1804 1= Run Command
Left Motor Run /
E: O
O.Data
.Data [4] 0= Stop Command
Reverse
P: Byte 8 (Hi) Bit 8:
4:0260
Byte 9 (L
(Lo)
o) 0= Run in Configured Direction
1= Run opposite of Configured Direction
Integer Value:
M: 4:1805 1 = Use Standard Brake Method
Left Motor Brake
E: O
O.Data
.Data [5] 2 = Use Free Coast Brake Method
Method
P: Byte 10 (Hi) 3 = Use Servo 1 Brake Method
4:0261
Byte 11 (L
(Lo)
o) 4 = Use Servo 2 Brake Method
0 = Remain at last configured or last value entered
Bit 0:
M: 4:1807 1= Run Command
Right Motor Run /
E: O
O.Data
.Data [7] 0= Stop Command
Reverse
P: Byte 14 (Hi) Bit 8:
4:0270
Byte 15 (L
(Lo)
o) 0= Run in Configured Direction
1= Run opposite of Configured Direction
Integer Value:
M: 4:1808 1 = Use Standard Brake Method
Right Motor Brake
E: O
O.Data
.Data [8] 2 = Use Free Coast Brake Method
Method
P: Byte 16 (Hi) 3 = Use Servo 1 Brake Method
4:0271
Byte 17 (L
(Lo)
o) 4 = Use Servo 2 Brake Method
0 = Remain at last configured or last value entered
M: 4:1820
Set Discharge
E: O
O.Data
.Data [20]
Tracking Word 1
P: Byte 40 (Hi) Only used when local PLC I/O Mode ConveyLinx Module
4:0201
Byte 41 (L
(Lo)
o) needs to pass tracking data to a downstream connected
M: 4:1821 ConveyLinx Module. Used in conjunction with Set Status
Set Discharge to Downstream Module register
E: O
O.Data
.Data [21]
Tracking Word 2
P: Byte 42 (Hi)
4:0202
Byte 43 (L
(Lo)
o)
M: 4:1822
E: O
O.Data
.Data [22]
Reserved
P: Byte 44 (Hi)
Byte 45 (L
(Lo)
o)
Bitwise Value:
bit 00 = Left Sensor Port – Pin 3
bit 01 = Left Control Port – Pin 3
Sensor Port Input M: 4:1819 bit 02 = Right Sensor Port – Pin 3
Signal Condition E: O
O.Data
.Data [19] bit 03 = Right Control Port – Pin 3
Mask P: Byte 38 (Hi) bit 04 = Left Sensor Port – Pin 4
4:0034 Byte 39 (L
(Lo)
o) bit 05 = Left Control Port – Pin 4
bit 06 = Right Sensor Port – Pin 4
bit 07 = Right Control Port – Pin 4
bit 08 thru bit 15 = Reserved
For an ConveyLinx Module in standard ZPA mode, the Auto-Configuration procedure sets values
in this register to allow the ConveyLinx Module 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 ConveyLinx Module’s sensor input pin 4 when
the zone is clear. The ConveyLinx Module’s 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 & Contr
Control
ol P
Port
ort 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 ConveyLinx Module 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 ConveyLinx
Module’s inputs. The same pattern applies to all 8 available ERSC inputs:
ON 0 1 Green = ON
OFF 1 1 Green = ON
ON 1 0 Green = OFF
Example: L
Lef
eftt Contr
Control
ol P
Port
ort – P
Pin
in 3 Signal
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; when
the green and red LEDs are illuminated at the same time, the color will be
amber
M: 4:1824
Left Motor Servo Bit 0: Reset Command
E: O
O.Data
.Data [24]
Command Word 1 = Set Current Pulse Count to “0”
P: Byte 48 (Hi)
4:0009
Byte 49 (L
(Lo)
o)
Bit 1: Servo Run Command
M: 4:1826 1 = Run in Motor from current pulse count to set
Right Motor Servo
E: O
O.Data
.Data [26] pulse count in Left Motor Servo Command
Command Word
P: Byte 52 (Hi) Pulses Register
4:0014
Byte 53 (L
(Lo)
o)
M: 4:1823
Left Motor Servo
E: O
O.Data
.Data [23]
Command Pulses
P: Byte 46 (Hi) Signed integer value in motor pulses of the position to
4:0008
Byte 47 (L
(Lo)
o) move to on the next Servo Run Command
M: 4:1825
Right Motor Servo Valid values are from -32767 to +32767
E: O
O.Data
.Data [25]
Command Pulses
P: Byte 50 (Hi)
4:0013
Byte 51 (L
(Lo)
o)
! 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
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. Learn about Motor Pulse to Distance Calculation
• 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
! 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 ConveyLinx Module’s
configuration
Sequence of Operation
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:
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:
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.
Step #7: For the 3rd rotation, we keep the ramp values from the 2nd 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.
Byte 0 (Hi)
4:0035 Sensor & Control Port Inputs 4:2700 I.Data [0]
Byte 1 (L
(Lo)
o)
Byte 2 (Hi)
4:0036 Sensor Detect 4:2701 I.Data [1]
Byte 3 (L
(Lo)
o)
Byte 4 (Hi)
4:0057 Left Motor Temperature 4:2702 I.Data [2]
Byte 5 (L
(Lo)
o)
Byte 6 (Hi)
4:0058 Left Motor Status 4:2703 I.Data [3]
Byte 7 (L
(Lo)
o)
Byte 8 (Hi)
4:0081 Right Motor Temperature 4:2704 I.Data [4]
Byte 9 (L
(Lo)
o)
Byte 10 (Hi)
4:0082 Right Motor Status 4:2705 I.Data [5]
Byte 11 (L
(Lo)
o)
Byte 12 (Hi)
4:0060 Left Motor Port Digital I/O Status 4:2706 I.Data [6]
Byte 13 (L
(Lo)
o)
Byte 14 (Hi)
4:0084 Right Motor Port Digital I/O Status 4:2707 I.Data [7]
Byte 15 (L
(Lo)
o)
Byte 16 (Hi)
Reserved 4:2708 I.Data [8]
Byte 17 (L
(Lo)
o)
Byte 0 (Hi)
4:0060 Set Left Motor Port Digital Control 4:2800 O.Data [0]
Byte 1 (L
(Lo)
o)
Byte 2 (Hi)
4:0084 Set Right Motor Port Digital Control 4:2801 O.Data [1]
Byte 3 (L
(Lo)
o)
Byte 4 (Hi)
4:0037 Control Port Digital Output Control 4:2802 O.Data [2]
Byte 5 (L
(Lo)
o)
Byte 6 (Hi)
4:0260 Left Motor Run / Reverse 4:2803 O.Data [3]
Byte 7 (L
(Lo)
o)
Byte 8 (Hi)
4:0270 Right Motor Run / Reverse 4:2804 O.Data [4]
Byte 9 (L
(Lo)
o)
Byte 10 (Hi)
4:0040 Left Motor Speed Reference 4:2805 O.Data [5]
Byte 11 (L
(Lo)
o)
Byte 12 (Hi)
4:0064 Right Motor Speed Reference 4:2806 O.Data [6]
Byte 13 (L
(Lo)
o)
Byte 14 (Hi)
4:0022 Clear Motor Error 4:2807 O.Data [7]
Byte 15 (L
(Lo)
o)
Byte 16 (Hi)
Reserved 4:2808 O.Data [8]
Byte 17 (L
(Lo)
o)
11.5. ConveyL
ConveyLogix
ogix Interface
ConveyLinx Modules 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 ConveyLinx Module that is running a ConveyLogix program.
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 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.
! These assemblies are only available for ConveyLinx Module firmware 4.25 and
later and ConveyLogix version 2.02 or later is required to create programs that
can access these assemblies
11.5.1. ConveyL
ConveyLogix
ogix Assembly Inputs to
PLC
ConveyL
ConveyLogix
ogix Modbus PLC
Ether
Ethernet
net I/P T
Tag
ag Profinet I/O Byte Offset
Contr
Controller
oller T
Tag
ag Holding R
Register
egister
ToPLCAr
oPLCArray
ray [0] E: I.Data [0] M: 4:13100 P: Byte 0 (Hi) Byte 1 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [1] E: I.Data [1] M: 4:13101 P: Byte 2 (Hi) Byte 3 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [2] E: I.Data [2] M: 4:13102 P: Byte 4 (Hi) Byte 5 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [3] E: I.Data [3] M: 4:13103 P: Byte 6 (Hi) Byte 7 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [4] E: I.Data [4] M: 4:13104 P: Byte 8 (Hi) Byte 9 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [5] E: I.Data [5] M: 4:13105 P: Byte 10 (Hi) Byte 11 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [6] E: I.Data [6] M: 4:13106 P: Byte 12 (Hi) Byte 13 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [7] E: I.Data [7] M: 4:13107 P: Byte 14 (Hi) Byte 15 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [8] E: I.Data [8] M: 4:13108 P: Byte 16 (Hi) Byte 17 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [9] E: I.Data [9] M: 4:13109 P: Byte 18 (Hi) Byte 19 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [10] E: I.Data [10] M: 4:13110 P: Byte 20 (Hi) Byte 21 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [11] E: I.Data [11] M: 4:13111 P: Byte 22 (Hi) Byte 23 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [12] E: I.Data [12] M: 4:13112 P: Byte 24 (Hi) Byte 25 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [13] E: I.Data [13] M: 4:13113 P: Byte 26 (Hi) Byte 27 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [14] E: I.Data [14] M: 4:13114 P: Byte 28 (Hi) Byte 29 (L
(Lo)
o)
ToPLCAr
oPLCArray
ray [15] E: I.Data [15] M: 4:13115 P: Byte 30 (Hi) Byte 31 (L
(Lo)
o)
11.5.2. ConveyL
ConveyLogix
ogix Assembly Outputs
fr
from
om PLC
ConveyL
ConveyLogix
ogix Modbus PLC
Ether
Ethernet
net I/P T
Tag
ag Profinet I/O Byte Offset
Contr
Controller
oller T
Tag
ag Holding R
Register
egister
FromPLCAr
omPLCArray
ray [0] E: O
O.Data
.Data [0] M: 4:13200 P: Byte 0 (Hi) Byte 1 (L
(Lo)
o)
FromPLCAr
omPLCArray
ray [1] E: O
O.Data
.Data [1] M: 4:13201 P: Byte 2 (Hi) Byte 3 (L
(Lo)
o)
FromPLCAr
omPLCArray
ray [2] E: O
O.Data
.Data [2] M: 4:13202 P: Byte 4 (Hi) Byte 5 (L
(Lo)
o)
FromPLCAr
omPLCArray
ray [3] E: O
O.Data
.Data [3] M: 4:13203 P: Byte 6 (Hi) Byte 7 (L
(Lo)
o)
FromPLCAr
omPLCArray
ray [4] E: O
O.Data
.Data [4] M: 4:13204 P: Byte 8 (Hi) Byte 9 (L
(Lo)
o)
FromPLCAr
omPLCArray
ray [5] E: O
O.Data
.Data [5] M: 4:13205 P: Byte 10 (Hi) Byte 11 (L
(Lo)
o)
FromPLCAr
omPLCArray
ray [6] E: O
O.Data
.Data [6] M: 4:13206 P: Byte 12 (Hi) Byte 13 (L
(Lo)
o)
FromPLCAr
omPLCArray
ray [7] E: O
O.Data
.Data [7] M: 4:13207 P: Byte 14 (Hi) Byte 15 (L
(Lo)
o)
FromPLCAr
omPLCArray
ray [8] E: O
O.Data
.Data [8] M: 4:13208 P: Byte 16 (Hi) Byte 17 (L
(Lo)
o)
FromPLCAr
omPLCArray
ray [9] E: O
O.Data
.Data [9] M: 4:13209 P: Byte 18 (Hi) Byte 19 (L
(Lo)
o)
FromPLCAr
omPLCArray
ray
E: O
O.Data
.Data [10] M: 4:13210 P: Byte 20 (Hi) Byte 21 (L
(Lo)
o)
[10]
FromPLCAr
omPLCArray
ray
E: O
O.Data
.Data [11] M: 4:13211 P: Byte 22 (Hi) Byte 23 (L
(Lo)
o)
[11]
FromPLCAr
omPLCArray
ray
E: O
O.Data
.Data [12] M: 4:13212 P: Byte 24 (Hi) Byte 25 (L
(Lo)
o)
[12]
FromPLCAr
omPLCArray
ray
E: O
O.Data
.Data [13] M: 4:13213 P: Byte 26 (Hi) Byte 27 (L
(Lo)
o)
[13]
FromPLCAr
omPLCArray
ray
E: O
O.Data
.Data [14] M: 4:13214 P: Byte 28 (Hi) Byte 29 (L
(Lo)
o)
[14]
FromPLCAr
omPLCArray
ray
E: O
O.Data
.Data [15] M: 4:13215 P: Byte 30 (Hi) Byte 31 (L
(Lo)
o)
[15]
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.
11.6.1. ZP
ZPAA Mode Assembly Inputs with
Reset P
Prrotection
Modbus PLC
Module
Register Name Ether
Ethernet
net I/P T
Tag
ag Holding
Addr
ddress
ess
Register
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
N/A Cur
Currrent Module R
Reset
eset Count E: I.Data [19] M: 4:3519
11.6.2. ZP
ZPAA Mode Assembly Outputs with
Reset P
Prrotection
Modbus PLC
Module Ether
Ethernet
net I/P
Register Name Holding
Addr
ddress
ess Tag
Register
4:0132 Set Local Upstream Zone Tracking Word 1 E: I.Data [0] M: 4:3600
4:0133 Set Local Upstream Zone Tracking Word 2 E: I.Data [1] M: 4:3601
4:0212 Set Local Downstream Zone Tracking Word 1 E: I.Data [2] M: 4:3602
4:0213 Set Local Downstream Zone Tracking Word 2 E: I.Data [3] M: 4:3603
4:0104 Accumulation Control for Local Upstream Zone E: I.Data [4] M: 4:3604
4:0184 Accumulation Control for Local Downstream Zone E: I.Data [5] M: 4:3605
E: I.Data
4:0134 Set Status for Upstream Induct M: 4:3610
[10]
E: I.Data
4:0232 Set Status for Downstream Discharge M: 4:3611
[11]
E: I.Data
4:0139 Set Induct Tracking Forward Direction Word 1 M: 4:3612
[12]
E: I.Data
4:0140 Set Induct Tracking Forward Direction Word 2 M: 4:3613
[13]
E: I.Data
4:0237 Set Induct Tracking Reverse Direction Word 1 M: 4:3614
[14]
E: I.Data
4:0238 Set Induct Tracking Reverse Direction Word 2 M: 4:3615
[15]
E: I.Data
4:0022 Clear Motor Error M: 4:3616
[16]
E: I.Data
4:0063 Set Control Port Outputs M: 4:3617
[17]
E: I.Data
N/A Set Module R
Reset
eset Count M: 4:3618
[18]
E: I.Data
4:0020 ConveyStop Command M: 4:3619
[19]
E: I.Data
4:0109 Clear Sensor Jam Command for Local Upstream Zone M: 4:3620
[20]
E: I.Data
4:0189 Clear Sensor Jam Command for Local Downstream Zone M: 4:3621
[21]
E: I.Data
4:0387 ConveyMerge Interface M: 4:3624
[24]
Modbus PLC
Module Ether
Ethernet
net I/P
Register Name Holding
Addr
ddress
ess Tag
Register
4:0105 Current Release Count for Upstream Zone E: I.Data [8] M: 4:4908
4:0185 Current Release Count for Downstream Zone E: I.Data [9] M: 4:4909
N/A Cur
Currrent Module R
Reset
eset Count E: I.Data [11] M: 4:4911
Outputs fr
from
om PLC
Modbus PLC
Module Ether
Ethernet
net I/P
Register Name Holding
Addr
ddress
ess Tag
Register
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 [0] M: 4:5001
4:0109 Clear Sensor Jam Command for Local Upstream Zone E: O.Data [11] M: 4:5011
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
N/A Cur
Currrent Module R
Reset
eset Counter E: I.Data [18] M: 4:3718
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:0034 Sensor Port Input Signal Condition Mask E: O.Data [19] M: 4:3819
Modbus PLC
Module Ether
Ethernet
net I/P
Register Name Holding
Addr
ddress
ess Tag
Register
4:0060 Left Motor Port Digital I/O Status E: I.Data [6] M: 4:4706
4:0084 Right Motor Port Digital I/O Status E: I.Data [7] M: 4:4707
N/A Cur
Currrent Module R
Reset
eset Count E: I.Data [8] M: 4:4708
Outputs fr
from
om PLC
Modbus PLC
Module Ether
Ethernet
net I/P
Register Name Holding
Addr
ddress
ess Tag
Register
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
• When the ConveyLinx Module detects that the value in Set Module R Reset
eset Counter register
is equal to the value in the Cur
Currrent Module R
Reset
eset Counter register; the ConveyLinx Module
will respond to data being written by the PLC to the remaining output assembly registers.
* To make sure a given ZPA zone accumulates upon power up, use EasyRoll
configuration tool software to set the zone to “Accumulate”. When set from
EasyRoll, this setting will be retained in the flash memory of the ConveyLinx
Module so that the zone will initially accumulate if a load happens to be in the
zone at the time of power up. Learn about Accumulate function in EasyRoll
* When a ZPA zone is commanded to accumulate with a PLC and you happen to
connect to that ConveyLinx Module 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 ConveyLinx Module
Module. 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
11.7. Motor P
Port
ort as Digital I/O
! Motor port as digital I/O is only applicable for an ERSC in PLC I/O Mode
* Please note that the ERSC switches to GND to complete the circuit
! 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
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
11.8. OD
ODVVA Compliant Cr
Cross-R
oss-Refer
eference
ence
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
11.8.1. ZP
ZPA
A Mode Assembly Inputs
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
11.8.2. ZP
ZPA
A Mode Assembly Outputs
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
11.8.3. ZP
ZPA
A Mode R
Reduced
educed Size
ZP
ZPA
A Mode Inputs
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
ZP
ZPA
A Mode Outputs
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
11.8.7. Reset P
Prrotection for ZP
ZPA
A Mode
Assembly Inputs
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
11.8.8. Reset P
Prrotection for ZP
ZPA
A Mode
Assembly Outputs
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
Upstream Zone
11.8.9. Reset P
Prrotection for R
Reduced
educed Size
ZP
ZPA
A Assemblies
ZP
ZPA
A Mode Inputs
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
ZP
ZPA
A Mode Outputs
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
11.8.10. Reset P
Prrotection for PLC I/O Mode
Assembly Inputs
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
11.8.11. Reset P
Prrotection for PLC I/O Mode
Assembly Outputs
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
11.8.12. Reset P
Prrotection for PLC I/O Mode
Reduced Size
PLC I/O Mode Inputs
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
Assembled Assembled
Module
Register Name Addr
ddress
ess for FW Addr
ddress
ess for FW
Addr
ddress
ess
5.2 4.25 and earlier
! THIS SECTION ONLY APPLIES TO FIRMWARE 4.25 AND OLDER AND 5.02 AND
OLDER. FOR FIRMWARE 4.27 / 5.07 AND NEWER THIS FUNCTIONALITY IS
PROVIDED AUTOMATICALLY THROUGH SET UP IN EASYROLL
This section describes how to set up conveyor zones with two motor rollers in scenarios
involving ZPA Mode, PLC I/O Mode, and ConveyLogix program control. The details of the set up
are also governed by the mechanical construction of the conveyor zone.
! THIS SECTION ONLY APPLIES TO FIRMWARE 4.25 AND OLDER AND 5.02 AND
OLDER. FOR FIRMWARE 4.27 / 5.07 AND NEWER THIS FUNCTIONALITY IS
PROVIDED AUTOMATICALLY THROUGH SET UP IN EASYROLL
This scenario is perhaps the most common in that this would be the case for a two-motor roller
belted zone used in an incline or decline application as shown. Please note that mechanically
the two motor rollers can be coupled with just O-bands, Poly-V belts, etc. The concept is that
the upstream motor roller is there to assist the downstream motor roller.
12.1.1. ZP
ZPA
A Mode
In general, when you perform an Auto
Auto-Configur
-Configure
e procedure, ConveyLinx Modules will configure
in ZP
ZPA
A mode. If one sensor is connected (either Left or Right) and two motors are connected,
the module is automatically configured as a single logical zone and will run both motors at the
same time. If the modules are at factory default, both motors will be at factory default settings.
Otherwise, the motor settings will be the ones last set by EasyRoll.
! Auto-Configuration of a two motor roller logical zone with an ERSC does not
automatically cause both motors to adopt the same motor settings.
For F
Fir
irmwar
mware
e 4.25 or OD
ODVVA Fir
irmwar
mware
e 5.02 and EasyR
EasyRoll
oll version 4.19
For F
Fir
irmwar
mware
e 4.27 and later or OD
ODVVA Fir
irmwar
mware
e 5.07 and later and EasyR
EasyRoll
oll
version 4.21
12.1.1.1. For F
Fir
irmwar
mware
e 4.25/5.02
Open L
Loop
oop
If open loop speed control is desired; then set both motors to the same settings in EasyRoll
Closed L
Loop
oop
When using closed loop control, it is important to never place both motors into closed loop
control because they will “fight” each other particularly when accelerating and decelerating.
Perform the following basic steps in EasyRoll for the selected ERSC module:
Place
discharge
end motor
in closed
loop and
infeed end
motor in
open loop
Force Run
and both
motors
should run
Enter
desired
speed for
the zone
for the
closed loop
motor
Enter slow
speed in
open loop
motor
Verify that
the open
loop motor
current is
non zero
and that
closed loop
current is
in the
range of
the rated
current
Adjust the
open loop
motor’s speed
until the
closed loop
motor’s
current is
approximately
500 to 800
mA
Please Note
that the
speed values
shown are
examples
only. The
actual speed
and current
values you
see may be
different
It is
important to
not set the
Open Loop
motor’s
speed so
high as to
make the
Closed Loop
motor’s
current draw
be 0 mA
In our
example,
previously
our setting of
65% speed
on the Open
Loop motor
resulted in
@500 mA
draw on the
Closed Loop
motor. But
an
adjustment
to 70%
speed on the
Open Loop
motor results
in 0 mA
current draw
on the
Closed Loop
motor. This
will
eventually
cause an
overheat
error on the
Closed Loop
motor.
12.1.1.2. For F
Fir
irmwar
mware
e 4.27/5.07 and
EasyR
EasyRoll
oll 4.21
This is automatically handled when you utilize the Slave F
Function
unction in EasyRoll
For F
Fir
irmwar
mware
e 4.25 or OD
ODVVA Fir
irmwar
mware
e 5.02
For F
Fir
irmwar
mware
e 4.27 and later or OD
ODVVA Fir
irmwar
mware
e 5.07 and later and EasyR
EasyRoll
oll
4.21 and later
12.1.2.1. For F
Fir
irmwar
mware
e 4.25/5.02
Open L
Loop
oop
If open loop control is acceptable for your application, simply set both motors to open loop and
use the same settings in EasyRoll and write your PLC logic to run both motors at the same time
and in the same direction.
Closed L
Loop
oop
You have two choices if you wish to used closed loop speed control: Independent and Master/
Slave.
Independent
With this method you set up closed loop as described above for ZP
ZPA
A mode. In your PLC logic,
you must run both motors at the same time and in the same direction.
Master / Slave
The ConveyLinx Module firmware has the capability when in PLC I/O mode to operate both
motors at the same time by setting one motor as a master and its settings will be used for both
motors. With this method, your PLC logic first configures the functionality and then only
logically controls the master motor.
Unfortunately, the register to configure this functionality (4:0015) is not included in any of the
PLC I/O mode assemblies. Your PLC code must utilize a MSG instruction to write to this
configuration register.
* Programming Tip: You can set up your MSG instruction to continually write to
Register 15, even though the ConveyLinx Module only needs to get written to
once. If continually sending a MSG instruction is of concern for conservation of
PLC resources; you can monitor the module’s Reset Counter register or AOI
Module Enable bit to trigger the MSG write to register 15 only when you detect
You should use these bits as pairs. Either use bits 0 and 1 or use bits 2 and 3. Setting both bits
0 and 2 will not work
work.
For example, if you set bit 0, then your program logic only needs to control the Left motor in
the PLC I/O instance assembly and the Right motor will have its settings internally controlled by
the module.
! Please note when using Master/Slave motor control, the ConveyLinx Module
ignores the EasyRoll settings for the slave motor
12.1.2.2. For F
Fir
irmwar
mware
e 4.27/5.07 and
EasyR
EasyRoll
oll 4.21
Functionality is provided within the defined PLC I/O Assembly. See the Lef
eftt Motor Contr
Control
ol topic
to configure the Left Motor as a slave and see the Right Motor Contr
Control
ol topic to configure the
Right Motor as a slave.
12.1.3. ConveyL
ConveyLogix
ogix P
Prrogram
You follow the same procedure as described for PLC I/O mode. You use the FirstLadderEx
irstLadderExec
ec
controller tag Boolean in a rung that executes a WR
WRCC block that writes the desired data to
Register 4:0015. By using the FirstLadderExec in this rung, it makes sure the data is written
upon any power up or re-boot of the ConveyLinx Module and that it is not continuously writing
the data every program scan and using up unnecessary module resources.
! THIS SECTION ONLY APPLIES TO FIRMWARE 4.25 AND OLDER AND 5.02 AND
OLDER. FOR FIRMWARE 4.27 / 5.07 AND NEWER THIS FUNCTIONALITY IS
PROVIDED AUTOMATICALLY THROUGH SET UP IN EASYROLL
Some Pulseroller models are available with two motors in one tube as shown.
! Regardless of which mode you will use, prior to performing the Auto
Configuration P
Prrocedur
ocedure
Auto--
e, unplug the motor cable opposite the ConveyLinx
Module
12.2.1. ZP
ZPA
A Mode
Once Auto
Auto-Configur
-Configuree is complete with the opposite motor cable unplugged, you can reconnect
this motor cable.
For F
Fir
irmwar
mware
e 4.25 or OD
ODVVA Fir
irmwar
mware
e 5.02
You follow the same procedures as described for ZPA Mode in section Mechanically Coupled 2
Motor Roller – ZPA Mode for both Open Loop and Closed Loop control.
! Be sure to change the rotation direction in EasyRoll for the opposite motor
For F
Fir
irmwar
mware
e 4.27 and later or OD
ODVVA Fir
irmwar
mware
e 5.07 and
later and EasyR
EasyRoll
oll 4.21
This is handled by the Motor Slave F
Function
unction in EasyRoll
! Be sure to select the appropriate “opposite dir.” selection from the Motor Slave
drop down selector
For F
Fir
irmwar
mware
e 4.25 or OD
ODVVA Fir
irmwar
mware
e 5.02
You have the same options as described in section Mechanically Coupled 2 Motor Roller – PLC I/
O Mode. For Open Loop control and Closed Loop – Independent control, remember to change
the direction of the opposite motor in EasyR
EasyRoll
oll. For Master/Slave control, be sure to remember
to set either bit 1 or bit 3 in Register 4:0015 to change the direction of the slave motor.
For F
Fir
irmwar
mware
e 4.27 and later or OD
ODVVA Fir
irmwar
mware
e 5.07 and
later and EasyR
EasyRoll
oll 4.21
Functionality is provided within the defined PLC I/O Assembly. See the Lef
eftt Motor Contr
Control
ol topic
to configure the Left Motor as a slave and see the Right Motor Contr
Control
ol topic to configure the
Right Motor as a slave.
! Be sure to use the appropriate “opposite direction” value for the Hi Byte in the
register
12.2.3. ConveyL
ConveyLogix
ogix P
Prrogram
Follow the exact procedure as described in section Mechanically Coupled 2 Motor R
Roller
oller –
ConveyL
ConveyLogix
ogix P
Prrogram
* Because the motors are not mechanically coupled, set the motor settings the
same in EasyR
EasyRoll
PLC I/O mode
oll and there are no other special things to do regardless of ZPA or
13. Connecting to R
Rockwell
ockwell PLCs with
Ether
Ethernet
net I/P
This manual will provide instructions on how to connect your Rockwell Ethernet I/P capable PLC
to a network of ConveyLinx modules. There are three basic methods for connecting ConveyLinx
to Rockwell PLCs:
All three methods can be used for ConveyLinx modules in ZPA mode and in PLC I/O mode.
However, the MSG Instruction method does not maintain a constant connection to a
ConveyLinx module and should not be used for “time critical” operations.
Ether
Ethernet
net I/P Guidelines
Each Allen-Bradley PLC has 2 metrics for limiting maintained Ethernet I/P communications to
remote devices:
If the limit of either of these quantities is reached, the PLC processor will indicate I/O
communications fault on one or more instances of device declaration. For ConveyLinx device
declarations utilizing either ZPA or PLC I/O Mode instances, in general the PLC limitation on TCP
connections will be reached before I/O data table memory limit is realized.
For example, for a CompactLogix L3x series processor, the documented quantity of TCP
connections available on its Ethernet Port is 32. The processor always keeps one TCP
connection in reserve for programming terminal access, etc. An L3x series processor can
accept 31 full-time ConveyLinx Connections as generic I/O modules utilizing any combination of
ZPA mode and PLC I/O Mode instances.
When a ConveyLinx module is attached as a “full-time generic I/O module” to the PLC, the
connection is continually maintained and data is exchanged at a minimum RPI value (referred
to as an implicit connection). If the PLC cannot communicate with the ConveyLinx module for
any reason, the PLC’s I/O tree will register a fault. It is possible for the PLC to communicate via
Ethernet I/P with any ConveyLinx module it can physically reach over its Ethernet port without
the module being “full-time connected as a generic I/O module”. This is accomplished with a
Logix5000 MSG instruction (referred to as explicit connection).
* Reserve Ethernet I/P TCP connections for ConveyLinx modules in PLC I/O Mode
* Use MSG Instruction to gather less time-critical data for things such as status
and diagnostics
13.1. Selecting Y
Your
our Connection Method
based upon Assembly
As described in our PLC Developer’s Guide, the data that you exchange with your PLC and a
given ConveyLinx module depends on the mode of the module and how you want to use it. The
I/O data to be exchanged are arranged in register Assemblies and depending on the assembly,
will dictate whether you can connect using the EDS file method or the Generic Ethernet Module
method.
All available assemblies can be connected utilizing the Generic Ethernet Module method and
only selected assemblies are available from the EDS file installation
Available as
Available
Generic
Assembly P
Pair
air fr
from
om EDS File
Ether
Ethernet
net
Installation
Module
Reduced Size PLC I/O Mode Assembly Inputs with Reset Protection
✔
Reduced Size PLC I/O Mode Assembly Outputs with Reset Protection
OD
ODVVA Compliant F
Fir
irmwar
mware
e 5.xx for ERSC
Pulseroller has been granted a Certificate of Conformity from ODVA for ConveyLinx ERSC
firmware version 5.02. The main difference between firmware 5.xx and previous versions (4.xx,
3.xx) as it pertains to connecting to ODVA compliant Ethernet I/P (EIP) PLC devices is that these
previous versions utilized Instance Identifiers that were classified as “reserved” by the ODVA
specification.
All Firmware 5.xx versions have re-assigned these identifiers into the allowable range for ODVA
compliance. The actual data registers and functionality of all EIP assemblies has remained
unchanged from the published assemblies in our PLC Developer’s Guide. The only thing that
has changed in version 5.xx is the value used for the Instance Identifiers when connecting to
the PLC. Firmware 4.25/4.27 recognizes both the previous and ODVA values for backward
compatibility if you happen to upgrade ERSC firmware from 4.24 (or earlier) to 4.25 or 4.27.
The following chart is a reference showing all the available assemblies and their respective
Instance Values used when connecting as a Generic Ethernet Device.
Recognized Instance V
Values
alues
Assembly
Pre 4.25 4.25/4.27 5.xx
ZPA Mode Assembly Inputs with Reset Protection 25 25 & 305 305
ZPA Mode Assembly Outputs with Reset Protection 26 26 & 306 306
PLC I/O Mode Assembly Inputs with Reset Protection 27 27 & 307 307
PLC I/O Mode Assembly Outputs with Reset Protection 28 28 & 308 308
Reduced Size PLC I/O Mode Assembly Inputs 17 17 & 117 117
Reduced Size PLC I/O Mode Assembly Outputs 18 18 & 118 118
Not
ConveyLogix Assembly Inputs 121 121
Available
Not
ConveyLogix Assembly Outputs 122 122
Available
13.3. Procedur
oceduree for Connecting using
Generic Ether
Ethernet
net Module
All assembly pairs can be connected to a single ERSC using the same procedure within RSLogix
5000 environment:
For example if you need to attach to 5 ERSC modules that are in ZPA Mode, each module will
have to have a unique name and I.P. address (step 3) and steps 4, 5, 6, and 7 will use the same
values for each ERSC.
https://www.youtube.com/embed/21vxtPUUWv8?rel=0
* Please note that for all Assemblies and all versions of firmware the Instance
value for the “Configuration” parameter is always “1” and its size is always “0”
For F
Fir
irmwar
mware
e 4.24 and Earlier
Input 5 21
ZP
ZPA
A Mode Assembly
Output 6 24
Input 25 21
ZP
ZPA
A Mode Assembly with R
Reset
eset P
Prrotection
Output 26 24
Input 7 23
PLC I/O Mode Assembly
Output 8 27
Input 27 23
PLC I/O Mode Assembly with R
Reset
eset P
Prrotection
Output 28 27
For F
Fir
irmwar
mware
e 4.25 and 4.27
Input 5 21
ZP
ZPA
A Mode Assembly
Output 6 25
Input 25 21
ZP
ZPA
A Mode Assembly with R
Reset
eset P
Prrotection
Output 26 25
Input 19 12
Reduced Size ZP
ZPA
A Mode Assembly
Output 20 15
Reduced Size ZP
ZPA
A Mode Assembly with R
Reset
eset Input 39 12
Protection Output 40 15
Input 7 23
PLC I/O Mode Assembly
Output 8 27
Input 27 23
PLC I/O Mode Assembly with R
Reset
eset P
Prrotection
Output 28 27
Input 17 9
Reduced Size PLC I/O Mode Assembly
Output 18 9
Input 121 16
ConveyL
ConveyLogix
ogix Assembly
Output 122 16
For F
Fir
irmwar
mware
e 5.02 and Higher
Input 105 21
ZP
ZPA
A Mode Assembly
Output 106 25
Input 305 21
ZP
ZPA
A Mode Assembly with R
Reset
eset P
Prrotection
Output 306 25
Input 119 12
Reduced Size ZP
ZPA
A Mode Assembly
Output 120 15
Reduced Size ZP
ZPA
A Mode Assembly with R
Reset
eset Input 319 12
Protection Output 320 15
Input 107 23
PLC I/O Mode Assembly
Output 108 27
Input 307 23
PLC I/O Mode Assembly with R
Reset
eset P
Prrotection
Output 308 27
Input 117 9
Reduced Size PLC I/O Mode Assembly
Output 118 9
Input 121 16
ConveyL
ConveyLogix
ogix Assembly
Output 122 16
13.4. Procedur
oceduree for using EDS Method
Selecting the P
Prroper EDS File
The first step is to select the proper EDS file based upon the firmware version of your
ConveyLinx ERSC modules. Our Pulseroller.com website contains all EDS files for download
including older versions. The following chart lists firmware version, operation mode, and EDS
file cross-reference information:
ERSC Fir
irmwar
mware
e ERSC Mode EDS File
! For best results, you should remove any previous ERSC EDS file(s) you may have
installed in your RSLogix 5000 environment before installing a version from this
list
! Delete all unused module data types from your program especially if you are
modifying or starting with an existing program
Installing the EDS file provided by Pulseroller into your RSLogix 5000 environment will allow
you to select the ERSC module from your list of known devices without having to use the
Generic Ethernet Module method. The EDS file contains the Instance and size parameters so
you do not have to fill in this information. When you connect to an ERSC, the data is arranged
in assembled registers with the data appearing in your Controller Tags similarly to how the data
appears when you connect to an ERSC as a Generic Ethernet Module.
https://www.youtube.com/embed/z28iBdmeRyg?rel=0
Selecting the P
Prroper AOI Instruction
AOI are imported to your specific PLC program file and not into the RSLogix 5000 environment
like an EDS file. The following chart provides a cross-reference for selecting the proper AOI file
based upon the ERSC firmware version and mode of operation
ERSC Fir
irmwar
mware
e ERSC Mode EDS File AOI File
PLC I/O
4.24 and Earlier ConveyLinx_PLC_IO_Instance_1.eds ERSC
ERSC_PLCIO_424.L5X
_PLCIO_424.L5X
Mode
4.25 ZP
ZPA
A Mode ConveyLinx_V5_6.eds ERSC
ERSC_ZP
_ZPA_425_5xx.L5X
A_425_5xx.L5X
PLC I/O
4.25 ConveyLinx_V5_6.eds ERSC
ERSC_PLCIO_425_5xx.L5X
_PLCIO_425_5xx.L5X
Mode
5.02 ZP
ZPA
A Mode ConveyLinx_V5_6.eds ERSC
ERSC_ZP
_ZPA_425_5xx.L5X
A_425_5xx.L5X
PLC I/O
5.02 ConveyLinx_V5_6.eds ERSC
ERSC_PLCIO_425_5xx.L5X
_PLCIO_425_5xx.L5X
Mode
4.27/5.07 ZP
ZPA
A Mode ConveyLinx_V5_6.eds ERSC
ERSC_ZP
_ZPA_427_507.L5X
A_427_507.L5X
PLC I/O
4.27/5.07 ConveyLinx_V5_6.eds ERSC
ERSC_PLCIO_425_507.L5X
_PLCIO_425_507.L5X
Mode
* Please refer to the downloads section of Pulseroller.com for the latest updates to
https://www.youtube.com/embed/dvkgMVEocoI?rel=0
13.5.1. AOI T
Tag
ag Descriptions
The following links take you to the listings for each tag made available in the both the
ERSC-ZPA AOI and the PLC I/O AOI.
13.5.1.1. ZP
ZPA
A Mode Inputs
* These tags ar
aree for AOI file ERSC
ERSC_ZP
_ZPA_427_507.L5X
A_427_507.L5X
Data Module
Tag Name Bit Description
Type Register
I_Contr
I_ControlP
olPortP
ortPin3_L
in3_Lef
eftt BOOL 4:0035 1 Left Control Port Pin 3 Energized
I_Contr
I_ControlP
olPortP
ortPin3_Right
in3_Right BOOL 4:0035 3 Right Control Port Pin 3 Energized
I_Contr
I_ControlP
olPortP
ortPin4_L
in4_Lef
eftt BOOL 4:0035 5 Left Control Port Pin 4 Energized
I_Contr
I_ControlP
olPortP
ortPin4_Right
in4_Right BOOL 4:0035 7 Right Control Port Pin 4 Energized
4:0201
(MSW) Current Forward Tracking Value at
I_GetF
I_GetForwar
orwardT
dTracking
racking DINT -
4:0202 Induct to Local Upstream Zone
(LSW)
4:0088
(MSW)
I_ModuleStatus DINT Modules Status Words 1 and 2
4:0089
(LSW)
I_MtrEr
I_MtrErrror_L
or_Lef
eftt BOOL 4:0088 3 Left Motor Error is Active
I_MtrEr
I_MtrErrror_Right BOOL 4:0089 3 Right Motor Error is Active
I_SensorP
I_SensorPortP
ortPin3_L
in3_Lef
eftt BOOL 4:0035 0 Left Sensor Port Pin 3 Energized
I_SensorP
I_SensorPortP
ortPin3_Right
in3_Right BOOL 4:0035 2 Right Sensor Port Pin 3 Energized
I_SensorP
I_SensorPortP
ortPin4_L
in4_Lef
eftt BOOL 4:0035 4 Left Sensor Port Pin 4 Energized
I_SensorP
I_SensorPortP
ortPin4_Right
in4_Right BOOL 4:0035 6 Right Sensor Port Pin 4 Energized
4:0199
(MSW) Current Tracking Value for Arrival
I_T
I_TrackingDNZn
rackingDNZn DINT -
4:0200 at Local Downstream Zone
(LSW)
4:0119
(MSW) Current Tracking Value for Arrival
I_T
I_TrackingUPZn
rackingUPZn DINT -
4:0120 at Local Upstream Zone
(LSW)
13.5.1.2. ZP
ZPA
A Mode Outputs
* These tags ar
aree for AOI file ERSC
ERSC_ZP
_ZPA_427_507.L5X
A_427_507.L5X
Data Module
Tag Name Bit Description
Type Register
O_ClearMotorEr
O_ClearMotorErrror BOOL 4:0022 0 Clear Motor Error Left & Right
O_Contr
O_ControlP
olPortOutputL
ortOutputLef
eftt BOOL 4:0063 1 Set Left Control Port Output
O_Contr
O_ControlP
olPortOutputRight
ortOutputRight BOOL 4:0063 3 Set Right COntrol Port Output
O_ConveyMer
O_ConveyMerge_DisableCenter
ge_DisableCenter BOOL 4:0387 4 Set to disable center release
O_ConveyMer
O_ConveyMerge_DisableL
ge_DisableLef
eftt BOOL 4:0387 5 Set to disable left release
O_ConveyMer
O_ConveyMerge_DisableRight
ge_DisableRight BOOL 4:0387 6 Set to disable right release
AOI
O_EnableModule BOOL - Enable Output to ERSC
Logic
O_SpeedL
O_SpeedLef
eftMtr
tMtr INT 4:0040 - Set Left Motor Speed Reference
4:0212
(MSW) Set Tracking Value for Local
O_T
O_TrackingDNZn
rackingDNZn DINT -
4:0213 Downstream Zone
(LSW)
4:0139
(MSW) Set Forward Induct Tracking
O_T
O_TrackingInductFwd
rackingInductFwd DINT -
4:0140 Value
(LSW)
4:0132
(MSW) Set Tracking Value for Local
O_T
O_TrackingUPZn
rackingUPZn DINT -
4:0133 Upstream Zone
(LSW)
O_W
O_Wak
akeUpUPZn
eUpUPZn BOOL 4:0104 12 Wakeup Local Upstream Zone
* These tags ar
aree for AOI file ERSC
ERSC_PLCIO_427_507.L5X
_PLCIO_427_507.L5X
Data Module
Tag Name Bit Description
Type Register
I_Contr
I_ControlP
olPortP
ortPin3_L
in3_Lef
eftt BOOL 4:0019 1 Port Inputs
I_Contr
I_ControlP
olPortP
ortPin3_Right
in3_Right BOOL 4:0035 3 Port Inputs
I_Contr
I_ControlP
olPortP
ortPin4_L
in4_Lef
eftt BOOL 4:0035 5 Port Inputs
I_Contr
I_ControlP
olPortP
ortPin4_Right
in4_Right BOOL 4:0035 7 Port Inputs
I_ConveyStopByL
I_ConveyStopByLef
eftContr
tControlP
olPort
ort BOOL 4:0019 8 ConveyStop
I_ConveyStopByL
I_ConveyStopByLostConnection
ostConnection BOOL 4:0019 6 ConveyStop
I_ConveyStopByR
I_ConveyStopByRemoteModule
emoteModule BOOL 4:0019 5 ConveyStop
I_ConveyStopByRightContr
I_ConveyStopByRightControlP
olPort
ort BOOL 4:0019 9 ConveyStop
I_DigitalMtrOverCur
I_DigitalMtrOverCurrrent_L
ent_Lef
eftt BOOL 4:0060 14 Left Motor Port as Digital
I_DigitalMtrOverCur
I_DigitalMtrOverCurrrent_Right BOOL 4:0084 14 Right Motor Port as Digital
I_DigitalMtrShortCkt_L
I_DigitalMtrShortCkt_Lef
eftt BOOL 4:0060 12 Left Motor Port as Digital
I_Downstr
I_DownstreamModuleStatus
eamModuleStatus SINT 4:0232 Lo Byte Module Status
I_ModuleV
I_ModuleVoltage
oltage REAL 4:0024 - Module Status
I_MtrCur
I_MtrCurrrent_L
ent_Lef
eftt REAL 4:0055 - Left Motor Status
I_MtrCur
I_MtrCurrrent_Right REAL 4:0079 - Right Motor Status
I_MtrF
I_MtrFrreq_L
eq_Lef
eftt INT 4:0056 - Left Motor Status
I_MtrF
I_MtrFrreq_Right INT 4:0080 - Right Motor Status
AOI
I_MtrR
I_MtrRunningCCW_L
unningCCW_Lef
eftt BOOL 4:0058 Left Motor Status
Logic
AOI
I_MtrR
I_MtrRunningCCW_Right
unningCCW_Right BOOL 4:0082 Right Motor Status
Logic
AOI
I_MtrR
I_MtrRunningCW_L
unningCW_Lef
eftt BOOL 4:0058 Left Motor Status
Logic
AOI
I_MtrR
I_MtrRunningCW_Right
unningCW_Right BOOL 4:0082 Right Motor Status
Logic
I_MtrStatus_L
I_MtrStatus_Lef
eftt INT 4:0058 - Left Motor Status
I_SensorDetectL
I_SensorDetectLef
eftP
tPort
ort BOOL 4:0036 1 Sensor Port Status
I_SensorDetectRightP
I_SensorDetectRightPort
ort BOOL 4:0036 0 Sensor Port Status
I_SensorP
I_SensorPortP
ortPin3_L
in3_Lef
eftt BOOL 4:0035 0 Port Inputs
I_SensorP
I_SensorPortP
ortPin3_Right
in3_Right BOOL 4:0035 2 Port Inputs
I_SensorP
I_SensorPortP
ortPin4_L
in4_Lef
eftt BOOL 4:0035 4 Port Inputs
I_SensorP
I_SensorPortP
ortPin4_Right
in4_Right BOOL 4:0035 6 Port Inputs
I_ServoCmdStatus_L
I_ServoCmdStatus_Lef
eftt BOOL 4:0011 2 Left Servo Function
I_ServoLastCmdComplete_L
I_ServoLastCmdComplete_Lef
eftt BOOL 4:0011 0 Left Servo Function
I_ServoP
I_ServoPosition_L
osition_Lef
eftt INT 4:0062 - Left Servo Function
I_ServoP
I_ServoPosition_Right
osition_Right INT 4:0086 - Right Servo Function
I_ServoR
I_ServoResetStatus_L
esetStatus_Lef
eftt BOOL 4:0011 1 Left Servo Function
I_ServoR
I_ServoResetStatus_Right
esetStatus_Right BOOL 4:0016 1 Right Servo Function
I_T
I_Temperatur
emperatureCalculated_L
eCalculated_Lef
eftt SINT 4:0057 Hi Byte Left Motor Status
I_T
I_Temperatur
emperatureCalculated_Right
eCalculated_Right SINT 4:0081 Hi Byte Right Motor Status
I_T
I_Temperatur
emperatureOnBoar
eOnBoard_L
d_Lef
eftt SINT 4:0057 Lo Byte Left Motor Status
I_T
I_Temperatur
emperatureOnBoar
eOnBoard_Right
d_Right SINT 4:0081 Lo Byte Right Motor Status
I_Upstr
I_UpstreamModuleStatus
eamModuleStatus SINT 4:0134 Lo Byte ZPA Status
4:0139
(MSW)
I_Upstr
I_UpstreamT
eamTracking
racking DINT - ZPA Tracking
4:0140
(LSW)
* These tags ar
aree for AOI file ERSC
ERSC_PLCIO_427_507.L5X
_PLCIO_427_507.L5X
Data Module
Tag Name Bit Description
Type Register
Lo
O_Brak
O_BrakeMethod_L
eMethod_Lef
eftt SINT 4:0261 Left Motor Control
Byte
Lo
O_Brak
O_BrakeMethod_Right
eMethod_Right SINT 4:0271 Right Motor Control
Byte
O_ClearMotorEr
O_ClearMotorErrror BOOL 4:0022 Motor Control
O_Contr
O_ControlP
olPortOutput_L
ortOutput_Lef
eftt BOOL 4:0037 1 Left Motor Control
O_Contr
O_ControlP
olPortOutput_Right
ortOutput_Right BOOL 4:0037 3 Right Motor Control
Sensor/Control Port
O_Contr
O_ControlP
olPortP
ortPin3Mask_L
in3Mask_Lef
eftt BOOL 4:0034 1
Configuration
Sensor/Control Port
O_Contr
O_ControlP
olPortP
ortPin3Mask_Right
in3Mask_Right BOOL 4:0034 3
Configuration
Sensor/Control Port
O_Contr
O_ControlP
olPortP
ortPin4Mask_L
in4Mask_Lef
eftt BOOL 4:0034 5
Configuration
Sensor/Control Port
O_Contr
O_ControlP
olPortP
ortPin4Mask_Right
in4Mask_Right BOOL 4:0034 7
Configuration
4:0201
(MSW)
O_Dischar
O_DischargeT
geTracking
racking DINT ZPA Tracking
4:0202
(LSW)
Lo
O_Downstr
O_DownstreamStatus
eamStatus SINT 4:0196 ZPA Status
Byte
O_L
O_Lef
eftMtrDigitalP
tMtrDigitalPin3
in3 BOOL 4:0060 0 Left Motor Port Digital Control
O_L
O_Lef
eftMtrDigitalP
tMtrDigitalPin4
in4 BOOL 4:0060 1 Left Motor Port Digital Control
O_L
O_Lef
eftMtrDigitalP
tMtrDigitalPin5
in5 BOOL 4:0060 2 Left Motor Port Digital Control
O_MtrA
O_MtrAccel_L
ccel_Lef
eftt INT 4:0043 Left Motor Control
O_MtrA
O_MtrAccel_Right
ccel_Right INT 4:0067 Right Motor Control
O_MtrDecel_L
O_MtrDecel_Lef
eftt INT 4:0044 Left Motor Control
O_Mtr_R
O_Mtr_Run_L
un_Lef
eftt BOOL 4:0260 0 Left Motor Control
O_Mtr_R
O_Mtr_Run_Right
un_Right BOOL 4:0270 0 Right Motor Control
O_Mtr_Dir_L
O_Mtr_Dir_Lef
eftt BOOL 4:0260 8 Left Motor Control
Hi
O_Mtr_Slave_Mode_L
O_Mtr_Slave_Mode_Lef
eftt SINT 4:0260 Left Motor Control
Byte
Hi
O_Mtr_Slave_Mode_Right SINT 4:0260 Right Motor Control
Byte
Sensor/Control Port
O_SensorP
O_SensorPortP
ortPin3Mask_L
in3Mask_Lef
eftt BOOL 4:0034 0
Configuration
Sensor/Control Port
O_SensorP
O_SensorPortP
ortPin3Mask_Right
in3Mask_Right BOOL 4:0034 2
Configuration
Sensor/Control Port
O_SensorP
O_SensorPortP
ortPin4Mask_L
in4Mask_Lef
eftt BOOL 4:0034 4
Configuration
Sensor/Control Port
O_SensorP
O_SensorPortP
ortPin4Mask_Right
in4Mask_Right BOOL 4:0034 6
Configuration
O_ServoCmdP
O_ServoCmdPulses_L
ulses_Lef
eftt INT 4:0008 Left Servo Function
O_ServoCmdP
O_ServoCmdPulses_Right
ulses_Right INT 4:0013 Right Servo Function
O_ServoGoCmd_L
O_ServoGoCmd_Lef
eftt BOOL 4:0009 1 Left Servo Function
O_ServoZer
O_ServoZero_L
o_Lef
eftt BOOL 4:0009 0 Left Servo Function
O_ServoZer
O_ServoZero_Right
o_Right BOOL 4:0014 0 Right Servo Function
O_L
O_Lef
eftMtrDigital_Enable
tMtrDigital_Enable BOOL 4:0060 15 Left Motor Port Digital Control
Lo
O_SpeedMethod_L
O_SpeedMethod_Lef
eftt SINT 4:0262 Left Motor Control
Byte
Lo
O_SpeedMethod_Right SINT 4:0272 Right Motor Control
Byte
O_SpeedR
O_SpeedRefer
eference_L
ence_Lef
eftt INT 4:0040 Left Motor Control
O_SpeedR
O_SpeedRefer
eference_Right
ence_Right INT 4:0064 Right Motor Control
Lo
O_Upstr
O_UpstreamStatus
eamStatus SINT 4:0116 ZPA Status
Byte
13.6. Using L
Logix
ogix 5000 MSG Instruction
Access to ConveyLinx ERSC modules is also available utilizing the Logix 5000 MSG instruction.
The MSG instruction utilizes CIP Explicit Messaging. This means that the connection is not
maintained as an implicit connection. Generic Ethernet Module and EDS connections are
implicit and thus must be maintained at all times or there will be a communication fault.
Explicit Messaging opens the connection, reads/writes data, and then closes the connection
thus freeing up communications resources for the PLC.
Because the MSG instruction is executed asynchronous to program scan and is not subject to
implicit messaging RPI restrictions; the response time between requesting data and receiving
data is not deterministic and can vary between separate requests for the same data from the
ecommend that MSG instructions should not be used for dedicated
same device. Therefore, we rrecommend
“real time” contr
control equipment. For ConveyLinx ERSC modules, MSG instructions are intended
ol of equipment
to gather “low priority” status information and/or to send infrequent parameter changes.
Please note that this is only a recommendation. Your particular application’s specifics, PLC’s
capacity, available network bandwidth, etc. may allow you to get expected results with “real
time” control utilizing MSG instructions to interface with ERSC modules.
Module Addresses are the 512 “actual” registers in the module and and Assemblies are
“virtual” registers grouped based upon function. There are certain restrictions on what you can
do with a MSG Instruction:
• You can us a single MSG instruction to read one and up to 30 consecutive Module
registers
• You can use a single MSG instruction to write to one (an only one) of the Module registers
• You can use a single MSG instruction to read any of the available Input Assembly registers
in their entirety
• You CANNOT use any MSG instruction to write to any Output Assembly registers.
From the Service Type drop down, select Get Attribute Single
For the Attribute Field, enter “2” because we want to read 4:0088 and 4:0089
For the Destination Element, use the Tag Browser drop down to select TempDiagStatus
From the Service Type drop down, select Set Attribute Single
For the Source Element, use the Tag Browser drop down to select NewSpeed
For this example, we have created an ERSC module in our Ethernet Tree and added a MSG
Instruction to a ladder rung. We named this MSG block “ReadZPA” and created the Controller
Tag for it. With this MSG Instruction we are going to read all 21 registers from PLC Inputs for
ZPA Mode. We also created a Controller Tag called “ZPA_Inputs” which is an INT array of 21
elements in order to hold the data.
* When reading any input Assembly with a MSG Instruction, be sure you create the
Destination Element Controller Tag an array of INT with the number of elements
that match the number of registers in the Assembly
From the Service Type drop down, select Get Attribute Single
For the Instance Field, enter “105” which is the Assembly vale for the ZPA Mode inputs
For the Destination Element, use the Tag Browser drop down to select ZPA_Inputs and
expand to select the [0] element
In situations where you may inherit an existing program and your RSLogix 5000 environment is
missing the EDS file used for this program; you will need to determine which version of EDS file
was used and then go find it on our Pulseroller.com web site. Similarly, you may also have the
situation where you need to be able to match your AOI version to its correct EDS file. The
following chart cross references the most common EDS files, AOI files, and Module Data Types
4.25 / _055C:ERSC_84EED4D3:I:0
ERSC_ZPA_5_2.L5X 5.02 and
newer _055C:ERSC_3015BAF1:O:0
ConveyLinx_V5_4.eds
4.25 / _055C:ERSC_C92675D8:I:0
ERSC_PLCIO_5_2.L5X 5.02 and
newer _055C:ERSC_7DDD1BFA:O:0
4.25 / _055C:ERSC_84EED4D3:I:0
ERSC_ZPA_425_5xx.L5X 5.02 and
newer _055C:ERSC_3015BAF1:O:0
ConveyLinx_V5_6.eds
4.25 / _055C:ERSC_C92675D8:I:0
ERSC_PLCIO_425_5xx.L5X 5.02 and
newer _055C:ERSC_7DDD1BFA:O:0
4.24 and
ConveyLinx_PLC_IO_Instance.eds ERSC_PLCIO_424.L5X _055C:ERSC_PLCIO_C92675D8:
older
_055C:ERSC_PLCIO_7DDD1BFA:O
! This section assumes you have a solid working knowledge of both Siemens PLC’s
and the TIA Portal or Step7 manager development environments.
! This section applies to all ConveyLinx Family modules. Figures and software
screenshots may only show ConveyLinx-Ai Family examples, but the concepts are
applicable to all ConveyLinx modules
S7 PLCs from Siemens can use ConveyLinx modules because they support PROFINET IO
communication protocol and can act as PROFINET IO-devices with the S7 PLC acting as a
PROFINET IO controller. The PLC can connect in different ways to the same ConveyLinx module
based upon how you want to use it. Each of these different ways that the PLC can connect to a
given module is called a Device A Access
ccess PPoint
oint ((D AP)). For a given ConveyLinx module type or
DAP
family, your PLC programming environment needs a GSDML file installed so your environment
can display each of the DAP AP’s
’s available for that given module type or family. Each ConveyLinx
module family (ConveyLinx-ERSC, ConveyLinx-Ai, and ConveyLinx-ECO) has their own GSDML
file that contains all of its DAP information. Each DAP corresponds to a Mode of Operation of the
ConveyLinx module.
Preparing your P
Prrogramming Envir
Environment
onment
Understanding the ConveyLinx Module’s Modes of Operation
Device A
Access
ccess P
Points
oints ((D
DAP
AP))
The ProfiNet protocol allows for multiple access ways for a single physical device. This is called
a Device A
Access
ccess PPoint
oint or DAP. In essence each DAP allows the PLC to connect to the same
physical device in a different way from the other DAPs for that device. The number of DAPs a
device supports is vendor specific so every manufacturer decides how many access ways to
provide for their device.
After you install the appropriate GSDML file into your programming environment based upon
the ConveyLinx Family you are using, there will be two directories (or folders) of DAP
APss:
1. Contains the DAPs that are used when you want to use Separate ConveyLinx Auto
Auto--
Configuration by either Install Button (ConveyLinx-ERSC Family) or by EasyRoll
(ConveyLinx-Ai Family and ConveyLinx-ECO)
2. Contains DAPs that are used when you want to use Integrated Configuration Dir
Direct
ect fr
from
om
PLC Topology to detect the topology of your ConveyLinx network and configure all
modules
14.1. Preparing Y
Your
our P
Prrogramming
Envir
Environment
onment
In order to use ConveyLinx with your PLC, you need to install the proper configuration files into
your TIA Portal or STEP 7 programming environment. The files required will be included in a
downloadable .zip ararchive
chive fr
from
om our site and will include an xml with the filename structur
structuree
“GSDML
GSDML--V2.xx-IndustrialSof
V2.xx-IndustrialSoftwar
tware-ConveyLinx-yyyymmdd.xml”
e-ConveyLinx-yyyymmdd.xml” and at least 1 bitmap file ((.bmp)
with the graphic image of the particular module(s) for which the xml file specifies for your
Siemens programming environment.
* The files you will need are dependent on the specific Conveylinx module and
module firmware version you are using.
Full ZP
ZPA
A Mode
n this mode, ConveyLinx works as a one or two zone ZP
ZPAA contr
controller
oller. When communicating with
module in this mode, the S7-300 PLC can control mainly material handling properties such as
accumulation, release, wake-up/full stop, read/write tracking, MDR parameters (speed,
acceleration and deceleration), and ConveyStop. In this mode the PLC does not have access to
directly control start/stop of MDRs because internal ZPA logic is operating the module. When
communicating with ConveyLinx in ZPA mode, the PLC does not require fast reaction time as
would be expected for a remote I/O device. Typically, 32 ms to 256 ms is the range of response
time utilized between the PLC and a ConveyLinx module in ZPA mode. The data array instance
lengths for input and output data mode are 64 bytes.
Reduced ZP
ZPA
A Mode
In this mode, the ConveyLinx modules operates as a one or two zone ZP ZPAA contr
controller
oller just like the
Full ZPA Mode. However, the instance data presented to the S7-300 PLC is limited to basic
material handling properties such as accumulation, release, wake-up/full stop, and MDR speed.
In this mode, because the instances length is reduced to 30 bytes; the PLC may be able to
accommodate more modules especially in applications where all ZPA features (such as
tracking) are not required. Similarly to the Full ZPA Mode, the 32 ms to 256 ms response time is
typical for this mode.
Mer
Merger
ger Mode
In this mode, the module is running in ZP
ZPA
A mode and exchanging 64 bytes of data with the PLC.
In addition to the ZPA logic, the module now runs the Merger task on one of their zones.
Configuring the Merger zone, differs between the two configuration methods (see Configuration
methods chapter). Similarly to the Full ZPA Mode, the 32 ms to 256 ms response time is typical
for this mode. The exchanged data is the same as for the Full ZPA mode.
handling control and tracking data support. A ConveyLinx module in PLC I/O mode is also
capable of Servo functions that are made available to the PLC. In this mode, the ConveyLinx
module responds as would be expected for a remote I/O device. ConveyLinx will connect to the
PLC with a 4 ms communication response time. The data array instance lengths for input and
output data in this mode are 64 bytes.
PLC Contr
Controlled
olled Mode with ConveyL
ConveyLogix
ogix P
Prrogram
In this mode, the ConveyLinx module has been programmed with ConveyLogix and this
program is running inside. ConveyLogix allows you to write your own programs and download it
to the ConveyLinx module turning it into a small PLC. The ToPLCArray(WORD [16] ) and
FromPLCArray(WORD [16]) are exchanged with the PLC. What data is exchanged in those data
arrays, is programmed by the engineer in the ConveyLogix program and in the PLC. The
communication response time should be adjusted by the programmer, based on the size and
complexity of the ConveyLogix program. The bigger it is, the higher update speeds should be
selected.
! Before going further, you will need to decide which of these two methods you are
going to use!
* Changing parameters like motor settings, ZPA functionality, etc. can be done
for multiple modules all at once with EasyRoll
* Your PLC only has to connect to modules it needs to interface with and not
every module in the network
* ZPA Extension function is able to be configured
! This method is only available for ConveyLinx-ERSC Family for 4 series firmware
4.27 and higher and 5 series firmware 5.03 and higher
When using this method, you create your network topology within the Siemens PLC
programming environment (TIA Portal or STEP 7). All pertinent module parameters become
available within your environment and can be configured at design time. As long as your
physical installed network topology of control modules matches your designed topology in your
PLC programming environment; when you download your project to your PLC, the PLC takes
care of all of the ConveyLinx control module configuration.
Advantages of Configuration fr
from
om PLC Topology
opology::
Disadvantages to Configuration fr
from
om PLC Topology
opology::
! This section applies ONLY when you use Separate ConveyLinx Auto-Configuration
(EasyRoll or ConveyLinx module Install button)
* The Mode of Operation of a given ConveyLinx module will determine which of the
DAP
APss to drag and drop from the Har
Hardwar
dware
e Catalog window into your project
The following chart shows the exact syntax for Profinet Names:
* Please do not confuse the module’s General Name or Project Name that you
assign for a given device with its Profinet Name
Name. The Profinet Name is required to
be in the proper syntax or the module will not connect to the PLC. The module’s
Project Name is completely user’s choice to identify the module in the your
Siemens programming environment and is what is displayed in your project’s
Network View(s) and Project Tree.
14.4.2. Examples of A
Adding
dding Modules
In this section we will provide an example that will add a single module of each Mode to a
project. This will require a combination of selecting the proper DAP from the Hardware catalog
coupled with using the correct Profinet Name to achieve our desired result. The following chart
lists the 6 modules we want to add to our project and the proper Device and Profinet Name
syntax needed.
DAP fr
from
om
Module
I.P
I.P.. A
Addr
ddress
ess Har
Hardwar
dware
e Profinet Name
Mode
Catalog
Full PLC
192.168.101.21 ConveyLinx-Ai conveylinxplc-101-21
Controlled
ConveyLinx-Ai in
Reduced
192.168.101.22 reduced ZPA conveylinxzpa-101-22
ZPA
mode
Reduced ConveyLinx-Ai in
PLC 192.168.20.123 reduced PLC conveylinxplc-20-123
Controlled mode
ConveyLinx-Ai in
ConveyLogix
192.168.0.22 PLC mode with conveylogix-0-22
Interface
ConveyLogix
* The following sections will show the details of adding each of these items to you
TIA Portal environment
14.4.2.1. Full ZP
ZPA
A
STEP 1: A
Add
dd the Module to the PLC Network
In the Project T
Trree locate
your newly created
module under the
Ungr
Ungrouped
ouped devices folder.
Right Click on your module
to show a pop-up menu
and select Properties
14.4.2.3. Reduced ZP
ZPA
A
STEP 1: A
Add
dd the Module to the PLC Network
14.4.2.5. Mer
Merger
ger Mode
The Mer
Merge
ge function is configured in EasyR
EasyRoll
oll. Follow the exact same steps as for a Full ZPA
module to add a module that will eventually be configured as merging zone in EasyR
EasyRoll
oll
* The CPU usage on a ConveyLinx module can be viewed when you go on-line with
the ConveyLogix programming software
The following table provides the recommended Update times based upon CPU usage of your
ConveyLogix program.
Minimum
CPU Usage Recommended
Update T
Time
ime
! Using a faster than recommended Update Time may produce unexpected results.
! This section applies ONLY when you use TIA Portal or STEP 7 Manager Topology to
configure your ConveyLinx modules
* The Mode of Operation of a given ConveyLinx module will determine which of the
DAP
APss to drag and drop from the Har
Hardwar
dware
e Catalog window into your project
* For users new to ConveyLinx and are familiar with the Siemens platform should
find the Integrated PLC Topology Configuration quicker and easier to implement.
! Please note that Step7 Manager will not auto-correct if you enter a non-
compliant name. A frequent mistake is using upper case letters which are not
allowed according to the Profinet standard. TIA Portal will autocorrect upper case,
but Step7 Manager will not auto-correct and will eventually result in program
error.
Update T
Time
ime
The DAPs for Integrated PLC Topology Configuration are already pre-configured with the lowest
recommended Update time for the given functionality. This means that you can skip STEP 4
when adding your modules.
DAP fr
from
om
Module Profinet
I.P
I.P.. A
Addr
ddress
ess Har
Hardwar
dware
e
Mode Name
Catalog
ConveyLinx-
Full ZPA 192.168.0.20 Ai in ZPA feeder
mode
ConveyLinx-
ConveyLogix Ai in PLC
192.168.0.22 divert
Interface mode with
ConveyLogix
mode
ConveyLinx-
Reduced Ai in
192.168.10.20 spur
ZPA reduced ZPA
mode
ConveyLinx-
Reduced
Ai in
PLC 192.168.15.20 reject
reduced PLC
Controlled
mode
For this example, add these to your network in the same fashion as described earlier in the
Examples of Adding Modules section. Because our example is using a switch, you need to
select a Profinet switch from the Catalog. In our example we selected a SCLANCE XF204 four
port switch. Here is a view showing all the items added to our topology including the Profinet
switch and ConveyLinx modules.
When you are done with the 1st subnet of modules, it should look like the following:
* Note which port on the merge module is connected to which specific port on its
neighbor modules.
When you are done with the 2nd subnet of modules, it should look like the following:
The following sections show the various parameters you have access to for each of the DAPs
along with links to the corresponding EasyRoll explanations of the particular parameter:
14.5.4.1. ZP
ZPA/R
A/Reduced
educed ZP
ZPA
A Modes
General
Change Upstr
Upstream
eam ConveyLinx Connection.
If you want to perform the EasyR
EasyRoll
oll
equivalent of selecting “None” for the
connection, select the drop down option
“Connect the the module with the below IP
address” and enter “0” for each IP address
octet.
Change Downstr
Downstream
eam ConveyLinx
Connection. If you want to perform the
EasyR
EasyRoll
oll equivalent of selecting “None” for
the connection, select the drop down
option “Connect the the module with the
below IP address” and enter “0” for each IP
address octet.
14.5.4.1.1. Upstr
Upstream/Downstr
eam/Downstream
eam Zones
Timer
Change
value
the
Set zone’s when
logical
release mode using
polarity
of operation GAP
of the
Train
Sensor
Release
Configure
Sensor port to
accept Push
Pull type
sensor
Change
motor’s Default
Rotation
Direction
Enable/Disable
various zone
options
Set zone’s
Motor Type
Enter desired
Motor Speed
Change
motor’s Brake
Method
Enter desired
motor Accel/
Decel values
14.5.4.1.2. Upstr
Upstream/Downstr
eam/Downstream
eam Zone
Timing
These settings are only used if this given module is discharging onto another ConveyLinx
module that is configured as a Mer
Merger
ger. In EasyR
EasyRoll
oll this operation is performed when connected
to the Merger module’s Mer
Merge
ge Zone. The difference here is that you enter the I.P. address of
the Mer
Merger
ger module where the Mer
Mergege Zone is located. In the EasyR
EasyRoll
oll example you are
connected to the Mer
Merger
ger module’s Mer
Merge
ge Zone and you enter the I.P. address of the ZPA
module that is feeding the Mer
Merge
ge Zone. This function is depicted in an example in the
ConveyMer
ConveyMergege section.
14.5.4.2. PLC/R
PLC/Reduced
educed PLC Mode
General
Change Upstr
Upstream
eam ConveyLinx Connection.
If you want to perform the EasyR
EasyRoll
oll
equivalent of selecting “None” for the
connection, select the drop down option
“Connect the the module with the below IP
address” and enter “0” for each IP address
octet.
Change Downstr
Downstream
eam ConveyLinx
Connection. If you want to perform the
EasyR
EasyRoll
oll equivalent of selecting “None” for
the connection, select the drop down
option “Connect the the module with the
below IP address” and enter “0” for each IP
address octet.
Lef
eftt / Right Side Configuration
14.5.4.3. Mer
Merger
ger Mode
The Mer
Merger
ger DAP is essentially a Full ZP
ZPA
A mode module with an added parameter to configure
the mer
merger
ger. So the General, Upstream/Downstream Zones, and Upstream/Downstream Zone
Timing parameters are the same as previously described.
Mer
Merger
ger Configuration
14.5.4.4. ConveyL
ConveyLogix
ogix Mode
The ConveyL
ConveyLogix
ogix DAP is essentially the same as a Full PLC mode module, so the previous topic
for PLC/Reduced PLC Mode is identical for the ConveyLogix DAP.
1. R
Raw
aw Unmapped Dir
Direct
ect fr
from
om the Module
This method allows you to access the raw data to/from the array of I/O data defined in the DAP
directly from within one of you program blocks. You then initiate the communications using
GETIO/SETIO functions within your block. This method is typically only used by advanced
programmers or programmers who do not want to use tags or UDTs. This method is not
recommended for new users.
* This method is not recommended for new users or applications where multiple
programmers have to edit and understand the same program
With this method, you create separate program tags for the particular word/integer array
element you want to read or write to on a given module. This method would maybe be
desirable if you know you only need to access a small number of items from a given module
and not all available data. This method also requires that you have detailed knowledge of the
structure of the given module’s Input/Output Assembly Instances and operational mode as
defined in the Developer’s Guide. Also, this method does not allow for simple access to sub-
element items such as Boolean bits within a Word element.
* This method is not recommended in applications where you need to access more
than one or two data elements from a module because you have to manually
create individual tags for each element you want to access and it is not very sub-
element friendly.
With this method, you import a UDT file provided by Pulseroller that has pre-defined tags and
structures that match up with each operational mode available for the module. You then use
these intuitively named tags directly in your PLC program. This method allows you to have
access to all of the data that is made available to/from the module based upon its assigned
DAP and operational mode.
* Using the UDTs is the recommended method of data access with ConveyLinx
modules because these have been tested and verified by Pulseroller.
* This method is not recommended for new users or applications where multiple
programmers have to edit and understand the same program
With this method of data access, you are copying data to/from the module’s I/O memory
directly to your function block’s local variables by using the GETIO/SETIO instructions. The I/O
memory addresses for you module were assigned when you added the module to your project.
The memory locations are dependent upon the order you added them to you project and the
amount of memory used as defined in the DAP.
Example
You are creating a function block called Block_1 and you want to read the input data from and
write output data to the ConveyLinx module we created called workstation from our Topology
Example. For your local static variables in your Block_1, you need to set the Data types for your
in and out variables to be Ar
Array[0..31]
ray[0..31] of W
Wor
ordd. To read data to the local in variable you need to
use the GETIO function and to write data to the local out variable you need to use the SETIO
function. Both the GETIO and SETIO functions require an ID parameter which corresponds to the
specific module’s input and output memory.
* This method is not recommended in applications where you need to access more
than one or two data elements from a module because you have to manually
create individual tags for each element you want to access
This method allows you to create your own global tags with meaningful names and map them
to a specific Wor
ord
d address within a given module. To use this method you will have to be very
familiar with the Instance Assembly structure for the ConveyLinx Module
Example
In this example we want to read the sensor port inputs and be able to send a clear jam
command to the upstream zone on the ConveyLinx module we named feeder in our Topology
Example. We also want to read the sensor port inputs and control the left motor on the
ConveyLinx module we named workstation in our Topology Example.
Cr
Create
eate Tags for our feeder Module
Tags
the starting byte offset address. In our example, this means that the Sensor Port Inputs word
register data will be located at I address bytes 36 and 37. When we declare our tag with the W
syntax, it will know that the tag requires the 2 bytes beginning at I address 36.
Cr
Create
eate Tags for our workstation Module
Tags
* Using the UDTs is the recommended method of data access with ConveyLinx
modules because these have been tested and verified by Pulseroller.
Each given DAP consumes some number of input memory bytes and output memory bytes.
When you use UDT
UDTss and create tags with the UDT data types; the PLC
PLC’s
’s I/O memory is properly
allocated and the memory boundaries between modules are easily established.
Ai F
Family
amily DAP
APss when using Separate ConveyLinx Auto
Auto--
Configuration
Module Module Input Output
Input UDT Output UDT
Mode Mode Bytes Bytes
ConveyLinx
Full ZPA 64 CLXAiZPA_IN 64 CLXAiZPA_OUT
Ai
ConveyLinx
Reduced Ai in
30 CLXAiZPAmini_IN 30 CLXAiZPAmini_OUT
ZPA reduced ZPA
mode
ConveyLinx
Full PLC 64 CLXAiPLC_IN 64 CLXAiPLC_OUT
Ai
ConveyLinx
Reduced Ai in
16 CLXAiPLCmini_IN 16 CLXAiPLCmini_OUT
PLC reduced PLC
mode
ConveyLinx
PLC with Ai in PLC
32 N/A 32 N/A
ConveyLogix mode with
ConveyLogix
Ai F
Family
amily DAP
APss when using T
Topology
opology Configuration
Module Module Input Output
Input UDT Output UDT
Mode Mode Bytes Bytes
ConveyLinx
Full ZPA Ai in ZPA 64 CLXAiZPA_IN 64 CLXAiZPA_OUT
mode
ConveyLinx
Reduced Ai in
30 CLXAiZPAmini_IN 30 CLXAiZPAmini_OUT
ZPA reduced ZPA
mode
ConveyLinx
Full PLC Ai in PLC 64 CLXAiPLC_IN 64 CLXAiPLC_OUT
mode
ConveyLinx
Reduced Ai in
16 CLXAiPLCmini_IN 16 CLXAiPLCmini_OUT
PLC reduced PLC
mode
ConveyLinx
PLC with Ai in PLC
32 N/A 32 N/A
ConveyLogix mode with
ConveyLogix
ConveyLinx
Full ZPA 64 CLXERSCZPA_IN 64 CLXERSCZPA_OUT
in ZPA mode
ConveyLinx
Reduced
in reduced 30 CLXERSCZPAmini_IN 30 CLXERSCZPAmini_OUT
ZPA
ZPA mode
ConveyLinx
Full PLC 64 CLXERSCPLC_IN 64 CLXERSCPLC_OUT
in PLC mode
in reduced
PLC
PLC mode
ConveyLinx
PLC with in PLC mode
32 N/A 32 N/A
ConveyLogix with
ConveyLogix
ConveyLinx
Full ZPA 64 CLXERSCZPA_IN 64 CLXERSCZPA_OUT
in ZPA mode
ConveyLinx
Reduced
in reduced 30 CLXERSCZPAmini_IN 30 CLXERSCZPAmini_OUT
ZPA
ZPA mode
ConveyLinx
Full PLC 64 CLXERSCPLC_IN 64 CLXERSCPLC_OUT
in PLC mode
ConveyLinx
Reduced
in reduced 16 CLXERSCPLCmini_IN 16 CLXERSCPLCmini_OUT
PLC
PLC mode
ConveyLinx
PLC with in PLC mode
32 N/A 32 N/A
ConveyLogix with
ConveyLogix
DAP fr
from
om
Profinet Module
Har
Hardwar
dware
e Input UDT Name Output UDT Name
Name Mode
Catalog
ConveyLinx-
feeder Full ZPA Ai in ZPA CLXAiZPA_IN CLXAiZPA_OUT
mode
ConveyLinx-
ConveyLogix Ai in PLC
divert N/A N/A
Interface mode with
ConveyLogix
ConveyLinx-
Full PLC
workstation Ai in PLC CLXAiPLC_IN CLXAiPLC_OUT
Controlled
mode
ConveyLinx-
Reduced Ai in
spur CLXAiZPAmini_IN CLXAiZPAmini_OUT
ZPA reduced ZPA
mode
ConveyLinx-
Reduced
Ai in
reject PLC CLXAiPLCmini_IN CLXAiPLCmini_OUT
reduced PLC
Controlled
mode
Adding R
Remaining
emaining Modules
For this example, you can access the divert module by either the Raw Unmapped Data Direct
from Module or Module Data Elements Mapped to Tags method previously described.
Each given DAP consumes some number of input memory bytes and output memory bytes.
When you use UDT
UDTss and create tags with the UDT data types; the PLC
PLC’s
’s I/O memory is properly
allocated and the memory boundaries between modules are easily established.
14.7.1. UDT
UDTss for ConveyLinx-ERSC F
Family
amily
Conveyor Contr
Control
ol DAP
APss for Separate ConveyLinx Auto
Auto--
Configuration
ConveyLinx Input Output
DAP fr
from
om Catalog
Mode Bytes Bytes
ConveyLinx in
Full ZPA 64 64
ZPA mode
ConveyLinx in
Full PLC 64 64
PLC mode
ConveyLinx in
PLC with
PLC mode with 32 32
ConveyLogix
ConveyLogix
ConveyLinx in
Reduced
reduced PLC 16 16
PLC
mode
ConveyLinx in
Reduced
reduced ZPA 30 30
ZPA
mode
Conveyor Contr
Control
ol DAP
APss for Integrated PLC Topology
Configuration
ConveyLinx Input Output
DAP fr
from
om Catalog
Mode Bytes Bytes
ConveyLinx in
Full PLC 64 64
PLC Mode
ConveyLinx in
PLC with
PLC mode with 32 32
ConveyLogix
ConveyLogix
Reduced ConveyLinx in
16 16
PLC reduced PLC
mode
ConveyLinx in
Reduced
reduced ZPA 30 30
ZPA
mode
ConveyLinx in
Full ZPA 64 64
ZPA mode
14.7.1.1. Full ZP
ZPA
A Mode Inputs
CLX
CLX_ERSC_ZP
_ERSC_ZPA_IN
A_IN
Element Name Sub Element Data T
Type
ype Link
LocalUpstr
ocalUpstreamZoneStatus_R
eamZoneStatus_Rev
ev Byte
LocalUpstr
ocalUpstreamZoneStatus_Fwd
eamZoneStatus_Fwd Byte More
LocalDownstr
ocalDownstreamZoneStatus_R
eamZoneStatus_Rev
ev Byte Info
LocalDownstr
ocalDownstreamZoneStatus_Fwd
eamZoneStatus_Fwd Byte
Ar
ArrivalCountUpstr
rivalCountUpstreamZone
eamZone Int
Departur
DepartureCountUpstr
eCountUpstreamZone
eamZone Int More
Ar
ArrivalCountDownstr
rivalCountDownstreamZone
eamZone Int Info
Departur
DepartureCountDownstr
eCountDownstreamZone
eamZone Int
Lef
eftMotorOver
tMotorOverheat
heat Bool
Lef
eftMotorMaxT
tMotorMaxTor
orque
que Bool
Lef
eftMotorShort
tMotorShort Bool
Lef
eftMotorNotConn
tMotorNotConn Bool
Lef
eftMotorOverload
tMotorOverload Bool
Lef
eftMotorStalled
tMotorStalled Bool
Lef
eftMotorBadHall
tMotorBadHall Bool
Lef
eftMotorNotUsed
tMotorNotUsed Bool More
Diagnostic
ModuleR
ModuleResetFlag
esetFlag Bool Info
Inde
Index06Bit01
x06Bit01 Bool
OverV
OverVoltage
oltage Bool
Lef
eftMotorAnyEr
tMotorAnyErrr Bool
ConnectionsNotOK Bool
Upstr
UpstreamJamEr
eamJamErrr Bool
Lef
eftSensL
tSensLowGain
owGain Bool
LowV
owVoltage
oltage Bool
RightMotorOver
RightMotorOverheat
heat Bool
RightMotorMaxT
RightMotorMaxTor
orque
que Bool
RightMotorShort Bool
RightMotorNotConn Bool
RightMotorOverload Bool
RightMotorStalled Bool
RightMotorBadHall Bool
RightMotorNotUsed Bool
Inde
Index07Bit00
x07Bit00 Bool
Inde
Index07Bit01
x07Bit01 Bool
OverV
OverVoltage1
oltage1 Bool
RightMotorAnyEr
RightMotorAnyErrr Bool
Inde
Index07Bit04
x07Bit04 Bool
Downstr
DownstreamJamEr
eamJamErrr Bool
RightSensL
RightSensLowGain
owGain Bool
LowV
owVoltage1
oltage1 Bool
TrackingUpstr
rackingUpstreamZone
eamZone DWord More
TrackingDownstr
rackingDownstreamZone
eamZone DWord Info
ReleaseCounterUpstr
eleaseCounterUpstreamZone
eamZone Int More
ReleaseCounterDownstr
eleaseCounterDownstreamZone
eamZone Int Info
GetDischar
GetDischargeT
geTracking_Fwd
racking_Fwd DWord More
GetDischar
GetDischargeT
geTracking_R
racking_Rev
ev DWord Info
Bit08 Bool
Bit09 Bool
Bit12 Bool
Bit13 Bool
Bit14 Bool
Heartbeat Bool
Lef
eftSensorP
tSensorPin3
in3 Bool
Lef
eftContr
tControlP
olPin3
in3 Bool
RightSensorP
RightSensorPin3
in3 Bool
RightContr
RightControlP
olPin3
in3 Bool
Lef
eftSensorP
tSensorPin4
in4 Bool
Lef
eftContr
tControlP
olPin4
in4 Bool
RightSensorP
RightSensorPin4
in4 Bool
RightContr
RightControlP
olPin4
in4 Bool
Inde
Index19
x19 Word
StopOnL
StopOnLef
eftt Bool
StopOnRight Bool
StopA
StopActiveCommandPLC
ctiveCommandPLC Bool
Bit11 Bool
Bit12 Bool
Bit13 Bool
Bit14 Bool
Bit01 Bool
Bit02 Bool
Bit03 Bool
Bit04 Bool
StopA
StopActiveOtherModule
ctiveOtherModule Bool
StopA
StopActiveL
ctiveLostConn
ostConn Bool
StopA
StopActiveL
ctiveLostPLC
ostPLC Bool
Futur
uture
e Array[21..31]
of Word
14.7.1.2. Full ZP
ZPA
A Mode Outputs
CLX
CLX_ERSC_ZP
_ERSC_ZPA_OUT
A_OUT
Element Name Sub Element Data T
Type
ype Link
InductT
InductTrackingOnUpstr
rackingOnUpstreamZone
eamZone DWord More
InductT
InductTrackingOnDownstr
rackingOnDownstreamZone
eamZone DWord Info
AccumUpstr
ccumUpstreamT
eamToThisZone
oThisZone Bool
SetAr
SetArrival
rival Bool
JogZoneFwd Bool
JogZoneR
JogZoneRev
ev Bool
Wak
akeUp
eUp Bool
MaintEnable Bool
Bit14 Bool
Bit01 Bool
Bit02 Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
AccumUpstr
ccumUpstreamT
eamToThisZone
oThisZone Bool
SetAr
SetArrival
rival Bool
Wak
akeUp
eUp Bool
MaintEnable Bool
Bit14 Bool
Bit15 Bool
Accumulate Bool
Bit01 Bool
Bit02 Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
SetSpeedL
SetSpeedLef
eftMotor
tMotor Int More
SetSpeedRightMotor Int Info
SetR
SetReleaseCountUpstr
eleaseCountUpstream
eam Int More
SetR
SetReleaseCountDownstr
eleaseCountDownstream
eam Int Info
SetInductT
SetInductTrackingFwd
rackingFwd DWord More
SetInductT
SetInductTrackingR
rackingRev
ev DWord Info
More
ClearMotorEr
ClearMotorErrror Word
Info
Bit08 Bool
Bit09 Bool
Bit10 Bool
Bit13 Bool
Bit14 Bool
Bit15 Bool
Bit00 Bool
Ener
EnergizeL
gizeLef
eftt Bool
Bit02 Bool
Ener
EnergizeRight
gizeRight Bool
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
Inde
Index18
x18 Word
More
ConveyStopContr
ConveyStopControl
ol Word
Info
ClearJamUpstr
ClearJamUpstream
eam Word More
ClearJamDownstr
ClearJamDownstream
eam Word Info
SetDir
SetDirectionContr
ectionControlUpstr
olUpstream
eam Word More
SetDir
SetDirectionContr
ectionControlDownstr
olDownstream
eam Word Info
More
ConveyMer
ConveyMerge
ge Word
Info
Array[25..31]
Futur
uture
e
of Word
14.7.1.3. Reduced ZP
ZPA
A Mode Inputs
CLX
CLX_ERSC_ZP
_ERSC_ZPA_R
A_Reduced_IN
educed_IN
Element Name Sub Element Data T
Type
ype Link
LocalUpstr
ocalUpstreamZoneStatus_R
eamZoneStatus_Rev
ev Byte
LocalUpstr
ocalUpstreamZoneStatus_Fwd
eamZoneStatus_Fwd Byte More
LocalDownstr
ocalDownstreamZoneStatus_R
eamZoneStatus_Rev
ev Byte Info
LocalDownstr
ocalDownstreamZoneStatus_Fwd
eamZoneStatus_Fwd Byte
Ar
ArrivalCountUpstr
rivalCountUpstreamZone
eamZone Int
Departur
DepartureCountUpstr
eCountUpstreamZone
eamZone Int More
Ar
ArrivalCountDownstr
rivalCountDownstreamZone
eamZone Int Info
Departur
DepartureCountDownstr
eCountDownstreamZone
eamZone Int
Lef
eftMotorOver
tMotorOverheat
heat Bool
Lef
eftMotorMaxT
tMotorMaxTor
orque
que Bool
Lef
eftMotorShort
tMotorShort Bool
Lef
eftMotorNotConn
tMotorNotConn Bool
Lef
eftMotorOverload
tMotorOverload Bool
Lef
eftMotorStalled
tMotorStalled Bool
Lef
eftMotorBadHall
tMotorBadHall Bool
Lef
eftMotorNotUsed
tMotorNotUsed Bool More
Diagnostic
ModuleR
ModuleResetFlag
esetFlag Bool Info
Inde
Index06Bit01
x06Bit01 Bool
OverV
OverVoltage
oltage Bool
Lef
eftMotorAnyEr
tMotorAnyErrr Bool
ConnectionsNotOK Bool
Upstr
UpstreamJamEr
eamJamErrr Bool
Lef
eftSensL
tSensLowGain
owGain Bool
LowV
owVoltage
oltage Bool
RightMotorOver
RightMotorOverheat
heat Bool
RightMotorMaxT
RightMotorMaxTor
orque
que Bool
RightMotorShort Bool
RightMotorNotConn Bool
RightMotorOverload Bool
RightMotorStalled Bool
RightMotorBadHall Bool
RightMotorNotUsed Bool
Inde
Index07Bit00
x07Bit00 Bool
Inde
Index07Bit01
x07Bit01 Bool
OverV
OverVoltage1
oltage1 Bool
RightMotorAnyEr
RightMotorAnyErrr Bool
Inde
Index07Bit04
x07Bit04 Bool
Downstr
DownstreamJamEr
eamJamErrr Bool
RightSensL
RightSensLowGain
owGain Bool
LowV
owVoltage1
oltage1 Bool
ReleaseCounterUpstr
eleaseCounterUpstreamZone
eamZone Int More
ReleaseCounterDownstr
eleaseCounterDownstreamZone
eamZone Int Info
Bit08 Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
Bit14 Bool
Heartbeat Bool
Lef
eftSensorP
tSensorPin3
in3 Bool
Lef
eftContr
tControlP
olPin3
in3 Bool
RightSensorP
RightSensorPin3
in3 Bool
RightContr
RightControlP
olPin3
in3 Bool
Lef
eftSensorP
tSensorPin4
in4 Bool
Lef
eftContr
tControlP
olPin4
in4 Bool
RightSensorP
RightSensorPin4
in4 Bool
RightContr
RightControlP
olPin4
in4 Bool
Array[11..14]
Futur
uture
e
of Word
14.7.1.4. Reduced ZP
ZPA
A Mode Outputs
CLX
CLX_ERSC_ZP
_ERSC_ZPA_R
A_Reduced_OUT
educed_OUT
Data
Element Name Sub Element Link
Type
AccumUpstr
ccumUpstreamT
eamToThisZone
oThisZone Bool
SetAr
SetArrival
rival Bool
JogZoneFwd Bool
JogZoneR
JogZoneRev
ev Bool
Wak
akeUp
eUp Bool
MaintEnable Bool
Bit14 Bool
Bit01 Bool
Bit02 Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
AccumUpstr
ccumUpstreamT
eamToThisZone
oThisZone Bool
SetAr
SetArrival
rival Bool
JogZoneFwd Bool
More
AccumulateContr
ccumulateControlDownstr
olDownstream
eam JogZoneR
JogZoneRev
ev Bool
Info
Wak
akeUp
eUp Bool
MaintEnable Bool
Bit14 Bool
Bit15 Bool
Accumulate Bool
Bit01 Bool
Bit02 Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
SetSpeedL
SetSpeedLef
eftMotor
tMotor Int More
SetSpeedRightMotor Int Info
SetR
SetReleaseCountUpstr
eleaseCountUpstream
eam Int More
SetR
SetReleaseCountDownstr
eleaseCountDownstream
eam Int Info
SetDishar
SetDishargeStatus
geStatus Word Info
More
ClearMotorEr
ClearMotorErrror Word
Info
Bit08 Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
Bit12 Bool
More
SetContr
SetControlP
olPortOutputs
ortOutputs Bit13 Bool
Info
Bit14 Bool
Bit15 Bool
Bit00 Bool
Ener
EnergizeL
gizeLef
eftt Bool
Bit02 Bool
Ener
EnergizeRight
gizeRight Bool
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
Inde
Index10
x10 Word
ClearJamUpstr
ClearJamUpstream
eam Word More
ClearJamDownstr
ClearJamDownstream
eam Word Info
SetDir
SetDirectionContr
ectionControlUpstr
olUpstream
eam Word More
SetDir
SetDirectionContr
ectionControlDownstr
olDownstream
eam Word Info
StopOnL
StopOnLef
eftt Bool
StopOnRight Bool
StopA
StopActiveCommandPLC
ctiveCommandPLC Bool
Bit11 Bool
Bit12 Bool
Bit13 Bool
Bit14 Bool
Bit01 Bool
Bit02 Bool
Bit03 Bool
Bit04 Bool
StopA
StopActiveOtherModule
ctiveOtherModule Bool
StopA
StopActiveL
ctiveLostConn
ostConn Bool
StopA
StopActiveL
ctiveLostPLC
ostPLC Bool
Bit08 Bool
Bit09 Bool
Bit10 Bool
Bit13 Bool
Bit14 Bool
Heartbeat Bool
Lef
eftSensorP
tSensorPin3
in3 Bool
Lef
eftContr
tControlP
olPin3
in3 Bool
RightSensorP
RightSensorPin3
in3 Bool
RightContr
RightControlP
olPin3
in3 Bool
Lef
eftSensorP
tSensorPin4
in4 Bool
Lef
eftContr
tControlP
olPin4
in4 Bool
RightSensorP
RightSensorPin4
in4 Bool
RightContr
RightControlP
olPin4
in4 Bool
Bits08_15 Byte
RightSensorDetect Bool
Lef
eftSensorDetect
tSensorDetect Bool
Bit02 Bool
More
SensorDetect Bit03 Bool
Info
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
More
ModuleV
ModuleVoltage
oltage Int
Info
Lef
eftMotorCur
tMotorCurrrent Int
Lef
eftMotorF
tMotorFrreq Int More
Lef
eftMotorCalcT
tMotorCalcTemp
emp Byte Info
Lef
eftModuleT
tModuleTemp
emp Byte
Over
Overheat
heat Bool
MaxT
MaxTor
orque
que Bool
More
Lef
eftMotorDiagnostic
tMotorDiagnostic ShortCir
ShortCircuit
cuit Bool
Info
MotorNotConnected Bool
Overload Bool
Stalled Bool
BadHall Bool
MotorNotUsed Bool
MotorStatus1 Bool
MotorStatus2 Bool
MotorP
MotorPortinDOmode
ortinDOmode Bool
Bit03 Bool
Bit04 Bool
Boar
BoardOver
dOverheat
heat Bool
OverV
OverVoltage
oltage Bool
LowV
owVoltage
oltage Bool
RightMotorCur
RightMotorCurrrent Int
RightMotorF
RightMotorFrreq Int More
RightMotorCalcT
RightMotorCalcTemp
emp Byte Info
RightModuleT
RightModuleTemp
emp Byte
Over
Overheat
heat Bool
MaxT
MaxTor
orque
que Bool
ShortCir
ShortCircuit
cuit Bool
MotorNotConnected Bool
Overload Bool
Stalled Bool
More
RightMotorDiagnostic BadHall Bool
Info
MotorNotUsed Bool
MotorStatus1 Bool
MotorStatus2 Bool
MotorP
MotorPortinDOmode
ortinDOmode Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
OverV
OverVoltage
oltage Bool
LowV
owVoltage
oltage Bool
Bit08 Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
More
Lef
eftMotorDIOstatus
tMotorDIOstatus ShortCir
ShortCircuit
cuit Bool
Info
Bit13 Bool
OverCur
OverCurrrent Bool
Bit15 Bool
Bits00_07 Byte
Bit08 Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
More
RightMotorDIOstatus ShortCir
ShortCircuit
cuit Bool
Info
Bit13 Bool
OverCur
OverCurrrent Bool
Bit15 Bool
Bits00_07 Byte
Upstr
UpstreamModuleStatus
eamModuleStatus Word
More
Downstr
DownstreamModuleStatus
eamModuleStatus Word
Info
TrackingF
rackingFrromUpstr
omUpstream
eam DWord
Inde
Index18
x18 Word
ServoL
ServoLocationL
ocationLef
eftt Int
More
ServoL
ServoLocationRight
ocationRight Int
Info
ServoStatusL
ServoStatusLef
eftt Word
ServoStatusRight Word
Array[23..31]
Futur
uture
e
of Word
More
ConveyStopContr
ConveyStopControl
ol Word
Info
ClearP
ClearPortEr
ortErrror Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
Bit12 Bool
Bit13 Bool
Bit14 Bool
Ener
EnergizeJSTP
gizeJSTPin4
in4 Bool
Ener
EnergizeJSTP
gizeJSTPin5
in5 Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
Ener
EnergizeJSTP
gizeJSTPin9
in9 Bool
EnableJSTP
EnableJSTPin9
in9 Bool
ClearP
ClearPortEr
ortErrror Bool
Bit09 Bool
Bit12 Bool
Bit13 Bool
Bit14 Bool
EnableMotDIO Bool
Ener
EnergizeJSTP
gizeJSTPin3
in3 Bool
Ener
EnergizeJSTP
gizeJSTPin4
in4 Bool
Ener
EnergizeJSTP
gizeJSTPin5
in5 Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
Ener
EnergizeJSTP
gizeJSTPin9
in9 Bool
EnableJSTP
EnableJSTPin9
in9 Bool
Bit08 Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
Bit12 Bool
Bit13 Bool
Bit14 Bool
Ener
EnergizeL
gizeLef
eftP
tPort
ort Bool
Bit02 Bool
Ener
EnergizeRightP
gizeRightPort
ort Bool
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
Dir
Direction
ection Bool More
Lef
eftMotorContr
tMotorControl
ol
Bit09 Bool Info
Bit10 Bool
Bit11 Bool
Bit12 Bool
Bit13 Bool
Bit14 Bool
Bit15 Bool
Run Bool
Bit01 Bool
Bit02 Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
SetL
SetLef
eftMotorBrak
tMotorBrakeMode
eMode Word More
SetL
SetLef
eftMotorSpeedMode
tMotorSpeedMode Word Info
Dir
Direction
ection Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
Bit12 Bool
Bit15 Bool
Run Bool
Bit01 Bool
Bit02 Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
SetRightMotorBrak
SetRightMotorBrakeMode
eMode Word More
SetRightMotorSpeedMode Word Info
More
SetSpeedL
SetSpeedLef
eftMotor
tMotor Int
Info
More
SetSpeedRightMotor Int
Info
SetL
SetLef
eftMotorA
tMotorAccel
ccel Int More
SetL
SetLef
eftMotorDeccel
tMotorDeccel Int Info
SetRightMotorA
SetRightMotorAccel
ccel Int More
SetRightMotorDeccel Int Info
More
ClearMotorEr
ClearMotorErrror Word
Info
SendStatusT
SendStatusToDownstr
oDownstream
eam Word More
SendStatusT
SendStatusToUpstr
oUpstream
eam Word Info
Bit08 Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
Bit12 Bool
More
SetSensorP
SetSensorPolarity
olarity Bit13 Bool
Info
Bit14 Bool
Bit15 Bool
Lef
eftSensorP
tSensorPin3
in3 Bool
Lef
eftContr
tControlP
olPin3
in3 Bool
RightSensorP
RightSensorPin3
in3 Bool
RightContr
RightControlP
olPin3
in3 Bool
Lef
eftSensorP
tSensorPin4
in4 Bool
Lef
eftContr
tControlP
olPin4
in4 Bool
RightSensorP
RightSensorPin4
in4 Bool
RightContr
RightControlP
olPin4
in4 Bool
More
TrackingT
rackingToDownstr
oDownstream
eam DWord
Info
Inde
Index22
x22 Word
ServoContr
ServoControlDistanceL
olDistanceLef
eftt Int
ServoContr
ServoControlCommandL
olCommandLef
eftt Word More
ServoContr
ServoControlDistanceRight
olDistanceRight Int Info
ServoContr
ServoControlCommandRight
olCommandRight Word
Array[27..31]
Futur
uture
e
of Word
Bit08 Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
Bit12 Bool
Bit13 Bool
Bit14 Bool
Lef
eftContr
tControlP
olPin3
in3 Bool
RightSensorP
RightSensorPin3
in3 Bool
RightContr
RightControlP
olPin3
in3 Bool
Lef
eftSensorP
tSensorPin4
in4 Bool
Lef
eftContr
tControlP
olPin4
in4 Bool
RightSensorP
RightSensorPin4
in4 Bool
RightContr
RightControlP
olPin4
in4 Bool
Bits08_15 Byte
RightSensorDetect Bool
Lef
eftSensorDetect
tSensorDetect Bool
More
SensorDetect Bit02 Bool
Info
Bit03 Bool
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
Lef
eftMotorCalcT
tMotorCalcTemp
emp Byte More
Lef
eftModuleT
tModuleTemp
emp Byte Info
Over
Overheat
heat Bool
MaxT
MaxTor
orque
que Bool
ShortCir
ShortCircuit
cuit Bool
MotorNotConnected Bool
Overload Bool
Stalled Bool
BadHall Bool
MotorStatus2 Bool
MotorP
MotorPortinDOmode
ortinDOmode Bool
Bit03 Bool
Bit04 Bool
Boar
BoardOver
dOverheat
heat Bool
OverV
OverVoltage
oltage Bool
LowV
owVoltage
oltage Bool
RightMotorCalcT
RightMotorCalcTemp
emp Byte More
RightModuleT
RightModuleTemp
emp Byte Info
Over
Overheat
heat Bool
MaxT
MaxTor
orque
que Bool
ShortCir
ShortCircuit
cuit Bool More
RightMotorDiagnostic
MotorNotConnected Bool Info
Overload Bool
Stalled Bool
BadHall Bool
MotorNotUsed Bool
MotorStatus1 Bool
MotorStatus2 Bool
MotorP
MotorPortinDOmode
ortinDOmode Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
OverV
OverVoltage
oltage Bool
LowV
owVoltage
oltage Bool
Bit08 Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
More
Lef
eftMotorDIOstatus
tMotorDIOstatus ShortCir
ShortCircuit
cuit Bool
Info
Bit13 Bool
OverCur
OverCurrrent Bool
Bit15 Bool
Bits00_07 Byte
Bit08 Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
More
RightMotorDIOstatus ShortCir
ShortCircuit
cuit Bool
Info
Bit13 Bool
OverCur
OverCurrrent Bool
Bit15 Bool
Bits00_07 Byte
ClearP
ClearPortEr
ortErrror Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
Bit12 Bool
Bit13 Bool
Bit14 Bool
Ener
EnergizeJSTP
gizeJSTPin4
in4 Bool
Ener
EnergizeJSTP
gizeJSTPin5
in5 Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
Ener
EnergizeJSTP
gizeJSTPin9
in9 Bool
EnableJSTP
EnableJSTPin9
in9 Bool
ClearP
ClearPortEr
ortErrror Bool
Bit09 Bool
Bit10 Bool
More
RightMotorAsDIO Bit11 Bool
Info
Bit12 Bool
Bit13 Bool
Bit14 Bool
EnableMotDIO Bool
Ener
EnergizeJSTP
gizeJSTPin3
in3 Bool
Ener
EnergizeJSTP
gizeJSTPin4
in4 Bool
Ener
EnergizeJSTP
gizeJSTPin5
in5 Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
Ener
EnergizeJSTP
gizeJSTPin9
in9 Bool
EnableJSTP
EnableJSTPin9
in9 Bool
Bit08 Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
Bit12 Bool
Bit13 Bool
Bit14 Bool
Ener
EnergizeL
gizeLef
eftP
tPort
ort Bool
Bit02 Bool
Ener
EnergizeRightP
gizeRightPort
ort Bool
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
Dir
Direction
ection Bool
More
Lef
eftMotorContr
tMotorControl
ol Bit09 Bool
Info
Bit10 Bool
Bit11 Bool
Bit12 Bool
Bit13 Bool
Bit14 Bool
Bit15 Bool
Run Bool
Bit01 Bool
Bit02 Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
Dir
Direction
ection Bool
Bit09 Bool
Bit10 Bool
Bit11 Bool
Bit12 Bool
Bit13 Bool
Bit14 Bool
More
RightMotorContr
RightMotorControl
ol Bit15 Bool
Info
Run Bool
Bit01 Bool
Bit02 Bool
Bit03 Bool
Bit04 Bool
Bit05 Bool
Bit06 Bool
Bit07 Bool
More
SetSpeedL
SetSpeedLef
eftMotor
tMotor Int
Info
More
SetSpeedRightMotor Int
Info
More
ClearMotorEr
ClearMotorErrror Word
Info