tlx dscom pl7 general and communication tools...

A

B

C

D

P

E

G

F

H

General and communication tools

Remote location of nano-PLCs

Character mode communication

UNI-TELWAY bus

Modbus

Modem

Modbus plus

FIPIO

FIPWAY

ETHERNET

Bridge

Index

TLX DSCOM PL7

Setting upcommunicationfunctionsunder PL7

I

J

K

___________________________________________________________________________

B/2

___________________________________________________________________________1

A

General and communication tools Contents

Section Page

1 General 1/1

1.1 Communication function 1/11.1-1 Definition 1/11.1-2 Methodology 1/21.1-3 Language interface 1/31.1-4 Language objects common to all communication modules 1/31.1-5 Language objects common to all communication channels 1/4

1.2 Addressing a communication entity 1/61.2-1 Principles 1/61.2-2 Addressing system using PL7 language 1/61.2-3 Presentation of the addressing 1/71.2-4 Addressing communication channels on the TSX 57 1/81.2-5 Definition and number of application-specific

communication channels 1/91.2-6 Addressing a TSX SCY 21600 / 21601

communication module 1/101.2-7 Examples of intra-station addressing 1/111.2-8 FIPIO addressing 1/121.2-9 Example of inter-station addressing 1/131.2-10 Example of addressing to a third party device 1/14

1.3 Communication from a programming terminal 1/151.3-1 General 1/151.3-2 Initial connection to an application 1/151.3-3 Local connection 1/161.3-4 Connection to a UNI-TELWAY slave on the terminal port 1/161.3-5 Connection to a UNI-TELWAY slave on the PCMCIA card 1/161.3-6 Remote connection example : 1 1/171.3-7 Remote connection example : 2 1/181.3-8 Remote connection (FIPIO) example : 3 1/19

___________________________________________________________________________

2

A


Section Page

2 Communication tools 2/1

2.1 Introduction 2/12.1-1 Role 2/12.1-2 General structure of a communication function 2/22.1-3 List of communication functions 2/72.1-4 Help with entering communication functions 2/82.1-5 Limitation of communication functions 2/122.1-6 Server function 2/14

2.2 Description of the various communication functions 2/152.2-1 Reading standard objects : READ_VAR 2/152.2-2 Writing standard objects : WRITE_VAR 2/232.2-3 Example of use 2/252.2-4 Sending UNI-TE requests : SEND_REQ 2/282.2-5 Exchanging text type data : DATA_EXCH 2/312.2-6 Sending a telegram : SEND_TLG 2/342.2-7 Receiving a telegram : RCV_TLG 2/372.2-8 Writing a character string : PRINT_CHAR 2/392.2-9 Reading a character string : INPUT_CHAR 2/422.2-10 Sending/receiving a character string : OUT_IN_CHAR 2/452.2-11 Stopping a current exchange : CANCEL 2/482.2-12 Shift one byte to the right in a table : ROR_ARB1 2/502.2-13 Swapping bytes in a word table : SWAP 2/512.2-14 Reading Modbus + common data : READ_GDATA 2/522.2-15 Writing Modbus + common data : WRITE_GDATA 2/532.2-16 Immediate server : SERVER 2/542.2-17 Asynchronous message handling services :

WRITE_Asyn and READ_Asyn 2/55

___________________________________________________________________________3

A


Section Page

2.3 Compatibility of communication between TSX37/57 and Series 7 2/572.3-1 Communication block compatibility 2/572.3-2 Exchange compatibility 2/57

2.4 General rules for using text blocks 2/582.4-1 Example : Exchanges with a UNI-TE server 2/59

3 Configuring the communication function 3/1

3.1 Introduction 3/1

3.2 The configuration tool 3/13.2-1 Accessing the configuration tool 3/13.2-2 Choosing the processor 3/23.2-3 Choosing TSX 37 communication modules 3/43.2-4 Choosing TSX 57 communication modules 3/5

3.3 Presentation of the screens 3/63.3-1 Description 3/63.3-2 Configuration screen 3/73.3-3 Debug screen 3/8

___________________________________________________________________________

4

A


Section Page

General 1

___________________________________________________________________________A1/1

A

1.1 Communication function

1.1-1 Definition

The various communication functions available are :

• The terminal port function.

• The extension link to the TSX07 function for TSX 37 PLCs.

• The character mode function.

• The UNI-TELWAY function.

• The Modbus/Jbus function.

• The Modem function.

• The Modbus+ function.

• The FIPIO function (manager and agent).

• The FIPWAY function.

• The ETHERNET TCP-IP function.

• The bridge function.

The language interface and the installation tools are similar for all communicationfunctions. However, each family contains special features which are characterized byparticular operations at the language interface level or specific procedures in theinstallation tools. Details of these special features can be found in the sections devotedto the respective communication functions.

Section 11 General

Terminal port

TSX 07 link

Character mode

UNI-TELWAY

Modbus/Jbus

Modem

Modbus+

FIPIO

FIPWAY

Communicationlanguage interface

Communicationinstallation tools ETHERNET TCP-IP

Bridge

Communication function

___________________________________________________________________________A1/2

A

1.1-2 Methodology

The methodology below shows the main points to follow when installing acommunication function.

1- Determine which hardware and software components are required : terminaldevices, drop cables, connection accessories, trunk cables, wiring test tools , toolsfor developing automation applications, installation operating tools (adjustment,diagnostics, maintenance).

2- Assemble and test the wiring system (cables and connection devices)

3- Connect terminal devices and configure their communication channel.

4- Test the accessibility of each channel from any point on the architecture by usingPL7 in offline and online mode on each of the TSX 57 or TSX 37 present (using theso-called "transparency" function). This applies to PL7-2 and PL7-3 if TSX 17 or TSXmodel 40 PLCs are used in the configuration.

5- Program PLC applications and their communication functions.

Operation

Yes

Communicationintegrated in the processor ?

Configure thecommunication function

Program the communicationfunction

No

Install thecommunication module

General 1

___________________________________________________________________________A1/3

A

1.1-3 Language interface

The language interface of a communication function defines all the data which can beobserved or modified by the application program, as well as all the communication tools(communication functions) for transmitting/receiving data to/from a communicationchannel.

The structure of the communication data is linked to the type of communication used,but certain language objects are common to all modules and all communicationchannels. Details of these objects can be found in the tables below.

Details of the information specific to a type of communication can be found in thesections devoted to the respective communication functions.

1.1-4 Language objects common to all communication modules

Each topological address (module rack) has an associated module fault bit which isupdated on each PLC scan. Details of the various objects associated with the modulefaults can be found below :

Object Function Meaning

%Im.MOD.ERR I Module fault Bit set to 1 when a module fault occurs (atleast one channel faulty, etc.)

%MWm.MOD.0 E Current x0 = 1 Read current statusexchanges x1 = 1 Send control parameters to the

communication modulex2 = 1 Send adjustment parameters to the

communication module

%MWm.MOD.1 E Report x1 = 0 Control parameters received,accepted by the module

x2 = 0 Adjustment parameters received,accepted by the module

%MWm.MOD.2 E Module status x0 = 1 Defective modulex1 = 1 Operating fault (communication fault

between the CPU and the module,command, adjustment or configurationvalue not accepted, etc.)

x2 = 1 Terminal block fault (not connected)x3 = 1 Self-tests runningx4 = 1 Reservedx5 = 1 Hardware or software configuration fault

(the existing module is not the onedeclared in configuration, submodulesare not compatible)

x6 = 1 No module presentx7 = 1 Submodule fault

= Implicit exchanges (1) E = Explicit exchanges (2)m = module position (possible values : 0 to 10, 100 0 110, .. 700 to 710) x = bit position(1) The %I values are automatically updated at the start of the task.(2) The %MW values are only updated after READ_STS or READ_PARAM has been executed.

___________________________________________________________________________A1/4

A

1.1-5 Language objects common to all communication channels

A module is composed of at least one communication channel. Each channel has anassociated channel fault bit which is updated for : channel fault, module missing, self-tests etc. The various objects associated with the faults of a channel v are :Implicit exchange objects :


%Im.v.ERR Channel fault = 1 Line fault

%IWm.v.i I Periodic The value depends on the type of communication.%QWm.v.i exchanges

%KWm.v.0 I Configuration 16#00 = UNI-TELWAY masterdata 16#01 = UNI-TELWAY slave

16#03 = Character string mode16#04 = FIPWAY16#05 = Remote TSX 07 (via channel 4 on TSX 37)16#06 = Modbus master16#07 = Modbus slave16#09 = FIPIO agent16#11 = Ethernet

%KWm.v.1 I The content of these words depends on the%KWm.v.j type of communication.

Note : I = implicit exchangesm = module position (possible values 0 to 710)v = channel (0 or 1)i = object number

General 1

___________________________________________________________________________A1/5

A

Explicit exchange objects :


%MWm.v.0 E Current x0 = 1 Read current statusexchange x1 = 1 Send control parameters to the

communication channelx2 = 1 Send adjustment parameters to the

communication channel

%MWm.v.1 E Report x1 = 0 Control parameters received, acceptedby the communication channel

x2 = 0 Adjustment parameters received, accepted by the communication channel

%MWm.v.2 E Standard x0 = 1 No device is operating on the channelchannel status x1 = 1 One device on the channel is faulty

x2 = 1 Terminal block fault (not connected)x3 = 1 Time-out error (check wiring),x4 = 1 Module faulty, missing or self-tests

runningx5 = 1 Hardware or software configuration faultx6 = 1 Communication faultx7 = 1 Application fault (configuration fault,

adjustment fault, etc.)

%MWm.v.3 E Special Depends on the type of communicationchannel status

%MWm.v.4 E Fault counter The number of counters depends on type of communication

%MWm.v.i E Special channel Additional status information depending onfeature the type of communication

%MWm.v.i E Control x0 = 1 Counter resetx1 to x15 Depends on type of communication

Note : E = explicit exchangesm = module position (possible values 0 to 710)v = channel (0 or 1)i = object number

___________________________________________________________________________A1/6

A

1.2 Addressing a communication entity

1.2-1 Principles

In an X_WAY architecture each station is identified by a unique address consisting ofa network number and a station number. Within a station each communication entityis also addressed by a topological address which determines its access path.

Address = { Network no. Station no. } topological address

In the case of communication within a station, the topological address is enough tospecify the path used to reach the destination entity.

Topological Module no. No. of the destination addressaddress = which manages . communication . on the channel :

the communication channel in the (Slave no., etc) channel

Key words are used to simplify access to certain communication entities (UNI-TEserver, PL7-application, etc) or to perform broadcast exchanges.

1.2-2 Addressing system using PL7 language

PL7 language uses communication functions for transmitting and receiving messagesto/from a communication entity. These communication functions are described insection 2 of this part (operation, characteristics, syntax, etc).

A particular feature of these functions is that they offer a language interface whichprovides access to certain station communication entities via key words :

• The key word SYS is used to access the UNI-TE server on the CPU, a channel, acommunication module, etc.

• The key word APP is used to access the PL7 application on a station.

Note

When the sender application wishes to communicate with a text function blockof the PL7-2 or PL7-3 application in a TSX series 7 PLC, the key word has to beAPP.num , where num corresponds to the number of the destination text block ofthe exchange.

• The key word ALL is defined to describe a broadcast. It can replace one of theelements of a topological address. The broadcast level is determined according tothe position of the key word ALL in the address :- if next to the network number, the broadcast applies to all stations on the selected

network (example : 2.ALL provides access to all the stations connected to network2),

- if next to a station number, the broadcast applies to all the entities connected to intra-station communication channels (example : 2.4ALL provides access to all thecommunication entities of station 4 of network 2).

General 1

___________________________________________________________________________A1/7

A

1.2-3 Presentation of the addressing

Local addresses :

Destination address

UNI_TE server of a TSX 37/57 S Y S

PL7_Micro/ Junior application A P P

PL7_3 application APP . number of the text block

UNI_TELWAY slave module . channel . slave no.

Modbus slave module . channel . slave no.

Character mode link module . channel . SYS

Module server module . SYS

Submodule server module . channel . SYS

FIPIO device server \ module . channel . connection point\ SYS

Remote addresses :

Destination address

Destination on a remote network { network . station } local address

Destination on a local network { station } local address

Broadcast addresses :

Destination address

Broadcast to all stations { network . ALL } local address

Broadcast to all modules ALL . SYS

Broadcast to all UNI_TELWAY or Modbusslaves module . channel . ALL

___________________________________________________________________________A1/8

A

01 02 03 04 05 06PS 00 07 08 09 10

01 02 03 04 05 06PS 00 07 08 09 10

1.2-4 Addressing communication channels on the TSX 57

For the TSX 57, the processors must be installed in rack 0. Depending on theconfiguration required, the rack can take a single or double format power supplyoccupying 1 or 2 slots. The modules have a geographical address which depends onthe position of the module in the rack. The communication channels of the processorcan have the following addresses :

Single format power supply in a rack (12 positions for example)

Rack 0

Double format power supply in a rack (12 positions for example)

Rack 0

Addressing channels of a TSX SCY 21600 / SCY 21601 communication module :A TSX 57-20/30 configuration can comprise a maximum of 8 racks numbered from 0to 7 (a maximum of 2 racks for a TSX 57-10 configuration). A communication modulecan be installed in any available position. Channel 0 is integrated in the module,channel 1 is the PCMCIA communication card slot. Channel 2 is reserved for the FIPIOlink in processors which support it. See the table on the following page for details onthe calculation of the number of communication channels.

Module 0. Channel 0, terminal port

Module 0 . Channel 2, integrated FIPIO port

Module 0 . Channel 1, PCMCIA card (host channel)

Module 1 . Channel 2, integrated FIPIO port

Module 1 . Channel 1, PCMCIA card (host channel)

Module 1. Channel 0, terminal port

General 1

___________________________________________________________________________A1/9

A

1.2-5 Definition and number of application-specific communication channels

Application Module/card App-spec. chan s Number

Communicatio n Serial link TSX SCP11i (in processor) No 0 (*)

TSX SCP11i (in TSX SCY 21i) Yes 1

TSX JNP11i (in TSX SCY 21i) Yes 1

TSX SCY 21i (integrated channel) Yes 1

FIPIO agent TSX FPP10 in processor No 0 (*)

FIPIO master integrated in processor No 0 (*)

Ethernet TSX ETY 110 Yes 1

(*) Although these channels are application-specific channels, they are not included in thecalculation of the maximum number of application-specific channels supported by the processor.TSX SCY 21i = TSX SCY 21600 or TSX SCY 21601

Note : only channels configured using PL7 Junior or PL7 Pro software are included.

___________________________________________________________________________A1/10

A

1.2-6 Addressing a TSX SCY 21600 / 21601 communication module

Rack 0

Terminal port

Module 0Channel 0

PCMCIA card PCMCIA cardModule 0 . Channel 1 Module 5 . Channel 1

Rack 1

Rack 7

Module 705Channel 0

PCMCIA cardModule 705 . Channel 1

The physical position of the module is defined by the number of the rack in which islocated and by its position in the rack.In the rest of this document, the following symbols are used to symbolize the address :

ADR#{ n . s } m . v . i

For the TSX 57, the geographical position includes the rack number (rack module).Example : ADR#{20.3}705.1.2 = address of slave 2 of channel 1 of the module presentin slot 5 of rack 7 of station 3 on network 20.

01 02 03 04 05 06PS 00 07 08 09 10

{ n .

Networknumber

s }

Stationnumber

m .

Geographicalposition ofthe module

v .

Channelnumber(0 or 1)

i

Slaveaddress

Integrated link Module 110 Channel 1

PCMCIA card Module 110 . Channel 1

Integrated link Module 5 Channel 0

Integrated link

General 1

___________________________________________________________________________A1/11

A

UNI-TELWAY

1.2-7 Examples of intra-station addressing

Warning : In the rest of this part, the examples are shown with connections in diagramform. For more details on possible connections between PLCs see part D of the TSXDM 57 installation manual.

A device with address Ad0=8 is A device with address Ad0=1 isconnected to the terminal port of a connected to the integral link of aTSX 57. TSX SCY 21600 / 21601 with address 2.

Address of slave 8 = 0.0.8 Address of slave 1 = 2.0.1

Important : The processor terminal port (channel 0), configured as a master, scansa maximum of 8 slave addresses. The integral link of the TSX SCY21600 / 21601module and PCMCIA TSX SCP111 cards, configured in UNI-TELWAY master orModbus/JBus, scan a maximum of 98 slave addresses.

UNI-TELWAY

Master

SlaveAd0 = 8

Master

SlaveAd0 = 1

Address

Slave addressfrom 1 to 98 if PCMCIA cardfrom 1 to 8 if terminal port

Module i

Always 0, if TSX 370 to 710, if TSX 57

Channel i

0 if terminal port0 if integral link1 if PCMCIA card

___________________________________________________________________________A1/12

A

1.2-8 FIPIO addressing

The FIPIO link is managed by a TSX P57-25 / 35/45, TPCX 5735 or TPMX 5735 managerPLC. It enables TSX 57 and TSX 37 PLC agents or any device which supports the FIPIOagent function to be connected.

Exchanges with the manager are variable ormessage type exchanges. The addressing syntaxfor accessing the UNI-TE message server is asfollows :

\ module . channel. connection point \ SYS

The module can take the value 0 or 1 depending onthe size of the power supply.

The link integrated in the processors is alwayschannel 2. The connection point identifies thedestination PLC on the bus by its bus connectionpoint number which is between 1 and 127.

In the example opposite, the manager addressesthe TSX 57 at connection point 4 :\ 0.2.4\SYS

or the CCX 17 at connection point 8 :\ 0.2.8\SYS

0

4

FIPIO

55

8

General 1

___________________________________________________________________________A1/13

A

ETHERNET

FIPWAY

UNI-TELWAY

FIPWAY

FIPWAY

A

B

C

FIPWAY

1

56

3 4

4

7

5

6

0 3 2 4 5

1 4

2

1

1.2-9 Example of inter-station addressing

During an inter-station exchange (ie. between two stations on the same network or ondifferent networks), the address must, in addition, indicate the network number and thestation number of the destination entity.

The syntax for an inter-station address is as follows :

• The network and station number pairing must be separated with a full stop and putin brackets : {network.station} .

• The module, channel and address number or connection point parameters must beseparated with a full stop and entered after the {network.station} pairing.

• In the event that the destination address contains additional parameters (for example,the module and channel numbers of a connection point), the syntax is :\module.channel.connection point\module.channel.

Example of multi-network addressing :

1) Station B addresses the system of station A :

{21.1}.SYS

2) Station B addresses the system of station C :

{1.2} 0.0.56

Address

DestinationaddressAd0 = x

Channel i

0 for terminal portor integral channel,1 for PCMCIAcommunication card.

Module i

Geographical position of themodule or processor

{ network . station }

Address of thedestination station

network #11 network #13

network #21

___________________________________________________________________________A1/14

A

1.2-10 Example of addressing to a third party device

The example below depicts accessing the system of an CCX17 connected to a FIPIObus (connection point 6) and communicating with text block TXT 8 of a model 40 PLCconnected to network 2.

The address of the TSX7 station 4 PLC text block TXT 8 is :

{2.4}APP.8 network 2, station 4, access to the application (APP logical channel) and text block 8.

The address of the CCX 17 system is :

{2.4}\0.2.6\SYS network 2, station 4, module 0, channel 2 (on a model 40 PLC, the link integratedin the processor is assigned to channel 2), connection point 6, access to thesystem (SYS logical channel).

Note : For a model TSX47-107 PLC, theUNI_TELWAY (SCI) communication moduleintegrated in the processor is accessed via channel100 = 0.100.x

TSX 7

CCX 17

TSX 7

Network 2

Station 4 Station 2

Communicationwith text block TXT8

Network 3

Station 1 Station 3

Communicationwith theCCX 17 system

Connection point 6

FIPIO

FIPWAY

FIPWAY

TSX 7

FIPWAY network 2

{2.4}0.100.x

General 1

___________________________________________________________________________A1/15

A

1.3 Communication from a programming terminal

1.3-1 GeneralThe addresses of TSX 37/57 PLCs communicating via networks are defined by thesoftware. Before any communication can occur, each PLC must therefore have anaddress which is already defined. This address must be known in order to locate a PLCon the network.

The address of the PLC is defined in the PL7 screen of the terminal. After opening anapplication, click on PLC in the menu bar and then on "Define PLC address". A windowopens, and proposes a default address, SYS, corresponding to a local connection. Toestablish a remote connection, the default address must be altered to the destinationaddress of the remote PLC.

1.3-2 Initial connection to an application

The X-WAY network addresses of TSX 37/ 57 PLCs are defined by the software. Whenthe PLC is first started up, each one must be configured by physically connecting aprogramming terminal to the terminal port on each station. The address of the stationon the network must then be defined. When all the station addresses are defined, it isthen possible to connect to any part of the network and access all the remote stationsto perform remote loading, adjustment etc.

Ethernet

Note : a PLC without an application can only be loaded via the terminal port andFIPWAY link on the processor.

Master

Application

___________________________________________________________________________A1/16

A

1.3-3 Local connectionConnect the programming terminal to the TER or AUX port of the PLC.

The default PLC address, SYS, corresponds to the system address of the PLC.

1.3-4 Connection to a UNI-TELWAY slave on the terminal port

Change of address :

1.3-5 Connection to a UNI-TELWAY slave on the PCMCIA card

TSX 57

TSX 37

slave Ad0 = 4

Change of address :

TSX 37

TSX 57

slave Ad0 = 4

General 1

___________________________________________________________________________A1/17

A

1.3-6 Remote connection example : 1

The address of the destination remote PLC will be : {17.1}SYS corresponding tonetwork 17, station 1, system gate SYS.

Network 17FIPWAY

S1

TSX 57

UNI-TELWAY

___________________________________________________________________________A1/18

A

ETHERNET

FIPWAY

UNI-TELWAY

FIPWAY

FIPWAY

A

B

C

FIPWAY

1

56

3 4

4

7

5

6

0 3 2 4 5

1 4

2

1

1.3-7 Remote connection example : 2

The address of the remote PLC will be :

Example 1 : access to station A Example 2 : access to station B{21.1}SYS, corresponding {11.4}SYS correspondingto network 21, station1 to network 11, station 4

network #1

network #11

network #12

network #21

General 1

___________________________________________________________________________A1/19

A

FIPIO

63

1

0

4

1.3-8 Remote connection (FIPIO) example : 3

\ 0.1.0 \ SYS

\ 0.1.4 \ SYS

The default connection point is 63 for a programming terminal.

___________________________________________________________________________A1/20

A

Communication tools 2

___________________________________________________________________________A2/1

A

2.1 Introduction

2.1-1 Role

All X-WAY communication channels of the following types :

• Character mode link,

• UNI-TELWAY, MODBUS fieldbus,

• Modem,

• Modbus+,

• FIPIO manager and agent,

• FIPWAY,

• ETHERNET TCP-IP,

• Bridge,

use a message handling service for data exchanges. The PL7 language interface offersspecial communication functions (which allow transmission and/or reception of messagesto or from a communication entity). The destination entities of an exchange can belocated in the local station, in a remote station on a communication channel, or directlyin the CPU.

The communication functions offer an interface which is independent of the locationof the destination entity, and mask coding of communication requests from the user.They also ensure compatibility of communication with TSX model 40, TSX 17 andSeries 1000 PLCs.

Important

The processing of communication functions is asynchronous in relation to theprocessing of the application task used to activate them. The only exceptions arethe telegram transmission/reception and the operation stop functions, becausetheir execution is completely synchronous with execution of the activating task.A task is said to be synchronous when it is executed entirely during the PLC taskwhich activated it.A task is said to be asynchronous when it is executed during one or more PLC tasksafter that which activated it.

Section 22 Communication tools

Communicationfunction

Terminal port

Character mode

UNI-TELWAY

Modbus/Jbus

Modem

Modbus +

FIPIO manager and agent

FIPWAYETHERNET TCP-IP

Bridge

___________________________________________________________________________A2/2

A

2.1-2 General structure of a communication function

A communication function uses :

• an address parameter,

• parameters specific to a communication operation,

• management parameters.

Each function is structured as follows :

Function (Destination address, Specific parameters, Management parameters)

Each parameter can be programmed either by its address (example, %MW3) or itssymbol (example, Station1).

Destination address

This parameter indicates the exchange destination address. This may either be locatedin the internal words (%MW) or the internal constants (%KW), or be written directly asan immediate value.

To make the preparation phase of the exchange easier, PL7 language has an operatorwith ADR# syntax which permits assignment of an address-type immediate value toa table which always has six consecutive internal words (%MW) or constant words(%KW).

Examples :

%MWi:6: = ADR#{2.4}\0.2.4\SYSStation2:6: = ADR#{1.8}SYS

Specific parameters

These parameters are specific to each type of communication function. They aredescribed in the sections dedicated to these individual functions.

Management parametersThe management parameters are common to all asynchronous communicationfunctions. They comprise :

• a parameter which gives information on the function activity,

• a parameter which specifies the exchange number identifying the current transac-tion,

• a parameter which contains the exchange report (communication report and operationreport),

• a time-out parameter which checks for a lack of response,

• a length parameter for storing the number of bytes to be sent or the number of bytesreceived.


___________________________________________________________________________A2/3

A

These parameters require a table of four consecutive words with the followingstructure :

Word number High order byte Low order byte

Data managed %MWk Exchange number Activity bit

by the system %MWk+1 Operation Communicationreport report

Data managed %MWk+2 Time-out

by the user %MWk+3 Length

• Activity bit (bit 0)

This bit signals the state of execution of the function. It is set to 1 at the start of executionand returns to 0 at the end.

• Exchange number

When a function is transmitted, the system automatically allocates it a number so thatthe exchange can be identified. This number can be used to stop the currentexchange, if necessary (via the CANCEL function).

• Communication report

This report is common to all functions. It is significant when the value of the activitybit changes from 1 to 0. The various values of this report are shown in the followingtable :

Note : The function can detect a parameter error before activating the exchange. In this case,the activity bit remains at 0 and the report is initialized with the values corresponding to the fault.

Important :The parameters of the communication functions are standard objects to which thegeneral rules for immediate, direct or indexed addressing apply, as defined in part Aof the PL7 Reference Manual.It is recommended that the communication function reports are always tested as soonas they have been executed and before they are next activated.On a cold start, it is essential to check that all the communication function managementparameters are reset to 0.

___________________________________________________________________________A2/4

A

• Communication report

Reports whose values are within the range 16#01 to 16#FE concern errors detectedby the processor which executed the function

Value Communication report : low order byte

16#00 Correct exchange

16#01 Exchange stopped on time-out

16#02 Exchange stopped on user request (CANCEL)

16#03 Incorrect address format

16#04 Incorrect destination address16#05 Incorrect management parameter format

16#06 Incorrect specific parameters

16#07 Problem in transmission to destination

16#08 Reserved

16#09 Reception buffer size too small

16#0A Transmission buffer size too small

16#0B No CPU system resources

16#0C Incorrect exchange number

16#0D No telegram received

16#0E Incorrect length

16#10 Network module missing

16#11 No request

16#12 Application server already active

16#13 Incorrect UNI-TE V2 transaction number

16#0F Telegram service not configured

16#FF Message refused


___________________________________________________________________________A2/5

A

• Operation report

This report byte, which is specific to each function, defines the result of the operationon the remote application. It is only significant if the communication report has thefollowing values :- 16#00 (correct exchange).- 16#FF' (message refused).

When the communication report is 16#FF = refused message. An error was detectedin one of the communication modules which leads to the destination. The table belowdefines the result of the operation.

If the communication report = 16#FF

Error code Operation report : (high order byte)Value meaning :

16#01 No resources to CPU

16#02 No line resources

16#03 Device missing or no resource (*)

16#04 Line error

16#05 Length error

16#06 Communication channel fault

16#07 Addressing error

16#08 Application error

16#0B System resource missing

16#0C Communication function not active

16#0D Destination missing

16#0F Intra-station routing problem or channel not configured

16#11 Address format not managed

16#12 No destination resources

16#14 Connection not functioning (example : Ethernet TCP-IP)

16#15 No resource on the local channel

16#16 Access not authorized (example : Ethernet TCP-IP)

16#17 Inconsistent network configuration (example : Ethernet TCP-IP)

16#18 Not available

16#21 Application server stopped

(*) this code is only managed by TSX FPP20 and TSX FPP10 PCMCIA cards

If the communication report = 16#00

Error code Operation report : (high order byte)Value meaning

16#00 Positive result

16#01 Request not processed

16#02 Incorrect response

16#03 Reserved

___________________________________________________________________________A2/6

A

• Length

The length parameter is used both to define the number of characters (bytes) to sendduring a transmission and to store the number of characters (bytes) received afterreceipt of a message.

Important : for a PRINT_CHAR function, for example, the length parameter %MWk+3before a transmission must contain the number of bytes (characters) to be transmitted.Once the characters have been sent, it contains the number of bytes sent as thecommunication report. If another function in the application uses the same reporttable with a number of bytes to be sent which is different from the previous function,%MWk+3 must be initialized with the new number of bytes to be sent. Otherwise,%MWk+3 retains the number of bytes sent by the previous function.

Before each launch of certain communication functions (SEND_REQ, DATA_EXCH,PRINT_CHAR, SEND_TLG), the length parameter must be updated.

• Time-out

The time-out determines the maximum wait time for the response. The time base forthis parameter is 100 ms (the value 0 corresponds to an infinite wait value). If the time-out has expired, the exchange finishes with an error report. In the same way, receiptof a response after the end of the time-out is refused by the system.

Start of function Activity bit = 1Activation of time-outSet report to 0Assignment of exchange no.

End of time-out Receipt of response

Activity bit = 0 Activity bit = 0Report = 1 Stop time-out

Update report

Note :The time-out value of a communication function must be sufficient to ensure that aresponse to the question asked is received. This time depends on the type of networkand the effective load at the time of the transaction.


___________________________________________________________________________A2/7

A

2.1-3 List of communication functions

A number of functions are used for communication between devices. Some functionsare common to several types of communication channel, while others may be specificto a single communication function.

Functions whose execution is asynchronous with the PLC scan :

Function Role

READ_VAR Reads standard language objects : words, bits, double words,internal floating point objects, constant words, system words andbits, timers, monostables, drum controllers, registers, counters

WRITE_VAR Writes standard language objects : word, bit, double word, internalfloating point object, system word and bit

SEND_REQ Sends UNI-TE requests

DATA_EXCH Sends and/or requests receipt of data

PRINT_CHAR Writes a string of characters

INPUT_CHAR Reads a string of characters

OUT_IN_CHAR Sends a character string and waits for a response

READ_GDATA Reads Modbus+ common data

WRITE_GDATA Writes Modbus+ common data

SERVER Immediate server

WRITE_Asyn Writes 1K via message handling

READ_Asyn Reads 1K via message handling

Functions whose execution is synchronous with the PLC scan :

Function Role

SEND_TLG Sends a telegram

RCV_TLG Receives a telegram

CANCEL Stops a current exchange

ROR1_ARB Shifts a table byte to the right

S W A P Swaps bytes in a word table

The ROR_ARB1 and SWAP functions do not carry out communication processing,however it is necessary for processing the response to some UNI-TE requests. Forexample, reading a word table with the SEND_REQ function.

Note : It is recommended to trigger the asynchronous functions on rising and falling edges andnot on state 0 or 1.

___________________________________________________________________________A2/8

A

Hardware and protocols which support these functions :

Function T S X TSX 57 FIP FIPIO UTW UTW CHAR. Modbus Modbus+ ETH

37-10 37-20 WAY M a s t e r S lave m o d e TCP-IP

READ_VAR x x x x x x x x x

WRITE_VAR x x x x x x x x x

SEND_REQ x x x x x x x x x

DATA_EXCH x x x x x x x

PRINT_CHAR x x x x x

INPUT_CHAR x x x x x

OUT_IN_CHAR x x x x x

S E N D _ T L G x x

R C V _ T L G x x

READ_GDATA x x

WRITE_GDATA x x

2.1-4 Help with entering communication functions

Reminder :

When entering a communication function, the user has access to a help screenproviding information on the programming parameters for this function.

Example :


___________________________________________________________________________A2/9

A

Placing a function in the PL7 data entry screen opens the following window :

Communication function parameters can be written from this window by entering theparameters of the selected function one by one in the data entry zone. The List buttonaccesses a new window which enables the parameters of the selected function to beentered easily. The button does not appear for the READ_GDATA, WRITE_GDATA,CANCEL, RCV_TLG, ROR1_ARB and SWAP functions, which do not have anassociated help screen.

The button :

accesses a new window which helps define the address which will be used by thecommunication function.

___________________________________________________________________________A2/10

A

This screen describes the architecture in which the communication function is integrated.

Mode : used to select local communication (within the station) or remote communication(to another station).Three entry levels :

- network level : only for remote communication, this is used to enter the networkaddress of the destination station (network no., station no.) and the station type.

- station level, three types of communication :- to the PL7 application, exchanges to a communication function,- to the PLC system, transmission of a request,- to a device connected to a link (UTW, Modbus, FIPIO, etc) managed by one of the

channels of a station communication module. In this case, the module addressmust be entered. The device level must be entered according to the protocol.

- device level :- specifies the type of destination device and its address.

Notes : The type of communication function may impose restrictions when entering the address. The type of destination PLC may also limit address entry.


___________________________________________________________________________A2/11

A

When this screen is confirmed, it returns to the function parameter entry screen.

Example of a data entry help screen :

When this window is confirmed, PL7 software checks the parameters entered. In caseof error a message is displayed. Confirming this screen writes the communicationfunction parameters in the PL7 screen.

Limitations :In the address entry help screen, some communications (from a UNI-Telway slave)require the destination address to be coded in the transmission buffer. The help windowenables the whole of the part corresponding to ADR# to be entered, advising the userthat the complementary buffer should be coded.Coding the addresses of remote stations can only be performed for the followingdevices : TSX 17, TSX 37, TSX 47-107, TSX 57. Third party devices only permit a gatenumber to be entered, in other cases the address must be entered manually.

Note : when an element has been entered, the data entry help screen shows the type(s) of objectaccepted in the selected field.

___________________________________________________________________________A2/12

A

2.1-5 Limitation of communication functions

TSX 37 PLCs permit the simultaneous execution of 4 communication functions to theterminal port (channel 0) and 4 communication functions to the PCMCIA card (channel 1).

TSX 5710 PLCs permit the simultaneous execution of 16 communication functions toall their communication channels.

TSX 5720 PLCs permit the simultaneous execution of 32 communication functions toall their communication channels.

TSX 5725/30, PCX 5735 and PMX 5735 PLCs permit the simultaneous execution of48 communication functions to all their communication channels.

TSX 5740/45 and PMX 5745 PLCs permit the simultaneous execution of 64communication functions to all their communication channels.

Capacity of PLCs to execute communication functions on each PLC scan accordingto various configuration possibilities :

Capacity TSX 37 TSX 5710 TSX 5720 TSX 5725TSX 5730TSX 5740TSX 5745PCX , PMX

UTW Master terminal port 4 4 4 4

UTW Master PCMCIA or SCY link 4 8 8 8

UTW Slave client terminal port 4 1 1 1

UTW Slave client PCMCIA or SCY link 1 1 1 1

UTW Slave server terminal port 4 4 4 4

UTW Slave server PCMCIA or SCY 4 6 6 6

Modbus PCMCIA or SCY link 4 8 8 8

Modbus terminal port (TSX Micro only) 4

Character mode terminal port 1 1 1 1

Character mode PCMCIA or SCY link 4 8 8 8

FIPWAY messages 4 8 8 8

FIPWAY telegrams (*) 1/10ms 1/10ms 1/10ms 1/10ms

Modbus + 4 - 4 4

ETHERNET - 16 16 16

(*) The TSX FPP20 PCMCIA card permits the sending of a telegram every 10ms.

The performance of the TSX 37/57 PLCs communication functions decreases as theMAST task period increases, but the capacity per PLC scan remains constant.


___________________________________________________________________________A2/13

A

The maximum size of transmissible data depends on the communication channel, thecommunication module and the type of function used for message handling.

Protocol (Channel) max. length in bytes

UNITELWAY (terminal port) 128

Character Mode (terminal port) 120

UNITELWAY (SCP 111, 112, 114) and SCY2160• 240

Character Mode (SCP 111, 112, 114) and SCY2160• 4096

FIPWAY (FPP20) 128

Modbus (SCP 111, 112, 114) and SCY2160• 256

ETHWAY (main server)* 256

ETHWAY (auxiliary server)** 1024

Modbus+ (TSX MBP 100) 200

(*) PLC servers : main server, auxiliary server

(**) The auxiliary server cannot be accessed from a communication function.

___________________________________________________________________________A2/14

A

2.1-6 Server function

TSX P5735, TPCX 5735 and TPMX 5735 processors have two request servers :

PLC scan :

The main server (port 0)*is activated at the beginning of the PLC MAST scan. Theresponse time from the point of view of the client PLC depends on the scan time of theserver PLC. It can process a maximum of 4 requests simultaneously on each PLC scan.All UNI-TE requests are supported. The maximum size of the requests is 256 bytes. Thisentity can be addressed using the topological address SYS or {network.station}SYS.The auxiliary server (port 7)* is only activated on the periodic task at the end of thePLC scan after the MAST task has been processed, before the next scan begins. If thenext scan has higher priority, it can interrupt a request which is in progress. For thisreason, access to this server is reserved for applications which do not require datawhich is read or written to be consistent. The application response time depends onthe PLC scan time. The maximum size of the request is 1024 bytes. It cannot beaccessed from a communication function. The server processes READ / WRITE object(bit or word), Read object list requests.Both servers can be activated simultaneously.(*) see the "X-WAY communication" manual

MAST task

Inputs

Outputs

Processing

Main server

Auxiliary server


___________________________________________________________________________A2/15

A

2.2 Description of the various communication functions

2.2-1 Reading standard objects : READ_VAR

Role

The READ_VAR function is used to read the value of one or more language objects :• internal bit, internal word, system bit, system word, constant word, double internal

word, double constant word,• structured objects (timer, monostable, counter, registers, drum controller).

The objects read must always be consecutive. They can be located in a remote CPUor in a device connected to an ETHERNET TCP-IP, FIPWAY, UNI-TELWAY, Terminalport, Modbus, Modbus+ or Modem communication channel.The response must contain a maximum number of bytes depending on the protocol andon the type of destination product. See the table in section 2.1.

At the end of the read operation, the length of the data received is stored in word 4 ofthe management parameter.Warning : This function cannot be used when an address should be placed at the startof the transmission buffer (UNI-Telway slave). See the UNI-TELWAY section.

Syntax

READ VAR(Address, Type of object, No. of first, Number, Value, Management parameters)

Address Destination address of the exchange (see section 2.1-2). The followingaddresses {Network. Station}APP, {Network.Station}APP.num andaddresses being broadcast (ALL) are not allowed in this field.

Type of object Character string specifying the type of object to be read :%I : external input bit,%IW : external input word,%M : internal bit,%MW : internal word,%S : system bit,%SW : system word,%KW : constant word,%MD : double internal word,%KD : double constant word,%T : timer (PL7-3),%TM : timer (IEC 1131 standard),%MN : monostable,%R : register,%C : counter,%DR : drum controller.

No. of first Double word indicating the index of the first object to be read.Number Word specifying the number of objects to be read.Value Word table containing the value of the objects read.

___________________________________________________________________________A2/16

A

Note :Modbus : only %M and %MW objects can be used,Modbus + : addresses %I and %IW can only be used in Modbus + to access the input data ofa remote device.

In PL7, object type entry must be consistent. It has to be written either in lower case onlyor in upper case only, otherwise the function returns a report corresponding to 16#06(incorrect specific parameters).

For a TSX 37 or a TSX 57 PLC, access to reading internal bits (via UNI-TELWAY) isas follows :• The bit forcing value is returned in the response,• The reading of 1 bit will therefore be composed of two response bytes,

The first containing the value of 8 bits starting at that requested,The second containing the forcing indicator of these bits.

• To read one of the last 8 memory bits, it is necessary to read the last 8 otherwise thefunction returns a 16#01 operation report.

Management Parameters for managing the exchange in progress.parameters The operation report takes one of the following values :

16#00 = Correct read operation,16#01 = Operation error,16#02 = Incorrect response,16#03 = Incorrect response size.

It is not necessary to initialize the length parameter before launching the function.Warning : in the size of the reception table allow for the forcing indicator bytes. Otherwisethe 16#03 default code will reappear in the report.

The READ_VAR function can read up to 1000 consecutive bits in a remote device,whatever the device and protocol used (UNI-TELWAY or Modbus/Jbus).To read more than 1000 bits, it is necessary to use the SEND_REQ function. Note thatTSX 07, TSX 37 and TSX 57 PLCs are unable to send more than 1000 bits followinga read request.


___________________________________________________________________________A2/17

A

Data entry help screen :

This function has 6 parameters

Parameter Object type Comments

Address ADR#%MWx : n ............ the button for accessing address entry help is

grayed out

Type of object to eg : %MW a selection field is offeredbe read

Address of first %MDxobject to be read %KDx ............................ a value entry field is displayed

immediate value

Number of %MWxconsecutive objects %KWx ........................... a value entry field is displayed

immediate value

Response %MWx:n

Report %MWx:4

Symbols are accepted

Screen :

___________________________________________________________________________A2/18

A

Example of use

• The master station reads internal words %M100 to %M109 of the station at address6 on the UNI-TELWAY bus. The value of the words read must be stored starting atinternal word %M10, the management parameters are inserted from %MW40.

TSX 57 Master TSX 37 Slave

Ad0 = 6UNI-TELWAY

%MW40:4)

Activity bit,report,length

%MW10:10,

Content ofthe response

10,

Consecutivenumbers

100,

No. of1st object

OPERATE

(1)

%MW40:X0%I3.0

P /

'%MW',

Type ofobject(internalwords)

(1) READ_VAR(ADR#0.0.6,

Destination address :Module = 0Channel = 0Ad0 = 6


___________________________________________________________________________A2/19

A

Example of network use

Reading a 5-word table %MW0 to %MW4 from the UNI-TELWAY slave with addressnetwork 20, station 1, communication module TSX SCM 2116 in slot 5, channel 1 in thecommunication module, server address Ad0 = 3.

Master

TSX 87

FIPWAY {20.2}{20.1}

UNI-TELWAY

Network 20

Ad0 = 3

Ad0 = 1

OPERATE

(1)

%MW50:X0%I3.1

P /

%MW50:4)


%MW20:5,

Content ofthe response

5,

Consecutivenumbers

0,

No. of1st object

'%MW',

Type ofobject(internalwords)

(1) READ_VAR(ADR#{20.1}5.1.3,

Network = 20Station = 1Module = 5Channel = 1Slave = 3

___________________________________________________________________________A2/20

A

Example of variable exchange with parameter check

Reading a variable

(1):READ_VAR(ADR#3.1.7,'%MW',20,1,%MW1701:1,%MW210:4)

- %I1.2 command input for the function,- %M21 function activity bit,

- management parameter initialization,

- time-out initialization

%MW214 word counts the number of exchanges,%MW 215 word counts the number of correct exchanges,%MW 216 word counts the number of incorrect exchanges.%MW217 word saves the last error message,%Q2.2 external signalling of an exchange fault.

OPERATE

OPERATE

OPERATE

S

/ %MW210:4:=0

%MW212:=50

(1)

%M21

%I1.2%M21

%M21 %MW210:X0

0

%MW211

EN

INC%M215

INC%M216

%MW217:=%MW211

%Q2.2

%M21>

=

<

<>

INC%M214

/ R

S

COMPARE

OPERATE

OPERATE

OPERATE

OPERATE

OPERATE


___________________________________________________________________________A2/21

A

Further information reading bits and the status of certain logic functions :

Examples

Reading 32 internal bits :

READ_VAR( ADR# {20.1}5.1.3, '%M', 0, 32, %MW100:4, %MW50:4)

The reception table must include 8 bytes (4 words), 4 bytes for the value and 4 bytesfor forcing indication.

Value %MW100 0000 0000 1111 1111%MW101 1111 1111 0000 0111

Forcing %MW102 0000 0000 0000 0000%MW103 0000 0000 0000 1111

There is forcing when there is an indicator at 1, the forcing value being that of thecorresponding read bit.

Example :value : 1100 1100forcing : 0101 0101

bit forced to 0bit forced to 1bit not forcedbit not forced

Reading 18 internal bits :

READ_VAR( ADR# {20.1}5.1.3, '%M', 0, 18, %MW100:3, %MW50:4)

The reception table must contain 6 bytes (modulo 8 the closest to 18)

Value %MW100 0000 0000 1111 1111Forcing %MW101 0000 0000 0000 0111

%MW102 0000 1111 0000 0000

___________________________________________________________________________A2/22

A

Reading the current parameters of a timer : %T or %TM

READ_VAR( ADR# {17.1}7.1.3, '%T', 0, 1, %MW100:4, %MW50:4)

Example of reading the parameters of a %T timer 8 bytes must be read, so a 4-word table is required

%MW100 E8 01 Type of preset

%MW101 0F 03 Preset value

%MW102 03 27 Current value

%MW103 00 00 R output

Time base D output

Interpretation of the bytes read :

01 = type of preset (see reference manual TSX RDNET)03 E8 = preset value (1000)27 0F = current timer value (9999)

03 = time base (1mn)00 = current R output value (0 or 1)00 = current D output value (0 or 1)

Reading the current parameters of a %MN monostable :

READ_VAR( ADR# {17.1}7.1.3, '%MN', 0, 1, %MW100:4, %MW50:4)

7 bytes must be read :

%MW100 D2 01 Preset type

%MW101 0F 04 Preset value

%MW102 03 00 Current value

%MW103 00 R output

Time base

Warning : if the current parameters of two monostables are read, the parameters of thesecond begin at the end of the parameters of the first, in other words from byte 8. Thereis therefore a one-byte shift which must be taken into account when the read parametersare being interpreted.The same applies when reading register parameters which are read on an odd numberof bytes (9).In this case, if the parameters of several consecutive functions are being read, therewill be a 1 byte shift to the left for the even parameters in relation to the odd parameters.There is no shift when the number of parameter bytes read is even.

For more explanation, see reference manual TSX DR NET.


___________________________________________________________________________A2/23

A

2.2-2 Writing standard objects : WRITE_VAR

Role

The WRITE_VAR function is used to write the value(s) of one or more language objectsof the same type (internal bit, internal word, constant word, system bit, system word,double internal word, double constant word).

The objects to be written must always be consecutive. They can be located in a remoteCPU or in a device connected to a UNI-TELWAY, Terminal port, FIPWAY, Modbus,Modbus+, ETHWAY communication channel.

Warning : This function cannot be used when an address should be placed at the startof the transmission buffer (UNI-Telway slave). See part D : UNI-TELWAY.

Syntax

WRITE_VAR(Address, Type of object, No. of first, Number, Value, Management parameters)

Address Destination address of the exchange. The following addresses{Network.Station}APP and {Network.Station}APP.num are notallowed in this field. If the PLC is a UNI-TELWAY slave, see part D.

Type of object Character string specifying the type of object to be written :%M : Internal bit,%MW : Internal word,%S : System bit,%SW : System word,%KW : Constant word,%MD : Double internal word,%KD : Double constant word.

No. of first Double word indicating the index of the first object to be written.

Number Word specifying the number of objects to be written.

Value Word table containing the value of the objects to be transmitted.

Management Parameters for managing the exchange (see part D).parameters The operation report takes one of the following values :

16#00 = Correct write operation,16#01 = Operation error,16#02 = Incorrect response.

The length management parameter must not be initialized before the function islaunched.Note : only %M and %MW objects can be used with Modbus and Modbus+.

___________________________________________________________________________A2/24

A




Address ADR#%MWx : n ............. the button for accessing address entry help is

grayed out

Type of object to be eg : %MW a selection field is offeredwritten

Address of first %MDxobject to be written %KDx ............................ a value entry field is displayed

immediate value

Number of %MWxconsecutive objects %KWx ........................... a value entry field is displayed

immediate value

Objects to be sent %MWx : n%KWx : n

Report %MWx : n

Symbols or addresses are accepted

Screen :


___________________________________________________________________________A2/25

A

2.2-3 Example of use

The master station writes 50 internal words (%MW0 to %MW49) to the slave at address6 (Ad0=6). The value of the words to be written is located in internal words %MW100 to%MW149 of the master station, the management parameters are inserted from%MW50.

UNI-TELWAY

Master

Slave 6(Ad0 = 6)

Slave n(Ad0 = n)

OPERATE

(1)

%MW50:X0%I3.5

P /

%MW50:4)


%MW100:50,

Value of thewords to bewritten

50,

No. ofconsecutivewords

0,

No. of the1st wordto bewritten

'%MW',

Internalwords

(1) WRITE_VAR(ADR#0.0.6,

module = 0channel = 0slave = 6

___________________________________________________________________________A2/26

A

Example of multi-network use

Writing a 50-word table (%MW0 to %MW49) to the UNI-TELWAY slave with addressnetwork 20, station 1, TSX SCM 2116 communication module in slot 5, channel 1 in thecommunication module, server address Ad0 = 3. The values to be written are in words%MW0 to %MW49 of the sender, the management parameters are inserted from%MW100.

TSX 7

FIPWAY {20.2}{20.1}

UNI-TELWAY

Network 20

Ad0 = 3

Ad0 = 1

Master

(1) WRITE_VAR(ADR#{20.1}5.1.3,

network = 20station = 1module = 5channel = 1slave = 3

%MW100:4)


%MW0:50,

Value of thewords to bewritten

50,

No. ofconsecutivewords

0,

No. of the1st wordto bewritten

'%MW',

Internalwords

OPERATE

(1)

%MW100:X0%I3.1

P /


___________________________________________________________________________A2/27

A

Example of variable exchange with parameter check

Writing a variable

(1):WRITE_VAR(ADR#3.1.7,'%MW',20,1,%MW1700:1,%MW200:4)

- %I1.2 command input for the function,- %M21 function activity bit,

- management parameter initialization,

- time-out initialization

%MW204 word counts the number of exchanges,%MW 205 word counts the number of correct exchanges,%MW 206 word counts the number of incorrect exchanges.%MW207 word saves the last error message,%Q2.2 external signalling of an exchange fault.

OPERATE

OPERATE

OPERATE

OPERATE

S

/ %M200:4:=0

INC%MW1700

%MW202:=50

(1)

%M20

%M20 %I1.2

INC %MW204

%M20

INC %MW205

INC %MW206

%MW207:=%MW201

%Q2.2

>

=

<

<>

EN

%MW201

0

%M200:X0%M20

/ R

S

COMPARE

OPERATE

OPERATE

OPERATE

OPERATE

OPERATE

___________________________________________________________________________A2/28

A

2.2-4 Sending UNI-TE requests : SEND_REQ

Role

The SEND_REQ function is used to code and send all UNI-TE and Modbus/Jbusrequests and to receive the associated responses (a detailed explanation of UNI-TErequest coding is given in the TSX DR NET Communication Reference Manual,Modbus/Jbus request coding is explained in the TSX DG MDB Manual).

Syntax

SEND_REQ(Address, Request code, Data, Response, Management parameter)

Address Destination address of the exchange (see part D). Addresses{Network.Station}APP, {Network.Station}APP.num are not allowedin this field, unless the sender of the request is a slave. In this case,the address is that of the exchange sender (Ad1), see part D.

Request code This parameter defines the value of the request code conforming tothe UNI-TE standard. It is in decimal notation by default (for example :252 for the unsolicited data request). If the user wishes to code therequests in hexadecimal notation, the request code must have thefollowing syntax : 16# followed by the hexadecimal request code (forexample : 16#FC for the unsolicited data request).

Data to be sent Word table whose value depends on the request to be sent. It mustbe at least one word long even if the request does not contain anyparticular data to be transmitted (Run, Stop, Identification, etc,request). The length of the data to be sent must be stored in the fourthword of the management parameter (length word) before launchingthis function.

Response Word table containing the response data. It must be at least one wordlong even if the request does not contain any particular data to bereceived (unsolicited data request). The length of the data actuallyreceived is given, at the end of the exchange, in the fourth word of themanagement parameter.

Management Parameter for managing the exchange (see part D).parameters The operation report takes one of the following values :

16#00 = Correct operation,16#02 = Incorrect response,16#FD = Operation error,Other = (Request code + 16#30) or 16#FE on positive responsevalue of some requests,

16#FB on response to a mirror request.

Only the value 0 is significant for the unsolicited data request.


___________________________________________________________________________A2/29

A

The fourth word of the management parameter table corresponds to the Lengthparameter (see section 2.1-2). It must contain the length (in bytes) of the data to be sentbefore the function is executed. Once the request has been executed, it is automaticallyupdated and contains the length of the response (in bytes).

The SEND_REQ function is used to read more than 1000 bits in a remote device. Notethat TSX 07, TSX 37 and TSX 57 PLCs are unable to return more than 1000 bits followinga read request.





grayed out

Request code %MWx%KWx ........................... a value entry field is displayedimmediate value

Data to be %MWx : nsent %KWx : n

Response %MWx : n

Report %MWx : 4


Screen :

___________________________________________________________________________A2/30

A

Example of use

Identification by the master station (Network 20 / Station 2) of the station connected tonetwork 20 station 1 and with address Ad0 = 3 on UNI-TELWAY. The identificationrequest is coded 15 in decimal notation (or 0F in hexadecimal notation), and isexplained in detail in the TSX DR NET Communication Reference Manual.

OPERATE

(1)

%MW90:X0%I3.2

P /

15,

Request 15(or 16#0F ifcoding is inhexadecimalnotation)

%MW90:4)

Activity bit,report, length ofreception (inbytes) afterexecution

%MW150:24,

Content of theresponse(receipt of 24words)

%MW0:1,

Data sent (notused = 1 wordlong)

(1) SEND_REQ(ADR#{20.1}5.1.3,

network = 20station =1module = 5channel = 1slave = 3

Network 20

Ad0 = 3

Ad0 = 1

TSX 7

FIPWAY {20.2}{20.1}

UNI-TELWAY

Master

Important : before each launch of the function, initialize the length parameter.In the example : %MW93 = 0.


___________________________________________________________________________A2/31

A

2.2-5 Exchanging text type data : DATA_EXCH

Role

The DATA_EXCH function is used to send and receive data, or to link a transmissionand a reception. This function is used either to exchange data between two PL7applications or to send data to a device with a specific application protocol.

Syntax

DATA_EXCH(Address, Type of operation, Data, Response, Management parameters)

Address Destination address of the exchange in transmission mode oraddress of the sender in reception mode (see part D). If the operationis an exchange type, addresses being broadcast (ALL) are notallowed.

Type of operationThis parameter defines the operation performed.1 = Transmission followed by a request to wait for reception

(cannot be used on UNI-TELWAY slave),2 = Transmission only,3 = Request to wait for reception.

Data Word table whose content is sent to the destination device. It must beat least one word long, even if there is no data to be sent (receptionoperation). The length of the data to be sent (in bytes) must be storedin the fourth word of the management parameter (length word) beforelaunching this function.

Response Word table containing the value of the data received. It must be atleast one word long even if no data has been received (transmissionoperation). The length (in bytes) of the data actually received isindicated, at the end of the exchange, in the fourth word of themanagement parameter.

Management Parameters for managing the exchange (see part D).parameters The operation report takes one of the following values :

16#00 = Correct operation,16#02 = Incorrect operation,16#03 = Incorrect response size (this value is not significant if this

is a transmission operation).

___________________________________________________________________________A2/32

A




Address ADR#%MWx : n ............. the button for accessing address entry help is

grayed out

Exchange, %MWxtransmission, %KWx ..................... a value entry field is displayedreception immediate value ........ a value entry field is displayed

Objects to be %MWx : ntransmitted %KWx : n

Response %MWx : n

Report %MWx : n


Screen :


___________________________________________________________________________A2/33

A

Examples of use

• Transmission of data to station 2 of network 20. Word %MW93 must contain the lengthof data to be transmitted : %MW93 = 20 (10 words to be transmitted).

• Receipt, by station 2, network 20, of data transmitted by station 1, network 20.

{20.1}

FIPWAY

{20.2}

network 20

OPERATE

(1)

%MW90:X0%I3.2

P /

(1) DATA_EXCH(ADR#{20.2}APP,

Destination application address

2,

Sendrequest

%MW70:10,

Content ofdata sent(10 wordslong)

%MW80:1,

Content of datareceived (notused, 1 word)

%MW90:4)

Activity bit, report,length oftransmission

OPERATE

(1)

%MW90:X0%I3.2

P /

(1) DATA_EXCH(ADR#{20.1}APP,

Address of the sending application

%MW90:4)

Activity bit, report,length of reception

3,

Receptionrequest

%MW80:10,

Receptionbuffer(10 words long)

%MW70:1,

Data sent :not used(1 word long)

___________________________________________________________________________A2/34

A

2.2-6 Sending a telegram : SEND_TLG

Role

The SEND_TLG function is used to send telegram type data to a remote PL7application. The data to be sent must not be more than 16 bytes long. Unlike the othercommunication functions, it is processed immediately (synchronously) : the activity bitand time-out parameters do not therefore exist. Consequently the word table assignedto the management parameters only uses two words instead of four. This function canonly be used on FIPWAY, and for stations at address 0 to 15.

Syntax

SEND_TLG(Address, Message data, Management parameters)

Address Destination address of the exchange (see part D). Only addresses{Network.Station}APP or {Network.Station}APP.num are permitted.

Data to be sent Word table containing the data to be sent. The maximum length of thistable is 8 words (16 bytes).

Management Parameters for managing the exchange (see part D).parameters The word table corresponding to the management parameters must

comprise : the communication report and the length of the data to besent.The SEND_TLG communication report is placed at the end of theexchange in the low order byte of the first word of this table and takesthe following values :16#00 = Correct exchange16#03 = Incorrect address format16#04 = Incorrect destination address16#05 = Incorrect management parameters16#06 = Incorrect specific parameters16#07 = Module fault16#0A = Insufficient size of transmission buffer16#0B = No system resources

The length (in bytes) of the data sent must be stored in the secondword of the management parameter (length word) before executingthis function.


___________________________________________________________________________A2/35

A




Address ADR#%MWx : n (n≥6).......... the button for accessing for address entry

help is grayed out

Data to be %MWx : nsent %KWx : n

Report %MWx : n (n≥2)


Screen :

___________________________________________________________________________A2/36

A

Example of use

• Send a telegram of 8 words from station 1 to remote station 3 on FIPWAY network 20.

Word %MW 201 must be initialized to 16 (8 words) before sending the request.

Note : the synchronous execution of this function requires that the operation report be testedimmediately after the program line which activates execution of this function.

OPERATE

(1)

%I3.10

P

(1) SEND_TLG(ADR#{20.3}APP,

Destination address

%MW200:2)

Exchangereport andlength to besent

%MW190:8,

Content oftelegram

{20.1} {20.3}

FIPWAY Network 20


___________________________________________________________________________A2/37

A

2.2-7 Receiving a telegram : RCV_TLG

Role

The RCV_TLG function is used to read telegram type data from a remote PL7application. The data received must not be more than 16 bytes long. Unlike the othercommunication functions, it is processed immediately (synchronously) : the activity bitand time-out parameters do not therefore exist. Consequently the word table assignedto the management parameters only uses two words instead of four. It can be activatedin an event-triggered task, or in the FAST or MAST task. This function can only be usedon FIPWAY, and for stations at address 0 to 15.

Syntax

RCV_TLG(Address, Reception buffer, Management parameters)

Address Contains, at the end of the reception, the address of the stationsending the telegram.High order byte corresponds to the network number (in hexadecimalnotation),Low order byte corresponds to the station number (in hexadecimalnotation).

Reception Word table containing the data received. The maximum length of thisbuffer table is 8 words (16 bytes).

Management Parameters for managing the exchange (see part D).parameters The word table corresponding to the management parameters only

comprises two words : the operation report and the length of the dataactually received.The operation report for sending a telegram is placed in the first wordof this table at the end of the exchange. It takes the following values :16#00 = Correct exchange16#05 = Incorrect management parameters16#06 = Incorrect specific parameters16#09 = Insufficient size of reception buffer16#0B = No system resources16#0D = No telegram received16#10 = Network module missing16#0F = Telegram service not configured.

The length of the data received is indicated in bytes (maximum 16)in the second word of this parameter table.

___________________________________________________________________________A2/38

A

Example of use

• Receiving a telegram of 8 words (16 bytes) from a remote application.

Note

When an RCV_TLG function is programmed in an event-triggered task, it cannot beused in the MAST or FAST tasks.

Note : the synchronous execution of this function requires that the operation report be testedimmediately after the program line which activates execution of this function.

OPERATE

(1)

%I3.11

P

(1) RCV_TLG(%MW300,

Contains the address of the senderat the end of the exchange

%MW320:2)

Exchangereport andlengthreceived

%MW310:8,

Contentof telegramreceived

{20.1} {20.3}

FIPWAY Network 20


___________________________________________________________________________A2/39

A

2.2-8 Writing a character string : PRINT_CHAR

Role

The PRINT_CHAR function is used to send a character string of 4 kbytes, 120 byteson the terminal port, designed to be transmitted via a character mode link or to theterminal port of a PLC. A message can also be sent in the form of an immediate value(series of bytes between apostrophes, for example : 'Message to be sent').Special characters can also be sent. They must start with the character $ followed bythe hexadecimal value of the character to be transmitted. For example $0D. Alternatively,special characters are defined : $R = CR (carriage return), $L = LF (line feed),$N = CR+LF.

Syntax

PRINT_CHAR(Address, String to be sent, Management parameters)

Address Address of the character mode channel sending the message (seesection 2.1). Only system addresses (which end in SYS) are supportedby this function. Examples :{Network.Station}ModuleRack.Channel.SYS,

String to String of bytes containing the character string to be sent. It is eitherbe sent stored in a byte table (%MB..) or supplied as an immediate value. It

has a maximum length of :- 4K bytes to a character string link managed by a TSX SCP111, 112,

114 PCMCIA card, and by the integrated link of the TSX SCY 21600module.

- 120 bytes to a terminal port,- 250 bytes if the value is supplied as an immediate value.The length of the data sent can be stored in the fourth word of themanagement parameter (length word) before executing this function.If the length is initialized to 0, the entire character string is transmitted.

Management Parameters for managing the exchange (see section 2.1-2).parameters The operation report takes one of the following values :

16#00 = Correct operation,16#01 = Operation error,16#02 = Incorrect operation.16#04 = RTS/CTS signal error.

Warning : Sending a character string which is greater than 240 bytes requires severalPLC scans (the string will be fragmented). It is therefore important to ensure that themanagement data is not modified during processing of the function. The systemensures coherent transmission of the string in several fragments, but does not prohibittransmission of another character string between two fragments.

___________________________________________________________________________A2/40

A





grayed out

String transmitted %MBx : n .............. no entry field displayed%KBx : n ............... entry field displayedimmediate value ..... entry field displayed, variable field blank

Report %MWx:4


Screen :


___________________________________________________________________________A2/41

A

Examples of use

• Sending a character string to a video terminal connected to the integrated link of theTSX SCY 21600 / 21601 module of a PLC at address network 17, station 5.

Important : before each launch of the function, initialize the length parameter in thecommunication report word. In the example : %MW113 = 42. In the example :%MW113 = 19. Special characters are preceded by the $ character in the string to besent. $ characters are not sent by the sender, and must therefore not be counted duringparameter length initialization.

Warning :

On a terminal port link configured in Character mode, if the PRINT_CHAR functionis activated while an INPUT_CHAR function is in progress, the PRINT_CHARfunction remains blocked. It is recommended to program a time-out for thesefunctions.

{20.1}{20.3}

FIPWAY Network 20

(1) PRINT_CHAR(ADR#{20.3}2.0.SYS,

Destination address

'Oven overtemp. 4$L$R',

String of bytes containing thedata to be sent

%MW110:4)

Exchange report andlength of string sent

OPERATE

(1)

%MW90:X0%I3.2

P /

___________________________________________________________________________A2/42

A

2.2-9 Reading a character string : INPUT_CHAR

Role

The INPUT_CHAR function is used to send a request to read a character string to acharacter mode communication module. The message received is stored in a table ofbytes %MB.This function is used to receive up to 4 K bytes (120 bytes for the terminal port). It must beconsistent with the channel configuration, or an error will be returned. There are only twopossibilities :

• reading a number of characters : no condition should be configured.

• reading a message : a stop condition must be configured in the configuration screen.

In both cases, resetting the module memory can be requested for the next messagein order to avoid receiving "old data".

Syntax

INPUT_CHAR(Address, Reset, No. of characters to be read, String received,Management parameters)

Address Address of the entity receiving the message (see section 2.1). Onlysystem addresses (which end in SYS) are supported by this function.Examples :{Network.Station}ModuleRack.Channel.SYS,

Reset This parameter specifies a reset of the module reception memory. Itmust be set to 1 for the terminal port .- 0 no memory reset,- 1 memory reset.

No. of characters A value equal to 0 specifies the reading of an available message, inwhich case a stop condition must be specified in the configurationscreen. A value greater than 0 indicates a number of characters tobe read (the maximum length is 4K bytes). No stop condition shouldbe configured. In the case of communication with a terminal port,only the value 0 is permitted .

String received Byte table (%MB) containing the character string or the messagereceived. The length of the data received is stored (in bytes) in thefourth word of the management parameter (length word) once thisfunction has been executed.

Warning : Receiving a character string which is greater than 240 bytes requires severalPLC scans (the string will be fragmented). It is therefore important to ensure that themanagement data is not modified during the processing of the function. The systemensures coherent transmission of the string in several fragments.


___________________________________________________________________________A2/43

A


16#00 = Correct operation,16#01 = Operation error,16#02 = Incorrect operation,16#03 = Incorrect response size,16#06 = Module configured in character mode,16#07 = Module configured in message mode.




Address ADR#%MWx : n............ the button for accessing address entry help is

grayed out

Reset module %MWxmemory %KWx .................. yes / no button displayed

immediate value ..... yes / no button displayed

Number of %MWxcharacters %KWx ................... a value entry field is displayed

immediate value ..... When this number is 0, the next messagewill be received in its entirety

String to be received %MBx : n

Report %MWx : 4


Screen :

___________________________________________________________________________A2/44

A

Example of use

• Same as the previous example, but reading a character string sent by a video terminalconnected to the terminal port (TER) of the PLC at address network 20, station 5.

{20.1} {20.5}

FIPWAY

%MW120:4)

Exchangereport andlength ofstringreceived

%MB200:20,

Content of themessage (inbytes)

0,

Reading thewholecharacterstring

1,

Reset

(1) INPUT_CHAR(ADR#{20.5}0.0.SYS,

Address of the sender of the message

OPERATE

(1)

%MW120:X0%I3.6

P /

Network 20

Video terminal


___________________________________________________________________________A2/45

A

2.2-10 Sending/receiving a character string : OUT_IN_CHAR

Role

The OUT_IN_CHAR function, which can only be used if the communication channelis configured with a stop condition, is used to send a string of 210 bytes maximum (120for the terminal port) followed by a request to receive a message (a single transmissionor reception is also possible). A message can also be transmitted in the form of animmediate value (series of words between apostrophes, for example : 'Message to besent').Special characters can also be sent. They must start with the character $ followed bythe hexadecimal value of the character to be sent. For example : $0D. Alternatively,special characters are defined : $R = CR (carriage return), $L = LF (line feed), $N =CR+LF.

Although this function is mainly used for communication with a terminal port, it can also be usedwith a character mode type link. Upon reception of a message request, the destination moduleresets its reception memory. It is essential to configure message end or silence in theconfiguration screen.

Syntax

OUT_IN_CHAR(Address, Type, String sent, String received, Management parameters)

Address Address of the entity sending the message (see section 2.1-2). Onlysystem addresses (which end in SYS) are supported by this function.Examples :{Network.Station}ModuleRack.Channel.SYS,

Type This parameter specifies the type of operation- 1 Transmission of a message and reception request,- 2 Transmission of a message,- 3 Request to receive a message.

String sent Byte table (%MB..) containing the character string to be sent. It mustbe at least one character long, even if there is no data to be sent. Thelength of the message must be specified (in bytes) in the fourth wordof the management parameter (length word). A length defined as 0leads to the transmission of the entire string.

String received Byte table containing the character string or the message received.It must be at least one character long, even if there is no data to bereceived. The length of the data received is stored in the fourth wordof the management parameter (length word). A stop condition mustalready be configured.

___________________________________________________________________________A2/46

A


16#00 = Correct operation,16#01 = Operation error,16#02 = Incorrect operation,16#03 = Incorrect response size,16#04 = RTS/CTS error,16#06 = Module configured without stop condition.




Address ADR#%MWx : n............. the button for accessing for address entry help is

grayed out

Mode : exchange, %MWxtransmission, %KWx ..................... a value entry field is displayedreception immediate value ........ a value entry field is displayed

String to be %MBx : n ................. a string entry field is displayedtransmitted %KBx : n .................. a string entry field is displayed

immediate value ........ the variable zone is blank

String to be received %MBx : n

Report %MWx:4


Screen :


___________________________________________________________________________A2/47

A

Example of use

• Sending and receiving a character string to and from a video terminal connected tothe terminal port (TER) configured in character mode.

Important : before each launch of the function, initialize the length parameter in thecommunication report word. In the example : %MW173 = 10. At the end of the exchange,it will contain the length of the data received.

OPERATE

(1)

%MW170:X0%I3.8

P /

{20.1} {20.5}

FIPWAY Network 20

Video terminal

%MW170:4)

Exchangereport andlength ofstring sentand stringreceived

(1) OUT_IN_CHAR(ADR#{20.5}0.0.SYS,

Address of the destination device for themessage

1,

TransmissionReception

%MB300:10,

Content ofmessage tobe sent

%MB310:10,

Content of themessagereceived

___________________________________________________________________________A2/48

A

2.2-11 Stopping a current exchange : CANCEL

Role

The CANCEL function is used to interrupt an asynchronous function which is inprogress. The exchange number assigned at the start of the transaction is used toidentify the function to be stopped.

This function is executed synchronously with the PL7 program.

Syntax

CANCEL (Exchange number, Report)

Exchange Specifies the number of the exchange whose execution is to benumber interrupted.

Reminder : The exchange number is indicated in the most significantbit of the first word of the management parameters of the function tobe interrupted (see section 2.1-2).

Report The operation report takes one of the following values :16#00 = Communication interrupted, the activity bit of the interrupted

function is set to 0 and its report takes the value 2.16#0C = Incorrect exchange number.

Example of use

Stopping the OUT_IN_CHAR exchange in the previous example :

When the OUT_IN_CHAR function is started, it is automatically assigned an exchangenumber. This characterizes the exchange until the end of the operation. The CANCELfunction uses this number to interrupt this operation.

Reminder : transmission/reception of a character string :

(1) OUT_IN_CHAR(ADR#{20.5}0.0.SYS, 1, %MB300:10, %MB310:10, %MW170:4)

Managementparameter :Exchange number =high order byte of firstword (%MW170)


___________________________________________________________________________A2/49

A

Before cancelling the OUT_IN_CHAR exchange, shift 8 bits to place the high order byteof %MW170 into %MW180 for example. %MW180 will be used by the CANCEL function,and will contain the OUT_IN_CHAR function exchange number.

(1) %MW180:=SHR(%MW170,8)

(1) CANCEL(%MW180,

Contains the exchangenumber of the function to beinterrupted

%MW185)

Report

OPERATE

(1)

OPERATE

(1)

%I3.9

P

___________________________________________________________________________A2/50

A

2.2-12 Shift one byte to the right in a table : ROR_ARB1

Role :

This function carries out a circular shift to the right of ONE byte from a byte table.It is used after a response has been received to certain UNI-TE requests (SEND-REQfunction).The ROR_ARB1 function does not process communication, however it is required forprocessing certain UNI-TE requests. For example, reading a word table with theSEND_REQ function.

Syntax :

ROR1_ARB (byte table)

table Specifies the address of the first word in the table and the number ofbytes in the table to be shifted.

Example :

Reading a 5 word table in the PLC with address network 2 station 4, Request code =36 (16#0036) read objects.

SEND_REQ ( ADR# {2.4} SYS, 16#0036, %MW200:6, %MW210:6, %MW220:4)

request code = read objects

Transmission table :%MW200 = 16#0768 Object type = 07(16 bit integer),

segment = 68 (internal words)

%MW201 = 50 in decimal notation : origin of the table of words to read%MW202 = 05 in decimal notation : number of words to read

Table of words read :

%MW210 = Lo of 1st word 07

%MW211 = Lo of 2nd word Hi of 1st word

%MW212 = Lo of 3rd word Hi of 2nd word

%MW213 = Lo of 4th word Hi of 3rd word

%MW214 = Lo of 5th word Hi of 4th word

%MW215 = not significant Hi of 5th word


___________________________________________________________________________A2/51

A

07 = Type of objects read (16 bit integer)Lo Low-order byteHi Hi-order byte

The low-order byte of the first word contains the type of objects read, the reception tableis therefore shifted by 1 byte.

Shift 1 byte to the right of the table read :

ROR1_ARB (%MW210:6)

after shifting, the table of words read looks like this :

%MW210 = Hi of 1st word Lo of 1st word

%MW211 = Hi of 2nd word Lo of 2nd word

%MW212 = Hi of 3rd word Lo of 3rd word

%MW213 = Hi of 4th word Lo of 4th word


%MW215 = not significant 07

2.2-13 Swapping bytes in a word table : SWAP

The SWAP function is used in a word table to reverse low and high order bytes. Thisfacilitates message management, in particular on Modbus.

Syntax : SWAP (%MW40 : 4)

Example :

%MW40 = 16#0F43 %MW40 = 16#430F%MW41 = 16#21AC ---------> SWAP (%MW40 : 4) ---------> %MW41 = 16#AC21%MW42 = 16#8127 %MW42 = 16#2781%MW43 = 16#8811 %MW43 = 16#1188

first word inthe table

number of words

___________________________________________________________________________A2/52

A

2.2-14 Reading Modbus + common data : READ_GDATA

A TSX Micro or Premium PLC can use global data exchanges to communicate withremote Modbus stations. Global data is a database shared by a maximum of 64 stationson a network. Each station can write 32 words which can be used by all the otherstations, and can read 32 words from each remote station. For PL7 applications, thereare two functions for writing to the Modbus+ network or reading global data from anystation.

The READ_GDATA function is used to read 32 words from a remote station.

Syntax :

READ_GDATA (ADR#0.1.10, %MW... : 32,%MW... : 4)

The TSX MBP 100 PCMCIA card provides the connection to the Modbus+ network. Itshould only be inserted in the host channel on the processor. The host channel ischannel 1.

READ_GDATA (ADR#0.1.10, %MW100 : 32, %MW200 : 4)

The address parameter must be initialized with the value of the node address to whichthe station containing the objects to be read is connected. The reception zone willcontain the value of the global data. It can be a maximum of 32 words in length.At the end of the operation, the management word contains the size, in bytes, of theglobal data produced by the station specified in the address.

position of the processor inthe rack : 0 or 1channel : 1address of the remote station

address of the globaldata reception zone

activity bit,report, length


___________________________________________________________________________A2/53

A

2.2-15 Writing Modbus + common data : WRITE_GDATA

The WRITE_GDATA function is used to write 32 data words to a remote station.

Syntax :

WRITE_GDATA (ADR#0.1.SYS, %MW...: 32, %MW... : 4)

WRITE_GDATA (ADR#0.1.SYS, %MW100:32, %MW200 : 4)

The function is defined to transfer 32 internal %MW words from the PL7 application tothe PCMCIA card common data buffer.The reception address parameter must be initialized with the value of the localModbus+ server. A buffer with a maximum of 32 words contains the data. The entirecontent of the buffer is then copied into the global data database. The length word isnot used.

position of the processor inthe rack : 0 or 1channel : 1TSX MBP 100 PCMCIA cardsystem

address of the zonecontaining the wordsto be produced

activity bit,report, length

___________________________________________________________________________A2/54

A

2.2-16 Immediate server : SERVER

The SERVER function is used to process UNI-TE requests immediately from theapplication program. This function can be activated in the MAST task or in the FAST task.A single SERVER function can be activated by the application at any given moment.It can only be used for processing requests from a Modbus link (TSX SCP 114 PCMCIAcard in a TSX SCY 21601 module configured as a Modbus slave with immediateserver).

Syntax :

SERVER (Client address, Response request, Management parameters)

Client address :Table of three words for storing the "Network Station Gate Module Channel" addressof the module to which the sender of the request is connected. This is an outputparameter.Response request :Word for storing the request code received (high order byte), and the response codesent back (low order byte). This is an output parameter.Management parameters :

High order byte Low order byte Word number

Exchange number Activity bit %MWk

Operation report Communication report %MWk+1

Communication report (low order byte of word 2)

16#00 = correct exchange

16#01 = stop on time-out, it has not been possible to send the response in less than 2 seconds

16#02 = stop on user request : STOP, S0, INIT, warm or cold restart

16#03 = incorrect client address format

16#05 = incorrect management parameter format

16#07 = problem with transmission to destination

16#11 = no request received

16#12 = SERVER function already called by another task

16#FF = message refused

When the communication report is 16#FF (message refused) an error has beendetected. The operation report (high order byte) then takes the value : 16#14 = serverstopped.


___________________________________________________________________________A2/55

A

2.2-17 Asynchronous message handling services : WRITE_Asyn andREAD_Asyn

These two functions are used to write or read 1 Kbyte of PL7 objects via theasynchronous message handling channel of the TSX ETY 110 module.

Principle of exchanges between two stations :

client station

server station

application processing

triggering of theWRITE_Asynfunction

wait for end ofMAST task

sending of the WRITE_Asyn function for period n

reception of asynchronous messages,processing of requests by the serverand immediate sending of theresponse

reception of messages, processingof requests and immediate sendingof the response

triggering of theWRITE_Asynfunction

reception of asynchronous messages,routing of responses to theWRITE_Asyn functions

sending of the WRITE_Asyn function for period n

period n

period n+1

period n+2

Reception of the response in theWRITE_Asyn function (whenactivity bit falls)

It is possible to restart anew WRITE_Asyn function

reception of asynchronous messages,routing of responses to theWRITE_Asyn functions

sending of the WRITE_Asynfunction for period n+2

start of MAST task

start of MAST task

start of MAST task

___________________________________________________________________________A2/56

A

The WRITE_Asyn and Read_Asyn functions are sent at the end of the MAST task onlyif the task is configured for periodic mode.The size of the transmission and reception buffers is expressed in words. It is 512words, that is 1024 bytes.Syntax of the functions :

WRITE_Asyn (address, type of object, word number, number of words, transmissionbuffer, management parameters)

READ_Asyn (address, type of object, word number, number of words, receptionbuffer, management parameters)

Address : table of three words for storing the address of the sender of the requestType of object : type of objects exchanged : '%MW', '%M'Word number : number of the first word to be written or readNumber of words : number of objects to be written or readTransmission or reception buffer : value of the words to be written or the words readManagement parameters : management of the exchange in progress

High order byte Low order byte Word number

Exchange number Activity bit %MWk

Operation report Communication report %MWk+1

Time-out %MWk+2

Length %MWk+3

Communication report (low order byte of word 2)

16#00 = correct exchange

16#01 = stop on time-out, it has not been possible to send the response in less than 2 seconds

16#02 = stop on user request : STOP, S0, INIT, warm or cold restart

16#03 = incorrect function parameter format

16#05 = incorrect destination address

16#07 = no destination

16#09 = reception buffer too small

16#10 = transmission buffer too small

16#11 = no system resource (8 functions already active)

16#19 = incorrect exchange number

16#FF = message refused

A Time-out value must be programmed to stop an exchange which is in progress whenthe response is not sent back to the sender.The length is expressed in bytes.


___________________________________________________________________________A2/57

A

2.3 Compatibility of communication between TSX37/57 and Series 7

In order for communication to be possible between a TSX37 or a TSX 57 and a Series7 PLC such as TSX47-107 or TSX17, they must be compatible at both communicationblock and exchange level.

2.3-1 Communication block compatibility

PL7-3 defines 5 types of Text Block. A Text Block is characterized by destination entities,whereas a function is characterized by a type of operation. The correspondencebetween a Text block and a communication function takes account of two parameters :

• Type of destination

• Type of communication operation

Text Blocks CPL SYS TER TXT TLG Equivalent functions

Local

UTW x Send-Req, Read-var, Write-var**

Fipio x* Send-Req, Read-var, Write-var**

TER port x Print_char/Input_char/out_in_char

Char. mode x Print_char/Input_char/out_in_char

Remote

UNI-TE x Send-Req, Read-var, Write-var**

UTW x Send-Req, Read-var, Write-var**

Fipio x* Send-Req, Read-var, Write-var**

Application x Data_exch

Telegram x Send_TLG, Rcv_TLG

* Only with integrated Fipio link** Send_req performs the same operations as Read_var and Write_var.

2.3-2 Exchange compatibility

Communication functions enable communication with TSX17, TSX47, TSX107 orSeries 1000 PLCs.

___________________________________________________________________________A2/58

A

2.4 General rules for using text blocks

A text block TXT which receives a communication function :Always set TXT,T to H'FF'

A text block TXT which transmits to a function :Always set TXT,T to 0

A function which transmits to a text block, the address is :ADR#{network.station}APP.i where : i = N° of receiver text block

A function which receives a text block, the address is :ADR#{network.station}APP.i where : i = N° of sending text block

The TXT, A parameter contains either the sender address or the destination address(network and station) depending on the direction of the exchange.

Example : Communication between TSX 37 or TSX 57 PLCs and TSX 47 - TSX 107PLCs.

From communication function to text block

From text block to communication functionH'1101'

Station = 01Network =17

Reception of a messagefrom a TSX 57

with the TXT3 text block

TXT3 TXTTXT3,T = H'FF' /* always FF */TXT3,L = lengthTXT,A H'1101'Input TXT3

Data_Exch(ADR#{17.3}APP.3,2,%MW20:10,%MW30:1, %MW50:4)

Data_Exch(ADR#{17.3}APP,3,%MW70:1,%MW80:10,%MW90:4)

Reception

Transmission

Transmission of a messageto a TSX 57

with the TXT4 text block

TXT4 TXTTXT4,T = 0 (always for TSX37 and 57)TXT4,L = Length in bytesTXT4,A = H'1101'Wi = messageOutput TXT4

FIPWAY

{17.1}{17.3}

TSX 107TSX 57

Network 17


___________________________________________________________________________A2/59

A

2.4-1 Example : Exchanges with a UNI-TE server

A function (Read_Var, Write_Var, Send_Req) can communicate with the system of aTSX 17, 47-107 server. In the same way, a SYS Text block can also be used tocommunicate with a TSX37 and TSX 57 server.

The Data_Exch function is used to transmit, receive, exchange data with a PL7application. This type of processing is performed by the TXT type text block in PL7.

Warning : a communication function cannot be used to communicate with a TSX 17PLC text block.

For further information on text blocks, refer to the TXT DR PL7-3 reference manual.

To ensure compatibility, the following programming rules must be observed :

Reading 1 bitfrom the TSX 57

with the TXT3 SYS text block

TXT 3 SYSTXT,C = H'00'TXT,L = 2TXT,A H'1101'Wi = bit numberEXCHG TXT3

Writing 10 words to the TSX 47-107from the TSX 57

WRITE-VAR (ADR#{17.3}SYS,'%MW',0,10, %MW50:10, %MW100:4)

FIPWAY

{17.1}{17.3}

TSX 107TSX 57

Network 17

___________________________________________________________________________A2/60

A

Examples of compatibility

TSX 37/57 TSX 47/107 Compatibilitynetwork 2, station 1 network 2, station 2

Transmission function Reception text block

DATA_EXCHG(ADR#{2.2}APP.8, TXT8,A <--- H'0201' (@ sender) Thus, there is exchange2,%MW10:20,%MW50:1, TXT8,T <--- 255 compatibility between a%MW100:4) INPUT TXT8 transmission function

TXT8,L=40 andTransmission to text block 8. Since text block 8 cannot a reception text block.

recognize the number of theInitialize the length before sender, it is set to wait fortransmission. all possible numbers (255).

Reception function Transmission text block

DATA_EXCHG(ADR#{2.2}APP,3, TXT8,A<--- H'0201' (@ dest.) Thus, there is exchange%MW10:1%MW50:10, TXT8,T<--- 0 compatibility between a%MW100:4) TXT8,L<--- 20 transmission text blockFunction waiting for a text OUTPUT TXT8 andblock whatever its number. The text block always a reception function.

transmits to the number zeroto communicate with acommunication function.

Exchange function Recept./trans. text blockDATA_EXCHG(ADR#{2.2}APP.8, TXT8,A<--- H'0201'1,%MW20:20,%MW50:10, TXT8,T<--- 255 Thus, there is exchange%MW100:4) INPUT TXT8 compatibility between an

exchange functionThe function transmits a message TXT8,A<--- H'0201' andto text block 8 and then waits for TXT8,T<--- 0 a reception text block followeda response from this text block. TXT8,L<--- 20 by a transmission text block.

OUTPUT TXT8

The text block behaves inthe same way as in theprevious two cases.

Reception and transmission Trans./recept. text blockfunction

DATA_EXCHG(ADR#{2.2}APP.8, TXT8,A<--- H'0201' Thus, there is an3,%MW10:1,%MW50:10, TXT8,T<--- 0 incompatibility of exchange%MW100:4) TXT8,L<--- 20 between an exchange text block

EXCHG TXT8 andDATA_EXCHG(ADR#{2.2}APP.8, The text block cannot a transmission function2,%MW10:20,%MW50:1, recognize the number of the followed by a reception%MW100:4) function, therefore it is not function.

possible to initialize the TXT,Tparameter to a value whichcan be used for communicationtransmission and reception.

___________________________________________________________________________A3/1

Configuring the communication function 3A

3.1 Introduction

Before creating an application program, it is necessary to define the physical operatingcontext in which it will be executed, ie the type of processor and the modules locatedin each slot.

The use of communication functions also requires parameters to be defined for thecommunication channels used (choice of protocol, definition of specific parameters,etc).

To do this, PL7 Micro and PL7 Junior software offer the configuration tool whichsimplifies these operations. During online operation, they also offer a debug functionwhich is used to adjust certain parameters so that they are best suited to the application.

3.2 The configuration tool

3.2-1 Accessing the configuration tool

To create a new application, pull down the file menu and select New.The window for configuring TSX 37 or TSX 57 devices appears. A list of processors isoffered for each type. When this choice is confirmed, an "Application Browser" windowappears, from which all the configuration, program creation and diagnostic functionscan be accessed directly.

The icon in the PL7 menu

bar can also be used to openthe Application Browser

Section 33 Configuring the communication function

___________________________________________________________________________A3/2

A

3.2-2 Choosing the processor

TSX 37 and TSX 57 screens are identical for accessing PL7 Micro or PL7 Juniorfunctions. The screens shown as examples in the pages of this part are common to bothproducts with the exception of a few details which will be pointed out.The processor type is shown in a window in the top left-hand corner of the configurationscreen (the default is TSX 37-10). If the default processor type is not suitable, select anew one from those offered in the pull-down menu :

Once the change of processor type has been confirmed, the graphic representation ofthe new processor is displayed on-screen.

___________________________________________________________________________A3/3


Depending on the final configuration required, it is then possible to choose either a singleor double format power supply. At this stage the processor is in position 1.

For TSX 57 PLCs the configuration screen is :The processor displayed in the configuration is that chosen in the New screen. Theprocessor can be changed in this screen as with TSX 37.

___________________________________________________________________________A3/4

A

3.2-3 Choosing TSX 37 communication modules

This choice is made by double-clicking on the position to be configured (position 4, forexample), which displays the following dialog box :

In the Family field, select the type of module (Communication), then, in the Module field,the reference of the module to be configured (TSX STZ 10, for example). Once theselection has been confirmed by OK, the module is declared in its position (this appearsin a frame and contains the module reference).

To access the configuration of a communication module (to modify the protocol or thespecific parameters, etc), simply double-click on this module.

___________________________________________________________________________A3/5


3.2-4 Choosing TSX 57 communication modules

This choice is made by double-clicking on the position to be configured

Select the type of communication module, then confirm. The module will then be in itsposition in the configuration.

To access the configuration of a communication module (to modify the protocol or thespecific parameters, etc), simply double-click on this module.

___________________________________________________________________________A3/6

A

3.3 Presentation of the screens

3.3-1 Description

Each communication family has :

• a PL7 configuration screen for compiling the configuration data to be transmitted tothe communication channel.Example

• a debug and communication test screen, accessible in online mode only, forproviding first level channel diagnostics.Example

___________________________________________________________________________A3/7


3.3-2 Configuration screen

Configuration screens are made up of two distinct parts :

• the upper part (shaded gray), common to all types of configuration screen, is devotedto information about the module and the communication channel. Its content isdescribed below,

• the lower part is devoted to the configuration parameters and data. This zone, specificto the type of communication selected, is described in detail in the rest of thisdocument in the sections reserved for the various types of communication.

Description of the part common to all configuration screens

1 Title bar. This gives the product reference and the module position,

2 Choice of function : Configuration or Debug (available in online mode only),

3 Name of communication module,

4 Choice of communication channel,

5 Selection of communication module assigned to the channel,

6 Choice of communication protocol for the selected module,

7 Assignment of the communication module within a PLC task (communicationmodules must always be declared as MAST task).

2

3

1

4

6 7

5

___________________________________________________________________________A3/8

A

Warning : It is prohibited to modify communication channel configuration parametersonline with the PLC in RUN.

3.3-3 Debug screen

Debug mode can only be accessed in online mode, by selecting Debug from theconfiguration screen.

The debug screens are made up of two distinct parts :

• the upper part (shaded gray), common to all types of debug screen, is devoted toinformation about the module and the communication channel. Its content isdescribed later,

• the lower part is devoted to the debug parameters and data. This zone, specific tothe type of communication selected, is described in detail in the rest of this documentin the sections reserved for the various types of communication.

___________________________________________________________________________A3/9


Description of the part common to all the debug screens

1 Title bar. This gives the product reference and the module position,

2 Choice of function : Debug (available in online mode only) or Configuration,

3 In addition to the description of the communication module and its version, this fielddisplays the status of the indicator lamps on the front panel of the communicationmodule,

4 When a fault is detected at modulelevel, a DIAGNOSTICS button can beused to access information relating tothe status of this module (whether thisbutton can be accessed or not dependson the value of the module status bit :%I4.0.MOD.ERR),

5 Choice of communication channel,

6 Display of the reference of the communication module assigned to the channel,

7 Choice of communication protocol for the selected module,

8 When a fault is detected at channellevel, a DIAGNOSTICS button can beused to access information relating tothe status of this channel (whether thisbutton can be accessed or not dependson the value of the channel status bit :%I4.0.MOD.ERR),

9 Display of the communication channel ERR indicator lamp.

2

3

1

5

7

6

4

8

9

___________________________________________________________________________A3/10

A

___________________________________________________________________________1

BRemote location of nano-PLCs Contents

Section Page

1 Remote location of nano-PLCs 1/1

1.1 General 1/1

1.2 Data exchange with an analog module 1/41.2-1 Content of %QW words in write mode 1/51.2-2 Content of %IW words in read mode 1/61.2-3 Converting the analog values of input channels 1/8

1.3 Configuration mode 1/101.3-1 General 1/101.3-2 Description of the configuration screen 1/11

1.4 Debug mode 1/121.4-1 Description of the debug screens 1/12

1.5 Language interface 1/14

1.6 TSX STZ 10 module operating modes 1/16

1.7 Performance 1/171.7-1 Network cycle time 1/171.7-2 Positioning an output 1/181.7-3 Summary of the times for positioning a remote output 1/19

1.8 Example of communication with TSX 07 PLCs 1/20

___________________________________________________________________________

2

B Remote location of nano-PLCs Contents

Section Page

Remote location of nano-PLCs 1

___________________________________________________________________________B1/1

B

TSX 07

TSX 07

TSX 07

TSX AMN400.

1

2

3

4

1.1 General

Warning : this section, "remote location of nano-PLCs" only deals with TSX 37PLCs equipped with the STZ 10 communication module.

Reminder :

The TSX STZ 10 module is used to connect a TSX 37 PLC to nano-PLCs in order toincrease the number of I/O or to exchange application data. These various functionsare summarized briefly below (the characteristics of this link (operating principles,connections, addressing, hardware installation, functions, etc) are given in part B2 ofdocument TSX DM 37E.

The rest of this section describes the configuration and operating principles of theTSX STZ 10 module.

I/O data exchanges

This service is used to exchange I/O data between a TSX 37 PLC and up to four nano-PLC remote I/O blocks, which is equivalent to a maximum of 96 additional I/O, orbetween a TSX 37 PLC and three analog I/O blocks, TSX AMN4000 or TSX AMN4001.

TSX 37-10 Master

I/O

I/ORead/Write the I/O

I/O

Analog I/O

The addresses of the I/O blocks are coded by selectors on each TSX07.

On a remote link, address 1 must always be occupied by an I/O block or leftunoccupied. An analog module is configured and exchanged like a "slave PLC"type nano-PLC.

Section 11 Remote location of nano-PLCs

___________________________________________________________________________B1/2

B

1

2

%QW\4.0\2.0

%QW\4.0\2.1

%IW\4.0\2.0

%IW\4.0\2.1

%QW\4.0\4.0

%QW\4.0\4.1

%IW\4.0\4.0

%IW\4.0\4.1

%IW0.0

%IW0.1

%QW0.0

%QW0.1

Application data exchanges

This service is used to exchange application data between a TSX 37 PLC and up tothree nano-PLCs. This data, limited to four words (two production words and twoconsumption words) per nano-PLC, can be exchanged in both directions

Zone One table perreserved nano-PLCfor slave 2

Zonereservedfor slave 4

TSX 37 Master

Slave 2 Slave 3 Slave 4

Mixed link

It possible to mix these two types of exchange on the same link (in this case, the firstdevice should always be configured as an I/O block).

TSX 37 Master

I/O

I/O Analog I/O

Slave 3 (Slave 4)


___________________________________________________________________________B1/3

BObjects exchanged (addressing)

The link between a TSX 37 and the various remote TSX 07s is managed by theTSX STZ 10 module. Since this has to be installed in position 4, the application data(I/O and words) can be accessed by the following syntaxes :

I/O block

• Inputs

%I \ 4.0 \ link address . input number

• Outputs

%Q \4.0 \ link address . output number

Slave PLC

• Input words

%IW \4.0 \ link address . word n°

• Output words

%QW \ 4.0 \ link address . word n°

Example of addressing

Status (%MW) and configuration (%KW) objects atchannel level

Address 1 : I/O

Address 2 : Slave PLC

Address 3 : I/O

Address 4 : Slave PLC

%I\4.0\1.x

%IW\4.0\2.0

%IW\4.0\2.1

%Q\4.0\3.x

%QW\4.0\4.0%QW\4.0\4.1

___________________________________________________________________________B1/4

B1.2 Data exchange with an analog module

Addressing of analog I/O is identical to that of nano-PLC extensions.

An analog module comprises 3 input channels and one output channel. In write mode,the %QW and %IW words exchanged with these modules contain the configurationparameters of each input channel and the value of the output analog channel. In readmode, they contain the status bits of each channel and the value of each channel.For input channel 1, the resolution is dependent on the number of channels configured :12 bits if channels 0 and 1 are configured, and 8 bits if channels 0, 1 and 2 are configured.

%QW\4.0\2.0

%QW\4.0\2.1

%IW\4.0\2.0

%IW\4.0\2.1

%QW\4.0\3.0

%QW\4.0\3.1

%IW\4.0\3.0

%IW\4.0\3.1

%IW0.0

%IW0.1

%QW0.0

%QW0.1

%QW\4.0\4.0

%QW\4.0\4.1

%IW\4.0\4.0

%IW\4.0\4.1

2 3 4

TSX 37

Analogmodule 2

Analogmodule 3

Analogmodule 4

Master

One table peranalogmodule

Analog modules


___________________________________________________________________________B1/5

B1.2-1 Content of %QW words in write mode

The following description is a view from the user program.

Example for an analog module at address 2.

Content of word %QW\4.0\2.0This word contains the configuration of the analog inputs.

Meaning of the configuration bits in word %QW\4.0\2.0

Selection of the channels used :

X1 X0 Number of input channels used

0 0 None

0 1 Channel 0

1 0 Channel 0 and channel 1

1 1 Channel 0, channel 1 and channel 2

Choice of input type :

(X7,X6), (X5,X4), (X3,X2) Input type for the channel

0 0 Voltage input +/- 10V

0 1 Voltage input 0/10V

1 0 Current input 10-20 mA

1 1 Current input 4-20 mA

Choice of filter type :

(X13,X12), (X11,X10), (X9,X8) Filter type for the channel

0 0 Hardware filter

0 1 150 ms filter

1 0 750 ms filter

1 1 3 s filter

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

ConfCh 0Ch 1Ch 2Ch 0Ch 1Ch 2

x0x1x2x3x4x5x6x7x8x9x10x11x12x13x14x15

Number of inputchannels used

Choice of input type

Choice of channelfilter type

___________________________________________________________________________B1/6

BContent of word %QW\4.0\2.1

This word contains the numeric value of the analog output.

The numeric value of the output is defined on 15 bits. The last bit X15 is the sign bit.

1.2-2 Content of %IW words in read mode

The first word %IW\4.0\2.0 contains the value of analog input 0 and the module status.

The value of the analog input is defined on 11 bits and bit X11 is the sign bit. Bits X12to X15 indicate the module status.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


Numeric value of theanalog output

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


Overshootingstops channel 1


Self-calibrationfault

Value of the inputon 12 bits



___________________________________________________________________________B1/7

BThe content of the second word %IW\4.0\2.1 depends on the configuration selected forchannels 0 and 1.Configuration 1 : inputs 0 and 1 are configured, the value of analog channel 1 is asfollows :

In this configuration the value is defined on 15 bits and the last bit X15 is the sign bit.

Configuration 2 : all the 0, 1 and 2 inputs are configured. Word %IW\4.0\2.1 containsthe value of channel 1 and channel 2.

In this configuration the value of the channels is defined on 7 bits. Bits X7 and X15 arethe sign bits.

The input read value for processing by PL7 must be defined on 16 bits with bit X15 asthe sign bit.

Once it has been read, channel 0 must always be processed by the application softwareso that the result can be used by PL7.When channels 0 and 1 are configured, no processing is necessary on the channel 1read value.When all channels 0, 1 and 2 are configured, processing is necessary on the readoperations of channels 1 and 2.

The following examples are given for information purposes for an analog moduleconnected at address 2.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0


Value of the channel 1 input

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0x0x1x2x3x4x5x6x7x8x9x10x11x12x13x14x15



___________________________________________________________________________B1/8

B1.2-3 Converting the analog values of input channels

Converting channel 0

In Ladder language :

%MW0 contains the value of channel 0 coded on 16 bits.

In Instruction List language :

LD %IW\4.0\2.0:X11[%MW0:=%IW\4.0\2.0 OR 16#F000]LDN %IW\4.0\2.0:X11[%MW0:=%IW\4.0\2.0 AND 16#0FFF]


Converting channels 1 and 2 :

Converting the analog value of channel 1 :

In Ladder language :



LD 1[%MW0:=%IW\4.0\2.1 AND 16#00FF]LD %IW\4.0\2.1:X7[%MW1:=%MW0 OR 16#FF00]LDN %IW\4.0\2.1:X7[%MW1:=%MW0]


(%MW0:=%IW\4.0\2.0 OR 16#F000)

%IW\4.0\2.0:X11

(%MW0:=%IW\4.0\2.0 AND 16#0FFF)

%IW\4.0\2.0:X11

OPERATE

OPERATE

(%MW1:=%MW0 OR 16#FF00)

%IW\4.0\2.1:X7

(%MW1:=%MW0)

%IW\4.0\2.1:X7

(%MW0:=%IW\4.0\2.1 AND 16#00FF)OPERATE

OPERATE

OPERATE


___________________________________________________________________________B1/9

BConverting the analog value of channel 2 :



LD 1[%MW0:=%IW\4.0\2.1 AND 16#FF00]LD 1[%MW1:=ROR(%MW0,8)]LD %IW\4.0\2.1:X15[%MW2:=%MW1 OR 16#FF00]LDN %IW\4.0\2.1:X15[%MW2:=%MW1]


(%MW2:=%MW1 OR 16#FF00)

%IW\4.0\2.1:X15

(%MW2:=%MW1)

%IW\4.0\2.1:X15

(%MW1:=ROR(%MW0,8))

(%MW0:=%IW\4.0\2.1 AND 16#FF00)OPERATE

OPERATE

OPERATE

OPERATE

___________________________________________________________________________B1/10

B1.3 Configuration mode

1.3-1 General

The TSX STZ 10 communication module must be installed in position 4 of a TSX 37PLC.

The procedures for installing and accessing the configuration screens for acommunication module are described in part A of this document.

Important comment :

When configuring the TSX07 extension link, the TSX AMN 4000 and TSX AMN4001 analog modules must be declared as slave PLCs.


___________________________________________________________________________B1/11

B1.3-2 Description of the configuration screen

All configuration parameters can be modified in both online and offline mode.

Slave n Specify the function type chosen for the selected slave (the possiblevalues : Absent, I/O block and slave PLC).Reminder : slave 1 can never be configured as a slave PLC.

Filtering Associated with each I/O block type slave, this function is used toassign filtering of 3 or 12 ms (default value) to each of the inputs inorder to be able to avoid interference during acquisition of theseinputs. The filter time represents the minimum time for which an inputmust keep the same value for it to be taken into account.

Signal

3ms filtering

12ms filtering

Transmission rateCorresponds to the data rate. It must be 9600 or 19200 bits/s in thecase of a link comprising slave PLCs only or a mixed link (slave PLCsand I/O block). Its value can be increased to 38400 bits/s in the caseof a link comprising I/O blocks only.

Fallback mode This parameter is used to configure the output fallback position of allthe I/O blocks on the link (Fallback to 0 or Maintain state).

___________________________________________________________________________B1/12

B1.4 Debug mode

1.4-1 Description of the debug screens

Reminder : The gray shaded part of this screen (common to all communicationmodules) is described in section 3 part A of this manual.

The part which is specific to the TSX STZ 10 module debug parameters is made up oftwo windows :

• the Character errors window,

• the Link configuration window.

Character errors window

This window indicates the number of communication errors counted by the TSX STZ 10module.

Transmission Corresponds to the number of errors during transmission. Itis the image of word %MW4.0.7,

Reception Corresponds to the number of errors during reception. It is theimage of word %MW4.0.8,

Reset counters Pressing this button resets the module error counters to zero(corresponds to bit 0 of word %MW4.0.9).


___________________________________________________________________________B1/13

BLink configuration window

Configured Indicates the type of slave configured (Absent, I/O block or slave PLC).

Present Indicates the type of slave physically present (Absent, I/O block orslave PLC).

Err If the slave concerned is faulty, this button is in reverse video.

Diag When the slaveconcerned is faulty, thisbutton contains a cross.Clicking on this crossdisplays a diagnosticscreen which indicatesthe causes of the error.

Data Displays the I/O image of the slave concerned :1 = value of bit at 10 = value of bit at 01F = value of bit forced to 10F = value of bit forced to 0

Example of data of aslave PLC device.

Example of data of anI/O block device

___________________________________________________________________________B1/14

B1.5 Language interface

The various language objects associated with the TSX STZ 10 module are given in thetable below. They are in addition to the language objects which are common to all thecommunication modules presented in part A of this manual :


%I4.0.ERR Status of the link = 1 If there is a configuration error or if one of the devices is faulty.

%I\4.0\dev n°.n Value of remote I/O Value of inputs%Q\4.0\dev n°.n Value of outputs

%IW4.0.0 Device status x0 = 1 If there is a configuration errorxn = 1 If device n is faulty (0 if OK),x5 = 1 If at least one device is faulty.

%IW\4.0\devn°.word Application data Words consumed by the master%QW\4.0\devn°.word values Words produced by the master

%MW4.0.2 Standard channel status x0 = 1 No device operating,x1 = 1 At least one device is faulty,x4 = 1 Self-test fault,x5 = 1 Hardware or software configuration fault,x6 = 1 Communication fault,x7 = 1 Application fault (configuration error, adjustment error, etc).

%MW4.0.3 Specific status One byte per device (byte 0 = device 1, ...,%MW4.0.4 byte 3 = device 4)

16#00 = Correct exchange,16#02 = Character transmission error,16#03 = Character reception error,16#04 = ERROR type PDU,16#05= Incoherence (I/O and PLC),16#06 = Incorrect PDU,16#07 = BCC error,16#08 = Time out error,16#09 = Intercharacter time error,16#81 = Protected outputs fault,16#82 = Power supply fault.

%MW4.0.5 Physical configuration Byte 0 : Value of slave 1slaves 1 and 2 Byte 1 : Value of slave 2

x0 and x1 :00 no slave01 Slave PLC10 I/O slave

x2 and x3 :Type of I/O block :00 = 6I/4O01 = 9I/7O10 = 14I/10O11 = 9I/7O alternative


___________________________________________________________________________B1/15

BLanguage interface (continued)


%MW4.0.6 Physical configuration Byte 0 : slave 3slaves 3 and 4 Byte 1 = slave 4

The coding of these bytes is the same as thatfor slaves 1 and 2

%MW4.0.7 Fault counter Transmission error%MW4.0.8 Control Reception error%MW4.0.9 x0 = 1 Reset counter

x1 = 1 Reactivate outputs slave 1x2 = 1 Reactivate outputs slave 2x3 = 1 Reactivate outputs slave 3x4 = 1 Reactivate outputs slave 4

%KW4.0.0 Type 5 = TSX 37 master

%KW4.0.1 Rate 16#03 = 9600 bits/s16#04 = 19200 bits/s16#05 = 38400 bits/s

%KW4.0.2 Logic configuration One byte per device (byte 0 = device 1, ...,%KW4.0.3 byte 3 = device 4)

16#00 = Absent16#01 = Slave PLC16#02 = I/O block

%KW4.0.4 Filtering Byte 0 (2 bits per device) :01 = 3 ms11 = 12 ms (default value)

Fallback Byte 1 :x0 = 0 Outputs to 0x0 = 1 Maintain outputs

___________________________________________________________________________B1/16

B1.6 TSX STZ 10 module operating modes

General overview

• After power-up, the module performs its self-tests then initializes the applicationconfiguration with the configuration physically present (teach phase) and selects thedefault rate of 19200 bits/s.

• If there is no PL7 application in the PLC, the module is loaded with the configurationphysically present and communicates with the I/O devices only.

• The configuration phase, triggered by the PLC, is used to take the applicationconfiguration into account (rate, devices configured, etc).

• If there is a PL7 application in the PLC, the application configuration is transmittedto the module. In the event of any incoherence or if one of the devices is faulty, theERR indicator lamp flashes. The incoherent devices are interrogated periodically,so that any correction to the configuration is automatically taken into account withoutrestarting the module.

• When the PLC is in STOP, the module only exchanges data with the coherent I/Oblocks. When the PLC changes to RUN, the module can also exchange data with thecoherent slave PLC devices. Common word exchanges with remote TSX 07 PLCsare inhibited during the processing of a modification in RUN.

• In the event of a power break, the PLC CPU performs a warm restart and reconfiguresthe module without the need for any user intervention.

• In the event of a break in communication with the PLC CPU, the module stops allexchanges on the bus.

Module powered off

Stop module Power-up

Module in self-testReset counters phase

Module configured Reactivate Self-tests OKthe I/O

Configuration Module in teachphase

Configuration Teachfinished

Module not configured


___________________________________________________________________________B1/17

B1.7 Performance

1.7-1 Network cycle time

When an STZ10 module is present in position 4, it is recommended, for performancereasons, to associate it with the MAST task.

The network cycle time corresponds to the processing time for all the devices presenton the link, ie :

• updating the inputs/outputs for an I/O device,

• processing the application data for a slave PLC device.

The network cycle time depends on the :

• number and type of slave devices,

• rate of the line.

Example of network cycle with 3 devices on the link.

TEE TIE TEE TIE TEE TIC TEE TIE

Slave 1 Slave 2 Slave 3

Cycle n Cycle n+1

TEE : Basic exchange time. This is the time required for exchanging data between a master and a slave.

TIE : Inter-device time. This is the time required for processing between exchanges with slaves.

TIC : Inter-device time. This is the time required for processing between two cycles.

The tables below give, as a function of the number and type of devices, the minimumPLC scan time required for updating the application data on each cycle :

I/O link

38400 bits/s 1 I/O block 2 I/O blocks 3 I/O blocks 4 I/O blocks

Network cycle time 6.8 ms 12 ms 17.2 ms 22.4 ms

Basic exchange time 3.3 ms 3.3 ms 3.3 ms 3.3 ms

Inter-device time 0 ms 1.9 ms 1.9 ms 1.9 ms

Inter-cycle time 3.5 ms 3.5 ms 3.5ms 3.5 ms

Mini CPU scan time 20 ms 20 ms 20 ms 25 ms

___________________________________________________________________________B1/18

BI/O link (continued)


Network cycle time 10.8 ms 19.9 ms 29.1 ms 38.2 ms

Basic exchange time 6.1 ms 6.1 ms 6.1 ms 6.1 ms


Inter-cycle time 4.7 ms 4.7 ms 4.7 ms 4.7 ms

Min CPU scan time 15 ms 20 ms 30 ms 40 ms


Network cycle time 19.2 ms 36.6 ms 54 ms 71.6 ms

Basic exchange time 12 ms 12 ms 12 ms 12 ms


Inter-cycle time 7 ms 7 ms 7 ms 7 ms

Min CPU scan time 20 ms 40 ms 55 ms 75 ms

1.7-2 Positioning an output

The diagram below shows the difference in time between positioning an in-rack outputand positioning a remote output (it is assumed that the network cycle time is less thanthe PLC scan time and the transmission rate is 38400 bits/s) :

Address 1 Address 2 Address 3 Address 4

In-rack

30 msAddress 1

35 msAddress 2

40 msAddress 3

45 msAddress 4

If several devices are used, the one which is located at the lowest address has theshortest positioning time.


___________________________________________________________________________B1/19

B1.7-3 Summary of the times for positioning a remote output

38400 bits/s Addr 1 Addr 2 Addr 3 Addr 4

1 15 ms

2 20 ms 25 ms

3 27 ms 30 ms 36 ms

4 30 ms 35 ms 41 ms 46 ms


1 20 ms

2 29 ms 38 ms

3 38 ms 47 ms 57 ms

4 48 ms 57 ms 66 ms 75 ms


1 32 ms

2 47 ms 64 ms

3 66 ms 83 ms 100 ms

4 84 ms 101 ms 118 ms 136 ms

The times given above are maximum values which take into account the link cycle timeand the processing times for the remote devices. These times are asynchronous inrelation to each other.

0

10

0

20

30

40

50ms

2 3 41

0

10

0

20

30

40

50

ms

2 3 41

60

70

80

0

20

0

40

60

80

100

ms

2 3 41

120

140

___________________________________________________________________________B1/20

B

%MW0 %QW\4.0\3.0

%IW\4.0\3.0

%IW0.0

%QW0.0

1.8 Example of communication with TSX 07 PLCs

Configuration

Ad0 = 1 I/O block 9 inputs, 7 outputs

Ad0 = 2 I/O block 14 inputs, 10 outputs

Ad0 = 3 Slave PLC

Ad0 = 4 Slave PLC

Aim of the example : to use two TSX 37 internal words (%MW0 and %MW1) as a shiftregister. Each of these words is transmitted to the TSX 07 nano-PLCs configured asslaves. The program for these nano-PLCs consists solely of copying input words tooutput words (%QW0.0 := %IW0.0.....).The TSX 37 PLC then retrieves these output words from the two slave PLCs fortransmission to the outputs of the two PLCs configured as I/O blocks. The TSX 37executes a circular shift operation on words %MW0 and %MW1 every second.

Operating diagram for word %MW0 :

Input wordTSX 37

Slave TSX 07 (I/O)PLC Ad0 = 3

Output word

Zone reserved forthe PLC at address 3

I/O block TSX 07(7 outputs)


___________________________________________________________________________B1/21

BConfiguration screen for the TSX 07 extension link

Reminder of TSX 07 coding

Slave 1 I/O (always I/O) thumbwheel on 1Slave 2 Slave PLC at address 2 thumbwheel on 5Slave 3 I/O thumbwheel on 3Slave 4 Slave PLC at address 4 thumbwheel on 7

___________________________________________________________________________B1/22

BListing

Management of the change limits in %MW0

Management of the change limits in %MW1

Time delay 1 s

On a rising or falling edge at %M0, circular shift one bit to the left of %MW0 and %MW1 togenerate the shifts.

Internal word %MW0 is placed in output word %Q\4.0\3.0:16 which is assigned to the PLC ataddress 3. This output word will correspond to input word %IW0.0

Internal word %MW1 is placed in output word %Q\4.0\4.0:16 which is assigned to the PLC ataddress 4. This output word will correspond to input word %IW0.0

Copy to I/O blocks

OPERATE

%MW0:=1

COMPARE

%MW0>64

COMPARE

%MW0=0

OPERATE

%MW1:=1

COMPARE

%MW0>512

COMPARE

%MW1=0

%M0%S6

OPERATE

%MW0:=ROL(%MW0,1)

%M0

P

OPERATE

%MW1:=ROL(%MW1,1)N

%M0

OPERATE

%Q\4.0\3.0:16=%MW0

OPERATE

%Q\4.0\4.0:16=%MW1

OPERATE

%MW0:=ROL(%MW0,1)

OPERATE

%MW1:=ROL(%MW1,1)

___________________________________________________________________________1

C

Character mode communication Contents

Section Page

1 Character mode communication 1/1



1.3 Debug mode 1/81.3-1 Description of the debug screen 1/8


1.5 Operating modes 1/121.5-1 Character mode PCMCIA cards and terminal port 1/12

1.6 Performance 1/131.6-1 PCMCIA card and integrated link of the SCY 21600 / 21601

communication module in character mode 1/131.6-2 Limitations in character mode with PCMCIA card and the

integrated link of the TSX SCY 21600 / 21601 module 1/131.6-3 Terminal port 1/141.6-4 Limitations in character mode on the terminal port 1/141.6-5 Example of communication in character mode 1/15

___________________________________________________________________________

2

C

Character mode communication Contents

Section Page

Character mode communication 1

___________________________________________________________________________C1/1

C

1.1 Introduction

Communication via character mode is used for performing dialog and communicationfunctions between the PLCs and their environment :

• ordinary peripherals : printer, screen with keypad, workshop terminal,

• specialized peripherals : barcode readers,

• link with a supervisory or production management computer,

• transmission of data between heterogeneous devices (numerical controller, vari-able speed drives, etc),

• link with an external modem.

This type of communication is available on :

• the terminal port of TSX 37 PLCs : in this case, the data exchanged has a maximumlength of 120 characters.

• the various PCMCIA format communication modules which have an integralasynchronous serial link. The character mode link is associated with the physicallayer :- RS232 for the TSX SCP 111 module,- 20 mA current loop for the TSX SCP 112 module,- RS 485/RS422 for the TSX SCP 114 module,- RS 485 for the integrated link of the SCY 21600 / 21601 communication module.

For all these links, the data exchanged has a maximum length of 4 KBytes.

The hardware installation of these various devices is given in the manuals TSX DM 37 E,part E for the terminal port and part K for PCMCIA cards, TSX DM 57E part D.

The remainder of this section describes the configuration and operating principles ofthe various devices.

Section 11 Character mode communication

___________________________________________________________________________C1/2

C

1.2 Configuration mode

1.2-1 General

The procedures for installing and accessing the configuration screens for acommunication module are described in section 3 of this document. The screenexamples shown below are given as a reminder only.

Accessing the configuration of the terminal port in character mode (channel 0 ofthe PLC)

Accessing the configuration of the PCMCIA ports in character mode


___________________________________________________________________________C1/3

C

1.2-2 Description of the configuration screen

Reminder : The gray shaded part of this screen (common to all communicationmodules) is described in part A of this manual.

The part which is specific to the configuration parameters is made up of severalwindows. Depending on the physical layer used, some parameters cannot be modified.They are grayed out. The table below summarizes the various options :

Physical layer RS 232 Int. SCY link CL 20 TerminalRS 485 RS 422 port

Reception echo x x xRestart echo on receipt of first character x xAuto LF x xBackspace x x x x xBeep management x x x x xFlow control via Xon-Xoff x xFlow control via RTS/CTS xRTS/CTS delay xStop reception x x x x xEnd of message (TIC) x x x xPSR management xFull duplex xManagement of DCD carrier x

Note : The terminal port and the integrated link of the TSX SCY 21600 / 21601 communicationmodule are RS485 links.

It is not possible to modify the CONFIGURATION parameters online.

___________________________________________________________________________C1/4

C

Flow control window

RTS / DCD : The RTS and DCD signals are used for hardware management of theflow control.

This type of flow control should be used when the equipment connected to the PCMCIAcard cannot manage the flow control using Xon - Xoff (a low quality printer for example).The PCMCIA card sends the RTS signal to inform the connected equipment (which mustbe plugged via the CTS input) that it is ready to send characters.The DCD signal is used by the PCMCIA card to find out the status of the connectedequipment (must be plugged via the DTR output of the equipment). When the signal isactive, the equipment is ready to receive characters. If the signal is not active, thePCMCIA card stops sending characters to the connected equipment.

Connection principle :

RTS / CTS :

Xon-Xoff Used for software management of the flow control.

5

20

CTS

DTR

RTS

DCD

TSX SCP CD 1030/1130

PCMCIA TSX SCP111

5

4

CTS

RTS

RTS

CTS

TSX SCP CD 1030/1130

PCMCIA TSX SCP111

25-pin SUB-D connector


___________________________________________________________________________C1/5

C

Echo window

On reception Enables management of the reception echo. Any character receivedby the module is resent immediately on the line as an echo. If a writerequest is sent by the PLC during reception, the reception echo isinterrupted. Once the write request is finished, the echo is restartedin one of two ways (see below).

Restart on 1st char.Indicates, once management of the reception echo is enabled, therestart of the echo. This is done in two ways :- either from the first character received,- or from the interrupted character.

CR --> CR LF After each reception of the carriage return character (CR = 16#0D),the module sends, within the echo, the carriage return characterfollowed automatically by the line feed character (LF = 16#0A).

Other functions

Beep managementEmits an audible beep when the module reception buffer is empty orfull (only configured when the card is connected to a man-machineinterface terminal).

Backspace managementThis character corresponds to moving the cursor to the left.- if this management is inhibited, any backspace character received

is stored like any other character,- if this management is enabled, a backspace character received is

not stored and the previous character is deleted. If the module isconfigured to echo, it sends the following three characters :backspace (16#08), then space (16#20) and then backspace again(16#08).

Full Duplex

Enables data transmission and reception to occur simultaneously.

___________________________________________________________________________C1/6

C

Current loop (PSR) window

Multidrop Selection of multidrop communication (20 mA inactive).

Point-to-point Selection of point-to-point communication (0 mA inactive).

Stop on reception window

Two stop reception conditions : via special character or silence. If one of the twoconditions is activated, the function is in message mode. It is therefore impossible toread a number of characters defined in the INPUT_CHAR function.When there is no condition, the INPUT_CHAR function cannot be used in messagemode, and the OUT_IN_CHAR function cannot be used during reception. It is onlypossible to read a number of characters.A reception request can end on receipt of a special character. The following parametersare used to define up to two end characters :

Stop Selects the Stop reception function for an end character.

CR The end character selected is the carriage return.

LF The end character selected is the line feed.

Used to select, via the scroll arrows, the value of both of the endcharacters. The possible values are :- 0 to 255 for 8-bit characters,- 0 to 127 for 7-bit characters.

Character includedDepending on the choice, the selected end character(s) may or maynot be included in the reception table of the PL7 PLC application.

RTS / CTS delay window

Before each transmission of a character string, the module activatesthe RTS signal and waits for activation of the CTS signal. The timedelay (expressed in hundredths of a millisecond) is selected via thescroll arrows and is used to set the maximum waiting period. If thiswaiting period expires, the character string is not sent on the link. Thevalue 0 (default value) indicates that there is no delay managementbetween these two signals.


___________________________________________________________________________C1/7

C

Enabling the data carrier (DCD signal) is useful where the TSX SCP111 PCMCIA card is used with a modem with a controlled data carrier.If this option is enabled, only characters can be received and only ifthe data carrier signal (DCD) is enabled. If nothing is selected, all thecharacters received are taken into account. In other instances ofusing the TSX SCP 111 PCMCIA card, this option is inoperative.

Windows specific to transmission

Transmission speedSpecifies the speed of transmission of data on the line. The speedsavailable are : 300, 600, 1200, 2400, 4800, 9600 and 19200 bits/s.

Stop on silence This parameter is used to detect the end of a message duringreception by the absence of characters for a given time. The timedelay (expressed in milliseconds) is selected via the scroll arrowsand is used to set the length of this silence. The message is receivedby the INPUT_CHAR function.

Data This field specifies the size of the data exchanged on the line. Thepossible values are : 7 or 8 bits.

Stop This field specifies the number of stop bits used as a characterterminator. The possible values are 1 or 2 stop bits.

Parity This field is used to define the optional addition of a parity bit and itstype. The possible values are : Odd, Even or No parity.

The maximum size of data exchanged on the line is :• 1 start bit• 8 data bits• 1 parity bit• 2 stop bits= 12 bits maximum

It is not possible to modify the CONFIGURATION parameters online.

___________________________________________________________________________C1/8

C

1.3 Debug mode

1.3-1 Description of the debug screen


The part which is specific to the parameters for debugging a character mode link is madeup of four windows.

Errors window

This window indicates the number of communication errors counted by thecommunication module : PCMCIA card in the processor or TSX SCY 21600 or 21601communication module.

Transmission Corresponds to the number of errors during transmission, (it is theimage of word %MWm.v.4 for a PCMCIA module present in theprocessor or communication module),

Reception Corresponds to the number of errors during reception, (it is the imageof word %MWm.v.5 for a PCMCIA module present in the processoror communication module),

Reset Counters Pressing this button resets the module error counters to zero (it is theimage of bit 0 of word %MWm.v.15 for a PCMCIA module present inthe processor or communication module).


___________________________________________________________________________C1/9

C

Request Transmission window

This window is used to test a communication channel by transmitting and / or receivinga character string. The content of the string to be sent is entered in the Message Sentwindow, the content of a message received is displayed in the Message Receivedwindow.

Transmission Sends the character string entered in the Message Sent window.

Reception Used to receive a character string which can be viewed in theMessage Received window. Reception stops when the user pressesthe ESC key or if a message is received.

Transmission / ReceptionUsed to send a character string and to wait for its response. Receptionstops when the user presses the ESC key or if a message is received.

Message Sent window

This window is used to enter the message to be sent.Special characters can also be transmitted. They must begin with the character $followed by the hexadecimal value of the character to be transmitted, for example : $0D.

Message Received window

This window displays the character string received and its length. The display can bein either ASCII or Hexadecimal format. The character mode function must be inmessage mode (stop condition configured).

(*) Warning : this function can only be used if a stop condition has been configured whenconfiguring the channel in character mode.

___________________________________________________________________________C1/10

C

1.4 Language interface

The various language objects associated with character mode communication aregiven in the tables below. They are in addition to the language objects which arecommon to all the communication modules presented in section 1 of this manual.

Language interface for PCMCIA cards and for the integrated link of the SCY21600 /21601 communication module


%IWm.v.0 Input signals Byte 0 : Common signalsx0 = DCD signalx1 = RI signalx2 = CTS signalx3 = DSR signal

%QWm.v.0 Output signals Byte 0 :x0 = rising edge at 1 : stops all exchangesin progress

%MWm.v.2 Standard channel status See section 1.1-3

%MWm.v.3 Specific status Character mode type = 3

%MWm.v.4 Fault counters Characters sent with error

%MWm.v.5 Fault counters Characters received with error

%MWm.v.15 Control Byte 0 :x0 = 1 : Reset counterByte 1 :x0 = 1 : DTR ON signalx1 = 1 : DTR OFF signal

%KWm.v.0 Type Character mode function : 3

%KWm.v.1 Rate/Format Byte 0 : Rate00 = 1200 bits/s, ... ..., 04 = 19200 bits/sByte 1 : Formatx0 : No. of bits : 1 = 8 bits, 0 = 7 bitsx1 = 1 : Parity managementx2 : Type of parity : 1 = even, 0 = oddx3 : Stop bit : 1 = 1 bit, 0 = 2 bit

%KWm.v.2 Stop on silence Value of silence in ms (0 = not active)

%KWm.v.3 Various Byte 0x0 = 1 : Reception echox1 = 1 : Restart echo on first characterx2 = 1 : Automatic transmission of Lx3 = 1 : Backspace managementx4 = 1 : Flow control Xon-Xoff activex5 = 1 : Flow control RTS/DCD activex6 = 1 : Beep managementx7 = 1 : Flow control RTS/CTS active


___________________________________________________________________________C1/11

C

Language interface for PCMCIA cards and SCY 21600 / 21601 module (continued)


%KWm.v.4 Signal management Byte 0 : ReservedByte 1x0 = 1 : PSR management (current loop) activex1 = 1 : With Full Duplexx2 = 1 : DCD data carrier management(TSX SCP 111)

%KWm.v.5 RTS / CTS delay Value of delay (in hundredths of amillisecond)

%KWm.v.6 Stop during reception Byte 0(end character 1) x0 = 1 : End character 1 valid

x1 = 1 : End character 1 includedByte 1 : Value of end character

%KWm.v.7 Stop during reception Byte 0(end character 2) x0 = 1 : End character 1 valid

x1 = 1 : End character 1 includedByte 1 : Value of end character

Language interface for the terminal port configured in character mode


%MW0.0.3 Specific status Byte 0 : Character mode type = H'03'

%KW0.0.0 Type Byte 0 : Character mode function = H'03'

%KW0.0.1 Rate/Format Byte 1 : Rate00 = 1200 bits/s, ... ..., 04 = 19200 bits/sByte 1 : Formatx0 : No. of bits : 1 = 8 bits, 0 = 7 bitsx1 = 1 : Parity managementx2 : Type of parity : 1 = even, 0 = oddx3 : Stop bit : 1 = 1 bit, 0 = 2 bitsx4 = 1 : Reception echox5 = 1 : Beep managementx6 = 1 : Backspace management

Communication functions

Three specific communication functions are defined to transmit data to and receive datafrom a character mode communication channel :

Function Meaning

PRINT_CHAR Send a character string

INPUT_CHAR Request to read a character string

OUT_IN_CHAR Send a character string followed by a read request

The use of these functions must be consistent with the configuration.

___________________________________________________________________________C1/12

C

1.5 Operating modes

1.5-1 Character mode PCMCIA cards and terminal port

General overview

• After power-up, the module performs its self-tests.

• If there is no PL7 application in the PLC, the module awaits configuration.

• If there is a PL7 application in the PLC, the application configuration is transmittedto the module.

• In the event of a power break, the PLC CPU performs a warm restart. The module thenrecommences its self-test procedures.

Module powered off


Module configured Communication Module infunction self-test phase

ResetConfiguration Self-tests OK



___________________________________________________________________________C1/13

C

1.6 Performance

1.6-1 PCMCIA card and integrated link of the SCY 21600 / 21601communication module in character mode

Average execution time of the PRINT_CHAR function in ms :

• as a function of the programmed cycle time,• as a function of the number of characters transmitted.

Messagelength 80 characters 960 characters

Speed in bits/s Cycle time Average Averagein ms time time

PCMCIA SCY21600 PCMCIA SCY21600

4800 10 190 210 2100 22004800 25 200 220 2166 23004800 50 200 230 2300 24009600 10 108 125 1120 12009600 25 118 135 1147 12309600 50 137 157 1148 1240

19200 10 62 90 604 70019200 25 75 105 696 80019200 50 100 120 698 810

1.6-2 Limitations in character mode with PCMCIA card and the integrated linkof the TSX SCY 21600 / 21601 module

For TSX 37 PLCs, the TSX SCP 111 PCMCIA card enables simultaneous processing of :

- 4 communication functions which may be :

INPUT_CHAR or PRINT_CHAR or OUT_IN_CHAR

For TSX 57 PLCs, the TSX SCP 111 PCMCIA card and the integrated link of theSCY 21600 / 21601 module enable simultaneous processing for each link of :

- 8 communication functions, which may be :


The maximum permissible size is 4K bytes per communication function.

___________________________________________________________________________C1/14

C

1.6-3 Terminal port

Typical exchange times

Average time of the PRINT_CHAR function in msTransmission of 80 characters

TSX 37/57 TSX 57

Speed Cycle time Average Averagein bits/s in ms time time

1200 10 9391200 20 9451200 50 9481200 100 10001200 255 10184800 10 2424800 20 2424800 50 2494800 100 2994800 255 2559600 10 1299600 20 1399600 50 1499600 100 1999600 255 355

19200 10 _ 6519200 20 _ 7519200 50 _ 10519200 100 _ 15519200 255 _ 285

1.6-4 Limitations in character mode on the terminal port

The TSX 37 terminal port enables simultaneous processing of :- 1 communication function, which may be :


The TSX 57 terminal port enables simultaneous processing of :

- 1 communication function, which may be :


The maximum permissible size is 120 bytes per communication function.


___________________________________________________________________________C1/15

C

1.6-5 Example of communication in character mode

• Transmission then reception of a character string to and from a video terminalconnected to the terminal port (TER) configured in character mode.

Important : before each launch of the function, initialize the length parameter in thecommunication report word. In the example : %MW173 = 10. At the end of the exchange,it will contain the length of the data received. The value 0 is used to send the wholecharacter string.

{20.1} {20.3}

FIPWAY

(1) OUT_IN_CHAR(ADR#{20.3}0.0.SYS, %MW170:4)1, %MB300:10, %MB310:10,

Address ofthe devicereceiving themessage

TransmissionReception Content of the

message to besent

Content ofthe messagereceived

Exchange reportlength of thestring sent, thenof the stringreceived

OPERATE

(1)

%MW40:X0%I3.0

P /

___________________________________________________________________________C1/16

C

___________________________________________________________________________1

D

Communication via UNI-TELWAY bus Contents

Section Page

1 Communication via UNI-TELWAY bus 1/1


1.2 Slave PLC addresses 1/21.2-1 Introduction 1/21.2-2 Master to Slave exchanges 1/31.2-3 Slave to Master exchanges 1/41.2-4 Slave to Slave exchanges 1/81.2-5 Event-triggered data managed by the master 1/14




1.6 Operating modes 1/271.6-1 PCMCIA cards for UNI-TELWAY and integrated link

of the SCY 21600 / 21601 communication module 1/27

1.7 Performance 1/281.7-1 UNI-TELWAY mode PCMCIA cards 1/281.7-2 Limitations of communication via the UNI-TELWAY bus 1/281.7-3 Terminal port 1/291.7-4 Limitations of communication via the terminal port 1/291.7-5 Common restrictions on UNI-TELWAY communication 1/30

___________________________________________________________________________

2

D

Communication via UNI-TELWAY bus Contents

Section Page

Communication via UNI-TELWAY bus 1

___________________________________________________________________________D1/1

D

1.1 Introduction

Communication via UNI-TELWAY bus is used for exchanging data between all devicesconnected to the bus.

This type of communication is available on :

• the terminal port of TSX 37 and TSX 57 PLCs (128 characters),

• the various PCMCIA format communication modules which have an integratedUNI-TELWAY link (240 characters). This link is associated with the physicallayer :- RS232 for the TSX SCP 111 module,- 20 mA current loop for the TSX SCP 112 module,- RS 422 / 485 for the TSX SCP 114 module.

• on the integrated link of the SCY 21600 / 21601 communication module, and thePCMCIA reception channel, RS 485 physical layer (240 characters).

The hardware installation of these various devices is given in manual TSX DM 37E partE for the terminal port and manual TSX DM 57 E part A2 for the terminal port and part Dfor the PCMCIA cards and the TSX SCY 21600 / 21601 modules.


For a detailed description of UNI-TE message handling see the X_way communicationreference manual, and for UNI-TELWAY protocol the UNI-TELWAY communicationuser guide.

Section 11 Communication via UNI-TELWAY bus

___________________________________________________________________________D1/2

D

1.2 Slave PLC addresses

1.2-1 Introduction

A slave PLC can have up to three UNI-TELWAY addresses :

• a server address , called Ad0, which is compulsory and coded by configuration. Itprovides access to the PLC system for such functions as adjustment, diagnostics,reading or writing variables, uploading or downloading programs, etc),

• a client application address , called Ad1 , allocated optionally by configuration to theslave module. It is used for sending messages or requests, requiring a response ornot, to another device connected to the UNI-TELWAY bus,

• a text reception address , called Ad2 , allocated optionally by configuration to theslave module. It is used for receiving Unsolicited Data requests (16#FC) from anotherdevice connected to the UNI-TELWAY bus.

Addresses Ad1 and Ad2 are consecutive with address Ad0 (Ad1 = Ad0 + 1 andAd2 = Ad0 + 2)

Logical entities Example of(processor of the slave PLC) UNI-TELWAY link address

Replies to questions System Ad0 = 6

Asks questions Client application Ad1 = 7of a serverdevice onUNI-TELWAY

Receives "Unsolicited Text reception Ad2 = 8request for the local PL7application


___________________________________________________________________________D1/3

D

1.2-2 Master to Slave exchanges

1 Master to Ad0 :

For communication from the application program of the master to the slave system(access to various objects, etc),

2 Master to Ad2 :

For sending messages from the application program of the master to the applicationprogram of the slave.

The READ_VAR, WRITE_VAR and SEND_REQ functions can be used to communicatewith Ad0.

The SEND_REQ and DATA_EXCH functions may also be used to communicate withAd2.

Example :

SEND_REQ(ADR#0.1.x,16#FC,%MW...........)in this case : use the unsolicited data request code, 16#FC. x = Ad2 of the slave.

Examples :

ADR# 0.1.x for a slave connected to a PCMCIA master

ADR# 0.0.x for a slave connected to a Terminal port master

See the example given in the description of the SEND_REQ function.

1

2

Master

Processor Link

System

Application

Slave

Link Processor

Ad0 System

Ad1 Application

Ad2

___________________________________________________________________________D1/4

D

1.2-3 Slave to Master exchanges

1 Slave (Ad1) to Master :

For communication from the application program of the slave to the master system(access to various objects, etc),

2 Slave (Ad1) to Master :

For sending messages from the application program of the slave to the applicationprogram of the master.

The use of the SEND_REQ function by a slave requires a 6-byte table correspondingto the destination address to be placed at the beginning of the transmission buffer :

The first 6 bytes in the transmission buffer are coded as follows :

Byte 1 (high order) Byte 0 (low order)

WORD1 station networkWORD2 module or selector no. gate no.WORD3 reference if gate 8 channel no.

To transmit to the master system identified by gate 0 :


WORD1 16#FE 16#00WORD2 16#00 16#00WORD3 16#00 16#00

To transmit to the master application identified by gate 16 :


WORD1 16#FE 16#00WORD2 16#00 16#10WORD3 16#00 16#00

Note : in the case of a TSX 47-107 master, the gate number is : 16 + No. of the text block.

1

2

Slave

Link Processor

Ad0 System

Ad1 Application

Ad2

Master

Processor Link

System

Application


___________________________________________________________________________D1/5

D

To send to the system of a remote PLC (network2 . station 3)

Byte 1 (High order) Byte 0 (low order)

WORD1 16#03 16#02WORD2 16#00 16#00WORD3 16#00 16#00

Important : when a slave uses the SEND-REQ function, the address syntax is asfollows :

SEND_REQ (ADR# m.v.i, Request number, %MW start:size, etc.

ADR# m.v.i = address of the sender of the requestm = module 0 or 1 for processors, and >0 for SCY 21600 / 21601 modulev = channel 0 if transmission is via the terminal port or SCY 21600 / 21601 integrated linkv = channel 1 if transmission is via the PCMCIA card (processor or SCY 21600 / 21601module)i = client address of the sender (Ad1 sender)

Request number : see the X-WAY reference manual : TSX DR NET E

%MW 1:size, word table containing the destination address structured as follows :

If master system If master application

%MW1 = FE 00 %MW1 = FE 00%MW2 = 00 00 %MW2 = 00 10%MW3 = 00 00 %MW3 = 00 00%MW4 = request parameters %MW4 = request parameters%MW...= " " %MW...= " "

___________________________________________________________________________D1/6

D

Example of an exchange from the slave to the master system

Master

SlaveAd0 = 6Ad1 = 7

SlaveAd0 = 8

Sending the identification request :

SEND_REQ (ADR#0.1.7 , 15 ,%MW0:3 , %MW10:30 , %MW40:4)

Module 0Chnl 1 (PCMCIA) Identification request (or 16#0F)Sender address (Ad1)

Transmission table : %MW0 = 16#FE 00%MW1 = 16#00 00 Access to the master system gate%MW2 = 16#00 00

Initialization of the length word : %MW43 = 6 (Transmission of 3 words = 6 bytes)

After the exchange : %MW40 = 16#11 00%MW41 = 16#3F 00 16#3F = report >0 (request code +

H'30')

%MW42 = 16#00 00%MW43 = 16#00 14 Reception of H'14' bytes from %MW10

TSX 57

TSX 37

TSX 37

UNI-TELWAY


___________________________________________________________________________D1/7

D

Example of a direct exchange from the slave to the master system

The reception channels of TSX 37 V2.0 processors and TSX SCY 21600 or TSX SCY21601 modules equipped with PCMCIA cards (SCP11i version ≥ 1.5) enable theREAD_VAR and WRITE_VAR communication functions to be used to communicatewith the server of a master or a slave on a single UNI-TELWAY link.

With the SCY 21600 / 21601 module in position 0 of the slave rack and via the integratedlink, the slave 8 server is accessed :

READ_VAR (ADR#2.0.8,'%MW',0,5,%MW20:5,%MW50:4)

The master server is accessed :

READ_VAR (ADR#2.0.0,'%MW',0,5,%MW20:5,%MW50:4)

Ad0 = 8

master

slaveAd0 = 6

slave

TSX 57

TSX 57

TSX 37

UNI-TELWAY

___________________________________________________________________________D1/8

D

1.2-4 Slave to Slave exchanges

1 Slave (Ad1) to destination Slave (Ad0) :

For communication from the application program of the sending slave to the systemof the destination slave (access to various objects, etc).

2 Slave (Ad1) to destination Slave (Ad2) :

For sending messages from the application program of the sending slave to thesystem of the destination slave.

In all cases, requests pass completely transparently via the master.

The use of the SEND_REQ function requires a 6-byte table corresponding to thedestination address to be placed at the beginning of the transmission buffer :

The first 6 bytes in the transmission buffer are coded as follows :


WORD1 16#FE 16#00WORD2 16#FE 16#05WORD3 16#00 slave no. (Ad0 of destination slave)

2

1

Sender slave

Processor Link

System Ad0

Ad1Application

Ad2

Destination slave

Link Processor

Ad0 System

Ad1Application

Ad2

Link

Processor System Application

Master


___________________________________________________________________________D1/9

D

Examples of slave to slave exchanges

Example 1A : exchange to the server of a slave (Ad0)Master

slave :Ad0 = 6Ad1 = 7Ad2 = 8

slave :Ad0 = 9Ad1 = 10Ad2 = 11

Slave 6/7/8 writing a 5-word table to slave 9 by slave 6/7/8 from word %MW50.

SEND_REQ (ADR# 0.1.7, 16#0037, %MW100:11, %MW120:1, %MW130:4)Module 0Chnl 1 (PCMCIA)sender address (Ad1) request code = write objects

Transmission table : %MW100 = 16#FE 00 destination address%MW101 = 16#FE 05 (Ad0 of the slave : Ad0 = 9)%MW102 = 16#00 09

%MW103 = 16#07 68 Type of object = 07,(16-bit integer),segment = 68 (internal words)

%MW104 = 50 in decimal : origin of the word table to be written%MW105 = 05 in decimal : number of words to be written

%MW106 ="" Content of the words to be written%MW110 = in the destination

%MW120:1 No response : 1 byte long

%MW133 Length of data to be sent= 11 words (%MW100 to %MW 110)thus : %MW133 = 22 (bytes)

TSX 57

TSX 37

TSX 37

UNI-TELWAY

___________________________________________________________________________D1/10

D

Example 1B : exchange to the application of a slave (Ad2)

In the PLC which sends the data :

SEND_REQ (ADR# 0.1.7, 16#00FC, %MW100:10, %MW120:1, %MW130:4)

Request code 16#00FC = unsolicited data

Transmission table : %MW100 = 16# FE 00%MW101 = 16# FE 05 destination address%MW102 = 16# 00 0B%MW103 ... application data to be sent

In the PLC which receives the data :

DATA_EXCH (ADR#0.1.11, 3, %MW10:1, %MW20:10, %MW100:4)

Request code 3 = reception request

Reception table : %MW20 = 16# FE 00%MW21 = 16# 00 xx exchange no. of the sender function%MW22 = 16# 00 00%MW23 ... application data received


___________________________________________________________________________D1/11

D

Example 2

The slave at address Ad1 = 7 reading a 5-word table in the slave PLC at addressAd0 = 9. Request code = 36 (16#0036) read objects.

SEND_REQ (ADR# 0.1.7, 16#0036, %MW200:6, %MW210:6, %MW220:4)Module 0Chnl 1 (PCMCIA)sender address (Ad1) request code = read objects

Transmission table: %MW200 = 16#FE 00%MW201 = 16#FE 05 Destination address%MW202 = 16#00 08

%MW203 = 16#07 68' Type of object = 07,(16-bit integer),segment = 68 (internal words)

%MW204 = 50 in decimal : origin of word table to be read%MW205 = 05 in decimal : number words to be read

Table of words read :

%MW210 = Lo of 1st word 07

%MW211 = Lo of 2nd word Hi of 1st word

%MW212 = Lo of 3rd word Hi of 2nd word

%MW213 = Lo of 4th word Hi of 3rd word

%MW214 = Lo of 5th word Hi of 4th word

%MW215= not significant Hi of 5th word

07 = Types of object read (16-bit integer)Lo = low order byteHi = high order byte

The low order byte of the first word read contains the type of object read, and thereception table is shifted by 1 byte.

For this reason, an additional word must be provided in the reception table.Data processing requires a logarithm to process this shift, which is the user's responsibilityfor TSX 37 PLCs (see the following example). For TSX 57 PLCs, this logarithm isprovided by the ROR_ARB1 function.

On transmission, initialize the length word with the number of bytes to be sent%MW223 = 12 (transmission of 6 words)

Once the function has been executed, the length word in the report is as follows :%MW223 = 11 (reception of 11 bytes : 10 (5 words) + 1 (type of object)

___________________________________________________________________________D1/12

D

Example of shift to the right by 1 byte in a byte table

Table to shift : number of bytes contained in %MW99, and starting at %MW100. Workingvariables : %MW0 - %MW 1 - %MW 2 ......

Initialization of the %MW0 index and saving of the first word of the table in %MW1,%MW2 = length of the table -1.

As long as the index is < the length of the table, execute shift operations.

(1) %MW100[%MW0]:=SHR(%MW100[%MW0],8) OR SHL(%MW101[%MW0],8)

(1) %MW100[%MW0] := SHR(%MW100[%MW0],8) OR SHL(%MW1,8)(2) %MW100[%MW0] :=(%MW100[%MW0] AND 16#FF00) OR (%MW1 AND 16#00FF)

OPERATE

DEC %MW2

COMPARE

%MW99 REM 2 = 0

OPERATE

%MW2:=%MW99/2

OPERATE

%MW1:=%MW100[%MW0]

OPERATE

%MW0:=0

OPERATE

(1)

COMPARE

%MW0 < %MW2

OPERATE

INC %MW0

%L1

%L1

OPERATE

(1)

COMPARE

%MW99 REM 2 = 0

OPERATE

(2)

COMPARE

%MW99 REM 2 <> 0


___________________________________________________________________________D1/13

D

After the shift operation, the table of words read is as follows :

%MW210 = Hi of 1st word Lo of 1st word

%MW211 = Hi of 2nd word Lo of 2nd word

%MW212 = Hi of 3rd word Lo of 3rd word



%MW215 = not significant 07

Example 3 : Sending a STOP requestSlave PLC at address Ad0 = 8 set to STOP by the PLC at address Ad1= 7

Master

1

Ad0 = 6Ad1 = 7

Ad0 = 8

SEND_REQ (ADR# 0.1.7, 16#0025, %MW0:3, %MW10:1, %MW40:4)

sender address no receptionSTOP request code length = 1

Transmission table : %MW0 = 16#FE 00 network 00 station FE%MW1 = 16#FE 05 gate 05 module FE%MW2 = 16#00 08 slave station Ad0 = 8

Before each transmission, initialize the length of the transmission table :%MW43 = 6 (3 words = 6 bytes)

TSX 57

TSX 37

TSX 37

UNI-TELWAY

___________________________________________________________________________D1/14

D

1.2-5 Event-triggered data managed by the master

The SEND_REQ function is used to read data from one or more slaves at consecutiveaddresses. The UNI-TELWAY request : 16#82 is used to read event-triggered data byaccessing the UTW PCMCIA server :

SEND_REQ(ADR#0.1.SYS, 16#0082, %MW20:10,%MW50:30,%MW100:4)The transmission buffer contains the following data :

Byte 1 (high order) byte 0 (low order)

%MW21 16#'31 16#06%MW22 16#01 16#00%MW23 Slave No. 16#00%MW24 16#FF 16#00%MW25 16#00 Number of slaves

Note : Reception of event-triggered data from a slave initializes a bit of one of the words: %IW0.1.2or %IW0.1.3. Only UNI-TELWAY master PCMCIA cards handle this type of data.

Event-triggered data : Segment No. 1 byte 16#06Family No 2 bytes 16#0031Type No 2 bytes 16#0001Address 1 byte Slave No.Type of access 2 bytes 16#00FFQuantity 2 bytes 16#00No. of slaves


___________________________________________________________________________D1/15

D


1.3-1 General


Accessing the configuration of the terminal port in UNI-TELWAY mode (channel 0of the PLC)

Accessing the configuration of the PCMCIA cards in UNI-TELWAY mode

___________________________________________________________________________D1/16

D




Physical layer RS 232 RS 485 20CL TerminalSCY int. link port

Type x x x xMaster x x x xSlave x x x xCurrent loop (PSR) xTransmission rate x x x xWait time x x x xData / Stop x x xParity x x xRTS/CTS Delay xManagement of data carrier (DCD) x

The integrated link of the SCY 21600 / 21601 communication module is an RS 485physical layer.

Important : to improve performance during the connection phase of a slave device onUNI-TELWAY, it is advised that the number of slaves is configured in relation to theslaves present and that the addresses are selected starting with 1.


___________________________________________________________________________D1/17

D

Type window

Master Selects UNI-TELWAY master.

Slave Selects UNI-TELWAY slave.

Master window

Event-triggered dataChoice of the size of the event-triggered data. The possible valuesare 0, 4 or 8 bytes. Function only supported by PCMCIA cards : TSXSCP•••.

Number of slavesEnables the selection, using the scroll arrows, of the number of slavesto be scanned by the master. The possible values are between 0 and98. The default value depends on the communication channel (31for a PCMCIA card and the integrated link of the SCY 21600 / 21601module, 8 for the terminal port).

Slave function

Server address (Ad0)Can only be accessed if the UNI-TELWAY Slave communicationfunction is selected. This then enables the device server address(Ad0) to be chosen.

The possible values are between 1 and 98, from 1 to 8 for the terminalport.

Number of addressesCan only be accessed if the UNI-TELWAY Slave communicationfunction is selected. This enables up to three slave addresses to beassigned to the same device. This option is, for example, offered toPLCs which have three slave addresses : a Server address (Ad0),a Client address (Ad1) and a Listening Application address (Ad2).

In these two fields, the scroll arrows are used to select the requiredvalue.

___________________________________________________________________________D1/18

D


Multidrop Selection of multidrop communication (20 mA inactive).

Point-to-point Selection of point-to-point communication (0 mA inactive).


Transmission speedSpecifies the speed of transmission of data on the line. The speedsavailable are : 300, 600, 1200, 2400, 4800, 9600, and 19200 bits/s.The default value is 9600bits/s for the TSX 37 and 19200 bits/s for theTSX 57 terminal port and SCY 21600 / 21601 integrated link.

Wait time This parameter is used to choose the waiting time (time-out) at theend of which the destination station will be considered absent in theevent of no response. The default value is 30 ms.

The scroll arrows are used to select the required value. The possiblevalues are between 1 and 255 ms for the terminal port, and 1 and65000ms for the PCMCIA card and the integrated link of theSCY 21600 / 21601 module.

Data This field specifies the size of the data exchanged on the line. Thepossible values are : 7 or 8 bits.

Stop This field specifies the number of stop bits used. The possible valuesare 1 or 2 stop bits.

Parity This field is used to define the optional addition of a parity bit and itstype. The possible values are : Odd, Even or None.


___________________________________________________________________________D1/19

D


This function is only accessible on TSX SCP 111 PCMCIA cards.

Before each character string transmission the module activates theRTS signal and awaits activation of the CTS signal.

The time delay (expressed in hundredths of a millisecond) is selectedvia the scroll arrows and is used to set the maximum waiting period. Ifthis waiting period expires, the request is not sent on the UNI-TELWAYbus. Value 0 specifies the absence of delay management between thetwo signals.

Enabling the data carrier (DCD signal) is useful where the TSX SCP111 PCMCIA card is used with a modem with a controlled data carrier.If this option is enabled, only characters can be received and only ifthe data carrier signal (DCD) is enabled. If nothing is selected, all thecharacters received are taken into account. In other instances ofusing the TSX SCP 111 PCMCIA card, this option is inoperative.

___________________________________________________________________________D1/20

D

1.4 Debug mode


Reminder : The gray shaded part of this screen (common to all communicationmodules) is described in part A, of this manual.

Note : this screen is not available when remotely connected on a UNI-TELWAY slave.

The part which is specific to the parameters for debugging a UTW link is made up ofthree windows.

Type window

This window indicates the type of UNI-TELWAY function configured(master or slave).

Local error counters window

This window displays the communication module error counters(messages sent and not acknowledged, sent and refused, receivedand not acknowledged and received and refused).

Reset countersResets the communication module error counters to zero.


___________________________________________________________________________D1/21

D

Channel test window

This window is used to test a communication channel by transmitting a UNI-TE request.

When the module is UNI-TELWAY master, this window is used to send a UNI-TE requestto one of the slaves present on the bus. The slave is selected by choosing its link addressfrom the list which is offered.

When the module is UNI-TELWAY slave, the channel test is limited to the master device.

Warning : Sending a request to a slave address which is neither a server norconnected, results in an error message.

Identification Sends the Identification request to the designated slave. The replyto this request is given in the Request Response window. Screenexample :

Counters Sends the Read error counters request to the designated slave. Thereply to this request is given in the Request Response window.

Reset CountersResets the error counters of the designated slave.

Enter Request Sends a UNI-TE request, other than those supplied by the controlbuttons, to the designated slave. The choice of this function givesaccess to a screen for selecting the parameters specific to the request(the request code must be coded in hexadecimal format). Details oncoding a UNI-TE request are given in the network reference manual,TSX DR NET E.

___________________________________________________________________________D1/22

D

Mirror Sends a Mirror request to the designated slave. The choice of thisfunction gives access to a screen for selecting the length of thecharacter string to be sent (a maximum of 80 characters). The PLCsends this character string (ABCD etc), to the destination slave. Thisautomatically sends the received character string to the transmitter.It is then displayed in the Request Response window.

Screen examples.

Response for the transmission of a 12-character message :

Reception of the response :


___________________________________________________________________________D1/23

D


The various language objects associated with UNI-TELWAY communication are givenin the table below. They are in addition to the language objects which are common toall the communication modules presented in part A.

Language interface for a PCMCIA UNI-TELWAY master function and integrated linkof SCY 21600 / 21601 communication modules .


%IWm.v.0 I Input signals Byte 0 : Common signalsx0 = DCD signalx1 = RI signalx2 = CTS signalx3 = DSR signal

%IWm.v.1 I General status of slaves x0 = 1 if at least one slave does not respond

%IWm.v.2 I Event-triggered data 1 bit is dedicated to each slave. If xi = 1%IWm.v.3 status the slave at address i has sent data

%MWm.v.2 E Standard channel status See section 1.1-4

%MWm.v.3 E Specific channel status = 0 for UNI-TELWAY master

%MWm.v.4 E Error counters Messages sent not acknowledged

%MWm.v.5 E Error counters Messages sent and refused

%MWm.v.6 E Error counters Messages received not acknowledged

%MWm.v.7 E Error counters Messages received and refused

%MWm.v.8 E Slave status 1 bit is dedicated to each slave.to If xi = 1 the slave at address i%MWm.v.14 respond

%MWm.v.15 E Control Byte 0 :x0 = 1 : Reset counterByte 1 :x0 = 1 : DTR ON signalx1 = 1 : DTR OFF signalx6 = 1 : Mode change : UNI-TELWAYto character mode (modem)x7 = 1 : Mode change : Charactermode to UNI-TELWAY

%KWm.v.0 I Type = 0 for UNI-TELWAY master

%KWm.v.1 I Speed/Format Byte 0 : Speed00 = 1200 bits/s, ... ..., 04 = 19200 bits/sByte 1 : Formatx0 : No. of bits : 1 = 8 bits, 0 = 7 bitsx1 = 1 : Parity managementx2 : Type of parity : 1 = odd, 0 = evenx3 : Stop bit : 1 = 1 bit, 0 = 2 bits

I = implicit exchanges, E = explicit exchanges

___________________________________________________________________________D1/24

D

Language interface for a PCMCIA UNI-TELWAY master function and integrated linkof the SCY 21600 / 21601 communication module. (continued)


%KWm.v.2 Wait time Value of wait time (time-out) in ms. Thedefault value is 10 ms. Value 0 indicatesthat the wait time has been calculated bythe system

%KWm.v.3 Number of slaves Value from 1 to 98 (default value = 31)

%KWm.v.4 Size of the event- Byte 0 : Value from 0 to 8 bytes (defaulttriggered data and value = 0)signal management Byte 1 :

x0 = 1 if PSR management (current loop)x2 = 1 if data carrier management (TSX SCP111)

%KWm.v.5 RTS/CTS delay Value of the delay in hundredths of milliseconds.The default value is 0 ms and the maximumvalue is 10 s

Language interface for a PCMCIA UNI-TELWAY slave function and integrated linkof the SCY 21600 / 21601 communication module.

The language interface is identical to that for the UNI-TELWAY master function. Onlythose objects defined below are different.


%IWm.v.1 Status address Absence of polling from the masterx0 = 1 on Ad0x1 = 1 on Ad1x2 = 1 on Ad2

%IWm.v.2 Not applicable%IWm.v.3 Not applicable

%MWm.v.3 Specific channel status = 1 for UNI-TELWAY slave

%IWm.v.8 Not applicableto

%IWm.v.14 Not applicable

%KWm.v.0 Type = 1 for UNI-TELWAY slave

%KWm.v.3 Slave addresses Byte 0 :Value of base slave addressByte 1 :Number of consecutive addresses from 1 to 3

%KWm.v.4 Signals Byte 0 :Not significantByte 1 :x0 = 1 if PSR management of (current loop)


___________________________________________________________________________D1/25

D

Language interface for a UNI-TELWAY terminal port master function


%MWm.0.2 Standard channel status Byte 0 : see section 1.1-4Byte 1 : reserved

%MWm.0.3 Specific channel status Byte 0 = 0 UNI-TELWAY master

%MWm.0.4 Slave status Byte 1 : 1 bit dedicated to each slave.If xi = 1 slave number i replies

%KWm.0.0 Type/speed Byte 0 = 0 UNI-TELWAY masterByte 1 : speed

00 = 1200 bits/s,.......04 = 19200 bits/s

%KWm.0.1 Wait time Byte 0 = reservedByte 1 = Value of the wait time (time-out) inms. The default value is 30 ms. The value 0specifies that the wait time has beencalculated by the system.

%KWm.0.2 Number of slaves Byte 0 = number of slaves, value of 1 to thedefault value = 8

Language interface for a UNI-TELWAY terminal port slave function

The language interface is identical to that for the UNI-TELWAY master function. Onlythose objects defined below are different.


%MWm.0.2 Standard channel status Byte 0 : see section 1.1-4Byte 1 : reserved

%MWm.0.3 Specific channel status Byte 0 = 1 UNI-TELWAY slave

%KWm.0.0 Type/speed Byte 0 = 1 UNI-TELWAY slaveByte 1 : speed00 = 1200 bits/s,.......04 = 19200 bits/s

%KWm.0.1 Wait time Byte 0 = reservedByte 1 = Value of the wait time (time-out) inms. The default value is 30 ms. The value 0specifies that the wait time has beencalculated by the system.

%KWm.0.2 Slave addresses Byte 0 = value of server addressByte 1 = number of addresses

___________________________________________________________________________D1/26

D

Communication function

There are five specific communication functions principally defined to transmit data toand receive data from a UNI-TELWAY master or slave device :

Function Meaning

READ_VAR * Reads standard language objects : words, bits, double words, floatingpoint objects, constant words, system words and bits, timers,monostables, drum controllers

WRITE_VAR * Writes standard language objects : words, bits, double words, floatingpoint objects, system bits and word

SEND_REQ Exchanges UNI-TE requests

EXCHG_DATA Sends and/or requests reception of text type data

Man-machine Exchanges various communication functions specific to theinterface man-machine interface (Send_Msg, Send_Alarm, Ask_Msg,functions Ini_Buttons, Control_Leds, Command)

For more detailed information on parameter entry and use of these communicationfunctions, see part A of this manual.

* Note : These functions should not be used by a slave PLC wishing to send a request. TheSEND_REQ function must be used, except for the integrated link of the SCY 21600 /21601 communication module.


___________________________________________________________________________D1/27

D

1.6 Operating modes

1.6-1 PCMCIA cards for UNI-TELWAY and integrated link of the SCY 21600 /21601 communication module

General overview

• After power-up, the module performs its self-tests. During this phase the indicatorlamps flash.


• If there is a PL7 application in the PLC, the application configuration is transmittedto the module and the module starts.

• In the event of a power break, the PLC processor performs a warm restart. The modulethen recommences its self-test procedures.

Module powered off


Module configured Communication Module in self-testfunction phase



___________________________________________________________________________D1/28

D

1.7 Performance

1.7-1 UNI-TELWAY mode PCMCIA cards

Typical exchange times

Average execution time for the READ_VAR function in ms :

Number of objects read : 1 word

Speed in bits/s Cycle time in ms TSX SCP114 TSX SCY2160•

4800 cycl ic 131 1524800 10 160 1704800 50 180 2009600 cycl ic 95 1109600 10 107 1209600 50 167 190

19200 cycl ic 64 8419200 10 67 8719200 50 107 130

Number of objects read : 100 words

Speed in bits/s Cycle time in ms TSX SCP114 TSX SCY2160•

4800 cycl ic 620 6384800 10 640 6604800 50 710 7309600 cycl ic 363 3879600 10 373 3959600 50 402 428

19200 cycl ic 213 23019200 10 214 24019200 50 249 272

1.7-2 Limitations of communication via the UNI-TELWAY bus

The TSX SCP 114 PCMCIA card and the integrated link of the SCY 21600 / 21601module in UNI-TELWAY master mode permit the processing of :• 8 transmission messages to the bus, and 8 reception messages.

The TSX SCP 114 PCMCIA card and the integrated link of the SCY 21600 / 21601module in UNI-TELWAY slave mode permit the processing of :• 6 transactions at the Server address (Ad0),• 1 transaction at the Client address (Ad1),• 8 receptions at application address (Ad2).

The maximum size of each message is 240 bytes.


___________________________________________________________________________D1/29

D

1.7-3 Terminal port

Typical exchange times for TSX 37

Average execution time for the READ_VAR function in ms.For the TSX 37 terminal port the default transmission speed is 9600 bits/s.


Cycle time in ms Average time

10 20520 21350 258100 299255 457

Typical exchange times for TSX 57For the TSX 57 terminal port the default transmission speed is 19200 bits/s.


Cycle time in ms Average time

10 13520 15050 185100 210255 340

1.7-4 Limitations of communication via the terminal port

The terminal port in UNI-TELWAY master mode permits the processing of :• 4 transmission messages to the UNI-TELWAY bus,

• 4 reception messages.

The terminal port in UNI-TELWAY slave mode permits the processing of :

• 4 transactions at server address Ad0,

• 4 transactions at server address Ad1,

• 4 receptions at application address Ad2.


___________________________________________________________________________D1/30

D

1.7-5 Common restrictions on UNI-TELWAY communication

The READ_VAR function can read up to 1000 consecutive bits in a remote device,whatever the device and protocol used (UNI-TELWAY or Modbus/Jbus).To read more than 1000 bits, it is necessary to use the SEND_REQ function. Note thatTSX 07, TSX 37, TSX 57 PLCs are unable to send more than 1000 bits following a readrequest.

___________________________________________________________________________1

E

Communication via Modbus Contents

Section Page

1 Communication via Modbus 1/1


1.2 Configuration mode 1/21.2-1 General 1/21.2-2 Description of the configuration screen 1/31.2-3 Modbus connection on the terminal port 1/8

1.3 Debug mode 1/91.3-1 Description of the master debug screen 1/91.3-2 Description of the slave debug screen 1/11


1.5 Communication function 1/161.5-1 Modbus master function 1/161.5-2 Using the SEND_REQ communication function 1/171.5-3 Modbus slave function 1/18

1.6 Operating modes of the Modbus PCMCIA card and the integrated

link of the SCY 21600 / 21601 module 1/19

1.7 Compatibility between a TSX 37/57 and a Series 1000 PLC 1/201.7-1 Using the READ_VAR and WRITE_VAR functions 1/20

1.8 Performance 1/211.8-1 Typical exchange times in Modbus 1/211.8-2 Limitations of communication via Modbus 1/21

___________________________________________________________________________

2

A

E

Communication via Modbus Contents

Section Page

Communication via Modbus 1

___________________________________________________________________________E1/1

E

1.1 Introduction

Communication via Modbus (master or slave) is used for exchanging data between alldevices connected to the network.

For TSX Premium PLCs this type of communication is available on the various PCMCIAcard format communication modules which have an integrated Modbus link. This linkis associated with the physical layer :

• RS232 for the TSX SCP 111 module,

• 20 mA current loop for the TSX SCP 112 module,

• RS 422 / 485 for the TSX SCP 114 module,

• RS485 for the integrated link of the SCY 21600 / 21601 module.

The maximum message size is 256 bytes.

The hardware installation of these cards is described in the TSX DM 37E manual, partK and the TSX DM 57E manual for PCMCIA cards and the TSX SCY 21600 / 21601module.

TSX micro PLCs, in slave mode, can be connected to Modbus via the terminal port.

For a detailed description of the Modbus protocol, see the Modbus/Jbus communicationuser guide TSX DG MDB E.


Section 11 Communication via Modbus

___________________________________________________________________________E1/2

E


1.2-1 General


Accessing the configuration of the Modbus PCMCIA card


___________________________________________________________________________E1/3

E




Physical layer RS 232 RS 485 CL 20

Master x x xSlave x x xCurrent loop (PSR) xTransmission speed x x xDelay between characters x x xData / Stop x x xParity x x xRTS/CTS delay xData carrier management (DCD) x

The integrated link of the SCY 21600 / 21601 communication module has an RS 485physical layer.

___________________________________________________________________________E1/4

E

Type window

Master Selects the Modbus master.

Slave Selects the Modbus slave.

Master window

Number of retriesSelection of the number of attempts at communication made by themaster before the slave is declared absent.- the default value is 3,- the possible values are between 0 and 15,- the value 0 indicates that the master does not attempt any retries.

Response timeThis is the delay between the time the request is sent by the masterand its repetition in the event of no response from the slave. Themaximum time at the master end between transmission of the lastcharacter and reception of the first character.The default value is 1s (100 x 10ms).The possible values are between 10ms and 10s.Notes :This delay must be greater than the sum of :- the request transmission time, (1)- the response transmission time, (1)- the processing times for the various devices on the bus (slaves,modems, etc.).(1) Approximate transmission time in ms :T = N x (9600 / V) where :- N = number of bytes in the request and its response- V = transmission speed (19200 bits/s, 9600, 4800, 2400, etc)


___________________________________________________________________________E1/5

E

Slave function

Slave numberCan only be accessed if the Modbus Slave communication functionis selected. This then enables the choice of the device slave number.

The possible values are between 1 and 98.

Immediate server function

In the configuration screen, after selecting the TSX SCP 114 interface and the slavefunction, "immediate server" can be selected. In this case the Modbus slave channelis configured to route UNI-TE requests to the SERVER function and not to the mainserver of the processor. For this mode, the SERVER function must be programmed inPL7 as described in part A of this manual.


Multidrop Selection of multidrop communication (current loop).

Point-to-point Selection of point-to-point communication (current loop).

___________________________________________________________________________E1/6

E


Transmission speedSpecifies the speed of transmission of data on the line. The speedsavailable are : 1200, 2400, 4800, 9600 and 19200 bits/s. 300 and 600bits/s can be accessed using the TSX SCP 111 PCMCIA card.

Delay between charactersThis is the end of frame detection delay and the maximum timeseparating two characters during reception. It is used when the PLCis receiving messages, either as master or slave.

The default values can be used in configurations without modems orintermediate devices. In other cases, higher values may be necessary.The default value depends on the transmission speed selected.

Data RTU mode : A silence time which is longer than this delay betweencharacters determines the end of frame. The integrity of the frame isthen checked using the checksum contained within it.ASCII mode : The end of frame is detected when either of thefollowing events occurs :- CR and LF characters received (carriage return and line break)- silence longer than the delay between charactersCaution : In ASCII mode, the value 10000 corresponds to an infinitedelay between characters.


___________________________________________________________________________E1/7

E

Stop This field specifies the number of stop bits used. The possible valuesare 1 or 2 stop bits.

Parity This field is used to define the optional addition of a parity bit and itstype. The possible values are : Odd, Even or None.


Before each transmission of a character string, the module activatesthe RTS signal and waits for activation of the CTS signal.

The time delay (expressed in hundredths of a millisecond) is selectedusing the scroll arrows and sets the maximum waiting period. If thiswaiting period expires, the request is not sent on the bus.Value 0 specifies the absence of management of the delay betweenthese two signals.Enabling the data carrier (DCD signal) is useful where the TSX SCP111 PCMCIA card is used with a modem with a controlled datacarrier. If this option is enabled, only characters can be received andonly if the data carrier signal (DCD) is enabled. If nothing is selected,all the characters received are taken into account. In other instancesof using the TSX SCP 111 PCMCIA card, this option is inoperative.

___________________________________________________________________________E1/8

E

1.2-3 Modbus connection on the terminal port

On TSX Micro PLCs, a Modbus link can be connected via the terminal port.

This connection is only possible if the channel is declared as a slave. A slave numbermust then be declared. The characteristics of the link to be configured are those of aModbus link as described previously.


___________________________________________________________________________E1/9

E

1.3 Debug mode

1.3-1 Description of the master debug screen


The part which is specific to the parameters for debugging a character mode link is madeup of three windows.

Type window

This window indicates the type of Modbus function configured (master).

Counters window

This window displays the various counters (master configuration) of the PCMCIA cardand of the integrated link of the SCY 21600 / 21601 module.

Reset counters : resets the counters to zero.

___________________________________________________________________________E1/10

E

Channel test window

This window is used to test a communication channel via the transmission of a requestto one of the stations present on the bus. The station is chosen by selecting its addressfrom the Slave window.

Identification Sends the Identification request to the designated station. The replyto this request is given in the Receive Response window.

Screen example :

Enter Request Sends a request, other than those supplied by the control buttons, tothe designated station. The choice of this function gives access to ascreen for selecting parameters specific to the request (the requestcode must be coded in hexadecimal format). Details of coding arequest are given in the Modbus reference manual, TSX DG MDB.


___________________________________________________________________________E1/11

E

1.3-2 Description of the slave debug screen


Type window

This window indicates the type of Modbus function configured (slave).

Counters window

This window displays the various counters (slave configuration) of the PCMCIA cardand of the integrated link of the SCY 21600 / 21601 module.Reset counters : resets the counters to zero.

___________________________________________________________________________E1/12

E

Counter : Slave Busy or LOMSlave busy : this counter is incremented by the slave when it receives a request fromthe master when it is already processing another request. This case arises when themaster sends a broadcast request. It does not wait for a response from the slave andcan send another request of this type.

Slave LOM (Listen Only Mode) : a slave in this operating mode can only listen to trafficon the network. It will not respond to frames sent by the master. This counter indicatesthe number of frames received by the slave.


___________________________________________________________________________E1/13

E


The various language objects associated with Modbus communication are describedin the tables below. They are in addition to the language objects which are commonto all the communication modules presented in part A.

Language interface for a Modbus master function


%IWm.v.0 Input signals Byte 0 : Common signalsx0 = 1 : DCD signalx1 = 1 : RI signalx2 = 1 : CTS signalx3 = 1 : DSR

%MWm.v.2 Standard channel status See part A of this manual

%MWm.v.3 Specific channel status Byte 0 = 16#06 for the Modbus master function

%MWm.v.4 Error counter Number of responses received without CRC error

%MWm.v.5 Error counter Number of messages received with CRC error

%MWm.v.6 Error counter Number of responses received withexception code

%MWm.v.7 Error counter Number of master messages sent withoutresponse

%MWm.v.8 Error counter Number of broadcast transmissions

%MWm.v.9 Error counter Number of NACK receptions

%MWm.v.10 Error counter Number of repeated master messages

%MWm.v.11 Error counter Number of character errors

___________________________________________________________________________E1/14

E


%MWm.v.15 Control Byte 0 :x0 = 1 : Reset counterByte 1 :x0 = 1 : DTR ON signalx1 = 1 : DTR OFF signalx6 = 1 : Change from Modbus to character

mode (modem)x7 = 1 : Change from character mode

(modem) to Modbus

%KWm.v.0 Type Byte 0 = 16#06 for the Modbus master function

%KWm.v.1 Speed / Format Byte 0 : Speed128 = 300 bits/s, 129 = 600 bits/s only for :TSX SCP 111,00 = 1200 bits/s, ... ..., 04 = 19200 bits/sByte 1 : Formatx0 : No of bits : 1 = 8 bits, 0 = 7 bitsx1 = 1 : Parity managementx2 : Parity type : 1 = odd, 0 = evenx3 : Stop bit : 1 = 1 bit, 0 = 2 bits

%KWm.v.2 Delay between characters Value in ms from 2 to 10 000 ms

%KWm.v.3 Wait time Wait time in ms from 10 to 10 000 ms

%KWm.v.4 Repetition and Byte 0 : Number of retries (3 by default)signal management Byte 1 :

x0 = 1 if PSR signal management (TSX SCP 112)x0 = 2 if data carrier management (TSX SCP 111)

%KWm.v.5 RTS/CTS delay Delay value in hundredths of ms (defaultvalue 100 ms)


___________________________________________________________________________E1/15

E

Language interface for a Modbus slave function

The language interface is identical to that for the Modbus master function. Only thoseobjects defined below are different.


%IWm.v.0 Input signals Byte 1 : Specific datax0 = 1 : listen only mode

%MWm.v.3 Specific channel status Byte 0 = 16#07 for the Modbus slave function

%MWm.v.7 Error counters Number of messages for the processor

%MWm.v.8 Error counters Number of broadcast receptions

%MWm.v.10 Error counters No. of messages received in Slave Busy or LOM

%KWm.v.0 Type Byte 0 = 16#07 Modbus slave functionByte 1 : (*)x1 = 1 immediate server selectedx1 = 0 immediate server not selected

%KWm.v.3 Slave addresses Byte 0 : Slave number (0 to 98)

(*) Only concerns the language interface for TSX SCP 114 PCMCIA cards configuredas Modbus slave.

___________________________________________________________________________E1/16

E


1.5-1 Modbus master function

This section describes the services available on a TSX 37 or TSX 57 Modbus link masterstation. Details on coding the various Modbus functions are given in the Modbusreference manual, TSX DG MDB.

Data exchanges

The following requests are addressed to the slave device which is to read and writethe variables.

These requests use the READ-VAR and WRITE-VAR communication functions. Referto part A of this document for details on their coding.

Modbus Request Code and sub-function Communication function

Read bits 16#01 READ_VAR

Read words 16#03 READ_VAR

Write bits 16#05 and 16#0F WRITE_VAR

Write words 16#06 and 16#10 WRITE_VAR

Read input bits 16#02 SEND_REQ

Read input words 16#04 SEND_REQ

Example : read word 4 in Modbus slave 3.

READ_VAR (ADR#0.1.3, '%MW'',4,1,%MW100:1,%MW200:4)

The write services can be broadcast, in which case no response is sent back to thesender. It is therefore recommended that a time-out is configured to acknowledge theactivity bit of the function.

Diagnostics and maintenance

The diagnostics and maintenance data for Modbus slaves use the SEND_REQcommunication function. Refer to part A of this document for details on their coding.

Modbus Request Code and sub-function Communication function

Exception status 16#07 SEND_REQ

Diagnostics 16#08/16#xx SEND_REQ

Event counter 16#0B SEND_REQ

Event connection 16#0C SEND_REQ

Slave identification 16#11 SEND_REQ


___________________________________________________________________________E1/17

E

1.5-2 Using the SEND_REQ communication function

The UNI-TE Action-object request (request code 16#9F) is used to transmit all Modbusfunctions.

The transmission buffer must contain the following information :

• First word : Byte 0 function codeByte 1 sub-function code

• Second word : Identification of the Modbus function, always 16#0296

• Third word : = 0 reserved

• Fourth word : Modbus function parameters

• Fifth word : Modbus function parameters

• n th word : Modbus function parameters.

Example :

SEND_REQ(ADR#0.1.x,16#9F,%MW10:10,%MW50:30,%MW100:4)

Before sending the function, the following must be initialized :the first word with : function code, sub-function code

MW10 := 16#0008 Echo

the next three words specify the MODBUS function

%MW11 := 16#0296 Identification of the Modbus function%MW12 := 0 Reserved%MW13 := 16#1234 Echo function parameter

The length of data to be sent must also be initialized :

%MW103 := 8

Response structure :The first word (%MW50) in the reception buffer contains a report :- First word = 0 if action performed- First word = 1 if action not performedThe second word contains the request parameters :If action not performed,- Second word = 16#0007 request parameters incorrector Second word = 16#0004 question parameters incorrector Second word = byte 0 = 0x80 + function code

byte 1 = Modbus error code = 6 if slave occupied= 1 if function unknown= 3 if data invalid

If action performed :- Second word = byte 0 : function code byte 1: sub-function code- Third word to nth word : Modbus response data

___________________________________________________________________________E1/18

E

1.5-3 Modbus slave function

Data exchanges

The slave module manages the Modbus requests listed in the table below :

Description Function code PLC object

Read n output bits 16#01 % M

Read n input bits 16#02 % M

Read n output words 16#03 %MW

Read n input words 16#04 %MW

Write one output bit 16#05 % M

Write one output word 16#06 %MW

Write n output bits 16#0F % M

Write n output words 16#10 %MW

Diagnostics and maintenance

Diagnostics and maintenance data, which can be accessed via the Modbus link, areindicated below :

Description Code and sub-function

Read exception status 16#07

Echo 16#08/16#00

Module initialization 16#08/16#01

Read the PLC diagnostic registers 16#08/16#02

Change of end of frame delimiter (ASCII mode) 16#08/16#03

Change to listen mode 16#08/16#04

Counter reset 16#08/16#0A

Number of messages received without CRC error 16#08/16#0B

Number of frames received with CRC error 16#08/16#0C

Number of exception responses 16#08/16#0D

Number of messages addressed to the PLC 16#08/16#0E

Number of broadcast messages received 16#08/16#0F

Number of correct responses 16#08/16#10

Number of messages received in listen mode 16#08/16#11

Number of incorrect characters received 16#08/16#12

Read event counter 16#0B

Read event connection 16#0C

Read identification 16#11


___________________________________________________________________________E1/19

E

1.6 Operating modes of the Modbus PCMCIA card and the integratedlink of the SCY 21600 / 21601 module

General overview



• If there is a PL7 application in the PLC, the application configuration is transmittedto the module which then starts.


Module configured

Module stop


Reset

ConfigurationModule notconfigured

Self-tests OK

Module in self-testphase

Power-upModule powered off

___________________________________________________________________________E1/20

E

1.7 Compatibility between a TSX 37/57 and a Series 1000 PLC

1.7-1 Using the READ_VAR and WRITE_VAR functions

The :Read_varWrite_var

functions are used to read objects contained in Series 1000 PLCs. These are words,double words, floating point objects, character strings, etc.The object address determines the object type.

The Read_var and Write_var functions are used to read/write %MW words from %MW0to %MW65737.Example of configuring a 5000 PLC fitted with a standard CPU5130 card :

- words :first %MW %MW0last %MW %MW24999

first %MD %MD25000last %MD %MD26998

first %FD %FD27000last %FD %FD28998

'

- bits :first %MX %MX0last %MX %MX4095

Warning : an offset must be used on the address to be read/written. Bits %MX0 toMX4095 can be accessed via addresses A000 and AFFF on JBUS.

TSX 37/57 communication functions cannot be used to exchange double words orcharacter strings via the Modbus protocol. If required, the transfer can be made usingthe %MW form, the application will be responsible for the word storage direction.

The diagnostic functions can be accessed via the Send_req function.

When using a master Series 1000 PLC, only the BFC READ and BFC WRITE functionscan be used to read/write :

- %MW words from %MW0 to %MW65737- %MX bits

An example of compatibility between a S1000 PLC and a TSX 37 is given in theMODBUS reference manual.


___________________________________________________________________________E1/21

E

1.8 Performance

1.8-1 Typical exchange times in Modbus

Average execution time for the READ_VAR function in ms :

Number of objects read : 1 word

Speed in bits/s Cycle time in ms Average time Average timeTSX SCP 114 TSX SCY2160i

4800 cycl ic 105 1204800 10 133 1404800 50 152 1729600 cycl ic 74 909600 10 86 1109600 50 149 172

19200 cycl ic 57 7519200 10 60 9019200 50 100 118


Speed in bits/s Cycle time in ms Average time Average timeTSX SCP 114 TSX SCY2160i

4800 cycl ic 616 6304800 10 637 6504800 50 700 7309600 cycl ic 357 3759600 10 367 3909600 50 405 425

19200 cycl ic 215 22819200 10 216 23919200 50 251 280

1.8-2 Limitations of communication via Modbus

The Modbus master TSX SCP 114 PCMCIA card and the integrated link of theSCY 21600 / 21601 module permit processing of :

8 Modbus transactions simultaneously.

The maximum size of the messages is 240 bytes.

The READ_VAR function can read up to 1000 consecutive bits in a remote device,whatever the device and protocol used (UNI-TELWAY or Modbus/Jbus).To read more than 1000 bits it is necessary to use the SEND_REQ function. Note thatTSX 07, TSX 37, TSX 57 PLCs are unable to send more than 1000 bits following a readrequest.

___________________________________________________________________________E1/22

E

___________________________________________________________________________1

Communication via modem Contents

Section Page

F

1 Communication via modem 1/1

1.1 Presentation 1/11.1-1 Introduction 1/11.1-2 Typical configurations 1/11.1-3 Principle 1/31.1-4 Setup 1/41.1-5 Functions and limits 1/6

1.2 Configuration mode 1/81.2-1 Main screen : UNI-TELWAY mode 1/81.2-2 Modem parameters 1/101.2-3 Configuration screen : character mode 1/12

1.3 Debug mode 1/13

1.4 Language interface 1/151.4-1 PL7 language objects 1/151.4-2 Modem language objects 1/16

1.5 CALL_MODEM communication function 1/201.5-1 General information 1/201.5-2 Syntax 1/201.5-3 Communication / transaction report 1/231.5-4 Example of communication between two PLCs 1/25

1.6 Guide to choosing the operating parameters 1/271.6-1 In UNI-TELWAY mode 1/271.6-2 In character mode 1/29

1.7 Appendix 1/301.7-1 Coding exchanges 1/301.7-2 AT commands 1/31

___________________________________________________________________________

2

Communication via modem Contents

Section Page

F

Communication via modem 1

___________________________________________________________________________F1/1

F

1.1 Presentation

1.1-1 Introduction

A large number of applications involve communication via modem. Communicationvia modem can be used for accessing remote stations on the switched telephonenetwork in order to perform remote monitoring, diagnostics or control operations.

This type of communication is available via a Modem PCMCIA card, reference TSXMDM 10. This card can only be installed in the host channel of a :

• TSX Micro processor (with memory card)

• TSX Premium processor

• PC (with a type 3 PCMCIA card slot).

Processors must have at least 25 Kb of free program memory space to use theCALL_MODEM communication function.

1.1-2 Typical configurations

Standard configuration

The following diagram represents the standard configuration for using communicationvia modem, together with the various services.

Section 11 Communication via modem

ProgrammingDebuggingCommands

Switched telephonenetwork

Sending backalarms and

measurements

Remote station 1 Remote station n

TelephoneFax

Exchange of variablesCommands

Alarms and measurements

Programming terminal

Pocketreceiver

___________________________________________________________________________F1/2

F

Other configurations

Remote stations on the switched telephone network can be called from a network ora bus if one of the stations has a modem connection.

The following diagram shows a configuration using modem communication with aFIPWAY network via a station.

External CALL_MODEM communication functionThe function is transmitted by a station on the network.

Local CALL_MODEM communication functionThe function is transmitted by the station supporting the TSX MDM 10 card.

ProgrammingDebugging

Remote control


Remote station 1 Remote station n



Programming terminal



Intermediatestation

Station 1.1 Station 1.n

FIPWAY 1 network

Station 1.3

Calling station

Calledstation

Ext

erna

l CA

LL_M

OD

EM

com

mun

icat

ion

func

tion


___________________________________________________________________________F1/3

F

1.1-3 Principle

When they are idle, all modems are by default waiting for a possible connectionrequest.

Station A transmits a call request to number X of station B using AT commands (viathe CALL_MODEM communication function for PLCs).

A process of exchanges between the modems results in establishing the line, in pointto point mode, between station A and station B. The connection is made subject toacceptance of a password, if this method is used.

Stations A and B then communicate according to the protocol chosen when the callis made (UNI-TELWAY or character mode). The stations communicate via thestandard communication functions. Either of the stations can initiate the exchange.

Only one communication function can be active at a time using the TSX MDM 10 card.

By default in UNI-TELWAY mode, the calling station is the slave and the called stationis the master. To ensure compatibility with existing applications, it is possible to setthe parameters of the CALL_MODEM communication function so that the local stationremains in UNI-TELWAY master mode.

Station A sends a release request to its local modem which releases the line : this isthe disconnection phase.

Stations A and B return to their initial state and may initiate another call.


Station Acalling station

initiates the call (sender)

Station Bcalled station

(receiver)

___________________________________________________________________________F1/4

F

1.1-4 Setup

The functions supported by the TSX MDM 10 card enable the most frequentlyencountered types of use to be handled immediately, with no prior configuration.

The most frequently encountered types of operation are :

• Communication between PLCs equipped with a TSX MDM 10 modem card

• Communication from PL7 software to a PLC equipped with a TSX MDM 10 modemcard

The setup comprises :

• Simple declaration of the module in the PLC configuration : This is adequate to ensurethat the modem link is established in the event of an incoming call.

• Making a call : The telephone number of the remote station must be entered in theCALL_MODEM communication function.

• Communication : This is normally performed in the same way as on a UNI-TELWAYbus with a standard local link.

UNI-TELWAY communication between PLCs via the TSX MDM 10 card

Calling station : Called station :PLC with TSX MDM 10 card PLC with TSX MDM 10 card

1 Default declaration of the 1 Default declaration of theTSX MDM 10 card : TSX MDM 10 card :- UNI-TELWAY protocol - UNI-TELWAY protocol- transmission speed of 9600 Bits/s - transmission speed of 9600 Bits/s- automatic switching to slave - automatic switching to master

mode on addresses 1 and 2 mode to scan addresses 1 and 2- no password management - no password management

2 Confirmation of the configuration 2 Confirmation of the configuration

3 Programming the CALL_MODEMfunction for calling the remote station :- address : ADR# 0.1.SYS- command : 1- telephone number (%MBx:y)- connection option : 0- slave mode : 0- report : %MWx:4

Remotestation 1

Remotestation 2

Switchedtelephone network


___________________________________________________________________________F1/5

F

Communication from PL7

Calling station : Called station :PC with PL7 software PLC with TSX MDM 10 card

1 The UNI-TELWAY driver provided must 1 Default declaration of thebe in slave mode with addresses 1 and 2, TSX MDM 10 card :a transmission speed of 9600 Bits/s and - UNI-TELWAY protocolthe modem option must be selected - transmission speed of 9600 Bits/s

- automatic switching to mastermode to scan addresses 1 and 2

- no password management

2 Confirmation of the configuration

When the PL7 application is launched in online mode, the external modemautomatically dials the telephone number of the remote station, establishes theconnection then responds to prompting.Operation is then identical to that for PL7 connected directly to the terminal port. Allfunctions are available, except for loading applications.

Switchedtelephone network

PC with PL7

Externalmodem

Remotestation

___________________________________________________________________________F1/6

F

1.1-5 Functions and limits

Hardware

The TSX MDM 10 card can only be installed in the PCMCIA host channel of one of thefollowing processors from version V3.3 onwards :• TSX Micro

• TSX Premium

The card can also be installed in a PC which has a type 3 PCMCIA card slot.

The use of a PCMCIA memory card is recommended for certain types of processor(since the CALL_MODEM communication function takes up 25 Kb of program memoryspace).

The TSX MDM 10 communication card can only be connected to the STN (SwitchedTelephone Network). It cannot be connected to :• direct lines

• ISDN (Integrated Services Digital Network)

• GSM (Global System for Mobile communications) networks

Compatibility with third-party modems is ensured for modems intended for the switchedtelephone network connected on COM 1.

The TSX MDM 10 card supports two character formats : 10 or 11 bits. However, whenit is configured for 11 bits, the parity bit is not transmitted on the telephone network, butregenerated by the card.For 11-bit communication between modems, compatibility is thus ensured for modemsintended for the telephone network on COM1.With third-party modems, 11-bit communication may cause the TSX MDM 10 card tomalfunction.

In character mode, the TSX MDM 10 card can be used for :

• transmission of data coded on 7 or 8 bits

• reception of data coded on 8 bits

In UNI-TELWAY protocol, the modem card is not compatible with data compression anderror correction protocols on third-party modems.


___________________________________________________________________________F1/7

F

Software

The modem card provides X-WAY transparency and allows two types of protocol :• UNI-TELWAY master or slave protocol

• character mode protocol

The card may call a remote modem (corresponds to calling mode) or be called(corresponds to called mode).

The transmission speed varies between 1200 bits/s and 9600 bits/s, and the total sizeof the frames transmitted is 256 bytes.

Only one communication function can be active at a time using the TSX MDM 10 card.

The called station can only recognize up to 8 calling stations when the password serviceis used. Password management is only provided by the TSX MDM 10 card. For third-party devices, password management is performed according to the protocol given inthe appendix - Coding password exchanges.

PL7 software (version V3.3 onwards) is required to configure the modem.

The modem card does not allow uploading or downloading of PL7 applications.

___________________________________________________________________________F1/8

F


Operation of the modem card is based on the possible use of two protocols (UNI-TELWAY or character mode).The choice of protocol is determined by the parameters of the CALL_MODEM function.

Preliminary operations for accessing the configuration screen1 Change to offline mode to configure the TSX MDM 10 card.2 Open the hardware configuration (can be accessed via the Application Browser)

and open the communication channel.3 Select channel 1 and the TSX MDM 10 card.

1.2-1 Main screen : UNI-TELWAY mode

The UNI-TELWAY protocol is offered by default and the following configuration screenappears :


___________________________________________________________________________F1/9

F

The configuration screen displays :

• a Modem button for configuring :- the password management service- the dialing mode (tone or pulse)- the call parameters- the connection parameters

• a ASCII button for selecting character mode protocol if the PL7 application uses thisprotocol

• a Server address (AD0) field :- used for entering the base address used in UNI-TELWAY slave mode.

• a Number of addresses field (default value : 2) :- used for entering the number of addresses used in UNI-TELWAY mode- If the station is the caller, it is recommended that the value 2 is entered in this field.

• a Transmission speed field :- possible values 1200 Bits/s, 2400 Bits/s, 4800 Bits/s, 9600 Bits/s- Adjust the transmission speed according to the remote devices.

• a Waiting time (ms) field (default value : 1 s) :- maximum waiting time for the connection acknowledgment message from the

remote device (not to be confused with the application program response toREAD_VAR, for example)

- Adjust the transmission time according to the transmission speed. Increase the timefor long distance calls (for example, intercontinental calls) or when there is a poorquality telephone connection.

• a Data field :- This field cannot be modified; the UNI-TELWAY protocol requires the use of 8 data

bits per character.

• a Stop field (default : 1 bit) :- Adjust according to the remote device (generally, 1 Stop bit with the UNI-TELWAY

protocol).

• a Parity field (default : odd) :- Adjust according to the remote device (generally, odd with the UNI-TELWAY

protocol).

___________________________________________________________________________F1/10

F

1.2-2 Modem parameters

The configuration screen appears by selecting the Modem button :

For the called station, the modem configuration consists of :

• Password verification :- Check the box if password management by the called station is required. The

default setting is password test disabled. It is possible to suppress this option bydeselecting the box.

• List of passwords :- If password management is used, each called station has a list of up to 8

passwords for a TSX Micro and 16 passwords for a TSX Premium, enabling 8 or16 separate devices to be identified (only authorizes connection to these devices).

- A password should not exceed 8 characters (upper or lower case letters, numbersor special characters).


___________________________________________________________________________F1/11

F

For the calling station, the modem configuration consists of :

• Passwords :- Each station has its own password. This is used to identify the station. When

connection is requested, the calling station sends its password so that the calledstation can identify it and authorize the connection.

- For communication with other devices, the exchange protocol described in theappendix (Coding password exchanges) must be supported by the remote device.

• Call parameters :- Dialing time : duration of a call in seconds (default : 60 seconds).- Interval between calls : in seconds, the time the calling station waits between two

connection attempts. If a connection attempt fails, the PLC starts to call again afterthis interval if the number of retries has not been exceeded.

- Number of retries (default : 3 retries) : This is used to define the number of callretries in the event of unsuccessful connection attempts. If the last call fails, theCALL_MODEM function, which initiated the connection attempts, sends back anerror report. If the number of configured retries is 0, no retry will be attempted.

• Type of dialing :- tone- pulse

• Maximum connection time (default : 0 seconds) :- defines the connection time in seconds. After this time, the current connection will

be stopped. This time-out is necessary if the sender station is unable to disconnectthe line following an error caused by the application changing to STOP mode ora system error.

- If the configured connection time is 0, no time-out is initiated.

• Maximum time between two frames (default : 0 seconds) :- in seconds. If the time between two frames is longer than this maximum time, the

connection is broken. This time-out is necessary if there is a connection which isnot used.

- If the configured value is 0 or greater than 360 seconds, communication will bebroken at the end of the 360 seconds.

___________________________________________________________________________F1/12

F

1.2-3 Configuration screen : character mode

The character mode configuration screen appears by selecting the ASCII button :

The configuration screen displays :

• a Transmission speed field (default : 9600 Bits/s) :- possible values 1200 Bits/s, 2400 Bits/s, 4800 Bits/s, 9600 Bits/s- Adjust the transmission speed according to the remote devices.

• a Data field (default : 7 bits) :- number of data bits per character- Adjust the number of bits according to the remote devices.

• a Stop field (default : 1 bit) :- number of stop bits per character- Adjust the number of bits according to the remote devices.

• a Parity field (default : odd) :- number and type of parity bits per character- Adjust according to the remote devices.

• a Stop on reception field (default : CR) :The stop on reception can be performed by detecting :- the carriage return at the end of the frame- the line feed at the end of the frame- a configured hexadecimal value at the end of the frame


___________________________________________________________________________F1/13

F

1.3 Debug mode

Description of the debug screen :

Debug mode is accessed from the configuration screen, in online mode only, byselecting Debug in the dialog box.

This screen shows the current status of the modem, and can only be accessed in readmode.

List of data which is diagnosed :

• Communication mode :- Command : connection request in progress (establishment of the connection)- Transparent : connection established

• Dial command :- indicates whether a CALL_MODEM function has been received by the TSX MDM

10 card and is being processed

• Mode :- indicates the mode of the TSX MDM 10 card (calling or called)- in calling mode, the screen indicates whether the CALL_MODEM function has been

sent by the local station or by a station via a network

• Number of retries :- indicates the remaining number of retries

• Time between retries :- indicates the remaining time between retries

___________________________________________________________________________F1/14

F

• Dialing time remaining :- indicates the remaining dialing time

• Connection time remaining :- indicates the remaining connection time (if the local station is connected)

• Causes of disconnection :- "CALL_MODEM" EF : the line has been disconnected by the local station using the

CALL_MODEM function- Protocol error : a protocol error has caused the disconnection- Modem (CD) : the line has been disconnected by the remote modem- Connection time exceeded : the connection period has been exceeded- Interval between 2 frames exceeded : the interval between 2 frames has been

exceeded- Password error : the password which has been received is invalid (does not appear

in the list of the local station)


___________________________________________________________________________F1/15

F


1.4-1 PL7 language objects

The language objects of the communication functions define all the data which may beobserved or modified by the application.The table below lists the language objects which are common to all communicationmodules.


%Im.MOD.ERR I Module fault Bit active when the modem cannot establishthe connection

%MWm.MOD.0 E Current exchanges x0 = 1 read current statusx1 = 1 send control parametersx2 = 1 send adjustment parameters

%MWm.MOD.1 E Report x1 = 1 control parameters received by the modulex2 = 1 adjustment parameters received by themodule

%MWm.MOD.2 E Module status x0 = 1 module faultyx1 = 1 operating fault (communicationfault between the processor and themodule, configuration, control oradjustment data not accepted, etc)x2 = 1 terminal block fault (not connected)x3 = 1 self-test phase in progressx4 = 1 reservedx5 = 1 hardware or software configurationfault (the existing module is different fromthe module declared at configuration)x6 = 1 no module presentx7 = 1 sub-module fault

I : Implicit exchange (updated automatically at the start of the task)E : Explicit exchange (updated after execution of a user request)

___________________________________________________________________________F1/16

F

1.4-2 Modem language objects

The following table describes the constants which are required for the modem cardconfiguration.

m is 0 or 1 depending on which slot the processor occupies in the rack.


%KWm.1.0 Type 0 for UNI-TELWAY mode

%KWm.1.1 Speed / Format byte 0 : speed00 = 1200 bits/s, ..., 03 = 9600 bits/sbyte 1 : formatx0 number of bits (x0 = 1 : 8 bits, x0 = 0 : 7 bits)x1 = 1 parity managementx2 type of parity (x2 = 1 : even, x2 = 0 : odd)x3 stop bit (x3 = 1 : 1 bit, x3 = 0 : 2 bits)

%KWm.1.2 Waiting time value of the time-out

%KWm.1.3 Slave addresses byte 0 : slave base addressbyte 1 : number of consecutive addresses (1 to 3)

%KWm.1.4 Not used

%KWm.1.5 RTS / CTS delay delay value in hundredths of a millisecond

%KWm.1.6 Speed / Format byte 0 : speed in ASCII modein ASCII mode 00 = 1200 bits/s, ..., 03 = 9600 bits/s

byte 1 : format in ASCII modex0 number of bits (x0 = 1 : 8 bits, x0 = 0 : 7 bits)x1 = 1 parity managementx2 : type of parity (x1 = 1 : even, x1 = 0 : odd)x3 : stop bit (x3 = 1: 1 bit, x3 = 0 : 2 bits)

%KWm.1.7 Stop bits received byte 0 :x0 = 1 : end character enabledx1 = 1 : end character includedbyte 1 : value of the end of frame character

%KWm.1.8 Not used

%KWm.1.9 Number of retries value between 0 and 10 retries

%KWm.1.10 Interval between byte 0 : interval between retries in seconds, valueretries between 30 and 180 seconds in increments of 30 s

%KWm.1.11 Dialing mode byte 0 : type of dialingx0 = 0 : tonex0 = 1 : pulsex1 = 0 : password testx1 = 1 : no password testbyte 1 : dialing time, value between 30 and 180seconds in increments of 30 s


___________________________________________________________________________F1/17

F


%KWm.1.12 Maximum time message transfer time-out, value in secondsbetween 2 messages between 0 and 32767 seconds

%KWm.1.13 Maximum value between 0 and 32767 secondsconnection time = 0 : no connection time time-out

> 0 : connection time time-out

%KWm.1.14-17 Passwords station password, 8 characters maximum

Modem constants for TSX Micro PLCs

%KWm.1.18-49 List of words list of 8 passwords, 8 characters max. foreach password

%KWm.1.50-123Modem string string of 148 bytes

Modem constants for TSX Premium PLCs

%KWm.1.18-81 List of words list of 16 passwords, 8 characters max. foreach password

%KWm.1.82-155Modem string string of 148 bytes

The following table describes the language objects which are required for thecommunication protocols for the modem card.

m is 0 or 1 depending on which slot the processor occupies in the rack.


%IWm.1.0 Not used

%IWm.1.1 General slave x0 = 1 if at least one of the slaves is not respondingstatus

%MWm.1.3 Specific channel 0 for UNI-TELWAY master modestatus

%MWm.1.4 Not used

%MWm.1.5 Not used

%MWm.1.6 Not used

%MWm.1.7 Not used

%MWm.1.8 Slave address Base address of the calling slave

___________________________________________________________________________F1/18

F


%MWm.1.12 Modem status byte 0x0 = 1 : command mode (establishment of the connection)x0 = 1 : transparent mode (connection established)x1 = 0 : calling mode (sender station)x1 = 1 : called mode (receiver station)x2 = 1 : connection requestx3 = 1 : dialing requestx4 = 1 : disconnection requestx5 = 1 : connection via a local CALL_MODEM functionx6 = 1 : connection via an external CALL_MODEM functionx7 = 1 : connection via a remote modembyte 1x0 = 1 : disconnection via a local CALL_MODEM functionx1 = 1 : disconnection via an external

CALL_MODEM functionx2 = 1 : disconnection due to a time-outx3 = 1 : disconnection due to a protocol errorx4 = 1 : disconnection via a remote modemx5 = 1 : disconnection due to a password errorx6 = 1 : disconnection due to the configured

time-out being exceededx7 = 1 : modem error

%MWm.1.13-16 Current password password for sender (calling) station

%MWm.1.17 Modem status byte 0x0 = 1 : initialization of card activex1 = 1 : command mode activex2 = 1 : transparent mode activex3 = 1 : dialing in progressx4 = 1 : disconnection in progressx5 = 1 : call in progressx6 = 1 : busybyte 1x4 = 1 : card initialization errorx5 = 1 : card initialization request

%MWm.1.18 Dialing byte 0status x0 = 1 : dialing in progress

x1 = 1 : sending AT D (dialing) commandx2 = 1 : connection receivedx3 = 1 : password test in progressx4 = 1 : valid password receivedx5 = 1 : protocol mode can be launchedx6 not usedx7 = 1 : Carriage Return not detectedbyte 1x0 = 1 : no DCD signalx1 = 1 : dialing time exceededx2 = 1 : general I/O errorx3 = 1 : illegal commandx4 = 1 : disconnection during dialing


___________________________________________________________________________F1/19

F


%MWm.1.19 Caller status byte 0x0 = 1 : call in progressx1 = 1 : sending AT A (answer) commandx2 = 1 : connection receivedx3 = 1 : password test in progressx4 = 1 : password receivedx5 = 1 : password not receivedx6 = 1 : Carriage Return not detectedbyte 1x2 = 1 : general I/O errorx3 = 1 : illegal command

%MWm.1.20 Connection byte 0status x0 = 1 : DTR signal active

x1 = 1 : sending AT H (hang-up) commandx2 = 1 : awaiting disconnectionbyte 1 : not used

%MWm.1.21-32 Telephone Telephone number of the called stationnumber

%MWm.1.33 Remaining number number of calls remaining to be madeof retries

%MWm.1.34 Remaining interval remaining interval between calls, value betweenbetween calls 0 and 255 (between 30 s and 180 s)

%MWm.1.35 Remaining dialing remaining dialing time, value between 40 andtime 255 seconds

%MWm.1.36 Remaining time remaining time between two framesbetween 2 messages

%MWm.1.37 Remaining display of the remaining connection timeconnection time

%MWm.1.38 Track of input offset of the last character, between 0 and 99characters bytes

%MWm.1.39-88 Track of input continuous track of last 100 characterscharacters

%MWm.1.89 Track of output offset of the last character, between 0 and 99characters bytes

%MWm.1.90-139 Track of output continuous track of last 100 characterscharacters

___________________________________________________________________________F1/20

F

1.5 CALL_MODEM communication function

1.5-1 General information

The CALL_MODEM communication function manages the connection of the TSXMDM 10 card.

It can be used to :

• connect a line between the TSX MDM 10 card and another TSX MDM 10 card, or aremote third-party modem

• disconnect a line once it has been established or while it is being established

• reinitialize the TSX MDM 10 card if necessary (for example following a protocol error)

• send AT commands

1.5-2 Syntax

The syntax of the CALL_MODEM communication function is as shown below :

CALL_MODEM (ADR#0.1.SYS, 1, %MB100:20, 0, 0, %MW256:4)

Modem address :. processor position : 0or 1. PCMCIA channel : 1. system server : SYS

Command Connectionoptions

Choice of UNI-TELWAYmaster orslave mode

Activity bitand lengthreport

. Telephonenumberof the stationbeing calledor. AT commandto be sent

Managementparameters

Specificparameters


___________________________________________________________________________F1/21

F

!

Description of the specific parameters

Parameter Type Meaning

Command word value = 1 : connection commandvalue = 2 : disconnection commandvalue = 3 : modem reinitialization commandvalue = 4 : AT command to be sent

Telephone number Byte telephone number of the called station or AT commandor table to be sent. Its size (24 bytes maximum) is givenAT command by the last management parameter (%MWk+3). If

%MWk+3 = 0, the size is 24 bytes.

Options word connection optionvalue = 0 : connection in UNI-TELWAY mode with passwordvalue = 1 : connection in ASCII mode with passwordvalue = 2 : connection in UNI-TELWAY mode without passwordvalue = 3 : connection in ASCII mode without passwordvalue = 4 : connection in UNI-TELWAY mode without

sending any character string on the line atthe connection request

value = 5 : connection in ASCII mode without sending anycharacter string on the line at the connection request

Mode word select UNI-TELWAY master or UNI-TELWAY slavemode for the calling stationvalue = 0 : connection in UNI-TELWAY slave modevalue = xx : connection in UNI-TELWAY master mode• byte 0 (low order) corresponds to the number of slave

addresses,value = 1 for Ad0,value = 2 for Ad0 and Ad1• byte 1 (high order) address Ad0 of the UNI-TELWAY

slave (1 to 98)

The data size of the telephone number or AT command is given in bytes.

Description of the management parameters

These parameters are the same as for all other communication functions.They are structured in the following way :

Words Byte 1 Byte 2

%MWk number of exchanges x0 : activity bit*

%MWk+1 transaction report communication report

%MWk+2 Time-out for the function

%MWk+3 Length of the telephone number to be called

The time-out for the function is the time which allows for the absence of the CALL_MODEMfunction response.

___________________________________________________________________________F1/22

F

This time (increment of a time base of 100 ms) is a combination of the variousparameters configured via the Modem Configuration screen.

It is recommended that the time-out is given the following minimum value :

Min. time-out = Number of retries * dialing time + (number of retries - 1)*interval between calls

Examples of connection and disconnection with a remote station

• Example of connection in UNI-TELWAY slave mode, without password :


• Example of connection in UNI-TELWAY slave mode, with password :


• Example of disconnection :

In this example, the telephone number, UNI-TELWAY slave mode and the passwordare not required. The line will be disconnected.


• Example of reinitializing the modem :

In this example, the telephone number, UNI-TELWAY slave mode and the passwordare not required. The modem will be reinitialized.


Telephonenumberof the stationbeing called

Modem address Connection Without passwordand UNI-TELWAYmode

UNI-TELWAYslave mode

Telephonenumberof the stationbeing called


Modem address Connection With passwordand UNI-TELWAYmode

UNI-TELWAYslave mode


Modem address Disconnection

Modem address Modemreinitialization


___________________________________________________________________________F1/23

F

1.5-3 Communication / transaction report

These messages are common to all types of communication function.

Transaction reports specific to the modem and significant only for the values of thecorresponding communication reports.

Communication report (low order byte)

Value Meaning

16#00 Exchange correct

Transaction report (high order byte)

value / error code Meaning

16#00 Command executed16#01 Request not processed16#02 Invalid response16#03 Current connection via a remote modem16#04 Current connection via a local

CALL_MODEM function16#05 Current connection via an external

CALL_MODEM function16#06 Request for connection via a local

CALL_MODEM function16#07 Request for connection via a external

CALL_MODEM function16#09 Remote station busy16#0A Disconnection via a remote modem16#0B Disconnection due to a protocol error16#0C Disconnection due to a time-out

16#01 Exchange stopped on time-out

16#02 Exchange stopped on user request

16#03 Invalid address format

16#04 Invalid destination address

16#05 Invalid management parameter format

16#06 Invalid specific parameters

16#07 Problem with sending to destination

16#08 Reserved

16#09 Reception buffer too small

16#0A Transmission buffer too small

16#0B No processor system resource

16#0C Invalid exchange number

16#0E Invalid length

___________________________________________________________________________F1/24

F

Communication report (low order byte)

Value Meaning

16#FF Message failed

Transaction report (high order byte)

value / error code Meaning

16#01 No resource to the processor16#02 No line resource16#03 Device missing16#04 Line failure16#05 Length fault16#06 Communication channel faulty16#07 Addressing fault16#08 Application program fault16#0B No system resource16#0C Communication function inactive16#0D Destination missing16#0F Routing problem between stations or

channel not configured16#11 Address format not handled16#12 No destination resource16#14 Connection not operating16#15 No resource on local channel16#16 Access not authorized16#17 Incompatible network configuration

The connection and disconnection of a line or reinitializing the modem must bemanaged by the application and uses the CALL_MODEM communication function.

The disconnection of a line must be managed by the application. Only thesender station has the right to disconnect a line using the CALL_MODEMcommunication function.


___________________________________________________________________________F1/25

F

1.5-4 Example of communication between two PLCs

The following example describes the various phases of communication between twoTSX Micro PLCs connected via a telephone network :

• The connection phase

• The data exchange phase

• The disconnection phase

Connection phase

The calling station makes the call in UNI-TELWAY slave mode without passwordmanagement.


Parameter Variable Description

Address ADR#0.1.SYS Modem addressprocessor slot : 0 or 1PCMCIA channel : 1system server : SYS

Command 1 Connection command

Telephone number %MB50:4 Telephone number of the called station (in bytes)

Option 2 Connection in UNI-TELWAY mode without password

Mode 0 Connection in UNI-TELWAY slave mode

Report %MW1024:4 %MW1026 = 300, corresponds to a time-out of 30 s%MW 1027 = 4, corresponds to the length in bytesof the telephone number to be called (in the example4 bytes)

Data exchange phase

The calling station reads internal words %MW100 to %MW199 of the called station. Thecalled station is considered to be the UNI-TELWAY master.

READ_VAR(ADR#0.1.0, '%MW', 100, 100, %MW200:100, %MW1094:4)


Address ADR#0.1.1 Address of the UNI-TELWAY master station to be scanned

Type of object '%MW' Internal words

No. of the first object 100 Indicates the index of the first internal word to beread (%MW100)

Consecutive numbers 100 Specifies the number of internal words to be read(100 words)

Content of the answer%MW200:100 Word table containing the value of the objects read

Report %MW1094:4

___________________________________________________________________________F1/26

F

Disconnection phase



Address ADR#0.1.SYS Modem addressprocessor slot : 0 or 1PCMCIA channel : 1system server : SYS

Command 2 Disconnection command

Telephone number %MB50:4 Telephone number of the called station (in bytes)

Option 2 Connection in UNI-TELWAY mode without password

Mode 0 Connection in UNI-TELWAY slave mode

Report %MW1024:4 %MW1030= 300, corresponds to a time-out of 30 s%MW 1031 = 4, corresponds to the length in bytesof the telephone number to be called (in the example4 bytes)


___________________________________________________________________________F1/27

F

1.6 Guide to choosing the operating parameters

1.6-1 In UNI-TELWAY mode

UNI-TELWAY master or slave mode, and the addresses used, depend on the followingparameters :

• the parameters in the Calling mode field in the configuration screen

• the Mode parameter of the CALL_MODEM communication function

Communication between two TSX MDM 10 cards

Caller

Screen parameters default : Ad0 = n and default :Ad0 = 1 and no. of addresses = 2 Ad0 = 1 andno. of addresses = 2 no. of addresses = 2

CALL_MODEM default : default : value xx, byte 0 = 02mode value 0 value 0 byte 1 = 50 (slave to be

scanned at address 50and 51)

Description becomes UTW slave becomes UTW slave becomes UTW masterwith addresses with addresses and scans addressesAd0 = 1 and Ad1 = 2 Ad0 = n and Ad1 = n+1 50 and 51

Called

Screen parameters default : N/A N/AAd0 = 1 andno. of addresses = 2

Description becomes UTW master becomes UTW master becomes slave whichand scans slave and scans slave answers on addressesaddresses 1 and 2 addresses n and n+1 50 and 51

Comments most common situation : this mode is used to this mode is used tocommunication between allocate a different communicate with2 TSX MDM 10 cards slave address to devices configured

each caller (useful as UTW slavesin a multistationarchitecture)

___________________________________________________________________________F1/28

F

Communication with a called third-party device

Caller : TSX MDM 10

Screen parameters default : Ad0 = n and default :Ad0 = 1 and no. of addresses = 2 Ad0 = 1 andno. of addresses = 2 no. of addresses = 2

Function mode default : default : value xx, byte 0 = 02value 0 value 0 byte 1 = 50 (slave to be

scanned at address 50and 51)

Description becomes UTW slave becomes UTW slave becomes UTW masterwith addresses with addresses and scans addressesAd0 = 1 and Ad1 = 2 Ad0 = n and Ad1 = n+1 50 and 51

Called : third-party device

Description UTW master and UTW master and slave withscans slave scans slave slave addressesaddresses 1 and 2 addresses n and n+1 Ad0 = 50 and Ad1 = 51

Comments use the initialization use the initializationprotocol described in protocol described inthe appendix (coding the appendix (codingexchanges) exchanges)

Communication with a calling third-party device

Caller : third-party device

Description slave with slave with UTW master and must scanaddresses 1 and 2 slave addresses the addresses configured

n and n+1 in the TSX MDM 10

Called : TSX MDM 10

Screen parameters default : requires the N/AAd0 = 1 and configuration Ad0 = nno. of addresses = 2 and no. of addresses = 2

Description becomes UTW master becomes UTW master becomes UTW slaveand scans addresses and scans addresses with the configuredAd0 = 1 and Ad1 = 2 Ad0 = n and Ad1 = n+1 addresses

Comments _ _ use the initializationprotocol described inthe appendix (codingexchanges)


___________________________________________________________________________F1/29

F

1.6-2 In character mode

Character mode depends on the following parameters :

• the parameters in the configuration screen

• the Option parameter of the CALL_MODEM communication function.

Communication between two TSX MDM 10 cards

Caller

Screen parameters character mode configuration (data coded on 8 bits)

Option character mode protocol

Called

Screen parameters character mode configuration identical to that for the caller

Comments transmission of the character string described in the appendix(coding exchanges)

Communication with a called third-party device

Caller

Screen parameters character mode configuration

Option character mode protocol

Called

Description use the initialization protocol described in the appendix (codingexchanges)


Communication with a calling third-party device

Caller

Screen parameters character mode configuration (data coded on 8 bits)

Description use the initialization protocol described in the appendix (codingexchanges) for transmission of the character string

Called

Screen parameters character mode configuration identical to that for the caller


___________________________________________________________________________F1/30

F

1.7 Appendix

1.7-1 Coding exchanges

Password management depends on the following parameters :

• the Station password parameter in the modem configuration screen

• the Mode and Options parameters of the CALL_MODEM communication function.

The character string which can be sent on the line complies with the following format :

• Password field : 8 bytes containing the value FFFFFFFF in hexadecimal format orthe value of the station password

• Type (type of protocol) field : 1 byte containing 0 for UNI-TELWAY mode or 1 forcharacter mode

• Slave number field : 1 byte containing a value of 1 to 98

• Number of slave addresses field : 1 byte

• additional field of 20 bytes (not used)

Calling station (TSX MDM 10) Called station (TSX MDM 10)

If the station has the default configuration, the Situation in which password managementmodem does not transmit a character string on is not configured :the line. 1 If no character string is received on theDefault configuration : line, after a 5 second wait the station changesconnection without password by the to UNI-TELWAY master mode and scansCALL_MODEM function slave addresses Ad0=1 and Ad1=2.and 2 Otherwise the station tests whether theUNI-TELWAY slave protocol with Password field is equal to FFFFFFFFhaddresses AD0 = 1 and AD1 = 2 - If the test result is true, the station tests the

Type, Mode and Number of addressesfields and switches to the corresponding mode.

- Otherwise, the line is closed.Situation in which password managementis configured :The station tests the password which is received- If the password received does not

correspond to any of the passwords inthe list, the line is closed.

- If the test result is true, the station tests theType, Mode and Number of addressesfields and switches to the corresponding mode.

In all other cases, the station sends thecharacter string


___________________________________________________________________________F1/31

F

1.7-2 AT commands

The modem will respond to the commands described below. Parameters applicableto each command are given in the description of the command. The default settingsshown for each configuration command are those used in the Rockwell factory profile.

A/ - Re-execute Command

The modem behaves as though the last command line had been re-sent by the DTE."A/" will repeat all the commands in the command buffer.The principal application of this command is to repeat a call (using the Dial command)that failed to connect due to a busy line or no answer. This command must appearalone on a command line and must be terminated by the "/" character. This commandshould not be terminated by a carriage return.

AT= x - Write to Selected S-Register

This command writes the value x to the S-register which is currently selected. An S-register can be selected by using the ATSn command. All of the S-registers will returnthe OK response if x is a number.

Result codes :OK For all arguments.

AT? - Read Selected S-Register

This command reads and displays the selected S-register. An S-register can beselected by using the ATSn command.

Result codes :OK For all arguments.

A - Answer

The modem will go off-hook and attempt to answer an incoming call if the requiredconditions are met. Upon successful completion of the answer handshake, themodem will go on-line in answer mode.

Cn - Carrier Control

This command is included for compatibility only and has no effect other than returninga result code. The only valid parameter is 1.

Result codes :OK n = 1.ERROR Otherwise.

___________________________________________________________________________F1/32

F

Dn - DialThis command directs the modem to go off-hook, dial the number corresponding to thedial string entered and attempt to establish a connection. If no dial string is supplied,the modem will go off-hook and attempt the handshake in originate mode.Dial Modifiers :The valid dial string parameters are described below. Punctuation characters such asparentheses, hyphens and spaces may be used for clarity, since they are ignored bythe command.

0-9 DTMF digits 0 to 9.* The 'star' symbol (tone dialing only).# The 'hash' symbol (tone dialing only).A-D DTMF characters A, B, C and D. Some countries may prohibit sending of these

characters during dialing.L Last number redial : the modem redials the last valid telephone number.

The L must be immediately after the D with all the following characters ignored.P Selects pulse dialing : pulse dialing dials the numbers which follow until a "T"

is encountered. Applies to the current and subsequent dialing operations. Insome countries, it is not possible to change dialing mode after thefirst digit is dialed.

T Selects tone dialing : tone dialing dials the numbers which follow until a "P" isencountered. Applies to the current and subsequent dialing operations.In some countries, it is not possible to change dialing mode after the first digit isdialed.

R This command will be accepted, but not acted on.S=n Dials the number stored in the directory (n = 0 to 19) (see &Z command).! Flash : the modem will go on-hook for a time defined by the value of S29.

In some countries, limits may be set for this time period.W Await dial tone : the modem waits for the tone before dialing the digits which

follow "W".@ Await silence : the modem will wait for at least 5 seconds of silence in the call

progress frequency band before continuing to execute the dial string. If themodem does not detect this 5 second silence before the expiry of a perioddefined by the call abort timer (S7), the modem will terminate the call attemptwith a NO ANSWER message. If busy detection is enabled, the modem mayterminate the call with the BUSY result code. If the answer tone arrives duringexecution of this parameter, the modem handshakes.

, Dial pause : the modem pauses for the time period indicated by S8, beforedialing the digits which follow ",". ;

; Return to command state. Added to the end of the dial string, this parametercauses the modem to return to the command state after it has processed theportion of the dial string preceding the ";".This allows the user to issue additional AT commands while remaining off-hook.The additional AT commands may be placed in the original command linefollowing the ";" and/or entered on subsequent command lines. The modem willonly try to establish the connection when a new dialing command is sent withoutthe ";" terminator. Use "H" to abort the dial in progress, and go back on-hook.

^ Toggles the call tone : only applies to the current dial attempt.( ) Ignored : can be used to format the dial string.- Ignored : can be used to format the dial string.<space> Ignored : can be used to format the dial string.<i> Invalid symbol : will be ignored.


___________________________________________________________________________F1/33

F

En - Command Echo

The modem enables or disables the echo of characters to the DTE according to theparameter entered. The parameter value, if valid, is written to S14.

E0 Disables command echo.E1 Activates command echo (default).

Result codes :OK n = 0 or 1.ERROR Otherwise.

Hn - Disconnect (Hang-Up)

This command initiates a hang-up sequence. It may not be available in somecountries.

H0 The modem will release the line if it is currently on-line, and will terminate anytest (AT&T) which is in progress. Country-specific, modulation-specific, anderror correction protocol-specific (S38) processing is handled outside the H0 command.

H1 Only in STN mode, if the modem is on-hook, it will go off-hook and entercommand mode. The modem will return on-hook after a period of timedetermined by S7.


In - Identification

The modem reports to the DTE the result corresponding to the command parameterentered.

I0 Gives the product code (eg. "14400").I1 Gives the precalculated checksum from the ROM (eg. "007").I3 Gives the firmware revision (eg. "V1.000S").I4 Gives the identifier string defined by the OEM (eg. "RC96ACL").I5 Gives the country code (eg. "022").I6 Gives the modem data pump model.

Result codes :OK n = 0 to 6.ERROR Otherwise.

Ln - Speaker Volume

The modem sets the speaker volume control according to the parameter entered. Theparameter value, if valid, is written to S22 bits 0 and 1.

L0 Off or low volume.L1 Low volume (default).L2 Medium volume.L3 High volume.


___________________________________________________________________________F1/34

F

Mn - Speaker ControlThis command controls when the speaker will be on or off. The parameter value, if valid,is written to S22 bits 2 and 3.

M0 The speaker is always off.M1 The speaker is on during call establishment, but off when receiving

the carrier (default).M2 The speaker is always on.M3 The speaker is off when receiving the carrier and during dialing.

Result codes :OK n = 0 to 3.ERROR If n is other than 0 to 3.Nn - Automode EnableThis command enables or disables automode detection. The parameter value, ifvalid, is written to S31 bit 1.

N0 Automode detection is disabled (equivalent to setting the +MS subparameter to0). The subsequent handshake will be conducted according to the contents ofS37 or, if S37 is zero, according to the most recently detected DTE speed.

N1 Automode detection is enabled (equivalent to setting the +MS subparameter to1). The subsequent handshake will be conducted according to the automodealgorithm supported by the modem, ie. according to the contents of S37 or, ifS37 is zero, starting at 28800 bps V.34 (RC288). This command is alsoequivalent to F0 (RC144) (default).

Result codes :OK n = 0 to 1.ERROR Otherwise.Notes1. The Nn and S37=x commands override the +MS command settings. When the N0 or N1command is issued, the +MS subparameters are updated to reflect the Nn and S37 values (see+MS command and S37 register). For example :N1S37=10 updates the +MS command subparameters to reflect +MS=10,1,300,12000N0S37=10 updates the +MS command subparameters to reflect +MS=10,0,12000,120002. Use of the +MS command is recommended instead of the Nn and S37=x commands. Nn andS37=x commands are supported for compatibility with existing communication software.


___________________________________________________________________________F1/35

F

On - Return to Online Data Mode

This command determines how the modem will enter online data mode. If the modemis in the online command mode, this command enters the online data mode with orwithout a retrain. If the modem is in the offline command mode (no connection), ERRORis reported.

O0 Enters online data mode without a retrain. Handling is determined by the CallEstablishment task. Generally, if a connection exists, this command reconnectsthe DTE to the remote modem after an escape (+++).

O1 Only in STN mode. Enters online data mode after a retrain.

Result codes :CONNECT n = 0 or 1 and a connection exists.ERROR Otherwise or if not connected.

P - Set Pulse Dial Default

This command forces pulse dialing until the next T dial modifier or T command isreceived. It sets S14 bit 5 to 1. As soon as a dial command is executed which explicitlyspecifies the dialing mode for that particular call (eg. ATDT...), this command iscanceled so that all future dialing will be tone dialed (see T command). This commandmay not be permitted in some countries.

Result code :OK

Qn - Quiet Result Codes Control

The command enables or disables the sending of result codes to the DTE accordingto the parameter supplied. The parameter value, if valid, is written to S14.

Q 0 Sends result codes to the DTE (default).Q 1 Disables result codes to the DTE.


___________________________________________________________________________F1/36

F

Sn - Read/Write S-Register

The modem selects an S-register, performs an S-register read or write function, orreports the value of an S-register.

n Establishes S-register n as the default register.n=v Sets S-register n to the value v.n? Indicates the value of S-register n. Parameter n can be omitted, in which case

the value of S0 will be assumed. S can be omitted, in which case the value ofthe last S-register accessed (default register) will be assumed.

For example :

ATS7 establishes S7 as the default register.ATS38 establishes S38 as the default register.AT=40 sets the contents of the default register to 40.ATS=20 sets the contents of S0 to 20.

If the number "n" is outside the range of the available S-registers, the modem will returnan ERROR message. The value "v" is "MOD"ulo 256. If the result is outside the rangepermitted for a given S-register the values will still be stored, but functionally the lowerand higher limits will be observed.Input and output values are always in decimal format. It should be noted that some S-registers are read-only. In these cases, writing to the S-register will appear to beaccepted but the value will not actually be written.

T - Set Tone Dial Default

This command forces DTMF dialing until the next P dial modifier or P command isreceived. The modem will set an S-register bit to indicate that all subsequent dialingshould be conducted in tone mode. Note that the DP command will override thiscommand. It clears S14 bit 5. This command may not be permitted in some countries(see P command).

Result code :OK

Vn - Result Code Form

This command selects the sending of short-form or long-form result codes to the DTE.The parameter, if valid, is written to S14 bit 3.

V0 Enables short-form (numeric) result codes. A line feed is not issued before ashort-form result code.

V1 Enables long-form (text) result codes (default).



___________________________________________________________________________F1/37

F

Wn - Error Correction Message ControlThis command controls the format of CONNECT messages. The parameter value, ifvalid, is written to S31 bits 2 and 3. (See also, description of S95).

W0 Upon connection, the modem reports only the DTE speed (eg. CONNECT9600). Subsequent responses are disabled (default).

W1 Upon connection, the modem reports the line speed, the error correctionprotocol, and the DTE speed respectively. Subsequent responses are disabled.

W2 Upon connection, the modem reports the DCE speed (eg. CONNECT 2400).Subsequent responses are disabled.

Result codes :OK n = 0, 1, or 2.ERROR Otherwise.

Xn - Extended Result CodesThis command selects which subset of the result messages will be used by the modemto inform the DTE of the results of commands. Table 3-1 indicates the messages whichare enabled for each X value.If the modem is in facsimile mode (+FCLASS=1 or 2), the only message sent to indicatea connection is CONNECT without a speed indication.

X0 Disables busy tone detection unless this is imposed by country requirements.Only sends OK, CONNECT, RING, NO CARRIER, ERROR and NO ANSWERresult codes. Blind dialing mode is enabled/disabled following country parameters. Ifbusy tone detection is enforced and a busy tone is detected, NO CARRIER willbe reported instead of BUSY. If dial tone detection is enforced or selectedand no dial tone is detected, NO CARRIER will be reported instead of NO DIALTONE. The binary value 000 is written to S22 bits 6, 5 and 4 respectively.

X1 Disables busy tone detection unless this is imposed by country requirements.Only sends OK, CONNECT, RING, NO CARRIER, ERROR, NO ANSWERand CONNECT XXXX (XXXX = rate) result codes. Blind dialing mode isenabled/disabled by country parameters. If busy tone detection is enforced anda busy tone is detected, NO CARRIER will be reported instead of BUSY. If dialtone detection is enforced or selected and no dial tone is detected, NOCARRIER will be reported instead of NO DIAL TONE. The binary value 100 iswritten to S22 bits 6, 5 and 4 respectively.

X2 Disables busy tone detection unless this is imposed by country requirements.Only sends OK, CONNECT, RING, NO CARRIER, ERROR, NO DIALTONE,NO ANSWER and CONNECT XXXX result codes. If busy tone detection isenforced and a busy tone is detected, NO CARRIER will be reported instead ofBUSY. If dial tone detection is enforced or selected and no dial tone is detected,NO CARRIER will be reported instead of NO DIAL TONE. The binary value101 is written to S22 bits 6, 5 and 4 respectively.

X3 Enables busy tone detection. Only sends OK, CONNECT, RING, NO CARRIER,ERROR, NO DIALTONE, NO ANSWER and CONNECT XXXX result codes.Blind dialing enabled/disabled by country parameters. If dial tone detection isenforced and no dial tone is detected, NO CARRIER will be reported instead ofNO DIAL TONE. The binary value 110 is written to S22 bits 6, 5 and respectively.

X4 Enables busy tone detection. Sends all messages. The binary value 111 iswritten to S22 bits 6, 5 and 4 respectively (default).

___________________________________________________________________________F1/38

F


Table of Result Codes

Short form Long form Value n in ATXn command Notes0 1 2 3 4

0 O K x x x x x

1 CONNECT x x x x x

2 RING x x x x x

3 NO CARRIER x x x x x

4 ERROR x x x x x

5 CONNECT 1200 1 x x x x

6 NO DIALTONE 3 3 x x x

7 BUSY 3 3 3 x x

8 NO ANSWER x x x x x












20 CONNECT 230400 x x x x x Note 4

22 CONNECT 75TX/1200RX 1 x x x x

23 CONNECT 1200TX/75RX 1 x x x x

24 DELAYED 4 4 4 4 x

32 BLACKLISTED 4 4 4 4 x

33 F A X x x x x x

35 DATA x x x x x


___________________________________________________________________________F1/39

F



40 CARRIER 300 x x x x x

44 CARRIER 1200/75 x x x x x

45 CARRIER 75/1200 x x x x x








53 CARRIER 16800 x x x x x Note 2






59 CONNECT 16800 1 x x x x Note 2





66 COMPRESSION: CLASS 5 x x x x x

67 COMPRESSION: V.42 bis x x x x x

69 COMPRESSION: NONE x x x x x

70 PROTOCOL: NONE x x x x x

77 PROTOCOL: LAPM x x x x x



80 PROTOCOL: ALT x x x x x

81 PROTOCOL: ALT-CELLULAR x x x x x



___________________________________________________________________________F1/40

F





























+F4 +FCERROR x x x x x

Notes :1. An 'x' in a column indicates that the message (either the long form if verbose, or the value onlyfor short form) will be generated when the corresponding value of 'n' (shown at the top of thecolumn) has been selected by the use of the ATXn command. If the column is blank, then nomessage will be generated for that x option. A number indicates which less explicit message (longor short form) will be sent for that x option. 2. RC288 and higher rate modems. 3. RC336 and higherrate modems. 4. RC56 modems.


___________________________________________________________________________F1/41

F

Yn - Long Space DisconnectThis command enables/disables the generation and response to long spacedisconnect. The parameter value, if valid, is written to S21 bit 7.

Y0 Disables long space disconnect.Y1 Enables long space disconnect. In non-error correction mode, the modem will

send a long space of four seconds prior to hanging up. In non-error correction mode, themodem will respond to the receipt of a long space (eg. a break signal longer than 1.6seconds) by hanging up.


Zn - Soft Reset and Restore ProfileThe modem performs a soft reset and restores (recalls) the configuration profiledefined by the parameter. If no parameter is specified, zero is assumed.

Z0 Soft reset and restore stored profile 0.Z1 Soft reset and restore stored profile 1.


&Cn - DCD Option

The modem controls the DCD output according to the parameter which has beenentered. The parameter value, if valid, is written to S21 bit 5.

&C0 DCD is on at all times (default).&C1 DCD follows the state of the carrier.


&Dn - DTR OptionThis command interprets the ON to OFF transition of the DTR signal from the DTE inaccordance with the parameter supplied. The parameter value, if valid, is written to S21bits 3 and 4.

&D0 DTR drop is interpreted according to the current &Q setting asfollows : (default value)&Q0,&Q5, DTR is ignored (assumed ON). Allows operation with&Q6 DTEs which do not have DTR signals provided.&Q4 DTR drop causes the modem to hang up. Auto-answer

not affected.&D1 DTR drop is interpreted according to the current &Q setting as follows :

&Q0, &Q4,DTR drop is interpreted by the modem as if the synchronous&Q5, &Q6 escape sequence had been entered. The modem returns to

asynchronous command state without disconnecting.&D2 DTR drop is interpreted according to the current &Q setting as follows :

&Q0 to DTR drop causes the modem to hang up. Auto-answer&Q6 is disabled.

___________________________________________________________________________F1/42

F

Yn - Long Space DisconnectThis command enables/disables the generation and response to long spacedisconnect. The parameter value, if valid, is written to S21 bit 7.

Y0 Disables long space disconnect.Y1 Enables long space disconnect. In non-error correction mode, the modem

will send a long space of four seconds prior to hanging up. In non-errorcorrection mode, the modem will respond to the receipt of a long space (ie., a breaksignal longer than 1.6 seconds) by hanging up.


Zn - Soft Reset and Restore ProfileThe modem performs a soft reset and restores (recalls) the configuration profiledefined by the parameter. If no parameter is specified, zero is assumed.

Z0 Soft reset and restore stored profile 0.Z1 Soft reset and restore stored profile 1.


&Cn - DCD OptionThe modem controls the DCD output according to the parameter which has beenentered. The parameter value, if valid, is written to S21 bit 5.

&C0 DCD is on at all times (default).&C1 DCD follows the state of the carrier.


&Dn - DTR OptionThis command interprets the ON to OFF transition of the DTR signal from the DTE inaccordance with the parameter supplied. The parameter value, if valid, is written to S21bits 3 and 4.

&D0 DTR drop is interpreted according to the current &Q setting as follows : (default)&Q0,&Q5, DTR is ignored (assumed ON). Allows operation with DTEs&Q6 which do not have DTR signals provided.&Q4 DTR drop causes the modem to hang up. Auto-answer is not

affected.&D1 DTR drop is interpreted according to the current &Q setting as follows :

&Q0, &Q4,DTR drop is interpreted by the modem as if the synchronous&Q5, &Q6 escape sequence had been entered. The modem returns to

asynchronous command state without disconnecting.


___________________________________________________________________________F1/43

F

&D2 DTR drop is interpreted according to the current &Q setting as follows :&Q0 to DTR drop causes the modem to hang up. Auto-answer&Q6 is disabled.

&D3 DTR drop is interpreted according to the current &Q setting as follows :&Q0, &Q4,DTR drop causes the modem to execute a soft reset as if it had&Q5, &Q6 received the Z command. The value of &Y defines which profile is

loaded.

If &Q5, &Q6, +FCLASS=1 is in effect, the action taken is the same as for &Q0.

&Fn - Restore Factory Configuration (Profile)

The modem loads the factory default configuration profile according to the parametersupplied. The Rockwell factory default values for profile 0 (&F0) are used for eachcommand and in the S-register descriptions. Two profiles are available. A configurationprofile consists of a subset of S-registers.

&F0 restore factory profile 0 (default).&F1 restore factory profile 1.

&Gn - Select Guard Tone

The modem generates the guard tone selected by this command according to theparameter supplied (DPSK modulation modes only). The parameter value, if valid, iswritten to S23 bits 6 and 7.

&G0 Disables guard tone (default for US models).&G1 Disables guard tone. &G2 selects a guard tone of 1800 Hz (default valuefor W-class models).


&Kn - Flow Control

This command defines the DTE/DCE (terminal/modem) flow control mechanism. Theparameter value, if valid, is written to S39 bits 0, 1, and 2.

&K0 disables flow control.&K3 enables RTS/CTS flow control - Hardware flow control (default for

data modem modes).&K4 enables XON/XOFF flow control - Software flow control.&K5 supports transparent XON/XOFF flow control.&K6 enables both RTS/CTS flow control and XON/XOFF flow control (defaultfor fax-modem modes).

Result codes :OK n = 0, 3, 4, 5, or 6.ERROR Otherwise.

___________________________________________________________________________F1/44

F

&Pn - Select Pulse Dial make/Break Ratio

This command determines the make/break ratio used during pulse dialing. It is onlyeffective if the appropriate bit to enable this command is set through the ConfigurACEprogram. If enabled, it will override the make/break ratios in the OEM parameters inConfigurACE. The default is country-dependent. The parameter value, if valid, is writtento S28 bits 3 and 4.

&P0 Selects 39%-61% make/break ratio at 10 pulses per second. (Default.)&P1 Selects 33%-67% make/break ratio at 10 pulses per second.&P2 Selects 39%-61% make/break ratio at 20 pulses per second.&P3 Selects 33%-67% make/break ratio at 20 pulses per second.

Result Codes:OK n = 0 to 3.ERROR Otherwise.

&Qn - Sync/Async Mode

This command is an extension of the &M command and is used to control theconnection modes permitted. It is used in conjunction with S36 and S48. (Also, see\N command.)

&Q0 Selects direct asynchronous operation. See &M0.&Q4 Selects autosync operation. The binary value 100 is written to S27 bits 3, 1,

and 0, respectively.&Q5 The modem will try to negotiate an error-corrected link. The modem can be

configured using S36 to determine whether a failure will result in the modemreturning on-hook or will result in fallback to an asynchronous connection. Thebinary value 101 is written to S27 bits 3, 1, and 0, respectively. (Default.)

&Q6 Selects asynchronous operation in normal mode (speed buffering). The binaryvalue 110 is written to S27 bits 3, 1, and 0, respectively.

Result Codes:OK n = 0, 1, 2, 4, 5, 6ERROR Otherwise.

&Rn - RTS/CTS Option

This selects how the modem controls CTS. CTS operation is modified if hardware flowcontrol is selected (see &K command).

&R0 In sync mode, CTS tracks the state of RTS; the RTS-to-CTS delay is definedby S26. In async mode, CTS acts according to V.25 bis handshake.

&R1 In sync mode, CTS is always ON (RTS transitions are ignored). In asyncmode, CTS will only drop if required by flow control. (Default.)

Result Codes:OK n = 0 or 1.ERROR Otherwise.


___________________________________________________________________________F1/45

F

&Sn - DSR Override

This command selects how the modem will control DSR. The parameter value, if valid,is written to S21 bit 6.

&S0 DSR will remain ON at all times. (Default.)&S1 DSR will become active after answer tone has been detected and inactive after

the carrier has been lost.

Result Codes:OK n = 0 or 1.ERROR Otherwise.

&V - Display Current Configuration and Stored Profiles

Reports the current (active) configuration, the stored (user) profiles, and the first fourstored telephone numbers. The stored profiles and telephone numbers are notdisplayed if the NVRAM is not installed or is not operational as detected by the NVRAMtest during reset processing.

Result Code:OK

Example:AT&VACTIVE PROFILE:B0 E1 L1 M1 N1 QO T V1 W0 X4 Y0 &C0 &D0 &G2 &J0 &K3 &Q5 &R1 &S0 &T4 &X0&Y0S00:002 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002 S07:030 S08:002S09:006S10:014 S11:255 S12:050 S18:000 S25:005 S26:001 S36:007 S37:000 S38:020S46:138S48:007 S95:000

STORED PROFILE 0:B0 E1 L1 M1 N1 QO T V1 W0 X4 Y0 &C0 &D0 &G2 &J0 &K3 &Q5 &R1 &S0 &T4 &X0S00:002 S02:043 S06:002 S07:030 S08:002 S09:006 S10:014 S11:095 S12:050S18:000S36:007 S37:000 S40:105 S41:003 S46:138 S95:000

STORED PROFILE 1:B0 E1 L1 M1 N1 QO T V1 W0 X4 Y0 &C0 &D0 &G2 &J0 &K3 &Q5 &R1 &S0 &T4 &X0S00:002 S02:043 S06:002 S07:030 S08:002 S09:006 S10:014 S11:095 S12:050S18:000S36:007 S37:000 S40:105 S41:003 S46:138 S95:000

TELEPHONE NUMBERS:0 = 1 =2 = 3 =OK

___________________________________________________________________________F1/46

F

&V1 - Display Last Connection Statistics

Displays the last connection statistics in the following format (shown with typicalresults) :

TERMINATION REASON..........LINK DISCONNECT or LOCAL REQUESTLAST TX data rate..........33600 BPSHIGHEST TX data rate...........33600 BPSLAST RX data rate...........28800 BPSHIGHEST RX data rate........28800 BPSError correction PROTOCOL...LAPMData COMPRESSION............V42BisLine QUALITY................030Highest SPX RX state........068Highest SPX TX state........067

&Wn - Store Current Configuration

Saves the current (active) configuration (profile), including S-registers, in one of the twouser profiles in NVRAM as denoted by the parameter value. This command will resultin an ERROR message if the NVRAM is not installed or it is detected as not operationalby the test. The current configuration comprises of a list of storable parametersillustrated in the &V command. These settings are restored to the active configurationupon receiving a Zn command or at power up (see &Yn command).

&W0 Store the current configuration as profile 0.&W1 Store the current configuration as profile 1


&Yn - Designate a Default Reset Profile

Selects which user profile will be used after a hard reset.&Y0 The modem will use profile 0.&Y1 The modem will use profile 1.


&Zn=x - Store telephone number

The modem can store up to 20 telephone numbers. Each telephone number dial stringcan contain up to 45 digits.

&Zn=x n = 0 to 19 (W-class) and x = dial string (requires a 2048 byte NVRAM).

Result codes :OK n = 0 to 19 and x less than or equal to 45 digits.ERROR If n > 19 or x greater than 45 digits.


___________________________________________________________________________F1/47

F

%En - Enable/Disable Line Quality Monitor and Auto-Retrain or Fallback/FallForward

Controls whether or not the modem will automatically monitor the line quality andrequest a retrain (%E1) or fall back when line quality is insufficient or fall forward whenline quality is sufficient (%E2). Applies to dial-up line only. The parameter value, if valid,is written to S41 bits 2 and 6.If enabled, the modem attempts to retrain for a maximum of 30 seconds.

%E0 Disable line quality monitor and auto-retrain (default).%E1 Enable line quality monitor and auto-retrain.%E2 Enable line quality monitor and fallback/fall forward.

Result codes :OK n = 0, 1, or 2.ERROR Otherwise.

%L - Line Signal Level

Returns a value which indicates the received signal level. The value returned is a directindication of the receive level at the Modem Data Pump, not at the telephone lineconnector. For example, 009 = -9 dBm, 043 = -43 dBm, and so on.

Result codes :OK

%Q - Line Signal Quality

Reports the line signal quality (DAA dependent). Returns the higher order byte of theEQM value. Based on the EQM value, retrain or fallback/fall forward may be initiatedif enabled by %E1 or %E2.Example :AT%Q015

Result codes :OK If connected.ERROR If not connected, or connected in 300 bps, V.23, or fax modes.

___________________________________________________________________________F1/48

F

\Kn - Break Control

Controls the response of the modem to a break received from the DTE or the remotemodem or the \B command according to the parameter supplied. The parameter value,if valid, is written to S40 bits 3, 4, and 5.The response is different in three separate cases.

The first case is where the modem receives a break from the DTE when the modem isoperating in data transfer mode :

\K0 Enter online command mode, no break sent to the remote modem.\K1 Clear data buffers and send break to remote modem.\K2 Same as \K0\K3 Send break to remote modem immediately.\K4 Same as \K0\K5 Send break to remote modem in sequence with the data transmitted (default).

The second case is where the modem is in the online command state (waiting for ATcommands) during a data connection, and the \B is received in order to send a breakto the remote modem :

\K0 Clear data buffers and send break to remote modem.\K1 Clear data buffers and send break to remote modem (same as \K0).\K2 Send break to remote modem immediately.\K3 Send break to remote modem immediately (same as \K2).\K4 Send break to remote modem in sequence with data.\K5 Send break to remote modem in sequence with the data (same as \K4) (default).

The third case is where a break is received from the remote modem during a non-errorcorrected connection :

\K0 Clear data buffers and sends break to the DTE.\K1 Clear data buffers and send break to the DTE (same as \K0).\K2 Send break immediately to DTE.\K3 Send break to the DTE immediately (same as \K2).\K4 Send break in sequence with received data to DTE.\K5 Send break to the DTE in sequence with the data received (same as \K4)

(default).



___________________________________________________________________________F1/49

F

\Nn - Operating Mode

This command controls the preferred error correction mode to be negotiated in asubsequent data connection. This command is affected by the OEM firmwareconfiguration.

\N0 Selects normal speed buffered mode (disables error-correction mode)(equivalent to &Q6).

\N1 Serial interface selected - Selects direct mode and is equivalent to &M0, &Q0operating mode (equivalent to &Q0). Parallel interface selected - same as \N0.

\N2 Selects reliable (error-correction) mode). The modem will first attempt an LAPMconnection then an MNP connection. If this fails, the modem hangs up (equivalentto &Q5, and S48=7).

\N3 Selects auto reliable mode. This mode is the same as \N2 except that if themodem fails to establish a reliable connection, it defaults to normal mode(equivalent to &Q5, S36=7 and S48=7).

\N4 Selects LAPM error-correction mode. If this fails, the modem hangs up(equivalent to &Q5 and S48=0).

\N5 Selects MNP error-correction mode. If this fails, the modem hangs up(equivalent to &Q5, S36=4 and S48=128).


\Vn - Single Line Connect Message Enable

The single line connect message format can be enabled or disabled by the \Vncommand as follows :

\V0 Connect messages are controlled by the command settings X and W, andS95.

\V1 Connect messages are displayed in the single line format described below,subject to the command settings V (verbose) and Q (quiet).In short-form mode (V0), single line connect messages are disabled and asingle-number result code is generated for CONNECT DTE.

When single line connect messages are enabled, there are no CARRIER, PROTOCOL,or COMPRESSION messages apart from the fields described below.

The single line connect messages format is:

CONNECT <DTE Speed></Modulation></Protocol></Compression></Line Speed>/<Voice and Data>

Where :DTE Speed = DTE speed, eg., 57600.Modulation = "V32" for V.32 or V.32bis modulations.

"V34" for V.34 modulations.

NoteModulation is omitted for all other modulations.

___________________________________________________________________________F1/50

F

Protocol = "NONE" for no protocol."ALT" for Microcom Network Protocol."LAPM" for LAP-M protocol.

Compression = "CLASS5" for Microcom MNP5 compression."V42BIS" for V.42bis compression.Note : Compression is omitted if protocol is NONE.

Line Speed = Asymmetric rates are displayed as follows : /rate TX/rate RX, eg. /1200 TX/75 RX.

Symmetric rates are displayed as a single DCE rate,eg. 14400.Voice and Data = Blank for Data mode only.

"SVD" for AudioSpan analog simultaneous audio/voiceand data.

"DSVD" pour communication simultanée numérique voix etdonnées G.729A ou DigiTalk.

___________________________________________________________________________1

G

Modbus Plus Contents

Section Page

1 Modbus Plus 1/1

1.1 General 1/1

1.2 Peer Cop service 1/2

1.3 PL7 installation 1/51.3-1 Configuring the network 1/51.3-2 Debugging 1/7

1.4 Modbus Plus protocol 1/81.4-1 Description of the logical network 1/81.4-2 Read / Write function on a local segment 1/81.4-3 Exchange services on Modbus Plus remote networks 1/111.4-4 Diagnostic function 1/141.4-5 Global data exchange function 1/16

1.5 Integration in an X-WAY architecture 1/17

1.6 Integration in a Modbus Plus architecture 1/19

1.7 Language objects 1/20

___________________________________________________________________________

2

G

Modbus Plus Contents

Section Page

Modbus Plus 1

___________________________________________________________________________G 1 / 1

G

Section 11 Modbus Plus

1.1 General

Communication via a Modbus Plus network is used for exchanging data between alldevices connected on the network.A Modbus Plus communication channel has three main functions :

• Point-to-point exchanges of data by a message handling service using the Modbusprotocol

• Broadcast exchanges of global data between all the stations involved in the exchange

• Multidrop exchanges of specific data via the Peer Cop services (only on TSXPremium)

This type of communication is available when a PCMCIA type III card, reference TSXMBP 100, is used. This card can only be inserted in the host channel of a TSX Microor Premium processor. It occupies one network communication channel.The hardware installation of this card is described in the TSX Premium or TSX MicroPLC installation manuals.Installation of the Modbus Plus bus is described in the Modicon Modbus plus networkinstallation manual : 890 USE 100 01.In the examples given in this document, it is assumed that the remote device is aQuantum PLC.

G 1 / 2___________________________________________________________________________

G

1.2 Peer Cop service

The Peer Cop service is an automatic exchange mechanism between stationsconnected on the same local Modbus Plus segment.This service is used to control remote I/O continuously via implicit exchanges.

TSX Premium PLCs support two types of Peer Cop transfer :

• specific inputs

• specific outputs

Specific inputs and outputs are point-to-point services using the multicast (multistation)protocol. Each message contains one or more destination addresses for sendingdata. This allows the exchange of data between several stations without having torepeat it.

This type of service requires the configuration of the internal words (location and size)in the Premium station which will be used during the exchanges.

TSX Micro PLCs do not support the Peer Cop service.

Specific inputs

When configuring the inputs, up to 32 internal words can be allocated for eachconnection point of the local bus. The total number of words must not exceed 500internal words.The data blocks are copied in full from the PCMCIA card to the internal words spacereserved during configuration.

There are three types of report :

• an activity bit : provides information on the availability and validity of the status bits

• status bits (one bit per station) :- ensure consistency between the number of specific inputs configured and the

number of specific inputs received- indicate whether the specific inputs have been received during the Timeout

• presence bits (one bit per station) : indicate whether the specific inputs have beenupdated

In the following example, the address of the first internal word is %MW10.

Modbus Plus 1

___________________________________________________________________________G 1 / 3

G

Specific outputs

When configuring the outputs, up to 32 internal words can be allocated for eachconnection point of the local bus. The total number of words must not exceed 500internal words.The data blocks are copied in full from the internal words space reserved duringconfiguration to the PCMCIA card. The reports are copied from the PCMCIA card to thelanguage objects.

There are two types of report :

• an activity bit : provides information on the availability and validity of the status bits

• status bits (one bit per station) :- ensure consistency between the number of specific outputs configured and the

number of specific outputs sent- indicate whether the specific outputs have been received by the stations

%MW103 words for station 1






copy

copy

Specific inputsPeer Cop data

Station 1

Status bits

Presence bits

Activity bit

Station 5

Station 6

Station 62

%IW0.1.6%IW0.1.7

... ... ...%IW0.1.14

500

wor

ds m

ax.

Modbus Plus networkPCMCIA cardInternal words

G 1 / 4___________________________________________________________________________

G

In the following example, the address of the first internal word is %MW10.







copy

copy

Specific outputsPeer Cop data

Station 1

Status bits

Activity bitStation 5

Station 6

Station 62%IW0.1.6%IW0.1.7

... ... ...%IW0.1.14

500

wor

ds m

ax.

Modbus Plus networkPCMCIA cardInternal words

Station 1

Station 5

Station 6

Station 62

Modbus Plus 1

___________________________________________________________________________G 1 / 5

G

1.3 PL7 installation

1.3-1 Configuring the network

To set up a Modbus Plus link, a TSX Micro or TSX Premium processor must be selectedfirst. Double-clicking on the "Comm" host channel icon opens a configuration windowused to select the PCMCIA TSX MBP 100 card and define the Modbus Plus addressof the connected station. This address must be unique on all the network stations.

If the specific Peer Cop services are used, the corresponding box must be checked andthe following data entered :

• the Timeout value (input update time)

• the input fallback mode (maintained or reset)

• the specific inputs and outputs

Timeout value

This is used to specify the maximum time by which the inputs from remote stations mustbe updated in the PCMCIA card. If the data is not updated in the time allocated, an erroris detected.

The time range extends from 20 ms to 2 s in increments of 20 ms.

G 1 / 6___________________________________________________________________________

G

Specific inputs and outputs

For specific inputs and outputs, the user must specify the start address and the size ofthe data to be exchanged.This data is stored in the internal words of the application.

Click on Specific Inputs or Specific Outputs to open a style window :

For each connection point of the local bus segment, the user must define :

• The start address in the table of internal words (%MW)

• The size of the exchanges from 0 to 32 words per station on the local bus segment

The internal words corresponding to specific inputs or outputs are stored continuously.The maximum size of the specific data must not exceed 1000 words (up to 500 wordsfor inputs and up to 500 words for outputs).

Modbus Plus 1

___________________________________________________________________________G 1 / 7

G

1.3-2 Debugging

Debug mode can only be accessed when the programming terminal is in online mode.Double-clicking on the processor host channel slot opens a window which displays thecounters indicating the number of faults on the Modbus Plus link between the local PLCand the remote PLCs.

A "Reset Counters" button is used to reset the counters to zero during networkdebugging or a maintenance operation. The station configuration cannot be modifiedin online mode.

G 1 / 8___________________________________________________________________________

G

1.4 Modbus Plus protocol

1.4-1 Description of the logical network

The Modbus Plus protocol is based on the principle of a logical token bus (LogicalToken Passing). Each station on the same network is identified by an address from 1to 64 and can access the network once it has received a token. Duplicate addressesare not valid.

1.4-2 Read / Write function on a local segment

A TSX Micro or PREMIUM PLC can exchange data with stations connected on the localModbus Plus network.Addressing a remote station :• The processor is located in a rack in position 0 or 1, depending on the size of the

selected power supply.

• The PCMCIA communication card is located in the processor host channel, namelychannel 1.

The READ_VAR and WRITE_VAR functions are used to access internal bits or wordsor input and output words in read/write mode on remote stations on the same localsegment. These exchanges are explicit exchanges managed by the application.The address of a remote TSX Premium or Micro station is defined in configuration modefor the processor which accepts the PCMCIA TSX MBP 100 card. For Quantum devices,refer to the processor documentation for information on how to define remote addresses.

Addressing from a TSX Premium station will be, for example :In read mode :

READ_VAR (ADR#0.1.10, '%MW', 10, 20, %MW10:20, %MW100:4

Address :slot in the processor :0 or 1. PCMCIA channel : 1. Destination stationnumber

Object type(internalwords)

Addressof the 1st

word to beread

Number ofwordsto be read

Content ofthe response Activity

bit andreportlength

Token bus (logical ring)

QuantumPremium

Modbus Plus 1

___________________________________________________________________________G 1 / 9

G

Address :slot in the processor :0 or 1. PCMCIA channel : 1. Destinationstation number

Object type(internalwords)

Address ofthe firstword to bewritten

Number ofwords tobe written

Value ofwords tobe written

Activitybit andreportlength

In write mode :

WRITE_VAR (ADR#0.1.10, '%MW', 10, 20, %MW10:20, %MW100:4

The object type parameter of the READ_VAR and WRITE_VAR functions is used toselect the object to be accessed in the remote stations :Read/write exchanges are on the initiative of the TSX Micro / Premium.

Premium transmits ----------------------------> Quantum responds Premium responds

READ_VAR or Type of PL7 object Quantum object Premium objectWRITE_VAR function sent back sent back

'%MW' output word 4x... memory area %MW

'%M' internal bit 0x... memory area %M

'%IW' input word 3x... memory area %MW

'%I' internal bit 1x... memory area %M

Quantum transmits ----------------------------> Premium responds

MSTR function block Premium object

Read %MWWrite %MW

In the READ-VAR and WRITE_VAR functions, '%I' and '%IW' PL7 object types can onlybe used in Modbus Plus to access input data of a remote device.

G1/10___________________________________________________________________________

G

WRITE_VAR(ADR#0.1.2,’%MW’,10,5,%MW100:10,%MW200:4)

READ_VAR(ADR#0.1.5,’%IW’,5,8,%MW100:5,%MW200:4)

Modbus +

Quantum

Quantum

1 2 5

Example :

The TSX Premium application writes 10 internal words to the Quantum PLC at address2, and reads 5 input words from the Quantum at address 5.

Comment

The Quantum memory area starts with address 1 and the Premium memory areastarts with address 0. There is an offset of one word between the two PLC memoryimages.

Modbus Plus 1

___________________________________________________________________________G1/11

G

1.4-3 Exchange services on Modbus Plus remote networks

A TSX Micro or Premium PLC can exchange data with stations connected to otherModbus Plus segments via BP85 Bridge Plus gateways.

This type of exchange can be accessed by the SEND_REQ function. To differentiatebetween reading and writing data from a remote station, a request code is associatedwith the SEND_REQ function. These exchanges are explicit exchanges managed bythe application.

In order to access a station connected to another network segment, the full routing pathmust be indicated in the information to be sent. Each device address must be explicitlystated, thus allowing exchanges to be made up to the destination station.

The data from read / write requests is encoded in the internal words to be sent as shownbelow :

Addressing syntax from a TSX Premium station :

SEND_REQ (ADR#0.1.61, 16#36, %MW300:50, %MW450:150, %MW600:4)

The actual size of the data to be sent must be indicated in bytes in the report.

%MWi %MWi+1 %MWi+2 %MWi+3 %MWi+4 %MWi+5

Thirdaddress

Secondaddress

Fifth address Fourthaddress

Type Segment Address ofthe first word

Size of thedata

Data

Address :slot in the processor : 0or 1. PCMCIA channel : 1. Destination nodenumber on the localbus

Request code :16#36 to readobjects,16#37 to writeobjects

Routingpath, lengthof data to besent

Address,length of datato be received

Activity bit andreport length

G1/12___________________________________________________________________________

G

2

1Modem

Modem

Modem

Slave113

Slave67

Slave A

MasterA

1 2 3 4

Multiplexerbridge

Premium

Quantum

Quantum

QuantumQuantum

22 13 61

12 30 2515

7 22

9

4

62

BP85Bridge Plus

Modbus Plus

BP85Bridge Plus

BP85Bridge Plus

BM85

Example 1 :

For a TSX Premium to read 120 internal words from the Quantum station at local address62, the following are required :

• the routing path to access the Quantum station : 61, 30, 22, 62, 0• the request code for the read operation : 16#36• the actual size of the data to be sent (stored in %MW603) : 10 bytes

SEND_REQ(ADR#0.1.61, 16#36, %MW300:5, %MW450:120, %MW600:4)

Internal words

%MW300 = 0x161E Second and third routing addresses (30, 22)

%MW301 = 0x003E Fourth and fifth routing addresses (62, 0)

%MW302 = 0x0768 Segment 104 and type 7 (depends on the type of variable to be read or written)

%MW303 = 80 Address of the first internal word to be read in the Quantum station

%MW304 = 240 Size of the data to be read (in bytes)

No data

Modbus Plus 1

___________________________________________________________________________G1/13

G

Example 2 :

For a TSX Premium to write 50 internal words to address 560 of slave 113 connectedto port 4 of the multiplexer bridge, the following are required :

• the routing path to access the slave : 61, 25, 4, 113, 0• the request code for the read operation : 16#37• the actual size of the data to be sent (stored in %MW603) : 110 bytes

• the value of the data to be written (stored in %MW305 to %MW354),

• the response (stored in %MW450:1) : does not contain any data to receive but musthave a minimum length of one word.

SEND_REQ(ADR#0.1.61, 16#37, %MW300:55, %MW450:1, %MW600:4)

Internal words

%MW300 = 0x0419 Second and third routing addresses (25, 4)

%MW301 = 0x0071 Fourth and fifth routing addresses (113, 0)

%MW302 = 0x0768 Segment 104 and type 7 (depends on the type of variable to be read or written)

%MW303 = 560 Address of the first internal word to be written in the slave

%MW304 = 100 Size of the data to be written (in bytes)

%MW305...%MW354 Data to be written

%MW603 = 110 Actual size of the data to be sent with this function (in bytes)

G1/14___________________________________________________________________________

G

1.4-4 Diagnostic function

The SEND_REQ function should be used to read the local or remote fault counters orreset them to zero. The UNI-TE request code 16#A2 is used to read the counters. Theaddress may be local or remote.Example :

SEND_REQ (ADR#0.1.5,16#A2,%MW100:1,%MW200:54,%MW300:4)

The counters comply with the Modbus Plus standard which defines the variouscounters for all the functions. The counters linked to the programming functions are notmanaged by the Premium or Micro PLC.The response will be the content of the 20 counters.

The UNI-TE request code 16#A4 is used to reset the counters to zero. The address maybe local or remote.

Example :

SEND_REQ(ADR#0.1.5, 16#A4, %MW100:1, %MW200:1, %MW300:4)

Report : 16#FE, eg : %MW301 = 16#FE00

The UNI-TE request code 16#A2 is used to read the contents of the counters.

SEND_REQ(ADR#0.1.5, 16#A2, %MW100:1, %MW200:20, %MW300:4)

Report : 16#D2, eg : %MW301: 16#D200. The length parameter in the report wordsshould be initialized to 0 before the request is sent (%MW304 = 0).


Requestcode16#A2readcounters

Data :no datato send Activity bit

and reportlength

Content oferrorcounters


Request code16#A4reset countersto zero

Data :no datato send

No data toreceive Activity bit and

report length

Modbus Plus 1

___________________________________________________________________________G1/15

G

List of the 20 counters :

Counter no. Meaning

1 Retransmit deferral error counter

2 Receive buffer DMA overrun error counter

3 Repeated command received counter

4 Frame size error counter

5 Receiver collision abort error counter

6 Receiver alignment error counter

7 Receiver CRC error counter

8 Bad-packet-length error counter

9 Bad link address error counter

10 Transmit buffer DMA underrun error counter

11 Bad internal packet length error counter

12 Bad mac function code error counter

13 Communication retry counter

14 Communication failed error counter

15 Good receive packet success counter

16 No response received error counter

17 Exception response received error counter

18 Unexpected path error counter

19 Unexpected response error counter

20 Forgotten transaction error counter

G1/16___________________________________________________________________________

G

1.4-5 Global data exchange function

The global data exchange function is a mechanism for a single exchange between thestations connected on the same Modbus Plus network. During an exchange, the stationwhich has the token can broadcast 32 words to the other 63 stations (maximum)connected on the network. A receiver station takes all or some of the words sent by thetransmitter stations and stores them. The same process occurs for each station as thetoken is passed on. Each station stores the global information from the network stationsin the PCMCIA card. These exchanges are periodic and are managed by theapplication.A TSX Premium or Micro PLC can transmit up to 32 words. It is important to initializethe memory correctly each time the device is switched on. The validity of the data mustbe ensured before any exchange with the global database. Two PL7 functions aredefined for writing global data from the application to the Modbus Plus network and forreading global data from the remote stations via the PCMCIA card.

Example of writing global data :

x = 1 to 32 global data words to be sent

WRITE_GDATA (ADR#0.1.SYS, %MW100:32, %MW200:4)

Example of reading global data.The address parameter specifies the address of the remote station in which theapplication wishes to read the global data :

READ_GDATA (ADR#0.1.10, %MW30:32, %MW300:4)

The length of the global data actually read is contained in the length word of the activityreport (eg : %MW304). If the length = 0, no new global data is available in the stationspecified in the request.


Global data to besentx= 1 to 32 words




Contents ofglobal data

Modbus Plus 1

___________________________________________________________________________G1/17

G

Quantum

FIPWAY #5

Modbus+

Quantum

READ_VAR(ADR#{5.3}0.1.5,’%MW’, 100, 10, %MW200:10,%MW300:4)

3

85

Premium

1.5 Integration in an X-WAY architecture

A Modbus Plus segment can be integrated into an X-WAY network architecture. A clientapplication connected to a FIPWAY or Ethernet TCP-IP network can communicate witha Modbus Plus station via the Modbus Plus protocol. In this case the user must indicatethe X-WAY network address of the TSX Premium PLC which is connected on theModbus Plus segment and on the FIPWAY network, as well as indicating the numberof the Modbus Plus destination station. The syntax is as follows :

{network number . station number} 0.1. Modbus Plus station number

Example :READ_VAR(ADR#{5.3}0.1.5, '%MW', 100, 10,%MW200:10, %MW300:4)

In this example, the FIPWAY station {5.3} has a Modbus Plus connection, and thereforeany remote FIPWAY station which wishes to communicate with a Modbus Plus station(station 5 for example) must use this address.

Configuration example :

Routing between FIPWAY and Modbus Plus is automatically provided by the system.

Important : In a network architecture, there is no need to declare a bridge station.

G1/18___________________________________________________________________________

G

If a Modbus Plus segment is integrated in an X-WAY architecture, a Quantum stationcannot communicate with stations connected on another network within the architecture(for example Fipway or Ethernet TCP-IP). It is only possible to communicate with thelocal Premium PLC.

The Quantum PLC sends in write request to modify 5 words in the PL7 application(%MW10, .....), but it cannot access stations on Fipway.

FIPWAY #5

Modbus+

Premium Quantum

3

5 8

MBP-MSTRwrite

510

RP=5.0.0.0.0

Modbus Plus 1

___________________________________________________________________________G1/19

G

1.6 Integration in a Modbus Plus architecture

A Quantum application can communicate with a TSX Premium PLC via a MSTR functionblock. In this case the TSX Premium or Micro is the server, therefore all the Modbus Plusstations connected in a network architecture, up to a maximum of 5 levels, cancommunicate with it.

The Quantum station sends a read request to the Premium station using the addresspath : 8.5.1.0.0 (routing path).The MSTR function block is used to read or write internal words of a Premium or Microstation. The slave register parameter of the MSTR function block directly indicates theaddress of internal word %MW in the PL7 application. This function block is also usedto read the statistical counters of a Premium or Micro station or to reset them to zero.This request is executed directly by the PCMCIA card which responds directly.

Bridge Modbus+

Bridge Modbus+

Quantum

Quantum

Premium

Modbus+

QuantumModbus+

MSTRread

1 2 3

5

84

G1/20___________________________________________________________________________

G

1.7 Language objects

Configuration objects :In TSX Premium PLCs, depending on the type of power supply selected, p equals 0 or1 according to the position of the processor in the rack.


%KWp.1.0 Modbus Plus type byte 0 = 14, Modbus Plus communication

%KWp.1.1 station address byte 0 = station address

%KWp.1.2 Peer cop byte 0 = 1, no Peer cop functionbyte 0 = 2, Peer cop function

Timeout byte 1 = 1, inputs resetbehavior byte 1 = 2, inputs maintained at their last value

%KWp.1.3 destination address address of the first internal word %MW used toof specific inputs receive specific inputs

%KWp.1.4 source address address of the first internal word %MW used toof specific outputs send specific outputs

%KWp.1.5 size of specific number of specific output words to be sent tooutputs for connection points 1 and 2nodes 1 and 2 byte 0 = connection point 1

byte 1 = connection point 2



... ... ...



%KWp.1.37 size of specific number of specific input words to be receivedinputs for from connection points 1 and 2nodes 1 and 2 byte 0 = connection point 1




... ... ...



%KWp.169 Timeout of the Timeout interval (increments of 20 ms)Peer cop service byte 0 = [1 to 100] (from 20 ms to 2 s)

Modbus Plus 1

___________________________________________________________________________G1/21

G

Explicit exchange objects :In TSX Premium PLCs, depending on the type of power supply selected, p equals 0or 1 according to the position of the processor in the rack.


%MWp.1.2 standard status x0 = 1 unique station on the networkx1 = 1 not usedx2 = 1 transmission line errorx3 = 1 not usedx4 = 1 internal software failurex5 = 1 hardware or software configuration fault or

no configurationx6 = 1 error communicating with the processorx7 = 1 application error : duplicate station address

%MWp.1.3 specific status byte 0 :MAC state = 0 initialization phasevariable = 3 awaiting token phase

= 4...10 normal status

%MWp.1.4 specific status byte 0 :Peer status = 0 station performing test

= 32 normal status= 64 no token= 96 unique station (same as x0 for %MWp.1.2)= 128 two stations have the same number

(same as x7 for %MWp.1.2)

Implicit exchange objects :

In TSX Premium PLCs, depending on the type of power supply selected, p equals 0or 1 according to the position of the processor in the rack.


%IWp.1.0 requests status of the communication channelsByte 0 = number of communication functions processed

simultaneously in client modex0 communication function 1x1 communication function 2x2 communication function 3x3 communication function 4

Byte 1 = number of communication functions processedsimultaneously in server mode

x0 communication function 1x1 communication function 2x2 communication function 3x3 communication function 4

G1/22___________________________________________________________________________

G


%IWp.1.1 not used

%IWp.1.2 presence of A bit at 1 indicates the presence of a station sending globalto global data data. Stations 01 to 64%IWp.1.5

%IWp.1.6 Availability Byte 0 = the specific inputs of all remote stations areof status bits available

x0 = 0 the specific inputs are not availablex0 = 1 the specific inputs are available

state of the byte 1 = a bit at 1 indicates the presence of a stationspecific inputs sending specific inputs. Stations 1 to 8

%IWp.1.7 state of the A bit at 1 indicates the presence of a stationto specific inputs sending specific inputs. Stations 9 to 56%IWp.1.9

%IWp.1.10 state of the byte 0 = a bit at 1 indicates the presence of a stationspecific inputs sending specific inputs. Stations 57 to 64

presence of new byte 1 = a bit at 1 indicates the presence of newspecific inputs specific inputs. Stations 1 to 8

%IWp.1.11 presence of new A bit at 1 indicates the presence of new specificto specific inputs inputs. Stations 9 to 56%IWp.1.13

%IWp.1.14 presence of new byte 0 = a bit at 1 indicates the presence of newspecific inputs specific inputs. Stations 57 to 64

byte 1 = not used

%IWp.1.15 Availability Byte 0 = the specific outputs of all remote stations areof status bits available

x0 = 0 the specific outputs are not availablex0 = 1 the specific outputs are available

state of the byte 1 = a bit at 1 indicates the presence of a stationspecific outputs receiving specific outputs. Stations 1 to 8

%IWp.1.16 state of the A bit at 1 indicates the presence of a stationto specific outputs receiving specific outputs. Stations 9 to 56%IWp.1.18

%IWp.1.19 state of the byte 0 = a bit at 1 indicates the presence of a stationspecific outputs receiving specific outputs. Stations 57 to 64

byte 1 = not used

___________________________________________________________________________1

FIPIO Contents

Section Page

H

1 FIPIO bus 1/1


1.2 Inter-station communication to the FIPIO network 1/2

1.3 Device address 1/41.3-1 General 1/41.3-2 Features specific to certain connected devices 1/41.3-3 Topological addressing 1/61.3-4 Maximum configuration 1/7

1.4 Configuration mode 1/101.4-1 Creating an application in offline mode 1/101.4-2 Modifying, deleting a configured device 1/151.4-3 Moving a device 1/171.4-4 Copying a device 1/18

1.5 Language interface 1/191.5-1 Diagnostics of device faults by PL7 1/201.5-2 Channel fault diagnostics 1/221.5-3 System bits and words relating to I/O faults on the

FIPIO bus 1/231.5-4 FIPIO bus command system words 1/261.5-5 Fault detection algorithm 1/30

1.6 FIPIO bus operating mode 1/31

___________________________________________________________________________

2

FIPIO Contents

Section Page

H

1.7 Limitations of explicit exchanges on the FIPIO bus 1/331.7-1 Example of hardware configuration 1/341.7-2 Examples of explicit exchange overflow detection 1/34

1.8 Managing the I/O on the FIPIO bus using PL7 tasks 1/371.8-1 Cyclic task 1/381.8-2 Periodic task 1/381.8-3 Confirming the configuration 1/391.8-4 Examples of confirmation refusal 1/40

1.9 Debug mode 1/421.9-1 General 1/421.9-2 Common part of the application-specific screens in

debug mode 1/43

1.10 FIPIO bus communication diagnostics in online mode 1/441.10-1 General 1/441.10-2 Sequence of the diagnostic screens of a FIPIO application 1/451.10-3 Monitoring the FIPIO bus 1/461.10-4 Device monitoring 1/471.10-5 Monitoring the communication of one device 1/491.10-6 Communication error log 1/50

1.11 Managing the FIPIO bus 1/521.11-1 FIPIO bus properties 1/521.11-2 Network cycle time 1/55

1.12 Visual diagnostics of the FIPIO connection on the processor 1/59

___________________________________________________________________________3

FIPIO Contents

Section Page

H

2 Standard profiles 2/1

2.1 General 2/1

2.2 Volume of data exchanged 2/1

2.3 Accessing a standard profile 2/22.3-1 Choosing a standard profile 2/22.3-2 List of standard profiles supported by PL7 : 2/32.3-3 Special feature of the FSD C8 P and FSD M8 P profiles 2/42.3-4 Accessing a standard profile with PL7 2/52.3-5 Accessing a standard profile in the Momentum family 2/6

2.4 Language objects 2/72.4-1 Reminder on addressing language objects 2/72.4-2 Implicit exchange language objects 2/72.4-3 Explicit exchange language objects 2/8

2.5 Using a standard profile 2/122.5-1 Configuration mode 2/122.5-2 Adjust mode 2/14

2.6 Debug mode 2/152.6-1 Common part of the application-specific screens in

debug mode 2/152.6-2 Functions available in online mode 2/16

___________________________________________________________________________

4

FIPIO Contents

Section Page

H

3 FIPIO Agent 3/1

3.1 Introduction : FIPIO Agent 3/1

3.2 Configuration 3/13.2-1 Installation : the manager is a TSX 57, PCX 57, TPMX PLC 3/13.2-2 Installation : the manager is a TSX 47 - 107 (series 7) PLC 3/23.2-3 Installation : the manager is an APRIL 5000 PLC 3/23.2-4 Installation in PL7 Micro and PL7 Junior 3/3

3.3 Language objects 3/43.3-1 Dialog and configuration language objects 3/43.3-2 Data access : the manager is a Premium PLC 3/53.3-3 Data access : the manager is a Series 7 PLC 3/6

3.4 Addressing 3/7

3.5 Debug screen 3/8

FIPIO bus 1

___________________________________________________________________________H1/1

H

Section 11 FIPIO bus

1.1 Introduction

FIPIO is part of the WORLDFIP global offer from Schneider Automation.The FIPIO bus is used to connect 127 devices from the connection point integrated inthe processor.PL7 software and TSX P 57252 / 352 / 452, TPCX P 573512 and TPMX 57352 /452processors are used to configure and monitor the connected devices. These devicesmay be FIPIO agent PLCs, discrete or analog TBXs, discrete or analog Momentum,CCX 17, ATV16/58/66, TBX SAP10 AS-i gateway, devices which conform to FIPIOstandard profiles or PCs.The FIPIO bus connects to Hirschmann fiber optic transceivers. This means thatmedium redundancy architectures can be created and clusters of devices can belocated remotely on an optical FIPIO segment. Architectures and special conditionsrelating to configuration are presented in the installation documentation for thesedevices.Please refer to the documentation for each connected device for information oninstallation.

H1/2___________________________________________________________________________

H

1.2 Inter-station communication to the FIPIO network

Inter-station communication to FIPIO is only available if the bus arbitrator is a TSX PLC≥ V3.3, and the TSX Premium PLCs are connected as slaves. There is no communicationto a TSX 37 PLC. The higher level network may be Fipway, Ethernet etc.

63

Magelis

TSX 57 ≥ V3.3

TSX 57 ≥ V3.3

TSX 37

0

FIP

IO

FIPWAY / ETHERNET ETC.

Third party

FIPIO bus 1

___________________________________________________________________________H1/3

H

If the configuration is not the same as the above configuration, requests are not routeddirectly.

i If there is a terminal in the configuration, it must be connected at the defaultconnection point (63).

i For any other device, the sending station must address the master PLC and not thedestination device.It is the master PLC application which transfers requests to the destinationdevice .

Example :

In the following example, an exchange is to be performed from the FIPIO bus to theUNI-TELWAY bus. For a transfer in the opposite direction, the procedure is identical.

i Step 1

The sending station, connected at connection point 6 on FIPIO, transmits the requestto the master PLC. The destination address is the address of the master PLC.

WRITE_VAR ( ADR#\6.1.0\SYS, %MW,0,10, %MW:10, %MW100:4)

The report is provided by the master PLC.

i Step 2

When the master PLC application receives the request from the sending station, itdirects it to the destination device using the UNI-TELWAY protocol.

WRITE_VAR (ADR#0.0.1, '%MW', 100, 10, %MW10:10, %MW40:4)

The report is sent to the master PLC.

Step 1

6

0

TSX Premium Master

Step 2

Ad0 = 1Ad1 = 2Ad2 = 3

UNI_TELWAY

FIPIO

63

H1/4___________________________________________________________________________

H

1.3 Device address

1.3-1 General

Processors with an integrated FIPIO link can manage 128 connection points on the bus.FIPIO addresses are numbered from 0 to 127. The TSX Premium is connected ataddress 0. It can manage up to 126 remote devices. Address 63 is reserved for theprogramming and diagnostics terminal.Warning : maximum configurations depend on the type of device connected on the bus.

1.3-2 Features specific to certain connected devices

TBX devices : the device connected to a connection point, if it is modular, must behomogenous at the application-specific function level : discrete base unit and extensionor analog base unit and extension.The device must only be controlled by a single task (FAST or MAST) in PL7 : groupsof channels in the same TBX cannot be assigned to different tasks.

Momentum : the use of Momentum devices is only possible on FIPIO with thecommunication module : 170 FNT 110 01.

Programming terminal at privileged address 63 : a programming terminal equippedwith a TSX FPC 10 card or TSX FPP 20 PCMCIA card must be connected at FIPIOaddress 63. PL7 operates in online mode with the FIPIO manager PLC if the managerPLC has an application in which one or more agent devices are configured :• PL7 communicating with FIPIO agent Micro / Premium PLCs,

• MMI 17 communicating with CCX-17 terminals.

It is not possible to download a PL7 application to the manager from a programmingterminal at address 63. However, it is possible to download a PL7 application to a FIPIOagent PLC.

Limitation specific to the connected device : some devices in the catalog have alimited FIPIO addressing range. The device does not support all the possible addresses.

Message handling : on a FIPIO bus, up to 20 128-byte messages can be exchangedbetween all stations, including the programming terminal at connection point 63.

FIPIO bus 1

___________________________________________________________________________H1/5

H

Summary :

Type of device FIPIO addresses Comments

Compact TBXs 1...31 TBX C...

Dust and damp proof TBXs 1...62, 64...127 TBX E ...

Modular TBXs 1...62, 64...127 TBX LEP 020, TBX LEP 030

Momentum 1...62, 64...99 170 FNT 110 01 communicator only

ATV 16, ATV 66 1...62 PCMCIA : TSX FPP10 version V1.8 minimum

ATV58 1...62

CCX-17 1...62 version ≥ V2.4 onlyPCMCIA : TSX FPP10 version V1.8 minimum

TBX SAP 10 1...62, 64...127 AS-i gateway

TSX 37/57 1...62 PCMCIA : TSX FPP10 version V1.8 minimum

Programming terminal 63

FIP-connect products 1...62, 64...127 exc. limitation : see product documentation

Magelis 1...62 PCMCIA : TSX FPP10 version V1.8 minimum

H1/6___________________________________________________________________________

H

0

1

FIPIO

1.3-3 Topological addressing

A PL7 language object belonging to a remote FIPIO device is addressed by indicating :• the type of object : %I, %Q, %IW, %QW, %MW, %KW,

• the slot in the rack for the processor with the FIPIO integrated link : always 0 or 1according to the type of power supply selected,

• the number of the integrated FIPIO channel : always 2,

• the number of the connection point for the remote device (this is its FIP address),

• the number of the module in the device : 0 for the base, 1 for the extension (always0 if the device is compact),

• the number of the channel in the module.

TBX example :

Discrete input

%I\0.2.1\0.2

discrete channel no.module no.connection point no.channel no.processor slot no.

Discrete output

%Q\0.2.1\0.8

FIPIO bus 1

___________________________________________________________________________H1/7

H

1.3-4 Maximum configuration

Processors with an integrated FIPIO link have a RAM memory which is used to storethe configuration of the devices connected on the bus. This memory has a capacity of94320 bytes. Each device family occupies a different number of bytes. Duringconfiguration, the maximum number of bytes occupied by the application must becalculated by adding together the number of bytes occupied by all the devices andcomparing the result with the maximum value 94320. The values in the table below areexpressed in bytes.In one configuration, the number of modules with the same reference which can beconnected on the FIPIO bus is limited.

Size occupied by : Maximum no. of modules

Family Module base extension with the same reference

ATV-16 All references 1952 48

ATV-58 All references 1808 52

CCX-17 All references 1952 4

CCX-17-32 All references 2448 4

Magelis All references 1424 66

Gateway TBX SAP 10 1808 52

TSX TSX 37 1424 66

TSX 57 1424 66

Momentum 170 ADI 340 00 832 98

170 ADI 350 00 832 98

170 ADI 540 50 832 98

170 ADM 350 10 832 98

170 ADM 350 11 832 98

170 ADM 370 10 832 98

170 ADM 390 10 832 98

170 ADM 390 30 832 98

170 ADM 690 50 832 98

170 ADO 340 00 832 98

170 ADO 350 00 832 98

170 ADO 530 50 832 98

170 ADO540 50 832 98

170 ADO730 50 832 98

170 ADO740 50 832 98

H1/8___________________________________________________________________________

H

Maximum configuration : continuation of table from the previous page



Momentum 170 AAI 030 00 1808 52

(cont.) 170 AAI 140 00 2304 40

170 AAI 520 40 2304 52

170 AAO 120 00 1808 52

170 AAO 921 00 1808 52

170 AEC 920 00 1808 52

170 AMM 090 00 1808 52

Other FED 1280 73

Other FED_P 2304 40

Other FRD 832 98

Other FRD_P 1744 50

Other FSD 896 98

Other FSD_P 1808 52

TBX AES 200 1332 272 70 x 2 or 4-channel modules

ASS 400 1332 272 59 x 8-channel modules

AMS 620 1584 528 50 x 10 or 12-channel modules

CEP 1622 1152 31

CSP 1622 1152 31

CSP 1625 1152 31

EEP 08C22 1152 81

EEP 1622 1152 81

ESP 08C22 1152 81

ESP 1622 1152 81

FIPIO bus 1

___________________________________________________________________________H1/9

H

Maximum configuration : continuation of tables from the previous pages



TBX DES 1622 1152 144

(cont.) DES 1633 1152 144

DES 16C22 1152 144

DES 16F22 1152 144

DES 16S04 1152 144 81 x 16-channel modules

DMS 1025 1152 144

DMS 1625 1152 144

DMS 16C22 1152 144 72 x 32-channel modules

DMS 16C222 1152 144

DMS 16P22 1152 144

DMS 16S44 1152 144

DSS 1622 1152 144

DSS 1625 1152 144

DSS 16C22 1152 144

DSS 1235 1152 144

STD_P FRD C2 832 113

FRD C2 P 1744 54

FSD C8 896 105

FSD C8P 1808 52

FSD M8 1040 90

FSD M8P 1952 48

FED C32 1280 73

FED C32P 2304 40

FED M32 1424 66

FED M32P 2448 38

When configuring the device hardware, the user must calculate the total consumptionin bytes of processor memory, and ensure that the maximum number of identicalmodules on the bus is not exceeded.

H1/10___________________________________________________________________________

H


1.4-1 Creating an application in offline mode

After selecting the File / New command from the menu bar, select the processor requiredfor the new device :

The following processors are equipped with an integrated FIPIO link : TSX P 57252 /57352 / 57452, TPMX P57352 / 452, or TPCX P573512. Confirming this window opensan Application Browser window. Selecting "Hardware configuration" accesses ascreen displaying a configuration with the FIPIO bus connection integrated in theprocessor. Opening an existing application takes you directly to the browser.

FIPIO bus 1

___________________________________________________________________________H1/11

H

Double-click on the representation of the FIPIO connector on the processor. A windowopens showing by default the minimum structure required for the FIPIO bus. The grayedrectangles on the bus indicate the two reserved addresses : 0 for the bus manager, and63 for the privileged terminal. A small circle indicates the connection points available.A scale indicator is used to set the length of the FIPIO bus. The default value is 1km.The adjustment increment is 1 km. This length must be set as it is used for propagationtimes of signals on the bus, and therefore in the calculation of network cycle times bythe processor.

Warning : Each time the length of the FIPIO bus is modified, all the connecteddevices must be powered off then powered on after the new application has beendownloaded (to the PLC).

H1/12___________________________________________________________________________

H

Double-click on a small circle representing a connection point to open the "Add / Modifya Device" window. This window lists the catalog of devices which can be connectedto the selected connection point. Select an element in the "Families" window, then abase module. The "Communicator" window opens if the FIPIO bus communicator is notintegrated in the selected module or if one must be selected. Select an extensionmodule as required. The connection point number for the device to be configuredshould be entered in this window.It is also possible to add a comment (80 characters maximum) relating to the deviceconnected to the connection point.

FIPIO bus 1

___________________________________________________________________________H1/13

H

After confirmation, the device setup at the selected connection point will be displayedin the FIPIO configuration window for each connection point. The representation of theapplication in this window is a logical representation in ascending order of connectionpoint numbers. Repeat the procedure for each point. The order of entry for the pointsis irrelevant.

Example :

H1/14___________________________________________________________________________

H

When a device has been declared, click on the module to be able to access itsconfiguration in the same way as for an in-rack module. This screen is used to selectthe task enabling I/O exchanges : FAST or MAST, and to modify the configuration oradjustment parameters specific to the module. This screen is identical to the one forin-rack modules (see the documentation relating to the discrete function or thedocumentation specific to the module being configured).

Example of a configuration screen for a discrete mixed I/O module :screen corresponding to the module inputs

screen corresponding to the module inputs

The symbol associated with each I/O bit is shown in the window and is defined in theI/O variables function in the Application Browser.

FIPIO bus 1

___________________________________________________________________________H1/15

H

1.4-2 Modifying, deleting a configured device

After selecting a connection point in the configuration window, select "Modify Device"in the Edit menu or double-click with the left mouse button on a configured connectionpoint. The same screen as for adding a device appears, initialized with the elementsof the current device. It is not possible to change the family of the configured device orthe connection point number. It is possible to modify the device components : the basemodule, the communicator, the comment and, for TBXs, the extension module.

H1/16___________________________________________________________________________

H

"Delete Device" :In offline mode, select a configured connection point. Selecting the "Edit" menu orpressing the "DEL" key after user confirmation removes the connection point from theFIPIO configuration screen.

FIPIO bus 1

___________________________________________________________________________H1/17

H

1.4-3 Moving a device

Moving a device does not correspond to physically moving it on the bus but to logicallychanging the device address. This modifies the address of the I/O objects in the programand moves the variables associated with these objects. The application program willbe modified accordingly on a global confirmation of the configuration. The connectionpoint to be moved must be selected.Using the "Edit / Move a Device" menu :A window opens displaying the current address. Enter the destination address.Confirmation of this window launches a check by PL7 to ensure that the destinationaddress is empty and that the source device is authorized at the destination address.

Using the mouse :Click on the connection point to be moved, hold the mouse button down and drag it toa free connection point. When the mouse button is released, a window opens to enterthe address of the destination connection point.In both cases, the configuration screen is updated, the device is positioned in the correctlocation in ascending order of addresses and the new address is displayed.

H1/18___________________________________________________________________________

H

1.4-4 Copying a device

This function is similar to the function for moving a device. Select a connection pointto be copied. The "Edit / Copy Device" function is used to enter the address of theconnection point for the copied device. The device at the old address is not modified.Using the mouse : holding the "CTRL" key down, click on the left mouse button, holdit down and drag it to a free connection point. When the mouse button is released, awindow opens to enter the address of the new device. The new device contains thesame modules with the same parameters as those which already exist. The configurationscreen is updated, the device is positioned in the correct location in ascending orderof addresses and the new address is displayed.

FIPIO bus 1

___________________________________________________________________________H1/19

H


The various language objects associated with the management of the FIPIO bus aregiven in the table below. They are in addition to the language objects which are commonto all devices.Reminder of instructions :The WRITE_CMD instruction is used to write command words

• WRITE_CMD %CH\p.2.c\m.v

The READ_STS instruction is used to update diagnostic words %MW...• READ_STS %CH\p.2.c\m.v

Read channel adjustment parameters• READ_PARAM %CH\p.2.c\m.v

Write channel adjustment parameters• WRITE_PARAM %CH\p.2.c\m.v

Save and restore adjustment parameters• SAVE_PARAM %CH\p.2.c\m.v• RESTORE_PARAM %CH\p.2.c\m.v


%I\p.2.c\m.v bit exchange I reading discrete inputs (bit)

%IW\p.2.c\m.v word exchange I reading inputs (word)

%Q\p.2.c\m.v bit exchange I controlling discrete outputs (bit)

%QW\p.2.c\m.v word exchange I controlling outputs (word)

%I\p.2.c\0.MOD.ERR module fault I =1 module faulty

%I\p.2.c\m.v.ERR channel fault I =1 channel faulty

%MW\p.2.c\0.MOD.2 module status E low order byte = base diagnosticshigh order byte = extension diagnostics

%MW\p.2.c\m.v.2 channel status E m = 0 diagnostic byte for base channels

m = 1 diagnostic byte for extension channels

I = implicit exchange, E = explicit exchangep = processor slot (0 or 1), c = connection point number, m = 0 for a base module, m=1for an extension module, v = channel numberThe PLC system implicitly updates the input objects and copies the output objects tothe remote module (%I, %IW or %Q, %QW).

The status, command and adjustment parameters are exchanged on request by theuser program. These are explicit exchange objects. PL7 instructions are used in thesame way as in-rack I/O objects.

H1/20___________________________________________________________________________

H

1.5-1 Diagnostics of device faults by PL7

%I\p.2.c\0.MOD.ERR : this error bit is managed implicitly by the processor in alloperating modes. Normally at 0, it is at 1 if there is a connection point fault. %MW\p.2.c\0.MOD.2 : this word is updated explicitly by the READ_ STS instruction.Bits 0 to 7 (low order bytes) indicate the status of the base module. Bits 8 to 15 (highorder bytes) indicate the status of the extension module.• READ_STS %CH\p.2.c\0.MOD updates the module status in

%MW\p.2.c\0.MOD.2

The module status word read by the processor is dependent on the device connectedon the bus. Its generic meaning is :

%I\p.2.c\0.MOD.ERR Module fault = 1 module faulty

%MW\p.2.c\0.MOD.2 Module status base : low order bytex0 : internal faultx1 : operating faultx2 : terminal block faultx3 : base module running self-testsx4 : reserved at 0x5 : configuration faultx6 : module missingx7 : extension module faultextension : high order bytex8 : internal faultx9 : operating faultx10: terminal block faultx11: extension module running self-testsx12 : reserved at 0x13 : configuration faultx14: module missingx15: reserved at 0

For each connected device, refer to the relevant documentation for details on theapplication-specific status words used.

FIPIO bus 1

___________________________________________________________________________H1/21

H

Example of a diagnostic word at module level for a discrete TBX device :

%I\p.2.c\0.MOD.ERR Module fault = 1 module faulty

%MW\p.2.c\0.MOD.2 Module status base : low order bytex0 : base module failurex1 : operating faultx2 : terminal block faultx3 : base module running self-testsx4 : reserved at 0x5 : base present but not the same as

the one configuredx6 : base configured but missingx7 : extension module faultextension : high order bytex8 : extension module failurex9 : operating faultx10: terminal block faultx11: extension module running self-testsx12 : reserved at 0x13 : extension present but not the same as

the one configuredx14: extension configured but missingx15: reserved at 0

H1/22___________________________________________________________________________

H

1.5-2 Channel fault diagnostics

Channel diagnostics :%I\p.2.c\m.v.ERR : this bit is managed implicitly by the processor in all operating modes.Normally at 0, it is at 1 if there is a connection point fault.

Definition :

A group of physical channels is seen by the user program as a logical channel. Alogical channel uses physical resources. It can group several physical channels.THE I/O CHANNEL MANIPULATED BY THE USER IS ALWAYS A LOGICALCHANNEL.

The language interface for channel faults on a FIPIO bus is as follows :%I\p.2.c\0.v.ERR : for base module channels,%I\p.2.c\1.v.ERR : for extension module channels.

The READ_STS %CH\p.2.c\0.v and READ_STS %CH\p.2.c\1.v instructions update thechannel status words %MW...

Generic meaning of channel level diagnostic word :

%I\p.2.c\0.v.ERR Channel fault =1 if channel faulty%I\p.2.c\1.v.ERR

%MW\p.2.c\0.v.2 Channel x0 : external fault 4%MW\p.2.c\1.v.2 status x1 : external fault 3

x2 : external fault 2x3 : external fault 1x4 : internal faultx5 : hardware configuration faultx6 : communication errorx7 : application fault

Example of a diagnostic word at channel level for a discrete TBX device

%MW\p.2.c\0.v.2 Channel x0 : output tripped%MW\p.2.c\1.v.2 status x1 : global tripping

x2 : terminal block faultx3 : external power supply faultx4 : channel configured but not physically presentx5 : channel present but not the same as the one

configuredx6 : communication errorx7 : application fault

For each connected device, refer to the relevant documentation for details on theapplication-specific status words used.Device diagnostics is available in PL7 debug mode.

FIPIO bus 1

___________________________________________________________________________H1/23

H

1.5-3 System bits and words relating to I/O faults on the FIPIO bus

Reminder of the system bits and words used in PL7 which are specific to or havemeaning in FIPIO bus installation :

System bits :

%S9 : switch to output fallback stateNormally at 0, this bit is set to 1 by the user, via the program or the programming terminal.It switches the outputs on Bus X and the FIPIO bus to fallback state.

%S10 : general I/O faultThis bit indicates a global I/O fault.Normally at 1, this bit is set to 0 by the system when a fault occurs on a Bus X moduleor on a FIPIO device. When the fault disappears this bit is reset to 1 by the system.

%S16 : task I/O faultNormally at 1, this bit is set to 0 by the system when a fault occurs on a Bus X moduleor on a FIPIO device. This bit must be reset to 1 by the user. Bit %S16 is assigned toeach of the tasks in which it is tested. Therefore, it is only significant for the task in whichit is tested.

%S118 : general FIPIO I/O faultNormally at 1, this bit is set to 0 by the system when a fault occurs on a device connectedon the FIPIO bus. When the fault disappears this bit is reset to 1 by the system.

%S119 : Bus X I/O faultNormally at 1, this bit is set to 0 by the system when a fault occurs on a device connectedon Bus X. When the fault disappears this bit is reset to 1 by the system.

H1/24___________________________________________________________________________

H

System words :

%SW8 : control of reading of inputs for each taskNormally at 0, these bits are set to 1 by the user, via the program or the programmingterminal.%SW8 :

x0 = 1 assigned to the MAST task : the inputs relating to this task are no longerupdated in the application memory

x1 = 1 assigned to the FAST task : the inputs relating to this task are no longerupdated in the application memory

%SW9 : control of reading of outputs for each taskNormally at 0, these bits are set to 1 by the user program or by the programming terminal.%SW9 :

x0 = 1 assigned to the MAST task : the outputs relating to this task are no longercontrolled

x1 = 1 assigned to the FAST task : the outputs relating to this task are no longercontrolled

Warning : the outputs of modules connected on Bus X are automatically switchedto fallback mode. The outputs of devices connected on the FIPIO bus are maintainedin the state which preceded the bit being set to 1.

%SW 116 : FIPIO I/O fault in the taskNormally at 0, each bit of this word represents a FIPIO exchange state in the task inwhich it is tested.This word is reset to 0 by the user.%SW 116 :

x0 = 1 explicit exchange error (the variable is not exchanged on the bus),x1 = 1 time-out on an explicit exchange (no response at the end of the time-out),x2 = 1 maximum number of simultaneous explicit exchanges,x3 = 1 a frame is not correct,x4 = 1 the length of a received frame is greater than the declared length,x5 = reserved at 0,x6 = 1 a frame is invalid, or an agent is being initialized,x7 = 1 configured device missing,x8 = 1 channel fault (at least one channel is indicating an error),x9 = reserved at 0,tox14 = reserved at 0,x15 = reserved at 0.

FIPIO bus 1

___________________________________________________________________________H1/25

H

%SW128 to %SW143 : FIPIO device connection point faultEach bit in this group of words indicates the status of a device connected on the FIPIObus.Normally at 1, if one of these bits is at 0 a fault has occurred on this connection point.For a non-configured connection point, the corresponding bit is always at 1.Table of correspondence between word bits and a connection point address.

x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 x10 x11 x12 x13 x14 x15

%SW128 : 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

%SW129 : 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

%SW130 : 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47

%SW131 : 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63

%SW132 : 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79

%SW133 : 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95

%SW134 : 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111

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

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

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

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

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

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

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

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

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

H1/26___________________________________________________________________________

H

1.5-4 FIPIO bus command system words

%SW144 :Warning : modifying this system word may stop the PLC station.This system word is used to stop and start the bus arbitrator function and the producer /consumer function. It is used to modify the automatic and manual start-up modes forthe bus in the event of a stop.%SW144 :

x0 = 1 producer / consumer function in RUNx0 = 0 producer / consumer function in STOP (no variables are exchanged

on the bus),x1 = 1 the bus arbitrator is in RUNx1 = 0 the bus arbitrator is in STOP (no scanning of variables and messages

on the bus),x2 = 1 automatic start if the bus has stopped automaticallyx2 = 0 manual start if the bus has stopped manuallyx3 = reserved at 1x4 to x15 reserved at 0.

Note : this system word is handled every second. If the user wishes to know when theoperation will be taken into account by the system, he must display the %SW146 systemword which gives the state of the bus arbitrator and producer / consumer functions.

%SW145 :Warning : modifying this system word may stop the PLC station.Modifying the FIPIO bus arbitrator parametersThe bits are set to 1 by the user and reset to 0 by the system when initialization has beencompleted.%SW145 :

x0 = 1 modification of bus arbitrator priority : The high order byte of thissystem word contains the value of the bus arbitrator priority which will beapplied on the bus.

x1 = 1 modification of the slot time value (Tr) : The high order byte of this systemword contains the slot time value Tr (in µs) which will be applied on thebus. The system word is reset to 0 when initialization has been completed.

x2 = 1 modification of the silence time value (T0) : The high order byte of thissystem word contains the silence time value T0 (in µs) which will be appliedon the bus. The system word is reset to 0 when initialization has beencompleted.

x3 to x7 reserved at 0,x8 = 1 value of bus arbitrator priority,x9 = 1 value of Tr,x10 = 1 value of T0.

These parameters can be modified when the bus arbitrator is in RUN, but theapplication must be stopped and then restarted for the modifications to be taken intoaccount.

FIPIO bus 1

___________________________________________________________________________H1/27

H

FIPIO bus command system words (cont.)

%SW146 :Displaying the bus arbitrator and producer / consumer functions on the FIPIO bus.The low order byte indicates the state of the producer / consumer function.The high order byte indicates the state of the bus arbitrator function.Byte value :

16#00 : The function does not exist (no FIPIO application).16#07 : The function is in STOP (the STOP command has been sent, the

command has not been terminated).16#0F : The function is in RUN (the RUN command has been sent, the

command has not been terminated).16#70 : The function has been initialized but is not operational (in STOP).16#F0 : The function is being executed normally (in RUN).

The network cycle times given here are described in section 1.7 of this part.

%SW147 :Value of MAST task network cycle time.A value not equal to 0 indicates, in ms, the value of the network cycle time (NCT-MAST)for the MAST task.

%SW148 :Value of FAST task network cycle time.A value not equal to 0 indicates, in ms, the network cycle time (NCT-FAST) for the FASTtask.

%SW149 :Reserved at 0.

%SW150 :This word shows the number of frames transmitted by the FIPIO channel manager.

%SW151 :This word shows the number of frames received by the FIPIO channel manager.

%SW152 :This word shows the number of message retries attempted by the FIPIO channelmanager.

H1/28___________________________________________________________________________

H

%SW153 and %SW154 : list of FIPIO channel manager faults. Each bit is set to 1 bythe system and reset to 0 by the user.%SW153 :

X0 = station overrun fault : corresponds to the loss of a MAC symbolon reception, caused by the receiver reacting too slowly.

X1 = message refusal fault : indicates a message with acknowledg-ment refused or no acknowledgment.

X2 = interrupt variable refusal fault : indicates an overflow of the stackof interrupt variable exchange requests. The bus arbitrator istemporarily incapable of memorizing or satisfying the request.

X3 = station underrun fault : corresponds to the inability of the stationto meet the network transmission speed.

X4 = physical layer fault : corresponds to a prolonged absence oftransmission at the physical layer level.

X5 = non echo fault : corresponds to a fault which indicates that thetransmitter is in the process of sending, with a transmission currentwithin the operating range, and there is no signal on the samechannel.

X6 = chatter fault : corresponds to a fault which indicates that thetransmitter has been in control of the line for longer than themaximum defined operating limit. This fault can be caused bymodulator deterioration or by a defective data link layer.

X7 = hypocurrent fault : corresponds to a fault which indicates that thetransmitter, when solicited, produces a current on the line belowthe minimum defined operating limit. This fault can be caused byincreased line impedance, for example (open line, etc).

X8 = pierced frame fault : indicates the reception of a silence in thebody of a frame after a start delimiter has been identified and beforean end delimiter has been identified. In normal operating condi-tions, a silence error appearsafter an end delimiter has beenidentified.

X9 = frame reception CRC fault : indicates a discrepancy between theCRC calculated on the frame normally received and the CRCcontained in this frame.

X10 = frame reception coding fault : indicates the reception of certainsymbols, belonging exclusively to the start and end delimitersequences, in the body of a frame.

X11 = received frame length fault : the number of bytes received for thebody of a frame is greater than 256 bytes.

FIPIO bus 1

___________________________________________________________________________H1/29

H

X12 = unknown frame type received : in the body of a frame, the first byteidentifies the type of frame link. A certain number of frame types aredefined in the link protocol of the WORLDFIP standard. Thepresence of any other code in a frame indicates an unknown frametype fault

X13 = truncated frame received : a frame fragment is characterized bythe recognition of a sequence of end delimiter symbols while thedestination station is waiting to receive a start delimiter.

X14 = not used , value not significantX15 = not used , value not significant

%SW154 :X0 = aperiodic sequence time out : indicates an overshoot of the

message or aperiodic variables window in an elementary cycle ofthe macro cycle.

X1 = message handling request refused : indicates a message stackoverflow, the bus arbitrator is temporarily incapable of memorizingor satisfying a request.

X2 = urgent update command refused : indicates an overflow of thestack of urgent aperiodic variable exchange requests, the busarbitrator is temporarily incapable of memorizing or satisfying arequest.

X3 = non-urgent update command refused : indicates an overflow ofthe stack of non-urgent aperiodic variable exchange requests, thebus arbitrator is temporarily incapable of memorizing or satisfyingthe request.

X4 = silence fault : the bus arbitrator has not detected any activity on thebus for a period longer than that stipulated in the WorldFipstandard.

X5 = network collision on transmission of identifier : indicates activityon the network during periods intended for silence. During the timebetween transmission and the wait for a response from the busarbitrator, there must be no activity on the bus. If the bus arbitratordetects any activity, it generates a collision fault (for example, ifseveral arbitrators are active simultaneously on the bus).

X6 = bus arbitrator overrun fault : indicates a conflict accessing thebus arbitrator station memory.

X7 = not used, value not significantX8 = reserved at 0toX15 = reserved at 0

%SW155 :Number of explicit exchanges currently being processed.

H1/30___________________________________________________________________________

H

1.5-5 Fault detection algorithm

Example of a fault detection and management algorithm on Bus X or FIPIO bus :

test bit %S10(general I/O fault)

%S10 = 0

yesfind faulty segment

(Bus X or FIPIObus)

FIPIO bus fault Bus X fault

%S118 = 0 %S119 = 0

yes yes

find faulty devicegroup %SW128

(cnx0..15)... %SW143(cnx240..255)

find faulty rack%S40 to %S47

find faulty deviceamong the 16

%SWi:x. or%I\p.2.c\0.MOD.ERR

= 1

READ_STS%CH\p.2.c\0.MOD

wait forpositioning of

%MW\p.2.c\0.MOD.2

devicediagnostics

channeldiagnostics

find faultychannel

%I\p.2.c\m.v.ERR = 1

READ_STS%CH\p.2.c\m.v

wait forpositioning of

%MW\p.2.c\m.v.2

find faulty module inthe rack

%I@ module.MOD.ERR=1

READ_STS%[email protected]

%[email protected]

READ_STS%CH\@module.channel

%[email protected]

channeldiagnostics

find faulty channel%[email protected]

= 1

modulediagnostics

FIPIO bus 1

___________________________________________________________________________H1/31

H

1.6 FIPIO bus operating mode

The FIPIO bus operating mode is linked to the processor operating mode and thephysical status of the bus. If the number of physical errors detected by the processorrepresents a danger to the normal operation of the devices connected on the bus, theprocessor will stop any bus activity. In this case, the connected devices apply thefallback values to the I/O.

Processor operating mode :

1- Cold restart of the processor with a FIPIO application : the bus is started automatically,the I/O are checked and controlled.

2- Loading a FIPIO application : the bus is started automatically, the I/O are checkedand controlled.

3- If the processor detects any serious physical errors, the FIPIO bus is stoppedautomatically. The connected devices apply the fallback values, and the processorno longer controls the I/O. Physical errors include disconnection of the lineterminator, disconnection of the FIPIO terminal block from the processor, etc.

4- Following an automatic stop (detection by the processor of serious errors) :• Bit %SW144:x2 is at 1, the processor periodically attempts a restart by trying to

check and control the I/O of the connected devices. This is automatic mode.• Bit %SW144:x2 is at 0, to restart the bus, user action via the program or

programming terminal is required. Set bits %SW144:x0 and %SW144:x1 to 1.This is manual mode.

5- Warm restart : the bus is restarted automatically if it was not stopped voluntarily byan action on system word %SW144 bits 0 and 1. The bus is set to the state whichpreceded the power break.

6- If %S0 = 1 the system words are initialized, and if the bus had been stopped it isrestarted.

By default the processor tries periodically to restart the FIPIO bus if it has stoppeditself (%SW144:x2 = 1).

If %SW144:x0 is set to 0 (via the programming terminal or the program) the producer/consumer function (PC) stops. No more variables or messages are exchanged on thebus.If %SW144:x1 is set to 0 (via the programming terminal or the program) the bus arbitratorfunction (BA) stops. No more variables or messages are scanned on the bus.

To deliberately stop FIPIO bus activity, bits 0 and 1 in system word %SW144 must beset to 0 simultaneously by the programming terminal or by the program.

H1/32___________________________________________________________________________

H

If the FIPIO bus is stopped without any deliberate action on system word %SW144, thisimplies that the processor has detected some physical errors which are preventing thenormal operation of the bus and the connected devices.In this case and only in this case , if bit %SW144:x2 is at 1 (automatic start) theprocessor will periodically and automatically try to restart exchanges on the bus.If bit %SW144 :x2 is at 0 following a bus stop due to the occurrence of physical errors,bits %SW144 x:0 and %SW144 x:1 must be reset to 1 via the program or theprogramming terminal to restart the FIPIO bus. In this case, the bus will restart if andonly if the physical error which caused the stop has disappeared .

Example : If bit %SW144 x:2 = 1 on disconnection / reconnection of the FIPIO terminalblock from / to the processor, the bus will be restarted automatically. The devices willbe checked again and will apply the program values.If bit %SW144 x:2 = 1 on disconnection / reconnection of the FIPIO terminal block from / tothe processor, the devices connected on the bus will not be checked and will not beable to apply the program values. The devices will be checked again if the user setsbits %SW144:x0 and %SW144:x1 to 1.

FIPIO bus 1

___________________________________________________________________________H1/33

H

1.7 Limitations of explicit exchanges on the FIPIO bus

TSX P57252/352/452, TPCX 573512, and TPMX 57352/452 processors are equippedwith the integrated FIPIO channel 2. A maximum of 24 explicit exchange functions canbe activated simultaneously.An exchange request addressed to a FIPIO device can take several scans in the MASTtask. It is therefore absolutely necessary that the user manage the exchangemanagement parameter words for every exchange of explicit variables, includingREAD_STS %CH@channel and READ_STS %[email protected] : The READ_STS service is immediate for exchanges on Bus X.System word %SW155 contains the number of explicit exchanges in progress. Bit%SW116 : x2 is set to 1 if the maximum number of explicit exchanges is reached orexceeded.If, for example, 24 functions are being processed simultaneously, or if 25 functions arelaunched in the same task scan, any new function or the 25th function will not beprocessed and will terminate with an error.However, in the case of a READ_STS exchange, the 25th exchange is not possible,the report will signal a communication error in word : %MW\p.2.c\m.v.2.For WRITE_CMD, READ_PARAM, WRITE_PARAM, RESTORE_PARAM exchanges,if an unsuccessful report is active in status word %MW\p.2.c\m.v.1, the fault hasprobably been caused by inadequate system resources.The user must repeat the request in the application.

The examples in this document are given in Structured Text language, but they can betranslated into all PL7 languages.They should only be taken into account if the PL7 application is in danger of activatingmore than 24 explicit functions simultaneously and if the user wishes to repeat a requestif there has been an explicit exchange overflow.

H1/34___________________________________________________________________________

H

1.7-1 Example of hardware configuration

Please refer to part A (General) of this manual for the meaning of the various statuswords used in the following examples.

1.7-2 Examples of explicit exchange overflow detection

- Management of READ_STS module :

IF (NOT (%MW\0.2.1\0.MOD :x0)) THEN (*no request in progress*)SET %M0; (*memorization of a request*)(*reset the bit indicating the explicit exchange overflow to 0*)%SW116 :=%SW116 AND 2#1111111111111011;READ_STS %CH\0.2.1\0.MOD;IF (%SW116 :x2) THEN

RESET %M0; (*repeat READ_STS, there has been an overflow*)(*%MW\0.2.1\0.MOD.2 :x1 signals an operating fault*)

END_IF;END_IF;

IF(%M0 AND NOT (%MW\0.2.1\0.MOD :x0)) THEN(*%MW\0.2.1\0.MOD.2 can be used*)RESET %M0;

END_IF;

FIPIO bus 1

___________________________________________________________________________H1/35

H

- Management of READ_STS channel :

IF (NOT (%MW\0.2.1\0.0.MOD :x0)) THEN (*no request in progress*)SET %M1; (*memorization of a request on channels 0 to 7*)(*reset the bit indicating the explicit exchange overflow to 0*)%SW116 :=%SW116 AND 2#1111111111111011;READ_STS %CH\0.2.1\0.0;IF (%SW116 :x2) THEN

RESET %M1; (*repeat READ_STS, there has been an overflow*)(*%MW\0.2.1\0.0.2 :x6 signals a communication error*)

END_IF;END_IF;

IF(%M1 AND NOT (%MW\0.2.1\0.0 :x0)) THEN(*%MW\0.2.1\0.0.2.MOD.can be used*)RESET %M1;

END_IF;

- READ_PARAM at connection point 02 :

IF (NOT (%MW\0.2.2\0.0 :x2)) THEN (*no request in progress*)SET %M2; (*memorization of a request on channels 0 to 7*)(*reset the bit indicating the explicit exchange overflow to 0*)%SW116 :=%SW116 AND 2#1111111111111011;READ_PARAM %CH\0.2.2\0.0; (*parameter request*)IF ((%MW\0.2.2\0.0.1 :x) AND (%SW116 :x2)) THEN

(*exchange refused*)RESET %M2; (*explicit exchange overflow*)

END_IF;END_IF;

IF(%M2 AND NOT (%MW\0.2.2\0.0 :x2)) THEN(*reading of parameters completed*)RESET %M2;

END_IF;

H1/36___________________________________________________________________________

H

- WRITE_PARAM at connection point 02 :

IF (NOT (%MW\0.2.2\0.0 :x2)) THEN (*no request in progress*)SET %M3; (*memorization of a request on channels 0 to 7*)(*reset the bit indicating the explicit exchange overflow to 0*)%SW116 :=%SW116 AND 2#1111111111111011;WRITE_PARAM %CH\0.2.2\0.0; (*transmission of parameters*)IF ((%MW\0.2.2\0.0.1 :x2) AND (%SW116 :x2)) THEN


END_IF;END_IF;

IF(%M3 AND NOT (%MW\0.2.2\0.0 :x2)) THEN(*end of parameter transmission*)RESET %M3;

END_IF;

The examples above can be applied to the SAVE_PARAM and RESTORE_PARAMfunctions.

- WRITE_CMD at connection point 02 :

IF (NOT (%MW\0.2.2\0.0 :x1)) THEN (*no request in progress*)SET %M3; (*memorization of a request on channels 0 to 7*)(*reset the bit indicating the explicit exchange overflow to 0*)%SW116 :=%SW116 AND 2#1111111111111011;WRITE_CMD %CH\0.2.2\0.0; (*transmission of commands*)IF ((%MW\0.2.2\0.0.1 :x1) AND (%SW116 :x2)) THEN


END_IF;END_IF;

IF(%M3 AND NOT (%MW\0.2.2\0.0 :x1)) THEN(*end of command transmission*)RESET %M3;

END_IF;

FIPIO bus 1

___________________________________________________________________________H1/37

H

1.8 Managing the I/O on the FIPIO bus using PL7 tasks

Definitions : The network cycle times corresponding to the management of the FIPIOI/O are defined as follows :NCT : "network cycle time" is the time taken to scan all the FIPIO I/O from the PL7configuration. The bus arbitrator scans all the configured FIPIO I/O. The NCT alsoincludes the exchange of data required to manage the bus and the windows dedicatedto message handling.NCT_Task : "task network cycle time" is the time taken to scan all the FIPIO I/Oassociated with a PL7 task.

There are two operating modes for tasks using the FIPIO I/O :Controlled mode : in this mode, the PLC task period (MAST or FAST) is greater thanor equal to the NCT_Task (network cycle time associated with a task). The system willupdate the I/O of all the devices on the FIPIO bus at least once during a task period.Free mode : in this mode, there are no limits on the task period. This can be less thanthe NCT_Task time. In this case, the task can be executed without updating the FIPIOremote I/O.

PL7 default screen :

H1/38___________________________________________________________________________

H

1.8-1 Cyclic task

If the PLC task is configured cyclicly (no period has been imposed by the processor)and uses the FIPIO I/O, the only mode supported by PL7 is free mode.

1.8-2 Periodic task

If the PLC task is in periodic mode, the duration of the period is defined by theconfiguration and the task uses the FIPIO I/O, free mode or controlled mode arepossible.

FIPIO bus 1

___________________________________________________________________________H1/39

H

1.8-3 Confirming the configuration

After the FIPIO bus configuration has been defined, it must be confirmed so that it canbe taken into account in the new application. PL7 then checks the limits related to thenew application. Help screens are available in the event of a failure.If the limits imposed are not respected, the FIPIO bus arbitrator variables scan table willnot be generated and a global window will appear.

The configuration remains unconfirmed (Bus X physical configuration and FIPIOphysical configuration) as long as the problem is not corrected by the user. Thisconfiguration cannot be transferred to the PLC.

The "Recommendations" button is used to enlarge the dialog box above to display thecauses of the refusal and the advice needed to correct the problem.

Important : Not all the information is displayed when the "Recommendations" windowis opened. The scroll bar must be used to view all the available information. For amultitask application (MAST task with FIPIO I/O and FAST task with FIPIO I/O), the"Recommendations" screen concerns the MAST and FAST tasks.

The characteristics of the configured task are displayed. If the limits for a task are notrespected, the cause of the failure and recommendations for correcting it complete thecharacteristics.Depending on the recommendations, the user has two options for correcting theconfiguration :1. Return to the Command Status screen and modify the parameter(s) :

free / controlled mode, period and/or watchdog2. Return to the FIPIO bus configuration screen and modify the distribution of the

devices configured in the faulty task.

H1/40___________________________________________________________________________

H

1.8-4 Examples of confirmation refusal

Periodic MAST or FAST task in controlled mode :The network cycle time is greater than the period.

Cyclic MAST task :The network cycle time is greater than the watchdog.

FIPIO bus 1

___________________________________________________________________________H1/41

H

MAST or FAST task in free modeThe network cycle time is greater than the watchdog.

H1/42___________________________________________________________________________

H

1.9 Debug mode

1.9-1 General

The "FIPIO configuration" screen is accessible in online mode.In online mode, if a device is faulty, the rectangle which displays its address on the busappears in red. This means that bit %I\p.2.c\0.mod.err = 1. When the rectangle whichdisplays the address of the processor is red, the FIPIO link is inactive.Double-clicking on a device module opens the application-specific screencorresponding to that module in debug mode. Only 4 application-specific screens canbe open at any one time.

When in debug mode and online, the following functions can be accessed by openingthe application-specific screen for a device :

• Displaying and modifying the module configuration parameters,

• Reading, writing and saving adjustment parameters,

• Reading, writing and forcing I/O,

• Reading aperiodic status data,

• Writing command words.

After the configuration or command parameter data has been entered, it is sent onceit has been confirmed.

In the application-specific screen of the selected module, the inaccessible zones aregrayed-out.Also, in this screen, the functions corresponding to the actions for constructing anapplication are not accessible. A message is displayed in the status bar of the windowindicating the reason why access is impossible. These functions are :

• Selecting an empty connection point,

• Adding a device,

• Modifying the modules of a device,

• Deleting a device,

• Moving a device,

• Copying a device.

FIPIO bus 1

___________________________________________________________________________H1/43

H

1.9-2 Common part of the application-specific screens in debug mode

The module debug screens comprise a common part relating to module diagnostics.Processing operations at channel level are different.Refer to the application-specific documentation of the selected module for informationabout the channels.

The RUN, ERR and IO LEDs are represented in the module zone, as they appear onthe module front panel.Module fault diagnostics are only available if the button is displayed in red. In normaloperation, this button is displayed in gray. Clicking on the DIAG... button will open amessage window indicating the cause(s) of the module fault in text form.

H1/44___________________________________________________________________________

H

1.10 FIPIO bus communication diagnostics in online mode

1.10-1 General

General diagnostics of bus errors and device faults can be performed in online mode.This is possible by using the screens available in PL7 or by means of the system bitsand words managed by the application software.Two modes are available : FIPIO bus monitoring, device monitoring with or without errorlog.Each configured connection point has a "report" variable (including connection points0 and 63). This variable contains the values of the communication and performancecounters.This variable contains :• Standard Worldfip activity counters numbered from 00h to 20h

• Standard Worldfip error counters numbered from 21h to 7Fh

• Manufacturer counters numbered from 80h to FFh; these are not standard Worldfipcounters.

The error counters change when there are communication errors on the FIPIO bus.Four types of screens are used to display the evolution of the various counters andtherefore of the communication errors :

• The "FIPIO Bus Monitoring" screen provides a global view of the FIPIO bus. It displaysthe communication errors for the whole of the bus.

• The "Device Monitoring" screen provides a summary for each connection point. Itcontains all the connection points and indicates the changes in the error countersfor each connection point.

• The "Device Monitoring at Connection Point X" screen shows all the counters andtheir changes at a given connection point.

• The "Communication Errors History" screen is a log of all the errors, making it possibleto keep a dated track of the changes in the error counters.

Only one of each type of screen can be opened (one per connection point for the thirdtype). If the user tries to open a screen which is already open, that screen appearsimmediately.The two last screens can only be opened if the "Device Monitoring" screen is open. Theyare closed automatically when this screen closes.Closing the "FIPIO Configuration" screen or changing to offline mode will cause allthese screens to close.When opening the 1st or 2nd screen, the "report" variables of all the connection pointsare read one by one. The counter values of each "report" variable are stored in orderto create a reference status.A "Reinitialize" menu is used to reinitialize the reference status and all the openscreens.

FIPIO bus 1

___________________________________________________________________________H1/45

H

Monitoring of the FIPIO bus by the application program :

In PL7, system words %SW150 and %SW151 indicate the number of frames transmittedand received by the channel manager. If these two counters stop, this indicates that theFIPIO channel manager function has stopped. The user is informed of this stop in onlinemode in the configuration screen by the background of connection point 0 changingto red.

1.10-2 Sequence of the diagnostic screens of a FIPIO application

Access to the diagnostic screens takes place by clicking on the background of the"FIPIO Configuration" screen.

Click on the background of the configuration screenor select via the Utilities menu

H1/46___________________________________________________________________________

H

1.10-3 Monitoring the FIPIO bus

This screen provides the user with a global view of the bus and indicates communicationerrors on the bus. The screen contains a list of all the communication error countersof the bus and indicates their changes.Each line contains :• an icon representing the status of the error counters. White indicates normal status,

red indicates a counter showing an error which has changed from the referencestatus. The reference status is the status which was valid at the time the screen wasopened.

• the number of the counter in hexadecimal format

• the name of the counter (as given by the WorldFip standard)

The variables are read cyclically (one per second). The time between two readings ofthe same variable is equal to : [number of configured devices + 2 (0 and 63)] in seconds.As soon as an error counter changes value in relation to its reference value, andwhatever the connection point, the icon of the counter changes to red.Example : Counter 21 changes to red. This means that at least one counter numbered21 of all the counters numbered 21 has changed.Reinitializing this screen involves reading the reference status, thus all the counterschange to white.

Click on the background of the configurationscreen or select the Utilities menu

FIPIO bus 1

___________________________________________________________________________H1/47

H

1.10-4 Device monitoring

These screens are used to access the monitoring for all the configured devices, thenfor one device at a specific connection point.

It is possible to open several screens corresponding to the configured connectionpoints (one for each connection point).

Click on the background of the configuration screen

Click with right mouse buttonon the line of the connection point

double-click

H1/48___________________________________________________________________________

H

The "Monitoring All Devices" screen contains a list of the configured connection points,as well as points 0 and 63.For each connection point there is :• an icon specifying whether the connection point needs to be monitored; this icon

changes to red if the connection point is faulty

• the number of the connection point, in decimal format.

A connection point is considered to be faulty if the value of at least one of its errorcounters has changed from the reference status. When the point is faulty, the icon isdisplayed in red.The icon to the left of the connection point can be checked or unchecked using themouse or the spacebar. A connection point whose icon has been checked will bemonitored. It is possible to monitor all (or none) of the connection points via the menu.As soon as an error counter for a connection point changes value (in relation to itsreference value), the connection point changes to red.The user can deactivate monitoring of a connection point by clicking on the icon v . Inthis case, the "report" variable for this connection point is no longer read and itsreference status is reinitialized. This reinitialization can modify the "FIPIO Bus Monitoring"screen if it is open.Clicking with the right mouse button on a connection point forces this connection pointto be monitored, and the "Monitoring Device at Connection Point X" screen can beopened via the menu or by pressing Return on a selected connection point.Deactivating monitoring of a connection point (X) closes the associated "MonitoringDevice at Connection Point X" screen, if it was open.

Reinitializing this screen involves reading the reference status and all the statesof the connection points change to white.

FIPIO bus 1

___________________________________________________________________________H1/49

H

1.10-5 Monitoring the communication of one device

This screen displays details of changes in all the counters for a given connection point.It contains three zones which correspond to each type of counter : activity, error,manufacturer. Each zone contains the list of counters.Each line contains :• an icon indicating the change in the counter from the reference status

- white : no change- green : change in the activity or manufacturer counters- red : change in the error counters (the current value is different from the referencestatus)

• the number of the counter in hexadecimal format,

• its reference value in hexadecimal format,

• its value during the previous read operation, in hexadecimal format,

• its current value in hexadecimal format,

• its name in accordance with the WorldFip standard, or "Counter not listed" for themanufacturer part.

Clicking with the right mouse button on the "Communication Error Log" screen displaysthe above screen. Reinitialization involves reading the reference status, and all thecounters change to white.

H1/50___________________________________________________________________________

H

1.10-6 Communication error log

This screen contains a list of the communication errors for the connection points (plus0 and 63) which are configured and declared as being monitored in the "MonitoringAll Devices" screen.Each time an error counter for a connection point changes, a line is added. The linecontains :

• the current date and time of the programming terminal,

• the number of the connection point in decimal format,

• the number of the error counter in hexadecimal format,

• the value of the counter in hexadecimal format,

• the name of the counter (in accordance with the WorldFip standard).

Clicking with the right mouse button on the background of the previous screen accessesthe functions available for managing error counter information :

Empty Log :This command, which is accessible if the "Suspend Log" function is enabled, is usedto delete all the lines from the screen.

Suspend / Resume Log :This command is used to stop and resume updating of the screen.

Sort :This function is used to sort all the lines of the log by :• date and time,

• connection point, date and time,

• counter, date and time.

Sorting is also activated by clicking on the column header.

FIPIO bus 1

___________________________________________________________________________H1/51

H

Stop Log Automatically :When this function is selected, it enables the log to stop when it has reached themaximum number of lines (4000 lines). The stop is indicated to the user by a message.When the function is not selected, and the maximum number is reached, any new linesadded will replace the first lines (revolving mode).

Copy :This function, which is only accessible if the log is suspended, copies the selected linesonto the clipboard in text format.

Reinitialize :This function is used to read the reference status of all the counters and to update thescreens. The lines in the log are then deleted.

H1/52___________________________________________________________________________

H

1.11 Managing the FIPIO bus

On a FIPIO bus, a single PLC authorizes I/O exchanges. This is the bus arbitrator. It isresponsible for managing access to the bus by each connected device. The list, theperiodic FIPIO I/O, the windows allocated to message handling and the aperiodic I/Oform the macrocycle. The constant scanning of this macrocycle is performed by the busarbitrator.

1.11-1 FIPIO bus properties

Double-clicking on the right-hand side of the bus configuration window opens up a"Properties of the FIPIO Bus" screen which is used to select the type of profile managedby the FIP or WORLDFIP manager. It is also possible to set the length of the bus.FIP / WORLDFIP : the default mode is FIP. This mode is compatible with all Schneiderproducts and those of their partners.Selecting WORLDFIP mode allows the FIPIO bus to operate in accordance withEN 50170.This mode can be used with the following restrictions :- no TSX FP ACC6 or TSX FP ACC8 repeaters,- TBX : TBX LEP 020 version 1.4 minimum,

TBX LEP 030 version 1.2 minimum,- PCMCIA TSX FPP 10 Version ≥1.8.

FIPIO bus 1

___________________________________________________________________________H1/53

H

The Expert tab is used to select automatic mode or manual mode.Automatic mode : This is the recommended mode, the parameters are calculatedbased on the bus data and the parameters of the configured devices. In this mode theparameters cannot be modified.

Manual mode : This is used to enter times T0 and TR and the Variables and Messagespassbands. It is mainly reserved for specific applications which require these valuesto be modified (example : use of Hirshmann transceivers).

T0 : silence time-out. This defines the maximum silence time permissible on the FIPIObus.TR : slot time. This is the minimum time between frames during which there must beno activity on the bus for normal operation.These times are expressed in µs.Aperiodic passband for messages : This is the flow of messages able to circulate onthe bus, expressed in Kbits / second.Aperiodic passband for variables : This is the flow of variables able to circulate onthe bus, expressed in Kbits / second.

H1/54___________________________________________________________________________

H

• The silence time-out T0 must be greater than the slot time TR and less than 255.

• The slot time TR must be greater than or equal to 1 and less than the silence time-out T0.

• The passbands must be between 1 and 200Kbits/s.

Warning : No check is performed in manual mode; modification of these parametersmay cause the devices connected on the bus to fail.Warning: Each time the T0 or TR parameters or the length of the bus is modified,the connected devices must be powered down then powered up after the newapplication has been downloaded (to the PLC).

Aperiodic passband :

The standard flow of exchanges on the FIPIO bus is 1 Mbits/s. On a FIPIO bus, thereare two types of exchange : exchanges of cyclic variables which are reserved forprocess data and exchanges of aperiodic variables which relate to the configurationof the connected devices, adjustment and message handling.The window is used to adjust the passband (and therefore the time) allocated to theaperiodic variables or to message handling.

The default values are the optimal values for the proper functioning of the system.A decrease or increase in the passband for the aperiodic exchanges (Variables andMessages) is intended to slow down or speed up the flow of configuration or adjustmentvariables which are able to circulate on the bus. The same applies in the case of adecrease or increase of the aperiodic passband for message handling.The parameters can be set from 1 to 200 Kbits/s.An increase in the aperiodic passband increases the network cycle time.

FIPIO bus 1

___________________________________________________________________________H1/55

H

1.11-2 Network cycle time

Two options are possible depending on the application configuration (for a 1km bus withdefault T0 and TR and passbands (automatic mode)) :

Single task applicationFor an application with all the devices configured in one task, the value of the tasknetwork cycle time (in milliseconds) is calculated using the following formula :

NCT_Task = 1.45 + Σ Σ Σ Σ Σ (K x number of devices from the same family)

The coefficient K is defined as follows :

Coefficient : K Family Devices

0.5 TBX Discrete

0.9 TBX Analog

0.4 Momentum Discrete

0.6 Momentum Analog

0.6 ATV-16 All

0.6 ATV-58 All

0.6 CCX-17 All

1.5 CCX-17-32 All

1.5 TSX .. A l l

0.6 AS-i gateway TSX SAP10

1.5 Magelis All

0.4 STD_P FRD

0.6 STD_P FSP

1.5 STD_P FED

Example :Application with all elements configured in the MAST task :10 discrete TBX modules11 analog TBX modules12 discrete Momentum modulesCalculation of the Mast task cycle time

NCT_MAST = 1.45 + ((0.5 x 10) + (0.9 x 11) + (0.4 x 12)) = 21.15

NCT_MAST = approx. 21 ms

H1/56___________________________________________________________________________

H

Multitask application :

For a multitask application with two periodic tasks, if the devices are configured in eachof the tasks, the network cycle time depends on the configuration of the different tasks.The cycle time values calculated using the algorithm below are maximum values. Theactual values are less than or equal to these values.

Periodic task and cyclic task :The configuration constraints must be respected :• Network cycle time of periodic task < task period• Network cycle time of cyclic task ≤ network cycle time of periodic task timeIt can be concluded that for one application, as the period of the task increases, the tasknetwork cycle time decreases.

Periodic task in free mode :The following constraint applies :The expression : Network cycle time < task periodis replaced by : Network cycle time < task watchdog

Algorithm for calculating network cycle times in multitasks :Preliminary definitions :Pmax = value of the longest period among the tasks (Mast or Fast)Pmin = value of the shortest period among the tasks (Mast or Fast)

Tmax = task with the period Pmax

Tmin = task with the period Pmin

Replace "Period" with "watchdog" if the task is in free or cyclic mode.

R = ratio between periodsR = Pmax / Pmin (the ratio R must be a whole number, it will be rounded up if necessary)

EN_Dev = equivalent number of connection pointsEN_Dev = (R x number of devices from the same family configured in Tmin

+ number of devices from the same family configured in Tmax )

NCT_Tmax : Network cycle time of task Tmax

NCT_Tmin : Network cycle time of task Tmin

Note :- if the period of the Mast task is greater than that of the Fast task :

Tmax = TMast and Tmin = TFast

- if the period of the Fast task is greater than that of the Mast task :Tmax = TFast and Tmin = TMast

FIPIO bus 1

___________________________________________________________________________H1/57

H

Algorithm :

NCT_Tmax = 1.5 + ΣΣΣΣΣ (K x number of devices in the same family)NCT_Tmin = NCT_Tmax / R

The coefficient K is defined as follows :

Coefficient : K Family Devices

0.5 TBX Discrete

0.9 TBX Analog

0.4 Momentum Discrete

0.6 Momentum Analog

0.6 ATV-16 All

0.6 ATV-58 All

0.6 CCX 17 All

1.5 CCX 17-32 All

1.5 TSX .. All

0.6 AS-i gateway TSX SAP 10

1.5 Magelis All

0.4 STD_P FRD

0.6 STD_P FSP

1.5 STD_P FED

Example :PLC configuration :40ms Mast task60ms Fast task

Devices connected on the bus :10 discrete TBX modules configured in the Mast task, 5 in the Fast task10 analog TBX modules configured in the Mast task, 5 in the Fast task6 discrete Momentum modules configured in the Mast task, 4 in the Fast task6 analog Momentum modules configured in the Mast task, 4 in the Fast task6 FED C32P configured in the Mast task, 4 in the Fast task

Mast period < Fast period, thus :Pmax = 50, Pmin = 20Tmax = TFast, Tmin = TMast

NCT_Tmax = NCT_TFast

NCT_Tmin = NCT_TMast

H1/58___________________________________________________________________________

H

1) calculation of ratio RR = Pmax / Pmin = 50 / 20 = 1.5 rounded up to 2

2) calculation of the equivalent number of devices EN_ Dev :EN_discrete_TBX = (R x 5 + 10) = 20EN_analog_TBX = (R x 5 + 10) = 20EN_discrete_Momentum = (R x 4 + 6) = 14EN_analog_Momentum = (R x 4 + 6) = 14EN_FED = (R x 4 + 6) = 14

3) calculation of network cycle time :NCT_TMast = 1.45 + Σ (K x EN_Dev)NCT_TMast = 1.45 + ((0.5 x 20) + (0.9 x 20) + (0.4 x 14) + (0.6 x 14) + (1.5 x 14))

= 64.5msNCT_TFast = (NCT_TMast / R) = 32ms rounded up to 32ms

Result =NCT_TMast = approx. 64msNCT_TFast = approx. 32ms

FIPIO bus 1

___________________________________________________________________________H1/59

H

1.12 Visual diagnostics of the FIPIO connection on the processor

The yellow FIP LED on the processor display block is used to diagnose the state of theFIPIO link.

FIP LED FIPIO link diagnostics

Off Link not active

Flashing Link active

H1/60___________________________________________________________________________

H

Standard profiles 2

___________________________________________________________________________H2/1

H

Section 22 Standard profiles

2.1 General

A device conforming to FIPIO communication standard profiles may be connected ona FIPIO bus and used to exchange I/O variables. The exchanges of data with the devicesenable : I/O exchanges, writing of configuration or adjustment parameters, diagnosticsof the connected device. There are three types of standard profile :

• FRDP : FIPIO Reduced Device Profile

• FSDP : FIPIO Simple Device Profile

• FEDP : FIPIO Extended Device Profile

2.2 Volume of data exchanged

Devices conforming to a standard profile have a profile which depends on the numberof I/O to be exchanged.The table below shows the words managed by the various standard profiles :

Profile FRD FSD FED

Process dataReading inputs 2 words 8 words 32 wordsControlling outputs 2 words 8 words 32 words

Configuration (optional) 16 words 30 words

Adjustment (optional) 32 words 30 words

CommandsSpecific command 8 words

DiagnosticsValidity of inputs 1 byte 1 byte 1 byteSpecific status 8 words

___________________________________________________________________________

H

H2/2

2.3 Accessing a standard profile

2.3-1 Choosing a standard profile

A device conforming to the FIPIO communication standard profiles is declared byassigning one of the standard profiles in the STD_P family to the device at the FIPIOconnection point. The family is made up of a list of standard profile references. Eachreference is made up of several codes with the following meanings :

• the standard profile used : FRD, FSD, FED,

• the structure of the connected device : Compact or Modular,

• the number and the type of objects exchanged with the manager : 2, 8, 32 wordscorresponding to the volume of I/O exchanges in 16-bit words,

• the presence of configuration or adjustment Parameters (optional).

Standard profileCompact or modular deviceNumber of I/O objectsPresence of parameters

FRD

FED

FSD

C/M

C 2

32

[P]8C/M

[P]

[P]

Standard profiles 2

___________________________________________________________________________H2/3

H

2.3-2 List of standard profiles supported by PL7 :

Compact device

Reference Designation Language interface

FRD C2 EQP RED CPMCT 2M 32 %I bits, 32 %Q bits

FRD C2 P EQP STD CMPCT 2M P 32 %I bits, 32 %Q bitsSTD DEV CMPCT 2W P 16 configuration words, 32 adjustment words

FSD C8 EQP STD CMPCT 8M 8 %IW words, 8 %QW wordsSTD DEV CMPCT 8W

FSD C8 P EQP STD CMPCT 8M P 8 %IW words, 8 %QW wordsSTD DEV CMPCT 8W P 16 configuration words, 32 adjustment words

FED C32 EQP STD CMPCT 32M 32 %IW words, 32%QW wordsSTD DEV CMPCT 32W

FED C32 P EQP STD CMPCT 32M P 32 %IW words, 32 %QW wordsSTD DEV CMPCT 32W P 30 configuration words, 30 adjustment words

Modular device :

Reference Designation Language interface (in number of words)

FSD M8 EQP STD MOD 8M 8 %IW words, 8 %QW wordsSTD DEV MOD 8W

FSD M8 P EQP STD MOD 8M P 8 %IW words, 8 %QW wordsSTD DEV MOD 8W P 16 configuration words, 32 parameter words

FED M32 EQP STD MOD 32M 32 %IW words, 32 %QW wordsEXTENDED DEV MOD 32W

FED M 32P EQP STD MOD 32M P 32 %IW words, 32 %QW wordsEXTENDED DEV MOD 32W P 30 configuration words, 30 parameter words

Communicator :

Reference Designation

TSX FPP10 TSX FIPIO communication module

OTHER Other communication module

___________________________________________________________________________

H

H2/4

2.3-3 Special feature of the FSD C8 P and FSD M8 P profiles

In order to ensure that a device connected on the bus can be started quickly, it is possibleto inhibit the transfer of the configuration and adjustment parameters. The device willthen start on a power up or on initialization with its own parameters.This option is selected using the "Local configuration" button in the configurationscreen.

By default, the button is not checked. When it is checked, the parameters are not sent,and in offline mode PL7 does not authorize access to the configuration and adjustmentscreens. The adjustment screen can be accessed in online mode but the SAVE /RESTORE and reconfiguration functions are grayed out (not available).

Standard profiles 2

___________________________________________________________________________H2/5

H

2.3-4 Accessing a standard profile with PL7

A standard profile is accessed in the same way as an I/O module is selected on the FIPIObus at a connection point. Select STD_P in the "Add / Modify Device" window. A catalogof profiles appears along with a list of communicators which can be selected if required.

___________________________________________________________________________

H

H2/6

2.3-5 Accessing a standard profile in the Momentum family

In the Momentum family, if an analog I/O base unit is not given in the catalog, one ofthe OTHER_FxD_[P] standard profile references must be selected. The selectioncriteria are as follows :

Base unit without parameters Base unit with parameters

Number of input bits = 32 and OTHER_FRD OTHER_FRDPNumber of output bits = 32

Number of input words ≤ 8 and OTHER_FSD OTHER_FSDPNumber of output words ≤ 8

Number of input words > 8 or OTHER_FED OTHER_FEDPNumber of output words > 8

To determine the number of input and output words required by each base unit used,refer to the installation manual for that base unit.If this base unit uses parameters, the format and syntax of the parameters to be enteredare given in the FIPIO communicator installation manual.

Example of a configuration screen :

Standard profiles 2

___________________________________________________________________________H2/7

H


2.4-1 Reminder on addressing language objects

% I,Q,M,K X,W,D \p.2.c\0 . i . n :X j

p = position in the rack : 0 or 1 according the processor slot2 = number of FIPIO channel, always 2c = number of device connection pointi = number of device channeln = rank of language object wordj = rank of bit in the word

Example : %MW\0.2.7\0.0.0

The various language objects associated with FIPIO data exchanges are given in thetables below. They are in addition to the language objects which are common to all thecommunication modules.

2.4-2 Implicit exchange language objects

The language objects are managed in automatic mode by the system. They areupdated on each cycle of the manager.


%I\p.2.c\0.0.ERR channel fault bit = 1 faulty channel

%I\p.2.c\0.MOD.ERR module fault bit = 1 faulty module

Profile Exchange Objects accessed

FRD input %I\p.2.c\0.0 to 0.31output %Q\p.2.c\0.0 to 0.31

FSD input %IW\p.2.c\0.0.0 to 0.0.7output %QW\p.2.c\0.0.0 to 0.0.7

FED input %IW\p.2.c\0.0.0 to 0.0.31output %QW\p.2.c\0.0.0 to 0.0.31

Type :I= inputQ= outputM= wordK= constant

Format :X= BooleanW= wordD= double word

Position :channeladdress

Channel no. rank rank of bitin a word(optional)

___________________________________________________________________________

H

H2/8

2.4-3 Explicit exchange language objects

Explicit exchange language objects are managed on request by the user program withthe READ_STATUS and WRITE_CMD functions. The WRITE_CMD function is onlyactive for FED... profiles.The configuration and adjustment words can be accessed in read only mode using theREAD_PARAM function, whereas adjustment words can be accessed using theREAD_PARAM, WRITE_PARAM, SAVE_PARAM, RESTORE_PARAM functions. Theyonly exist for profiles for which the parameters can be set : FRD... P, FSD... P and FED... P.

Configuration parameters which can only be accessed in read mode


%KW\p.2.c\0.0.0 channel configuration n = 15 for the FSD profileto words n = 29 for the FED profile%KW\p.2.c\0.0.n These words contain the channel parameters

defined in the configuration editor

Read parameters using the READ_STATUS function :


%MW\p.2.c\0.MOD.2 device status Low order byte :x0 = 1 internal faultx1 = 1 communication fault between manager

and agentx2 = 1 not usedx3 = 1 not usedx4 = 1 not usedx5 = 1 hardware or software configuration fault :

the module present is not the same asthat declared in the configuration

x6 = 1 module missingx7 = 1 reserved at 0High order byte :x8 to x15 reserved at 0

The following words are not updated by the READ-STATUS function but on eachexchange

%MW\p.2.c\0.0.0 exchange in x0 = 1 read the statusprogress x1 = 1 send the command parameters

x2 = 1 send the adjustment parametersx3 to x14 = reservedx15 = configuration in progress

%MW\p.2.c\0.0.1 report x0 = 0 read status OKx1 = 0 command parameters received,

accepted by the devicex2 = 0 adjustment parameters received,

accepted by the devicex3 to x14 reserved at 0x15 = 0 configuration parameters accepted by

the device

Standard profiles 2

___________________________________________________________________________H2/9

H

Read parameters using the READ_STATUS function : (cont.)


%MW\p.2.c\0.0.2 standard channel Low order byte :status x0 = 1 external fault 4

x1 = 1 external fault 3x2 = 1 external fault 2x3 = 1 external fault 1x4 = 1 internal module faultx5 = 1 hardware configuration fault : the

modules present are not compatiblex6 = 1 communication faultx7 = 1 application program fault : error in the

configuration or adjustment parameters,or specific command refused

High order byte :x8 to x15 = reserved at 0

%MW\p.2.c\0.0.3 validity of inputs for the FRD, FSD, FED profiles, 1 low order bytespecific to the connected device, see thecorresponding documentation

%MW\p.2.c\0.0.4 specific status for the FED profile only (8 specific statusto words)%MW\p.2.c\0.0.11

Specific write command words, for the FED profile, using the WRITE_CMD function :


%MW\p.2.c\0.0.12 specific command for the FED profile onlyto at channel level%MW\p.2.c\0.0.19 (8 specific command words)

Read / write adjustment words using the WRITE_PARAM, READ_PARAM,SAVE_PARAM, RESTORE_PARAM functions :


%MW \ p.2.c \ 0.0.4 adjustment for the FRD and FSD profilesto parameters%MW \ p.2.c \ 0.0.35

%MW \ p.2.c \ 0.0.20 adjustment for the FED profileto parameters%MW \ p.2.c \ 0.0.49

___________________________________________________________________________

H

H2/10

Summary of objects which can be accessed via the standard profiles :

The FRD profile is used to exchange I/O bits.

FRD C2 FRD C2 P

Reading inputs %I \ p.2.c \ 0.0 %I \ p.2.c \ 0.0%I \ p.2.c \ 0.31 %I \ p.2.c \ 0.31

Controlling outputs %Q \ p.2.c \ 0.0 %Q \ p.2.c \ 0.0%Q \ p.2.c \ 0.31 %Q \ p.2.c \ 0.31

Configuration words %KW\p.2.c\0.0.0 to 0.0.15

Exchange management %MW \ p.2.c \ 0.0.0 %MW \ p.2.c \ 0.0.0status

Exchange report %MW \ p.2.c \ 0.0.1 %MW \ p.2.c \ 0.0.1

Standard channel status %MW \ p.2.c \ 0.0.2 %MW \ p.2.c \ 0.0.2

Validity of inputs %MW \ p.2.c \ 0.0.3 %MW \ p.2.c \ 0.0.3

Specific channel status - -

Command words - -

Adjustment words - %MW\p.2.c\0.0.4 to 0.0.35

Standard profiles 2

___________________________________________________________________________H2/11

H

The FSD and FED profiles are used to exchange I/O words.

FSD C/M8 FSD C/M8P

Reading inputs %IW \ p.2.c \ 0.0.0 %IW \ p.2.c \ 0.0.0%IW \ p.2.c \ 0.0.7 %IW \ p.2.c \ 0.0.7

Controlling outputs %QW \ p.2.c \ 0.0.0 %QW \ p.2.c \ 0.0.0%QW \ p.2.c \ 0.0.7 %QW \ p.2.c \ 0.0.7

Configuration words - %KW \ p.2.c \ 0.0.0%KW \ p.2.c \ 0.0.15




Validity of inputs %MW \ p.2.c \ 0.0.3 %MW \ p.2.c \ 0.0.3

Specific channel status - -

Command words - -

Adjustment words - %MW \ p.2.c \ 0.0.4%MW \ p.2.c \ 0.0.35

FED C/M32 FED C/M32P

Reading inputs %IW \ p.2.c \ 0.0.0 %IW \ p.2.c \ 0.0.0%IW \ p.2.c \ 0.0.31 %IW \ p.2.c \ 0.0.31

Controlling outputs %QW \ p.2.c \ 0.0.0 %QW \ p.2.c \ 0.0.0%QW \ p.2.c \ 0.0.31 %QW \ p.2.c \ 0.0.29

Configuration words - %KW \ p.2.c \ 0.0.0%KW \ p.2.c \ 0.0.29




Validity of inputs %MW \ p.2.c \ 0.0.3

Specific channel status %MW \ p.2.c \ 0.0.4 %MW \ p.2.c \ 0.0.4%MW \ p.2.c \ 0.0.11 %MW \ p.2.c \ 0.0.11

Command words %MW \ p.2.c \ 0.0.12 %MW \ p.2.c \ 0.0.12%MW \ p.2.c \ 0.0.19 %MW \ p.2.c \ 0.0.19

Adjustment words - %MW \ p.2.c \ 0.0.20%MW \ p.2.c \ 0.0.49

___________________________________________________________________________

H

H2/12

2.5 Using a standard profile

2.5-1 Configuration modeIn the FIPIO bus configuration window, select a module. Double-clicking on its imageor selecting "Open Module" in the Edit menu opens a window in configuration mode.

It is possible to assign a channel to a manager task (FAST or MAST) in the channel partof this window.The %KW configuration words corresponding to the profile configured on the bus (16words if FSD and FRD profiles, or 30 words if FED profile) appear in the parameterspart of this window.A symbol (defined in the Variables function in the Application Browser) associated witheach bit is displayed for each word.

Standard profiles 2

___________________________________________________________________________H2/13

H

The "Base" window in the channel zone is used to select the display base for the valueof the selected word. This value can be decimal, hexadecimal or binary.

The display base for the selected word can be changed in real time.

Double-clicking with the right mouse button in a selected "value" box opens a"Properties of : " dialog box.

This window is used to enter the value in binary format. The bits to be set to 1 must bechecked. Closing this box confirms the value of the word entered according to the formatdefined in the "Base" window.

___________________________________________________________________________

H

H2/14

2.5-2 Adjust mode

Adjust mode is accessed via the hardware configuration menu in the ApplicationBrowser. The principle is the same as for configuration mode, the adjustment wordsare %MW. There are 32 possible words for the FSD and FRD profiles, and 30 wordsfor the FED profile.

Standard profiles 2

___________________________________________________________________________H2/15

H

2.6 Debug mode

This mode is only accessible in online mode. It provides access to the followingfunctions :• debug screens used to display and modify the I/O variables of the discrete or analog

modules in real time

• functions used to modify the configuration parameters in online mode

• functions for displaying configuration and adjustment words in the form of bytes or4-bit bytes

2.6-1 Common part of the application-specific screens in debug mode

The module debug screens comprise a common part relating to module diagnostics.Processing operations at channel level are different.

The RUN, ERR and IO LEDs are represented in the module zone as they appear onthe module front panel.Special feature of standard profiles :When the Diag button in the module zone is red, channel diagnostics can be accessedregardless of the color of the Diag button in the channel zone. In normal operation, thisbutton is displayed in gray.

___________________________________________________________________________

H

H2/16

2.6-2 Functions available in online mode

In online mode, the following functions can be accessed by opening the application-specific screen for a device :• Displaying the module configuration parameters• Reading, writing and saving the adjustment parameters• Reading, writing and forcing the I/O• Reading the aperiodic status data

If they have been entered correctly, the new module parameters are saved when theapplication-specific screen is closed.

Example of an application-specific screen :

Before modifying the device parameters, refer to the corresponding documentation.

FIPIO Agent 3

___________________________________________________________________________H3/1

H

Section 33 FIPIO Agent

3.1 Introduction : FIPIO Agent

TSX 37 or TSX 57 PLCs, equipped with a TSX FPP 10 PCMCIA on their integratedcommunication channel, are agents on the FIPIO bus. The bus manager can be aTSX P 5725 / 35 / 45, TPCX 5735, TPMX 57352, TPMX 57452, TSX 47-107or S1000 PLC.The FIPIO agent function enables two types of data exchange :

- periodic exchanges of data with the manager (shared type variables),- aperiodic exchanges of messages with the manager, CCX 17 devices or other

agents.

The hardware installation of the TSX FPP 10 PCMCIA card is described in the manuals :TSX DM 37 E, part K and TSX DM 57 E, part D.Warning : The TSX FPP10 PCMCIA must be version ≥ 1.8 to be compatible with a TSXPremium bus arbitrator.

3.2 Configuration

3.2-1 Installation : the manager is a TSX 57, PCX 57, TPMX PLC

The integrated link on TSX P 57252 / 352 / 452, TPCX 57 3512, TPMX 352or TMPX 57452 processors is used to connect 128 devices which may be PLCs,remote I/O, or any devices which conform to the standard profile.PL7 software (≥V3) is used to configure the bus.The installation of a manager is described in section 1 of this part.The configuration which should be used for an agent device in the "Add/Modify Device"screen is as follows :• Family : STD_P (standard profile),

• Module : FED M32 (standard profile type),

• Communicator : TSX FPP10 (FIPIO PCMCIA card),•• TSX family.

___________________________________________________________________________H3/2

H

3.2-2 Installation : the manager is a TSX 47 - 107 (series 7) PLC

TSX 37 and TSX 57 PLCs comply with the FED standard profile. Installation requires :- a FIPIO manager PLC : TSX / PMX version 5.3 minimum,- XTEL software workshop version 6.0 or later,- or XTEL V52 software workshop version 5.5 and the TSX LF CTG FSDP catalog

V6.0.

The TSX 37 or TSX 57 FIPIO agent must be declared in the TSX 47-107 manager remoteI/O configuration. To do this use the XTEL-CONF station tool (see "X-TEL SoftwareWorkshop" manual).• Selection :

- Device family : STD_P- base : FED M 32- communication : TSX FPP10

For more detailed information, refer to the "Installing FIPIO Standard Profiles" manual.Specific command and status words are not managed by the TSX 37/57 FIPIO AgentPLCs.

3.2-3 Installation : the manager is an APRIL 5000 PLC

The TSX 37/57 must be agent declared with the help of the ORPHEE configurationeditor for APRIL 5000 PLCs (see "ORPHEE Language and Software" manual). A TSX37/57 is declared by associating the FED reference to a connection point on the FIPIObus.• Selection :

- Device family : STD_P- base : FED M 32- communication : TSX FPP10

Specific command and status words are not managed by the TSX 37/57 FIPIO AgentPLCs.

FIPIO Agent 3

___________________________________________________________________________H3/3

H

3.2-4 Installation in PL7 Micro and PL7 Junior

Setup and access procedures for communication module configuration are describedin the communication functions section of this document. The screen below is onlyprovided as a reminder.

Connection point address window :

State the number of the connection point (between 1 and 127)State the %MW table start address for the table of 64 words reserved per connectionpoint for exchanging periodic data with the manager.

___________________________________________________________________________H3/4

H


3.3-1 Dialog and configuration language objects

The various dialog and configuration language objects associated with FIPIOcommunication and which can be used in a PL7 Micro or PL7 Junior program are :


%Im.v.ERR Channel fault = 1 Line fault

%IWm.v.0 I Agent function status Byte 0 = 16#01 = IDLE function 16#02 = RUN function 16#03 = STOP function Byte 1 =

strategy to apply 16#01 = Safetyto the outputs 16#02 = Value of the %MW valid

16#03 = Fallback

%MWm.v.2 E Standard status Byte 0 = x0 = 1 RIW not valid (Agent • RUN) x1 = 1 ROW not valid (Manager • RUN) x4 = 1 FPP10 internal error (or card not yet started

up by the manager) x5 = 1 Configuration error (module configured

differently from the current module) x6 = 1 Communication error on FIPIO x7 = 1 Application error (overflow of the %MW table) Byte 1 = Reserved

%KWm.v.0 I Type of channel Byte 0 =16#09 = FIPIO Agent

%KWm.v.1 I Reserved

%KWm.v.2 I Address of connection Byte 0 =point value from H'01' to H'7F' (1 to 127)

%KWm.v.3 I Table start address Byte 0 = Low order, Byte 1 = High order

%KWm.v.4 I Table length Byte 0 = Number of wordsByte 1 = Reserved

A PL7 Micro or PL7 Junior application of a TSX 37/57 Agent PLC can communicate withthe UNI-TE server of the manager PLC or with that of another FIPIO Agent device byusing the following communication functions : READ_VAR, WRITE_VAR, SEND_REQ.It cannot communicate with a station connected to the manager PLC via an X-WAYnetwork .

Note : I = implicit exchangesE = explicit exchanges (per READ_STS instruction)m = position of module (0 or 1)v = channel (always 1)

FIPIO Agent 3

___________________________________________________________________________H3/5

H

3.3-2 Data access : the manager is a Premium PLC

Every FIPIO Agent PLC uses 64 consecutive %MW words to exchange periodic data.The first 32 words are reserved for transmitting data to the manager, the next 32 wordsare reserved for receiving data.The syntax is : %IW\p.2.c\0.0.i for input data words

%QW\p.2.c\0.0.i for output data words

p = position of processorc = number of connection pointi = number of word (0 to 31 for inputs, 32 to 63 for outputs)

Reminder :%MW... status words and %MW... command words are not significant.

TSX 5725/35

TSX 57

TSX 37

ATV 16

FIPIO

1

2

3

4

%IW\0.2.1\0.0.0/%IW\0.2.1\0.0.15

%IW\0.2.1\0.0.16/%IW\0.2.1\0.0.31

%QW\0.2.1\0.0.32/%QW\0.2.1\0.0.47

%QW\0.2.1\0.0.48/%QW\0.2.1\0.0.63

%IW\0.2.4\0.0.0/%IW\0.2.4\0.0.15

%IW\0.2.4\0.0.16/%IW\0.2.4\0.0.31

%QW\0.2.4\0.0.32/%QW\0.2.4\0.0.47

%QW\0.2.4\0.0.48/%QW\0.2.4\0.0.63

%MW.../%MW...+31

%MW...+32/%MW...+63

%MW.../%MW...+31

%MW...+32/%MW...+63

Language viewin the agent

manager

Example : Language view of the manager

___________________________________________________________________________H3/6

H

TSX 47-107

TSX 57

TSX 37

ATV 16

FIPIO

1

2

3

4

3.3-3 Data access : the manager is a Series 7 PLC

Every FIPIO Agent PLC uses 64 consecutive %MW words to exchange periodic data.The first 32 words are reserved for transmitting data to the manager, the next 32 wordsare reserved for receiving data.The syntax is : RIWA i, j, k RIWB i, j, k

i = connection pointj = module (always 0)k = input/output word (0 to 15)

Example :

Language view of the manager

%MW... /%MW...+31

%MW...+32 /%MW...+63

%MW... /%MW...+31

%MW...+32 /%MW...+63

Language viewin the agent

ROWB4,0,0 /ROWB4,0,15

ROWA4,0,0 /ROWA4,0,15

RIWB4,0,0 /RIWB4,0,15

RIWA4,0,0 /RIWA4,0,15

ROWB1,0,0 /ROWB1,0,15

ROWA1,0,0 /ROWA1,0,15

RIWB1,0,0 /RIWB1,0,15

RIWA1,0,0 /RIWA1,0,15

manager

FIPIO Agent 3

___________________________________________________________________________H3/7

H

TSX 57

TSX 517

TSX 5725/35

TSX 37

1

2

63

0

3.4 Addressing

Example of architecture and access to the system of the various PLCs

Network manager

\1.1.0\SYSaccess to manager server

The terminal default address is 63.

The syntax of an address entered in a TSX 37/57 PLC or in PL7 is :

\ start module . start channel . connection point of arrival \ SYS

In a TSX 37 base, the processor position is 0. In a TSX 57 rack, the processor positioncan be 0 or 1 depending on the type of power supply (standard or double format).Example : reading, by means of the application, from TSX 57 address 2 to TSX 37 address1 :

READ_VAR (ADR#\1.1.1\SYS, %MW, 0, 10,%MW:10, %MW100:4)

The connection point identifies the destination PLC from its connection point number.This number is between 0 and 128, except for special devices, see the FIPIO section.

\0.1.0\SYSaccess tomanager server

start module = 1start channel = 1connect. pt. = 1



\0.1.1\SYSaccess to station 1 server

\0.1.2\SYSaccess to station 2 server

access to the agent server

___________________________________________________________________________H3/8

H

3.5 Debug screen

This screen accesses information on the selected FIPIO link.

___________________________________________________________________________1

I

Communication via FIPWAY network Contents

Section Page

1 Communication via FIPWAY network 1/1





1.5 Communication function 1/101.5-1 Message handling 1/101.5-2 Common words and shared table 1/11

1.6 TSX FPP 20 PCMCIA card operating modes 1/12

1.7 Performance 1/131.7-1 Transaction time between two stations

(normal message handling) 1/131.7-2 Limitations of communication via FIPWAY 1/13

1.8 Specific examples 1/141.8-1 Introduction 1/141.8-2 Using the common words service 1/141.8-3 Using the shared table service 1/17

___________________________________________________________________________

2

I

Communication via FIPWAY network Contents

Section Page

Communication via FIPWAY network 11

___________________________________________________________________________I1/1

I

1.1 Introduction

Communication via a FIPWAY network is used for exchanging data between all devicesconnected to the network.

A FIPWAY communication channel consists of three basic functions :

• the inter-station message handling function which routes the messages,

• the function for sending/receiving telegrams,

• the function for the production/consumption of common words (%NW) or for sharedtable.

This type of communication is available via a type III PCMCIA card, referenceTSX FPP 20.

The hardware installation of this card is described in the TSX DM 37E manual, part Kand the TSX DM57 E manual, part D for PCMCIA cards and the TSX SCY21600 / 21601module.

The FIPWAY network connects to Hirschmann fiber optic transceivers using theTSX FPP 200 PCMCIA card. Architectures and special conditions relating to configurationare presented in the installation documentation for these devices.


Section 11 Communication via FIPWAY network

___________________________________________________________________________I1/2

I


1.2-1 General

The procedures for installing and accessing the configuration screens for acommunication module are described in section 3 of this document. The screenexamples shown below are given as a reminder only. They are identical for TSX 37 andTSX 57 PLCs.

Accessing the configuration of the FIPWAY PCMCIA card

Depending on the type of processor, 1 to 3 FIPWAY links can be supported in aconfiguration. In a TSX 57-30 configuration, at least 3 FIPWAY (*) links can besupported, one in the processor host channel, and two others in the TSX SCY 21601modules, or all three in the TSX SCY 21601 modules.(*) Reminder : aTSX 57-202/302 supports at least 3 FIPWAY, ETHERNET, or Modbus + modules.


___________________________________________________________________________I1/3

I



The part which is specific to the configuration parameters is made up of severalwindows :

Telegram window

This service can only be accessed on the FIPWAY link of the processor hostchannel.

Telegram managementConfirms the management of telegrams.

Event processingSelects the management of telegrams by event-triggered task. Thescroll arrows are used to select the event-triggered task where thetelegrams will be processed. The possible values are between 0 and15 for a TSX 37, between 0 and 31 for a TSX 57-10 and between 0and 63 for a TSX 57-20.

___________________________________________________________________________I1/4

I

Physical layer window

FIP Selects the physical layer specific to FIP

IEC Selects the physical layer specific to WORLDFIP (not available)

Common data window

None Selected when no common data is managed in the application.

Common words The management of common data is performed by common words(%NW).

For more detailed information on the use of common words, referto the Network reference manual TSX DR NET, part A section 2.

Network no. In a multi-network architecture, the network number must be enteredto access %NW common word objects.

Shared table (ST)Common data is managed using a shared table. If this function isselected, the following three parameters are offered :

• Start of table address : indicates the start of the table of internalwords which is reserved in the PLC. Warning : the 128 wordsfollowing the start of the table will be reserved for the shared tablefunction.

• Zone address produced : indicates the address of the start of thezone of internal words produced by the PLC.

• Length of the produced zone in words : indicates the length (inwords) of the table of internal words produced by the PLC (1 to 32words).

For more information on the use of the shared table, see section 8.

Bridge The bridge button activates the dialog window used to enter routinginformation.


___________________________________________________________________________I1/5

I

1.3 Debug mode



The part which is specific to the parameters for debugging a FIPWAY network is madeup of three windows.

Channel information window

Network address Indicates the network address selected by the thumbwheels on theTSX FPP20 PCMCIA card.

Station address Indicates the station address selected by the thumbwheels on theTSX FPP20 PCMCIA card.

B.A Indicates whether the PCMCIA card is the FIPWAY network bus arbitrator.

Router Indicates whether the PCMCIA card is the router.

Common data Reminder of the type of common data selected in configuration mode(none, common words or shared table).

___________________________________________________________________________I1/6

I

Message errors window

This window displays the PCMCIA card error counters (messagessent and not acknowledged, and messages refused).

Reset countersResets the error counters to zero.

Channel test window

This window is used to test a communication channel by transmitting a UNI-TE requestto one of the stations present on the bus. The station is selected by choosing its addressfrom the list offered.

Identification Sends the Identification request to the FIPWAY card of the designatedstation. The reply to this request is given in the Receive Responsewindow.

Screen examples

Counter Sends the Read error counters request to the FIPWAY card of thedesignated station. The result of this request is given in the RequestResponse window.

Reset Counters Resets the error counters of the FIPWAY card of the designatedstation.

Enter Request Sends a UNI-TE request, other than those supplied by the controlbuttons, to the designated station. The choice of this function givesaccess to a screen for selecting parameters specific to the request(the request code must be coded in decimal format without aheader). Details of coding a UNI-TE request are given in the networkreference manual, TSX DR NET E.


___________________________________________________________________________I1/7

I

Mirror Sends a mirror request to the FIPWAY card of the designated station.The choice of this function gives access to a screen for selecting thelength of the character string to be sent (a maximum of 80 characters).The PLC sends this character string (ABCD etc) to the destinationdevice. This automatically sends the received character string to thetransmitter. It is then displayed in the Request Reply window.

Screen examples

Request for the transmission of a string of 12 characters :

Reception of the response :

___________________________________________________________________________I1/8

I


The various language objects associated with FIPWAY communication are given in thetable below. They are in addition to the language objects which are common to all thecommunication modules presented in part A of this manual.


%NW{n.s}.word Common word values

%IWm.1.0 Network status x0 = 1 if at least one station is present

%IWm.1.1 Network station Stations 0 to 15%IWm.1.2 shared table or common Stations 16 to 31%IWm.1.3 words refresh indicator Stations 32 to 47%IWm.1.4 Stations 48 to 63

%MWm.1.2 Standard channel status See section part A

%MWm.1.3 Specific channel status Byte 0 :x0 = 1 : if router (0 if not router)Byte 1 :16#00 = bus arbitrator function not supported16#10 = active bus arbitrator function16#20 = bus arbitrator function on standby

%MWm.1.4 Error counters Messages not acknowledged

%MWm.1.5 Error counters Messages refused

%MWm.1.6 Network/station address Byte 0 = network numberByte 1 = station number

%MWm.1.7 Common word or Byte 0 = activity status :shared table data 16#00 = Service inactive

16#01 = Read/write common words16#02 = Read common words16#03 = Participation in the exchange of a

shared table16#04 = Overlap of the exchange zone of a

shared table16#05 = Shared table exchange errorByte 1 = Size

%MWm.1.8 Network station Byte 0 x0 : station 0 ... Byte 1 x7 : station 15%MWm.1.9 status Byte 0 x0 : station 16 ... Byte 1 x7 : station 31%MWm.1.10 1 present Byte 0 x0 : station 32 ... Byte 1 x7 : station 47%MWm.1.11 0 absent Byte 0 x0 : station 48 ... Byte 1 x7 : station 63

%MWm.1.12 Control Byte 0 :x0 = 1 : Reset counter


___________________________________________________________________________I1/9

I


%KWm.1. 0 Type = 4 for FIPWAY

%KWm.1.1 Physical layer Byte 0 = 0 : FIP physical layer= 1 : WORLD FIP physical layer

Byte 1 : reserved

%KWm.1.2 Services supported Byte 0 : Common data16#00 = None16#01 = Common words16#02 = Shared tableByte 1 : Telegrams16#00 = not supported16#01 = supported

%KWm.1.3 Shared table data Shared table start address

%KWm.1.4 Common words and Byte 0 : Number of common words or size ofshared table the shared table production zone

Byte 1 : Start address (in bytes) for theshared table production zone

___________________________________________________________________________I1/10

I


1.5-1 Message handling

The PCMCIA card message handling service enables :

• the exchange of datagrams between two network stations,

• the broadcast of messages to all network stations,

• the transmission and reception of telegrams between stations at addresses 0 to 15,

• the return to devices of messages to be routed to another network (routing function).

Messages are exchanged synchronously between the PLC and the PCMCIA card.

Capacity

• The maximum size of a request is 128 bytes,

• the maximum size of a telegram is 16 bytes.

The maximum storage capacity for messages is :

• four reception messages,

• four transmission messages,

• one reception telegram,

• one transmission telegram.Note : The SEND_TLG and RGV_TLG communication functions are used to manage telegrams,the other functions can be used on FIPWAY to communicate with a remote station.


___________________________________________________________________________I1/11

I

1.5-2 Common words and shared table

By configuration, the PCMCIA card can support either the common words service orthe shared table service.

Common words service

The common words service is supported by stations with addresses between 0 and 31.These stations can produce four common words and can consume the other commonwords on the network. See the example.

Language interface :%NW{net no.,stat no.} word no. ...The network number selects the network on which common words are exchanged inthe case of a multi-network configuration.The TSX37 and the TSX 57-20 only manage one network hence:%NW{stat} number of the word

Shared table service

The shared table service is supported by stations with addresses between 0 and 31.These stations can produce the number of words defined during configuration (1 to 32words) and can consume words produced by the other stations on the network.

Important : the shared table service and the common words service cannot beused simultaneously on the same FIPWAY network.

___________________________________________________________________________I1/12

I

1.6 TSX FPP 20 PCMCIA card operating modes

General overview


• If there is no configuration, the card operates in message handling service mode, andit can receive a PL7 configuration.

• If there is a PL7 application in the PLC, the application configuration is transmittedto the module.


Note : In a TSX 57 station, only the card present within the processor can be used without a PL7configuration.

Module powered off

Stop module

Module configured

ConfigurationReset


Module in self-testphase

Power-up

Self-tests OK



___________________________________________________________________________I1/13

I

1.7 Performance

1.7-1 Transaction time between two stations (normal message handling)

Station during reception

Station during transmission cyclic periodic 50ms

cyclic 50ms

periodic 50ms 120ms 160ms

The time to exchange telegrams between two stations is 21ms.

1.7-2 Limitations of communication via FIPWAY

The TSX FPP20 PCMCIA card permits the processing of :8 transmission transactions and 8 reception transactions.


___________________________________________________________________________I1/14

I%NW {1} 0

FIPWAY

%NW {1} 1

%NW {1} 2

%NW {1} 3

%NW {2} 0

%NW {2} 1

%NW {2} 2

%NW {2} 3

%NW {3} 0

%NW {3} 1

%NW {3} 2

%NW {3} 3

1.8 Specific examples

1.8-1 Introduction

This section is not intended as a description of a programming example, but rather asa methodology for accessing common words and shared table services.

The shared table service can only be used with TSX37 or TSX 57 configurations.

1.8-2 Using the common words service

The common words service is supported by the FIPWAY network.

Description of the example

Station 1 Station 2 Station 3

Table of common words exchanged by stations 1, 2, 3.

Three PLCs connected to a FIPWAY network must exchange data between themselves(manufacturing parameters, action reports, etc) via the common words service. Thisservice corresponds to the exchange of 4 words (%NW) per PLC.

Note : only stations with addresses from 0 to 31 can exchange common words on FIPWAY.


___________________________________________________________________________I1/15

I

2 4 5

Multi-network example :

Station with several modules

In a multi-network architecture, the common words can be accessed from the networkaddress of each module.

%NW{1.2}0%NW{1.2}1%NW{1.2}2%NW{1.2}3

%NW{2.4}0%NW{2.4}1%NW{2.4}2%NW{2.4}3

%NW{3.5}0%NW{3.5}1%NW{3.5}2%NW{3.5}3


network #3

___________________________________________________________________________I1/16

I

Methodology :1) Configure the common words in the FIPWAY PCMCIA card configuration screen ofeach of the PLCs concerned by this exchange.

Example of configuring station 1

2) Via the application program, manage the content of the various common words (readcommon words from remote stations, write common words form the local station). Thesyntax for writing or reading a common word is the same as that for internal words :

%NW {2.1} 0 := %MW 10 (read in an internal word)%NW {2.2} 3 := 357 (write a value)

3) Transfer the applications to the various PLCs.

4) Set to RUN, the exchanges are performed without any intervention from theapplication program.The common words written by one station can be read by the others. The syntax is asfollows :

%NW {network n°.station n°} 0 for the first word""

%NW {network n°.station n°} n for the nth word


___________________________________________________________________________I1/17

I%MW200

%MW210

%MW209

%MW230

%MW229

%MW234

%MW300

%MW310

%MW309

%MW330

%MW329

%MW334

%MW400

%MW410

%MW409

%MW430

%MW429

%MW434

FIPWAY

{17.1} {17.2} {17.3}

network 17

1.8-3 Using the shared table service

The shared table service is supported by the FIPWAY network.

Description of the example

Three TSX 37 or TSX 57 PLCs connected to a FIPWAY network must exchange databetween themselves (manufacturing parameters, action reports, etc) via the sharedtable service. This service corresponds to the exchange of 32 words (%MW) per station.There may be a maximum of 32 stations on the FIPWAY network.

Station 1 exchanges a 10-word table starting at %MW200 to %MW300 on station 2 and%MW400 on station 3. Station 2 exchanges a 20-word table starting at %MW310 to%MW210 on station 1 and %MW410 on station 3. Station 3 exchanges a 5-word tablestarting at %MW430 to %MW230 on station 1 and %MW330 on station 2.

Shared table production diagram :

Station 1 Station 2 Station 3

10 wordsproduced bystation 1

20 wordsproducedby station 2

5 words producedby station 3

___________________________________________________________________________I1/18

I

Important :

1) The following should be defined :• the table start address• the start address for the internal word zone produced by the station• the length of the zone produced• via the application program, manage the content of the various words

produced by each station, in read and write mode.

2) Transfer the various applications to the PLCs

3) Set to RUN, the exchanges are performed without any intervention from theapplication program.

Methodology :1) Configure the parameters of the shared table in the FIPWAY PCMCIA card

configuration screen of each of the PLCs concerned by this exchange.Example of configuration screens for stations 1, 2, 3 :

Station 1

Station 2

Station 3

Important :

• from the address at the start of the configured table, the station reserves a table of128 words dedicated to the shared table. The total number of words produced by theother stations must be less than 128 words. If the length is less than 128, any wordswhich are not used must not be written by the application program,

• the data produced must be consecutive,

• it is not necessary to have identical lengths.

___________________________________________________________________________1

J

Communication via ETHERNET network Contents

Section Page

1 Communication via ETHERNET network 1/1

1.1 Introduction 1/11.1-1 General 1/11.1-2 Reminder on addressing 1/11.1-3 Compatibility 1/3

1.2 Configuration mode 1/41.2-1 Description of the configuration screen 1/41.2-2 Configuring TCP-IP services 1/51.2-3 Advanced window 1/91.2-4 Configuring ETHWAY services 1/10

1.3 Debug mode 1/121.3-1 Debugging common services 1/121.3-2 Debugging on ETHWAY services 1/131.3-3 Debugging on TCP-IP services 1/14


1.5 Message handling service common to Ethway and TCP-IP

profiles 1/18

1.6 Communication functions on the TCP-IP profile 1/191.6-1 Common words 1/191.6-2 Detecting a duplicate MAC address 1/19

1.7 Communication functions on the TCP-IP profile 1/201.7-1 Managing IP parameters 1/201.7-2 Managing TCP connections for X-WAY UNI-TE and

Modbus 1/201.7-3 Communication on the TCP-IP profile 1/231.7-4 Modbus communication on TCP-IP 1/24

___________________________________________________________________________

2

J

Communication via ETHERNET network Contents

Section Page

1.8 SNMP communication on UDP-IP 1/271.8-1 Introduction 1/271.8-2 SNMP protocol 1/271.8-3 Description of SNMP services used 1/28

1.9 TSX ETY 110 module operating modes 1/29

1.10 Example of Ethway private type architecture 1/301.10-1 Communication between the Premium 1 PLC and the

supervisor via TCP-IP 1/311.10-2 Communication between Premium PLCs via Ethway 1/33

1.11 Example of Ethway type architecture connected to TCP-IP 1/351.11-1 Communication between the Premium 1 PLC and the

supervisor via TCP-IP 1/36

1.12 Example of connecting to an existing TCP-IP network 1/381.12-1 Communication between the Premium 1 PLC and the supervisor

via TCP-IP 1/39

1.13 Example of communication between Premium and Quantum 1/411.13-1 Communication with a Premium server PLC 1/421.13-2 Communication with a Premium client PLC 1/43

1.14 Performance 1/44

1.15 Communication limits 1/44

Communication via ETHERNET network 1

___________________________________________________________________________

J

J1/1

1.1 Introduction

1.1-1 General

The TSX ETY 110 ETHERNET module communication channel offers two types ofconnection :

• connection to an ETHWAY network supporting services such as common words,X-WAY UNI-TE message handling service on an ETHWAY profile,

• connection to a TCP-IP network supporting the X-WAY UNI-TE and Modbusmessage handling service on an TCP-IP profile,

• SNMP : due to its function as an SNMP agent, the module can be supervised by oneor two SNMP managers. SNMP is one of the principal network supervision standardsof the TCP-IP environment.

This module can be used in three different contexts :• in an Ethway private type architecture

• in an Ethway private type architecture connected to a TCP-IP network via a gateway

• in an open TCP-IP architecture via direct connection to the network

Depending on the architecture chosen, the recommended mode of use is different (seeexamples of use).When the Ethway network exceeds 30%, it is advisable to use the TCP-IP profile insteadof the ETHWAY profile.Note : The TSX ETY 110 module also provides transparent routing of X-WAY UNI-TE messagesfrom a TCP-IP network to an X-WAY network and vice versa.

The hardware setup for this module is detailed in the TSX DM 57E manual, part D.

1.1-2 Reminder on addressing

IP address :

Each device connected to the network must have a unique IP address .This address consists of two identifiers, one identifying the network and the otheridentifying the connected machine.When the network environment is open type, the unique nature of the address isensured by the allocation of a network identifier by the qualified body in the countrywhere the network is in use.If the network environment is closed type, the unique nature of the address is managedby the company network administrator.An IP address is defined on 32 bits. It consists of 4 numbers, one for each byte in theaddress.

Example : 140.186.90.3

Section 11 Communication via ETHERNET network

___________________________________________________________________________

J

J1/2

0

0

0

1

11

Depending on the span of the network, three classes of address can be used :

class A

class B

class C

Spaces reserved for the various classes of IP address :

Class Range

A 0.0.0.0 to 127.255.255.255

B 128.0.0.0 to 191.255.255.255

C 192.0.0.0 to 223.255.255.255

- Class A is suitable for networks with a large number of connected sites.- Class B is suitable for medium-sized networks with fewer connected sites.- Class B is suitable for small networks with few connected sites.

Subaddressing and subnetwork mask

An IP address consists of two identifiers, one identifying the network and the otheridentifying the connected machine. In reality, the machine identifier can also includea subnetwork identifier.In an open environment, once a network identifier has been obtained from the approvedbody, the local system administrator can manage several networks. This enables localnetworks to be installed without any changes to the external appearance of the network,which is still viewed by the outside world as a single network designated by the networkidentifier.The subnetwork mask is used to find out the number of bits allocated to the networkidentifier and the subnetwork indicator respectively (bits at 1), and then to the machineidentifier (bits at 0).

Example : 140.186.90.316 bits 8 bits 8 bits

class B network subnetwork machineidentifier = 140.186 identifier = 90 identifier = 3

Subnetwork 24 bits at 1 8 bits at 0maskclass C

This organization allows 254 subnetworks with 254 machines per subnetwork.

7 bits 24 bits

14 bits 16 bits

21 bits 8 bits

Network ID Machine ID

Machine ID

Machine ID

Network ID

Network ID


___________________________________________________________________________

J

J1/3

The value of the subnetwork mask must be consistent with the class of the IP address.The subnetwork mask will have the value :

• for a class A address : 255.xxx.xxx.xxx

• for a class B address : 255.255.xxx.xxx

• for a class C address : 255.255.255.xxx

xxx is a value which can be freely selected by the user.

Gateway :The term gateway is used in this manual in the sense of "router". If the target machineis not connected to the local network, the message will be sent to the "default gateway"connected to the local network which will route the message either to another gatewayor to its final destination.

Reminder on TCP characteristics :- Time-out on a TCP connection : if a TCP connection cannot be established (if adestination is missing for example), the time-out for registering an error is 80 seconds.Each communication function time-out should be set at a value greater than 80 secondsas long as the first exchange has not been successfully completed.Keep Alive : the TCP layer sends a probe every 2 hours to detect broken connections(cable disconnection, detection of a client switched off by a server, etc). Use of thismechanism is explained in the section entitled "Managing TCP connections" in thispart.

1.1-3 Compatibility

The common words, SNMP and Modbus services are available from version V2.6 of theTSX ETY 110 module. PL7 must be installed and ≥ V3.3 of TSX 57 ••• PLCs used.If < V3.3 versions are installed, the above services cannot be activated.If < V2.6 version of the TSX ETY 110 module is used with ≥ V3.3 versions of PL7 andthe PLC, activating these services (common words or selection of the Modbus protocolin the connection configuration table) will result in the module not starting (flashing ERRLED).

___________________________________________________________________________

J

J1/4



The configuration screen is made up of two parts :- the left part for configuring TCP-IP services- the right part for configuring Ethway services


___________________________________________________________________________

J

J1/5

1.2-2 Configuring TCP-IP services

IP addresses configuration window

There are two options for configuring IP address parameters for the modulecommunication channel.

1- Check : "IP default address"The IP address is calculated from the programming of the module

thumbwheels.

2- Check : "Configured"The IP address parameters are configured explicitly by the user.They must include :- the IP address (a value must be entered)- the subnetwork mask which defines the part of the IP address allocated to the network identifier- the default gateway address to which messages destined for another network will be sent

Important notes :

- Default parameters should only be selected when the module is connected to aclosed or private network.- If the module is connected to an existing TCP-IP network, the IP addresses areadministered globally, so the IP parameters should be configured. If they are notconfigured, the network may be disrupted by duplicate IP addresses.

___________________________________________________________________________

J

J1/6

Connection configuration window

Connections allowed :gives the maximum number of TCP connections supported by the module (=< 32). Asingle TCP connection can be open between the module and a remote device, thisparameter therefore gives the maximum number of remote devices which can beconnected to the module in parallel.Setting this parameter to the useful value optimizes the communication resources foreach connection point.

Access control :This service is used to control (authorize or prohibit) the option for a device to establisha TCP connection with the module.- Check the "access control" box to globally activate the service.- Do not check the "access control" to use teach mode. (See the following example).

Grid : Net.Sta IP Address, Protocol, AccessThis is used to enter addresses to define :- the addresses of remote devices with which the application wishes to open a TCP

connection and then send to (in client mode). If they are not declared, the messagewill be sent to the Ethway profile and not to the TCP-IP profile.

- the addresses of remote devices authorized to connect to the local module, bychecking the "access" box for each line (this is only possible if "access control" isenabled).

- the type of protocol used (choice : UNI-TE or Modbus via pulldown menu).


___________________________________________________________________________

J

J1/7

TSX 57

Ethernet

TSX 57

Special cases

1- Self-teach mode :

This mode enables third-party remote devices to communicate with the module evenif they are not declared in the grid.It is activated when "access control" is not activated (box not checked). The "access"column in the grid is then invalid.

In this mode, the remote device should first establish a dialog with the module in servermode. After this communication, it will be possible to send messages from the PL7application to the remote devices.

Note : If the remote device closes TCP communication, it will be no longer possibleto transmit from the PL7 application.

UNI-TE communication on TCP-IP

Supervisor

{5.3}196.211.185.21

{5.1} 196.211.185.22

Premium 1

{5.2} 196.211.185.20

Premium 2bridgeX-WAY

network 6FIPWAY

___________________________________________________________________________

J

J1/8

In the above architecture, station 1 (TSX Premium 1) should communicate with thesupervisor and the other devices connected on FIPWAY. The grid will therefore beconfigured as follows :X-WAY address {5.3} IP address 196.211.185.21 (for the supervisor)X-WAY address {6.x} IP address 196.211.185.20 (for all the devices connected onFIPWAY, a station number x and the IP address of the TCP-IP access point, namely theTSX Premium 2 bridge station, are configured).The latter configuration {6.x} is used to for X-WAY broadcasts via TCP-IP from the TSXPremium 1 station to all stations on FIPWAY network 6.

2- Modbus devices connected on TCP-IP- the Modbus device does not have an X-WAY address. An X-WAY address is

nevertheless configured to allow addressing of functions in PL7. The configuredX-WAY address should have a station number between 100 and 164.

Ethernet configuration window :

There are two possible selections for the format of the Ethernet frames via TCP-IP :- Ethernet II format (default selection as it is that of TCP-IP profiles on PC)

- 802.3 formatNote :Ethernet II format is described in standard RFC 894802.3 format is described in standard RFC 1042

Advanced window


___________________________________________________________________________

J

J1/9

1.2-3 Advanced window

The SNMP button can be used to access the configuration screen of the ETY 110which can be used as an SNMP agent.

IP addresses :These designate IP addresses or remote managers (up to 2 managers). Theseaddresses are used when sending a TRAP (See the section on SNMP communicationon UDP-IP).

Agent :Location (SysLocation) : Indicates the physical location of the device (string of up to 32characters).Contact (SysContact) : Indicates the contact person for device management and howthey can be contacted (string of up to 32 characters).

Security :Activates the "Authentification Failure" trap : Enables (when checked) or disables thesending of an authentification failure trap from a manager.

Community names :Defines a community name by Set/Get/Trap service family (string of up to 16 characters).These families define the access rights of the manager to the MIB objects of the SNMP.

Note :Only ASCII characters on 7 bits are authorized in the input fields of character strings.

___________________________________________________________________________

J

J1/10

1.2-4 Configuring ETHWAY services

Ethway data window :

Ethway data :

The common data consists of common words. In the configuration, it is possible toselect the type of support service and the number of common words allocated perstation (4 by default). A base of a total of 256 words is available, shared between thestations. The size of the common words should be the same in each station.Three options are available :- "none" : no common words are managed in the application,

- "read common words" : the common words can only be read by the application,

- "read/write common words" : the common words can be read and written by theapplication.

The user should configure the network address of the current station for the last twooptions in order to be able to program the network common word language objects inthe application.

Important :If the network address configured is different from the one encoded on the thumbwheelsof the module, the latter will not start (ERR LED will flash).Similarly, if the size of the common words selected is incompatible with the stationaddress encoded on the thumbwheels, the module will not start (ERR LED will flash).

Example :A words/station size of 64 and a station address ≥≥≥≥≥ 4 are incompatible because thisexceeds the maximum size of the database (256 common words).


___________________________________________________________________________

J

J1/11

Bridge function configuration

The "Bridge..." button is used to gain direct access to a window for entering thelist of networks which can be accessed by the module.See part K, "Multi-network communication", in this manual for details on installation.

___________________________________________________________________________

J

J1/12

1.3 Debug mode

Description of the debug screen :It is made up of three parts

TCP-IP ETHWAYservices services

Commonservices

1.3-1 Debugging common services

Message traffic window :

This shows the number of messages per minute processed by the module (sendingand receiving). This number can be compared to the maximum rate offered by themodule (12000 messages of 128 bytes per minute) to determine whether the moduleis operating within a normal operating range or is overloaded.


___________________________________________________________________________

J

J1/13

Message errors window :

The message errors window shows the number of messages not acknowledged onEthway and the number of messages refused on Ethway or TCP-IP.The user can reset these counters to zero by clicking on the Reset Counters button.

1.3-2 Debugging on ETHWAY services

Station address window :

Network address : indicates the network address selected on the module thumbwheelStation : indicates the station address selected on the module thumbwheelCommon data : reminder of the type of service selected in configuration mode forcommon data (None, Common Words (Read), Common Words (R/W).Bridge : if the box is checked, indicates that the station has been declared as an X-WAYbridge.

___________________________________________________________________________

J

J1/14

Station test window :

This window displays in realtime the list of stations connected on the Ethernet networkwhich support the ETHWAY profile.

This window is also used to test communication by sending a UNI-TE request viaEthway to another station present on the local segment. It can be selected by selectingits number from the list. The result of the request appears in the "response reception"window. There are two possible formats for presentation of the response :- ASCII string (default option)

- hexadecimal.Note : Only stations with a Telemecanique MAC address are included in the list and can be tested.

1.3-3 Debugging on TCP-IP services

IP address window :

This window summarizes the configuration data of the IP address :- IP address and subnetwork mask : indicates the station IP network identifier used by the module- gateway address : indicates the address of the local gateway used by the module


___________________________________________________________________________

J

J1/15

Communication test window :

Used to test the IP communication with another station declared in the grid of remotedevices. The list of configured IP addresses is used to select the station with which tocommunicate by activating a "ping" which feeds back as a status the loop-back timeof the message (in ms) or :- "time out" : no response from the remote device within a set time period- "host unreachable" : remote device cannot be reached in the network architectureAs an option, the user can specify the length of the message to be sent. Its size can befrom 64 to 1472 bytes.

___________________________________________________________________________

J

J1/16


The various language objects associated with ETHERNET communication are givenin the following tables. They are in addition to the language objects which are commonto all the communication modules presented in section 1 of this manual.


%Im.0.ERR Link state

%NW{n.s}word Values of commonwords

%IWm.0.0 Network state x0 = 1 if common words are receivedfrom at least one remote station

%IWm.0.1 Update indicator Stations 0 to 15%IWm.0.2 for the network Stations 16 to 31%IWm.0.3 station common Stations 32 to 47%IWm.0.4 words Stations 48 to 63

%MWm.0.2 Standard channel status x0 to x3 = reserved at 0x4 = faulty module or self-tests in progressx5 to x6 = reserved at 0x7 = application fault

(configuration fault)

%MWm.0.3 Specific channel status Byte 0 :x0 = 1 : if X-WAY bridge (0 if not)Byte 1 : number of open TCP connections

%MWm.0.4 Error counters Messages not acknowledged on Ethway%MWm.0.5 X-WAY on Ethway Messages refused on Ethway

%MWm.0.6 X-WAY network address Byte 0 = station numberByte 1 = network number

%MWm.0.7 Common words or Byte 0 = activity status :shared table data 16#00 = Service inactive

16#01 = Read / write common words16#02 = Read common wordsByte 1 = Size of common words produced

%MWm.0.8 Message counter Messages refused on X-WAY TCP-IPon TCP-IP

%MWm.0.9%MWm.0.10 Message Messages received on the link layer

counter%MWm.0.11 on the link%MWm.0.12 layer Messages sent on the link layer


___________________________________________________________________________

J

J1/17


%KWm.0.0 Type = 11 for ETHWAY

%KWm.0.1 Physical layer Byte 0 : reservedByte 1 : reserved

%KWm.0.2 Services supported Byte 0 : Common data (0 by default)bit 0 : activation of Ethway common wordsbit 1 : reservedbit 2 : common words read onlybit 3 : common words read and writebits 4 to 7 : reservedByte 1 : reserved

%KWm.0.4 Common words Byte 0 : size of common wordsByte 1 : reserved

%KWm.0.5 X-WAY network address Byte 0 : network number (0 by default)Byte 1 : reserved

%KWm.0.6 Type of driver Byte 0 : 16#00 = AUI (default value)Ethernet for TCP-IP 16#01 = RJ45

Byte 1 : 16#00 = Ethernet II (default value) 16#01 = 802.3

%KWm.0.7 TCP-IP configuration : Byte 1 : address inherited (16#00 by default)type of address 16#01 from the application-specific function

16#03 from a server

%KWm.0.8 Local IP address Byte 0 (low order) to byte 3 (high order)%KWm.0.9 (default value = 0.0.0.0)

%KWm.0.10 Default gateway IP Byte 0 (low order) to byte 3 (high order)%KWm.0.11 address (default value = 0.0.0.0)

%KWm.0.12 Subnetwork mask Byte 0 (low order) to byte 3 (high order)%KWm.0.13 (default value = 0.0.0.0)

%KWm.0.14 reservedto%KWm.0.46

___________________________________________________________________________

J

J1/18

1.5 Message handling service common to Ethway and TCP-IP profiles

The message handling service of the TSX ETY 110 module is used to :

• Exchange datagrams between two network stations• Transmit or broadcast messages to all network stations• Feed back to the device messages to be routed to another network (routing function)

There are two types of datagram exchange service :

- An exchange service synchronized on the PLC scan time (UNI-TE, applicationto application). The maximum size of the data in a message is 256 bytes.

- An asynchronous exchange service (in relation to the PLC scan time) :

In server mode : This service is used to exchange messages up to a maximum sizeof 1024 bytes. The authorized requests are :36 : READ_Object (bit or word)37 : WRITE_Object (bit or word)38 : READ_Object _ List3A : MIRROR82 : READ_Generic_Object83 : WRITE_Generic_ObjectConsistency of data read can be guaranteed (guarantee that the request has beensent in one scan) by setting system bit %S91 to 1. In this configuration, a jitterphenomenon of a maximum of 1.5 ms may appear on the MAST task.

In client mode two functions can be used :The “Write_ASYN” function (request 37 : WRITE_Object) is used to write up to 507words (%MW) or 8112 bits (%M) by the asynchronous message handling channelvia the ETY110 module.The “Read_ASYN” function (request 36 : READ_Object) is used to read up to 510words (%MW) or 8160 bits (%M) by the asynchronous message handling channelvia the ETY110 module.A maximum of 8 functions can be activated at the same time.The WRITE_Asyn and READ_Asyn functions cannot cross a bridge.

The PLC MAST task should be configured as periodic for this service to operatecorrectly.The internal description of the PLC functions SERVER, READ_Asyn and WRITE_Asynis given in part A of this manual.

Note :The asynchronous server function supports V2.0 or V1 UNI-TE protocols.The WRITE_Asyn and READ_Asyn functions use the UNI-TE V2.0 protocol.


___________________________________________________________________________

J

J1/19

1.6 Communication functions on the TCP-IP profile

1.6-1 Common words

By configuration in the "Ethway data" screen, the TSX ETY 110 module can support thecommon words service.

The ETHWAY common words service is described in the X-WAY communicationreference manual, section 2.

Language interface :%NW{ net no., stat no. } word no. etc.The network number is used to select the network on which common words areexchanged in the case of a multi-network configuration.

! The common words service alone can consume a large part of the messagehandling passband of the module if there are a large number of stations connected andif the PLC scan time configured is very short. Common words are sent on each PLCscan if their status changes, and every 10 scans if their value is not modified.The user should therefore ensure that the maximum capacity of the module indicatedin section 1.14 of this part is not exceeded.

1.6-2 Detecting a duplicate MAC address

A check for duplicate MAC addresses (defined by the thumbwheels) between stationswith Telemecanique MAC addresses is performed when the device is switched on. Forthis check to function, the network connection cable must be plugged in before thedevice is switched on.If a duplicate is detected, the RUN and ADR LEDs on the front panel of the module lightup.

___________________________________________________________________________

J

J1/20

1.7 Communication functions on the TCP-IP profile

1.7-1 Managing IP parameters

In a closed architecture, it is possible not to configure the IP parameters, and to retainthe default values.In an open TCP-IP architecture, the IP parameters (IP address, subnetwork mask,gateway address) must be configured.The default value of the local IP address is derived from the MAC address (itsuniqueness is not guaranteed in an open TCP-IP architecture), and is a class A IPaddress.

MAC address

16# 00 80 F4 00 <network address> <station address>

Default IP address

16# 54 00 <network address> <station address>

The default value of the subnetwork mask is 0.0.0.0 (no concept of subnetwork).

The default value of the gateway is 0.0.0.0 (no IP gateway).

1.7-2 Managing TCP connections for X-WAY UNI-TE and Modbus

The connection can be opened either by the local PLC or by a remote station wishingto communicate with the local PLC.A connection is characterized by the pair :(local TCP port, local IP address; remote TCP port, remote IP address)

The value of the Modicon TSX text reception port is : 502

Connection management is transparent to the user.

Opening a connection from a remote device :

The TSX ETY 110 module waits for a connection from a remote device. When aconnection is received, it is necessary to check that the IP address of the remotemachine is on the list of remote machines authorized to connect. If it is, the connectionis opened, if not it remains closed.

A single TCP connection can be opened between the local PLC and a remotedevice connected on TCP-IP.


___________________________________________________________________________

J

J1/21

TSX 57 TSX 57

TSX 57

Ethernet TCP-IP

FIPWAY

PC

Opening a connection from a local PLC

When a message is sent by a communication function, if there is no connection to theremote device, one is automatically opened internally by the TSX ETY 110 module tothe Modicon TSX (502) remote port.

A single TCP connection can be opened between the local PLC and a remotedevice connected on TCP-IP.

Example of connections :

{2,1}

{1,3}84.0.1.3

{1,2}84.0.1.2

{1,4}84.0.1.4

{1,1}84.0.1.1

Bridge

___________________________________________________________________________

J

J1/22

In the example opposite, four TCP connections are open for communication betweenthe terminal and the PLC stations or between two PLC stations.- The terminal always takes the initiative in opening connections.- Between two PLCs, either of the PLCs can take the initiative in opening the

connection.- A single TCP connection is open between two devices connected on TCP. This

implies a single connection between the terminal and a PLC for all the terminalapplications and a single connection for all the applications of the devices connectedon FIPWAY.

Closing connectionsConnections can be closed in two ways :- by the remote station which decides to stop communicating and sends a TCP-IP

connection closure message- by the local PLC if the maximum number of open connections has been reached (the

oldest open connection is closed)The closure of a connection is signaled to the PL7 application by an error report(message refused) on any exchanges in progress.

Exchanging messages on TCP-IPBehavior when a remote device disappears (malfunction, power cut, disconnection ofthe network cable, etc), and in the absence of communication, the TCP connection willbe terminated after a period of approximately ∆t = 2h. If within this time :- the cable is reconnected : communication with the remote device will resume on the

TCP connection previously open- the remote device becomes operational and two situations are then possible :

The remote device which has disappeared was a server :

If the remote device is a server, and sending to it will cause the closure of the TCP-IPconnection which stayed half-open on the client ETY110 side (1) (a Reset command(2) is sent by the server). The next exchange initiated by the client ETY110 will opena new TCP-IP connection (3).

1

3

2

Client ETY110 Remotedevice

Server


___________________________________________________________________________

J

J1/23

The remote device which has disappeared was a client :

21

3

Server ETY110

Client

Remotedevice

If the remote device is a client, and sending by it (1) will cause an open connectionrequest to be sent to the server ETY110 (2). The latter will immediately close theconnection which stayed half-open (3) if there is no current activity on it and accept theincoming connection (2).

1.7-3 Communication on the TCP-IP profile

Message handling :The characteristics of the message handling services offered are the same as for theETHWAY function, with the exception of broadcasting, which is not available onTCP-IP.See setting up READ_VAR, WRITE_VAR, SEND_REQ, DATA_EXCH, READ_Asyn,WRITE_ Asyn communication functions in this manual.Each communication function uses an XWAY address to designate a remote station.The module uses internally a table of correspondence between the IP address and theXWAY <network, station> address. This table is generated during module configura-tion.

With a PL7 application, it is not possible to address an Ethway profile and a TCP-IPprofile simultaneously from the same remote device. Selection is made atconfiguration level. If the IP address is declared in the table, the message will besent to the TCP-IP profile, otherwise it will be sent to the ETHWAY profile.

___________________________________________________________________________

J

J1/24

1.7-4 Modbus communication on TCP-IP

Description :This service allows communication using the Modbus protocol between a TSXPremium PLC and a Quantum PLC, another TSX Premium PLC or supervisor softwareon a PC.

A single module can communicate with a remote device in client mode (for example aQuantum PLC) and another remote device in server mode (for example a supervisorPC).The TSX Premium 1 PLC is a client in relation to the Quantum PLC : it opens the TCP-IPconnection and sends Modbus messages to the Quantum.The TSX Premium 1 PLC is a server in relation to the supervisor : the supervisor hasopened a TCP-IP connection and sends Modbus messages to the TSX Premium 1.

Recommendations for use :

Double profile : UNI-TE and Modbus are not supported on the same TSX Premiumremote station.Client/server modes are exclusive in relation to a given remote device .PLC applications and network architectures must be designed so that switchingfrom one mode to another occurs as infrequently as possible between the sametwo devices .Frequent switching could result in the loss of messages :

- If the Premium PLC communicates in server mode with a Quantum PLC which hasopened the TCP-IP connection, the client PL7 application sending a message willcause the closure of the server TCP-IP connection after the processing of anycurrent server transactions.- If the Premium PLC which has opened the TCP-IP connection communicates inclient mode with a Quantum PLC, a request to open a connection from the Quantumwill cause the closure of the client TCP-IP connection with the possible loss ofcurrent client transactions.

Quantum

TSX 57

TCP-IP Ethernet

TSX 57

Clientsupervisor

Client/ServerPremium 2Server Quantum

MODBUSProtocol

MODBUSProtocol

Client/ServerPremium 1

MODBUSProtocol


___________________________________________________________________________

J

J1/25

Quantum

TSX 57

Ethernet

Modbus+

TSX 57

FIPWAY

Modbus Modbus

Architecture supported :

- Modbus protocol ensures interoperability between Premium and Quantum stationson an Ethernet TCP-IP network. However, access from a Premium PLC to a Modbus+ network connected to the Quantum PLC is not possible via TCP-IP.

- Similarly, the Modbus protocol does not cross X-WAY Premium bridges.

Message handling :

See setting up READ_VAR, WRITE_VAR, SEND_REQ communication functions inthis manual.The user communication functions are identical to those described in the Modbus +communication function.

Programmingterminal

Modbus communication UNI-TE communication

___________________________________________________________________________

J

J1/26

Although a Modbus remote station does not have an X-WAY format address, eachcommunication function uses an X-WAY format address to designate a remote IPstation.

For each Modbus remote station, the user must configure the IP / X-WAY <network,station> address in the table of correspondence where :<network> : network number of the local X-WAY station<station> : 100 to 164 = logic number of the X-WAY station

This address will only be used by the local Premium module, it is not transmitted on thenetwork.If a TSX Premium remote station is configured with the Modbus protocol, it is recom-mended to assign an X-WAY station address equal to the number of the local station(encoded on the thumbwheels), increased by 100.


___________________________________________________________________________

J

J1/27

1.8 SNMP communication on UDP-IP

1.8-1 Introduction

The set of SNMP (Simple Network Management Protocol) standards defines networksupervision solutions in terms of protocol and exchange of supervised data.The SNMP architecture is based on the following essential elements :

- The "manager" which is used to supervise all or part of the network.- One or more "agents". Each supervised device has a software module called"agent" which is used by the SNMP protocol.- An MIB (Management Information Base), which is a database or collection ofobjects.- The SNMP supervision protocol.

The SNMP agent service is implemented on the ETY110 module. It allows amanager to access the MIB - II standardized objects from the ETY110 agent usingthe SNMP V1 protocol.

Note :No operating software is supplied on the manager side and it is not possible to download a privateMIB.

1.8-2 SNMP protocol

The SNMP protocol defines 5 types of message between the agent and manager.These messages are enclosed in "UDP" datagrams.

Messages from the manager to an agent :- Get_Request : Used to obtain the value of one or more variables- Get_Next_Request : Used to obtain the value of subsequent variables- Set_Request : Used to set the value of a variable

Messages from the agent to the manager :- Get_Reponse : Used by the agent to send the value of the requested variable- Trap : Used by the agent for asynchronous signalling of an event

___________________________________________________________________________

J

J1/28

1.8-3 Description of SNMP services used

The SNMP manager sends write or read requests (SetRequest/GetRequest/GetNextRequest, etc) concerning objects defined in the SNMP MIB - II, and the ETY110module SNMP agent responds to them.

The module SNMP agent sends events (traps) to the manager. The system trapsmanaged are as follows :

- Cold Start Trap : Event sent following a module supply reset- Authentification Failure Trap : Event sent following an authentification problem.The "Community Name" field in the message received is not the same as the oneconfigured on the module. This trap can be disabled when configuring the ETY110module in PL7.

SNMP agentPLC station ETY110

Set_Request, Get_Request,Get_Next_Request

SNMP manager

Get_Response, Trap

Ethernet


___________________________________________________________________________

J

J1/29

1.9 TSX ETY 110 module operating modes

General overview

• After power-up, the module performs its self-tests.

• The module does not operate with a default configuration. The configuration must betransmitted by the PL7 application of the local PLC.The configuration values are given in the list of language objects %KW. T h enetwork, station address is given by the thumbwheels on the front panel.

• After receiving the configuration, the module resets the communication in progressbefore configuring itself (exchanges in progress are ended and TCP connectionsclosed).

Module powered off


Module configured Communication Module in self-testfunction phase


Module notconfigured

___________________________________________________________________________

J

J1/30

TSX 57

Ethernet

TSX 57

FIPWAY

Premium 1 Premium 2

1.10 Example of Ethway private type architecture

Key to graphics used in the following examples :

Ethway communication

Ethway or TCP-IP communication

Example of use :

Recommended mode of use :- IP addressing not administered (default value), the IP address is derived from the

values displayed on the module thumbwheels

- Ethway services (COM, UNI-TE) for communication between PLCs

- Ethway or UNI-TE services on TCP-IP for communication between the supervisorand the programming / debug tool (equipped or not with the TCP-IP profile)

- format of frames : Ethernet 802.3 on Ethway and Ethernet II on TCP-IPNote : In the examples which follow, it is assumed that communication with the terminals is viaTCP-IP.


Supervisor Programmingterminal

Ethway or UNI-TE onTCP-IP communication

Ethway or UNI-TE onTCP-IP communication

{1.3}84.0.1.3

{1.4}84.0.1.4

{1.2}84.0.1.2

{1.1}84.0.1.1

Network 1.84.00. cell level


___________________________________________________________________________

J

J1/31

1.10-1 Communication between the Premium 1 PLC and the supervisor via TCP-IP

Configuration of the Ethernet function of the Premium 1 PLC module :

1) Configuration of the local address :

In a closed environment, it is possible not to administer the IP addresses, the defaultIP mode is selected.

2) Configuration of connections :

The X-WAY address of the remote stations with which the PLC wishes to communicate(X-WAY address 1.3) must be entered in the relevant field, the other fields areautomatically initialized. Access protection is inhibited by default and the maximumnumber of connections is 32.Note : as the PLC is always the server in relation to the programming terminal, it does not needto be declared.

___________________________________________________________________________

J

J1/32

3) Ethernet configuration :

The Ethernet frame format selected for TCP-IP is Ethernet II as the terminals use thisformat in the example.

Debugging :

In debug mode, the IP address screen gives the IP address, subnetwork mask andgateway address parameters actually used by the module.

The communication test screen is used to send a PING to a station declared duringconfiguration of connections (in this example, to terminal 1.3 or supervisor 1.4). Clickon the target IP address in the address window.


___________________________________________________________________________

J

J1/33

1.10-2 Communication between Premium PLCs via Ethway

Message handling configuration mode :No configuration is required for Ethway message handling.

Common words :

The following must, without fail, be configured :- the type of service,

- the size of the common words of the selected station,

- the network number.

Message handling debug mode :

The message traffic screen shows the number of messages per minute processed bythe module on TCP-IP and on Ethway.

___________________________________________________________________________

J

J1/34

Message errors screen :

This screen shows the number of messages not acknowledged on Ethway and thenumber of messages refused on Ethway or TCP-IP. The user can reset these countersto zero by clicking on the Reset Counters button.

This screen displays the X-WAY address of the station (in this example 1.2) and the typeof common words service selected.

This screen is used to send a UNI-TE request (identification) on the local segment ofthe Ethway network :- Click on the target station to be tested in the station no. window.

- Select the type of request to be sent (identification or mirror).

- The response is displayed in the response reception screen, in ASCII mode orhexadecimal mode.

12

12

2

21

Common words Read/Write


___________________________________________________________________________

J

J1/35

FIPWAY

Premium 1 Premium 2

Ethernet

Ethernet TCP-IP

1.11 Example of Ethway type architecture connected to TCP-IP

Example of use :

supervisor

UNI-TE communicationon TCP-IP

programming terminaland PLC debugging


Ethway or UNI-TEcommunication on TCP-IP

{1.3}140.252.1.11

{1.4}140.252.2.4

{1.1}140.252.2.1

{1.2}140.252.2.2

subnetwork 140.252.2.0cell level

network 1 140.252 factory level

Bridge

140.252.1.255

___________________________________________________________________________

J

J1/36

Recommended mode of use :- IP addressing administered globally, as you are connecting to an existing TCP-IP

factory network,

- UNI-TE services on TCP-IP for communication between the supervisor and PLCs,

- Ethway services (COM, UNI-TE) for communication between PLCs at cell level,

- Ethway or UNI-TE services on TCP-IP for communication at cell level between theprogramming terminal and PLCs depending on whether the terminal is equipped withthe TCP-IP profile.

Ethway cell level services are identical to those described in the previous example. Thisexample only describes communication between the supervisor at factory level anda Premium PLC at cell level.

1.11-1 Communication between the Premium 1 PLC and the supervisor via TCP-IP

In the configuration screen of PLC 1 :1) Configuration of the local IP address :

As the IP addresses must be administered, "IP address configured" mode is selected.The user should enter the IP parameters listed above. These values come from theglobal installation addressing plan managed by the network administrator.The administrator can ensure their uniqueness by having the network ID (140.252)assigned by a qualified body.The cell level network is an IP subnetwork. This means that a unique network ID(140.252) can be assigned to the entire architecture. The subnetworks are then definedby the subnetwork mask user 255.255.255.0.

The address class selected (here class B) will depend on the number of machines andthe number of networks in the system.


___________________________________________________________________________

J

J1/37

2) Connection configuration :

The user must enter both the X-WAY address and the IP address of the devices withwhich they will communicate.

If there is to be an access control check, the "access control" box must be checked andthe corresponding box must be checked in the "access" column in the table. Themaximum number of connections for the application can be adjusted.


The Ethernet frame format selected for TCP-IP is Ethernet II as the terminals use thisformat.

Debug mode :

The options offered by debug mode are the same as those described in the previousexample.

XX

___________________________________________________________________________

J

J1/38

TSX 57

Ethernet TCP-IP

TSX 57

FIPWAY

Premium 1 Premium 2

{1.1}140.252.2.8

{1.2}140.252.2.10

{1.3}140.252.2.11

{1.4}140.252.2.9

140.252.2.255

1.12 Example of connecting to an existing TCP-IP network

Example of use :

Recommended mode of use :- IP addressing administered obligatorily, as you are connecting to an existing TCP-IP

network

- UNI-TE services on TCP-IP for communication between PLCs

- UNI-TE services on TCP-IP for communication between the programming terminaland PLCs depending on whether the terminal is equipped with the TCP-IP profile


Supervisor Programmingterminal



Network 3

Gateway


___________________________________________________________________________

J

J1/39

1.12-1 Communication between the Premium 1 PLC and the supervisorvia TCP-IP

1) Configuration of the local IP address :

The IP addresses must be administered, "IP address configured" mode is selected, theuser must enter the IP parameters.

___________________________________________________________________________

J

J1/40

2) Configuration of connections :

The user must enter both the X-WAY address and the IP address of the devices betweenwhich exchanges will take place.Click the "access control" box to activate the check, then check the corresponding boxin the "access authorized" column. The maximum number of connections in theapplication can be adjusted.


The Ethernet frame format selected for TCP-IP is Ethernet II as the programmingterminals use this format.

Debug mode :

The options offered by debug mode are the same as those described in example 1.


___________________________________________________________________________

J

J1/41

Quantum

TSX 57

Ethernet

Modbus

{1.101}140.252.2.8

{1.2}142.252.2.10

{1.3}140.252.2.11

Modbus+

Premium

FIPWAY

140.252.2.255

Gateway

1.13 Example of communication between Premium and Quantum

Recommended mode of use :- IP addressing must be administered obligatorily because of the risk of duplicating IP

addresses with default values

- Modbus services on TCP-IP for communication between PLCs

Programmingterminal

Modbus communicationon TCP-IP

UNI-TE communication on TCP-IP

X-WAY network 1 140.252 IP

Communication

___________________________________________________________________________

J

J1/42

1.13-1 Communication with a Premium server PLC

In this example, the Premium PLC is only used as a server .

In the configuration screen of the Premium PLC :

Configuration :

1) Configuration of the local IP address :

The IP addresses must be administered, "IP address configured" mode is selected, theuser must enter the IP parameters.

2) Connection configuration window

The Premium PLC is only used in server mode, the user does not need to configurethe X-WAY and IP addresses of the remote Quantum PLC. The connection to beconfigured is the one with the programming terminal as access control is enabled.

3) Ethernet configuration

The Ethernet frame format selected for TCP-IP is Ethernet II as the terminals use thisformat.

Debug mode :

The options offered by debug mode are the same as those described in example 1.


___________________________________________________________________________

J

J1/43

1.13-2 Communication with a Premium client PLC

The procedure is identical to the previous example, except that the PLC operates inclient mode. As it must send in client mode, the local X-WAY address and the IP addressof the remote Quantum PLC must be configured.

Click the "access control" box to activate the check, then check the corresponding boxin the "access authorized" column. The maximum number of connections in theapplication can be adjusted.

___________________________________________________________________________

J

J1/44

1.14 Performance

The performance statistics given below are for communication between two PLCequipped with TSX 57-30 processors. The values are given in ms and represent anaverage duration of the time described in the table.

Time taken to open a TCP-IP connection 10ms

Transaction time for a UNI-TE request of 128 bytes 150msin 50ms periodic mode

Transaction time for a UNI-TE request of 128 bytes 80msin 4ms cyclic mode

Transfer time for common words (both directions) 250msin 50ms periodic mode

Module transit time 15 to 30ms

1.15 Communication limits

• 32 connections maximum on TCP-IP

• UNI-TE messages of 256 bytes maximum with synchronous message handling, and1 Kbyte with asynchronous message handling

• 16 messages maximum processed simultaneously on TCP-IP

• 16 messages maximum processed simultaneously on Ethway

• maximum capacity of the module :130 msg / s for ETHWAY message handling140 msg / s for X-WAY message handling on TCP-IP100 msg / s for Modbus message handling on TCP-IP

• Common words :A common words message is equivalent to 0.5 msg of data.Example of an application size :5 stations exchange common words every 100 ms together with X-WAY messageson TCP-IP.The flow rate of common words received by each module is therefore 50 msg / s ofcommon words or approximately 25 msg / s on TCP-IP.The remaining maximum capacity on each module on TCP-IP is therefore :140 - 25 = 115 msg / s.

Recommendation : On TSX Premium, the common words are sent at the beginningof the next scan after they have been updated by the application.In order to optimize the performance of common words, it is therefore recommendedto work in cyclic mode or to adjust the period of the PLC MAST task to the maximumexecution time of the application.

___________________________________________________________________________1

K

Multi-network architectures Contents

Section Page

1 Multi-network architectures 1/1

1.1 General 1/1

1.2 Functions 1/2

1.3 Configuration 1/31.3-1 Configuring single network services 1/41.3-2 Configuring multi-network services 1/4

1.4 Examples of multi-network architectures 1/71.4-1 Bridge station 1/71.4-2 Multi-module station 1/91.4-3 Partial routing 1/10

1.5 Exchange services 1/121.5-1 Common words services 1/121.5-2 Shared table exchange service 1/131.5-3 Message handling 1/14

___________________________________________________________________________

2

K

Multi-network architectures Contents

Section Page

Multi-network architectures 1

___________________________________________________________________________K1/1

K

Section 11 Multi-network architectures

1.1 General

A multi-network architecture is made up of several networks.

There are two different levels of architecture :

• Multi-module network architectures in which several segments are present, but nocommunication between these different segments is offered by the communicationsystem.

• Multi-network architectures made up of several network segments interconnectedby "bridge" stations. Transparent communication is offered between all the devicesin this type of architecture.

This section describes the setup of the bridge function in a TSX 57.. PLC station, as wellas the use of communication services in a multi-network architecture. Multi-networkarchitecture conforms to X-WAY communication standards.

For the installation of stations on the various networks, refer to the relevant documen-tation for the module used.

K1/2___________________________________________________________________________

K

1 2

3 4

1

2

1

2

1.2 Functions

An X-WAY multi-network control system architecture is made up of several levels ofnetworks which interconnect via intermediate stations.In a multi-network architecture,a single logical link must exist between two end stations.

Example :

End stations :An end station is addressed by the module {network address . station address}.End stations receive the messages destined for their network address as well asgeneral broadcast messages, and send all the messages destined for a remote stationto their network connection.

Intermediate stations :An intermediate station has as many network addresses as connection points todifferent networks. One of its addresses is known as the main address. This addressensures access to all bridge station communication entities.

Intermediate stations are divided into two categories :

"Multi-module" stationsThese manage several network modules and provide all the single network serviceson the various network segments (common words, telegrams (*), messagehandling).They do not offer a routing function between the various network connec-tions.(*) The telegram exchange service is only offered on the FIPWAY link managed by aPremium or Micro processor.

"Bridge" stations :These provide the same services as multi-module stations and ensure communicationtransparency between the various network connections.Note : a station can provide the bridge function between two networks and the multi-modulefunction between two other networks simultaneously.

station{1.1}

station{1.2}

station{3.2}

station{2.2}

station{1.3} and {2.1}


network #1


end stations

intermediate stations

end stations


___________________________________________________________________________K1/3

K

station{1.3} and{2.1}

network #2

1 2

3 4

1

2

1

2

network #1

1.3 Configuration

In an intermediate station, the management of several network modules requires aconfiguration phase to distribute the operating characteristics to the various networkentities.

Multi-network routing data is compiled at station level during PL7 configuration ofeach bridge. No consistency check is performed on routing data in the samenetwork architecture.

station{1.1}

station{1.2}

station{3.2}

station{2.2}


network #3

end stations

end stations

PL7 station configuration

intermediatestations

K1/4___________________________________________________________________________

K

1.3-1 Configuring single network services

The PL7 application-specific configuration screen (FIPWAY, ETHERNET) is used toenter the information required for the operation of the different types of exchanges onthe network : telegrams, common words, shared tables, single station messagehandling.Common word and shared table exchanges are exclusive on a network. However, itis possible to vary them in a multi-module configuration. A station can, for example,participate in a common word exchange on one network, and a shared table exchangeon its second network attachment.Telegrams can only be used on the Fipway channel managed by the PCMCIA card onthe processor host channel.

1.3-2 Configuring multi-network services

Multi-network routing data is compiled at station level during PL7 configuration ofeach bridge. No consistency check is performed on routing data in the samenetwork architecture.

In a station which supports several network modules, each network connection pointis considered as an address for the station. When configuring each module, thenumbers of the networks which can be accessed must be defined for each connectionpoint.

Depending on the processor selected during hardware configuration, a bridge stationcan only manage 3 or 4 network modules. The table will thus have a maximum of 4elements.A special screen is used to enter routing data for all station network modules. It can beaccessed via the FIPWAY or ETHWAY configuration screens.


___________________________________________________________________________K1/5

K

Example of a configuration screen for a processor host channel :

Example of a configuration screen for a network module :

In the screens, a button :

gives access to the screens which are used to define the networks which can beaccessed. A list of numbers from 1 to 127 represents the networks available for aconnection point. Each network number selected as accessible is removed from thelist to avoid configuration errors.

K1/6___________________________________________________________________________

K

Clicking on the "Bridge" button and then on the selected module opens the followingdialog boxes :

These windows are used to define a bridge with 3 connection points for a TSX 57-302/352 processor. They are used to enter the list of networks which can be accessed bythis module. In the "Selection of networks which can be accessed" window, the or

buttons are used to add or delete a network. "OK" confirms the module configuration.In the "Bridge Configuration" window, the "Cancel" button is used to delete the entryfor the address confirmed previously. The "Save" button is used to confirm the multi-network configuration entered. The "Delete" button is used to delete the entireconfiguration entered for the module.To configure a bridge, the same number of windows should be active as there aremodules.PL7 carries out consistency checks on module addresses and declaration of functionchecks for other modules. A message appears giving details of each error detected.Itis not possible to confirm a module configuration while an error remains uncorrected.


___________________________________________________________________________K1/7

K

41

6

ETHERNET

FIPWAY

UNI-TELWAY

FIPWAY

FIPWAY

A

B

C

FIPWAY

1 2

3 4

4

7

5

0 5 2 4 5

56

1.4 Examples of multi-network architectures

1.4-1 Bridge stationA station configured in bridge mode has as many addresses as network connectionpoints. The network address corresponding to the network module with the lowestmodule address (module furthest to the left in the station rack) is considered to be themain station address. Using the main station address ensures access to a bridgestation.

Rule: a bridge station must always be accessed by its main address.

Examples of addressing :Communication between stations connected on Fipway networksA ----> B : {11.4}.SYS main address of R1 = {11.4}A ----> R1 : {12.7}.SYS main address of R1 = {12.7}B ----> R3 : {13.5}.SYS main address of R3 = {13.5}A ----> C : {12.7}.5.0.56 main address of R1 = {12.7}

network #1


network #13

network #21

R1R2

Processor

TSX SCY 21601

TSX ETY 110

R3

K1/8___________________________________________________________________________

K

Configuring each station in full bridge mode :

Each station must be configured in order to define the list of networks which can beaccessed. In accordance with the previous example :Screen for bridge R1

Screen for bridge R2



___________________________________________________________________________K1/9

K

ETHERNET

FIPWAY

FIPWAY

A

B

2

4

7

2 4 5

5

1.4-2 Multi-module station

In the following example, station R1 does not have a bridge function between modules2,4,5.

Example : B ----> R1 {13.5}.SYSA ----> R1 {12.7}.SYS

Rule : a multi-module station must always be accessed by the network addresscorresponding to the network module which allows entry to the station.

network #12

network #13

station R1

K1/10___________________________________________________________________________

K

41

ETHERNET

FIPWAY

UNI-TELWAY

FIPWAY

FIPWAY

A

B

C

FIPWAY

1

56

3 4

4

7

5

6

0 3 2 4 5

2

1

1.4-3 Partial routing

Based on the bridge station example (in 1.4-1), FIPWAY network #12 is no longer takeninto account in multi-network routing.

As before, the bridge stations must be configured taking account of the module(s)participating in routing. The module at position 2 in the rack of station R1 is notparticipating in routing.The main address for bridge station R1 becomes : {1.2}.

Rule : the two rules described on the preceding pages apply to a partiallybridged station.

network #1

network #11

network #12

network #13

network #21

R1R2

R3


___________________________________________________________________________K1/11

K




Routing screens for stations :

K1/12___________________________________________________________________________

K2

4

4

1.5 Exchange services

The exchange services described in this section concern a bridge or multi-moduleintermediate station.

1.5-1 Common words services

Common word exchanges are only available for single networks; they are linked toeach module. There can therefore be as many common word zones as there arenetwork modules in a station. The access syntax for common words in a configurationis as follows :

%NW {network no. . station no.} word no.

Common word exchanges are managed by the PLC system.

The update bits associated with each zone of exchanged words are :


%IW m.v.0.x network status x = 1 if at least one station is present

%IW m.v.1 network station 0 ... station 15

%IW m.v.2 station station 16 ... station 31*

%IW m.v.3 update station 32 ... station 47*

%IW m.v.4 indicators station 48 ... station 63*

(*) limited to station 31 on FIPWAY

Example :

In the example opposite,the station has twocommon word productionzones. The networknumber is used todistinguish which zone hasbeen accessed.On network 3 it produces 4words : %NW {3.2}0..3. Theupdate bits are stored inwords : %IW 4.1.1.., %IW4.1.2On network 1 it produces 4words : %NW {1.4}0..3. Theupdate bits are stored inwords : %IW 0.1.1.., %IW0.1.2

common word zone %NW{3.2}0...3

common word zone %NW{1.4}0...3

network #1

network #3%NW{3.2}0...3

%NW{1.4}0...3


___________________________________________________________________________K1/13

K

1.5-2 Shared table exchange service

The shared table exchange is mutually exclusive with the common word exchange.Shared table exchanges are only possible on single network architectures. On aFIPWAY network, the first 32 stations produce 1 to 32 words, the data exchange mustbe equal to 128 words. The exchange zone is in the %MW defined by the PL7application. In a multi-network application, several shared tables can be present, oneper network.Each zone in the table has an associated update bit which indicates the status of theproducer of a common word zone. Bit i = 1 if the station has produced its shared tablezone. This information is updated periodically by the system.


%IW m.v.0.x network status x = 1 if at least one station is present

%IW m.v.1 network station station 0 ... station 15

%IW m.v.2 update indicators station 16 ... station 31

The zone between words%MW10 and %MW137corresponds to the sharedtable exchanged onnetwork 3.Only words %MW20 to%MW30 are produced onthe network by the station,the other words are theimage of the words sent byother stations.The zone between words%MW200 and %MW337corresponds to the sharedtable exchanged onnetwork 1.

2

4

4

shared table on network 3

shared table on network 1

%MW 10. . . . .

% M W 2 0. . .% M W 3 0

. . . . .% M W 1 3 7

% M W 2 0 0. . . . .

% M W 2 1 0. . .% M W 2 3 0

. . . . .% M W 3 3 7

network #3

network #1

K1/14___________________________________________________________________________

K

2

4

4

1.5-3 Message handling

Multi-module station : messages destined for a network are sent to the moduleconnected to the destination network. The configuration phase is used to define thedestination module. Special case : messages destined for a network with an unknownaddress are sent to the main station network, as are messages whose network numberis 0.

The main station network is managed by the module with the lowest moduleaddress in the station (module furthest to the left in the rack).

Example :

All messages destined for network #3 are sent to the module at address 4, and thosemessages for which the destination network is 1 are sent to the network link integratedin the processor.All messages where the network number address is different from 1 or 3 are sent to theprocessor which manages the main network.In a multi-module architecture, communication is limited to a single network level.

network #1

network #3

READ_VAR(ADR#{3.2}.4.1,...)

READ_VAR(ADR#{2}.SYS,...)READ_VAR(ADR#{1.2}.SYS,...)READ_VAR(ADR#{15.2}.SYS,...)


___________________________________________________________________________K1/15

K

2

4

4

Bridge station :A bridge station has as many addresses as network connection points.

The network address corresponding to the module with the lowest module addressis considered to be the main station address.

Addresses {3.2} and {1.4} identify the station in its network architecture. Address {1.4}is its main address.Special case : messages where the network number equals the default networknumber (no.0) are sent to the main network address.

network #1

network #3

station{3.2}and{1.4}

K1/16___________________________________________________________________________

K

Index 10

___________________________________________________________________________P/1

B

P

IndexCommunication

Index

AAddressing A1/6

Broadcast addresses A1/7Examples of addressing A1/11Introduction A1/7Principles A1/6Remote addresses A1/7

CCANCEL A2/48Character mode communication C1/1

Configuration mode C1/2Debug mode C1/8Introduction C1/1Language interface C1/10Operating modes C1/12Performance C1/13Terminal port C1/14

Communication function A1/1Definition A1/1

Communication functions A2/15CANCEL A2/48DATA_EXCH A2/31INPUT_CHAR A2/42OUT_IN_CHAR A2/45PRINT_CHAR A2/39RCV_TLG A2/37READ_Asyn A2/55READ_GDATA A2/52READ_VAR A2/15SEND_REQ A2/28SEND_TLG A2/34SERVER A2/54WRITE_Asyn A2/55WRITE_GDATA A2/53WRITE_VAR A2/23

Communication tools A2/1Communication via UNI-TELWAY Bus D1/1Compatibility of communication A2/58Configuration screen A3/7

Configuring the communication function A3/1Accessing the configuration tool A3/1Choosing the communication modulesA3/4Choosing the processor A3/2Configuration screen A3/7

DDATA_EXCH A2/31Debug mode H1/42Debug screen A3/8

EETHERNET J1/1

Addressing J1/1Common words J1/19Communication test window J1/15Configuring ETHWAY services J1/10Configuration mode J1/4Configuring TCP-IP services J1/5Debug mode J1/12Debugging common services J1/12ETHWAY services J1/13Examples J1/30Introduction J1/1Language interface J1/16Managing connections TCP J1/27Managing IP parameters J1/20, J1/27Message handling J1/23Modbus communication on TCP-IP J1/14Modbus onTCP-IP J1/24Opening a connection J1/21Performances J1/44Station test window J1/14TSX ETY 110 module operatingmodes J1/29

Examples of intra-station addressing A1/11

P/2___________________________________________________________________________

P

FFIPIO Agent H3/1

Addressing H3/7Configuring H3/1Debug screen H3/8Introduction H3/1Language objects H3/4

FIPIO Bus communication diagnosticsH1/44FIPIO H1/1

Configuring mode H1/10Cyclic task H1/38Device monitoring H1/47Diagnostic of device faults H1/20Examples H1/34Introduction H1/1Language interface H1/19Limitations of explicit exchanges H1/33Managing the E/S H1/37Managing the FIPIO bus H1/52Maximum configuration H1/7Monitoring the communication H1/49Monitoring the FIPIO bus H1/46Network single time H1/55Operating mode H1/31Sequence of the diagnostic screens H1/45System bits and words H1/23Topological addressing H1/6

FIPWAY Communication I1/1Common words I1/14Configuration mode I1/2Debug mode I1/5Examples I1/14Introduction I1/1Language interface I1/8Operating modes I1/12Performances I1/13Shared table I1/17

HHelp with entering communication functions A2/8

IInitial connection to an application A1/15INPUT_CHAR A2/42

LLanguage interface A1/3Language objects common

to all communication channels A1/4to all communication modules A1/3

Limitation of communication functions A2/12List of communication functions A2/7

MManagement parameters A2/2

Activity bit (bit 0) A2/3Communication report A2/3, A2/4Length A2/6Operation report A2/5Word number A2/3

Modbus E1/1Communication function E1/16Compatibilities E1/20Configuration mode E1/2Debug mode E1/9Introduction E1/1Language interface E1/13Operating modes E1/19Performances E1/21

Modbus+ G1/1Configuring the network G1/5Debugging G1/7Global data exchange functions G1/16Integration in a Modbus plus architecture G1/19Integration in an X-WAY architecture G1/17List of the counters G1/15Language objects G1/20Protocol G1/8

Modem F 1/1AT commands F 1/31CALL_MODEM F 1/20Character modes F 1/12Coding exchanges F 1/30Communication function F 1/20Configurations F 1/1Configuration mode F 1/8

Index 10

___________________________________________________________________________P/3

B

P

Debug mode F 1/13Functions F 1/6Guide to choosing the operatingpararemeters F 1/27Introduction F 1/1Language interface F 1/15Limits F 1/6Parameters F 1/10Principle F 1/3Set-up F 1/4Transaction report F 1/23, F 1/25, F 1/26UNI-TELWAY mode F 1/8

Multi-network architectures K1/1Bridge station K1/7, K1/15Common words services K1/12Configuring multi-network services K1/4Configuring single network services K1/4Configuration K1/3Examples K1/7Functions K1/2General K1/1Message handling K1/14Multi module station K1/9Partial routing K1/10Shared table exchange service K1/13

NNumber of application specificcommunication channels A1/9

OOUT_IN_CHAR A2/45

PPRINT_CHAR A2/39

RRCV_TLG A2/37READ_Asyn A2/55READ_GDATA A2/52READ_VAR A2/15Remote location of nano-PLCs B1/1

Addressing B1/3Application data exchanges B1/2Configuration mode B1/10Converting the analog values B1/8Data exchange with an analog moduleB1/4Debug mode B1/12Example of communication B1/20General B1/1I/O data exchanges B1/1Language interface B1/14Module operating modes B1/16Performances B1/17

ROR1_ARB A2/50

SSEND_REQ A2/28SEND_TLG A2/34SERVER A2/54Standard profiles H2/1

Accessing a standard profile H2/5Adjust mode H2/14Choosing a standard profile H2/2Configuration mode H2/12General H2/1Language objects H2/7

Structure of a communication function A2/2Destination address A2/2Management parameters A2/2Specific parameters A2/2

SWAP A2/51

P/4___________________________________________________________________________

P

UUNI-TELWAY

Configuration mode D1/15Debug mode D1/20Example of exchanges D1/6Introduction D1/1Language interface D1/23Limits D1/28Module operating modes D1/27Performances D1/28Slave PLC addresses D1/2Terminal port D1/29

Using text blocks A2/59

VVolume of data exchanged H2/1

WWRITE_Asyn A2/55WRITE_GDATA A2/53WRITE_VAR A2/23

tlx dscom pl7 general and communication tools...

Documents