Did I fry my MD25?

Help & Support Robot Parts
1

I think I may have fried my MD25…is there some way to tell? I have been running the MD25 in I2C mode with an Arduino Uno and LCD03. I didn’t know I had to pay attention to the jumper arrangement until just about a week ago.

Before that, I had been running the MD25 with both jumpers attached (the way it was shipped to me), and I ran both the Series and I2C configurations. Now when I run this code, robot-electronics.co.uk/files/arduino_md25_i2c.ino, the program stops after printing “MD25 Example V:” which is on line 39, right before the command “byte softVer = getSoft();”

So, evidently the program is encountering problems when it tries to call the software from the MD25. Would setting the improper jumpers fry the MD25? When I first setup the devices, I was running them in Serial mode with both jumpers attached. It ran okay for the first few tries, but then it eventually stopped. How can I tell if the MD25 is fried? Would running these programs with the jumpers in the wrong setup cause my MD25 to fry?

2

The controller does not smell or look burnt. It did not spark or release smoke.

Well, some good news…I hooked up the circuit in Series mode, and I got the motors to turn, but without any LCD readout. The motors turn for about 4 seconds, so I am still trying to figure out how to control their run time.

3

The Serial/I2C jumpers have nothing to do with the controller power management, so they would not make it fry.

It is more likely that you have some communication issues if you did not overloaded the controller. Does it smell or look burnt? Did it spark ot release some smoke?