hacker7mai.param (23.8 KB)
This is the closest parameter list I found. I have checked these parameters correspond to a quad + tailsitter. Q_tailsit_motmx is set to 15 which means copter tailsitter with all four motor running in plane mode. The description is in the full parameter list.
I guess you want to use plane 4.0 but this parameter list goes with a binaries that contains features and parameters which are not already in plane 4: The gain attenuation method is chosen with the help of q_tailsit_gscmsk parameter. But I think the way it works in plane 4 is a little different and is explained in the wiki http://ardupilot.org/plane/docs/qacro-mode.html
Also the differential thrust was not implement in May and I dont know if this feature is in plane 4.0.
A important parameter difference between copter and traditional tailsitter is about servo_function. Motors 1 to 4 are declared as 33 to 36 and for the correct mapping you have to refer to copter mapping.
I think the most important to begin is above, @kd0aij will correct me if I miss something.
hacker7mai.param (23.8 KB)
Thanks alot. Yes of course, the params are not new, but I will learn about and try to understand it. At least, they are from a real and good flying wing. And I do not simply copy it.
In my case I intend not to use all four mots for plane mode. And I need more time so the plane 4.0 will then perhaps be ready.
I made several flights with the new binaries. Tried q_hover, q_loiter, q_acro and fbwa.
To fly q_acro I had to lower gain scaling parameter to 0.05, spin min to 0.1 and q_throttle_expo to 0.1 but the result is very very good. Absolutely no oscillations can be seen whatever the attitude and throttle. There are no glitches and no rates limitation. The high gain attenuation has no effect on transition and hover stability (much better than with the batwing). While flying q_acro, motor surge can be heard, I suppose the differential thrust is active and want to correct the plane roll resulting in these surges. I will test other attenuation method soon.
Q_hover and q_loiter works good as usual. But yaw rate is limited to about 60°/s in q_hover mode but not in loiter mode. That was also true with the previous binaries. This limitation is not linked to q_tailsit_rll_mx. Anything else is OK.
I played a little with q_a_rat_yaw_flt parameters. Effect is not obvious, the only thing I can tell is about FLTE when low but not 0 the yaw become sluggish and oscillate. Do you have some ideas how to test these parameters ?
Great! Thanks for testing.
I assume this was the bi-wing copter tailsitter and GSCMSK=2?
Interesting that Q_TAILSIT_GSCMIN is so low at 0.05; I guess that would mean the elevons are more effective than with the batwing?
It might be a good idea to scale the differential yaw torque with airspeed also, if the surging is happening in forward flight (the log should help with that).
You might try reducing Q_A_RAT_YAW_FF to see if it is causing the surging.
The defaults for FLTE and FLTT are both zero, meaning no filter on PID loop error and target values. They should probably stay that way. FILT was renamed to FLTD and the default value for quadplane roll/pitch is 10Hz (20Hz for copters). A copter tailsitter might benefit from a larger value for roll or pitch, but I’m not sure. I thought @lthall had written some documentation on tuning those params for Copter, but I can’t find it now.
last flight log, yes, it was the biplane and gscmask=2
4 control surfaces directly on propellers wash make ailerons very very effective, oscillations that forced me to reduce the scaling parameter were with plane roll
My test wing is now dismantled to get back the electronic.
It looks like the torque response for bodyframe roll is pretty large in QACRO:
So I’d try reducing Q_A_RAT_YAW_FF.
Have you tried the no-yaw-torque X frame type? That’s Q_FRAME_CLASS=17.
I can’t remember whether we determined if it was necessary for a bi-wing with elevons.
After a lot of annoyance with Updating Win 7, I hat to reinstall the whole PC.
But now, the work can continue.
I plan to modify the small wing to a Copter-Tailsitter. What is your meaning about this setup?
And to use the DJI Snail System: https://www.dji.com/ch/snail/info#specs
With 4 Props 6x3", Battery 3S, 3000 mAh. The weight would be 920 gr.
Would the Mot Distance behind be enoughe with 240 mm. (9.5")
That’s a good idea to use again your Caipirinha. The 240 mm distance between top and bottom motors seems fine. I had 220 mm on my test wing (1200mm wing span) and 180mm on my jet wing (980mm wing span) so you will probably get more pitch authority. The CG will be relatively high when the wing will sit on his tail, so you can expect the wing to tip. Maybe some legs below motor mounts will help.
Thanks for the feedback.
CG is 24 cm from the ground.
Yes, one of the disadvantage of Tailsitters. I will add thin carbon sticks to the elevons from tip to tip (vertical in Plane mode) a least for hover tests.
Edit: Or do you mean tip while hovering?
No, I meant during landing. I am pretty sure hovering will be solid.
Nice looking model. Are you planning to add it to the SITL_models repo?
I made it about 2 years about as vectored Tailsitter for Tridge. I don’t know if it worked it was not the best
idea that I made the designe, Tridge the Test with comment, and redesigne by me and test… and so on. Therefore Tridge installed also the 3DStudio to do it by himself.
For me its difficult to test, because my RF8 makes troubles on different PC’s. It needs to edit the model, but everytime when I quit edit, RF8 crashed. And no answer from RF8 support. I was used to develope MS Flight Simulator Aircrafts, Landscape, Airport, Panels and Gauges. But was frustrated about the quality of RF8 and stopped to use it. Below a Pic of my setup, approach cologne (Germany) airport at night.
Very nice simulation setup!
The CatTailsitter in SITL_models flies, but it is extremely difficult for me to hover in QACRO mode. Not sure exactly what the issue is there. Here’s a short clip of qhover mode in RF8 with my version edited to match @losawing 's Batwing and flying with my gainscaling PR:
Yes. this cat I made from the data of a real non vectored tailsitter from David. Nice to see it in the air.
As I knew, it was difficult to fly even in QStabilize. David tried to find the reason and worked with different CG.
I did the 3D Design only, and Tridge the nescessary for RF8.
Motivated by your question, I had a look to my last project for the simulator.
Also I hoped that the “Exit Editor” issue has solved in the new update in the last 18 month.
This is not the case, when exit Editor the title menu bar doesn’t work anymore.
The same issue is with all standard Aircrafts.
Here the last job “Called SkyCat”,a vectored Tailsitter, not ready to fly yet. Perhaps you can complete it if possible at this state.
And the Params of the last RC Flight:
@lorbass Thanks for the model.
I was able to import and edit it in RF8; no crashes
I don’t think I changed anything in the editor, and it flies on Plane 4.0, though I wasn’t able to tune it very well. Maybe @iampete would have better luck.
Hello Mark, I must say thank you. Finally after hard working I could see the plane flying.
Did you use the params from my link?
About RF8 issue. After exit Edit the title menu bar doesn’t work anymore also with all standard airplane.
Also when nothing was edited. Just select in the simulator edit Aircraft, and back with exit edit.
And with Win 7 Ultimate and Win 7 Home Premium on 3 different PC’s. I will try to contact again the support.
The side trip to the threads Tailsitter and Simulator showed me, that’s possible to make the caipirinha copter Tailsitter as model for SITL.
You’re quite welcome, and I’m glad to be able to help with this; I’d also like to be able to try your quad copter tailsitter, if you have done a Realflight version of it.
I started from scratch with the basic tailsitter params, then tried qautotune, but the resulting PID gains weren’t very good, and it crashed several times during tuning. There’s something weird going on with yaw; it seems very unstable in yaw and the motors are tilted significantly in opposite directions when hovering.
I put the params I wound up with here: https://github.com/ArduPilot/SITL_Models/tree/master/RealFlight/markw/Tailsitters/TVBS
along with my modified version of your RFX. I remembered that I moved the CG back 3cm while trying to improve hover stability.
I did try the PID gains from your file, but I believe the yaw gain was too low for a stable hover. Do you have any stability issues with the real model?
@lorbass Regarding RF8, I’m not having any problems with the Steam version on my Intel Windows 10 laptop with nvidia gforce gtx graphics. I don’t think I’ve seen a single crash or hang with the model editor since I installed it a year ago.
In this case, I will continue with the design to create the RFX. Just a question: How are the numbers of the motors (left, right, top, bottom)
My hover tuning was perfect, in Plane mode not yet.
I do hover tuning always in a Rig.
- no damage in case of (Like here at the beginning when a did it not in a Rig: https://youtu.be/KwYbkTRZ5lk
- can concentrate on tuning, not flying,
- Close to my eyes.
- no start, landing between modifying params.
Tuning in SITL would be easier, but I already heard from David (Palm369) that the behavior between RF8 and Reality is different.