EdgeTX / edgetx

EdgeTX is the cutting edge open source firmware for your R/C radio
https://edgetx.org
GNU General Public License v2.0
1.57k stars 333 forks source link

Search for Receiver and Auto Switch Model #3335

Open jmxp69 opened 1 year ago

jmxp69 commented 1 year ago

Is there an existing issue for this feature request?

Is your feature request related to a problem?

RX Search and Automated Model Selection

Describe the solution you'd like

Having been on OTX/ETX for the last 8 years, I've been shielded from certainm features on other radios. Recently while exploring the PL18 I found an option to "Search for Rx on Boot". Here's how it works:

Model 1 - Receiver 1 Model 2 - Receiver 2 TX off RX off

Last model on TX is Model 1 Turn on TX Pop-Up: "Searching for Receiver" Turn on Receiver 2 TX binds to Receiver 2 and automatically changes the model from Model 1 to Model 2. Turn off Rx Turn off Tx Turn on TX Pop-Up: "Searching for Receiver" Turn on Receiver 1 TX binds to Receiver 1 and automatically changes the model from Model 2 to Model 1.

I would consider this another major improvement in safety of EdgeTX as the radio now ensures the correct model is selected based on the RX turned on by the pilot which will be in the model the pilot intends to fly.

I am aware of Model IDs. This takes that feature a step forward by binding and switching to the correct model.

Describe alternatives you've considered

I don't believe EdgeTX has a programmable alternative for this feature request.

Additional context

Looks like I picked a bad week to quit sniffing glue.

pfeerick commented 1 month ago

I remember this one... if only for the additional context. 😆

I do like this idea (which I think Hitec also had on their Aurora9 platform?) from a usability standpoint, but one thing bear in mind is that it can only work properly if receiver/model IDs (aka Spektrum ModelMatch) are being used. i.e. this would not work with ELRS/CRSF if you don't use Model Match or D16/DSMX if you don't use unique model/RX numbers (and possibly others), as the TX will talk to any RX with the same passphrase/same ID, and thus would simply select the first RX that responds back with telemetry when stepping through your models, which could be the complete wrong model. It works well with Flysky system since they require a unique ID for each receiver... I'm pretty sure when you try to bind two receivers on the same ID it loses the configuration of the old RX completely, as they also store all the RX configuration data in that slot.

Now, if receivers would broadcast a unique hardware ID (think MAC address) as part of their telemetry, that would be different, as then you could then save that as part of the bind to the model config, and then if that matched when you are scanning, regardless of if model match is in use or not, you would know you have the right receiver. I think FrSky has an element of this in their ACCESS system... (as part of the registration/bind system) but that doesn't really help here.

Anyway, the point is that this is something that can only work in conjunction with a properly configured model match fleet, or with RF links that require it as standard.