Home Forums Everything about the Mini Tricopter Howto: Taranis telemetry for the F3FC

Viewing 12 posts - 16 through 27 (of 27 total)
  • Author
    Posts
  • #31487
    bassmaniac
    Participant

    Photo 9 I do not understand. This is with the tri powered up , armed but throttle at zero. Where is this data comming from, but nothing is shown on the other telemetry screens

    #31490
    Deepnine
    Participant

    Telemetry setting has to be S.Port or Smart Port. On one Uart 2 or 3 . (img 6)

    Frsky is the older Telemetry type of Frsky. The XSR like the X4R, X6R and X8R only knows s.Port.

    And then TX and RX (of the UART you choose 2 or 3) have to be connected both to the one s.Port Telemetry wire. (img 4)

    And i suggest updating the Taranis to 2.1.18 telemery is handled a bit different (better).

    #31492
    efbe
    Participant

    Hi GAntonjo
    I am also trying to learn, in my case with the Tx9xtreme. And the FCF3 board.

    How did You connect the LED’s.
    I think I fried the board by connecting 16 addresable ADAfruit Leds directly to one of the UART 5V /GND connectors.
    Is separate converter batt > 5V safer ?
    Thanks,

    #31493
    Deepnine
    Participant

    It depends how the R8 restistor on you board is set. Is it set to BEC it should take up to 3 Amps without problems.
    Is it set to 5V then only 200mA can be drawn and you killed the LDO.

    F3FC Tricopter Frame (with integrated Power distribution)

    Instructions on how to select UART1 voltage and UART2,3 and PWM voltages:
    R8, which have the marking 5V/BEC sets the voltage output on UART2,3 and PWM5+6. If BEC is selected (which is the default) The voltage will be whatever the built in BEC voltage is set to (5V default) If a higher BEC voltage is selected (for instance 8V) the 0 ohm resistor can be moved to the 5V position. This will engage a small LDO voltage regulator that will supply the UART2,3+PWM5,6 with 5V power. The current rating on this regulator is rather small (around 200mA) so it’s extremely important that you don’t try and power LED’s through any of the PWM ports while using this option. This option is available so that sensitive UART devices that cannot operate on 6 or 8V can still be powered through the board without an external power source.

    #31504
    GAntonjo
    Moderator

    @efbe: I have powered my LEDs (Adafruit type) as follows: Din to LED pin on the F3FC, GND and V+ through a separate 5V BEC.

    I believe the “non-important” units should be powered from separate BEC in order to leave the on-board BEC for flight critical functions only. And, even though you may say that FPV cam and VTX are flight critical, I would power these from separate BEC too (and in fact many VTXes can be powered straight from the LiPo and has a BEC that can power the camera and OSD). The more “gadgets” added to the tricopter, the more “juice” is drawn from the BEC(s), and hence care should be taken to not overload the BEC(s).

    #31505
    efbe
    Participant

    @GAntonjo:
    Thanks,
    I think I am going to use the BabyPDB as a second Power supply, from the raw battery output.

    I think there should be “stickys” in the forum addressing al the possibilities of the F3FC, like
    Baro, GPS, OSD, ect.
    Because this is the same for Baby, Mimi and V4

    #31571
    bassmaniac
    Participant

    Thanks Deepnine for the pointers. I will make the corrections and try again. I will do some research on going to OpenTX 2.1.18 . Last time when I went from the OEM firmware to OpenTX 2.0.xx I bricked my Taranis and nearly had heart failure, but thankfully recovered lol. ( no lol at the time though). I will be back on the thread if I don’t come right. I will attempt on the weekend. Thanks again.

    #31640
    bassmaniac
    Participant

    Ok guys, still no telemetry (sad face). As per deepnines pointers higher up in this thread (reply #31490) I set my uart2 telemetry option to s.port and upgraded my TX firmware to OpenTX 2.1.8. I then powered up the tri, armed motors, set Taranis to search for sensors but I only get the following sensors : SWR,RSSI,RxBt, A2 . I seem to get nothing from the F3FC. My board connections with the XSR receiver are as per picture.
    Deepnine mentions that the RX & TX pins on the F3FC need to be both connected to the one S.port wire ( by bridging the RX & TX pins I presume)??? Surely the receiver s.port wire goes to the TX pin on Uart2? Can anyone confirm?? I am a noob to S.port telemetry and do not want to damage my board by misunderstanding this. Thanks.

    Attachments:
    #31643
    bassmaniac
    Participant

    SUCCESS ! The problem was a loose connection on the s.port wire pin. So all is now roses and sunshine and I am a happy camper. Thanks guys.

    #34077
    billyd
    Participant

    I have the baby tri stock setup and using the 9xd with x4rsb.

    I get all the telemetry readings but my current consumed is wildly in accurate. When I set it to ma in the 9XD instread of %, my radio reports 900mah consumed when only 400mah have actually been consumed.

    Is there a way to adjust this in the radio or in the F3FC board?

    By the way there is a nice beginners video on setting up the Taranis 9XD for use with a quad (very similar arrangement for a tri). It includes setting up telemetry for use on the 9XD with the X4RSB. by Rotor Riot here: https://www.youtube.com/watch?v=f40mXxzU4hY

    #34078
    norwenkel
    Participant

    Regarding telemetry there have been some changes made when using newer versions of OpenTx greater than 2.0x. That’s the reason for the different screens @bassmaniac.

    …. Sorry just realized that this has already been answered. By the way, i’m using just one wire for the s.port. F3FC Uart Tx to s.port at the x4rsb.

    #34083
    billyd
    Participant

    Regarding my post above I found if I alter the cleanflight current sensor scale to 544 (stock value is 360) for my stock baby tri I get the correct Fuel mah consumed on my 9XD tx and X4RSB rx.

Viewing 12 posts - 16 through 27 (of 27 total)
  • The forum ‘Everything about the Mini Tricopter’ is closed to new topics and replies.