MAN - Cable Laying Practices - 2

___________________________________________________________________________
X-WAY General
___________________________________________________________________________
UNI-TE Protocol, request coding
___________________________________________________________________________
Safety, ground connections
___________________________________________________________________________
Character string communication
___________________________________________________________________________
A
Contents
Part A
Section
1
Page
Introduction
1/1
1.1
Network documentation presentation

1.1-1 Introduction to the various manuals
1.1-2 Using the network documentation
1/1
1/1
1/1
1.2
Types of architecture
1.2-1 General
1.2-2 Single network architecture
1.2-3 Multi-network architecture
1.2-4 Concentrator
1.2-5 Redundancy
1.2-6 Bridge
1/3
1/3
1/4
1/6
1/8
1/9
1/10
1.3
The OSI model as defined by the ISO standard

1.3-1 Introducing the model
1.3-2 Physical layer
1.3-3 Data link layer
1.3-4 Network layer
1.3-5 Transport layer
1.3-6 Session layer
1.3-7 Presentation layer
1.3-8 Application layer
1/11
1/11
1/12
1/12
1/13
1/13
1/13
1/14
1/14
1.4
Positioning of the various networks in the OSI model

1.4-1 X-WAY and OSI model
1.4-2 UNI-TELWAY
1.4-3 FIPWAY
1.4-4 FIPIO
1.4-5 ETHWAY
1/15
1/15
1/16
1/17
1/18
1/19
___________________________________________________________________________
A/1
A
Contents
Part A
Section
2
Page
Services
2/1
2.1
Introduction to the services
2/1
2.2
UNI-TE service
2.2-1 Presentation
2.2-2 CLIENT-SERVER concept
2.2-3 List of requests
2/2
2/2
2/2
2/3
2.3
Common word service : COM service
2/5
2.4
Shared table service
2/7
2.5
Application-to-application communication
2.5-1 Standard
2.5-2 Priority exchanges
2/9
2/9
2/10
2.6
Remote Input / Output services
2/11
___________________________________________________________________________
A/2
A
Contents
Part A
Section
3
Page
X-WAY addressing mechanisms
3/1
3.1
General
3/1
3.2
Communication entities
3.2-1 Presentation
3.2-2 Station level entities
3.2-3 Module level entities
3.2-4 Communication channel level entities
3/3
3/3
3/3
3/3
3/3
3.3
Address format
3.3-1 Principles
3.3-2 Network number-station number
3.3-3 Broadcast address
3/4
3/4
3/4
3/4
3.4
Introduction to hierarchical addressing
3/5
3.5
Three level addressing

3.5-1 Presentation
3.5-2 Example
3/6
3/6
3/7
3.6
Five level addressing

3.6-1 Presentation
3.6.2 Example
3/8
3/8
3/10
3.7
Six level addressing

3.7-1 Presentation
3.7-2 Example
3/11
3/11
3/13
___________________________________________________________________________
A/3
A
Contents
Part A
Section
4
Page
Appendix
4/1
4.1
4/1
4/1
4/2
4/3
4/4
4/5
4/6
4/7
4/8
X-WAY frame format

4.1-1 Presentation
4.1-2 X-WAY frame
4.1-3 NPDU type
4.1-4 Addresses
4.1-5 Five level addressing
4.1-6 Six level addressing
4.1-7 Data (message handling system)
4.1-8 Distributed data
___________________________________________________________________________
A/4
Section 11
Introduction
1 Introduction
1.1
Network documentation presentation
1.1-1 Introduction to the various manuals

This manual is designed for users wanting an insight into X-WAY communication. It aims
to give an overall view of the various X-WAY networks and protocols without dealing with
specific hardware features (communication modules) and software features
(programming languages).
General information on hardware is given in the basic manual : TSX DM 37NE.
General information on the software setup of the various networks is given in the
manual : TLX DM PL7ME.
Information appropriate to each network is described in the dedicated User's Manuals :
FIPWAY network
: TSX DG FPWE,
FIPIO fieldbus
: TSX DG FIOE,
UNI-TELWAY bus
: TSX DG UTWE,
MODBUS/JBUS protocol : TSX DG MDBE,

ETHWAY network
: TSX DG ETWE.
Note :
Each module is supplied with a manual concerning its hardware setup in the PLC.
1.1-2 Using the network documentation

The following example illustrates this section :
A user wishes to install an inter-PLC communication with very precise requirements
(response time, services, size of exchange, etc). He has :
this manual for defining the type of network which meets his requirements :
Communication Reference Manual : TSX DR NETE,
the specific manual for the selected network in order to physically install it
(eg : FIPWAY) :
FIPWAY Installation Manual : TSX DG FPWE,
the basic "hardware" manual for selecting the appropriate communication modules :
Basic manual : TSX DM 37NE,
the basic "software" manual for setting up the exchanges with the selected protocol :
Basic manual : TSX DM PL7ME,
___________________________________________________________________________
1/1
A
The module is installed in the PLC by following the manual supplied with the module.
General
AEG
TSX DR NET
FIPWAY
UNI-TELWAY
AEG
AEG
TSX DG FPW
TSX DG UTW
AEG
TSX DM 37N
MODBUS/JBUS
AEG
TSX DG MDB
AEG
TLX DM PL7M
HARDWARE SOFTWARE
Each manual corresponds to a very precise kind of use and refers to the relevant manual
for any other use (eg : separation of the hardware and software integration).
___________________________________________________________________________
1/2
Introduction
1.2
Types of architecture
1.2-1 General
X-WAY networks can be perfectly integrated into the model of an integrated plant (CIM*
concept) which defines the various levels of communication :
management-design level :
orientated towards production management, this level requires the installation of
networks which can handle a large amount of traffic with no restrictions on response
time. Local area networks adapted for this level are usually based on an Ethernet
architecture,
factory floor level :
factory floors, which are made up of cells, exchange data and can therefore monitor
production. At this level the data rate of the network must be high enough to exchange
large quantities of data,
(eg : ETHWAY network, MMS/Ethernet),
cell level :
all devices connected to the cell share, via the network, data controlled by an overall
control system (eg : program, parameters, control messages, etc),
(eg : FIPWAY network),
machine or field level :
intelligent sensors and actuators and simple control systems communicate at this
level, with the aspect of real-time having priority,
(eg : FIPIO fieldbus).
Several networks operating on different levels, and on sites which may reach a
considerable size, can only work together and provide total communication if the
networks are connected together. Two network architectures will be described :
simple architecture (single network) where a single network links all the stations,
hierarchical architecture (multi-network) where a number of networks are connected
together by common PLCs (network nodes). There are two types of network node :
- bridge type where the PLC routes messages from one network to another,
- multi-network station type where the node PLC collects and exchanges data
separately with each network, but does not provide user-transparent data routing
from one network to another.
Examples of network architectures illustrating the various possibilities are described in
this section.
* CIM : Computed Integrated Manufacturing
___________________________________________________________________________
1/3
A
1.2-2 Single network architecture
The example below shows a small scale application typical of a manufacturing process.
The production cell comprises :
a conveyor system (TSX 37),
a pallet control station,
a machining center (NUM 1060),
a control and supervision station (CCX 77),
a PC compatible microcomputer,
an FTX 507 programming terminal.
FTX 507
CCX 77
ETHWAY
Pallet
handling
Conveyor
TSX 37
Machining
TSX 37
NUM 1060
IBM PC
UNI-TELWAY
TBX
XGS
FIPIO
CCX17
ATV 16
Machine tool
___________________________________________________________________________
1/4
Introduction
This application ensures close coordination between the various controllers, reducing
manufacturing time and eliminating stoppages. Production quality is ensured by
monitoring product and tool condition.
The control station sends commands (Start/Stop) to the controllers and downloads the
production programs and data. The control station provides :
man-machine interface function using real-time animated synoptics,
feedback of alarms,
storage of all event data, simplifying diagnostics and providing system operation
statistics.
___________________________________________________________________________
1/5
A
1.2-3 Multi-network architecture
In this example, the factory comprises a number of separate workshops, technical
departments, sales and management departments, etc.
CAD
CAM
Sales
Scheduling
OSI/MMS
TSX 7
TSX 7
FIPWAY
CCX77
FIPWAY
IBM PC
Large quantities of data are exchanged between the various functions. Two different
types of network are installed to separate the data flows and improve installation
performance and safety :
a computer network which links the various computer systems,
a number of networks which feed back production data to the management levels and
vice-versa, which control a PLC or a numerical controller from a terminal located away
from the factory floor (eg. in the design office).
___________________________________________________________________________
1/6
Introduction
The factory floor is divided into a number of separate production lines which are relatively
independent and therefore need only exchange limited amounts of data.
A CCX 77 supervisor directly connected to each factory floor network is used for local
production monitoring.
The various factory floor networks are connected in clusters to the local area network
via bridge PLCs.
This network also has computers connected to it which provide the link with the
factorywide computer network. The FTX 507 terminal is also connected at this level and
supports the same functions as those described in section 1.2-2 (single network
architecture).
This architecture primarily enables :
separation of the various data flows so that individual networks are not needlessly
overloaded,
intervention on one network, if required, without affecting normal operation in the rest
of the facility.
The user-transparency of the multiple network architecture enables any device to
address any other device on the network.
___________________________________________________________________________
1/7
A
1.2-4 Concentrator
The concentrator is a connection system which connects a number of terminals to the
network.
The concentrator can have an active role on the network as soon as it can manage the
links and can perform certain operations connected with the conversion of data which
passes through filtering and control.
It can have "buffer" functions, that is it can store data while waiting for a channel to
become available.
A PLC can function as a concentrator and provide multi-network architectures as
described in the example below.
In this example, the factory comprises two identical production lines. Their length and
the number of devices to be connected preclude the use of a single network.
Station 1
Station 2
Station 3
Station 4
Station 1
Station 2
Station 3
Station 4
The processes do not require exchanges between networks. Only supervision data
needs to be fed back to the higher management level. In this case, the PLC only performs
the function of data concentrator for information from the two networks.
This split architecture enables intervention on one production line without affecting
production on the other line, while releasing the network node PLC from the workload
caused by the bridge function, which is no longer necessary.
___________________________________________________________________________
1/8
Introduction
1.2-5 Redundancy
Where a network architecture is designed to ensure reliable and safe operation,
redundancy generally involves the use of a multi-network architecture; an example of
a basic ETHWAY architecture is shown below.
The ETHWAY network architecture does not provide any redundancy in the event of a
serious problem on the network. It is possible however to ensure a high level of safety
via the application program as shown below :
Network N2
Network N1
All stations are connected to two separate ETHWAY networks, networks N1 and N2, via
two TSX ETH 107 interface modules.
Each station will therefore have two network-station addresses : N1S1 on ETHWAY
network N1 and N2S2 on ETHWAY network N2.
The application program of each PLC periodically checks its ability to access all stations
via network N1.
If all stations can be accessed, the messages destined for other stations will be sent with
the N1S1 address of the target station.
If a problem is encountered, the PLCs will switch to the second network by replacing the
N1S1 target address of the station with its N2S2 address.
___________________________________________________________________________
1/9
A
1.2-6 Bridge
The bridge allows two different functions on a corporate network : division of the local
area network in two to improve performance levels, and connection of two local or
remote networks with the same topology to authorize exchanges and the sharing of
data.
The bridge provides a multi-network architecture as described in section 1.2-3 and
shown below :
CAD
CAM
Sales
Scheduling
ETHERNET/DECNET
Bridge
ETHWAY
TSX 7
TSX 7
FIPWAY
CCX77
FIPWAY
IBM PC
Cell 1
Cell 2
Cell n
Comment
The bridge operates to level 2 of the ISO layer (see section 1.3) and therefore does
not perform any protocol conversion. In this example, this connection is possible
since the ETHWAY layers 1 and 2 are identical to those of Ethernet/Decnet.
___________________________________________________________________________
1/10
Introduction
1.3
The OSI model as defined by the ISO standard
1.3-1 Introducing the model

Compatibility between different types of device can only be ensured by following the
definition of connection standards which describe the behavior of each device with
regard to others. These standards have been designed by the ISO (International
Standards Organization) which has defined a standard Network Architecture better
known as the OSI MODEL (Open Systems Interconnection).
This model consists of seven hierarchical layers, each fulfilling the defined function as
required for the connection of systems to one another.
Layers from one device communicate with equivalent layers of other devices via
standard protocols. Within the device, layers communicate with those next to them via
hardware or software interfaces.
STATION 1
7
Application
Presentation
Session
Transport
Network
Data link
Physical
STATION 2
Layers designed for

data processing
Layers designed for

communication
Physical connection medium
___________________________________________________________________________
1/11
A
1.3-2 Physical layer
This handles the transparent transmission of binary elements between two systems by
means of a communication medium.
It provides the mechanical, electrical and functional means as well as the necessary
procedures to operate, maintain and deactivate the physical transmission connections.
Example : This layer defines transmission procedures (half and full duplex), the type of
link (parallel or serial), data coding, the operation of electrical interfaces, etc.
1.3-3 Data link layer

This handles data transfers between two adjacent systems and incorporates error
detection.
It must ensure a reliable transfer, by detecting and correcting transmission errors and
ordering the data.
It monitors and regulates the data flow on the link.
This layer is divided into two sub-layers : the LLC sub-layer (logical link control) and the
MAC sub-layer (medium access control).
L.L.C.
Data link
M.A.C.
Physical
Physical
Data link
layer
MAC sub-layer :
shares the transmission channel between the various stations.

Access to the network is therefore managed at this level (eg :
CSMA/CD, use of tokens, etc).
LLC sub-layer :
manages the control and flow of data.
___________________________________________________________________________
1/12
Introduction
1.3-4 Network layer

This handles data routing and selects a path between two devices located on different
networks.
The network layer controls the general operation of the transmission. It is this layer which
checks the path used by a data packet. Depending on the complexity of the network,
several routes can be used for packets to pass from the transmitter to the receiver. The
network layer defines the best route to optimize the transfer. It also controls the flow to
avoid congestion on the network.
It is completely independent from the topological structure of the network.
1.3-5 Transport layer

This handles data transfers between two systems, reliably and transparently.
It also controls the service quality. It is said that it provides the entire transport between
two remote stations.
The transport layer optimizes the use of available network services to provide in an
economical way the performance levels required by each session unit.
1.3-6 Session layer

This layer organizes and synchronizes dialog between two application processes, and
is responsible for organizing their data.
The session function can temporarily cut the communication, interrupt and resume a
task (activity) which can be executed in several stages; the session layer manages this
dialog by assigning restart or transmission rights.
___________________________________________________________________________
1/13
A
1.3-7 Presentation layer
This handles the representation of data passing between application processes. The
Presentation layer actually exchanges structured data by providing them with a common
presentation. It only deals with the syntax (grammar) and not the semantics (meaning)
of the representation, which is processed at level 7 (Application layer).
Note :
The data may be coded in different ways depending on the host system. In order to cover these
differences, the ISO has defined a common standard language : ASN (abstract syntax notation).
The Presentation layer also has functions for coding or decoding data which has been
compressed due to cost reasons.
1.3-8 Application layer

The Application layer is a high level service, which provides the means of accessing the
communication system, and acts as a window between the processes which work
together on the different systems. As these systems and applications may vary
considerably, it is impossible to define a single service.
A group of specific services is defined for a family of applications (eg : file transfer :
FTAM; industrial message handling service : MMS, etc).
The Application layer provides the user interface with the lower levels.
___________________________________________________________________________
1/14
Introduction
1.4
Positioning of the various networks in the OSI model
1.4-1 X-WAY and OSI model

The X-WAY architecture which is common to all PLCs in the TSX series 7 range, is
integrated in the OSI model as shown below :
UNI-TE
7
Application
COM
Shared
table
Presentation
Session
Transfer
Network
Data link
Physical
Remote
I/O
X-WAY addressing
Master/Slave
RS 485
(RS 232 20 mA CL)
UNI-TELWAY
ISO 8802.2/3
Ethernet
FIP
WORLDFIP
FIP
WORLDFIP
ISO 8802.3
10 Mbits/s
FIP/WORLDFIP
FIP/WORLDFIP
1 Mbits/s
1 Mbits/s
ETHWAY
FIPWAY
FIPIO
Whichever network is used, the application interface remains identical and the
UNI-TE services are always available.
___________________________________________________________________________
1/15
A
1.4-2 UNI-TELWAY
UNI-TELWAY is fully integrated into the TSX Series 7 communication architecture. This
architecture corresponds to the OSI model with an application layer (UNI-TE) and a
network layer (addressing system) which are common to various communication
interfaces : PLC programming port and UNI-TELWAY industrial bus.
The presentation, session and transport layers (6, 5 and 4) are not supported.
The OSI model has an application layer (UNI-TE) and a network layer (addressing
system) that are common to various communication interfaces : programming port
UNI-TE message handling system

Read/Write variables
Operating mode
7
Application
Diagnostics
Program up/download
Standard
Presentation
Session
Transport
Network
X-WAY addressing
Data link
Access to the network : Master/Slave
Physical
RS 485 1200 b/s to 19200 b/s
Notes :
The technical characteristics of the different layers are described in detail in the UNI-TELWAY
manual ref. : TSX DG UTW.
UNI-TELWAY also supports the RS 232 link, as well as the 20 mA current loop on the physical
layer.
___________________________________________________________________________
1/16
Introduction
1.4-3 FIPWAY
FIPWAY is a low-cost cell network which conforms to the FIP standard. It is integrated
in the X-WAY communication architecture.
The presentation, session and transport layers (6, 5 and 4) are not supported, as they
are not required by the targeted applications.
Exchange of cyclic data
- Read/Write variables
- Operating mode
- Diagnostics
- Program up/download
- COM word
- Shared table
Application
Application-to-application
communication
- Standard
- Priority
Presentation
Session
Transport
Network
X-WAY addressing
Data link
FIP/WORLDFIP
Producer/Consumer type exchange
Physical
FIP/WORLDFIP
Shielded twisted pair 1 Mb/s
Note :
The technical characteristics of the different layers are described in detail in the FIPWAY manual
ref. : TSX DG FPW.
___________________________________________________________________________
1/17
A
1.4-4 FIPIO
FIPIO is the fieldbus for TSX Series 7 and APRIL Series 1000 PLCs. It conforms to the
FIP standard and is integrated in the X-WAY communication architecture.
The presentation, session and transport layers (6, 5 and 4) are not supported, as they
are not required by the targeted applications.
Exchange of cyclic data
- Operating mode
- Diagnostics
- Program
up/download
- Exchange of
I/O data
Application
Presentation
Session
Transport
Network
X-WAY addressing
Data link
FIP/WORLDFIP
Producer/Consumer type exchange
Physical
FIP/WORLDFIP
Shielded twisted pair 1 Mb/s
___________________________________________________________________________
1/18
Introduction
1.4-5 ETHWAY
ETHWAY is the X-WAY communication profile for Ethernet.
It meets Ethernet ISO 8802.3 standards and ETHWAY devices can be connected to any
existing installation and work with third-party devices which comply with this standard.
Application
Distributed database
- Operating mode
- Diagnostics
- Program
up/download
- COM word
communication
- Standard
- Priority
Presentation
Session
Transport
Network
Data link
Physical
X-WAY addressing
LLC ISO 8802.2
MAC ISO 8802.3
CCMA-CD
ISO 8802.3
___________________________________________________________________________
1/19
___________________________________________________________________________
1/20
Section 22
Services
2 Services
2.1.
Introduction to the services
Each of the networks described in the previous section supports one or more industrial
message handling services, as shown in the table below :
Services
Network
UNI-TE
UNI-TELWAY
FIPWAY
FIPIO
ETHWAY
- standard
- priority (TLG)
FIPWAY
ETHWAY
UNI-TELWAY (except TLG)
Common words (COM)
FIPWAY
ETHWAY
Remote I/O
FIPIO
Shared table(s)
FIPWAY
___________________________________________________________________________
2/1
A
2.2.
UNI-TE service
2.2-1 Presentation
UNI-TE is an industrial message handling system providing broadcast or point-to-point
communication using a question/answer mechanism called Request/Confirmation.
The application layer provides the user with standard services which can have services
added to them which are specific to PLCs, machine tool numerical controllers, robots,
etc.
2.2-2 CLIENT-SERVER concept

A device which supports the UNI-TE protocol may be either of the following :
CLIENT :
This device initiates communication. It asks a question (read), transmits

data (write) or sends orders (Run, Stop, etc).
Note : the term REQUESTER is sometimes used instead of CLIENT.
SERVER :
This device executes the order requested by the CLIENT and sends a
confirmation after execution.
Request
CLIENT
SERVER
Action
Confirmation
Some devices may be both CLIENT and SERVER simultaneously. For example, a PLC
is a SERVER during its system tasks (programming, adjustment, diagnostics, etc), and
a CLIENT, via the user program text blocks (sending commands, reading status data,
etc), in relation to another PLC, machine tool numerical controller, sensor or
preactuator.
___________________________________________________________________________
2/2
Services
2.2-3 List of requests

The standard UNI-TE requests that are listed in detail in section B.2 with their coding,
provide the following services :
ACCESS TO DATA
These requests are used to access bits, words or other standard data objects (bit string,
word string, etc), or objects specific to certain devices :
read bit,
read word,
write bit,
write word,
read data objects,
write data objects.
Requests most commonly used
UNSOLICITED DATA
This is the only service which does not generate a confirmation as it is already a
response to an implicit question.
This service will transfer a byte string from one application program to another without
it having been requested first.
The actual use of this data is the responsibility of the destination device which is implicitly
awaiting this data.
CLIENT
SERVER
APPLICATION
APPLICATION
Event
Unsolicited data
GENERAL USE
These requests are especially useful for diagnostics and on power-up (device and
application protocol identification, system and communication path tests, etc) :
identification,
mirror,
protocol version,
communication control,
read status.
___________________________________________________________________________
2/3
A
OPERATING MODE
These requests are used to run or stop a device connected to the bus. They can also
initialize the device and run a self-test sequence :
Run,
Init.
Stop,
SEMAPHORE MANAGEMENT
These requests are used for device reservation, dereservation or hold reservation
functions :
reservation,
hold reservation,
dereservation.
FILE TRANSFER
These requests enable a CLIENT device to upload or download program or data blocks
(segments), or other information to or from a SERVER using the following functions :
initialize load,
initialize download,
upload a segment,
download a segment,
end upload,
end download.
Note :
All devices do not necessarily support all requests. Refer to the appropriate product
documentation to ascertain which standard requests are supported, together with
their specific parameters and how they affect the device.
___________________________________________________________________________
2/4
Services
2.3
Common word service : COM service
The COM service is used to exchange numeric data (common words) between devices
forming part of the series 7 range.
The complete set of common words forms a database which is distributed among some
or all of the devices connected on the same network.
The database comprises :
256 words of 16 bits for ETHWAY,

128 words of 16 bits for FIPWAY.
Depending on their configuration, all network stations can access this database.
When configuring a module it is possible to :
inhibit its COM word activity,
enable its COM word activity in read only,
enable its COM word activity in read and write,
declare the number of common words (from 4 to 64) handled by the station. All stations
on a network which exchange common words must be configured to handle the same
number of common words.
Each module which uses the COM service has a memory zone of 256 words of 16 bits
which is reserved for exchanges between PLCs.
This memory zone is split depending on the network used (ETHWAY or FIPWAY) :
for FIPWAY, the split is fixed. Each station has 4 COM words (these stations will be
numbered from 0 to 31),
for ETHWAY, this memory zone is split into several sub-sets of words. Depending on
the number of stations sending words on the network, it is possible to have a maximum
of :
- 4 COM words per station for 64 active stations,
- 64 COM words per station for 4 active stations.
Stations which are declared active for the exchange of COM words must have low
network addresses (eg for 32 stations which each handle 8 COM words, these
stations must be numbered from 0 to 31).
___________________________________________________________________________
2/5
A
Operating principle
When the common words of a station have been updated by the CPU, they are
broadcast on the network.
On reception, the network interface of any PLC using the COM word service updates the
corresponding zone and makes them available to the CPU.
Use of the distributed database is recommended for the periodical broadcasting of
status variables without adding extra application program workload. To send data on
brief events, application-to-application communication with a confirmation is
recommended as transmission is guaranteed.
Station 0
Station 1
%NW{1}1
COM 0.1
Station 63 max
%NW{1}1
COM
0.1
OPERATE
OPERATE
Write :
to COM zone in the station
Read :
possible by all connected stations
Common memory zone

(256 words of 16 bits)
___________________________________________________________________________
2/6
Services
2.4
Shared table service
This service is used to exchange numeric data between all TSX 37, TSX 57 type devices.
All exchanged words form a table (exchange table) within the PLC. The table is split into
as many zones as there are PLCs on the network.
The principle of these exchanges is based on each PLC broadcasting one of these
zones to other PLCs on the network (broadcasting zone).
The maximum size of the exchange table is 128 words.
The maximum size of one broadcast zone is 16 words, the minimum size being 1 word.
The broadcast zones must be adjacent and the station numbers in ascending order.
Each broadcast zone is assigned to one PLC.
The length of the broadcast zone for PLC X must be the same in all PLCs.
Maximum number of PLCs taking part in the table exchange : 32 (addresses 0 to 31)
(but there can be 64 devices on the network).
Operating principle
These exchanges are based on the principle of broadcasting, by each device, of one
word memory zone (broadcast zone) to other devices on the network. All exchanged
words form the exchange zone, which must be defined in each device and have the
same length in all of them.
Device 1
@0
@30
Broadcast zone
PLC n 1
Device n
@1000
Zone PLC n 2
@40
@100
Zone PLC n 2
@1040
Zone PLC n 31
@120
@127
Zone PLC n 1
@1030
@1100
Zone PLC n 31
@1120
Zone PLC n 32
@1127
Zone PLC n 32
___________________________________________________________________________
2/7
A
Sending data
PLC n 1 broadcasts the data from its broadcast zone to all PLCs.
Write
PLC n 1
PLC n 2
Z. PLC1
Z. PLC2
Write
PLC n 16
Z. PLC1
Z. PLC1
Z. PLC2
Z. PLC2
Z. PLC n : Broadcast zone assigned to PLC n n
PLC n 2 then broadcasts the data from its broadcast zone to all PLCs.
PLC n 1
PLC n 2
PLC n 16
Z. PLC1
Z. PLC1
Z. PLC1
Z. PLC2
Z. PLC2
Z. PLC2
The exchange table in each PLC is updated separately from the PLC program. These
exchanges are cyclic.
Note :
The Shared Table and COM words service are exclusive on the same network.
___________________________________________________________________________
2/8
Services
2.5
2.5-1 Standard
This service provides point-to-point communication from application program to
application program. The partner devices in question are Series 7 and Series 1000
PLCs.
This service is especially suitable for :
sending an alarm message from a PLC to a supervision station,
exchanging data tables between two PLCs under the control of the application
programs in the source and destination device.
The maximum size of application-to-application messages is 1024 characters when
both partners are Series 1000 PLCs, otherwise the maximum size is 256 characters.
Station 0
Station 1
Station 15
Table of internal words

(16 or 32 bit words, floating point objects and characters)
This service can be installed using dedicated function blocks or by sending the UNI-TE
"Unsolicited data" request does not require a confirmation.
___________________________________________________________________________
2/9
A
2.5-2 Priority exchanges
The telegram service is a special type of application-to-application message designed
for transmitting urgent, high priority and infrequent data between two PLCs on the same
network.
A telegram from the PLC processor is sent immediately to its network module without
waiting for the end of the PLC scan.
It can be received :
either by scanning the fast task,
or by an associated event-triggered task during the configuration task.
The maximum size of messages sent using this service is restricted to 16 bytes.
Cyclic tasks
TLG read event task
Inputs
Processing
TSX 37
TSX 37
Outputs
___________________________________________________________________________
2/10
Services
2.6
Remote Input / Output services
This FIPIO service is used to exchange input status variables and output commands.
These exchanges are performed cyclically and automatically without any intervention
from the application program.
This service is also used to manage remote devices (configuration, etc). These
exchanges are aperiodic without any intervention from the application program.
In order to use this service, the remote inputs / outputs must be configured with the
correct software workshop :
the XTEL-CONF station tool for series 7 (for more information on these configurations,
refer to the X-TEL Software Workshop manual),
ORPHEE configuration environment for series 1000 (for more information on these
configurations, refer to the ORPHEE Language and software manual).
The use of this service and the associated language interface are described :
for series 7 in the PL7-3 Languages, V5 Operating modes manual,
for series 1000 in the APRIL 5000 PLC manual, Ref. TEM30000E.
The diagnostics and maintenance functions associated with this service are described :
for series 7 in the SYSDIAG, PL7-2/PL7-3 Application adjustment software manual,
for series 1000 in the ORPHEE language and software manual, Ref. TEM10000E and
the ORPHEE-DIAG Software manual Ref. 10800E. The SYSDIAG (DOS) tool is used
for diagnostics and maintenance purposes.
___________________________________________________________________________
2/11
___________________________________________________________________________
2/12
Section 33
3 X-WAY addressing mechanisms
3.1
General
This section describes the general addressing rules for assigning an address to
each communication entity in an architecture. It is to be read only by informed users,
who want to install a line analyzer on a network, code an address from a third party
device, etc).
In a communication architecture, all exchanges are generally in point-to-point mode
between two logical entities (client and server). These logical entities must be identified
by a unique address. This address has two construction levels :
architecture level
A network architecture consists of terminal stations and intermediate stations (bridges)
which link two or more networks.
A station is identified by :
- a unique network number in the architecture,
- a unique station number on a network.
The intermediate stations which are connected to different networks therefore have
several network addresses.
Terminal station
Station i
Address = N1S2
Network 1
Station j
Intermediate station
Address = N1S1
Address = N2S2
Station k
Address = N1S3
Network 2
Station l
Address = N2S1
Station m
Intermediate station
Address = N2S3
Address = N3S1
Terminal station
Network 3
Station n
Address = N3S2
___________________________________________________________________________
3/1
A
station level
This level is used to address an entity in the station.
A station which is connected to a network consists of a series of communication
entities which are located in the station itself as well as the devices connected to its
internal communication channels (FIPIO bus, PLC backplane bus, UNI-TELWAY
bus, etc).
A communication entity is identified in its station by an address (module number,
channel number in the module, connection point or slave address, etc).
Examples
Network 1
Module 0
channel 1
Connection
point 6
Station 1
Station 2
Module 3
channel 1
Module 1
channel 15
Connection
point 22
___________________________________________________________________________
3/2
3.2
3.2-1 Presentation
PLCs and devices which can be connected to an X-WAY network generally consist of
one or more communication entities.
The following three entities can be defined :
Station level entities,
Module level entities,
Communication channel level entities.
3.2-2 Station level entities

Each network station has application entities which are unique within that station. PLCs
for example have the following entities :
the station UNI-TE server,
communication tools:
- communication function for TSX 37 PLCs, etc
- text function blocks for TSX 17 and TSX/PMX model 40 PLCs,
the programming terminal which is connected to the terminal port,
the programming terminal which is connected to the privileged address on the FIPIO
fieldbus (address 63).
3.2-3 Module level entities

Each communication module manages one or more channels which can either be the
same or different type and has entities which are unique within this module. PLC
modules for example can have the following entities :
UNI-TE client/server,
network management, etc
3.2-4 Communication channel level entities

Communication channel level entities generally correspond to devices (and their
communication entities) connected to the bus or the network stemming from that
channel. PLC modules for example can have the following entities :
UNI-TE client/server,
PL7 application, etc
___________________________________________________________________________
3/3
A
3.3
Address format
3.3-1 Principles
The general format for describing the address of a destination entity which is part of an
X-WAY network is described below :
Address of an entity on an X-WAY network
Remote address (inter-station)
Local address (intra-station)
Network N Station N followed

by the local address
Physical address
3.3-2 Network number-station number

The "Network number" field shows the network number of the destination station during
the exchange. It must be between 0 and 127.
The "Station number" field shows the number of the destination station during the
exchange. It must be between 0 and 63.
3.3-3 Broadcast address

A broadcast corresponds to the sending of messages to all stations on a network or to
all communication entities of the same station.
The FF value, which is defined to describe a broadcast, can replace one of the elements
of a topological address. The broadcast level is determined according to the location of
that value in the address :
associated with the network number, messages are broadcast to all stations on the
selected network (example : 2.FF provides access to all stations connected to
network 2),
associated with a communication channel, messages are broadcast to all entities
connected to that channel (example : 2.4.5.1.FF provides access to all communication
entities on the UNI-TELWAY bus which are located in slot 1 of rack 0 in station 4 on
network 2).
___________________________________________________________________________
3/4
3.4
Introduction to hierarchical addressing
The address of a target communication entity of an exchange is organized in a hierarchy

on several levels (three, five or six).
Network 2
NETWORK
Station 4
STATION
System
Terminal
port
1, 2, 3
GATE
Communication
module
5
Application
16...249
16...99
MODULE
SELECTOR
CHANNEL
CONNECTION POINT
REFERENCE
3 levels
5 levels
6 levels
This address is organized into a hierarchy according to the communication entity slot :
over three levels for accessing the system, the terminal port or the application
(Network/Station/Gate),
over five levels for accessing the channel of a communication module
(Network/Station/Gate/Module/Channel). See section 3.6 for further details.
over six levels for accessing a communication entity located on a communication
channel (Network/Station/Gate/Selector/Connection point/Reference). See
section 3.7 for further details.
___________________________________________________________________________
3/5
A
3.5
3.5-1 Presentation
Addressing which is organized into a hierarchy over three levels and used for accessing
a communication module entity.
Network number
Shows the network number of the destination station of the exchange. Is between 0 and
127.
Station number
Shows the number of the destination station of the exchange. Is between 0 and 63.
When a broadcast is made to all the stations of the selected network, the station number
must have the value 255.
Gate number
The gate number is used to choose the communication entity within the selected station.
The entities which are unique in the station and whose locations are explicit are identified
by a logical address :
the system of the station (its UNI-TE server) : gate 0,
the programming terminal on the terminal port : gates 1, 2 and 3,
the programming terminal on the privileged address of a FIPIO fieldbus : gates 11, 12
and 13,
the communication blocks of TSX 37 PLCs, etc : gate 16,
the text block functions of the station application (TSX 17 and TSX/PMX model 40
PLCs) : from gate 16 for the TXT0 textblock to gate 79 for text block 63,
the communication functions of TSX 37/57 PLCs : gates 16 to 239,
the other gate numbers are reserved.
value 254 is reserved for showing : "all gate values"
___________________________________________________________________________
3/6
3.5-2 Example
The address of certain communication entities is organized into a hierarchy over three
levels. This applies particularly to :
the system of a device,
the terminal port of a PLC,
the PL7 application of a PLC (text block or communication function depending on the
case).
The coding of these addresses is shown in the example below :
Network 2
System : 2.4.0
Terminal port : 2.5.1
Text block 6 :
2.4.22
Communication function:
Station 4
2.5.16
Station 5
2.4.0
Access the system of the CPU : network 2, station 4, gate 0.
2.4.22
Access text block 6 of the application : network 2, station 4, gate 22 (16 + 6).
2.5.1
Access the terminal port : network 2, station 5, gate 1.
2.5.16
Access the communication functions : network 2, station 5, gate 16.
___________________________________________________________________________
3/7
A
3.6
3.6-1 Presentation
Addressing organized into a hierarchy over five levels and accessible via gate five is
used to access a channel of a communication module :
Network 2
NETWORK
Station 4
STATION
Communication
module
GATE
Channel 0
MODULE
Rack/Slot
Channel 1
CHANNEL
Channel n
104
Channel n
101
Channel n
1
Address
4
Address
1
Address
1
___________________________________________________________________________
3/8
The network, station and gate numbers were defined in section 3.5-1.
Module number
Only used if the gate number is 5 (access to a communication module), the module
number corresponds to the physical location of this module on the backplane bus (rack
number and slot in the rack).
Channel number
Only used if the gate number is 5 (access to a communication module), the channel
number corresponds to the address of the device connected to the network or bus from
the module selected.
The devices connected to channel 0 of the module can be accessed directly via their
address (if, for example, communication with the device at address 5 on channel 0 is
required, the channel number must take the value 5). The value 99 is used for
broadcasting to all channel 0 devices.
The devices connected to channel 1 of the module can be accessed via their address
+ 100 (if, for example, communication with the device at address 5 on channel 1 is
required, the channel number must take the value 105). The value 199 is used for
broadcasting to all channel 1 devices.
A slave PLC connected to a UNI-TELWAY bus can, for example, have up to three
addresses :
a system address (known as Ad0)
This address is compulsory. All messages received at this address are transmitted to
the system gate of the destination PLC of the exchange,
a client address (known as Ad1)
This optional address is managed by the application program of the slave PLC. It
authorizes the transmission of requests to any UNI-TELWAY address (system gate
or master PLC / other slave application) and the reception of responses or associated
confirmations,
a text reception address (known as Ad2)
This optional address is assigned to the slave module for the reception of unsolicited
data from another device in the architecture. The messages received on this address
are transmitted to the application program of the destination PLC of the exchange.
A slave PLC with, for example, the address Ad0 = 10, Ad1 = 11 and Ad2 = 12 on a UNITELWAY bus connected to channel 1 of a communication module, can be accessed via
the following channel numbers :
channel 110 for Ad0,
channel 111 for Ad1,
channel 112 for Ad2.
___________________________________________________________________________
3/9
A
3.6.2 Example
The address of certain communication entities is organized into a hierarchy over five
levels. This applies particularly to devices connected to a channel of a communication
module.
Example of five level addressing :
Network 2
Station 4
Uni-Telway
Communication module installed

in slot 6 of rack 0.
Channel 1 used.
System : 2.4.5.06.114
Link address 14
System : 2.4.5.06.103
Ad0 = 3
Ad1 = 4
Ad2 = 5
Application : 2.4.5.06.105
2.4.5.06.114
Access to the ATV 16 system : network 2, station 4, gate 5 (access to the

communication module), module 06 (rack 0 slot 6), channel 114 (link address
of the destination device + 100 as it is channel 1 of the communication module
which is used).
2.4.5.06.103
Access to the CPU system of the slave PLC on the UNI-TELWAY bus : network
2, station 4, gate 5 (access to the communication module), module 06 (rack 0
slot 6), channel 103 (address Ad0 + 100 as it is channel 1 of the communication
module which is used).
2.4.5.06.105
Access to the application of the slave PLC on the UNI-TELWAY bus :

network 2, station 4, gate 5 (access to the communication module), module 06
(rack 0 slot 6), channel 105 (address Ad2 + 100 as it is channel 1 of the
communication module which is used).
___________________________________________________________________________
3/10
3.7
3.7-1 Presentation
Addressing organized into a hierarchy over six levels, which can only be accessed via
gate 8, is used to physically identify application entities in a station made up of several
communication channels (TSX 57 for example) :
Network 2
NETWORK
Station 4
STATION
Communication
module
GATE
Module in
the
backplane bus
1
SELECTOR
Module
integrated in
the CPU
2
CONNECTION POINT
REFERENCE
UNI-TE
Server
System
0
UNI-TE
Client
System
1
UNI-TE
Server
Channel 0
4
UNI-TE
Server
Channel 1
7
UNI-TE
Server
Channel 2
10
___________________________________________________________________________
3/11
A
The network, station and gate numbers were defined in section 3.5-1.
Channel selector number
This parameter identifies the communication channel within the station to which the
destination device of the exchange is connected.
It takes one of the following values :
1 : for exchanges with a communication module located on the backplane bus of the
PLC,
2 : for exchanges with a device connected to the bus or the network from the
communication module integrated in the CPU (such as the FIPIO link integrated in the
CPU).
Connection point number
This parameter identifies the destination device of the exchange by its connection point
number on the bus or the network to which it is connected. It is between 0 and 252.
When the target device is located on the backplane bus of a PLC (for example, the
system of a communication module), the connection point number corresponds to the
slot number of this module (slot 0 : connection point 0, slot 3 : connection point 3, etc).
When broadcasting to all the devices of the selected intra-station channel, the connection
point number must have the value 255.
Reference number
This parameter identifies the communication entity in the destination device of the
exchange.
It takes one of the following values :
0 : for exchanges with the UNI-TE Server of the destination entity (for example, the
system),
1 : for exchanges with the UNI-TE Client of the destination entity,
4 : for exchanges with the channel 0 Server (terminal port, for example),
7 : for exchanges with the channel 1 Server (PCMCIA card, for example),
10 : for exchanges with the channel 2 Server (FIPIO link, for example).
___________________________________________________________________________
3/12
3.7-2 Example
The address of certain communication entities is organized into a hierarchy over six
levels. This applies particularly to application entities in a station made up of several
communication channels.
Example of six level addressing :
Network 6
Terminal port (channel 0) :

6.2.8.1.0.4
Station 2
FIPIO link (channel 2) :
Channel 0 : 6.2.8.1.3.4
PCMCIA card (channel 1) :
6.2.8.1.0.10
6.2.8.1.3.7
Module system :
6.2.8.1.3.0
PCMCIA card (channel 1) :
6.2.8.1.0.7
ATV 16 system :
Connection point 18
6.2.8.2.18.0
___________________________________________________________________________
3/13
A
6.2.8.1.0.4
Access to the server of the terminal port (channel 0) of the CPU : network 6,
station 2, gate 8 (extended addressing), selector 1 (communication module on
the backplane bus), connection point 0 (the CPU is module 0), reference 4
(channel 0.)
Note : the terminal port can also be accessed via hierarchical addressing over
three levels. Its address is then 6.2.1 (network 6, station 2 and gate 1).
6.2.8.1.0.10
Access to the server of the FIPIO module (channel 2) of the CPU : network 6,
(channel 2).
6.2.8.2.18.0
Access to the ATV 16 system : network 6, station 2, gate 8 (extended

addressing), selector 2 (exchange with a device connected to the bus or the
network from the communication module integrated in the CPU), connection
point 18, reference 0 (access to the system).
6.2.8.1.0.7
Access to the server of the PCMCIA card (channel 1) of the CPU : network 6,
(channel 1).
6.2.8.1.3.4
Access to the server of channel 0 of the module located in slot 3 : network 6,

the backplane bus), connection point 3 (slot 3), reference 4 (channel 0).
6.2.8.1.3.0
Access to the system of the module located in slot 3 : network 6, station 2, gate 8
(extended addressing), selector 1 (communication module on the backplane
bus), connection point 3 (slot 3), reference 0 (system).
6.2.8.1.3.7
Access to the server of the PCMCIA card (channel 1) of the module located in
slot 3 : network 6, station 2, gate 8 (extended addressing), selector 1
(communication module on the backplane bus), connection point 3 (slot 3),
reference 7 (channel 1).
___________________________________________________________________________
3/14
Section 44
Appendix
4 Appendix
4.1
X-WAY frame format
4.1-1 Presentation
This section describes the general addressing rules used for assigning an address
to each communication entity in an architecture. It is to be read only by informed
users, who want to install a line analyzer on a network, code an address from a thirdparty device, etc).
The general format of a network datagram is as follows :
Physical Layer
Preamble
Data link Layer
End
Link layer data
Network Layer (message handling system)
CRC
X-WAY frame
Application Layer (message handling system)

Application Layer (shared data)
Data
Shared data
Preamble and end

These two pieces of information linked to the Physical layer synchronize the exchanges.
They are specific to the type of network used (for more information on their coding, refer
to the reference manual for the network concerned).
CRC and Link layer data
These two pieces of information are linked to the Data link layer. They are specific to the
type of network used (for more information on their coding, refer to the reference manual
for the network concerned).
X-WAY frame
The X-WAY frame contains all the information required for inter-station exchanges.
Details are given in the following sections.
Shared data
The frame reserved for shared data contains all the information required for periodic
exchanges (common words, remote inputs/outputs, etc). Details are given in section
4.1-8.
___________________________________________________________________________
4/1
A
4.1-2 X-WAY frame
The X-WAY frame is made up as follows :
NPDU
type
Addresses
3 and 5 level
addressing
6 level
addressing extension
Data
(message system)
NPDU type (Network Protocol Data Unit)

This field is linked to the network layer. It is described in section 4.1-3.
Addresses
This field shows the addresses (network, station and gate numbers) of the sender and
destination of the exchange. It is described in section 4.1-4.
Three and five level addressing
This field defines the addresses of the exchange sender and destination communication
entities when addressing is structured into three or five levels (module, channel
numbers, etc). It is described in section 4.1-5.
Six level addressing extension
This field defines the addresses of the exchange sender and destination communication
entities when addressing is structured into six levels (selector, connection point
numbers, etc). It is described in section 4.1-6.
Data (message handling system)
This field contains all the exchange data. It is described in section 4.1-7.
Note
When the address of the sender entity is coded on five levels and the address of the
destination entity is on six levels, the two fields "Three and five level addressing" and
"Six level addressing extension" are filled in.
___________________________________________________________________________
4/2
Appendix
4.1-3 NPDU type

NPDU
type
Addresses
Five level
addressing
Six level
addressing
4 bits
2 bits
1 bit
1 bit
Type
Level of
service
Refusal
Ext.
Data
(message system)
Type
Takes one of the following values :
0 to 14 Reserved,
15
NPDU data.
Level of service
0
Standard,
Telegram,
2 to 3
Reserved.
Refusal
0
Message accepted,
Message refused.
Extension
0
if one of the devices (sender or destination) uses addressing on three or six

levels for the exchange concerned,
if one of the devices (sender or destination) uses addressing on five levels

for the exchange concerned.
___________________________________________________________________________
4/3
A
4.1-4 Addresses
NPDU
type
Addresses
3 and 5 level
addressing
6 level
2 bytes
2 bytes
Sender address
Destination address
1 byte
4 bits
4 bits
Station
number
Network
number
Gate
number
Data
(message system)
Station number
Corresponds to the station number (of the sender or the destination). The station
number must be between 0 and 63 (the value 255 is reserved for broadcasting).
Network number
Corresponds to the network number (of the sender or the destination). The network
number must be between 0 and 127.
When the value is greater than 15, an address extension is required.
Gate number
Corresponds to the gate number targeted in the destination entity of the exchange.
0
access the system of the device,
1, 2, 3
access the terminal port of a PLC,
access a communication module (addressing structured on five levels),
access a communication module (addressing structured on six levels),
11, 12, 13 access the terminal connected at connection point 63 on FIPIO,

16 to 239 access the application (text function block, communication function block,
etc),
the other values are reserved.
when the value is greater than 15, an address extension is required.
___________________________________________________________________________
4/4
Appendix
4.1-5 Five level addressing

NPDU
type
Addresses
Parameter 1
3 and 5 level
addressing
Parameter 2
6 level
Data
addressing extension (message system)
Parameter n
1 byte
1 to 7 bytes
Parameter code
Parameter value
Length (in bytes) of the value

1 if last parameter
Identifier
The various possibilities are shown in the table below :

Parameter value
Identifier
Length
Sending gate n if > 15
Destination gate n if > 15
1
1
Sending network n if > 15
Destination network n if > 15
Module n and channel n

of the sender
Module n and channel n

of the destination
8 bits
8 bits
Module Channel
number number
___________________________________________________________________________
4/5
A
4.1-6 Six level addressing
Reminder : six level addressing can be accessed via gate 8
NPDU
type
Addresses
Parameter 1
3 and 5 level
addressing
Parameter 2
6 level
Data
(message system)
Parameter n
1 byte
1 to 7 bytes
Parameter code
Parameter value
Length (in bytes) of the value

1 if last parameter
Identifier
The various possibilities are shown in the table below :

Parameter value
Identifier
Length
Compacted physical
sender address
Compacted physical
destination address
Extended physical
sender address
Extended physical
destination address
4 bits
4 bits
8 bits
Selector
Refe- Connect.
rence
point
8 bits
8 bits
Selector
Refe- Connect.
rence
point
8 bits
___________________________________________________________________________
4/6
Appendix
4.1-7 Data (message handling system)

NPDU
type
Addresses
3 and 5 level
addressing
6 level addressing
extension
Data
(message system)
Data for the

UNI-TE service
Transmitted data is structured in one of the three following ways :

Request code
1 byte
Category code
1 byte
Transmission data
1 to 254 bytes
Application-to-application data (text block, function block, etc)

1 to 256 bytes
Telegram type data

1 to 16 bytes
Received data is structured as follows :

Confirmation
1 byte
Response data
0 to 255 bytes
___________________________________________________________________________
4/7
A
4.1-8 Distributed data
Distributed data, at Application layer level, is specific to periodic data exchanges
(common words, remote I/O, etc).
Distributed data is structured as follows :
Common words
Shared table
FIP network
MPS frame
I/O management
Network mgnt.
Distributed data
ETHWAY, etc network
Common words
Shared data for a FIP network (FIPWAY or FIPIO)

Shared data for a FIP network uses the standard FIP MPS service (Manufacturing
Periodical Services). Their frame is as below :
APDU
type
1 byte
Data
Status
1 to 127 bytes
1 byte
APDU type (Application Protocol Data Unit)

This parameter takes one of the following values :
80
Application type data (common words, remote I/O, etc),
64
Data specific to network management.
Data
The data corresponds to the value of the common words, the states of the remote I/O,
etc. Details of the coding of this data are not given in this document because the syntax
is specific to the type of information circulating (series of bits for discrete modules, series
of words for analog modules, etc).
Status
This parameter indicates whether the cyclic variables have really been updated by their
producer. It takes one of the following values :
1
The cyclic variables have been updated,
The cyclic variables have not been updated.
___________________________________________________________________________
4/8
Appendix
Common words on ETHWAY

The data specific to this service is structured as below :
Station
number
1 byte
Size of
COM
1 byte
Common words
8 to 128 bytes
Station number
This parameter indicates the number of the station sending the common words.
Size of COM
This parameter indicates the size of the common words exchanged on the network.
Common words
This byte string corresponds to the value of the common words transmitted.
___________________________________________________________________________
4/9
___________________________________________________________________________
4/10
Contents
Part B
B
Section
1
Page
General principles of the UNI-TE protocol
1/1
1.1
Description of the services
1/1
1.2
UNI-TE V1.1 and V2.0
1/2
1.3
UNI-TE exchange format

1.3-1 Presentation
1.3-2 Link with an XWAY frame
1.3-3 Description of a UNI-TE request
1/3
1/3
1/4
1/5
1.4
Type of data used
1/7
___________________________________________________________________________
B/1
Contents
Part B
B
Section
2
Page
Request coding
2/1
2.1
List of UNI-TE requests
2/2
2.2
General use requests

2.2-1 Identifying a device
2.2-2 System diagnostics for a programmable device
2.2-3 Exchange of UNI-TE characteristics between the
Client/Server
2.2-4 Communication test
2/3
2/3
2/8
2/10
2/12
2.3
Requests to access standard objects

2.3-1 Read an internal bit
2.3-2 Write an internal bit
2.3-3 Read a system bit
2.3-4 Write a system bit
2.3-5 Read an internal word
2.3-6 Write an internal word
2.3-7 Read a system word
2.3-8 Write a system word
2.3-9 Read a constant word
2.3-10 Force an internal bit
2.3-11 Read Grafcet step status
2/13
2/13
2/14
2/15
2/16
2/17
2/18
2/19
2/20
2/21
2/22
2/23
2.4
Requests to access the objects of an I/O module

2.4-1 Read the memory image of a simple discrete module
2.4-2 Write memory image bit of a simple discrete module
2.4-3 Read the status of a module
2.4-4 Read the objects of an I/O channel
2.4-5 Write the objects of an I/O channel
2/25
2/26
2/29
2/31
2/34
2/37
___________________________________________________________________________
B/2
Contents
Part B
B
Section
Page
2.5
Requests to access generic objects

2.5-1 Identification of objects
2.5-2 Access parameters
2.5-3 Read an object
2.5-4 Write an object
2.5-5 Read a generic object
2.5-6 Write a generic object
2.5-7 Read a list of objects
2.5-8 Write a list of objects
2.5-9 Action on an object
2/39
2/39
2/40
2/42
2/44
2/45
2/47
2/49
2/51
2/52
2.6
Operating mode management requests

2.6-1 Launching an application or task
2.6-2 Stopping an application or task
2.6-3 Initialization
2/54
2/54
2/55
2/56
2.7
Data transfer requests

2.7-1 Start downloading
2.7-2 Downloading a segment
2.7-3 Ending a downloading sequence
2.7-4 Launching a backup sequence
2.7-5 Backing up a segment
2.7-6 Ending a backup
2.7-7 Memory transfer and comparison
2/57
2/58
2/59
2/60
2/61
2/62
2/63
2/64
2.8
Semaphore management request

2.8-1 Reservation
2.8-2 Release
2.8-3 Hold a reservation
2/65
2/65
2/66
2/67
___________________________________________________________________________
B/3
Contents
Part B
B
Section
3
Page
Appendix
3/1
3.1
List of request codes
3/1
3.2
Compatibility between UNI-TE V1.1 and V2.0 requests
3/2
3.3
Correspondence table between UNI-TE V1.1 and V2.0 requests
3/4
3.4
Description of various classes of object

3.4-1 Timer objects
3.4-2 Monostable objects
3.4-3 Counter object
3.4-4 Register objects
3.4-5 Drum controller
3.4-6 Fast counter object
3.4-7 "Pulse width modulation" object
3.4-8 "Pulse train generation" object
3.4-9 "Shift register" object
3.4-10 "Step register" object
3.4-11 "Operator dialog message" object
3.4-12 Real-time clock object
3/6
3/6
3/7
3/7
3/8
3/8
3/9
3/9
3/10
3/10
3/11
3/11
3/12
___________________________________________________________________________
B/4
General principles of the UNI-TE Section

protocol 11
1 General principles of the UNI-TE protocol
1.1
Description of the services
The UNI-TE protocol respects the client/server model.

Request
B
SERVER
CLIENT
Request
processing
Confirmation
The client entity prepares the request to be transmitted to the server. This interprets the
request code and activates the associated processing. Following the processing result,
the server sends a positive or negative response to the client.
Each UNI-TE request is identified by a unique code.
The majority of UNI-TE requests are "confirmed". That is, they operate on a Question/
Answer mechanism called "Request/Confirmation". Mirror and unsolicited data requests
are the exceptions to this rule.
The confirmation gives the result of the operation performed by the server. There are
three possibilities :
Request
confirmation
Request code + 30H

Request exception
Mirror
The operation has been performed by

the server, additional data
summarizes the result of the operation
Positive
confirmation
FEH
The operation has been performed

correctly and no additional
data is transmitted in the
response
Negative
confirmation
FDH
The operation could not be executed

by the server : unknown
request, value out of range,
configuration absent, etc
___________________________________________________________________________
1/1
1.2
UNI-TE V1.1 and V2.0
The UNI-TE V1.1 protocol is incorporated in communication systems which are

integrated in basic model 40 architectures or in third-party equipment.
An extension of the UNI-TE protocol has been developed to improve performance

(supervision, man-machine interface, etc).
The two versions are compatible. However, some functions may be different. The
differences between the two versions are shown in a correspondence table (this table
is in the appendix, section 3).
___________________________________________________________________________
1/2
1.3
UNI-TE exchange format
1.3-1 Presentation
The general structure of an exchange observes the following format. It depends on the
UNI-TE protocol version.
Request format
F9H
TransacRequest Category
tion
code
code
number
Data specific to
the request
<-------------------UNI-TE V1.1 ----------------->

<-------------------------------- UNI-TE V2.0 ------------------------------->
Confirmation format
F0H
TransacConfirma- Data specific to the

tion
tion
confirmation
number
<------------UNI-TE V1.1 --------->

<------------------------ UNI-TE V2.0 ------------------------>
UNI-TE V2.0 is a superset of UNI-TE version V1.1
___________________________________________________________________________
1/3
1.3-2 Link with an XWAY frame
Summary
A UNI-TE request (question or confirmation) is integrated in an XWAY frame as
indicated below (more detailed information on coding an XWAY frame is described in
section 4.1 in part A) :
<--------------------------------------- XWAY frame ---------------------------------------->
Header
NPDU
Addresses
Addressing
5 levels
Addressing
6 levels
Data
F9H
Transaction
number
Request
code
Category
code
Data
End
Request
<------------------------ V1.1 ------------------------->

<---------------------------------------------- V2.0 ---------------------------------------------->
Confirmation
F0H
Transaction
number
Confirmation
Data
<------------------------ V1.1 ------------------------->

<---------------------------------------------- V2.0 ---------------------------------------------->
___________________________________________________________________________
1/4
1.3-3 Description of a UNI-TE request

The general structure of a UNI-TE request observes the following format :
Request format
B
F9H
TransacRequest Category
tion
code
code
number
Data
specific
to the
request
<----------><-----------><-----------><-----------><----------->
1 byte
1 byte
1 byte
1 byte
1 byte
The transaction number given at each transmission of requests enables a client to

associate a response with the request sent and thus, avoid any possible mixing of
responses. The header byte (F9H), and the transaction number are managed by the
system and are thus transparent to the user. They are nevertheless transmitted on the
support during transmission of the message.
Confirmation format
Positive confirmation with no specific data
F0H
TransacFEH
tion
confirmanumber
tion
<----------><-----------><----------->
1 byte
1 byte
1 byte
Negative confirmation with no specific data

F0H
TransacFDH
tion
confirmanumber
tion
<----------><-----------><----------->
1 byte
1 byte
1 byte
Positive confirmation with specific data

F0H
TransacConfirmation
tion report
number
Data specific to
the request
<-1 byte-><-1 byte--><-1 byte-><-------1 byte---------->
___________________________________________________________________________
1/5
Note :
A device which supports the UNI-TE V2.0 protocol will code its requests in the UNI-TE V2.0. Due
to the compatibility of the various V1.1 and V2.0 requests, a V1.1 level server will respond to a
UNI-TE V2.0 client in a transparent manner. When a request is totally different in V1.1 and V2.0,
the V1.1 level server will respond with a negative (FDH) to the question from a UNI-TE V2.0 client.
___________________________________________________________________________
1/6
1.4
Type of data used
The types of UNI-TE data are as follows :

bit,
byte,
unsigned integer (16-bit),

signed integer (16-bit),
single length floating point word (32-bit),
bit string, byte string, character string, word string, etc
The UNI-TE protocol has specific coding for each type :
Type
Comments on the coding
Bit
1 bit
Value 0 : false / Value 1 : true
Byte
Series of 8 bits
16-bit unsigned integer
Byte 0 : least significant / Byte 1 : most significant
16-bit signed integer
Two's complement
32-bit signed integer
Two's complement
Single length floating point
IEEE 754 format
Variable length
bit string
The first byte describes the length in number of significant bits in

the string. The number of bits is limited to 256.
An additional type can be defined for using
a length greater than 2 bytes.
For example : a 19-bit string is coded :
byte 0
length = 19
byte 1
7....0
byte 2
byte 3
15 . . . . 8 23 . . . 9 . . . 16
not significant
Fixed length
byte table
There is no length byte at the beginning of the table
Variable length
byte table
The first byte gives the length of the table

length = 4
byte 0
byte 1
byte 2
byte 3
___________________________________________________________________________
1/7
Type
Comments on the coding
Fixed length
byte table
There is no length byte at the beginning of the table
Variable length
byte table
The first byte gives the length of the table

length = 3
byte 1 = 'A'
byte 2 = 'T'
byte 3 = 'S'
Fixed length
character string
The length byte at the beginning of the string is not used
Variable size 16-bit

word table
The first byte gives the length of the table in

number of words
Fixed size 16-bit

word table
The length byte at the start of the table is not used
___________________________________________________________________________
1/8
RequestSection
coding 22
2 Request coding
This section describes the coding of requests associated with UNI-TE V2.0 and V1.1
services.
The two header bytes specific to the V2.0 protocol (F9H or F0H and transaction number)
are transparent to the user ; for an easier understanding of the requests, these two bytes
are not shown in the presentation of messages in this document. They are however
transmitted on the line.
When presenting confirmation frames the detailed coding is only given for positive
responses with additional data (simple responses have been described in section 1.3).
Confirmed requests have a compulsory field, called the "category code", used to
manage access rights (values 0 to 7). This code depends on the device concerned. For
example, all PLCs in the TSX range use category code 7.
Note :
The requests described in this section are those which are most widely used. There are other
requests which are reserved for internal use. These are not described in this document.
Where there are differences between UNI-TE V1.1 and V2.0 frames these are mentioned in this
manual. If no difference is mentioned, the frames are identical in both versions.
___________________________________________________________________________
2/1
2.1
Heading
Request name
General use
General use
General use
General use
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
I/O modules
I/O modules
I/O modules
I/O modules
I/O modules
Generic objects
Generic objects
Generic objects
Generic objects
Generic objects
Object list
Object list
Operating mode
Operating mode
Operating mode
Data transfer
Data transfer
Data transfer
Data transfer
Data transfer
Data transfer
Data transfer
Semaphore
Semaphore
Semaphore
IDENTIFICATION
READ_CPU
PROTOCOL_VERSION
MIRROR
READ_INTERNAL_BIT
WRITE_INTERNAL_BIT
READ_SYSTEM_BIT
WRITE_SYSTEM_BIT
READ_INTERNAL_WORD
WRITE_INTERNAL_WORD
READ_SYSTEM_WORD
WRITE_SYSTEM_WORD
READ-CONSTANT-WORD
FORCE-INTERNAL-BIT
READ-GRAFCET-BIT
READ_DIGITAL_MODULE_IMAGE
WRITE_DIGITAL_MODULE_IMAGE
READ_STATUS_MODULE
READ_IO_CHANNEL
WRITE_IO_CHANNEL
READ_GENERIC-OBJECT
WRITE_GENERIC_OBJECT
READ_OBJECT
WRITE_OBJECT
ACTION_GENERIC_OBJECT
READ_OBJECT_LIST
WRITE_OBJECT_LIST
RUN
STOP
INIT
OPEN_DOWNLOAD
WRITE_DOWNLOAD
CLOSE_DOWNLOAD
OPEN_UPLOAD
READ_UPLOAD
CLOSE_UPLOAD
BACKUP
RESERVE
RELEASE
I_AM_ALIVE
Request
code
Confirmation
code
0FH
4FH
30H
FAH
00H
10H
01H
11H
04H
14H
06H
15H
05H
1BH
2AH
49H
4AH
44H
43H
48H
82H
83H
36H
37H
9FH
38H
39H
24H
25H
33H
3AH
3BH
3CH
3DH
3EH
3FH
45H
1DH
1EH
2DH
3FH
7FH
60H
FBH
30H
FEH
31H
FEH
34H
FEH
36H
FEH
35H
FEH
5AH
79H
7AH
74H
73H
78H
B2H
B3H
66H
FEH
CFH
68H
69H
FEH
FEH
63H
6AH
6BH
6CH
6DH
6EH
6FH
75H
FEH
FEH
FEH
___________________________________________________________________________
2/2
Request coding
2.2
The UNI-TE protocol can identify and diagnose any type of device which has a
UNI-TE server. These two functions are divided into separate requests :
identification using the same request name and Protocol Version request,
diagnosis using Status, Read-CPU, Mirror requests.
2.2-1 Identifying a device

Request name : IDENTIFICATION.
This service supplies identification and structure data on the UNI-TE server which is the
destination of the request. The identification is general for all types of CPU devices,
network module, communciation module, axis controllers, speed drives, numerical
controllers, operator interface terminals, etc.
This data is broken down into three levels :
product range level,
sub-family level, divided into :
- type of application (eg : discrete, analog, communication, etc),
- type of product (eg : sensor/actuator level, cell level, workshop level, etc).
catalogue reference level.
The values correspond to the type of application, type of product and catalogue
reference depending on the destination device. Refer to corresponding document.
The IDENTIFICATION request also supplies a minimum amount of diagnostic data,
giving the indicator lamp status and the content of the status words of the devices.
___________________________________________________________________________
2/3
Comment
A device which has several elements (eg : modular TBX, etc) gives in the response
the complete identification of the elements of which it consists.
B
Product range
Type of application
Type of product
Catalogue reference
2 components (2 channels)
Basic module
Channel 1
Type of application
Type of product
Catalogue reference
No components
Channel 2
Type of application
Type of product
Catalogue reference
No components
Request format
Request Category
code
code
0FH
07
1 byte
1 byte
Confirmation format (UNI-TE V2.0)

Confirmation
3FH
Type of
identification
Product
range
Identification
element
Number
of components
Identification
of components
1 byte
1 byte
1 byte
8 bytes
1 byte
0 to n bytes
Type of identification
255
Product range
identifies the product range to which the device belongs
Number of components
indicates the number of channels for that particular module.
___________________________________________________________________________
2/4
Request coding
Component identification :
Address
Identification
element
Address
Identification
element
1 byte
> 8 bytes
1 byte
...
. . .
B
<---------Component N 1--------><--------Component N 2--------->
Etc.
These fields are present if the number of components is other than 0.

- Address
- Identification element
number of logical channels

coding these parameters is identical to that described on
the previous page.
Identification element :
Version
1 byte
ASCII
string
Device
status
Status of standard
indicator lamps
Character
string
Bit
string
8-bit table
- Version
- ASCII string
- Device status
Basic
Basic
module module
type of
type of
application product
1 byte
1 byte
Catalogue
Reference
Status of
basic module
1 byte
8-bit table
version number of device coded on two BCD 4-bit bytes

product reference
describes general status of the device.
In general, a single byte is sufficient to describe the status of the device. However,
extensions are possible.
Status values :
0
1
2
3
4
5
6
=
=
=
=
=
=
=
Does not exist

Autotest
Faulty
Ready/Run
Waiting
Not Configured
Stop.
If the server does not manage the information, the length field takes the value 0
(see section 1.4).
___________________________________________________________________________
2/5
- Indicator lamp status : the 8 bits show the status of the following indicator lamps :
Coding
bit 7
bit 0
B
00
01
10
11
Off
Blinking
On
Not significant
Run indicator lamp

Fault indicator lamp
I/O indicator lamp
Other indicator
lamp
16#FF if not used
- Basic module application type : for the value of this field, refer to specific product
documentation,
- Basic module product type
: for the value of this field, refer to specific product
documentation,
- Catalogue reference
: designates the device in the product type : for the
value of this field, refer to specific product
documentation,
- Basic module status :
Type of fault
Bit n
Comment
Internal fault
Hardware failure
Operating fault
Terminal block fault
Terminal block absent
Self-test
Module performing self-test
Reserved
Conf. fault
Modules not compatible
Absent
Module absent or powered down
Down
One of the modules supported is faulty
___________________________________________________________________________
2/6
Request coding

Confirmation
3FH
Type of
product
Product
subtype
Version
1 byte
1 byte
1 byte
1 byte
ASCII
string
Character
string
Type of product
coding this header is identical to that described in UNI-TE

V2.0 confirmation
Version and ASCII string
device version and product reference identical to items

which have the same name in UNI-TE V2.0
Product sub-type
identification extension created in the product type field.
___________________________________________________________________________
2/7
2.2-2 System diagnostics for a programmable device

Request name : READ_CPU.
This service enables system diagnostics to be performed on any device using

UNI-TE V2.0. This service does not exist in version 1.1.
Request format (UNI-TE V2.0)
Request Category
code
code
Extension
4FH
07
1 byte
1 byte
1 byte
Extension : reserved for future developments. The default value is 0

Confirmation
Extension
7FH
Status of standard
indicator lamps
CPU status
Reserver
address
8-bit table
Byte table
1 byte
1 byte
8-bit table
. . .
Type of
application
error
Debug
data
Product
range
Specific
1 byte
8-bit table
1 byte
0 bytes
. . .
Extension
: reserved for future developments. The default value is 0,
Lamp status
: identical to field which has the same name in the previous

service (section 2.2-1).
___________________________________________________________________________
2/8
Request coding
CPU status : logical status of a CPU or a device,

bit 7
bit 0
B
Run (1)/# of Run (0)
Application can be executed (1)
Memory cartridge present (1)
Current reservation (1)
BreakPoint complete stop
Application error
Partial run
Grafcet Overrun
Reserver address
: network address of the application which has reserved

the CPU (16#FFFFFF signifies "no current reservation")
Type of application error : additional data on the CPU status

Memory
RAM memory can be executed
and software error
Software error
0
2
no valid configuration
several valid configurations
0
1
Watchdog overflow
Application cannot be executed
Unexpected processing interruption
Debug data
: not used
Product range
: identifies the product range to which the device belongs
Specific
: optional field in which additional diagnostic data can be given

(eg : program in Ram with checksum OK, application
compatible with operating system, etc).
___________________________________________________________________________
2/9
2.2-3 Exchange of UNI-TE characteristics between the Client/Server

Request name : PROTOCOL_VERSION.
In a client/server relationship, this service can negotiate UNI-TE requests between the
2 communicating entities.
Request format
List
<----------------------------------------------------->
Request Category Maximum Number
code
code
size of of versions Version
30H
07
APDU supported
1 byte
1 byte
1 word
1 byte
1 byte
Version
Version
1 byte
1 byte
. . .
Maximum size of the APDU
: 128 bytes (in V1.1)

: 256 bytes (in V2.0)
(Corresponds to the maximum size of a UNI-TE frame)
Number of versions supported
: number of UNI-TE versions supported by the

device and listed in the "Version" fields
Version
: UNI-TE version n coded on two BCD 4-bit

bytes.

List
<----------------------------------------->
Confirm- Maximum Number
ation
size of of versions Version
60H
APDU supported
1 byte
1 word
. . .
Size
of the
T-list
1 word
1 byte
1 byte
. . .
Version
. . .
1 byte
List of
Horizontal
requests
conformity
supported
Bit
string
Bit
string
Maximum size of the APDU
: 128 bytes (in V1.1)

: 256 bytes (in V2.0)
(Corresponds to the maximum size of a UNI-TE frame)
Number of versions supported
: number of UNI-TE versions supported by the

device and listed in the "Version" fields
___________________________________________________________________________
2/10
Request coding
Version
: UNI-TE version n coded on two BCD 4-bit bytes
T-List size
: reserved for future developments. Its default

value is 0
Horizontal conformity
: reserved for future developments. Its default

value is 0 (optional)
List of requests supported
: bit string indicating the requests supported by

the server. It has the following format :
Byte 0
Request code 00
Byte 1
Length = nb bit
Request code 08
Byte 2
1
Request (n-1) * 8
Byte n
1
Bit i : 1 if the request is managed

Bit i : 0 if the request is not managed

List
<----------------------------------------->
ConfirmNumber
Max. size
ation
of versions Version
of APDU
60H
supported
1 byte
1 byte
1 byte
1 byte
. . .
Version
1 byte
Size of
T-list
1 byte
The meaning of all these fields is identical to that described in UNI-TE V2.0 confirmation.
The UNI-TE V1.1-V2.0 difference is found where the 2 last fields of theUNI-TE V2.0
frame disappear.
___________________________________________________________________________
2/11
2.2-4 Communication test

Request name : MIRROR.
This service is used to test the correct routing of data between 2 communicating devices.
It is also used for carrying out performance measurements.
Request format
Request Category
code
code
FAH
07
1 byte
1 byte
User data :
User
data
Byte table
series of bytes transmitted in the request which must be retransmitted

in full in the response.
Confirmation format
Confirmation
FBH
User
data
1 byte
Byte table
User data : retransmission of the series of bytes transmitted in the request.
___________________________________________________________________________
2/12
Request coding
2.3
Requests to access standard objects
The UNI-TE protocol offers a number of services for read/write access to the following
types of data :
internal bit,
system bit,
internal word,
system word,
floating point object,
constant word,
Grafcet data.
2.3-1 Read an internal bit

Request name : READ_INTERNAL_BIT.
This service is used to read the value of an internal bit.
Request format
Request Category Internal
code
code
bit
00H
07
number
1 byte
1 byte
1 word
Internal bit number
: number of bit to read.
Confirmation format
Confirmation
30H
Value
Forcing
1 byte
8-bit table
8-bit table
Value
: value of read bit (located in the table in the ((bit n) MOD8) position)
Forcing
: indicates forcing of the read bit.
___________________________________________________________________________
2/13
2.3-2 Write an internal bit

Request name : WRITE_INTERNAL_BIT.
This service is used to write the value of an internal bit.
Request format
code
code
bit
10H
07
number
1 byte
1 byte
1 word
Value
1 byte
Internal bit number : number of bit to write

Value : 0 or 1.
Confirmation format
Request
code
FEH
1 byte
(No additional data in the response).
___________________________________________________________________________
2/14
Request coding
2.3-3 Read a system bit

Request name : READ_SYSTEM_BIT.
This service is used to read the value of a system bit.
Request format
Request Category System
code
code
bit
01H
07
number
1 byte
1 byte
1 word
System bit number : system bit number to read.

Confirmation format
Confirmation
31H
User
data
1 byte
8-bit table
Value : value of read bit (located in the table in the ((bit n) MOD 8) position).
___________________________________________________________________________
2/15
2.3-4 Write a system bit

Request name : WRITE_SYSTEM_BIT.
This service is used to write the value of a system bit.
Request format
code
code
bit
11H
07
number
1 byte
1 byte
1 word
Value
1 byte
Internal bit number : bit number to write

Value
: 0 or 1.
Confirmation format
Confirmation
FEH
1 byte
___________________________________________________________________________
2/16
Request coding
2.3-5 Read an internal word

Request name : READ_INTERNAL_WORD.
This service is used to read the value of an internal word.
Request format
code
code
word
04H
07
number
1 byte
1 byte
1 word
Internal word number : number of word to read.

Confirmation format
Confirmation
34H
Value
1 byte
1 word
Value : value of read word.
___________________________________________________________________________
2/17
2.3-6 Write an internal word

Request name : WRITE_INTERNAL_WORD.
This service is used to write the value of an internal word.
Request format
code
code
word
14H
07
number
1 byte
1 byte
1 word
Value
1 word
Internal word number : number of word to write

Value : value to write in word.
Confirmation format
Confirmation
FEH
1 byte
___________________________________________________________________________
2/18
Request coding
2.3-7 Read a system word

Request name : READ_SYSTEM_WORD.
This service is used to read the value of a system word.
Request format
code
code
word
06H
07
number
1 byte
1 byte
1 word
Internal word number : number of word to read.

Confirmation format
Confirmation
36H
Value
1 byte
1 word
Value : value of read word.
___________________________________________________________________________
2/19
2.3-8 Write a system word

Request name : WRITE_SYSTEM_WORD.
This service is used to write the value of a system word.
Request format
code
code
word
15H
07
number
1 byte
1 byte
1 word
Value
1 word
Internal word number : number of word to write

Value : value to write in the word.
Confirmation format
Confirmation
FEH
1 byte
___________________________________________________________________________
2/20
Request coding
2.3-9 Read a constant word

Request name : READ_CONSTANT_WORD.
This service is used to read the value of a constant word.
Request format
Request Category Constant
code
code
word
05H
07
number
1 byte
1 byte
1 word
Constant word number : number of word to read.

Confirmation format
Confirmation
35H
Value
1 byte
1 word
Value : value of the read word.
___________________________________________________________________________
2/21
2.3-10 Force an internal bit

Request name : FORCE_INTERNAL_BIT.
This service is used to force an internal bit.
Request format
Request Category
Internal bit Type of
code
code
number
forcing
1BH
07
1 byte
1 byte
1 word
1 byte
Value
1 byte
Internal bit number
: number of internal bit to force
Type of forcing
: 0 if unforcing and writing

1 if forcing
Value
: forcing value (0 or 1).
Confirmation format
Confirmation
FEH
1 byte
___________________________________________________________________________
2/22
Request coding
2.3-11 Read Grafcet step status

Request name : READ_GRAFCET_BIT.
This service is used to read the status of 127 steps of a Grafcet chart.
Request format
Request Category
code
code
2AH
07
1 byte
1 byte
Bit
interval
1 word
Bit interval : the read operation applies to an interval of 127 steps defined as follows :
0=
1=
2=
3=
4=
5=
6=
7=
interval [X0..X127]
interval [X128..X255]
Confirmation format
Confirmation
5AH
1 byte
Value
127-bit
table
___________________________________________________________________________
2/23
Values : step values (0 : inactive or not managed, 1 : active)
Xi+7
Xi
15
16 bytes
Xi+127
Xi+120
127
120
___________________________________________________________________________
2/24
Request coding
2.4
Requests to access the objects of an I/O module
Use of these requests requires a knowledge of the general rules for I/O addressing.
These rules are described in sections 3 and 4, part A.
Summary
The address is coded in variable length byte table. The first byte specifies the table
length, bytes 1 and 2 specify the rack number (byte 1) and the module number on the
rack (byte 2).
Bytes
Length Rack Num Rod Num

<------------------------------------ Access route ---------------------------------------->
This format is used for all requests to access I/O objects.

Examples :
Address 4.0 is coded on 4 bytes : 3 0 4 0
The first indicates the length of the significant address.
Address 104.0 is also coded on 4 bytes : 3 1 4 0
The rack number is placed on byte 1.
Address \0.2.6\4.0 is coded on 6 bytes : 6 0 0 2 6 4 0
%I4.0
%I104.0
4
6
%I\0.2.6\4.0
___________________________________________________________________________
2/25
2.4-1 Read the memory image of a simple discrete module

Request name : READ_DIGITAL_MODULE_IMAGE.
This service is used to read the image bits of the I/O of a simple discrete module.
This service does not exist in version 1.1.
Request Category
code
code
Extension
07
49H
1 byte
1 byte
1 word
Module
address
Type of values
to read
Byte
table
8-bit
table
Extension
: reserved for future developments. Its default value is 0
Address module
: address of the module concerned according to the format

described in the introduction of section 2.4
Type of value to read
: gives the list of data to be given in the response.
bit 7
bit 0
D
FI
1 I/O value
1 log
1 local forcing
1 fallback value
1 I/O fault
___________________________________________________________________________
2/26
Request coding

ConfirmConfirmation Extension
ation
79H
1 byte
. . .
1 byte
1 byte
Module
status
. . .
B
1 byte
Module
class
Type of
values read
1 byte
8-bit table
Number
Condiof I/O
tional
channels parameters
1 byte
Bit
string
Extension
: identical to field which has the same name in the question
Confirmation
: 0 if the result is positive

1 if module address is out of range
2 if module has not been configured in a PLC which has
been configured
3 if input parameter is incorrect
Status module
: 0 if internal fault
1 if operating fault
2 if terminal block fault
3 if module is performing self-tests
4 (reserved)
5 if configuration fault
6 if module is absent
7 if support module fault
Module class
: 0 if module with fixed configuration

1 if module configurable
Type of read value
: identical to "type of values to read" field in the question
I/O channel number
: number of I/O of the module
Conditional parameters (depending on "type de value to read" field) :

Module
structure
I/O
value
Log
Forcing
Fallback
Channel
fault
Bit
string
Bit
string
Bit
string
Bit
string
Bit
string
Bit
string
___________________________________________________________________________
2/27
Module structure
: representation of module I/O

(0 : inputs, 1 : outputs)
Module with 8 inputs/4 outputs
Outputs
Not significant
Inputs
Length = 12
Byte 0
I/O value
0
7
Byte 1
0 0 0
0 15
1
8
Byte 2
: value of module input or output bits
Log
: previous value of the module I/O
Forcing
: indicates the forced channels of the module (bit i = 1 if channel i is

forced)
Fallback state
: fallback value of the module I/O
Fault
: indicates module channels which are faulty (bit i : 1 if channel i is

faulty),
also indicates that the module is in fallback state.
___________________________________________________________________________
2/28
Request coding
2.4-2 Write memory image bit of a simple discrete module

Request name : WRITE_DIGITAL_MODULE_IMAGE.
This service is used to write the image bits of the I/O of a discrete module and can also
force I/O discrete channels. This service does not exist in version 1.1.
Request Category
code
code
4AH
07
1 byte
1 byte
. . .
Address
module
Number
of operations
Byte table
1 byte
Type of
operation
Channel
number
8-bit table
1 byte
. . .
Type of Channel
channel
value
1 byte
1 byte
Extension
Address Module
: address of the module concerned according to the format

described in the introduction of section 2.4
Number of operations : number of operations described in remainder of request

Type of operation
0
1
2
254
255
if no specific action
if forcing is requested
if unforcing is requested
I/O globally reset
I/O globally unforced
Channel number
: number of the channel to which the operation applies
Type of channel
Channel value
: 0 or 1 (least significant bit, the other bits are not significant).
0 if input
1 if output (least significant bit)
___________________________________________________________________________
2/29
ConfirmConfirmation
Extension
ation
7AH
1 byte
1 byte
1 byte
Extension
: identical to field which has the same name in the request
Confirmation
: 0
1
2
3
4
if result is positive
if address is out of range
if module is not configured
if input parameter is : "correct"
if result is partially correct.
___________________________________________________________________________
2/30
Request coding
2.4-3 Read the status of a module

Request name : READ_STATUS_MODULE.
This service is used to identify the physical structure and complete status of a device.
Request Category
code
code
44H
07
1 byte
1 byte
Module address
Byte table
Module address : address of the module concerned according to the format

described in the introduction of section 2.4.
If module is configured
<------------------------------------------------------>
ConfirmResponse
ation
format
74H
1 byte
1 byte
Confirmation
8-bit
table
Product Application Product

range
type
type
1 byte
1 byte
1 byte
Cat.
reference
. . .
1 byte
If module is present
<----------------------------------------------------------------------------------------------->
. . .
Device Application Product

type
type
type
Cat.
reference
Module
status
Module
version
1 byte
1 byte
16-bit table
1 byte
1 byte
1 byte
. . .
___________________________________________________________________________
2/31
If module is present
If sub-module exists
If sub-module is configured
<--------------------------------><--------------------------------><--------------------------------------->
. . .
Status of
indicator
lamps
Sub- Sub-module
Application Product
module channel Confirmation
type
type
number number
8-bit
table
1 byte
1 byte
8-bit
table
1 byte
1 byte
Cat.
reference
. . .
1 byte
If sub-module is present
<--------------------------------------------------------------------------------->
. . .
SubApplication Product Catalogue

module
type
type
reference
version
1 byte
1 byte
1 byte
1 byte
Sub-module
status
8-bit table
Note :
The part of the response relating to the sub-assemblies appears as many times as there are
sub-modules.
Response format
: 0 if identification of the basic modules and the

sub-modules is described
1 if only the basic module identification is described
2 if no identification is supplied
Confirmation
: 0 if module is absent and not configured

1 if module is present and not configured
2 if module is absent and configured
3 if module is present and configured
Product range
: identifies the product range to which the product

belongs
Basic module application type : for the value of this field, refer to the specific product
documentation
Product type
: for the value of this field, refer to the specific product

documentation
Catalogue reference
: describes the device in the product type : for the

value of this field, refer to the specific product
documentation.
___________________________________________________________________________
2/32
Request coding
Sub-module status :
Type of fault
Bit n
Comment
Internal fault
:0
Hardware failure
Operating fault
:1
Terminal block fault
:2
Terminal block absent
Self-test
:3
Module performing self-tests
Reserved
:4
Conf. fault
:5
Modules incompatible
Absent
:6
Module absent or powered down
Down
:7
One of the modules supported is faulty
___________________________________________________________________________
2/33
2.4-4 Read the objects of an I/O channel

Request name : READ_IO_CHANNEL.
This service is used to read channel level I/O objects (eg : configuration data, parameter
entry, command, status, etc). This service does not exist in version V1.1.
x (Number of operations)
<----------------------------------------->
Request Category
code
code
43H
07
1 byte
1 byte
Number of Type of
operatdata to
tions
read
Channel
address
Byte table
1 byte
1 word
Number
Start
number
1 word
1 word
Channel address
: address of the channel (rack, module, channel)

(see format described in introduction of section 2.4)
Number of operations
: Number of read operations requested in the request
Type of data to read
Number
: number of objects to read (not used for periodic data)
Start number
: number of first object to read (not used for periodic data).
0
1
2
3
4
5
6
7
8
9
11
14
255
:
:
:
:
:
:
:
:
:
:
:
:
:
periodic data
discrete input
discrete output
numerical input
numerical output
internal word standard zone
channel status
channel parameter entry
command data (fallback states, reset, etc)
configuration data (transmission, parity, etc)
specific to backup operations
initial parameters
access to system data
___________________________________________________________________________
2/34
Request coding

Confirm- General
ation
confirm73H
ation
1 byte
1 byte
Number of
Operation Specific
Channel
Type of
operations Continue
confirm- operation
fault
operation
performed
ation
zone
1 byte
1 byte
1 byte
1 word
1 byte
General confirmation
: 0 if result is positive
1 if module or channel is not configured
3 if input parameters are out of range
4 if result is partly positive
Channel fault
: 1 if there is a blocking fault on the channel, or a

configuration error.
performed
: number of operations completely or partially

performed
Continue
: indicates that the response is incomplete (when

amount of data to be transmitted is too great)
Type of operation
: field which has the same meaning as "type of data to

read" field in the request
Operation confirmation
: 0 if result is positive
2 if there is an exchange error
3 if input parameters are out of range
4 if objects cannot be accessed
6 if module is not compatible (discrete)
7 if exchange is in progress
9 if operation is not possible.
___________________________________________________________________________
2/35
Zone specific
to the operation
1st case : reading periodic data

Size
of an
element
Value of discrete
inputs
1 byte
Byte table
Value of discrete
outputs
Byte table
Value of
numerical
inputs
Value of
numerical
outputs
Byte table
Byte table
2nd case : reading other data (command, configuration, etc)

Data
value
Word table
3rd case : backup : no specific field
4th case : reading the system

Descriptor
address
2 word
table
Descriptor address gives access to the system zones.
___________________________________________________________________________
2/36
Request coding
2.4-5 Write the objects of an I/O channel

Request name : WRITE_IO_CHANNEL.
This service is used to write the value of the objects of an I/O channel. This service does
not exist in version V1.1.
Operating parameters
<------------------------------------->
Request Category
code
code
48H
07
1 byte
Channel address
1 byte
Byte table
Number of Type of
operations object
1 byte
1 byte
Type of Object n Number of

write
to
objects to
operation modify
modify
1 byte
1 word
1 word
Value
1 word
Channel address
Type of object
: type of object to write

1 : discrete input
2 : discrete output
3 : digital input
4 : digital output
7 : parameter entry data
8 : command data
10 : reconfiguration operation
12 : restore operation
13 : deconfiguration operation
Type of operation
: specifies the operation to perform :

0 : no specific operation (write the value)
1 : forcing operation
2 : unforcing operation
Object number
to modify
: number of first object to write
Number of objects
to modify
: number of consecutive objects to modify
Value
: - binary data is coded on a byte (low order),

- numerical data is coded on one word.
___________________________________________________________________________
2/37

List
<------------>
Confirm- General
ation
confirm78H
ation
1 byte
1 byte
: result of the operation (identical to the field which has the

same name in the READ_IO_CHANNEL confirmation).
___________________________________________________________________________
2/38
Request coding
2.5
Requests to access generic objects
The UNI-TE protocol offers read/write services on the following types of object :
application (internal word, internal bit, timer, counter),
system (configuration data),

network management (error counter, routing data),
device management (configuration data for a functional unit, etc).
2.5-1 Identification of objects

These objects are identified via a class identifier which has the following format :
<---2 byte format--->
Segment
n
1 byte
Type
Address
1 byte 1 or 2 words
or
<----------5 byte format----------->
Segment
n
Family
1 byte
1 word
Type
Address
1 word 1 or 2 words
The segment number determines the choice of format : 2 or 5 bytes.

Segment n
: < 100
100
Type
: class of object to access in the given segment (1 byte)

(see section 3.4 in appendix)
Family, type
: class of object to access in the given segment (2 bytes)

(see section 3.4 in appendix).
identification on 5 bytes
identification on 2 bytes
This data is specific to each device. For the various values, refer to specific product
documentation.
Address
: address of the object to access.
___________________________________________________________________________
2/39
2.5-2 Access parameters

For each operation to read or write an object, the type of access for that object is defined
in the following parameters :
1st case : continuous total access

Type of
access
255
Quantity
1 byte
1 byte
Data
for write only
Quantity : number of consecutive elements to access

Data
: data to write (for write operation).
2nd case : single partial access

Type of
access
2
Element
number
1 byte
1 byte
Data
for write only
Element number
: number of element to access
3rd case : continuous partial access

Type of
access
0
1 byte
Element Number
number of element
1 word
Data
1 word
if written
Element number
: number of 1st element to access
Number of element : number of the element to access.
___________________________________________________________________________
2/40
Request coding
4th case : dispersed partial access

<-----x (number of elements)---->
Type of
access
1
Number of
elements
Element
number
1 byte
Table
1 byte
Table Number of
position stations
1 word
Data
1 word
<-------------------------> if write
only exists in an
element table
Number of elements : number of elements to access.

For each element the following is defined :
the number of the element to access.
If this element is a table, the following are defined :
position to access in the table,
number of consecutive positions to access.
___________________________________________________________________________
2/41
2.5-3 Read an object

This number is used to read one or more consecutive objects of the same type.
Request Category
Type of
code
code
Segment
object
36H
07
1 byte
1 byte
Segment
1 byte
1 byte
Address Quantity
1 word
1 word
: specifies the addressing mode of objects to read (eg : internal bit

segment, function block segment, system object segment, etc)
Type of object: type of object to read (eg : 16 or 32-bit integer, internal bits, etc)
Address
: address of object in segment
Quantity
: number of objects of the same type to read

Confirmation
66H
1 byte
Type of
object
1 byte
Data
Byte table
Type of object: identical meaning to the field which has the same name in the request
Data
: values of read objects.
___________________________________________________________________________
2/42
Request coding
List of objects which can be accessed :

System
Segment
Family
Type
H'06' Network
management
Communication layer
0x31 UNI-TELWAY
event-triggered data
Communication object
01 UNI-TELWAY
event-triggered data
H'32' PL7 objects
1 : Common words
byte 0 : Network n
byte 1 : Station n
User
Segment
Type
System memory
1 : system byte
H'64'
Bit space
5 : internal bit
6 : system bit
85 : 32-bit address %M (1)
8x : 32-bit address .....
%M
%S
H'68'
Internal data space
6:
7:
8:
9:
A:
B:
%MB
%MW
%MDW
internal byte
internal word
double word
reserved
floating point single word
floating point double word
%MF
%MDF
H'69'
Constant data space
7 : constant word
8 : constant double word
%KW
%KDW
H'6A'
System data space
7 : system word
8 : system double word
%SM
%SDW
H'80'
TSX 7 / TSX 37 system
1 : real-time clock
H'81'
PL7 function blocks
0 : Text block
1 : PL7 timer
2 : PL7M timer
3 : Counter
4 : Drum controller
5 : Monostable
6 : Word register
TSX 07 objects
7 : Shift bit register
8 : Step counter
9 : PWM (Pulse Width Modulation)
A : PLS pulse
B : Fast counter
C : Message
H'82' to H'96'
%T
%TM
%C
%DR
%MN
%R
%SBR
%SC
%PWM
%PLS
%FC
%MSG
Reserved
___________________________________________________________________________
2/43
2.5-4 Write an object

This service is used to write one or more consecutive objects of the same type.
Request Category
Type of
code
code
Segment
object
37H
07
1 byte
1 byte
Segment
1 byte
1 byte
Address Quantity
1 word
1 word
Data
Byte table
: specifies the addressing mode of the objects to read (eg : internal bit
segment, function block segment, system object segment, etc)
Type of object: type of object to read (eg : 16 or 32-bit integer, internal bits, etc)
Address
: address of object in segment
Quantity
: number of objects of the same type to write
Data
: values to write.

Confirmation
FEH
1 byte
___________________________________________________________________________
2/44
Request coding
2.5-5 Read a generic object

Request name : READ_GENERIC_OBJECT.
This service is used to read all or part of a structured object or single objects. This service
does not exist in version 1.1.
Request Category
code
code
Object identification Access parameters
82H
07
1 byte
1 byte
from 3 to 9 bytes
from 2 to x bytes
Object identification : see section 2.5-1

Access parameters : see section 2.5-2.
Total access
Confirmation
B2H
Type
1 byte
1 word
List
<------------------------->
Address Quantity
1 word
1 word
Status
Values
1 byte
Byte table
Partial access
List
<------------------------->
Confirmation
B2H
Type
Address
Size
Status
Values
1 byte
1 word
1 word
1 word
1 byte
Byte table
Type
: type of access specified in the question (access parameters)
Address : address specified in the question (object identification)

Quantity : number of read elements
Size
: number of returned bytes (corresponding to all the status and values).
___________________________________________________________________________
2/45
Status
: 00 : read correctly
02 : element does not exist, object out of range
03 : range error in a table
04 : application does not exist
05 : insufficient resources
07 : incorrect parameter
08 : object temporarily inaccessible (real-time clock for example)
Values
: only present if status = 00. its coding depends on the type of object or
element read.
___________________________________________________________________________
2/46
Request coding
2.5-6 Write a generic object

Request name : WRITE_GENERIC_OBJECT.
This service is used to write all or part of a structured object or single objects.
Request Category
code
code
Object identification Access parameters
83H
07
1 byte
1 byte
from 3 to 9 bytes
from 2 to x bytes
Object identification : See section 2.5-1

Access parameters : See section 2.5-2.
Total access
Confirmation
B3H
Type
1 byte
1 word
Address Quantity
1 word
1 word
Partial access
Status
1 byte
List
<------------>
Confirmation
B3H
Type
Address
Size
Status
1 byte
1 word
1 word
1 word
1 byte
Type
: type of access specified in the question (access parameters)
Address : address specified in the question (object identification).
___________________________________________________________________________
2/47
Quantity : number of elements written
Size
: number of bytes written (corresponds to all statuses)
Status
: 00 : written correctly
01 : element write-protected
02 : element does not exist, object out of range
03 : range error in a table
04 : application does not exist
05 : insufficient resources
06 : data out of range
07 : incorrect parameter.
___________________________________________________________________________
2/48
Request coding
2.5-7 Read a list of objects

Request name : READ_OBJECT_LIST.
This service is used to read different types of object within the same request. This service
does not exist in version 1.1.
Summary
A UNI-TE V2.0 request is limited to 128 or 256 bytes (or more, depending on the class),
depending on the number and type of objects, the response size can exceed 128 or 256
bytes, in which case the confirmation indicates an incomplete response.
x (number of operations)
<----------------------------------------------------->
Request Category
Number of
code
code
Extension opera- Object identification Access parameters
38H
07
tions
1 byte
1 byte
Extension
1 byte
1 byte
from 3 to 9
from 2 to x
Number of operations: number of read operations to perform

Object identification : See section 2.5-1
Access parameters : See section 2.5-2.
Total access
<------------------------------------------------------------------->
ConfirmNumber
Confirmation
Extension
of
ation
68H
results
1 byte
1 byte
1 byte
1 byte
Status
1 byte
Partial access
1 byte
Status
List of
values
. . .
Byte
table
x (number of results)
<------------------------------------------------------------------->
ConfirmNumber
Confirmation
Extension
of
ation
68H
results
1 byte
List of
values
1 byte
1 byte
Status
Value
1 byte
Byte
table
Status
Value
. . .
___________________________________________________________________________
2/49
Extension
: identical to field which has the same name as in the request
Confirmation
: 0 : positive result
1 : positive result but incomplete response
2 : system not configured
3 : incorrect syntax
B
Number of results
: number of read operations performed
Status
: 00 : correct read operation

01 : element read-protected
02 : element does not exist, or out of range
03 : ...
A single status is supplied when there is total access, one status per element read is
supplied when there is partial access.
Values
: value of the read variable (if status = 00).
___________________________________________________________________________
2/50
Request coding
2.5-8 Write a list of objects

Request name : WRITE_OBJECT_LIST.
This service is used to write different types of object within the same request. This
service does not exist in version 1.1.
<----------------------------------------------------->
Request Category
Number of
Access parameters
code
code
Extension opera- Object identification
and values
39H
07
tions
1 byte
1 byte
1 byte
1 byte
from 3 to 9 bytes
from 2 to x bytes
These fields have an identical meaning to the fields which have the same names defined
in the READ_OBJECT_LIST request (the number of operations concerns the number
of write operations to perform).
<---------------------------------------->
ConfirmNumber
Confirmation
Extension
of
ation
results
69H
1 byte
1 byte
1 byte
1 byte
Status
Status
1 byte
1 byte
. . .
Extension
Confirmation
: 0 : positive result
1 : one or more operations have not been performed
2 : system not configured
3 : incorrect syntax
Number of results
: Number of write operations performed
Status
: each write operation gives rise to a status :

00 : correct operation
01 : object inaccessible in write
02 : object out of range
03 : object reserved
04 : object not configured.
___________________________________________________________________________
2/51
2.5-9 Action on an object

Request name : ACTION_GENERIC_OBJECT.
This request is used to manage operating modes, activate particular communication

operations, manage Grafcet steps, etc.
Request Category
code
code
9FH
07
1 byte
1 byte
Action
Action
code
sub-code
1 byte
1 byte
Object identification
Parameter
from 3 to 9 bytes
Word table
Action code :
Action code
Meaning
0 to 255 specific to a class of object
Segment 150, type : 1 /* character mode */

101 : character transmission
102 : character reception
103 : character transmission/reception
104 : reception with reset to zero
Segment 150, type : 2 /* modbus */
xx : modbus function code
action s/code = fonction s/code
Segment 150, type : 2 /* grafcet step */
100 : blocking
101 : unblocking
102 : forcing
103 : unforcing
104 : set
105 : reset
___________________________________________________________________________
2/52
Request coding
Action sub-code
: depends on the action code
: see section 2.5.1
Parameter
: depends on the type of action.

Confirm- General
ation
confirmCFH
ation
1 byte
1 word
Specific
confirmation
Specific
parameters
1 word
Word table
: 0 : action completed
1 : action not completed
2 : action partially completed
Specific confirmation
: Confirmation specific to the action
Specific parameters
: these parameters are dependent upon the operation

and the object to which it applies.
___________________________________________________________________________
2/53
2.6
Operating mode management requests
The UNI-TE protocol provides services for controlling CPU operating modes via orders
such as RUN, STOP or INIT.
2.6-1 Launching an application or task

Request name : RUN.
This service can start the execution of one or more tasks of a processor.
<-----------------------c-->
Request Category
code
code
Segment
24H
07
1 byte
1 byte
1 byte
Type
Execution
parameter
1 byte
Byte table
Segment and type
: identifies the task to activate (the absence of this parameter

indicates activation of all tasks in an application)
Execution parameters
: describes the parameters required to activate the task.
Confirmation format
Confirmation
FEH

Request Category
code
code
24H
07
1 byte
1 byte
Note :
These two versions are compatible.
___________________________________________________________________________
2/54
Request coding
2.6-2 Stopping an application or task

Request name : STOP.
This service is used to stop the execution of one or more tasks of a processor.
One task
<------------------------c->
Request Category
code
code
Segment
25H
07
1 byte
1 byte
1 byte
Type
1 byte
Segment and type : identifies the task to activate (the absence of this parameter
indicates stopping of all tasks in an application).
Confirmation format
Confirmation
FEH

Request Category
code
code
25H
07
1 byte
1 byte
Note :
The two versions are compatible.
___________________________________________________________________________
2/55
2.6-3 Initialization
Request name : INIT.
This service is used to trigger a warm/cold restart. This service does not exist in
version 1.1.
Request Category Type of
code
code
initia33H
07
lization
1 byte
1 byte
1 word
Type of initialization : type of restart to activate :

0 : cold restarts for PLC
other : specific to other devices.
ConfirmConfirmation
ation
63H
1 byte
1 byte
Confirmation :
Initialization
Config. absent.
Other errors
: 0
: 1
: 2.
___________________________________________________________________________
2/56
Request coding
2.7
Data transfer requests
The UNI-TE protocol offers services for remotely uploading or downloading data
between devices, as well as the transfer or comparison of data within a device.
Downloading and backing up data follow the sequence shown below :
CLIENT
SERVER
Open_Download.rq
Open_Download.rp
Write_Download.rq
Write_Download.rp
Write_Download.rq
Write_Download.rp
Start
downloading
Downloading of
first segment
Downloading of
segment n
Close_Download.rq
End of downloading
Close_Download.rp
___________________________________________________________________________
2/57
2.7-1 Start downloading

Request name : OPEN_DOWNLOAD.
This service is used to initialize a data downloading phase.
Request format
Request Category
code
code
07
3AH
1 byte
1 byte
Optional
<------------>
File
identification
Extension
code
File
name
Byte table
1 byte
Character
string
File identification
: reference of the file to download

This parameter is specific to a type of equipment. Refer to the
product documentation for the construction rules
Extension code
: identification extension of file to download, it depends on the

device concerned (0 : for PLC)
File name
: name of file to download.
Confirmation format
Confirmation
6AH
Status
1 byte
1 byte
Status : 16#00 : OK
16#0C : CPU status incompatible with downloading.
___________________________________________________________________________
2/58
Request coding
2.7-2 Downloading a segment

Request name : WRITE_DOWNLOAD.
This service is used to download a data segment.
Request format
x length of segment
<---------------------------------------->
Request Category
Segment Segment
code
code
number
length
3BH
07
1 byte
1 byte
1 word
Segment number
1 word
Data
Data
1 byte
1 byte
: 1st segment
2nd segment
.
.
.
nth segment
. . .
: 1
: 2
: n
Segment length
: length of data which make up the segment
Data
: list of data in the segment.
Confirmation format
Confirmation
6BH
Status
Segment
number
1 byte
1 byte
1 word
Status
: 16#00
16#0D
16#19
16#20
:
:
:
:
OK
Incorrect data
Sequencing error
Cannot write or reserved file
Segment number
: identical to field which has the same name in the

question.
___________________________________________________________________________
2/59
2.7-3 Ending a downloading sequence

Request name : CLOSE_DOWNLOAD.
This service is used to end a downloading sequence.
Request format
Request Category
code
code
3CH
07
1 byte
1 byte
Confirmation format
Confirmation
6CH
Status
1 byte
1 byte
Status :
16#00 : OK
16#0E : Error.
___________________________________________________________________________
2/60
Request coding
2.7-4 Launching a backup sequence

Request name : OPEN_UPLOAD.
This service is used to initialize a data uploading sequence (or backup).
Request format
Request Category
code
code
3DH
07
1 byte
1 byte
Optional
<------------>
File
identification
Byte table
File identification
Maximum
segment
size
1 word
: reference of the file to back up (refer to the documentation

for the product concerned for the construction rules)
Maximum segment size : size of a backup segment (optional, the default size is
122 bytes).
Confirmation format
Confirmation
6DH
Status
1 byte
1 byte
Status : 16#00 : OK
16#05 : Uploading impossible :
invalid station
incorrect identification
no space available
16#1F : Protected application.
___________________________________________________________________________
2/61
2.7-5 Backing up a segment

Request name : READ_UPLOAD.
This service is used to read the contents of a file segment while it is being backed up.
Request format
Request Category
Segment
code
code
number
3EH
07
1 byte
1 byte
1 word
Segment number
: 1st segment
2nd segment
.
.
.
nth segment
: 1
: 2
: n.
Confirmation format
Confirmation
6EH
Status
1 byte
1 byte
Segment Segment
number
length
1 word
1 word
Data
Bytes table
Status
: 16#00
16#19
16#0F
16#20
:
:
:
:
OK
Sequencing error
OK end of file
Uploading not performed :
read error
Segment number
: identical to field which has the same name in the question
Segment length
: size of transmitted data
Data
: transmitted data.
___________________________________________________________________________
2/62
Request coding
2.7-6 Ending a backup

Request name : CLOSE_UPLOAD.
This service is used to end a backup sequence.
Request format
Request Category
code
code
3FH
07
1 byte
1 byte
Confirmation format
Confirmation
6FH
Status
1 byte
1 byte
Status :
16#00 : OK
16#0E : Error.
___________________________________________________________________________
2/63
2.7-7 Memory transfer and comparison

Request name : BACKUP.
This service is used to compare memory zones or save data from one memory zone to
another. This service does not exist in version 1.1.
only if the type of action = 5 or 6
<---------------------------------------->
Request Category
Type of
code
code
action
45H
07
1 byte
1 byte
1 byte
Source
Target
Number
zone start zone start
of bytes
number address
one 32-bit one 32-bit
word
word
1 byte
Type of action
: 1 : copy PLC RAM to EPROM

2 : copy PLC RAM to EPROM with
protection
3 : copy EPROM to PLC RAM
4 : compare PLC RAM and EPROM
5 : copy memory
6 : compare memory
Source zone start address
: address in the source memory of the start of the

zone to copy or compare
Target zone start address
: address in the target memory of the start of the

zone to copy or compare
Number of bytes
: number of bytes to copy or compare from the

source zone to the target zone.

Confirmation
75H
Status
1 byte
1 byte
Status
: 0 : operation completed successfully

1 : incorrect copying operation
2 : comparison operation terminated on an
error
3 : comparison operation impossible
4 : source not configured
___________________________________________________________________________
2/64
Request coding
2.8
Semaphore management request
The UNI-TE protocol offers a semaphore management mechanism which protects the
server, to avoid conflicting access during a critical period. This reservation mechanism
is provided by 3 services :
establish a reservation,
hold a reservation,
release a reservation.
2.8-1 Reservation
Request name : RESERVE.
This service enables a client to totally or partially reserve the functions of a server.
Request format
Example of an object class which can be identified by its segment and type
Request Category Identificode
code
cation
07
type
1DH
Segment
Type
1 byte
1 byte
1 byte

code
cation
1DH
07
type
Name
Range
1 byte
1 byte
Range
Another example
1 byte
1 byte
1 byte
Confirmation format
Confirmation
FEH
___________________________________________________________________________
2/65
2.8-2 Release
Request name : RELEASE.
This service enables a client to release the reserved server
Request format
Example of an object class which can be identified via its segment and type
Request Category
code
code
1EH
07
1 byte
Identification
type
Segment
Type
Table
1 byte
1 byte
1 byte
Another example
code
cation
1EH
07
type
1 byte
1 byte
Name
1 byte
Confirmation format
Confirmation
FEH
___________________________________________________________________________
2/66
Request coding
2.8-3 Hold a reservation

Request name : I_AM_ALIVE.
This service is essential for maintaining the reservation of the server by the client.
Request format
Request Category
Reserver
code
code
address
2DH
07
1 byte
1 byte
1 word
Reserver address
: network address of the reserving entity

(16#FFFF if the holding entity is identical to the reserving
entity).
Confirmation format
Confirmation
FEH
___________________________________________________________________________
2/67
___________________________________________________________________________
2/68
Section 33
Appendix
3 Appendix
3.1
Heading
Name of request
General use
General use
General use
General use
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
Standard objects
I/O modules
I/O modules
I/O modules
I/O modules
I/O modules
Generic objects
Generic objects
Generic objects
Generic objects
Generic objects
List of objects
List of objects
Operating modes
Operating modes
Operating modes
Data transfer
Data transfer
Data transfer
Data transfer
Data transfer
Data transfer
Data transfer
Semaphore
Semaphore
Semaphore
IDENTIFICATION
READ_CPU
PROTOCOL_VERSION
MIRROR
READ_INTERNAL_BIT
WRITE_INTERNAL_BIT
READ_SYSTEM_BIT
WRITE_SYSTEM_BIT
READ_INTERNAL_WORD
WRITE_INTERNAL_WORD
READ_SYSTEM_WORD
WRITE_SYSTEM_WORD
READ-CONSTANT-WORD
FORCE-INTERNAL-BIT
READ-GRAFCET-BIT
READ_DIGITAL_MODULE_IMAGE
WRITE_DIGITAL_MODULE_IMAGE
READ_STATUS_MODULE
READ_IO_CHANNEL
WRITE_IO_CHANNEL
READ_GENERIC_OBJECT
WRITE_GENERIC_OBJECT
READ_OBJECT
WRITE_OBJECT
ACTION_GENERIC_OBJECT
READ_OBJECT_LIST
WRITE_OBJECT_LIST
RUN
STOP
INIT
OPEN_DOWNLOAD
WRITE_DOWNLOAD
CLOSE_DOWNLOAD
OPEN_UPLOAD
READ_UPLOAD
CLOSE_UPLOAD
BACKUP
RESERVE
RELEASE
I_AM_ALIVE
Request
code
Confirmation
code
0FH
4FH
30H
FAH
00H
10H
01H
11H
04H
14H
06H
15H
05H
1BH
2AH
49H
4AH
44H
43H
48H
82H
83H
36H
37H
9FH
38H
39H
24H
25H
33H
3AH
3BH
3CH
3DH
3EH
3FH
45H
1DH
1EH
2DH
3FH
7FH
60H
FBH
30H
FEH
31H
FEH
34H
FEH
36H
FEH
35H
FEH
5AH
79H
7AH
74H
73H
78H
B2H
B3H
66H
FEH
CFH
68H
69H
FEH
FEH
63H
6AH
6BH
6CH
6DH
6EH
6FH
75H
FEH
FEH
FEH
___________________________________________________________________________
3/1
3.2
Compatibility between UNI-TE V1.1 and V2.0 requests
Minimum compatibility between UNI-TE V1 and V2 requests is ensured.

All requests giving access to standard objects remain the same.
Equally, requests connected with downloading, operating mode and stopping mode are
totally compatible.
However, certain UNI-TE V2 requests have been redefined and their format is incompatible
with version 1.
In all cases, the changes have been made in such a way that :
either ensures V1.1 - V2.0 compatibility,
or enables devices to recognize the changes and respond, if this case arises, in a
negative way if they do not recognize the service.
A summary table showing this compatibility is given on the next page.
___________________________________________________________________________
3/2
Appendix
UNI-TE V1.1
Compatibility
Comments
General use
(Identification
Mirror
Protocol Version)
Partial
Although it has been modified, the format of

the response to the Identification request
remains compatible in V2
TSX CPU diagnostics is incompatible
Standard objects
(bits, word, etc)
Total
Function blocks can be accessed via object

requests
I/O objects
(IOIM, direct)
Incompatible
Changes to adapt to TSX 37 I/O

system
Generic objects
(total, partial access)
Total
V2.0 requests are enhanced and remain

compatible
Operating mode
(stop, run, init)
Partial
The Stop and Run requests are compatible

The Init request in not compatible
Data transfer
(downloading, backup)
Total
No modification between V1 and V2
Semaphore
Total
No modifications made to total

reservation requests
Comment
Note that the "Protocol Version" request enables the client to ascertain the version
number supported by the server and therefore adapt to the set of requests to use.
Note :
The V2.0 version modifies the role of certain requests and introduces new requests to facilitate
operations previously obtained by sending several V1.1 requests. A table showing the
correspondence between versions V1.1 and V2.0 requests is described in section 3.3.
___________________________________________________________________________
3/3
3.3
Correspondence table between UNI-TE V1.1 and V2.0 requests
Functions
Request code
(hex)
V1.1/V2.0 compatibility
Identification
0F
Compatible on the first 4 fields

of the response
CPU diagnostics
4F
New request in V2.0
Protocol characteristic
30
Compatible on the first fields

(addition in V2.0 of a list of requests
supported by a server)
Communication test
FA
Compatible
Read bit
00
Compatible
Read system bit
01
Compatible
Read word
04
Compatible
Read constant
05
Compatible
Read system word
06
Compatible
Write bit
10
Compatible
Write system bit
11
Compatible
Write word
14
Compatible
Write system word
15
Compatible
Force an internal bit
1B
Compatible
Read Grafcet bit
2A
Compatible
Run
24
Compatible with enhancement in V2.0
Stop
25
Compatible with enhancement in V2.0
Init
33
New request in V2.0
Download data
3A
3B
3C
Compatible
Back up data
3D
3E
3F
Compatible
___________________________________________________________________________
3/4
Appendix
Functions
Request code
(hex)
V1.1/V2.0 compatibility
Memory transfer and

comparison
45
New request in V2.0
Reserve server
1D
Compatible
Release server
1E
Compatible
Hold a reservation
2D
Compatible
Read I/O data of a channel
42
New request in 2.0
Write I/O data of a channel
48
New request in 2.0
Read status of an I/O module
44
New request in 2.0
Read %I, %Q
49
New request in 2.0
Write %I, %Q
4A
New request in 2.0
Read objects
or
Read generic objects
36
or
82
Compatible
Write objects
or
Write generic objects
37
or
83
Compatible
Action on objects
9F
New request in UNI-TE V2.0
Read list of objects
38
New request in 2.0
Write list of objects
39
New request in 2.0
Specific programming
operation *
90
New request in 2.0
Specific debugging
operation *
91
New request in 2.0
* These two functions are reserved for internal use and are not described in this manual.
___________________________________________________________________________
3/5
3.4
Description of various classes of object
For any object which can be partially accessed via "requests/objects"

(Read_Generic_Object and Write_Generic_Object), a description abstracted from its
class must be given.
The remainder of this section deals with these descriptions (nb : in the following tables
the services associated to objects are given : R for Read, W for Write).
3.4-1 Timer objects

Segment = 129, type = 1
Class
: PL7 TIMER
Attribute
Attribute
Attribute
Attribute
Attribute
Constraint
Attribute
Attribute
:
:
:
:
:
:
:
:
Timer type (PL7)

Preset type
Preset value
Value
Time base
(Type = PL7)
R output
D output
Num
Type
Service
1
2
3
4
5
6
7
byte
byte
word
word
byte
byte
byte
R
R
R/W
R/W
R
R
R
Num
Type
Service
1
2
3
4
5
6
byte
byte
word
word
byte
byte
R
R
R/W
R/W
R
R

Class
: IEC TIMER
Attribute
Attribute
Attribute
Attribute
Attribute
Constraint
Attribute
:
:
:
:
:
:
:
Timer type
Preset type
Preset value
Value
Time base
Q.R.D. output
Timer type (TP, TON, TOF)

Preset type
Preset value
Value
Time base
(Type = TP, TON, TOF)
Q output
PL7(1), TP(2), TON(3), TOF(4)

NotModifiable(0), Modifiable(1)
min(0), max(9999)
min(0), max(9999)
1 ms(4), 10 ms(0), 100 ms(1), 1 s (2), 1 min(3)
bit 0 of the byte at 0 = 0
___________________________________________________________________________
3/6
:
:
:
:
:
:
Appendix
3.4-2 Monostable objects

Class
: MONOSTABLE
Attribute
Attribute
Attribute
Attribute
Attribute
:
:
:
:
:
Preset type
Preset value
Value
Time base
R output
Preset type
Preset value
Value
Time base
R output
:
:
:
:
:
Num
Type
Service
1
2
3
4
5
byte
word
word
byte
byte
R
R/W
R/W
R
R
Num
Type
Service
1
2
3
4
5
6
byte
word
word
byte
byte
byte
R
R/W
R/W
R
R
R
min(0), max(9999)
min(0), max(9999)
10 ms(0), 100 ms(1), 1 s (2), 1 min(3)
3.4-3 Counter object

Class
: COUNTER
Attribute
Attribute
Attribute
Attribute
Attribute
Attribute
:
:
:
:
:
:
Preset type
Preset value
Value
E.D.F. output
Preset type
Preset value
Value
E output
D output
F output
:
:
:
:
min(0), max(9999)
min(0), max(9999)
___________________________________________________________________________
3/7
3.4-4 Register objects

Class
: Word REGISTER
Attribute
Attribute
Attribute
Attribute
Attribute
Attribute
:
:
:
:
:
:
Register type
E.F. output
Register type
Register length
Input value
Output value
E output
F output
Num
Type
Service
1
2
3
4
5
6
7
byte
word
word
word
byte
byte
word table
R
R
R/W
R
R
R
R
Num
Type
Service
1
2
3
4
5
6
7
byte
word
word
word
word
byte
word table
R
R
R
R
R
R
R
: LIFO(1), FIFO(0)
: bit 0 of the byte at 0 = 0
3.4-5 Drum controller

Class
: DRUM
Attribute
Attribute
Attribute
Attribute
Attribute
Attribute
Attribute
:
:
:
:
:
:
:
Time base
F output
Time base
Activity time
Number of steps
Number of current step
Status of current step
F output
Status table
: 10 ms(0), 100 ms(1), 1 s (2), 1 min(3)

___________________________________________________________________________
3/8
Appendix
3.4-6 Fast counter object

Class
: FC Fast counter
Attribute
Attribute
Attribute
Attribute
Attribute
Attribute
Attribute
Attribute
Attribute
:
:
:
:
:
:
:
:
:
Fast counter type

Preset type
Preset value
Value
Threshold 0 value
Threshold 1 value
F output
TH0 output
TH1 output
Fast counter type

Preset type
F, THO, TH1 output
Num
Type
Service
1
2
3
4
5
6
7
8
9
byte
byte
word
word
word
word
byte
byte
byte
R
R
R/W
R/W
R/W
R/W
R
R
R
: Counter(0), Frequency meter(1), Up/down counter(2)

: NotModifiable(0), Modifiable(1)
3.4-7 "Pulse width modulation" object

Class
: PWM (Pulse Width Modulation)
Attribute
Attribute
Attribute
Attribute
:
:
:
:
Time base
Preset type
Preset value
Ratio
Time base
Preset type
Preset value
Output ratio at 1
:
:
:
:
Num
Type
Service
1
2
3
4
byte
byte
word
byte
R
R
R/W
R/W
0.2 ms(5), 1 ms(4), 10 ms(0), 100 ms(1), 1 s (2), 1 min(3)

min(0), max(32767)
min(0), max(100)
___________________________________________________________________________
3/9
3.4-8 "Pulse train generation" object

Class
: PLS pulse
Attribute
Attribute
Attribute
Attribute
Attribute
Attribute
:
:
:
:
:
:
Time base
Preset type
Preset value
Number of pulses
Q.D. output
Time base
Preset type
Preset value
Number of pulses
Q output
D output
:
:
:
:
:
Num
Type
Service
1
2
3
4
5
6
byte
byte
word
word
byte
byte
R
R
R/W
R/W
R
R
0,2 ms(5), 1 ms(4), 10 ms(0), 100 ms(1), 1 s (2), 1 min(3)

min(0), max(32767)
min(0), max(32767)
3.4-9 "Shift register" object

Class
: Shift bit REGISTER
Attribute
Attribute
Attribute
: Register length
: Number of current step
: Status of current step
Num
Type
Service
1
2
3
byte
byte
byte
R
R/W
R
Status of current step : bit 0 of the byte at 0 = 0

___________________________________________________________________________
3/10
Appendix
3.4-10 "Step counter" object

Class
: Step REGISTER
Attribute
Attribute
Attribute
: Number of steps
: Number of current step
: Status of current step
Num
Type
Service
1
2
3
byte
byte
byte
R
R/W
R
Num
Type
Service
1
2
3
byte
byte
byte
R
R
R
Status of current step : bit 0 of the byte at 0 = 0

3.4-11 "Operator dialog message" object

Class
: Operator dialog MSG message
Attribute
Attribute
Attribute
: Message type
: E output
: D output
Message type
E.D. output
: XBT/CCX(0)
___________________________________________________________________________
3/11
3.4-12 Real-time clock object

The real-time clock object which can be accessed via the UNI-TE protocol permits
several formats :
Read current date and time in BCD format (9 byte table).

Bytes
<----------------------------------->
Tenth of a second
Day of the week
Second
Minute
Hour
Day
Month
Year
Century
Read date and time of the last stop in BCD format (9 byte table).
Octets
<----------------------------------->
Tenth of a second
Code of last stop *
Second
Minute
Hour
Day
Month
Year
Century
* RUN ---> STOP power break, program failure.
___________________________________________________________________________
3/12
Contents
Part C
Section
1
Page
Safety
1/1
1.1
Elementary rules
1/1
1.2
Grounding
1/2
1.3
Connections between buildings
1/3
1.4
Neutral point connections

1.4-1 TT layout
1.4-2 IT layout
1.4-3 TN layout
1/5
1/6
1/7
1/8
Cable ducts
2/1
2.1
General
2/1
2.2
Installation location
2/1
2.3
Reducing effect
2.3-1 Correct procedure
2.3-2 Principle
2.3-3 Routing methods
2/2
2/2
2/2
2/3
2.4
Separation effect
2.4-2 Principle
2.4-3 Mounting topology
2/4
2/4
2/4
2/5
2.5
Labeling cable ducts
2/8
2.6
Special cases
2/9
___________________________________________________________________________
C/1
Contents
Part C
Section
3
Page
Electromagnetic caging
3/1
3.1
General
3/1
3.2
Principles
3/1
3.3
Creating the cage
3/3
Conclusion
4/1
Appendix
5/1
5.1
Electrical risks
5/1
5.2
Comments concerning low voltage networks
5/2
5.3
Bibliography
5/2
___________________________________________________________________________
C/2
Section
Safety 11
1 Safety
1.1
Elementary rules
This section summarizes some of the elementary rules (from the standard NFC 15 100)
relating to the safety of personnel and equipment.
These rules must be applied in any industrial installation; they are not specific to
installations comprising control system equipment.
A few mA can kill!!
Although this amount of electricity may seem ridiculously low, the risk is nevertheless
very real (see section 5.1).
It is essential that the standards relating to the safety of personnel are respected.
These standards cover, among others, the following two points :
the grounding of equipment and associated links,
the conformity of the "neutral point connection" used.
___________________________________________________________________________
1/1
1.2
Grounding
Two different concepts should be distinguished :

The concept of machine or chassis ground
This is a low impedance path between two devices, used for reasons of equipotentiality
(improving immunity to interference). The purpose of this "ground" is to reduce any
accidental and interference voltage which may exist between the two devices. This is
done over a very large frequency band. This concept takes account of the operating
requirements.
The concept of protective earth ground

This is a low frequency, low impedance path between the machine ground of the
devices and the earth ground, used in the event of a malfunction between an electrical
circuit and the machine ground. This concept takes account of thesafety requirements.
These are the two different concepts, but they are not two different circuits.
All grounding networks must be connected to the earth ground.
Grounding network
This is a network created by interconnecting all the metal elements (building structure,
pipes, cable ducts, equipment and their enclosures).
Earth ground
This is the reference earth connection, consisting of a grounding rod, grounding grid or
the grounding belt of the building, to which the grounding networks are connected. There
must only be one earth ground per building.
___________________________________________________________________________
1/2
Safety
There is a danger of death by electrocution if two grounds which are not

interconnected are touched simultaneously. This is also true if the recommendations
in section 413.1.2.1 of standard IEC 364 concerning the main equipotential
connection are not observed.
Signal cable
C
risk if U > UL (*)
Inevitable difference in voltage U
other
ground
Risk of electrocution if two unconnected

grounds are touched simultaneously
* UL = Conventional voltage limit :
1.3
25 volts rms (AC)

60 volts (DC)
(standard IEC 364.4.41)
Connections between buildings
An installation occupying more than one building runs the risk of having different earth
grounds (grounding rods). There are three possible cases :
the earth grounds are interconnected : no problem,
the earth grounds are not interconnected : interconnect them (this connection is
a safety rather than an operating requirement),
the interconnection is doubtful : make the interconnection !!
To interconnect the earth grounds, use conductors reserved for this purpose.
Currents circulating between two earth grounds can be very strong :
Never make the interconnection using the shielding of a shielded cable.
Always use conductors with a gauge of at least 35 mm2 to be able to support any
possible fault currents.
___________________________________________________________________________
1/3
Any conducting trunking entering a building (conducting cable, conducting piping or

isolated piping carrying a conducting fluid) must be connected to the earth
ground at their point of entry to the building and over the shortest possible distance.
It is important to comply with the characteristics of use of the cable supplied by the
manufacturer :
characteristics relating to the physicochemical nature of the cable :
- operating environment and temperature,
- use inside or outside,
- whether it can be buried with or without protection.
characteristics relating to the physical nature of the cable :

- bending radius,
- whether it is self-supporting.
Lightning
conductor
Cable gland for conductor
BAY
Grounding
strip
Grounding
belt
Ground
interconnection
conductor
Shielding
grounding clip
Buried shielded cable
___________________________________________________________________________
1/4
Safety
1.4
Neutral point connections
Every subscriber supplied via one or more medium voltage/low voltage transformers
must select the neutral point connection according to a certain number of factors (current
regulations, practical and financial considerations, etc).
The neutral, despite its name, is not totally harmless.
It must always be considered as an active conductor.
Several different neutral point connections exist which have a 2-letter reference : TT, IT
and TN :
the first letter represents, at the level of the distribution transformer, the location of the
neutral in relation to the earth ground :
- T = direct connection of the neutral to the earth ground,
- I = connection via an impedance,
the second letter represents the location of the machine grounds in the installation :
- T = connection of the machine grounds to one distinct earth ground boss,
- N = connection of the machine grounds to the neutral.
___________________________________________________________________________
1/5
1.4-1 TT layout
Neutral earth ground
Machine ground
C
This layout is imposed in public low voltage distribution (LV).
Differential protective systems are required.
Each earth ground connection (of the machine grounds) must be protected by its own differential
protective device.
Disconnection must occur at the first insulation fault (on one phase).
A single earth grounding network is preferable.
Example of single phase distribution with insulation fault on the phase :

Distribution
Id
P
230 V
N
P : Phase
N : Neutral
Differential
protection Id
Id
Neutral
earth ground
Return of fault current Id by the earth ground
Machine
ground
___________________________________________________________________________
1/6
Safety
1.4-2 IT layout
Impedance
Continuity of service is possible on the first fault.

The permanent insulation controller (or impedance) must indicate the first fault.
This layout requires a private transformer and a maintenance service.
In the event of a second fault, the protection is the same as for the TN layout (except for a second fault
on the same phase).
The distance between the installations must be limited.
Surge arresters must be installed.
Example of single phase distribution with insulation fault on the phase :

Private transformer
Id
P
230 V
N
P : Phase
N : Neutral
ld
Z : Impedance or permanent
Insulation controller
Id
Return of fault current Id by the earth ground
___________________________________________________________________________
1/7
1.4-3 TN layout
C
This layout requires a private transformer.
Additional equipotential connections are required (refer to the standard NFC 15 100).
Disconnection occurs selectively on the first insulation fault.
There are two versions : TN-C (Common PEN connections) and TN-S (Separate PE and N connections)
shown below.
The TN-C layout is prohibited downstream of the TN-S layout.
The TN-C layout is prohibited in mobile trunking or Scu < 10 mm2.
The best layout is TN-S, which is highly recommended.
Example of single phase TN-C layout with insulation fault on the phase :
Private transformer
Id
la
Magneto-thermal relay
P
PEN
230 V
N
Id
PEN
P
N
:
:
:
:
ld
ld
Fault current
"Protective Earth and Neutral" : protection and neutral cables
Phase
Neutral.
___________________________________________________________________________
1/8
Safety
Example of single phase TN-S layout with insulation fault on the phase :
Private transformer
Id
230 V
la
Magneto-thermal relay
N
PE
ld
ld
C
Id : Fault current,
N : Neutral
PE : "Protective Earth" : protection cable.
Differential protective systems (Idn of 0.5A to several Amps) can be used in this layout.
This is recommended for improved protection against unspecified faults and fire.
___________________________________________________________________________
1/9
___________________________________________________________________________
1/10
Section
Cable
ducts 22
2 Cable ducts
2.1
General
A control system installation which is correctly wired from the outset avoids incurring
additional costs and delays due to electromagnetic interference.
The role of cable ducts as a physical support is widely acknowledged. However, if certain
mounting criteria (distance, electrical continuity) are observed, they can be particularly
effective in reducing the effect of interference.
In the rest of this section, the term "signal cables" refers to cables carrying information
such as measurement signals, digital signals, video signals, etc.
In order to minimize the effect of cables causing interference on the signal cables,
the following rules must be respected.
2.2
Installation location
Cable ducts must be installed on a site rendered equipotential by interconnecting the

"earth grounds" : see sections 1.2 and 1.3.
The best way to carry information between buildings is via optical fibres.
If a signal cable, on an equipotential site, is located outside a building (a water treatment
plant, for example), additional precautions must be taken (using overvoltage protectors,
etc).
Any type of mobile cable (for example : garland) must be specially selected. The specific
rules relating to the installation of these cables are beyond the scope of this document.
___________________________________________________________________________
2/1
2.3
Reducing effect
_______________________________________________________________________________________
Metal cable ducts are essential for all fixed cables.
Run all cables (insulated), from end to end, as close to a metal ground as
possible, for example a metal cable duct.
Ensure the electrical continuity of all the consecutive cable segments in the cable
duct.
Connect this metal ground to the electromagnetic caging (for further details, see
section 3).
The devices must be fixed to metal plates or standard rails connected to ground.
2.3-2 Principle
Shielding via mutual inductance between the cables and ground conductors.
To illustrate the effectiveness of mounting cables in metal cable ducts, connected to
each other and to ground, here are some figures taken from the "EMI Control"
document.
The proximity of the ground is used to reduce couplings between cables by :
a factor of 10 if the distance is h = 20 mm,
a factor of 1000 if the distance is only h = 1 mm.
Cable duct
(grounding network)
___________________________________________________________________________
2/2
Cable ducts
2.3-3 Routing methods

Visible
mountings
N
O
Insulating
wall
PVC tube
Insulating
moulding
or plinth
C
Avoid these routing methods which have no reducing effect
Cable duct
Y
E
S
Non-perforated rack or
metal trunking
Cable rack
or ladder
Use these routing methods which have a reducing effect
Reminder
Pay attention to the bending radius and to the temperature conditions imposed by the
cable manufacturer.
___________________________________________________________________________
2/3
2.4
Separation effect

Use signal cable ducts which are distinct and separate from cable ducts which
cause interference.
Also keep signal cables away from equipment which causes interference.
2.4-2 Principle
To illustrate the effectiveness of keeping cable ducts separate, here are some figures
taken from the "EMI Control" document.
In comparison to cables which are run side by side, the capacitive and inductive
couplings are reduced by :
a factor of 10 if they are separated by d = 10 cm,
a factor of 1000 if they are separated by d = 1 m.
Grounding network
___________________________________________________________________________
2/4
Cable ducts
2.4-3 Mounting topology

Separate cable ducts must be used for power and signal cables :
A power cable duct is filled up very quickly. If one or more additional power cables
are needed at a later date, it can be very tempting to run them in the signal cable
duct. The labeling system outlined in section 2.5 should avoid this.
Parallel mounting
This is quite common, although not recommended. It requires a minimum distance
between both cable ducts.
C
Signal
Power
50 cm min
The ducts can be laid side by side (1) provided
that they are separated by a metal partition and
that a metal cover is placed on the signal duct
providing an electrical contact with the duct.
Electrical contacts
Signal
Power
Signal
30 cm min
Power
Electrical contacts
The ducts can be laid closer together (1) provided

that a metal cover is added to the bus cable duct.
Signal
Power
(1) When using a MAPWAY network, separate cable ducts must be used. Moreover, the minimum
distances are increased to 1 m.
___________________________________________________________________________
2/5
Crossing cable ducts (at any angle)

Power
30 cm minimum except if the bus
cable duct has a metal cover in
electrical contact with the ducting.
Signal
C
A minimum distance of 20 cm must be respected between the signal cables and
any equipment causing interference (1 m for MAPWAY cables).
In the case of an element causing particularly high levels of interference, a larger
separation distance or additional safety
precautions may be required.
Signal
20 cm
minimum
20 cm
minimum
Interference
Power
Equipment
causing
interference
Self-starting
synchronous
motor
(for example)
___________________________________________________________________________
2/6
Cable ducts
Ensure electrical continuity at the interface between a cable duct and a device.
Bolted to ensure electrical continuity (*)

Enclosure
(*) The duct must be fixed at a minimum of two points :

remove any paint from the points of contact,
fix the cable duct using bolts,
retouch the paintwork.
___________________________________________________________________________
2/7
2.5
Labeling cable ducts
All cable ducts must be labeled :

in conformance with the current standards used in the plant (special labels or color
code),
or, in the absence of any standards, using labels as shown below :
Numerical links
No power cables less than 20 cm away
C
1.5 to 2 m
1.5 to 2 m
Signal
Ducts should be labeled every 1.5 m or 2 m, so that if any partitions or devices are added
at a later date, the labels will still be visible.
___________________________________________________________________________
2/8
Cable ducts
2.6
Special cases
Always :
run cables as far away as possible from equipment which causes interference,
where this cannot be avoided, run as few cables as possible close to such
elements.
If it is not possible to respect the recommended distance or if elements causing
interference are particularly powerful, it is advisable to provide a special protection
solution, such as that described below.
A good solution is to run the signal cable in a metal tube which is directly connected
at both ends to the metal ground (chassis) of the devices. The electrical continuity of
the tube must be perfect throughout its length (the elements may be assembled by
welding, or by screws with no fibre or teflon packing material).
Junction box
Metal tube
Equipment
causing
interference
Equipment
causing
interference
Tube
Exterior
Conductor cable gland
Interior
CONDUCTING CONNECTION
___________________________________________________________________________
2/9
Entry of cables in protective tubes
Use a METAL cable duct

if there is no tube
Equipment enclosure
C
Conductor cable gland
Metal tube
Grounding strip
the tube should enter as close as possible to the equipment

to be connected (25 to 30 cm maximum),
the connection between the tube and the grounding strip
should be as short as possible,
the tube should enter as far away as possible from
equipment causing interference.
___________________________________________________________________________
2/10
Cable ducts
Ensure the electrical continuity of a protective tube exiting an enclosure :
Conductor cable gland (*)
Enclosure
Metal tube
(*) Mounting precautions :

remove any paint from the points of contact,
fix the cable gland,
retouch the paintwork.
___________________________________________________________________________
2/11
___________________________________________________________________________
2/12
ElectromagneticSection
caging 33
3 Electromagnetic caging
3.1
General
Electromagnetic caging is an industrial solution, which is very effective at all

frequencies (up to more than 100 Mhz) and can be verified by the IEC 801-4 test :
"Electromagnetic compatibility for measurement and control materials in industrial
processes; Instructions relating to rapid electrical transients in bursts".
It protects all the electronic transmissions and is an excellent safety factor in case of a
lightning strike.
C
3.2
Principles
The cage must be operative both vertically (1) and horizontally.

The purpose of the operation is to create the smallest possible cage (3 to 5 m on
each side) by interconnecting all equipment in three dimensions.
To be protected by the cage, each device must be connected to at least 2 different
sides of the cage.
A junction or distribution box must be considered as an item to be protected by the cage.
Its case must be connected to the cable ducts and/or the building structure.
Whenever a piece of equipment is added to an installation, it must be integrated in the
electromagnetic cage.
(1) A horizontal grounding network by itself does not give adequate protection against lightning.
Since the current produced by lightning is vertical, it therefore produces a horizontal magnetic field.
___________________________________________________________________________
3/1
Illustration of the principle of a three-dimensional electromagnetic cage :
Horizontal
cable duct
Vertical cable duct
Vertical
grounding
network
Horizontal cable
ducts
Vertical cable
duct
Equipment
Iron strip (1)

d
Horizontal
grounding
network
d
Distance "d" must be less than 5 meters.

(1) Continuity is ensured using, for example, an iron strip of 100 x 5 mm.
___________________________________________________________________________
3/2
3.3
Creating the cage
Many conductive elements exist in all industrial installations, including the following :
metal structures of buildings,
conductive equipment enclosures,
metal cable ducts mentioned in section 2.3-1 (with electrical continuity from end to
end),
protective cables and conductive pipes.
The cage is created by interconnecting electrically :
all the grounding elements,
any additional conductors added later,

in such a way that the principles outlined in section 3.2 are respected.
The conductive structures are interconnected either by direct contact or using a flat braid
(35 mm2 minimum) or an iron strip (100 x 5 mm minimum) over the shortest possible
distance.
"NELSON" bolts (welded)

Electrical continuity
braid
Conducting pipes
Protection cable
(connected to the
building earth ground)
Grating
Interconnection of all the conductive structures
___________________________________________________________________________
3/3
Wherever possible, false metal floors should be used.

< 50 cm
Bolted
Braid < 50 cm
Example of a cage made with a braid of 35 mm2 connecting the supports of a false floor
in pairs every 3 meters :
___________________________________________________________________________
3/4
Section 44
Conclusion
4 Conclusion
C
In industrial environments, equipment should be connected :
respecting the safety rules, (section 1),
making use of the reducing and separation effects, (section 2),
creating an electromagnetic cage, (section 3).
This is an effective industrial solution for protecting electronic transmissions which

are the basis of increasingly automated systems.
___________________________________________________________________________
4/1
___________________________________________________________________________
4/2
Section 55
Appendix
5 Appendix
5.1
Electrical risks
Table of physiological and pathological effects (AC 50/60 Hz)

Current intensity
Effect on the human body
1 mA
Tingling sensation on the skin
5 mA
Electric shock
10 mA
Muscular contraction causing an inability to let go
25 mA for 3 min
Tetanization of respiratory muscles
40 mA for 5 s
80 mA for 1 s
Ventricular fibrillation
20000 mA
Inhibition of nerve centres
(Extract from "La scurit lectrique" by R. Choquet).
Most of the data available is the result of experiments conducted by IEC standards
experts. For perception thresholds and muscular contraction, the tests were carried out
directly on humans. For the tetanization of respiratory muscles, ventricular fibrillation
and inhibition of the nerve centres, the tests were carried out on animals.
Taking account of the fact that the thresholds may vary from one individual to another,
and that the transposition to humans of the results obtained on animals is not always
reliable, the figures given in the table above must be considered as approximate.
___________________________________________________________________________
5/1
5.2
Comments concerning low voltage networks
Voltage drops are frequent and last a maximum of 0.5 seconds.

The harmonics must be frequently filtered. In particular, the differential protection of a
3-phase network must be protected against the third harmonic using a filter.
The distribution of the power supply, in contrast to the machine and earth ground
connections, should be mounted in a star connection around the transformer.
An ininterruptible static power supply protects against interference in differential mode
only, and not in common mode.
The various neutral point connections only differ from each other at low frequencies
(< 100 KHz), and in common mode only.
The neutral should only be connected to the earth ground at one point (this is a problem
with the TN-C layout).
The best layout is the TNS.
The earth ground bosses must be interconnected.
External overvoltages must be limited (surge arresters, etc).
The neutral must be connected to the earth ground at one point.
The TN-S layout combines the three conditions immediately above, as does the IT layout,
but it is essential that the connected hardware supports the voltage between phases.
The neutral is generally connected to the earth ground at the same point as the lightning
conductor (or surge arrester) to minimize the effects of a lightning strike on the installation.
5.3
Bibliography
"La scurit lectrique", R. CHOQUET (1984) published by DUNOD.

IEC 100-4-x standard
withstand to HF interference
IEC 364.xxx standard electrical installation in buildings
NFC 15.100. standard low voltage electrical installation
IEC 1024-1 standard
protection of structures against lightning
ECMA-97 standard
safety of local networks
IEC 65A/WG6 draft standard.
Esprit de l'antiparasitage es-tu l ? (Telec).
(74 rue de la fdration 75015 Paris).
IBM System/370 - 3090 Processor Complex :
Installation Manual-Physical Planning (GC22-7074-6).
IBM General Information Manual :
Installation Manual-Physical Planning (GC22-7072).
EMI Control by White and Mardigan published by Interference Control Technologies
(4th edition 1986 - Virginia USA).
"Parasites et Perturbations des lectroniques" by A.CHAROY (1992) published by
DUNOD.
___________________________________________________________________________
5/2
Contents
Part D
Section
1
Page
1/1
1.1
General
1/1
1.2
Transmission principles
1.2-1 Parallel transmission
1.2-2 Asynchronous serial transmission
1.2-3 Synchronous serial transmission
1/2
1/2
1/3
1/4
1.3
General parameters of asynchronous serial transmission

1.3-1 Types of link
1.3-2 Number of data bits
1.3-3 Parity
1.3-4 Number of stop bits
1.3-5 Transmission speed
1/5
1/5
1/6
1/7
1/7
1/7
RS 232 C link
2/1
2.1
Description
2/1
2.2
Electrical characteristics
2/2
2.3
Mechanical and functional characteristics
2/3
2.4
Use of the link
2/7
2.5
RS 232 transmission distance as a function of transmission rate
2/8
___________________________________________________________________________
D/1
Contents
Part D
Section
3
Page
RS 422/RS 485 link
3/1
3.1
Description
3/1
3.2
Topologies
3.2-1 Half-duplex bus topology with single line adaptation
3.2-2 Half-duplex bus topology with distributed line adaptation
3.2-3 Full-duplex point-to-point topology
3/2
3/2
3/3
3/4
3.3
Main electrical characteristics
3/5
D
4
Current loop link
4/1
4.1
Description
4/1
4.2
Configurations
4/2
4.3
Characteristics
4/4
___________________________________________________________________________
D/2
Section 11
1 Character string communication
1.1
General
A certain number of functions must be performed in order to exchange data between two
remote devices without error, loss or duplication :
organize data into blocks before transmitting it sequentially,
synchronize the transmitter and receiver,
detect transmission errors and if possible recover the corrupted data,
identify the devices which are communicating,
control transmission flow.
These functions form the basis of all link protocols and justify the transmission
characteristics outlined in the following sections.
___________________________________________________________________________
1/1
1.2
Transmission rates and requirements vary considerably from one device to another.
They are dependent upon the distance covered, volumes exchanged, required response
times, installation costs, etc.
To meet all these demands, three transmission modes have been defined.
1.2-1 Parallel transmission

The information from the output of the data
processing equipment is usually sent in
the form of "n" bit words.
Parallel transmission requires the

simultaneous transmission of the "n" data
bits and therefore requires a transmission
line with "n" wires, called a bus, along with
test and command lines.
This transmission mode allows fast transfer
rates (1 megabyte per second) over short
distances (up to 20 meters). This type of
transmission is mainly used for
instrumentation : IEEE-488 standard or for
printers which use a Centronics interface.
Data transmission in parallel mode over
distances of more than a few meters require
a large investment because of the number
of transmission wires required and the
need to use receivers to ensure data
integrity.
Unit
1
Unit
2
BUS
Unit
3
Unit
4
Bus control
lines
8 data
control
address
lines
Data
transfer
control
lines
___________________________________________________________________________
1/2
1.2-2 Asynchronous serial transmission

This type of transmission is widely used in industrial environments as it is easy to set up
and inexpensive.
For this type of transmission the line has only one wire : the binary data bits for a word
or a character are sent one after another (serialization) at a clock frequency.
On arrival the receiver converts the data from serial into parallel mode using a clock of
the same frequency as that used by the transmitter.
Falling edge detection

Detection of start bit
Parity bit (optional)
D
Start bit
Data
(between 5 and 8 bits)
Stop bit
(1 ; 1 1/2 or 2 bits)
The two clocks are synchronized by preceding the transmission of each character by a
Start bit and ending it by 1 or 2 Stop bits.
The type of transmission is called asynchronous, as the time interval between the
transmission of two full characters (including START and STOP bits) may vary
considerably.
This transmission is particularly suitable for low speed data exchanges.
___________________________________________________________________________
1/3
1.2-3 Synchronous serial transmission

Contrary to asynronous transmission, data is sent in frames (from a few bytes to several
Kbytes). The frame consists of a continuous stream of bits (with no start/stop bit as with
asynchronous mode).
The two clocks (transmitter and receiver) are synchronized using a self-synchronizing
code (eg : Manchester code).
H1
H2
Bytes at
end of frame
Data
Start of frame
This type of transmission is particularly suitable for high speed exchange of large
volumes of data (rate 50 Kbits/s).
___________________________________________________________________________
1/4
1.3
General parameters of asynchronous serial transmission
1.3-1 Types of link

Point-to-point link
This type of link is simple, with two stations.
Depending on requirements and on the physical line capability, this type of link can be
used in the following three modes :
simplex (uni-directional) transmission :
Station A is always the transmitter.
Station B is always the receiver.
bi-directional half-duplex transmission :

Each of the two stations can be a
transmitter or a receiver, but not both
simultaneously. The link can only operate
in one direction at any given time.
or
bi-directional full-duplex transmission :

The two stations are simultaneously
transmitters and receivers.
C
and
Multidrop link
When connecting a number of stations to a central unit, a separate point-to-point link can
be used for each one.
However, this approach is costly, especially over long distances. A multidrop system is
therefore generally preferred.
A
In this configuration, the data sent by central device A is received simultaneously by all
the connected stations. However, only one of the stations B, C, or D can send data to
A at any given time.
Consequently, a special procedure must be used for sequencing the data exchanges
between stations.
___________________________________________________________________________
1/5
1.3-2 Number of data bits

Data is coded on 7 bits or 8 bits :
8-bit coding
: pure binary coding, signed and unsigned,
7-bit coding
: standard ASCII coding (American Standard Code for Information

Interchange).
The ASCII codes table is given in the appendix, section 5.

Transmission direction
PARITY STOP
START
i
Eg : Transmission of the character "i" (16#69 in ASCII).
Note :
The 1st bit of a byte (least significant bit) is transmitted first and the 8th (most significant bit) is
transmitted last.
___________________________________________________________________________
1/6
1.3-3 Parity
In the view of the risks of an error during transmission, it is advisable to add information
to the data blocks which are to be sent, so that the receiver can detect an error.
The technique used is to add a parity bit to the transmitted character.
The receiver concludes that there is an error if the parity of the received character does
not match its parity bit.
The parity bit is a function of the type of parity chosen :
even parity
: the total number of bits at 1 (character + parity bit) must be even,
odd parity
: the total number of bits at 1 (character + parity bit) must be odd.
The parity check can be inhibited in certain cases, as other data exchange checks are
installed (eg : check using Checksum or CRC cylic redundancy check).
This is the case of : "no parity".
D
1.3-4 Number of stop bits
The number of stop bits can vary from 1 to 2. When this or these stop bits are received
the receiver returns to idle status.
The receiver clock is only synchronized with the transmitter clock for the duration of the
character transmission. Adding service bits (start and stop) to each byte to be
transmitted corresponds to a minimum loss of 25 % of the line transmission capacity.
It is therefore advisable only to use one stop bit in order to improve efficiency.
Note :
The choice of using more than one stop bit is associated with equipment using old technology where
the electronics are not sufficiently precise to be able to detect a character end on a single stop bit.
This problem is not seen on more up-to-date equipment.
1.3-5 Transmission speed

Asynronous serial mode is particularly suited for low transmission speeds. The associated
speeds are as follows :
1 200 bit/s
9 600 bit/s
2 400 bit/s
19 200 bit/s
4 800 bit/s
___________________________________________________________________________
1/7
___________________________________________________________________________
1/8
Section
RS 232
C link 22
2 RS 232 C link
2.1
Description
The name of this link comes from the RS 232 C standard defined by the EIA (Electronic
Industries Association). It is also sometimes referred to as V24, as it is almost identical
to the V24 and V28 standards defined by the CCITT (International Telegraph and
Telephone Consultative Committee).
The objective of the EIA RS 232 C standard is to define the functional, electrical and
mechanical characteristics of exchanges between DTE and DCE :
DTE
: Data Terminal Equipment such as PLCs, computers, etc
DCE
: Data Circuit terminating Equipment such as modems, signal converters, etc
In practice, the RS 232 C link is a voltage interface defined for asynchronous and
synchronous serial transmissions.
The RS 232 C link includes two data transmission lines, one for each direction and a set
of control and command lines required for establishing a communications channel.
All of these lines are referenced to a common wire (Signal ground).
The RS 232 link is a point-to-point link.
___________________________________________________________________________
2/1
2.2
Electrical characteristics
The RS 232 C link is defined for distances of up to 15 meters and transmission speeds
of up to 20 Kbps.
Output voltage (no load)
Output voltage (full load)
Transition levels
Receiver impedance
Signal variation speed
For data lines :
25 volts max.
5 to 15 volts
(positive and negative polarity)
3 volts
3 to 7 k
30 V/s max.
+ 15 V
voltage > 0 = bit at logic 0,

voltage < 0 = bit at logic 1.
For service signals :
+5V
-5V
voltage > 0 = TRUE state,

voltage < 0 = FALSE state.
- 15 V
Closed circuit voltages
___________________________________________________________________________
2/2
RS 232 C link
2.3
Mechanical and functional characteristics
The RS 232 C connection characteristics

are the same as the ISO 2110 standard
which defines a 25-pin connector and the
function of the different pins.
13 ...
25 ...
... 21
... 14
___________________________________________________________________________
2/3
Pin n
on 25-pin
connector
Function
Abbrev.
Name
Abbrev.
Name
Grounds
PG
Protection
Ground
PG
Protection
Ground
Data
SD
Send Data
SD
Send Data
Data
RD
Receive Data
RD
Receive Data
Control
signal
(transmission
command)
RTS
Request to
Send
RTS
Request To
Send
The DTC indicates to

the DCE that it is ready
to transmit and sets it
to transmission mode
Control
signal
(transmission
command)
CTS
Clear to
Send
CTS
Clear To
Send
The DCE indicates to

the DTC that it is ready
to transmit the signal
and prepares the DTC
for transmission
Control
signal
(establishing the
connection)
DSR
Data Set
Ready
DSR
Data Set
Ready
The DCE indicates its

local state to the DTE,
if it is correctly
connected, the line
is active
Grounds
SG
Signal
Ground
SG
Signal
Ground
Electrical ground
Control
signals
(indicator)
DCD
Data Carrier
Detect
DCD
Data Carrier
Detect
Indicates to the DTE

that a signal has been
received
Voltage
tests
PTV
Positive Test
Voltage
Reserved for DCE to

test the voltage of the
DTC
10
Voltage
tests
NTV
Negative
Test Voltage
Reserved for DCE to

test the voltage of the
DTC
11
Parameter
selection
STF
Select
Transmit
Frequency
STF
Select
Transmit
Frequency
11
Parameter
selection
SRF
Select
Receive
Frequency
SRF
Select
Receive
Frequency
12
Secondary
channel
SDCD
Secondary
DCD
CCITT
EIA
Observations
DTCDCE
direction
In the 1987 update, the

protection ground
protection was replaced
with cable screening
Signal detection on the

secondary channel
___________________________________________________________________________
2/4
RS 232 C link
Pin n
on 25-pin
connector
CCITT
Function
Abbrev.
Observations
DTCDCE
direction
Abbrev.
Name
13
Secondary
channel
SCTS
Secondary
CTS
Secondary channel
ready
14
Secondary
channel
SSD
Secondary
SD
Data transmitted on the

secondary channel
15
Clocks
SCTE
Serial Clock
Transmit
External
DCE transmission clock

for synchronization
16
Secondary
channel
SRD
Secondary
RD
Data received on the

secondary channel
17
Clocks
SCR
Time base
for signals
element to be
received
SCR
Serial Clock
Receive
Reception clock
18
Miscellaneous
LL
Test
Command
LL
Local Loop
back
19
Secondary
channel
SRTS
Secondary
RTS
20
Control
signals
(establishment of the
connection)
SCTE
CDS
Name
EIA
Time base
for signals
element to be
transmitted
Connect
Data Set to
line
CDS
Request to send on
secondary channel
Connect Data Closed state :

Set to line
connection on the line
Open state :
disconnected after
transmission
DTR
Data
terminal
ready
DTR
Data
Terminal
Ready
Closed state :
DCE can connect if
called
Open state :
disconnected after
transmission
21
Miscellaneous
SQD
Signal
Quality
Detector
SQD
Signal
Quality
Detector
22
Control
signals
(indication)
RI
Ring
indicator
RI
Ring
Indicator
The DCE indicates to

the DTE that a call has
been detected
___________________________________________________________________________
2/5
Pin n
on 25-pin
connector
23
CCITT
Function
Parameter
selection
EIA
Abbrev.
Name
Abbrev.
Name
DRS
Binary Rate
Selector
(DTE)
DRS
Data Rate
Selector
Binary Rate
Selector
(DCE)
DRS
Observations
Selection of
transmission
DRS
Data Rate
Selector
24
Clocks
`
SCTI
Basic time for

signal
elements
to be
transmitted
SCTI
Serial Clock
Transmit
Internal
25
Miscellaneous
TM
Test
Indicator
TM
Test Mode
DTCDCE
direction
speed
Synchronization
Pins 1 to 8, 20, 22 and 23 are the most frequently used. The other pins (seldom used)
are mainly assigned to the time bases required for synchronous serial transmission, as
well as a secondary channel for supervising the link.
The RI, DST, DTR signals are used to make and break the circuit when a line is not
permanently assigned to the link.
The RTS, CTS, DSR signals are used to initialize transmission.
The DRS signal is used to select one of two transmission speeds when a choice is
offered by the Modem.
___________________________________________________________________________
2/6
RS 232 C link
2.4
Use of the link
The RS 232 C standard is certainly the most widely used today. Its relative complexity
is due to its wide range of applications : synchronous and asynchronous transmission,
manual dial or auto-dial, etc.
Although originally designed for data transfer via a telephone line, it is often used for local
communication. In this case the main service signals designed for modem control are
used for status checks and the control of peripherals such as printers.
___________________________________________________________________________
2/7
2.5
RS 232 transmission distance as a function of transmission rate
Distance
15 m
20 kb/s
10 b/s
100 b/s
1000 b/s
10 kb/s
100 kb/s
1 Mb/s
Rate
___________________________________________________________________________
2/8
RS 422/RS Section
485 link 33
3 RS 422/RS 485 link
3.1
Description
These standards are completely different from the RS 232 C standard as they define a
differential transmission mode. Each data signal is transmitted through two wires, and
is not referenced to ground, but is presented as a differential signal on the transmitter
outputs and on the receiver inputs. The RS 485 standard is an extension of the
well-known RS 422A standard which allows multidrop as well as point-to-point links.
The use of a terminating device (Rt resistor)
is recommended so that the line is adapted
to its characteristic impedance. This layout
minimizes noise and echo, and ensures a
better quality of transmission. Normally
the line is adapted at one end.
Line
A
Terminating
resistor
A'
Rt
B
Transmitter
B'
Receiver
___________________________________________________________________________
3/1
3.2
Topologies
3.2-1 Half-duplex bus topology with single line adaptation

This adaptation is used for ModBus type networks
5V
Rx
Tx+
Rp
L
Rc
Pc
L+
Rp
0V
The diagram above shows the general architecture of a RS 485 network.

Tx+
Transmitters are symbolized as
Tx
Rx+
Receivers are symbolized as
Rx
(A)
(B)
(A')
(B')
The network is a single shielded twisted pair. The various stations are connected simply
by linking :
on the one hand, allthe outputs labelled + (Tx+, Rx+) to the + wire of the network labelled
(L+),
on the other hand, all the outputs labelled - (Tx-, Rx-) to the - wire of the network labelled
(L-).
The network impedance is adapted using two adaptation resistors (Rc) located on the
two end stations on the network.
Polarization of the network is possible by connecting the L + wire to 0 V and the L- wire
to 5 V via two polarization resistors (R = 470). This polarization enables a current to
continuously circulate on the network. This adaptation can be located anywhere on the
network (in practice, it is generally at master station level).
There should only be one polarization point for the entire network, whatever its length.
___________________________________________________________________________
3/2
RS 422/RS 485 link
The main characteristics are :

up to 32 stations,
maximum length : approximately 1 300 m,
bus topology,
tap link 15 m,
half-duplex on 2 wires,
end of line adaptation on the end stations.
single line adaptation Rp = 470
3.2-2 Half-duplex bus topology with distributed line adaptation
This adaptation is used for UNI-TELWAY type networks
5V
5V
5V
Rx
Rp
5V
Tx+
Rp
Rp
Rp
L
Rc
Rc
L+
Rp
0V
Rp
0V
Rp
0V
Rp
0V
The diagram above shows the general architecture of a UNI-TELWAY network.

The network is a single shielded twisted pair. The various stations are connected simply
by linking :
on the one hand, all the outputs labelled + (Tx+, Rx+) to the + wire of the network
labelled (L+),
on the other hand, all the outputs labelled - (Tx-, Rx-) to the - wire of the network
labelled (L-).
The network impedance is adapted using two adaptation resistors (Rc) located on the
two end stations on the network.
Distributed polarization of the network is possible by connecting the L+ wire to 0 V and
the L- wire to 5V via two polarization resistors (R = 4.7K). This polarization enables a
current to continuously circulate on the network. This adaptation must be performed for
every station on the network.
___________________________________________________________________________
3/3
The main characteristics are :

up to 32 stations,
maximum length : approximately 1 300 m,
bus topology,
tap link 15 m,
half-duplex on 2 wires,
end of line adaptation on the end stations.
distributed line adaptation Rp = 4.7K
3.2-3 Full-duplex point-to-point topology

This type of link enables the RS 485 link to be used for full duplex with devices which
do not have an RS 422 A link. When set up this way, the link communication conforms
to the RS 422 A standard.
D
Rc = 120
Tx+
Rx+
Tx
Rx
Rx+
Tx+
Rx
Tx
Rp
Rc
Rp+
Station A
5V
0V
Station B
The maximum distance between the two devices is around 1 300 m, in accordance with
the RS 422 A standard.
For greater distances, it is advisable to install an Rc adaptation resistor in parallel on the
Rx+ and Rx- terminals of the receiver of the device to be connected.
___________________________________________________________________________
3/4
RS 422/RS 485 link
3.3

transmitter
Output voltage with an open circuit :
6 volts > Vo > - 6 volts
Output voltage with circuit closed
through a 120 resistor :
I Vt I > 2 volts and at I Vo/2 I
Vo
120
Vt
Polarity reversed according to the two binary states.

receiver
The receiver is set to provide discrimination between the two binary states when the
differential signals applied to the inputs have an amplitude of between 200 mV and
6 Volts.
The maximum signal differential allowed is + 12 Volts.
Dynamic characteristics
Using shielded twisted pairs with a gauge of more than 0.2 mm2 (AWG 24), and a line
terminating device, data rates of up to 100 K bits/sec are possible over distances of 1000
meters.
In practice, the use of this standard with reduced data rates (10 Kbits/s) allows data links
of up to a few kilometers.
The electrical characteristics of the RS 422 A/RS 485 links (differential mode and high
current level) which provide data transmission with a high degree of immunity from
interference make this a standard which is increasingly widely used. The transmitters
can be placed in a "high impedance" state using a related command, enabling operation
in multidrop configuration.
This link ensures good distance/speed performance, a low-cost configuration which
enables any subscriber to be disconnected without disturbing the network.
___________________________________________________________________________
3/5
___________________________________________________________________________
3/6
Section
Current loop
link 44
4 Current loop link
4.1
Description
The 20 mA current loop link is probably the oldest type of serial link. It was originally
developed for communication with a teleprinter but has never been defined as a
standard.
The link is made up of two loops, one for transmission, one for reception, which may or
may not have a 20 mA current running through them, obtained from a voltage source.
___________________________________________________________________________
4/1
4.2
Configurations
Transmission is via a 2 pair telephone type line, the length of which is limited by the
characteristics of the line (loop resistance and line capacitance) and by the transmission
speed.
The current junction can be active or passive. Active or passive mode can be selected
at either end of the line.
For every active mode there must be a corresponding passive mode and vice versa.
Station A active, station B passive
Transmission
Reception
Reception
Transmission
D
Station A
Station B
Note :
The station is said to be active if it supplies the energy required to transport data, and passive if this
is not the case.
Station A passive, station B active,
Transmission
Reception
Station A
Reception
Transmission
Station B
Line idle status corresponds to current passing.
___________________________________________________________________________
4/2
Current loop link
Warning
It is possible to "mix " the operating mode for transmission and reception loops on
the same station (active transmission and passive reception, for example).
The slave stations are in series with the master.
Line idle status is 20 mA.
Master station (active)
Slave stations (passive)
D
Maximum number of slave stations is 8
Key :
Current generator
(active station)
Receiver
Transmitter
Direction of the current
___________________________________________________________________________
4/3
4.3
Characteristics
No current through the loop corresponds to :

A START bit,
20 mA
A data bit at logic 0.

When a 20 mA current is
present, this corresponds
to :
0 mA
A STOP bit,
A data bit at logic 1,
Line idle.
Line idle
Stop
Data
Start
Performance
The data transmission speed reached with this type of link is quickly limited by the length
and gauge of a cable used. A current loop allows a data rate of 600 bits/sec over a
distance of approximately 3 kilometers. For higher data rates (9600 bits/s) the maximum
distance is a few hundred meters only.
Due to its simplicity and ease of operation, the current loop is often used for applications
where a data rate of a few thousand bits per second is sufficient and when the data to
be sent is not systematic (operator dialog for example).
The 20 mA current loop link has a good immunity to interference and is a low-cost
configuration.
___________________________________________________________________________
4/4
Index
Index
X_WAY communication index
Index
A
Access generic objects
B2/39
Access parameters
B2/40
Action on an object
B2/52
Identification of objects
B2/39
Read a generic object
B2/45
Read a list of objects
B2/49
Write a generic object
B2/47
Write a list of objects
B2/51
Access standard objects
B2/13
Force an internal bit
B2/22
Grafcet step status
B2/23
Read a constant word
B2/21
Read a system bit
B2/15
Read a system word
B2/19
Read an internal bit
B2/13
Read an internal word
B2/17
Write a system bit
B2/16
Write a system word
B2/20
Write an internal bit
B2/14
Write an internal word
B2/18
Access to I/O modules
B2/25
Read the memory image of a simple
discrete module
B2/26
Read the objects of an I/O channel B2/34
Read the status of a module
B2/31
Write memory image bit of a simple
discrete module
B2/29
Write the objects of an I/O channel B2/37
Address format
A3/4
A3/8
A3/11
A3/6
Architecture
A1/3
Bridge
A1/10
Concentrator
A1/8
Multi-network
A1/6
Redundancy
A1/9
Single network
A1/4
C
Cable ducts
C2/1
D1/1
Channel level
Module level
Station level
A3/3
A3/3
A3/3
A3/3
D
Data transfer
Backing up a segment
Downloading a segment
Ending a backup
Ending a downloading sequence
Launching a backup sequence
Start downloading
Description of object classes
Counter object
Drum controller
Fast counter object
Monostable objects
"Operator dialog message" object
"Pulse train generation" object
"Pulse width modulation" object
Real-time clock object
Register objects
"Shift register" object
"Step register" object
Timer objects
B2/57
B2/62
B2/59
B2/63
B2/60
B2/61
B2/58
B3/6
B3/7
B3/8
B3/9
B3/7
B3/11
B3/10
B3/9
B3/12
B3/8
B3/10
B3/11
B3/6
E
ETHWAY
C3/1
A1/19
F
FIPIO
FIPWAY
A1/18
A1/17
G
IDENTIFICATION
MIRROR
PROTOCOL_VERSION
READ_CPU
Grounding
B2/3
B2/3
B2/12
B2/10
B2/8
C1/2
___________________________________________________________________________
1
L
B2/2
O
Operating mode management
Initialization
Launching an application or task
Stopping an application or task
OSI model
Application layer
Data link
Network layer
Physical layer
Presentation layer
Session layer
Transport layer
B2/54
B2/56
B2/54
B2/55
A1/11
A1/14
A1/12
A1/13
A1/12
A1/14
A1/13
A1/13
X-WAY addressing
Architecture level
Station level
X-WAY frame
Addresses
Common words
Data
Distributed data
NPDU type
A3/1
A3/1
A3/2
A4/1
A4/4
A4/9
A4/7
A4/8
A4/5
A4/3
A4/6
R
RS 232 C link
RS 422/RS 485 link
D2/1
D3/1
S
Semaphore management
Hold a reservation
Release
Reservation
B2/65
B2/67
B2/66
B2/65
T
Asynchronous serial transmission
Synchronous serial transmission
D1/2
D1/3
D1/4
U
UNI-TE exchange
UNI-TE requests
UNI-TE service
CLIENT-SERVER
Common words
Remote I/O
Shared table
UNI-TELWAY
B1/3
B2/2
A2/2
A2/9
A2/2
A2/5
A2/11
A2/7
A1/16
___________________________________________________________________________
2

MAN - Cable Laying Practices - 2

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

MAN - Cable Laying Practices - 2

Caricato da

Copyright:

Formati disponibili

___________________________________________________________________________

UNI-TE Protocol, request coding

Safety, ground connections

Character string communication

Network documentation presentation

The OSI model as defined by the ISO standard

Positioning of the various networks in the OSI model

Introduction to the services

Common word service : COM service

Shared table service

Remote Input / Output services

X-WAY addressing mechanisms

Introduction to hierarchical addressing

Three level addressing

Five level addressing

Six level addressing

X-WAY frame format

Network documentation presentation

1.1-1 Introduction to the various manuals

MODBUS/JBUS protocol : TSX DG MDBE,

1.1-2 Using the network documentation

* CIM : Computed Integrated Manufacturing

The OSI model as defined by the ISO standard

1.3-1 Introducing the model

Layers designed for

Layers designed for

Physical connection medium

1.3-3 Data link layer

shares the transmission channel between the various stations.

manages the control and flow of data.

1.3-4 Network layer

1.3-5 Transport layer

1.3-6 Session layer

1.3-8 Application layer

Positioning of the various networks in the OSI model

1.4-1 X-WAY and OSI model

UNI-TE message handling system

Access to the network : Master/Slave

RS 485 1200 b/s to 19200 b/s

UNI-TE message handling system

Exchange of cyclic data

UNI-TE message handling system

Exchange of cyclic data

UNI-TE message handling system

Introduction to the services

Common words (COM)

2.2-2 CLIENT-SERVER concept

This device initiates communication. It asks a question (read), transmits

2.2-3 List of requests

Requests most commonly used

Common word service : COM service

256 words of 16 bits for ETHWAY,

Common memory zone

Shared table service

Z. PLC n : Broadcast zone assigned to PLC n n

Table of internal words

Remote Input / Output services

X-WAY addressing mechanisms

3.2-2 Station level entities

3.2-3 Module level entities

3.2-4 Communication channel level entities

Remote address (inter-station)

Local address (intra-station)