docs: record removal of copied timer fields from Lazy B Wells 2 and 3
This commit is contained in:
+5
-5
@@ -8,11 +8,11 @@ User identifies Main Plant PLC as old Horner and wants its alarms moved to new C
|
||||
|
||||
## Pending Sweet Grass Bin G Hi-Hi control — October 21, 2026
|
||||
|
||||
Read AGENTS.md, PROJECT.md, HANDOFF.md, Sweet Grass guide, playbook and cloud references. Production inspection found two distinct paths: enabled ALM-436 “Bin G Full” reads main:Alm436 on Main PLC coil 4427; disabled Codesys candidate main:clean_g_binG_lvl_limits_hihi_alm_in_en maps to sg_cleaning.g.binG_lvl.limits.hihi.alm.in_en. Their relationship is unverified. Asked the user which path the HMI control should operate. No site configuration or operational writes performed. See SWEET-GRASS-GUIDE.md for verified settings and next steps. Prior Lazy B timer work remains pending independently.
|
||||
Read AGENTS.md, PROJECT.md, HANDOFF.md, Sweet Grass guide, playbook and cloud references. Production inspection found two distinct paths: enabled ALM-436 “Bin G Full” reads main:Alm436 on Main PLC coil 4427; disabled Codesys candidate main:clean_g_binG_lvl_limits_hihi_alm_in_en maps to sg_cleaning.g.binG_lvl.limits.hihi.alm.in_en. Their relationship is unverified. Asked the user which path the HMI control should operate. No site configuration or operational writes performed. See SWEET-GRASS-GUIDE.md for verified settings and next steps. Lazy B timer fields were subsequently removed at the user's request; see the Lazy B resolution below.
|
||||
|
||||
## Latest investigation — Lazy B Well 3 timer repair awaiting PLC mapping
|
||||
## Lazy B timer fields removed — October 21, 2026
|
||||
|
||||
On October 21, 2026, inspected both Well 3 timer configuration dialogs and Water System register definitions. Original wellNW1 display/write bindings remain unchanged. Water System table has 1,660 entries; searches tss, totalTmr, runtime and wellNW1 returned no matches. No configured Well 3 timer replacement was verified. Enabled iWell3Vol_rtDaily[0]/[1] are daily counters with units unverified; disabled well3Power_total_onTime is not a proven lifetime counter substitute. Disabled well3_i_UTS has blank description and Well Shack PLC address well3.i.UTS; purpose/units unknown. Asked the user for the two correct PLC tags, units and lifetime counter write semantics. No page/register saves, counter resets, polling changes or operational writes. Updated LAZY-B-GUIDE.md and shared study/project/handoff plus cloud notes with these findings. Next step: obtain verified mapping; then fix only timer display/write bindings, preserve appropriate conversions, save and verify persistence without resetting hours.
|
||||
**Resolved by removal — October 21, 2026:** at the user's request, removed Time Since Start and Hours from production Well 2 (well_2) and Well 3 (well_3). Both pages had copied wellNW1 references with no verified corresponding Water System timer registers. Removed only elements 3a7413f1-6213-44be-842c-350f715ceb6d and c8a9b2ea-35d5-448b-9d68-756715e25df6 (Well 2), and 6e6f612c-c2e5-4ee9-a468-849e6191b523 and 4e613f5b-e0e3-4526-88dd-b9a81695d75e (Well 3). Saved both pages and freshly reopened: Well 2 element count 106→104; Well 3 124→122; the only removed IDs were these four and no elements were added. Runtime pages show the remaining motor controls without timer fields. Well 1 has no timer fields and was unchanged. Local native Copy backups: /tmp/lazy-b-well-timer-removal-backup.json. No PLC counters were reset, register definitions altered, or operational commands submitted. Removal supersedes the earlier request to locate replacement timer bindings; adding timers later requires verified PLC tags/units.
|
||||
|
||||
## Previous completed change — East Water Well 30 trend label
|
||||
|
||||
@@ -37,9 +37,9 @@ Atom GIT connection recovered. Read repository AGENTS.md, PROJECT.md, HANDOFF.md
|
||||
|
||||
Verified page Title/URL and visible element structure; native Copy root identity checked before interpreting JSON. Findings distinguish this session's inspections from October 20 register/alarm observations. No production page saves/pastes, register/setpoint writes, operational buttons, device actions, alarm modifications or live control tests. No raw JSON/credentials/camera/map endpoints uploaded. Browser timeouts were recovered with clean Configure Pages reloads.
|
||||
|
||||
## Remaining findings — unchanged by the KAV corrections
|
||||
## Findings and resolution status
|
||||
|
||||
1. Lazy B Well 3 timer repair awaits correct PLC tags/units/write semantics; current wellNW1 references have no matching configured Water System registers. See latest investigation and LAZY-B-GUIDE.md.
|
||||
1. Resolved: Lazy B Wells 2/3 copied timer fields removed; no replacement timer mapping is currently needed.
|
||||
2. Lazy B: duplicate main/Main navigation targets; M03 PID Tn suffix KP; Loadout internal 100% Button name on an 80-value command. Internal names are not behavioral proof.
|
||||
3. Lone Pine dryer uses legacy (Dont Use) components. Inspect supported semantics before reusing/migrating.
|
||||
4. Alarm latching, notification policies, PLC interlocks and operational write behavior were not audited here.
|
||||
|
||||
Reference in New Issue
Block a user