447 Commits

Author	SHA1	Message	Date
Ben Meadors	09de0e3edb	Merge branch 'master' into develop	2025-09-14 08:15:25 -05:00
Ben Meadors	70724bef72	Fix overflow of time value (#7984) ... * Fix overflow of time value * Revert "Fix overflow of time value" This reverts commit 0847969201. * That got boogered up	2025-09-14 08:12:38 -05:00
Mike Robbins	bf4e2e8e86	Fix GPS gm_mktime memory leak (#7981)	2025-09-14 06:36:16 -05:00
Ben Meadors	2dc7760508	Scale probe buffer size based on current baud rate (#7975) ... * Scale probe buffer size based on current baud rate * Throttle bad time validation logging and fix time comparison logic * Remove comment * Missed the other instances * Copy pasta	2025-09-14 06:31:17 -05:00
Mike Robbins	00772996b6	Fix GPS gm_mktime memory leak (#7981)	2025-09-14 05:05:06 -05:00
Tom Fifield	d201f6a1ed	Guard bad time warning logs using GPS_DEBUG (#7897) ... In 2.7.7 / 2.7.8 we introduced some new checks for time accuracy. In combination, these result in a spamming of the logs when a bad time is found When the GPS is active, we're calling the GPS thread every 0.2secs. So this log could be printed 4,500 times in a no-lock scenario :) Reserve this experience for developers using GPS_DEBUG. Fixes https://github.com/meshtastic/firmware/issues/7896	2025-09-14 05:00:42 -05:00
Ben Meadors	ca4b98f2b1	Merge branch 'master' into develop	2025-09-09 08:42:29 -05:00
Ben Meadors	c8afbe68b5	Use char buffer for probeResponse (#7870) ... * Use char buffer for probeResponse * \Update src/gps/GPS.cpp Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Revert "\Update src/gps/GPS.cpp" This reverts commit 54d64e19f7. * Remove string --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>	2025-09-09 06:34:38 -05:00
Tom Fifield	d5bb566276	Only log good times. (It's not always a good time then) (#7904) ... Further to https://github.com/meshtastic/firmware/pull/7897 , there was another log line that was triggering indiscriminantly on GPS_INTERVAL_THRESHOLD . Rather than logging a bad time 4000 times, let's just log one good time when it is set.	2025-09-08 05:59:37 -05:00
Tom Fifield	2354c52b16	Only log good times. (It's not always a good time then) (#7904) ... Further to https://github.com/meshtastic/firmware/pull/7897 , there was another log line that was triggering indiscriminantly on GPS_INTERVAL_THRESHOLD . Rather than logging a bad time 4000 times, let's just log one good time when it is set.	2025-09-08 05:53:49 -05:00
Tom Fifield	81cb1e427f	Guard bad time warning logs using GPS_DEBUG (#7897) ... In 2.7.7 / 2.7.8 we introduced some new checks for time accuracy. In combination, these result in a spamming of the logs when a bad time is found When the GPS is active, we're calling the GPS thread every 0.2secs. So this log could be printed 4,500 times in a no-lock scenario :) Reserve this experience for developers using GPS_DEBUG. Fixes https://github.com/meshtastic/firmware/issues/7896	2025-09-07 19:29:26 -05:00
Quency-D	f825e61b89	Add a new GPS model CM121. (#7852) ... * Add a new GPS model CM121. * Add CM121 to Unicore. * Trunk fixes, remove unneded NMEA lines --------- Co-authored-by: Tom Fifield <tom@tomfifield.net>	2025-09-05 19:29:53 +10:00
Jonathan Bennett	1c1c0cc791	Portduino config refactor (#7796) ... * Start portduino_config refactor * refactor GPIOs to new portduino_config * More portduino_config work * More conversion to portduino_config * Finish portduino_config transition * trunk * yaml output work * Simplify the GPIO config * Trunk	2025-09-03 17:50:26 -05:00
Tom Fifield	3040e5a7bb	Fix GPS that hard code 2080 as the start time. (#7803) ... * Fix GPS that hard code 2080 as the start time. Some GPS chips, such as the AG3335 in T1000e and L96 have a hardcoded time of 2080-01-05 when they start up. To fix that in a way that seems permanent, let's ignore times that are more than 40 years since the firmware was built. We should followup in late 2039 to see if any changes are needed. Reported-By: @b8b8 * Update src/gps/RTC.cpp Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Put FORTY_YEARS in header and use in both places. * Restore Ben's nicer log lines. --------- Co-authored-by: Ben Meadors <benmmeadors@gmail.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>	2025-09-02 06:41:26 -05:00
Tom Fifield	7612799ef6	Fix GPS that hard code 2080 as the start time. (#7803) ... * Fix GPS that hard code 2080 as the start time. Some GPS chips, such as the AG3335 in T1000e and L96 have a hardcoded time of 2080-01-05 when they start up. To fix that in a way that seems permanent, let's ignore times that are more than 40 years since the firmware was built. We should followup in late 2039 to see if any changes are needed. Reported-By: @b8b8 * Update src/gps/RTC.cpp Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Put FORTY_YEARS in header and use in both places. * Restore Ben's nicer log lines. --------- Co-authored-by: Ben Meadors <benmmeadors@gmail.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>	2025-09-02 06:40:59 -05:00
Tom Fifield	a6b8202cd4	Hold for 20s after GPS lock (#7801) ... * Hold for >20s after GPS lock GPS chips are designed to stay locked for a while to download some data and save it. This data is important for speeding up future locks, and making them higher quality. Our present configuration could make every lock perform similar to first lock. This patch sets a hold of between 20s and 10% of the lock search time after lock is acquired. This should allow the GPS to finish its work before we turn it off. Fixes https://github.com/meshtastic/firmware/issues/7466 * Remove T1000E-specific GPS holds The new code does the same thing, for all devices. * Fix publishing settings * Cleanups, removing unused variables. * ifdef log line with GPS_DEBUG * fixQual is not a bool.	2025-09-02 06:06:06 -05:00
Tom Fifield	c5fad6cca1	Hold for 20s after GPS lock (#7801) ... * Hold for >20s after GPS lock GPS chips are designed to stay locked for a while to download some data and save it. This data is important for speeding up future locks, and making them higher quality. Our present configuration could make every lock perform similar to first lock. This patch sets a hold of between 20s and 10% of the lock search time after lock is acquired. This should allow the GPS to finish its work before we turn it off. Fixes https://github.com/meshtastic/firmware/issues/7466 * Remove T1000E-specific GPS holds The new code does the same thing, for all devices. * Fix publishing settings * Cleanups, removing unused variables. * ifdef log line with GPS_DEBUG * fixQual is not a bool.	2025-09-02 06:05:14 -05:00
Jonathan Bennett	bd3cbfc1ad	Add support for the RV-3028 on native Linux (#7802)	2025-09-01 08:04:04 -05:00
Jonathan Bennett	ca79760372	Add support for the RV-3028 on native Linux (#7802)	2025-08-31 21:08:58 -05:00
Tom Fifield	11db6d4dcc	Can't trust RTCs to tell the time. (#7779) ... Further to https://github.com/meshtastic/firmware/pull/7772 , we discovered that some RTCs have hard-coded start times well in the past. This patch gives RTCs the same treatment as GPS - if the time is earlier than BUILD_EPOCH, we don't use it. Fixes #7771 Fixes #7750	2025-08-29 13:23:14 -05:00
Tom Fifield	10c6836263	Can't trust RTCs to tell the time. (#7779) ... Further to https://github.com/meshtastic/firmware/pull/7772 , we discovered that some RTCs have hard-coded start times well in the past. This patch gives RTCs the same treatment as GPS - if the time is earlier than BUILD_EPOCH, we don't use it. Fixes #7771 Fixes #7750	2025-08-29 13:22:23 -05:00
Tom Fifield	d3e3a91096	We don't gotTime if time is 2019. (#7772) ... There are certain GPS chips that have a hard-coded time in firmware that they will return before lock. We set our own hard-coded time, BUILD_EPOCH, that should be newer and use the comparison to not set a bad time. In https://github.com/meshtastic/firmware/pull/7261 we introduced the RTCSetResult and improved it in https://github.com/meshtastic/firmware/pull/7375 . However, the original try-fix left logic in GPS.cpp that could still result in broadcasting the bad time. Further, as part of our fix we cleared the GPS buffer if we didn't get a good time. The mesh was hurting at the time, so this was a reasonable approach. However, given time tends to come in when we're trying to get early lock, this had the potential side effect of throwing away valuable information to get position lock. This change reverses the clearBuffer and changes the logic so if time is not set it will not be broadcast. Fixes https://github.com/meshtastic/firmware/issues/7771 Fixes https://github.com/meshtastic/firmware/issues/7750	2025-08-29 09:09:13 -05:00
Tom Fifield	5f8503c62d	We don't gotTime if time is 2019. (#7772) ... There are certain GPS chips that have a hard-coded time in firmware that they will return before lock. We set our own hard-coded time, BUILD_EPOCH, that should be newer and use the comparison to not set a bad time. In https://github.com/meshtastic/firmware/pull/7261 we introduced the RTCSetResult and improved it in https://github.com/meshtastic/firmware/pull/7375 . However, the original try-fix left logic in GPS.cpp that could still result in broadcasting the bad time. Further, as part of our fix we cleared the GPS buffer if we didn't get a good time. The mesh was hurting at the time, so this was a reasonable approach. However, given time tends to come in when we're trying to get early lock, this had the potential side effect of throwing away valuable information to get position lock. This change reverses the clearBuffer and changes the logic so if time is not set it will not be broadcast. Fixes https://github.com/meshtastic/firmware/issues/7771 Fixes https://github.com/meshtastic/firmware/issues/7750	2025-08-29 09:08:33 -05:00
Tom Fifield	bdedd0e1fe	Airoha GPS - ignore estimated fixes (#7429) ... TinyGPS Fix Quality has this information: 0 - fix not available, 1 - GPS fix, 2 - Differential GPS fix (values above 2 are 2.3 features) 3 = PPS fix 4 = Real Time Kinematic 5 = Float RTK 6 = estimated (dead reckoning) 7 = Manual input mode 8 = Simulation mode the previous Airoha code would allow quality >0 , which includes estimated positions. These wouldn't be passed through to the mesh due to other checks, but would affect the Airoha GPS_FIX_HOLD_TIME calculations. Changes the calculation to 1 >= quality <=5 .	2025-07-31 12:21:10 +10:00
Tom Fifield	8836be0f47	AG3335 GPS: Use NAVIC in India/Nepal, L1+L5 elsewhere. (#7413) ... As determined by @b8b8 , enabling NAVIC meant the more modern L5 GPS signal was not used (L1 GPS is always available). NAVIC, India's GNSS, probably provides the best coverage in India and the neighbouring region. However, outside of NAVIC's coverage area, L5 GPS is highly desirable. This patch amends the AG3335-family GPS configuration to enable L5 GPS coverage by default. If the Lora region is set to India or Nepal, NAVIC will be enabled instead.	2025-07-22 21:00:34 -05:00
Ben Meadors	cf574c71d8	Fix build	2025-07-18 09:24:34 -05:00
Tom Fifield	abe0a34fc0	Add additional Epoch check for time set (#7375) ... We have two perhapsSetRTC functions, which are called to set the time. The one with 3 parameters had a helpful check to reject an invalid time, by comparing the time from the source against when the firmware was compiled. The one with 2 parameters, which is called from the GPS lookForTime did not. As a result, certain GPS with bad time handling could set a time that was in the past. This patch adds the same epoch check code to the other perhapsSetRTC method. Fixes https://github.com/meshtastic/firmware/issues/7364	2025-07-18 05:49:19 -05:00
Chloe Bethel	1be4fc5ae9	GPS for STM32WL (#7297) ... * Enable GPS for Wio-E5 variant on Serial2 * Add ability to override GPS serial port using GPS_SERIAL_PORT, and make RAK2560 use it. * Don't try to send ATAK packets if ATAK is disabled, +4k flash	2025-07-14 05:12:26 -05:00
Ben Meadors	415dc4aa47	Try-fix: L76K spamming bad times can crash nodes (#7261) ... * Try-fix: Clear GPS buffer when we encounter a bad time in NMEA * Fix signed int warnings	2025-07-07 19:35:57 -05:00
Chloe Bethel	d494c23a88	Enable telemetry and I2C sensors on STM32WL (except accelerometers) (#7008) ... * Update platformio inis for stm32 platform and wio-e5 variant for enabling i2c * Don't reference timezone functions if MESHTASTIC_EXCLUDE_TZ is defined * Use custom pow_of_two in RadioInterface instead of floating-point pow() * First pass: enable sensors for STM32wL * Fix AirQualityTelemetryModule being created if the PM25AQI header is missing * Link in power sensor libraries * more ini tweaks * Add =1 to EXCLUDE defines, fix indentation. * Drop HAS_WIRE in ini, it's defined in architecture.h * Fix build when power sensor libraries are missing Make MAX sensor integration into Power.cpp optional based on its library header existing. Also make NullSensor expose a voltage and current sensor, because Power calls directly into these for INA sensors. This lets us remove all the deps for the STM32WL platform. * Change default I2C for RAK3172 to be I2C1, not I2C2 * Respect the laws of mathematics (oops)	2025-07-02 06:01:45 -05:00
Tom Fifield	6bba17d463	Add suppport for Quectel L80 (#6803) ... * Add suppport for Quectel L80 Another PMTK family chip, requires only a modification to the probe code. * Update support for L80 based on testing.	2025-05-15 19:26:41 +10:00
Ferdia McKeogh	947191a797	Add PA1010D GPS support (#6691)	2025-05-02 10:11:09 +08:00
todd-herbert	06ce6f3e8a	fix: remove redundant GPS code targeting Heltec T114 (#6497)	2025-04-10 09:48:40 +10:00
Ikko Eltociear Ashimine	1b1d4625aa	chore: update ubx.h (#6522) ... usefull -> useful	2025-04-08 14:04:33 -05:00
Thomas Göttgens	606abfc116	Fix several features of M1 and M2 (i know what the 7 is now ...) (#6507) ... * Fix several features of M1 and M2 (i know what the 7 is now ...) * 'THe' should be 'The'. Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * remove floating definition --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Ben Meadors <benmmeadors@gmail.com>	2025-04-07 05:46:22 -05:00
Chris LaFlash	56eb0c08b2	Add support for Quectel-L96, a MT3333 module (#6498)	2025-04-06 11:49:01 +08:00
Thomas Göttgens	3148e7277d	Fix a couple of warnings (#6445) ... * Fix a couple of warnings * fix build error --------- Co-authored-by: Ben Meadors <benmmeadors@gmail.com>	2025-03-29 08:14:24 -05:00
Tom Fifield	cff93adb5e	[WIP] LS20031 setup support (#5737) ... LS20031 is a MTK3339-based chip. Therefore, it should share some heritage with other MTK3333 or MTK3339 chips. Re-use the L76B commands for setup.	2025-03-21 05:58:52 -05:00
Thomas Göttgens	1640fb105d	new device: Lilygo T-Eth-Elite (#6321)	2025-03-15 14:15:35 +01:00
Tom Fifield	2391982c1d	Only call GPS Probe commands once per family (#6114) ... In the GPS probe code we write commands on the serial line and determine which GPS we have based on the result. GPS units in the same family sometimes use the same command, but return different results (eg AG3335 and AG3332 both use $PAIR021*39). Currently we run the command once per GPS. Instead we should run each command only once per family, record the result, and select the GNSS MODEL based on the result, which is what this patch does. Before the change, we put 12 commands on the serial bus. Now we only put 6. This should markedly improve the speed and reliability of GPS detection. Fixes https://github.com/meshtastic/firmware/issues/5193 Co-authored-by: Ben Meadors <benmmeadors@gmail.com>	2025-03-04 09:47:06 -06:00
Tom Fifield	fe1ced7480	GPS Factory Reset no longer needed. (#6116) ... In 2020 there was a bad batch of tbeams whose ubloxen went a little loopy. We factory reset them to bring them sane again. It's now 2025, the problem with tbeam is long fixed, and this is not necessary for any other devices we're aware of. Removing the function to make our code more maintainable. There is an associated protobuf entry did_gps_reset that we might be able to re-purpose for something else, or remove in 3.0.	2025-02-21 16:53:46 -06:00
Tom Fifield	ec0eafedab	Move variant-specific lines back to variant (#6044) ... Last release a change introduced different branching functions in gps.cpp based on the model of a device. This makes the code less readable and introduces the potential for bugs. This patch creates a new variable, GPS_PROBETRIES that can be set in variant.h of devices that will control how many times we will probe for GPS presence. It sets up the T1000-E to use this variable and cleans the code in gps.c	2025-02-20 07:48:37 -06:00
dylanli	4e8c4f0d55	T1000-E hardware updates and GPS positioning accuracy optimisation (#6003) ... * T1000-E button setting update * T1000-E GNSS lock error fix * T1000-E GNSS improve detection success --------- Co-authored-by: WayenWeng <jinyuan.weng@seeed.cc>	2025-02-07 10:02:56 +02:00
Bernd Giesecke	2e44de262e	Add GPS capability to RAK2560 (RAKwireless WisMesh Hub) (#5797) ... * Add GPS to RAK2560 * Add GPS to RAK2560	2025-01-09 19:20:38 -06:00
Alex Markley	9afadde2f4	Add support for LS20031 GPS module. (#5718) ... Hardware documentation referenced: - https://cdn.sparkfun.com/datasheets/GPS/LS20030~3_datasheet_v1.3.pdf - https://cdn-shop.adafruit.com/datasheets/PMTK%20command%20packet-Complete-C39-A01.pdf	2025-01-04 07:00:39 +08:00
Ben Meadors	b5777beb7d	Warnings and log cleanup (#5472) ... * Don't log if keyboard not found * Signed comparison issue	2024-11-28 11:20:06 -06:00
Christopher Hoover	b00c05012d	GPS.h cleanups round 3. (#5447) ... * GPS.h cleanups round 3. No effective behavior change. Protected members can be private so make it so. (Supporting subclasses needs a lot more work.) Moves uBloxGnssModelInfo into file scope. Moves uBloxProtocolVersion into uBloxGnssModelInfo. Moves baud rate arrays into file scope. Removes unused/ unimplemented powerStateToString. Signed-off-by: Christopher Hoover <ch@murgatroid.com> * Trunk Format. --------- Signed-off-by: Christopher Hoover <ch@murgatroid.com> Co-authored-by: Tom Fifield <tom@tomfifield.net>	2024-11-27 18:56:25 +08:00
Ben Meadors	474f9b5bfb	Clean up some inline functions (#5454)	2024-11-26 14:00:10 -06:00
Christopher Hoover	0048e3cdcb	A second round of cleanup on GPS.h. (#5433) ... * Move yet more stuff out of GPS.h and into file scope. * Protect code macros from eating semicolons. * Remove unused (and unimplemented) getDOPString. * clang-format with project style file on affected files. Signed-off-by: Christopher Hoover <ch@murgatroid.com>	2024-11-25 05:32:04 -06:00
Christopher Hoover	fadcbd597f	Cleans up visibility in GPS.h (#5426) ... Signed-off-by: Christopher Hoover <ch@murgatroid.com>	2024-11-23 06:10:09 -06:00