What changed since Ganter Lab 2026.10 is below. Everything else works as it did.
Highlights
- A Welcome page shows where to start. The station opens on Welcome, the first entry of the menu, for every role that sets something up (the Connector, the Logic, the Process, screens, users or agent access). By hand draws the pages in the order a station is built (Connector, then Logic beside an optional Process, then View, with Users under it), each with a green check once the station holds something there (the optional Process shows it only when it is used). With AI shows a short conversation with an assistant and Connect an assistant, which opens the Agent page at Connect a client. Under both, Getting started opens the help panel, and the rest of the menu is named with what each page is for. Don't show again takes the page off the menu for everyone, and Show the Welcome page in the menu in Settings, Startup, brings it back. A station updated from an earlier version shows the page too, until somebody takes it off.
- The AI assistant answers from the app's own documentation. Two read-only agent tools,
help_searchandhelp_read, hand an assistant the offline help this installation carries for its version, the same articles the help panel opens, in the station's interface language by default. They are there whenever Enable agent access (MCP) is on, whatever capability groups are open, since the text is the public documentation and shows nothing of the station. The assistant is told to read the help before answering how the app works, so it names the buttons and fields as the screen shows them instead of inventing steps. The With AI card of the Welcome page shows such a question answered. - Every decimal box reads the station's decimal separator. On a station whose Decimal separator is a comma, 12,5 is read as twelve and a half, and 12.5 is accepted everywhere. This covers the tag fields (scale, calibration, limits, the substitute values and Write value), the two-point assistant, a Logic variable's Set value and Initial value, an evaluation's Min, Max and Tolerance, a procedure's Quantity per completion and Reference rate, recipe setpoints and segment targets, numeric run metadata, the annotation time of a run, a chart's scale and reference entries, the dashboard Input, a Button that writes a value, and the number boxes of the dashboard editor (axes, plot heights, row values, scale bands, content scale, icon size, symbol slot constants, a symbol's test value and a connection's thickness). A box that shows a number for editing, the refusals of a dashboard command and the editor's notices and slot ranges write numbers with the same separator.
- A dashboard command no longer sends a value outside the tag's limits. The Setpoint slider, the Selector, the Step keys and a Button that writes a fixed value respect the tag's Limits, as the Input already did: a value outside them is refused before anything is sent, with the reason, instead of being clamped on its way to the device while the component announced the value that was asked for. They also refuse a fraction sent to a point that holds only whole numbers, so a slider armed at 2.5 over an integer tag no longer sends 3. Step keys stop at the tag's limit and grey the key that would pass it, and the Setpoint slider's editor warns when its travel reaches past the tag's Limits.
- A wrong address stops only its own point. An address the equipment does not hold (a Modbus TCP register, a Rockwell tag, a Beckhoff symbol, an IEC 61850 attribute the IED lacks or denies) and a point whose type does not fit what the equipment sends (an OPC UA node, an IEC 61850 attribute) mark only that point bad, with a sentence saying why (and, for a type that does not fit, which type to declare the tag as). The device no longer reconnects on every sweep, and its other points keep reading. Timeouts and lost connections still reconnect.
Changed
- On a View with no screen yet, New dashboard says why it is greyed while the station is locked in engineering.
- A device's Host reads a pasted address whole, on every driver that has one.
opc.tcp://192.168.0.10:4841becomes the host 192.168.0.10 and the Port 4841,host:portfills the port on Modbus TCP, Beckhoff, Mitsubishi, BACnet and IEC 61850, and the HTTP and AVEVA PI drivers take a pastedhttp://orhttps://as their transport and a path as the resource path, with an IPv6 address keeping its brackets. What the device has no field for (another protocol's address, a path or a port the driver cannot keep, an IPv6 address without brackets) is refused with the reason under the box. Whatever was pasted, the box then shows what the device kept instead of the pasted text. A device an earlier version saved with the whole address in its host connects to that address, and nothing saved is rewritten. - IEC 61850 supports 64-bit integers. Discovery proposes an Int64 tag for an INT64 or an unsigned 32-bit attribute and it reads and writes the whole number; an Int32 tag whose value outgrows 32 bits fails only that point, with a message naming the type that holds it.
- OCPP: each connector (1.6) and EVSE (2.x) publishes the number of the transaction running on it, beside its meter and status readings, so the stop and transaction status commands can take it from a tag. Name the tag with the Transaction suffix; it empties when the transaction ends.
- When a driver refuses a write on purpose (a value the point cannot hold, a refusal the device answered), the reason reads as the driver's own sentence, without a technical name in front of it.
- The agent reads a device's address as the Connector panel does: browsing the Connector and saving a device report the host, the port and the resource path the station connects with. The agent also reads whether the Welcome page is on the menu with the station's settings, and can open it while it is there.
- The Terms of Use were revised, and after the update the station shows them once more, with a note on what changed, to be accepted again: creating an account on the website now accepts them, without a separate box.
- The first time the close button hides Ganter Lab, a window of its own, Ganter Lab keeps running, explains that the station goes on, where its icon is (next to the clock, or behind the taskbar's ^ arrow), that Exit in the icon's menu ends the app, and how to make the close button exit every time (Keep running in the background when closed in Settings, Startup). Continue in the background is the default and hides the window; Exit now ends the app for this close only. The notice replaces the Windows notification, so Do not disturb can no longer swallow it, and once it is answered, whichever the choice, it does not appear again.
- The help has a Welcome page, and Getting started, installation, startup and the View page say where the station opens and how the Welcome page comes back. The Agent pages describe the two help tools. The pages of the devices and of the OPC UA, AVEVA PI, Rockwell, IEC 61850, BACnet, OCPP and LoRaWAN drivers say how a pasted address fills the device, how values are converted and written, what each OCPP command does in each version, and that a LoRaWAN sensor's session belongs to the station. The pages of the dashboard commands, the recipes, the run notes and the localization settings follow the changes above.
Fixed
View
- An imported icon, or a tag text shown as an icon glyph, can no longer carry hidden markup that runs in the page: comments are removed from the drawing and CDATA sections are kept as plain text. Icons with an editor's note in them still import.
- A component's settings no longer take a screen down. Clearing the constant reference of a Gauge, KPI card or Progress keeps the last number instead of breaking the editor, a value an agent writes out of range is held to the field's range (a negative row count on an Alarm banner), and an empty one reads as the default (a Line chart with no series). A component that still cannot be built shows as unavailable, and the rest of the screen keeps updating.
- A long line chart no longer loses its history when a KPI card with a shorter window reads the same point at the same rate; each keeps the span it asks for after a save and after the periodic refresh.
- A line chart whose time axis Counts in the sample number numbers the samples in view, 0 for the oldest, instead of plotting unlabeled seconds, so a dashboard saved in that mode draws what the mode says.
- The axis labels of a chart never land on each other. The room a live chart keeps past its newest sample carries no number of its own (such as "4.8 s"), a live clock axis keeps that room too and no longer draws its last label half off the edge, and an end pinned by hand is still labeled.
- On a station set to the 12-hour AM/PM (02:05:09 PM) time format, a chart's time axis shows AM or PM on every clock label, in the run PDF too, and a clock label that would overlap its neighbor is left out instead of drawn over it.
Process
- A run that ends as failed also sends the recipe's Finalization (safe state) block before it releases the equipment, so a heater or a pump is left in the safe state the recipe declares instead of on the last value the profile sent. A finalization that cannot be applied is journaled and does not hold the run's end.
- Copy model gives each unit's Automation in the copy switched off and without its PLC returns, so the copy never answers the original's PLC. The rest of the automation travels: point its command sources at the copy's own signals, declare its returns and switch it on with Enabled.
- Changing the Time counting of a recipe segment that was already saved is kept. Before, every segment created from the panel waited for its setpoints to reach the device, ramps included, whatever the panel showed.
- On the Process screens and the unit view, a live card whose reading fails no longer stops the other cards from updating or keeps the view from opening. A card that cannot be built is left out and the rest of the view works.
- A role that may only view the Process can no longer change an occurrence's condition by typing in its script editor. The script and expression editors of the Logic follow the same rule: when the role or the engineering lock forbids editing, they are read-only.
- Switching a model's stop interlock updates the open unit view at once: the banner and Rearm appear without leaving the unit.
- A unit that had its own productivity configuration and was set back to Follows the model default gets its own configuration back untouched when it stops following the model again, instead of the model's copy.
- Histories and the detached run chart draw a recorded run whole, from its first sample. Before, a long run showed only the last 5,000 samples of each channel, although its PDF and CSV had everything.
- In Histories, a note or annotation being typed on the open run, and the label layout chosen, survive while the list refreshes as the filter is typed.
Logic
- A script that gives a memory variable a value its type cannot hold, such as the result of
parseInt("")into an Integer or a text into a Boolean, is refused as a failed write, and the variable keeps its current and retained values. Before, the run showed OK and the variable was emptied. Clearing a variable on purpose from the Logic page works as before. - The Logic editors follow a change made elsewhere (by the agent or another window) to the variable, action, trigger or alarm they have open, instead of writing their older copy back over it at the next autosave. A field you are editing keeps your value.
- Opening another variable, action or alarm in the script editor no longer saves its script as if it had been edited, and the Logic page no longer treats the field as being typed in.
- While the name being typed would be refused, Run stays greyed with the reason, and a refused name never takes the Logic page down. Removing a Logic folder that holds an item with the folder's own name no longer fails.
Connector
- While a device cannot be read, the station's OPC UA server keeps publishing a tag's held or substitute value in the tag's raw form, marked Uncertain. Before, an external client saw the number switch to the engineering unit at the moment the reading failed (1234 becoming 123.4 with a 0.1 factor), or an inverted Boolean flip.
- A factor of 0 on an enabled Scale or Calibration stage is refused when typed on the tag card or in the grid, with the same message the panel shows, and the stage goes back to its saved value. Before, it was saved, the tag showed, published and recorded only the offset, and later changes to that device were no longer saved.
- A new tag can be named before its address is filled in, and renaming a device or another tag no longer fails while a tag still waits for its address. While a device holds changes it cannot save yet, renaming one of its saved tags to the name of a new tag in those changes is refused where the name is typed, instead of the later save dropping the new tag from the panel.
- The hint under a Beckhoff, IEC 61850, Rockwell or Mitsubishi tag address the driver cannot read, and the refusal of a rename for a tag that left its device, speak the station's language instead of English.
- The stray dot that showed after the selection box of every row in the tag grid is gone.
- Opening an HTTP or AVEVA PI device whose saved Host still spells
http://orhttps://no longer changes its Transport: the panel shows the choice the station connects with, and only an address pasted into the box changes it. An AVEVA PI device over plain HTTP with no port of its own connects on port 80, and one found by a scan over plain HTTP no longer keeps port 443. - On a Windows set to a decimal comma, the AVEVA PI driver reads 12.5 as 12.5 instead of 125, and the BACnet driver no longer sends a 12.5 setpoint as 125.
- The OPC UA driver converts values between the tag and the server's node by their number, in both directions: a Double node of 25.0 read by a Float tag reads 25 instead of 0, a Float tag over a Double node writes a Double, an integer that does not fit the node's type is refused before anything is sent, and a UInt64 tag writes instead of failing.
- The Rockwell driver writes only the bit or the structure member a point addresses, instead of reading the whole word or structure and writing it back, which could undo what changed on the controller in between. A point the driver cannot write this way is refused with the reason and the advice to address the member by its own name. A Boolean point on one element of a BOOL array, such as Flags[5], reads and writes that element and leaves the others alone, where it used to read the wrong part of the array and report it as good.
- The Rockwell tag browse proposes each tag in its own type: an array proposes its first element in the element's type (Temps[0]), a BOOL array a Boolean on its first element, and a structure or system type no point, instead of a REAL that read the first bytes as a number.
- Mitsubishi addresses in hexadecimal (XFF, XA, WABC) are accepted on the devices MELSEC numbers that way, and the tag panel agrees with the driver on every device code.
- The IEC 61850 driver reads unsigned attributes (INT8U to INT32U) into an Int32 tag, and text values with accents and other non-English characters read correctly.
- The BACnet driver writes a value with the datatype the standard gives the object, so switching a binary output on and off works on controllers that refused the old write. A value the object cannot hold is refused before anything is sent, and a refusal from the device names what it answered without dropping the connection.
- The OCPP driver's commands work with chargers on 2.0, 2.0.1 and 2.1: the command list keeps the same names, and each one goes out in the form that version expects (remote start and stop, reset, charging profile, availability, unlock and set variables). On 1.6, the charger's maximum profile goes to connector 0.
- OCPP 2.x: the status and meter tags are numbered by EVSE, so on a charger with two EVSEs the second one's status no longer overwrites the first's, and the meter a charger reports during a session moves the Meter tag. An EVSE with several connectors shows its most significant connector state, and a Status tag says it is waiting until the first status arrives instead of showing an empty text. OCPP 1.6 keeps numbering by connector.
- An OCPP charger that drops leaves the station's list, and its tags read a fault that says since when it disconnected, instead of its last status and meter being published as fresh good readings. A charger that connects again reports its status and meter afresh, takes commands at once after the station restarts even when it only sends a Heartbeat, and is no longer shown as disconnected when it reconnects while its old connection is still being removed.
- OCPP 2.1: a session identified by one of the new identification types (direct payment, EVCCID, NEVI, VIN) is authorized, and a transaction event carrying a new measurand or reason keeps its meter value. A value the station does not know is read as unrecognized instead of refusing the whole message.
- LoRaWAN sensors keep reading for good. An AS923 uplink no longer fails before the frame counter advances, a sensor's frame counter passing 65535 no longer drops every later frame until it joins again, and after 65536 downlinks the sensor still accepts acknowledgements, commands and answers, because the station signs them with the full frame counter.
- LoRaWAN: a sensor's session belongs to the station, not to the concentrator that relayed its join. An uplink relayed by any connected concentrator is understood, a rejoin through another concentrator replaces the session, and a concentrator that drops or is removed no longer takes its sensors' sessions with it. A join never gives a sensor the address another sensor on the station already holds, a join request recorded off the air and sent again is refused, and a China 470 join that cannot be answered is refused before a session is recorded for it.
- LoRaWAN answers each sensor under the region its concentrator was registered in, and guesses from the frequency only when the concentrator has none: a China 470 revision 1 sensor is answered where it listens, and AS923 uplinks between 923.6 and 924.6 MHz are no longer taken for AU915. AS923 sensors receive the dwell-time setting (and stop getting an empty downlink after every uplink), and the answer to an uplink goes out at the data rate the LoRaWAN Regional Parameters set for EU868 and AS923.
Events
- The line of a tag write records the value that actually went out to the device, the clamped one when the tag limits it.
- Exporting the event history no longer repeats a row when an event is recorded while a long export is running.
Account
- A station no longer signs itself out of its Ganter account when an antivirus or a backup briefly blocks the saving of its session: the station keeps the renewed session in memory, retries the save until it lands, and the warning stays on screen until it does.
- Sign out checks the permission again when it is pressed and after the confirmation, and the journal records who disconnected the account and from where.
- Pressing Cancel while signing the station in is honored even when the browser already finished the sign-in: the station stays signed out and the seat is given back.
- When the station's integrator ID changes, the contact of the previous integrator is dropped at once, so an offline or failed lookup never shows one integrator's contact under another's ID.
Window and help
- A greyed button or field refuses on the station itself, not only in the browser: a person viewing the station from another computer can no longer run a command or change a field that is greyed for them.
- Esc dismisses the A recording is running confirmation shown on exit, choosing Keep running.
- The browser built into the application speaks the station's language: its own texts, such as form validation balloons and the labels of its menus and dialogs, follow the interface language chosen in Settings. A change of language takes effect at the next start, as the rest of the interface does.
- In the application window, the help panel opens below the window keys in the top-right corner instead of hiding behind them. A browser on the network is unchanged.