I have an MD22 driver that I am trying to use with i2c in conjunction with an Arduino board. I am getting some very odd results and I think my driver board is no longer functioning.
I have used my own code as well as the sample code at http://www.robot-electronics.co.uk/htm/ ... r%20Driver and I can't seem to get a response from the board. Instead, when I read the i2c bus I am seeing the last thing I wrote to it. For example, if I wrote a 0x07 to the bus to read the version register, the next time I read the bus it will return 0x07.
When I first got the board I was using it with RC control and it worked fine, however now it doesn't seem to respond to RC control either so I guess it is toast? There is no obvious damage to any of the components or any scorching -- the board is very clean, but very unresponsive. How would I go about identifying the problem? If the board is completely unresponsive like this it's most likely an issue with the PIC, right? Is there any way I can check individual components to see if they are working? If the PIC is toast is there a way to either replace it or use an external source (like the Arduino) to drive the h-bridge? Any insight into this issue is greatly appreciated.