Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
52 commits
Select commit Hold shift + click to select a range
47ece3c
first pass at adding ROS-like api to the documentaion
jmastrangelo-cpr Jul 2, 2025
5264fb4
added a using the api page
jmastrangelo-cpr Aug 19, 2025
b41cb7c
visual as table
jmastrangelo-cpr Aug 25, 2025
154e804
proofreading - mostly spelling (#459)
nvanheyst Aug 26, 2025
e01693c
Update supported_manipulators.mdx
tonybaltovski Aug 27, 2025
00111fe
Merge pull request #460 from clearpathrobotics/add-lift-support
tonybaltovski Aug 27, 2025
bbbf2f7
spelling (#461)
nvanheyst Aug 28, 2025
0afddfb
Accessories section – spelling and grammar (#462)
nvanheyst Aug 29, 2025
d094696
Ridgeback r100 step model (#463)
rhysfaultless-cpr Sep 2, 2025
6287d30
spelling and grammar (#464)
nvanheyst Sep 2, 2025
005d757
change headings
jmastrangelo-cpr Sep 8, 2025
a2f5876
moved changes made to 2.0.0 to the docs_outdoornav_usesr_manual folder
jmastrangelo-cpr Sep 11, 2025
f2041df
fix link to delete dock
jmastrangelo-cpr Sep 11, 2025
c8ebaca
review changes
jmastrangelo-cpr Sep 11, 2025
6e851c1
turn off next version
jmastrangelo-cpr Sep 11, 2025
b28110a
fix broken link
jmastrangelo-cpr Sep 11, 2025
9aacf8a
fix broken links
jmastrangelo-cpr Sep 11, 2025
842d0d5
Merge pull request #466 from clearpathrobotics/ONAV-2803
jmastrangelo-cpr Sep 11, 2025
3f70940
added update instructions
jmastrangelo-cpr Aug 19, 2025
4c52ef3
move note location and update scp command
jmastrangelo-cpr Aug 22, 2025
0fe8cd7
Added setup path details for running clearpath_viz. (#467)
tonybaltovski Sep 12, 2025
67e8a4e
finalized update pages for 2.0.0 and 2.1.0
jmastrangelo-cpr Sep 12, 2025
57e852a
CPE87-2851: Add more A300 regulatory notes (#472)
jhiggins-cpr Sep 17, 2025
487128c
Remove duplicate regulatory entry (#473)
jhiggins-cpr Sep 18, 2025
4bb45b6
Rename oakd namespace in robot.yaml (#471)
civerachb-cpr Sep 18, 2025
f0865ac
Added note to use CLI to get diagnostics if Cockpit is not running. (…
tonybaltovski Sep 19, 2025
da10930
Jackal pacs integration (#474)
rhysfaultless-cpr Sep 19, 2025
9e8be94
review changes
jmastrangelo-cpr Sep 22, 2025
fe8ea38
review fix
jmastrangelo-cpr Sep 22, 2025
e2181f7
Merge pull request #469 from clearpathrobotics/ONAV-2811
jmastrangelo-cpr Sep 22, 2025
0831074
Readme updates (#476)
rhysfaultless-cpr Oct 1, 2025
cf59025
Jackal heading indenture (#477)
rhysfaultless-cpr Oct 1, 2025
4a8eeae
Updated the hyperlink to the Husky A200's STEP model. (#478)
rhysfaultless-cpr Oct 1, 2025
0755131
fixed some small issues with the update process
jmastrangelo-cpr Oct 2, 2025
3172298
Merge pull request #479 from clearpathrobotics/fix/update
jmastrangelo-cpr Oct 2, 2025
ec9ccc0
Add documentation for system.bash and updated platform.extras.launch …
civerachb-cpr Oct 2, 2025
a5138cd
Add documentation for new automatic discovery fields (#470)
civerachb-cpr Oct 2, 2025
f0d53fe
Update navigation tutorials with `scan_topic` argument (#480)
civerachb-cpr Oct 16, 2025
d451a00
added messages for the 2.1.1 release (will released as documentation …
jmastrangelo-cpr Oct 16, 2025
85963f7
added task executor action/service
jmastrangelo-cpr Oct 17, 2025
065dada
Merge pull request #481 from clearpathrobotics/2.1.0_outdoornav_msg_u…
jmastrangelo-cpr Oct 17, 2025
b5ba430
release onav 2.1.0
jmastrangelo-cpr Oct 17, 2025
3a7068a
Merge pull request #483 from clearpathrobotics/release_onav_2.1.0
jmastrangelo-cpr Oct 21, 2025
ad2d1f9
Added Jazzy 2.8 changes for clearpath_config.
tonybaltovski Oct 23, 2025
b3b0a10
Added Jazzy 2.8 changes for clearpath_common.
tonybaltovski Oct 23, 2025
7241df8
Added Jazzy 2.8 changes for clearpath_robot.
tonybaltovski Oct 23, 2025
c3753dc
Manipulators (#485)
luis-camero Oct 23, 2025
751400b
Fixed spelling inconsistencies.
tonybaltovski Oct 24, 2025
02ac9c3
Added note about 3D lidar scans being experimental.
tonybaltovski Oct 24, 2025
de02be7
Merge pull request #486 from clearpathrobotics/release-jazzy-2.8
tonybaltovski Oct 24, 2025
f987095
Grammer changes.
tonybaltovski Oct 24, 2025
c4e3ab8
Merge pull request #487 from clearpathrobotics/fix/3d-nav-note
tonybaltovski Oct 24, 2025
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
44 changes: 37 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,9 +50,9 @@

git clone https://github.com/clearpathrobotics/cpr-documentation.git

2. Create a branch from development. with a name indicating the purpose, such as _feature_xxxxxx_
2. Create a branch from development with a name indicating the purpose, such as _feature_xxxxxx_
3. Make changes to the relevant files.
4. Test using your local server, using the steps mentioned [Steps to run this on your computer locally](##-steps-to-run-this-on-your-computer-locally)
4. Test using your local server, using the steps mentioned [Steps to run this on your computer locally](#steps-to-run-this-on-your-computer-locally)
5. When ready, enter `ctrl-c` in your terminal to stop the server. Then run `npm run build` to test that the site builds corretly.
6. Resolve any errors that the terminal reports, and rerun the command `npm run build`.
7. Finally, check that your updates adhere to our code formatting standard, by running the command `npm run format-check`.
Expand Down Expand Up @@ -129,18 +129,18 @@ When it is time to publish a numbered release of the user manual:

<br>
Follow the steps for the OutdoorNav User Manual workflow above, replacing
**outdoornav** with **indoornav**.
<b>outdoornav</b> with <b>indoornav</b>.

</details>

## Workflow for publishing Robots / ROS User Manual updates
## Workflow for publishing Software User Manual updates

<details>

<summary>Click to expand for details on how to update the Robots / ROS User Manual</summary>
<summary>Click to expand for details on how to update the Software User Manual</summary>

<br>
The Robots / ROS sections of the website are a "versioned" document called `docs`, which means that a snapshot of the content is
The Software sections of the website are a "versioned" document called <code>docs</code>, which means that a snapshot of the content is
made to align with each ROS version. This allows users to access version-specific copies of the
documentation.

Expand Down Expand Up @@ -217,7 +217,7 @@ includeCurrentVersion: false,
HTML commenting—`<!-- -->`—causes issues with the MDX extension in VS Code.
2. Refer to [Docusaurus's guide](https://docusaurus.io/docs/next/markdown-features) for supported Markdown features.
3. For advanced users, refer to [Markdown MDX](https://mdxjs.com/) for adding React Components to a Markdown file.
4. for advanced users, you may create React pages using _.js_ or _.ts_ file types.
4. For advanced users, you may create React pages using _.js_ or _.ts_ file types.

## How should I name files?

Expand Down Expand Up @@ -513,3 +513,33 @@ Even though the font size has been modified, the rendered diagram's font may not
`}
/>
```

## Spelling Guide

Spelling on within this repository should align with the Government of Canada's [TERMIUM Plus®](https://www.btb.termiumplus.gc.ca/).
Industry terms should align with the related organization's preferred spelling.

<details>
<summary>Click to expand spelling examples</summary>
<table>
<tr><th>Correct spelling</th><th>Mistake</th></tr>
<tr><th>10</th><th>Ten</th></tr>
<tr><th>2X</th><th>2x</th></tr>
<tr><th>Aluminum</th><th>Aluminium</th></tr>
<tr><th>Antennas</th><th>Antennae</th></tr>
<tr><th>Antennas</th><th>Aerial</th></tr>
<tr><th>AWS, or Amazon Web Services</th><th>Amazon AWS</th></tr>
<tr><th>Colour</th><th>Color</th></tr>
<tr><th>Computer</th><th>PC</th></tr>
<tr><th>Enable Switch</th><th>Deadman Switch</th></tr>
<tr><th>Emergency Stop</th><th>E-stop</th></tr>
<tr><th>GitHub</th><th>Github</th></tr>
<tr><th>Lidar</th><th>LiDAR</th></tr>
<tr><th>Metre</th><th>Meter</th></tr>
<tr><th>ROS 2</th><th>ROS2</th></tr>
<tr><th>RViz</th><th>Rviz</th></tr>
<tr><th>Gmapping</th><th>gmapping</th></tr>
<tr><th>Tire</th><th>Tyre</th></tr>
<tr><th>Wi-Fi</th><th>wifi</th></tr>
</table>
</details>
2 changes: 1 addition & 1 deletion components/common_wireless_joystick_ps4.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ To connect the joystick to your robot:
3. Press the _PS_ button in the centre of the joystick.
4. The joystick's top LED should start pulsing white or blue.
This means the joystick is attempting to connect.
5. The joysick's top LED should eventually become solid blue, indicating that it has connected to the robot's computer.
5. The joystick's top LED should eventually become solid blue, indicating that it has connected to the robot's computer.


<center>
Expand Down
2 changes: 1 addition & 1 deletion components/husky_a200/husky_a200_step_model.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ import ComponentButtonStepDownload from "/components/button_download_step.tsx";
### STEP Model {#step-model}

<div>
<ComponentButtonStepDownload filePath={"https://cpr-documentation-large-files.s3.us-east-2.amazonaws.com/034991-GEO_1.STEP"}/>
<ComponentButtonStepDownload filePath={"https://cpr-documentation-large-files.s3.us-east-2.amazonaws.com/034991-GEO_2.STEP"}/>

This simplified 3D model of the Husky A200 includes details like the internal
battery, circuit board where you can connect to the robot's electrical
Expand Down
2 changes: 1 addition & 1 deletion components/husky_a300/husky_a300_amp_arch_cables.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ The _Sensor Arch_ places Husky's cameras and GNSS antennas above the robot for o
These steps will give you access to the related cable routings for repairs:

1. Remove the 3 screws from the inside access panel.
2. Remove the panel by sliding is toward the end of the robot.
2. Remove the panel by sliding it toward the end of the robot.
3. The _Arch Posts_ have cable tie anchors.
You can remove the cable ties with side cutters.
4. Cables route through an obround cutout in the _Enclosure_.
Expand Down
2 changes: 1 addition & 1 deletion components/husky_a300/husky_a300_amp_check_sensors.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
Husky AMP includes several sensors that are used for robot navigation. After connecting
to Husky AMP's network, confirm that each sensor is functional by using the steps below.

1. Connect to your laptop to the robot using SSH. To do so, execute the following in a terminal window:
1. Connect your laptop to the robot using SSH. To do so, execute the following in a terminal window:
```
ssh robot@192.168.131.1
```
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@
</center>

To make a Husky AMP, we take a Husky A300, remove the Top Plate, and then install an enclosure on top of the base robot.
We added a connector bulkhead between the base robot and the enclosure to keep cable routings tidy, and make the maintenence process quick.
We added a connector bulkhead between the base robot and the enclosure to keep cable routings tidy, and make the maintenance process quick.
The connectors on this bulkhead are extension cables from existing [Husky A300 interfaces](/docs_robots/outdoor_robots/husky/a300/integration_husky/#system-interface-circuit-board-connector-summary), which are listed below.

<center>
Expand Down
2 changes: 1 addition & 1 deletion components/husky_a300/husky_a300_components_observer.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,6 @@ Refer to the [Husky A300 AMP's Components Overview](/docs_robots/solutions/husky
src="/img/robot_images/husky_a300_images/husky_a300_observer_isometric_3.png"
width="800"
/>
<figcaption>The Husky Oberver, with the included Stationary Dock.</figcaption>
<figcaption>The Husky Observer, with the included Stationary Dock.</figcaption>
</figure>
</center>
2 changes: 1 addition & 1 deletion components/husky_a300/husky_a300_computer.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Clearpath offers a standard computer with an Intel i3 processor, or a performanc
4. Wi-Fi antennas.
5. Power cable.
6. Optional graphics card's PCIe riser cable.
4. Remove the 4 screws fastning the computer to Husky's _Electronics Tray_.
4. Remove the 4 screws fastening the computer to Husky's _Electronics Tray_.
5. Remove the computer from the robot.

:::note
Expand Down
2 changes: 1 addition & 1 deletion components/husky_a300/husky_a300_electronics_tray.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ This tray includes the:
* Optional secondary computer or graphics card, _(not shown in the image)_
* Optional USB hub, _(not shown in the image)_

You may want to access remove the _Electonics Tray_ to access the integration bay under the tray,
You may want to remove the _Electronics Tray_ to access the integration bay under the tray,
or to maintain Husky's _Batteries_ and _Power Distribution_ components.

#### Hinging The Electronics Tray
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ The 2 relays are connected in series, so if one welds closed due to a failure, t
The relays's physical states are monitored with Husky's Common Core microcontroller, and should flag a maintenance issue if either relay is damaged.

<Admonition type="danger" title=" ">
Husky's microcontroller is does not meet any performance level per ISO 13849-1.
Husky's microcontroller does not meet any performance level per ISO 13849-1.
Husky's microcontroller can be replaced with a PLC to achieve a known performance level for fault monitoring.
[Contact our Support Team](#support) if you have questions about this.
</Admonition>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ The Husky's status lights show these light patterns for different Emergency Stop

1. Twist all the _Emergency Stop Buttons_.
2. Close the Husky's _Rear Charge Port Door_.
3. If included; conncet the _Wireless Emergency Stop_ to the Husky.
3. If included; connect the _Wireless Emergency Stop_ to the Husky.
4. If included; clear the Emergency Stop State on your custom devices.

After clearing the Emergency Stop, the Husky's status lights should change to the _Needs Reset_ state's pattern.
Expand Down
2 changes: 1 addition & 1 deletion components/husky_a300/husky_a300_fans.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ These fans operate similar to a server; as all 4 push air into the robot to crea
src="/img/robot_images/husky_a300_images/husky_a300_fans_2.png"
width="500"
/>
<figcaption>Fiew From The Front Of Husky</figcaption>
<figcaption>View From The Front Of Husky</figcaption>
</figure>
</center>
7. Disconnect the fan's latching connector, and remove the fan.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

[//]: <> (TODO, add image of an internal integration)

There are interfaces inside the Husky for your custom compnents.
There are interfaces inside the Husky for your custom components.
This [Interface Control Drawing](/assets/pdf/clearpath_robotics_034163.pdf) shows the available volume near the robot's batteries,
noting that the size of this volume changes depending on what battery configuration your Husky has—_(40 Ah, 80 Ah, or 120 Ah)_.
The drawing also shows mounting provisions on the robot's Electronics Tray, for including these components:
Expand Down
2 changes: 1 addition & 1 deletion components/husky_a300/husky_a300_ip_addresses.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,6 @@
:::info Custom Additions

Our [Network IP Addresses page](/docs/ros/networking/network_ip_addresses) lists the common ranges we use per sensor type.
Clearpath will provide a supplementary manual that includes the IP addressess of custom configuration sensors.
Clearpath will provide a supplementary manual that includes the IP addresses of custom configuration sensors.

:::
2 changes: 1 addition & 1 deletion components/husky_a300/husky_a300_lifting_sling.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
</figure>
</center>

The lifting equipment and straps must rated for the weight of Husky and any mounted payloads, plus any factor of safety per your local worksite regulations.
The lifting equipment and straps must be rated for the weight of Husky and any mounted payloads, plus any factor of safety per your local worksite regulations.
Refer to the [Husky's Technical Specifications](#technical-specifications) for the weight of Husky and its maximum payload.

:::note
Expand Down
2 changes: 1 addition & 1 deletion components/husky_a300/husky_a300_lockout_tagout.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ import Admonition from "@theme/Admonition";
</figure>
</center>

Lockout procedures remove potentional energy from machines as we perform maintenance.
Lockout procedures remove potential energy from machines as we perform maintenance.
This reduces risk of harm while performing maintenance.
The Husky's main source of potential energy is the batteries.
We cannot completely discharge these batteries without damaging them, but we can disconnect them from all the robot's electronics.
Expand Down
4 changes: 2 additions & 2 deletions components/husky_a300/husky_a300_motors.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,9 @@
width="600"
/>
</center>
3. Disconnect the both sets of motor power and cables from the chassis on the side of the robot with the motor being replaced.
3. Disconnect both sets of motor power and cables from the chassis on the side of the robot with the motor being replaced.
The thick power cables are removed by pulling on the cable.
The thiner data cables have a latch on the connector; press on the latch and then pull on the connector.
The thinner data cables have a latch on the connector; press on the latch and then pull on the connector.
<center>
<img
src="/img/robot_images/husky_a300_images/husky_a300_motor_2.jpg"
Expand Down
2 changes: 1 addition & 1 deletion components/husky_a300/husky_a300_network_switch.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ The network switch connects the primary computer, the rear debugging port, and a
When reinstalling the switch:

* Make sure the power cable is connected.
* Make sure the waterfroofing washers are included.
* Make sure the waterproofing washers are included.
* Torque the 4 screws to 1.2 N·m.

:::
Expand Down
6 changes: 3 additions & 3 deletions components/husky_a300/husky_a300_power_connections.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ User Power is enabled by default shortly after the robot first powers up, regard
#### Expansion Power _(EXP 1 and EXP 2)_ {#expansion-power}

There are 2 Expansion Power connectors on the System Interface circuit board.
The Expanison Power connectors can power small manipulators, DC-AC inverters, and DC-DC supplies.
The Expansion Power connectors can power small manipulators, DC-AC inverters, and DC-DC supplies.

These connectors supply VBAT voltage, with a combined current of up to 20 A.
The connectors also include soft-start circuitry which limits inrush current to 25 A.
Expand Down Expand Up @@ -209,8 +209,8 @@ You must enable the output, via the ROS topic above, each time after the system

### AUX Inputs {#aux-inputs}

The System Interface circuit board has 3 auxilliary inputs—_(AUX1 IN, AUX2 IN, AUX3 IN)_—that allow external payloads to provide inputs to the robot.
Each of these auxilliary inputs can be driven by one of the following:
The System Interface circuit board has 3 auxiliary inputs—_(AUX1 IN, AUX2 IN, AUX3 IN)_—that allow external payloads to provide inputs to the robot.
Each of these auxiliary inputs can be driven by one of the following:

- a 12 V input
- a 24 V input
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,9 @@ Performing a circle check can reduce safety risks, increase the operating lifesp
These are our suggested daily checks before sending the Husky on missions:

1. Check that the weather forecast has acceptable conditions for the robot.
2. Check that the intended worksite's terrain is acceptable, without deep trenches, overhanging obstacles, children, of other hazards that were not acceptable per your Risk Assessment.
2. Check that the intended worksite's terrain is acceptable, without deep trenches, overhanging obstacles, children, or other hazards that were not acceptable per your Risk Assessment.
3. Check the tire pressures.
4. Inspect the tire treads for excessive wear of punctures.
4. Inspect the tire treads for excessive wear or punctures.
5. Inspect the drivetrain for loose screws.
6. Inspect the drivetrain for any branches or debris lodged in robot's motors or suspension.
7. Inspect the drivetrain for damage to any of the motor cables or to the cable ties that are used to secure the motor cables to the suspension beam. Check that there is clearance between the motor cables and the tires.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ Confirm that Husky's Emergency Stop System is functioning after changing any of
</center>

5. Remove the failing circuit board by gently lifting the board up.
These circuit boards have many pins, so a large amount of force is requred.
These circuit boards have many pins, so a large amount of force is required.
<center>
<img
src="/img/robot_images/husky_a300_images/husky_a300_circuitboard_4.jpg"
Expand Down Expand Up @@ -159,7 +159,7 @@ Confirm that Husky's Emergency Stop System is functioning after changing any of

5. Place the old and new Main circuit boards on an ESD mat.

6. Move the funcational DC-DC, BLDC, and Common Core circuit boards from the old Main circuit board to the new Main circuit board by following the procedures above.
6. Move the functional DC-DC, BLDC, and Common Core circuit boards from the old Main circuit board to the new Main circuit board by following the procedures above.
<center>
<img
src="/img/robot_images/husky_a300_images/husky_a300_circuitboard_10.jpg"
Expand Down
8 changes: 4 additions & 4 deletions components/husky_a300/husky_a300_safety_alternate.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -232,7 +232,7 @@ export function ComponentRiskAssessmentLine_5_6_7_8() {
<SafetyAdmonition>
<>
Husky A300 with payload can have a total kinetic energy of 360 joules of energy <em>(180 kg at 2 m/s)</em>.
This is a significant amount of energy that can cause severe injury of death.
This is a significant amount of energy that can cause severe injury or death.
<br/>
<br/>
Husky A300, Husky AMP, and Husky Observer have been designed to ensure the robot will not impact a person's torso or head.
Expand Down Expand Up @@ -393,7 +393,7 @@ export function ComponentRiskAssessmentLine_24() {
<SafetyAdmonition>
<>
Do not ride on a moving Husky A300.
This includes standing, sitting, or any other method of mobing a person using a Husky A300.
This includes standing, sitting, or any other method of moving a person using a Husky A300.
<br/>
<br/>
The robot may become unstable or move unpredictably.
Expand Down Expand Up @@ -445,7 +445,7 @@ export function ComponentRiskAssessmentLine_27() {
Racking must be securely fastened, and be loaded to prevent falling items.
<br/>
<br/>
It is the commissioning and operating teams's responibility to ensure that the Husky A300 colliding with racking will not cause items to fall on a person.
It is the commissioning and operating teams's responsibility to ensure that the Husky A300 colliding with racking will not cause items to fall on a person.
It is the commissioning team's responsibility to ensure local regulations are followed.
</>
</SafetyAdmonition>
Expand Down Expand Up @@ -675,7 +675,7 @@ export function ComponentRiskAssessmentLine_53() {
<div>
<SafetyAdmonition>
<>
Always tie up long hair, and remove loose jewellery, and wear clothing without snag points when working aroung Husky A300.
Always tie up long hair, and remove loose jewellery, and wear clothing without snag points when working around Husky A300.
This reduces the risk of entanglement with the moving robot.
</>
</SafetyAdmonition>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Husky A300 is equipped with 3 safety functions to reduce the system risk:
:::info

Your commissioning team must evaluate the functionality of Husky's safety functions in the context of your worksite and use case.
Perfrom a Risk Assessment to understand the risks of deploying Husky in your application, and whether customizations should be be made to recude these risks.
Perform a Risk Assessment to understand the risks of deploying Husky in your application, and whether customizations should be made to reduce these risks.

ISO 12100 is the Risk Assessment guide that we use at Clearpath Robotics, but there are other options from standards agencies like ISO, and IEC.

Expand Down
2 changes: 1 addition & 1 deletion components/husky_a300/husky_a300_system_architecture.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ import Admonition from "@theme/Admonition";
<br/>
<br/>

The motor controllers and batteries connect to the MCU through indiviual CANbuses.
The motor controllers and batteries connect to the MCU through individual CANbuses.
The MCU's firmware then passes this to the computer over Ethernet.
The computer is configured with SocketCAN to interface with these networks.

Expand Down
2 changes: 1 addition & 1 deletion components/husky_a300/husky_a300_system_limits.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ To reduce current draw, consider commanding wider-radius turns from your control
Ensure that the robot's centre of mass will not result in tipping hazards due to driving on hills.

Your commissioning team needs to perform calculations to confirm the robot's centre of mass will remain within the robot's footprint across its operating terrain.
You calculations should include a safety margin.
Your calculations should include a safety margin.

Refer to the [Technical Specifications](#technical-specifications) for the safe operating limits when there is no payload on the Husky.

Expand Down
Loading