"This is resolved. I guess its really a Mission Planner issue. As of Plane 3.8, a new param ASPD_TYPE was added to select type. MP defaults to one type of sensor, in fact, it does not even allow NO SENSOR, although a 0 in ASPD_TYPE is what is needed…"
I just installed 3.8 on a pixhawk without AS sensor and was surprised to find that Airspeed (synthetic since I have no sensor) was not being reported over Mavlink to my OSD....I am pretty sure that on a 3.4 APM system I had, it was being reported…
"no, I dont want an older version of MP...I want arduplane hex for APM ver 2.78b or 3.0....MP will not allow you to download ANY plane firmware for APM other than 3.4"
I understand that APM is no longer supported, but my 2.78b system was flying great on my miniTalon on an APM FC....but then I had to replace the FC when it was destroyed accidentally when installing some new lighting on the plane ....and I find now…
"Yes, use compass is enabled....as I said, everything was working fine on previous releases and I transferred all parameters to new controller....except, of course, reintializing the acc offsets...the compass offsets are the same as before, because…"
I have been flying my APM miniTalon succesfully for a long time on AP3.0.1....recently I had to replace the APM and reflash....unfortunately, MP will only load 3.4 firmware....the problem is that with this firmware MAG_ENABLE is not longer…
"well almost...the tumble works now...almost...as it pass 90deg, yaw flips also since we are in earth frame in stabilized modes...so it starts to correct the yaw as the tumble goes 90 to -90 ...winds up a little cocked...I tried to fix it by setting…"
"Got it working....thanks!...really have to think thru how the roll and pitch are varying as you progress thru the tumble so as to let the flight controllers take over at the right point...got some interesting never ending tumbles to earth today…"
"Thinking back through what I saw, I think that the pitch flip is stopping in all flight modes at inverted...in STAB it then rolls out upright and is facing 180deg from start...in ACRO there is no leveling so it just stays inverted and falling for…"
"Leonard, I have a bit of a unique situation...I have an AIOP V2 board...the latest stable port to that board from Arducopter is 3.0.1...it flies well and I am NOT using a GPS (an FPV miniquad for bashing!)....
but...1) I wanted a true ACRO…"
Running 3.0.1 on a micro quad and want to confirm that its okay to run it WITHOUT a GPS....anything that I need to change in Params...like in the AHRS section? I see references to GPS weighting....should I set that to 0?I want to save the space and…
Since neither Andropilot nor Droidplanner is capable of reading a mission text file without having issues with commands each program doesnt recognize because of being out of date or having a bug...wouldn't it be nice if some Android programmer out…
"Update, just to check...I reprogrammed the BT module to 115K for MultiWii...hooked it up to an old MultiWii board...ran the Multiwii config tool from my phone...connected and transferred setting, acc data real time, etc....verifying that the BT…"