docs: audit Sweet Grass bin alarm PLC sources and migration gaps

2026-10-21 19:44:28 +00:00
parent 7e5e6f9f66
commit 8728839a20
3 changed files with 55 additions and 1 deletions
@@ -2,6 +2,10 @@

 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. Prior Lazy B timer work remains pending independently.
@@ -56,4 +60,4 @@ Use Atom GIT to open Auto/atom-hmi-ui-chatgpt on master. Read AGENTS.md, PROJECT

 ### 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.
+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.