Ignition reads Siemens
1. Two driver modules
The 8.3 manual lists the Siemens drivers by the module that provides them:
| Driver | Module | PLCs | Addressing |
|---|---|---|---|
| Siemens Driver module | one driver per family | absolute only; tags cannot be browsed | |
| Siemens Enhanced Driver | Siemens Enhanced Driver module | absolute for all four; symbolic, with browsing and optimized data blocks, for |
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
Both versions note that some
2. What has to be set on the PLC
The manual lists requirements for
- 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 over TCP/IP, port 102 | nothing listed | ||
| S7 over TCP/IP, port 102 | Optimized block access off; Full access (no protection); PUT/GET permitted; global DBs only | ||
| Enhanced in Symbolic mode | S7 over TCP/IP, port 102 | read access to read and browse, write access to write | |
| some |
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;
| 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 andS7-1500 ) and DT (Date_And_Time,S7-300 ,S7-400 andS7-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
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,
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
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
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
- Inductive Automation, Siemens, Siemens Drivers and Siemens Enhanced Driver, Ignition 8.3 user manual
- Inductive Automation, Siemens, Ignition 8.1 user manual
- Inductive Automation, Driver Modules (8.3) and Driver Modules (8.1)
- Inductive Automation, New in this Version (8.3) and New in this Version (8.1), release notes
- Inductive Automation, OPC UA Drivers (device diagnostic tags) and Exporting and Importing Tags, Ignition 8.3
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.