Repository navigation
PlantCraft 0.6.1
Released 2026-11-09. The setup guide (Heron) for new installations, a demo plant of 100 loops with loop health that matches the known faults, app packages and licences for closed apps, PlantCraft PID, the Historian's data lake feed, and fixes from the public demo and the engineer sweeps.
[0.6.1] - 2026-11-09
Added
- Simulator and demo: 100 loops, most of them healthy. Beside the 50 loops of the demo
story, the Simulator serves 50 healthy, well-tuned loops over every unit, so the demo reads as
a real plant where a minority of loops need attention. - Platform: the setup guide. A small robot walks an administrator through a new
installation: a language model, the basics (time zone, language), the plant's data (OPC UA,
PI Web API or a file), documents, the asset tree, the apps' first steps, the team and email.
Each step knows by itself when it is done. "Do it with me" opens the assistant with that
step's work and proposes each change as a card the person applies; the model never writes
(setup-guide.md). - Platform: asset trees drafted from more tag conventions. DeltaV paths, Experion names,
area prefixes, Portuguese and Spanish role words, and tags with no ISA tag (Pump1_Speed)
all draft a tree; a CSV whose times carry an offset reads. - Platform and SDK: app packages and licences.
app.tomlsays which PlantCraft versions an
app installs on and was tested on, its languages and whether it is closed; PlantCraft checks
them before an install or an upgrade. Closed apps run with a signed licence for one
installation, added in Apps › Licences (app-package.md). - PlantCraft PID, the first closed app: the P&ID reader and plant map, moved out of
Documents. - Historian: data lake feed. A saved export goes to the data lake every hour or every day.
- Docs: integrators' guide for PlantCraft next to MES, a data lake and an on-premises
language model (integrators.md). - Development:
make previewandmake preview-lightstart the whole suite locally with the
demo story, apart from any other installation.
Changed
- SDK: written once. Analytics runs block code in the SDK's one sandbox (as Alarms and
Documents do); the asset picker, the apps' command line and the PI Web API client are one copy
in the SDK. - The apps build against the repository's own SDK and ui, and pull requests run the tests of
every folder they change. - Tours are shorter, and Operations has its own.
- Translations: the pt-BR and es wording follows the words industry tools already use.
Fixed
- Public demo: a visit no longer ends while someone reads (scrolling, pointer moves and page
loads count as use); the clock no longer covers pages or the assistant's box; Documents opens
inside the suite's frame; the assistant retries a model that limits the rate, follows answers
without stalling, and charts the right hours. - Platform: an asset tree drafted from a source now routes its tags to that source, so the
plant shows values after the setup; a text signal's last value (a loop's mode) shows; Desk's
Coming days leaves out what already happened; notifications of a row of changes arrive as one;
long references wrap on a phone; Customize no longer covers an app's notice on its Overview. - Analytics: loop health matches the known faults. Checked against the Simulator's 100
loops, the likely cause matches in all 100 at live sampling (about 22 of 50 before): a move to
a new setpoint is no longer counted as error or oscillation, stiction, noise and valve travel
read right, and a new diagnostic names a slow output drift. Each loop's row shows its likely
cause beside the health score. - Analytics: a database gives disk space back by itself (older ones are compacted once, in
a quiet hour); the engine hands back the memory a round used; the Overview is built once at a
time; phone layouts fit. - Alarms, Documents, Historian, Models, View: overview cards translated; clearer messages
and labels (a rule without a place, "found by words", compression figures, asset types in
View's picker, readable coloured table cells). - Install: a bundle over 2 GiB is written in parts GitHub accepts; the machine profile sizes
Analytics' read cache; the public demo's limits reach PlantCraft from.env.
Security
- Historian: a PI Web API source only ever reads (its session refuses anything but GET, HEAD
and OPTIONS).
Downloads
| Bundle | For | Size | SHA-256 |
|---|---|---|---|
plantcraft-0.6.1-linux-amd64-bundle.tar.gz |
most servers | 2,253,065,117 bytes (2.1 GiB) | fb412706b4891c6da44238bdd3de77ee98f92427714a3a27abd9a263c0d2aee1 |
plantcraft-0.6.1-linux-arm64-bundle.tar.gz |
ARM servers and Apple silicon | 2,183,450,902 bytes (2.0 GiB) | 678b095b3061584fbb10c21bf82b3fe6586752f31e5f9efe775d55c4387e4ff1 |
Each bundle comes with its .sha256 and .sha256.sig. docs/verify-a-release.md explains how to check them with ssh-keygen as release@plantcraft (OpenSSH fingerprint SHA256:9l/yDgR8/Pzel1pncxrXz2IGCIhFirKpDT78tO49fG8).
Joining the parts
GitHub limits each file to 2 GiB, so a larger bundle comes in parts. Download every part of your processor, join them, then check the hash and signature as usual:
cat plantcraft-0.6.1-linux-amd64-bundle.tar.gz.part-* > plantcraft-0.6.1-linux-amd64-bundle.tar.gz
Upgrading
From 0.6.0: unpack the new bundle and run ./install.sh. It checks the bundle's signature, backs up the data folder before updating, and rolls back automatically if the update fails (./install.sh --rollback also returns to 0.6.0 by hand). Data, settings and accounts are kept. The only schema change is one new table, app_licenses; nothing is migrated by hand.
Each app's own changes are in its CHANGELOG.md under apps/.