DeviceNet Option Board for use with the VSM500 Integrated Drive/Motor Instruction Manual D2-3463
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.
CONTENTS Contents Preface ................................................................................................................................... VII Chapter 1 Getting Started 1.1 Components .................................................................................................... 1-1 1.2 Option Features ............................................................................................... 1-2 1.3 Required Equipment.........................................................
Chapter 6 Using Explicit Messaging 6.1 About Explicit Messaging .................................................................................6-1 6.2 Using Explicit Messaging .................................................................................6-1 6.3 Formatting Explicit Messages ..........................................................................6-2 6.4 Example SLC Ladder Logic Program...............................................................6-3 Chapter 7 Troubleshooting 7.
List of Figures Figure 1.1 – DeviceNet Option Board Components ................................................. 1-1 Figure 2.1 – Removing the Cover............................................................................. 2-2 Figure 2.2 – Mounting the DeviceNet Option Board ................................................. 2-2 Figure 2.3 – Switches on the VSM500 Drive Unit and DeviceNet Option Board...... 2-3 Figure 2.4 – Connecting a 10-Pin Linear Plug to the Cable .....................................
Figure 6.1 – Explicit Message Format.......................................................................6-2 Figure 6.2 – Example SLC Ladder Logic Program ...................................................6-5 Figure 7.1 – VSM500 Integrated Drive/Motor COMM Status Indicator ....................
List of Tables Table 2.1 – Drive Setup Switch 10 Settings ............................................................. 2-3 Table 2.2 – DeviceNet Option Board Switch Settings (Switches 1-6) ...................... 2-4 Table 2.3 – DeviceNet Option Board Switch Settings (Switches 7-8) ...................... 2-4 Table 2.4 – Linear Plug Terminal Connections.........................................................
VI VSM500 DeviceNet Option Board
PREFACE The purpose of this manual is to provide you with information needed to apply the DeviceNet option board to the VSM500 Integrated Drive/Motor. It includes methods for installing, configuring, and troubleshooting this option board. Read this manual in its entirety before installing, operating, or servicing the VSM500 Integrated Drive/Motor with a DeviceNet option board. Audience for this Manual This manual is intended for qualified personnel.
Getting Assistance from Reliance Electric If you have any questions or problems with the products described in this instruction manual, contect your local Reliance Electric sales ofice. For technical assistance, call 1-800-726-8112.
CHAPTER 1 Getting Started This chapter provides an overview of the VSM500 DeviceNet option board and the steps that you need to start using it. 1.1 Components The following figure illustrates some of the DeviceNet option board components. ③ ④ ⑤ ① ⑥ ② Top View # Part Description 1 Access to Unit Switches Rotary switches and DIP switches on the VSM500 unit can be accessed through the holes and underneath the DeviceNet option board. 2 Unit Cable A ribbon cable that connects to the VSM500 unit.
1.2 Option Features The DeviceNet option board supports the following: • Polled I/O, change of state, and cyclic data exchange • Explicit messaging • Explicit Unconnected Message Manager (UCMM) • Autobaud • Self-generating EDS files • Faulted node recovery • Parameters for the VSM500 unit and for the DeviceNet option board 1.3 Required Equipment The following equipment is supplied with the DeviceNet option board.
1.4 Quick Start This quick start is for users who have previously installed and configured a DeviceNet network and Rockwell Automation drives. It may help reduce the time of installation. Because this is a start up guide for experienced users, it does not contain detailed instructions. It does, however, reference other chapters in this manual where detailed information can be found.
1-4 VSM500 DeviceNet Option Board
CHAPTER 2 Installing the DeviceNet Option Board This chapter provides instructions for installing and wiring the DeviceNet option board on the VSM500 Integrated Drive/Motor. Read this chapter and referenced information completely before you attempt to install or configure the DeviceNet option board. Before you apply power, review the attention statements on the inside front cover of this manual. 2.
2.4 Connecting the Option to the VSM500 Unit ! ATTENTION: A VSM500 Integrated Drive/Motor and DeviceNet network may contain voltages that can cause injury or death. Remove power from the VSM500 unit and network, and then verify that bus voltage has discharged to a zero before working on them. Failure to observe these precaution could result in severe bodily injury or loss of life.
Step 6. Before reconnecting the cover (shown in figure 2.5), commission the VSM500 unit and connect it to the network (instructions in sections 2.5 and 2.6). 2.5 Commissioning the VSM500 Unit for DeviceNet ATTENTION: Pen ink or pencil lead may damage the switches on the DeviceNet option board. Do not use a pen or pencil to set the switches. Failure to observe these precaution could result in damage to equipment. ! Step 1. Verify that power has been removed from the VSM500 unit and network. Step 2.
Step 3. On the DeviceNet option board, set switches 6 through 1 to a unique DeviceNet address between 0 and 63. The default switch setting is 63. Table 2.
2.6 Connecting the DeviceNet Option Board and VSM500 Unit to the Network Step 1. Verify that power has been removed from the VSM500 unit and network. Step 2. Connect a DeviceNet cable to the network. Important: Maximum cable length depends on data rate. Refer to the DeviceNet Cable System Planning and Installation Manual. Step 3. Connect a Linear plug to the DeviceNet cable. Red White Bare Blue Black 5 4 3 2 1 Figure 2.4 – Connecting a 10-Pin Linear Plug to the Cable Table 2.
1.46 Nm (13 in-lb) Display Cable Figure 2.5 – Reinstalling the Cover 2.8 Applying Power ! ATTENTION: Unpredictable operation may occur if you fail to verify that connections and switch settings are compatible with your application. Verify that connections and parameter settings are compatible with your application before applying power to the VSM500 unit. Failure to observe this precaution could result in severe bodily injury or loss of life. Step 1. Apply power to the network. Step 2.
CHAPTER 3 Configuring the VSM500 Unit and DeviceNet Option Board This chapter provides information and instructions for configuring the VSM500 Integrated drive/motor and DeviceNet option board to communicate on a DeviceNet network. This chapter does not contain information on all possible configurations. Refer to Appendix B in this manual for a complete list of parameters. Refer to the VSM500 Integrated Drive/Motor User Manual for information on configuring the VSM500 unit.
Figure 3.1 – DeviceNet Driver Selection Dialog Box Step 3. Under Available DeviceNet Drivers, select a DeviceNet driver, and then click OK. The Driver Configuration dialog box appears. Figure 3.2 – Driver Configuration Dialog Box Step 4. Select the appropriate settings for the following: Box Serial Port Setup Baud Rate Node Address Data Rate Description Select the communications port on your computer to which the DeviceNet adapter is connected.
3.3 Creating an EDS File After you go online, you can download an EDS (Electronic Data Sheet) file from any device on the network. An EDS file is a specially formatted ASCII file that provides all the information necessary for a configuration tool such as DeviceNet Manager to access and edit the parameters in a device. To create an EDS file for a VSM500 unit with a DeviceNet option board: Step 1. Select Utilities > Create EDS Stub to display the Create EDS Stub dialog box. Figure 3.
Step 5. Under Select Bitmap for this Device in the Create EDS Stub dialog box (see figure 3.4), click Browse. An Open dialog box appears. Figure 3.6 – Open Dialog Box Step 6. Select the VSM500.bmp in the list box, and then click OK. The Create EDS Stub dialog box reappears. Step 7. Click OK. A DeviceNet Manager message box appears and asks if you want to save the EDS file to the EDS library. Step 8. Click OK to save the EDS file. The EDS Description dialog box appears. Step 9.
Step 2. Double-click the icon for the VSM500 unit. The Device Configuration Enhanced Mode dialog box appears. Figure 3.8 – Device Configuration - Enhanced Mode Dialog Box Parameters for the VSM500 unit and DeviceNet option board are displayed under Parameters. You can either scroll through the parameters in the list, or you can select a specific group of parameters in the Parameter Group box.
Step 2. Type a unique node address, and then click Save to Device. Step 3. Click OK to close the dialog box. Step 4. Reset the DeviceNet option board. The new setting for this parameter will take effect after a reset. See section 3.13 for more information. After setting a new node address, you must scan the network. DeviceNet Manager will then display the new address in the Network Who window (see figure 3.7) and be able to communicate with the drive so that future parameter changes take place. 3.
3.7 Selecting Input and Output Assemblies The VSM500 unit uses Assembly Objects to send data to and from a scanner over an I/O connection. The terms input and output are defined from the scanner’s point of view. An output assembly is the information that is output by the scanner and consumed by the VSM500 unit. An input assembly is the status data that is sent by the VSM500 unit and consumed as input by the scanner. Refer to Chapter 5 for a discussion on control I/O and assemblies.
Figure 3.12 – Modifying the Network Control Parameter Step 2. Select Network, and then click Save to Device. Step 3. Click OK to close the dialog box. 3.9 Enabling Network Speed Reference In order for a scanner to change the speed of the VSM500 unit, the unit must be configured to accept its speed reference from the network. Step 1. In the Device Configuration - Enhanced Mode dialog box (see figure 3.8), double-click parameter 36 [SPEED REF SOURCE].
3.10 Setting the Communications Fault Action The communications fault action determines how the VSM500 unit and DeviceNet option board respond when communications are disrupted (e.g., disconnected cable). By default, the VSM500 unit is faulted and stopped. You can change this setting if your application requires a different setting. ! ATTENTION: Parameter 109 [DNET FAULT MODE] determines the action of the option and connected VSM500 unit if communications are disrupted.
3.11 Setting the Idle Action The idle action determines how the VSM500 unit and DeviceNet option board respond when the scanner is placed in idle/program mode. By default, the VSM500 unit is sent zero data. You can change these settings if your application requires it. ! ATTENTION: Parameter 110 [DNET IDLE MODE] determines the action of the option and connected VSM500 unit if the scanner is placed in idle mode. By default, this parameter sends zero data to the unit.
Figure 3.16 – Modifying the Change of State Mask Step 2. Select the bits (an “X” appears) that you want reviewed for changes, and then click Save to Device. Step 3. Click OK to close the dialog box. 3.13 Resetting the Devicenet Option Board ! ATTENTION: Resetting the option may fault the VSM500 unit, resulting in equipment damage, injury, or death. Ensure that the VSM500 unit can stop safely before resetting it. Failure to observe this precaution could result in severe bodily injury or loss of life.
Step 2. Select Reset DNet, and then click Save to Device. The DeviceNet option board will be reset. To view the new settings in DeviceNet Manager, you may need to scan the network. Step 3. Click OK to close the dialog box.
CHAPTER 4 Configuring a Scanner This chapter provides the procedures that are needed to configure the simple network that is illustrated in figure 4.1. It provides information and instructions for configuring an SLC 500 controller with a 1747-SDN scanner to communicate with a VSM500 Integrated drive/motor using a DeviceNet option board.
4.1 Setting Up the Scan List For the scanner to communicate with a VSM500 unit, the scanner must be configured and the VSM500 unit’s node number must be added to its scan list. Step 1. Go online with DeviceNet Manager. Refer to section 3.2 Step 2. Select Who > Network Who. The Network Who window appears, and DeviceNet Manager scans the network for devices. You can wait for DeviceNet Manager to scan the entire network, or click Stop after it displays your VSM500 unit and scanner. Figure 4.
û Figure 4.4 – 1747-SDN Scan List Editor Dialog Box Step 5. Under Add Devices From, click Who. The Add Devices to Scan List dialog box appears. Figure 4.5 – Add Devices to Scan List Dialog Box Step 6. Drag and drop the icon for the VSM500 unit onto the scanner icon. The VSM500 icon will be outlined with a square. Step 7. Click OK. The Scan List Editor dialog box reappears, and the VSM500 node appears in the scan list.
î î Figure 4.6 – Scan List Editor Dialog Box Step 8. Click the new node to highlight it, and then click Edit I/O Parameters. The Edit Device I/O Parameters dialog box appears. Figure 4.7 – Edit Device I/O Parameters Dialog Box Step 9. Set up the scanner for Polled I/O, Change of State, or Cyclic data exchange.
Figure 4.7 shows an example that uses polled I/O. The Enable box was selected, 4 was typed in the Rx box because Input Assembly 71 is being used, and 4 was typed in the Tx box because Output Assembly 21 is being used. Finally, Every Scan was selected in the Poll Rate box. Step 10. Click OK. A DeviceNet Manager message appears. Figure 4.8 – DeviceNet Manager Message Step 11. Click Yes. The Scan List Editor dialog box reappears. It should have the size of I/O in the RX Size and Tx Size columns. Figure 4.
4.2.1 Mapping the Input I/O Step 1. In the Scan List Editor dialog box (see figure 4.9), click Datatable Map under Scan List Tools. The Datatable Map dialog box appears. ô í û ÷ ü ù ø î Figure 4.10 – Datatable Map Dialog Box Step 2. Next to Display Mode, select Data Entry. A dot appears in the circle. Step 3. Next to Data Map, select Input to map the input data. Step 4. In the Map Data To box, select where the data is to be placed. Step 5.
4.2.2 Mapping the Output I/O Step 1. In the Datatable Map dialog box (see figure 4.11), select Output to map the Output data. A dot appears in the circle. í ô ù ÷ û ø Figure 4.12 – Output Datatable Map Step 2. In the Map Data From box, select from where the data is transmitted. Step 3. In the Map Data To box, select the destination of the data. Step 4. In the O:1 box, type the word where the data will be found. Step 5. In the Bit box, type the bit at which the data starts. Step 6. In the No.
Step 8. Click Close. The Scan List Editor dialog box reappears. Figure 4.14 – Scan List Editor Dialog Box The data transmitted between the VSM500 unit and SLC scanner is now mapped to the scanner. 4.3 Saving the Configuration After creating a configuration, you should download it to the scanner. Step 1. In the Scan List Editor dialog box, click SDN under Save To. The Scan List Editor - Download dialog box appears. Figure 4.15 – Scan List Editor - Download Dialog Box Step 2.
CHAPTER 5 Using I/O Messaging This chapter provides information about using control I/O. It includes information on understanding I/O messaging and assemblies, an example of I/O messaging, and an example SLC ladder logic program. Important: To use control I/O, you must have already configured the VSM500 unit and DeviceNet option (refer to chapter 3) and scanner (refer to chapter 4). 5.
5.
5.3 Example SLC Ladder Logic Program The example program runs the VSM500 unit in the forward and reverse direction. It also provides a speed reference. Note that the scanner must be in Slot 1 of the SLC 500 rack for this example. Enable the 1747-SDN Scanner. 1747-SDN Run Bit O:1 0000 0 1747-SDN This rung clears a fault if the VSM500 unit is faulted.
5-4 VSM500 DeviceNet Option Board
CHAPTER 6 Using Explicit Messaging This chapter provides information about using explicit messaging. It includes information on about using explicit messaging, how to format explicit messages, and an example of an SLC ladder logic program. Important: In order to use explicit messaging, you must have already configured the VSM500 unit and DeviceNet option (see chapter 3) and the scanner (see chapter 4). 6.
6.3 Formatting Explicit Messages There are ten 32-word transaction blocks within the scanner module reserved for explicit message program control. These transaction blocks 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 6.1.
6.4 Example SLC Ladder Logic Program The example ladder logic program (see figure 6.2) can be used to do explicit messaging from an SLC. This ladder program will allow the SLC 500 to use explicit messaging to read and write parameters to a VSM500 Integrated drive/motor. To run the example program: Step 1. Enter data into the program. The request information will be placed in the N10 file. The first word in N10 will be the TXID and command information, which both receive a value of one.
Data Format for a Read and Write Parameter The data in this example is for a VSM500 unit with a DeviceNet option at node address 1. .
Example Ladder Logic Program Note that the scanner must be in Slot 1 of the SLC 500 rack for this example. This rung moves the Explicit Message Request data from the SLC500 processor to the 1747-SDN. Explicit Msg Request enable bit N7:0 0000 0 Generate Explicit Request Only Once. B3:0 OSR 0 Copy Request data from the SLC to the SDN Scanner COP Copy File #N10:0 Source #M0:1.224 Dest 32 Length This rung moves the response data from the 1747-SDN to the SLC500 processor when it is available.
6-6 VSM500 DeviceNet Option Board
CHAPTER 7 Troubleshooting This chapter contains information for diagnosing and correcting potential problems. 7.1 Locating the COMM Status Indicator The VSM500 Integrated drive/motor has a COMM status indicator that you can use to determine the status of the VSM500 unit and DeviceNet communications. COMM Status Indicator Figure 7.
7.2 Understanding the COMM Status Indicator The COMM status indicator provides status information on the DeviceNet option board. Important: When power is first applied to the DeviceNet option board, the COMM status indicator flashes green for 1/4 second, red for 1/4 second, and then turns off while the communication module finishes its initialization. Color State None Red Solid What It Means: The option board is not receiving power from the network.
7.3 Fault Codes When there is a fault, you can view the fault code using the value in parameter 10 [LAST FAULT], the value of Class 0x29 (Control Supervisor Object), Instance 1, Attribute 13 (Fault Code), or the display on the keypad. Fault Codes 1 Parameter Value DeviceNet Display Name 0 0x0000 No Fault 1 0x5300 F.FL Function Loss 2 0x2220 F.OC Over Current Description Normal operation. Open connection on Function Loss control terminal block inputs (terminals 7 and 11). Shaft rotation blocked.
Fault Codes 1 Parameter Value DeviceNet Display Name Description Corrective Action 9 0x6312 F.Id EEPROM Drive Contents of the EEPROM - Reset parameters to default values and ID is corrupted. cycle power. - If fault persists, replace VSM500 unit. 10 0x7700 F.dcn Keypad Keypad cable Remove power from the VSM500 unit. Disconnect disconnected while Check keypad cable connection. Reapply VSM500 unit under power to the VSM500 unit. power. 11 0x7701 F.
7.4 Solving Potential Problems Description Solution Parameters settings are not taking effect, or switch settings are not taking effect. Check the setting of DIP switch 10 on the VSM500 unit (Figure 2.3). If this switch is On, then the VSM500 unit uses the settings of the drive parameters in EEPROM. If it is Off, then the VSM500 unit uses the settings of the DIP switches and rotary switches on the board. Unit uses an incorrect data rate or node address. Troubleshooting 1. Set the switch as desired.
7-6 VSM500 DeviceNet Option Board
APPENDIX A Technical Specifications Electrical Network Supply Voltage: 11 to 25 VDC Power Consumption: 0.5 Watt maximum Node Current Consumption: 40 mA (Use this value to size the network current draw from the power supply.) Environmental Ambient Temperature Operating: 0 to 40 °C (32 to 104 °F) Storage: -40 to 85 °C (-40 to 185 °F) Relative Humidity: 0 to 95% non-condensing Vibration: 1.0 G Operational 2.5 G Non-operational Shock: 15.0 G Operational 30.0 G Non-operational Altitude: 1,000 m (3,300 ft.
A-2 VSM500 DeviceNet Option Board
APPENDIX B Parameters Appendix B contains a list of the parameters in the VSM500 Integrated drive/motor and the DeviceNet option board. B.1 Product Codes and EDS Files Catalog Number Parameters Power Rating (HP) Voltage Motor Frame Product Version Code EDS File 10XS1011 1 115V, 1 Phase 56C Std 137 137.cod/3.eds 10XW1011 1 115V, 1 Phase 56C Loc 138 138.cod/3.eds 11XS1011 1 115V, 1 Phase 143TC Std 139 139.cod/3.eds 11XW1011 1 115V, 1 Phase 143TC Loc 140 140.cod/3.
B.2 Parameter Groups Parameters in the VSM500 Integrated drive/motor are grouped into either the Display group or the Program group. Parameters in the Display group are read only. You can get their values, but you cannot change their values. Parameters in the Program group are read/write. You can get and set their values. When a DeviceNet option board is connected, its parameters are grouped in the DNet Config group. Its parameters are also read/write. Figure B.
B.3 Parameter List # Object Mapping Access Rule1 Name and Description Units/ Range Factory Default Drive Display Parameters 01 0x0F-1-1 Command Frequency Value of the presently selected speed reference. Get 0.1 Hz None 02 0x0F-2-1 Output Frequency Output frequency to the motor. Get 0.1 Hz None 03 0x0F-3-1 Output Voltage Output voltage to the motor. Get 1 Volt None 04 0x0F-4-1 Output Current Output current to the motor. Get 0.
# Object Mapping Access Rule1 Name and Description Units/ Range Factory Default Drive Program Parameters 30 0x0F-30-1 Minimum Frequency Lowest frequency that the drive will output continuously. Its value must be less that parameter 31 - [MAXIMUM FREQUENCY]. Get/ Set2 0 Hz to 60 Hz 31 0x0F-31-1 Maximum Frequency Highest frequency that the drive will output. Its value must be greater that the value of parameter 30 [MINIMUM FREQUENCY].
# Object Mapping Name and Description Access Rule1 Units/ Range Factory Default Drive Program Parameters (continued) 39 0x0F-39-1 Auto Restart Delay Time between restart attempts. Get/ Set 1 Sec. to 5 Sec. 60 Sec. 40 0x0F-40-1 Torque Curve Get/ Type of torque curve used by the VSM500 unit. A variable torque curve Set provides a squared V/Hz curve, 110% electronic thermal overload, and 110% current limit for one minute.
Object Mapping Name and Description Access Rule1 Units/ Range Factory Default Drive Program Parameters (continued) 49 0x0F-49-1 Analog Maximum Get/ The percent of analog input used to represent parameter 31 [MAXIMUM Set2 FREQUENCY]. If the maximum analog input equals maximum frequency, no action is needed.
Object Mapping Name and Description Access Rule1 Units/ Range Factory Default DeviceNet Parameters (continued) 103 0x0F-103-1 NV MAC ID Get/ Node address independent of the node address DIP switches. To use this Set address, set both baud rate switches to On before power up. Changes to this parameter take effect only after power is cycled. 0 to 63 63 104 0x0F-104-1 NV Baud Rate Get/ Baud address independent of the baud rate DIP switches.
Object Mapping Access Rule1 Name and Description Units/ Range Factory Default DeviceNet Parameters (continued) 0 to 71 70 0 to 1 0 Get/ Set 0 to 1 0 Get 0.000 to 10.000 None 108 0x0F-108-1 Input Assembly Get/ The input assembly instance that is used for polled messaging with the Set3 master. The input assembly defines the data format that the drive sends to the master in response to a polled message from the master. This parameter determines the format of data being sent to the master.
Object Mapping Name and Description Access Rule1 Units/ Range Factory Default DeviceNet Parameters (continued) 112 0x0F-112-1 COS Mask A 16-bit mask used to enable automatic change of state messages. A 0 disables the indicated status from causing an automatic message. A 1 enables the status. The mask is applied to the defined input status assembly. The default value is 0xFFFF.
B-10 VSM500 DeviceNet Option Board
APPENDIX C DeviceNet Objects This appendix provides information on the DeviceNet objects supported by the VSM500 Integrated drive/motor for DeviceNet. C.
C.
Instance 2 Attributes: DeviceNet Option Instance Attribute ID Access Rule Name Data Type Value 1 Get Vendor ID UINT 5 2 Get Device Type UINT 12 3 Get Product Code UINT 75 4 Get Revision Major Revision Minor Revision Structure of USINT 1 USINT 7 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 String Length ASCII String Structure of USINT 29 STRING “
C.
C.
C.5 Class Code 0x04 – Assembly Object Class Attributes Attribute ID Access Rule Name Data Type Value 1 Get Revision UINT 2 2 Get Max Instance UINT 106 Instance 1 to 106 Attributes: I/O Instances Attribute ID Access Rule 3 Get Name Data Data Type Min/Max Default Description See instance data format for individual I/O assemblies on pages C-7 to C-9.
Instance Data Format: Output Assemblies Instance 1 Data Format (Basic Contactor Output Assembly) Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 0 Bit 0 Run Instance 2 Data Format (Basic Overload Output Assembly) Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 0 Bit 2 Bit 1 Bit 0 Fault Reset Instance 3 Data Format (Basic Motor Starter Output Assembly) Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 0 Bit 2 Bit 1 Fault Reset Bit 0 Run Instance 4 Data Format (Extended Contactor Output Assembly) Byte Bit
Instance Data Format: Output Assemblies (Continued) Instance 106 Data Format (Preset Control with Speed) Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 0 Bit 2 Bit 1 Fault Reset RunRev 1 Preset 2 2 1 Speed Ref Hz (0.1 Hz) (Low Byte) 3 1 Speed Ref Hz (0.1 Hz) (High Byte)2 Bit 0 RunFwd Preset 1 Preset 0 2 1 If speed references are outside of their min/max limits, the drive ignores them and previous speed reference will be maintained. 0 = 0 Hz, 1200 = 120.0 Hz.
Instance Data Format: Input Assemblies Byte Instance 50 Data Format (Basic Overload/Contactor Input Assembly) Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 0 Byte 0 Byte Bit 0 Faulted Instance 51 Data Format (Extended Overload/Contactor Input Assembly) Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 CtrlFrom Net Faulted Bit 7 0 Bit 6 Instance 52 Basic Motor Control Bit 5 Bit 4 Bit 3 Bit 2 Running1 Bit 1 Bit 0 Faulted/Trip Instance 53 Extended Motor Control 1 (see table for functional assignments)
C.
Instance 2 Attributes: Polled I/O Connection Attribute ID Access Rule Name Data Type Value 1 Get State USINT 0 = Nonexistent 1 = Configuring 3 = Established 4 = Timed out 2 Get Instance Type USINT 1 = I/O Message 3 Get Transport Class Trigger USINT 0x83 4 Get Produced Connection ID UINT 01111xxxxxx xxxxxx = Node Address 5 Get Consumed Connection ID UINT 10xxxxxx101 xxxxxx = Node Address 6 Get Initial Comm.
Instance 4 Attributes: Change of State/Cyclic I/O Message Connection Attribute Access ID Rule Name Data Type Value 1 Get State USINT 0 = Nonexistent 1 = Configuring 3 = Established 4 = Timed out 2 Get Instance Type USINT 1 = I/O Message 3 Get Transport Class Trigger USINT 0x00 = Cyclic, ack inhibited 0x03 = Cyclic 0x10 = COS, ack inhibited 0x13 = COS 4 Get Produced Connection ID UINT 01101xxxxxx xxxxxx = Node Address 5 Get Consumed Connection ID UINT Ack inhibited 0xFFFF Ack enab
Instances 6 through 10: Explicit Message Connections Attribute Access ID Rule Name Data Type Value 1 Get State USINT 0 = Nonexistent 1 = Configuring 3 = Established 4 = Timed out 5 = Deferred delete 2 Get Instance Type USINT 0 = Explicit Message 3 Get Transport Class Trigger USINT 0x83 4 Get Produced Connection ID UINT 11yyyxxxxxx yyy = Group 3 Message ID xxxxxx = Node Address 5 Get Consumed Connection ID UINT 11yyyxxxxxx yyy = Group 3 Message ID xxxxxx = Client Node Address 6
C.
Common Services Service Code 0x01 0x05 0x0E 0x10 0x4B DeviceNet Objects Implemented for Class Instance Yes Yes Yes No Yes Yes No Yes No Yes Service Name Get_Attributes_All Reset Get_Attribute_Single Set_Attribute_Single Get_Enum_String C-15
C.
Instance 2 Attributes: Drive Program Instance Attribute ID DeviceNet Objects Access Rule Name Data Type Value 1 Get Group Name String SHORT_STRING Drive Program 2 Get Number of Members in Group UINT 3 Get 1st Parameter Number in Group UINT 30 4 Get 2nd Parameter Number in Group UINT 31 5 Get 3rd Parameter Number in Group UINT 32 6 Get 4th Parameter Number in Group UINT 33 7 Get 5th Parameter Number in Group UINT 34 8 Get 6th Parameter Number in Group UINT 35 28 9
Instance 3 Attributes: DNet Config Instance Attribute ID Access Rule Name Data Type Value 1 Get Group Name String SHORT_STRING DNet Config 2 Get Number of Members in Group UINT 13 3 Get 1st Parameter Number in Group UINT 101 4 Get 2nd Parameter Number in Group UINT 102 5 Get 3rd Parameter Number in Group UINT 103 6 Get 4th Parameter Number in Group UINT 104 7 Get 5th Parameter Number in Group UINT 105 8 Get 6th Parameter Number in Group UINT 106 9 Get 7th Parame
C.
C.
Attribute Access ID Rule 13 Get 14 Get 15 Get 16 Name Value UINT 0x0000 = No fault 0x1000 = general fault 0x2220 = over current 0x3210 = high bus 0x3220 = low bus (stopped) 0x3221 = low bus (running) 0x4310 = drive overtemp 0x5300 = function loss 0x5301 = tb redundant start 0x6310 = eeprom parameter checksum 0x6311 = devicenet eeprom 0x6312 = eeprom drive id 0x7122 = thermal overload 0x7500 = no devicenet power 0x7501 = devicenet lost i/o connection 0x7502 = devicenet unrecoverable fault 0x7504 =
State Transition Diagram The following State Transition Diagram provides a graphical description of the states and state transitions that are reflected in attribute #6. Non-Existent Switch Power On Ready Switch Power Off Faulted Fault Reset Fault Detected Run Fault Detected Enabled Run Stop Complete No Run Fault Detected Stopping Figure C.1 – State Transition Diagram Run/Stop Event Matrix Attribute 5, NetCtrl, is used to request that Run/Stop events be controlled from the network.
C.
C.
APPENDIX D Glossary Assembly Objects: The DeviceNet Specification defines Assembly Objects as objects that “bind attributes of multiple objects to allow data to or from each object to be sent over a single connection.” The VSM500 unit with a DeviceNet option board uses assembly objects to transmit data to and from a scanner over a control I/O connection. The terms “input” and “output” are defined from the scanner’s point of view. Output assemblies are sent by the scanner and consumed by the unit.
DeviceNet Network: A DeviceNet Network is a producer/consumer Control Area Network (CAN) that connects controllers (e.g., PLCs and SLCs) and devices (e.g., drives and motor starters). Both implicit (control I/O) and explicit (configuration) messages can be transmitted over the network. A DeviceNet network can support a maximum of 64 devices. Each device is assigned a unique node address and transmits data on the network at the same data rate. A cable is used to connect devices on the network.
Electronic Data Sheet (EDS) Files: EDS files are simple text files that are used by network configuration tools, such as DeviceNet Manager and RSNetWorx for DeviceNet, to help you identify products such as VSM500 units and easily commission them on a network. EDS files describe a product device type, revision, and configurable parameters. Explicit Messaging: Explicit messages are used to configure, monitor, and diagnose devices.
Producer/Consumer Network: DeviceNet is a producer/consumer network. On producer/consumer networks, packets are identified by content rather than by an explicit destination. If a node needs the packet, it will accept the identifier and consume the packet. The source therefore sends a packet once and all the nodes consume the same packet if they need it. Data is therefore produced once, regardless of the number of consumers.
INDEX Numerics 10-pin linear plug, 2-5 A AC Drive object, C-23 Accel Time parameter, B-4 accessing parameters, 3-4 to 3-5 Acknowledge Handler object, C-24 adapter, see DeviceNet option board Analog Input parameter, B-3 Analog Maximum parameter, B-6 Analog Minimum parameter, B-5 assemblies definition, D-1 relationship to I/O messaging, 5-1 selecting, 3-7 Assembly object, C-6 Auto Restart Attempts parameter, B-4 Auto Restart Delay parameter, B-4 autobaud, B-7, D-2 B Base Frequency parameter, B-5 Base Voltag
DeviceNet cables, 2-5 definition, D-2 example network, D-2 objects, C-1 to C-24 DeviceNet Configuration dialog box, 3-5 DeviceNet Manager accessing parameters with, 3-4 creating EDS files, 3-3 definition, D-2 going online, 3-1 to 3-2 mapping data in a scanner, 4-5 to 4-7 saving a configuration, 4-8 setting up the scan list, 4-2 to 4-5 DeviceNet object, C-5 DeviceNet option board adding to a scan list, 4-2 to 4-5 components, 1-1 configuring, 3-1 to 3-12 definition, D-2 features, 1-2 installation, 2-1 to 2-6
input I/O illustrated example, 5-2 mapping in the scanner, 4-6 Input Status parameter, B-3 installation applying power, 2-6 commissioning the unit for DeviceNet, 2-3 to 2-4 connecting the cover, 2-5 to 2-6 connecting the option board to the unit, 2-2 connecting to the network, 2-5 DeviceNet option board, 2-1 to 2-6 EMC Directive 89/336/EEC, 2-1 Low Voltage Directive 73/23/EEC, 2-1 preparing, 2-1 IR compensation parameter, B-5 L ladder logic programs example for explicit messaging, 6-3 to 6-5 example for I/
protocol, A-1 Q quick start, 1-4 R reference/feedback definition, D-4 enabling, 3-8 Relay Control paramete,B-4 Reset parameter ,B-9 resetting the option board, 3-11 to 3-12 Reverse Disable parameter, B-5 RSNetWorx for DeviceNet, D-4 Run On Power Up parameter, B-4 S saving the configuration, 4-8 scan list, 4-2 to 4-5 scanner configuring, 4-1–4-8 definition, D-4 explicit messaging, 6-1 ladder logic program, 5-3, 6-3 to 6-5 mapping data in, 4-5 to 4-7 setting up a scan list, 4-2 to 4-5 Slip Compensation par
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-3463- February 2000 Copyright © 2000 Rockwell Automation, Inc. All Rights Reserved. Printed in USA.
