Triflight 0.7 Beta 2

[bhuism]

@sirpoonga where do you see the triflight hex for your CLRACINGF4?

If I read the code correctly, EXT1 is not defined for CLRACINGF4,

Pin PC3 is used for feedback wire

as per:

https://github.com/lkaino/Triflight/blob/0_7_beta2/src/main/target/OMNIBUSF4/target.h#L194

How this CPU pin is broken out on that board I don’t know

[Kevin]

Well, per the pinout for the microcontroller PC3 is pin 11. Unless someone know exactly what label uses that I can at least do a trace to find now. But then it looks like I would make have to disable RSSI?

[bhuism]

PC3 is RSSI on the CLRACINGF4 board:

https://github.com/betaflight/betaflight/blob/master/src/main/target/CLRACINGF4/target.h#L116

Can u use that, that’s the ‘normal’ way of connecting feedback wire.

[ME-tan]

I’m right to set the FC to 180 degree pitch? V4 is currently doing somersaults just above the ground when I throttle up.

Zero degrees just span, tried 180 degree roll instead and broke a prop spectacularly…

[Kevin]

After reading through other posts, and the new yaw logic thread, I am over thinking this. Though I might try to get the CLRF4 working to give the community information about it. However the issue is there is no RSSI pad. I assume that is because it connected to the OSD on the circuit board. Not sure if I would have to cut a trace or something? Plus, where does it get the RSSI from? SmartPort? If using the RSSI pin is the normal way how does that work?

But, after reading through several other threads I am replacing a BFF3 with the CLRF4. There is plenty of documentation on how to get that working. So maybe I will just do that. Then if I do get this working there’s probably a good chance I will get a baby tri as a winter project.

[hsamuels]

Probably 180 degrees around the yaw axis. But you should check the correct orientation in the configuration tab. Just move the tricopter around, and make sure the one on the screen moves in the same way.

[ME-tan]

Tested that, only 0 degree everything and 180 degree pitch move the picture correctly.

Ed – Reverted back to Cleanflight to test my config was correct, and all my peripherals that had stopped working in CF now work again for some reason. I’m gonna hold off on upgrading and let people who know what they are doing (i.e. not me) figure out how to config this on the v4.

[LitterBug]

@lkaino I’m reviving my beat up TriFecta frame with a DTFc (doge) FC so I can test with a larger frame. Unfortunately there is no RSSI pin exposed/mapped for this FC https://www.airdtf.com/DTFc_User_Manual.pdf . Would it be possible to map the servo feedback to the LED pin on A06 for this target?

Cheers!
LitterBug

[LitterBug]

@lkaino, I’ve been working with @Jihlein on bench testing the DTFc FC (Doge) with a copy of Beta2V6 where EXT1 is tied to A06 for the Feedback. Trying to get the resource mapping correct starting with the Servo. The servo moves correctly when in ground tailtune mode. I can select the end/center points, make adjustments, and kick off the servo speed measurement, and it completes with the “successful” sequence. The servo speed is however -1.

Servo is on channel 1
Motor 1 is on channel 3
Motor 2 is on channel 4
Motor 3 is on channel 5

Here’s my resource mapping so far.

# diff
# Triflight 0.7 Beta 2 - new control test v6 / DOGE 3.1.7 Jul  7 2017 / 18:03:36 (fc9f38d)
resource MOTOR 1 A10
resource MOTOR 2 A09
resource MOTOR 3 A00
resource MOTOR 4 NONE
resource MOTOR 5 NONE
resource MOTOR 6 NONE
resource MOTOR 7 NONE
resource MOTOR 8 NONE
resource SERVO 1 B08
servo 5 938 2016 1396 40 40 100 -1

feature -RX_PPM
feature RX_SERIAL
map TAER1234
serial 2 64 115200 57600 0 115200
aux 0 0 1 1450 2050
aux 1 28 0 1450 2050
aux 2 1 0 950 1050
aux 3 2 0 1450 1550
aux 4 13 2 1950 2050
aux 5 31 2 1450 1550
set serialrx_provider = SPEK2048
set tri_tail_servo_speed = -1
set tri_servo_feedback = EXT1

Trying to wrap my head around the servo mapping. Seems like TriFlight treats it as Servo 5, but betaflight it is servo 1. Any insight to how the servo mapping works would be great.

Cheers!
LitterBug

[Phrozen]

I’ve been trying to get the Servo working on my Tri with the BetaFlight F3 FC (BFF3). So far i can get all the motors reassigned but the servo doesn’t seem to work in any function.

Here is the wiring diagram

# diff
# Triflight 0.7 Beta 2 / BETAFLIGHTF3 3.1.7 Jun  4 2017 / 13:24:55 (1698ba5)
resource MOTOR 1 B08
resource MOTOR 3 B09
resource MOTOR 4 A06
resource MOTOR 5 NONE
resource MOTOR 6 NONE
resource MOTOR 7 NONE
resource MOTOR 8 NONE
resource MOTOR 9 NONE
resource SERVO 1 B07
resource PPM 1 NONE
servo 5 1000 2000 1500 40 40 100 -1

map TAER1234
aux 0 31 0 1300 2100
set serialrx_provider = SPEK1024
set tri_servo_feedback = EXT1
profile 0

rateprofile 0
rateprofile 0

Any clues to what i can attempt to try here?

–Edit
Looks like BetaFlight 3.2 has no problem with activating the servo (had to swap to it for the Blheli_32 passthrough, had to reverse a motor)

–Edit #2
And i am leaving this post just in case someone else needs a diagram of how to wire this up. I found the ground wires on the BFF3 are a royal pain and the servo came slightly out of the ground so it no longer was making enough contact to get the servo to move. The FW is working and i now need to go fly!

[Allenhat]

I have a question on running Triflight on a Furious FPV Radiance. How do I know which pads to connect the tail servo to and what motors go where on the Radiance? Has anyone tried running Triflight on one yet?

[wynnsquad]

Hello,

I’ve had a little success flying the V4 with 0.7 Beta 2 but the tail/yaw is doing some funny things. The tail servo is excessively jittery, and I have quite a bit of yaw drift. When I yaw right, the tail feels pretty locked in. I start a yaw spin, and then when I release the stick, it stops. When I yaw left however, after letting go of the stick it lazily keeps turning for a bit. I’d estimate it overshoots by about 45 degrees on average. The default yaw pids weren’t working and my current pids are P = 80 I = 60 D = 100 (the high D term was to try and reduce the servo jitters). Any suggestions from anyone? Thanks!

[sbole04]

Hi, I have been struggling with my tri for a while, thought it was the Graupner FC, so I decided to get triflight a shot, but a no go so far.

So the issue is that when i am flying around and I go to make a turn while in forward flight my tri seems to be fighting itself the entire time around, and at times it is so bad that it will not even turn.

here is my set up:
motors: xnova rm2206 2300kv xts
esc: dys 30amps
fc: sp racing f3
servo TGY-210DMH
here is the dump hopefully this helps, kinda at wits end with this

# diff
# Triflight 0.7 Beta 2 / SPRACINGF3 3.1.7 Jun  4 2017 / 13:44:00 (1698ba5)
servo 5 1000 2000 1500 40 40 -100 5

feature -RX_PPM
feature -VBAT
feature -FAILSAFE
feature -TELEMETRY
feature -CURRENT_METER
feature -BLACKBOX
feature -TRANSPONDER
feature RX_SERIAL
feature MOTOR_STOP
map TAER1234
serial 2 64 115200 57600 0 115200
aux 0 0 0 1300 1700
aux 1 1 1 900 1300
set disarm_kill_switch = OFF
set serialrx_provider = SUMD
set align_gyro = CW180
set align_acc = CW180
set align_mag = CW180
set tri_unarmed_servo = ON
profile 0

rateprofile 0
rateprofile 0

[LitterBug]

@sbole04, can you do a “diff” instead of a “dump”? It’s much easier to review the list of parameters that aren’t set to defaults rather than every single parameter on the board. What flight mode are you using? Are you trying to steer with yaw, roll, or coordinated turns with Yaw, pitch, and Roll?

Cheers!
LitterBug

[sbole04]

Yea, will update that when I get home from work. Yes the issue is when doing coordinated turns. It was happening in both angle and acro

[Author]

Posts