RPi Camera Robot issues - Please help!
Posted: Tue Sep 29, 2015 10:56 am
Hi, I sent a message yeterday about my Raspberry Pi Camera Robot not working (no movement of the camera pan/tilt or the wheels, but the camera stream works fine). I have since gone onto the log (192.168.42.1/logs.html - *) and realised the Pi is not communicating with the mini driver. Also from reading other threads, I see that I should expect to see a blue light flash when I power on the mini driver, however I do not see this - it is just red the whole time.
Please help me ASAP. I am a Secondary school teacher and had promised sessions to primary school students this week where they can come in and move the robot around an obstacle course and don't want to keep dissapointing. This is the reason we purchased the robot. It is so frustrating because it was working absolutely fine on monday morning, then just decided to have no life in its motors the next time powered on and nothing was changed at all.
*Here is the log:
Main Log
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 /logs.html (192.168.42.15) 48.84ms INFO:tornado.access:200 GET /js/sockjs-0.3.min.js (192.168.42.15) 23.50ms INFO:tornado.access:200 GET /js/jquery.js (192.168.42.15) 140.91ms WARNING:tornado.access:404 GET /favicon.ico (192.168.42.15) 26.72ms INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.65ms
Ino Build Log
Please help me ASAP. I am a Secondary school teacher and had promised sessions to primary school students this week where they can come in and move the robot around an obstacle course and don't want to keep dissapointing. This is the reason we purchased the robot. It is so frustrating because it was working absolutely fine on monday morning, then just decided to have no life in its motors the next time powered on and nothing was changed at all.
*Here is the log:
Main Log
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 /logs.html (192.168.42.15) 48.84ms INFO:tornado.access:200 GET /js/sockjs-0.3.min.js (192.168.42.15) 23.50ms INFO:tornado.access:200 GET /js/jquery.js (192.168.42.15) 140.91ms WARNING:tornado.access:404 GET /favicon.ico (192.168.42.15) 26.72ms INFO:tornado.access:200 GET /robot_control/info (192.168.42.15) 3.65ms
Ino Build Log