Hi!
I wonder why there is no any FW development to support these powerful and cheap modules? There are full variety of them for 433, 868, 915, 100mw and 1w. Price is ridiculous starting from $4 to $8.
It was already implemented incredibly long range free LRS for these modules, that also supports Mavlink telemetry, but there is no any only telemetry dedicated FW.
Would be very nice to have it. Looks like it can be most cost effective link ever made.
Yes, it is slow for full telemetry, but for most main parameters it still can be very useful.
It can be used to drive AAT, or to show position on map, as well as add waypoints or lunch other mission commands. For most of the flights we donât need raw sensors data and other bulky things.
I totally agree! Even in itâs most extreme long range settings, the bandwidth is still on par with those of the Apollo missions. And crossfire is based on the SX1276 LoRa chip from Semtech.
Mostly I think the issue is that the lightest (and cheapest) modules canât simply be connected to a serial port: They only talk SPI and that is often not broken out in an easily accessible way. Still, I hope one day someone will write a communication back-end for them!
I bought these: https://www.aliexpress.com/item/32852066531.html?spm=a2g0s.9042311.0.0.27424c4d3JRSBl
They are dirt cheap and absolutely tiny and light. All the ones that I found with UART are basically this, but paired with an ESP32 for communication. E.g. the ones called âE32â: They are twice the size and the antenna connector alone weighs twice as much as the whole Ra-01 module. That seems overkill to me, when my FC (Omnibus F4 Pro V3) already has a spare SPI.
For those that indeed have UART, would we really need any changes in the FW? Wonât that be rather transparent, like HC-12s? At least that is how I envision itâŚ
Iâve mentioned Qlrs in the first message, as you can see, just without naming it. But Qlrs doesnât work like telemetry modem, it uses mavlink encapsulation, and it requests telemetry packets, which is completely different scenario. So it doesnât really help. We donât discuss LRS systems here.
Gotcha. Not sure it will be easy or even possible as LORA seems to present some challenges. QLRS 2.0 does have a full bi-directional Mavlink option but it is only for parameter configuration. It is very slow and it cannot run RC at the same time. You can switch in and out of that mode.
If anyone wanted to further develop this I imagine Kris would be helpful (QLRS Developer).