Home Forums Everything about everything else Triflight 0.7 Beta 3

Viewing 12 posts - 106 through 117 (of 117 total)
  • Author
  • #58529

    The Servo is not activated until after the disarmed tail tune. Probably to protect the servo/tilt mechanism/idiot pilot.

    I am humbly here to ask for help.
    I am trying to replace my Baby Tricopter’s burned out FC with an Omnibus F4SD. Following https://github.com/lkaino/Triflight/wiki/Servo-output-channels-for-targets the Servo Output Channels for targets for OmniBus SD:
    Target Servo output channels Motor output channels
    OMNIBUSF4SD 5 1-4
    I connected the motors to PWM 1-3 and the Servo to PWM5. I connected the servo feedback wire to a teeeny pad on the bottom of the FC labeled RSSI and changed

    tri_servo_feedback = VIRTUAL to tri_servo_feedback = RSSI

    so far so good?

    Here’s where I run into trouble. I’m not inept with working in Betaflight, but I do not understand it’s core design and processes so these next parts are confusing to me. With some direction I should be good.

    I see that the 40 degree tail servo limit has been assigned to Servo 5:
    servo 4 1000 2000 1500 90 90 100 -1
    servo 5 1000 2000 1500 40 40 100 -1
    servo 6 1000 2000 1500 90 90 100 -1

    But the only resource allocated to a servo is Servo 1:
    resource SERVO 1 A01
    resource SERVO 2 NONE
    resource SERVO 3 NONE
    resource SERVO 4 NONE
    resource SERVO 5 NONE
    resource SERVO 6 NONE
    resource SERVO 7 NONE
    resource SERVO 8 NONE

    In Betaflight GUI, on the Motors Tab it is Servo 6 that reacts to physical yaw deflection (pic attached) and in the Config Tab Mixer section the servo is labeled S1 – but this my be default and doesn’t change.

    I don’t know what resource is associated with PWM 5 on my board, but that is where I connected the servo (and I have tried the googler).

    I don’t understand why it appears to be Servo 6 that reacts to yaw deflections in the motors tab.

    I’m pretty sure my tail servo is non responsive because I don’t have the proper resource set (and maybe other mis configured settings) but I do not know how to fix them.

    One last thing: I am still using David’s PDB but I brought battery power and ground up to the battery inputs on the Omnibus for power and OSD Voltage. Betaflight does not seem to be reading the Onboard ADC voltage (assuming this gets pulled from the battery inputs and is current independent).

    • This reply was modified 3 years, 2 months ago by Cshep70.

    Dear All, after nearly one year loosing a bit of interesst in Tri´s I just want to start again with Davids Mini Tri based on the RCF3 board. I´m still on triflight 0.5. Therefore i need to use the old cleanflight 1.23 configurator. I would like to test the new triflight 0.7 beta 3 Version and wondering which configurator I need to use.
    With my quads I´m on the cleanflight 2.2.0, Betaflight 10.4.0 configurator and inav 2.0.0 rc3. I do not want to mess up my excisting triflight setup therefore i would be happy if someone could give me an advice which one to use. Another question is want to do with the cli dump. Could the dump be copied for starting because diff all is not a valid command in CL 1.23. what’s about resources. Do I need to change it? What about the feedback measurement? Is it necessary to do any adaptation when using the beta software? Maybe a 0.7 Beta 3 clip dump for an rcf3 board would be helpful

    Thanks a lot

    Thanks for your advices

    Greetings out of Germany



    Hi Norbert, I flashed triflight 0.7 beta 3 Version with Betaflight 10.4.0 and had no problems. I flashed my big V4 tri. I still need to raise an issue on the forums but after flashing I could not arm the quad even though I checked that the radio signals were good and the Aux channel as activating other functions, the Tri would not arm. I am running a PPM receiver ( this tri is a slow cruiser not a 5″ freestyle rig!). After flashing back to triflight 0.7 beta 2 everything worked fine again using the same Diff setup.
    What tri are you building? I am happy to share my diff with you if you would like.


    Hi good people, this might have already been posted but here goes anyway.
    On the weekend I decided to covert my V4 tri running 10″ props and PPM receiver to a longer range rig and I wanted to covert the receiver to crossfire. I was flashed with triflight 0.7 beta 2. I thought that if I was doing the conversion I might as well go to the new triflight 0.7 beta 3, so did a diff backup and I flashed the new level. I connected with Betaflight 10.4.0 restored my diff and changed the receiver setup to crossfire. A strange thing happened….the top 2 channels in the receiver tab were not separated (yaw and roll I think are the top two) but the one stick command operated both channels and the other stick command had no effect. I checked my Taranis and it showed that the channels were separated and operating correctly. I changed back to my PPM receiver and the tri would not arm no matter what I tried. I flashed back to triflight 0.7 beta 2 and did not restore my diff but only setup the arming switch (so no other influences would be present) with the PPM receiver and the tri armed. I flashed triflight 0.7 beta 3 and did exactly the same thing (setup the arming switch only on my PPM receiver) and it would not arm!
    So I am now back to triflight 0.7 beta 2 with my original diff restored and everything works again using my original PPM receiver.
    Anyone have any idea what the issue is?
    Has anyone run crossfire on triflight 0.7 beta 2 or triflight 0.7 beta 3 ??



    @bassmaniac thanks for your Note that you would like to share the diff with me. I allready build a minitri based on the rcf3 flashed with triflight .5. As I wrote I would like to change to triflight .7 beta 3. A diff would be perfect even if you use the v4. As long it is the same board the diff would be a good start point.
    Back to your not arming point. Did you do the on bench tail tune procedure and save the results? Another point could be that arming is blocked when the Tri is not leveled and arming is blocked when USB is connected.

    • This reply was modified 3 years, 2 months ago by norwenkel.

    0.7b3 + original minitri = ok (almost)

    I picked up my old minitri (with integrated NAZE) that had been resting for two years. Found out I couldn’t connect with the updated configurator so I took a chance on upgrading from 0.5 to 0.7b3.
    Most things on default, except for radio and rates. Performed motor calibration. Performed the whole tail tune procedure.
    It flies reasonable well for me. So far only angle mode, but pretty aggressive.

    One new issue. Sometimes when I arm, one of the motors will not start. I tried once to give it a little more throttle, but of course it just flipped over. Dis-arm and arm usually work.
    Wanted to see what the BLHeli suite said about the ESC’s, but couldn’t get that pass-through to work.
    Any ideas?


    I haven’t used the configurator in awhile but I think you can increase the throttle level at idle? I can’t recall the function name. But that will help all your motors arm if one is not turning due to too low of a value.


    Hi @norwenkel, thanks for the thoughts, but I levelled the tri, did the accelerometer calib. and still would not arm, I also disconnected the USB and nada, nothing. No I did not do the bench tailtune as I don’t believe it should be necessary and it has not been needed in the past. I also reflashed 2x to be sure it did not have a bad flash. As I said, I went back to the beta2 version and the tri armed with no levelling calibration or tailtune being done.
    @billyd, yep I also raised and lowered the idle throttle level to different levels and also checked my small angle.

    My mystery continues and when I have more time I will try again but would I still will welcome suggestions.

    @norwenkel, here is my diff 🙂


    @bassmaniac thanks lot. I still have no clues about your arming problem except the ones I already mentioned. Keep us informed and happy flying



    Well arming needs
    Calibrated escs
    Properly programmed tx
    Properly bound rx
    Rx connected to flight control properly
    UART setup correctly for Rx
    Tricopter accs calibrated and aircraft relatively level
    Rx sending low throttle signal to fc and in turn to esc’s
    esc’s functioning properly with correct firmware and configurator set to proper type of esc firmware
    throttle signal properly sent to expected channel of rx and rx properly configured for expected channel arrangement in firmware.

    That’s all I can think of…


    “No I did not do the bench tailtune as I don’t believe it should be necessary and it has not been needed in the past.”

    But I believe it is necessary in the latest release, there was some logic added to make sure the servo fdbk is producing sane tail angles. Worth a try.


    HI @billyd, thanks for the thoughts and yes I went through all of those and it all works with triflight 0.7 Beta 2 but not the Beta 3.

    @jihlein, I agree, worth a try so I’ll give it a go this weekend if work allows.

    Thanks guys.

Viewing 12 posts - 106 through 117 (of 117 total)
  • The forum ‘Everything about everything else’ is closed to new topics and replies.