Getting started
What Ganter Lab is, where every page lives, and the short pages that take a fresh install to its first live value.
Ganter Lab is a local SCADA (supervisory control and data acquisition) application for Windows. It reads field devices over industrial protocols through its Connector, turns raw readings into engineering values, computes variables, actions, triggers and alarms in Logic, runs and records test and manufacturing procedures in Process, and shows all of it on the dashboards you assemble on View. Everything runs on the station, the computer that runs Ganter Lab: an OPC UA server embedded in the app serves the same values to other clients, browsers on the local network can open the same pages, and an agent endpoint lets an AI assistant read and, if you allow it, configure the station. This page says where everything lives; the pages under it take you from a fresh install to the first live value.
Where everything lives
The rail follows the order an application is built in; its top group is the work, its foot group the station:
- View: the dashboards, and the panels a Process unit publishes.
- Process: the models, units, procedures, recipes, evaluations, actions and templates of the test workspace, and the Histories of recorded runs.
- Logic: the address space; variables, actions, triggers and alarms; the assets (images, icons, colors, symbols, connection types).
- Connector: drivers, serial lines, folders, devices and tags.
- Users: local users, roles and the permissions that gate every page and verb.
- Validation: what the configuration points at that no longer exists.
- Events: alarms, occurrences, interlocks and the diagnostics console.
- Agent: the agent (MCP) endpoint and which areas it may reach.
- Settings: appearance, startup, localization, remote access, the OPC UA server, backups, crash reports, updates, about.
- Account: the Ganter account, the subscription and its seats, the integrator details and feedback.
Which entries you see depends on the role in force; The window lists the permission behind each.
The rest of this group
- Install and first launch: where the installer comes from, the commissioning window, the data folder, 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 window: the frame around every page, the status bar, notifications, the tray.
- How the pages work: the page templates, autosave, the command bar and its refusals.
- Free mode and the license: how long the runtime runs unlicensed, and what stops when the window ends.