PowerFlex 1769-SM2 Compact I/O DSI/Modbus Communications Module Firmware Version 1.
Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (Publication SGI-1.1 available from your local Rockwell Automation sales office or online at http:// www.rockwellautomation.com/literature) describes some important differences between solid state equipment and hard-wired electromechanical devices.
Summary of Changes The information below summarizes the changes made to this manual since version 1769-UM013B-EN-P (January 2006): Description Page(s) Changed Figures 1.3 and 1.4 to correctly show the wiring of the RJ45 daisy-chained connectors. 1-4 and 1-5 In the “Compatible Products” section, added the PowerFlex 4M and PowerFlex 40P drives. 1-6 Moved the Module Start-Up Status Indication table from Chapter 1 to Chapter 2 after the “Applying Power” section.
soc-ii
Table of Contents Preface About This Manual Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1 Rockwell Automation Support. . . . . . . . . . . . . . . . . . . . . . . . P-2 Conventions Used in this Manual . . . . . . . . . . . . . . . . . . . . . P-3 Chapter 1 Getting Started Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii Table of Contents Chapter 4 Understanding the I/O Image Module Control Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Module Status Word. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Logic Command/Status . . . . . . . . . . . . . . . . . . . . . . . . Using Reference/Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 5 4-2 4-3 4-4 4-4 Understanding Explicit Messaging Formatting Explicit Messages . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Appendix B iii Module Parameters About Parameter Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 Parameter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 Appendix C CIP/DSI Objects CIP Identity Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3 CIP Parameter Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4 DSI Device Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv Table of Contents
Preface About This Manual Topic Related Documentation Conventions Used in this Manual Rockwell Automation Support Page P-1 P-3 P-2 Related Documentation For: DriveExplorer™ Refer to: http://www.ab.com/drives/driveexplorer, and DriveExplorer online help (1) DriveTools™ SP http://www.ab.
P-2 About This Manual You can view or download publications at http:// literature.rockwellautomation.com. To order paper copies of technical documentation, contact your local Rockwell Automation distributor or sales representative. To find your local Rockwell Automation distributor or sales representative, visit www.rockwellautomation.com/locations. For information such as firmware updates or answers to drive-related questions, go to the Drives Service & Support web site at www.ab.
About This Manual P-3 Conventions Used in this Manual The following conventions are used throughout this manual: • Parameter names are shown in the format Parameter xx - [*]. The xx represents the parameter number. The * represents the parameter name. For example Parameter 01 - [Config Mode]. • Menu commands are shown in bold type face and follow the format Menu > Command. For example, if you read “Select File > Open,” you should click the File menu and then click the Open command.
P-4 Notes: About This Manual
Chapter 1 Getting Started The 1769-SM2 Compact I/O to DSI module provides a Compact I/O connection for PowerFlex 4-Class drives. It can be used with a MicroLogix 1500, CompactLogix, or a remote 1769-based adapter such as the 1769-ADN. Topic Components Features Single Mode vs. Multi-Drive Mode Compatible Products Page 1-1 1-2 1-3 1-6 Topic Required Equipment Safety Precautions Quick Start Status Indicators Page 1-6 1-7 1-9 1-10 Components Figure 1.
1-2 Getting Started Features The 1769-SM2 Compact I/O to DSI module features include: • Three Compact I/O connection channels for PowerFlex 4-Class drives. Up to 3 drives can be connected in Single mode (1 per channel) and up to 15 drives can be connected in Multi-Drive mode (5 per channel).
Getting Started 1-3 Single Mode vs. Multi-Drive Mode Single mode is a one-to-one connection, where a channel is connected to a single PowerFlex 4-Class drive (Figure 1.2). Figure 1.2 Single Mode Wiring Example Powerflex 4-Class Drives 1769-SM2 Module MODULE CH1 CH1 CH2 CH3 CH2 CH3 C H 1 AK-U0-RJ45-TB2P Terminal Block Connector AK-U0-RJ45-TB2P Terminal Block Connector AK-U0-RJ45-TB2P Terminal Block Connector C H 2 C H 3 22-RJ45CBL-C20 Cable, or User-Supplied Wire (recommend Belden No.
1-4 Getting Started Multi-Drive mode enables increased connectivity, where one to five PowerFlex 4-Class drives can be connected per channel. All of the drives are daisy-chained to the 1769-SM2 module over RS-485 as shown in Figure 1.3. Figure 1.3 Multi-Drive Mode Wiring Example Up to 5 PowerFlex 4-Class drives Wiring Tip: The 1769-SM2 has an integral terminating resistor for each channel.
Getting Started 1-5 In Multi-Drive mode, any channel can be configured for “RTU Master” operation (Figure 1.4). This enables connection of up to 31 RTU Slave devices, such as PowerFlex 7-Class drives with 20-COMM-H RS485 HVAC adapters. Figure 1.4 Multi-Drive Mode and Modbus RTU Master Mode Wiring Example CH1 - Multi-Drive Mode (up to 5 PowerFlex 4-Class Drives) Wiring Tip: The 1769-SM2 has an integral terminating resistor for each channel.
1-6 Getting Started Benefits of Multi-Drive mode include: • Lower hardware costs. Only one 1769-SM2 is needed for up to five PowerFlex 4-Class drives per channel (15 total). • Controller can independently control, monitor, and read/write parameters for all five drives on each channel (same functionality as Single mode). The trade-offs of Multi-Drive mode include: • Since the RS-485 ports are used for daisy-chaining the drives, additional DSI peripheral devices cannot be used with the drives.
Getting Started 1-7 User-Supplied Equipment To install and configure the 1769-SM2 module, you must supply: ❑ A small flathead screwdriver ❑ Communications cable 22-RJ45CBL-C20 - orAK-U0-RJ45-TB2P terminal block connectors (one for each channel connection and one for each drive connection) and twisted pair network wiring (Belden No.
1-8 Getting Started ! ! ! ATTENTION: Risk of injury or equipment damage exists. Parameters 04 - [Idle Action 1], 19 - [Idle Action 2], and 34 - [Idle Action 3] let you determine the action of the module and connected drives if communications are disrupted. By default, these parameters fault the drive. You can set these parameters so that the drive continues to run. Precautions should be taken to ensure that the settings of these parameters do not create a risk of injury or equipment damage.
Getting Started 1-9 Quick Start This section is provided to help experienced users quickly start using the 1769-SM2 Compact I/O to DSI module. If you are unsure how to complete a step, refer to the referenced chapter. Step 1 2 3 Action Review the safety precautions for the module. Verify that the drive is properly installed. Install the module. 4 Verify that the controller is not powered. Connect the module to the controller backplane bus.
Getting Started Status Indicators The module uses four status indicators to report its operating status. They can be viewed on the front of the module (Figure 1.5). Figure 1.5 Status Indicators ➊ MODULE MODULE CH1 CH2 CH1 CH3 CH2 CH3 DSI 1-10 C H 1 ➋ C H 2 ➍ ➌ C H 3 Item Name ➊ ➋ ➌ ➍ MODULE CH1 CH2 CH3 After installing the module and applying power to the drive(s), refer to Viewing Start-Up Status Indicators on page 2-15 for possible start-up status indications and their descriptions.
Chapter 2 Installing the Module This chapter provides instructions for installing the 1769-SM2 as an expansion I/O module on MicroLogix 1500 and CompactLogix controllers, or with a remote 1769-based adapter.
2-2 Installing the Module ! ATTENTION: Risk of equipment damage exists. The 1769-SM2 module contains ESD (Electrostatic Discharge) sensitive parts that can be damaged if you do not follow ESD control procedures. Static control precautions are required when handling the module. If you are unfamiliar with static control procedures, refer to Guarding Against Electrostatic Damage (publication 8000-4.5.2). Removing Power ! ATTENTION: Risk of equipment damage exists.
Installing the Module 2-3 Setting the Configuration Mode Switch Before installing the module, make sure its Configuration Mode Switch is correctly set. See Configuration Methods on page 3-3 for details on the Controller and Parameter configuration modes. Then set the Configuration Mode Switch (SW1 in Figure 2.1) for your application. Figure 2.
2-4 Installing the Module Setting the Operating Mode Switch (Single/Multi-Drive) Before installing the module, set its Operating Mode Switch (SW2 in Figure 2.1) for Single or Multi-Drive operation. All channels (CH1, CH2, and CH3) will operate in the selected mode. SW2 Setting 1X (Single mode) back position Description Default setting — sets the 1769-SM2 module for Single mode using a single drive connection (one drive per channel). Important: In Single mode, only one drive can be connected per channel.
Installing the Module 2-5 Assembling the Module to the Controller The 1769-SM2 module can be attached to adjacent controller modules before or after mounting. For mounting instructions, see Panel Mounting on page 2-6 or DIN Rail Mounting on page 2-8. To work with a system that is already mounted, see Replacing the Module within a System on page 2-9. Figure 2.2 and the following procedure describes how to assemble the Compact I/O system. Figure 2.
2-6 Installing the Module 7. Attach an end cap terminator (F) to the last module in the system by using the tongue-and-groove slots as before. 8. Lock the end cap bus terminator (G). Important: A 1769-ECR or 1769-ECL right or left end cap must be used to terminate the end of the serial communication bus. Mounting the Module Minimum Spacing Maintain spacing from enclosure walls, wireways, adjacent equipment, etc. Allow 50 mm (2 in.
Installing the Module 2-7 Panel Mounting Using the Dimensional Drawing NOTE: All dimensions are in mm (inches). Hole spacing tolerance is ±0.4 mm (0.016 in.). Figure 2.3 1769-SM2 Module with MicroLogix 1500 Base Unit and Processor 168 mm (6.62 in) 35 mm (1.38 in) 35 mm (1.38 in) DPI / SCANport 118 mm (4.65 in) 59 mm (2.32 in) 59 mm (2.32 in) 122.6 mm (4.83 in) 132 mm (5.19 in) 147 mm (5.79 in) MODULE CH1 CH2 CH3 C H 1 C H 2 C H 3 13.5 mm (0.53 in) DIN Rail Center Line 28.5 mm (1.
Installing the Module Figure 2.5 1769-SM2 Module with Remote 1769-Based Adapter NS DIAG 70 mm (2.76 in) 35 mm 35 mm (1.38 in) (1.38 in) 35 mm (1.38 in) 35 mm (1.38 in) 28.5 mm (1.12 in) MODULE CH1 CH2 CH3 C H 1 C H 2 C H 3 DIN Rail Center Line 147.4 mm (5.81 in) 59 mm 59 mm (2.32 in) (2.32 in) 118 mm (4.65 in) 122.6 mm (4.83 in) MS IO 35 mm (1.38 in) 35 mm (1.38 in) DPI / SCANport 50 mm (1.97 in) 40 mm (1.58 in) Mounting Hole Dimension 132 mm (5.19 in) 2-8 14.7 mm (0.
Installing the Module 2-9 Replacing the Module within a System The 1769-SM2 module can be replaced while the system is mounted to a panel (or DIN rail). ! ATTENTION: Risk of equipment damage exists. Remove power before installing or removing the 1769-SM2 module. When you install or remove the module with power applied, an electrical arc may occur.
2-10 Installing the Module 8. Connect the 1769-SM2 module and adjacent modules together by locking (fully left) the bus levers on the 1769-SM2 module and the right-side adjacent module. 9. Replace the mounting screws (or snap the module onto the DIN rail). 10. Plug the appropriate communications cable into its respective port on the 1769-SM2 module. 11. Restore 1769-SM2 module configuration using an appropriate configuration tool.
Installing the Module 2-11 When connecting a drive to the channel port using 22-RJ45CBL-C20 communications cable, the above drive parameters do not require configuration because the drive senses that a DSI peripheral is connected and it ignores these parameter settings.
Installing the Module Grounding the Module The 1769-SM2 module is intended to be mounted to a well-grounded mounting surface such as a metal panel. Additional grounding connections from the module’s mounting tabs or DIN rail (if used) are not required unless the mounting surface cannot be grounded. Refer to Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1, for additional information.
Installing the Module 2-13 Unshielded Connector Grounding Requirements When using twisted pair network wiring with unshielded AK-U0-RJ45-TB2P connectors, ground the RJ45 socket on the drive by connecting the drive chassis ground power terminal to the I/O block shield terminal.
2-14 Installing the Module Network Cable Strain Relief Some type of strain relief should be provided for the communication cables within 12 inches (305 mm) of the 1769-SM2 module. This may include wireways, cable ties, panel mounted strain reliefs, or some other appropriate strain relief device. Applying Power ! ATTENTION: Risk of equipment damage, injury, or death exists. Unpredictable operation may occur if you fail to verify that parameter settings are compatible with your application.
Installing the Module 2-15 Viewing Start-Up Status Indicators Status indicators for the communication module can be viewed on the front of the module (Figure 2.8) after power has been applied. Possible start-up status indications are shown in Table 2.A. Figure 2.8 Module Status Indictors ➊ MODULE MODULE CH2 CH1 CH3 CH2 CH3 DSI CH1 C H 1 ➋ C H 2 ➍ ➌ C H 3 Table 2.A Module Start-Up Status Indications Item ➊ ➋ ➌ ➍ (1) Status Status(1) Description Indicator MODULE Green Normal Operation.
2-16 Notes: Installing the Module
Chapter 3 Configuring the Module This chapter provides instructions and information for setting the parameters in the 1769-SM2 module.
3-2 Configuring the Module Multi-Drive Mode When the module is in Multi-Drive mode, the I/O image is comprised of a maximum of 31 words (Table 3.B). Table 3.
Configuring the Module 3-3 Configuration Methods The 1769-SM2 module has two methods of configuration, which are determined by the Configuration Mode Switch (SW1 in Figure 2.1): • Controller mode—The 1769-SM2 uses the configuration data downloaded from the controller on power-up and when the controller is placed in run mode. The data is configured using RSLogix 500, RSLogix 5000 or RSNetWorx for DeviceNet. • Parameter mode—The 1769-SM2 uses its internal parameter settings to configure the module.
3-4 Configuring the Module The configuration data directly correlates to the module parameters. Refer to Appendix B for more information. Entering MicroLogix 1500 Configuration Data Using RSLogix 500 Before v6.30 Earlier versions of RSLogix 500 can be used, but the configuration data must be entered in raw form in a Data Config table following the format in Table 3.C. However, RSLogix 500 v6.
Configuring the Module 3-5 2. Enter the Series letter of the 1769-SM2, which can be determined by checking the data nameplate label on the module (item 9 in Figure 1.1). The I/O image of the module can be up to 31 words of Input and 31 words of Output, depending on the mode selected (Single or Multi-Drive) and the number of drives connected. A Single mode system with one drive on each channel requires 7 Input words and 7 Output words.
3-6 Configuring the Module 3. Click on the Chan. 1 tab (Figure 3.3) and set the I/O Config data area accordingly. In this example, the 1769-SM2 is configured to fault if the controller is switched to Program mode, and one drive is connected at node address 100. Figure 3.3 Chan.
Configuring the Module 3-7 Figure 3.4 Chan. 1 Tab Data Screen with Idle Action - Send Flt Cfg Enabled 4. For each additional channel being used, select its respective tab, set the desired I/O configuration, and enable the appropriate idle action. TIP: Alternatively, data can be entered on the Generic Extra Data Config tab (shown in Figure 3.5 for identification purposes only). However, with the easy-to-use Chan.1, Chan. 2, and Chan.
3-8 Configuring the Module See Table 3.C for descriptions of these configuration words. 5. Click OK when finished. The MicroLogix 1500 will download the configuration data to the 1769-SM2 module when the controller is placed in run mode. Special Case— Data Entry for 2 Stop Bits Communication The Chan.1, Chan. 2, and Chan 3 tabs do not allow settings that specify 2 stop bits communication in Modbus RTU operation.
Configuring the Module 3-9 3. Click OK to apply the changes and close the screen. However, if you click Apply or leave this tab to go to another tab, you may see this message dialog box. If so, click Yes to apply the changes. Entering CompactLogix Configuration Data Using RSLogix 5000 v10 (or higher) Allocate and enter the configuration data by performing these steps: 1. In the RSLogix 5000 treeview, right-click on CompactBus Local and select New Module. Figure 3.
3-10 Configuring the Module Figure 3.8 Select Module Type Screen 3. After the Module Properties screen (Figure 3.9) appears, enter a name for the module, such as “My_1769_SM2.” Change the Comm Format to “Data - INT,” which will enable the entry of Output Connection parameters (no longer grayed out). Enter the Slot location of the 1769-SM2. Enter the desired Input and Output word length (see Table 3.A or Table 3.B) and Configuration data size (Table 3.C). Click Next >. Figure 3.
Configuring the Module 3-11 Figure 3.10 Module Properties Last Screen 5. The treeview (Figure 3.11) now shows the 1769-MODULE. Figure 3.11 RSLogix 5000 Treeview with Listed 1769-MODULE 6. Double-clicking on the Controller Tags or Program Tags in the treeview will display the various tags, including the tags for the 1769-SM2 module (Figure 3.12). Click on the Monitor Tags tab at the bottom of the window to enter the configuration data. Figure 3.
3-12 Configuring the Module Parameter Mode When the Configuration Mode Switch (SW1 in Figure 2.1) is in the PARAM (Parameter) position, the 1769-SM2 uses its internal parameter settings to configure the module. If any configuration data is downloaded by the controller, it will be ignored. Important: When the Parameter mode is used, the configuration data size in the controller should be set to “0.” See Controller Mode on page 3-3 for more information.
Configuring the Module 3-13 Using the Optional, External PowerFlex 4-Class HIM When using the 1769-SM2 module in Single mode, the optional, external PowerFlex 4-Class HIM (Human Interface Module) can be used to access its parameters. Basic steps to access module parameters using the HIM are shown in Table 3.E. For additional HIM information, refer to the PowerFlex 4-Class HIM Quick Reference (publication 22HIM-QR001). Table 3.
Configuring the Module Setting the I/O Configuration (Multi-Drive Mode Only) The I/O configuration sets the number of drives that are connected to each channel. When the 1769-SM2 module is used in Single mode (Operating Mode Switch SW2 set to “1X”), only one PowerFlex 4-Class drive can be connected to each channel and module Parameters 07 [DSI I/O Cfg 1], 22 - [DSI I/O Cfg 2], and 37 - [DSI I/O Cfg 3] have no effect.
Configuring the Module 3-15 Setting an Idle Action (Single and Multi-Drive Mode) By default, when the controller is idle, the drive responds by faulting when using I/O from the 1769-SM2 module. You can respectively configure a different response to an idle controller using Parameters 04 - [Idle Action 1], 19 - [Idle Action 2], and 34 - [Idle Action 3] for each channel’s connected drives. ! ATTENTION: Risk of injury or equipment damage exists.
3-16 Configuring the Module ATTENTION: Idle Action is NOT available for RTU Master operation in Multi-Drive mode. The connected RTU Slave devices will take their respective internal fault actions in response to receiving no communications from the 1769-SM2 module.
Configuring the Module 3-17 Configuring the Modbus RTU Master Parameters In Multi-Drive mode, any module channel can be configured for RTU Master operation by setting Parameter 07 - [DSI I/O Cfg 1], 22 - [DSI I/O Cfg 2] or 37 - [DSI I/O Cfg 3] to “5” (RTU Master). When doing this, additional Modbus RTU Master parameters must be set to complete that channel’s configuration. Setting the RTU Baud Rate By default, each channel set for RTU Master operation uses a 38.4K baud rate.
3-18 Configuring the Module Figure 3.18 Example RTU Format HIM Screen for CH1 Drives RTU Format 1 Parameter: # 015 0 VALUE SEL LIMITS Value 0 1 2 3 4 5 Format 8-N-1 (default) 8-E-1 8-O-1 8-N-2 8-E-2 8-O-2 2. Reset the module (see Resetting the Module on page 3-20). Setting the RTU Rx Delay Time 1.
Configuring the Module 3-19 Figure 3.20 Example RTU Tx Delay HIM Screen for CH1 Drives RTU Tx Delay 1 Parameter: # 017 0 VALUE Default: 0 milliseconds Minimum: 0 milliseconds Maximum: 500 milliseconds SEL LIMITS TIP: If the Modbus RTU slave is a PowerFlex 4-Class drive, set the value of [RTU Tx Delay x] to 8 milliseconds when the value of [RTU Baud Rate x] is 19200. 2. Reset the module (see Resetting the Module on page 3-20). Setting the RTU Message Timeout 1.
3-20 Configuring the Module Resetting the Module Changes to switch settings and some module parameters require that you reset the 1769-SM2 module before the new settings take effect. You can reset the module by cycling power to the module or by using Parameter 03 - [Reset Module]. ! ATTENTION: Risk of injury or equipment damage exists. If the module is transmitting control I/O to the drive, the drive may fault when you reset the module.
Configuring the Module 3-21 Viewing the Module Status Using Parameters The following parameters provide information about the status of the 1769-SM2 module. You can view these parameters at any time.
3-22 Configuring the Module Flash Updating the Module The adapter can be flash updated over the network (via EtherNet/IP using DriveExplorer Full only) or serially through a direct connection from a computer to the drive using a 1203-USB converter or 22-SCM-232 serial converter module (firmware v2.005 or higher). Not all flash methods (DriveExplorer Lite/Full, ControlFLASH or HyperTerminal) can be used successfully in all cases.
Chapter 4 Understanding the I/O Image This chapter provides information and examples of the 1769-SM2 module I/O image, including Module Control/Status, Logic Command/ Status, and Reference/Feedback.
4-2 Understanding the I/O Image needed. Likewise, five PowerFlex drives on CH1 in Multi-Drive mode using control would require 11 words of I/O. TIP: To minimize the number of I/O words needed, connect the drive(s) starting with CH1, followed by CH2, and then CH3. Table 4.
Understanding the I/O Image 4-3 Module Status Word The Module Status Word (input word 0) is used for all channels, where: Bit # Bit Name Description 0 CH1 Logic Status 0 Valid “0” = Logic Status/Feedback data for CH1 Drive 0 is not valid “1” = Logic Status/Feedback data for CH1 Drive 0 is valid 1 CH1 Logic Status 1 Valid “0” = Logic Status/Feedback data for CH1 Drive 1 is not valid “1” = Logic Status/Feedback data for CH1 Drive 1 is valid 2 CH1 Logic Status 2 Valid “0” = Logic Status/Feedback da
4-4 Understanding the I/O Image Using Logic Command/Status The Logic Command is a 16-bit word of control data produced by the controller and consumed by the 1769-SM2 module. The Logic Status is a 16-bit word of status data produced by the 1769-SM2 module and consumed by the controller. This manual contains the bit definitions for compatible products available at the time of publication in Appendix D. For other products, refer to their documentation.
Chapter 5 Understanding Explicit Messaging This chapter provides information about explicit messaging. Topic Formatting Explicit Messages Modbus RTU Master Operation Messages Page 5-2 5-9 Explicit messaging is used to read/write data that is not part of the module’s I/O Image (Chapter 4), such as: • Reading/writing drive parameters. • Operating as a Modbus RTU Master and initiating Request/Response messages to Modbus RTU Slave devices, such as PowerFlex 7-Class drives with 20-COMM-H adapters.
5-2 Understanding Explicit Messaging Formatting Explicit Messages For RSLogix 500, format each message as shown in Figure 5.1 and see Table 5.A for a description of the data required in each field. For RSLogix 5000, format each message as shown in Figure 5.2 and see Table 5.B. Figure 5.1 RSLogix 500 Explicit Message Setup Screen Table 5.
Understanding Explicit Messaging Figure 5.2 RSLogix 5000 Explicit Message Setup Screen Table 5.B RSLogix 5000 Explicit Message Configuration Data Configuration Tab Message Type Service Type Service Code Class Instance Attribute Source Element Source Length Destination Communication Tab Path Tag Tab Name Description Always use “CIP Generic.” The service is used to read/write a parameter value. Code for the requested service. Class ID for the DSI Parameter Object. Instance number in the Class.
5-4 Understanding Explicit Messaging Table 5.C shows the instance numbers to be used for message configuration: Table 5.C Instance Numbers for Message Configuration Instances (Dec.
Understanding Explicit Messaging 5-5 RSLogix 500 Parameter Read/Write Examples In this example, a read and a write of PowerFlex 40 drive Parameter 78 - [Jog Frequency] is being done. The RSLogix 500 Message Configuration screen example to read a parameter is shown in Figure 5.3. It is assumed that the 1769-SM2 module occupies slot 1 and is operated in Single mode, and that the drive is connected to CH1. See Table 5.A for descriptions of the message configuration data. Figure 5.
5-6 Understanding Explicit Messaging The RSLogix 500 Message Configuration example screen to write to a parameter is shown in Figure 5.4. It is assumed that the 1769-SM2 module occupies slot 1 and is operated in Single mode, and that the drive is connected to CH1. See Table 5.A for descriptions of the message configuration data. Figure 5.4 RSLogix 500 Example Message Setup Screen to Write to a Parameter The request data for the message is stored at Data Table Address N7:2.
Understanding Explicit Messaging 5-7 RSLogix 5000 Parameter Read/Write Examples In this example, a read and a write of PowerFlex 40 drive Parameter 78 - [Jog Frequency] is being done. The RSLogix 5000 Message Configuration example screen to read a parameter is shown in Figure 5.5. It is assumed that the 1769-SM2 module occupies slot 1 and is operated in Single mode, and that the drive is connected to CH1. See Table 5.B for descriptions of the message configuration data. Figure 5.
5-8 Understanding Explicit Messaging The RSLogix 5000 Message Configuration example screen to write to a parameter is shown in Figure 5.6. It is assumed that the 1769-SM2 module occupies slot 1 and is operated in Single mode, and that the drive is connected to CH1. See Table 5.B for descriptions of the message configuration data. Figure 5.6 RSLogix 5000 Example Message Setup Screen to Write to a Parameter The request data for the message is stored in CH1_Write_Value.
Understanding Explicit Messaging 5-9 Modbus RTU Master Operation Messages In Multi-Drive mode, any channel can be configured for Modbus RTU Master operation to communicate with a variety of Rockwell Automation or 3rd Party RTU Slave devices, such as PowerFlex 7-Class drives with 20-COMM-H adapters. In the Multi-Drive ladder examples provided in this manual, CH3 is used to communicate with a PowerFlex 70 drive.
5-10 Understanding Explicit Messaging Figure 5.7 RSLogix 500 Modbus RTU Master Message Setup Screen Table 5.D RSLogix 500 Modbus RTU Master Message Configuration Data This Controller Section Description Channel Always use “Expansion Comms Port.” Slot The chassis slot occupied by the 1769-SM2 module. Port Always set to “2.” Note: This field was not configurable in earlier versions of RSLogix 500. Communication Command Always use “CIP Generic.
Understanding Explicit Messaging Figure 5.8 RSLogix 5000 Modbus RTU Master Message Setup Screen Table 5.E RSLogix 5000 Modbus RTU Master Message Configuration Data Configuration Tab Description Message Type Always use “CIP Generic.” Service Type Type of Service to execute. Service Code Code of the respective Service Type. Class Class ID for the DSI Parameter Object. Instance Instance number in the Class. Attribute Attribute number of the Instance.
5-12 Understanding Explicit Messaging RSLogix 500 Modbus RTU Master Write Message Example Figure 5.9 shows an example Modbus RTU Master write message setup screen. See Table 5.D for descriptions of the message configuration data. Figure 5.9 RSLogix 500 Example Modbus RTU Master Write Message Setup Screen In this example, Logic Command and Reference are being written to a PowerFlex 70 drive.
Understanding Explicit Messaging 5-13 RSLogix 500 Modbus RTU Master Read Message Example Figure 5.10 shows an example Modbus RTU Master read message setup screen. See Table 5.D for descriptions of the message configuration data. Figure 5.10 RSLogix 500 Example Modbus RTU Master Read Message Setup Screen In this example, Logic Status and Feedback are being read from a PowerFlex 70 drive.
5-14 Understanding Explicit Messaging RSLogix 5000 Modbus RTU Master Write Message Example Figure 5.11 shows an example Modbus RTU Master write message setup screen. See Table 5.E for descriptions of the message configuration data. Figure 5.11 RSLogix 5000 Example Modbus RTU Master Write Message Setup Screen In this example, Logic Command and Reference are being written to a PowerFlex 70 drive.
Understanding Explicit Messaging 5-15 RSLogix 5000 Modbus RTU Master Read Message Example Figure 5.12 shows an example Modbus RTU Master read message setup screen. See Table 5.E for descriptions of the message configuration data. Figure 5.12 RSLogix 5000 Example Modbus RTU Master Read Message Setup Screen In this example, Logic Status and Feedback are being read from a PowerFlex 70 drive.
5-16 Notes: Understanding Explicit Messaging
Chapter 6 MicroLogix 1500 Example Ladder Programs This chapter provides ladder examples for a MicroLogix 1500 controller used with a 1769-SM2 module in Single mode and Multi-Drive mode. Topic Single Mode Multi-Drive Mode Page 6-1 6-8 Single Mode The ladder example provided in this section is based on a 1769-SM2 module in slot 1 with one PowerFlex 4/40 drive connected to each channel (Figure 6.1).
MicroLogix 1500 Example Ladder Programs Figure 6.1 Example MicroLogix 1500 Single Mode System Arrangement MicroLogix 1500 Controller PowerFlex 4/40 Drives DSI 6-2 C H 1 C H 2 C H 3 CH1 CH2 CH3 PowerFlex 40 Drive Settings The PowerFlex 40 drives used in the example program have the following parameter settings: Parameter P036 - [Start Source] P038 - [Speed Reference] A103 - [Comm Data Rate] A104 - [Comm Node Addr] A107 - [Comm Format] Setting 5 (Comm Port) 5 (Comm Port) 4 (19.
MicroLogix 1500 Example Ladder Programs 6-3 The I/O configuration in RSLogix 500 v6.30 (or higher) for the Single mode example program is: Refer to Table 3.C for configuration data words and parameter descriptions. Also, see Chapter 4 for information about the I/O image, Module Enable/Status, Logic Command/Status, and Reference/ Feedback.
6-4 MicroLogix 1500 Example Ladder Programs MicroLogix 1500 Example Program Figure 6.
MicroLogix 1500 Example Ladder Programs 6-5 Figure 6.3 Example MicroLogix 1500 Single Mode Ladder Logic CH1 Subroutine 1769-SM2 Channel 1 Subroutine The following rungs display some of the Logic Status bits from the drive. Refer to Appendix D in the 1769-SM2 user manual for additional information about the Logic Status word.
6-6 MicroLogix 1500 Example Ladder Programs Figure 6.3 Example MicroLogix 1500 Single Mode Ladder Logic CH1 Subroutine (Continued) This rung unlatches the contact that turns on the Start command when the drive is not communicating with the 1769-SM2. This prevents the drive from immediately starting when communications is restored. If an immediate start is desired for the application, this rung could be deleted.
MicroLogix 1500 Example Ladder Programs 6-7 The read and write message instructions for PowerFlex 40 drive Parameter 78 - [Jog Frequency] are configured as follows: Single Mode Example Program Data Table Integer File N7: is used to contain the input and output data to/from the three channels of the module: N7: Word CH1 0 1 2 3 CH2 10 11 12 13 CH3 20 21 22 23 Description Reference Feedback Parameter 78 Write Value Parameter 78 Read Value
6-8 MicroLogix 1500 Example Ladder Programs An example of data table values are shown below: A value of “200” for the Reference equates to 20.0 Hz. A value of “100” for drive Parameter 78 - [Jog Frequency] equates to 10.0 Hz. Since CH2 and CH3 ladder routines are similar to the CH1 routine, they are not provided.
MicroLogix 1500 Example Ladder Programs 6-9 Figure 6.
6-10 MicroLogix 1500 Example Ladder Programs 20-COMM-H Settings The 20-COMM-H adapter used in the example program has the following parameter and switch settings: Parameter Settings Parameter 5 - [Net Rate Cfg] 7 - [Net Parity Cfg] 16 - [DPI I/O Cfg] 30 - [Stop Bits Cfg] Setting 2 (19200 Baud) 1 (Odd) 00001 = Logic Command/Reference 0 (1 bit) Switch Settings Switch Node Address Switches Network Protocol Switch Setting 15 RTU position 1769-SM2 Settings The 1769-SM2 module used in the example program ha
MicroLogix 1500 Example Ladder Programs 6-11 The I/O configuration in RSLogix 500 v6.30 (or higher) for the Multi-Drive mode example program is: Refer to Chapter 4 for information about the I/O image, Module Enable/ Status, Logic Command/Status, and Reference/Feedback.
6-12 MicroLogix 1500 Example Ladder Programs MicroLogix 1500 Multi-Drive Mode Example Program Figure 6.
MicroLogix 1500 Example Ladder Programs 6-13 Figure 6.
6-14 MicroLogix 1500 Example Ladder Programs Figure 6.6 Example MicroLogix 1500 Multi-Drive Ladder Logic CH1 Drive 0 Subroutine 1769-SM2 Channel 1 Drive 0 Subroutine The following rungs display some of the Logic Status bits from the drive. Refer to Appendix D in the 1769-SM2 user manual for additional information about the Logic Status word.
MicroLogix 1500 Example Ladder Programs 6-15 Figure 6.6 Example MicroLogix 1500 Multi-Drive Ladder Logic CH1 Drive 0 Subroutine (Continued) This rung unlatches the contact that turns on the Start command when the drive is not communicating with the 1769-SM2. This prevents the drive from immediately starting when communications is restored. If an immediate start is desired for the application, this rung could be deleted.
6-16 MicroLogix 1500 Example Ladder Programs The read and write message instructions for PowerFlex 40 drive Parameter 78 - [Jog Frequency] are configured as follows: For additional information about the message setup, refer to page 5-3.
MicroLogix 1500 Example Ladder Programs N7: Words for CH2 Drive 0 Drive 1 Drive 2 50 60 70 51 61 71 52 62 72 53 63 73 Drive 3 80 81 82 83 Drive 4 90 91 92 93 6-17 Description Reference Feedback Parameter 78 Write Value Parameter 78 Read Value An example of data table values are shown below: A value of “101” for the Reference equates to 10.1 Hz. A value of “100” for drive Parameter 78 - [Jog Frequency] equates to 10.0 Hz.
6-18 MicroLogix 1500 Example Ladder Programs CH3 Modbus RTU Master Subroutine Example In Multi-Drive mode, any channel can be configured for Modbus RTU Master operation. In the MicroLogix 1500 Multi-Drive ladder logic example, CH3 is used to communicate with a PowerFlex 70 drive via Modbus RTU operation. Figure 6.7 Example MicroLogix 1500 Modbus RTU Ladder Logic CH3 Subroutine 1769-SM2 Channel 3 Modbus RTU Master Subroutine Channel 3 consists of a single PowerFlex 70 drive with a 20-COMM-H adapter.
MicroLogix 1500 Example Ladder Programs 6-19 Figure 6.7 Example MicroLogix 1500 Modbus RTU Ladder Logic CH3 Subroutine (Continued) 0004 Write Parameter 100 [Jog Frequency] (written 1x per request). N7:120 = Slave Address ("15" is the 20-COMM-H address) N7:121 = Function Code ("6" is Write Single Register command) N7:122 = Starting Address ("1099" = 4x1100) N7:123 = Length ("1") N7:124 = Pr. 100 [Jog Frequency] Write Value CH3 Write Pr.
6-20 MicroLogix 1500 Example Ladder Programs The format of the command data is: Data Word N7:100 N7:101 N7:102 N7:103 N7:104 N7:105 N7:106 Example Value 15 16 0 3 18 0 8192 Description PowerFlex 70 node address Function Code – Write Multiple Registers Starting Register Address (40001) Number of registers to write Value for 40001 – Logic Command word Value for 40002 – not used Value for 40003 – Reference word The Logic Status/Feedback read message instruction on rung 0002 is configured as follows: The f
MicroLogix 1500 Example Ladder Programs The write message instruction on rung 0004 for PowerFlex 70 drive Parameter 100 - [Jog Speed] is configured as follows: The format of the command data is: Data Word N7:120 N7:121 N7:122 N7:123 N7:124 Example Value 15 6 1099 1 111 Description PowerFlex 70 node address Function Code – Write Single Registers Starting Register Address (41100) Number of registers to write Parameter 100 write data 6-21
6-22 MicroLogix 1500 Example Ladder Programs The read message instruction on rung 0005 for PowerFlex 70 drive Parameter 100 - [Jog Speed] is configured as follows: The format of the command data is: Data Word N7:130 N7:131 N7:132 N7:133 Example Value 15 3 1099 1 Description PowerFlex 70 node address Function Code – Read Holding Registers Starting Register Address (41100) Number of registers to read The format of the response data is: Data Word N7:134 Example Value 111 Description Parameter 100 read d
Chapter 7 CompactLogix Example Ladder Programs This chapter provides ladder examples for a CompactLogix controller used with a 1769-SM2 module in Single mode and Multi-Drive mode. Topic Single Mode Multi-Drive Mode Page 7-1 7-10 Single Mode The ladder example provided in this section is based on a 1769-SM2 module in slot 1 with one PowerFlex 4/40 drive connected to each channel (Figure 7.1).
CompactLogix Example Ladder Programs Figure 7.1 Example CompactLogix Single Mode System Arrangement CompactLogix Controller PowerFlex 4/40 Drives MODULE CH1 CH2 CH3 DSI 7-2 C H 1 C H 2 C H 3 CH1 CH2 CH3 PowerFlex 40 Settings The PowerFlex 40 drives used in the example program have the following parameter settings: Parameter P036 - [Start Source] P038 - [Speed Reference] A103 - [Comm Data Rate] A104 - [Comm Node Addr] A107 - [Comm Format] Setting 5 (Comm Port) 5 (Comm Port) 4 (19.
CompactLogix Example Ladder Programs 7-3 The I/O configuration in RSLogix 5000 for the Single mode example program is: Refer to Chapter 4 for information about the I/O image, Module Enable/ Status, Logic Command/Status, and Reference/Feedback.
7-4 CompactLogix Example Ladder Programs CompactLogix Example Program Figure 7.
CompactLogix Example Ladder Programs 7-5 Figure 7.3 Example CompactLogix Single Mode Ladder Logic CH1 Subroutine 1769-SM2 Channel 1 Subroutine The following i rungs display some of the Logic Status bits from the drive. Refer to Appendix D in the 1769-SM2 user manual for additional information about the Logic Status word. Channel 1 Logic Status Bit 00 Local:1:I.Data[1].0 CH1_Ready Channel 1 Logic Status Bit 01 Local:1:I.Data[1].1 CH1_Active Channel 1 Logic Status Bit 03 Local:1:I.Data[1].
7-6 CompactLogix Example Ladder Programs Figure 7.3 Example CompactLogix Single Mode Ladder Logic CH1 Subroutine (Continued) 7 This rung unlatches the contact that turns on the Start command when the drive is not communicating with i the 1769-SM2. This prevents the drive from immediately starting when communications are restored. If an immediate start is desired for an application, this rung could be deleted. CH1_Valid_Data
CompactLogix Example Ladder Programs 7-7 Figure 7.3 Example CompactLogix Single Mode Ladder Logic CH1 Subroutine (Continued) 15 Move Source MOV CH1_Read_Value 111 Dest CH1_Read_Jog_Frequency 111 MOV Move Source CH1_Write_Jog_Frequency 111 Dest CH1_Write_Value 111 16 CH1_Write_Param 17 Type - CIP Generic Message Control 18 MSG CH1_Write_Msg ...
7-8 CompactLogix Example Ladder Programs Write Message (Rung 17) Single Mode Example Program Tags The following tags are used to contain the input and output data to/from the three channels of the module:
CompactLogix Example Ladder Programs 7-9
7-10 CompactLogix Example Ladder Programs Since CH2 and CH3 ladder routines are similar to the CH1 routine, they are not provided. Multi-Drive Mode The ladder example provided in this section is based on a 1769-SM2 module in slot 1 with five PowerFlex 4/40 drives connected to CH1 and to CH2, and one PowerFlex 70 connected to CH3 (Figure 7.4).
CompactLogix Example Ladder Programs 7-11 Figure 7.
7-12 CompactLogix Example Ladder Programs 20-COMM-H Settings The 20-COMM-H adapter used in the example program has the following parameter and switch settings: Parameter Settings Parameter 5 - [Net Rate Cfg] 7 - [Net Parity Cfg] 16 - [DPI I/O Cfg] 30 - [Stop Bits Cfg] Setting 2 (19200 Baud) 1 (Odd) 00001 = Logic Command/Reference 0 (1 bit) Switch Settings Switch Node Address Switches Network Protocol Switch Setting 15 RTU position 1769-SM2 Settings The 1769-SM2 module used in the example program has t
CompactLogix Example Ladder Programs 7-13 Refer to Chapter 4 for information about the I/O image, Module Enable/ Status, Logic Command/Status, and Reference/Feedback.
7-14 CompactLogix Example Ladder Programs CompactLogix Multi-Drive Mode Example Program Figure 7.
CompactLogix Example Ladder Programs 7-15 Figure 7.
7-16 CompactLogix Example Ladder Programs Figure 7.5 Example CompactLogix Multi-Drive Ladder Logic Main Routine (Continued) CH2_Drv0_Valid_Data CH2_Drv1_Valid_Data CH2_Drv2_Valid_Data CH2_Drv3_Valid_Data 14 CH2_Drv4_Valid_Data SM2_CH1_Data_Valid SM2_CH2_Data_Valid SM2_CH2_Data_Valid SM2_Input_Data_Valid 15 16 (End) SM2_Cfg_Data_Valid
CompactLogix Example Ladder Programs 7-17 Figure 7.6 Example CompactLogix Multi-Drive Ladder Logic CH1 Drive 0 Subroutine 1769-SM2 Channel 1 Drive 0 Subroutine The following i rungs display some of the Logic Status bits from the drive. Refer to Appendix D in the 1769-SM2 user manual for additional information about the Logic Status word. CH1 Drv0 Logic Status Bit 00 Local:1:I.Data[1].0 CH1_Drv0_Ready CH1 Drv0 Logic Status Bit 01 Local:1:I.Data[1].
7-18 CompactLogix Example Ladder Programs Figure 7.6 Example CompactLogix Multi-Drive Ladder Logic CH1 Drive 0 Subroutine (Continued) 7 This rung unlatches the contact that turns on the Start command when the drive is not communicating with i the 1769-SM2. This prevents the drive from immediately starting when communications are restored. If an immediate start is desired for an application, this rung could be deleted. CH1_Drv0_Valid_Data
CompactLogix Example Ladder Programs 7-19 Figure 7.6 Example CompactLogix Multi-Drive Ladder Logic CH1 Drive 0 Subroutine (Continued) 15 MOV Move Source CH1_Drv0_Read_Value 111 Dest CH1_Drv0_Read_Jog_Frequency 111 MOV Move Source CH1_Drv0_Write_Jog_Frequency 111 Dest CH1_Drv0_Write_Value 111 16 CH1_Drv0_Write_Param 17 Type - CIP Generic Message Control 18 MSG CH1_Drv0_Write_Msg ...
7-20 CompactLogix Example Ladder Programs A “17486” equates to Parameter 78 (17486 - 17408 = 78), since 17408 is Instance 0 in the drive (17409 is Parameter 1). For additional information about the message setup, refer to page 5-3. Write Message (Rung 17) A “17486” equates to Parameter 78 (17486 - 17408 = 78), since 17408 is Instance 0 in the drive (17409 is Parameter 1). For additional information about the message setup, refer to page 5-3.
CompactLogix Example Ladder Programs 7-21 Multi-Drive Example Program Tags The following tags are used to contain the input and output data to/from CH1 Drive 0: Since the Drive 1…4 and CH2 ladder routines are similar to the CH1 Drive 0 routine, they are not provided.
7-22 CompactLogix Example Ladder Programs CH3 Modbus RTU Master Subroutine Example In Multi-Drive mode, any channel can be configured for Modbus RTU Master operation. In the CompactLogix Multi-Drive ladder logic example, CH3 is used to communicate with a PowerFlex 70 drive via Modbus RTU operation. Figure 7.7 Example CompactLogix Modbus RTU Ladder Logic CH3 Subroutine 1769-SM2 Channel 3 Modbus RTU Master Subroutine Channel 3 consists of a single PowerFlex 70 drive with i a 20-COMM-H adapter.
CompactLogix Example Ladder Programs 7-23 Figure 7.7 Example CompactLogix Modbus RTU Ladder Logic CH3 Subroutine (Continued) Write Parameter 100 [Jog Frequency] (written 1x per request) CH3_MSG3_REQ[0] = Slave Address ("15" is the 20-COMM-H address) CH3_MSG3_REQ[1] = Function Code ("6" is Write Single Register command) CH3_MSG3_REQ[2] = Starting Address ("1099" = 4x1101) CH3_MSG3_REQ[3] = Length ("1") CH3_MSG3_REQ[4] = Pr.100 Write Value Channel 3 Write Pr.
7-24 CompactLogix Example Ladder Programs The Logic Command/Reference write message instruction on rung 0 is configured as follows: The format of the command data is:
CompactLogix Example Ladder Programs The Logic Status/Feedback read message instruction on rung 2 is configured as follows: The format of the command and response data is: 7-25
7-26 CompactLogix Example Ladder Programs The write message instruction on rung 4 for PowerFlex 70 drive Parameter 100 - [Jog Speed] is configured as follows: The format of the command data is: The read message instruction on rung 5 for PowerFlex 70 drive Parameter 100 - [Jog Speed] is configured as follows:
CompactLogix Example Ladder Programs The format of the command and response data is: For additional information about Modbus RTU Master messages for PowerFlex 7-Class drives, refer to the 20-COMM-H Adapter User Manual, publication 20COMM-UM009.
7-28 Notes: CompactLogix Example Ladder Programs
Chapter 8 ControlLogix w/1769-ADN DeviceNet Example Ladder Program This chapter provides an example of a ControlLogix controller and 1769-ADN Remote DeviceNet adapter system used with a 1769-SM2 module in Single mode. Important: When the 1769-SM2 module is used with the 1769-ADN, the Configuration Mode switch (SW1) must be set to the “Controller” position (default). See Chapter 2 for information on Configuration Mode switch settings.
ControlLogix w/1769-ADN DeviceNet Example Ladder Program Explicit messaging (parameter read/write) capability varies between the RSLogix software packages and controllers: • At the time of publication, the 1769-ADN does NOT have explicit messaging capability. Refer to ADN documentation for possible future explicit messaging support. Figure 8.
ControlLogix w/1769-ADN DeviceNet Example Ladder Program 8-3 5. In the Add New RSLinx Driver screen, use the default name or type a new name and click OK. The Configure Drivers screen reappears with the new driver in the Configured Drivers list (Figure 8.2). Figure 8.2 Configure Drivers Dialog Box with a Configured Driver 6. Click Close to close the Configure Drivers screen. Keep RSLinx running. 7. Verify that your computer recognizes the drive.
8-4 ControlLogix w/1769-ADN DeviceNet Example Ladder Program Figure 8.3 Example DeviceNet Network Setting Up the 1769-ADN To configure the 1769-ADN for use with the example program using RSNetWorx for DeviceNet v3.21 (or higher), perform these steps: 1. Double-click on the 1769-ADN adapter image in the graphic display window (Figure 8.4). In the ladder example system, the node address setting on the adapter is “2.” Figure 8.4 1769-ADN Adapter Image Screen 2.
ControlLogix w/1769-ADN DeviceNet Example Ladder Program 8-5 Figure 8.5 1769-ADN Adapter Module Configuration Tab Screen The EDS file for the 1769-SM2 module is needed to configure the remote 1769-ADN DeviceNet system. If the 1769-SM2 is not listed as a selection (Figure 8.5), the EDS file will need to be downloaded from the Internet. For more information, refer to Registering the 1769-SM2 EDS File on page 8-8. 3. Select the 1769-SM2 and click on the Properties command button.
8-6 ControlLogix w/1769-ADN DeviceNet Example Ladder Program 4. Select the Advanced Parameters tab (Figure 8.7). Refer to Chapter 4, Understanding the I/O Image regarding the Input and Output Data Sizes. In the ladder example, the Input and Output Data Sizes are set for 7 words each to allow for Logic Command/Reference and Logic Status/Feedback for all 3 drives. Figure 8.7 1769-SM2 Module Advanced Parameters Tab Screen 5. Select the Configuration Settings tab.
ControlLogix w/1769-ADN DeviceNet Example Ladder Program 8-7 Parameters can be adjusted by double-clicking on the desired parameter. Default settings are used for this ladder example. Click OK to complete the 1769-SM2 configuration. 6. Select the I/O Summary tab (Figure 8.9). The 1769-ADN uses 4 Input bytes and the 1769-SM2 module has been configured for 14 bytes (7 words) of Input and Output data. The I/O Summary below is required for the example ladder program. Figure 8.
8-8 ControlLogix w/1769-ADN DeviceNet Example Ladder Program Registering the 1769-SM2 EDS File The EDS file for the 1769-SM2 module is needed to configure the remote 1769-ADN DeviceNet system. If the 1769-SM2 is not listed as a selection in the Hardware list (Figure 8.10), the EDS file will need to be downloaded from the Internet and registered using the EDS Wizard. Figure 8.10 1769-ADN Adapter Module Configuration Tab Screen 1. Download the EDS file for the 1769-SM2 module from www.ab.com/networks/eds.
ControlLogix w/1769-ADN DeviceNet Example Ladder Program 8-9 3. Click Next > to display the EDS Wizard Task screen (Figure 8.12). Select Register an EDS file(s) and click Next >. Figure 8.12 EDS Wizard Task Screen 4. The EDS Wizard Registration screen (Figure 8.13) will appear. Select Register a single file and use the Browse command button to browse to the EDS file on your hard drive. Click Next >. Figure 8.13 EDS Wizard Registration Screen 5. The EDS file is installed and tested (Figure 8.14).
8-10 ControlLogix w/1769-ADN DeviceNet Example Ladder Program Figure 8.14 EDS Wizard Installation Test Screen 6. The EDS Wizard Change Graphic Image screen (Figure 8.15) appears, enabling the icon associated with the EDS file for the 1769-SM2 module to be changed if desired. Click Next >. Figure 8.15 EDS Wizard Change Graphic Image Screen 7. The EDS Wizard Final Task Summary screen (Figure 8.16) will appear. Click Next > to register the 1769-SM2 module.
ControlLogix w/1769-ADN DeviceNet Example Ladder Program 8-11 Figure 8.16 EDS Wizard Final Task Summary Screen 8. The EDS Wizard is now completed (Figure 8.17). Click Finish. Figure 8.17 EDS Wizard Finish Screen Earlier versions of RSNetWorx for DeviceNet require you to close and restart RSNetWorx for DeviceNet to enable the 1769-SM2 module to appear in the 1769-ADN Module Configuration tab (Figure 8.10). If you do not see the 1769-SM2 in the Hardware list, close and restart RSNetWorx for DeviceNet.
8-12 ControlLogix w/1769-ADN DeviceNet Example Ladder Program PowerFlex 40 Settings The PowerFlex 40 drives used in the example program have the following parameter settings: Parameter P036 - [Start Source] P038 - [Speed Reference] A103 - [Comm Data Rate] A104 - [Comm Node Addr] A107 - [Comm Format] Setting 5 (Comm Port) 5 (Comm Port) 4 (19.
ControlLogix w/1769-ADN DeviceNet Example Ladder Program 8-13 ControlLogix w/1769-ADN Example Program Figure 8.
8-14 ControlLogix w/1769-ADN DeviceNet Example Ladder Program Figure 8.18 Example ControlLogix Ladder Logic Main Routine (Continued) This rung enables the 1769-SM2 to send the Channel 3 Logix Command and Reference words to the drive. CH3_Enable 6 Channel 3 Subroutine CH3 control logic JSR Jump To Subroutine Routine Name Channel_3 7 CH1_Valid_Data CH2_Valid_Data CH3_Valid_Data
ControlLogix w/1769-ADN DeviceNet Example Ladder Program 8-15 Figure 8.19 Example ControlLogix Ladder Logic CH1 Subroutine 1769-SM2 Channel 1 Subroutine The following i rungs display some of the Logic Status bits from the drive. Refer to Appendix D in the 1769-SM2 user manual for additional information about the Logic Status word. SM2_Input_Data[3].0 CH1_Ready SM2_Input_Data[3].1 CH1_Active SM2_Input_Data[3].3 CH1_Forward SM2_Input_Data[3].7 CH1_Fault SM2_Input_Data[3].
8-16 ControlLogix w/1769-ADN DeviceNet Example Ladder Program Figure 8.19 Example ControlLogix Ladder Logic CH1 Subroutine (Continued) CH1_Forward_Cmd SM2_Output_Data[1].4 CH1_Forward_Cmd / SM2_Output_Data[1].5 11 12 13 14 (End) This rung displays the Reference being sent to the drive. An integer represents the xxx.x Hz format (decimal is implied) used by the drive, so a displayed value of "300" equates to 30.0 Hz.
ControlLogix w/1769-ADN DeviceNet Example Ladder Program 8-17 Figure 8.20 Example ControlLogix Ladder Logic CH2 Subroutine 1769-SM2 Channel 2 Subroutine The following rungs display some of the Logic Status bits from the drive. Refer to Appendix D in the 1769-SM2 user manual for additional information about the Logic Status word. SM2_Input_Data[5].0 CH2_Ready SM2_Input_Data[5].1 CH2_Active SM2_Input_Data[5].3 CH2_Forward SM2_Input_Data[5].7 CH2_Fault SM2_Input_Data[5].
8-18 ControlLogix w/1769-ADN DeviceNet Example Ladder Program Figure 8.20 Example ControlLogix Ladder Logic CH2 Subroutine (Continued) CH2_Forward_Cmd SM2_Output_Data[3].4 CH2_Forward_Cmd SM2_Output_Data[3].5 11 12 13 14 (End) / This rung displays the Reference being sent to the drive. An integer represents the xxx.x Hz format (decimal is implied) used by the drive, so a displayed value of "300" equates to 30.0 Hz.
ControlLogix w/1769-ADN DeviceNet Example Ladder Program 8-19 Figure 8.21 Example ControlLogix Ladder Logic CH3 Subroutine 1769-SM2 Channel 3 Subroutine The following i rungs display some of the Logic Status bits from the drive. Refer to Appendix D in the 1769-SM2 user manual for additional information about the Logic Status word. SM2_Input_Data[7].0 CH3_Ready SM2_Input_Data[7].1 CH3_Active SM2_Input_Data[7].3 CH3_Forward SM2_Input_Data[7].7 CH3_Fault SM2_Input_Data[7].
8-20 ControlLogix w/1769-ADN DeviceNet Example Ladder Program Figure 8.21 Example ControlLogix Ladder Logic CH3 Subroutine (Continued) CH3_Forward_Cmd SM2_Output_Data[5].4 CH3_Forward_Cmd / SM2_Output_Data[5].5 11 12 13 14 (End) This rung displays the Reference being sent to the drive. An integer represents the xxx.x Hz format (decimal is implied) used by the drive, so a displayed value of "300" equates to 30.0 Hz.
ControlLogix w/1769-ADN DeviceNet Example Ladder Program Example Program Data Table In this example program, the following controller tags are used: Figure 8.
8-22 ControlLogix w/1769-ADN DeviceNet Example Ladder Program An example of Input/Output values are shown below: Figure 8.23 1769-SM2 Input Data Figure 8.
Chapter 9 Troubleshooting This chapter provides information for troubleshooting potential problems with 1769-SM2 module and network. Topic Locating the Status Indicators MODULE Status Indicator CH1…CH3 Status Indicators Viewing Module Diagnostic Items Viewing and Clearing Events Page 9-1 9-2 9-3 9-4 9-6 Locating the Status Indicators The 1769-SM2 module has four status indicators. They can be viewed on the front of the module. See Figure 9.1. Figure 9.
9-2 Troubleshooting MODULE Status Indicator The MODULE status indicator is a bicolor red and green LED. Status Cause Corrective Action Off The module is not powered. Apply power to the module. Flashing Red The module’s configuration data • Change the controller configuration is not valid. data to valid settings. • Reset the module parameters to their default settings, and then reset the module. Steady Red The module is unable to Cycle power to the controller.
Troubleshooting 9-3 CH1…CH3 Status Indicators The CH1, CH2, and CH3 status indicators are bicolor red and green LEDs. Status Cause Corrective Action Off The module is not powered. • Apply power to the module. The channel is not connected to • Apply power to the PowerFlex 4-Class a PowerFlex 4-Class DSI drive. DSI drive. • Connect the module channel to the The channel is set for Modbus RTU Master operation, but is not drive using a communications cable. transmitting.
9-4 Troubleshooting Viewing Module Diagnostic Items Diagnostic items are provided for each respective channel. The following diagnostic items can be accessed using DriveExplorer v3.01 (or higher). Table 9.A Diagnostic Items for Module in Single Mode No. Name Description 1 Reserved — 2 Logic Cmd Current value of the product-specific Logic Command being transmitted to the drive by this module.
Troubleshooting 9-5 Table 9.B Diagnostic Items for Module in Multi-Drive Mode (Continued) No. Name Description 9 Drv 1 Logic Sts Current value of the product-specific Logic Status being received from Drive 1 by this module. 10 Drv 1 Feedback Current value of the product-specific Feedback being received from Drive 1 by this module. 11 Drv 2 Logic Cmd Current value of the product-specific Logic Command being transmitted to Drive 2 by this module.
9-6 Troubleshooting Viewing and Clearing Events The module has an event queue to record significant events that occur in the operation of the module. When such an event occurs, an entry is put into the event queue. You can view the event queue using DriveExplorer v3.01 (or higher) software. Figure 9.2 DriveExplorer Event View/Clear Screen The event queue can contain up to 32 entries. Eventually the event queue will become full, since its contents are retained through module resets.
Troubleshooting 9-7 Table 9.C Module Events (Continued) Code Event Description 7-9 — Reserved DSI Events 10 Slave Detected The module detected that the slave has been connected. 11 Slave Removed The module detected that the slave has been disconnected. 12 Slave Logon The module has established communications with the slave. 13 Slave Timeout The module has lost communications with the slave. 14 Slave Brand Flt The slave brand is different than the module.
9-8 Troubleshooting Table 9.C Module Events (Continued) Code Event Description 52 Msg Ctrl Open The module has begun receiving Client-Server Control messages (the Client-Server Control Timeout was previously set to a non-zero value). 53 Msg Ctrl Close The device sending Client-Server Control messages to the module has set the Client-Server Control Timeout to a value of zero.
Appendix A Specifications Appendix A presents the specifications for the module.
A-2 Specifications Environmental Temperature Operating Storage Relative Humidity Atmosphere Shock Operational Non-Operational Vibration Operational Non-Operational -10…50 °C (14…122 °F) -40…85 °C (-40…185 °F) -5…95% non-condensing Important: The module must not be installed in an area where the ambient atmosphere contains volatile or corrosive gas, vapors, or dust.
Appendix B Module Parameters Appendix B provides information about the 1769-SM2 module parameters. Topic About Parameter Numbers Parameter List Page B-1 B-1 About Parameter Numbers The parameters in the module are numbered consecutively. Configuration Tool Numbering Scheme • DriveExplorer The module parameters begin with parameter 01. For example, Parameter 01 - [Config Mode] is parameter 01 as indicated by this manual.
B-2 Module Parameters Parameter No. Name and Description 03 [Reset Module] Details Default: No action if set to “0” (Ready). Resets the module Values if set to “1” (Reset Module). Restores the module to its factory default settings if set to “2” (Set Defaults). This parameter is a command. It will be Type: reset to “0” (Ready) after the command has been Reset Required: performed. ! 04 05 ATTENTION: Risk of injury or equipment damage exists.
Module Parameters [Drv 0 Addr 1] [Drv 1 Addr 1] [Drv 2 Addr 1] [Drv 3 Addr 1] [Drv 4 Addr 1] Sets the corresponding node addresses of the daisy-chained CH1 drives when the module is in Multi-Drive mode. 14 Drive 4 Drive 3 Drive 2 Drive 1 Drive 0 Default Bit Not Used Type: Bit Definition 09 10 11 12 13 xxx0 0000 0 = Drive Active 1 = Drive Inactive Read Only Not Used Displays the CH1 drives that are active in Multi-Drive mode. Details Default: Bit Values: Not Used Parameter No.
B-4 Module Parameters Parameter No. Name and Description 17 [RTU Tx Delay 1] 18 19 Details Default: Sets the CH1 inter-frame delay used to delay the Minimum: sending of a transmit packet when the module is in Maximum: Type: Multi-Drive mode and Parameter 07 - [DSI I/O Reset Required: Cfg 1] is set to “5” (RTU Master). If this value is set to 0 (zero), the ModBus default delay of 3.5 character times is used.
Module Parameters [Drv 0 Addr 2] [Drv 1 Addr 2] [Drv 2 Addr 2] [Drv 3 Addr 2] [Drv 4 Addr 2] Sets the corresponding node addresses of the daisy-chained CH2 drives when the module is in Multi-Drive mode. 29 Drive 4 Drive 3 Drive 2 Drive 1 Drive 0 Default Bit Not Used Type: Bit Definition 24 25 26 27 28 xxx0 0000 0 = Drive Active 1 = Drive Inactive Read Only Not Used Displays the CH2 drives that are active in Multi-Drive mode. Details Default: Bit Values: Not Used Parameter No.
B-6 Module Parameters Parameter No. Name and Description 32 [RTU Tx Delay 2] 33 34 Details Default: Sets the CH2 inter-frame delay used to delay the Minimum: sending of a transmit packet when the module is in Maximum: Type: Multi-Drive mode and Parameter 22 - [DSI I/O Reset Required: Cfg 2] is set to “5” (RTU Master). If this value is set to 0 (zero), the ModBus default delay of 3.5 character times is used.
Module Parameters [Drv 0 Addr 3] [Drv 1 Addr 3] [Drv 2 Addr 3] [Drv 3 Addr 3] [Drv 4 Addr 3] Sets the corresponding node addresses of the daisy-chained CH3 drives when the module is in Multi-Drive mode. 44 Drive 4 Drive 3 Drive 2 Drive 1 Drive 0 Default Bit Not Used Type: Bit Definition 39 40 41 42 43 xxx0 0000 0 = Drive Active 1 = Drive Inactive Read Only Not Used Displays the CH3 drives that are active in Multi-Drive mode. Details Default: Bit Values: Not Used Parameter No.
B-8 Module Parameters Parameter No. Name and Description 47 [RTU Tx Delay 3] 48 Details Default: Sets the CH3 inter-frame delay used to delay the Minimum: sending of a transmit packet when the module is in Maximum: Type: Multi-Drive mode and Parameter 37 - [DSI I/O Reset Required: Cfg 3] is set to “5” (RTU Master). If this value is set to 0 (zero), the ModBus default delay of 3.5 character times is used.
Appendix C CIP/DSI Objects Appendix C presents information about the CIP and DSI objects that can be accessed using Explicit Messages. For information on formatting Explicit Messages and example ladder logic programs, refer to the corresponding chapter: • Chapter 5, Understanding Explicit Messaging • Chapter 6, MicroLogix 1500 Example Ladder Programs • Chapter 7, CompactLogix Example Ladder Programs • Chapter 8, ControlLogix w/1769-ADN DeviceNet Example Ladder Program Object Class Code Hex.
C-2 CIP/DSI Objects Supported Data Types Data Type Description BYTE 8-bit unsigned integer WORD 16-bit unsigned integer DWORD 32-bit unsigned integer LWORD 64-bit unsigned integer SINT 8-bit signed integer USINT 8-bit unsigned integer INT 16-bit signed integer UINT 16-bit unsigned integer DINT 32-bit signed integer UDINT 32-bit unsigned integer BOOL 8-bit value -- low bit is true or false BOOL[n] Array of n bits STRING[n] Array of n characters SHORT_STRING 1-byte length indica
CIP/DSI Objects C-3 CIP Identity Object Class Code Hexadecimal 0x01 Decimal 1 Services Service Code 0x01 0x0E Implemented for: Class Instance Yes Yes Yes Yes Service Name Get_Attributes_All Get_Attribute_Single Class Attributes Attribute ID 1 2 6 Access Rule Get Get Get 7 Get Name Data Type Description Revision Max Instance Max ID Number of Class Attributes Max ID Number of Instance Attributes UINT UINT UINT 1 1 7 UINT 7 Instance Attributes Attribute ID 1 2 3 Access Rule Get Get Get 4
C-4 CIP/DSI Objects CIP Parameter Object Class Code Hexadecimal 0x0F Decimal 15 Instances The parameters for the DSI devices can be accessed using the instance-offset encoding shown in the table below: Instances (Dec.
CIP/DSI Objects C-5 CIP Parameter Object (Continued) Instance Attributes Attribute Access Name ID Rule (1) Parameter Value 1 2 Get Link Path Size Data Type Description (2) (3) USINT 0 = No link specified n = The size of Attribute 3 in bytes (4) 3 4 Get Get Link Path Descriptor WORD 5 Get Data Type USINT 6 7 Get Get Get 9 Get Help String USINT SHORT_ STRING SHORT_ STRING SHORT_ STRING (3) 8 Data Size Parameter Name String Units String 10 11 12 13 14 15 16 17 18 19 20 21 Get Get Get G
C-6 CIP/DSI Objects CIP Parameter Object (Continued) Services Service Code 0x01 0x05 0x0E 0x10 0x4B 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
CIP/DSI Objects C-7 DSI Device Object Class Code Hexadecimal 0x92 Decimal 146 Services Service Code 0x0E 0x10 Implemented for: Class Instance Yes Yes Yes Yes Service Name Get_Attribute_Single Set_Attribute_Single 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, Class Attribute 4. Instances (Dec.
C-8 CIP/DSI Objects DSI Device Object (Continued) Class Attributes (Continued) Attribute Access Name ID Rule 3 Get Product Series Data Type Description BYTE 4 Get Number of Components BYTE 5 Set User Definable Text STRING[16] 6 7 8 Get Get Get Status Text Configuration Code Configuration Text STRING[12] BYTE STRING[16] 9 11 Get Get Brand Code NVS Checksum WORD WORD 12 13 Get Get Class Revision WORD Character Set Code BYTE 1=A 2 = B… Number of components (for example, main control bo
CIP/DSI Objects DSI Device Object (Continued) Instance Attributes Attribute ID 3 4 Access Name Rule Get Component Name Get Component Firmware Revision 5 Get 6 Get 7 Get 8 Get Component Hardware Change Number First Flash Object Instance Number of Flash Object Instances Component Serial Number Data Type Description STRING[32] STRUCT of: BYTE BYTE BYTE Name of the component DWORD Major Revision Minor Revision Value between 0x00 and 0xFFFFFFFF C-9
C-10 CIP/DSI Objects DSI Parameter Object Class Code Hexadecimal 0x93 Decimal 147 Instances The number of instances depends on the number of parameters in the device. The total number of parameters can be read in Instance 0, Attribute 0. Instances (Dec.
CIP/DSI Objects C-11 DSI Parameter Object (Continued) Instance Attributes Attribute Access Name ID Rule 7 Get DSI Online Read Full 8 9 11 Get DSI Descriptor Get/Set DSI Parameter Value Get/Set DSI RAM Parameter Value Get/Set DSI Link 12 Get 13 Get 10 14 Get 15 Get 16 Get (1) Help Object Instance DSI Read Basic DSI Parameter Name DSI Parameter Alias Parameter Processing Error Data Type Description STRUCT of: BOOL[32] CONTAINER(1) CONTAINER CONTAINER CONTAINER WORD WORD STRING[4] UINT UI
C-12 CIP/DSI Objects DSI Parameter Object (Continued) Descriptor Attributes Bit 0 1 2 Name Data Type (Bit 1) Data Type (Bit 2) Data Type (Bit 3) 3 Sign Type 4 Hidden 5 Not a Link Sink 6 Not Recallable 7 ENUM 8 Writable 9 Not Writable When Enabled Instance 10 11 12 13 14 15 16 17 18 Reserved Decimal Place (Bit 0) Decimal Place (Bit 1) Decimal Place (Bit 2) Decimal Place (Bit 3) Extended Data Type (Bit 1) Extended Data Type (Bit 2) Extended Data Type (Bit 2) Description Right bit is least
CIP/DSI Objects C-13 DSI Parameter Object (Continued) Descriptor Attributes (Continued) Bit 19 20 21 22 23 24 25 26 Name Parameter Exists Not Used Formula Links Access Level (Bit 1) Access Level (Bit 2) Access Level (Bit 3) Writable ENUM Not a Link Source 27 28 29 30 31 Enhanced Bit ENUM Enhanced ENUM Not Used Not Used Not Used Description Reserved Reserved Reserved Reserved Reserved Reserved Reserved 0 = Parameter can be a source for a link 1 = Parameter cannot be a source for a link Reserved Reserve
C-14 CIP/DSI Objects DSI Fault Object Class Code Hexadecimal 0x97 Decimal 151 Products such as PowerFlex drives use this object for faults. Modules use this object for events. Services Service Code 0x0E 0x10 Implemented for: Class Instance Yes Yes Yes Yes Service Name Get_Attribute_Single Set_Attribute_Single 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.
CIP/DSI Objects C-15 DSI Fault Object (Continued) Class Attributes (Continued) Attribute Access Name ID Rule 5 Get Fault Data List 6 Get 7 Get Number of Recorded Faults Fault Parameter Reference Data Type Description STRUCT of: BYTE BYTE WORD[n] WORD Reserved WORD Number of faults/events in the queue. A “0” indicates the fault queue is empty.
C-16 CIP/DSI Objects DSI Diagnostic Object Class Code Hexadecimal 0x99 Decimal 153 Services Service Code Implemented for: Class Instance Yes Yes Yes Yes 0x0E 0x10 Service Name Get_Attribute_Single Set_Attribute_Single Instances The number of instances depends on the maximum number of diagnostic items in the device. The total number of diagnostic items can be read in Instance 0, Attribute 2. Instances (Dec.
CIP/DSI Objects C-17 DSI Diagnostic Object (Continued) Instance Attributes Attribute Access Name ID Rule 0 Get Full/All Info 1 (1) Get/Set Value Data Type STRUCT of: BOOL[32] CONTAINER (1) CONTAINER CONTAINER CONTAINER WORD WORD STRING[4] UINT UINT UINT INT DWORD STRING[16] Various Description Descriptor (see pages C-12 and C-13) Value Minimum value Maximum value Default value Pad Word Pad Word Units (e.g.
C-18 Notes: CIP/DSI Objects
Appendix D PowerFlex 4-Class Drives Logic Command/Status Words Appendix D provides the definitions of the Logic Command/Logic Status words that are used for some drives that can be connected to the 1769-SM2 module. If the Logic Command/Logic Status for the drive that you are using is not listed, refer to your drive’s documentation.
D-2 PowerFlex 4-Class Drives Logic Command/Status Words Logic Status Word Logic Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 x x x x x x x x x x x x x x x (1) (2) 0 Status x Ready Description 0 = Not Ready 1 = Ready Active 0 = Not Active 1 = Active Command 0 = Reverse Direction 1 = Forward Actual Direction 0 = Reverse 1 = Forward Accel 0 = Not Accelerating 1 = Accelerating Decel 0 = Not Decelerating 1 = Decelerating Alarm 0 = No Alarm 1 = Alarm Fault 0 = No Fault 1 = Fault At Speed 0 = Not At Ref
Glossary C CIP (Common Industrial Protocol) CIP is the transport and application layer protocol used for messaging over EtherNet/IP, ControlNet, and DeviceNet networks. The protocol is used for implicit messaging (real time I/O) and explicit messaging (configuration, data collection, and diagnostics). Class A class is defined by the DeviceNet specification as “a set of objects that all represent the same kind of system component. A class is a generalization of an object.
Glossary-2 DSI Peripheral A device that provides an interface between DSI and a network or user. Peripheral devices are also referred to as “adapters” or “modules.” The 1769-SM2 module, 1203-USB or 22-SMC-232 converter, and PowerFlex 4-Class HIMs (22-HIM-A3 or 22-HIM-C2S) are examples of DSI peripherals. DSI Product A device that uses the DSI communications interface to communicate with one or more peripheral devices. For example, a motor drive such as a PowerFlex 4-Class drive is a DSI product.
Glossary-3 H HIM (Human Interface Module) A device that can be used to configure and control a drive. PowerFlex 4-Class HIMs (22-HIM-A3 or 22-HIM-C2S) can be used to configure PowerFlex 4-Class drives and their connected peripherals. Hold Last When communication is disrupted (for example, the controller is idle), the module and PowerFlex drive can respond by holding last. Hold last results in the drive receiving the last data received via the network connection before the disruption.
Glossary-4 P PCCC (Programmable Controller Communications Command) PCCC is the protocol used by some controllers to communicate with devices on a network. Some software products (for example, DriveExplorer and DriveExecutive) also use PCCC to communicate. PowerFlex 4-Class (Component Class) Drives The Allen-Bradley PowerFlex 4-Class family of drives supports DSI and includes the PowerFlex 4, PowerFlex 4M, PowerFlex 40, PowerFlex 40P, and PowerFlex 400.
Glossary-5 S Scanner A scanner is a separate module (of a multi-module controller) or a built-in component (of a single-module controller) that provides communication with modules connected to a network. See also Controller. Status Indicators Status indicators are LEDs that are used to report the status of the module, network, and drive. They are on the front of the module. Z Zero Data When communication is disrupted (for example, the controller is idle), the module and drive can respond with zero data.
Glossary-6 Notes:
Index A adapter, see module applying power to the module, 2-14 assembling module to the controller, 2-5 attentions, 1-7 B baud rate, see RTU baud rate bit definitions for Logic Command word, D-1 Logic Status word, D-2 C CH1…CH3 status indicators locating, 1-10 troubleshooting with, 9-3 CIP (Common Industrial Protocol), G-1 CIP/DSI objects list, C-1 class, G-1 communications cables, 1-6, 2-10 CompactLogix example ladder program Multi-Drive mode 1769-SM2 settings, 7-12 20-COMM-H settings, 7-12 CH3 Modbus R
Index-2 ControlLogix w/1769-ADN example ladder program 1769-SM2 input/output data, 8-22 registering the EDS file, 8-8 settings, 8-12 controller tags, 8-21 main routine/subroutines, 8-13 to 8-20 Multi-Drive mode, 8-13 PowerFlex 40 settings, 8-12 setting up the 1769-ADN, 8-4 Single mode, 8-1 Single mode system arrangement, 8-2 D DeviceNet definition, G-1 specification, G-1 dimensions of module, A-1 DriveExecutive accessing parameters with, 3-2 supported feature, 1-2 DriveExplorer accessing parameters with, 3
Index-3 H HIM (Human Interface Module) accessing parameters with, 3-13 definition, G-3 hold last configuring the module for, 3-15 definition, G-3 I I/O configuring the module for, 3-14 definition, G-3 image examples, 3-2, 4-2 image table, 3-1, 4-1 module control word, 4-2 module status word, 4-3 understanding the I/O image, 4-1 using Reference/Feedback, 4-4 Identity object, C-3 idle action configuring the module for, 3-15 definition, G-3 Idle Action 1 parameter, B-2 Idle Action 2 parameter, B-4 Idle Actio
Index-4 module applying power, 2-14 assembling to the controller, 2-5 compatible products, 1-6 components, 1-1 connecting drives to, 2-10 control word, 4-2 controller mode, 3-3 dimensions, A-1 features, 1-2 flash updating, 3-22 grounding, 2-12 illustration, 1-1 installing, 2-1 to 2-15 mounting, 2-6 operating status, 2-15 parameter mode, 3-12 parameters, B-1 to B-8 removing power, 2-2 replacing within a system, 2-9 resetting, 3-20 selecting configuration mode, 2-3 setting Configuration Mode Switch (SW1), 2-3
Index-5 related documentation, P-1 removing power from the module, 2-2 replacing module within a system, 2-9 Reset Module parameter, B-2 resetting the module, 3-20 RSLinx, P-3, 8-2 RSLogix 500/5000, G-4 RSNetWorx for DeviceNet definition, G-4 setting up RSLinx for, 8-2 using, 8-3 web site, G-4 RTU Baud Rate 1 parameter, B-3 RTU Baud Rate 2 parameter, B-5 RTU Baud Rate 3 parameter, B-7 RTU baud rate definition, G-4 RTU Format 1 parameter, B-3 RTU Format 2 parameter, B-5 RTU Format 3 parameter, B-7 RTU Master
Index-6
U.S. Allen-Bradley 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 www.rockwellautomation.com Power, Control and Information Solutions Headquarters Americas: Rockwell Automation, 1201 South Second Street, Milwaukee, WI 53204-2496 USA, Tel: (1) 414.382.2000, Fax: (1) 414.382.
