Skip to main content
Version: 8.1


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:

  • S7-300
  • S7-400
  • S7-1200
  • S7-1500

Considerations for 1200 and 1500 Devices​

The following considerations and configurations changes must be made when using the S7-1200 and S7-1500 drivers.

  1. Only global DBs can be accessed.
  2. The optimized block access must be turned off.
  3. The access level must be "full" and the "connection mechanism" must allow GET/PUT.
  4. Reading and writing is not supported for timer (TM) and counter (CT) areas.

Connecting to a Siemens Device​

Inductive University

Connecting to S7 Devices

Watch the video

  1. Go to the Config section of the Gateway Webpage.
  2. Scroll down and select OPC UA > Device Connections.
  3. On the Devices page, click on Create new Device.
  4. On the Add Device Step 1: Choose Type page, select Siemens S7-1200, and click Next.
  5. There are four modules to choose from:
    • Siemens S7-1500: Connects to Siemens S7-1500 PLCs over Ethernet.
    • Siemens S7-1200: Connects to Siemens S7-1200 PLCs over Ethernet.
    • Siemens S7-300: Connects to Siemens S7-300 PLCs over Ethernet.
    • Siemens S7-400: Connects to siemens S7-400 PLCs over Ethernet.
  6. On the New Device page, leave all the default values and type in the following fields:
    • Name: S71200
    • Hostname: type the IP address, for example
  7. You can check the box for Show advanced properties? to see the additional settings, but you can keep all the defaults.
  8. Click Create New Device. The Devices page is displayed showing the Siemens device is successfully created and added to Ignition. The Status will show as Disconnected and then Connected.

Siemens devices do not support browsing, therefore you can not browse the tags by going to the OPC Connections > Quick Client in the Configure section of the Gateway. To see and browse the tags, you need to create the tags manually as described in the Configuring Siemens Addressing section.

Configuring Siemens Addressing​

Inductive University

About Siemens Addressing

Watch the video

The S7 protocol does not support tag browsing. Therefore, you must configure all tags in the Designer. This can be done either manually, as needed, or by importing bulk using the tags CSV import functionality.

Manually Specify Each Address​

  1. From the Designer, in the Tag Browser, click the Add (Add Icon) icon.

  2. Select New Standard Tag, then OPC Tag.

    Manually Specify Each Address Step 2

  3. In the Tag Editor window, as an example, you can set the following values:

    • Name: Tag
    • Data Type: Int4
    • OPC Server: choose Ignition OPC-UA Server with the edit button on the right.
    • OPC Item Path: [S71200]IW0, the S71200 device name goes in the square brackets then you give the address to PLC which in this example is IW0 (Word at Offset 0 in the Inputs area). The Address Syntax section explains how you can construct these addresses.
  4. Click OK. Now you can see the Temp tag in the Tag Browser.

Address Syntax​

You need a device name plus a tag address to create a tag. The device name is a known, but the tag address needs to be configured. Once you have both the device name and tag address you enter them in the in the OPC Item Path field of the Tag Editor window using the [device_name]address format, where device_name is the name of the device and address is the configured tag address, which is described here.

Tag addresses are made up of three different components: Area, Data Type, and Offset.

Area Syntax​


Data Type Syntax​

Data TypeSyntaxSignedness
New in 8.1.29

Note: Due to limitations on Siemens devices, this data type is only supported on the following devices:
  • S7-300
  • S7-400
  • S7-1500
New in 8.1.29

Note: Due to limitations on Siemens devices, this data type is only supported on the following device:
  • S7-1500
New in 8.1.29

Note: Due to limitations on Siemens devices, this data type is only supported on the following devices:
  • S7-1200
  • S7-1500
Extracting Bytes in DATE_AND_TIME Items

The Siemens driver does not support Ignition tag's DateTime type. In these cases it is recommended to extract each byte in the Siemens DATE_AND_TIME value item, storing each into a separate Ignition tag. Then use an expression tag to combine each byte into a human readable datetime.


// The following assumes each byte of the DATE_AND_TIME value is under a tag named like "BASIC_DATA_AND_TIME", and that each tag is a String type.

"20" + //First part of the year, assuming in 21st century
toHex({[.]BASIC_DATE_AND_TIME[0]}) + β€œ-” + //Second part of the year, reading from an Ignition tag.
numberFormat(toHex({[.]BASIC_DATE_AND_TIME[1]}), β€œ00”) + β€œ-” + //Month
numberFormat(toHex({[.]BASIC_DATE_AND_TIME[2]}), β€œ00”) + β€œ-” + //Day
numberFormat(toHex({[.]BASIC_DATE_AND_TIME[3]}), β€œ00”) + β€œ:” + //Hours
numberFormat(toHex({[.]BASIC_DATE_AND_TIME[4]}), β€œ00”) + β€œ:” + //Minutes
numberFormat(toHex({[.]BASIC_DATE_AND_TIME[5]}), β€œ00”) + β€œ:” + //Seconds
numberFormat(fromBinary(left(numberFormat(toBinary({[.]BASIC_DATE_AND_TIME[6]} + {[.]BASIC_DATE_AND_TIME[7]}), β€œ0000000000000000”), 12)), β€œ000”) + " " + //Milliseconds, it includes the first 4 bits of byte 7
case( //Day of the week, last 4 bits of byte 7
right(numberFormat(toBinary({[.]BASIC_DATE_AND_TIME[7]}), β€œ00000000”), 4),
β€œ0000”, β€œSunday”,
β€œ0001”, β€œMonday”,
β€œ0010”, β€œTueday”,
β€œ0011”, β€œWednesday”,
β€œ0100”, β€œThursday”,
β€œ0101”, β€œFriday”,
β€œ0111”, β€œSaturday”,
β€œError - No Day Found”)

Area + Data Type + Offset Examples​

To form an address, you combine syntax for the desired Area and Data Type with an Offset into that area.

IB0Byte at Offset 0 in the Inputs area.
IW0Word at Offset 0 in the Inputs area.
DB500,DI8DInt at Offset 8 in DataBlock 500.
ISTRING24.50A String of length 50 starting at offset 24 in the Inputs area.
IX20.3Bit 3 of the Byte at Offset 20 in the Inputs area.
T0Timer at offset 0 (No DataType is specified for Timers).
C0Counter at offset 0 (No DataType is specified for Counters).


It is important to note that offsets are absolute. IW0 and IW1 share a byte. To get two consecutive, non-overlapping words you need to address IW0 and IW2.


Bits are addressed by using the Bit data type (X) and appending .bit to the end, where bit is in the range [0-7]. When addressing a bit at a given offset, that offset is always treated as a byte.


Strings are assumed to be in the S7 string format and have a max length of 210.


Timers are scaled up to a DWord and converted from S5 time format so they can represent the time in milliseconds without requiring any multipliers. When you write to a timer it is automatically converted from milliseconds into S5 time format for you. A data type is not specified when accessing timers.


Counters in the PLC are stored in BCD. The driver automatically converts to/from BCD for you and exposes any counter Tags as UInt16 values. A data type is not specified when accessing counters.

Device Settings​


NameThe name of the Device Connection.
DescriptionA description for the Device Connection. The description will appear on the Devices page on the Gateway.
EnabledWhether or not the connection is active. Disabling this setting terminates communication with the device.


HostnameThe hostname or IP address of the device.
Local Address​
New in 8.1.8
The local address to connect from when establishing a TCP connection. If left blank, then the driver will simply pick an available address.
TimeoutThe request timeout, specified in milliseconds. The default is 2,000.


PortThe port to use when connecting to the device. The default is 102.
PDU SizeNumber 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 NumberThe number of the rack that the device is positioned in. The default is 0.
CPU Slot NumberThe slot number assigned to the CPU. The default is 2.
Reconnect After Consecutive TimeoutsAfter several consecutive timeouts, the Device Connection will attempt to reconnect to the Device. Default is true.