From 77b981be0d6c9b907faec4186c5ae265e5e38475 Mon Sep 17 00:00:00 2001 From: Adam Mandel Date: Thu, 22 Oct 2026 04:37:26 +0000 Subject: [PATCH] Document verified Lazy B motor RPM graph additions --- HANDOFF.md | 11 +++++++++++ LAZY-B-GUIDE.md | 11 +++++++++++ PROJECT.md | 4 ++++ 3 files changed, 26 insertions(+) diff --git a/HANDOFF.md b/HANDOFF.md index 9808e90..17d9b3a 100644 --- a/HANDOFF.md +++ b/HANDOFF.md @@ -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. diff --git a/LAZY-B-GUIDE.md b/LAZY-B-GUIDE.md index fc42363..c60c1c7 100644 --- a/LAZY-B-GUIDE.md +++ b/LAZY-B-GUIDE.md @@ -104,6 +104,17 @@ Loadout controls M41: - One internal name is 100% Button but its configured value is 80; another writes 100. Internal element names alone are insufficient to establish a button's behavior. - Status expression references grain:g_m41_out_fault/open/close. No claim about physical valve movement or interlocks. +## 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. + ## Future use Use Main/Settings for navigation context, the specific well for water, Receiving/Reclaim for sequence controls, and Grain Motors for individual equipment. Diagnostics contains consequential maintenance actions; inspect its element configuration without clicking the operational buttons. Treat alarms pages as UI content, not an audit of Manage Alarms definitions. Test-named pages are existing content, not authorized disposable pages. \ No newline at end of file diff --git a/PROJECT.md b/PROJECT.md index 8a8bed4..7de3712 100644 --- a/PROJECT.md +++ b/PROJECT.md @@ -67,6 +67,10 @@ October 21 resolution: user chose to remove the unverified Time Since Start and - Cloud Atom guide: https://chatgpt.com/space/page_4f4290a63c008191bffe66804b6e1777 - Cloud Chep guide: https://chatgpt.com/space/page_c13336dbaeac81919fa1f2b07fbe3f6a +## Lazy B RPM trends — October 21, 2026 + +Production Receiving and Reclaim now chart seven distinct existing motor RPM sensors with separate RPM axes and distinct per-motor colors. Saved and verified after fresh configuration reload and runtime navigation. See LAZY-B-GUIDE.md for exact bindings, colors and validation limits. M02TEMP shares M02's configured RPM binding; no separate sensor was invented. + ## Retired sites — October 21, 2026 Current status — October 21, 2026: the user deleted and retired Demo (site_demo) and Westland (site_westland). Removed their five dashboard rows: Demo/demo, Demo/main, Demo/unknown, Westland/test_trailer and Westland/trailer_1. The saved dashboard now has 33 non-Global devices across the 31 accessible sites (30 with devices; Atom has Global scope only). The current Select Site catalog independently showed 31 sites and neither retired site. Do not recreate either site, its devices, diagnostic registers or Terminal sources unless the user explicitly requests reinstatement.