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
Copy file name to clipboardExpand all lines: wiki/actuation/__all_subsections.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -439,7 +439,7 @@ In most of the applications for a DC geared motor speed control or position cont
439
439
In order to use feedback control, we need information about the state of the motor. This is achieved through the use of encoders mounted on the motor shaft. Typically, data from this encoder is fed into a microcontroller, such as an Arduino. The microcontroller would need to have a code for PID control. Another easier option would be to use a motor controller which has the ability to read data from the encoder. One such controller is Pololu Jrk 21v3 USB Motor Controller with Feedback. More details about this component can be found [here](https://www.pololu.com/product/1392.).
440
440
441
441
442
-
/wiki/actuation/moveit-and-HEBI-integration/
442
+
/wiki/actuation/moveit-and-hebi-integration/
443
443
---
444
444
# Jekyll 'Front Matter' goes here. Most are set by default, and should NOT be
445
445
# overwritten except in special circumstances.
@@ -709,7 +709,7 @@ If your sensor readings are very noise you might want to consider adding a Kalma
709
709
Finally, you can write your own PID software using [this guide](http://brettbeauregard.com/blog/2011/04/improving-the-beginners-pid-introduction/). You might want to do this if you want to add custom features or just want to learn more about controls. Only recommended for advanced users.
@@ -897,7 +897,7 @@ For instance, in the [Husky](https://github.com/husky/husky/tree/humble-devel) r
897
897
This tutorial aims to guide you through the process of setting up the ROS 1 navigation stack on the Clearpath Husky and seamlessly connecting it to ROS 2. It assumes a foundational understanding of both ROS 1 and ROS 2.
898
898
899
899
## ROS 1 - ROS 2 Bridge
900
-
To configure the Clearpath Husky hardware, we will be using the [husky_robot](https://github.com/husky/husky_robot) repository. This repository contains the ROS 1 packages for the Husky, including the navigation stack. To connect the ROS 1 packages to ROS 2, we will be using the [ros1_bridge](https://github.com/ros2/ros1_bridge) package. Detailed instruction on how to setup this is provided in [this tutorial](https://roboticsknowledgebase.com/wiki/interfacing/ros1_ros2_bridge/) on the Robotics Knowledgebase. Once the bridge is established, we can proceed to configure the Husky using the following steps.
900
+
To configure the Clearpath Husky hardware, we will be using the [husky_robot](https://github.com/husky/husky_robot) repository. This repository contains the ROS 1 packages for the Husky, including the navigation stack. To connect the ROS 1 packages to ROS 2, we will be using the [ros1_bridge](https://github.com/ros2/ros1_bridge) package. Detailed instruction on how to setup this is provided in [this tutorial](https://roboticsknowledgebase.com/wiki/interfacing/ros1-ros2-bridge/) on the Robotics Knowledgebase. Once the bridge is established, we can proceed to configure the Husky using the following steps.
@@ -1280,7 +1280,7 @@ This tutorial provides a step-by-step guide to configure the Clearpath Husky for
1280
1280
It is recommended to read the [Nav2 documentation](https://navigation.ros.org/index.html) to understand the Nav2 stack in detail. The [Nav2 tutorials](https://navigation.ros.org/getting_started/index.html) are also a good place to start.
Copy file name to clipboardExpand all lines: wiki/common-platforms/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ We encourage contributions to further enhance the knowledge base in this section
35
35
-**[Interfacing with the Nvidia Orin](/wiki/common-platforms/interfacing-with-nvidia-orin/)**
36
36
A comprehensive guide to using the Nvidia Jetson AGX Orin for robotics. Covers power delivery, GPIO pinouts, high-speed interfaces like USB and Ethernet, and debugging tools for reliable sensor integration.
37
37
38
-
-**[Husky Interfacing and Communication](/wiki/common-platforms/husky_interfacing_and_communication/)**
38
+
-**[Husky Interfacing and Communication](/wiki/common-platforms/husky-interfacing-and-communication/)**
39
39
Discusses how to set up communication with the Clearpath Husky robot, including hardware setup and localization using GPS, IMU, and odometry.
Copy file name to clipboardExpand all lines: wiki/common-platforms/ros/ros-intro.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,9 +25,8 @@ Actually, ROS is not an operating system but a meta operating system, which mean
25
25
26
26
ROS is useless without knowing how it works. Merely reading through the tutorials are not enough; this cannot be stressed enough. Learning ROS takes time and effort, so when going through the tutorials, try to understand what you are seeing, and make sure you follow along by Typing the example code, and run each tutorial to learn what is happening.
27
27
28
-
One of the most important package in ROS is [navigation stack](ros-navigation). Here are several topics of it covered in this directory for reference.
28
+
One of the most important package in ROS is [navigation stack](ros-navigation). Here are several topics of it covered in this wiki for reference.
29
29
1.[Global Planner](ros-global-planner.md)
30
-
2.[Local Planner](ros-local-planner)
31
-
3.[Costmap](ros-cost-maps)
32
-
4.[Mapping and Localization](ros-mapping-localization)
33
-
5.[Motion Server](ros-motion-server-framework)
30
+
2.[Costmap](ros-cost-maps)
31
+
3.[Mapping and Localization](ros-mapping-localization)
Copy file name to clipboardExpand all lines: wiki/common-platforms/ros2-navigation-for-clearpath-husky.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ For instance, in the [Husky](https://github.com/husky/husky/tree/humble-devel) r
10
10
This tutorial aims to guide you through the process of setting up the ROS 1 navigation stack on the Clearpath Husky and seamlessly connecting it to ROS 2. It assumes a foundational understanding of both ROS 1 and ROS 2.
11
11
12
12
## ROS 1 - ROS 2 Bridge
13
-
To configure the Clearpath Husky hardware, we will be using the [husky_robot](https://github.com/husky/husky_robot) repository. This repository contains the ROS 1 packages for the Husky, including the navigation stack. To connect the ROS 1 packages to ROS 2, we will be using the [ros1_bridge](https://github.com/ros2/ros1_bridge) package. Detailed instruction on how to setup this is provided in [this tutorial](https://roboticsknowledgebase.com/wiki/interfacing/ros1_ros2_bridge/) on the Robotics Knowledgebase. Once the bridge is established, we can proceed to configure the Husky using the following steps.
13
+
To configure the Clearpath Husky hardware, we will be using the [husky_robot](https://github.com/husky/husky_robot) repository. This repository contains the ROS 1 packages for the Husky, including the navigation stack. To connect the ROS 1 packages to ROS 2, we will be using the [ros1_bridge](https://github.com/ros2/ros1_bridge) package. Detailed instruction on how to setup this is provided in [this tutorial](https://roboticsknowledgebase.com/wiki/interfacing/ros1-ros2-bridge/) on the Robotics Knowledgebase. Once the bridge is established, we can proceed to configure the Husky using the following steps.
@@ -393,7 +393,7 @@ This tutorial provides a step-by-step guide to configure the Clearpath Husky for
393
393
It is recommended to read the [Nav2 documentation](https://navigation.ros.org/index.html) to understand the Nav2 stack in detail. The [Nav2 tutorials](https://navigation.ros.org/getting_started/index.html) are also a good place to start.
0 commit comments