Difference between revisions of "Troubleshooting"
From Pengatom Robotics Wiki
(Created page with "== Q) I receive the following error when trying to launch a project or utility: == > [Dynamixel Monitor for DARwIn v1.00] > Fail to open port > Arbotix Pro is used by anoth...") |
(→Q) I receive the following error when trying to launch a project or utility:) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Q) I receive the following error when trying to launch a project or utility: == | == Q) I receive the following error when trying to launch a project or utility: == | ||
| − | + | Fail to open port | |
| + | Arbotix Pro is used by another program or do not have root privileges. | ||
| − | + | '''A)''' | |
| + | This is either a permissions issue, or the Subcontroller comm port (/dev/ttyUSB0) is in use or otherwise disconnected. Ensure you are using `sudo` prior to launching project executables, file permissions are set correctly, and that no other programs are currently attached to the Subcontroller comm port. | ||
| − | + | If all of these conditions are met, check /dev/ for the correct comm port assignment (/dev/ttyUSB0) of the subcontroller: | |
| − | + | $ ls /dev/ | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | If all of these conditions are met, check /dev/ for the correct comm port assignment (/dev/ttyUSB0) of the subcontroller: | ||
== Q) dxl_monitor `scan` is coming back with ID result 'Fail` == | == Q) dxl_monitor `scan` is coming back with ID result 'Fail` == | ||
Latest revision as of 10:47, 16 March 2017
Q) I receive the following error when trying to launch a project or utility:
Fail to open port Arbotix Pro is used by another program or do not have root privileges.
A) This is either a permissions issue, or the Subcontroller comm port (/dev/ttyUSB0) is in use or otherwise disconnected. Ensure you are using `sudo` prior to launching project executables, file permissions are set correctly, and that no other programs are currently attached to the Subcontroller comm port.
If all of these conditions are met, check /dev/ for the correct comm port assignment (/dev/ttyUSB0) of the subcontroller:
$ ls /dev/
