-
Notifications
You must be signed in to change notification settings - Fork 91
status errors
JamesNewton edited this page Jul 22, 2019
·
12 revisions
- Most oplets will return a [status](status data) with a standard error code (see list below)
- [Read From Robot](read from robot) and [Write To Robot](write to robot) deal with file IO and so return the standard Linux error numbers
- The Monitor can override any of the above, replacing the status error with a number in the 600-699 range.
| No | Description |
|---|---|
| 0 | No error |
| 1 | Unknown Most often returned when the requested oplet or sub command is not known. This is most likely to occur because the firmware on the robot is out of date, and it should be updated. |
| 665 | Boundary error A joint was commanded to move past the boundary set for it, [Read](read from robot) the errors.log file for details. There are high and low boundary settings for each joint: J#Boundry(High |
| 666 | Monitor error Raw encoder position or velocity exceeded, [Read](read from robot) the errors.log file for details. If the error was velocity related, the robot will be switched into open loop mode from any closed loop mode. |
To search the Wiki, use the main search box in the black bar at the top, then select WiKi to filter the results or go to https://github.com/HaddingtonDynamics/Dexter/search?type=Wikis&q= and then add your search terms to the end of the URL.
To report errors, or request additional data, please chat with us on discord and/or raise a new issue