3bua000359r0007 G en Symphony Communication Module Reference Table

Instruction
General Purpose Interface (GPI)

Version 3.0
Notice
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB. ABB assumes no responsibility for any errors that
may appear in this document.
In no event shall ABB be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB be
liable for incidental or consequential damages arising from use of any software or hard-
ware described in this document.
This document and parts thereof must not be reproduced or copied without written
permission from ABB, and the contents thereof must not be imparted to a third party nor
used for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.
This product meets the requirements specified in EMC Directive 89/336/EEC and in Low
Voltage Directive 72/23/EEC.
Copyright © 2008 by ABB.
All rights reserved.
Release: January 2008
Document number: 3BCA014034R0001 Rev F
Trademarks
Registrations and trademarks used in this document include:
Adaptec Registered trademark of Adaptec, Inc.

Adobe Acrobat Reader Registered trademark of Adobe Systems Inc
Ethernet Trademark of Xerox Corporation.
FrontPage Registered trademark of Microsoft Corporation.
Industrial IT Trademark of ABB.
Microsoft Registered trademark of Microsoft Corporation.
Pentium Registered trademark of Intel Corporation.
PROFIBUS Registered trademark of PROFIBUS International.

Windows Registered trademark of Microsoft Corporation.
Windows Server Trademark of Microsoft Inc.
3BCA014034R0001 Rev. F
Table of Contents
Section 1 — Introduction ..............................................................................................1-1

Overview .................................................................................................................. 1-1
Who Should Use This Manual .............................................................................. 1-2
Dependencies and Constraints ............................................................................. 1-2
Read Groups .................................................................................................... 1-2
Transactions Per Second .................................................................................. 1-2
Write To PLC Mode ........................................................................................... 1-2
Read vs Write Transactions RTU....................................................................... 1-3
Read vs Write Transaction AB.......................................................................... 1-3
Multiple Point Value Write Groups................................................................... 1-3
Baud Rates...................................................................................................... 1-3
Function Blocks .............................................................................................. 1-3
Multiple Point Value Read Groups ................................................................... 1-4
Data Not Suitable for a General Serial Interface ............................................... 1-4
Minimum Read Points Per PLC ........................................................................ 1-4
Relation to Composer ........................................................................................... 1-5
Diagram of GPI Design ......................................................................................... 1-5
Protocol Sub-Set Supported ................................................................................. 1-6
RTU.................................................................................................................. 1-6
RTUSLAVE ....................................................................................................... 1-7
AB.................................................................................................................... 1-7
Hardware Requirements ....................................................................................... 1-8
Work Station Requirements .............................................................................. 1-8
Controller Module Requirements ...................................................................... 1-8
Deliverables ....................................................................................................... 1-10
Glossary of Terms .............................................................................................. 1-11
References ............................................................................................................. 1-12
Document Conventions .......................................................................................... 1-12
Section 2 — Getting Started ........................................................................................2-1

Installing the User Interface Software ...................................................................... 2-1
Product Licensing ................................................................................................... 2-3
Controller Module Installation ................................................................................. 2-3
Dipswitch Settings .............................................................................................. 2-4
IMMFP02/IMMFP12 ........................................................................................ 2-4
IMMFP03/IMMPI01 ......................................................................................... 2-5
BRC100/BRC200/BRC300/BRC400 ............................................................... 2-7
HAC01 Initialization ............................................................................................ 2-8
Serial Interface Installation ..................................................................................... 2-9
Redundancy .................................................................................................. 2-10
Setting Up the Controller Module Termination ................................................... 2-13
RS-232 Communication .................................................................................... 2-16
3BCA014034R0001 Rev. F iii

Table of Contents(continued)
RS485 Communication ......................................................................................2-18
DCE/DTE Handshaking ....................................................................................2-21
Example J1/J2 Jumper Settings .......................................................................2-26
Allen-Bradley Data Highway Interface Module Settings ......................................2-31
Section 3— General Configuration Information .........................................................3-1

Host Controller Modules .......................................................................................... 3-2
RTUSLAVE and Modbus RTU Addresses .............................................................. 3-2
Single Value Data Transfer............................................................................... 3-3
Multiple Value Data Transfer ........................................................................... 3-3
Point Types.......................................................................................................... 3-3
Communication Overview ........................................................................................ 3-5
GPI RTU and PLCs that Support Modbus RTU ..................................................... 3-5
GPI AB PLC Data Addressing ...............................................................................3-7
Viewing Controller Module Error Log.................................................................... 3-9
Function Block Requirements................................................................................ 3-11
GPI RTU Program Support Blocks ...................................................................... 3-13
GPI AB Program Support Blocks ........................................................................ 3-18
RTUSLAVE Program Support Blocks .................................................................. 3-21
Serial Port Parameters (Optional) ....................................................................... 3-25
Section 4 — The User Interface ...................................................................................4-1

User Interface.......................................................................................................... 4-1
Main Menu .............................................................................................................. 4-1
Configuration Overview ........................................................................................... 4-3
UDF/Batch Support ................................................................................................ 4-7
Changing GPI Point Data OnLine ......................................................................... 4-8
Saving/Restoring Module File 2 Using Composer ........................................... 4-10
Re-Install Data File in Primary Module ........................................................... 4-10
Module Licensing................................................................................................... 4-13
Adding a License................................................................................................ 4-14
Editing a License ............................................................................................... 4-15
Deleting a License.............................................................................................. 4-16
Configuration Data File ......................................................................................... 4-16
GPI RTU ................................................................................................................ 4-16
Information Required For Configuration............................................................. 4-16
Configuration Menus ......................................................................................... 4-18
File Menu....................................................................................................... 4-19
Importing Configuration Data ........................................................................ 4-19
Edit Menu...................................................................................................... 4-20
Verify Configuration Menu ............................................................................. 4-21
Point Parameters ............................................................................................... 4-25
iv 3BCA014034R0001 Rev. F
Table of Contents
Analog Point Scaling.......................................................................................... 4-30
RTUSLAVE............................................................................................................ 4-32
Configuration Requirements.............................................................................. 4-32
User Interface Menus ........................................................................................ 4-35
GPI AB.................................................................................................................. 4-35
Information Required For The Configuration ...................................................... 4-35
Configuration Menus......................................................................................... 4-39
File Menu ....................................................................................................... 4-39
Importing Configuration Data ........................................................................ 4-40
Edit Menu ..................................................................................................... 4-40
Verify Configuration ...................................................................................... 4-41
Common Parameters............................................................................................. 4-43
Point Parameters................................................................................................... 4-47
Communicating with the RSLogix System ............................................................. 4-53
Composer Drawing Manager ................................................................................. 4-55
Creating Composer Drawings ............................................................................ 4-57
GPI Tag Database Modifications ........................................................................ 4-59
Common Parameters ......................................................................................... 4-60
Section 5 — Troubleshooting ......................................................................................5-1

General Information ................................................................................................ 5-1
The Module Startup Sequence................................................................................. 5-2
Monitoring the Link Status ..................................................................................... 5-3
Option Startup .................................................................................................... 5-3
Sections of the Monitor Screens........................................................................... 5-4
Allen-Bradley ...................................................................................................... 5-6
Modbus RTU ....................................................................................................... 5-9
GPI RTU Troubleshooting Information ................................................................... 5-11
Initial Startup Evaluation .................................................................................. 5-11
Check for Fatal Errors ....................................................................................... 5-12
Check the Error Log Messages........................................................................... 5-12
Block Access Errors .......................................................................................... 5-16
Example RTU Error Log..................................................................................... 5-16
Action Codes ..................................................................................................... 5-17
Error Code Counters ......................................................................................... 5-19
GPI AB Troubleshooting Information ..................................................................... 5-19
Check for Fatal Errors....................................................................................... 5-20
Check the Error Log Messages........................................................................... 5-20
Block Access Errors .......................................................................................... 5-24
RTUSLAVE Troubleshooting Information ............................................................... 5-25
3BCA014034R0001 Rev. F v
Table of Contents(continued)
Check for Fatal Errors ....................................................................................... 5-25
Check the Status Output Blocks........................................................................ 5-26
Status & Statistics Output Blocks ......................................................................... 5-31
Output Blocks for RTU ...................................................................................... 5-31
Output Blocks for AB......................................................................................... 5-34
Appendix A — GPI Database Structure ..................................................................... A-1
Appendix B — GPI RTU Reference Information ....................................................... B-1

Example Configuration (.RTU) File .......................................................................... B-1
GPI RTU Configuration Keywords ........................................................................... B-2
GPI RTU NVM Error File Messages .......................................................................... B-5
Appendix C — GPI AB Reference Information ......................................................... C-1

Example Configuration (.AB) File ............................................................................ C-1
GPI AB Configuration Keywords .............................................................................. C-2
GPI AB NVM Error File Messages ............................................................................ C-4
Appendix D — RS-232
Cable Configurations .................................................................................................. D-1
Appendix E — Example License String Document .................................................. E-1
Appendix F — Example GPI RTU Review Output File ...............................................F-1
Appendix G — Example GPI AB Review Output File ............................................... G-1
vi 3BCA014034R0001 Rev. F
List of Tables
No. Title Page
1-1. Modbus Functions Supported by RTU ....................................................... 1-6
1-2. Modbus Functions Supported by RTUSLAVE ............................................ 1-7
1-3. Allen-Bradley DF1 Commands Supported by AB ....................................... 1-7
1-4. Controller Module Requirements .............................................................. 1-9
1-5. Reference Documents ............................................................................. 1-12
2-1. IMMFP02/IMMFP12 Dipswitch Unit SW.................................................... 2-4
2-2. IMMFP02/IMMFP12 Dipswitch Unit SW2.................................................. 2-5
2-3. IMMFP03 Dipswitch Unit UUB0 (SW4) ..................................................... 2-6
2-4. IMMFP03 Dipswitch Unit UMB1 (SW1)...................................................... 2-6
2-5. BRC100/200/300/400 Dipswitch Unit SW5 ............................................. 2-8
2-6. BRC100/200/300/400 Dipswitch Unit SW2 ............................................. 2-8
2-7. Standard RS-232 Serial Cables ............................................................... 2-14
2-8. Standard RS-232 Signals ........................................................................ 2-14
2-9. Required Data Highway Interface Module Settings................................... 2-28
3-1. RTU Point Types ...................................................................................... 3-4
3-2. AB Point Types ......................................................................................... 3-4
3-3. AEG Modicon Address Mapping to Modbus RTU ....................................... 3-6
3-4 Modbus RTU Communication Adapter Modules ........................................ 3-6
3-5 GPI RTU, PLC Table References ................................................................ 3-7
3-6 Allen-Bradley Communication Adapter Modules ....................................... 3-7
3-7 GPI Data Point Connections .................................................................... 3-12
3-8 Required Program Support Function Blocks for GPI RTU ........................ 3-13
3-9 Modbus Port Options BAUD Rate ........................................................... 3-15
3-10 GPI RTU Segment Control Block Specifications ...................................... 3-16
3-11 GPI RTU Invoke C Block Specifications ................................................... 3-16
3-12 GPI RTU C Allocation Specification Values ............................................. 3-17
3-13 Required Program Support Function Blocks for GPI AB .......................... 3-18
3-14 GPI AB Segment Control Block Specifications ......................................... 3-19
3-15 GPI AB Invoke C Block Specifications ..................................................... 3-20
3-16 GPI AB C Allocation Block Specifications ................................................ 3-21
3-17 RTUSLAVE Program Support Function Blocks ....................................... 3-22
3-18 RTUSLAVE C Allocation Block Specifications ......................................... 3-24
3-19 RTUSLAVE Invoke C Block Specifications ............................................... 3-24
3-20 MODBUS Slave Port Options .................................................................. 3-26
4-1 Modbus PLC Point Data ......................................................................... 4-17
4-2 RTU Configuration Common Parameters ................................................ 4-23
4-3 RTU Point Parameters ............................................................................ 4-29
4-4 Allen-Bradley PLC Point Data ................................................................. 4-35
4-5 GPI AB Configuration Common Parameters ............................................ 4-46
4-6 GPI AB Point Parameters ........................................................................ 4-51
4-7 PLC Analog Value Maximum Ranges ...................................................... 4-53
4-8 GPI Tag Database Fields ........................................................................ 4-59
5-1 Module Performance Statistics .................................................................. 5-7
3BCA014034R0001 Rev. F vii

List of Tables (continued)
No. Title Page
5-2 Link Status ...............................................................................................5-7
5-3 PLC Last Retry Code .................................................................................5-7
5-4 Device Status ...........................................................................................5-7
5-5 Tunable Parameters .................................................................................5-8
5-6 Module Performance Statistics ................................................................5-10
5-7 Link Status ............................................................................................5-10
5-8 Link Performance Statistics ....................................................................5-10
5-9 Device Status .........................................................................................5-11
5-10 Tunable Parameters ...............................................................................5-11
5-11 RTU Fatal Errors ....................................................................................5-12
5-12 Modbus Error Code Definitions ...............................................................5-17
5-13 Action Code Definitions ..........................................................................5-18
5-14 AB Fatal Errors ......................................................................................5-20
5-15 RTUSLAVE Fatal Errors ..........................................................................5-26
5-16 RTU Status & Statistic Outputs ..............................................................5-31
5-17 AB Status Outputs .................................................................................5-34
A-1. ABconfig .................................................................................................. A-1
A-2. ABdetails.................................................................................................. A-1
A-3. RTUcfg .................................................................................................... A-2
A-4. RTUdetails ............................................................................................... A-4
A-5. ScaleNdx ................................................................................................. A-4
B-1. Keyword Descriptions .............................................................................. B-2
B-2. Error File Message and Description ......................................................... B-5
C-1. Keyword Descriptions .............................................................................. C-2
C-2. Error File Messages ................................................................................. C-4
viii 3BCA014034R0001 Rev. F

List of Figures
No. Title Page
1-1 GPI Design Diagram ................................................................................. 1-5
2-1 GPI Version Information ........................................................................... 2-2
2-2 Welcome Window ..................................................................................... 2-2
2-3 Module Licensing Screen .......................................................................... 2-3
2-4 Basic Serial Connection ........................................................................... 2-9
2-5 Serial Connection with Interposing Devices ............................................ 2-10
2-6 Typical redundant hardware configuration ............................................. 2-11
2-7 Total redundant hardware configuration ................................................ 2-12
2-8 NTMP01 Termination Unit Circuit Board ................................................ 2-13
2-9 NIMP01 Termination Module Circuit Board ............................................ 2-14
2-10 Communication TU Serial Port Jumpers ................................................ 2-15
2-11 NTMP01 Miscellaneous Jumpers ............................................................ 2-18
2-12 NIMP01 Miscellaneous Jumpers ............................................................. 2-19
2-13 HAC TU Miscellaneous Jumpers ............................................................ 2-20
2-14 NTMP01 Old and New Jumper Sets ........................................................ 2-21
2-15 NIMP01 Old and New Jumper Sets ......................................................... 2-22
2-16 HAC TU Jumper Sets ............................................................................. 2-23
2-17 NTMP01 Jumper Sets for DCE Handshaking .......................................... 2-24
2-18 NIMP01 Jumper Sets for DTE Handshaking ........................................... 2-25
2-19 NTMP01 Jumper Sets for Allen-Bradley 1771-KG with Cable 1771-CG.... 2-26
2-20 NTMP01 Jumper Sets for Allen-Bradley 1771-KG with Custom Cable...... 2-27
2-21 Custom Cable for Allen-Bradley 1771-KG RS-232 Interface .................... 2-28
2-22 NTMP01 Jumper Sets for Allen-Bradley 1770-KF2 with Standard Cable .. 2-29
2-23 NIMP01 Jumper Sets for Modicon 984/385 ............................................ 2-30
3-1 GPI Hardware Diagram ............................................................................. 3-1
3-2 Error File Windows ................................................................................ 3-10
3-3 Viewing Controller Module Files ............................................................. 3-11
4-1 The User Interface Main Screen ............................................................... 4-2
4-2 Installation to Module Menu .................................................................... 4-4
4-3 Initialize Module and Install Screen .......................................................... 4-5
4-4 Confirm Address and Status .................................................................... 4-6
4-5 Initial Download Dialog Box ..................................................................... 4-7
4-6 Reserve for UDF/Batch Dialog Box ........................................................... 4-8
4-7 Re-install Data File Preparation Prompt ................................................. 4-11
4-8 Re-install Data File Module Selection Screen .......................................... 4-11
4-9 Re-install Data File Completion Prompt Screen ...................................... 4-12
4-10 Re-install Data File Checkpointing Timer Box ........................................ 4-12
4-11 Composer Online Configuration Prompt Box .......................................... 4-13
4-12 Module Licensing Screen ........................................................................ 4-14
4-13 License Information Screen .................................................................... 4-15
4-14 MODBUS RTU Files Menu ..................................................................... 4-19
4-15 The Modbus RTU Edit ............................................................................ 4-20
4-16 The Modbus RTU Verify Configuration ................................................... 4-21
3BCA014034R0001 Rev. F ix
List of Figures (continued)
No. Title Page
4-17 Process RTU Configuration Screen .........................................................4-22
4-18 Modbus RTU Common Configuration Parameters Screen.........................4-22
4-19 Modbus RTU Grid Control Point Data Entry screen ................................4-25
4-20 Modbus RTU Single Point Data Entry Screen ..........................................4-26
4-21 Screen to Enter Scaling Coefficients .......................................................4-31
4-22 The Allen-Bradley File Menu ...................................................................4-39
4-23 The Allen-Bradley Edit Menu ..................................................................4-40
4-24 AB Verify Configuration Menu ................................................................4-41
4-25 Process Allen-Bradley Configuration Screen ............................................4-42
4-26 AB Configuration Common Parameters Screen .......................................4-43
4-27 AB Configuration Grid Control Point Data Entry Screen .........................4-47
4-28 AB Configuration Single Point Data Entry Screen ...................................4-48
4-29 Composer Drawing Manager ....................................................................4-57
4-30 Sample CLD ...........................................................................................4-58
5-1 Module Address Selection Screen .............................................................5-4
5-2 Allen-Bradley Monitor Screen ...................................................................5-6
5-3 Modbus RTU Monitor Screen ....................................................................5-9
B-1 Configuration (.RTU) Example ................................................................. B-1
D-1 Standard Cable L700550A1 Layout ......................................................... D-1
D-4 Standard Cable L700579M12 Layout ....................................................... D-2
D-5 Standard Cable L700579E5 Layout ......................................................... D-3
D-6 Standard Cable L700579M12 Layout ....................................................... D-3
D-7 Standard Cable L700579E4 Layout ......................................................... D-3
D-8 Standard Cable L700579K10 Layout ........................................................ D-4
E-1 License String Example ........................................................................... E-1
x 3BCA014034R0001 Rev. F
Safety Summary
Electrostatic Sensitive Device

Devices labeled with this symbol require special handling precau-
tions as described in the Installation section.
GENERAL Equipment Environment

WARNINGS All components, whether in transportation, operation or storage,
must be in a noncorrosive environment.
Electrical Shock Hazard During Maintenance

Disconnect power or take precautions to insure that contact with
energized parts is avoided when servicing.
SPECIFIC It is especially important to note that from the time the GPI point
WARNINGS data file is replaced in the primary module to the time that the Com-
poser Online Configuration is completed, the GPI point data file and
the function block configuration in the primary module are incompat-
ible. It is therefore important to perform both parts of the online
update procedure in one session to minimize the time during which
the backup module is not available and the primary module has
incompatible data in its NVM.
SPECIFIC If the Composer Online Configuration procedure is aborted for any

CAUTIONS reason and the backup module is returned to its backup role, the pri-
mary and backup modules' current GPI data point files and function
block configurations will be incompatible. The GPI program may run
with errors after either a module switchover or a power cycle.
3BCA014034R0001 Rev. F xi
3BCA014034R0001 Rev. F
Support Services
ABB will provide assistance in the operation and repair of its

products. Requests for sales or application services should be
made to your nearest sales or service office. ABB can also
provide installation, repair and maintenance contract services.
When ordering parts, use nomenclature or part numbers and

part descriptions from equipment manuals. Parts without a
description must be ordered from the nearest sales or service
office. Recommended spare parts lists, including prices are
available through the nearest sales or service office.
ABB has modern training facilities available for training your

personnel. On-site training is also available. Contact your
nearest ABB sales office for specific information and
scheduling.
3BCA014034R0001 Rev. F xiii

3BCA014034R0001 Rev. F
Introduction Section 1
Overview
General Purpose Interface (GPI) provides a facility for ABB con-
troller modules to interface to external devices for the purpose
of data communication. Three GPI communication products
are available. RTU, AB and RTUSLAVE. A user interface
(Microsoft Windows application) is provided for setting up and
maintaining the data communication configuration.
The RTU and AB interface must be configured to establish

data connections between ABB module function blocks and
specific external PLC device data points. RTUSLAVE does not
require a configuration data file.
RTU Represents a Modbus master interface using Modbus RTU

protocol for communicating with Modbus slave devices. Such
slave devices include AEG/Modicon 984 and Quantum PLCs,
GE Fanuc Series-6, Series-5, Series-90 PLCs and many others.
RTUSLAVE Represents a Modbus slave interface using Modbus RTU
protocol for communicating with Modbus master devices.
Such devices are typically Digital Control Systems (DCS).
AB Represents an Allen-Bradley DF1 interface using DF1
protocol for communicating with Allen-Bradley PLCs. Such
PLCs include PLC-2, PLC-3, PLC-5, PLC-5/250 and SLC-5.
The ABB controller modules that support GPI are IMMFP02/12,

IMMFP03, BRC100, BRC200, BRC300, BRC400 and HAC01
modules.
The GPI user interface includes facilities to enter the required

configuration data and install the communication software into
an ABB controller module. Generally, it provides the following:
• Generate and maintain the GPI configuration data for the

point-to-point data connections with PLCs.
• Install the controller module communication software and

configuration data into the target controller module.
• Monitor the performance of the data communication

interface.
3BCA014034R0001 Rev. F 1-1

Overview
Who Should Use This Manual

This manual describes the GPI communication interfaces and
user configuration procedures. It is assumed that the reader is
familiar with the target PLC system and its data point layout
and has a working knowledge of ABB Inc. controller modules.
In implementing a GPI data communication link, it is further
assumed that the reader is familiar with the data link require-
ments and the limitations of an RS232 serial communication
interface.
Dependencies and Constraints

Read Groups
PLC point data is read (polled) by groups. The number of read
groups directly affects the update cycle time to read all points
once. Typically a configuration will contain one or two groups
per PLC referenced. The number of PLCs in an application
(communication link) is typically one or two for a total of two to
four read groups. Point data is written to PLCs by
change-of-state exception (or significant change of state).
Transactions Per Second

The communication command/reply transaction rate may vary
from 3 to 15 transactions per second. Rate transfer times
depend on the amount of data that must be transmitted for the
read group transactions.
Write To PLC Mode

Point data may be written to PLCs using all single point or all
multiple point value transactions. The method is chosen by
the user through the Configuration option Write Command
Protocol. The amount of data transmitted is the same for all
single point value write transactions. For multiple point value
write transactions, the amount of data transmitted is depen-
dent on the size of the multiple point value write groups and
on the data change activity (rate at which significant changes
of state are occurring).
1-2 3BCA014034R0001 Rev. F

Overview
Read vs Write Transactions RTU

In order to share the serial communication link between read
and write operations, the RTU interface, which applies the
Modbus RTU master/slave protocol, performs three single
value write transactions for every read group transaction as
long as there are write transactions (significant changes) out-
standing. The application queues the backlog of digital
changes of state. Analog changes of state are tracked through
internal data table structures and always writes current ana-
log point values to PLCs.
Read vs Write Transaction AB

The AB interface, which applies the peer-to-peer DF1 protocol,
queues digital and analog changes of state. The DF1 protocol
allows it to write multiple single point value changes of state to
the same PLC in the same write transaction. The PLC-3, using
the Bit Write command, is an exception to this. The Bit Write
command does not allow multiple point value changes to be
written in the same command message.
Multiple Point Value Write Groups

Multiple point value write groups are defined by the user inter-
face application. All point values are re-written whenever one
or more point values of a write group change state.
Baud Rates
Baud rates up to 19200 baud are supported on all MFP
controller modules, the BRC controller modules support a
maximum baud rate of 38400. The time required to transmit
data to and from PLCs is directly dependent on the applied
baud rate.
Function Blocks
The target module application function block configuration
time utilization, determined via Composer, should not exceed
100 milliseconds to allow adequate time for the GPI software to
service the serial communication port or ports.
3BCA014034R0001 Rev. F 1-3

Overview
Multiple Point Value Read Groups

The read group transaction commands read consecutive point
values from a PLC data table or file. Read group transactions
may include data of interspersed points that are not refer-
enced in the configuration data. The total number of data
bytes that are read for the read group transactions should be
minimized, i.e. the data bytes that must be read for each group
should include the minimum of point data not referenced in
the configuration.
Data Not Suitable for a General Serial Interface

All of the above must be taken into account when defining a
GPI interface configuration especially when faster throughput
rates are required. On/Off pulse train signals with pulse rates
faster than one pulse every 2 seconds should not be included
in a GPI configuration. Furthermore, rapidly varying analog
values or analog ramping signals should also not be included.
The serial communication of GPI, which sequentially performs
all its scheduled read group transactions with varying impact
from the change of state driven write activity, does not provide
the predictable response required to reliably pass such time
dependent signals.
Minimum Read Points Per PLC

There must be at least one read point (analog or digital) from
each PLC referenced by the configuration. Read operations are
always tried first and are used to determine the communica-
tion status of each PLC. Without good communication status,
no write action to the PLC is allowed to take place.
The ABB controller modules that support GPI have two RS-232
serial ports usually referred to as port 0 (terminal port) and
port 1 (printer port). Both ports can be allocated (by configura-
tion) for PLC data communication. When one of the ports is
not allocated for PLC data communication, the port may be
assigned to log error messages to a RS232 serial terminal or
printer.
1-4 3BCA014034R0001 Rev. F

Overview
Relation to Composer
The GPI user interface shares the Composer semAPI system
interface for connecting and communicating with ABB system
controller modules. Refer to Figure 1-1.
All function blocks required for the GPI communication soft-

ware must be included in the user function block configura-
tion for the target controller module. The function block
configuration must be created, maintained and loaded into the
controller module using Composer.
Diagram of GPI Design
Windows
Composer
Module
Run-Time
Programs
Composer
GPI
Run-Time
User Interface
Communication
Configuration
Data Files
Log Files
Review Files
semAPI
Local Network
Loop
GS001001A
Figure 1-1. GPI Design Diagram
3BCA014034R0001 Rev. F 1-5

Overview
Protocol Sub-Set Supported

RTU
RTU as a Modbus RTU protocol master interface supports the
Modbus protocol functions listed in Table 1-1.
Table 1-1. Modbus Functions Supported by RTU
Function Description
1 Read coil status
2 Read input status
3 Read output register
4 Read input register
5 Force single coil
6 Preset single register
8 Loopback diagnostic test
Diagnostic codes
0 (Loopback Test) to test standby port only.
11 Bus Message Count
12 Bus Communication Error Count
13 Bus Exception Error Count
14 Slave Message Count
15 Slave No Response Count
16 Slave NAK Count
17 Slave Busy Count
18 Bus Character Overrun Count
19 Overrun Error Count
11 Fetch event counter
15 Force multiple coils
16 Preset multiple output registers
1-6 3BCA014034R0001 Rev. F

Overview
RTUSLAVE
RTUSLAVE as a Modbus RTU protocol slave responds only to
the Modbus protocol functions listed in Table 1-2.
Table 1-2. Modbus Functions Supported by RTUSLAVE
Function Description
1 Read coil status.
2 Read input status.
3 Read output register.
4 Read input register.
5 Force single coil.
6 Preset single register.
8 Loopback diagnostic test
Diagnostic codes: 0 Loopback test
Other diagnostic codes are not supported. The
RTUSLAVE software does not maintain this diagnostic
information.
15 Force multiple coils.
16 Preset multiple output registers.
17 Report slave ID (emulates a 584 PLC response).
AB
AB supports the Allen-Bradley DF1 protocol commands listed
in Table 1-3.
Table 1-3. Allen-Bradley DF1 Commands Supported by AB
Command
PLC Medium Description
cmd (fnc)
PLC-2 DH 00 Protected write.
01 Unprotected read.
02 Protected bit write.
05 Unprotected bit write.
08 Unprotected write.
PLC-3 DH 0F (00) Word range write.
0F (01) Word range read.
0F (02) Bit write.
3BCA014034R0001 Rev. F 1-7

Overview
Table 1-3. Allen-Bradley DF1 Commands Supported by AB (continued)
Command
PLC Medium Description
cmd (fnc)
0F (08) Physical write.
PLC-5 DH+ 0F (00) Word range write.
ControlNet 0F (01) Word range read.
DeviceNet 0F (26) Read-modify-write.
PLC-5/250 DH+ 0F (00) Word range write.
ControlNet 0F (01) Word range read.
DeviceNet 0F (26) Read-modify-write.
SLC-500 DH485 0F (A2) Protected typed logical read with
three address fields.
SLC-5/01
SLC-5/02 0F (AA) Protected typed logical write with
SLC-5/04
SLC-5/04 DH+ 0F (A2) Protected typed logical read with
ControlNet 0F (AA) Protected typed logical write with

DeviceNet
Hardware Requirements
Work Station Requirements
GPI requires a minimum of 128MB RAM and 40MB of hard
drive space. The GPI user interface is installed on the Com-
poser workstation therefore it also shares its requirements.
Refer to Hardware Requirements in the Composer: Primary
Interface manual.
Controller Module Requirements

Table 1-4 shows the different module types supported by RTU,
AB and RTUSLAVE and the peripheral hardware needed for
each module type to implement serial communication.
Table 1-4 also shows how the RTU and AB software is supplied
with different maximum point capacities for the different mod-
ule types. The RTUSLAVE is not supplied with a maximum
point limit, however, it is limited by the number of function
1-8 3BCA014034R0001 Rev. F

Overview
blocks required to pass the data between the PLC and ABB
system.
Standard ABB controller module redundancy can be applied

with redundant module cabling to the termination unit. Refer
to the appropriate instruction document listed under
References.
Table 1-4. Controller Module Requirements
Module Product Capacities Peripheral Hardware

IMMFP03 RTU 500 IMMPI01 module
RTUSLAVE 1500
AB 3000
4000
(not relevant to
RTUSLAVE)
Auxiliary I/O ribbon cable
1948720A60
Termination unit NTMP01&
cable NTKU01
or
Termination module NIMP01
& cable NTKU02
BRC100 RTU 500 Processor bus adapter board
BRC200 RTUSLAVE 1500 (PBA board)
BRC300 AB 3000
BRC400 4000
(not relevant to
RTUSLAVE)
Termination unit NTMP01
& cable NTKU01
or
Termination module NIMP01
& cable NTKU02
3BCA014034R0001 Rev. F 1-9

Overview
Table 1-4. Controller Module Requirements (continued)
Module Product Capacities Peripheral Hardware

HAC01 RTU 500 Serial communication termination unit
(licensed for C RTUSLAVE 1500
Program support) AB 3000
4000
(not relevant to
RTUSLAVE)
MFP02 RTU 500 Termination unit NTMP01
MFP12 RTUSLAVE 1500 & cable NTKU01
AB (not relevant to or
RTUSLAVE) Termination module NIMP01
& cable NTKU02
Deliverables
The CD provided includes the following components:
• The user interface software.
• The module run-time software.
• Sample Composer project including templates.
• User manual.
A software license string is required for each module interface.
1 - 10 3BCA014034R0001 Rev. F
Overview
Glossary of Terms
AB - Allen Bradley.
ASCII Mode - Modbus protocol mode, communicates using ASCII
characters.
BRC - Bridge Controller.
Composer - Configuration Toolkit.
Controller - Symphony term, equivalent to INFI-90 Module number.
Control Network - Symphony term, equivalent to INFI-90 Loop number.
Control Unit - Symphony term, equivalent to INFI-90 PCU number.
DCS - Distributed Control System.
DF1 - Allen-Bradley communication protocol.
Download - Write or transfer program files to another device.
FORMAT - Set memory boundaries in a controller module.
GPI - General Purpose Interface.
HAC - Harmony Area Controller (HAC01).
INICI12 - Infi-Net to Computer Interface.
LOAD - Install or transfer program files.
MFP - Multi Function Processor.
MFP02 - Multi Function Processor module type 2.
MFP03 - Multi Function Processor module type 3.
MODBUS - An AEG modicon communication protocol.
NVM - Non Volatile Memory; memory on controller which
retains the module configuration data including C
application and files during a power outage.
RS232 - A standard serial communication protocol.
RS485 - A standard serial communication protocol.
Red Light - The changing of the top LED on a module, from green to
red to indicate a problem.
Run-Time Program - Refers to the program that is executed in the controller
module.
RTU - General Purpose Master Interface for communication
with Modbus protocol slave devices.
RTU Mode - Modbus protocol mode; communicates using hexadeci-
mal values.
RTUSLAVE - General Purpose Slave Interface for communication
with a Modbus protocol master device.
SemAPI - Strategic Enterprise Management Application Program-
ming Interface functions library.
3BCA014034R0001 Rev. F 1 - 11
References
TU - Termination Unit, serial interface between controllers

and external devices.
Upload - Read or transfer program/data files from another
device.
References
Table 1-5. Reference Documents
Document No. Title

WBPEEU1210504E1_1 Instruction – Function Code Application Manual.
(codes 1—174) and
WBPEEU1210504E1_2
(codes 177 — 247)
WBPEEU1230021A0 Instruction – Multi-Function Processor Module (IMMFP02/IMMFP12).
I-E96-203 Instruction – Multi-Function Processor Module (IMMFP03/IMMFP03B).
I-E96-401 Instruction – Multi-Function Processor Interface Module (IMMPIO01).
WBPEEUI230023A1 Instruction – Harmony Area Controllers
WBPEEUI230017A1 Instruction – Harmony Bridge Controller and Process Bus Adapter
(BRC-100 and BRC-200).
3BUA000279R0001 Instruction – Harmony Bridge Controller and Process Bus Adapter
(BRC-300 and BRC-400).
WBPEEU1260039A2 Instruction – Multi-Function Processor Termination Unit (NTMP01).
I-E96-428 Instruction – Multi-Function Processor Termination Module (NIMP01/
02).
3BUA000271R0001 Introduction and Installation – Composer 4.3
Document Conventions
This document uses standard text conventions to represent
keys, display items and user data inputs:
Display item Any item displayed on a screen appears as italic text. Example:
Running
User data input Bold - Identifies any part of a command line that is not
optional or variable and must be entered exactly as shown.
Italic - Identifies a variable parameter entered in a command

line.
1 - 12 3BCA014034R0001 Rev. F
[ ] - Indicates an optional parameter; text within the brackets

follows the previously described conventions.
Example:
CUP [port] [baud] [file_name.CSP]SPECIAL KEYS - Identifies a

specific key that is not alphabetic, numeric or punctua-
tion. Examples:
Press ENTER.
Press ESC V M. (Press and release each key in sequence.)
Press CTRL-ALT-SHIFT-DEL. (Press all keys in sequence with-
out releasing any one key until you have pressed them all.)
File names Name - Indicates a file or directory name. Example:
file1.exe
c:\new
Revision variable A ? indicates a value that may change depending on the ver-
sion of an item. Example:
Part number: 1234567?0

Part number: 1234567??
3BCA014034R0001 Rev. F 1 - 13
1 - 14 3BCA014034R0001 Rev. F
Getting Started Section 2
The CD shipped includes the user interface program files, a

copy of this manual and the controller module run-time soft-
ware. Also included in the shipment is a form listing the
license strings for the purchased controller module run-time
software.
Installing the User Interface Software

NOTE: If Symphony GPI 2.6 is currently installed on the engineering worksta-
tion then installing Symphony GPI 3.0 will not interfere with the previous ver-
sion.
To install the user interface software, place the CD provided

into the CD-ROM drive. Shutdown all applications currently
running to avoid conflicts.
1. Select Start > Run
2. Click the Browse button and select Setup.exe on the

CD-ROM drive then click the Open button.
3. Click the OK button.
The window shown in Figure 2-1 and Figure 2-2 is displayed

first.
4. Read and complete the Install dialogue commands. The

software will be loaded and the wizard screen will indicate
that the software installation is complete.
3BCA014034R0001 Rev. F 2-1

Installing the User Interface Software
Figure 2-1. GPI Version Information
Figure 2-2. Welcome Window
2-2 3BCA014034R0001 Rev. F

Product Licensing
Product Licensing
The Product License string, issued to ABB Inc. customers
separately on paper, must be entered via the User Interface
Main Menu licensing option. Refer to Figure 2-3.
Figure 2-3. Module Licensing Screen
Initially the Licensing screen will not have any licenses

displayed. One license string is provided for each GPI product
purchased. The license string identifies the interface, type of
controller and maximum number of tags available. Refer to
Module Licensing in Section 4 for more details.
Controller Module Installation

The controller modules that support GPI and the required
peripheral hardware are listed under Controller Module
Requirements in Section 1. For general installation
instructions refer to the documents listed under References in
Section 1.
For quick reference, the switch settings for the particular

controller modules are shown in Dipswitch Settings.
3BCA014034R0001 Rev. F 2-3

Dipswitch Settings
IMMFP02/IMMFP12
The IMMFP02 and IMMFP12 controller modules have two
8-pole dip-switch units labeled SW1 and SW2. Before install-
ing the GPI program and configuration, the controller module
should be hardware initialized using the special operations
applied with SW2. Refer to the Controller Module Installa-
tion section of the Controller’s Instruction document. The
instruction documents are listed under References in
Section 1. Hardware initializing a IMMFP02 or IMMFP12 mod-
ule is a two step procedure. For each step the module must be
pulled out of the rack, the special operation switches must be
set and then the module must be inserted into the rack again.
After each step the module will red light with the group of eight
LEDs indicating the specified code.
Step 1 Open SW2 poles 1 and 7, LEDs lit 1, 2, 3, 4, 5 and 6.
Step 2 Open SW2 poles 1 and 6, LEDs lit 1, 2, 3, 4, 5 and 6.
After hardware initialization, close all poles of SW2. Next the

run-time parameters must be set into SW1 and SW2. An
example setting is shown in Tables 2-1 and 2-2. Select the
desired module bus address for the controller module in poles
4-8 of SW1 and be sure to select the module bus speed with
pole 3 of SW1 (1 MHz or 83.3 KHz) to match other modules in
the module bus rack.
Table 2-1. IMMFP02/IMMFP12 Dipswitch Unit SW1
SW1 ON (0) 1 2 3 4 5 6 7 8
Pole Setting OFF (1)
1 ON Normal (run-time) position.
OFF Position to invoke diagnostics using SW2.
2 ON Reserved. Do not change setting.
3 ON Controlway (1 MHz).
OFF Module bus (83.3 KHz).
4-8 1-31 Controlway or module bus address (address 5 shown).
2-4 3BCA014034R0001 Rev. F

Select the appropriate module redundancy settings for the

application in SW2.
Table 2-2. IMMFP02/IMMFP12 Dipswitch Unit SW2
SW2 Redundancy Switch Selections

Poles 1 2 3 4 5 6 7 8
Non-Redundant N/A ON (0)
OFF (1)
Redundant Primary ON (0)
Online OFF (1)
Configuration Redundant ON (0)
Disabled
OFF (1)
Online OFF (1)
Enabled
OFF (1)
NOTE: When module redundancy is applied, specification S3 of the Extended

Executive function block (function code 90 at block 20) must be set to module
redundancy. For details, refer to documentation in Section 1, the Function
Code Application Manuals.
IMMFP03/IMMPI01
The IMMFP03 module must be installed along with a IMMPI01
Multi-Function Processor Interface module. The IMMFP03 and
IMMPI01 must be interconnected by ribbon cable (P/N
1948720A60). The cable to the termination (NTMP01 or
NIMP01), connects to the IMMPI01. Refer to the instructions
listed under References in Section 1.
The IMMFP03 controller module has four 8-pole dip-switch

units labeled UUB0 (SW4), UMB1 (SW1), LMB2 (SW2) and
LLB3 (SW3). Before installing the GPI program and configura-
tion, the controller module must be hardware initialized using
the special operations applied with UMB1 (SW1). Refer to Con-
troller Module Installation section of the Controller’s
Instruction document. The instructions are listed under Refer-
ences in Section 1. It is a three step procedure. The third step
sets the IMMFP03 module up for the IMMPI01 interface. For
each step the module must be pulled out of the rack, the spe-
cial operation switches must be set and then the module must
3BCA014034R0001 Rev. F 2-5

be inserted into the rack again. After each step the module will
red light with the group of eight LEDs indicating the specified
code.
Step 1 Open UMB1 poles 1 and 7 LEDs lit 1, 2, 3, 4, 5 and 6.
Step 2 Open UMB1 poles 1 and 6 LEDs lit 1, 2, 3, 4, 5 and 6.
Step 3 Open UMB1 poles 1, 6, 7 and 8 LEDs lit 1, 2, 3, 4, 5 and 6.
After hardware initialization, close all poles of UMB1 (SW1).

Next the run-time parameters must be set into UUB0 (SW4)
and UMB1 (SW1). An example setting is shown in Tables 2-3
and 2-4. Select the desired module bus address for the con-
troller module in poles 4-8 of UUB0 and be sure to select the
Module Bus speed with pole 3 of UUB0 (1 MHz or 83.3 KHz) to
match other modules in the module bus rack.
Table 2-3. IMMFP03 Dipswitch Unit UUB0 (SW4)
UUB0 (SW4) ON (0) 1 2 3 4 5 6 7 8

1 ON Normal (run) position.
OFF Position to invoke diagnostics using SW1 (UMB1).
Table 2-4. IMMFP03 Dipswitch Unit UMB1 (SW1)
UMB1 (SW1) Redundancy Switch Selections

Poles 1 2 3 4 5 6 7 8
OFF (1)
Online OFF (1)
Disabled
OFF (1)
2-6 3BCA014034R0001 Rev. F

Table 2-4. IMMFP03 Dipswitch Unit UMB1 (SW1) (continued)
UMB1 (SW1) Redundancy Switch Selections

Poles 1 2 3 4 5 6 7 8
Online OFF (1)
Enabled
OFF (1)

Executive function block (function code 90 at block 20) must be set to Mod-
ule Redundancy. For details, refer to documentation in Section 1, the
Function Code Application Manuals.
BRC100/BRC200/BRC300/BRC400
All the BRC controller modules have four 8-pole dip-switch
units labeled SW5, SW2, SW3 and SW4. Before installing the
GPI program and configuration, the controller module must be
hardware initialized using the special operations applied with
SW2. Refer to Controller Module Installation section of the
Controller’s Instruction document. The instructions are listed
under References in Section 1. It is a two step procedure. For
each step the module must be pulled out of the rack, the spe-
cial operation switches must be set and then the module must
be inserted into the rack again. After each step the module will
red light with the group of eight LEDs indicating the specified
code.
Step 1 Open SW2 poles 1 and 7 LEDs lit 1, 2, 3, 4, 5 and 6.
Step 2 Open SW2 poles 1 and 6 LEDs lit 1, 2, 3, 4, 5 and 6.
After hardware initialization, close all poles of SW2. Next the

run-time parameters must be set into SW5 and SW2. An
example setting is shown in Tables 2-5 and 2-6. Select the
desired module bus address for the controller module in poles
4-8 of SW5 and be sure to select the Module Bus Speed with
pole 3 of SW5 (1 MHz or 83.3 KHz) to match other modules in
the module bus rack.
3BCA014034R0001 Rev. F 2-7

Table 2-5. BRC100/200/300/400 Dipswitch Unit SW5
SW5 ON (0) 1 2 3 4 5 6 7 8
1 ON Normal (run) position.
OFF Position to invoke diagnostics using SW2.
Table 2-6. BRC100/200/300/400 Dipswitch Unit SW2
SW2 Redundancy Switch Selections

Poles 1 2 3 4 5 6 7 8
OFF (1)
Online OFF (1)
Disabled
OFF (1)
Online OFF (1)
Enabled
OFF (1)

Executive function block (function code 90 at block 20) must be set to
Module Redundancy. For details, refer to documentation in Section 1,
the Function Code Application Manuals.
HAC01 Initialization
Follow the instruction for the HAC01 controller module. The
instruction document is listed under References in Section 1.
2-8 3BCA014034R0001 Rev. F

Serial Interface Installation

The serial communication connection will generally consist of
these major hardware components.
• The cable (NKTU01) between the module and the termina-

tion unit
• The termination unit (NTMP01) or termination module
(NIMP01).
• The serial communication cable.
• The external system (PLC system) port connection.
• For BRC modules the PBA module between the module
NKTU01 cable.
Figure 2-4. Basic Serial Connection
The maximum length for the serial RS-232 cable is dependent

on the baud rate and the environment (amount of electromag-
netic interference) in the vicinity of the cable. Depending also
on the capacitance in the cable, the generally specified maxi-
mum length of the cable at 9600 baud is 50 feet. The maxi-
mum allowable length increases with decreasing baud rate.
Instead of a simple serial RS-232 cable, the connection may

include interposing devices like short haul or driver modems,
telephone modems or radio modems to increase the distance
and /or provide electrical isolation between the ABB and PLC
systems.
The modem inter-connection requirements depend on the

modem type, make and model. Always refer to the modem doc-
umentation for details regarding installation and operation of
the modems. The RS-232 serial cable requirements and the
termination unit jumper settings (J1/J2) are now indepen-
dent of the PLC system communication port characteristics
but must meet the requirements of the modem RS-232 port.
Refer to Redundancy.
3BCA014034R0001 Rev. F 2-9

Figure 2-5. Serial Connection with Interposing Devices
Redundancy
To set the modules as a typical redundant pair the following
must be done:
• Both modules must be at the same firmware level.
• Both modules must be set to the same module address.
• a dipshunt must be placed at the back of the MMU

between the two slots the module will be placed.
• termination cables must be connected to the termination

board as shown in Figure 2-6, 2-8 and 2-9.
• For BRC controllers a PBA unit is required between the

module and the termination cable. A CNET cable must be
attached to both the PBA's. Refer to the particular BRC's
manual for further details.
• A dipswitch (refer to the controller's manual for the specific

switchbank) must be set on in the primary controller and
off in the redundant controller.
• Whether the two serial ports are to be redundant or not

depends on configuration settings within GPI and if the
devices to which it connects support redundancy.
Figure 2-7 illustrates the hardware configuration which

includes redundancy of the TU. A IKTMR01 cable is required
to connect the two termination units together.
2 - 10 3BCA014034R0001 Rev. F
BRC300 BRC300
PBA PBA
NKUT01 NKUT01
P1 P2
Termination Unit
(NTMP01)
Terminal Printer
(P6) (P5)
RS232 RS232
Foreign Foreign
Device Device
(Primary) (Redundant)
Figure 2-6. Typical redundant hardware configuration.
3BCA014034R0001 Rev. F 2 - 11
BRC300 BRC300
PBA PBA
IKTMR01
NKUT01 NKUT01
P1 P2 P1 P2
Termination Unit Termination Unit

(NTMP01) (NTMP01)
Terminal Printer Terminal Printer
(P6) (P5) (P6) (P5)
RS232 RS232
Foreign Foreign
Device Device
(Primary) (Redundant)
Figure 2-7. Total redundant hardware configuration
2 - 12 3BCA014034R0001 Rev. F
Setting Up the Controller Module Termination

Both the termination unit, NTMP01, and the termination
module, NIMP01, can be used with the IMMFP02/IMMFP12,
IMMP03/IMMPI01 and the BRC100, BRC 200, BRC300 and
BRC 400 controller modules. The NTMP01 and NIMP01
termination circuit boards have a number of jumpers posi-
tioned as shown in Figures 2-8 and Figure 2-9 respectively.
STATION BRC
COM. B ACTIVE LED
NTMP01
NKTU01 P2
CABLE
J2 P5
J4
TERMINAL
+24 V J16 J5
PORT
J6
J17 CR1 J7
RS-485
J12
FUSE F1 E2 P4
CHASSIS SPARE
GROUND E1 P7 P8
COM
P3 J1
E3
CR2
J14 PRINTER
J3 PORT
J15 J18 J9
J8
J10
NKTU01 J11
CABLE P6
P1 SPARE
STATION BRC
COM. A ACTIVE LED
GS001004
Figure 2-8. NTMP01 Termination Unit Circuit Board
The NTMP01 termination unit and NIMP01 termination mod-

ule circuit boards exist in two versions referred to in this man-
ual as the old and the new version. NTMP01 circuit board
assembles D1 and later have the new circuit board layout.
NIMP01 assembles C1 and later have the new layout. The old
and new circuit boards differ in the layout of jumper sets J1
and J2 which serve to adapt the ports characteristics to the
requirements of the device being connected to. This difference
is depicted in Figures 2-14 and 2-15.
3BCA014034R0001 Rev. F 2 - 13
J2 SYSTEM COMMON
CR2 CHASSIS GROUND
J19
J6
P5 +24 VDC
SYSTEM COMMON
J2
J5
J7 J19 P5 TERMINAL
+24 VDC PORT
J6
J16 J1 (RS-232-C)
J20 J5
J17 J7 TERMINAL PORT
J14 J8 PRINTER PORT
J16 J1 P6 (RS-232-C)
J9 J20
J15 J17 J10 J8
(RS-232-C)
P3 J14 J13 J9 P6 PRINTER PORT
J15
J10
(RS-232-C)
P3 J11 J13 RS-485 PORT
J18 P7
SPARE
J11
J18 P7 RS-485 PORT
P8
J12
SPARE
P1 P8 DIGITAL INPUT
P8
J12 P1 P4P8 DIGITAL INPUT
P11 P4 LINK B SERIAL LINK
FOR
SERIAL LINK
FUSE F1 P11 LINKAB STATIONS
LINK FOR
FUSE
NIMP02 F1
CABLES LINK A STATIONS
ATTACH HERE
NIMP02 CABLES P2
ATTACH HERE P2 GS001005
GS001005
Figure 2-9. NIMP01 Termination Module Circuit Board
The Serial Communication Termination unit is used only with

the HAC01 controller module and plugs into the HAC docking
station.
All jumpers except J1 and J2 must be set as indicated in

Figure 2-11 for a NTMP01, Figure 2-12 for a NIMP01 or Figure
2-13 for a HAC Serial Communication Termination unit.
Jumpers J1 and/or J2 must be set to reflect the cable used
and PLC system communication port requirements.
The cable must have the appropriate mating connectors for

both the termination unit end and the PLC system port. The
NTMP01 has DB-25 female connectors for its RS-232 ports.
The NIMP01 has DB-9 female connectors. The HAC Serial

Communication unit has DB-9 female connectors.
Depending on which termination unit is used and what the

PLC system communication port characteristics are, one of
eight standard RS-232 cables may be installed for the interface
The standard cable configurations are described in RS-232

Cable Configurations in Appendix D.
2 - 14 3BCA014034R0001 Rev. F
Figure 2-10. Communication TU Serial Port Jumpers
The NTMP01 termination unit and NIMP01 termination mod-

ule each have two ports labeled terminal and printer. The
jumpers J1 serve the printer port while the jumpers J2 serve
3BCA014034R0001 Rev. F 2 - 15
Table 2-7. Standard RS-232 Serial Cables
PLC System
Termination ABB
Standard Cable Communication
Unit Part Number
Port Connector
NTMP01 DB-25 Male to DB-25 Female DB-25 Male L700550A1
DB-25 Male to DB-25 Male DB-25 Female L700550A2
DB-25 Male to DB-9 Female DB-9 Male L700579A1
DB-25 Male to DB-9 Male 1 DB-9 Female L700579M12
NIMP01 DB-9 Male to DB-25 Female DB-25 Male L700579E5
DB-9 Male to DB-25 Male 1 DB-25 Female L700579M12
DB-9 Male to DB-9 Female DB-9 Male L700579E4
DB-9 Male to DB-9 Male DB-9 Female L700579K10
Note 1 This cable shows twice in the table.
the terminal port. These two jumper sets allow a user to adapt
each port to most standard RS-232 port requirements.
The HAC Serial Communication unit has two ports labeled

RS232A and RS232B. The RS232A port is equivalent to the
printer port of the NTMP01 and the RS232B port is equivalent
to the terminal port of the NTMP01.
Figures 2-11 and 2-12 show the jumper pairs for the miscella-
neous communication signals for the NTMP01 and NIMP01
respectively. The lower numbered jumper is associated with
the printer port.
Example In Figure 2-11 jumpers J4/J3, J4 is associated with the terminal port and J3
with the printer port.
RS-232 Communication
RS-232 communication generally includes the signals listed in
Table 2-8 and requires a cable conductor (wire) for each.
Table 2-8. Standard RS-232 Signals
Signal Pin-Out Device Type

Description
DB25 DB9 DTE DCE
Gnd 1 - -
TXD 2 3 Data transmit. Send Receive
RXD 3 2 Data receive. Receive Send
2 - 16 3BCA014034R0001 Rev. F
Table 2-8. Standard RS-232 Signals
RTS 4 7 Request to send. Send Receive

CTS 5 8 Clear to send. Receive Send
DSR 6 6 Data set ready. Receive Send
SC 7 5 Signal common. - -
DCD 8 1 Data carrier detect. Receive Send
DTR 20 4 Data terminal ready. Send Receive
Not all RS-232 interfaces utilize all of the signals. In fact, most
point-to-point connections do not use the DSR, DCD and DTR
signals which for data communications serve mainly to
manage interposing devices like telephones and radio
modems. In fact, the ABB controller modules cannot manipu-
late these signals for external devices and only provides jump-
ers to permanently enable the signals with pull up circuits to
+12 Volts DC. Refer to Figures 2-11 and 2-12.
The RTS and CTS signals normally provide flow control to pre-
vent overflow of the serial input buffer associated with each
port. The CTS signal (DTE port mode or RTS in DCE mode)
must be enabled (high) to allow the ABB controller module to
transmit. The jumper sets J1 and J2 serve to channel these
signals to the port connector when these signals are required.
Where these signals are not needed or desired for the PLC sys-
tem communications, the RTS signal at the ABB controller end
must be looped back to its CTS signal line if the PLC system
port does not enable its CTS signal output. Figures 2-14 and
2-15 show the J1 and J2 jumper arrangement. Refer to
Example J1/J2 Jumper Settings which provides a more
detailed description for setting these jumpers.
The minimum requirement for two way communication

includes just the TXD, the RXD and the SC signals. When this
minimum is applied, the RTS/CTS signals must be looped
back as mentioned in the preceding paragraph to allow the
ABB controller module to transmit.
The GND signal is the safety ground which for many PLC sys-
tems connects to the AC power shared ground bus. Where this
3BCA014034R0001 Rev. F 2 - 17
is the case, the GND signal should be left disconnected at the

termination unit port. Refer to Figure 2-11, jumper J4/J3.
NOTE: Refer to ABB document WBPEEUI200505A0, Site Planning Guide-

lines for information relating to AC power and grounding.
Figure 2-11. NTMP01 Miscellaneous Jumpers
RS485 Communication
GPI applications do not use the RS485 port provided on the
termination unit, as it is not optically isolated as the two
RS232 ports are. Instead an RS232 to RS485 converter must
be used to connect to the selected RS232 port of the termina-
tion unit.
2 - 18 3BCA014034R0001 Rev. F
Figure 2-12. NIMP01 Miscellaneous Jumpers
3BCA014034R0001 Rev. F 2 - 19
Figure 2-13. HAC TU Miscellaneous Jumpers
In Figure 2-13, the lower jumper numbers of pairs (e.g. J7/J8)

serve the Channel A RS-232 port and the higher numbers
serve the Channel B RS-232 port.
2 - 20 3BCA014034R0001 Rev. F
Figure 2-14. NTMP01 Old and New Jumper Sets
DCE/DTE Handshaking
Jumper sets J1/J2 serve to channel the controller module
TXD, RXD, RTS and CTS signals to the DB connector in order
to meet an external device’s RS232 port characteristics. One
main characteristic of a RS-232 port is its designation as
either a DTE (Data Terminal) or a DCE (Data Communication)
port. Generally, to connect to an external DTE port, the termi-
nation port must be set up as DCE. Conversely, to connect to
an external DCE port, the termination port must be set up as
DTE.
Placing jumpers vertically between J1/J2 jumper pins 3 and 5,

4 and 6, 7 and 9, and 8 and 10 of the new NTMP01, NIMP01 or
HAC termination sets the port up as DCE. Placing jumpers
horizontally between J1/J2 jumper pins 3 and 4, 5 and 6, 7
and 8, and 9 and 10 of the new NTMP01, NIMP01 or HAC ter-
mination unit sets the port up as DTE.
3BCA014034R0001 Rev. F 2 - 21
On the old NTMP01 or NIMP01, jumper J1/J2 pins 1 and 2, 8

and 7, 3 and 4, and 6 and 5 for DCE and jumper pins 1 and 8,
2 and 7, 3 and 6 and 4 and 5 for DTE. Figure 2-17 depicts
general jumper settings for the NTMP01 port in DCE mode.
Figure 2-18 shows the jumper settings for the NIMP01 port set
up for DTE mode.
Figure 2-15. NIMP01 Old and New Jumper Sets
The jumper settings of Figure 2-17 and 2-18 apply when the
external port provides the RTS and CTS signals to the control-
ler module port.
2 - 22 3BCA014034R0001 Rev. F
Figure 2-16. HAC TU Jumper Sets
3BCA014034R0001 Rev. F 2 - 23
Figure 2-17. NTMP01 Jumper Sets for DCE Handshaking
2 - 24 3BCA014034R0001 Rev. F
Figure 2-18. NIMP01 Jumper Sets for DTE Handshaking
3BCA014034R0001 Rev. F 2 - 25
Example J1/J2 Jumper Settings
Figure 2-19. NTMP01 Jumper Sets for Allen-Bradley 1771-KG with Cable 1771-CG
The J1/J2 jumper settings shown in Figure 2-19 can be used

to connect a NTMP01 port to an Allen-Bradley 1771-KG mod-
ule using the Allen-Bradley standard 1771-CG cable. This
cable crosses the TXD and RXD lines and has RTS/CTS pin
loopback at each end.
The same interface, NTMP01 port to an Allen-Bradley 1771-KG

module, can also be made using a custom cable (Figure 2-21)
and the jumper settings shown in Figure 2-20.
2 - 26 3BCA014034R0001 Rev. F
Figure 2-20. NTMP01 Jumper Sets for Allen-Bradley 1771-KG with Custom Cable
3BCA014034R0001 Rev. F 2 - 27
Figure 2-21. Custom Cable for Allen-Bradley 1771-KG RS-232 Interface
To provide the RTS/CTS loopback on the old NTMP01 termi-

nation unit shown in Figure 2-20, the crossed jumpers
between pins 3 and 5 and between 4 and 6 must be wire
wrapped, soldered, or be made with special wire jumpers.
Figure 2-22 shows a NTMP01 J1/J2 setting that can be used

to connect to an Allen-Bradley 1770-KF2 using standard cable
P/N L700550A2.
Figure 2-23 shows a NIMP01 J1/J2 setting that can be used to

connect to a Modicon 984/382 PLC Modbus port using stan-
dard cable P/N L700579K10. To provide the RTS/CTS loop-
back on the old NIMP01 termination unit as shown, the
crossed jumpers between pins 3 and 5 and between 4 and 6
must be wire wrapped, soldered, or be made with special wire
jumpers.
3BCA014034R0001 Rev. F
Figure 2-22. NTMP01 Jumper Sets for Allen-Bradley 1770-KF2 with Standard Cable
3BCA014034R0001 Rev. F 2 - 29
Figure 2-23. NIMP01 Jumper Sets for Modicon 984/385
2 - 30 3BCA014034R0001 Rev. F
Allen-Bradley Data Highway Interface Module Settings

Allen-Bradley provides a number of data highway interface
modules. These modules typically have switches that must be
set to obtain the desired RS-232 port characteristics. For a
GPI AB connection to a data highway interface module, the
data highway interface module RS-232 port must be set as
shown in Table 2-9.
Table 2-9. Required Data Highway Interface Module Settings
Parameter Required Setting

RS-232 Baud Rate As required up to 19200
# of Data Bits 8
# of Stop Bits 1
Parity None
Handshaking Ignore *
DF1 Mode Full Duplex
Error Checking BCC
Embedded Responses No
Accept duplicate messages Yes
Execute diagnostic commands Yes
* If interposing line driver modems are applied and the modems are signal powered, the Hand-
shaking must be enabled on the Data Highway Interface module for this purpose.
For details about setting the data highway interface module

switches, always refer to the associated Allen-Bradley sup-
plied documentation.
3BCA014034R0001 Rev. F 2 - 31
2 - 32 3BCA014034R0001 Rev. F
General Configuration Section 3
Information
Figure 3-1 generally depicts the GPI communication interface
hardware.
Figure 3-1. GPI Hardware Diagram
3BCA014034R0001 Rev. F 3-1

Host Controller Modules

The different controller modules support a GPI communication
interface with the following limitations:
IMMFP02/ GPI RTU and AB for 500 and 1500 point

IMMFP12 capacity. RTUSLAVE.
IMMFP03 GPI RTU and AB for all capacities; 500, 1500,

3000 and 4000 points. RTUSLAVE.
BRC100/ GPI RTU and AB for all capacities; 500, 1500,

200/300/ 3000 and 4000 points. RTUSLAVE.
400
HAC01 GPI RTU and AB for all capacities; 500, 1500,

3000 and 4000 points. RTUSLAVE.
NOTE: RTUSLAVE is not limited on point capacity. It requires no configuration

data file. It is instead limited by the host module memory capacity and the
installed function blocks for responding to data addressing requests received
from the connected master device. The person programming the master device
must know the RTUSLAVE module function block assignments in order to
address its data via the Modbus interface.
RTUSLAVE and Modbus RTU Addresses

RTUSLAVE responds to Modbus RTU command messages that
it receives on the controller's termination units active serial
port. It uses the Modbus address of the command messages
directly or with a globally applied bias (refer to S7 of
Table 3-19) as a block number reference.
When the RTUSLAVE receives a command message to read or

write digital data (Modbus commands 01,02, 05, or 15) it
addresses the block number referenced as a Modbus address
that can output or accept digital (Boolean/coil) data.
In the same way if the RTUSLAVE receives a command mes-

sage to read or write integer data (Modbus commands
03,04,06,16) it addresses the block number referenced as a
Modbus address that can output or accept integer (Register)
data.
3-2 3BCA014034R0001 Rev. F

The addressing for floating point data or long integers is more

complicated as the relationship between the Modbus register
addresses and the function code block numbers is not direct
(Modbus commands 03,04,16). For a floating point number
value to be passed between the Modbus Master and Slave two
integers (or Registers) are required. In order to define the
addresses of the function blocks to provide data to and from
the Modbus master it must be determined the method used to
send and receive the data. The two methods are single value or
multiple value data transfer.
Single Value Data Transfer

The Modbus command to read one function block value speci-
fies the block address of the function block and the number of
registers as two. In the controller the function blocks can be
placed at any address. The Modbus command to write to one
function block specifies the block address of the function block
and the number of registers as two. In the controller the func-
tion block can be placed at any address.
Multiple Value Data Transfer

The Modbus command to read a group of function blocks
specifies the block address of first function block and the
number of registers times two. In the controller the function
blocks must be placed at consecutive addresses. The Modbus
command to write a group function block specifies block
addresses of the first function block and the number of regis-
ters times two. In the controller the function blocks must be
placed at consecutive addresses.
NOTE: The RTUSlave must be configured (refer to S6 of Table 3-18) to handle

all the registers as 16 bit integers, floating points or long intergers. These three
types cannot all be supported at the same time.
Point Types
RTU and AB support four different point types that may be
established as connections between controller module function
blocks and PLC data points. In addition, the RTU allows a user
to read a number of status registers defined for AEG Modicon
PLCs. Tables 3-1 and 3-2 list the point types for GPI RTU and
AB.
3BCA014034R0001 Rev. F 3-3

Table 3-1. RTU Point Types
GPI
Description
Point Type
DOP Reads one PLC digital output or digital input into one controller module func-
tion code 45 (Digital Exception Report) or 138 (C or Basic Boolean Output with
Quality) block.
DIP Writes one boolean output function block value to one PLC digital input.
AOP1 Reads one PLC output register or input register into one controller module
function code 30 (Analog Exception Report) or 137 (C or Basic Real Output
with Quality) block.
AIP1 Writes one real function block value to one PLC input register.
Status Register Reads one PLC status counter value into one controller module function code
30 (Analog Exception Report) or 137 (C or Basic Real Output with Quality)
block. The status data is read with Modbus function 08 (loopback test) using
one of diagnostic codes 11 through 19 to select the status counter.
Communication Reads the PLC Communication Event Counter value into one controller mod-
Event Counter ule function code 30 (Analog Exception Report) or 137 (C or Basic Real Output
with Quality) block. The event counter is read with Modbus function 11.
NOTE: GPI point types AOP and AIP may be set up to reference IEEE float or
32-bit long PLC data stored in two consecutive registers. For this purpose, the
point configuration includes a PLC data type field that must be set to S (16-bit
short integer), FHL/FLH (IEEE Float) or LHL/LLH (32-bit long integer) to indi-
cate the type of data stored at the register referenced. HL (High Low) in FHL or
LHL or LH (Low High) in FLH or LLH defines the order in which the two regis-
ters in the register table contain the 32-bit value.
Table 3-2. AB Point Types
GPI
Description
Point Type
DO1 Reads one PLC file or physical memory bit (digital) value into one controller
module function code 45 (Digital Exception Report) or 138 (C or Basic Bool-
ean Output with Quality) block.
DI1 Writes one boolean function block value to one PLC file or physical memory
bit.
AO2 Reads one PLC file or physical memory 16-bit word (analog) value into one
controller module function code 30 (Analog Exception Report) or 137 (C or
Basic Real Output with Quality) block.
AI2 Writes one real function block value to one PLC file or physical memory 16-bit
word.
3-4 3BCA014034R0001 Rev. F

Communication Overview
NOTES:
1. AB references digital PLC data for DO and DI points by word and bit num-
ber. The word number represents a file offset – from the beginning of the file
(word 0) or physical memory address while the bit number specifies the bit
position within the 16-bit word (0 – 15).
2. GPI point types AO and AI may be set up to reference IEEE Float or 32-bit
Long PLC data stored in two consecutive words of an integer (N) type file. File
type must always be specified for AB for the purpose of data translation even
though PLC-2 does not support files. For this purpose, the point configuration
PLC Data Type field that must be set to S (16-bit short integer), FHL/FLH (IEEE
Float) or LHL/LLH (32-bit long integer) to indicate the type of data stored at the
word referenced. HL (High – Low) in FHL or LHL or LH (Low High) in FLH or LLH
defines the order in which the two PLC data words contain the 32-bit value.
GPI RTU and PLCs that Support Modbus RTU
PLCs are produced by many manufacturers. While each man-
ufacturer’s PLC data is organized uniquely for its local require-
ments, many have adopted the Modbus RTU protocol to
communicate data to external systems. Some PLCs provide
optional Modbus RTU communication adapter modules while
other PLCs have built-in Modbus RTU support via local
RS-232 ports. The Modbus protocol was originally developed
by AEG Modicon for their inter-PLC communication so that
the protocol functions (commands) naturally address the AEG
Modicon PLC data tables. All other manufacturer Modbus RTU
interfaces provide mapping of Modbus addressing to their PLC
data. In the RTU configuration, all PLC data points must be
referenced by their Modbus RTU equivalent addresses, even
for AEG Modicon PLCs.
Table 3-3 shows the AEG Modicon PLC mapping to Modbus

RTU addresses. Notice that the AEG Modicon address shows
six digits reflecting the newer Quantum PLC’s larger data
tables. Notice also that the GPI RTU can address only the
lower 65535 data points of each table. The Modbus RTU proto-
col query message address field width of two hexadecimal
bytes (16 bits) limits the range to 0x0000 – 0xFFFF or 0 –
65535 decimal. GPI limits the range further to 0 – 6553.
3BCA014034R0001 Rev. F 3-5

Table 3-3. AEG Modicon Address Mapping to Modbus RTU
PLC Data AEG Modicon Modbus RTU

Digital Outputs 000001 – 099999 0 – 65534 (function 01)
Digital Inputs 100001 – 199999 0 – 65534 (function 02)
Input Registers 300001 – 399999 0 – 65534 (function 04)
Output Registers 400001 – 499999 0 – 65534 (function 03)
Other manufacturer PLCs like GE Fanuc and Square-D have

more complex data mapping schemes. For all manufacturer
PLCs, the Modbus RTU addresses must be known to enter the
data point connections into the RTU configuration.
Table 3-4 lists a number of Modbus RTU communication

adapter modules that have been applied in GPI RTU applica-
tions.
Table 3-4. Modbus RTU Communication Adapter Modules
Manufacturer PLC Model Adapter Module

GE Fanuc Series-5 CCM
Series-6 CCM3
Series 90 CPM1
CMM
Square-D SY/MAX Processors CRM-530
Siemens S5 CP524, CP5252
Note:
1. The CPM communication adapter module must be programmed by GE Fanuc to process Modbus RTU protocol messages.
2. The CP524 and CP525 modules serve as a sort of mail box via which a host (GPI RTU) and the Siemens S5 PLC pass data.
The modules and the S5 PLC must be programmed for this purpose.
The Modbus RTU protocol functions that are supported by GPI

RTU each uniquely address one of four PLC data tables. GPI
RTU refers to the tables using the mnemonics DO, DI, AO and
AI. Table 3-5 shows how the PLC data tables are referenced by
both the Modbus RTU protocol and for GPI RTU configura-
tions.
3-6 3BCA014034R0001 Rev. F

Table 3-5. GPI RTU, PLC Table References
PLC Modbus RTU PLC GPI RTU GPI RTU

Data Table Function Data Type Reference Point Types
Digital Outputs 01, 05, 15 Boolean or Bit data Output Table (DO) DOP and DIP
Digital Inputs 02 Boolean or Bit data Input Table (DI) DOP
Output Registers 03, 06, 16 16-bit integer Output Registers (AO) AOP and AIP
Input Registers 04 16-bit integer Input Registers (AI) AOP
GPI AB PLC Data Addressing

GPI AB is typically applied to interface to Allen-Bradley PLCs,
namely PLC-2, PLC-3, PLC-5, PLC-5/250 and the SLC500. The
interface is usually established via a data highway interface
module; Data Highway (DH), Data Highway Plus (DH+), Data
Highway II (DH2) and Data Highway 485 (DH485). DF1 proto-
col interfaces can be established via ControlNet and DeviceNet,
Table 3-6 lists a number of Allen-Bradley communication
adapter modules and the PLC types that can be connected as
local nodes on the network.
Table 3-6. Allen-Bradley Communication Adapter Modules
Communication DF1 Protocol

Network PLC Model
Adapter Module Command (Function)
DH 1771-KE/KF PLC-2 00 Protected Write
01 Unprotected Read
02 Protected Bit Write
05 Unprotected Bit Write
08 Unprotected Write
PLC-3 0F(00) Word Range Write
0F(01) Word Range Read
0F(02) Bit Write (single word)
DH+ 1770-KF2 PLC-3 0F(00) Word Range Write
1785-KE 0F(01) Word Range Read
PLC-5 F(00) 0Word Range Write
PLC-5/250
0F(26) Read-Modify-Write (multiple words)
SLC-5/04 0F(A2) Protected Typed Logical Read with
Three Address Fields
0F(AA) Protected Typed Logical Write with
3BCA014034R0001 Rev. F 3-7

Table 3-6. Allen-Bradley Communication Adapter Modules (continued)
Communication DF1 Protocol

Network PLC Model
Adapter Module Command (Function)
DH2 1779-KFL PLC-2 00 Protected Write
1779-KFLR 01 Unprotected Read
02 Protected Bit Write
05 Unprotected Bit Write
08 Unprotected Write
PLC-5/250 0F(01) Word Range Read
DH485 1770-KF3 SLC-500 0F(A2) Protected Typed Logical Read with
SLC-5/01 Three Address Fields
SLC-5/02 0F(AA) Protected Typed Logical Write with
SLC-5/03 Three Address Fields
SLC-5/04
ControlNet 1770-KFC PLC-5 0F(00) Word Range Write
DeviceNet 1770-KFD PLC-5 0F(00) Word Range Write
The PLCs and the communication adapter module installed as

local nodes on the Allen-Bradley network must each be
assigned a unique network address (node number). The
RS-232 port on the communication adapter must be set up as
described in Table 2-11 of Allen-Bradley Data Highway
Interface Module Settings in Section 2.
3-8 3BCA014034R0001 Rev. F

Viewing Controller Module Error Log

The Composer facilities can be used to view the files in the
NVM of controller modules. Perform the following steps within
Composer to determine what files exist in a controller module.
1. Within the Composer navigator select the module from the

project and right-click on it.
2. Choose Run Time > View Files from the controller pop up
menu (Figure 3-3). A new window containing all the files
loaded in the controller will appear. An empty list view indi-
cates that no files exist in the controller.The controller file ID’s
represent the following:
32767 - .map file

32765 - GPI program file
32766 - program data file
1 - module error log
2 - configuration data file
The controller may be in execute mode for this process.
To upload the error log to the EWS, do the following:
1. In the View Files screen, right click on the 1 file.

2. Select the Save option and save as a .txt file.
3. From the File Manager, open the .txt file to review the
error log.
If the .txt file has 0 bytes and file 1 in the controller does not,
then put the controller into Configure mode and repeat the
upload procedure.
The GPI Monitor menu provides a View Error Log button to

view the error log from the controller to the EWS computer.
See Figures 5-2 and 5-3 in section 5 on Monitoring the Link
Status. Clicking on the View Error Log button launches the
Error File Window as shown in Figure 3-2. The user can edit
the error file to add comments and save as a text file to disk.
3BCA014034R0001 Rev. F 3-9

Figure 3-2. Error File Windows
3 - 10 3BCA014034R0001 Rev. F
Function Block Requirements
Figure 3-3. Viewing Controller Module Files

GPI module run-time programs require a number of function
blocks via which specific run-time parameters are defined and
via which status and statistic outputs are reported. The
required blocks are different for the RTU, AB and RTUSLAVE.
The function code, location and purpose of these required pro-
gram support blocks are described in GPI RTU Program Sup-
port Blocks, GPI AB Program Support Blocks and
RTUSLAVE Program Support Blocks.
3BCA014034R0001 Rev. F 3 - 11
The run-time programs communicate PLC system point values

via function blocks. Digital (DO) values read from the PLC sys-
tem are written to function code 45 (Digital Exception Report)
or function code 138 (C and Basic Program Boolean Output
with Quality) blocks. Analog (AO) values read from the PLC
system are written to function code 30 (Analog Exception
Report) or function code 137 (C and Basic Program Real Out-
put with Quality) blocks.
NOTE: Specification S1 of function codes 30 and 45 (block address of input)

must be set to 2 to allow the block to accept values from the run-time program.
Refer to Table 3-7 for typical GPI point data connections to

PLC data.
Table 3-7. GPI Data Point Connections
Function Block Point Type3 PLC Data Point

FC 30 Block ←⎯ AO⎯⎯ Data Register
FC 137 Block ←⎯ AO⎯⎯ Data Register
1 FC 15 Block ⎯⎯AI⎯→ Output Register

1 FC 68 Block ⎯⎯AI⎯→ Output Register
FC 45 Block ←⎯ DO⎯⎯ Digital I/O Point

FC 138 Block ←⎯ DO⎯⎯ Digital I/O Point
2 FC 39 Block ⎯⎯DI⎯→ Digital Output

2 FC 62 Block ⎯⎯DI⎯→ Digital Output
NOTES:
1. The Function Code (FC) of function blocks for AI GPI points may be any
function code that provides a real output value at the block number referenced.
2. The Function Code (FC) of function blocks for DI GPI points may be any
function code that provides a boolean output value at the block number refer-
enced.
3. The Point Type column uses the terms ‘AI’, ‘AO’, ‘DI’, ‘DO’ from the PLC’s
point of view. For RTUs a second set of point types called GPI Point Types are
also used. Refer to Table 3-5 for the relationship between these two definitions.
3 - 12 3BCA014034R0001 Rev. F
Digital (DI) values that are written to the PLC system are read
from boolean output function blocks while analog (AI) values
that are written to the PLC system are read from real output
function blocks. Any function code that provides the appropri-
ate block output can supply these values.
With respect to access, the DO and AO destination blocks and

DI and AI source blocks can be located anywhere in the con-
troller module.
All of the above described function blocks must be included in

the application function block configuration for the target con-
troller module.
GPI RTU Program Support Blocks

For GPI RTU, the run-time program support function block
numbers are defined relevant to the segment control block
number of the segment from which the run-time program is
invoked. The user must specify the block number of the seg-
ment control block in the configuration data file. The relevant
blocks numbers are defined in Table 3-8. Refer to Table 5-16
for a description of the information provided by the support
function blocks.
Table 3-8. Required Program Support Function Blocks for GPI RTU
Relative Function Description

Offset Code
0 82 Segment control block of GPI RTU segment.
9 144 C Allocate (memory) block (optional).
10 143 GPI RTU run-time program Invoke C block.
11 (Optional)1=Write enable, (Default) 0=Write disable. Any boolean
output function block placed at the offset.
12 (Optional) Write group sync default. (optional) Any boolean output
function block placed at the offset.
0-normal operation, 1-write group sync read never sent
13 (Optional) Communications parameter settings (see Table 3-10).
Any Analog output function block placed at this offset.
19 50 For Re-install Data File in primary module.
20 138 Communication interface (link) status. (Good =1; Bad = 0)
21 Port 0 (terminal port) communication status. (Good =1; Bad = 0)
22 Port 1 (printer port) communication status. (Good =1; Bad = 0)
3BCA014034R0001 Rev. F 3 - 13
Table 3-8. Required Program Support Function Blocks for GPI RTU (continued)

Offset Code
23 Current active port (0 or 1).
30 137 # of PLCs referenced in the configuration.
31 # of PLCs with good status.
32 # of DIP and AIP source block read errors.
33 Not used.
34 137 Current cycle execution time in msec.
35 Not used.
36 Not used.
37 Not used.
38 2 Action code for Illegal Function code.
39 2 Action code for Illegal Data Address.
40 2 Action code for Illegal Data Value.
41 2 Action code for Failure in Device.
42 2 Action code for Program Acknowledge.
43 2 Action code for Busy, Rejected Message.
44 2 Action code for NAK, Negative Acknowledge.
50 137 PLC communication failure count.
51 PLC communication time-out count.
52 PLC digital read transaction count.
53 PLC error replies.
54 137 PLC digital write transaction count.
55 PLC register write transaction count.
56 Total DOP + AOP block update count.
57 Total DIP + AIP write to PLC backlog.
60 138 1st PLC status (good = 1, bad = 0).
61 2nd PLC status (good = 1, bad = 0).
62 3rd PLC status (good = 1, bad = 0).
63 to 109 etc. for up to 50 PLCs in increments of four.
120 137 1st PLC station address.
121 2nd PLC station address.
122 3rd PLC station address.
123 to 169 etc. for up to 50 PLCs.
180 137 Illegal Function Code error counter.
3 - 14 3BCA014034R0001 Rev. F
Table 3-8. Required Program Support Function Blocks for GPI RTU (continued)

Offset Code
181 Illegal Data Address error counter.
182 Illegal Data Value error counter.
183 Failure in Device error counter.
184 137 Program Acknowledge error counter.
185 Busy, Rejected Message error counter.
186 NAK, Negative Acknowledge error counter.
Refer to GPI RTU Troubleshooting Information in Section 5 for a description

on how to define action codes (blocks 38 to 44).
Table 3-9. Modbus Port Options BAUD Rate
BAUD Rate Decimal Value Default Example

1200 34305
2400 34817
4800 35073
9600 35585
19200 (Default) 35841 35841 35841
Parity
Even 0
Odd 2
None (Default) 8 8 8
Stopbits
1 (Default) 0 0
2 16 16
Invoke C Block +3 Value 35849 35865
3BCA014034R0001 Rev. F 3 - 15
The Segment Control function block (relative offset 0) specifi-

cations should be set as shown in Table 3-10.
Table 3-10. GPI RTU Segment Control Block Specifications
Specification Value Description

S1 1 Time units of seconds.
S2 0.25 Segment cycle time in units of S1.
S3 255 Segment priority (0 = lowest, 255 = highest).
S4 16 Checkpointing period in cycles S2.
others Defaults or per non-GPI other requirements.
NOTE: For BRC100 and BRC200 with firmware revisions F0 to F5 the value of
S3 should be 0 instead of 255.
The GPI RTU run time program cannot be located in segment 0

due to the number of predefined function blocks in the con-
troller module.
Table 3-11. GPI RTU Invoke C Block Specifications

S1 0 Always 0.
S2 0 Always 0.
S3 6 EOE + RC
EOE is the Error Output Enable with 0 being disabled and 1
enabled.
RC is the maximum Retry Counter. Values are even numbers
between 0 and 20. Application will divide number by 2 to get the
actual number of retries.
S4 5 AIP to PLC minimum update time in segment cycles.
S5 5 Target module % freetime.
S6 2000 PLC communication time-out in msec.
S7 0 DIP + AIP to PLC maximum update time in seconds. If used,
should be set to a value equal to or greater than the number of
DIP + AIP points.
S8 4 Next command delay time in msec.
S9 0 Enhanced Communication
0 = Normal (Max = 19200)
1 = Enhanced (Max = 38400
GPI Configuration Link Baud Rate is set to 19200.
3 - 16 3BCA014034R0001 Rev. F
The RTU module run-time program Invoke C function block

specifications should be set according to Table 3-11.
The RTU module program C Allocation block is optional.

The communication interface works without this block.
The C Allocation block allows Composer to estimate the mem-
ory utilization of the module including the memory utilization
of the RTU module program. Without this block the Composer
memory utilization estimate will include the requirements for
the function block configuration only.
If used, the C Allocation block specifications must be set as

specified in Table 3-12.
Table 3-12. GPI RTU C Allocation Specification Values
Capacity Module RAM (S1) NVM (S2)

500 IMMFP02/12 130072 60000
IMMFP03 140000 66000
BRC100/200 140000 66000
BRC300/400 256000 75000
HAC01 140000 66000
1500 IMMFP02/12 130072 60000
IMMFP03 140000 71000
BRC100/200 140000 71000
BRC300/400 256000 80000
HAC01 140000 71000
3000 IMMFP03 170000 94000
BRC100/200 170000 94000
BRC300/400 256000 105000
HAC01 170000 94000
4000 IMMFP03 180000 109000
BRC100/200 180000 109000
BRC300/400 256000 120000
HAC01 180000 109000
The function code 50 block at Relative Offset 19 (Table 3-8),

with description For Re-install Data File in Primary Module
serves only to introduce a minimal function block configura-
tion change for the purpose of invoking the module Online
3BCA014034R0001 Rev. F 3 - 17
Configuration logic during the Re-install Data File in Primary

Module procedure. If no other function block configuration
changes are needed for this procedure, then a change of this
block’s specification S1 must be applied.
GPI AB Program Support Blocks

For GPI AB, the support function blocks are allocated in
groups for which the starting block numbers must be specified
in the AB Configuration menu (refer to the GPI AB: Common
Parameters in Section 4). The support blocks and their
respective function codes are identified in Table 3-13. The val-
ues and states for these support function blocks are defined in
Table 5-17. The number of function blocks required for each of
the support groups will depend on the number of PLC’s with
which the GPI AB is to communicate.
Table 3-13. Required Program Support Function Blocks for GPI AB
Support Group Function

Description
Block Name Code
Segment Block Segment Number from where the 82
Number program is to be executed
Invoke C Block Function code to execute the 143
Number C program
Offset Component
1 Port selection block Any boolean
(optional) output block
2 Re-install Data File in 50
Primary Module.
Status Block Interface and PLC status group 138
Number starting Block number.
PLC Address Start- PLC address group starting block 137
ing Block Number number.
KF Status Starting KF status group starting block 137
Block Number number.
Write enable block Write enable block number. Any boolean
number. output block
3 - 18 3BCA014034R0001 Rev. F
The GPI AB Segment Control function block specifications

should be set as indicated in Table 3-14.
Table 3-14. GPI AB Segment Control Block Specifications

S1 1 Time units of seconds.
S2 0.25 Segment cycle time in units of S1.
S3 255 Segment priority (0 = lowest, 255 = highest).
S4 16 Checkpointing period in cycles S2.
others Defaults or per non-GPI other requirements.
NOTE: For BRC100 and BRC200 with older firmware revisions F0 to F5 the
value of S3 should be 0 instead of 255.
The AB module run-time program Invoke C function block

specifications should be set according to Table 3-15.
The AB module program C Allocation block is optional. The

communication interface works without this block. The C Allo-
cation block allows Composer to estimate the memory utiliza-
tion of the module including the memory utilization of the AB
module program. Without this block the Composer memory
utilization estimate will include the requirements for the func-
tion block configuration only.
The function block with description Port Selection Block, Off-

set 1, is optional. If installed, it serves to override the Port
Options selected through S4 of the Invoke C Block Specifica-
tions in Table 3-15. This block is typically not installed. When
installed, the block must have a boolean output and will serve
to let function block logic select the active port by which
GPI AB communicates with PLCs.
The function code 50 block with description Re-install Data File

in Primary Module, Offset 2, serves only to introduce a minimal
function block configuration change for the purpose of invoking
the module Online Configuration logic during the Re-install
Data File in Primary Module procedure. If no other function
block configuration changes are needed for this procedure, then
a change of this block’s specification S1 must be applied.
3BCA014034R0001 Rev. F 3 - 19
Table 3-15. GPI AB Invoke C Block Specifications

S1 0 Always 0.
S2 0 Always 0.
S3 20 Startup write to PLC delay in segment cycles
(0 to 127 cycles, equivalent to 0 to 32 seconds).
S4 0 Port options.
0 = Port 0 (terminal) for communications.
Port 1 (printer) for error log output.
1 = Port 0 (terminal) for communications.
Port 1 (printer) not used.
2 = Port 0 and port 1 for primary and standby communications ports. All
configured data communication takes place on the primary port. The
standby port is periodically tested to determine its status.
S5 0 Must be set to 0.
S6 9600 PLC communication baud rate.
Set to one of the rates; 110, 300, 600, 1200, 2400, 4800, 9600 or 19200
baud.
S7 150 The duration in msec that the AB module program will run each segment
cycle. This parameter is ignored if specification S8 is set non-zero.
S8 5 Target module % free time. If set non-zero, the AB module program will
ignore specification S7 and instead automatically adjust it cycle execu-
tion time to maintain this % module free time.
0 = Normal (Max = 19200)
1 = Enhanced (Max = 38400)
3 - 20 3BCA014034R0001 Rev. F

Table 3-16. GPI AB C Allocation Block Specifications
Capacity Module RAM (S1) NVM (S2)

500 IMMFP02/12 154000 44000
IMMFP03 121000 71000
BRC100/200 121000 71000
BRC300/400 121000 73000
HAC01 121000 71000
1500 IMMFP02/12 154000 44000
IMMFP03 154000 71000
BRC100/200 154000 71000
BRC300/400 154000 73000
HAC01 154000 71000
3000 IMMFP03 220000 104000
BRC100/200 220000 104000
BRC300/400 224000 107000
HAC01 220000 104000
4000 IMMFP03 252000 114000
BRC100/200 252000 114000
BRC300/400 290000 116000
HAC01 252000 114000
RTUSLAVE Program Support Blocks

The RTUSLAVE communication interface does not require a
configuration data file. All user input program parameters
must be entered as Invoke C specifications defined in Table
3-19. The support function blocks are described in Table 3-17.
No particular segment is designated for invoking the

RTUSLAVE module run-time program.
If the module function block configuration contains no logic

requiring special handling priority and all blocks serve the
communication interface, than one segment starting at the
default block 15 may serve best. All source function blocks can
3BCA014034R0001 Rev. F 3 - 21
Table 3-17. RTUSLAVE Program Support Function Blocks
Function Function Code Description

Segment Control 82 Segment Segment control.
Control block
C Allocate 144 C Memory C Allocate.
Allocation
block
(optional)
Invoke C 143 Invoke C Invoke C.
block
(Optional) 2 Manual Set Allocated at Invoke C block number + 10
Serial Port Parameters Constant
Status Outputs Allocated at Invoke C block number + 20.
(These outputs are 138 45 Communication interface status.
optional. Refer to the (0 = ok, 1 = errors)
Invoke C specifica- 45 Function block read errors.
tions) (0 = none, 1 = yes)
45 Function block write errors.
(0 = none, 1 = yes)
then be allocated in the lower block numbers. The Invoke C

block can be allocated above the source blocks and the block
receiving data can be allocated above the Invoke C block. With
block order processing of the function blocks, the source blocks
will be processed first, the RTUSLAVE program will serve the
ports next and the blocks receiving data will be processed last
each segment cycle. This sequence will, as far as is possible,
synchronize communications to function block processing.
Example Block #’s Function Code Description

15 FC 82 Segment Control block.
30 - 4900 Interface data source blocks.
4988 FC 144 C Allocate block.
4990 FC 143 Invoke C block.
5010 FC 138/45 Status output blocks.
5100 - 9998 FC 137/138 or Interface data receiving blocks.
FC 30/45
If there are many data values serviced by the communication

interface, it may be best to set up a segment dedicated to the
3 - 22 3BCA014034R0001 Rev. F
RTUSLAVE program. The segment can be set up in the high

block numbers.
Example Block #’s Function Code Description

15 - 9899 Interface data source blocks, interface
data receiving blocks and other function
blocks.
9900 FC 82 Segment Control block.
9909 FC 144 C Allocate block.
9910 FC 143 Invoke C block.
9930 FC 138/45 Status output blocks.
If the module function block configuration contains no logic

requiring special handling priority, the dedicated segment can
be assigned a high priority and a relatively short cycle time of
the order of 0.1 second to maximize the communication port
throughput. If the module function block configuration does
contain logic requiring special handling priority, the priority of
the dedicated segment must be balanced against the require-
ments of the function block logic.
The Segment Control function block specifications should be

set as shown in Table 3-19.
The RTUSLAVE module program C Allocation block is

optional. The communication interface works without this
block. This block allows Composer to estimate the memory uti-
lization of the module including the memory utilization of the
RTUSLAVE module program. Without this block the Composer
memory utilization estimate will include the requirements for
the function block configuration only.
NOTE: For BRC100 and BRC200 with older firmware revisions F0 to F5 the
value of S3 should be 0 instead of 255.
3BCA014034R0001 Rev. F 3 - 23

Table 3-18. RTUSLAVE C Allocation Block Specifications
Module RAM (S1) NVM (S2)

IMMFP02/12 75000 8500
IMMFP03 80000 33000
BRC100/200 80000 33000
BRC300/400 80000 33000
HAC01 80000 33000
The RTUSLAVE module run-time program Invoke C function

block specifications should be set as indicated in Table 3-19.
Table 3-19. RTUSLAVE Invoke C Block Specifications

S1 0 Always 0.
S2 0 Always 0.
S3 0 Reset (pulse) boolean blocks enable.
0 = Disable resetting of boolean blocks.
1-255 = Enable resetting of boolean blocks.
This number specifies the range of the consecutive blocks that will be
reset starting with the block number specified in S8.
S4 64 Parity and baud rate selection.
Parity = 0 (no parity)
(9600 baud, = 1 (odd parity)
no parity) = 2 (even parity)
Baud Rate = 8 (300 baud)
= 16 (1200 baud)
= 32 (2400 baud)
= 64 (9600 baud)
= 128 (19200 baud)
S4 value = Parity + Baud Rate
Set S4 = 0, to use the optional serial port definition
S5 1 The Modbus slave node address to which the RTUSLAVE communi-
cation interface will respond. This node address is applied to both
port 0 (terminal port) and port 1 (printer port).
3 - 24 3BCA014034R0001 Rev. F
Table 3-19. RTUSLAVE Invoke C Block Specifications (continued)

S6 1 Specifies how RTUSLAVE will process register (analog) data
requests.
S = 0 Unsigned 16-bit integer
S = 1 Signed 16-bit integer
Selects optional status output to 4 blocks starting at the Invoke C
block number + 20.
O = 0 No status outputs
O = 2 Status outputs selected
Overrides S option and sets all analog data to be IEEE floating point.
F = 0 No IEEE float support
F = 4 LH byte IEEE float support
F = 12 HL byte IEEE float support
S6 value = S + O + F
S7 0 Block addressing bias. The RTUSLAVE program adds this value to all
modbus addresses to determine the function block number(s) that it
will reference for the request.
S8 0 Block number of the first boolean block that will be reset if S3 is
non-zero.
NOTE: S3 plus S8 must not exceed the highest legal block number 9998 (31999 for the
HAC01 and BRC400 module).
0 = Normal (Max = 19200)
1 = Enhanced (Max = 38400)
Serial Port Parameters (Optional)

The ability to select port options can be configured by a second
method. To use this option, the S4 specification on the Invoke
C block must be set to 0 and a manual set constant (FC 2)
must be located at an offset of 10 from the Invoke C block. The
value in this block will be passed directly to the module's port
open function. If the block has a value of 0 or does not exist
then the port will be opened with the default options of 9600
baud, 8 data bits, 1 stopbits, no parity and no echo.
Table 3-20 shows the values that are to be used to initialize
the portopen function. To construct an initialization value do
3BCA014034R0001 Rev. F 3 - 25
as follows: BaudRate + Parity + StopBits + NOECHO + DATA8.

The default option is equal to 0x8B09..
Table 3-20. MODBUS Slave Port Options
BAUD Rate Decimal Value Default Example

1200 34305
2400 34817
4800 35073
9600 35585
19200 (Default) 35841 35841 35841
Parity
Even 0
Odd 2
None (Default) 8 8 8
Stopbits
1 (Default) 0 0
2 16 16
Invoke C Block +3 Value 35849 35865
3 - 26 3BCA014034R0001 Rev. F
The User Interface Section 4
User Interface
The GPI user interface integrates the support facilities of GPI
RTU, GPI AB and RTUSLAVE into one application program.
NOTE: Make sure that the workstation display settings are for small fonts.
GPI screens may not display properly when the display setting is for large
fonts.
Main Menu
The Main Menu, Figure 4-1, offers eight menu items in the
menu bar that provide access to the following functions:
• Allen-Bradley
Create and maintain AB databases for the Symphony GPI
AB interface. This menu item is enabled only if a valid AB
license string has been entered using the license menu.
• Modbus RTU
Create and maintain RTU databases for the Symphony GPI
RTU interface. This menu item is enabled only if a valid
RTU license string has been entered using the license
menu.
• RTUSLAVE
Set up the user interface for downloading the RTUSLAVE
software to the target controller module.
• Installation to Module
Downloads the GPI application software for one of the
three types of GPIs selected, along with any necessary con-
figuration files. This menu item is enabled only if a data-
base has been successfully processed (for either the AB or
RTU databases) or the RTUSlave was previously selected.
• Monitor
Provides a screen summarizing the interfaces statistics
including the status of each of the devices it is suppose to
be communicating. The contents of the screen will be
3BCA014034R0001 Rev. F 4-1

Main Menu
unique for each of the two (AB, RTU) interfaces. The

RTUSlave does not have a monitor screen. This menu is
enabled only if a database has been selected.
• Licenses
Provides a menu to enter or modify GPI license informa-
tion.
• Help
Contact sensitive help.
• Exit
Terminate the GPI application.
Figure 4-1. The User Interface Main Screen
The Allen-Bradley and Modbus RTU menus lead to the facili-

ties for creating and maintaining the configuration for GPI AB
and GPI RTU applications respectively. These two menu items
allow a user to specify a new or an existing database file, and
allow the entry and verification of configuration data.
An RTUSLAVE interface does not require a configuration data

file, however, this option is required to activate the download of
the module program files.
The Help and Exit options provide a typical Windows Help

facility and an exit path from the user interface.
4-2 3BCA014034R0001 Rev. F

Configuration Overview
1. Launch GPI.
2. If new licenses need to be added, select Licenses and add

applicable license strings.
3. Choose the Allen-Bradley, Modbus RTU or RTU Slave

option.
NOTE: The RTUSLAVE does not require a configuration data file. Selecting the
RTU Slave option enables the main menu Installation to Module option for
RTUSLAVE.
4. For AB or RTU applications, select File > New or Open to

open a database. This step is necessary to allow access to all
other menu options.
5. To import an existing RTU (.RTU) or AB (.AB) text data file,

select Import Data under Files.
NOTE: Changes made to the imported data within the GPI user interface can-
not be sent back to the text file. i.e. The user interface does not provide export-
ing capability.
6. Select Edit to update the configuration data.
7. Select File > Save or Save As to preserve the changes.
8. When finished editing, use the Verify Configuration options

to validate the Configuration Data. The verification process
produces a log (.LOG) file and a review (.REV) file. Verification
Milestone Event and Fatal Error messages are appended to the
log file. General configuration error messages and a summary
of the configuration are saved in the review file. The View Log
option can be used to display the review file.
9. Follow these steps to download the GPI program and data

file to the module:
a. Composer must be installed and running for these

operations. If it is not, install and run it first. The Com-
poser Output window will have a tab added for GPI. Click
this tab to view messages logged during the download pro-
cedure.
b. For GPI AB and GPI RTU applications only, if these

steps have not already been done, complete them now.
3BCA014034R0001 Rev. F 4-3

• If the required database file is not already open, use

File > Open to select and open the configuration
database (.MDB) file.
• Under Licenses, check that the target module
address shown with the license information is cor-
rect
c. Select Verify Configuration to confirm that there are no

errors in the configuration data.
• If the configuration is error free, continue by

selecting the Installation to Module option from the
Main Menu. If there are errors, return to the Edit
facilities to correct the errors first.
d. From the Installation to Module menu, select the Initial-

ize Module and Install option to install the controller mod-
ule program and configuration data for Allen-Bradley or
Modbus RTU. For the RTUSLAVE only the controller mod-
ule program will be installed. The Re-Install Data File in
Primary Module option is part of the Online Configuration
technique described in the Changing GPI Point Data
OnLine section.
Figure 4-2. Installation to Module Menu
4-4 3BCA014034R0001 Rev. F

Enter the target controller module address, control network

number, control unit number and controller number. Refer to
Figure 4-3.
NOTE: The address must match the Loop, PCU and Module numbers associ-
ated and shown with the license string information.
The module must be in Configure mode to allow downloading

to take place. If the module is not in Configure mode, you will
be prompted during the download to change the module’s
mode.
Figure 4-3. Initialize Module and Install Screen
e. Click on Confirm Address and Status to get the status

of the module. This must be done before you do the down-
load. Figure 4-4 shows a successful address confirmation.
3BCA014034R0001 Rev. F 4-5

Figure 4-4. Confirm Address and Status
f. Click on the Download to Module button. The program

will now automatically:
• Validate the licensing information against the tar-

get controller. If this fails, the download operation
will be aborted.
• For AB and RTU applications, process the point
data information. If errors are encountered, the
download operation will be aborted.
• Format the module to allocate controller module
memory to the program files. This operation
removes all existing configuration data from the
module’s memory.
• Download the program files.
• For AB and RTU applications, download the point
data information to a module file.
4-6 3BCA014034R0001 Rev. F

UDF/Batch Support
UDF/Batch Support
In order to support UDF and Batch functionality all that is
required is to reserve extra directory and NVRAM space within
the module that will be running GPI. It is not possible to pre-
dict the amount of space needed so the option is to allow the
User to specify the amounts to be used. When the initial down-
load dialog box is displayed (Figure 4-6) click on the Supported
check box and proceed to download by clicking the Download
to Module button. The dialog box shown in Figure 4-7 is dis-
played. Enter the number of extra files and NVRAM bytes
needed for the UDF/Batch configuration. Click on the Con-
tinue button to finish the download. The Composer product is
used to load the function block configuration and UDF/Batch
Files.
Figure 4-5. Initial Download Dialog Box
3BCA014034R0001 Rev. F 4-7

UDF/Batch Support
Figure 4-6. Reserve for UDF/Batch Dialog Box
Changing GPI Point Data OnLine

NOTE: In order to accommodate controller changes in the IMMFP, BRC and
HAC modules, online GPI data changes are invoked via a method slightly dif-
ferent than the controller Online Configuration process. This section
describes the proper method for implementing Symphony GPI data changes
online.
The GPI point data configuration currently in the module can-

not be modified through Composer Online Configuration
alone. The procedure described in this section is the technique
required to modify GPI point data in a redundant module set
without stopping the modules (placing the primary module in
configure mode).
The procedure consists of two parts. The first part is to load a

modified data file into the primary module of a redundant
module set. The redundant module checkpointing facility
4-8 3BCA014034R0001 Rev. F

UDF/Batch Support
copying the primary module file changes to the backup mod-

ule. The second part must be performed immediately after the
first part. This involves using the Composer Online Configura-
tion procedure to update the function block configuration in
the module to match the GPI point data changes and to invoke
the changes made in the primary module. Some minimal func-
tion block change is required to invoke the Online Configura-
tion logic in the module. The Online Configuration procedure
invokes both the GPI point data changes and the function
block changes in the backup module.
NOTE: This procedure is not equal to the Composer Online Configuration pro-
cedure during which a user is allowed to back out of the changes made to
restore the pre-change state. The GPI-based changes made to the primary
module and copied to the backup module exist in both modules before the
Online Configuration procedure is invoked.
It is especially important to note that from the time the GPI point data file is
replaced in the primary module to the time that the Composer Online Configuration
is completed, the GPI point data file and the function block configuration in the pri-
SPECIFIC
mary module are incompatible. It is therefore important to perform both parts of the
CAUTION
online update procedure in one session to minimize the time during which the
backup module is not available and the primary module has incompatible data in its
NVM.
If the Composer Online Configuration procedure is aborted for any reason and the
SPECIFIC backup module is returned to its backup role, the primary and backup modules' cur-
CAUTION rent GPI data point files and function block configurations will be incompatible. The
GPI program may run with errors after either a module switchover or a power cycle.
Before this online update is initiated, it is recommended that

the user save the data file currently in the module to disk so
that it can be re-installed in the primary module if the Com-
poser Online Configuration procedure is aborted. Refer to
Saving/Restoring Module File 2 Using Composer
Before beginning the Re-install Data File in Primary Module

procedure, prepare both the GPI point data changes and any
Composer function block configuration changes that need to
be made to have both completely ready for the online update.
3BCA014034R0001 Rev. F 4-9

UDF/Batch Support
NOTE: A minimal function block change is required to invoke the module

online configuration logic.
For this purpose, a function code 50 block was added to the

Program Support blocks. As a minimum (or rule), this block’s
specification S1 value should be changed between 0 and 1.
Saving/Restoring Module File 2 Using Composer

File 2 in the NVM memory of the module holds the GPI
Configuration File Information.
Save the module file 2 contents to a disk file as follows:
• Within the Composer navigator, right click on the Control-

ler icon. From the pop up menu select Run Time > View
Files. This will open a screen listing the files currently
stored in the module. Right click on file 2 and select Save.
In the Browser window that is opened select the directory
and enter the file name for saving the module GPI point
data to. Then click on Open.
Restore a saved file 2 to the module as follows:
• Within the Composer navigator, right click on the Control-

ler icon. From the pop up menu select Run Time > View
Files. Right click in the white space of the screen listing the
files currently stored in the module and select Load Data
File. In the browser window that is opened, select the pre-
viously saved file. Click on Open. In the Load C Data File
window enter 2 for the Controller file ID and click on OK.
Re-Install Data File in Primary Module

To load a modified GPI point data file into the primary module of
a redundant module set, select Re-install Data File in Primary
Module from the Installation to Module menu. Refer to Figure
4-8.
The User Interface next displays the prompt message shown in

Figure 4-8.
4 - 10 3BCA014034R0001 Rev. F
UDF/Batch Support
Figure 4-7. Re-install Data File Preparation Prompt
If the existing module file has not been saved or the configura-
tion changes have not been made, click on the Cancel button
to return to the Main Menu. Click the OK button to continue.
Selecting OK displays the screen shown in Figure 4-8. Enter

the address for the licensed module to be updated and click
the Re-install Data File button.
Figure 4-8. Re-install Data File Module Selection Screen
After the data file has been installed, the prompt box of
Figure 4-9 is displayed. Click the OK button to continue.
3BCA014034R0001 Rev. F 4 - 11
UDF/Batch Support
Figure 4-9. Re-install Data File Completion Prompt Screen
While the changed GPI Configuration file is being copied to the

backup module, the checkpointing timer progress bar shown
in Figure 4-10 is displayed. The timer represents a fixed period
to allow the changed data file to be copied to the backup module.
Figure 4-10. Re-install Data File Checkpointing Timer Box
4 - 12 3BCA014034R0001 Rev. F
Module Licensing
After the checkpointing timer period has elapsed, the prompt

message shown in figure 4-11 is displayed. This message
advises the importance of performing the Composer Online
Configuration procedure immediately.
Figure 4-11. Composer Online Configuration Prompt Box
Remember that as a minimal function block configuration

change, specification S1 of the block dedicated to Re-install
Data File in the Primary Module within the Program Support
Blocks must be changed and the module project controller
documents must be re-compiled in preparation for the Online
Configuration update of the configuration in the controller. If
no change is introduced in the Composer project .CLD file, the
controller module will not invoke its Online Configuration
logic, the backup module will simply return to its backup role
and the GPI Configuration file changes will not be invoked.
If module data file 2, the module GPI Configuration file, was

saved to disk before the Re-install Data File in Primary Module
procedure was initiated, and the Composer Online Configura-
tion procedure is aborted, remember to restore the primary
module file 2 from the disk file.
Module Licensing
A license string is provided for each GPI package purchased.
The Licenses option on the Main Menu displays a list of cur-
rently entered license information. From the Module Licensing
menu (Figure 4-12) a new license may be entered and existing
licenses may be modified or removed.
In addition to the controller module type and address, the

license is evaluated with respect to the interface type (RTU, AB
or RTUSLAVE) and the maximum point capacity of the config-
uration data file as purchased. The correct module software,
3BCA014034R0001 Rev. F 4 - 13
Module Licensing
determined by the licensed nomenclature, will be installed to

the controller during the download procedure.
Two new fields have been added to the Module Licensing

screen; Date and Type. The Type field indicates whether the
license is permanent or temporary. If the license is permanent
then the date displayed is the date (month/day/year) that the
license was issued. If the license is temporary then the date
displayed is the date of expiry. When the GPI application is
opened after the expiry date, the Type field will contain the
word "Expired" instead of "Temporary". If the temporary
license was used to download a module configuration then the
application will no longer communicate with the Modbus slave
devices.
Adding a License
On first entry or when new licenses are obtained, the user
must enter each license string by pressing the Add button
(Figure 4-13). The license string must be entered in the
Encrypted License data box. The module address connected to
this license may be entered now, or left at its default setting of
zero and entered later through the Edit facility.
Figure 4-12. Module Licensing Screen
4 - 14 3BCA014034R0001 Rev. F
Module Licensing
The software will validate the license and fill in all other col-
umns except the module location columns. The Loop, PCU and
Module columns will contain user-entered information from
the Add/Edit License facility.
After the license information has been entered, the user can
select the main menu entry Installation to Module.
Prior to downloading the program and data files to a module,

the target module’s location is cross-referenced to a valid
license. If the module address is not assigned to a valid
license, the download operation will be terminated.
NOTE: Plan the modules to licenses map carefully. Once the licensed software
has been assigned to a controller address, the module address can only be
changed or deleted by formatting (initializing) the module in which the licensed
software is currently installed.
Figure 4-13. License Information Screen
Editing a License
The Edit function allows the user to change the module
address from its default setting of zero to a valid module
address.
3BCA014034R0001 Rev. F 4 - 15
Configuration Data File
Deleting a License
In order to delete a license, Composer must be running and
communicating with the module for which the license is to be
deleted. In the case where the module address has been left at
its default setting, Composer is not required to be active.
Configuration Data File

The main data file is an Access database (.MDB) file. The user
interface editing facilities directly access this file. The database
contains five (5) tables named:
ABconfig To hold AB common parameters.

ABdetails To hold AB point parameters.
RTUcfg To hold RTU common parameters.
RTUdetails To hold RTU point parameters.
ScaleNdx To hold RTU scaling data.
NOTE: The scaling data for AB points is stored in Table A-2 of Appendix A
which shows the structure of the tables.
Import facilities are provided to bring data from older genera-

tion DOS GPI02.RTU (.RTU) or GPI03.AB (.AB) text files into
the Access database file.
GPI RTU
Information Required For Configuration
Before starting work on a new configuration, determine the
addresses of all PLC data points that must be read or written
via the RTU serial interface. The PLC supply or support people
can usually provide a list of the point definitions including
point data Modbus addresses. Table 4-1 lists the reference
data required for each PLC data point.
Determine the controller module block numbers that will be

used to accept and source the PLC data. Select a suitable
function block configuration block number layout. If the mod-
ule will be dedicated to the serial communication interface, it
may be convenient to create two module segments. One seg-
4 - 16 3BCA014034R0001 Rev. F
GPI RTU
Table 4-1. Modbus PLC Point Data
PLC Point Parameter Description

Modbus Node Address The Modbus node number by which the PLC is addressed as a
Modbus device. A number in range 1 to 247.
Data Table The Modbus functions supported by GPI RTU each reference one
of four data tables. The tables are generally referred to as the
digital outputs, digital inputs, input registers and output registers
table. Refer to General Configuration Information in Section 3,
Table 3-5.
Table Offset The zero based offset to the point value in the table. i.e. the zero
based digital output, digital input, input register or output register
number. The table offset range for GPI RTU is 0 to 65534.
DOP Alarm State If a digital output or digital input point represents an alarm point,
determine if its alarm state is logic 1 (high) or 0 (low).
AOP/AIP Value Range Input register or output register values may need to be converted
to some engineering units range. To select the appropriate conver-
sion, the PLC value range is needed.
Point ID Tag The point identification text. This text is not required by the inter-
face but can be entered into a GPI RTU as any point identification.
ment for invoking and scheduling the module’s run-time pro-

gram and to contain the run-time program support function
blocks. Refer to General Configuration Information in
Section 3. The second segment can contain all other function
blocks including the blocks to accept and source PLC data.
Determine which write option to use for writing data to PLCs.

GPI RTU provides two methods for writing data to PLCs. One
method is by single point value write transactions using Mod-
bus functions 05 and 06. The second is by multiple sequential
point values write group transactions using Modbus functions
15 and 16. Refer to Dependencies and Constraints in
Section 1, Table 1-1. The multiple sequential point values
write group transactions are more efficient but require the PLC
points to be in successive table locations or at least have inter-
spersed point gaps of no more than 64 non-referenced digital
outputs or 4 non-referenced output registers among the data
points of a group. The maximum number of points in a write
group (including gaps) is 800 digital outputs or 50 output reg-
isters.
NOTE: The table locations in the gaps will be overwritten each time a write
group write transaction is performed.
3BCA014034R0001 Rev. F 4 - 17
GPI RTU
Multiple value write groups are created by the GPI program.

The program sorts all GPI points in a configuration by GPI
point type, PLC node address, PLC data table and table offset.
From the sorted points, the program selects the write group
points in order so that all points within a group will lie within
the same PLC and the same data table.
Example If a configuration includes DIP points which address Digital Outputs 200 ..
217, 221 .. 279, 352 .. 519 and 535 .. 635 all in the same PLC, then the fol-
lowing groups will be created in terms of the digital output numbers:
Group 1, 80 Digital Outputs will be written including

Digital Outputs 200 .. 279 those in the 3 digital outputs gap between
outputs 217 and 221.
Group 2, 284 Digital Outputs will be written including
Digital Outputs 352 .. 635 those in the 15 Digital Outputs gap between
outputs 519 and 535.
The Digital Outputs in the gap between outputs 279 and 352
are not included or written and force the split to two instead of
one group.
The write method selection is critical to users who intend to

utilize the data table elements in the interspersed gaps for
other purposes. A gap may be enclosed within a write group
depending on the size of the gap and the position of the gap
with respect to the referenced data points. If the multiple point
write group transaction method is used, the point assignments
must be made with care.
Configuration Menus
The data entered into this database will be used to generate
the GPI data file that is downloaded to the module. The config-
uration parameters and point table contained in the database
that is open at the time downloading is initiated will be used to
create the data file. The license attached to the target module
address in the Licenses table will be used to verify the destina-
tion of the program and data files. The target module type and
the run-time module program files will also be selected based
on the license strings entered.
4 - 18 3BCA014034R0001 Rev. F
GPI RTU
File Menu
The configuration of the RTU interface starts from the main
menu Modbus RTU option. To start a new configuration for a
RTU Modbus interface, select the Modbus RTU menu option.
From the pull-down menu select File > New to create a new
database or Open to open an existing database file.
Importing Configuration Data

Configuration data may be imported from a DOS based
GPI02.RTU configuration (.RTU) text file by selecting main
menu option Modbus RTU > File > Import Data. This selection
opens a Browse window to find and select the required (.RTU)
text file.
NOTES:
1. The text (.RTU) file data must have the format described in Appendix B of
this manual.
2. The DOS based GPI02.RTU does not support 32-bit long or IEEE float
data and its configuration does not include file type selection for AOP and AIP
point types. All AOP and AIP points are therefore imported as 16-bit integer (S
for short integer) PLC data type points
Refer to Figure 4-14 for a view of the pull-down menu options.
Figure 4-14. MODBUS RTU Files Menu
3BCA014034R0001 Rev. F 4 - 19
GPI RTU
Edit Menu
To place data into the configuration database or to edit the
data, again click on the Modbus RTU pull-down menu and
select Edit. Figure 4-15 shows the edit options of the Modbus
RTU menu. Configuration serves to enter the shared common
parameters. Refer to Common Parameters and Figure 4-19
for details. Point Data Grid (Figure 4-19) and Single Data
Record (Figure 4-20) provide two methods for entering or mod-
ifying the RTU point data parameters.
Figure 4-15. The Modbus RTU Edit
The Point Data Grid method displays a grid which provides all
parameter fields for each data point in a row of the grid. Refer
to Figure 4-20 and Point Parameters for a detailed descrip-
tion of the types of entries available for each of the fields in the
grid. Horizontal and vertical scrolling is provided.
The Single Data Record method opens a window with all

parameter fields for a single data point shown vertically with
field names to the left of each data field and valid options
where available. Refer to Figure 4-20 and Point Parameters
for a detailed description of the types of entries available for
each of the fields in the menu.
4 - 20 3BCA014034R0001 Rev. F
GPI RTU
Verify Configuration Menu

The Verify Configuration menu item through its submenus
(Figure 4-16) serves to verify the current RTU configuration
data (Process Configuration), view the configuration data (View
Review File) and the configuration information results (View
Log File) of the verification process on the screen. To look at
these two log files outside the GPI menu, they are located in
the same directory as the GPI database (shown in the lower left
section of the GPI Main Menu). The file name extension for the
Review File is ".REV" and for the Log File it is ".LOG".
Figure 4-16. The Modbus RTU Verify Configuration
Select Process Configuration to verify the current configuration

data. It first presents the sub-menu shown in Figure 4-17.
Select the Hardware Platform (controller module type),
Redundancy (controller is redundant or not) and Point
Capacity according to the license information for the destina-
tion controller then click the Process File button. When the
verification has been completed, Number of Points, Number of
Read Groups and Number of Write Groups are reported under
Configuration Information. The Close button can be clicked
before or after verifying the configuration data to return to the
Main Menu.
After the verification process has been performed, the result

can be viewed by making the main menu selection
Modbus RTU > Verify Configuration > View Log. The verification
process outputs messages to two files, a .LOG and a .REV file.
The file name will be that of the database with the letters RTU
appended.
3BCA014034R0001 Rev. F 4 - 21
GPI RTU
Example If the database name is confdata.mdb, the messages are output to files con-
fdatartu.LOG and confdatartu.REV. If the configuration data contains major
errors that prevent it from being processed, the .REV file will not contain use-
ful information and the View Log option will display the .LOG file in which a
message or messages will describe the reason why the configuration data
could not be processed. If the configuration can be processed, then the .REV
file content will first list any discrepancies encountered in the data and will
then list a review of the configuration data. Appendix F shows an example
(incomplete) review output file.
Figure 4-17. Process RTU Configuration Screen
Figure 4-18. Modbus RTU Common Configuration Parameters Screen
4 - 22 3BCA014034R0001 Rev. F
GPI RTU
Table 4-2. RTU Configuration Common Parameters
Parameter Allowable Entries Description

Link Baud Rate 1200, 2400, 4800, This is the PLC system serial communication baud rate
9600 or 19200 that will be set in the controller module ports.
NOTE: This baud rate always applies to both port 0 and port1 regardless
of their usage.
Parity ODD, EVEN, NONE The parity checking options that may be selected for
the PLC system communication.
RTS Control RTS, NO-RTS Select RTS for half-duplex communication. With RTS
selected, the RTS line is raised while a message is
transmitted from the port.
Select NO-RTS for full-duplex communication. With
NO-RTS selected, the RTS/CTS lines are used for port
read buffer overflow control only.
Link Port AUTOMATIC, Select AUTOMATIC for normal redundant ports where
Selection 0 (TERMINAL PORT), one port is used for primary PLC system communica-
1 (PRINTER PORT), tion and the other port is periodically tested only for
ALTERNATE, standby.
FOLLOW BLK,
When the Bumpless Redundant Module Takeover
WRITE BOTH AUTO,
option is selected, the Automatic option will provide
FOLLOW-WRT BOTH
bumpless switching of primary to back-up serial ports,
if the back-up port status is Good.
Select 0 (terminal port) or 1 (printer port) to do all PLC
communication on one serial cable interface to the PLC
system.
The remaining options are highly specialized modes for
PLC system communication.
ALTERNATE forces the module program to alternate
between port 0 and port 1 for successive transactions.
FOLLOW BLK works in conjunction with the Port Select
Block Number parameter setting to allow the function
block configuration to select the port for the module
program.
WRITE BOTH AUTO invokes normal redundant ports
(AUTOMATIC) but additionally performs all write trans-
actions to both the ports (primary and standby).
FOLLOW-WRT BOTH takes the primary port selection
from the block specified for parameter Port Select Block
Number but additionally performs all write transactions
to both the ports (primary and standby).
3BCA014034R0001 Rev. F 4 - 23
GPI RTU
Table 4-2. RTU Configuration Common Parameters (continued)

GPI Segment 30 ≤ Block # ≤ 9800 The block number of the Segment Control function
Block 31800 for HAC, block starting the module segment from which the
BRC400 run-time program is invoked and in which the RTU Pro-
gram Support Blocks must be installed. Refer to
General Configuration Informationin Section 3.
Link Port Select 30 ≤ Block # ≤ 9998 The port select block for parameter Link Port Selection
Block Number 31998 for HAC or option FOLLOW BLK and FOLLOW-WRT BOTH. The
BRC400 block must have a boolean output.
Maximum 2 ≤ Size ≤ 224 The maximum byte size of a digital read group reply
Digital Read message data field. Eight digital values (bits) require
Group Size one byte of the reply data field.
Maximum 2 ≤ Size ≤ 224 The maximum byte size of an analog read group reply
Analog Read message data field. One register value requires two
Group Size bytes of the reply data field.
Maximum Write 2 ≤ Size ≤ 100 The maximum byte size of a write group command
Group Size message data field. One register value requires two
bytes of the command data field. Eight digital values
(bits) require one byte of the command data field.
Redundant NORMAL or Selects the Redundant Module Switchover method for
Module BUMPLESS initial writing DIP and AIP point values to the PLC sys-
Takeover tem.
Translation NONE, MODICON, NONE - No translation.
SQUARE-D, GE Ser-6,
MODICON - 584, 984, Quantum PLCs.
GE Ser-5, GE 90-PCM
or GE 90-CMM SQUARE-D - Square-D SY/MAX Controllers.
GE Ser-6 - GE Fanuc Series 6.
GE Ser-5 - GE Fanuc Series 5.
GE 90-PCM - GE Fanuc 90 Series with a PCM inter-
face module.
GE 90-CMM - GE Fanuc 90 Series with a CMM inter-
face module.
4 - 24 3BCA014034R0001 Rev. F
GPI RTU
Point Parameters
Figure 4-19. Modbus RTU Grid Control Point Data Entry screen
Module Point Type DOPNA - To read a digital value from a PLC for output to a
controller function code 45 (Digital Exception Report) or 138
(Basic or C Boolean Output with Quality) block in the applica-
tion configuration. It defines a DOP digital read point with no
alarm indication.
DOP - Same as DOPNA above. Provided for compatibility with

older version .RTU files.
DOPAH - This defines a DOP digital read point for which the
high state (boolean 1) is the alarm state. Otherwise same as
DOPNA above.
DOPAL - This defines a DOP digital read point for which the
low state (boolean 0) is the alarm state. Otherwise same as
DOPNA above.
AOP - To read an analog type value from a PLC for output to a

controller function code 30 (Analog Exception Report) or 137
(Basic or C Real Output with Quality) block in the application
configuration.
3BCA014034R0001 Rev. F 4 - 25
GPI RTU
Figure 4-20. Modbus RTU Single Point Data Entry Screen
DIP - Read the output of a block from the application configu-

ration (any block with type boolean output) for output to a PLC
digital output table point.
AIP - Read the output of a block from the application configu-

ration (any block with type real output) for output to a PLC
output register table point.
Block Number Specifies the function block number where data will be read
from for DIP and AIP points or where data will be written to for
DOP and AOP points. The block numbers may be anywhere in
the controller module.
PLC Number The Modbus node number. This is the number by which the
PLC is addressed by Modbus communication. Refer to Table
4-3.
PLC Data Table The PLC Data table in which the PLC point data is located.
The Modbus protocol sub-set implemented for GPI RTU

addresses four data tables.
4 - 26 3BCA014034R0001 Rev. F
GPI RTU
Read/Write Digital - PLC Digital Output (DO) table. This table

is read with Modbus command 01 (Read Digital Outputs) and
written into with command 05 (Force Single Digital Output) or
command 15 (Force Multiple Digital Outputs). The actual size
of this table depends on the PLC make and model.
Read Digital - PLC Digital Input (DI) table. This table is read
with Modbus command 02 (Read Digital Inputs) and cannot be
written into. The actual size of this table depends on the PLC
make and model.
Read/Write Analog - PLC Output Register (AO) table. This

table is read with Modbus command 03 (Read Output Regis-
ters) and written into with Modbus command 06 (Preset Single
Output Register) or command 16 (Preset Multiple Output Reg-
isters). The actual size of this table depends on the PLC make
and model.
Read Analog - PLC Input Register (AI) table. This table is read
with Modbus command 04 (Read Input Registers) and cannot
be written into. The actual size of this table depends on the
PLC make and model.
Point Address The PLC Data table location (zero based offset into the table).
Scale Index An index to the required scaling coefficients for converting the
AOP point’s PLC value to the module block value or for con-
verting the AIP point’s block value to the PLC value. Scaling
can be applied to all AOP and AIP points, whether the PLC
data is a 16-bit integer (single register) or 32-bit long or IEEE
float (two register) value.
NOTE: The scaling data also includes a selection to process the PLC integer
value as a signed or unsigned integer.
The scaling coefficients are applied as described in the follow-

ing two equations:
BV = Scale Factor * PV + Offset Value
PV = (BN – Offset Value) / Scale Factor
where: BV is the block value
PV is the PLC value
A configuration may have up to 64 different scaling coefficient

sets. Each set consists of a Scale Factor, an Offset Value and
3BCA014034R0001 Rev. F 4 - 27
GPI RTU
an integer Signed vs Unsigned indicator. Refer to Analog

Point Scaling.
Analog Data Type The Analog Data Type parameter defines the data type of the
PLC point value and applies only to analog type (register) data.
The PLC point value may be one of five data types indicated in
the RTU configuration as S, LHL, LLH, FHL, or FLH each
described as follows:
S - A one register 16-bit integer. The register value may be des-

ignated signed or unsigned in the scaling coefficient set refer-
enced by the Scaling Index. Refer to Analog Point Scaling.
LHL - A two register 32-bit (long) integer. The 32-bit integer

value is contained in two consecutive registers of the PLC. The
register order is High Low (HL) meaning that the high order 16
bits of the 32-bit value are contained in the first (lower num-
bered) register and the low order 16 bits in the next register in
the PLC Register table.
LLH - A two register 32-bit (long) integer. The 32-bit integer

value is contained in two consecutive registers of the PLC. The
register order is Low High (LH) meaning that the low order 16
bits of the 32-bit value are contained in the first (lower num-
bered) register and the high order 16 bits in the next register
in the PLC Register table.
FHL - A two register 32-bit IEEE float. The 32-bit float value is
contained in two consecutive registers of the PLC. The register
order is High Low (HL) meaning that the high order 16 bits of
the 32-bit value (the sign, exponent and high order 8 bits of
the mantissa) are contained in the first (lower numbered) reg-
ister and the low order 16 bits (of the mantissa) in the next
register in the PLC Register table.
FLH - A two register 32-bit IEEE float. The 32-bit float value is
contained in two consecutive registers of the PLC. The register
order is Low High (LH) meaning that the low order 16 bits of
the 32-bit value (the low order 16 bits of the mantissa) are con-
tained in the first (lower numbered) register and the high order
16 bits (the sign, exponent and high order 8 bits of the man-
tissa) in the next register in the PLC Register table.
Tag - A 256 character text entry to identify the GPI point. This
entry is for the user’s convenience and is not used by the con-
4 - 28 3BCA014034R0001 Rev. F
GPI RTU
troller module’s run-time program for the communication

interface.
Table 4-3. RTU Point Parameters

Point Type DOP, DOPNA, DOPAH, DOP, DOPNA, DOPAH and DOPAL specify
DOPAL, AOP, DIP, AIP, digital points read from a PLC DO or DI table.
Status Register DOPAH and DOPAL specify points that alarm
on High and Low respectively. DOP and
DOPNA specify status points without alarm
indication.
AOP specifies an analog point read from a
PLC AO or AI table.
DIP specifies a digital point written to a PLC
DO table.
AIP specifies an analog point written to a PLC
AO table.
Block Number BN = Block Number An DOP or AOP point target block number
For PLC write points into which the point value will be written.
AIP and DIP:
Function block requirements:
30 ≤ BN ≤ 9998
30 ≤ BN ≤ 31998 (HAC or DOP Function code 138
BRC400) DOP Function code 45 (S1 = 2)
AOP Function code 137
For PLC read points
AOP Function code 30 (S1 = 2)
AOP and DOP:
0 ≤ BN ≤ 9998 An DIP or AIP point source block number that
0 ≤ BN ≤ 31998 (HAC or supplies the value written to a PLC.
BRC400)
DIP Any block output of type boolean.
AIP Any block output of type real.
PLC Number PN = PLC Number The PLC Modbus number, the number by
1 ≤ PN ≤ 247 which the PLC is addressed as a Modbus
device on the Modbus network. The Modbus
network may be a simple point-to-point
RS232 connection between the controller
module termination port and the PLC device.
It can also be a multi-drop RS485 network
interconnecting multiple Modbus slave
devices to a RS485/RS232 convertor and the
controller module termination port. Regard-
less, Modbus slave devices only respond to
Modbus command messages addressed to
their PLC number.
3BCA014034R0001 Rev. F 4 - 29
GPI RTU
Table 4-3. RTU Point Parameters (continued)

PLC Table DO, DI, AI, AO DO = Read/Write Digital (Modbus CMD 1)
DI = Read Digital (Modbus CMD 2)
AI = Read Analog (Modbus CMD 3)
AO = Read/Write Analog (Modbus CMD 4)
Point Address MA = Modbus Address The PLC point value location within the PLC
0 ≤ MA ≤ 65534 table. A zero based offset from the start of the
table.
Scale Index SI = Scale Index An index to select one of the scaling coeffi-
1 ≤ SI ≤ 64 cients sets.
An RTU configuration contains a maximum of
64 scaling coefficient sets for converting PLC
analog (register) data to ABB controller mod-
ule function block real (IEEE float) values and
vice versa. These coefficients can be set by
the user to meet the application requirements.
Each scaling coefficient set includes an indi-
cator that specifies that the PLC integer value
should be handles as either a signed or
unsigned integer.
Refer to Analog Point Scaling.
Analog Data Type S, LHL, LLH, FHL or FLH S = 16-bit integer (1 register)
LHL = 32-bit integer (2 registers)
register order High/Low
LLH = 32-bit integer (2 registers)
register order Low/High
FHL = 32-bit IEEE float (2 registers)
register order High/Low
FLH = 32-bit IEEE float (2 registers)
register order Low/High
Tag Up to 256 alphanumerical May be entered as a brief point description.
characters. Not used by the communication software.
Analog Point Scaling

A GPI database file RTU configuration contains a table of scal-
ing coefficient sets for converting PLC analog type (register)
values to ABB controller function block IEEE float real values
and vice versa. This table can contain up to 64 scaling coeffi-
cient sets. Each set includes a scale factor, an offset value, and
4 - 30 3BCA014034R0001 Rev. F
GPI RTU
an indicator specifying that the PLC integer value must be

interpreted as either a signed or unsigned value.
PLC analog type (register) values can represent five data types
described in Table 4-3 as parameter analog data type. The
signed or unsigned indicator is ignored when the analog data
type specified is an IEEE float type FHL or FLH.
To enter or modify RTU scaling coefficients select Modbus RTU

on the Main Menu and then select Edit > Scale Index. This
brings up the window shown in Figure 4-21. To add a new
scaling coefficient set, click the Add button to open a new
record (maximum of 64). Then enter the required Scale Factor,
Offset Value and Signed/Unsigned indicator. To modify or
delete scaling coefficients, use the horizontal scroll bar to
select the desired scaling coefficient record. Then simply
change record contents as required or click the Delete button
to change to the default contents (Scale Factor = 1.0, Offset
Value = 0.0, Signed/Unsigned = Unsigned). Click the Restore
button to restore the record contents to what they were before
changes were made. Click the Update button to update the
database table and save changed data. Changed entries can-
not be restored by clicking the Restore button after the Update
button has been clicked.
Figure 4-21. Screen to Enter Scaling Coefficients
Each AOP and AIP type point in a RTU configuration refer-

ences a Scaling Coefficient set by its Scale Index. The Scale
Index is equal to the Record: number shown in the horizontal
scroll bar. Refer to Figure 4-21.
3BCA014034R0001 Rev. F 4 - 31
RTUSLAVE
RTUSLAVE
Configuration Requirements
RTUSLAVE, as the name implies, provides a Modbus slave
interface to a Modbus master device. It does not utilize a con-
figuration data file as do GPI RTU and GPI AB and has no
pre-programmed data communication requirements. As such
it does not initiate transactions but instead waits to receive
data transaction command messages from the master device.
RTUSLAVE supports the Modbus commands list in Table 1-1,
RTUSLAVE in Section 1.
With no configuration data file, the RTUSLAVE configuration is

entirely by function blocks. The RTUSLAVE module’s run-time
program uses the data addresses that it receives in Modbus
command messages to address function blocks. Block num-
bers are references to the defined function blocks in a module.
Typically not all block numbers are defined. Undefined block
numbers may lie anywhere in the block number range. The
MFP02, MFP12, MFP03, BRC100, BRC200, BRC300 and
BRC400 all have a block number range of 0 to 9999. The
HAC01 and BRC400 block number range is 0 to 31998 of
which 4000, 10000 or 20,000 may be defined (configured) by a
user depending on the software license purchased.
RTUSLAVE is dependent on a number of function blocks to

invoke the module’s run-time program and to schedule its exe-
cution. It further can optionally output four interface status
values and requires function block for these outputs. These
function block requirements are described in Table 3-17 of
RTUSLAVE Program Support Blocks in Section 3.
RTUSLAVE translates a Modbus command message address

into a block number reference using the user specified bias set
in Invoke C block S7. Refer to RTUSLAVE Program Support
Blocks in Section 3.
Block number = Modbus Address + Bias
RTUSLAVE does not discriminate between PLC data types

(Modbus commands) to translate the Modbus addresses into
block numbers thus allowing register and boolean data to
completely overlap. It is up to the user programming or config-
uring the master Modbus device to know how function blocks
4 - 32 3BCA014034R0001 Rev. F
RTUSLAVE
are allocated in the RTUSLAVE module in order to reference

appropriate data.
Example 1 For a user familiar with AEG Modicon conventional PLC addressing, where
data points are referenced as follows:
Digital Outputs 00001 – 09999

Digital Inputs 10001 – 19999
Input Registers 30001 – 39999
Output Registers 40001 - 49999
Bias (Invoke C block S7) = 1, Modbus address = 100

Block number = 100 + 1 = 101
Example 2 A user may want to allocate all data to be communicated to block numbers
5000 and up and reference the blocks using Modbus address 0 and up. This
can be done by setting the Bias (Invoke C block S7) to 5000.
Modbus address 0 would yield block reference 5000 (0 + 5000).

Modbus address 4999 would yield block reference 9999 (4999 + 5000).
A Modbus address may represent a Digital Output, Digital

Input, Input Register or an Output Register depending on the
Modbus function in the command message. In Example 1, to
address block 101 as Digital Output (Modicon 00101) or Digi-
tal Input data (Modicon 10101), the block output must be a
boolean value output. To address block 101 as Output Regis-
ter (Modicon 40101) or Input Register (Modicon 30101) data,
the block output must be a real value output.
Modbus read commands 01 (Read Digital Outputs), 02 (Read

Digital Inputs), 03 (Read Output Registers) and 04 (Read Input
Registers) address multiple successive data point values start-
ing with the Modbus address in the command message. The
commands reference successive points of the same type. To
meet this requirement, the module configuration must contain
successive function blocks that can supply appropriate data
(boolean or real) in successive blocks starting at the block ref-
erenced by the Modbus address in the command. Thus, to sat-
isfy Modbus read commands 01 and 02, there must be
successive block boolean outputs at the block number
addressed in order to provide values for all points included in
the read command. For Modbus commands 03 and 04, there
must be successive block real outputs at the block number
addressed. When a block in the range of blocks referenced by a
3BCA014034R0001 Rev. F 4 - 33
RTUSLAVE
read command does not provide the appropriate output value,

the RTUSLAVE interface substitutes the value boolean 0 or
real 0.0. If none of the blocks in the range of blocks referenced
by a read command provide appropriate output values, the
RTUSLAVE interface returns a Modbus error reply with Error
Code 02, Illegal Data Address.
The single value write commands, Modbus command 05 (Force

Single Digital Output) and 06 (Preset Single Output Register),
serve to write a value to a function block. To accept a value
from the module program, the referenced block function code
must be function code 138 (C and Basic Program Boolean Out-
put with Quality) or function code 45 (Digital Exception
Report) function block for Modbus command 05. The refer-
enced block must be function code 137 (C and Basic Program
Real Output with Quality) or function code 30 (Analog Excep-
tion Report) function block for Modbus command 06.
NOTE: For function code 30 and 45, specification S1 must be set 2 to allow the
function block to accept the program value. If the module program cannot write
the value to the referenced block (wrong function code or undefined block num-
ber), a Modbus error reply is returned with Error Code 02, Illegal Data Address.
Modbus read commands 15 (Force Multiple Digital Outputs)

and 16 (Preset Multiple Output Registers) address multiple
successive data point values starting with the Modbus address
in the command message. The commands reference successive
points of the same type. To meet this requirement, the module
configuration must contain successive function blocks that
can accept a boolean or real data value in successive blocks
starting at the block referenced by the Modbus address in the
command. Thus, to satisfy Modbus write command 15, there
must be successive function code 138 (C and Basic Program
Boolean Output with Quality) and/or function code 45 (Digital
Exception Report) function blocks at the block numbers
addressed in order to write the values for all points included in
the command. For Modbus command 16, there must be suc-
cessive function code 137 (C and Basic Program Real Output
with Quality) and/or function code 30 (Analog Exception
Report) function blocks at the block number addressed. When
any block in the range of blocks referenced by a write com-
mand does not accept the command value, the RTUSLAVE
interface returns a Modbus error reply with Error Code 02, Ille-
gal Data Address.
4 - 34 3BCA014034R0001 Rev. F
GPI AB
User Interface Menus

A RTUSLAVE interface is configured entirely by function
blocks and does not use a configuration data file so that there
are no configuration data file maintenance menus specific to
it. Refer to RTUSLAVE Program Support Blocks in Section 3.
Before the RTUSLAVE program files can be downloaded to the

licensed module address, the RTUSLAVE menu item must be
selected. A message will then be displayed indicating that the
application will download the files to the module, based on
having at least one valid RTUSLAVE license string entered.
Click on the OK button and the Installation to Module menu
item will be activated. Select the Installation to Module > Initial-
ize Module and Install menu item.
Enter the RTUSLAVE’s module address and click on the Down-

load to Module button.
NOTE: Composer must be active before beginning the installation sequence.
GPI AB
Information Required For The Configuration
Before starting work on a new configuration determine the
addresses of all PLC data points that must be read or written
via the AB serial interface. The PLC supply or support people
can usually provide a list of the point definitions and their PLC
data point addresses. Table 4-4 lists the reference data
required for each PLC data point.
Table 4-4. Allen-Bradley PLC Point Data

DH2 Link Address Data Highway II link number. Always 0 for DH, DH+, DH485, ControlNet
and DeviceNet applications.
DH2 Node Address Data Highway II node number. Always 0 for DH, DH+, DH485,
ControlNet and DeviceNet applications.
Station Address The network station number. The range is as follows:
DH, DH+ and DH2 0 to 254
DH485 0 to 31
ControlNet 1 to 99
DeviceNet 0 to 63
3BCA014034R0001 Rev. F 4 - 35
GPI AB
Table 4-4. Allen-Bradley PLC Point Data (continued)

Context PLC-3 context 0 to 15
PLC-5/250 module no. 0 to 4
Other PLC types 0
File Type The file type is required for two reasons.
1. For some PLCs it is used in the data communication address field.
2. GPI AB uses it to determine how to convert analog type data. The file
types are:
O Output (digital)
I Input (digital)
S Status (PLC status information)
B Bit (digital)
D Decimal (BCD)
C Control (addressed as a word file)
T Timer (addressed as a word file)
X PLC-2 (dummy digital data entry)
N iNteger
IEEE float and unsigned long 32-bit data can be read from an integer (N)
file type as two consecutive words. To identify a 32-bit data point value,
the file type letter N must be replaced as follows:
F IEEE float
L Unsigned Long (32-bit) integer
IEEE float data can be accessed directly from a float (F) file type for the
PLC-5 and SLC-5.
NOTE: If data is to be written to the PLC then the Block Write option must
be used.
The file types supported for configuration by PLC type are:
PLC-2 D, X, N (F, L)
PLC-3 O, I, S, B, D, C, T, N (F, L)
PLC-5 O, I, S, B, D, C, T, N (F, L)
PLC-5/250 B, S, N (F, L)
SLC-5 B, N (F,L)
File Number Range 0 to 999.
PLC-2 does not support files and the file number must be set to 0.
Word Address The zero based offset to the word of the file. The range is 0 to 1999. For
PLC-2, the point value address is the physical PLC memory word
address.
4 - 36 3BCA014034R0001 Rev. F
GPI AB
Table 4-4. Allen-Bradley PLC Point Data (continued)

Bit Information For digital point values, the word bit number (0 to 15). For analog type
point values, the value bit size. Most analog type values will be 16-bit val-
ues. On older PLCs values may be 8, 12 or 16 bits wide. 8 or 12-bit val-
ues must occupy the lower order bits of a word. GPI AB masks out the
high order 8 or 4 bits of the 16-bit value received when it extracts 8 or
12-bit values from PLC reply messages. For 32-bit data, the word bit
number must be 13 for Long integer, 14 for float data in an integer (N)
file, and 4 for float data in a float (F) file.
DO Alarm State If a digital input point represents an alarm point, determine if its alarm
state is logic 1 (high) or 0 (low).
AO/AI Value Range Analog type values may need to be converted to some engineering units
range. To select the appropriate conversion, the PLC value range is
needed.
Point ID Tag The point identification text. This text can be entered into the configura-
tion for convenience.
A point list provided by a PLC supplier will typically not

include all of the point data information listed in Table 4-2.
Some of the information, specifically the first four items may
be the same for all points and may be generally known for an
application.
Determine the controller module block numbers that will be

used to accept and source the PLC data. Select a suitable
function block configuration block number layout. If the mod-
ule will be dedicated to the serial communication interface, it
may be convenient to create two module segments. One seg-
ment for invoking and scheduling the module’s run-time pro-
gram and to contain the run-time program support function
blocks. Refer to General Configuration Information in
Section 3. The second segment can contain all other function
blocks including the blocks to accept and source PLC data.
Determine which write option to use for writing data to PLCs.

AB provides two methods for writing data to PLCs. One method
is by single point value change of state activity. All PLC types
except PLC-3 (bit write) allow multiple single point points in
the same PLC to be updated in the same transaction. The sec-
ond method is by multiple sequential point values write group
transactions using word range write type commands. Refer to
Table 1-3 Allen-Bradley DF1 Commands Supported by AB
in Section 1. The multiple sequential point values write group
3BCA014034R0001 Rev. F 4 - 37
GPI AB
transactions are more efficient but require the PLC points to

be in successive file or memory locations or at least have gaps
of no more than 10 non-referenced words among the data
points of a group. The maximum number of points in a group
(including gaps) is 112 analog type points (16-bit words) which
can contain 1792 digital type points.
NOTE: The table locations in the gaps will be overwritten each time a multiple
sequential point values write transaction is performed.
Multiple value write groups are created by the GPI Application

program. The program sorts all GPI points in a configuration
by GPI point type, PLC link, node, station address, PLC data
file number and file word address (and bit number for digital
points). From the sorted points, the program selects the write
group points so that all points within a group lie within the
same PLC and file.
Example If a configuration includes DI points all in file B3, with word/bit positions
20/0 .. 21/7, 22/1 .. 24/9, 36/2 .. 51/9 and 53/5 .. 63/5 all in the same PLC,
then the following groups will be created in terms of the word/bit numbers:
Group 1, 20/0 .. 24/9 bits in the 8 bit gap from 21/8 to 22/0 and the un-ref-
erenced high order bits 10 through 15 of word 24.
Group 2, 36/2 .. 63/5 448 bits (28 words) will be written including the low
order bits 0 and 1 of word 35, the bits in the 27 bit
gap from 51/10 to 53/4 and the high order bits 6
through 15 of word 63.
The bits in the 176 bit (11 words) gap from 25/0 through 35/
15 are not included or written and force the split to two
instead of one group.
The write method selection is critical to users who intend to

utilize the data table elements in the gaps for other purposes.
A gap may be enclosed within a write group depending on the
size of the gap and the position of the gap with respect to the
referenced data points. If the multiple sequential point values
write group transaction method is used, the point assignments
must be made with care.
4 - 38 3BCA014034R0001 Rev. F
GPI AB
Configuration Menus
The data entered into this database is used to generate the GPI
data file that is downloaded to the module. The configuration
parameters and point table contained in the database that is
open at the time downloading is initiated, is used to create the
data file. The license attached to the target module address in
the Licenses table, verifies the destination of the program and
data files. The target module type and the run-time module
program files are also selected, based on the license strings
entered.
File Menu
To start a new configuration for an AB interface to an
Allen-Bradley PLC system, click on the Allen-Bradley button
on the menu bar. From the pull-down menu select File > New
to create a new database or select File > Open to open an exist-
ing database. This creates a new table or opens an existing
table in the GPI database. Refer to Figure 4-22 for a view of the
pull-down menu selection.
Figure 4-22. The Allen-Bradley File Menu
3BCA014034R0001 Rev. F 4 - 39
GPI AB
Importing Configuration Data

Configuration data may be imported from a DOS based
GPI03.AB configuration text (.AB) file by selecting menu bar
Allen-Bradley > File > Import Data.
The text (.AB) file data must have the format described in
Appendix C of this manual.
If importing an older configuration file from a SLC-500, the

line “{GLOBAL} BLOCKWRITE=Y” must be added in the Global
Parameter section of the file before proceeding with the import.
Edit Menu
There are three choices for the Edit option of the Allen-Bradley
pull-down menu (Figure 4-23). The first choice, Configuration,
Figure 4-23. The Allen-Bradley Edit Menu
is to enter shared common parameters that establish

communication criteria and define the module program
support function block locations. Refer to Figure 4-26 for a
view of the Entry window and the Common Parameters
section for details. The second, Point Data Grid, and third,
Single Data Record choices, provide two formats for entering
configuration data point information.
4 - 40 3BCA014034R0001 Rev. F
GPI AB
The Point Data Grid method opens a window with a grid control
in which all parameter fields for a data point lie in a row of the
grid. Refer to Figure 4-27 and the Point Parameters section
for a detailed description of the types of entries available for
each of the fields in the grid. Horizontal scrolling has to be
used to view all data fields.
The Single Data Record method opens a window with all

parameter fields for a single data point shown vertically with
field names to the left of each field. Refer to Figure 4-28 and
the Point Parameters section for a detailed description of the
types of entries available for each of the fields in the grid.
Verify Configuration
The Verify Configuration menu item through its submenus
(Figure 4-24) serves to verify the current AB configuration data
(Process Configuration), view the configuration data (View
Review File) and the configuration information results (View
Log File) of the verification process on the screen. To look at
these two log files outside of the GPI menu, they are located in
the same directory as the GPI database. The file name exten-
sion for the Review File is ".REV" and for the Log File it is
".LOG" .
Figure 4-24. AB Verify Configuration Menu
Select Process Configuration to verify the current configuration

data. This first presents the sub-menu shown in Figure 4-25.
Select the Hardware Platform (controller module type) >
Redundancy (controller is redundant or not) > Point Capacity
according to the purchase license information and then click
the Process File button. When the verification has been com-
3BCA014034R0001 Rev. F 4 - 41
GPI AB
pleted, Number of Points, Number of Read Groups and Number

of Write Groups are reported under Configuration Information in
the sub-menu. The Close button can be clicked before or after
verifying the configuration data to return to the Main Menu.
After the verification process has been performed, the result

can be viewed by making the main menu selection Allen-Brad-
ley > Verify Configuration > View Log. The verification process
outputs messages to the .LOG and a .REV files. The file name
will be that of the database with the letters AB appended.
Example If the database name is datafile1.mdb, the messages are output to files
datafile1ab.LOG and datafile1ab.REV. If the configuration data contains
major errors that prevent it from being processed, the .REV file will not con-
tain useful information and the View Log option will display the .LOG file in
which the reason why the configuration data could not be processed will be
described. If the configuration can be processed, then the .REV file content
will first list any discrepancies encountered in the data and will then list a
review of the configuration data. Appendix G shows an example (condensed)
review output file..
Figure 4-25. Process Allen-Bradley Configuration Screen
4 - 42 3BCA014034R0001 Rev. F
Common Parameters
Common Parameters
Figure 4-26. AB Configuration Common Parameters Screen
Highway Defines the Allen-Bradley network on which the PLCs reside.

The number of nodes that may reside on the network depends
on the network type. Refer to Table 4-2.
KF Address for Port 0 The network station address of the network interface module
and Port 1 (e.g. 1785-KE) of the serial communication interface to port 0
(terminal port) and port 1 (printer port). Both ports may be
used in a primary and standby mode. Alternatively port 0 only
may be designated for PLC system communication while port 1
is not used or is used to log error messages to a printer or ter-
minal that supports RS-232 serial input. Refer to GPI AB Pro-
gram Support Blocks in Section 3, Table 3-15.
3BCA014034R0001 Rev. F 4 - 43
Common Parameters
KF Time-out and Retries KF Time-out is the maximum time (in milliseconds) that the
run-time program will wait to receive an ACK or NAK response
after sending a command message to the network interface
adapter module (e.g. 1770-KF2 on DH+). KF Retries is the
number of times an ENQ message will be sent to prompt for an
ACK/NAK response before the transaction fails and the port is
assigned Bad status. If an ACK is received, the run-time pro-
gram next waits for the command reply to arrive from the tar-
get PLC.
PLC Time-out and PLC Time-out is the maximum time (in milliseconds) that the
Retries run-time program will wait to receive a command reply mes-
sage from a PLC after an ACK has been received from the net-
work interface adapter module. PLC Retries is the number of
times the command will be tried before the PLC status and all
DOP and AOP points dependent on the PLC are marked Bad.
PLCs that are marked Bad are retried every 5 seconds to
attempt to re-establish communication. The slower retry rate
is to minimize the impact from PLCs with known Bad status
on the overall cycle time.
PLC-2 Write Type Defines whether protected or unprotected write commands will
be applied for PLC-2 write transactions.
Segment Number Specifies the controller module segment number of the seg-
ment from which the run-time program will be invoked.
NOTE: The segment number is dependent on the order of segment control

blocks (FC 82) in the controller module configuration. The first one (fixed at
block number 15) starts segment 0, the next one segment 1, etc., in block num-
ber order.
Segment Block Number The block number of the segment control function block from
which the run-time program is invoked. Defines by definition
the starting block number of the specified segment. The Invoke
C block and, if used, the C Allocation block should be installed
in this segment, typically immediately following the Segment
block. Refer to GPI RTU Program Support Blocks in
Section 3, Table 3-14 to set the block specifications.
Invoke C Block Number Defines the block number of the Invoke C block (FC 143) from
which the run-time program is invoked. This block number
must lie within the block number range of the specified seg-
ment. Refer to GPI AB Program Support Blocks in Section 3,
Table 3-15 to set the block specifications.
4 - 44 3BCA014034R0001 Rev. F
Common Parameters
Loop Number Defines the number of the INFINET loop on which the control-
ler module resides.
PCU Number Defines the number of the PCU in which the controller module
is installed.
Module Number Defines the module number assigned to the controller module.
Module Type Defines the controller module type. Must be MFP02/12,
MFP03, BRC100, BRC200, BRC300, BRC400 or HAC01.
Status Block Number Defines the block number of the first of four or more succes-
sive blocks via which the run-time program reports the status
of the ports and PLCs. Refer to GPI AB Program Support
Blocks in Section 3, Table 3-13.
KF/PLC Status Block Defines the block number of the first of four or more succes-
Number sive blocks via which the run-time program reports the status
of each KF/PLCs. Refer to GPI AB Program Support Blocks
in Section 3, Table 3-13.
PLC Address Block Defines the block number of the first of four or more succes-
Number sive blocks via which the run-time program reports the station
address of each PLC referenced in the configuration. Refer to
GPI AB Program Support Blocks in Section 3, Table 3-13.
Write Enable Block Defines the block number of the Write Enable function. The
Number function code block must be boolean.
If the parameter entry is a value of 0 (zero), writes to the PLC

device will be enabled.
If the parameter entry is a non-zero value and a boolean func-

tion code does not exist at the specified block address, writes
to the PLC device will be enabled.
If the parameter entry is a non-zero value and a boolean func-

tion code exists at the specified block address then an output
value of 1 (one) for this block will enable writes to the PLC
device. An output value of 0 (zero) for this block will disable
writes to the PLC device. Refer to GPI AB Program Support
Blocks in Section 3, Table 3-13.
Table 4-5 describes the configuration common parameters and

the entries that may be made for each parameters.
3BCA014034R0001 Rev. F 4 - 45
Common Parameters
Table 4-5. GPI AB Configuration Common Parameters

Highway I Supports the Allen-Bradley network types: DH,
DH+, DH485, ControlNet and DeviceNet.
II Supports the Allen-Bradley network type DH2 in
PCL mode.
KF Address for Port 0 0 .. 254 The network station address for the network inter-
face module (e.g. 1785-KE) of serial communica-
tion interface to port 0 (terminal port).
KF Address for Port 1 0 .. 254 The network station address for the network inter-
face module (e.g. 1785-KE) of serial communica-
tion interface to port 1 (printer port).
KF Reply Time-out 1000 .. 32767 The network interface module communication
reply (ACK/NAK) time-out in milliseconds.
KF Retries 0 .. 10 The number of times network interface module
communication will be retried.
PLC Reply Time-out 1000 .. 32767 PLC transaction time-out in milliseconds.
PLC Retries 0 .. 10 The number of times a failed PLC transaction will
be retried.
PLC-2 Write Type Protected Defines whether protected or unprotected write
Unprotected commands will be applied for PLC-2 write transac-
tions.
Segment No. 0 .. 7 Specifies the controller module segment number
of the segment from which the run-time program
will be invoked.
Segment Block No. Any legal function The block number of the Segment Control function
block number. block from which the run-time program is invoked.
Invoke C Block No. Any legal function Defines the block number of the Invoke C block
block number (FC 143) from which the run-time program is
invoked. This block number must lie within the
block number range of the specified segment.
Loop No. 0 .. 255 The controller module address INFINET loop num-
ber.
PCU No. 0 .. 255 The controller module address INFINET PCU
number.
Module No. 0 .. 31 The controller module number.
Module Type MFP02/12 Specifies the target controller module type.
MFP03
BRC100/200/300/400
HAC01
4 - 46 3BCA014034R0001 Rev. F
Point Parameters
Table 4-5. GPI AB Configuration Common Parameters (continued)

Status Block No. Any legal function Starting block number of the blocks via which the
block number. run-time program reports the status of the ports
and PLCs.
KF/PLC Status Block Any legal function Starting block number of the blocks via which the
No. block number. run-time program reports the status of each KF/
PLCs.
PLC Address Block Any legal function Starting block number of the blocks via which the
No. block number. run-time program reports the station address of
each PLC referenced in the configuration.
Write Enable Block Any legal function The block number of the write enable.
No. block number.
Point Parameters
Figure 4-27. AB Configuration Grid Control Point Data Entry Screen
3BCA014034R0001 Rev. F 4 - 47
Point Parameters
Figure 4-28. AB Configuration Single Point Data Entry Screen
Point Type DO - To read a digital value from a PLC for output to a control-
ler function code 45 (Digital Exception Report) or 138 (Basic or
C Boolean Output with Quality) block in the application con-
figuration.
AO - To read an analog type value from a PLC for output to a

controller function code 30 (Analog Exception Report) or 137
(Basic or C Real Output with Quality) block in the application
configuration.
DI - Read the output of a block of the application configuration

(any block of type boolean output) for output to a PLC word/bit
location.
AI - Read the output of a block of the application configuration

(any block of type real output) for output to a PLC word loca-
tion.
4 - 48 3BCA014034R0001 Rev. F
Point Parameters
Alarm Definition The user may add an alarm description for DO points only.
This field may be set to one of the following 2-letter entries:
NA - No alarming specified for the point.
AH - Alarm on High (logical 1). GPI AB will set the point’s

alarm indication when the point value is logical 1.
AL - Alarm on Low (logical 0). GPI AB will set the point’s alarm
indication when the point value is logical 0.
Number System Either D (decimal) or O (octal) may be selected for describing
the PLC word and bit fields. These two fields will always be dis-
played in the number system selected.
Tag Name Any 28 character tag name. This field has no impact on PLC
communication. It is included exclusively for documentation.
The only ASCII character that is not valid is the double quote “.
Block Number Specifies the function block number where data will be read
from for DI and AI points or where data will be written for DO
and AO points. The block numbers may be anywhere in the
controller module. For DO and AO points, refer to the next
item.
Block Type GPI AB can write DO PLC values to either function code 45
(digital exception report) or function code 138 (Basic or C Bool-
ean Output with Quality) blocks. It can write AO PLC values to
either function code 30 (Analog Exception Report) or function
code 137 (Basic or C Real Output with Quality) blocks. Enter E
(Exception Report FC 30 or 45) or B (Basic Output with Qual-
ity FC 137 or 138).
PLC Type PLC-2, PLC-3, PLC-5, PLC-5/250 and SLC500 (SLC500,
SLC-5/01/02/03/04) are supported. GPI AB will address a
mix of different type PLCs on the same network but all must be
addressable as local nodes from the communication adapter
(1785-KE etc.). Some PLC types are compatible with one net-
work type.
For example: SLC500, SLC-5/01/02/03 are compatible with

DH485 only. PLC-5, PLC-5/250 and SLC-5/04 directly sup-
port DH+ while PLC-2 and PLC-3 can be connected to DH+ as
local nodes using special Allen-Bradley bridge modules.
Link Allen-Bradley DH2 link address.
Node Allen-Bradley DH2 node address.
3BCA014034R0001 Rev. F 4 - 49
Point Parameters
PLC Number The Allen-Bradley network station address. The legal address
range is dependent on the network type. Refer to Table 4-6.
Module Type PLC-5/250 module type. Only RM (Resource Module) and LP
(module memory) are supported. Refer to Table 4-6.
Module Number PLC-5/250 module number or PLC-3 Context. Refer to
Table 4-6.
File Type Refer to Table 4-6 for the file types supported by PLC type. File
types X, F and L are not PLC file types but were introduced for
GPI AB to verify and manage PLC data. For PLC-5 and SLC-5
the file type F is supported.
File Number The PLC file number. Refer to Table 4-6 for limitations.
Word Address The zero based offset to the word of the file. For PLC-2, the
point value word address is the physical PLC memory word
address. IEEE Float (F) and unsigned Long (L) 32-bit values
are stored in two successive words. Specify the lower word
address for such values.
Bit For DO and DI points, the bit number is part of the point’s PLC
address and refers to the bit position in the word referenced.
For AO and AI points, the bit number may specify the bit width
of the point value. It is also used to identify 32-bit IEEE float
and unsigned long point values (mainly to the run-time pro-
gram). Refer to Table 4-6.
Multiplier and Offset The controller uses float values for all analog (real) values. In
PLCs, analog type values are defined as shown in Table 4-7. To
do the conversion from float to the PLC format (AI points) or
from the PLC format to float (AO points), a multiplier/offset
may be applied to re-scale values.
AI, PV = Multiplier * BV + Offset

AO, BV = Multiplier * PV + Offset
where: PV is the PLC point value
BV is the function block value
Table 4-6 describes the GPI AB point parameter restrictions.
Table 4-7 describes the maximum range of PLC analog values

with respect to file type and bit information.
4 - 50 3BCA014034R0001 Rev. F
Point Parameters
Table 4-6. GPI AB Point Parameters

GPI Point Type DO DO Digital point read from PLC.
AO AO Analog point read from PLC.
DI DI Digital point written to PLC.
AI AI Analog point written to PLC.
Block No. Any legal function Defines the block number into which a PLC value will be
block number. written or from which a value will be read and written to
a PLC.
Block Type B Relevant to DO and AO points only.
E B (Basic): FC 137 or FC 138.
E (Exception): FC 30 or FC 45.
For DO and AO points only, specification S1 of FC 30
and FC 45 must be set to 2 (S1=2)
Alarm Definition AH DO point alarm description.
AL AH Alarm on logical 1.
NA AL Alarm on logical 0.
NA No alarming.
Number System D Number system in which PLC addresses will be speci-
O fied.
D Decimal
O Octal
PLC Type PLC-2 The Allen-Bradley PLC type. The SLC500 selection
PLC-3 serves SLC models SLC500, SLC-5/01, SLC-5/02,
PLC-5 SLC-5/03 and SLC-5/04.
PLC-5/250
SLC500
Link 0 .. 254 The Allen-Bradley Data Highway II link address. Always
(octal 0..376) 0 for other networks.
Node 0 .. 254 The Allen-Bradley Data Highway II node address.
(octal 0..376) Always 0 for other networks.
PLC Number 0 .. 254 The Allen-Bradley network station address.
(octal 0..376) The legal address range is dependent on the network
type. For ControlNet the range is 1 to 99. For DeviceNet
the range is 0 to 63.
Module Type 0 or 3 PLC-5/250 module type.
0 RM (resource module).
3 LP (module memory).
Module No. 0 .. 15 PLC-5/250 Module number (always 0).
PLC-3 Context (0 to 15).
0 = default context
3BCA014034R0001 Rev. F 4 - 51
Point Parameters
Table 4-6. GPI AB Point Parameters (continued)

File Type O (Output) The file types supported by PLC type are:
I (Input) PLC-2 D, X, N (F, L)
S (Status) PLC-3 O, I, S, B, D, C, T, N (F, L)
B (Bit) PLC-5 O, I, S, B, D, C, T, N (F, L)
D (Decimal) PLC-5/250 B, S, N (F, L)
C (Control) SLC-5 B, N (F, L)
T (Timer)
X is a dummy file type for PLC-2 digital point data refer-
X (non-file)
ences.
N (iNteger)
F (IEEE float) IEEE float and long 32-bit data can be read from an inte-
L (Long) ger (N) file type as two consecutive words. To identify a
32-bit data point value, the file type letter N must be
replaced as follows:
F IEEE float
L Unsigned Long (32-bit) integer
IEEE float can be accessed from a float (F) file type for
PLC-5 and SLC-5 only.
NOTE: If data is to be written to the PLC then the Block

Write option must be used.
File No. 0 .. 999 PLC-2 does not support files and the file number must
be set to 0.
Word Address 0 .. 1999 The zero based offset to the word of the file. For PLC-2,
the point value word address is the physical PLC mem-
ory word address.
F and L 32-bit values are stored in two successive
words. Specify the lower word address for such values.
Specify the correct float word address for float (F) type
files.
Bit 0 .. 16 DO and DI points, 0 to 15.
AO and AI points by file type:
S, C, Te16
D, N eee8, 12, 15, 16
L eeeee 13
F eeeee14 (using N type file)
F eeeee4 (using true F type file)
Refer to Table A-2 in Appendix A.
4 - 52 3BCA014034R0001 Rev. F
Communicating with the RSLogix System
Table 4-6. GPI AB Point Parameters (continued)

Offset Any real value in AI,eePV = Multiplier * BV + Offset
fixed point or sci-
AO,eBV = Multiplier * PV + Offset
entific notation
where: BV is the function block value
Multiplier Any real value in AIaaaPV = Multiplier * BV + Offset
fixed point or sci-
AOaaBV = Multiplier * PV + Offset
entific notation
where: BV is the function block value
Tag Text up to 28 char- The point identification text. Alphanumeric characters
acters only.
Table 4-7. PLC Analog Value Maximum Ranges
File Type Bit Range

S, C, T 16 0 .. 65535
D 8 0 .. 99
12 0 .. 999
16 0 .. 9999
N 8 0 .. 255
12 0 .. 4095
15 -32768 .. +32767
16 0 .. 65535
L 13 0 .. 4294967295
F 14 ±2.0E±38 (7 significant decimal digits)

The Symphony GPI AB communicates with the AB family of
controllers using DF1 protocol and routing method. The
RSLogix family of controllers uses a routing method called
ControlNet. The Symphony GPI AB communicates with the
controllers using the AB 1770-KFC15 module (revision 4.2 or
greater firmware is required) to route the messages between
the ControlNet and DF1 families. In order for the AB KFC mod-
ule to be able to route these messages the node addresses
must be modified in the GPI AB configuration. The modifica-
3BCA014034R0001 Rev. F 4 - 53
tion is dependent on which slot the CNB module is located in

the PLC rack. One of the following values must be added to the
ControlNet node address to have it routed correctly.
- Add 100 to the ControlNet node address to route the

messages to slot 0.

messages to slot 1.

messages to slot 2.
When the KFC module receives a message with an address

greater than 99, it will add a Port number of 1 and a slot num-
ber of 0, 1, or 2 (based on the node address) to the message.
The Port Number of 1 refers to the Control Logix backplane
port of the CNB module.
NOTE: The actual ControlNet address of the CNB module must be between 1
and 50.
Example The Control Logix rack has a controller in slot 0 and a CNB module that is set
to MAC ID 5. The GPI AB is to communicate with a controller by setting the
node address to 105. All messages will get routed to the CNB at MAC ID 5
then to the controller in slot 0.
4 - 54 3BCA014034R0001 Rev. F
Composer Drawing Manager

The Manage Drawings menu item provides a feature to create
the Composer logic drawings (CLDs) for the Analog and Digital
data to be transferred from the foreign device to the GPI con-
troller in the Symphony system. This feature is for the RTU
Master and Allen Bradley interfaces. The logic is created using
a set of templates and includes both the block number assign-
ments and tag definitions.
Analog Tag Definition

- Name
- Description
- Engineering Units
- Low and High Alarm Limits
Digital Tag Definition

- Name
- Description
- Digital Alarm State
In order to use this feature to create these drawings the follow-

ing conditions must be met:
• The necessary information must be entered into the GPI

Tag database, using the GPI menus.
• Additional function code related information must be

entered, using ACCESS 97. (Access 2000 or later can be
used provided the database is not converted to the newer
version).
• A set of CLD templates must be supplied. The sample

project provided has templates that can be copied or a site
specific set of templates can be created provided that the
object names are not modified with addresses used in
Figure 4-29 in the Composer project
Example: Control Net: 1 Control Unit: 32 Controller: 8.
The Composer Drawing Manager menu includes user definable

entries for the four types of CLD's to be used to generate the
supporting logic for transferring the data from the foreign
device to the GPI controller. To transfer digital data from the
3BCA014034R0001 Rev. F 4 - 55
foreign device to the GPI controller the two templates defined

in the "DI CLT" and "DO CLT" provides the supporting block-
ware for the GPI application. To transfer analog data from the
foreign device to the GPI controller the two templates defined
in the "AI CLT" and the "AO CLT" provides the supporting
blockware for the GPI application. The I/O references between
the sets of drawings are based on the tag name with an added
suffix.
The CLD names shown in Figure 4-29 match those in the sam-
ple Composer project provided with the GPI application. The
field "Number of Blocks per page" refers to the number of tags
to be assigned per CLD. This number applies to all the four
data types.
The "AOL Block" and "DOL Block" fields indicate the starting
function code address for each type of exception block within
the controller. The values entered must be sufficiently far
apart to allow no overlap in addresses assigned.
The "Block AOL Sum" field when assigned a value of "-1" indi-
cates the Sum function code (FC 15) is not used. When it is
assigned a valid function code address and the
GPI_AOL_VS_CLT is specified as the AOL CLT then this func-
tion code is included for all the analog tags and the specifica-
tions is set based on the entries in the GPI tag database.
The "REF Suffix" field contains the text to be appended onto

the tag name in order to create an I/O reference between the
two groups of CLDs.
The box below the "REF Suffix" field is a status message box
where the GPI application displays activity messages. The box
in the lower right corner indicates the number of tags in the
GPI configuration.
4 - 56 3BCA014034R0001 Rev. F
Figure 4-29. Composer Drawing Manager
Creating Composer Drawings

The buttons on the right side of the menu are the user's inter-
face to creating the CLD's for the selected GPI interface. The
process to create the CLD drawings requires the GPI to create
a Master database from the GPI database. Two buttons are ini-
tially enabled on the menu, Save and Transfer to Master. If
the Transfer to Master button is disabled then there is a pre-
vious tag database in the master database which may not be
up to date.
To create or modify the Composer drawing perform the following
1. Copy the current GPI configuration information to the

Master database click Transfer to Master.
2. To create the number of CLDs for both the analog and

digital tags in the GPI database click Create CLDs.
3. Update the I/O references between the DI/DO CLTs and the
AI/AO CLTs through the Update IRef/ORef CLDs.
4. Next update the block numbers on all the CLDs using the
Update Block Numbers button.
5. Update all static text on all CLDs. Click Update Text.
3BCA014034R0001 Rev. F 4 - 57
6. Update all the Exception Report function codes. Click

Update Exception Reports.
Sample GPI Executive CLDs for both RTU and AB interfaces

(Figure 4-30) have been included and can be manually copied
into the modules configuration.
Figure 4-30. Sample CLD
4 - 58 3BCA014034R0001 Rev. F
GPI Tag Database Modifications
Modifying fields other than those described below could result in the GPI to not
WARNING
function correctly. Backup the GPI configuration database before continuing.
NOTE: The Symphony GPI 3.0 tag database includes a number of new fields
that do not exist in the earlier Symphony GPI 2.x tag databases. To use this
feature with a tag database created with an earlier version the tag information
must be copied from the earlier database structure to the new database struc-
ture using ACCESS.
The GPI tag database requires modifications to a number of

fields in order for the Composer Drawing Manager to create the
GPI's supporting CLD's. Locate the GPI tag database and open it
using ACCESS. In the database there are seven tables listed,
only open either the RTUdetails or ABdetails table depending on
the type of interface used. All the field descriptors that begin
with "XGG" are related to the Composer Drawing Manager.
Table 4-8 lists the fields of information that need to be entered.
Table 4-8. GPI Tag Database Fields
Field Name Applies To Purpose

XGG_TAGDESC Both types Tag description (32 characters max)
XGG_VAL0 Analogs Tags 0 value in Eng. Units
XGG_SPAN Analogs Tags maximum value in Eng. Units
XGG_SCALEFACTOR Analogs Scaling Factor for Block AOL Sum function, must be
used in conjunction with Block AOL Summ menu item.
XGG_ALARM Digitals Alarm state for DOL function code (0, 1, 2)
XGG_ENGUNITS Analogs Eng Unit index for AOL function code
XGG_PACKBIT Analogs 0 - no packed registers; 1 - packed register
XGG_LOWALARM Analogs Low alarm limit for AOL function code
XGG_HIGHALARM Analogs High alarm limit for AOL function code
XGG_SIGCHANGE Analogs % Significant change limit for AOL function code
3BCA014034R0001 Rev. F 4 - 59
Common Parameters
Link Baud Rate The PLC communication baud rate. Refer to Table 4-2 for all the supported
rates.
Parity The PLC communication RS232 port parity setting. Refer to Table 4-2 for
supported settings.
RTS Control The PLC communication RS232 Port Handshake option selected. Refer to
Table 4-2 for available options.
Link Port Selection This selection defines which port (terminal port 0, printer port 1, or both) will
be used for communications with PLCs. For a single RS232 cable connec-
tion to the PLC system, one of the single port options (Port 0 Only or Port 1
Only) should be selected so that the module’s run-time program will not
attempt to use the port that has no cable connection to the PLC system. For
redundant (two cable) connections to the PLC system, the AUTOSELECT
option should be selected. With AUTOSELECT, the module’s run-time pro-
gram will initially attempt communicating on one port. If successful, this port
becomes the primary port. If not successful, communicating is tried on the
other port and if successful this port becomes the primary port. The non-pri-
mary port always becomes the standby port. All configured data communi-
cation takes place on the primary port. The standby port is periodically
tested to determine its status.
GPI Segment Block The block number for the segment from which the module’s run-time pro-
gram is invoked and in which the RTU Program Support Blocks must be
installed. Refer to General Configuration Information in Section 3.
Link Port Select When the Link Port Selection is set to FOLLOW BLK or FOLLOW-WRT
Block Number BOTH, this entry must be set to specify the block number from which the
port selection will be made. The block must have a boolean output value
that will specify 0 when Port 0 (terminal port) is to be used and 1 when Port
1 (printer port) is to be used. When the Link Port Selection is not FOLLOW
BLK or FOLLOW-WRT BOTH, this selection plays no roll.
Maximum Digital This setting limits the number of digital points that can be placed in a digital
Read Group Size read group. The limit is defined in terms of the maximum byte size of the
data field of a digital read Modbus reply message. One byte can hold 8 digi-
tal values. Refer to Table 4-2 for the range limits.
Maximum Analog This setting limits the number of register points that can be placed in an
Read Group Size analog read group. The limit is defined in terms of the maximum byte size of
the data field of an analog read Modbus reply message. A register value is
equivalent to two bytes. Refer to Table 4-2 for the range limits.
Maximum Write This setting limits the size of digital and analog write groups. The limit is
Group Size defined in terms of the maximum byte size of the data field of write com-
mand messages. One byte can hold 8 digital values. A register value is
equivalent to two bytes. Refer to Table 4-2 for the range limits.
4 - 60 3BCA014034R0001 Rev. F
Redundant Module This setting specifies the way the module’s run-time program will manage
Takeover DIP and AIP write points after a redundant module switchover to the backup
module. If set to NORMAL, the module’s run-time program will re-write all
DIP and AIP PLC points with the current values of the module source
blocks. If set to BUMPLESS, the module’s run-time program will update DIP
and AIP PLC points only when their module source block values change
after the module switchover.
Write Command This setting defines which Modbus write commands will be used to update
Protocol DIP and AIP PLC points. If set to SINGLEWRITE, Modbus commands 05
(Force Single Digital Output) and 06 (Preset Single Output Register) will be
used to update the PLC system one point at a time. If set to BLOCKWRITE,
Modbus commands 15 (Force Multiple Digital Outputs) and 16 (Preset Mul-
tiple Output Registers) will be used.
NOTE: If BLOCKWRITE is selected, the run-time program will initially read

the write group data point values to initialize the write group data buffers with
PLC data in case the groups include interspersed non-referenced PLC data.
Translation There are many different PLC types that support Modbus RTU communica-
tion. Programming facilities for such PLCs typically reference data points
using PLC specific address formats. Users typically know PLC data points
by the PLC specific addresses. This GPI user interface can optionally trans-
late the Modbus point address to its PLC specific address as feedback to
users. This translation is applied only in the main menu Modbus RTU, Edit,
Single Data Record sub-menu. Refer to Table 4-2 for available translations.
Comment This entry allows comment text to be added to the configuration for the
user’s convenience. This data is not used by the interface.
3BCA014034R0001 Rev. F 4 - 61
3BCA014034R0001 Rev. F
Troubleshooting Section 5
General Information
GPI provides diagnostic facilities for identifying errors that
may be encountered during configuration and errors that may
occur online in the communication interface. Diagnosing of
errors encountered during configuration is described in User
Interface in Section 4 of this manual. This section of the man-
ual describes the online error diagnosing mechanisms avail-
able.
The GPI module programs report status and statistics infor-
mation to support function blocks. In addition, the RTU and
AB programs log error messages to a controller module NVM
Error Log file. Both are described in the following sub-sections,
Status & Statistics Output Blocks and GPI NVM LOG File.
When only one of the two serial ports is assigned to the com-
munications interface of a GPI application, the error messages
may be output to the unused port. To view the messages, an
ASCII terminal may be connected by RS232 serial communica-
tion cable to the unused port. This output facility provides
only a simple message by message dump to the serial port as
the messages are produced and includes no scrolling or any
other control for viewing or holding the messages.
Output of GPI error messages to the unused port must be
enabled. Refer to General Configuration Information in
Section 3, Table 3-11 and 3-15.
For RTU, Invoke C block specification S3 must be set to 1 to
enable the error message output. The module program will
output messages to the unused port only if port option
(PORT=) Port 0 Only (1) or Port 1 Only (2) is selected in the con-
figuration.
For AB, Invoke C block specification S4 must be set to 0, Port 0
used for communication and Port 1 used for error log output.
This section provides some general guide lines for diagnosing
the communication interface. Most problems are encountered
after the hardware is first set up and software is first installed
and configurations are first tried. The first objective is to
3BCA014034R0001 Rev. F 5-1

The Module Startup Sequence
establish communication with the PLC system. This objective

proves out the cabling and the termination jumper settings,
items that do not change after a working arrangement has
been obtained. After communication with the PLC system has
been established, remaining errors usually relate to situations
where most of the configured data points can be addressed
successfully but some of the configured data points cannot.
This is typically indicated when a PLC’s status alternates
between Good and Bad status. Other problems may relate to
environmental interference (continuous or intermittent elec-
tromagnetic interference) and run-time system variables such
as variations in PLC reply times, controller module and/or PLC
system loading, etc.
GPI products report status information in the following ways:
• Status output function blocks. The outputs are

described in Function Block Requirements in Section 3.
These blocks indicate link (communication interface) and
individual PLC status as either good or bad.
• The Invoke C block output. This output indicates the GPI

version number or a fatal error code. Refer to Check for
Fatal Errors in GPI RTU Troubleshooting Information
and Check for Fatal Errors in GPI AB Troubleshooting
Information.
A NVM error log file. The RTU and AB programs log messages
to a NVM file. Refer to Viewing Controller Module Error Log
in Section 3 for information on how to view the messages. The
RTUSLAVE program does not produce an error log file. The dif-
ferent messages that may be logged are listed in the
Appendix B and Appendix C.
The Module Startup Sequence

At startup, the controller module GPI program reads the con-
figuration binary data from the NVM configuration file (file #1)
and initializes all its parameters (RTU and AB only,
RTUSLAVE has no configuration data file.). The program also
reads the Invoke C function block specifications and initializes
the user tunable run-time parameters. After this, it initializes
5-2 3BCA014034R0001 Rev. F

Monitoring the Link Status
the communication ports and begins communicating with the

PLC system.
NOTE: The RTUSLAVE does not initiate communication but instead enters a
mode where it monitors both ports for incoming command messages.
During the startup sequences, the program monitors its inter-

nal operations for the occurrence of fatal errors. Fatal errors
indicate internal module hardware, firmware or software prob-
lems that typically should never occur. Fatal errors prevent the
program from establishing communication with the PLC sys-
tem.

This utility can be used to monitor the performance of the user
interface, the GPI programs in the modules and the status of
the controllers. The outputs from GPI status blocks, as defined
in the Configuration for the current project, can be viewed
using this utility.
The Modbus RTU and Allen-Bradley screens present the
unique status block feedback and tunable block specifications
available for each interface. The information displayed on
these screens is retrieved from the module at one-second
intervals. Due to the added number of blocks to be scanned,
large PLC configurations may take a longer interval to update.
Option Startup
Before the Monitor can be started, a valid tag database must
be selected and the configuration must be either processed
(using the Process Configuration menu item) or downloaded to
the module (using the Installation to Module item).
On selection of the Monitor main menu option, the Module
Address Selection screen (Figure 5-1) will be displayed to allow
the user to select the required licensed module address.
Once the address has been entered and the Monitor button on
this screen has been clicked, the monitor screen for the cur-
rent interface (Modbus RTU or Allen-Bradley) will be dis-
played. The speed with which this screen is completely
displayed will depend on the number of PLC's, the speed of the
system and the link.
3BCA014034R0001 Rev. F 5-3

Figure 5-1. Module Address Selection Screen
Sections of the Monitor Screens

Common to both interface screens are the Module Address
and the PLC Address sections. The values displayed in the
Module Address section consist of the elements of the address
entered through the Module Address screen shown in Figure
5-1. When the program is scanning the module, the word
Updating will flash slowly in the upper left corner of this sec-
tion (refer to Figure 5-3). This indicates that the program is
requesting information from the module.
The Module Performance and Link Status sections of the
screen have slight variations for the two interfaces but provide
essentially the same information. If the time-based values in
the Module Performance section are updating, the program in
the module is running.
The Modbus RTU screen displays Link Performance Statistics
to aid in troubleshooting. In the same area of the Allen-Bradley
screen, PLC Last Retry Code, the KF status is shown for each
PLC address.
5-4 3BCA014034R0001 Rev. F

PLC addresses and status are retrieved from the blocks indi-
cated in the charts contained in each interface's section. The
addresses are retrieved only once as the screen is opened. The
status is updated along with the other values displayed on the
screen.
The tunable parameters contain the only editable fields on the
screen. Enter the new value and click on the Update button to
complete the edit. When the value has been sent to the mod-
ule, the phrase Block Specifications Updated will appear in the
centre of the bottom of the section. The initial value for each
field is displayed under the editable field as a reference and is
not updated while the screen is open.
3BCA014034R0001 Rev. F 5-5

Allen-Bradley
Figure 5-2. Allen-Bradley Monitor Screen
The following charts detail the source block outputs and spec-
ifications for each field.
Segment Control Block, Invoke C Block, PLC Address Block
Number, KF Status Block Number and Status Block Number
are the values entered in the Edit > Configuration screen.
5-6 3BCA014034R0001 Rev. F

Table 5-1. Module Performance Statistics
Field Block Number

Total Module Free Time 12
GPI Segment Cycle Time Segment Control Block
GPI Execution Time (each pass) Segment Control Block +1
Table 5-2. Link Status
Field Block Number

Active Port Status Block + 2
Terminal Port 0 Status Status Block
Printer Port 1 Status Status Block + 1
Table 5-3. PLC Last Retry Code
Field Block Number

PLC Number PLC Address Block Number + n
PLC Last Reply Status KF Status Block Number + n
Table 5-4. Device Status
Field Block Number

PLC Number PLC Address Block Number + n
PLC Status (indicated by green or red Status Block Number +3+ n
text)
3BCA014034R0001 Rev. F 5-7

Table 5-5. Tunable Parameters
Field Specification Number

Target Module Free Time Invoke C - S8
Segment Time Segment Control Block - S2
GPI Execution Time Limit Invoke C - S7
GPI Version Number or Fatal Error Invoke C output
Code
5-8 3BCA014034R0001 Rev. F

Modbus RTU
Figure 5-3. Modbus RTU Monitor Screen
The following tables detail the source block outputs and speci-
fications for each field.
3BCA014034R0001 Rev. F 5-9

Table 5-6. Module Performance Statistics
Field Block Number

Total Module Free Time 12
Module Time Used by GPI Segment Segment Control Block + 2
GPI Segment Cycle Time Segment Control Block
GPI Execution Time (each pass) Segment Control Block + 34
Table 5-7. Link Status
Field Block Number

Link Status Segment Control Block +20
Active Port Segment Control Block +23
Terminal Port 0 Status Segment Control Block +21
Printer Port 1 Status Segment Control Block +22
Table 5-8. Link Performance Statistics
Field Block Number

Read Cycle Count Segment Control Block +52
Time-out Count Segment Control Block +51
Error Reply Count Segment Control Block +53
Communication Failure Count Segment Control Block +50
Function Block Write Count Segment Control Block +56
Digital Write Count Segment Control Block +54
Analog Write Count Segment Control Block +55
Write Backlog Count Segment Control Block +57
Function Block Read Error Count Segment Control Block +32
5 - 10 3BCA014034R0001 Rev. F
GPI RTU Troubleshooting Information
Table 5-9. Device Status
Field Block Number

Number of PLC's Segment Control Block +30
PLC Number Segment Control Block +120+n
PLC Status (indicated by green or Segment Control Block +60+n
red text)
Table 5-10. Tunable Parameters
Invoke C Block
Field
Specification Number
Target Module Free Time S5
PLC Time-out Limit S6
Minimum AIP Update S4
PLC New Command Delay S8
Write Refresh Time S7
Error Log Output Enable S3 bit 0 (0=OFF, 1=ON)
PLC Command Retries S3 bits 1 - 7
GPI Version Number or Segment Control Block+10
Fatal Error Code

Initial Startup Evaluation
View the status and statistics information displays of the user
interface to determine if the interface started up successfully.
Within about 5 to 10 seconds after the target module is placed
into execute mode, is powered up or is re-started, the Link,
Port and PLC status indicators should all show Good status. If
they do not show Good status, perform the following proce-
dure.
NOTE: If only one of the two ports is designated for PLC communication, the
unused port will show Bad status.
Verify that the module did not red light. If the module red
lights, note down the LEDs that are lit. Hardware initialize the
module following the procedure described in the Module
3BCA014034R0001 Rev. F 5 - 11
Instruction manual. Refer to References in Section 1. Con-

troller modules should always be hardware initialized before
installing a new configuration. Re-load the module. If the prob-
lem persists, contact the ABB Regional Service Office.
Check for Fatal Errors

The GPI RTU logs fatal error messages to the Error Log file
(refer to Viewing Controller Module Error Log in Section 3)
and writes the corresponding error code (refer to Table 5-11) to
the Invoke C function block.
Table 5-11. RTU Fatal Errors
Code Description Action

1 Module NVM configuration file read Repeat the GPI installation
error. procedure. If the error per-
2 Dynamic memory allocation error. sists, contact the ABB
Regional Service Office.
3 Communication port initialization
error.
4 Configuration file verification error.
5 Invalid configuration data.
6 Nomenclature evaluation error.
7 Temporary License has expired.
When no fatal errors are encountered, the Invoke C output will

indicate a value representing the GPI version number as a neg-
ative value.
Example Version 2.60 will show on the Invoke C output as –2.60.
The fatal errors described are local to the GPI application and
do not red light the module.
Check the Error Log Messages

The module has not red lit and no fatal error was reported.
View the NVM error log file to determine if the module program
has reported a specific error condition. Refer to Viewing Con-
troller Module Error Log in Section 3 for information on how
to view the NVM error log messages. Appendix B contains a list
of the error messages that can be logged.
5 - 12 3BCA014034R0001 Rev. F
If the error log shows only messages relating to communica-

tion time-out and retries, then the physical and logical config-
uration of the RS-232 serial interface connection should be
verified. The following are examples of messages relating to
time-out and retry activity.
[06/20/00|02:10:30] PLC 1 TIMEOUT 2, PORT 0
[06/20/00|02:10:31] Port 1 output buffer NOT EMPTYING. Port
initialized
[06/20/00|02:10:31] -> PORT 1 OPENED @ 8b09
[06/20/00|02:10:31] Baud=9600,Stop=1,Data=8,Par=none,R/
CTS=on,Brk=off
If such messages are logged, do the following checks:
• Verify that the green LED on the termination unit

(NTMP01) or module (NIMP01) comes ON after the initial
module startup time (3 to 10 seconds depending on the
module function block size). If it does not, power down the
module and termination unit and then:
1. Verify that the NTKU01 cable is seated properly at the back

of the module and into the connector on the termination unit.
2. Check that a fuse has been installed on the termination

unit and that it is not burned out.
3. Verify that the termination unit is wired for power. Refer to

References in Section 1 for detail.
If all three items do not check out OK, try a new termination
unit (NTMP01 or NIMP01), a new cable (NTKU01), a new con-
troller module, or contact the ABB Regional Service Office.
• Check that the RS-232 cable is plugged into the appropri-

ate port and that the jumpers on the termination unit are
set properly. Refer to in Section 2 for more information.
• Verify that the PLC system connection is correct and that

the PLC system has been powered up and has been set up
appropriately for the interface.
• If interposing devices are installed in the serial connection

to the PLC system, verify that these devices have been set
up correctly. With interposing devices, the termination
jumpers must be set to meet the requirements of the inter-
3BCA014034R0001 Rev. F 5 - 13
posing device port. Refer to the Instruction manual for the

interposing device to determine its characteristics. Some
interposing devices have LEDs that give an indication that
data is being received and/or transmitted. Use these indi-
cators to determine if transmission is being blocked at an
interposing device.
• Verify the RS-232 protocol settings (baud rate, parity,

number of stop bits, number of data bits). Make sure both
the controller module GPI interface settings match the set-
tings of the PLC system port. The controller module RTU
interface settings are in the configuration data file and are
preceded by the keyword COMM= or the keyword PCOM.
Refer to User Interface in Section 4 for details. Refer to
the PLC System documentation and its maintenance facil-
ities to verify its settings.
• Connect a protocol analyzer into the physical interface at

the termination unit end to verify that command messages
are being sent from the controller module termination port.
If the protocol analyzer indicates that no command mes-

sages are being transmitted, no fatal errors are reported
and no specific error messages relating to communication
are reported in the error log, check that the program is not
inhibited via Invoke C function block input S1 or specifica-
tion S2. Both are typically set to 0. Refer to the Function
Code Application manual for detail. Contact the ABB
Regional Service Office if the problem source cannot be
determined.
If the protocol analyzer indicates that command mes-
sages are being transmitted, connect the protocol ana-
lyzer at the opposite end (or at an interposing device) to
determine if the command messages reach this location in
the connection network. If messages do reach the location,
verify that they are transmitted on the line on which data
is received by the PLC or interposing device port. If data is
being received on the wrong line, the cable may be wrong
for the current port characteristics. Some interposing
devices can be switched between DTE and DCE character-
istics and switching may allow the interposing device to
receive the data.
If there are no interposing devices installed and the data is
being received on the wrong line, the controller module ter-
5 - 14 3BCA014034R0001 Rev. F
mination jumper set J1/J2 can be changed from the DTE

to the DCE configuration, or vice versa, to transmit data on
the appropriate line for the PLC system port. Refer to
in Section 2 for more information.
If PLC communication cannot be established using the above
procedure, contact the ABB Regional Service Office.
If communication is taking place but with errors, the error log
will show messages relating to these errors. The following are
examples of communication error messages that may be
reported.
[06/20/00|02:10:30] PLC 1: ERROR REPLY 02 to CMD 03,
Addr=057C, Data=000A
[06/20/00|02:10:30] PLC 1 Status Change from GOOD to BAD,
TIMEOUTS
[06/20/00|02:10:30] PLC 1 Status Change from BAD to GOOD,
Reply OK
The first message shows that the reply error code 02 was
received for a command message with Modbus function
code 03 (Read Output Registers) to read 10 Output Registers
(hexadecimal 000A) starting at 1404 (hexadecimal 057C). The
second message shows the PLC status changing from good to
bad after the command message is unsuccessfully retried. The
third message shows the PLC status changing from bad to
good after a command transaction is successfully completed.
The above error reply code 02 indicates that the output regis-
ter address range 1404 through 1413 was all or partially
invalid for the PLC addressed. Other Modbus error reply codes
include: 01 (illegal Modbus function), 02 (illegal data address),
03 (illegal data value), 04 (failure in associated device), 05
(acknowledge), 06 (busy, rejected message), 07 (negative
acknowledge), 08 (memory parity error). These are Modicon
PLC Modbus error codes. Most Modbus interfaces apply at
least error code 01, 02 and 03 as a minimum.
All such error reply messages indicate that the PLC system can
not accept the command message that it received. The GPI
RTU software does not discriminate between error codes. The
software tries to recover from the error reply by retrying the
command transaction. If the retries are not successful, the
PLC and all associated read points (DO and AO) function
blocks are assigned bad quality.
3BCA014034R0001 Rev. F 5 - 15
Block Access Errors

The following error log messages indicate a conflict between
function blocks referenced for GPI data points in the configu-
ration data file and function blocks assigned in the function
block configuration of the module.
[06/20/00|02:10:30] BLOCK ACCESS ERROR nnn @ BLOCK
nnnn
[06/20/00|02:10:30] Boolean Bout or Exception Block nnnn is
missing or wrong type
[06/20/00|02:10:30] Analog Bout or Exception Block nnnn is
missing or wrong type
For all messages above, nnnn indicates the block number in
question. The blocks may be missing from the function block
configuration or are not the correct type of function code.
Example RTU Error Log

[ 1/ 1/84| 0: 0: 0] GPI for Modbus, ABB Inc., Rev. 1.40 Apr.
2000
[ 1/ 1/84| 0: 0: 0] Initializing
[ 1/ 1/84| 0: 0: 0] ->AUTO PORT SELECT:
[ 1/ 1/84| 0: 0: 0] 0 DRds, 64 ARds, 0 DWts, 64 AWts => 2
RdGrp, 2 WtGrp
[ 1/ 1/84| 0: 0: 0] READ GRP 0:Dev 1, Cmd 3, Addr 0 to 31
[ 1/ 1/84| 0: 0: 0] READ GRP 1:Dev 1, Cmd 3, Addr 32 to 63
[ 1/ 1/84| 0: 0: 0] EXPORT GRP 0:Dev 1, Cmd 16,Addr 0 to 31
[ 1/ 1/84| 0: 0: 0] EXPORT GRP 1:Dev 1, Cmd 16,Addr 32 to 63
[ 1/ 1/84| 0: 0: 0] NORMAL REDUNDANCY
[ 1/ 1/84| 0: 0: 0] FREE TIME TARGET=8
[ 1/ 1/84| 0: 0: 0] ->PORT 0 OPENED @ 8b09
[ 1/ 1/84| 0: 0: 0] Baud=9600,Stop=1,Data=8,Par=none,R/
CTS=on,Brk=off
[ 1/ 1/84| 0: 0: 0] ->PORT 1 OPENED @ 8b09
5 - 16 3BCA014034R0001 Rev. F
[ 1/ 1/84| 0: 0: 0] Baud=9600,Stop=1,Data=8,Par=none,R/
CTS=on,Brk=off
[ 1/ 1/84| 0: 0: 0] Initial Ports. PRIMARY is 1, BACKUP is 0
[ 1/ 1/84| 0: 0: 1] Swapping Ports. PRIMARY is 0, BACKUP is 1
[ 1/ 1/84| 0: 0: 1] 2 GRPS=>; 2 SCAN, 0 STAT
[ 1/ 1/84| 0: 0: 1] PLCTIMOUT=3000 msec
[ 1/ 1/84| 0: 0: 4] PLC 1 Status Change from START to BAD,
TIMEOUTS
[ 1/ 1/84| 0: 0: 4] FLAG_UPDATE from PLC 1 (BAD)
[ 1/ 1/84| 0: 0: 4] PLC 1 Status Change from BAD to GOOD,
(null)
[ 1/ 1/84| 0: 0: 4] FLAG_UPDATE from PLC 1 (OK)
[ 1/ 1/84| 0: 0: 4] FLAG_UPDATE to PLC 1
[ 1/ 1/84| 0: 0: 4] PORT STS: Term=GOOD, Ptr=BAD (PLC 1
Status Change from BAD to GOOD, (null))
[ 1/ 1/84| 0: 0: 4] LINK STS GOOD
Action Codes
The GPI RTU allows the user to select from a set of actions, to
be taken when a specific error code is received in response to a
Modbus message. The Modbus error codes supported are 1, 2,
3, 4, 5, 6 and 7 (Table 5-12).
Table 5-12. Modbus Error Code Definitions
Error Code Description

1 Illegal Function
2 Illegal Data Address
3 Illegal Data Value
4 Failure In Associated Device
5 Program Acknowledge
6 Busy, Rejected Message
7 NAK, Negative Acknowledge
There are a total of five action codes (refer to Table 5-13) that
can be defined (using numbers 1 to 5) to respond to any of the
3BCA014034R0001 Rev. F 5 - 17
seven error codes, with each error code having its own
response code selection. The actions are defined using a group
of function blocks, which will be defined as part of the func-
tions blocks currently used to support and provide diagnostics
for the GPI Modbus RTU protocol. These function blocks must
be offset from the INVOKE C (FC 143) by 38 and output a real
value to be accepted. These function block addresses are cur-
rently not used and are within the block addresses that are
currently used to monitor the status of the GPI link.
Typically the Manual Set Constant (FC 2) is used, as these
values should not be changed. The GPI RTU program shall
read these values only during module start-up, any changes to
these function code values will require the controller to be
restarted.
If function blocks are not defined at these offset addresses or
an entered value is not part of the defined set of action codes,
then the GPI RTU software will assume action code 1 as the
default response.
Table 5-13. Action Code Definitions
Action Code Description

1 Current handling method, after standard number of retries
set the quality of all points assigned to the PLC to Bad.
2 Ignore error reply and do not change related points quality
and do not do any retries.
3 Set group related point’s quality to Bad after standard num-
ber of retries.
4 Set group related point’s quality to Bad immediately with no
retries.
5 Set PLC and PLC related point’s quality to Bad immediately
with no retries.
5 - 18 3BCA014034R0001 Rev. F
GPI AB Troubleshooting Information
Error Code Counters

In addition to responding to these Modbus error codes based
on the Actions Codes defined by the user, the GPI RTU will
also increment a group of seven counters, with one counter
dedicated to each Modbus error code. The values of these
counters will be written to function blocks, which will be
defined as part of the group of function blocks currently used
to provide diagnostics for the GPI Modbus RTU protocol. These
function blocks must be offset from the INVOKE C (FC 143) by
180 and must be assigned to either an Analog Exception
Report (FC 30) or a C and Basic Program Real Output With
Quality (FC 137) function code.

View the status and statistics information displays of the user
interface to determine if the interface started up successfully.
Within about 5 to 10 seconds after the target module is placed
into execute mode, is powered up or is re-started, the Link,
Port and PLC status indicators should all show Good status. If
they do not show Good status, perform the following proce-
dure.
NOTE: If only one of the two ports is designated for PLC communication, the
unused port will show Bad status.
module following the procedure described in the module
instruction manual. Refer to References in Section 1. Control-
ler modules should always be hardware initialized before
3BCA014034R0001 Rev. F 5 - 19

The GPI AB logs fatal error messages to the Error Log file (refer
to Viewing Controller Module Error Log in Section 3) and
writes the corresponding error code (refer to Table 5-14) to the
Invoke C function code.
Table 5-14. AB Fatal Errors
Code Message Action

1001 Startup error 1001: Memory allocation Repeat the GPI instal-
error lation procedure. If the
1002 Startup error 1002: NVM file access error persists, contact
error the ABB Regional
Service Office.
1003 Startup error 1003: Port initialization
error
1005 Startup error 1005: Configuration
incompatible
1006 Temporary License has expired. Your Temporary
License has expired,
contact the ABB
Regional Service
Office.
When no fatal errors are encountered the Invoke C output will

indicate a value representing the GPI version number.
Example Version 3.0 will show on the Invoke C output as 3.0.
Check the Error Log Messages

View the NVM error log file to determine if the module program
has reported a specific error condition. Refer to Viewing Con-
troller Module Error Log in Section 3 for information on how
to view the NVM error log messages. Appendix C contains a list
of the error messages that can be logged.
If the error log shows only messages relating to communica-
tion time-out and retries, then the physical and logical config-
5 - 20 3BCA014034R0001 Rev. F
verified. The following are examples of messages relating to

time-out and retry activity.
[06/20/00|02:10:31] KF TO, ENQ SENT
[06/20/00|02:10:32] PLC 3 TO
[06/20/00|02:10:32] PLC 3 TO, Max Retries
[06/20/00|02:10:32] Primary port (0) Opened
If such messages are logged, do the following checks:





set properly. Refer to Setting Up the Controller Module
Termination in Section 2 for more information.
• Verify that the PLC system connection is correct and that

the PLC system has been powered up and has been set up
appropriately for the interface.

to the PLC system, verify that these devices have been set
up correctly. With interposing devices, the termination
jumpers must be set to meet the requirements of the inter-
posing device port. Refer to the Instruction manual for the
interposing device to determine its characteristics. Some
interposing devices have LEDs that give an indication that
data is being received and/or transmitted. Use these indi-
3BCA014034R0001 Rev. F 5 - 21
cators to determine if transmission is being blocked at an

interposing device.
• Verify the RS-232 protocol settings (baud rate, no parity, 1

stop bit, 8 data bits). For GPI AB, the RS-232 settings must
be no parity, 8 data bits, 1 stop bit. Make sure both the
controller module GPI interface settings match the settings
of the PLC system port. The controller module AB interface
baud rate settings are made with the Invoke C specifica-
tions (refer to Function Block Requirements in Section 3
for detail).

the termination unit end to verify that command messages
are being sent from the controller module termination port.
If the protocol analyzer indicates that no command mes-

sages are being transmitted, no fatal errors are reported
and no specific error messages relating to communication
are reported in the error log, check that the program is not
inhibited via Invoke C function block input S1 or specifica-
tion S2. Both are typically set to 0. Refer to the Function
Code Application manual for detail. Contact the ABB
Regional Service Office if the problem source cannot be
determined.
sages are being transmitted, connect the protocol ana-
lyzer at the opposite end (or at an interposing device) to
determine if the command messages reach this location in
the connection network. If messages do reach the location,
verify that they are transmitted on the line on which data
is received by the PLC or interposing device port. If data is
being received on the wrong line, the cable may be wrong
for the current port characteristics. Some interposing
devices can be switched between DTE and DCE character-
istics and switching may allow the interposing device to
receive the data.
mination jumper set J1/J2 can be changed from the DTE
to the DCE configuration, or vice versa, to transmit data on
the appropriate line for the PLC system port. Refer to
DCE/DTE Handshaking in Section 2 for more informa-
tion.
5 - 22 3BCA014034R0001 Rev. F
If PLC communication cannot be established using the above

procedure, contact the ABB Regional Service Office.
If PLC communication is established and writes to the PLC are
not occurring, check the Write Enable Block Number parameter
in the GPI Allen-Bradley Configuration menu.
If communication is taking place but with errors, the error log
will show messages relating to these errors. The following are
examples of communication error messages that may be
reported.
[06/20/00|02:10:30] Sent READ 10 02 01 00 0F 00 25 36 01
etc..
[06/20/00|02:10:30] Sent WRITE 10 02 01 00 0F 00 25 36 00
etc..
[06/20/00|02:10:30] Received dst=11 src=01 sts=50 tns=2536
ext=00
The first two messages indicate the command message that
was sent. The third message identifies the destination station
address (dst) which in a reply message must be the station
address of the Data Highway interface module (1770-KF2,
1785-KE, etc..). It further defines the PLC station address (src)
and also shows the transaction identification number (tns)
which must match the tns of the command message associ-
ated with the reply message. Lastly it shows the status code
(sts) and the extended status code (ext). An sts value of hexa-
decimal 50 indicates an addressing problem or memory pro-
tect rungs. For data communication this error typically
indicates that the PLC data file addressed by a command mes-
sage does not exist or the data reference is outside the range
(size) of the file. There are many other codes. Refer to the Data
Highway Interface Module Instruction manual for more
information.
All such error reply messages indicate that the PLC system can
not accept the command message that it received. The AB soft-
ware does not discriminate between error codes. The software
tries to recover from the error reply by retrying the command
transaction. If the retries are not successful, the PLC and all
associated read points (DOP and AOP) function blocks are
assigned Bad quality.
3BCA014034R0001 Rev. F 5 - 23
Block Access Errors

The following error log messages indicate a conflicts between
function blocks referenced for GPI data points in the configu-
ration data file and function blocks assigned in the function
block configuration of the module.
[06/20/00|02:10:30] OUT Real nnnn
[06/20/00|02:10:30] OUT Bool nnnn
[06/20/00|02:10:30] IN Real nnnn
[06/20/00|02:10:30] IN Bool nnnn
[06/20/00|02:10:30] OUT Real Exception nnnn
[06/20/00|02:10:30] OUT Bool Exception nnnn
For all messages above, nnnn indicates the block number in
question. The blocks may be missing from the function block
configuration or are the correct type of function code.Example
AB Error Log
15.697: GPI03 for AB SOFTWARE V1.4
15.844: Primary port (0) Opened
15.855: Non-Primary port (1) Opened
16.468: Port 0 GOOD
16.479: PLC 1 GOOD
16.743: PLC 2 GOOD
17.228: PLC 3 GOOD
17.738: PLC 4 GOOD
17.998: PLC 5 GOOD
18.476: PLC 6 GOOD
18.772: PLC 7 GOOD
19.291: PLC 8 GOOD
266.462: CMD
269.296: PLC 6 TO
269.463: CMD
269.469: PLC 6 TO
5 - 24 3BCA014034R0001 Rev. F
RTUSLAVE Troubleshooting Information
269.524: CMD
272.461: PLC 6 TO
272.516: CMD
272.545: PLC 6 TO
272.712: CMD
275.524: PLC 6 TO
278.711: PLC 6 TO, Max. Retries
278.719: PLC 6 BAD

View the RTUSLAVE status and Statistics Information display of
the user interface to verify that the interface started up suc-
cessfully. Within about 5 to 10 seconds after the target module
is placed into execute mode, is powered up or is re-started, the
link status indicator should show Good status. If it does not
show Good status, perform the following procedure.
module following the procedure described in the Module
Instruction manual. Refer to References in Section 1. Con-
troller modules should always be hardware initialized before

The RTUSLAVE program reports one fatal error code to the
Invoke C output.
When no fatal errors are encountered, the Invoke C output will
indicate a value representing the GPI version number.
e.g. Version 2.60 will show on the Invoke C output as 2.60.
3BCA014034R0001 Rev. F 5 - 25
Table 5-15. RTUSLAVE Fatal Errors
Code Description Action

-1 Communication port Repeat the GPI installation procedure. If the error persists,
initialization error. contact the ABB Regional Service Office.
-2 License Missing from Repeat GPI installation process. If error persists, contact
module file system. the ABB Regional Service Office
-3 License Read error Repeat GPI installation process. If error persists, contact
the ABB Regional Service Office
-4 License Checksum error Repeat GPI installation process. If error persists, contact
the ABB Regional Service Office
-5 Incorrect License Version License string used is not supported.
-6 License Expired The temporary license string has expired. Contact the ABB
Regional Service Office about puchasing a permanent
license.
Check the Status Output Blocks

View the RTUSLAVE status and statistics output blocks to
determine if the module program has reported an error condi-
tion. The program reports four indicators for the following con-
ditions:
• Communication interface status.
• Function block read errors.
• Function block write errors.
• Communication port errors.
If no communication takes place or the Communication Inter-
face status or Communication Port Errors status output
blocks indicate a problem, then the physical and logical config-
verified by doing the following checks:


5 - 26 3BCA014034R0001 Rev. F



set properly. Refer to RS-232 Communication in
Section 2 for more information.
• Verify that the Modbus Master system connection is cor-

rect and that the Modbus Master system has been powered
up and has been set up appropriately for the interface.

to the Modbus Master system, verify that these devices
have been set up correctly. With interposing devices, the
termination jumpers must be set to meet the requirements
of the interposing device port. Refer to the Instruction
manual for the interposing device to determine its charac-
teristics. Some interposing devices have LEDs that give an
indication that data is being received and/or transmitted.
Use these indicators to determine if transmission is being
blocked at an interposing device.
• Verify the RS-232 protocol settings (baud rate, parity,

number of stop bits, number of data bits). Make sure the
controller module RTUSLAVE interface settings match the
settings of the Modbus Master system port. The controller
module interface settings for RTUSLAVE are made with the
Invoke C specifications (refer to Function Block Require-
ments in Section 3 for details).

the Modbus Master system port to verify that command
messages are being sent from the Modbus Master system
port.
NOTE: For a RTUSLAVE interface all transactions are initiated from the Mod-
bus Master side. If no command messages are transmitted from the Modbus
Master end, no communication will take place. Contact the people responsible
for the Modbus Master system to determine why no transactions are initiated.
3BCA014034R0001 Rev. F 5 - 27

sages are being transmitted, and no fatal errors are
reported and no problem is reported via the status output
blocks, then continue with the next troubleshooting step.
If the protocol analyzer indicates that command messages
are being transmitted, connect the protocol analyzer at the
opposite end (or at the interposing device) to determine if
the command messages reach this location in the connect-
ing network. If messages do reach the location, verify that
they are transmitted on the line on which data is received
by the controller module termination unit port or interpos-
ing device port. If data is being received on the wrong line,
the cable may be wrong for the current port characteris-
tics. Some interposing devices can be switched between
DTE and DCE characteristics and switching may allow the
interposing device to receive the data.
mination jumper set J1, J2 or both can be changed from
the DTE to the DCE configuration, or vice versa, to receive
data on the appropriate line of the controller module termi-
nation unit port. Refer to DCE/DTE Handshaking in
Section 2 for more information.
If communication cannot be established using the above pro-
cedure, contact the ABB Regional Service Office.
If communication is taking place but problems are reported
from the status output blocks, read the following paragraphs
which include general guidance for identifying and responding
to the reported problem condition. These indicators are cleared
after 5 seconds if the problems do not persist.
1. Communication Interface Status
If the Communication Interface Status block output indi-

cates a problem (logic value 1), the module program can
not initialize the terminal or the printer port. Verify that
the NTKU01 cable between the controller module and the
termination unit (NTMP01 or NIMP01) is properly seated at
both ends. (Power down the controller module and termi-
nation unit if the cable has to be removed during the verifi-
cation process). If the cable is seated OK but the problem
5 - 28 3BCA014034R0001 Rev. F
persists, try another controller module, another NTKU01

cable or another termination unit (NTMP01 or NIMP01).
2. Function Block Access Errors
If the Function Block Access Errors block output indicates

a problem (logic value 1), then the controller module appli-
cation function block configuration does not have appro-
priate function codes at block numbers addressed by the
Modbus Master commands. The following are possible
causes:
• Modbus function 01 (Read Coil Status) and 02 (Read Input

Status). These commands serve to read multiple succes-
sive boolean output function blocks. If any blocks outputs
in the range of the read request are undefined or have
non-boolean outputs, this problem indication is set. If at
least one block in the range has a boolean output, a reply
message is sent in which the values of all undefined blocks
and all non-boolean output blocks will be boolean logic 0.
If all of the blocks referenced are either undefined or have a
non-boolean output, an error reply message is returned
with error code 02, Illegal Address.
• Modbus function 03 (Read Output Registers) and 04 (Read

Input Registers). These commands serve to read multiple
successive real output function blocks. If any blocks out-
puts in the range of the read request are undefined or have
non-real outputs, this problem indication is set. If at least
one block in the range has a real output, a reply message
is sent in which the values of all undefined blocks and all
non-real output blocks will be 16-bit integer 0. If all of the
blocks referenced are either undefined or have a non-real
output, an error reply message is returned with error code
02, Illegal Address.
• Modbus function 05 (Force Single Coil). This command

serves to write a boolean value to a single function code 45
or function code 138 block. If the block referenced is unde-
fined or is not a function code 45 or function code 138
block, this problem indication is set and an error reply
message is returned with error code 02, Illegal Address.
• Modbus function 06 (Preset Single Register). This com-

mand serves to write a register value to a single function
code 30 or function code 137 block. If the block referenced
3BCA014034R0001 Rev. F 5 - 29
is undefined or is not a function code 30 or function code

137 block, this problem indication is set and an error reply
message is returned with error code 02, Illegal Address.
• Modbus function 15 (Force Multiple Coils). This command

serves to write boolean values to multiple successive func-
tion code 45 and/or function code 138 blocks. If any
blocks in the range of the write request are undefined or
are not a function code 45 or function code 138 blocks,
this problem indication is set and an error reply message is
returned with error code 02, Illegal Address.
• Modbus function 16 (Preset Multiple Registers). This com-

mand serves to write register values to multiple successive
function code 30 and/or function code 137 blocks. If any
blocks in the range of the write request are undefined or
are not a function code 30 or function code 137 blocks,
this problem indication is set and an error reply message is
returned with error code 02, Illegal Address.
Block access errors do not inhibit the communication inter-

face. The block access error indication can only be cleared by
modifying the Controller Module Application function block
configuration to install appropriate function blocks to provide
the data access requests from the Modbus Master system or
by modifying the Modbus Master system interface requests.
3. Terminal Port Errors
This block output is set to logic value 1 after an incomplete

command message is received or a CRC error is calculated
for a command message received at the terminal port. No
reply message is returned for such received messages.
If many such errors are reported, the baud rate may be too
rapid for the physical connection. The cable length may be
too long or cable may be subject to electromagnetic inter-
ference somewhere along its length. It may be necessary to
lower the baud rate or route the cable differently. It may be
possible to upgrade the cable quality to better withstand
interference.
4. Printer Port Errors
This block output is set to logic value 1 after an incomplete

command message is received or a CRC error is calculated
5 - 30 3BCA014034R0001 Rev. F
Status & Statistics Output Blocks
for a command message received at the printer port. No

reply message is returned for such received messages.
If many such errors are reported, the baud rate may be too
rapid for the physical connection. The cable length may be
too long or cable may be subject to electromagnetic inter-
ference somewhere along its length. It may be necessary to
lower the baud rate or route the cable differently. It may be
possible to upgrade the cable quality to better withstand
interference.

Refer to Function Block Requirements in Section 3 to deter-
mine the block number associated with the status and statis-
tic output blocks.
Output Blocks for RTU

The RTU status and statistics output block numbers, defined
by the relative offset, are as defined in the Function Block
Requirements in Section 3.
Table 5-16. RTU Status & Statistic Outputs
Relative
Description
Offset
10 Invoke C block output.
Program version number (format -n.nn, e.g. -2.50 for V2.50).
or
Fatal error codes.
This output should always indicate the version number. Any other positive non-zero
value indicates that a fatal error has occurred.
1 = Configuration file open error
2 = Dynamic memory allocation error
3 = Communication port initialization error
4 = Configuration file verification error
5 = Invalid configuration data
6 = Nomenclature evaluation error
20 Link (Communication Interface) status
1 = ok, 0 = bad
This output is set to 1 (ok) as long as communication with at least 1 PLC is successful.
It is set to 0 (bad) if the program cannot communicate successfully with any PLCs.
3BCA014034R0001 Rev. F 5 - 31
Table 5-16. RTU Status & Statistic Outputs (continued)
Relative
Description
Offset
21 Port 0 (terminal port) communication status
1 = ok, 0 = bad
This output is set to OK after a successful transaction has been performed. It is set to
Bad after a transaction has failed through the initial and retry attempts.
If this port is not assigned for communication, it is assigned Bad status.
22 Port 1 (printer port) Communication status
1 = ok, 0 = bad
This output is set to OK after a successful transaction has been performed. It is set to
Bad after a transaction has failed through the initial and retry attempts.
If this port is not assigned for communication, it is assigned Bad status.
23 Current active port
0 = Terminal port, 1 = Printer port
This output indicates which port is the current primary communication port regardless
of port assignment.
30 # of PLCs referenced in the configuration.
This output indicates the number of PLCs referenced by the configuration.
31 # of PLCs with good status.
This output indicates how many of the PLCs referenced by the configuration currently
have Good status.
32 # of DIP and AIP source block read errors.
This output indicates how many DIP and AIP source function block read errors have
occurred since the module was placed into execute mode.
33 Not assigned.
34 Current cycle execution time in milliseconds.
35 Not assigned.
36 Not assigned.
37 Not assigned.
50 PLC communication failure count.
This output indicates the number of transitions from good to bad for all PLCs, accumu-
lated from module startup.
51 PLC communication time-out count.
This output indicates the total number of communication time-outs that have occurred
since the module was started up.
52 PLC read cycle count (Modbus function 1, 2, 3 or 4).
This output indicates the total number of times all read transactions have been per-
formed since the module was started up.
53 PLC error reply count.
This output indicates the total number of transaction reply errors since the module was
started up.
5 - 32 3BCA014034R0001 Rev. F
Table 5-16. RTU Status & Statistic Outputs (continued)
Relative
Description
Offset
54 PLC digital write transaction count (Modbus function 5 or 15).
This output indicates the total number of digital write transactions that have been per-
55 PLC register write transaction count (Modbus function 6 or 16).
This output indicates the total number of register write transactions that have been per-
56 DOP point destination block update count.
This output indicates the total number of DOP and AOP target function block updates
that have been performed since the module was started up.
57 DIP and AIP write backlog.
This output indicates the current backlog of DIP and AIP writes to PLC’s.
60 1st PLC status 1 = good, 0 = bad.
This output is initially set to Good. It is set to Bad after a transaction and all its retries
have failed. It is set to Good again after the first successive successful transaction.
61 2nd PLC status.
ditto
62 3rd PLC status.
ditto
63 to 109 etc.. for up to 50 PLCs.
120 1st PLC station address.
This output indicates the PLC’s Modbus node number or address as designated in the
configuration.
121 2nd PLC station address.
configuration.
122 3rd PLC station address.
configuration.
123 to etc.. for up to 50 PLCs.
169 The order of PLCs (1st PLC, 2nd PLC, etc..) is determined during the offline configura-
tion session and is the numerical order by station address. The same order applies to
the PLC status outputs above.
3BCA014034R0001 Rev. F 5 - 33
Output Blocks for AB

The AB status and statistics output block numbers are defined
in the configuration data file. Refer to Function Block
Requirements in Section 3 where they are listed by Support
Block Group.
Table 5-17. AB Status Outputs
Relative
Support Block
Block Description
Name
Offset
Invoke C Block 0 Invoke C block output.
Number Program version number (format -n.nn, e.g. -2.50 for V2.50).
or
Fatal error codes.
This output should always indicate the version number. Any other
positive non-zero value indicates that a fatal error has occurred.
1002 = Configuration file access error.
1003 = Port initialization error.
1005 = Configuration not for licensed product.
Status Block 0 KF at port 0 (terminal) status. 1 = good, 0 = bad
Number Local communication module status.
1 KF at port 1 (printer) status. 1 = good, 0 = bad
Local communication module status.
2 Current active port.
1 = (printer) port 1
0 = (terminal) port 0
3 First PLC status 1 = good, 0 = bad.
(PLC in order of station address).
4 Second PLC status 1 = good, 0 = bad
etc.. etc.. for up to 50 PLCs.
PLC Address 0 First PLC station address (0 to 254).
Block Number (PLC in order of station address).
1 Second PLC station address (0 to 254).
2 Third PLC station address (0 to 254).
3 Fourth PLC station address (0 to 254).
5 - 34 3BCA014034R0001 Rev. F
Table 5-17. AB Status Outputs (continued)
Relative
Support Block
Block Description
Name
Offset
KF Status Block These status values are from the STS and EXT field of the received reply mes-
Number sages. Refer to the Allen-Bradley Documentation for the communication inter-
face module (1770-KF2, 1785-KE etc.).
0 KF at port 0 (terminal) last reply (local) status.
1 KF at port 1 (printer) last reply (local) status.
2 First PLC last reply (remote) status.
3 Second PLC last reply (remote) status.
4 Third PLC last reply (remote) status.
3BCA014034R0001 Rev. F 5 - 35
5 - 36 3BCA014034R0001 Rev. F
GPI Database Structure Appendix A
Table A-1. ABconfig
Data Field Data Type Description

Highway Text Allen-Bradley Data Highway type (I, PCL or II).
InvokeCBlock Text Invoke C block number.
KFPort0 Text KF on terminal port data highway node number (octal).
KFPort1 Text KF on printer port data highway node number (octal).
KFRetry Text KF serial communication maximum retry count.
KFStatBlock Text Report KF/PLC status first block number.
KFTimeOut Text KF serial communication acknowledge time-out period.
ModType Text Controller module type.
Module Text Controller location module number.
PCU Text Controller location PCU number.
PLC2WriteType Text PLC-2 write command type (protected/unprotected).
PLCAddrBlock Text Report PLC data highway node number first block no.
PLCRetry Text PLC communication maximum retry count.
PLCTimeOut Text PLC communication time-out period.
Ring Text Controller location ring (loop) number.
SegmentBlock Text AB program segment block number.
SegmentNumber Text AB program segment number (0 -7).
StatusBlock Text Report Link status first block number.
WriteEnable Text Write to PLC enable block number.
Table A-2. ABdetails

Index AutoNumber Record index.
BlockType Number Program output function block type (E = exception report
block, B = Basic boolean output).
BlockNumber Text Point block number reference.
PointType Text GPI point type (AO, AI, DO, DI).
AlarmDefinition Text DO point alarm description (AL, AH or NA).
3BCA014034R0001 Rev. F A-1

Table A-2. ABdetails (continued)

NumberSystem Text Number system (octal or decimal) for specifying data
highway and PLC addresses.
PLCType Text PLC type (2=PLC-2, 3=PLC-3, 5=PLC-5, 250=PLC-5/250
or 500=SLC PLCs).
Link Number PLC Data Highway II address link number.
Node Number PLC Data Highway II address node number.
PLCnumber Number PLC Data Highway II address station number.
ModuleType Text PLC-5/250 module type (RM or LP).
ModuleNumber Number Context PLC-3 (0 - 15) or PLC-5/250 (0 - 4).
FileType Text Point data reference PLC file type.
FileNumber Number Point data reference PLC file number.
WordAddress Number Point data reference PLC file word offset.
Bit Number DO or DI point data reference PLC file word bit number (0
- 15 decimal or 0 -17 octal).
AO or AI point data reference PLC data type (8 = 8-bit
unsigned binary or BCD, 12 = 12-bit binary or BCD,
13 = unsigned long, 14 = IEEE float (using N type file),
4 = IEEE float (using true F type file), 15 = signed 16-bit
binary, 16 = unsigned 16-bit binary or BCD)
Offset Number AO or AI point data conversion offset.
Multiplier Number AO or AI point data conversion multiplier.
Tag Text Optional point tag text.
Table A-3. RTUcfg

BaudRate Text RS232 communication baud rate (1200, 2400, 4800,
9600,19200).
Parity Text RS232 communication parity (ODD, EVEN, NONE).
RTScontrol Text RS232 communication (RTS, NO-RTS).
A-2 3BCA014034R0001 Rev. F

Table A-3. RTUcfg (continued)

LinkPort Text Controller module port utilization.
AUTOMATIC = Both ports primary + Standby,
PORT0ONLY = Terminal port only,
PORT1ONLY = Printer port only,
ALTERNATE = Alternate between ports,
FOLLOWBLOCK = Get active port from block,
AUTOBOTH = Same as AUTOMATIC but send write com-
mands to both ports,
FOLLOWBOTH = Same as FOLLOWBLOCK but send
write commands to both ports.
BlkAddrOffset Text FOLLOWBLOCK port select block number.
MaxDigRdGrpiSz Text Maximum byte size for modbus functions 01 and 02 read
reply message data field. (1 - 224).
MaxAnaRdGrpiSz Text Maximum byte size for modbus functions 03 and 04 read
reply message data field. (2 - 224).
MaxWrGrpSz Text Maximum byte size for modbus functions 15 and 16 write
command message data field. (2 - 224).
RedundMod Text Redundant module switchover method (NORMAL or
BUMPLESS).
WriteCmd Text Write to PLC method (SINGLE or MULTIPLE).
Translation Text Point PLC address translation from Modbus RTU (MODI-
CON, SQD, GE-Ser5, GE-Ser6, GE-90PCM,
GE-90CMM).
Comment Text User comment text up to 28 characters.
linkPortItemNo Text Numeric coded value associated with LinkPort field.
(0=AUTOMATIC, 1=PORT0ONLY, 2=PORT1ONLY,
3=ALTERNATE,4=FOLLOWBLOCK, 5=AUTOBOTH,
6=FOLLOWBOTH)
SegBlock Text RTU program segment block number.
3BCA014034R0001 Rev. F A-3

Table A-4. RTUdetails

Index AutoNumber Record index.
PointType Text GPI point type (AOP, AIP, DOP, DIP or STATUSREG).
DigAlm Text DOP point alarm description (AL, AH, NA).
Blocknumber Number Point block number reference.
PLCnumber Number PLC Modbus node number (1 - 247).
ModbusAddress Number Point PLC data table reference (0-Digital Output table,
1 = Digital Input table, 3 = Input Register table, 4 = Output
Register table).
PointAddress Number PLC table offset (0 - 65534).
ScaleIndex Number Scaling table index (0 - 63).
DataType Text PLC point analog data type (S, FLH, FHL, LLH, LHL).
Tag Text Point tag name (up to 20 characters).
Translate Text Translated PLC point data address (address converted from
ModbusAddress/PointAddress to its Modicon, Square-D,
GE-Series6, GE-Series5, GE-Series90 with PCM or
GE-Series90 with CMM equivalent address).
Table A-5. ScaleNdx

ScaleIndex AutoNumber Record index.
Scale Factor Number Floating point scaling factor.
Offset Value Number Floating point offset value.
Signed Text PLC data type indicator (SIGNED/UNSIGNED).
A-4 3BCA014034R0001 Rev. F

GPI RTU Reference Information Appendix B
Example Configuration (.RTU) File

A text file of this format may be imported to a GPI database.
The keywords shown in bold print must exactly match. Refer
to GPI RTU Configuration Keywords Table B-1 for a very
brief explanation of each keyword.
GPI RTU REV 4.00 GPI_SEG_BLK=9000 ,MAXDOP= 500, MAXAOP= 200

OPTIONS:USER BLOCKS,COMM=101 ,PORT=1,FOLLOW=1000,GROUPWRITE,
TARGET: LOOP 0, PCU 0, MODULE 3, DCSBAUD 9600, MODULETYPE MFP03
RDDIGRPSIZ=224, RDANGRPSIZ=224, WRITEGRPSIZ=100, BUMPLESS
TRANSLATION: NONE
;COMMENT:Test DOP alarming facility
0: SCALE FACTOR=1.000000 , OFFSET VALUE=0.000000 , UNSIGNED

2: SCALE FACTOR=1.000000 , OFFSET VALUE=0.000000 , SIGNED
3: SCALE FACTOR=1.000000 , OFFSET VALUE=0.000000 , SIGNED
" """"" "
1:DOPAL ,BLK=1000 ,PLC PT= 1,0, 100 ,TAG>TAG DOP 1 <
2:DOPAH ,BLK=1001 ,PLC PT= 1,0, 101 ,TAG>TAG DOP 2 <
3:DIP ,BLK=2000 ,PLC PT= 1,0, 100 ,TAG>TAG DIP 3 <
4:AOP ,BLK=3000 ,PLC PT= 1,4, 0 ,SCALE_INDEX=0, TAG>TAG AOP 4 <
5:AIP ,BLK=4000 ,PLC PT= 1,4, 0 ,SCALE_INDEX=0, TAG>TAG AIP 5 <
6:STAT ,BLK=5000 ,PLC 1, STATUS REG=11,TAG>TAG STAT 6 <
7:DOPAL ,BLK=1002 ,PLC PT= 1,0, 102 ,TAG>TAG DOP 7 <
8:DOPAH ,BLK=1003 ,PLC PT= 1,0, 103 ,TAG>TAG DOP 8 <
@END@
Figure B-1. Configuration (.RTU) Example
3BCA014034R0001 Rev. F B-1

GPI RTU Configuration Keywords

Table B-1. Keyword Descriptions
KEYWORD DESCRIPTION
BLK= The function block receiving or sourcing the point value.
BLOCKWRITE Configuration text file to be compiled for MULTIPLE point write run-time
module program (refer to SINGLEWRITE).
BUMPLESS Redundant module switchover without initial re-writing of all DIP and AIP
point values to PLCs (refer to NORMAL).
COMM= Module port communication option word (a hex value, e.g. 101).
NOTE: Need ‘COMM=’ entry or ‘PCOM(’ entry).
DCSBAUD No longer applicable under Composer.

User interface serial communication baud rate.
FOLLOW= Block number of a boolean output function block which specifies the port
selection at its output. (0 = Terminal port, 1 = Printer port).
(refer to PORT=)
GPI_SEG_BLK The GPI module segment block number.
LOOP Target module LOOP number.
MODULE Target module MODULE number.
MODULETYPE Specifies target module type when followed by one of MFP02, MFP03,
BRC100, BRC200, BRC300, BRC400 or HAC01.
NORMAL Redundant module switchover with initial re-writing of all DIP and AIP point
values to PLCs. This is the default selection (refer to BUMPLESS).
OFFSET VALUE= Register/Float conversion coefficients: zero offset (refer to SCALE
FACTOR= and SIGNED and UNSIGNED).
OPTIONS: Defines line on which communication options are specified
(refer to COMM=, PCOM(, PORT=, FOLLOW=, SINGLEWRITE and
BLOCKWRITE).
PCOM( Module port communication parameters. Allows parameters to be set in
human recognizable form as in the following format:
PCOM(BAUD PARITY RTS)
where: BAUD = 1200, 2400, 4800, 9600 (default) or 19200
PARITY = ODD, EVEN or NONE (default)
RTS = RTS or NO_RTS (default)
NOTE: Need COMM= entry or ‘PCOM(‘ entry).
PCU Target module PCU number.

PLC PLC node number associated with status register read.
B-2 3BCA014034R0001 Rev. F

Table B-1. Keyword Descriptions (continued)
KEYWORD DESCRIPTION
PLC PT= The PLC point address consisting of three fields separated by commas (,):
Node number (typically 1 to 247).
Table of file reference.
(0=coils, 1=Digital Inputs, 3=Output Registers, 4=input registers).
Table or file offset (range 0 through 65534).
PORT= Module port selection
0 = AutoSelect, 1 = Port 0 (Terminal port) only,
2 = Port 1 (Printer port) only, 3 = Alternate Ports, 4 = Follow Block,
5 = Write Both, 6 = Follow Both
RDANGRPSIZ Analog read group transaction reply data field maximum size in bytes.
Two bytes = one register value (default and maximum is 224).
RDDIGRPSIZ Digital read group transaction reply data field maximum size in bytes.
One byte = eight consecutive digital (bit) values
(default and maximum is 224).
SCALE FACTOR= Register/Float conversion coefficients: scale factor (multiplier) (refer to
OFFSET VALUE and SIGNED and UNSIGNED).
SCALE_INDEX= Scale index to reference one of the Register/Float conversion coefficient
sets (SCALE FACTOR, OFFSET VALUE, SIGNED and UNSIGNED).
Range 0 through 63 (64 sets).
SIGNED Handle register value as a signed integer (refer to UNSIGNED).
SINGLEWRITE Configuration text file to be compiled for SINGLE point write module’s
run-time program (refer to BLOCKWRITE).
STATUS REG= Status register number identifying the status register to be read. Range 1
through 9 and 11.
- 1 through 9 applies Modbus function 8, diagnostic codes 11 through 19.
- 11 applies Modbus function 11 to read the Communications Events
Counter.
TAG A tag name text string (length 0 to 24 chars).
TARGET: Defines line on which the target module location and module type are
specified (refer to LOOP, PCU, MODULE and MODULETYPE).
3BCA014034R0001 Rev. F B-3

Table B-1. Keyword Descriptions (continued)
KEYWORD DESCRIPTION
TRANSLATION: Specifies RTU address translation in the user interface when followed by
one of NONE, MODICON, SQD, GE6, GE5, GE90PCM or GE90CMM.
where:
NONE = No translation
MODICON = Modicon PLCs
SQD = Square D PLCs
GE6 = GE Series 6 PLCs
GE5 = GE Series 5 PLCs
GE90PCM = GE Series 90 PLCs with PCM interface
GE90CMM = GE Series 90 PLCs with CMM interface
NOTE: The translation serves only to display the address in the PLC’s format on the user inter-
face. The translated address is not used in binary data file downloaded to the target module.
UNSIGNED Handle register value as an unsigned integer (refer to SIGNED).

USER BLOCKS No longer applicable.
All blocks defined in the user application function block configuration. The
previous facility to have program support and output function blocks
installed by GPI02 and not defined in the user application function block
configuration is no longer supported.
WRITEGRPSIZ Write group transaction command data field maximum size in bytes.
Two bytes = one register value.
One byte = eight consecutive digital (bit) values
(default and maximum is 100)
:AIP Analog point written to a PLC.
:AOP Analog point read from a PLC.
:DIP Digital point written to a PLC.
:DOP Digital point read from a PLC with no alarming.
:DOPAH Digital point read from a PLC with alarming on logic 1.
:DOPAL Digital point read from a PLC with alarming on logic 0.
:DOPNA Digital point read from a PLC with no alarming.
:STAT Status register read from a PLC.
;COMMENT: Optional comment field for the configuration.
B-4 3BCA014034R0001 Rev. F

GPI RTU NVM Error File Messages

Table B-2. Error File Message and Description
Message Description
“[mm/dd/yy|hh:mm:ss] message” The date and time pre-fix added to each message
logged.
“GPI for Modbus, ABB Inc., Rev. n.nn Product identification message showing revision n.nn
mmm yyyy” and revision data month mmm and year yyyy.
“FREE TIME TARGET=nn %” Current target free time setting as nn %.
“FIXED intime=nnn” Current intime setting as nnn msec.
“PLCTIMOUT=nnnn msec” Current communication time-out setting as nnnn
msec.
“REFRESH RATE=nnn Sec” Current refresh rate setting as nnn seconds.
“Max Update Rate=nnn” Current max update rate setting as nnn segment
cycles.
“INITIAL REFRESH INHIBIT Bumpless refresh inhibited indication.
FLAGGED”
“Initializing” Initializing from NVM configuration file.
“File open err” NVM configuration file open error.
“File read err” NVM configuration file read error.
“Nomenclature mismatch” License Product, Module or Capacity mismatch.
"->PORT 0 ONLY:" Communication on port 0 (terminal) only selected.
"->PORT 1 ONLY:" Communication on port 1 (printer) only selected.
"->ALTERNATING PORTS:" Alternate communication between ports with each
transaction selected.
"->AUTO PORT SELECT:" Automatic primary port selection. Non-selected port
serves as standby port.
"->AUTO PORT-WRITE BOTH:" Automatic primary port selection. Non-selected port
serves as standby port. Write transaction performed
on both ports.
"->PORT FOLLOWS BLOCK nnnn:" Communication port selected by block number nnnn.
"->PORT FOLLOWS BLOCK Communication port selected by block number nnnn.
nnnn-WRITE BOTH:" Write transaction performed on both ports.
"Memory alloc err" Fatal memory allocation error.
"Write Grps init err" Write group initialization error.
3BCA014034R0001 Rev. F B-5

Table B-2. Error File Message and Description (continued)
Message Description
"ann DRds, bnn ARds, cnn DWts, Configuration has ann Digital Read (DOP) points,
dnn AWts => m RdGrp, k WtGrp" bnn Analog Read (AOP) points, cnn Digital Write
(DIP) points and dnn Analog Write (AIP) points. The
points are allocated to m Read groups and k Write
groups.
"READ GRP n:Dev nnn, Cmd cc, n’th read group, addresses device nnn using read
Addr xxxx to yyyy" command cc to read data points xxxx through yyyy.
"READ GRP n:Dev nnn, Cmd 08, Sta- n’th read group, addresses device nnn using com-
tus Reg. Diagnostic Code dd" mand 08 serves to read one status register identified
by diagnostic code dd.
"READ GRP n:Dev nnn, Cmd 11, Sta- n’th read group, addresses device nnn using com-
tus Reg. Comm Event Counter" mand 11 serves to read the device Communication
Event Counter.
"EXPORT GRP n:Dev nnn, Cmd cc, n’th write group, addresses device nnn using write
Addr xxxx to yyyy" command cc to write to data points xxxx through
yyyy.
"BUMPLESS REDUNDANCY" Bumpless redundant module switchover selected. All
write points (DIP and AIP) are not automatically
re-written to devices after a module switchover.
"NORMAL REDUNDANCY" Non-bumpless redundant module switchover
selected. All write points (DIP and AIP) are automat-
ically re-written to devices after a module switchover.
"Initial Ports. PRIMARY is 1, Ports initialized. Port 1 (printer) is primary and port 0
BACKUP is 0" (terminal) is backup port.
"DEBUG ON" Error message output to the non-primary port is
enabled. Can be applied if the port usage is set to
communicate on either port 0 or port 1 only.
"DEBUG OFF" Error message output to the non-primary port is dis-
abled.
B-6 3BCA014034R0001 Rev. F

Message Description
"PLC nnn Status Change from Reports a PLC device status. Reason very briefly
START to GOOD, reason" describes why the status change took place.
"PLC nnn Status Change from START is the status assigned at startup. TRY is the
START to BAD, reason" status assigned when a device with BAD status is
"PLC nnn Status Change from GOOD being re-tried.
to BAD, reason"
"PLC nnn Status Change from BAD
to TRY, reason"
"PLC nnn Status Change from TRY to
GOOD, reason"
"PLC nnn Status Change from TRY to
BAD, reason"
"LINK STS GOOD" Link (interface connection) status change to GOOD.
"LINK STS BAD" Link (interface connection) status change to BAD.
"Swapping Ports. PRIMARY is 0, The primary port selection changed from port 1
BACKUP is 1" (printer) port to 0 (terminal) port. Port swapping is
applied when the port usage is set to AUTO-
PORT-SELECT or AUTOPORT-WRITEBOTH only.
"PORT STS: Term=GOOD, Ptr=BAD Port status change report (explanation) very briefly
(explanation)" describes why the status change took place.
"->PORT n OPENED @ xxxx" Port opened with option value xxxx.
"Baud=bbbb,Stop=s,Data=d,Par=ppp xxxx breaks down as follows:

p,R/CTS=ooo,Brk=ooo" Baud rate bbbb, s stop bits, d data bits, parity of
pppp, RTS/CTS handshaking set ooo and the break
enable set ooo.
s = 1 or 2
d = 7 or 8
pppp =NONE, EVEN, ODD, LOW or HIGH
ooo = ON or OFF
"Receiving invalid data from PLC Reports that invalid data is being received from
nnn. CMD cc, Addr=xxxx" device nnn using command cc targeting data
address xxxx. This data cannot be processed and is
being dumped.
3BCA014034R0001 Rev. F B-7

Message Description
"PLC nnn: ERROR REPLY nn to Received an error reply from device nnn, transaction
CMD cc,Addr=xxxx,Data=aaaa" command cc, data address xxxx, data aaaa. For read
commands (cc = 01, 02, 03 or 04), aaaa is the num-
ber of data items being read. For single value write
commands (cc = 05 or 06), aaaa is the value being
written. For group write commands (cc = 15 or 16),
aaaa is the number of data items being written.
"TP:GRP n DATA LENGTH ERROR Group read reply error. aaa is the number of bytes
(aaa),max eee" received. eee is the number of bytes expected.
" TP:->reply=>xx xx xx xx" xx xx xx xx lists the first four bytes of the reply.
" PLC nnn TIMEOUT m, PORT n" Transaction with device nnn experienced the m’th
time-out on port n.
"Port n output buffer NOT EMPTY- The port output buffer is not emptying and will be ini-
ING. Port initialized" tialized. This typically means that transmission is
inhibited by the incoming CTS line. Verify the termi-
nation unit jumper settings. Make sure that the CTS
line allows transmission either by the external device
or RTS/CTS loop back on the termination unit jump-
ers, the cable or an interposing device (e.g. modem).
"Send to port n FAILED" Send command message port n failed.
“Backup port n WRITE ERROR. Port A backup port n write error occurred. The port will be
initialized.” initialized.
"nn GRPS=>; mm SCAN, ss STAT" Reports that the configuration has nn read groups
consisting of mm data point read groups and ss sta-
tus register reads.
"BLOCK ACCESS ERROR nnn @ Reports block access error # nnn for block # nnnn.
BLOCK nnnn"
"FLAG_UPDATE to PLC nnn" Reports flagging of all write points associated with
device nnn for updating to device. This is typically in
response to the PLC’s status change.
"FLAG_UPDATE from PLC nnn (ssss)" Reports flagging of all read points associated with
device nnn for updating to blocks. This is typically in
"Boolean Bout or Exception Block Report a boolean block nnnn access error.
nnnn is missing or wrong type."
"Analog Bout or Exception Block Report a analog block nnnn access error.
nnnn is missing or wrong type."
B-8 3BCA014034R0001 Rev. F

Message Description
"TP:WRITE GRP nn DATA LENGTH Write group transaction reply size error. Received
ERROR (aaa),max eee" aaa reply bytes. Expected eee bytes.
" TP:->reply=>xx xx xx xx" xx xx xx xx lists the first four bytes of the reply.
"FLAG_UPDATE to PLC nnn" Reports flagging of all write points associated with
device nnn for updating to device. This is typically in
"[mm/dd/yy|hh:mm:ss] message" The date and time pre-fix added to each message
logged.
3BCA014034R0001 Rev. F B-9

3BCA014034R0001 Rev. F
GPI AB Reference Information Appendix C
Example Configuration (.AB) File

GPI DTA V3.00
Licenced to: INTERNAL ABB COPY

NOT FOR CUSTOMER RELEASE
GPI AB V3.00
File Name: E:\GPI AB\VER300\TEST\1EACH.AB

Save Date and Time: 05/10/99 09:16:45
Number of PLC's = 1
number of Points = 4
Global Link Parmeters
{GLOBAL} HIGHWAY = I or PCL

{GLOBAL} KFPORT0 = 0 (octal)
{GLOBAL} KFPORT1 = 0 (octal)
{GLOBAL} KFTIMEOUT = 3000
{GLOBAL} KFRETRY = 3
{GLOBAL} PLCTIMEOUT = 3000
{GLOBAL} PLCRETRY = 3
{GLOBAL} PLC2WRITETYPE = U
{GLOBAL} SEGMENTNUMBER = 0
{GLOBAL} SEGMENTBLOCK = 15
{GLOBAL} INVOKECBBLOCK = 30
{GLOBAL} STATUSBLOCK = 0
{GLOBAL} PLCADDRRBOCK = 0
{GLOBAL} KFSTATBLOCK = 0
{GLOBAL} WRITEENABLE = 0
{GLOBAL} RING = 0
{GLOBAL} PCU = 0
{GLOBAL} MODULE = 3
{GLOBAL} MODTYPE = MFP02
The PLC definitions
{PLC} PLC5 0 0 1
Index Block PT AD NS PLC link node PLC# Mod Cnt FT F# Addr Bit offset multiplier
{POINT} 1 E1000 DO AH D PLC5 0 0 1 NA 0 B 7 0 0 0.000000e+000 0.000000e+000
{POINT} 2 E2000 DI NA D PLC5 0 0 1 NA 0 B 7 0 0 0.000000e+000 0.000000e+000
{POINT} 3 E3000 AO NA D PLC5 0 0 1 NA 0 F 9 0 14 0.000000e+000 1.000000e+000
{POINT} 4 E4000 AI NA D PLC5 0 0 1 NA 0 F 9 0 14 0.000000e+000 1.000000e+000
3BCA014034R0001 Rev. F C-1

GPI AB Configuration Keywords
A text file of this format may be imported to a GPI database.

The keywords shown in bold print must exactly match. Refer
to GPI AB Configuration Keywords for a very brief explana-
tion of each key word.
Table C-1. Keyword Descriptions
KEYWORD DESCRIPTION
{GLOBAL} Begins a line containing a definition that applies to the entire configura-
tion.
HIGHWAY Defines communication to be with an Allen-Bradley I (Data Highway,
PCL or DH485) or II (Data Highway II).
KFPORT0 Defines the station number of the communication adapter connected to
the terminal port.
KFPORT1 Defines the station number of the communication adapter connected to
the printer port.
KFTIMEOUT The communication adapter time-out period in milliseconds.
Typically 1000 to 3000 milliseconds.
KFRETRY The number of retries to be applied to attempt communication with the
adapter.
Typically 1 to 3 retries.
PLCTIMEOUT The PLC reply time-out period in milliseconds.
Typically 1000 to 3000 milliseconds.
PLCRETRY The number of retries to be applied to attempt communication with the
target PLC.
Typically 1 to 3 retries.
PLC2WRITETYPE Define use of unprotected (U) or protected (P) write commands to
PLC02 devices.
SEGMENTNUMBER Define the module segment number (0 to 7) from which the GPI run-time
program will be invoked.
SEGMENTBLOCK The block number of the Segment Control function block for the segment
from which the GPI run-time program will be invoked.
INVOKECBLOCK The Invoke C function block number.
STATUSBLOCK Defines the first of four or more function code 138 output blocks that will
represent the communication status of the PLCs and communication
adapters.
PLCADDRBLOCK Defines the first of four or more function code 137 output blocks that will
represent the number of PLCs referenced in the configuration file and
the station address of each PLC.
C-2 3BCA014034R0001 Rev. F

Table C-1. Keyword Descriptions (continued)
KEYWORD DESCRIPTION
KFSTATBLOCK Defines the first of four or more function code 137 output blocks that will
represent the last status value received from the communication adapt-
ers for each PLC.
WRITEENABLE GPI AB write enable block number.
RING Controller module location ring number.
PCU Controller module location PCU number.
MODULE Controller module location module number.
MODTYPE Controller module type into which the GPI AB is to be installed.
{PLC} Begins a line that defines a PLC referenced in the configuration file.
PLC2 Defines a PLC02.
PLC525 Defines a PLC05/250.
SLC500 Defines a SLC05/01/02/03/04 PLC.
{POINT} Begins a line on which a point=to=point connection between an Asea
Brown Boveri Inc. function block and a PLC data point is defined. Each
line has multiple fields shown under a header line in the example above.
Each of the fields is described next.
Index The header for column listing the configuration text file point indices.
Block The header for column listing the function block number associated with
the GPI AB points.
PT The header for column listing the point type. Digital input from a PLC
(DO), digital output to a PLC (DI), analog input from a PLC (AO) or ana-
log output to a PLC (AI).
AD The header for column listing the alarm description for DO point type.
Alarm on High (AH), Alarm on Low (AL) or No Alarming (NA).
NS The header for column listing the numeric system in which the PLC point
address will be stated. Decimal (D) or Octal (O).
PLC The header for column listing the PLC type. 2=PLC02, 3=PLC03,
5=PLC05, 250=PLC05/250, 500=SLC05/01/02/03/04.
Link The header for column listing the Data Highway II link number. Make 0
for non-Data Highway II.
Node The header for column listing the Data Highway II node. Make 0 for
non-Data Highway II.
PLC# The header for column listing the Data Highway II user number or Data
Highway/Data Highway Plus/DH485 Station number.
Mod The header for column listing the module on PLC05/250.
3BCA014034R0001 Rev. F C-3

GPI AB NVM Error File Messages
Table C-1. Keyword Descriptions (continued)
KEYWORD DESCRIPTION
Cnt The header for column listing the context on PLC03 and PLC05/250
(Make 0 for other PLC types).
FT The header for column listing the file type (make 0 for PLC02).
F# The header for column listing the file number (make 0 for PLC02).
Addr The header for column listing the file word number (offset). Word
address for PLC02. Specify in decimal or octal depending on the
numeric system.
Bit The header for column listing the word bit number for digital point refer-
ences. For analog type data, this parameter defines the analog data type
as 8-bit (8), 12-bit (12), unsigned long 32-bit (13), IEEE float 32-bit (14)
(using N-Type file), IEEE float 32-bit (4) (using F-Type file), unsigned
16-bit (15) or signed 16-bit (16).
Offset The header for column listing the AO or AI point conversion coefficient
offset. Make 0 for DO and DI points.
Multiplier The header for column listing the AO or AI point conversion coefficient
multiplier. Make 0 for DO and DI points.
Tag The header for column listing the point tag text (up to 28 characters). Not
shown in the example because of page space. Follows after the multi-
plier field to define a tag name enclosed between the characters > and <.
e.g. “>FEEDPMP2-INL-PRS<”

Table C-2. Error File Messages
Message Description
"[mm/dd/yy|hh:mm:ss] message" The date and time pre-fix added to each message
logged.
"GPI03 for AB SOFTWARE V.xx" Reports the single write software ID and version.
"GPI03BW for AB SOFTWARE V.xx" Reports the block write software ID and version.
"Not Enough Module Free Time for Reports that the software has insufficient time to per-
GPI03 to Run!" form all configured (scheduled) functions.
This message may occasionally occur at start up. It
should never occur during normal running of the soft-
ware.
"Startup error 1001: Memory alloca- Fatal startup error.
tion error"
C-4 3BCA014034R0001 Rev. F

Message Description
" Startup error 1002: NVM file Fatal startup error while reading the configuration
access error" file.
" Startup error 1003: Port initializa- Fatal error while initializing communication ports.
tion error"
" Startup error 1005: Configuration Fatal startup error. The configuration file data is not
incompatible" compatible with the licensed software, controller
module or point capacity.
"Port n Error" Fatal error. Port n open error.
"Primary port (n) Opened" Primary port n opened successfully.
"Non-Primary port (n) Opened" Non-primary port n opened successfully.
"PLC nnn TRY" Failed PLC being re-tried every 5 seconds.
"PLC nnn ssss" Reports PLC nnn status change to status ssss.
"PLCs BAD" The status of all PLCs has been set to BAD.
"Port n ssss" Reports port n status change to status ssss.
"NAK" Reports receiving a NAK reply.
"Sent READ xx xx xx xx xx xx xx xx xx Reports bytes of read command sent.
xx xx xx"
"Sent WRITE xx xx xx xx xx xx xx xx xx Reports bytes of write command sent.
xx xx xx"
"Received dst=oo src=oo sts=xx Reports the 3rd and 4th and 6th through 9th bytes of
tns=xxxx ext=xx" reply message received for a DH or DH+ device. The
bytes should represent DST SRC STS TNS1 TNS2
and EXT bytes of the reply message. The DST and
SRC bytes are in octal. The remainder are in hexa-
decimal.
"Received link=ooo node=ooo Reports the 5th through 7th and 9th through 12th
user=ooo sts=xx tns=xx xx ext=xx" bytes of reply message received for a DH II device.
The bytes should represent link node user STS
TNS1 TNS2 and EXT of the reply message. The link,
node and user bytes are in octal. The remainder are
in hexadecimal.
"KF TO, ENQ SENT" Reports that no ACK was received from the commu-
nication adapter (KF) during the time-out interval and
that an ENQ was sent to request the acknowledge-
ment.
"PLC nnn TO" Reports that no reply was received from PLC nnn
during the time-out interval. The command will be
re-tried.
3BCA014034R0001 Rev. F C-5

Message Description
"PLC nnn TO, Max. Retries" Reports that no reply was received from PLC nnn
after re-tries. The PLC will be assigned BAD status.
"Serial error" A serial communication error occurred, probably
because the port buffer is full or a port error
occurred. Cannot send a command. Will switch to
the other port immediately if both ports are assigned
for communication.
"Send Timeout" No command message sent in last 20 seconds.
Serial communication problems.
"BCC" Reports a checksum error.
"Reply long" Reports that a received reply message is too long.
"TNS" Reports that the TNS of a reply message does not
match the TNS of any outstanding (expected) reply.
Usually means that a reply message is received after
the time-out interval and the outstanding TNS has
been cleared.
"CMD" Reply message has an invalid command (CMD).
"OUT Real nnnn" Reports problem writing to Basic real output block
nnnn for updating an AO point.
"OUT Bool nnnn" Reports problem writing to Basic boolean output
block nnnn for updating a DO point.
"IN Real nnnn" Reports problem reading real output block nnnn for a
AI point.
"IN Bool nnnn" Reports problem reading boolean output block nnnn
for a DI point.
"OUT Real Exception nnnn" Reports problem writing to real exception report
block nnnn for updating an AO point.
"OUT Bool Exception nnnn" Reports problem writing to boolean exception report
block nnnn for updating a DO point.
C-6 3BCA014034R0001 Rev. F

RS-232 Appendix D
Cable Configurations
Figure D-1. Standard Cable L700550A1 Layout
3BCA014034R0001 Rev. F D-1

Figure D-4. Standard Cable L700579M12 Layout
D-2 3BCA014034R0001 Rev. F

Figure D-5. Standard Cable L700579E5 Layout
Figure D-6. Standard Cable L700579M12 Layout
Figure D-7. Standard Cable L700579E4 Layout
3BCA014034R0001 Rev. F D-3

Figure D-8. Standard Cable L700579K10 Layout
D-4 3BCA014034R0001 Rev. F

Example License String Appendix E
Document
GPI Software Keys Issued
Software Order Number: GPI SO Number
Customer: GPI Customer
License File: SGPI070417.txt
Date Issued: 12/04/2007 11:32:17 AM
The software described below is licensed to the End User based on the
ABB Inc. Terms and Conditions for software.
License String Ver S/N Features
XXXXXXXXXXX 3.0 SGPI070417 Modbus RTU, BRC400,

Single, 1500 Points
Figure E-1. License String Example
3BCA014034R0001 Rev. F E-1

3BCA014034R0001 Rev. F
Example GPI RTU Review Appendix F
Output File
Thu Nov 29 15:27:51 2007 *** GPI02 CONFIGURATION PROCESSING

ERROR REVIEW for GPI02_500rtu ***
Thu Nov 29 15:27:51 2007 *** END OF GPI02 CONFIGURATION

PROCESSING ERROR REVIEW ***
Thu Nov 29 15:27:51 2007 <<<<<<< REVIEW OF CONFIGURATION FILE

GPI02_500rtu >>>>>>>
GPI Modbus Version 3.0, Module type BRC300, Capacity 500.

Configuration Specifies: Module type BRC300.
Write Mode = Block Writes.
Redundant module switchover mode specified is BUMPLESS.
The specified GPI module Segment Control block number is 9000.
This places the Invoke C block at block number 9010.
Starts the Link Status & Port Selection blocks at block number
9020.
Starts the Link Performance Output blocks at block number 9030.
Starts the GPI Statistic Output blocks at block number 9050.
Starts the PLC Status blocks at block number 9060.
Starts the PLC Node Address blocks at block number 9120.
Total Number of points in the configuration is 500.
Number of Read Points is 250. Digital 125, Analog 125.
Number of Write Points is 2 5 0 . Di gital 5, Analog 125.
Number of PLCs referenced is 1.
Comm Opts (8c09): Comm Opts:19200 Baud, NO Parity,8 bits,1 stop,
no RTS-CTS.rt Select Opts:AUTO PORT SELECT.
The address translation key is set to NONE.
----- LIST OF PLCS REFERENCED IN THE CONFIGURATION -----

PLC Node 1.
Number of Read groups = 3. Number of Write groups = 4.

Maximum Read Transaction Data Field Size (bytes): Digtal = 224,
Analog = 224.
Maximum Write Transaction Data Field Size = 100 bytes.
----- LIST OF SORTED DIGITAL READ (DOP) POINTS -----

Index PtType Block PLC DataTable PointAddress
1 DOPNA 1000 1 DI 0
5 DOPNA 1001 1 DI 1
9 DOPNA 1002 1 DI 2
13 DOPNA 1003 1 DI 3
17 DOPNA 1004 1 DI 4
21 DOPNA 1005 1 DI 5
25 DOPNA 1006 1 DI 6
29 DOPNA 1007 1 DI 7
33 DOPNA 1008 1 DI 8
37 DOPNA 1009 1 DI 9
41 DOPNA 1010 1 DI 10
3BCA014034R0001 Rev. F F-1

45 DOPNA 1011 1 DI 11
49 DOPNA 1012 1 DI 12
53 DOPNA 1013 1 DI 13
57 DOPNA 1014 1 DI 14
61 DOPNA 1015 1 DI 15
65 DOPNA 1016 1 DI 16
69 DOPNA 1017 1 DI 17
73 DOPNA 1018 1 DI 18
77 DOPNA 1019 1 DI 19
81 DOPNA 1020 1 DI 20
85 DOPNA 1021 1 DI 21
89 DOPNA 1022 1 DI 22
93 DOPNA 1023 1 DI 23
97 DOPNA 1024 1 DI 24
101 DOPNA 1025 1 DI 25
105 DOPNA 1026 1 DI 26
109 DOPNA 1027 1 DI 27
113 DOPNA 1028 1 DI 28
117 DOPNA 1029 1 DI 29
121 DOPNA 1030 1 DI 30
125 DOPNA 1031 1 DI 31
129 DOPNA 1032 1 DI 32
133 DOPNA 1033 1 DI 33
137 DOPNA 1034 1 DI 34
141 DOPNA 1035 1 DIDI 35 35
145 DOPNA 1036 1 DI 36
149 DOPNA 1037 1 DI 37
153 DOPNA 1038 1 DI 38
157 DOPNA 1039 1 DI 39
161 DOPNA 1040 1 DI 40
165 DOPNA 1041 1 DI 41
169 DOPNA 1042 1 DI 42
173 DOPNA 1043 1 DI 43
177 DOPNA 1044 1 DI 44
181 DOPNA 1045 1 DI 45
185 DOPNA 1046 1 DI 46
189 DOPNA 1047 1 DI 47
193 DOPNA 1048 1 DI 48
197 DOPNA 1049 1 DI 49
201 DOPNA 1050 1 DI 50
205 DOPNA 1051 1 DI 51
209 DOPNA 1052 1 DI 52
213 DOPNA 1053 1 DI 53
217 DOPNA 1054 1 DI 54
221 DOPNA 1055 1 DI 55
225 DOPNA 1056 1 DI 56
229 DOPNA 1057 1 DI 57
233 DOPNA 1058 1 DI 58
237 DOPNA 1059 1 DI 59
241 DOPNA 1060 1 DI 60
245 DOPNA 1061 1 DI 61
249 DOPNA 1062 1 DI 62
253 DOPNA 1063 1 DI 63
257 DOPNA 1064 1 DI 64
261 DOPNA 1065 1 DI 65
265 DOPNA 1066 1 DI 66
269 DOPNA 1067 1 DI 67
F-2 3BCA014034R0001 Rev. F

273 DOPNA 1068 1 DI 68
277 DOPNA 1069 1 DI 69
281 DOPNA 1070 1 DI 70
285 DOPNA 1071 1 DI 71
289 DOPNA 1072 1 DI 72
293 DOPNA 1073 1 DI 73
297 DOPNA 1074 1 DI 74
301 DOPNA 1075 1 DI 75
305 DOPNA 1076 1 DI 76
309 DOPNA 1077 1 DI 77
313 DOPNA 1078 1 DI 78
317 DOPNA 1079 1 DI 79
321 DOPNA 1080 1 DI 80
325 DOPNA 1081 1 DI 81
329 DOPNA 1082 1 DI 82
333 DOPNA 1083 1 DI 83
337 DOPNA 1084 1 DI 84
341 DOPNA 1085 1 DI 85
345 DOPNA 1086 1 DI 86
349 DOPNA 1087 1 DI 87
353 DOPNA 1088 1 DI 88
357 DOPNA 1089 1 DI 89
361 DOPNA 1090 1 DI 90
365 DOPNA 1091 1 DI 91
369 DOPNA 1092 1 DI 92
373 DOPNA 1093 1 DI 93
377 DOPNA 1094 1 DI 94
381 DOPNA 1095 1 DI 95
385 DOPNA 1096 1 DI 96
389 DOPNA 1097 1 DI 97
393 DOPNA 1098 1 DI 98
397 DOPNA 1099 1 DI 99
401 DOPNA 1100 1 DI 100
405 DOPNA 1101 1 DI 101
409 DOPNA 1102 1 DI 102
413 DOPNA 1103 1 DI 103
417 DOPNA 1104 1 DI 104
421 DOPNA 1105 1 DI 105
425 DOPNA 1106 1 DI 106
429 DOPNA 1107 1 DI 107
433 DOPNA 1108 1 DI 108
437 DOPNA 1109 1 DI 109
441 DOPNA 1110 1 DI 110
445 DOPNA 1111 1 DI 111
449 DOPNA 1112 1 DI 112
453 DOPNA 1113 1 DI 113
457 DOPNA 1114 1 DI 114
461 DOPNA 1115 1 DI 115
465 DOPNA 1116 1 DI 116
469 DOPNA 1117 1 DI 117
473 DOPNA 1118 1 DI 118
477 DOPNA 1119 1 DI 119
481 DOPNA 1120 1 DI 120
485 DOPNA 1121 1 DI 121
489 DOPNA 1122 1 DI 122
493 DOPNA 1123 1 DI 123
497 DOPNA 1124 1 DI 124
3BCA014034R0001 Rev. F F-3

----- LIST OF SORTED ANALOG READ (AOP) POINTS -----
Index PtType Block PLCDataType PLC DataTable PointAddress ScaleNdx
3 AOP 3000 S 1 AI 0 1
7 AOP 3001 S 1 AI 1 1
11 AOP 3002 S 1 AI 2 1
15 AOP 3003 S 1 AI 3 1
19 AOP 3004 S 1 AI 4 1
23 AOP 3005 S 1 AI 5 1
27 AOP 3006 S 1 AI 6 1
31 AOP 3007 S 1 AI 7 1
35 AOP 3008 S 1 AI 8 1
39 AOP 3009 1 S 1 AI A1 9 9 1 1
43 AOP 3010 S 1 AI 10 1
47 AOP 3011 S 1 AI 11 1
51 AOP 3012 S 1 AI 12 1
55 AOP 3013 S 1 AI 13 1
59 AOP 3014 S 1 AI 14 1
63 AOP 3015 S 1 AI 15 1
67 AOP 3016 S 1 AI 16 1
71 AOP 3017 S 1 AI 17 1
75 AOP 3018 S 1 AI 18 1
79 AOP 3019 S 1 AI 19 1
83 AOP 3020 S 1 AI 20 1
87 AOP 3021 S 1 AI 21 1
91 AOP 3022 S 1 AI 22 1
95 AOP 3023 S 1 AI 23 1
99 AOP 3024 S 1 AI 24 1
103 AOP 3025 S 1 AI 25 1
107 AOP 3026 S 1 AI 26 1
111 AOP 3027 S 1 AI 27 1
115 AOP 3028 S 1 AI 28 1
119 AOP 3029 S 1 AI 29 1
123 AOP 3030 S 1 AI 30 1
127 AOP 3031 S 1 AI 31 1
131 AOP 3032 S 1 AI 32 1
135 AOP 3033 S 1 AI 33 1
139 AOP 3034 S 1 AI 34 1
143 AOP 3035 S 1 AI 35 1
147 AOP 3036 S 1 AI 36 1
151 AOP 3037 S 1 AI 37 1
155 AOP 3038 S 1 AI 38 1
159 AOP 3039 S 1 AI 39 1
163 AOP 3040 S 1 AI 40 1
167 AOP 3041 S 1 AI 41 1
171 AOP 3042 S 1 AI 42 1
175 AOP 3043 S 1 AI 43 1
179 AOP 3044 S 1 AI 44 1
183 AOP 3045 S 1 AI 45 1
187 AOP 3046 S 1 AI 46 1
191 AOP 3047 S 1 AI 47 1
195 AOP 3048 S 1 AI 48 1
199 AOP 3049 S 1 AI 49 1
203 AOP 3050 S 1 AI 50 1
207 AOP 3051 S 1 AI 51 1
211 AOP 3052 S 1 AI 52 1
215 AOP 3053 S 1 AI 53 1
219 AOP 3054 S 1 AI 54 1
F-4 3BCA014034R0001 Rev. F

223 AOP 3055 S 1 AI 55 1
227 AOP 3056 S 1 AI 56 1
231 AOP 3057 S 1 AI 57 1
235 AOP 3058 S 1 AI 58 1
239 AOP 3059 S 1 AI 59 1
243 AOP 3060 S 1 AI 60 1
247 AOP 3061 S 1 AI 61 1
251 AOP 3062 S 1 AI 62 1
255 AOP 3063 S 1 AI 63 1
259 AOP 3064 S 1 AI 64 1
263 AOP 3065 S 1 AI 65 1
267 AOP 3066 S 1 AI 66 1
271 AOP 3067 S 1 AI 67 1
275 AOP 3068 S 1 AI 68 1
279 AOP 3069 S 1 AI 69 1
283 AOP 3070 S 1 AI 70 1
287 AOP 3071 S 1 AI 71 1
291 AOP 3072 S 1 AI 72 1
295 AOP 3073 S 1 AI 73 1
299 AOP 3074 S 1 AI 74 1
303 AOP 3075 S 1 AI 75 1
307 AOP 3076 S 1 AI 76 1
311 AOP 3077 S 1 AI 77 1
315 AOP 3078 S 1 AI 78 1
319 AOP 3079 S 1 AI 79 1
323 AOP 3080 S 1 AI 80 1
327 AOP 3081 S 1 AI 81 1
331 AOP 3082 S 1 AI 82 1
335 AOP 3083 S 1 AI 83 1
339 AOP 3084 S 1 AI 84 1
343 AOP 3085 S 1 AI 85 1
347 AOP 3086 S 1 AI 86 1
351 AOP 3087 S 1 AI 87 1
355 AOP 3088 S 1 AI 88 1
359 AOP 3089 S 1 AI 89 1
363 AOP 3090 S 1 AI 90 1
367 AOP 3091 S 1 AI 91 1
371 AOP 3092 S 1 AI 92 1
375 AOP 3093 S 1 AI 93 1
379 AOP 3094 S 1 AI 94 1
383 AOP 3095 S 1 AI 95 1
387 AOP 3096 S 1 AI 96 1
391 AOP 3097 S 1 AI 97 1
395 AOP 3098 S 1 AI 98 1
399 AOP 3099 S 1 AI 99 1
403 AOP 3100 S 1 AI 100 1
407 AOP 3101 S 1 AI 101 1
411 AOP 3102 S 1 AI 102 1
415 AOP 3103 S 1 AI 103 1
419 AOP 3104 S 1 AI 104 1
423 AOP 3105 S 1 AI 105 1
427 AOP 3106 S 1 AI 106 1
431 AOP 3107 S 1 AI 107 1
435 AOP 3108 S 1 AI 108 1
439 AOP 3109 S 1 AI 109 1
443 AOP 3110 S 1 AI 110 1
447 AOP 3111 S 1 AI 111 1
3BCA014034R0001 Rev. F F-5

451 AOP 3112 S 1 AI 112 1
455 AOP 3113 S 1 AI 113 1
459 AOP 3114 S 1 AI 114 1
463 AOP 3115 S 1 AI 115 1
467 AOP 3116 S 1 AI 116 1
471 AOP 3117 S 1 AI 117 1
475 AOP 3118 S 1 AI 118 1
479 AOP 3119 S 1 AI 119 1
483 AOP 3120 S 1 AI 120 1
487 AOP 3121 S 1 AI 121 1
491 AOP 3122 S 1 AI 122 1
495 AOP 3123 S 1 AI 123 1
499 AOP 3124 S 1 AI 124 1
----- LIST OF SORTED PLC STATUS (STATUS REGISTER) POINTS -----

Index PtType Block PLC StatusRegister
There are no STATUS REGISTER points in this configuration.
----- LIST OF SORTED DIGITAL WRITE (DIP) POINTS -----

Index PtType Block PLC DataTable PointAddress
2 DIP 2000 1 DO 0
6 DIP 2001 1 DO 1
10 DIP 2002 1 DO 2
14 DIP 2003 1 DO 3
18 DIP 2004 1 DO 4
22 DIP 2005 1 DO 5
26 DIP 2006 1 DO 6
30 DIP 2007 1 DO 7
34 DIP 2008 1 DO 8
38 DIP 2009 1 DO 9
42 DIP 2010 1 DO 10
46 DIP 2011 1 DO 11
50 DIP 2012 1 DO 12
54 DIP 2013 1 DO 13
58 DIP 2014 1 DO 14
62 DIP 2015 1 DO 15
66 DIP 2016 1 DO 16
70 DIP 2017 1 DO 17
74 DIP 2018 1 DO 18
78 DIP 2019 1 DO 19
82 DIP 2020 1 DO 20
86 DIP 2021 1 DO 21
90 DIP 2022 1 DO 22
94 DIP 2023 1 DO 23
98 DIP 2024 1 DO 24
102 DIP 2025 1 DO 25
106 DIP 2026 1 DO 26
110 DIP 2027 1 DO 27
114 DIP 2028 1 DO 28
118 DIP 2029 1 DO 29
122 DIP 2030 1 DO 30
126 DIP 2031 1 DO 31
130 DIP 2032 1 DO 32
134 DIP 2033 1 DO 33
138 DIP 2034 1 DO 34
142 DIP 2035 1 DO 35
F-6 3BCA014034R0001 Rev. F

146 DIP 2036 1 DO 36
150 DIP 2037 1 DO 37
154 DIP 2038 1 DO 38
158 DIP 2039 1 DO 39
162 DIP 2040 1 DO 40
166 DIP 2041 1 DO 41
170 DIP 2042 1 DO 42
174 DIP 2043 1 DO 43
178 DIP 2044 1 DO 44
182 DIP 2045 1 DO 45
186 DIP 2046 1 DO 46
190 DIP 2047 1 DO 47
194 DIP 2048 1 DO 48
198 DIP 2049 1 DO 49
202 DIP 2050 1 DO 50
206 DIP 2051 1 DO 51
210 DIP 2052 1 DO 52
214 DIP 2053 1 DO 53
218 DIP 2054 1 DO 54
222 DIP 2055 1 DO 55
226 DIP 2056 1 DO 56
230 DIP 2057 1 DO 57
234 DIP 2058 1 DO 58
238 DIP 2059 1 DO 59
242 DIP 2060 1 DO 60
246 DIP 2061 1 DO 61
250 DIP 2062 1 DO 62
254 DIP 2063 1 DO 63
258 DIP 2064 1 DO 64
262 DIP 2065 1 DO 65
266 DIP 2066 1 DO 66
270 DIP 2067 1 DO 67
274 DIP 2068 1 DO 68
278 DIP 2069 1 DO 69
282 DIP 2070 1 DO 70
286 DIP 2071 1 DO 71
290 DIP 2072 1 DO 72
294 DIP 2073 1 DO 73
298 DIP 2074 1 DO 74
302 DIP 2075 1 DO 75
306 DIP 2076 1 DO 76
310 DIP 2077 1 DO 77
314 DIP 2078 1 DO 78
318 DIP 2079 1 DO 79
322 DIP 2080 1 DO 80
326 DIP 2081 1 DO 81
330 DIP 2082 1 DO 82
334 DIP 2083 1 DO 83
338 DIP 2084 1 DO 84
342 DIP 2085 1 DO 85
346 DIP 2086 1 DO 86
350 DIP 2087 1 DO 87
354 DIP 2088 1 DO 88
358 DIP 2089 1 DO 89
362 DIP 2090 1 DO 90
366 DIP 2091 1 DO 91
370 DIP 2092 1 DO 92
3BCA014034R0001 Rev. F F-7

374 DIP 2093 1 DO 93
378 DIP 2094 1 DO 94
382 DIP 2095 1 DO 95
386 DIP 2096 1 DO 96
390 DIP 2097 1 DO 97
394 DIP 2098 1 DO 98
398 DIP 2099 1 DO 99
402 DIP 2100 1 DO 100
406 DIP 2101 1 DO 101
410 DIP 2102 1 DO 102
414 DIP 2103 1 DO 103
418 DIP 2104 1 DO 104
422 DIP 2105 1 DO 105
426 DIP 2106 1 DO 106
430 DIP 2107 1 DO 107
434 DIP 2108 1 DO 108
438 DIP 2109 1 DO 109
442 DIP 2110 1 DO 110
446 DIP 2111 1 DO 111
450 DIP 2112 1 DO 112
454 DIP 2113 1 DO 113
458 DIP 2114 1 DO 114
462 DIP 2115 1 DO 115
466 DIP 2116 1 DO 116
470 DIP 2117 1 DO 117
474 DIP 2118 1 DO 118
478 DIP 2119 1 DO 119
482 DIP 2120 1 DO 120
486 DIP 2121 1 DO 121
490 DIP 2122 1 DO 122
494 DIP 2123 1 DO 123
498 DIP 2124 1 DO 124
----- LIST OF SORTED ANALOG WRITE (AIP) POINTS -----

Index PtType Block PLCDataType PLC DataTable PointAddress ScaleNdx
4 AIP 4000 S 1 AO 0 1
8 AIP 4001 S 1 AO 1 1
12 AIP 4002 S 1 AO 2 1
16 AIP 4003 S 1 AO 3 1
20 AIP 4004 S 1 AO 4 1
24 AIP 4005 S 1 AO 5 1
28 AIP 4006 S 1 AO 6 1
32 AIP 4007 S 1 AO 7 1
36 AIP 4008 S 1 AO 8 1
40 AIP 4009 S 1 AO 9 1
44 AIP 4010 S 1 AO 10 1
48 AIP 4011 S 1 AO 11 1
52 AIP 4012 S 1 AO 12 1
56 AIP 4013 S 1 AO 13 1
60 AIP 4014 S 1 AO 14 1
64 AIP 4015 S 1 AO 15 1
68 AIP 4016 S 1 AO 16 1
72 AIP 4017 S 1 AO 17 1
76 AIP 4018 S 1 AO 18 1
80 AIP 4019 S 1 AO 19 1
84 AIP 4020 S 1 AO 20 1
88 AIP 4021 S 1 AO 21 1
F-8 3BCA014034R0001 Rev. F

92 AIP 4022 S 1 AO 22 1
96 AIP 4023 S 1 AO 23 1
100 AIP 4024 S 1 AO 24 1
104 AIP 4025 S 1 AO 25 1
108 AIP 4026 S 1 AO 26 1
112 AIP 4027 S 1 AO 27 1
116 AIP 4028 S 1 AO 28 1
120 AIP 4029 S 1 AO 29 1
124 AIP 4030 S 1 AO 30 1
128 AIP 4031 S 1 AO 31 1
132 AIP 4032 S 1 AO 32 1
136 AIP 4033 S 1 AO 33 1
140 AIP 4034 S 1 AO 34 1
144 AIP 4035 S 1 AO 35 1
148 AIP 4036 S 1 AO 36 1
152 AIP 4037 S 1 AO 37 1
156 AIP 4038 S 1 AO 38 1
160 AIP 4039 S 1 AO 39 1
164 AIP 4040 S 1 AO 40 1
168 AIP 4041 S 1 AO 41 1
172 AIP 4042 S 1 AO 42 1
176 AIP 4043 S 1 AO 43 1
180 AIP 4044 S 1 AO 44 1
184 AIP 4045 S 1 AO 45 1
188 AIP 4046 S 1 AO 46 1
192 AIP 4047 S 1 AO 47 1
196 AIP 4048 S 1 AO 48 1
200 AIP 4049 S 1 AO 49 1
204 AIP 4050 S 1 AO 50 1
208 AIP 4051 S 1 AO 51 1
212 AIP 4052 S 1 AO 52 1
216 AIP 4053 S 1 AO 53 1
220 AIP 4054 S 1 AO 54 1
224 AIP 4055 S 1 AO 55 1
228 AIP 4056 S 1 AO 56 1
232 AIP 4057 S 1 AO 57 1
236 AIP 4058 S 1 AO 58 1
240 AIP 4059 S 1 AO 59 1
244 AIP 4060 S 1 AO 60 1
248 AIP 4061 S 1 AO 61 1
252 AIP 4062 S 1 AO 62 1
256 AIP 4063 S 1 AO 63 1
260 AIP 4064 S 1 AO 64 1
264 AIP 4065 S 1 AO 65 1
268 AIP 4066 S 1 AO 66 1
272 AIP 4067 S 1 AO 67 1
276 AIP 4068 S 1 AO 68 1
280 AIP 4069 S 1 AO 69 1
284 AIP 4070 S 1 AO 70 1
288 AIP 4071 S 1 AO 71 1
292 AIP 4072 S 1 AO 72 1
296 AIP 4073 S 1 AO 73 1
300 AIP 4074 S 1 AO 74 1
304 AIP 4075 S 1 AO 75 1
308 AIP 4076 S 1 AO 76 1
312 AIP 4077 S 1 AO 77 1
316 AIP 4078 S 1 AO 78 1
3BCA014034R0001 Rev. F F-9

320 AIP 4079 S 1 AO 79 1
324 AIP 4080 S 1 AO 80 1
328 AIP 4081 S 1 AO 81 1
332 AIP 4082 S 1 AO 82 1
336 AIP 4083 S 1 AO 83 1
340 AIP 4084 S 1 AO 84 1
344 AIP 4085 S 1 AO 85 1
348 AIP 4086 S 1 AO 86 1
352 AIP 4087 S 1 AO 87 1
356 AIP 4088 S 1 AO 88 1
360 AIP 4089 S 1 AO 89 1
364 AIP 4090 S 1 AO 90 1
368 AIP 4091 S 1 AO 91 1
372 AIP 4092 S 1 AO 92 1
376 AIP 4093 S 1 AO 93 1
380 AIP 4094 S 1 AO 94 1
384 AIP 4095 S 1 AO 95 1
388 AIP 4096 S 1 AO 96 1
392 AIP 4097 S 1 AO 97 1
396 AIP 4098 S 1 AO 98 1
400 AIP 4099 S 1 AO 99 1
404 AIP 4100 S 1 AO 100 1
408 AIP 4101 S 1 AO 101 1
412 AIP 4102 S 1 AO 102 1
416 AIP 4103 S 1 AO 103 1
420 AIP 4104 S 1 AO 104 1
424 AIP 4105 S 1 AO 105 1
428 AIP 4106 S 1 AO 106 1
432 AIP 4107 S 1 AO 107 1
436 AIP 4108 S 1 AO 108 1
440 AIP 4109 S 1 AO 109 1
444 AIP 4110 S 1 AO 110 1
448 AIP 4111 S 1 AO 111 1
452 AIP 4112 S 1 AO 112 1
456 AIP 4113 S 1 AO 113 1
460 AIP 4114 S 1 AO 114 1
464 AIP 4115 S 1 AO 115 1
468 AIP 4116 S 1 AO 116 1
472 AIP 4117 S 1 AO 117 1
476 AIP 4118 S 1 AO 118 1
480 AIP 4119 S 1 AO 119 1
484 AIP 4120 S 1 AO 120 1
488 AIP 4121 S 1 AO 121 1
492 AIP 4122 S 1 AO 122 1
496 AIP 4123 S 1 AO 123 1
500 AIP 4124 S 1 AO 124 1
F - 10 3BCA014034R0001 Rev. F
----- LIST OF SORTED READ GROUPS -----
GrpNo DataType PLC DataTable FirstPoint LastPoint
0 DIGITAL 1 DI 0 124
1 ANALOG 1 AI 0 111
2 ANALOG 1 AI 112 124
----- LIST OF SORTED WRITE GROUPS -----

GrpNo DataType PLC DataTable FirstPoint LastPoint
0 DIGITAL 1 DO 0 124
1 ANALOG 1 AO 0 49
2 ANALOG 1 AO 50 99
3 ANALOG 1 AO 100 124
----- LIST OF SCALING SETS SPECIFIED -----

Reference Multiplier Offset Signed/Unsigned
1 1.00000000e+000 0.00000000e+000 UNSIGNED
2 0.00000000e+000 0.00000000e+000 UNSIGNED
3 0.00000000e+000 0.00000000e+000 UNSIGNED
4 0.00000000e+000 0.00000000e+000 UNSIGNED
5 0.00000000e+000 0.00000000e+000 UNSIGNED
6 0.00000000e+000 0.00000000e+000 UNSIGNED
7 0.00000000e+000 0.00000000e+000 UNSIGNED
8 0.00000000e+000 0.00000000e+000 UNSIGNED
9 0.00000000e+000 0.00000000e+000 UNSIGNED
10 0.00000000e+000 0.00000000e+000 UNSIGNED
11 0.00000000e+000 0.00000000e+000 UNSIGNED
12 0.00000000e+000 0.00000000e+000 UNSIGNED
13 0.00000000e+000 0.00000000e+000 UNSIGNED
14 0.00000000e+000 0.00000000e+000 UNSIGNED
15 0.00000000e+000 0.00000000e+000 UNSIGNED
16 0.00000000e+000 0.00000000e+000 UNSIGNED
17 0.00000000e+000 0.00000000e+000 UNSIGNED
18 0.00000000e+000 0.00000000e+000 UNSIGNED
19 0.00000000e+000 0.00000000e+000 UNSIGNED
20 0.00000000e+000 0.00000000e+000 UNSIGNED
21 0.00000000e+000 0.00000000e+000 UNSIGNED
22 0.00000000e+000 0.00000000e+000 UNSIGNED
23 0.00000000e+000 0.00000000e+000 UNSIGNED
24 0.00000000e+000 0.00000000e+000 UNSIGNED
25 0.00000000e+000 0.00000000e+000 UNSIGNED
26 0.00000000e+000 0.00000000e+000 UNSIGNED
27 0.00000000e+000 0.00000000e+000 UNSIGNED
28 0.00000000e+000 0.00000000e+000 UNSIGNED
29 0.00000000e+000 0.00000000e+000 UNSIGNED
30 0.00000000e+000 0.00000000e+000 UNSIGNED
31 0.00000000e+000 0.00000000e+000 UNSIGNED
32 0.00000000e+000 0.00000000e+000 UNSIGNED
33 0.00000000e+000 0.00000000e+000 UNSIGNED
34 0.00000000e+000 0.00000000e+000 UNSIGNED
35 0.00000000e+000 0.00000000e+000 UNSIGNED
36 0.00000000e+000 0.00000000e+000 UNSIGNED
37 0.00000000e+000 0.00000000e+000 UNSIGNED
38 0.00000000e+000 0.00000000e+000 UNSIGNED
39 0.00000000e+000 0.00000000e+000 UNSIGNED
40 0.00000000e+000 0.00000000e+000 UNSIGNED
41 0.00000000e+000 0.00000000e+000 UNSIGNED
42 0.00000000e+000 0.00000000e+000 UNSIGNED
3BCA014034R0001 Rev. F F - 11
43 0.00000000e+000 0.00000000e+000 UNSIGNED
44 0.00000000e+000 0.00000000e+000 UNSIGNED
45 0.00000000e+000 0.00000000e+000 UNSIGNED
46 0.00000000e+000 0.00000000e+000 UNSIGNED
47 0.00000000e+000 0.00000000e+000 UNSIGNED
48 0.00000000e+000 0.00000000e+000 UNSIGNED
49 0.00000000e+000 0.00000000e+000 UNSIGNED
50 0.00000000e+000 0.00000000e+000 UNSIGNED
51 0.00000000e+000 0.00000000e+000 UNSIGNED
52 0.00000000e+000 0.00000000e+000 UNSIGNED
53 0.00000000e+000 0.00000000e+000 UNSIGNED
54 0.00000000e+000 0.00000000e+000 UNSIGNED
55 0.00000000e+000 0.00000000e+000 UNSIGNED
56 0.00000000e+000 0.00000000e+000 UNSIGNED
57 0.00000000e+000 0.00000000e+000 UNSIGNED
58 0.00000000e+000 0.00000000e+000 UNSIGNED
59 0.00000000e+000 0.00000000e+000 UNSIGNED
60 0.00000000e+000 0.00000000e+000 UNSIGNED
61 0.00000000e+000 0.00000000e+000 UNSIGNED
62 0.00000000e+000 0.00000000e+000 UNSIGNED
63 0.00000000e+000 0.00000000e+000 UNSIGNED
64 0.00000000e+000 0.00000000e+000 UNSIGNED
Thu Nov 29 15:27:51 2007 <<<<<<< END OF CONFIGURATION FILE

GPI02_500rtu REVIEW >>>>>>>
F - 12 3BCA014034R0001 Rev. F
Example GPI AB Review Output Appendix G
File
Thu Nov 29 15:43:48 2007 *** GPI03 CONFIGURATION COMPILE ERROR REVIEW for GPI03_500ab.AB ***
No errors found in file GPI03_500ab.AB
Thu Nov 29 15:43:48 2007 *** END GPI03 CONFIGURATION COMPILE ERROR REVIEW for GPI03_500ab.AB ***
Thu Nov 29 15:43:48 2007 <<<<<<< REVIEW OF CONFIGURATION FILE GPI03_500ab.AB >>>>>>>
Symphony GPI Version 3.00, Module type BRC300, Capacity 500

Write Mode = Block Writes. Maximum # of Write Points = 500
The GPI module segment at block number 9000. Invoke C block at 9010
The Communication Status blocks start at block number 9020
The PLC Address blocks start at block number 9040
The KF Status blocks start at block number 9060
Number of points in the configuration is 500. 250 Read Pts, 250 Write Pts
Number of PLCs referenced is 1
The Data Highway type is Data Highway, Data HIghway Plus or PCL
Terminal Port KF Address = 6, Printer Port KF Address = 7
KF Communication Timeout = 1000 MSec, Number of Retries = 2
===== LIST OF PLCS REFERENCED IN CONFIGURATION =====

PLCType Link Node Station
PLC-5 0 0 1
PLC Response Timeout = 1000 MSec, Number of Retries = 2
===== LIST OF SORTED AOP AND DOP POINTS =====
Under ScaleRef, NA indicates Not Applicable for DOP & DIP points and
Default indicates a Multiplier/Offset pair of 1.0/0.0
A positive number is an index to the Scaling listed below.
PType DOAlarm BType Block PLC Link Node Station FileType FileNo DataType Word Bit ScaleRef Tag
DO NA B 1000 PLC5 0 0 1 B 14 Boolean 0 0 NA
3BCA014034R0001 Rev. F G-1

G-2 3BCA014034R0001 Rev. F

AO NA B 3000 PLC5 0 0 1 N 16 UInteger 0 16 Default
3BCA014034R0001 Rev. F G-3

G-4 3BCA014034R0001 Rev. F

===== LIST OF SORTED AIP AND DIP POINTS =====
Under ScaleRef, NA indicates Not Applicable for DOP & DIP points and
Default indicates a Multiplier/Offset pair of 1.0/0.0
A positive number is an index to the Scaling listed below.
PType BType Block Link Node Station FileType FileNo DataType Word Bit ScaleRef Tag
DI NA 2000 PLC5 0 0 1 B 15 Boolean 0 0 NA
3BCA014034R0001 Rev. F G-5

G-6 3BCA014034R0001 Rev. F

AI NA 4000 PLC5 0 0 1 N 17 UInteger 0 16 Default
3BCA014034R0001 Rev. F G-7

G-8 3BCA014034R0001 Rev. F

===== LIST OF READ GROUPS IN ORDER =====

GrpNo Link Node Station PLCType Module Context FileType File# FirstWord LastWord
0 0 0 1 PLC-5 NA 0 B 14 0 7
1 0 0 1 PLC-5 NA 0 N 16 0 112
2 0 0 1 PLC-5 NA 0 N 16 113 124
===== LIST OF WRITE GROUPS IN ORDER =====

GrpNo Link Node Station PLCType Module Context FileType File# FirstWord LastWord
0 0 0 1 PLC-5 NA 0 B 15 0 7
1 0 0 1 PLC-5 NA 0 N 17 0 112
2 0 0 1 PLC-5 NA 0 N 17 113 124
===== LIST OF SCALING PAIRS SPECIFIED =====

Reference Multiplier Offset
Default 1.0 0.0
No other Multiplier/Offset pairs assigned
Thu Nov 29 15:43:48 2007 <<<<<<< END OF CONFIGURATION FILE GPI03_500ab.AB REVIEW >>>>>>>
3BCA014034R0001 Rev. F G-9

G - 10 3BCA014034R0001 Rev. F
Index
A Configuration
Data File ..............................................4-16
AB ......................................................... 1-1 Data Importing .....................................4-40
Access Errors ..................................... 5-24 Requirements ......................................4-32
Configuration ........................................C-1 RTU .....................................................4-17
Configuration Menus ........................... 4-39 Configuration Keywords
Data Importing .................................... 4-40 AB ........................................................ C- 2
Error File Messages..............................C- 4 RTU...................................................... B- 2
Error Log.................................... 5- 20, 5-24 Controller Module
Error Messages ....................................C-4 Error Log ...............................................3-9
Fatal Errors ......................................... 5-20 Installation .............................................2-3
Function Block Requirements.............. 3-11 Requirements ........................................1-8
General Information ............................... 5-1 Termination Set Up .............................2-13
Information .......................................... 4-35
Keywords ..............................................C-2
D
PLC Data Addressing ........................... 3-6
Point Parameters ................................ 4-47 DF1
Support Blocks .................................... 3-18 Allen-Bradley.........................................1- 7
Troubleshooting .................................. 5-19 Commands Supported by AB................1- 7
Address Dipswitch Settings
Modbus RTU ......................................... 3-2 BRC100 .................................................2-7
RTUSLAVE ........................................... 3-2 IMMFP03/IMMPI01 ...............................2- 5
Selection Screen ................................... 5-3 Document Conventions ..........................1-12
Allen-Bradley
1770-KF2 ............................................ 2-25 E
1771-KG Module ................................. 2-23
Data Highway ..................................... 2-28 Error File Messages
Modbus RTU ......................................... 5-3 RTU ...................................................... B-5
Screen .................................................. 5-4 Error Log
AB .............................................. 5-20, 5-24
B RTU ............................................5-12, 5-16
Example
Baud Rates .............................................. 1-3 J1/J2 Jumper Settings .........................2-26
C F
CD Software ................................... 1-10, 2-1 Fatal Errors
Common Parameters AB .......................................................5-20
AB ....................................................... 4-43 RTUSLAVE .........................................5-25
RTU .................................................... 4-24 Function Block..........................................1- 3
Communication Interface Status ............ 5-28 Access Errors ......................................5-29
Composer ................................................ 1- 5 Requirements......................................3- 11
3BCA014034R0001 Rev. F Index - 1

Index (continued)
G M
General Configuration Information ...........3-1 Modbus
General Serial Interface ............................1-4 Functions .............................................. 1-6
Glossary of Terms ..................................1-11 Functions - RTUSLAVE ........................ 1- 7
GPI Modbus RTU ........................................... 1-3
AB ..................................................1-1, 1-7 Address ................................................ 3-2
Composer Relation ...............................1-5 Communication Overview..................... 3-5
Limitations .............................................1-2 Link Status ............................................ 5-3
Protocol .................................................1- 6 Screen .................................................. 5-4
RTU ................................................1-1, 1-6 Module
RTUSLAVE ....................................1-1, 1-7 Address Selection Screen ............. 5-3, 5-4
Controller .............................................. 1- 1
H File........................................................ 1- 2
Saving and Restoring ...................... 4-10
HAC01 Host Controller...................................... 3- 2
Initialization ...........................................2-8 Licensing ............................................ 4-13
Re-install Data File in Primary ... 4-10, 4-13
I Startup Sequence................................. 5- 2
Multiple Point Value
Install Read Groups ........................................ 1-3
Controller Module.................................. 2-3 Write Groups ........................................ 1- 3
Serial Interface ......................................2-9
User Interface Software ........................2-1
Interface Module
N
Settings ...............................................2-31 NVM
Invoke C Error Log ............................................... 5-1
General Information ..............................5-1 Startup Sequence ................................. 5-2
J O
J1/J2 Output Blocks
Jumper Setting Example .....................2-26 AB ....................................................... 5-34
RTU .................................................... 5-31
K
Keywords
P
AB ........................................................ C-2 PLC .......................................................... 1-2
RTU...................................................... B- 2 Communication Overview..................... 3-5
Data Addressing ................................... 3-7
L Minimum Read Points .......................... 1-4
PLC Writes ................................... 4- 45, 5-23
Licensing .........................................2-3, 4-14
Log Error Messages .................................1-4
Index - 2 3BCA014034R0001 Rev. F

Index (continued)
Point Parameters Troubleshooting ..................................5-25

AB .......................................................... 4- 47
RTU ....................................................... 4-25 S
Primary Module ............................ 4-10, 4-13
Protocol Analyzer .................................. 5-22 Serial Interface
Installation ..............................................2-9
R Software .................................................1-10
CD ..........................................................2-1
Read vs Write User Interface.........................................2-1
AB ......................................................... 1- 3 Status & Statistics Output Blocks............5-31
RTU ...................................................... 1- 3 Status Output Blocks
References .............................................1-12 RTUSLAVE .........................................5-26
Re-install Data File in Primary Module ... 4-13 Support Blocks
Requirements AB .......................................................3-18
Controller Module ................................. 1- 8 RTU .....................................................3-13
RS232...................................................... 1- 4 RTUSLAVE .........................................3-21
RS485..................................................... 1-18
RTU .................................................. 1-1, 1-3 T
Access Errors ..................................... 5-16
Common Parameters .......................... 4-24 Terms .....................................................1-11
Communication Overview ..................... 3-5 Troubleshooting
Configuration ...................................... 4-17 AB .......................................................5-19
Configuration Examples ........................B-1 RTU .....................................................5-11
Error Log..................................... 5-12, 5-16 RTUSLAVE .........................................5-25
Error Log Messages ........................... 5-12
Fatal Errors ......................................... 5-12 W
General Information .............................. 5-1
Information .......................................... 4-17 Work Station
Support Blocks .................................... 3-13 Requirements ........................................1-8
Troubleshooting .................................. 5-11
RTU Status & Statistic Outputs ..............5-31
RTUSLAVE ..................................... 1-1, 4-32
Address................................................. 3- 2
Fatal Errors ......................................... 5-25
Function Block Requirements............. 3- 11
Interface Menus .................................. 4-35
Requirements ..................................... 4-32
Status Output Blocks .......................... 5-26
Support Blocks .................................... 3-21
3BCA014034R0001 Rev. F Index - 3

3BCA014034R0001 Rev. F
For the latest information on ABB visit us on the World Wide Web at http://www.abb.com
Our worldwide staff of professionals is ready to meet your needs for process automation.
For the location nearest you, please contact the appropriate regional office.
Americas Asia/Pacific Germany Europe, Africa, Middle East

29801 Euclid Avenue 539 Yishun Industrial Park A Industriestrasse 28 Via Puccini 2
Wickliffe, Ohio USA 44092 Singapore 768740 D-65760 Eschborn 16154 Genoa, Italy
Telephone 1-440-585-8500 Telephone 65-756-7655 Germany Telephone 39-010-6584-943
Telefax 1-440-585-8756 Telefax 65-756-7309 Telephone 49-6196-800-0 Telefax 39-010-6584-941
Telefax 49-6196-800-1119
Form 3BCA014034R0001 Rev. F Printed in Canada 01/08

Copyright © 2008 by ABB, All Rights Reserved
® Registered Trademark of ABB
™ Trademark of ABB

3bua000359r0007 G en Symphony Communication Module Reference Table

Uploaded by

Document Information

Original Title

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

3bua000359r0007 G en Symphony Communication Module Reference Table

Uploaded by

Copyright:

Available Formats

Instruction

General Purpose Interface (GPI)

Adaptec Registered trademark of Adaptec, Inc.

Ethernet Trademark of Xerox Corporation.

FrontPage Registered trademark of Microsoft Corporation.

Industrial IT Trademark of ABB.

Microsoft Registered trademark of Microsoft Corporation.

Pentium Registered trademark of Intel Corporation.

PROFIBUS Registered trademark of PROFIBUS International.

Windows Server Trademark of Microsoft Inc.

Section 1 — Introduction ..............................................................................................1-1

Section 2 — Getting Started ........................................................................................2-1

3BCA014034R0001 Rev. F iii

Section 3— General Configuration Information .........................................................3-1

Section 4 — The User Interface ...................................................................................4-1

Section 5 — Troubleshooting ......................................................................................5-1

Appendix A — GPI Database Structure ..................................................................... A-1

Appendix B — GPI RTU Reference Information ....................................................... B-1

Appendix C — GPI AB Reference Information ......................................................... C-1

Appendix E — Example License String Document .................................................. E-1

Appendix F — Example GPI RTU Review Output File ...............................................F-1

Appendix G — Example GPI AB Review Output File ............................................... G-1

3BCA014034R0001 Rev. F vii

viii 3BCA014034R0001 Rev. F

Electrostatic Sensitive Device

GENERAL Equipment Environment

Electrical Shock Hazard During Maintenance

SPECIFIC If the Composer Online Configuration procedure is aborted for any

ABB will provide assistance in the operation and repair of its

When ordering parts, use nomenclature or part numbers and

ABB has modern training facilities available for training your

3BCA014034R0001 Rev. F xiii

The RTU and AB interface must be configured to establish

RTU Represents a Modbus master interface using Modbus RTU

The ABB controller modules that support GPI are IMMFP02/12,

The GPI user interface includes facilities to enter the required

• Generate and maintain the GPI configuration data for the

• Install the controller module communication software and

• Monitor the performance of the data communication

3BCA014034R0001 Rev. F 1-1

Who Should Use This Manual

Dependencies and Constraints

Transactions Per Second

Write To PLC Mode

1-2 3BCA014034R0001 Rev. F

Read vs Write Transactions RTU

Read vs Write Transaction AB

Multiple Point Value Write Groups

3BCA014034R0001 Rev. F 1-3

Multiple Point Value Read Groups

Data Not Suitable for a General Serial Interface

Minimum Read Points Per PLC

1-4 3BCA014034R0001 Rev. F

All function blocks required for the GPI communication soft-

Diagram of GPI Design

Figure 1-1. GPI Design Diagram

3BCA014034R0001 Rev. F 1-5

Protocol Sub-Set Supported

Table 1-1. Modbus Functions Supported by RTU

1-6 3BCA014034R0001 Rev. F

Table 1-2. Modbus Functions Supported by RTUSLAVE

Table 1-3. Allen-Bradley DF1 Commands Supported by AB

3BCA014034R0001 Rev. F 1-7