deploy: 32c50d1cfe

solo_features/tools_screen/tools_screen/index.html

@@ -1407,6 +1407,28 @@
       </ul>
     </nav>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#diagnostics" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Diagnostics
+      
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#repeater" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Repeater
+      
+    </span>
+  </a>
+  
 </li>
       
     </ul>
@@ -1611,6 +1633,28 @@
       </ul>
     </nav>
   
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#diagnostics" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Diagnostics
+      
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#repeater" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Repeater
+      
+    </span>
+  </a>
+  
 </li>
       
     </ul>
@@ -1657,7 +1701,7 @@
 </tr>
 </tbody>
 </table>
-<p>The Tools screen is a hub for GPS trail recording, nearby node browsing, ringtone editing, auto-reply bot, and auto-advert. Navigate the tool list with <strong>UP/DOWN</strong> and press <strong>Enter</strong> to open a tool.</p>
+<p>The Tools screen is a hub for GPS trail recording, nearby node browsing, ringtone editing, auto-reply bot, auto-advert, compass, device diagnostics, and repeater mode. Navigate the tool list with <strong>UP/DOWN</strong> and press <strong>Enter</strong> to open a tool.</p>
 <hr />
 <h2 id="nearby-nodes">Nearby Nodes</h2>
 <table>
@@ -2195,6 +2239,147 @@ If the companion app is connected via <strong>BLE</strong>, the export is safe
 </table>
 <p>Several commands can be combined in one message — <code>!batt !time !hops</code> is answered with a single <code>4.10V | 14:30 | 3 hops</code> reply (one transmission). A message with no recognised command falls through to the trigger bot.</p>
 <p>Commands also work on the <strong>monitored channel</strong> (the one selected for channel mode) — anyone there can query the node. Channel replies are broadcast to everyone, so unlike DM commands they respect quiet hours and use the shared per-channel cooldown. DM commands use the per-contact throttle.</p>
+<hr />
+<h2 id="diagnostics">Diagnostics</h2>
+<p>A single read-only screen of live device and mesh stats, refreshed once a second. On a small OLED the rows scroll with <strong>UP/DOWN</strong>; on a larger e-ink display they all fit at once.</p>
+<table>
+<thead>
+<tr>
+<th>Row</th>
+<th>Shows</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Uptime</td>
+<td>Time since boot (<code>d hh:mm:ss</code>)</td>
+</tr>
+<tr>
+<td>Total rx/tx</td>
+<td>All received / transmitted packets, summed across the categories below</td>
+</tr>
+<tr>
+<td>Msg</td>
+<td>Text and group-text packets, <code>rx/tx</code></td>
+</tr>
+<tr>
+<td>Advert</td>
+<td>Advert packets, <code>rx/tx</code></td>
+</tr>
+<tr>
+<td>Ack/Path</td>
+<td>Ack, path-return and trace packets, <code>rx/tx</code></td>
+</tr>
+<tr>
+<td>Other</td>
+<td>Everything else (requests, responses, control, raw, …), <code>rx/tx</code></td>
+</tr>
+<tr>
+<td>Forwarded</td>
+<td>Packets this node actually re-transmitted as a repeater (reflects overhear suppression, if on)</td>
+</tr>
+<tr>
+<td>Heap free</td>
+<td>Free / total heap</td>
+</tr>
+<tr>
+<td>Stack free</td>
+<td>Current task's minimum-ever stack headroom</td>
+</tr>
+<tr>
+<td>Noise floor</td>
+<td>Live radio noise floor (dBm)</td>
+</tr>
+<tr>
+<td>RSSI/SNR</td>
+<td>Signal strength / signal-to-noise of the last received packet</td>
+</tr>
+<tr>
+<td>Pool free</td>
+<td>Free entries in the packet pool</td>
+</tr>
+<tr>
+<td>Queue</td>
+<td>Packets waiting in the outbound queue</td>
+</tr>
+<tr>
+<td>Errors</td>
+<td>Radio error flags since boot/reset — <code>OK</code>, or tokens <code>F</code> (queue full), <code>C</code> (CAD timeout), <code>R</code> (RX-start timeout)</td>
+</tr>
+</tbody>
+</table>
+<p>The packet counters, <strong>Forwarded</strong> and <strong>Errors</strong> are cumulative since boot. <strong>Hold Enter</strong> opens a one-item <em>Reset counters</em> menu (Back dismisses it); the live readings (noise, RSSI/SNR, pool, queue, uptime) are not affected. <strong>Cancel/Back</strong> returns to the Tools list.</p>
+<p>The counters make the repeater behaviour observable: <strong>Forwarded</strong> confirms the node is actually relaying (not just configured to), and <strong>Pool free</strong> / <strong>Queue</strong> show whether forwarding is exhausting the packet pool. See <strong>Tools › Repeater</strong> for the relaying options.</p>
+<hr />
+<h2 id="repeater">Repeater</h2>
+<p>Turns the companion into a packet <strong>repeater</strong> while it keeps working as a normal companion — no separate firmware. By default, enabling it switches the radio to a dedicated repeater profile rather than relaying on whatever network you're chatting on (see <strong>Network</strong> below) — that matches the MeshCore community norm of repeaters sitting on a standard channel, not a private one. Loop-detection and an advert flood-depth cap are always applied. This screen keeps the toggle, the network/profile, and its flood-filter options together; live forwarding stats are on <strong>Tools › Diagnostics</strong>.</p>
+<p>Navigate with <strong>UP/DOWN</strong>; change a value with <strong>LEFT/RIGHT</strong> (or <strong>Enter</strong> for toggles). <strong>Cancel/Back</strong> saves and returns to Tools.</p>
+<table>
+<thead>
+<tr>
+<th>Setting</th>
+<th>Options</th>
+<th>Notes</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Repeater</td>
+<td>ON / OFF</td>
+<td>Master switch. The options below appear only while it is ON.</td>
+</tr>
+<tr>
+<td>Network</td>
+<td>Current / Custom</td>
+<td><strong>Custom</strong> <em>(default)</em>: enabling the repeater switches the radio to a dedicated profile (below) and disabling restores the companion's settings — so you can drop onto a separate repeater network and come back. A never-configured device seeds Custom with a frequency in the same band as your own network (433/868/915 MHz region), not a flat one-size-fits-all default — so it can't land outside what's legal for your region. Switching to Custom afterwards (if it was OFF and unconfigured) seeds it from your current settings instead. <strong>Current</strong>: relay on the companion's own frequency — opt-in; not the community norm.</td>
+</tr>
+<tr>
+<td>Rpt preset</td>
+<td>named presets</td>
+<td><em>(Custom only)</em> <strong>Enter</strong> picks a community/saved preset for the repeater profile.</td>
+</tr>
+<tr>
+<td>Rpt freq</td>
+<td>chip range</td>
+<td><em>(Custom only)</em> <strong>Enter</strong> opens the digit-by-digit editor (chip-validated bounds).</td>
+</tr>
+<tr>
+<td>Rpt SF / BW / CR</td>
+<td>5–12 / 7.8–500 kHz / 5–8</td>
+<td><em>(Custom only)</em> <strong>LEFT/RIGHT</strong> to adjust the profile's spreading factor, bandwidth, coding rate.</td>
+</tr>
+<tr>
+<td>Skip advert</td>
+<td>ON / OFF</td>
+<td>Don't re-flood <strong>advert</strong> packets (the highest-volume flood traffic); messages and acks still relay.</td>
+</tr>
+<tr>
+<td>Max hops</td>
+<td>OFF / 1–8</td>
+<td>Drop a flood packet once it has already travelled this many hops.</td>
+</tr>
+<tr>
+<td>Yield</td>
+<td>OFF / x2–x9</td>
+<td>Scales the retransmit delay for <strong>forwarded</strong> floods only (your own sends are unaffected), so a mobile companion defers to better-sited fixed repeaters. Widens the window for <strong>Suppress dup</strong>.</td>
+</tr>
+<tr>
+<td>Min SNR</td>
+<td>OFF / −20…10 dB</td>
+<td>Drop a flood copy received below this signal-to-noise threshold, so marginal fringe traffic isn't re-flooded.</td>
+</tr>
+<tr>
+<td>Suppress dup</td>
+<td>ON / OFF</td>
+<td>If the same flood packet is overheard from another node while still queued to retransmit, cancel our copy — a peer already relayed it. Cuts redundant airtime in dense meshes; pairs with <strong>Yield</strong>.</td>
+</tr>
+</tbody>
+</table>
+<p>The five flood filters are <strong>opt-in</strong> (default OFF, so a plain repeater is unaffected) and act on <strong>flood</strong> traffic only — on a direct route this node is the named next hop, so it never drops those.</p>
+<p><strong>Same network vs. separate network.</strong> With <strong>Network = Current</strong> (or a Custom profile set equal to your companion settings) the repeater stays on your own network — you keep messaging while relaying. With a <em>different</em> Custom profile the device moves entirely onto that network while relaying (a single radio can't be on two at once) and returns to your companion network when the repeater is switched off. The profile also re-applies after a reboot if the repeater was left on.</p>
+<p>While the repeater is on, a <strong>»</strong> indicator appears in the status bar (same blink convention as the auto-advert and trail markers) so you can tell it's relaying at a glance. Two radio settings are also overridden while relaying and restored afterwards: <strong>Settings › Radio › Pwr save</strong> is forced off (a repeater must listen continuously) and <strong>Auto pwr</strong> is forced off (a repeater holds full TX power for consistent relay reach). Both show <code>--</code> in Settings while the repeater is on.</p>
+<p>Live forwarding stats — <strong>Forwarded</strong>, <strong>Pool free</strong>, <strong>Queue</strong> — are shown on <strong>Tools › Diagnostics</strong>.</p>
+<p>While the repeater is ON, the bottom of the screen shows live stats: <strong>Forwarded</strong> (packets actually re-transmitted — reflects Suppress dup), <strong>Pool free</strong>, and <strong>Queue</strong>. The same numbers appear, alongside the full device picture, in <strong>Tools › Diagnostics</strong>.</p>