The Siemens drivers in Ignition support basic connections to S7 devices. Ignition connects to these PLCs via TCP/IP using the S7 protocol. Similar to Modbus and some Allen Bradley connections, the Siemens S7 devices do not support Tag browsing. You can create S7 Tags manually in Ignition, or use Ignition's Tag import/export to create all of your Tags quickly in Excel or another spreadsheet program. Currently, Ignition has drivers for the following Siemens PLCs:
Considerations for 1200 and 1500 Devices
The following considerations and configurations changes must be made when using the S7-1200 and S7-1500 drivers:
- Only global DBs can be accessed.
- The optimized block access must be turned off.
- The access level must be "full" and the "connection mechanism" must allow GET/PUT.
- Reads and Writes can not be used in TM/CT areas.
|Name||The name of the device connection|
|Description||A description for the device connection. The description will appear on the Devices page on the Gateway.|
|Enabled||Whether or not the connection is active. Disabling this setting terminates communication with the device.|
The hostname or IP address of the device.
The local address to connect from when establishing a TCP connection. If left blank, then the driver will simply pick an available address.
|Timeout||The request timeout, specified in milliseconds. The default is 2,000.|
|Port||The port to use when connecting to the device. The default is 102.|
|PDU Size||Number of bytes to fit into PDU block of a single packet. Increasing this number can improve request throughput only if the processor supports a higher PDU Size. Varies from 240 and up to 960 depending on the device. The default is 240.|
|Rack Number||The number of the rack that the device is positioned in. The default is 0.|
|CPU Slot Number||The slot number assigned to the CPU. The default is 2.|
|Reconnect After Consecutive Timeouts||After several consecutive timeouts, the device connection will attempt to reconnect to the device. This setting determines how many consecutive timeouts must occur before reconnecting.|