Good Morning!
I woke up this morning and when booting up ground control I started getting the constant connect and then disconnect errors in ground control. I went to upgrade to firmware 1.10 but i’m getting the following error in the Arduino firmware updater. Is my Mega fried? Anyone else run into this and know how to resolve the issue?
Arduino: 1.8.5 (Windows 7), Board: “Arduino/Genuino Mega or Mega 2560, ATmega2560 (Mega 2560)”
Sketch uses 53666 bytes (21%) of program storage space. Maximum is 253952 bytes.
Global variables use 1867 bytes (22%) of dynamic memory, leaving 6325 bytes for local variables. Maximum is 8192 bytes.
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_getsync(): timeout communicating with programmer
An error occurred while uploading the sketch
This report would have more information with
“Show verbose output during compilation”
option enabled in File -> Preferences.
Tried following things suggested in the other thread without any luck. Guess my board might be fried? Any ideas? I’ve tried using both Mac and Windows to update the Firmware but i’m unable to connect.
I wouldn’t give up on that board quite yet tho! It seems like the board is having trouble connecting over USB but it might be worth just prodding it and trying things like unplugging the shield, unplugging the Arduino, restarting the computer and having a fresh go at it
Good Morning!
I tried everything and finally replaced the Mega 2560 and i’m no longer having issues with connecting. However, i’m now having issues with calibration again. I switched up my setup to connect from the top of the sprocket to the sled and it’s not centering up in the middle of the plywood like it would before.
Woah! I have not seen the motors extend different distances before. What do you see when you run the Actions -> Test Motors/Encoders? A lose connection could cause that kind of thing