1. Manuals
  2. Brands
  3. APARIAN Manuals
  4. Network Hardware
  5. ControlNet Router A-CNR
  6. User manual

APARIAN ControlNet Router A-CNR User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

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

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the ControlNet Router A-CNR and is the answer not in the manual?

Questions and answers

Related Manuals for APARIAN ControlNet Router A-CNR

Summary of Contents for APARIAN ControlNet Router A-CNR

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

  • Page 2: Table Of Contents

    Preface CONTENTS 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.
  • Page 3 Preface 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 Logix Controller Programming Over ControlNet ............106 4.1. RSLinx Setup ......................106 4.1.1. Uploading EDS File from Module ..............
  • Page 4 Preface 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.
  • Page 5 Preface 8.9. EtherNet/IP Originator .................... 174 8.10. Modbus TCP Master .................... 174 8.11. Modbus TCP Slave ....................175 8.12. Certifications ......................175 Appendix ........................177 Index ..........................178 Revision History Revision Date Comment 31 January 2022 Initial document 16 February 2022 Fixed ControlNet Router catalog number A-CNR.

  • Page 6: 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).
  • Page 7 Preface 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.
  • Page 8 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.

  • Page 9: Features

    Preface 1.2. FEATURES The module has the following ControlNet operating modes: o ControlNet Target, where the ControlNet Router can be owned by a controller over scheduled ControlNet. o ControlNet Originator, where the ControlNet Router owns ControlNet IO over a scheduled ControlNet connection. The module has the following Ethernet operating modes: o PCCC Client, allowing the ControlNet Router to emulate a PLC5 or SLC to exchange data with Ethernet-only PanelViews.

  • Page 10: Architecture

    Preface 1.3. ARCHITECTURE Various architectures can be supported by the ControlNet Router for interfacing various Ethernet protocols to ControlNet. 1.3.1. E THERNET ANEL IEW 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.
  • Page 11 Preface 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 Document No. D138-016 Page 11 of 178 Revision 1.1...

  • Page 12: Ethernet/Ip Target To Controlnet Io (Scheduled Controlnet)

    Preface 1.3.2. E /IP T IO (S THER ARGET TO ONTROL CHEDULED ONTROL 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.

  • Page 13: Controlnet Target (Scheduled) To Ethernet/Ip Io (Class 1)

    Preface 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.

  • Page 14: Controlnet Target (Scheduled) To Modbus Tcp Slaves

    Preface 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. C TCP S ONTROL ARGET CHEDULED ODBUS LAVES When ControlNet Router is configured as a ControlNet Target and Modbus TCP Master, a controller (e.g.

  • Page 15: Additional Information

    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 http://www.aparian.com/products/controlnetrouter Example Code & UDTs www.cisco.com/c/en/us/td/docs/video/cds/cde/cde205_220_420/installation/gui Ethernet wiring standard de/cde205_220_420_hig/Connectors.html...

  • Page 16: Support

    For additional support the user can use either of the following: Resource Link Contact Us web link www.aparian.com/contact-us Support email support@aparian.com Table 1.2. – Support Details Document No. D138-016 Page 16 of 178...

  • Page 17: Installation

    Installation 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.

  • Page 18: Module Mounting

    Installation 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.
  • Page 19 Installation 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.

  • Page 20: Power

    Installation 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.

  • Page 21: Setup

    Setup 3. SETUP 3.1. INSTALL CONFIGURATION SOFTWARE All the network setup and configuration of the module is achieved by means of the Aparian Slate device configuration environment. This software can be downloaded from http://www.aparian.com/software/slate. Figure 3.1. - Aparian Slate Environment 3.2.
  • Page 22 Setup Figure 3.3. - DHCP Server NOTE: If the DHCP requests are not displayed in the DHCP Server it may be due to the local PC’s firewall. During installation the necessary firewall rules are automatically created for the Windows firewall. Another possibility is that another DHCP Server is operational on the network and it has assigned the IP address.
  • Page 23 Setup background of the associated row. Figure 3.5. - Successful IP address assignment It is possible to force the module back into DHCP mode by powering up the device with DIP switch 2 set to the On position. A new IP address can then be assigned by repeating the previous steps.
  • Page 24 Setup The Target Browser automatically scans the Ethernet network for EtherNet/IP devices. Figure 3.8. - Target Browser Right-clicking on a device, reveals the context menu, including the Port Configuration option. Figure 3.9. - Selecting Port Configuration All the relevant Ethernet port configuration parameters can be modified using the Port Configuration window.

  • Page 25: Creating A New Project

    Setup Figure 3.10. - Port Configuration Alternatively, these parameters can be modified using Rockwell Automation’s RSLinx software. 3.3. CREATING A NEW PROJECT Before the user can configure the module, a new Slate project must be created. Under the File menu, select New. Figure 3.11.
  • Page 26 Setup Figure 3.12. - Adding a new device In the Add New Device window select the ControlNet Router, and click the Ok button. Figure 3.13 – Selecting a new ControlNet Router The software will provide the user with the option to select either the Legacy or Enhanced ControlNet Router.

  • Page 27: General Parameters

    Setup Figure 3.14 – Selecting a Legacy or Enhanced ControlNet Router The device will appear in the Project Explorer tree as shown below, and its configuration window opened. The device configuration window can be reopened by either double clicking the module in the Project Explorer tree or right clicking the module and selecting Configuration.
  • Page 28 Setup module and selecting Configuration. Figure 3.16 - General Configuration The general configuration consists of the following parameters: Parameter Description This parameter is a user defined name to identify between various ControlNet Instance Name Routers. This parameter is used to provide a more detailed description of the application for Description the module.

  • Page 29: Controlnet Configuration

    Setup the IO connections and schedule the ControlNet network. ControlNet Explicit Messaging This ControlNet Router can exchange data with up to 10 ControlNet devices using explicit messaging over ControlNet. PCCC Client This will allow the module to emulate a PLC5 or SLC, providing a legacy interface for PanelViews and other devices over scheduled ControlNet EtherNet/IP Target A Logix controller can own the ControlNet Router over EtherNet/IP using a class 1...
  • Page 30 Setup Figure 3.17 - General Configuration The ControlNet configuration consists of the following parameters: Parameter Description The ControlNet Router module has two ControlNet ports and supports redundant ControlNet Channels ControlNet operation. The ControlNet Channels can be selected in this parameter to communicate on Channel A Only, Channel B Only, or A+B Redundant.

  • Page 31: Target

    Setup When using Scheduled ControlNet this is the size of the output data (being sent from Output Assembly Size the ControlNet Router) that can be mapped for the PLC5 emulation. See the Scheduled ControlNet section. Table 3.2 - General configuration parameters The module can operate as either a ControlNet Target or a ControlNet Originator.
  • Page 32 Setup The user must enter the ControlNet node number of the ControlNet Router that will be used. The assembly instance and size must also be added for the input, output, and configuration in the connection parameters section. Below are the required connection parameters. NOTE: The input and output assembly connection sizes will be dynamic and based on the sizes of the Mapped Data for the input and output (as shown below).
  • Page 33 Setup Figure 3.20 - Logix General module properties in Logix 5000 NOTE: The user will need to enter the exact connection parameters before the module will establish a class 1 connection with the Logix controller. Next the user needs to configure the connection requested packet interval (RPI). This is the rate at which the input and output assemblies are exchanged.
  • Page 34 Setup Defined Types (UDTs) to the input and output assemblies. The user can import the required UDTs by right-clicking on User-Defined sub-folder in the Data Types folder of the IO tree and selecting Import Data Type. The assemblies are then assigned to the UDTs with a ladder copy instruction (COP) as shown in the figure below.
  • Page 35 Setup Figure 3.24 - Selecting partial import file The import will create the following: • The required UDTs (user defined data types) • Two controller tags representing the Input and Output assemblies. • A routine mapping the ControlNet Router module to the aforementioned tags. The user may need to change the routine to map to the correct ControlNet Router module instance name, and make sure that the mapping routine is called by the Program’s Main Routine.
  • Page 36 Setup Figure 3.25 - Imported Logix 5000 objects Refer to the additional information section of this document for an example Logix 5000 project as well as the required UDTs. 3.5.1.2. RSNETWORX CONFIGURATION The ControlNet scheduling is typically done using RSNetworx for ControlNet and is required when the module is operating in ControlNet Target Mode.
  • Page 37 Setup Figure 3.26 – RSNetWorx browse for ControlNet network Click the online button and the software will scan the network for all the devices. Additional devices can be added (offline) if required. Figure 3.27 – RSNetWorx for ControlNet Online NOTE: The EDS file of the ControlNet Router will need to be installed to schedule the ControlNet network.
  • Page 38 Setup Figure 3.28 – RSLinx EDS upload Once the scan is completed the online devices will be displayed. Figure 3.29 – RSNetWorx found devices on the ControlNet network The user can then make changes (e.g. Redundant ControlNet selected, Max scan address, etc.) to the ControlNet network by pressing the edit button.
  • Page 39 Setup Figure 3.30 – RSNetWorx network edits. Once done the user must download the ControlNet network configuration to the network by right-clicking on the background and selecting Download to Network. Document No. D138-016 Page 39 of 178 Revision 1.1...
  • Page 40 Setup Figure 3.31 – RSNetWorx download Once this is done the ControlNet Router will connect to the Logix controller over the scheduled ControlNet network (see below): Figure 3.32 – ControlNet Router connected over Scheduled ControlNet Document No. D138-016 Page 40 of 178 Revision 1.1...
  • Page 41 Setup 3.5.1.3. INTERNAL DATA SPACE MAPPING When the module is operating as a ControlNet Target, the data from the originator device (e.g. Logix Controller) can be mapped to the Ethernet interface using the Internal Map. The Internal Map configuration window is opened by either double clicking on the module in the tree or right-clicking the module and selecting Configuration and selecting the Internal Map tab.

  • Page 42: Originator

    Setup Figure 3.35 – IDS Copy – ControlNet Target Destination Type The destination instance will be the connection number, which in this case is always Connection 0. The Destination Offset is the offset in the Mapped Data section of the ControlNet input assembly from where the data must be copied.
  • Page 43 Setup A. MANUAL CONFIGURATION A class 1 connection can be added to the ControlNet Connections tree by right-clicking on the tree in Slate and selecting Add ControlNet Connection. Figure 3.37 – Adding ControlNet Scheduled IO Device Connection Next the user will need to enter the connection parameters for the Scheduled connection. Figure 3.38 –...
  • Page 44 Setup Parameter Description Connection Name The instance name given to the Scheduled ControlNet Connection. This is the offset in the Internal Data Space (IDS) which provides the communication status of each ControlNet device. The Communication Status is as shown below: Comm Status Offset (1: Device online / 0:Device offline) Bit 0 -...
  • Page 45 Setup Keying is not enabled and no key information will be sent in the connection establishment. Compatible Keying has been enabled with compatibility enabled. This will allow devices with older firmware to also establish a connection. Exact Keying has been enabled and the exact device with specific firmware revision will allow the establishment of the connection.
  • Page 46 Setup NOTE: When instantiating modules in Studio5000 do not make use of the “Rack Optimization” communication format. NOTE: Some versions Logix (V32+) do not support the reading of the module’s configuration. Where possible use an earlier version (e.g. V24). IMPORT CONNECTION PARAMETERS The connection parameters can be imported from the Logix controller by selecting the Import Connection Parameters from Online Controller option under the Import menu of the Class 1 Connection form.
  • Page 47 Setup Figure 3.41 – Import Connection Parameters – Select Connection In order to import all the necessary connection information, the user will need to select both the appropriate Configuration Tag, and the matching Connection. The new connection’s configuration data is derived from the selected Configuration Tag, when the new connection’s parameters are derived from the selected Connection.
  • Page 48 Setup The user can then modify the Connection Name, Path and RPI as required. 3.5.2.2. CONTROLNET EXPLICIT MESSAGE DEVICE CONNECTIONS Up to 10 ControlNet devices can be added for explicit unscheduled messaging. The user will need to add each device as explained in the ControlNet Devices section below. Once the ControlNet devices have been added the user can then configure the required mapping for the ControlNet Explicit messaging as shown in ControlNet Map section below.
  • Page 49 Setup The ControlNet Devices configuration consists of the following parameters: Parameter Description The configurable update rates (in milliseconds) for each Scan Class in the ControlNet Scan Class A, B, C, D Map. Device List (per device) Device Name The user assigned instance name for the specific device. The CIP Path to the target device.
  • Page 50 Setup Figure 3.44 – ControlNet Map configuration The ControlNet Map configuration consists of the following parameters: Parameter Description The device instance name configured in the previous ControlNet Devices tab. Device The selected device will be used for executing the communication function. The user can select one of four functions.
  • Page 51 Setup supports in that device’s user manual. The user can select Scan Class A, B, C or D (which was configured in the ControlNet Devices tab). The specific mapped item will then be executed at that configured scan class rate. Scan The user can also select the S class which means that the mapped item will only execute once when communication to the target device is established.
  • Page 52 Setup Figure 3.45 – ControlNet Scheduler select From the ControlNet Scheduler the ControlNet network can be scanned for connection originator devices, the network schedule can be calculated, and the scheduled and Keeper data can be downloaded to a ControlNet Router. Figure 3.46 –...
  • Page 53 Setup The user can update the Network Parameters in the Scheduler. NOTE: Unless the user is experienced in ControlNet networks, it is recommended to leave the Network Update Time (NUT) at its default value of 5ms. Parameter Description The name assigned to the ControlNet network. This can be any name Network Name selected by the user.
  • Page 54 Setup originators (via the ControlNet network). The schedule will be stored in Non-Volatile memory for each of the ControlNet Routers having connection origination. Figure 3.47 – ControlNet Scheduler – Scan-Schedule-Download Figure 3.48 – ControlNet Scheduler – Scheduling Complete Once done the ControlNet Router will establish scheduled connections to the devices in the ControlNet IO tree of the module (in Slate) and ControlNet IO devices will go green in the local and other ControlNet Routers.
  • Page 55 Setup Figure 3.49 – ControlNet Scheduler – ControlNet IO devices online SCAN ONLY When pressing the button in the Slate Scheduler, the software will only scan the ControlNet network up to the Maximum Scheduled Node (as configured in the Network Parameters).
  • Page 56 Setup SCHEDULE ONLY When pressing the button in the Slate Scheduler, the ControlNet network will be scheduled once all the ControlNet devices (with configuration with connection origination) have been found. Figure 3.51 – ControlNet Scheduler – Schedule DOWNLOAD ONLY When pressing the button in the Slate Scheduler (and 2hen the scheduled has finished compiling), it will download the schedule to the local module as well as all the other ControlNet Router connection originators (via the ControlNet network).
  • Page 57 Setup Figure 3.52 – ControlNet Scheduler – Download Figure 3.53 – ControlNet Scheduler – Download Complete Figure 3.54 – ControlNet Scheduler – ControlNet IO devices online Document No. D138-016 Page 57 of 178 Revision 1.1...
  • Page 58 Setup B. MEDIA To allow for a more accurate ControlNet schedule, the user can enter the media type and cable distance being used in the ControlNet network. This will add the appropriate delays to the ControlNet schedule calculation. The Media configuration is opened by selecting the Media tab in the Slate Scheduler.
  • Page 59 Setup 3.5.2.4. INTERNAL DATA SPACE MAPPING When the module is operating as a ControlNet Originator, the data from the ControlNet IO devices can be mapped to the Ethernet interface using the Internal Map. The Internal Map configuration window is opened by either double clicking on the module in the tree or right- clicking the module and selecting Configuration and selecting the Internal Map tab.

  • Page 60: Ethernet Mode

    Setup Figure 3.59 – IDS Copy – ControlNet Originator Destination Type The destination instance will be one of the ControlNet IO devices added to the ControlNet IO tree in Slate. Figure 3.60 – IDS Copy – ControlNet Originator Destination Instance The Destination Offset is the offset in the selected ControlNet device Scheduled Output Assembly.
  • Page 61 Setup This IP address will be seen as the IP address of the PLC5 controller that the ControlNet Router is emulating. Therefore, there will be two IP addresses on the network when in PLC5 Emulation mode. One for the actual target module and one for the emulated PLC5 controller. NOTE: These two IP addresses must not be the same.
  • Page 62 Setup Figure 3.62 - Selecting Connection Path in RSLinx Enterprise 3.6.1.2. FTVIEW CONFIGURATION The ControlNet Router can be interfaced directly to FTView using PCCC (PLC5 Ethernet emulation) or Unscheduled ControlNet. This is illustrated in the following examples where a PanelView is configured to read data from the ControlNet Router. Using FTView Studio (Machine Edition) create a new project.
  • Page 63 Setup A. COMMUNICATION – SCHEDULED CONTROLNET To configure the communication link to the ControlNet Router (when using Scheduled ControlNet), select the Communication Setup under the RSLinx Enterprise section. If the RSLinx Enterprise heading does not appear, then it should be added by right-clicking on the project and selecting Add New Server.
  • Page 64 Setup Figure 3.66 – Adding Ethernet Device The Add Device dialog will open. Under the Ethernet PLC devices section, select the 1785- L40E PLC-5/40 Processor with an Ethernet interface option. NOTE: The ControlNet Router supports a PLC5 emulation mode, allowing it to be accessible by RSLinx Enterprise.
  • Page 65 Setup Figure 3.68 – Device Properties At the top of the Communication Setup dialog, select the Copy from Design to Runtime button. As the name implies, this copies the configuration to be used by the PanelView at runtime. Select the Ok button to close the Communication Setup dialog. B.
  • Page 66 Setup Figure 3.70 – Adding RSLinx Enterprise Server C. ANIMATION Once the communication has been correctly configured, objects can be linked to the ControlNet Router data points. Create a new graphic Display by right-clicking on the Display item, under the Graphics section. Figure 3.71 –...
  • Page 67 Setup The Numeric Display can now be linked to a ControlNet Router data point using the Connections tab. Select the Tag (…) button adjacent to the Value item. The FTView Tag Browser dialog will open. To view all the available data points, select the Refresh All Folders button.

  • Page 68: Ethernet/Ip Target

    Setup D. DIAGNOSTIC DATA Various diagnostic items can be displayed in the FTView using the Diagnostic File. The diagnostic file number is N11. The description of each diagnostic data point is tabulated below. Offset Group Description ControlNet Router Status Bit 0 – Config Valid Bit 1 –...
  • Page 69 Setup The user will need to add the ControlNet Router to the Logix IO tree under a EtherNet/IP bridge (e.g. 1756-EN2TR). 3.6.2.1. STUDIO / LOGIX 5000 CONFIGURATION A. ADD MODULE TO ETHERNET/IP I/O CONFIGURATION When operating in EtherNet/IP Target mode, the ControlNet Router can be added to the Logix 5000 I/O tree under an Ethernet bridge (e.g.
  • Page 70 Setup Figure 3.75 - Logix General module properties in Logix 5000 NOTE: The user will need to enter the exact connection parameters before the module will establish a class 1 connection with the Logix controller. Next the user needs to configure the connection requested packet interval (RPI). This is the rate at which the input and output assemblies are exchanged.
  • Page 71 Setup Once the module has been added to the Logix 5000 I/O tree the user must assign the User Defined Types (UDTs) to the input and output assemblies. The user can import the required UDTs by right-clicking on User-Defined sub-folder in the Data Types folder of the IO tree and selecting Import Data Type.
  • Page 72 Setup Figure 3.79 - Selecting partial import file The import will create the following: • The required UDTs (user defined data types) • Two controller tags representing the Input and Output assemblies. • A routine mapping the ControlNet Router module to the aforementioned tags. The user may need to change the routine to map to the correct ControlNet Router module instance name, and make sure that the mapping routine is called by the Program’s Main Routine.
  • Page 73 Setup Figure 3.80 - Imported Logix 5000 objects Refer to the additional information section of this document for an example Logix 5000 project as well as the required UDTs. 3.6.2.2. INTERNAL DATA SPACE MAPPING When the module is operating as a EtherNet/IP Target, the data from the originator device (e.g.
  • Page 74 Setup Figure 3.81 – IDS Copy – EtherNet/IP Target Source Type The source instance will be the connection number, which in this case is always Connection 0. The Source Offset is the offset in the Mapped Data section of the EtherNet/IP output assembly from where the data must be copied.

  • Page 75: Modbus Tcp Slave

    Setup Figure 3.84 – EtherNet/IP Input Mapped Data UDT 3.6.3. M TCP S ODBUS LAVE The ControlNet Router can operate as a Modbus Slave for Modbus TCP. A Modbus TCP Master can read and write to the full Modbus Register range in the ControlNet Router. The user will need to configure the relevant Modbus Parameters as shown below.
  • Page 76 Setup Update Rate The period (in milliseconds) between master requests to the target Modbus device. (Modbus TCP Master mode only) Retry Limit The number of successive Modbus request retries before the request is set to have failed. (Modbus TCP Master mode only) Response Timeout The time (in milliseconds) the module will wait for a valid Modbus response.
  • Page 77 Setup Figure 3.86 – IDS Copy - Modbus Source Type The source instance will be the Modbus register type required. Figure 3.87 – IDS Copy - Modbus Source Instance The Source Offset is the Modbus Register offset from where the data must be copied. The Count is the number of bytes that will be copied.

  • Page 78: Modbus Tcp Master

    Setup Figure 3.89 – IDS Copy - Modbus Destination Instance The Destination Offset is the Modbus Register offset to where the data must be copied. The Count is the number of bytes that will be copied. See the Internal Data Space Mapping section for more information regarding the operation.
  • Page 79 Setup Parameter Description Local Node The Modbus Node address assigned to the ControlNet Router. Modbus TCP Port The TCP port to be used for the Modbus communication. By default the module will use the standard TCP port 502. Update Rate The period (in milliseconds) between master requests to the target Modbus device.
  • Page 80 Setup Figure 3.91 – Modbus Auxiliary Map Configuration The Modbus Auxiliary Map configuration consists of the following parameters: Parameter Description Modbus Function This is the Modbus function that is sent to the Modbus Slave. Read – Read a Modbus Register (e.g. HR, IR, CS, or IS) from a Modbus Slave. Write –...
  • Page 81 Setup Table 3.12 – Modbus Auxiliary Map parameters 3.6.4.2. INTERNAL DATA SPACE MAPPING When the module is operating as a Modbus TCP Master, the data from the Modbus Registers (used to exchange data with various Modbus TCP Slaves) can be mapped to the ControlNet interface using the Internal Map.

  • Page 82: Ethernet/Ip Originator

    Setup Figure 3.94 – IDS Copy - Modbus Destination Type The destination instance will be the Modbus register type required. Figure 3.95 – IDS Copy - Modbus Destination Instance The Destination Offset is the Modbus Register offset to where the data must be copied. The Count is the number of bytes that will be copied.
  • Page 83 Setup tree in Slate and selecting Add EtherNet/IP Connection. Figure 3.96 – Adding EtherNet/IP Class 1 Connection Next the user will need to enter the connection parameters for the Class 1 connection. Figure 3.97 – EtherNet/IP Class 1 Connection Parameters NOTE: It is recommended that the user not change the values in the Advanced frame of the connection parameters.
  • Page 84 Setup When the ControlNet communication has failed, the EtherNet/IP IO can be configured to either keep the connection running as is, change the connection status to program mode, or force the connection offline. This will allow the Interface Fail Action EtherNet/IP device to go into a pre-determined state when the communication to the controller (i.e., connection originator on ControlNet) is lost.
  • Page 85 Setup Device Type The Device Type of the target device. Product Code The Product Code of the target device. Major Revision The Major Revision of the target device. Minor Revision The Minor Revision of the target device. Advanced (Note: Changing these values is not recommended) Tick Time For unconnected messages, this is the time for each tick to calculate the unconnected Time-Out time.
  • Page 86 Setup Connection form. Figure 3.98 – Import Connection Parameters from Online Controller The Import Connection Parameters form will open. Figure 3.99 – Import Connection Parameters – Controller Path Enter the path to the Logix controller. This can be either entered manually, or the Browse button “…”, can be selected to launch the Target Browser, where the Logix controller can be selected.
  • Page 87 Setup Figure 3.100 – Import Connection Parameters – Select Connection In order to import all the necessary connection information, the user will need to select both the appropriate Configuration Tag, and the matching Connection. The new connection’s configuration data is derived from the selected Configuration Tag, when the new connection’s parameters are derived from the selected Connection.
  • Page 88 Setup The user can then modify the Connection Name, Path and RPI as required. 3.6.5.2. ETHERNET/IP EXPLICIT MESSAGE DEVICE CONNECTIONS Up to 10 EtherNet/IP devices can be added for explicit messaging. The user will need to add each device as explained in the EtherNet/IP Devices section below. Once the EtherNet/IP devices have been added the user can then configure the required mapping for the EtherNet/IP Explicit messaging as shown in EtherNet/IP Map section below.
  • Page 89 Setup The EtherNet/IP Devices configuration consists of the following parameters: Parameter Description The configurable update rates (in milliseconds) for each scan class in the EtherNet/IP Scan Class A, B, C, D Map. Device List (per device) Device Name The user assigned instance name for the specific device. The module can use either Class 3 or Unconnected Messaging when communicating Message Type to the target EtherNet/IP device.
  • Page 90 Setup Figure 3.103 – EtherNet/IP Map configuration The EtherNet/IP Map configuration consists of the following parameters: Parameter Description The device instance name configured in the previous EtherNet/IP Devices tab. Device The selected device will be used for executing the communication function. The user can select one of four functions.
  • Page 91 Setup same transaction. The user will need to see which custom services that target device supports in that device’s user manual. Read Tag When using a Logix controller as a EtherNet/IP Device, the ControlNet Router module can read a Logix tag from the target Logix controller using Class 3 or UCMM messaging.
  • Page 92 Setup 3.6.5.3. INTERNAL DATA SPACE MAPPING When the module is operating as a EtherNet/IP Originator, the data from the EtherNet/IP IO devices can be mapped to the ControlNet interface using the Internal Map. The Internal Map configuration window is opened by either double clicking on the module in the tree or right- clicking the module and selecting Configuration and selecting the Internal Map tab.

  • Page 93: Internal Data Space Map

    Setup Figure 3.106 – IDS Copy – EtherNet/IP Originator Destination Type The destination instance will be one of the EtherNet/IP IO devices added to the EtherNet/IP IO tree in Slate. Figure 3.107 – IDS Copy – EtherNet/IP Originator Destination Instance The Destination Offset is the offset in the selected EtherNet/IP device Class 1 Output Assembly.

  • Page 94: Copy From

    Setup Bit to Bit Each bit from the source will be directly copied to each bit in the destination. Each bit from the source will be copied to each byte in the destination. If a value of one is read from the source bit then a 1 will be written to the destination byte address. If Bit to Byte a value of zero is read from the source bit then a 0 will be written to the destination byte address.
  • Page 95 Setup Figure 3.109 – IDS Copy – Internal Source Type The source instance is Not Applicable for the internal data space. The Source Offset is the offset in the Internal Data Space (IDS) which has a max of 100,000 bytes. The Count is the number of bytes that will be copied.
  • Page 96 Setup to be EIP Originator. Figure 3.112 – IDS Copy – EtherNet/IP Originator Source Type The source instance will be one of the EtherNet/IP IO devices added to the EtherNet/IP IO tree in Slate. Figure 3.113 – IDS Copy – EtherNet/IP Originator Source Instance The Source Offset is the offset in the selected EtherNet/IP device Class 1 Input Assembly.
  • Page 97 Setup Figure 3.115 – IDS Copy - Modbus Source Instance The Source Offset is the Modbus Register offset from where the data must be copied. The Count is the number of bytes that will be copied. 3.7.1.5. CNET TARGET When copying data from a connection originator (e.g. the output assembly from the Logix Controller) to the Ethernet interface, the source type needs to be CNet Target.

  • Page 98: Copy To

    Setup Figure 3.118 – IDS Copy – ControlNet Originator Source Type The source instance will be one of the ControlNet IO devices added to the ControlNet IO tree in Slate. Figure 3.119 – IDS Copy – ControlNet Originator Source Instance The Source Offset is the offset in the selected ControlNet device Scheduled Input Assembly.
  • Page 99 Setup Figure 3.121 – IDS Copy – Internal Source Type The destination instance is Not Applicable for the internal data space. The Destination Offset is the offset in the Internal Data Space (IDS) which has a max of 100,000 bytes. The Count is the number of bytes that will be copied.
  • Page 100 Setup 3.7.2.3. EIP ORIGINATOR When copying data from the ControlNet interface to a EtherNet/IP IO device Output Assembly, the destination type needs to be EIP Originator. Figure 3.124 – IDS Copy – EtherNet/IP Originator Destination Type The destination instance will be one of the EtherNet/IP IO devices added to the EtherNet/IP IO tree in Slate.
  • Page 101 Setup The destination instance will be the Modbus register type required. Figure 3.127 – IDS Copy - Modbus Destination Instance The Destination Offset is the Modbus Register offset to where the data must be copied. The Count is the number of bytes that will be copied. 3.7.2.5.

  • Page 102: Advanced

    Setup 3.7.2.6. CNET ORIGINATOR When copying data from the Ethernet interface to a ControlNet IO device Output Assembly, the destination type needs to be CNet Originator. Figure 3.130 – IDS Copy – ControlNet Originator Destination Type The destination instance will be one of the ControlNet IO devices added to the ControlNet IO tree in Slate.

  • Page 103: Module Download

    Setup Figure 3.132 – Advanced configuration The Advanced configuration consists of the following parameters: Parameter Description The ControlNet Router can synchronize its onboard clock to an NTP Server by NTP Enable enabling NTP. This setting is the IP address of the NTP Server which will be used as a time NTP –...
  • Page 104 Setup Figure 3.133 - Selecting Connection Path The new connection path can then be either entered manually or selected by means of the Target Browser. Figure 3.134 - Connection Path To initiate the download, right-click on the module and select the Download option. Document No.
  • Page 105 Setup Figure 3.135 - Selecting Download Once complete, the user will be notified that the download was successful. Figure 3.136 - Successful download Within the Slate environment the module will be in the Online state, indicated by the green circle around the module. The module is now configured and will start operating immediately. Figure 3.137 - Module online Document No.

  • Page 106: Logix Controller Programming Over Controlnet

    PC. This can be achieved in two ways: • Uploading the EDS file from the ControlNet Router online, or • Downloading the EDS file from the Aparian website and manually registering it. Document No. D138-016 Page 106 of 178...

  • Page 107: Uploading Eds File From Module

    Logix Controller Programming Over ControlNet NOTE: Older revision of RSLinx may not support the uploading of the EDS file option, in which case, the second (manual) option should be used. 4.1.1. U EDS F PLOADING ILE FROM ODULE First add the ControlNet Router module in RSLinx. Under the Communications menu select the Configure Drivers menu item.
  • Page 108 Logix Controller Programming Over ControlNet the EDS file has not yet been registered. Right-click on the ControlNet Router in the RSWho browser and select the “Upload EDS file from device” option. Figure 4.4 – RSLinx Upload EDS File from Device The Rockwell Automation EDS Wizard will then launch.

  • Page 109: Manually Installing The Eds File Option

    NSTALLING THE PTION To install the ControlNet Router’s EDS file manually, it must first be downloaded from the Aparian website: https://www.aparian.com/products/controlnetrouter#downloads The EDS file and associated icon are zipped in a single file. Save the file to local hard drive and unzip the file.
  • Page 110 Logix Controller Programming Over ControlNet Figure 4.7 – Launch EDS Hardware Installation Tool In the Hardware Installation Tool, select the Add option. Figure 4.8 – Hardware Installation Tool - ADD Use the Browse button to navigate to the folder where the EDS file was unzipped and select the EDS file.
  • Page 111 Logix Controller Programming Over ControlNet Figure 4.9 – EDS Registration Figure 4.10 – EDS File Select Follow the prompts and select the Next button to complete the EDS file registration. Document No. D138-016 Page 111 of 178 Revision 1.1...

  • Page 112: Rslogix 5000

    Logix Controller Programming Over ControlNet Figure 4.11 – EDS Registration Complete NOTE: Depending on the RSLinx revision, RSLinx may need to be shut-down and re-started. If RSLinx is running as a service, make sure the service is shut down completely before re-starting. 4.2.
  • Page 113 Logix Controller Programming Over ControlNet In the Communications window, browse to the Logix controller under the ControlNet Router, and select Online, Upload or Download as required. Figure 4.13 – Select Device Figure 4.14 – Online with Controller Document No. D138-016 Page 113 of 178 Revision 1.1...

  • Page 114: Device Firmware Update

    5. DEVICE FIRMWARE UPDATE The ControlNet Router module supports in-field firmware upgrading. The latest firmware for the module can be downloaded from the Aparian website www.aparian.com. The firmware is digitally signed, so only the correct firmware can be used. To firmware upgrade the module, follow the steps below: •...
  • Page 115 Device Firmware Update • After selecting the file, the user will be prompted to select the device to firmware upgrade on the local network. Figure 5.3 – Select the device to be updated • After the device selection the user will be prompted if the device flash must start. The firmware update will take less than 2 minutes to complete.
  • Page 116 Device Firmware Update Figure 5.5 – Firmware update successfully completed. NOTE: If for any reason the firmware update failed (e.g. power down during the update), then the module will revert back to the bootloader. The user can then simply reflash the module again to update it to the latest application firmware.

  • Page 117: Operation

    Operation 6. OPERATION 6.1. CONTROLNET 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.

  • Page 118: Controlnet Originator

    Operation 6.1.1.2. OUTPUT ASSEMBLY (CONTROLNET) The following parameters are used in the output assembly of the module. Parameter Datatype Description General Control DINT Bit 0 - Inhibit Routing MappedData SINT[] The data that is mapped to PLC5 file N9 and F10 when operating as a PCCC Client or by the Internal Mapping.
  • Page 119 Operation Figure 6.1 – Internal Mapping from EtherNet/IP to ControlNet Originator Any Internal Map copying from a ControlNet IO device will be read from the input assembly of selected ControlNet device (Target to Originator). In the Internal Map the user will specify which device instance is the target and at what offset the data must be read from the input assembly.

  • Page 120: Explicit Messaging

    Operation Figure 6.2 – Internal Mapping from ControlNet Originator to EtherNet/IP 6.2.2. E XPLICIT ESSAGING When using the ControlNet Explicit Messaging, the user can configure up to 10 ControlNet devices which will be used for the Explicit Messaging. This configuration is located in the ControlNet Devices tab.
  • Page 121 Operation Figure 6.3 – Internal Mapping from EtherNet/IP to IDS The ControlNet Router then uses the data from the EtherNet/IP Output assembly (which was copied to IDS offset 5030) to execute a Set Single Attribute to a target ControlNet device using explicit messaging.

  • Page 122: Ethernet/Ip Target

    Operation 6.3. ETHERNET/IP TARGET A controller (e.g. Logix controller) can own the ControlNet Router over EtherNet/IP using a Class 1 EtherNet/IP connection when the ControlNet Router is operating as an EtherNet/IP target. This will allow the ControlNet Router to exchange data with the controller using the input and output assembly of the Class 1 EtherNet/IP connection.

  • Page 123: Ethernet/Ip Originator

    Operation 6.3.1.2. OUTPUT ASSEMBLY (ETHERNET/IP) The following parameters are used in the output assembly of the module. Parameter Datatype Description General Control DINT Bit 0 - Inhibit Routing MappedData SINT[] The data that is mapped to by the Internal Mapping. Can be up to 492 bytes.
  • Page 124 Operation Figure 6.7 – Internal Mapping from ControlNet to EtherNet/IP Originator Any Internal Map copying from an EtherNet/IP device will be read from the input assembly of selected EtherNet/IP device (Target to Originator). In the Internal Map the user will specify which device instance is the target and at what offset the data must be read from the input assembly.

  • Page 125: Explicit Messaging

    Operation Figure 6.8 – Internal Mapping from EtherNet/IP Originator to ControlNet 6.4.2. E XPLICIT ESSAGING When using the EtherNet/IP Explicit Messaging, the user can configure up to 10 EtherNet/IP devices which will be used for the Explicit Messaging. This configuration is located in the EtherNet/IP Devices tab.
  • Page 126 Operation Figure 6.9 – Internal Mapping from ControlNet to IDS The ControlNet Router then uses the data from the ControlNet Output assembly (which was copied to IDS offset 4080) to execute a Set Single Attribute to a target EtherNet/IP device using explicit messaging.

  • Page 127: Modbus Tcp Master

    Operation 6.5. MODBUS TCP MASTER When the ControlNet Router has the Ethernet Mode set to Modbus TCP Master, then the ControlNet data can be mapped to and from configurable internal Modbus Registers using the Internal Map. The internal Modbus Registers are then asynchronously exchanged with up to 20 Modbus devices as configured in the Modbus Auxiliary Map.

  • Page 128: Modbus Tcp Slave

    Operation Figure 6.14 – Modbus Master Aux Mapping Next the data saved in the internal Modbus Register at MB Holding Register 3000 is mapped to the ControlNet Scheduled Target connection input assembly with offset 50. Figure 6.15 – Internal Mapping from Modbus Register to ControlNet NOTE: The user will need to ensure that when writing to the ControlNet Router Modbus Holding Registers that the registers holding data from the device are not inadvertently overwritten.

  • Page 129: Ftview / Panelview Interfacing

    Operation Figure 6.16 – Modbus TCP Master to ControlNet IO operation For this example the remote Modbus TCP Master will write data to Modbus Holding Register 4000 in the ControlNet Router. The ControlNet Router will map the received Modbus data (at Holding Register 4000) to the output assembly of ControlNet IO (FlexOW8) being owned (using Scheduled ControlNet) by the ControlNet Router.

  • Page 130: Panelview Reading Data From Logix

    Operation PLC5 emulation. This ControlNet Router is scheduled using RSNetWorx for ControlNet (see section ControlNet Configuration – RSNetWorx for a detailed explanation on how to schedule the ControlNet Router over a ControlNet network). The data in the MappedData tags (see the Logix Operation section) in the Logix input and output assembly of the ControlNet Router is used by the ControlNet Router to provide PLC5- Type Files that can be accessed from the PanelView by using the PLC5 driver.

  • Page 131: Panelview Writing Data To Logix

    Operation Figure 6.18 – PanelView reading Logix data over Scheduled ControlNet 6.7.2. P ANEL RITING OGIX The PanelView will write to N7 when sending integer values to Logix, and F8 when sending floating/real values. The data being read by the Logix Controller from the MappedData tag of the Input Assembly UDT will be copied from both file N7 and F8 respectively, but in N7 the data is formatted for integers, while in F8 the data is formatted for real values.

  • Page 132: Panelview Reading Diagnostic Data From Controlnet Router

    Operation Figure 6.19 – PanelView writing Logix data over Scheduled ControlNet 6.7.3. P ANEL EADING IAGNOSTIC ATA FROM ONTROL OUTER The PanelView will read N11 when accessing diagnostics information from the ControlNet Router. See the Diagnostic Data section for the format of the diagnostic data. The data will be read similar to the above section where the PanelView will read the Logix data using the PLC5 driver emulation.

  • Page 133: Internal Data Space (Ids)

    Operation 6.8. INTERNAL DATA SPACE (IDS) The ControlNet Router Status and Control can be mapped to a specific Internal Data Space register offset. The Internal Status Offset Start is the address in the IDS where the module status will be written to. The Internal Control Offset Start is the address in the IDS where the module control will be read from.
  • Page 134 Operation Ethernet Port1 Status SINT Status of Ethernet Port 1. 0 – The Link is down Link Up 21.0 1 – The Link is up Ethernet Port2 Status SINT Status of Ethernet Port 2. 0 – The Link is down Link Up 22.0 1 –...

  • Page 135: Internal Control

    Operation operating as a ControlNet target. The module ControlNet Keeper functionality ControlNet Keeper Active 28.7 has been enabled and is active. When the module has the Keeper functionality enabled and another Keeper is active with a ControlNet Keeper CRC Mismatch 29.0 signature that does not match the local module.

  • Page 136: Diagnostics

    Diagnostics 7. DIAGNOSTICS 7.1. LEDS The module provides three LEDs for diagnostics purposes as shown in the front view figure below. A description of each LED is given in the table below. Figure 7.1 – ControlNet Router front view Description The module LED will provide information regarding the system-level operation of the module.

  • Page 137: Module Status Monitoring In Slate

    The statistics can be accessed in full by Slate or using the web server in the module. To view the module’s status in the Aparian-Slate environment, the module must be online. If the module is not already Online (following a recent configuration download), then right-click on the module and select the Go Online option.

  • Page 138: General

    Diagnostics Figure 7.3 - Selecting online Status The Status monitoring window can be opened by either double-clicking on the Status item in the Project Explorer tree, or by right-clicking on the module and selecting Status. The status window contains multiple tabs to display the current status of the module. 7.2.1.
  • Page 139 Diagnostics The General tab displays the following general parameters: Parameter Description EtherNet/IP Owned When the module is configured as an EtherNet/IP Target, this will indicate if the module is owned by an EtherNet/IP connection originator. EtherNet/IP Originator When the module is configured as an EtherNet/IP Originator, this will show if all the Class 1 and Explicit Message connections to EtherNet/IP target devices are established and returning valid data.
  • Page 140 Diagnostics Down The Ethernet connector has not been successfully connected to an Ethernet network. The Ethernet connector has successfully connected to an Ethernet network. Mirror Enabled The Ethernet port is mirroring the traffic on the other Ethernet port. Ethernet DLR (Device Level Ring) The status of the Ethernet DLR.

  • Page 141: Controlnet Statistics

    Diagnostics 7.2.2. C ONTROL TATISTICS The ControlNet Statistics tab displays the statistics associated with the ControlNet communication network. Figure 7.5 - Status monitoring – ControlNet Statistics Statistic Description CNet Rx Packet Count Number of ControlNet packets received. CNet Tx Packet Count Number of ControlNet packets sent.

  • Page 142: Controlnet Explicit

    Diagnostics 7.2.3. C ONTROL XPLICIT The ControlNet Explicit Statistics tab displays the statistics associated with ControlNet Device unscheduled explicit mapping. NOTE: This tab is only applicable when the module has the ControlNet mode set to Originator. Figure 7.6 - Status monitoring – ControlNet Explicit Statistics Statistic Description Read Successes...

  • Page 143: Controlnet Map

    Diagnostics 7.2.4. C ONTROL The ControlNet Map tab displays the success counts for each ControlNet device mapped item. NOTE: This tab is only relevant when the module has the ControlNet mode set to Originator. Figure 7.7 - Status monitoring – ControlNet Map Each time a mapped item is executed successfully its associated count will increase.

  • Page 144: Pccc Statistics

    Diagnostics 7.2.5. PCCC S TATISTICS The PCCC tab displays the Ethernet PCCC statistics. NOTE: This tab is only applicable when the module has the Ethernet mode set to PCCC Client. Figure 7.8 - Status monitoring – PCCC Statistics Statistic Description PCCC Connection Requests The number of PCCC connection establishment requests received.

  • Page 145: Ethernet/Ip Explicit

    Diagnostics 7.2.6. E /IP E THER XPLICIT The EtherNet/IP Explicit Statistics tab displays the statistics associated with EtherNet/IP Device explicit mapping. NOTE: This tab is only applicable when the module has the Ethernet mode set to EtherNet/IP Originator. Figure 7.9 - Status monitoring – EtherNet/IP Explicit Statistic Description Read Successes...

  • Page 146: Ethernet/Ip Map

    Diagnostics When the Explicit Message Function is a Tag Read, this statistic will increase CIP Tag Read Successes when there was a successful Logix Tag Read. When the Explicit Message Function is a Tag Write, this statistic will increase CIP Tag Write Successes when there was a successful Logix Tag Write.

  • Page 147: Ethernet/Ip Originator

    Diagnostics 7.2.8. E /IP O THER RIGINATOR The EtherNet/IP Originator tab displays the EtherNet/IP Class 1 connection status and statistics for each configured EtherNet/IP device. NOTE: This tab is only applicable when the module has the Ethernet mode set to EtherNet/IP Originator. Figure 7.11 - Status monitoring –...

  • Page 148: Logix

    Diagnostics Connection Timeouts The number of this connection was closed due to timeouts. Tx Count Number of Class 1 messages sent to the specific target device. Rx Count Number of Class 1 messages received from the specific target device. Table 7.7 – EtherNet/IP Class 1 status and statistics 7.2.9.

  • Page 149: Modbus

    Diagnostics Logix tag being set to either None or Read Only. Tag Reads The number of tag read transactions executed by the ControlNet Router module. Tag Writes The number of tag write transactions executed by the ControlNet Router module. ENIP Retries This count increases when no response was received from the Logix Controller by the time the ENIP timeout is reached.
  • Page 150 Diagnostics The Modbus tab displays the following parameters: Statistic Description Tx Packet Count The number of Modbus packets sent by the module. Rx Packet Count The number of Modbus packets received by the module. Checksum errors The number of corrupted Modbus packets received by the module. Parity errors The number of bytes with parity errors received by the module.

  • Page 151: Cip Statistics

    Diagnostics 7.2.11. CIP S TATISTICS The CIP tab displays the Ethernet CIP statistics. Figure 7.14 - Status monitoring – CIP Statistics Statistic Description Class 1 Timeout Count The number of Class 1 connections closed due to Timeouts. Class 3 Timeout Count The number of Class 3 connections closed due to Timeouts.

  • Page 152: Ethernet Clients

    Diagnostics 7.2.12. E THERNET LIENTS The Ethernet Clients tab displays details of the Ethernet and EtherNet/IP clients connected to the ControlNet Router. Figure 7.15 –Status monitoring – Ethernet Client Statistics 7.2.13. TCP/ARP The TCP/ARP tab displays details of the internal Ethernet ARP and TCP lists of the ControlNet Router.

  • Page 153: Target Device Status Monitoring In Slate

    Diagnostics 7.3. TARGET DEVICE STATUS MONITORING IN SLATE The ControlNet Router can also provide individual statistics and status for each for each of the EtherNet/IP Class 1 or ControlNet Scheduled IO devices when the Ethernet Mode is EtherNet/IP Originator or the ControlNet Mode is ControlNet Originator. 7.3.1.
  • Page 154 Diagnostics 7.3.1.1. GENERAL The General Status for the EtherNet/IP device shows the connection statistics and parameters associated with the EtherNet/IP Class 1 connection. Figure 7.18 – EtherNet/IP Device Status – General Status Statistic Description Connection Status The current connection status of the module. Connected The device is connected and exchanging data using Class 1 cyclic communication.
  • Page 155 Diagnostics Tx Count Number of Class 1 messages sent to the specific target device. Rx Count Number of Class 1 messages received from the specific target device. Connection Details Serial Number The active connection’s serial number. O -> T Connection Id The active connection Originator to Target Connection Id.

  • Page 156: Controlnet

    Diagnostics Figure 7.20 – EtherNet/IP Device Status – Output Data 7.3.2. C ONTROL When online with the module in Slate, right-click on the desired ControlNet device under the ControlNet Connections tree in Slate and select Status. Figure 7.21 – ControlNet Device Status – Status selection Document No.
  • Page 157 Diagnostics 7.3.2.1. GENERAL The General Status for the ControlNet device shows the connection statistics and parameters associated with the ControlNet Scheduled connection. Figure 7.22 – ControlNet Device Status – General Status Statistic Description Connection Status The current connection status of the module. Connected The device is connected and exchanging data using Scheduled communication.
  • Page 158 Diagnostics Rx Count Number of Scheduled messages received from the specific target device. Connection Details Serial Number The active connection’s serial number. O -> T Connection Id The active connection Originator to Target Connection Id. T -> O Connection Id The active connection Target to Originator Connection Id.

  • Page 159: Module Event Log

    Diagnostics Figure 7.24 – ControlNet Device Status – Output Data 7.4. MODULE EVENT LOG The ControlNet Router module logs various diagnostic records to an internal event log. These logs are stored in non-volatile memory and can be displayed using Slate or via the web interface.

  • Page 160: Web Server

    Diagnostics The Event Log window will open and automatically read all the events from the module. The log entries are sorted so as to have the latest record at the top. Custom sorting is achieved by double-clicking on the column headings. Figure 7.26 - Module Event Log The log can also be stored to a file for future analysis, by selecting the Save button in the tool menu.

  • Page 161: Controlnet Packet Capture

    Diagnostics Figure 7.27 – Web interface 7.6. CONTROLNET PACKET CAPTURE The module provides the capability to capture the ControlNet traffic for analysis. The will allow the user and a remote support team to resolve any possible issues on site. To invoke the capture of the module, right-click on the ControlNet Router and select the ControlNet Packet Capture option.

  • Page 162: Operational Capture

    Diagnostics Figure 7.28 - Selecting ControlNet Packet Capture 7.6.1. O PERATIONAL APTURE The operational capture is the ControlNet packet capture when the module is in normal routing operation mode. This is set when the Main Mode parameter in the General Configuration is set to Operational.
  • Page 163 Diagnostics pressing the Stop button. Figure 7.30 – ControlNet Packet Capture complete The captured ControlNet packets are tabulated as follows: Statistic Description Index The packet index, incremented for each packet sent or received. Time The elapsed time since the module powered up. The status of the packet.

  • Page 164: Promiscuous Capture

    Diagnostics ControlNet Packet Capture Viewer option in the tools menu. Figure 7.31 - Selecting the ControlNet Packet Capture Viewer 7.6.2. P ROMISCUOUS APTURE The Promiscuous Capture is the ControlNet packet capture when the module is not actively part of the ControlNet network, but rather listening to all packet being sent on the network. This is set when the Main Mode parameter in the General Configuration is set to Promiscuous Capture.
  • Page 165 Diagnostics Figure 7.32 – ControlNet Pre-Capture Filter The ControlNet Packet Capture window will open and automatically start capturing all ControlNet packets. Figure 7.33 – ControlNet packet capture – Promiscuous Mode To display the captured ControlNet packets, the capture process must first be stopped, by pressing the Stop button.
  • Page 166 Diagnostics Figure 7.34 – ControlNet Packet Capture complete – Promiscuous Mode The captured ControlNet packets are tabulated as follows: Statistic Description Index The packet index, incremented for each packet sent or received. Time The elapsed time since the module powered up. The status of the packet.

  • Page 167: Modbus Packet Capture

    Diagnostics 7.7. MODBUS PACKET CAPTURE The module provides the capability to capture the Modbus traffic for analysis. The will allow the user and a remote support team to resolve any possible issues on site. To invoke the capture of the module, double-click on the Modbus Packet Capture item in the Project Explorer tree.
  • Page 168 Diagnostics Figure 7.36 – Modbus packet capture To display the captured Modbus packets, the capture process must first be stopped, by pressing the Stop button. Figure 7.37 – Modbus Packet Capture complete The captured Modbus packets are tabulated as follows: Statistic Description Index...

  • Page 169: Module Status Report

    Diagnostics Figure 7.38 - Selecting the Modbus Packet Capture Viewer 7.8. MODULE STATUS REPORT For assisting with support Slate can generate a status report for the module which is a word document that can be emailed to support. To generate this report the user can right-click on Document No.
  • Page 170 Diagnostics the module (when online in Slate) and select Generate Status Report. Figure 7.39 – Module Status Report Document No. D138-016 Page 170 of 178 Revision 1.1...

  • Page 171: Technical Specifications

    Technical Specifications 8. TECHNICAL SPECIFICATIONS 8.1. DIMENSIONS Below are the enclosure dimensions as well as the required DIN rail dimensions. All dimensions are in millimetres. Figure 8.1 – ControlNet Router enclosure dimensions Figure 8.2 - Required DIN Rail dimensions Document No. D138-016 Page 171 of 178 Revision 1.1...

  • Page 172: Electrical

    Technical Specifications 8.2. ELECTRICAL Specification Rating Power requirements Input: 10 – 36V DC, (85 mA @ 24 VDC) Power consumption 2W (max) Connector 3-way terminal Conductors 24 – 18 AWG Enclosure rating IP20, NEMA/UL Open Type Temperature -20 – 70 °C Earth connection Yes, terminal based Emissions...

  • Page 173: Controlnet

    Technical Specifications 8.4. CONTROLNET Specification Rating Connectors 2 x BNC connectors (ControlNet A and B). Redundant ControlNet Supported Conductors Quad shield RG-6 coaxial cable Routing Supported (RSLogix programming) Table 8.3 – ControlNet specification 8.5. CONTROLNET TARGET Specification Rating Scheduled Connection Size Max Input Size –...

  • Page 174: Ethernet/Ip Target

    Technical Specifications Specification Rating Max PCCC Connections Max PCCC Payload 1000 bytes Table 8.6 – PCCC specification 8.8. ETHERNET/IP TARGET Specification Rating Class 1 Connection Size Max Input Size – 500 bytes (492 bytes mapped data) Max Output Size – 496 bytes (492 bytes mapped data) Class 1 Connection Count Class 3 Messaging Supported UCMM Messaging Supported...

  • Page 175: Modbus Tcp Slave

    Technical Specifications Input Status 0 – 65535 Coil Status 0 – 65535 Base Offset Modbus (Base 0) PLC (Base 1) Configurable Modbus TCP Port Data Re-formatting Supported BB AA BB AA DD CC CC DD AA BB DD CC BB AA Table 8.9 –...
  • Page 176 Technical Specifications * F/W 1.001 UL Mark File: E494895 CLASS 1, DIV 2, GROUPS A, B, C, D Table 8.11 – Certifications Document No. D138-016 Page 176 of 178 Revision 1.1...

  • Page 177: Appendix

    Appendix 9. APPENDIX Channel A Channel B Value LED State Flash Phase 0 Flash Phase 1 Flash Phase 0 Flash Phase 1 Green Green Green Green Green Flashing Green Green Green Flashing Red Flashing Red/Green Green Green Railroad Red Railroad Red/Green Green Green Table 9.1 –...

  • Page 178: Index

    Index 10. INDEX input voltage, 20 Adanced, 88, 89 assembly instance, 32, 69 LED, 136, 137 CANopen Router, 6, 149 MODBUS, 150 CANopen Router, 149 CANopen Router general configuration, 41, 59, 73, 75, 76, 78, 79, 81, 92, 93 output assembly, 117, 118, 122, 123, 129 Connection path, 103 Contact Us, 16 ControlNet, 6, 8, 10, 15, 17, 18, 26, 27, 28, 29, 103, 137,...

Table of Contents