Ganter Lab
Sign in Download

Documentation

Ganter Lab page by page, as the application is built: what every panel, field and command does, and what it does not.

Getting started

Getting started What Ganter Lab is, where every page lives, and the short pages that take a fresh install to its first live value.Account The Account page, where the station is connected to its Ganter account, its subscription and license seat are read, the integrator details are kept, and feedback is sent.

Getting started

Install and first launch Where the installer comes from and what it puts on the station, the commissioning window the first launch opens, the data folder everything is written into, and why closing the window does not stop the station.The first live value The walk from an empty Connector to a tag that reads: the driver, the device, the tag, the first poll, and the Logic address the value gets.The window The frame around every page: the title bar with its theme keys and user chip, the navigation rail and what shows each entry, the status bar and its action feed, the stopped-runtime band, notifications, the crash-consent dialog, the screens a lost connection shows, full screen and the system tray.How the pages work The two page templates, the inline panels that save as you edit, the command bar and its two kinds of refusal, right-click menus, the engineering lock, the stopped runtime, confirmations, and where every result lands.Free mode and the license What a license changes, how long an unlicensed station runs, what stops when the window ends and what stays up, and how signing in widens it.

Account

Account The Account row of the Account page, connecting the station to its Ganter account through the system browser, the connected and offline states, Sign out, and what the sign-in belongs to.Subscription The Subscription row of the Account page, the plan and its status, renewal, license seats, the stations signed in to the account, the attention states, Manage subscription, and free mode with the runtime countdown.Developer & integrator The Developer & integrator row of the Account page, the support and maintenance contact that never leaves the station, and the optional integrator ID that rides the station's registration and shows the integrator's public profile.Feedback The Feedback row of the Account page, reporting a bug, suggesting an improvement or requesting a driver under the station's Ganter account, what is sent, and when it cannot be sent.

Settings

Settings The station's own configuration on one scrolling page: appearance, startup, localization, remote access, the embedded OPC UA server, backups, crash reports, updates, and the legal texts.The embedded OPC UA server The OPC UA server the station runs in-process: what it publishes, the four Settings rows that watch, configure and guard it, what it shares with the tray and the status bar, and what a remote browser may not do.

Settings

Appearance The theme the whole station draws in, and the zoom of the desktop window.Startup Starting with Windows, what closing the window does, and the tray icon that keeps the station reachable while it runs in the background.Localization The language the station's screens are written in, and the date, time and number formats every screen and every exported file reads in.Remote access Opening this station's dashboards to other devices on the network, over HTTPS if you choose, who may use them, and the restart every change costs.Backups Online snapshots of the configuration, an export that carries the stored passwords to another machine, a restore that is scheduled for the next start rather than applied live, and the rebuild of the run-history index.Crash reports What the station keeps when it closes unexpectedly, what it sends and when it asks, and the two debug commands a development build carries.Updates How a new release reaches this station: the two switches, the check, the download, the restart that installs, and the mark on the status bar.About and Legal What the product is and which version runs, and the Terms of Use and Desktop Privacy Policy this station accepted, readable offline.

The embedded OPC UA server

Status The faceplate of the embedded OPC UA server: its lamp and state, the endpoint, Start, Stop, Restart and Test connection, and the six live meters.Configuration The embedded OPC UA server's application name, listen port and client authentication, and the Apply & restart that makes a change live.Client access The certificates of the OPC UA applications that dial this station: enrolling a client, reviewing and trusting or blocking certificates, the connection addresses, the Windows Firewall rule, the live sessions and the trusted roster.Equipment access The certificates of the OPC UA equipment the Connector dials: what waits for approval, what is approved, what is blocked, importing a certificate ahead of the first connection, and what a waiting device says in the Connector.

Build the application

Users The Users page, where the station decides who is signed in on each screen, which local users exist, and which role decides what each of them may do.Connector The Connector page: the Communication column, its tree of drivers, lines, folders, devices and tags, the two identities every tag carries, and the permissions and locks that govern editing.Drivers What a driver is, how drivers are enabled and disabled, the fixed driver of a device, the table of every driver this product knows, what each driver page documents, and the note on drivers a package does not carry.Logic The Logic page, its Address space column, the folders, the command bar, the sweep and the write funnel behind every panel, and the three permissions that decide what the page draws.Assets The Assets root of the Logic column: the overview panel with its five categories and counts, the create and import verbs, the shape every library shares, the three categories a Logic address can name, and where each kind is used.Process The workspace where a procedure model is defined once, realized on units and run as recorded, evaluated tests: the Workspace column, a model's four groups, the command bar, the permission ladder and the two locks.Definition The structure of a process, changed only when the process itself changes: the Channels, Metadata, Automation, Productivity and Printers screens, and the one shape all five share.Visualization The group of a model that says how it shows itself, with its two folders, Dashboards and Panels, each defined once and drawn for every unit.Setup The group of a model that changes when the product on the bench changes, with its seven folders in the order a procedure composes them.Operate The units in use: one node per unit with the panels and dashboards it is run through, what a run is, the lifecycle from Start to Completed, and what is refused while stopped.Templates The station-wide root of the Workspace column: the Reports and Labels libraries every model draws from, their folders, the create and delete verbs, and who may edit them.Histories The recorded-run browser: the Histories root of the Process tree, the list and the open run, what each part covers, the permissions, and what a stopped runtime refuses.View and dashboards The View page: the Visualization column of folders, screens and unit panels, the open screen's bar with Expand and Full screen, the grid a screen composes on, and who may press what on it.Dashboard components What a dashboard component is: the catalog of kinds, the addresses they bind, how a reading is drawn, and the property sections every kind shares.

Users

Signed in now The leading root of the Users page, showing who is signed in on this screen, what this screen can do now, and the Sign in, Switch user and Sign out verbs.Users The Users root of the Users page, the roster of local users, and the user panel where a user's display name, role and PIN are set, including the primary administrator and the admin PIN recovery.Roles The Roles root of the Users page, the role list with its reach strips, and the role panel where a role's name, description and permission switches are set, including the two fixed roles.Permissions The complete permission catalog exactly as the role switches read, the implication rules between them, and what each permission gates across the app, page by page.Signing in The user chip in the title bar, the sign-in dialog and its PIN pad, switching and signing out, what a change of identity does to the open page, and how browsers and remote circuits sign in.

Connector

The drivers list and a driver's page The Drivers row's registry table with its enable and disable pair, and a driver node's page: Refresh, Discover, Add device, Pair device, Add line, the device table and the state of a driver the package does not carry.Serial lines The Modbus RTU line node: the physical tuple every unit on the bus shares, its timing, its states, the unit scan, the devices filed under it, and what is locked while the line is enabled.Device folders Folders under a driver: creating, renaming and removing them, filing devices into them, the two-level limit, the folder page, and how a folder becomes a level of the Logic address.Devices The device page: its header and verbs, the Device card, the Connection card with the fields each driver shows, credentials and certificates, the Tags grid with mass edit, copying a device, and how duplicates and name collisions are handled.Tags The tag page card by card: the header and verbs, General, Source with the fields of every driver, Conversion, Live value with the write field, and Used by with Replace all.The value pipeline The typed conversion every tag shares, from the raw reading to the engineering value, the two invalid-reading policies, the out-of-range actions, the Boolean and String transforms, and how a write reverses the stages.Calibration The Calibration stage of a tag, the two-point assistant step by step, what Apply does and refuses, and what the Calibrate tags permission allows on its own.Discovery Letting a driver scan for devices or points, what each scan needs and returns, the progress and cancel behavior, adding results, and pairing a Matter device over Bluetooth.Enabling and health What takes part in acquisition at each level of the tree, what the dots and state texts mean, the All/OK/Issues/Off chips, the status bar, Last error, and the Reconnect, Refresh and Refresh all verbs.

Drivers

Simulated Synthetic in-app signals for testing, training and dashboard building without hardware.Modbus TCP Modbus registers and coils over TCP/IP, with typed addressing, byte-order control and a bounded network scan.Modbus RTU Modbus over a serial bus, with the physical line modeled explicitly and shared by its unit-addressed devices.OPC UA An OPC UA client for third-party servers, with certificate-gated trust, node-id addressing and address-space discovery.Siemens S7 Connect Siemens S7 PLCs over S7comm - rack and slot, memory areas, typed byte/bit addressing and the native data types.Rockwell EtherNet/IP Connect Allen-Bradley Logix controllers over EtherNet/IP (CIP) - controller tag names, byte offsets, atomic CIP types and network discovery.Beckhoff ADS Connect Beckhoff TwinCAT PLCs over ADS/AMS - the AMS route, runtime port, symbol paths and read lengths.Mitsubishi MC Connect Mitsubishi MELSEC PLCs over the MC protocol (3E frame) - device codes, decimal and hexadecimal numbering, and read lengths.BACnet Connect BACnet/IP building-automation devices - device instance, object type and instance addressing, Who-Is discovery and presentValue.IEC 61850 Connect IEC 61850 substation IEDs over MMS - object references, the functional-constraint suffix and the supported MMS value types.LoRaWAN Reference for the LoRaWAN driver: the embedded Basics Station network server, gateway certificates, the sensor and concentrator registrations, and payload addressing.Matter Reference for the Matter driver: Bluetooth commissioning into the local Fabric, the Pair device flow, node identity and cluster tags.OCPP Reference for the OCPP driver: the embedded central system, charge point certificates, connector tags and the Meter/Status naming rule.Redfish Reference for the Redfish driver: HTTPS connection to a BMC, resource-path plus JSON-pointer addressing, reads, PATCH writes and types.AVEVA PI Reference for the AVEVA PI driver: PI Web API over HTTPS, bearer or Basic authentication, AF and PI point addressing, reads and writes.HTTP Reference for the HTTP driver: polling HTTP and HTTPS endpoints as tags, credentials, path mapping, body parsing, PUT writes and types.

Logic

The address space The seven reserved roots every point lives under, how an address is spelled and sanitized, where a point ends and a member begins, what the filter box narrows, and the three ways to enter an address in an editor.Variables The variable editor, card by card: identity and address, the Expression and Memory kinds, the output types, the live Value card, Set value, quality and retention, the commands, and what the editor refuses.Expressions The one expression language behind variables and alarm conditions, what it may reference, the read surface of every kind of point, the rules the evaluator enforces, the messages validation gives, and how the script editor and its Browse… picker work.Actions The action editor: identity and location, the script block, what a script may read and write, every validation message, the Run verb and its journal, Enable and Disable, Copy and Delete, and the run limits.Triggers The trigger editor: identity and location, the Schedule card with Kind, Interval and Action, the Scheduling rail, the 100 ms scheduler with its fixed delay and skipped ticks, the commands, and what a trigger cannot do.Alarms The alarm editor: identity and address, the condition, the Behavior card with priority, notification, delays, message and acknowledge, the State rail, the state machine, annunciation, and Acknowledge and Ack all.From other pages The System, Server, Connector and Process roots as the Logic column shows them, every fixed point with its meaning, the read-only point and branch panels, and the notice that names the page where each root is edited.

Assets

Images The Images library: importing PNG and JPG files and what is refused, the card grid and its inspector, renaming an image with its references, the organization logo, deleting, and where an image is used.Icons The Icons library: the Fluent UI System Icons catalog and your own SVG icons, search by name or tag, the inspector, creating and editing an icon from SVG markup, what the sanitizer keeps and removes, and where an icon is used.Colors The Colors library: the ten named system colors with their values and addresses, your own swatches, the inspector, creating and editing a color, overriding a system color, and where a color is used.Symbols The Symbols library: the eleven system libraries and My symbols, the gallery's search and filters, the inspector with its live inputs and terminals, the New user symbol editor and every slot kind, Import symbol…, Export package, Duplicate, Copy chat instruction, and where a symbol is used.Connection types The eight fixed connection types every dashboard route carries: what each is for, its default color and thickness, the global override this panel edits, Restore default, and how symbol terminals and dashboard connections use them.Portable SVG symbols Build and share static SVG symbols with safe Ganter bindings and typed connection terminals.

Process

Models and folders The Models root and its cards, a model's own page with its identity and structure, Copy model and Delete model, and the folders models, reports and labels are filed into.Units The stations a model is realized on: the units table on the model's page, adding and removing a unit, the unit picked across the Definition screens, the unit under Operate, and Start all and Stop all.

Definition

Channels The abstract channels a model is defined by (number, name, alias, alias scope, role, type, engineering unit, color and chart group) and the source, alias and live value each unit binds behind them.Metadata The catalogue of fields a run captures at Start (text, number or a composed sequential identifier), the counter behind a sequential field, and each unit's code and counter states.Automation What moves a unit with nobody pressing a button: the model's External stop and the signal every unit follows, each unit's stop interlock, and the PLC-facing automation that selects a procedure, drives the lifecycle and answers back.Productivity The rolling period the production figures are read over and the named quantities the outputs are grouped into, declared on the model and followed or overridden per unit, and the productivity card each unit presents.Printers The four printer queues a unit prints through (a label or a report, at Start or at Completion), declared on the model and followed or overridden per unit, and how a command finds its queue.

Visualization

Dashboards of a model The free-form dashboards defined on a model, the unit placeholder their bindings carry, and how each unit opens its own resolved copy.Panels The operating panels of a model: the fixed cards each unit is run through, arranged once on the model, and how a panel reaches Operate and the View page.

Setup

Occurrences Watched conditions of the thing under test, written as a JavaScript expression over the model's channels and judged during a run or always.Alias sets Named sets of channel names, one per product for example, applied to a unit beside its bindings or pinned to a procedure so that staging it applies them.Datalogs The recording configurations of a model: one snapshot per interval, the channels it captures, and the column order every run follows.Recipes The setpoints a run writes: an instant set applied at Start, or a temporal Step, Ramp and Soak profile, each with the finalization block every ending run writes.Evaluations The pass/fail criteria a run is judged against, every field of a criterion, what each result does to the run, and how the results fold into a verdict.Actions The named packages of labels and reports a run emits at Start or at Completion, their commands, the marker mappings of a label, and how a procedure selects them.Procedures What the operator starts on a unit: the run's window, the recipe, datalog, alias set and evaluation it composes, the fields it prompts, the occurrences it arms, the actions it emits and what a completed run produces.

Operate

Runs and comments The panel of a unit: staging a procedure and its metadata, Start and what it validates, Hold, Resume, Stop and Abort, the live cards, comments, the single commands, the run file, and the automation and agent paths.The unit address space Every point a unit publishes under Process.Model.Unit, its type and meaning, which points are writable commands, and what a Logic script may read from it.

Templates

Report layouts Every field of a report layout, the section catalogue and its options, the close and footer furniture, the sample print, and what the PDF prints.Label templates One printer command file of the Labels library: its name and encoding, the printer commands editor and file import, the marker grammar, the installed Windows queue and the test send.Emitting labels and reports What a run emits at Start and at Completion, in which order, through which queue, what is frozen into the run file, and how every delivery is recorded.

Histories

The run list The Runs list and its filters, the row anatomy, paging and refreshing, the import control, and deleting one run or a whole sweep.The run record What an open run shows: the strip of verbs above it, the header with its status and the two actors, the interlock notice, the datalog chart, the judged criteria and the occurrence episodes.Comments and annotations Free notes recorded with a timestamp and an author into the run file, and the markers placed at a time on the datalog chart, with the add, edit and delete gestures of each.Labels and reports The Report and Labels dossiers of a run: every registration and artifact with its delivery attempts, the queue picker, Open PDF, Resend report, Print and Reprint, and the two ways to record a new document.Exporting a run The portable copies and the generated PDF of a run: what each verb needs, how the files are named, and exactly what a CSV, an XLSX, a GLAB and a PDF contain.Importing runs Take a .glab file recorded on another installation into this archive as an independent, fully traceable entry: what is validated, what the copy gets, and what it never gets.

View and dashboards

Screens and folders What the Visualization column lists and how it is organized: creating, copying, filing, renaming, reordering and removing screens and folders, the unit panels among them, the startup screen and who sees which screen.The dashboard editor The workbench behind Edit: the palette and adding components, the Components locator, selection and the canvas gestures, the property sections every kind shares, the Dashboard area, the connections drawn between symbol terminals, and the autosave behind all of it.Dashboard settings What one screen declares about itself in the editor's Dashboard area: name, description, icon, the grid it composes on, the startup flag, the status bar in full screen, who sees it, and how it is deleted.Fullscreen operator mode Expand and Full screen: the two ways a finished screen takes the whole window or the whole monitor, the keys that enter and leave them, the flyout that keeps the list reachable, the status bar preference, and what a remote browser gets.Unit panels on View The stack of cards a Process unit is operated through, as it appears on the View page: how it gets there, what each card shows and lets you do, and the Process permissions it obeys.Charts The toolbar every chart carries and what each button does, the scale, statistics and reference-line panels, the detached chart window, where charts appear in the app, and the one engine behind all of them.

Dashboard components

Alarm banner Dashboard component reference for the Alarm banner, its three presentations, every property, and how alarms are acknowledged from it.Bar chart Dashboard component reference for the Bar chart, the categorical comparison of live points, with every editor property.Button The command key: writes a preset value, fires a unit run command, opens another dashboard or runs a Logic action.Comment timeline Dashboard component reference for the Comment timeline, the operator comments of a unit's active run, with the add, rewrite and delete conduct.Frame A titled background frame drawn around a region of the screen, behind the components it groups.Gauge Dashboard component reference for the radial Gauge, its dial geometry, presets, indication, scale bands and every editor property.Icon A mark from the app's icon library, in a chosen color and size, optionally driven by Logic variables.Image A user image on the screen, fitted four ways, optionally swapped by an Image variable.Input Operator value entry written to a point: the box takes what the point takes, and refuses the rest with the reason.Interlock Dashboard component reference for the Interlock status banner, its states, the manual rearm and its permission.KPI card Dashboard component reference for the KPI card, its mini-chart and distribution, window statistics, retention and every editor property.Label Static text on the screen: size, alignment, weight, slant and ink, all yours to state.Line chart Dashboard component reference for the Line chart, its series, axes and stacked plots, window and retention, drawing fidelity and the toolbox.Occurrence list Dashboard component reference for the Occurrence list, the active and recent occurrence episodes of a unit's run.Pie chart Dashboard component reference for the Pie chart, how a whole divides across live points, with every editor property.Point table Dashboard component reference for the Point table, several live readings as one list, with every editor property.Procedure picker Dashboard component reference for the Procedure picker, which stages the procedure for a unit's next start.Progress Dashboard component reference for the Progress track, one bounded reading as a bar, a bargraph or a banded scale, with every editor property.Selector Registered options over one point, as keys or a list, showing which one the plant is actually in.Setpoint slider A handle between two ends: the drag arms the value, the key writes it, and the handle otherwise follows the plant.Status LED A lamp, or the state written out, over a Bool point, an alarm or a point that reports a state code.Step keys A − / + pair that moves a point one step from where it is, inside a declared band.Symbol Dashboard component reference for the Symbol, an animated industrial SVG driven by live points, with its inputs, connections and orientation.Toggle A switch over a Bool point that follows the plant: the click writes, the plant confirms.Value The formatted live readout: one point written out with unit, decimals, a declared field width and optional meaning bands.

Tools

Events The station's record of what happened: durable alarm, occurrence and interlock timelines beside the live diagnostics console, with search, filters and CSV/JSON export.Validation The configuration-health page: what the station scans in procedures, logic and dashboards, every finding it can report and how it is worded, what a row opens, the rail badge, and why nothing is repaired here.Agent access (MCP) Let AI assistants connect to the running app over a local, loopback-only MCP endpoint.

Events

Alarms The alarms waiting for an answer, acknowledged where they are read, over the durable timeline of every alarm state transition.Occurrences The durable timeline of every occurrence edge, observed by a run's judge or by the outside-run Always watcher, with the frozen condition behind each one.Interlocks The durable history of each unit's stop-interlock latch: trips, the source returning safe, and the manual rearms with who performed them.Console The live diagnostic feed of the running program: 500 entries in memory, searched and filtered by level, area and component, with a detailed capture and a support package for troubleshooting.

Agent access (MCP)

Turning it on The master switch, the port the endpoint listens on, and the four things that keep it local.What each area opens Every capability toggle, the tier it belongs to, its default, and the tools it advertises.Connecting a client Copy-ready setup for Claude, Codex, Gemini CLI, GitHub Copilot and any other MCP client.The tools, area by area What every tool an agent can call does, grouped by the capability toggle that advertises it.Guardrails and journaling The funnels, validation and locks every agent write shares, and the trail each action leaves behind.