___________________________________________________________________________

X-WAY General___________________________________________________________________________

A

UNI-TE Protocol, request coding B___________________________________________________________________________

Safety, ground connections C___________________________________________________________________________

Character string communication D___________________________________________________________________________

ContentsPart A

Section Page

___________________________________________________________________________

A/1

A

1 Introduction 1/1

1.1 Network documentation presentation 1/11.1-1 Introduction to the various manuals 1/11.1-2 Using the network documentation 1/1

1.2 Types of architecture 1/31.2-1 General 1/31.2-2 Single network architecture 1/41.2-3 Multi-network architecture 1/61.2-4 Concentrator 1/81.2-5 Redundancy 1/91.2-6 Bridge 1/10

1.3 The OSI model as defined by the ISO standard 1/111.3-1 Introducing the model 1/111.3-2 Physical layer 1/121.3-3 Data link layer 1/121.3-4 Network layer 1/131.3-5 Transport layer 1/131.3-6 Session layer 1/131.3-7 Presentation layer 1/141.3-8 Application layer 1/14

1.4 Positioning of the various networks in the OSI model 1/151.4-1 X-WAY and OSI model 1/151.4-2 UNI-TELWAY 1/161.4-3 FIPWAY 1/171.4-4 FIPIO 1/181.4-5 ETHWAY 1/19

ContentsPart A

Section Page

A/2___________________________________________________________________________

A

2 Services 2/1

2.1 Introduction to the services 2/1

2.2 UNI-TE service 2/22.2-1 Presentation 2/22.2-2 CLIENT-SERVER concept 2/22.2-3 List of requests 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/92.5-1 Standard 2/92.5-2 Priority exchanges 2/10

2.6 Remote Input / Output services 2/11

ContentsPart A

Section Page

___________________________________________________________________________

A/3

A

3 X-WAY addressing mechanisms 3/1

3.1 General 3/1

3.2 Communication entities 3/33.2-1 Presentation 3/33.2-2 Station level entities 3/33.2-3 Module level entities 3/33.2-4 Communication channel level entities 3/3

3.3 Address format 3/43.3-1 Principles 3/43.3-2 Network number-station number 3/43.3-3 Broadcast address 3/4

3.4 Introduction to hierarchical addressing 3/5

3.5 Three level addressing 3/63.5-1 Presentation 3/63.5-2 Example 3/7

3.6 Five level addressing 3/83.6-1 Presentation 3/83.6.2 Example 3/10

3.7 Six level addressing 3/113.7-1 Presentation 3/113.7-2 Example 3/13

ContentsPart A

Section Page

A/4___________________________________________________________________________

A

4 Appendix 4/1

4.1 X-WAY frame format 4/14.1-1 Presentation 4/14.1-2 X-WAY frame 4/24.1-3 NPDU type 4/34.1-4 Addresses 4/44.1-5 Five level addressing 4/54.1-6 Six level addressing 4/64.1-7 Data (message handling system) 4/74.1-8 Distributed data 4/8

Introduction 1

___________________________________________________________________________

1/1

A

1.1 Network documentation presentation1.1-1 Introduction to the various manualsThis manual is designed for users wanting an insight into X-WAY communication. It aimsto give an overall view of the various X-WAY networks and protocols without dealing withspecific 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 themanual : 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 documentationThe 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,

Section 11 Introduction

1/2___________________________________________________________________________

A

AEG AEG AEG

AEG AEG

AEG

The module is installed in the PLC by following the manual supplied with the module.

Each manual corresponds to a very precise kind of use and refers to the relevant manualfor any other use (eg : separation of the hardware and software integration).

General

TSX DR NET

FIPWAY UNI-TELWAY MODBUS/JBUS

TSX DG FPW TSX DG UTW TSX DG MDB

TSX DM 37N TLX DM PL7M

HARDWARE SOFTWARE

Introduction 1

___________________________________________________________________________

1/3

A

1.2 Types of architecture1.2-1 GeneralX-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 ofnetworks which can handle a large amount of traffic with no restrictions on responsetime. Local area networks adapted for this level are usually based on an Ethernetarchitecture,

factory floor level :factory floors, which are made up of cells, exchange data and can therefore monitorproduction. At this level the data rate of the network must be high enough to exchangelarge quantities of data,(eg : ETHWAY network, MMS/Ethernet),

cell level :all devices connected to the cell share, via the network, data controlled by an overallcontrol system (eg : program, parameters, control messages, etc),(eg : FIPWAY network),

machine or field level :intelligent sensors and actuators and simple control systems communicate at thislevel, with the aspect of real-time having priority,(eg : FIPIO fieldbus).

Several networks operating on different levels, and on sites which may reach aconsiderable size, can only work together and provide total communication if thenetworks 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 routingfrom one network to another.

Examples of network architectures illustrating the various possibilities are described inthis section.

* CIM : Computed Integrated Manufacturing

1/4___________________________________________________________________________

A

ETHWAY

UNI-T

ELW

AY

FIPI

O

1.2-2 Single network architectureThe 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.

CCX 77 FTX 507

Pallet Conveyor Machininghandling

TSX 37 TSX 37 NUM 1060

IBM PCTBX

CCX17

ATV 16XGS Machine tool

Introduction 1

___________________________________________________________________________

1/5

A

This application ensures close coordination between the various controllers, reducingmanufacturing time and eliminating stoppages. Production quality is ensured bymonitoring product and tool condition.The control station sends commands (Start/Stop) to the controllers and downloads theproduction 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/6___________________________________________________________________________

A

OSI/MMS

FIPWAY

FIPWAY

1.2-3 Multi-network architectureIn this example, the factory comprises a number of separate workshops, technicaldepartments, sales and management departments, etc.

Large quantities of data are exchanged between the various functions. Two differenttypes of network are installed to separate the data flows and improve installationperformance 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 awayfrom the factory floor (eg. in the design office).

CAD CAM Sales Scheduling

TSX 7 TSX 7

CCX77

IBM PC

Introduction 1

___________________________________________________________________________

1/7

A

The factory floor is divided into a number of separate production lines which are relativelyindependent and therefore need only exchange limited amounts of data.A CCX 77 supervisor directly connected to each factory floor network is used for localproduction monitoring.The various factory floor networks are connected in clusters to the local area networkvia bridge PLCs.This network also has computers connected to it which provide the link with thefactorywide computer network. The FTX 507 terminal is also connected at this level andsupports the same functions as those described in section 1.2-2 (single networkarchitecture).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 toaddress any other device on the network.

1/8___________________________________________________________________________

A

1.2-4 ConcentratorThe concentrator is a connection system which connects a number of terminals to thenetwork.

The concentrator can have an active role on the network as soon as it can manage thelinks and can perform certain operations connected with the conversion of data whichpasses through filtering and control.It can have "buffer" functions, that is it can store data while waiting for a channel tobecome available.

A PLC can function as a concentrator and provide multi-network architectures asdescribed in the example below.

In this example, the factory comprises two identical production lines. Their length andthe number of devices to be connected preclude the use of a single network.

The processes do not require exchanges between networks. Only supervision dataneeds to be fed back to the higher management level. In this case, the PLC only performsthe function of data concentrator for information from the two networks.

This split architecture enables intervention on one production line without affectingproduction on the other line, while releasing the network node PLC from the workloadcaused by the bridge function, which is no longer necessary.

Station 1 Station 2 Station 3 Station 4

Station 1 Station 2 Station 3 Station 4

Introduction 1

___________________________________________________________________________

1/9

A

1.2-5 RedundancyWhere a network architecture is designed to ensure reliable and safe operation,redundancy generally involves the use of a multi-network architecture; an example ofa basic ETHWAY architecture is shown below.The ETHWAY network architecture does not provide any redundancy in the event of aserious problem on the network. It is possible however to ensure a high level of safetyvia the application program as shown below :

All stations are connected to two separate ETHWAY networks, networks N1 and N2, viatwo TSX ETH 107 interface modules.Each station will therefore have two network-station addresses : N1S1 on ETHWAYnetwork N1 and N2S2 on ETHWAY network N2.

The application program of each PLC periodically checks its ability to access all stationsvia network N1.

If all stations can be accessed, the messages destined for other stations will be sent withthe N1S1 address of the target station.If a problem is encountered, the PLCs will switch to the second network by replacing theN1S1 target address of the station with its N2S2 address.

A B C D

Network N2

Network N1

1/10___________________________________________________________________________

A

1.2-6 BridgeThe bridge allows two different functions on a corporate network : division of the localarea network in two to improve performance levels, and connection of two local orremote networks with the same topology to authorize exchanges and the sharing ofdata.

The bridge provides a multi-network architecture as described in section 1.2-3 andshown below :

Comment

The bridge operates to level 2 of the ISO layer (see section 1.3) and therefore doesnot perform any protocol conversion. In this example, this connection is possiblesince the ETHWAY layers 1 and 2 are identical to those of Ethernet/Decnet.

ETHERNET/DECNET

ETHWAY

FIPWAY

FIPWAY

CAD CAM Sales Scheduling

Bridge

TSX 7 TSX 7

CCX77

IBM PC Cell 1 Cell 2 Cell n

Introduction 1

___________________________________________________________________________

1/11

A

7

6

5

4

3

2

1

1.3 The OSI model as defined by the ISO standard1.3-1 Introducing the modelCompatibility between different types of device can only be ensured by following thedefinition of connection standards which describe the behavior of each device withregard to others. These standards have been designed by the ISO (InternationalStandards Organization) which has defined a standard Network Architecture betterknown as the OSI MODEL (Open Systems Interconnection).This model consists of seven hierarchical layers, each fulfilling the defined function asrequired for the connection of systems to one another.

Layers from one device communicate with equivalent layers of other devices viastandard protocols. Within the device, layers communicate with those next to them viahardware or software interfaces.

STATION 1 STATION 2

Application

Presentation Layers designed fordata processing

Session

Transport

Network

Data link Layers designed forcommunication

Physical

Physical connection medium

1/12___________________________________________________________________________

A

1.3-2 Physical layerThis handles the transparent transmission of binary elements between two systems bymeans of a communication medium.

It provides the mechanical, electrical and functional means as well as the necessaryprocedures to operate, maintain and deactivate the physical transmission connections.

Example : This layer defines transmission procedures (half and full duplex), the type oflink (parallel or serial), data coding, the operation of electrical interfaces, etc.

1.3-3 Data link layerThis handles data transfers between two adjacent systems and incorporates errordetection.

It must ensure a reliable transfer, by detecting and correcting transmission errors andordering 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 theMAC sub-layer (medium access control).

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.

2

1

L.L.C.Data linklayer

Data link M.A.C.

Physical Physical

Introduction 1

___________________________________________________________________________

1/13

A

1.3-4 Network layerThis handles data routing and selects a path between two devices located on differentnetworks.

The network layer controls the general operation of the transmission. It is this layer whichchecks 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. Thenetwork layer defines the best route to optimize the transfer. It also controls the flow toavoid congestion on the network.It is completely independent from the topological structure of the network.

1.3-5 Transport layerThis handles data transfers between two systems, reliably and transparently.

It also controls the service quality. It is said that it provides the entire transport betweentwo remote stations.

The transport layer optimizes the use of available network services to provide in aneconomical way the performance levels required by each session unit.

1.3-6 Session layerThis layer organizes and synchronizes dialog between two application processes, andis responsible for organizing their data.The session function can temporarily cut the communication, interrupt and resume atask (activity) which can be executed in several stages; the session layer manages thisdialog by assigning restart or transmission rights.

1/14___________________________________________________________________________

A

1.3-7 Presentation layerThis handles the representation of data passing between application processes. ThePresentation layer actually exchanges structured data by providing them with a commonpresentation. 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 thesedifferences, 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 beencompressed due to cost reasons.

1.3-8 Application layerThe Application layer is a high level service, which provides the means of accessing thecommunication system, and acts as a window between the processes which worktogether on the different systems. As these systems and applications may varyconsiderably, 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.

Introduction 1

___________________________________________________________________________

1/15

A

1.4 Positioning of the various networks in the OSI model1.4-1 X-WAY and OSI modelThe X-WAY architecture which is common to all PLCs in the TSX series 7 range, isintegrated in the OSI model as shown below :

Whichever network is used, the application interface remains identical and theUNI-TE services are always available.

UNI-TE

Application-to-application communication7 Application

COM

Shared Remotetable I/O

6 Presentation

5 Session

4 Transfer

3 Network X-WAY addressing

2 Data link Master/Slave ISO 8802.2/3 FIP FIPEthernet WORLDFIP WORLDFIP

1 Physical RS 485 ISO 8802.3 FIP/WORLDFIP FIP/WORLDFIP(RS 232 20 mA CL) 10 Mbits/s 1 Mbits/s 1 Mbits/s

UNI-TELWAY ETHWAY FIPWAY FIPIO

1/16___________________________________________________________________________

A

1.4-2 UNI-TELWAYUNI-TELWAY is fully integrated into the TSX Series 7 communication architecture. Thisarchitecture corresponds to the OSI model with an application layer (UNI-TE) and anetwork layer (addressing system) which are common to various communicationinterfaces : 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 (addressingsystem) that are common to various communication interfaces : programming port

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.

UNI-TE message handling system

Read/Write variablesOperating mode

7 Application DiagnosticsProgram up/download

Application-to-application communication

Standard

6 Presentation

5 Session

4 Transport

3 Network X-WAY addressing

2 Data link Access to the network : Master/Slave

1 Physical RS 485 1200 b/s to 19200 b/s

Introduction 1

___________________________________________________________________________

1/17

A

1.4-3 FIPWAYFIPWAY is a low-cost cell network which conforms to the FIP standard. It is integratedin the X-WAY communication architecture.

The presentation, session and transport layers (6, 5 and 4) are not supported, as theyare not required by the targeted applications.

Note :The technical characteristics of the different layers are described in detail in the FIPWAY manualref. : TSX DG FPW.

UNI-TE message handling system Exchange of cyclic data

- Read/Write variables - COM word- Operating mode - Shared table- Diagnostics- Program up/download

7 Application

Application-to-applicationcommunication

- Standard- Priority

6 Presentation

5 Session

4 Transport

3 Network X-WAY addressing

2 Data link FIP/WORLDFIPProducer/Consumer type exchange

1 Physical FIP/WORLDFIPShielded twisted pair 1 Mb/s

1/18___________________________________________________________________________

A

1.4-4 FIPIOFIPIO is the fieldbus for TSX Series 7 and APRIL Series 1000 PLCs. It conforms to theFIP standard and is integrated in the X-WAY communication architecture.The presentation, session and transport layers (6, 5 and 4) are not supported, as theyare not required by the targeted applications.

UNI-TE message handling system Exchange of cyclic data

- Read/Write variables - Exchange of7 Application - Operating mode I/O data

- Diagnostics- Program up/download

6 Presentation

5 Session

4 Transport

3 Network X-WAY addressing

2 Data link FIP/WORLDFIPProducer/Consumer type exchange

1 Physical FIP/WORLDFIPShielded twisted pair 1 Mb/s

Introduction 1

___________________________________________________________________________

1/19

A

1.4-5 ETHWAYETHWAY is the X-WAY communication profile for Ethernet.

It meets Ethernet ISO 8802.3 standards and ETHWAY devices can be connected to anyexisting installation and work with third-party devices which comply with this standard.

UNI-TE message handling system Distributed database

- Read/Write variables - COM word- Operating mode- Diagnostics- Program

7 Application up/download

Application-to-applicationcommunication

- Standard- Priority

6 Presentation

5 Session

4 Transport

3 Network X-WAY addressing

2 Data linkLLC ISO 8802.2MAC ISO 8802.3

1 Physical CCMA-CDISO 8802.3

1/20___________________________________________________________________________

A

Services 2

___________________________________________________________________________

2/1

A

2.1. Introduction to the servicesEach of the networks described in the previous section supports one or more industrialmessage handling services, as shown in the table below :

Services NetworkUNI-TE UNI-TELWAY

FIPWAYFIPIOETHWAY

Application-to-application communication FIPWAY- standard ETHWAY- priority (TLG) UNI-TELWAY (except TLG)Common words (COM) FIPWAY

ETHWAY

Remote I/O FIPIOShared table(s) FIPWAY

Section 22 Services

2/2___________________________________________________________________________

A

2.2. UNI-TE service2.2-1 PresentationUNI-TE is an industrial message handling system providing broadcast or point-to-pointcommunication using a question/answer mechanism called Request/Confirmation.The application layer provides the user with standard services which can have servicesadded to them which are specific to PLCs, machine tool numerical controllers, robots,etc.

2.2-2 CLIENT-SERVER conceptA 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 aconfirmation after execution.

Some devices may be both CLIENT and SERVER simultaneously. For example, a PLCis a SERVER during its system tasks (programming, adjustment, diagnostics, etc), anda CLIENT, via the user program text blocks (sending commands, reading status data,etc), in relation to another PLC, machine tool numerical controller, sensor orpreactuator.

Request

CLIENT SERVER Action

Confirmation

Services 2

___________________________________________________________________________

2/3

A

2.2-3 List of requestsThe standard UNI-TE requests that are listed in detail in section B.2 with their coding,provide the following services :

ACCESS TO DATAThese 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 DATAThis is the only service which does not generate a confirmation as it is already aresponse to an implicit question.

This service will transfer a byte string from one application program to another withoutit having been requested first.The actual use of this data is the responsibility of the destination device which is implicitlyawaiting this data.

GENERAL USEThese requests are especially useful for diagnostics and on power-up (device andapplication protocol identification, system and communication path tests, etc) : identification, mirror, protocol version, communication control, read status.

CLIENT SERVER

APPLICATION APPLICATION Event

Unsolicited data

2/4___________________________________________________________________________

A

OPERATING MODEThese requests are used to run or stop a device connected to the bus. They can alsoinitialize the device and run a self-test sequence : Run, Init. Stop,

SEMAPHORE MANAGEMENTThese requests are used for device reservation, dereservation or hold reservationfunctions : reservation, hold reservation, dereservation.

FILE TRANSFERThese 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 productdocumentation to ascertain which standard requests are supported, together withtheir specific parameters and how they affect the device.

Services 2

___________________________________________________________________________

2/5

A

2.3 Common word service : COM serviceThe COM service is used to exchange numeric data (common words) between devicesforming part of the series 7 range.The complete set of common words forms a database which is distributed among someor 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 samenumber of common words.

Each module which uses the COM service has a memory zone of 256 words of 16 bitswhich 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 maximumof :- 4 COM words per station for 64 active stations,- 8 COM words per station for 32 active stations,- 16 COM words per station for 16 active stations,- 32 COM words per station for 8 active stations,- 64 COM words per station for 4 active stations.

Stations which are declared active for the exchange of COM words must have lownetwork addresses (eg for 32 stations which each handle 8 COM words, thesestations must be numbered from 0 to 31).

2/6___________________________________________________________________________

A

Operating principleWhen the common words of a station have been updated by the CPU, they arebroadcast on the network.

On reception, the network interface of any PLC using the COM word service updates thecorresponding zone and makes them available to the CPU.Use of the distributed database is recommended for the periodical broadcasting ofstatus variables without adding extra application program workload. To send data onbrief events, application-to-application communication with a confirmation isrecommended as transmission is guaranteed.

OPERATECOM 0.1

OPERATECOM 0.1

Station 0 Station 1 Station 63 max

Write : Read :to COM zone in the station possible by all connected stations

Common memory zone(256 words of 16 bits)

%NW{1}1%NW{1}1

Services 2

___________________________________________________________________________

2/7

A

2.4 Shared table serviceThis 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 intoas many zones as there are PLCs on the network.

The principle of these exchanges is based on each PLC broadcasting one of thesezones 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 principleThese exchanges are based on the principle of broadcasting, by each device, of oneword memory zone (broadcast zone) to other devices on the network. All exchangedwords form the exchange zone, which must be defined in each device and have thesame length in all of them.

@0

@30

@40

@100

@120

@127

@1000

@1030

@1040

@1100

@1120

@1127

Device 1 Device n

Broadcast zonePLC n 1 Zone PLC n 1

Zone PLC n 2 Zone PLC n 2

Zone PLC n 31 Zone PLC n 31

Zone PLC n 32 Zone PLC n 32

2/8___________________________________________________________________________

A

Sending dataPLC n 1 broadcasts the data from its broadcast zone to all PLCs.

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

PLC n 2 then broadcasts the data from its broadcast zone to all PLCs.

The exchange table in each PLC is updated separately from the PLC program. Theseexchanges are cyclic.Note :The Shared Table and COM words service are exclusive on the same network.

Write

PLC n 1 PLC n 2 PLC n 16

Z. PLC1 Z. PLC1 Z. PLC1

Z. PLC2 Write Z. PLC2 Z. PLC2

PLC n 1 PLC n 2 PLC n 16

Z. PLC1 Z. PLC1 Z. PLC1

Z. PLC2 Z. PLC2 Z. PLC2

Services 2

___________________________________________________________________________

2/9

A

2.5 Application-to-application communication2.5-1 StandardThis service provides point-to-point communication from application program toapplication program. The partner devices in question are Series 7 and Series 1000PLCs.

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 whenboth partners are Series 1000 PLCs, otherwise the maximum size is 256 characters.

This service can be installed using dedicated function blocks or by sending the UNI-TE"Unsolicited data" request does not require a confirmation.

Station 0 Station 1 Station 15

Table of internal words(16 or 32 bit words, floating point objects and characters)

2/10___________________________________________________________________________

A

2.5-2 Priority exchangesThe telegram service is a special type of application-to-application message designedfor transmitting urgent, high priority and infrequent data between two PLCs on the samenetwork.

A telegram from the PLC processor is sent immediately to its network module withoutwaiting 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

ProcessingTSX 37 TSX 37

Outputs

Services 2

___________________________________________________________________________

2/11

A

2.6 Remote Input / Output servicesThis FIPIO service is used to exchange input status variables and output commands.These exchanges are performed cyclically and automatically without any interventionfrom the application program.This service is also used to manage remote devices (configuration, etc). Theseexchanges are aperiodic without any intervention from the application program.In order to use this service, the remote inputs / outputs must be configured with thecorrect 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 usedfor diagnostics and maintenance purposes.

2/12___________________________________________________________________________

A

X-WAY addressing mechanisms 3

___________________________________________________________________________

3/1

A

3.1 GeneralThis section describes the general addressing rules for assigning an address toeach 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 partydevice, etc).

In a communication architecture, all exchanges are generally in point-to-point modebetween two logical entities (client and server). These logical entities must be identifiedby 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 haveseveral network addresses.

Section 33 X-WAY addressing mechanisms

Terminal station Station i Address = N1S2

Network 1

Intermediate stationStation j Address = N1S1 Station k Address = N1S3

Address = N2S2

Network 2

Station l Address = N2S1 Station m Intermediate stationAddress = N2S3Address = N3S1

Network 3

Terminal station Station n Address = N3S2

3/2___________________________________________________________________________

A

station levelThis level is used to address an entity in the station.

A station which is connected to a network consists of a series of communicationentities which are located in the station itself as well as the devices connected to itsinternal communication channels (FIPIO bus, PLC backplane bus, UNI-TELWAYbus, 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).

ExamplesNetwork 1

Station 1 Station 2Module 0 Module 3channel 1 channel 1

Connection Module 1point 6 channel 15

Connectionpoint 22

X-WAY addressing mechanisms 3

___________________________________________________________________________

3/3

A

3.2 Communication entities3.2-1 PresentationPLCs and devices which can be connected to an X-WAY network generally consist ofone 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. PLCsfor 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 entitiesEach communication module manages one or more channels which can either be thesame or different type and has entities which are unique within this module. PLCmodules for example can have the following entities : UNI-TE client/server, network management, etc

3.2-4 Communication channel level entitiesCommunication channel level entities generally correspond to devices (and theircommunication entities) connected to the bus or the network stemming from thatchannel. PLC modules for example can have the following entities : UNI-TE client/server, PL7 application, etc

3/4___________________________________________________________________________

A

3.3 Address format3.3-1 PrinciplesThe general format for describing the address of a destination entity which is part of anX-WAY network is described below :

3.3-2 Network number-station numberThe "Network number" field shows the network number of the destination station duringthe exchange. It must be between 0 and 127.The "Station number" field shows the number of the destination station during theexchange. It must be between 0 and 63.

3.3-3 Broadcast addressA broadcast corresponds to the sending of messages to all stations on a network or toall communication entities of the same station.

The FF value, which is defined to describe a broadcast, can replace one of the elementsof a topological address. The broadcast level is determined according to the location ofthat 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 tonetwork 2),

associated with a communication channel, messages are broadcast to all entitiesconnected to that channel (example : 2.4.5.1.FF provides access to all communicationentities on the UNI-TELWAY bus which are located in slot 1 of rack 0 in station 4 onnetwork 2).

Address of an entity on an X-WAY network

Remote address (inter-station) Local address (intra-station)

Network N Station N followed Physical addressby the local address

X-WAY addressing mechanisms 3

___________________________________________________________________________

3/5

A

5 16...990 81, 2, 3

3.4 Introduction to hierarchical addressingThe address of a target communication entity of an exchange is organized in a hierarchyon several levels (three, five or six).

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). Seesection 3.7 for further details.

Network 2NETWORK

Station 4

STATION

System Terminal Communication ApplicationGATE port module

MODULE SELECTOR

CHANNEL CONNECTION POINT

REFERENCE

3 levels 5 levels 6 levels

16...249

3/6___________________________________________________________________________

A

3.5 Three level addressing3.5-1 PresentationAddressing which is organized into a hierarchy over three levels and used for accessinga communication module entity.

Network numberShows the network number of the destination station of the exchange. Is between 0 and127.

Station numberShows 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 numbermust have the value 255.

Gate numberThe 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 identifiedby 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"

X-WAY addressing mechanisms 3

___________________________________________________________________________

3/7

A

3.5-2 ExampleThe address of certain communication entities is organized into a hierarchy over threelevels. 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 :

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.

Network 2

System : 2.4.0 Terminal port : 2.5.1

Text block 6 : Communication function:2.4.22 Station 4 2.5.16 Station 5

3/8___________________________________________________________________________

A

5

3.6 Five level addressing3.6-1 PresentationAddressing organized into a hierarchy over five levels and accessible via gate five isused to access a channel of a communication module :

Network 2NETWORK

Station 4

STATION

CommunicationGATE module

Channel 0

MODULE Rack/Slot

Channel 1Channel n Channel n Channel n

104 101 1CHANNEL

Address Address Address4 1 1

X-WAY addressing mechanisms 3

___________________________________________________________________________

3/9

A

The network, station and gate numbers were defined in section 3.5-1.Module numberOnly used if the gate number is 5 (access to a communication module), the modulenumber corresponds to the physical location of this module on the backplane bus (racknumber and slot in the rack).Channel numberOnly used if the gate number is 5 (access to a communication module), the channelnumber corresponds to the address of the device connected to the network or bus fromthe module selected.

The devices connected to channel 0 of the module can be accessed directly via theiraddress (if, for example, communication with the device at address 5 on channel 0 isrequired, the channel number must take the value 5). The value 99 is used forbroadcasting 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 isrequired, the channel number must take the value 105). The value 199 is used forbroadcasting to all channel 1 devices.

A slave PLC connected to a UNI-TELWAY bus can, for example, have up to threeaddresses : a system address (known as Ad0)

This address is compulsory. All messages received at this address are transmitted tothe 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. Itauthorizes the transmission of requests to any UNI-TELWAY address (system gateor master PLC / other slave application) and the reception of responses or associatedconfirmations,

a text reception address (known as Ad2)This optional address is assigned to the slave module for the reception of unsoliciteddata from another device in the architecture. The messages received on this addressare 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 UNI-TELWAY bus connected to channel 1 of a communication module, can be accessed viathe following channel numbers : channel 110 for Ad0, channel 111 for Ad1, channel 112 for Ad2.

3/10___________________________________________________________________________

A

3.6.2 ExampleThe address of certain communication entities is organized into a hierarchy over fivelevels. This applies particularly to devices connected to a channel of a communicationmodule.

Example of five level addressing :

2.4.5.06.114 Access to the ATV 16 system : network 2, station 4, gate 5 (access to thecommunication module), module 06 (rack 0 slot 6), channel 114 (link addressof the destination device + 100 as it is channel 1 of the communication modulewhich is used).

2.4.5.06.103 Access to the CPU system of the slave PLC on the UNI-TELWAY bus : network2, station 4, gate 5 (access to the communication module), module 06 (rack 0slot 6), channel 103 (address Ad0 + 100 as it is channel 1 of the communicationmodule 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 thecommunication module which is used).

Network 2

Station 4Communication module installedin slot 6 of rack 0.Channel 1 used.

System : 2.4.5.06.114 Link address 14

System : 2.4.5.06.103Ad0 = 3Ad1 = 4Ad2 = 5

Application : 2.4.5.06.105

Uni-T

elwa

y

X-WAY addressing mechanisms 3

___________________________________________________________________________

3/11

A

3.7 Six level addressing3.7-1 PresentationAddressing organized into a hierarchy over six levels, which can only be accessed viagate 8, is used to physically identify application entities in a station made up of severalcommunication channels (TSX 57 for example) :

8

1 2

107410

Network 2NETWORK

Station 4

STATION

CommunicationGATE module

Module in ModuleSELECTOR the integrated in

backplane bus the CPU

CONNECTION POINT

UNI-TE UNI-TE UNI-TE UNI-TE UNI-TEREFERENCE Server Client Server Server Server

System System Channel 0 Channel 1 Channel 2

3/12___________________________________________________________________________

A

The network, station and gate numbers were defined in section 3.5-1.

Channel selector numberThis parameter identifies the communication channel within the station to which thedestination 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 theCPU).

Connection point numberThis parameter identifies the destination device of the exchange by its connection pointnumber 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, thesystem of a communication module), the connection point number corresponds to theslot 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 connectionpoint number must have the value 255.

Reference numberThis parameter identifies the communication entity in the destination device of theexchange.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).

X-WAY addressing mechanisms 3

___________________________________________________________________________

3/13

A

3.7-2 ExampleThe address of certain communication entities is organized into a hierarchy over sixlevels. This applies particularly to application entities in a station made up of severalcommunication channels.

Example of six level addressing :Network 6

Terminal port (channel 0) : Station 2 Channel 0 : 6.2.8.1.3.46.2.8.1.0.4

FIPIO link (channel 2) : 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 186.2.8.2.18.0

3/14___________________________________________________________________________

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 onthe 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 overthree 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,station 2, gate 8 (extended addressing), selector 1 (communication module onthe backplane bus), connection point 0 (the CPU is module 0), reference 10(channel 2).

6.2.8.2.18.0 Access to the ATV 16 system : network 6, station 2, gate 8 (extendedaddressing), selector 2 (exchange with a device connected to the bus or thenetwork from the communication module integrated in the CPU), connectionpoint 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,station 2, gate 8 (extended addressing), selector 1 (communication module onthe backplane bus), connection point 0 (the CPU is module 0), reference 7(channel 1).

6.2.8.1.3.4 Access to the server of channel 0 of the module located in slot 3 : network 6,station 2, gate 8 (extended addressing), selector 1 (communication module onthe 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 backplanebus), 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 inslot 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).

Appendix 4

___________________________________________________________________________

4/1

A

4.1 X-WAY frame format4.1-1 Presentation

This section describes the general addressing rules used for assigning an addressto each communication entity in an architecture. It is to be read only by informedusers, who want to install a line analyzer on a network, code an address from a third-party device, etc).

The general format of a network datagram is as follows :

Preamble and endThese 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, referto the reference manual for the network concerned).

CRC and Link layer dataThese two pieces of information are linked to the Data link layer. They are specific to thetype of network used (for more information on their coding, refer to the reference manualfor the network concerned).

X-WAY frameThe X-WAY frame contains all the information required for inter-station exchanges.Details are given in the following sections.

Shared dataThe frame reserved for shared data contains all the information required for periodicexchanges (common words, remote inputs/outputs, etc). Details are given in section4.1-8.

Section 44 Appendix

Physical Layer Preamble End

Data link Layer Link layer data CRC

Network Layer (message handling system) X-WAY frame

Application Layer (message handling system) Data

Application Layer (shared data) Shared data

4/2___________________________________________________________________________

A

4.1-2 X-WAY frameThe X-WAY frame is made up as follows :

NPDU Addresses 3 and 5 level 6 level Datatype addressing addressing extension (message system)

NPDU type (Network Protocol Data Unit)This field is linked to the network layer. It is described in section 4.1-3.

AddressesThis field shows the addresses (network, station and gate numbers) of the sender anddestination of the exchange. It is described in section 4.1-4.

Three and five level addressingThis field defines the addresses of the exchange sender and destination communicationentities when addressing is structured into three or five levels (module, channelnumbers, etc). It is described in section 4.1-5.

Six level addressing extensionThis field defines the addresses of the exchange sender and destination communicationentities when addressing is structured into six levels (selector, connection pointnumbers, 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 thedestination entity is on six levels, the two fields "Three and five level addressing" and"Six level addressing extension" are filled in.

Appendix 4

___________________________________________________________________________

4/3

A

4 bits 2 bits 1 bit 1 bit

Type Level of Refusal Ext.service

4.1-3 NPDU type

TypeTakes one of the following values : 0 to 14 Reserved, 15 NPDU data.

Level of serviceTakes one of the following values : 0 Standard, 1 Telegram, 2 to 3 Reserved.

RefusalTakes one of the following values : 0 Message accepted, 1 Message refused.

ExtensionTakes one of the following values : 0 if one of the devices (sender or destination) uses addressing on three or six

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

for the exchange concerned.

NPDU Addresses Five level Six level Datatype addressing addressing (message system)

4/4___________________________________________________________________________

A

4.1-4 Addresses

Station numberCorresponds to the station number (of the sender or the destination). The stationnumber must be between 0 and 63 (the value 255 is reserved for broadcasting).Network numberCorresponds to the network number (of the sender or the destination). The networknumber must be between 0 and 127.When the value is greater than 15, an address extension is required.Gate numberCorresponds to the gate number targeted in the destination entity of the exchange.Takes one of the following values : 0 access the system of the device, 1, 2, 3 access the terminal port of a PLC, 5 access a communication module (addressing structured on five levels), 8 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.

2 bytes 2 bytes

Sender address Destination address

1 byte 4 bits 4 bits

Station Network Gatenumber number number

NPDU Addresses 3 and 5 level 6 level Datatype addressing addressing extension (message system)

Appendix 4

___________________________________________________________________________

4/5

A

4.1-5 Five level addressing

The various possibilities are shown in the table below :

Parameter value Identifier Length

Sending gate n if > 15 0 1Destination gate n if > 15 1 1Sending network n if > 15 2 1Destination network n if > 15 3 1Module n and channel n 4 2of the senderModule n and channel n 5 2of the destination

8 bits 8 bits

Module Channelnumber number

Parameter 1 Parameter 2 Parameter n

Length (in bytes) of the value1 if last parameterIdentifier

1 byte 1 to 7 bytesParameter code Parameter value

NPDU Addresses 3 and 5 level 6 level Datatype addressing addressing extension (message system)

4/6___________________________________________________________________________

A

4.1-6 Six level addressingReminder : six level addressing can be accessed via gate 8

The various possibilities are shown in the table below :

Parameter value Identifier Length

Compacted physical 6 2sender addressCompacted physical 7 2destination addressExtended physical 6 3sender addressExtended physical 7 3destination address

Parameter 1 Parameter 2 Parameter n

Length (in bytes) of the value1 if last parameterIdentifier

1 byte 1 to 7 bytesParameter code Parameter value

4 bits 4 bits 8 bits

Selec- Refe- Connect.tor rence point

8 bits 8 bits 8 bits

Selec- Refe- Connect.tor rence point

NPDU Addresses 3 and 5 level 6 level Datatype addressing addressing extension (message system)

Appendix 4

___________________________________________________________________________

4/7

A

4.1-7 Data (message handling system)

Transmitted data is structured in one of the three following ways :

Received data is structured as follows :

Data for theUNI-TE service

Request code Category code Transmission data1 byte 1 byte 1 to 254 bytes

Application-to-application data (text block, function block, etc)1 to 256 bytes

Telegram type data1 to 16 bytes

Confirmation Response data1 byte 0 to 255 bytes

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

4/8___________________________________________________________________________

A

4.1-8 Distributed dataDistributed data, at Application layer level, is specific to periodic data exchanges(common words, remote I/O, etc).

Distributed data is structured as follows :Common wordsShared 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 (ManufacturingPeriodical Services). Their frame is as below : APDU Data type Status 1 byte 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.

DataThe 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 syntaxis specific to the type of information circulating (series of bits for discrete modules, seriesof words for analog modules, etc).

StatusThis parameter indicates whether the cyclic variables have really been updated by theirproducer. It takes one of the following values : 1 The cyclic variables have been updated, 0 The cyclic variables have not been updated.

Appendix 4

___________________________________________________________________________

4/9

A

Common words on ETHWAYThe data specific to this service is structured as below :

Station Size ofnumber COM Common words1 byte 1 byte 8 to 128 bytes

Station numberThis parameter indicates the number of the station sending the common words.

Size of COMThis parameter indicates the size of the common words exchanged on the network.

Common wordsThis byte string corresponds to the value of the common words transmitted.

4/10___________________________________________________________________________

A

ContentsPart B

Section Page

___________________________________________________________________________

B/1

B

1 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/31.3-1 Presentation 1/31.3-2 Link with an XWAY frame 1/41.3-3 Description of a UNI-TE request 1/5

1.4 Type of data used 1/7

ContentsPart B

Section Page

B/2___________________________________________________________________________

B

2 Request coding 2/1

2.1 List of UNI-TE requests 2/2

2.2 General use requests 2/32.2-1 Identifying a device 2/32.2-2 System diagnostics for a programmable device 2/82.2-3 Exchange of UNI-TE characteristics between the

Client/Server 2/102.2-4 Communication test 2/12

2.3 Requests to access standard objects 2/132.3-1 Read an internal bit 2/132.3-2 Write an internal bit 2/142.3-3 Read a system bit 2/152.3-4 Write a system bit 2/162.3-5 Read an internal word 2/172.3-6 Write an internal word 2/182.3-7 Read a system word 2/192.3-8 Write a system word 2/202.3-9 Read a constant word 2/212.3-10 Force an internal bit 2/222.3-11 Read Grafcet step status 2/23

2.4 Requests to access the objects of an I/O module 2/252.4-1 Read the memory image of a simple discrete module 2/262.4-2 Write memory image bit of a simple discrete module 2/292.4-3 Read the status of a module 2/312.4-4 Read the objects of an I/O channel 2/342.4-5 Write the objects of an I/O channel 2/37

ContentsPart B

Section Page

___________________________________________________________________________

B/3

B

2.5 Requests to access generic objects 2/392.5-1 Identification of objects 2/392.5-2 Access parameters 2/402.5-3 Read an object 2/422.5-4 Write an object 2/442.5-5 Read a generic object 2/452.5-6 Write a generic object 2/472.5-7 Read a list of objects 2/492.5-8 Write a list of objects 2/512.5-9 Action on an object 2/52

2.6 Operating mode management requests 2/542.6-1 Launching an application or task 2/542.6-2 Stopping an application or task 2/552.6-3 Initialization 2/56

2.7 Data transfer requests 2/572.7-1 Start downloading 2/582.7-2 Downloading a segment 2/592.7-3 Ending a downloading sequence 2/602.7-4 Launching a backup sequence 2/612.7-5 Backing up a segment 2/622.7-6 Ending a backup 2/632.7-7 Memory transfer and comparison 2/64

2.8 Semaphore management request 2/652.8-1 Reservation 2/652.8-2 Release 2/662.8-3 Hold a reservation 2/67

ContentsPart B

Section Page

B/4___________________________________________________________________________

B

3 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/63.4-1 Timer objects 3/63.4-2 Monostable objects 3/73.4-3 Counter object 3/73.4-4 Register objects 3/83.4-5 Drum controller 3/83.4-6 Fast counter object 3/93.4-7 "Pulse width modulation" object 3/93.4-8 "Pulse train generation" object 3/103.4-9 "Shift register" object 3/103.4-10 "Step register" object 3/113.4-11 "Operator dialog message" object 3/113.4-12 Real-time clock object 3/12

General principles of the UNI-TE protocol 1

___________________________________________________________________________

1/1

B

1.1 Description of the servicesThe UNI-TE protocol respects the client/server model.

The client entity prepares the request to be transmitted to the server. This interprets therequest 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 requestsare the exceptions to this rule.

The confirmation gives the result of the operation performed by the server. There arethree possibilities :

Request Request code + 30H The operation has been performed byconfirmation Request exception the server, additional data

Mirror summarizes the result of the operation

Positive FEH The operation has been performedconfirmation correctly and no additional

data is transmitted in theresponse

Negative FDH The operation could not be executedconfirmation by the server : unknown

request, value out of range,configuration absent, etc

Section 11 General principles of the UNI-TE protocol

Request

SERVER

CLIENT Requestprocessing

Confirmation

1/2___________________________________________________________________________

B

1.2 UNI-TE V1.1 and V2.0The UNI-TE V1.1 protocol is incorporated in communication systems which areintegrated 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. Thedifferences between the two versions are shown in a correspondence table (this tableis in the appendix, section 3).

General principles of the UNI-TE protocol 1

___________________________________________________________________________

1/3

B

1.3 UNI-TE exchange format1.3-1 PresentationThe general structure of an exchange observes the following format. It depends on theUNI-TE protocol version.

Request format

Transac- Request CategoryF9H tion code codeData specific to

number the request

Confirmation format

Transac- Confirma-F0H tion tionData specific to the

number confirmation

UNI-TE V2.0 is a superset of UNI-TE version V1.1

1/4___________________________________________________________________________

B

1.3-2 Link with an XWAY frameSummaryA UNI-TE request (question or confirmation) is integrated in an XWAY frame asindicated below (more detailed information on coding an XWAY frame is described insection 4.1 in part A) :

Request

Confirmation

Header NPDU Addresses Data EndAddressing

5 levelsAddressing

6 levels

F9H DataRequest

codeCategory

codeTransaction

number

F0H DataConfirma-

tionTransaction

number

General principles of the UNI-TE protocol 1

___________________________________________________________________________

1/5

B

1.3-3 Description of a UNI-TE requestThe general structure of a UNI-TE request observes the following format :

Request format

Transac- Request Category DataF9H tion code code specificnumber 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 toassociate a response with the request sent and thus, avoid any possible mixing ofresponses. The header byte (F9H), and the transaction number are managed by thesystem and are thus transparent to the user. They are nevertheless transmitted on thesupport during transmission of the message.

Confirmation format

Positive confirmation with no specific data

Transac- FEHF0H tion confirma-

number tion

1 byte 1 byte 1 byte

Negative confirmation with no specific data

Transac- FDHF0H tion confirma-

number tion

1 byte 1 byte 1 byte

Positive confirmation with specific data

Transac- Confirma-F0H tion tion reportData specific to

number the request

1/6___________________________________________________________________________

B

Note :A device which supports the UNI-TE V2.0 protocol will code its requests in the UNI-TE V2.0. Dueto the compatibility of the various V1.1 and V2.0 requests, a V1.1 level server will respond to aUNI-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.

General principles of the UNI-TE protocol 1

___________________________________________________________________________

1/7

B

1.4 Type of data usedThe 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, etcThe UNI-TE protocol has specific coding for each type :

Type Comments on the codingBit 1 bit

Value 0 : false / Value 1 : trueByte Series of 8 bits16-bit unsigned integer Byte 0 : least significant / Byte 1 : most significant16-bit signed integer Two's complement32-bit signed integer Two's complementSingle length floating point IEEE 754 formatVariable length The first byte describes the length in number of significant bits inbit string the string. The number of bits is limited to 256.

An additional type can be defined for usinga length greater than 2 bytes.For example : a 19-bit string is coded :

byte 0 byte 1 byte 2 byte 3

length = 19 7 . . . . 0 15 . . . . 8 23 . . . 9 . . . 16

not significantFixed length There is no length byte at the beginning of the tablebyte tableVariable length The first byte gives the length of the tablebyte table

length = 4 byte 0 byte 1 byte 2 byte 3

1/8___________________________________________________________________________

B

Type Comments on the codingFixed length There is no length byte at the beginning of the tablebyte tableVariable length The first byte gives the length of the tablebyte table

length = 3 byte 1 = 'A' byte 2 = 'T' byte 3 = 'S'

Fixed length The length byte at the beginning of the string is not usedcharacter stringVariable size 16-bit The first byte gives the length of the table inword table number of wordsFixed size 16-bit The length byte at the start of the table is not usedword table

Request coding 2

___________________________________________________________________________

2/1

B

This section describes the coding of requests associated with UNI-TE V2.0 and V1.1services.

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 bytesare not shown in the presentation of messages in this document. They are howevertransmitted on the line.

When presenting confirmation frames the detailed coding is only given for positiveresponses with additional data (simple responses have been described in section 1.3).Confirmed requests have a compulsory field, called the "category code", used tomanage access rights (values 0 to 7). This code depends on the device concerned. Forexample, 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 otherrequests 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 thismanual. If no difference is mentioned, the frames are identical in both versions.

Section 22 Request coding

2/2___________________________________________________________________________

B

2.1 List of UNI-TE requests

Heading Request name Request Confirmationcode code

General use IDENTIFICATION 0FH 3FHGeneral use READ_CPU 4FH 7FHGeneral use PROTOCOL_VERSION 30H 60HGeneral use MIRROR FAH FBHStandard objects READ_INTERNAL_BIT 00H 30HStandard objects WRITE_INTERNAL_BIT 10H FEHStandard objects READ_SYSTEM_BIT 01H 31HStandard objects WRITE_SYSTEM_BIT 11H FEHStandard objects READ_INTERNAL_WORD 04H 34HStandard objects WRITE_INTERNAL_WORD 14H FEHStandard objects READ_SYSTEM_WORD 06H 36HStandard objects WRITE_SYSTEM_WORD 15H FEHStandard objects READ-CONSTANT-WORD 05H 35HStandard objects FORCE-INTERNAL-BIT 1BH FEHStandard objects READ-GRAFCET-BIT 2AH 5AHI/O modules READ_DIGITAL_MODULE_IMAGE 49H 79HI/O modules WRITE_DIGITAL_MODULE_IMAGE 4AH 7AHI/O modules READ_STATUS_MODULE 44H 74HI/O modules READ_IO_CHANNEL 43H 73HI/O modules WRITE_IO_CHANNEL 48H 78HGeneric objects READ_GENERIC-OBJECT 82H B2HGeneric objects WRITE_GENERIC_OBJECT 83H B3HGeneric objects READ_OBJECT 36H 66HGeneric objects WRITE_OBJECT 37H FEHGeneric objects ACTION_GENERIC_OBJECT 9FH CFHObject list READ_OBJECT_LIST 38H 68HObject list WRITE_OBJECT_LIST 39H 69HOperating mode RUN 24H FEHOperating mode STOP 25H FEHOperating mode INIT 33H 63HData transfer OPEN_DOWNLOAD 3AH 6AHData transfer WRITE_DOWNLOAD 3BH 6BHData transfer CLOSE_DOWNLOAD 3CH 6CHData transfer OPEN_UPLOAD 3DH 6DHData transfer READ_UPLOAD 3EH 6EHData transfer CLOSE_UPLOAD 3FH 6FHData transfer BACKUP 45H 75HSemaphore RESERVE 1DH FEHSemaphore RELEASE 1EH FEHSemaphore I_AM_ALIVE 2DH FEH

Request coding 2

___________________________________________________________________________

2/3

B

2.2 General use requestsThe UNI-TE protocol can identify and diagnose any type of device which has aUNI-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 deviceRequest name : IDENTIFICATION.This service supplies identification and structure data on the UNI-TE server which is thedestination of the request. The identification is general for all types of CPU devices,network module, communciation module, axis controllers, speed drives, numericalcontrollers, 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 cataloguereference 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/4___________________________________________________________________________

B

CommentA device which has several elements (eg : modular TBX, etc) gives in the responsethe complete identification of the elements of which it consists.

Request format

Request Categorycode code0FH 0 7

1 byte 1 byte

Confirmation format (UNI-TE V2.0)Confirm- Type of Number Identification

ation identi- Product Identification of com- of components3FH fication

range element ponents

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.

Product rangeType of applicationType of productCatalogue reference

Basic module 2 components (2 channels)Channel 1 Type of application

Type of productCatalogue referenceNo components

Channel 2 Type of applicationType of productCatalogue referenceNo components

Request coding 2

___________________________________________________________________________

2/5

B

Component identification :

Identification IdentificationAddress element Address element . . .

1 byte > 8 bytes 1 byte . . .

Etc.

These fields are present if the number of components is other than 0.

- Address number of logical channels- Identification element coding these parameters is identical to that described on

the previous page. Identification element :

Basic Basic Cata-ASCII Device Status of standard module module logue Status ofVersion string status indicator lamps type of type of Refer- basic module

application product ence

1 byte Character Bit 8-bit table 1 byte 1 byte 1 byte 8-bit tablestring string

- Version version number of device coded on two BCD 4-bit bytes- ASCII string product reference- Device status 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 = Does not exist1 = Autotest2 = Faulty3 = Ready/Run4 = Waiting5 = Not Configured6 = Stop.

If the server does not manage the information, the length field takes the value 0(see section 1.4).

2/6___________________________________________________________________________

B

- Indicator lamp status : the 8 bits show the status of the following indicator lamps :

- Basic module application type : for the value of this field, refer to specific productdocumentation,

- Basic module product type : for the value of this field, refer to specific productdocumentation,

- Catalogue reference : designates the device in the product type : for thevalue of this field, refer to specific productdocumentation,

- Basic module status :

Type of fault Bit n CommentInternal fault 0 Hardware failureOperating fault 1Terminal block fault 2 Terminal block absentSelf-test 3 Module performing self-testReserved 4Conf. fault 5 Modules not compatibleAbsent 6 Module absent or powered downDown 7 One of the modules supported is faulty

Coding bit 7 bit 0

00 Off Run indicator lamp01 Blinking Fault indicator lamp10 On I/O indicator lamp11 Not significant Other indicator

lamp

16#FF if not used

Request coding 2

___________________________________________________________________________

2/7

B

Confirmation format (UNI-TE V1.1)Confirm- Product

ation Type of sub- Version ASCII3FH

product type string

1 byte 1 byte 1 byte 1 byte Characterstring

Type of product coding this header is identical to that described in UNI-TEV2.0 confirmation

Version and ASCII string device version and product reference identical to itemswhich have the same name in UNI-TE V2.0

Product sub-type identification extension created in the product type field.

2/8___________________________________________________________________________

B

2.2-2 System diagnostics for a programmable deviceRequest name : READ_CPU.

This service enables system diagnostics to be performed on any device usingUNI-TE V2.0. This service does not exist in version 1.1.

Request format (UNI-TE V2.0)Request Category

code code Extension4FH 0 7

1 byte 1 byte 1 byte

Extension : reserved for future developments. The default value is 0

Confirmation format (UNI-TE V2.0)Confirm-

Status of standard Reserveration Extension indicator lamps CPU status address . . .7FH

1 byte 1 byte 8-bit table 8-bit table Byte table

Type of. . . application Debug Product Specific

error data range

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).

Request coding 2

___________________________________________________________________________

2/9

B

CPU status : logical status of a CPU or a device,

Reserver address : network address of the application which has reservedthe CPU (16#FFFFFF signifies "no current reservation")

Type of application error : additional data on the CPU status

Memory 0 no valid configuration2 several valid configurations

RAM memory can be executedand software error 0 Watchdog overflow

1 Application cannot be executedSoftware error 3 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, applicationcompatible with operating system, etc).

bit 7 bit 0

Run (1)/# of Run (0)Application can be executed (1)Memory cartridge present (1)Current reservation (1)BreakPoint complete stopApplication errorPartial runGrafcet Overrun

2/10___________________________________________________________________________

B

2.2-3 Exchange of UNI-TE characteristics between the Client/ServerRequest name : PROTOCOL_VERSION.

In a client/server relationship, this service can negotiate UNI-TE requests between the2 communicating entities.

Request formatList

Request Category Maximum Numbercode code size of of versions Version Version Version . . .30H 0 7 APDU supported

1 byte 1 byte 1 word 1 byte 1 byte 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.

Confirmation format (UNI-TE V2.0)List

Confirm- Maximum Numberation size of of versions Version . . . Version . . .60H APDU supported

1 byte 1 word 1 byte 1 byte 1 byte

Size List of. . . of the Horizontal requests

T-list conformity supported

1 word Bit Bitstring 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

Request coding 2

___________________________________________________________________________

2/11

B

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 :

Bit i : 1 if the request is managedBit i : 0 if the request is not managed

Confirmation format (UNI-TE V1.1)List

Confirm- Numberation Max. size of versions Version . . . Version Size of60H

of APDUsupported T-list

1 byte 1 byte 1 byte 1 byte 1 byte 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.0frame disappear.

0 0 0 0 1 0 0 10 1 0 0 1 1 1 01 1 1 0 0 1 1 0

Request code 00 Request code 08 Request (n-1) * 8Byte 0 Byte 1 Byte 2 Byte n

Length = nb bit

2/12___________________________________________________________________________

B

2.2-4 Communication testRequest 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 Categorycode code UserFAH 0 7

data

1 byte 1 byte Byte table

User data : series of bytes transmitted in the request which must be retransmittedin full in the response.

Confirmation format

Confirm-ation User FBH

data

1 byte Byte table

User data : retransmission of the series of bytes transmitted in the request.

Request coding 2

___________________________________________________________________________

2/13

B

2.3 Requests to access standard objectsThe UNI-TE protocol offers a number of services for read/write access to the followingtypes of data : internal bit, system bit, internal word, system word, floating point object, constant word, Grafcet data.

2.3-1 Read an internal bitRequest name : READ_INTERNAL_BIT.

This service is used to read the value