ControlNet Communications Module M/N RECOMM-CNET Instruction Manual D2-3497
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 ControlNet Module Features.......................................... 1-1 1.2 Related Documentation ................................................. 1-2 1.3 Conventions Used in This Manual ................................. 1-2 1.4 Getting Assistance from Reliance Electric..................... 1-2 Chapter 2 Getting Started 2.1 ControlNet Module Components ................................... 2-1 2.2 Required Equipment .....................................................
Chapter 6 PLC-5C Applications 6.1 About I/O Messaging ..................................................... 6-1 6.2 Understanding the I/O Image......................................... 6-2 6.3 Using Logic Command/Status ....................................... 6-4 6.4 Using Reference/Feedback ........................................... 6-5 6.5 Using Datalinks .............................................................. 6-5 6.5.1 Rules for Using Datalinks .................................... 6-5 6.5.
List of Figures Figure 2.1 – Components of the ControlNet Module .................................. 2-1 Figure 3.1 – Setting the Module’s Node Address ....................................... 3-2 Figure 3.2 – DPI Ports and Internal Interface Cables ................................. 3-3 Figure 3.3 – Mounting the Module .............................................................. 3-4 Figure 3.4 – Typical ControlNet Network Wiring......................................... 3-5 Figure 4.
Figure 6.1 – Sample I/O Image with All I/O Enabled................................... 6-3 Figure 6.2 – Sample I/O Image with Only Logic/Reference and Datalink B Enabled ................................................................. 6-4 Figure 6.3 – I/O Messaging......................................................................... 6-8 Figure 6.4 – I/O Messaging (Continued) ..................................................... 6-9 Figure 6.5 – I/O Messaging (Continued) .................................
List of Tables Table 2.1 – Equipment Shipped with the ControlNet Module ................... 2-2 Table 2.2 – Required User-Supplied Equipment ...................................... 2-2 Table 4.1 – Configuration Tools................................................................ 4-1 Table 4.2 – Selections for Drive Response to Communication Fault........ 4-6 Table 4.3 – Fault Configuration Parameters ............................................. 4-7 Table 4.4 – Module Configuration Status Parameters .......
VI ControlNet Communications Module
CHAPTER 1 Introduction The ControlNet module (RECOMM-CNET) is an embedded communication option for DPI AC drives, such as the SP600 drive. The module is mounted in the drive and receives its required power from the drive and from the network. The module can be used with other products that implement DPI, a peripheral communication interface. Refer to the documentation for your product for specific information about how it works with the module.
1.2 Related Documentation Refer to the following related publications as necessary for more information. All of the publications are available from http://www.theautomationbookstore.com. 1.
CHAPTER 2 Getting Started This chapter provides: • • • • 2.1 A description of the ControlNet module components A list of parts shipped with the module A list of user-supplied parts required for installing the module An installation checklist ControlNet Module Components ➊ ➋ ➎ ➌ ➍ ➊ Status Indicators ➋ DPI Connector ➌ Channel A BNC Receptacle Four LEDs that indicate the status of the ControlNet channel(s), DPI, and the module. Refer to chapter 8 for more information.
2.2 Required Equipment Table 2.1 lists the equipment shipped with the ControlNet module. When you unpack the module, verify that the package includes all of these items. Table 2.1 – Equipment Shipped with the ControlNet Module Item Description One RECOMM-CNET ControlNet module A 2.54 cm (1 in) and a 15.24 cm (6 in) Internal Interface cable (only one cable is needed to connect the module to the drive) One grounding wrist strap ControlNet Module User Manual (D2-3497) Table 2.
2.3 Installation Checklist This section is designed to help experienced users start using the ControlNet module. If you are unsure about how to complete a step, refer to the referenced chapter. ✔ Step ❒ 1 Review the safety precautions for the module. Throughout this manual ❒ 2 Verify that the drive is properly installed. SP600 AC Drive User Manual ❒ 3 Install the module. Verify that the drive is not powered.
✔ Step ❒ 8 Action • • 2-4 Refer to Create a ladder logic program. Use a programming tool to create a ladder logic program that enables you to do the following: Chapter 6, PLC-5C Applications Control the module and connected drive. Monitor or configure the drive using Explicit Messages.
CHAPTER 3 Installing the ControlNet Module Chapter 3 provides instructions for installing the module on an SP600 drive. 3.1 Preparing for an Installation Before installing the ControlNet module, verify that you have all requirement equipment. Refer to chapter 2, Getting Started, for a list of equipment. 3.2 Commissioning the Module To commission the module, you must set a unique node address on the network. (Refer to the Glossary for details about node addresses.
Important: The node address must be set before power is applied because the module uses the node address it detects when it first receives power. To change a node address, you must set the new value and then remove and reapply power to or reset the module. 2 2 3 4 1 0 5 9 7 Tens Digit Setting 0 to 99 4 0 6 8 3 1 5 9 6 8 7 Ones Digit Description Node address used by the module if switches are enabled. The default switch setting is 02.
➋ ➊ ControlNet Module SP600 Drive 1-20 HP @ 460 V ➌ SP600 Drive 25-40 HP @ 460 V ➊ ➋ ➌ DPI Connector 15.24 cm (6 in) Internal Interface cable 2.54 cm (1 in) Internal Interface cable Figure 3.2 – DPI Ports and Internal Interface Cables Step 4. For 1-20 HP SP600 drives, fold the Internal Interface cable behind the module and mount the module on the drive using the four captive screws. See figure 3.3.
Important: All screws must be tightened since the module is grounded through a screw. Drive Module Adapter SP600 1-20 HP Drive Internal Interface Cable Folded Behind the Module and in Front of the Drive SP600 Drive 25-40 HP @ 460 V Figure 3.
3.4 Connecting the Module to the Network ! ATTENTION: The SP600 drive may contain high voltages that can cause injury or death. Remove power from the drive, and then verify power has been discharged before installing or removing a module. Failure to observe this precaution could result in severe bodily injury or loss of life. Step 1. Remove power from the drive. Step 2. Use static control precautions. Step 3. Route the ControlNet cable through the bottom of the SP600 drive. (See figure 3.3.
3.5 Applying Power ! 3-6 ATTENTION: Unpredictable operation may occur if parameter settings and switch settings are not compatible with your application. Verify that settings are compatible with your application before applying power to the drive. Failure to observe these precations could result in severe bodily injury of loss of life. Step 1. Close the door or reinstall the cover on the drive. The status indicators can be viewed on the front of the drive after power has been applied. Step 2.
CHAPTER 4 Configuring the ControlNet Module Chapter 4 provides instructions and information for setting the parameters in the module. For a complete list of parameters, refer to Appendix B, ControlNet Module Parameters. For definitions of terms in this chapter, refer to the Glossary. 4.1 Configuration Tools The ControlNet module stores parameters and other information in its own non-volatile memory. Therefore, you must access the module to view and edit its parameters. Table 4.
4.2 Using the LCD OIM to Configure the Module Use the procedure in figure 4.1 to access the parameters on the ControlNet module 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.
4.4 Setting the I/O Configuration The I/O configuration determines the type of data sent to the drive. This is a two-part process: enabling/disabling the data transmitted betweeen the module and the drive, and identifying the data transmitted between the module and the scanner. Step 1. Enable or disable the data transmitted between the module and the drive by setting the bits in DPI I/O Config (13). A “1” enables the I/O. A “0” disables the I/O.
4.5 Selecting Master-Slave A hierarchy determines the type of device with which the module exchanges data. In a Master-Slave hierarchy, a module exchanges data with a scanner. To set a Master-Slave hierarchy Step 1. Enable the desired I/O in DPI I/O Config (13). Refer to figure 4.3. Step 2. Set the bits in the M-S Input (25). This parameter determines the data transmitted from the scanner to the drive. A “1” enables the I/O. A “0” disables the I/O.
The module is ready to receive I/O from the master (i.e., scanner). You must now configure the scanner to recognize and transmit I/O to the module. Refer to chapter 5, RSNetWorx Configuration for PLC-5C Applications. 4.6 Selecting Reference Adjust Reference Adjust is the percent scaling factor for the Reference from the Network and can be set from 0-200%.
4.7.1 Changing the Fault Action Set the values of Comm Flt Action (10) and Idle Flt Action (11) to the desired responses as shown in table 4.2. See figure 4.6 for sample LCD OIM Fault Action screens. Table 4.2 – Selections for Drive Response to Communication Fault Value Action 0 Fault (default) Description 1 Stop 2 Zero Data The drive is sent 0 for output data after a communications disruption. This does not command a stop. 3 Hold Last The drive continues in its present state.
4.7.2 Setting the Fault Configuration Parameters If you set Comm Flt Action (10) or Idle Flt Action (11) to “Send Flt Cfg,” the values in the parameters shown in table 4.3 are sent to the drive after a communications fault and/or idle fault occurs. You must set these parameters to values required by your application. Table 4.3 – Fault Configuration Parameters Parameter Number Name Description 15 Flt Cfg Logic A 16-bit value sent to the drive for Logic Command.
Set Reset Module (9) to Reset Module. See figure 4.7. Port 5 Device RECOMM-CNET Parameter #: 9 Reset Module 1 Reset Module Value 0 1 2 Description Ready (Default) Reset Module Set Defaults Figure 4.7 – Reset Screen on an LCD OIM When you enter 1 (Reset Module), the module will be immediately reset. When you enter 2 (Set Defaults), the module will set all module parameters to their factory-default settings.
Table 4.4 – Module Configuration Status Parameters No. 14 25 26 27 Name and Description Default: DPI I/O Active I/O that the module is actively transmitting. The Bit Values: value of this parameter will usually be equal to the value of parameter 13 - DPI I/O Config.
4-10 ControlNet Communications Module
CHAPTER 5 RSNetWorx Configuration for PLC-5C Applications This chapter provides information for using RSNetWorx for ControlNet to configure a PLC-5C controller to communicate with the RECOMM-CNET ControlNet module. RSNetWorx for ControlNet is a 32-bit Windows application for configuring ControlNet networks. After installing and configuring the module, RSNetWorx is used to configure the controller to recognize and communicate with the module. Before configuring the controller, your PC must be: 5.
5.1.1 Installing and Registering EDS Files in RSNetWorx This section needs to be performed only if new EDS (Electronic Data Sheet) files need to be added to RSNetWorx. The latest EDS files can be obtained at: http://www.reliance.com/prodserv/standriv/networks. In the Tools menu, select EDS Wizard and click Next (figure 5.2). Figure 5.2 – Rockwell Software EDS Wizard Step 1.
Figure 5.3 – EDS Wizard Option Screen Step 2. The EDS Wizard allows for registering single or multiple EDS files. Click Browse and locate where your EDS files are located. In our example (figure 5.4), multiple EDS files are registered from a directory on the hard drive. Figure 5.
Step 3. The EDS Wizard will install and test the EDS files. A green check mark next to each file indicates success. Click Next to continue (figure 5.5). Figure 5.
Step 4. The graphic images for each EDS file are displayed and can be changed if desired. Click Next to continue (figure 5.6). SP600 Figure 5.
Step 5. Click Next to register the EDS files (figure 5.7). You would like to register the following device: SP600 Figure 5.7 – EDS Wizard Final Task Summary Screen Step 6. The EDS files have been installed and registered. Click Finish to return to the main RSNetWorx screen (figure 5.8). Figure 5.
Step 7. Click on the DPI to ControlNet folder in the Hardware window to view the EDS files that have been installed to the RSNetWorx database (figure 5.9). SP600 Figure 5.9 – RSNetWorx for ControlNet DPI to ControlNet Folder Example 5.1.2 Configuring a Network with RSNetWorx The main screen for RSNetWorx consists of several windows: • The Network Usage View displays current and pending values associated with the ControlNet network configuration.
The various views can be displayed or closed by using the View menu. In figure 5.10, the Network Usage, Hardware and Graphic views are displayed while the Message and Favorites views are closed. Step 1. Click the on-line icon to browse the network. Figure 5.10 – RSNetWorx for ControlNet Screen Step 2. 5-8 Select the ControlNet network access method and click OK. In this example, RSNetWorx will use the 1784-PCC to access the ControlNet network (figure 5.11).
. Figure 5.11 – Sample Browse for Network Dialog Box RSNetWorx starts browsing the ControlNet network for nodes and builds the graphic representation of the network (figure 5.12). Figure 5.
Step 3. When the network browse is complete, a graphical view of the network is displayed. In this example (figure 5.13), the ControlNet network consists of a PLC-5C/40C controller, two SP600 drives, and a PC using a 1784-PCC. The symbol indicates the device shown on the network does not exist in the configuration file, but it was found on the network. Double-click on the PLC-5C/40C icon. SP600 SP600 Figure 5.13 – Sample ControlNet Configuration Screen Step 4.
Figure 5.14 – Sample ControlNet Configuration Box Step 5. The ControlNet module must be configured on the ControlNet network so the controller can communicate with it. Click the Edits Enabled check-box (figure 5.15). SP600 SP600 Figure 5.
Step 6. If the On-line / Off-line Mismatch dialog box appears, click OK to use the on-line data (figure 5.16). If prompted to save, save the data (figure 5.17). Figure 5.16 – Online / Offline Mismatch Dialog Box RECOMM-CNET Example.XC Figure 5.17 – Save Data Screen Important: During the save process, RSNetWorx will execute the browse function. Allow RSNetWorx to complete the browse (1-99 nodes), even if you already see the entire network.
.. SP600 SP600 Figure 5.18 – Scanlist Configuration Screen Step 8. Enter the Integer files to be used for ControlNet communications (figure 5.19). In this example, N9 is the Data Input File, N10 is the Data Output File, N11 is the Status File, and N13 is the Configuration File. Doubleclick the Node 2 row (SP600 drive).
SP600 SP600 Figure 5.19 – Integer Files for ControlNet Communications Screen Step 9. Enter the input and output size for the node on the network. The number of words selected depends on the I/O to be communicated with the node. In this example, the Node 2 SP600 is set for all I/O enabled which equates to 10 words of I/O (table 5.1). Table 5.
Note the values in the Input Address and Output Address fields. These are needed to develop a ladder program. Step 10. Enter the desired Requested Packet Interval (RPI) and note the value (figure 5.20). Ensure that this value is equal to or greater than the value that will be set later for Network Update Time (NUT). The Actual Packet Interval (API) may vary from the Requested Packet Interval. SP600 Figure 5.20 – Communicaiton Properties Step 11. Click the Electronic Keying tab.
Figure 5.21 – Connection Properties: Electronic Keying Settings Step 12. Click the Details (figure 5.22) tab. The availability of choosing connection options are determined by the EDS file for the node. Click OK. Figure 5.
Step 13. Repeat steps 9-12 for additional nodes. When complete, all of the nodes should be mapped (figure 5.23). SP600 SP600 Figure 5.23 – ScanList Configuration: Mapped Nodes Step 14. Click File / Save to save the project (figure 5.24). If prompted to optimize and re-write schedule for all connections, click OK. Figure 5.
Step 15. Enter a file name and click Save. The project is now saved for future use. RECOMM-CNET Example.XC Figure 5.25 – Save As File Box 5.1.3 Verifying Network Properties In the Network menu, select Properties to display the ControlNet dialog box (figure 5.26). Verify: • The number in the Max Scheduled Address field is higher than or equal to the highest node number that will perform I/O messaging.
Figure 5.26 – ControlNet Dialog Box Step 16. If a special media configuration is required (e.g., repeater), select the Media Configuration tab (figure 5.27) and make the appropriate changes. Refer to the RSNetWorx on-line help for more information. Figure 5.
Step 17. If desired, select the General tab and enter a name and description for the network (figure 5.28). Click OK. RECOMM-CNET ControlNet demonstration program using two SP600 demo units. Figure 5.28 – ControlNet: General Tab Step 18. In the Network menu, select Save the properties and download them to the PLC. The module(s) are now mapped on the network and the controller will communicate with it.
CHAPTER 6 PLC-5C Applications Chapter 6 provides information and examples that explain how to use I/O Messaging and Explicit Messaging to control, configure, and monitor an SP600 drive using a PLC-5C. ! 6.1 ATTENTION: The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application.
6.2 Understanding the I/O Image The terms input and output are defined from the scanner’s point of view. Therefore, output I/O is data that is output from the scanner and consumed by the ControlNet module. Input I/O is status data that is produced by the module 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 (Ref/Fdbk Size (07)) words and Datalink words used by the drive.
ControlNet Scanner Controller Output Image (Write) DPI Module Word and I/O 0 Logic Command Logic Command 1 Reference 2 Datalink In A1 3 Datalink In A2 4 Datalink In B1 5 Datalink In B2 6 Datalink In C1 7 Datalink In C2 8 Datalink In D1 9 Datalink In D2 Reference Data In A1 Data In A2 Data In B1 Data In B2 Data In C1 Data In C2 Data In D1 Data In D2 Message Handler Input Image (Read) SP600 Drive Message Buffer 0 Logic Status 1 Feedback 2 Datalink Out A1 3 Datalink Out A2 4 Datalink Out B1 5 Datalink
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.4 Using Reference/Feedback The Reference (16 bits or 32 bits) is produced by the controller and consumed by the module. The Feedback (16 bits or 32 bits) is produced by the module and consumed by the controller. The size of the Reference/Feedback is determined by the drive and displayed in Ref/Fdbk Size (07) in the module. Size 16-bit 32-bit 6.5 Valid Values -32768 to 32767 -2147483648 to 2147483647 In I/O Image Example Word 1 Figure 6.1 Word 2 and Word 3 Figure 6.
6.5.2 32-Bit Parameters using 16-Bit Datalinks To read (and/or write) a 32-bit parameter using 16-bit Datalinks, typically both Datalinks (x1 and x2) are set to the 32-bit parameter. For example, to read Elapsed MWh (9) in an SP600 drive, 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.8 MWh is read as a “58” in Datalink A1.
6.6 Function of the Sample Program The program performs the following actions: • • Obtains Logic Status information from the drive. • Sends a Reference to the drive and receives Feedback from the drive. • Sends/Receives Datalink data to/from the drive. Uses the Logic Command to control the drive (for example, start, stop). Module Settings for the Sample Program • • Nodes 2 and 3. See Chapter 5, RSNetWorx Configuration for PLC-5C Applications. Parameter Settings for the Sample Program Table 6.
6.
Operator Clear Faults Pushbutton I:000 Drive Logic Command CLEAR FAULTS N10:0 002 2 3 Operator Fwd / Rev Selector Switch I:000 Drive Logic Command FORWARD N10:0 003 4 3 Operator Fwd / Rev Selector Switch I:000 Drive Logic Command REVERSE N10:0 004 3 Drive READY Status Bit N9:0 5 Operator Drive Ready Status Display O:000 005 0 0 Drive ACTIVE Status Bit N9:0 Operator Drive Active Status Display O:000 006 1 1 Figure 6.
Drive FAULTED Status Bit N9:0 Operator Drive Faulted Status Display O:000 007 2 7 008 009 010 This rung moves the Speed Reference from the operator station to the drive. MOV Move Source I:001 0< Dest N10:1 0< The rung moves the Speed Feedback from the drive to the operator station. MOV Move Source N9:1 0< Dest O:001 0< This rung moves Datalink data (N7) to the drive, where it is moved into parameters. Drive Datalink A1 In COP Copy File Source #N7:0 Dest #N10:2 Length 8 Figure 6.
011 012 This rung moves Datalink data from the drive to file N7. COP Copy File Source Dest Length #N9:2 #N7:10 8 This rung executes the messaging logic. JSR Jump To Subroutine Prog File Number U:3 END 013 Figure 6.
6.8 About Explicit Messaging Explicit Messaging is used to transfer data that does not require continuous updates. With Explicit Messaging, you can configure and monitor a slave device’s parameters on the ControlNet network. 6.8.1 Performing Explicit Messages Important: There are five basic events in the Explicit Messaging process defined below. The details of each step will vary depending on the controller. Refer to the documentation for your controller.
The ControlNet I/O Transfer (CIO) instruction is used to send Explicit Messages. For PLC-5C controllers before Series F Revision C, the available services you should use are Get Attribute Single, Get Attribute All, Set Attribute Single, or Set Attribute All. Series F Revision C (or later) allow for more complex messages using a new Generic Bi-Directional communication command. 6.8.2 Explicit Messaging Examples This rung sends a message to the drive over ControlNet and receives the response from the drive.
Figure 6.
Response Data N14:0 N14:1 N14:2 N14:3 N14:4 N14:5 N14:6 N14:7 N14:8 N14:9 N14:10 N14:11 12 3333 0 11 0 0 10 148 Parameter Number = 12 Value = 333.3VDC (Pad Word) Parameter Number = 11 Value = 0.0Hz (Pad Word) Parameter Number = 10 Value = 14.8Hrs 9 23 Parameter Number = 9 Value = 2.3MWh A Set Attributes Scattered message is used to write multiple parameters that may or may not be in sequential order (figure 6.10).
Set Attributes Scattered Example request and response Data: Request Data N13:0 N13:1 N13:2 N13:3 N13:4 N13:5 N13:6 N13:7 N13:8 N13:9 N13:10 N13:11 45 50 0 44 1740 0 43 600 0 42 16 0 Parameter Number = 45 Value = 0.50HP (Pad Word) Parameter Number = 44 Value = 1740RPM (Pad Word) Parameter Number = 43 Value = 60.0Hz (Pad Word) Parameter Number = 42 Value = 1.
Figure 6.11 – CIO Get Attribute Single Screen Get Attribute Single example response (reading SP600 Parameter 1 in figure 6.11): Response Data N14:0 0 Value = 0.0Hz A Set_Attribute_Single message is used to write a single parameter (figure 6.12). • A Service Code of “10” indicates the Set_Attribute_Single service (see page C-20, Common Services). • An Instance Number of “41” indicates Drive Parameter 41 will be accessed (see page C-16, Instances).
. Figure 6.12 – CIO Set Attribute Single Screen Set Attribute Single example request (writing SP600 parameter 41 in figure 6.12): Request Data N13:0 6-18 2300 Value = 230.
CHAPTER 7 ControlLogix Applications Chapter 7 provides information and examples that explain how to use I/O Messaging and Explicit Messaging to control, configure, and monitor an SP600 drive using a ControlNet scanner module. ! ATTENTION: The examples in this publication are intended solely for purpose of example. There are many variables and requirements with any application.
7.1 Configuring a ControlLogix CNB Scanner Configuring a ControlLogix CNB scanner, and the network, is mainly done using RSLogix 5000 software (figure 7.1). RSNetWorx is still required, but only at the end of the configuration process. Start the RSLogix 5000 software to begin the configuration process. RSLogix 5000 - Example_RECOMM-CNET[1756-L1] _RECOMM-CNET Figure 7.1 – RSLogix 5000: I/O Configuration Selection Step 1. 7-2 Right-click on the I/O Configuration folder and select New Module (figure 7.
RSLogix 5000 - Example_RECOMM-CNET[1756/L1] _RECOMM-CNET Figure 7.2 – RSLogix 5000: New Module Selection Step 2. Select the ControlNet module used by the controller. In this example (figure 7.3), a 1756-CNB Series B ControlNet Bridge is selected. Click OK. Figure 7.
Step 3. Enter a Name, Slot number, and Revision number (figure 7.4). Click Next>. Figure 7.4 – Module Properties: Name Selection Step 4. This step is used to define controller-to-module behavior (figure 7.5). Inhibit Module inhibits/un-inhibits the connection to the module. The Major Fault check-box selects if a failure on the connection of this module causes a major fault on the controller if the connection for the module fails. Click Next>. Figure 7.
Step 5. This window (figure 7.6) is displayed for informational purposes only. Click Next>. Figure 7.6 – Module Properties: Indentification/Status Screen Step 6. This window (figure 7.7) is displayed for informational purposes only. Click Finish>>. Figure 7.
Step 7. The 1756-CNB/B now appears in the I/O Configuration folder (figure 7.8). RSLogix 5000 - Example_RECOMM-CNET[1756-L1] _RECOMM-CNET Figure 7.
Step 8. Right-click on the 1756-CNB and select New Module (figure 7.9). RSLogix 5000 - Example_RECOMM-CNET[1756-L1] _RECOMM-CNET Figure 7.
Step 9. To configure a RECOMM-CNET ControlNet module, select the CONTROLNET-MODULE type (figure 7.10). Click OK. Figure 7.10 – Select Module Type: Generic ControlNet Module Screen Step 10. Enter the Name, Description and Node number (figure 7.11). The Comm Format selects the communication format for the module and must be set to Data-INT. Input Instance is the input connection point for the primary connection. Output Instance is the output connection point for the primary connection.
SP600_02 Figure 7.11 – Module Properties: ControlNet Module Parameters Step 11. The Requested Packet Interval (RPI) schedules the connection to move data to or from the module at least this often or the connection will fail with the RPI Not Valid error. Set this value to 5 ms or greater, and click Next> (figure 7.12). Important: The RPI time must be set greater than or equal to the Network Update Time (NUT). Figure 7.
Step 12. This window (figure 7.13) is for informational purposes only. Click Finish>>. Figure 7.13 – Module Properties: My ControlNet Step 13. The configured node (“SP600_02” in this example) now appears under the 1756-CNB module in the I/O Configuration folder. RSLogix 5000 - Example_RECOMM-CNET [1756-L1] Controller Example_RECOMM-CNET SP600_02 Figure 7.14 – RSLogix: Configure Additional Nodes Screen Step 14. Repeat the previous steps for each additional node you need to configure.
Step 15. In the Data Types folder, click on the Module-Defined sub-folder. When you create a module, module-defined data types and tags are automatically created. These tags allow you to access the Input and Output Data of the module via the controller’s ladder logic. RSLogix 5000 - Example_RECOMM-CNET [1756-L1] Controller Example_RECOMM-CNET RE: RE: RE: SP600_02 Figure 7.15 – RSLogix 5000: Module-Defined Screen Step 16.
Step 17. An Attention symbol is located next to the Node 2 (SP600_02) icon in figure 7.17, which indicates the ControlNet scanner needs to be configured. RSLogix 5000 - Example_RECOMM-CNET [1756-L1] Controller Example - RECOMM-CNET RE: RE: RE: SP600_02 Figure 7.17 – RSLogix: Attention Symbol Step 18. Start RSNetWorx and perform the following: a. Click the On-line icon and browse the network. b. Select Edits Enabled and view the messages in the Message View for completion (figure 7.18).
SP600 Figure 7.
SP600 Figure 7.
Step 19. The Attention symbol on the RSLogix 5000 connection tree will disappear if the network has been configured properly (figure 7.20). You are now ready to develop your ladder logic program. RSLogix 5000 - Example_RECOMM-CNET [1756-L1] Controller Example_RECOMM-CNET RE: RE: RE: SP600 Figure 7.20 – RSLogix 5000: Connection Tree Without Attention Symbol 7.2 Function of the Sample Program The program performs the following actions: • • Obtains Logic Status information from the drive.
Parameter Settings for the Sample Program Table 7.
7.3 RSLogix 5000 Ladder Logic Program This rung determines whether the drive is running, and sets the DriveStatusRunning tag appropriately. DriveInputImage.Data[2].1 DriveStatusRunning This rung determines whether the drive is faulted, and sets the DriveStatusFaulted tag appropriately. DriveInputImage.Data[2].7 DriveStatusFaulted This rung moves the drive's frequency feedback to the DriveFeedback tag.
This rung moves data from the DriveReference tag to the drive where it is used as a frequency reference. COP Copy File Source DriveReference Dest DriveOutputImage.Data[1] Length 1 7 This rung moves Datalink data from the drive. 8 COP Copy File Source DriveInputImage.Data[4] Dest ParameterDataFromDrive[0] Length 8 COP Copy File Source ParameterDataToDrive[0] Dest DriveOutputImage.Data[2]
7.4 About Explicit Messaging Explicit Messaging is used to transfer data that does not require continuous updates. With Explicit Messaging, you can configure and monitor a slave device’s parameters on the ControlNet network. 7.4.1 Performing Explicit Messages Important: There are five basic events in the Explicit Messaging process defined below. The details of each step will vary depending on the controller. Refer to the documentation for your controller.
7.4.2 Explicit Messaging Examples This drive at70ControlNet Address 2.address The data2.sent obtained Thisrung rungsends sendsaaCIP CIPmessage messagetotothetheSP600 PowerFlex drive at ControlNet Theisdata sent is obtained from the MessageSendData tag. The data received is stored in the MessageReplyData tag. This MSG instruction can be configured to send any CIP message. 0 EnableDriveMessage MSG Type - CIP Generic Message Control DriveMessageControl ... EN DN ER (End) Figure 7.
Figure 7.
(Destination) Response Data 0 1 2 3 4 5 6 7 8 9 10 11 12 3333 0 11 0 0 10 148 Parameter Number = 12 Value = 333.3VDC (Pad Word) Parameter Number = 11 Value = 0.0Hz (Pad Word) Parameter Number = 10 Value = 14.8Hrs 9 23 Parameter Number = 9 Value = 2.3MWh A Set _Attributes_Scattered message is used to write multiple parameters that may or may not be in sequential order (figure 7.26). A Service Code of “4C” indicates the Set_Attributes_Scattered service (see page C-20, Object Specific Services).
Set_Attributes_Scattered sample request and response data: (Source) Request Data N13:0 N13:1 N13:2 N13:3 N13:4 N13:5 N13:6 N13:7 N13:8 N13:9 N13:10 N13:11 45 50 0 44 1740 0 43 600 0 42 16 0 Parameter Number = 45 Value = 0.50HP (Pad Word) Parameter Number = 44 Value = 1740RPM (Pad Word) Parameter Number = 43 Value = 60.0Hz (Pad Word) Parameter Number = 42 Value = 1.
. Figure 7.27 – Set_Attribute_Single Message Screen Set_Attribute_Single example (writing SP600 Parameter 45 in figure 7.27 ): Send Data 0 50 Value = 0.50HP A Get_Attribute_Single message is used to read a single parameter (figure 7.28). 7-24 • A Service Code of “E” indicates the Get_Attribute_Single service (see page C-8, Services). • A Class Name of “F” indicates the Parameter Object (see page C-6, Parameter Object).
Figure 7.28 – Get_Attributes_Single Message Screen Get Attributes Single example (reading S600 Parameter 45 in figure 7.28): Reply Data 0 50 ControlLogix Applications Value = 0.
ControlLogix Applications 7-26
CHAPTER 8 Troubleshooting the ControlNet Module and Network Chapter 8 contains information for troubleshooting the ControlNet module and the network. 8.1 Understanding the Status Indicators The ControlNet module has four status indicators. They can be viewed on the module or through the drive cover. (See figure 8.1.) ➀ ➁ ➂ ➃ Status Number Indicator DRIVE ➀ MS ➁ NET A ➂ ➃ NET B ➀ ➁ ➂ ➃ Description DPI Connection Status Module Status ControlNet A Status ControlNet B Status Refer to... Section 8.1.
8.1.1 DRIVE Status Indicator Table 8.1 – DRIVE Status Indicator: State Definitions Status Cause Off The module is not powered or is not connected properly to the drive. • Corrective Action Securely connect the module to the drive using the ribbon cable. • Apply power to the drive. Flashing The module is not • Verify that cables are Red receiving a ping securely connected. message from the • Cycle power to the drive. drive.
8.1.2 MS Status Indicator Table 8.2 – MS Status Indicator: State Definitions Status Off Cause The module is not powered. • • Flashing The module has Red failed the firmware test. Solid Red The module has failed the hardware test. Flashing The module is Green operational but is not transferring I/O data. Solid Green The module is operational and transferring I/O data. • Corrective Action Securely connect the module to the SP600 drive using the ribbon cable. Apply power to the drive and network.
8.1.3 NET A and B Together Table 8.3 – NET A and B Together: State Definitions Status Both LEDs are off Both LEDs are steady red LEDs are alternating red/green LEDs are alternating red/off 8-4 Cause A reset occurred or there is no power. A link interface failed. • Corrective Actions Apply power to the module. • Check media for broken cables, loose connectors, missing terminators, etc. • Power cycle or reset the module. If the problem persists, contact Rockwell Automation support.
8.1.4 NET A and B Independently Table 8.4 – NET A and B Independently: State Definitions Status One channel LED is steady off One channel LED is flashing red/green One channel LED is flashing red/off One channel LED is flashing green/off One channel LED is steady green Cause That channel is disabled or not supported. There is an invalid link configuration for that channel. • Corrective Actions Program the network for redundant media, if required. • Power cycle or reset the module.
8.2 Module Diagnostic Items Table 8.5 lists diagnostic items that can be accessed using VS Utilities software or the LCD OIM. Table 8.5 – Module Diagnostic Items No. Event 1 Common Logic Cmd 2 Prod Logic Cmd 3 4 5 6 7 8 9 10 11 12 13 14 15 16 8-6 Description The current value of the Common Logic Command being transmitted to the host. The current value of the Product-Specific Logic Command being transmitted to the host.
Table 8.5 – Module Diagnostic Items (Continued) No. Event 17 Datalink B1 Out 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Description The current value of Datalink B1 being received from the host. Datalink B2 Out The current value of Datalink B2 being received from the host. Datalink C1 Out The current value of Datalink C1 being received from the host. Datalink C2 Out The current value of Datalink C2 being received from the host. Datalink D1 Out The current value of Datalink D1 being received from the host.
8.3 Viewing and Clearing Events The module 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-CNET module as the selected device to access the event queue.
Table 8.6 – Event Codes and Descriptions Code Event 9 Online @ 500kbps 10 Bad Host Flt 11 Dup.
Table 8.6 – Event Codes and Descriptions Code Event 31 PCCC IO Open 32 PCCC IO Time Flt 33 34 Watchdog T/O Flt EEPROM Init 35 36 37 DPI Fault Clear Normal Startup Manual Reset Description The peripheral has begun receiving PCCC Control messages (the PCCC Control Timeout was previously set to a non-zero value). The peripheral has not received a PCCC Control Message for longer than the PCCC Control Timeout. The software watchdog detects a failure.
APPENDIX A Technical Specifications Communications Network Protocol Data Rates ControlNet 5M baud Drive Protocol Data Rates DPI 125 Kbps or 500 Kbps Electrical Consumption Drive Network 275 mA at 5 VDC supplied through the drive Mechanical Dimensions Height Length Width 16 mm (0.624 in) 103 mm (4 in) 80 mm (3.
A-2 ControlNet Communications Module
APPENDIX B ControlNet Module Parameters The following information is provided for each ControlNet module 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: Module must be reset before parameter value is recognized.
1 DPI Port Range: 0 to 7 Default: 5 Type: Read Only Reset Required: N/A Port to which the module is connected. This will usually be port 5. 2 DPI Data Rate Range: 0 = 125 Kbps 1 = 500 Kbps Default: 0 = 125 Kbps Type: Read Only Reset Required: N/A Data rate used by the drive. This data rate is set in the drive and the module detects it. 3 CN Addr Cfg Range: 1 to 99 Default: 2 Type: Read/Write Reset Required: Yes Configures the network if the Node Address Switches are set to “00.
5 CN Rate Cfg Range: 0 = 5 Mbps Default: 0 = 5 Mbps Type: Read/Write Reset Required: Yes Configures the Network Data Rate. Updates CN Rate Act (6) after a reset. 6 CN Rate Act Range: 0 = 5 Mbps Default: 0 = 5 Mbps Type: Read Only Reset Required: N/A The actual Network Data Rate. 7 Ref/Fdbk Size Range: 0 = 16-bit 1 = 32-bit Default: 0 = 16-bit Type: Read Only Reset Required: N/A The size of the Reference/Feedback. The drive determines the size of the Reference/Feedback.
9 Reset Module Range: 0 = Ready (No action) 1 = Reset Module 2 = Set Defaults (Restores module to factory-default settings) Default: 0 = Ready Type: Read/Write Reset Required: No No action if set to “Ready.” Resets the module if set to “Reset Module.” Restores the module to factory default settings if set to “Set Defaults.” This parameter is a command. It will be reset to “0 = Ready” after the command has been performed.
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 module takes if the module detects that the PLC is set to program mode. This setting is effective only if the I/O that controls the drive is transmitted through the module. ! 12 ATTENTION: Idle Flt Action (11) lets you determine the action of the module and connected Host product if the controller is idle (e.g., in program mode).
13 DPI I/O Cfg Range: See figure B.1. Default: xxx0 0001 Type: Read/Write Reset Required: Yes No t No Used t No Used tU Da sed ta Da link D t Da alink tali C Da nk B ta Cm link A d/R ef Configures the I/O that is transferred through the module. 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.
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. The bit definitions will depend on the product to which the module is connected.
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: • Comm Flt Action (10) is set to Send Flt Cfg and the scanner is put into Program mode. • Idle Flt Action (11) is set to Send Flt Cfg and communications are disrupted. 25 M-S Input Range: See figure B.3.
26 M-S Output Range: See figure B.4. Default: xxx0 0001 Type: Read/Write Reset Required: Yes No t No Used t No Used tU Da sed ta Da link D t Da alink tali C Da nk B ta Cm link A d/R ef Configures the I/O Data to be transferred from the drive to the network. 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.4 – M-S Output (26) 27 Ref Adjust Range: 0.00 to 200.00 Default: 100.
ControlNet Module Parameters B-10
APPENDIX C ControlNet Objects Appendix C presents information about the ControlNet 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, ControlLogix Applications. Class Code Hex. Dec. Refer to Section Identity Object 0x01 1 C.1 Register Object 0x07 7 C.2 Parameter Object 0x0F 15 C.3 Parameter Group Object 0x10 16 C.4 Object PCCC Object 0x67 103 C.
C.1 Identity Object Class Code Hexadecimal Decimal 0x01 1 Instances The number of instances depends on the number of components in the device connected to the module. This number of components can be read in Instance 0, Attribute 2.
Attribute Access ID Rule 7 Get Name Product Name Data Type SHORT_ STRING Description Product name and rating Services Service Code 0x05 0x0E ControlNet Objects Implemented for: Class Instance Service Name Yes Yes Reset Yes Yes Get_Attribute_Single C-3
C.
Instance Attributes Attribute ID Access Rule 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 ARRAY of BITS Data to be transferred 4 Conditional Data 1 1 Data Type Name Description The access rule of Set is optional if attribute 2, Direction = 1.
C.3 Parameter Object Class Code Hexadecimal Decimal 0x0F 15 Instances The number of instances depends on the number of parameters in the DPI drive. The module 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 Set 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= Instance Attributes Attribute Access ID Rule Data Type Name Parameter Value Description 1 1 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 = Supports
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.4 Parameter Group Object Class Code Hexadecimal Decimal 0x10 16 Instances The number of instances depends on the number of groups in the device. A group of module 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 1 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 Value varies based on group instance.
C.5 PCCC Object Class Code Hexadecimal Decimal 0x67 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.6 DPI Device Object Class Code Hexadecimal Decimal 0x92 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 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. 8 Get Configuration Text STRING[16] Text identifying a variation of a family device.
Attribute ID Access Rule 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. 129 Get Customization WORD Revision Number Revision of the customized device.
C.7 DPI Parameter Object Class Code Hexadecimal Decimal 0x93 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 Data Type Description 5 Get First Accessible Parameter 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 11 Get/Set 12 13 Name Data Type Description DPI Link BYTE[3] Link (parameter or function block that is the source of the value) (0 = no link) Get Help Object Instance WORD ID for help text for this parameter 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 22 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.
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.
Format for Set_Attributes_Scattered Service The structure shown below can get up to 22 parameters in a single message. In the Response Message, a parameter number with the high bit set indicates that the associated pad word field contains an error code.
The PLC data in this example is for a Set_Attributes_Scattered of SP600 parameters; Accel Time 1 (140), Decel Time 1 (142), and Jog Speed (100) to a device at node address 1. Request Data for Set_Attributes_Scattered Word Value (hex) 0 008C Parameter Number 140 (8C Hex) 1 0032 Value = 50 (32 hex) = 5.0 seconds 2 0000 3 008E Parameter Number 142 (8E hex) 4 0032 Value = 50 (32 hex) = 5.0 seconds 5 0000 6 0064 Parameter Number 100 (64 hex) 7 0064 Value = 100 (64 hex) = 10.
C.8 DPI Fault Object Class Code Hexadecimal Decimal 0x97 151 Products such as SP600 drives use this object for faults. Modules 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 0x0E Yes Yes Get_Attribute_Single 0x10 Yes Yes Set_Attribute_Single ControlNet Objects Service Name C-27
C.9 DPI Alarm Object Class Code Hexadecimal Decimal 0x98 152 Products such as SP600 drives use this object for alarms or warnings. Modules 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 Full/All Information Data Type 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 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 Reserved Reser
C.10 DPI Time Object Class Code Hexadecimal Decimal 0x9B 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 1 Get 2 Get/Set Name Read Full Timer Text 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 Timer Value LWORD -OR- Elapsed time in milliseconds unless the timer is a real time clock.
C-32 ControlNet Communications Module
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 ControlNet module. If you do not see the Logic Command/Logic Status for the product that you are using, refer to your product’s documentation. D.
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 ControlNet Communications Module
GLOSSARY CAN (Controller Area Network) - A serial bus protocol on which DPI is based. ControlNet - An open producer/consumer communication network, with features such as redundant media and deterministic I/O timing, designed for high-performance or time-critical requirements. controller - Also called programmable logic controller.
Explicit Messaging - Used to transfer data that does not require continuous updates. It is typically used to configure or monitor a device’s parameters on the network. fault action - Determines how the module and connected product act when a communications fault (for example, a cable is disconnected) occurs or when the scanner is switched out of run mode. The former uses a communications fault action, and the latter uses an idle fault action.
module - Devices such as drives, controllers, and computers usually require an module to provide a communication interface between them and a network such as ControlNet. An module 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-CNET ControlNet module is a module that connects SP600 drives to a ControlNet network.
status indicators - LEDs that are used to report the status of the module, network, and drive. They are on the module and can be viewed on the front cover of the drive when the drive is powered. VS Utilities software - A software tool for monitoring and configuring Reliance Electric products and modules. It can be run on computers running Microsoft Windows 95, Windows 98, Windows NT (version 4.0 or greater), Windows Me, Windows 2000, or Windows XP operating systems.
INDEX A E assistance, technical, 1-2 EDS files, 5-2 equipment required for installation, 2-2 events codes and descriptions, 8-8 viewing and clearing, 8-8 examples datalinks, 6-7 Explicit Messaging, 7-20 Explicit Messaging, 6-12, 7-19 C CN Active Cfg (12), B-5 CN Addr Actual (4), B-2 CN Addr Cfg (3), B-2 CN Rate Act (6), B-3 CN Rate Cfg (5), B-3 Comm Flt Action (10), B-4 communications specifications, A-1 configuring the module, 4-1 to 4-9 connecting the module to the drive, 3-2 connecting the module to
M P Master-Slave hierarchy configuring a module for, 4-4 mechanical specifications, A-1 module components, 2-1 configuration, viewing, 4-8 configuring, 4-1 to 4-9 diagnostic items, 8-6 dimensions, A-1 features, 1-1 installing, 3-1 to 3-6 parameters, B-1 to B-9 resetting, 4-7 specifications, A-1 troubleshooting, 8-1 to 8-10 M-S Input (25), B-8 M-S Output (26), B-9 MS status indicator, 8-3 parameter descriptions, B-1 to B-9 parameter group object, C-9 parameter object, C-6 PCCC object, C-11 P-DP Addr Cfg (
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-3497 - December 2001 Copyright © 2001 Rockwell Automation, Inc. All Rights Reserved. Printed in USA.
