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

Document verified Lazy B motor RPM graph additions

Browse Source
This commit is contained in:
snkbyte
2026-10-22 04:37:26 +00:00
parent 595c7ccd17
commit 77b981be0d
3 changed files with 26 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
HANDOFF.md
+11
View File
@@ -2,6 +2,17 @@
Last updated: 2026-10-21 (America/Edmonton)
## Motor RPM trends added — October 21, 2026
User-authorized production graph change at https://www.atomhmi.com/site_lazy_b/ (the requested site_lazyb resolves in project context to Lazy B, site_lazy_b). Edited existing Trend forms through Configure Pages; no register definitions, polling, setpoints or operational commands changed.
- Receiving (page_receiving), Trend 8ba2e7b6-c517-4a04-b8db-aa9479111724: retained six speed/current series and added M01 RPM, M02 RPM, M03 RPM, M04 RPM, bound respectively to grain:g_m01Spd_out_eu through grain:g_m04Spd_out_eu. Colors: M01 blue #0072B2; M02 vermilion #D55E00; M03 green #009E73; M04 purple #CC79A7.
- Reclaim (page_reclaim), Trend 88723cfc-585b-4e32-bf0f-fdacca341fca: retained M31 speed/current and added M29 RPM (blue #0072B2), M30 RPM (vermilion #D55E00), M31 RPM (green #009E73), using grain:g_m29Spd_out_eu, grain:g_m30Spd_out_eu, grain:g_m31Spd_out_eu.
- Each graph has its own RPM scale (name/id RPM), min 0, automatic maximum, opposite true, neutral #444444 title/labels. The native renderer adds tickAmount "7". Colors distinguish RPM sensors within each sequence graph; they do not indicate alarm state.
- Verified these RPM bindings from existing read-only numerical displays. M02TEMP and M02 both reference g_m02Spd_out_eu; charted this sensor once as M02 RPM. Separate physical sensor ownership for M02TEMP remains unverified. M21–M28 cards on Reclaim have no RPM display. Grain Motors has no Trend components in its current editor tree.
- Saved both pages and freshly reloaded/reopened native Copy configurations. Full subtree comparisons, excluding regenerated data.id values, matched the intended series/scale additions plus native tickAmount only. Original element IDs and other configuration were retained. Fresh runtime pages show all seven RPM legend entries and RPM axes. Motors were off at verification; nonzero historical RPM plotting was not established.
- Local originals: /tmp/lazy-b-rpm-backup.json. Runtime screenshots: /tmp/lazy-b-receiving-rpm.png and /tmp/lazy-b-reclaim-rpm.png. These local artifacts are not committed.
## Gladacres read-only diagnostics check — October 21, 2026
October 21 Gladacres check: all 30 diagnostic/maintenance entries are enabled and Terminal is configured as {}. The native Device Status page and Atom dashboard both populated readings without any saved configuration change (CPU 63.7 °C, HMI 1012 observed). Most diagnostics poll every 600 seconds; uptime is configured for 10 seconds but was about 2–5 minutes old during checks. Initial blank register-table values were not proof of a complete outage. Delayed uptime reporting remains unexplained; no agent/connection cause or repair was established. No commands, resets, updates, reboots, service restarts or log uploads. See GLADACRES-GUIDE.md.