Thank you, i am new on the fpv world and i bought a toothpick with a SPI based ELRS reciever but i was having so much trouble with updating the ELRS version and setting up the binding phrase, this tutorial/explanation helped me alot in both ways 😀
"SPI receivers DO NOT support D(D250, D500), F(F500, F1000) and Full Res(100Hz Full Res, 333Hz Full Res) Modes (Packet Rates) and thus will not bind or sync with a TX module in any of these modes." This is what let me finally bind.
Here is the model match gotcha with ExpressLRS. The module saves just about all the settings for each model match number. This includes whether model match is on or off and it does this even if the model match feature is not enabled. If you set up your first quad on model match number 1 and turn it on in the module and receiver it works. Then you go to add a second quad that has different settings and it’s easy to forget that when you switch to number 2, you need to redo all the module settings including turning on model match for that number. This does allow for not really using model match but creating multiple configurations with different settings. You could have a long range and short range model for the same quad, for example.
I just got the jumper t pro and a mobula 7 about 10 days ago to get into Elrs and was having a hell of a time trying figure out the whole process with flashing and binding phrase ans so on. I never did flash anything on the jumper or the mobula , but managed to find the lua in the jumper that had the word bind, and used the bind function in the receiver tab of betaflight and got it all working and got the radio and quad to bind. But, wow was I confused watching your other video and about 20 other videos on the subject, my brain had turned to mush and was about to give up on Elrs. Now I understand a little more after watching this video. Thanks Joshua. ;-) (The mobula 7 has a spi based receiver with no wifi)...
I honestly think this is the better way, even if the ELRS devs don't agree. Most pilots will setup their quad, find a sweet spot, and not touch the software again unless they have to. ELRS development may move fast, but most users probably don't mind much, especially since the ELRS firmware is forwards/backwards compatible within the major version number. Maybe the Maintenance release branch can be used to push ELRS updates faster, or create a new release branch specifically for SPI ELRS.
Thanks for this. I just got one of these recently, and happy model has zero information about these spi receivers. I contacted them and got ghosted... I ended up finding this info on the eLRS sites spi page, but it took hunting and frustration. This video will help a bunch of folks not go through what I did.
Very excited for the Mobeetle6 review! I'm loving mine, I landed it 2 times already in my kittens water trays and it's still working. I have never had an RC this durable.
SPI RX is good for FC whoop for simplicity and liteweight. I think whoop pilots only need the basic important functions of RX-TX which are link quality, stability and low latency and I think improvements are not always nor should be new features. I just hope AIO FC with SPI RX will keep exists and work for future version of ELRS release ... don't mind if it stuck or limited to current available features.
They could add binding phrase to the BF UI (I guess that's what's going to happen eventually), but the CLI just sends the commands directly to the FC and I guess they didn't want to bloat the ROM by adding the hashing function to command handler on the FC side.
As long as the new versions of ELRS TX firmware are backwards compatible with the BF SPI RX versions there's no problem with the different projects beeing out of sync in release schedule. If it works it works, do not update. 🙂
Hello, I have not had any problem (mobula6 elrs) yesterday I updated the tx to 2.5, copied the luas to the station and from betaflight I put 4.3 stable, in the receiver tab you hit bind and in the luas too, good without problems, 0 failures 🤷
For my SPI ELRS FC I simply uploaded latest BF firmware and then clicked the bind button in the receiver tab which did the trick somehow without UID, etc.
Use the Bind button on the Receiver Tab... Super easy and takes 2 seconds. ELRS V3 includes the ability to integrate the analog vtx. So we should see whoops with integrated serial Rx in the near future.
Just curious, if this was that much of a limitation, why design AIO FCs like the Pancake then? Seems that it could've been uart-based with all the extra space on an FC/VTX/RX only compared to a literal FC/ESC/VTX/RX AIO on whoops.
@@nikotttin I have binding fraze and elrs 2.0 and bind mobula7 1s ELRS using bind button in betaflight and bind button on luascript on tx( I have betafpv ELRS micro module+ flysky i6x with opentx) It binded in 10 seconds
I thought a reason for the 1.x and 2.x naming scheme was because all version 2.x hardware should at least have the basic functionality to work with all 2.x hardware. So you should be able to update your tx to the newest 2.x version even if the spi receiver is stuck on 2.1
*FACEPALM* I've had this HX115LR for MONTHS trying to get it to work and only just now found the "V 2.1" stamp on the bottom, which makes it a DIFFERENT version than the one in your tutorial, which worked for the second HX I bought (a v1) when I couldn't get the first to work. Only watching this video after watching the HX setup guide do I finally understand wtf I was doing wrong. THANK YOU even though you didn't even know you were getting this figured out for me after so many months of fruitless efforts to get these working.
I feel you pain, I had the same issue. Another one was that I couldn't change VTX channel so I just change all my other drone fro F4. Also, after a while my controller stopped giving power to ESC so it works in cli, but doesn't fly because voltage is always 0. I don't recommend for anyone to buy HX115LR.
This is really only a problem for me, when there's a big update, which requires you to update the ELRS version on your transmitter as well. Because then you need to delay this update on ALL of your quads until it's avaible for your FC. Otherwise I don't always need the latest and greatest on such a tiny micro-whoop.
@@jermadjesty Yes. But at one point there might be a version 3. (Version 2 and 1 are not compatible.) That's what I wanted to say: To me, it's not that much of a problem with the slow updates on SPI-based receivers as long as there's no major-update.
Oh no I just got a SPI ELRS Mobula6 as my first FPV which gets delivered in a week and now I'm worried, but it doesn't sound too bad for something like that I guess. Its just something small and durable to learn off of inside a small house before getting something else for outside
is spi similar to like spectrum sSRXL2 micro telemetry receiver, after all these different rfs and protocols, spektrum,frysky,crsf,tracer. i finally had to buy a radiomaster ranger module for a elrs 3.0 receiver . the micro and nonos were on back order so i bought the cnc one for 2watts over 1 watt hopefully, i wanted to avoid the whole xt30 pcb external power issue
One thing I've heard is running the PID loop on anything other than 2khz will spike cpu utilization due to the cpu timing running the eLRS firmware code in the PID loop. CPU is around 35% on a 2khz loop on my mobula 6.
i mean, its really good for light hardware. it sounds like they just ditched the whole elrs processor and are just running the radio chip and letting that giant arm chip you already have on the flight controller run the code. probably a step in the right direction, but with growing pains. Would be awesome if you could use that new presets picker to select elrs, but i know that doesnt actually recompile the code. Honestly, i wouldnt care about being several elrs revisions behind. I just want to get a good radio link and then never mess with it again.
I have it on a whoop board. Doesn't go far. I haven't had an issue yet. Also fly out a window to outside. I wouldn't put on bigger quad. I just upgraded to 4.4 to get elrs3 thpugh my whoop is broke. Motor wire pulled out the motor
Finally!! Elrs is getting easier. Few more months and it might actually be dumb-user friendly. I don't care about updating every month, I just wanted it to work, n it didnt. The spi way would have been alot simpler for me to get into.
6 months ago I flew my first ELRS quad, the Crux35 and it was SPI Receiver based. I was blown away at the range (1+ mile) and penetration that could be achieved an SPI ELRS receiver, and I still fly that quad now as it's one of my favorites. I thought for sure that this would be the future of whoops and micros. But as the months have gone by, I have watched the constant firmware updates by the BF team to address ELRS issues. As much of a fan as I have been of SPI ELRS for getting us away from god-awful FrSky and FlySky SPI receivers, I was wondering how the issues with the updates were going to play out. Today one of the ELRS developers Bryan Mayland stated that "SPI hardware should not be considered" in his opinion. And that "ExpressLRS 2.x works fine, but when 3.0 RC starts in a couple weeks, SPI RX will not work at all due to changes in the over-the-air formatting... SPI hardware is already obsolete in the eyes of the development team as that information should be known before making your next whoop." That was sad for me to hear… but it is understandable why. I wish there was a way for there to be some middle ground, but a dedicated UART looks like the only real solution. I don't think whoop or micro flyers necessarily cared about access to every new shiny feature ELRS brought to the table, we just wanted a stable, fast link that didn't suck. But as a programmer I see the challenge of trying to add new features while worrying about what's going on in SPI receiver code baked into BF that can't be updated easily - it must have been a nightmare. Integrated serial RX then, is the only way forward. Also, you can just hit the bind button on the rx tab which makes things a whole lot easier.
There is a solution and it's coming, there will be boards with a single MCU handling both ELRS RX and VTX and the total number of parts will be the same as SPI with bleeding edge compatibility of UART.
The bind button on the spi receivers is sooooo nice. But tbf, if you've got elrs on a uart and it's implented correctly and can be updated and configured with the elrs configurator then you can just do the binding phrase and that's not THAT much more difficult.
@@JohnCuppi I mean it's really valid. I have the 1s jhemcu board with elrs on a uart and binding it the first time was a pain because the target it's supposed to flash to doesn't work and it comes as elrs 1.x so there's no option to add a binding passphrase or anything and unless you know the unique method jhemcu has for binding, you'll never get it bound. Took me like an hour or more to get it to work and even then, I couldn't find any documentation on how to do it. It was just by talking to a friend that I figured it out. I was really missing the spi rx that day.
Hello Josué, as always, a pleasure to see your videos, but I have a question at the end of the video, you say how to link from cli I have done it as you mention but I cannot link. Do I have to touch any other parameter that I have missed?... I use radiomaster zorro with an external module and I have linked other elrs but this one resists me.
I have a Mobula 7 ELRS and had so many failsafes at short range and not binding on power up. I tried every RC version of BF4.3, reconfigured the options many times, and went through all the troubleshooting documentation with no luck. It worked best right after flashing firmware, but usually failsafed quickly after then just wouldn't bind. I ended up soldering on an EP2 instead and it's worked flawlessly ever since. Thanks for the video Joshua, it's nice to know I didn't miss anything in the setup! Looking forward to the Mobeetle6 review.
@@XscapePrime That's what I would guess too since I haven't seen anyone else with the same issue. I did reach out to HappyModel support but didn't hear anything back.
SPI is literally Serial Peripheral Interface. UART is universal asynchronous receiver-transmitter. The continuous use of the word 'Serial' when they are both serial interfaces with different protocols is just confusing. It's like calling every radio control link Ghost when the physical hardware you're using is Crossfire.
Amen. Not to mention SPI (which marks a peripheral-controller distinction) is literally made for a processor to talk to nearby peripherals without the need for them to have their own beefy processor serving as a second space-wasting, redundant controller.
Joshua I have a FrSky radio and use it for fixed wing, helis & quads. Horus X10s Express. I'd like to try ELRS in some quads. Is there an external module I can use for this radio? Cheers 🏴
I have a question that has nothing to do with this vid, but I'm new to drones and figured you'd have an answer, but also you would probably check these comments sooner than later lol. I have a Eachine Wizard X220S FPV Racer RC Drone Omnibus F4 5.8G 40CH 30A Dshot600 800TVL Flysky FS-i6X RTF, and a BetaFPV FPV Whoop Racing RTF Advanced Kit 2. I think I prefer the radio that came with the Whoop over the bigger Flysky. I watched your vid on the Radiomaster Zorro. Would that be a good choice for me moving forward with more drone purchases in the near future and would it bind to the 2 I already have? I don't want to have a different radio for every drone.
This what I do, read changelog, worth it=update after week or more to be sure no bugs, changelog not worth = no update, I had many troubles in the past for updating my pc/phone every time there new one that taught me " if its not broken, don't fix it " I know you addressing issue here, but may scares some Pilots from going to spi-elrs specially newbe.
You are the best! I have a Happymodel mobula 7 1s Whoop and until your video I didn't know about SPI. Now my Whoop is flying. Question: how do I found my binding phrase from my radio, if I forget it? Thanks!
hey just watched the video and used the bind phrase to connect to my beta85pro2, in betaflight in the radio tab if i'm moving my stick to full throttle it's jumping from 0 to 2000 where my stick is and also my radio is not showing i'm connected to the quad no telemetry recovered or disconnected notifications i'm so confused.
Oh good. I chose the FRsky SPI receiver on my Crux35 instead of the Elrs because the frsky version has 20a ESCs and the elrs version comes with 12a ESCs. So if they both suck, that's great because I got better ESCs and didn't lose anything on the receiver side of things.
@@jermadjesty The other reason I chose the frsky version is because I have radios that will do D8 frsky protocol but I don't have any elrs 2.4 stuff yet.
Bigger issue I can see is having your one whoop holding you back from updating your tx to the latest elrs firmware and holding all of your other elrs builds hostage to that one whoops old firmware
Hi i have the UART but the yellow led dosn't flash, and i want to change my binding phrase i can't bind to my radio can you pls help me. i played with the setting i don't know what i have done. i have the meteor 75 pro elrs. with Radiomaster pocket
I have a question, if I've bound an SPI ELRS receiver in betaflight by using the bind command, then doing the same in the ELRS LUA does that mean that the receiver fetched my binding phrase from my module or is it somehow bound without a binding phrase?
I got my first elrs whoop recently, a mobula7 and I've had some issues. Before watching this video, I assumed flashing bf4.4 was the easiest way to bind but it would appear that my issues start as soon as I flash 4.4...one or more of the esc seem to brick after that has been done. When checked in bl heli suite or bl heli, it says erased or unknown fw. Does anyone know how to rectify that?
Thanks for this great informations Please can you tell me what is better?? I want to buy mobula7 1s elrs and are two obtions 1 --elrs integrated spi (flight controller is 1s only and have mpu 6000) or 2 without receiver and add an ep2 on uart(flight controller is 1 and 2s but have another giro chip not mpu600)
It depends if you care most about weight, or more about the future upgradeability of the FC. If you care about weight, get the SPI receiver. If you care about upgradeability, get the EP2 receiver.
I have a crux 35 ELRS and i have on disarm a Loop saying "Telemetry lost/ telemetry recover". On arm loop does not exit anymore but sometimes i have failsafe very very close to me (less than 50m !!) I don't know what to do. Crux recommend ELRS 2.0 i'm on 2.0. They recommend 250ghz, i'm on 250ghz. I can't fly safety. Someone told me that there's issue with BF and spi elrs with BMI270 (because of Dshot 300 and a low pid loop.) I really don't know what to do. Any solution someone ?
SPI is considerably faster especially when you run express LRS at 500Hz. Do you know what data rates the UARTs run? 115200 is pretty standard, though faster rates are possible in some cases. If you are running at 500hz, do the math on how many bytes fit into 115200, and it’s likely 500Hz just won’t fit. This may be worth the trade off.
github.com/betaflight/betaflight/blob/master/src/main/rx/crsf.c runs on 420kbaud, 1.5ms per frame max. sounds like a lot until you realize dji link is 28+ ms
Not to burst your bubble, dude. But, not all UARTs run at 115.2 kilobytes per second. That's more of a loosely kept guideline, than an absolute rule. CRSF is a UART protocol that runs at 420 kilobytes per second or higher. If you went through the source code of BetaFlight, you would know this. Also, when it comes to SPI vs UART vs I2C etc. It's not a case of "which one is better than the other" or "which one is crap". It's moreover to do with which one is more better suited to the application at hand versus the availability of compatible hardware that can drive it & what price point the device is being made for. For example, the reason why the vast majority of servos (that aren't made by Futaba or FrSky) & motor controllers (ESCs) still use PWM & not a UART-based protocol (such as D Shot) or (better yet) CAN, is because of backward compatibility.
@@NiCadHeliPilot True, but in the video you can see the uart speeds are all set to 115200 in betaflight configurator. ua-cam.com/video/G1dK7nk5Ds4/v-deo.html And for this application 115200 is not enough to get data to the FC at 500Hz.
If the ELRS firmware needs to be baked into BetaFlight, then what's the point of the SPI/ELRS drop down in the configurator? Conversely, what they should do is decouple these by standardizing the flight controller's receiver API and letting the ELRS firmware conform to that standard. If they did that, then BetaFlight could include a stable Rx blob, but the moment it is outdated, the Rx can be updated by updating BetaFlight (with a newer stock Rx blob), some as-yet undefined Rx firmware pass-through over SPI, or over WiFi. As long as all of the Rx firmware use the same protocol to talk to the FC over SPI, the Rx can be kept updated independently... just like the UART version.
Betaflight isnt the standard setter, it is one FC firmware (of many). Receivers can be used without FCs so wouldn't make too much sense, but I see your idea
Yeah... I don't know what would be a solution for this. Perhaps ELRS should just stop allowing SPI receivers from 3.0 on... Or maybe from 4.0 on, I don't really know... Either way, great info, Joshua! Thanks! 😃 Stay safe there with your family! 🖖😊
You... can't flash a new version on the SPI. It's built into Betaflight. You flash new ELRS firmware by flashing a new version of Betaflight that has the new version of ELRS built in. To update the SPI-based ELRS receiver, you have to integrate the new ELRS code into the betaflight codebase, bug-test it, and then compile it. This is the whole point of the chapter starting at 6:35 in the video. That it's basically impossible for a typical person to do that. And so SPI-based receivers can't easily be upgraded like UART-based ones can.
i think that (at least in my experience) telemetry must be turned off on SPI elrs receivers, otherwise it wont bind i dont know if this works for serial receivers too...
The only issue I ALWAYS have with ELRS is the wifi always stops working after every update. It broadcasts but once you try and connect it drops off. Unless it's betafpv issue, it's happened every time on all my receivers... So I can't do wifi updates
That's strange. I update every release as they come out using wifi on all my quads and it works flawlessly every time. I have a Happymodel module and ep rx's.
ok so I got through all of this and I have my spi receiver bound and i can see the inputs in betaflight but there's a huge delay and it's really choppy and when I try to arm it i get an error code saying "bad rx" or "rx lost". Does anyone have any ideas how to fix this? I'm using the BetaFPV F4 1S 12A AIO flight controller and the BetaFPV ELRS Nano module in a lite radio 3
Can you bind an upgraded radio controller with 3.0 with a spi receiver which is only in betaflight based elrs 2.0? I was zero successful even after putting same passphrase by wifi on radio and cli to receiver. Really frustrated by hundreds of tries to bind the iflight commando and the mobula 7
3.x code cannot bind to 2.x code. Here is the workaround: ua-cam.com/video/bPbPCyjhE1Q/v-deo.html&ab_channel=JoshuaBardwell See the pinned comment below that video for an updated recommendation after watching that video. For what it's worth, the compatibility warning is right at the top of the release notes for ELRS 3.0. It's always a good idea to check the release notes before flashing any new version. github.com/ExpressLRS/ExpressLRS/releases/tag/3.0.0
Seems to me this is a real downside to SPI ELRS. The basic issue is that both Betaflight and ELRS are projects under active development, and they aren't synchronised - why should they be? Way too easy to get incompatibilities with the ELRS Tx which is probably going to be the common factor across multiple craft. I assume the same problem could occur with SPI FrSky or FlySky receivers, but the difference is the protocols are pretty stable. The problem really is that ELRS is moving so fast at the moment. Maybe in time it won't be. I use standalone ELRS but am about to build a whoop style quad. The FC for that will either have to be one with no Rx (most likely) so I can fit an ELRS Rx, or one with FrSky built in. I will not be looking at built in ELRS unless it is via UART link.
Hey Josh, have I missed something here? Ok so if the rx firmware is locked, what happens if you have 2 , 3 or more whoops of different ages, and you want to fly them all on the same day do we have to juggle flashing the tx each time? If so that would be a real pain, I am just starting to dabble in this, so just trying to learn something to day, hahaha, or, are they all covered by V2 tx
This is the problem with SPI based receivers. Once you flash your module to 3.x, you can't use the SPI-based whoops any more. So you either have two modules with two firmwares, or you flash the module back and forth.
Can a SPI based ELRS receiver be disabled on a flight controller? If yes, how? Or is it disabled if I connect an external receiver and enable the uart?
Sorry, when I see the target name, I only see "crazy beef" and some numbers. Thanks for the tutorial, though. I'm going to need it. Why does this have to be so complicated?!
So when you say "poor range", I guess you mean that it loses signal even inside the house? Because based on flight time, and size......I personally probably wouldn't even be flying this quad much outdoors, as I have 3.5" and mostly 5" quads for that. But perhaps many do fly these like their 5", outdoors.
@@angelsinraver Well, I guess I fly my TinyHawk Freestyle 2 outside also, I mean......it can be flown in doors, but it is quite punchy on the throttle:)
I get random failsafes even indoors close to 5ft when flying with 150hz packet rate and dynamic power on with my mobula 8. It regains connection once I disarm and rearm...have you faced an issue like this? This is very disappointing after moving to ELRS.
There's something wrong with your quad. I know this doesn't really solve your issue, but this is not an ELRS problem; it's not an SPI problem; it's not even a Mobula6 problem. There is something broken about your specific quad.
@@JoshuaBardwellThank you.. It is a brand new quad....it happens one time out of 8-9 packs. Do you think the CPU is getting overloaded due to dynamic power ON? Will reflashing betaflight fix it?
@@JoshuaBardwellI can't figure out what the issue is but I turned off Dynamic power as per Nick burns (power level locked at 50mw) and haven't failsafed for 10+ packs.
So ELRS 3.0 is out and not compatible with 2.x receivers; can my Zorro handle both 2.x and 3.x ELRS or do I need to stay on 2.x to be compatible with my Mobula 7? Or if it can't, does this mean I need to switch the Zorro back and forth between the two versions (or get 2 controllers)?
You cannot run two different versions of ELRS at the same time on the same module. So your Zorro has to be either 2.x or 3.x. There is a nightly version of Betaflight that you can put on the Mobula7 that makes it compatible with ELRS v3. Or you can get an external module to put in your Zorro, and run 2.x on the internal and 3.x on the external. Or you can just switch back and forth.
Yes it is. It's baked into the Betaflight code. There is a nightly build of Betaflight 4.4 that has barebones ELRS 3.0 support. I don't have the link right here unfortunately.
I’ve thought about everything you mentioned in this video, but for SPI on 65mm, 75mm quads. I can live with this limitation. Everything 3” and bigger I can afford the weight of an external receiver.
Feels more like an implementation issue then an SPI vs UART issue. Not having looked at the actual boards with the ExpressLRS SPI implementation, it sounds more like they share CPU since the code has to be built into Betaflight, to save cost, instead of just using SPI for communication between the different functions.
@@lightbulbjim understandable then that they want to remove that behaviour from the board manufacturers, since it then creates that dependency. Would have been better to run SPI but separate chips/functions.
As someone looking to get into the hobby with a limited budget, I was looking at getting a BNF quad and I guess it has SPI ELRS. Would it be a bad idea for me to get it right now? I wouldn't plan on flying anything else in the near-future, so would I really have to worry about firmware updates or anything?
@@JoshuaBardwell thank you so much for the reply and the super informative video! Assuming I get everything to work, I probably shouldn't update anything until the next quad I upgrade to, right?
Hi, I just got this quad and for some reason it says No Gyro/Acc on betaflight. Do you know why this is happening. This is with no flight time just setup?
Most likely you flashed the wrong Betaflight target to it, so now the FC can't find the gyro. Go to CLI and type "version" and you will see the current target on the FC. It should be: CRAZYBEEF4SX1280
Thank you, i am new on the fpv world and i bought a toothpick with a SPI based ELRS reciever but i was having so much trouble with updating the ELRS version and setting up the binding phrase, this tutorial/explanation helped me alot in both ways 😀
I've been stumped for a week, thanks for the solution.
"SPI receivers DO NOT support D(D250, D500), F(F500, F1000) and Full Res(100Hz Full Res, 333Hz Full Res) Modes (Packet Rates) and thus will not bind or sync with a TX module in any of these modes." This is what let me finally bind.
OMFG.
This cost me 8 hours.
THANK YOU For your comment. I thought I'd go crazy.
You the man!
Here is the model match gotcha with ExpressLRS. The module saves just about all the settings for each model match number. This includes whether model match is on or off and it does this even if the model match feature is not enabled. If you set up your first quad on model match number 1 and turn it on in the module and receiver it works. Then you go to add a second quad that has different settings and it’s easy to forget that when you switch to number 2, you need to redo all the module settings including turning on model match for that number. This does allow for not really using model match but creating multiple configurations with different settings. You could have a long range and short range model for the same quad, for example.
Thanks!
Man, i have been watching your videos and I must say, they are goood. Nice and clear and complete. Subscribed!
I just got the jumper t pro and a mobula 7 about 10 days ago to get into Elrs and was having a hell of a time trying figure out the whole process with flashing and binding phrase ans so on. I never did flash anything on the jumper or the mobula , but managed to find the lua in the jumper that had the word bind, and used the bind function in the receiver tab of betaflight and got it all working and got the radio and quad to bind. But, wow was I confused watching your other video and about 20 other videos on the subject, my brain had turned to mush and was about to give up on Elrs. Now I understand a little more after watching this video. Thanks Joshua. ;-) (The mobula 7 has a spi based receiver with no wifi)...
I honestly think this is the better way, even if the ELRS devs don't agree. Most pilots will setup their quad, find a sweet spot, and not touch the software again unless they have to. ELRS development may move fast, but most users probably don't mind much, especially since the ELRS firmware is forwards/backwards compatible within the major version number.
Maybe the Maintenance release branch can be used to push ELRS updates faster, or create a new release branch specifically for SPI ELRS.
Thanks for this. I just got one of these recently, and happy model has zero information about these spi receivers. I contacted them and got ghosted... I ended up finding this info on the eLRS sites spi page, but it took hunting and frustration. This video will help a bunch of folks not go through what I did.
Very excited for the Mobeetle6 review! I'm loving mine, I landed it 2 times already in my kittens water trays and it's still working. I have never had an RC this durable.
The ExpressLRS firm used by BF-4.3 is 2.0. Can work with all TX firm 2.X , but no with 1.X.
SPI RX is good for FC whoop for simplicity and liteweight. I think whoop pilots only need the basic important functions of RX-TX which are link quality, stability and low latency and I think improvements are not always nor should be new features.
I just hope AIO FC with SPI RX will keep exists and work for future version of ELRS release ... don't mind if it stuck or limited to current available features.
They could add binding phrase to the BF UI (I guess that's what's going to happen eventually), but the CLI just sends the commands directly to the FC and I guess they didn't want to bloat the ROM by adding the hashing function to command handler on the FC side.
As long as the new versions of ELRS TX firmware are backwards compatible with the BF SPI RX versions there's no problem with the different projects beeing out of sync in release schedule.
If it works it works, do not update. 🙂
Love the Explanation! Any ideas where one could find that SWEET Shirt though? 😃
Hello, I have not had any problem (mobula6 elrs) yesterday I updated the tx to 2.5, copied the luas to the station and from betaflight I put 4.3 stable, in the receiver tab you hit bind and in the luas too, good without problems, 0 failures 🤷
For my SPI ELRS FC I simply uploaded latest BF firmware and then clicked the bind button in the receiver tab which did the trick somehow without UID, etc.
Use the Bind button on the Receiver Tab... Super easy and takes 2 seconds.
ELRS V3 includes the ability to integrate the analog vtx. So we should see whoops with integrated serial Rx in the near future.
Can't wait for V3, especially the support for extra high res channels!
Just curious, if this was that much of a limitation, why design AIO FCs like the Pancake then? Seems that it could've been uart-based with all the extra space on an FC/VTX/RX only compared to a literal FC/ESC/VTX/RX AIO on whoops.
Bind button won't work if you have a binding phrase. If that's set-up, then yes it does work (provided you use elrs 2.x as backed into 4.3.x)
@@nikotttin I have binding fraze and elrs 2.0 and bind mobula7 1s ELRS using bind button in betaflight and bind button on luascript on tx( I have betafpv ELRS micro module+ flysky i6x with opentx) It binded in 10 seconds
I thought a reason for the 1.x and 2.x naming scheme was because all version 2.x hardware should at least have the basic functionality to work with all 2.x hardware. So you should be able to update your tx to the newest 2.x version even if the spi receiver is stuck on 2.1
That's true, but there is ELRS 3.0 soon.
Also the devs say dont buy SPI if you can avoid it.
Would have saved me te most part of the weekend if this was mentioned in the complete ELRS tutorial video.😅
Glad I finally found this. Great video
*FACEPALM*
I've had this HX115LR for MONTHS trying to get it to work and only just now found the "V 2.1" stamp on the bottom, which makes it a DIFFERENT version than the one in your tutorial, which worked for the second HX I bought (a v1) when I couldn't get the first to work. Only watching this video after watching the HX setup guide do I finally understand wtf I was doing wrong. THANK YOU even though you didn't even know you were getting this figured out for me after so many months of fruitless efforts to get these working.
I feel you pain, I had the same issue. Another one was that I couldn't change VTX channel so I just change all my other drone fro F4. Also, after a while my controller stopped giving power to ESC so it works in cli, but doesn't fly because voltage is always 0. I don't recommend for anyone to buy HX115LR.
This is really only a problem for me, when there's a big update, which requires you to update the ELRS version on your transmitter as well.
Because then you need to delay this update on ALL of your quads until it's avaible for your FC.
Otherwise I don't always need the latest and greatest on such a tiny micro-whoop.
I thought all 2.X releases we're compatible, no?
@@jermadjesty Yes. But at one point there might be a version 3.
(Version 2 and 1 are not compatible.)
That's what I wanted to say:
To me, it's not that much of a problem with the slow updates on SPI-based receivers as long as there's no major-update.
@@uhu4677 Like now for example!
so my Radiomaster ZORRO has ELRS 3.0 Should I flash the new ELRS for the Mobula7 1s? since it 'SPI FRSKY'?
Oh no I just got a SPI ELRS Mobula6 as my first FPV which gets delivered in a week and now I'm worried, but it doesn't sound too bad for something like that I guess. Its just something small and durable to learn off of inside a small house before getting something else for outside
It is another option.
In the future if we can't update spi ELRS receivers, we can install an external ep2 on spare UARTS.
There a a Whoop FC my JHEMCU that has ELRS built into the board but it used a UART and has WIFI!
actually works very good now with 4.4.0 betaflight, but i was very confuse as i was trying to wifi flash it. thanks for the video
I have two HM AIO CrazyF4 ELRS 915 whoopboards that are using a uart an use csrf .....just flashed both with 3.0 👍
is spi similar to like spectrum sSRXL2 micro telemetry receiver, after all these different rfs and protocols, spektrum,frysky,crsf,tracer. i finally had to buy a radiomaster ranger module for a elrs 3.0 receiver . the micro and nonos were on back order so i bought the cnc one for 2watts over 1 watt hopefully, i wanted to avoid the whole xt30 pcb external power issue
One thing I've heard is running the PID loop on anything other than 2khz will spike cpu utilization due to the cpu timing running the eLRS firmware code in the PID loop. CPU is around 35% on a 2khz loop on my mobula 6.
No, this is fixed in 4.3 now. Betaflight 4.3 also reports CPU differently now. Up to 75% CPU is acceptable.
There was a post on the elrs fb saying that the spi interface is deprecated.
If ELRS 3.0 comes out with unified targets it would probably be much simpler to integrate the ELRS code with betaflight.
i mean, its really good for light hardware. it sounds like they just ditched the whole elrs processor and are just running the radio chip and letting that giant arm chip you already have on the flight controller run the code. probably a step in the right direction, but with growing pains. Would be awesome if you could use that new presets picker to select elrs, but i know that doesnt actually recompile the code. Honestly, i wouldnt care about being several elrs revisions behind. I just want to get a good radio link and then never mess with it again.
I have it on a whoop board. Doesn't go far. I haven't had an issue yet. Also fly out a window to outside. I wouldn't put on bigger quad.
I just upgraded to 4.4 to get elrs3 thpugh my whoop is broke. Motor wire pulled out the motor
Just got the diamond elrs built in fc. Going to build my own moblite7.
Have you ever wondered what's up with the binding phrase? It's a mac address for the ESPNOW unicast communication protocol.
Finally!! Elrs is getting easier. Few more months and it might actually be dumb-user friendly. I don't care about updating every month, I just wanted it to work, n it didnt. The spi way would have been alot simpler for me to get into.
6 months ago I flew my first ELRS quad, the Crux35 and it was SPI Receiver based. I was blown away at the range (1+ mile) and penetration that could be achieved an SPI ELRS receiver, and I still fly that quad now as it's one of my favorites.
I thought for sure that this would be the future of whoops and micros. But as the months have gone by, I have watched the constant firmware updates by the BF team to address ELRS issues. As much of a fan as I have been of SPI ELRS for getting us away from god-awful FrSky and FlySky SPI receivers, I was wondering how the issues with the updates were going to play out.
Today one of the ELRS developers Bryan Mayland stated that "SPI hardware should not be considered" in his opinion. And that "ExpressLRS 2.x works fine, but when 3.0 RC starts in a couple weeks, SPI RX will not work at all due to changes in the over-the-air formatting... SPI hardware is already obsolete in the eyes of the development team as that information should be known before making your next whoop." That was sad for me to hear… but it is understandable why.
I wish there was a way for there to be some middle ground, but a dedicated UART looks like the only real solution. I don't think whoop or micro flyers necessarily cared about access to every new shiny feature ELRS brought to the table, we just wanted a stable, fast link that didn't suck. But as a programmer I see the challenge of trying to add new features while worrying about what's going on in SPI receiver code baked into BF that can't be updated easily - it must have been a nightmare. Integrated serial RX then, is the only way forward.
Also, you can just hit the bind button on the rx tab which makes things a whole lot easier.
There is a solution and it's coming, there will be boards with a single MCU handling both ELRS RX and VTX and the total number of parts will be the same as SPI with bleeding edge compatibility of UART.
The bind button on the spi receivers is sooooo nice. But tbf, if you've got elrs on a uart and it's implented correctly and can be updated and configured with the elrs configurator then you can just do the binding phrase and that's not THAT much more difficult.
@@zachmachina agreed! I just wanted to point that out because it was a nice little perk of ELRS SPI, but I would survive just fine without it.
@@JohnCuppi I mean it's really valid. I have the 1s jhemcu board with elrs on a uart and binding it the first time was a pain because the target it's supposed to flash to doesn't work and it comes as elrs 1.x so there's no option to add a binding passphrase or anything and unless you know the unique method jhemcu has for binding, you'll never get it bound. Took me like an hour or more to get it to work and even then, I couldn't find any documentation on how to do it. It was just by talking to a friend that I figured it out. I was really missing the spi rx that day.
If i power the kwad but not the TX, the EP2 stats to flash and won't connect, is this normal?
Hello Josué, as always, a pleasure to see your videos, but I have a question at the end of the video, you say how to link from cli I have done it as you mention but I cannot link. Do I have to touch any other parameter that I have missed?... I use radiomaster zorro with an external module and I have linked other elrs but this one resists me.
Bryan just posted on FB about how elrs spi may be over soon and moving more to an AIO with a separate processor for the elrs rx.
I have a Mobula 7 ELRS and had so many failsafes at short range and not binding on power up. I tried every RC version of BF4.3, reconfigured the options many times, and went through all the troubleshooting documentation with no luck. It worked best right after flashing firmware, but usually failsafed quickly after then just wouldn't bind. I ended up soldering on an EP2 instead and it's worked flawlessly ever since. Thanks for the video Joshua, it's nice to know I didn't miss anything in the setup! Looking forward to the Mobeetle6 review.
Maybe it was faulty unit, my Mobula6 elrs never failsafe, it was simple bind and fly.
@@XscapePrime That's what I would guess too since I haven't seen anyone else with the same issue. I did reach out to HappyModel support but didn't hear anything back.
SPI is literally Serial Peripheral Interface. UART is universal asynchronous receiver-transmitter. The continuous use of the word 'Serial' when they are both serial interfaces with different protocols is just confusing. It's like calling every radio control link Ghost when the physical hardware you're using is Crossfire.
This explains exactly how confusing and irritating some of this stuff is.
Well, they are both serial links, just different types for different purposes.
Amen. Not to mention SPI (which marks a peripheral-controller distinction) is literally made for a processor to talk to nearby peripherals without the need for them to have their own beefy processor serving as a second space-wasting, redundant controller.
Joshua
I have a FrSky radio and use it for fixed wing, helis & quads. Horus X10s Express. I'd like to try ELRS in some quads. Is there an external module I can use for this radio?
Cheers 🏴
I have a question that has nothing to do with this vid, but I'm new to drones and figured you'd have an answer, but also you would probably check these comments sooner than later lol. I have a Eachine Wizard X220S FPV Racer RC Drone Omnibus F4 5.8G 40CH 30A Dshot600 800TVL Flysky FS-i6X RTF, and a BetaFPV FPV Whoop Racing RTF Advanced Kit 2. I think I prefer the radio that came with the Whoop over the bigger Flysky. I watched your vid on the Radiomaster Zorro. Would that be a good choice for me moving forward with more drone purchases in the near future and would it bind to the 2 I already have? I don't want to have a different radio for every drone.
Nothing like having to downgrade the Elrs in my Zorro to 2.5.1 so I can fly my "new" Mobula 7.... Should have watched this video sooner!
Hi there, is there any flash targets that work for MATEKF411RX?
This what I do, read changelog, worth it=update after week or more to be sure no bugs, changelog not worth = no update, I had many troubles in the past for updating my pc/phone every time there new one that taught me " if its not broken, don't fix it " I know you addressing issue here, but may scares some Pilots from going to spi-elrs specially newbe.
You are the best! I have a Happymodel mobula 7 1s Whoop and until your video I didn't know about SPI. Now my Whoop is flying. Question: how do I found my binding phrase from my radio, if I forget it? Thanks!
What about the spi receiver embedded in the sp racing H7 ?
hey just watched the video and used the bind phrase to connect to my beta85pro2, in betaflight in the radio tab if i'm moving my stick to full throttle it's jumping from 0 to 2000 where my stick is
and also my radio is not showing i'm connected to the quad no telemetry recovered or disconnected notifications i'm so confused.
Is there a way to convert uid to word? (Oposite that you've shown)?
No. It's a one-way conversion.
Oh good. I chose the FRsky SPI receiver on my Crux35 instead of the Elrs because the frsky version has 20a ESCs and the elrs version comes with 12a ESCs. So if they both suck, that's great because I got better ESCs and didn't lose anything on the receiver side of things.
He was mostly joking
@@jermadjesty The other reason I chose the frsky version is because I have radios that will do D8 frsky protocol but I don't have any elrs 2.4 stuff yet.
Thanks for the video Josh!
Bigger issue I can see is having your one whoop holding you back from updating your tx to the latest elrs firmware and holding all of your other elrs builds hostage to that one whoops old firmware
I think all 2.X firmware's are compatible
Yeah I've got 2.4 on my TX and no issue binding with 2.0
My new Meteor65 (2022) will not let me write to the CLI. I guess this is what you are talking about.
Hi i have the UART but the yellow led dosn't flash, and i want to change my binding phrase i can't bind to my radio can you pls help me. i played with the setting i don't know what i have done. i have the meteor 75 pro elrs. with Radiomaster pocket
I have a question, if I've bound an SPI ELRS receiver in betaflight by using the bind command, then doing the same in the ELRS LUA does that mean that the receiver fetched my binding phrase from my module or is it somehow bound without a binding phrase?
It bind without frase
Can I get rssi dbm on spi reciver? I'm trying 😪
I got my first elrs whoop recently, a mobula7 and I've had some issues. Before watching this video, I assumed flashing bf4.4 was the easiest way to bind but it would appear that my issues start as soon as I flash 4.4...one or more of the esc seem to brick after that has been done. When checked in bl heli suite or bl heli, it says erased or unknown fw. Does anyone know how to rectify that?
Also can't update to the new 3.0 elrs I just got the baby ape freestyle that thing looks like it rips
Thanks for this great informations
Please can you tell me what is better??
I want to buy mobula7 1s elrs and are two obtions 1 --elrs integrated spi (flight controller is 1s only and have mpu 6000) or 2 without receiver and add an ep2 on uart(flight controller is 1 and 2s but have another giro chip not mpu600)
It depends if you care most about weight, or more about the future upgradeability of the FC. If you care about weight, get the SPI receiver. If you care about upgradeability, get the EP2 receiver.
@@JoshuaBardwell Thank you
Wish I had found this video a week ago. :) I was pulling my (already sparse) hair out trying to get my whoop working.
Great video JB! Thanks
I have a crux 35 ELRS and i have on disarm a Loop saying "Telemetry lost/ telemetry recover". On arm loop does not exit anymore but sometimes i have failsafe very very close to me (less than 50m !!) I don't know what to do. Crux recommend ELRS 2.0 i'm on 2.0. They recommend 250ghz, i'm on 250ghz. I can't fly safety. Someone told me that there's issue with BF and spi elrs with BMI270 (because of Dshot 300 and a low pid loop.) I really don't know what to do. Any solution someone ?
SPI is considerably faster especially when you run express LRS at 500Hz. Do you know what data rates the UARTs run? 115200 is pretty standard, though faster rates are possible in some cases. If you are running at 500hz, do the math on how many bytes fit into 115200, and it’s likely 500Hz just won’t fit. This may be worth the trade off.
github.com/betaflight/betaflight/blob/master/src/main/rx/crsf.c
runs on 420kbaud, 1.5ms per frame max. sounds like a lot until you realize dji link is 28+ ms
Not to burst your bubble, dude. But, not all UARTs run at 115.2 kilobytes per second. That's more of a loosely kept guideline, than an absolute rule.
CRSF is a UART protocol that runs at 420 kilobytes per second or higher. If you went through the source code of BetaFlight, you would know this.
Also, when it comes to SPI vs UART vs I2C etc. It's not a case of "which one is better than the other" or "which one is crap". It's moreover to do with which one is more better suited to the application at hand versus the availability of compatible hardware that can drive it & what price point the device is being made for.
For example, the reason why the vast majority of servos (that aren't made by Futaba or FrSky) & motor controllers (ESCs) still use PWM & not a UART-based protocol (such as D Shot) or (better yet) CAN, is because of backward compatibility.
@@NiCadHeliPilot True, but in the video you can see the uart speeds are all set to 115200 in betaflight configurator. ua-cam.com/video/G1dK7nk5Ds4/v-deo.html
And for this application 115200 is not enough to get data to the FC at 500Hz.
Got be honest with you...I could have used this when I got a Meteor65 pro Axis /Thor combo.... Oh well there's a first for everything, lol. Cheers
Thanks Joshua, here’s hoping 🤞🏼the binding gods are merciful 🤔
Can I bind these spi elrs receivers with my taranis r9m module or not ? Does anyone know about it ?
If the ELRS firmware needs to be baked into BetaFlight, then what's the point of the SPI/ELRS drop down in the configurator? Conversely, what they should do is decouple these by standardizing the flight controller's receiver API and letting the ELRS firmware conform to that standard. If they did that, then BetaFlight could include a stable Rx blob, but the moment it is outdated, the Rx can be updated by updating BetaFlight (with a newer stock Rx blob), some as-yet undefined Rx firmware pass-through over SPI, or over WiFi. As long as all of the Rx firmware use the same protocol to talk to the FC over SPI, the Rx can be kept updated independently... just like the UART version.
You can still use the drop down and select a uart based receiver ..
Betaflight isnt the standard setter, it is one FC firmware (of many). Receivers can be used without FCs so wouldn't make too much sense, but I see your idea
Yeah... I don't know what would be a solution for this. Perhaps ELRS should just stop allowing SPI receivers from 3.0 on... Or maybe from 4.0 on, I don't really know...
Either way, great info, Joshua! Thanks! 😃
Stay safe there with your family! 🖖😊
Would have been helpful to see how to flash a new version on the spi, instead of settings we can easily look up
You... can't flash a new version on the SPI. It's built into Betaflight. You flash new ELRS firmware by flashing a new version of Betaflight that has the new version of ELRS built in. To update the SPI-based ELRS receiver, you have to integrate the new ELRS code into the betaflight codebase, bug-test it, and then compile it.
This is the whole point of the chapter starting at 6:35 in the video. That it's basically impossible for a typical person to do that. And so SPI-based receivers can't easily be upgraded like UART-based ones can.
i think that (at least in my experience) telemetry must be turned off on SPI elrs receivers, otherwise it wont bind
i dont know if this works for serial receivers too...
The only issue I ALWAYS have with ELRS is the wifi always stops working after every update. It broadcasts but once you try and connect it drops off. Unless it's betafpv issue, it's happened every time on all my receivers... So I can't do wifi updates
That's strange. I update every release as they come out using wifi on all my quads and it works flawlessly every time. I have a Happymodel module and ep rx's.
All your receivers are BetaFPV and all of them have this issue. Meanwhile /me using Happymodel it works every time. Hmmm.
@@skree_fpv436 the TX has no issues, only the betafpv nano rxs wifi always seems to lock up after updating.. I don't get why
ok so I got through all of this and I have my spi receiver bound and i can see the inputs in betaflight but there's a huge delay and it's really choppy and when I try to arm it i get an error code saying "bad rx" or "rx lost". Does anyone have any ideas how to fix this? I'm using the BetaFPV F4 1S 12A AIO flight controller and the BetaFPV ELRS Nano module in a lite radio 3
Can you bind an upgraded radio controller with 3.0 with a spi receiver which is only in betaflight based elrs 2.0? I was zero successful even after putting same passphrase by wifi on radio and cli to receiver. Really frustrated by hundreds of tries to bind the iflight commando and the mobula 7
3.x code cannot bind to 2.x code. Here is the workaround: ua-cam.com/video/bPbPCyjhE1Q/v-deo.html&ab_channel=JoshuaBardwell
See the pinned comment below that video for an updated recommendation after watching that video.
For what it's worth, the compatibility warning is right at the top of the release notes for ELRS 3.0. It's always a good idea to check the release notes before flashing any new version.
github.com/ExpressLRS/ExpressLRS/releases/tag/3.0.0
Seems to me this is a real downside to SPI ELRS. The basic issue is that both Betaflight and ELRS are projects under active development, and they aren't synchronised - why should they be?
Way too easy to get incompatibilities with the ELRS Tx which is probably going to be the common factor across multiple craft.
I assume the same problem could occur with SPI FrSky or FlySky receivers, but the difference is the protocols are pretty stable. The problem really is that ELRS is moving so fast at the moment. Maybe in time it won't be.
I use standalone ELRS but am about to build a whoop style quad. The FC for that will either have to be one with no Rx (most likely) so I can fit an ELRS Rx, or one with FrSky built in. I will not be looking at built in ELRS unless it is via UART link.
Hey Josh, have I missed something here? Ok so if the rx firmware is locked, what happens if you have 2 , 3 or more whoops of different ages, and you want to fly them all on the same day do we have to juggle flashing the tx each time? If so that would be a real pain, I am just starting to dabble in this, so just trying to learn something to day, hahaha, or, are they all covered by V2 tx
This is the problem with SPI based receivers. Once you flash your module to 3.x, you can't use the SPI-based whoops any more. So you either have two modules with two firmwares, or you flash the module back and forth.
Bardwell is a damn hero
Can a SPI based ELRS receiver be disabled on a flight controller? If yes, how? Or is it disabled if I connect an external receiver and enable the uart?
Exactly. Connect external RX and change the Receiver Tab RX type from SPI to Serial.
well then....I am so ready for this.....very soon...
Sorry, when I see the target name, I only see "crazy beef" and some numbers. Thanks for the tutorial, though. I'm going to need it. Why does this have to be so complicated?!
Thanks Joshua 👊🏻
If I buy a drone with uart elrs would I be able to put a TBS crossfire on it instead?
Yes.
@@JoshuaBardwell awesome sauce thank you man myth legand
Sorry I got the happymodel Mobula7 hdzero.
Great information thx
Great overview as usual....😳🤔😀🇬🇧
So when you say "poor range", I guess you mean that it loses signal even inside the house? Because based on flight time, and size......I personally probably wouldn't even be flying this quad much outdoors, as I have 3.5" and mostly 5" quads for that. But perhaps many do fly these like their 5", outdoors.
I have a 2.5 in that I fly outside quite a bit.
Same, i fly my 2,5“ outside and i haven‘t had any issue regarding range. But that’s with an ELRS SPI receiver onboard ;-)
@@eyeflytinkerings I have an ep2 on mine so it has range for days
@@angelsinraver Well, I guess I fly my TinyHawk Freestyle 2 outside also, I mean......it can be flown in doors, but it is quite punchy on the throttle:)
Been trying to bind a brand new remote and a brand new drone I’ve had for a week now and it’s making me fucking sick. I’m bout to throw the shit out.
Shakes the weak hands out of the hobby
How do I *switch off* an SPI based receiver completely? (In this case a FrSky rx in the TH3)
It's not really possible as far as I know, without cutting a trace on the PCB or de-soldering a component.
@@JoshuaBardwell oh pity. Can I at least disable the indicator LED that shows the SPI rx looking for a D8 bind?
I really wish TBS would make a small rx/fc
I get random failsafes even indoors close to 5ft when flying with 150hz packet rate and dynamic power on with my mobula 8. It regains connection once I disarm and rearm...have you faced an issue like this?
This is very disappointing after moving to ELRS.
There's something wrong with your quad. I know this doesn't really solve your issue, but this is not an ELRS problem; it's not an SPI problem; it's not even a Mobula6 problem. There is something broken about your specific quad.
@@JoshuaBardwellThank you.. It is a brand new quad....it happens one time out of 8-9 packs. Do you think the CPU is getting overloaded due to dynamic power ON? Will reflashing betaflight fix it?
@@JoshuaBardwellI can't figure out what the issue is but I turned off Dynamic power as per Nick burns (power level locked at 50mw) and haven't failsafed for 10+ packs.
Solved: I switched off "LED STRIPE" in the configuration page as per Happy model recommended now my random failsafes are gone.
.. Or you can just solder on an ep2 as i did to not get mad, i know i know, but, i wanted my babytooth to get back as soon as possible.. :D
The biggest problem with isolated open source projects.
So ELRS 3.0 is out and not compatible with 2.x receivers; can my Zorro handle both 2.x and 3.x ELRS or do I need to stay on 2.x to be compatible with my Mobula 7? Or if it can't, does this mean I need to switch the Zorro back and forth between the two versions (or get 2 controllers)?
You cannot run two different versions of ELRS at the same time on the same module. So your Zorro has to be either 2.x or 3.x. There is a nightly version of Betaflight that you can put on the Mobula7 that makes it compatible with ELRS v3. Or you can get an external module to put in your Zorro, and run 2.x on the internal and 3.x on the external. Or you can just switch back and forth.
@@JoshuaBardwell didn't get the part about making the Mobula7 compatible with v3; isn't the ELRS version baked into the fc with SPI?
Yes it is. It's baked into the Betaflight code. There is a nightly build of Betaflight 4.4 that has barebones ELRS 3.0 support. I don't have the link right here unfortunately.
Hum... Interesting to know this about SPI ELRS receivers
I’ve thought about everything you mentioned in this video, but for SPI on 65mm, 75mm quads. I can live with this limitation. Everything 3” and bigger I can afford the weight of an external receiver.
Feels more like an implementation issue then an SPI vs UART issue. Not having looked at the actual boards with the ExpressLRS SPI implementation, it sounds more like they share CPU since the code has to be built into Betaflight, to save cost, instead of just using SPI for communication between the different functions.
Yes, my understanding was that SPI setups share the CPU with all the other functions of the FC.
@@lightbulbjim understandable then that they want to remove that behaviour from the board manufacturers, since it then creates that dependency. Would have been better to run SPI but separate chips/functions.
As someone looking to get into the hobby with a limited budget, I was looking at getting a BNF quad and I guess it has SPI ELRS. Would it be a bad idea for me to get it right now? I wouldn't plan on flying anything else in the near-future, so would I really have to worry about firmware updates or anything?
Personally I probably wouldn't treat it as a deal-breaker and would go ahead.
@@JoshuaBardwell thank you so much for the reply and the super informative video! Assuming I get everything to work, I probably shouldn't update anything until the next quad I upgrade to, right?
Hi, I just got this quad and for some reason it says No Gyro/Acc on betaflight. Do you know why this is happening. This is with no flight time just setup?
Most likely you flashed the wrong Betaflight target to it, so now the FC can't find the gyro. Go to CLI and type "version" and you will see the current target on the FC. It should be: CRAZYBEEF4SX1280
@@JoshuaBardwell I didn't flash it ,just got it yesterday and connect to betaflight to bind. I will check that.
@@JoshuaBardwell Hi, just checked and has CRAZYBEEF4SX1280 (hamo) 4.3.0 June 14 2022
@@JoshuaBardwell I saw your video on the Mobula6 and I checked my ports and the UART2 was on configuration/MPS ?