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

3DM-GQ7 RTCM / NMEA configuration for external data #334

Closed
mschratter opened this issue May 23, 2024 · 2 comments
Closed

3DM-GQ7 RTCM / NMEA configuration for external data #334

mschratter opened this issue May 23, 2024 · 2 comments
Labels
bug Something isn't working New This issue is new, and should not be marked as stale

Comments

@mschratter
Copy link

I want to use an external ntrip server for the rtcm data. Previously I used another GNSS receiver with your ntrip_client to get the rtcm_msgs via the nmea_msgs message.
If I read the documentation correctly, one way to get the rtcm data to the 3DM-GQ7 is to use the aux port via a second cable. Is this correct?

If so, how do I configure the 3DM-GQ7 in the yaml to receive the nema message via ROS and how do I configure the ntrip_client node to send the rtcm data to the 3DM-GQ7 via the aux port, or does the microstrain_inertial_driver send the rtcm data to the 3DM-GQ7?

Expected behavior
Getting rtcm data on the 3DM-GQ7

Environment (please complete the following information):

  • OS: Ubuntu
  • Architecture: x86_64
  • ROS Version: humble
  • Version: 4.3.0
  • Sensor(s): 3DM-GQ7
@mschratter mschratter added the bug Something isn't working label May 23, 2024
@github-actions github-actions bot added the New This issue is new, and should not be marked as stale label May 23, 2024
@Aposhian
Copy link

Aposhian commented May 24, 2024

If you set the ROS param ntrip_interface_enable: True then it will subscribe to RTCM messages that the ntrip_client publishes, and write them to the aux port, as well as read NMEA sentences from the aux port and publish them for the ntrip_client.

https://github.com/LORD-MicroStrain/microstrain_inertial_driver_common/blob/80378f949792743bdc15de1c549e7ff28d00004e/config/params.yml#L165-L168

@robbiefish
Copy link

Thanks for answering this @Aposhian. I am closing this issue.

Additionally, for a simple example of using microstrain_inertial_driver with the ntrip_client, check out microstrain_inertial_localization and it's wiki page, specifically the NTRIP Settings section

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working New This issue is new, and should not be marked as stale
Projects
None yet
Development

No branches or pull requests

3 participants