-
Notifications
You must be signed in to change notification settings - Fork 54
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
Issue of the Ntrip client #35
Comments
I do not recognize the logs you see on your screen. Did you add or remove log messages? Could you provide logs from a run with normal ROS logs? Aditionally running with It looks like you are logging a successful response from an NTRIP 1.0 server. If the client received that response, it should consider itself connected, but I do not see a log saying that, but as mentioned before, I do not see any of the logs I would expect to see. My initial thought from the logs you provided would be that it is constantly reconnecting. This is behavior I often see when connecting to an NTRIP caster that needs NMEA sentences without sending NMEA sentences. |
I have the same problem with the Sapos NTRIP Caster and the ROS2 client. I suspect the NTRIP Caster requires NMEA GGA strings to allow data pull. |
Not sure if you have found a solution to the issue, but yes, for SAPOS you do need to send nmea sentences to the server i order to get a response. Generally, you get those from your GPS-module/driver or you could write a node that subscribes to the NavSatFix ( e.g. /fix) topic and computes an nmea sentence from Lat/Lon. |
Hi everyone:
Recently I got the Ublox F9P and I would like to get RTK support, and I ran the package from here: https://github.com/LORD-MicroStrain/ntrip_client when I ran: roslaunch ntrip_client ntrip_client.launch I encountered the problem shown below:
Seems to be I did not receive any RTCM message. I live in Germany and used SAPOS service. For the connection I used Jetson Nano and communicate with UART.
I will appreciate if you can give me some good ideas. Thx!
The text was updated successfully, but these errors were encountered: