Ignition reads Mitsubishi MELSEC and Omron controllers with three drivers of its OPC UA module: Mitsubishi TCP, Omron FINS (over TCP or UDP) and Omron NJ. With all three, the addresses are typed or imported on the Gateway first, and only then can they be browsed in the Designer. Below: settings, address syntax, data types and the PLC side, from the Ignition 8.1 and 8.3 manuals and Omron's EtherNet/IP port manual. For Allen-Bradley see the Logix driver article; for Siemens, Ignition and Siemens
1. Three drivers and the controllers they name
| Driver | Controllers, as the pages state | Transport | From the 8.1 page |
|---|---|---|---|
| Mitsubishi TCP | MELSEC iQ-R, iQ-F (FX5U), Q, L and F (FX3) | MELSEC protocol over TCP | new in 8.1.28; F (FX3) from 8.1.31 |
| Omron FINS/TCP, Omron FINS/UDP | Omron FINS devices; no PLC family is listed | FINS over TCP or UDP | XML address files from 8.1.2 |
| Omron NJ Driver | Omron NJ series controllers | CIP connections | Local Address from 8.1.8 |
The device connection is created in 8.3 under Connections > Devices > Connections, and in 8.1 under Config > OPC UA > Device Connections. In 8.3 each driver needs the OPC UA module installed and enabled, otherwise it faults with Missing Dependency. The 8.3 FINS and NJ pages add that the device name appears in every OPC item path and must start with a letter or an underscore, with no special characters.
2. Mitsubishi TCP: connection and PLC settings
| Setting | Meaning | Default |
|---|---|---|
| Hostname, Port | IP address and port of the PLC, as set in GX Works | not stated |
| Timeout | milliseconds, 0 to 16,383,750 | 5,000 |
| Series | iQR, iQF, Q or L in the connection step; a wrong choice can cause an error condition on the device | iQR |
| PC Number | station number of the target; through a multi-drop connection, the relay station | 255 |
| Network Number | network number of the target | 0 |
| Request Destination Module I/O Number | start I/O of the multi-drop source module, or the CPU of a multiple CPU system | 1023 |
| Request Destination Module Station Number | target station when PC Number is the relay station | 0 |
| Max Gap Size | address gap spanned when requests are merged | 0 in 8.1; -1 in 8.3 (changed in 8.3.2), meaning the largest request |
In 8.1 the four routing settings exist from 8.1.43. The connection step offers no F option under Series, and the page does not say which value suits an FX3.
The page lists what must be set in the PLC first. For iQ-R, iQ-F, Q and L it describes GX Works3 (GX Works2 differs slightly): under Own Node Settings, Enable/Disable Online Change set to Enable All (SLMP) and Communication Data Code to Binary; in External Device Configuration, an SLMP Connection Module with protocol TCP, whose IP address and port go into the driver; then write to the PLC and power cycle it. Some areas need more points under Memory Device Setting, again with a write and a power cycle.
For the F series it uses FX Configurator-EN on an
3. Mitsubishi addressing
Addresses are entered on the device's Addresses panel, or imported from a CSV or GX Works CSV file. The page advises testing one address before importing a list. In the Designer the OPC item path is ns=1;s=[DeviceName]Area{<DataType{[array]}>}Offset{.Bit}, optional parts in braces.
- Areas are MELSEC device keywords such as X, Y, M, B, D, W, R, ZR, TN and CN. Extended data and link registers are not supported. On the F series, CN is a word for offsets 0 to 199 and a double word for 200 to 255.
- Offsets are decimal except for X, Y, DX, DY, B, SB, W and SW. X and Y are hex on iQ-R, Q and L, octal on iQ-F and F; the others are hex.
D0.0is bit 0 of D0,D<int32>0combines D0 and D1, andD<string10>0reads up to 10 characters. Types smaller than the native type are not supported.- Without a type, bits read as bool, words as int16 and double words as int32. Byte order defaults to little endian (@LE), word order to high-low (@HL).
- An address with a bit index is read-only; a write returns Bad_NotSupported. An array too large for one request is split into sequential requests that are not atomic.
4. Omron FINS: transport, node numbers and areas
FINS/TCP takes Hostname, Port (default 9600) and Timeout (default 2,000 ms). FINS/UDP takes a Bind Address and Bind Port on the Gateway and a Remote Address and Remote Port for the device, all 9600 by default. Both carry the same FINS settings: Source Network, Node and Unit for the Gateway, Destination Network, Node and Unit for the PLC. Networks run from 0 to 127, nodes from 0 to 254 and units from 0 to 255, all defaulting to 0. The node is typically the last octet of the IP address, and the page says the device's node is set with the dials on its front.
Ignition's area codes are CIO, WR (W), HR (H), AR (A), TIM (T), CNT (C), IR, DR, DM (D) and EM. E00 to E18 (hex) are the 25 EM banks, so E001000 is word 1000 of bank 0. TIM0 is a timer's present value and TIM<Bool>0 its completion flag. Data types include BCD16 and BCD32. The defaults are the reverse of the Mitsubishi driver: big endian (@BE) and low-high word order (@LH).
Addresses are imported from CSV, TSV or CXR files in 8.3 (CSV, TSV or XML in 8.1).
On the PLC side, Omron's manual
5. Omron NJ driver: variables, not memory areas
The NJ driver needs Hostname and Timeout (2,000 ms). Its Advanced settings are Connection Size (default and maximum 1,994 bytes), Date/Time Offset in hours, Slot Number of the CPU (0) and Concurrency (2), which equals the number of CIP connections used.
Tags come from the PLC's global variables. In Sysmac Studio, Tools > Export Global Variables > CX-Designer copies them as tab-separated text, which is saved to a file and imported on the Addresses panel. Each row has Browse Name (structure members separated by periods), Datatype, Characters, Elements and R/W. A blank Elements gives a scalar, 0..9 a 0..3,0..3 a two-dimensional one. The driver takes the lowest mapped element as the lowest element in the PLC, so a mapping of 3..7 against a PLC array of 0..4 shifts every index; the page strongly recommends matching the program.
Omron's manual adds the PLC side. The CIP Message Server of the built-in port is set to Use by default and opens UDP 2222 and UDP and TCP 44818; set to Do not use, the controller cannot receive CIP messages. With the packet filter in use, CIP message packets must be permitted. A class 3 connection with Large_Forward_Open carries up to 1,994 bytes on NJ-series CPUs, the driver's maximum Connection Size. In Omron's examples of one controller reading another's variable by CIP message, the variable is global with the Network Publish attribute set; the Ignition page does not say whether the driver needs that.
6. What to set on each side
| PLC family | Ignition driver | Protocol | What to set on the PLC (source) |
|---|---|---|---|
| MELSEC iQ-R, iQ-F, Q, L | Mitsubishi TCP | MELSEC over TCP | Enable All (SLMP), Binary, SLMP connection module on TCP, write and power cycle (Ignition) |
| MELSEC F (FX3) with |
Mitsubishi TCP | MELSEC over TCP | FX Configurator-EN: Binary code, TCP connection with Procedure Exist (MC) (Ignition) |
| Omron FINS devices | Omron FINS/TCP or FINS/UDP | FINS, port 9600 | node number on the front dials (Ignition); FINS settings of NJ/NX built-in ports (Omron W506) |
| Omron NJ series | Omron NJ Driver | CIP | CIP Message Server on Use, packet filter permitting CIP (Omron W506); global variables exported (Ignition) |
All three drivers share the device diagnostic tags, including OverloadFactor, explained in the Logix driver article. A PLC with only a serial Modbus port takes another route: Modbus RTU, TCP and register maps.
What we check first
This is TDL's practice, not an Inductive Automation or Omron requirement.
- We back up the PLC program and parameters before any change, because the Mitsubishi settings are written to the PLC and need a power cycle.
- We record the CPU series, Ethernet module and port, and ask whether the plant allows the PLC-side change at all: SLMP, FINS ports, the CIP Message Server or the packet filter.
- We trace the network path from the Gateway to the PLC, switch and routers included.
- We build the address list from the PLC project, the GX Works CSV or the Sysmac Studio export, agree tag names with the plant, and match NJ array ranges to the program.
- We read one known value of each
32-bit , string and BCD type before importing the rest, to settle byte order, word order and octal or hex offsets. - We start with few concurrent requests and slow tag groups, and raise them only while OverloadFactor stays low.
How TDL approaches it
TDL Industrial Automation is an Ignition Certified Integrator. We have no Ignition project page with a Mitsubishi or Omron PLC. At Yakult Vietnam the existing Mitsubishi FX-series PLC stays in service and its serial port reaches a FactoryTalk Optix SCADA through a Modbus RTU to Modbus TCP gateway. Driver coverage across platforms: PLC drivers for Siemens, Mitsubishi and Omron compared. Services: Ignition SCADA integrator in Vietnam and Connecting existing PLCs and equipment to SCADA. Background: What is Ignition.
Frequently asked questions
Which Mitsubishi PLCs does the Ignition Mitsubishi TCP driver support?
The 8.1 and 8.3 pages list the MELSEC iQ-R, iQ-F (FX5U), Q, L and F (FX3) series. The driver arrived in 8.1.28 and the F series in 8.1.31.
What has to be changed in GX Works3 before Ignition can connect?
Enable All (SLMP) for online change, Binary communication data code, and an SLMP connection module on TCP whose IP address and port go into the driver. The settings are then written to the PLC and the PLC is power cycled.
Which Omron driver suits an NJ controller?
The Omron NJ Driver reads the controller's global variables over CIP once they are exported from Sysmac Studio and imported on the Gateway. Omron's manual also lists FINS ports on NJ-series built-in ports, but the FINS driver addresses memory areas such as CIO and DM, not variables.
Why do the Mitsubishi or Omron tags not appear in the Designer?
The addresses or variables must first be typed or imported on the Gateway, on the device's Addresses panel. Only then can they be browsed in the Designer.
Why does a 32-bit value read wrong?
Byte and word order differ. The Mitsubishi driver defaults to little endian and high-low word order, the FINS driver to big endian and low-high word order; modifiers such as @HL or @LH change it per address.
Sources
- Inductive Automation, Mitsubishi TCP Driver (Ignition 8.3, updated 8 September 2026) and Mitsubishi TCP Driver (Ignition 8.1, updated 4 March 2026)
- Inductive Automation, Omron FINS Driver (8.3, updated 8 September 2026) and Omron FINS Driver (8.1, updated 17 April 2025)
- Inductive Automation, Omron NJ Driver (8.3, updated 8 September 2026) and Omron NJ Driver (8.1, updated 17 April 2025)
- Inductive Automation, Driver Modules (8.3, updated 8 September 2026) and OPC UA Drivers (8.3, updated 18 September 2026)
- OMRON, NJ/NX-series CPU Unit Built-in EtherNet/IP Port User's Manual, Cat. No.
W506-E1-37 , February 2025, pp.4-21 ,5-15 ,5-16 ,7-3 ,7-22 and7-40
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.