With Betaflight cloud builds, the flash memory is no longer an issue. F722 having inverters we don't use anymore, doesn't really seem like a reason to "Be careful".
Warm greetings from Georgia, Mr. Simpson! I have started learning FPV from your channel and now I am starting an FPV school, all thanks to your kind, wise and smart videos I have watched back in the days! Wish you the best!
If anything, the f405 processors are gonna get a feature cut, since f722's are just faster + the memory constraint is almost irelevant since cloud builds are a thing now(you can just cut out features that you don't use and save on space). Also releases of hardware are an indicator - iFlight blitz stacks(only f722 and f745), Flywoo GOKU(only f722), darwinfpv cement (only f435 and f722) etc.
I’m picky about the flight controllers I use. Here’s a reason to use an F722 that has nothing to do with the processor itself. There are other features that I consider important. I want a barometer because it gives a more accurate altitude than just GPS and I want to have an indicator of whether I am within the legally allowed range. The 9 to 10v BEC needs to be able to support the most power hungry digital VTX units currently on the market. There needs to be a built in pit mode switch so I can turn off the VTX when initially getting satellites. There needs to be enough UARTs for GPS and i2C pads in case I want to do barometer are preferred but not necessarily required. I have found a few F722s that meet all these requirements but have not found any F405s yet that do.
@@craigcupit1917i had to set up a switch for my axis flying argus f7 aio to turn on vtx 😉 you might be able to set up a switch on others for it. I think it was a user 1 switch. Was a while ago. I wonder if i set up a user switch on others if it would work 🤔
I'm keen to get some advice on sbus and smartport. Currently I use frsky equipment and esc and use smartport telemetry to send it to my transmitter. I have a speedybee f405wing and a matek h743 wing. Is there a better way to to connect my receiver and telemetry?
FPort as someone else also suggested is the best option. If you have SPort working already then the wiring is already set up correctly except you can disconnect the sbus wire since it will not be used. With SBus, you need to put RSSI on a channel but with FPort, the value is available without using up a channel.
on my speedybee f722 the erls module will not commmunicate on CRFS but work on sbus, and yep inverted. same for geprc and skystars and RM rp1 receivers.
If you're using 03 cut the the yellow wire of the VTX cable. It's interfering with your elrs / Xfire. I had the same thing happen to me and when I checked the SpeedyBee f7 manual it indicates this as well. They suggest you cut / or eliminate the sbus wire (yellow) on the VTX cable for the 03. Hope this helps.
If you opt for a 405 controller, I think that it will not be compatible with the upcoming version 8 of iNav. I think that it will require STM32F7 based microcontrollers. In that case the STM32F405 would not be upgradable. Someone please correct me if I have that wrong.
@@FPVBites Ahhh, I learned something today so "thank you" for setting me straight. I didn't realize that the F411 is a stripped down F405 with slower max clock speed and some limitations on the real-time-clock that the F405 isn't subjected to. I checked with Perplexity and it spelled out the differences. I've always assumed that a larger part number meant it had "more good stuff". And yes, it appears that it's only the F411 that iNav plans to discontinue support for: ""INAV 7 is the last INAV official release available for F411 based flight controllers. The next milestone, INAV 8 will not be available for F411 boards."
What do you think of Artery AT32F435 mister? This new chip offers nice features above F405 and bellow F722, is this new chip worth to buy? Need more advice please
You will be stuck using betaflight 4.5 or newer or a fork that supports it. Or any other firmware that supports it. But otherwise, the at32f435 is the same size as an f405 and a couple bucks cheaper and faster so there’s not really any other downsides to using it aside from compatibility.
I found a forum topic with name "Betaflight Too Big?" and post writing this: F405 Region Size 922K Betaflight 4.3.0 with 43,6% usage. F722 (the bad versions with 512K not better versions with 1024K, STM32F722RGT6) Region size 480K Betaflight Betaflight 4.3.0 with 89,5% usage. So if you don't want to use a trimmed (cloud) new Betaflight OS, then FCs with 512K will probably no longer be sufficient very soon...
The RGT6 variant of the f722 doesn't exist, there is no mention of it anywhere aside from mislabeled listings. The F722 datasheet clearly says "up to 512Kbytes of flash". Only The F745/746/756 etc variants have 1Mb flash. And the F769 and F77* series which have 2Mb flash.
@@pvim Maybe you look at an old datasheet ? Github => Supported MCUs #197 => 4. F722. From what I could find, some FCs use the STM32F722RET6 (with 512 KiB of flash) while others use the STM32F722RGT6 (with 1024 KiB of flash)...
Stay away from them due to price, but if you need any of their features like additional UARTs or more motor pins than F405s allow, go for them. That's what he said previously
Aw shucks, I’m building a new micro with an iFlight Blitz f722 stack, and plan to use crossfire. However I’m not using gps or anything, not sure if this will be a problem for me.
First where i can find this S-BASS protocol , now don't buy F7, a month ago don't buy H7 next month you will tell people to buy F3 ... or is a new catch for G4 :)
With Betaflight cloud builds, the flash memory is no longer an issue. F722 having inverters we don't use anymore, doesn't really seem like a reason to "Be careful".
If you ever one to try ArduPilot, you'll need a different FC.
I have several F722 boards but I don't plan to purchase any in the future.
I'm sticking with my NAZE32 Rev 5 FCs and Baseflight. Style never goes out of fashion! 🙂
classic
I think it is time for you to upgrade to the NAZE32 Rev 6 by now
@@MatthewTaylor3 Slow down my friend... there's such a thing as moving *too* fast you know! 😛
Warm greetings from Georgia, Mr. Simpson! I have started learning FPV from your channel and now I am starting an FPV school, all thanks to your kind, wise and smart videos I have watched back in the days! Wish you the best!
If anything, the f405 processors are gonna get a feature cut, since f722's are just faster + the memory constraint is almost irelevant since cloud builds are a thing now(you can just cut out features that you don't use and save on space). Also releases of hardware are an indicator - iFlight blitz stacks(only f722 and f745), Flywoo GOKU(only f722), darwinfpv cement (only f435 and f722) etc.
I’m picky about the flight controllers I use. Here’s a reason to use an F722 that has nothing to do with the processor itself. There are other features that I consider important. I want a barometer because it gives a more accurate altitude than just GPS and I want to have an indicator of whether I am within the legally allowed range. The 9 to 10v BEC needs to be able to support the most power hungry digital VTX units currently on the market. There needs to be a built in pit mode switch so I can turn off the VTX when initially getting satellites. There needs to be enough UARTs for GPS and i2C pads in case I want to do barometer are preferred but not necessarily required. I have found a few F722s that meet all these requirements but have not found any F405s yet that do.
every f405 i have except an ancient emax one has all that
@@420247paulI just took a Quick Look and couldn’t find a single one for sale with the pit mode switch functionality.
Yea its hard to get that VTX power switch on and off. Its like flight controlers dont offer than anymore.
@@craigcupit1917i had to set up a switch for my axis flying argus f7 aio to turn on vtx 😉 you might be able to set up a switch on others for it. I think it was a user 1 switch. Was a while ago. I wonder if i set up a user switch on others if it would work 🤔
Hi, do You have any knowledge about DAKEFPVF722 ? Is this stack supporting SBUS or IBUS ?
I'm keen to get some advice on sbus and smartport. Currently I use frsky equipment and esc and use smartport telemetry to send it to my transmitter. I have a speedybee f405wing and a matek h743 wing. Is there a better way to to connect my receiver and telemetry?
fport
Yeah ELRS.
FPort as someone else also suggested is the best option. If you have SPort working already then the wiring is already set up correctly except you can disconnect the sbus wire since it will not be used. With SBus, you need to put RSSI on a channel but with FPort, the value is available without using up a channel.
Fport is my preferred connection with frsky. Its nice it includes RSSI.
Yo, how many channels do you have bro?
in total or RC/FPV related?
Do AT32 microcontrollers have software inverters? And more memory?
AT32F435 do not
We have cloud builds now, F722's memory is not a problem anymore ;)
on my speedybee f722 the erls module will not commmunicate on CRFS but work on sbus, and yep inverted. same for geprc and skystars and RM rp1 receivers.
Are you using O3?
If you're using 03 cut the the yellow wire of the VTX cable. It's interfering with your elrs / Xfire.
I had the same thing happen to me and when I checked the SpeedyBee f7 manual it indicates this as well. They suggest you cut / or eliminate the sbus wire (yellow) on the VTX cable for the 03. Hope this helps.
@@jomarayala6128 Yea, precisely, that is why I asked. This sounds suspiciously like user error
A neater way is to carefully remove JST SH connector for the SBUS wire
@@jomarayala6128 If you are running an O3 you only need power, ground, rx and tx
If you opt for a 405 controller, I think that it will not be compatible with the upcoming version 8 of iNav. I think that it will require STM32F7 based microcontrollers. In that case the STM32F405 would not be upgradable.
Someone please correct me if I have that wrong.
You are mistaken. INAV is stopping support for F411, not F405. F405 are indeed more powerful MCUs (in some areas) than F722
@@FPVBites Ahhh, I learned something today so "thank you" for setting me straight. I didn't realize that the F411 is a stripped down F405 with slower max clock speed and some limitations on the real-time-clock that the F405 isn't subjected to. I checked with Perplexity and it spelled out the differences. I've always assumed that a larger part number meant it had "more good stuff".
And yes, it appears that it's only the F411 that iNav plans to discontinue support for: ""INAV 7 is the last INAV official release available for F411 based flight controllers. The next milestone, INAV 8 will not be available for F411 boards."
What do you think of Artery AT32F435 mister? This new chip offers nice features above F405 and bellow F722, is this new chip worth to buy? Need more advice please
drivers are annoying, but as long as you stay with betaflight, you should definitely go for them as they are cheaper and more powerful than F405
You will be stuck using betaflight 4.5 or newer or a fork that supports it.
Or any other firmware that supports it.
But otherwise, the at32f435 is the same size as an f405 and a couple bucks cheaper and faster so there’s not really any other downsides to using it aside from compatibility.
I tought F7 flight controllers had more available UARTs. Is this the case?
F722 and F405 have the same number of UARTs
I found a forum topic with name "Betaflight Too Big?" and post writing this: F405 Region Size 922K Betaflight 4.3.0 with 43,6% usage. F722 (the bad versions with 512K not better versions with 1024K, STM32F722RGT6) Region size 480K Betaflight Betaflight 4.3.0 with 89,5% usage. So if you don't want to use a trimmed (cloud) new Betaflight OS, then FCs with 512K will probably no longer be sufficient very soon...
The RGT6 variant of the f722 doesn't exist, there is no mention of it anywhere aside from mislabeled listings. The F722 datasheet clearly says "up to 512Kbytes of flash". Only The F745/746/756 etc variants have 1Mb flash. And the F769 and F77* series which have 2Mb flash.
@@pvim Maybe you look at an old datasheet ? Github => Supported MCUs #197 => 4. F722. From what I could find, some FCs use the STM32F722RET6 (with 512 KiB of flash) while others use the STM32F722RGT6 (with 1024 KiB of flash)...
What about other F7 chips, Pawel? If I'm not mistaken, there's the F745 and F765... Something like that.
Anyway, stay safe there with your family! 🖖😊
Stay away from them due to price, but if you need any of their features like additional UARTs or more motor pins than F405s allow, go for them. That's what he said previously
@@bspringer Thank you! 😊
Yes the other F7 chips have twice as much memory as the F722.
Been flying and bashing around to skystar F722 hd pro v4's for months and theyre awesome. Dont get why to consider
Aw shucks, I’m building a new micro with an iFlight Blitz f722 stack, and plan to use crossfire. However I’m not using gps or anything, not sure if this will be a problem for me.
I miss frsky f port. Three wires vs 4 and not worrying about rx tx so much easier. I use f4s now that i dont use frsky elrs works great with f4
Cool, I use sbus and Smart Port still
they stick to F722 as it's the best for you
For 3D flying spend more for an f7.
I will avoid S-bass, to be safe :-)
First where i can find this S-BASS protocol , now don't buy F7, a month ago don't buy H7 next month you will tell people to buy F3 ... or is a new catch for G4 :)
Hey Pawel. Do you own this channel? If so, I'll subscribe. Just wondering why count is low. I want to make sure it's legit.
It's me, yes. This is a new one where I just post clips from live streams. So it's only starting, but it's frowing I suppose :)
@@FPVBites Cool! Subscribed!
You got nice House and garden!🍻
Not mine :) But I'm free fly there
„S-BASS“ receiver - i love AI text recognition
H7 on Kiss Ultra is the way to go, if your flying fpv quads that is.
raz, raz, raz, no one uses s-bass :D
Next step H722 FC's
You talk utter nonsense
Considering INAV he might be correct. If we look at Betaflight then its true that flash size issues have been mitigated with cloud build for now.
And what are your arguments my boy?
Overdramatic title.. makes it sound like its gonna drop out of the sky