I jumped in the rabit hole big time.

You bet! Really excited with what ELRS is doing right now.

Thanks Robert. Have been very heads down lately and have a pile of gear inbound. There will be a lot of videos on ELRS coming up.

You bet!

My pleasure!

It sure is. Great developments going on out there.

Even with good text it can be intimidating to digest the practical application. I kind of like this format too, but need to tone down the anvil :)

No problem!

Thanks! Appreciate the comment.

Thank you! Cheers!

It was weird, they weren’t quite as loud in the editor or in the KZfaq app. Try new things..gonna crack some eggs. I’ll know next time to turn them down a little more :)

You're very welcome!

You're welcome and thanks for hitting the tip jar.

Just hang tight on aux1. There are a lot of things happening right now. And I will have a video going up in the next few days. I have a LOT of ELRS gear inbound right now.

Uggh. That sucks.

Either arrangement: - ELRS Internal and 4-in-1 external or - 4-in-1 Internal and ELRS external will work great...

Thanks and welcome.

@@RCVideoReviews i have short term memory~car accidents,long story.i noticed i miss posted below ,was ment for a fishing channel,i deleted it im sure you ave enough to do! now im resettting up my radio and adding a cinewhooop ,havnt been mobile for 8months,poped 2 discson top of having a deteriorating spine,so sadly thiss is all new to me again even with 10 months of videos lol.God bless and please fforgive me if i repeat a question.not that i do it often as i try re read my posts.thanx for sharing.

TX parameters are set via LUA on the radio. RX parameters can be set via LUA or via the WebUI.

Yikes!

2.8 updated the range to use 0-100. So now you can chose an RQLY range that works for you. In speaking with one of the main developers he said going as low as 5 still works. Personally I’m think a n alert at 75 with a critical at 50 would be a safe starting point.

Look at my Beginner Series Playlist kzfaq.info/sun/PLy3TC1ILJYTjqDXFB84oXVWZG14zyMYYt and also take a look at my snippet videos: kzfaq.info/sun/PLy3TC1ILJYTjsMsQ2YF5ZCUubv0IFiWkd

@@RCVideoReviews thank you 🙏, but this looks like a link to Open TX. I’ll look to see if you have Edge TX for beginners.

Core functions are the same on both systems. i.e. Learn to mix on one, the mix rules apply the same on the other.

@@RCVideoReviews yup I agree. I’ve messed around for a few days now and think I’m a pro lol. Jk…it’s intuitive when you click around. I think I was just overwhelmed after all the problem solving with upgrading to EdgeTX. Thanks again for the responses

After discussing with the ELRS developers, I changed to 50/20. The reality is though, it doesn't matter that much. The number reported is RQLY which, even if it dropped to 5% at a paltry 100hz would still mean 5 updates are being understood on the RX per second which is still very good connectivity. At the time though, the radio firmware itself didn't allow a floor below 65. That has also since been changed.

@@RCVideoReviews okey! Thank you so much!

Does the external module work on the other radio? Did you update the LUA script? You really need to get on our discord and ask there. KZfaq is not good for sorting this kind of thing.

@@RCVideoReviews I did, the Discord invite says the "The address is invalid" when i click on it.

Not sure what to tell you. Link is in every video I post and I just verified it works discord.gg/jSFTASU

@@RCVideoReviews I'ts ok, thank you. I'm just gonna order another TX12 Mark 2 for my son. Not gonna spend any more time dealing with the HM ES24 TX external module. Thanks for trying to help. Much appreciated.

All the videos have the invite in the description: ► Discord - Hang out with the RCVR Crew: discord.gg/jSFTASU

If you're 100% sure you're bound, but the FC isn't responding, then you probably either have your rx/tx swapped, or the protocol on the FC is wrong.

@@RCVideoReviews Thanks I have had information from the fc like the betaflight version so i have reflashed the rx and started new with model mach and after few settings there i have managed to get it working but dat model mach is really confusing and hard to get it working

It indicates sensitivity. Higher dBm is better. So we'd rather have -5 than -10 RSSI, but was distance/obstacles between RX and TX increase, the dBm decreases toward the limit (-105 or -112). As your RSSI decreases, would you rather stop at -105 or would you rather be able to go to -112--which is -7dBm more effectively meaning double the range of -105.

Based on my research at the time, the higher numbers in the video were generally espoused best practices. Not content with guesstimates, I spoke with the actual developer and revised the range down based on his feedback. There is no harm in using the higher value so I left the video up. Model match is not burned in, but it part of the binding logic so if you use it to bind and disable it on the radio, you will have to rebind. I’ve done a lot of flying with ELRS at this point and believe it will be my primary Rx tech.

You're bound and have discovered sensors on the telemetry page?

@@RCVideoReviews what do you mean? With bound

The Rx is bound to the Tx and you've discovered sensors on the telemetry page.

You might want to check your work: "every 6-dBm increase in output power doubles the possible distance that is achievable." www.electronicdesign.com/technologies/communications/article/21796484/understanding-wireless-range-calculations I believe you're confusing power:dbm and range:dbm Everytime you double the power, you increase the dbm by 3. That has nothing to do with range. To double the range, you need to increase the dbm by 6. www.raviyp.com/calculating-the-range-of-a-wireless-device/ Double the power = 3 dB increase Half the power = 3 dB decrease 120 dB link budget at 433 MHz gives approximately 2000 meters (Chipcon rule of thumb) 6 dB improvement ~ twice the distance

Not the issue in my case. My dhcp range does not include LAN assigned statics. DHCP should really never try to assign IP addresses if the server is setup correctly.

@@RCVideoReviews the configurator RX Wi-Fi protocol will try and open a web page on 10.0.0.1 static so it can be configured. My Router IP address happens to be 10.0.0.1. I had to change that address for it to work. DHCP is not in the picture.

The RX only uses 10.0.0.1 when it is using it's own hotspot. In this case, your home router isn't relevant. If your Rx connects to your home SSID, it will ask your DHCP server for an address which should not conflict with your router if your DHCP is setup correctly. In either case, DHCP is used. If you connect to the hotspot, the Rx provides your wifi interface on the PC an address and it should be 10.0.0.2. If your RX connects to your SSID, the DHCP server on your wireless issues an addres. The Rx doesn't use 10.0.0.1 if it connects to the SSID so there is no conflict.

@@RCVideoReviews so the home router has to be set up for the 10.0.0.0 255.255.255.0 subnet inside dhcp for this to work properly?

Not at all. My home subnet is 192.168.1.0/24. Re-read my previous comment. There are two scenarios: Scenario #1) The Rx/Tx is in hotspot mode. In this mode, your home network has nothing to do with anything. The communications exist between the rx/tx and the computer directly. You are not connected to your home ssid. You are not connected to your home router. Your home subnet can be anything it wants to be because it's simply not material in scenario #1. In this scenario, the rx/tx uses 10.0.0.1 and your pc gets an address 10.0.0.2. Again, DOES NOT MATTER WHAT your home network uses in this scenario. Scenario #2) The Rx/Tx connect to your home SSID and ask the home router for an IP Address. In this instance, the HOME ROUTER IS RESPONSIBLE for providing an IP address to the Rx/Tx that does NOT CONFLICT with the home router address. In your case, if your home router is 10.0.0.1, then the router DHCP server should know this and NOT give 10.0.0.1 to the Rx/Tx. It should assign an address that is not already being used. Any further response on this from me will occur on discord.

Congratulations. You get the most ignorant comment of the week award. You're clearly clueless about the tech, so I'm not going to even bother with a debate. Go do your homework and try again. PS You might want to consider NOT polluting the Internet with ignorance.