I have a Pixhawk with ArduPlane 3.2.3 on it that crashed. This combination of parameters and firmware has several hundred hours on it and in air crashes are rare ( sadly bad launches and landings are more common than I would like but they are user…
"I couldnt fix it on the pixhawk or on the receiver so I just bought the spiffy new DX6 controller which lets you re order the channels on the transmitter side of things. Its not the cheapest fix but at some point time wasted fighting with it is more…"
I have a pixhawk and it uses PPM so I cant just switch the wires from the receiver to the auto pilot and the dx6i cant re map the channels as far as I can tell.currently the input channels are mapped as follows transmitter > autopilotthrottle >…
"If your compass got loose then the plane's attitue estimation would be wildly wrong causing it to do all sorts of bad things. this could lead to a stall or a condition where it thinks it's pitched up and is actually pitched down so the auto pilot…"
"I have had the same thing happen to me with a Zephyr on the APM 2.6 running 2.7 something firmware. It doesnt happen every time but looking back at it i would say it happens maybe 10% or 20% of the time - never solved it though :("
I have noticed that sometimes mission planner assumes that I am using a copter when it is not connected to my plane. The little icon for the vehicle in the flight data tab briefly switches to a quad copter (before disappearing) and then there is no…
"When I upgraded from 2.76b to 2.78b it introduced a weird issue with auto landings. Is there a new landing parameter that I need to set? With 2.78 in normal flight the nav_pitch more or less tracks the alt_error and it does a good job maintaining…"
Data flash says this: FMT, 13, 51, TECS, ffffffffffff, h,dh,h_dem,dh_dem,sp_dem,sp,dsp,ith,iph,th,ph,dsp_dem I have no idea what most of those values mean and I cant find anything other than the arducopter data flash message explanation.
"I had to make my own cable with a transistor in there to amp the servo signal enough for CHDK to register it on the USB port. I recently upgraded to firmware 2.74b and my plane stopped logging CAM events. anyone know what log bitmask i need to start…"
I switched from V2.73 to 2.74b and in doing so, the LOG_BITMASK changed from 5 (fast attitude and GPS) to 69 (fast attitude, GPS and MODE) without me noticing. long story short i did a few flights and it appears that neither the tlog or the onboard…