You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When in Rover mode, it should not be possible to start the connections to the NTRIP Servers. But I see the server being started when in Rover mode - after having been in Base.
Provide WiFi credentials.
Provide server details for one (or two) NTRIP servers.
Start the RTK in Temporary Base mode.
Allow the survey-in to complete. Firmware begins sending RTCM data to the servers.
Change to Rover mode.
The NTRIP server connections should be stopped, but I see them being periodically restarted - leading to WiFi badness when going into WiFi Config mode.
The text was updated successfully, but these errors were encountered:
PaulZC
changed the title
NTRIP Server perpetually restarted when going from Base to Rover
NTRIP Server restarted after going from Base to Rover
Jun 7, 2024
After a lot of digging and head-scratching, I eventually traced this to ntripServerRestart being called - instead of ntripServerStop. I believe calling ntripServerStop is the correct thing to do. ntripServerRestart actually turns the server on if the connection limit has not been reached... The same is true for ntripClientStop vs. ntripClientRestart.
@nseidle@LeeLeahy2 : please review this commit and let me know if you agree with the solution : af73bf3
When in Rover mode, it should not be possible to start the connections to the NTRIP Servers. But I see the server being started when in Rover mode - after having been in Base.
Provide WiFi credentials.
Provide server details for one (or two) NTRIP servers.
Start the RTK in Temporary Base mode.
Allow the survey-in to complete. Firmware begins sending RTCM data to the servers.
Change to Rover mode.
The NTRIP server connections should be stopped, but I see them being periodically restarted - leading to WiFi badness when going into WiFi Config mode.
The text was updated successfully, but these errors were encountered: