ControlNet Communications Module

7/22/2019 ControlNet Communications Module

1/160

Instruction Manual

ControlNetCommunications Module

M/N RECOMM-CNET

D2-3497


2/160


3/160

Contents I

CONTENTSChapter 1 Introduction

1.1 ControlNet Module Features.......................................... 1-1

1.2 Related Documentation ................................................. 1-2

1.3 Conventions Used in This Manual................................. 1-2

1.4 Getting Assistance from Reliance Electric..................... 1-2

Chapter 2 Getting Started

2.1 ControlNet Module Components ................................... 2-1

2.2 Required Equipment...................................................... 2-2

2.3 Installation Checklist ...................................................... 2-3

Chapter 3 Installing the ControlNet Module

3.1 Preparing for an Installation........................................... 3-1

3.2 Commissioning the Module ........................................... 3-1

3.3 Connecting the Module to the Drive .............................. 3-2

3.4 Connecting the Module to the Network.......................... 3-5

3.5 Applying Power.............................................................. 3-6

Chapter 4 Configuring the ControlNet Module4.1 Configuration Tools........................................................ 4-1

4.2 Using the LCD OIM to Configure the Module ................ 4-2

4.3 Setting the Node Address.............................................. 4-2

4.4 Setting the I/O Configuration ......................................... 4-3

4.5 Selecting Master-Slave.................................................. 4-4

4.6 Selecting Reference Adjust ........................................... 4-5

4.7 Setting a Fault Action..................................................... 4-5

4.7.1 Changing the Fault Action ................................... 4-6

4.7.2 Setting the Fault Configuration Parameters ........ 4-7

4.7.3 Resetting the Module........................................... 4-7

4.8 Viewing the Module Configuration................................. 4-8

Chapter 5 RSNetWorx Configuration for PLC-5C Applications5.1 Configuring a ControlNet Network: An Example............ 5-1

5.1.1 Installing and Registering EDS Files in

RSNetWorx ......................................................... 5-2

5.1.2 Configuring a Network with RSNetWorx.............. 5-7

5.1.3 Verifying Network Properties ............................. 5-18


4/160

II ControlNet Communications Module

Chapter 6 PLC-5C Applications

6.1 About I/O Messaging .....................................................6-1

6.2 Understanding the I/O Image......................................... 6-2

6.3 Using Logic Command/Status ....................................... 6-4

6.4 Using Reference/Feedback ........................................... 6-5

6.5 Using Datalinks.............................................................. 6-5

6.5.1 Rules for Using Datalinks .................................... 6-5

6.5.2 32-Bit Parameters using 16-Bit Datalinks............ 6-6

6.6 Function of the Sample Program ................................... 6-7

6.7 Main Program (PLC-5C) ................................................6-8

6.8 About Explicit Messaging............................................. 6-12

6.8.1 Performing Explicit Messages ........................... 6-12

6.8.2 Explicit Messaging Examples ............................6-13

Chapter 7 ControlLogix Applications

7.1 Configuring a ControlLogix CNB Scanner ..................... 7-2

7.2 Function of the Sample Program ................................. 7-15

7.3 RSLogix 5000 Ladder Logic Program.......................... 7-17

7.4 About Explicit Messaging............................................. 7-19

7.4.1 Performing Explicit Messages ........................... 7-19

7.4.2 Explicit Messaging Examples ............................7-20

Chapter 8 Troubleshooting the ControlNet Module and Network

8.1 Understanding the Status Indicators.............................. 8-18.1.1 DRIVE Status Indicator........................................ 8-2

8.1.2 MS Status Indicator ............................................. 8-3

8.1.3 NET A and B Together ........................................ 8-4

8.1.4 NET A and B Independently ................................ 8-5

8.2 Module Diagnostic Items................................................ 8-6

8.3 Viewing and Clearing Events ......................................... 8-8

Appendix A Technical Specifications...................................................... A-1

Appendix B ControlNet Module Parameters ............................................ B-1

Appendix C ControlNet Objects ............................................................... C-1

Appendix D Logic Command/Status Words............................................. D-1

Glossary ..................................................................................Glossary-1

Index .......................................................................................Index-1


5/160


6/160


7/160

Contents V

List of Tables

Table 2.1 Equipment Shipped with the ControlNet Module ................... 2-2

Table 2.2 Required User-Supplied Equipment ...................................... 2-2

Table 4.1 Configuration Tools................................................................ 4-1

Table 4.2 Selections for Drive Response to Communication Fault........ 4-6

Table 4.3 Fault Configuration Parameters............................................. 4-7

Table 4.4 Module Configuration Status Parameters.............................. 4-8

Table 5.1 Input/Output Table ............................................................... 5-14

Table 6.1 Parameter Settings for the Sample Program......................... 6-7

Table 7.1 Parameter Settings for the Sample Program....................... 7-16

Table 8.1 DRIVE Status Indicator: State Definitions.............................. 8-2

Table 8.2 MS Status Indicator: State Definitions ................................... 8-3

Table 8.3 NET A and B Together: State Definitions .............................. 8-4

Table 8.4 NET A and B Independently: State Definitions ......................8-5

Table 8.5 Module Diagnostic Items........................................................ 8-6

Table 8.6 Event Codes and Descriptions............................................... 8-8


8/160

VI ControlNet Communications Module


9/160

Introduction 1-1

CHAPTER1Introduction

The ControlNetmodule (RECOMM-CNET) is an embedded

communication option for DPI

AC drives, such as the SP600

drive. The module is mounted in the drive and receives its requiredpower from the drive and from the network.

The module can be used with other products that implement DPI, aperipheral communication interface. Refer to the documentation foryour product for specific information about how it works with themodule.

This manual is intended for qualified electrical personnel familiarwith installing, programming, and maintaining AC drives andnetworks.

1.1 ControlNet Module Features

The ControlNet module features the following:

A number of configuration tools that can be used to configure themodule and connected drive. The tools include the LCD OperatorInterface Module (OIM) on the drive and drive-configurationsoftware such as VS Utilities (version 1.01 or later).

Status indicators that report the status of the drivecommunications, module, and network. They are visible bothwhen the cover is opened and when it is closed.

I/O, including Logic Command/Reference and up to four pairs ofDatalinks, that may be configured for your application using aparameter.

Support of explicit messages.

User-defined fault actions that determine how the module and thedrive respond to communication disruptions on the network andcontrollers in idle mode.


10/160

1-2 ControlNet Communications Module

1.2 Related Documentation

Refer to the following related publications as necessary for moreinformation. All of the publications are available fromhttp://www.theautomationbookstore.com.

D2-3485 SP600 AC Drive User Manual

D2-3488 VS Utilities Getting Results ManualOnline help installed with the software

9399-WAB32GR Getting Results with RSLinxOnline help installed with the software

9399-RL53GR RSLogix 5 Getting Results GuideOnline help installed with the software

9399-RL50GR RSLogix 500 Getting Results GuideOnline help installed with the software

9399-RLD300GR RSLogix 5000 Getting Results GuideOnline help installed with the software

9357-CNETL3 RSNetWorx for ControlNet Getting ResultsGuideOnline help installed with the software.

1.3 Conventions Used in This Manual

The following convention is used throughout this manual:

Parameters are referenced as follows:

Parameter Name (Parameter Number)

For example: DPI Port (1)

1.4 Getting Assistance from RelianceElectric

If you have any questions or problems with the products describedin this instruction manual, contact your local Reliance Electric salesoffice.

For technical assistance, call 1-800-726-8112.


11/160

Getting Started 2-1

CHAPTER2Getting Started

This chapter provides:

A description of the ControlNet module components A list of parts shipped with the module

A list of user-supplied parts required for installing the module

An installation checklist

2.1 ControlNet Module Components

Status Indicators Four LEDs that indicate the status of theControlNet channel(s), DPI, and the module. Referto chapter 8 for more information.

DPI Connector A 20-pin, single-row shrouded male header. AnInternal Interface cable is connected to thisconnector and a connector on the drive.

Channel A BNCReceptacleChannel ABNC connection for the ControlNetcable.

Channel B BNCReceptacle

Channel BBNC is an optional connection for theredundnat ControlNet cable.

ControlNet NodeAddress Switches

Switches for setting the node address.

Figure 2.1 Components of the ControlNet Module


12/160


2.2 Required Equipment

Table 2.1 lists the equipment shipped with the ControlNet module.When you unpack the module, verify that the package includes all ofthese items.

Table 2.2 lists user-supplied equipment also required to install andconfigure the ControlNet module.

Table 2.1 Equipment Shipped with the ControlNet Module

Item Description

One RECOMM-CNET ControlNet module

A 2.54 cm (1 in) and a 15.24 cm (6 in) Internal Interface cable(only one cable is needed to connect the module to the drive)

One grounding wrist strap

ControlNet Module User Manual (D2-3497)

Table 2.2 Required User-Supplied Equipment

Item Description

A small flathead or Phillips screwdriver

Configuration tool, such as:

LCD OIM

VS Utilities (version 1.01 or later)

with RECOMM-232 Serial Converter

RSNetWorx for ControlNet (version 3.00.00 or later)

Controller configuration software (for example, RSLogix 5,RSLogix 500, or RSLogix 5000)

A PC connection to the ControlNet network, such as:

1784-PCC

1770-KFC

1784-KTCX


13/160

Getting Started 2-3

2.3 Installation Checklist

This section is designed to help experienced users start using theControlNet module. If you are unsure about how to complete a step,refer to the referenced chapter.

Step Action Refer to 1 Review the safety precautions for the

module.Throughoutthis manual

2 Verify that the drive is properly installed. SP600 ACDrive UserManual

3 Install the module.Verify that the drive is not powered. Then,connect the module to the network using aControlNet cable and to the drive using theInternal Interface cable. Use the captivescrews to secure and ground the module tothe drive.

Chapter 3,Installing theControlNetModule

4 Apply power to the module.The module receives power from the drive.Apply power to the drive. The statusindicators should be green. If they flash red,there is a problem. Refer to chapter 8,

Troubleshooting the ControlNet Module andthe Network.

Chapter 3,Installing theControlNetModule

5 Configure the module for yourapplication.Set the parameters for the following featuresas required by your application:

I/O configuration.

Fault actions.

Chapter 4,ConfiguringtheControlNetModule

6 Apply power to the ControlNet master andother devices on the network.Verify that the master and network areinstalled and functioning in accordance withControlNet standards, and then apply powerto them.

7 Configure the scanner to communicatewith the module.Use a network tool for ControlNet toconfigure the master on the network.

Chapter 5,RSNetWorxConfigurationfor PLC-5CApplications


14/160


8 Create a ladder logic program.Use a programming tool to create a ladderlogic program that enables you to do thefollowing:

Control the module and connected drive.

Monitor or configure the drive using ExplicitMessages.

Chapter 6,PLC-5CApplications

Step Action Refer to


15/160

Installing the ControlNet Module 3-1

CHAPTER3Installing the

ControlNet Module

Chapter 3 provides instructions for installing the module on anSP600 drive.

3.1 Preparing for an Installation

Before installing the ControlNet module, verify that you have allrequirement equipment. Refer to chapter 2, Getting Started, for alist of equipment.

3.2 Commissioning the Module

To commission the module, you must set a unique node address onthe network. (Refer to the Glossary for details about nodeaddresses.)

Important: New settings are recognized only when power isapplied to the module or it is reset. If you change asetting, cycle power or reset the module.

Important: To guard against device malfunction, you must wear agrounding wrist strap when installing the ControlNetmodule.

Step 1. Set the ControlNet modules node address by rotating thenode address switches to the desired value for each digitas shown in figure 3.1.

Important: Each node on the ControlNet network must have aunique address.

!

ATTENTION: The ControlNet module contains ESD-(Electrostatic Discharge) sensitive parts that can bedamaged if you do not follow ESD controlprocedures. Static control precautions are requiredwhen handling the module. Failure to observe theseprecautions could result in damage to equipment.


16/160


Important: The node address must be set before power is appliedbecause the module uses the node address it detectswhen it first receives power. To change a nodeaddress, you must set the new value and then removeand reapply power to or reset the module.

3.3 Connecting the Module to the DriveStep 1. Remove power from the drive.

Step 2. Use static control precautions.

Step 3. Connect the Internal Interface cable to the DPI port on thedrive and then to the DPI connector on the module. See

figure 3.2.

Setting Description

0 to 99 Node address used by the module if switches are enabled.The default switch setting is 02.

Important: If the address switch is set to 00, the modulewill use the setting of CN Addr Cfg (03) for the nodeaddress. Refer to chapter 4, Configuring the ControlNetModule, for more information.

Figure 3.1 Setting the Modules Node Address

2

1

0

9

8

3

4

5

6

7

2

1

0

9

8

3

4

5

6

7

TensDigit

OnesDigit


17/160


18/160


Important: All screws must be tightened since the module isgrounded through a screw.

Figure 3.3 Mounting the Module

Adapter

Drive

SP600 1-20 HP Drive

Internal Interface CableFolded Behind the Moduleand in Front of the Drive

Module

SP600 Drive25-40 HP @ 460 V


19/160

Installing the ControlNet Module 3-5

3.4 Connecting the Module to theNetwork

Step 1. Remove power from the drive.

Step 2. Use static control precautions.

Step 3. Route the ControlNet cable through the bottom of theSP600 drive. (See figure 3.3.)

Step 4. Connect the ControlNet cable to the module.A 1786-TPS (straight tap) is recommended.

See figure 3.4 for typical ControlNet network wiring.

!

ATTENTION: The SP600 drive may contain highvoltages that can cause injury or death. Removepower from the drive, and then verify power hasbeen discharged before installing or removing a

module. Failure to observe this precaution couldresult in severe bodily injury or loss of life.

Figure 3.4 Typical ControlNet Network Wiring

Scanner SP600 Drive SP600 Drive


20/160


3.5 Applying Power

Step 1. Close the door or reinstall the cover on the drive. Thestatus indicators can be viewed on the front of the driveafter power has been applied.

Step 2. Apply power to the drive. The module receives its powerfrom the connected drive. When you apply power to theproduct for the first time, the status indicators should begreen or off after an initialization. If the status indicatorsare red, refer to chapter 8.

Step 3. Apply power to the master device and other devices onthe network.

!

ATTENTION: Unpredictable operation may occurif parameter settings and switch settings are notcompatible with your application. Verify thatsettings are compatible with your applicationbefore applying power to the drive. Failure toobserve these precations could result in severebodily injury of loss of life.


21/160

Configuring the ControlNet Module 4-1

CHAPTER4Configuring the

ControlNet Module

Chapter 4 provides instructions and information for setting theparameters in the module.

For a complete list of parameters, refer to Appendix B, ControlNetModule Parameters. For definitions of terms in this chapter, refer tothe Glossary.

4.1 Configuration Tools

The ControlNet module stores parameters and other information inits own non-volatile memory. Therefore, you must access themodule to view and edit its parameters. Table 4.1 lists the tools that

can be used to access the module parameters.

Table 4.1 Configuration Tools

Tool Refer to:

VS Utilities Software VS Utilities online help

LCD OIM Section 4.2


22/160


23/160


4.4 Setting the I/O Configuration

The I/O configuration determines the type of data sent to the drive.This is a two-part process: enabling/disabling the data transmittedbetweeen the module and the drive, and identifying the datatransmitted between the module and the scanner.

Step 1. Enable or disable the data transmitted between themodule and the drive by setting the bits in DPI I/O Config(13). A 1enables the I/O. A 0disables the I/O.

Bit 0 is the right-most bit. In figure 4.3, it is highlighted and equals1.

Step 2. If Logic Command/Reference is enabled (default),configure the parameters in the drive to accept the LogicCommand and Reference from the module. For example,set Speed Ref A Sel (90) in an SP600 drive to Networkso that the drive uses the Reference from the module.Also, verify that Logic Source Sel (89) is configured toreceive the desired logic from the module.

Step 3. If you enabled one or more Datalinks (optional), configureparameters in the drive to determine the source anddestination of data in the Datalink(s). Also, ensure that theControlNet module is the only module using the enabledDatalink(s).

Step 4. Reset the module. Refer to section 4.7.3, Resetting theModule.

The module is ready to receive I/O from the master (i.e., scanner).You must now configure the scanner to recognize and transmit I/Oto the module. Refer to chapter 5, RSNetWorx Configuration forPLC-5C Applications, for more information.

Figure 4.3 I/O Configuration Screen on an LCD OIM

Port 5 Device

RECOMM-CNET

Parameter #: 13DPI I/O Configx x x x x x x x x x x 0 0 0 0 1Cmd/Ref b00

Bit Description

0 Logic Command/Reference (Default)

1 Datalink A

2 Datalink B

3 Datalink C

4 Datalink D

5 - 15 Not Used


24/160


4.5 Selecting Master-Slave

A hierarchy determines the type of device with which the moduleexchanges data. In a Master-Slave hierarchy, a module exchangesdata with a scanner.

To set a Master-Slave hierarchy

Step 1. Enable the desired I/O in DPI I/O Config (13). Refer tofigure 4.3.

Step 2. Set the bits in the M-S Input (25). This parameter

determines the data transmitted from the scanner to thedrive. A 1enables the I/O. A 0disables the I/O.


Step 3. Set the bits in the M-S Output (26). This parameterdetermines the data transmitted from the drive to thescanner. A 1enables the I/O. A 0disables the I/O.


Step 4. Reset the module. Refer section 4.7.3 for this procedure.

Figure 4.4 Master-Slave Input Screen on an LCD OIM

Figure 4.5 Master-Slave Input Screen on an LCD OIM

Bit Description

0 Logic Command/Reference (Default)

1 Datalink A Input

2 Datalink B Input

3 Datalink C Input

4 Datalink D Input

5 - 15 Not Used

Port 5 Device

RECOMM-CNET

Parameter #: 25M-S Inputx x x x x x x x x x x 0 0 0 0 1Cmd/Ref b00

Bit Description

0 Status/Feedback (Default)

1 Datalink A Output

2 Datalink B Output

3 Datalink C Output

4 Datalink D Output

5 - 15 Not Used

Port 5 Device

RECOMM-CNET

Parameter #: 26M-S Outputx x x x x x x x x x x 0 0 0 0 1Status/Fdbk b00


25/160


The module is ready to receive I/O from the master (i.e., scanner).You must now configure the scanner to recognize and transmit I/Oto the module. Refer to chapter 5, RSNetWorx Configuration forPLC-5C Applications.

4.6 Selecting Reference Adjust

Reference Adjust is the percent scaling factor for the Referencefrom the Network and can be set from 0-200%. This allows thedrives Reference to either match the network Reference (=100%),scale below the network Reference (100%).

4.7 Setting a Fault Action

By default, when communications are disrupted (for example, acable is disconnected) or the master is idle, the drive responds byfaulting if it is using I/O from the network.

You can configure a different response to communicationdisruptions using Comm Flt Action (10) and a different response toan idle scanner using Idle Flt Action (11).

!

ATTENTION: Comm Flt Action (10) and Idle FltAction (11)let you determine the action of the moduleand connected Host product if the controller is idle(for example, in program mode). These parameterscan be used to fault the Host product (default) orperform another function such as allow the Host tocontinue to run. Some ControlNet scanners mayoperate differently when a controller is idle, whichcould limit the Idle Fault Actions operating states.The Idle Flt Action should be verified whencommissioning the drive on the network by testingthe operation with the controller in idle.


26/160


27/160


4.7.2 Setting the Fault Configuration Parameters

If you set Comm Flt Action (10) or Idle Flt Action (11) to Send FltCfg,the values in the parameters shown in table 4.3 are sent to thedrive after a communications fault and/or idle fault occurs. You mustset these parameters to values required by your application.

Changes to these parameters take effect immediately. A reset is notrequired.

4.7.3 Resetting the Module

Changes to switch settings or some module parameters require thatyou reset the module before the new settings take effect. You canreset the module by cycling power to the drive or by using ResetModule (9).

Table 4.3 Fault Configuration Parameters

Parameter

Number Name Description

15 Flt Cfg Logic A 16-bit value sent to the drivefor Logic Command.

16 Flt Cfg Ref A 32-bit value (0 to 4294967295)sent to the drive as a Referenceor Datalink.

Important: If the drive uses a16-bit Reference or 16-bitDatalinks, the most significantword of the value must be set tozero (0) or a fault will occur.

17 - 24 Flt Cfg x1 InFlt Cfg x2 In

!

ATTENTION: If the module is transmitting controlI/O to the drive, the drive may fault when you resetthe module. Determine how your drive will respondbefore resetting a connected module. Failure toobserve this precaution could result in bodily injuryor damage to equipment.


28/160


Set Reset Module (9) to Reset Module. See figure 4.7.

When you enter 1 (Reset Module), the module will be immediatelyreset. When you enter 2 (Set Defaults), the module will set allmodule parameters to their factory-default settings. The value of thisparameter will be restored to 0 (Ready)after the module is reset orresetting the defaults. The module should be reset after performinga Set Defaults.

4.8 Viewing the Module Configuration

The parameters in table 4.4 provide information about how themodule is configured. You can view these parameters at any time.

Figure 4.7 Reset Screen on an LCD OIM

Port 5 Device

RECOMM-CNET

Parameter #: 9Reset Module

1Reset Module

Value Description

0 Ready (Default)

1 Reset Module

2 Set Defaults

Table 4.4 Module Configuration Status Parameters

No. Name and Description Details

01 DPI PortPort to which the module is connected. This willusually be port 5.

Default: 5Minimum: 0Maximum: 7Type: Read Only

02 DPI Data RateData rate used by the drive. This data rate is set inthe drive and the module detects it.

Default: 0 = 125 KValues 0 = 125 K 1 = 500 KType: Read Only

04 CN Addr ActThe actual network node address.

Default: 2Minimum: 1Maximum: 99Type: Read Only

06 CN Rate ActThe actual network data rate. Default: 0 = 5 MbpsValues: 0 = 5 MbpsType: Read Only

07 Ref/Fdbk SizeSize of the Reference/Feedback. The drivedetermines the size of the Reference/Feedback.

Default: 0 = 16-bitValues: 0 = 16-bit

1 = 32-bitType: Read Only

08 Datalink SizeSize of each Datalink word. The drive determinesthe size of Datalinks.

Default: 0 = 16-bitValues: 0 = 16-bit

1 = 32-bitType: Read Only


29/160


14 DPI I/O ActiveI/O that the module is actively transmitting. Thevalue of this parameter will usually be equal to thevalue of parameter 13 - DPI I/O Config.

Default: xxx0 0001Bit Values: 0 = I/O disabled

1 = I/O enabledType: Read Only

Bit Definitions0 = Cmd/Ref1 = Datalink A2 = Datalink B3 = Datalink C4 = Datalink D

5 = Not Used6 = Not Used7 = Not Used

25 M-S InputConfigures the I/O Data to be transferred from thenetwork to the drive.

Default: xxx0 0001Bit Values: 0 = I/O disabled

1 = I/O enabledType: Read/WriteReset Required: Yes

Bit Definitions0 = Cmd/Ref1 = Datalink A2 = Datalink B3 = Datalink C4 = Datalink D5 = Not Used6 = Not Used7 = Not Used

26 M-S Output

Configures the I/O Data to be transferred from thedrive to the network.

Default: xxx0 0001

Bit Values: 0 = I/O disabled1 = I/O enabledType: Read/WriteReset Required: Yes

Bit Definitions0 = Cmd/Ref1 = Datalink A2 = Datalink B3 = Datalink C4 = Datalink D5 = Not Used6 = Not Used7 = Not Used

27 Ref AdjustPercent scale factor for the Reference from theNetwork.

Default: 100.00Minimum: 0.00Maximum: 200.00Type: Read/WriteReset Required: No

Table 4.4 Module Configuration Status Parameters

No. Name and Description Details

BitDefault 10000x xx

0123457 6


0123457 6


0123457 6


30/160



31/160

RSNetWorx Configuration for PLC-5C Applications 5-1

CHAPTER5RSNetWorx Configuration

for PLC-5C Applications

This chapter provides information for using RSNetWorx forControlNet to configure a PLC-5C controller to communicate withthe RECOMM-CNET ControlNet module.

RSNetWorx for ControlNet is a 32-bit Windows application forconfiguring ControlNet networks. After installing and configuring themodule, RSNetWorx is used to configure the controller to recognizeand communicate with the module.

Before configuring the controller, your PC must be:

Connected to the ControlNet network using a 1784-PCC,1770-KFC, or similar device.

Running RSNetWorx with RSLinx communications.

5.1 Configuring a ControlNet Network:An Example

In this example, we will be configuring two SP600 drives to beNode 2 and Node 3 on a ControlNet network. This chapterdescribes the steps to configure a simple network as shown infigure 5.1.

Figure 5.1 Sample ControlNet Network

SP600 DriveNode 2

SP600 DriveNode 3

Scanner


32/160


5.1.1 Installing and Registering EDS Files inRSNetWorx

This section needs to be performed only if new EDS (ElectronicData Sheet) files need to be added to RSNetWorx. The latest EDSfiles can be obtained at:http://www.reliance.com/prodserv/standriv/networks.

In the Tools menu, select EDS Wizard and click Next (figure 5.2).

Step 1. The EDS Wizard can be used to install (register) newEDS files to the RSNetWorx database, remove(unregister) EDS files from the RSNetWorx database, andchange the graphic icon used to represent the device.Select Register an EDS file(s) and click Next (figure5.3).

Figure 5.2 Rockwell Software EDS Wizard


33/160


Step 2. The EDS Wizard allows for registering single or multipleEDS files. Click Browse and locate where your EDS filesare located. In our example (figure 5.4), multiple EDS files

are registered from a directory on the hard drive.

Figure 5.3 EDS Wizard Option Screen

Figure 5.4 EDS Wizard Designation Screen


34/160


35/160


Step 4. The graphic images for each EDS file are displayed andcan be changed if desired. Click Next to continue (figure5.6).

Figure 5.6 EDS Wizard Change Graphic Image Screen

SP600


36/160


Step 5. Click Next to register the EDS files (figure 5.7).

Step 6. The EDS files have been installed and registered. ClickFinish to return to the main RSNetWorx screen (figure5.8).

Figure 5.7 EDS Wizard Final Task Summary Screen

You would like to register the following device:

SP600

Figure 5.8 EDS Wizard Completion Screen


37/160


Step 7. Click on the DPI to ControlNetfolder in the Hardwarewindow to view the EDS files that have been installed tothe RSNetWorx database (figure 5.9).

5.1.2 Configuring a Network with RSNetWorx

The main screen for RSNetWorx consists of several windows:

The Network Usage View displays current and pending valuesassociated with the ControlNet network configuration.

A Hardware View displays a list of all network hardware currentlyavailable to RSNetWorx software.

The Favorites View displays a list of hardware that is frequentlyused when working with the current RSNetWorx configuration.

The Graph View shows a pictorial representation of all thehardware used in the current RSNetWorx configuration.

The Message View displays a log of messages which are listedfrom top to bottom, newest to oldest. This view may containinformational, warning, and/or error messages.

Figure 5.9 RSNetWorx for ControlNet DPI to ControlNet Folder Example

SP600


38/160


The various views can be displayed or closed by using the Viewmenu. In figure 5.10,the Network Usage, Hardware and Graphicviews are displayed while the Message and Favorites views areclosed.

Step 1. Click the on-line icon to browse the network.

Step 2. Select the ControlNet network access method and clickOK. In this example, RSNetWorx will use the 1784-PCCto access the ControlNet network (figure 5.11).

Figure 5.10 RSNetWorx for ControlNet Screen


39/160


.

RSNetWorx starts browsing the ControlNet network for nodes andbuilds the graphic representation of the network (figure 5.12).

Figure 5.11 Sample Browse for Network Dialog Box

Figure 5.12 Sample Network Displayed in RSNetWorx


40/160


Step 3. When the network browse is complete, a graphical view ofthe network is displayed. In this example (figure 5.13), theControlNet network consists of a PLC-5C/40C controller,two SP600 drives, and a PC using a 1784-PCC.

The symbol indicates the device shown on thenetwork does not exist in the configuration file, but it wasfound on the network. Double-click on the PLC-5C/40Cicon.

Step 4. The ControlNet configuration box displays informationabout each node (figure 5.14). Click OK.

Figure 5.13 Sample ControlNet Configuration Screen

SP600 SP600


41/160


42/160


Step 6. If the On-line / Off-line Mismatch dialog box appears, clickOK to use the on-line data (figure 5.16). If prompted tosave, save the data (figure 5.17).

Important: During the save process, RSNetWorx will execute thebrowse function. Allow RSNetWorx to complete thebrowse (1-99 nodes), even if you already see the entirenetwork. Canceling the browse early may cause animproper scheduling of I/O.

Step 7. Right-click on the controllers icon (PLC-5C) and select

SCANlist Configuration. The Scanlist Configurationscreen (figure 5.18), is used to configure the controller tocommunicate with the nodes.

Figure 5.16 Online / Offline Mismatch Dialog Box

Figure 5.17 Save Data Screen

RECOMM-CNET Example.XC


43/160


..

Step 8. Enter the Integer files to be used for ControlNetcommunications (figure 5.19). In this example, N9 is theData Input File, N10 is the Data Output File, N11 is theStatus File, and N13 is the Configuration File. Double-click the Node 2 row (SP600 drive).

Figure 5.18 Scanlist Configuration Screen

SP600

SP600


44/160


Step 9. Enter the input and output size for the node on the

network. The number of words selected depends on theI/O to be communicated with the node. In this example,the Node 2 SP600 is set for all I/O enabled which equatesto 10 words of I/O (table 5.1).

Important: The size of the Reference (Ref/Fdbk Size (7)) andDatalinks (Datalink Size (8)) will affect the size youconfigure for the network I/O. For example, 32-bitDatalinks requires twice as many words as 16-bitDatalinks. Depending on your application, theconfigured I/O size may vary.

Figure 5.19 Integer Files for ControlNet Communications Screen

Table 5.1 Input/Output Table

Words Input to PLC-5C Output to PLC-5C

0-1 Logic Command /Reference

Logic Status /Feedback

2-3 Datalinks A1 & A2 Out Datalinks A1 & A2 In

4-5 Datalinks B1 & B2 Out Datalinks B1 & B2 In

6-7 Datalinks C1 & C2 Out Datalinks C1 & C2 In

8-9 Datalinks D1 & D2 Out Datalinks D1 & D2 In

SP600

SP600


45/160


Note the values in the Input Address and Output Address fields.These are needed to develop a ladder program.

Step 10. Enter the desired Requested Packet Interval (RPI) andnote the value (figure 5.20). Ensure that this value isequal to or greater than the value that will be set later forNetwork Update Time (NUT). The Actual Packet Interval(API) may vary from the Requested Packet Interval.

Step 11. Click the Electronic Keying tab. Electronic Keying isused to determine the criteria used for the scanner toestablish a connection to a node. Select the settingsaccording to your application needs (figure 5.21).

Figure 5.20 Communicaiton Properties

SP600


46/160


Step 12. Click the Details(figure 5.22)tab. The availability ofchoosing connection options are determined by the EDS

file for the node. Click OK.

Figure 5.21 Connection Properties: Electronic Keying Settings

Figure 5.22 Connection Properties: Details Settings


47/160


Step 13. Repeat steps 9-12 for additional nodes. When complete,all of the nodes should be mapped (figure 5.23).

Step 14. Click File/ Save to save the project (figure 5.24). Ifprompted to optimize and re-write schedule for allconnections, click OK.

Figure 5.23 ScanList Configuration: Mapped Nodes

Figure 5.24 Save Configuration Dialog Box

SP600

SP600


48/160


49/160


50/160


Step 17. If desired, select the General tab and enter a name anddescription for the network (figure 5.28). Click OK.

Step 18. In the Network menu, select Save the properties anddownload them to the PLC. The module(s) are nowmapped on the network and the controller willcommunicate with it.

Figure 5.28 ControlNet: General Tab

RECOMM-CNET ControlNet demonstrationprogram using two SP600 demo units.


51/160


52/160


53/160

PLC-5C Applications 6-3

An image that uses 32-bit words for Reference and Datalinks A andD would change the I/O image in figure 6.1 as follows:

Figure 6.1 Sample I/O Image with All I/O Enabled

Controller Scanner Module SP600 DriveControlNet DPI

Output

Image

(Write)

MessageHandler

Input

Image

(Read)

0 Logic Status

1 Feedback

2 Datalink Out A1

3 Datalink Out A2

4 Datalink Out B1

5 Datalink Out B2

6 Datalink Out C1

7 Datalink Out C28 Datalink Out D1

9 Datalink Out D2

0 Logic Command

1 Reference

2 Datalink In A1

3 Datalink In A2

4 Datalink In B1

5 Datalink In B2

6 Datalink In C17 Datalink In C2

8 Datalink In D1

9 Datalink In D2

Logic Status

Feedback

Data Out A1

Data Out A2

Data Out B1

Data Out B2

Data Out C1

Data Out C2Data Out D1

Data Out D2

Word and I/O

MessageHandler

MessageHandler

Message

Buffer

Message

Buffer

MessageHandler

Logic Command

Reference

Data In A1

Data In A2

Data In B1

Data In B2

Data In C1Data In C2

Data In D1

Data In D2

Word I/O Word I/O

0 Logic Command/Status 8 - 11 Datalink B1/B21 Pad Word 12 - 15 Datalink C1/C2

2 - 3 Reference/Feedback 16 - 19 Datalink D1/D2

4 - 7 Datalink A1/A2


54/160


Figure 6.2 illustrates an example of an I/O image that does not useall of the I/O data. Only the Logic Command/Reference andDatalink B are enabled. In this example, the Reference is a 32-bitword, and Datalinks are 16-bit words.

6.3 Using Logic Command/Status

When enabled, the Logic Command/Status word is always word 0 inthe I/O image. The Logic Commandis a 16-bit word of controlproduced by the scanner and consumed by the module. The LogicStatusis a 16-bit word of status produced by the module andconsumed by the scanner.

This manual contains the bit definitions for compatible productsavailable at the time of publication in Appendix D, Logic Command/Status Words. For other products, refer to their documentation.

Figure 6.2 Sample I/O Image with Only Logic/Reference and Datalink BEnabled

Controller Scanner Module SP600 Drive

ControlNet DPI

Output

Image

(Write)

Input

Image

(Read)

0 Logic Status1 Pad Word

2 Feedback (LSW)

3 Feedback (MSW)

4 Datalink Out B1

5 Datalink Out B2

0 Logic Command

1 Pad Word

2 Reference (LSW)

3 Reference (MSW)

4 Datalink In B1

5 Datalink In B2

Word and I/OLogic Command

Reference

Data In A1

Data In A2

Data In B1

Data In B2

Data In C1

Data In C2

Data In D1

Data In D2

Logic Status

Feedback

Data Out A1

Data Out A2

Data Out B1

Data Out B2

Data Out C1

Data Out C2

Data Out D1

Data Out D2

LSW = Least Signicant Word (Bits 15 - 0)MSW = Most Significant Word (Bits 31 - 16)


55/160


6.4 Using Reference/Feedback

The Reference(16 bits or 32 bits) is produced by the controller andconsumed by the module. The Feedback(16 bits or 32 bits) isproduced by the module and consumed by the controller. The sizeof the Reference/Feedback is determined by the drive and displayedin Ref/Fdbk Size (07) in the module.

6.5 Using Datalinks

A Datalink is a mechanism used by SP600 drives to transfer data toand from the controller. Datalinks allow a parameter value to bechanged without using an Explicit Message.

When enabled, each Datalink consumes either two 16-bit or 32-bitwords in both the input and output image depending on its size. Thesize of Datalinks (16-bit words or 32-bit words) is determined by thedrive and displayed in Datalink Size (08) in the module.

6.5.1 Rules for Using Datalinks

Each set of Datalink parameters in an SP600 drive can be usedby only one module. If more than one module is connected to asingle drive, multiple modules must not try to use the sameDatalink.

Parameter settings in the drive determine the data passedthrough the Datalink mechanism. Refer to the documentation foryour drive.

When you use a Datalink to change a value, the value is notwritten to the Non-Volatile Storage (NVS). The value is stored involatile memory and lost when the drive loses power.

Size Valid Values In I/O Image Example

16-bit -32768 to 32767 Word 1 Figure 6.1

32-bi t -2147483648 to 2147483647 Word 2 and Word 3 Figure 6.2


56/160


6.5.2 32-Bit Parameters using 16-Bit Datalinks

To read (and/or write) a 32-bit parameter using 16-bit Datalinks,typically both Datalinks (x1 and x2) are set to the 32-bit parameter.

For example, to read Elapsed MWh (9)in an SP600 drive, bothDatalink A1 and A2 are set to 9.Datalink A1 will contain the leastsignificant word (LSW) and Datalink A2 the most significant word(MSW). In this example, the parameter 9 value of 5.8 MWh is readas a 58in Datalink A1.

Regardless of the Datalink combination, x1 will always contain theLSW and x2 will always contain the MSW. In the following examplesPower Up Marker (242) contains a value of 88.4541 hours.

32-bit data is stored in binary as follows:

Example:

Power Up Marker (242) = 88.4541 hours

MSW = 13decimal= 1101binary= 219+ 218+ 216= 851968

LSW = 32573

851968 + 32573 = 884541

DatalinkMost/Least

Significant Word ParameterData

(decimal)

A1 LSW 9 58

A2 MSW 9 0

Datalink

Most/Least

Significant Word Parameter

Data

(decimal)

A1 LSW 242 32573

A2 - Not Used - 0 0

Datalink

Most/Least


Data

(decimal)

A1 - Not Used - 0 0

A2 MSW 242 13

Datalink

Most/Least


Data

(decimal)

A2 MSW 242 13

B1 LSW 242 32573

MSW 231through 216

LSW 215through 20


57/160


6.6 Function of the Sample Program

The program performs the following actions:

Obtains Logic Status information from the drive.

Uses the Logic Command to control the drive (for example, start,stop).

Sends a Reference to the drive and receives Feedback from thedrive.

Sends/Receives Datalink data to/from the drive.

Module Settings for the Sample Program

Nodes 2 and 3.

See Chapter 5, RSNetWorx Configuration for PLC-5CApplications.

Parameter Settings for the Sample Program

Logic Command/Status Words

These examples use the Logic Command word and Logic Statusword for SP600 drives. Refer to Appendix D, Logic Command/Status Words to view these. The definition of the bits in these wordsmay vary if you are using a different DPI product. Refer to thedocumentation for your drive.

Table 6.1 Parameter Settings for the Sample Program

Device Parameter Name Value Description

SP600 Drive

90 Speed Ref A Sel 22 Network (RECOMM-CNET)

300 Data In A1 140 Points to 140 (Accel Time 1)

301 Data In A2 142 Points to 142 (Decel Time 1)302 Data In B1 100 Points to 100 (Jog Speed)

303 Data In B2 155 Points to 155 (Stop Mode A)

310 Data Out A1 140 Points to 140 (Accel Time 1)

311 Data Out A2 142 Points to 142 (Decel Time 1)

312 Data Out B1 100 Points to 100 (Jog Speed)

313 Data Out B2 155 Points to 155 (Stop Mode A)

13 DPI I/O Cfg xxx1 1111 Enables Cmd/Ref, Datalinks A-D

RECOMM-CNET

25 M-S Input xxx1 1111 Configures the I/O Data to betransferred from the network to thedrive.

26 M-S Output xxx1 1111 Configures the I/O Data to be

transferred from the drive to thenetwork.


58/160


6.7 Main Program (PLC-5C)

Figure 6.3 I/O Messaging

There is an operator station wired into the local rack as follows:I:000/0 Start (Normally Open Pushbutton)I:000/1 Stop (Normally Closed Pushbutton)I:000/2 Clear Faults (Normally Open Pushbutton)I:000/3 Forward / Reverse Selector SwitchI:001 Operator Speed Reference

O:000/0 Drive ReadyO:000/1 Drive ActiveO:000/2 Drive FaultedO:001 Operator Speed FeedbackThe 20-COMM-C on the PowerFlex 70 drive is mapped as follows:N9:0 Logic Status N10:0 Logic CommandN9:1 Feedback N10:1 ReferenceN9:2 Datalink A1 Out N10:2 Datalink A1 InN9:3 Datalink A2Out N10:3 Datalink A2 InN9:4 Datalink B1 Out N10:4 Datalink B1 InN9:5 Datalink B2 Out N10:5 Datalink B2 InN9:6 Datalink C1 Out N10:6 Datalink C1 InN9:7 Datalink C2 Out N10:7 Datalink C2 InN9:8 Datalink D1 Out N10:8 Datalink D1 InN9:9 Datalink D2 Out N10:9 Datalink D2 In

0000I:000

0

Operator

StartPushbutton

N10:0

1

Drive

Logic CommandSTART

0001I:000

1

OperatorStopPushbutton

N10:0

0

DriveLogic CommandSTOP

The RECOMM-CNET on the SP600 drive is mapped as follows:


59/160


Figure 6.4 I/O Messaging (Continued)

002I:000

2

OperatorClear FaultsPushbutton

N10:0

3

DriveLogic CommandCLEAR FAULTS

003I:000

3

OperatorFwd / RevSelector Switch

N10:0

4

DriveLogic CommandFORWARD

004I:000

3

OperatorFwd / RevSelector Switch

N10:0

5

DriveLogic CommandREVERSE

005N9:0

0

DriveREADYStatusBit

O:000

0

OperatorDrive ReadyStatusDisplay

006N9:0

1

DriveACTIVE

StatusBit

O:000

1

OperatorDrive Active

StatusDisplay


60/160



007N9:0

7

DriveFAULTEDStatusBit

O:000

2

OperatorDrive FaultedStatusDisplay

This rung moves the Speed Reference from the operator station to thedrive.

008

MOV

MoveSource I:001 0>.

Step 13. The configured node (SP600_02in this example) nowappears under the 1756-CNB module in the I/OConfiguration folder.

Step 14. Repeat the previous steps for each additional node youneed to configure.

Figure 7.13 Module Properties: My ControlNet

Figure 7.14 RSLogix: Configure Additional Nodes Screen

RSLogix 5000 - Example_RECOMM-CNET [1756-L1]

SP600_02

Controller Example_RECOMM-CNET


79/160

ControlLogix Applications 7-11

Step 15. In the Data Types folder, click on the Module-Definedsub-folder. When you create a module, module-defineddata types and tags are automatically created. These tagsallow you to access the Input and Output Data of themodule via the controllers ladder logic.

Step 16. Select Communications / Downloadto download theconfiguration to the controller (figure 7.16). RSLogixautomatically enters on-line mode when complete.

Figure 7.15 RSLogix 5000: Module-Defined Screen



RE:

RE:

RE:

SP600_02

Figure 7.16 Download to the Controller Dialong Box

Example_RECOMM-CNET


80/160


Step 17. An Attention symbol is located next to the Node 2(SP600_02) icon in figure 7.17, which indicates theControlNet scanner needs to be configured.

Step 18. Start RSNetWorx and perform the following:

a. Click the On-line icon and browse the network.

b. Select Edits Enabled and view the messages in the

Message View for completion (figure 7.18). Theicon should disappear from the nodes in the GraphicalView.

c. Select File / Saveand save the project (figure 7.19).

d. Close RSNetworx.

This schedules the I/O that was configured in

RLSLogix 5000.

Figure 7.17 RSLogix: Attention Symbol


Controller Example - RECOMM-CNET

SP600_02

RE:

RE:

RE:


81/160


82/160


Figure 7.19 RSLogix 5000: Example Without Attention Symbol

SP600


83/160


Step 19. The Attention symbol on the RSLogix 5000 connectiontree will disappear if the network has been configuredproperly (figure 7.20). You are now ready to develop yourladder logic program.

7.2 Function of the Sample Program

The program performs the following actions:

Obtains Logic Status information from the drive.

Uses the Logic Command to control the drive (for example, start,stop).

Sends a Reference to the drive and receives Feedback from thedrive.

Sends/Receives Datalink data to/from the drive.

Module Settings For Use With the Example

Nodes 2 and 3.

Figure 7.20 RSLogix 5000: Connection Tree Without Attention Symbol



SP600

RE:

RE:RE:


84/160


Parameter Settings for the Sample Program

Logic Command/Status Words

These examples use the Logic Command word and Logic Statusword for SP600 dr ives. Refer to Appendix D, Logic Command/Status Words to view these. The definition of the bits in these wordsmay vary if you are using a different DPI product. Refer to thedocumentation for your drive.

Table 7.1 Parameter Settings for the Sample Program

Device Parameter Name Value Description

SP600 Drive

90 Speed Ref A Sel 22 Network(RECOMM-CNET)

300 Data In A1 140 Points to 140 (Accel Time 1)

301 Data In A2 142 Points to 142 (Decel Time 1)

302 Data In B1 100 Points to 100 (Jog Speed)

303 Data In B2 155 Points to 155 (Stop Mode A)

310 Data Out A1 140 Points to 140 (Accel Time 1)

311 Data Out A2 142 Points to 142 (Decel Time 1)

312 Data Out B1 100 Points to 100 (Jog Speed)

313 Data Out B2 155 Points to 155 (Stop Mode A)

13 DPI I/O Cfg xxx1 1111 Enables Cmd/Ref, Datalinks A-D

RECOMM-CNET

25 M-S Input xxx1 1111 Configures the I/O Data to betransferred from the network to thedrive.

26 M-S Output xxx1 1111 Configures the I/O Data to betransferred from the drive to thenetwork.


85/160


7.3 RSLogix 5000 Ladder Logic Program

Figure 7.21 I/O Messaging

This rung determines whether the drive is running, and sets the DriveStatusRunning tag appropriately.

DriveInputImage.Data[2].1

DriveStatusRunning

This rung determines whether the drive is running, and sets the DriveStatusRunning tag appropriately.

This rung determines whether the drive is faulted, and sets the DriveStatusFaulted tag appropriately.

DriveInputImage.Data[2].7

DriveStatusFaulted

This rung determines whether the drive is faulted, and sets the DriveStatusFaulted tag appropriately.

This rung moves the drive's frequency feedback to the DriveFeedback tag.

Copy FileSource DriveInputImage.Data[3]

Dest DriveFeedbackLength 1

COP

This rung moves the drive's frequency feedback to the DriveFeedback tag.

When the DriveCommandStart tag is true, this rung sends a start command to the drive.

DriveCommandStart

DriveOutputImage.Data[0].1

When the DriveCommandStart tag is true, this rung sends a start command to the drive.

When the DriveCommandNotStop tag is false, this rung sends a stop command to the dri ve. This rung uses anXIO input instruction because Stop pushbuttons are usually normally closed so that the equipment stops if a wirebreaks.

/DriveCommandNotStop


When the DriveCommandNotStop tag is false, this rung sends a stop command to the dri ve. This rung uses anXIO input instruction because Stop pushbuttons are usually normally closed so that the equipment stops if a wirebreaks.

When the DriveCommandJog tag is true, this rung sends a jog command to the drive.

DriveCommandJog


When the DriveCommandJog tag is true, this rung sends a jog command to the drive.

When the DriveCommandClearFault tag is true, this rung sends a clear fault command to the drive.

DriveCommandClearFault


When the DriveCommandClearFault tag is true, this rung sends a clear fault command to the drive.


86/160



This rung moves data from the DriveReference tag to the drive where it is used as a frequency reference.

7 Copy FileSource DriveReferenceDest DriveOutputImage.Data[1]

Length 1

COP

This rung moves data from the DriveReference tag to the drive where it is used as a frequency reference.

This rung moves Datalink data from the drive.

8 Copy FileSource DriveInputImage.Data[4]

Dest ParameterDataFromDrive[0]Length 8

COP

This rung moves Datalink data from the drive.

This rung moves Datalink data to the drive.

9 Copy FileSource ParameterDataToDrive[0]Dest DriveOutput Image.Data[2]

Length 8

COP

This rung moves Datalink data to the drive.

(End)


87/160


7.4 About Explicit Messaging

Explicit Messaging is used to transfer data that does not requirecontinuous updates. With Explicit Messaging, you can configureand monitor a slave devices parameters on the ControlNet network.

7.4.1 Performing Explicit Messages

Important: There are five basic events in the Explicit Messaging

process defined below. The details of each step willvary depending on the controller. Refer to thedocumentation for your controller.

Important:The scanner module may be integrated with thecontroller (e.g., PLC-5C).

Retrieve ParameterMessage Response

Complete ParameterMessage

Set up and sendParameter Message

Format the required data and set up the ladderlogic program to send an Explicit Messagerequest to the scanner module (download).

The scanner module transmits the ExplicitMessage Request to the slave device over theControlNet network.

The slave device transmits the Explicit MessageResponse back to the master.

The controller retrieves the Explicit MessageResponse.

The Explicit Message is complete.

Figure 7.23 Explicit Message Process


88/160


7.4.2 Explicit Messaging Examples

A Get_Attributes_Scattered message allows for reading multipleparameters that may or may not be in sequential order (figure 7.25).

A Service Code of 4Bindicates the Get_Attributes_Scatteredservice (see page C-20, Object Specific Services).

A Class Number of 93indicates accessing the DPI ParameterObject (see page C-16, DPI Parameter Object).

An Instance Number of 0is the Class Attributes for the drive(see page C-16, Instances).

The Source identifies the service data with the request messageto send.

The Destination contains the response message to the request.

Figure 7.24 Explicit Messaging

This rung sends a CIP message to the PowerFlex 70 drive at ControlNet address 2. The data sent is obtainedfrom the MessageSendData tag. The data received is stored in the MessageReplyData tag. This MSG instructioncan be configured to send any CIP message.

0 EnableDriveMessage

ENDNER

Type - CIP GenericMessage Control DriveMessageControl ...

MSG

This rung sends a CIP message to the PowerFlex 70 drive at ControlNet address 2. The data sent is obtainedfrom the MessageSendData tag. The data received is stored in the MessageReplyData tag. This MSG instructioncan be configured to send any CIP message.

(End)

This rung sends a CIP message to the SP600 drive at ControlNet Address 2. The data sent is obtained


89/160


Get Attributes Scattered sample request and response data:

(Source) Request Data

Figure 7.25 Get_Attributes_Scattered Message Screen

0 12 Parameter Number = 12

1 0 (Pad Word)

2 0 (Pad Word)


4 0 (Pad Word)

5 0 (Pad Word)


7 0 (Pad Word)

8 0 (Pad Word)


10 0 (Pad Word)11 0 (Pad Word)


90/160


(Destination) Response Data

A Set _Attributes_Scattered message is used to write multipleparameters that may or may not be in sequential order (figure 7.26).

A Service Code of 4Cindicates the Set_Attributes_Scattered

service (see page C-20, Object Specific Services).


1 3333 Value = 333.3VDC

2 0 (Pad Word)


4 0 Value = 0.0Hz

5 0 (Pad Word)


7 148 Value = 14.8Hrs

8


10 23 Value = 2.3MWh

11

Figure 7.26 Set_Attributes_Scattered Message Screen


91/160


Set_Attributes_Scattered sample request and response data:

(Source) Request Data

(Destination) Response Data

A Set_Attribute_Single message is used to write a single parameter(figure 7.27).

A Service Code of 10indicates the Set_Attribute_Single service(see page C-8, Services).

A Class Name of Findicates the Parameter Object (see pageC-6, Parameter Object).

An Instance of 45indicates the Drive Parameter 45 Attributes(see page C-6, Instances).

An Attribute of 1indicates the Parameter Value (see page C-7,Instance Attributes).

N13:0 45 Parameter Number = 45

N13:1 50 Value = 0.50HP

N13:2 0 (Pad Word)


N13:4 1740 Value = 1740RPM

N13:5 0 (Pad Word)

N13:6 43 Parameter Number = 43N13:7 600 Value = 60.0Hz

N13:8 0 (Pad Word)


N13:10 16 Value = 1.6Amps

N13:11 0 (Pad Word)


N14:1 0 (Pad Word)

N14:2 0 (Pad Word)


N14:4 0 (Pad Word)N14:5 0 (Pad Word)


N14:7 0 (Pad Word)

N14:8 0 (Pad Word)


N14:10 0 (Pad Word)

N14:11 0 (Pad Word)


92/160


.

Set_Attribute_Single example (writing SP600 Parameter 45 in figure7.27 ):

Send Data

A Get_Attribute_Single message is used to read a single parameter(figure 7.28).

A Service Code of Eindicates the Get_Attribute_Single service(see page C-8, Services).

A Class Name of Findicates the Parameter Object (see pageC-6, Parameter Object).

An Instance of 45indicates the Drive Parameter 45 Attributes(see page C-6, Instances).

An Attribute of 1indicates the Parameter Value (see page C-7,Instance Attributes).

Figure 7.27 Set_Attribute_Single Message Screen

0 50 Value = 0.50HP


93/160


Get Attributes Single example (reading S600 Parameter 45 in figure7.28):

Reply Data

Figure 7.28 Get_Attributes_Single Message Screen

0 50 Value = 0.50HP


94/160



95/160

Troubleshooting the ControlNet Module and Network 8-1

CHAPTER8Troubleshooting the

ControlNet Module

and NetworkChapter 8 contains information for troubleshooting the ControlNetmodule and the network.

8.1 Understanding the Status Indicators

The ControlNet module has four status indicators. They can beviewed on the module or through the drive cover. (See figure 8.1.)

Number

Status

Indicator Description Refer to...

DRIVE DPI Connection Status Section 8.1.1

MS Module Status Section 8.1.2

NET A ControlNet A Status Sections 8.1.3and 8.1.4

NET B ControlNet B Status Sections 8.1.3and 8.1.4

Figure 8.1 Status Indicators (Location on Drive May Vary)


96/160


8.1.1 DRIVE Status Indicator

Table 8.1 DRIVE Status Indicator: State Definitions

Status Cause Corrective Action

Off The module is notpowered or is notconnected properly tothe drive.

Securely connect the moduleto the drive using the ribboncable.

Apply power to the drive.FlashingRed

The module is notreceiving a pingmessage from thedrive.

Verify that cables aresecurely connected.

Cycle power to the drive.

SolidRed

The drive has refusedan I/O connection fromthe module.

Another DPI peripheralis using the same DPIport as the module.

Important:Cycle power to theproduct after making any of thefollowing corrections:

Verify that all DPI cables aresecurely connected and notdamaged. Replace cables ifnecessary.

Verify that the DPI Hostsupports Datalinks.

Configure the module andDPI Host to use a Datalink

that is not already beingused by another peripheral.

Orange The module isconnected to a productthat does not supportReliance Electric DPIcommunications.

Connect the module to aproduct that supportsReliance Electric DPIcommunications (forexample, SP600 drives).

FlashingGreen

The module isestablishing an I/Oconnection to the drive.

No action. Normal behavior ifno DPI I/O is enabled.

SolidGreen

The module is properlyconnected and iscommunicating with thedrive.

No action.


97/160


8.1.2 MS Status Indicator

Table 8.2 MS Status Indicator: State Definitions

Status Cause Corrective Action

Off The module is notpowered.

Securely connect the moduleto the SP600 drive using theribbon cable.

Apply power to the drive andnetwork.

FlashingRed

The module hasfailed the firmwaretest.

Cycle power to the drive.Parameter settings may havebeen changed.

Clear faults in the module.

If cycling power does notcorrect the problem, theparameter settings may havebeen corrupted. Reset defaultsand reconfigure the module.

If resetting defaults does notcorrect the problem, flash themodule with the latest firmwarerelease.

Solid

Red

The module has

failed the hardwaretest.

Cycle power to the drive.

Replace the module.

FlashingGreen

The module isoperational but is nottransferring I/O data.

Place the scanner in RUNmode.

Program the controller torecognize and transmit I/O tothe module.

Configure the module for theprogram in the controller.

Normal behavior if no DPI I/Ois enabled.

SolidGreen

The module isoperational and

transferring I/O data.

No action.


98/160


8.1.3 NET A and B Together

Table 8.3 NET A and B Together: State Definitions

Status Cause Corrective Actions

Both LEDsare off

A reset occurred orthere is no power.

Apply power to the module.

Both LEDsare steadyred

A link interfacefailed.

Check media for broken cables,loose connectors, missingterminators, etc.

Power cycle or reset themodule. If the problem persists,contact Rockwell Automationsupport.

LEDs arealternatingred/green

The module is inself-test mode.

No action required. The modulewill exit this mode when theself-test is completed.

LEDs arealternatingred/off

There is a badconfiguration.

Verify that all node addressesare unique.

Check the modulesconfiguration.

Check media for broken cables,loose connectors, missingterminators, etc.

Power cycle or reset themodule.


99/160


8.1.4 NET A and B Independently

Table 8.4 NET A and B Independently: State Definitions

Status Cause Corrective Actions

OnechannelLED issteady off

That channel isdisabled or notsupported.

Program the network forredundant media, if required.

Onechannel

LED isflashingred/green

There is an invalidlink configuration

for that channel.

Power cycle or reset themodule.

Reset the controller.

If the problem persists, contactRockwell Automation support.

OnechannelLED isflashingred/off

The channel is notreceiving networkactivity.

Check media for broken calbes,loose connectors, missingterminators, etc.

OnechannelLED isflashinggreen/off

A temporarychannel error hasoccurred, or thechannel is in listen-only mode.

Verify the controller is presenton the network and working.

One

channelLED issteadygreen

Normal operation

for that channel.

No action required.


100/160


8.2 Module Diagnostic Items

Table 8.5 lists diagnostic items that can be accessed usingVS Utilities software or the LCD OIM.

Table 8.5 Module Diagnostic Items

No. Event Description

1 Common LogicCmd

The current value of the Common LogicCommand being transmitted to the host.

2 Prod Logic Cmd The current value of the Product-Specific LogicCommand being transmitted to the host.

3 Reference The current value of the Product-SpecificReference being transmitted to the host.

4 Common Logic Sts The current value of the Common Logic Statusbeing received from the host.

5 Prod Logic Sts The current value of the Product-Specific Statusbeing received from the host.

6 Feedback The current value of the Product-SpecificFeedback being received from the host.

7 Datalink A1 In The current value of Datalink A1 beingtransmitted to the host. (Value of 0 if datalink isnot used).

8 Datalink A2 In The current value of Datalink A2 beingtransmitted to the host. (Value of 0 if datalink isnot used).

9 Datalink B1 In The current value of Datalink B1 beingtransmitted to the host. (Value of 0 if Datalink isnot used).

10 Datalink B2 In The current value of Datalink B2 beingtransmitted to the host. (Value of 0 if Datalink isnot used).

11 Datalink C1 In The current value of Datalink C1 beingtransmitted to the host. (Value of 0 if Datalink notused).

12 Datalink C2 In The current value of Datalink C2 beingtransmitted to the host. (Value of 0 if Datalink isnot used).

13 Datalink D1 In The current value of Datalink D1 being

transmitted to the host. (Value of 0 if Datalink isnot used).

14 Datalink D2 In The current value of Datalink D2 beingtransmitted to the host. (Value of 0 if Datalink isnot used).

15 Datalink A1 Out The current value of Datalink A1 being receivedfrom the host.

16 Datalink A2 Out The current value of Datalink A2 being receivedfrom the host.


101/160


17 Datalink B1 Out The current value of Datalink B1 being receivedfrom the host.

18 Datalink B2 Out The current value of Datalink B2 being receivedfrom the host.

19 Datalink C1 Out The current value of Datalink C1 being receivedfrom the host.

20 Datalink C2 Out The current value of Datalink C2 being receivedfrom the host.

21 Datalink D1 Out The current value of Datalink D1 being receivedfrom the host.

22 Datalink D2 Out The current value of Datalink D2 being receivedfrom the host.

23 DPI Rx Errors The current value of the DPI Receive errorcounter.

24 DPI Rx Err Max The maximum value (since reset) of the DPIReceive error counter.

25 DPI Tx Errors The current value of the DPI Transmit errorcounter.

26 DPI Tx Err Max The maximum value (since reset) of the DPITransmit error counter.

27 Node Address SW The current value set on the Node AddressSwitches.

28 Boot Flash Count The number of times the Boot flash segment hasbeen updated in the field.

29 App Flash Count The number of tmes the Application flashsegment has been updated in the field.

30 M-S Input Size The size of data transferred from the network tothe drive.

31 M-S Output Size The size of data transferred from the drive to thenetwork.

Table 8.5 Module Diagnostic Items (Continued)

No. Event Description


102/160


8.3 Viewing and Clearing Events

The module maintains an event queue that reports the history of itsactions. You can view the event queue using an LCD OIM orVS Utilities software.

To View and Clear Events Using an LCD OIM

Use the procedure shown in figure 8.2 to access the event queueusing the LCD OIM. Note that you must have the RECOMM-CNETmodule as the selected device to access the event queue.

Events

Many events in the event queue occur under normal operation. Ifyou encounter unexpected communications problems, the eventsmay help you or Reliance Electric personnel troubleshoot theproblem. Table 8.6 lists events that may appear in the event queue.

Figure 8.2 VIewing and Clearing Events Using an LCD OIM

Diagnostics:

Device VersionOIM Version

View Event Queue

P0: RECOMM-CNET

Stopped Auto

Main Menu

Diagnostics

EvtQ# : E# xxxxxOnline @ 500kbps

1

Clrqu

Highl ight Diagnostics icon

Highl ight i temMoni to r Lang

>>

Press F2 key toclear event queue

Table 8.6 Event Codes and Descriptions

Code Event Description

1 No Event Empty event queue entry.

2 DPI Bus Off Flt A bus-off condition was detected on DPI. Thisevent may be caused by loose or brokencables or by noise.

3 Ping Time Flt A ping message was not received on DPIwithin the specified time.

4 Port ID Flt The module is not connected to a correct porton a DPI product.

5 Port Change Flt The DPI port changed.

6 Host Sent Reset The DPI product issued this because it wasreset.

7 EEPROM Sum Flt The EEPROM in the module is corrupt.

8 Online @ 125kbps The module and DPI product arecommunicating at 125 kbps.


103/160


9 Online @ 500kbps The module and DPI product arecommunicating at 500 kbps.

10 Bad Host Flt The module was connected to an incompatibleproduct.

11 Dup. Port Flt Another peripheral with the same port numberis already in use.

12 Type 0 Login The module has logged in for type 0 control.

13 Type 0 Time Flt The module has not received a type 0 status

message within the specified time.14 DL Login The module has logged into a datalink.

15 DL Reject Flt The host rejected an attempt to log in to adatalink because the datalink is not supportedor is used by another peripheral.

16 DL Time Flt The module has not received a datalinkmessage within the specified time.

17 Reserved Not used.

18 Control Disabled The module has sent a Soft Control Disablecommand to the DPI product.

19 Control Enabled The module has sent a Soft Control Enablecommand to the DPI product.

20 Message Timeout A Client-Server message sent by theperipheral was not completed.

21 Flt Cfg Error Flt Cfg for the Reference or Data links is set toa value greater than 65535 and the drive is setfor 16-bit.

22 App CRC Flt Start-up sequence detected corruptapplication firmware.

23 App Updated Start-up sequence detected new applicationfirmware in candidate area.

24 CN Comm Flt The module detected a fault condition on theControlNet network.

25 CN Sent Reset The peripheral received a reset from thenetwork.

26 CN Close Fit An I/O connection from the network to theperipheral was closed.

27 CN Idle Flt The peripheral is receiving idlepackets fromthe network.

28 CN Open An I/O connection to the peripheral from thenetwork has been opened.

29 Net Timeout Flt An I/O connection from the network to theperipheral has timed out.

30 PCCC IO Close The device sending PCCC Control messagesto the peripheral has sent the PCCC ControlTimeout to a value of zero.




104/160


31 PCCC IO Open The per ipheral has begun receiving PCCCControl messages (the PCCC Control Timeoutwas previously set to a non-zero value).

32 PCCC IO Time Flt The peripheral has not received a PCCCControl Message for longer than the PCCCControl Timeout.

33 Watchdog T/O Flt The software watchdog detects a failure.

34 EEPROM Init Start-up sequence detected a blank EEPROM

map revision. Intended to happen in factorytest.

35 DPI Fault Clear The user cleared a fault in the Host.

36 Normal Startup Peripheral completes a normal start up.

37 Manual Reset The user reset the module.




105/160

Technical Specifications A-1

APPENDIXATechnical

Specifications

Communications

Electrical

Mechanical

Environmental

Regulatory Compliance

Network

Protocol

Data Rates

ControlNet

5M baud

Drive

Protocol

Data Rates

DPI

125 Kbps or 500 Kbps

Consumption

Drive

Network

275 mA at 5 VDC supplied through the drive

Dimensions

Height

Length

Width

16 mm (0.624 in)

103 mm (4 in)

80 mm (3.125 in)

Weight 85 g (3 oz)

Temperature

Operating

Storage

-10 to +50C (14 to 149F)

-40 to +85C (-40 to 185F)

Relative Humidity 5 to 95% non-condensing

UL 508C and CUL

CE EN61800-3


106/160

A-2 ControlNet Communications Module


107/160

ControlNet Module Parameters B-1

APPENDIXBControlNet Module

Parameters

The following information is provided for each ControlNet moduleparameter along with its description:

About Parameter Numbers

The parameters in the ControlNet module are numberedsequentially. However, depending on the configuration tool used,they may have different numbers.

Parameter Number: Unique number assigned to eachparameter.

Parameter Name: Unique name assigned to eachparameter.

Range: Predefined parameter limits orselections.

Default: Factory default setting.

Type: Read Only or Read/Write

Reset Required: Module must be reset before parametervalue is recognized.

Configuration Tool Numbering Schemes

VS Utilities

OIM

The module parameters begin with

parameter 1. For example, parameter 01

(DPI Port) is parameter 1 as indicated by

the manual. Explicit Messaging The module parameters are appended to

the list of drive parameters. For example,

with a drive with 300 parameters,

parameter 01 (DPI Port) is parameter 301.


108/160

B-2 ControlNet Communications Module

Port to which the module is connected. This will usually be port 5.

Data rate used by the drive. This data rate is set in the drive and themodule detects it.

Configures the network if the Node Address Switches are set to00.Updates CN Addr Act (4) after reset.

The actual network node address.

1 DPI Port

Range: 0 to 7

Default: 5

Type: Read Only

Reset Required: N/A

2 DPI Data RateRange: 0 = 125 Kbps

1 = 500 Kbps

Default: 0 = 125 Kbps

Type: Read Only

Reset Required: N/A

3 CN Addr Cfg

Range: 1 to 99

Default: 2

Type: Read/Write

Reset Required: Yes

4 CN Addr Actual

Range: 1 to 99

Default: 2

Type: Read Only

Reset Required: N/A


109/160


Configures the Network Data Rate. Updates CN Rate Act (6) after areset.

The actual Network Data Rate.

The size of the Reference/Feedback. The drive determines the sizeof the Reference/Feedback.

The size of each Datalink word. The drive determines the size ofDatalinks.

5 CN Rate Cfg

Range: 0 = 5 Mbps

Default: 0 = 5 Mbps

Type: Read/Write

Reset Required: Yes

6 CN Rate Act

Range: 0 = 5 Mbps

Default: 0 = 5 Mbps

Type: Read Only

Reset Required: N/A

7 Ref/Fdbk Size

Range: 0 = 16-bit1 = 32-bit

Default: 0 = 16-bit

Type: Read Only

Reset Required: N/A

8 Datalink Size

Range: 0 = 16-bit1 = 32-bit

Default: 0 = 16-bit

Type: Read Only

Reset Required: N/A


110/160


No action if set to Ready.Resets the module if set to ResetModule.Restores the module to factory default settings if set toSet Defaults.This parameter is a command. It will be reset to0 = Readyafter the command has been performed.

Sets the action that the module takes if the module detects anetwork failure. This setting is effective only if I/O that controls thedrive is transmitted though the module.

9 Reset Module

Range: 0 = Ready (No action)1 = Reset Module2 = Set Defaults (Restores module to factory-default

settings)

Default: 0 = Ready

Type: Read/Write

Reset Required: No

!

ATTENTION: If the module is transmitting I/O thatcontrols the drive, the drive may fault when you resetthe module. Determine how your drive will respondbefore resetting a connected module. Failure toobserve this precaution could result in bodily injuryor damage to equipment.

10 Comm Flt Action

Range: 0 = Fault

1 = Stop2 = Zero Data3 = Hold Last4 = Send Flt Cfg

Default: 0 = Fault

Type: Read/Write

Reset Required: No

!

ATTENTION: Comm Flt Action (10) lets youdetermine the action the module and connected

drive if communications are disrupted. By default,this parameter faults the drive. You can set thisparameter so that the drive continues to run. Takeprecautions to ensure that the setting of thisparameter does not create a hazard of injury orequipment damage. Failure to observe thisprecaution could result in bodily injury or damage toequipment.


111/160


Sets the action that the module takes if the module detects that thePLC is set to program mode. This setting is effective only if the I/Othat controls the drive is transmitted through the module.

Indicates either the Node Address Switches or CN Addr Cfg (03) inthe module are controlling the node address.

11 Idle Flt Action

Range: 0 = Fault1 = Stop2 = Zero Data3 = Hold Last4 = Send Flt Cfg

Default: 0 = Fault

Type: Read/Write

Reset Required: No

!

ATTENTION: Idle Flt Action (11) lets you determinethe action of the module and connected Host productif the controller is idle (e.g., in program mode). Thisparameter can be used to fault the Host product(default) or to perform another function such as allowthe Host to continue to run. Ensure that the settingof this parameter does not create a hazard of injuryor equipment damage. Failure to observe thisprecaution could result in bodily injury or damage toequipment.

12 CN Active Cfg

Range: 0 = Switches1 = EEPROM

Default: 0 = Switches

Type: Read Only

Reset Required: N/A


112/160


Configures the I/O that is transferred through the module.

I/O that the module is actively transmitting. The value of thisparameter will usually be equal to the value of DPI I/O Cfg (13).

13 DPI I/O Cfg

Range: See figure B.1.

Default: xxx0 0001

Type: Read/Write

Reset Required: Yes

Figure B.1 DPI I/O Config (13)

000 10xxx01234567

1= I/O Enabled0= I/O Disabledx =Not Used

Cmd/R

ef

DatalinkA

DatalinkB

Date post:	10-Feb-2018
Category:	Documents
Upload:	luis-salinas
View:	227 times
Download:	0 times

ControlNet Communications Module

Documents