Well, it is not about the speed, because you set the speed for both servos not individually. It’s about their respective position. When I tried same props on the front motors I got about 90 degrees of yaw at the transition start.
Do you have your LOG_BITMASK enabled (i.e. =65535 for PX4/PixHawk Full Logs default)?
Yes, and the problem with logging seemed to be a full SD card.
1 Like
I’ve started looking into .lua scripting. I’m trying to make a servo move but I cant seem to figure out how. Either the pixhawk doesn’t run my script or there is some syntax error… I am currently only running example scripts for testing 
“Unable to allocate scripting memory” is the error I get
EDIT: Switched to a CubeOrange from 2.4.8 and it seems to work run the script - albeit with errors
We’re trying a belly lander bicopter with both motors on the same axis, i.e., not able to move individually. Is there any way to do this? I am not aware of any settings for this and I’m currently playing with scripts to make the motors move 
Here are some photos
Got it to work! Heap size was too big! Getting familiar with .lua syntax helped too 
Hey, we went for a waypoint mission yesterday but crashed the plane. It went up to the desired height and then just fell down to the ground. We couldn’t read the bin logs (don’t know - corrupted) but the tlogs are available. It seems the plane thought it was doing 66m/s when hovering on the spot. We think this is cause we had previously enabled an analog aspd sensor but forgot to disable it in the parameters.
If someone can try to look at the bin logs that would be awesome, we can’t seem to do it!
(Edit: uploaded bin)
I had a look and it doesn’t look like there is any data to recover.
Can you link to the tlog?
We have started getting some errors when trying to read logs - across all our pixhawks. The error says it cannot read the logs.
!
We removed all our logs, changed firmware from 4.1.0DEV to 4.0.5 and noticed a change of parameters. FFT_ENABLE was gone and the logs seem to log perfectly now. The old ones were written in 0000xxx.bin format which appears to be the case for all corrupted files. Now its back to logging as DATE_TIME.bin.
Tags for people who have a similar error -
FMT_ENABLE
FMT ERROR
LOGGING
CORRUPTED LOGS
Log browse will not function correctly without FMT messages in your log
no. ArduPilot always logs as 000xxx.bin files, and always has done. The DATE_TIME.bin is from the ground station scanning the file looking for GPS messages and using those to work out the date then renaming the file on the GCS.
Where exactly did you get that corrupted log from? Did you get it from MissionPlanner download, or did you get it directly from the microSD card? If you got it from MissionPlanner then there is a chance the corruption came from the download process.
1 Like
Ah, I didn’t know that.
We downloaded it using both mission planner and QGC, both had no FMT messages and/or couldn’t download the logs. We could get the logs from the sd card directly but had similar errors. We changed the fw and got it to log but sadly it resulted in a 15kb log every 2 seconds. All of these issues appeared around the same time on all of our boards which is a bit scary.
We went to Idre, a calm mountain town in Sweden, to do some testing. Here’s the result of that trip!
3 Likes
Very cool indeed! Congratulations! Would you provide access to your latest vehicle parameters file just for comparison purposes?
Best regards
Very nice!
(och jatte kul!)
1 Like
Absolutely, unfortunately the parameters are not perfect but you can look at them for sure!
X8_backup_20_06_28.param (21.6 KB)
1 Like