Porovnávané verzie

Kľúč

  • Tento riadok sa pridal
  • Riadok je odstránený.
  • Formátovanie sa zmenilo.

...

Kotva
typy_verzie
typy_verzie
Supported device types and versions

...

This protocol supports a data reading/writing from the control PLC machines Siemens SIMATIC:

  • types S7-300 and S7-400 equipped by an ethernet interface for the communication S7 ISO over TCP communication .
  • types S7-1200, S7-1500
  • Siemens LOGO
  • Siemens Microbox

Note: communication via Profinet/Profibus adapter ACCON-NetLink-PRO compact produced by company DELTALOGIC has been verified. Communication with multiple S-300 series PLCs on Profibus worked after firmware upgrade of adapter to version V2.54 (31. march 2015) with adapter's BIOS version V2.39 (7. June 2011). When the adapter's firmware was version V2.37 (8. august 2011), communication could not be correctly established.
Note: communication with PLC Siemens LOGO was tested. A part of memory that is accessible for reading/writing is the V area that which is seen as DB1.
Note: the protocol has a "big-endian" data representation.

...

When a TCP Redundant communication line is configured, you can configure an IP address and port of a backup device. If a communication process lost the connection or is unable to connect to the device, it will switch periodically between the configured devices. KOM process tries to connect to a primary device at first.
Note: Multiple IP addresses of primary/backup device devices can also be configured (separated by commas or semicolons).

...

ParameterMeaningUnit / sizeDefault value
Kotva
rack
rack
Rack
Siemens Simatic rack number. Rack 0 is most often used.
Note: when using the ACCON-NetLink-PRO compact adapter, the Rack/Slot parameters must be set so that the MPI address of the S7 with which the D2000 KOM process communicates is equal to 32 * Rack + Slot. It is therefore necessary to create a separate line with specific Rack/Slot values for each S7.
0 to 70
Kotva
slot
slot
Slot
Siemens Simatic slot number. Slot 2 is most often used.0 to 310

Kotva
s7sub1
s7sub1
S7 Subnet ID-part 1 (hex)

S7 subnet address sent as a part of Remote TSAP if parameter Use long TSAP is set to True0x0 to 0xFFFF0

Kotva
s7sub2
s7sub2
S7 Subnet ID-part 2 (hex)

S7 subnet address sent as a part of Remote TSAP if parameter Use long TSAP is set to True0x0 to 0xFFFF0

Kotva
us
us
 Use Secondary

The parameter allows the use of redundant PLCs, which may differ in the settings of some parameters (Rack, Slot, S7 Subnet ID).

If its value is True, the primary and secondary parameters are used alternately when connecting to the PLC using the specified IP addresses.

-False

Kotva
conres
conres
Connection Resource (hex)

Connection resource, it enters as MSB byte to the calculation of the value of Remote TSAP at initialization of ISO Connection-request.
See the description of parameter Use long TSAP.
Note: in the specific case, when two systems (one of them D2000) needed to communicate with S7-300, they each had to have a different Connection resource, otherwise after sending the initial sequence of D2000 KOM process, the connection broke:

/TSK1/Sending CR-TPDU: CLASS=0, SRC-REF=0x0001, TPDU size=1024, SRC-TSAP=10-00, DST-TSAP=03-02
/TSK1/OUT-<03><00><00><16><11><E0><00><00><00><01><00><C0><01><0A><C1><02><10><00><C2><02><03><02>
recv error '10.94.11.237:102 (handle: 2888, objId: 2563271)' - WSA_ECONNRESET [ 10054] Task: L.N337-S7ExecTsk/TSK1/

After changing the Connection resource from 3 to 2, the communication started working.

Note: according to Siemens documentation, the Connection Resource can be:

  • 0x01 - PG connection (intended for programming)
  • 0x02 - OP connection (designed for operator panel)
  • 0x03 - Other (another purpose, can be used for multiple connections)
  • 0x10..0xDF - Connections with static or dynamic connection process (various purposes, each usable for one configured connection)
  • 0xFD - S7 basic communication (typically connections from CPU to another module within the subnet)
0x0 to 0xFF3
Kotva
ltsap
ltsap
Local TSAP (hex)
ISO Local TSAP (Transport Service Local Point).  Source TSAP value during the initialization of ISO Connection-request.
See the description of parameter Use long TSAP.
0x0 to 0xFFFF0x1000
Kotva
srcref
srcref
Source Reference
ISO Source Reference. Value of SRC-REF during the initialization of ISO Connection-request.0 to 655351
Kotva
ult
ult
Use long TSAP
Enables a long format of local and remote TSAP which is sent during the connection setup phase.
Short TSAP is 2 bytes long.
Short local TSAP has the following format:Short remote TSAP has the following format:Long local TSAP is 28 bytes long. The last 2 bytes are higher and lower byte of parameter Local TSAP
Full remote TSAP is 28 bytes long and it contains:
-False
Kotva
mpiaddr
mpiaddr
MPI/Profibus Address
MPI/Profibus address sent as a part of Remote TSAP if parameter Use long TSAP is set to True0 to 1261

Kotva
tpdus
tpdus
ISO TPDU Size Variable Parameter

The maximum required size of ISO TPDU. The parameter value the initialization of ISO Connection-request.8192, 4096, 2048, 1024, 512, 256 or 128 bytes1024 bytes
Kotva
pnj
pnj
Nr. of Parallel Network Threads
Maximum parallel communication threads. Increase the value if there is a demand for more data read from the device in a shorter time.1 to 41
Kotva
ct
ct
Cycle Time
The required time of one data reading cycle.ms1000 ms
Kotva
wt
wt
Message Timeout
Maximal wait time on a reply from the device.ms2500 ms
Kotva
imd
imd
Inter Message Delay
Delay before sending a data request. When a high data transfer rate is required, set 0 ms.sec.ms20 ms
Kotva
rd
rd
Reconnect Delay
Delay before reconnection to the device if the connection has failed or some communication error has occurred.sec.ms2 sec
Kotva
cet
cet
Connection Error Timeout
When Timeout passes and communication error occurs in all threads, a communication error status is set on the stations. The FALSE state is set on the communication line.sec.ms20 sec

Kotva
pdu
pdu
S7 PDU Size

Maximum PDU in bytes at S7 communication with the device.240, 480, 960 bytes480 bytes

Kotva
tnd
tnd
Tcp No Delay

Setting "Tcp No Delay" parameter causes the low-level socket option TCP_NODELAY to be set, thus turning off the default packet coalesce feature.-False
Kotva
nvd
nvd
Debug Values
Activates debug info about the received values of I/O tags. Use this parameter only when communication must be debugged because it highly uses CPU and slows down the communication.YES/NONO
Kotva
iopd
iopd
Debug I/O Binary Packets Info
Activates debug info about the binary content of packets. Use this parameter only when communication must be debugged because it highly uses CPU and slows down the communication.YES/NONO
Kotva
rdd
rdd
Debug Requests Info
Activates basic debug info about requested data.YES/NOYES
Kotva
rad
rad
Debug Answers Info
Activates basic debug info about received packets.YES/NOYES

...