Controlnet Geral

7/28/2019 Controlnet Geral

http://slidepdf.com/reader/full/controlnet-geral 1/160

Instruction Manual

ControlNetCommunications Module

M/N RECOMM-CNET

D2-3497





Contents I

CONTENTS

Chapter 1 Introduction

1.1 ControlNet Module Features.......................................... 1-11.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 Module

4.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 Applications

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



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-56.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-27.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-1

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






http://slidepdf.com/reader/full/controlnet-geral 7/160Contents 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



VI ControlNet Communications Module



Introduction 1-1

CHAPTER1Introduction

The ControlNet module (RECOMM-CNET) is an embeddedcommunication 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 the

module.

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 a

parameter.

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



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.



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

Internal Interface cable is connected to thisconnector and a connector on the drive.

Channel A BNCReceptacle

Channel “A” BNC connection for the ControlNetcable.

Channel B BNCReceptacle

Channel “B” BNC 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




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



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

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 the

Internal 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




❒ 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



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 on

the 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 module’s 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.




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. Seefigure 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 node

address. Refer to chapter 4, Configuring the ControlNetModule, for more information.

Figure 3.1 – Setting the Module’s Node Address

2

1

0

9

8

3

4

5

6

7

2

1

0

9

8

3

4

5

6

7

Tens

Digit

Ones

Digit




Step 4. For 1-20 HP SP600 drives, fold the Internal Interfacecable behind the module and mount the module on thedrive using the four captive screws. See figure 3.3.

For 25-40 HP SP600 drives, mount the module on thedrive using the four captive screws to secure and groundit to the drive.

DPI Connector

15.24 cm (6 in) Internal Interface cable

2.54 cm (1 in) Internal Interface cable

Figure 3.2 – DPI Ports and Internal Interface Cables

ControlNet ModuleSP600 Drive

1-20 HP @ 460 V

SP600 Drive25-40 HP @ 460 V




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 Module

and in Front of the Drive

Module

SP600 Drive25-40 HP @ 460 V




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 the

SP600 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 amodule. 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




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 be

green 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 application

before applying power to the drive. Failure toobserve these precations could result in severebodily injury of loss of life.



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 to

the 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 thatcan 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




4.2 Using the LCD OIM to Configure theModule

Use the procedure in figure 4.1 to access the parameters on theControlNet module using the LCD OIM. If you are unfamiliar withthe operation of the LCD OIM, refer to the SP600 AC Drive User

Manual (D2-3485) for more information.

4.3 Setting the Node Address

If the node address switches are set to “00”, the value of CN Addr

Cfg (3) determines the node address.

Step 1. Set the value of CN Addr Cfg (3) to a unique nodeaddress.

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

Figure 4.1 – Accessing the ControlNet Parameters using the LCD OIM

P0: SP600

>> AutoStopped

Main Menu

Device Select

Use to selectRECOMM-CNET.

P0: SP600

>> AutoStopped

P5: RECOMM-CNET

>> AutoStopped

Main Menu

Parameters

Device: Port 0

SP600RECOMM-CNET

Monitor Lang

Edit the ControlNetparameters using thesame techniques as fordrive parameters.

Use to highlightDevice Select icon

Figure 4.2 – ControlNet Node Address Screen on an LCD OIM

Port 5 Device

RECOMM-CNET

Parameter #: 3CN Addr Cfg

020 <> 99

Default = 02




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 “1” enables the I/O. A “0” disables the I/O.

Bit 0 is the right-most bit. In figure 4.3, it is highlighted and equals“1.”

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 “Network” so 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 #: 13

DPI I/O Configxxxxxxxxxxx0000 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




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 parameterdetermines the data transmitted from the scanner to thedrive. A “1” enables the I/O. A “0” disables 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 “1” enables the I/O. A “0” disables 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 LogicCommand/Reference (Default)

1 DatalinkA Input

2 DatalinkB Input

3 DatalinkC Input

4 DatalinkD Input

5 - 15 Not Used

Port 5 Device

RECOMM-CNET

Parameter #: 25

M-S Inputxxxx xxxx xxx0 0001Cmd/Ref b00

Bit Description

0 Status/Feedback(Default)

1 DatalinkA Output

2 DatalinkB Output

3 DatalinkC Output

4 DatalinkD Output

5 - 15 Not Used

Port 5 Device

RECOMM-CNET

Parameter #: 26M-S Output

xxxxxxxxxxx0000 1Status/Fdbk b00

Th d l i d i I/O f h (i )




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 thedrive’s Reference to either match the network Reference (=100%),scale below the network Reference (<100%), or scale above thenetwork 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 Action’s operating states.The Idle Flt Action should be verified whencommissioning the drive on the network by testingthe operation with the controller in idle.

4 7 1 Ch i th F lt A ti




4.7.1 Changing the Fault Action

Set the values of Comm Flt Action (10) and Idle Flt Action (11) tothe desired responses as shown in table 4.2. See figure 4.6 forsample LCD OIM Fault Action screens.

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

required.

Table 4.2 – Selections for Drive Response to Communication Fault

Value Action Description

0 Fault (default) The drive is faulted and stopped(Default).

1 Stop The drive is stopped, but notfaulted.

2 Zero Data The drive is sent 0 for output dataafter a communications disruption.This does not command a stop.

3 Hold Last The drive continues in its presentstate.

4 Send Flt Cfg The drive is sent the data that youset in the fault configurationparameters, Flt Cfg Logic (15)through Flt Cfg D2 In (24).

Figure 4.6 – Fault Action Screens on an LCD OIM

Port 5 Device

RECOMM-CNET

Parameter #: 10CommFlt Action

0Fault

Port 5 Device

RECOMM-CNET

Parameter #: 11

Idle Flt Action0

Fault

4 7 2 Setting the Fault Configuration Parameters




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 a

16-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 to

observe this precaution could result in bodily injuryor damage to equipment.

Set Reset Module (9) to Reset Module See figure 4 7




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 or

resetting 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 #: 9

Reset Module1

Reset 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 networknode address.

Default: 2Minimum: 1

Maximum: 99Type: Read Only

06 CN Rate ActThe actual networkdata 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 Datalinkword. The drive determinesthe size of Datalinks.

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

1 = 32-bitType: Read Only

Table 4.4 – Module Configuration Status Parameters




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 = DatalinkA2 = DatalinkB3 = DatalinkC4 = DatalinkD5 = Not Used6 = Not Used7 = Not Used

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


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

Bit Definitions0 = Cmd/Ref1 = DatalinkA2 = DatalinkB3 = DatalinkC4 = DatalinkD5 = Not Used6 = Not Used7 = Not Used

26 M-S OutputConfigures the I/O Data to be transferred fromthedrive to the network.


1 = I/O enabledType: Read/Write

Reset Required: YesBit Definitions0 = Cmd/Ref1 = DatalinkA2 = DatalinkB3 = DatalinkC4 = DatalinkD5 = Not Used6 = Not Used7 = Not Used

27 Ref AdjustPercent scale factor for the Reference fromtheNetwork.

Default: 100.00Minimum: 0.00Maximum: 200.00

Type: Read/WriteReset Required: No

g

No. Name and Description Details

Bit

Default10000x xx

0123457 6

BitDefault 10000x xx

0123457 6

Bit

Default 10000x xx

0123457 6




CHAPTER5



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 for

configuring 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

5.1.1 Installing and Registering EDS Files in




g g gRSNetWorx

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




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 filesare registered from a directory on the hard drive.

Figure 5.3 – EDS Wizard Option Screen

Figure 5.4 – EDS Wizard Designation Screen

Step 3. The EDS Wizard will install and test the EDS files. Agreen check mark next to each file indicates success




green check mark next to each file indicates success.Click Next to continue (figure 5.5).

Figure 5.5 – EDS Files Installation Test Results Screen

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




can be changed if desired. Click Next to continue (figure5.6).

Figure 5.6 – EDS Wizard Change Graphic Image Screen

SP600

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 (figure

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

Step 7. Click on the DPI to ControlNet folder in the Hardwarewindow to view the EDS files that have been installed to




the 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

The various views can be displayed or closed by using the View menu. In figure 5.10, the Network Usage, Hardware and Graphici di l d hil h M d F i i




views 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

.




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

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




ControlNet 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/40C

icon.

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

Figure 5.13 – Sample ControlNet Configuration Screen

SP600 SP600




Step 5. The ControlNet module must be configured on theControlNet network so the controller can communicatewith it. Click the Edits Enabled check-box (figure 5.15).

Figure 5.14 – Sample ControlNet Configuration Box

Figure 5.15 – Example of Product Line after Drive Connection is Selected

SP600 SP600

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




save, 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 controller’s icon (PLC-5C) and selectSCANlist 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-CNETExample.XC

..




Step 8. Enter the Integer files to be used for ControlNetcommunications (figure 5.19). In this example, N9 is the

Data 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




Step 9. Enter the input and output size for the node on thenetwork. 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 equates

to 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-bit

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

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) and




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




Step 12. Click the Details (figure 5.22) tab. The availability ofchoosing connection options are determined by the EDSfile for the node. Click OK.

Figure 5.21 – Connection Properties: Electronic Keying Settings

Figure 5.22 – Connection Properties: Details Settings

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). If

prompted 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

Step 15. Enter a file name and click Save. The project is nowsaved for future use.




5.1.3 Verifying Network Properties

In the Network menu, select Properties to display the ControlNetdialog box (figure 5.26). Verify:

• The number in the Max Scheduled Address field is higher thanor equal to the highest node number that will perform I/Omessaging.

• The number in the Max Unscheduled Address field is higherthan or equal to the highest node number on the network.

• The correct type of media redundancy is selected in the MediaRedundancy field.

Important: The value in the Network Update Time (ms) field is5 ms or greater. Do not set lower than 5 ms. The NUTmust be set equal or lower than the RPI times set forthe devices on the network.

Figure 5.25 – Save As File Box

RECOMM-CNETExample.XC




Step 16. If a special media configuration is required (e.g.,repeater), select the Media Configuration tab (figure5.27) and make the appropriate changes. Refer to theRSNetWorx on-line help for more information.

Figure 5.26 – ControlNet Dialog Box

Figure 5.27 – ControlNet: Media Configuration Tab

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 will

communicate with it.

Figure 5.28 – ControlNet: General Tab

RECOMM-CNETControlNetdemonstrationprogramusingtwo SP600 demo units.

CHAPTER6C C li i



PLC-5C Applications 6-1

PLC-5C Applications

Chapter 6 provides information and examples that explain how touse I/O Messaging and Explicit Messaging to control, configure, andmonitor an SP600 drive using a PLC-5C.

6.1 About I/O Messaging

I/O messaging is used to transfer the data which controls the SP600

drive and sets its Reference. I/O can also be used to transfer data toand from Datalinks in SP600 drives.

The ControlNet module provides options for configuring and usingI/O, including the following:

• The size of I/O can be configured by enabling or disabling theLogic Command/Reference and Datalinks.

Chapter 4, Configuring the ControlNet Module, and Chapter 5,RSNetWorx Configuration for PLC-5C Applications, discuss how to

configure the module and scanner on the network for these options.The Glossary defines the different options. This chapter discusseshow to use I/O after you have configured the module and scanner.

!

ATTENTION: The examples in this publication areintended solely for purposes of example. There aremany variables and requirements with anyapplication. Rockwell Automation does not assume

responsibility or liability (to include intellectualproperty liability) for actual use of the examplesshown in this publication. Failure to observe thisprecaution could result in bodily injury or damage toequipment.

6.2 Understanding the I/O Image

The terms input and output are defined from the scanner’s point ofview Therefore output I/O is data that is output from the scanner




view. Therefore, output I/O is data that is output from the scannerand consumed by the ControlNet module. Input I/O is status datathat is produced by the module and consumed as input by thescanner.

The I/O image table will vary based on the following:

• Size (either 16-bit or 32-bit) of the Reference/Feedback (Ref/FdbkSize (07)) words and Datalink words used by the drive.

• Size (either 16-bit or 32-bit) of the Datalink words (Datalink Size(08)). If all I/O is not enabled, the image table is truncated. Theimage table always uses consecutive words starting at word 0.

Figure 6.1 illustrates an example of an I/O image with 16-bitwords.The configuration is shown to illustrate utilizing 10 words of

inputs and 10 words of outputs. Depending on your applicationneeds, this may vary.

Controller Scanner Module SP600 Drive

ControlNet DPI

WordandI/O




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

Output

Image

(Write)

Message

Handler

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 C2

8 Datalink Out D1

9 Datalink Out D2

0 LogicCommand

1 Reference

2 DatalinkIn A1

3 DatalinkIn A24 DatalinkIn B1

5 DatalinkIn B2

6 DatalinkIn C1

7 DatalinkIn C2

8 DatalinkIn D1

9 DatalinkIn D2

LogicStatus

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

Word and I/O

Message

Handler

Message

HandlerMessage

Buffer

Message

Buffer

Message

Handler

LogicCommand

Reference

Data In A1

Data In A2Data In B1

Data In B2

Data In C1

Data In C2

Data In D1

Data In D2

Word I/O Word I/O0 LogicCommand/Status 8 - 11 Datalink B1/B2

1 Pad Word 12 - 15 Datalink C1/C2

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

4 - 7 DatalinkA1/A2

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/StatusWhen enabled, the Logic Command/Status word is always word 0 inthe I/O image. The Logic Command is a 16-bit word of controlproduced by the scanner and consumed by the module. The LogicStatus is 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 LogicStatus

1 Pad Word

2 Feedback(LSW)

3 Feedback(MSW)

4 DatalinkOut B1

5 DatalinkOut B2

0 LogicCommand

1 Pad Word

2 Reference (LSW)

3 Reference (MSW)

4 DatalinkIn B1

5 DatalinkIn B2

Word and I/O

LogicCommand

Reference

Data In A1

Data In A2

Data In B1

Data In B2

Data In C1

Data In C2

Data In D1Data 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)

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) is




produced 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-bit -2147483648 to 2147483647 Word 2 and Word 3 Figure 6.2

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 “58” in 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

Datalink

Most/Least

Significant Word Parameter

Data

(decimal)

A1 LSW 9 58

A2 MSW 9 0

Datalink

Most/Least


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 231 through 216

LSW 215 through 20

6.6 Function of the Sample Program

The program performs the following actions:

• Obtains Logic Status information from the drive.




g

• 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 fromthe network to thedrive.

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

6.7 Main Program (PLC-5C)

There is an operator station wired into the local rackas follows:




Figure 6.3 – I/O Messaging

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 Feedback The 20-COMM-C on the PowerFlex70 drive is mapped as follows: N9:0 LogicStatus N10:0 LogicCommandN9:1 Feedback N10:1 Reference

N9:2 DatalinkA1 Out N10:2 DatalinkA1 InN9:3 DatalinkA2Out N10:3 DatalinkA2 InN9:4 DatalinkB1 Out N10:4 DatalinkB1 InN9:5 DatalinkB2 Out N10:5 DatalinkB2 InN9:6 DatalinkC1 Out N10:6 DatalinkC1 InN9:7 DatalinkC2 Out N10:7 DatalinkC2 InN9:8 DatalinkD1 Out N10:8 DatalinkD1 InN9:9 DatalinkD2 Out N10:9 DatalinkD2 In

0000I:000

0

OperatorStartPushbutton

N10:0

1

DriveLogicCommandSTART

0001I:000

1

OperatorStopPushbutton

N10:0

0

DriveLogicCommandSTOP

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

002I:000

OperatorClear FaultsPushbutton

N10:0

DriveLogicCommandCLEAR FAULTS




Figure 6.4 – I/O Messaging (Continued)

0022

3

003I:000

3

Operator

Fwd / RevSelector Switch

N10:0

4

Drive

LogicCommandFORWARD

004I:000

3

OperatorFwd / RevSelector Switch

N10:0

5

DriveLogicCommandREVERSE

005N9:0

0

Drive

READYStatusBit

O:000

0

Operator

Drive ReadyStatusDisplay

006N9:0

1

DriveACTIVEStatusBit

O:000

1

OperatorDrive ActiveStatusDisplay

N9:0

Drive

FAULTED

Status

Bit

O:000

Operator

Drive Faulted

Status

Display





007

N9:0

7

O:000

2

This rung moves the Speed Reference fromthe operator station to the

drive.

008

MOV

Move

Source I:001

0<

Dest N10:1

0<

MOV

The rung moves the Speed Feedbackfromthe drive to the operator

station.

009MOV

Move

Source N9:1

0<

Dest O:001

0<

MOV

This rung moves Datalinkdata (N7) to the drive, where it is moved

into parameters.

010COP

Copy File

Source #N7:0

Dest #N10:2

Length 8

COP

Drive

DatalinkA1 In

This rung moves Datalinkdata fromthe drive to file N7.

011COP

Copy FileSource #N9:2Dest #N7:10

COP





Dest #N7:10Length 8

This rung executes the messaging logic.

012JSR

Jump To SubroutineProg File Number U:3

JSR

013 END

6.8 About Explicit Messaging

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




6.8.1 Performing Explicit MessagesImportant: 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 send

Parameter 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 Message

Response. The Explicit Message is complete.

Figure 6.7 – Explicit Message Process

The ControlNet I/O Transfer (CIO) instruction is used to sendExplicit Messages. For PLC-5C controllers before Series F RevisionC, the available services you should use are Get Attribute Single,Get Attribute All, Set Attribute Single, or Set Attribute All. Series FRevision C (or later) allow for more complex messages using a newGeneric Bi-Directional communication command.




6.8.2 Explicit Messaging Examples

A Get Attributes Scattered message allows for reading multipleparameters that may or may not be in sequential order (figure 6.9).

• A Service Code of “4B” indicates the Get_Attributes_Scatteredservice (see page C-20, Object Specific Services).).

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

• An Instance Number of “0” accesses the Class Attributes (seepage C-16, Instances).

• N13:0-11 contains the request message and N14:0-11 containsthe response message (see page C-20, Format forGet_Attributes_Scattered Service).

Figure 6.8 – Explicit Messaging

This rung sends a message to the drive over ControlNet and receives

file N13 while the response data is placed in data file N14.the response fromthe drive. The message to be sent is built in data

000N7:2

0

User LogicMessageInitiate

ENDN

ER

CIOControlNet I/O TransferControl CT12:0

Setup Screen

CIO

001 END




Get Attributes Scattered Example request and response Data:

Request Data

Figure 6.9 – CIO Get Attributes Scattered Screen

N13:0 12 Parameter Number = 12

N13:1 0 (Pad Word)

N13:2 0 (Pad Word)


N13:4 0 (Pad Word)

N13:5 0 (Pad Word)


N13:7 0 (Pad Word)

N13:8 0 (Pad Word)


N13:10 0 (Pad Word)

N13:11 0 (Pad Word)

Response Data


N14:1 3333 Value = 333.3VDC

N14:2 0 (Pad Word)





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

• A Service Code of “4C” indicates the Set_Attributes_Scatteredservice (see page C-19, Object Specific Services).


N14:4 0 Value = 0.0Hz

N14:5 0 (Pad Word)N14:6 10 Parameter Number = 10

N14:7 148 Value = 14.8Hrs

N14:8


N14:10 23 Value = 2.3MWh

N14:11

Figure 6.10 – CIO Set Attributes Scattered Screen

Set Attributes Scattered Example request and response Data:

Request Data


N13:1 50 Value = 0.50HP




Response Data

A Get Attribute Single message is used to read a single parameter(figure 6.11).

• A Service Code of “E” indicates the Get_Attribute_Single service(see page C-20, Common Services).

• An Instance Number of “1” indicates Drive Parameter 1 will beaccessed (see page C-16, Instances).

• An Attribute Number of “9” indicates the Parameter ValueAttribute will be accessed (see page C-17, Instance Attributes).

N13:2 0 (Pad Word)


N13:4 1740 Value = 1740RPM

N13:5 0 (Pad Word)


N13: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)




Get Attribute Single example response (reading SP600 Parameter 1in figure 6.11):

Response Data

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

• A Service Code of “10” indicates the Set_Attribute_Single service(see page C-20, Common Services).

• An Instance Number of “41” indicates Drive Parameter 41 will beaccessed (see page C-16, Instances).

• An Attribute Number of “9” indicates the Parameter ValueAttribute will be written (see page C-17, Instance Attributes).

Figure 6.11 – CIO Get Attribute Single Screen

N14:0 0 Value = 0.0Hz

.




Set Attribute Single example request (writing SP600 parameter 41in figure 6.12):

Request Data

Figure 6.12 – CIO Set Attribute Single Screen

N13:0 2300 Value = 230.0 VAC

CHAPTER7ControlLogix Applications



ControlLogix Applications 7-1

Chapter 7 provides information and examples that explain how touse I/O Messaging and Explicit Messaging to control, configure, andmonitor an SP600 drive using a ControlNet scanner module.

Refer to chapter 6 for further information on I/O Image layout andusing Logic Command/Status, Reference/Feedback and Datalinks.

!

ATTENTION: The examples in this publication areintended solely for purpose of example. There aremany variables and requirements with anyapplication. Rockwell Automation does not assumeresponsibility or liability (to include intellectual

property liability) for actual use of the examplesshown in this publication. Failure to observe thisprecaution could result in bodily injury or damage toequipment.

ATTENTION: If Explicit Messages are programmedto write parameter data to Non-Volatile Storage(NVS) frequently, the NVS will quickly exceed its lifecycle and cause the drive to malfunction. Do notcreate a program that frequently uses ExplicitMessages to write parameter data to NVS. Datalinks

do not write to NVS and should be used for frequentlychanged parameters. Failure to observe thisprecaution could result in damage to, or destructionof, the equipment.

7.1 Configuring a ControlLogix CNBScanner

Configuring a ControlLogix CNB scanner, and the network, ismainly done using RSLogix 5000 software (figure 7.1). RSNetWorxis still required but only at the end of the configuration process




is still required, but only at the end of the configuration process.Start the RSLogix 5000 software to begin the configuration process.

Step 1. Right-click on the I/O Configuration folder and selectNew Module (figure 7.2).

Figure 7.1 – RSLogix 5000: I/O Configuration Selection

RSLogix5000 - Example_RECOMM-CNET[1756-L1]

_RECOMM-CNET

RSLogix 5000 - Example_RECOMM-CNET[1756/L1]




Step 2. Select the ControlNet module used by the controller. Inthis example (figure 7.3), a 1756-CNB Series BControlNet Bridge is selected. Click OK.

Figure 7.2 – RSLogix 5000: New Module Selection

_RECOMM-CNET

Figure 7.3 – Select Module Type: 1756-CNB/B Selection

Step 3. Enter a Name, Slot number, and Revision number(figure 7.4). Click Next>.




Step 4. This step is used to define controller-to-module behavior(figure 7.5). Inhibit Module inhibits/un-inhibits theconnection to the module. The Major Fault check-boxselects if a failure on the connection of this modulecauses a major fault on the controller if the connection forthe module fails. Click Next>.

Figure 7.4 – Module Properties: Name Selection

Figure 7.5 – Module Properties: Controller-to-Module Behavior Screen

Step 5. This window (figure 7.6) is displayed for informationalpurposes only. Click Next>.




Step 6. This window (figure 7.7) is displayed for informationalpurposes only. Click Finish>>.

Figure 7.6 – Module Properties: Indentification/Status Screen

Figure 7.7 – Module Properties: Informational Screen

Step 7. The 1756-CNB/B now appears in the I/O Configurationfolder (figure 7.8).

RSLogix5000- Example_RECOMM-CNET[1756-L1]




Figure 7.8 – RSLogix 5000: I/O Configuration Folder

_RECOMM-CNET



Step 9. To configure a RECOMM-CNET ControlNet module,select the CONTROLNET-MODULE type (figure 7.10).Click OK.




Step 10. Enter the Name, Description and Node number (figure7.11). The Comm Format selects the communicationformat for the module and must be set to Data-INT. Input Instance is the input connection point for the primaryconnection. Output Instance is the output connectionpoint for the primary connection. Configuration Instanceis the size of the configuration assembly. The valuesentered will vary based on your application needs and thesize (16- or 32-bit) of the Reference/Feedback andDatalinks in the drive. For example:

SP600 (16-Bit Ref/Fdbk and Datalinks)

Figure 7.10 – Select Module Type: Generic ControlNet Module Screen

Node configured for: Input Size Output Size

Logic Command / Reference andLogic Status / Feedback only

4 2

plus Datalink A 6 4

plus Datalink B 8 6

plus Datalink C 10 8

plus Datalink D 12 10

SP600_02




Step 11. The Requested Packet Interval (RPI) schedules theconnection to move data to or from the module at least

this often or the connection will fail with the RPI Not Validerror. Set this value to 5 ms or greater, and click Next> (figure 7.12).

Important: The RPI time must be set greater than or equal to theNetwork Update Time (NUT).

Figure 7.11 – Module Properties: ControlNet Module Parameters

Figure 7.12 – Module Properties: RPI Selection

Step 12. This window (figure 7.13) is for informational purposesonly. Click Finish>>.




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

Step 14. Repeat the previous steps for each additional node you

need to configure.

Figure 7.13 – Module Properties: My ControlNet

Figure 7.14 – RSLogix: Configure Additional Nodes Screen


SP600_02

ControllerExample_RECOMM-CNET

Step 15. In the Data Types folder, click on the Module-Defined sub-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 controller’s ladder logic.





Step 16. Select Communications / Download to 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

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.

RSLogix 5000 - Example_RECOMM-CNET [1756-L1]




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 / Save and save the project (figure 7.19).

d. Close RSNetworx.

This schedules the I/O that was configured inRLSLogix 5000.

Figure 7.17 – RSLogix: Attention Symbol

Controller Example - RECOMM-CNET

SP600_02

RE:

RE:

RE:




Figure 7.18 – RSNetWorx for ControlNet Screen

SP600

SP600




Figure 7.19 – RSLogix 5000: Example Without Attention Symbol

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 ProgramThe 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:

Parameter Settings for the Sample Program

Table 7.1 – Parameter Settings for the Sample Program

Device Parameter Name Value Description

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)




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.

SP600 Drive

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 be

transferred fromthe network to thedrive.

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

7.3 RSLogix 5000 Ladder Logic Program

This rungdetermines whether thedriveis running, andsets theDriveStatusRunningtagappropriately.

DriveInputImage.Data[2].1<PowerFlex70_02:I.Data[2].1>

DriveStatusRunning

This rungdetermines whether thedriveis running, andsets theDriveStatusRunningtagappropriately.

<SP600




Figure 7.21 – I/O Messaging

This rungdetermines whether thedriveis faulted, andsets theDriveStatusFaultedtagappropriately.

DriveInputImage.Data[2].7<PowerFlex70_02:I.Data[2].7>

DriveStatusFaulted

This rungdetermines whether thedriveis faulted, andsets theDriveStatusFaultedtagappropriately.

This rungmoves thedrive's frequency feedbacktotheDriveFeedbacktag.

Copy FileSource DriveInputImage.Data[3]

<PowerFlex70_02:I.Data[3]>Dest DriveFeedbackLength 1

COP

This rungmoves thedrive's frequency feedbacktotheDriveFeedbacktag.

WhentheDriveCommandStarttagis true, this rungsends astartcommandtothedrive.

DriveCommandStart

DriveOutputImage.Data[0].1<PowerFlex70_02:O.Data[0].1>

WhentheDriveCommandStarttagis true, this rungsends astartcommandtothedrive.

WhentheDriveCommandNotStoptagis false, this rungsends astopcommandtothedrive. This runguses anXIO inputinstructionbecauseStoppushbuttons areusually normally closedsothattheequipmentstops if awirebreaks.

/

DriveCommandNotStop


WhentheDriveCommandNotStoptagis false, this rungsends astopcommandtothedrive. This runguses anXIO inputinstructionbecauseStoppushbuttons areusually normally closedsothattheequipmentstops if awirebreaks.

WhentheDriveCommandJogtagis true, this rungsends ajogcommandtothedrive.

DriveCommandJog


WhentheDriveCommandJogtagis true, this rungsends ajogcommandtothedrive.

WhentheDriveCommandClearFaulttagis true, this rungsends aclear faultcommandtothedrive.

DriveCommandClearFault


WhentheDriveCommandClearFaulttagis true, this rungsends aclear faultcommandtothedrive.

<SP600_

<SP600_

<SP600_

<SP600_

<SP600_

<SP600_

This rungmoves datafromtheDriveReferencetagtothedrivewhereitis usedas afrequency reference.

7 Copy FileSource DriveReferenceDest DriveOutputImage.Data[1]

<PowerFlex70_02:O.Data[1]>Length 1

COP

This rungmoves datafromtheDriveReferencetagtothedrivewhereitis usedas afrequency reference.

This rungmoves Datalinkdatafromthedrive.This rungmoves Datalinkdatafromthedrive.

<SP600_





8 Copy FileSource DriveInputImage.Data[4]

<PowerFlex70_02:I.Data[4]>Dest ParameterDataFromDrive[0]Length 8

COP

This rungmoves Datalinkdatatothedrive.

9 Copy FileSource ParameterDataToDrive[0]Dest DriveOutputImage.Data[2]

<PowerFlex70_02:O.Data[2]>Length 8

COP

This rungmoves Datalinkdatatothedrive.

(End)

<SP600_

<SP600_

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 device’s parameters on the ControlNet network.

7.4.1 Performing Explicit Messages




Important: There are five basic events in the Explicit Messagingprocess 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

7.4.2 Explicit Messaging Examples

This rungsends aCIP messagetothePowerFlex70driveatControlNetaddress 2. Thedatasentis obtainedfromtheMessageSendDatatag. Thedatareceivedis storedintheMessageReplyDatatag. This MSG instructioncanbeconfiguredtosendany CIP message.

0 EnableDriveMessage

ENDNER

Type- CIP GenericMessageControl DriveMessageControl ...

MSG

This rungsends aCIP messagetothePowerFlex70driveatControlNetaddress 2. Thedatasentis obtainedfromtheMessageSendDatatag. Thedatareceivedis storedintheMessageReplyDatatag. This MSG instructioncanbeconfiguredtosendany CIP message.

This rungsends aCIP messagetotheSP600driveatControlNetAddress2. Thedatasentisobtained




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 “4B” indicates the Get_Attributes_Scattered

service (see page C-20, Object Specific Services).• A Class Number of “93” indicates accessing the DPI Parameter

Object (see page C-16, DPI Parameter Object).

• An Instance Number of “0” is 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

(End)




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)

(Destination) Response Data


1 3333 Value = 333.3VDC

2 0 (Pad Word)


4 0 Value = 0.0Hz

5 0 (Pad Word)





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 “4C” indicates the Set_Attributes_Scattered

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


7 148 Value = 14.8Hrs

8


10 23 Value = 2.3MWh

11

Figure 7.26 – Set_Attributes_Scattered Message Screen

Set_Attributes_Scattered sample request and response data:

(Source) Request Data


N13:1 50 Value = 0.50HP

N13:2 0 (Pad Word)


N13:4 1740 Value = 1740RPMN13 5 0 (P d W d)




(Destination) Response Data

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

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

• A Class Name of “F” indicates the Parameter Object (see pageC-6, Parameter Object).

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

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

N13:4 1740 Value 1740RPMN13:5 0 (Pad Word)


N13: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)






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



CHAPTER8Troubleshooting the

ControlNet Module

andNetwork



Troubleshooting the ControlNet Module and Network 8-1

and Network

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

8.1 Understanding the Status IndicatorsThe 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)



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 and

network.Flashing The module has • Cycle power to the drive




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 defaults

and reconfigure the module.• If resetting defaults does not

correct the problem, flash themodule with the latest firmwarerelease.

SolidRed

The module hasfailed the hardwaretest.

• Cycle power to the drive.

• Replace the module.

FlashingGreen

The module isoperational but is not

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

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 steady

red

A link interfacefailed.

• Check media for broken cables,loose connectors, missing

terminators, etc.• Power cycle or reset the




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 arealternating

red/off

There is a badconfiguration.

• Verify that all node addressesare unique.

• Check the module’sconfiguration.

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

• Power cycle or reset themodule.

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.

OnechannelLED is

There is an invalidlink configurationfor that channel

• Power cycle or reset themodule.




LED isflashingred/green

for that channel. • 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.

OnechannelLED issteadygreen

Normal operationfor that channel.

• No action required.

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 Logic

Cmd

The current value of the Common Logic

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




Command 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-Specific

Feedback being received from the host.7 Datalink A1 In The current value of Datalink A1 being

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

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 received

Table 8.5 – Module Diagnostic Items (Continued)

No. Event Description




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.







APPENDIXATechnical

Specifications



Technical Specifications A-1

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 +50°C (14 to 149°F)

-40 to +85°C (-40 to 185

°F)

Relative Humidity 5 to 95% non-condensing

UL 508C and CUL

CE EN61800-3



A-2 ControlNet Communications Module

APPENDIXBControlNet Module

Parameters



ControlNet Module Parameters B-1

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.

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

1 DPI Port

Range: 0 to 7

Default: 5

Type: Read Only

Reset Required: N/A

2 DPI Data Rate

Range: 0 = 125 Kbps



B-2 ControlNet Communications Module

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

module detects it.

Configures the network if the Node Address Switches are set to

“00.” Updates CN Addr Act (4) after reset.

The actual network node address.

Range: 0 125 Kbps1 = 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

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

reset.

5 CN Rate Cfg

Range: 0 = 5 Mbps

Default: 0 = 5 Mbps

Type: Read/Write

Reset Required: Yes

6 CN Rate Act




The actual Network Data Rate.

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

of the Reference/Feedback.

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

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



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/O

11 Idle Flt Action

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

Default: 0 = Fault

Type: Read/Write

Reset Required: No




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

!

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

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

13 DPI I/O Cfg

Range: See figure B.1.

Default: xxx0 0001

Type: Read/Write

Reset Required: Yes

fkAkBkCkDededd




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

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

000 10xxx

01234567

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

C m d / R e f

D a t a l i n k

A

D a t a l i n k

B

D a t a l i n k

D a t a l i n k

D

N o t U

s e d

N o t U

s e d

N o t U

s e d

14 DPI I/O Active


Default: xxx0 0001

Type: Read Only

Reset Required: N/A

Figure B.2 – DPI I/O Active (14)

000 10xxx

01234567


C m d / R e f

D a t a l i n k

A

D a t a l i n k

B

D a t a l i n k

C

D a t a l i n k

D

N o t U

s e d

N o t U

s e d

N o t U

s e d

Sets the Logic Command data that is sent to the drive if thefollowing is true:

• Comm Flt Action (10) is set to Send Flt Cfg and communicationsare disrupted.

• Idle Flt Action (11) is set to Send Flt Cfg and the scanner is put

15 Flt Cfg Logic

Range: 0000 0000 0000 0000 to 1111 1111 1111 1111

Default: 0000 0000 0000 0000

Type: Read/Write

Reset Required: No




• Idle Flt Action (11) is set to Send Flt Cfg and the scanner is putinto Program or Test mode.

The bit definitions will depend on the product to which the module isconnected.

Sets the Reference data that is sent to the drive if any of thefollowing is true:

• Comm Flt Action (10) is set to Send Flt Cfg and communications

are disrupted.

• Idle Flt Action (11) is set to Send Flt Cfg and the scanner is putinto Program mode.

Important: If the drive uses a 16-bit Reference, the most significantword of this value must be set to zero (0) or a fault willoccur.

16 Flt Cfg RefRange: 0 to 4294967295

Default: 0

Type: Read/Write

Reset Required: No



Configures the I/O Data to be transferred from the drive to the

network.

26 M-S Output


Default: xxx0 0001

Type: Read/Write

Reset Required: Yes

CD




The percent scale factor for the Reference from the Network.

Figure B.4 – M-S Output (26)

000 10xxx

01234567


C m d / R e f

D a t a l i n k

A

D a t a l i n k

B

D a t a l i n k

C

D a t a l i n k

D

N o t U

s e d

N o t U

s e d

N o t U

s e d

27 Ref Adjust

Range: 0.00 to 200.00

Default: 100.00

Type: Read/Write

Reset Required: No




APPENDIXCControlNet

Objects

Appendix C presents information about the ControlNet objects thatcan be accessed using Explicit Messages For information on the



ControlNet Objects C-1

can be accessed using Explicit Messages. For information on theformat of Explicit Messages and example ladder logic programs,refer to Chapter 7, ControlLogix Applications.

Refer to the ControlNet specification for more information aboutControlNet objects. Information about the ControlNet specification isavailable on the ControlNet web site (http://www.controlnet.org).

Object

Class Code Refer to

SectionHex. Dec.

Identity Object 0x01 1 C.1

Register Object 0x07 7 C.2

Parameter Object 0x0F 15 C.3

Parameter Group Object 0x10 16 C.4

PCCC Object 0x67 103 C.5

DPI Device Object 0x92 146 C.6

DPI Parameter Object 0x93 147 C.7

DPI Fault Object 0x97 151 C.8

DPI AlarmObject 0x98 152 C.9

DPI Time Object 0x9B 155 C.10

C.1 Identity Object

Class Code

Instances

The number of instances depends on the number of components inthe device connected to the module. This number of componentscan be read in Instance 0, Attribute 2.

Hexadecimal Decimal

0x01 1

I D i i



C-2 ControlNet Communications Module

Class Attributes

Instance Attributes

Instance Description

0 Class

1 Entire device

2 - 7 DPI Peripherals on ports 1 - 6

Attribute

ID

Access

Rule Name Data Type Description

2 Get Max Instance UINT Total number ofinstances

Attribute

ID

Access


1 Get Vendor ID UINT 5 = Reliance Electric

2 Get Device Type UINT 120

3 Get Product Code UINT Number identifyingproduct name andrating

4 Get Revision:

MajorMinor

STRUCT of

USINTUSINT

Value variesValue varies

5 Get Status WORD Bit 0 = OwnedBit 2 = ConfiguredBit 10 = RecoverablefaultBit 11 =Unrecoverable fault

6 Get Serial Number UDINT Unique 32-bit number



C.2 Register Object

Class Code

Instances

Hexadecimal Decimal

0x07 7


1 All I/O data being read fromthe DPI device (read-only)

2 AllI/OdatawrittentotheDPIdevice(read/write)




Class Attributes

2 All I/O data written to the DPI device (read/write)

3 Logic Status and Feedback data (read-only)

4 Logic Command and Reference data (read/write)

5 Datalink A (input data fromdevice to scanner) (read only)

6 Datalink A (output data fromscanner to device) (read/write)

7 Datalink B (input data fromdevice to scanner) (read only)

8 Datalink B (output data fromscanner to device) (read/write)

9 Datalink C (input data fromdevice to scanner) (read only)

10 Datalink C (output data fromscanner to device) (read/write)

11 Datalink D (input data fromdevice to scanner) (read only)

12 Datalink D (output data fromscanner to device) (read/write)

13 Logic Status and Feedback Data (read-only)

14 Mask1(read/write)

1 The mask command word is set to the value of the first word of the datawhere there are ones in the second word of the data. Command = (word1 and not word 2) or (word 1 and word 2). This only controls specified bitsin the Logic Command data to the DPI product and does not change theReference value.

AttributeID

AccessRule Name Data Type Description

100 Set Control Timeout UINT Control timeout inseconds

Instance Attributes

Attribute

ID

Access

Rule Name

Data

Type Description

1 Get Bad Flag BOOL If set to 1, then attribute4 may contain invalid,bad or otherwise corruptdata.0 = good

1 = bad

2 Get Direction BOOL Direction of data transfer0 = Producer Register1 = Consumer Register




Important: Setting a register object attribute can only beaccomplished through a connection with a non-zerocontrol timeout attribute.

Services

3 Get Size UINT Size of register data inbits

4 Conditional1

1

The access rule of Set is optional if attribute 2, Direction = 1.If Direction = 0, the access rule is Get.

Data ARRAYof BITS

Data to be transferred

Service

Code

Implemented for:

Service NameClass Instance0x0E Yes Yes Get_Attribute_Single

0x10 No Yes Set_Attribute_Single

C.3 Parameter Object

Class Code

Instances

The number of instances depends on the number of parameters inthe DPI drive. The module parameters are appended to the list ofdrive parameters. The total number of parameters can be read inInstance 0, Attribute 2.

Hexadecimal Decimal

0x0F 15




Class Attributes


0 Class Attributes

1 Drive Parameter 1 Attributes

… …n Last Drive Parameter Attributes

n + 1 Module Parameter 1 Attributes

… …

n + 43 Last Module Parameter Attributes

AttributeID

AccessRule Name

DataType Description

1 Get Revision UINT 1

2 Get Max Instance UINT Number of parameters

8 Get ParameterClassDescriptor

WORD Bits that describe parameters.

9 Get ConfigurationAssembly

Instance

UINT 0

Instance Attributes

10 Set NativeLanguage

USINT 0 = English1 = French2 = Spanish3 = Italian4 = German5 = Japanese6 = Portuguese

7 = Mandarin Chinese8 = Russian9 =

Attribute

ID

Access

Rule Name

Data

Type Description




Attribute

ID

Access

Rule Name

Data

Type Description

1 1 ParameterValue

2 3

2 Get LinkPath Size USINT 0 = No link specifiedn = Link specified

3 Get LinkPath 4

4 Get Descriptor WORD 0 = False, 1 = TrueBit 1 = Supports ENUMsBit 2 = Supports scalingBit 3 = Supports scaling linksBit 4 = Read onlyBit 5 = Monitor

Bit 6 = Extended precision scaling

5 Get Data Type USINT 1 = WORD (16-bit)2 = UINT (16-bit)3 = INT (16-bit)4 = BOOL5 = SINT6 = DINT7 = LINT8 = USINT

6 Get Data Size USINT 3

7 Get ParameterName String

SHORT_STRING

3

8 Get Units String SHORT_STRING

3

9 Get Help String SHORT_STRING

0



C.4 Parameter Group Object

Class Code

Instances

The number of instances depends on the number of groups in thedevice. A group of module parameters is appended to the list ofgroups in the device. The total number of groups can be read inInstance 0, Attribute 2.

Hexadecimal Decimal

0x10 16




Class Attributes

Number Description

0 Class Attributes

1 Drive Group 1 Attributes

… …n Last Drive Group Attributes

n + 1 Module Group Attributes

Attribute

ID

Access

Rule Name

Data

Type Description

1 Get Parameter

groupversion

UINT 1

2 Get MaxInstance

UINT Total number of groups

8 Get NativeLanguage

USINT 0 = English1 = French2 = Spanish (Mexican)3 = Italian4 = German

5 = Japanese6 = Portuguese7 = Mandarin Chinese8 = Russian9 =

Instance Attributes

Attribute

ID

Access

Rule Name

Data

Type Description

1 Get Group NameString

SHORT_STRING

Group name

2 Get Number ofMembers inGroup

UINT Number of parameters in group.

3 Get 1st ParameterNumber in Group

UINT 1

4 Get 2nd ParameterNumber in Group

UINT 1




Services

n Get … UINT 1

1 Value varies based on group instance.

Service Code

Implemented for:

Service NameClass Instance

0x0E Yes Yes Get_Attribute_Single

0x01 Yes No Set_Attribute_Single



Message Structure for Execute_PCCC

Request Response

Name

Data

Type Description Name

Data

Type Description

Length USINT Length ofrequestor ID

Length USINT Length of requestor ID

Vendor UINT Vendor number

of requestor

Vendor UINT Vendor number of

requestorSerialNumber

UDINT ASA serialnumber ofrequestor

SerialNumber

UDINT ASA serial number ofrequestor

Other Product Identifier of user, Other Product Identifier of user, task,




Specific task, etc,. on therequestor

Specific etc., on the requestor

CMD USINT Command byte CMD USINT Command byte

STS USINT 0 STS USINT Status byte

TNSW UINT Transport word TNSW UINT Transport word. Samevalue as the request.

FNC USINT Function code.Not used for allCMDs.

EXT_STS USINT Extended status. Notused for all CMDs.

PCCC_params

ARRAY ofUSINT

CMD/FNCspecificparameters

PCCC_results

ARRAY ofUSINT

CMD/FNC specificresult data









5 Get FirstAccessibleParameter

WORD First parameter available ifparameters are protected bypasswords. A“0”indicates allparameters are protected.

7 Get Class Revision WORD 2 = DPI

8 Get First ParameterProcessingError

WORD The first parameter that has beenwritten with a value outside of itsrange. A“0”indicates no errors.

9 Set LinkCommand BYTE 0 = No operation1 = Clear all parameter links (This

does not clear links to functionblocks.)

Attribute

ID

Access

Rule Name

Data

Type Description




Instance Attributes

Attribute

ID

Access


7 Get DPI OnlineRead Ful

STRUCT ofBOOL[32]

CONTAINER1

CONTAINERCONTAINERCONTAINERWORDWORDSTRING[4]

UINT

UINT

UINT

INT

BYTE[3]BYTESTRING[16]

Descriptor (refer to pages C-21to C-22)Parameter valueMinimumvalueMaximumvalueDefault valueNext parameterPrevious parameterUnits (e.g., amp, Hz)

Multiplier2

Divisor2

Base2

Offset2

Link (source of the value) (0 =no link)Always zero (0)Parameter name

8 Get DPI

Descriptor

BOOL[32] Descriptor (refer to pages

C-22 to C-23)9 Get/Set DPI

ParameterValue

Various Parameter value in NVS3

10 Get/Set DPI RAMParameterValue

Various Parameter value in temporarymemory

11 Get/Set DPI Link BYTE[3] Link (parameter or functionblockthat is the source of thevalue) (0 = no link)

12 Get Help ObjectInstance

WORD ID for help text for thisparameter

13 Get DPI ReadBasic

STRUCT ofBOOL[32]

CONTAINERCONTAINERCONTAINERCONTAINERSTRING[16]S G[ ]

Descriptor (Refer to pages C-22 to C-23)Parameter valueMinimumvalueMaximumvalueDefault valueParameter name

i ( )

Attribute

ID

Access





STRING[4] Units (e.g., Amp, Hz)

14 Get DPIParameterName

STRING[16] Parameter name

15 Get DPIParameterAlias

STRING[16] Customer-supplied parametername

16 Get ParameterProcessingError

BYTE 0 = No error1 = Value is less than the

minimum2 = Value is greater than the

maximum

1 A CONTAINER is a 32-bit block of data that contains the data type used by aparameter value. If signed, the value is sign extended. Padding is used in theCONTAINER to ensure that it is always 32-bits.

2 This value is used in the formulas used to convert the parameter value betweendisplay units and internal units. Refer to Formulas for Converting on page C-20.

3 Do NOT continually write parameter data to NVS. Refer to the attention on page 7-1.

Descriptor Attributes

Bit Name Description

0 Data Type (Bit 1) Right bit is least significant bit (0).000 = BYTE used as an array of Boolean001 = WORD used as an array of Boolean010 = BYTE (8-bit integer)011 = WORD (16-bit integer)100 = DWORD (32-bit integer)

101 = TCHAR (8-bit (not unicode) or 16-bits (unicode))110 = REAL (32-bit floating point value)111 = Use bits 16, 17, 18

1 Data Type (Bit 2)

2 Data Type (Bit 3)

3 Sign Type 0 = Unsigned1 = Signed

4 Hidden 0 = Visible




1 = Hidden

5 Not a Link Sink 0 = Parameter can sink a link1 = Parameter cannot sinka link

6 Not Recallable 0 = Recallable fromNVS1 = Not Recallable fromNVS

7 ENUM 0 = No ENUMtext1 = ENUMtext

8 Writable 0 = Read only1 = Read/write

9 Not Writable WhenEnabled

0 = Writable when enabled (e.g., drive running)1 = Not writable when enabled

10 Instance 0 = Parameter value is not a Reference to another

parameter1 = Parameter value refers to another parameter

11 Reserved Must be zero

12 Decimal Place (Bit 0) Number of digits to the right of the decimal point.0000 = 01111 = 15

13 Decimal Place (Bit 1)



16 ExtendedData Type (Bit 1)

Right bit is least significant bit (16).000 = Reserved001 = DWORD used as an array of Boolean010 = Reserved011 = Reserved100 = Reserved101 = Reserved110 = Reserved111 = Reserved



19 Parameter Exists Reserved

20 Not Used Reserved

21 Formula Links Reserved

22 Access Level (Bit 1) Reserved

23 Access Level (BIt 2) Reserved

24 Access Level (Bit 3) Reserved

25 Writable ENUM Reserved

26 Not a Link Source 0 = Parameter can be a source for a link1 = Parameter cannot be a source for a link

27 Enhanced Bit ENUM Reserved

28 Enhanced ENUM Reserved


Bit Name Description




Formulas for Converting

Display Value = ((Internal Value + Offset) xMultiplier xBase) / Divisor x10Decimal Places

Internal Value =((Display Value xDivisor x10Decimal Place) / (Multiplier xBase)) -Offset

Common Services

Object Specific Services



Service

Code

Implemented for:

Service NameClass Instance0x0E Yes Yes Get_Attribute_Single

0x10 Yes Yes Set_Attribute_Single

Service

Code

Implemented for:


0x4B Yes Yes Get_Attributes_Scattered0x4C Yes Yes Set_Attributes_Scattered

Format for Get_Attributes_Scattered Service

The structure shown below can get up to 22 parameters in a singlemessage. In the Response Message, a parameter number with thehigh bit set indicates that the associated parameter value fieldactually contains an error code.

Request Response

Word 0 Parameter Number Word 0 Parameter Number

1 Pad Word 1 Parameter Value LSW

2 Pad Word 2 Parameter Value MSW

3 Parameter Number 3 Parameter Number


5 PadWord 5 ParameterValueMSW














15 Parameter Number 15 Parameter Number16 Pad Word 16 Parameter Value LSW






22 Pad Word 22 Parameter Value LSW23 Pad Word 23 Parameter Value MSW

... ...


64 Pad Word 64 Pad Word

65 Pad Word 65 Pad Word

The PLC data in this example is for a Get_Attributes_Scattered ofSP600 parameters; Output Freq (1), Output Current (3), and OuptutVoltage (6) from a device at node address 1.

Request Data for Get_Attributes_Scattered

Word Value (hex) Description

0 001 Parameter Number 1

1 0000 Pad Word

2 0000 Pad Word


4 0000 Pad Word

5 0000 Pad Word

6 0006 ParameterNumber6




Response Data for Get_Attributes_Scattered


7 0000 Pad Word

8 0000 Pad Word

Word

Value

(hex) Description


1 0258 Value = 600 (258 hex) = 60.0 Hz

2 0000


4 0001 Value = 1 (1 hex) = 0.1A

5 0000


7 0864 Value = 2148 (864 hex) = 214.8V AC

8 0000





C.8 DPI Fault Object

Class Code

Products such as SP600 drives use this object for faults. Modulesuse this object for events.

Instances

The number of instances depends on the maximum number offaults or events supported in the queue. The maximum number offaults/events can be read in Instance 0, Attribute 2.

Hexadecimal Decimal

0x97 151

Number Description




Class Attributes

Number Description

0 Class Attributes (Drive)

1 Most Recent Drive Fault/Event

2 Second Most Recent Drive Fault/Event

… …

16384 Class Attributes (Module)

16385 Most Recent Module Fault/Event

… …

Attribute

ID

Access


1 Get Class Revision WORD Revision of object

2 Get Number ofInstances

WORD Maximumnumber of faults/ events that the device canrecord in its queue

3 Set Fault CommandWrite

BYTE 0 = No Operation1 = Clear Fault/Event

2 = Clear Fault/Event Queue3 = Reset Device

4 Get Fault TripInstance Read

WORD Fault that tripped the device.For modules, this value isalways 1 when faulted.

5 Get Fault Data List STRUCT ofBYTEBYTEWORD[n]

Reserved

Instance Attributes

6 Get Number ofRecorded Faults

WORD Number of faults/events in thequeue. A“0”indicates the faultqueue is empty.

7 Get Fault ParameterReference

WORD Reserved

Attribute

ID

Access


Attribute

ID

Access


0 Get Full/AllInformation

STRUCT ofWORDSTRUCT ofBYTE

Fault codeFault sourceDPIport




BYTEBYTESTRING[16]STRUCT ofLWORD

BOOL[16]

WORDCONTAINER[n]

DPI portDPI Device ObjectFault textFault time stampTimer value (0 = Timer notsupported)BOOL[0]: (0 = invalid data,

1 = valid data)BOOL[1]: (0 = elapsed time,

1 = real time)BOOL[2 - 15]: Not usedReservedReserved

1 Get Basic

Information

STRUCT of

WORDSTRUCT ofBYTEBYTESTRUCT ofLWORD

BOOL[16]

Fault codeFault sourceDPI portDPI Device ObjectFault time stampTimer value (0 = Timer notsupported)BOOL[0]: (0 = invalid data,


1 = real time)BOOL[2 - 15]: Not used



C.9 DPI Alarm Object

Class Code

Products such as SP600 drives use this object for alarms orwarnings. Modules do not support this object.

Instances

The number of instances depends on the maximum number ofalarms supported by the queue. The maximum number of alarmscan be read in Instance 0, Attribute 2.

Hexadecimal Decimal

0x98 152

Number Description




Class Attributes

u be esc pt o

0 Class Attributes

1 Most Recent Alarm

2 Second Most Recent Alarm

… …

Attribute

ID

Access




WORD Maximumnumber of alarms thatthe device can record in itsqueue

3 Set AlarmCommandWrite

BYTE 0 = No Operation1 = Clear Alarm2 = Clear AlarmQueue3 = Reset Device

4 Get Fault Data List STRUCT ofBYTEBYTEWORD[n]

Reserved

5 Get Number ofRecordedAlarms

WORD Number of alarms in the queue.A“0”indicates the alarmqueueis empty.

Instance Attributes

Attribute

ID

Acces

s Rule Name Data Type Description

0 Get Full/AllInformation

STRUCT ofWORDSTRUCT ofBYTEBYTESTRING[16]STRUCT ofLWORD

BOOL[16]

AlarmcodeAlarmsourceDPI portDPI Device ObjectAlarmtextAlarmtime stampTimer value (0 = Timer not

supported)BOOL[0]: (0 = invalid data,


1 = real time)BOOL[2- 15]Reserved




Services

WORDCONTAINER[n]

BOOL[2 - 15] ReservedReservedReserved

1 Get BasicInformation

STRUCT ofWORDSTRUCT ofBYTEBYTESTRUCT ofLWORD

BOOL[16]

AlarmcodeAlarmsourceDPI portDPI Device ObjectAlarmtime stampTimer value (0 = Timer not

supported)BOOL[0]: (0 = invalid data,


1 = real time)BOOL[2 - 15] Reserved

Service Code

Implemented for:




C.10 DPI Time Object

Class Code

Instances

The number of instances depends on the number of timers in thedevice. Instance 1 is always reserved for a real time clock althougha device may not support it. The total number of timers can be readin Instance 0, Attribute 2.

Hexadecimal Decimal

0x9B 155

Number Description

0 Class Attributes

1 R lTi Cl k(P d fi d)




Class Attributes

1 Real Time Clock (Predefined)(Not always supported)

2 Timer 13 Timer 2

… …

Attribute

ID

Access

Rule Name

Data

Type Description



WORD Number of timers in the object,excluding the real time clock thatis predefined

3 Get First DeviceSpecificTimer

WORD Instance of the first timer that isnot predefined

4 Set Time CommandWrite

BYTE 0 = No operation1 = Clear all timers (Does not

clear the real time clock orread only timers)

Instance Attributes

Attribute

ID

Access


0 Get Read Full STRUCT ofSTRING[16]LWORD orSTRUCT

BOOL[16]

Name of the timerElapsed time in milliseconds unlesstimer is a real time clock (Seeattribute 2)See Attribute 3

1 Get Timer Text STRING[16] Name of the timer

2 Get/Set Timer Value LWORD-OR-

STRUCT ofWORDBYTE

Elapsed time in milliseconds unlessthe timer is a real time clock.Real Time ClockData:

Milliseconds (0 – 999)Seconds (0 – 59)




Services

BYTEBYTE

BYTEBYTEBYTE

( )Minutes (0 – 59)Hours (0 – 23)

Days (1 – 31)Months (1 = January, 12 = December)Years (since 1972)

3 Get TimerDescriptor

BOOL[16] BOOL[0]: (0 = invalid data,1 = valid data)

BOOL[1]: (0 = elapsed time,1 = real time)

BOOL[2 - 15]: Not used

Service

Code

Implemented for:







APPENDIXDLogic Command/

Status Words

Appendix D provides the definitions of the Logic Command/LogicStatus words that are used for some products that can beconnected to the ControlNet module. If you do not see the LogicCommand/Logic Status for the product that you are using, refer toyour product’s documentation.



Logic Command/Status Words D-1

D.1 SP600 Drives

Logic Command Word

Logic Bits

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Command Description

x Stop 0 = Not Stop

1 = Stop

x Start1 0 = Not Start

1 = Start

x Jog 0 = Not Jog

1 = Jog

x Clear Faults 0 = Not Clear Faults

1 = Clear Faults

x x Direction 00 = No Command

01 = Forward Command

10 = Reverse Command

11 = Hold Direction Control

x Local Control 0 = No Local Control

1 = Local Control

x MOP

Increment

0 = Not Increment

1 = Increment

x x Accel Rate 00 = No Command

01 = Accel Rate 1 Command

10 = Accel Rate 2 Command

11 = Hold Accel Rate

x x Decel Rate 00 = No Command

01 = Decel Rate 1 Command

10 = Decel Rate 2 Command

11 = Hold Decel Rate



x x x x Reference 0000 = Ref A Auto

0001 = Reserved

0010 = Preset 2 Auto






1000 = TermBlkManual1001 = DPI 1 Manual

1010 = DPI 2 Manual

1011 = DPI 3 Manual

1100 = DPI 4 Manual

1101 = DPI 5 Manual

1110 = DPI 6 Manual

1111 = Jog Ref

Logic Bits15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Status Description



Logic Command/Status Words D-3



D-4 ControlNet Communications Module

GLOSSARY

CAN (Controller Area Network) - A serial bus protocol on whichDPI is based.

ControlNet - An open producer/consumer communication network,

with features such as redundant media and deterministic I/O timing,designed for high-performance or time-critical requirements.

controller - Also called programmable logic controller. A solid-statecontrol system that has a user-programmable memory for storageof instructions to implement specific functions such as I/O control,logic, timing, counting, report generation, communication,arithmetic, and data file manipulation. A controller consists of acentral processor, input/output interface, and memory. See also



Glossary Glossary-1

scanner.

data rate - The data rate is the speed at which data is transferredon the ControlNet network (fixed at 5 Mbps).

Datalink - A type of pointer used by some SP600 drives to transferdata to and from the controller. Datalinks allow specified parametervalue(s) to be accessed or changed without using explicitmessages. When enabled, each Datalink consumes either fourbytes or eight bytes in both the input and output image table of thecontroller. The drive determines the size of Datalinks.

DPI (Drive Peripheral Interface) - A peripheral communicationinterface used by various Reliance Electric drives and powerproducts.

DPI peripheral - A device that provides an interface between DPIand a network or user. Peripheral devices are also referred to as“modules” and “adapters.” The ControlNet module and SP600 OIMare examples of DPI peripherals.

DPI product - A device that uses the DPI communications interfaceto communicate with one or more peripheral devices. For example,

a motor drive such as a SP600 drive is a DPI product. In thismanual, a DPI product is also referred to as “product” or “host.”

Electronic Data Sheet (EDS) files - Simple text files that are usedby network configuration tools such as RSNetWorx for ControlNet todescribe products so that you can easily commission them on anetwork. EDS files describe a product device type, revision, andconfigurable parameters.

Explicit Messaging - Used to transfer data that does not requirecontinuous updates. It is typically used to configure or monitor adevice’s parameters on the network.

fault action - Determines how the module and connected productact when a communications fault (for example, a cable isdisconnected) occurs or when the scanner is switched out of runmode. The former uses a communications fault action, and the latteruses an idle fault action.

fault configuration - When communications are disrupted (for

example, a cable is disconnected), the module and SP600 drive canrespond with a user-defined fault configuration. The user sets thedata that is sent to the drive in the fault configuration parameters(parameters 15 (Flt Cfg Logic) through 24 (Flt Cfg D2 In). When afault action parameter is set to use the fault configuration and a faultoccurs, the data from these parameters is sent as the CommandLogic, Reference, and/or Datalink(s).

flash update - The process of updating firmware in the module.Th d l b fl h d d i h X M d l d



Glossary-2 ControlNet Communications Module

The module can be flash updated using the X-Modem protocol anda RECOMM-232 serial converter.

hold last - When communications are disrupted (for example, acable is disconnected), the module and SP600 drive can respond byholding last. Hold last results in the drive receiving the last datareceived via the ControlNet connection before the disruption. If thedrive was running and using the reference from the module, it willcontinue to run at the same reference.

I/O connection - 1-to-n-based I/O messaging link in which I/O datais produced or consumed by a device without any interpretation.

I /O data - I/O data, sometimes called “implicit messages” or “input/ output,” transmit time-critical data such as a Logic Command andReference. The terms “input” and “output” are defined from thescanner’s point of view. Output is transmitted by the scanner andconsumed by the module. Input is transmitted by the module andconsumed by the scanner.

Logic Command/Logic Status - The Logic Command is used tocontrol the SP600 drive (e.g., start, stop, direction). It consists ofone 16-bit word of input to the module from the network. The

definitions of the bits in this word depend on the drive.

The Logic Status is used to monitor the SP600 drive (for example,operating state, motor direction). It consists of one 16-bit word ofoutput from the module to the network. The definitions of the bits inthis word depend on the drive.

master - see scanner



status indicators - LEDs that are used to report the status of themodule, network, and drive. They are on the module and can beviewed on the front cover of the drive when the drive is powered.

VS Utilities software - A software tool for monitoring andconfiguring Reliance Electric products and modules. It can be runon computers running Microsoft Windows 95, Windows 98,Windows NT (version 4.0 or greater), Windows Me, Windows 2000,or Windows XP operating systems. VS Utilities can be used toconfigure the ControlNet module and SP600 drives.

zero data - When communications are disrupted (for example, acable is disconnected), the module and drive can respond with zerodata. Zero data results in the drive receiving zero as values forcommand data. If the drive was running and using the referencefrom the module, it will stay running but at zero reference.



Glossary-4 ControlNet Communications Module



MMaster-Slave hierarchy

configuring a module for, 4-4

mechanical specifications, A-1

module

components, 2-1

configuration, viewing, 4-8

configuring, 4-1 to 4-9

diagnostic items, 8-6

dimensions, A-1

features, 1-1installing, 3-1 to 3-6

parameters, B-1 to B-9

resetting, 4-7

specifications , A-1

troubleshooting, 8-1 to 8-10

M-S Input (25), B-8

M-S Output (26), B-9

MS status indicator, 8-3

Pparameter descriptions, B-1 to B-9

parameter group object, C-9

parameter object, C-6

PCCC object, C-11

P-DP Addr Cfg (3), B-2

PLC-5C applications, 6-1 to 6-18

PLC-5C main program, 6-8

power consumption, A-1

protocol, A-1

publications, related, 1-2

R

Ref Adjust (27), B-9

Ref/Fdbk Size (7), B-3

Reference Adjust, selecting, 4-5

Reference/Feedback, 6-5

register object, C-4

regulatory compliance A-1



Index-2 ControlNet Communications Module

NNET A and B status indicators, 8-4

NET A or NET B status indicators, 8-5

network, troubleshooting, 8-1 to 8-10

node address

setting with parameter, 4-2

setting with switches, 3-1

O

objectDPI alarm, C-28

DPI device, C-13

DPI fault, C-25

DPI parameter, C-16

DPI time, C-30

identity, C-2

parameter, C-6

parameter group, C-9

PCCC, C-11

register, C-4

OIM (Operator Interface Module)configuring the module with, 4-2

regulatory compliance, A 1

Reliance Electric, getting assistance

from, 1-2

Reset Module (9), B-4

resetting the module, 4-7

RSLogix 5000 ladder logic

program, 7-17 to 7-18

RSNetWorx configuration, 5-1 to 5-20

RSNetWorx, configuring a network

using, 5-7

S

specifications , A-1

status indicators, 8-1

T

troubleshooting, 8-1 to 8-10

V

VS Utilities, documentation for, 1-2

DIFDocumentation

Improvement Form

Use this form to give us your comments concerning this publication or to report an error

that you have found. For convenience, you may attach copies of the pages with your

comments. After you have completed this form, please return it to:

Reliance Electric

Technical Documentation

P.O. Box 248019

Mayfield Heights, OH 44124-8019

Fax: 440-646-7317



Thank you for your comments.

Publication Name: ControlNet Communications Module

Publication Number: D2-3497 Publication Date: December 2001

Comments:

Your Name: Date:

Company Name: Phone: ( )

Address:

E-mail:

Technical Writing Internal Use

Date: DIF Number:

Follow-Up Action:



Publication D2-3497 - December 2001 2001 Rockwell Automation. All rights reserved. Printed in USA.P/N 194011

Documents

Controlnet Geral