Hi Andy, This happens indeed when the e-puck is flooding the BT socket. To solve this cleanly, you can upload your new controller using an ICD2 from Microchip. Another solution that I use very often (less nice, but faster) : just repeat the operation a lot of times. The game is to press reset just when you start sending the controller. Don't hesitate resetting the robot a lot :-) With some experience I manage to send the controller in 10 secs.
In the future, when you write a controller, simply put a wait, so that the robot by default is not sending data through bluetooth, but rather waits for your command to start his operations. Cheers, alex. On Thu, 7 Feb 2008 12:37:27 +0000 "Andy Guest" <[EMAIL PROTECTED]> wrote: > What I day I'm having with these little things ! > > One of my e-pucks is behaving oddly now. When I try to use the tiny > bootloader to upload a hex file to the it the bootloader seems to > automatically connect to the puck without me pressing the reset button. The > orange light comes on on the e-puck but doesn't flash. If I preset the reset > button the bootloader fails with a write error, if I don't press the reset > button the orange led eventually goes off and the bootloader eventually > stops responding. It seems like the epuck is trying to communicate as soon > as it is switched on and the bootloader never gets chance to upload the > code. Powering down, reseting the epuck, removing the battery, even trying > to choose other programs from the e-puck selector doesn't change anything. > > How do I get the e-puck working again ? > > > Thanks, > Andy _______________________________________________ E-puck-user mailing list [email protected] https://mail.gna.org/listinfo/e-puck-user
