I'm currently working on a Bachelor's thesis about playing soccer with Balanduinos. Recently a problem occured when my robots are acting differently on the same code sequence.

My main question is, can the Balanduino hardware take any damage from losing its balance and falling on the floor?Here is a link for two videos showing the difference from two robots and how inbalanced one of them is, it twitch back and forth a lot when trying to find back to its balance position. The sequence is to drive some forward, turn, forward again and then stop. Notice both the difference in balancing and how one of the robots is driving a shorter distance.

Last week it could find and follow a ball smoothly with a Pixy connected but today with the very same code it sends too large signals and just twitch back and forth and loses its balance.

At almost every start of the broken robot it sends out the long beep, which means it resets the EEPROM, could anything been damaged in the memory?

Motors have been recalibrated.

While connecting with the Bluetooth-dongle to my phone and reading the graphs I get some strange values from the gyro. It starts at 180 where also the Kalman and accelerometers are ranged around when standing still. The gyro value is slowly growing from 180 to 360 during 20 seconds before it jumps down to 180 again and restarts that cycle. The robot gets much more instable as the gyro value gets higher and then gets somewhat stable again when the value jumps down to 180 again.

I don't know how to proceed further in my search of what could be wrong, what should I try?

The gyro drift you are seeing is likely caused by the calibration routing getting wrong values because the Balanduino is not at rest. I would recommend putting the Balanduino on its side when turning it on.

PS: Sorry for the long delay in my response. I must have missed you post in my inbox.