You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Started with launch command "roslaunch livox_ros_driver2 msg_MID360.launch".
Usually, ROS Topic is published without any problem,
However, about once in a hundred times,
error occurs and ROS Topic of point cloud or imu is not published.
If the error occurs, launch livox_ros_driver2 msg_MID360.launch again about 1 minute after launch is launched,
ROS Topic is successfully published.
If I do roslaunch livox_ros_driver2 msg_MID360.launch again immediately, the output is not normal.
I have not changed the power supply or Ethernet connection conditions.
I wait at least one minute after the power supply is turned on before starting up.
Has there been any report of such a problem with init fail at startup?
The text was updated successfully, but these errors were encountered:
Started with launch command "roslaunch livox_ros_driver2 msg_MID360.launch".
Usually, ROS Topic is published without any problem,
However, about once in a hundred times,
error occurs and ROS Topic of point cloud or imu is not published.
If the error occurs, launch livox_ros_driver2 msg_MID360.launch again about 1 minute after launch is launched,
ROS Topic is successfully published.
If I do roslaunch livox_ros_driver2 msg_MID360.launch again immediately, the output is not normal.
I have not changed the power supply or Ethernet connection conditions.
I wait at least one minute after the power supply is turned on before starting up.
Has there been any report of such a problem with init fail at startup?
The text was updated successfully, but these errors were encountered: