Hello All,, 

Been out of hobby for sometime.
Last week bought a Betafpv Meteor65 Pro (2022) Frsky SPI version 
My transmitter is, Taranis X9 Lite with open Tx version 2.3. (If I am right, it should support both ACCST and ACCESS)

Now for binding, 
Do I just create a model in Tx set to ACCST-D16 and in betaflight issue bind_rx command and then press bnd option in TX?
Will I be able to get voltage displayed on the Tx (like how I used to get that in frsky r-xsr)?
What version of configurator I should use? I confirmed that FC is flashed with 4.2.11? I have 10.7.0 version configurator installed already, can I use that?

Finally,
At some point, will I be able to flash latest betaflight firmware on this? Or what I have on the FC is some custom firmware and I am stuck with that?

Thanks.

you have all the firmware options, from betaflight 4,2 up to 4,1. you could go for emuflight or quicksilver

(15-Apr-2023, 07:24 AM)hugnosed_bat Wrote: you have all the firmware options, from betaflight 4,2 up to 4,1. you could go for emuflight or quicksilver

I am going through F4 1S 5A AIO Brushless Flight Controller and it says,

For the SPI Frsky version, DO NOT flash the other firmware, otherwise, the RX will be lost in control at a very close range. We have already built our own firmware betaflight_4.2.11_BETAFPVF411RX for SPI Frsky RX version to support BMI270 gyro

So now Beta has their own proprietary Betaflight versions . . .  

Their "own" firmware is garbage and shows their electronics aren't compatible with the standards all the other companies use so their boards will work with Betaflight and it's updates and the other flightware like Hug mentioned, and more. All that proprietary flightware makes it a lot harder to troubleshoot problems too. What you would normally look for & change settings or upgrade to cure the problem may not even be available in their software, like on their Silverware boards.

I have a Jumper multi protocol, and not familiar with the Frsky radios, but it sounds similar. I set up a model, usual switches scroll down to Frsky, which I doubt you have to do, but I just pick either the D8 or D16, I think Frsky & FrskyX, do the bind in the cli, click the Bind button on the radio & it hooks right up. I've had a bunch on onboard Crazybees in Fr & Fly sky & a couple DSMX, and they bind up pretty easy. What you wrote typed sounds like it would work for me.

(16-Apr-2023, 08:18 AM)Brian_OH Wrote: So now Beta has their own proprietary Betaflight versions . . .  

Their "own" firmware is garbage and shows their electronics aren't compatible with the standards all the other companies use so their boards will work with Betaflight and it's updates and the other flightware like Hug mentioned, and more.

The problem is BMI270 requires BF 4.3.1 AFAIK and I couldn't get an SPI FrSky to run on 4.3.1, but it ran fine on 4.2.11.  So the only way out they had was to build their own firmware for it.  As ever, you may have some advanced skills in hacking firmware, but I spent like 4 hours trying to fix it, only for Snow to suggest I put 4.2.11 back on it, which made it work again. Why they changed to BMI270 is beyond me. ICM20689 on SPI FrSky is fine.

@OP. Personally, I would run Quicksilver on it if you have a hard on for upgrading it.  You will get less hassle doing it that way.  Or leave the firmware as it is.  If it flies, then why try and intentionally break it?

(16-Apr-2023, 04:10 PM)Pathfinder075 Wrote: The problem is BMI270 requires BF 4.3.1 AFAIK and I couldn't get an SPI FrSky to run on 4.3.1, but it ran fine on 4.2.11.  So the only way out they had was to build their own firmware for it.  As ever, you may have some advanced skills in hacking firmware, but I spent like 4 hours trying to fix it, only for Snow to suggest I put 4.2.11 back on it, which made it work again.  Why they changed to BMI270 is beyond me.  ICM20689 on SPI FrSky is fine.

@OP. Personally, I would run Quicksilver on it if you have a hard on for upgrading it.  You will get less hassle doing it that way.  Or leave the firmware as it is.  If it flies, then why try and intentionally break it?

First, I'd never buy a Beta electronic anything again, and would never pay their ridiculously high prices for their barely average quality products. All that proprietary krap of theirs just makes it way harder . . . "but I spent like 4 hours trying to fix it"  . . . and way too much like work just trying to get a factory quad in the air. I remember having to go back in BF versions, somewhere around 4.0.x, because some of the tabs weren't even coming up in latest BF configurator when I plugged the quad into the puter. NBD, but a hassle and more work that shouldn't have had to do, but BF is free & open source, and they really do one helluva job putting it out for us, and continually improve it . . . even with their share of bugs. Also with BetaFPV's "own" flightware, you're extremely limited in even doing an update by their own warning about doing it. And there's the confusion working out problems with Betaflight firmware vs BetaFPV firmware, and the back & forth trying to get what worked to fix a problem in BF vs working the same way with BFPV.

The cause of so many problems I've seen on the forums are from people, usually kinda new to the quads & BF. With how well the factory quads do fly outta the box any more, they've never flown it on BF, or just a couple times, and right away are all ready to start changing out the flightware when they'd never notice the difference between them if someone didn't tell them. With all the changes & intricacies of the custom firmware versions, it isn't as simple of a process as even just updating the version of BF, which itself has caused numerous problems for people not following the proper procedures, and upgrading "just because." I agree completely, and have always told my computer clients that too . . . if it ain't broke . . . . 

If you can get it set up & working, Silverware is flippin awesome. It's a very smooth, locked in feeling flying with it and almost seems to anticipate what you're going to do next. It's hard to describe, but as much fun as flying is anyway, the Silverware just makes it even more enjoyable. I still fly my brushed Silverware 65 whoopin through the house as much as my brushless, and will still get the bigger brushed Silverware Whoops outside to play throughout the outside flying season.

Just for clarification, Silverware and Quicksilver are not the same thing.

https://intofpv.com/t-the-difference-bet...uicksilver

I tested binding and a quick flight, it worked!. Rssi also displayed on OSD.
I think my goggles was not set on correct Band. Tomorrow will try to check again.
Thank you all, I shall post here if I have more questions

I have SPI FrSky on the Flea build, but it slightly differs in that it has the diversity version with two antennas. It seems to have better range than other standard D8s and signal was still good at about 100m away.

(17-Apr-2023, 12:24 AM)Pathfinder075 Wrote: I have SPI FrSky on the Flea build, but it slightly differs in that it has the diversity version with two antennas.  It seems to have better range than other standard D8s and signal was still good at about 100m away.

Is that the 12amp Crazybee board that's set up for a Pick with the closed mounting holes, and not the regular open end holes like the regular Whoop boards? I grabbed one of those a while back, but had trouble with the onboard, but I thought it was diversity Frsky D16 . . . my onboard doesn't want to work anyway, and am ending up putting an outboard receiver on it for a 3" Pick with the BH 1404/9500s. The HM videos I've seen with that board have the quad going out one helluva lot farther than 100 yards. It looked like they were pushing it out to where the outboard receivers would reach. 

I've always got a good solid 100 yards + from the onboard receivers on the Crazybees in Fr & Fly sky & the DSMX, and still fly them a solid three houses up & down from mine w/o any problems or drops. I have a Jumper, and it seems like the multi protocol radios have less problems with the onboards reception than a lot of the factory specific radios.

sim_tcr . . . glad it bound up, sounded like you had everything good for that. I'd fly it for a bit and see how you like it & give yourself a chance to get use to it for a bit before you decide if you need to change anything major with it. I'd hope even with Beta's proprietary stuff, you should still be able to tweak the flight characteristics in BF to your liking, and most all the factory quads . . . even Beta's, fly pretty good right outta the box.


http://sirdomsen.diskstation.me/dokuwiki/doku.php

https://github.com/NotFastEnuf/NFE_Silverware

https://www.rcgroups.com/forums/showthre...e-firmware

Going bit off topic.

My FrSky X9 lite radio shows “RTC battery too low” error.
I found that, there is a small battery inside the motherboard of radio. Is this battery important for the radio functionality? (It still turns on without that battery)

After few minutes radio turned on, I get a “SD card error” on the screen and then all voice features gone. (I know sounds comes from sd card)
I tried formatting the card and placed contents again, and same issue.
Can I buy a new sd card and try? (Hoping that fix it)
Could the above battery issue be the reason for this error too?

(17-Apr-2023, 04:42 AM)sim_tcr Wrote: Going bit off topic.

My FrSky X9 lite radio shows “RTC battery too low” error.
I found that, there is a small battery inside the motherboard of radio. Is this battery important for the radio functionality? (It still turns on without that battery)

After few minutes radio turned on, I get a “SD card error” on the screen and then all voice features gone. (I know sounds comes from sd card)
I tried formatting the card and placed contents again, and same issue.
Can I buy a new sd card and try? (Hoping that fix it)
Could the above battery issue be the reason for this error too?

You can experience some odd things happening when that button cell RTC battery starts to run out, so I recommend that you replace it ASAP.

(17-Apr-2023, 11:32 AM)SnowLeopardFPV Wrote: You can experience some odd things happening when that button cell RTC battery starts to run out, so I recommend that you replace it ASAP.

Do those batteries need to be replaced regularly or are they rechargeable? My Taranis has been sitting on the shelf for several seasons now, may have to give it a checkup.

(17-Apr-2023, 02:01 PM)mstc Wrote: Do those batteries need to be replaced regularly or are they rechargeable? My Taranis has been sitting on the shelf for several seasons now, may have to give it a checkup.

They're not rechargeable but they tend to last quite a long time. I only had to change the one in my X9D+ for the first time last year after 4 years of use.

(17-Apr-2023, 01:41 AM)Brian_OH Wrote: Is that the 12amp Crazybee board that's set up for a Pick with the closed mounting holes, and not the regular open end holes like the regular Whoop boards? I grabbed one of those a while back, but had trouble with the onboard, but I thought it was diversity Frsky D16 . . . my onboard doesn't want to work anyway, and am ending up putting an outboard receiver on it for a 3" Pick with the BH 1 404/9500s. The HM videos I've seen with that board have the quad going out one helluva lot farther than 100 yards. It looked like they were pushing it out to where the outboard receivers would reach.

Yes.  12A 2-4S.  I kind of like it as a FC.  Also being able to run up to 4S is a boon.  It is a diversity receiver (AFAIK), but i'm running D8 on it.  Don't know that running D16 would make any difference and a bunch of people told me not use D16 when I first got into this so i never bothered.  It will get ELRS with a dipole eventually (when I stop being lazy and just solder the damned receiver), but for now while it flies, I can't be bothered.  It's not really a quad I send out far, probably 100m max in general.  It's more freestyle than long range or cine.  But I have also seen the Cine8 videos that show maybe quarter of a mile range on it.