[quote=“John2014”]I was thinking of something if we can find it inside the logs, let’s assume there was a weight shifting inside the plane for unknown reason, despite we were flying stable, and we were in the RTL mode. Can you check if the Pixhawk has felt something 1/10 of the second just before it starts to move/lock the servos . We were at the RTL mode then stabilize then manual.
[/quote]
can you help me narrow down exactly which part of log 280 you are suggesting I concentrate on? There are 6 segments in RTL mode in that log. Four of those had RTL then STABILISE then MANUAL.
If you can give me a timestamp or some other marker that may help narrow things down.
Cheers, Tridge
[quote=“tridge”][quote=“John2014”]I was thinking of something if we can find it inside the logs, let’s assume there was a weight shifting inside the plane for unknown reason, despite we were flying stable, and we were in the RTL mode. Can you check if the Pixhawk has felt something 1/10 of the second just before it starts to move/lock the servos . We were at the RTL mode then stabilize then manual.
[/quote]
can you help me narrow down exactly which part of log 280 you are suggesting I concentrate on? There are 6 segments in RTL mode in that log. Four of those had RTL then STABILISE then MANUAL.
If you can give me a timestamp or some other marker that may help narrow things down.
Cheers, Tridge[/quote]
It goes crazy at about 54.9% of the log or after the 9minutes and 30sec.
I think we must be looking at different scales. 9 min 30 seconds is 7% of the way through the log (by log size), in MANUAL.
Can you identify the time to concentrate on based on this printout of the modes and timestamps in 280.BIN ?
Sat Nov 29 11:10:50 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417266650 0%)
Sat Nov 29 11:10:50 2014 MAV.flightmode=CIRCLE (MAV.timestamp=1417266650 0%)
Sat Nov 29 11:17:24 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417267044 0%)
Sat Nov 29 11:18:19 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417267099 3%)
Sat Nov 29 11:19:47 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417267187 7%)
Sat Nov 29 11:28:59 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417267739 34%)
Sat Nov 29 11:29:02 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417267742 34%)
Sat Nov 29 11:29:36 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417267776 36%)
Sat Nov 29 11:32:14 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417267934 44%)
Sat Nov 29 11:32:20 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417267940 44%)
Sat Nov 29 11:34:10 2014 MAV.flightmode=RTL (MAV.timestamp=1417268050 49%)
Sat Nov 29 11:34:29 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417268069 50%)
Sat Nov 29 11:35:30 2014 MAV.flightmode=CRUISE (MAV.timestamp=1417268130 53%)
Sat Nov 29 11:35:52 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417268152 54%)
Sat Nov 29 11:39:25 2014 MAV.flightmode=RTL (MAV.timestamp=1417268365 65%)
Sat Nov 29 11:39:46 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417268386 66%)
Sat Nov 29 11:40:12 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417268412 67%)
Sat Nov 29 11:49:49 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417268989 95%)
Sat Nov 29 11:49:50 2014 MAV.flightmode=RTL (MAV.timestamp=1417268990 95%)
Sat Nov 29 11:50:00 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417269000 96%)
Sat Nov 29 11:50:01 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417269001 96%)
Sat Nov 29 11:50:08 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417269008 96%)
Sat Nov 29 11:50:12 2014 MAV.flightmode=RTL (MAV.timestamp=1417269012 96%)
Sat Nov 29 11:50:18 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417269018 97%)
Sat Nov 29 11:50:24 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417269024 97%)
Sat Nov 29 11:50:25 2014 MAV.flightmode=RTL (MAV.timestamp=1417269025 97%)
Sat Nov 29 11:50:42 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417269042 98%)
Sat Nov 29 11:50:44 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417269044 98%)
Sat Nov 29 11:50:52 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417269052 98%)
Sat Nov 29 11:50:53 2014 MAV.flightmode=RTL (MAV.timestamp=1417269053 98%)
Sat Nov 29 11:51:01 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417269061 99%)
Sat Nov 29 11:51:05 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417269065 99%)
I think we must be looking at different scales. 9 min 30 seconds is 7% of the way through the log (by log size), in MANUAL.
Can you identify the time to concentrate on based on this printout of the modes and timestamps in 280.BIN ?
Sat Nov 29 11:10:50 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417266650 0%)
Sat Nov 29 11:10:50 2014 MAV.flightmode=CIRCLE (MAV.timestamp=1417266650 0%)
Sat Nov 29 11:17:24 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417267044 0%)
Sat Nov 29 11:18:19 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417267099 3%)
Sat Nov 29 11:19:47 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417267187 7%)
Sat Nov 29 11:28:59 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417267739 34%)
Sat Nov 29 11:29:02 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417267742 34%)
Sat Nov 29 11:29:36 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417267776 36%)
Sat Nov 29 11:32:14 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417267934 44%)
Sat Nov 29 11:32:20 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417267940 44%)
Sat Nov 29 11:34:10 2014 MAV.flightmode=RTL (MAV.timestamp=1417268050 49%)
Sat Nov 29 11:34:29 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417268069 50%)
Sat Nov 29 11:35:30 2014 MAV.flightmode=CRUISE (MAV.timestamp=1417268130 53%)
Sat Nov 29 11:35:52 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417268152 54%)
Sat Nov 29 11:39:25 2014 MAV.flightmode=RTL (MAV.timestamp=1417268365 65%)
Sat Nov 29 11:39:46 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417268386 66%)
Sat Nov 29 11:40:12 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417268412 67%)
Sat Nov 29 11:49:49 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417268989 95%)
Sat Nov 29 11:49:50 2014 MAV.flightmode=RTL (MAV.timestamp=1417268990 95%)
Sat Nov 29 11:50:00 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417269000 96%)
Sat Nov 29 11:50:01 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417269001 96%)
Sat Nov 29 11:50:08 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417269008 96%)
Sat Nov 29 11:50:12 2014 MAV.flightmode=RTL (MAV.timestamp=1417269012 96%)
Sat Nov 29 11:50:18 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417269018 97%)
Sat Nov 29 11:50:24 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417269024 97%)
Sat Nov 29 11:50:25 2014 MAV.flightmode=RTL (MAV.timestamp=1417269025 97%)
Sat Nov 29 11:50:42 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417269042 98%)
Sat Nov 29 11:50:44 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417269044 98%)
Sat Nov 29 11:50:52 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417269052 98%)
Sat Nov 29 11:50:53 2014 MAV.flightmode=RTL (MAV.timestamp=1417269053 98%)
Sat Nov 29 11:51:01 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417269061 99%)
Sat Nov 29 11:51:05 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417269065 99%)[/quote]
Sat Nov 29 11:39:25 2014 MAV.flightmode=RTL (MAV.timestamp=1417268365 65%)
Sat Nov 29 11:39:46 2014 MAV.flightmode=STABILIZE (MAV.timestamp=1417268386 66%)
Sat Nov 29 11:40:12 2014 MAV.flightmode=MANUAL (MAV.timestamp=1417268412 67%)
The problem started when we switched to RTL then we tried to fly in stabilize, as we thought it was a GPS issue, but also in Stabilize the plane was still going crazy, we moved to manual to save the plane, and in manual the response from the servos was still very slow.
Here is the graph with details.
Hi John,
I think we are not looking at the same log file. I have been looking at 280.BIN from this download site that you gave me:
drive.google.com/folderview?id= … sp=sharing
The log file 280.BIN does not have any RCIN messages, which means it can’t show the flightmode channel changes you just graphed. That is because the flight for 280.BIN had LOG_BITMASK set to 8062. For a pixhawk you should normally have LOG_BITMASK=65535, meaning “log all messages”.
Also, the graph you showed is from a tlog, not from a BIN log.
Can you please use the graphing and mission plotting capabilities of MissionPlanner to work out exactly which log files show the issue, and which part of the log files. Then upload the exact log files again.
Please also change LOG_BITMASK to 65535 for future flights so we can log all messages.
Anyway, I have spent quite a lot of time looking at 280.BIN. What I was looking for was a sign of the issue you describe where there is a sudden change in flight behaviour. What I found is that the plane acted “tail heavy” throughout the flight. For example, here is demanded vs achieved pitch for the first two RTL segments in 280.BIN:
uav.tridgell.net/John2014/RTL1_pitch.png
uav.tridgell.net/John2014/RTL2_pitch.png
You can see that both are similar. In both cases the actual pitch is well above the demanded pitch. That is “tail heavy” behaviour.
The cause of that is the pitch tuning of the aircraft. You have:
PTCH2SRV_D 0.000000
PTCH2SRV_I 0.040000
PTCH2SRV_P 0.250000
I don’t know how you ended up with those values, but it certainly didn’t come from AUTOTUNE. The P gain is far too small and you have no D gain. The I gain is almost certainly too small too.
I really would like to help you, as the problem you describe (bad flight in manual due to misbehaviour of manual pass-thru) would be an extremely serious bug if true. I just need you to narrow down the issue for me in a way that I can examine it. It now seems that I’ve spent a long time just looking at a log that doesn’t show the issue, and just shows a log of a badly tuned plane.
If you can find the right log and tell me what part of the log to look at then I’ll look again.
Cheers, Tridge
HI Andrew,
We did new flights today
We don’t know what is happening but it seems where are a magnet for the bad luck, even the SDcard is not working to retrieve the data.
We did 3 flights and on the 3rd one after the take off, we lost control but not the throttle.
In the first flight, we did a flight without the autopilot, it was great for 5 minutes. Then we landed, and we’ve connect the pixhawk and we did a flight in manual mode and it was great also. We did some trims.
We landed again, and we did autopilot calibration and we moved all sticks to the maximum for the pixhawk to know the limits then we changed the battery.
We did the 3rd flight and just after the launch, we lost control of the servos but the motor was still working and it crashed and we were at the manual mode.
The failsafe was only programmed on the microRx and not on the Pixhawk.
We did all DragonLink test as micro power test, surface control, checking the LEDs and everything was OK before the flights.
The telemetry was Off all the time.
We are checking now with the SDcard but it seems it was damage due to the crash.
We don’t know why the crash happened and we are out of logs. I don’t know what happened and we are feeling we are out of good luck.
is there anything wrong we did, was it the right procedure? Do you think we need to format the pixhawk.
We feel bad too that the sdcard is not working, all the good files are in it.
What are the reasons that the SDcard get failed after a crash and the Pixhawk still good?
HI Andrew
We were able to get the log files from the terminals screen.
here is the link of the folder where are the logs: drive.google.com/folderview?id= … sp=sharing
I have attached the crash file. 2014-12-06 16-06-53.log
Here what we did in the day:
First fly, we flew fully manually NOT Via the pixhawk, but it was ON i guess. We did some trim and we landed.
Then we have connected the Pixhawk and we flew with it in manual mode only, we did some trim also.
After we landed, we unplug the battery then plug it back, we did arming to do Autopilot/Radio calibration, we saw one of the aileron very up, we did a trim on the ground, then we did Autopilot/Radio calibration by moving all sticks to the maximum in the radio, then we turn it off and change the battery.
Then we removed the Telemetry and we armed the Pixhawk and we throw the plane in manual mode, it went up left for few seconds but then it turned left and down and crashed badly.
Failsafe was only activated on the dragonlink Radio and not on the Pixhawk.
Please tell us what we did wrong, is it from the Pixhawk or Trims or Radio controller…?
We really appreciate your help and time.
At the 3rd flight, when it was going left, we were not able to guide the plane, it was like a failsafe or the servos didn’t get the command from us.
[quote=“John2014”]HI Andrew
We were able to get the log files from the terminals screen.
here is the link of the folder where are the logs: drive.google.com/folderview?id= … sp=sharing
I have attached the crash file. 2014-12-06 16-06-53.log
Here what we did in the day:
First fly, we flew fully manually NOT Via the pixhawk, but it was ON i guess. We did some trim and we landed.
Then we have connected the Pixhawk and we flew with it in manual mode only, we did some trim also.
After we landed, we unplug the battery then plug it back, we did arming to do Autopilot/Radio calibration, we saw one of the aileron very up, we did a trim on the ground, then we did Autopilot/Radio calibration by moving all sticks to the maximum in the radio, then we turn it off and change the battery.
Then we removed the Telemetry and we armed the Pixhawk and we throw the plane in manual mode, it went up left for few seconds but then it turned left and down and crashed badly.
Failsafe was only activated on the dragonlink Radio and not on the Pixhawk.
Please tell us what we did wrong, is it from the Pixhawk or Trims or Radio controller…?
We really appreciate your help and time.[/quote]
Hi Guys,
New user of APM here, im trying to download version 3.2 in Mission Planner to no avail, can some one post the link where to download the legit 3.2 hex file?
I tried the version 3.4 but my bluetooth not working when connected to my android phone, but when i connected to PC was using bluetooth was ok, also having some issue with minimosd, not showing battery voltage but when connected to mission planner was ok using bluetooth.
thanks!