We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
E (7021) w5500.mac: emac_w5500_init(823): reset w5500 failed E (7021) esp_eth: esp_eth_driver_install(228): init mac failed [ 7027][E][ETH.cpp:659] beginSPI(): SPI Ethernet driver install failed: 263 Rover Accuracy (m): 429496.719, SIV: 0 GNSS State: No Fix System time set to: Wednesday, June 19 2024 17:50:40 Rover Accuracy (m): 429496.719, SIV: 0 GNSS State: No Fix Rover Accuracy (m): 429496.719, SIV: 0 GNSS State: No Fix Rover Accuracy (m): 429496.719, SIV: 0 GNSS State: No Fix
To replicate, factory reset a device and the rover accuracy will be huge.
This is likely due to GNSS reset. Should we just not display rover accuracy until we get a fix?
The text was updated successfully, but these errors were encountered:
We have no control over the 429496.719. That's just the default hAcc while the module gets a fix. Suspiciously close to 0xFFFFFFFF * 0.1mm!
We can easily cap this at ">30m" like we do on the display.
Sorry, something went wrong.
Fixed in #376
Merge pull request #376 from sparkfun/Fix_#356
0f94773
Fix #356
a4d69ef
PaulZC
No branches or pull requests
To replicate, factory reset a device and the rover accuracy will be huge.
This is likely due to GNSS reset. Should we just not display rover accuracy until we get a fix?
The text was updated successfully, but these errors were encountered: