4Borg issue

It sounds like something might be connected incorrectly.
The most likely reason the Raspberry Pi is powering off is that the 5V or 3.3V pins are getting connected to the GND pin.

Can you take a couple of photos of how things are currently wired so we can see?

Just to check does the LED on the PicoBorg Reverse come on when:

• The USB power has been disconnected
• The 9V battery is plugged in
• The switch on the 9V board is turned on

If it is then the BattBorg should be supplying 5V to the Raspberry Pi and the 4Borg should be working.

Given that the chassis is inverted it is quite possible that the + and - connections from the 9V board are also back-to-front.

If the LED is not coming on with the above list then the BattBorg is likely no supplying 5V to the Raspberry Pi.
Try removing the BattBorg from the PicoBorg Reverse and see if you are able to make the wheels turn.
You will need the 9V battery plugged in and the switch turned on along with the USB power attached to try this.

Is the speed slider fully to the right?

What does the Speeds line say when you press the various buttons?

It sounds like there may be another script running which is also setting the output speeds.

Are you running any other scripts via rc.local or crontab?

There is no test mode in the 4BorgFollowBall.py script.
When it is displaying the two numbers they are the speeds sent to the left and right drive.

Are you still running the WebUI script at the same time?
If you run two of the example scripts they will prevent each other working.

As the motors are not running I would recommend checking the drive is working manually.

First kill all any running Python scripts to make sure nothing is running:
sudo killall python

Second load up a python session from the 4Borg directory:
cd ~/4borg
python

Lift the 4Borg off the ground so the wheels can freely rotate

Now run these lines from python:

import PicoBorgRev
PBR = PicoBorgRev.PicoBorgRev()
PBR.Init()
PBR.SetCommsFailsafe(False)
PBR.ResetEpo()
PBR.SetMotor1(0.7)
PBR.SetMotor2(-0.5)
# At this stage both motors should be turning, but at slightly different speeds
print PBR.GetEpo()
print PBR.GetDriveFault()
print PBR.GetMotor1()
print PBR.GetMotor2()
PBR.MotorsOff()

Let us know if the motors moved and what the output from Python is.

If the motors did turn after that try the 4BorgFollowBall.py script again and see if it is now working.

What you need to do is create a window with a name for each image you wish to show like this:

cv2.namedWindow("red threshold", cv2.WINDOW_NORMAL)

This only has to be done once per window you need.

Now you can show an image on that window using the same name and passing the image like this:

cv2.imshow("red threshold", red)
cv2.waitKey(1)

If you want to draw the contours found on the image you will probably want to use the drawContours function:
http://docs.opencv.org/3.0-beta/modules/imgproc/doc/drawing_functions.ht...

What are the results from the previous test I asked you to run:
https://www.piborg.org/comment/4804#comment-4804

The important bit of information from this is that PBR.GetDriveFault() returns True.
This means the board is detecting a problem and refusing to power the motors.

The most likely explanation is that the battery is getting flat.
If you are using a rechargeable 9V try recharging the battery fully.
If you are using a non-rechargeable 9V try replacing it with a fresh battery.

If that does not help see the GetDriveFault returns True section on the troubleshooting page:
https://www.piborg.org/picoborgrev/troubleshoot