...
| Kotva | ||||
|---|---|---|---|---|
|
...
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
- types 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 the firmware upgrade of the adapter to version V2.54 (31. march 2015) with the adapter's BIOS version V2.39 (7. June 2011). When the adapter's firmware was version V2.37 (8. august 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.
...
- Communication line category: TCP/IP-TCP, TCP Redundant.
- IP address (addresses) is set according to a network configuration of a specific Siemens SIMATIC device.
- The port number is 102 (according to specification RFC 1006).
- The line number is not used, set on to 1.
When the a TCP Redundant communication line is set as TCP Redundant configured, you can configure an IP address and port of a backup device. If a communication process lost loses the connection or is unable to connect to the device, it will switch periodically between the configured devices. The 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).
...
Note: if all of the stations are in StOFF mode (or in simulation), the TCP connection will be closed. Thus it is possible to control TCP communication from the event using an STSTAT tell command.
| Kotva | ||||
|---|---|---|---|---|
|
...
A
...
A dialog window of communication line configuration - Protocol parameters tab.
They influence some optional protocol parameters.
...
See the description of parameter Use long TSAP.
| Parameter | Meaning | Unit / size | Default value | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Siemens Simatic rack number. | 0 to 7 | 0 | ||||||
| Kotva | |||||||||
| slot | slot | Siemens Simatic slot number. | 0 to 31 | 0 | |||||
| Kotva | |||||||||
| s7sub1 | s7sub1 | S7 subnet address sent as a part of Remote TSAP, if parameter Use long TSAP is set to True | 0x0 to 0xFFFF | 0 | |||||
| Kotva | |||||||||
| s7sub2 | s7sub2 | S7 subnet address sent as a part of Remote TSAP, if parameter Use long TSAP is set to True | 0x0 to 0xFFFF | 0 | |||||
| Kotva | |||||||||
| us | us | 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 | 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. It is also necessary to set "RFC Routing over CPs with TSAP" to ON in the adapter web interface. | 0 to 7 | 0 | ||
| Siemens Simatic slot number. Slot 2 is most often used. | 0 to 31 | 0 | ||||||
| S7 subnet address sent as a part of Remote TSAP if parameter Use long TSAP is set to True | 0x0 to 0xFFFF | 0 | ||||||
| S7 subnet address sent as a part of Remote TSAP if parameter Use long TSAP is set to True | 0x0 to 0xFFFF | 0 | ||||||
| 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 | ||||||
| Connection resource, it enters as MSB byte to the calculation of the value of Remote TSAP at initialization of ISO Connection-request. /TSK1/Sending CR-TPDU: CLASS=0, SRC-REF=0x0001, TPDU size=1024, SRC-TSAP=10-00, DST-TSAP=03-02 After changing the Connection resource from 3 to 2, the communication started working. Note: according to Siemens documentation, the Connection Resource can be:
| ||||||||
| Kotva | |||||||||
| conres | conres | 0x0 to 0xFF | 3 | ||||||
| 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 0xFFFF | 0x1000 | ||||||
| ISO Source Reference. Value of SRC-REF during the initialization of ISO Connection-request. | 0 to 65535 | 1 | ||||||
| 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:
Full remote TSAP is 28 bytes long and it contains:
| - | False | ||||||
| MPI/Profibus address sent as a part of Remote TSAP , if parameter Use long TSAP is set to True | 0 to 126 | 1 | ||||||
| The maximum required size of ISO TPDU. The parameter value the initialization of ISO Connection-request. | 8192, 4096, 2048, 1024, 512, 256 or 128 bytes | 1024 bytes | ||||||
| Maximum parallel communication threads. Increase the value if there is a request on demand for more data read from the device in a shorter time. | 1 to 4 | 1 | ||||||
| The required time of one data reading cycle. | ms | 1000 ms | ||||||
| Maximal wait time on a reply from the device. | ms | 2500 ms | ||||||
| Delay which is used before sending a data request. When a high data transfer rate is required, set 0 ms. | sec.ms | 20 ms | ||||||
| Delay before reconnection to the device if the connection has failed or some communication error has occurred. | sec.ms | 2 sec | ||||||
| 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.ms | 20 sec | ||||||
| Maximum PDU in bytes at S7 communication with the device. | 240, 480, 960 bytes | 480 bytes | ||||||
| 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 | ||||||
| Activates a debug info about the loaded 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/NO | NO | ||||||
| Activates a debug info about a 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/NO | NO | ||||||
| Activates a basic debug info about requested data. | YES/NO | YES | ||||||
| Activates a basic debug info about received packets. | YES/NO | YES |
...
- Communication protocol: Siemens SIMATIC S7 ISO over TCP.
- No station address, no protocol parameters on the station.
- The time parameter setting is ignored. See the line parameter Cycle Time.
- Time synchronization of the device is not supported.
| Kotva | ||||
|---|---|---|---|---|
|
...
| ; | Optional parameter. It disables the I/O tag from communication, stops the I/O tag address check when it is saved, and can be useful when the communication with the device is activated or debuggeduseful when the communication with the device is being developed or debugged. Note: Also an I/O tag with an address starting with %IGNORE will be ignored. | ||||||||
| S7:[connectionname] | Optional parameter. It does not contain any useful information but it is supported only because of backward compatibility with the Siemens SimaticNET OPC server. | ||||||||
| DB | Data block. S7 variable identifier from "Data block". | ||||||||
| DI | Instance data block. S7 variable identifier from " Instance data block". | ||||||||
| <no> | A number of "data block" number or "instance data block" number. | ||||||||
| <object> | Specification of block or area in S7 PLC. Possible values:
| ||||||||
| PQ | Peripheral Output ( Peripherie Ausgang, PA) | ||||||||
| M | Memory bit (F) | ||||||||
| C | Counter (Zähler, Z) - BCD coded integer numbers <0-999> | ||||||||
| T | Timer (Timer, T) - BCD coded time values from intervals <0.00-9.99>, <00.0-99.9>, <000-999>, <0000-9.9990> | ||||||||
| Kotva | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| szl | szl | System Status Lists (System-ZustandsListen, SZL) - lists with diagnostic information that are available on CPU family S7-300 and S7-400. Diagnostic information differs for various classes of PLC and details are described in manuals (e.g. System Software for S7-300/400 System and Standard Functions, Volume 1/2) Note: I/O tag S must be of TxtI type. |
| PE) | |||||||
| PQ | Peripheral Output ( Peripherie Ausgang, PA) | ||||||
| M | Memory bit (F) | ||||||
| C | Counter (Zähler, Z) - BCD coded integer numbers <0-999> | ||||||
| T | Timer (Timer, T) - BCD coded time values from intervals <0.00-9.99>, <00.0-99.9>, <000-999>, <0000-9.9990> | ||||||
| System Status Lists (System-ZustandsListen, SZL) - lists with diagnostic information that are available on CPU family S7-300 and S7-400. Diagnostic information differs for various classes of PLC and details are described in manuals (e.g. System Software for S7-300/400 System and Standard Functions, Volume 1/2) Note: I/O tag S must be of TxtI type. |
The data type of S7. It is not specified for T, C, and S objects.
| Identifier <type> | Description |
|---|---|
| X | Bit (boolean). Specify a bit number 0 to 7 - e.g. DB9,X8.3 |
| B BYTE | Byte (8 bits unsigned). |
| W WORD | Word (16 bits unsigned). |
| D DWORD | Double word (32 bits unsigned). |
| CHAR | Character (8 bits signed). |
| INT | Integer (16 bits signed). |
| DINT | Double integer (32 bits signed). |
| BCD | BCD-coded 2-byte number (0-9 999) |
| LBCD | BCD-kódované 4-byte number (0-99 999 999) |
| REAL | Floating-point number (32 bits according to IEEE754 standard). |
| LREAL | Long floating-point number (64 bits according to IEEE754 standard). |
| STRING | String. Specify the maximal length of the string. |
| CHARARR | An array of CHARs interpreted as a string. The array length must be specified. |
| DATE | Date, 2 bytes (the number of days since January 1st, 1990) |
| DT | Date and Time, 8 bytes in BCD format, millisecond accuracy |
| DTL | Date and Time, 12 bytes in BCD format, nanosecond accuracy Note: D2000 uses only a millisecond accuracy |
| TIME | Time (32 bits signed) in ms. Note: if the I/O tag is of the TiR type, it is necessary to ensure the conversion by configuring the linear conversion (A=0.001, B=0) on the Conversion tab |
| S5TIME | Double byte time - Simatic S5 format (0 - 9990 seconds with variable accuracy 0.01 - 10 seconds). Measured points of the type Ai/Ao, Ci/Co, TiR/ToR are supported. Note: An alternative to this data type is to use the "W" type and set the "Simatic S5Time" conversion |
| . | |
| TOD | Time of day (32 bits unsigned) in ms. |
Note: The CHARARR type is a D2000 extension that allows you to read/write an array of CHARs as a string. This type is not compatible with the Siemens SimaticNET OPC server addressing.
The difference between CHARARR and STRING is as follows:
- STRING - standard format of the S7 string, when there are 2 bytes in front of the string itself (maximum and current string length). For example, a 10-character STRING takes up 12 bytes.
- CHARARR - an array of characters, without a 2-byte header. For example, CHARARR with a length of 10 characters takes up 10 bytes.
- Byte offset (offset within a block, a number 0-65535)
- Byte offset.bit (only for the X data type, bit number in the range of 0 to 7)
- Byte offset.String length (only for the STRING data type, string length from 1 to 254 characters)
- Id.Index[.StringOffset[.StringLength]] - only for object S (system status list):
- Id and Index are 16-bit numbers in the range 0-65535 defining ID of specific system status list and index of the item in this list
- StringOffset and StringLength are byte offset (0..65535) and length (1..65535) of the substring in answer, which will be parsed as a value of I/O tag.
- DB10,W35
- DB8,X10.0
- DB1,REAL12
- DB5,STRING5.14
- DB5,CHARARR5.14
- T20
- C7
- MB11
- MDINT30
- QX3.7
Structured I/O tags are not supported for objects of type T (timers), C (counters), and S (system status lists) nor for data type STRING.
Note: All "items" elements are read at once. If e.g. 100 elements of type D (double word) are configured, it means reading of a block of 400 bytes. If a smaller size of the packet (S7 PDU size) is agreed on during the establishment of connection, reading of this I/O tag will not be performed and the trace file of the line will contain an error message. Agreed S7 PDU size is minimum of size offered by D2000 (parameter S7 PDU Size) and supported size of a specific device.
Note: the syntax of address when specifying the number of elements is compatible with Siemens S7 OPC server (e.g. S7:[MyPLC]DB120,INT1050, 24), which facilitates a simple transition from OPC communication to Siemens SIMATIC S7 ISO on TCP protokol protocol by configuring a new line, a new station and then changing the parent of I/O tags (e.g. via CSV or XML export and import).
Example of addresses:
- DB10,W35, 20 a block of 20 words will be read (i.e. 40 bytes) from addresses 35-54
- DB8,X10.0, 100 a block of 100 bits will be read (i.e. 13 bytes) from addresses 10-22
