Schneider Electric TSXD24004 Reference manual

PDF

Dokuments

Reklāma

Contents

Uni-Telway - Reference Manual

Section

Introduction

Installation

UNI-TE Services

Operating Principles

Appendix

Sub-section

1.1

Documentation Presentation

1.2

General

1.3

Communication Principles

1.4

Characteristics

Page

2.1

General

2.2

Implementing the Hardware

2.3

Diagnostics

3.1

General

3.2

List of Requests

4.1

Addressing System

4.2

Controlling the Uni-Telway Link

4.3

Bus Performance

5.1

Connection Block and Subscriber Socket

Coding

5.2

ASCII Code Table

5.3

Request Coding

5.4

Decimal/Hexadecimal Conversion

5.5

Connecters

5.6

Frame Code Information

1 Introduction

1.1

Documentation Presentation

The Uni–Telway documentation is designed for users implementing the

Uni--Telway industrial bus.

The complete documentation set and the points it covers are described below:

This Reference Manual covers:

. Uni-Telway bus operating principles,

. Bus installation and diagnostics principles,

. Procedures for communication between the various devices,

. Bus performance,

. Standard UNI-TE requests, describing those available.

Specialized User's Manuals:

Are available for each device or family of devices that can be connected to the

Un-i-Telway bus. Devices that can be connected to Uni-Telway include TSX 17,

TSX 47-20, TSX 67/87 PLCs, ATV5 variable speed drives and XBT industrial terminals. The main points covered by these manuals include:

. Product description,

. Uni-Telway implementation for each product (connection),

. How to use Uni-Telway, its features and the client/server functions,

. System and device performance,

. A description of standard device requests and, if necessary, a list of specific device requests.

A specialized A5 format manual is supplied with each device.

The Reference Manual is supplied in an A5 format binder with dividers provided for inserting the various specialized manuals. It is supplied with the TSX SCM 21.6

Uni-Telway module.

XBT-B8

ATV.5

TSX

UNI-TELWAY

TSX

Uni-Telway Bus

Reference Manual

TSX

TSX 17 ACC5

Uni-Telway Adapter for TSX 17-20 Micro-PLCs

TSX

TSX SCM 21.6 Channel 1

Uni-Telway Bus

User's Manual

1 Introduction

1.2

General

Uni-Telway

Used as a multidrop bus, Uni-Telway is the standard means of communication between Telemecanique's control devices including: PLCs, operator dialog terminals, variable speed drives, numerical controls, weighing indicators.

Uni-Telway can also simplify communication with devices from other vendors, such as supervision and control computers.

Uni-Telway can be used for two types of application:

. Control and surveillance of system devices by PLC

Devices such as ATV5 variable speed drives, LT8 protection relays, ASN specialized couplers, numerical controls.

ALTIVAR 45

ATV 45

Variable speed drive

XGS On

DEF1

DEF2

IN1

IN2

OUT1

OUT2

XGS

Inductel

NUM 760

Numerical control

NUM 760

TSX 47-30

UNI-TELWAY

. Man-Machine dialog and supervision

Devices such as XBT operator dialog terminals or Monitor 77 and the capacity to support open communications with networks and computers from other vendors.

TSX 47-30

MONITOR 77

TSX 47-30

CONTRAST DEGAUSS ON.OFF

Reset

Keyboard

OFF

UNI-TELWAY UNI-TELWAY

Uni-Telway requires:

. 1 Master

This device supervises the data link and checks its operation. It controls the allocation of bus access time to the various connected stations. This entity comprises a modular TSX Series 7 PLC equipped with a TSX SCM 21.6 serial communication module.

. 1 to 27 slaves

1 Introduction

General (Cont'd)

Uni-Telway's transparent, peer to peer type of communication permits the transmission of messages from master to slave, slave to master and slave to slave without the need for any application program in the master.

Master bus controller

(with TSX SCM 21.6 module) b c

Slave

Slave n

Slave to slave communication involves two steps that are automatically synchronized:

. message transmission to the master module: from slave 2 to the TSX SCM 21.6,

. automatic message routing to the destination address: from the TSX SCM 21.6

module to slave 3 (without requiring involvement of the processor or the application program of the PLC of the master).

The Uni-Telway bus and its UNI-TE protocol ensure the coordination of activity between the various intelligent devices:

. application to application communication, between PLCs for example (text block to text block exchange),

. application to device communication, reading data bits, words, controlling operating modes, for example.

1 Introduction

1.3

Communication Principles

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) that are common to various communication interfaces: programming port, Telway 7 network and Uni-Telway industrial bus.

The presentation, session and transport layers (6, 5 and 4) are not supported as they are seldom used in automation applications.

APPLICATION

PRESENTATION

SESSION

TRANSPORT

NETWORK

DATA LINK

PHYSICAL

UNI-TE

TE NETWORK

PROGRAMMING

PORT

TELWAY 7 UNI-TELWAY

Uni-Telway

. The UNI-TE application layer

This is a list of requests that are common to all devices (standard requests) or specific to one device (specific PLC or NC requests).

The following services are supported:

- read/write data objects (bits, words, etc.),

- control of operating modes (INIT, RUN, STOP),

- bus and device diagnostics,

- file and program up/download.

. The TSX7 network layer

This layer ensures all message routing functions to ensure that the message travels from the sender to the destination address. Each entity is identified by its own network address.

1 Introduction

Communication Principles (Cont'd)

. The Uni-Telway data link layer

This layer controls access to the bus by the various devices through a master/ slave procedure. A slave is identified by its data link address(es). The fixed master allows sequential access to the bus and allocates the line to any slave address.

. The Physical Layer

An RS-485 isolated multidrop bus with a standard speed of 9600 bps that can interconnect 2 to 28 devices on a trunkline of up to 1000 meters in length to which drops of up to 20 meters can be connected.

1 Introduction

1.4

Characteristics

Physical Layer

Topology

Interface

Bus cable

Bus length

Drop length

Number of devices

Speed

Character format

- bus,

- RS-485 isolated,

- shielded, double twisted pairs,

- cable resistance: 85 ohms/km,

- shield resistance: 12 ohms/km,

- capacitance between conductors: 100pF/m,

- characteristic differential impedance: 85 ohms,

- attenuation per km: 13 dB/km from 0 to 20kHz.

- 1000 meter trunkline, excluding drops,

- 20 meters max.,

- 28 max. connected to the bus,

- 9600 bps standard (configurable up to 19200 bps, depending on the device (refer to the appropriate documentation),

- 8 data bits,

- odd parity,

- 1 stop bit.

Data Link Layer

Data link

Access method

Checks

- asynchronous serial link,

- fixed master,

- polls up to 255 slave data link addresses (a single device can use several data link addresses).

- BCC,

- Retries.

UNI-TE Application Layer

Messages - Peer to peer message exchange, 128 characters max.

2 Installation

2.1

General

Uni-Telway Bus Connection

The Uni-Telway bus is an isolated RS-485 line that must be fitted with a line adapter or terminator at one end. There are two ways of connecting to the bus:

. by daisy-chaining the devices together (as shown by device B in the example),

. by T-Junction and passive drops, as shown by device C in the example, making the connection of intermediate devices easier.

≤

1000 m

≤

20 m

Device a

Device b

Device c

Device d

Connection Accessories

Various accessories are available for connecting devices to the Uni-Telway multidrop bus.

TSX SCA 50 Tap Junction

This component is a passive junction box containing a printed circuit board fitted with three sets of screw terminals. It connects a device via a passive drop to the main Uni-Telway trunkline. It can be mounted anywhere on the bus (e.g. in the cable duct). It ensures:

. electrical signal continuity in all three directions including shielding,

. end of line terminating when it is located at the end of the trunkline.

Telemecanique

TSX SCA 60/61 Connection Blocks

For connecting standard Uni-Telway devices (TSX SCM, XBT, NUM, VW3

A45 103 coupler, etc.) with 1 15-pin male

D-type connecter in either a daisy-chain or multidrop layout. Designed for use with devices such as VW3 A45 103 couplers for variable speed drives. Address coding is set by the micro-switches located in the connecters. In addition, the TSX SCA 61 acts as an end of line terminator.

TSX SCA 60 TSX SCA 61

The pin arrangement for these connecters is shown in the Appendix (Sub-section

5.1).

2 Installation

General (Cont'd)

TSX SCA 62 Subscriber Socket

This component is a passive Y-junction box containing a printed circuit board fitted with screw terminals and 2 15-pin female connecters. It is used to connect two devices that cannot use TSX SCA 60 and TSX SCA 61 Connection Blocks to the

Un-Telway bus. Included in this unit are:

. bus address coding for both devices,

. end of line terminating when it is located at the end of the trunkline.

Telemecanique

THIS DEVICE CODES THE ADDRESS, THEREFORE THE DISTANCE BET-

WEEN THE SOCKET AND THE DEVICE IS RESTRICTED TO 1.5 METERS.

TSX SCA 72 Adapter box

An active component for connecting equipment not fitted with an RS-485 interface, but which does use the higher layers of the protocol to connect to the

Uni-Telway bus. This box adapts RS-232-/RS-485 signals (electrical adaptation and signal isolation).

It does not provide address coding for the devices, nor will it provide end of line terminating).

Uni-Telway bus

Télémécanique

A shielded, double twisted pair cable is used. It is available in three different lengths:

. TSX CSA 100

. TSX CSA 200

. TSX CSA 300 length 100 meters, length 200 meters, length 500 meters.

Connection Cables

. Standard connection cable TSX CSE 015.

This cable is used to connect a TSX SCA 62 and any device fitted with a 15-pin connecter that meets the requirements described in the Appendix, Sub-section

5.1).

. Special connection cables

These cables are used to connect various devices to the TSX SCA 62

Subscriber Socket. These cables are described in the documentation supplied with each product.

TSX CSB 015

XBT Z908

TSX SCA 62 <--> TSX SCM 21.6 (15-pin/25-pin, len. 1.5m)

TSX SCA 62 <--> XBT 8...

(15-pin/25-pin, len. 1.5m)

TSX M77CB2 015 TSX SCA 62 <--> Monitor 77

TSX CSB 015 TSX SCA 62 <--> TSX 17 ACC5

(15-pin/15-pin, len. 1.5m)

2 Installation

General (Cont'd)

Connecting the Devices

Daisy-chain connection

When the subscriber socket (or the cable connecter) is directly connected to the

Uni-Telway bus trunkline. The TSX SCA 62 Subscriber Socket ensures device address coding.

Example of connection to a PLC

TSX 87-30

UNI-TELWAY

TSX SCM 20

TSX SCM 21.6

Ch0

Ch1

TSX CSB 015

1.5m

Telemecanique

TSX SCA 62

Subscriber Socket

Drop connection

This kind of connection requires that the drop cable be the same as the main

Un-Telway cable and that its length not exceed 20 meters.

Signal continuity, including that of the shielding is ensured by the junction box.

Address coding is set in the TSX SCA 60 Connection Block.

Example of connection to an ATV 45 variable speed drive.

ALTIVAR 45

ATV 45

Variable speed drive

UNI-TELWAY

VW3 A45 103

Coupler

Télémécanique

Telemecanique

TSX SCA 50

TSX SCA 60

It is possible to combine the various types of connections on the same Uni–Telway bus.

2 Installation

General (Cont'd)

End of Line Terminating

The Uni-Telway bus must absolutely be fitted with an end of line terminator at each end of the line. The TSX SCA 50 Tap Junction and the TSX SCA 62 Subscriber

Socket can be set by jumper to provide line terminator functions. The TSX SCA 61

Connection Block has a built-in end of line terminator. The terminator ensures end of line impedance matching.

Terminator location examples

TSX SCA 50

TSX SCA. 00

TSX SCA 62

Terminator

TSX SCA 62

Terminator

Device Device Device

TSX SCA 50

Device

TSX SCA. 00

TSX SCA 62

Device

TSX SCA 61

(Terminator)

Device

Connection Examples

TSX Series 7 PLC

TSX SCA 62

Telemecanique

Device

TSX 87

Device

TSX SCA 60

Device

TSX 7 PLC -> XBT B8 Terminal

XBT B8 TSX 87

Device

TSX CSB 015

TSX 17 PLC

UNI-TELWAY

XBT Z918

TSX SCA 62

Telemecanique

TSX CSC 015

TSX 17

2 Installation

2.2

Implementing the Hardware

Installing the Line

Within the same facility no special precautions need be taken when installing the cable. The cable must never be run on the outside of a building.

Over long distances, avoid running the cable close to high voltage lines.

The term Uni-Telway line refers to the bus cable with a trunkline of up to 1000 meters, to which drops of up to 20 meters can be connected.

Connecting the Shield

The shield should be grounded through the connecter and the ground on each device.

When remote devices are connected, to meet electrical safety requirements and ensure protection of personnel, it is necessary to check the voltage level between the various grounding points. Having a difference in the voltage level between the various points on the bus can cause personnel and equipment safety hazards.

If any such problems occur, improve the quality of the grounding.

TSX SCA 50

Mounting:

This unit can be mounted on an AM1

PA.. mounting plate.

AM1 - PA..

2 x Ø5.5

50 End of line terminator

When the TSX SCA 50s are directly connected to a device at the end of the line then end of line terminating must be selected by setting the jumper to the ON position as illustrated opposite

(The device is supplied with the jumper set to the OFF position).

OFF

Wiring

Position the seals supplied and connect to the bus as shown in the figure opposite.

Shield

OVL OVL D(A) D(B)

1 2 3 4

White Red White Blue

Insulating sleeve

(mandatory)

2 Installation

Implementing the Hardware (Cont'd)

TSX SCA 60/61

Mounting

These connection blocks are mounted on the device to be connected to the

Uni-Telway bus.

Addressing

The address of a device on the Uni-

Telway bus is coded by setting the microswitches located on the printed circuit board.

The code value is set by moving the switches to the OFF position.

The addressing system switches are assigned binary weights of 1-2-4-8-16.

Each switch set to OFF takes a binary value of 1 (0 for ON).

The address is used with a parity switch that must always be set to ensure that an odd number of switches are set to OFF.

The example opposite shows the coding for addresses 5 and 11. For additional information refer to Subsection 5.2 in the Appendix where the coding for all addresses from 0

(master) to 31 (slave) are listed.

TSX SCA 60

Parity

Binary weight

ON OFF

TSX SCA 61

ON OFF

Address

1 2 3 4 5 6

P 16 8 4 2 1

OFF

End of line terminator

End of line terminating is automatically provided by the TSX SCA 61

Connection Block.

Device 5

1 2 3 4 5 6

P 16 8 4 2 1

OFF

Device 11

1 2 3 4 5 6

P 16 8 4 2 1

OFF

Wiring

Shield

Position the seals supplied and connect to the bus as shown in the figure opposite.

Insulating sleeve

(mandatory)

OVL OVL D(A) D(B)

1 2 3 4

White Red White Blue

2 Installation

Implementing the Hardware (Cont'd)

TSX SCA 62

Mounting

This unit can be mounted on an AM1

PA.. mounting plate or an AM1 DE/DP

Omega rail with mounting plate LA9

D09976.

2 x Ø5,5

Addressing

The address of a device on the Uni-

Telway bus is coded by setting the microswitches located on the printed circuit board.The code value is set by moving the switches to the OFF position.

The addressing system switches are assigned binary weights of 1-2-4-8-16.

Each switch set to OFF takes a binary value of 1 (0 for ON).

The address is used with a parity switch that must always be set to ensure that an odd number of switches are set to

OFF.

Parity

Binary weight

The example opposite shows the coding for addresses 5 and 11. For additional information refer to Sub-section

5.2 in the Appendix where the coding for all addresses from 0 (master) to 31

(slave) are listed.

Device 5

End of line terminator channel 2

1 2 3 4 5 6

OFF

SW2

OFF channel 1

SW1

OFF

Address

1 2 3 4 5 6

P 16 8 4 2 1

Master

1 2 3 4 5 6

P 16 8 4 2 1

Device 11

1 2 3 4 5 6

When the subscriber sockets are directly connected to a device at the end of the line, terminating must be provided.

Set the jumper to the ON position as shown opposite. (As supplied, devices are set to the OFF position).

P 16 8 4 2 1

OFF

P 16 8 4 2 1

SW1

OFF

Wiring

Position the seals supplied and connect to the bus as shown in the figure opposite.

Shield

OVL OVL D(A)

2 3 4

White Red White Blue

D(B)

Insulating sleeve

(mandatory)

2 Installation

Implementing the Hardware (Cont'd)

TSX SCA 72

The TSX SCA 72 Adapter Box comprises:

. an RS-232/Uni-Telway adapter box,

. a mains power cord.

Configuration

The TSX SCA 72 Adapter Box is factory configured for a 220V supply, be sure to change this setting if necessary, before powering-up, as an incorrect configuration can terminally damage the device. To check the position of the switches and jumpers proceed as follows:

Remove the cover from the box, then:

Select the position of switch S4 (220V or 110V) as necessary.

Check that the 5 dip-switches and the

3 jumpers are set as shown opposite.

2 1

Connecting a TSX SCA 50 and TSX SCA 72

This connection uses a TSX CSA .00 available from Telemecanique.

OFF

LINE

OVL

D(A)

D(B)

J1/J2/J3

Shield

White

Red

White

Blue

White

Blue

White

Red

D(A)

D(B)

OVL

TSX SCA 50

TSX SCA 72

As end of line terminating is automatically ensured by the TSX SCA 72 Adapter

Box, the terminator jumper from TSX SCA 50 must be set to OFF, even if located at the end of the line.

Connecting a TSX SCA 72 and an RS-232 Device

The type of cable selected depends on the device to be connected. The cables listed below are available from Telemecanique:

. TSX CSF 050 (2 male 25-pin connecters),

. TSX M77 CB0 615 (1 male 25-pin connecter and 1 female 15-pin connecter, used to connect Monitor 77).

2 Installation

Implementing the Hardware (Cont'd)

2.3 Diagnostics

General

The TSX TS4 310 Uni-Telway operating cartridge simplifies implementation and maintenance of the Uni-Telway bus and the devices connected to it.

This multilingual cartridge can be installed in any

TSX T407 terminal which itself can be connected to the programming port of any TSX Series 7 PLC.

In addition to its Uni-Telway diagnostics, the cartridge can also be used to access the PL7-1, PL7-2,

PL7-3 addressable objects in all TSX Series 7

PLCs (from the TSX 17 to the TSX 87).

Telemecanique

TSX TS4 31

Uni-Telway Function

A TSX T407 terminal with a TSX TS4 310 Uni-Telway operating cartridge, connected to any PLC enables the user to:

. Identify Uni-Telway master or slave modules installed in the PLC,

. Read and change the configuration of these modules,

. Perform data link diagnostics (read and reset the transmission error counters for each module).

If the terminal is connected to a Uni-

Telway bus master PLC, it can in addition:

. Display a list of stations present on the bus,

. Logically connect each slave to the bus (data link addressing), for:

. Identification of the type of device connected at this address,

. Data link diagnostics (error counter contents) as seen by this device,

. Access to normal PLC operating functions if one of the devices connected to the data link is a TSX Series 7 PLC. The functions available are listed on the next page:

2 Installation

Implementing the Hardware (Cont'd)

Operating Function

The TSX TS4 310 cartridge provides the following services for TSX Series 7

PLCs.

Connection

It is possible to connect to a local or remote PLC via a Telway 7 network.

Adjust Mode

. displays all bits, words and function blocks,

. forces I/O bits and internal bits,

. blocks PL7-3 Grafcet steps.

Diagnostic Mode

. displays the processor module front panel indicator data,

. displays the status of the I/O racks and whether or not any faults are present.

Control Mode

. RUN, STOP, INIT,

. displays the list of active steps.

Transfer Mode

. stores (or restores) programs (via Uni-Telway with TSX 17-20 and TSX 47-20) and Adjust mode parameters (for any TSX Series 7 PLC). Storage can be made to the TSX T407 terminal or a tape recorder connected to it.

For further details on the characteristics and the operation of this cartridge, refer to the TSX T407 Adjustment Cartridge Manual.

3 UNI-TE Services

3.1

General

Presentation

The Uni-Telway application layer provides a single communication interface for all devices supplied by Telemecanique or other vendors that support the UNI-TE protocol.

The application layer provides standard services can be completed by additional services specific to PLCs, Numerical Controls, Machine Tools, Robots etc.

Most of the implementation steps for these services are implemented by a question and answer dialog called REQUEST/CONFIRM.

Dialog Sequencing

A device that supports the UNI-TE protocol can be a:

CLIENT:

SERVER:

This device initiates communications. It asks a question (reads), sends an answer (writes) or an order (Run, Stop, etc.).

This device executes the order sent by the client and sends a confirm after execution.

1 Request

CLIENT SERVER 2 Action

3 Confirm

Some devices can be both Client and Server. A PLC, for example is a server for its system tasks (program, adjust, diagnostics). It is also a Client of other PLCs

(and machine tool numerical controls, sensors, actuators) via the user program text blocks (when sending commands, reading status data).

TSX 7

Request Request

TX T

XBT 8 SYSTEM

ATV 5

SLAVE

CLIENT

Confirm

SERVER

MASTER

CLIENT

Confirm

SLAVE

SERVER

Important: Being a Client or Server is completely separate from the master/slave relationship on the bus.

3 UNI-TE Services

3.2

List of Requests

The standard requests that are listed in detail in the Appendix (Sub-section 5.4) with their coding, provide the following services:

Variable Management

These requests enable access to bits, words or other standard data objects (bit string, word string, etc.) or specific data objects in both read and write modes.

The requests most often used are:

. read bit (R),

. read word (W),

. write bit (B),

. write word (W),

. read data objects,

. write data objects.

Unsolicited Data

This is the only service that does not generate a confirm as it is already a response to an implicit question.

This service will transfer a byte string from the application program without it having been requested first.

The actual use of this data is up to the destination device, that is implicitly awaiting this data.

CLIENT SERVER

APPLICATION

Unsolicited data

APPLICATION Event

Data Link and Device Management

These requests are supported by all Uni-Telway devices. They are especially useful for diagnostics and on power-up (device and application protocol identification, system and communication path tests, etc.).

. identification,

. protocol version,

. read status,

. mirror,

. communication control.

3 UNI-TE Services

List of Requests (Cont'd)

Operating Mode Management

These requests are used to run or stop a device connected to the bus. They can also perform initialization and run a self-test sequence.

. Run,

. Stop,

. Self-test,

. Init.

Semaphore Management

These requests are used for device reservation, dereservation or hold reservation functions. Some requests (identification, read variables, etc.) can be used simultaneously by two clients. Other requests (e.g. up/download) require mutual exclusion mechanisms that are controlled by the semaphore management requests.

. reservation,

. dereservation,

. hold reservation.

File Transfer

These requests allow a client device to upload or download blocks (segments) of data, program or other information to or from a server. There are 3 steps in the implementation of this service, once the server has been reserved:

1 Establish a sequence that defines the type of service (up or download) and identify the data to be transferred,

2 Start the sequence on command from the client,

3 End the up/download sequence.

. initialize upload,

. upload a segment,

. end upload,

. initialize download,

. download a segment,

. end download.

Request File

These requests enable a list of requests to be stored and executed. Once execution is complete, the client can read the data received in a confirm file. This gives a coherent picture of the data that cannot normally be accessed with a single request. This service requires that the server be reserved first.

. write the request file,

. read the request file,

. execute the request file,

. clear the request file.

Note: All devices do not necessarily support all requests. Refer to the appropriate product documentation to know which standard requests are supported, what their specific parameters are and how they affect the device.

4 Operating Principles

4.1

Addressing System

General

In the Telemecanique communication architecture, all message exchanges are made in peer to peer mode between two logical entities (client and server). The logical entities must be identified by a unique address that is only used once in the entire architecture. The sender and the destination addresses are sent with each message.

Sender

Address

Destination

Address

MESSAGE

In the Telemecanique addressing system that is based on TSX Series 7 PLCs, the sender and destination addresses are encoded in 5 bytes:

. network number,

. station number,

. gate number,

. module number,

. channel number.

The network and station number bytes are used to identify the devices connected to the Telway 7 network.

Network Number

The network number provided for multiple network extensions. If a single

Telway 7 network is used, the network number is set to 0.

Station Number

This corresponds to the station number of the device connected to the Telway 7 network (H'00' to H'0F').

FOR STANDALONE STATIONS THAT ARE NOT CONNECTED TO A TELWAY 7

NETWORK, THE BYTES CORRESPONDING TO THE NETWORK AND

STATION NUMBERS MUST TAKE VALUES OF H'00' AND H'FE'

RESPECTIVELY.

Gate Number

The gate number identifies the following logical devices:

System :

Terminal :

For communication with preprogrammed functions allowing access to PL7 data objects in TSX Series 7 PLCs.

Gate number = H'00'.

For communication with PLC programming terminals.

4 Operating Principles

Addressing System (Cont'd)

Text block : To communicate with application programming terminals. The corresponding gate number is H'10' + text block number (in Hex).

Examples: TXT3 corresponds to gate H'13',

TXT12 corresponds to gate H'1C'.

Modules : To communicate with all of the intelligent modules in a PLC and especially with TSX SCM 21.6 Uni-Telway modules.

Gate number is H'05'.

Module Number

Once the module gate number (H'05') has been selected, the module number (in

Hex.) gives the location of the module in the rack.

Examples: H'03' corresponds to rack 0, slot 3,

H'27' corresponds to rack 2, slot 7.

The module number can also take the value H'FE' by default (e.g. Uni-Telway slave to Uni-Telway slave).

FOR PROGRAMMING PORT, TEXT BLOCK AND SYSTEM GATE, THE

MODULE NUMBER IS NON-SIGNIFICANT AND MUST BE SET TO H'00'.

Channel Number

The channel number identifies the various module logical devices. This is used in TSX SCM 21.6 modules in particular. The channel number corresponds to the link address of Uni-Telway slaves, incremented by H'64':

THE CHANNEL NUMBER IS NON-SIGNIFICANT FOR SYSTEM GATES,

PROGRAMMING PORTS AND TEXT BLOCKS. ITS VALUE MUST BE H'00'.

Examples: link address 1 --> channel nbr. = H'65', link address 7 --> channel nbr. = H'6B'.

Addressing Examples

In the case of a standalone PLC:

Address of slave CNC nbr. 2 on the Uni-Telway bus. The TSX SCM 21.6 master module is located in Rack 0, slot 3.

Network nbr.

= H'00'

Station nbr.

= H'FE'

Gate nbr.

Module nbr.

H'05'

H'03'

Channel nbr.

= H'66'

ATV 45

Variable speed drive

MASTER

UNI-TELWAY

ALTIVAR 45

NUM 760

4 Operating Principles

Addressing System (Cont'd)

Addressing Examples

For a Telway 7 Network:

Network

Station 4

TELWAY 7 (network 0)

Station 7 Station 12

Gate System

Terminal

Intelligent

Module

TXT 0 TXT 4 TXT i

10 + i

Module

Channel

Dev.

UNI-TELWAY

Dev.

Device B on Uni-Telway

(data link address 2)

Network nbr.

= H'00'

Station nbr.

= H'07'

Gate nbr.

Module nbr.

H'05'

H'04'

Channel nbr.

= H'66'

TXT4 in PLC nbr. 7 on

Telway 7

Network nbr.

= H'00'

Station nbr.

= H'07'

Gate nbr.

Module nbr.

H'14'

H'00'

Channel nbr.

= H'00'

Master

0-4

(Rack, Slot)

2-7

PLC system gate 12 on

Telway 7

Network nbr.

= H'00'

Station nbr.

Gate nbr.

= H'0C'

= H'00'

Module nbr.

= H'00'

Channel nbr.

= H'00'

4 Operating Principles

Addressing System (Cont'd)

Application to Uni-Telway

A Uni-Telway slave can access the complete architecture controlled by the master:

. another slave on the Uni-Telway bus,

. a logic gate (system, text block) on the master,

. a PLC connected to the master via Telway 7.

Addressing Examples

1) Slave to Slave on Uni-Telway

MONITOR 77

Address:

Network nbr.

Station nbr.

Gate nbr.

Module nbr.

Channel nbr.

sender

H'00'

H'FE'

H'05'

H'FE'

H'65' destination

H'00'

H'FE'

H'05'

H'FE'

H'66'

The network, station, gate and module numbers take the default values. The channel numbers correspond to the sender and destination data link addresses.

2) Slave to PLC via Telway

TSX 47

Master

CONTRAST DEGAUSS ON.OFF

Reset

Keyboard

OFF

UNI-TELWAY

NUM 760

Numerical control

MONITOR 77

NUM 760

Address:

Network nbr.

Station nbr.

Gate nbr.

Module nbr.

Channel nbr.

sender

H'00'

H'02'

H'05'

H'02'

H'65' destination

H'00'

H'03'

H'00'

CONTRAST DEGAUSS ON.OFF

Reset

Keyboard

OFF

UNI-TELWAY

TELWAY 7

The channel numbers correspond to the sender and destination data link addresses.

Note: A Uni-Telway slave identified by its link address represents a single logical entity. This explains that when a slave has a number of logical entities, it requires multiple link addresses : one for each addressable logical device. For example a PLC requires three link addresses (system gate, client text block, server text block).

No other slave PLC logical entities can be addressed.

4 Operating Principles

4.2

Controlling the Uni-Telway Link

Accessing the Bus

The master polls each slave address. The number of link addresses to poll is defined in the configuration (n).

The master polls each link address in rising order.

The polling message comprises 3 characters:

2 header characters (DLE - ENQ) followed by a character giving the slave link address.

The response from the slave can be either:

. information that there is no message to send (EOT),

. a message (request or confirm) that is sent to another address.

When there is no response to a message before the time-out (TO), then the entity is declared absent. It will then be temporarily deleted from the polling list. The time-out value TO is configurable in the master.

The polling cycle is illustrated below:

MASTER

Polling 1

EOT

Link

Address 1

Polling link address i

EOT

Link

Address i

Polling link address n

EOT

Polling 1

EOT

Link

Address n

Etc...

4 Operating Principles

Controlling the Uni-Telway Link (Cont'd)

Sending a Message

1) Master to Slave

The bus master can send a message at any time during the "polling" cycle.

This message can be a request, a confirm or unsolicited data.

A message comprises:

. 2 header characters (DLE-STX),

. 1 character for the message destination link address,

. 1 character for the message length,

. the message itself, comprising:

. the remote address (6 bytes),

. the request code followed by data (1 to 128 characters),

. a check character (BCC).

The answer from the slave can be either:

. an acknowledgment that the message was received (ACK),

. an acknowledgment that the message was received but cannot be processed for lack of system resources (NACK).

No response after a set period of time (time-out) means that the message was incorrect or that the station was absent.

Example: Sending a message from the master to slave 1.

MASTER

Polling 1

EOT

Link

Address 1

Polling link address i

EOT

Link

Address i

Message 1

ACK

Polling n

EOT

Polling n

EOT

Etc...

Link

Address n

4 Operating Principles

Controlling the Uni-Telway Link (Cont'd)

Addressing

In the case of communication from the master to a slave device, the various addresses are:

Sender Address

This address is coded in 5 bytes (refer to Sub-section 4.1) and is called a remote address:

. Network number,

. Station number,

. Gate number,

. Module number,

. Channel number.

N S G

Remote address

M CHANNEL

Destination Address

This address is coded in a single byte and is the link address of the destination of the exchange.

The four Network/Station/Gate/Module bytes identify the Uni-Telway master module (TSX SCM 21.6). They are not sent on the line. The destination slave is identified by its link address only.

N S G

Implicit

Remote address

M CHANNEL

Link address + H'64'

2) Slave to Master

The slave can only send a message when it is polled by the master. This message can be a request, a confirm or unsolicited data.

A message comprises:

. 2 header characters (DLE-STX),

. 1 character for the message sender link address,

. 1 character for the message length,

. the message itself, comprising:

- the remote address (1 address type byte, 5 address bytes),

- the request code followed by data (1 to 128 characters),

- a check character (BCC).

An answer from the master that can be either:

. an acknowledgment that the message was received (ACK),

. an acknowledgment that the message was received but cannot be processed for lack of system resources (NACK).

No response after a set period of time (time-out) means that the message was incorrect.

4 Operating Principles

Controlling the Uni-Telway Link (Cont'd)

Example: Sending a message from slave i to the master.

MASTER

Link

Address 1

Link

Address i

Link

Address n

Polling 1

EOT

Polling i

Message 1

ACK

Polling n

EOT

Etc...

Addressing

Polling 1

EOT

In the case of communication from the master to a slave device, the various addresses are:

Sender Address

This address is coded in one byte and is the link address of the origin of the exchange.

The four Network/Station/Gate/Module bytes identify the Uni-Telway master module (TSX SCM 21.6). They are not sent on the line. These bytes are added by the master module for possible transmission to a logical entity that is not connected to the Uni-Telway bus (a station on a Telway 7 network for example).

N S G M CHANNEL

Implicit

Link address + H'64'

Destination Address

This address is encoded in 5 bytes (refer to Sub-section 4.1) and is called the remote address:

. Network number,

. Station number,

. Gate number,

. Module number,

. Channel number.

N S G

Remote address

M CHANNEL

4 Operating Principles

Controlling the Uni-Telway Link (Cont'd)

3) Slave to Slave

Communication between slaves is performed in two stages that are linked together automatically by the bus master (TSX SCM 21.6 module).

a) slave sending to master, b) master sending to destination slave.

These steps have already been described.

Example: sending a message from i to n.

MASTER

Link

Address 1

Link

Address i

Link

Address i + 1

Link

Address n

Polling 1

EOT

Polling i

Message for device n

ACK

Message from device i

ACK

Polling i + 1

EOT

Etc...

Connecting and Disconnecting a Device

Reminder: The master polls the link addresses from 1 to n, where n is number of link addresses declared when the master is configured.

Disconnecting a Slave

When a link address does not respond to polling from the master (caused by power break, physical disconnection, etc.), it is declared absent. Periodically, every 10 cycles, the master polls an link address again, enabling it to reconnect.

If the disconnected device is the master, then the bus can no longer operate.

Connecting a Slave

If the link address was planned in the configuration of the master, connection is automatic using the procedure described above.

If the new address was not planned, a new master configuration is required.

4 Operating Principles

Controlling the Uni-Telway Link (Cont'd)

Multiflow Operation

Uni-Telway allows multiflow operation. This means that a device can start an exchange on the bus even when other devices on the bus are still awaiting answers from previous exchanges.

Example:

Sending a message (request) from the bus master to:

. slave i,

. slave j.

Data is returned after the responses (confirms) have been prepared.

Polling i Polling j

Rqi Rqj Rpi Rpj

Link

Master

Prepare request i

Prepare request j

Process

Rpi

Process

Rpj

Slave i

Slave j

Generate confirm await polling i

Generate confirm await polling j

4 Operating Principles

4.3

Bus Performance

The application to application response time on the Uni-Telway bus is a function of:

. the Bus Cycle Time (BCT),

. the software response time of the client and server devices. This cycle time is specific to each type of device and cannot be quantified here,

. the asynchronism in client, bus and server cycle times.

The bus cycle time is the time interval between two successive polling cycles.

The cycle time depends on:

. the number of devices (link addresses) polled,

. the binary data rate,

. the device turnaround time (the time that elapses between polling and its acknowledgement),

. the number type and the length of the messages involved (master to slave, slave to master or slave to slave dialog).

The diagram below illustrates the Bus Cycle Time (BCT) without messages, for a binary data flow of 9600 and 19200 bits per second.

BCT (no message)

(mS)

400

300

A: 9600 bps

B: 19200 bps

200

100

1 4 8

Turnaround time = 5 ms.

12 16 20 24 27

Slave

Addresses

When there are messages, the bus cycle time is determined by adding the following values (expressed in milliseconds) to the times shown in the graph:

M S

S M

S S

9600 bps

24 + 1.2 N

19 + 1.2N

44 + 2.3N

19200 bps

17 + 0.6N

12 + 0.6N

29 + 1.15N

(N = Number of usable characters sent on the line).

5 Appendix

5.1

Connection Block and Subscriber Socket Coding

Master

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 4

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 8

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 12

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 16

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 20

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 24

1 2 3 4 5 6

P 16 8 4 2 1

Device 28

1 2 3 4 5 6

OFF

P 16 8 4 2 1

OFF

Device 1

1 2 3 4 5 6

P 16 8 4 2 1

Device 5

1 2 3 4 5 6

P 16 8 4 2 1

Device 9

1 2 3 4 5 6

P 16 8 4 2 1

Device 13

1 2 3 4 5 6

P 16 8 4 2 1

Device 17

1 2 3 4 5 6

P 16 8 4 2 1

Device 21

1 2 3 4 5 6

P 16 8 4 2 1

Device 25

1 2 3 4 5 6

P 16 8 4 2 1

Device 29

1 2 3 4 5 6

P 16 8 4 2 1

OFF

Device 2

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 6

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 10

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 14

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 18

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 22

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 26

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 30

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 3

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 7

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 11

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 15

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 19

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 23

1 2 3 4 5 6

OFF

P 16 8 4 2 1

Device 27

1 2 3 4 5 6

P 16 8 4 2 1

Device 31

1 2 3 4 5 6

OFF

P 16 8 4 2 1

OFF

5 Appendix

5.2

ASCII Code Table b7 → b6 → b5 → b4 →

0 b3 b2

1 b1 b0

Line

Column →

0 1 2

NUL DLE SP

SOH

STX

DC1

DC2 "

ETX DC3 #

EOT DC4 $

ENQ NAK %

ACK SYN &

)

(

' BEL ETB

BS CAN

HT EM

LF SUB

VT ESC

FF FS

CR GS

SO RS

SI US

3 4 5 6 7

]

[

;

1 k j i h n o l m

DEL

}

: z

{ x y f g d e b c

\ a v w t u s r p q

5 Appendix

5.3

Request Coding

Family

Operating Mode

Management

Reset counters

RUN

STOP

Self-Test

INIT

Service

Variable

Management

Read a bit

Read a word

Read objects

Read structured objects

Write a bit

Write a word

Write objects

Write structured objects

Unsolicited Data Unsolicited data

Data Link and

Device Management

Device identification

Protocol version

Status

Mirror

Read error counters

Read slave status

Request Confirm

Hex.

Dec.

Hex.

Dec.

Description

Reads a bit (B).

Reads a word (W).

36 54

102 Reads objects (bits, words, bit or word strings ...).

100 Reads homogeneous or heterogeneous objects.

FE 254 Writes a bit (B).

FE 254 Writes a word (W).

252

FE 254 Writes objects (bits, words, bit or word strings ...).

FE 254 Writes homogeneous or heterogeneous objects.

_ _ Sends data without first receiving a request.

3F 63

Returns the type of device, its version and ref. nbr.

Returns version and communication protocol parameters.

Gives detailed information on the status of a device.

250

162

FB 251 Tests the communication system and path.

D2 210 Gives a record of device data link faults.

A3 163 D3 211 Gives the number of slaves controlled by the master and their status (connected or not).

164

FE 254 Resets a device's error counters.

FE 254 Sets a device to RUN.

254

Sets a device to STOP.

Device self-test.

Device initialization.

5 Appendix

Request Coding (Cont'd)

Family

Semaphore

Management

File Transfer

Request Files

Service

Reservation

Dereservation

Hold reservation

Initiate upload sequence

Segment upload

Terminate upload sequence

Initiate download sequence

Segment download

Terminate download sequence.

Write a request file

Request Confirm

Hex.

Dec.

Hex.

Dec.

1D 29

1E 30

Description

FE 254 Authorizes device reservation (with time-out).

FE 254 Authorizes release of a reserved device.

254

106

Holds the reservation of a device.

Sets-up an upload sequence.

6B 107 Transfers a segment.

6C 108 Ends an upload sequence.

6D 109 Sets-up a download sequence.

6E 110 Transfers a segment.

6F 111 Ends a download sequence.

20 32

Read a confirm file

Execute a request file.

Clear a request file

FE 254 Writes a file comprising a list of requests.

51 81 Reads the content of the confirm file after executing a request file.

FE 254 Starts the execution of a request file.

FE 254 Clears a request file.

5 Appendix

Request Coding (Cont'd)

Syntax

Requests are defined as byte and word sets.

A byte is an 8-bit string. The least significant bit is always sent first.

A word comprises two bytes. The least significant byte is always sent first.

Standard request format

A request comprises:

. a request code (coded in hex. over 1 byte),

. a category code (sender category that defines access rights coded in hex. over

1 byte),

. the parameters and/or data (126 bytes max.).

Request

Code

Category

Code

Parameters/Data

Standard confirm format

A confirm comprises:

. a confirm code (coded in hex. over 1 byte),

. the parameters and/or data (127 bytes max.).

If the confirm is positive, the confirm code depends on the request. If the confirm is negative, the confirm code is H'FD'.

Confirm

Code

Parameters/Data

Note: Some devices will not accept messages of more than 32-bytes. In addition the path used to send the data can also be limited to 32-bytes when, for example, a Telway 7 network is used.

5 Appendix

Request Coding (Cont'd)

Read a Bit

This request is used to read the state of a bit (0 or 1) and whether or not it is forced.

Request format

Request

Code

Hex.

Category

Code

Bit Number

00/00

Confirm format

Positive confirm

Confirm

Code

Hex.

Value Forcing

30/48

Value

Forcing

: Comprises an 8-bit string where the address of the first bit is the highest multiple of 8 found in the number of the bit to be read.

: Comprises an 8-bit string that gives the forcing indicator of the 8 "value" bits:

. 1 if the bit is forced, where the forcing value is in the

"value" information,

. 0 if the bit is not forced.

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. Bit number out of range.

5 Appendix

Request Coding (Cont'd)

Read a Word

This request will read a word (W).

Request format

Request

Code

Hex.

Category

Code

Word Number

04/04

Confirm format

Positive confirm

Confirm

Code

Hex.

Value

34/52

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. Bit number out of range.

5 Appendix

Request Coding (Cont'd)

Read Objects

This request reads simple objects (words or word strings).

Request format

Request

Code

Hex.

Category

Code

Segment

Specific

Byte

Object

Address

Number of Objects to Read

36/54 (*)

(*) Device dependent

Segment

Object address

: specifies the addressing mode of the objects to be read and their location (in Hexadecimal notation):

0 : physical byte addressing,

1 : physical word addressing,

2 : physical bit addressing,

64 : internal bit location,

68 : internal word location,

99 : time location:

. object 0: universal time,

. object 1: local time.

: Physical or logical address in the segment.

Confirm format

Positive confirm

Confirm

Code

Hex.

Specific

Byte

Data

66/102 (*)

(*) Device dependent

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. Unknown segment or object,

. Address out of range,

. Too many objects for the reception buffer.

5 Appendix

Request Coding (Cont'd)

Read Structured Objects

This request reads the state of homogeneous and heterogeneous objects.

Request format

Request

Code

Hex.

Category

Code

Segment

Object

Address

Element

Address

Quantity

34/52

Segment

Object address

Element Address

Quantity

: specifies the logical field number of objects with the same structure.

: object address in the segment.

: element address in the object.

: number of consecutive elements to read.

Confirm format

Positive confirm

Confirm

Code

Hex.

64/100

Data

Succession of Bytes

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. Unknown segment or object,

. Address out of range.

5 Appendix

Request Coding (Cont'd)

Write a Bit

This request sets a bit to 0 or 1.

Request format

Request

Code

Hex.

Category

Code

Bit Number

Bit

State

10/16

Bit State : 0 → state 0,

1 → state 1.

Confirm format

Positive confirm

Confirm

Code

Hex.

FE/254

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. Bit number out of range.

5 Appendix

Request Coding (Cont'd)

Write a Word

This request writes the contents of a word.

Request format

Request

Code

Hex.

Category

Code

Word Number Word Value

14/20

Confirm format

Positive confirm

Confirm

Code

Hex.

FE/254

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. Word number out of range.

5 Appendix

Request Coding (Cont'd)

Write Objects

This request writes objects (words or word strings).

Request format

Request

Code

Hex.

Category

Code

Segment

Specific

Byte

Object

Address

Number of Objects to Write

37/55 (*)

Data

Succession of Bytes

(*) Device dependent

Segment

Object Address

: specifies the addressing mode of the objects to be read and their location (in Hexadecimal notation):

0 : physical byte addressing,

1 : physical word addressing,

2 : physical bit field,

64 : internal bit field,

68 : internal word field,

99 : time field:

. object 0 : universal time,

. object 1 : local time.

: Physical or logical address in the segment.

Confirm format

Positive confirm

Confirm

Code

Hex.

FE/254

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. Unknown object,

. Address of the last object out of range.

5 Appendix

Request Coding (Cont'd)

Write Structured Objects

This request writes simple homogeneous and heterogeneous objects.

Request format

Request

Code

Hex.

Category

Code

Segment

Object

Address

Element

Address

Quantity Data

35/53

Succession of Bytes

Segment

Object Address

Element Address

Quantity

Confirm format

Positive confirm

Confirm

Code

Hex.

FE/254

: specifies the logical field number of objects with the same structure.

: object address in the segment.

: element address in the object.

: number of consecutive elements to write.

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. Unknown segment or object,

. Address out of range.

5 Appendix

Request Coding (Cont'd)

Unsolicited Data

A device on the Uni-Telway bus may have to take the initiative of sending data without having first received a request and therefore having to support a client function.

This type of message does not require a confirm from the destination. Using this service reduces the data flow between clients and servers by avoiding the need for the client to systematically send requests.

As there is no answer from the destination, this service is reserved for certain types of information:

. Random data providing information, that if lost does not affect correct operation.

. Data that triggers a predictable response from the client (triggering a request/ confirm dialog between the client and the server caused by an event).

. Short, cyclically transmitted data, where recurrence is enough to ensure data coherence.

A TSX SCM 21.6 module, configured as a Uni-Telway master also provides an event triggered data service. For further information refer to the TSX SCM 21.6

Uni-Telway User's Manual.

Request format

Request

Code

Hex.

Category

Code

FE/252

File Name

Succession of Bytes

Confirm format

There is no confirm from the destination of the exchange.

5 Appendix

Request Coding (Cont'd)

Device Identification

This request allows the server to include device type, software version and reference number in its confirm.

Request format

Request

Code

Hex.

Category

Code

0F/15

Confirm format

Positive confirm

Confirm

Code

Hex.

Dev.

Type

Dev.

Sub-type

Dev.

Version

3F/63 (*) (*) (*)

Reference Number

ASCII Character String (**)

(*)

(**)

Device dependent,

1 byte for length, n ASCII bytes for the device reference number.

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights.

5 Appendix

Request Coding (Cont'd)

Protocol Version

This service identifies the version and any application protocol parameters that apply to data communication. In this request the client sends the application protocol versions that it supports, the maximum message size, the size of the request file, etc. The server then sends its own characteristics. This allows the client to send requests using a format and size that is acceptable to both parties.

Request format

Request

Code

Hex.

Category

Code

Max.

Message

Size

30/48

Length

Version

Succession of Bytes

: supported version number.

: list of supported versions.

Confirm format

Positive confirm

Confirm

Code

Hex.

Max.

Message

Size

60/96

Length Version

Succession of Bytes

Request

File Size

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights.

5 Appendix

Request Coding (Cont'd)

Status

In its confirm, the server sends a standard status message, with (if required) a device dependent status message in the data field. This provides detailed information on device status (cause of stoppage, active program, etc.).

Request format

Request

Code

Hex.

Category

Code

Required

Detail

31/49 (*)

(*) Device dependent

Confirm format

Positive confirm

Request

Code

Hex.

Current

Status

Mask

61/97

Data

(*)

(*) Device dependent

Current Status : Bit 0 : System idle,

Bit 1 : Correctable error detected,

Bit 2 : Uncorrectable error detected,

Bit 3 : Check the auxiliary power source,

Bit 4 : System reset,

Bit 5 : Critical operation in progress,

Bit 6 : Stopped,

Bit 7 : Local mode.

Status Mask : Bit string. Only current status bits that have a bit of the same weight at "1" in the "Status Mask" are significant.

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights.

5 Appendix

Mirror

Request Coding (Cont'd)

This service tests the system and the communication path. The client sends a sequence that the server then returns to the client.

Request format

Request

Code

Hex.

Category

Code

FA/250

Data

Succession of Bytes

Confirm format

Positive confirm

Confirm

Code

Hex.

FB/251

Data

Succession of Bytes Sent by the Request

Negative confirm

There is never a negative confirm.

5 Appendix

Request Coding (Cont'd)

Read Error Counters

Each device keeps a log of data link faults (character, frame and protocol errors) by counting 4 types of error in counters (16-bit words):

. number of messages sent not acknowledged,

. number of messages sent and refused,

. number of messages received not acknowledged,

. number of messages received and refused.

Request format

Request

Code

Hex.

Category

Code

A2/162

Confirm format

Positive confirm

Confirm

Code

Hex.

Number of

Messages Sent not Acknowledged

Number of

Messages Sent and Refused

Nbr. of Messages

Received not

Acknowledged

Nbr. of Messages

Received and

Refused

D2/210

Caution:

Negative confirm

Confirm

Code

Hex.

FD/253

There is no counter overflow. They remain stuck at 7FFF (32767) until they are reset by a counter reset request (A4).

Reasons for rejection : . Unknown request.

5 Appendix

Request Coding (Cont'd)

Read Uni-Telway Slave Status

The Uni-Telway bus master controls a number of slaves (link addresses) that can be parametered. It also controls their status (connected or not). The number of slaves connected and their status can be determined using this request.

Request format

Request

Code

Hex.

Category

Code

A3/163

Confirm format

Positive confirm

Confirm

Code

Hex.

Number of

Slaves

D3/211

Slave Status

Succession of Bits

Number of Slaves

Slave Status

: Number of slaves that can be controlled, e.g.: 152 for TSX SCM 21.6 Master 152 bits = 19 bytes.

: Succession of bytes with a weight corresponding to the slave address and value to slave status:

Bit 0 : Status Slave 1,

Bit 1 : Status Slave 2,

Bit n : Status Slave n + 1.

Values:

0 : Slave Disconnected,

1 : Slave Connected.

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Controller not configured,

. Unknown request.

5 Appendix

Request Coding (Cont'd)

Reset Uni-Telway Diagnostics Counters

This request resets the error counters of a device.

Request format

Request

Code

Hex.

Category

Code

A4/164 0 7

Confirm format

Positive confirm

Confirm

Code

Hex.

FE/254

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights.

5 Appendix

RUN

Request Coding (Cont'd)

This request sets a device to Run.

Request format

Request

Code

Hex.

Category

Code

24/36

Caution: Depending on the device used, prior reservation may be required.

Confirm format

Positive confirm

Confirm

Code

Hex.

FE/254

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation.

5 Appendix

STOP

Request Coding (Cont'd)

This request sets a device to Stop.

Request format

Request

Code

Hex.

Category

Code

25/37

Caution: Depending on the device used, prior reservation may be required.

Confirm format

Positive confirm

Confirm

Code

Hex.

FE/254

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation.

5 Appendix

Request Coding (Cont'd)

Self-Test

This request starts a device's self-test procedure.

Request format

Request

Code

Hex.

Category

Code

Test

Type

32/50 (*)

Specific

Code

(* *)

(*)

(**)

Device dependent coding,

Field and coding are optional, depending on the type of test.

Confirm format

Positive confirm

Confirm

Code

Hex.

Result

Specific

Code

62/98 (*) (* *)

(*)

(**)

Test OK : 0

Test NOK : specific code

Specific field and coding are optional.

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation.

5 Appendix

INIT

Request Coding (Cont'd)

This request initializes a device.

Request format

Request

Code

Hex.

Category

Code

33/51

Caution: Depending on the device used, prior reservation may be required.

Confirm format

Positive confirm

Confirm

Code

Hex.

Result

63/99 (*)

(*) INIT OK : 0,

INIT NOK : specific code.

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation.

5 Appendix

Request Coding (Cont'd)

Reservation

This service allows a client to reserve the server device with which it wishes to dialog during critical requests (up/download, manual operation, etc.).

Caution: The station that requests the reservation must send a hold reservation request at least once every 60 seconds, otherwise the server will be automatically dereserved.

Request format

Request

Code

Hex.

Category

Code

1D/29

Confirm format

Positive confirm

Confirm

Code

Hex.

FE/254

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. Reservation by another address.

5 Appendix

Request Coding (Cont'd)

Dereservation

As soon as the client sends this request to the server, it ceases to be reserved.

Request format

Request

Code

Hex.

Category

Code

1E/30

Confirm format

Positive confirm

Confirm

Code

Hex.

FE/254

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. Reservation by another address.

5 Appendix

Request Coding (Cont'd)

Hold Reservation

This request must be sent at least once every 60 seconds by the entity that requested the reservation, In order to hold the reservation made. This request requires that the entity have been reserved first.

Request format

Request

Code

Hex.

Category

Code

Reserved

2D/45 FF FF

Confirm format

Positive confirm

Confirm

Code

Hex.

FE/254

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation,

. Reservation by another address.

Note : A reservation will also be held automatically on receipt of any request from the sender that initially reserved it.

The hold reservation request is therefore optional.

5 Appendix

Request Coding (Cont'd)

Initiate Upload Sequence

This request authorizes identification of the data to upload. It requires prior reservation.

Request format

Request

Code

Hex.

Category

Code

File Name

3A/58 Succession of 8 Bytes

Confirm format

Positive confirm

Confirm

Code

Hex.

Status

6A/106 (*)

(*) Coding is device dependent.

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation.

5 Appendix

Request Coding (Cont'd)

Segment Upload

This request uploads data from client to server. It requires prior reservation.

Request format

Request

Code

Hex.

Category

Code

Segment Number Segment Length Data

3B/59 Succession of Bytes

Confirm format

Positive confirm

Confirm

Code

Hex.

Status

Received

Segment Nbr.

6B/107 (*)

(*) Coding is device dependent.

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation.

5 Appendix

Request Coding (Cont'd)

Terminate Upload Sequence

This request terminates the upload sequence. It requires prior reservation.

Request format

Request

Code

Hex.

Category

Code

3C/60

Confirm format

Positive confirm

Confirm

Code

Hex.

Status

6C/108 (*)

(*) Coding is device dependent.

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation.

5 Appendix

Request Coding (Cont'd)

Initiate Download Sequence

This request authorizes identification of the data to download. It requires prior reservation.

Request format

Request

Code

Hex.

Category

Code

File Name

3D/61 Succession of 8 Bytes

Confirm format

Positive confirm

Confirm

Code

Hex.

Status

6D/109 (*)

(*) Coding is device dependent.

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation.

5 Appendix

Request Coding (Cont'd)

Segment Download

This request downloads data from server to client. It requires prior reservation.

Request format

Request

Code

Hex.

Category

Code

Segment

Number

3E/62

Confirm format

Positive confirm

Confirm

Code

Hex.

Status Segment Number Segment Length

6E/110 (*)

(*) Coding is device dependent.

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation.

Data

Succession of Bytes

5 Appendix

Request Coding (Cont'd)

Terminate Download Sequence

This request terminates the download sequence. It requires prior reservation.

Request format

Request

Code

Hex.

Category

Code

3F/63

Confirm format

Positive confirm

Confirm

Code

Hex.

Status

6F/111 (*)

(*) Coding is device dependent.

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation.

5 Appendix

Request Coding (Cont'd)

Write a Request File

Once the server is reserved, this request enables writing a list of requests for execution to a buffer of up to 256 bytes max. (called TLIST). These requests are written in their usual format. The device making the request must also tell the server which buffer field is to be used for storing confirms. (The format of the TLIST buffer will be described later).

Caution: The device making the request must ensure that the list of requests and their associated answers do not overflow the space assigned to TLIST. This buffer can store up to 256 bytes max. in servers that can support this size, however a different size can be specified in the answer to the "Protocol Version" request.

Request format

Request

Code

Hex.

Category

Code

20/32

Index in the File

Data

Length

Index in the File

Data Length

Data

Succession of Bytes

: This is the location in the (TLIST) buffer after which the requests to be executed are stored (refer to the buffer format),

: From one byte to the maximum (some devices can only accept lengths of less than 32 bytes),

: Shown using the following format.

Header Reserved

Reception

Buffer Index

Reserved Reserved

(*) 00 00 00

List of Requests

(Request Code ...)

End of

List

Header : 00: Request File.

Reception Buffer Index : Location in the (TLIST) buffer where the confirms are stored once the requests are executed.

Important: Index value must be an even number.

5 Appendix

Request Coding (Cont'd)

Write a Request File (Cont'd)

Confirm format

Positive confirm

Confirm

Code

Hex.

FE/254

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation,

. Request file overflow.

5 Appendix

Request Coding (Cont'd)

Read a Confirm File

Once the server is reserved, this request enables reading the confirm file from the

TLIST buffer.

Request format

Request

Code

Hex.

Category

Code

Confirm File

Index

21/33

Data

Length

Index in the File

Data Length

: This is the location in the (TLIST) buffer after which the requests are read,

: From one byte to the maximum (some devices can only accept lengths of less than 32 bytes).

Confirm format

Positive confirm

Confirm

Code

Hex.

Start

Confirm

Field

3A/58

Data

Start Confirm Field

Data

: 00: Confirm field full,

FF: Confirm field empty or being filled.

: Confirms sent to acknowledge requests are in standard format (code, confirm, data...).

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation,

. TLIST overflow.

5 Appendix

Request Coding (Cont'd)

TLIST Buffer Structure

The structure of the TLIST buffer comprizing the request file to execute and its related confirms is detailed below.

Bytes 0

HEADER

RESERVED

RECEPTION

BUFFER INDEX

RESERVED

LIST OF REQUESTS m END OF LIST

N n + 1

255

START CONFIRM FIELD with status indicator

LIST OF

CONFIRMS

5 Appendix

Request Coding (Cont'd)

Execute a Request File

Once the server has been reserved, this request can be used to execute a previously written request file.

Request format

Request

Code

Hex.

Category

Code

22/34

Confirm format

Positive confirm

Confirm

Code

Hex.

FE/254

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation,

. Incorrect request file.

5 Appendix

Request Coding (Cont'd)

Clear a Request File

After server reservation, this request can be used to clear a previously written request file.

Request format

Request

Code

Hex.

Category

Code

23/35

Confirm format

Positive confirm

Confirm

Code

Hex.

FE/254

Negative confirm

Confirm

Code

Hex.

FD/253

Reasons for rejection : . Unknown request,

. Inadequate access rights,

. No reservation.

5 Appendix

5.4

Decimal/Hexadecimal Conversion

This table gives direct conversions for decimal numbers from 0 to 255 and hexadecimal numbers from H'00' to H'FF'.

0 1 2 3 4 5 6 7 8 9 A B C D E F

000 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015

016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031

032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047

048 049 050 051 052 053 054 055 056 057 058 059 060 061 062 063

064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079

080 081 082 083 084 085 086 087 088 089 090 091 092 093 094 095

096 097 098 099 100 101 102 103 104 105 106 107 108 109 110 111

112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127

128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143

144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159

160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175

176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191

192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207

208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223

224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239

240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255

5 Appendix

5.5

Connecters

Pin Arrangement

The Uni-Telway interface uses a 15-pin Sub-D connecter with a metal case. A female connecter is fitted on the connected component end and a male connecter is fitted on the transmission line end.

The pin arrangement for this connecter is illustrated below:

15-pin Female Sub-D Connecter

Outside view

LINE voltage level

(insulation)

DEVICE voltage level

OVL

D(B)

Illegal

/UTW

OVL

D(A)

Illegal

Address common

Parity

Illegal

Note: The connecter body is connected to the local protective ground (device level).

15-pin Male Sub-D Connecter

Outside view

LINE voltage level

(insulation)

DEVICE voltage level

OVL

D(A)

Illegal

Address common

Parity

Illegal

OVL

D(B)

Illegal

/UTW

Note: The connecter body is connected to the cable shield.

Signals Exchanged

Four types of signals are exchanged via the Uni-Telway interface:

. Addressing signals N0 to N4, the parity and common line. These signals are used for coding the address of the connected device,

. The control signal (/UTW) that is connected as an input to the device and detects if the connected device is using the Uni-Telway protocol or not,

. The data signals on line D(A), D(B) and OVL,

. The shield (SHIELD).

5 Appendix

5.6

Frame Code Information

Reminder

A message has the following structure:

Header Link Address

Message

Length

Type of

Address.

Remote Address Data Trailer

The start of message identifier is:

. <DLE> <STX> in a selecting message,

. <DLE> <ENQ> in a polling message.

The type of addressing value is:

. H’00'

. H’20'

. H’22' for simplified addressing, for standard addressing, for service messages (requests not processed by the server).

The end of message identifier is:

. <BCC> The modulo 256 sum of bytes between <DLE> and the last data byte inclusive.

Note: Any <DLE> character included in the data field is duplicated to ensure character transparency.

In this case the second <DLE> character is taken into account when calculating the BCC value.

The other parameters are described in Section 4.

Selection Message

The data link frame is:

Master:

<DLE> <STX> <LINK ADDR.> <LENGTH> <NPDU> <BCC>

<TYPE> <REMOTE ADDR.> <TPDU>

<REQUEST CODE> <CATEGORY CODE> <DATA>

. <NPDU> : Network Protocol Data Unit,

. <TPDU> : Transport Protocol Data Unit.

Slave:

. <ACK> : Message received correctly,

. <NACK> : Message not processed,

. <EOT> : No message available (for polling),

. Silence : Incorrect message.

5 Appendix

Frame Code Information (Cont'd)

Interrogation Message

The data link frame is:

Master:

<DLE> <ENQ> <LINK ADDR.>

Slave:

. <EOT> : No message available,

. Silence : Incorrect message received.

<DLE> <STX> <LINK ADDR.> <LENGTH> <NPDU> <BCC>

<TYPE> <REMOTE ADDR.> <TPDU>

Examples

<REQUEST CODE> <CATEGORY CODE> <DATA>

. <NPDU> : Network Protocol Data Unit,

. <TPDU> : Transport Protocol Data Unit.

Slave:

. <ACK> : Message received correctly,

. <NACK> : Message not processed,

. Silence : Incorrect message.

Master

Slave

Master

2 3

Slave

5 Appendix

Frame Code Information (Cont'd)

A Master

➪

Slave

Example: TXT 8 from the master PLC to device 3.

DLE STX 03 L 20 00 FE 18 00 00 TPDU

≤

128 char.

BCC

Link Address

Message Length

Type of Addressing

: Destination

: TPDU + 6

: Standard

Remote Address

- Network

- Station

- Gate

. Text block offset

. Text block number

: Sender

: 00 by default

: FE by default

: 18 = 10 + 8

- Module

- Channel

: 00 not significant

B Slave

➪

Master

Example: Device 2 to TXT 4 of the master PLC.

DLE STX 02 L 20 00 FE 14 00 00 TPDU

≤

128 char.

BCC

Link Address

Message Length

Type of Addressing

: Sender

: TPDU + 6

: Standard

Remote Address

- Network

- Station

- Gate

. Text block offset

. Text block number

: Destination

: 00 by default

: FE by default

: 14 = 10 + 4

- Module

- Channel

: 00 not significant

5 Appendix

Frame Code Information (Cont'd)

C Slave

➪

Slave

Example: Device 2 to device 3.

Communication takes place in two steps that are automatically synchronized by the system tasks of the master (TSX SCM 21.6

module).

- Device 2 -> Master

- Master -> Device 3

Step 1: Device 2 to master

DLE STX 02 L 20 00 FE 05 FE 67 TPDU

≤

128 char.

BCC

Link Address

Message Length

Type of Addressing

: Sender

: TPDU + 6

: Standard

Remote Address

- Network

- Station

- Gate

- Module

- Channel

. Uni-Telway offset

. Device link address

: Destination

: 00 by default

: FE by default

: 05 = I/O module

: FE by default

: 67 = 64 + 3

Step 2: Master to device 3

DLE STX 03 L 20 00 FE 05 FE 66 TPDU

≤

128 char.

BCC

Link Address

Message Length

Type of Addressing : Standard

: Destination

: TPDU + 6

Remote Address

- Network

- Station

- Gate

- Module

- Channel

: Sender

: 00 by default

: FE by default

: 05 = I/O module

: FE by default

: 66 = 64 + 2

. Uni-Telway offset

. Device link address

5 Appendix

Frame Code Information

Step 1

- Device 2 to master

DLE STX 02 L 20 00 FE 05 FE 67 TPDU

≤

128 char.

BCC

Step 2

- Master to device 3

67 - 64 02 + 64

DLE STX 03 L 20 00 FE 05 FE 66 TPDU

≤

128 char.

BCC

Sveiki! Esmu AI tērzēšanas robots, kas īpaši apmācīts, lai palīdzētu jums ar Schneider Electric TSXD24004 Reference manual. Esmu rūpīgi pārskatījis dokumentu un varu palīdzēt jums atrast precīzu nepieciešamo informāciju vai izskaidrot saturu skaidri un vienkāršiem vārdiem. Neatkarīgi no tā, vai meklējat norādījumus par konkrētām funkcijām, problēmu novēršanas darbībām vai vispārēju lietošanu, droši uzdodiet savus jautājumus. Jo vairāk informācijas sniegsiet par savām bažām vai vajadzībām, jo precīzāk un efektīvāk es varu jums palīdzēt!