Skip to content

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
merged 37 commits into from
Sep 27, 2023

Conversation

nseidle
Copy link
Member

@nseidle nseidle commented Sep 27, 2023

RTK-Beta-Firmware-Update
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:

github-actions bot and others added 30 commits September 19, 2023 16:48
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
Remove state STATE_KEYS_PROVISION_WIFI_TIMEOUT
@nseidle nseidle merged commit d7f3f96 into main Sep 27, 2023
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.

2 participants