Unable to connect to correct firmwa

[dirk123]

Hi,

I assembled my Raspberry Pi Camera robot but it does not work properly. Sometimes if I start the robot it is partially working (pan/tilt works always, camera does not work right now but can be something else, one of the motors are working). If I start the robot the next time nothing works and this is the log. It seems to me that the firmware was not installed correctly on the first start and now it sometimes tries to install the firmeware again but that does not work properly. Does anyone please have a suggestion? Is there a way to just reset the firmware manually?

Best,
Dirk

DEBUG:tornado.general:sockjs.tornado will use json module
INFO:root:Starting web server...
INFO:root:Read 0X0 0.0
INFO:root:Expected 0XACED 0.38
INFO:root:Unable to connect to correct firmware, uploading...
INFO:root:No file copy needed
DEBUG:root:Building sketch in dir /root/.ino_uploader/mini_driver_firmware
DEBUG:root:Trying to upload /root/.ino_uploader/mini_driver_firmware/.build/atmega8/firmware.hex
DEBUG:root:uploadResult = 0
INFO:root:Read 0X0 0.0
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 6.52ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.57ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.62ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.03ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 2.34ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 2.40ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.47ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.37ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.46ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.62ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.37ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.38ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.56ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.33ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.30ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.33ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.30ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.54ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.16) 3.49ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.57ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.97ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.41ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.40ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.34ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.49ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.87ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.32ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.45ms
INFO:tornado.access:200 GET / (192.168.42.16) 52.23ms
INFO:tornado.access:200 GET /css/modal.css (192.168.42.16) 34.23ms
INFO:tornado.access:200 GET /css/style.css (192.168.42.16) 5.75ms
INFO:tornado.access:200 GET /js/jquery.joystick.js (192.168.42.16) 8.21ms
INFO:tornado.access:200 GET /images/ajax-loader.gif (192.168.42.16) 8.04ms
INFO:tornado.access:200 GET /js/sockjs-0.3.min.js (192.168.42.16) 31.07ms
INFO:tornado.access:200 GET /js/jquery.js (192.168.42.16) 102.14ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.16) 2.52ms
WARNING:tornado.access:404 GET /favicon.ico (192.168.42.16) 18.23ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 2.45ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 2.49ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 2.40ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.33ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.30ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.72ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.30ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.26ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.27ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.72ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.39ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.74ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.50ms
INFO:tornado.access:200 GET /logs.html (192.168.42.16) 7.78ms
INFO:root:SockJS connection closed
INFO:tornado.access:304 GET /js/sockjs-0.3.min.js (192.168.42.16) 4.35ms
INFO:tornado.access:304 GET /js/jquery.js (192.168.42.16) 4.00ms
INFO:tornado.access:200 GET /robot_control/info (192.168.42.16) 3.40ms

[Alan]

Hi there,

Welcome to the forums. Apologies that I've taken so long to reply to this post.

I think perhaps that the bootloader on the mini driver may be corrupt. I'm hoping that your order will have contained a 'programming' cable for the mini driver with 4 built in resistors that you can use to fix the mini driver using the instructions on this page.

If you don't have this cable, or have trouble following the instructions then please let me know, and I'll provide more help.

Apologies that you're experiencing this problem, it seems to be a fairly intermittent problem with the mini driver, which not everyone encounters, but it is annoying when it does happen.

Regards

Alan

[dirk123]

Hey Alan,

thanks for the instructions. However, in the meanwhile I was able to "fix" the problem. I formatted the SD card and transferred the operating system again to the SD card because I hoped that on the first start it will flash the bootloader again. And it worked, the problem vanished. Maybe this dirty fix can help other users, too.

The not moving wheel was due to a broken solder joint. The camera did not worked because amazon delivered a broken one... I sent it back and have a working one now.

My robot is fully working now

Next project: Adding infrared sensors and making the robot autonomous The robot is really a very nice toolkit.

[dirk123]

If someone has the same problem:

After running the robot for some days the problem returned.

This time I did not want to reinstall a new operating system because I had already installed a lot of stuff. However, I soldered four cables with a 1K resistor and tried Alan's idea. It worked but I needed to unplug the pan/tilt kit and the motors from the board before.

Dirk