Merge pull request #416 from clearpathrobotics/development

Merge development into production

Author: jhiggins-cpr

components/button_step_download.module.css renamed to components/button_download.module.css

@@ -1,4 +1,4 @@
-import styles from "./button_step_download.module.css";
+import styles from "./button_download.module.css";
 
 export default function ButtonStepDownload(props) {
   return(

components/button_step_download.tsx renamed to components/button_download_step.tsx

@@ -0,0 +1,12 @@
+import styles from "./button_download.module.css";
+
+export default function ButtonDownload(props) {
+  return(
+    <div>
+      <div className={styles.buttons}>
+        <a className="button button--secondary button--lg" href={props.filePath} target="_blank">Download The Robot's Wiring Diagram</a>
+      </div>
+      <br/>
+    </div>
+  )
+}

components/button_download_wiring_diagram.tsx

@@ -0,0 +1,77 @@
+{/* This file has been auto-generated by scripts/update_error_codes.py */}
+
+---
+## E100 - Critical errors {#critical-errors}
+
+### E110 - Main Contactor Error! {#E110} 
+
+
+### E113 - Battery Out of Range! {#E113} 
+
+
+### E116 - E-Stop Contactor Error! {#E116} 
+
+
+### E117 - Brake Contactor Error! {#E117} 
+
+
+### E120 - Motor 1 Voltage Range Error! {#E120} 
+
+
+### E121 - Motor 2 Voltage Range Error! {#E121} 
+
+
+### E122 - Motor 3 Voltage Range Error! {#E122} 
+
+
+### E123 - Motor 4 Voltage Range Error! {#E123} 
+
+
+### E124 - Motor Voltage Range Error! {#E124} 
+This is a general error for a voltage issue on any motor.
+
+### E140 - User Power Contactor Error! {#E140} 
+
+
+### E150 - 24V Aux Power Fail! {#E150} 
+
+
+### E151 - 12V Aux Power Fail! {#E151} 
+
+
+### E152 - 12V1 Sys Power Fail! {#E152} 
+
+
+### E153 - 12V2 Sys Power Fail! {#E153} 
+
+
+### E154 - 12V A User Power Fail! {#E154} 
+
+
+### E155 - 12V B User Power Fail! {#E155} 
+
+
+### E156 - VBAT User Power Fail! {#E156} 
+
+
+### E157 - 24V User Power Fail! {#E157} 
+
+
+### E160 - Power Supply Failure! {#E160} 
+This is a general error which is set for any of the power fail errors.
+
+### E170 - VBAT User Power Fuse Tripped! {#E170} 
+
+
+### E171 - 24V User Power Fuse Tripped! {#E171} 
+
+
+### E172 - 12V A User Power Fuse Tripped! {#E172} 
+
+
+### E173 - 12V B User Power Fuse Tripped! {#E173} 
+
+
+### E174 - Expansion Power Fuse Tripped! {#E174} 
+
+

components/error_codes/_critical_errors.mdx

@@ -0,0 +1,59 @@
+{/* This file has been auto-generated by scripts/update_error_codes.py */}
+
+---
+## E800 - Low priority errors {#low-priority-errors}
+
+### E810 - Fan 1 Below Minimum Speed! {#E810} 
+
+
+### E811 - Fan 2 Below Minimum Speed! {#E811} 
+
+
+### E812 - Fan 3 Below Minimum Speed! {#E812} 
+
+
+### E813 - Fan 4 Below Minimum Speed! {#E813} 
+
+
+### E814 - Fan 5 Below Minimum Speed! {#E814} 
+
+
+### E815 - Fan 6 Below Minimum Speed! {#E815} 
+
+
+### E816 - Fan 7 Below Minimum Speed! {#E816} 
+
+
+### E817 - Fan 8 Below Minimum Speed! {#E817} 
+
+
+### E820 - Fan Below Minimum Speed! {#E820} 
+This is a general error for any fan.
+
+### E830 - Fan 1 Above Maximum Speed! {#E830} 
+
+
+### E831 - Fan 2 Above Maximum Speed! {#E831} 
+
+
+### E832 - Fan 3 Above Maximum Speed! {#E832} 
+
+
+### E833 - Fan 4 Above Maximum Speed! {#E833} 
+
+
+### E834 - Fan 5 Above Maximum Speed! {#E834} 
+
+
+### E835 - Fan 6 Above Maximum Speed! {#E835} 
+
+
+### E836 - Fan 7 Above Maximum Speed! {#E836} 
+
+
+### E837 - Fan 8 Above Maximum Speed! {#E837} 
+
+
+### E840 - Fan Above Maximum Speed! {#E840} 
+This is a general error for any fan.
+

components/error_codes/_low_priority_errors.mdx

@@ -0,0 +1,27 @@
+{/* This file has been auto-generated by scripts/update_error_codes.py */}
+
+import CriticalErrors from "./_critical_errors.mdx";
+import LowPriorityErrors from "./_low_priority_errors.mdx";
+
+<style>
+    {`
+    h2::before {
+    content: "" !important;
+    }
+    h3::before {
+    content: "" !important;
+    }
+    h4::before {
+    content: "" !important;
+    }
+    `}
+</style>
+
+# Error Codes
+
+This section includes a full list of the possible error codes along with troubleshooting guidance for each one.
+
+<CriticalErrors />
+
+<LowPriorityErrors />
+

components/error_codes/error_codes.mdx

@@ -1,4 +1,4 @@
-### Air Filter
+### Air Filter  {#air-filter-maintenance}
 
 Husky includes four 80 X 80 mm fans to cool the internal electronics.
 The air passes through the Husky's _Front Grille_, then through the _Air Filter_, before reaching the fans.

components/husky_a300/husky_a300_air_filter.mdx

@@ -0,0 +1,24 @@
+### Check That Sensors Are Functional
+
+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:
+   ```
+   ssh robot@192.168.131.1
+   ```
+   You will be prompted to enter a password. The default password is `clearpath`.
+1. Use the `ping` command to check that each of the [sensors](#ip-addresses) is functional.
+   For example, to confirm that the front teleop camera (`192.168.131.15`) is working:
+   ```
+   $ ping 192.168.131.15
+   PING 192.168.131.15 (192.168.131.2) 56(84) bytes of data.
+   64 bytes from 192.168.131.15: icmp_seq=1 ttl=255 time=0.265 ms
+   64 bytes from 192.168.131.15: icmp_seq=2 ttl=255 time=0.213 ms
+   64 bytes from 192.168.131.15: icmp_seq=3 ttl=255 time=0.282 ms
+   64 bytes from 192.168.131.15: icmp_seq=4 ttl=255 time=0.216 ms
+   ^C
+   --- 192.168.131.15 ping statistics ---
+   4 packets transmitted, 4 received, 0% packet loss, time 3100ms
+   rtt min/avg/max/mdev = 0.213/0.244/0.282/0.030 ms
+   ```

components/husky_a300/husky_a300_amp_check_sensors.mdx

@@ -0,0 +1,19 @@
+import Admonition from "@theme/Admonition";
+
+### Connecting To Husky AMP's Network  {#basic-network-connection}
+
+To access additional Husky AMP functionality, a network connection to the robot is required.
+The easiest way to accomplish this is to connect your laptop to Husky AMP's Wi-Fi
+access point using the steps below.
+
+1. Use your laptop to find and to connect to Husky AMP's Wi-Fi network. The Wi-Fi network name (SSID) will be
+   `cpr_a300_amp_XXXXX`, where `XXXXX` matches the serial number of the Husky AMP. When
+   prompted, use the password `clearpath`.
+
+1. Confirm that your laptop's Wi-Fi network interface is configured to use DHCP and that it
+   has been assigned an IP address in the `192.168.131.XXX` range.
+
+<Admonition type="danger" title="Additional Networking Options">
+  Refer to <a href="#network-connection">Robot Network Connection</a> for alternative networking connections.
+</Admonition>
+

components/husky_a300/husky_a300_amp_networking_basic.mdx

@@ -0,0 +1,16 @@
+### Confirming That OutdoorNav Software Is Functioning
+
+Husky AMP includes OutdoorNav Software, which allows the robot to be operated autonomously.
+Follow the steps below to confirm that OutdoorNav Software is functioning.
+
+1. [Connect to Web UI](/docs_outdoornav_user_manual/quick_start#connecting_to_web_ui)
+1. [Check camera views](/docs_outdoornav_user_manual/quick_start#checking-camera-feeds)
+1. [Check system status](/docs_outdoornav_user_manual/quick_start#checking-system-status)
+1. [Check GPS RTK fix](/docs_outdoornav_user_manual/quick_start#checking-gpt-rtk-fix)
+1. Complete system configuration:
+   1. [Load map tiles](/docs_outdoornav_user_manual/quick_start#loading_map_tiles)
+   1. [Set dock location](/docs_outdoornav_user_manual/quick_start#set-dock-location), if a dock is included with your system
+1. [Create your first map](/docs_outdoornav_user_manual/quick_start#create-your-first-map)
+1. [Create your first mission](/docs_outdoornav_user_manual/quick_start#create-your-first-mission)
+1. [Execute your first mission](/docs_outdoornav_user_manual/quick_start#execute-your-first-mission)
+