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

docs: record Sweet Grass Bin G alarm paths awaiting target clarification

Browse Source
This commit is contained in:
snkbyte
2026-10-21 19:16:50 +00:00
parent 140c7e93c0
commit 73e71e7dd6
2 changed files with 19 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
HANDOFF.md
+4
View File
@@ -2,6 +2,10 @@
Last updated: 2026-10-21 (America/Edmonton)
## 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.
## Latest investigation — Lazy B Well 3 timer repair awaiting PLC mapping
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.