I'm brand new to m3pi and XBee. I've so far been very impressed with how easy it has been to get going, so kudos for that. I want to be able to control the robot from a computer. As per the user manual I do not have the mbed socketed, and so i shorted the three jumpers beside the XBee socket. As per Digi documentation i set up the XBees with API firmware using the XCTU software. I also confirmed that the XBees can communicate. In both cases the serial was set to 115200 8N1.
There are two related problems. First, when i turn the m3pi on, it beeps twice and displays "bad cmd 75", and then beeps twice again and says "bad cmd 73". Second, when i send a wireless command, i get the "bad cmd" message but the byte that i sent is not the byte that gets displayed. For example, if i send a 0xb7, it says "bad cmd 32". Some bytes cause the robot to react (move forward, etc) but are always associated with an error message.
I'm thinking that maybe the XBee is forwarding a frame to the m3pi serial slave and the error message displayed is the checksum or something. But i don't know why it would be doing this, and i can't find any clues as to how to fix it. Can anyone help?