[hertz]

Still not sure what F7 issues you’re talking about. I’ve spent a good amount of time to ensure F7 runs faster than F4, and it also has no inverter problem.

[hertz]

Well, if Osprey flies with a pilot inside, then FPV on bicopter should be possible 🙂
Maybe not the kind of FPV we’ve got used on Tris and Quads, but should be manageable. Maybe the camera should be actuated based on the angle of attack.

Please no F4 FCs anymore, go for F722RE 🙂

@Kevin_Erik
>What I understand about F7, it has some major firmware issues.
What issues you’re talking about?
Chances are they’ve been solved a while ago: https://github.com/betaflight/betaflight/pull/5674

[hertz]

The increase associated with F7 isn’t massive though. I’ve worked hard on making BetaFlight work nicely with F7 and it’s now measurably better than the F4, but there’s not much more to be gained.

The performance of memory subsystem and the FPU is the same for F7 and F4 overclocked to the same frequency, some benefits come from F7 having ITCM-RAM and ITCM-FLASH interfaces for the most critical parts of the code, but it’s still not a major breakthrough.

H7 will have a much bigger benefit, and we’re also looking into using Cortex-A5 dual-core CPUs as the future steps.

[hertz]

Latest revision of QX7 have a SPORT marked port on the bottom, previous versions as well as the X9D(+) required you to use the JR module bay connector, but that’s basically the same procedure.

Are you sure it doesn’t support your particular toy quad? It’s best to consult RCGroups on this one or find the GitHub page for Multi-protocol TX module firmware, there are lots and and lots of supported models and most of them share the same protocol. Maybe your’s will work with some other model but with e.g. channels swapped, which is not a problem for a programmable radio with OpenTX.

[hertz]

Each of XSR, XSR-M, X4R-SB, and XM+ has SBUS and the lowest delay possible for FrSky, no worries. Just pick whichever you like most from it’s price/appearance point of view, and whether you need telemetry or not.
If you want signal strength, then you’re XM/XM+ aren’t viable because they don’t have any telemetry, even RSSI.

With a Taranis, changing firmware on receivers is a piece of cake, just put an appropriate HEX file on your SD card, plug receiver into Taranis upgrade port and flash it from Taranis menu.

Latest EU-LBT promised equal or better range than International firmware and was overall a more up-to-date version, International firmware hadn’t been updated for a while.

[hertz]

CE vs FCC is determined by firmware flashed onto your internal TX module and RX, you can replace it.
Living in Russia with virtually no regulations, I used International (FCC) firmware at first, but then moved to a EU-LBT firmware.
I’d recommend going with a XSR, XSR-M or X4R-SB receivers if you’d like to have telemetry, or XM+ if you don’t need telemetry.

There were rumours of Hall Gimbals coming for QX7, and they probably will, but FrSky is a slow manufacturer.
They’re releasing R9D 900MHz system soon btw, which you’ll be able to plug into your Taranis (either X9D or QX7) and get a solid long-range link with SBUS and SmartPort telemetry.

[hertz]

Go with a Taranis!
You can also get a multiprotocol module for it which may allow to control your existing toy-quads.

[hertz]

BG solder is fake Asahi, it sucks big time. Real Asahi is awesome, but I’m not sure where you could get a reel. I have one which I’m currently finishing, but there’s also Kester which I love and will be using after Asahi runs out.
Amazon is full of offers on Kester 63/37.

[hertz]

X-series receivers require a FrSky radio or XJT module to bind with, I’m not sure Aurora 9x is compatible with X-series receivers unless you have an JR XJT module.

[hertz]

I’ll look into it during this weekend for BetaFlight.

[hertz]

@swissfreek that’s why I added this feature, so you could flash your Vendetta 🙂 Let me know how it works for you!

This code for flashing Atmel was written at the same time as SiLabs, but I had no chance to test it until now, and I don’t like releasing an untested product. Now it is tested and working solid.

[hertz]

I was being ironic 🙂

[hertz]

It does Atmel since I’ve released v1.0, tried it on my Mini Tricopter DYS SN20A ESCs from the original package, both SimonK and BLHeli bootloaders supported.
P.S. Actually, if you look very carefully at the screenshot, you could see that the first ESC on it is DYS SN20A 🙂

[hertz]

@lauka Parameter Groups are actually there in BetaFlight, just not used throughout the code yet, but Martin expects the switch to PG to occur before BF3.2 is out. Any new parameters can be added using the parameter groups now if I understand correctly.
We would be happy if you join us at BetaFlight’s slack channel 🙂

@unseen I noticed it became very slow in accepting PRs and new features, not sure about stability as I don’t fly it at the moment. Would be interesting to see usage statistics of CF vs BF vs TF vs iNav.

[hertz]

@unseen, wow, you’re also there 🙂 My RC adventure has started from this forum.

without the parameter groups in Betaflight

I think Martin is working on it at the moment, would you consider the rebase after PG are implemented into BF? I’m willing to provide assistance if necessary 🙂

The CPU load issue is not fixed, which I find quite weird.

Look at the possibility of using per-file aggressive optimization flags like BF3.1 does in latest commits, -Ofast improves the situation quite a bit for F3 targets. No luck for F1 though due to increased code bloat.

P.S. If you have time and will, join BF https://betaflightgroup.slack.com for discussing incorporation of tricopter matters into BetaFlight. I can invite you if you let me know your email address, mine is [email protected] .

[Author]

Posts