IMDTouchKnowledge BaseShop main store

Selection guide

Do You Need SCADA Software for a Modbus HMI Project

HMI and touchscreens Published 7 min read

Short answer

No. Modbus only proves a possible data link, so pick the runtime target first: a touch panel programmed by its own editor for machine-side parameter control, or a licensed PC SCADA runtime when the screens must run on a computer. The documented demonstration mode of a Vijeo Citect-class runtime stops after about 15 minutes with live devices, which settles a bench test but not continuous operation.

On this page
  1. What Modbus decides and what it does not
  2. Pick the runtime target before the license
  3. The panel route: two editors are a valid architecture
  4. The PC SCADA route: license and demonstration limits
  5. Budgeting demo time for a 30-minute Modbus demonstration
  6. Getting the Modbus link right once the target is chosen
  7. The decision
  8. Questions asked

No. A Modbus data-exchange requirement does not by itself mean you need SCADA software such as Vijeo Citect. Modbus proves a possible data link between two devices; it says nothing about which editor builds your screens or which runtime you must license. Decide where the operator screens run first. A machine-side parameter interface with a touch panel already in the parts list belongs to the panel route: the panel is programmed by its own editor and the PLC by its own engineering tool, and Modbus carries the values between them. SCADA software enters when the screens must run on a PC as a supervisory application — and then it is licensed software whose documented demonstration mode runs about 15 minutes with live devices, or 10 hours with simulated tags only. Cracking, registration tricks and dongle workarounds are not commissioning options; the license, the documented demo and academic arrangements are.

What Modbus decides and what it does not #

Modbus is a register-level protocol. When both endpoints speak it, the HMI can read and write registers in the controller — and that is everything the protocol guarantees. It does not establish that your editor can build an application for the panel, that the download will take, or that a PC runtime is entitled to run unsupervised. Those are three separate gates, and each one belongs to a different tool.

A Schneider PLC in the project therefore does not force Schneider HMI software, and a free controller tool does not become a free HMI tool. Select by target, not by brand and not by protocol. Where the narrower question is which small package fits simple Modbus I/O, selecting lightweight HMI software for Modbus I/O control covers that ground.

Pick the runtime target before the license #

Read the intended runtime target out of the project specification before anything is bought or installed: a Windows PC running a supervisory application, or a dedicated touch panel running its own firmware. The software list follows from that single answer, and the choice between a headless HMI server and an operator panel is the same split seen from the hardware side.

Engineering task Software that does it Selection gate
Operator screens on a dedicated touch panel The panel's own editor, for example Vijeo Designer on supported Magelis targets The exact panel model appears in the editor's supported-target list
Supervisory screens, historians, multi-controller access on a PC A PC SCADA runtime of the Vijeo Citect / Citect SCADA class Runtime supported on the PC's OS, Modbus driver present, runtime license purchased
PLC control logic SoMachine or SoMachine Basic The exact controller appears in the tool's supported-device list
Servo drive setup and diagnostics SoMove, where the drive is supported Drive model and connection method on the tool's supported-device list

Editor-to-panel matching is a check of its own, separate from the protocol: which HMI software works with which panel hardware lists the manufacturers' tool-to-target pairs. Confirm the controller — an M241 is the usual candidate in this class of machine — in its own tool's supported-device list, independently of the panel check.

The panel route: two editors are a valid architecture #

Nothing in Modbus requires the PLC and the HMI to share one project file. The clean default for a machine-side parameter interface is two tools: the controller programmed in its own environment, the panel programmed in its own editor, and the configured Modbus link between them. Parameter ownership stays where it belongs — the HMI requests a change, and PLC logic decides whether the value and the machine state accept it.

One environment covering both targets is a genuine convenience where it exists, and it does exist for controllers that integrate the screen and the logic in a single unit. That is settled by the complete catalog number in the supported-device list, not by the brand on the box and not by a family nickname quoted in a discussion. If the panel's full model is not a listed target of the controller tool, run two projects.

License state is per tool and per edition. Download access, engineering use and deployed runtime entitlement are three different questions; read the license terms of the exact edition you install.

The PC SCADA route: license and demonstration limits #

Vijeo Citect and its Citect SCADA lineage need a runtime license for normal operation. The documented alternative for development is demonstration mode, and the vendor's own material fixes its limits: a short mode of approximately 15 minutes that may communicate with real I/O devices — the vendor's FAQ words it as about 15 minutes with unlimited dynamic points, and the installation guides of that era cap the mode at 50,000 real I/O — and a long mode of 10 hours that runs memory tags only, with no live device data. When a window closes, the runtime stops.

Buy the license through the manufacturer or its distributors, or through an academic arrangement if your institution holds one. Those are the legitimate paths, and they are also the fast ones: a runtime that stops and reports a demonstration limit is in a licensing state, not a Modbus fault, and no register debugging will move it.

Budgeting demo time for a 30-minute Modbus demonstration #

Inputs: the cell must show parameter control over Modbus, with values read live from the controller — that is the point of the build. The required continuous run for the demonstration is 30 min. The documented short demonstration window is approximately 15 min and allows real device data; the documented long window is 10 h and allows none.

Rule in words: only the mode that permits live device data counts toward the run. Divide the required run time by that window to get the number of windows, and the manual restarts are one fewer than the windows. A mode that excludes external I/O contributes zero minutes of live operation whatever its length.

Arithmetic: 30 min ÷ 15 min per window = 2 windows, so 2 − 1 = 1 manual restart in the middle of the demonstration. Long mode: 10 h × 0 live Modbus points = 0 min of live data.

Result and decision: one stop-and-restart halfway through the run. Above 15 min of unattended operation with live device data, demonstration mode fails the requirement — license the PC runtime, or move the screens to the touch panel. Since a touch panel is already in this project's parts list, the panel editor is the selection, and the PC demonstration mode stays on the bench for development.

Three checks, in order. Transport first: Modbus TCP needs IP addresses and reachability; Modbus RTU needs matched baud, parity and stop bits plus verified wiring. Roles second: one side initiates requests and the other responds, so a reachable device that receives no valid requests has a role or driver problem, not an addressing one. Register map third: configure one documented read-only value and check register type, address convention, data width, signedness, scaling and word order before any write. Modbus moves registers, not engineering meaning — an address offset selects the wrong register, and a scaling mismatch produces a plausible wrong number. When the HMI disagrees with the same quantity in PLC monitoring, fixing Modbus TCP addressing errors between an HMI and a PLC walks that branch.

The decision #

For one machine, one operator position, parameters over Modbus and a touch panel in the parts list, you do not need SCADA software. Program the panel in its own editor, program the controller in its own tool, and let Modbus carry the values.

The PC SCADA route earns its license when one station must supervise several controllers, or must provide historians, recipes, alarm databases or remote clients a panel does not. Then buy the runtime license — and when the screens belong at the machine rather than in a control room, mount the runtime on industrial panel PCs so the supervisory application has a touchscreen computer at the cell.

Use the short demonstration mode for what it is: a bench tool that proves the driver and the screens before the license arrives.

Questions asked

How long does the Vijeo Citect demonstration mode run before it stops?

About 15 minutes with live device data allowed; when the window closes the runtime stops and you start it again by hand, which suits bench testing but not an unattended demonstration. A separate 8-hour mode with up to 42,000 real I/O exists only through special Vijeo Citect Integration Partner keys, so it is not something you switch on yourself.

Can the 10-hour demonstration mode run my real PLC values?

No. The long mode excludes external device data and runs memory tags only, so live Modbus values from the controller are not part of it. Its purpose is screen development and logic testing with simulated data, which is still useful: build and exercise every screen in the 10-hour mode, then switch to the short mode only when you need the real device connection.

Can SoMachine program the HMI as well as the PLC?

Only when the exact HMI model appears in that editor's supported-target list. A controller-family name or a discussion-board suggestion does not establish it. Some controllers integrate the screen and the logic in one unit and are programmed together, decided by the complete catalog number rather than the brand. If your panel is not a listed target, two projects over Modbus is the correct architecture, not a workaround.

Is SoMachine free to use?

The documented split is this: Schneider Electric publishes SoMachine Basic as free software created for its smaller controller range, and the full SoMachine as licensed software for the wider range. A version number quoted in a discussion is not a license statement. Read the license terms of the exact edition you install, and treat download access, engineering use and deployed runtime entitlement as three separate questions.

When is a SCADA license worth it over a panel?

When one station must serve several controllers, or the application needs historians, recipes, alarm databases or remote clients that a single panel does not provide. One licensed PC runtime can poll multiple controllers when its driver list, ports and documented connection limits support the combination, and that consolidation, not Modbus itself, is what earns the license. A single machine with one operator position belongs on a panel.

Keep reading

  • Troubleshooting

    Why an HMI Transfer Fails in Initial Start Mode Despite Ping

    Ping success proves only that the panel's IP stack answers. On a new Magelis XBTG in Initial Start Mode, run three checks in order: build in the engineering version that still supports the target (Vijeo Designer 6.2 for XBTG), clear the license so the download command activates, then load runtime and application over one transport at a time.

    HMI and touchscreens

  • How-to

    Using a VNC Viewer object on an HMI to display other panels

    The VNC Viewer object is a VNC client, so a display-equipped host running the required OS can show any panel or PC that runs a VNC server, not just its own family. On cMT-series hosts the session appears only on the panel's own screen, never through the cMT Viewer app and never in online simulation. Use WebView for remote access.

    HMI and touchscreens

  • Selection guide

    Selecting an HMI That Talks Modbus RTU to Remote I/O

    Select the HMI whose exact software release documents a Modbus RTU client driver that can open the serial port, or route the data through a supported communications server. Prove the choice by polling one module and reading the driver diagnostics before comparing graphics or scripting.

    HMI and touchscreens

Building a complete on-screen keyboard from bitmap HMI assets