Document all-site device dashboard, diagnostic registers, and Chep alarm strings

This commit is contained in:
2026-10-21 21:11:41 +00:00
parent 50f37db66c
commit 19d56ff87e
7 changed files with 509 additions and 0 deletions
+12
View File
@@ -86,3 +86,15 @@ Reload clean Configure Pages between previews, particularly after large charts/m
For bindings, record display value, editable flag, updateRegister, writeValue/updateValue, limits flag and units independently. A read-only field can retain a stale write target. Legacy (Dont Use) components can have both register and updateRegister keys; behavior is not established by an internal name alone. Limit values do not enforce anything when limits=false.
This survey used Copy only and discarded editors. No production paste, Save, register command, device action or alarm test was performed. Earlier Mandel development tests remain separate evidence with separate authorization.
## Alarm strings and Terminal register imports — October 21, 2026
Alarm Message and Return to Normal Message are expressions. Plain text must be a quoted string literal. Preserve existing valid concatenation/lookup expressions instead of quoting the entire expression. Chep HighPlains had 73 Main definitions: three user-corrected entries were retained; 70 others received 134 string-field corrections. See CHEP-HP-GUIDE.md for verification limits.
Manage Registers → Import → Advanced supports native JSON for Terminal sources even when Normal says Import Currently Not Supported. Select the correct device/source and explicitly turn Delete Unused OFF (default ON). Each item uses id, siteId, deviceId, description, slaveId, address:{formula:commandText}, updateType, updateInterval, systemRegister and enabled. The Confirm Import preview exposes the actual persisted schema. Check exact values by ID (native sorting can change order), and allow only intended inserts with zero updates/deletes for additive work. Submit only that inspected preview. After Import Successful, reload the page before readback; the Edit table may remain stale.
For a read-only definition audit, Validate [] with Delete Unused OFF; inspect unchanged and close without Submit. This verified all 239 new definitions on nine devices. Command registers for update/reboot/restart use updateType DISABLED, distinct from enabled=false; do not poll or trigger them as a monitoring test. New create forms reject intervals above 600 seconds. Terminal slave type with configuration {} was verified on APYD Main and added to eight explicitly approved devices. Source creation enables command execution and needs appropriate authorization.
Modal animations can make an early Close or next Create click ineffective. Wait for the correct Register ID and settled dialog before reading; an open dialog can still contain the previous register. Verify identity, not only dialog visibility. Keep batches bounded and persist successful IDs after each save to recover safely from browser timeouts.
Cross-site tokens use |{register:siteId:deviceId:registerId}|; timestamp is registerId.timestamp. The production Atom dashboard now covers 38 devices across 33 accessible sites (Atom itself has Global scope only). Explicit null guards prevent missing uptime/IP values being displayed as zero/null octets. A valid uptime timestamp within 120 seconds is a display freshness threshold, not proof of operational health. Wait for initial polling to populate before classifying No data. See ATOM-DEVICES-GUIDE.md and terminal-register-templates.json.