Interbus

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.
The thick black bar shown on the outside margin of this page will be used throughout
this instruction manual to signify new or revised text or figures.
ATTENTION:The drive may contain high voltages that can cause

injury or death. Remove all power from the drive, and then verify power
has been removed before installing or removing an Interbus module.
! Failure to observe these precautions could result in severe bodily
injury or loss of life.
ATTENTION:Only qualified electrical personnel familiar with drive and
power products and the associated machinery should plan or
implement the installation, start up, configuration, and subsequent
maintenance of the product using an Interbus module. Read and
understand this manual in its entirety before proceeding. Failure to
observe these precautions could result in bodily injury and/or damage
to equipment.
ATTENTION:DPI host products must not be directly connected
together via RECBL-xxx cables. Unpredictable behavior due to timing
and other internal procedures can result if two or more devices are
connected in this manner. Failure to observe this precaution could
result in bodily injury and/or damage to equipment.
ATTENTION:Comm Flt Action (6) lets you determine the action of the
module and connected drive if communications are disrupted. By
default, this parameter faults the drive. You can set this parameter so
that the drive continues to run. Precautions should be taken to ensure
that the setting of this parameter does not create a hazard of injury or
equipment damage. Failure to observe this precaution could result in
bodily injury and/or damage to equipment.
ATTENTION: When a system is configured for the first time, there
may be unintended or incorrect machine motion. Disconnect the motor
from the machine or process during initial system testing. Failure to
observe this precaution could result in bodily injury and/or damage to
equipment.
ATTENTION:If the Interbus 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 the module. Failure to observe
this precaution could result in bodily injury and/or damage to
equipment
Interbus is a trademark of the Interbus Trade Organization.

Trademarks not belonging to Rockwell Automation are property of
Windows, Windows NT, and Microsoft are trademarks of Microsoft Corporation.
their respective
Reliance, SP600, VScompanies.
Utilities, DPI, and SLC are trademarks of Rockwell Automation.
©2002 Rockwell Automation. All rights reserved.

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 ...................................................... 2-2
2.3 Installation Checklist ...................................................... 2-3
Chapter 3 Installing the Interbus Module

3.1 Preparing for an Installation........................................... 3-1
3.2 Connecting the Module to the Network.......................... 3-1
3.3 Connecting the Module to the Drive .............................. 3-4
3.4 Applying Power.............................................................. 3-5
Chapter 4 Configuring the Interbus Module

4.1 Configuration Tools........................................................ 4-1
4.2 Using the LCD OIM to Configure the Module ................ 4-2
4.3 Setting the I/O Configuration ......................................... 4-2
4.4 Setting a Fault Action..................................................... 4-5
4.4.1 Changing the Fault Action ................................... 4-5
4.4.2 Setting the Fault Configuration Parameters ........ 4-6
4.4.3 Resetting the Module........................................... 4-7
4.5 Viewing the Module Configuration ................................. 4-8
Chapter 5 Configuring the Interbus Scanner

5.1 Configuring a Simple Network: An Example.................. 5-1
5.2 Configuring the Module for use with the Ladder
Examples....................................................................... 5-2
5.3 Configuring the Network Using CMD Software.............. 5-3
5.4 Configuring the SP600 Drive for use with the Ladder
Examples..................................................................... 5-15
5.5 Configuring the RSLogix 500 SST Interbus Scanner .. 5-16
Contents I
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.2 32-Bit Parameters using 16-Bit Datalinks ............ 6-5
6.6 Sample SLC Ladder Logic Program .............................. 6-6
6.6.1 Sample SLC Ladder Logic - Main Program ......... 6-8
6.6.2 Sample SLC Ladder Logic - Station 2 Program. 6-11
Chapter 7 Using Explicit Messaging (PCP Communications)

7.1 About Explicit Messaging............................................... 7-1
7.2 Running Explicit Messages............................................ 7-2
7.3 PCP Communications.................................................... 7-3
7.3.1 PCP Read Message Format................................ 7-5
7.3.2 Read Examples ................................................... 7-7
7.3.3 PCP Write Message Format .............................. 7-10
7.4 Sample SLC Ladder - Peripheral Communications
Protocol (PCP)............................................................. 7-16
7.4.1 PCP Write Subroutine (Explicit Messaging) ...... 7-20
Chapter 8 Troubleshooting the Interbus Module and Network

8.1 Understanding the Status Indicators.............................. 8-1
8.2 Cable Check (CC) Status Indicator................................ 8-2
8.3 Remote Bus Disable (RD) Status Indicator.................... 8-2
8.4 Transmit/Receive (TR) Status Indicator......................... 8-2
8.5 Bus Active (BA) Status Indicator.................................... 8-3
8.6 Bus Voltage (UL) Status Indicator.................................. 8-3
8.7 Module Diagnostic Items................................................ 8-3
8.8 Viewing and Clearing Events ......................................... 8-5
Appendix A Technical Specifications ...................................................... A-1
Appendix B Interbus Module Parameters ................................................ B-1
Appendix C Logic Command/Status Words............................................. C-1
Glossary ..................................................................................Glossary-1
Index ....................................................................................... Index-1
II Interbus Communications Module

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 .............................. 4-2
Figure 4.3 – Fault Action Screen on an LCD OIM ...................................... 4-5
Figure 4.4 – Reset Module Screen on an LCD OIM ................................... 4-7
Figure 5.1 – Sample Interbus Network ....................................................... 5-2

Figure 5.2 – Creating a New Interbus Project using CMD .......................... 5-4
Figure 5.3 – Entering a Name for the New Interbus Project ....................... 5-4
Figure 5.4 – Entering a Name for the Interbus Controller ........................... 5-5
Figure 5.5 – Entering a Name for the Interbus Program............................. 5-5
Figure 5.6 – Sample Interbus CMD Project ................................................ 5-5
Figure 5.7 – Selecting the Port Communication Path ................................. 5-6
Figure 5.8 – Selecting the Interbus Controller Type ................................... 5-7
Figure 5.9 – Entering a Description for the Controller Board ...................... 5-7
Figure 5.10 – Sample Interbus CMD Project .............................................. 5-8
Figure 5.11 – CMD Bus Configuration ........................................................ 5-8
Figure 5.12 – Sample Interbus I/O Mapping ............................................... 5-9
Figure 5.13 – Scanner Mapping / SLC Addressing..................................... 5-9
Figure 5.14 – Entering a Station Name..................................................... 5-11
Figure 5.15 – Selecting Data for the Parameter Channel Screen............. 5-12
Figure 5.16 – Sample SP600 Demo #2 .................................................... 5-13
Figure 5.17 – Selecting Data for Parameterization/Execute Screen......... 5-14
Figure 5.18 – Sample Parameterization Execution................................... 5-14
Figure 5.19 – Scanner I/O Configuration .................................................. 5-16
Figure 5.20 – Scanner_G_Files ................................................................ 5-16
Figure 6.1 – Sample I/O Image with All I/O Enabled .................................. 6-2
Figure 6.2 – Sample I/O Image with Only Logic/Reference and
Datalink B Enabled ................................................................. 6-3
Figure 6.3 – Sample SLC Ladder Logic - Main Program ............................ 6-8
Figure 6.4 – Sample SLC Ladder Logic - Station 1 Program...................... 6-9
Figure 6.5 – Sample SLC Ladder Logic - Station 1 Program (Continued) 6-10
Figure 6.6 – Sample SLC Ladder Logic - Station 2 Program.................... 6-11
Figure 6.7 – Sample SLC Ladder Logic - Station 2 Program (Continued) 6-12
Contents V
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.6 – Writing Preset Speed 6 (106) to an SP600 Drive (DPI Host) 7-12
Figure 7.7 – Writing Comm Flt Action (6) to a RECOMM-IBUS
Interbus Module..................................................................... 7-13
Figure 7.8 – Writing Flt Cfg A1 (12) to an RECOMM-IBUS Interbus
Module .................................................................................. 7-14
Figure 7.9 – LAD5 - PCP Read Subroutine .............................................. 7-16
Figure 7.10 – LAD5 - PCP Read Subroutine (Continued)......................... 7-17
Figure 7.13 – LAD6 - PCP Write Subroutine............................................. 7-20
Figure 7.14 – LAD6 - PCP Write Subroutine (Continued)......................... 7-21
Figure 7.15 – LAD6 - PCP Write Subroutine (Continued)......................... 7-22
Figure 8.1 – Status Indicators (Location on Drive May Vary)...................... 8-1

Figure 8.2 – VIewing and Clearing Events Using an LCD OIM................... 8-5
VI Interbus Communications Module

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 ............................................................. 4-3
Table 4.3 – Module I/O Configuration Example .......................................... 4-4
Table 4.4 – Selections for Drive Response to Communication Fault.......... 4-5
Table 4.5 – Fault Configuration Parameters ............................................... 4-6
Table 4.6 – Module Configuration Status Parameters ............................... 4-8
Table 5.1 – Module Parameter Settings for Ladder Example ................... 5-2
Table 5.2 – Scanner I/O Layout ................................................................ 5-10
Table 5.3 – SLC Addressing for Device 1.0.............................................. 5-10
Table 5.4 – SP600 Parameter Settings for Ladder Examples .................. 5-15
Table 5.5 – G File Data Information.......................................................... 5-17
Table 7.1 – PCP Message Definition .......................................................... 7-3

Table 7.2 – Command Word Bit Descriptions............................................. 7-4
Table 7.3 – Command Message Format .................................................... 7-5
Table 7.4 – Reply Message Format............................................................ 7-5
Table 7.5 – PCP Read Main Program Data................................................ 7-6
Table 7.6 – PCP Read Subroutine Command Message ............................ 7-6
Table 7.7 – PCP Read Subroutine Reply Message.................................... 7-6
Table 7.8 – Command Message Format for PCP Writes.......................... 7-10
Table 7.9 – Reply Message Format for PCP Writes ................................. 7-10
Table 7.10 – PCP Write Main Program Data ............................................ 7-11
Table 7.11 – PCP Write Subroutine Command Message......................... 7-11
Table 7.12 – PCP Write Subroutine Reply Message ................................ 7-12
Table 8.1 – Cable Check (CC) Status Indicator: State Definitions.............. 8-2
Table 8.2 – Remote Bus Disable (RD) Status Indicator: State Definitions . 8-2
Table 8.3 – Transmit/Receive (TR) Status Indicator: State Definitions....... 8-2
Table 8.4 – Bus Active (BA) Status Indicator: State Definitions.................. 8-3
Table 8.5 – Bus Voltage (UL) Status Indicator: State Definitions ............... 8-3
Table 8.6 – Module Diagnostic Items.......................................................... 8-3
Table 8.7 – Event Codes and Descriptions................................................. 8-6
Contents VII
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.
This manual is intended for qualified electrical personnel familiar

with installing, programming, and maintaining AC drives and
networks.
1.1 Interbus Module Features

The Interbus module features the following:
• A number of configuration tools that can be used to configure the
module and connected drive. The tools include the LCD Operator
Interface Module (OIM) on the drive and drive-configuration
software such as VS Utilities (version 1.01 or later).
• Status indicators that report the status of the drive
communications, module, and network. They are visible both
when the cover is opened and when it is closed.
• I/O, including Logic Command/Reference and up to four pairs of
Datalinks, that may be configured for your application using a
parameter.
• Explicit messages (PCP Read/Write.)
• User-defined fault actions that determine how the module and the
drive respond to communication disruptions on the network.
Introduction 1-1
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.15 SLC 500 and MicroLogix 1000 Instruction Set
Documentation about the scanner, SST-IBS-SLC User’s Guide,

Version 1.20, can be obtained online at
http://www.mysst.com/download.
1.3 Conventions Used in This Manual

The following convention is used throughout this manual:
• Parameters are referenced as follows:
Parameter Name (Parameter Number)
For example: DPI Port (1)
1.4 Getting Assistance from Reliance

Electric
If you have any questions or problems with the products described
in this instruction manual, contact your local Reliance Electric sales
office.
For technical assistance, call 1-800-726-8112.
1-2 Interbus Communications Module

CHAPTER 2
Getting Started
This chapter provides:
• 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
2.1 Interbus Module Components

Status Indicators Five LEDs that indicate the status of the

connected drive, module, and network.
Refer to chapter 8, Troubleshooting the
Interbus Module and Network, for more
information.
DPI Connector A 20-pin, single-row shrouded male
header. An Internal Interface cable is
connected to this connector and a
connector on the drive.
Bus In Interbus One 6-pin plug-in connector.
Connector
Bus Out Interbus One 7-pin plug-in connector.
Connector
Figure 2.1 – Components of the Interbus Module
Getting Started 2-1

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 lists user-supplied equipment also required to install and

configure the Interbus module.
Table 2.2 – Required User-Supplied Equipment
Item Description
A small flathead screwdriver
A grounding wrist strap
Interbus cable
Configuration tool, such as:
• LCD OIM
• VS Utilities (version 1.01 or later)
• with RECOMM-232 Serial Converter
Interbus configuration software (CMD)

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 Throughout
module. this manual
U 2 Verify that the drive is properly installed. SP600 AC
Drive User
Manual
U 3 Install the module. Chapter 3,
Verify that the drive is not powered. Then, Installing the
connect the module to the network using a Interbus
Interbus cable and to the drive using the Module
Internal Interface cable. Use the captive
screws to secure and ground the module to
the drive.
U 4 Apply power to the module. Chapter 3,
The module receives power from the drive. Installing the
Apply power to the drive. Refer to chapter 8, Interbus
Troubleshooting the Interbus Module and the Module
Network, if there is a problem.
U 5 Configure the module for your Chapter 4,
application. Configuring
Set the parameters for the following features the Interbus
as required by your application: Module
• I/O configuration.
• Fault actions.
U 6 Apply power to the Interbus master and
other devices on the network.
Verify that the master and network are
installed and functioning in accordance with
Interbus standards, and then apply power to
them.
U 7 Configure the scanner to communicate Chapter 5,
with the module. Configuring
Use a network tool for Interbus to configure the Interbus
the master on the network. Scanner
U 8 Create a ladder logic program. Chapter 6,
Use a programming tool to create a ladder Using I/O
logic program that enables you to do the Messaging.
following: Chapter 7,
Using Explicit
• Control the module and connected drive. Messaging
• Monitor or configure the drive using Explicit (Parameter
Messages. Protocol)
Getting Started 2-3

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.
ATTENTION:The Interbus 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. Failure to observe these
precautions could result in damage to equipment.
3.2 Connecting the Module to the

Network
ATTENTION:The drive may contain high voltages
that can cause injury or death. Remove all power
! from the drive, and then verify power has been
removed before installing or removing an Interbus
module. Failure to observe these precautions could
result in severe bodily injury or loss of life.
Step 1. Remove power from the drive.

Step 2. Use static control precautions.
Step 3. Route the Interbus cables through the bottom of the
SP600 drive. (See figure 3.1.)
Step 4. Connect the Interbus connectors to the cables. (See
figure 3.1 and tables 3.1 and 3.2.)
Installing the Interbus Module 3-1

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.2 – Bus Out Connector (To Next Node on the Network)
Terminal Name Description

1 /DO2 Receive
2 DO2 Receive
3 /DI2 Transmit
4 DI2 Transmit
5 GND1 Ground Connection
6 RBST1 Termination
7 PE Protective Earth
1
Connect GND to RBST if the module is NOT the last module on the bus. If
the connection is not made, the module will terminate the outgoing bus.

See figure 3.1 for an explanation of wiring an Interbus network.
SST SLC Scanner

DO DI COM /DO /DI
1 2 3 4 5 6 7 8 9 9-pin D-shell Shield

jumper
Station 1
Bus Out (See Table 3.2)
/DO2 DO2 /DI2 DI2 GND RBST PE
1 2 3 4 5 6 1 2 3 4 5 6 7
/DO1 DO1 /DI1 DI1 GND PE

Bus In jumper
(See Table 3.1)
Bus Out (See Table 3.2)

/DO2 DO2 /DI2 DI2 GND RBST PE
Station 2 1 2 3 4 5 6 1 2 3 4 5 6 7
/DO1 DO1 /DI1 DI1 GND PE

Bus In
(See Table 3.1)
Figure 3.1 – Sample Network Wiring
Step 5. Connect the Interbus connector to the module.

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.2 – DPI Ports and Internal Interface Cables

Step 4. For 1-20 HP SP600 drives: Fold the Internal Interface
cable behind the module and mount the module on the
drive using the four captive screws 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.
Important: All screws must be tightened to ground the module.
Drive
Module
Adapter
Internal Interface cable

folded behind the module
and in front of the drive
SP600 Drive
Figure 3.1 – Mounting and Grounding the Interbus Module
3.4 Applying Power

ATTENTION:Unpredictable operation may occur
if parameter settings and switch settings are not
! compatible with your application. Verify that
settings are compatible with your application
before applying power to the drive. Failure to
observe these precautions could result in severe
bodily injury or loss of life.
Step 1. Close the door or reinstall the cover on the drive. Key
status indicators can be viewed on the front of the drive
after power has been applied.
Important: Interbus compliance requires different LED
functions than what is normally displayed on the
front of the drive (DRIVE, MS, Net A, and Net B
LEDs). LED labels are provided with the module for
application to the drive cover.

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.1 lists the tools that can be
used to access the module parameters.
Table 4.1 – Configuration Tools
Tool Refer to:

VS Utilities Software (version VS Utilities online help
1.01 or later)
LCD OIM Section 4.2
Configuring the Interbus Module 4-1

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.
>> Stopped Auto >> Stopped Auto >> Stopped Auto

P0: SP600 P0: SP600 P5: RECOMM-IBUS
Main Menu Device: Port 0 Main Menu
SP600
RECOMM-IBUS
Device Select Parameters

Monitor Lang
Use to highlight Use to select Edit the Interbus

Device Select icon RECOMM-IBUS. parameters using the
same techniques as for
drive parameters.
Figure 4.1 – Accessing the Interbus Parameters using the LCD OIM
4.3 Setting the I/O Configuration

The I/O configuration determines the data that is sent to and from
the drive. This is a two part process: enabling/disabling the data
transmitted between the module and drive, and identifying the data
transmitted between the module and the scanner.
Step 1. Enable or disable the data transmitted between the
module and drive by setting the bits in DPI I/O Config (8).
A “1” enables the I/O. A “0” disables the I/O.
Port 5 Device Bit Description

RECOMM-IBUS 0 Logic Command/Reference (Default)
Parameter #: 8 1 Datalink A
DPI I/O Config 2 Datalink B
xxxxxxxxxxx0000 1 3 Datalink C
Cmd/Ref b00 4 Datalink D
LCD OIM Screen
5 - 16 Not Used
Figure 4.2 – I/O Configuration Screen on an LCD OIM
Bit 0 is the right-most bit. In figure 4.2, it is highlighted and equals

“1.”

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. If you enabled one or more Datalinks, configure
parameters in the drive to determine the source and
destination of data in the Datalink(s). Also, ensure that the
Interbus module is the only module using the enabled
Datalink(s).
Step 4. Interbus requires the network I/O mapping to be
configured first in the module. CMD software will read this
configuration online when it is configuring the scanner.
Process Input Data Description (PIDD) words map input
data on the network (data seen as inputs to the scanner
and controller program). Example input data includes
Logic Status, Feedback and Datalinks (Datalink x1 Out).
Up to 9 words of input data can be mapped.
Process Output Data Description (PODD) words map
output data on the network (data sent as outputs from the
scanner and controller program). Example output data
includes Logic Command, Reference and Datalinks
(Datalink x1 In). Up to 9 words of output data can be
mapped.
Table 4.2 lists the indexes used to select the I/O data.
Table 4.2 – PIDD / PODD Indexes
Input Output
Value Value Value Value
(Hex) (Dec) Selects (Hex) (Dec) Selects
2F9A 12186 Logic Status 2F98 12184 Logic
Command
2F9B 12187 Feedback 2F99 12185 Reference
2FA4 12196 Datalink A1 Out 2F9C 12188 Datalink A1 In
2FA5 12197 Datalink A2 Out 2F9D 12189 Datalink A2 In
2FA6 12198 Datalink B1 Out 2F9E 12190 Datalink B1 In
2FA7 12199 Datalink B2 Out 2F9F 12191 Datalink B2 In
2FA8 12200 Datalink C1 Out 2FA0 12192 Datalink C1 In
2FAA 12202 Datalink D1 Out 2FA2 12194 Datalink D1 In
2FAB 12203 Datalink D2 Out 2FA3 12195 Datalink D2 In

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.3 – Module I/O Configuration Example

Parameter # Name Value Value Description
(Hex) (Dec)
20 PIDD W0 Cfg 2F9A 12186 Logic Status (default)
22 PIDD W1 Cfg 2F9B 12187 Feedback (default)
24 PIDD W2 Cfg 2FA4 12196 Datalink A1 Out
26 PIDD W3 Cfg 2FA5 12197 Datalink A2 Out
Input 28 PIDD W4 Cfg 2FA6 12198 Datalink B1 Out
30 PIDD W5 Cfg 2FA7 12199 Datalink B2 Out
32 PIDD W6 Cfg 2FA8 12200 Datalink C1 Out
34 PIDD W7 Cfg 2FA9 12201 Datalink C2 Out
36 PIDD W8 Cfg 2FAA 12202 Datalink D1 Out
38 PODD W0 Cfg 2F98 12184 Logic Command (default)
40 PODD W1 Cfg 2F99 12185 Reference (default)
42 PODD W2 Cfg 2F9C 12188 Datalink A1 In
44 PODD W3 Cfg 2F9D 12189 Datalink A2 In
Output 46 PODD W4 Cfg 2F9E 12190 Datalink B1 In
48 PODD W5 Cfg 2F9F 12191 Datalink B2 In
50 PODD W6 Cfg 2FA0 12192 Datalink C1 In
52 PODD W7 Cfg 2FA1 12193 Datalink C2 In
54 PODD W8 Cfg 2FA2 12194 Datalink D1 In
Note that Datalink D2 is not used in this example because

maximum configuration has been reached. The maximum
configuration is shown to illustrate utilizing all 9 words of
inputs and 9 words of outputs. Depending on your
application needs, any subset of the above example can
be implemented.
The corresponding DPI I/O Config (8) setting would be
“11111” for all of the above information to transfer
between the module and the drive.
Step 5. Reset the module. Refer to the section 4.4.3, Resetting
the Module, in this chapter.
The module is ready to receive I/O from the master (i.e., scanner).
You must now configure the scanner to recognize and transmit I/O
to the module. Refer to chapter 5, Configuring the Interbus Scanner.

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. You can set this
parameter so that the drive continues to run.
Precautions should be taken to ensure that the
setting of this parameter does not create a hazard
of injury or equipment damage. Failure to observe
this precaution could result in bodily injury or
damage to equipment.
4.4.1 Changing the Fault Action

Set the value of Comm Flt Action (6) to the desired response as
shown in table 4.4. See figure 4.3 for a sample LCD OIM Fault
Action screen.
Table 4.4 – Selections for Drive Response to Communication Fault
Value Action Description

0 Fault (default) The drive is faulted and stopped.
(Default)
1 Stop The drive is stopped, but not faulted.
2 Zero Data The drive is sent 0 for output data after
a communications disruption. This does
not command a stop.
3 Hold Last The drive continues in its present state
after a communications disruption.
4 Send Flt Cfg The drive is sent the data that you set in
the fault configuration parameters, Flt
Cfg Logic (10) through Flt Cfg D2 (19).
Port 5 Device
RECOMM-IBUS
Parameter #6:
Comm Flt Action
0
Fault
Figure 4.3 – Fault Action Screen on an LCD OIM

Changes to this parameter take effect immediately. A reset is not
required.

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.
11 Flt Cfg Ref A 32-bit value (0 – 4294967295) sent to
12 – 19 Flt Cfg x1 In the drive as a Reference or Datalink.
Important: If the drive uses a 16-bit
Reference or 16-bit Datalinks, the most
significant word of the value must be set
to zero (0) or a fault will occur.
Changes to these parameters take effect immediately. A reset is not

required.

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. Failure to
observe this precaution could result in bodily injury
or damage to the equipment.
Set Reset Module (5) to Reset Module. See figure 4.4.
Port 5 Device Value Description

RECOMM-IBUS 0 Ready (Default)
Parameter #: 5 1 Reset Module
Reset Module 2 Set Defaults
1
Reset Module
Figure 4.4 – Reset Module Screen on an LCD OIM
When you enter 1 (Reset Module), the module will be immediately

reset. When you enter 2 (Set Defaults), the module will set all
module parameters to their factory-default settings. The value of this
parameter will be restored to 0 (Ready) after the module is reset.

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 Details

01 DPI Port Default: 0
Port to which the module is connected. This will Minimum: 0
usually be port 5. Maximum: 7
Type: Read Only
03 Ref/Fdbk Size Default: 0 = 16-bit
Size of the Reference/Feedback. The drive Values: 0 = 16-bit
determines the size of the Reference/Feedback. 1 = 32-bit
Type: Read/Write
04 Datalink Size Default: 0 = 16-bit
Size of each Datalink word. The drive determines Values: 0 = 16-bit
the size of Datalinks. 1 = 32-bit
Type: Read Only
09 DPI I/O Active Default: xxx0 0001
I/O that the module is actively transmitting. The Bit Values: 0 = I/O disabled
value of this parameter will usually be equal to the 1 = I/O enabled
value of parameter 8 - DPI I/O Config. Type: Read Only
Bit 7 6 5 4 3 2 1 0 Bit Definitions
Default x x x 0 0 0 0 1 0 = Cmd/Ref
1 = Datalink A
2 = Datalink B
3 = Datalink C
4 = Datalink D
5 = Not Used
6 = Not Used
7 = Not Used
21 PIDD W0 Actual Value: See table 4.2
Actual Process Input Description for Word 0 Type: Read Only
Displays the Actual PIDD Config being transmitted
to word 0 in the Interbus Master.

Table 4.6 – Module Configuration Status Parameters (Continued)
No. Name and Description Details

39 PODD W0 Actual Value: See table 4.2
Actual Process Output Description for Word 0 Type: Read Only
Displays the actual PODD Configuration being
received from word 0 in the Interbus Master.
57 PCP Comm Act Value: Enabled, Disabled
Actual PCP configuration

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.1 Configuring a Simple Network:

An Example
All examples in this manual are based on the following:
• SLC controller with an SST Interbus scanner (SST-IBS-SLC)
in slot 1.
• SP600 drive at Device 1.0 / CR 2 (CR# is needed for PCP
commands).
• SP600 drive at Device 2.0 / CR 3 (CR# is needed for PCP
commands).
• Logic Command/Status, Reference/Feedback and Datalinks A-D
are enabled in the RECOMM-IBUS and mapped to network
I/O.
• Phoenix Contact CMD software is used to configure the network.
This chapter describes the steps to configure a simple network like

the one featured in figure 5.1.
Configuring the Interbus Scanner 5-1

Fault LED
COMM LED
Interbus
REMOTE OUT
Config
RS232 Port
Interbus Scanner in
Multi-Module Controller
SP600 Drive SP600 Drive

Station 1.0 Station 2.0
(CR=2) (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.1 – Module Parameter Settings for Ladder Example
Value
Binary/
Parameter Name Decimal Hexadecimal Description
8 DPI I/O Config xxx1 1111 001F Enable Cmd/Ref,
Datalinks A-D
20 PIDD W0 Cfg 12186 2F9A Logic Status
22 PIDD W1 Cfg 12187 2F9B Feedback
24 PIDD W2 Cfg 12196 2FA4 Datalink A1 Out
26 PIDD W3 Cfg 12197 2FA5 Datalink A2 Out

Table 5.1 – Module Parameter Settings for Ladder Example (Continued)
Value
Binary/
Parameter Name Decimal Hexadecimal Description
28 PIDD W4 Cfg 12198 2FA6 Datalink B1 Out
30 PIDD W5 Cfg 12199 2FA7 Datalink B2 Out
32 PIDD W6 Cfg 12200 2FA8 Datalink C1 Out
34 PIDD W7 Cfg 12201 2FA9 Datalink C2 Out
36 PIDD W8 Cfg 12202 2FAA Datalink D1 Out
38 PODD W0 Cfg 12184 2F98 Logic Command
40 PODD W1 Cfg 12185 2F99 Reference
42 PODD W2 Cfg 12188 2F9C Datalink A1 In
44 PODD W3 Cfg 12189 2F9D Datalink A2 In
46 PODD W4 Cfg 12190 2F9E Datalink B1 In
48 PODD W5 Cfg 12191 2F9F Datalink B2 In
50 PODD W6 Cfg 12192 2FA0 Datalink C1 In
52 PODD W7 Cfg 12193 2FA1 Datalink C2 In
54 PODD W8 Cfg 12194 2FA2 Datalink D1 In
PIDD and PODD parameters are used to identify what will be

transmitted on the network and the amount of network I/O the CMD
software will allocate on the scanner.
5.3 Configuring the Network Using CMD

Software
Before starting the network configuration process, make sure the
PC running CMD software is connected to the SST scanner (a null
modem cable is supplied with the scanner). The SLC and drives
need to be connected to the Interbus network and powered in order
for CMD software to configure the network. The CMD software tool
automatically creates a Reliance Electric sub-folder (in the Slaves
folder), if it does not already exist.
CMD needs to be in Extended Mode to configure the network. A

password (supplied by Phoenix Contact along with the CMD
software), is requested for this functionality each time CMD is
started. After CMD has started, you can also click Options/
Extended (Function Scope) to enter the password.
Step 1. Select File / New from the pull-down menu to create a
new project. (See figure 5.2.)

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. Right-click on the PLC/PC icon and select

Description. Enter a name for the controller and any

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
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.6 – Sample Interbus CMD Project

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. Click on the Communication Path icon and then the
Standard tab.
Step 8. Select the port communication path. Typically, this is
“Serial Port” and “Com1” respectively, as shown in figure
5.7. Click OK until you return to the main screen.
Figure 5.7 – Selecting the Port Communication Path
Step 9. Right-click on the Controller Board icon and select

Type. Set the type to “IBS USC/4(4K)” and click OK. This
identifies the type of Interbus controller used on the SST
scanner. (See figure 5.8.)

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
Figure 5.9 – Entering a Description for the Controller Board


.
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. The first SP600
drive has a Device Number of 1.0 and the second has a Device
Number of 2.0.

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 scanner mapping correlates to SLC addressing as shown in
figure 5.13.
Scanner Scanner
(USC/4) Output SLC (USC/4) Input SLC
0 O:x.0(high) 512 I:x.0(high)

1 O:x.0(low) 513 I:x.0(low)
63 O:x.31(low) 575 I:x.31(low)

64 M0:x.0(high) 576 M1:x.0(high)
65 M0:x.0(low) M1:x.0(low)
511 M0:x.223(low) 1023

M1:x.223(low)
Figure 5.13 – Scanner Mapping / SLC Addressing

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.2 – Scanner I/O Layout

Station Outputs Station
Inputs (Data from
Word (Data to Master) 1.0 2.0 Master) 1.0 2.0
0 Logic Status 512 530 Logic Command 0 18
1 Feedback 514 532 Reference 2 20
2 Datalink A1 Out 516 534 Datalink A1 In 4 22
3 Datalink A2 Out 518 536 Datalink A2 In 6 24
4 Datalink B1 Out 520 538 Datalink B1 In 8 26
5 Datalink B2 Out 522 540 Datalink B2 In 10 28
6 Datalink C1 Out 524 542 Datalink C1 In 12 30
7 Datalink C2 Out 526 544 Datalink C2 In 14 32
8 Datalink D1 Out 528 546 Datalink D1 In 16 34
Device 1.0’s SLC addressing is as follows:
Table 5.3 – SLC Addressing for Device 1.0

Inputs Assignment Outputs Assignment
(Data to (Data from
Word Master) Scanner SLC Master) Scanner SLC
0 Logic Status 512 I:1.0 Logic 0 O:1.0
Command
1 Feedback 514 I:1.1 Reference 2 O:1.1
2 Datalink A1 Out 516 I:1.2 Datalink A1 In 4 O:1.2
3 Datalink A2 Out 518 I:1.3 Datalink A2 In 6 O:1.3
4 Datalink B1 Out 520 I:1.4 Datalink B1 In 8 O:1.4
5 Datalink B2 Out 522 I:1.5 Datalink B2 In 10 O:1.5
6 Datalink C1 Out 524 I:1.6 Datalink C1 In 12 O:1.6
7 Datalink C2 Out 526 I:1.7 Datalink C2 In 14 O:1.7
8 Datalink D1 Out 528 I:1.8 Datalink D1 In 16 O:1.8
Device 2.0’s SLC addressing starts immediately after 1.0

addressing (I:1.9 and O:1.9).

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.

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.

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.
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.4 – SP600 Parameter Settings for Ladder Examples

Parameter Name Value Description
90 Speed Ref A Sel 22 Network (RECOMM-IBUS)
provides the Reference
300 Data In A1 140 Accel Time 1 (140)
301 Data In A2 142 Decel Time 1 (142
302 Data In B1 100 Jog Speed (100)
303 Data In B2 155 Stop Mode A (155)
304 Data In C1 101 Preset Speed 1 (101)
305 Data In C2 102 Preset Speed 2 (102)
306 Data In D1 103 Preset Speed 3 (103)
310 Data Out A1 140 Accel Time 1 (140)
311 Data Out A2 142 Decel Time (142)
312 Data Out B1 100 Jog Speed (100)
313 Data Out B2 155 Stop Mode A (155)
314 Data Out C1 101 Preset Speed 1 (101)
315 Data Out C2 102 Preset Speed 2 (102)
316 Data Out D1 103 Preset Speed 3 (103)

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.20 – Scanner_G_Files

Table 5.5 – G File Data Information
Value Value
Word (Decimal) (Hexadecimal) Description
0 8224 2020 Fixed to 2020h by the SLC
1 4096 1000 Enables the command interface
between the SLC and the USC/4
2 0 0 Use the CMD specified Bus Update
Time
3 0 0 Use the CMD specified Bus Warning
Time
4 0 0 Use the CMD specified Bus Timeout
5 0 0 The number of words used at the
beginning of the M files for Inputs
and Outputs
6 128 80 Maximum data size for commands
and replies sent between the SLC
and the scanner
Refer to the SST_IBS_SLC User’s Guide for more information.

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.
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. Failure to observe this
precaution could result in bodily injury or damage to
equipment.
6.1 About I/O Messaging

I/O messaging is used to transfer the data which controls the SP600
drive and sets its Reference. I/O can also be used to transfer data to
and from Datalinks in SP600 drives.
The Interbus module provides options for configuring and using I/O,
including the following:
• The size of I/O can be configured by enabling or disabling the
Logic Command/Reference and Datalinks.
Chapter 4, Configuring the Interbus Module, and chapter 5,

Configuring the Interbus Scanner, discuss how to configure the
module and scanner on the network for these options. The Glossary
defines the different options. This chapter discusses how to use I/O
after you have configured the module and scanner.
6.2 Understanding the I/O Image

The terms input and output are defined from scanner’s point of
view. Therefore, Output I/O is data that is output from the scanner
and consumed by the Interbus module. Input I/O is status data that
is produced by the module and consumed as input by the scanner.
Using I/O Messaging 6-1

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.
Interbus DPI
Controller Scanner Module SP600 Drive
Word and I/O
Output 0 Logic Command Logic Command
Image 1 Reference Reference
(Write) 2 Datalink In A1 Data In A1
3 Datalink In A2 Data In A2
4 Datalink In B1 Data In B1
6 Datalink In C1 Data In C1
7 Datalink In C2 Data In C2
8 Datalink In D1 Data In D1
M0/M1 PCP Communications Message

Files Handler
Input 0 Logic Status Logic Status

Image 1 Feedback Feedback
(Read) 2 Datalink Out A1 Data Out A1
3 Datalink Out A2 Data Out A2
4 Datalink Out B1 Data Out B1
6 Datalink Out C1 Data Out C1
7 Datalink Out C2 Data Out C2
8 Datalink Out D1 Data Out D1
M0/M1 Message
PCP
Handler
Files Communications
Figure 6.1 – Sample I/O Image with All I/O Enabled

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.
Interbus DPI
Controller Scanner Module SP600 Drive
Word and I/O

Output 0 Logic Command Logic Command
Image 1 Reference (LSW) Reference
(Write) 2 Reference (MSW) Data In A1
3 Datalink In B1 Data In A2
Data In B2
Data In C1
Data In C2
Data In D1
Input 0 Logic Status Logic Status

Image 1 Feedback (LSW) Feedback
(Read) 2 Feedback (MSW) Data Out A1
3 Datalink Out B1 Data Out A2
Data Out B2
Data Out C1
Data Out C2
Data Out D1
LSW = Least Significant Word (Bits 15 - 0)

MSW = Most Significant Word (Bits 31 - 16)
Figure 6.2 – Sample I/O Image with Only Logic/Reference and Datalink B
Enabled

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.4 Using Reference/Feedback

When enabled, Reference/Feedback always begins at word 1 in the
I/O image. The Reference (16 bits or 32 bits) is produced by the
controller and consumed by the module. The Feedback (16 bits or
32 bits) is produced by the module and consumed by the controller.
The size of the Reference/Feedback is determined by the product
and displayed in Ref/Fdbk Size (3) in the module.
Size Valid Values In I/O Image Example

16-bit -32768 to 32767 Word 1 Figure 6.1
32-bit -2147483648 to Word 1 and Figure 6.2
2147483647 Word 2
6.5 Using Datalinks

A Datalink is a mechanism used by SP600 drives to transfer data to
and from the controller. Datalinks allow a parameter value to be
changed without using an Explicit Message.
When enabled, each Datalink consumes either two 16-bit or 32-bit

words in both the input and output image depending on its size. The
size of Datalinks (16-bit words or 32-bit words) is determined by the
drive and displayed in Datalink Size (4) in the module.
6.5.1 Rules for Using Datalinks

• Each set of Datalink parameters in an SP600 drive can be used
by only one module. If more than one module is connected to a
single drive, multiple modules must not try to use the same
Datalink.
• Parameter settings in the drive determine the data passed
through the Datalink mechanism. Refer to the documentation for
your product.

• 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.” Datalink A1 will contain the least
significant word (LSW) and Datalink A2 the most significant word
(MSW). In this example, the parameter 9 value of 5.8 MWh is read
as a “58” in Datalink A1.
Most/Least Data
Datalink Significant Word Parameter (decimal)
A1 LSW 9 58
A2 MSW 9 0
Regardless of the Datalink combination, x1 will always contain the

LSW and x2 will always contain the MSW. In the following
examples, Power Up Marker (242) contains a value of 88.4541
hours.
Most/Least Data
A1 LSW 242 32573
A2 - Not Used - 0 0
Most/Least Data
A1 - Not Used - 0 0
A2 MSW 242 13
Most/Least Data
A2 MSW 242 13
B1 LSW 242 32573
32-bit data is stored in binary as follows:
MSW 231 through 216

LSW 215 through 20

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.
Function of the Sample Program
The program is written for (2) drives on the network and

demonstrates using:
• Logic Command / Reference
• Logic Status / Feedback
• Datalinks
• PCP Read / Write (See chapter 5.)
Module Settings
The RECOMM-IBUS node addresses are set via CMD software to:
• “1.0” (CR=2) for Station 1
• “2.0” (CR=3) for Station 2
See section 5.2, Configuring the Module for use with the Ladder
Examples.
SP600 Settings
See section 5.4, Configuring the SP600 Drive for use with the
Ladder Examples.
SST Scanner Settings
See section 5.5, Configuring the RSLogix 500 SST Interbus

Scanner.

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 Station 2
Address 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.17 Datalink D1
Write Data
The scanner is configured for 18 bytes (9 words) of outputs for each
drive, the maximum amount allowed. Two drives require 36 bytes
(18 words).
Station 1 Station 2
Address Address Function
O:1.0 O:1.9 Logic Command
O:1.1 O:1.10 Reference
O:1.2 O:1.11 Datalink A1
O:1.3 O:1.12 Datalink A2
O:1.4 O:1.13 Datalink B1
O:1.5 O:1.14 Datalink B2
O:1.6 O:1.15 Datalink C1
O:1.7 O:1.16 Datalink C2
O:1.8 O:1.17 Datalink D1
Logic Command/Status Words
These examples use the Logic Command word and Logic Status
word for SP600 drives. Refer to Appendix C, Logic Command/
Status Words to view these. The definition of the bits in these words
may vary if you are using a different DPI product. Refer to the
documentation for your product.

6.6.1 Sample SLC Ladder Logic - Main Program
The following rung performs power-up initialization of the PCP Read and PCP Write routines.
Execute
PCP Read
First Pass Subroutine
S:1 B3:47
0000 U
15 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
Execute LAD 3 - Station 1.0 Drive Logic (Logic Command / Status, Reference / Feedback and Datalinks).
JSR
0001 Jump To Subroutine
SBR File Number U:3
Execute LAD 4 - Station 2.0 Drive Logic (Logic Command / Status, Reference / Feedback and Datalinks).
JSR
SBR File Number U:4
Execute LAD 5 - PCP Read Subroutine (Explicit Messaging)

Can Read OR Write 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.
Execute Execute
PCP Read PCP Write
Subroutine Subroutine
B3:47 B3:47 JSR
0 10 SBR File Number U:5
Execute LAD 6 - PCP Write Subroutine (Explicit Messaging)

Can only Write OR Read at any one time. B3:47/10 will be turned off by the subroutine when the writing is complete and
signals that another write (or read) cycle can take place.
Execute Execute
PCP Read PCP Write
Subroutine Subroutine
B3:47 B3:47 JSR
0 10 SBR File Number U:6
0005 END
Figure 6.3 – Sample SLC Ladder Logic - Main Program

Controlling the Logic Command to the drive at Station 1.0.
Start Logic Command
Command START
B3:20 O:1.0
0000
1 1
OTHER

Stop Logic Command
Command STOP
B3:20 O:1.0
0001
0 0
OTHER

Jog Logic Command
Command JOG
B3:20 O:1.0
0002
2 2
OTHER

Clear Faults Logic Command
Command CLEAR FAULTS
B3:20 O:1.0
0003
3 3
OTHER

Reverse Logic Command
Command FORWARD
B3:20 O:1.0
0004
4 4
OTHER

Command REVERSE
B3:20 O:1.0
0005
4 5
OTHER
Station 1.0 Speed Reference

PowerFlex
SP600 Speed 70 Ref
Speed Ref
A Sel A Sel
(90) (Pr.90)
needs to be needs to be set to 'DPI Port 5'
set to “Network”
Station 1.0
Speed Reference
MOV
0006 Move
Source N19:1
8192 <
Dest O:1.1
8192 <
Station 1.0 Datalink A1

Datalink A1 (Pr. 300) set to Acceleration Time 1 (Pr. 140)
Station 1.0
Datalink A1
MOV
0007 Move
Source N19:2
50<
Dest O:1.2
50<
Figure 6.4 – Sample SLC Ladder Logic - Station 1 Program

Datalink A2 (Pr. 301) set to Deceleration Time 1 (Pr. 142)
Station 1.0
Datalink A2
MOV
0008 Move
Source N19:3
50<
Dest 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
0009 Move
Source N19:4
100<
Dest O:1.4
100<

Datalink B2 (Pr. 303) set to Stop Mode A (Pr. 155)
Station 1.0
Datalink B2
MOV
0010 Move
Source N19:5
1<
Dest O:1.5
1<
Station 1.0 Datalink C1

Datalink C1 (Pr. 304) set to Preset Speed 1 (Pr. 101)
Station 1.0
Datalink C1
MOV
0011 Move
Source N19:6
100<
Dest O:1.6
100<

Station 1.0
Datalink C2
MOV
0012 Move
Source N19:7
200<
Dest O:1.7
200<
Station 1.0 Datalink D1

Datalink D1 (Pr. 306) set to Preset Speed 3 (Pr. 103)
Station 1.0
Datalink D1
MOV
0013 Move
Source N19:8
300<
Dest O:1.8
300<
0014 END
Figure 6.5 – Sample SLC Ladder Logic - Station 1 Program (Continued)

6.6.2 Sample SLC Ladder Logic - Station 2 Program
Controlling the Logic Command to the drive at Station 2.0.

Start Logic Command
Command START
B3:21 O:1.9
0000
1 1
OTHER

Stop Logic Command
Command STOP
B3:21 O:1.9
0001
0 0
OTHER

Jog Logic Command
Command JOG
B3:21 O:1.9
0002
2 2
OTHER

Clear Faults Logic Command
Command CLEAR FAULTS
B3:21 O:1.9
0003
3 3
OTHER

Command FORWARD
B3:21 O:1.9
0004
4 4
OTHER

Command REVERSE
B3:21 O:1.9
0005
4 5
OTHER
Station 2.0 Speed Reference

SP600 Speed
PowerFlex 70 Ref A Sel
Speed Ref(90) needs
A Sel to be needs
(Pr.90) set to “Network”
to be set to 'DPI Port 5'
Station 2.0
Speed Reference
MOV
0006 Move
Source N19:15
8192 <
Dest O:1.10
8192 <

Datalink A1 (Pr. 300) set to Acceleration Time 1 (Pr. 140)
Station 2.0
Datalink A1
MOV
0007 Move
Source N19:16
50<
Dest O:1.11
50<
Figure 6.6 – Sample SLC Ladder Logic - Station 2 Program

Datalink A2 (Pr. 301) set to Deceleration Time 1 (Pr. 142)
Station 2.0
Datalink A2
MOV
0008 Move
Source N19:17
50<
Dest O:1.12
50<

Datalink B1 (Pr. 302) set to Jog Speed (Pr. 100)
Station 2.0
Datalink B1
MOV
0009 Move
Source N19:18
100<
Dest O:1.13
100<

Datalink B2 (Pr. 303) set to Stop Mode A (Pr. 155)
Station 2.0
Datalink B2
MOV
0010 Move
Source N19:19
1<
Dest O:1.14
1<

Station 2.0
Datalink C1
MOV
0011 Move
Source N19:20
100<
Dest O:1.15
100<

Station 2.0
Datalink C2
MOV
0012 Move
Source N19:21
200<
Dest O:1.16
200<
Station 2.0 Datalink D1

Datalink D1 (Pr. 306) set to Preset Speed 3 (Pr. 103)
Station 2.0
Datalink D1
MOV
0013 Move
Source N19:22
300<
Dest O:1.17
300<
0014 END
Figure 6.7 – Sample SLC Ladder Logic - Station 2 Program (Continued)

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. Rockwell Automation does not assume
responsibility or liability (to include intellectual
property liability) for actual use of the examples
shown in this publication. Failure to observe this
equipment.
ATTENTION:If Explicit Messages are programmed
to write parameter data to Non-Volatile Storage
(NVS) frequently, the NVS will quickly exceed its life
cycle and cause the drive to malfunction. Do not
create a program that frequently uses Explicit
Messages to write parameter data to NVS. Datalinks
do not write to NVS and should be used for frequently
changed parameters. Failure to observe this
precaution could result in damage to, or destruction
of, equipment.
7.1 About Explicit Messaging

Explicit Messaging (PCP Communications) is used to transfer data
that does not require continuous updates. With Explicit Messaging,
you can configure and monitor a slave device’s parameters on the
Interbus network.
To be able to use Explicit Messaging in the module, PCP Comm Act

(57) must be set to “Enabled”.
Using Explicit Messaging (PCP Communications) 7-1

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.

Set up and send
Parameter Message

Complete Parameter
Message

Retrieve Parameter
Message Response

Format the required data and set up the ladder
logic program to send an Explicit Message
request to the scanner module (download).
The scanner module transmits the Explicit
Message Request to the slave device over the
Interbus network.
The slave device transmits the Explicit Message
Response back to the master.
The controller retrieves the Explicit Message
Response.
The Explicit Message is complete.
Figure 7.1 – Explicit Message Process

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.1 – PCP Message Definition
PCP - Index Value Access

Name Range Rights Description
Hex Decimal
Host Parameters 3001 to 12289 Host 3001 (12289
(3001 to Parameter Dec) =
+n) (12289 Dependent Parameter 1 -
+ n) etc.
Host Fault Queue 2FF9 to 12281 Read Only Host fault
3000 to queue
12288 containing up
to 8 faults
RECOMM-IBUS 2FB6 to 12214 Parameter 2FB6 (12214
Parameters 2FEE to Dependent Dec) =
12270 Parameter 1 -
etc.
RECOMM-IBUS 2FAE to 12206 Read Only Module event
Event Queue 2FB5 to queue (8
12213 events)
The Command Interface for the SST SLC Interbus scanner must be
enabled for PCP Communications to take place:
• Bit 12 of word 1 in the G File must be set
• Word 5 in the G File must be set to the length of process data
required in the M Files. This value can range from 0 to 224.
• Word 6 in the G File must be set to the maximum length of the
command buffer. This value can range from 0 to 128 and must be
non-zero to enable the buffer.

O/I O/I:0 Process Data
(I/O Messaging)
M0/M1:0
M0/M1
M0/M1:(G:5-1)
M0/M1:(G:5) Command/Status word
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.)
The first word in the Command Interface memory area is the

Command (M0) or Status (M1) word. The remaining words form a
buffer to pass command data to and from the scanner. The M0 file
contains the buffer for the command written by the SLC and the M1
file contains the reply to the SLC written by the scanner.
The lower six bits in the Command word are command bits to the
scanner. Commands are initiated by setting bits in this Command
word. The scanner acknowledges the command by setting bits in
the Status word. The high bit is either the Message Acknowledge bit
(command word) or the Message Present bit (Status word).
Table 7.2 – Command Word Bit Descriptions
Bit Description
0 PCP Start
1 PCP Stop
2 PCP Read
3 PCP Write
4 PCP Command
5 IBS Command
15 Message acknowledge (Command) / Message present
(Status)
The ladder example used in this manual performs PCP Reads and
PCP Writes.

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.4 – Reply Message Format

0 Command Echo of the Command Word (0004h)
Word Echo
1 Message Number of words following
Length
2 CR The Communication Reference (CR #)
the Reply is from
3 Result Result Code:
0=Success
FFFFh = Timeout
FFFEh = Out of buffers to store the
reply
FFFDh = Invalid CR
FFFCh = Could not connect to device
with CR
FFFBh = Reply of Command bigger
than buffer
4 Data Length The # of bytes of data following (1, 2 or
4 bytes)
5 Data Word 1 Contains 8-bit (1 byte) data reads
(stored in the high byte), 16-bit (2 byte)
data reads, and the most significant
word for 32-bit (4 byte) data reads
6 Data Word 2 Least significant word for 32-bit (4 byte)
data reads

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:
N22:0 Set to “2” to access Station 1.0 (CR=2)
Set to “3” to access Station 2.0 (CR=3)
The desired Parameter / Event / Fault area to be
accessed:
N22:1 Set to “0” to read SP600 parameters
Set to “1” to read RECOMM-IBUS parameters
Set to “2” to read SP600 Fault Queue
Set to “3” to read RECOMM-IBUS Event Queue
The actual Parameter number or Event / Fault
N22:2 Queue item number to read. Set to “1” to read
Parameter number 1 or Fault / Event Queue item
number 1....etc....
The PCP Read Subroutine uses the data in table 7.5 to create the
following Command Message (table 7.6):
Table 7.6 – PCP Read Subroutine Command Message
N22:10 The PCP Command word (set to “4” for PCP Read).
N22:11 The Communication Reference (CR) to read from.
N22:12 The PCP Index of the variable to read (“3001h”=
Host parameter 1, etc.).
N22:13 Sub Index not used (set to “0”).
Table 7.7 – PCP Read Subroutine Reply Message
N22:20 = PCP Status Word.
N22:21 = Echo of the Command word (0004h).
N22:22 = Number of words following.
N22:23 = CR.
N22:24 = Result (“0”=good).
N22:25 = Number of bytes read (1-byte for 8-bit parameters,
2-bytes for 16-bit parameters, 4-bytes for 32-bit
parameters).
N22:26 = Data Word #1 (1-byte & 2-byte reads, MSW of
4-byte read).
N22:27 = Data Word #2 (LSW of 4-byte read).

7.3.2 Read Examples
tion
ress
x)
c)
e
(He
sag
(De
crip
Add
e
Mes
Des
Valu
SLC
Valu
Command N22:10 4 4 Command word = 4 = PCP Read (bit 2 ON)
N22:11 2 2 CR# = 2 (Station 1.0)
IIndex
ndex=3000h+8Ch
= 3000h + =8Ch = Accel
Parameter 140Time
[Accel(140)
Time]
N22:12 12428 308C 3001h
3001h isisthethe start
start of SP600
of PowerFlex 70parameters (1)
parameters (Pr.1)
8C hex==140
8C hex 140
decdec = Accel 140
= Parameter Time (140)
[Accel Time]
N22:13 0 0 Sub Index not used

Status word:
Reply N22:20 -32,764 8004 "8000" (bit 15 ON) indicates Reply message present
"0004" (bit 2 ON) echo's the command (PCP Read)
N22:21 4 4 Echo of the Command Word (PCP Read)
N22:22 4 4 Number of words following = 4
N22:23 2 2 CR# = 2 (Station 1.0)

N22:24 0 0 Result = 0 (success)
N22:25 2 2 Number of bytes read = 2
N22:26 50 32 Data word 1 = 32 hex = 50 dec = 5.0 seconds
N22:27 0 0 Data word 2 not used
Figure 7.3 – Reading Accel Time 1 (140) from an SP600 Drive (DPI Host)
In the sample ladder logic program, the user would load these
registers before calling the subroutine to perform the PCP Read:
on
ress
x)
)
age
(He
ti
(De
crip
Add
s
e
Mes
Des
Valu
SLC
Valu
Request N22:0 2 2 CR# =2 (Station 1.0)

N22:1 0 0 0 =PowerFlex
0= SP600 (DPI Host)Host)
70 (DPI
N22:3 140 8C Parameter # = 140 [Accel Time]

tion
ress
x)
c)
e
(He
sag
(De
crip
Add
e
Mes
Des
Valu
SLC
Valu
N22:11 2 2 CR# = 2 (Station 1.0)
Index = 3000h + F4h = Fault 1 Time (244)
Index =3000h+F4h = Parameter 244 [Fault 1 Time]
N22:12 12532 30F4 3001h is the start of SP600 parameters (1)
3001h is the start of PowerFlex 70 parameters (Pr.1)
F4 hex ==244
F4 hex 244dec
dec= Parameter
= Fault 1 Time (244)
244 [Fault 1Time]

Status word:
N22:23 2 2 CR# =2(Station 1.0)
N22:26 59 3B 3B235B hex = 3875675 decimal = 387.5675 hours
N22:27 9051 235B
Figure 7.4 – Reading Fault 1 Time (244) from an SP600 Drive (DPI Host)
In the example ladder logic program, the user would load these
registers before calling the subroutine to perform the PCP Read:
tion
ss
x)
)
e
(He
ddre
sag
(De
crip
A
e
Mes
Des
Valu
SLC
Valu

N22:1 0 0 000===PowerFlex
0= SP600
SP600 (DPI
SP600(DPI Host)
70Host)
(DPI (DPI
Host)Host)
N22:3 244 F4 Parameter##==244
Parameter 244[Fault
(Fault 1 Time)
1 Time]

tion
ss
x)
)
e
(He
re
sag
(De
crip
Add
e
Mes
Des
Valu
SLC
Valu
N22:11 2 2 CR# = 2 (Station 1.0)
Index =2FB5h+15h
Index = 2FB5h + 15h = PIDD W021Actual
= Parameter [PIDD(21)
W0 Actual]
N22:12 12234 2FCA 2FB6h
2FB6h isisthe
thestart
startofofthe 20-COMM-I parameters
RECOMM-IBUS parameters(Pr.1)
1515hex
hex==2121dec
dec==Parameter 21 [PIDD
PIDD W0 Actual (21)W0 Actual]

Status word:
N22:23 2 2 CR# = 2 (Station 1.0)

N22:26 12186 2F9A Data word 1 = 2F9A hex = Logic Status
Figure 7.5 – Reading PIDD W0 Actual (21) from an RECOMM-IBUS

Interbus Module
registers before calling the subroutine to perform the PCP read:
tion
ress
)
c)
Hex
age
(De
crip
Add
e(
s
Mes
Des
Valu
SLC
Valu
Request N22:0 2 2 CR# = 2 (Station 1.0)

N22:1 1 1 1=
1 =20-COMM-I
RECOMM-IBUS
N22:3 21 15 Parameter # = 21 [PIDD W0 Actual]

7.3.3 PCP Write Message Format
PCP Writes require the following Command and Reply message
formats:
Command
Table 7.8 – Command Message Format for PCP Writes

0 CR The Communication Reference (CR #) to
write to
1 Index The index of the variable to write
2 Sub Index The sub-index of the variable to write (not
used)
3 Data The # of bytes of data following (1, 2, or 4
Length bytes)
4 Data Contains 8-bit (1 byte) write data (stored in
Word 1 the high byte), 16-bit, (2 byte) write data,
and the most significant word for 32-bit (4
byte) write data
5 Data Least significant word for 32-bit (4 byte)
Word 2 write data
Reply
Table 7.9 – Reply Message Format for PCP Writes

0 Command Echo of the Command Word (0008h)
Word Echo
1 Message Number of words following
Length
2 CR The Communication Reference (CR #) the
Reply is from
3 Result Result Code:
0=Success
FFFFh = Timeout
FFFEh = Out of buffers to store the reply
FFFDh = Invalid CR
FFFCh = Could not connect to device with
CR
FFFBh = Reply of Command bigger than
buffer

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
The Communication Reference (CR) to write to:
N23:0 Set to “2” to access Station 1.0 (CR=2)
Set to “3” to access Station 2.0 (CR=3)
N23:1 The desired parameter area to be accessed:
Set to “0” for DPI Host parameters
Set to “1” for RECOMM-IBUS parameters
N23:2 The actual parameter number to write to (1, 2, ....n).
N23:3 The number of bytes of data to write:
Set to either “1” (1 byte), “2” (2 bytes) and “4” (4
bytes)
N23:4 Data Word #1
(1 and 2-byte writes, MSW of 4 byte write).
N23:5 Data Word #2
(LSW of 4-byte write).
The PCP Write Subroutine uses the data in table 7.10 to create the
following Command Message:
Table 7.11 – PCP Write Subroutine Command Message
N23:10 The PCP Command word (set to “8” for PCP Write).
N23:11 The Command Reference (CR) to write to.
N23:12 The PCP Index of the variable to write (“306Ah” =
Host parameter 106, etc.).
N23:13 Sub Index not used.
N23:14 The number of bytes of data to write (set to “1”, “2”
or “4”).
N23:15 Data word 1.
N23:16 Data word 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
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).
Write Examples:
on
ss
x)
)
e
(He
ddre
ripti
sag
(De
A
c
e
Mes
Des
Valu
SLC
Valu
Command N23:10 8 8 Command word = 8 = PCP Write (bit 3 ON)

N23:11 2 2 CR# = 2 (Station 1.0)
Index= =3000h+6Ah
Index 3000h + 6Ah = Preset
= Parameter 106Speed
[Preset6Speed
(106)6]
N23:12 12394 306A 3001hisisthe
3001h the start
start of SP60070
of PowerFlex parameters
parameters (1)
(Pr.1)
6A hex = 106 dec = Preset Speed 6 (106)
6A hex = 106 dec = Parameter 106 [Preset Speed 6]
N23:14 2 2 2 bytes of data following
N23:15 123 7B Data word 1 = 123 = 12.3 Hz
Reply N23:20 -32,760 8008 Status word:
"8000" (bit 15 ON) indicates Reply message present
"0008" (bit 3 ON) echo's the command (PCP Write)
N23:21 8 8 Echo of the Command Word (PCP Write)

N23:23 2 2 CR# = 2 (Station 1.0)
Figure 7.6 – Writing Preset Speed 6 (106) to an SP600 Drive (DPI Host)

registers before calling the subroutine to perform the PCP Write.
tion
ress
x)
)
e
(He
sag
(De
crip
Add
e
Mes
Des
Valu
SLC
Valu
N23:1 0 0 00== PowerFlex 70 (DPI
SP600 drive (DPI Host)
Host)
N23:2 106 6A Parameter # = 106
N23:3 2 2 2 byte data write
N23:4 123 7B Data Word 1 = 123 = 12.3 Hz
N23:5 0 0 Data Word 2 not used
on
ress
x)
c)
e
(He
ripti
sag
(De
Add
c
e
Mes
Des
Valu
SLC
Valu

N23:11 2 2 CR# = 2 (Station 1.0)
Index
Index == 2FB5h+6h
2FB5h+6h==Comm Flt Action
Parameter (6) Flt Action
6 [Comm
N23:12 12219 2FBB 2FB6h is the start of RECOMM-IBUS parameters
62FB6h
hex =is6 the
decstart of the
= Comm Flt20-COMM-I
Action (6) parameters (Pr.1)
6 hex = 6 dec = Parameter 6 [Comm Flt Action]
N23:14 1 1 1 byte of data following
N23:15 512 200 Data Word 1 (upper byte) = 2 (Zero Data)

N23:23 2 2 CR# = 2 (Station 1.0)
Figure 7.7 – Writing Comm Flt Action (6) to a RECOMM-IBUS Interbus

Module

registers before calling the subroutine to perform the PCP Write:
tion
ress
x)
c)
e
(He
sag
(De
crip
Add
e
Mes
Des
Valu
SLC
Valu
N23:1 1 1 1 ==20-COMM-I
1= RECOMM-IBUS
RECOMM-IBUS
N23:2 6 6 Parameter # = 6
N23:4 2 2 Data Word 1 = 2 (Zero Data)
N23:5 0 0 Data Word 2 not used
on
ss
x)
)
e
(He
re
ripti
sag
(De
Add
c
e
Mes
Des
Valu
SLC
Valu

N23:11 2 2 CR# = 2 (Station 1.0)
Index
Index == 2FB5h+Ch
2FB5h + Ch= =Parameter
Flt Cfg A112In[Flt
(12)Cfg A1 In]
N23:12 12225 2FC1 2FB6h
2FB6h is the start
start of
of the
RECOMM-IBUS parameters
20-COMM-I parameters (Pr.1)
CC hex
hex == 12
12 dec
dec == Flt Cfg A1 In12(12)
Parameter [Flt Cfg A1 In]
N23:14 4 4 4 bytes of data following
N23:15 0 0
00000800 hex = 2048 decimal
N23:16 2048 800

N23:23 2 2 CR# = 2 (Station 1.0)
Figure 7.8 – Writing Flt Cfg A1 (12) to an RECOMM-IBUS Interbus Module

registers before calling the subroutine to perform the PCP Write:
tion
ress
x)
c)
e
(He
sag
(De
crip
Add
e
Mes
Des
Valu
SLC
Valu
N23:1 1 1 1=
1 = 20-COMM-I
RECOMM-IBUS
N23:2 12 12 Parameter # = 12
N23:4 0 0 Data Word 1 = 0
N23:5 2048 800 Data Word 2 = 2048

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:10 = PCP Command Word (Always set to "4" to cause a PCP Read: a "4" = bit 2 ON)
PCP Read PCP
Routine Command
1-shot Word
B3:47 MOV
0000 Move
1 Source 4
4<
Dest N22:10
4<
N22:11 = The Communication Reference (CR) to read from. There is a unique CR for each Station.
"2" = CR 2 = Station 1.0
"3" = CR 3 = Station 2.0
PCP Read PCP Read
Routine Command Msg
1-shot CR
B3:47 MOV
0001 Move
1 Source N22:0
2<
Dest N22:11
2<
Figure 7.9 – LAD5 - PCP Read Subroutine

N22:12 = Index (the parameter number or fault/event queue item to be read)
N22:1 determines what area is to be read:
N22:1 determines
0=SP600 (Host) what area is to
parameter be read:
(N22:2 + 12288 decimal (3000h) = mapped parameter address)
01=RECOMM-IBUS
= PowerFlex 70 (Host) parameter(N22:2
parameter (N22:2 decimal
+ 12288 decimal
(2FB5h)(3000h) = mapped
= mapped parameter
parameter address)
address)
1 = 20-COMM-I
2=SP600 parameter
(Host) (N22:2(N22:2
Fault queue + 12213+ decimal (2FB5h) =(2FF8h)
12280 decimal mapped =parameter
mappedaddress)
fault item)
2 = PowerFlex 70 (Host) Fault queue (N22:2 + 12280 decimal (2FF8h) = mapped fault item)
3=RECOMM-IBUS Event Queue (N22:2 + 12205 decimal (2FADh) = mapped event item)
3 = 20-COMM-I Event Queue (N22:2 + 12205 decimal (2FADh) = mapped event item)
PCP Read PCP Read PCP Read
Routine Param / Queue Command Msg
1-shot to Read Index
B3:47 EQU ADD
0002 Equal Add
1 Source A N22:1 Source A N22:2
0< 1<
Source B 0 Source B 12288
0< 12288 <
Dest N22:12
12289 <
PCP Read PCP Read

Param / Queue Command Msg
to Read Index
EQU ADD
Equal Add
Source A N22:1 Source A N22:2
0< 1<
1< 12213 <
Dest N22:12
12289 <
PCP Read PCP Read

to Read Index
EQU ADD
Equal Add
0< 1<
2< 12280 <
Dest N22:12
12289 <
PCP Read PCP Read

to Read Index
EQU ADD
Equal Add
0< 1<
3< 12205 <
Dest N22:12
12289 <
N22:13 = Sub Index (Not used)

PCP Read PCP Read
Routine Command Msg
1-shot Sub Index
B3:47 MOV
0003 Move
1 Source 0
0<
Dest N22:13
0<
Figure 7.10 – LAD5 - PCP Read Subroutine (Continued)

Copy the PCP Read Command message to the scanner for transmission on the network.
PCP Read
Routine
1-shot
B3:47 COP
0004 Copy File
1 Source #N22:10
Dest #M0:1.0
Length 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
0005 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).
Status Command
PCP Read PCP Read
M1:1.0 M0:1.0
0006 U
2 2
When the scanner Status word indicates that a message is available, copy the message for processing and handshake with the
scanner by turning the Command word Message Acknowledge bit ON.
Status PCP Read PCP Read
Message Reply Msg Reply Msg
Present 1-Shot Status Word
M1:1.0 B3:47 COP
0007 Copy File
15 2 Source #M1:1.0
Dest #N22:20
Length 8
Command
Message
Acknowledge
M0:1.0
L
15
If the Reply contains only 1 byte of data, then the high and low bytes need to be swapped (e.g. a value of "5" will be stored as a
"0005" as opposed to "0500".
Status PCP Read PCP Read PCP Read
Message Reply Msg Reply Msg Reply Msg
Present 1-Shot # Bytes of Data Data Word #1
M1:1.0 B3:47 EQU SWP
0008 Equal Swap
15 2 Source A N22:25 Source #N22:26
2< Length 1
Source B 1
1<
If the Reply does not contain 4 bytes of data, then the parameter is not 32-bit and Data Word #2 needs to be zero'd (might
contain leftover data from a previous 4-byte PCP Read).
Present 1-Shot # Bytes of Data Data Word #2
M1:1.0 B3:47 NEQ MOV
0009 Not Equal Move
15 2 Source A N22:25 Source 0
2< 0<
Source B 4 Dest N22:27
4< 0<

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).
Present 1-Shot Result Data Word #1
M1:1.0 B3:47 NEQ MOV
0010 Not Equal Move
15 2 Source A N22:24 Source 0
0< 0<
Source B 0 Dest N22:26
0< 325<
PCP Read
Reply Msg
Data Word #2
MOV
Move
Source 0
0<
Dest N22:27
0<
The PCP Read Reply 1-shot is used so the subroutine processes the Reply message only once.
Status PCP Read
Message Reply Msg
Present 1-Shot
M1:1.0 B3:47
0011 L
15 2
When the Command / Status Message handshake is complete, reset the 1-shot bits and exit the PCP Read routine by turning the
"Execute PCP Read" bit off (B3:47/0)
Command Status Execute
Message Message PCP Read
Acknowledge Present Subroutine
M0:1.0 M1:1.0 B3:47
0012 U
15 15 0
PCP Read
Routine
1-shot
B3:47
U
1
PCP Read
Reply Msg
1-Shot
B3:47
U
2
Command
Message
Acknowledge
M0:1.0
U
15
0013 END

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:10 = PCP Command Word (Set to "8" to cause a PCP Write: an "8" = bit 3 ON)
PCP Write PCP

Routine Command
1-shot Word
B3:47 MOV
0000 Move
11 Source 8
8<
Dest N23:10
8<
N23:11 = CR (The Communication Reference to write to. A unique CR is the established for each Station)
"2" = CR 2 = Station 1.0
"3" = CR 3 = Station 2.0
PCP Write PCP Write
Routine Command Msg
1-shot CR
B3:47 MOV
0001 Move
11 Source N23:0
2<
Dest N23:11
2<
N23:12 = Index
N23:1 determines what area is to be written to:

0 == PowerFlex 70 (Host)
SP600 (Host) parameter
parameter (N23:2(N23:2
+ 12288+ 12288
decimaldecimal
(3000h)(3000h) = mapped
= mapped parameter
parameter address)
address)
1 == 20-COMM-I
RECOMM-IBUS parameter
parameter (N23:2
(N23:2 + 12213
+ 12213 decimal
decimal (2FB5h)
(2FB5h) = mapped
= mapped parameter
parameter address)
address)
PCP Write PCP Write PCP Write
Routine Parameter Area Command Msg
1-shot to Write Index
B3:47 EQU ADD
0002 Equal Add
11 Source A N23:1 Source A N23:2
0< 107<
0< 12288 <
Dest N23:12
12395 <
PCP Write PCP Write

Parameter Area Command Msg
to Write Index
EQU ADD
Equal Add
0< 107<
1< 12213 <
Dest N23:12
12395 <
N23:13 = Sub Index (Not used)

PCP Write PCP Write
Routine Command Msg
1-shot Sub Index
B3:47 MOV
0003 Move
11 Source 0
0<
Dest N23:13
0<
Figure 7.13 – LAD6 - PCP Write Subroutine

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)
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. a "2" instead of a "0200" hex).
PCP Write PCP Write
Routine Command Msg
1-shot # Bytes of Data
B3:47 COP
0004 Copy File
11 Source #N23:3
Dest #N23:14
Length 3
PCP Write
Command Msg
# Bytes of Data
EQU SWP
Equal Swap
Source A N23:14 Source #N23:15
2< Length 1
Source B 1
1<
Copy the PCP Write Command message to the scanner for transmission on the network.
PCP Write
Routine
1-shot
B3:47 COP
0005 Copy File
11 Source #N23:10
Dest #M0:1.0
Length 7
The PCP Write Command 1-shot is used so the subroutine processes and sends the Command only once when called by the
MAIN PGM
PCP Write
Routine
1-shot
B3:47
0006 L
11
When
When thethe scanner
scanner acknowledges
acknowledges theWrite
the PCP PCPcommand,
Write command, turn the Command
turn the Command wordbitPCP
word PCP Write OFF Write bit OFF
(originally comes(originally
from
comeswhich
N23:10 fromwas
N23:10 which
COPied was
to M0: copied to M0: above).
above).
Status Command
PCP Write PCP Write
M1:1.0 M0:1.0
0007 U
3 3
When the scanner Status word indicates that a message is available, copy the message into an Interger file (N23:) for processing
and handshake with the scanner by turning the Command word Message Acknowledge bit ON.
Status PCP Write PCP Write
Message Reply Msg Reply Msg
Present 1-Shot Status Word
M1:1.0 B3:47 COP
0008 Copy File
15 12 Source #M1:1.0
Dest #N23:20
Length 5
Command
Message
Acknowledge
M0:1.0
L
15
Figure 7.14 – LAD6 - PCP Write Subroutine (Continued)

Status PCP Write
Message Reply Msg
Present 1-Shot
M1:1.0 B3:47
0009 L
15 12
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
0010 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
0011 END
Figure 7.15 – LAD6 - PCP Write Subroutine (Continued)

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
Status
Number Indicator Description Section
CC Cable Check 8.1.1
RD Remote Bus Disable 8.1.2
TR Transmit/Receive 8.1.3
BA Bus Active 8.1.4
UL 1 Bus Voltage 8.1.5
Figure 8.1 – Status Indicators (Location on Drive May Vary)

1 The UL indicator cannot be seen when the drive cover is installed or
closed.
Troubleshooting the Interbus Module and Network 8-1

Important: 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.
8.2 Cable Check (CC) Status Indicator

Table 8.1 – Cable Check (CC) Status Indicator: State Definitions
Status Cause Corrective Action

Off Master is reset or no • Connect the module to the
cable connection. network using an Interbus
cable.
• Verify master not in reset.
Solid Cable connection • No action required.
Green good.
8.3 Remote Bus Disable (RD) Status

Indicator
Table 8.2 – Remote Bus Disable (RD) Status Indicator: State Definitions
Status Cause Corrective Action

Off Outgoing remote bus • No action required.
is not switched off.
Solid Red Outgoing remote bus • Read configuration or start data
is switched off. transmission. Master may have
to be reset first.
8.4 Transmit/Receive (TR) Status

Indicator
Table 8.3 – Transmit/Receive (TR) Status Indicator: State Definitions
Status Cause Corrective Actions

Off No PCP connection is • Verify that master is sending
carried out. PCP messages.
Solid A PCP connection is • No action required.
Green being carried out.
Flashes when a new
PCP frame has been
received.

8.5 Bus Active (BA) Status Indicator
Table 8.4 – Bus Active (BA) Status Indicator: State Definitions

Off Bus not active. • Set master to start data
transmission.
Solid Bus active, • No action required.
Green exchanging data.
Flash Bus active, but no • Set master to start data
Green data exchange. transmission.
8.6 Bus Voltage (UL) Status Indicator

Table 8.5 – Bus Voltage (UL) Status Indicator1: State Definitions

Off Bus voltage is not OK. • Securely connect the module to
the drive using the Internal
interface cable
• Apply power to the drive.
Solid Bus active. • No action required.
Green
1
LED is visible only when the drive cover is open.
8.7 Module Diagnostic Items

Module Diagnostic Items can be viewed using VS Utilities software
or an LCD OIM. Diagnostic items show current data being
transmitted and received by the Host device (e.g., drive), and other
diagnostic information regarding the RECOMM-IBUS module.
Table 8.6 – Module Diagnostic Items
No. Event Description

1 Common Logic The current value of the Common Logic Command
Cmd being transmitted to the Host.
2 Prod Logic Cmd The current value of the Product-Specific Logic
Command being transmitted to the Host.
3 Reference The current value ofthe Product-Specific Reference
being transmitted to the Host.
4 Common Logic The current value of the Product-Specific Logic
Sts Status being received from the Host.

Table 8.6 – Module Diagnostic Items (Continued)

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
9 Datalink B1 In The current value of Datalink B1 being transmitted
10 Datalink B2 In The current value of Datalink B2 being transmitted
11 Datalink C1 In The current value of Datalink C1 being transmitted
to the Host. (Value of 0 if Datalink not used).
12 Datalink C2 In The current value of Datalink C2 being transmitted
13 Datalink D1 In The current value of Datalink D1 being transmitted
14 Datalink D2 In The current value of Datalink D2 being transmitted
15 Datalink A1 Out The current value of Datalink A1 being received
from the Host.
16 Datalink A2 Out The current value of Datalink A2 being received
from the Host.
17 Datalink B1 Out The current value of Datalink B1 being received
from the Host.
18 Datalink B2 Out The current value of Datalink B2 being received
from the Host.
19 Datalink C1 Out The current value of Datalink C1 being received
from the Host.
20 Datalink C2 Out The current value of Datalink C2 being received
from the Host.
21 Datalink D1 Out The current value of Datalink D1 being received
from the Host.
22 Datalink D2 Out The current value of Datalink D2 being received
from the Host.
23 Field Flash Cntr The number of times this device has been flash
updated.

Table 8.6 – Module Diagnostic Items (Continued)

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.
To View and Clear Events Using an LCD OIM

Use the procedure shown in figure 8.2 to access the event queue
using the LCD OIM. Note that you must have the RECOMM-IBUS
module as the selected device to access the event queue.
>> Stopped Auto

P5: RECOMM-IBUS
Main Menu
Diagnostics: EvtQ# 1 : E#xxxxx
View Event Queue Online @ 500kbps
Device Version
OIM Version
Diagnostics Clrqu
Monitor Lang
Highlight item Press F2 key to
clear event queue
Highlight Diagnostics icon
Figure 8.2 – VIewing and Clearing Events Using an LCD OIM

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 Empty event queue entry.
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.
3 Ping Time Flt A ping message was not received on DPI within
the specified time.
4 Port ID Flt The module is not connected to a correct port on a
DPI product.
5 Port Change The DPI port changed.
Flt
6 Host Sent The DPI product issued this because it was reset.
Reset
7 EEPROM Sum The EEPROM in the module is corrupt.
Flt
8 Online @ The module and DPI product are communicating
125kbps at 125kbps.
9 Online @ The module and DPI product are communicating
500kbps at 500kbps.
10 Bad Host Flt The module was connected to an incompatible
product.
11 Dup. Port Flt Another peripheral with the same port number is
already in use.
12 Type 0 Login The module has logged in for type 0 control.
13 Type 0 Time Flt The module has not received a type 0 status
message within the specified time.
14 DL Login The module has logged into a Datalink.
15 DL Reject Flt The host rejected an attempt to log in to a Datalink
because the Datalink is not supported or is used
by another peripheral.
16 DL Time Flt The module has not received a Datalink message
within the specified time.
17 Control The module has sent a “Soft Control Disable”
Disabled command to the DPI product.
18 Control The module has sent a “Soft Control Enable”
Enabled command to the DPI product.

Table 8.7 – Event Codes and Descriptions (Continued)
Code Event Description

19 Message A Client-Server message sent by the peripheral
Timeout 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 The module detected a fault condition on the
Interbus network.
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.
25 IB Online The Interbus module has gone on-line the Interbus
network.
26 IB Offline The Interbus module has gone off-line the Interbus
network.
27 Lang CRC Bad Language file CRC is Bad

APPENDIX A
Technical
Specifications
Communications
Network
Protocol Interbus
Data Rates 500 K
Drive
Protocol DPI
Data Rates 125 K or 500 K
Electrical
Consumption 450 mA at 5 V supplied through the drive
Mechanical
Dimensions
Height 19 mm (0.75 in)
Length 86 mm (3.33 in)
Width 78.5 mm (3.09 in)
Weight 65 g (2.3 oz)
Environmental
Temperature
Operating -10 to +50°C (14 to 149°F)
Storage -40 to +85°C (-40 to 185°F)
Relative Humidity 5 to 95% non-condensing
Regulatory Compliance
UL 508C and CUL
CE EN50081-2 (1993) and EN61000-6-2 (1999)
Technical Specifications A-1

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.
The parameters in the Interbus module are numbered sequentially.

However, depending on the configuration tool used, they may have
different numbers.
Interbus Module Parameters B-1

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. The drive determines the size of
the Reference/Feedback.
4 Datalink Size
Range: 0 = 16-bit
1 = 32-bit
Default: 0 = 16-bit
Type: Read Only
Reset Required: N/A
Size of each Datalink word. The drive determines the size of
Datalinks.
B-2 Interbus Communications Module

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.
ATTENTION: If the module is transmitting I/O that

controls the drive, the drive may fault when you reset
or damage to equipment.
6 Comm Flt Action

Range: 0 = Fault
1 = Stop
2 = Zero Data
3 = Hold Last
4 = Send Flt Cfg
Default: 0 = Fault
Type: Read/Write
Reset Required: No
Action that the module and drive take if the module detects that
Interbus communications have been disrupted. This setting is
effective only if I/O that controls the drive is transmitted though the
module.
ATTENTION: Comm Flt Action (6) lets you

determine the action the module and connected
! drive if communications are disrupted. By default,
this parameter faults the drive. You can set this
parameter so that the drive continues to run. Take
precautions to ensure that the setting of this
parameter does not create a hazard of injury or
equipment damage. Failure to observe this
equipment.

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
I/O that is transferred through the module.
ta C
D
Cm link A
Da link B
No Used
Da sed
No Used
ef
Da alink
Da link
d/R
1 = I/O Enabled
tU
ta
ta
t
t
t
0 = I/O Disabled
No
x x x 0 0 0 0 1 x =Not Used
7 6 5 4 3 2 1 0
Figure B.1 – DPI I/O Config (8)
ATTENTION: If the module is transmitting I/O that

controls the drive, the drive may fault when you reset
or damage to equipment.

9 DPI I/O Active
Range: See figure B.2.
Default: See figure B.2.
Type: Read Only
Reset Required: N/A
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).
tali C
D
Cm link A
Da k B
No Used
Da sed
No Used
ef
Da alink
Da link
d/R
1 = I/O Enabled
tU
ta
ta
t
t
t
0 = I/O Disabled
No
x x x 0 0 0 0 1 x =Not Used
7 6 5 4 3 2 1 0
Figure B.2 – DPI I/O Active (9)
10 Flt Cfg Logic

Range: 0000 0000 0000 0000 to 1111 1111 1111 1111
Default: 0000 0000 0000 0000
Type: Read/Write
Reset Required: No
Sets the Logic Command data that is sent to the drive if the
following is true:
• Comm Flt Action (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 or Test mode.
The bit definitions will depend on the product to which the module is
connected.

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:
are disrupted.
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.
12 Flt Cfg A1
13 Flt Cfg A2
14 Flt Cfg B1
15 Flt Cfg B2
16 Flt Cfg C1
17 Flt Cfg C2
18 Flt Cfg D1
19 Flt Cfg D2
Range: 0 to 4294967295
Default: 0
Type: Read/Write
Reset Required: No
Sets the data that is sent to the Datalink in the drive if any of the
following is true:
are disrupted.
Program mode.

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
Default: N/A
Type: Read Only
Reset Required: N/A
Actual Process Input Data Description for Word 0.
22 PIDD W1 Cfg
Default: 0x2F9B (Feedback)
Type: Read/Write
restarted)
Configured Process Input Data Description for Word 1, PCP Object

23 PIDD W1 Actual
Default: N/A
Type: Read Only
Reset Required: N/A

24 PIDD W2 Cfg
Default: 0
Type: Read/Write
restarted)

25 PIDD W2 Actual
Default: N/A
Type: Read Only
Reset Required: N/A
26 PIDD W3 Cfg
Default: 0
Type: Read/Write
restarted)

27 PIDD W3 Actual
Default: N/A
Type: Read Only
Reset Required: N/A

28 PIDD W4 Cfg
Default: 0
Type: Read/Write
restarted)

29 PIDD W4 Actual
Default: N/A
Type: Read Only
Reset Required: N/A
30 PIDD W5 Cfg
Default: 0
Type: Read/Write
restarted)

31 PIDD W5 Actual
Default: N/A
Type: Read Only
Reset Required: N/A

32 PIDD W6 Cfg
Default: 0
Type: Read/Write
restarted)

33 PIDD W6 Actual
Default: N/A
Type: Read Only
Reset Required: N/A
34 PIDD W7 Cfg
Default: 0
Type: Read/Write
restarted)

35 PIDD W7 Actual
Default: N/A
Type: Read Only
Reset Required: N/A

36 PIDD W8 Cfg
Default: 0
Type: Read/Write
restarted)

37 PIDD W8 Actual
Default: N/A
Type: Read Only
Reset Required: N/A
38 PODD W0 Cfg
Default: 0X2F98
Type: Read/Write
restarted)
Configured Process Output Data Description for Word 0. PCP

Object to use for Word 0 received from Interbus master.
39 PODD W0 Actual
Default: N/A
Type: Read Only
Reset Required: N/A
Actual Process Output Data Description for Word 0.

40 PODD W1 Cfg
Default: 0X2F99
Type: Read/Write
restarted)

41 PODD W1 Actual
Default: N/A
Type: Read Only
Reset Required: N/A
42 PODD W2 Cfg
Default: 0
Type: Read/Write
restarted)

43 PODD W2 Actual
Default: N/A
Type: Read Only
Reset Required: N/A

44 PODD W3 Cfg
Default: 0
Type: Read/Write
restarted)

45 PODD W3 Actual
Default: N/A
Type: Read Only
Reset Required: N/A
46 PODD W4 Cfg
Default: 0
Type: Read/Write
restarted)

47 PODD W4 Actual
Default: N/A
Type: Read Only
Reset Required: N/A

48 PODD W5 Cfg
Range: See table b.1
Default: 0
Type: Read/Write
restarted)

49 PODD W5 Actual
Default: N/A
Type: Read Only
Reset Required: N/A
50 PODD W6 Cfg
Default: 0
Type: Read/Write
restarted)

51 PODD W6 Actual
Default: N/A
Type: Read Only
Reset Required: N/A

52 PODD W7 Cfg
Default: 0
Type: Read/Write
restarted)

53 PODD W7 Actual
Default: N/A
Type: Read Only
Reset Required: N/A
54 PODD W8 Cfg
Default: 0
Type: Read/Write
restarted)

55 PODD W8 Actual
Default: N/A
Type: Read Only
Reset Required: N/A

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.1 – PIDD / PODD Indexes
Input Output
Value Value Value Value
(Hex) (Dec) Selects (Hex) (Dec) Selects
2F9A 12186 Logic Status 2F98 12184 Logic
Command
2F9B 12187 Feedback 2F99 12185 Reference
2FA4 12196 Datalink A1 Out 2F9C 12188 Datalink A1 In
2FA5 12197 Datalink A2 Out 2F9D 12189 Datalink A2 In
2FA6 12198 Datalink B1 Out 2F9E 12190 Datalink B1 In
2FA7 12199 Datalink B2 Out 2F9F 12191 Datalink B2 In
2FAA 12202 Datalink D1 Out 2FA2 12194 Datalink D1 In
2FAB 12203 Datalink D2 Out 2FA3 12195 Datalink D2 In

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 Command Word
Logic Bits
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Command Description
x Stop 0 = Not Stop
1 = Stop
x Start 1 0 = Not Start
1 = Start
x Jog 0 = Not Jog
1 = Jog
x Clear Faults 0 = Not Clear Faults
1 = Clear Faults
x x Direction 00 = No Command
01 = Forward Command
10 = Reverse Command
11 = Hold Direction Control
x Local Control 0 = No Local Control
1 = Local Control
x MOP 0 = Not Increment
Increment 1 = Increment
x x Accel Rate 00 = No Command
01 = Accel Rate 1 Command
10 = Accel Rate 2 Command
11 = Hold Accel Rate
x x Decel Rate 00 = No Command
01 = Decel Rate 1 Command
10 = Decel Rate 2 Command
11 = Hold Decel Rate
Logic Command/Status Words C-1

Logic Bits
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Command Description
x x x Reference 000 = No Command
Select 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)
x MOP 0 = Not Decrement
Decrement 1 = Decrement
1
A 0 = Not Stop condition (logic 0) must first be present before a 1 = Start condition
will start the drive.
Logic Status Word
Logic Bits
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Status Description
x Ready 0 = Not Ready
1 = Ready
x Active 0 = Not Active
1 = Active
x Command 0 = Reverse
Direction 1 = Forward
x Actual 0 = Reverse
Direction 1 = Forward
x Accel 0 = Not Accelerating
1 = Accelerating
x Decel 0 = Not Decelerating
1 = Decelerating
x Alarm 0 = No Alarm
1 = Alarm
x Fault 0 = No Fault
1 = Fault
x At Speed 0 = Not At Reference
1 = At Reference
x x x Local 000 = Port 0 (TB)
Control 001 = Port 1
010 = Port 2
011 = Port 3
100 = Port 4
101 = Port 5 “Network”
110 = Port 6
111 = No Local
C-2 Interbus Communications Module

Logic Bits
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Status Description
x x x x Reference 0000 = Ref A Auto
0001 = Reserved
0010 = Preset 2 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
Logic Command/Status Words 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.
The RECOMM-IBUS module is an module that connects SP600

drives to a Interbus network. Modules are sometimes also called
“adapters,” “cards,” “embedded communication options,” “gateways,”
and “peripherals.”
Communication Reference (CR) - Identifies an Interbus device in

the parameter data channel (PCP). To send a PCP service to a
device, its CR must be specified. The CRs begin at “2” and must be
assigned in ascending order.
controller - Also called programmable logic controller. A solid-state

control system that has a user-programmable memory for storage
of instructions to implement specific functions such as I/O control,
logic, timing, counting, report generation, communication,
arithmetic, and data file manipulation. A controller consists of a
central processor, input/output interface, and memory. See also
scanner.
data rate - The data rate is the speed at which data is transferred
on the Interbus network (fixed at 500 K).
Datalink - A type of pointer used by some SP600 drives to transfer

data to and from the controller. Datalinks allow specified parameter
value(s) to be accessed or changed without using explicit
messages. When enabled, each Datalink consumes either four
bytes or eight bytes in both the input and output image table of the
controller. The drive determines the size of Datalinks.
DPI - A peripheral communication interface used by various

Reliance Electric drives and power products.
DPI peripheral - A device that provides an interface between DPI

and a network or user. Peripheral devices are also referred to as
“adapters” and “modules.” The serial converter and SP600 OIM are
examples of DPI peripherals.
Glossary Glossary-1
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.
fault action - Determines how the module and connected product

act when a communications fault (for example, a cable is
disconnected) occurs or when the modules receives a “Stop
Transmission” command from the scanner. The former uses a
communications fault action, and the latter uses an idle fault action.
fault configuration - When communications are disrupted (for

example, a cable is disconnected), the module and SP600 drive can
respond with a user-defined fault configuration. The user sets the
data that is sent to the drive in the fault configuration parameters
(parameters 10 (Flt Cfg Logic) through 19 (Flt Cfg D2)). When a
fault action parameter is set to use the fault configuration and a fault
occurs, the data from these parameters is sent as the Command
Logic, Reference, and/or Datalink(s).
flash update - The process of updating firmware in the module.

The module can be flash updated using the X-Modem protocol and
a RECOMM-232 serial converter.
hold last - When communications are disrupted (for example, a

cable is disconnected), the module and SP600 drive can respond by
holding last. Hold last results in the drive receiving the last data
received via the Interbus connection before the disruption. If the
drive was running and using the reference from the module, it will
continue to run at the same reference.
I/O data - I/O data transmit time-critical data such as a Logic

Command and Reference. The terms “input” and “output” are
defined from the scanner’s point of view. Output is transmitted by
the scanner and consumed by the module. Input is transmitted by
the module and consumed by the scanner.
Interbus Network - An Interbus network uses RS485 to connect

devices (for example, controllers, drives, and motor starters) and it
can support a maximum of 126 devices in a daisy chain
connection., Each device is assigned a unique node address and
transmits data on the network at the same data rate.
General information about Interbus and the Interbus specification

are maintained by the Interbus Club at http://www.ibsclub.com.
Logic Command/Logic Status - The Logic Command is used to

control the SP600 drive (e.g., start, stop, direction). It consists of
one 16-bit word of input to the module from the network. The
definitions of the bits in this word depend on the drive.
Glossary-2 Interbus Communications Module

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.”
operator interface module (OIM) - A device that can be used to

configure and control an SP600 drive.
PIDD (Process Input Data Description) - Words used to mapping

input data on the network. Examples of input data include Logic
Status, Feedback, and Datalinks (Datalink x1 Out).
ping - A message that is sent by a DPI product to its peripheral

devices. They use the ping to gather data about the product,
including whether it can receive messages and whether they can
log in for control.
reference/feedback - The reference is used to send a reference

(for example, speed, frequency, torque) to the product. It consists of
one word of input to the module from the network. The size of the
word (either a 16-bit word or 32-bit word) is determined by the drive.
Feedback is used to monitor the speed of a product. It consists of

one word of output from the module to the network. The size of the
word (either a 16-bit word or 32-bit word) is determined by the drive.
scanner - 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. Also called a
master. See also controller.
status indicators - LEDs that are used to report the status of the
module, network, and drive. They are on the module and can be
viewed on the front cover of the drive when the drive is powered.
VS Utilities software - A Windows-based software tool for

monitoring and configuring Reliance Electric products and modules.
VS Utilities can be used to configure the Interbus module and
SP600 drives.
zero data - When communications are disrupted (for example, a

cable is disconnected), the module and drive can respond with zero
data. Zero data results in the drive receiving zero as values for
command data. If the drive was running and using the reference
from the module, it will stay running but at zero reference.
Glossary Glossary-3
Glossary-4 Interbus Communications Module
INDEX
A events
codes and descriptions, 8-6
assistance, technical, 1-2 viewing and clearing, 8-5
examples
datalinks, 6-6
B PCP message read, 7-7
BA status indicator, 8-3 PCP write messages, 7-12
bus active (BA) status indicator, 8-3 SLC ladder for PCP, 7-16
bus in Interbus connector SLC ladder logic program, 6-6
location of, 2-1 Explicit Messaging, using, 7-1
terminals, 3-2
bus out Interbus connector F
location of, 2-1
terminals, 3-2 fault action, setting, 4-5
bus voltage (UL) status indicator, 8-3 fault configuration parameters,
setting, 4-6
Flt Cfg A1 (12), B-6
C Flt Cfg A2 (13), B-6
cable check (CC) status indicator, 8-2 Flt Cfg B1 (14), B-6
cables, Internal Interface, 3-4 Flt Cfg B2 (15), B-6
CC status indicator, 8-2 Flt Cfg C1 (16), B-6
CMD software, 5-1 Flt Cfg C2 (17), B-6
Comm Flt Action (6), B-3 Flt Cfg D1 (18), B-6
communications specifications, A-1 Flt Cfg D2 (19), B-6
configuration tools, 4-1 Flt Cfg Logic (10), B-5
connector Flt Cfg Ref (11), B-6
bus in Interbus, 2-1
bus out Interbus, 2-1 G
DPI, 2-1
grounding the module, 3-5
D
I
Datalink Size (4), B-2
Datalinks, using, 6-4 I/O configuration, 4-2
dimensions, module, A-1 I/O messaging, using, 6-1 to 6-12
DPI connector, 2-1 installation checklist, 2-3
DPI Data Rate (2), B-2 Internal Interface cable, 3-4
DPI I/O Active (9), B-5
DPI I/O Config (8), B-4
DPI Port (1), B-2
L
LCD OIM see OIM
E Logic Command/Status words, C-1 to
C-3
equipment required for installation, 2-2 Logic Command/Status, using, 6-4
Index Index-1
M PIDD W4 Cfg (28), B-9
PIDD W5 Actual (31), B-9
mechanical specifications, A-1 PIDD W5 Cfg (30), B-9
module PIDD W6 Actual (33), B-10
components, 2-1 PIDD W6 Cfg (32), B-10
configuration, viewing, 4-8 PIDD W7 Actual (35), B-10
configuring, 4-1 to 4-9 PIDD W7 Cfg (34), B-10
connecting to drive, 3-4 PIDD W8 Actual (37), B-11
connecting to network, 3-1 PIDD W8 Cfg (36), B-11
diagnostics items, 8-3 PODD W0 Actual (39), B-11
dimensions, A-1 PODD W0 Cfg (38), B-11
features, 1-1 PODD W1 Actual (41), B-12
grounding, 3-5 PODD W1 Cfg (40), B-12
installing, 3-1 to 3-6 PODD W2 Actual (43), B-12
mounting, 3-5 PODD W2 Cfg (42), B-12
parameters, B-1 to B-16, ?? to PODD W3 Actual (45), B-13
B-16 PODD W3 Cfg (44), B-13
resetting, 4-7 PODD W4 Actual (47), B-13
specifications, A-1 PODD W4 Cfg (46), B-13
troubleshooting, 8-1 to 8-7 PODD W5 Actual (49), B-14
mounting the module, 3-5 PODD W5 Cfg (48), B-14
PODD W6 Actual (51), B-14
PODD W6 Cfg (50), B-14
N PODD W7 Actual (53), B-15
network PODD W7 Cfg (52), B-15
configuring using CMD PODD W8 Actual (55), B-15
software, 5-1, 5-3 PODD W8 Cfg (54), B-15
sample wiring, 3-3 power consumption, A-1
protocol, A-1
publications, related, 1-2
O
OIM (Operator Interface Module) R
configuring the module with, 4-2
RD status indicator, 8-2
Ref/Fdbk Size (3), B-2
P Reference/Feedback, using, 6-4
parameters, Interbus module, B-1 to regulatory compliance, A-1
Reliance Electric, getting assistance
B-16, ?? to B-16
from, 1-2
PCP Comm Act (57), B-16
Remote bus disable (RD) status
PCP Comm Cfg (56), B-16
indicator, 8-2
PCP communications, 7-3
Reset Module (5), B-3
PIDD / PODD Indexes, B-16
PIDD W0 Cfg (20), B-7 S
PIDD W1 Cfg (22), B-7 scanner
PIDD W2 Actual (25), B-8 configuring, 5-16
PIDD W2 Cfg (24), B-8 I/O layout, 5-10
PIDD W3 Actual (27), B-8 scanner mapping / SLC addressing, 5-9
PIDD W3 Cfg (26), B-8 specifications, A-1
PIDD W4 Actual (29), B-9 status indicators, 8-1
Index-2 Interbus Communications Module

T U
TR status indicator, 8-2 UL status indicator, 8-3
transmit/receive (TR) status
indicator, 8-2
troubleshooting, 8-1 to 8-7
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: [email protected], 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.

Interbus

Uploaded by

Copyright:

Available Formats

Interbus

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Interbus

Uploaded by

Copyright:

Available Formats

Interbus

Instruction Manual D2-3480-1

ATTENTION:Identifies information about practices or circumstances

Important: Identifies information that is critical for successful application and

ATTENTION:The drive may contain high voltages that can cause

Interbus is a trademark of the Interbus Trade Organization.

©2002 Rockwell Automation. All rights reserved.

Chapter 2 Getting Started

Chapter 3 Installing the Interbus Module

Chapter 4 Configuring the Interbus Module

Chapter 5 Configuring the Interbus Scanner

Chapter 7 Using Explicit Messaging (PCP Communications)

Chapter 8 Troubleshooting the Interbus Module and Network

Appendix A Technical Specifications ...................................................... A-1

Appendix B Interbus Module Parameters ................................................ B-1

Appendix C Logic Command/Status Words............................................. C-1

Index ....................................................................................... Index-1

II Interbus Communications Module

Figure 3.1 – Sample Network Wiring .......................................................... 3-3

Figure 5.1 – Sample Interbus Network ....................................................... 5-2

Figure 8.1 – Status Indicators (Location on Drive May Vary)...................... 8-1

VI Interbus Communications Module

Table 4.1 – Configuration Tools.................................................................. 4-1

Table 7.1 – PCP Message Definition .......................................................... 7-3

This manual is intended for qualified electrical personnel familiar

1.1 Interbus Module Features

Documentation about the scanner, SST-IBS-SLC User’s Guide,

1.3 Conventions Used in This Manual

1.4 Getting Assistance from Reliance

For technical assistance, call 1-800-726-8112.

1-2 Interbus Communications Module

2.1 Interbus Module Components

 Status Indicators Five LEDs that indicate the status of the

Getting Started 2-1

Table 2.1 – Equipment Shipped with the Interbus Module

Table 2.2 lists user-supplied equipment also required to install and

Table 2.2 – Required User-Supplied Equipment

2-2 Interbus Communications Module

 Step Action Refer to

Getting Started 2-3

3.1 Preparing for an Installation

ATTENTION:The Interbus module contains ESD-

3.2 Connecting the Module to the

Step 1. Remove power from the drive.

Installing the Interbus Module 3-1

Terminal Name Description

Terminal Name Description

3-2 Interbus Communications Module

SST SLC Scanner

1 2 3 4 5 6 7 8 9 9-pin D-shell Shield

/DO1 DO1 /DI1 DI1 GND PE

Bus Out (See Table 3.2)

/DO1 DO1 /DI1 DI1 GND PE

Figure 3.1 – Sample Network Wiring

Step 5. Connect the Interbus connector to the module.

Installing the Interbus Module 3-3

 Interbus Module SP600 Drive

3-4 Interbus Communications Module

Internal Interface cable

Figure 3.1 – Mounting and Grounding the Interbus Module

Status Indicators Five LEDs that indicate the status of the

Step Action Refer to

Interbus Module SP600 Drive