Auto/atom-hmi-ui-chatgpt
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record verified Well 10 chlorine write-target correction

Browse Source
This commit is contained in:
snkbyte
2026-10-21 18:48:14 +00:00
parent ddba519c3c
commit e3f3f84e59
4 changed files with 18 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
KAV-GUIDE.md
+2 -2
View File
@@ -75,7 +75,7 @@ Well 10 New's copied operating root has 67 elements:
- Concentration `water:g_chemStrength` is editable but limits=false, despite populated 0/20 fields. Rate `g_well10Rate` is read-only, mL/h.
- History series use `g_well10_lvlHistory_hi`, `g_well10_lvlHistory_lo`, `g_well10_lvl_out_eu`; level axis 0–40, navigator current level.
**Unresolved write mismatch:** editable Chlorine Current PPM displays `water:g_well10ChemPPM` but writes `water:g_well1ChemPPM`. Verified from copied JSON on October 21; no write or correction was attempted. Check the intended target before using this field or template.
**Corrected and persisted, October 21, 2026:** on production Well 10 New (`well_10_new`), element Chlorine Current PPM (visible label Target ppm, element ID `4f503dce-01d9-4339-9d14-8668186b2cea`) now reads and writes `water:g_well10ChemPPM`. The original write target was `water:g_well1ChemPPM`. Changed only `updateRegister` through Configure Element, saved the element and page (Successfully Saved Page), then reloaded and reopened the configuration. Comparison of all 37 form controls confirmed only the intended write target changed. Editable=true, writeValue=`value`, limits=false, suffix ppm, number format 0.0 and all other captured controls were preserved. No chlorine value was submitted and no live register-write/physical dosing test was performed.
## East Water
@@ -98,4 +98,4 @@ The Wells chart has ten series. Older registers include `water:well21GPM`, `well
## Future work
Use this guide to locate the relevant page and equipment without repeating the whole site survey. Reopen only the page/subtree being changed, verify its current read/write bindings, and back it up before authorized edits. Neither alarm latching nor PLC interlocks were audited here. Operational testing requires its own site-specific authorization.
Use this guide to locate the relevant page and equipment without repeating the whole site survey. Reopen only the page/subtree being changed, verify its current read/write bindings, and back it up before authorized edits. Neither alarm latching nor PLC interlocks were audited here. Operational testing requires its own site-specific authorization.