Forum Replies Created
I don’t know the dx8, but if you have enough channels for arm switch, mode switch (acro, angle, horizon) and two spare for other betaflight/triflight mode functions, it should work.
That being said, the taranis and other open tx transmitters opens up a lot of options that older radios don’t offer, such as telemetry, Lua scripts, etc. I rely on the taranis functions to call out battery voltage warnings and timer values which leaves you free to concentrate on the flying and not having to look down at your transmitter.
I started with tricopters 3 years ago as my first multi-rotor. Because I was a noob at flying and at tuning, I did a lot of repairs … It cost me a few arms, tail servos and even fc boards. If I would start knowing what I know now, I would start with a quad. Much more robust. When you have the quad down pat, the tri is much easier to fly.
Flying something that doesn’t break as easily allows for faster progression in skill, as you gain confidence by trying and succeeding in more risky manoeuvres.
The F3FC from RCE does not have an OSD. The 3amp bec is able to drive all sorts of peripherals such as an external OSD.
The hex file is not compatible with current versions of betaflight Configurator. You will need older version of Configurator (from GitHub?) or go to the 0.7 beta 2 hex file, which is stable enough. I got it on all 3 variants of RCE tricopters.
Thanks mate. Did some research and I believe the issue is in part that triflight is based on BF3.1.7, while BLheli 32 pass-through requires BF3.2. I was thinking I may need to desolder etc as you suggest, but I would rather get some non 32 bit ESCs and create a consistent set of escs.
It is with the BLHeli Configurator (your first link) that I see the little bees but not the Aikon 32.
I did run BLHelisuit using the Wine app, but no joy in getting it to see any ESC, but I suspect I have some comms issue. I recall now how I have used the BLHelisuit in the past, using arduino. Pain in the butt as well …
Remind me how to set them up individually? I run Mac and recall from the early days that I had lots of grief to configure the ESCs.
Would like to try it. Keen to know how easy it is to find the step response sequences in the recordings. It looks like a easy, systematic process to tune the pids.
Bought at Jaycar in Australia
Kevin, I spray my fc boards with laquer spray to isolate them against moisture or other fod causing shorts. Worked well for me so far. In the naze 32 days I lost a few boards due to shorts.
I would guess the props are not compatible with the motors.30 April, 2018 at 22:16 in reply to: Can i use one of the F3FC UART ports for my Graupner GR-16 Receiver? #57721
As far as I recall it depends on the firmware that you run. I think I saw yesterday that these ESCs can do dshot 600.
I can just say that the tricopters (all three models) from David gave me immense pleasure. I did buy stuff also from flitetest, BG and HobbyKing. Sometimes the experience is better than others. I started flying tricopters on the flitetest electrohub on nase32. What I found was that it is challenging to follow advice on this and other forums. Especially when the perspective is lost a little bit. It is easy to think one’s own experience, budget and overall context apply to others asking questions. Those questions and the answers often have gaps in them, which only gets filled by your own experience and reading of many answers.
By the way, I crashed and rebuilt many times. Part of the fun is troubleshooting and upgrading when you rebuild 🙂 They are all stock.
After another look at your pics and the video I think it is a panel resonating at a specific frequency (motor speed) combined with propwash. Check if there is movement or flex in some of your custom parts.