May 6, 2020
I hope you can help me with my problem.
I got the robot half a year ago, and it worked fine right away, making some little programs with EdBlocks which he executed. After some weeks without being used, he doesn’t execute programs anymore. The batteries are fine (LEDs staying on), no network problems, the same hardware setup as before.
When I press the record button and send him a program via EdBlocks, I actually get the “modem” noise as if the compiled code is being transmitted. I also get the “success” sound. However, when I press the play button afterwards, he doesn’t actually do anything, regardless of the specific program (even simple one-block programs where he only has to drive forward for a second).
Thanks in advance for your help!
September 2, 2019
We are aware of a common scenario that may match what you’re experiencing.
If the batteries are running low, Edison will still turn on okay, but when it attempts to drive will respond with a beep and not execute the program, which sounds a lot like what you describe experiencing. This is unexpected for many users, who expect the robot would not work at all if the battery is low.
To rule out that the issue is being caused by low batteries, please replace all four batteries with new alkaline-based disposable batteries or nickel metal hydride rechargeable batteries.
Also please make sure the batteries you are using are not “Heavy Duty” or “Super Heavy Duty” (carbon zinc based) as these types of batteries can provide insufficient power (even when brand new), resulting in the same symptoms.
If this does not resolve the issue for you, then there may be an issue with your specific robot, in which case please send us a request in our contact us form – https://meetedison.com/edison-robot-support/contact-us/ – so that we can provide specific advice for you.