Triflight setup guide

[chilternflyer]

@Leo
Funny you should say that. I worked out that increasing the rates makes it more scary and prone to flipping out on a turn.
Tomorrow I’m going to try a profile with 30% rates on pitch and roll. most of my other settings are as per the download of the CLI dump in the setup page.
Thanks for doing the setup guide. It was very helpful 🙂
P.S. I’m only on 3S at the moment.

Attachments:

1. 

   Capture.jpg
   

[LeoTheHuman]

Well, this is exactly why I suggested lowering rates. I don’t see anything funny there. If you never want to do flips with this setup you might want to lower the rates from 0.4 to 0.2 or even 0.0, 0.3 won’t help much. You might also want to lower the expo to get it to respond more quickly around the center if you lower the rates that much.
Also, I would refrain from flying this on 3S, as it was never tuned for that and it will have much worse behavior on 3S with current setup. I’ve tried that out of curiosity and it feels like a cow on the ice rink… It still moves, but forcing it to do something you want is very-very hard. (:

[Terje]

Adding a CLI Variable Reference table to the guide might be a good idea.

Might be a good place to state the default values, and recommended values for different servos at different voltages as well.

[LeoTheHuman]

I will include it if someone writes it down. I definitely don’t have enough time to do that in the next few days.

[Terje]

@LeoTheHuman I’ll look into it if you would share a CLI dump of your latest working setup?

[Terje]

I stumbled upon this post when looking for looptime info on the DYS BL20A ESCs.

It specifically adresses the issue of motors (and ESCs) overheating when using the Betaflight firmware.

We are talking about lowpass cutoff filters.

The values mentioned are:
gyro_cut_hz
pterm_cut_hz
dterm_cut_hz

The default values in Cleanflight 1.10 are 0 so that people can upgrade their systems without changing the values. Using a 0 value seems to be disastrous though?

The author recommends setting the values to:
set gyro_cut_hz = 60
set pterm_cut_hz = 40
set dterm_cut_hz = 15

I’ve checked against the Triflight 0.3RC2 and the variables
gyro_cut_hz
pterm_cut_hz
don’t exist.

dterm_cut_hz is set to 20.

Could this affect the motors and ESCs on tricopters running Triflight 0.3RC2?

[lauka]

The low pass filters have been removed in betaflight, replaced with more efficient 7-tap FIR filter. The filter parameters are precalculated for approximately 100 hz cutoff. Thos produces much better filtration with less delays. Only the D term low pass filter remains and the default value should be sufficient.

You don’t have to be worried Terje:)

[Terje]

Thanks for the swift reply @lauka 🙂 I guess the same goes for the looptime variable?

[chilternflyer]

Slightly off topic:- I’ve had to replace one of my DYS 20a’s because it was making a funny squealing noise (sounded like something rubbing inside the motor and didn’t produce the same power as the others. I swapped the motor and it was still doing it).
Anyway, the new motor/ESC combo started off ok but it is now doing the same as the last motor/ESC (on and off).
Has anyone else had a similar problem?
Nothing is getting hot or binding. If it was desyncing it would stop.
Have I got the timing or something wrong?

[LeoTheHuman]

Updated the setup guide for latest triflight 0.3 released by lauka today.

[Terje]

Made the triflight setup guide sticky.

[Ralph]

I assume the CLI-code on the Tricopter-Shoppage is no more needed in the current triflight build 0.3?
Or do I still need to insert it after flashing the board?

[LeoTheHuman]

No, you don’t. I thought it should be clear from the current version of the guide.

[Ralph]

btw the guide has still some “old” triflight_NAZE.hex link in it.
maybe just use the direct link from github?
Triflight_0.3_NAZE.hex

[LeoTheHuman]

The guide has some “new” triflight_NAZE.hex link in it with tuning improvements, made by lauka after releasing 0.3, and new betaflight release but before messing with other stuff. (:

[Author]

Posts