Skip to content

Commit adc2e98

Browse files
Fix headers for supported sensors, manipulators (#406)
* Add an H2 "Supported ____" to all sensor pages, move individual sensors to H3 for consistency in header levels * Add H2 level for supported manipulators
1 parent c7060b8 commit adc2e98

File tree

7 files changed

+32
-18
lines changed

7 files changed

+32
-18
lines changed

docs_versioned_docs/version-ros2jazzy/ros/config/yaml/manipulators.mdx

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,9 @@ Additionally, MoveIt! must be launched to plan paths and move manipulators to a
2020

2121
Every arm can have at most one gripper, and grippers can only be added to an existing arm. This way, depending on the arm and the gripper, the configuration system can determine whether the arm handles communication with the gripper or whether it must be done through an external connection directly to the robot computer.
2222

23-
## Kinova Arms {#kinova-arms}
23+
## Supported Manipulators
24+
25+
### Kinova Arms {#kinova-arms}
2426
<KinovaGen3Lite/>
2527
<br/>
2628

@@ -30,17 +32,17 @@ Every arm can have at most one gripper, and grippers can only be added to an exi
3032
<KinovaGen37Dof/>
3133
<br/>
3234

33-
## Kinova Grippers {#kinova-grippers}
35+
### Kinova Grippers {#kinova-grippers}
3436
<Kinova2FLite/>
3537
<br/>
3638

37-
## Robotiq Grippers {#robotiq-grippers}
39+
### Robotiq Grippers {#robotiq-grippers}
3840
<Robotiq2F85/>
3941
<br/>
4042

4143
<Robotiq2F140/>
4244
<br/>
4345

44-
## Universal Robots {#universal-robots}
46+
### Universal Robots {#universal-robots}
4547
<UniversalRobots/>
4648
<br/>

docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/charger.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,5 +9,7 @@ import Wiferion from "/docs_versioned_docs/version-ros2jazzy/components/yaml/sen
99

1010
Wireless battery chargers are necessary attachments for a fully autonomous, self docking robot platform. These devices incorporate sensors that determine the quality of the charging position and orientation, status of the charging coil, and status of the stationary unit.
1111

12-
## Wiferion Wireless Charger
12+
## Supported Chargers
13+
14+
### Wiferion Wireless Charger
1315
<Wiferion/>

docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/gps.mdx

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,14 +12,16 @@ import SwiftNavDuro from "/docs_versioned_docs/version-ros2jazzy/components/yaml
1212

1313
GPS (aka: GNSS) receivers are all devices that publish a `sensor_msgs/NavSatFix` message, which provides a latitude and longitude position.
1414

15-
## SwiftNav Duro
15+
## Supported GPS Sensors
16+
17+
### SwiftNav Duro
1618
<SwiftNavDuro/>
1719

18-
## Garmin 18X
20+
### Garmin 18X
1921
<Garmin18x/>
2022

21-
## Novatel Smart6
23+
### Novatel Smart6
2224
<NovatelSmart6/>
2325

24-
## Novatel Smart7
26+
### Novatel Smart7
2527
<NovatelSmart7/>

docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/imu.mdx

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,13 @@ import MicrostrainIMU from "/docs_versioned_docs/version-ros2jazzy/components/ya
1111

1212
Inertial measurement units are sensors that publish messages of the type `sensor_msgs/Imu`. These messages contain orientation, angular velocity, and/or linear acceleration depending on the device.
1313

14-
## Microstrain IMU
14+
## Supported IMUs
15+
16+
### Microstrain IMU
1517
<MicrostrainIMU/>
1618

17-
## CHRobotics UM6
19+
### CHRobotics UM6
1820
<CHRoboticsUM6/>
1921

20-
## Redshift UM7
22+
### Redshift UM7
2123
<RedShiftUM7/>

docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/ins.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,8 @@ can be augmented with GNSS and/or visual data for more precise outputs.
1313
INS may publish a variety of data, including `sensor_msgs/msg/Imu`,
1414
`sensor_msgs/msg/NavSatFix`, and `nav_msgs/msg/Odometry` types.
1515

16-
## Fixposition Vision-RTK 2
16+
## Supported INS Sensors
17+
18+
### Fixposition Vision-RTK 2
1719

1820
<FixpositionXVN/>

docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/lidar2d.mdx

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,10 @@ import SickLMS1xx from "/docs_versioned_docs/version-ros2jazzy/components/yaml/s
1010

1111
Two dimensional LiDARs provide a single planar scan, which is pusblished as a `sensor_msgs/LaserScan` message. It is important to accurately position the scanner in the visual description of the robot to ensure that the scanned plane is accurate with respect to the robot.
1212

13-
## Hokuyo UST
13+
## Supported 2D Lidars
14+
15+
### Hokuyo UST
1416
<HokuyoUST/>
1517

16-
## SICK LMS1xx
18+
### SICK LMS1xx
1719
<SickLMS1xx/>

docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/lidar3d.mdx

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,13 @@ import VelodyneLidar from "/docs_versioned_docs/version-ros2jazzy/components/yam
1111

1212
Three dimensional LiDARs provide a pointcloud of all points detected by several planar scanners at various angles, which is published as a `sensor_msgs/PointCloud2` message. It is important to accurately position the LiDAR in the visual descriptiuon of the robot to ensured that the scanned points are accurate with respect to the robot.
1313

14-
## Ouster OS1
14+
## Supported 3D Lidars
15+
16+
### Ouster OS1
1517
<OusterLidar />
1618

17-
## Seyond Robin W
19+
### Seyond Robin W
1820
<SeyondLidar />
1921

20-
## Velodyne Lidar
22+
### Velodyne Lidar
2123
<VelodyneLidar/>

0 commit comments

Comments
 (0)