IMDTouchKnowledge BaseShop main store

Selection guide

Running Third-Party HMI Software on a Marine Display Host

HMI and touchscreens Published 6 min read

Short answer

Keep the marine monitor: it only displays what the industrial PC host draws, so the software decision belongs on the host. Test whether the installed Infilink runtime can deliver the graphics and the smartphone or tablet access; where it cannot, select a replacement runtime with documented operating-system support, licensing and a Modbus TCP driver, and prove it on an isolated bench before rebuilding screens.

On this page
  1. What the monitor does, and what the host does
  2. Three approaches, one decision
  3. Verify the host before selecting software
  4. The Wago 750 end of the link
  5. Phone and tablet access
  6. Commission on a bench, not on the boat
  7. Bench proof for one marine station: four objects, seven checks
  8. The decision by case
  9. Questions asked

Run the third-party HMI software on the industrial PC that already feeds the marine monitor, and leave the monitor alone. The marine display renders whatever the host draws on its video cable, and its touch reports come back over USB, so nothing about screen appearance or phone access lives inside the monitor. The decision sits on the host. The installed Infilink runtime already documents graphics, trends, alarms, scripting and Modbus RTU and TCP connectivity, so the first test is whether its current build also delivers the presentation your customer wants and a smartphone or tablet client. Where it cannot, replace the runtime on that same PC, after verifying host support, licensing and the driver, and prove the replacement on a bench before any screen gets rebuilt.

What the monitor does, and what the host does #

The monitors in this installation network into an industrial PC or into a marine navigation black box. The industrial PC runs the HMI/SCADA runtime, Infilink in this plant, and exchanges data with Wago 750 controllers over Modbus TCP on Ethernet. A different look on the screen is therefore a host-software change: the monitor keeps rendering, the host decides what to render.

Durability is why these monitors were bought, and a software swap does not touch it. Hold one boundary, though: the display's marine rating says nothing about the industrial PC, the Ethernet switch or any remote-access hardware. Each of those carries its own environmental rating and is verified on its own.

Three approaches, one decision #

Approach Where the change happens What decides it Main engineering impact
Revise the installed Infilink project Existing industrial PC and its project file Whether the installed runtime documents the graphics depth and the remote clients needed Communications, tags and alarms stay; smallest migration
Replace the HMI/SCADA runtime Same industrial PC, new software Operating-system support, licensing, a Modbus TCP driver, graphics tools, mobile client support Screens, tags, alarms and commands rebuilt or imported
Add phone and tablet access Runtime client plus the remote-access layer Client support, authentication, connection security, permitted actions Network and operator-authority decisions even with local screens unchanged

Order the work by cost. A small graphics prototype in the installed project is the cheapest test, the mobile-client question comes next, and full runtime replacement is what you choose when the first two fail on documented capability rather than taste. The candidate runtimes for a Modbus TCP controller are compared in choosing a PC-based HMI runtime for a Modbus TCP PLC, and the wider criteria for replacing a DCS SCADA system with third-party SCADA software apply when the incumbent package reaches beyond one operator station.

Verify the host before selecting software #

Identify the actual computer first, because a monitor, an industrial PC and a navigation black box are different components. If the screens turn out to run on the navigation box, its committed functions and installation restrictions argue against loading an HMI runtime onto it.

From the host's own system information, record the model, operating-system edition and build, processor architecture, memory, storage, display resolution and touch interface. The interface pattern on a documented 12.1-inch monitor of this class: touch returns over USB through a Type-B socket, and the video inputs are DisplayPort, DVI-D shared with HDMI, and HDMI. The host therefore needs one free USB port and one matching video output. If the existing PC is inadequate or reserved for other work, industrial mini PCs drive a separate display and can carry the runtime while the marine monitor stays where it is.

Check the candidate's supported host requirements and its licensing through the manufacturer or an authorized distributor. A recommendation from another user endorses a package's tools; it is not a compatibility result for your computer.

The 750 family name alone does not identify the controller; read the exact model and obtain its register map. Before any migration, document the Modbus TCP endpoint, register addresses, data types, scaling, word order and read/write permissions.

Modbus TCP moves addressed registers and nothing more; it carries no engineering meaning. Meaning lives in the tag database, so a successful connection proves connectivity, never correct interpretation. Because HMI drivers present register references differently, an address string copied verbatim between packages can target a different location: compare the driver's convention against the controller map and prove one known value before moving the tag database.

Phone and tablet access #

Decide viewing versus control first, because every remote client that can write is an operator station. Prefer the runtime's own web or smartphone client over a remote-desktop path when one is documented. Put authentication on it, carry it over a VPN or a segmented network, and grant the mobile account write rights only where an operator at the panel would have them. Start read-only; the method is laid out in making remote HMI access read-only over RDP. Keep the safety interlocks in PLC logic so no screen, local or remote, can bypass them.

Commission on a bench, not on the boat #

Put the pilot on an isolated bench with verified test tags, never on the running plant. Build one representative screen holding a live numeric value, a changing status, an alarm indication and one authorized command. Compare raw values against the controller's engineering tool before applying any scaling, and test the command write only under supervision, confirming that the PLC logic accepts or rejects it as designed. Pull the controller link once and restart the host once; both must recover without manual intervention. The same prove-first method is walked through in how to prove a PC-based HMI before replacing panel terminals.

Bench proof for one marine station: four objects, seven checks #

Inputs. One marine monitor, retained, fed by the host over video with touch returning over USB, per the interface pattern above. One industrial PC host, operating system recorded from its system information. One Wago 750-series controller reached over Modbus TCP on Ethernet, which is the plant as installed. The requirements carried from the job: graphics the customer accepts, and viewing from a smartphone or tablet. The pilot screen carries four objects: one live numeric value, one changing status, one alarm indication, one authorized command.

Rule. A candidate earns the rebuild only when every object verifies against the controller, the mobile client shows the same live data over its real network path, and the application survives one link pull and one host restart with no manual intervention.

Arithmetic. Object checks: 3 reads plus 1 write = 4. Mobile-client session: 1. Resilience: 1 disconnect with recovery plus 1 restart with reconnect = 2. Total: 4 + 1 + 2 = 7, and the pass mark is 7 of 7.

Decision. Seven of seven, together with documented operating-system support, licensing and a Modbus TCP driver on that host, commits the rebuild on the industrial PC and keeps the marine monitor in place. Any single miss keeps the candidate on the bench and changes nothing in the plant. The installed Infilink project runs the same seven checks; if it passes and its vendor documents a mobile client, revise the graphics in place and skip the replacement.

The decision by case #

The vendor documents that the installed Infilink build covers the graphics and a mobile client: revise the project in place. Monitor, host and Modbus TCP configuration stay untouched.

The mobile client or the graphics depth is not documented for Infilink: replace the runtime on the industrial PC and keep the monitor. InduSoft Web Studio is one candidate with documented Modbus TCP connectivity; treat it as a bench candidate, not as a compatibility determination for your host.

The screens run on the navigation black box: do not add a runtime there. Move the application to the industrial PC or to a separate host computer.

The monitor itself fails: replace the display unit and keep the software. The runtime investment survives the hardware swap, which is the point of hosting it on the PC.

Questions asked

Does the marine rating on the monitor cover the rest of the station?

No. The rating belongs to the display enclosure alone. The industrial PC, the Ethernet switch, the power supply and any remote-access hardware each carry their own environmental ratings and enclosure strategy, so verify dust, corrosion and mounting for every part before calling the station marine-grade.

Can the new runtime go on the navigation black box instead of the industrial PC?

Not as a first choice. A navigation appliance reserves its processor and storage for committed functions and may carry installation restrictions from its manufacturer. Keeping the HMI runtime on a separate computer also means a graphics fault cannot take the navigation functions down with it.

Why would a tag read wrong after moving to the new package?

Drivers present Modbus register references differently, so an address string copied between packages can point at a different register. Recheck data type, scaling and, for values spanning multiple registers, word order against the controller's register map, then re-verify every scaled value on the first live run.

What is the cheapest path to phone viewing?

If the installed runtime's vendor documents a web or smartphone client, enabling it is configuration work: start the client service, publish it through a secured network path, and issue accounts. If no client is documented, no setting creates one, and mobile access becomes a selection criterion for the replacement runtime instead.

How do we stop a tablet from starting machinery?

Give the mobile client its own account with write rights removed for anything that moves equipment, keep confirmation steps on commands, and leave the interlocks in PLC logic. Remote viewing and remote control are separate permissions, so grant them separately and audit who holds the write rights.

Keep reading

  • Selection guide

    How to Prove a PC-Based HMI Before Replacing Panel Terminals

    Use an isolated bench controller to compare candidate PC-based HMI runtimes. Test the read path, one write to a spare test tag, touch response, communication loss and automatic recovery. Check the deployed license on the target PC.

    HMI and touchscreens

  • Comparison

    Choosing Free Modbus HMI Software for a Windows Panel PC

    For a Windows panel PC that must show Modbus TCP data and alarms, Ignition Maker Edition and VTScada Lite are the only candidates with a free tier and a specific Modbus TCP claim on record. Maker Edition is documented free for non-commercial use only, so production machines bench-test VTScada Lite first or fall back to code-based AdvancedHMI.

    HMI and touchscreens

  • Selection guide

    How to Choose HMI Software for a New Control System

    Count operator stations, controllers and connections first, keep sequencing and permissives in the PLC, and pick the smallest architecture that meets the full requirement. One station with no logging duties takes a dedicated panel; multiple stations needing simultaneous control or sustained history take a PC-based runtime.

    HMI and touchscreens