19 October, 2018 at 10:33 #59993
I don’t see much recent development activities on Triflight, but nonetheless I would like to ask how easy it would be to use it for another board.
I own a couple of Elle0 boards that were designed for paparazzi, which have an STMF4 with 1Mb of flash.
From the FC target list available in Triflight I can see that an HEX is being generated as firmware, but I have the feeling that the specific board is not configured for the servo positioning wire feedback.
Could anyone help / suggest me the best way to get this implemented?
D19 October, 2018 at 16:49 #59996
I don’t see an existing target file for that board, so you would need to take the pinout functions diagram of the board and create the necessary target.h and target.c files that define the resource mapping.21 October, 2018 at 09:59 #60009
the board target is under tree/master/src/main/target/ELLE0
I am looking at the RCEXPLORER3F3 target example. I believe I have to specify somehow an ADC in for the servo position voltage and enable the servo feedback with an option like :
#define TARGET_BOARD_IDENTIFIER <ADD SOMETHING HERE…>
#define DEFAULT_SERVO_FEEDBACK_SOURCE TRI_SERVO_FB_RSSI
Furthermore I have seen that, other enabled boards dont have the same pattern for the servo feedback settings (i.e. DODGE)
not sure …. help is much appreciated here.21 October, 2018 at 16:21 #60011
There appears to be only two ADC inputs available on this board, one is defined for battery voltage monitoring, the other is for current monitoring.
While I don’t recall the exact CLI command, you can use the CLI to specify which ADC input (Virtual, Current, RSSI, EXT1) to use for servo fdbk. With this board, your only option is Current, so using the CLI set the current monitoring ADC pin for servo fdbk. No changes to the existing target code required.
You could modify the existing target files to “steal” an ADC capable pin from an existing function and define it as either the RSSI or EXT1 input but that gets complex quickly and leaves you with non standard firmware to maintain.16 January, 2019 at 18:02 #60870
Ok, while waiting on new parts from David’s shop, I decided to reuse a DYSF4 FC stick it into my tricopter, flash it with triflight-0-7 OmnibusF4 target… but I’m having some issues locating the pads for the servo and notice when yawing left right the motor spins! SO, does any one try to use a DYSF4 on tricopter configuration? So far… no success… :.-(
Ed24 January, 2019 at 08:54 #60942
I have a question about arming. I setup the AUX for arming and everything but when I try to arm on my controller the arm tab in betaflight would not light up. Does anyone know what is wrong?
Cindy24 January, 2019 at 14:59 #60948
It’s been awhile since I’ve gone through the setup process but that can happen when you don’t have everything else set up yet. I am assuming you’ve done the receiver setup and did the subtrims, travels and directions to match the screen display? Also the modes tab lights won’t work unless you have the main battery connected. Obviously do all that without props.24 January, 2019 at 16:17 #60949
well… have you try out not plugged into the computer and verify it arms? lol16 February, 2019 at 23:56 #61095
so i have not flown my baby tricopter in a while and i was getting the itch but i didnt remember how i had it set up so i went to plug it into cleanflight and that didnt work as my firmware is so old so i figured i would update it and i cant seem to get it to flash new firmware either so i put it back on my wall and came straight here. i have the baby f3fc and need help flashing new firmware thanks
You must be logged in to reply to this topic.