Hey everyone
On my first bench test I made the wrong assumption that my receiver scales the input voltage. I have a 7.4V receiver pack hooked up to the receiver that’s hooked up to the AMP2. I then connected the AMP2 to the PC through USB. Initially everything seemed fine with light flashing. I continued to Mission Planner to set up the plane, although AMP2 fails to connect now.
It is still visible in the COM port and 3Dfix is solid so it does still get GPS lock. When I hit connect in Mission Planner the blue and red light (A, C) rapidly alternately flash for a couple of seconds and stop and the yellow TX and RX don’t flash. I can’t see any visible burn/scorch marks on the board.
Has anyone else supplied overvoltage to the board and is there a way to fix this?
Cheers!
Replies
Two main questions:
Are you using the correct serial speed in Mission Planner?
Are you using the APM with 7.4v plug-pack whilst also plugged into USB? - It is best not to do this, you could cause an overvoltage ground loop (where the potential difference between the ground and the two vcc is the killer, not the overvoltage itself.)
Also just check that the correct driver appears when the device is plugged in (in device manager in control panel.)
I would even go so far as to uninstall the device (whilst plugged in choose to uninstall and remove driver.) - next uninstall Mission Planner, re-install Mission planner using the latest MSI. then plug in the APM and see if it installs the correct driver and shows that COM port in MP...try from there and let us know.
if using USB speed should usually be 115200 default, if using xbee the default is 57600
Next option would also be to download arduino software and the ARDU of your choice (arduplane, copter, etc.) choose the Ardumega 2560 as board type, and try to upload the ARDU software to it (after choosing the correct serial port just like you would in Mission Planner.