For the life of me I can't get this thing to work. I reloaded the firmware since it would just turn on and both stat LED's would be lit. No matter what I do it won't turn the motors on.
I have it at 115200 and nothing. I get a ready on startup too. Whenever I send a command I get the command echoed back on the serial.
Even if I make the command too long, whatever I sent gets echoed back.
I am running a Arduino Mega and the motors have been tested.
I got the same experience with it as you do... And finally when I got it working, it kept shutting off because of the short initial current the motors draw.
I didn't I messed around with it for some hours, then threw it away.
I don't know how long it takes to your place, but from seeedstudio and to me (DK), it takes between 2 and 3 weeks, but a lot of that is also customs.
To control the motor driver I posted a link to, you use 4 digital pins to set the direction each motor will go, and then a PWM for each of them to set the speed they should run at.
MobileWill:
Did yours echo back what cmd you sent it?
Yes it did, along with whimpering about too much current being drawn.
The dual H-Bridge is using 6 pins yes, which might be many on an UNO, but for a mega (which I am using on my project too), it isn't an issue, unless you really fill it with sensors
What I also like about the driver, is that it responds a lot faster than the serial one, because you don't first compile a message to send to it, then the controller processes that message, then does what it was told (maybe), the simple driver is just doing what you set the controller's pins to. Can't be much faster than that.
I haven't tried pwm on other pins than the ones I am using, and the wires are soldered on now with heat shrink tubing, so I am not going to test if I can get it to work on other pins too.