Triflight setup guide

[mcla118800]

Hello all,

I am just finishing my build on the mini tricopter and have run into a bit of a problem connecting my receiver(Frsky X4R). i cannot find any documentation anywhere of how to connect the receiver in sbus mode to the naze 32 frame. – i do not know what pins-
Any help is appreciated=)

[PlanB]

x4r does not support SBUS, you need x4rsb for this.
SBUS signal pin goes to UART RX pin on naze. You only shouldn’t use UART1, as it’s shared with USB.
If you use RCExplorer frame integrated naze you also need signal inverter for sbus

Attachments:

1. 

   x4r-expl.png
   

2. 

   ports-expl.png
   

3. 

   sbus.png
   

[pqueiros]

Here is a good (at least worked for me :)) howto regarding frsky SBUS and smart port telemetry.
http://blog.oscarliang.net/sbus-smartport-telemetry-naze32/

I ended hacking the receiver to get the uninverted SBUS signal, by sacrificing channel 2 signal pin. The drawback is what now is not so easy to enable CCPM during binding. You need to think what is best for you.

Please keep in mind to use a HW serial port for the SBUS connection (UART(1,2,3)). SOFTSERIAL might even work but I would not trusts it. I don’t think you want to make your rc input vulnerable to potential delays caused by sw routines.

In my setup I use:
UART1 -> MSP, BLACKBOX (only enabled when tri is armed)
UART2 ->SBUS
SOFTSERIAL2 -> Smart port telemetry

[mcla118800]

Thanks for the response. I think that the only question I have is where is the actual uart2 port on the Naze 32 frame?
Thanks

[pqueiros]

Hi,
Pin mapping is explained in
https://github.com/cleanflight/cleanflight/blob/master/docs/Board%20-%20Naze32.md

SBUS is a one way protocol, where the Naze is the receiver, thus you will only need RX pin which is on RC4 on the naze32.

/pq

Attachments:

1. 

   naze32_uart.jpg
   

[Maze82]

Ok, a quick question.

I guess that the pwm freq for the servo is set to 330?
I have a Rgb led switch that i usualy connect to a reciever och before i switched to triflight, to one of the extra outputs on the CC3D.
Now i have a Naze32 but i cant get the switch to work, i Have done the Servo_tilt and Channel forwarding, i have tried the output (motor out 2) with a servo and it works.
Is there someway i can change the freq for only that output and not the one for the tail servo?

/Jonas

[Terje]

The PWM frequency for the BlueBird 210 should be 250.

[Maze82]

Ok maybe it is, im not that in to that part :-p, but i thought maybe the problem with my led switch was the too high freq, can i change it only for one but not the other?

[Divi]

Hello! Morjens!

Is there a way I could use naze pins 1-4 for servo and 3 motors, and not 1,3,4,5? Does triflight work with custom mixer and how can I set it up? Reason for this is that I’m using RotorX Atom PDB which has only those 4 pins. http://www.paragonuav.com/atom-pdb/

Thanks!

– Jussi, Finland

[LeoTheHuman]

Well, you can route the wires from ESCs directly to FC. You can’t use the pins 1 & 2 for different frequencies of PWM, because they share the same timer, I believe. If you run the servo and ESCs at the same PWM frequency, you can use pins 1-4, but you’ll need to modify the code.

[Divi]

Ok thanks.. gotta ditch the idea of using atom for signal routing then.

[Bengt]

New checklist available

Greetings,

I’ve been experimenting and I’ve crashed and I found myself searching for the same information several times.
The various video guides are very good the first time, but after a few times it’s more helpful for me with a printed check-list. So I made one.
I started from Leo’s (slightly outdated) guide at the top of this thread and added pieces collected from different places, such as lauka’s release notes and this forum.

I made it in md format (easier to maintain) and today I have published it as a pull request on Github. You can find it here.

I think it’s up to date with TriFlight 0.5 Beta 2.

I hope it is helpful, and that someone can help to review it.

/Bengt

[Joost]

A really good idea, it looks a bit rough around the edges, I’ll try to pretty it up & add where I can. Best if we try to keep it up to date as lauka updates the code.

I have one question though, and probably I missed it, but I couldn’t find/determine when exactly tailtune has successfully saved the values after landing -> disarming -> wait few seconds -> turn off tailtune.

I’ve had a bunch of times last weekend when switching props and try to redo the tune where it would not save properly and default to a value of 10. This would happen if I tried the stick command to force a save, or it would fly great after a tailtune (indicating it did work) but as soon as I’d switch batteries it would go back go the value 10 with the servo locked in maximum yaw right position.
I would then have to drag it back home to manually reset the tri_tail_motor_thrustfactor to something flyable (89 ish)

[Terje]

Really good Work @Bengt 🙂 There is a huge difference between thinking about doing some documentation (me) and actually doing it 🙂

Maybe the parts could be split up into something like:

tailtune.md
servofeedback.md
connections_Naze32.md
connections_SPRF3.md
etc?

I’m often realizing that what I thought was easy to remember, really isn’t… Sometimes the really simple stuff like which motor is #2 Again?

[LeoTheHuman]

Yeah, I agree on splitting idea. I was going to update the guide when I get back to my tri later this week, but now, as I see it being done by someone else, I will hopefully have more time to actually fly. (:

[Author]

Posts