mirror of
https://github.com/MarekZegare4/MeshCore-Solo.git
synced 2026-09-14 15:16:40 +00:00
deploy: e47233f557
This commit is contained in:
MarekZegare4
@@ -1850,9 +1850,9 @@
|
||||
<h3 id="clock-tools-alarm-timer-stopwatch">Clock tools — Alarm, Timer, Stopwatch</h3>
|
||||
<p><strong>Press Enter</strong> (short press) on the Clock page to open <strong>Clock Tools</strong>, a small menu with three time utilities. <strong>Cancel</strong> backs out one level (tool → menu → home). The same menu also has an entry under <strong>Tools › System</strong>, so it's reachable without the Clock page.</p>
|
||||
<h4 id="alarm">Alarm</h4>
|
||||
<p>A wake alarm with an optional repeat. Rows: <strong>Hour</strong>, <strong>Minute</strong>, <strong>Repeat</strong> and <strong>Armed</strong>. <strong>Enter</strong> on Hour or Minute opens the digit editor (LEFT/RIGHT moves between the tens/units, UP/DOWN changes the digit); <strong>Enter</strong> on Repeat cycles <strong>Off → Daily → Weekdays → Weekends → Off</strong>; <strong>Enter</strong> on Armed toggles ON/OFF. The configured time is shown next to the <strong>Alarm</strong> menu row when armed, and the setting persists across reboots.</p>
|
||||
<p>A wake alarm with an optional repeat. Rows: <strong>Hour</strong>, <strong>Minute</strong>, <strong>Repeat</strong> and <strong>Armed</strong>. <strong>Enter</strong> on Hour or Minute opens the digit editor (LEFT/RIGHT moves between the tens/units, UP/DOWN changes the digit); <strong>Enter</strong> on Repeat cycles <strong>OFF → Daily → Weekdays → Weekends → OFF</strong>; <strong>Enter</strong> on Armed toggles ON/OFF. The configured time is shown next to the <strong>Alarm</strong> menu row when armed, and the setting persists across reboots.</p>
|
||||
<p>While an alarm is armed a bell icon signals it in two places: the top-left corner of the <strong>Clock page</strong> itself, and the <strong>top status bar</strong> of the other home pages (the status bar is hidden on the Clock page, which is why the clock face carries its own indicator). The bell is icon-only — the exact alarm time is on the <strong>Alarm</strong> row inside Clock Tools.</p>
|
||||
<p>The alarm is scheduled as an absolute fire instant, so it is <strong>robust to clock re-syncs</strong> — the mesh (every inbound packet), the companion app, GPS and the CLI can all jump the device clock at any moment. A correction that moves the clock a little still fires at the right wall-clock time; a jump that skips over the alarm time still fires (late). With <strong>Repeat</strong> set to Off (the default) the alarm disarms itself after firing once, same as before; with a repeat pattern set, it stays armed and re-schedules itself for the next matching day instead.</p>
|
||||
<p>The alarm is scheduled as an absolute fire instant, so it is <strong>robust to clock re-syncs</strong> — the mesh (every inbound packet), the companion app, GPS and the CLI can all jump the device clock at any moment. A correction that moves the clock a little still fires at the right wall-clock time; a jump that skips over the alarm time still fires (late). With <strong>Repeat</strong> set to OFF (the default) the alarm disarms itself after firing once, same as before; with a repeat pattern set, it stays armed and re-schedules itself for the next matching day instead.</p>
|
||||
<p>The alarm only fires while the device is <strong>awake</strong> (it keeps running with the display off or locked). It cannot wake the device from a full <strong>Shutdown</strong> (the CPU and RAM are powered down), and needs a valid time source — it stays pending until the clock is synced.</p>
|
||||
<h4 id="timer-countdown">Timer (countdown)</h4>
|
||||
<p>A large <strong>HH:MM:SS</strong> readout with one digit underlined. <strong>LEFT/RIGHT</strong> moves the cursor one digit at a time, <strong>Up/Down</strong> changes the digit under it (minute/second tens cap at 5, hours at 23), and <strong>Enter</strong> starts the countdown. While running it shows <strong>H:MM:SS</strong> — <strong>Enter</strong> stops it, <strong>Cancel</strong> returns to the menu and leaves it counting. When it reaches zero the device rings, even if you have navigated to another screen.</p>
|
||||
|
||||
@@ -1742,7 +1742,7 @@
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Auto-lock</td>
|
||||
<td>on / off</td>
|
||||
<td>ON / OFF</td>
|
||||
<td>Locks device when display turns off</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -1772,7 +1772,7 @@
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Full refresh interval <em>(e-ink only)</em></td>
|
||||
<td>off / 5 / 10 / 20 / 30</td>
|
||||
<td>OFF / 5 / 10 / 20 / 30</td>
|
||||
<td>Partial refreshes between full clears; reduces ghosting on long sessions</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@@ -1790,7 +1790,7 @@
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Buzzer</td>
|
||||
<td>On / Off / Auto</td>
|
||||
<td>ON / OFF / Auto</td>
|
||||
<td>Auto: silences while BLE connected, re-enables on disconnect</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -1936,13 +1936,13 @@
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Low battery</td>
|
||||
<td>off / 3.0 V / 3.1 V / 3.2 V / 3.3 V / 3.4 V / 3.5 V</td>
|
||||
<td>OFF / 3.0 V / 3.1 V / 3.2 V / 3.3 V / 3.4 V / 3.5 V</td>
|
||||
<td>Auto-shutdown threshold; also sets the 0 % anchor for the battery percentage indicator</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>GPS pwr <em>(if GPS detected)</em></td>
|
||||
<td>off / 1 min / 5 min / 15 min / 30 min / 1 h</td>
|
||||
<td><strong>Battery saver.</strong> Cycles GPS off between fixes instead of running it continuously; each wake waits for a fix (up to 60 s) before sleeping again for the chosen interval. Automatically stays continuously on regardless of this setting whenever something needs a live position — an active Trail recording, Map › Live share, an armed Locator, the Compass / Nearby navigate view, or an in-flight <code>!gps fix</code> bot request. <code>off</code> (default) matches earlier releases: GPS runs continuously whenever enabled. The GPS status icon blinks while napping between fixes.</td>
|
||||
<td>OFF / 1 min / 5 min / 15 min / 30 min / 1 h</td>
|
||||
<td><strong>Battery saver.</strong> Cycles GPS off between fixes instead of running it continuously; each wake waits for a fix (up to 60 s) before sleeping again for the chosen interval. Automatically stays continuously on regardless of this setting whenever something needs a live position — an active Trail recording, Map › Live share, an armed Locator, the Compass / Nearby navigate view, or an in-flight <code>!gps fix</code> bot request. <code>OFF</code> (default) matches earlier releases: GPS runs continuously whenever enabled. The GPS status icon blinks while napping between fixes.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Units</td>
|
||||
@@ -2027,7 +2027,7 @@
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Resend</td>
|
||||
<td>off / 1×–5×</td>
|
||||
<td>OFF / 1×–5×</td>
|
||||
<td>Auto-resend an on-device direct message this many times when no delivery ACK is received (default 2×)</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
||||
@@ -2376,17 +2376,17 @@ The <strong>Map</strong> view is also reachable directly from the home carousel
|
||||
<tr>
|
||||
<td>Auto-pause</td>
|
||||
<td>always</td>
|
||||
<td>Off / 1 / 2 / 5 min — auto-freeze the trail after a stop, resume on movement (see below)</td>
|
||||
<td>OFF / 1 / 2 / 5 min — auto-freeze the trail after a stop, resume on movement (see below)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Mark avg</td>
|
||||
<td>always</td>
|
||||
<td>Off / 5 / 10 / 30 s — GPS averaging for <strong>Mark here</strong> (see Waypoints below)</td>
|
||||
<td>OFF / 5 / 10 / 30 s — GPS averaging for <strong>Mark here</strong> (see Waypoints below)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Auto-save</td>
|
||||
<td>always</td>
|
||||
<td>Off / On — auto-write the live trail to flash on shutdown, so a <strong>low-battery auto-shutdown</strong> doesn't lose the route (see below)</td>
|
||||
<td>OFF / ON — auto-write the live trail to flash on shutdown, so a <strong>low-battery auto-shutdown</strong> doesn't lose the route (see below)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Readout</td>
|
||||
@@ -2408,7 +2408,7 @@ The <strong>Map</strong> view is also reachable directly from the home carousel
|
||||
<h3 id="waypoints">Waypoints</h3>
|
||||
<p>A waypoint is a saved spot — your car, camp, a water source — that you can navigate back to later. Waypoints are <strong>independent of the trail</strong>: they live in their own flash file (<code>/waypoints</code>), survive a reboot, and are <strong>not</strong> cleared by <em>Reset trail</em>. Up to 16 can be stored — the Waypoints list header shows how many are in use (e.g. <code>WAYPOINTS 3/16</code>).</p>
|
||||
<p><strong>Dropping a waypoint</strong> — <strong>Hold Enter → Mark here</strong>. This captures the current GPS fix and opens the on-screen keyboard for a short label (up to 11 characters — e.g. <code>CAR</code>, <code>CAMP</code>, <code>H2O</code>). Leaving it blank auto-names it <code>WP1</code>, <code>WP2</code>, … Marking works whether or not the trail is being recorded; it needs a GPS fix (otherwise it reports <em>No GPS fix</em>).</p>
|
||||
<p><strong>GPS averaging</strong> — with <strong>Settings → Mark avg</strong> set (5 / 10 / 30 s), <em>Mark here</em> doesn't snapshot a single fix; it samples the GPS once a second for that window and stores the <strong>mean</strong> position, for a steadier mark than one instantaneous reading (handy for a precise spot — a cache, a car, a trailhead). A short screen shows the time left and the sample count while it runs; <strong>Cancel</strong> aborts. When the window closes it opens the label keyboard as usual. With <strong>Mark avg = Off</strong> (the default) marking is instant.</p>
|
||||
<p><strong>GPS averaging</strong> — with <strong>Settings → Mark avg</strong> set (5 / 10 / 30 s), <em>Mark here</em> doesn't snapshot a single fix; it samples the GPS once a second for that window and stores the <strong>mean</strong> position, for a steadier mark than one instantaneous reading (handy for a precise spot — a cache, a car, a trailhead). A short screen shows the time left and the sample count while it runs; <strong>Cancel</strong> aborts. When the window closes it opens the label keyboard as usual. With <strong>Mark avg = OFF</strong> (the default) marking is instant.</p>
|
||||
<p><strong>Adding by coordinates</strong> — open <strong>Hold Enter → Waypoints</strong> and select the <strong>+ Add by coords</strong> row (always the last entry in the list). This creates a waypoint without being there — no GPS fix required (handy for a meeting point or a spot read off a map). It opens a small form with three editable rows plus <strong>Save</strong>:</p>
|
||||
<table>
|
||||
<thead>
|
||||
@@ -2481,10 +2481,10 @@ If the companion app is connected via <strong>BLE</strong>, the export is safe
|
||||
</blockquote>
|
||||
<hr />
|
||||
<h2 id="auto-advert">Auto-Advert</h2>
|
||||
<p>Periodically broadcasts a 0-hop advert with your GPS position. Configurable interval: off / 30 s / 1 min / 2 min / 5 min / 10 min / 30 min / 1 h. A blinking <strong>A</strong> appears in the status bar while active.</p>
|
||||
<p>Periodically broadcasts a 0-hop advert with your GPS position. Configurable interval: OFF / 30 s / 1 min / 2 min / 5 min / 10 min / 30 min / 1 h. A blinking <strong>A</strong> appears in the status bar while active.</p>
|
||||
<blockquote>
|
||||
<p>[!TIP]
|
||||
<strong>Audible connection heartbeat</strong> — the device chirps each time it <em>receives</em> an advert from any node (sound chosen in <strong>Settings › Sound › AD sound</strong>). With Auto-Advert running on both ends (e.g. two people on a hike), each hearing the other's periodic advert becomes a hands-free "in range" beep — no need to look at the screen. It fires for <strong>every</strong> received advert, so in a busy mesh it can get chatty; choose <code>None</code> in <strong>Settings › Sound › AD sound</strong> to silence just this event, or set <strong>Settings › Sound › Advert scope</strong> to <code>Zero-hop</code> to limit it to local adverts only. You can also set <strong>Settings › Sound › Buzzer</strong> to <em>Off</em> (or <em>Auto</em>, which mutes while a companion app is connected) to silence all buzzer output.</p>
|
||||
<strong>Audible connection heartbeat</strong> — the device chirps each time it <em>receives</em> an advert from any node (sound chosen in <strong>Settings › Sound › AD sound</strong>). With Auto-Advert running on both ends (e.g. two people on a hike), each hearing the other's periodic advert becomes a hands-free "in range" beep — no need to look at the screen. It fires for <strong>every</strong> received advert, so in a busy mesh it can get chatty; choose <code>None</code> in <strong>Settings › Sound › AD sound</strong> to silence just this event, or set <strong>Settings › Sound › Advert scope</strong> to <code>Zero-hop</code> to limit it to local adverts only. You can also set <strong>Settings › Sound › Buzzer</strong> to <em>OFF</em> (or <em>Auto</em>, which mutes while a companion app is connected) to silence all buzzer output.</p>
|
||||
</blockquote>
|
||||
<hr />
|
||||
<h2 id="live-share">Live Share</h2>
|
||||
@@ -2543,7 +2543,7 @@ If the companion app is connected via <strong>BLE</strong>, the export is safe
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Heartbeat</td>
|
||||
<td>Off / 5 / 15 min</td>
|
||||
<td>OFF / 5 / 15 min</td>
|
||||
<td>Optional keep-alive: re-send even while stationary, so the other end knows you're still there.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@@ -3104,7 +3104,7 @@ Mark the spot first with <strong>Tools › Trail → Hold Enter → Mark here</s
|
||||
<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="gpio">GPIO</h2>
|
||||
<p><em>Board-specific — currently Wio Tracker L1 only.</em> Four otherwise-unused pins (GPIO1-GPIO4) are exposed for general-purpose use. Each pin gets its own row showing its current mode; <strong>Enter</strong> (or LEFT/RIGHT) cycles it through <strong>Off → Input → Output</strong> and back to Off — GPIO1 and GPIO2 additionally step through <strong>Analog</strong> between Output and Off (GPIO3/GPIO4 have no ADC channel, so their cycle skips it). Switching a pin's mode shows a brief confirmation (<code>GPIO1: Input</code>, <code>GPIO1: Output</code>, …).</p>
|
||||
<p><em>Board-specific — currently Wio Tracker L1 only.</em> Four otherwise-unused pins (GPIO1-GPIO4) are exposed for general-purpose use. Each pin gets its own row showing its current mode; <strong>Enter</strong> (or LEFT/RIGHT) cycles it through <strong>OFF → Input → Output</strong> and back to OFF — GPIO1 and GPIO2 additionally step through <strong>Analog</strong> between Output and OFF (GPIO3/GPIO4 have no ADC channel, so their cycle skips it). Switching a pin's mode shows a brief confirmation (<code>GPIO1: Input</code>, <code>GPIO1: Output</code>, …).</p>
|
||||
<p>Once a pin is set to <strong>Output</strong>, a second <strong>State</strong> row appears right underneath it — <strong>Enter</strong> toggles it <strong>ON</strong>/<strong>OFF</strong>, with its own confirmation. The direction (Mode row) and the on/off state (State row) are deliberately separate: changing one never surprises you by also changing the other.</p>
|
||||
<ul>
|
||||
<li><strong>Input</strong> shows its live level inline on the Mode row: <code>Input (High)</code> / <code>Input (Low)</code>, refreshed continuously.</li>
|
||||
|
||||
Reference in New Issue
Block a user