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

This pack can cause changes to firmware that invluences the baudrate of your sensor #223

Open
BartVanderHaagen opened this issue Jul 14, 2023 · 0 comments

Comments

@BartVanderHaagen
Copy link

Describe the bug
A year ago i had the same isue with a ublox m6 and ROS1 melodic. Than i thought it was a cheap replica or something and i did not gave it time. but now The ROS2 version with my brand-new neo m8u module has also become "unusable".

description of what the bug is:
the launch file forces to explicitly set the baudrate specified in the yaml.

If this not success it trows an error: cant configure baudrate and the process dies. if the condition is satified. the pack runs, and the topics echo ...great!

really great ? ..well
after this the sensor is acting very wired and the output (terminal or serial monitor or ublox terminal) is unreadable in any baudrate.

Next is to try and flash the firmware fresh to the modulle. this did not work sofar. (ublox center 1 and 2 installed on windows 11)

I had exacly the same problems with the neo m6 and the neo m8u (sparkfun)

**Desktop

  • OS: jetson nx [ Ubuntu 20.04 ]
  • ROS Version [ ROS2 foxy ]

tried : rs232 to usb (works better)
tried : uart 1 RXTX /dev/ttyTHS0

windows 11 ucenter 1 and 2

Additional context
plz help to restore sensors and help adjust force baud settings.

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

1 participant