Release Notes

ATLabs_RM2_MeshCore_1.14.1.AT.3 carries forward the RM-2 GPS power-management layer across MeshCore, plus the latest fresh-board repeater GPS stabilization work. GPS can be duty-cycled with a persisted interval setting, the receiver syncs time every time it wakes, and repeater/companion both inherit the same shared behavior from EnvironmentSensorManager.cpp and CommonCLI.cpp.

This release keeps the previously validated RM-2 work intact:

CASIC/AT6558R runtime GPS configuration for RM-2
working companion BLE and USB GPS
new RM-2 Companion Dual firmware with both BLE and USB CDC companion access in one image
working repeater GPS advert/telemetry
official MeshCore USB setup-tool compatibility for repeater location
RM-2 8 dBm radio clamp
AT Labs release naming cleanup to 1.14.1.AT.3
Companion Access

This release now includes three RM-2 companion firmware flavors:

Companion_BLE
Companion_USB
Companion_Dual
Companion_Dual keeps a single shared companion protocol/backend and allows only one active companion session at a time.

Transport arbitration in Companion_Dual:

BLE can advertise while idle
USB CDC takes priority when a host opens the serial session
if BLE is active and USB is opened, BLE is cleanly disconnected and ownership moves to USB
when USB closes, BLE advertising resumes and BLE can connect again

Operational note:

opening the USB serial port claims the companion session, even if the host is just a serial terminal and not the full companion app
New GPS control commands:

gps interval
gps interval 0
gps interval <seconds>
gps
gps sync
Semantics:

gps interval 0 = continuous GPS while enabled
gps interval <seconds> = wake on that cadence, sync time, then sleep
gps now reports active vs sleeping so duty-cycling doesn’t look like GPS is disabled
Companion Control

On companion, there is now a mechanism, but it is not yet a first-class toggle in the normal app UI.

What the official companion app currently exposes:

the location/privacy toggle, which we map to GPS on/off in MyMesh.cpp
What controls the update rate:

the shared CLI command: gps interval <seconds>
the underlying custom var path: gps_interval
So today, on companion:

on/off is available through the normal app location toggle
interval/rate is available through CLI or any client that can send the gps_interval custom var
there is no normal app control yet for “set GPS to every N seconds”