ProSoft Technology A-DNTR User manual

DeviceNet Router

User Manual

A-DNTR

Document No. D116-009

10/2017

Revision 1.3

Preface

Document No. D116-009 Page 2 of 66

Revision 1.3

CONTENTS

1. Preface ............................................................................................................................... 4

1.1. Introduction to the DeviceNet Router ........................................................................ 4

1.2. Features ....................................................................................................................... 5

1.3. Architecture ................................................................................................................. 5

1.4. Additional Information ................................................................................................ 7

1.5. Support ........................................................................................................................ 8

2. Installation ......................................................................................................................... 9

2.1. Module Layout ............................................................................................................ 9

2.2. Module Mounting ..................................................................................................... 10

2.3. DeviceNet .................................................................................................................. 11

2.4. Ethernet Port ............................................................................................................. 12

3. Setup ................................................................................................................................ 13

3.1. Install Configuration Software .................................................................................. 13

3.2. Network Parameters ................................................................................................. 13

3.3. Creating a New Project .............................................................................................. 18

3.4. General parameters .................................................................................................. 20

3.5. PLC5 Mapping ............................................................................................................ 22

3.6. Scheduled Parameter Mapping................................................................................. 23

3.6.1. Scheduled Devices ............................................................................................. 24

3.6.2. Scheduled Parameters ....................................................................................... 26

3.7. Module Download ..................................................................................................... 29

3.8. Logix 5000 Configuration .......................................................................................... 31

3.8.1. Add Module to I/O Configuration ...................................................................... 31

3.8.2. Importing UDTs and Mapping Routines ............................................................ 33

4. DeviceNet Configuration – RSNetworx ............................................................................ 36

4.1. Polled Method ........................................................................................................... 37

4.2. Change of State Method ........................................................................................... 38

4.3. Input and Output Mapping ....................................................................................... 39

5. FTView Configuration ....................................................................................................... 43

5.1. Communication ......................................................................................................... 43

5.2. Animation .................................................................................................................. 46

Preface

Document No. D116-009 Page 3 of 66

Revision 1.3

5.3. Diagnostic Data ......................................................................................................... 48

6. Operation ......................................................................................................................... 49

6.1. Message Routing ....................................................................................................... 49

6.2. Logix 5000 assemblies ............................................................................................... 49

6.2.1. Input Assembly................................................................................................... 49

6.2.2. Output Assembly................................................................................................ 50

7. Diagnostics ....................................................................................................................... 52

7.1. LEDs ........................................................................................................................... 52

7.2. Module Status Monitoring in Slate ........................................................................... 52

7.3. DeviceNet Packet Capture ........................................................................................ 59

7.4. Module Event Log...................................................................................................... 61

7.5. Web Server ................................................................................................................ 62

8. Technical Specifications ................................................................................................... 63

8.1. Dimensions ................................................................................................................ 63

8.2. Electrical .................................................................................................................... 64

8.3. Ethernet ..................................................................................................................... 64

8.4. DeviceNet .................................................................................................................. 65

8.5. PCCC .......................................................................................................................... 65

8.6. Certifications ............................................................................................................. 65

9. Index ................................................................................................................................. 66

Revision History

Revision Date Comment

1.0 29 April 2016 Initial document

1.1 27 June 2016 Adjusted temperature range

1.2 5 June 2017 Add Scheduled mode to configuration

Update certification

1.3 5 October 2017 Added UL Class 1 Division 2

Preface

Document No. D116-009 Page 4 of 66

Revision 1.3

1. PREFACE

1.1. INTRODUCTION TO THE DEVICENET ROUTER

This manual describes the installation, operation, and diagnostics of the Aparian DeviceNet

Router. The DeviceNet Router provides intelligent data routing between DeviceNet and

EtherNet/IP or Ethernet PCCC (CSP). The later allows the module to emulate a PLC5 providing

a legacy interface for PanelViews and other devices (as shown below).

Figure 1.1. – Typical Setup

The DeviceNet Router can also be used in Scheduled Mode allowing the user to extract

parameters from various DeviceNet devices and write them directly into Logix tags. The

DeviceNet Router will also apply the necessary scaling to the values per EDS file or custom

user configuration.

Preface

Document No. D116-009 Page 5 of 66

Revision 1.3

1.2. FEATURES

The DeviceNet Router is able to asynchronously exchange data between a DeviceNet polling

master (scanner) and an Ethernet PCCC device. The sizes of the DeviceNet’s produced and

consumed data are independently configurable from 0 to 128 bytes each.

The consumed (DeviceNet) data can then be mapped to a PLC5 type address file, e.g. N33,

and then read by an Ethernet device e.g. a PanelView. Similarly, the produced data

(DeviceNet) can also be mapped to a PLC5 type address file, to which an Ethernet device could

write.

In addition, the DeviceNet Router can be used to transfer parameters of a DeviceNet device

directly to Logix tags. The scaling of the parameter values will either be extracted from the

EDS file imported or can be manually updated by the user.

The module also provides a range of statistics and an on-board DeviceNet traffic analyser to

assist with fault finding.

A built-in webserver provides detailed diagnostics of system configuration and operation,

including the display of DeviceNet operation and communication statistics, without the need

for any additional software.

The DeviceNet Router is configured using the Aparian Slate application. This program can be

downloaded from www.aparian.com free of charge.

1.3. ARCHITECTURE

The figure below provides an example of the typical network setup in PLC Emulation mode,

where the DeviceNet Router acts as a DeviceNet slave device.

Preface

Document No. D116-009 Page 6 of 66

Revision 1.3

Figure 1.2. - Example of a typical network setup in PLC Emulation mode

In this example, the DeviceNet Router provides the PanelView data access to the PLC5’s

DeviceNet scanner module (SDN).

In the next example the DeviceNet Router is used to extract parameters from various

DeviceNet devices (running in conjunction with the DeviceNet Scanner – e.g. DNB).

Preface

Document No. D116-009 Page 7 of 66

Revision 1.3

Figure 1.3. - Example of a typical network setup in Scheduled Parameter Mode

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

DeviceNet Router User Manual

DeviceNet Router Datasheet

Example Code & UDTs

http://www.aparian.com/products/devicenetrouter

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

DeviceNet http://www.odva.org

Table 1.1. - Additional Information

Preface

Document No. D116-009 Page 8 of 66

Revision 1.3

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 support@aparian.com

Table 1.2. – Support Details

Installation

Document No. D116-009 Page 9 of 66

Revision 1.3

2. INSTALLATION

2.1. MODULE LAYOUT

The module has two ports at the bottom of the enclosure as shown in the figure below. The

ports are used for Ethernet and DeviceNet. The 5-way DeviceNet connector also provides

power to the module. The Ethernet cable must be wired according to industry standards

which can be found in the additional information section of this document.

Figure 2.1. – DeviceNet Router side and bottom view

The module provides three diagnostic LEDs as shown in the front view figure below. These

LEDs are used to provide information regarding the module system operation, the Ethernet

interface, and the DeviceNet interface.

Installation

Document No. D116-009 Page 10 of 66

Revision 1.3

Figure 2.2. – DeviceNet Router front and 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 Reserved

DIP Switch 4 Applies the 120Ω terminating resistor across the DeviceNet network. Switched

between Can-H and Can-L.

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. D116-009 Page 11 of 66

Revision 1.3

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 screw driver 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

2.3. DEVICENET

A five-way DeviceNet connector is used to connect the DeviceNet CAN interface (Can-L, Can-

H), 24Vdc power, and Shield.

Installation

Document No. D116-009 Page 12 of 66

Revision 1.3

Figure 2.5 - DeviceNet connector

NOTE: It is important that the shield is connected to earth at only one end of

the cable to avoid current loops.

2.4. ETHERNET PORT

The Ethernet connector should be wired according to industry standards. Refer to the

additional information section in this document for further details.

Setup

Document No. D116-009 Page 13 of 66

Revision 1.3

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. NETWORK PARAMETERS

The module will have DHCP (Dynamic Host Configuration Protocol) enabled as factory default.

Thus a DHCP server must be used to provide the module with the required network

parameters (IP address, subnet mask, etc.). There are a number of DHCP utilities available,

however it is recommended that the DHCP server in Slate be used. Within the Slate

environment, the DHCP server can be found under the Tools menu.

Figure 3.2. - Selecting DHCP Server

Once opened, the DHCP server will listen on all available network adapters for DHCP requests

and display their corresponding MAC addresses.

Setup

Document No. D116-009 Page 14 of 66

Revision 1.3

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.

To assign an IP address, click on the corresponding “Assign” button. The IP Address

Assignment window will open.

Figure 3.4. - Assigning IP Address

The required IP address can then be either entered, or a recently used IP address can be

selected by clicking on an item in the Recent List. If the “Enable Static” checkbox is checked,

then the IP address will be set to static after the IP assignment, thereby disabling future DHCP

requests.

Once the IP address window has been accepted, the DHCP server will automatically assign the

IP address to the module and then read the Identity object Product name from the device.

The successful assignment of the IP address by the device is indicated by the green

Setup

Document No. D116-009 Page 15 of 66

Revision 1.3

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.

NOTE: It is important to return DIP switch 2 back to Off position, to avoid the

module returning to a DHCP mode after the power is cycled again.

If the module’s DIP switch 2 is in the On position during the address assignment, the user will

be warned by the following message.

Figure 3.6. - Force DHCP warning

In addition to the setting the IP address, a number of other network parameters can be set

during the DHCP process. These settings can be viewed and edited in Slate’s Application

Settings, in the DHCP Server tab. Once the DHCP process has been completed, the network

settings can be set using the Ethernet Port Configuration via the Target Browser. The Target

Browser can be accessed under the Tools menu.

Setup

Document No. D116-009 Page 16 of 66

Revision 1.3

Figure 3.7. - Selecting the Target Browser

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.

Setup

Document No. D116-009 Page 17 of 66

Revision 1.3

Figure 3.9. - Selecting Port Configuration

All the relevant Ethernet port configuration parameters can be modified using the Port

Configuration window.

Figure 3.10. - Port Configuration

Alternatively, these parameters can be modified using Rockwell Automation’s RSLinx

software.

Setup

Document No. D116-009 Page 18 of 66

Revision 1.3

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. - Creating a new project

A Slate project will be created, showing the Project Explorer tree view. To save the project

use the Save option under the File menu. A new device can now be added by selecting Add

under the Device menu.

Figure 3.12. - Adding a new device

In the Add New Device window select the DeviceNet Router, and click the Ok button.

Setup

Document No. D116-009 Page 19 of 66

Revision 1.3

Figure 3.13 – Selecting a new DeviceNet 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.

Figure 3.14 - DeviceNet Router configuration

Setup

Document No. D116-009 Page 20 of 66

Revision 1.3

3.4. GENERAL PARAMETERS

The DeviceNet parameters will be configured by Slate. When downloading this configuration

into the module it will be saved in non-volatile memory that persists when the module is

powered down.

NOTE: When a firmware upgrade is performed the module will clear all

DeviceNet and mapping configuration.

The general configuration consists of the following parameters:

Parameter Description

Instance Name

This parameter is a user defined name to identify between various DeviceNet

Routers.

Description

This parameter is used to provide a more detail description of the application for the

module.

Major Revision The major revision of the module

IP Address

The IP address of the target module. The user can use the target browse button to

launch the target browser to the select the DeviceNet Router on the network.

Mapping Mode

There are two mapping modes to choose from:

PLC5 Emulation

When in this mode the DeviceNet Router will produce and consume data on the

DeviceNet network and emulate a PLC5 Controller (as a PCCC Ethernet slave) over

Ethernet. This will, for example, allow the user to connect a newer “Ethernet only”

PanelView to a DeviceNet network.

Scheduled Parameter

When in this mode the DeviceNet Router will request parameters from various

DeviceNet nodes, scale them to engineering units and write them into Logix tags. This

will allow the user to extract additional parameters from DeviceNet devices without

making use of Logix message blocks.

PLC5 Emulation

The IP Address used to emulate a PLC5 controller. This IP address will be seen as the

IP address of the PLC5 controller that the DeviceNet 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.

Logix Configuration

Logix Path:

The Logix path is the CIP path to the Logix controller which will be used to exchange

data with the various DeviceNet devices. The user can use the browse button to launch

the target browser to the select the Logix controller on the network.

ENIP Retry Limit

The amount of EtherNet/IP retries the module will make once no response was

received from the Logix Controller.

ENIP TimeOut

The time in milliseconds after which a retry is sent. Once the first retry is sent the next

retry will be sent after the same amount of time. This will repeat until the ENIP Retry

Limit is reached.

Table 3.1 - General configuration parameters

Page is loading ...

ProSoft Technology A-DNTR User manual

ProSoft Technology A-DNTR User manual

Related papers

Other documents