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

Nothing published on rostopics #91

Closed
Smiffe opened this issue Jun 16, 2020 · 2 comments
Closed

Nothing published on rostopics #91

Smiffe opened this issue Jun 16, 2020 · 2 comments

Comments

@Smiffe
Copy link
Contributor

Smiffe commented Jun 16, 2020

Hi!
I'm using Flexpak6 device and I noticed that's not supporting "RAWIMUX" command. Anyway ROS starting without any errors, warnings or infos. There are available rostopics, but nothing is published. I checked serial communication and all frames are going trough.

Is that missing command responsible for this situation?

@pjreed
Copy link
Contributor

pjreed commented Jun 29, 2020

Just to be sure, do you have a SPAN device? Not all FlexPak6 enclosures have SPAN support, and if you don't, then it won't produce any IMU-related messages.

If you connect directly to it with a serial terminal (I like CuteCom ), if you type something like log rawimuxa once, does it print anything?

@Smiffe
Copy link
Contributor Author

Smiffe commented Jul 7, 2020

Yeah, it's not SPAN device so it doesn't support "RAWIMUX" command (it prints back info about that after sending a command).

The main problem was empty rostopics, but after some tries i fixed it. The first problem was GPS rate lower than 20Hz described in for example #6 or #44 issue and the second was with antenna. Testing device was in garage and it wasn't getting fix. I was getting "insufficient data rate" error even with all frames visible on serial port so I thought it's ros/driver problem, not device problem.

It would be easier if driver could parse messages with no fix inside and I could see something when doing "rostopic echo" for example "no fix" when tracking 0 satellites. Anyway it's not any bug, driver works fine, so I'm closing this Issue.

@Smiffe Smiffe closed this as completed Jul 7, 2020
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

2 participants