request for crsf protocol support
I'll put in a soft request for crsf (crossfire) support.
I'm flying expresslrs on a quads/planes with flight controllers and would like to use it on helis.
I'm interested in flying/using the tiny rx's with tiny antennas on my heli.
The Crossfire protocol is a radio frequency communication protocol (that work at the900MHz band instead of the 2,4GHz band) between transmitter and receiver in which our flight control units are not involved.
Instead, our control units receive and decode the most common and widely used serial signal protocols from the receivers.
Since Crossfire receivers can output serial signals according to PWM, PPM, and S.Bus protocols, and our controllers are able to decode all these communication protocols, you only need to tell our controller which of these three output protocols has been activated and used in the Crossfire receiver.
crsf is also a full duplex serial communication protocol from the radio to the module and then from the rx to the flight controller.
TBS made this very confusing.
I was hoping for this serial protocol support. I understand i'm probably only a few people that would ask for this, but throwing it out there at least.
have a good one.
We believe that those who buy and use the Crossfire TX/RX system do so in order to have a 900MHz radio frequency connection system between transmitter and receiver mounted on the model that is different from other radio systems. This is to ensure a better connection in areas where 2.4GHz signals are disturbed or to have a greater range. This choice is basically made for model control and is certainly not made just to use a different serial protocol through which to receive the same telemetry data that are not required and not indispensable to fly the model.
Moreover, the Crossfire protocol does not communicate in half duplex mode, as many other protocols do, and therefore requires two separate and distinct ports and connectors between receiver and control unit, one for the TX signal and one for the RX signal. Instead the S.Bus protocol needs only one single connection to work.
In addition, the telemetry data of ESCs or sensors connected to our flight controllers can also be recorded in the memory of Flight Logs of our controllers and then reviewed, analyzed and evaluated at the end of the flight.
With the last release we wanted to highlight that even those who use this 900MHz radio system can already use it with extreme simplicity and ease with our control units.
As far as the Crossfire serial protocol is concerned, through which the telemetry data can also travel, since the protocols can be assigned to any connector of the TBS receivers, the CRSF RX and CRSF RX connections are obviously already usable in a "parallel" manner distinct and separate from the S.Bus connection by other devices that use this serial communication protocol and that can be connected to the receivers on board the model independently from the S.Bus communication channel through which the data of the various model control channels travel.
In order to be able to say with certainty that this system worked properly with our control units, we obviously had to purchase transmission modules and receivers in order to make the necessary and due verifications.
Since we have also recently received from TBS the documentation and specifications of their telemetry communication protocol, and given the investment already made for the transmission modules and receivers, we will also implement this telemetry protocol in one of the next releases, however, given the very small number of users who request it is not currently among our priorities.
i understand, thank you for explanation.
I'll stick with inverted f.port for now, which was an awesome change, thank you.