Industrial Ethernet On PC2000ETH (ISO Layer 4) : Woodhead Woodhead

electrical & safety · industrial connectivty · software & electronics · advanced connectivity
Woodhead
Protocol manual
Industrial Ethernet on
PC2000ETH (ISO Layer 4)
applicom® 3.8
a product of Woodhead Software & Electronics
H1.doc 06/05/2004
Copyright © 2004 Woodhead Software & Electronics. All rights reserved.

http://www.applicom-int.com
Woodhead
H1.doc 06/05/2004
® TM TM TM
Copyright © 2004 Woodhead Software & Electronics. All rights reserved. applicom , Direct-Link , RJ-Lnxx , SST are registered
trademarks of Woodhead Software & Electronics. Other product names are trademarks of their respective owners.
http://www.applicom-int.com
Woodhead
Table of contents
1. - Generalities ..................................................................................1
2. - Simatic® S5 (READ/WRITE S5 and TF Messaging) ...................3

- Functionality ..........................................................................................................4
- Configuration.......................................................................................................10
Server equipment configuration ............................................................................13
- Siemens equipments implementation .................................................................15
- applicom® functions usable on the master channel ...........................................39
- Item of image variables .......................................................................................41
- Appendices .........................................................................................................63
- Return status of applicom® functions .................................................................64
3. - Simatic® TI505 Texas (READ/WRITE S5 Messaging) ..............66

- Functionality ........................................................................................................67
- Configuration.......................................................................................................74
- Item of image variables - Presentation ...............................................................86
- Item of image variables - Standard descriptor ....................................................86
- Item of image variables - Texas Instrument descriptor.......................................91
- Appendices .......................................................................................................103
- Return status of applicom® functions ...............................................................104
4. - Simatic® S7 (S7 Protocol) ....................................................... 106

-Functionality .......................................................................................................107
- Configuration.....................................................................................................116
Server equipment configuration ..........................................................................118
- Siemens S7 equipments implementation..........................................................120
- applicom® functions usable on the master channel .........................................128
- Item of image variables .....................................................................................130
- Appendices .......................................................................................................140
5. - Glossary of terms .................................................................... 143
6. - Index ......................................................................................... 144
Industrial Ethernet on PC2000ETH (ISO Layer 4) •i• Table of contents

Woodhead
1. - Generalities
" Industrial Ethernet " is the new name of the SIEMENS communication system, in the past called
SINEC H1. This open communication system can operate in a homogeneous environment (Siemens
CP143, CP1430, CP443-1, CP343-1 et CP1434 couplers amongst others) or heterogeneous environment
(Siemens couplers with other manufacturers). It is located both at the cell supervisor level (level 3) and
inter-PLC communication network (level 2).
applicom® Industrial Ethernet functionality against OSI model
CUSTOMER
APPLICATION
applicom®
Layer 7 TI
Application READ/WRITE S5 mess. TF Protocol S7
Peer to Peer
Layer 6
Presentation
Layer 5
Session
Layer 4
Transport ISO 8073 CLASS 4
Layer 3 Empty
Network
Absolute NSAP
Layer 2
Link IEEE 802.2 (CSMA/CD)
Layer 1
Physical IEEE 802.3
Layers 1 and 2 (2a), the physical and datalink layers, operate according to the CSMA/CD
procedure according to IEEE 802.3. The layer 2b (LL6) corresponds to IEEE 802.2.
Layer 3 (network layer) is not implemented in the case of Industrial Ethernet. Siemens only uses
"empty protocols" here.
Layer 4 (transport layer) is implemented according to specifications:
• ISO 8073
• ISO ADDUM 8073
It includes:
• virtual connections in CLASS 4
• express data
• datagram service
Industrial Ethernet on PC2000ETH (ISO Layer 4) •1• - Generalities

Woodhead
Layers 5 and 6 are not used.
Functionality Industrial Ethernet supported by applicom®:
• S5 READ/WRITE messaging (Client, Server).

• TF messaging (Client)
• S7 protocol (Client, Server)
The Industrial Ethernet solution on applicom® can be used to access functions supported by this
industrial network using the READ/WRITE, TF or S7 Protocol mode. It can be used to access variables of
Step5 or Step7 (inputs, outputs, DB ....). The Industrial Ethernet solution on applicom® can be used to
manage client and server accesses with PLCs in the Siemens Simatic® S5 and Simatic® TI505 or
Simatic® S7 range, supporting the CP 143, CP1430, CP1434, CP343-1 or CP443-1 communication
couplers.
READ/WRITE or TF functionalities need no special programming in PLCs, the user handles
standards Siemens communication blocks, types SEND, RECEIVE, FETCH and RECEIVE-ALL to
activate the various contracts between the PLC CPU and the communication coupler. With S7 Protocol,
communication runs with standard CFB blocks.
Layer 7 (application layer) allows S5 contracts to be used (Simatic® S5 and Simatic® TI505 range),
via the S5 READ/WRITE(HTB) messaging or S7 Protocol (with Simatic® S7 range). The CP 143,
CP1430 or CP 1434 generates S5 specific labels for request and acknowledge telegrams and CP343-1 or
CP443-1 for S7 Protocol.
The applicom® concept version 3.0 can be used to exchange a number of data depending on the
type of interface and the type of operation.
In the case of a use of the PC2000ETH interface with an application supporting the buffer of 256
bytes, the exchanges will be of 256 bytes maximum, even less in certain cases (ex: TF messaging).
Refer to the manual of the messaging used to have the limits of exchange according to the type of
data.
Industrial Ethernet on PC2000ETH (ISO Layer 4) •2• - Generalities

Woodhead
2. - Simatic® S5 (READ/WRITE S5 and TF

Messaging)
Contents
- Functionality ..........................................................................................................4
- Industrial Ethernet client..........................................................................4
- Industrial Ethernet server ........................................................................8
- Configuration.......................................................................................................10
- PLC under Industrial Ethernet protocol READ/WRITE ................................. 15
- PLC under Industrial Ethernet TF............................................................. 31
- Wait mode ........................................................................................... 39
- Deferred mode...................................................................................... 39
- Cyclic mode.......................................................................................... 40
- Item of image variables .......................................................................................41
- Presentation ......................................................................................... 41
- Standard descriptor ............................................................................... 42
- Siemens Simatic S5 PLCs descriptor - German (D) and French syntax ......... 47
- Siemens Simatic S5 PLCs descriptor - English syntax................................. 55
- Appendices .........................................................................................................63
- List of extra files for this protocol ............................................................ 63
- Evolution / compatibility ........................................................................ 63
- Return status of applicom® functions .................................................................64
- applicom® general statuses ................................................................... 64
- Statuses according to the protocol........................................................... 65
Industrial Ethernet on PC2000ETH (ISO Layer 4) •3• - Simatic® S5 (READ/WRITE S5 and TF Messaging)
Woodhead
- Functionality
- Industrial Ethernet client
The Client Industrial Ethernet on applicom® interface can be used to poll Siemens architecture
® ® ®
network Simatic S5, Simatic S7 and Simatic TI505 PLCs using standard functions (wait, deferred,
cyclic modes) of the applicom® product. Multiflow communication is used (several transactions
simultaneously, maximum 8).
- Simatic® S5 range
Functions managed by choosing a Industrial Ethernet HTB channel (READ/WRITE) 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.
This addressing allows to reach DB of 256, 2048 and 4096 words in a transparent way. The
addressing of the preceding versions gave access only to DB of 256 words but remains compatible with
this version.
The item descriptor usable with PCDDE associated with this addressing is " SIMATIC S5 (Industrial
Ethernet) ".
The old descriptor remains compatible but gives access only to DB of 256 words.
Siemens applicom® Type of exchange Corresponding applicom®

PLC Addressing (addr) (cyclic mode) function (library/DLL access)
Variable
M v.w v*8+w Read bits READPACKBIT, READDIFBIT
DB x D y.z x*65536+y*16+z+134217728 Write bits WRITEPACKBIT, WRITEDIFPACKBIT
DX x D y.z idem + 16777216
MB v v Read bytes READBYTE

Write bytes WRITEBYTE
MB v v Read packed bytes READPACKBYTE, READDIFBYTE

Write packed bytes WRITEPACKBYTE, WRITEDIFPACKBYTE
MW v v Read words READWORD, READDIFWORD

DB x DW y x*4096+y+134217728 Write words WRITEWORD, WRITEDIFWORD
DX x DW y idem + 1048576
MW v v Read BCD words READWORDBCD

DB x DW y x*4096+y+134217728 Write BCD words WRITEWORDBCD
DX x DW y idem + 1048576
MD v v Read double words READDWORD, READDIFDWORD

DB x DD y x*4096+y+134217728 Write double words WRITEDWORD, WRITEDIFDWORD
DX x DD y idem + 1048576
Woodhead
MD v KG v Read floating words READFWORD, READDIFFWORD
DBxDDyK x*4096+y+134217728 Write floating words WRITEFWORD, WRITEDIFFWORD
G idem + 1048576
DXxDDyKG
E v.w v*8+w Read input bits READPACKIBIT, READDIFIBIT
EB v v Read input bytes READIBYTE
EB v v Read packed input bytes READPACKIBYTE, READDIFIBYTE
EW v v Read input words READIWORD, READDIFIWORD
A v.w v*8+w Read output bits READPACKQBIT, READDIFQBIT

Write output bits WRITEPACKQBIT, WRITEDIFPACKQBIT
AB v v Read output bytes READQBYTE, READDIFQBYTE

Write output bytes WRITEQBYTE
AB v v Read packed output bytes READPACKQBYTE, READDIFQBYTE

Write packed output WRITEPACKQBYTE, WRITEDIFPACKQBYTE
AW v v Read output words READQWORD, READDIFQWORD

Write output words WRITEQWORD, WRITEDIFQWORD
TB n n Read timers READTIMER
Write timers WRITETIMER
ZB 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 255)
Woodhead
- Maximum number of variables per exchange with the library
The maximum number of variables depends on the type of interface and the type of buffer used.
HTB messaging (READ/WRITE)
Object Maximum quantity in read / write

Bit 2048
Byte * 256
Word 128
Double word 64
Timer/counter 128
TF messaging

Bit 1824
Byte * 228
Word 114
Double word 57
Timer/counter 114
*: It is imperative to write an even number of bytes, otherwise the Most Significant Byte of the last
word is corrupted.
- Maximum number of variables per exchange with PCDDE

Bit 2048
Byte 256
Word 128
Double word 64
Timer/counter 128
TF messaging

Bit 1824
Byte 228
Word 114
Double word 57
Timer/counter 114
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.
Woodhead
- Maximum number of variables per exchange with OPC server

Bit 2048
Byte 256
Word 128
Double word 64
Timer/counter 128
TF messaging

Bit 1824
Byte 228
Word 114
Double word 57
Timer/counter 114
options").
For the write frames, see chapter "OPC Server/Optimization of synchronous and asynchronous
requests".
Woodhead
- 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 requests Type of data in Addresses in Corresponding

DATA-BASE DATA-BASE S5 Addresses
Read inputs(EB) byte area 0 - 127 EB0 to EB127
Read outputs (AB) byte area 128 - 255 AB0 to AB127
Read memos (MB) byte area 256 - 511 MB0 to MB255
Read data blocks (DB) word area 256 - 31999 DB1DW0 to DB124DW255
Write outputs (AB) byte area 128 - 255 AB0 to AB127
Write memos (MB) byte area 256 - 511 MB0 to MB255
Write data blocks (DB) word area 256 - 31999 DB1DW0 to 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 memo bytes
128 DB words
The Industrial Ethernet Server functionality on the applicom® database can be used to optimize
data feedback. Rather than permanently polling devices to monitor variables changing status
occasionally, the devices 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.
Woodhead
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 maximum time interval between client equipment accesses to the applicom®
Industrial Ethernet Server, in the name of the client Local TSAP. This name is defined in the
client PLC configuration. The Industrial Ethernet Server task on applicom® interface can
manage up to 60 connections with client stations. As seen by applicom®, a connection with a
client station is marked by a number from 0 to 59. For a given connection, a client station can
initialize the access time-out value. This initialization is made by the client PLC local TSAP name
during the connection sequence. The name of the local TSAP must be type: APnn-vvv where
AP is the applicom® identifier, nn represents a connection number seen by applicom® (from
00 to 59) and vvv represents the access time-out to the applicom® DATA-BASE (from 001-
999 seconds).
Example: for connection 1 with a time-out value of 10 seconds, a local TSAP = AP01-010.
After this interval, absence is signaled to the application by an « ACCESS STATUS WORD » in the
applicom® database. Define the address of this status word using the channel configuration
utility.
• The application is informed of the write access by each device to the applicom® Industrial
Ethernet Server by incrementing an « ACCESS INDICATOR WORD » in the applicom®
database. The application can query the variables of this device 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 device of this acknowledgment).
After this period, absence is signaled to the application by an « ACCESS STATUS WORD » in the
applicom® database. Use the channel configuration utility to define the address of this status
word.
Woodhead
- Configuration
This protocol is only configurable on applicom® interfaces with an Ethernet way (PC2000ETH or
PCI2000ETH).
Local read TSAP of server

This choice is used to define the name of the TSAP (Transport Service Access Point). It is used to
allow client equipment read access to the DATA-BASE server.
This TSAP must also be defined in the client PLC coupler configuration.
PLC coupler (CP 143) configuration:
Contract Active FETCH.
Ethernet Address Identical to that defined in the field « Card Ethernet
address ».
ID LOCAL TSAP See fields « Status words» and « Indicator words ».
ID REMOTE TSAP Identical to this field (READREAD by default).
Local write TSAP of server

allow client equipment write access to the DATA-BASE server.
PLC coupler (CP 143) configuration:
Contract passive SEND
Ethernet Address Identical to that defined in the field « Card Ethernet
address ».
ID LOCAL TSAP See fields « Status words» and « Indicator words ».
ID REMOTE TSAP Identical to this field (WRITWRIT by default).
Industrial Ethernet on PC2000ETH (ISO Layer 4) • 10 • - Simatic® S5 (READ/WRITE S5 and TF Messaging)

Woodhead
Ethernet address of the card
If you enter « ############ » as Ethernet address, the default applicom® interface Internet
address will be used.
The default Ethernet address is made up of 6 bytes including the applicom® IEEE address
followed by the applicom® interface serial number. The serial number is given on the applicom®
interface labels (on the rear plate and on the copper) or displayed when the interface is initialized (
« applicom » or « pcinit » command under MS-Windows).
applicom® Interface
IEEE serial number
Address (in Hexadecimal)
00 A0 91 xx xx xx
Example:
applicom® interface Ethernet address with serial number 20100 i.e. 4E84 Hexadecimal.
00 A0 91 00 4E 84
If you enter an address, then this address will be used. This means that an Ethernet card can be
replaced without having to reconfigure its peer's address in the client station.
Address « Access status words » in DATA-BASE

Start storage address of the 60 « Access status words » in DATA-BASE. If this management is not
used set value -1.
Otherwise the address can range from 0 to 31 999.
This option is used to monitor the access interval of the applicom® Industrial Ethernet server client
equipment. If the « Access Time-Out » configured in the name of the client equipment local TSAP is
exceeded, the applicom® interface will indicate this absence in the corresponding word at the
offset defined in the client equipment local TSAP.
Client PLC coupler configuration in the field:

« ID LOCAL TSAP » in the form Apnn-vvv example AP00-010
or AP obligatory for applicom®
nn offset in the status word table (00 to 59)
- obligatory separator
vvv time-out value from 000 to 999 seconds
1st access status word AP00-vvv

2nd access status word AP01-vvv
. .
60th access status word AP59-vvv

Woodhead
Address « Access indicator words » in DATA-BASE
Start storage address of the 60 « Access indicator words » in DATA-BASE. If this management is
not used set value -1. Otherwise the address can range from 0 to 31 999. In this case, all write
access by client equipment to the applicom® server will be signaled by the increment of the
corresponding word at the offset defined in the client equipment local TSAP.

« ID LOCAL TSAP » in the form APnn-vvv example AP00-010

. .
Resetting this word to 0 is your responsibility to be informed of the next write and/or inform the
transmitting equipment of this acknowledgment.

Woodhead
Server equipment configuration

Up to 60 peers numbered from 0 to 59 can be defined. For each equipment, give its Ethernet
address in hexadecimal, the local TSAP, the remote TSAP for the read and the remote TSAP for the
write. The TSAPs are 8-character ASCII strings.
If an equipment type is selected, a virtual connection request and maintenance mechanism will be
established as soon as the applicom® channel is initialized, even if no data is taken from the
server equipment (layer 4 management).
You can select these devices in the device library among the following types:
H1 HTB (R/W)
H1 TF (Sinec AP)
H1 TF2 (CNC)

Woodhead
Equipment number
Number of the applicom device used to access the H1 client
Ethernet address of the equipment

This choice is used to define the Ethernet address of the server PLC. This address must be
identical to that defined in the server PLC CP143 coupler configuration.
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 to the server equipment during the
connection phase: the server equipment can use this name as an identifier.
Remote read TSAP

This choice is used to define the name of the TSAP (Transport Service Access Point) for read
access to the server PLC equipment.
This name must also be defined in the server PLC coupler.
Server PLC coupler configuration (CP 143):
Contract Passive FETCH
Ethernet Address 000000000000
ID LOCAL TSAP Identical to this field (READREAD by default)
ID REMOTE TSAP not defined
Remote write TSAP

This choice is used to define the name of the TSAP (Transport Service Access Point) for write
Server PLC coupler configuration (CP 143):
Contract Passive RECEIVE
Ethernet Address 000000000000
ID LOCAL TSAP Identical to this field (WRITWRIT by default)
ID REMOTE TSAP not defined
For further information concerning PLC configuration, refer to SIEMENS documentation.

Woodhead
- Siemens equipments implementation
- PLC under Industrial Ethernet protocol READ/WRITE
- Connection between the computer and SIEMENS PLC
The PC is connected to the Industrial Ethernet network using the PC2000ETH card. A SIEMENS
PLC is connected to the Industrial Ethernet network by installing a special communication processor, the
CP143 or the CP1430, that is connected directly onto the mother board bus of SIMATIC® S5 PLCs. The
CP143 or CP1430 can be used with all S5 systems from S5 115U and greater. There are two physical
interfaces on the couplers, one to connect the Ethernet Industrial Ethernet network (AUI connector) and
the other for access to the coupler adjustment and configuration. Traffic management on the Industrial
Ethernet network is processed independently by the coupler, so releasing the CPU of the S5 PLC.
- 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.
BLGR : KY 0,6 ;Size of data zone used for the CPU <->CP communication(512
bytes).
PAFE : MB 255 ;Diagnostic byte.

Woodhead
- Example : CP143 and CP1430 configuration
Description
In this example, 4 types of exchange will be performed:
- 1 the applicom® card 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. Cyclic mode will be used to carry out this exchange.
- 2 The application can write words in the PLC in wait mode.
- 3 The 115U PLC must be client of the applicom® DATA-BASE. It must transmit a table of 128
words from DB10DW0 towards the DATA-BASE at the same address on the active status of the
E13.1 input.
- 4 On the active status of the E13.0 input, the PLC must also read in the DATA-BASE 128 words
from DB20DW0. They will be stored at the same address in the PLC.
applicom® card Ethernet address : 00A091004E84 (if the card has serial number 20100)
DATA-BASE TSAP in read : READREAD (default value)
DATA-BASE TSAP in write : WRITWRIT (default value)
PLC Ethernet address : 080006010000

PLC TSAP in read : READREAD
PLC TSAP in write : WRITWRIT
CP143 SIEMENS configuration with COM143

In this example, the configuration is carried out using the program COM143 supplied by SIEMENS.
This section is supplied for reference, and it is based on the COM143 program version available to
date (6/6/95). If this program has changed in the meantime, adapt this example with your new tool.
The first step is to configure the header (SYSID menu)
Enter the SSNR corresponding to your CP143 card (see « switch ») and the PLC Ethernet address.
Press F7 then F1 to confirm.

Woodhead
In second step, you must define the initialization block ( INIT menu ).
The third step allows you to define the different connections ( CONN menu).
In this example, four connections must be defined:
- server connection in read
Then SSNR must correspond with the one defined in the SYSID rubric. You must enter a contract
number and its type (here passive FETCH because server in read). Ethernet address of partner must be =
0. The SSNR and ANR « VERS API DIST » fields must be blank.

Woodhead
Press F5 to continue the connection definition
Select the READ/WRITE option in priority 2, then enter the local TSAP. This latter must be the
same that the one defined in the « Remote read TSAP » during the equipment configuration in the
applicom® configurator
Press F5 then F3 to start the following connection
- server connexion in write
number and its type (here passive RECEIVE because server in write). Ethernet address of partner must
be = 0. The SSNR and ANR « VERS API DIST » fields must be blank.

Woodhead
Select the READ/WRITE option in priority 2,.then enter the local TSAP. This latter must be the
same that the one defined in the « Remote write TSAP » during the equipment configuration in the
applicom® configurator.

Woodhead
- client connexion in read
number and its type (here active FETCH because client in read). Ethernet address of partner must be the
one of the applicom® board. The SSNR and ANR « VERS API DIST » fields must be blank.
Select the READ/WRITE option in priority 2, then enter the remote TSAP. This latter must be the
same that the one defined in the « local read TSAP » during the DATA-BASE configuration in the

Woodhead
- client connexion in write
number and its type (here passive SEND because client in write). Ethernet address of partner must be the
one of the applicom® board. The SSNR and ANR « VERS API DIST » fields must be blank.
Select the READ/WRITE option in priority 2,.then enter the remote TSAP. This latter must be the
same that the one defined in the « Local write TSAP » during the DATA-BASE configuration in the

Woodhead
CP1430 SIEMENS configuration with SINEC NCM COMs
In this example, the configuration is carried out using the program SINEC NCM COMs supplied by
SIEMENS. This section is supplied for reference, and it is based on the program version available to date
(V5.01). If this program has changed in the meantime, adapt this example with your new tool.
In the top tools bar, choise « Edition ».

Then, choice « Init CP »
Enter the PLC Mac Ethernet address and the SSNR and its shifting corresponding to your CP1430
card.
Press F7 to confirm.

Woodhead
The second step allows you to define the different connections
Always in menu « Edition », choise « Liaisons », then « Liaisons de transport »
In this example, 4 connections must be defined:
- server connection in read
The SSNR must correspond with the one defined in the Init CP rubric. You must enter a contract
number and its type (here passive FETCH because server in read). Select the READ/WRITE option in
priority 2, then enter TSAP local. This latter must be the same that the one defined in the « Remote read
TSAP » (READREAD by default) during the equipment configuration in the applicom® configurator.
Ethernet address of partner must be = 0. The « VERS API DIST » fields must be blank.
Press F3 to start the following connection

Woodhead
- server connection in write
number and its type (here passive RECEIVE because server in write). Select the READ/WRITE option in
priority 2, then enter TSAP local. This latter must be the same that the one defined in the « Remote write
TSAP » (WRITWRIT by default) during the equipment configuration in the applicom® configurator.
Ethernet address of partner must be = 0. The « VERS API DIST » fields must be blank.

Woodhead
- client connection in read
number and its type (here active FETCH because client in read). Select the READ/WRITE option in
priority 2, then enter TSAP distant. This latter must be the same that the one defined in the « Local read
TSAP of Server» (READREAD by default) during the equipment configuration in the applicom®
configurator. You can enter a TSAP local (Ex. AP00-010) to use card access management. Ethernet
address of partner must be the one of the applicom® board.

Woodhead
- client connection in write
number and its type (here active SEND because client in write). Select the READ/WRITE option in priority
2, then enter TSAP distant. This latter must be the same that the one defined in the « Local write TSAP of
Server» (WRITWRIT by default) during the equipment configuration in the applicom® configurator. You
can enter a TSAP local (Ex. AP00-010) to use card access management. Ethernet address of partner
must be the one of the applicom® board.

Woodhead
- 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)
A-NR : KY 0,0 send all
QTYP : KC NN source type non defined
DBNR : KY 0,0 non significant
ZANF : KF +0 non significant
ZLAE : KF +0 non significant
:
: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)
A-NR : KY 0,30 contract 30 see config CP143 or CP1430
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
:
: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)
A-NR : KY 0,31 contract 31 see config CP143 or CP1430
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
:
: BE

Woodhead
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;

Woodhead
- applicom® server configuration
Define the general characteristics of server with applicom console software program.
Definition of the equipment number 1 with stands for the PLC seen as client by applicom®

Woodhead
Creation of the read cyclic function in the PLC with the « PCCYC » software program.
Example of a write in the PLC in wait mode

Woodhead
- PLC under Industrial Ethernet TF
CP143 or the CP1430, that is connected directly onto the mother board bus of SIMATIC® S5. The CP143
or CP1430 can be used with all S5 systems from S5 115U and greater. There are two physical interfaces
on the couplers, one to connect the Ethernet Industrial Ethernet network (AUI connector) and the other for
access to the coupler adjustment and configuration. Traffic management on the Industrial Ethernet
network is processed independently by the coupler, so releasing the CPU of the S5 PLC.
- 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
SYNCHRON
Initialization and synchronization between the CPU and the CP. This block must be called on PLC
warm start or cold start sequences.
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.
BLGR : KY 0,6 ;Size of data zone used for the CPU ←→ CP communication (512 bytes).
PAFE : MB 255 ;Diagnostic byte.

Woodhead
- Configuration example : CP143 and CP1430 configuration
Description
- 1 the applicom® card is client of a SIMATIC® S5 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.
Cyclic mode will be used to carry out this exchange.
applicom® card Ethernet address : 00A091004E84 (if the card has serial number 20100)

PLC TSAP : READREAD
CP143 SIEMENS configuration with COM143
In this example, the configuration is carried out using the program COM143 supplied by SIEMENS.
This section is supplied for reference, and it is based on the COM143 program version available to date
(6/6/95). If this program has changed in the meantime, adapt this example with your new tool.
The first step is to configure the header (SYSID menu)
Enter the SSNR corresponding to your CP143 card (see « switch ») and the PLC Ethernet address.
Press F7 then F1 to confirm.

Woodhead
In second step, you must define the initialization block ( INIT menu ).
The third step allows you to define the TF connection. Press F5 ( STF DEF menu) then F1
(CONFIGURATION CONNEXION-STF menu).
Then SSNR must correspond with the one defined in the SYSID rubric. Enter an ANR number, an
ANZW control word with type MW x. Then enter a TSAP local according configured equipment in
applicom® configurator (READREAD by default). Select P4 in MODE ETAB option. Ethernet address of
partner must be equal to applicom® card Ethernet address.
CP1430 SIEMENS configuration with SINEC NCM COMs

Woodhead
In this example, the configuration is carried out using the program SINEC NCM COMs supplied by
SIEMENS. This section is supplied for reference, and it is based on the program version available to date
(V5.01). If this program has changed in the meantime, adapt this example with your new tool.
In the top tools bar, choise « Edition ».

Then, choise « Init CP »
Enter the PLC Mac Ethernet address and the SSNR and its shifting corresponding to your CP1430
card.

Woodhead
The second step allows you to define the TF connection
Always in menu « Edition », choise « Liaisons », then « Liaisons TF »
Then SSNR must correspond with the one defined in the Init CP rubric. Enter an ANR number, an
ANZW control word with type MW x. Select P4 in MODE ETAB option. Then enter a TSAP local
according configured equipment in applicom® configurator (READREAD by default). Ethernet address of
partner must be equal to applicom® card Ethernet address.

Woodhead
- PLC program for SIMATIC S5
C:READWRIT.S5D
Segment 1 0000
Nom : Industrial Ethernet
: AWL
:A DB 3 DB de travail
: SPA FB 245
Nom : RECEIVE FB receive (fonction automate serveur)
SSNR : KY 0,0 SSNR de votre CP143 ou CP1430
A-NR : KY 0,0 receive all
ANZW : DW 12 mot indicateur
ZTYP : KC NN type de la source non défini
DBNR : KY 0,0 non significatif
ZANF : KF +0 non significatif
ZLAE : KF +0 non significatif
PAFE : MB 242 octet indicateur
:
: SPA FB 244
Nom : SEND FB send (fonction automate serveur)
SSNR : KY 0,0 SSNR de votre CP143 ou CP1430
A-NR : KY 0,0 send all
ANZW : DW 10 mot indicateur
QTYP : KC NN type de la destination non défini
DBNR : KY 0,0 non significatif
ZANF : KF +0 non significatif
ZLAE : KF +0 non significatif
PAFE : MB 242 octet indicateur
:
:
: BE
Description du bloc de travail 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 (automate serveur)
11 : KH = 0000;
12 : KH = 0000; ANZW RECEIVE-ALL (automate serveur)
13 : KH = 0000;

Woodhead
- applicom® server configuration example

Woodhead

Woodhead
- applicom® functions usable on the master channel
- 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

Woodhead
- 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

Woodhead
- 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".
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.

Woodhead
- 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, 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 6
"- Maximum number of variables per exchange with OPC server" on page 7
Refer to chapter "- Simatic® S5 range" on page 4 for variable addressing.

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

Example: BI4
- Input bits => BIx_n, BIx_n_l
n: Number of bits.
Examples : BI4_10, BI4_10_5
- Output bits => BOx (type: BIT)

Example: BO4
- Output bits => BOx_n, BOx_n_l
n: Number of bits.
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

Woodhead
- Input bytes => OIx (type: BYTE)

Example: OI4
- Input bytes => OIx_n, OIx_n_l
n: Number of bytes.
Examples: OI4_10, OI4_10_5
- Output bytes => OOx (type: BYTE)

Example: OO4
- Output bytes => OOx_n, OOx_n_l
n: Number of bytes.
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

Woodhead
- Bits in internal words => Wx.b (type : bit)
in read : 128*16
in write : 1
x : First word number.

b : Bit range in the word (0 to 15).
Example : W4.5
- Input words => WIx (type: 16 bit WORD)

Example: WI4
- Input words => WIx_n, WIx_n_l
n: Number of words.
Examples: WI4_10, WI4_10_5
- Output words => WOx (type: 16 bit WORD)

Example: WO4
- Output words => WOx_n, WOx_n_l
n: Number of words.
Examples : WO4_10, WO4_10_5
- ASCII string in internal words => M_Wx_n (type: 16 bit WORD)
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.

Woodhead
- 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

Woodhead
- 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®
PC2000ETH (Ethernet channel).
For strings and matrices, the Descriptor checks for acceptable addressing limits, thus avoiding data
overlap.

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

Woodhead
Remarks :
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.
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.
Examples : E94.7_24 or E94:7_24, E94.7_24_8 or E94:7_24_8

Woodhead
- 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.
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.
Examples: MB4_10, MB4_10_5
- Input bytes => EBx (type: BYTE)
x: Number of the first input byte (0 to 127).

Example: EB4

Woodhead
- Input bytes => EBx_n, EBx_n_l
n: Number of bytes.
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.
Examples: AB4_10, AB4_10_5
- ASCII string in flag bytes => M_MBx_n (type: BYTE)
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
- Words in flag bytes => MWx_n, MWx_n_l
n: Number of words.
Examples : MW4_10, MW4_10_5
- Input words => EWx (type: 16 bit WORD)

Example: EW4
- Input words => EWx_n, EWx_n_l
n: Number of words.
Examples : EW4_10, EW4_10_5
- Output words => AWx (type: 16 bit WORD)

Example: AW4

Woodhead
- Output words => AWx_n, AWx_n_l
n: Number of words.
Examples: AW4_10, AW4_10_5
- Words in DB => DBxDWy (type: 16 bit WORD)
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.
Examples : DB4DW8_10, DB4DW8_10_5
- Words in DX => DXxDWy (type: 16 bit WORD)
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.
Examples : DX4DW8_10, DX4DW8_10_5
- Right byte of a word in the DB => DBxDRy (type: BIT)
in read : 128*2
in write : 1
y: Number of the word in the DB (0 to 255).
Example: DB4DR5
- Left byte of a word in the DB => DBxDLy (type: BIT)
in read : 128*2
in write : 1
Example: DB4DL5

Woodhead
- Right byte of a word in the DX => DXxDRy (type: BIT)
in read : 128*2
in write : 1
y: Number of the word in the DX (0 to 255).
Example: DX4DR5
- Left byte of a word in the DX => DXxDLy (type: BIT)
in read : 128*2
in write : 1
Example: DX4DL5
- ASCII string in DB words => M_DBxDWy_n (type: 16 bit WORD)
mode".
y: Number of the first word in the DB containing the string (0 to 255).
Example: M_DB4DW0_10
In the example, the word array DB4DW0 to DB4DW9 can contain the string.

Woodhead
- ASCII string in DX words => M_DXxDWy_n (type: 16 bit WORD)
mode".
y: Number of the first word in the DX containing the string (0 to 255).
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)

Example: MD4
- Double words in flag bytes => MDx_n, MDx_n_l

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

KG: 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)
Example: DB4DD8
- Double words in DB => DBxDDy_n, DBxDDy_n

Examples : DB4DD8_10, DB4DD8_10_5

Woodhead
- Double words in DX => DXxDDy (type: 32 bit WORD)
Example: DX4DD8
- Double words in DX => DXxDDy_n, DXxDDy_n

Examples : DX4DD8_10, DX4DD8_10_5
- Floating words in DB => DBxDDyKG (type REEL IEEE 32 bits)
Example : DB4DD8KG
- Floating words in DX => DXxDDyKG (type REEL IEEE 32 bits)
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

Woodhead
- Siemens Simatic S5 PLCs descriptor - English syntax
This descriptor can be used only for accessing Siemens Simatic S5 PLCs via the applicom®
PC2000ETH (Ethernet channel).
For strings and matrices, the Descriptor checks for acceptable addressing limits, thus avoiding data
overlap.

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

Woodhead
Remarks :
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.
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).

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.
Examples : I94.7_24 or I94:7_24, I94.7_24_8 or I94:7_24_8

Woodhead
- Output bits => Qx.y or Qx:y (type: BIT)

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.
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)
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.
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)
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.
Examples : DX94D10.7_24 or DX94D10:7_24, DX2D3.7_24_8 or DX2D3:7_24_8
- Flag bytes => FYx (type: BYTE)

Example: FY4
- Flag bytes => FYx_n, FYx_n_l
n: Number of bytes.
Examples : FY4_10 or FY4_10_5
- Input bytes => IBx (type: BYTE)

Example: IB4

Woodhead
- Input bytes => IBx_n, IBx_n_l
n: Number of bytes.
Examples : IB4_10, IB4_10_5
- Output bytes => QYx (type: BYTE)

Example: QY4
- Output bytes => QYx_n, QYx_n_l
n: Number of bytes.
Examples: QY4_10, QY4_10_5
- ASCII string in flag bytes => M_FYx_n (type: BYTE)
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)

Example: FW4
- Words in flag bytes => FWx_n, FWx_n_l
n: Number of words.
Examples : FW4_10, FW4_10_5
- Input words => IWx (type: 16 bit WORD)

Example: IW4
- Input words => IWx_n, IWx_n_l
n: Number of words.
Examples : IW4_10, IW4_10_5
- Output words => QWx (type: 16 bit WORD)

Example: QW4

Woodhead
- Output words => QWx_n, QWx_n_l
n: Number of words.
Examples: QW4_10, QW4_10_5
- Words in DB => DBxDWy (type: 16 bit WORD)
Example: DB4DW8
- Words in DB => DBxDWy_n, DBxDWy_n_l
n: Number of words.
Example : DB4DW8_10, DB4DW8_10_5
- Words in DX => DXxDWy (type: 16 bit WORD)
Example: DX4DW8
- Words in DX => DXxDWy_n, DXxDWy_n_l
n: Number of words.
Example : DX4DW8_10, DX4DW8_10_5
- Right byte of a word in the DB => DBxDRy (type: BIT)
in read : 128*2
in write : 1
Example: DB4DR5
- Left byte of a word in the DB => DBxDLy (type: BIT)
in read : 128*2
in write : 1
Example : DB4DL5

Woodhead
- Right byte of a word in the DX => DXxDRy (type: BIT)
in read : 128*2
in write : 1
Example: DX4DR5
- Left byte of a word in the DX => DXxDLy (type: BIT)
in read : 128*2
in write : 1
Example : DX4DL5
- ASCII string in DB words => M_DBxDWy_n (type: 16 bit WORD)
mode".
y: Number of the first word in the DB containing the string (0 to 255).
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)
mode".
y: Number of the first word in the DX containing the string (0 to 255).
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)

Example: FD4
- Double words in flag bytes => FDx_n, FDx_n_l

Examples: FD4_10, FD4_10_5

Woodhead
- Floating words in flag bytes => FDxKG (type: 32 bit IEEE REAL)
x: Number of the floating word (0 to 252).

Example: FD48KG
- Double words in DB => DBxDDy (type: 32 bit WORD)
Example: DB4DD8
- Double words in DB => DBxDDy_n, DBxDDy_n_l

Examples : DB4DD8_10, DB4DD8_10_5
- Double words in DX => DXxDDy (type: 32 bit WORD)
Example: DX4DD8
- Double words in DX => DXxDDy_n, DXxDDy_n_l

Examples : DX4DD8_10, DX4DD8_10_5
- Floating words in DB => DBxDDyKG (type: 32 bit IEEE REAL)
Example : DB4DD8KG
- Floating words in DX => DXxDDyKG (type: 32 bit IEEE REAL)
Example : DX4DD8KG
- Timers => TBx (type: 16 bit WORD)

Example: TB4
- Timers => TBx_n, TBx_n_l
Examples : TB4_10, TB4_10_5

Woodhead
- Counters => ZBx (type: 16 bit WORD)

Example: ZB4
- Counters => ZBx_n, ZBx_n_l
Examples : ZB4_10, ZB4_10_5

Woodhead
- Appendices
- List of extra files for this protocol
CLIH1HTB. Client task Industrial Ethernet

SERH1HTB. Server task Industrial Ethernet
NETH1HTB. Industrial EthernetNetwork management task
RDH1HTB. Industrial EthernetReception task
BTH1HTB. Industrial Ethernet time base
- Evolution / compatibility
This protocol necessitates on applicom® interfaces a version EPROM minimum V3.5.

Woodhead
- 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 statuses
-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.
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.

Woodhead
- Statuses according to the protocol

Further details :
Industrial Ethernet protocol:
- Returned by the destination coupler equipment. Undeclared DB or DB address out of delimiters.
3 Incorrect data.
Further details :
- Inconsistent frame content.
Function: BINBCD, BCDBIN, READWORDBCD, WRITEWORDBCD.
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).
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 »).
36 Equipment not configured.
Define the equipment configuration with the console and start again the applicom® product.
55 Time-Out elapsed, Message Lost
Further details :
- Communication established but no response to a request.
Further details :
- Insufficient resource for extra communication.
70 Communication terminated by remote user
Further details :
- 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 »).

Woodhead
3. - Simatic® TI505 Texas (READ/WRITE S5

Messaging)
Contents
- Functionality ........................................................................................................67
- Industrial Ethernet client........................................................................ 67
- Estimating the performance of an applicom® Industrial Ethernet Client. ...... 71
- Industrial Ethernet server ...................................................................... 73
- Configuration.......................................................................................................74
- PLC under Industrial Ethernet protocol READ/WRITE ................................. 77
- Wait mode ........................................................................................... 84
- Deferred mode...................................................................................... 84
- Cyclic mode.......................................................................................... 85
- Item of image variables - Presentation ...............................................................86
- Item of image variables - Standard descriptor ....................................................86
- Item of image variables - Texas Instrument descriptor.......................................91
- Internal variables .................................................................................. 91
- Input and output variables ..................................................................... 93
- Timers / Counters ................................................................................. 94
- Variables DRUM .................................................................................... 95
- System status....................................................................................... 96
- Constant words..................................................................................... 96
- LOOP variables ..................................................................................... 98
- ALARM variables ................................................................................. 101
- Appendices .......................................................................................................103
- List of extra files for this protocol .......................................................... 103
- Evolution / compatibility ...................................................................... 103
- applicom® general statuses ................................................................. 104
- Statuses according to the protocol......................................................... 105
Industrial Ethernet on PC2000ETH (ISO Layer 4) • 66 • - Simatic® TI505 Texas (READ/WRITE S5 Messaging)
Woodhead
- Functionality
® ® ®
- Simatic® TI505 range
The 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 in the most significant byte the
representation of the corresponding Q/ZTYP column (see A-1 Table of the A-1 appendix of the « Industrial
Ethernet Communication Processor User Manuel » manual). The three following bytes represent the
address of the constant decremented of 1.
Example : K1 constant
adr = 05 00 00 00 (hexa)
KF5 constant
adr = 06 00 00 04 (hexa)
For the other variables (LOOP, ALARM, ...), the applicom® corresponding address is calculated on
32 bits with the most significant bit equals to 08, the following byte is equal to the value in the PLC TT
column up to the 73 (hexa) value (see A-1 Table of the A-1 appendix of the « Industrial Ethernet
Communication Processor User Manual ») and the two following bytes equal to the address of the
variable decremented of 1. (Run the ESSAI program with the hexa option « essai hex » in order to enter
the hexadecimal address).
Example : Loop Status of the loop n°1 : LS0001

adr = 08 1E 00 00
High Alarm Limit of the alarm n°2 : AHA0002
adr = 08 50 00 01
The item descriptor usable with PCDDE associated with this addressing is " Texas Instrument ".
Woodhead
Siemens PLC applicom® corresponding applicom®

Simatic TI505 Addressing Type of exchange Function
Variable (addr) (library/DLL access)
Cv v-1 Read bits READPACKBIT, READDIFBIT
Write bits WRITEPACKBIT, WRITEDIFPACKBIT
Vv v-1 Read words READWORD, READDIFWORD

Write words WRITEWORD, WRITEDIFWORD
Vv v-1 Read double words READDWORD, READDIFDWORD

Write double words WRITEDWORD, WRITEDIFDWORD
VF v v-1 Read floats READFWORD, READDIFFWORD

Write floats WRITEFWORD, WRITEDIFFWORD
Xv v-1 Read input bits READPACKIBIT, READDIFIBIT
WX v v-1 Read input words READIWORD, READDIFIWORD
Yv v-1 Read output bits READPACKQBIT, READDIFQBIT

Write output bits WRITEPACKQBIT,
WRITEDIFPACKQBIT
WY v v-1 Read output words READQWORD, READDIFQWORD
Write output words WRITEQWORD, WRITEDIFQWORD
Constants xx (v)(address Read(voir colonne Q/ZTYP), READxxxx, READDIFxxxx

in hexa) Write(voir colonne Q/ZTYP) WRITExxx,WRITEDIFxxxx
Kv 05 (v - 1) Read words READWORD, READDIFWORD

Kv 05 (v - 1) Read double words READDWORD, READDIFDWORD

Write double words WRITEDWORD, WRITEDIFDWORD
KF v 06 (v - 1) Read floats READFWORD, READDIFFWORD

Other 08(PLC TT)(v) Read(voir colonne PLC READxxxx, READDIFxxxx

Variables (address in Repres), Write(si autorisée voir WRITExxx,WRITEDIFxxxx
(examples) hexa) colonne PLC Repres)
TCP v 08 0E(v - 1) Read words READWORD, READDIFWORD

TCC v 08 0F (v - 1) Read words READWORD, READDIFWORD

...
LS v 08 1E (v - 1) Read words READWORD, READDIFWORD
LM v 08 1F (v - 1) Read words READWORD, READDIFWORD

Woodhead
LKC v 08 20 (v - 1) Read floats READFWORD, READDIFFWORD
...
AHA v 08 50 (v - 1) Read floats READFWORD, READDIFFWORD

ALA v 08 51 (v - 1) Read floats READFWORD, READDIFFWORD

...
AACK v 08 73 (v - 1) Read words READWORD, READDIFWORD

v : Variable N°

Bit 256
Word 128
Double word 64
Floating word 64

Bit 256
Word 128
Double word 64
Floating word 64
configuring the length of frames in the topic (see the chapter "Implementation/Topic Configuration/
Advanced Options / frame length”
Woodhead

Bit 256
Word 128
Double word 64
Floating word 64
configuring the length of frames in the topic (see the chapter "Implementation/Topic Configuration/
Advanced Options / frame length”)
For write frames, see chapter "OPC Server/Synchronous and Asynchronous Request
Optimization".
Woodhead
- Estimating the performance of an applicom® Industrial Ethernet
Client.
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 20 Siemens stations type
115U with a CPU 943B and a CP 143 coupler card, with a cycle time of 25 ms.
The « SendAll » and « ReceiveAll » call is only made once per PLC cycle, which means that
the PLC access is monoflow. The PLC configuration is as described in the software
installation manual « Software installation » chapter « Configuration with Siemens
equipment » without the client PLC contracts. No inter-PLC exchange is active.
applicom
international
PC2000ETH
I. E. Network
Station 0 Station 19
20 Simatic TI stations
( 545 / CP1434 )
Woodhead
Number of variables:
3 tables of 128 words and 1 table of 2048 bits per station.

i.e. a total of 80 requests to retrieve all the variables (7680 words and 40960 bits) spread
over the 20 Industrial Ethernet stations.
Req / s
140
120
100
80
60
40
20
Nb
1 2 3 4 5 6 7 Station
20
applicom® database retrieval time (Except application and supervision)

Notes:
The number of simultaneous cyclic functions is deliberately limited to 8 on the Industrial
Ethernet network in order not to overload the Ethernet network.
Network transmission time is negligible as long as it does not exceed 10% load.
In our example, to retrieve variables from 20 devices, 80 requests are needed, i.e.
80 (requests) / 100 (requests/s) = 0.8 second.
This calculation is only valid if the data retrieved is distributed in all devices.
Woodhead
The Industrial Ethernet Server on applicom® interface makes available a 32 kword database to
Siemens network architecture clients TI (READ/WRITE).

Read input bits (X) bits area 0000 - 1023 X1 to X1024
Read output bits(Y) bits area 1024 - 2047 Y1 to Y1024
Read bits (C) bits area 2048 - 31999 C1 to C29952
Read datas (V) word area 0000 - 31999 V1 to V32000
Write input bits(X) bits area 0000 - 1023 X1 to X1024
Write output bits(Y) bits area 1024 - 2047 Y1 to Y1024
Write bits (C) bits area 2048 - 31999 C1 to C29952
Write datas (V) word area 0000 - 31999 V1 to V32000

256 bits, input or output bits
128 data words
transmitting equipment is disconnected. To do this :
• You can define a maximum time interval between client equipment accesses to the applicom®
Industrial Ethernet Server, in the name of the client Local TSAP. This name is defined in the
client PLC configuration. The Industrial Ethernet Server task on applicom® interface can
manage up to 60 connections with client stations. As seen by applicom®, a connection with a
client station is marked by a number from 0 to 59. For a given connection, a client station can
initialize the access time-out value. This initialization is made by the client PLC local TSAP name
during the connection sequence. The name of the local TSAP must be type: APnn-vvv where
AP is the applicom® identifier, nn represents a connection number seen by applicom® (from
00 to 59) and vvv represents the access time-out to the applicom® DATA-BASE (from 001-
999 seconds).
Example: for connection 1 with a time-out value of 10 seconds, a local TSAP = AP01-010.
applicom® database. Define the address of this status word using the channel configuration
utility.
After this period, absence is signaled to the application by an « ACCESS STATUS WORD » in the
applicom® database. Use the channel configuration utility to define the address of this status
word.
Woodhead
- Configuration
PCI2000ETH).

allow client equipment read access to the DATA-BASE server.

allow client equipment write access to the DATA-BASE server.

Woodhead
IEEE serial number
00 A0 91 xx xx xx
Example:
00 A0 91 00 4E 84

used set value -1.
equipment. If the « Access Time-Out » configured in the name of the client equipment local TSAP is
exceeded, the applicom® interface will indicate this absence in the corresponding word at the
offset defined in the client equipment local TSAP.
. .

corresponding word at the offset defined in the client equipment local TSAP.

« ID LOCAL TSAP » in the form APnn-vvv example AP00-010
. .
Resetting this word to 0 is your responsibility to be informed of the next write and/or inform the
transmitting equipment of this acknowledgment.
Woodhead

If an equipment type is selected, a virtual connection request and maintenance mechanism will be
established as soon as the applicom® channel is initialized, even if no data is taken from the
server equipment (layer 4 management).
You can select the type « H1 TI » in the equipment library.
Equipment number
Number of the applicom device used to access the H1 client.

identical to that defined in the server PLC CP1434 coupler configuration.
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 to the server equipment during the
connection phase: the server equipment can use this name as an identifier.
Remote read TSAP

This choice is used to define the name of the TSAP (Transport Service Access Point) for read
Remote write TSAP

This choice is used to define the name of the TSAP (Transport Service Access Point) for write
Woodhead
- Siemens equipments implementation
- PLC under Industrial Ethernet protocol READ/WRITE
CP1434 for SIMATIC® TI505 PLCs. Traffic management on the Industrial Ethernet network is processed
independently by the coupler, so releasing the CPU of the TI505 PLC.
- Communication between the TI505 processor and the CP 1434 coupler
Communication between the PLC processor and the CP1434 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
Woodhead
- Configuration example : CP1434 Texas Configuration
Description
- 1 the applicom® card is client of a SIMATIC® TI505 PLC.
applicom® card Ethernet address : 080006010001

PLC TSAP in read : READREAD
PLC TSAP in write : WRITWRIT
CP1434 Configuration with 505H1 utility (for Windows)
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 ».
Woodhead
Enter informations in Peer Service Read window like under
Then create a « Read Passive » « Job » type
Woodhead
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 ».
Woodhead
It’s possible to controle the coupler working and the « Jobs » activity for reading and writing. Press
« Debug » in main window then « Peers Services ». Look at the select « job » like under.
Woodhead
- applicom® server configuration example
Woodhead
Woodhead
- Wait mode
readpackibit
readbyte writebyte
readibyte
readpackibyte
readword writeword
readiword
- Deferred mode
readdifibit
readdifibyte
readdifiword
Woodhead
- Cyclic mode
createcyc

Packed bits X X
Input packed bits X
Packed bytes X X
Bytes X X
Input bytes X
Output bytes X X
Words X X
BCD words X X
Input words X
Output words X X
Woodhead
- Item of image variables - Presentation
For more information, please refer to the chapter "DDE Server/Data Access/Data Access
Principles" or to the chapter "OPC Server/ Data Access/Data Access Principles".
equipment. For Texas Instrument, Simatic TI505 is the default descriptor.
- Item of image variables - Standard descriptor


Woodhead
Remarks :

Refer to chapter "- Simatic® TI505 range" on page 67 for variable addressing.
- Internal bits => Bx (type : BIT)

Example: B4
n: Number of bits.
Examples : B4_10, B4_10_5
- Input bits => BIx (type : BIT)

Example : BI4
n: Number of bits.
- Output bits => BOx (type : BIT)

Example: BO4
n: Number of bits.

Example : O4
n : Number of bytes.
l : Number of bytes per line (Matrix mode only).
Woodhead
in read : 256*8
in write : 1

Example : O4.5
- Input bytes => OIx (type : BYTE)

Example : OI4
Examples : OI4_10, OI4_10_5
- Output bytes => OOx (type : BYTE)

Example : OO4
- ASCII string in internal bytes => M_Ox_n (type : BYTE)
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.
- Internal words => Wx (type : 16 bit WORD)

Example: W4
n: Number of words.
Examples : W4_10, W4_10_5
Woodhead
- Bits in internal words => Wx.b (type : BIT)
in read : 128*16
in write : 1
b: Rank of the bit in the word (0 to 15).
Example : W4.5
- Input words => WIx (type : 16 bit WORD)

Example: WI4
n: Number of words.
Examples : WI4_10, WI4_10_5
- Output words => WOx (type : 16 bit WORD)

Example: WO4
n: Number of words.
- ASCII string in internal words => M_Wx_n (type : 16 bit WORD)
mode".

Example: M_W100_30
Woodhead
- Internal double words => Dx (type : 32 bit WORD)

Example: D4

Examples: D4_10, D4_10_5
- Internal floating words => Fx (type : 32 bit IEEE REAL)

Example: F4

Woodhead
- Item of image variables - Texas Instrument descriptor
This descriptor is usable only for access to the Texas Instrument equipments with applicom®
interfaces.
- Internal variables

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.
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.
Examples : V4_10, V4_10_5
Woodhead
- Bits in the internal words => Vx.b (type : BIT)
in read : 128*16
in write : 1

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

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

Examples : VF4_10, VF4_10_5
- ASCII string in the internal words => M_Vx_n (type : 16 bit WORD)
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.
Woodhead
- Input and output variables

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.
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.
Examples : Y4_10, Y4_10_5
- Input words => WXx (type : 16 bit WORD)

Example : WX4
- Input words => WXx_n, WXx_n_l
n: Number of words.
Examples : WX4_10, WX4_10_5
Woodhead
- Output words => WYx (type : 16 bit WORD)

Example : WY4
- Output words => WYx_n, WYx_n_l
n: Number of words.
Examples : WY4_10, WY4_10_5
- Timers / Counters

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.
Examples : TCP4_10, TCP4_10_5
- Timer / counter current values => TCCx (type : 16 bit WORD)

Example : TCC4
- Timer / counter current values => TCCx_n, TCCx_n_l
n: Number of words.
Examples : TCC4_10, TCC4_10_5
Woodhead
- Variables DRUM

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)

Example : DSP4
- Preselection values of the "DRUM" step => DSPx_n, DSPx_n_l
n: Number of words.
Examples : DSP4_10, DSP4_10_5
- Values of the current "DRUM" step => DSCx (type : 16 bit WORD)

Example : DSC4
- Values of the current "DRUM" step => DSCx_n, DSCx_n_l
n: Number of words.
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.
Examples : DCP4.5_10, DCP4.5_10_5
Woodhead
- System status

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.
Examples : STW4_10, STW4_10_5
- Constant words

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 :

Woodhead
- Constant words => Kx (type : 16 bit WORD)

Example : K4
- Constant words => Kx_n, Kx_n_l
n: Number of words.
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

Examples : KD4_10, KD4_10_5
- Bits in the internal constants => Kx.b ( type : BIT)
in read : 128*16
in write : 1

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

Examples : KF4_10, KF4_10_5
Woodhead
- LOOP variables
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
Bits in the words X X LHARx.b
Woodhead
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).
Woodhead
Remarks :

Woodhead
- ALARM variables
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
AODAR 16 bit WORD X X AODARx AODARx_n, AODARx_n_l
Bits in the words X X APVRx.b
Woodhead
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).
Remarks :

Woodhead
- Appendices

Woodhead
activated.
1 Unknown function.
3 Incorrect data.
Further details :
positions).
Comments :
Woodhead

Further details :
3 Incorrect data.
Further details :
Further details :
Further details :
Define the equipment configuration with applicom console and start again the applicom® product.
Further details :
Further details :
Further details :
Woodhead
4. - Simatic® S7 (S7 Protocol)
Contents
-Functionality .......................................................................................................107
- Industrial Ethernet client...................................................................... 107
- Estimating the performance of an applicom® Industrial Ethernet Client. .... 112
- Industrial Ethernet server .................................................................... 114
- Configuration.....................................................................................................116
Server equipment configuration ..........................................................................118
- Siemens S7 equipments implementation..........................................................120
- Description ......................................................................................... 120
- SIEMENS PLC configuration with Step7 .................................................. 120
- applicom® server configuration ............................................................ 125
- applicom® functions usable on the master channel .........................................128
- Wait mode ......................................................................................... 128
- Deferred mode.................................................................................... 128
- Cyclic mode........................................................................................ 129
- Item of image variables .....................................................................................130
- Presentation ....................................................................................... 130
- Standard descriptor ............................................................................. 130
- Siemens Simatic S7 PLCs descriptor ..................................................... 135
- Appendices .......................................................................................................140
- List of extra files for this protocol .......................................................... 140
- Evolution / compatibility ...................................................................... 140
- applicom® general statuses ................................................................. 141
- Statuses according to the protocol......................................................... 142
Industrial Ethernet on PC2000ETH (ISO Layer 4) • 106 • - Simatic® S7 (S7 Protocol)

Woodhead
-Functionality
® ® ®
- Simatic® S7 range
The variables of the Siemens S7 series are numbered by byte and not by 16 bit word as the DB
variables of the Siemens S5 series. So it’s nevertheless possible to access to words, double words or
floating words which addresses start on even or odd addresses. A request of reading several words must
allow the user to access to a word array, whatever their physical addresses. To solve this problem, the
Industrial Ethernet protocol task returns as much variables according to configuration with address on
byte, word or double word.
Example 1 : An application wants to read in one request, the words MW11 and MW14. So It will
use a reading request from the address 11. The content of the response will be presented as followed:
-alignment on byte address
User array offset S7 variable Physical address in the PLC (in byte)
0 MW11 11 and 12
1 MW12 12 and 13
2 MW13 13 and 14
3 MW14 14 and 15
-alignment on word address
0 MW11 11 and 12
1 MW13 13 and 14
2 MW15 15 and 16
3 MW17 17 and 18
Note : This principle cannot be applied to the writing of several variables in one request.
Writing of 2 words from the address 11.
0 MW11 11 and 12
1 MW13 13 and 14

Woodhead
Example 2 : An application wants to read in one request the double words MD10 and MD16. It will
use a reading request from the address 11. The content of the response will be presented as followed:
-alignment on byte address
0 MD10 from 10 to 13
-alignment on word address
-alignment on double word address
Writing of 2 double words from the address 10
Adressing 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 ".

Woodhead
S7-300 S7-400 applicom® Type of exchange Corresponding applicom® function
Variable Addressing (library/DLL access)
(addr)
My.z y*8+z Read bits READPACKBIT
DBx.DBXy.z x*524288+y*8+z Write bit WRITEPACKBIT
Ey.z y*8+z Read input bits READPACKIBIT
Ay.z y*8+z Read output bits READPACKQBIT

Write output bit WRITEPACKQBIT
MBy y Read bytes READPACKBYTE,READBYTE

DBx.DBBy x*65536+v Write bytes WRITEPACKBYTE,WRITEBYTE
EBy y Read input bytes READPACKIBYTE,READIBYTE
ABy y Read output bytes READPACKQBYTE,READQBYTE

Write output bytes WRITEPACKQBYTE,WRITEQBYTE
MWy y Read words READWORD

DBx.DBWy x*65536+y Write words WRITEWORD
EWy y Read input words READIWORD
AWy y Read output words READQWORD

Write output words WRITEQWORD
MDy y Read double words READDWORD

DBx.DBDy x*65536+y Write double words WRITEDWORD
MDyF y Read floating words READFWORD

DBx.DBDyF x*65536+y Write floating words WRITEFWORD
Tn n Read timers READTIMER
Write timers WRITETIMER
Zn 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 127)
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

Woodhead
Object Max. quantity in read Max. quantity in write

PLC PLC PLC PLC
S7-400 S7-300 S7-400 S7-300
Bit 2048 1776 1 1
Byte 256 222 256 212
Word 128 111 128 106
Double word 64 55 64 53
Timer/counter 128 111 128 106
The maximum quantities in read are different according to addressing mode (byte, word or double
word) for S7-300 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.

Alignment byte word double word
PLC S7-300 S7-400 S7-300 S7-400 S7-300 S7-400 S7-300 and S7-400
Bit 1776 2048 1
Byte 222 256 1
Word 128 128 111 128 1
Double Word 64 64 64 64 55 64 1
PLC S7-300 S7-400 S7-300 and S7-400
Timer/counter 111 128 1
options").

Woodhead

Alignment byte word double word
PLC S7-300 S7-400 S7-300 S7-400 S7-300 S7-400 S7-300 S7-400
Bit 1776 2048 1 1
Byte 222 256 212 256
Word 128 128 111 128 106 128
Double Word 64 64 64 64 55 64 53 64
PLC S7-300 S7-400 S7-300 S7-400
Timer/counter 111 128 106 128
options").
For the write frames, see chapter "OPC Server/Optimization of synchronous and asynchronous
requests".

Woodhead
- Estimating the performance of an applicom® Industrial Ethernet
Client.
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 20 Siemens stations type
S7-400 with a CPU 413-2 and a CP 443-1 coupler card, with a cycle time of 25 ms.
The PLC configuration is as described in the example of this manual, chapter "- Siemens S7
equipments implementation". No inter-PLC exchange is active.
applicom
international
PC2000ETH
I. E. Network
Station 0 Station 19
20 Simatic S7 stations
( S7-413 / CP443-1 )

Woodhead
Number of variables:
3 tables of 128 words and 1 table of 1904 bits per station.

i.e. a total of 80 requests to retrieve all the variables (7680 words and 38080 bits) spread
over the 20 S7 stations.
Req / s
140
120
100
80
60
40
20
Nb
1 2 3 4 5 6 7 Station
20
applicom® database retrieval time (except application and supervision)

Notes:
The number of simultaneous cyclic functions is deliberately limited to 8 on the Industrial
Ethernet network in order not to overload the Ethernet network.
Network transmission time is negligible as long as it does not exceed 10% load.
In our example, to retrieve variables from 20 devices, 80 requests are needed, i.e.
80 (requests) / 100 (requests/s) = 0.8 second.
This calculation is only valid if the data retrieved is distributed in all devices.

Woodhead
The Industrial Ethernet Server on applicom® interface makes available a 32 kwords database to
Simatic S7 network architecture clients (protocol S7).

Read inputs(EB) byte area 0 - 127 EB0 to EB127
Read outputs (AB) byte area 128 - 255 AB0 to AB127
Read memos (MB) byte area 256 - 511 MB0 to MB255
Read data blocks (DB) word area 256 - 31999 DB1.DBW0 to DB124.DBW255
DB1.DBD0 to DB124.DBD254
Read data blocks (DB) byte area 1200 - 13999 DB100.DBB0 to DB124.DBB511
Write outputs (AB) byte area 128 - 255 AB0 to AB127
Write memos (MB) byte area 256 - 511 MB0 to MB255
Write data blocks (DB) word area 256 - 31999 DB1.DBW0 to DB124.DBW255
DB1.DBD0 to DB124.DBD254
Write data blocks (DB) byte area 1200 - 13999 DB100.DBB0 to 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

y : N° of DBB byte in the DB (0 to 511)
z : Bit n° in word (0 to 15)
• for words in a DB DBx.DBWy x*256+y

y : N° of DBW word in the DB (0 to 255)

128 input or output bytes
256 memo bytes or from DB’s
128 DB words (with alignment on byte address)


Woodhead
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.
applicom® database. Use the address of this status word using the channel configuration utility.
The Industrial Ethernet Server task on applicom® interface can manage up to 14 connections
with Simatic S7 client stations. As seen by applicom®, a connection with a client station is marked by a
number from 2 to 15. For a given connection, a client station can initialize this number. This initialization is
made by the declaration of the CPU position of the « face » equipment configured in the global project of
Step7. This number is sent by PLC at connection sequence.

Woodhead
- Configuration
PCI2000ETH).

Only with S5 range.

Only with S5 range.

Woodhead
IEEE serial number
00 A0 91 xx xx xx
Example:
00 A0 91 00 4E 84

used set value -1.
equipment. If the « Access Time-Out » configured is exceeded, the applicom® interface will
indicate this absence in the corresponding word at the offset defined in the client equipment.

corresponding word at the offset defined in the client equipment.
General time-out for the S7 clients access

Time-out between two requests from S7 client. After this delay, an error status is copied in
DATA_BASE at the offset corresponding to the client number, if the option « Address Access
Status Word » is actived.
The default value of this time-out is 10 sec. and it is global for all S7 clients. It can vary from 0 to
999 secondes.

Woodhead

If an equipment type is selected (here « Industrial Ethernet S7 »), a virtual connection request and
maintenance mechanism will be established as soon as the applicom® channel is initialized, even
if no data is taken from the server equipment (layer 4 management).
You can select these devices in the device library on the Protocol S7 type.
Equipment number
Number of the applicom device used to access the H1client.

identical to that defined in the server PLC CP443-1 coupler configuration.
CPU slot
This choice is used to define the position of the CPU card in the PLC rack (from 2 to 15) according
to the configuration in Step7. This number will be transmitted to the server equipment during the
connection phase.

Woodhead
Data alignment for 16 bits words reading in the DB
This parameter allows the 16 bits data alignment on byte addresss (value=1) or on word address
(value=2) during words table reading in th DB’s. The default value is 1.
Word X Word X+1

byte 1 byte 2 byte 3 byte 4
first array word
second array word alignment = 1
third array word
first array word second array word alignment = 2
Data alignment for 32 bits words reading in the DB

This parameter allows the 32 bits data alignment on byte addresss (value=1), on word address
(value=2) or on double word address (value=4).
Double Word X Double Word X+1

byte 1 byte 2 byte 3 byte 4 byte 5 byte 6 byte 7 byte 8
first array double word
second array double word
third array double word alignment = 1
fourth array double word
fifth array double word
first array double word
second array double word alignment = 2
third array double word
first array double word second array double word alignment = 4

Woodhead
- Siemens S7 equipments implementation
- Description
- 1 the applicom® card is client of a SIMATIC® S7-400 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.
applicom® card Ethernet address : 080006010001

CPU Slot :3
- SIEMENS PLC configuration with Step7
In this example, the configuration is carried out using the program Step7 supplied by SIEMENS. For
further information concerning PLC configuration, refer to SIEMENS documentation.
The first step is to create a project in the environment

Woodhead

Woodhead
In second step, you must declare the hardware configuration for your PLC. For this :
1 Rack
1 Alimentation
1 CPU (note its slot number for server equipment configuration)
1 Coupler « Industrial Ethernet » CP443-1.

Woodhead
After, you must click on the line corresponding with the coupler in order to define its Ethernet
address.

Woodhead
Click on « SINEC H1 » and define the Ethernet address
After, load this configuration in PLC during « Stop »mode. Then activate the « Run » mode.
The green leds on CPU and coupler must be lighted and fixed.
Now, the coupler is ready to run and to do the connection with the client when the init is running
(PCINIT).

Woodhead
- applicom® server configuration

Woodhead

Woodhead

Woodhead
- Wait mode
readpackibit
readbyte writebyte
readibyte
readpackibyte
readword writeword
readiword
- Deferred mode
readdifibit
readdifibyte
readdifiword

Woodhead
- Cyclic mode
createcyc

Packed bits X X
Input packed bits X
Packed bytes X X
Bytes X X
Input bytes X
Output bytes X X
Words X X
BCD words X X
Input words X
Output words X X

Woodhead
- Item of image variables
- Presentation
Report you to sections "DDE server/Principles regarding access to Data" or "OPC server/Data
Access Principle
equipment. For S7, the default descriptor is Simatic S7.
- Standard descriptor


Woodhead
Remarks:

- Internal bits => Bx (type : BIT)

Example: B4
n: Number of bits.
Examples : B4_10, B4_10_5
- Input bits => BIx (type : BIT)

Example : BI4
n: Number of bits.
- Output bits => BOx (type : BIT)

Example: BO4
n: Number of bits.

Example : O4

Woodhead
in read : 238*8
in write : 1

Example : O4.5
- Input bytes => OIx (type : BYTE)

Example : OI4
Examples : OI4_10, OI4_10_5
- Output bytes => OOx (type : BYTE)

Example : OO4
- ASCII string in internal bytes => M_Ox_n (type : BYTE)
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.

Woodhead
- Internal words => Wx (type : 16 bit WORD)

Example: W4
n: Number of words.
Examples : W4_10, W4_10_5
- Bits in internal words => Wx.b (type : BIT)
in read : 119*16
in write : 1

Example : W4.5
- Input words => WIx (type : 16 bit WORD)

Example: WI4
n: Number of words.
Examples : WI4_10, WI4_10_5
- Output words => WOx (type : 16 bit WORD)

Example: WO4
n: Number of words.

Woodhead
- ASCII string in internal words => M_Wx_n (type : 16 bit WORD)
mode".
Example: M_W100_30
- Internal double words => Dx (type : 32 bit WORD)

Example: D4

Examples: D4_10, D4_10_5
- Internal floating words => Fx (type : 32 bit IEEE REAL)

Example: F4


Woodhead
- Siemens Simatic S7 PLCs descriptor
This descriptor is usable for access to the Siemens 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.

Marker 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
Marker 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 marker bytes M_MBx_n
ASCII string in the DB bytes M_DBx.DBBy_n
Words in the markers MWx
Words in the DB DBx.DBWy
Input words EWx
Output words AWx
Double words in the markers MDx
Double words in the DB DBx.DBDy
Floating words in the markers MDxF
Floating words in the DB DBx.DBDyF
Timers Tx Tx_n, Tx_n_l
Counters Zx Zx_n, Zx_n_l
Remarks:


Woodhead
- Marker bits => Mx.y (type: BIT)
x: Number of the marker (0 to 65 535).

y: Rank of the first bit in the marker (0 to 7).
Example : M94.7
- Marker bits => Mx.y_n, Mx.y_n_l
n: Number of bits.
Examples : M94.7_24, M94.7_24_8
- Input bits => Ex.y (type: BIT)
x: Number of the input byte (0 to 65 535).

Example : E94.7
- Input bits => Ex.y_n, Ex.y_n_l
n: Number of bits.
Examples : E94.7_24, E94.7_24_8
- Output bits => Ax.y (type: BIT)

Example : A94.7
- Output bits => Ax.y_n, Ax.y_n_l
n: Number of bits.
Examples : A94.7_24, A94.7_24_8
- Bits of bytes in the DBs => DBx. DBXy.z (type: BIT)
Example : DB94.DBX3.7
- Bits of bytes in the DBs => DBx. DBXy.z_n, DBx.DBXy.z _n_l
n: Number of bits.
Examples : DB94.DBX3.7_24, DB94.DBX3.7_24_8
- Marker bytes => MBx (type: BYTE)
x: Number of the first marker (0 to 65535).

Example : MB4

Woodhead
- Marker bytes => MBx_n, MBx_n_l
n: Number of bytes.
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.
Examples : DB4.DBB5_10, DB4.DBB5_10_2
- Input bytes => EBx (type: BYTE)

Example : EB4
- Input bytes => EBx_n, EBx_n_l
n: Number of bytes.
Examples : EB4_10, EB4_10_5
- Output bytes => ABx (type: BYTE)

Example : AB4
- Output bytes => ABx_n, ABx_n_l

n: Number of bytes.
Examples : AB4_10, AB4_10_5

Woodhead
- ASCII string in the marker bytes => M_MBx_n (type: BYTE)
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.
- ASCII string in the DB bytes => M_DBx.DBBy_n (type: BYTE)
mode".
x : DB number (0 to 32 767).
y: Number of the first byte containing the string (0 to 65535).
n: Number of potential marker 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 markers => MWx (type: 16 bit WORD)

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

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

Example : AW4
- Double words in the markers => 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 markers => 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
- Timers => Tx (type: 16 bit WORD)

Example: T4
- Timers => Tx_n, Tx_n_l
Examples : T4_10, T4_10_5
- Counters => Zx (type: 16 bit WORD)

Example: Z4
- Counters => Zx_n, Zx_n_l
Examples : Z4_10, Z4_10_5

Woodhead
- Appendices


Woodhead
activated.
1 Unknown function.
3 Incorrect data.
Further details :
positions).
Comments :

Woodhead

Further details :
3 Incorrect data.
Further details :
Further details :
Further details :
Define the equipment configuration with applicom console and start again the applicom® product.
Further details :
Further details :
Further details :

Woodhead
5. - Glossary of terms
applicom® interface
Communication card, ISA or PCI type, with the applicom® real time multi-task kernel
ASCII
American Standard Code for Information Interchange
Channel
Physical output of an applicom® card
Client
Node which has communication initiative
Coupler
Communication interface
DATA-BASE
applicom® database, with 32 kbits and 32 kwords
DB
Siemens word to describe a Data bloc
Item
Defines an element
Memo
Siemens word to describe internal memory of a PLC
OPC
Ole for Process Control
PCDDE
applicom® DDE server
Industrial Ethernet on PC2000ETH (ISO Layer 4) • 143 • - Glossary of terms

Woodhead
6. - Index
Addressing, 6, 78, 121

Client
Performance S7, 126
Performance TI, 82
S5, 6
S7, 121
TI, 78
Configuration
S5, 13
S7, 130
TI, 85
Coupler
CP143, 18, 36
CP1430, 18, 36
CP1434, 88
CP143, 18, 36
CP1430, 18, 36
CP1434, 88
DATA-BASE
S5, 11
S7, 128
TI, 84
EPROM
S5, 71
S7, 155
TI, 114
Equipments Siemens
Implementation S5, 18
Implementation S7, 134
Implementation TI, 88
Error
S5, 72
S7, 156
TI, 115
Evolution
S5, 71
S7, 155
TI, 114
FETCH, 18
Functionality, 6, 78, 121
Functions return
S5, 72
S7, 156
TI, 115
Industrial Ethernet
Presentation, 1
Item descriptor S5
Simatic S5 D FR descriptor, 53
Simatic S5 GB descriptor, 62
Standard descriptor, 47
Item descriptor S7
Siemens S7 descriptor, 149
Industrial Ethernet on PC2000ETH (ISO Layer 4) • 144 • - Index

Woodhead
Item descriptor TI
Texas Instrument descriptor, 102
Items S5
Simatic S5 D FR descriptor, 53
Simatic S5 GB descriptor, 62
Items S7
Siemens S7 descriptor, 149
Items TI
Texas Instrument descriptor, 102
Layer, 1
Limits S5
Library, 8
OPC server, 9
PCDDE, 8
Limits S7
Library, 124
OPC server, 125
PCDDE, 124
Limits TI
Library, 80
OPC server, 81
PCDDE, 80
Maximum number of variables per exchange S5
Library, 8
OPC server, 9
PCDDE, 8
Maximum number of variables per exchange S7
Library, 124
OPC server, 125
PCDDE, 124
Maximum number of variables per exchange TI
Library, 80
OPC server, 81
PCDDE, 80
Performance
S7, 126
TI, 82
Presentation, 1
READ/WRITE
S5, 18
TI, 88
RECEIVE, 18
S5
Client, 6
Configuration, 13
DATA-BASE, 11
Functionality, 6
Server, 11
S7
Client, 121
Configuration, 130
DATA-BASE, 128
Functionality, 121
Performance, 126
Server, 128

Woodhead
SEND, 18
Server
S5, 11
S7, 128
TI, 84
Status
S5, 72
S7, 156
TI, 115
Supported variables, 6, 78, 121
SYNCHRON, 18, 36
TF, 36
TI
Client, 78
Configuration, 85
DATA-BASE, 84
Functionality, 78
Performance, 82
Server, 84
Usable functions S5
Cyclic mode, 45
Deferred mode, 44
Wait mode, 44
Usable functions S7
Cyclic mode, 143
Deferred mode, 142
Wait mode, 142
Usable functions TI
Cyclic mode, 96
Deferred mode, 95
Wait mode, 95

Industrial Ethernet On PC2000ETH (ISO Layer 4) : Woodhead Woodhead

Uploaded by

Copyright:

Available Formats

Industrial Ethernet On PC2000ETH (ISO Layer 4) : Woodhead Woodhead

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Industrial Ethernet On PC2000ETH (ISO Layer 4) : Woodhead Woodhead

Uploaded by

Copyright:

Available Formats

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

a product of Woodhead Software & Electronics

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

2. - Simatic® S5 (READ/WRITE S5 and TF Messaging) ...................3

3. - Simatic® TI505 Texas (READ/WRITE S5 Messaging) ..............66

4. - Simatic® S7 (S7 Protocol) ....................................................... 106

5. - Glossary of terms .................................................................... 143

6. - Index ......................................................................................... 144

Industrial Ethernet on PC2000ETH (ISO Layer 4) •i• Table of contents

applicom® Industrial Ethernet functionality against OSI model

Industrial Ethernet on PC2000ETH (ISO Layer 4) •1• - Generalities

Functionality Industrial Ethernet supported by applicom®:

• S5 READ/WRITE messaging (Client, Server).

Industrial Ethernet on PC2000ETH (ISO Layer 4) •2• - Generalities

2. - Simatic® S5 (READ/WRITE S5 and TF

- Industrial Ethernet client

Siemens applicom® Type of exchange Corresponding applicom®

MB v v Read bytes READBYTE

MB v v Read packed bytes READPACKBYTE, READDIFBYTE

MW v v Read words READWORD, READDIFWORD

MW v v Read BCD words READWORDBCD

MD v v Read double words READDWORD, READDIFDWORD

E v.w v*8+w Read input bits READPACKIBIT, READDIFIBIT

EB v v Read input bytes READIBYTE

EB v v Read packed input bytes READPACKIBYTE, READDIFIBYTE

EW v v Read input words READIWORD, READDIFIWORD

A v.w v*8+w Read output bits READPACKQBIT, READDIFQBIT

AB v v Read output bytes READQBYTE, READDIFQBYTE

AB v v Read packed output bytes READPACKQBYTE, READDIFQBYTE

AW v v Read output words READQWORD, READDIFQWORD

HTB messaging (READ/WRITE)

Object Maximum quantity in read / write

Object Maximum quantity in read / write

- Maximum number of variables per exchange with PCDDE

HTB messaging (READ/WRITE)

Object Maximum quantity in read / write

Object Maximum quantity in read / write

HTB messaging (READ/WRITE)

Object Maximum quantity in read / write

Object Maximum quantity in read / write

Supported requests Type of data in Addresses in Corresponding

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

x : DB n° (1 to 255) (DB0 forbidden)

Maximum number of variables per exchange:

• The PLC processors are used less.

Local read TSAP of server

Local write TSAP of server

Industrial Ethernet on PC2000ETH (ISO Layer 4) • 10 • - Simatic® S5 (READ/WRITE S5 and TF Messaging)

Address « Access status words » in DATA-BASE

Client PLC coupler configuration in the field:

1st access status word AP00-vvv

Industrial Ethernet on PC2000ETH (ISO Layer 4) • 11 • - Simatic® S5 (READ/WRITE S5 and TF Messaging)

Client PLC coupler configuration in the field:

1st access status word AP00-vvv

Industrial Ethernet on PC2000ETH (ISO Layer 4) • 12 • - Simatic® S5 (READ/WRITE S5 and TF Messaging)

Server equipment configuration

Industrial Ethernet on PC2000ETH (ISO Layer 4) • 13 • - Simatic® S5 (READ/WRITE S5 and TF Messaging)

Ethernet address of the equipment

Remote read TSAP

• for bits in a DB DB x D y.z x4096+y16+z