Ganter Lab 2026.10.0

v2026.10.0

What changed since Ganter Lab 2026.9 is below. Everything else works as it did.

Highlights

  • The Logic never waits on equipment. The station decides a tag write at once (the value, the target, a lock held by a run or an interlock, whether the device is connected) and hands it to that device's own delivery queue, where the values owed to one device leave one at a time, in the order they arrived. A slow or silent device delays only what is addressed to it: the expressions, the alarms, the operator and every other device keep their pace.
  • A write reports what became of the value. A tag's Write value, the button, input and toggle of a dashboard and the agent's write tools are the ones that wait for the equipment, so their answer tells apart a value the equipment took, a write the station refused before anything was sent (with the reason), a write the equipment refused or never answered, and a value that a newer write to the same point replaced before it was sent, which is not a failure.
  • Two write verbs in an action script. Write(value) hands the value over and the next line runs. WriteAndWait(value, timeoutMs, continueOnFailure) waits for the equipment and answers true only when it took the value. No write ends a script by itself: when the script finished and one of its writes failed, the run says so in the feed, on the action's last run and in the Actions list. Actions run on a lane of their own, one at a time, so an action that waits for a device holds back only the actions behind it, and the 500 ms limit stops counting while the script waits.
  • A recipe segment chooses when its time starts counting. The new Time counting field of a Step or a Ramp reads Wait until they reach the device or Send and go on. A segment that waits starts its clock only once the equipment took every setpoint, the unit reads "Waiting for the setpoints to reach the device" meanwhile, and a refusal or a timeout triggers the On failure rule. The setpoints of a segment leave together, each to its own device's queue, so a station with several devices pays the slowest one once, not the sum. The instant recipe at Start and the finalization block always wait.
  • The installer and the application are digitally signed. The installer, the application and its updater carry the publisher's signature, so Windows shows a verified publisher instead of an unknown one.

Changed

  • The Connector and the Logic pages follow what an agent writes: a device or a serial line the agent creates, and an action, a trigger, a variable, an alarm or a folder it adds, moves or renames, appear in the open tree without reopening the page.
  • Connecting the station to its Ganter account is free on the station's own screen. Disconnecting takes an administrator only once the station has local users. Sign in and Sign out stay drawn for whoever may not press them, greyed, with the reason on the button.
  • The page the browser shows after the station's sign-in carries the Ganter Lab brand in the light and the dark theme, speaks the station's language and says so when the site refused the sign-in.
  • After a change to Remote access restarts the web server, a page open in a browser comes back on its own within seconds, and the cover says that a browser signs in again.
  • In the light theme, dividers and the borders of cards and controls stand as far from the page as they do in the dark theme.
  • The installer shows the Ganter Lab icon and brand while it unpacks, and Windows lists Ganter Lab as the publisher of the program and shows the product icon on its uninstall entry.
  • The application's top bar shows the version with a v in front, so the number reads as the version. About keeps the bare number beside its own label.

Fixed

  • A reading is one instant. A tag and a variable publish their value, quality and time together, so the Logic, the recorded history, the OPC UA server, the Connector page and the agent never see a value beside the quality or the time of another moment.
  • In the installed application, an expression or a script that calls a member of a point's read surface, such as .State() or .ValueToReal(), reads the point instead of getting nothing.
  • On a slow or busy station, the first script to run after start (an action, an expression or an occurrence condition) could be aborted as an infinite loop, because the station was still preparing the script engine while the script's time was counting. The engine is now prepared once, when the logic starts, and the first script runs as fast as every other.
  • When the OPC UA server cannot take its port, the notice the application shows as it starts, the tray notification and Settings say why in the station's language: another application on this computer holds the port, or Windows refused it, which is how a port inside a range reserved for Hyper-V, WSL or Docker answers. The sentence names the port and what to do next.
  • A maximized window reopens maximized and in place, from the notification area and at the next start, instead of coming back shrunk and out of position. The place it had before being maximized is kept too.

← All release notes