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
Originally posted by pat-2010 October 27, 2024
Troubleshooting a different problem I saw the following behavior. Is it expected?
Configuration: Raspberry Pi 5 running pypgsclient 1.4.22. Python 3.11.42. GPS receiver not applicable, since I see this behavior without turning on my GPS receiver. EDIT: noticed that my pygpsclient version was out of date. Updated to 1.4.24 and repeated the test with no change.
When I stop the NTRIP client using the stop button on the bottom of the NTRIP client connection, the status at the bottom says "Disconnected". Using Wireshark I can see the NTRIP message from the server and the ACK from my computer. When I disconnect, my computer continues to send ACKs and the server thinks I'm still connected. It's not until I exit pygpsclient that I get a different message from my computer that actually disconnects from the NTRIP server.
The text was updated successfully, but these errors were encountered:
Discussed in #97
Originally posted by pat-2010 October 27, 2024
Troubleshooting a different problem I saw the following behavior. Is it expected?
Configuration: Raspberry Pi 5 running pypgsclient 1.4.22. Python 3.11.42. GPS receiver not applicable, since I see this behavior without turning on my GPS receiver. EDIT: noticed that my pygpsclient version was out of date. Updated to 1.4.24 and repeated the test with no change.
When I stop the NTRIP client using the stop button on the bottom of the NTRIP client connection, the status at the bottom says "Disconnected". Using Wireshark I can see the NTRIP message from the server and the ACK from my computer. When I disconnect, my computer continues to send ACKs and the server thinks I'm still connected. It's not until I exit pygpsclient that I get a different message from my computer that actually disconnects from the NTRIP server.
The text was updated successfully, but these errors were encountered: