Home › Technical articles

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

FactoryTalk Optix drivers for Siemens, Mitsubishi, Omron and Modbus: stations, tags and PLC-side settings

TDL Industrial Automation · Last updated:

From the FactoryTalk Optix 1.8.0 help and the 1.4.1.7 object reference: the S7TCP and S7 TIA PROFINET, MELSEC FX3U and MELSEC Q, OMRON EtherNet/IP and OMRON Fins, Modbus TCP/RTU drivers and the OPC UA client; online and offline tag import, station properties, memory areas, PUT/GET and Network Publish, OperationCode values.

FactoryTalk Optix reads PLCs from other makers through its own communication drivers: S7TCP and S7 TIA PROFINET for Siemens, MELSEC FX3U and MELSEC Q for Mitsubishi, OMRON EtherNet/IP and OMRON Fins for Omron, and a Modbus driver for Modbus TCP and RTU. A device with an OPC UA server is read through an OPC UA client instead. Below: what the Optix 1.8.0 help says about each (a few of its pages still carry a 1.7.x header, noted where used), with station and tag properties from the older 1.4.1.7 object reference, also noted where used. What Optix is: FactoryTalk View SE vs ME vs Optix.

Other makers' PLCs into FactoryTalk Optix: family, driver, projectLeft column: PLC families and devices. Middle column: the matching Optix driver and its tag import. Siemens S7-300, S7-400, S7-1200 and S7-1500 use S7TCP, non-optimized structures; S7-1200 and S7-1500 can also use S7 TIA PROFINET, optimized structures, tags only through the TagImporter. Mitsubishi FX3U uses MELSEC FX3U, offline import from English CSV; MELSEC-Q and MELSEC-L (which the driver page says it may support) use MELSEC Q, offline import. Omron NJ, NX, NU (which the driver page says it may support) use OMRON EtherNet/IP, offline import from TXT; Omron CJ, CP use OMRON Fins, offline import from TXT. Modbus TCP and RTU devices use the Modbus driver, tags set by memory area and register. OPC UA servers use the OPC UA client, nodes imported online or from a NodeSet. Right column: the FactoryTalk Optix project with one station per controller, Tags, Types and TagImporter, graphic objects, and OperationCode for diagnostics. Based on the FactoryTalk Optix 1.8.0 help and the 1.4.1.7 object reference.Other makers' PLCs into FactoryTalk Optix: family, driver, projectPLC familyOptix driverOptix projectSiemens S7-300,S7-400, S7-1200,S7-1500S7TCPnon-optimized structuresSiemens S7-1200,S7-1500S7 TIA PROFINEToptimized structures, tags only viaTagImporterMitsubishi FX3UMELSEC FX3Uoffline import from English CSVMitsubishi MELSEC-Q,MELSEC-LMELSEC Q“may support” · offline importOmron NJ, NX, NUOMRON EtherNet/IP“may support” · offline importfrom TXTOmron CJ, CPOMRON Finsoffline import from TXTModbus TCP andModbus RTU devicesModbustags by memory area and registerOPC UA serversOPC UA clientnodes online or from a NodeSetFactoryTalk Optixprojectone station per controllerTags, Types, TagImportergraphic objectsOperationCode fordiagnosticsBased on Rockwell Automation, FactoryTalk Optix 1.8.0 help, Communication drivers and OPC UA sections, andthe 1.4.1.7 object reference (read 15 November 2026). Figure: drawn by TDL.
Figure 1: Other makers' PLCs into FactoryTalk Optix: family, driver, project. On a phone, swipe sideways to see the whole figure.

1. The drivers the Optix 1.8.0 help lists

The communication drivers overview lists thirteen entries and the tag import modes each supports. Besides the ones below, it has three drivers for Allen-Bradley equipment (RA EtherNet/IP, Micro Controller, RA Device), CODESYS, TwinCAT and a Serial port entry for controllers with custom protocols.

Driver Controllers named on the driver page Tag import
S7TCP Siemens S7-1200, S7-1500, S7-300, S7-400 online for S7-1200 and S7-1500; offline for all four
S7 TIA PROFINET Siemens S7-1200, S7-1500 online and offline
MELSEC FX3U none beyond the driver name offline, from English CSV files
MELSEC Q "may support" MELSEC-Q and MELSEC-L series offline
OMRON EtherNet/IP "may support" NJ, NX and NU series; tested with NJ301-1100 firmware 1.09 and NJ101-9000 firmware 1.50 offline, from TXT files
OMRON Fins CJ and CP families; tested with CJ2 offline, from TXT files
Modbus Modbus TCP and Modbus RTU devices none

The OPC UA client sits in the OPC UA section of the help, not in this list.

2. Driver, station, tag

Each driver stands for a protocol and holds one station per physical controller. A station holds Tags, Types and a TagImporter that reads tags from the controller (online) or from an exported file (offline).

Stations are made from the dashboard: Configure communications to devices, New station, station type, properties, import mode, tags, Apply. Modbus has no tag import; in the 1.4.1.7 reference each Modbus tag carries its own memory area and register number. Opening the TagImporter again brings later PLC changes in; tags removed from the PLC or the file show crossed out on red.

The help says that at runtime Optix synchronizes only the tags shown or written by active graphic objects, to save bandwidth. The interval is the Dynamic variables polling time, set on the NativePresentationEngine or WebPresentationEngine.

3. Siemens: S7TCP or S7 TIA PROFINET

The S7TCP page says the driver supports only non-optimized structures; the S7 TIA PROFINET page says only optimized structures, with tags created only by the TagImporter.

Before an online import, the help asks for:

  • S7TCP: Access level set to a Full access option, Permit access with PUT/GET communication from remote partner enabled, and Only allow secure PG/PC and HMI communication disabled where it applies.
  • S7 TIA PROFINET: Full access and the same secure-communication option disabled where it applies. With certificates, the controller's DER certificate is exported from TIA Portal into the project's PKI folder and set in the station's Controller certificate file.

Offline import reads project files ap13 to ap19, and both pages say the project must be compiled with Optimized block access enabled. For S7TCP this sits next to the non-optimized rule, so we check the block settings on the real project first.

In the 1.4.1.7 reference, the S7TCP station has IP address, Port, Timeout, Remote rack (default 0) and Remote slot (default 2). Remote device ID 2, the default, takes an OP channel meant for HMI links; 1 takes a PG channel, usually scarce and kept for programming. An S7TCP tag is a memory area (DataBlock, Marker, Peripheral, Counter, Timer, Input or Output) with block number, position and bit. An S7 TIA PROFINET tag carries the symbol name.

4. Mitsubishi: MELSEC FX3U and MELSEC Q

The MELSEC FX3U page has one rule: offline import from English CSV files. In the 1.4.1.7 reference, the station has IP address, Port (matching the controller) and Timeout, and a tag is a memory area, such as X, Y, M, S, D or R, plus a device number and bit offset.

For MELSEC Q, the 1.4.1.7 reference gives the IP address as that of the controller's Ethernet module. Port is the Local station Port No. of the TCP or UDP connection set up in that module, in decimal; the default is 0 for TCP and 5000 for UDP. Network Number and PC Number take the module's Network No. and Station No. The pages we opened do not name the Mitsubishi protocol or frame.

5. Omron: OMRON EtherNet/IP and OMRON Fins

For OMRON EtherNet/IP, Network Publish is set to Publish only in Sysmac Studio before the tags are exported to TXT. In the 1.4.1.7 reference, the station has IP address, Port, Timeout and CPU slot; tags are addressed by symbol name.

For OMRON Fins, the CX-Programmer symbol table is copied into a TXT file. The areas are CIO, A, T, C, D, H and W; Ex is location x of the current EM bank and Ex_y location y of bank x; IR, DR and TK are not supported. In the 1.4.1.7 reference, Protocol is Ethernet or serial, and Port defaults to 9600. FINS needs the same source and destination port, so a new Port means the same value in Local Bound Port. The PLC-side node address defaults to 50 and usually equals the last octet of the PLC's IP address; the unit is 0 for the CPU.

6. Modbus TCP and Modbus RTU

The Modbus driver page (headed 1.7.x) gives two protocols, Modbus TCP (TCP socket) and Modbus RTU (serial port; the 1.4.1.7 reference lists COM port, baud rate, data size, parity, stop bits and flow control), and six data areas:

Area Function codes as listed Access Range
Single Coils 01 read, 05 write read/write 0–65535
Coils 01 read, 15 write multiple read/write 0–65535
Discrete Inputs 02 read read only 0–65535
Single Register 03 read, 06 write read/write 0–65535
Multiple Register 03 read, 10 write read/write 0–65535
Input Register 04 read read only 0–65535

The help notes that addressing differs between devices. The 1.4.1.7 reference counts positions from 0 and prints position 0 of the holding registers as register 4001. The station has Unit identifier, IP address, Port, Timeout, Tag optimization (off when the device cannot read several tags at once) and Swap bytes, Swap words and Swap DWords.

7. OPC UA client

An OPC UA client takes a Server endpoint URL, a Minimum message security mode (None, Sign, or Signature and cryptography), a Minimum security policy (None, Basic256Sha256, Aes128_Sha256_RsaOaep or Aes256_Sha256_RsaPss) and a client certificate and private key. Nodes come online from the server or offline from a NodeSet XML file; at runtime the client reads, writes, receives events and calls methods.

8. Is the station talking?

A station's OperationCode is 0 when communication is good. The codes are Good; BadNoCommunication, a timeout against the station's Timeout; BadCommunicationError, an error returned by the controller; and BadConfigurationError, for example an invalid address. A control that cannot read or write its tag is outlined in red; the Station Connection Status widget (page headed 1.7.x) shows a green or red LED.

Summary: PLC family, driver, PLC side

PLC family Optix driver Protocol, as documented What to set on the PLC side
S7-1200, S7-1500 S7TCP S7TCP Full access, PUT/GET permitted, secure PG/PC and HMI communication off if applicable; non-optimized structures
S7-300, S7-400 S7TCP S7TCP no online import; tags from the ap13–ap19 project file
S7-1200, S7-1500 S7 TIA PROFINET S7 TIA PROFINET Full access, secure communication off if applicable; optimized structures
MELSEC FX3U MELSEC FX3U TCP-IP connection port matching the controller
MELSEC-Q, MELSEC-L (may support) MELSEC Q TCP or UDP a Local station Port No. on the Ethernet module
Omron NJ, NX, NU (may support) OMRON EtherNet/IP EtherNet/IP Network Publish set to Publish only
Omron CJ, CP OMRON Fins FINS, Ethernet or serial same port on both sides, 9600 by default
Modbus devices Modbus Modbus TCP or RTU unit ID and register map of the device
OPC UA servers OPC UA client OPC UA matching security mode and policy, certificates

What we check first

This is TDL's practice, not a Rockwell Automation requirement.

  • We back up the PLC program before any change on the PLC side.
  • We note the CPU model, firmware and port, and compare them with the families and tested firmware on the driver page.
  • We trace the network path and the switch between the Optix computer and the PLC.
  • We ask the plant before changing access level, PUT/GET or block access on a Siemens CPU; the block setting decides between S7TCP and S7 TIA PROFINET.
  • We size the polling time and the tags on open screens to what the PLC and serial links can carry.
  • We fix tag names before the first import, because every graphic links to them.

FactoryTalk Optix work at Yakult Vietnam

TDL Industrial Automation is a System Integrator in the Rockwell Automation PartnerNetwork. In 2026 we built a monitoring SCADA for the ice bank cooling system at Yakult Vietnam on FactoryTalk Optix. The existing Mitsubishi FX-series PLC stays in control. After a site survey and a backup of the PLC program, its serial port was connected through a Modbus RTU to Modbus TCP gateway and a Stratix switch to the SCADA workstation, and the Optix runtime serves the screens to browsers on the plant network. Where Siemens controllers were replaced instead, our project pages say so: at SEHC VD5 failed Siemens PLCs and HMIs gave way to a CompactLogix, and on the Vietsovpetro LP compressor a Siemens S5 to ControlLogix.

Related: Ignition Logix driver, Modbus register maps for SCADA and PLC drivers compared across platforms. Services: Rockwell Automation system integrator and connecting existing equipment to SCADA.

Frequently asked questions

Can FactoryTalk Optix read a Siemens S7-1200 or S7-1500?

Yes, through either S7TCP or S7 TIA PROFINET. S7TCP supports only non-optimized structures and, for online import, needs Full access and PUT/GET permitted on the CPU. S7 TIA PROFINET supports only optimized structures and creates its tags only through the TagImporter.

Which Mitsubishi PLCs does Optix document?

The MELSEC FX3U driver, with offline import from English CSV files, and the MELSEC Q driver, which may support the MELSEC-Q and MELSEC-L series and also imports offline only. For MELSEC Q, the station port is the Local station Port No. set in the PLC's Ethernet module.

What does the OMRON Fins driver need?

A CJ or CP controller, the symbol table copied from CX-Programmer into a TXT file, and the same port on both sides, 9600 by default. The IR, DR and TK areas are not supported.

Does the Optix Modbus driver count registers from 0 or 1?

The 1.4.1.7 reference counts tag positions from 0 and prints position 0 of the holding registers as register 4001. The help also says addressing differs between devices, so the device's register map decides.

How do I see that a station has lost the PLC?

Read the station's OperationCode: 0 means good, and BadNoCommunication means a timeout. Controls bound to tags that cannot be read are outlined in red, and the Station Connection Status widget shows a red LED.

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:
Rockwell Automation (Allen-Bradley) Connecting existing equipment to SCADA