APARIAN ControlNet Router A-CNR User manual

ControlNet Router
(Enhanced)
Firmware Revision v1.001.010+
User Manual
A-CNR
Document No. D138-016
02/2022
Revision 1.1

Preface
Document No. D138-016 Page 2 of 178
Revision 1.1
CONTENTS
1. Preface ...............................................................................................................................6
1.1. Introduction to the ControlNet Router (Enhanced)....................................................6
1.2. Features.......................................................................................................................9
1.3. Architecture...............................................................................................................10
1.3.1. Ethernet-Only PanelView interface ...................................................................10
1.3.2. EtherNet/IP Target to ControlNet IO (Scheduled ControlNet)..........................12
1.3.3. Modbus TCP Slave to ControlNet IO (Scheduled ControlNet)...........................12
1.3.4. ControlNet Target (Scheduled) to EtherNet/IP IO (Class 1) ..............................13
1.3.5. ControlNet Target (Scheduled) to Modbus TCP Slaves .....................................14
1.4. Additional Information..............................................................................................15
1.5. Support......................................................................................................................16
2. Installation .......................................................................................................................17
2.1. Module Layout ..........................................................................................................17
2.2. Module Mounting .....................................................................................................18
2.3. Power ........................................................................................................................20
2.4. ControlNet.................................................................................................................20
2.5. Ethernet Port.............................................................................................................20
3. Setup ................................................................................................................................21
3.1. Install Configuration Software ..................................................................................21
3.2. Network Parameters.................................................................................................21
3.3. Creating a New Project..............................................................................................25
3.4. General parameters ..................................................................................................27
3.5. ControlNet Configuration..........................................................................................29
3.5.1. Target.................................................................................................................31
3.5.2. Originator...........................................................................................................42
3.6. Ethernet Mode ..........................................................................................................60
3.6.1. PCCC Client.........................................................................................................60
3.6.2. EtherNet/IP Target.............................................................................................68
3.6.3. Modbus TCP Slave..............................................................................................75
3.6.4. Modbus TCP Master...........................................................................................78
3.6.5. EtherNet/IP Originator.......................................................................................82

Preface
Document No. D138-016 Page 3 of 178
Revision 1.1
3.7. Internal Data Space Map...........................................................................................93
3.7.1. Copy From..........................................................................................................94
3.7.2. Copy To ..............................................................................................................98
3.8. Advanced.................................................................................................................102
3.9. Module Download...................................................................................................103
4. Logix Controller Programming Over ControlNet ...........................................................106
4.1. RSLinx Setup ............................................................................................................106
4.1.1. Uploading EDS File from Module.....................................................................107
4.1.2. Manually Installing the EDS File Option...........................................................109
4.2. RSLogix 5000 ...........................................................................................................112
5. Device Firmware Update ...............................................................................................114
6. Operation.......................................................................................................................117
6.1. ControlNet Target ...................................................................................................117
6.1.1. Scheduled.........................................................................................................117
6.2. ControlNet Originator .............................................................................................118
6.2.1. Scheduled ControlNet Connections.................................................................118
6.2.2. Explicit Messaging............................................................................................120
6.3. EtherNet/IP Target ..................................................................................................122
6.3.1. Class 1 Connection...........................................................................................122
6.4. EtherNet/IP Originator............................................................................................123
6.4.1. EtherNet/IP Class 1 Connections .....................................................................123
6.4.2. Explicit Messaging............................................................................................125
6.5. Modbus TCP Master................................................................................................127
6.6. Modbus TCP Slave...................................................................................................128
6.7. FTView / PanelView Interfacing ..............................................................................129
6.7.1. PanelView Reading Data From Logix ...............................................................130
6.7.2. PanelView Writing Data To Logix.....................................................................131
6.7.3. PanelView Reading Diagnostic Data from ControlNet Router ........................132
6.8. Internal Data Space (IDS) ........................................................................................133
6.8.1. Internal Status..................................................................................................133
6.8.2. Internal Control................................................................................................135
7. Diagnostics.....................................................................................................................136
7.1. LEDs .........................................................................................................................136

Preface
Document No. D138-016 Page 4 of 178
Revision 1.1
7.2. Module Status Monitoring in Slate .........................................................................137
7.2.1. General.............................................................................................................138
7.2.2. ControlNet Statistics ........................................................................................141
7.2.3. ControlNet Explicit...........................................................................................142
7.2.4. ControlNet Map ...............................................................................................143
7.2.5. PCCC Statistics..................................................................................................144
7.2.6. EtherNet/IP Explicit..........................................................................................145
7.2.7. EtherNet/IP Map..............................................................................................146
7.2.8. EtherNet/IP Originator.....................................................................................147
7.2.9. Logix .................................................................................................................148
7.2.10. Modbus ........................................................................................................149
7.2.11. CIP Statistics .................................................................................................151
7.2.12. Ethernet Clients............................................................................................152
7.2.13. TCP/ARP........................................................................................................152
7.3. Target Device Status Monitoring In Slate ...............................................................153
7.3.1. EtherNet/IP ......................................................................................................153
7.3.2. ControlNet........................................................................................................156
7.4. Module Event Log....................................................................................................159
7.5. Web Server..............................................................................................................160
7.6. ControlNet Packet Capture .....................................................................................161
7.6.1. Operational Capture ........................................................................................162
7.6.2. Promiscuous Capture.......................................................................................164
7.7. Modbus Packet Capture..........................................................................................167
7.8. Module Status Report .............................................................................................169
8. Technical Specifications.................................................................................................171
8.1. Dimensions..............................................................................................................171
8.2. Electrical ..................................................................................................................172
8.3. Ethernet...................................................................................................................172
8.4. ControlNet...............................................................................................................173
8.5. ControlNet Target ...................................................................................................173
8.6. ControlNet Originator .............................................................................................173
8.7. PCCC ........................................................................................................................173
8.8. EtherNet/IP Target ..................................................................................................174

Preface
Document No. D138-016 Page 5 of 178
Revision 1.1
8.9. EtherNet/IP Originator............................................................................................174
8.10. Modbus TCP Master ............................................................................................174
8.11. Modbus TCP Slave ...............................................................................................175
8.12. Certifications........................................................................................................175
9. Appendix ........................................................................................................................177
10. Index............................................................................................................................178
Revision History
Revision
Date
Comment
1.0
31 January 2022
Initial document
1.1
16 February 2022
Fixed ControlNet Router catalog number A-CNR.

Preface
Document No. D138-016 Page 6 of 178
Revision 1.1
1. PREFACE
1.1. INTRODUCTION TO THE CONTROLNET ROUTER
(ENHANCED)
This manual describes the installation, operation, and diagnostics of the Aparian ControlNet
Router (Enhanced). The ControlNet Router (Enhanced) is defined as the ControlNet Router
with firmware revision 1.001.010 (or later) being used with Slate v1.057 (or later).
The ControlNet Router, (hereafter referred to as the module) provides intelligent data routing
between either EtherNet/IP or Modbus TCP/RTU and a ControlNet network. This allows the
user to integrate ControlNet devices into a EtherNet/IP based Rockwell Logix platform (e.g.,
ControlLogix or CompactLogix) or any Modbus Master or Slave device with minimal effort.
The ControlNet Router also provides intelligent data routing between ControlNet and
Ethernet PCCC (CSP). This will allow the user to connect new PanelView Plus devices (with no
ControlNet interface) to existing ControlNet networks.
The ControlNet Mode can be configured to be either of the following two interface modes:
Target
A Logix controller can own the ControlNet Router over ControlNet using a scheduled
ControlNet connection when the ControlNet Router is operating as a ControlNet
target. This will allow the ControlNet Router to exchange data with the Logix controller
using the input and output assembly of the scheduled ControlNet connection. Data
from EtherNet/IP or Modbus TCP devices can be mapped to the Logix controller over
ControlNet.
Originator
As a ControlNet originator, the module can use one of two methods to read and write
data to and from ControlNet IO:
•Scheduled ControlNet
The ControlNet Router can be configured to own ControlNet IO by using the Slate
software to configure the IO connections and schedule the ControlNet network.
Each ControlNet Router can own up to 10 ControlNet devices with a total
maximum of 570 bytes of IO data. Multiple ControlNet Routers can exist on the
same ControlNet network with the Slate software having the ability to schedule all
of the ControlNet Routers on the network with originator IO connections and
downloading the ControlNet Keeper configuration into one of the ControlNet
Routers. Data from the ControlNet IO (via the IO input and output assemblies) can

Preface
Document No. D138-016 Page 7 of 178
Revision 1.1
be exchanged with any of the Ethernet mode interfaces (e.g. EtherNet/IP Target
or Modbus TCP Slave).
•ControlNet Explicit Messaging
This allows the ControlNet Router to exchange data with up to 10 ControlNet
devices using explicit messaging over ControlNet. The module can Get or Set
data in the remote ControlNet devices with Custom Class, Instance, Attribute
values.
The Ethernet Mode can be configure to be any of the following five interface modes:
PCCC Client
The support for Ethernet PCCC (CSP) allows the module to emulate a PLC5 or SLC
providing a legacy interface for PanelViews and other devices over scheduled
ControlNet. This will allow an Ethernet-only PanelView to exchange data with a Logix
controller using an existing ControlNet connection.
EtherNet/IP Target
A Logix controller can own the ControlNet Router over EtherNet/IP using a class 1
connection when the ControlNet Router is operating as a EtherNet/IP Target. This will
allow the ControlNet Router to exchange data with the Logix controller using the input
and output assembly of the EtherNet/IP Class 1 connection. Data from ControlNet
devices (when operating as a ControlNet Originator) or Controllers on ControlNet
(when operating as a ControlNet Target) can be mapped to the Logix controller over
EtherNet/IP.
EtherNet/IP Originator
As an EtherNet/IP originator, the module can use one of three methods to read and
write data to and from the EtherNet/IP network:
•EtherNet/IP Class 1 Connection
The ControlNet Router can be configured to own EtherNet/IP IO by using the
Slate software to configure the Class 1 connections. Each ControlNet Router
can own up to 10 EtherNet/IP devices. Data from the EtherNet/IP IO (via the
input and output assemblies) can be exchanged with the ControlNet network
(when operating as either a ControlNet Target or Originator).
•EtherNet/IP Explicit Messaging
This allows the ControlNet Router to exchange data with up to 10 EtherNet/IP
devices using explicit messaging over EtherNet/IP. The module can use either
Class 3, Unconnected Messaging (UCMM), or Logix Tag to Get and Set data in
the remote EtherNet/IP devices with configurable Class, Instance, Attribute

Preface
Document No. D138-016 Page 8 of 178
Revision 1.1
values (when using UCMM or Class 3). Logix Tag messages are used to
exchange data with a Logix controller by directly writing to or reading from
Logix tags. The user can browse to the Logix controller (using the Slate Target
Browser) as well as browse the Logix Controller Tag list (using the Slate Tag
Browser) to select the desired destination Tag.
Modbus TCP Master
The data from either ControlNet IO (when operating as a ControlNet originator) or
ControlNet input and output assemblies (when operating as a ControlNet Target) will
be written to, or read from, the module’s internal Modbus Registers. The Modbus
Auxiliary Map can then be used to configure the Modbus data exchange between
multiple remote Modbus Slave devices and the module’s internal Modbus registers.
The Modbus communication utilizes Modbus TCP.
Modbus TCP Slave
The data from either ControlNet IO (when operating as a ControlNet originator) or
ControlNet input and output assemblies (when operating as a ControlNet Target) will
be written to, or read from, the module’s internal Modbus Registers using the internal
mapping functions. These Modbus registers can be accessed by a remote Modbus
Master using Modbus TCP.
The ControlNet Router uses an internal mapping strategy allowing the user to map any data
from any supported interface to any other supported interface. Slate provides an online
import tool for existing Logix controllers with IO connections to assist with the setup and
configure of originator connections (EtherNet/IP or ControlNet).
The ControlNet Router can also be used to go online and program a Logix controller over
ControlNet using an Ethernet connection from the local PC.
The module provides a range of statistics on Ethernet and ControlNet to assist with fault
finding. A built-in webserver provides detailed diagnostics of system configuration and
operation, including the display of ControlNet operation and communication statistics,
without the need for any additional software.
The ControlNet Router is configured using the Aparian Slate application. This program can be
downloaded from www.aparian.com free of charge.

Preface
Document No. D138-016 Page 9 of 178
Revision 1.1
1.2. FEATURES
-The module has the following ControlNet operating modes:
oControlNet Target, where the ControlNet Router can be owned by a controller
over scheduled ControlNet.
oControlNet Originator, where the ControlNet Router owns ControlNet IO over
a scheduled ControlNet connection.
-The module has the following Ethernet operating modes:
oPCCC Client, allowing the ControlNet Router to emulate a PLC5 or SLC to
exchange data with Ethernet-only PanelViews.
oEtherNet/IP Target, where the ControlNet Router can be owned by a
controller via a Class 1 EtherNet/IP connection.
oEtherNet/IP Originator, where the ControlNet Router owns EtherNet/IP IO
using a Class 1 EtherNet/IP connection.
oModbus TCP Master, where the ControlNet Router module can exchange data
with Modbus TCP Slaves.
oModbus TCP Slave, where the ControlNet Router module can exchange data
with a Modbus TCP Master.
-The ControlNet network can be scheduled using the Slate software environment.
-ControlNet Router can operate as ControlNet Keeper.
-Multiple ControlNet Routers can own ControlNet IO on the ControlNet network.
-Supports Redundant ControlNet.
-Supports Promiscuous Capture mode allowing the ControlNet Router to capture all
traffic on the ControlNet network.
-Supports unscheduled ControlNet allowing Logix programming over ControlNet.
-Dual Ethernet ports which supports Device-Level-Ring (DLR).
-Network Time Protocol (NTP) supported for external time synchronization.
-ControlNet, EtherNet/IP, and Modbus Statistics and packet captures providing
diagnostic data for fault finding.
-Built-in webserver providing (read-only) diagnostics.
-Small form factor –DIN rail mounted.

Preface
Document No. D138-016 Page 10 of 178
Revision 1.1
1.3. ARCHITECTURE
Various architectures can be supported by the ControlNet Router for interfacing various
Ethernet protocols to ControlNet.
1.3.1. ETHERNET-ONLY PANELVIEW INTERFACE
When set to PCCC Client Mode, the ControlNet Router provides an interface between modern
Rockwell Automation PanelView Plus HMIs (without any ControlNet interface) and existing
ControlNet networks using either Unscheduled or Scheduled ControlNet.
When using unscheduled ControlNet, the ControlNet Router can be used as a drop-in
replacement for existing legacy PanelView HMI’s by simply changing the RSLinx path.
When using scheduled ControlNet, the ControlNet Router can be configured to allow for up
to 400 bytes of input data and 400 bytes of output data to be exchanged with the Logix
Controller. The ControlNet Router will emulate a PLC5 controller which is used by the
PanelView HMI to map PLC5 Files (e.g. N7 or F8) to the Logix input and output assembly over
scheduled ControlNet. The consumed (ControlNet) data can be mapped to a PLC5 type
address file, N9 and F10, and then read by an Ethernet device e.g. a PanelView. Similarly, the
produced (ControlNet) data can also be mapped to a PLC5 type address file, N7 and F8, to
which an Ethernet device could write.
Figure 1.1 –Typical Setup for PanelViews

Preface
Document No. D138-016 Page 11 of 178
Revision 1.1
Figure 1.2. - Example of a typical network setup in PLC Emulation mode
Figure 1.3. - Example of a PLC5/SLC500 Messaging in PLC Emulation mode

Preface
Document No. D138-016 Page 12 of 178
Revision 1.1
1.3.2. ETHERNET/IP TARGET TO CONTROLNET IO (SCHEDULED CONTROLNET)
When ControlNet Router is configured as a EtherNet/IP Target and ControlNet Originator, a
controller (e.g. Logix Controller) can own the ControlNet Router via EtherNet/IP Class 1 while
the ControlNet Router, in turn, owns ControlNet IO using Scheduled ControlNet.
The data from the controller (e.g., Logix Controller) can be exchanged with the ControlNet
Router using the EtherNet/IP Class 1 input and output assembly. This data, in turn, can be
mapped to any of the configured Scheduled ControlNet IO input and output assemblies being
owned by the ControlNet Router.
The ControlNet Router can also exchange data with ControlNet devices using the Explicit
Messaging Map. A CIP message with specific service, class, instance, and attribute can be
configured to execute at a configured rate with the data being stored in the internal data
space (IDS).
Figure 1.4 –Typical Setup for EtherNet/IP Target to ControlNet IO
1.3.3. MODBUS TCP SLAVE TO CONTROLNET IO (SCHEDULED CONTROLNET)
When ControlNet Router is configured as a Modbus TCP Slave and ControlNet Originator,
Modbus TCP Master and read and write data to the ControlNet Router internal Modbus
Registers while the ControlNet Router owns ControlNet IO using Scheduled ControlNet.

Preface
Document No. D138-016 Page 13 of 178
Revision 1.1
The data from the Modbus TCP Master can be mapped to any of the configured Scheduled
ControlNet IO input and output assemblies being owned by the ControlNet Router.
Figure 1.5 –Typical Setup for Modbus TCP Slave to ControlNet IO
1.3.4. CONTROLNET TARGET (SCHEDULED)TO ETHERNET/IP IO (CLASS 1)
When ControlNet Router is configured as a ControlNet Target and EtherNet/IP Originator, a
controller (e.g. Logix Controller) can own the ControlNet Router via Scheduled ControlNet
(e.g. via 1756-CNB/R) while the ControlNet Router owns EtherNet/IP IO using a class 1
connection.
The data from the controller (e.g., Logix Controller) can be exchanged with the ControlNet
Router using the Scheduled ControlNet input and output assembly. This data, in turn, can be
mapped to any of the configured Class 1 EtherNet/IP IO input and output assemblies being
owned by the ControlNet Router.
The ControlNet Router can also exchange data with EtherNet/IP devices using the Explicit
Messaging Map. A CIP message with specific service, class, instance, and attribute can be

Preface
Document No. D138-016 Page 14 of 178
Revision 1.1
configured to execute at a configured rate with the data being stored in the internal data
space (IDS).
Figure 1.6 –Typical Setup for ControlNet Target to EtherNet/IP IO
1.3.5. CONTROLNET TARGET (SCHEDULED)TO MODBUS TCP SLAVES
When ControlNet Router is configured as a ControlNet Target and Modbus TCP Master, a
controller (e.g. Logix Controller) can own the ControlNet Router via Scheduled ControlNet
(e.g. via 1756-CNB/R) while the ControlNet Router exchanges data with multiple Modbus TCP
Slaves.
The data from the controller (e.g., Logix Controller) can be exchanged with the ControlNet
Router using the Scheduled ControlNet input and output assembly. This data, in turn, can be
mapped to any of the Modbus TCP Slaves being written to or read from by the ControlNet
Router.

Preface
Document No. D138-016 Page 15 of 178
Revision 1.1
Figure 1.7 –Typical Setup for ControlNet Target to Modbus TCP Slaves
1.4. ADDITIONAL INFORMATION
The following documents contain additional information that can assist the user with the
module installation and operation.
Resource
Link
Slate Installation
http://www.aparian.com/software/slate
ControlNet Router User Manual
ControlNet Router Datasheet
Example Code & UDTs
http://www.aparian.com/products/controlnetrouter
Ethernet wiring standard
www.cisco.com/c/en/us/td/docs/video/cds/cde/cde205_220_420/installation/gui
de/cde205_220_420_hig/Connectors.html
CIP Routing
The CIP Networks Library, Volume 1, Appendix C:Data Management
ControlNet
http://www.odva.org
ControlNet Cabling
ControlNet Coax Media Planning and Installation Guide
https://literature.rockwellautomation.com/idc/groups/literature/documents/in/c
net-in002_-en-p.pdf
Table 1.1. - Additional Information

Preface
Document No. D138-016 Page 16 of 178
Revision 1.1
1.5. SUPPORT
Technical support is provided via the Web (in the form of user manuals, FAQ, datasheets etc.)
to assist with installation, operation, and diagnostics.
For additional support the user can use either of the following:
Resource
Link
Contact Us web link
www.aparian.com/contact-us
Support email
[e-mail]
Table 1.2. –Support Details

Installation
Document No. D138-016 Page 17 of 178
Revision 1.1
2. INSTALLATION
2.1. MODULE LAYOUT
The module has one 3-way power connector at the bottom of the enclosure as shown in the
figure below.
Figure 2.1. –ControlNet Router side and front view
There are two ControlNet BNC connectors in the front of the module for redundant
ControlNet. There are two Ethernet RJ45 connectors on the front angle of the module which
is used for the Ethernet connection. The Ethernet cable must be wired according to industry
standards which can be found in the additional information section of this document.
The module provides six diagnostic LEDs on the front of the module. These LEDs are used to
provide information regarding the module system operation, the Ethernet interface, and the
ControlNet interface.

Installation
Document No. D138-016 Page 18 of 178
Revision 1.1
Figure 2.2 –ControlNet Router top view
The module provides four DIP switches at the top of the enclosure as shown in the top view
figure above.
DIP Switch
Description
DIP Switch 1
Used to force the module into “Safe Mode”. When in “Safe Mode” the module will not
load the application firmware and will wait for new firmware to be downloaded. This
should only be used in the rare occasion when a firmware update was interrupted at
a critical stage.
DIP Switch 2
This will force the module into DHCP mode which is useful when the user has forgotten
the IP address of the module.
DIP Switch 3
This DIP Switch is used to lock the configuration from being overwritten by the Slate.
When set Slate will not be able to download to the module.
DIP Switch 4
When this DIP Switch is set at bootup it will force the module Ethernet IP address to
192.168.1.100 and network mask 255.255.255.0. The user can then switch the DIP
switch off and assign the module a static IP address if needed.
Table 2.1. - DIP Switch Settings
2.2. MODULE MOUNTING
The module provides a DIN rail clip to mount onto a 35mm DIN rail.

Installation
Document No. D138-016 Page 19 of 178
Revision 1.1
Figure 2.3 - DIN rail specification
The DIN rail clip is mounted on the bottom of the module at the back as shown in the figure
below. Use a flat screwdriver to pull the clip downward. This will enable the user to mount
the module onto the DIN rail. Once the module is mounted onto the DIN rail the clip must be
pushed upwards to lock the module onto the DIN rail.
Figure 2.4 - DIN rail mouting

Installation
Document No. D138-016 Page 20 of 178
Revision 1.1
2.3. POWER
A 3-way power connector is used to connect Power+, Power–(GND), and earth. The module
requires an input voltage of 10 –36Vdc. Refer to the technical specifications section in this
document.
Figure 2.5 - Power connector
2.4. CONTROLNET
ControlNet uses a coax media system. The ControlNet connectors should be wired according
to industry standards. Refer to the additional information section in this document for further
details.
2.5. ETHERNET PORT
The Ethernet connector should be wired according to industry standards. Refer to the
additional information section in this document for further details.