Siemens TCP/IP Ethernet

Product Overview

The Siemens TCP/IP Ethernet driver works in conjunction with KEPServerEX to exchange data between OPC clients and Siemens S7-200, S7-300, S7-400, and S7-1200 PLCs using the TCP/IP Ethernet protocol. The driver talks directly to the S7 PLC using a standard PC network interface card, and does not require additional software packages or libraries. Specialized block read and write optimizations automatically increase the speed of many applications when using CP243, CP343, and CP443 communications processors.

Added a new setting called Maximum PDU Size. The driver and device negotiate the highest supported PDU size by starting at this defined setting and no higher. Available PDU sizes include 240, 480, and 960.

6.3.273.0

9/27/2017

Fixed an issue where atomic data types inside an array of structs were not generated when doing automatic tag generation (ATG).

6.2.460.0

7/6/2017

Added Chinese language support.

6.2.429.0

6/8/2017

Support for importing Siemens TIA Portal tags into the Siemens TCP/IP Ethernet driver.

Requires using the export files produced by the TIA Portal Exporter Utility. The installer for this utility is included with the Siemens TCP/IP Ethernet driver.

5.18.673.0

8/17/2015

Fixed an issue where validating invalid tag addresses with 16 or more continuous alpha characters could result in a crash of the Runtime. This could occur in two cases: after Auto Tag Generation from a device containing symbolic tags or if a client referenced tag names not defined in the server.

5.17.495.0

2/24/2015

Fixed an issue where tags of type 'Date' could result in other tag values not being updated. This only occurred with tags that were in the same block as the Date tag.

Added support for HEXSTRING data types.

5.15.585.0

7/22/2014

Enhanced Automatic Tag Generation support to include extended (non-ASCII) characters.

Fixed an issue where an uninitialized buffer could cause a buffer overflow and result in a crash.

Fixed an issue where an invalid data length in a response could cause a buffer overflow and result in a crash.

Fixed an issue where the driver would treat a WSAEWOULDBLOCK as an error when waiting to receive data. This could result in an error reported for a valid packet.

5.14.491.0

2/18/2014

Added a new S7-1500 model.

Added support for automatic tag generation from a Step 7 project file for S-400 and S-300 controllers.

5.12.140.0

6/18/2013

Added support for BOOL arrays.

5.10.205

11/13/2012

Added Applicom address syntax to provide both Byte and Word order control at the tag level.

Fixed a Read/Write issue introduced in 4.190 that can occur for S7-200 addresses utilizing the KT suffix.

Added Read/Write support for the S7 TIME data type as String for the following memory types: DB, I, E, Q, A, PI, PE, PQ, PA, M, and F.

Added write support for the S7 TIME_OF_DAY data type as String for the DB memory type.

Updated the Read/Write support for the S7 TIME_OF_DAY data type as String to include the following memory types: I, E, Q, A, PI, PE, PQ, PA, M, and F.

Updated the read support for the S7 DATE_AND_TIME data type as String or Date to include the following memory types: I, E, Q, A, PI, PE, PQ, PA, M, and F.

5.9.170

6/26/2012

Fixed an issue where the Byte Order (Big Endian or Little Endian) for a tag could unexpectedly change. This occurred when there were two or more devices under one channel that had tags pointing at the same address, but with a different Byte Order selected. This could result in an incorrect Byte Order for one or all of those tags.

Added support for the Date data type for the Siemens DATE_AND_TIME (DT) data block memory type.

What Is a Driver?

KEPServerEX is more than an OPC server—it's a connectivity platform for industrial automation and IoT. Simply download KEPServerEX, and then select from Kepware's library of more than 150 device drivers, client drivers, and advanced plug-ins to fit the communication requirements unique to your industrial control system.

A driver is a software component that enables KEPServerEX to meet the connectivity requirements of a specific device, system, or other data source. The driver handles all proprietary communications to the data source for KEPServerEX; the client interfaces handle all supported OPC, proprietary, and open standards connectivity to applications that monitor or control the devices.

Drivers may be licensed individually or in suites. Additional drivers can be licensed on demand as connectivity needs evolve.