Interbus Communications Module M/N RECOMM-IBUS Instruction Manual D2-3480-1
The information in this manual is subject to change without notice. Throughout this manual, the following notes are used to alert you to safety considerations: ! ATTENTION:Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Important: Identifies information that is critical for successful application and understanding of the product.
CONTENTS Chapter 1 Introduction 1.1 Interbus 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 Interbus Module Components........................................ 2-1 2.2 Required Equipment .................................................
Chapter 6 Using I/O Messaging 6.1 About I/O Messaging ..................................................... 6-1 6.2 Understanding the I/O Image......................................... 6-1 6.3 Using Logic Command/Status ....................................... 6-4 6.4 Using Reference/Feedback ........................................... 6-4 6.5 Using Datalinks .............................................................. 6-4 6.5.1 Rules for Using Datalinks .................................... 6-4 6.5.
List of Figures Figure 2.1 – Components of the Interbus Module....................................... 2-1 Figure 3.1 – Sample Network Wiring .......................................................... 3-3 Figure 3.2 – DPI Ports and Internal Interface Cables ................................ 3-4 Figure 3.1 – Mounting and Grounding the Interbus Module ....................... 3-5 Figure 4.1 – Accessing the Interbus Parameters using the LCD OIM ........ 4-2 Figure 4.2 – I/O Configuration Screen on an LCD OIM ....
Figure 7.1 – Explicit Message Process ....................................................... 7-2 Figure 7.2 – Memory Map ........................................................................... 7-4 Figure 7.3 – Reading Accel Time 1 (140) from an SP600 Drive (DPI Host)7-7 Figure 7.4 – Reading Fault 1 Time (244) from an SP600 Drive (DPI Host) 7-8 Figure 7.5 – Reading PIDD W0 Actual (21) from an RECOMM-IBUS Interbus Module ...................................................................... 7-9 Figure 7.
List of Tables Table 2.1 – Equipment Shipped with the Interbus Module ......................... 2-2 Table 2.2 – Required User-Supplied Equipment ........................................ 2-2 Table 3.1 – Bus In Connector (From Previous Node on the Network)........ 3-2 Table 3.2 – Bus Out Connector (To Next Node on the Network)................ 3-2 Table 4.1 – Configuration Tools.................................................................. 4-1 Table 4.2 – PIDD / PODD Indexes ...............................
VIII Interbus Communications Module
CHAPTER 1 Introduction The Interbus module (RECOMM-IBUS) 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. • • D2-3485 SP600 AC Drive User Manual D2-3488 VS Utilities Getting Results Manual Online help installed with the software • 1747-6.2 SLC 500 Modular Hardware Style Installation and Operation Manual • 1747-6.
CHAPTER 2 Getting Started This chapter provides: • • • • 2.1 A description of the Interbus module components A list of parts shipped with the module A list of user-supplied parts required for installing the module An installation checklist Interbus Module Components Status Indicators DPI Connector Bus In Interbus Connector Bus Out Interbus Connector Five LEDs that indicate the status of the connected drive, module, and network.
2.2 Required Equipment Table 2.1 lists the equipment shipped with the Interbus module. When you unpack the module, verify that the package includes all of these items. Table 2.1 – Equipment Shipped with the Interbus Module Item Description One RECOMM-IBUS Interbus 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) LED labels Interbus Module User Manual (D2-3480) Table 2.
2.3 Installation Checklist This section is designed to help experienced users start using the Interbus module. If you are unsure about how to complete a step, refer to the referenced chapter. Step Action Refer to U 1 Review the safety precautions for the module. Throughout this manual U 2 Verify that the drive is properly installed. SP600 AC Drive User Manual U 3 Install the module. Verify that the drive is not powered.
2-4 Interbus Communications Module
CHAPTER 3 Installing the Interbus Module Chapter 3 provides instructions for installing the Interbus module on an SP600 drive. 3.1 Preparing for an Installation Before installing the Interbus module, verify that you have all required equipment. Refer to chapter 2, Getting Started, for a list of equipment. ! 3.2 ATTENTION:The Interbus module contains ESD(Electrostatic Discharge) sensitive parts that can be damaged if you do not follow ESD control procedures.
Table 3.1 – Bus In Connector (From Previous Node on the Network) Terminal Name Description 1 /DO1 Receive 2 DO1 Receive 3 /DI1 Transmit 4 DI1 Transmit 5 GND Ground Connection 6 PE Protective Earth . Table 3.
See figure 3.1 for an explanation of wiring an Interbus network. SST SLC Scanner DO DI COM 1 2 3 4 5 /DO /DI 6 7 8 Station 1 1 9 9-pin D-shell jumper Shield Bus Out (See Table 3.2) 2 3 /DO1 DO1 /DI1 4 DI1 5 Bus In (See Table 3.1) /DO2 DO2 /DI2 DI2 GND RBST PE 1 2 3 4 5 6 7 6 GND PE jumper /DO2 Station 2 1 2 /DO1 DO1 3 4 5 6 /DI1 DI1 GND PE Bus In (See Table 3.1) 1 Bus Out (See Table 3.2) DO2 /DI2 2 3 DI2 GND 4 5 RBST PE 6 7 Figure 3.
3.3 Connecting the Module to the Drive Step 1. Remove power from the drive. Step 2. Use static control precautions. Step 3. Connect the Internal Interface cable to the DPI port on the drive and then to the DPI connector on the module. Interbus Module SP600 Drive 1-20 HP @ 460 VAC SP600 Drive 25-40 HP @ 460 VAC # Description 15.24 cm (6 in) Internal Interface cable DPI Connector Interbus Connectors 2.54 cm (1 in) Internal Interface Cable Figure 3.
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 to secure and ground it to the drive. See figure 3.2. For 25-40 HP SP600 drives: Mount the module in the drive using the four captive screws to secure and ground it to the drive. All screws must be tightened to ground the module. Important: Drive Module Adapter Internal Interface cable folded behind the module and in front of the drive SP600 Drive Figure 3.
3-6 Step 2. Apply power to the SP600 drive. The module receives its power from the connected drive. When you apply power to the product for the first time, the status indicators should be green or off after initialization. Refer to chapter 8, Troubleshooting the Interbus Module and Network, for more information. Step 3. Apply power to the master device and other devices on the network.
CHAPTER 4 Configuring the Interbus Module Chapter 4 provides instructions and information for setting the parameters in the module. For a list of parameters, refer to Appendix B, Interbus Module Parameters. For definitions of terms in this chapter, refer to the Glossary. 4.1 Configuration Tools The Interbus 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 Interbus 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.
Step 2. If Logic Command/Reference is enabled, configure the parameters in the drive to accept the Logic and Reference from the module. For example, set Speed Ref A Sel (90) in an SP600 drive to “Network” so that the drive uses the Reference from the module. Also, verify that the mask parameters (for example, Manual Mask (286)) in the drive are configured to receive the desired logic from the module. Step 3.
To configure the module for Logic Command/Status, Reference/Feedback and the maximum number of Datalinks enabled in see the example in table 4.3. Table 4.
4.4 Setting a Fault Action By default, when communications are disrupted (for example, a cable is disconnected), the drive responds by faulting if it is using I/O from the network. You can configure a different response to communication disruptions using Comm Flt Action (6). ! ATTENTION:Comm Flt Action (6) lets you determine the action of the module and connected SP600 drive if communications are disrupted. By default, this parameter faults the drive.
4.4.2 Setting the Fault Configuration Parameters If you set Comm Flt Action (6) to “Send Flt Cfg,” the values in the following parameters are sent to the drive after a communications fault occurs. You must set these parameters to values required by your application. Table 4.5 – Fault Configuration Parameters Number Name Description 10 Flt Cfg Logic A 16-bit value sent to the drive for Logic Command.
4.4.3 Resetting the Module Changes to switch settings or some module parameters require that you reset the module before the new settings take effect. You can reset the module by cycling power to the drive or by using Reset Module (5). ! ATTENTION: If the module is transmitting control I/O to the drive, the drive may fault when you reset the module. Determine how your drive will respond before resetting a connected module.
4.5 Viewing the Module Configuration The parameters in table 4.6 provide information about how the module is configured. You can view these parameters at any time. Table 4.6 – Module Configuration Status Parameters No. Name and Description 01 DPI Port Port to which the module is connected. This will usually be port 5. 03 Ref/Fdbk Size Size of the Reference/Feedback. The drive determines the size of the Reference/Feedback.
Table 4.6 – Module Configuration Status Parameters (Continued) No. Name and Description 33 PIDD W6 Actual Actual Process Input Description for Word 6 Displays the Actual PIDD Config being transmitted to word 6 in the Interbus Master. PIDD W7 Actual Actual Process Input Description for Word 7 Displays the Actual PIDD Config being transmitted to word 7 in the Interbus Master.
4-10 Interbus Communications Module
CHAPTER 5 Configuring the Interbus 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 a module connected to a network. Interbus scanners are available from several manufacturers, including SST. Chapter 5 provides instructions on how to use Phoenix Contact CMD software to configure the network on an SST scanner. 5.
Fault LED COMM LED Interbus REMOTE OUT Config RS232 Port Interbus Scanner in Multi-Module Controller SP600 Drive Station 1.0 (CR=2) SP600 Drive Station 2.0 (CR=3) Figure 5.1 – Sample Interbus Network 5.2 Configuring the Module for use with the Ladder Examples Prior to setting up the SST Interbus scanner with CMD software, the parameters listed in table 5.1 need to be configured to use the sample ladder logic program. Table 5.
Table 5.
Figure 5.2 – Creating a New Interbus Project using CMD Step 2. Right-click on the Project icon and select Description. Enter a name for the project and any additional information desired, as shown in figure 5.3. Click OK when complete. SP600 Interbus Demo An SP600 Interbus demonstration program using an SLC-5/05 system with an SST-IBS-SLC Interbus scanner. Figure 5.3 – Entering a Name for the New Interbus Project Step 3. 5-4 Right-click on the PLC/PC icon and select Description.
Figure 5.4 – Entering a Name for the Interbus Controller Step 4. Right-click on the Program icon and select Description. Enter a name for the program (the actual RSLogix500 file name is recommended), and any additional information desired, as shown in figure 5.5. Click OK when complete. Using SP600 w/RECOMM-IBUS Figure 5.5 – Entering a Name for the Interbus Program Step 5. When complete, the representation area will look as shown in figure 5.6. SP600 Interbus Demo Figure 5.
This provides useful information regarding the CMD project being created: • “SP600 Interbus Demo” indicates what this project is for. • “SLC 5/05” indicates the controller used. • “Interbus_SLC_Demo” indicates that Interbus_SLC_Demo.RSS is the associated RSLogix500 program used with this system. Step 6. To configure the PC Com Port that CMD will use to communicate with the SST scanner, click on Options/ Settings and then the Driver tab. Step 7.
Figure 5.8 – Selecting the Interbus Controller Type Step 10. Right-click on the Controller Board icon and select Description. Enter “SST-IBS-SLC” in the name field, as shown in figure 5.9. Figure 5.9 – Entering a Description for the Controller Board Step 11. When complete, the representation area will look as shown in figure 5.10.
. SP600 Interbus Demo Figure 5.10 – Sample Interbus CMD Project Step 12. From the pull-down menu select Configuration/ Configuration Frame/Read In and answer Yes to changing the operating state to Configuration Online. If there are additional prompts, answer OK or Yes to perform the read anyway. CMD will then read the bus configuration. (See figure 5.11.) SP600 Interbus Demo Figure 5.11 – CMD Bus Configuration The gray PCP icons represent each SP600 drive.
Step 13. Right-click on the SST-IBS-SLC scanner and select Process Data. This shows the Interbus I/O mapping for each device on the network, as shown in figure 5.12. Figure 5.12 – Sample Interbus I/O Mapping In the example, the length is 144 bits (9 words) because the RECOMM-IBUS was previously configured for the maximum I/O configuration. (See section 4.3, Setting the I/O Configuration. Depending on your application needs, this length may be less.
The mapping in the scanner is set up in bytes. Inputs to the scanner start at byte #512 and outputs start at byte #0. PIDD/PODD parameter settings in the module determine the length of I/O data mapped. In the example, each device is configured for 9 words (144 bits) of inputs and 9 words (144 bits) of outputs, the maximum allowed for each device. Using the PIDD/PODD values previously set in the RECOMM-IBUS module, the I/O layout in the scanner is as shown in table 5.2. Table 5.
Step 14. Right-click on the 1.0 PCP icon and select Description. Enter a Station Name such as “SP600 Demo #1”. Note the Communication Reference (CR) is 2. The CR needs to be known when using PCP communication services (explicit messaging). (See figure 5.14.) SP600 Demo #1 Figure 5.14 – Entering a Station Name Step 15. Click on the Parameter Channel button. Set Transmit and Receive to 128 bytes and enable Read, Write, and Get-0D (long format) services, as shown in figure 5.15. Click OK when complete.
Figure 5.15 – Selecting Data for the Parameter Channel Screen Step 16. Repeat steps #14 and #15 using the 2.0 PCP icon . Enter a Station name such as “SP600 Demo #2”. Note the Communication Reference (CR) is 3. The CR needs to be known when using PCP communication services (explicit messaging). Click OK when complete. Step 17. When complete, the representation area will look as shown in figure 5.16.
SP600 Demo #1 SP600 Demo #2 Figure 5.16 – Sample SP600 Demo #2 Step 18. Right-click on the SST-IBS-SLC icon and select Parameterization/Execute. Select “Startup without PDP” as shown in figure 5.17, and click OK. This uses the mapping already set up in the scanner and does not allow re-mapping by the software tool.
. Figure 5.17 – Selecting Data for Parameterization/Execute Screen If parameterization execution is successful, there will be a prompt to click OK. Click OK. Step 19. When complete, the representation area will look as shown in figure 5.18. SP600 Demo #1 SP600 Demo #2 Figure 5.18 – Sample Parameterization Execution Step 20. Click File/Save from the pull-down menu and save the project.
5.4 Configuring the SP600 Drive for use with the Ladder Examples Configure the parameters as shown in table 5.4 to use the sample ladder logic program. Table 5.
5.5 Configuring the RSLogix 500 SST Interbus Scanner The SST Interbus scanner is configured by clicking on the I/O Configuration in RSLogix500. The SST-IBS-SLC scanner has an ID Code of 13635. The settings in figures 5.19 and 5.20 are used by the sample ladder logic program. Figure 5.19 – Scanner I/O Configuration Figure 5.
Table 5.
5-18 Interbus Communications Module
CHAPTER 6 Using I/O Messaging Chapter 6 provides information and examples that explain how to use I/O Messaging to control an SP600 drive. ! 6.1 ATTENTION: The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application. Rockwell Automation does not assume responsibility or liability (to include intellectual property liability) for actual use of the examples shown in this publication.
The I/O image table will vary based on the following: • Size (either 16-bit or 32-bit) of the Reference/Feedback word and Datalink words used by the drive. • Configuration of DPI I/O Config (8) in the module. If all I/O is not enabled, the image table is truncated. The image table always uses consecutive words starting at word 0. Figure 6.1 illustrates an example of an I/O image with 16-bit words.
An image that uses 32-bit words for Reference and Datalinks would change the I/O image as follows: Word I/O 0 Logic Command/Status 1-2 Reference/Feedback 3-6 Datalink A1/A2 7 - 10 Datalink B1/B2 Figure 6.2 illustrates an example of an I/O image that does not use all of the I/O data. Only the Logic Command/Reference and Datalink B are enabled. In this example, the Reference is a 32-bit word, and Datalinks are 16-bit words.
6.3 Using Logic Command/Status When enabled, the Logic Command/Status word is always word 0 in the I/O image. The Logic Command is a 16-bit word of control produced by the scanner and consumed by the module. The Logic Status is a 16-bit word of status produced by the module and consumed by the scanner. This manual contains the bit definitions for compatible products available at the time of publication in Appendix C, Logic Command/ Status Words. For other products, refer to their documentation. 6.
• When you use a Datalink to change a value, the value is not written to the Non-Volatile Storage (NVS). The value is stored in volatile memory and lost when the drive loses power. 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.
Example: Power Up Marker (242) = 88.4541 hours MSW = 13decimal = 1101binary = 219 + 218 + 216 = 851968 LSW = 32573 851968 + 32573 = 884541 6.6 Sample SLC Ladder Logic Program The sample Interbus program uses an SLC processor with an SST Interbus scanner (SST-IBS-SLC) in the first slot of the rack and works with SP600 drives.
SLC Data Table Read Data The scanner is configured for 18 bytes (9 words) of inputs for each drive, the maximum amount allowed. Two drives require 36 bytes (18 words) maximum. Station 1 Address Station 2 Address Function I:1.0 I:1.9 Logic Status I:1.1 I:1.10 Feedback I:1.2 I:1.11 Datalink A1 I:1.3 I:1.12 Datalink A2 I:1.4 I:1.13 Datalink B1 I:1.5 I:1.14 Datalink B2 I:1.6 I:1.15 Datalink C1 I:1.7 I:1.16 Datalink C2 I:1.8 I:1.
6.6.1 Sample SLC Ladder Logic - Main Program The following rung performs power-up initialization of the PCP Read and PCP Write routines. First Pass S:1 0000 15 Execute PCP Read Subroutine B3:47 U 0 PCP Read Routine 1-shot B3:47 U 1 PCP Read Reply Msg 1-Shot B3:47 U 2 Execute PCP Write Subroutine B3:47 U 10 PCP Write Routine 1-shot B3:47 U 11 PCP Write Reply Msg 1-Shot B3:47 U 12 0001 0002 0003 0004 Execute LAD 3 - Station 1.
Controlling the Logic Command to the drive at Station 1.0. Station 1.0 Start Command B3:20 Station 1.0 Logic Command START O:1.0 0000 1 1 OTHER Station 1.0 Stop Command B3:20 Station 1.0 Logic Command STOP O:1.0 0 0 OTHER Station 1.0 Jog Command B3:20 Station 1.0 Logic Command JOG O:1.0 2 2 OTHER 0001 0002 Station 1.0 Clear Faults Command B3:20 Station 1.0 Logic Command CLEAR FAULTS O:1.0 3 3 OTHER 0003 Station 1.0 Reverse Command B3:20 Station 1.0 Logic Command FORWARD O:1.
Station 1.0 Datalink A2 Datalink A2 (Pr. 301) set to Deceleration Time 1 (Pr. 142) Station 1.0 Datalink A2 MOV Move Source 0008 Dest N19:3 50< O:1.3 50< Station 1.0 Datalink B1 Datalink B1 (Pr. 302) set to Jog Speed (Pr. 100) Station 1.0 Datalink B1 MOV Move Source 0009 Dest N19:4 100< O:1.4 100< Station 1.0 Datalink B2 Datalink B2 (Pr. 303) set to Stop Mode A (Pr. 155) Station 1.0 Datalink B2 MOV Move Source 0010 Dest N19:5 1< O:1.5 1< Station 1.0 Datalink C1 Datalink C1 (Pr.
6.6.2 Sample SLC Ladder Logic - Station 2 Program Controlling the Logic Command to the drive at Station 2.0. Station 2.0 Start Command B3:21 Station 2.0 Logic Command START O:1.9 0000 1 1 OTHER Station 2.0 Stop Command B3:21 Station 2.0 Logic Command STOP O:1.9 0 0 OTHER Station 2.0 Jog Command B3:21 Station 2.0 Logic Command JOG O:1.9 2 2 OTHER 0001 0002 Station 2.0 Clear Faults Command B3:21 Station 2.0 Logic Command CLEAR FAULTS O:1.9 3 3 OTHER 0003 Station 2.
Station 2.0 Datalink A2 Datalink A2 (Pr. 301) set to Deceleration Time 1 (Pr. 142) Station 2.0 Datalink A2 MOV Move Source 0008 Dest N19:17 50< O:1.12 50< Station 2.0 Datalink B1 Datalink B1 (Pr. 302) set to Jog Speed (Pr. 100) Station 2.0 Datalink B1 MOV Move Source 0009 Dest N19:18 100< O:1.13 100< Station 2.0 Datalink B2 Datalink B2 (Pr. 303) set to Stop Mode A (Pr. 155) Station 2.0 Datalink B2 MOV Move Source 0010 Dest N19:19 1< O:1.14 1< Station 2.0 Datalink C1 Datalink C1 (Pr.
CHAPTER 7 Using Explicit Messaging (PCP Communications) Chapter 7 provides information and examples that explain how to use Explicit Messaging to monitor and configure the module and connected SP600 drive, as well as other peripherals. ! ATTENTION: The examples in this publication are intended solely for purposes of example. There are many variables and requirements with any application.
7.2 Running Explicit Messages There are five basic events in the Explicit Messaging process as shown in figure 7.1. The details of each step will vary depending on the controller. Refer to the documentation for your controller. Important: There must be a request message and a response message for all Explicit Messages, whether you are reading or writing data.
7.3 PCP Communications Peripheral Communications Protocol (PCP) messages are used for Explicit Messaging, which is not part of the normal Interbus I/O data scan. The scanner takes care of all of the details of establishing a connection for PCP communication services. PCP communications can be used to: • • • • Read or write DPI Host (SP600 drive, etc.) parameters Read or write RECOMM-IBUS parameters Read DPI Host (SP600 drive, etc.) faults Read RECOMM-IBUS events See table 7.1. Table 7.
Process Data (I/O Messaging) O/I:0 O/I M0/M1:0 M0/M1 M0/M1:(G:5-1) Command/Status word M0/M1:(G:5) M0/M1:(G:5+1) Command/Response Buffer (Explicit Messaging) M0/M1: (G:5+G:6-1) Figure 7.2 – Memory Map The ladder example used in this manual uses Input (I:) and Output (O:) files for I/O messaging (Logic Command/Status, Reference/Feedback, and Datalinks) and M Files for PCP messaging (See section 5.5, Configuring the RSLogix 500 SST Interbus Scanner.
7.3.1 PCP Read Message Format PCP Reads require the following Command and Reply message formats: Command Table 7.3 – Command Message Format Word Name Description 0 CR The Communication Reference (CR #) to read from 1 Index The index of the variable to read 2 Sub Index The sub-index of the variable to read (not used) Reply Table 7.
The sample ladder logic program simplifies addressing the various PCP indexes. Before calling the PCP Read Subroutine (figure 7.9), three registers are loaded to identify the variable to be read: Table 7.5 – PCP Read Main Program Data Register Description The Communication Reference (CR) to read from: Set to “2” to access Station 1.0 (CR=2) Set to “3” to access Station 2.
tion Des crip (He x) Valu e (De c) Valu e Add SLC Mes sag e ress 7.3.2 Read Examples Command N22:10 4 4 Command word = 4 = PCP Read (bit 2 ON) N22:11 2 2 CR# = 2 (Station 1.0) ndex=3000h+8Ch = 3000h + =8Ch = Accel IIndex Parameter 140Time [Accel(140) Time] 3001h start of SP600 (1) 3001h isisthethe start of PowerFlex 70parameters parameters (Pr.
4 2 2 N22:12 12532 Reply tion (He x) Command word = 4 = PCP Read (bit 2 ON) CR# = 2 (Station 1.0) 30F4 Index = 3000h + F4h = Fault 1 Time (244) Index =3000h+F4h = Parameter 244 [Fault 1 Time] 3001h is the start of SP600 parameters (1) 3001h is the start of PowerFlex 70 parameters (Pr.
tion Des crip (He x) Valu e (De c ) ss Valu e SLC Add re e sag Mes Command N22:10 4 4 Command word = 4 = PCP Read (bit 2 ON) N22:11 2 2 CR# = 2 (Station 1.0) Index =2FB5h+15h = 2FB5h + 15h = PIDD W021Actual Index = Parameter [PIDD(21) W0 Actual] N22:12 12234 2FCA 2FB6h 2FB6h isisthe thestart startofofthe RECOMM-IBUS parameters(Pr.
7.3.3 PCP Write Message Format PCP Writes require the following Command and Reply message formats: Command Table 7.
The sample ladder logic program simplifies addressing the various PCP indexes. Before calling the PCP Write Subroutine (figure 7.13), six registers are loaded to identify the variable to write: Table 7.10 – PCP Write Main Program Data Register Description The Communication Reference (CR) to write to: Set to “2” to access Station 1.0 (CR=2) Set to “3” to access Station 2.
Note that writing to parameters causes a non-volatile storage (NVS) write cycle and therefore must NOT be done frequently (can exceed the maximum number of allowable write cycles and cause the product to malfunction). Table 7.12 – PCP Write Subroutine Reply Message Register Description N23:20 = PCP Status Word. N23:21 = Echo of the Command word (0008h). N23:22 = Number of words following. N23:23 = CR. N23:24 = Result (“0” = good).
tion Des crip (He x) ) Valu e 2 CR# =2 (Station 1.0) 0 00== PowerFlex SP600 drive (DPI Host) Host) 70 (DPI 6A 2 Data Word 1 = 123 = 12.
tion CR# = 2 (Station 1.
Request N23:0 2 2 CR# = 2 (Station 1.
7.4 Sample SLC Ladder - Peripheral Communications Protocol (PCP) PCP Read Subroutine (Explicit Messaging) The PCP Read Subroutine is executed from the Main Program (chapter 6) by turning on bit B3:47/0. Only one PCP Read or Write can be performed at any one time. B3:47/0 will be turned off by the subroutine when the reading is complete and signals that another read (or write) cycle can take place.
N22:12 = Index (the parameter number or fault/event queue item to be read) N22:1 determines what area is to be read: 0002 N22:1 determines area is to be read: 0=SP600 (Host) what parameter (N22:2 + 12288 decimal (3000h) = mapped parameter address) 01=RECOMM-IBUS = PowerFlex 70 (Host) parameter(N22:2 (N22:2 decimal + 12288 decimal = mapped parameter address) parameter (2FB5h)(3000h) = mapped parameter address) 1 = 20-COMM-I parameter (N22:2(N22:2 + 12213+ decimal (2FB5h) =(2FF8h) mapped =parameter 2=SP600
Copy the PCP Read Command message to the scanner for transmission on the network. PCP Read Routine 1-shot B3:47 0004 1 0005 0006 0007 COP Copy File Source Dest Length #N22:10 #M0:1.0 4 The PCP Read Command 1-shot is used so the subroutine processes and sends the Command only once when called by the MAIN PGM PCP Read Routine 1-shot B3:47 L 1 When the scanner acknowledges the PCP Read command, turn the Command word PCP Read bit OFF (originally comes from N22:10 which was COPied to M0: above).
0010 If the PCP Read Reply message indicates that the result was "not good" (N22:24 <> 0), then zero out the data area of the Reply message (might contain leftover data from a previous successful PCP Read). PCP Read PCP Read PCP Read Status Reply Msg Reply Msg Reply Msg Message Data Word #1 Result 1-Shot Present MOV NEQ B3:47 M1:1.
7.4.1 PCP Write Subroutine (Explicit Messaging) The PCP Write Subroutine is executed from the Main Program (chapter 6) by turning on bit B3:47/10. Only one PCP Read or Write can be performed at any one time. B3:47/10 will be turned off by the subroutine when the reading is complete and signals that another read (or write) cycle can take place.
N23:14 = Number of bytes to write ("1" for byte, "2" for 16-bit parameter and "4" for 32-bit parameter) Data is contained in: N23:15 = Data word #1 to write (8-bit & 16-bit parameters, MSW of 32-bit parameters) N23:16 = Data word #2 to write (LSW of 32-bit parameters) 0004 If only 1 byte is being written, it needs to be loaded into the high byte of Data word #1 (N23:15). The subroutine performs this via the SWP instruction so the main program can work with a normal number (i.e.
Status Message Present M1:1.0 PCP Write Reply Msg 1-Shot B3:47 L 12 0009 15 0010 When the Command / Status Message handshake is complete, reset the 1-shot bits and exit the PCP Write routine by turning the "Execute PCP Write" bit off (B3:47/10) Command Status Execute Message Message PCP Write Acknowledge Present Subroutine M0:1.0 M1:1.0 B3:47 U 15 15 10 PCP Write Routine 1-shot B3:47 U 11 PCP Write Reply Msg 1-Shot B3:47 U 12 Command Message Acknowledge M0:1.0 U 15 END 0011 Figure 7.
CHAPTER 8 Troubleshooting the Interbus Module and Network Chapter 8 contains information for troubleshooting the Interbus module and the network. 8.1 Understanding the Status Indicators The Interbus module has five status indicators. They can be viewed on the module or through the drive cover. See figure 8.1. PWR STS CC RD TR BA Number Status Indicator Description Section CC Cable Check 8.1.1 RD Remote Bus Disable 8.1.2 TR Transmit/Receive 8.1.
Important: 8.2 Interbus compliance requires different LED functions than what is normally displayed on the front of the drive (Port, Mod, Net A and Net B LEDs). LED labels are provided with the module for application to the drive cover. Cable Check (CC) Status Indicator Table 8.1 – Cable Check (CC) Status Indicator: State Definitions Status Cause Off Master is reset or no cable connection. Solid Green Cable connection good. 8.
8.5 Bus Active (BA) Status Indicator Table 8.4 – Bus Active (BA) Status Indicator: State Definitions Status Cause Corrective Actions Off Bus not active. • Set master to start data transmission. Solid Green Bus active, exchanging data. • No action required. Flash Green Bus active, but no data exchange. • Set master to start data transmission. 8.6 Bus Voltage (UL) Status Indicator Table 8.
Table 8.6 – Module Diagnostic Items (Continued) No. Event Description 5 Prod Logic Sts The current value of the Product-Specific Status being received from the Host. 6 Feedback The current value of the Product-Specific Feedback being received from the Host. 7 Datalink A1 In The current value of Datalink A1 being transmitted to the Host. (Value of 0 if Datalink is not used). 8 Datalink A2 In The current value of Datalink A2 being transmitted to the Host. (Value of 0 if Datalink is not used).
Table 8.6 – Module Diagnostic Items (Continued) No. Event Description 24 DPI Rx Err Cntr The current value of the DPI CAN Receive error counter. 25 DPI Tx Err Cntr The current value of the DPI CAN Transmit error counter. 26 IbusImage Siz Amount of process data bytes used on the Interbus network by the module. 8.8 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.
Events Many events in the event queue occur under normal operation. If you encounter unexpected communications problems, the events may help you or Reliance Electric personnel troubleshoot the problem. Table 8.7 lists events that may appear in the event queue. Table 8.7 – Event Codes and Descriptions Code Event Description 1 No Event 2 DPI Bus Off Flt A bus-off condition was detected on DPI. This event may be caused by loose or broken cables or by noise.
Table 8.7 – Event Codes and Descriptions (Continued) Code 19 Event Description Message Timeout A Client-Server message sent by the peripheral was not completed. 20 DPI Fault Msg The DPI Host has faulted. 21 DPI Fault Clear The user cleared a fault in the module. 22 Normal Startup Peripheral completes a normal startup. 23 Net Comm Flt 24 Fault Cfg Error The peripheral detected a 32-bit fault configuration Reference when the Host supports only a 16-bit Reference, or vice-versa.
8-8 Interbus Communications Module
APPENDIX A Technical Specifications Communications Network Protocol Data Rates Interbus 500 K Drive Protocol Data Rates DPI 125 K or 500 K Electrical Consumption 450 mA at 5 V supplied through the drive Mechanical Dimensions Height Length Width 19 mm (0.75 in) 86 mm (3.33 in) 78.5 mm (3.09 in) Weight 65 g (2.
A-2 Interbus Communications Module
APPENDIX B Interbus Module Parameters The following information is provided for each Interbus 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: 0 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 K 1 = 500 K Default: 0 = 125 K 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 Ref/Fdbk Size Range: 0 = 16-bit 1 = 32-bit Default: 0 = 16-bit Type: Read Only Reset Required: N/A Size of the Reference/Feedback.
5 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.
7 Reserved Range: N/A Default: N/A Type: N/A Reset Required: N/A 8 DPI I/O Config Range: See figure B.1. Default: See figure B.1. Type: Read/Write Reset Required: N/A No t No Used t No Used tU Da sed ta Da link D t Da alink ta C Da link B ta Cm link A d/R ef I/O that is transferred 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.
9 DPI I/O Active Range: See figure B.2. Default: See figure B.2. Type: Read Only Reset Required: N/A No t No Used t No Used tU Da sed ta Da link D t Da alink tali C n Da k B ta Cm link A d/R ef I/O that the module is actively transmitting. The value of this parameter will usually be equal to the value of DPI I/O Config (8). 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.
11 Flt Cfg Ref Range: 0 to 4294967295 Default: 0 Type: Read/Write Reset Required: No Sets the Reference data that is sent to the drive if any of the following is true: • Comm Flt Action (6) is set to Send Flt Cfg and communications are disrupted. • Idle Flt Action (7) is set to Send Flt Cfg and the scanner is put into Program mode. Important: If the drive uses a 16-bit Reference, the most significant word of this value must be set to zero (0) or a fault will occur.
20 PIDD W0 Cfg Range: See table B.1 Default: 0x2F9A (Logic Status) Type: Read/Write Reset Required: No (becomes active when Interbus network is restarted) Configured Process Input Data Description for Word 0. PCP Object to use for Word 0 transmitted to Interbus master. 21 PIDD W0 Actual Range: See table B.1 Default: N/A Type: Read Only Reset Required: N/A Actual Process Input Data Description for Word 0. 22 PIDD W1 Cfg Range: See table B.
24 PIDD W2 Cfg Range: See table B.1 Default: 0 Type: Read/Write Reset Required: No (becomes active when Interbus network is restarted) Configured Process Input Data Description for Word 2. PCP Object to use for Word 2 transmitted to Interbus master. 25 PIDD W2 Actual Range: See table B.1 Default: N/A Type: Read Only Reset Required: N/A Actual Process Input Data Description for Word 2. 26 PIDD W3 Cfg Range: See table B.
28 PIDD W4 Cfg Range: See table B.1 Default: 0 Type: Read/Write Reset Required: No (becomes active when Interbus network is restarted) Configured Process Input Data Description for Word 4. PCP Object to use for Word 4 transmitted to Interbus master. 29 PIDD W4 Actual Range: See table B.1 Default: N/A Type: Read Only Reset Required: N/A Actual Process Input Data Description for Word 4. 30 PIDD W5 Cfg Range: See table B.
32 PIDD W6 Cfg Range: See table B.1 Default: 0 Type: Read/Write Reset Required: No (becomes active when Interbus network is restarted) Configured Process Input Data Description for Word 6. PCP Object to use for Word 6 transmitted to Interbus master. 33 PIDD W6 Actual Range: See table B.1 Default: N/A Type: Read Only Reset Required: N/A Actual Process Input Data Description for Word 6. 34 PIDD W7 Cfg Range: See table B.
36 PIDD W8 Cfg Range: See table B.1 Default: 0 Type: Read/Write Reset Required: No (becomes active when Interbus network is restarted) Configured Process Input Data Description for Word 8. PCP Object to use for Word 8 transmitted to Interbus master. 37 PIDD W8 Actual Range: See table B.1 Default: N/A Type: Read Only Reset Required: N/A Actual Process Input Data Description for Word 8. 38 PODD W0 Cfg Range: See table B.
40 PODD W1 Cfg Range: See table B.1 Default: 0X2F99 Type: Read/Write Reset Required: No (becomes active when Interbus network is restarted) Configured Process Output Data Description for Word 1. PCP Object to use for Word 1 received from Interbus master. 41 PODD W1 Actual Range: See table B.1 Default: N/A Type: Read Only Reset Required: N/A Actual Process Output Data Description for Word 1. 42 PODD W2 Cfg Range: See table B.
44 PODD W3 Cfg Range: See table B.1 Default: 0 Type: Read/Write Reset Required: No (becomes active when Interbus network is restarted) Configured Process Output Data Description for Word 3. PCP Object to use for Word 3 received from Interbus master. 45 PODD W3 Actual Range: See table B.1 Default: N/A Type: Read Only Reset Required: N/A Actual Process Output Data Description for Word 3. 46 PODD W4 Cfg Range: See table B.
48 PODD W5 Cfg Range: See table b.1 Default: 0 Type: Read/Write Reset Required: No (becomes active when Interbus network is restarted) Configured Process Output Data Description for Word 5. PCP Object to use for Word 5 received from Interbus master. 49 PODD W5 Actual Range: See table B.1 Default: N/A Type: Read Only Reset Required: N/A Actual Process Output Data Description for Word 5. 50 PODD W6 Cfg Range: See table B.
52 PODD W7 Cfg Range: See table B.1 Default: 0 Type: Read/Write Reset Required: No (becomes active when Interbus network is restarted) Configured Process Output Data Description for Word 7. PCP Object to use for Word 7 received from Interbus master. 53 PODD W7 Actual Range: See table B.1 Default: N/A Type: Read Only Reset Required: N/A Actual Process Output Data Description for Word 7. 54 PODD W8 Cfg Range: See table B.
56 PCP Comm Cfg Range: 0 = Disable 1 = Enable Default: 1 = Enable Type: Read/Write Reset Required: Yes Enable Interbus PCP communications. 57 PCP Comm Act Range: 0 = Disable 1 = Enable Default: 1 = Enable Type: Read Only Reset Required: N/A Actual PCP configuration. Table B.
APPENDIX C Logic Command/ Status Words Appendix C provides the definitions of the Logic Command/Logic Status words that are used for some products that can be connected to the Interbus module. If you do not see the Logic Command/Logic Status for the product that you are using, refer to your product’s documentation.
Logic Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Command x x x x 1 Description Reference Select 000 = No Command 001 = Ref. 1 (Ref A Select) 010 = Reserved 011 = Ref. 3 (Preset 3) 100 = Ref. 4 (Preset 4) 101 = Ref. 5 (Preset 5) 110 = Ref. 6 (Preset 6) 111 = Ref. 7 (Preset 7) MOP Decrement 0 = Not Decrement 1 = Decrement A 0 = Not Stop condition (logic 0) must first be present before a 1 = Start condition will start the drive.
Logic Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 x x x x Logic Command/Status Words Status Reference Description 0000 = Ref A Auto 0001 = Reserved 0010 = Preset 2 Auto 0011 = Preset 3 Auto 0100 = Preset 4 Auto 0101 = Preset 5 Auto 0110 = Preset 6 Auto 0111 = Preset 7 Auto 1000 = Term Blk Manual 1001 = DPI 1 Manual 1010 = DPI 2 Manual 1011 = DPI 3 Manual 1100 = DPI 4 Manual 1101 = DPI 5 Manual 1110 = DPI 6 Manual 1111 = Jog Ref C-3
C-4 Interbus Communications Module
GLOSSARY CMD software - (IBS CMD G4) A software package that enables configuration, monitoring, and diagnostics of all connected devices in an Interbus network. communications module - Devices such as drives, controllers, and computers usually require a module to provide a communication interface between them and a network such as Interbus. A 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.
DPI product - A device that uses the DPI communications interface to communicate with one or more peripheral devices. For example, a motor drive such as an SP600 drive is a DPI product. In this manual, a DPI product is also referred to as “product” or “host.” Explicit Messaging - see Peripheral Communications Protocol (PCP) Messaging.
The Logic Status is used to monitor the SP600 drive (for example, operating state, motor direction). It consists of one 16-bit word of output from the module to the network. The definitions of the bits in this word depend on the drive. master - see scanner non-volatile storage (NVS) - NVS is the permanent memory of a device. Devices such as the module and drive store parameters and other information in NVS so that they are not lost when the device loses power. NVS is sometimes called “EEPROM.
Glossary-4 Interbus Communications Module
INDEX A assistance, technical, 1-2 B BA status indicator, 8-3 bus active (BA) status indicator, 8-3 bus in Interbus connector location of, 2-1 terminals, 3-2 bus out Interbus connector location of, 2-1 terminals, 3-2 bus voltage (UL) status indicator, 8-3 C cable check (CC) status indicator, 8-2 cables, Internal Interface, 3-4 CC status indicator, 8-2 CMD software, 5-1 Comm Flt Action (6), B-3 communications specifications, A-1 configuration tools, 4-1 connector bus in Interbus, 2-1 bus out Interbus, 2-1
M mechanical specifications, A-1 module components, 2-1 configuration, viewing, 4-8 configuring, 4-1 to 4-9 connecting to drive, 3-4 connecting to network, 3-1 diagnostics items, 8-3 dimensions, A-1 features, 1-1 grounding, 3-5 installing, 3-1 to 3-6 mounting, 3-5 parameters, B-1 to B-16, ?? to B-16 resetting, 4-7 specifications, A-1 troubleshooting, 8-1 to 8-7 mounting the module, 3-5 N network configuring using CMD software, 5-1, 5-3 sample wiring, 3-3 O OIM (Operator Interface Module) configuring the m
T U TR status indicator, 8-2 transmit/receive (TR) status indicator, 8-2 troubleshooting, 8-1 to 8-7 UL status indicator, 8-3 V VS Utilities, documentation for, 1-2 Index Index-3
Index-4 Interbus Communications Module
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 Trademarks not belonging to Rockwell Automation are property of their respective companies. Publication D2-3480-1 - February 2002 Copyright © 2002 Rockwell Automation, Inc. All Rights Reserved. Printed in USA.
