Mirrors_Framework/ODrive
1
0
Fork 0
mirror of https://github.com/odriverobotics/ODrive.git synced 2026-09-25 19:13:39 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update troubleshooting.md

Browse Source
This commit is contained in:
Oskar Weigl
2018-07-24 16:25:03 -07:00
committed by GitHub
parent b9237bf4ed
commit 5bee2a2199
1 changed files with 1 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/troubleshooting.md
+1 -5
View File
@@ -4,7 +4,6 @@
If your ODrive is not working as expected, run `odrivetool` and type `hex(<axis>.error)` <kbd>Enter</kbd> where `<axis>` is the axis that isn't working. This will display a [hexadecimal](https://en.wikipedia.org/wiki/Hexadecimal) representation of the error code. Each bit represents one error flag.
<details><summary markdown="span">Example</summary><div markdown="block">
Say you got this error output:
```python
In [1]: hex(odrv0.axis0.error)
@@ -13,12 +12,9 @@ Out[1]: '0x6'
Written in binary, the number `0x6` corresponds to `110`, that means bits 1 and 2 are set (counting starts at 0).
Looking at the reference below, this means that both `ERROR_DC_BUS_UNDER_VOLTAGE` and `ERROR_DC_BUS_OVER_VOLTAGE` occurred.
The axis error may say that some other component has failed. Say it reports `ERROR_ENCODER_FAILED`, then you need to go check the encoder error: `hex(<axis>.encoder.error)`.
</div></details>
There is a slight chance that the values here are out of sync with the actual firmware. To be completely sure, check the linked definition in the source code.
The axis error may say that some other component has failed. Say it reports `ERROR_ENCODER_FAILED`, then you need to go check the encoder error: `hex(<axis>.encoder.error)`.
* Axis error flags defined [here](../Firmware/MotorControl/axis.hpp).
* Motor error flags defined [here](../Firmware/MotorControl/motor.hpp).