Skip to content

Fix webconfig when PointPerfect is enabled #557

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 308 commits into from
Feb 20, 2025
Merged

Fix webconfig when PointPerfect is enabled #557

merged 308 commits into from
Feb 20, 2025

Conversation

nseidle
Copy link
Member

@nseidle nseidle commented Feb 20, 2025

Changes in this release:

nseidle and others added 30 commits December 27, 2024 16:43
This test was used in early days of ZED logging before the SEMP was in place. No longer relevant or needed.
When a consumer requests NETCONSUMER_WIFI_STA, the bit field looks different from NETCONSUMER_WIFI_AP_STA, at which point the network is shut down (bad). The solution is to remove NETCONSUMER_WIFI_AP_STA and just use a combination of bits _AP and _STA.
PaulZC and others added 29 commits February 17, 2025 11:08
E.g. on the mosaic, the Rover settings must be reapplied when settings.enablePointPerfectCorrections becomes true... Otherwise the required RTCM messages are never enabled...
@nseidle nseidle merged commit 6fd4a20 into main Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants