Commit Graph
3798 Commits
Author SHA1 Message Date
fdlamotte ca5804616e Merge pull request #3843 from fdlamotte/raki2cgps_time_sync
gps: support time sync on rak i2c gps
2026-11-16 12:30:17 -04:00
ripplebiz 33cd5dbd90 Merge pull request #3849 from liamcottle/fix/cc310-mutex-lock
Fix CC310 Mutex Lock
2026-11-15 18:09:10 +11:00
Liam Cottle b6a9b5d877 Merge pull request #3754 from netrunnereve/bluetooth-name
Allow the user to set a custom bluetooth name using the cli
2026-11-15 20:01:46 +13:00
liamcottle ab7b5d87a0 workaround for CC310 where mutex can still be locked after a failed verification 2026-11-15 18:22:21 +13:00
fdlamotte a367b11bec Merge pull request #3844 from Ve2mrx/fix/rak-gps-firstfix-diag
rak4631: forward the first-fix limit and gps diag to the serial GPS
2026-11-14 21:15:23 -04:00
fdlamotte 69bace867a Merge pull request #3845 from Ve2mrx/fix/gps-sync-before-settle
gps: don't let the settle time close a periodic window before the time sync
2026-11-14 21:13:58 -04:00
fdlamotte 08d59458c0 Merge pull request #3846 from meshcore-dev/reapply-3726
Fix USB serial issue on Xiao ESP32-S3 Wio (#1416) (#3726)
2026-11-14 21:11:41 -04:00
Cyclic3 e365863ffe Fix USB serial issue on Xiao ESP32-S3 Wio (#1416) (#3726)
* Initial attempt at fixing serial issue on Xiao ESP32-S3 Wio (#1416)

* restrict Xiao ESP32-S3 WIO fix to just that board
2026-11-14 21:06:23 -04:00
Martin BoissonneaultandClaude Opus 5.5 9bf8f92df5 gps: don't let the settle time close a periodic window before the time sync
In periodic mode a window closed after GPS_FIX_SETTLE_MS (10 s) from the
first fix even if the clock sync was still pending. The sync needs about
4 s of continuous valid fixes (time_valid > 2, reset on any pass without
a fix), so after a hot start, when the receiver reports a fix within
seconds but not yet steadily, the window could close unsynced. On a
board without an RTC the clock then stays at its default until the next
window, a whole period later.

Close the window only once the sync has been tried (done, not needed, or
refused by GPS_GUARD); the settle time and the satellite count apply
after that. The acquisition timeout still bounds the window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 18:23:54 -05:00
Martin BoissonneaultandClaude Opus 5.5 2596f0f11b rak4631: forward the first-fix limit and gps diag to the serial GPS
RakLocationProvider wraps a MicroNMEALocationProvider but did not override
setFirstFixTimeout(), getFirstFixTimeout() or formatDiagnostics(), so on
RAK4631 boards with a serial GPS:
- `gps firstfix` always answered "0 (no limit)" (the LocationProvider
  default), while the limit in force was the build default (1 h);
- `gps firstfix <n>` saved the value but never applied it, at once or at boot;
- `gps diag` gave the short base form, without the UART/NMEA counters or fm:.

Forward all three to the NMEA provider. The RAK12500 (I2C) path has no
first-fix limit, so it keeps reporting 0 and the short diagnostics.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 17:42:51 -05:00
Eve 0dbf8f62c3 change prefix as well 2026-11-14 15:17:32 -05:00
Florent 1e2c5557f7 gps: support time sync on rak i2c gps 2026-11-14 15:03:01 -04:00
Marcel Verdult 7f7512d94c rak: keep WB_IO2 driven HIGH after a failed RAK12500 probe (#3834)
The I2C probe left WB_IO2 as an input when no RAK12500 answered. WB_IO2
switches the 3V3_S slot rail, which also powers a serial GPS. On base
boards that pull this line low, the serial GPS lost power right after
detection and never got a fix (#3830). Before df5a768c the pin stayed
HIGH, so keep it driven HIGH again. WB_IO4 and WB_IO5 still go back to
inputs.
2026-11-14 08:13:08 -04:00
Eve 2a53a81e82 use ble.name 2026-11-13 20:35:32 -05:00
Liam Cottle a4c66307a8 Merge pull request #3032 from Quency-D/heltec-rc52
Add heltec rc52
2026-11-14 10:43:40 +13:00
fdlamotte 888c7ca083 Merge pull request #3821 from AlexandrTyshchenko/feature/gps-guard-3d-fix
GPS: keep the GPS on for a 3D fix, prefer a recent 3D fix over a 2D one
2026-11-13 14:48:56 -04:00
fdlamotte 65cae3bc1c Merge branch 'dev' into feature/gps-guard-3d-fix 2026-11-13 14:48:02 -04:00
fdlamotte 7a900cf1c8 Merge pull request #3823 from AlexandrTyshchenko/fix/gps-first-fix-timeout
Limit the first periodic GPS acquisition after boot
2026-11-13 14:47:17 -04:00
Olexandr Tyshchenko 402abb7dbd GPS: accept a 2D fix, but keep the GPS on for a 3D fix
Per review: a 2D fix is valid, only less precise, and in some places a
receiver never gets a 3D fix. So the guard no longer rejects it; instead
the fix mode decides when the GPS may sleep:

- the fix mode is read from GSA for every NMEA receiver, not only with
  GPS_GUARD (`fm:` in `gps diag`), and stored with the last fix;
- in periodic mode, and for `gps once`, the GPS sleeps only after a 3D
  fix (or a fix from a receiver that does not report the mode); after a
  2D fix it stays on up to the acquisition timeout;
- a 2D fix does not replace a 3D fix younger than 5 min
  (GPS_3D_FIX_PREFERRED_MS).
2026-11-13 14:30:24 +02:00
Olexandr Tyshchenko 069b9fdaf8 GPS: first fix timeout as a saved setting (gps firstfix), 1 h by default
A cold start can take up to ~30 min with a weak sky view, so the default
limit before the first fix since boot goes from 15 min to 1 h.

The limit is now a GPS preference, set with `gps firstfix <duration>`
(0 = no limit, at most 1 day) and saved with the other GPS settings, so
repeaters and companions can use different values without a rebuild.
GPS_FIRST_FIX_TIMEOUT_MS stays as the build default.
2026-11-13 14:29:02 +02:00
Eve 4c7a134e15 add cli option to set custom bluetooth name 2026-11-12 11:09:43 -05:00
Olexandr Tyshchenko ac2bf9372a Limit the first periodic GPS acquisition after boot
Before the first fix since boot, a periodic acquisition had no timeout. If no
fix is accepted (no sky view, no antenna, or a guard rejecting spoofed fixes),
the receiver then stayed on until a fix was accepted.

Give that window its own limit, GPS_FIRST_FIX_TIMEOUT_MS (15 min by default,
enough for a full almanac; 0 keeps the old behaviour). It counts as a miss and
the next acquisition starts after the configured period.
2026-11-12 10:48:10 +02:00
Quency-D 242b5db7fa Fix RC52 unused SPI1 MISO pin mapping
Use pin index 0, which maps to NRFX_SPIM_PIN_NOT_USED, to avoid the nRF52 SPI constructor indexing g_ADigitalPinMap[255]. Remove the absent MISO shutdown reset so the sentinel cannot reset physical P0.00. Follows the variant-side fixes in #3188 and #3189.

Validated heltec_rc52_repeater and heltec_rc52_companion_radio_ble builds. ELF disassembly confirms the MISO lookup uses map[0]=0xFF instead of the +1020-byte read and shutdown has no P0.00 reset. No hardware testing performed.
2026-11-12 15:54:21 +08:00
Quency-D dd83853585 Fix RC52 companion radio builds 2026-11-12 14:20:08 +08:00
Quency-D 38d95975e8 Merge pull request #20 from meshcore-dev/dev
merge Dev
2026-11-12 14:03:11 +08:00
Liam Cottle bb870313e4 Merge pull request #3822 from liamcottle/fix/3811
fix for mdns string not compiling due to ambiguous overload
2026-11-12 16:10:48 +13:00
liamcottle e3c1c34828 fix for mdns string not compiling due to ambiguous overload 2026-11-12 16:08:30 +13:00
Olexandr Tyshchenko 172e9d4290 GPS guard: reject a fix the receiver reports as 2D (GSA)
The guard checked satellites and HDOP but not the fix type. When the
receiver sends GSA, a fix it reports as 2D or no-fix is now rejected
(`rej 2d`). Receivers without GSA are unchanged (fix mode unknown).
GPS_GUARD_REQUIRE_3D=0 turns the check off. `gps diag` shows the fix
mode as `fm`.
2026-11-12 00:34:05 +02:00
fdlamotte 7812ecaea6 Merge pull request #3819 from nullrouten0/fix/gps-nmea-buffer-tail
GPS: stop MicroNMEA reading past the NMEA buffer
2026-11-11 18:29:30 -04:00
nullrouten0andClaude Sonnet 5.5 e1c1d76c5f GPS: stop MicroNMEA reading past the NMEA buffer
Add a 16-byte zeroed tail behind the 100-byte NMEA buffer. MicroNMEA's
fixed-width field skips can read a few bytes past the end of a malformed
sentence; with the tail those reads land on NUL bytes.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-11 17:58:36 +00:00
fdlamotte 6e6b7b105f Merge pull request #3817 from AlexandrTyshchenko/docs/gps-guard-alert-telemetry
GPS guard: drop leftovers of the alert telemetry channel
2026-11-11 10:39:49 -04:00
Olexandr Tyshchenko b920e7d249 GPS guard: drop leftovers of the alert telemetry channel
#3813 removed the telemetry channel for the GPS time alert. Remove the
docs sentence that still described it and the now unused
GpsGuard::getAlertOffset().
2026-11-11 16:18:58 +02:00
fdlamotte c4258a5beb Merge pull request #3801 from AlexandrTyshchenko/feature/gps-guard-time-wait
GPS guard: show "time wait" instead of "rej nofix" between fixes
2026-11-11 10:13:11 -04:00
fdlamotte 0f51fd70e7 Merge pull request #3815 from fdlamotte/advert_loc_pref
CommonCLI: get/set loc to replace gps advert command
2026-11-11 10:11:49 -04:00
Florent bed7286192 CommonCLI: get/set loc to replace gps advert command 2026-11-11 09:52:03 -04:00
fdlamotte 1e384b109d Merge pull request #3813 from fdlamotte/gps_guard_telem_removal
gps_guard: remove time alert telemetry
2026-11-11 08:06:44 -04:00
fdlamotte d1d802717a Merge pull request #3811 from fdlamotte/mdns_using_char
companion_radio: rewrite mdns part removing String class
2026-11-11 07:58:59 -04:00
Florent 79e0f4eafe gps_guard: remove time alert telemetry 2026-11-11 07:58:39 -04:00
fdlamotte 5a762ad907 Merge pull request #3812 from fdlamotte/revert-3784
Revert "Merge pull request #3784 from Maxwell456/feature/repeater-his…
2026-11-11 07:52:27 -04:00
Florent 74f1f5a156 Revert "Merge pull request #3784 from Maxwell456/feature/repeater-history"
This reverts commit f678f6ac15, reversing
changes made to b8ae75d258.
2026-11-11 07:49:41 -04:00
Florent 85bba10742 companion_radio: rewrite mdns part removing String class 2026-11-11 07:37:24 -04:00
fdlamotte e7c6d079cc Merge pull request #3810 from fdlamotte/revert_rak13302_tests
tests: revert rak13302 tests
2026-11-11 07:30:25 -04:00
Florent 0147165b14 tests: revert rak13302 tests 2026-11-11 07:26:01 -04:00
Liam Cottle 09eac55bc3 Merge pull request #3807 from Valentin-Metz/fix/cli-reply-buffer-overflow
Fix stack-buffer overflow in CLI reply buffers
2026-11-11 17:37:42 +13:00
Valentin Metz 224658694f Fix stack-buffer overflow in CLI reply buffers
The remote-CLI reply buffers in onPeerDataRecv() (repeater, room server,
sensor) and BaseChatMesh were sized temp[166] for a 5-byte datagram
header plus 161 bytes of reply. But MyMesh::handleCommand() first
reflects a 3-byte correlation prefix (e.g. 'aa|') into the reply, after
which CommonCLI commands may write up to 160 chars + NUL into the
remaining 158 bytes -- overflowing the buffer by 2 bytes (e.g. a full
'regions' listing via exportTo(reply, 160)).

Triggering this remotely crashes the node (observed as an unresponsive
repeater after a prefixed 'regions' query); the 2 out-of-bounds bytes
are a printable region-name character and a NUL.

Size the buffers for the full worst case instead:
5 header + 3 prefix + 160 reply + 1 NUL = 169.

Verified with a host ASan harness reproducing the exact layout:
prefixed 'regions' with a 25-region listing overflowed temp[166]
(BufStream::write, RegionMap.cpp) and now passes clean with temp[169];
unprefixed (serial) path unaffected.
2026-11-11 05:30:54 +01:00
Olexandr Tyshchenko 196ca97751 GPS guard: show "time wait" instead of "rej nofix" between fixes
When the last GPS time check passed but there is no current trusted fix
(e.g. the GPS is asleep between periodic fixes), gps guard showed
"time rej nofix", which reads like a rejection although the clock is fine.
Show "time wait" instead. A real rejection without a trusted fix (GPS time
arriving while fixes are rejected) still shows "rej nofix".
2026-11-11 01:48:12 +02:00
fdlamotte ef4477b69d Merge pull request #3798 from AlexandrTyshchenko/feature/gps-baud-probe-list
GPS: GPS_BAUD_PROBE_LIST as a build flag for any NmeaGpsDriver; enable on Station G2/G3
2026-11-10 18:57:35 -04:00
Olexandr Tyshchenko ef6ef2e9d2 GPS: GPS_BAUD_PROBE_LIST as a build flag for any NmeaGpsDriver; enable on Station G2/G3
The probe list was wired only in variants/promicro/target.cpp. It is now the
default list of NmeaGpsDriver when GPS_BAUD_PROBE_LIST is set, so a variant
enables baud autodetection with a build flag alone.

Station G2 and G3 enable it: their Grove UART connector is used with M5Stack
Unit GPS modules, which default to 115200.
2026-11-10 23:51:29 +02:00
fdlamotte f678f6ac15 Merge pull request #3784 from Maxwell456/feature/repeater-history
Add min/max/avg history queries to repeaters
2026-11-10 12:42:53 -04:00
fdlamotte b8ae75d258 Merge pull request #3770 from lihardyextreme/feature-mdns
feat: mDNS ESP32 - enable local network discovery over mDNS
2026-11-10 12:07:18 -04:00