1) This is due to a conflict with the FTDI chip when the USB cable is plugged in. It is not an issue in the field, when the board is powered the normal way, with the ESC.
2) If this troubles you, we will be releasing instructions on how to modify the board (cutting a trace and soldering a wire jumper) to avoid it. The next batch of boards will have this fixed.
3) Needless to say, if your IMU shield is on the bottom and you're using the reset button on the APM board, there is no problem.
4) Remember that when you upload code to APM, Arduino automatically resets the board, so no manual reset is required. So you shouldn't have to use this button in normal operations anyway.
Replies
I believe I am having the same problem. I want to do a little further investigation first. I did notice that if I power up the APM/IMU with the slider switch away from the DIP switches, it attempts to read flight data but still disconnects.
I read somewhere you can do everything in the CLI that you can do in the configurator. Where do you set PIDs in the CLI?
Still no good explanation for this behavior.............
This problem only exists with the configurator. Using standard ArduCopter code and it's configurator, AeroQuad code and it's configurator, or my modifed code with the AeroQuad configurator. All behave the same way. And all work as expected with the Arduino serial monitor.
I need to get a scope out, but I'm beginning to wonder if the DTR signal timing is different on the Arduno serial monitor vs the configurators?
John
chris.
I'll be curious to see the fix when its posted.
chris.