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
|
## 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
|
## 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.
|
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.
|
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.
|
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.
|
4. Alarm latching, notification policies, PLC interlocks and operational write behavior were not audited here.
|
||||||
|
|||||||
+4
-2
@@ -16,7 +16,7 @@ All 21 page trees were opened on October 21. Native Copy inspected representativ
|
|||||||
| Main | main | Trend + Wells and Pumps |
|
| Main | main | Trend + Wells and Pumps |
|
||||||
| Outflow | outflow | div + row; 127 elements |
|
| Outflow | outflow | div + row; 127 elements |
|
||||||
| Well 1 | well_1 | div + operating row + information/map row; 111 elements |
|
| Well 1 | well_1 | div + operating row + information/map row; 111 elements |
|
||||||
| Well 2 | well_2 | same three-root layout; 106 elements |
|
| Well 2 | well_2 | same three-root layout; 104 elements after timer removal |
|
||||||
| Well 3 | well_3 | same three-root layout; includes motor/speed control |
|
| Well 3 | well_3 | same three-root layout; includes motor/speed control |
|
||||||
| Air Compressor | air | layout div + all operating root |
|
| Air Compressor | air | layout div + all operating root |
|
||||||
| Boiler | boiler | layout div + row operating root |
|
| Boiler | boiler | layout div + row operating root |
|
||||||
@@ -57,7 +57,9 @@ Copied operating row contains 55 elements:
|
|||||||
|
|
||||||
Current flow/level chart navigator is water:aiWell3Flow_eu. Historical level navigator is water:aiWell3LvlAgg_Past24Avg, default button index 1. The information/map/report root is separate; preserve it during control-page replacement and do not publish its location details unnecessarily.
|
Current flow/level chart navigator is water:aiWell3Flow_eu. Historical level navigator is water:aiWell3LvlAgg_Past24Avg, default button index 1. The information/map/report root is separate; preserve it during control-page replacement and do not publish its location details unnecessarily.
|
||||||
|
|
||||||
**Timer repair pending verified PLC tags — October 21, 2026:** rechecked production Well 3 (`well_3`). Time Since Start, element `6e6f612c-c2e5-4ee9-a468-849e6191b523`, still reads `|{register:water:wellNW1_tssTmr}| * 1000`, non-editable, HH:mm:ss, blank updateRegister. Hours, element `4e613f5b-e0e3-4526-88dd-b9a81695d75e`, still reads `|{register:water:wellNW1_totalTmr}| * 1000`, editable, writes `value / 1000` to `water:wellNW1_totalTmr`, format d [days] HH:mm. Captured both original configurations and left them unchanged. The Water System (water) register table contained 1,660 entries; searches for tss, totalTmr, runtime and wellNW1 returned no matches. The Well 3 family has no verified replacement for either timer. Existing enabled `iWell3Vol_rtDaily[0]` / `[1]` are daily counters, not established equivalents of time-since-start or lifetime Hours; units were not independently verified. `well3Power_total_onTime` exists disabled and is likewise not a verified replacement. Disabled `well3_i_UTS` has blank description, slave Well Shack 2080-LC20-20QBB, address well3.i.UTS; its role/units do not establish a timer binding. Do not invent well3_tssTmr/well3_totalTmr mappings or enable an unrelated counter. Requested the correct PLC tags, units and lifetime-counter write semantics from the user. No page/register saves, counter resets, polling changes or operational tests were performed.
|
**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.
|
||||||
|
|
||||||
|
**Historical audit before removal — October 21, 2026:** rechecked production Well 3 (`well_3`). Time Since Start, element `6e6f612c-c2e5-4ee9-a468-849e6191b523`, then read `|{register:water:wellNW1_tssTmr}| * 1000`, non-editable, HH:mm:ss, blank updateRegister. Hours, element `4e613f5b-e0e3-4526-88dd-b9a81695d75e`, then read `|{register:water:wellNW1_totalTmr}| * 1000`, editable, writes `value / 1000` to `water:wellNW1_totalTmr`, format d [days] HH:mm. Captured both original configurations and left them unchanged. The Water System (water) register table contained 1,660 entries; searches for tss, totalTmr, runtime and wellNW1 returned no matches. The Well 3 family has no verified replacement for either timer. Existing enabled `iWell3Vol_rtDaily[0]` / `[1]` are daily counters, not established equivalents of time-since-start or lifetime Hours; units were not independently verified. `well3Power_total_onTime` exists disabled and is likewise not a verified replacement. Disabled `well3_i_UTS` has blank description, slave Well Shack 2080-LC20-20QBB, address well3.i.UTS; its role/units do not establish a timer binding. Do not invent well3_tssTmr/well3_totalTmr mappings or enable an unrelated counter. Initially requested correct PLC tags, units and lifetime-counter write semantics; the user subsequently chose removal instead. No page/register saves, counter resets, polling changes or operational tests were performed.
|
||||||
|
|
||||||
## Valve, compressor and boiler
|
## Valve, compressor and boiler
|
||||||
|
|
||||||
|
|||||||
@@ -56,3 +56,5 @@ October 21 Lazy B follow-up: attempted to verify Well 3 timer replacements. Wate
|
|||||||
## Sweet Grass alarm migration direction — October 21, 2026
|
## Sweet Grass alarm migration direction — October 21, 2026
|
||||||
|
|
||||||
User identifies the old Main Plant PLC as Horner and wants its alarms migrated to the new Codesys plant PLC. HMI slave IDs are main_plc (Main PLC) and codesys_plc (Codesys PLC); groater_plc and sg_dryer are separate sources. SWEET-GRASS-GUIDE.md now maps 39 bin/equipment high/full alarms and migration gaps. Source reassignment and PLC logic equivalence remain unperformed/unverified. User also confirms the recent Atom HMI upgrade moved alarm logs to a new database, making previous history unavailable.
|
User identifies the old Main Plant PLC as Horner and wants its alarms migrated to the new Codesys plant PLC. HMI slave IDs are main_plc (Main PLC) and codesys_plc (Codesys PLC); groater_plc and sg_dryer are separate sources. SWEET-GRASS-GUIDE.md now maps 39 bin/equipment high/full alarms and migration gaps. Source reassignment and PLC logic equivalence remain unperformed/unverified. User also confirms the recent Atom HMI upgrade moved alarm logs to a new database, making previous history unavailable.
|
||||||
|
|
||||||
|
October 21 resolution: user chose to remove the unverified Time Since Start and Hours fields from Lazy B Wells 2 and 3. Removed four elements total, saved/reloaded both pages and verified the remaining element IDs. Well 1 had no timer fields. No counter reset or operational write. This supersedes the pending timer-mapping request; see LAZY-B-GUIDE.md.
|
||||||
|
|||||||
+1
-1
@@ -10,7 +10,7 @@ Catalogs now cover 202 pages: KAV Main Mill 43, East Mill 4, Main Water 29, East
|
|||||||
|
|
||||||
Scope was production Configure Pages and native Copy inspection only. No pastes, site saves, register writes, device actions or operational tests. Development equivalence was not checked. User's two work environments are dev.atomhmi.com and atomhmi.com (observed production host www.atomhmi.com).
|
Scope was production Configure Pages and native Copy inspection only. No pastes, site saves, register writes, device actions or operational tests. Development equivalence was not checked. User's two work environments are dev.atomhmi.com and atomhmi.com (observed production host www.atomhmi.com).
|
||||||
|
|
||||||
Follow-up correction, October 21, 2026: the user authorized fixing production KAV Main Water Well 10 New. Its chlorine field's updateRegister changed from water:g_well1ChemPPM to water:g_well10ChemPPM, matching its display expression. The page saved successfully; a fresh reload/reopen confirmed persistence and only this field changed among 37 captured form controls. No chlorine setpoint value was submitted or dosing behavior tested. See KAV-GUIDE.md. The preceding read-only scope describes the baseline survey, before this separately authorized configuration edit. Lazy B Well 3 timer repair remains pending: the October 21 register audit found no configured tss/totalTmr/wellNW1 registers and no verified equivalent. The page was left unchanged; correct PLC tags, units and write semantics were requested. See LAZY-B-GUIDE.md. The East Water Well 30 trend label was subsequently corrected in a separately authorized edit; see the dated Trends and history note below.
|
Follow-up correction, October 21, 2026: the user authorized fixing production KAV Main Water Well 10 New. Its chlorine field's updateRegister changed from water:g_well1ChemPPM to water:g_well10ChemPPM, matching its display expression. The page saved successfully; a fresh reload/reopen confirmed persistence and only this field changed among 37 captured form controls. No chlorine setpoint value was submitted or dosing behavior tested. See KAV-GUIDE.md. The preceding read-only scope describes the baseline survey, before this separately authorized configuration edit. Lazy B follow-up: Well 1 has no timer fields; Wells 2 and 3 had the same unverified wellNW1 timer references. The user chose removal. Time Since Start and Hours were removed from both pages on October 21; saves were verified by fresh editor reloads and runtime inspection. No PLC counters/register values were changed. See LAZY-B-GUIDE.md. The East Water Well 30 trend label was subsequently corrected in a separately authorized edit; see the dated Trends and history note below.
|
||||||
|
|
||||||
## Original October 20 coverage
|
## Original October 20 coverage
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user