DeviceNet Adapter for use with DPI AC Drives M/N RECOMM-DNET Instruction Manual D2-3478
The information in this manual is subject to change without notice. Throughout this manual, the following notes are used to alert you to safety considerations: ! ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Important: Identifies information that is critical for successful application and understanding of the product. ! ATTENTION: The drive may contain high voltages that can cause injury or death.
CONTENTS Chapter 1 Introduction 1.1 DeviceNet Adapter Features ......................................... 1-1 1.2 Related Documentation ................................................. 1-2 1.3 Conventions Used in This Manual ................................. 1-3 1.4 Getting Assistance from Reliance Electric..................... 1-3 Chapter 2 Getting Started 2.1 DeviceNet Adapter Components ................................... 2-1 2.2 Required Equipment .....................................................
Chapter 5 Configuring the Scanner 5.1 Configuring a Simple Network: An Example .................. 5-1 5.2 Setting Up the Scan List ................................................ 5-2 5.3 Mapping the Drive Data in the Scanner ......................... 5-6 5.3.1 Mapping the Input I/O .......................................... 5-6 5.3.2 Mapping the Output I/O ....................................... 5-7 5.4 Saving the Configuration................................................
Appendix A Technical Specifications .....................................................A-1 Appendix B DeviceNet Adapter Parameters ...........................................B-1 Appendix C DeviceNet Objects ...............................................................C-1 Appendix D Logic Command/Status Words ............................................D-1 Appendix E Master-Slave I/O Configuration............................................E-1 Glossary .................................................
IV DeviceNet Adapter for use with DPI AC Drives
List of Figures Figure 2.1 – Components of the DeviceNet Adapter .................................. 2-1 Figure 3.1 – Setting the Node Address....................................................... 3-2 Figure 3.2 – Setting the Data Rate ............................................................. 3-2 Figure 3.3 – Connecting a 5-Pin Linear Plug to the Cable.......................... 3-3 Figure 3.4 – DPI Ports and Internal Interface Cables ................................. 3-4 Figure 3.
Figure 6.1 – Sample I/O Image with All I/O Enabled................................... 6-2 Figure 6.2 – Sample I/O Image with Only Logic/Reference and Datalink B Enabled .................................................................................. 6-3 Figure 6.3 – Sample ControlLogix Ladder Logic Program .......................... 6-7 Figure 6.4 – Sample ControlLogix Ladder Logic Program (continued).............................................................................. 6-8 Figure 6.
List of Tables Table 2.2 – Equipment Shipped with the DeviceNet Adapter ..................... 2-2 Table 2.3 – Required User-Supplied Equipment ........................................ 2-2 Table 4.1 – Configuration Tools.................................................................. 4-1 Table 4.2 – Procedure for Setting Up RSLinx for RSNetworx for DeviceNet 4-3 Table 4.3 – Viewing Devices on the DeviceNet Network using RSNetWorx. 4-4 Table 4.4 – Procedure for Creating an EDS File .........................
VIII DeviceNet Adapter for use with DPI AC Drives
CHAPTER 1 Introduction This manual provides information about the DeviceNet adapter (RECOMM-DNET) and using it with SP600 drives. The adapter is mounted in the SP600 drive and receives its required power from the drive and from the DeviceNet network. The DeviceNet adapter can be used with other products that implement DPI. DPI is a peripheral communication interface. Refer to the documentation for your product for specific information about how it works with the adapter.
1.2 • Master-slave or peer-to-peer hierarchies that can be set up so that the adapter and connected SP600 drive transmit data to and from either a scanner or another SP600 drive on the network. • User-defined fault actions that determine how the adapter and SP600 drive respond to communication disruptions on the network and controllers in idle mode. • Faulted node recovery is supported.
1.3 • 1747-6.5.2 DeviceNet Scanner Module Configuration Manual • 1747-5.8 DeviceNet Scanner Module Installation Instructions • 1771-6.5.118 DeviceNet Scanner Module Configuration Manual Conventions Used in This Manual The following conventions are used throughout this manual: 1.4 • Menu commands are shown in bold type face and follow the format Menu > Command. For example, if you read “Select File > Open,” you should click the File menu and then click the Open command.
1-4 DeviceNet Adapter for use with DPI AC Drives
CHAPTER 2 Getting Started This chapter provides: • A description of the DeviceNet adapter’s components • A list of parts shipped with the adapter • A list of user-supplied parts required for installing the adapter • An installation checklist 2.1 DeviceNet Adapter Components 1 2 4 3 5 ➀ Status Indicators ➁ DPI Connector ➂ DeviceNet Connector ➃ ➄ Node Address Switches Data Rate Switch Three LEDs that indicate the status of the connected drive, adapter, and network.
2.2 Required Equipment Table 2.2 lists the equipment shipped with the DeviceNet adapter. When you unpack the adapter, verify that the package includes all of these items. Table 2.2 – Equipment Shipped with the DeviceNet Adapter Item Description DeviceNet adapter 2.54 cm (1 in) and 15.
2.3 Installation Checklist This section is designed to help experienced users start using the DeviceNet adapter. If you are unsure how to complete a step, refer to the referenced chapter. ✔ Step ❒ 1 ❒ 2 ❒ 3 ❒ 4 ❒ 5 ❒ 6 Action Review the safety precautions for the adapter. Verify that the SP600 drive is properly installed. Commission the adapter. Set a unique node address and the appropriate data rate using the switches on the adapter.
✔ Step Action Refer to ❒ 7 Apply power to the DeviceNet master and other devices on the network. Verify that the master and network are installed and functioning in accordance with DeviceNet standards, and then apply power to them. ❒ 8 Configure the scanner to communicate with the adapter. Use a network tool such as RSNetWorx for DeviceNet to configure the scanner on the network.
CHAPTER 3 Installing the DeviceNet Adapter Chapter 3 provides instructions for installing the DeviceNet adapter in an SP600 drive. 3.1 Preparing for an Installation Before installing the DeviceNet adapter: • Read the DeviceNet Product Overview Manual, Publication DN-2.5, and the DeviceNet Cable System Planning and Installation Manual, Publication DN-6.7.2. These manuals will provide information on selecting cables, setting up a network, and network basics. • Verify that you have all required equipment.
2 2 3 4 1 0 5 9 4 0 5 9 6 8 7 6 8 Tens Digit Setting 0-63 3 1 7 Ones Digit Description Node address used by the adapter if switches are enabled. The default switch setting is 63. Node address 63 is also the default address used by all uncommissioned devices. Do not use this address as the final adapter address. Important: If the Data Rate switch is set to “PGM” (Program), the adapter will use the setting of DN Addr Cfg (3) for the node address. The default parameter setting is 63.
3.3 Connecting the Adapter to the Network ATTENTION: The drive may contain high voltages that can cause injury or death. Remove all power from the drive, and then verify power has been removed before installing or removing a DeviceNet adapter. Failure to observe these precautions could result in severe bodily injury or loss of life. ! Step 1. Remove power from the network and drive. Step 2. Use static control precautions. Step 3.
3.4 Connecting the Adapter to the Drive Step 1. Remove power from the drive and network. Step 2. Use static control precautions. Step 3. Connect the Internal Interface cable to the DPI port on the drive and then to the DPI connector on the adapter. ➀ ➁ ➂ SP600 AC Drive 1-20 HP @ 460 V DeviceNet Adapter ➃ ➀ ➁ ➂ ➃ SP600 AC Drive 25-40 HP @ 460 V 15.24 cm (6 in.) Internal Interface cable DPI Connector DeviceNet cable 2.54 cm (1 in.) Internal Interface cable Figure 3.
Step 4. Mount the adapter on the drive, using the four captive screws to secure it in place and ground it to the drive. Important: On an SP600 drive, tighten the screw in the lower right hole to ground the adapter. SP600 AC Drive Figure 3.5 – Mounting and Grounding the DeviceNet Adapter 3.5 Applying Power ! ATTENTION: Unpredictable operation may occur if you fail to verify that parameter settings and switch settings are compatible with your application.
Step 5. If the data rate switch is set to “PGM,” use a configuration tool to set the data rate and node address parameters in the adapter (see chapter 4, Configuring the DeviceNet Adapter). If you are using RSNetWorx for DeviceNet, you need to create a point-to-point connection to the drive. Step 6. Apply power to the master device (scanner) and other devices on the network.
CHAPTER 4 Configuring the DeviceNet Adapter Chapter 4 provides instructions and information for setting the parameters in the DeviceNet adapter. For a list of parameters, refer to Appendix B, DeviceNet Adapter Parameters. For definitions of terms in this chapter, refer to the Glossary. 4.1 Configuration Tools The DeviceNet adapter stores parameters and other information in its own non-volatile memory. Therefore, you must access the adapter to view and edit its parameters. Table 4.
4.2 Using the LCD OIM to Configure the Adapter Use the procedure in figure 4.1 to access the parameters on the DeviceNet adapter using the LCD OIM. If you are unfamiliar with the operation of the LCD OIM, refer to the SP600 AC Drive User Manual (D2-3485) for more information.
Table 4.2 – Procedure for Setting Up RSLinx for RSNetworx for DeviceNet Step Action 1. Start RSLinx, and select Communications > Configure Drivers to display the Configure Drivers dialog box. See figure 4.2. 2. In the Available Driver Types box, select DeviceNet Drivers, and then click Add New. The DeviceNet Driver Selection dialog box appears. 3. In the Available DeviceNet Drivers list, select the adapter connected to your computer, and then click Select. A Driver Configuration dialog box appears.
4.3.2 Going Online with RSNetWorx for DeviceNet You can view the devices on a DeviceNet network by going online. A device may appear as an unrecognized device (node 63 in figure 4.3) if RSNetWorx for DeviceNet does not have an Electronic Data Sheet (EDS) file for it. See table 4.3 for the procedure to view devices. Table 4.3 – Viewing Devices on the DeviceNet Network using RSNetWorx Step 1. Action Icon After setting up a driver in RSLinx, start RSNetWorx for DeviceNet. 2. Select Network > Online.
4.3.3 Creating an Electronic Data Sheet (EDS) File If the adapter and drive appear as an unrecognized device, create an EDS file for it using the procedure in table 4.4. Table 4.4 – Procedure for Creating an EDS File Step Action 1. Right-click the “Unrecognized Device” icon, and select Register Device in the menu. The EDS Wizard (figure 4.4) appears. 2. Click Next to display the next step. 3. Select Upload EDS, and then click Next. 4. Type a description (if desired), and then click Next. 5.
Figure 4.4 – EDS Wizard Screen 4.3.4 Accessing and Editing Parameters Parameters in the drive and adapter can be edited with RSNetWorx using the procedure in table 4.5. The adapter parameters are appended to the list of drive parameters. In figure 4.5, for example, the drive has 387 parameters, so parameter 388 is the first adapter parameter. Table 4.5 – Procedure to Access and Edit Parameters Using RSNetWorx Step Action 1.
SP600 Standard Figure 4.5 – Sample SP600 Drive Dialog Box (Drive Parameters Tab) 4.4 Setting the Node Address If the adapter Data Rate switch is set to “PGM,” the value of DN Addr Cfg (3) determines the node address. Step 1. Set the value of DN Addr Cfg (3) to a unique node address. See figure 4.6. Do not use node address 63 because all new devices use it as the default address. Address 63 is also used for Automatic Device Replacement (ADR).
4.5 Setting the Data Rate If the adapter Data Rate switch is set to “PGM,” the value of DN Rate Cfg (05) determines the DeviceNet data rate. See figure 4.7. The Autobaud setting will detect the data rate used on the network if another device is setting the data rate. Your application may require a different setting. Step 1. Set the value of DN Rate Cfg (05) to the data rate at which your network is operating.
Step 3. If you enabled Logic Command/Reference, configure the parameters in the drive to accept the logic and reference from the adapter. For example, set Speed Ref A Sel (90) in an SP600 drive to “Network” so that the drive uses the reference from the adapter. Step 4. If you enabled one or more Datalinks, configure parameters in the drive to determine the source and destination of data in the Datalink(s). Also, ensure that the DeviceNet adapter is the only adapter using the enabled Datalink(s). Step 5.
Step 3. Set the bits in M-S Output (26). This parameter determines the data transmitted from the drive to the scanner. A “1” enables the I/O. A “0” disables the I/O. Bit 0 is the right-most bit. In figure 4.10, it is highlighted and equals “1.” Port 5 Device RECOMM-DNET Parameter #: 26 M-S Output xxxxxxxxxxx0000 1 Status/Fdbk b00 Bit 0 1 2 3 4 5-15 Description Status/Feedback (Default) Datalink A Output Datalink B Output Datalink C Output Datalink D Output Not Used Figure 4.
Port 5 Device RECOMM-DNET Parameter #: 39 Peer A Output 1 Cmd/Ref Value 0 1 2-5 6-9 Description Off (Default) Logic Command/Reference Datalink A, B, C, or D Input Datalink A, B, C, or D Output Figure 4.12 – Peer A Output Screen on an LCD OIM Step 3. If desired, select an additional source of the data to output to the network in Peer B Output (40). See figure 4.13.
4.7.3 Setting an Adapter To Receive Peer-to-Peer Data Step 1. Verify that Peer Inp Enable (37) is set to Off. This parameter must be set to Off while you configure some of the peer input parameters. See figure 4.15. Value 0 1 Port 5 Device RECOMM-DNET Setting Off (Default) On Parameter #: 37 Peer Inp Enable 0 Off Figure 4.15 – Peer Input Enable Screen on an LCD OIM Step 2. Select the node from which you want to receive data in Peer Note to Inp (35).
Step 4. If desired, select the destination of the data to input to the drive in Peer B Input (31). See figure 4.18. Value 0 1 25 Port 5 Device RECOMM-DNET Parameter #: 31 Peer B Input 2 DL A Input Description Off (Default) Logic Command/Reference Datalink A, B, C, or D Input Figure 4.18 – Peer B Input Screen on an LCD OIM Step 5. If you are receiving a Logic Command, set the bits in it that should be used in Peer Cmd Mask (32).
Default = 0.00% Port 5 Device RECOMM-DNET Parameter #: 33 Peer Ref Adjust 0.00 % 0.00 <> 199.99 Figure 4.20 – Peer Reference Adjust Screen on an LCD OIM Step 7. Set Peer Inp Timeout (36) to the maximum amount of time the adapter will wait for a message before timing out. See figure 4.21. Important: This value must be greater than the product of Peer Out Time (42) multiplied by Peer Out Skip (43) in the adapter from which you are receiving I/O. Default = 10.
Port 5 Device RECOMM-DNET Parameter #: 34 Peer Flt Action 0 Fault Value 0 1 2 3 4 Description Fault (Default) Stop Zero Data Hold Last Send Flt Cfg Figure 4.22 – Peer Fault Action Screen on an LCD OIM Step 9. Set Peer Inp Enable (37) to On. The adapter is now configured to receive I/O from the specified node. Ensure that the specified node is configured to transmit I/O. 4.
Port 5 Device Port 5 Device RECOMM-DNET RECOMM-DNET Parameter #: 13 DPI I/O Config xx xx x xx x x xx 0 000 1 Cmd/Ref b00 Parameter #: 26 M-S Output xx xx xx xx x xx 0 000 1 Status/Fdbk b00 Figure 4.23 – I/O Configuration Screens on an LCD OIM Step 2. Set the bits in the Logic Status word that should be checked for changes in COS Status Mask (27). See figure 4.24. The bit definitions for the Status Mask will depend on the drive to which you are connected. Refer to the drive documentation.
4.9 Setting a Fault Action By default, when communications are disrupted (for example, a cable is disconnected) or the scanner is idle, the drive responds by faulting if it is using I/O from the network. You can configure a different response to communication disruptions using Comm Flt Action (10) and a different response to an idle scanner using Idle Flt Action (11).
Port 5 Device Port 5 Device RECOMM-DNET RECOMM-DNET Parameter #: 10 Comm Flt Action 0 Fault Parameter #: 11 Idle Flt Action 0 Fault Figure 4.26 – Fault Action Screens on an LCD OIM Changes to these parameters take effect immediately. A reset is not required. 4.9.2 Setting the Fault Configuration Parameters If you set Comm Flt Action (10), Idle Flt Action (11), or Peer Flt Action (34) to the “Send Flt Cfg,” the values in parameters shown in table 4.
4.10 Resetting the Adapter Changes to switch settings on some adapter parameters require that you reset the adapter before the new settings take effect. You can reset the adapter by cycling power to the drive or by using Reset Module (9). ! ATTENTION: If the adapter is transmitting control I/O to the drive, the drive may fault when you reset the adapter. Determine how your drive will respond before resetting a connected adapter.
4.11 Viewing the Adapter Configuration The parameters in table 4.8 provide information about how the adapter is configured. You can view these parameters at any time. Table 4.8 – Adapter Configuration Status Parameters Number Name Description 01 DPI Port The port on the drive to which the adapter is connected. Usually, it is port 5. 02 DPI Data Rate The data rate used by DPI in the drive. It will be either 125 kbps or 500 kbps. It is set in the drive, and the adapter detects it.
Table 4.8 – Adapter Configuration Status Parameters (Continued) Number Name DPI I/O Active Description The Reference/Feedback and Datalinks used by the adapter. This value is the same as DPI I/O Config (13) unless the parameter was changed and the adapter was not reset.
4-22 DeviceNet Adapter for use with DPI AC Drives
CHAPTER 5 Configuring the Scanner A scanner is a separate module of a multi-module controller or a built-in component of a single-module controller that provides communication with an adapter connected to a network. Chapter 5 provides instructions on how to configure a scanner to communicate with the DeviceNet adapter and the connected SP600 drive. 5.1 Configuring a Simple Network: An Example After the adapter is configured, the connected drive and adapter will be a single node on the network.
5.2 Setting Up the Scan List For the scanner to communicate with a drive, the scanner must be configured and the drive’s node number must be added to its scan list. Step 1. Go online with RSNetWorx for DeviceNet. Refer to section 4.3.2. The devices on the network are displayed in the configuration view as shown in figure 5.2. SP600 AC Drive Figure 5.2 – Configuration View (Graph Tab) Step 2. Right-click the DeviceNet scanner (node 00 in figure 5.2 and select Properties.
. 63 6WDQGDUG Figure 5.3 – Scanlist Page in the Scanner Module Dialog Box Step 7. Under Scanlist, select the drive, and then click Edit I/O Parameters. The Edit I/O Parameters dialog box (figure 5.4) appears. Figure 5.
Step 8. Select the type(s) of data exchange (Polled, Change of State, and /or Cyclic). In our example, we selected Polled. Step 9. Type the number of bytes that are required for your I/O in the Rx Size and Tx Size boxes. The size will depend on the following: • I/O that you enabled in the adapter. This information can be found in DPI I/O Active (14) in the adapter. • Size of the Reference/Feedback and Datalinks in your drive.
Table 5.2 – Host Products Using 32-Bit Reference/Feedback & Datalinks Rx Size Tx Size Logic Command/ Status Reference/ Feedback (32-bit) 8 8 ✔ ✔ 16 16 ✔ ✔ ✔ 24 24 ✔ ✔ ✔ ✔ 32 32 ✔ ✔ ✔ ✔ ✔ 40 40 ✔ ✔ ✔ ✔ ✔ Datalinks (32-bit) A B C D ✔ Step 10. Set the scan rate. See table 5.3. (Click Help for more information.) Table 5.3 – Scan Rates Data Exchange Rate to set Polled Polled Rate Change of State Heartbeat Rate Cyclic Send Rate Step 11. Click OK.
5.3 Mapping the Drive Data in the Scanner Data from I/O messages must be mapped in the scanner. This mapping determines where a ladder logic program can find data that is passed over the network. You must map both the Input I/O and the Output I/O. 5.3.1 Mapping the Input I/O Step 1. In the Scanner Module dialog box, click the Input tab. See figure 5.5. (If necessary, right-click the scanner in the configuration view (figure 5.2) to display this dialog box.
Table 5.4 – Scanner Module Memory Locations Scanner Memory Locations 1747-SDN Discrete or M-File 1756-DNB Assembly Data 1771-SDN Block Xfer 62 – 57 In our example, we are using a 1747-SDN and selected Discrete. Step 3. In the Start Word box, select the word in memory at which the data should start. In our example, we selected 1. Logic Status and Speed Feedback information will be found in I:1.1 and I:1.2, respectively. 5.3.2 Mapping the Output I/O Step 1.
Step 2. In the Memory box, select a location in scanner memory from table 5.5. Table 5.5 – Scanner Module Memory Locations Scanner Memory Locations 1747-SDN Discrete or M-File 1756-DNB Assembly Data 1771-SDN Block Xfer 62 – 57 In our example, we are using a 1747-SDN scanner and selected Discrete. Step 3. In the Start Word box, select the word in memory at which the data should start. In our example, we selected 1. Logic Command and Speed Reference data should be written to O:1.1 and O:1.
CHAPTER 6 Using I/O Messaging Chapter 6 provides information and examples that explain how to use I/O Messaging to control an SP600 drive. ! 6.1 ATTENTION: The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application. Rockwell Automation does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication.
6.2 Understanding the I/O Image The DeviceNet specification requires that the terms input and output be defined from scanner’s point of view. Output I/O is data that is output from the scanner and consumed by the DeviceNet adapter. Input I/O is status data that is produced by the adapter and consumed as input by the scanner. The I/O image table will vary based on the following: • Size (either 16-bit or 32-bit) of the Reference/Feedback word and Datalink words used by the drive.
An image that uses 32-bit words for Reference and Datalinks would change the I/O image in figure 6.1 as follows: Word I/O Word I/O 0 Logic Command/Status 7 - 10 Datalink B 1-2 Reference/Feedback 11 14 Datalink C 3-6 Datalink A 15 18 Datalink D Figure 6.2 illustrates an example of an I/O image that does not use all of the I/O data. Only the Logic Command/Reference and Datalink B are enabled. In this example, the Reference is a 32-bit word, and Datalinks are 16-bit words.
6.3 Using Logic Command/Status When enabled, the Logic Command/Status word is always word 0 in the I/O image. The Logic Command is a 16-bit word of control produced by the scanner and consumed by the adapter. The Logic Status is a 16-bit word of status produced by the adapter and consumed by the scanner. This manual contains the bit definitions for compatible products available at the time of publication in Appendix D, Logic Command/Status Words.
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 (A,B,C,D) are set to the 32-bit parameter. For example, to read Elapsed MWH (9), both Datalink A1 and A2 are set to “9.” Datalink A1 will contain the least significant word (LSW) and Datalink A2 the most significant word (MSW). In this example, the parameter 9 value of 5.8MWh is read as a “58” in Datalink A1.
6.6 Sample Ladder Logic Programs These sample ladder logic programs (figures 6.3 through 6.8) work with SP600 drives. Functions of the Sample Programs The sample programs use an operator station wired to an I/O module in Slot 0, Module Group 0, Rack 0. The operator can perform the following actions: • Obtain status information from the drive. • Use the Logic Command to control the drive (for example, start, stop). • Send a Reference to the drive.
6.6.1 Sample ControlLogix Ladder Logic Program Table 6.1 – Tags for the Sample ControlLogix Program Tag Name Local:1:I Local:1:O DriveCommandClearFault DriveCommandJog DriveCommandStart DriveCommandStop Type DINT[] DINT[] BOOL BOOL BOOL BOOL Tag Name DriveFeedback DriveInputImage DriveOutputImage DriveReference DriveStatusFaulted DriveStatusRunning This rung enables the DeviceNet scanner. Type INT INT[2] INT[2] INT BOOL BOOL Local:1:O.CommandRegister.
DriveCommandClearFault DriveOutputImage[0].3 8 This rung transfers the reference tag to the drive's output image. 9 This rung copies the output image into the 32-bit DeviceNet scanner output structure. The length in this instruction is one because only one 32-bit array element of the destination is used. 10 COP Copy File Source DriveReference Dest DriveOutputImage[1] Length 1 COP Copy File Source DriveOutputImage[0] Dest Local:1:O.Data[0] Length 1 (End) Figure 6.
6.6.2 Sample PLC-5 Ladder Logic Program Table 6.2 – Control File for Block Transfers BT20:0 BT20:1 EN 0 0 ST DN ER CO EW NR TO RW RLEN DLEN FILE ELEM R G S 0 0 0 0 0 0 0 0 62 0 9 0 00 0 0 0 0 0 0 0 0 0 0 62 0 10 0 00 0 0 The scanner gathers drive data via the DeviceNet network. The Block Transfer Read in this rung then moves the drive status data from the scanner to the N9 data file in the PLC.
Operator Input Drive Stop Command Bit I:000 SP600 STOP Command Bit N10:1 0006 11 0 Operator Input Drive Jog Command Bit I:000 SP600 JOG Command Bit N10:1 0007 12 Operator Input Drive Clear Faults Command Bit I:000 2 SP600 CLEAR FAULT Command Bit N10:1 0008 13 0009 The Block Transfer Write in this rung sends the drive command to the scanner and out to the drive via the DeviceNet network.
6.6.3 Sample SLC Ladder Logic Program 0000 The scanner gathers drive status data via the DeviceNet network. The M-File is copied into the N9 data file in the SLC to move the drive status information to a convenient location. SP600 RUNNING Status Bit N9:0 CO P Copy File Source Dest Length #M1:1:0 #N9:0 128 These rungs move the drive status from the N9 data file to an operator display. Operator Display Drive Running Status Bit O:3.0 0001 1 0 1746-O*8 Operator Display Drive Faulted Status Bit O:3.
0007 SP600 CLEAR FAULTS Command Bit N10:0 Operator Input Drive Clear Faults Command Bit I:2.0 3 1746-I*16 3 SP600 REFERENCE Command Word MOV Move Source 0008 Dest This rung enables the scanner. It changes the scanner to RUN mode. N21:0 0< N10:1 0< 1747-SDN Scanner Enable Bit O:1.0 0009 0 1747-SDN 0010 This rung copies the drive command data to the scanner and out to the drive via the DeviceNet network. COP Copy File Source Dest Length #N10:0 #M0:1.0 128 END 0011 Figure 6.
CHAPTER 7 Using Explicit Messaging Chapter 7 provides information and examples that explain how to use Explicit Messaging to monitor and configure the adapter and the connected SP600 drive. ! 7.1 ATTENTION: The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application.
7.2 Formatting Explicit Messages for a ControlLogix Controller ControlLogix scanners accommodate both downloading Explicit Message Requests and uploading Explicit Message Responses. The scanner module can accommodate one request or response for each transaction block. Each transaction block must be formatted as shown in figure 7.1. Refer to table 7.1 for a description of the data that is required in each box (items 1 – 9). 1 2 3 4 7 6 8 5 9 Figure 7.
Table 7.1 – ControlLogix Message Requests and Responses Box Description ➀ Message Type The message type must be CIP Generic. ➁ Service Code The service code is the requested DeviceNet service. Available services depend on the class and instance that you are using. Refer to Appendix C, DeviceNet Objects. ➂ Object Type The object type is a DeviceNet class. Refer to Appendix C, DeviceNet Objects, for available classes. ➃ Object ID The object ID is an instance of a DeviceNet class.
7.3 Formatting Explicit Messages for a PLC or SLC Controller Transaction blocks in PLC and SLC scanners accommodate both downloading Explicit Message Requests and uploading Explicit Message Responses. The scanner module can accommodate one request or response for each transaction block. Each transaction block must be formatted as shown in figure 7.2 or figure 7.3.
Table 7.2 identifies the number of transaction blocks within a scanner that are reserved for Explicit Messaging. Table 7.2 – Number of Transaction Blocks Reserved for Explicit Messaging Scanner No. of Transaction Blocks Words in Each Transaction Block 1747-SDN 10 32 Figure 7.3 1771-SDN 10 32 (two blocks can be moved at once) Figure 7.2 Refer To Table 7.
Table 7.
7.4 Running Explicit Messages There are five basic events in the Explicit Messaging process as shown in figure 7.4. The details of each step will vary depending on the controller (ControlLogix, PLC, or SLC). Refer to the documentation for your controller. Important: There must be a request message and an response message for all Explicit Messages, whether you are reading or writing data.
7.5 ControlLogix Example The data in this example is for an SP600 drive at node address 1. Refer to section 7.2 for a description of the content in each box. Configuration Service Code Object Type Object ID Object Attribute Value e (hex) f (hex) 101 (dec) 1 (hex) Description Get_Attribute_Single Parameter Object Parameter Address Parameter Value Refer to . . . Page C-10 Page C-8 Page C-9 Figure 7.
Configuration Service Code Object Type Object ID Object Attribute Value 10 (hex) f (hex) 101 (dec) 1 (hex) Description Refer to . . . Get_Attribute_Single Parameter Object Parameter Address Parameter Value Page C-10 Page C-8 Page C-9 Figure 7.6 – Data Format for a Read and Write Parameter (2 of 2) Table 7.
7.6 PLC-5 Example Data Format for a Read and Write Parameter The data in this example is for an SP600 drive at node address 1. Refer to section 7.2 for a description of the content of the data file. Table 7.6 – Request Data for Read of Drive Parameter 101 Address Value (hex) Description Refer to . . . N30:0 0101 TXID = 01, Command = 01 (execute) Section 7.3 N30:1 0006 Port = 00, Size = 06 bytes Section 7.
Ladder Logic Program When I:000/17 is set to true, a one-time Block Transfer Write sends data to the scanner. The Move instruction then initializes the first word of the data file that is used by the Block Transfer Read instruction in the next rung. I:000 0000 17 B3:0 ONS 0 BTW Block Transfer Write Module Type 1771-SDN DeviceNet Scanner Module Rack 000 Group 0 Module 0 Control Block BT20:2 Data File N30:0 Length 64 Continuous No MOV Move Source When BT20:2.
7.7 SLC Example Data Format for a Read and Write Parameter The data in this example is for an SP600 drive at node address 1. Refer to section 7.2 for a description of the content of the data file. Table 7.10 – Request Data for Read of Drive Parameter 101 Address Value (hex) Description Refer to . . . N20:10 0101 TXID = 01, Command = 01 (execute) Section 7.3 N20:11 0006 Port = 00, Size = 06 bytes Section 7.
Ladder Logic Program Important: To originate a scanner transaction, use a copy operation to M0:[slot number]:224. Then, use a copy operation to read M1:1.224 for the result. If more than one message is enabled, use the TXID to determine which message you are reading. 0000 Initiate Explicit Message B3:0 When B3:0/0 is set to true, this rung will copy the 32 words of Explicit Message from the buffer at N20:10 to M0-File Explicit Message buffer. The scanner will send the message out over DeviceNet.
7-14 DeviceNet Adapter for use with DPI AC Drives
CHAPTER 8 Troubleshooting the DeviceNet Adapter and Network Chapter 8 contains information for troubleshooting the DeviceNet adapter and network. 8.1 Understanding the Status Indicators The DeviceNet adapter has three status indicators. They can be viewed on the adapter or through the drive cover. See figure 8.1. ➀ ➁ ➂ ➃ ➀ ➁ ➂ Number ➀ ➁ ➂ ➃ Status Indicator Description Refer to ... DRIVE DPI Connection Status Section 8.1.1 MS Adapter Status Section 8.1.2 NET A DeviceNet Status Section 8.
8.1.1 DRIVE Status Indicator Table 8.1 – DRIVE Status Indicator: State Definitions State Off Cause The adapter is not powered or is not connected properly to the drive. Flashing The adapter is not Red receiving a ping message from the drive. Solid The drive has refused Red an I/O connection from the adapter. Another DPI peripheral is using the same DPI port as the adapter. Corrective Action • Securely connect the adapter to the drive using the ribbon cable. • Apply power to the drive.
8.1.2 MS Status Indicator Table 8.2 – MS Status Indicator: State Definitions State Off Cause The adapter is not powered. Corrective Action • Securely connect the adapter to the drive using the ribbon cable. • Apply power to the drive. Flashing The adapter has failed • Verify that the node address Red the firmware test or switch setting is between 0 the node address and 63. switch setting is • Clear faults in the adapter. invalid. • Cycle power to the drive.
8.1.3 NET A Status Indicator Table 8.3 – NET A Status Indicator: State Definitions State Off Cause Corrective Actions The adapter and/or • Securely connect the adapter network is not powered to the drive using the Internal or adapter is not Interface cable and to the connected properly to network using a DeviceNet the network. cable. • Correctly connect the DeviceNet cable to the DeviceNet plug. Flashing Red/ Green Flashing Red Solid Red • Apply power to the drive and network.
8.2 Adapter Diagnostic Items The following diagnostic items can be accessed using VS Utilities. Table 8.4 – Diagnostic Items Accessed Using VS Utilities No. Name Description 1 Common Logic Cmd Current value of the Common Logic Command being transmitted to the host by this peripheral. 2 Prod Logic Cmd Current value of the Product Specific Logic Command being transmitted to the host by this peripheral.
Table 8.4 – Diagnostic Items Accessed Using VS Utilities (Continued) No. Name Description 15 Datalink A1 Out Current value of Datalink A1 being received from the host by this peripheral. 16 Datalink A2 Out Current value of Datalink A2 being received from the host by this peripheral. 17 Datalink B1 Out Current value of Datalink B1 being received from the host by this peripheral. 18 Datalink B2 Out Current value of Datalink B2 being received from the host by this peripheral.
8.3 Viewing and Clearing Events The adapter maintains an event queue that reports the history of its actions. You can view the event queue using an LCD OIM or VS Utilities software. To View and Clear Events Using an LCD OIM Use the procedure shown in figure 8.2 to access the Event Queue using the LCD OIM. Note that you must have the RECOMM-DNET adapter as the selected device to access the event queue.
Table 8.5 – Event Codes and Descriptions (Continued) Code Event Description 6 EEPROM Sum Flt The EEPROM in the adapter is corrupt. 7 Online @ 125 kbps The adapter and DPI product are communicating at 125 kbps. 8 Online @ 500 kbps The adapter and DPI product are communicating at 500 kbps. 9 Bad Host Flt The adapter was connected to an incompatible product. 10 Dup. Port Flt Another peripheral with the same port number is already in use.
Table 8.5 – Event Codes and Descriptions (Continued) Code Event Description 25 Idle I/O Message The DeviceNet scanner was placed in program mode. 26 Peer I/O Timeout The adapter has not received peer I/O from another device on the network within the specified time-out interval. 27 DPI Fault Clear The DPI product issued this because a fault was cleared. 28 DN COS Timeout A change of state (COS) connection has timed out. 29 DN Poll Allocate A polled connection has been allocated.
8-10 DeviceNet Adapter for use with DPI AC Drives
APPENDIX A Technical Specifications Communications Network Protocol Data Rates DeviceNet 125K, 250K, 500K, Autobaud, PGM The PGM (Program) setting on the switch is used to set the data rate using the adapter parameter. Autobaud can be set only if another device on the network is setting a data rate. Electrical Consumption 150 mA at +5 V supplied through the drive 60 mA at +24 V supplied through DeviceNet Use the 60 mA value to size the network current draw from the power supply.
A-2 DeviceNet Adapter for use with DPI AC Drives
APPENDIX B DeviceNet Adapter Parameters The following information is provided for each DeviceNet adapter parameter along with its description: Parameter Number: Unique number assigned to each parameter. Parameter Name: Unique name assigned to each parameter. Range: Predefined parameter limits or selections. Default: Factory default setting. Type: Read Only or Read/Write Reset Required: Adapter must be reset before parameter value is recognized.
1 DPI Port Range: 0 to 7 Default: 0 Type: Read Only Reset Required: N/A Port to which the adapter is connected. This will usually be port 5. 2 DPI Data Rate Range: 0 = 125 kbps 1 = 500 kbps Default: 1 = 500 kbps Type: Read Only Reset Required: N/A Data rate used by the drive. This data rate is set in the drive and the adapter detects it. 3 DN Addr Cfg Range: 0 to 63 Default: 63 Type: Read/Write Reset Required: Yes Node address if the Data Rate switch is set to “PGM” (Program).
5 DN Rate Cfg Range: 0 = 125 kbps 1 = 250 kbps 2 = 500 kbps 3 = Autobaud Default: 3 = Autobaud Type: Read/Write Reset Required: Yes DeviceNet data rate if the data rate switch is set to “PGM” (Program). 6 DN Rate Actual Range: 0 = 125 kpbs 1 = 250 kbps 2 = 500 kbps 3 = Autobaud Default: 0 = 125 kbps Type: Read Only Reset Required: N/A DeviceNet data rate actually used by the adapter.
9 Reset Module Range: 0 = Ready (No action) 1 = Reset Module 2 = Set Defaults (Restores adapter to factory-default settings) Default: 0 = Ready Type: Read/Write Reset Required: No This parameter is a command. It will be reset to 0 = Ready after the command has been performed. ! 10 ATTENTION: If the adapter is transmitting I/O that controls the drive, the drive may fault when you reset the adapter. Determine how your drive will respond before resetting a connected adapter.
11 Idle Flt Action Range: 0 = Fault 1 = Stop 2 = Zero Data 3 = Hold Last 4 = Send Flt Cfg Default: 0 = Fault Type: Read/Write Reset Required: No Sets the action that the adapter and the drive take if the adapter detects that the scanner is idle because the controller was switched to program mode. This setting is effective only if the I/O that controls the drive is transmitted through the adapter.
13 DPI I/O Config Range: See figure B.1. Default: See figure B.1. Type: Read Only Reset Required: N/A No t No Used t No Used tU Da sed ta Da link D t Da alink ta C Da link B ta Cm link A d/R ef I/O that is transferred. x x x 0 0 0 0 1 7 6 5 4 3 2 1 0 1 = I/O Enabled 0 = I/O Disabled x =Not Used Figure B.1 – DPI I/O Config (13) 14 DPI I/O Active Range: See figure B.2. Default: See figure B.2.
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 Sets the Logic Command data that is sent to the drive if the following 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 put into Program or Test mode. • Peer Flt Action (34) is set to Fault Cfg and communications are disrupted.
17 18 19 20 21 22 23 24 Flt Cfg A1 Flt Cfg A2 Flt Cfg B1 Flt Cfg B2 Flt Cfg C1 Flt Cfg C2 Flt Cfg D1 Flt Cfg D2 Range: 0 to 4294967295 Default: 0 Type: Read/Write Reset Required: No Sets the data that is sent to the Datalink in the drive if any of the following is true: • Idle Flt Action (11) is set to Send Flt Cfg and the scanner is put into Program mode. • Comm Flt Action (10) is set to Send Flt Cfg and communications are disrupted.
26 M-S Output Range: 0 = I/O Disabled 1 = I/O Enabled Default: See figure B.4. Type: Read/Write Reset Required: Yes No t No Used t No Used tU DL sed D DL Inp u DL C Inp t B I ut DL npu A t Sta Inpu tus t /Fd bk Master-slave output data. This data is produced by the adapter and consumed by the scanner. x x x 0 0 0 0 1 7 6 5 4 3 2 1 0 1 =I/O Enabled 0 =I/O Disabled x =Not Used Figure B.
29 COS/Cyc Interval Range: 0 to 655.35 seconds Default: 0 seconds Type: Read Only Reset Required: N/A Amount of time that a scanner will wait to check for data in the adapter. When COS (change of state) data exchange has been set up, this is the maximum amount of time between scans. Scans will happen sooner if data changes. When cyclic data exchange has been set up, this interval is the fixed time between scans. This interval is configured in the scanner.
32 Peer Cmd Mask Range: 0 = Ignore bit 1 = Use bit Default: 0000 0000 0000 0000 Type: Read/Write Reset Required: No Mask that is used for the Logic Command word when it is received through peer input. If the mask bit is 0 (Off), the command bit is ignored and not used. If the mask bit is 1 (On), the command bit is checked and used. Important: If the adapter receives a Logic Command from both a master device and a peer device, each command bit must have only one source.
34 Peer Flt Action Range: 0 = Fault 1 = Stop 2 = Zero Data 3 = Hold Last 4 = Fault Cfg Default: 0 = Fault Type: Read/Write Reset Required: No Action that the adapter and drive take if the adapter detects that DeviceNet communications with a peer have been disrupted. This setting is effective only if I/O is transmitted through the adapter. ATTENTION: Peer Flt Action (34) lets you determine the action of the adapter and connected drive if the adapter is unable to communicate with the designated peer.
36 Peer Inp Timeout Range: 0.01 to 180.00 seconds Default: 10.00 seconds Type: Read/Write Reset Required: No Timeout for a Change of State peer-to-peer connection. If the time is reached without the adapter receiving a message, the adapter will respond with the action specified in Peer Flt Action (34).
39 40 Peer A Output Peer B Output Range: 0 = Off 1 = Cmd/Ref 2 = DL A Input 3 = DL B Input 4 = DL C Input 5 = DL D Input 6 = DL A Output 7 = DL B Output 8 = DL C Output 9 = DL D Output Default: 0 = Off Type: Read/Write Reset Required: No Source of peer output data. The adapter transmits this data to the network. Important: These parameters can be changed only when Peer Out Enable (41) is Off. Important: If a 32-bit Datalink or Reference is used in Peer A Output (39), Peer Output (40) cannot be used.
43 Peer Out Skip Range: 1 to 16 Default: 1 Type: Read/Write Reset Required: No Maximum time that a adapter will wait when transmitting data to a peer. The value of Min Peer Tx Time (42) is multiplied by the value of this parameter to set the time.
B-16 DeviceNet Adapter for use with DPI AC Drives
APPENDIX C DeviceNet Objects Appendix C presents information about the DeviceNet objects that can be accessed using Explicit Messages. For information on the format of Explicit Messages and example ladder logic programs, refer to Chapter 7, Using Explicit Messaging. Class Code Hex. Dec. Refer to Section Identity Object 0x01 1 C.1 Connection Object 0x05 5 C.2 Register Object 0x07 7 C.3 Parameter Object 0x0F 15 C.4 Parameter Group Object 0x10 16 C.5 PCCC Object 0x67 103 C.
C.1 Identity Object Class Code Hexadecimal 0x01 Decimal 1 Instances The number of instances depends on the number of components in the device connected to the adapter. This number of components can be read in Instance 0, Attribute 2.
Attribute Access ID Rule Name Data Type Description 5 Get Status WORD Bit 0 = Owned Bit 2 = Configured Bit 10 = Recoverable fault Bit 11 = Unrecoverable fault 6 Get Serial Number UDINT Unique 32-bit number 7 Get Product Name SHORT_ STRING Product name and rating Services Implemented for: Service Code Class Instance Service Name 0x05 Yes No Reset 0x0E Yes Yes Get_Attribute_Single 0x11 Yes N/A Find_Next_Obj_Instance DeviceNet Objects C-3
C.
Attribute ID Access Rule Name Data Type Description 12 Get/Set Watchdog Action USINT 0 = Transition to timed out 1 = Auto delete 2 = Auto reset 13 Get Produced Path Length UINT Number of bytes of data in the produced connection path 14 Get Produced Connection Path ARRAY of UINT Byte stream which defines Application objects whose data is to be produced by this Connection object 15 Get Consumed Path Length UINT Number of bytes of data in the consumed connection path 16 Get Consumed
C.
Instance Attributes Attribute ID Access Rule Data Type Name Description 1 Get Bad Flag BOOL If set to 1, then attribute 4 may contain invalid, bad or otherwise corrupt data. 0 = good 1 = bad 2 Get Direction BOOL Direction of data transfer 0 = Producer Register 1 = Consumer Register 3 Get Size UINT Size of register data in bits 4 Conditional1 Data ARRAY of BITS Data to be transferred 1 The access rule of Set is optional if attribute 2, Direction = 1.
C.4 Parameter Object Class Code Hexadecimal 0x0F Decimal 15 Instances The number of instances depends on the number of parameters in the DPI drive. The adapter parameters are appended to the list of drive parameters. The total number of parameters can be read in Instance 0, Attribute 2.
Attribute Access ID Rule 10 Get Data Type Name Native Language USINT Description 0 = English 1 = French 2 = Spanish 3 = Italian 4 = German 5 = Japanese 6 = Portuguese 7 = Mandarin Chinese 8 = Russian 9 = Dutch Instance Attributes Attribute Access ID Rule Data Type Name Description 1 1 Parameter Value 2 Get Link Path Size USINT 0 = No link specified n = Link specified 3 Get Link Path 4 4 Get Descriptor WORD 0 = False, 1 = True Bit 1 = Supports ENUMs Bit 2 = Supports scaling Bit 3 = S
Attribute Access ID Rule Data Type Name Description 10 Get Minimum Value 1 3 11 Get Maximum Value 1 3 12 Get Default Value 1 3 13 Get Scaling Multiplier UINT 3 14 Get Scaling Divisor UINT 3 15 Get Scaling Base UINT 3 16 Get Scaling Offset UINT 3 17 Get Multiplier Link UINT 3 18 Get Divisor Link UINT 3 19 Get Base Link UINT 3 20 Get Offset Link UINT 3 21 Get Decimal Precision USINT 3 1 Access rule is defined in bit 4 of instance attribute 4.
C.5 Parameter Group Object Class Code Hexadecimal 0x10 Decimal 16 Instances The number of instances depends on the number of groups in the device. A group of adapter parameters is appended to the list of groups in the device. The total number of groups can be read in Instance 0, Attribute 2.
Instance Attributes Attribute Access ID Rule Name Data Type Description Get Group Name String SHORT_ STRING Group name 2 Get Number of Members in Group UINT Number of parameters in group. 3 Get 1st Parameter UINT Number in Group 1 4 Get 2nd Parameter UINT Number in Group 1 n Get UINT 1 1 … 1 Value varies based on group instance.
C.6 PCCC Object Class Code Hexadecimal 0x67 Decimal 103 Instances Not supported. Class Attributes Not supported. Instance Attributes Not supported.
Message Structure for Execute_PCCC Request Name Data Type Description Response Name Data Type Description Length USINT Length of requestor ID Length USINT Length of requestor ID Vendor UINT Vendor number of requestor Vendor UINT Vendor number of requestor Serial Number UDINT ASA serial number of requestor Serial Number UDINT ASA serial number of requestor Other Product Specific Identifier of user, Other task, etc,. on the requestor Product Specific Identifier of user, task, etc.
C.7 DPI Device Object Class Code Hexadecimal 0x92 Decimal 146 Instances The number of instances depends on the number of components in the device. The total number of components can be read in Instance 0, Attribute 4.
Attribute ID Access Rule Name Data Type Description 3 Get Product Series BYTE 1=A 2=B … 4 Get Number of Components BYTE Number of components (e.g., main control board, I/O boards) in the device. 5 Get/Set User Definable Text STRING[16] Text identifying the device with a user-supplied name. 6 Get Status Text STRING[12] Text describing the status of the drive. 7 Get Configuration Code BYTE Identification of variations.
Attribute ID Access Rule Name Data Type Description 19 Get/Set Language Selected BYTE 0 = Default (OIM will prompt at start up) 1 = Language was selected (no prompt) 20 Get/Set CustomerGenerated Firmware STRING[36] GUID (Globally Unique Identifier) identifying customer firmware flashed into the device. 128 Get Customization Code WORD Code identifying the customized device.
Services Implemented for: Service Code C-18 Class Instance Service Name 0x0E Yes Yes Get_Attribute_Single 0x10 Yes Yes Set_Attribute_Single DeviceNet Adapter for use with DPI AC Drives
C.8 DPI Parameter Object Class Code Hexadecimal 0x93 Decimal 147 Instances The number of instances depends on the number of parameters in the device. The total number of parameters can be read in Instance 0, Attribute 0.
Attribute Access ID Rule Name First Accessible Parameter Data Type Description 5 Get 7 Get Class Revision WORD 2 = DPI 8 Get First Parameter WORD Processing Error The first parameter that has been written with a value outside of its range. A “0” indicates no errors. 9 Set Link Command BYTE 0 = No operation 1 = Clear all parameter links (This does not clear links to function blocks.) WORD First parameter available if parameters are protected by passwords.
Attribute Access ID Rule Name Data Type Description 11 Get/Set DPI Link BYTE[3] Link (parameter or function block that is the source of the value) (0 = no link) 12 Get Help Object Instance WORD ID for help text for this parameter 13 Get DPI Read Basic STRUCT of BOOL[32] CONTAINER CONTAINER CONTAINER CONTAINER STRING[16] STRING[4] Descriptor (Refer to pages C22 to C-23) Parameter value Minimum value Maximum value Default value Parameter name Units (e.g.
Descriptor Attributes Bit Name Description 0 Data Type (Bit 1) 1 Data Type (Bit 2) 2 Data Type (Bit 3) 3 Sign Type 0 = Unsigned 1 = Signed 4 Hidden 0 = Visible 1 = Hidden 5 Not a Link Sink 0 = Parameter can sink a link 1 = Parameter cannot sink a link 6 Not Recallable 0 = Recallable from NVS 1 = Not Recallable from NVS 7 ENUM 0 = No ENUM text 1 = ENUM text 8 Writable 0 = Read only 1 = Read/write 9 Not Writable When Enabled 0 = Writable when enabled (e.g.
Bit Name Description 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 link 1 = Parameter cannot be a source for a link 27 Enhanced Bit ENUM Reserved 28 Enhanced ENUM Reserved 29 Not Used Reserved 30 Not Used Reserved 31 Not Used Reserved Formulas for Converting Display Value = ((Internal Valu
Format for Get_Attributes_Scattered Service The structure shown below can get up to eight parameters in a single message. In the Response Message, a parameter number with the high bit set indicates that the associated parameter value field actually contains an error code.
Request Word 0 TXID Response Command TXID 29 Pad Word Not Used 30 Not Used Not Used Word 31 Not Used Not Used Status The PLC data in this example is for a Get_Attributes_Scattered of SP600 parameters; Output Freq (1), Output Current (3), and Ouptut Voltage (6) from a device at node address 1. Request Data for Get_Attributes_Scattered Value Address (hex) Description Refer to ... N30:0 0101 TXID = 01, Command = 01 (execute) Section 7.
Response Data for Get_Attributes_Scattered Value Address (hex) Description Refer To . . . N30:70 0101 TXID = 01, Status = 01 (successful transaction) N30:71 0012 Port = 00, Size = 18 bytes (12 hex) Section 7.3 N30:72 CB01 Service = CB (successful) Section 7.3 Address = 01 (Node Address) Section 7.3 N30:73 0001 Parameter Number 1 N30:74 0258 Value = 600 (258 hex) = 60.0 Hz N30:75 0000 N30:76 0003 Parameter Number 3 N30:77 0001 Value = 1 (1 hex) = 0.
Request Word 0 TXID Response Command TXID Status 12 Parameter Number Parameter Number 13 Parameter Value LSW Pad Word or Error Code 14 Parameter Value MSW Pad Word 15 Parameter Number Parameter Number 16 Parameter Value LSW Pad Word or Error Code 17 Parameter Value MSW Pad Word 18 Parameter Number Parameter Number 19 Parameter Value LSW Pad Word or Error Code 20 Parameter Value MSW Pad Word 21 Parameter Number Parameter Number 22 Parameter Value LSW Pad Word or Error Co
Value Address (hex) Description N30:5 0000 Attribute (not used for this service) N30:6 008C Parameter Number 140 (8C hex) N30:7 0032 Value = 50 (32 hex) = 5.0 seconds N30:8 0000 N30:9 008E Parameter Number 142 (8E hex) N30:10 0032 Value = 50 (32 hex) = 5.0 seconds N30:11 0000 N30:12 0064 Parameter Number 100 (64 hex) N30:13 0064 Value = 100 (64 hex) = 10.0 Hz N30:14 0000 Refer to . . .
C.9 DPI Fault Object Class Code Hexadecimal 0x97 Decimal 151 Products such as SP600 drives use this object for faults. Adapters use this object for events. Instances The number of instances depends on the maximum number of faults or events supported in the queue. The maximum number of faults/events can be read in Instance 0, Attribute 2.
Attribute Access ID Rule Name Data Type Description 6 Get Number of Recorded Faults WORD Number of faults/events in the queue. A “0” indicates the fault queue is empty.
Services Implemented for: Service Code Class Instance Service Name 0x0E Yes Yes Get_Attribute_Single 0x10 Yes Yes Set_Attribute_Single DeviceNet Objects C-31
C.10 DPI Alarm Object Class Code Hexadecimal 0x98 Decimal 152 Products such as SP600 drives use this object for alarms or warnings. Adapters do not support this object. Instances The number of instances depends on the maximum number of alarms supported by the queue. The maximum number of alarms can be read in Instance 0, Attribute 2.
Instance Attributes Attribute Acces ID s Rule 0 Get Name Data Type Full/All Information STRUCT of WORD STRUCT of BYTE BYTE STRING[16] STRUCT of LWORD BOOL[16] WORD CONTAINER[n] 1 Get Basic Information STRUCT of WORD STRUCT of BYTE BYTE STRUCT of LWORD BOOL[16] Description Alarm code Alarm source DPI port DPI Device Object Alarm text Alarm time stamp Timer value (0 = Timer not supported) BOOL[0]: (0 = invalid data, 1 = valid data) BOOL[1]: (0 = elapsed time, 1 = real time) BOOL[2 - 15] Reserved Res
C.11 DPI Time Object Class Code Hexadecimal 0x9B Decimal 155 Instances The number of instances depends on the number of timers in the device. Instance 1 is always reserved for a real time clock although a device may not support it. The total number of timers can be read in Instance 0, Attribute 2.
Instance Attributes Attribute Access ID Rule 0 Get Name Read Full Data Type STRUCT of STRING[16] LWORD or STRUCT BOOL[16] Name of the timer Elapsed time in milliseconds unless timer is a real time clock (See attribute 2) See Attribute 3 STRING[16] Name of the timer 1 Get Timer Text 2 Get/Set Timer Value LWORD -OR- Elapsed time in milliseconds unless the timer is a real time clock.
C-36 DeviceNet Adapter for use with DPI AC Drives
APPENDIX D Logic Command/ Status Words Appendix D provides the definitions of the Logic Command/Logic Status words that are used for some products that can be connected to the DeviceNet adapter. If you do not see the Logic Command/Logic Status for the product that you are using, refer to your product’s documentation.
Logic Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Command x x x x 1 Description Reference Select 000 = No Command 001 = Ref. 1 (Ref A Select) 010 = Reserved 011 = Ref. 3 (Preset 3) 100 = Ref. 4 (Preset 4) 101 = Ref. 5 (Preset 5) 110 = Ref. 6 (Preset 6) 111 = Ref. 7 (Preset 7) MOP Decrement 0 = Not Decrement 1 = Decrement A 0 = Not Stop condition (logic 0) must first be present before a 1 = Start condition will start the drive.
Logic Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 x x x x Logic Command/Status Words Status Reference Description 0000 = Ref A Auto 0001 = Reserved 0010 = Preset 2 Auto 0011 = Preset 3 Auto 0100 = Preset 4 Auto 0101 = Preset 5 Auto 0110 = Preset 6 Auto 0111 = Preset 7 Auto 1000 = Term Blk Manual 1001 = 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 D-3
D-4 DeviceNet Adapter for use with DPI AC Drives
APPENDIX E Master-Slave I/O Configuration Appendix E lists possible configurations for the M-S Input/Output parameters and the possible data size allocation associated with each value depending on the method of data transfer. E.1 M-S Input Parameter Configurations M-S Input (25) has five configurable bits as shown in figure E.1. Datalink B Datalink A Datalink C Cmd/Ref Datalink D xxx0, 0000 0 = Peer or other input 1 = Master-Slave input Figure E.
Table E.
Table E.
Table E.
Table E.
E.2 M-S Output Parameter Configurations M-S Output (26) has five configurable bits as shown in figure E.2. Datalink B Datalink A Datalink C Datalink D Cmd/Ref xxx0, 0000 0 = Peer or other output 1 = Master-Slave output Figure E.2 – Bits and Corresponding I/O When you enable Cmd/Ref or Datalink in the adapter, you must set the corresponding bit in M-S Output (26) if you want the output data to be sent to the scanner or master device. Tables E.3 and E.
Table E.
Table E.
GLOSSARY adapter - Devices such as drives, controllers, and computers usually require an adapter to provide a communication interface between them and a network such as DeviceNet. An adapter reads data on the network and transmits it to the connected device. It also reads data in the device and transmits it to the network. The RECOMM-DNET DeviceNet adapter is an adapter that connects SP600 drives to a DeviceNet network.
controller - Also called programmable logic controller. A solid-state control system that has a user-programmable memory for storage of 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 a central processor, input/output interface, and memory. See also scanner.
General information about DeviceNet and the DeviceNet specification are maintained by the Open DeviceNet Vendor’s Association (ODVA). ODVA is online at http://www.odva.org. DPI - A peripheral communication interface used by various Reliance Electric drives and power products. DPI peripheral - A device that provides an interface between DPI and a network or user. Peripheral devices are also referred to as “adapters” and “modules.” The serial converter and SP600 OIM are examples of DPI peripherals.
heartbeat rate - The heartbeat rate is used in change of state (COS) data exchange. It is associated with producing data once every EPR (Expected Packet Rate) duration. There may be four heartbeats before a time-out happens. hold last - When communications are disrupted (for example, a cable is disconnected), the adapter and SP600 drive can respond by holding last. Hold last results in the drive receiving the last data received via the DeviceNet connection before the disruption.
operator interface module (OIM) - A device that can be used to configure and control a SP600 drive. programmable controller communications command (PCCC) The protocol used by some controllers to communicate with devices on a network. Some software products (for example, VS Utilities) also use PCCC to communicate. peer-to-peer hierarchy - An adapter that is configured for a peerto-peer hierarchy can exchange data with a device on the network that is not a scanner.
scanner - A separate module (of a multi-module controller) or a built-in component (of a single-module controller) that provides communication with adapters connected to a network. See also controller. status indicators - LEDs that are used to report the status of the adapter, network, and drive. They are on the adapter and can be viewed on the front cover of the drive when the drive is powered.
INDEX A adapter adding to the scan list, 5-2 commissioning, 3-1 components, 2-1 configuring, 4-1 to 4-21 connecting to network, 3-3 connecting to the drive, 3-4 definition, Glossary-1 features, 1-1 grounding, 3-5 installation, 3-1 to 3-6 mapping I/O in the scanner, 5-6 mounting, 3-5 parameters, B-1 to B-15 resetting, 4-19 specifications, A-1 tools to configure, 4-1 troubleshooting, 8-1 to 8-9 viewing the active configuration, 4-20 assistance, technical, 1-3 Automatic Device Replacement (ADR) definition, Glo
DeviceNet adapter, see adapter DeviceNet connector, location of, 2-1 dimensions, A-1 DN Active Cfg (12), B-5 DN Addr Actual (4), B-2 DN Addr Cfg (3), B-2 DN Rate Actual (6), B-3 DN Rate Cfg (5), B-3 DPI data rate, 4-20 definition, Glossary-3 peripheral, Glossary-3 products, Glossary-3 DPI alarm object, C-32 DPI connector, location of, 2-1 DPI Data Rate (2), B-2 DPI device object, C-15 DPI fault object, C-29 DPI I/O Active (14), B-6 DPI I/O Config (13), B-6 DPI parameter object, C-19 DPI ports and internal i
indicator DRIVE status, 8-2 MS status, 8-3 NET A status, 8-4 installation checklist, 2-3 commissioning the adapter, 3-1 preparing for, 3-1 L LCD OIM see OIM LEDs, see status indicators logic command/status definition, Glossary-4 in I/O image, 6-2 using, 6-4 M MAC ID, see node address master-slave communications, E-1, E-6 master-slave hierarchy configuring an adapter for, 4-9 definition, Glossary-4 mechanical specifications, A-1 messages, see Explicit Messages mounting the adapter, 3-5 M-S Input (25), B-8
processor, see controller producer/consumer network, Glossary-5 products, see DPI products programmable logic controller, see controller protocol, A-1 publications, related, 1-2 R Ref/Fdbk Size (7), B-3 reference/feedback definition, Glossary-5 in I/O image, 6-2 using, 6-4 register object, C-6 regulatory compliance, A-1 Reliance Electric, getting assistance from, 1-3 Reset Module (9), B-4 resetting an adapter, 4-19 RSLinx, 4-2 RSNetWorx for DeviceNet creating EDS files with, 4-5 definition, Glossary-5 edit
U.S. Drives Technical Support Tel: (1) 262.512.8176, Fax: (1) 262.512.2222, Email: support@drives.ra.rockwell.com, Online: www.ab.com/support/abdrives Publication D2-3478-July 2001 Copyright © 2001 Rockwell Automation, Inc. All Rights Reserved. Printed in USA.
