Installation Issues
Issue | Cause | Solution |
Permission denied or File Not Found or 404 or similar | Out of disk space | This error can happen when you have a small SD card. Check the space left by using |
Unable to find file/404 | Most likely the internet connection is down, check you are connected to the internet by typing in a terminal If your connection is fine, check that the command used to get the repo from GitHub is correct. If there is still a problem it might be an issue with the Linux repositories, try | |
Unable to write to given location | Try running the commands using sudo in the terminal window instead. | |
Unable to locate package | No internet connection | Most likely the internet connection is down, check you are connected to the internet by typing in a terminal |
Packages aren't up to date | Make sure your Raspberry Pi is up to date, try | |
PiBorg logo is missing from the Desktop shortcut, but text is present | Desktop needs a refresh | Try restarting your Raspberry Pi to refresh the desktop. |
Use Issues
Issue | Cause | Solution |
Motor spins when I am not running code | Wiring issues | Double check all connections are correct. If you're following an example, refer back to the images to confirm your wiring. |
Robot motor runs backwards | Motor wired backwards | Swap the wires connected to M+ and M- to reverse the running direction of the motor. |
Motor does not work when sent commands | Errors during Init() | Try running the following short script:
Ensure there are no errors present when initialising the Diablo. Double check wiring is correct before moving onto the EPO check below. |
Jumper not connected across the two pin EPO/safety switch. | Try running the following short script:
If this prints
If this still doesn't work, try the above script with two additional lines:
If this prints Otherwise the most likely cause for this is a wiring problem, double check all the connections as shown on the Getting Started page. | |
GetDriveFault() returns True | Under-voltage (low power) | Faults may indicate power problems, such as under-voltage (not enough power), and may be cleared by setting a lower drive power. If a fault is persistent, it repeatably occurs when trying to control the board, this may indicate a wiring problem such as:
Faults will self-clear, they do not need to be reset, however some faults require both motors to be moving at less than 100% to clear. The easiest way to check is to put both motors at a low power setting which is high enough for them to rotate easily, such as 30% Note that the fault state may be true at power up, this is normal and should clear when both motors have been driven. If there are no faults but you cannot make your motors move check GetEpo to see if the safety switch has been tripped. For more details on correct wiring check the Getting Started Guide and double check the wiring instructions. |
Permission denied | Logged in without sufficient permissions | It is likely that the user you are currently logged in with does not have permission to use the I²C driver, try running the same command with sudo, e.g. If that resolves the issue then you can add the user to the i2c group with: |
| Running a GUI via SSH | This script can only be run in the Raspbian Desktop or an environment with a GUI. |
Diablo not found error | Board incorrectly wired or issue with cables | You should see the boards I²C address if you run the following from a terminal running Python:
If no boards are found check that the Diablo is attached correctly as shown on the Getting Started Guide. If a board is shown then set the I²C address to the shown value before calling Init(), e.g.
|
Python says it cannot find the Diablo module | diablo.py library missing from folder or path | Make sure the diablo.py module file is present in your working directory. If you still have a problem you can manually add the correct folder to the Python path using the following at the start of your script:
|
Comments
Leave a Comment
Leave a Reply