diff --git a/ifm3d_ros_driver/doc/building.md b/ifm3d_ros_driver/doc/building.md index 157b58b..74e4d1d 100644 --- a/ifm3d_ros_driver/doc/building.md +++ b/ifm3d_ros_driver/doc/building.md @@ -5,7 +5,7 @@ We suggest to build the `ifm3d-ros` node on top of Ubuntu 20.04 and ROS noetic. If you have reached this document via the [noetic ifm3d building instructions](noetic.md) and followed all the major steps in there you can skip the three steps listed below. They are just a short repetition. 1. [Ubuntu 20.04 LTS](http://www.ubuntu.com) 2. [ROS Noetic](http://wiki.ros.org/noetic/Installation/) - we recommend `ros-noetic-desktop-full`. -3. [ifm3d](https://github.com/ifm/ifm3d/tree/o3r/dev) +3. [ifm3d](https://github.com/ifm/ifm3d) > **NOTE**: Some users may require older ROS distributions for legacy reasons. The supplied ROS package may very well work with limited changes on older ROS distributions. At least previous version could be run as far back as Indigo and Kinetic. However, we didn't test this ourselves. Please be aware that if you chose to go this route no guarantee is given. diff --git a/ifm3d_ros_driver/doc/troubleshooting.md b/ifm3d_ros_driver/doc/troubleshooting.md index 43577f6..87d80e1 100644 --- a/ifm3d_ros_driver/doc/troubleshooting.md +++ b/ifm3d_ros_driver/doc/troubleshooting.md @@ -13,7 +13,7 @@ On systems utilizing a single core processor, you may find that the Dump, Config This issue can be resolved by setting the "num_worker_threads" parameter for your ROS nodelet manager to use a value > 1. You can read more about this parameter [here](http://wiki.ros.org/nodelet). -The snippet below show's how to set this parameter using the [nodelet.launch](https://github.com/ifm/ifm3d-ros/blob/master/launch/nodelet.launch) file of the ifm3d-ros package. +The snippet below show's how to set this parameter using the [nodelet.launch](https://github.com/ifm/ifm3d-ros/blob/master/ifm3d_ros_driver/launch/nodelet.launch) file of the ifm3d-ros package. ```