LUFP1 v1, Fipio-Modbus RTU Gateway PDF

TeSys U LUFP1
FIPIO / Modbus RTU Gateway

Users Manual
1743315
03/2009
www.schneider-electric.com
Schneider Electric assumes no responsibility for any errors that may appear in this document. If you have any
suggestions for improvements or amendments or have found errors in this publication, please notify us.
No part of this document may be reproduced in any form or by any means, electronic or mechanical, including
photocopying, without express written permission of Schneider Electric.
All pertinent state, regional, and local safety regulations must be observed when installing and using this
product. For reasons of safety and to help ensure compliance with documented system data, only the
manufacturer should perform repairs to components.
When devices are used for applications with technical safety requirements, the relevant instructions must be
followed.
Failure to use Schneider Electric software or approved software with our hardware products may result in injury,
harm, or improper operating results.
Failure to observe this information can result in injury or equipment damage.
2009 Schneider Electric. All rights reserved.
1743315 03/2009
Table of Contents
Safety Information .....................................................4

1. Introduction............................................................6
1.1. Introduction to the Users Manual .......................................... 6
1.2. Introduction to the LUFP1 Gateway ....................................... 8
1.3. Terminology............................................................................ 8
1.4. Introduction to the Communication System Architecture..... 9
1.5. Principle of LUFP1 Gateway Configuration and Operation.. 10
2. Hardware Implementation of the LUFP1

Gateway ........................................................... 12
2.1. On Receipt ........................................................................... 12
2.2. Introduction to the LUFP7 Gateway ..................................... 12
2.3. Mounting the Gateway on a DIN Rail ................................... 13
2.4. Powering the Gateway ......................................................... 14
2.5. Connecting the Gateway to the Modbus Network ................ 14
2.5.1. Examples of Modbus Connection .................................. 15
2.5.2. Pin Outs ......................................................................... 17
2.5.3. Wiring Recommendations for the Modbus Network....... 18
2.6. Connecting the LUFP7 gateway to the Profibus-DP
Network................................................................................. 20
2.6.1. Pin Outs ......................................................................... 20
2.6.2. Wiring Recommendations for the FIPIO Network .......... 21
2.7. Configuring the FIPIO Communication Features ................. 23
2.7.1. Encoding the Gateway Address..................................... 23
5.4.2. Channel Status (%MW\p.2.c\0.0.2) ............................... 59

5.4.3. Module Status (%MW\p.2.c\0.MOD.2)........................... 59
5.5. Status of Explicit Exchanges................................................ 60
5.6. Parameters Specific to Profile FED C32 P .......................... 60
5.6.1. Configuration Parameters (%KW\p.2.c\0.0 to
%KW\p.2.c\0.0.29) ......................................................... 61
5.6.2. Adjustment Parameters (%MW\p.2.c\0.0.20 to
%MW\p.2.c\0.0.49)......................................................... 61
6. Advanced Implementation of the Gateway ...... 62

6.1. Introduction to Advanced Implementation of the Gateway .. 62
6.2. Implementation under PL7 PRO .......................................... 64
7. Using ABC-LUFP Config Tool ........................... 67

7.1. Connecting the Gateway to the Configuration PC ............... 67
7.1.1. Pin-Outs ......................................................................... 67
7.1.2. RS-232 Link Protocol..................................................... 68
7.2. Installing ABC-LUFP Config Tool......................................... 69
7.3. Connecting to / Disconnecting from the Gateway................ 69
7.4. Importing the Gateway Configuration .................................. 70
7.5. Transferring a Configuration to the Gateway ....................... 71
7.5.1. Transferring the Internal Configuration (Profile FED
C32 P) ............................................................................ 71
7.6. Monitoring the Contents of the Gateways Memory ............. 71
Appendix A:........................................................... 108
3. Signaling ............................................................. 25
Appendix B:........................................................... 114
4. Software Implementation of the Gateway........ 26
Appendix C ............................................................ 127
4.1. Introduction........................................................................... 26
4.1.1. System Architecture ....................................................... 26
4.1.2. Configuring the Motor Starters ....................................... 27
4.1.3. Modbus Cycle Time ....................................................... 27
4.1.4. Managing Degraded Modes With the Gateway Default
Configuration .................................................................. 27
4.2. Gateway Configuration under PL7 PRO .............................. 31
4.2.1. WorldFIP Mode .............................................................. 31
4.2.2. Adding the LUFP1 Gateway under PL7 PRO ................ 31
4.2.3. Configuring and Adjusting the LUFP1 Gateway ............ 33
4.2.4. Selecting and Adding the Profibus-DP Master Station .. 34
4.2.5. Adjustment Parameter Values, Standard Configuration 35
4.2.6. Deleting One or More TeSys U Motor Starters from the
Configuration .................................................................. 36
4.2.7. Configuring Gateway Inputs / Outputs ........................... 38
4.2.8. Description of Services Assigned to Gateway I / O ....... 40
4.2.9. Validating and Saving the FIPIO Network
Configuration .................................................................. 41
4.2.10. Assigning Symbols to the Gateways FIPIO Objects ... 41
4.2.11. Checking the Operational Status of the Gateway ........ 42
4.2.12. Modifying the Gateway Parameters in ONLINE Mode. 43
4.2.13. Debugging and Using the Gateway Configuration....... 43
4.2.14. Developing a FIPIO Application ................................... 43
Appendix D ............................................................ 130

Appendix E ............................................................ 136
Index....................................................................... 139
Glossary................................................................. 140
5. FIPIO Objects Available for Programming....... 44

5.1. Periodic Command and Control Words................................ 45
5.1.1. Standard Configuration with 8 TeSys U Motor Starters . 45
5.1.2. Configuration under PL7 PRO with Profile FED C32 P . 46
5.1.3. Configuration under ABC-LUFP Config Tool with
Profile FED C32.............................................................. 47
5.2. List of Active Slaves (LAS) Service ...................................... 48
5.3. Indexed Periodic Variables (PKW) Service.......................... 49
5.3.1. Introduction to the PKW Service .................................... 49
5.3.2. PKW Service: Command and Response ....................... 50
5.3.3. Using the Indexed Periodic Variables (PKW) Service ... 51
5.3.4. Sample Uses of PKW Service ....................................... 53
5.3.5. LUFP1 Gateway Internal Registers ............................... 55
5.4. FIPIO Diagnostic Objects ..................................................... 58
5.4.1. System Words %SW128 to %SW135............................ 59
1743315 03/2009
Safety Information
NOTICE
Read these instructions carefully, and look at the equipment to become familiar with the
device before trying to install, operate, or maintain it. The following special messages may
appear throughout this documentation or on the equipment to warn of potential hazards or
to call attention to information that clarifies or simplifies a procedure.
DANGER
DANGER indicates an imminently hazardous situation which, if not avoided, will result
in death or serious injury.
WARNING
WARNING indicates a potentially hazardous situation which, if not avoided, can result
in death or serious injury.
CAUTION
CAUTION indicates a potentially hazardous situation which, if not avoided, can result
in minor or moderate injury.
CAUTION
CAUTION, used without the safety alert symbol, indicates a potentially hazardous
situation which, if not avoided, can result in equipment damage.
PLEASE NOTE
Electrical equipment should be installed, operated, serviced and maintained only by

qualified personnel. No responsibility is assumed by Schneider Electric for any
consequences arising out of the use of this material.
1743315 03/2009
About the book

Validity Note
This document applies to all V2 gateways.
Related
Documents
Title of Documentation
Reference Number
AnyBus Communicator User Manual

Safety Guidelines for the Application,
Maintenance of Solid State Control
Installation,
ABC_User_Manual.pdf
(SDN-7061-059)
and NEMA ICS 1.1
(latest edition)
Safety Standards for Construction and Guide for Selection, NEMA ICS 7.1
Installation and Operation of Adjustable-Speed Drive Systems
(latest edition)
Modbus User Guide
TSX DG MDB E
Modicon Modbus Protocol Reference Guide
PI-MBUS-300 Rev. J
You can download these technical publications and other technical information from our
website at www.schneider-electric.com.
User Comments
1743315 03/2009
We welcome your comments about this document. You can reach us by e-mail at
[email protected]
1. Introduction
1.1. Introduction to the Users Manual
The LUFP1 Gateway Users Manual is organised into a series of chapters, which can in turn be grouped
together into three parts as follows:
Part I:
Chapter 1:
Chapter 2:
Chapter 3:
Chapter 4:
Chapter 5:
Part II:
Chapter 6:
Chapter 7:
Part III:
Appendix A:
Appendix B:
Appendix C:
Appendix D:
Appendix E:
covers all the elements required in order to set up the gateway and operate it on a FIPIO
network.
describes the gateway, the user manual that comes with it and the terms used in it.
gives an introduction to the gateway and describes all the items used when setting it up, both
inside the gateway (coding wheels) and outside (cables and connectors).
describes the six LEDs on the front of the gateway.
describes the successive steps for setting the gateway up with a PLC using FIPIO. You need
to use PL7 PRO to configure the gateway and thus interface a FIPIO master with Modbus
slaves. The example used in this implementation enables the FIPIO master to dialog with 8
TeSys U motor starters.
describes all the FIPIO objects associated with the LUFP1 gateway and which you can use
with PL7 PRO.
is dedicated to a third-party application, ABC-LUFP Config Tool, which enables the gateway
to be configured in greater detail than as set out in Part I. This part therefore supersedes
chapt. 4.
describes an alternative method for configuring the LUFP1 gateway. Rather than using PL7
PRO, the gateway is configured with third-party software known as ABC-LUFP Config Tool,
allowing for more detailed configuration of the LUFP1 gateway. The example used in this
implementation is the same as in Chapter 4.
describes how to use ABC-LUFP Config Tool to create or modify a configuration for the
gateway, but only in the context of an Advanced Implementation of the Gateway. It also
presents the various software functions (add or delete a Modbus slave, add or modify a
Modbus command, etc.) and the changes to be made regarding advanced gateway
implementation operations with PL7 PRO (Chapter 6).
contains the full set of Appendices which supplement the first two parts.
Technical Characteristics describes the technical aspects of both the gateway and the
networks it is interfaced with, namely the FIPIO and Modbus RTU networks.
describes the configuration and adjustment parameters for the LUFP1 gateway.
Standard Configuration describes the main features of the configuration used in the Advanced
Implementation of the Gateway (Chapter 6). However, it does not go into ABC-LUFP Config
Tool in detail.
Sample Use under PL7 PRO provides an example of how the LUFP1 gateway is used, based
on the configuration described in the Software Implementation of the Gateway (Chapter 4).
This example employs the command and control registers for 8 TeSys U motor starters and
uses the gateways indexed periodic variables (PKW) service and list of active slaves (LAS)
service.
Modbus Commands describes the contents of the Modbus command frames supported by the
LUFP1 gateway.
1743315 03/2009
1. Introduction
Quick Access to Critical Information
using
(2) TeSys U Products
(1)
User of
Presentation
of
Hardware
and
Connections
the predefined
(2b) configuration, the nb of
modifying
slaves (< 8)
using
(3)
User of
other Products
the predefined
(2a) configuration
(with 8 slaves)
(2c) new variables
using
via ABC-LUFP
Config Tool
(4)
Managing Loss of Communication

in case of a predefined configuration
(5) Signaling and Diagnostics
(1) Presentation of Hardware and Connections

See Chapter 2
- powering,
- mounting,
- Modbus connecting,
- Profibus connecting,
- Transmission speed and address selecting
(3) User of other Generic Modbus Products

See Chapter 7
(7.6 to 7.11, 7.11.2)
Select between:
- adapting the predefined configuration
provided with the gateway, if close
enough to that you wish (1 register to
read and 1 to write, 1 register address
to change), or
- building up your own configuration
from scratch (see ABC User Manual)
(2) User of TeSys U Products (LUFP1 as a FED C32 P device)

(2a) / (2b) / (2c) Software implementation of the gateway
See Chapter 4 and 5
(2b) reducing the number of slaves

See Chapter 7
with a supplementary request:

- add-up extra commands
- other operations (6.8 to 6.13)
The variables described are:

- Reconnect time
(unit = 10ms, default value = 10s)
- Retries (default value = 3)
- Timeout time
(unit = 10ms, default value = 1s)
(5) Signaling of faults and status, Diagnostics

See Chapter 3
Using ABC-LUFP Config Tool to access

other registers than standard
704 (Command) and 455 (Status)
with the same request:
- replace a register with another (for
instance 455 with 458)
- expand the size (the number of
registers)
1743315 03/2009
See Chapter 4.1.4

and Chapter 7.11.2.2
Using ABC-LUFP Config Tool:

- install (7.2),
- connect (7.1),
- remove slaves (7.7)
(2c) access to new variables

See Chapter 7
(4) Loss of Communication
See Chapter 5.4
See Chapter 7.5

and 7.12.3
Signaling defaults and gateway status

by LEDs on the front
Description of the standard FIPIO
diagnostics objects
ABC-LUFP Config Tool includes the
following features:
- monitoring of the gateway's input,
output, and general memory areas
- activation / deactivation of one or
more Modbus slaves
- diagnostics of the sub-network
(Modbus) with statistics counters
1. Introduction
1.2. Introduction to the LUFP1 Gateway
The LUFP1 gateway allows a master located on a FIPIO network to enter into a dialogue with the slaves on a
Modbus RTU network. This is a generic protocol converter operating in a way which is transparent to the user.
This gateway allows you to interface many products marketed by Schneider Electric with a FIPIO network.
These include TeSys U motor starters, Altivar drivers and Altistart soft start- soft stop units.
1.3. Terminology
Throughout this document, the term user refers to any person or persons who may need to handle or use the
gateway.
The term RTU, which refers to the Modbus RTU communication protocol, will be omitted most of the time. As a
result, the simple term Modbus will be used to refer to the Modbus RTU communication protocol.
As it is still the case with all communication systems, the terms input and output are somewhat ambiguous.
To avoid any confusion, we use a single convention throughout this document. So the notions of input and
output are always as seen from the PLC, or the FIPIO master.
Hence, an output is a command signal sent to a Modbus slave, whereas an input is a monitoring signal
generated by this same Modbus slave.
The diagram below shows the flows of inputs and outputs exchanged between a FIPIO master and Modbus
RTU slaves via the LUFP1 gateway:
NOTE: For more explanation about specific terms, refer to the Glossary at the end of this guide.
1743315 03/2009
1. Introduction
1.4. Introduction to the Communication System Architecture
Each LUFP1 FIPIO / Modbus RTU gateway allows one PLC on the FIPIO network to command, control and
configure up to 8 Modbus slaves. If there are more than 8 Modbus slaves, you will need to use an appropriate
number of LUFP1 gateways. Likewise, if the gateway needs to exchange more than 26 words with the Modbus
slaves (sum of the read and write operations); the Modbus slaves will have to be shared over more than one
gateway.
1743315 03/2009
1. Introduction
The LUFP1 gateway behaves both as a FIPIO slave on the upstream network and as a Modbus RTU master on
the downstream network.
Config Tool
See 7 Using ABC-LUFP

characteristics of the LUFP1 gateway.
if you would like to read about the technical communication
In the context of the Software Implementation of the Gateway, the data exchanges (input and output words)
between the gateway and the Modbus slaves are all periodic. Collectively, these Modbus exchanges form the
gateways Modbus scanner; they are configured using PL7 PRO (by configuring and adjusting the standard
profile FED C32 P). Every item of data exchanged in this way is made available to the FIPIO master, which can
access it periodically and implicitly. The only aperiodic exchanges that can be performed with the
LUFP1gateway on the FIPIO network are explicit exchanges relating to the adjustment parameters and gateway
status parameters.
The gateway has a configuration and adjustment service called PKW, which offers read-write access to any
Modbus slave parameter via the periodic input and output of the LUFP1 gateways. This service is aperiodic on
the Modbus network and periodic on the FIPIO network. It can be used for the following tasks:
Retrieving or updating the parameters on some or all of the Modbus slaves;
Reading the value of one or more data for which a low refresh rate is sufficient;
Reading the value of a data item when an event is signalled by a periodic variable.
One of the gateway input words informs the FIPIO master of the presence or absence of each Modbus slave.
The input word in question is the LAS service.
The diagram illustrates the distribution of several slaves throughout three Modbus RTU downstream networks,
each one being interfaced with the FIPIO master PLC using a LUFP1 gateway.
1.5. Principle of LUFP1 Gateway Configuration and Operation

The gateway is part of a family of products (referred to as LUFP ) designed to meet generic needs for
connection between two networks using different communication protocols.
The software elements common to all these gateways (a configuration tool known as ABC-LUFP Config Tool
and the embedded Modbus software) cohabit with the specific features of the network upstream of each of them
(FIPIO in the case of the LUFP1 gateway) generically. This is one of the reasons why the interfacing between
the upstream network and the Modbus network is carried out entirely via the gateways physical memory. In the
case of the LUFP1 gateway, however, using a standard FIPIO profile (FED C32 P) in PL7 PRO makes it easier
to configure the gateway, dispensing with the need to use ABC-LUFP Config Tool.
Exchanges between the gateway (acting as the Modbus master) and the Modbus slaves are configured
bythe gateway, using the configuration and adjustment parameters of profile FED C32 P entered by the
user in PL7 PRO. Thanks to this configuration, the gateway creates links between part of the contents of
the corresponding Modbus frames and the contents of its physical memory (input memory for the
contents of the Modbus responses and output memory for the contents of the queries).
The periodic exchanges between the FIPIO master PLC and the LUFP1 gateway are limited to
transferring the contents of the gateways input memory to the %IW inputs on the PLC and transferring
the PLCs %QW outputs to the gateways output memory.
Each LUFP1 gateway is delivered so that it must be configured using PL7 PRO instead of ABC-LUFP
Config Tool. But this configuration is blank because it will be configured by the master PLC itself when
the FIPIO network is initialised. Hence, it is absolutely necessary to use PL7 PRO to configure the FED
C32 P device that corresponds to the LUFP1 gateway (see chapter 4.2).
10
1743315 03/2009
1. Introduction
The FIPIO network is totally separate from the Modbus network. The frames on a network are not directly
translated by the gateway to generate frames on the other network. Instead, the exchanges between the
contents of the gateways memory and the Modbus slaves make up a system independent of the one entrusted
with managing the exchanges between the gateway memory and the FIPIO master.
The example which follows illustrates the independent management of each of the two networks:
Managing Gateway Modbus slaves exchanges (FED C32 P)
(1)
The sum of Input Data and Output Data is limited to 26 words max.
1743315 03/2009
11
2. Hardware Implementation of the LUFP1 Gateway

2.1. On Receipt
After opening the packaging, check that you have an LUFP1 FIPIO / Modbus RTU gateway equipped with a
detachable power connector.
2.2. Introduction to the LUFP7 Gateway

The cables and other accessories for connecting to FIPIO and Modbus networks need to be ordered separately.
Legend:
12
Detachable power connector for the

24V 10%).
gateway (
Female RJ45 connector to a PC

running ABC-LUFP Config Tool
configuration software.
Female RJ45 connector for the

downstream Modbus RTU network.
Six diagnostic LEDs.
Removable cover for the coding

wheels used to configure the gateway,
shown and described in chapter 2.7.
The label describing the LEDs is stuck
onto this cover.
Female FIPIO connector.
1743315 03/2009

The LUFP1 enables communications between a FIPIO network and Modbus devices for the purpose of industrial
automation and control. As with any component used in an industrial control system, the designer must evaluate
the potential hazards arising from use of the LUFP1 in the application.
WARNING
LOSS OF CONTROL
The designer of any control scheme must consider the potential failure modes of control paths and, for
certain critical control functions, provide a means to achieve a safe state during and after a path failure.
Examples of critical control functions are emergency stop and overtravel stop.
Separate or redundant control paths must be provided for critical control functions.
System control paths may include communication links. Consideration must be given to the implications of
unanticipated transmission delays or failures of the link. a
Each implementation of an LUFP Gateway must be individually and thoroughly tested for proper
operation before being placed into service.
Failure to follow this instruction can result in death, serious injury, or equipment damage.
a
For additional information, refer to NEMA ICS 1.1 (latest edition), Safety Guidelines for the Application, Installation, and Maintenance of Solid
State Control and to NEMA ICS 7.1 (latest edition), Safety Standards for Construction and Guide for Selection, Installation and Operation of
Adjustable-Speed Drive Systems.
2.3. Mounting the Gateway on a DIN Rail

Mounting the gateway
Removing the gateway
Start by fitting the rear base of the gateway to the

upper part of the rail, pushing downwards (1) to
compress the gateways spring. Then push the
gateway against the DIN rail (2) until the base of the
gateway box fits onto the rail.
Start by pushing the gateway downwards (1) to

compress the gateways spring. Then pull the
bottom of the gateway box forwards (2) until the box
comes away from the rail.
NOTE: The spring is also used to ground the gateway (Protective Earth).
1743315 03/2009
13

2.4. Powering the Gateway
FIPIO / Modbus RTU gateway View from underneath
+
Power supply
24V isolated (10%)
95 mA max.
WARNING
RISK OF UNINTENDED EQUIPMENT OPERATION
Do not use the 24 VDC power available from the FIPIO network cabling to operate the LUFP Gateways, as
the negative terminal () of this power is not necessarily at the installation earth ground potential. Use of an
ungrounded power supply may cause the LUFP devices to operate in an unexpected manner.
To ensure reliable operation, the LUFP Gateways require a separate power supply where the negative
terminal () is connected to the installation earth ground.
Recommendations:
Use 60/75 or 75xC copper (CU) wire only.

The terminal tightening torque must be between 5-7 lbs-in (0.5-0.8 Nm).
2.5. Connecting the Gateway to the Modbus Network

Three typical examples of Modbus connection for the gateway and its slaves are shown below. There are many
other possible Modbus connections, but they are not covered in this document.
14
1743315 03/2009

2.5.1. Examples of Modbus Connection
Star topology: This topology uses LU9GC03 Modbus hubs, which have 8 female RJ45 connectors.
These hubs should be placed close to the Modbus slaves to which they are connected using VW3 A8 306 R
cables. On the other hand, the nature of the cable connecting the LUFP1 gateway to one of these hubs will
depend on the network architecture, so long as there is a male RJ45 connector at each end. If necessary, one or
two line terminations may be directly connected to the hubs.
The connections are shown below:
1743315 03/2009
15

Bus topology with VW3 A8 306 TF3 drop boxes: This topology uses VW3 A8 306 TF3 drop boxes to
connect each of the Modbus slaves to the main section of the Modbus network. Each box should be placed in
the immediate vicinity of the Modbus slave it is associated with. The cable for the main section of the Modbus
network must have male RJ45 connectors (like the VW3 A8 306 R cable used for the star topology). The lead
between the drop box and the slave or the Modbus gateway is an integral part of this box.
16
1743315 03/2009

Bus topology with tap boxes: This topology is similar to the previous one, except that it uses TSXSCA62
subscriber connectors and / or TSXCA50 subscriber connectors. We recommend using a VW3 A68 306
connection cable and the TSXCSA00 Modbus cables. Connect the RJ45 connector on the VW3 A68 306 cable
to the Modbus connector on the LUFP1 gateway.
VW3 A68 306
TSXSCA62
Modbus
LUFP1 Gateway
TSXCSA00
2.5.2. Pin Outs

In addition to the pin out for the connector on the gateway, the one on the VW3 A68 306 cable is also shown
below, as it is the only Modbus cable which does not exclusively use RJ45 connections.
LUFP1 connector
Female RJ45
Male RJ45
Male 15-point SUB-D
1
2
D(B)
D(B)
14 D(B)
D(A)
D(A)
0V
1743315 03/2009
VW3 A68 306 cable for TSXSCA62 box
0V
D(A)
15 0V
17

2.5.3. Wiring Recommendations for the Modbus Network
Use a shielded cable with 2 pairs of twisted conductors,
connect the reference potentials to one another,
maximum length of line: 1,000 meters (3280 ft)
maximum length of drop line / tap-off: 20 meters (65.5 ft)
do not connect more than 9 stations to a bus (slaves and one LUFP1 gateway),
WARNING
Do not connect more than 9 stations to the Modbus fieldbus (gateway and 8 slaves). While the gateway
may appear to operate correctly with more than 9 devices, it is likely one or more devices will only
communicate intermittently, leading to unpredictable system behavior.
cable routing: keep the bus cable away from power cables (at least 30 cm (0.98 ft)), make crossings at
right angles if necessary, and connect the cable shielding to the earth on each unit,
adapt the line at both ends using a line terminator (see diagram and VW3 A8 306 RC termination below).
D(B)
D(A)
120
1 nF
Line termination recommended at both ends of the line
VW3 A8 306 RC line termination
WARNING
MODBUS TERMINATION USING THE RESISTANCE-ONLY METHOD
Use only RC (Resistance-Capacitance) Modbus cable terminations with the LUFP1 Gateway. The LUFP
gateways are designed to support client equipment that will not function correctly without using RC-type
Modbus cable termination.
18
1743315 03/2009

To make it easier to connect the units using the topologies described in chapter 2.5.1, various accessories are
available in the Schneider Electric catalogue:
1) Hubs, junctions, and line terminations:
LU9GC03 hub ..........................................................This passive box has 8 female RJ45 connectors. Each of
these connectors can be connected to a Modbus slave, to
(bus topology with LU9GC03 splitter boxes)
a Modbus master, to another Modbus hub, or to a line
termination.
VW3 A8 306 TF3 T-junction box ..............................This passive box includes a short lead with a male RJ45
(bus topology with VW3 A8 306 TF3 T-junction connector allowing it to be connected directly to a Modbus
boxes)
slave, without having to use a different cable. It is fitted
with 2 female RJ45 connectors for the connection of two
Modbus cables of the VW3 A8 306 R type.
2-way TSXSCA62 subscriber connector..................This passive box has a printed circuit fitted with screw
(bus topology with SCA junction boxes)
terminals and allows the connection of 2 subscribers to
the bus (2 female 15 point SUB-D connectors). It includes
the line termination when the connector is located at the
end. It is fitted with 2 screw terminals for the connection of
two double twisted pair Modbus cables.
TSXCA50 SCA junction box.....................................This passive box allows a Modbus unit to be connected to
a screw terminal. It includes the line termination when the
connector is located at the end. It is fitted with 2 screw
terminals for the connection of two double twisted pair
Modbus cables.
VW3 A8 306 RC double termination ........................Each of these two red passive boxes is a male RJ45
(all topologies)
connector 3 cm (1.18 in) long containing an RC line
termination (see diagram and illustration above). Only the
abbreviation RC is shown on these boxes.
2) Cables:
VW3 A8 306 R Modbus cable................................Shielded cable with a male RJ45 connector at each end.
VW3 A68 306 Modbus cable....................................Shielded cable with a male RJ45 connector and a male
15 point SUB-D connector. It is used to connect a Modbus
subscriber (slave or master) to a TSXSCA62 or TSXCA50
box.
Shielded double twisted pair Modbus cable.............Bare cable (without connectors) used to make up the
(bus topology with branch boxes)
main section of the Modbus network. There are three
items available: TSXCSA100 (100 m or 328 ft),
TSXCSA200 (200 m or 656 ft), and TSXCSA500 (500 m
or 1640 ft).
1743315 03/2009
19

2.6. Connecting the LUFP7 gateway to the Profibus-DP Network
Connect the SUB-D 9-point male plug on
the FIPIO connector to the FIPIO plug on
the LUFP1 gateway.
Connections are illustrated here:
2.6.1. Pin Outs

LUFP1 plug
9-point SUB-D female
1
2
3
4
5
Signal (+) 6
Signal (-)
7
8
9
Grounding / Shielding
TSX FPACC12 connector

9-point SUB-D male
1
2
3
4
5
6
FIP cables
(TSX FP CA )
Incoming main cable
Signal (+)
Outgoing main cable
7 Signal (-)
8
9
Shielding / Grounding
NOTE: If the two main cables are replaced by a TSX FP CC tap-off cable, the red and orange wires
correspond to the signal (+), while the green and black wires correspondent to the signal ().
20
1743315 03/2009

2.6.2. Wiring Recommendations for the FIPIO Network
Use TSX FP ACC 12 connectors (or TSX FP ACC 2 in the case of TSX 17-20 micro-PLCs) to connect the
gateway to the FIPIO network.
Use a TSX FP CA main FIPIO cable to link up the connectors and a TSX FP CC FIPIO tap-off cable
if you need to connect up to a tap box (TSX FP ACC 14, TSX FP ACC 3, TSX FP ACC 4 or TSX FP ACC
10). Both of these shielded cables are available in lengths of 100, 200 or 500 meters.
Use two line terminations to close off the FIPIO network at both ends of each electrical segment. The TSX
FP ACC 7 kit includes two FIP terminations.
Connect the reference potentials to one another.
The transmission rate is fixed at 1 Mbit / s.
Use TSX FP ACC 6 repeaters to connect up two electrical segments on the same FIPIO network. The
maximum length of an electrical segment is 1,000 m. Follow this rule:
[ (Number of repeaters 2) + Sum of lengths (in km) ] < 22
The longest FIPIO network that can be implemented under this rule would be 15 km long and would
require 14 repeaters (14 2 + 15 = 22).
Do not connect more than 32 master or slave stations per segment (not counting repeaters).
Cable routing: keep the bus away from power cables (at least 30 cm), make crossings at right angles if
necessary and connect the cable shielding to the earth on each unit.
For more details about connections, see the FIPIO Bus / FIPWAY Network Reference Manual
(ref. TSX DR FIP F for the French version, TSX DR FIP E for the English version, TSX DR FIP G for the German
version and TSX DR FIP S for the Spanish version). This manual also contains details on the operating
characteristics and implementation of a FIPIO field bus.
In addition, the manual Electromagnetic Compatibility of Industrial Field Buses and Networks
(ref. TSX DGKBL F for the French version, ref. TSX DGKBL E for the English version and ref. TSX DGKBL G for
the German version) contains valuable rules and precautionary measures for wiring up a FIPIO field bus.
A number of accessories are available from the Schneider Electric catalogue to facilitate the connection of
stations on a FIPIO network:
1) Connectors, tap boxes and line terminations:
TSX FP ACC 12 connector ....... Isolating connector for equipment with a 9-pin female SUB-D connector.Used
for daisy-chain or parallel cabling (see illustration on next page).
TSX FP ACC 2 connector ......... Female connector for the TSX FPG 10 coupler (TSX 17-20 micro-PLCs).
Used for daisy-chain or parallel cabling.
TSX FP ACC 14 box ................. Isolating tap box for bus connections to the main cable.
TSX FP ACC 4 box ...................
TSX FP ACC 10 box
Watertight tap boxes for bus connections to the main cable. They alsosupport
one 9-pin female SUB-D connector (for the PCMCIA card cable TSX FP CG
010 / 030).
TSX FP ACC 3 box ................... Isolated tap box for bus connections to the main cable. Also supports two 9pin female SUB-D connectors (as above).
TSX FP ACC 7 terminations ..... Set of two line terminations for adapting the impedance of both ends of an
electrical segment. You will need one set per electrical segment.
TSX FP ACC 6 repeater............ Electrical repeater for joining two segments, each with a maximum length of
1,000 m.
1743315 03/2009
21

2) Cables:
TSX FP CA main cable......................Shielded twisted 150 cable with a single pair of conductors: red (+)
and green (). In lengths of 100, 200 or 500 m. This cable is the main
trunk of the FIPIO network and is therefore used to link up connectors
and tap boxes.
TSX FP CC tap link cable...................Shielded twisted 150 cable with two pairs of conductors: red or
orange (+), and green or black (). In lengths of 100, 200 or 500 m.
This cable is used to connect a tap box to a distant connector.
NOTE: When calculating the length of a FIPIO segment, remember to
multiply the length of the cable by two.
The illustration opposite shows the wiring in the TSX FP
ACC 12 connector when connecting up to the main cable
(two sections of TSX FP CA cable).
Replace one of the two cables by one of the two
lineterminations supplied in the TSX FP ACC 7 kit, if the
connector is at the end of an electrical segment.
Replace the two cables (A) and (B) by a TSX FP CC
cable (in (A)) if the connection point is a derivation rather
than a daisy-chain link; if so, the orange wire corresponds
to the (+) signal of the second pair of conductors and the
black wire corresponds to the () signal.
2.6.3. FIPIO Bus Commissioning Procedure

We recommend commissioning the devices in sequence, one after the other. For a detailed description of the
initial commissioning of an application on FIPIO, see the FIPIO Bus / FIPWAY Network Reference Manual.
22
1743315 03/2009

2.7. Configuring the FIPIO Communication Features
This configuration must be carried out when the gateway is powered off.
CAUTION
OPENING LUFP COVER WITH POWER ON
The power supply of the gateway must be turned off before opening the cover. Once the cover has been
removed, make sure you touch neither the electrical circuits nor the electronic components, as this may
damage the device.
Failure to follow this instruction can result in injury or equipment damage.
This task is limited to configuring the gateway's FIPIO address, as the communication speed on the FIPIO
network is fixed at 1 Mbit/s.
The two coding wheels used for configuring the gateways address are hidden behind the gateway cover g (see
illustration in chapter 2.2). To remove this cover, insert the end of a small flat screwdriver between the top of the
hood and the gateway box and pull it out.
2.7.1. Encoding the Gateway Address

The LUFP1 gateway is identified on the Profibus-DP bus by its address, ranging from 1 to 99.
On FIPIO, address 0 is reserved for the PLC that manages the bus. Address 63 is reserved for the programming
or operation terminal. All the other addresses, up to physical address 127, can be used.
Units
Tens
1743315 03/2009
The gateway's FIPIO address depends on the position of the two coding
wheels represented on the left, in their factory-setting positions (default
address = 2).
This address is the sum of the decimal values given by the angular
positions of the bottom coding wheel (tens) and the top coding wheel
(units).
23

Any change to the gateway's address shall be taken into account only once it is powered on again.
NOTE:
No two devices on the same FIPIO bus can ever have the same address. Simultaneous, fast (2 Hz) and
continuing flashing of LEDs n, o, pand qmeans that the device cannot connect to the FIPIO bus
because the address is already used by another device.
This flashing signal also occurs when address 00 is configured using the gateways coding wheels.
Examples:
Address = 19
Units
Tens
24
Address = 73
Units
Tens
1743315 03/2009
3. Signaling
The gateways 6 LEDs and the descriptive label on the removable cover which hides its two coding wheels
(gateway address) allow you to diagnose the status of the gateway:
NOTE:
all flash at the same time at a
If LED does not flash from red to green and if LEDs
frequency of 2 Hz, this means that the physical gateway address is already used by another FIPIO
device, or that it has been set at 0 with the gateways coding wheels.
Try to resolve this address conflict by viewing the FIPIO network configuration in PL7 PRO. If necessary,
modify the addresses in the configuration. Also check the physical address configured on the gateway
using the coding wheels (see Section 2.7.1).
If both identically-addressed devices are reconnected to FIPIO network simultaneously, then the four
will flash, and then only discontinuously
LEDs mentioned above will not flash. In this case, only LED
and in an irregular manner. This happens, for example, when you disconnect and then reconnect the
bus arbitrator.
1743315 03/2009
25
4. Software Implementation of the Gateway

4.1. Introduction
This chapter presents the implementation of the LUFP1 gateway in PL7 PRO, with a Schneider Electric
Premium PLC (e.g. PLC TSX 57353 v5.1) acting as master and FIPIO bus arbitrator via the FIPIO link built into
its processor card.
NOTE: The various configuration possibilities for Modbus exchanges on the gateway are not covered in this
section, as the aim here is to describe a standard configuration with 8 TeSys U motor starters. This configuration
is described with a view to implementing the gateway using PL7 PRO. The full range of gateway configuration
possibilities is set out in Appendix B
4.1.1. System Architecture
The configuration described in this LUFP1 gateway implementation enables the device to command and control
eight TeSys U motor starters:
See Chapter 2 for details on implementing the hardware for the standard configuration.
26
1743315 03/2009

4.1.2. Configuring the Motor Starters
Each motor starter should be configured as follows:
Protocol:
Modbus address
Bitrate
Data bits
Modbus RTU slave

1 to 8
19,200 bits/s
8
Start bits
Parity
Parity bit
Stop bits
1
None
0
1
When using a TeSys U motor starter with a Modbus communication module (LULC03 module), the
configuration parameters for the RS485 connection are automatically detected, only the Modbus address of the
motor starter needs to be configured.
NOTE: The gateways Modbus slaves cannot be configured with PL7 PRO; the configuration and adjustment of
the LUFP1 gateway are limited to the gateway and to the management of generic Modbus exchanges.
4.1.3. Modbus Cycle Time
The LUFP1 gateways default configuration sets a cycle time of 300 ms on Modbus commands for each of the
8 TeSys U motor starters.
4.1.4. Managing Degraded Modes With the Gateway Default Configuration

The degraded-mode management of the LUFP1 gateway standard configuration is described below. In this
instance, we are using a Premium PLC with a FIPIO link built into the processor card.
(1) The desired behavior with regard to outputs should be directly configured on each TeSys U motor starter.
(2) Use the List of Active Slaves (LAS) Service described in Section 5.2.
(3) Use the FIPIO Diagnostic Objects (Section 5.4) to detect the underlying event.
Please refer to Appendix B if you would like to change the way that degraded modes for all Modbus commands
are managed.
4.1.4.1. Description of the Gateway Degraded Mode Options

%MW\p.2.c\0.0.23 (bits 0-7): Effects on Modbus exchanges
This parameter affects the data sent to all Modbus slaves if there is no communication from the FIPIO master.
1743315 03/2009
27

This parameter can take 3 values:
0x00 ...... Freeze: All data sent retains its current values.
0x01 ...... No scanning: No more Modbus queries are transmitted.
0x02 ...... Clear: All data sent to the Modbus slaves is reset to 0.
The default behavior for the gateway's standard configuration described here is Clear. Hence, the TeSys U
Command (704) and Status (455) registers continue to be refreshed, but:
The corresponding gateway's output memory (TeSys U Command registers) is forced to 0,
And the corresponding gateway's input memory (TeSys U Status registers) is normally refreshed.
%MW\p.2.c\0.0.21 (bits 0-7): Modbus timeout time (unit: 100 ms)
This parameter defines the time the gateway will wait for a response before it either retries sending the same
request, or it disconnects the slave and declares it missing.
The same Modbus timeout time is applied to all Modbus commands.
In the gateways standard configuration, described here, this time is equal to 300 ms (3 100 ms).
%MW\p.2.c\0.0.21 (bits 8-15): Retries
This parameter determines the number of re-transmissions carried out by the gateway if there is no response
from a Modbus slave.
The same number of retries is used for all Modbus commands.
In the gateways standard configuration, described here, this parameter is set to 3.
%MW\p.2.c\0.0.22 (bits 0-7): Reconnection time (unit: 1 s)
This parameter defines the amount of time the gateway will wait before it again tries to communicate with a
Modbus slave that was previously declared missing.
The same reconnection time is applied to all Modbus slaves.
In the gateways standard configuration, described here, this time is equal to 10 s (10 1 s).
! WARNING
During the reconnect time, you cannot control a slave (read/write) via the bus. Depending on the slave
characteristics and the watchdog configuration, the slave can keep the same status or take a fallback position.
To avoid an unintended equipment operation, you must know the possible status of a slave and adapt the timeout
and reconnect time values according to the request sending rate.
%MW\p.2.c\0.0.23 (bits 8-15): Effects on FIPIO exchanges
This parameter affects the data sent to the FIPIO master if there is no response from a slave or if a slave is absent.
It is defined for all Modbus slaves, but only the data related to an absent slave is affected.
This parameter can have 2 values:

0x00 ...... No action: All data sent to the FIPIO master retains its current values.
0x02 ...... Clear: All data sent to the FIPIO master are reset to 0.
The default behavior for the gateway's standard configuration described here is Clear. Hence, any TeSys U
status register is forced to 0 if the corresponding TeSys U motor starter is missing.
4.1.4.2. Degraded Mode Description
This description takes into account the following elements, but only applies to the standard configuration
described here:
The PLC processor
The FIPIO master
28
1743315 03/2009
The LUFP1 gateway

The Tesys U starters-controllers.
PLC processor stopped or on failure

PLC processor response
Outputs:
Software error: outputs reset to default state or hold their present state depending on
configuration.
Hardware error: (EEPROM or hardware failure), output state will be undetermined.
Inputs:
PLC stops responding to inputs in any error state.
FIPIO master response
Depending on FIPIO master configuration:
the FIPIO master stops to communicate with the LUFP1 gateway, or
the FIPIO master forces outputs to 0, and refreshes inputs, or
the FIPIO master holds outputs in their last position, and refreshes inputs.
LUFP1 gateway response
If the FIPIO master stops communicating with the LUFP1 gateway (case of a Premium PLC), the
periodic Modbus exchanges continue to run:
all output data is reset to 0 and sent to the Modbus slaves,
the input memory continues to be refreshed with the Modbus slaves' response data.
If the FIPIO master forces outputs to 0 and refreshes the inputs, the periodic Modbus exchanges
continue to run:
the input memory continues to be refreshed with the Modbus slaves' response data..
If the FIPIO master forces holds outputs in their last state and refreshes the inputs, the periodic
Modbus exchanges continue to run:
Tesys U response
If the FIPIO master stops communicating with the LUFP1 gateway (such as in the case of a Premium
PLC) or forces outputs to 0, the periodic Modbus exchanges continue to run:
Command registers (704) are forced to 0 and the motors are stopped,
Status registers (455) are transmitted to the gateway.
If the FIPIO master keeps outputs in their last state, the periodic Modbus exchanges continue to run:
Command registers (704) keep their last values and the motors rest in the same state,
FIPIO master stopped or on failure
The PLC processor provides some error and/or diagnostic objects to the application in case of FIPIO
master stop or failure (input/output not valid).
Refer to the PLC user manual to have their description.
This information must be managed in the PLC application.
If the Profibus master is stopped (command coming from the application):
the master stops to communicate with the LUFP1 gateway.
Periodic Modbus exchanges continue to run:
1743315 03/2009
29

Tesys U response
Periodic: Modbus exchanges continue to run:
LUFP1 gateways disconnected on FIPIO side
The PLC processor provides some error and diagnostic objects coming from the FIPIO master in case
of slave disconnection from the application:
The FIPIO master provides the processor with some error and diagnostic objects in case of FIPIO
slave disconnection.
the input memory continues to be refreshed with the data of the Modbus slaves' responses.
Tesys U response
LUFP1 gateways failure
The PLC processor provides some error and diagnostic objects coming from the FIPIO master in case
of slave failure to the application.
This information must be managed in the PLC application
The FIPIO master provides the processor with some error and diagnostic objects in case of FIPIO
slave failure.
In case of a failure, the gateway stops to communicate with the FIPIO master and the Modbus slaves.
Tesys U response
Depending on the Tesys U configuration:
If the starters-controllers do not receive any requests, they will:
stop the motor,
keep the same state, or
run the motor.
Refer to the Tesys U user manuals to adjust these fallback positions.
30
1743315 03/2009

LUFP1 gateways disconnected on Modbus side or Tesys U failure
The processor has access to the List of Active Slaves (LAS) from the FIPIO master input table.
This word must be managed in the PLC application in order to detect if a Modbus slave is missing.
The FIPIO master continues communicating with the PLC processor and the LUFP1 gateway.
With the gateways standard configuration described here:
Modbus timeout time = 300 ms,
Retries = 3,
Reconnection time = 10 sec, and
Effects on FIPIO exchanges = Clear.
After sending a request to a slave, if there is no response after 300 ms, the gateway will send it again
three more times before providing information about the missing slave in the List of Active Slave
(LAS). If, despite the three retries, there is no answer from the slave, the input data sent to the FIPIO
master (Read requests) is reset to 0, but only for the data received from the missing slave. The
gateway will try to reconnect the missing slave by communicating with it again every 10 seconds.
Tesys U response
If the LUFP1 gateway is disconnected on Modbus side:
The starters-controllers do not receive any requests, depending on their configuration, they will:
stop the motor,
keep the same state, or
run the motor.
Refer to the Tesys U user manuals to adjust the fallback position.
In case of a Tesys U failure:
No response is sent to the gateway, the motor state will be undetermined.
This case must be managed in the PLC application.
4.2. Gateway Configuration under PL7 PRO

The following sections describe the configuration steps in PL7 PRO that you will need to go through to ensure
that the gateway is correctly recognized by the FIPIO master PLC and that it can command and control the 8
motor starters in the standard configuration described earlier.
4.2.1. WorldFIP Mode
The LUFP1 gateway supports the WorldFIP mode, configured via the FIPIO bus properties in PL7.
4.2.2. Adding the LUFP1 Gateway under PL7 PRO
Open the hardware configuration of your application and edit the FIPIO network configuration by doubleclicking
on the PLC processor card (TSX 57353).
Add the FIPIO device corresponding to the LUFP1 gateway by double-clicking the first free connection point. In
the window that appears, select the family STD_P and the basic module for that family, FED C32 P.
You also need to enter the physical address of the gateway on the FIPIO bus in the field Connection point
number. Entering a Comment is optional, but it does make it easier to pick out the gateway from among the
other devices on the same FIPIO bus.
1743315 03/2009
31
32
1743315 03/2009

4.2.3. Configuring and Adjusting the LUFP1 Gateway
Once the gateway has been added to the
FIPIO network (see opposite), double-click
the basic module
to edit its configuration and adjustment
parameters.
In the window that appears, enter the values
given on the next two pages. These
correspond to the configuration described in
Section 4.1.1.
NOTE: Make sure you configure the Bus Length correctly (see Section 2.6.2).
NOTE: The FED C32 P [FIPIO2 MODULE 0] windows shown above present Symbols which have been
added manually using the PL7 PRO variables editor. By default, no symbol is attributed to the gateways
configuration parameters (%KW) or adjustment parameters (%MW).
1743315 03/2009
33

All the configuration and adjustment parameters described in the following sections are an integral part of the
PLC application. The FIPIO master PLC will transmit these parameters to the gateway implicitly via the FIPIO
bus whenever either of the two following events occurs:
The PLC goes into RUN mode.
The gateway is disconnected from and reconnected to the FIPIO network.
NOTE:
The gateway configuration possibilities offered by the FED C32 P model are limited to the gateway itself;
it cannot be used to configure the Modbus slaves.
If you want to configure the Modbus slaves, you will need to use a different method (local configuration
or remote configuration with a software tool such as PowerSuite, for example).
4.2.4. Selecting and Adding the Profibus-DP Master Station
34
1743315 03/2009
Syntax:
p = processor position (0 or 1);

c = connection point number (gateway address).
For modifications to these adjustment parameters, see Appendix B.

However, during the Software Implementation of the Gateway, you will probably find it useful to know how to
delete one or more TeSys U motor starters. This operation is therefore described in Section 4.2.6.
4.2.5. Adjustment Parameter Values, Standard Configuration
Syntax:

1743315 03/2009
35

WARNING
Do not confuse the order of configuration of the Modbus slaves with their Modbus addresses.
In the configuration shown in parameters %MW\p.2.c\0.0.31 to %MW\p.2.c\0.0.34 the order numbers of the
Modbus slaves (1 to 8) are identical to the addresses of the corresponding TeSys U motor starters (Modbus
addresses 1 to 8).
For modifications to these adjustment parameters, see Appendix B.
However, during the Software Implementation of the Gateway, you will probably find it useful to know how to
delete one or more TeSys U motor starters. This operation is therefore described in Section 4.2.6.
4.2.6. Deleting One or More TeSys U Motor Starters from the Configuration
We will just look at one modification operation on the standard 8 TeSys U motor starter configuration: the
deletion of one or more motor starters. The 8 motor starters were configured to represent the typical maximal
configuration (a maximum of 8 Modbus slaves).
It is best to delete any slaves absent from your configuration in order to avoid any degradation in performance
that might be caused by the physical absence of motor starters declared in the LUFP1 gateway configuration.
Make the following changes to the Configuration Parameter Values, Standard Config (Section 4.2.4) and to the
Adjustment Parameter Values, Standard Configuration (Section 4.2.5):
For each absent TeSys U motor starter, reset to zero the number of periodic command words
(%KW\p.2.c\0.0.0 and %KW\p.2.c\0.0.1) and the number of periodic control words (%KW\p.2.c\0.0.2 and
%KW\p.2.c\0.0.3) on a single slave, starting with slave n8 and working back towards slave n1.
For each absent TeSys U motor starter, two of the addresses of periodic words n1 to 16
(%KW\p.2.c\0.0.4 to %KW\p.2.c\0.0.19) will become Not used parameters, starting with n16 and
working back towards n1. These two words comprise a command word / control word pair, which
means that you have to delete the last command word, shift the control words along by one parameter,
and then delete the last control word.
Check the mappings between Modbus slaves n1 to 8 and the addresses of the TeSys U motor starters
in your configuration (%MW\p.2.c\0.0.31 to %MW\p.2.c\0.0.34). For each absent motor starter, one of
the slaves will take the value 0x00 as its Modbus address, starting with slave n8 and working back to
n1.
36
1743315 03/2009

Example: Deletion of the motor starters corresponding to Modbus addresses 1, 3, 4 and 8. The starters at
Modbus addresses 2, 5, 6 and 7 will remain present. The new configuration and settings for the gateway are as
follows:
1743315 03/2009
37

4.2.7. Configuring Gateway Inputs / Outputs
The settings described in the previous sections enable the gateway to establish a Modbus scanner made up of
periodic write commands (commands) and read instructions (controls), which are sent out to the Modbus
slaves.
Each control word corresponds to a Modbus periodic read instruction, and each command word to a Modbus
periodic write command. Each word also corresponds to a gateway input or output. All of these inputs and
outputs are defined by the gateway by means of its configuration parameters (%KW): the periodic control words
correspond to the inputs, and the periodic command words to the outputs.
The gateway establishes the following correspondences between its inputs / outputs and the values of its
periodic command / control words:
38
1743315 03/2009

For the standard configuration presented here, the mapping between the gateway inputs and the PLC inputs is
as follows:
Likewise, the PLC outputs correspond to the gateway outputs as follows:
1743315 03/2009
39

4.2.8. Description of Services Assigned to Gateway I / O
On the FIPIO network, all the inputs / outputs that correspond to the gateway are periodic; the same is not true
of the Modbus network. There are therefore two types of service: periodic services and aperiodic services.
All of these services correspond to FIPIO objects. For a more detailed description, see Chapter 5.
Periodic communications (inputs): For the configuration described here, the value of each of the first 8
gateway input words corresponds to the value of the status register of a TeSys U motor starter (register located
at address 455).
Periodic communications (outputs): Likewise, the value of each of the first 8 gateway output words
corresponds to a value to be sent to the command register of a TeSys U motor starter (register located at
address 704).
The FIPIO objects corresponding to the gateways periodic Modbus communications are described in Section
5.1.
See also Command and Control of the 8 TeSys U Motor Starters in Appendix D for an example of how these
periodic communications services are used with the type of configuration adopted in this gateway
implementation (8 TeSys U devices).
If you delete any motor starters from the configuration, you will need to adjust the two tables on the previous
page accordingly.
Aperiodic communications: The aperiodic communications service operates in the same way as the indexed
periodic variables, or PKW, service found on a number of other Schneider Electric products, such as some ATV
drives. Hence the service continues to use the name PKW.
The FIPIO objects corresponding to the gateways aperiodic Modbus communications are described in Section
5.3.
See also Using the Indexed Periodic Variables (PKW) Service in Appendix D for an example of the simplified
use of the gateways aperiodic communications service.
List of active slaves (LAS): This service is specific to the gateway, and does not generate any communications
over the Modbus network. That is why it is named differently from the other gateway inputs / outputs (periodic or
aperiodic communications). Each bit (from 0 to 7) of the input word indicates the absence or presence of a
Modbus slave (slaves n1 to 8, in that order).
The only FIPIO object corresponding to the list of active slaves service is described in Section 5.2.
40
1743315 03/2009

4.2.9. Validating and Saving the FIPIO Network Configuration
4.2.10. Assigning Symbols to the Gateways FIPIO Objects

It is advisable to assign symbols to the gateways inputs and outputs: this makes it easier to understand the PLC
application that will be managing them. Edit I / O variables using PL7 PRO, and select the address \0.2.2\0:
FED C32 P if, for example, the gateway is located at address 2.
You can also assign symbols to the configuration and adjustment parameters described in the previous sections,
as well as to the gateways FIPIO diagnostic objects, but this is not as useful as it is for the inputs and outputs.
Once defined, these symbols are used in the various FED C32 P profile configuration and monitoring windows.
1743315 03/2009
41

4.2.11. Checking the Operational Status of the Gateway
After validating any changes made, you must send the new configuration and adjustment parameters for profile
FED C32 P to the corresponding gateway by downloading the PL7 PRO application to the PLC. Then check that
the gateway has been duly recognized on FIPIO by the PLC, by viewing its status in the FIPIO network
configuration window.
In the example shown here, the

connection point is signaling an error
(and is therefore in red). If this
happens, open the debug window by
double-clicking the basic module
In this window, click on the two red

DIAG buttons.
The table below sets out the
procedure to be followed in the two
most likely instances:
NOTE: Neither of these configuration errors will be signaled by the gateway (its LEDs will indicate normal
operation). It is therefore essential that you perform the foregoing checks.
42
1743315 03/2009

4.2.12. Modifying the Gateway Parameters in ONLINE Mode
The modification of one or more configuration and / or adjustment parameters in
mode will
momentarily bring the gateway to a halt (for complete reconfiguration of the Modbus scanner). This interrupts the
periodic Modbus communications, but for such a brief period of time that the Modbus slaves are unlikely to
detect it, even if they have very short communication timeouts.
4.2.13. Debugging and Using the Gateway Configuration

mode, open the gateway debug window by double-clicking the basic module
While in
.
This window displays the gateway diagnostics (see previous page), and the values of the gateway inputs or
outputs (selected using the scroll bar in the Variables pane).
The display mode for the selected value can be modified (in the Base pane) to make it easier to read if, for
example, it consists of two independent bytes or a register of 16 independent bits.
The values of the outputs can also be modified, so that you can check in the absence of a PLC program that
updates the values periodicallythat the periodic commands have been transmitted to the gateway, first of all,
and subsequently to the TeSys U motor starters.
4.2.14. Developing a FIPIO Application

The FIPIO master PLC used in the example is a TSX 57353 v5.1, marketed by Schneider Electric. A sample
PLC application, developed under PL7 PRO, is presented in Appendix D: Sample Use under PL7 PRO. This
example uses the PLC, the gateway and the 8 TeSys U motor starters shown in the Software Implementation of
the Gateway.
1743315 03/2009
43
5. FIPIO Objects Available for Programming

This section presents all the language objects associated with standard profiles FED C32 and FED C32 P
(depending on the chosen configuration methodPL7 PRO or ABC-LUFP Config Tool) for FIPIO communication
with the LUFP1 gateway.
All the FIPIO objects described in the following sections (e.g. output word %QW\p.2.c\0.0.7) obey the following
syntax:
The table below sets out all the FIPIO objects available for use with the gateway. They are then described in
detail in the rest of the section.
(1) IMPLICIT exchanges are performed by the PLC without any additional programming; these are the periodic
FIPIO exchanges. EXPLICIT exchanges call for the programming of communication functions like
READ_PARAM, READ_STS, etc; these are aperiodic FIPIO exchanges for passing diagnostic variables,
downloading complete configurations, and so on.
(2) If the gateway is configured using ABC-LUFP Config Tool (see Chapter 6), the profile FED C32 must be
used. The configuration and adjustment parameters then become internal to the gateway and no longer
need to be transmitted by the FIPIO PLC, and the associated %MW and %KW objects cease to exist.
44
1743315 03/2009

5.1. Periodic Command and Control Words
Unlike the other FIPIO objects for the LUFP1 gateway, the periodic command words (%QW\p.2.c\0.0 to
%QW\p.2.c\0.0.25) and periodic control words (%IW\p.2.c\0.0 to %IW\p.2.c\0.0.25) are fully configurable by the
user.
Their organizational structure is presented in three different ways, depending on how the gateway is used:
Use of the standard configuration with 8 TeSys U motor starters;
Configuration with PL7 PRO, using the standard profile FED C32 P;
External configuration (with ABC-LUFP Config Tool), using the standard profile FED C32.
These objects are updated implicitly by the FIPIO master (by periodic FIPIO exchanges), at the start of the PLC
cycle for the control words, and at the end of the PLC cycle for the command words.
5.1.1. Standard Configuration with 8 TeSys U Motor Starters

The periodic command and control words described below correspond to the configuration described in
Chapter 4.
1743315 03/2009
45

The input assigned to a motor starter gives the value of the status register for that motor starter (address 704 in
the motor starter memory). The gateway handles the periodic Modbus communications with the motor starter in
order to update the value of the FIPIO object that corresponds to the input.
The output value assigned to a motor starter is transmitted to that motor starter in order to update the value of its
command register (address 455 in the motor starter memory). The gateway handles the periodic Modbus
communications with the motor starter in order to transmit the value of the FIPIO object that corresponds to the
output.
Transmission is periodic, but writing a new value means that the gateway will transmit it as soon as possible.
NOTE: If you delete any motor starters from the configuration (see Section 4.2.6), you will need to adapt the two
tables above accordingly. If, for example, you delete 3 motor starters (it has to be the last 3, whichever Modbus
addresses are used), the statuses and commands for motor starters ,
and
will become the words Not
used.
5.1.2. Configuration under PL7 PRO with Profile FED C32 P
The actual contents of the periodic command and control words described below will depend entirely on the
values you entered for the gateways configuration and adjustment parameters. These parameters are described
in Chapter 1.
(1)
You can only configure a total of 26 periodic words. If you configure 20 periodic control words, for example, you
can then only configure a maximum of 6 periodic command words.
Periodic words (control and command) are organized in increasing order of the Modbus slaves (from n1 to n8).
Within this schema, the words assigned to each slave are, in turn, organized in increasing order.
Example: In the next example, the gateway is configured to control and command 4 Modbus slaves. This
example exploits the fact that the number of words is not necessarily the same for each slave.
46
1743315 03/2009
5.1.3. Configuration under ABC-LUFP Config Tool with Profile FED C32
The actual contents of the periodic command and control words described below will depend entirely on the
Modbus data / gateway memory associations you configured in ABC-LUFP Config Tool. These associations
involve the Data or Preset Data elements in the Modbus query and response frames. See Chapter 7, for the
various possibilities offered by this gateway configuration tool, especially in conjunction with profile FED C32.
NOTE: Unlike with profile FED C32 P, you are not restricted to a maximum total of 26 periodic words. You can
use all 26 input words and all 26 output words in the two tables above, organizing them in the gateway memory
as you see fit, within the limit of the addresses shown.
You are still limited to 26 Modbus commands, however, but you can read or write more than one word with each
of these commands.
1743315 03/2009
47

5.2. List of Active Slaves (LAS) Service
This service consists of a single implicit input word (%IW\p.2.c\0.0.27) in which each bit (X0 to X7) corresponds
to a Modbus slave. Each bit will have the value 1 if the corresponding Modbus slave is present and active on the
Modbus network.
In the event of no response, or an invalid response, from a Modbus slave (after the timeout and subsequent
retransmissions of the Modbus command) the corresponding bit switches to 0. It will return to 1 as soon as the
gateway receives a valid response from the slave.
If several periodic words (or several Modbus commands) are configured for the same Modbus slave, then it only
requires one of the words to generate valid communications for the corresponding LAS bit to be set to 1.
NOTE:
You must configure at least one periodic command or control word per slave (profile FED C32 P) or at
least one Modbus command per slave (ABC-LUFP Config Tool and profile FED C32). If not, the slave
will be considered permanently absent (bit at 0).
If you want to communicate with a Modbus slave using the PKW service only, be aware that the LAS
and PKW services are totally disassociated: a PKW response from a Modbus slave will not set to 1 the
corresponding bit in word %IW\p.2.c\0.0.27.
Standard configuration (8 TeSys U devices): If you delete any motor starters from the configuration (see
Section 4.2.6), you will need to adapt the above table accordingly. If, for example, you delete 3 motor starters (it
has to be the last 3, whichever Modbus addresses are used), the bits corresponding to TeSys U motor starters
n6, 7 and 8 namely bits X5-X7will take on the value Not used (bits at 0).
48
1743315 03/2009

Configuration under PL7 PRO (profile FED C32 P): The absence from the configuration of one or more
Modbus slaves entails the same modifications as for the standard configuration of 8 TeSys U devices.
Configuration under ABC-LUFP Config Tool (profile FED C32): The order of the slaves in the LAS word
corresponds to the declaration order for the various Nodes in the Sub-Network element, as they appear in
ABCLUFP Config Tool. As in the two previous cases, if fewer than 8 Modbus slaves are used, then one or more
slaves starting with the 8th and working back towards the 1stwill be absent from the list.
5.3. Indexed Periodic Variables (PKW) Service

5.3.1. Introduction to the PKW Service
With this service, you can configure and adjust any Modbus slave: it offers read and write access to any
parameter of a slave via the periodic inputs and outputs of LUFP1 gateway. It can also be used for access to
certain reserved registers on the LUFP1 gateway.
The PKW service is aperiodic on the Modbus network (a command is transmitted whenever one of the %QW
outputs associated with the service changes) and periodic on the FIPIO network (implicit exchanges). You can
use the service to perform the following tasks:
Retrieving or updating the parameters on some or all of the Modbus slaves;
Reading the value of one or more data for which a low refresh rate is sufficient;
Reading the value of a data item when an event is signaled by a periodic variable.
In the absence of any response from the queried Modbus slave using this service, the gateway retransmits the
samecommand 3 times in succession, waiting for 1 second between transmissions. If you wish, you can modify
the values of these two parameters (number of retransmissions and timeout) using ABC-LUFP Config Tool (see
Section 7.13.3).
1743315 03/2009
49

5.3.2. PKW Service: Command and Response
50
1743315 03/2009

5.3.3. Using the Indexed Periodic Variables (PKW) Service
To perform a complete transaction, the FIPIO master must first update the whole of the command
(%QW\p.2.c\0.0.28 to %QW\p.2.c\0.0.31), and then wait until the values in the response (%IW\p.2.c\0.0.28 to
%IW\p.2.c\0.0.31) match the command (by comparing the PKE, DN and R/Wor, in the case of the response,
R/W/Nvalues).
The gateway stores the response values for as long as the FIPIO master modifies none of the command values.
If any output word in the PKW command (even the PWE outputs) is modified, a new command is transmitted
over the Modbus network, except when R/W = 0x00.
NOTE:
Stick strictly to the values given in the PKW service command table. Otherwise the gateway will send an
erroneous response.
Be careful not to write incorrect values in the outputs corresponding to the PKW service, as this would
generate an incoherent command: only limited checks are run on the data used by this service, and it is
therefore left to the FIPIO master PLC application to handle them.
The PKE addresses corresponding to periodic command words (profile FED C32 P) or to registers
assigned by Modbus write commands (profile FED C32) must not be used in PKW service write
commands, as this could lead to a write conflict in the same registers.
Such a command could however be envisaged if, for example, you wanted to run the same command on
all the Modbus slaves urgently and simultaneously (DN = 255). In this case, you will also need to write
the same value as the broadcast command PWE into the periodic command words that share the same
PKE address, in order to avoid generating conflicts between the values transmitted.
As the write commands (R/W = 0x57 and 0x58) return no value, you will have to use the appropriate
read command (R/W = 0x52 or 0x53) if you want to check that the write operation has been performed
correctly.
Below are further details on the most important data in this service:
Device Number (DN):
DN = 0
1st Modbus slave. This is TeSys U motor starter n1, or Modbus slave n1 when profile FED
C32 P is used. When profile FED C32 is used, it stands for the first node configured in the
Sub-Network element under ABC-LUFP Config Tool. In either case, the gateway will use the
true physical Modbus address every time to query the 1st slave.
DN = 1 to 247
Physical address of the queried Modbus slave. The queried slave must be one of the Modbus
slaves configured under PL7 PRO (profile FED C32 P) or under ABC-LUFP Config Tool
(profile FED C32). By querying one or more of the slaves episodically via the PKW service, you
can avoid having to configure periodic words (under PL7 PRO) or Modbus commands (under
ABC-LUFP Config Tool).
DN = 254
LUFP1 gateway. With this reserved address you can read the values of certain registers on the
gateway (see Section 5.3.5). All the registers on the gateway are in 8-bit format and their
values will be returned to bits 0-7 of word %IW\p.2.c\0.0.30.
Some of these registers cannot be written using the PKW service; they are noted as being
Read Only, or RO, and only the 16-bit word read command (R/W = 0x52) can be used with
them. All the other gateway's internal registers can be read and written using the PKW service;
they are noted as being Read/Write, or R/W, and the 16-bit word read and write commands
(R/W = 0x52 or 0x57) can be used with them.
1743315 03/2009
51

DN = 255
Broadcast to all Modbus slaves. This DN value must only be used for write operations (R/W/N
= 0x4E in the event of a read operation). On the Modbus network, the command generated
uses the address 0: this means that all the Modbus slaves must accept the command,
although none of them will acknowledge it.
The drawback with the broadcast command is that the gateway has no way of checking
whether the Modbus slaves have received the command. Even if there are no slaves present
on the Modbus network, the gateway will still return a valid PKW response (R/W/N = OK).
NOTE: This feature can be particularly useful if you need to perform an urgent command on all
the slaves at the same time.
DN = ...........
Incorrect address. Any value other than those indicated above will elicit an error code from the
gateway (R/W/N = 0x4E).
Read / Write (R/W):

R/W = 0x00 ...... Reset command and response. As long as R/W remains at 0x00, no command will be
generated on the Modbus network (even if one of the other PKW service outputs is modified)
and all the PKW service inputs will remain at 0x0000. Basically, you should use this value if
you want to deactivate the PKW service.
NOTE: As the PKW service only performs single read and write operations (the active
command is only executed once), you could use this specific value of R/W to repeatedly
overwrite the active R/W value. This would generate a series of identical commands
(interspersed with resets to zero), thereby enabling the gateway to emulate the principle of
permanent read and write operations.
R/W = 0x52 ......Read a 16-bit word. This is also the command to use for reading an 8-bit register from the
gateway (DN = 254).
R/W = 0x53 ......Read 2 consecutive 16-bit words or a 32-bit Dword. This command is used mainly for reading
the values of two 16-bit registers located at two consecutive addresses on the same Modbus
slave. The value located at address PKE will be returned in the input %IW\p.2.c\0.0.30 (1st
word of PWE) and the value at address PKE+1 in the input %IW\p.2.c\0.0.31 (2nd word of
PWE).
NOTE: This command should be preferred to the 16-bit word read command (R/W = 0x52)
when using the PKW service to read a large number of consecutive registers on a Modbus
slave.
R/W = 0x57 ...... Write a 16-bit word. This command allows you to modify the value of the 16-bit register of
which the address is given by the PKE output. Only the 1st word of the PWE output is used
(%QW\p.2.c\0.0.30).
R/W = 0x58 ...... Write 2 consecutive 16-bit words or a 32-bit Dword. This command is used mainly for
modifying the value of two 16-bit registers located at two consecutive addresses on the same
Modbus slave. The value of output %QW\p.2.c\0.0.30 (1st word of PWE) is written into address
PKE and the value of output %QW\p.2.c\0.0.31 (2nd word of PWE) is written into address
PKE+1.
NOTE: This command should be preferred to the 16-bit word write command (R/W = 0x57)
when using the PKW service to update a large number of consecutive registers on a Modbus
slave.
52
1743315 03/2009

Read / Write / Error (R/W/N):
R/W/N = 0x4E This specific value enables the gateway to signal a PKW command runtime error to the
FIPIO master. In this case, the gateway uses the LSB of the 1st PWE word in the response to
return an error code to the FIPIO master:
0x04 if no Modbus response, or an erroneous Modbus response, is received.
0x01 to 0x08 (including 0x04) if an exception response is received from the Modbus slave.
This value will correspond to the exception code (see Appendix E).
R/W/N = 0x
Copies the value of the R/W command register (see above), thereby also acknowledging
the command.
5.3.4. Sample Uses of PKW Service

The examples below illustrate commands addressed to Modbus slaves consisting mainly of the 8 TeSys U motor
starters described in Chapter 4.
Sample reading of the value of a motor starter register (16-bit word)

The 1st fault register (address = 452) is read on TeSys U motor starter n5 (address = 5). The result of
the read operation is 0x0002 (presence of a magnetic fault only). Only the 1st PWE word in the response
is used; the 2nd word is forced to 0x0000 by the gateway.
Sample writing of the value of a motor starter register (16-bit word)

The 2nd command register (address = 705) is written to TeSys U motor starter n7 (address = 7) with
the value 0x0006 (clear statistics + reset thermal memory).
The result of the write operation is a simple acknowledgement, as no value is returned in the PWE of the
response; instead of inserting a value, the gateway forces both words of the PWE to 0x0000.
PKW Command PKW Response
Sample reading of the value of two consecutive motor starter registers (16-bit words)
The operating duration (addresses = 119 for the MSB and 120 for the LSB) is read on TeSys U motor
starter n8 (address = 8).
The result of the read operation (value of the register at 119 and value of the register at 120) is 0x000D
and 0xC9C4 (total operating duration = 0x000DC9C4 = 903,620 seconds, or 251.0055 hours). Both of
the response PWE words are therefore used.
1743315 03/2009
53
54
Sample writing of the value of two consecutive motor starter registers (16-bit words)
The timeout and threshold for the thermal reset (addresses = 607 and 608) are written to TeSys U motor
starter n2 (address = 2) with the following values: 90 s (0x005A) and 60% (0x003C).
response; instead of inserting one or two values, the gateway forces both words of the PWE to 0x0000.
Sample erroneous reading of the value of a motor starter register (16-bit word)
An attempt is made to read the status register value (address = 455 for a TeSys U motor starter) on a
slave whose physical address corresponds to none of the addresses configured for the gateways
Modbus slaves (address = 32 = 0x20).
The response is an error code (R/W/N = 0x4E) and is immediate: the gateway signals to the FIPIO
master that the queried slave does not exist (1st word of PWE = error code = 0x0002).
Sample erroneous writing of the value of a motor starter register (16-bit word)
An attempt is made to write the status register value (address = 455) to TeSys U motor starter n2
(address = 2) with the value 0x0001, but the register is in read-only mode.
The response is an error code (R/W/N = 0x4E): the motor starter returns an exception response (1st
word of PWE = error code = Modbus exception code = 0x0002 = Illegal Data Address).
1743315 03/2009
Sample writing of the value of a register (16-bit word) on all the motor starters (broadcast)
The command register (address = 704) is written to all the TeSys U motor starters (address = broadcast
= 255) with the value 0x2000 (Stop and Pause).
NOTE: This simultaneously switches off all the TeSys U motor starters, but you still need to insert the
value 0x2000 in the periodic output words sent to the motor starters, otherwise they will return to their
previous status at the next Modbus polling cycle.
response; instead of inserting a value, the gateway forces both words of the PWE to 0x0000.
Sample reading of the value of a register (8-bit byte) on the LUFP1 gateway
The last error code from Modbus slave n1 is read on the gateway (address = 300 and DN = 0xFE).
If Modbus slave n1 (TeSys U motor starter n1 in the case of the standard configuration) has already
been disconnected from the Modbus network, the gateway will have assigned it the error code 0x04. In
this case, the result of the read operation is 0x04. As the value of the register read is contained in the
LSB of the 1st word in the response PWE, the corresponding MSB is forced to 0x00 by the gateway;
likewise, the 2nd word is forced to 0x0000.
5.3.5. LUFP1 Gateway Internal Registers

The registers presented in this section are internal to the gateway and are all in 8-bit format. The PKW service
provides access to them (DN = 254), but only with the aid of a 16-bit word read command. The gateway inserts
the result of a read operation in bits 0-7 of the 1st word in the PWE (%QW\p.2.c\0.0.30); the rest of the PWE is
forced to 0.
The RO access right means that the registers are in read-only mode, rather than read / write (R/W). But
even when a register is in R/W, the gateway can reject a write operation via the PKW service if the value of the
PWE in the write command is incorrect. This tends to happen with any value other than 0x0000 in the case of
registers 300 to 307 (error code reset).
1743315 03/2009
55
The adjustment and configuration parameters will only be present when the gateway is configured using PL7
PRO, i.e. in accordance with the standard profile FED C32 P. You should therefore not use addresses 0 to 119 if
you configure the gateway with ABC-LUFP Config Tool (profile FED C32 cannot be configured under PL7 PRO).
These parameters are shown below with the sole purpose of listing their addresses and access rights to the
PKW service. For more details about them, see Appendix B. To make it easier to read, the table below is based
on the FIPIO objects that correspond to the gateways configuration and adjustment parameters:
56
1743315 03/2009
CAUTION
RISK OF UNPROPER COMMUNICATION
Be careful while modifying the register values at addresses 68 to 119. The FIPIO master can alter the very
nature of the information exchanged between the gateway and the slaves.
Failure to follow this instruction can result in injury or equipment damage.
Slave error codes: Each of the registers at addresses 300 to 307 contains the code of the last error declared by
the gateway for the Modbus slave concerned. If the gateway receives an exception response from a Modbus
slave (see Modbus Protocol Exception responses in Appendix E) during periodic exchanges, it puts the
exception code in the corresponding register (300-307). The value of each of these registers remains the same
until either a new error is signaled for the slave concerned, or you reset it to zero using the PKW service (the
gateway only accepts write commands where PWE = 0x0000).
1743315 03/2009
57

The value of the error code is 0x04 if the corresponding slave is declared absent by the gateway (after the
Modbus periodic commands for the slave have been retransmitted with timeouts).
NOTE: The LAS service is updated at the same time as registers 300 to 307 when this type of event occurs (see
Section 5.2). You can therefore use the various bits in the periodic word of this service (%IW\p.2.c\0.0.27) to
trigger a read operation on the internal register assigned to the slave declared absent by the LAS service.
5.4. FIPIO Diagnostic Objects

We strongly recommend that you adhere to the following five rules while using the other FIPIO objects
associated with the LUFP1 gateway:
See also the PL7 PRO documentation or on-line help (Working with communications > FIPIO bus
communications > Programming a FIPIO communication > Managing FIPIO faults) to learn more about the
procedures for managing FIPIO faults.
58
1743315 03/2009

5.4.1. System Words %SW128 to %SW135
Each bit in this group of words signals the status of a device connected to the FIPIO bus (addresses 0 to 127).
These bits are normally at 1, but switch to 0 in the event of a fault on the connection point (faulty FIPIO
connection point). For a non-configured connection point, the corresponding bit is always at 1.
The table below maps the correspondences between these system word bits and the addresses on the FIPIO
bus:
5.4.2. Channel Status (%MW\p.2.c\0.0.2)

Each of the channel status bits corresponds to a fault generated either by the gateway or by the PLC. A fault is
present if the corresponding bit is at 1. The channel status is updated by the explicit command
.
5.4.3. Module Status (%MW\p.2.c\0.MOD.2)

Each of the module status bits corresponds to a specific fault. A fault is present if the corresponding bit is at 1.
The module status is updated by the explicit command
.
1743315 03/2009
59

5.5. Status of Explicit Exchanges
The two implicit words %MW\p.2.c\0.0 (exchange in progress) and %MW\p.2.c\0.0.1 (report) serve to control
explicit exchanges. You should use them if you need to program explicit exchanges in the FIPIO master PLC
application.
Before carrying out an exchange, check that the relevant bit (%MW\p.2.c\0.0:X) is at 0 (exchange inactive).
The bit will switch to 1 for the duration of the exchange.
When the exchange is complete (the bit switches back to 0), you can check the bit at the other end
(%MW\p.2.c\0.0.1:X) to determine whether the exchange succeeded (bit at 0) or failed (bit at 1).
5.6. Parameters Specific to Profile FED C32 P

The gateway configuration and adjustment parameters are only stored in the FIPIO master PLC memory if the
gateway was configured (under PL7 PRO) to support configuration and adjustment using standard profile FED
C32 P.
If the gateway is configured with standard profile FED C32, then these parameters do not exist.
Configuration and adjustment must then be carried out independently. In this case, ABC-LUFP Config Tool will
be required: see Chapter 7. The software implementation of the gateway under PL7 PRO, using profile FED
C32, is described in Chapter 6. From the viewpoint of PL7 PRO, it then becomes a locally configured gateway.
NOTE: Some of the configuration and adjustment parameters cannot be modified after the initial setup of the
gateway using the PLC. See the tables in section 5.3.5 and in Appendix B.
60
1743315 03/2009
5.6.1. Configuration Parameters (%KW\p.2.c\0.0 to %KW\p.2.c\0.0.29)

The 30 configuration parameters of profile FED C32 P are transmitted to the gateway implicitly when it connects
up to the FIPIO network.
When you modify them in
mode under PL7 PRO and save the changes, communications in channel 0
are paused while the new settings are sent to the gateway.
These parameters are described in Appendix B.
5.6.2. Adjustment Parameters (%MW\p.2.c\0.0.20 to %MW\p.2.c\0.0.49)

The 30 adjustment parameters of profile FED C32 P are transmitted to the gateway implicitly when it connects
up to the FIPIO network.
mode under PL7 PRO and save the changes, a command is generated to
When you modify them in
send the parameters to the gateway.
You can also use the following functions to perform explicit exchanges between the FIPIO PLC and the LUFP1
gateway:
READ_PARAM %CH\p.2.c\0.0........... Read the adjustment parameters on the gateway.
WRITE_PARAM %CH\p.2.c\0.0......... Write adjustment parameters to the gateway.
SAVE_PARAM %CH\p.2.c\0.0........... Save the gateway adjustment parameters; the values replace the initial
adjustment parameters.
RESTORE_PARAM %CH\p.2.c\0.0 .... Restore the initial adjustment parameters.
NOTE: The values of the initial adjustment parameters are those defined using the PL7 PRO configuration editor
or, alternatively, the most recently saved values.
These parameters are described in Appendix B.
1743315 03/2009
61
6. Advanced Implementation of the Gateway

This chapter marks the start of Part II of the LUFP1 Gateway Users Manual. This part comprises Chapters 6
and 7 and focuses on the use of ABC-LUFP Config Tool. This configuration tool enables the gateway to be
configured and adjusted independently of PL7 PRO. The possibilities offered by the tool go well beyond the
limits imposed by the standard profile FED C32 P. The whole of Part II therefore supplements Chapter 4, and
supersedes certain sections.
6.1. Introduction to Advanced Implementation of the Gateway

The Advanced Implementation of the Gateway gets around certain limits imposed by the Software
Implementation of the Gateway (Chapter 4). The main differences between the two implementation methods are
summarized in the table below:
The main advantage of ABC-LUFP Config Tool lies in the possibility of configuring the gateways Modbus
scanner more precisely than under PL7 PRO, in that each Modbus command has its own configuration.
However, using this implementation method for the LUFP1 gateway substantially modifies the operating principle
described and illustrated in Chapter 7. The differences are set out below:
62
1743315 03/2009
6. Advanced ABC-LUFP Config Tool

The exchanges between the gateway (acting as Modbus master) and the Modbus slaves are configured
entirely using ABC-LUFP Config Tool. This configuration tool really goes into the details (exchange
timeouts, communication modes, frame content, etc.), which makes it somewhat harder to use. A
chapter of this guide has therefore been given over to the subject (Chapter 7).
By configuring Modbus command queries and responses with this tool, the user creates links between part of the
contents of the Modbus frames and the contents of the gateways physical memory (input memory for the
contents of the Modbus responses and output memory for the contents of the queries).
NOTE: Only use the address ranges indicated in this guide when creating these links.
The periodic exchanges between the FIPIO master PLC and the LUFP1 gateway are limited to
transferring the contents of the gateways input memory to the %IW inputs on the PLC and transferring
the PLCs %QW outputs to the gateways output memory.
The FIPIO network is totally separate from the Modbus network. The frames on a network are not directly
translated by the gateway to generate frames on the other network. Instead, the exchanges between the
contents of the gateways memory and the Modbus slaves make up a system independent of the one entrusted
with managing the exchanges between this gateway memory and the FIPIO master.
The figure that follows illustrates the independent management of each of the two networks:
Managing Gateway Modbus slave exchanges (FED C32)
1743315 03/2009
63

6.2. Implementation under PL7 PRO
The implementation described below is based on the one in Chapter 4.2.4. We just present a summary of that
implementation here, along with the modifications entailed by using profile FED C32 instead of FED C32 P:
A configuration example can be found on the http:///www.schneider-electric.com website:
LUFP1_FEDC32_Example.cfg. The system architecture for this configuration is identical in all respects to the one
described in Chapter 4. The example is provided mainly to assist you in understanding the uses and possibilities
of ABC-LUFP Config Tool.
Adding the LUFP1 Gateway under PL7 PRO............................................................................Section 4.2.2
Select basic module FED C32 instead of basic module FED C32 P.
Configuring and Adjusting the LUFP1 Gateway......................................................................Section 4.2.3
, as the gateway cannot be configured under
Do not double-click on basic module
PL7 PRO.
Ignore the description of how configuration and adjustment parameters are downloaded from the FIPIO
master PLC to the LUFP1 gateway. When ABC-LUFP Config Tool is usedand the configuration thus
downloaded from ABC-LUFP Config Tool (see next steps)the parameters will be located on the gateway only.
From the viewpoint of PL7 PRO and the FIPIO master PLC, the gateway will have a local configuration.
Configuration Parameter Values, Standard Configuration.....................................................Section 4.2.4
Ignore this step for the time being; it describes elements which, under ABC-LUFP Config Tool, will come into
play later on.
Adjustment Parameter Values, Standard Configuration.........................................................Section 4.2.5
Ignore this step for the time being; it describes elements which, under ABC-LUFP Config Tool, will come into
play later on.
Deleting One or More TeSys U Motor Starters from the Configuration .....................................Section 4.2.6
This operationdescribed in Section 7.8is specific to ABC-LUFP Config Tool. You must therefore run
ABCLUFP Config Tool and load the example file provided in order to delete a motor starter.
Configuring Gateway Inputs / Outputs .....................................................................................Section 4.2.7
As with PL7 PRO, no operation need be performed if you use the example file provided (this section
describes the inputs / outputs corresponding to the configuration entered during the previous steps). If you want
to modify the configuration or create a new one, consult the relevant sections of Chapter 7. The explanations
that follow seek to describe the configuration illustrated in the example.
The gateway inputs / outputs are configured entirely under ABC-LUFP Config Tool. The Modbus frames
configured for the various slaves (or Nodes) of the Modbus network (or Sub-Network) include Data or
Preset Data elements. Each element is a link between the contents of the Modbus frame it represents and a
precise location in the gateway memory. You can configure the size of the data exchanged, and the memory
location for the exchanges. This allows you to organize the gateway inputs and outputs as you see fit, within the
limit of the addresses that correspond to the inputs / outputs (see Section 5.1.3).
The configuration example provided with the gateway, LUFP1_FEDC32_Example.cfg, is designed to
reproduce the standard configuration used in the gateway implementation with profile FED C32 P (8 TeSys U
motor starters). The configuration of the gateway inputs / outputs is therefore identical to the one described for
the standard configuration. Each TeSys U n node in the example comprises a read command from the TeSys
U status register (address = 455 = 0x01C7) and a write command from the TeSys U command register (address
= 704 = 0x2C0). These commands are configured in exactly the same way, except for their Data elements. The
Modbus frame content / gateway memory address links for these elements, on which the equivalence with the
standard configuration is based, are configured as follows:
64
1743315 03/2009
NOTE: The Byte swap field must always have the value No swapping if you wish to avoid inverting the LSB
and MSB bytes of the data read or written using the Modbus commands.
Description of Services Assigned to Gateway I / O.................................................................Section 4.2.8
In the example provided, these services are identical to the ones in the standard configuration, for the
following reasons:
The periodic communications (inputs / outputs) are configured so that the gateway input / output
configuration (see above) is identical to the one in the standard configuration.
The aperiodic communications corresponding to the gateways PKW service must be active, whether the
gateway is configured according to profile FED C32 (in PL7 PRO) or profile FED C32 P (in ABC-LUFP
Config Tool).
The list of active slaves (LAS) must also be active on the gateway.
Validating and Saving the FIPIO Network Configuration........................................................Section 4.2.9
These operations have no equivalent under ABC-LUFP Config Tool, as ABC-LUFP Config Tool can configure
only one gateway at a time. The operations you can perform on a configuration are: Open and Save.
Under PL7 PRO, by contrast, you must always validate FED C32 P profile configuration and setting.
Assigning Symbols to the Gateways FIPIO Objects ............................................................Section 4.2.10
The FIPIO objects remain the same, except for the 30 configuration parameters (%KW\p.2.c\0.0 to
%KW\p.2.c\0.0.29) and the 30 adjustment parameters (%MW\p.2.c\0.0.20 to %KW\p.2.c\0.0.49), which
disappear, as their function is now taken over by ABC-LUFP Config Tool.
Checking the Operational Status of the Gateway..................................................................Section 4.2.11
If you want to use the example LUFP1_FEDC32_Example.cfg, run ABC-LUFP Config Tool, open the
configuration file (Open command in the File menu), transfer it to the gateway (Download configuration to
ABC-LUFP command in the File menu) and close ABC-LUFP Config Tool.
Once the configuration has been downloaded to the gateway, and the PL7 PRO application transferred to the
FIPIO
master
PLC,
use
PL7
PRO,
in
mode,
to
check
that
the
basic
module
corresponding to the gateway is operational on the FIPIO network.
1743315 03/2009
65

A Hardware configuration fault will occur if you downloaded an ABC-LUFP Config Tool configuration based
on FED C32 P rather than FED C32, which is not the case for the aforementioned example file.
Modifying the Gateway Parameters in ONLINE Mode .............................................................Section 4.2.12
This operation is now performed under ABC-LUFP Config Tool instead of under PL7 PRO. Downloading a
new configuration to the gateway reinitializes the gateway, and in the process its FIPIO and Modbus
communications.
Debugging and Using the Gateway Configuration ...............................................................Section 4.2.13
The diagnostics, inputs and outputs of the gateway are accessible, in
called up by double-clicking the basic module
mode, via the debug window

corresponding to the LUFP1 gateway.
Developing a FIPIO Application...............................................................................................Section 4.2.14

The PLC application example in Appendix D: Sample Use under PL7 PRO is fully compatible with the
gateway when configured using profile FED C32. The only modification required is to change the gateway profile
type (double-click the FIPIO connection point and select profile FED C32 instead of FED C32 P).
.
66
1743315 03/2009
7. Using ABC-LUFP Config Tool

Each part of this chapter describes a separate step allowing users to personalize the gateway configuration
according to their own particular needs, but only when it is configured using standard profile FED C32 under
PL7 PRO. Each part introduces a basic operation, isolating it from the rest of the configuration and describing the
operations to be carried out using ABC-LUFP Config Tool and how they affect the gateways general behavior.
Some of the operations can also be performed when the gateway is configured using standard profile
FED C32 P. This possibility will be flagged by the symbol
in the corresponding description.
In each case, the first two steps are required, as they allow you to establish the dialogue between the gateway and
the PC software that enables you to configure it, i.e. ABC-LUFP Config Tool.
We strongly recommend that you read Chapter 4, and, above all, Chapter 6, as all the ABC-LUFP Config Tool
operations described here assume that we are using the standard configuration (with 8 TeSys U motor starters)
presented in the context of the two LUFP1 gateway implementation methods.
7.1. Connecting the Gateway to the Configuration PC

This step is required when setting up the gateway configuration application, ABC-LUFP Config Tool.
Connecting the gateway to one of the serial (COM) ports on a PC requires a straight PowerSuite cable and an
RS232/RS485 converter. These two items are the same as those allowing dialogue with drives and soft start/soft
stop units using the PowerSuite application and are both available from the catalogue (ref.: VW3 A8 106).
Be sure to use the POWERSUITE cable and the RS232 / RS485 PC converter. An ATV28 before 09 / 2001
cable and an ATV 58 converter are also supplied with these items, but they should not be used with the LUFP1
gateway.
Once the gateway has been connected to a PC with the PowerSuite cable and the RS232/RS485 converter, you
can change its configuration using "ABC-LUFP Config Tool". This configuration tool also allows you to carry out a
few diagnostics on the gateway.
7.1.1. Pin-Outs
67
1743315 03/2009
NOTE: The inversion of the Rx and Tx signals between the gateway and the PC is shown on the 9-pin Sub-D
connectors, as beyond this junction, the RS-232 signals are replaced by the D(A) and D(B) polarizations of the RS485 signals.
7.1.2. RS-232 Link Protocol
There is no need to configure the PCs COM port, as ABC-LUFP Config Tool uses a specific setup which replaces
the one for the port being used. This replacement is temporary and is cancelled as soon as ABC-LUFP Config Tool
stops using this serial port, i.e. when ABC-LUFP Config Tool is closed.
68
1743315 03/2009

7.2. Installing ABC-LUFP Config Tool
The minimum system requirements for ABC-LUFP Config Tool are as follows:
Processor........................................Pentium 133 MHz
Free hard disk space ......................10 MB
RAM................................................08 MB
Operating system............................MS Windows 95 / 98 / ME / NT / 2000 / XP
Browser...........................................MS Internet Explorer 4.01 SP1
The ABC-LUFP Config Tool installation program can be found on the http:///www.schneider-electric.com website
(ref. VW3 A8 104).To install it, run ABC-LUFP153.exe and follow the on-screen instructions.
You can read about how to use ABC-LUFP Config Tool in a user manual entitled AnyBus Communicator User
Manual which is also on the http:///www.schneider-electric.com website: ABC_User_Manual.pdf. We strongly
recommend that you read this manual when using ABC-LUFP Config Tool: the present guide will limit itself to the
ABCLUFP Config Tool features relevant to a LUFP1 gateway implementation.
7.3. Connecting to / Disconnecting from the Gateway

In the ABC-LUFP Config Tool, the connection to the gateway must be performed manually.
But first, you should check which serial port the
ABCLUFP Config Tool will use for this connection. In
the Tools menu, the Port sub-menu will reveal
which serial ports (COM1, COM2, etc.) are currently
available. If several COM ports are available, select
the port you intend to use for connecting to and
configuring the gateway.
An example is given here:
NOTE: If all the serial ports of your PC are already used by other applications, you must first close ABC-LUFP
Config Tool, then free a serial port by disconnecting, closing, or terminating an application that currently uses a
serial port.
Afterward, restart ABC-LUFP Config Tool because COM ports are only scanned during its start-up; the freed COM
port should now be useable by it.
To connect ABC-LUFP Config Tool to the gateway:
right-click on the ABC-LUFP element and click on Connect in the popup menu that appears, or
select the ABC-LUFP element and choose Connect in the ABC-LUFP menu, or
click on the
button.
Once connected, you can disconnect ABC-LUFP Config Tool from the gateway by:
right-clicking on the ABC-LUFP element and clicking on Disconnect in the popup menu that appears, or
selecting the ABC-LUFP element and choosing Disconnect in the ABC-LUFP menu, or
clicking on the
button.
The rightmost part of the status bar of ABC-LUFP Config Tool displays its current connection mode:
In On-line mode, ABC-LUFP Config Tool periodically polls the gateway in order to detect if the gateway has been
disconnected.
1743315 03/2009
69

When an unwanted disconnection does occur, ABCLUFP Config
Tool goes to Off-line mode (the red LED is displayed) and
automatically retries to connect to the gateway. The Searching
for ABC-LUFP window is visible for the duration of this search.
If the search fails, ABC-LUFP Config Tool prompts you with No Module was found, retry?.
Should you select the Cancel button, ABC-LUFP Config Tool remains in Off-line mode.
Should you select the Retry button, ABC-LUFP Config Tool resumes the search for an ABC-LUFP gateway.
7.4. Importing the Gateway Configuration

Before you can make any changes to the gateway configuration, you will first need to import its current
configuration. If you already have this configuration on your hard disk, all you will need to do is open the file
corresponding to this configuration.
GATEWAY is
Check that the gateway has a valid configuration and that it is working properly, i.e. that LED
flashing green.
In ABC-LUFP Config Tool, choose Upload configuration from
button in the
ABC-LUFP from the File menu or click the
ABC-LUFP Config Tool toolbar. The Upload window opens,
containing a progress bar that tracks the advance of the
gateway configuration uploading process. The window closes
once the upload is completed.
This step is particularly important if you want to read details about the current contents of the gateway configuration
rather than about a configuration in a .cfg file on a PC. You can then use this configuration as a template for any
changes you wish to make subsequently, thus avoiding having to create one from scratch and reducing the
potential risk of error.
NOTE:
Save this configuration to your hard disk so that it is always available. This will allow you to reconfigure the
gateway cleanly should the configuration become invalid.
You can use the "Upload" command to check the configuration and settings that you made
under PL7 PRO. This is because the gateway creates an equivalent configuration that can be viewed using the
retrieve command.
70
1743315 03/2009

7.5. Transferring a Configuration to the Gateway
When using ABC-LUFP Config Tool, you can transfer the configuration you are editing to the gateway at any time.
Choose Download configuration to ABC-LUFP from the File
button in the ABC-LUFP Config Tool toolbar.
menu or click the
ABC-LUFP Config Tool initializes a check test of the gateway type.
NOTE: During this very quick test, the PC should not carry out any
other operations, as this could lead to ABC-LUFP Config Tool
apparently freezing up and slowing down the PCs general
operation for several minutes. After the test is complete, the PC will
return to full speed, and may be used normally.
Once this test has finished, a window called Download opens and
a progress bar shows the state of progress for the transfer of the
configuration to the gateway.
NOTE: Do not interrupt this operation; otherwise you will have to
start it again from the beginning.
Check that the transfer has been correctly carried out: LED
GATEWAY should be flashing green.
If this LED is flashing red/green, save the configuration you were editing, open a file containing a valid configuration
(LUFP1_FEDC32_Example.cfg, for example), and transfer it to the gateway. This will restore it to a known initial
state. You can then continue with the configuration you were transferring, and make any corrections which may be
necessary.
7.5.1. Transferring the Internal Configuration (Profile FED C32 P)

When using the standard profile FED C32 P to set up the gateway under PL7 PRO, never
use the command Download configuration to ABC-LUFP to transfer a configuration to the gateway.
The only exception to this rule involves the Hardware configuration fault (see Section 4.2.11).
In this case, you should perform the following actions:
Use the New command of the File menu;
Set the following properties for the ABC-LUFP
element:
o Control/Status Word ......................... Disabled
o Module Reset ................................... Disabled
o Protocol Mode .................................. FIPIO-MB
Gateway
o Statistics ........................................... Disabled
Set the following properties for the Fieldbus element:
o Fieldbus Type ................................... FIP I/O
o Profile ............................................... FED C32P
Do not add any node nor Modbus command to the
Sub-Network element;
Download this blank configuration into the gateway.
7.6. Monitoring the Contents of the Gateways Memory

One of the main commands that you will need to use when setting up the gateway is the command allowing you to
read the contents of the gateways memory and to display it in a window designed for this purpose. This will be
particularly useful when you are working on your PLC applications and configurations. However, it only shows data
from the Data and Preset Data fields configured in the Query and Response elements of a single Modbus
slave.
1743315 03/2009
71

As the gateways LAS and PKW services are not located in the memory zones reserved for exchanges with the
Modbus slaves, the input and output data of these services cannot be viewed in the same way. Only PL7 PRO and
the FIPIO master can access such data.
To monitor the contents of the
gateways memory, start by
selecting the node corresponding
to the Modbus slave whose data
you wish to view, and then
choose Monitor from the menu
with the same name as the
previously selected node. A
monitoring window then appears.
The sample window above displays the contents of the memory exchanged, under the standard configuration, with
TeSys U motor starter n1.
In the upper pane you can choose a Modbus command, edit its contents, and send it to the Modbus network
(Command menu). The response will then be displayed in the same pane. See Section 2.10 in the ABC-LUFP
Config Tool user manual, entitled AnyBus Communicator User Manual, for further information about how to
use this window. The manual can be found on the http:///www.schneider-electric.com website under
ABC_User_Manual.pdf.
The lower pane allows you to view the contents of the gateways memory, but only the bytes used in the query and
response frames of the commands configured for the selected node.
In the window shown above, the data displayed correspond to the values at the memory locations designated by
the Data fields in the commands configured for the node TeSys U n1, namely: Read Holding Registers and
Preset Multiple Registers.
NOTE: The data exchanged with the previously selected Modbus slave are displayed MSB-first, i.e. in the order
MSB /LSB (from left to right, in ascending order of memory address), provided that the Byte Swap option in the
Data or Preset Data element of the corresponding Modbus command was set to No swapping (see Section
7.12.2.4).
A brief description of the toolbar buttons in this window is given below:
72
1743315 03/2009

The menus of this window allow you to perform the following actions:
File menu:
- The Exit command closes the Monitor window, thus returning to ABC-LUFP Config Tool.
Node menu:
- The Start Node command restarts all the communications configured for the node
currently monitored. Since a node is active by default, this command is only useful if the
node has been explicitly stopped using the Stop Node command.
- The Stop Node command stops all the communications configured for the node currently
monitored. This means that all Commands configured for the node are inhibited.
Note: The Stop / Start Node commands can be particularly useful when used to isolate one
or more nodes in order to investigate Modbus communication problems.
Command menu: - The Select Command command opens a Select Command window that enables you to
select a Modbus command (see chapter 7.11.2). Once selected, the Query and Response
frames of this command will be displayed in the upper part of the Monitor window. You can
then edit the value associated with each field of the Query frame before sending the
command using Send Command (see below).
- The Send Command command triggers the emission of the Query displayed in the upper
part of the Monitor window. As soon as a Modbus Response is received by the gateway,
ABC-LUFP Config Tool displays its contents in the upper part of the Monitor window.
Columns menu:
- The Free choice configures the three monitoring columns (In Area, Out Area,
andGeneral Area) to automatically adjust their width on a 1-byte unit (1 byte, 2 bytes, 3
bytes, etc.) each time you modify the width of the Monitor window.
- The 8 Multiple choice configures the three monitoring columns to automatically adjust
their width on an 8-byte unit (8 or 16 bytes) each time you modify the width of the Monitor
window.
View menu:
- The Hex choice configures the three monitoring columns to display all monitored values
and memory addresses in Hexadecimal.
- The Decimal choice configures the three monitoring columns to display all monitored
values and memory addresses in Decimal.
Proceed with Importing the Gateway Configuration (Section 7.4) before Monitoring the
Contents of the Gateways Memory. This will ensure that the data displayed corresponds to the inputs and outputs
exchanged with the selected Modbus slave.
7.7. Creating a New Configuration

When you want to create a new configuration, you can either use an existing configuration as a starting-pointas
is the case with most of the operations described in Chapter 7or you can use a blank configuration.
For a blank configuration, use the New command in the File menu:
Set the Protocol Mode property to FIPIO-MB Gateway in the ABC-LUFP element;
Set the Fieldbus Type and Profile properties to FIP I/O and FED C32, respectively, in the Fieldbus element.
The creation of new configurations is performed entirely under PL7 PRO. Only transfer a new
configuration to the gateway if it signals a Hardware configuration fault (see Section 7.5.1).
7.8. Deleting a Modbus Slave

This step allows you, for instance, to free up a location on the downstream Modbus network, known as the SubNetwork in ABC-LUFP Config Tool, in order to replace one Modbus slave with another.
In fact the gateways standard configuration already allows it to communicate with eight TeSys U motor starters,
and the maximum number of Modbus slaves with which it is permitted to communicate is limited to eight.
1743315 03/2009
73

If the gateway is used to manage exchanges on a Modbus network with fewer than eight TeSys U motor starters, it
is preferable to delete the redundant TeSys U motor starters from the gateway configuration: the deterioration in
performance caused by the absence of one or more TeSys U motor-starters is such that it is preferable to carry out
this operation using ABC-LUFP Config Tool.
Procedure for deleting a Modbus slave
1)
Select the node corresponding to the Modbus slave you wish to delete from the configuration. If this is the only
node remaining in the configuration, you will not be able to delete it, as the downstream Modbus network must
include at least one slave.
2)
Right click on the icon or the name of this Modbus slave. A menu pops up underneath the mouse cursor.
or
In the ABC-LUFP Config Tool main menu, pull down the menu with the same name as the previously selected
node.
3)
In this menu, click Delete. The following confirmation window then appears, asking you to either confirm that
you want to delete the selected node (TeSys U n2 in this example) or cancel the operation.
4) If you confirm that you want to delete the node, the menu
disappears, along with the previously selected node.
Otherwise, the node will still be there when the window
closes.
Keyboard shortcut: Del key.
74
1743315 03/2009

7.9. Adding a Modbus Slave
This feature allows you to add a Modbus slave of a different type to the other Modbus slaves in the configuration.
On the other hand, if the slave is of the same type as one of the previously configured slaves, it is preferable to
copy the old slave rather than create a new one.
An additional import/export feature also allows you to individually save the complete configuration of a Modbus
slave, in order to have access to it in ABC-LUFP Config Tool, from any configuration and at any time.
These two features are only available provided that there are fewer than 8 Modbus slaves declared, which is not
the case in the standard configuration, as it comprises 8 TeSys U motor starters.
Adding a new type of Modbus slave
Use one of the two methods described below:
a)
Select Sub-Network, then choose Add Node from the Sub-Network menu. A new node is added after all
the other configured nodes. By default, its name is New Node.
b)
Select one of the nodes located under the Sub-Network element, then choose Insert New Node from the
menu with the same name as the selected node. A new node is added just before the selected node. By
default, its name is New Node.
All of the steps in configuring the new node are described in Section 7.11.
Copying a previously configured Modbus slave
Select the node corresponding to the slave whose configuration you want to copy, then choose Copy from the
menu with the same name as the selected node. Keyboard shortcut: Ctrl C.
Then use one of the two methods described below:
a)
Select Sub-Network, then choose Paste from the Sub-Network menu. A new node is added after all the
other configured nodes. Its name and its whole configuration are identical to that of the node you copied.
Keyboard shortcut: Ctrl V.
b)
Select one of the Sub-Network nodes, then choose Insert from the menu with the same name as the
selected node. A new node is added just before the one which is selected. Its name and its whole
configuration are identical to that of the node you copied.
As the new node and the original node are identical in every way, you will need to change (1) the name of the
node, (2) the address of the corresponding Modbus slave and (3) the location of the data exchanged between the
gateway memory and the Modbus slave. All these operations are described in Section 7.11 and Section 7.12.
WARNING
DUPLICATE MODBUS ADDRESSES OR GATEWAY MEMORY RANGES
If you choose to add a Modbus slave by copying the configuration of an existing Modbus slave, you must
change the added devices Modbus address and the memory locations it uses to exchange data with the
gateway.
Duplicated Modbus addresses or gateway memory locations may result in communications errors, incorrect
information being written to a slaves registers, or in writing the registers of an unintended device. Any of
these errors may result in unintended equipment operation.
Importing/exporting a Modbus slave configuration
With ABC-LUFP Config Tool you can independently save and load a node configuration on the downstream SubNetwork. This allows you, for example, to build up a library of Modbus slave templates, so that you can use them
in any configuration.
To save the configuration of a Modbus slave, select the node it corresponds to, then choose Save Node from the
menu with the same name as the selected node. A dialog box will then appear asking you to save the configuration
(export in XML format).
1743315 03/2009
75

To insert a node using the XML file containing a Modbus slave configuration as a template, use one of the two
methods described below:
a)
Select Sub-Network, then choose Load Node from the Sub-Network menu. A dialog box asks you to
choose a file containing a Modbus slave configuration (import in XML format). A new node is added after all
the other configured nodes. Its name and its whole configuration are identical to those of the Modbus slave as
configured when last saved.
b)
Select one of the Sub-Network nodes, then choose Insert from File from the menu with the same name as
the selected node. A new node is added just before the selected node. Its name and its whole configuration
are identical to those of the Modbus slave as configured when last saved.
You will then need to change (1) the name of the node, (2) the address of the corresponding Modbus slave and (3)
the location of the data exchanged between the gateway memory and the Modbus slave. All these operations are
described in Section 7.11 and Section 7.12.
WARNING
DUPLICATE MODBUS ADDRESSES OR GATEWAY MEMORY RANGES
If you choose to add a Modbus slave by copying the configuration of an existing Modbus slave, you must
change the added devices Modbus address and the memory locations it uses to exchange data with the
gateway.
Duplicated Modbus addresses or gateway memory locations may result in communications errors, incorrect
information being written to a slaves registers, or in writing the registers of an unintended device. Any of
these errors may result in unintended equipment operation.
76
1743315 03/2009
7.10. Modifying Periodic Data Exchanged with Modbus Slaves

This involves replacing, adding or deleting periodic data exchanged with one of the Modbus slaves. For each of
these operations, we shall take the standard configuration as described in Chapter 6) as the starting-point: any
changes previously made will have been cancelled at the start of each operation. Each operation is illustrated
below by a specific example.
Always remember to save the changes you have made, or to transfer the whole configuration to the gateway. This
will allow you to check that the configuration is valid, as the gateway automatically verifies the configuration when it
is downloaded.
7.10.1. Replacing a Periodic Input
E.g. TeSys U Motor starter n3: we want to replace the TeSys U Status Register control (address 455 = 0x01C7)
with the 1st Fault Register control (address 452 = 0x01C4).
The operation is a very simple one and consists merely of changing the value of the Starting Register Address
element in the Query of the Read Holding Registers command (Modbus command for reading values of multiple
registers).
Select this element, then change its value as shown at the top of the next page. You can enter the address of the
parameter in decimal format: ABC-LUFP Config Tool will automatically convert it to hexadecimal.
This operation in no way alters the contents of the gateway memory, as we do not need to change the values of the
Data length and Data location fields in the Data element of the Response to the aforementioned command;
so no additional operations are required in ABC-LUFP Config Tool.
However, the FIPIO master PLC application will have to take account of the change in the nature of the
corresponding input. In Input Data Memory, Appendix C, the description of the word located at address 0x0004
becomes Value of the 1st fault register of motor starter . This word corresponds to PLC input word
%IW\p.2.c\0.0.2 (see Section 4.2.7, Section 5.1.1, and Section 5.1.3).
1743315 03/2009
77

7.10.2. Replacing a Periodic Output
E.g. TeSys U Motor starter n6: we want to replace the Command Register command (address 704 = 0x02C0)
with the 2nd Command Register command (address 705 = 0x02C1).
This operation consists in changing the value of the Starting Register Address element in the Query and the
value of Starting Address in the Response to the Preset Multiple Registers command (Modbus command for
writing values to multiple registers).
Select Starting Register Address in the Query and modify its value as shown at the top of the next page. You
can enter the address of the parameter in decimal format: ABC-LUFP Config Tool will automatically convert it to
hexadecimal. Do the same for the Starting Address element of the Response, because the gateway
checks the value of this field when it receives each Modbus response. If the value does not correspond to that of
the query, the gateway will ignore the response.
This operation in no way alters the contents of the gateway memory, as we do not need to change the values of the
Data length and Data location fields in the Data element of the Query. No additional operations are required
in ABC-LUFP Config Tool.
However, the FIPIO master PLC application will have to take account of the change in the nature of the
corresponding output. In Output Data Memory, Appendix C, the description of the word located at address 0x020A
becomes Value of the 2nd command register of motor starter . This word corresponds to the PLC output word
%QW\p.2.c\0.0.5 (see Section 4.2.7, Section 5.1.1, and Section 5.1.3).
7.10.3. Increasing the Number of Periodic Inputs
E.g. TeSys U motor starter n2: we want to extend the controls on this motor starter, starting with the currently
controlled registerTeSys U Status Register (address 455 = 0x01C7)and expanding as far as the Reserved:
nd
2 Warning Register (address 462 = 0x01CE). This will bring the number of registers controlled from 1 up to 8.
The necessary operations are described below:
78
1743315 03/2009

1)
Change the number of registers controlled: This step consists in modifying the value of the element Number
of Registers in the Query of the Read Holding Registers command (Modbus command for reading the
values of multiple registers). Select this element, then change its value as shown at the top of the next page.
ABC-LUFP Config Tool will automatically convert any value entered in decimal to hexadecimal.
2)
Change the number of data bytes in the Modbus response: The number of bytes read from the memory of
TeSys U motor starter n2 increases from 2 to 16, as the number of registers controlled has increased from 1
to 8. Select the Byte count element in the Response and change its value as shown below. ABC-LUFP
Config Tool will automatically convert any value entered in decimal to hexadecimal.
3) Change the location of the Modbus data received in the gateway memory: As the number of bytes read
(see previous step) has increased from 2 to 16, the Modbus data received must be placed at a different
location in the gateway memory.
If you are unsure how much of the gateways memory is currently in use, select Sub-Network and choose
Monitor from the Sub-Network menu. The following window appears, allowing you to see how much of the
gateways memory is occupied.
1743315 03/2009
79
To see which memory locations are occupied by data from the command we are interested in, simply uncheck the
box corresponding to the Read Holding Registers command in the TeSys U n2 node, as shown above. This
reveals that the Modbus data received in response to this command occupy 2 bytes, starting at 0x0002.
NOTE: Only memory locations 0x0000 to 0x0033 can be used (max.size of input data = 52 bytes).
Using any other address in the gateways input data memory area (0x0034 to 0x01FF) will throw the gateway into
GATEWAY. LEDs
non-operational mode, signaled by the sudden red-green flashing of LED
will also flash, at a frequency of 2 Hz.
You can ignore the size indications on the graphics in this window (In Area 16 bytes and Out Area 16 bytes), as
the gateway has a fixed size for inputs and outputs alike.
If you want to memories the 16 bytes of Modbus data which will be received by the gateway for this command,
oncethe changes have been made, you will have to either shift all the other input data by 14 bytesa painstaking
operationor else change the memory location of the block of data received. In the example described here, we
will be using the second solution, although the first solution is actually preferable, in principle, as it avoids leaving
any holes in the gateways memory. This has no impact on the FIPIO exchanges; however, as the size of
transfers over the gateway is set at 32 input words and 32 output words by the use of the standard profile FED C32
(P).
We will be placing the 16 bytes of data starting at address 0x0010 (16 in decimal), i.e. directly after the input data
from the standard configuration. The 2 bytes at 0x0002 and 0x0003 become free memory locations.
Close the Sub-network Monitor window, then, once you are back in the main ABC-LUFP Config Tool window,
select the Data length and Data location fields respectively in the Data element of the Response and change
their values as shown at the top of the next page. ABC-LUFP Config Tool will automatically convert any value
entered in decimal to hexadecimal.
80
1743315 03/2009

To check that these changes have been integrated into the configuration, choose the Monitor command again in
the Sub-Network menu:
4)
Download this configuration to the gateway: See Section 7.5. Check that the configuration is valid (LED
GATEWAY flashing green).
5)
Save the configuration to your PCs hard disk.
6)
Use the FIPIO master PLC inputs: It only remains to assign symbols and use the inputs corresponding to the
new Modbus data read on motor starter n2.
This gives us the mapping shown on the next page, derived from the one used for the standard gateway
configuration. Changes in relation to the standard configuration are flagged by a grey background (except for the
reserved word %IW\p.2.c\0.0.26).
1743315 03/2009
81
7.10.4. Increasing the Number of Periodic Outputs

E.g. TeSys U motor starter n4: we want to extend the commands on this motor starter, retaining the currently
commanded register, Command Register (address 704 = 0x02C0), and adding the next register, 2nd Command
Register (address 705 = 0x02C1). This will bring the number of registers commanded from 1 up to 2.
The necessary operations are described below:
1)
Change the number of registers commanded: This step consists in modifying the value of the element No. of
Registers in both the Query and Response of the Preset Multiple Registers command (Modbus
command for writing values to multiple registers). Start by selecting the element Starting Register Address in
the Query: change its value as shown at the top of the next page. ABC-LUFP Config Tool will automatically
convert any value entered in decimal to h exadecimal. Do the same for the Starting Address element of
the Response, because the gateway checks the value of this field when it receives each Modbus response.
If the value does not correspond to that of the query, the gateway will ignore the response.
82
1743315 03/2009
2)
Change the number of data bytes in the Modbus query: The number of bytes written to the memory of TeSys
U motor starter n4 increases from 2 to 4, as the number of registers commanded has increased from 1 to 2.
Select the Byte count element in the Query and change its value as shown below. ABC-LUFP Config Tool
will automatically convert any value entered in decimal to hexadecimal.
3) Change the location of the Modbus data transmitted to the gateway memory: As the number of bytes
transmitted (see previous step) has increased from 2 to 4, the Modbus data to be sent to TeSys U motor
starter n4 must be placed at a different location in the gateway memory.
If you are unsure how much of the gateways memory is currently in use, select Sub-Network and choose
Monitor from the Sub-Network menu. The following window appears, allowing you to see how much of the
gateways memory is occupied.
1743315 03/2009
83
To see which memory locations are occupied by data from the command we are interested in, simply uncheck the
box corresponding to the Preset Multiple Registers command in the TeSys U n4 node, as shown above. This
reveals that the Modbus data transmitted with the query for the command occupy 2 bytes, starting at 0x0206.
NOTE: Only memory locations 0x0200 to 0x0233 can be used (max. size of input data = 52 bytes).
Using any other address in the gateways output data memory area (0x0234 to 0x03FF) will throw the gateway into
GATEWAY. LEDs
non-operational mode, signaled by the sudden red-green flashing of LED
will also flash, at a frequency of 2 Hz.
You can ignore the size indications on the graphics in this window (In Area 16 bytes and Out Area 16 bytes), as
the gateway has a fixed size for inputs and outputs alike.
If you want to memories the 4 bytes of Modbus data which will be transmitted by the gateway for this command,
once the changes have been made, you will have to either shift all the other transmitted data by 2 bytesa
painstaking operationor else change the memory location of the block of data transmitted. In the example
described here, we will be using the second solution, although the first solution is actually preferable, in principle,
as it avoids leaving any holes in the gateways memory. This has no impact on the FIPIO exchanges; however, as
the size of transfers over the gateway is set at 32 input words and 32 output words by the use of the standard
profile FED C32 (P).
We will be placing the 4 bytes of data starting at address 0x0210 (528 in decimal), i.e. directly after the output data
for the standard configuration. The 2 bytes at 0x0206 and 0x0207 become free memory locations.
Close the Sub-network Monitor window, then, once you are back in the main ABC-LUFP Config Tool window,
select the Data length and Data location fields respectively in the Data element of the Query and change
their values as shown at the top of the next page. ABC-LUFP Config Tool will automatically convert any value
entered in decimal to hexadecimal.
84
1743315 03/2009

To check that these chang
es have been integrated into the configuration, choose the Monitor command again in the Sub-Network menu:
4)
Download this configuration to the gateway: See Section 7.5. Check that the configuration is valid (LED
GATEWAY flashing green).
5)
Save the configuration to your PCs hard disk.
6)
Use the FIPIO master PLC outputs: It only remains to assign symbols and use the outputs corresponding to
the new Modbus data sent to motor starter n4.
This gives us the mapping shown on the next page, derived from the one used for the standard gateway
configuration. Changes in relation to the standard configuration are flagged by a grey background (except for
the two reserved words %QW\p.2.c\0.0.26 and %QW\p.2.c\0.0.27).
1743315 03/2009
85
7.11. Changing a Modbus Slave Configuration

Configuring a Modbus slave itself remains very simple because it only involves the name and the Modbus address
of the node to which it corresponds. By contrast, configuring Modbus commands is a more complex business and
is discussed in a separate section (see Section 7.12).
You will need to change the configuration of a Modbus slave when you add a new Modbus device (see Section
7.9), using any method.
Changing the name of the node which corresponds to a Modbus slave helps to distinguish it from the other nodes,
for instance when its Modbus command configuration has been changed.
7.11.1. Changing the Name of a Modbus Slave
To carry out this operation, all you have to do is select the node that corresponds to the Modbus slave involved
(Devices: pane), and perform one of the following four actions:
right-click on the node and click on Rename in the popup menu that appears, or
select the node and click on the node's name, or
select the node and choose Rename in the menu whose name matches the node's name, or
use the F2 function key.
After confirming the new name (Enter key or click outside the node's name), it will be used to update the menu bar
and the status bar of ABC-LUFP Config Tool. An example is given below. The three red frames shown in this
example show the consequences of the change made.
86
1743315 03/2009
7.11.2. Changing the Address of a Modbus Slave

To carry out this operation, simply select the node which corresponds to the Modbus slave involved (Devices:
pane), click on the value of the current address (value of the Slave address field in the Configuration: pane), and
change it.
Reminder: The address of a Modbus slave must be between 1 and 247. The system will not let you add a value >
247.
WARNING
USE OF RESERVED MODBUS ADDRESSES
Do not use Modbus addresses 65, 126, or 127 if a gateways Modbus slaves will include a Schneider Electric
Adjustable-Speed Drive System device such as an Altistart soft-starter or an Altivar motor drive. The Altistart
and Altivar devices reserve these addresses for other communications, and the use of these addresses in
such a system can have unintended consequences.
When you confirm the new address (Enter key or click outside the Modbus slave address input field), it
becomeseffective in ABC-LUFP Config Tool, and the values of the Slave Address elements in the queries and
responses of the Modbus commands for the selected node are automatically updated. In the example that follows,
a single Slave Address element is updated:
1743315 03/2009
87

7.11.3. Changing the Name of a Modbus Command
To rename a Modbus Command, first perform one of the following actions:
right-click on the name of the command itself (e.g. Preset Multiple Regs) and click on Rename in the
popup menu that appears, or
select the name of the command and choose Rename in its corresponding menu, or
select the name of the command and click inside its name, or
select the name of the command and press the F2 key.
Then, type the new name of the command, and confirm it (Enter key or click outside the names field) or cancel it
(Escape key). Once confirmed, the new name will become effective in ABC-LUFP Config Tool.
The type of command is automatically appended at the end of the Modbus command's new name.
An example is given below:
This renaming function can also be used

for the Queries and Responses of the
Modbus Commands, as illustrated by the
following example:
7.12. Adding and Setting up a Modbus Command

7.12.1. With TeSys U Motor Starters
With TeSys U motor starters, the main point of adding a Modbus command is to enable you to command or control
additional registers, without having to change the elements in the standard configuration. The periodic and
aperiodic communication services therefore operate in the same way as for the standard configuration, unlike the
various operations described in Section 7.10.
Instead of adding a command and configuring it from scratch, it is easier to copy one of the two default commands
for TeSys U motor startersRead Holding Registers (read / control) or Preset Multiple Regs (write /
command)and paste it into the list of Modbus commands for the appropriate node.
To copy a ready-configured Modbus command, select it, and then choose Copy from the menu with the same
name as the selected command. Keyboard shortcut: Ctrl C. Then proceed with either of the following methods:
a)
Select the node corresponding to the Modbus slave you want to add the command to (e.g. TeSys U n4),
then choose Paste from the menu with the same name as the selected node. A new command is added after
88
1743315 03/2009

all the other commands configured for this node. Its configuration is totally identical to that of the previously
copied command. Keyboard shortcut: Ctrl V.
or:
b) Select one of the commands on the node concerned, then choose Insert from the menu with the same name
as the selected command. A new command is added just before the one selected. Its configuration is totally
identical to that of the previously copied command.
As the new Modbus command and the original Modbus command are identical, you will need to make changes to
in one of the two diagrams below, depending on whether it is a Read Holding
the fields
Registers command or a Preset Multiple Registers command (see Section 7.10). The correspondence between
the different elements in these tree structures and the standard Modbus terminology is shown on the right:
NOTE: In all cases, the Query / Slave Address and Response / Slave Address elements are automatically
updated by ABC-LUFP Config Tool according to the node in which the command is located. Their values are not
usermodifiable. Likewise, the Query / Function code and Response / Function code fields depend on the nature
of the Modbus command and cannot be changed by you.
The operations to be carried out are much the same as those used for changing the default commands. For the
Read Holding Registers command, see Section 7.10.1 and Section 7.10.3. For the Preset Multiple Regs
command, see Section 7.10.2 and Section 7.10.4.
1743315 03/2009
89

7.12.2. With a Generic Modbus Slave
Unlike in the previous section, here we will be looking at adding and setting up a Modbus command which is
different from those configured by default with the LUFP1 gateway. We will use this opportunity to take an in-depth
look at the fields with which you can set up communications for such commands.
See Appendix E for a list and description of the Modbus functions supported by the LUFP1 gateway. Only a very
few Modbus commands are authorized, in order to limit the complexity of configuring Modbus exchanges on the
gateway. Moreover, ABC-LUFP Config Tool cannot be used to configure new Modbus commands (created from
scratch) for LUFP1 gateways.
E.g. To illustrate the various operations to be carried out and the explanations given, we will be taking the example
of a Altistart starter, the ATS48, and a Modbus command recognized both by the gateway and the ATS48. This is
the Preset Single Register command, whose function code is 6 and which allows you to write the value of a single
output word. This function will be used to periodically write the value of the ATS48s CMD command register,
located at address W400 (address 400 = 0x0190).
As the standard gateway configuration already has 8 Modbus slaves, you will need to delete one of them, such as
the TeSys U n2 node, for example, and to add a new node in its place (see Section 7.8, and Section 7.9).
After creating the new node, we rename
it and assign it Modbus address 10, as
shown at right:
We then add the Preset Single
Register command by choosing Add
Command from the ATS48 menu.
In the window which appears (opposite), select the command 0x06

Preset Single Register and choose Select in the File menu.
Back in the main ABC-LUFP Config Tool window, the Preset Single
Register command now appears in the list of Modbus commands for
the ATS48 node.
90
1743315 03/2009

Expand the full tree structure for this command, as shown below. The correspondence between the different
elements in this tree structure and the standard Modbus terminology is shown on the right:
These elements can be configured using ABC-LUFP Config Tool. There is a description of them in the following
sections. We will then return to the example of the ATS48 to illustrate how to use these elements.
7.12.2.1. Managing Degraded Modes
Due to the number of hardware elements and software tools used, the following table shows a summary of the
various degraded modes available to a FIPIO application. In this instance, the application is running on a LUFP1
gateway and a Premium PLC with a FIPIO master coupler on its processor card.
(1) The Offline options for fieldbus and Offline options for sub-network are described in the next section.
(2) The desired behavior with regard to outputs should be directly configured on each of the Modbus slaves. In
the case of drives marketed by Schneider Electric, for instance, the outputs are reset by setting the NTO bit to
0 (command with communication control), and held by setting NTO to 1 (command without communication
control).
(3) As regards inputs, we strongly recommend that you use the List of Active Slaves (LAS) Service (see Section
5.2) to detect the underlying event.
(4) Use the gateways FIPIO Diagnostic Objects (Section 5.4) to detect the underlying event.
1743315 03/2009
91

Managing Degraded Modes (7.11.2.1)
Outputs:
Software error, outputs reset to default state or hold their present state depending on configuration.
Hardware error (EEPROM or hardware failure), output state will be undetermined
Inputs: PLC stops responding to inputs in any error state.
Depending on the configuration of the FIPIO master:
the FIPIO master stops to communicate with the LUFP1 gateway, or
the FIPIO master forces outputs to 0 and refreshes the inputs, or
the FIPIO master holds outputs in their last state and refreshes the inputs.
If the FIPIO master stops communicating with the LUFP1 gateway (in the case of a Premium PLC), for each
Modbus Command, the behavior depends on its Offline options for fieldbus:
Clear:
The output data sent to the Modbus slave concerned is reset to 0 and the input memory
continues to be refreshed with the data of the slaves' response.
Freeze:
The output data sent to the Modbus slave concerned retains its current value and the
input memory continues to be refreshed with the data of the slaves' response.
No Scanning: The query of this Modbus Command is no longer transmitted and the input memory is no
longer refreshed with the data of the slaves' response.
If the FIPIO master forces outputs to 0 and refreshes the inputs, the periodic Modbus exchanges continue to
run:
all output Data are reset to 0 and sent to the Modbus slaves,
the input memory continues to be refreshed with the Data of the Modbus slaves' responses,
If the FIPIO master forces holds outputs in their last state and refreshes the inputs, the periodic Modbus
exchanges continue to run:
all output Data stay in their last state and are sent to the Modbus slaves,
the input memory continues to be refreshed with the Data of the Modbus slaves' responses,
TeSys U response
Depending on the slave.
FIPIO scanner stopped or on failure
The PLC processor provides some error and/or diagnostic objects to the application if FIPIO master stop or
failure (input/output not valid) occurs.
Refer to the PLC user manual for their description.
If the FIPIO master is stopped (command coming from the application):
the scanner stops communicating with the LUFP1 gateway.
If the FIPIO master is on failure:
the scanner stops communicating with the processor and the LUFP1 gateway.
Clear:
The output data sent to the Modbus slave concerned is reset to 0 and the input memory
Freeze:
No Scanning: The query of this Modbus Command is no longer transmitted and the input memory is no
longer refreshed with the data of the slaves' response.
TeSys U response
92
1743315 03/2009

PLC response
The PLC processor provides some error and/or diagnostic objects to the application if slave disconnection from
the application occurs.
The FIPIO master provides the processor with some error and diagnostic objects if FIPIO slave disconnection
occurs.
Clear: The output data sent to the Modbus slave concerned is reset to 0 and the input memory
Freeze:
No Scanning: The query of this Modbus Command is no longer transmitted and the input memory is
no longer refreshed with the data of the slaves' response.
TeSys U response
PLC response
The PLC processor provides some error and/or diagnostic objects to the application if slave failure to the
application occurs.
The FIPIO master provides the processor with some error and diagnostic objects if FIPIO slave failure occurs.
In case of a failure, the gateway stops communicating with the FIPIO master and the Modbus slaves.
TeSys U response
1743315 03/2009
93

LUFP1 gateways disconnected on Modbus side or slave failure
PLC response
The processor has access to the List of Active Slaves (LAS) coming from the FIPIO master input table.
Depending on the following properties, all of which are configurable for each Modbus Command:
Timeout time (10 ms) = x 10 ms,
Retries = y,
Reconnect time (10 ms) = z 10 ms, and
Offline options for sub-network = Clear / Freeze.
After sending a request to a slave, if there is no response after (x 10) ms, the gateway will send it again y
times before writing information about the missing slave to the List of Active Slave (LAS), if no other Modbus
Command has succeeded for this slave.
If, despite the y Retries, there is no answer from the slave, the input Data sent to the FIPIO master (Read
requests) is reset to 0 (if Clear) or retains its current value (if Freeze), but only for the data received from the
missing slave.
The gateway will try to reconnect the missing slave by communicating with it again every (z 10) ms.
Slave response
If the LUFP1 gateway is disconnected on Modbus side, the behavior depends on the slave.
In the event of a slave failure:
No response is sent to the gateway and the state of the slave is undetermined.
94
1743315 03/2009

7.12.2.2. Configuring the Query
Select the Query element from the Modbus command. The
various elements in the configuration of the query for this
command are shown opposite. The values displayed
correspond to the default values for any new command.
These elements allow you to configure how the whole command
is managed, including how degraded modes are managed
(number of retransmissions, for example).
Each of these elements is described, in order, in the table below. When a unit is assigned to an element, it is
shown in brackets after the name of that element.
Configuration
element
Offline options for
fieldbus
Reconnect time
(10ms)
Default value:
10ms x 1000 =
10s
Retries
Default value: 3
Timeout time
(10ms)
Default value:
10ms x 100 = 1s
1743315 03/2009
Description
This element affects the data sent to the Modbus slave, only for the command to which
the element belongs, whenever the gateway is disconnected from the FIPIO network. It
takes one of the following three values:
- Clear .............All data sent to the Modbus slave using this command is now set to 0x0000
(resetting the output data in the gateways memory).
- Freeze...........All data sent to the Modbus slave using this command retains its current
value (freezing the output data in the gateways memory).
- NoScanning ..The command is no longer transmitted to the Modbus slave by the
gateway.
If there is no response from the Modbus slave to a query, or following the receipt of an
incorrect response, the gateway uses the Retries and Timeout time (10ms) elements to
carry out retransmissions. If the Modbus slave has still not responded correctly after these
retransmissions, the gateway stops sending it the corresponding query for a period of time
which can be adjusted using Reconnect time (10ms).
When this period is over, the gateway attempts to restore communication with the Modbus
slave.
This element indicates the number of retransmissions carried out by the gateway if there is
no response from the Modbus slave to a query, or if the response is incorrect. This
retransmission process ceases as soon as the gateway gets a correct response within a
given time. If none of the retransmissions elicits a correct response, the Modbus slave is
deemed to be off-line, but only as regards the command in question. The gateway then
uses the Offline options for sub-network and Reconnect time (10ms) elements, and LED
MODBUS becomes red. It will only revert to green when the Modbus command receives a
correct response, following reconnection (see the element Reconnect time (10ms)).
If the number of retransmissions is set to 0, this process will not be executed.
This element represents the time that the Modbus slave will wait for a response. If a
response has not reached the gateway within the given time, as defined by this element,
the gateway tries retransmitting. This process continues until it reaches the last
retransmission allowed (see Retries), then the gateway declares the Modbus slave offline,
but only for the command to which the element timeout time (10ms) belongs.
95

Configuration
element
Trigger byte
address
Description
This element is only used by the gateway if Update mode is set to Change of state on
trigger. In this case, it specifies the address, in the gateways output memory (0x0200 to
0x0233), of an 8-bit counter managed by the FIPIO master. The FIPIO master updates this
counter in the same way as the other gateway outputs (see Section 5.1.3).
When the value located at this address is changed by the FIPIO master to any value other
than zero, the query configured with a Change of state on trigger for that address is
transmitted to the Modbus slave by the gateway.
Unlike the On data change and Change of state or Cyclically modes, this mode enables
you to send a command on a specific order from the FIPIO master if, for example, the latter
is unable to update all the data for any given query at the same time.
Update mode
NOTE: The trigger byte does not have to be an output updated by the FIPIO master. It is
quite possible for it to be an input between 0x0000 and 0x0033, in which case
theexchanges of the command currently being configured will be conditioned by the
Modbus slave that upd ates the byte.
This element is used to specify the transmission mode for the query on the Modbus
network. It takes one of the following four values:
- Cyclically.................................Default communication mode. The query is transmitted
periodically over the Modbus network (see Update time).
This is the communication mode used systematically for all
Modbus commands generated by the periodic control words configured by the user
under PL7 PRO.
- On data change ...................... The gateway transmits the query over the Modbus network
when at least one data item in the query is modified by the FIPIO master. This is
therefore an aperiodic communication mode that works in a similar way to the
indexed periodic variables (PKW) service described in Section 5.3. All the data from a
single query must therefore be updated at the same time by the FIPIO master. If you
are uncertain as to whether your software is able to update all the output data from a
query at the same time, we recommend using Change of State on trigger mode
rather than On data change.
- Single Shot ............................. This transmission mode only allows a single Modbus
exchange for the whole of the time that the gateway is operating. This exchange takes
place just after the initialization of the gateway.
- Change of state on trigger ...... With this aperiodic communication mode, the Modbus
query is sent every time that the FIPIO master changes the value of an 8-bit counter
designated by the Trigger byte address element. See the description of this element
for further information about how to use this communication mode.
- Change of state or Cyclically .... In this communication modea combination of the
Cyclically and On data change modesthe query is transmitted periodically over
the Modbus network (see Update time), and also whenever one of the outputs in the
query is modified by the FIPIO master.
Update time
(10ms)
This is the communication mode used systematically for all

Modbus commands generated by the periodic command words configured by the user
under PL7 PRO.
This element is only used by the gateway if Update mode is set to Cyclically or Change
of state or Cyclically. In this case, it specifies the querys transmission period on the
Modbus network.
Default value:
10ms x 100 = 1s
96
1743315 03/2009

For example, with the ATS48, we will be using the configuration
shown opposite. The most notable points of this configuration are:
The data are reset when either network is disconnected.
3 retransmissions with a 100 ms timeout.
Periodic communications with a cycle time of 300 ms.
7.12.2.3. Configuring the Response

Select the Response element from the Modbus command. The
various configuration elements of the response for this command
are shown opposite. The values displayed are the default values
for any new command.
These elements allow you to configure just one command management feature, described below. The elements
are described, in order, in the following table:
Configuration
Description
element
Offline options for
This element affects the input data sent to the FIPIO master, but only for the data of
sub-network
the Response to which this element belongs to, whenever the Modbus slave does not
answer to the corresponding Query (or upon disconnection from the Modbus subnetwork).
This element takes one of the following two values:
Clear
All data sent to the FIPIO master for this Response is set to 0x0000
(resetting of the input data in the gateways memory).
Freeze All data sent to the FIPIO master for this Response retain their current
values (the input data in the gateways memory is frozen).
Trigger byte
This element is used by the gateway to activate the unitary incrementation of an 8-bit
counter in order to notify the FIPIO master of the receipt of a new response to the
associated Modbus command. It takes one of the following two values:
- Disabled..................................Default configuration. The gateway does not increment
any counter on receipt of the Modbus response.
- Enabled................................... Each time that the gateway receives a new response to
the associated Modbus command, it increments the value of an 8-bit counter
designated by the Trigger byte address element (see below). This is useful
when the command query is configured to use one of the aperiodic
communication modes (see Update mode), as the counter mechanism allows
the FIPIO master to ignore response input data except when the counter is
incremented.
Trigger byte
This element is only used by the gateway if the element Trigger byte is set to
address
Enabled. In this case, it specifies the address, in the gateways input memory (0x0000
to 0x0033), of an 8-bit counter managed by the gateway. The FIPIO master reads the
value of this counter in the same way as the other gateway inputs (see Section 5.1.3).
When the gateway receives a response to the associated Modbus command, it
increments the value of this counter by one unit (value = value+1).
This mode keeps the FIPIO master informed when a new response is available. This
can be useful, for example, where there is a chance that the data from two consecutive
responses could be identical.
For example, with the ATS48, we do not want the response to be event driven, so we will retain the default
configuration.
1743315 03/2009
97

7.12.2.4. Configuring the Content of the Query Frame
The window below is obtained using Edit Transaction from the Query menu. Unlike the tree structure in the main
ABCLUFP Config Tool window, this display has the advantage of showing all of the frames fields along with their
values. The values displayed below are the values assigned by default to the Modbus command query we have
created. The correspondence with the content of the corresponding Modbus frame is shown underneath.
Slave n
Word n
(MSB / LSB)
Fu n ct ion n
Word valu e (MSB / LSB)
CRC1 6 (LSB / MSB)
Edit the values which are not grayed out, one after the other. There is a description of them below.
The nature of a frames fields depends on the Modbus command to which it corresponds. However, a certain
number of these fields are common to all frames, whereas others are common to a number of them. The
description of those shown above is given on the next page, as a part of the example described at the beginning of
Section 7.12.2.
Field in the
frame
Slave Address
Size in
the frame
1 byte
Description
This field is not user-modifiable and its value is grayed out accordingly. ABCLUFP Config Tool updates the value of this field automatically using the address
of the Modbus slave corresponding to the current node.
NOTE: This field is common to all Modbus command queries.
Function Code
1 byte
Example: The value of this field is set to the address of the Modbus slave
corresponding to the ATS48 node, namely 0x0A.
This field is not user-modifiable and its value is grayed out accordingly. ABCLUFP Config Tool updates the value of this field automatically using the function
code of the corresponding Modbus command.
NOTE: This field is common to all Modbus command queries.
Register
Address
2 bytes
E.g. The value of this field is set to the code for the Preset Single Register
command (write the value of an output word), namely 0x06.
Address of an output word, or of a register, in the Modbus slaves memory. This
field designates the memory object to which the command relates.
NOTE: This field is common to all Modbus command queries which seek to
access one or more locations in the memory of a Modbus slave. When accessing
several memory locations, the Register field designates the address of the first
word affected by the command.
E.g. The value of this field should be changed by entering the address of the
CMD command register, namely 400 (0x0190). This value will be automatically
converted to hexadecimal if the user enters it in decimal.
Preset Data
2 bytes,
or more for a
data block
Data Location: Address, in the gateways output data memory (0x0200 to

0x0233), of the datum to be transmitted in the Preset Data field of the query
frame.
NOTE: The Data location field is used for each frame that conveys data
between the Modbus slaves and the FIPIO master. In this instance, it
designates the starting address of the data block to be transmitted.
98
1743315 03/2009

WARNING
You must use even values for the Data Location field (i.e. 514, 516, 518, etc.). The selection of odd
locations complicates application programming.
Returning to our previous example, the value to be assigned to the ATS48s
CMD register should be placed in the gateways output data memory area. We
will be using the first free location starting at an even address, i.e. 0x0210 in
the case of the standard configuration.
------------------------------------------------------------------------------------------------------Data length: Length of the output data block, in the gateways memory, of
which the values are to be transmitted in the Preset Data field of the query
frame. It is expressed in number of bytes.
NOTE: The Data length field is always used together with the Data location
field, described above.
E.g. Since the Preset Single Register command is used to write the value of
a single (16-bit) register, the value of the Data length field must be set to 2.
See the documentation for each Modbus slave to find out the maximum
amount of 8-bit data which can be placed in Data type fields in the queries
and responses for this slave. With the ATS48, for instance, the maximum is 30
16-bit words.
-------------------------------------------------------------------------------------------------------Byte swap: Specifies whether or not the output data bytes to be transmitted to
the Modbus slave must be swapped before being placed in the Modbus frame.
The three possible values are as follows:
- No swapping .......Default configuration. The data is sent in the same order
as it appears in the gateways memory. This is the case which must be
used by default, because for a 16-bit datum, the most significant byte
(MSB) is placed first in the Modbus frame, and is always written MSBfirst into the gateways memory by a FIPIO master.
- Swap 2 bytes.......The bytes to be transmitted are swapped two by two.
- Swap 4 bytes.......The bytes to be transmitted are swapped four by four. This
is rarely used, as it only relates to 32-bit data. It works along the same
lines as Swap 2 bytes.
Example: We will be using the No swapping value, because the two bytes
ofthe value to be written into the ATS48s CMD register, as transmitted by
theFIPIO master, are placed in the gateway memory MSB-first.
1743315 03/2009
99

Field in the
frame
Checksum
Size in
the frame
2 bytes
Description
Error check type: Type of error check for the frame.
- CRC.....................Default method.
This is the method adopted for the Modbus RTU protocol. It cannot be changed.
-----------------------------------------------------------------------------------------------------------Error check start byte: Indicates the number of the byte, in the frame, from which
the checksum calculation should begin. The first byte in each frame carries the
number 0.
NOTE: The calculation of a frames checksum should always begin with the first
byte. Do not change the error check start byte from its default of zero. A non-zero
value will result in an incorrect CRC, and all Modbus communications
will return an error.
7.12.2.5. Configuring the Content of the Response Frame

The window shown below is obtained using Edit Transaction from the Response menu. The values displayed
are those assigned by default to the Modbus command response we have created. The correspondence with the
content of the corresponding Modbus frame is shown underneath.
Slave n
Fu n ct ion n
Word n
(MSB / LSB)
Word valu e (MSB / LSB)
CRC1 6 (LSB / MSB)
Edit the values which are not grayed out, one after the other.
There is a description of them below, but also see the previous section, as the nature of the content of response
frames is very similar to that of the fields in Modbus query frames.
NOTE: If the value of one of the fields in the response from a Modbus slave is different from that configured via
ABCLUFP Config Tool, the response will be rejected by the gateway. It will then proceed to retransmit the query,
provided that at least one retransmission has been configured for this command (see 7.12.2.2 Configuring the
Query).
100
1743315 03/2009

Field in the
frame
Slave Address
Function Code
Register
Address
Size in
the frame
1 byte
1 byte
2 bytes
Preset Data
2 bytes,
or more
for a data
block
Description
Identical to the querys Slave Address field.
Identical to the querys Function field
Identical to the querys Register field, since the Modbus response of any
Preset Single Register command is an echo to the corresponding query. Here
you should also enter the address of the memory object to which the command
relates.
If receiving an exception code, see (*).
Data Location: Address, in the gateways input data memory (0x0000 to
0x0033), of the datum received in the Preset Data field of the response frame.
NOTE: As far as possible, ensure that the data is located at even-numbered
addresses in order to align the Modbus data (in 16-bit format) with the
%IW\p.2.c\0.0. inputs of the FIPIO master.
E.g. The value sent back as an echo to the command must be placed in the
gateways input data memory area. We shall use the first two free bytes
following the standard configuration input data, i.e. 0x0020-0x0021.
* If receiving an exception code, the gateway re-transmits the request according to the number of retries that has
been defined. Then, it will disconnect the slave.
WARNING
You must use even values for the Data Location field (i.e. 0, 2, 4, 6, etc.). The selection of odd data
locations complicates application programming and increases the likelihood of improper Modbus values being
written to
or read from the slave devices. Depending on the users configuration, unintended equipment operation may
result
Field in the
frame
Size in the
frame
Description
Data length: Length of the block of input data received in the Preset Data field
of the response frame. It is expressed in number of bytes.
E.g. The value of the Data length field must be set to 2.
---------------------------------------------------------------------------------------------------------Byte swap: Identical to the querys Byte swap field.
Checksum
2 bytes
E.g. We will also be using the No swapping value, for the same reasons as
with the query.
Error check type: Identical to the querys Error check type field.
Error check start byte: Identical to the querys Error check start byte field.
However, these two fields are not user-modifiable and their values are grayed
out accordingly. ABC-LUFP Config Tool updates the values of these fields
automatically using the values in the querys Error check type and Error check
start byte fields.
1743315 03/2009
101

7.13. Configuring the General Characteristics of the Gateway
This operation relates to the gateways general characteristics
(Fieldbus to Sub-Network elements), whereas the previous
sections described the configuration of the Modbus slaves
(elements located under the Sub- Network element).
The Fieldbus element describes the upstream network, i.e. the
FIPIO network in the case of the LUFP1 gateway.
The ABC-LUFP and Sub-Network elements describe the
downstream networki.e. the Modbus network in the case of
the LUFP1 gateway and identify the version number of the
gateway software.
The configuration of these three elements, along with the
commands they give access to, are described in the next three
sections.
7.13.1. Fieldbus Element

Below this element is a list of the mailboxes configured by default. These elements are not described here, as they
areonly designed for the internal management of the gateway. The mailboxes can neither be modified nor deleted.
Their number and nature depend on the type of upstream network.
When the Fieldbus element is selected, you can select the
type of upstream network. With the LUFP1 gateway, you
must not modify the selection FIP I / O.
If your PC is connected to the gateway using the PowerSuite
cable and you are using ABC-LUFP Config Tool in on-line
mode when ABC-LUFP Config Tool starts up, then the type
of upstream network will be detected automatically.
The only command accessible from the Fieldbus menu is Restore Default Mailboxes. The usage of this
command is recommended if you inadvertently inserted a user-defined Mailbox under the Fieldbus device. Since
the usage of user-defined Mailboxes is not described in the present document, only the FIPIO Default Mailboxes
should be set under the Fieldbus device, in the following order:
StartInit
AnybusInit
Fieldbus specific
Fieldbus specific
Fieldbus specific
Fieldbus specific
EndInit
Should any other Mailbox also appear in this list,
please perform the Restore Default Mailboxes
command. Then, confirm the operation by clicking
on the Yesbutton in the confirmation / warning
window that appears.
102
1743315 03/2009

7.13.2. ABC-LUFP Element
The only command accessible from the ABC-LUFP menu is "Disconnect (or Connect if you are in off-line
mode). See chapter 7.3 for details about on-line" and off-line" modes.
In the configuration of the LUFP1 gateways ABC-LUFP element, the Control/Status Word, the Physical
Interface, and the Protocol Mode properties must not be changed. Their value, respectively, must always be set
to Disabled, Serial, and FIPIO-MB Gateway.
These seven properties allow you to configure some of the gateways system aspects:
Control/Status Word: The three possibilities available for this property are not described in the LUFP1
Gateway User Manual, as the option is reserved for other devices in the same product family. This option
must keep its existing value, i.e. Disabled.
Module Reset: By default, this property prevents the gateway from reinitializing itself when there is an
internal operation problem. Changing this option is mainly intended for laboratory type use.
Physical Interface: The only possibility offered by this property indicates that the physical interface of the
downstream network of the gateway (Modbus) is a serial link.
1743315 03/2009
103
Protocol Mode: This property should not be changed, because it indicates the type of protocol used on the
downstream network of the gateway. With the LUFP1 gateway, FIPIO-MB Gateway must not be
deselected. The other possibilities available are reserved for other products from the same family as this
gateway.
NOTE: Be careful not to modify the Protocol Mode property, as it would reset the entire configuration. If, by any
chance, this should happen, start again with a clean basic configuration (see Section 7.6) or load a previously
saved configuration.
Statistics: This property dictates the presence or absence of the two Receive and Transmit Counters in the
input memory of the gateway (see below). The four possibilities are:
Disabled
The two Receive Counter Location and Transmit Counter
Location properties are ignored.
Enable Receive Counter
Only the Receive Counter Location property is used by the
gateway.
Enable Transmit Counter
Only the Transmit Counter Location property is used by the
gateway.
Enable Transmit/Receive Counter
Both the Receive Counter Location and Transmit Counter
Location properties are used by the gateway.
Receive Counter Location: This property is only used by the gateway if Statistics = Enable Receive
Counter or Statistics = Enable Transmit/Receive Counter. It represents the 1-byte input memory address
(from 0x0000 to 0x0033) where the Modbus Responses counter is copied into. This is a modulo 256
counter (i.e. it starts over at 0 once it goes past 255) which is updated each time a Modbus frame is
received by the gateway.
Transmit Counter Location: This property is only used by the gateway if Statistics = Enable Transmit
Counteror Statistics = Enable Transmit/Receive Counter. It represents the 1-byte input memory address
(from 0x0000 to 0x0033) where the Modbus Queries counter is copied into. This is a modulo 256 counter
(i.e. it starts over at 0 once it goes past 255) which is updated each time a Modbus frame is emitted by the
gateway, retries included.
Finally, a useful command from the Help menu will allow you to check the software versions of the LUFP1
gateway (the ABC-LUFP element), but only in on-line mode; of course, it also shows the version of the ABCLUFP Config Tool.
To obtain this information, execute the About
command of the Help menu. An example in
online mode is given here:
In off-line mode, all versions and information from
the Sub-Network and Fieldbus categories are
replaced with Unknown since they could not be
obtained from an existing and connected gateway.
The http://www.hms.se/abc_lufp.shtml text is a
hypertext link. By clicking on it, you are directly
redirected to the Schneider Electric's Web page
dedicated to the ABC-LUFP gateways.
This page features many downloadable items
related to the family of LUFP gateways, including
the latest version of ABC-LUFP Config Tool.
104
1743315 03/2009

7.13.3. Sub-Network Element
The five commands accessible from the Sub-Network menu are:
- Paste: Appends a copy of the last copied node (after a Copy
command on an existing node), or a replica of the cut node (after a
Cut command), to the list of nodes of the Sub-Network element.
This command is only available if a node has been previously
copied or cut, and only if the 8 nodes limit has not been reached
yet.
- Sub-Network Monitor: Allows you to view the mapping between
the Modbus command data and the content of the gateways
memory.
Examples of how to use this command are shown in Sections
7.10.3 and 7.10.4.
- Add Node: Allows you to add a new node on the downstream Modbus network. Each node corresponds to a
different Modbus slave. This command is not available if there are already 8 Modbus slaves, as is the case with the
gateways standard configuration.
- Add Broadcaster: Allows you to add a broadcaster node (see Section 7.13.4).
- Load Node: Allows you to add a pre-configured node on the downstream Modbus network. The configuration for
this node is contained in an XML file (see the section on Importing/Exporting a Modbus Slave Configuration in
Section 7.9). This command is not available if there are already 8 Modbus slaves, as is the case with the gateways
standard configuration.
- Sub-Network Status: In on-line mode (see
Section 7.13.2), this command opens a window
displaying the values of the gateways error counters.
The Update button allows you to refresh the values
of these counters.
When you run this command in off-line mode, all of
the values are replaced by the word Unknown to
show that they cannot be read off the gateway. The
Update button then becomes inaccessible.
NOTE: The Sub Network Status window may be useful to detect problems on the Modbus sub-network. So, if the
number of retransmission errors increases upon using the Update button, this denotes the absence of one or
more slaves, Modbus cabling or speed problems, or invalid Commands. Since retransmission errors tend to lower
the general performances of the Modbus communications, you should undertake actions to prevent these
retransmission errors from increasing.
1743315 03/2009
105

When the Sub-Network element is selected, you have access to all of the options allowing you to configure the
gateways communication protocol format on the Modbus network. The various settings you can make are
described below. All of the Modbus slaves present must support these settings and must be configured
appropriately.
-
Bitrate (bits/s): The gateway

supports a limited number of
communication speeds. Choose
the one that suits your Modbus
network.
Data bits: 8 bits (required).
Parity:
Choose
the
parity
according to the format chosen
for communications on your
Modbus network.
Physical
(required).
PKW Broadcast Interval (10ms):

When the PKW service is used in
broadcast mode (DN = 255), this
option defines the interval
following the transmission of the
broadcast command. The next
Modbus message, of whatever
type, will not be sent by the
gateway until this period has
elapsed. The interval must
therefore be long enough to give
the slowest Modbus slave the
time to process the broadcast
command.
PKW Retries: Number of retransmissions attempted by the gateway when no response, or an erroneous
response, is received from a queried Modbus slave using the PKW service. The retries stop as soon as the
gateway receives a correct response.
PKW Timeout time (10ms): Waiting time for a response from a Modbus slave using the PKW service. When the
timeout elapses, the gateway starts a number of retries (see previous option).
Stop bits: 1 or 2 bits.
106
standard:
RS485
1743315 03/2009

7.13.4. Adding a Broadcaster Node
NOTE: In the specific case of the LUFP1 gateway, you should use the PKW service in broadcast mode (DN = 255)
instead of using a broadcaster node. Thus, you will save precious output data in the limited output memory (from
0x0200 to 0x233), and this data could be used for other Modbus commands. Please refer to section 5.3, for a
description of this service.
A broadcaster node does not correspond to any Modbus slave in particular: it applies to all Modbus slaves. All the
commands configured for this node will be transmitted with the Slave Address field set to 0x00. This means that
all of the slaves will execute the command, although none of them will respond to it.
To add a broadcaster node, select Sub-Network, then choose Add
Broadcaster from the Sub-Network menu. The broadcaster node
created in this way does not count in the limit on the number of
configurable nodes. A simple example is shown here:
The addition and configuration of a Modbus command in the list of
broadcaster node commands is done in the same way as for other
nodes, but with the following differences:
The list of standard Modbus commands which can be used in broadcast is smaller. Only functions 0x06
and 0x10 can be used (see list in chapter 7.11.2).
The command is made up of a query, but does not include any response. The query bears the name of
thecommand itself, instead of the name Query.
The value of the query frames Slave Address field is set to 0x00.
Please see chapter 7.12.2.2, for further details on how to configure a Modbus query
1743315 03/2009
107
Appendix A: Technical Characteristics
Environment
Communication Characteristics
108
1743315 03/2009
1743315 03/2009
109
110
1743315 03/2009

WARNING
USE OF RESERVED MODBUS ADDRESSES
Do not use Modbus addresses 65, 126, or 127 if a gateways Modbus slaves will include a Schneider Electric
Adjustable-Speed Drive System device such as an Altistart soft-starter or an Altivar motor drive. The Altistart
and Altivar devices reserve these addresses for other communications, and the use of these addresses in
such a system can have unintended consequences.
(1) Mode of communication (Update mode) for which the ABC-LUFP Config Tool equivalent is called Change of
state or Cyclically. The query for the command thus configured is transmitted periodically, but this periodicity
is overridden if any of the data to be sent are modified. This command mode prioritizes write commands,
ensuring that they are sent as soon as possible.
1743315 03/2009
111
112
1743315 03/2009
1743315 03/2009
113
Appendix B:
LUFP1 Gateway Settings
The settings described here correspond to the configuration and adjustment parameters for the LUFP1 gateway.
They only exist when the gateway is used according to standard profile FED C32 P. The exchange modes
for the corresponding FIPIO objects are described in Section 5.6. Once they have been downloaded to the
gateway, the values of these parameters can be read and / or replaced using the gateways PKW service (see
Section 5.3.5).
NOTE: Some of the configuration and adjustment parameters cannot be modified after the initial setup of the
gateway using the PLC. See the Configuration Parameters and Adjustment Parameters tables in Chapter 4.2.
Configuration Parameters
The configuration parameters enable the gateway to configure the Modbus commands that it exchanges with the
Modbus slaves. The configuration comprises:
1) The number of periodic write commands (periodic command words) for each slave (0 to 15);
2) The number of periodic read commands (periodic control words) for each slave (0 to 15);
3) The address of each periodic command or control word.
The total number of periodic words (command words + control words) is limited to 26.
Each periodic command word corresponds to a Modbus write command to a single register (function 0x06
Preset Single Register). This command is cyclical, with advance transmission of the write query if the new
value for the register is modified. This exchange mode is equivalent to Update mode = Change of state or
cyclically.
Each periodic control word corresponds to a Modbus read command for several registers (function 0x03
Read Holding Registers), even though the command is used to read a single register. This command is strictly
cyclical. This exchange mode is equivalent to Update mode = Cyclically.
The configuration parameter values for the standard 8 TeSys U motor starter configuration are listed in Section
4.2.4.
114
1743315 03/2009
Appendix B: LUFP1 Gateway Settings
In the above table, the mapping between the addresses of periodic words n1 to 26 and the command and
control words of the various Modbus slaves is not given, because it depends entirely on the numbers of periodic
command and control words for the Modbus slaves as a whole. These periodic words are organized as follows:
(1) If you do not use all of the 26 periodic words available, you must reset the addresses of the unused periodic
words.
Adjustment Parameters
The adjustment parameters enable the gateway to configure the general features of its exchanges with the
Modbus slaves.
The adjustment parameters values for the standard 8 TeSys U motor starter configuration are listed in Section
4.2.5.
1743315 03/2009
115
116
1743315 03/2009
Periodicity of Modbus exchanges and Cycle time of periodic Modbus commands / controls: The
parameters %MW\p.2.c\0.0.25 to %MW\p.2.c\0.0.30 set the cycle time of the Modbus commands corresponding
to the periodic command and control words defined by the configuration parameters:
The periodicity of Modbus exchanges parameters (%MW\p.2.c\0.0.25 and %MW\p.2.c\0.0.26) set fast
or slow periodicities for the periodic command and control words.
Each of the bits in the cycle time of periodic Modbus commands (%MW\p.2.c\0.0.27 and
%MW\p.2.c\0.0.28) determines either fast periodicity (bit at 0) or slow periodicity (bit at 1) for the
commands, both defined by the parameter %MW\p.2.c\0.0.25.
Each of the bits in the cycle time of periodic Modbus controls parameters (%MW\p.2.c\0.0.29 and
%MW\p.2.c\0.0.30) determines either fast periodicity (bit at 0) or slow periodicity (bit at 1) for the
controls, both defined by the parameter %MW\p.2.c\0.0.26.
Addresses of Modbus slaves: Remember that you must define the Modbus slaves starting at Modbus slave
n1 and then on in sequence, without leaving any empty slots.
1743315 03/2009
117

Management of Degraded Modes
The management of degraded modes on the LUFP1 gateway, described in Section 4.1.4, now depends on two
gateway adjustment parameters. The table below is the same as the one in that section, except that the two new
parameters have been included:
(1) See previous page for a description of the adjustment parameter used in this column.
(2) The desired behavior with regard to the outputs should be directly configured on each of the Modbus
slaves. In the case of drives marketed by Schneider Electric, for instance, the outputs are reset by setting
the NTO bit to 0 (command with communication control), and held by setting NTO to 1 (command Without
communication control).
(3) As regards inputs, we strongly recommend that you use the List of Active Slaves (LAS) Service (see
Section 5.2, page 48) to detect the underlying event.
(4) Use the FIPIO Diagnostic Objects (Section 5.4, page 58) to detect the underlying event.
Outputs:
Software error, outputs reset to default state or hold their present state depending on configuration.
Hardware error (EEPROM or hardware failure), output state will be undetermined
Inputs: PLC stops responding to inputs in any error state.
Depending on the configuration of the FIPIO master:
the FIPIO master stops communicating with the LUFP1 gateway, or
the FIPIO master forces outputs to 0 and refreshes the inputs, or
the FIPIO master holds outputs in their last state and refreshes the inputs.
Modbus Command, the behavior depends on bits 0-7 of the %MW\p.2.c\0.0.23 parameter:
0x00 (Freeze)
0x01 (No Scanning) The query of this Modbus Command is no longer transmitted and the input memory is
0x02 (Clear)
The output data sent to the Modbus slave concerned is reset to 0 and the input
memory continues to be refreshed with the data of the slaves' response.
If the FIPIO master forces outputs to 0 and refreshes the inputs, the periodic Modbus exchanges continue to
run:
all output data are reset to 0 and sent to the Modbus slaves,
118
1743315 03/2009

the input memory continues to be refreshed with the data of the Modbus slaves' responses,
If the FIPIO master forces holds outputs in their last state and refreshes the inputs, the periodic Modbus
exchanges continues to run:
all output data stay in their last state and are sent to the Modbus slaves,
the input memory continues to be refreshed with the data of the Modbus slaves' responses
TeSys U response
FIPIO scanner stopped or on failure
The PLC processor provides some error and/or diagnostic objects to the application if FIPIO master stop or
failure (input/output not valid) occurs.
If the FIPIO master is stopped (command coming from the application):
the scanner stops communicating with the LUFP1 gateway.
If the FIPIO master is on failure:
the scanner stops communicating with the processor and the LUFP1 gateway.
For all Modbus Commands, the behavior depends on bits 0-7 of the %MW\p.2.c\0.0.23 parameter:
0x00 (Freeze)
0x02 (Clear)
TeSys U response
PLC response
The PLC processor provides some error and/or diagnostic objects to the application if slave disconnection
from the application occurs.
The FIPIO master provides the processor with some error and diagnostic objects if FIPIO slave
disconnection occurs.
For all Modbus Commands, the behavior depends on bits 0-7 of the %MW\p.2.c\0.0.23 parameter:
0x00 (Freeze)
0x02 (Clear)
TeSys U response
1743315 03/2009
119

PLC response
The PLC processor provides some error and/or diagnostic objects to the application if slave failure to the
application occurs.
The FIPIO master provides the processor with some error and diagnostic objects if FIPIO slave failure occurs.
In case of a failure, the gateway stops communicating with the FIPIO master and the Modbus slaves.
TeSys U response
LUFP1 gateways disconnected on Modbus side or slave failure
PLC response
The processor has access to the List of Active Slaves (LAS) coming from the FIPIO master input table.
Depending on the following properties, all of which are configurable for each Modbus Command:
%MW\p.2.c\0.0.21:X0-X7 (Modbus Timeout) = x 100 ms,
%MW\p.2.c\0.0.21:X8-X15 (Number of retransmissions) = y,
%MW\p.2.c\0.0.22:X0-X7 (Reconnection time) = z 1 sec, and
%MW\p.2.c\0.0.23:X8-X15 (Effect on FIPIO exchanges) = 0x00 (No action) / 0x02 (Clear).
After sending a request to a slave, if there is no response after (x 100) ms, the gateway will send it again y
times before writing information about the missing slave to the List of Active Slave (LAS), if no other Modbus
Command has succeeded for this slave.
If, despite the y Retries, there is no answer from the slave, the input Data sent to the FIPIO master (Read
requests) is reset to 0 (if 0x02/Clear) or retains its current value (if 0x00/No action), but only for the data
received from the missing slave.
The gateway will try to reconnect the missing slave by communicating with it again every (z 1) ms.
Slave response
If the LUFP1 gateway is disconnected on Modbus side, the behavior depends on the slave.
In the event of a slave failure
No response is sent to the gateway and the state of the slave is undetermined.
Sample Gateway Settings

The example below illustrates a system architecture and Modbus exchanges that differ from those in the
standard configuration described in the rest of this manual.
The example uses the configuration and adjustment parameters described in the previous sections.
120
1743315 03/2009

System Architecture
The Modbus slaves are grouped by category, rather than in order of address, in the list of Modbus slaves on the
UFP1 gateway. The slaves, as seen by the gateway, are as follows:
(1) In the gateway settings, assigning a null address to a slave means that there is no slave at that location.
Not to be confused with the broadcasting of Modbus commands.
1743315 03/2009
121

Modbus Exchanges
The table below lists all the registers read or written periodically by the gateway on the Modbus slaves. It will
subsequently be used to configure the gateways periodic command and control words.
Number of periodic command words = 2 (x2) + 1 (x2) + 3 (x1) = 4 + 2 + 3 = 09

Number of periodic control words
= 3 (x2) + 3 (x2) + 4 (x1) = 6 + 6 + 4 = 16
Total number of periodic words
= 9 + 16 = 25
Reserve: 1 periodic command or control word (maximum of 26 periodic words).
The periodic words are assigned firstly to the periodic command words, and then to the periodic control words.
Each category starts with the first Modbus slave and ends with the last configured slave.
In the present example, this gives us the following configuration of periodic words; a grey background indicates a
periodic word with a fast periodicity (otherwise the periodicity is normal):
122
1743315 03/2009
WARNING
PLANNING OF THE MODBUS EXCHANGES
When you create a new configuration and you want to set up the gateway to handle the Modbus exchanges
for this configuration, it is highly advisable to plot out all such exchanges in advance, as illustrated above.
NOTE: The configuration of the Modbus slaves themselves is beyond the scope of this guide, and is therefore
not described here. See the user manuals of the corresponding products.
1743315 03/2009
123

Configuration Parameter Values
124
1743315 03/2009

Adjustment Parameter Values
1743315 03/2009
125

FIPIO Objects Available for Programming
Only the Modbus slave control words (%IW\p.2.c\0.0 to %IW\p.2.c\0.0.26), the Modbus slave command words
(%QW\p.2.c\0.0 to %QW\p.2.c\0.0.27) and the LUFP1 gateway LAS service (%IW\p.2.c\0.0.27) are discussed
again here, as no other FIPIO objects are modified in the following example.
See Section 5, for a description of all the gateways FIPIO objects.
Inputs %IW\p.2.c\0.0 to %IW\p.2.c\0.0.26 correspond to the gateways 26 periodic control words, plus one
reserved word. As only control words n1 to 16 are used, the only useful inputs are %IW\p.2.c\0.0 to
%IW\p.2.c\0.0.15. Inputs %IW\p.2.c\0.0.16 to %IW\p.2.c\0.0..26 must therefore not be used:
Outputs %QW\p.2.c\0.0 to %QW\p.2.c\0.0.27 correspond to the gateways 26 periodic command words, plus
two reserved words. As only command words n1 to 9 are used, the only useful outputs are %QW\p.2.c\0.0 to
%QW\p.2.c\0.0.8. Outputs %QW\p.2.c\0.0.9 to %QW\p.2.c\0.0.27 must therefore not be used:
NOTE: Only the mapping for the first and last inputs (or outputs) is shown here, as the intervening periodic
words were described in the tables in Modbus Exchanges, Appendix B.
Only the first 5 bits of the input word assigned to the
list of active slaves (LAS) service are actually used. A
Modbus slave is present if the corresponding bit is set
to 1.
See also Section 5.2 for more details on the list of
active slaves service.
126
1743315 03/2009
Appendix C: Standard Configuration

The configuration described below is the standard configuration used when implementing the LUFP1 gateway.
NOTE: This chapter mainly gives the user information about the performances obtained on the downstream
Modbus network. It allows users to decide whether, for example, they should change the timing of periodic
exchanges with one or more of the TeSys U motor starters (see Chapter 7).
Configuring Modbus Exchanges

The LUFP1 gateway carries out two types of exchanges with each of the 8 TeSys U motor starters. These
exchanges are periodic and allow you to control and monitor the motor starter.
As a result, on a network operating at 9,600 bits/s, you will need to considerably increase the cycle time for all or
some of the periodic Modbus commands. On the other hand, at a speed of 19,200 bits/s (the default speed), the
available bandwidth is sufficient to support acceptable communications, even with the occasional degraded
mode (retransmission of frames), and to allow the use of aperiodic parameter exchanges (using the PKW service
described in Section 5.3).
127
1743315 03/2009

Content of the Gateways DPRAM Memory
The LUFP1 gateways DPRAM memory contains all of the data exchanged between the gateway and the 8
TeSys U motor starters.
The flow of data between the TeSys U motor starters, the gateway and the FIPIO master is shown below, in
order to highlight the role of the gateways memory in these exchanges:
Input Data Memory Area

The gateway has 52 input bytes. Only the first 16 bytes are used.
(1) The data for these services are not actually stored in these gateway memory locations, but the mapping
between the gateway memory and the corresponding FIPIO inputs / outputs (see Section 5.1.3) means that
these locations are not to be used. If they were, the mapping would overwrite the stored data with data from
the services.
128
1743315 03/2009

Output Data Memory Area
The gateway has 52 output bytes. Only the first 16 bytes are used.
(1) See note on PKW service (RESPONSE) in the previous table.
Total Number of Modbus Queries and Responses

The total number of Modbus queries and responses is 32 (2 periodic queries and 2 periodic responses for
each of the 8 TeSys U motor starters). Since the total number of Modbus queries and responses one can
configure for a single gateway is limited to 52 (whichever profile is used: FED C32 or FED C32 P), there are 20
spare Modbus queries and responses (i.e. the equivalent of 10 Modbus commands).
This reserve is therefore enough for the addition of any single Modbus command to each of the TeSys U motor
starters, as this requires 16 Modbus queries and responses (1 query and 1 response for each of the 8 motor
starters).
1743315 03/2009
129
Appendix D: Sample Use under PL7 PRO

A practical example can be found on the http:///www.schneider-electric.com website.
The first file, "LUFP1_FEDC32_Example.cfg, is an ABC-LUFP Config Tool file; its content corresponds
to the system architecture described in Section 4.1.1. The gateway must therefore be configured using
under PL7 PRO (see Chapter 6). This ABC-LUFP Config Tool file
profile
corresponds to the standard configuration used in this guide.
The second file, lufp1 exemple du tutorial fedc32p tsx57252.stx , is a PL7 PRO file and provides the
example for a TSX Premium PLC with a TSX 57252 processor where the LUFP1 is configured under
PL7.
The third file, "lufp1_tutorial_en_fedc32p_tsx57353.stx, is a PL7 PRO file and provides the example for a
TSX Premium PLC with a TSX 57353 processor where the LUFP1 is configured under PL7.
The fourth file, "lufp1_tutorial_en_fedc32_tsx57252.stx, is a PL7 PRO file and provides the example for a
TSX Premium PLC with a TSX 57252 processor where the LUFP1 is configured under ABC-LUFP
Config Tool. The configuration LUFP1 - FED C32 - Exemple.cfg needs to be loaded onto the LUFP1.
The fifth file, "lufp1_tutorial_en_fedc32_tsx57353.stx, is a PL7 PRO file and provides the example for a
TSX Premium PLC with a TSX 57353 processor where the LUFP1 is configured under ABC-LUFP
Config Tool. The configuration LUFP1_FEDC32_Example.cfg needs to be loaded onto the LUFP1.
The content and application of these examples is dealt with in the following sections.
The configuration of the first file corresponds exactly to what is described in the previous sections; its content is
therefore not detailed here. However, the PL7 PRO file is described below, in terms of the structure of the
program sections used and the related operating screens.
Overview of the LUFP1_tutorial example
130
1743315 03/2009

This description remains concise, because it is only meant to describe the overall operation of the program and
the way to use the related screen. If you need a greater degree of detail, don't hesitate to review the actual
content of the example under PL7 PRO.
The source code contains numerous remarks to help you understand how it works. Each "program" file starts
with a short description of the way it operates, and each line includes a comment.
Each variable used has a symbol whose name describes its use. Use the keyboard shortcuts Ctrl+E and
Ctrl+F to display the variables by address (e.g. %MW100) or by symbol (e.g. Pkw_checked_boxes_dn).
) have been created, FIPIO Diagnostics, "lufp1_inputs_outputs" and
Three animation tables (icon
lufp1_Pkw.
However, the operating screens provided are more than sufficient to present the application data used
throughout thisexample.
Displaying LUFP1 Gateway Inputs / Outputs

The LUFP1 gateway exchanges operating screen comprises two separate panes:
Hexadecimal display of gateway input data (%IW\0.2.2\0.0 to %IW\0.2.2\0.0.31) in the INPUTS frame.
These inputs are named and grouped in the same way as in this guide (see Section 4.2.7). Of course, the
display of these input data is correct only if the standard gateway configuration is used.
In the case of the standard configuration, these input data comprise the periodic Modbus data (command
and control of TeSys U motor starters), the Modbus aperiodic data (indexed periodic variables / PKW
service) and the input word of the list of active slaves (LAS) service, as well as the free and reserved
memory locations.
Hexadecimal display of gateway output data (%QW\0.2.2\0.0 to %QW\0.2.2\0.0.31) in the OUTPUTS

frame. As above.
Command and Control of the 8 TeSys U Motor Starters

The Command Control operating screen (see illustration on next page) allows you to monitor the status of
the 8 TeSys U motor starters, numbered from 1 to 8. It also enables you to command them individually by means
of a number of buttons.
Registers 455 and 704 on each of the 8 TeSys U motor starters are used to conduct this control and command
function:
1743315 03/2009
131

These statuses and commands are grouped into two sections: General
Status, for the general operating mode of the motor starters, and
"Motor" for that of the controlled motors. The last section, DEBUG
COMM., displays the two registers %IW and %QW used for each motor
starter.
This screen is shown opposite, but only for the first motor starter, as it is
identical to the 7 others.
Most of the displays in this operating screen are directly linked to the
%MW registers, which in turn contain the values of registers %IW4.0.1
to %IW4.0.8 and %QW4.0.1 to %QW4.0.8 (status and command
registers of the TeSys U motor starters). Only the indirect commands
and statuses are described below.
The Cmd_mon program performs the following tasks:
It copies the values of words %MW20 to %MW27 into output

registers %QW\0.2.2\0.0 to %QW\0.2.2\0.0.7 and copies the values
of input registers %IW\0.2.2\0.0 to %IW\0.2.2\0.0.7 into words
%MW10 to %MW17.
These data are copied because word bit extraction can be
carriedout on %MW-indexed words, but not on %IW-indexed
words. The sub-program Sr0 makes extensive use of word
indexing, as it can be used to manage any motor starter, the latter
being designated by the word %MW0. E.g. %MW10[%MW0]:X13
is authorized, but not %IW\0.2.2\0.0 [%MW0]:X13.
Furthermore, the input and output words are copied one by one, as PL7 PRO does not support expressions such
as %IW\0.2.2\0.0:8.
It runs the Sr0 sub-program calling loop to command and control the 8 TeSys U motor starters. At each
iteration of the loop, the word %MW0 (Module) takes a value from 0 to 7 in order to serve as an index for
words %MW10 to %MW17 (inputs) and %MW20 to %MW27 (outputs).
The Sr0 sub-program is called once per motor starter from the Cmd_mon program. Each of these calls
should be made with a different value in the word %MW0 (between 0 and 7) as it is used to index the status
word and the command word of the same motor starter. The sub-program is used by the screen shown above to
perform the following tasks:
132
1743315 03/2009
Evaluating the value of the motor current, given as a percentage of the IR current value (unit = % FLA).
Bits 8 (LSB) to 13 (MSB) of the motor starter status word are extracted and the appropriate unit, i.e.
3.125% FLA, is then used to evaluate the current. The maximum value is therefore 63, or
196.875% FLA.
buttons exclusively to enable only one of the three following

Using the
commands at a time, while resetting the other two to zero, in descending order of priority: stop (bit 2 of
the command word), run forward (bit 0), and run reverse (bit 1).
Using the Indexed Periodic Variables (PKW) Service

The PKW service operation screen allows the user to command the reading or the writing of a register on a
Modbus slave, on the gateway, or on all the Modbus slaves at once (broadcast). The screen is divided up into a
number of frames, as illustrated below:
The first frame, DN (Device Number), is used
to select the station to be polled by the PKW
service. Only one box can be checked at any
given time. Depending on the box selected
when the SEND command button is clicked,
the DN field (MSB of %QW\0.2.2\0.0.29) of the
PKW service command will be updated
accordingly (see Section 5.3.2). The Other
address: box allows the user to type in an
address ranging from 1 to 247.
The second frame, PKE (Address Register), allows you to set the address of the register to be read /
written. When the SEND command button is clicked, the value currently entered in this frame is copied
into the PKE field (%QW\0.2.2\0.0.28) of the PKW service command.
The third frame, PWE (Value to be written), will only be used for write commands on registers. When
the SEND command button is clicked, the write command is copied into the first word
(%Q\0.2.2\0.0.30) in the PWE field of the PKW service command, providing the Write a register box is
checked.
The fourth frame, R/W (Read / Write), allows you to select the type of command generated by the PKW
service: Read, Write or Reset the response. Only one box can be checked at any given time.
The SEND command button triggers the update of the gateways periodic output data
(%QW\0.2.2\0.0.28 to %QW\0.2.2\0.0.31) so that the gateway generates a command that matches the
settings and values in the frames above. These updates are performed in the Pkw_service program.
Of course, using periodic data means that a new command can only be generated when one of the
values involved changes from one command to the next. This is why the Reset command is useful, for
example, so that the same command can be repeated several times.
E.g. In the above example, the frames are configured to issue a read command (0x52) on the register located at
address 455 (0x01C7) of TeSys U motor starter n3 (0x03).
1743315 03/2009
133
The last frame, beneath and apart from the others, displays the output data transmitted to the gateway in
order to generate the corresponding PKW command, and the input data from the gateways response to
this command.
The following example contains the PKW service output and input data for the instances described at
the bottom of the previous page. The reading value is 0x01C3.
The Pkw_service program includes the ST instructions that use the values entered in the PKW service
frame, described on the previous page, to update the PLC outputs for the PKW service command on the
gateway (%QW\p.2.c\0.0.28 to %QW\p.2.c\0.0.31). The program handles the following tasks:
It tests the checkboxes in the DN (Device Number) and R/W (Read / Write) frames. If, in either frame,
none of the boxes is checked, one of them will be selected by default (DN = 1st Modbus slave; R/W =
Read a register).
It compares the values over two consecutive PLC cycles in order to keep only one box checked at any
given time in each frame.
When it detects a click on the SEND command button, it updates the local variables, followed by the
outputs corresponding to the gateways PKW service. The purpose of this two-stage update procedure is
to isolate the use of the outputs from the rest of the program.
LUFP1 Gateway Diagnostics

The FIPIO Diagnostics operating screen provides a graphic example of the use of the list of active slaves
(LAS) service, specific to the gateway, and of the FIPIO diagnostic objects that a TSX Premium PLC assigns to
the stations on its FIPIO network. See the PL7 PRO user manual or online help for more details about using
FIPIO diagnostics on Premium PLCs.
The screen is divided up into three separate frames, as illustrated below:
List of active Modbus slaves: Each TeSys U n in this frame indicates that the corresponding TeSys
U motor starter is present. The hexadecimal value in the top right corner is that of the FIPIO input for the
list of active slaves (LAS) service, namely %IW\p.2.c\0.0.27. See Section 5.2 for a detailed description of
the LAS service.
In this example, bits 2 and 4 of
the LAS service input word have
been reset by the gateway.
Modbus slaves n3 and 5 are
therefore absent.
The LUFP1 box uses a system bit on the Premium PLC to indicate whether the gateway is present on,
or absent from, the FIPIO network (colored blue or red accordingly). This system bit (%SW128:X2 in this
example) is described in Section 5.4.1.
134
1743315 03/2009
Diagnostics: Implicit exchanges: The

first two rows of the table in this frame
correspond to the Module fault
(%I\p.2.c\0.MOD.ERR) and Channel
fault (%I\p.2.c\0.0.ERR) described at the
beginning of Section 5.4. The last two
rows
correspond
to
the
words
%MW\p.2.c\0.0 and %MW\p.2.c\0.0.1,
both described in Section 5.5.
If the FIPIO connection between the PLC
and the gateway is lost, the first two rows
signal the presence of just such a fault
(see example).
If these faults arise, the Explicit exchanges, refreshed every 5 seconds (see below), indicate the presence of
an Internal fault (Standard channel status) and Gateway absent (Module status). A sample screen is shown
below.
Diagnostics: Explicit exchanges: Both rows of the table in this frame are refreshed every 5 seconds.
They indicate the nature of any errors detected either by the gateway or by the FIPIO master.
See Sections 5.4.2 and 5.4.3 for a
description of the explicit objects
introduced here.
The example opposite illustrates one
type of error (gateway out of supply).
The Diagnostics program includes all the ST instructions for generating the explicit FIPIO diagnostic
commands. The program handles the following tasks:
A timeout (%TM4) is used to generate two explicit diagnostic commands every 5 seconds. One of these
commands reads the Module status and the other reads the Standard channel status.
A second timeout (%TM5) is used to prolong the Read status in progress alert (%MW\p.2.c\0.0:X0) by
500 ms, so that it can be seen in the Exchange management status line of the FIPIO Diagnostics
screen. This indicates the activity triggered by the two explicit diagnostic commands (see previous
point).
1743315 03/2009
135
Appendix E: Modbus Commands

Only the Modbus commands shown in
the table opposite are supported by the
gateway. The structure of the query and
response frames for each of these
commands is described in the rest of
this chapter.
(1) The content of this column shows whether the command can be added (Yes) or not () to the list of
commands for a broadcaster node, known as Broadcaster in ABC-LUFP Config Tool.
In the following sections, each byte in the query and
response frames of a Modbus command is described,
in sequence, with the exception of the fields opposite:
these are always present in the queries and
responses of Modbus commands.
The first two bytes of these frames correspond to the
Slave Address and Function fields. The last two
bytes are the two Checksum bytes.
The following descriptions of the Modbus frames are mainly intended to help you to configure the gateways
Modbus exchanges using ABC-LUFP Config Tool. See the documentation of each Modbus slave to check for
any restrictions on the use of these frames (number of registers which can be read or written in a single Modbus
command, for example).
It is preferable to get hold of a standard Modbus document, such as the Modicon Modbus Protocol Reference
Guide (ref. PI-MBUS-300 Rev. J), to see how the elements displayed in ABC-LUFP Config Tool map match the
content of the corresponding Modbus frames. Here is a mapping example for a complete frame (including the
start and end of frame fields shown above), based on the Read Holding Registers Command (0x03) section.
Section 7.12 also shows a few examples of mapping between the elements displayed in ABC-LUFP Config Tool
and the corresponding Modbus frame fields.
136
1743315 03/2009

NOTE: Here, the notions of input and output (and assimilated concepts) are meaningless, in as far all
Modbus commands have access to the entire memory of the Modbus slave. We continue to use these terms,
however, in order to conform to the terminology of the standard Modbus documentation.
Read Holding Registers Command (0x03)
Preset Single Register Command (0x06)
NOTE: Instead of placing the echo of the response to the Preset Single Register Command (0x06) in the
addresses reserved for FIPIO inputs (0x0000-0x0033), you can put it at 0x0400. This is what the gateway does
automatically when you configure periodic command words.
Preset Multiple Registers Command (0x10)
1743315 03/2009
137

Modbus Protocol Exception Responses
When it cannot process a command issued by a Modbus query, a slave sends an exception response instead of
the normal response to the query.
WARNING
UNATTENDED OPERATION OF THE SYSTEM
With standard Modbus commands, the LUFP1 gateway considers that all the exception responses it receives
from Modbus slaves are incorrect responses. As a result, it will carry out the re-transmissions configured for
the queries involved.
The structure of an exception response is independent of the Modbus command associated with the Function
field of the query involved. The complete frame of an exception response is shown below:
(1) See the standard Modbus documentation for further information about these various scenarios.
138
1743315 03/2009
Index
Line termination, 21
LU9GC03 hub, 19
2-way TSXSCA62 subscriber connector, 19

A
M
Modbus cable, 19
Address, 23
Architecture, 9, 28
P
C
Cable
type A, 20, 22
Communications
aperiodic, 44
periodic, 44
Cycle time, 29
PL7 PRO, 34, 39, 40, 42, 68, 77, 121

Product Related Warning, 5
Profibus-DP master, 34
Protective Earth, 13
R
Related documents, 5
RJ45 connector, 12
S
SyCon, 28, 34, 35, 37, 73, 76, 116, 121
Data exchanged, 11
Diagnostic LEDs, 12
DIN Rail, 13
T
E
End of line connector, 22

G
Gateways address, 23
GSD file, 36
SCA junction boxes, 17

Topology
bus, 16
TSXCA50 SCA junction box, 19
Type A cable, 20
V
VW3 A8 306 RC double termination, 19

VW3 A8 306 TF3 T-junction box, 19
LEDs, 25
Line connector, 22
139
1743315 03/2009
Glossary
0x
Value expressed in hexadecimal, which is equivalent to the H, h and 16# notations,

sometimes used in other documents.
NOTE: The ABC-LUFP Config Tool software uses the 0x notation.
e.g. 0x0100 = 16#0100 = 256.
2#
Value expressed in binary. The number of digits depends on the size of the item of data
represented. Each nibble (group of 4 bits) is separated from the other nibbles by a space.
Examples: byte 2#0010 0111 = 39, word 2#0110 1001 1101 0001 = 0x69D1 = 27089.
ABC-LUFP
Config Tool
Name of the PC software used to configure and monitor the LUFP7 Profibus-DP/Modbus
Gateway.
ASIC
Integrated circuits specific to a given user and application, covering two major families: precharacterised processes and pre-distributed networks.
ATS
Abbreviation of Altistart (soft start- soft stop unit).
ATV
Abbreviation of Altivar (drive).
CRC
Cyclical Redundancy Check.
LED
Light-Emitting Diode.
DP
Decentralised Periphery (remote I/O). Profibus version or protocol meant for quick
communication with remote I/O. This is the only Profibus protocol supported by the LUFP7
gateway.
DPM1
Class 1 DP master: the central automatic control of a Profibus-DP network. It resets and
controls I/O transfers and slave diagnostics on the network. One can have several DPM1
stations on a given Profibus-DP network, each one steering its own slaves.
DPM2
Class 2 DP master: The programming, configuration, and diagnostic device of a Profibus-DP

network.
Fieldbus
A term referring to the upstream Profibus-DP network in ABC-LUFP Config Tool.
FMS
Profibus-FMS messaging system that defines the objects and application services applicable to
these objects. By extension, the Profibus version or protocol dedicated to complex and advanced
communication tasks at the cell level. This protocol is not supported by the LUFP7 gateway.
GSD
Electronic equipment database, also called GSD file. This term designates the format of the
files (.gsd extension) that are used by a Profibus master configuration and adjustment tool to
configure their exchanges according to that same protocol.
Handshake
LRC
An old term referring to the two registers used for initialising and carrying out diagnostics of the
LUFP7 gateway. This term has been replaced by the expression Control/Status Byte.
Longitudinal Redundancy Check.
LSB
Least significant byte in a 16-bit word.
140
1743315 03/2009
Glossary
MSB
Most significant byte in a 16-bit word.
Node
A term referring to the connection point of a Modbus slave under ABC-LUFP Config Tool.
PA
Profibus version or protocol dedicated to process automation. This protocol is not supported by
the LUFP7 gateway.
PDP
Profibus-DP (see DP above).
PI
Profibus International. This term designates the international organization for users of the
Profibus protocol. It is responsible for federating Profibus skills centres, scattered throughout
the 20 largest industrial countries. The list of user groups of the Profibus protocol is available
on the Profibus web site, at http://www.profibus.com/. To get general-purpose support on
Profibus, please email to PI, at: [email protected].
PNO
This term designates the national and local associations of Profibus protocol users.
PPO
Parameter Process data Object. This term designates the type and size of the data exchanged
between a Profibus master and slave. In the case of the LUFP7 gateway, PPOs are not used
to configure its exchanges on the Profibus network.
Profibus
PROcess Field BUS.
PSU
Power supply.
Sub-Network
A term referring to the downstream Modbus network under ABC-LUFP Config Tool.
TSDI
Initiating station request time.
TSDR
Answering station response time.
XML
EXtensible Markup Language. The language used by ABC-LUFP Config Tool to import/export
the configuration of a Modbus slave.
141

LUFP1 v1, Fipio-Modbus RTU Gateway PDF

Uploaded by

Copyright:

Available Formats

LUFP1 v1, Fipio-Modbus RTU Gateway PDF

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

LUFP1 v1, Fipio-Modbus RTU Gateway PDF

Uploaded by

Copyright:

Available Formats

TeSys U LUFP1

FIPIO / Modbus RTU Gateway

Safety Information .....................................................4

2. Hardware Implementation of the LUFP1

5.4.2. Channel Status (%MW\p.2.c\0.0.2) ............................... 59

6. Advanced Implementation of the Gateway ...... 62

7. Using ABC-LUFP Config Tool ........................... 67

Appendix A:........................................................... 108

Appendix B:........................................................... 114

4. Software Implementation of the Gateway........ 26

Appendix C ............................................................ 127

Appendix D ............................................................ 130

5. FIPIO Objects Available for Programming....... 44

Electrical equipment should be installed, operated, serviced and maintained only by

About the book

This document applies to all V2 gateways.

AnyBus Communicator User Manual

(2) TeSys U Products

(2c) new variables

Managing Loss of Communication

(5) Signaling and Diagnostics

(1) Presentation of Hardware and Connections

(3) User of other Generic Modbus Products

(2) User of TeSys U Products (LUFP1 as a FED C32 P device)

See Chapter 4 and 5

(2b) reducing the number of slaves

with a supplementary request:

The variables described are:

(5) Signaling of faults and status, Diagnostics

Using ABC-LUFP Config Tool to access

See Chapter 4.1.4

Using ABC-LUFP Config Tool:

(2c) access to new variables

(4) Loss of Communication

See Chapter 5.4

See Chapter 7.5

Signaling defaults and gateway status

See 7 Using ABC-LUFP

if you would like to read about the technical communication

Retrieving or updating the parameters on some or all of the Modbus slaves;

1.5. Principle of LUFP1 Gateway Configuration and Operation

Managing Gateway Modbus slaves exchanges (FED C32 P)

2. Hardware Implementation of the LUFP1 Gateway

2.2. Introduction to the LUFP7 Gateway

Detachable power connector for the

Female RJ45 connector to a PC

Female RJ45 connector for the

Six diagnostic LEDs.

Removable cover for the coding

Female FIPIO connector.

2. Hardware Implementation of the LUFP1 Gateway

2.3. Mounting the Gateway on a DIN Rail

Removing the gateway

Start by fitting the rear base of the gateway to the

Start by pushing the gateway downwards (1) to

2. Hardware Implementation of the LUFP1 Gateway

Use 60/75 or 75xC copper (CU) wire only.

2.5. Connecting the Gateway to the Modbus Network

2. Hardware Implementation of the LUFP1 Gateway