IMDTouchKnowledge BaseShop main store

How-to

Connecting an HMISTO735 to an M241 PLC with Vijeo XD

HMI and touchscreens Published 7 min read

Short answer

Commission the HMISTO735 to M241 link in three layers: a driver and endpoint both Vijeo XD and the SoMachine project support, a proven Ethernet path with addresses and a ping, then one exposed test variable passed read and write end to end. Build screens only after that loop closes, and fix each fault at the first layer that fails.

On this page
  1. Commission the layers in this order
  2. Match the driver and endpoint in both tools
  3. Prove the link before you configure
  4. Worked example: a 192.168.1.x bench link on port 502
  5. Pass one test variable end to end
  6. Read the fault from its layer
  7. Close the loop before you build screens
  8. Questions asked

The HMISTO735 talks to the M241 over Modbus TCP on the controller's embedded Ethernet port: the panel connects as the client, the controller answers as the server. On the software pair this job runs — Vijeo XD V2.4 on the panel, SoMachine V4.2 on the controller — the connection does not exist until you commission three layers in order: a driver and endpoint both projects support, a network path you have proven with real addresses and a reachability test, and one exposed test variable passed read and write end to end. Installing SoMachine does not create the HMI connection, and two variables with the same name in both tools are not the same variable until the driver maps them to the same register. Work one layer at a time and every fault tells you which layer it belongs to; the loop you are driving toward is one variable, both directions.

Commission the layers in this order #

Fix the order before you touch either tool, because the order is what isolates a mapping fault from a cable fault:

  1. Driver and endpoint. Pick the protocol and interface both the HMISTO735 hardware and the M241 configuration support, and record the driver name and the connection parameters it needs. The panel and software names alone do not identify a protocol.
  2. Link and addressing. Connect the Ethernet path, read the IP address and subnet mask on both sides, and prove reachability.
  3. HMI configuration. Enter the verified endpoint in Vijeo XD, validate the project, download it, and confirm the runtime starts.
  4. One test variable. Expose one safe internal word in the SoMachine project and reference it in Vijeo XD.
  5. Read and write. Pass that single variable in both directions while you watch both ends.

A fault belongs to the first layer that fails. Until one variable moves both ways, do not bind any screen object beyond the test display.

Match the driver and endpoint in both tools #

Schneider Electric documents controller-to-HMI setup and variable linking for the M238, M241 and M251 range in FAQ FA339984; treat it as the controller-side reference for this connection. The controller side is the same one in the guide to connecting an XBTGT HMI to an M241 PLC over Modbus TCP; what differs is the panel side, because the STO project lives in Vijeo XD rather than Vijeo Designer.

In Vijeo XD, open the device or communication configuration of the panel project and select the driver that matches the M241 over Modbus TCP, then fill in that driver's own fields: controller address, port and protocol options. Do not copy connection settings from a project built for a different controller; similarly named devices do not share addressing.

Keep the controller's Ethernet services straight. Modbus TCP IO Scanning, which Schneider documents for the M241 in EcoStruxure Machine Expert (FAQ FA412154), makes the controller the client that polls remote devices. Your HMI attaches to the controller's Modbus TCP server service instead, with the panel as the client. Configuring IO Scanning for the panel will not connect them.

Decision: a panel driver that speaks the protocol the controller actually serves, plus a running controller application with that service enabled, lets commissioning continue. If your Vijeo XD release lists no driver match for the M241, stop there — no cabling or tag work fixes a missing driver.

A lit link LED confirms copper, not conversation. Do this before any driver settings:

  • Connect the panel and controller to the same network and confirm link indication on both ends.
  • Read the IP address, subnet mask and gateway from the Vijeo XD device settings and from the M241's Ethernet configuration in the SoMachine project; both addresses must be unique on the network.
  • Ping the controller's address from a laptop or the panel's own diagnostics, on the same network, and record the result.

Decision: no link light points at power, ports or cabling. A link light with no ping reply points at addressing or routing. A passing ping proves reachability only — it earns you permission to configure the driver, it does not prove the connection works.

Inputs, and where each comes from:

  • Panel address 192.168.1.50 with mask 255.255.255.0 — what you would enter in the Vijeo XD device settings (illustrative bench values).
  • Controller address 192.168.1.10 with mask 255.255.255.0 — set in the M241's Ethernet configuration inside the SoMachine project (illustrative bench values).
  • Modbus TCP port 502 — the documented default on the M241 and M251, per Schneider FAQ FA372974.
  • Tools: Vijeo XD V2.4 and SoMachine V4.2, the versions on this job.

Rule in words: two hosts on one link exchange Modbus TCP directly when masking each address with the subnet mask leaves both on the same network, and the Vijeo XD endpoint must repeat the controller's address and the port its service listens on.

Arithmetic, octet by octet, AND with the mask:

  • 192.168.1.50 AND 255.255.255.0: 192 AND 255 = 192, 168 AND 255 = 168, 1 AND 255 = 1, 50 AND 0 = 0, giving 192.168.1.0.
  • 192.168.1.10 AND 255.255.255.0: the same first three octets, 10 AND 0 = 0, giving 192.168.1.0.
  • Both masked networks are 192.168.1.0, so the hosts sit on the same subnet and no gateway is needed on the bench.

Result: the Vijeo XD endpoint for this bench is 192.168.1.10, port 502.

Decision: with link LEDs lit, ping 192.168.1.10. If the ping fails, the fault is addressing — correct the addresses, never the tags. Leave the port at 502; any other port value in the panel project is a fault unless your application deliberately moved the controller's port by Schneider's documented method.

Pass one test variable end to end #

In the SoMachine project, declare one internal word you can change safely during commissioning — a spare integer that no control logic depends on — and expose it the way your driver expects, by symbolic exchange or by mapped register address. Use one convention and never mix the two.

In Vijeo XD, create the matching variable: same data type as the controller declaration, the address or symbol the driver expects, and access set to read and write. Bind exactly one screen object to it — a numeric display — then validate and download the project.

Read test: change the word in the running controller and watch the panel display follow it. Write test: enter a bounded value at the panel and confirm the controller word takes it. Write only to that test word, never to a physical output the machine depends on, and keep the controller's interlocks in force; an HMI write lands in a data word and cannot drive a physical input, which the guide to why an HMI toggle switch cannot write a physical PLC input explains from the addressing side.

If the panel is not on the bench yet, prove the same mapping against a running controller in simulation first — the article on testing HMI simulation against a live PLC shows that setup.

Decision: one variable passed read and write closes the layer. That single two-direction loop, not a successful download and not a lit LED, is the number this commissioning turns on. Only then bind the rest of the screens.

Read the fault from its layer #

What you see Layer that owns it Next check
No link LED on either port Physical Power, patch cable, switch port
LEDs lit, ping fails Addressing Compare address and mask on both sides, repeat the ping
Ping passes, panel shows a device or connection error Driver or controller service Driver family, controller address, port 502, controller application running
Panel connects, tag invalid or value never moves Mapping One known variable end to end, type and access rights first

Change one item at a time and repeat the same test after each change, so a passing attempt names the layer you corrected. If you run the M241's serial port instead of Ethernet, the symptoms read differently; the article on fixing HMI Modbus device no response over RS-485 covers that path.

Close the loop before you build screens #

Record what passed: driver name, endpoint address and port, the ping result, the test variable's reference and type, and the values from the passing read and write. Then restart or reconnect the panel with its approved procedure and repeat the read test; the runtime should reconnect and the display should follow again.

Decisions by case:

  • Loop passes: build the screens — driver, path and mapping are all proven.
  • No driver match in your Vijeo XD release: choose another documented common path, a protocol both the panel's driver list and the M241 serve, before entering any variables.
  • Read passes, write fails: check the variable's access rights and the driver's write handling; the connection itself is fine.
  • Same-name variables that never resolve: that is the mapping layer, not the connection — fix the reference, not the cable.

Questions asked

Is the HMISTO735 project created inside SoMachine like other M241 HMI setups?

No. SoMachine V4.1 can embed Vijeo Designer so the HMI configuration lives inside the controller project, but that workflow covers the panel families it was built for, not the STO. The HMISTO735 is programmed in Vijeo XD, so the HMI project, its variable list and its transfer all live there, and the two tools meet only over the configured Ethernet connection.

What port does the M241 use for the HMI connection?

Port 502, the Modbus TCP default. Schneider documents that changing the Modbus TCP port on an M241 or M251 is done with a script command loaded from an SD card, not from a project setting. Unless your application deliberately does that, enter 502 in the Vijeo XD endpoint and treat any other port value there as a connection fault.

Do the SoMachine variables appear automatically in Vijeo XD?

No. Vijeo XD keeps its own variable list, and nothing publishes the controller's variables into it. You create a reference for each controller word you want on screen, matching the data type and the address or symbol the driver expects. When validation rejects a tag or the object stays unavailable, suspect a type or address mismatch first, not the network.

Does the same procedure cover the HMISTO715?

Yes, with the panel-specific settings changed. The HMISTO715 runs the same Vijeo XD workflow against the same controller services, so the layer order, the addressing check and the one-variable read and write test all apply unchanged. Only the panel model selection, its transfer settings and the screen size differ, so verify those against your Vijeo XD release before downloading.

The panel connects but some numeric values read as garbage. What is wrong?

Data type or word order. A REAL occupies two Modbus registers, and a 32-bit value with swapped words or an integer read as a floating-point number displays plausible nonsense. Recheck the Vijeo XD variable's type against the SoMachine declaration, then the word order the driver uses for REAL values, before suspecting the network or the panel.

Keep reading

  • How-to

    Connecting an XBTGT HMI to an M241 PLC over Modbus TCP

    Delete the Generic Modbus TCP slave from the M241 device tree and activate the Modbus server on the controller's Ethernet interface instead — that slave makes the M241 a client, so both devices poll and neither answers. Then map Vijeo Designer driver address 40001 to PLC word %MW0, keep TCP port 502 open between panel and controller, and shift the address map by one word if a test read lands one register off.

    HMI and touchscreens

  • Troubleshooting

    Why Vijeo Designer cannot connect to an M580 PLC

    The HMI fails to reach an M580 because one leap hides which layer broke. Match the project target to the HMIGTO, prove the computer-to-panel transfer path and the panel-to-PLC runtime path as two separate tests, add the Modbus TCP equipment the controller actually serves, then prove communication with one forced read and one approved write before any faceplate. Each layer gives a pass or a named fault.

    HMI and touchscreens

  • How-to

    Adding a Modbus RTU Driver and External Variables in Vijeo Designer

    Add one Modbus RTU equipment driver on the HMI serial port, set the baud, parity and stop bits every slave shares, and give each device a unique slave address. Then create one external variable per value, pointing it at that device and its documented register with the matching data type. Mismatched serial settings or duplicate addresses show up as read timeouts, so commission one device at a time.

    HMI and touchscreens