Merge pull request #248 from clearpathrobotics/lcamero/platform

Duplicate Platform File

docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/controllers.mdx

@@ -23,7 +23,7 @@ You may need to install _jstest_ with `sudo apt-get install jstest-gtk`
 Clearpath uses the _/bluetooth_teleop_ ROS node to publish velocity commands from the joystick to _/twist_mux_.
 _/twist_mux_ Takes in multiple sources of velocity commands, and prioritizes what actually gets sent to _/cmd_vel_ to drive the robot.
 
-Depending on the robot platform and related controller, you will need to configure your robot's [robot.yaml configuration file](../../../ros/config/yaml/platform.mdx).
+Depending on the robot platform and related controller, you will need to configure your robot's [robot.yaml configuration file](../../../ros/config/yaml/platform/controller.mdx).
 
 ---
 

docs_versioned_docs/version-ros2humble/ros/config/yaml/links.mdx

@@ -37,7 +37,7 @@ Include your custom mesh without creating a URDF of your own. You can either pro
 to the mesh file or if it is included in a ROS 2 package, then you can provide both the package name
 and relative link to the install location within the package.
 
-If you prefer to add a URDF instead, then you can link it directly through the [`platform.extras`](platform.mdx#extras) entry.
+If you prefer to add a URDF instead, then you can link it directly through the [`platform.extras`](platform/extras.mdx#extras) entry.
 <Mesh/>
 
 ## Sample

docs_versioned_docs/version-ros2humble/ros/config/yaml/mounts.mdx

@@ -26,7 +26,7 @@ Most sensors can use similar mounting structures. Therefore, we want to keep mou
 A mounting plate with the defined number of rows and columns of the PACS™ **80 mm X 80 mm** grid.
 
 :::warning not available without pacs:
- At this time, you will **need to use the PACS™ top plate**, only available using the `a200.top_plate` with `model: pacs`, to add these riser mounts. See the [**platform**](./platform.mdx) section for more information.
+ At this time, you will **need to use the PACS™ top plate**, only available using the `a200.top_plate` with `model: pacs`, to add these riser mounts. See the [**platform**](./platform/attachments/overview.mdx) section for more information.
 :::
 
 ### Preset Risers

docs_versioned_docs/version-ros2humble/ros/config/yaml/overview.mdx

@@ -14,7 +14,7 @@ The **Clearpath Robot Configuration YAML**, or `robot.yaml` for short, contains
 
 The `robot.yaml` is composed of five major sections:
 1. [**system**](./system.mdx) level information such as the robot's hostname, IP, and ROS middleware implementation.
-2. [**platform**](./platform.mdx) level configurations such as robot specific mounting structures and parameters.
+2. [**platform**](./platform/overview.mdx) level configurations such as robot specific mounting structures and parameters.
 3. [**links**](./links.mdx) of standard URDF primitives such as boxes, cylinders, and meshes.
 4. [**mounts**](./mounts.mdx) are predefined, generic, sensor mounting structures.
 5. [**sensors**](./sensors/overview.mdx) are selected from an inventory of Clearpath supported sensors.
@@ -44,7 +44,7 @@ You can also skip to each section to get an explanation of each part of the samp
 
 1. [**Serial Number Sample**](./serial.mdx#sample)
 2. [**System Sample**](./system.mdx#sample)
-3. [**Platform Sample**](./platform.mdx#sample)
+3. [**Platform Sample**](./platform/overview.mdx#sample)
 4. [**Links Sample**](./links.mdx#sample)
 5. [**Mounts Sample**](./mounts.mdx#sample)
 6. [**Sensors Sample**](./sensors/overview.mdx#sample)