A ROS interface to control Gremsy gimbals. Based on the gSDK interface and the MavLink protocol.

Disclaimer: This software package is not officially developed by or related to Gremsy.

This package includes a ROS Node which warps the gSDK for the Gremsy Gimbals which are mainly used for physical image stabilization.

The gimbal is connected via UART with a Linux host device running this node. Devices such as the Raspberry Pi feature a build-in UART interface others like most PCs or Laptops need a cheap USB Adapter. The used serial device, as well as many other gimbal specific parameters, can be configured in the config.yaml file. The node publishes the gimbals encoder positions, imu measurements, and the camera mount orientation.

Run the following commands to clone this repository and update all submodules (needed for the external gSDK repository).

git clone https://github.com/Flova/ros_gremsy
cd ros_gremsy
git submodule init
git submodule update

Now you need to install all dependencies using rosdep. To execute this command make sure that the correct catkin workspace is sourced and the repository you just cloned is (linked) inside the src directory.

rosdep install --from-paths . --ignore-src -r -y

After installing the dependencies you should be able to build the package using:

catkin build ros_gremsy

Type the following command to run the node. Make sure that the gimbal is connected properly, the Linux permissions regarding the serial interface are correct (this depends on your distro) and the config features the correct device and baudrate (default setting should be fine as far as I know).

roslaunch ros_gremsy gimbal.launch

The node publishes:

• /ros_gremsy/imu/data with a sensor_msgs/Imu message containing the raw gyro and accelerometer values.
• /ros_gremsy/encoder with a geometry_msgs/Vector3Stamped message containing the encode values around the x (roll), y (pitch) and z (yaw) axis.
• /ros_gremsy/mount_orientation_global_yaw with a geometry_msgs/Quaternion message representing the camera mount orientation in the global frame. This measurement is imprecise in the yaw axis because of the gyro drift.
• /ros_gremsy/mount_orientation_local_yaw with a geometry_msgs/Quaternion message representing the camera mount orientation in the global frame except for the yaw axis which is provided relative to the gimbals mount on the vehicle or robot.

The node receives:

• /ros_gremsy/goals expects a geometry_msgs/Vector3Stamped message containing the desired angles for each axis. The frame for each axis (local or global), as well as the stabilization mode, can be configured in the config.yaml file.

• Better dynamic reconfiguration
• Better handling of gimbal timestamps