Here's a bit of frustration that I just can't seem to figure out.
I was making great progress with my hexa and APM v2.4 and MP 1.1.48 -- no issues. Then I got a message in MP saying there was an upgrade so I clicked yes and got 1.1.54 installed. At that point I could no longer get MAVlink to connect to the MP in any tab other than "Firmware" and "Terminal".
I tried the "Firmware" tab and got another message about loading APM V2.5. Thinking this must be the problem I again answered YES and proceeded to get V2.5 loaded . Still can't connect to MP 1.1.54.
I went back and downloaded all of the MP 1.1.xx version from 48 thru 54 and began trying each one. I've found that I'm having no issues connecting/communcating through MP v1.1.50. Beyond that no dice.
I have tried this experiment with the 2011 version of the ftdi drivers as well as the "beta" 2012 driver version -- no difference.
One more data point ---- I cannot download to the APM1 from the arduino compiler at all.
So there you have the whole sad story. My question is does anyone have any idea what is going on here/? Right now I'd say it's not the APM1... but rather something that changed in the MP starting with V1.1.51 .
Any Ideas and suggestions would be appreciated....
TOM
Replies
can you try a few things.
1. make sure your rts on close is set in the com port properties.
2. in the planner > config > planner > untick reset apm on connect.
it sounds to me like a possible dtr issue. just need to get to the bottom of why.