thanks for looking again and fixing the bug. Important to know: Q-TRANSITION_MS ist starting after reaching target airspeed. Until we have the possibility to install a compiled version, we will try changing Q_TRANSITION_MS from 5000 to minimal ie 10,
I’ve put a new build here:
I’ve flown the CL84 tiltwing with ArduPilot and it flew very nicely. Did several manual flights with transition, then did 3 full auto flights (auto VTOL takeoff, auto-transition, auto-mission and auto VTOL land).
Unfortunately on the last auto-land one of the front propellers came off. Turns out the left/right props were mislabelled from the factory, so the nuts were self-loosening instead of self-tightening. It crashed hard when it lost the prop while hovering, but looks to be repairable.
I’ll post some videos later today.
@tridge: Congratulations and thanks very much. As soon as our aircraft is repaired, we will test the tiltrotor.
Here is a video of the flying today:
I’ll upload logs and parameters soon.
Note that I flew with a 5.2Ah 4S battery, which is much larger than the recommended 2.6Ah. It is a 10C multistar though, so lighter than a normal 5Ah
I’ve added a blog post on the test flights here:
I’ve put a log file of one of the auto missions here:
and the parameters I used here:
The servo mapping I used was:
- SERVO1: aileron
- SERVO2: elevator
- SERVO5: front right motor
- SERVO6: front left motor
- SERVO7: rear motor
- SERVO9: main wing tilt mechanism
- SERVO10: tail tilt servo
I used a 5.2Ah multistar (10C) battery, which is quite a bit bigger than the recommended battery, but its what I happened to have available. I added 30g of lead to the tail to keep it balanced with the larger battery.
Other than that I used the stock motors and ESCs from the RTF kit
I’m still alive so thanks for fixing the tilt rotor issues initially seen on the CL-84. I like the way this forum pings you lightly with updated posts so you can catch up.
Congratulations are in order to Rolf for his first successful transition to full forward flight. I hope the tree landing didn’t cause excessive damage. I was very lucky on my thick bush landing with the CL-84.
Although I have converted my CL-84 back to stock form, it really is a quick conversion back and forth to a Pixhawk with APM. I will consider converting it back during these long winter months of building. My indecision comes from the limited power of the stock design along with rather high wing-loading.
My VTOL hangar has grown to the following planes:
- FireFLY6 DIY25 with Mapping Key (tiltrotor)
- FireFLY6 DIY15 with Sport Key (tiltrotor)
- Bix3 QuadPlane
- Ranger EX QuadPlane
- CL-84 (tiltrotor)
- Ares V-Hawk X4 (tiltrotor)
I don’t have any interest in the E-flite Convergence as my focus changes to creating “productive” designs that can carry a 2.5lb-5lb (1.13kg-2.27kg) payload. The FireFLY6 and Ranger EX QuadPlane fall into this category. However, the FireFLY6, keys, and spare parts are expensive. The QuadPlane design on a low cost frame with available low cost spare parts has my main interest. The Ranger EX falls into this category and can easily carry a 5lb (2.27kg) payload. I’ll continue to look for suitable frames for testing the tiltrotor firmware. It would also be interesting to compare efficiencies between a tiltrotor implementation and a QuadPlane implementation.
Congratulations on your successful CL-84 transitions and autonomous flights! I am glad that you found and fixed several bugs to make this happen.
I use the 3s 5.2AH Multistar packs on my FireFLY6. They make several different sizes though. What dimensions are the pack that you used? Mine are 142 x 49 x 22mm.
It’s this one:
I cut away some of the foam to make it fit. You can see it fitted here:
it is pushed right back against the wood of the tilt mechanism, and I added 30g of lead on the tail.
support for Q_TILT_TYPE is now in master along with the other fixes, so anyone wanting to fly a tiltrotor or tiltwing should now just use the ‘latest’ build. For a tri-copter make sure you set Q_FRAME_CLASS=7.
Ahh yes, the CL-84 uses the 4s version of my FireFLY6 3s packs which explains the height difference. Sometimes I’m slow to catch on.
does that mean I can use 3.8.0beta1 from Missionplanner?
For pixhawk “latest” build should be this file:
I’ve released it today as 3.8.0-beta2, or use ‘latest’ as @Rolf suggests
Is anyone willing to try a FireFly6 with the latest APM:Plane? It should work, and does work in the simulator, but I’d appreciate feedback from someone who has the airframe and is willing to try it.
I’d be happy to provide config details if needed. I’d need to know what the servo output mapping (which output goes to each motor, which motors and CCW and which are CW, and which outputs go to the tilt mechanism). I’ll then mod the simulator to use the same output mapping and provide a set of parameter values which should fly it.
Thanks Tridge and Rolf,
on Friday we did some transitions with 3.8.0-beta1 and Saturday with the one Rolf suggested.
Our airspeed wasn’t working on Saturday, so we can’t supply any helpful information.
We are using a Quad with four tiltable motors. Right now we flow everything in QHOVER, MANUAL, STABILIZE and FBWA. We have to fly in windy conditions and experience a bad YAW behavior because of bad YAW authority if you are in forward flight and your roll and pitch input doesn’t fit together. Our current solution is to reduce YAW_P to 0. Otherwise two motors will throttle up to max throttle, the airframe is still flyable but sounds bad.
I hope I can support you with helpfull logs soon. But first airspeed has to work.
Hi @stundenblume, current master works without an airspeed sensor with quadplanes. It would be best in low wind though.
For your 4-tiltable setup, what is the motor order and motor direction? With a quad with 4 rotors tiltable it is critical that the front right motor be clockwise not counter-clockwise, otherwise the yaw moment from the prop as it tilts will cause more roll and you’ll never get it stable.
Can you post some photos of your build?
I’m all in with our FF6. Definitely could use help with the config and I’ll get you our current output map. Appreciate the help, we had pretty much shelved it until we could figure out its issues but it’d be nice to see it fly again.
Is anyone willing to try a FireFly6 with the latest APM:Plane?
It’s on my mind since I now have a second pre-enjoyed model which is only a DIY15. My primary FireFLY6 is a DIY25 with a Mapping key. The DIY15 only has a Sport key which doesn’t include Loiter and Auto modes. After I play around with it for a while “as is” then I may simply load the latest tiltrotor build to save myself $200 for a Pro key.
It is unfortunate that BirdsEyeView Aerobotics has gotten out of the R/C hobby sector and now focuses on commercial sectors. However, I understand their business needs. It would be great if Hobby King copied the frame. We need more VTOL ARFs!