Dawn Robotics Forum

Hi
First of all ; im a french 17 years old student in his last school year so sorry for my english

I did the whole tutorial about the raspberry robot camera . But i got a final problem
when i tried to launch the server i got this error .
@raspberrypi ~/sockjs-tornado/raspberry_pi_camera_bot $ sudo ./robot_web_server.py
sockjs.tornado will use json module
Starting web server...
Read 0X0 0.0
Expected 0XACED 0.29
Unable to connect to correct firmware, uploading...
No file copy needed
Building sketch in dir /root/.ino_uploader/mini_driver_firmware
Building of sketch was unsuccessful
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 505, in run
self.__target(*self.__args, **self.__kwargs)
File "./robot_web_server.py", line 71, in createRobot
r = robot_controller.RobotController( robotConfig )
File "/home/pi/sockjs-tornado/raspberry_pi_camera_bot/robot_controller.py", line 60, in __init__
raise Exception( "Unable to connect to the mini driver" )
Exception: Unable to connect to the mini driver

I checked all connections and everything is at his place .
Im pretty novice with linux so maybe it's a simple problem
Thanks for answers
Valentin

Hi Valentin,

Welcome to the forum. Sorry for the delayed reply, and your english seems pretty good to me.

Looking at the logs, everything is proceeding as it should, apart from the line 'Building of sketch was unsuccessful' which is a problem.

Can you try launching the webserver again? If the same problem occurs can you send me the contents of the file /tmp/ino_build_output.txt please?

Also, are you using an SD card image that you downloaded from our website, or one that you built yourself?

Regards

Alan

Hello,

I'd like to note I'm also having this exact problem. I should note though that I'm powering the dagu mini driver via the GPIO 5v pin and ground (instead of by battery, etc). I looked for the log file and found it, however, it was empty. Any ideas?

pi@raspberrypi ~/raspberry_pi_camera_bot $ sudo ./robot_web_server.py
sockjs.tornado will use json module
Starting web server...
Read 0X0 0.0
Expected 0XACED 0.31
Unable to connect to correct firmware, uploading...
No file copy needed
Building sketch in dir /root/.ino_uploader/mini_driver_firmware
Trying to upload /root/.ino_uploader/mini_driver_firmware/.build/atmega8/firmware.hex
done with autoreset

avrdude-original: AVR device initialized and ready to accept instructions

Reading | | 0% 0.00savrdude-original: error reading signature data for part "ATMEGA8", rc=-1
avrdude-original: error reading signature data, rc=-1
uploadResult = 0
Read 0X0 0.0
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 505, in run
self.__target(*self.__args, **self.__kwargs)
File "./robot_web_server.py", line 71, in createRobot
r = robot_controller.RobotController( robotConfig )
File "/home/pi/raspberry_pi_camera_bot/robot_controller.py", line 60, in __init__
raise Exception( "Unable to connect to the mini driver" )
Exception: Unable to connect to the mini driver


This is actually what mine is doing, very similar. Any ideas?

Hi Hiro,

Sorry for the delayed reply. It looks like the Pi can't communicate with the mini driver for some reason. A couple of things to try.

[list=][*]Can you make sure that the USB cable between the Pi and Mini Driver isn't loose?
[*]If that doesn't solve the problem, can you log into the Pi and tell me the result of running 'lsusb'?
[*]Can you check that when mini driver is powered on and you press the reset (rectangular white) button on the mini driver, that a blue light flashes?
[/list]

Also, which version of the Pi are you using? I've found that on start up new the Model B+ version of the Pi doesn't seem to be able to supply enough power to the mini driver and the servos. The symptons are the mini driver keeps on restarting, the blue light on the mini driver flashes, and any servos attached to the mini driver shake back and forth. The way to fix this is to add a battery pack on the mini driver, it can be small though (only 4xAA) if the Pi is powered from another supply.

Anyway, hopefully something here will be of help. Please let me know how you get on.

Regards

Alan

Doublechecked the connections, everything looks ok. I've sometimes noticed that "twitch" you talked about, where it seems to keep resetting. I'm powering it through battery now instead, (I've tried that on and off for some time also) still no luck.

lsusb outputs the following:

Code: Select all

Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 001 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light


The blue light DOES flash when I press the reset button, but anytime I try to write to it, it fails. It complains about a signature.

FYI, I'm using a Model B+.

I've been trying on and off all evening, and I can't seem to get it to accept any code via avrdude at all. I once received an error about a signature being 0x000000. After looking it up, I saw one place that claimed that meant it wasn't communicating with the board. I'm willing to try anything you suggest, but I'm starting to wonder if perhaps I have a bad board. I ordered this as part of the chassis kit from Dawn Robotics. Are there any options available to me to exchange boards if this turns out to be a bad board?

Hi Hiro,

Sorry you're having problems, and sorry for the delay replies.

It sounds like you might have a corrupted Arduino bootloader on the Mini Driver. This can prevent the upload of programs.

Do you have any experience of flashing Arduino bootloaders? You can do this either with a specialised programmer, or with another Arduino if you have one lying around. If neither of these are an option then we can replace your Mini Driver, but if we're able to get you to flash the board then obviously that would save you time.

Apologies for any inconvenience this is causing you.

Regards

Alan

Sounds like a replacement would be the best way to go. I sent you a PM, Alan.