Skip to content
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

Open
yulan0215 opened this issue Mar 15, 2023 · 4 comments
Open

Issue of the Ntrip client #35

yulan0215 opened this issue Mar 15, 2023 · 4 comments
Assignees

Comments

@yulan0215
Copy link

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:

5d457784464a40199c0ffe207b12296

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!

@robbiefish
Copy link
Contributor

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 debug:=true would provide me even more insight, so that would be appreciated.

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.

@robbiefish robbiefish self-assigned this Mar 17, 2023
@nzantopp
Copy link

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.

@yulan0215
Copy link
Author

yulan0215 commented May 31, 2023

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 debug:=true would provide me even more insight, so that would be appreciated.

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.

Screenshot from 2023-05-31 13-37-43
This was the debug output... I did not know how to solve this problem, is it the problem from GGA strings or any other problem?
Besides, do you know how to send the NMEA sentence? Thx

@tschuette22
Copy link

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.
The launch file of the ntrip_client has an option to remap your nmea topic to the one the client needs.

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

No branches or pull requests

4 participants