industrial ethernet on pci2000eth (tcp/ip and iso layer 4

electrical & safety · industrial connectivty · software & electronics · advanced connectivity

WoodheadWoodhead

IndEth.doc 04/09/2003

Copyright © 2003 Woodhead Software & Electronics. All rights reserved.

http://www.applicom-int.com

Protocol manual

Industrial Ethernet on PCI2000ETH (TCP/IP and ISO layer 4) and

SW1000ETH (TCP/IP)

applicom® 3.7

a product of Woodhead Software & Electronics


WoodheadWoodhead

IndEth.doc 04/09/2003 Copyright © 2003 Woodhead Software & Electronics. All rights reserved. applicom®, Direct-LinkTM, RJ-LnxxTM, SSTTM are registered trademarks of Woodhead Software & Electronics. Other product names are trademarks of their respective owners.

http://www.applicom-int.com


WoodheadWoodhead

Industrial Ethernet on PCI2000ETH (TCP/IP and ISO layer 4) and SW1000ETH (TCP/IP) • i • Table of contents

Table of contents

1. - Generalities ..................................................................................1 - OSI model .............................................................................................................1 - Functionality ..........................................................................................................3 - Client multi-request management .........................................................................5 - Request processing. .............................................................................................6

2. – Description of the applicom® console......................................7

3. - General configuration .................................................................8 - Ethernet : General.................................................................................................8 - Ethernet : Ethernet ..............................................................................................10 - Ethernet: SIMATIC..............................................................................................12 - TCP/IP properties : Advanced tab ......................................................................15

4. - SIMATIC® S5 (READ/WRITE S5 messaging)............................18 - Functionality ........................................................................................................19 - Configuration.......................................................................................................26 - Siemens equipments implementation .................................................................30 - applicom® functions usable on the master channel ...........................................49 - Item of image variables.......................................................................................51

5. - SIMATIC® S7-400, S7-300 (S7 messaging)...............................72 - Functionality ........................................................................................................73 - Configuration.......................................................................................................85 - Implementation of Siemens SIMATIC® S7 equipments......................................91 - Implementation of Siemens SIMATIC® S7-200 equipment with the CP243-1 coupler.................................................................................................................102 - applicom® functions usable on the master channel .........................................114 - Item of image variables.....................................................................................116

6. - SIMATIC® TI-505 (Camp and Read/Write TI messaging).......126 - Functionality ......................................................................................................128 - Configuring a SIMATIC® TI-505 server equipment ...........................................135 - Configuring a SIMATIC TI-505 client equipment ..............................................139 - Implementation of Siemens SIMATIC® TI-505 equipment on TCP/IP..............141 - Implementation of Siemens SIMATIC® TI-505 equipment on ISO ...................146 - applicom® functions usable on the master channel .........................................152 - Item of image variables : Presentation..............................................................154 - Item of image variables : Standard descriptor ..................................................154 - Item of image variables : SIMATIC® TI-505 descriptor .....................................158

7. - Appendices ..............................................................................170 - Evolution / compatibility.....................................................................................170 - TCP/IP appendix ...............................................................................................173

8. - Glossary ...................................................................................178


WoodheadWoodhead

Industrial Ethernet on PCI2000ETH (TCP/IP and ISO layer 4) and SW1000ETH (TCP/IP) • ii • Table of contents

9. - Index .........................................................................................180


WoodheadWoodhead

Industrial Ethernet on PCI2000ETH (TCP/IP and ISO layer 4) and SW1000ETH (TCP/IP) • 1 • - Generalities

1. - Generalities

- OSI model "Industrial Ethernet" is the new name of the SIEMENS communication system previously known

as SINEC H1. Industrial Ethernet includes all protocols supported by the SIEMENS PLCs on Ethernet : i.e. the

ISO CONS (International Standards Organisation Connection-Oriented) and TCP/IP (Transmission Control Protocol / Internet Protocol) transports.

This open communication system is located in the operation and cell automation levels.

��

��

��

��

��

��

��

�� !�

��

"��#��#

��!�$%��

�� &�&�� '�(�& �)

��*��+ ��

� �$%�,��

��'��#� �� $%�,��(��"�-�.)

��

��/��*�0� �� '��0�,,,

��

��

��!��12��%%�

��"�

�1�

��0�1��'-3�� '��0��"�

��

��

Figure 1 : applicom® Industrial Ethernet functionality faced with the OSI model


WoodheadWoodhead


applicom® uses the following specifications : The ISO transport is based on the specifications of the "class 4 ISO transport service". Siemens

does not use layer 3 in ISO. All TCP/IP protocols are made according to the RFCs (Request For Comments). However, an

"ISO on TCP" layer, extension of TCP/IP for transmission of messages (data blocks) is necessary :

Class 4 ISO TCP/IP

Layer 4 Class 4 ISO 8073ISO ADDUM 8073

ISO on TCP : RFC 1006TCP : RFC 793

Layer 3ICMP : RFC 792

IP : RFC 791ARP : RFC 826

Layer 2 b IEEE 802.2 LLC Ethernet IILayer 2 a IEEE 802.3 CSMA/CD IEEE 802.3 CSMA/CD

Layers 5 and 6 are not used. Remark: ISO class 4 mode is not supported by the SW1000ETH solution.


WoodheadWoodhead


- Functionality The Industrial Ethernet solution on applicom® supplies the following functionalities :

��

��%%% �4

��

��

��

��

��

��

!�

�"�

��

�

Figure 2 : applicom® client/server functionalities Multi-request Client Mode to the Siemens PLCs in the SIMATIC® range

Messaging supported depending on the range and the couplers :

System range Module CP Ethernet

Protocols Messaging service(application layer)

S5 115/135/155U CP143CP1430

CP1430 TCP

ISO transportISO transportISO on TCP

READ/WRITE S5READ/WRITE S5READ/WRITE S5

S7-200 CP 243-1 ISO on TCP S7 messagingS7-300 CP 343-1

CP 343-1 TCPISO transportISO on TCP

S7 messagingS7 messaging

S7-400 CP 443-1CP 443-1 TCP

ISO transportISO on TCP

S7 messagingS7 messaging

TI-505 CP 1434 ISO transport READ/WRITE TICP 2572 TCP CAMP messaging

Reading and writing variables in the various PLC memory areas (inputs, outputs, DB, Memories, etc.),

Remark: ISO class 4 mode is not supported by the SW1000ETH solution.

Server mode for PLC clients :


WoodheadWoodhead


SIMATIC® S5 (READ/WRITE S5 messaging) SIMATIC® S7 (S7 messaging) SIMATIC® TI-505 on TCP/IP (CAMP messaging) SIMATIC® TI-505 on ISO (READ/WRITE TI messaging)

Management of memory areas in the applicom® database and equipment monitoring. The Industrial Ethernet solution on applicom® is based on a transport layer which can be ISO and/or TCP depending on the targeted coupler and SIMATIC® messagings depending on the targeted PLC. Consequently, the following chapters deal with the common sections (Ethernet channel, TCP, etc.) and the separate messagings (functionalities, configurations, etc.). Redundancy of equipment: enables the application to dynamically change the target

equipment. (see chapter Functions for Redundancy of Equipment). Remark: equipment redundancy is not supported by the SW1000ETH solution.


WoodheadWoodhead


- Client multi-request management The applicom® client mode can be used to send several requests simultaneously to an equipment before having received the first response : this operation is called multi-request. A request is sent on a virtual communication channel. Each virtual channel corresponds to an ISO or TCP connection on an equipment. To send several requests simultaneously, several connections are used.

��

��%%% �4

��

��

��

��

��

��

��

��

��

��

��

�� !"�#!��#��!��

�

�

��

Figure 3 : Multiple connections and multi-request The connections are created according to needs, and existing connections are reused whenever possible. For example: a request is sent to an equipment for the first time. Connection No. 1 is created. Some time later, 2 requests must be sent to the equipment: connection No. 1 is reused and connection No. 2 is created. The applicom® interface manages 128 connections (64 with SW1000ETH). Only 30 of them can be used simultaneously for all equipments. The maximum number of connections which can be used simultaneously for this equipment is set in the configuration for each equipment. A connection remains open as long as data is travelling or a connection servicing process is active.


WoodheadWoodhead


- Request processing.

��$$�%�� &��#��!�

'��(��# ��

)��!��!�� !�

)��!��(��!#��

��#!�

�!��#��!��# ��

A request being processed is a request for which a frame has been sent on the network and for

which a response is expected. Each request being processed uses a virtual communication channel. A request is placed (temporarily) on hold when there are no more virtual channels available. When

virtual channels are released, the list of requests on hold is progressively emptied.


WoodheadWoodhead

Industrial Ethernet on PCI2000ETH (TCP/IP and ISO layer 4) and SW1000ETH (TCP/IP) • 7 • – Description of the applicom® console

2. – Description of the applicom® console

To use the applicom® console, please refer to the "Implementation/Configuration Principle"

manual.


WoodheadWoodhead

Industrial Ethernet on PCI2000ETH (TCP/IP and ISO layer 4) and SW1000ETH (TCP/IP) • 8 • - General configuration

3. - General configuration

- Ethernet : General

Figure 4 : Ethernet connection : General

Request Time-out Maximum time separating the transmission of a request by the applicom® Industrial Ethernet client from the response by the server. When the equipment does not answer within this time-out, the current request returns status 55 « Message lost » Value in seconds, from 2 to 255, default value 10.

Maximum number of simultaneous requests Sets the maximum number of requests being processed. Above this figure, the requests are placed on a waiting list until a request being processed is released.

The number of requests being processed indicates a number of requests sent simultaneously on the network. This requests contribute to the network load. By modifying the maximum number of requests being processed, this load can be regulated. Two cases may then arise for applications including an applicom® interface and PLCs : dedicated network : the maximum number of requests being processed proposed by default

optimizes the performance of the communication support.


WoodheadWoodhead


network shared with workstations : in case of network overload (>30%), reduce the maximum number of current requests. This is carried out to preserve the pass band for the other stations.

Value from 1 to 32, default value 24 (default value 16 in multi-messaging).

Access status words in DATA-BASE Check the « Active functionality » box to validate operation and specify the storage address of the 60 « access status words » in the applicom® database. Value from 0 to 31935, default value 0. This option is used to monitor the access interval of the client equipment to the applicom® server mode. If the « Access monitoring time-out » configured in the equipment (see configuration of client equipment) is exceeded, the applicom® interface will indicate its absence in the word corresponding to the client equipment number.

1st word Client equipment number 0 .. 60th word Client equipment number 59

Value of the access status word : 00 :OK, the equipment accesses the applicom® server in the defined time, 14 :Data inaccessible, the client equipment accesses inaccessible data in the

applicom® server, 233 :Time-out, the client equipment does not access the applicom® server within the

defined time, 3 :Equipment number not configured.

Access indicator words in DATA-BASE Check the « Active functionality » box to validate operation and specify the storage address of the 60 « access indicator words » in the applicom® database. Value from 0 to 31935, default value 0. All write access by a client equipment to the applicom® server will be indicated by incrementing the word corresponding to the number of the client equipment configured.

1st word Client equipment number 0 .. 60th word Client equipment number 59

This word has a maximum value of 65535; you must reset this value so that the word can count the accesses again .


WoodheadWoodhead


- Ethernet : Ethernet

Figure 5 : Ethernet : Ethernet

Connection type This choice determines which type of physical interface is used (DB15 or RJ45 connector) : AUI (Attachment Unit Interface) : DB15 connector to connect a transceiver (drop cable or direct transceiver), 10 Base T/RJ-45 : integrated transceiver, star topology, double twisted pairs RJ45 connector, SIMATIC NET® ITP : Industrial Twisted Pair, developed by Siemens using the DB15 connector without having to connect a transceiver. Remark: this parameter does not exist in the SW1000ETH solution.

Baud rate (PCI2000ETH version B only) Allow you to select the baud rate if the connection type is RJ45 or SIMATIC-NET ITP. The choice « auto 10/100Mb » squares with an automatic detection of the baud rate. Default baud rate: 10Mb with the AUI connection type and « auto 10/100Mb » with the RJ45 and SIMATIC-NET ITP connection type. Remark: this parameter does not exist in the SW1000ETH solution.

Connection lifetime Maximum inactivity time for an ISO or TCP connection. A connection is active when data is transiting or when it is being serviced (automatic procedure in ISO and configurable in TCP). After this time, the connection is closed, in order to avoid overloading connections (max. 128) when the partner is absent. Value in minutes, from 2 to 60, default value 3.


WoodheadWoodhead


Channel Ethernet address

Address on 6 bytes defining the Ethernet channel uniquely on the network. Manual input (« Automatic calculation » not checked ): Enter the Ethernet address in hexadecimal. if you enter an address, then the address which will be used is the one you entered. This means that an Ethernet board can be replaced without having to reconfigure its partner's address in the client station (valid for layer 4 ISO). Automatic address calculation : This address can be calculated automatically from the applicom® IEEE address and the board serial number :

0

IEEE InterfaceAddress serial number

applicom ® (in Hexadecimal)00 A0 91 xx xx xx

The serial number is indicated by labels on the applicom® interface (on the rear plate and on the copper) or visible when initializing the interface (« pcinit »). Example : Ethernet address of an applicom® interface bearing serial number 20100 i.e. 4E84 Hexadecimal.

00 A0 91 00 4E 84 Remark: this parameter does not exist in the SW1000ETH solution.


WoodheadWoodhead


- Ethernet: SIMATIC

Figure 6 : Ethernet : SIMATIC S5

Parameters for SIMATIC S5 : only if a SIMATIC S5 client is used. Parameters for SIMATIC TI : only if a SIMATIC TI client is used.

Parameters for SIMATIC S5

Local TSAP in read This choice is used to define the name of the TSAP (Transport Service Access Point). It offers client equipments read access to the DATA-BASE server. This TSAP must also be defined in the configuration of the client PLC coupler. Configuration of PLC couplers CP 1430 and CP1430 TCP: Contract FETCH active. Ethernet address Identical to that defined in the « Ethernet address field of the board » (CP143 or CP1430). IP address Identical to that defined in the « IP address field of the applicom® channel » (CP1430 TCP). Local TSAP ID String of 8 characters identifying the link. Remote TSAP ID Identical to this field (READREAD by default).

Local TSAP in write This choice is used to define the name of the TSAP. It offers clients read access to the DATA-BASE server. This TSAP must also be defined in the configuration of the client PLC coupler. Configuration of PLC couplers CP 1430 and CP1430 TCP: Contract SEND passive.


WoodheadWoodhead


Ethernet address Identical to that defined in the « Ethernet address field of the board » (CP143 or CP1430). IP address Identical to that defined in the « IP address field of the applicom® channel » (CP1430 TCP). Local TSAP ID String of 8 characters identifying the link. Remote TSAP ID Identical to this field (WRITWRIT by default).

Parameters for SIMATIC TI

Local TSAP in read This choice is used to define the name of the TSAP (Transport Service Access Point). It offers client equipments read access to the DATA-BASE server. This TSAP must also be defined in the configuration of the client PLC coupler. Configuration of PLC couplers CP 1434 : Contract Read passive. Ethernet address Identical to that defined in the « Ethernet address field of the board » (CP 1434). Local TSAP String of 8 characters identifying the link. Remote TSAP Identical to this field (READTSAP by default).

Local TSAP in write This choice is used to define the name of the TSAP. It offers clients read access to the DATA-BASE server. This TSAP must also be defined in the configuration of the client PLC coupler. Configuration of PLC couplers CP 1434 : Contract Write passive. Ethernet address Identical to that defined in the « Ethernet address field of the board » (CP 1434. Local TSAP String of 8 characters identifying the link. Remote TSAP Identical to this field (WRITTSAP by default).


WoodheadWoodhead


- TCP/IP properties : General

See "- TCP/IP appendix" on page 173 in the appendices for further details. Remark: this dialog box does not exist in the SW1000ETH solution.

Figure 7 : TCP/IP properties

The « Advanced parameters » button provides access to expert settings for TCP/IP.

applicom® channel IP address

Zone of 4 bytes entered in pointed decimal notation representing the Internet address or IP address of the applicom® board channel.

Gateway IP address IP address of a machine likely to perform a routing to another network (internal or external).

Sub-network mask Used to define the addresses to be routed by the gateway. Value 0.0.0.0 to 255.255.255.255, 255.255.255.0 by default.


WoodheadWoodhead


- TCP/IP properties : Advanced tab For further details, consult "- Time-out TCP" on page 176..

Figure 8 : TCP/IP advanced parameters

Number of retries Number of times that the applicom® board attempts to retransmit a non-acknowledged TCP packet. Value from 1 to 12, default value 2.

Interval between retries

Maximum time between two retries. The time between retries increases on every attempt. This parameter related to the number of retries, can therefore be used to determine a global time-out for transmission of a TCP packet. Value in seconds, from 1 to 5, default value 1. If a TCP packet is not acknowledged and terminates in time-out, the connection is closed and the function then returns a status 33 "Time-out"

Connection servicing Activation of the TCP/IP « keep alive » function used to keep the TCP connections open with a periodic check that the partner is present.


WoodheadWoodhead


- Equipment properties Generally, all server or client equipments will be composed of a common «Device Description» for

all equipment types, a «Network parameters » zone to enter the equipment address, and lastly a « Messaging parameters » zone specific to each equipment type.

applicom® description

Figure 9 : Server equipment properties

Topic name Enables OPC and DDE servers to access variables for this device. For more information, please refer to the "DDE and OPC Servers" manual.

Equipment number applicom® equipment number to be chosen from the list of non-configured equipments. Value: from 000 to 127 for the server equipments, from 000 to 59 for the client equipments.

Link parameters

Tick this box to activate the link between the device number and the device's IP address: the device number will then correspond to the station number of the IP address. Depending on the device type, this number may be linked to another one of the messaging parameters.

Active configuration

Check box to activate the equipment configuration in the applicom® interface : used to delete an equipment from the applicom® interface whilst keeping its configuration in the console.

Comment

Free text about an equipment. The maximum number of characters is 80.

Network parameters These parameters depend on the transport layer used : TCP/IP : IP address of the partner equipment.


WoodheadWoodhead


Figure 10 : IP network parameters Layer 4 ISO :

Ethernet address of the partner equipment.

Figure 11 : ISO network parameters Remark: this parameter does not exist in the SW1000ETH solution.

Messaging parameters These parameters are detailed in the documentation specific to the messaging used (see the following chapters).


WoodheadWoodhead

Industrial Ethernet on PCI2000ETH (TCP/IP and ISO layer 4) and SW1000ETH (TCP/IP) • 18 • - SIMATIC® S5 (READ/WRITE S5 messaging)

4. - SIMATIC® S5 (READ/WRITE S5 messaging)

- Functionality........................................................................................................19

- Industrial Ethernet client........................................................................ 19 - Estimating the performance of an applicom® Industrial Ethernet Client. ...... 22 - Industrial Ethernet server ...................................................................... 24

- Configuration.......................................................................................................26 - Configuring a SIMATIC® S5 server equipment........................................... 26 - Configuring a SIMATIC S5 client equipment.............................................. 28

- Siemens equipments implementation.................................................................30 - PLC under Industrial Ethernet READ/WRITE protocol ................................. 30

- applicom® functions usable on the master channel...........................................49 - Wait mode ........................................................................................... 49 - Deferred mode ..................................................................................... 49 - Cyclic mode.......................................................................................... 50

- Item of image variables.......................................................................................51 - Presentation......................................................................................... 51 - Standard descriptor............................................................................... 52 - Siemens Simatic S5 PLCs descriptor - German (D) and French syntax ......... 57 - Siemens Simatic S5 PLCs descriptor - English syntax................................. 65


WoodheadWoodhead


- Functionality

- Industrial Ethernet client

Functions managed by choosing an Industrial Ethernet channel can be used to access the variables defined in the following table.

The address of the variable accessed must be calculated in certain cases by referring to the " applicom® addressing" column in the table.

The item descriptor usable with PCDDE associated with this addressing is SIMATIC S5 (Industrial Ethernet).

Siemens PLC applicom® Type of exchange Corresponding applicom® function

variable addressing (addr) (cyclic mode) (library/DLL access)M v.w v*8+w Read bits READPACKBIT, READDIFBITDB x D y.z x*65536+y*16+z+134217728 Write bits WRITEPACKBIT, WRITEDIFPACKBITDX x D y.z idem +16777216MB v v Read bytes READBYTE

Write bytes WRITEBYTEMB v v Read packed bytes READPACKBYTE, READDIFBYTE

Write packed bytes WRITEPACKBYTE, WRITEDIFPACKBYTEMW v v Read words READWORD, READDIFWORDDB x DW y x*4096+y+134217728 Write words WRITEWORD, WRITEDIFWORDDX x DW y idem + 1048576MW v v Read BCD words READWORDBCDDB x DW y x*4096+y+134217728 Write BCD words WRITEWORDBCDDX x DW y idem + 1048576MD v v Read double words READDWORD, READDIFDWORDDB x DD y x*4096+y+134217728 Write double words WRITEDWORD, WRITEDIFDWORDDX x DD y idem + 1048576MD v KG v Read floating words READFWORD, READDIFFWORDDBxDDyKG x*4096+y+134217728 Write floating words WRITEFWORD, WRITEDIFFWORDDXxDDyKG idem + 1048576E v.w v*8+w Read input bits READPACKIBIT, READDIFIBITEB v v Read input bytes READIBYTEEB v v Read packed input bytes READPACKIBYTE, READDIFIBYTEEW v v Read input words READIWORD, READDIFIWORDA v.w v*8+w Read output bits READPACKQBIT, READDIFQBIT

Write output bits WRITEPACKQBIT, WRITEDIFPACKQBITAB v v Read output bytes READQBYTE, READDIFQBYTE

Write output bytes WRITEQBYTEAB v v Read packed output bytes READPACKQBYTE, READDIFQBYTE

Write packed output bytes WRITEPACKQBYTE,WRITEDIFPACKQBYTEAW v v Read output words READQWORD, READDIFQWORD

Write output words WRITEQWORD, WRITEDIFQWORDTB n n Read timers READTIMER

Write timers WRITETIMERZB n n Read counters READCOUNTER

Write counters WRITECOUNTER

v : Byte N° w : N° of bit in byte (0 to 7) x : DB N° (1 to 255) or DX N° (0 to 255) y : N° of word in DB or in the DX (0 to 4095) z : N° of bit in word (0 to 15) n : Timer or counter N° (0 to 779)


WoodheadWoodhead


Remarks : The item descriptor can be used to reach DBs of 256, 2048 and 4096 words (remains compatible with

versions earlier than V3.0). CAUTION! The Simatic S5 messaging (READ/WRITE) can only write bits with 16 bits words (case of DB

and DX) or with 8 bits bytes (case of memo, inputs and outputs). The applicom® software reads words or bytes containing the bits to write in API, hides and forces the user bits, then writes words or bytes in the equipment as a whole. This machinery can induce risks if the equipment has forced others bits of the word or of the byte between the reading and the writing. Access to the functions of the applicom.dll library is not supported by the SW1000ETH solution.


WoodheadWoodhead


- Maximum number of variables per exchange with the library The maximum number of variables is given with 1584 bytes exchange data buffers.

Remark: access to the functions of the applicom.dll library is not supported by the SW1000ETH solution.

S5 messaging READ/WRITE

Object Maximum quantity in read / write

and buffer 1584 bytesBit 12465Byte 1560Word 780Double word 390Timer/counter 780

- Maximum number of variables per exchange with PCDDE


Object Maximum quantity in read / writeBit 2048 / 1Byte 1560 / 1Word 780 / 1Double word 390 / 1Timer/counter 780 / 1

The number given for read frames corresponds to the maximum number of points (as imposed by

the server and/or the protocol) which can be grouped together during dynamic optimization of the frames carried out by the server. However, this number can be reduced to suit a specific item of equipment by configuring the length of frames in the topic (see chapter "Implementation/Topics configuration/Advanced options").

Where write operations are concerned, a variable automatically entails the formation of a frame.

- Maximum number of variables per exchange with OPC server


Object Maximum quantiy in read / writeBit 2048Byte 1560Word 780Double word 390Timer/counter 780

The number given for read frames corresponds to the maximum number of points (as imposed by the server and/or the protocol) which can be grouped together during dynamic optimization of the frames carried out by the server. However, this number can be reduced to suit a specific item of equipment by configuring the length of frames in the topic (see chapter "Implementation/Topics configuration/Advanced options").

For the write frames, see chapter "OPC Server/Optimization of synchronous and asynchronous requests".


WoodheadWoodhead


- Estimating the performance of an applicom® Industrial Ethernet Client.

Remark: it is impossible to estimate the performance of the SW1000ETH solution since it mainly depends on the performance of the host computer. This estimation is made in the worst context where the applicom® Industrial Ethernet Station is uniquely Industrial Ethernet CLIENT, all variables are refreshed by permanently active cyclic read functions. When the applicom® interface Industrial Ethernet SERVER is used (the PLCs place event variables in the database) the time to feed back data into the applicom® database is approximately equal to the Industrial Ethernet CLIENT PLC cycle time. Reminder: the Industrial Ethernet SERVER and CLIENT functionality can be accumulated. Estimating the performance is done using an example: The applicom® interface must feed back variables coming from Siemens stations type 115U with a CPU 943B and

• either a CP 143 coupler card on the Industrial Ethernet ISO Layer 4 network. • or a CP 1430 TCP on the Industrial Ethernet TCP/IP network.

The cycle time of PLC is 25 ms and the Simatic-S5 (READ/WRITE) messaging is used.

The « SendAll » and « ReceiveAll » call is only made once per PLC cycle, which means that the

PLC access is monoflow. The PLC configuration is described in the chapter "- Siemens equipments implementation" on page 30 (Simatic S5 (READ/WRITE) messaging) without the client PLC contracts. No inter-PLC exchange is active. Number of variables :

3 tables of 780 words and 1 table of 12465 bits per station.

0

20

40

60

80

100

120

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Number of Station

Req

uest

s / s

Industrial Ethernet ISO Layer 4Industrial Ethernet TCP/IP


WoodheadWoodhead


0%

5%

10%

15%

20%

25%

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Number of Station

Net

wor

k Lo

ad

Industrial Ethernet ISO Layer 4Industrial Ethernet TCP/IP

Remark :

The number of simultaneous requests generated by the applicom® Industrial Ethernet client is configured to 24 (default value in the console). See chapter "- Ethernet : " on page 8.

The network load is for an Ethernet network at 10 Mb.

applicom® database retrieval time (Except application and supervision) :

In our example, to retrieve variables from 20 equipments (60 tables of 780 words and 20 tables of 12465 bits), i.e. in all 46800 words and 249300 bits, 80 requests are used :

• On the Industrial Ethernet ISO Layer 4 network : 080 (requests) / 85 (requests/s) = 0.94 second.

• On the Industrial Ethernet TCP/IP network : 180 (requests) / 60 (requests/s) = 1.33 second.


WoodheadWoodhead


- Industrial Ethernet server The Industrial Ethernet Server on applicom® interface makes available a 32 kword database to

Siemens network architecture clients Simatic S5 (READ/WRITE).

Supported Type of data Addresses in Correspondingrequests in DATABASE DATABASE S5 addresses

Read inputs (EB) byte area 0 - 127 EB0 à EB127Read outputs (AB) byte area 128 - 255 AB0 à AB127Read memos (MB) byte area 256 - 511 MB0 à MB255Read data blocks (DB) word area 256 - 31999 DB1DW0 à DB124DW255Write outputs (AB) byte area 128 - 255 AB0 à AB127Write memos (MB) byte area 256 - 511 MB0 à MB255Write data blocks (DB) word area 256 - 31999 DB1DW0 à DB124DW255

Notes: Seen by the client PLCs, the DATA-BASE manages virtually 124 blocks of data of 256 words in its

word area. The client PLC program must generate SEND and RECEIVE type blocks with parameters identical to those used to access the DBs in server PLCs. To find the equivalent address on the applicom® database, use the formulae :

• for bits in a DB DB x D y.z x*4096+y*16+z • for words in a DB DB x DW y x*256+y

x : DB n° (1 to 255) (DB0 forbidden) y : N° of DW word in the DB (0 to 255) z : Bit n° in word (0 to 15) Maximum number of variables per exchange:

128 input or output bytes 256 memory bytes 256 DB words

The Industrial Ethernet server functionality on the applicom® database can be used to optimize

information feedback. Rather than permanently polling the equipments to monitor variables which change status occasionally, the equipments can store the information to be fed back in the applicom® database only on status changes (alarm feedback). This operating mode results in:

PLC processors less solicited. Network architecture less heavily loaded. Minimized information feedback time.


WoodheadWoodhead


This principle can be made reliable on the Industrial Ethernet server on applicom® interface to avoid working « blind ». For example, the variables in the applicom® database do not change since the transmitting equipment is disconnected. To do this:

• You can define in the configurator a maximum time between the accesses of the client equipment to the applicom® Industrial Ethernet server. After this interval, the absence is indicated to the application by a « ACCESS STATUS WORD » in the applicom® database. The address of this status is defined by you using the channel configuration utility.

• The application is informed of the write access by each equipment to the applicom® Industrial Ethernet server by incrementing an « ACCESS INDICATOR WORD » in the applicom® database. The application can consult the variables of this equipment in the applicom® database and reset the « ACCESS INDICATOR WORD » to be informed about the next access (or even to inform the transmitting equipment of this acknowledgment).


WoodheadWoodhead


- Configuration This protocol can only be configured on applicom® interfaces with an Ethernet channel

(PCI2000ETH or SW1000ETH).

- Configuring a SIMATIC® S5 server equipment

General Configuration After selecting the SIMATIC S5 type, entering the device number and the network parameters, you

must define the "Messaging Parameters" zone:

Figure 12 : General configuration of a server device applicom description See chapter "- Equipment properties" on page 16 Network properties See chapter "- Equipment properties" on page 16


WoodheadWoodhead


Messaging Parameters

Figure 13 : Messaging Parameters of a SIMATIC S5 server equipment

Local TSAP This choice is used to define the name of the local TSAP (Transport Service Access Point) for this applicom® client connection. This name will be transmitted during the connection phase to the server equipment, which can use this name as identifier.

Remote read TSAP This choice is used to define the name of the TSAP (Transport Service Access Point) for read accesses to the server PLC equipment.This name must also be defined in the server PLC coupler. Server PLC coupler configuration:

0Contract FETCH passive. 1Ethernet address 000000000000 (CP 143 or CP 1430) 2IP address 000.000.000.000 (CP 1430 TCP) 3LOCAL TSAP ID identical to this field (READREAD by default) 4REMOTE TSAP ID not defined.

Remote write TSAP

This choice is used to define the name of the TSAP (Transport Service Access Point) for write accesses to the server PLC equipment. This name must also be defined in the server PLC coupler. Server PLC coupler configuration:

0Contract RECEIVE passive. 1Ethernet address 000000000000 (CP 143 or CP 1430) 2IP address 000.000.000.000 (CP 1430 TCP) 3LOCAL TSAP ID identical to this field (WRITWRIT by default) 4REMOTE TSAP ID not defined.

For any further information concerning the PLC configuration, refer to SIEMENS documentation.


WoodheadWoodhead


- Configuring a SIMATIC S5 client equipment General configuration

After selecting the SIMATIC S5 READ/WRITE type, choosing the equipment number and entering

the network parameters, you must define the « Messaging parameters » zone :

Figure 14 : General configuration of a client device server

applicom description See chapter "- Equipment properties" on page 16 Network properties See chapter "- Equipment properties" on page 16


WoodheadWoodhead



Figure 15 : Messaging Parameters of a client equipment

Access time-out Definition of the access time-out to the applicom® Industrial Ethernet server (in seconds). Value from 0 to 65535, default value 5 s. This value determines the maximum time interval between the accesses of the client to the applicom® server. After this delay, its absence will be automatically indicated in the « Access status words » of the applicom® database.


WoodheadWoodhead


- Siemens equipments implementation

- PLC under Industrial Ethernet READ/WRITE protocol

- Connection between the computer and the SIEMENS PLC. The PC is connected to the Industrial Ethernet network via the PCI2000ETH board. Connecting the

SIEMENS PLC to the Industrial Ethernet network is carried out by installing a special communication processor :

• the CP143 or the CP1430 for the layer 4 ISO protocol • the CP1430TCP for the TCP/IP protocol This communication processor is connected directly on the motherboard bus of SIMATIC® S5

PLCs. It can be used with all S5 systems from S5 115U and better. There are two physical interfaces on these various couplers, one to connect the Industrial Ethernet network (AUI connector) and the other to access the coupler's configuration and setting. Traffic management on the Industrial Ethernet network is processed independently by the coupler, thereby releasing the S5 PLC CPU of this task.

- Communication between the S5 processor and the CP 143 or CP1430 coupler Communication between the PLC processor and the coupler is done via a double access RAM,

therefore providing very fast exchanges. This data exchange is carried out using communication blocks which are the standard PLC subprograms supplied by Siemens with the PLCs.

The communications blocks used can be: SYNCHRON FETCH RECEIVE SEND

SYNCHRON Initialization and synchronization between the CPU and the CP. This block must be called on PLC warm start or cold start sequences.

FETCH

Data fetch (when the PLC is client in read). RECEIVE

Data reception from the network towards the PLC program via the CP143 coupler (when the PLC is server in read).

SEND Data transmission from the S5 PLC processor towards the CP143 coupler (when the PLC is server or client in write). The example below shows how the SYNCHRON function block must be called if you are using a

PLC in the 115U family. It should be noted that the function block numbers vary from one type of PLC to another. The SYNCHRON block must be called by the PLC on each PLC warm or cold start.

Example: in OB21 and OB22 ( Organization blocks 21 and 22 ) : SPA FB 249 ;Call block FB249. Name : SYNCHRON ;The console writes the block name. SSNR : KY 0,0 ;Memory zone reserved for coupler access.


WoodheadWoodhead


BLGR : KY 0,6 ;Size of data zone used for the CPU <->CP communication(512 bytes).

PAFE : MB 255 ;Diagnostic byte.

- Example: Configuring CP143, CP1430 and CP1430TCP couplers

Description In this example, 4 types of exchange are performed: - 1 The applicom® board is client of a SIMATIC® S5 115U PLC, it must retrieve a table of 128

words in the DB100 from word DW0 in the PLC and store the values from address 0 in the DATA-BASE. We will use cyclic mode to perform this exchange.

- 2 The application program can write words in the PLC in mode with wait. - 3 The 115U PLC must be client of the applicom® DATA-BASE. The PLC must transmit a table of

128 words from the DB10DW0 to the DATA-BASE at the same address on active status of the input E13.1.

- 4 On active status of the input E13.0, the PLC must also read in the DATA-BASE 128 words from

DB20DW0. They will be stored at the same address in the PLC. Ethernet address of the applicom®board : 00A091004E84 (if the board serial number is 20100) IP address of the applicom® board : 143.152.3.3 DATA-BASE TSAP in read : READREAD (default value) DATA-BASE TSAP in write : WRITWRIT (default value) PLC Ethernet address : 080006010000 PLC IP address : 143.152.3.5 PLC TSAP in read : READREAD PLC TSAP in write : WRITWRIT

Configuring the CP143 SIEMENS with COM143 In this example, the configuration is carried out using COM143 software supplied by SIEMENS.

This section is supplied for information and it is based on the COM143 software version currently available (6/6/95). If this software has been updated in the meantime, you must adapt this example with your new tool.

The first step is to configure the title block (menu SYSID)


WoodheadWoodhead


Complete here the SSNR corresponding to your CP143 board (see « switch ») and the PLC

Ethernet address.


WoodheadWoodhead


Press F7 then F1 to confirm The second step is to define the initialization block (menu INIT)

The third step allows you to define the various connections (menu CONN) In this example, we must define 4 connections: - server connection in read

The SSNR must correspond with that defined in the section SYSID. You must give a contract

number and type (here, passive FETCH since server in read). The partner's Ethernet address must = 0. The SSNR and ANR fields « TO REMOTE PLC » must be blank.


WoodheadWoodhead


press F5 to define the rest of the connection

You must select the READ/WRITE option with priority 2. You must complete the local TSAP, which

must be identical to that defined in the section « Remote TSAP read » when configuring equipments in the applicom® configurator.

press F5 then F3 to enter the following connection - server connection in write


number and type (here, passive RECEIVE since server in write). The partner's Ethernet address must = 0. The SSNR and ANR fields « TO REMOTE PLC » must be blank.


WoodheadWoodhead



You must select the READ/WRITE option with priority 2. You must complete the local TSAP, which

must be identical to that defined in the section « Remote TSAP write » when configuring equipments in the applicom® configurator.

press F5 then F3 to enter the following connection


WoodheadWoodhead


- client connection in read


number and type (here, active FETCH since client in read). The partner's Ethernet address must also be equal to that of the applicom® board. The SSNR and ANR fields « TO REMOTE PLC » must be blank.


You must select the READ/WRITE option with priority 2. You must complete the remote TSAP,

which must be identical to that defined in the section « local TSAP read of server » when configuring the DATA-BASE in the applicom® configurator.

press F5 then F3 to enter the following connection


WoodheadWoodhead


- client connection in write


number and type (here, passive SEND since client in write). The partner's Ethernet address must also be equal to that of the applicom® board. The SSNR and ANR fields « TO REMOTE PLC » must be blank.


You must select the READ/WRITE option with priority 2. You must complete the remote TSAP. This

name must be identical to that defined in the section (local TSAP in write) when configuring the DATA-BASE in the applicom® configurator.


WoodheadWoodhead


Configuring SIEMENS CP1430 and CP1430TCP with SINEC NCM COMs

In this example, the CP1430 configuration is carried out using SINEC NCM COM 1430 software and the CP1430TCP configuration using SINEC NCM COM 1430TCP software, supplied by SIEMENS. This section is supplied for information and it is based on the software version currently available (V 5.01). If this software has been updated in the meantime, you must adapt this example with your new tool.

In the upper menu bar, choose « Edit ». Select « Init CP » With COM 1430 and COM 1430TCP

You must complete the coupler's Ethernet Mac address and the basic SSNR and its offset, then

press F7 to validate and exit. With COM 1430TCP, still in the « Edit » menu, select « TCP/IP Init »

You must complete the IP parameters (IP address, router, sub-network mask).


WoodheadWoodhead


The second step is used to define the various connections. Still in the « Edit » menu, choose « Links », then « Transport links »

In this example, we must define 4 connections: - server connection in read With COM 1430

With COM 1430TCP

The SSNR must correspond with that defined in the section Init CP. You must give a contract

number and type (here, passive FETCH since server in read). You must select the READ/WRITE option (priority 2 with COM 1430). You must complete the local TSAP, which must be identical to that defined in the section « Remote TSAP read » (by default READREAD) during equipment configuration in the applicom® configurator. The partner's Ethernet or IP address must = 0. The TSAP fields must be blank.

Press F3 to enter the following connection:


WoodheadWoodhead


- server connection in write With COM 1430

With COM 1430TCP


number and type (here, passive RECEIVE since server in write). You must select the READ/WRITE option (priority 2 with COM 1430).30 You must complete the local TSAP, which must be identical to that defined in the section « Remote TSAP write » (by default WRITWRIT) during equipment configuration in the applicom® configurator. The partner's Ethernet or IP address must = 0. The TSAP fields of the remote equipment must be blank.



WoodheadWoodhead


- client connection client in read With COM 1430

With COM 1430 TCP


number and type (here, active FETCH since client in read). You must select the READ/WRITE option (priority 2 with COM 1430). You can enter the local TSAP. You must enter the remote TSAP, which must be identical to that defined in the section « Local TSAP in read » (by default READREAD) during the configuration of the tab « Server mode » in the « Ethernet channel properties», and the partner's Ethernet or IP address.



WoodheadWoodhead


- client connection in write With COM 1430

With COM 1430TCP


number and type (here, active SEND since client in write). You must select the READ/WRITE option (priority 2 with COM 1430). You can enter the TSAP. You must enter the remote TSAP, which must be identical to that defined in the section « Local TSAP in write » (by default WRITWRIT) during the configuration of the tab « Server mode » in the « Ethernet channel properties», and the partner's Ethernet or IP address.

Press F7 to validate and exit.


WoodheadWoodhead


- Example : PLC program for SIMATIC S5

C:READWRIT.S5D Segment 1 0000 Nom : Industrial Ethernet : AWL : A DB 3 Working DB : SPA FB 245 Nom : RECEIVE FB receive (server functions) SSNR : KY 0,0 SSNR of your CP143 or CP1430 A-NR : KY 0,0 receive all ANZW : DW 12 indicator word ZTYP : KC NN source type non defined DBNR : KY 0,0 non significant ZANF : KF +0 non significant ZLAE : KF +0 non significant PAFE : MB 242 indicator byte : : SPA FB 244 Nom : SEND FB send (server functions) SSNR : KY 0,0 SSNR of your CP143 or CP1430 A-NR : KY 0,0 send all ANZW : DW 10 indicator word QTYP : KC NN source type non defined DBNR : KY 0,0 non significant ZANF : KF +0 non significant ZLAE : KF +0 non significant PAFE : MB 242 indicator byte : : U E 13.0 if input 13.0 is active : L DW 14 and no contract in progress : T MW 242 : UN M 243.1 : SPA FB 246 Nom : FETCH FB fetch (read client PLC) SSNR : KY 0,0 SSNR of your CP143 or CP1430 A-NR : KY 0,30 contract 30 see config CP143 or CP1430 ANZW : DW 14 indicator word ZTYP : KC RW indirect addressing DBNR : KY 0,3 indirection source in DB3 ZANF : KF +20 from DW20 (see DB3) ZLAE : KF +8 number of data in DB3W20 PAFE : MB 242 indicator byte : : U E 13.1 if input 13.0 is active : L DW 16 and no contract in progress : T MW 242 : UN M 243.1 : SPA FB 244 Nom : SEND FB send direct (write client PLC) SSNR : KY 0,0 SSNR of your CP143 or CP1430 A-NR : KY 0,31 contract 31 see config CP143 or CP1430 ANZW : DW 16 indicator word QTYP : KC RW indirect addressing DBNR : KY 0,3 indirection source in DB3 ZANF : KF +30 from DW30 (see DB3) ZLAE : KF +8 number of data in DB3W30 PAFE : MB 242 indicator byte : : BE


WoodheadWoodhead


Description of the working DB3 : DB3 C:READWRIT.S5D 0 : KH = 0000; 1 : KH = 0000; 2 : KH = 0000; 3 : KH = 0000; 4 : KH = 0000; 5 : KH = 0000; 6 : KH = 0000; 7 : KH = 0000; 8 : KH = 0000; 9 : KH = 0000; 10 : KH = 0000; ANZW SEND-ALL (PLC server) 11 : KH = 0000; 12 : KH = 0000; ANZW RECEIVE-ALL (PLC serveur) 13 : KH = 0000; 14 : KH = 0000; ANZW FETCH (read client) 15 : KH = 0000; 16 : KH = 0000; ANZW SEND (write client) 17 : KH = 0000; 18 : KH = 0000; 19 : KH = 0000; 20 : KC = ‘DB’; Indication source data type, here DB applicom® 21 : KY = 0,20; DB source number here DB20 in applicom® DATA-

BASE 22 : KF = +0; offset in DB applicom® DATA-BASE here 0 23 : KF = +128; number of data in the source 24 : KC = ‘DB’; destination type, here DB 25 : KY = 0,20; here DB20 in PLC 26 : KY = +0; from DW0 27 : KY = +128; number of data to copy in the PLC 28 : KH = 0000; 29 : KH = 0000; 30 : KC = ‘DB’; Indication source data type, here DB of the PLC 31 : KY = 0,100; DB number to send to applicom®, here DB100 32 : KF = +0; offset in DB, here DW0 33 : KF = 128; number of data to send to applicom® 34 : KC = ‘DB’; data type in applicom®, here DB (word area) 35 : KY = 0,100; adress of applicom® DB, here DB100 36 : KY = 0,0; offset in applicom® DB 37 : KF = +128; number of data to write in applicom® 38 : KH = 0000; 39 : KH = 0000; 40 : KH = 0000; 41 : KH = 0000; 42 : KH = 0000;


WoodheadWoodhead


- applicom® server configuration

Definition of the Local Read and Local Write TSAP with « the console » software program.


WoodheadWoodhead


Definition of the equipment number 0 with stands for the PLC seen as client by applicom®


WoodheadWoodhead


- Read cyclic function

Creation of the read cyclic function in the PLC with the « PCCYC » software program.


WoodheadWoodhead


Example of a write in the PLC in wait mode


WoodheadWoodhead


- applicom® functions usable on the master channel Remark: access to the functions of the applicom.dll library is not supported by the SW1000ETH

solution.

- Wait mode

readpackbit writepackbit readpackibit readpackqbit writepackqbit readbyte writebyte readibyte readqbyte writeqbyte readpackbyte writepackbyte readpackibyte readpackqbyte writepackqbyte readword writeword readiword readqword writeqword readwordbcd writewordbcd readdword writedword readfword writefword readtimer writetimer readcounter writecounter

- Deferred mode

readdifbit writedifpackbit readdifibit readdifqbit writedifpackqbit readdifbyte writedifpackbyte readdifibyte readdifqbyte writedifpackqbyte readdifword writedifword readdifiword readdifqword writedifqword readdifdword writedifdword readdiffword writediffword testtransdif transdif transdifpack


WoodheadWoodhead


- Cyclic mode

createcyc startcyc stopcyc actcyc transcyc transcycpack

Cyclic function Type:

TYPE OF VARIABLE Function type IN EQUIPMENT Reading Writing

Packed bits X X Input packed bits X Output packed bits X X Packed bytes X X Bytes X X Input packed bytes X Input bytes X Output packed bytes X X Output bytes X X Words X X BCD words X X Input words X Output words X X 32 bit double words X X 32 bit IEEE floating words X X


WoodheadWoodhead


- Item of image variables

- Presentation The "item of image variables" are the syntaxes which allow to access to the variables through the

DDE server "PCDDE" or the OPC server.

- With the DDE server, the item is the part "item name" of the DDE connection defined by: 0- application name 1- topic name 2- item name 3

Report you to sections "DDE server/Principles regarding access to Data" or "OPC server/Data

Access Principle". According to the configuration of the equipment, the descriptor is determined by default by the

server. In the case of Industrial Ethernet protocol, the default descriptor is depending on the type of equipment. For S5 equipment, the descriptor is Simatic S5 (German and French syntax and English syntax).

Caution, if you change the default descriptor, some optimizations of access to the equipment will be

devalidated and the performances could be corrupted. You however have the possibility of using another descriptor (in particular the applicom® standard

descriptor) by the means of the advanced options.


WoodheadWoodhead


- Standard descriptor The standard descriptor can be used for access to the equipments which have not specific

descriptors. The address field of the item name may be 10 digits long. It allows to compose a linear address from 0 to 4 giga.

Unitary mode Table Mode, Matrix Mode

Internal bits Bx Bx_n, Bx_n_l Input bits BIx BIx_n, BIx_n_l Output bits BOx BOx_n, BOx_n_l Internal bytes Ox Ox_n, Ox_n_l Bits in internal bytes Ox.b Input bytes OIx OIx_n, OIx_n_l Output bytes OOx OOx_n, OOx_n_l ASCII string in internal bytes M_Ox_n Internal words Wx Wx_n, Wx_n_l Bits in internal words Wx.b Input words WIx WIx_n, WIx_n_l Output words WOx WOx_n, WOx_n_l ASCII string in internal words M_Wx_n Internal double words Dx Dx_n, Dx_n_l Internal floating words Fx Fx_n, Fx_n_l

Remarks :

The limiting values of the parameters n and l depend on the protocol. However, in the case of PCDDE, they cannot be greater than 128 for bits bytes, 64 for words, 32 for double words and floating words.

To consult the read and write limits, refer to sections: "- Maximum number of variables per exchange with PCDDE" on page 21 "- Maximum number of variables per exchange with OPC server" on page 21 Refer to chapter "- Industrial Ethernet client" on page 19 for variable addressing.


WoodheadWoodhead


- Internal bits => Bx (type: BIT) x: Number of the first bit. Example: B4

- Internal bits => Bx_n, Bx_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples: B4_10, B4_10_5

- Input bits => BIx (type: BIT) x: Number of the first bit. Example: BI4

- Input bits => BIx_n, BIx_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : BI4_10, BI4_10_5

- Output bits => BOx (type: BIT) x: Number of the first bit. Example: BO4

- Output bits => BOx_n, BOx_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : BO4_10, BO4_10_5

- Internal bytes => Ox (type : BYTE) x: Number of the first byte. Example: O4

- Internal bytes => Ox_n, Ox_n_l n: Number of bytes. l: Number of bytes per line (Matrix mode only). Examples : O4_10, O4_10_5

- Bits in internal bytes => Ox.b (type : BIT) For this syntax, the maximum numbers of variables per frame are:

in read : 256*8 in write : 1

x : First byte number. b : Bit range in the byte (0 to 7). Example : O4.5


WoodheadWoodhead


- Input bytes => OIx (type: BYTE) x: Number of the first byte. Example: OI4

- Input bytes => OIx_n, OIx_n_l n: Number of bytes. l: Number of bytes per line (Matrix mode only). Examples: OI4_10, OI4_10_5

- Output bytes => OOx (type: BYTE) x: Number of the first byte. Example: OO4

- Output bytes => OOx_n, OOx_n_l n: Number of bytes. l: Number of bytes per line (Matrix mode only). Examples : OO4_10, OO4_10_5

- ASCII string in internal bytes => M_Ox_n (type: BYTE) For more information on the use of the ASCII string, you can consult the chapter "Use of message

mode". x: Number of the first byte containing the string. n: Number of potential bytes that could contain the ASCII string (1 to 131). Example: M_O100_30 In the example, the byte array O100 to O129 can contain the string.

- Internal words => Wx (type: 16 bit WORD) x: Number of the first word. Example: W4

- Internal words => Wx_n, Wx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples: W4_10, W4_10_5


WoodheadWoodhead


- Bits in internal words => Wx.b (type : bit) For this syntax, the maximum numbers of variables per frame are:


x : First word number. b : Bit range in the word (0 to 15). Example : W4.5

- Input words => WIx (type: 16 bit WORD) x: Number of the first word. Example: WI4

- Input words => WIx_n, WIx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples: WI4_10, WI4_10_5

- Output words => WOx (type: 16 bit WORD) x: Number of the first word. Example: WO4

- Output words => WOx_n, WOx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : WO4_10, WO4_10_5

- ASCII string in internal words => M_Wx_n (type: 16 bit WORD) For more information on the use of the ASCII string, you can consult the chapter "Use of message

mode". x: Number of the first word containing the string n: Number of potential words that could contain the ASCII string (1 to 65). Example: M_W100_30 In the example, the word array W100 to W129 can contain the string.


WoodheadWoodhead


- Internal double words => Dx (type: 32 bit WORD) x: Number of the first double word. Example: D4

- Internal double words => Dx_n, Dx_n_l n: Number of double words. l: Number of double words per line (Matrix mode only). Examples : D4_10, D4_10_5

- Internal floating words => Fx (type: 32 bit IEEE REAL) x: Number of the first floating word. Example: F4

- Internal floating words => Fx_n, Fx_n_l n: Number of floating words. l: Number of floating words per line (Matrix mode only). Examples: F4_10, F4_10_5


WoodheadWoodhead


- Siemens Simatic S5 PLCs descriptor - German (D) and French syntax This descriptor can be used only for accessing Siemens Simatic S5 PLCs via the applicom®

PCI2000ETH or SW1000ETH. For strings and matrices, the Descriptor checks for acceptable addressing limits, thus avoiding data

overlap. Unitary mode Table Mode, Matrix Mode

Bits in flag bytes Mx.y Mx.y_n, Mx.y_n_l Input bits Ex.y Ex.y_n, Ex.y_n_l Output bits Ax.y Ax.y_n, Ax.y_n_l Bits of DB word DBxDy.z DBxDy.z_n, DBxDy.z_n_l Bits of DX word DXxDy.z DXxDy.z_n, DXxDy.z_n_l Flag bytes MBx MBx_n, MBx_n_l Input bytes EBx EBx_n, EBx_n_l Output bytes ABx ABx_n, ABx_n_l ASCII string in flag bytes M_MBx_n Words in flag bytes MWx MWx_n, MWx_n_l Input words EWx EWx_n, EWx_n_l Output words AWx AWx_n, AWx_n_l Words in DB DBxDWy DBxDWy_n, DBxDWy_n_l Words in DX DXxDWy DXxDWy_n, DXxDWy_n_l Right byte of a word in the DB DBxDRy Left byte of a word in the DB DBxDLy Right byte of a word in the DX DXxDRy Left byte of a word in the DX DXxDLy ASCII string in DB words M_DBxDWy_n ASCII string in DX words M_DXxDWy_n Double words in flag bytes MDx MDx_n, MDx_n_l Floating words in flag bytes MDxKG Double words in DB DBxDDy DBxDDy_n, DBxDDy_n_l Double words in DX DXxDDy DXxDDy_n, DXxDDy_n_l Floating words in the DB DBxDDyKG Floating words in the DX DXxDDyKG Timers TBx TBx_n, TBx_n_l Counters ZBx ZBx_n, ZBx_n_l


WoodheadWoodhead


Remarks : The limiting values of the parameters n and l depend on the protocol. However, in the case of PCDDE, they cannot be greater than 128 for bits bytes, 64 for words, 32 for double words and floating words.

Caution: DX cannot be accessed with all Siemens CPUs. For access to words in flag bytes, to input words or output words, these are accessed in a byte

zone, word 1 being composed of bytes 1 and 2, word 2 of bytes 2 and 3, and so on. The words thus overlap one another.

Where access to double words and floating words in flag bytes is concerned, these variables are accessed in a byte zone, double word 1 being composed of bytes 1, 2, 3 and 4, double word 2 of bytes 2, 3, 4 and 5, and so on. The variables thus overlap one another.


- Bits in flag bytes => Mx.y or Mx:y (type: BIT) x: Flag byte number (0 to 255). y: First bit range in flag byte (0 to 7). Example: M94.7 or M94:7

- Bits in flag bytes => Mx.y_n or Mx:y_n, Mx.y_n_l or Mx:y_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : M94.7_24 or M94:7_24, M94.7_24_8 or M94:7_24_8

- Input bits => Ex.y or Ex:y (type: BIT) x: Number of the input byte (0 to 127). y: Rank of the first bit in the input byte (0 to 7). Example : E94.7 or E94:7

- Input bits => Ex.y_n or Ex:y_n, Ex.y_n_l or Ex:y_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : E94.7_24 or E94:7_24, E94.7_24_8 or E94:7_24_8


WoodheadWoodhead


- Output bits => Ax.y or Ax:y (type: BIT) x: Number of the output byte (0 to 127). y: Rank of the first bit in the output byte (0 to 7). Example: A94.7 or A94:7

- Output bits => Ax.y_n or Ax:y_n, Ax.y_n_l or Ax:y_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples: A94.7_24 or A94:7_24, A94.7_24_8 or A94:7_24_8

- Bits of DB word => DBxDy.z or DBxDy:z (type: BIT) x: DB number (1 to 255). y: First DB word number (0 to 255). z: First bit range (0 to 15). Example: DB94D10.7 or DB94D10:7

- Bits of DB word => DBxDy.z_n or DBxDy:z_n, DBxDy.z_n_l or DBxDy:z_n_l n: Number of bits. l : Number of bits per line (Matrix mode only) Examples : DB94D10.7_24 or DB94D10:7_24, DB2D3.7_24_8 or DB2D3:7_24_8

- Bits of DX word => DXxDy.z or DXxDy:z (type: BIT) x: DX number (0 to 255). y: First DX word number (0 to 255). z: First bit range (0 to 15). Example: DX94D10.7 or DX94D10:7

- Bits of DX word => DXxDy.z_n or DXxDy:z_n, DXxDy.z_n_l or DXxDy:z_n_l n: Number of bits. l : Number of bits per line (Matrix mode only) Examples : DX94D10.7_24 or DX94D10:7_24, DX2D3.7_24_8 or DX2D3:7_24_8

- Flag bytes => MBx (type: BYTE) x: First flag byte number (0 to 255). Example: MB4

- Flag bytes => MBx_n, MBx_n_l n: Number of bytes. l: Number of bytes per line (Matrix mode only). Examples: MB4_10, MB4_10_5


WoodheadWoodhead


- Input bytes => EBx (type: BYTE) x: Number of the first input byte (0 to 127). Example: EB4

- Input bytes => EBx_n, EBx_n_l n: Number of bytes. l: Number of bytes per line (Matrix mode only). Examples : EB4_10, EB4_10_5

- Output bytes => ABx (type: BYTE) x: Number of the first output byte (0 to 127). Example: AB4

- Output bytes => ABx_n, ABx_n_l n: Number of bytes. l: Number of bytes per line (Matrix mode only). Examples: AB4_10, AB4_10_5

- ASCII string in flag bytes => M_MBx_n (type: BYTE) For more information on the use of the ASCII string, you can consult the chapter "Use of message

mode". x: Number of first flag byte containing the string (0 to 255). n: Number of potential flag byte which can contain the ASCII string (1 to 131). Example: M_MB100_10 In the example the byte array MB100 to MB109 can contain the string.

- Words in flag bytes => MWx (type: 16 bit WORD) x: Number of the first word (0 to 254). Example: MW4


WoodheadWoodhead


- Words in flag bytes => MWx_n, MWx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : MW4_10, MW4_10_5

- Input words => EWx (type: 16 bit WORD) x: Number of the first word (0 to 126). Example: EW4

- Input words => EWx_n, EWx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : EW4_10, EW4_10_5

- Output words => AWx (type: 16 bit WORD) x: Number of the first word (0 to 126). Example: AW4

- Output words => AWx_n, AWx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples: AW4_10, AW4_10_5

- Words in DB => DBxDWy (type: 16 bit WORD) x: DB number (1 to 255). y: Number of the first word in the DB (0 to 255). Example: DB4DW8

- Words in DB => DBxDWy_n, DBxDWy_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : DB4DW8_10, DB4DW8_10_5

- Words in DX => DXxDWy (type: 16 bit WORD) x: DX number (0 to 255). y: Number of the first word in the DX (0 to 255). Example: DX4DW8


WoodheadWoodhead


- Words in DX => DXxDWy_n, DXxDWy_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : DX4DW8_10, DX4DW8_10_5

- Right byte of a word in the DB => DBxDRy (type: BIT) For this syntax, the maximum numbers of variables per frame are:


x: DB number (1 to 255). y: Number of the word in the DB (0 to 255). Example: DB4DR5

- Left byte of a word in the DB => DBxDLy (type: BIT) For this syntax, the maximum numbers of variables per frame are:


x: DB number (1 to 255). y: Number of the word in the DB (0 to 255). Example: DB4DL5

- Right byte of a word in the DX => DXxDRy (type: BIT) For this syntax, the maximum numbers of variables per frame are:


x: DX number (0 to 255). y: Number of the word in the DX (0 to 255). Example: DX4DR5


WoodheadWoodhead


- Left byte of a word in the DX => DXxDLy (type: BIT) For this syntax, the maximum numbers of variables per frame are:


x: DX number (0 to 255). y: Number of the word in the DX (0 to 255). Example: DX4DL5

- ASCII string in DB words => M_DBxDWy_n (type: 16 bit WORD) For more information on the use of the ASCII string, you can consult the chapter "Use of message

mode". x: DB number (1 to 255). y: Number of the first word in the DB containing the string (0 to 255). n: Number of potential words that could contain the ASCII string (1 to 65). Example: M_DB4DW0_10 In the example, the word array DB4DW0 to DB4DW9 can contain the string.

- ASCII string in DX words => M_DXxDWy_n (type: 16 bit WORD) For more information on the use of the ASCII string, you can consult the chapter "Use of message

mode". x: DX number (0 to 255). y: Number of the first word in the DX containing the string (0 to 255). n: Number of potential words that could contain the ASCII string (1 to 65). Example: M_DX4DW0_10 In the example, the word array DX4DW0 to DX4DW9 can contain the string.

- Double words in flag bytes => MDx (type: 32 bit WORD) x: First flag byte number (0 to 255). Example: MD4

- Double words in flag bytes => MDx_n, MDx_n_l n: Number of double words. l: Number of double words per line (Matrix mode only). Examples: MD4_10, MD4_10_5

- Floating words in flag bytes => MDxKG (type: 32 bit IEEE REAL) x: Number of the floating word (0 to 252). KC: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format. Example: MD48KG

- Double words in DB => DBxDDy (type: 32 bit WORD) x: DB number (1 to 255). y: First DB word number (0 to 254). Example: DB4DD8

- Double words in DB => DBxDDy_n, DBxDDy_n


WoodheadWoodhead


n: Number of double words. l: Number of double words per line (Matrix mode only). Examples : DB4DD8_10, DB4DD8_10_5

- Double words in DX => DXxDDy (type: 32 bit WORD) x: DX number (0 to 255). y: First DX word number (0 to 254). Example: DX4DD8

- Double words in DX => DXxDDy_n, DXxDDy_n n: Number of double words. l: Number of double words per line (Matrix mode only). Examples : DX4DD8_10, DX4DD8_10_5

- Floating words in DB => DBxDDyKG (type REEL IEEE 32 bits) x: DB number (1 to 255). y: First DB word number (0 to 254). KC: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format. Example : DB4DD8KG

- Floating words in DX => DXxDDyKG (type REEL IEEE 32 bits) x: DX number (0 to 255). y: First DX word number (0 to 254). KC: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format. Example : DX4DD8KG

- Timers => TBx (type: 16 bit WORD) x: Number of the timer (0 to 255). Example: TB4

- Timers => TBx_n, TBx_n_l n: Number of timers. l: Number of timers per line (Matrix mode only). Examples : TB4_10, TB4_10_5

- Counters => ZBx (type: 16 bit WORD) x: Number of the counter (0 to 255). Example: ZB4

- Counters => ZBx_n, ZBx_n_l n: Number of counters. l: Number of counters per line (Matrix mode only). Examples : ZB4_10, ZB4_10_5


WoodheadWoodhead


- Siemens Simatic S5 PLCs descriptor - English syntax This descriptor can be used only for accessing Siemens Simatic S5 PLCs via the applicom®

PCI2000ETH or SW1000ETH. For strings and matrices, the Descriptor checks for acceptable addressing limits, thus avoiding data

overlap. Unitary mode Table Mode, Matrix Mode

Bits in flag bytes Fx.y Fx.y_n, Fx.y_n_l Input bits Ix.y Ix.y_n, Ix.y_n_l Output bits Qx.y Qx.y_n, Qx.y_n_l Bits of DB word DBxDy.z DBxDy.z_n, DBxDy.z_n_l Bits of DX word DXxDy.z DXxDy.z_n, DXxDy.z_n_l Flag bytes FYx FYx_n, FYx_n_l Input bytes IBx IBx_n, IBx_n_l Output bytes QYx QYx_n, QYx_n_l ASCII string in flag bytes M_FYx_n Words in flag bytes FWx FWx_n, FWx_n_l Input words IWx IWx_n, IWx_n_l Output words QWx QWx_n, QWx_n_l Words in DB DBxDWy DBxDWy_n, DBxDWy_n_l Words in DX DXxDWy DXxDWy_n, DXxDWy_n_l Right byte of a word in the DB DBxDRy Left byte of a word in the DB DBxDLy Right byte of a word in the DX DXxDRy Left byte of a word in the DX DXxDLy ASCII string in DB words M_DBxDWy_n ASCII string in DX words M_DXxDWy_n Double words in flag bytes FDx FDx_n, FDx_n_l Floating words in flag bytes FDxKG Double words in DB DBxDDy DBxDDy_n, DBxDDy_n_l Double words in DX DXxDDy DXxDDy_n, DXxDDy_n_l Floating words in DB DBxDDyKG Floating words in DX DXxDDyKG Timers TBx TBx_n, TBx_n_l Counters ZBx ZBx_n, ZBx_n_l


WoodheadWoodhead


Remarks : The limiting values of the parameters n and l depend on the protocol. However, in the case of PCDDE, they cannot be greater than 128 for bits bytes, 64 for words, 32 for double words and floating words.

Caution: DX cannot be accessed with all Siemens CPUs. For access to words in flag bytes, to input words or output words, these are accessed in a byte

zone, word 1 being composed of bytes 1 and 2, word 2 of bytes 2 and 3, and so on. The words thus overlap one another.

Where access to double words and floating words in flag bytes is concerned, these variables are accessed in a byte zone, double word 1 being composed of bytes 1, 2, 3 and 4, double word 2 of bytes 2, 3, 4 and 5, and so on. The variables thus overlap one another.


- Bits in flag bytes => Fx.y or Fx:y (type: BIT) x: Flag byte number (0 to 255). y: First bit range in flag byte (0 to 7). Example: F94.7 or F94:7

- Bits in flag bytes => Fx.y_n or Fx:y_n, Fx.y_n_l or Fx:y_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples: F94.7_24 or F94:7_24, F94.7_24_8 or F94:7_24_8

- Input bits => Ix.y or Ix:y (type: BIT) x: Number of the input byte (0 to 127). y: Rank of the first bit in the input byte (0 to 7). Example: I94.7 or I94:7

- Input bits => Ix.y_n or Ix:y_n, Ix.y_n_l or Ix:y_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : I94.7_24 or I94:7_24, I94.7_24_8 or I94:7_24_8


WoodheadWoodhead


- Output bits => Qx.y or Qx:y (type: BIT) x: Number of the output byte (0 to 127). y: Rank of the first bit in the output byte (0 to 7). Example : Q94.7 or Q94:7

- Output bits => Qx.y_n or Qx:y_n, Qx.y_n_l or Qx:y_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : Q94.7_24 or Q94:7_24, Q94.7_24_8 or Q94:7_24_8

- Bits of DB word => DBxDy.z or DBxDy:z (type: BIT) x: DB number (1 to 255). y: Number of the first word in the DB (0 to 255). z: Rank of the first bit (0 to 15). Example: DB94D10.7 or DB94D10:7

- Bits of DB word => DBxDy.z_n or DBxDy:z_n, DBxDy.z_n_l or DBxDy:z_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : DB94D10.7_24 or DB94D10:7_24, DB2D3.7_24_8 or DB2D3:7_24_8

- Bits of DX word => DXxDy.z or DXxDy:z (type: BIT) x: DX number (0 to 255). y: Number of the first word in the DX (0 to 255). z: Rank of the first bit (0 to 15). Example: DX94D10.7 or DX94D10:7

- Bits of DX word => DXxDy.z_n or DXxDy:z_n, DXxDy.z_n_l or DXxDy:z_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : DX94D10.7_24 or DX94D10:7_24, DX2D3.7_24_8 or DX2D3:7_24_8

- Flag bytes => FYx (type: BYTE) x: First flag byte number (0 to 255). Example: FY4

- Flag bytes => FYx_n, FYx_n_l n: Number of bytes. l: Number of bytes per line (Matrix mode only). Examples : FY4_10 or FY4_10_5

- Input bytes => IBx (type: BYTE) x: Number of the first input byte (0 to 127). Example: IB4

- Input bytes => IBx_n, IBx_n_l n: Number of bytes. l: Number of bytes per line (Matrix mode only). Examples : IB4_10, IB4_10_5


WoodheadWoodhead


- Output bytes => QYx (type: BYTE)

x: Number of the first output byte (0 to 127). Example: QY4

- Output bytes => QYx_n, QYx_n_l n: Number of bytes. l: Number of bytes per line (Matrix mode only). Examples: QY4_10, QY4_10_5

- ASCII string in flag bytes => M_FYx_n (type: BYTE) For more information on the use of the ASCII string, you can consult the chapter "Use of message

mode". x: Number of first flag byte containing the string (0 to 255). n: Number of potential flag byte that could contain the ASCII string (1 to 131). Example: M_FY100_10 In the example the flag bytes array FY100 to FY109 can contain the string.

- Words in flag bytes => FWx (type: 16 bit WORD) x: Number of the first word (0 to 254). Example: FW4

- Words in flag bytes => FWx_n, FWx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : FW4_10, FW4_10_5

- Input words => IWx (type: 16 bit WORD) x: Number of the first word (0 to 126). Example: IW4

- Input words => IWx_n, IWx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : IW4_10, IW4_10_5

- Output words => QWx (type: 16 bit WORD) x: Number of the first word (0 to 126). Example: QW4

- Output words => QWx_n, QWx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples: QW4_10, QW4_10_5

- Words in DB => DBxDWy (type: 16 bit WORD) x: DB number (1 to 255). y: Number of the first word in the DB (0 to 255).


WoodheadWoodhead


Example: DB4DW8

- Words in DB => DBxDWy_n, DBxDWy_n_l n: Number of words. l: Number of words per line (Matrix mode only). Example : DB4DW8_10, DB4DW8_10_5

- Words in DX => DXxDWy (type: 16 bit WORD) x: DX number (0 to 255). y: Number of the first word in the DX (0 to 255). Example: DX4DW8

- Words in DX => DXxDWy_n, DXxDWy_n_l n: Number of words. l: Number of words per line (Matrix mode only). Example : DX4DW8_10, DX4DW8_10_5

- Right byte of a word in the DB => DBxDRy (type: BIT) For this syntax, the maximum numbers of variables per frame are:


x: DB number (1 to 255). y: Number of the word in the DB (0 to 255). Example: DB4DR5

- Left byte of a word in the DB => DBxDLy (type: BIT) For this syntax, the maximum numbers of variables per frame are:


x: DB number (1 to 255). y: Number of the word in the DB (0 to 255). Example : DB4DL5

- Right byte of a word in the DX => DXxDRy (type: BIT)

For this syntax, the maximum numbers of variables per frame are:


x: DX number (0 to 255). y: Number of the word in the DX (0 to 255). Example: DX4DR5

- Left byte of a word in the DX => DXxDLy (type: BIT) For this syntax, the maximum numbers of variables per frame are:


x: DB number (0 to 255). y: Number of the word in the DX (0 to 255). Example : DX4DL5


WoodheadWoodhead


- ASCII string in DB words => M_DBxDWy_n (type: 16 bit WORD)

For more information on the use of the ASCII string, you can consult the chapter "Use of message

mode". x: DB number (1 to 255). y: Number of the first word in the DB containing the string (0 to 255). n: Number of potential words that could contain the ASCII string (1 to 65). Example: M_DB4DW0_10 In the example the word array DB4DW0 to DB4DW9 can contain the string.

- ASCII string in DX words => M_DXxDWy_n (type: 16 bit WORD) For more information on the use of the ASCII string, you can consult the chapter "Use of message

mode". x: DX number (0 to 255). y: Number of the first word in the DX containing the string (0 to 255). n: Number of potential words that could contain the ASCII string (1 to 65). Example: M_DX4DW0_10 In the example the word array DX4DW0 to DX4DW9 can contain the string.

- Double words in flag bytes => FDx (type: 32 bit WORD) x: First flag byte number (0 to 255). Example: FD4

- Double words in flag bytes => FDx_n, FDx_n_l n: Number of double words. l: Number of double words per line (Matrix mode only). Examples: FD4_10, FD4_10_5

- Floating words in flag bytes => FDxKG (type: 32 bit IEEE REAL) x: Number of the floating word (0 to 252). KC: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format. Example: FD48KG

- Double words in DB => DBxDDy (type: 32 bit WORD) x: DB number (1 to 255). y: First DB word number (0 to 254). Example: DB4DD8

- Double words in DB => DBxDDy_n, DBxDDy_n_l n: Number of double words. l: Number of double words per line (Matrix mode only). Examples : DB4DD8_10, DB4DD8_10_5

- Double words in DX => DXxDDy (type: 32 bit WORD) x: DX number (0 to 255). y: First DX word number (0 to 254).


WoodheadWoodhead


Example: DX4DD8

- Double words in DX => DXxDDy_n, DXxDDy_n_l n: Number of double words. l: Number of double words per line (Matrix mode only). Examples : DX4DD8_10, DX4DD8_10_5

- Floating words in DB => DBxDDyKG (type: 32 bit IEEE REAL) x: DB number (1 to 255). y: First DB word number (0 to 254). KC: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format. Example : DB4DD8KG

- Floating words in DX => DXxDDyKG (type: 32 bit IEEE REAL) x: DX number (0 to 255). y: First DX word number (0 to 254). KC: Suffix used to convert a word into KG format of Siemens PLCs to IEEE format. Example : DX4DD8KG

- Timers => TBx (type: 16 bit WORD) x: Number of the timer (0 to 255). Example: TB4

- Timers => TBx_n, TBx_n_l n: Number of timers. l: Number of timers per line (Matrix mode only). Examples : TB4_10, TB4_10_5

- Counters => ZBx (type: 16 bit WORD) x: Number of the counter (0 to 255). Example: ZB4

- Counters => ZBx_n, ZBx_n_l n: Number of counters. l: Number of counters per line (Matrix mode only). Examples : ZB4_10, ZB4_10_5


WoodheadWoodhead

Industrial Ethernet on PCI2000ETH (TCP/IP and ISO layer 4) and SW1000ETH (TCP/IP) • 72 • - SIMATIC® S7-400, S7-300 (S7 messaging)

5. - SIMATIC® S7-400, S7-300 (S7 messaging)

- Functionality........................................................................................................73

- Industrial Ethernet client........................................................................ 73 - Estimating the performance of an applicom® Industrial Ethernet Client. ...... 79 - Industrial Ethernet server ...................................................................... 83

- Configuration.......................................................................................................85 - Configuring a SIMATIC® S7-400, S7-300, S7-200 server equipment............ 85 - Configuring a SIMATIC® S7 client equipment............................................ 89

- Implementation of Siemens SIMATIC® S7 equipments......................................91 - Description........................................................................................... 91 - Configuring the PLC with Step7............................................................... 91 - Configuring the applicom® server........................................................... 98

- Implementation of Siemens SIMATIC® S7-200 equipment with the CP243-1 coupler ................................................................................................................102

- Description......................................................................................... 102 - PLC configuration with Micro/WIN 32..................................................... 103 - applicom® board configuration .............................................................. 111 – Example of read in wait mode. ............................................................. 113

- applicom® functions usable on the master channel.........................................114 - Wait mode ......................................................................................... 114 - Deferred mode ................................................................................... 114 - Cyclic mode........................................................................................ 115

- Item of image variables.....................................................................................116 - Presentation....................................................................................... 116 - Standard descriptor............................................................................. 116 - Siemens Simatic S7 PLCs descriptor ..................................................... 121


WoodheadWoodhead


- Functionality


- Addressing mode Functions managed by choosing an Industrial Ethernet channel (S7 Protocol) can be used to

access the variables defined in the following table. The address of the variable accessed must be calculated in certain cases by referring to the "

applicom® addressing" column in the table. The item descriptor usable with PCDDE associated with this addressing is Siemens S7 Series.

S7-300 S7-400 applicom® Type of applicom® functionvariable addressing (addr) exchange (library/DLL access)

My.z y*8+z Read bits READPACKBITDBx.DBXy.z x*524288+y*8+z Write bits WRITEPACKBITEy.z y*8+z Read input bits READPACKIBITAy.z y*8+z Read output bits READPACKQBIT

Write output bits WRITEPACKQBITMBy y Read bytes READPACKBYTE,READBYTEDBx.DBBy x*65536+y Write bytes WRITEPACKBYTE,WRITEBYTEEBy y Read input bytes READPACKIBYTE,READIBYTEABy y Read output bytes READPACKQBYTE,READQBYTE

Write output bytes WRITEPACKQBYTE,WRITEQBYTEMWy y Read words READWORDDBx.DBWy x*65536+y Write words WRITEWORDEWy y Read input words READIWORDAWy y Read output words READQWORD

Write output words WRITEQWORDMDy y Read double words READDWORDDBx.DBDy x*65536+y Write double words WRITEDWORDMDyF y Read floating words READFWORDDBx.DBDyF x*65536+y Write floating words WRITEFWORDT n n Read timers READTIMER

Write timers WRITETIMERZ n n Read counters READCOUNTER

Write counters WRITECOUNTER

x : DB number y : Byte number z : Number of the bit in the byte (0 to 7) n : Timer or counter number (0 to 230) Remark : the areas V, I and Q can be accessed by this descriptor. Example :


WoodheadWoodhead


variable applicom® Type of applicom® functionaddressing (addr) exchange (library/DLL access)

VBy.z 524288+y*8+z Read bits READPACKBITWrite bits WRITEPACKBIT

Iy.z y*8+z Read input bits READPACKIBITQy.z y*8+z Read output bits READPACKQBIT

Write output bits WRITEPACKQBITVBy 65536+y Read bytes READPACKBYTE,READBYTE

Write bytes WRITEPACKBYTE,WRITEBYTEVWy 65536+y Read output words READPACKIBYTE,READIBYTE

Write output words READPACKQBYTE,READQBYTEVDy 65536+y Read double words WRITEPACKQBYTE,WRITEQBYTE

Write double words READWORD

y : Byte number. z : Number of the bit in the byte (0 to 7). Remark: access to the functions of the applicom.dll library is not supported by the SW1000ETH

solution.

- Addressing limits Every variable in DB can be addressed from the byte 0 to the byte 65535. For the bits in DB, only the DBs numbered from 1 to 8191 can be addressed. For the bytes, words, double words and floating words, only the DBs from 1 to 32767 can be

addressed


WoodheadWoodhead


- Alignments for the 16-bit words The variables of PLCs in the SIMATIC® S7 range (S7-400, S7-300 and S7-200) use a byte

addressing mode (unlike PLCs in the SIMATIC® S5 range which use a 16-bit word addressing mode). S7 messaging on applicom® Industrial Ethernet can be used to read a number of words, double or

floating words with byte, word or double word alignments.These alignment modes enable you to obtain words or double words with even or odd addresses.

Byte Words

address Even Odd0 01 12 2 3 34 45 56 6 7 7... ... ...

Figure 16 : 16-bit word alignments

For each configuration, applicom® proposes two types of alignment :

Alignment on word :

This mode returns, when reading several words, contiguous words with odd or even address. Example :

0Reading 3 words from address 0 will return words 0, 2 and 4. 1Reading 3 words from address 1 will return words 1, 3 and 5. 2

When writing, the same addressing mode is applied. Example :

0Writing 3 words from address 0 will allocate words 0, 2 and 4. 1Writing 3 words from address 1 will allocate words 1, 3 and 5. 2

Alignment on byte :

This mode offers the advantage, when reading several words, of returning the words of odd and even address. Example :

0Reading 4 words from address 1 will return words 1, 2, 3 and 4. 1

When writing several words, « alignment on word address » is applied.


WoodheadWoodhead


- Alignments for double words of 32 bits

Byte Double wordsaddress

0 01 12 23 34 4 5 56 67 78 8 9 910 1011 1112 12... ... ... ... ...

Figure 17 : 32-bit word alignments

For each configuration, applicom® proposes three types of alignment :

Alignment on double word : 0

This mode returns, when reading several double words, contiguous double words with an address step of 4 bytes. Exemple : Reading 3 double words from address 0 will return the double words 0, 4 and 8. Reading 3 double words from address 1 will return the double words 1, 5 and 9. Reading 3 double words from address 2 will return the double words 2, 6 and 10. When writing, the same addressing mode is applied. Example : Writing 3 double words from address 0 will allocate the double words 0, 4 and 8. Writing 3 double words from address 01 will allocate the double words 1, 5 and 9. Writing 3 double words from address 2 will allocate the double words 2, 6 and 10.

0 Alignment on word :

0 This mode returns, when reading several words, contiguous words of even or odd address. Example : Reading 3 double words from address 0 will return the double words 0, 2 and 4. Reading 3 double words from address 1 will return the double words 1, 3 and 5.

0 When writing several double words, « alignment on double word » is applied.

0 Alignment on byte :

This mode offers the advantage, when reading several words, of returning the words of odd and even address. Example : Reading 4 double words from address 1 will return the double words 1, 2, 3 and 4.

0 When writing several double words, « alignment on double word » is applied.


WoodheadWoodhead


- Maximum number of variables per exchange with the library Remark: access to the functions of the applicom.dll library is not supported by the SW1000ETH

solution. The maximum number of variables is given with 1584 bytes exchange data buffers.

Object Max. quantity in read Max. quantity in writePLC PLC PLC PLC

S7-300* S7-400 S7-300* S7-400Bit 1769 3689 8 1614Byte 222 462 212 452Word 111 231 106 226Double Word 55 115 53 113Timer/counter 111 231 106 226

* : The maximum numbers of variables for S7-200 and S7-300 are identical.

The maximum quantities in read are different according to addressing mode (byte, word or double

word) for S7-300, S7-200 and S7-400 PLC’s. The maximum quantities in read and in write are different for S7-300 and S7-400 PLC’s. The

maximum quantities for S7-400 are values by default in particular for PCDDE software. It is necessary to change these limits when you declare Topics in PCDDE for S7-300 PLC.


Object Max. quantity in read Max. quantity in writeAlignment byte word double wordPLC S7-300* S7-400 S7-300* S7-400 S7-300* S7-400 S7-300* S7-400Bit 1769 2048 1 1Byte 222 462 1 1Word 128 231 111 231 1 1Double Word 64 115 64 115 55 115 1 1PLC S7-300* S7-400 S7-300* S7-400Timer/counter 111 231 1 1

* : The maximum numbers of variables for S7-200 and S7-300 are identical. The maximum quantities in read are different according to addressing mode (byte, word or double

word) for S7-300, S7-200 and S7-400 PLC’s. The maximum quantities in read and in write are different for S7-300 and S7-400 PLC’s. The number given for read frames corresponds to the maximum number of points (as imposed by

the server and/or the protocol) which can be grouped together during dynamic optimization of the frames carried out by the server. However, this number can be reduced to suit a specific item of equipment by configuring the length of frames in the topic (see chapter " chapter "Implementation/Topics configuration/Advanced options"). Where write operations are concerned, a variable automatically entails the formation of a frame.


WoodheadWoodhead


- Maximum number of variables per exchange with OPC server

Object Max. quantity in read Max. quantity in writeAlignment byte word double wordPLC S7-300* S7-400 S7-300* S7-400 S7-300* S7-400 S7-300* S7-400Bit 1769 2048 8 1614Byte 222 462 212 452Word 128 231 111 231 106 226Double Word 64 115 64 115 55 115 53 113PLC S7-300* S7-400 S7-300* S7-400Timer/counter 111 231 106 226

* : The maximum numbers of variables for S7-200 and S7-300 are identical. The maximum quantities in read are different according to addressing mode (byte, word or double

word) for S7-300, S7-200 and S7-400 PLC’s. The maximum quantities in read and in write are different for S7-200, S7-300 and S7-400 PLC’s. The number given for read frames corresponds to the maximum number of points (as imposed by


For the write frames, see the chapter " OPC Server/Synchronous and Asynchronous Request Optimization".


WoodheadWoodhead



Remark: it is impossible to estimate the performance of the SW1000ETH solution since it mainly depends on the performance of the host computer. This estimation is made in the worst context where the applicom® Industrial Ethernet Station is uniquely Industrial Ethernet CLIENT, all variables are refreshed by permanently active cyclic read functions. When the applicom® interface Industrial Ethernet SERVER is used (the PLCs place event variables in the database) the time to feed back data into the applicom® database is approximately equal to the Industrial Ethernet CLIENT PLC cycle time. Reminder: the Industrial Ethernet SERVER and CLIENT functionality can be accumulated. Estimating the performance is done using an example: The applicom® interface must feed back variables coming from Siemens stations type S7-400 with a CPU 414-2 and

• either a CP 443-1 coupler card on the Industrial Ethernet ISO Layer 4 network. • or a CP 443-1 TCP on the Industrial Ethernet TCP/IP network.

The PLCs are loaded with a cycle time of 20ms. The PLC configuration is described in the chapter "- Implementation of Siemens SIMATIC® S7 equipments" on page 91. No inter-PLC exchange is active. Number of variables :

3 tables of 231 words and 1 table of 3689 bits per station.

Industrial Ethernet ISO Layer 4 Network :


WoodheadWoodhead


0,00

50,00

100,00

150,00

200,00

250,00

300,00

350,00

400,00

450,00

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Number of Station

Req

uest

s / s

1 simultaneous request by station2 simultaneous requests by station

0%

5%

10%

15%

20%

25%

30%

35%

40%

45%

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Number of Station

Net

wor

k Lo

ad



WoodheadWoodhead


Industrial Ethernet TCP/IP Network :

0,00

50,00

100,00

150,00

200,00

250,00

300,00

350,00

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Number of Station

Req

uest

s / s


0,00%

5,00%

10,00%

15,00%

20,00%

25,00%

30,00%

35,00%

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Number of Station

Net

wor

k Lo

ad



WoodheadWoodhead


Remark :

The number of simultaneous requests generated by the applicom® Industrial Ethernet client is configured to 24 (default value in the console). See chapter "- Ethernet : " on page 8.

The number of simultaneous requests by equipment can be setting. See chapter "- Configuring a SIMATIC® S7-400, S7-300, S7-200 server equipment" on page 85.

The network load is for an Ethernet network at 10 Mb.

applicom® database retrieval time (Except application and supervision) :

In our example, to retrieve variables from 12 equipments (36 tables of 231 words and 12 tables of 3689 bits), i.e. in all 8316 words and 44268 bits, 48 requests are used :

• On the Industrial Ethernet ISO Layer 4 network : 0 with 1 simultaneous request by equipment :

148 (requests) / 210 (requests/s) = 0.228 second. 2 with 2 simultaneous requests by equipment :

348 (requests) / 305 (requests/s) = 0.157 second. • On the Industrial Ethernet TCP/IP network : 4 with 1 simultaneous request by equipment :

548 (requests) / 160 (requests/s) = 0.300 second. 6 with 2 simultaneous requests by equipment :

748 (requests) / 245 (requests/s) = 0.196 second.


WoodheadWoodhead


- Industrial Ethernet server The Industrial Ethernet Server on applicom® interface makes available a 32 kwords database to

Simatic S7 network architecture clients (protocol S7).

Supported Type of data in Addresses in Correspondingrequests DATABASE DATABASE S7 addresses

Read inputs (EB) byte area 0 - 127 EB0 à EB127Read outputs (AB) byte area 128 - 255 AB0 à AB127Read memos (MB) byte area 256 - 511 MB0 à MB255Read data blocks (DB) word area 256 - 31999 DB1.DBW0 à DB124.DBW255

DB1.DBD0 à DB124.DBD254Read data blocks (DB) byte area 1200 - 13999 DB100.DBB0 à DB124.DBB511Write outputs (AB) byte area 128 - 255 AB0 à AB127Write memos (MB) byte area 256 - 511 MB0 à MB255Write data blocks (DB) word area 256 - 31999 DB1.DBW0 à DB124.DBW255

DB1.DBD0 à DB124.DBD254Write data blocks (DB) byte area 1200 - 13999 DB100.DBB0 à DB124.DBB511

Notes: Seen by the client PLCs, the DATA-BASE manages virtually 124 blocks of data of 256 words in its

word and/or byte area. The client PLC program must generate blocks with parameters identical to those used to access the DBs in server PLCs. To find the equivalent address on the applicom® database, use the formulae:

• for bytes in a DB DBx.DBBy x*512+y

x : DB n° (1 to 124) (DB0 forbidden) y : N° of DBB byte in the DB (0 to 511)

• for words in a DB DBx.DBWy x*256+y

x : DB n° (1 to 127) (DB0 forbidden) y : N° of DBW word in the DB (0 to 255)

Maximum number of variables per exchange:

128 input or output bytes 256 memory bytes 512 bytes or 256 DB words

The Industrial Ethernet Server functionality on the applicom® database can be used to optimize

data feedback. Rather than permanently polling equipments to monitor variables changing status occasionally, the equipments can put the data to feed back only on change of status (alarm feedback) in the applicom® database. Consequently, in this operating mode:

• The PLC processors are used less. • The network architecture is less heavily loaded. • Data feedback time is minimized.


WoodheadWoodhead


This principle can be made reliable on the Industrial Ethernet Server on applicom® interface to avoid « working blind ». For example, variables in the applicom® database do not move since the transmitting equipment is disconnected. To do this:

• You can define a global maximum time interval between client equipment accesses to

the applicom® Industrial Ethernet Server, by using configuration utility. After this interval, absence is signaled to the application by an « ACCESS STATUS WORD » in the

applicom® database. Use the address of this status word using the channel configuration utility.

• The application is informed of the write access by each equipment to the applicom® Industrial Ethernet Server by incrementing an « ACCESS INDICATOR WORD » in the applicom® database. The application can query the variables of this equipment in the applicom® database and reset the « ACCESS INDICATOR WORD » to zero, to be informed of the next access (or even to inform the transmitting equipment of this acknowledgment).


WoodheadWoodhead


- Configuration

- Configuring a SIMATIC® S7-400, S7-300, S7-200 server equipment

General configuration This protocol can only be configured on the applicom® interfaces with a PCI2000ETH Ethernet

channel. After selecting the SIMATIC S7-400, SIMATIC S7-300 or SIMATIC S7-200 type, choosing the

equipment number and entering the network parameters, you must define the « Messaging parameters »zone :

Figure 18: General configuration of a server device



WoodheadWoodhead


- Messaging parameters S7-300 and S7-400

Figure 19 : Messaging Parameters of a server device

Rack number Number of the rack where the CPU module to be polled is located. Value from 0 to 7, 0 by default.

CPU slot Position in the rack of the CPU module to be polled. Value from 2 to 31, 3 by default for a S7-400 and 2 for a S7-300. These numbers (rack and CPU) must be identical to those defined in the PLC hardware configuration using the Step7 utility. They will be transmitted to the server equipment during the connection phase to establish the connection.

Maximum number of simultaneous requests Limits the number of simultaneous requests per equipment.

Value: from 1 to 4, 2 by default for an S7-400, from 1 to 2, 1 by default for an S7-300.

Link type

This parameter is used to define the link type that the applicom® interface must use for the S7 connection.

Value: Standard: link available for the applications, it permits several simultaneous requests. PG: link reserved for the programming console but can be used in S7 with the applicom®

interface in a single simultaneous request. OP: link reserved for the operator panel but can be used in S7 with the applicom® interface

in a single simultaneous request.


WoodheadWoodhead


Remark: depending on the PLC type and the CPU type, the number of standard links available may vary.

S7-300 S7-400 S7-400 S7-400

CPU 314, 315 CPU 412, 413 CPU 414 CPU 416Standard 2 14 30 62PG 1 1 1 1OP 1 1 1 1

If all connections are taken (Standard, PG and OP), no new connection will be accepted (status 70).

The following parameters are accessible only in expert mode.

Alignment for the 16-bit words This parameter is used to make the byte or 16-bit word alignments for the 16-bit words, see chapter "- Alignments for the 16-bit words" on page 75. Value « on byte » or « on 16-bit word », « on 16-bit word » by default.

Alignment for the 32-bit words This parameter is used to make the byte, word or double word alignments for the 32-bit floating or double words, see chapter "- Alignments for double words of 32 bits" on page 76. Value « on byte » , « on 16-bit word » or « on 32-bit word », « on 32-bit word » by default. For any further information concerning the PLC configuration, refer to SIEMENS documentation.


WoodheadWoodhead


S7-200 messaging parameters

Figure 20 : Messaging parameters of S7-200 server equipment

Local TSAP. This parameter is used to configure the local equipment TSAP, corresponding to the client TSAP in Micro/WIN 32 for the configuration of the server link in the S7-200.

Remote TSAP.

This parameter is used to configure the remote equipment TSAP, corresponding to the server TSAP in Micro/WIN 32 for the configuration of the server link in the S7-200.

Alignment for the 16-bit words This parameter is used to carry out the byte or 16-bit word alignments for the 16-bit words, see chapter - Alignments for the 16-bit words. Value "on byte" or "on 16-bit word", by default "on 16-bit word".

Alignment for the 32-bit words

This parameter is used to carry out the byte, word or double word alignments for the 32-bit double or floating words, see - Alignments for double words of 32 bits. Value "on byte", "on 16-bit word" or "on 32-bit word", by default "on 32-bit word".

For any other information concerning the configuration of PLCs, refer to SIEMENS documentation.


WoodheadWoodhead


- Configuring a SIMATIC® S7 client equipment

General configuration This protocol can only be configured on applicom® interfaces with an Ethernet channel

(PCI2000ETH). After selecting SIMATIC S7 type, choosing the equipment number and completing the network

parameters, you must define the « Messaging parameters » zone :

Figure 21 : General configuration of a client device



WoodheadWoodhead


Messaging parameters

Figure 22 : Messaging Parameters of a client device

Access time-out Definition of the access time-out to the applicom® Industrial Ethernet server. Value from 0 to 65535, 5 by default. This value determines the maximum time interval between the accesses of the client to the applicom® server. After this delay, its absence will be automatically indicated in the « Access status words » of the applicom® database, see "- Ethernet: SIMATIC" on page 12.


WoodheadWoodhead


- Implementation of Siemens SIMATIC® S7 equipments

- Description In this example, 2 types of exchange are carried out : • The applicom® board is client of a SIMATIC® S7 PLC and the application program can write

words in the PLC in wait mode. • The applicom® board is SIMATIC® S7 Industrial Ethernet server and the PLC can read bytes

in the applicom® DATA-BASE. Ethernet address of the applicom®board : 080006010010 PLC Ethernet address : 080006010000 (CP343-1) and 080006010001 (CP 343-1 TCP) PLC IP address : 140.152.3.2 CPU slot : 3

- Configuring the PLC with Step7

The configuration is carried out with the Step7 software supplied by SIEMENS. For further information, refer to SIEMENS documentation.

First create a project in the environment.

Figure 23 : STEP7 : project


WoodheadWoodhead


Then, declare the basic hardware configuration of your PLC : 1 Rack 1 Power supply 1 Central Processing Unit(note the slot number for the server equipment configuration) 1 Coupler « Industrial Ethernet » CP443-1.or CP443-1TCP

Figure 24 : STEP7 : hardware configuration

Then, click on the line corresponding to the coupler to set its Ethernet address parameters.


WoodheadWoodhead


Define an Ethernet network with a basic Ethernet address and/or the IP parameters (basic address, sub-network mask, router) :

Figure 25 : STEP7 : new sub-network

Then configure the couplers CP 443-1 and CP443-1 TCP, attached to network defined.

Figure 26 : STEP7 : properties of the CP 443-1 Ethernet partner


WoodheadWoodhead


Figure 27 : STEP7 : properties of the CP 443-1 TCP Ethernet partner

Definition of the link with the applicom® Industrial Ethernet server. Add a station of type SIMATIC® S7-400 (ex : « applicom® card »)

Figure 28 : STEP7 : applicom® partner


WoodheadWoodhead


Run NETPRO, the link configurator, by clicking on « Links »

Figure 29 : STEP7 : applicom® partner link

Both stations are now on the Ethernet network. Select the CPU of the SIMATIC® S7-400 and then add a

link in the table with the applicom® card:

Figure 30 : STEP7 : new link


WoodheadWoodhead


We then obtain the link with the following characteristics :

Figure 31 : STEP7 :link table

Choose the coupler used for the link : CP443-1 or CP 443-1 TCP

Figure 32 : STEP7 : link properties

Note the local ID, for the communication block.


WoodheadWoodhead


Save the configuration, and add a program using the « GET » function block to read the data on the applicom® partner :

Example of GET block, use bit M500.4 to read 10 bytes from DB100.DBB0 and store the values in

the PLC DB100.

Figure 33 : STEP7 : Communication with the GET block

Lastly, load the configuration in the PLC in « Stop » mode; then transfer into « Run » mode. The green indicator lights of the CPU and coupler must be lit steadily. The coupler is ready to run and make a connection from the first request, after executing the initiation file

« pcinit ».


WoodheadWoodhead


- Configuring the applicom® server Define the general server characteristics with the « console » utility and the Industrial Ethernet

configurator. Definition of equipment 5 representing the PLC seen by applicom® in client

Figure 34 : Example : server device, General Configuration


WoodheadWoodhead


Figure 35 : Example : server device, Messaging Parameters

- Cyclic read function Creation of the cyclic read function in the PLC using « PCCYC »


WoodheadWoodhead


Figure 36 : Example : cyclic function


WoodheadWoodhead


- Example of writing in wait mode in the PLC

Figure 37 : Example : wait mode writing


WoodheadWoodhead


- Implementation of Siemens SIMATIC® S7-200 equipment with the CP243-1 coupler

- Description

In this example, 1 type of exchange is carried out: • The applicom® board is client of a SIMATIC® S7 PLC and the application program can read bytes in

the PLC in wait mode.

IP address of the cache : 128.127.56.50 IP address of the PLC : 128.127.56.227


WoodheadWoodhead


- PLC configuration with Micro/WIN 32

Configuration is carried out with MicroWin V3.2.1 software supplied by SIEMENS. For further information, refer to SIEMENS documentation.

You must first create a project in the Micro\WIN environment File\New\.

Figure 38 : Micro/WIN 32 : project

Description of elements to be used to configure the S7-200: • Communication: To configure the communication with the S7-200. • Ethernet wizard: To configure the Ethernet coupler on the S7-200 equipment (ref.: CP243-1) the

Micro/WIN 32 "Ethernet wizard" will be used.


WoodheadWoodhead


The two equipment configuration phases are explained below: First phase: To communicate with the S7-200 you must configure the Micro/WIN 32 communication module from the control panel "PG-PC interface configuration". You must indicate the network board which is used to access the S7-200 equipment.

Figure 39 : Micro/WIN 32 : Communication.

Second phase: The second phase consists of configuring the Ethernet module of the S7-200. The Micro/WIN 32 "Ethernet wizard" is used. You must set the position of the CP243-1 coupler with respect to the AP. Allocation can be carried out automatically by clicking on "Read modules".


WoodheadWoodhead


Figure 40 : Micro/WIN 32 : Module position.


WoodheadWoodhead


You must then enter: • the IP address of the CP243-1 coupler. • its subnetwork mask. • the gateway address. • The type of communication link.

Figure 41 : Micro/WIN 32 : Module address.


WoodheadWoodhead


You must then indicate the number of links you want to use. A link can be either server or client, a maximum of 8 links can be configured. In our example a server link will be used. Give address Q, this address can be obtained automatically if you have read the module position at the start of the second phase.

Figure 42 : Micro/WIN 32 : Number of links.


WoodheadWoodhead


Now configure the link defined above. The link can be client or server. In our example it will be a server link.

Figure 43 : Micro/WIN 32 : Link definition.

Local ownership (server) • TSAP

The first byte of the TSAP is 0x10 + link number. To indicate that a server is connecting to a SIMATIC operator panel (OP), check the box

“This server is going to connect to an operator panel (OP)”. If you select this option the first byte of the TSAP will be changed to “02”. There can be only one server link to an OP per configuration.

Remark: This TSAP will be the Remote TSAP found in the configurator of the applicom® S7-200 server

• Accept all link requests..

Used to filter the requests from a client on its IP address.


WoodheadWoodhead


Remote ownership (client)

• TSAP The first byte of the TSAP is 0x10 + link number. The second byte of the TSAP is the module position. These fields can be modified to set user values. Remark: This TSAP will be the Local TSAP found in the configurator of the applicom® S7-200 server.


WoodheadWoodhead


The Ethernet wizard will then generate the sub-program "ETH0_CTRL".

Figure 44 : Micro/WIN 32 : Generating the sub-program.

Once the sub-program has been generated, you can call the control block ETHx_CTRL in the OB1.

Once this phase is completed, you must load this configuration into the PLC.

Click on the "download cpu" button .


WoodheadWoodhead


- applicom® board configuration

You must define the general properties of the applicom® channel in the "console". • IP address. • etc.

To do this refer to the "General configuration" chapter in this documentation. Then define the properties of the Simatic S7-200 server equipment. General configuration:

Enter the IP address of the PLC. In our example 128.127.56.227.

Figure 45 : Example: server equipment, General configuration


WoodheadWoodhead


Messaging parameters: Enter the values of the local and remote TSAPs for the S7-200 PLC. The values of the local and remote TSAPs are those configured in the S7-200 PLC in the section "PLC configuration with Micro/WIN 32". In our example:

Figure 46 : Example: server equipment, Messaging parameters

Once the configuration is finished you must reset the board.


WoodheadWoodhead


– Example of read in wait mode.

Example of read in wait mode: 10 bytes in area V of the S7-200 equipment configured in the above chapter.


WoodheadWoodhead



solution.

- Wait mode

readpackbit writepackbit readpackibit readpackqbit writepackqbit readbyte writebyte readibyte readqbyte writeqbyte readpackbyte writepackbyte readpackibyte readpackqbyte writepackqbyte readword writeword readiword readqword writeqword readwordbcd writewordbcd readdword writedword readfword writefword readtimer writetimer readcounter writecounter

- Deferred mode

readdifbit writedifpackbit readdifibit readdifqbit writedifpackqbit readdifbyte writedifpackbyte readdifibyte readdifqbyte writedifpackqbyte readdifword writedifword readdifiword readdifqword writedifqword readdifdword writedifdword readdiffword writediffword testtransdif transdif transdifpack


WoodheadWoodhead


- Cyclic mode




Packed bits X X Input packed bits X Output packed bits X X Packed bytes X X Bytes X X Input packed bytes X Input bytes X Output packed bytes X X Output bytes X X Words X X BCD words X X Input words X Output words X X 32 bit double words X X 32 bit IEEE floating words X X


WoodheadWoodhead


- Item of image variables

- Presentation The "item of image variables" are the syntaxes which allow to access to the variables through the

DDE server "PCDDE" or the OPC server.

- With the DDE server, the item is the part "item name" of the DDE connection defined by: 0- application name 1- topic name 2- item name

Report you to sections "DDE server/Principles regarding access to Data" or "OPC server/Data Access Principle".

Caution, if you change the default descriptor, some optimizations of access to the equipment will be



- Standard descriptor The standard descriptor can be used for access to the equipments which have not specific



Internal bits Bx Bx_n, Bx_n_l Input bits BIx BIx_n, BIx_n_l Output bits BOx BOx_n, BOx_n_l Internal bytes Ox Ox_n, Ox_n_l Bits in internal bytes Ox.b Input bytes OIx OIx_n, OIx_n_l Output bytes OOx OOx_n, OOx_n_l ASCII string in internal bytes M_Ox_n Internal words Wx Wx_n, Wx_n_l Bits in internal words Wx.b Input words WIx WIx_n, WIx_n_l Output words WOx WOx_n, WOx_n_l ASCII string in internal words M_Wx_n Internal double words Dx Dx_n, Dx_n_l Internal floating words Fx Fx_n, Fx_n_l


WoodheadWoodhead


Remarks:



- Internal bits => Bx (type : BIT) x: Number of the first bit. Example: B4

- Internal bits => Bx_n, Bx_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : B4_10, B4_10_5

- Input bits => BIx (type : BIT) x: Number of the first bit. Example : BI4


- Output bits => BOx (type : BIT) x: Number of the first bit. Example: BO4


- Internal bytes => Ox (type : BYTE) x : First byte number. Example : O4


WoodheadWoodhead


- Internal bytes => Ox_n, Ox_n_l n : Number of bytes. l : Number of bytes per line (Matrix mode only). Examples : O4_10, O4_10_5

- Bits in internal bytes => Ox.b (type : BIT) For this syntax, the maximum numbers of variables per frame are:


x : First byte number. b : Bit range in the byte (0 to 7). Example : O4.5

- Input bytes => OIx (type : BYTE) x : First byte number. Example : OI4

- Input bytes => OIx_n, OIx_n_l n : Number of bytes. l : Number of bytes per line (Matrix mode only). Examples : OI4_10, OI4_10_5

- Output bytes => OOx (type : BYTE) x : First byte number. Example : OO4

- Output bytes => OOx_n, OOx_n_l n : Number of bytes. l : Number of bytes per line (Matrix mode only). Examples : OO4_10, OO4_10_5

- ASCII string in internal bytes => M_Ox_n (type : BYTE) For more information on the use of the ASCII string, you can consult the chapter "Use of message

mode". x : Number of first byte which contains the string. n : Potential number of bytes which can contain the ASCII string (1 to 131). Example : M_O100_30 In the example, the byte array from O100 to O129 can contain the string.


WoodheadWoodhead


- Internal words => Wx (type : 16 bit WORD) x: Number of the first word. Example: W4

- Internal words => Wx_n, Wx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : W4_10, W4_10_5

- Bits in internal words => Wx.b (type : BIT) For this syntax, the maximum numbers of variables per frame are:


x: Number of the first word. b: Rank of the bit in the word (0 to 15). Example : W4.5

- Input words => WIx (type : 16 bit WORD) x: Number of the first word. Example: WI4

- Input words => WIx_n, WIx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : WI4_10, WI4_10_5

- Output words => WOx (type : 16 bit WORD) x: Number of the first word. Example: WO4



WoodheadWoodhead


- ASCII string in internal words => M_Wx_n (type : 16 bit WORD) For more information on the use of the ASCII string, you can consult the chapter "Use of message


- Internal double words => Dx (type : 32 bit WORD) x: Number of the first double word. Example: D4

- Internal double words => Dx_n, Dx_n_l n: Number of double words. l: Number of double words per line (Matrix mode only). Examples: D4_10, D4_10_5

- Internal floating words => Fx (type : 32 bit IEEE REAL) x: Number of the first floating word. Example: F4



WoodheadWoodhead


- Siemens Simatic S7 PLCs descriptor This descriptor is usable for access to the Siemens S7-200, S7-300 and S7-400 PLCs with S7

protocol. Caution : The addressing mode of the protocol task forbids the utilization of the array mode

and matrix mode in the word, double word and floating word type variables. Unitary mode Table Mode, Matrix Mode

Memory bits Mx.y Mx.y_n, Mx.y_n_l Input bits Ex.y Ex.y_n, Ex.y_n_l Output bits Ax.y Ax.y_n, Ax.y_n_l Bits of bytes in the DB DBx.DBXy.z DBx.DBXy.z_n, DBx.DBXy.z_n_l Memory bytes MBx MBx_n, MBx_n_l Bytes in the DB DBx.DBBy DBx.DBBy_n, DBx.DBBy_n_l Input bytes EBx EBx_n, EBx_n_l Output bytes ABx ABx_n, ABx_n_l ASCII string in the memory bytes M_MBx_n ASCII string in the DB bytes M_DBx.DBBy_n Words in the memories MWx Words in the DB DBx.DBWy Input words EWx Output words AWx Double words in the memories MDx Double words in the DB DBx.DBDy Floating words in the memories MDxF Floating words in the DB DBx.DBDyF Timers Tx Tx_n, Tx_n_l Counters Zx Zx_n, Zx_n_l

Remarks:


The area V of Simatic S7 PLCs can be accessed by this descriptor: VBx.y for bits (x number of the byte, y number of the bit in the byte). VBx for bytes (x number of the byte). VWx for words (x number of the word). VDx for double words (x number of the double word).



WoodheadWoodhead


- Memory bits => Mx.y (type: BIT) x: Number of the memory bit (0 to 65 535). y: Rank of the first bit in the memory bit (0 to 7). Example : M94.7

- Memory bits => Mx.y_n, Mx.y_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : M94.7_24, M94.7_24_8

- Input bits => Ex.y (type: BIT) x: Number of the input byte (0 to 65 535). y: Rank of the first bit in the input byte (0 to 7). Example : E94.7

- Input bits => Ex.y_n, Ex.y_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : E94.7_24, E94.7_24_8

- Output bits => Ax.y (type: BIT) x: Number of the output byte (0 to 65535). y: Rank of the first bit in the output byte (0 to 7). Example : A94.7

- Output bits => Ax.y_n, Ax.y_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : A94.7_24, A94.7_24_8

- Bits of bytes in the DBs => DBx. DBXy.z (type: BIT) x: DB number (1 to 8191). y: Number of the first word in the DB (0 to 65535). z: Rank of the first bit (0 to 7). Example : DB94.DBX3.7

- Bits of bytes in the DBs => DBx. DBXy.z_n, DBx.DBXy.z _n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : DB94.DBX3.7_24, DB94.DBX3.7_24_8

- Memory bytes => MBx (type: BYTE) x: Number of the first memory byte (0 to 65535). Example : MB4


WoodheadWoodhead


- Memory bytes => MBx_n, MBx_n_l n: Number of bytes. l: Number of bytes per line (Matrix mode only). Examples : MB4_10, MB4_10_5

- Bytes in the DBs => DBx.DBBy (type: BYTE) x : DB number (1 to 32 767). y : Byte number (0 to 65 535). Example : DB4.DBB5

- Bytes in the DBs => DBx.DBBy_n, DBx.DBBy _n_l n: Number of bytes. l: Number of bytes per line (Matrix mode only). Examples : DB4.DBB5_10, DB4.DBB5_10_2

- Input bytes => EBx (type: BYTE) x: Number of the first input byte (0 to 65535). Example : EB4

- Input bytes => EBx_n, EBx_n_l n: Number of bytes. l: Number of bytes per line (Matrix mode only). Examples : EB4_10, EB4_10_5

- Output bytes => ABx (type: BYTE) x: Number of the first output byte (0 to 65535). Example : AB4

- Output bytes => ABx_n, ABx_n_l n: Number of bytes. l: Number of bytes per line (Matrix mode only). Examples : AB4_10, AB4_10_5

- ASCII string in the memory bytes => M_MBx_n (type: BYTE) For more information on the use of the ASCII string, you can consult the chapter "Use of message

mode". x: Number of the first byte containing the string (0 to 65535). n: Number of potential bytes that could contain the ASCII string (1 to 131). Example : M_MB100_10 In the example the byte array MB100 to MB109 can contain the string.


WoodheadWoodhead


- ASCII string in the DB bytes => M_DBx.DBBy_n (type: BYTE) For more information on the use of the ASCII string, you can consult the chapter "Use of message

mode". x : DB number (0 to 32 767). y: Number of the first byte containing the string (0 to 65535). n: Number of potential memory bytes that could contain the ASCII string (1 to 131). Example : M_DB1.DBB5_10 In the example the byte array DB1.DBB5 to DB1.DBB14 can contain the string.

- Words in the memories => MWx (type: 16 bit WORD) x: Number of the first word (0 to 65534). Example : MW4

- Words in the DB => DBx.DBWy (type: 16 bit WORD) x : DB number (0 to 32 767). y: Number of the first word (0 to 65 534). Example : DB4.DBW6

- Input words => EWx (type: 16 bit WORD) x: Number of the first word (0 to 65 534). Example : EW4

- Output words => AWx (type: 16 bit WORD) x: Number of the first word (0 to 65 534). Example : AW4

- Double words in the memories => MDx (type: 32 bit WORD) x : Byte number (0 to 65 532). Example : MD4

- Double words in the DB => DBx.DBDy (type: 32 bit WORD) x : DB number (0 to 32 767). y : Byte number (0 to 65 532). Example : DB1.DBD4

- Floating words in the memories => MDxF (type: 32 bit IEEE REAL) x: Number of the first byte (0 to 65 532). Example : MD4F

- Floating words in the DB => DBx.DBDyF (type: 32 bit IEEE REAL) x : DB number (1 to 32 767). y: Number of the first byte in the DB (0 to 65 532). Example : DB4.DBD8F


WoodheadWoodhead


- Timers => Tx (type: 16 bit WORD) x: Number of the timer (0 to 255). Example: T4

- Timers => Tx_n, Tx_n_l n: Number of timers. l: Number of timers per line (Matrix mode only). Examples : T4_10, T4_10_5

- Counters => Zx (type: 16 bit WORD) x: Number of the counter (0 to 255). Example: Z4

- Counters => Zx_n, Zx_n_l n: Number of counters. l: Number of counters per line (Matrix mode only). Examples : Z4_10, Z4_10_5


WoodheadWoodhead

Industrial Ethernet on PCI2000ETH (TCP/IP and ISO layer 4) and SW1000ETH (TCP/IP) • 126 • - SIMATIC® TI-505 (Camp and Read/Write TI messaging)

6. - SIMATIC® TI-505 (Camp and Read/Write TI messaging)

- Functionality......................................................................................................128

- Industrial Ethernet client...................................................................... 128 - Estimating the performance of an applicom® Industrial Ethernet Client. .... 132 - Industrial Ethernet server .................................................................... 134

- Configuring a SIMATIC® TI-505 server equipment...........................................135 - Configuring a SIMATIC® TI-505 server equipment on TCP/IP .................... 135 - Configuring a SIMATIC® TI-505 server equipment on ISO ........................ 137

- Configuring a SIMATIC TI-505 client equipment ..............................................139 General configuration ............................................................................ 139 Messaging Parameters ........................................................................... 140

- Implementation of Siemens SIMATIC® TI-505 equipment on TCP/IP..............141 - Description......................................................................................... 141 - Configuring the CP2572 coupler with IPSET.EXE ..................................... 141 - Configuring the applicom® server......................................................... 142

- Implementation of Siemens SIMATIC® TI-505 equipment on ISO ...................146 - Description......................................................................................... 146 - CP1434 Configuration.......................................................................... 146

- applicom® functions usable on the master channel.........................................152 - Wait mode ......................................................................................... 152 - Deferred mode ................................................................................... 152 - Cyclic mode........................................................................................ 153

- Item of image variables : Presentation .............................................................154 - Item of image variables : Standard descriptor ..................................................154 - Item of image variables : SIMATIC® TI-505 descriptor.....................................158

- Internal variables................................................................................ 158 - Input / output variables ....................................................................... 160 - Timers / Counters ............................................................................... 161 - Variables DRUM .................................................................................. 162 - System status .................................................................................... 163 - Constant words................................................................................... 163 - LOOP variables ................................................................................... 165 - ALARM variables ................................................................................. 168


WoodheadWoodhead



WoodheadWoodhead


- Functionality


- Addressing mode, generalities

Remark: access to the functions of the applicom.dll library is not supported by the SW1000ETH solution. The TI reachable variables are numbered from the address 1 (Ex V0001, X0001, etc.). The

applicom® addressing begins to 0. Therefore, the PLC address must be decremented of 1 (see « applicom® address » column). This addressing is valid for the usual variables (Bits, Words, Double words, Floating words).

For the (K, KF) constants, the applicom® address must have the most significant byte equals to

05. The three following bytes represent the address of the constant decremented of 1.

TI-505 applicom® Type of exchange Corresponding applicom® functionaddressing addressing (library/DLL access)

C v v - 1 Read bits READPACKBIT, READDIFBITWrite bits WRITEPACKBIT, WRITEDIFPACKBIT

V v v - 1 Read words READWORD, READDIFWORDWrite words WRITEWORD, WRITEDIFWORD

V v v - 1 Read double words READDWORD, READDIFDWORDWrite double words WRITEDWORD, WRITEDIFDWORD

VF v v - 1 Read floating words READFWORD, READDIFFWORDWrite floating words WRITEFWORD, WRITEDIFFWORD

X v v - 1 Read input bits READPACKIBIT, READDIFIBITWX v v - 1 Read input words READIWORD, READDIFIWORDY v v - 1 Read output bits READPACKQBIT, READDIFQBIT

Write output bits WRITEPACKQBIT, WRITEDIFPACKQBITWY v v - 1 Read output words READQWORD, READDIFQWORD

Write output words WRITEQWORD, WRITEDIFQWORDK v (05 00 00 00) + (v - 1) Read words READWORD, READDIFWORD

Write words WRITEWORD, WRITEDIFWORDK v (05 00 00 00) + (v - 1) Read double words READDWORD, READDIFDWORD

Write double words WRITEDWORD, WRITEDIFDWORDKF v (06 00 00 00) + (v - 1) Read floating words READFWORD, READDIFFWORD

Write floating words WRITEFWORD, WRITEDIFFWORDOther (08 cc 00 00) + (v - 1) Read READxxxx, READDIFxxxxvariables Write WRITExxxx, WRITEDIFxxxx

v : variable number, cc : address class

For the other variables (LOOP, ALARM, ...), the applicom® corresponding address must have the

the most significant byte equals to 08, the next byte equals to address class. And the two last bytes equal to the address of the variable decremented of 1.

The item descriptor usable with PCDDE associated with this addressing is Texas Instrument.


WoodheadWoodhead


• CAUTION: The CAMP messaging can only write bits with 16 bits words (case of C, X, Y variables). The applicom® software reads words containing the bits to write in API, hides and forces the user bits, then writes words in the equipment as a whole. This machinery can induce risks if the equipment has forced others bits of the word between the reading and the writing.

- Addressing mode, Loop variables Classe Nom Description Type 20 LKC Loop Gain Real 21 LTI Loop Reset Time (min) Real 22 LTD Loop Rate Time (min) Real 23 LHA Loop High Alarm Limit Real 24 LLA Loop Low Alarm Limit Real 25 LPV Loop Process Variable Real 26 LPVH Loop PV High Limit Real 27 LPVL Loop PV Low Limit Real 28 LODA Loop Orange Dev Alarm Limit Real 29 LYDA Loop Yellow Dev Alarm Limit Real 2A LTS Loop Sample Rate (sec) Real 2B LSP Loop Setpoint Real 2C LMN Loop Output (%) Real 2D LVF Loop Status (V) Flags 16 bits read 2E LCF Loop Control (C) Flags 32bit 2F LRSF Loop Ramp/Soak Status Flags 16 bits read 30 LERR Loop Error Real 31 LMX Loop Bias Real 32 LHHA Loop High-High Alarm Limit Real 33 LLLA Loop Low-Low Alarm Limit Real 34 LRCA Loop Rate of Change Alarm Limit Real 35 LSPH Loop Setpoint High Limit Real 36 LSPL Loop Setpoint Low Limit Real 37 LADB Loop Alarm Deadband Real 38 LHAR Loop Raw High Alarm Limit Integer 39 LLAR Loop Raw Low Alarm Limit Integer 3A LPVR Loop Raw Process Variable Integer 3B LODAR Loop Raw Orange Dev Alarm Limit Integer 3C LYDAR Loop Raw Yellow Dev Alarm Limit Integer 3D LMNR Loop Raw Output Integer 3E LSPR Loop Raw Setpoint Integer 3F LERRR Loop Raw Error Integer read 40 LHHAR Loop Raw High-High Alarm Limit Integer 41 LLLAR Loop Raw Low-Low Alarm Limit Integer 42 LADBR Loop Raw Alarm Deadband Integer 48 LMXR Loop Raw Bias Integer 49 LSPLR Loop Raw Setpoint Low Limit Integer 4A LSPHR Loop Raw Setpoint High Limit Integer 4B LCFH Loop C Flags - MSW Integer 4C LCFL Loop C Flags - LSW Integer 4D LKD Loop Derivative Gain Limiting Coef. Real 4E LRSN Loop Ramp/Soak Step Number Integer 4F LACK Loop Alarm Ack Flags Integer


WoodheadWoodhead


- Addressing mode, Alarm variables

Class Name Comment Type

50 AHA Alarm High Alarm Limit Real 51 ALA Alarm Low Alarm Limit Real 52 APV Alarm Process Variable Real 53 APVH Alarm PV High Limit Real 54 APVL Alarm PV Low Limit Real 55 AODA Alarm Orange Dev Alarm limit Real 56 AYDA Alarm Yellow Dev Alarm Limit Real 57 ATS Alarm Sample Rate (sec) Real 58 ASP Alarm Setpoint Real 59 AVF Alarm V Flags Integer 5A ACF Alarm C Flags Real 5B AERR Alarm Error Real 5C AHHA Alarm High-High Alarm Limit Real 5D ALLA Alarm Low-Low Alarm Limit Real 5E ARCA Alarm Rate of Change Alarm Limit Real 5F ASPH Alarm Setpoint High Limit Real 60 ASPL Alarm Setpoint Low Limit Real 61 AADB Alarm Alarm Deadband Real 62 AHAR Alarm Raw High Alarm Limit Integer 63 ALAR Alarm Raw Low Alarm Limit Integer 64 APVR Alarm Raw Process Variable Integer 65 AODAR Alarm Raw Orange Deviation Integer 66 AYDAR Alarm Raw Yellow Alarm Limit Integer 67 ASPR Alarm Raw Setpoint Integer 68 ADBR Alarm Raw Alarm Deadband Integer 69 AERRR Alarm Raw Error Integer 6A AHHAR Alarm Raw High-High Alarm Limit Integer 6B ALLAR Alarm Raw Low-Low Alarm Limit Integer 6F ASPLR Alarm Raw Setpoint Low Limit Integer 70 ASPHR Alarm Raw Setpoint High Limit Integer 71 ACFH Alarm MSW Alarm C Flag Integer 72 ACFL Alarm LSW Alarm C Flags Integer 73 AACK Analog Alarm - Alarm Ack Flag Integer

- Addressing mode, other variables

Class Name Comment Type 0E TCP Timer/Counter Preset Integer 0F TCC Timer/Counter Current Integer 10 DSP Drum Step Preset Integer 11 DSC Drum Step Current Integer 12 DCP Drum Count Preset Integer 1A STW System Status Word 16 bits read 1B DCC Drum Current Count 32 bits read


WoodheadWoodhead


- Maximum number of variables per exchange with the library

Remark: access to the functions of the applicom.dll library is not supported by the SW1000ETH solution. The maximum number of variables depends on the type of messaging :

• Camp on TCP/IP • Read/Write TI on ISO L4

Object Read Write

TCP/IP ISO L4 TCP/IP ISO L4Bit 1984 1568 784 1568Word 256 784 256 784Double/floating word 128 392 128 392


The maximum number of variables depends on the type of messaging :


Object Read WriteTCP/IP ISO L4 TCP/IP ISO L4

Bit 1984 2048 1 1Word 256 784 1 1Double/floating word 128 392 1 1



Where write operations are concerned, a variable automatically entails the formation of a frame.

- Maximum number of variables per exchange with OPC server The maximum number of variables depends on the type of messaging :


Object Read WriteTCP/IP ISO L4 TCP/IP ISO L4

Bit 1984 2048 784 2048Word 256 784 256 784Double/floating word 128 392 128 392



For write frames, see chapter "OPC Server/Synchronous and Asynchronous Request Optimization".


WoodheadWoodhead



Remark: it is impossible to estimate the performance of the SW1000ETH solution since it mainly

depends on the performance of the host computer. This estimation is made in the worst context where the applicom® Siemens station is only

CLIENT, all variables are refreshed by permanently active cyclic read functions. If the TI505 (CAMP on TCP/IP) SERVER functionality of the applicom® interface is used (The

PLCs deposit the variables on events in the database), the data feedback time in the applicom® database is virtually equal to the cycle time of the Siemens TI CLIENT PLC.

Reminder : The CLIENT and Cegelec SERVER functionalities can be combined. Performance estimation is made by using an example : The applicom® interface must provide feedback of variables from Siemens TI505 TCP/IP stations

with a UC545 and Ethernet CP2572 Interface driver board. The stations are loaded to obtain a cycle time of 50ms. No inter-PLC exchange is active. Numbers of variables :

03 tables of 256 words and 1 table of 4081 bits per station. 1

�

0,00

50,00

100,00

150,00

200,00

250,00

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Number of station

Req

uest

s / s

1 simultaneous request / station

2


WoodheadWoodhead


0,00%

5,00%

10,00%

15,00%

20,00%

25,00%

30,00%

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Number of station

Net

wor

k lo

ad

1 simultaneous request / station

Remarks:

The number of simultaneous requests generated by the applicom® Siemens TI is set to 24 (default value in the console). The number of simultaneous requests per equipment is configurable. The network load is for an Ethernet network at 10 Mb.

0 1

Retrieval time in the applicom®database (excluding application and supervision) In our example, to retrieve all variables from 24 equipments (72 tables of 256 words and 24 tables of 4081 bits), i.e. a total of 18432 words and 97944 bits, 96 requests are required :

96 (requests) / 167 (requests/s) = 0,574 second


WoodheadWoodhead


- Industrial Ethernet server The Industrial Ethernet Server on applicom® interface makes available a 32 kword database to

Siemens network architecture clients TI (READ/WRITE).

Supported Type of data Addresses in Correspondingrequests in DATABASE DATABASE TI addresses

Read bits (C) bit area 0 - 31999 C1 to C32000Read data (V) word area 0 - 31999 V1 to V32000Write bits (C) bit area 0 - 31999 C1 to C32000Write data (V) word area 0 - 31999 V1 to V32000

Maximum number of variables per exchange: 4081 data bits 256 data words The Industrial Ethernet Server functionality on the applicom® database can be used to optimize

data feedback. Rather than permanently polling equipments to monitor variables changing status occasionally, the equipments can put the data to feed back only on change of status (alarm feedback) in the applicom® database. Consequently, in this operating mode:

• The PLC processors are used less. • The network architecture is less heavily loaded. • Data feedback time is minimized.

This principle can be made reliable on the Industrial Ethernet Server on applicom® interface to

avoid « working blind ». For example, variables in the applicom® database do not move since the transmitting equipment is disconnected. To do this:

• You can define a global maximum time interval between client equipment accesses to

the applicom® Industrial Ethernet Server, by using configuration utility. After this interval, absence is signaled to the application by an « ACCESS STATUS WORD » in the

applicom® database. Use the address of this status word using the channel configuration utility.

• The application is informed of the write access by each equipment to the applicom® Industrial Ethernet Server by incrementing an « ACCESS INDICATOR WORD » in the applicom® database. The application can query the variables of this equipment in the applicom® database and reset the « ACCESS INDICATOR WORD » to zero, to be informed of the next access (or even to inform the transmitting equipment of this acknowledgment).


WoodheadWoodhead


- Configuring a SIMATIC® TI-505 server equipment

- Configuring a SIMATIC® TI-505 server equipment on TCP/IP

General configuration This protocol can only be configured on the applicom® interfaces with a PCI2000ETH Ethernet

channel. After selecting the SIMATIC® TI-505 type, entering the device number and the network parameters,

you must define the "Messaging Parameters" zone.

Figure 47 : General configuration of a server device


TCP port of the equipment. Defines the TCP port number of the remote device. Value from 1 to 65535, default value 1505.


WoodheadWoodhead




Maximum number of simultaneous requests Limits the number of simultaneous requests per equipment.

CPU type. Avoid the user to choise the CPU type about TI 505. You have the choice between CPU 565 or the others (CPU 545, CPU 555 …).



WoodheadWoodhead


- Configuring a SIMATIC® TI-505 server equipment on ISO

General configuration Remark: ISO class 4 mode is not supported by the SW1000ETH solution. This protocol can only be configured on the applicom® interfaces with a PCI2000ETH Ethernet

channel. After selecting the SIMATIC® TI-505 type, entering the device number and the network parameters,

you must define the "Messaging Parameters" zone:

Figure 39 : General configuration of a server device



WoodheadWoodhead




Local TSAP This choice is used to define the name of the local TSAP (Transport Service Access Point) for this applicom® client connection. This name will be transmitted during the connection phase to the server equipment, which can use this name as identifier.

Remote read TSAP This choice is used to define the name of the TSAP (Transport Service Access Point) for read accesses to the server PLC equipment.This name must also be defined in the server PLC coupler. Server PLC coupler configuration:

0Contract Read passive. 1Ethernet address 000000000000 (CP 1434) 2LOCAL TSAP identical to this field (READTSAP by default) 3REMOTE TSAP not defined (APPLICOM by default).

Remote write TSAP

This choice is used to define the name of the TSAP (Transport Service Access Point) for write accesses to the server PLC equipment. This name must also be defined in the server PLC coupler. Server PLC coupler configuration: 0Contract Write passive. 1Ethernet address 000000000000 (CP 1434) 2LOCAL TSAP identical to this field (WRITTSAP by default) 3REMOTE TSAP not defined (APPLICOM by default).



WoodheadWoodhead


- Configuring a SIMATIC TI-505 client equipment

General configuration This protocol can only be configured on applicom® interfaces with an Ethernet channel

(PCI2000ETH). After selecting SIMATIC® TI-505 type, entering the device number and the network parameters, you

must define the "Messaging Parameters" zone:

Figure 49 : General configuration of a client device

applicom description

See chapter "- Equipment properties". Network properties See chapter "- Equipment properties".


WoodheadWoodhead



Figure 50 : Messaging Parameters of a client device

Access time-out Definition of the access time-out to the applicom® Industrial Ethernet server. Value from 0 to 65535, 5 by default. This value determines the maximum time interval between the accesses of the client to the applicom® server. After this delay, its absence will be automatically indicated in the « Access status words » of the applicom® database, see "- Ethernet: SIMATIC" on page 12.


WoodheadWoodhead


- Implementation of Siemens SIMATIC® TI-505 equipment on TCP/IP

- Description In this example, 2 types of exchange are carried out : • The applicom® board is client of a SIMATIC® TI-505 PLC and the application program can

write words in the PLC in wait mode. • The applicom® board is SIMATIC® TI-505 Industrial Ethernet server and the PLC can read

bytes in the applicom® DATA-BASE. PLC IP address : 128.127.56.240 PLC port number : 1505 applicom® board IP address : 128.127.56.10 applicom® board port number : 1505

- Configuring the CP2572 coupler with IPSET.EXE The PC is connected to the Industrial Ethernet network via the PCI2000ETH board. Connecting the

SIEMENS PLC to the Industrial Ethernet network is carried out by installing a special communication processor : the CP2572 for the TCP/IP protocol.

This communication processor is connected directly on the motherboard bus of SIMATIC® TI-505 PLCs. There are four physical interfaces on this coupler, two to connect the Industrial Ethernet network (10BaseT & AUI connector) and the two others to access the coupler's configuration and setting (RS-232 & RS-422 connector). Traffic management on the Industrial Ethernet network is processed independently by the coupler, thereby releasing the TI-505 PLC CPU of this task.

A DOS-program, IPSET.EXE, is provided to configure the coupler.

Communication between the PLC processor and the CP2572 coupler is transparent and need no

special programming in PLC. It’s only necessary to configure the coupler to make a connection between PC and PLC


WoodheadWoodhead


- Configuring the applicom® server Define the general server characteristics with the « console » utility and the Industrial Ethernet

configurator. Definition of equipment 0 representing the PLC seen by applicom® in client

Figure 43 : Example : server device, General Configuration


WoodheadWoodhead


Figure 44 : Example : server device, Messaging Parameters


WoodheadWoodhead


Creation of the cyclic read function in the PLC using « PCCYC »

Figure 51 : Example : cyclic function


WoodheadWoodhead


- Example of writing in wait mode in the PLC

Figure 52 : Example : wait mode writing


WoodheadWoodhead


- Implementation of Siemens SIMATIC® TI-505 equipment on ISO

- Description

In this example the applicom® card is client of a SIMATIC® TI505 PLC. applicom® card Ethernet address : 080006010001 PLC Ethernet address : 080006010002 PLC TSAP in read : READTSAP PLC TSAP in write : WRITTSAP

- CP1434 Configuration

In this example, the configuration is carried out using the program 505H1 supplied by SIEMENS. This section is supplied for reference.

In the main window, select « File » then « New ». Enter « Local Ethernet Address » and declare two « Peer Services », one for Read and one for Write by pressing « insert ».


WoodheadWoodhead


Enter informations in Peer Service Read window like under

Then create a « Read Passive » « Job » type


WoodheadWoodhead


Enter informations in Peer Service Write window like under

Then create a « Write Passive » « Job » type

Save your configuration on disk. Then transfer this configuration into the CP1434. Press « Transfer » then « Download Configuration

To CP ». The coupler is ready to run and to make connection when you run script file « pcinit » or

« applicom ».


WoodheadWoodhead


- applicom® server configuration example

Define the general characteristics of server with « the console » software program.


WoodheadWoodhead


- Equipments configuration Definition of the equipment number 0 with stands for the PLC seen as client by applicom®


WoodheadWoodhead


- Example of a read in the PLC in wait mode


WoodheadWoodhead



solution.

- Wait mode

readpackbit writepackbit readpackibit readpackqbit writepackqbit readword writeword readiword readqword writeqword readwordbcd writewordbcd readdword writedword readfword writefword

- Deferred mode

readdifbit writedifpackbit readdifibit readdifqbit writedifpackqbit readdifword writedifword readdifiword readdifqword writedifqword readdifdword writedifdword readdiffword writediffword testtransdif transdif transdifpack


WoodheadWoodhead


- Cyclic mode




Packed bits X X Input packed bits X Output packed bits X X Words X X BCD words X X Input words X Output words X X 32 bit double words X X 32 bit IEEE floating words X X


WoodheadWoodhead


- Item of image variables : Presentation The "item of image variables" are the syntaxes which allow to access to the variables through the

DDE server "PCDDE" or the OPC server. Report you to sections "DDE server/Principles regarding access to Data" or "OPC server/Data

Access Principle". Caution, if you change the default descriptor, some optimizations of access to the equipment will be



- Item of image variables : Standard descriptor The standard descriptor can be used for access to the equipments which have not specific



Internal bits Bx Bx_n, Bx_n_l Input bits BIx BIx_n, BIx_n_l Output bits BOx BOx_n, BOx_n_l Internal words Wx Wx_n, Wx_n_l Bits in internal words Wx.b Input words WIx WIx_n, WIx_n_l Output words WOx WOx_n, WOx_n_l ASCII string in internal words M_Wx_n Internal double words Dx Dx_n, Dx_n_l Internal floating words Fx Fx_n, Fx_n_l


WoodheadWoodhead


Remarks :

The limiting values of the parameters n and l depend on the protocol. However, for PCDDE, they cannot be greater than 128 for bits bytes, 64 for words, 32 for double words and floating words.

To consult the read and write limits, refer to sections: "- Maximum number of variables per exchange with PCDDE" on page 131 "- Maximum number of variables per exchange with OPC server" on page 131 Refer to chapter "- Addressing mode, generalities" on page 128.

- Internal bits => Bx (type : BIT) x: Number of the first bit. Example: B4

- Internal bits => Bx_n, Bx_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : B4_10, B4_10_5

- Input bits => BIx (type : BIT) x: Number of the first bit. Example : BI4


- Output bits => BOx (type : BIT) x: Number of the first bit. Example: BO4


- Internal words => Wx (type : 16 bit WORD) x: Number of the first word. Example: W4

- Internal words => Wx_n, Wx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : W4_10, W4_10_5


WoodheadWoodhead


- Bits in internal words => Wx.b (type : BIT) For this syntax, the maximum numbers of variables per frame are:


x: Number of the first word. b: Rank of the bit in the word (0 to 15). Example : W4.5

- Input words => WIx (type : 16 bit WORD) x: Number of the first word. Example: WI4

- Input words => WIx_n, WIx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : WI4_10, WI4_10_5

- Output words => WOx (type : 16 bit WORD) x: Number of the first word. Example: WO4


- ASCII string in internal words => M_Wx_n (type : 16 bit WORD) For more information on the use of the ASCII string, you can consult the chapter "Use of message



WoodheadWoodhead


- Internal double words => Dx (type : 32 bit WORD) x: Number of the first double word. Example: D4

- Internal double words => Dx_n, Dx_n_l n: Number of double words. l: Number of double words per line (Matrix mode only). Examples: D4_10, D4_10_5

- Internal floating words => Fx (type : 32 bit IEEE REAL) x: Number of the first floating word. Example: F4



WoodheadWoodhead


- Item of image variables : SIMATIC® TI-505 descriptor This descriptor is usable only for access to the Texas Instrument equipments with applicom®

interfaces.

- Internal variables Unitary mode Table Mode, Matrix Mode

Internal bits Cx Cx_n, Cx_n_l Internal words Vx Vx_n, Vx_n_l Bits in the internal words Vx.b Internal double words VDx VDx_n, VDx_n_l Floating words VFx VFx_n, VFx_n_l ASCII string in the internal words M_Vx_n

Remarks :



- Internal bits => Cx (type : BIT) x : Number of the first bit (1 to 2 097152). Example : C4

- Internal bits => Cx_n, Cx_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : C4_10, C4_10_5

- Internal words => Vx (type : 16 bit WORD) x : Number of the first word (1 to 2 097 152). Example : V4

- Internal words => Vx_n, Vx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : V4_10, V4_10_5


WoodheadWoodhead


- Bits in the internal words => Vx.b (type : BIT) For this syntax, the maximum numbers of variables per frame are:


x : Number of the first word (1 to 2 097 152). b : Rank of the bit in the word (0 to 15). Example : V4.5

- Internal double words => VDx (type : 32 bit WORD) x : Number of the first double word (1 to 2 097 151). Example : VD4

- Internal double words => VDx_n, VDx_n_l n: Number of double words. l: Number of double words per line (Matrix mode only). Examples : VD4_10, VD4_10_5

- Floating words => VFx (type : 32 bit IEEE REAL) x : Number of the first floating word (1 to 2 097 151). Example : VF4

- Floating words => VFx_n, VFx_n_l n: Number of floating words. l: Number of floating words per line (Matrix mode only). Examples : VF4_10, VF4_10_5

- ASCII string in the internal words => M_Vx_n (type : 16 bit WORD) For more information on the use of the ASCII string, you can consult the chapter "Use of message

mode". x : Number of the first word containing the string (0 to 2 097 152). n : Number of potential words that could contain the ASCII string (1 to 65). Example : M_V100_30 In the example the word table V100 to V129 can contain the string.


WoodheadWoodhead


- Input / output variables Unitary mode Table Mode, Matrix Mode

Input bits Xx Xx_n, Xx_n_l Output bits Yx Yx_n, Yx_n_l Input words WXx WXx_n, WXx_n_l Output words WYx WYx_n, WYx_n_l

Remarks :



- Input bits => Xx (type : BIT) x : Number of the first bit (1 to 2 097 152). Example : X4

- Input bits => Xx_n, Xx_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : X4_10, X4_10_5

- Output bits => Yx (type : BIT) x : Number of the first bit (1 to 2 097 152). Example : Y4

- Output bits => Yx_n, Yx_n_l n: Number of bits. l: Number of bits per line (Matrix mode only). Examples : Y4_10, Y4_10_5

- Input words => WXx (type : 16 bit WORD) x : Number of the first word (1 to 2 097 152). Example : WX4

- Input words => WXx_n, WXx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : WX4_10, WX4_10_5


WoodheadWoodhead


- Output words => WYx (type : 16 bit WORD) x : Number of the first word (1 to 2 097 152). Example : WY4

- Output words => WYx_n, WYx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : WY4_10, WY4_10_5

- Timers / Counters Unitary mode Table Mode, Matrix Mode

Timer / counter preselection values TCPx TCPx_n, TCPx_n_l Timer / counter current values TCCx TCCx_n, TCCx_n_l

Remarks :



- Timer / counter preselection values => TCPx (type : 16 bit WORD) x : Number of the first word (1 to 65 536). Example : TCP4

- Timer / counter preselection values => TCPx_n, TCPx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : TCP4_10, TCP4_10_5

- Timer / counter current values => TCCx (type : 16 bit WORD) x : Number of the first word (1 to 65 536). Example : TCC4

- Timer / counter current values => TCCx_n, TCCx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : TCC4_10, TCC4_10_5


WoodheadWoodhead


- Variables DRUM Unitary mode Table Mode, Matrix Mode

Preselection values of the "DRUM" step DSPx DSPx_n, DSPx_n_l Values of the current "DRUM" step DSCx DSCx_n, DSCx_n_l Preselection values of the "DRUM" counter DCPx.y DCPx.y_n, DCPx.y_n_l

Remarks :



- Preselection values of the "DRUM" step => DSPx (type : 16 bit WORD) x : Number of the first word (1 to 65 536). Example : DSP4

- Preselection values of the "DRUM" step => DSPx_n, DSPx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : DSP4_10, DSP4_10_5

- Values of the current "DRUM" step => DSCx (type : 16 bit WORD) x : Number of the first word (1 to 65 536). Example : DSC4

- Values of the current "DRUM" step => DSCx_n, DSCx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : DSC4_10, DSC4_10_5

- Preselection values of the "DRUM" counter => DCPx.y (type : 16 bit WORD) x : Number of the first "DRUM" (1 to 4096). y : Number of the first step (1 to 16). Example : DCP4.5

- Preselection values of the "DRUM" counter => DCPx.y_n, DCPx.y_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : DCP4.5_10, DCP4.5_10_5


WoodheadWoodhead


- System status Unitary mode Table Mode, Matrix Mode

Values of the system status STWx STWx_n, STWx_n_l Remarks :



- Values of the system status => STWx (type : 16 bit WORD) x : Number of the first status (1 to 65 536). Example : STW4

- Values of the system status => STWx_n, STWx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : STW4_10, STW4_10_5

- Constant words Unitary mode Table Mode, Matrix Mode

Constant words Kx Kx_n, Kx_n_l Double constant words KDx KDx_n, KDx_n_l Bits in the internal constants Kx.b Constant floating words KFx KFx_n, KFx_n_l

Remarks :




WoodheadWoodhead


- Constant words => Kx (type : 16 bit WORD) x : Number of the first word (1 to 2 097 152). Example : K4

- Constant words => Kx_n, Kx_n_l n: Number of words. l: Number of words per line (Matrix mode only). Examples : K4_10, K4_10_5

- Double constant words => KDx (type : 32 bit WORD) x : Number of the first double word (1 to 2 097 151). Example : KD4

- Double constant words => KDx_n, KDx_n_l n: Number of double words. l: Number of double words per line (Matrix mode only). Examples : KD4_10, KD4_10_5

- Bits in the internal constants => Kx.b ( type : BIT) For this syntax, the maximum numbers of variables per frame are:


x : Number of the first word (1 to 2 097 152). b: Rank of the bit in the word (0 to 15). Example : K4.5

- Floating constant words => KFx (type : 32 bit IEEE REAL) x : Number of the first floating word (1 to 2 097 151). Example : KF4

- Floating constant words => KFx_n, KFx_n_l n: Number of floating words. l: Number of floating words per line (Matrix mode only). Examples : KF4_10, KF4_10_5


WoodheadWoodhead


- LOOP variables You must use this syntax with cautions, see the "Bit of word" section of the "DDE and OPC server"

manual. For this syntax, the maximum numbers of variables per frame are: in read: 128*16 in write: 1

"Array" mode (String and Matrix) provides access to the same contiguos LOOP variable. Examples : Item representing a string of data corresponding to the LKC variables of 4 LOOP from LOOP 10.

LKC10_4 This corresponds to access to variables LKC10, LKC11, LKC12, LKC13.

Item representing a string of data corresponding to the LKC variables of 4 LOOP from LOOP 10

with 2 variables per line. LKC10_4_2

This corresponds to access to variables LKC10, LKC11, LKC12, LKC13. The following array representes the "LOOP" variables with their formats and their various syntaxes.

« X » in column « L » represents the possibility of read and « X » in column « E » the possibility of write.

Variable name Variable type L E Unitary mode Table Mode, Matrix Mode

LKC 32 bit IEEE REAL X X LKCx LKCx_n, LKCx_n_l LTI 32 bit IEEE REAL X X LTIx LTIx_n, LTIx_n_l LTD 32 bit IEEE REAL X X LTDx LTDx_n, LTDx_n_l LHA 32 bit IEEE REAL X X LHAx LHAx_n, LHAx_n_l LLA 32 bit IEEE REAL X X LLAx LLAx_n, LHAx_n_l LPV 32 bit IEEE REAL X X LPVx LPVx_n, LPVx_n_l

LPVH 32 bit IEEE REAL X X LPVHx LPVHx_n, LPVHx_n_l LPVL 32 bit IEEE REAL X X LPVLx LPVLx_n, LPVLx_n_l LODA 32 bit IEEE REAL X X LODAx LODAx_n, LODAx_n_l LYDA 32 bit IEEE REAL X X LYDAx LYDAx_n, LYDAx_n_l LTS 32 bit IEEE REAL X X LTSx LTSx_n, LTSx_n_l LSP 32 bit IEEE REAL X X LSPx LSPx_n, LSPx_n_l LMN 32 bit IEEE REAL X X LMNx LMNx_n, LMNx_n_l LVF 16 bit WORD X X LVFx LVFx_n, LVFx_n_l

Bits in the words X X LVFx.b LCF 32 bit IEEE REAL X X LCFx LCFx_n, LCFx_n_l

LRSF 16 bit WORD X X LRSFx LRSFx_n, LRSFx_n_l Bits in the words X X LRSFx.b

LERR 32 bit IEEE REAL X LERRx LERRx_n, LERRx_n_l LMX 32 bit IEEE REAL X X LMXx LMXx_n, LMXx_n_l

LHHA 32 bit IEEE REAL X X LHHAx LHHAx_n, LHHAx_n_l LLLA 32 bit IEEE REAL X X LLLAx LLLAx_n, LLLAx_n_l LRCA 32 bit IEEE REAL X X LRCAx LRCAx_n, LRCAx_n_l LSPH 32 bit IEEE REAL X X LSPHx LSPHx_n, LSPHx_n_l LSPL 32 bit IEEE REAL X X LSPLx LSPLx_n, LSPLx_n_l LADB 32 bit IEEE REAL X X LADBx LADBx_n, LADBx_n_l LHAR 16 bit WORD X X LHARx LHARx_n, LHARx_n_l


WoodheadWoodhead


Bits in the words X X LHARx.b LLAR 16 bit WORD X X LLARx LLARx_n, LLARx_n_l

Bits in the words X X LLARx.b LPVR 16 bit WORD X X LPVRx LPVRx_n, LPVRx_n_l

Bits in the words X X LPVRx.b LODAR 16 bit WORD X X LODARx LODARx_n, LODARx_n_l

Bits in the words X X LODARx.b LYDAR 16 bit WORD X X LYDARx LYDARx_n, LYDARx_n_l

Bits in the words X X LYDARx.b LMNR 16 bit WORD X X LMNRx LMNRx_n, LMNRx_n_l

Bits in the words X X LMNRx.b LSPR 16 bit WORDX X LSPRx LSPRx_n, LSPRx_n_l

Bits in the words X X LSPRx.b LERRR 16 bit WORD X LERRRx LERRRx_n, LERRRx_n_l

Bits in the words X LERRRx.b LHHAR 16 bit WORD X X LHHARx LHHARx_n, LHHARx_n_l

Bits in the words X X LHHARx.b LLLAR 16 bit WORD X X LLLAx LLLAx_n, LLLAx_n_l

Bits in the words X X LLLARx.b LADBR 16 bit WORD X X LADBRx LADBRx_n, LADBRx_n_l

Bits in the words X X LADBRx.b LMXR 16 bit WORD X X LMXRx LMXRx_n, LMXRx_n_l

Bits in the words X X LMXRx.b LSPLR 16 bit WORD X X LSPLRx LSPLRx_n, LSPLRx_n_l

Bits in the words X X LSPLRx.b LSPHR 16 bit WORD X X LSPHRx LSPHRx_n, LSPHRx_n_l

Bits in the words X X LSPHRx.b LCFH 16 bit WORD X X LCFHx LCFHx_n, LCFHx_n_l

Bits in the words X X LCFHx.b LCFL 16 bit WORD X X LCFLx LCFLx_n, LCFLx_n_l

Bits in the words X X LCFLx.b LKD 32 bit IEEE REAL X X LKDx LKDx_n, LKDx_n_l

LRSN 16 bit WORD X X LRSNx LRSNx_n, LRSNx_n_l Bits in the words X X LRSNx.b

LACK 16 bit WORD X X LACKx LACKx_n, LACKx_n_l Bits in the words X X LACKx.b

x : Number of the first "LOOP" (1 to 64). n : Number of words. l : Number of words per line (Matrix mode only). b : Rank of the bit in the word (0 to 15).


WoodheadWoodhead


Remarks : The limiting values of the parameters n and l depend on the protocol. However, for PCDDE, they cannot be greater than 128 for bits bytes, 64 for words, 32 for double words and floating words.



WoodheadWoodhead


- ALARM variables You must use this syntax with cautions, see the "Bit of word" section of the "DDE and OPC server"

manual. For this syntax, the maximum numbers of variables per frame are: in read: 128*16 in write: 1

"Array mode (String and Matrix) provides access to the same contiguous ALARM variable. Examples : Item representing a string of data corresponding to the AHA variable of 4 ALARM from ALARM

10. AHA10_4

This corresponds to access to variables AHA10, AHA11, AHA12, AHA13. Item representing a string of data corresponding to the variables AHA of 4 ALARM from ALARM

10 with 2 variables per line. AHA10_4_2

This corresponds to access to variables AHA10, AHA11, AHA12, AHA13. The following array representes the "ALARM" variables with their formats and their various

syntaxes. « X » in column « L » represents the possibility of read and « X » in column « E » the possibility of write.

Variable name Variable type L E Unitary mode Table Mode, Matrix Mode

AHA 32 bit IEEE REAL X X AHAx AHAx_n, AHAx_n_l ALA 32 bit IEEE REAL X X ALAx ALAx_n, ALAx_n_l APV 32 bit IEEE REAL X X APVx APVx_n, APVx_n_l APVH 32 bit IEEE REAL X X APVHx APVHx_n, APVHx_n_l APVL 32 bit IEEE REAL X X APVLx APVLx_n, APVLx_n_l AODA 32 bit IEEE REAL X X AODAx AODAx_n, AODAx_n_l AYDA 32 bit IEEE REAL X X AYDAx AYDAx_n, AYDAx_n_l ATS 32 bit IEEE REAL X X ATSx ATSx_n, ATSx_n_l ASP 32 bit IEEE REAL X X ASPx ASPx_n, ASPx_n_l AVF 16 bit WORD X X AVFx AVFx_n, AVFx_n_l Bits in the words X X AVFx.b ACF 32 bit IEEE REAL X X ACFx ACFx_n, ACFx_n_l AERR 32 bit IEEE REAL X AERRx AERRx_n, AERRx_n_l AHHA 32 bit IEEE REAL X X AHHAx AHHAx_n, AHHAx_n_l ALLA 32 bit IEEE REAL X X ALLAx ALLAx_n, ALLAx_n_l ARCA 32 bit IEEE REAL X X ARCAx ARCAx_n, ARCAx_n_l ASPH 32 bit IEEE REAL X X ASPHx ASPHx_n, ASPHx_n_l ASPL 32 bit IEEE REAL X X ASPLx ASPLx_n, ASPLx_n_l AADB 32 bit IEEE REAL X X AADBx AADBx_n, AADBx_n_l AHAR 16 bit WORD X X AHARx AHARx_n, AHARx_n_l Bits in the words X X AHARx.b ALAR 16 bit WORD X X ALARx ALARx_n, ALARx_n_l Bits in the words X X ALARx.b APVR 16 bit WORD X X APVRx APVRx_n, APVRx_n_l Bits in the words X X APVRx.b


WoodheadWoodhead


AODAR 16 bit WORD X X AODARx AODARx_n, AODARx_n_l Bits in the words X X APVRx.b AYDAR 16 bit WORD X X AYDARx AYDARx_n, AYDARx_n_l Bits in the words X X AYDARx.b ASPR 16 bit WORD X X ASPRx ASPRx_n, ASPRx_n_l Bits in the words X X ASPRx.b AADBR 16 bit WORD X X AADBRx AADBRx_n, AADBRx_n_l Bits in the words X X AADBRx.b AERRR 16 bit WORD X AERRRx AERRRx_n, AERRRx_n_l Bits in the words X AERRRx.b AHHAR 16 bit WORD X X AHHARx AHHARx_n, AHHARx_n_l Bits in the words X X AHHARx.b ALLAR 16 bit WORD X X ALLAx ALLAx_n, ALLAx_n_l Bits in the words X X ALLARx.b ASPAR 16 bit WORD X X ASPARx ASPARx_n, ASPARx_n_l Bits in the words X X ASPARx.b ASPHR 16 bit WORD X X ASPHRx ASPHRx_n, ASPHRx_n_l Bits in the words X X ASPARx.b ACFH 16 bit WORD X X ACFHx ACFHx_n, ACFHx_n_l Bits in the words X X ACFHx.b ACFL 16 bit WORD X X ACFLx ACFLx_n, ACFLx_n_l Bits in the words X X ACFLx.b AACK 16 bit WORD X X AACKx AACKx_n, AACKx_n_l Bits in the words X X AACKx.b

x : Number of the first "ALARM" (1 to 128). n : Number of words. l : Number of words per line (Matrix mode only). b : Rank of the bit in the word (0 to 15). Remarks :




WoodheadWoodhead

Industrial Ethernet on PCI2000ETH (TCP/IP and ISO layer 4) and SW1000ETH (TCP/IP) • 170 • - Appendices

7. - Appendices

- Evolution / compatibility The protocols embedded in the PCI2000ETH board require version 3.7 EPROMs or better. Compatibility : The client equipment for monitoring (server mode functionality) must be defined in the

configurator (the equipment number in the TSAP chain is no longer required).

Upgrades : Simultaneous multi-requests on a S7-300, S7-400 equipment. Maximum number of total simultaneous requests increased from 8 to 30. Write bits on S7-300, S7-400 :

S7-300 : increase from 1 to 8 bits, S7-400 : increase from 1 to 1614 bits,

From version applicom® V3.3 :

Management of SIMATIC TI 505 PLCs on ISO layer 4. From version applicom® V3.7 :

Management of SIMATIC S7-200 PLCs on TCP/IP.


WoodheadWoodhead


- Return status of applicom® functions The various applicom® functions return a status word that: - Guarantees the request quality. - Can be used to diagnose the cause of a failure. The significance of the status word value is given in the table below. As well as the general

significance, « Further details » allow you to guide your diagnostic according to the protocol used.

- applicom® general status

-6 The TRANSCYC (or TRANSCYCPACK) function is used with a cyclic function number that is no longer activated.

-5 The user program tries to perform a TRANSDIF (or TRANSDIFPACK) deferred transfer although the deferred request in progress is not completed.

-1 TRANSDIF (or TRANSDIFPACK) deferred transfer request related to a write that took place correctly. 0 No anomaly detected. The function took place correctly. 1 Unknown function.

The requested function is not supported. 2 Incorrect address.

The address of the variable you are soliciting is incorrect. 3 Incorrect data.

Further details : Function: BINBCD, BCDBIN. - At least one of the accessed values is not in BCD format (0 ≤ value ≤ 9999).

4 Irretrievable data. 32 Bad parameter passed into the function.

Incorrect number of variables. 35 Data not available in cyclic read.

Attempt to transfer data with TRANSCYC (or TRANSCYCPACK) before it has been read in the equipment. 40 Deferred read or write attempt when the deferred request register is full.

Another task must free the resources by making an exitbus. 41 Deferred read or write attempt when the deferred request register is full

Perform deferred request transfers with TRANSDIF (or TRANSDIFPACK) in order to release the register (64 positions).

42 Deferred request transfer attempt with TRANSDIF (or TRANSDIFPACK) when the latter is empty (no deferred requests in progress).

45 Non-resident communication software. Initialize the applicom® interface before using it by typing command applicom (or PCINIT under Windows ).

46 Board number not configured, or Master/client applicom® function aiming at a channel configured as slave/server, or vice versa.

47 No applicom® interface. 51 Driver system problem. 59 Protection key missing on the applicom® interface..

Using applicom® function without INITBUS function. 66 Insufficient applicom® interface memory. 97 Operating mode not supported by the SW1000ETH solution. 255 Used by the « PCDDE » MS-Windows server. Initial value of « STATUS_READ » and « STATUS_WRITE ».

This value indicates that no transaction has been made between « PCDDE » and applicom® interface. Comments : Negative status codes are information codes.


WoodheadWoodhead


- Status according to the protocol

0 No anomaly detected. The function took place correctly. 2 Incorrect address.

The address of the variable you are soliciting is incorrect. Further details : Industrial Ethernet protocol: - Returned by the destination coupler equipment. Undeclared DB or DB address out of delimiters.

3 Incorrect data. Further details : Industrial Ethernet protocol: - Inconsistent frame content. The number of returned bytes is not equal to waiting quantity. Function: BINBCD, BCDBIN, READWORDBCD, WRITEWORDBCD. - At least one of the accessed values is not in BCD format (0 ≤ value ≤ 9999).

4 Inaccessible data. Further details : Industrial Ethernet Protocol: - The physical address does not exist « QVZ error»(for example: input or output card not present in the PLC).

33 Response time fault (Time-Out for request being processed). Further details : Industrial Ethernet HTB Protocol: - Equipment configured but never connected. Wiring problem, CPU in stop, the CPU does not run the communication FB, connection not declared or wrongly declared in the CPU (see chapter: « Configuring Siemens equipment ») , PLC not present, bad equipment or gateway IP address.

36 Equipment not configured. Define the equipment configuration with CONFAPLI (or console for MS-Windows) and start again the applicom® product.

49 Queue time-out fault The request could not be sent due to lack of resources (no communication channels available). This time corresponds to 4 times the value of the time-out for the requests being processed. Increase the value of the « time-out for requests being processed » Increase the maximum number of simultaneous requests on the targeted equipment.

55 Time-Out elapsed, Message Lost Further details : Industrial Ethernet Protocol: - Waiting time exceeding « time-out for request being processed » value good connection, the question was acked but no response. - Destination station was deconnected during exchange.

66 Insufficient applicom® interface memory. Further details : Industrial Ethernet Protocol: - Insufficient resource for extra communication.

70 Communication terminated by remote equipment Further details : Industrial Ethernet Protocol: - Communication aborted due to communication problem. Wiring problem, CPU in stop, the CPU does not run the communication FB, connection not declared or wrongly declared in the CPU (see chapter: « Configuring Siemens equipment »), bad equipment or gateway IP address, distant station is downed..


WoodheadWoodhead


- TCP/IP appendix

- IP address Each interface on a TCP/IP network or sub-network must have a unique IP address. Determination of this address depends on the network type :

open type network (e.g. : Connected to the worldwide Internet), the address or set of addresses must be issued by an authorized organization in the country where the network is installed, closed type network (network internal to the company), the addresses are issued by the

network administrator.

An IP address is represented on 4 bytes (or 32 bits). It is composed of : a network identifier, a machine identifier.

0 Using these two identifiers, the IP addresses can be divided into 5 different classes:

Class A : 128 networks and 16777216 stations

0 network id 7 bits station id 24 bits

Class B : 16384 networks and 65536 stations

1 0 network id 14 bits station id 16 bits

Class C : 2097152 networks and 256 stations

1 1 0 network id 21 bits station id 8 bits

Class D :

1 1 1 0 multicast group id 28 bits

Class E :

1 1 1 1 0 reserved for future use 27 bits Which gives us in pointed decimal notation :

Class RangeA 0.0.0.0 to 127.255.255.255B 128.0.0.0 to 191.255.255.255C 192.0.0.0 to 223.255.255.255D 224.0.0.0 to 239.255.255.255E 240.0.0.0 to 255.255.255.255

The choice of an internal address will therefore depend on the number of stations on this network; a

class C address is generally sufficient. Special case : « loopback » destination address 127.0.0.1, this address can be used to test the

TCP/IP layer. A packet with destination address 127.0.0.1 will not leave on the network, the packet drops down to the IP layer then goes straight back to TCP.


WoodheadWoodhead


- Sub-network mask Class A and B addresses include a large number of machines which are represented respectively

on 24 and 16 bits. It is therefore recommended to divide the machine identifier into sub-network identifier and machine identifier.

For example, for a class B address :

1 0 network id 14 bits sub-network id 8 bits station id 8 bits This breakdown authorizes 254 sub-networks, with 254 machines per sub-network. The sub-network mask can be used to specify the bits forming the sub-network mask. This mask is a 32 bit word containing bits set to 1 for the network and sub-network identifiers, and bits set to 0 for the machine identifier. Example for a sub-network mask with class B address :

network id sub-network id machine id16 bits 8 bits 8 bits

11111111 11111111 11111111 00000000 I.e. a sub-network mask of 255.255.255.0 Using its IP address and the sub-network mask, a machine can determine whether a packet is

intended for : - a machine on its own sub-network, - a machine on another sub-network (use of the gateway IP address), - a machine on a different network (use of the gateway IP address).

Example : The applicom® board at IP address 140.152.3.25 with a sub-network mask of 255.255.255.0. The address is therefore class B with a network ID of 140.152, a sub-network id of 3, and a

machine id of 25. The following equipments must be polled : - Equipment 1 with address 140.152.7.10 : identical network id (140.152), different

sub-network id (7) => use of the gateway. - Equipment 2 with address 140.152.3.20 : identical network id (140.152), identical

sub-network id (3), different machine id (20) => sent directly to the equipment. - Equipment 3 with address 194.204.26.43 : different network id (class C) => use of

the gateway.


WoodheadWoodhead


- Gateway The TCP/IP IP layer (layer 3) can be used to change network or sub-network via a dedicated

machine called a gateway or router. This machine must have at least two links on two different networks. When the destination address is on a different network, IP therefore uses the gateway IP address

to send the packet. This gateway handles this packet completely and returns it on the destination network. Example, transfer to an internal sub-network :

�� !�*��

��%%% �4

��

��

��

��

+��,

�� !�*��

��-�.�-�

��-�.�-�

��-�.�-�-�

��-�.�-�-��

��-�.�-�-�.

��-�.�-�-��

��-�.�-�-�

��/��-�.�-�-�.+��,�/��-�.�-�-��!�*��*�/��..-�..-�..-�

��/��-�.�-�-��+��,�/��-�.�-�-��!�*��*�/��..-�..-�..-�

��

Figure 53 : IP gateway

The request intended for equipment 2 with address 140.152.7.10, is sent to the gateway 140.152.3.1 (transfer from network 140.152.3 to 140.152.7). The gateway returns the request to equipment 2 (S7-300), which answers using gateway 140.152.7.1.


WoodheadWoodhead


- Time-out TCP The TCP/IP protocol supplies a reliable transport layer, i.e. it manages the time-out and retry

procedures for packet acknowledgment. The maximum number of retries is 12, and the time-out between each retry is variable. Initially, this

time is calculated using an estimation of the « round-trip time » of a packet on the connection then increases with the number of attempts exponentially up to a limit of 64 seconds, which generally produces :

� 0 ��

�� 1 0� 0�

�-.�-. ��-. ��-.

�0-. 2�-. �.1-. ��-. .��-.

� � � �

. 0 � 1 ��

�!��(

'��,��3

4��#!��5

��#!��

�

�0� 0� 0� 0� 0�

�10-. �.�-. ��-. ��1-.

Figure 54 : TCP time-out

We soon see that the wait time to know that a packet has not been acknowledged can be very long : 542.5 seconds, i.e. over 9 minutes. The applicom® interface allows you to configure :

The number of retries, The maximum interval between two retries.

To simplify the time-out calculation, it is easier to set the maximum interval between two retries to 1

second and then adjust the number of retries, by default the applicom® interface uses 2 retries, which gives you a time-out of about 3 seconds.

On very disturbed or very saturated networks (load greater than 30 %), it is recommended to set 4 retries.

- Connection servicing The TCP connections can be serviced with the « connection servicing » function in the « Advanced

parameters » (usually called « keep alive »). This servicing is used to keep the connection alive even if there is no data circulating. Also, if the partner equipment no longer responds to this servicing, the connection is automatically deleted.

The applicom® interface can be used to validate or not this operating mode. The operating mode

characteristics (which cannot be modified) are : Servicing frequency : 30 seconds Retry frequency : 20 seconds number of tries if no response : 8


WoodheadWoodhead


- Extended TCP/IP status Extended status for TCP/IP allows to improve the status linked to the protocol ; it can be reached by

using the utility « TCP-IP & ISO diagnostics » and validating the « Advanced mode ».

1035 Ressource temporarily unavailable1036 Operation now in progress1037 Operation already in progress1038 Socket default1039 Destination address required1040 Message too long1041 Protocol wrong type for socket1042 Protocol not available1043 Protocol not supported1044 Socket type not supported1045 Operation not supported1046 Protocol family not supported1047 Address family not supported by protocol family1048 Address already in use1049 Impossible address1050 No network1051 Network is unreachable1052 Network dropped connection on reset1053 Software caused connection abort1054 Connection reset by peer1055 No buffer space available1056 Socket is already connected1057 Socket is not connected1058 Can't send after socket shutdown1061 Connection refused1064 Host is down1065 Host is unreachable


WoodheadWoodhead

Industrial Ethernet on PCI2000ETH (TCP/IP and ISO layer 4) and SW1000ETH (TCP/IP) • 178 • - Glossary

8. - Glossary

applicom® interface Communication board of type ISA or PCI, equipped with the applicom® real time multi-task kernel

(PC1000, PC2000, PC4000, PC1500PFB, etc.)

ARP Address Resolution Protocol

ASCII American Standard Code for Information Interchange

AUI Attachment Unit Interface : interface entre coupleur et transceiver

Channel Physical output of an applicom® board

Client Equipment which takes the communication initiative

Coupler Communication interface

CP Communication Processor : module handling communication tasks

CSMA/CD Carrier Sense Multiple Access with Collision Detect

DATABASE applicom® database of 32 kbits and 32 kwords

DB Siemens terminology to designate a Data Block

EPROM Electronic component installed on the applicom® interface where non-erasable computer

programs are stored

ICMP Internet Control Message Protocol : control message protocol using IP

IP Internet Protocol : inter-network protocol

ISO International Standards Organization

Item Defines a unit article or element

ITP Industrial Twisted Pair : double industrial twisted pair developed by Siemens


WoodheadWoodhead

Industrial Ethernet on PCI2000ETH (TCP/IP and ISO layer 4) and SW1000ETH (TCP/IP) • 179 • - Glossary

LLC

Logical Link Control

Memory Siemens terminology to designate the internal memory of the PLC

OPC Ole for Process Control

OSI Open Systems Interconnection

PCDDE applicom® DDE server

RFC Request For Comment : set of specifications describing amongst other things all TCP/IP protocols

TCP

Transmission Control Protocol


WoodheadWoodhead

Industrial Ethernet on PCI2000ETH (TCP/IP and ISO layer 4) and SW1000ETH (TCP/IP) • 180 • - Index

9. - Index

accessible variables, 76 Addressing, 21, 76, 131 Alignments, 76 Client

Performance S5, 24 Performance S7, 82 Performance TI, 135 S5, 21 TI, 131

Client equipment configuration S7, 92, 142

Client mode, 10 Configuration

S5, 28 S7, 88 TI, 138

Coupler CP143, 32 CP1430, 32

CP143, 32 CP1430, 32 DATA-BASE

S5, 26 S7, 86 TI, 137

EPROM S7, 173

Equipment properties, 18

Equipments Siemens Implementation TI, 144, 149

Error S7, 174

Ethernet, 12 Evolution

S7, 173 FETCH, 32 Functionality, 5, 21, 76, 131 Functions return

S7, 174 Industrial Ethernet client

S7, 76 IP

address, 176 gateway, 178 sub-network mask, 177

IP addressing, 176 IP gateway, 178 IP Sub-network mask, 177 Item descriptor S5

Simatic S5 D FR descriptor, 59 Simatic S5 GB descriptor, 67


WoodheadWoodhead


Standard descriptor, 54 Item descriptor S7

Siemens S7 descriptor, 124 Standard descriptor, 119

Item descriptor TI Standard descriptor, 157 Texas Instrument descriptor, 161

Items S5 Simatic S5 D FR descriptor, 59 Simatic S5 GB descriptor, 67 Standard descriptor, 54

Items S7 Siemens S7 descriptor, 124 Standard descriptor, 119

Items TI Standard descriptor, 157 Texas Instrument descriptor, 161

Limits S5 Library, 23 OPC server, 23 PCDDE, 23

Limits S7 Library, 80 OPC server, 81 PCDDE, 80

Limits TI Library, 134 OPC server, 134 PCDDE, 134

Maximum number of variables per exchange S5 Library, 23 OPC server, 23 PCDDE, 23

Maximum number of variables per exchange S7 Library, 80 OPC server, 81 PCDDE, 80

Maximum number of variables per exchange TI Library, 134 OPC server, 134 PCDDE, 134

Multi-request, 7 Network parameter, 18 OSI, 3 Performance

S5, 24 S7, 82 TI, 135

READ/WRITE S5, 32

RECEIVE, 32 Requests, 8, 10 S5

Client, 21 Configuration, 28 DATA-BASE, 26 Functionality, 21 Performance, 24 Server, 26

S7


WoodheadWoodhead


Client equipment configuration, 92, 142 Configuration, 88 DATA-BASE, 86 Functionality, 76 Industrial Ethernet client, 76 Performance, 82 Server, 86 Server equipment configuration, 88

SEND, 32 Server

S5, 26 S7, 86 TI, 137

Server equipment configuration S7, 88 TI, 138, 140

Server mode, 14 Siemens equipments

S7 implementation, 94 Status

S7, 174 Supported variables, 21, 131 SYNCHRON, 32 TCP

servicing, 179 time-out, 179

TCP servicing, 179 TCP/IP, 16 TI

Client, 131 Configuration, 138 DATA-BASE, 137 Functionality, 131 Performance, 135 Server, 137 Server equipment configuration, 138, 140

Time-out TCP, 179 Usable functions S5

Cyclic mode, 52 Deferred mode, 51 Wait mode, 51

Usable functions S7 Cyclic mode, 118 Deferred mode, 117 Wait mode, 117

Usable functions TI Cyclic mode, 156 Deferred mode, 155 Wait mode, 155

industrial ethernet on pci2000eth (tcp/ip and iso layer 4

Documents