Support CRSF binding from CLI #8458
Comments
|
New crossfire firmware binds without the button and updates the rx. There is no need for this. I swap between two modules. I never touch the receiver. Just power up tx and put it in bind. Done! |
|
this has been removed as it was a bug. |
|
Im on 2.95 and can swap modules without the button. If it was a bug that was fixed its still working. |
|
@KnuckleUpFPV are you really on |
|
Yeah im on 2.95. Been on it for a few weeks. Ran 2.93 before that for a bit until the dropped telemetry bug from switching from 150hz to 50hz showed its face. Then went back to 2.42. Until 2.95 dropped and was supposed to fix the telemetry bug. Which it didn't. If you put it into force telemetry mode its fine. In normal mode it still drops telemetry after switching to 50hz mode from time to time. Are you still using the old configurator or agent x? If you are not on agent x you wont be able to get 2.95. Also get the early access code from the tbs lounge and put it in the settings after your device code. Seperate it with a comma. |
you need to reload the fw (got to a other fw than 2.95, update the rx and roll back to 2.95) btw - the lounge code is not used atm. there is no extra fw avalible with it. |
|
To add one more bit of information here: While the CRSF specification hints at CRSF commands for binding, the specification that was used to add CRSF support to Betaflight does not cover any details for such commands, and I am not sure if they were ever actually implemented. |
|
My 2.95 is a few days old. There is beta firmware for other devices. Like the smart audio fix. I went all the way back to 2.16 to test an issue for a friend. Couldnt take my lite back that far. But my full got rolled back then back to 2.95. Updated both modules at the same time to be sure they were on the exact same iteration of the firmware. |
|
This issue / pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week. |
stale
bot
added
the
Inactive
|
Automatically closing as inactive. |
|
I think binding from CLI is a good idea (for example the button on your Nano diversity doesn't work, like mine in this moment). Adding this feature is something already done in the TBS side or is a work for both TBS and Betaflight developers? |
|
Don't know if there is any status on this but personally agree. Having one nano missing the boot button. Have to replace it as I need to do a recovery. Another nano is buried in the quad and the sixty9 has the boot button at the underside of the board, not using the casing on a 20x20 it's hard to press the button - using tweezers it just like eating Japanese food 😁 |
|
Missing button too on my Crossfire Nano RX. If anyone knows how to put it in bind mode... Thanks! |
|
Finally replaced the nano receiver. Did you try to bind using the button on TX instead: |
|
I did. This is true for a new receiver I suppose. Mine is bound to a TX and I want to bind it to another TX. |
haslinghuis
added
BUG
Problem
When typically updating your TBS Crossfire TX module's firmware, this causes all previously bound Crossfire RX to be invalidated, forcing you to manually bind each one of them using a cumbersome and hard-to-reach physical button on the rx (specially on the Nano RX). This forces you, most of the time, to open up every single quad you have with Crossfire and consumes a lot of time. The user experience is really bad in that sense.
Suggested Solution
Imagine a CLI command, similar to
blfor bootload. Let's call itblingfor fun. When entering onblingmode, your RX is programmatically set to bind mode. I am unfamiliar with the CSFR protocol APIs, so take my suggestion more as a user than a developer's idea.The text was updated successfully, but these errors were encountered: