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.
SWEET-GRASS-GUIDE.md
+15
View File
@@ -67,3 +67,18 @@ These are dated prior observations, not a new register-table audit on October 21
Use this guide and the earlier full catalog instead of repeating the general survey. Verify current Title/slug and the particular subtree before editing. Preserve roots, location anchors, read/write distinctions, state mappings, chart series/scales/navigator and time conversions.
No PLC commands, setpoint writes, motor tests, alarm-latching changes or device actions were performed. History retention, alarm notification/latching and physical interlocks remain outside this survey. Old/test page names do not establish which content is current or safe to modify.
## Bin G Hi-Hi enable/disable investigation — October 21, 2026
User requested an Atom HMI enable/disable control for Sweet Grass Bin G Hi-Hi. Inspected production https://www.atomhmi.com/site_sweetgrass/ after reading repository instructions and cloud knowledge/site guide. No site changes or operational writes were made; target alarm path needs clarification.
Verified in Main PC (main):
- HMI alarm ALM-436 has description ALM-436, message "Bin G Full", calculation `|{register:main:Alm436}|`, enabled true, latching false, Warning importance, one-second update, zero on/off delays, notification groups Atom Notifications and Default Notifications.
- Source register Alm436 is enabled, observed 0, Main PLC slave, Modbus slave 1, Coil 4427, Bit format, bit 0, Swapped checked; On Change/two-second update, logging disabled.
- Separate Codesys register clean_g_binG_lvl_limits_hihi_alm_in_en has description Bin G level and address `{ "tag": "sg_cleaning.g.binG_lvl.limits.hihi.alm.in_en" }`. Enabled is unchecked; configured On Change/one-second update and logging disabled. No current value was available. This is a candidate alarm-enable input, not a verified control for ALM-436.
- Separate clean_g_binG_lvl_limits_hihi_in_en, ...hihi_in_sp, ...hihi_out and ...hihi_alm_out definitions also exist with Enabled No. Do not conflate threshold enable with alarm enable or infer PLC write ownership from names.
- clean_g_binG_lvl_out_eu is enabled and observed about 84.45–84.56; this readback does not establish the alarm path.
- Main PC tables currently report 20,055 registers and 1,538 alarms. Searching Bin alarm messages found ALM-436 but no Bin G Hi-Hi message.
- Navigation Bins opens page_bin_2 (editor Title Bin 2, slug bin_2), which displays Bin G among the bin gauges. The separately configured Bins page (slug bins) displays H/J/bagging/K/L/M/N and is not the navigation target.
Asked whether the intended control is the Codesys level Hi-Hi alarm or the existing Main PLC Bin G Full alarm. Next: resolve the intended path and verified writable setting, add a supported native enable/disable control on the relevant operator page, preserve existing state, save/reload and verify configuration. Do not write Alm436 or an alarm output to simulate enable. No polling, thresholds, alarm definitions, notifications, latching, pages, or equipment commands changed during this investigation.