Home › Technical articles

Đọc bằng tiếng Việt

Ignition and Siemens S7-1200, S7-1500: Siemens drivers, the Enhanced driver, PUT/GET and optimized blocks

TDL Industrial Automation · Last updated:

From the Ignition 8.1 and 8.3 user manuals: the four absolute-only Siemens drivers and the Siemens Enhanced Driver with symbolic addressing from 8.3.0, what to set on S7-1200 and S7-1500 (PUT/GET, Full access, Optimized block access), port 102, rack and slot, address syntax, limits and the 8.1 to 8.3 differences.

Ignition reads Siemens S7-300, S7-400, S7-1200 and S7-1500 PLCs over TCP/IP with the S7 protocol, through drivers of its OPC UA module. Ignition 8.3 offers two choices: the Siemens drivers, which use absolute addresses only, and the Siemens Enhanced Driver, added in 8.3.0, which can also browse S7-1200 and S7-1500 tags by name and read optimized data blocks. Below: settings, address syntax and PLC requirements from the Ignition 8.1 and 8.3 user manuals, and where the two versions differ. The same topic for Allen-Bradley: Ignition Logix driver.

Siemens S7 PLCs to Ignition: three documented pathsThree columns, top to bottom. Column 1: S7-300, S7-400, S7-1200 and S7-1500 through the Siemens drivers of the Siemens Driver module, absolute addresses only, S7 protocol over TCP port 102; on S7-1200 and S7-1500 Optimized block access off, Full access and PUT/GET permitted. Column 2: the Siemens Enhanced Driver, from 8.3.0; S7-1200 and S7-1500 in Symbolic mode need only read access to read and browse; S7-300 and S7-400 use Absolute only. Column 3: some S7-1200 and S7-1500 devices have an onboard OPC UA server that Ignition connects to over OPC UA instead of a Siemens driver. All three end in the OPC UA module of the Ignition Gateway. Based on the Ignition 8.1 and 8.3 user manuals.Siemens S7 PLCs to Ignition: three documented paths1 · SIEMENS DRIVERS2 · ENHANCED DRIVER3 · OPC UAS7-300, S7-400, S7-1200and S7-1500S7-1200/1500:Optimized block access off,Full access, PUT/GET permittedS7-1200, S7-1500(Symbolic)read access to read andbrowse, write access to writeSome S7-1200, S7-1500onboard OPC UA serverenabled on the PLCS7-300, S7-400, S7-1200,S7-1500 driversabsolute addresses only,no browsing ·S7 over TCP, port 102Siemens Enhanced Driverfrom 8.3.0 · browsing,optimized data blocks ·S7-300/400 Absolute only ·port 102OPC UA connectionIgnition connects to the PLC'sOPC UA server · tags browsedIgnition Gateway · OPC UA moduletags as [device]address or picked by browsing; 8.1 has the Siemens Driver module onlyBased on Inductive Automation, Ignition 8.1 and 8.3 user manuals (read 15 November 2026). PLC-side settingsonly as the manuals list them. Figure: drawn by TDL.
Figure 1: Siemens S7 PLCs to Ignition: three documented paths. On a phone, swipe sideways to see the whole figure.

1. Two driver modules

The 8.3 manual lists the Siemens drivers by the module that provides them:

Driver Module PLCs Addressing
S7-300, S7-400, S7-1200 and S7-1500 drivers Siemens Driver module one driver per family absolute only; tags cannot be browsed
Siemens Enhanced Driver Siemens Enhanced Driver module S7-300, S7-400, S7-1200, S7-1500 absolute for all four; symbolic, with browsing and optimized data blocks, for S7-1200 and S7-1500

The 8.1 manual lists only the Siemens Driver module. The 8.3 release notes add the Enhanced driver in 8.3.0 and support for S7-1200 G2 PLCs on it in 8.3.3. The 8.3 overview names what decides the choice: the Enhanced module is not included in a Platform license; the Siemens Driver module runs on Windows, Linux, Mac and ARM; the Enhanced module runs on Windows, Linux/x64 and Linux/ARM, not on Mac.

Both versions note that some S7-1200 and S7-1500 devices have an onboard OPC UA server; once it is enabled, Ignition can connect over OPC UA and browse tags instead of using a Siemens driver.

2. What has to be set on the PLC

The manual lists requirements for S7-1200 and S7-1500 only. With the Siemens drivers, and with the Enhanced driver in Absolute mode:

  • only global data blocks can be accessed;
  • timer (TM) and counter (CT) areas cannot be read or written;
  • the Optimized block access attribute must be turned off;
  • under Protection & Security, Full access (no protection) and Permit access with PUT/GET communication must be selected.

The manual adds that this may need the hardware configuration compiled again and downloaded, and that turning off optimized access on the blocks being read may make reads more reliable.

With the Enhanced driver in Symbolic mode, the two Protection & Security options are not needed: read access is enough to read and browse, and write access is still needed to write.

PLC family Driver Protocol What to set on the PLC, per the manual
S7-300, S7-400 S7-300 or S7-400 driver, or Enhanced in Absolute mode S7 over TCP/IP, port 102 nothing listed
S7-1200, S7-1500 S7-1200 or S7-1500 driver, or Enhanced in Absolute mode S7 over TCP/IP, port 102 Optimized block access off; Full access (no protection); PUT/GET permitted; global DBs only
S7-1200, S7-1500 Enhanced in Symbolic mode S7 over TCP/IP, port 102 read access to read and browse, write access to write
some S7-1200, S7-1500 OPC UA connection, no Siemens driver OPC UA onboard OPC UA server enabled

3. Creating the device connection

In 8.3, on the Gateway webpage under Connections > Devices > Connections: Create Device Connection, choose the driver, enter a name and the hostname. The Enhanced driver also asks for Device Type and Address Type; S7-300 and S7-400 must use Absolute. In 8.1 the page is Config > OPC UA > Device Connections, Create new Device. The device shows Disconnected, then Connected. The 8.3 pages add that both modules need the OPC UA module installed and enabled; otherwise they show Faulted Missing Dependency.

Setting Siemens drivers Siemens Enhanced Driver
Port 102 102
Timeout 2,000 ms 3,000 ms
Rack Number 0 0
CPU Slot Number / Slot Number 2 0
PDU Size 240 (240 to 960 by device; larger helps only if the CPU supports it) not listed
Reconnect After Consecutive Timeouts true not listed
Optimize Writes not listed batches tag writes
Secure Connection Mode not listed TLS: REQUIRED, PREFERRED (default) or DISABLED
Password not listed None, Embedded or Referenced

Secure Connection Mode replaced Force Secure Connection in 8.3.4. On upgrade, an enabled Force Secure Connection becomes REQUIRED and a disabled one PREFERRED.

4. Absolute addresses

The Siemens drivers cannot browse, so each tag is an OPC tag with the OPC Item Path [device]address, for example [S71200]IW0. An address is an area, a data type and an offset:

  • Areas: DBn (data block), I (inputs), Q (outputs), M (flags), T (timers), C (counters).
  • Types: X bit, B byte, C char, W word, I int, D dword, DI dint, REAL, STRING or STRING.LEN; also LI (LInt, S7-1500 only), LREAL (S7-1200 and S7-1500) and DT (Date_And_Time, S7-300, S7-400 and S7-1500). The 8.1 release notes added LREAL, LINT and DateTime in 8.1.29.

The manual's examples include IB0 (byte 0 of the inputs), DB500,DI8 (a DInt at offset 8 of DB500), IX20.3 (bit 3 of input byte 20), ISTRING24.50 (a 50-character string from offset 24), and T0 and C0 (no data type for timers and counters).

Offsets are absolute: IW0 and IW1 share a byte, so two consecutive words are IW0 and IW2. Bits run from 0 to 7. Strings use the S7 string format, up to 210 characters. Timers are converted between S5 time and milliseconds, counters between BCD and UInt16. The driver does not support Ignition's DateTime tag type for DT values; the manual suggests reading each byte into its own tag and joining them in an expression tag. The driver pages list no byte or word order setting.

The Enhanced driver in Absolute mode accepts the same syntax, plus a form close to TIA Portal with arrays: DB500.DBREAL10 (a REAL at offset 10), DB1.DBX9.7 (bit 7 at offset 9), MD5[2] (two DWords from offset 5), DB500.STRING255[7] (up to 7 characters from offset 255). Its table maps S7 types to OPC UA types, for example REAL to Float, LREAL to Double, DT to DateTime, and DATE to a UInt16 count of days since 1 January 1990.

For many tags, the manual points to tag import and export with a spreadsheet. The 8.3 tag import reads CSV, JSON and XML files; the CSV format carries no alarm configuration.

5. Symbolic addressing and browsing

With Address Type set to Symbolic, S7-1200 and S7-1500 tags can be browsed in the Designer: the Devices icon next to the OPC Item Path in the Tag Editor opens the OPC UA server to pick the tag. Since 8.3.7 a symbolic connection also offers Export PLC Symbols in its menu. Each request carries at most 100 items; larger subscriptions are split into several requests that the driver handles at the same time, and the 8.3.10 notes apply this cap to S7-1200 too.

6. Limits and diagnostics

The 8.3 Enhanced driver page lists:

  • a limit of 250 device connections;
  • a known issue on S7-1500 firmware 4.0.0 and 4.0.4 that can drop the connection, resolved in PLC firmware 4.1.2;
  • from 8.3.3, GLIBC 2.34 or newer on x64 (2.17 on ARM), which rules out Ubuntu 20.04, Debian 10 and Debian 11 on x64;
  • secure connections on a clean Linux install need libssl.so and libcrypto.so symlinks, which the Docker images include.

Every device connection has diagnostic tags such as Connected, State and Status, and a Sampling folder with throughput metrics, added for the Enhanced driver in 8.3.9. Reading them, OverloadFactor included: Logix driver article.

7. Ignition 8.1 and 8.3 side by side

Topic 8.1 8.3
Siemens drivers Siemens Driver module, four drivers the same, plus the Siemens Enhanced Driver
Browsing not with the drivers; the PLC's OPC UA server instead Enhanced driver in Symbolic mode, or the PLC's OPC UA server
Where the device is created Config > OPC UA > Device Connections Connections > Devices > Connections
Port setting under Advanced under Connectivity
Defaults, address syntax and PLC requirements of the Siemens drivers as in 8.3 as in 8.1

Before moving a gateway with Siemens devices to 8.3: Ignition 8.1 to 8.3 upgrade.

What we check first

This is TDL's practice, not an Inductive Automation requirement.

  • We take a backup of the PLC project before any change on the PLC side.
  • We note the CPU family, its firmware and the Ethernet port the gateway will use, and read rack and slot from the hardware configuration; the two drivers do not share a slot default.
  • We trace the network path from the gateway to the PLC: switch, VLAN and any firewall that must pass TCP port 102. Zones and conduits: IEC 62443.
  • We ask the plant whether full access, PUT/GET and non-optimized blocks are allowed, since they change the PLC's protection settings and may need a download. Where they are not, the documented alternatives are Symbolic mode and the PLC's OPC UA server.
  • We size the polling load: how many tags at which tag group rate, and the 100-item cap per request on the Enhanced driver.
  • We agree tag names and the address list (DB numbers, offsets, data types) with the PLC programmer, and keep that list in the spreadsheet used for the tag import.

How TDL approaches it

TDL Industrial Automation is an Ignition Certified Integrator. Our public Siemens project pages are migrations: on Vietsovpetro's LP compressor (2018) TDL replaced the Siemens S5 control system with ControlLogix and PanelView HMI, and at SEHC VD5 (2026) failed Siemens PLCs, HMIs and converters were replaced with a CompactLogix 5370 and brought back into the FMCS SCADA. Services: Connecting existing PLCs and equipment to SCADA, Ignition SCADA integrator in Vietnam and GE Fanuc, Siemens and older ControlLogix migration. Other PLC makes on Ignition: Mitsubishi and Omron drivers; all platforms side by side: PLC drivers compared.

Frequently asked questions

Which Ignition driver connects to an S7-1200 or S7-1500?

The S7-1200 or S7-1500 driver of the Siemens Driver module, with absolute addresses only, or in Ignition 8.3 the Siemens Enhanced Driver, which adds symbolic access and browsing. Some S7-1200 and S7-1500 devices also have an onboard OPC UA server that Ignition can connect to instead.

Does Ignition need PUT/GET enabled on the S7-1200 or S7-1500?

For absolute addressing, yes: the manual asks for Full access (no protection), Permit access with PUT/GET communication and Optimized block access turned off. In Symbolic mode of the Enhanced driver these protection options are not needed; read access is enough to read and browse, and write access is needed to write.

Can Ignition browse the tags of a Siemens PLC?

Not with the Siemens drivers: their tags are created by hand or imported. In 8.3 the Enhanced driver browses S7-1200 and S7-1500 tags in Symbolic mode, and a PLC with an enabled onboard OPC UA server can be browsed over OPC UA.

Why do IW0 and IW1 return overlapping values?

Offsets are absolute byte offsets, so IW0 and IW1 share a byte. Two consecutive words that do not overlap are IW0 and IW2.

Which port, rack and slot does Ignition use by default?

Port 102 and rack 0 for both drivers. The CPU slot defaults to 2 on the Siemens drivers and to 0 on the Siemens Enhanced Driver.

Sources

Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
Ignition (Inductive Automation) Connecting existing equipment to SCADA