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

No imu topic when SPAN is disabled #26

Open
Timple opened this issue Aug 16, 2021 · 6 comments
Open

No imu topic when SPAN is disabled #26

Timple opened this issue Aug 16, 2021 · 6 comments
Assignees
Labels
enhancement New feature or request

Comments

@Timple
Copy link

Timple commented Aug 16, 2021

Describe the bug
No imu topic when SPAN is disabled.

To Reproduce
Steps to reproduce the behavior:

  1. Disable span
  2. Look for imu topic

Expected behavior
Imu is still present and active. So could be outputted to ROS.

Screenshots

Environment (please complete the following information):

  • ROS1 Noetic

Additional context
SPAN is not working for us, but for roll and pitch information we would like to use the imu present in the Novatel. Can this information still be made available?

@Timple Timple added the bug Something isn't working label Aug 16, 2021
@MCFurry
Copy link

MCFurry commented Aug 17, 2021

To add to @Timple we are using a SMART7-S receiver in this case (with imu and SPAN integrated).
When disabling SPAN by executing INSCOMMAND DISABLE, the imu topic is not published anymore.
Although the rawimu* logs should still be present according to documentation, quote:

Use this command to enable or disable INS. When INS is disabled, no INS position, velocity or attitude is output
(however IMU data is still available).

@edwardribbit
Copy link

This may be a feature request, the gps/imu topic is actually the corrected imu which relies on SPAN alignment. Is there really a raw imu topic?

@MCFurry
Copy link

MCFurry commented Aug 18, 2021

Then maybe it is indeed a feature request.
gps/imu is the only imu topic available but we'd really like a raw imu topic as an option!

@novatel-applications-engineering
Copy link
Contributor

Hi @MCFurry and @edwardribbit.

Thank you for bringing this request to our attention. Can you confirm the request is for:

  • Oem7 RAWIMU message output to its own topic (vs. Oem7Raw)

or

  • ROS standard imu/data_raw populated per REP 145, based on RAWIMU

Please send those details and the feature request to support.novatel@hexagon.com. We can then track the request with our ROS development team and keep you updated on the progress.

Best regards,
NovAtel Application Engineering

@Timple
Copy link
Author

Timple commented Aug 20, 2021

For us that would be:

ROS standard imu/data_raw populated per REP 145, based on RAWIMU

Or even better, imu/data because I assume the roll and pitch are known?
Please use the ENU convention as per ROS default.

Without adhering to REP145 the data cannot easily be processed by other ROS nodes.

@novatel-applications-engineering
Copy link
Contributor

Thank you for the clarification! Right now it is not available, but I have put in new feature request to have this added. Users who want this added, please thumbs-up this Issue to help us weigh the level of interest in the item.

Best regards,
NovAtel Application Engineering

@novatel-applications-engineering novatel-applications-engineering added enhancement New feature or request and removed bug Something isn't working labels Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants