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

docs: record unavailable Sweet Grass alarm history lookup

Browse Source
This commit is contained in:
snkbyte
2026-10-21 19:25:35 +00:00
parent 73e71e7dd6
commit a54a5cc4e8
2 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
HANDOFF.md
+4
View File
@@ -53,3 +53,7 @@ Original screenshots/JSON artifacts remain outside this repository. Browser sess
## Resume prompt ## 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. 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. Next: retry when history retrieval works, search Bin G / ALM-436 / Codesys Bin G Hi-Hi identifiers, and record the returned range and timestamps.
SWEET-GRASS-GUIDE.md
+4
View File
@@ -82,3 +82,7 @@ Verified in Main PC (main):
- 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. - 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. 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.
### 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. Next: retry when history retrieval works, search Bin G / ALM-436 / Codesys Bin G Hi-Hi identifiers, and record the returned range and timestamps.