pushed _build folder for review

docs/reStructuredText/_build/html/.buildinfo

@@ -0,0 +1,4 @@
+# Sphinx build info version 1
+# This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
+config: 8b85c9846c0b4107ef4d52be5bee233a
+tags: 645f666f9bcd5a90fca523b33c5a78b7

docs/reStructuredText/_build/html/_panels_static/panels-variables.06eb56fa6e07937060861dad626602ad.css

@@ -0,0 +1,7 @@
+:root {
+--tabs-color-label-active: hsla(231, 99%, 66%, 1);
+--tabs-color-label-inactive: rgba(178, 206, 245, 0.62);
+--tabs-color-overline: rgb(207, 236, 238);
+--tabs-color-underline: rgb(207, 236, 238);
+--tabs-size-label: 1rem;
+}

docs/reStructuredText/_build/html/_sources/analog-input.rst.txt

@@ -0,0 +1,12 @@
+================================================================================
+Analog Input
+================================================================================
+
+Analog inputs can be used to measure voltages between 0 and 3.3V. 
+ODrive uses a 12 bit ADC (4096 steps) and so has a maximum resolution of 0.8 mV. 
+A GPIO must be configured with :code:`<odrv>.config.gpioX_mode = GPIO_MODE_ANALOG_IN` before it can be used as an analog input. 
+To read the voltage on GPIO1 in odrivetool the following would be entered: :code:`odrv0.get_adc_voltage(1)`.
+
+Similar to RC PWM input, analog inputs can also be used to feed any of the numerical properties that are visible in :code:`odrivetool`. 
+This is done by configuring :code:`odrv0.config.gpio3_analog_mapping` and :code:`odrv0.config.gpio4_analog_mapping`. 
+Refer to :ref:`RC PWM <rc-pwm-doc>` for instructions on how to configure the mappings.

docs/reStructuredText/_build/html/_sources/ascii-protocol.rst.txt

@@ -0,0 +1,180 @@
+.. _ascii-protocol:
+
+================================================================================
+ASCII Protocol
+================================================================================
+
+.. contents::
+   :depth: 1
+   :local:
+
+Sending Commands
+-------------------------------------------------------------------------------
+
+ * **Via USB:**
+    * **Windows:** Use `PuTTY <https://www.chiark.greenend.org.uk/~sgtatham/putty/>`_ to manually send commands or open the COM port using your favorite programming language 
+    * **Linux/macOS:** Run :code:`/dev/tty*` to list all serial ports. The ODrive will show up as :code:`/dev/ttyACM0` (or similar) on Linux and :code:`/dev/tty.usbmodem[...]` on macOS. 
+      Once you know the name, you can use :code:`screen /dev/ttyACM0` (with the correct name) to send commands manually or open the device using your favorite programming language. 
+      Serial ports on Unix can be opened, written to and read from like a normal file.
+ * **Via UART:** Connect the ODrive's TX (GPIO1) to your host's RX. Connect your ODrive's RX (GPIO2) to your host's TX. See :ref:`UART <uart-doc>` for more info.
+    * **Arduino:** You can use the `ODrive Arduino library <https://github.com/madcowswe/ODrive/tree/master/Arduino/ODriveArduino>`_ to talk to the ODrive.
+    * **Windows/Linux/macOS:** You can use an FTDI USB-UART cable to connect to the ODrive.
+
+The ODrive does not echo commands. That means that when you type commands into a program like :code:`screen`, the characters you type won't show up in the console.
+
+.. admonition:: Arduino
+
+   There is an Arduino library that gives some examples on how to use the ASCII protocol to communicate with the ODrive. 
+   Check it out `here <../Arduino/ODriveArduino>`.
+
+Command Format
+-------------------------------------------------------------------------------
+
+The ASCII protocol is human-readable and line-oriented, with each line having the following format:
+
+Format: :code:`command *42 ; comment [new line character]`
+
+ * :code:`*42` stands for a GCode compatible checksum and can be omitted. If and only if a checksum is provided, the device will also include a checksum in the response, if any. 
+   If the checksum is provided but is not valid, the line is ignored. The checksum is calculated as the bitwise xor of all characters before the asterisk (`*`). 
+   Example of a valid checksum: :code:`r vbus_voltage *93`.
+ * comments are supported for GCode compatibility
+ * the command is interpreted once the new-line character is encountered
+
+
+.. _acsii-cmd-ref:
+
+Command Reference
+-------------------------------------------------------------------------------
+
+.. _motor_traj-cmd:
+
+Motor Trajectory
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Format: :code:`t motor destination`
+
+* :code:`t` for trajectory.
+* :code:`motor` is the motor number, :code:`0` or :code:`1`.
+* :code:`destination` is the goal position, in [turns].
+
+Example::
+   
+   t 0 -2
+
+For general moving around of the axis, this is the recommended command.
+
+This command updates the watchdog timer for the motor. 
+
+Motor Position
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For basic use where you send one setpoint at at a time, use the :code:`q` command.
+
+Format: :code:`q motor position velocity_lim torque_lim`
+
+* :code:`q` for position.
+* :code:`motor` is the motor number, :code:`0` or :code:`1`.
+* :code:`position` is the desired position, in [turns].
+* :code:`velocity_lim` is the velocity limit, in [turns/s] (optional).
+* :code:`torque_lim` is the torque limit, in [Nm] (optional).
+
+Example:: 
+
+   q 0 -2 1 0.1
+
+If you have a realtime controller that is streaming setpoints and tracking a trajectory, use the :code:`p` command.
+
+Format: :code:`p motor position velocity_ff torque_ff`
+
+* :code:`p` for position
+* :code:`motor` is the motor number, :code:`0` or :code:`1`.
+* :code:`position` is the desired position, in [turns].
+* :code:`velocity_ff` is the velocity feed-forward term, in [turns/s] (optional).
+* :code:`torque_ff` is the torque feed-forward term, in [Nm] (optional).
+
+Example::
+   
+   p 0 -2 0 0
+
+This command updates the watchdog timer for the motor. 
+
+.. note:: If you don't know what feed-forward is or what it's used for, simply omit it.
+
+Motor Velocity
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Format: :code:`v motor velocity torque_ff`
+
+* :code:`v` for velocity
+* :code:`motor` is the motor number, :code:`0` or :code:`1`.
+* :code:`velocity` is the desired velocity in [turns/s].
+* :code:`torque_ff` is the torque feed-forward term, in [Nm] (optional).
+
+Example::
+   
+   v 0 1 0
+
+This command updates the watchdog timer for the motor.
+
+
+Motor Current
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Format: :code:`c motor torque`
+
+* :code:`c` for torque
+* :code:`motor` is the motor number, :code:`0` or :code:`1`.
+* :code:`torque` is the desired torque in [Nm].
+
+This command updates the watchdog timer for the motor. 
+
+
+Request Feedback
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+imput format: :code:`f motor`
+
+response format: :code:`pos vel`
+
+* :code:`f` for feedback.
+* :code:`pos` is the encoder position in [turns] (float).
+* :code:`vel` is the encoder velocity in [turns/s] (float).
+
+Update Motor Watchdog
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Format: :code:`u motor`
+
+* :code:`u` for /u/pdate.
+
+* :code:`motor` is the motor number, :code:`0` or :code:`1`.
+
+This command updates the watchdog timer for the motor, without changing any
+setpoints. 
+
+Parameter Reading/Writing
+-------------------------------------------------------------------------------
+
+Not all parameters can be accessed via the ASCII protocol but at least all parameters with float and integer type are supported.
+
+ * Reading format: :code:`r [property]`
+
+   * :code:`property` name of the property, as seen in ODrive Tool
+   * response: text representation of the requested value
+   * Example: :code:`r vbus_voltage` => response: :code:`24.087744`
+
+ * Writing format: :code:`w [property] [value]`
+
+   * :code:`property` name of the property, as seen in ODrive Tool
+   * :code:`value` text representation of the value to be written
+   * Example::
+
+         w axis0.controller.input_pos -123.456
+
+System Commands
+-------------------------------------------------------------------------------
+
+* :code:`ss` - Save config
+* :code:`se` - Erase config
+* :code:`sr` - Reboot
+* :code:`sc` - Clear errors