View Categories

3) FAQ​

2 min read

1) Why i am facing disconnetion after some minutes?​ #

Please make sure you assign a static IP to your computer interface (example: 192.168.7.100).

  • Go to the network settings of your computer where the IMU is connected.
  • Select the settings of the Ethernet USB interface.
  • Select the IPv4 tab in the settings.
  • Assign a static IP address. If you are using the default IP of the sensor, set the IP of the PC to 192.168.7.200.
  • Disconnect and reconnect your sensor from the USB port.
  • Done!

2) Why the device is not publishing any topics?​ #

(a) Possible Problem 1:​ #

To ensure optimal performance, please ensure that your main computer is configured to utilize FastDDS middleware. If you find that CycloneDDS is currently in use, you’ll need to switch the configuration from the device’s web-based GUI to CycloneDDS. Additionally, in cases where your computer employs multiple network interfaces, it’s essential to establish a specific configuration for CycloneDDS and explicitly designate the IP address of the active network. This ensures seamless operation and maximizes efficiency. Please follow this steps:

https://olive-robotics.com/docs2/9-data-distribution-service-dds/

(b) Possible Problem 2:​ #

Make sure the component ROS 2 domain ID is same with your host computer’s domain ID.

(c) Possible Problem 3:​ #

Sometimes you have to restart your ROS 2 daemon.

ros2 daemon stop
ros2 daemon start

(d) Possible Problem 4:​ #

Sometimes your ROS 2 cli terminal is not showing the topics, but in rqt you will see the topics and this is a bug in ROS 2 cli terminal. Double check with rqt, topic monitor plugin.

rqt

3) IMU AHRS data is freezing when my robot spins at a constant low speed (around 0.1 rad/s) #


The automatic background calibration detects it as stationary and suppresses the gyro output.

We recommend that if you need the raw sensor data without this effect, you should refer to the filtered_IMU stream instead of filtered_AHRS.

This gives you direct access to the accelerometer and gyroscope data without the aggressive bias correction.

Additionally, you can adjust the yaw sensitivity in filtered_IMU using the fusion_gain parameter:

A higher fusion_gain makes the system more responsive to motion.

A lower fusion_gain makes the output more stable but slower to respond.

Was this information useful?