Forum Replies Created

Viewing 15 posts - 436 through 450 (of 464 total)
  • Author
    Posts
  • in reply to: Triflight 0.6 RC1 #34855
    LitterBug
    Participant

    I’ve been doing a bunch of Quad flying on BetaFlight running stock PIDs and it has been rock solid for my variety of quads. I’ve been doing much the same leaving PIDs stock on the Baby Tri running TriFlight 0.5. I have a good grasp on tuning quads, but the tail tuning throws a new set of variables into the mix for the Baby Tri. I’d like to dive into more actively tuning the Baby, as it does have a few characteristics that I think should be able to be tuned out. Waggle foremost, and the twitches that happen during rapid throttle change or during some acrobatic maneuvers. Are there any good guides geared more on Tricopter tuning? I’d like to get a handle on the tuning before swapping the rather mellow 2205 2100kv motors on 3 and 4S out for some insane 2207 2450s on 3 thru 5S. I’ll be adding an OpenLager to the F3FC on uart3. I’m sure that will help me understand what is going on too.

    Cheers!
    LitterBug

    EDIT: I have read through the triflight setup guide HERE I’m looking for more info on the additional CLI commands that TriFlight introduces.

    in reply to: Triflight 0.6 RC1 #34854
    LitterBug
    Participant

    Great info Lauka!

    Thanks!
    LitterBug

    in reply to: Servo feedback speed, post your results #34852
    LitterBug
    Participant

    1. Blue Bird BMS-210DMH
    2. 5V
    TriFlight 0.5/F3FC 1.13.0 Jul 24 2016
    # get tri_tail_servo_speed
    tri_tail_servo_speed = 268

    in reply to: Triflight 0.6 RC1 #34850
    LitterBug
    Participant

    With the in-air tailtune, what is being measured, and after what changes to the vehicle would it need to be rerun? Are the results stored in a parameter that can be viewed from CLI, or are they still hidden in flash?

    Cheers!
    LitterBug

    in reply to: Triflight 0.6 RC1 #34840
    LitterBug
    Participant

    @lauka I had noticed higher than normal CPU utilization too. Thought about adjusting the looptimes, but the latest cleanflight configurator has moved things around to the point where it wasn’t obvious where to go. Wanted to get in the air this weekend and didn’t spend a whole lot of time on it. Everything was fine when I went back to 0.5 and flew a few packs through yesterday. Fortunately doesn’t look like there was any permanent damage to the motors. Not kidding, these things were smokin after 30 seconds on 0.6. Sounds like adding logging isn’t going to be much help at this point, so I will hold off on 0.6 for now unless you have any suggestions or updates.

    Cheers!
    LitterBug

    in reply to: Triflight 0.6 RC1 #34776
    LitterBug
    Participant

    Flashed back to 0.5, restored settings, and motors are running cool and smooth again. I had noticed the motors sounded really gritty when on 0.6.

    Cheers!
    LitterBug

    EDIT: I attached the Triflight settings I used for 0.5 and 0.6 for comparison. Basically just defaults plus rates and RX config are what I used in both cases.

    in reply to: Triflight 0.6 RC1 #34771
    LitterBug
    Participant

    I tried running a tailtune on my baby tri with stock .6 PIDs and it about fried my motors in less than 30 seconds. Don’t currently have BB logging, but I’d bet there was some serious oscillations causing the heat. Going back to .5 to see if it flies like it used to. Also going to add a serial logger.

    Cheers!
    LitterBug

    EDIT: running motors manually from Motors tab does not result in hot motors.

    in reply to: Triflight 0.6 RC1 #34700
    LitterBug
    Participant

    I Have 0.6 installed on my F3FC Baby Tri. Waiting on good weather and daylight to give it a fly. I’m going to start from scratch on the tuning since I hadn’t gotten too far anyhow.

    Cheers!
    LitterBug

    in reply to: Sunset rip with the Baby Tri #34527
    LitterBug
    Participant

    FYI… Running MicroMinimOSD with MWOSD 1.6.2 firmware.

    Cheers!
    LitterBug

    in reply to: Sunset rip with the Baby Tri #34526
    LitterBug
    Participant

    My Amps read a tad high with the recommended settings. If I run a 1550mah pack through to 1600mah on the OSD, I still have about 15-20% left in the pack. Going to do a calibration with an inline power meter soon. Been having fun playing while we still have daylight after work. Tried a few different props. Currently the Gemfan 5050 tri blades are my favorite for my setup. Still wish I would have gone with higher KV motors. Even with the 2100KVs, my buddy at the field is floored by how fast it is for a Tri and he’s been flying planks, full scale, and all size and configuration multi rotors for a long long time.

    Cheers!
    LitterBug

    in reply to: Baby Tri LOS Maiden #34365
    LitterBug
    Participant

    Ran a tail tune at the field last night with my old settings. Ran like a charm in under 30 seconds. There is not that big of a difference between the stock and recommended settings that I can see would make it run vs never beep and complete. Weather permitting, hope to try the recommended settings again tonight and do another tail tune test.

    Cheers!
    LitterBug

    in reply to: Help My F3FC is stuck in DFU mode #34124
    LitterBug
    Participant

    Is the boot button jammed or is something resting up against it?

    Cheers!
    LitterBug

    in reply to: F3FC reports extreme current draw #33989
    LitterBug
    Participant

    I can confirm that moving my OSD from UART2 to UART1 did in fact fix the current measurement problem on my Baby Tricopter/ F3FC Racing / Baby PDB build. Thanks to all that contributed to this thread for an easy fix for me!

    Should the Documentation be updated for the F3FC to state that UART2 should only be used for 3.3V IO? Should it also recommend that Spektrum recievers be connected to UART2 since they are also 3.3V?

    Cheers!
    LitterBug

    in reply to: Baby Tri LOS Maiden #33962
    LitterBug
    Participant

    I switched back to my old config the other day that had passed the tail tune. Flew fine with no waggles.
    Here’s the only differences there were from stock TriFlight with a good tail tune, to updating with the recommended settings.

    Cheers!
    LitterBug

    Attachments:
    in reply to: Baby Tri LOS Maiden #33896
    LitterBug
    Participant

    tri_tail_motor_thrustfactor = 50 is set as one of the preconfigured setup parameters. Wasn’t any wind the last time I gave it a go either. Hmmmm. Guess I will try double checking the RC inputs, ESC calibration, and level then give it another go.

    Cheers!
    LitterBug

Viewing 15 posts - 436 through 450 (of 464 total)