NEXT HMI 1.1.0: less glue in the PLC, ready to ship.

1.0 settled the project format. 1.1 removes the helper tags, hand-off variables and custom widgets that screen logic used to need, and gives you everything to put NEXT HMI on a machine that leaves your workshop.

Most of what changed in this release came from building real machine screens with 1.0 and noting every place where we needed a workaround. The most common workaround was a tag in the PLC that existed only to make the screen work: a flag to open a popup, a combined "ready" bit, an index to tell a dialog which station it's showing. Those tags don't belong in machine code, and with 1.1 you don't need them.

React to the machine, not to a button

Global Events gets a Variable Changed list. Each trigger names a variable and runs its actions every time the value changes, and once at start-up. Put an If around the actions to react to one value: open the door dialog when Door/Open goes high, show a toast when the machine enters a new phase, switch to the alarm page when a stop is pressed. Each open screen runs its own triggers, so nothing has to be set up on the server. Global events.

Conditions without a helper bit

Two new sources, AND and OR, combine a list of conditions: a variable, a comparison, an inverted value, a user-group check, or another AND/OR. A Start button is then interactable only while the machine is ready and the door is shut and the operator is signed in as a setter, with no extra bit in the PLC to keep in sync. They work in every Boolean field, in $if, and in the If action's condition.

One popup for every station

A machine with 27 valves used to need a Switch with 27 cases, or a hand-off tag the dialog read its station number from. Now a variable's array index can come from another value, such as a dialog's input parameter. One valve popup reads, writes and toggles Valves/Open[n] for whichever valve opened it. Around that:

  • Open Dialog Input ($overlay) reads the open dialog's input from anywhere on the screen, so the valve symbol whose popup is open lights up, and the light moves along when the popup moves to the next valve.
  • A tap outside a popover lands on what's underneath it, so going from one symbol's popover to the next takes one tap instead of two.
  • Navigate To Page takes a page from the dialog's input, so the Open station page button in that one popup leads to each station's own page.
  • Inside a component, Write, Toggle and Edit Value can write through the component's input. A parameter row with a setpoint and an edit button becomes one component you place once per setpoint.

Sequences and setpoints

  • Delay waits a number of milliseconds before running the next actions. A write goes to the PLC and back, so a toast after a short Delay shows the value the PLC confirmed: Lower limit set to −25 g.
  • Edit Value opens the numpad on any numeric tag, with no Number Input on the screen. Min, max and decimals come from the variable itself, and the actions afterwards can read both the new value and the one it replaced, for example for an audit message.
  • Acknowledge All Alarms makes any button the screen's acknowledge button.
  • A formula can fill an Integer field, rounded to a whole number, and Gauge and Trend accept an Integer tag directly, such as a PLC counter.

Ready to ship on a machine

A machine builder doesn't install software on a developer's laptop. NEXT HMI ends up on an industrial PC or a box in the cabinet, often on a network without internet. 1.1.0 is built for that:

  • A Linux zip next to the Windows and macOS ones, for the industrial PCs that run Linux.
  • An offline Docker installer for x64 and arm64: the image as a file, a compose file and install.sh. Copy it onto a USB stick and install on a machine that can't reach a registry. Docker without a registry.
  • A guide to shipping it. The new chapter Shipping it on a machine walks through the five steps: which build ships, hardware with a stable identity, activation on the commissioning bench, locking the installation down, and what to hand over to the customer.
  • Every download names its edition, Community or Enterprise, in the file name, on the splash screen and in System Information, so you can tell on site which one is installed.

More of the look lives in the theme

Machine builders ship one HMI in their customer's colours, so whatever can live in the theme should. Three new parts of the theme settings:

  • Toasts: where they appear (top or bottom, left, center or right), rounded or pill-shaped, and a background and text colour for each severity.
  • Numpad: key size, gap between keys, key font, Enter colour, and a 3- or 4-column layout. Every numeric input gets it, including custom widgets that open the SDK numpad.
  • Exo 2 is bundled next to Inter, Manrope and Lexend, served from the HMI itself so it looks the same without internet.

Every new setting starts at the current look, so existing projects don't change until you change them. Theming.

Touch input you can trust

A Target fill volume field showing 600 mL, next to its numpad. On the numpad the 600 is red, a warning below it reads Min: 480 · Max: 520, and the Enter key is greyed out.
New in 1.1.0. 600 mL against a maximum of 520: the numpad shows the bounds in red and won't let Enter write it.

In 1.0, typing 5000 into a field with a maximum of 200 sent 200 to the machine without saying anything, and × saved the half-typed entry. Now only Enter writes, and only a value inside min/max. Anything else cancels, and an out-of-range entry turns the bounds red, with an optional message that says why. A String Input can open the numpad for a PIN. Buttons get an On Released list and a Momentary switch for jog buttons. Keep a watchdog in the PLC for anything that moves: if the connection drops, the panel never sees the release.

Also new: alarm text and translations can show live values, a recipe screen can mark every setting that differs from the saved recipe, the Alarm List gets touch-sized rows and filter chips, and there's a Button Container and a Badge widget.

What to check before you upgrade

Your project is upgraded to file format 11 the first time 1.1.0 opens it, after you confirm and after a backup is zipped into .backups/. A few things are worth checking:

  • There's no way back to 1.0.x. Once a project is upgraded, 1.0.x refuses to open it and shows Requires update. Without that block, 1.0.x would quietly save over the alarms. Keep the backup if you might need to roll back.
  • Number Input binds a plain Float or Integer tag. One that's still bound to a bVisible/bEnabled/fValue struct shows --- until you rebind it. The upgrade doesn't convert these.
  • On Pressed runs on touch-down instead of on release. If you relied on the old timing, move those actions to On Released.
  • A tap outside a popover without a backdrop now also reaches what's underneath it. A new Tap through switch turns this off per dialog.
  • The User Badge is replaced by ordinary widgets that show the same thing. The Container's shadow and the Alarm List's own frame are gone.
  • Custom widgets: VirtualNumpad replaces onClose(value) with onApply and onCancel, and readNumberValue is now a reserved SDK name.
  • Usage reporting sends more, and more often: every hour instead of once a day, with fields such as how NEXT HMI was installed and the rough size of your projects. It still sends no names, values or addresses. Usage reporting lists every field and how to turn it off.

Get it

Download the portable zip for Windows, macOS or Linux, or the offline Docker installer for x64 or arm64. Unzip it, start it, and go to localhost:8000. The install guide covers the rest.

This post covers the highlights. Everything else is in the full changelog, including the fixes: alarms restored after a restart follow the tags again, a popover near the bottom edge stays on screen, and a toast no longer covers the numpad.

Sources: the 1.1.0 changelog and the user guide. Found something that doesn't work? Support explains how to report it.