atom-hmi-ui-chatgpt/HANDOFF.md

# Current handoff

Last updated: 2026-10-21 (America/Edmonton)

## Latest Sweet Grass bin alarm audit — October 21, 2026

User identifies Main Plant PLC as old Horner and wants its alarms moved to new Codesys plant PLC. Read-only HMI audit traced 39 unique bin/equipment high/high-high/high-shutdown/full alarms: 17 Main PLC, 5 Groater PLC, 13 Codesys PLC, 4 SG Dryer. See SWEET-GRASS-GUIDE.md for exact IDs, coils, tags, enabled states and migration gaps. Air Screen/Grader/Paddy already have enabled Codesys pairs; Air Screen/Paddy retain enabled legacy pairs, Grader legacy pair disabled. Indent Codesys pair and Bin G HiHi output are configured but unpolled, with no matching Hi/HiHi HMI definitions found in targeted searches. H/J similarly named alarms span Main and Groater PLCs. No live changes or writes. Next: verify PLC-side equivalence and enable ownership before migration; original Bin G HMI control remains unfinished. This was not a full plant alarm audit.

## 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. Lazy B timer fields were subsequently removed at the user's request; see the Lazy B resolution below.

## Lazy B timer fields removed — October 21, 2026

**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

On October 21, 2026, corrected production https://www.atomhmi.com/site_kav_east_water/page_wells, Trend element 95ec8b60-2fe9-462d-8222-f2c069e41560. Renamed only the series bound to water:g_well30_flow_out_eu from Well 29 to Well 30. Saved the element/page, freshly reloaded/reopened configuration, and verified only the series name differs among 11 captured form controls (10 series retained). The live chart legend separately shows Well 29 and Well 30. Register, scale gpm, color #b8c564, axes, range buttons and navigator preserved; no register/operational writes. Updated KAV-GUIDE.md, SITE-STUDY.md, PROJECT.md and the relevant cloud guides. Local screenshot: /tmp/kav-east-water-well30-trend-fixed.jpg (not committed).

## Previous completed change — Well 10 chlorine binding

On October 21, 2026, the user authorized correcting production https://www.atomhmi.com/site_kav_water/ Well 10 New (well_10_new). Element Chlorine Current PPM / visible Target ppm, ID 4f503dce-01d9-4339-9d14-8668186b2cea, now has updateRegister water:g_well10ChemPPM instead of water:g_well1ChemPPM. Its display already referenced Well 10. Saved the element and page, observed Successfully Saved Page, then freshly reloaded/reopened and compared all 37 configuration controls: only updateRegister changed. No chlorine value, live register write or operational dosing test was submitted. KAV-GUIDE.md, SITE-STUDY.md, PROJECT.md and their relevant cloud notes updated. Evidence screenshot retained locally at /tmp/kav-well10-chlorine-fixed.jpg (not committed).

## Previous completed survey

Atom GIT connection recovered. Read repository AGENTS.md, PROJECT.md, HANDOFF.md, playbook/study/inventory and current cloud knowledge before inspection. Used the signed-in production browser at www.atomhmi.com.

- Created KAV-GUIDE.md, LONE-PINE-GUIDE.md, LAZY-B-GUIDE.md and SWEET-GRASS-GUIDE.md with verified configure-page maps, subtree patterns, representative read/write bindings, units and limits.
- Opened every Lone Pine (16), Lazy B (21) and KAV East Mill (4) page tree. Refreshed all seven site catalogs and selected active pages in the other KAV sites and Sweet Grass; preserved the previous full survey for remaining pages.
- KAV Main Mill has 43 listed pages, including newly observed Mill 2 Test (mill_2_test). Other KAV counts remain 4/29/38; Sweet Grass 51.
- Resolved Sweet Grass Motors and old Motors inspection gaps: 1,435 and 1,246 elements respectively; native root Copy verified.
- Corrected stale clipboard inference, expanded PAGE-INVENTORY.md and added large-tree Copy inspection guidance to ATOMHMI-PLAYBOOK.md.
- Saved cloud copies of the four guides and updated the knowledge-base index/common notes. Repository and cloud documents are manually maintained, not automatically synchronized.

## Previous survey validation and scope

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.

## Findings and resolution status

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.

## Next task

Read AGENTS.md, PROJECT.md and the specific site guide; reconnect the signed-in browser and inspect only the current affected subtree. This baseline context survey need not be repeated. Verify intended target before any change to a flagged binding. User's work environments are dev.atomhmi.com and atomhmi.com.

## Prior work retained

Earlier repository import preserved project knowledge. Mandel dashboards/settings, navigation cleanup and 81 non-latching HMI alarms; Shop overview/heating/actuator/trends/diagnostics and 22 non-latching alarms remain in their guides, not new work in this survey. Shop temperature limits remain 0 °C pending commissioning; a separate boiler-water sensor/target was not found. Do not edit Shop atGVL_alarmManager.

Original screenshots/JSON artifacts remain outside this repository. Browser sessions and chat history do not transfer through Git.

## Resume prompt

Use Atom GIT to open Auto/atom-hmi-ui-chatgpt on master. Read AGENTS.md, PROJECT.md, HANDOFF.md and the relevant site guide. Target site: [dev.atomhmi.com or atomhmi.com URL]. Task: [requested change]. Inspect current affected elements, update guides with verified changes, then commit and push documentation.

### Alarm history lookup — October 21, 2026

User requested checking whether any Bin G alarm previously occurred. Opened the alarm icon → Alarm History at https://www.atomhmi.com/site_sweetgrass/alarm_history. Requested Last 30 Days (September 22–October 21, 2026), then freshly reloaded and requested October 21, and finally Yesterday (October 20). Every attempt remained on Loading... without a history table, records, or an explicit empty-result message. No browser warning/error logs were captured. Occurrence, timestamps and retention therefore remain unverified; this is not evidence of no prior Bin G alarms. No acknowledgement, reset, alarm edits, register writes or page saves performed. User-confirmed update on October 21, 2026: Atom HMI was just updated and alarm logs moved to a new database; previous history is no longer available. This supersedes the earlier plan to retry for pre-migration records. Historical Bin G occurrences cannot be determined from the current database. The migration explains unavailable prior history, but the cause of the observed Loading... UI was not independently established. The intended Bin G enable/disable alarm path remains unresolved; determine it from current configuration or user/PLC confirmation.