(29-Dec-2020, 04:37 PM)Ress Wrote: This is the same FC on Protek35 right? Can we use flysky ibus recievers on that?

You can use Flysky receivers on any FC that has a spare UART.

For those who aren't aware, there appears to be an ESC hardware design flaw with the iFlight Beast H7 55A FC. It's not really a surprise TBH based on past iFlight history of bad FC design & QC.

The hardware issue prevents one or all of the ESCs working when bi-directional DSHOT is enabled when using JESC or BlueJay ESC firmware, or BLHeli_M firmware other than version 16.71. The same issue also occurs on Betaflight 4.3.0 (currently still in alpha testing) with any version of BLHeli firmware. The only combination that seems to work is Betaflight 4.2.x and BLHeli_M 16.71, although there may still be some risk involved with using those firmware versions for people wanting to use bi-directional DSHOT and RPM filtering. Roll the dice and take your chances.

iFlight are aware of this issue but it doesn't look like it can be fixed with firmware alone, so they are talking about releasing a V2 board with a hardware fix on it. I wonder if they will offer free replacement V2 boards to all the people who paid $90 for their defective V1 FC's. I guess we shall have to wait and see.

(24-Mar-2021, 01:23 PM)SnowLeopardFPV Wrote: For those who aren't aware, there appears to be an ESC hardware design flaw with the iFlight Beast H7 55A FC. It's not really a surprise TBH based on past iFlight history of bad FC design & QC.

The hardware issue prevents one or all of the ESCs working when bi-directional DSHOT is enabled when using JESC or BlueJay ESC firmware, or BLHeli_M firmware other than version 16.71. The same issue also occurs on Betaflight 4.3.0 (currently still in alpha testing) with any version of BLHeli firmware. The only combination that seems to work is Betaflight 4.2.x and BLHeli_M 16.71, although there may still be some risk involved with using those firmware versions for people wanting to use bi-directional DSHOT and RPM filtering. Roll the dice and take your chances.

iFlight are aware of this issue but it doesn't look like it can be fixed with firmware alone, so they are talking about releasing a V2 board with a hardware fix on it. I wonder if they will offer free replacement V2 boards to all the people who paid $90 for their defective V1 FC's. I guess we shall have to wait and see.

The GitHub issues https://github.com/betaflight/betaflight/issues/10619 and https://github.com/betaflight/betaflight...-750838199. I was considering the H7 to go with a 2Fiddy frame but fortunately bought the F7 before knowing about this problem.

(24-Mar-2021, 01:23 PM)SnowLeopardFPV Wrote: For those who aren't aware, there appears to be an ESC hardware design flaw with the iFlight Beast H7 55A FC. It's not really a surprise TBH based on past iFlight history of bad FC design & QC.

The hardware issue prevents one or all of the ESCs working when bi-directional DSHOT is enabled when using JESC or BlueJay ESC firmware, or BLHeli_M firmware other than version 16.71. The same issue also occurs on Betaflight 4.3.0 (currently still in alpha testing) with any version of BLHeli firmware. The only combination that seems to work is Betaflight 4.2.x and BLHeli_M 16.71, although there may still be some risk involved with using those firmware versions for people wanting to use bi-directional DSHOT and RPM filtering. Roll the dice and take your chances.

iFlight are aware of this issue but it doesn't look like it can be fixed with firmware alone, so they are talking about releasing a V2 board with a hardware fix on it. I wonder if they will offer free replacement V2 boards to all the people who paid $90 for their defective V1 FC's. I guess we shall have to wait and see.

Hi Snow,

So, it is only an issue with Bi-directional DSHOT?  If that is not used should it be ok?

It looks like iFlight have actually already released a V2 of the Beast. I thought it was just something in the pipeline but it seems to be out already.

Source: https://www.facebook.com/iflightrc/posts...2698821493

iFlight Wrote:iFlight BEAST series V2 released ?

Upgraded Blheli32 and BlheliS AIOs for even more power (up to 55A). Optimized circuit, larger solder pads and external USB access. The highest performance AIO just got better in different versions for every pocket.

So what can I expect from my original Beast FCs? Are they going to work for awhile then die? I don't generally change firmwares so mine are totally factory stock. Just wondering what will happen when I fly one?

(24-Mar-2021, 07:28 PM)iFly4rotors Wrote: So what can I expect from my original Beast FCs? Are they going to work for awhile then die? I don't generally change firmwares so mine are totally factory stock. Just wondering what will happen when I fly one?

You'll probably be fine as long as you don't use bi-directional DSHOT / RPM filtering, or you take a gamble and use one of the workarounds. See the link to the GitHub post below that was posted by Fiction in post #18...

https://github.com/betaflight/betaflight...-750838199

Hi Snow,

Thanks. I hadn't planned on changing anything. I always like to try an FC just as it comes from the factory; other than setting modes and OSD. As long as it works, I probably won't change anything.

Thanks for the info.

Here’s a LOS flier pushing the beast AIO very hard.

Wow. Remember when we were all complaining about the thought of paying $90 for one of the iFlight Beast H7 AIO FC's. Well, with the chip shortage and supply chain issues they are now $145 USD which is just insane. Imagine blowing an ESC MOSFET and then being out of pocket by nearly $150

https://shop.iflight-rc.com/Beast-H7-V2-....5-pro1588

(28-Mar-2021, 01:28 AM)Rob3ddd Wrote: Here’s a LOS flier pushing the beast AIO very hard.

he tries it on 2005 motors on an ultralight quad, their max current is 25a... not even touching the half ampdraw of the raitings of that board. sadly thats not any sign about the promised performance...
never saw someone used it as it would be rated for.

Hi Bat,

So, what do you think a fair test for the iFlight BEAST 55A FC would be?

What do you think about using the iFlight BEAST 55A FC with 2306 2400 Kv motors spinning 7 inch props ??

$145 is too much money to risk over an AIO from iFlight given that they don’t have the best record making FC/ESC.

They make decent motors but their electronics has been yeah-so-so.

There is not enough evidence of people flying this AIO on proper 5” quads.

The last AIO 1S board they made had gyro issues and eventually blow ESC’s. Not an apples to apples comparison but same brand same quality.

I am not completely clear on their replacement warranty. Probably we all know the answer to that question.

On a build that requires 55amp, you will have enough space for a proper stack and the weight savings is negligible.

"So, what do you think a fair test for the iFlight BEAST 55A FC would be?"

https://m.racerstar.com/4pcs-racerstar-a...p-341.html
as example this motor on 11" and 6s should draw close to 55a - this direction

or just as a 5inch racer, not at all for cruising;
the freeflight motor at 2400kv on 5s, as the requirements matches the beast:
https://brotherhobby.com/vs-2207-motor-p00195p1.html
or maybe the gom 1900kv on 6s?
https://brotherhobby.com/gom-22075-motor...190p1.html

DrainMan FPV needs to put the iFlight Beast H7 through his ESC torture test chamber. Then we can see how good that AIO FC really is, or I should probably say, just how quickly it goes up in smoke. I can't believe MOSFETs that small can be useful for anything. Certainly not on a proper (not lightweight) 5" freestyle or race quad that is capable of drawing the full 55A (that it is supposedly designed to withstand) on each ESC.