focal-source |
focal-amd64 |
focal-armhf |
focal-arm64 |
dev |
doc |
|
---|---|---|---|---|---|---|
witmotion_ros
module implements a ROS 1 wrapper for Witmotion IMU driver library. It reads the data from the family of TTL-compatible inertial pose estimation units (IMUs) manufactured by WitMotion Shenzhen Co.,Ltd publishing the information in ROS-native way using sensor_msgs
and std_msgs
message definition packages. The module is focused on read-only access, so calibration and bias regulation functions are implemented in the underlying library. Port access model is implemented in monopolistic way acccording to UNIX specification, so only one instance of the module can be executed for the dedicated virtual device.
The module is developed according to the specifications released by Witmotion, the presented snapshot has download date is 23.02.2022. The official website https://wiki.wit-motion.com is not always accessible, so the PDF snapshots are placed under IPFS web directory.
The ROS2 compatible implementation of the driver is WIP under ros2
branch. The initial migration made by @fllay
(pull request #12).
The contributors are strongly encouraged to mark the names of their ROS2-related issues and pull requests with [ROS2]
prefix.
The package requires QtSerialPort development package from Qt 5.2+
sudo apt-get install libqt5serialport5-dev
cd catkin_ws
git clone --recursive https://github.com/ElettraSciComp/witmotion_IMU_ros.git src/witmotion_ros
catkin_make
If compilation fails, first check the directory src/witmotion_ros/witmotion-uart-qt
. If it is empty, the recursive clone failed, and you should manually clone the underlying library from the repository https://github.com/ElettraSciComp/witmotion_IMU_QT into this directory. IMPORTANT! Please beware of the directory name, the CMakeLists
file refers exactly to the name witmotion-uart-qt
specified in the target import section.
roslaunch witmotion_ros witmotion.launch
Configuration of the node is done by default via the configuration YAML file config.yml
. But it also can be done using roslaunch
XML syntax under the node's internal namespace. The single value measurements, like pressure and temperature, are enabled for the linear calibration because there can be differences in decoding coefficients between the sensors (proven for WT31N and JY901B sensors).
port
- the virtual kernel device name for a port, ttyUSB0
by defaultbaud_rate
- port rate value to be used by the library for opening the port, 9600 baud by defaultpolling_interval
- the sensor polling interval in milliseconds. If this parameter is omitted, the default value is set up by the library (50 ms).timeout_ms
- the sensor timeout period in milliseconds. If no data is received from the sensor after this period, then an error is raised and the node terminates. If this parameter is omitted, a default value of 3 times the polling interval is used. If this parameter is zero, the timeout check is disabled.restart_service_name
- the service name used to restart the sensor connection after an error.imu_publisher:
topic_name
- the topic name for IMU data publisher, imu
in the node's namespace by defaultframe_id
- IMU message header frame IDuse_native_orientation
- instructs the node to use the native quaternion orientation measurement from the sensor instead of synthesized from Euler angles. NOTE: if this setting is enabled bu the sensor does not produce orientation in the quaternion format, the IMU message will never be published!measurements
- every measurement in IMU message data pack can be enabled or disabled. If the measurement is disabled, the corresponding covariance matrix is set to begin from -1
as it is described in the message definition.
acceleration
enabled
covariance
- row-major matrix 3x3, all zeros for unknown covariationangular_velocity
enabled
covariance
- row-major matrix 3x3, all zeros for unknown covariationorientation
enabled
covariance
- row-major matrix 3x3, all zeros for unknown covariationtemperature_publisher
enabled
- enable or disable temperature measurement extractiontopic_name
- the topic name for publishing temperature dataframe_id
- message header frame IDfrom_message
- the message type string to determine from which type of Witmotion measurement message the temperature data should be extracted (please refer to the original documentation for detailed description). The possible values are: acceleration
, angular_vel
, orientation
or magnetometer
.variance
- the constant variance, if applicable, otherwise 0coefficient
- linear calibration multiplier, 1.0 by defaultaddition
- linear calibration addendum, 0 by defaultmagnetometer_publisher
enabled
- enable or disable magnetometer measurement extractiontopic_name
- the topic name for publishing the dataframe_id
- message header frame IDcoefficient
- linear calibration multiplier, 1.0 by defaultaddition
- linear calibration addendum, 0 by defaultcovariance
- row-major matrix 3x3, all zeros for unknown covariationbarometer_publisher
enabled
- enable or disable barometer measurement extractiontopic_name
- the topic name for publishing the dataframe_id
- message header frame IDcoefficient
- linear calibration multiplier, 1.0 by defaultaddition
- linear calibration addendum, 0 by defaultvariance
- the constant variance, if applicable, otherwise 0altimeter_publisher
enabled
- enable or disable altitude measurement extractiontopic_name
- the topic name for publishing the datacoefficient
- linear calibration multiplier, 1.0 by defaultaddition
- linear calibration addendum, 0 by defaultorientation_publisher
enabled
- enable or disable orientation measurement extractiontopic_name
- the topic name for publishing the datagps_publisher
enabled
- enables/disables all GPS receiver measurements extractionnavsat_fix_frame_id
- frame ID for GPS fixed position publishernavsat_fix_topic_name
- topic name for GPS fixed position publishernavsat_altitude_topic_name
- topic name for GPS altitude publishernavsat_satellites_topic_name
- topic name for GPS active satellites number publishernavsat_variance_topic_name
- topic name for GPS diagonal variance publisherground_speed_topic_name
- topic name for GPS ground speed publisherrtc_publisher
enabled
- enables/disables realtime clock information decodertopic_name
- topic name for realtime clock publisherpresync
- instructs the node to perform an attempt to pre-synchronize sensor's internal realtime clock