IMDTouchKnowledge BaseShop main store

How-to

Simulating a Basic HMI against a real TM172 HVAC controller

HMI and touchscreens Published 5 min read

Short answer

Yes, but only with the physical TM172 present: the Windows simulation replaces the HMI panel, never the controller. Run the HMI application in simulation as a Modbus TCP client to the controller's port 15797, or as a Modbus RTU master with the PC's RS-485 converter assigned to COM2. Without the physical controller there is no live application data to test against.

On this page
  1. What the simulation replaces, and what it cannot
  2. Prepare the controller before the panel
  3. Modbus TCP simulation, step by step
  4. Modbus RTU simulation, step by step
  5. Worked example: accepting a TCP simulation test on port 15797
  6. Choosing between TCP and RTU
  7. Symptoms and what each one tells you
  8. Questions asked

Yes, simulation testing between EcoStruxure Machine Expert-HVAC and Vijeo Designer Basic works, with one hard condition: the physical TM172 controller must be connected and running. Without the physical device, the HVAC application cannot serve data to the HMI, so there is nothing to simulate against. The HMI panel itself is optional in every case. Run the HMI project in Windows simulation mode and treat the engineering PC as the panel — a Modbus TCP client to the controller's configured port 15797, or a Modbus RTU master with the PC's RS-485 converter assigned to COM2.

What the simulation replaces, and what it cannot #

The Windows simulation substitutes for the panel, never for the controller. Screen navigation, animations and local behavior run without an external endpoint; live reads, writes, alarms and status indications need the physical TM172 to supply application data. The pattern is the same one behind testing HMI simulation against a live PLC: the simulated panel always talks to a real controller endpoint.

Test arrangement Result What stays physical
HMI simulation over Modbus TCP, controller port 15797 Works Controller only
HMI simulation over Modbus RTU, converter on COM2 Works Controller only
HMI simulation with no controller connected Not supported Nothing — no live data source

The controller appears as both TM172 and M172 in documentation and setups. Read the exact designation from the device label and the project configuration before commissioning; the requirement for a physical controller is the same under either name.

Prepare the controller before the panel #

  • Confirm the physical TM172 is powered and running the intended HVAC application, and that the device and application identity match the HMI project.
  • For the TCP path, set port 15797 on the controller first, over a USB connection, through the controller's web page, or with the ESME HVAC software.
  • For the RTU path, read the serial settings and the station address from the controller and HMI project configuration instead of assuming defaults.
  • Compare the HMI variable map against the controller's data map for at least one known read value and one permitted write value: address, data type, access direction and scaling.

Modbus TCP simulation, step by step #

  1. Connect the engineering PC and the physical controller to the same IP network.
  2. In the HMI project, set the communication driver to client and enter the controller's IP address with port 15797.
  3. Ping that address from the PC, and do not continue until it replies. If it stays silent, correct the address, subnet, cabling or network-interface selection first.
  4. Start the HMI application in Windows simulation mode and confirm the client establishes communication without a connection error or stale values.
  5. Open a screen with a known live value and compare it against the same value in the HVAC application. If the number reads shifted or byte-swapped, the checks behind displaying a PLC real value over Modbus on an HMI apply directly.
  6. If ping passes but data stays stale, check in this order: the port 15797 configuration on the controller, the client target in the HMI project, then the variable mapping. Ping cannot see a closed or misconfigured application port.

Modbus RTU simulation, step by step #

  1. Connect an RS-485 converter to the PC and wire its RS-485 side to the controller's serial connection.
  2. Open Windows Device Manager and assign the converter to COM2. The simulation expects COM2 because that is the port the physical panel uses for RS-485; do not continue until the converter sits there without an error.
  3. Configure the HMI side as the Modbus RTU master and match its serial settings and station address to the configured values. The driver and variable work follows adding a Modbus RTU driver and external variables in Vijeo Designer.
  4. Start the HMI application in Windows simulation mode and watch for data refresh, not merely a screen that opens.
  5. Test one known controller value before sending any operating command. If values stay stale, recheck the COM2 assignment, serial-setting equality, station addressing, converter wiring and RS-485 polarity.

Worked example: accepting a TCP simulation test on port 15797 #

Inputs, each from the machine and project:

  • One physical TM172, powered and running the intended HVAC application — the data source for the test.
  • Controller TCP service configured on port 15797, set over USB, the web page or the ESME HVAC software.
  • One known read variable and one permitted write variable taken from the HMI project's variable map.

Rule in words: the simulation test is accepted only when data moves in both directions — the known read appears in the simulated panel and matches the controller value, and the permitted write produces the intended change at the controller.

Arithmetic: required verified exchanges = 1 read + 1 write = 2. A screen that launches proves only that the runtime started, which counts as 0 of 2.

Decision: at 2 of 2 the communication path is proven — accept the test and move on to screen-level checks. Below 2 of 2, nothing is proven; fix the port, the client target or the mapping before trusting what the screen shows. The write reaches a live controller, so choose a variable and a machine state where the commanded change is harmless.

Choosing between TCP and RTU #

Use Modbus TCP when the controller is already reachable on Ethernet: it removes the COM-port dependency and gives ping as a first connectivity check. Use Modbus RTU when the deployed application uses RS-485, or when the serial path itself is part of acceptance. Never switch transports just to make the simulator connect — a simulation on a transport the machine will never use tests nothing you will run.

Symptoms and what each one tells you #

Observation First check Pass condition
Simulator runs, every live value unavailable Physical controller present and serving data Real TM172 connected and running the application
TCP ping fails IP configuration and network path Controller replies at the address entered in the client
Ping passes, values stay stale Port 15797, client target, variable mapping — in that order Known variables update
RTU simulation cannot open the serial interface Device Manager assignment Converter appears as COM2 without an error
Reads work, a write has no effect Address, data type, access direction, scaling Controller receives the permitted value at the mapped variable

Questions asked

Can I run the test with no physical TM172 at all?

No. Without the physical device, the HVAC application cannot serve simulation data to the HMI, so there is no live endpoint to read or write. A software-only pairing of the HMI and controller tools is documented for SoMachine Basic projects, but the TM172 programmed with EcoStruxure Machine Expert-HVAC is not that case: the controller must be real, powered and running the intended application.

Why must the RS-485 converter be on COM2?

The physical Basic panel uses COM2 for its RS-485 port, and the Windows simulation expects the same assignment on the PC. If Device Manager shows the converter on another COM number, change the assignment to COM2 there before starting the simulation. A converter sitting on any other port is the usual reason the RTU simulation cannot open the serial interface.

Ping succeeds but the simulated HMI shows stale values. What is wrong?

Ping proves only that the controller's IP address is reachable; it says nothing about the application port. Check three things in order: that port 15797 is actually configured on the controller, that the HMI client target matches that address and port, and that the variable mapping is right. A closed or misconfigured port passes ping every time.

Do I need a license to run the HMI simulation?

Yes. Running simulation mode needs a standalone Vijeo Designer license. If the HMI project was created inside the controller engineering software, that license is not included by itself, so confirm it is present on the engineering PC before you plan the test session.

Can I test writes from the simulated panel to the controller?

Yes, and the test is not complete without one. Acceptance needs a permitted write that produces the intended controller-side change: command the variable from the simulated panel and watch the value move in the HVAC application. Keep the machine in a state where a commanded change causes no motion or process upset.

Keep reading

  • 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

  • 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

    Connecting an HMISTO735 to an M241 PLC with Vijeo XD

    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.

    HMI and touchscreens