Clio Liu 947f632d7f feat(scada): CI Server tag database, historian, displays

The old 05-scada/, restructured around the distinction its README never
drew: configuration is deployed with dssqld, displays are deployed by
file copy. Conflating the two is what made the folder confusing.

  modbus_points/          the tag database - named for the protocol,
                          since CI Server configures others differently
  modbus_points/historian/  3 groups, 49 bindings - HAND-MADE, no
                          generator, and drifted from the server
  hmi/                    displays and their generator
  ciserver-backup-2026-08/  outdated exports, evidence only, never import
  QUICKLOAD.md            dssqld export/import, the 5 classes, the import
                          order, and why an item import kills every display
  README.md               the chain end to end, and the not-updating triage

Verified during the move - the whole chain is reproducible:
  scada-points.csv and all three .qli regenerate byte-identically
  all six displays build clean

Removed the K offset machinery from build_display.py, item-ids.meta.json
and DEPLOY.md. K was a consistency check on measured ids, not a source of
them, and diagnosing a dead screen by arithmetic is wasted effort when
validating the display in CI Server's Editor Module fixes it outright.
The guidance now leads with that one action.

Recorded, not fixed: the repo's historian config disagrees with the
2026-08 CI Server export - WRPS_THIRTY_SEC and a FIVE_SECONDS group exist
on the server and not here. cicore1 was unreachable during this audit, so
which is correct is unknown.

Not carried across: __pycache__, out/*.xml, and the top-level
WRPS_Overview.xml that was tracked despite .gitignore declaring the
display XMLs to be build output.

2026-09-02 17:16:18 +10:00

2.5 KiB

Raw Blame History

historian — collection groups and item bindings

Hand-made. There is no generator for this. Everything else under modbus_points/ is generated from 03-plc/register-map.csv; these two files are not, and that is the reason they have drifted from the server.

File	Class	Holds
`his_group.qli`	`@HIS_GROUP_DF`	3 collection groups
`item_his.qli`	`@ITEM_HIS_DF`	49 item → group bindings

The three groups

Group	Items	Collection
`WRPS_ONE_SEC`	5	1 s scan — the fast analogues: level, inflow, discharge
`WRPS_ONE_MIN`	4	1 min scan — slower trends
`WRPS_EVENT`	40	on change — states, commands, alarms, trips

Written 2026-08-21.

Why this matters more than it looks

The demo this project exists to support is built on historical grounding. From 01-design/00-origin/:

"Are you sure? What did inflow actually do last time we had rain like this?"

The answer to that question comes from the historian. Layer 1 of the demo — risk and headroom — works from live values alone. The push-back that earns trust does not. Without these two files there is no historian, and the demo loses the layer it was designed around.

⚠️ These files disagree with the server

ciserver-backup-2026-08/export_his_group.qli, exported from CI Server around 2026-08-20, contains groups that his_group.qli does not define:

In the CI Server export	In `his_group.qli`
`WRPS_EVENT`	✅
`WRPS_ONE_SEC`	✅
`WRPS_THIRTY_SEC`	❌ not defined here
`WRPS_ONE_MIN`	— not in the export
`FIVE_SECONDS` (binding `STN.LEVEL`, `STN.INFLOW`)	❌ not a WRPS group at all

Nobody currently knows which is right. The export is dated a day before these files, but contains groups they do not. Resolve it by exporting from cicore1 and comparing — see ../../QUICKLOAD.md.

Until then: do not import these files onto a working server without checking what is already there. You may remove a group something depends on.

Worth doing: generate these too

The points and items chain is generated end to end, which is what keeps the PLC and SCADA from drifting apart. The historian stops short of that, is maintained by hand, and has drifted — exactly the failure the generated chain exists to prevent.

Extending ../gen_ciserver_qli.py to emit @HIS_GROUP_DF and @ITEM_HIS_DF would close the gap. The item list is already there; what it needs is a table saying which item belongs to which group at what rate. Not done in this audit.

2.5 KiB Raw Blame History