Home › Technical articles

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

AVEVA SIDIRECT, MELSEC and OMRONFINS drivers: InTouch and System Platform to Siemens, Mitsubishi, Omron PLCs

TDL Industrial Automation · Last updated:

From AVEVA's Communication Drivers Pack 2026 docs: the PLC families each driver supports, SIDIRECT Legacy and Symbolic objects, PUT/GET and optimized block access on the S7-1200 and S7-1500, MELSEC and OMRONFINS stations, item syntax, data types and what to set on the PLC side.

AVEVA InTouch HMI and System Platform read Siemens, Mitsubishi and Omron PLCs through three drivers of the AVEVA Communication Drivers Pack: SIDIRECT, MELSEC and OMRONFINS. Each is configured in the OI Server Manager and serves InTouch, Application Server and OPC clients over SuiteLink, DDE or OPC. This article follows the Communication Drivers Pack 2026 documentation; naming history, device groups, Access Names and $SYS$ items are in the ABCIP driver article.

1. Three drivers, three different trees

Driver PLC families, as AVEVA lists them Protocol and transport Tree in the OI Server Manager
SIDIRECT Siemens S7-300, S7-400, S7-1200, S7-1500; designed for the S7-1500 TCP over Ethernet only; no MPI or PROFIBUS PORT, then Legacy and Symbolic objects
MELSEC Mitsubishi Q, QnA, L, iQ-R MC protocol for the Q series, SLMP for iQ-R; UDP, TCP or serial Channel Selector, then Device Selector
OMRONFINS Omron CS1, CJ1, CJ2, CP1 (CS1 mode); CV, CVM1, CVM1D (CV mode); other FINS devices FINS over UDP, or FINS Host Link on serial Channel Selector, then Device Selector

The SIDIRECT default instance appears as OI.SIDIR.1; AVEVA's command-line example gives OI.MELSEC.1 as the MELSEC ProgID, and older AVEVA examples call the Siemens DAServer DASSIDirect. SIDIRECT needs no Siemens CP card in the PC and no SIMATIC NET library, only an ordinary network card. For the full hardware and firmware lists, the SIDIRECT and OMRONFINS pages point to AVEVA's support site; the SIDIRECT page adds that models in a tested series are supported, so a tested S7-1211C covers the S7-1200 family.

Three AVEVA drivers for Siemens, Mitsubishi and Omron PLCsAt the top, InTouch HMI, Application Server and OPC clients reach the drivers over SuiteLink, DDE or OPC. In the middle, in the OI Server Manager: SIDIRECT with a PORT and then a Legacy or Symbolic object; MELSEC with a Channel Selector and then a Device Selector whose Station is IP:port, with iqr: in front for iQ-R; OMRONFINS with a Channel Selector and then a Device Selector whose Station is IP:port:network:node:unit. Protocol row: SIDIRECT uses TCP over Ethernet; MELSEC the MC protocol for the Q series or SLMP for iQ-R over UDP or TCP, or serial; OMRONFINS FINS over UDP or serial Host Link. At the bottom: Siemens S7-300, S7-400, S7-1200 and S7-1500, where an S7-1200 or S7-1500 used with the Legacy object must permit PUT/GET and have optimized block access off; Mitsubishi Q, QnA, L and iQ-R; Omron CS1, CJ1, CJ2, CP1, CV, CVM1 and CVM1D through an ETN unit, FINS port typically 9600. Based on the AVEVA Communication Drivers Pack 2026 documentation.Three AVEVA drivers for Siemens, Mitsubishi and Omron PLCsInTouch HMI, Application Server, OPC clientsover SuiteLink, DDE or OPCAVEVA Communication Drivers Pack 2026: the OI Server Manager treeSIDIRECTPORT, then a Legacy orSymbolic objectLegacy: DB10,INT2,8 ·Symbolic: Tank4.LvlMELSECChannel Selector, thenDevice SelectorStation: IP:port ·iQ-R: iqr:IP:portOMRONFINSChannel Selector, thenDevice SelectorStation:IP:port:network:node:unitTCP over EthernetMC protocol (Q series) orSLMP (iQ-R) over UDP,TCP; serialFINS over UDP; serialHost LinkSiemensS7-300, S7-400,S7-1200, S7-1500S7-1200, S7-1500 withLegacy: PUT/GET permitted,optimized block access offMitsubishiQ, QnA, L, iQ-RMELSEC port as set in the PLCOmronCS1, CJ1, CJ2, CP1;CV, CVM1, CVM1Dthrough an ETN unit; FINSport typically 9600Based on AVEVA, Communication Drivers Pack 2026 documentation: Get started and Supported hardware forSIDIRECT, MELSEC and OMRONFINS; Special pre-configuration for S7-1200 and S7-1500 PLCs; Set the stationID of a device (read 15 November 2026). Figure: drawn by TDL.
Figure 1: Three AVEVA drivers for Siemens, Mitsubishi and Omron PLCs. On a phone, swipe sideways to see the whole figure.

2. SIDIRECT: Legacy or Symbolic object

The tree starts at PORT, the PC's network card, one per instance. Under it sit up to 1,024 objects of two kinds:

  • Legacy object: absolute addresses such as DB1,INT0.
  • Symbolic object: symbolic names such as Tank4.Lvl on an S7-1200 or S7-1500, with optimized block access on or off.
Legacy setting Range and default
Network Address IP address or host name of the CP, never blank, up to 255 characters; the preconfigured object holds 1.1.1.1
Local TSAP two hex numbers, default 01 and 00
Remote TSAP rack 0–255 (default 0), slot 0–255 (default 3) and connection resource (default 03), matching the TSAP set for the CP
Reply Timeout 0–100,000 ms, default 15,000
Connection Timeout 0–100,000 ms, default 30,000

The Symbolic object needs only the network address, plus a password if the PLC is protected; a copied configuration file does not carry the password.

What the PLC must allow. For the Legacy object on an S7-1200 or S7-1500, AVEVA describes two changes in TIA Portal. In the CPU properties under Protection, choose an access level other than No Access and permit PUT/GET communication from a remote partner. In the attributes of each data block, clear Optimized block access. If communication still fails: go offline, rebuild all, download. The Symbolic object needs none of this.

Item names. Legacy items follow Siemens notation, with English or German identifiers:

  • DB10,INT2,8: an array of 8 integers from byte 2 of DB10; DB25,DWORD4BCD: a double word at byte 4 shown as BCD.
  • Other areas replace the DB part: M or F for flags, I or E for inputs, Q or A for outputs, PI and PQ for peripheral I/O, T and C for timers and counters.
  • Word, integer, double word and real values are byte-swapped from the PLC's big-endian order to the PC's little-endian order.
  • The S7-1200 and S7-1500 do not allow direct T and C access; the S7-1500 adds LREAL and DTL.

Symbolic items read DataBlock.Tag, for example Kettle2.PigmentTube[4]. Names may be up to 128 characters, arrays up to 1,600 elements, structures up to 8 levels deep. A name with a space or period goes in double quotes: DB."T1 T2"[2].Mem.

Device groups. Only Legacy device groups have an Edit dialog: cyclic services and an optimization mode, S7 SAPI, Block read or Auto (default). The S7-1200 and S7-1500 support neither cyclic services nor SAPI.

Diagnostics. Symbolic objects add statistics items such as $SYS$Load (1 means 1,000 updates per second over the last 15 minutes) and $SYS$ReadCountFailed. Error code C004D002L means the device is not connected, C004D101L a timeout. On the Symbolic node, Auto-Build generates the PLC's templates and instances in an Application Server Galaxy.

3. MELSEC: station = IP address and port

In the Channel Selector the communication type is UDP, TCP or Serial. Serial is either direct, with COM port, baud rate, data bits, stop bits and parity matching the PLC, or encapsulated over TCP/IP or UDP/IP to a terminal server.

The Device Selector holds the Station:

  • Ethernet: IP address:port, for example 10.168.23.73:5001;
  • iQ-R: iqr:IP address:port, for example iqr:10.168.25.74:5002.

The port is the one set in the PLC; AVEVA tested a Q00JCPU with a QJ71E71-100 on UDP 5000 and TCP 5002, and an R16SFCPU through its built-in port on UDP 3001 and TCP 5002. For UDP, the page adds that a destination IP address must be configured.

Items are written <register><address>@<type>, Word by default. X, Y, B, W, SB and SW addresses are hexadecimal; M, L, D and R are decimal. Examples: D0, W7, X7, Y7772, M7, R10, TN17; strings such as DSH1.2. Types are SHORT, WORD, BCD and LBCD (both with byte swap), LONG, DWORD and FLOAT. iQ-R models have their own register table, with long timers and counters.

4. OMRONFINS: station = IP, port, network, node, unit

The Channel Selector sets Connection (UDP or Serial) and Mode: CS1, CV or C-series (C200). AVEVA states that connection through an Omron ETN Ethernet unit is tested and supported, through an EIP Ethernet card it is not.

The Ethernet Station reads IP:port:network:node:unit:mode, for example 192.168.2.22:9600:0:22:0:CS1; serial is subnet:node:unit, for example 0:1:0.

  • Port: the FINS UDP port, typically 9600 and changeable in the PLC.
  • Network and node: the FINS subnet and the node number, 1–254.
  • Unit: the ID for the PC interface set in the PLC program, default 0, not the unit number in the hardware settings.

With older units such as the CS1W-ETN01, CS1W-ETN11 and CJ1W-ETN11, or newer ones in ETN11-compatible mode, the driver does not support simultaneous connections. AVEVA's fix is a different FINS port per PLC (9600, 9601) with the full IP and port in each station. Routing through several remote PLCs over a second Ethernet subnet is not supported; routing from an Ethernet PLC over Controller Link is documented.

Items use CIO, A, H, W, D, EM (banks A to M), PVC and PVT: CIO5000@Short or CIO5000S, D102F for a float, D102.00 for a bit, D102-D105C for an 8-character string; Word is the default. With Ignore Non Fatal PLC Error set to No, a non-fatal PLC error sets all items Bad; with Yes they stay Good and a warning is logged. Error 33281 means an invalid subnet: check the station and the PLC routing table.

Both drivers share the Channel Selector's Advanced settings: message timeouts, retries and up to 32 simultaneous requests per channel, 100 per instance.

5. What the PLC side needs, per AVEVA

PLC family Driver and object Protocol Set on the PLC, as documented
S7-1200, S7-1500, absolute addresses SIDIRECT – Legacy TCP over Ethernet PUT/GET permitted, access level not No Access, optimized block access off in each DB
S7-1200, S7-1500, symbolic names SIDIRECT – Symbolic TCP over Ethernet nothing; the password if the PLC has one
S7-300, S7-400 SIDIRECT – Legacy TCP over Ethernet the CP's TSAP, matched by the Remote TSAP
Q, QnA, L MELSEC MELSEC protocol (MC protocol for the Q series) over UDP or TCP; serial the MELSEC port; a destination IP for UDP
iQ-R MELSEC, station iqr: SLMP over UDP or TCP the port
CS1, CJ1, CJ2, CP1; CV, CVM1, CVM1D OMRONFINS, Mode CS1 or CV FINS over UDP through an ETN unit; Host Link FINS port, node, routing table; a separate port per ETN11-type unit

What we check first

This is TDL's practice, not an AVEVA requirement.

  • We take a backup of the PLC program before any change on the PLC side.
  • We note the CPU, firmware and port the driver will use (on-board, CP, ETN or QJ71E71) and compare them with AVEVA's lists.
  • We trace the network path, switches and FINS networks between the AVEVA node and each PLC.
  • We ask the plant whether PUT/GET and turning off optimized block access are allowed; both change the PLC project, and the Symbolic object avoids them.
  • We plan device groups by rate, and for SIDIRECT watch $SYS$Load and failed reads after start-up.
  • We agree tag names before mass import: device item aliases from CSV, or Auto-Build for S7-1500 symbolic tags.

How TDL approaches it

TDL Industrial Automation is a System Integrator member of the AVEVA Partner Ecosystem. Our AVEVA service page describes connecting the AVEVA software we build and maintain to Allen-Bradley and other control systems, with PLC, Modbus, BACnet and OPC UA data through KEPServerEX and gateways. At SEHC a new air compressor reached the FMCS SCADA on AVEVA System Platform through a Modbus RTU to Modbus TCP converter and KEPServerEX; at SEHC VD5 failed Siemens PLCs were replaced by a CompactLogix. See also connecting existing PLCs to SCADA and InTouch HMI troubleshooting. Modbus devices on AVEVA's MBTCP driver are covered in Modbus RTU and TCP for SCADA, and the drivers other platforms document for the same PLC families in Siemens, Mitsubishi and Omron PLC drivers compared.

Frequently asked questions

Which AVEVA driver connects to a Siemens S7-1200 or S7-1500?

SIDIRECT. Its Legacy object uses absolute addresses and needs PUT/GET permitted and optimized block access turned off; its Symbolic object reads symbolic names with or without optimized block access.

Why does the SIDIRECT Legacy object get no data from an S7-1500?

AVEVA lists the PLC-side conditions: PUT/GET permitted from a remote partner, an access level other than No Access, and optimized block access cleared in each data block. If it still fails, go offline, rebuild all and download again.

What goes in the Station field for a Mitsubishi iQ-R?

iqr: followed by the IP address and port, for example iqr:10.168.25.74:5002. A Q, QnA or L PLC uses the IP address and port without the prefix.

Can OMRONFINS connect through an Omron EtherNet/IP card?

AVEVA states that connection through an ETN Ethernet unit is tested and supported, and through an EIP Ethernet card it is not. The driver talks FINS over UDP, typically on port 9600.

Why can only one of two Omron PLCs with older ETN units connect?

AVEVA says the driver does not support simultaneous connections to older ETN units or to newer ones in ETN11-compatible mode. Give each PLC its own FINS port and enter the full IP address and port in each station.

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:
AVEVA (Wonderware) Connecting existing equipment to SCADA