[Clearpath Husky A200] Integration of sensors such as Zed2i, Phidget IMU and Bpearl Lidar

Hi,

we’re looking to integrate several sensors with our Husky [S/N: a200_0930] running on a intel PC with ROS2 Humble and 22.04 Ubuntu as the main robot PC. We are still quite inexperienced as far as this is concerned. The sensors we want to integrate are:

- Zed2i
- PhidgetSpatial Precision 3/3/3 IMU
- RS-Bpearl 3D LiDAR

For the Zed2i we use a Nvidia Jetson AGX Orin in addition. The sensors have already been tested with their ROS2 drivers and work independently of the Husky. How would we integrate these sensors correctly into the Husky? Our first attempts to integrate these somehow via the Husky’s robot.yaml were not successful following these instructions here: Cameras | Clearpath Robotics Documentation
The zed2i cam for example is not included in the tf tree of the husky (it should, if working correctly, right?).
Is there possibly another way to do this? Phidget and Bpearl are also not officially supported by Clearpath according to Inertial Measurment Units | Clearpath Robotics Documentation and 3D Lidar | Clearpath Robotics Documentation but it seems that they can still be integrated somehow if you look at the great projects here in the forum!
Any help would be greatly appreciated!

Dear @TKL,

You just need to add a custom URDF to the clearpath → robot.yaml containing the camera and additional sensors. Once done it should be linked.

Yes, you just need to disable the clearpath_control localization file (ekf_localization) and launch a copy with phidgets configuration in your own ros2 launch file.

Hi Sohail,

thank you for your response!
I still have a few questions since we’ve never done this before. So I think we should start with the Zed2i first.

You just need to add a custom URDF to the clearpath → robot.yaml containing the camera and additional sensors. Once done it should be linked.

With that you mean we should add, for example, the Zed2i URDF to the “extras” section instead of the “camera” section (Cameras | Clearpath Robotics Documentation) in the robot.yaml according to this: Extras | Clearpath Robotics Documentation ?

Assuming we get this to work on the robot PC with the robot.yaml. How does the linking work if we launch our zed_wrapper from the Jetson?

Yes, you just need to disable the clearpath_control localization file (ekf_localization) and launch a copy with phidgets configuration in your own ros2 launch file.

I’m not sure how to do this. How do we disable the clearpath localization file i.e. where to find where it launches?

Yes the extras.

It should be no issue, just make sure the tf and tf_static etc. are namespaced.

It is opt/ros/humble/share/clearpath_control