IMDTouchKnowledge BaseShop main store

How-to

Connecting Operator Terminal Expert to a Third-Party PLC

HMI and touchscreens Published 7 min read

Short answer

Operator Terminal Expert connects to a third-party PLC through a protocol both ends document — typically Modbus TCP or RTU, or OPC UA with the HMI as client and the PLC as server. Select the driver for your exact terminal target, match the driver's address notation to the PLC's register references, and prove one read and one controlled write on the deployed terminal before mapping the rest.

On this page
  1. Can Operator Terminal Expert connect to a non-Schneider PLC at all?
  2. Which protocol do I pick when the PLC offers both Modbus and OPC UA?
  3. What must the PLC side provide before I configure anything?
  4. How do I make Modbus addresses land on the right register?
  5. How do I set up the OPC UA connection?
  6. How do I prove the connection on the real terminal?
  7. What do the failure symptoms point to?
  8. Questions asked

Yes — the connection path is a protocol both ends document, typically Modbus TCP over TCP port 502 or Modbus RTU at a matched slave ID, or OPC UA with the HMI as client on the PLC's server endpoint. For a PLC that exposes both Modbus and OPC UA — a Unitronics PLC offering both is the common case — run Modbus TCP for plain registers or OPC UA for typed variables with quality and security. EcoStruxure Operator Terminal Expert's documented communication technologies include Modbus TCP, Modbus RTU and OPC UA client/server, and the driver is selected when you define the controller connection for your Harmony HMI or iPC target. The decision gate comes before screen building: confirm the driver exists for your exact terminal target and the PLC's enabled service, then prove one changing read and one controlled write on the deployed terminal before mapping the rest of the tags.

Can Operator Terminal Expert connect to a non-Schneider PLC at all? #

Yes — Operator Terminal Expert connects to a third-party PLC whenever both ends support one protocol from its driver list; the documented communication technologies include Modbus TCP, Modbus RTU and OPC UA client/server, and the driver is chosen when you define the controller connection in the project.

The word documented does the work: select the exact terminal model or runtime platform in the project and read the driver list for that target before you trust it. Two devices that both support OPC UA still need complementary roles — the HMI as client, the PLC as server. If no common protocol appears for your target and the PLC's enabled service, stop and ask the vendor's support team to verify the combination with the terminal model and software version in hand, rather than building screens around an unverified driver.

Which protocol do I pick when the PLC offers both Modbus and OPC UA? #

Pick Modbus TCP first when the PLC exposes plain bits and registers: it needs only an IP address, TCP port 502 and a register map, while OPC UA pays off when you need typed variables, quality flags or enforced security on the session.

Modbus moves addressed bits and registers; it carries no symbolic names and no engineering meaning, so you supply the register map and the scaling yourself. OPC UA, standardized as IEC 62541, is the opposite trade: the PLC's server exposes a typed address space, the client browses it, and every value arrives with a quality flag and timestamp — at the cost of endpoint and security configuration. Strings, structured data or a plant network that requires authenticated sessions push you to OPC UA; a quick register-based retrofit stays on Modbus TCP. The client/server shape you need is exactly the one in a documented HMI-to-PLC example, connecting an XBTGT HMI to an M241 PLC over Modbus TCP (article:connecting-an-xbtgt-hmi-to-an-m241-plc-over-modbus-tcp).

What must the PLC side provide before I configure anything? #

Before you configure anything, three PLC-side facts must be in hand: a server service enabled (Modbus server on TCP port 502, or an OPC UA server endpoint — port 4840 by default), a written data map or variable list, and a network or serial path the terminal's port can use.

On Ethernet, give the terminal an address in the PLC's subnet and confirm the service itself answers: a ping reply proves reachability, not that port 502 or the OPC UA endpoint is serving. On serial RTU, match the electrical interface, wiring and termination against the PLC's documentation; the Modbus serial line specification's default line settings are 9600 baud, even parity, one stop bit, rising to two stop bits when parity is none, and the slave ID comes from the PLC's communication settings — read it there rather than assuming. For OPC UA, read the endpoint URL and its security policy from the PLC's configuration; both ends must support the same policy and message-security mode. A connection timeout sends you back to transport and service state; a connected-but-empty variable list points at addressing or access rights instead.

How do I make Modbus addresses land on the right register? #

Treat the printed reference and the driver's address field as two notations for the same number and prove the mapping with one known value: holding-register reference 40011 and zero-based offset 10 are the same register, because 40011 - 40001 = 10.

Worked example: the PLC's documentation places a commissioning test register at reference 40021 and a real setpoint at 40011, both in Modicon 4xxxx notation, where 40001 is the first holding register.

  • If the driver's address field takes the five-digit reference, enter 40011 for the setpoint tag.
  • If it takes a zero-based offset, enter 40011 - 40001 = 10.

An off-by-one shifts every tag by one register, so the setpoint tag would display the neighboring register's value. Never chase a wrong number by nudging the address until it happens to look right — prove one location instead: write 1234 (raw counts) to the test register at offset 40021 - 40001 = 20, and watch 1234 arrive in the PLC's online monitor at the mapped variable.

Representation moves a value even when the address is right. A 32-bit float spans two consecutive registers: 50.0 encodes as 0x42480000, so the PLC holds 0x4248 (16,968) then 0x0000 (0). With the words assembled in the opposite order the pair reads 0x00004248, which has a zero exponent field, so it evaluates as 16,968 / 8,388,608 x 2^-126 ≈ 2.4 x 10^-41 and the tag shows 0 instead of 50.0. Set the word order the PLC documentation specifies, and apply scaling in exactly one layer: read the raw value first, then convert to engineering units on one side, not both.

How do I set up the OPC UA connection? #

Set up OPC UA only after the driver list confirms an OPC UA client for your target: the HMI takes the client role, the PLC the server role, and you enter the PLC's endpoint, then match security policy, message-security mode and authentication before browsing for one variable.

Enter the endpoint URL from the PLC's configuration, not a remembered default, so the session reaches the intended server rather than a device at an old address. Where certificates are required, complete the documented trust exchange on both devices and check their clocks, because certificate validation fails on clock skew. Select one exposed variable — browse if the driver allows it, otherwise enter the node identifier from the PLC's documentation — and match the HMI data type to it. Confirm a read whose value changes and whose quality is good, agreeing with the PLC's online monitor. Check write permission separately: server-side access rights and the HMI-side configuration are two different gates, so test the write on a commissioning variable, not a process value. A successful session proves nothing about variables you have not yet opened.

How do I prove the connection on the real terminal? #

Run the proof on the deployed terminal, not only in simulation: download the project, watch one changing read with valid quality, then perform one controlled write to a spare test point and confirm it in the PLC's online monitor before mapping the rest.

Build nothing more than the two proof screens — a blank project is enough, or start from the software's templates, and the page on where to get EcoStruxure Operator Terminal Expert templates (https://industrialmonitordirect.com/blogs/knowledgebase/where-do-i-get-ecostruxure-operator-terminal-expert-templates/) lists where those files come from. Then:

  1. Record the terminal model or runtime and the software version, and select that exact target in the project.
  2. Confirm the protocol driver for the selected target and create the connection with the endpoint, IP address or serial settings read from the PLC's configuration.
  3. Add one read tag on a test point that changes on its own, such as a counter or status word.
  4. Download the project to the terminal; if the transfer stalls, work through the checks in EcoStruxure Operator Terminal Expert download fails to HMI (article:ecostruxure-operator-terminal-expert-download-fails-to-hmi).
  5. Confirm the read on the terminal: value changing, quality good, matching the PLC's online monitor.
  6. Configure one write to a spare register or commissioning variable — never a live setpoint or output, so the first write cannot move the process.
  7. Perform the write from the terminal and confirm the new value in the PLC.
  8. Only then map the remaining tags, applying the notation and word-order checks from the section above.

What do the failure symptoms point to? #

Match the symptom to the layer before changing settings: no response means transport or service state, a Modbus exception means address range or permissions, a stable wrong value means notation or word order, and reads without writes mean the mapping is not writable.

What the terminal shows Where the fault sits
Timeout, no response IP and subnet, TCP port 502 listening, endpoint URL, slave ID, serial wiring and line settings, client/server roles
Modbus exception returned Register outside the PLC's map, read-only access, quantity or operation not permitted
Stable value, wrong number Address notation off by one, word order, signedness, scaling applied twice
Reads work, writes ignored Mapping not writable, server write rights, PLC logic overwriting the register each scan
Good session, variable missing Node not exposed by the server, access rights, wrong node identifier

Questions asked

Can I test the screens in a simulator before the third-party PLC is available?

Yes, for screen layout only. The software's simulator runs a project without hardware, and the vendor documents linking the Operator Terminal Expert simulator to the EcoStruxure Machine Expert simulator, which covers Schneider PLC pairs. A third-party PLC has no matching simulator link, so treat simulator runs as layout checks and keep the protocol proof on the real terminal.

What slave address range can a Modbus RTU PLC use?

The Modbus serial line specification allows slave addresses 1 through 247. Address 0 is reserved for broadcast writes and 248 through 255 are reserved, so give each PLC on a shared RS-485 bus its own address in that range and set the HMI driver's device ID to match.

What if the PLC offers neither Modbus nor OPC UA?

Then there is no documented driver path, so do not build the project around an unverified combination. Send the terminal model and software version to the vendor's support team for a driver check. The usual fallback is a protocol gateway that speaks the PLC's own protocol on one side and Modbus on the other, added to the project as its own server device.

Does a driver shown in the desktop software always run on my terminal?

Not necessarily. Driver availability depends on the selected target, so a desktop software version can list more drivers than a particular terminal or iPC runtime actually implements. Select the exact terminal model or runtime platform in the project and confirm the driver appears for that target before you build the tag database.

Keep reading

  • Explainer

    HMI OPC UA Server vs Client: Which Direction Works

    OPC UA support on an HMI spec sheet almost always means the panel runs a server that serves its tags to external clients. Reading PLC symbols by name needs an OPC UA client driver, a separate capability you verify in the driver list for your exact software release, target and license.

    HMI and touchscreens

  • How-to

    Connecting an Omron CV1000 PLC to WinCC over an OPC server

    Classic WinCC has no Omron CV-series channel, so the working route is an OPC server that speaks Host Link to the CV1000 and OPC DA to WinCC. Configure the server against the PLC first, prove one read, then build WinCC tags from the server's item addresses. Use the documented CV1000-CPU01-EV1 Host Link reference values: ASCII, 7 data bits, even parity, 2 stop bits, unit 00, 9600 or 19200 bps.

    HMI and touchscreens

  • Selection guide

    Choosing a PC-based HMI runtime for a Modbus TCP PLC

    No — C-more projects deploy to C-more panel hardware, so a PC-only interface needs a PC runtime instead. Run AdvancedHMI, a PyQt5 front end with pymodbus, or an Excel VBA socket client as the Modbus TCP client, with the PLC acting as the server on TCP port 502.

    HMI and touchscreens

How to Split Modbus Register Bytes in Operator Terminal Expert