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
I would like to use Eagleye in can_less mode with stand-alone positioning.
I am using simpleRTK2B (u-blox ZED-F9P ) and IMU (TAG300N-100).
(1)Does Eagleye_rt need both nmea_sentence and rtklib_msgs inputs?
It is difficult to input nmea_sentence and rtklib_msgs to Eagleye_rt at the same time because UART2 is not available on the F9P board we are using.
(2) I am inputting GNSS and IMU Topic with nmea_sentence specified, but /velocity is not published. What could be the cause of this problem?
(3) I am using the ROSBAG (eagleye_sample_20200127.bag) to check if it localization in CANLES mode, but it does not.
What could be the cause of this problem?
(I have specified rtklib_msgs as the GNSS to be used.)
The text was updated successfully, but these errors were encountered:
Thank you for your response.
(1), (2) I will verify the operation by setting use_gnss_mode to NMEA.
If it does not work, I will extract the ROSBAG data.
(3) Why does the CAN-less mode not work?
Are there any limitations, such as requiring GNSS: Ublox F9P with RTK for the CAN-less mode?
Thank you for your great work.
I would like to use Eagleye in can_less mode with stand-alone positioning.
I am using simpleRTK2B (u-blox ZED-F9P ) and IMU (TAG300N-100).
(1)Does Eagleye_rt need both nmea_sentence and rtklib_msgs inputs?
It is difficult to input nmea_sentence and rtklib_msgs to Eagleye_rt at the same time because UART2 is not available on the F9P board we are using.
(2) I am inputting GNSS and IMU Topic with nmea_sentence specified, but /velocity is not published. What could be the cause of this problem?
(3) I am using the ROSBAG (eagleye_sample_20200127.bag) to check if it localization in CANLES mode, but it does not.
What could be the cause of this problem?
(I have specified rtklib_msgs as the GNSS to be used.)
The text was updated successfully, but these errors were encountered: