Qing Joe Wong

Hi, thanks for the reply. Regarding the first question, if I do not have any input from RTKLIB, what should I put in the GNSS velocity source? I tried using...

Yes, for the gnss input this is what I used: velocity_source_type: 3, velocity_source_topic: /odometry_twist llh_source_type: 2, llh_source_topic: /gps/fix I checked that these topics are being subsrcibed. However running eagleye rt,...

I see, thank you. My issue is that I'm still trying to explore more on RTKLIB so that it can be used in this case. In the meantime, I suppose...

Unfortunately with the above set up, it is not working. The status is always showing this.

Hi, yes I tried using the above config you mentioned, and my nmea_sentence topic does have GNRMC and GNGGA, but the result is the same. This is my rosbag. [rosbag](https://drive.google.com/file/d/1VgO-dNyhoGqJ_f3QmyBn_AM2HCMARxbx/view?usp=share_link)...

Yes I'm using main-ros1 branch. Thanks for helping me checking it out.

Ohh I see, so my issue is at the imu rate and moving judgement threshold, which are also responsible for the process died in gnss_converter node? Is there any problem...

Thanks. I have changed my imu publishing rate to be 50 hz and followed the same configurations like the one you set above. However I realised there might be some...

I see, I will try that as well. However I realised it might be the issue of the nmea navsat driver that I'm using, it occasionally received an invalid checksum...

Yes, I have verifed that the issue is with my nmea sentence, which is not supposed to be just 2 characters otherwise it would cause the error. I'm still trying...