Ignition, FactoryTalk Optix, the AVEVA Communication Drivers, N3uron and Kepware all document drivers for Siemens, Mitsubishi and Omron controllers, and for Modbus, BACnet and OPC UA. The names differ, and so do the PLC families each driver lists and what must change in the PLC before it answers. The tables below use only each vendor's current documentation; "not found in docs" means we found no driver, not that the product cannot do it.
1. What was read
The versions read:
- Ignition: the 8.1 and 8.3 user manuals, which are separate doc sets. The tables give each its own row.
- FactoryTalk Optix: the FactoryTalk Optix 1.8.0 Help. Its Modbus driver page is labelled 1.7.x.
- AVEVA: the AVEVA Communication Drivers Pack 2026, whose driver pages also use the name OI Server.
- N3uron: the N3uron Knowledge Base V1.22.
- Kepware: the PTC Kepware Drivers help center, whose driver pages print no release number.
2. Siemens, Mitsubishi and Omron controllers
| Platform | Siemens S7 | Mitsubishi MELSEC | Omron |
|---|---|---|---|
| Ignition 8.1 | Siemens |
Mitsubishi TCP (new in 8.1.28): iQ-R, iQ-F (FX5U), Q, L, F (FX3) | Omron NJ driver; Omron FINS driver over TCP or UDP |
| Ignition 8.3 | the same four drivers, absolute addressing only; Siemens Enhanced driver adds browsing, symbolic access and optimized blocks on |
Mitsubishi TCP, same series | Omron NJ driver; Omron FINS driver over TCP or UDP |
| FactoryTalk Optix 1.8.0 | S7TCP: |
MELSEC Q driver: "may support" MELSEC-Q and MELSEC-L; MELSEC FX3U driver | OMRON EtherNet/IP: "may support" NJ, NX and NU; OMRON Fins: CJ and CP |
| AVEVA Communication Drivers 2026 | SIDirect: |
MELSEC: Q, QnA, L and iQ-R, Ethernet and serial | OMRONFINS: CS1, CJ1, CJ2 and CP1 in CS1 mode; CV, CVM1 and CVM1D in CV mode |
| N3uron V1.22 | Siemens Client: S7 300, 400, 1200, 1500, S7 protocol over TCP/IP | not found in docs | EtherNet/IP Client: Omron NJ/NX (from 1.22.0); FINS not found in docs |
| Kepware | Siemens TCP/IP Ethernet: |
Mitsubishi Ethernet: A, QnA, Q, L, FX3U, iQ-R and iQ-F, TCP/IP and UDP | Omron NJ Ethernet: NJ301, NJ501, |
Points the docs add to the table:
- Siemens symbolic access is a separate driver or object on three platforms: the Siemens Enhanced driver in Ignition 8.3 (not included on a Platform license; no such page in the 8.1 manual), the SIDirect Symbolic object in AVEVA, and Siemens S7 Plus Ethernet in Kepware, which uses S7 Comm Plus.
- In Optix, S7TCP supports only non-optimized structures and S7 TIA PROFINET only optimized ones.
- AVEVA's MELSEC page names the MC protocol for Q-series PLCs and SLMP for iQ-R. Its OMRONFINS page says connecting through an EIP Ethernet card is not supported.
3. Modbus, BACnet and OPC UA
| Platform | Modbus | BACnet | OPC UA server as the data source |
|---|---|---|---|
| Ignition 8.1 | Modbus TCP, Modbus RTU over TCP, Modbus RTU serial | BACnet driver, BACnet/IP over UDP | OPC UA client connection (OPC Client > OPC Connections) |
| Ignition 8.3 | Modbus TCP, Modbus RTU over TCP, Modbus RTU serial | BACnet driver, BACnet/IP over UDP | OPC UA Connection (Connections > OPC > Connections) |
| FactoryTalk Optix 1.8.0 | Modbus driver: Modbus TCP and Modbus RTU | not found in docs | OPC UA client object that imports nodes from an OPC UA server |
| AVEVA Communication Drivers 2026 | MBTCP: Modbus TCP/IP; serial Modbus controllers through a Modbus Bridge | BACLITE: BACnet/IP over UDP/IP | Gateway Communication Driver, OPC UA data source |
| N3uron V1.22 | Modbus Client: Modbus TCP, Modbus RTU and RTU over TCP | BACnet Client, BACnet/IP over UDP | OPC UA Client |
| Kepware | Modbus TCP/IP Ethernet; Modbus RTU Serial | BACnet/IP | OPC UA Client, described as a tunnel between OPC servers |
Ignition and N3uron both say that BACnet devices on other media, such as MS/TP, are reached through a gateway or router. The Ignition 8.3 manual has its own page for connecting to KEPServerEX over OPC UA.
4. What has to be set in the PLC
Only what the driver pages say about the PLC side; no row means we found nothing.
| PLC family | Driver | Protocol | What to set on the PLC, per the docs |
|---|---|---|---|
| Ignition Siemens |
S7 over TCP/IP | Optimized block access off; Full access (no protection) and PUT/GET permitted; only global DBs; the change may need the hardware configuration recompiled and downloaded | |
| Ignition 8.3 Siemens Enhanced, Symbolic | S7, symbolic | PUT/GET and full access not needed: read access to read and browse, write access to write | |
| AVEVA SIDirect Legacy object | TCP over Ethernet | PUT/GET enabled and optimized block access disabled in TIA Portal; the Symbolic object needs no pre-configuration | |
| N3uron Siemens Client | S7 over TCP/IP | Optimized block access off; access level full; PUT/GET allowed | |
| Optix S7TCP, online tag import | not named | Full access; PUT/GET from remote partner; "Only allow secure PG/PC and HMI communication" disabled if applicable | |
| MELSEC iQ-R, iQ-F, Q, L | Ignition Mitsubishi TCP | MELSEC, SLMP connection over TCP | GX Works3: online change Enable All (SLMP), data code Binary, an SLMP connection module with TCP; write to the PLC and power cycle |
| MELSEC F with |
Ignition Mitsubishi TCP | MC procedure over TCP | FX Configurator-EN: binary code, Always wait for OPEN, connection with TCP and Procedure Exist (MC) |
| Omron NJ, NX | Optix OMRON EtherNet/IP | EtherNet/IP | Network Publish set to Publish only in Sysmac Studio, then tags exported to a TXT file |
| Omron FINS devices | Ignition Omron FINS | FINS over TCP or UDP | Destination node is typically the last octet of the IP address, set with the dials on the device |
5. Choosing by plant situation
A SCADA is already running
We start from the platform the plant already has and look for the PLC in its list. At SEHC, Modbus and BACnet equipment reached the AVEVA System Platform SCADA through KEPServerEX, as our air compressor and Admin Building pages describe.
Several PLC brands on one site
One pattern is a platform whose own list covers every brand on site; the tables show where the lists differ, for example no Mitsubishi module in the N3uron docs. The other is an OPC server in between: Kepware's driver pages describe connecting devices to OPC client applications such as HMI, SCADA and historians, and every platform above documents an OPC UA client.
The PLC has an OPC UA server
Both Ignition manuals note that some
Serial devices and gateways
Ignition's Modbus driver connects to devices directly over Ethernet or through a gateway device. AVEVA's MBTCP reaches serial Modbus controllers through a Modbus Bridge. At Yakult Vietnam the serial port of the existing Mitsubishi FX-series PLC is connected through a Modbus RTU to Modbus TCP gateway to a FactoryTalk Optix SCADA, and the PLC stays in control. More on register maps and gateways: Modbus RTU and TCP for SCADA and Bringing AHUs and air compressors into an FMCS SCADA.
When the PLC is replaced instead
At SEHC VD5 the Siemens PLCs, HMIs and serial converters had stopped working and were replaced with a CompactLogix 5370, then brought back into the FMCS SCADA. On the Vietsovpetro LP compressor a Siemens S5 control system was replaced with ControlLogix. The S5 does not appear in any of the Siemens driver lists above.
What we check first
This is TDL's practice, not a requirement of Inductive Automation, Rockwell Automation, AVEVA, N3uron or PTC.
- We back up the PLC program before any change, as on the Yakult project.
- We note the exact CPU, its firmware and the port the SCADA will use: built-in Ethernet, a communication module or a serial port.
- We trace the network path from the SCADA server to the PLC, switch by switch.
- We ask the plant whether a PLC-side change is allowed. Changing PUT/GET, optimized block access or the SLMP settings can mean a download to the PLC, and the Mitsubishi page asks for a power cycle.
- We estimate the polling load: tags, rates and connections. The Ignition Omron NJ driver, for example, uses one CIP connection per concurrent request, two by default.
- We agree on tag names and where the tag list comes from: a TIA Portal project, a GX Works CSV file or a Sysmac Studio export.
How TDL approaches it
TDL Industrial Automation is a System Integrator in the Rockwell Automation PartnerNetwork, a System Integrator member of the AVEVA Partner Ecosystem, an Ignition Certified Integrator and a Certified Integrator of N3uron. Our project pages linked above cover a Mitsubishi PLC kept in service at Yakult Vietnam, Modbus and BACnet equipment at SEHC, and two sites where Siemens controllers were replaced. More on these services: Connecting existing PLCs and equipment to SCADA and SCADA and historian.
Platform by platform, in more depth:
- Ignition and Siemens
S7-1200 /1500 - Ignition with Mitsubishi and Omron PLCs
- FactoryTalk Optix drivers for Siemens, Mitsubishi, Omron and Modbus
- AVEVA OI Server drivers for Siemens, Mitsubishi and Omron
- N3uron Siemens S7 and Modbus Client
- Allen-Bradley controllers: Ignition Logix driver and AVEVA ABCIP driver
Frequently asked questions
Which platforms read an S7-1200 or S7-1500 by tag name?
Ignition 8.3 with the Siemens Enhanced driver, AVEVA with the SIDirect Symbolic object, and Kepware with the Siemens S7 Plus Ethernet driver. In Optix, the S7 TIA PROFINET driver is the one that supports optimized structures; its tags are created with the TagImporter.
Does the Siemens PLC need PUT/GET turned on?
For the Ignition Siemens drivers, the AVEVA SIDirect Legacy object, the N3uron Siemens Client and online tag import in Optix S7TCP, the docs say yes, together with full access. The SIDirect Symbolic object and Ignition's Siemens Enhanced driver in Symbolic mode do not need it. The change may need a download to the PLC.
Does "not found in docs" mean the platform cannot connect?
No. It means we found no driver for it in the documentation we read for that version. A newer release, another module or an OPC server in between may still cover it.
Can a Mitsubishi FX PLC be read without a Mitsubishi driver?
Yes. At Yakult Vietnam the serial port of the existing FX-series PLC reaches FactoryTalk Optix through a Modbus RTU to Modbus TCP gateway. Ignition, Optix and Kepware also list FX drivers: Ignition and Kepware through the
How do Omron NJ controllers connect?
Over EtherNet/IP. Ignition has the Omron NJ driver, Optix the OMRON EtherNet/IP driver, Kepware the Omron NJ Ethernet driver and N3uron the EtherNet/IP Client from 1.22.0. AVEVA's OMRONFINS page lists an NJ501 among its
Sources
- Inductive Automation, Driver Modules (Ignition 8.3) and Driver Modules (Ignition 8.1), user manual
- Inductive Automation, Siemens, Siemens Drivers and Siemens Enhanced Driver (Ignition 8.3); Siemens (Ignition 8.1)
- Inductive Automation, Mitsubishi TCP Driver (8.3) and Mitsubishi TCP Driver (8.1)
- Inductive Automation, Omron NJ Driver and Omron FINS Driver (8.3); Omron NJ Driver and Omron FINS Driver (8.1)
- Inductive Automation, Modbus and Connecting to Modbus Device (8.3); Connecting to Modbus Device (8.1)
- Inductive Automation, BACnet (8.3) and BACnet (8.1)
- Inductive Automation, OPC UA Connections and Connecting to Kepware OPC UA (8.3); OPC UA Client Connection Settings (8.1)
- Rockwell Automation, FactoryTalk Optix 1.8.0 Help: Communication drivers overview, S7TCP driver, S7 TIA PROFINET driver, MELSEC Q driver, MELSEC FX3U Driver, OMRON EtherNet/IP driver, OMRON Fins Driver, Modbus driver (page labelled 1.7.x) and OPC UA client
- AVEVA, Communication Drivers Pack 2026: Controller-specific Communication Drivers, SIDirect supported device protocols, SIDirect Symbolic object, Special pre-configuration for
S7-1200 andS7-1500 PLCs, MELSEC supported hardware and software, OMRONFINS supported hardware and software, MBTCP supported device protocols, Get started with the BACLITE Communication Driver and Connect to an OPC UA data source - N3uron, Knowledge Base V1.22: Siemens Client, Modbus Client, EtherNet/IP Client, BACnet Client and OPC UA Client, introduction pages
- PTC, Kepware Drivers help: Siemens TCP/IP Ethernet Setup, Siemens S7 Plus Ethernet Setup, Mitsubishi Ethernet Setup, Mitsubishi Ethernet Overview, Omron NJ Ethernet Setup, Omron FINS Ethernet Setup, Modbus TCP/IP Ethernet, Modbus RTU Serial Overview, BACnet/IP Overview and OPC UA Client Overview
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.