Industrial Networks & Databases X-Way Network System

Communication requirements - integrated plant X-Way performs the idea of an integrated plant which defines the various levels of communication:  management-design level

 factory floor level

 cell level

 machine or field level

2014-05-06

Level 3 managementdesign

Information system

Level 2 factory floor

Production management Supervision

Level 1 cell

Control system

Level 0 machine or field

Components

X-Way Network System Dr inż. Janusz Hajda

2

X-Way and the OSI model UNI-TE 7

APPLICATION

Application-to-application communication COM Shared table

Modbus Shared I/O

6

PRESENTATION

EMPTY

5

SESSION

EMPTY

4

TRANSPORT

EMPTY

3

NETWORK

2

LINK

Master/Slave

ISO802.2/3 Ethernet

FIP WORLDFIP

ISO 802 3 Ethernet

1

PHYSICAL

RS485

ISO 802.3 10Mbits/s

FIP/WORLDFIP 1 Mbits/s

ISO 802 3 10/100 Mbps

UNI--Telway UNI

ETHWAY

2014-05-06

X-Way Addressing

X-Way Network System Dr inż. Janusz Hajda

FIPWAY

IP

FIPIO

Ethernet TCP

3

X-WAY addressing mechanisms  Architecture level  consists of terminal stations and bridges  A station is identified by network number and a station number  The intermediate stations have several network addresses.

Station i Network A Station j

Station k Network B

Station l

Station m Network C Station n

2014-05-06

X-Way Network System Dr inż. Janusz Hajda

4

X-WAY addressing mechanisms  Station level  Used to address an entity in the station.

 A station consists of a series of communication entities  A communication entity is identified by an address

Module 3 Chanel 0

Network 1

Module 0 Chanel 1 Station 1 Connection point 6

Module 0 Channel 0

Module 2 Channel 0 Station 2

Connection point 15

2014-05-06

X-Way Network System Dr inż. Janusz Hajda

5

X-WAY addressing PLCs connected to an X-Way network consist of one or more communication entities. The entity levels:  Station level entities: the station UNI-TE server, communication tools, the programming terminal.  Module level entities: UNI-TE client/server, network management.  Communication channel level entities: UNI-TE client/server, PLC application.

2014-05-06

X-Way Network System Dr inż. Janusz Hajda

6

Hierarchical addressing Network Station

System Gate 0

Terminal port 1, 2, 3

Communication module 5 Module Channel

3 levels 2014-05-06

5 levels

8

Application 16 … 249

Selector Connection point References

6 levels

X-Way Network System Dr inż. Janusz Hajda

7

Hierarchical addressing – three level addressing Network. Station. Gate

System: 2.4.0

Network 2 Network number of the destination station of the exchange (0 ..127). Station 4 Station number - number of the destination station of the exchange. (0 … 63). Terminal port: 2.4.1 Gate number - communication entity within the selected station: • 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: gate 16, • the text block functions of the station application: from gate 16 to gate 79, • the communication functions: gates 16 to 239, • the other gate numbers are reserved. • "all gate values„: gate 254

2014-05-06

X-Way Network System Dr inż. Janusz Hajda

8

Hierarchical addressing – five level addressing Network. Station. Gate. Module. Channel Module number Only used if the gate number is 5 • corresponds to the physical location of this module on the backplane bus (rack number and slot in the rack). Channel number Only used if the gate number is 5 • corresponds to the address of the device connected to the network or bus from the module selected.

Slot 6 of rack 0

Network 2 Station

4

Communication module Gate

5 5

Channel 0 Module

06 Channel 1 System: 2.4.5.06.8 System: 2.4.5.06.102 Address 2

Address 8

System: 2.4.5.06.103 2014-05-06

X-Way Network System Dr inż. Janusz Hajda

Application: 2.4.5.06.105

Address Ad0=3 Ad1=4 Ad2=5

9

Hierarchical addressing – six level addressing Network. Station. Gate. Selector. Connection point. Reference Network Station

Communication module Gate 8 Module in the backplane bus 1

Selector

Module integrated in the CPU 2

Connection point

Reference

2014-05-06

Server UNI-TE System 0

Client UNI-TE System 1

Server UNI-TE Channel 0 4

X-Way Network System Dr inż. Janusz Hajda

Server UNI-TE Channel 1 7

Server UNI-TE Channel 2 10 10

X-WAY frame format Foreword

END Link layer data

CRC X-Way frame Data Shared data

The X-Way frame is made up as follows: NPDU type

Addresses

3 and 5 level addressing

Six level addressing extension

Data (message system)

Network Protocol Data Unit

2014-05-06

X-Way Network System Dr inż. Janusz Hajda

11

X-WAY frame format NPDU type

Addresses

4 bits Type

3 and 5 level addressing

2 bits

Six level addressing extension

Data (message system)

1 bit 1 bit

Level of Ref Ext service usal

Network Protocol Data Unit

Type: 0 to14 Reserved, 15 NPDU data. Level of service: 0 Standard, 1 Telegram, 2 to 3 Reserved. Refusal: 0 Message accepted, 1 Message refused. Extension: 0 if one of the devices uses addressing on three or six levels addressing, 1 if one of the devices uses addressing on five levels addressing.

2014-05-06

X-Way Network System Dr inż. Janusz Hajda

12

X-WAY frame format NPDU type

Addresses

2 bytes Sender address

3 and 5 level addressing

Six level addressing extension

2 bytes Destination address

1 byte

=2x

Station number

Data (message system) 4 bits

4 bits

Network Gate number number

Station number: between 0 and 63 (the value 255 is reserved for broadcasting). Network number: between 0 and 127. when the value is greater than 15, an address extension is required. Gate number: 0 access to the system of the device, 1, 2, 3 access to the terminal port of a PLC, 5 access to a communication module (addressing structured on five levels), 8 access to a communication module (addressing structured on six levels), 11, 12, 13 access to the terminal connected at connection point 63 on FIPIO, 16 to 239 access to 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. 2014-05-06

X-Way Network System Dr inż. Janusz Hajda

13

X-WAY frame format NPDU type

Addresses

3 and 5 level addressing

2-8 bytes Parameter 1 Parameter 2

Parameter n

2-8 bytes Parameter 1 Parameter 2

2014-05-06

Parameter n

Six level addressing extension

Data (message system)

Parameter value

Identifier Length

Sending gate n° if >15 Destination gate n° if >15 Sending network n° if >15 Destination network n° if >15 Sending module n° and channel n° Destination module n° and channel n°

0 1 2 3 4 5

Parameter value

Identifier Length

Compacted physical sender address Compacted physical destination address Extended physical sender address Extended physical destination address

6 7 8 9

X-Way Network System Dr inż. Janusz Hajda

1 1 1 1 2 2

2 2 3 3

14

X-WAY frame format NPDU type

Addresses

3 and 5 level addressing

Six level addressing extension

Data (message system) Data for the UNI-TE service

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

1byte

1 to 254 bytes

Request code Category code

Transmission data 1 to 256 bytes

Application-to-application data (text block, function block, etc) 1 to 254 bytes Telegram type data

Received data is structured as follows: 1 byte Confirmation

2014-05-06

1to 254 bytes Response data

X-Way Network System Dr inż. Janusz Hajda

15

UNI-TE protocol  The UNI-TE protocol respects the client/server model  UNI-TE V1.1 and V2.0  The general structure of an exchange observes the following format. It depends on the UNI-TE protocol version. Request format: F9h

Transaction number

Request code

Category code

Data specific to the request

UNI-TE 1.1 UNI-TE 2.0

Confirmation format: F0h

Transaction Confirmation number report

Data specific to the confirmation UNI-TE 1.1 UNI-TE 2.0

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

X-Way Network System Dr inż. Janusz Hajda

16

UNI-TE request and confirmation Request: 1 byte

F9h

1 byte

1 byte

Transaction number

Request code

1 byte

1 byte

Category code

Data specific to the request

Positive confirmation with no specific data: 1 byte

F0h

1 byte

1 byte

Transaction number

FEh

Negative confirmation with no specific data: 1 byte

F0h

1 byte

1 byte

Transaction number

FDh

Positive confirmation with specific data: 1 byte

F0h 2014-05-06

1 byte

1 byte

Transaction number

Request code

1 byte

Data specific to the request

X-Way Network System Dr inż. Janusz Hajda

17

Lists UNI-TE requests

2014-05-06

X-Way Network System Dr inż. Janusz Hajda

18

Example: Reading internal words (READ_INTERNAL_WORD) Read the value of word %MW2: Request

F9h

The header byte (F9H, F0h), and the transaction number are managed by the system

Transaction number Request code

04h

Category code

07h

Data specific to the request Confirmation

02 00h pay attention to the internal word number in Intel format, which corresponds to %MW2

F0h

Transaction number Negative response code

FDh

Confirmation

F0h

application does not existor internal word number exceeding the configured internal word zone.

Transaction number Positive response code Value

2014-05-06

34h AB 00h pay attention to the value of the internal word %MW2 in Intel format, in this case ABh

X-Way Network System Dr inż. Janusz Hajda

19

Example: Writing internal words (READ_INTERNAL_WORD) Write 0Ah to the word %MW2: Request

F9h

The header byte (F9H, F0h), and the transaction number are managed by the system

Transaction number Request code

14h

Category code

07h

Internal word number Value Confirmation

02 00h pay attention to the internal word number in Intel format, which corresponds to %MW2 0A 00h pay attention to the value of the word to write in Intel format, in this case 0Ah F0h

Transaction number Negative response code

FDh

Confirmation

F0h

application does not existor internal word number exceeding the configured internal word zone.

Transaction number Positive response code

2014-05-06

FEh

X-Way Network System Dr inż. Janusz Hajda

20

Example: Writing objects (WRITE_OBJECTS) Request format: Request Transaction number Request code Category code Object segment Object type Instance of first object Number of objects to write

37h 07h Byte Byte Word Word

contains address of first object to write. number of objects to write. data to write, the format depends on the object type and the number of objects to

Data Object label

F9h

Word tabel write. Segment

Type

Instance

%Mi

64h

5

internal bit number (number of bits as a multiple of 8)

%Si

64h

6

i: internal system number (number of bits as a multiple of 8).

%MWi

68h

7

i: internal word number

%MDi

68h

8

i: internal double word number

%KWi

69h

7

i: constant word number

%KDi

69h

8

i: constant double word number

%SWi

6Ah

7

i: system word number

Real-time_clock

80h

1

03h: current date and time In BCD format,

2014-05-06

X-Way Network System Dr inż. Janusz Hajda

21

Example: Writing objects (WRITE_OBJECTS) The request writing %MW10 to 11 and %MW11 to 12 Request Transaction number Request code Category code Object segment Object type Instance of first object Number of objects to write Data

37h 07h 68h 07h 0A 00h 02 00h 0B 00h

Data

0C 00h

Confirmation

F9h

segment of objects to write (word space) object type (%MWi) instance of first object, %MW10 (10=0Ah). number of object to write, in this case 2 the value to write in %MW10 is 0B00h, that is 11 the value to write in %MW11 is 0B00h, that is 12

F0h

Transaction number Negative response code

FDh

Confirmation

F0h

application does not existor internal word number exceeding the configured internal word zone.

Transaction number Positive response code

2014-05-06

FEh

X-Way Network System Dr inż. Janusz Hajda

22

Example: Reading an object list (READ_OBJECT_LIST) Request format: Request Transaction number Request code Category code Extension Number of operations Object identification Access parameters

2014-05-06

F9h 38h 07h equals 0 Byte number of read operations to be performed Byte Byte Word / byte

X-Way Network System Dr inż. Janusz Hajda

23

Example: Reading an object list (READ_OBJECT_LIST) Example with three operations for a reading of the 3 words %MW10, %MW20 and %MW30: Request Transaction number Request code Category code Extension Number of operations Object 1 identification

Object 2 identification Object 3 identification Confirmation Transaction number Positive response Extension Confirmation Number of operations Status+values object 1 Status+values object 2 Status+values object 3 2014-05-06

F9h 38h 07h 00h 03h

extension, always 00h number of operations; a read status will appear for each reading of elements

68h object segment; the read operation is performed on internal data; 07h: type of object, in this case a %MWi; 0A00h: instance of first object; pay special attention in 68 07 0A 00 FF 01 00h Intel format, the value is 000Ah; FFh: total access; 01 00h: number of elements to read, in this case 1 to demonstrate an example of three successive read operations. This is the first one 68h: internal data; 07h: %MWi; 1400h: instance of second object; FFh: total access; 01 68 07 14 00 FF 01 00h 00h: number of elements to read 68h: internal data; 07h: %MWi; 1E00h: instance of third object; FFh: total access; 01 68 07 1E 00 FF 01 00h 00h: number of elements to read

F0h FEh 00h 00h 03h 00 02 00h 00 03 00h 00 04 00h

extension, always 00h report, "Read operation performed" number of operations performed 00h: read status, identical to report; 02 00h: value of %MW10 = 2 00h: read status, identical to report; 03 00h: value of %MW20 = 3 00h: read status, identical to report; 04 00h: value of %MW30 = 4

X-Way Network System Dr inż. Janusz Hajda

24