-
Notifications
You must be signed in to change notification settings - Fork 53
v3.9 - Automatically prioritize RTCM over L-Band corrections #682
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
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The left justified timestamp is displayed approximately once per second. Data is delivered by the ZED to the ESP32 a byte at a time. The "Tx RTCM" messages are printed after 5 milliesconds of idle time, trying to display transactions between the ZED and the ESP32. The "NTRIP Server transmitted" messages are printed after 100 milliseconds of idle time, trying to display network packets that might be sent to the NTRIP server. In the old behavior, several "Tx RTCM" messages were displayed and the value in the last message equaled the value in the "NTRIP Server transmitted" message. This was confusing because the byte count grew with each "TX RTCM" message. This commit adds the zedBytesSent value to count the bytes sent by the ZED to the ESP32. The zedBytesSent value is displayed after 5 milliseconds of idle time and then reset to zero. Totaling the "Tx RTCM" values between the "NTRIP Server transmitted" messages equals the value in the "NTRIP Server transmitted" message. Another way to say this is: Totaling the bytes output by the ZED ("Tx RTCM") separated by 5 milliseconds of idle time equals the number of bytes ("NTRIP Server transmitted") separated by 100 milliseconds.
Testing shows that the ZED gets confused (positional accuracy bounces around a lot) if both PMP and RTCM are fed into the ZED.
menuSystem: Fix typo in debug menu item 26
NTRIP Server: Add zedBytesSent value
menuSystem: Fix Wifi IP Address entry in network menu
Add Esp32_Timer.h to display the watchdog timer registers
States: Eliminate infinite loop in STATE_KEYS_WIFI_STARTED
States: Shutdown WiFi in STATE_KEYS_WIFI_TIMEOUT
Turn off L-Band if RTCM is received
States: Turn off WiFi before entering STATE_KEYS_WIFI_TIMEOUT
Print state as currentState --> newState, or *currentState w/timestamp
…Fun_RTK_Firmware into release_candidate
Remove state STATE_KEYS_PROVISION_WIFI_TIMEOUT
States: Stop WiFi on exit paths from key provisioning
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: If you are running firmware v3.x or greater, you can load the latest firmware or release candidate over the air. If you are using older firmware (2.x or lower) you will need to load v3.x firmware using a USB connection. We have created a Windows GUI to ease this process. Please see Updating Firmware from GUI for a step by step process.
Changes in this release: