Sometimes you win, sometimes you lose. This time I've lost. Not by much, but always. During testing of my DIY LoRa RC link, radio caught a glitch during a flip few meters above a ground. It was not even a failsafe situation. Link recovered a few milliseconds later, but it was too late and quadcopter crashed into the ground.
During a roll, while being behind a tree, RX antenna got hidden behind a carbon fuselage and both antennas were at 90 deg. That was enough.
Damage is not severe, nothing I can not 3D print in one evening. It's more like a discredited honor or something.
The glitch was so short that is was not even recorded in blackbox log. RSSI was fine, no locked rcData. Quadcopter just kept 90deg attitude for too long.
There is a slight chance it was not faulted in software or hardware. Maybe there was a strong rouge TX polluting the aether. Why? I've caught a failsafe on a different quad (2.4GHz FrSky link) while being only a few meters away and a friend caught a failsafe on a TBS Crossfire. So maybe it's not entirely my fault after all.
Looks like I was able to solve all major known problems with my DIY long range radio system Crossbow. I'm writing known, since no idea what lies beneath… Anyhow… What changed? Quite a lot:
I've extended Arduino-LoRa library with ability to transfer full packet in single SPI transaction. Right now, each read of write to SX1276 uses single transaction. Previously, there were 2 transactions per byte…
The same library now has ability to send packets in async mode. Previously it was blocking code execution until LoRa packet was transmitted. Huge waste on processing time
With OpenTX 2.2.1 on the loose, I was finally able to drop PPM input from Taranis to TX module and replace it with S.BUS. But not without problems. According to specification, S.Bus should be SERIAL_8E2. But my Taranis clearly outputs it as SERIAL_8N2
For now, OLED display is disabled. It was taking too much time to update it using I2C and TX module was loosing S.Bus packets
I've improved RC channels processing time, time required for encoding/decoding went down by 1ms
LoRa modulation has some advantages. Like superb receiver sensitivity and immunity to interference. Has some problems, true, but at the end, it's a great way to send small packets of data to long ranges using low power.
Anyhow, today only one picture: how LoRa spectrum compares to FSK signal spectrum? Like this:
Those two peaks are nearby FSK stations, while plateau is 250kHz wide LoRa signal. Difference is at least clearly visible 😉
CC1101 is another example of modern radio modules. I might not have the receiver sensitivity or LoRa SX1276, but with proper antennas should give more than 1 km of radio transmission. Recently I got a couple of them, so expect some new projects with CC1101 and Arduino.
Now, something that took me some time to find out, so you will not have to: CC1101 pinout:
Only two weeks ago I thought I solved all my major problems with DIY LoRa RC link. I was wrong. I was able to solve one problem (link unstable due to rouge packets messing up with protocol decoding), but an old problem came up again: PPM input from Taranis is no longer stable. At least I know why since this is a second time this is happening.
Current code read bytes from SX1276 buffer inside interrupt callback procedure (ISR). PPM decoding is also done in ISR. How many threads ATmega has? What happens when one ISR is triggered while second is still executed? Problems. The solution is to keep ISRs as simple and fast as possible. My code was not simple and fast enough.
On top of that, it turned out that Arduino LoRa library I’m using is not efficient. It performs 2 SPI transactions to read one byte from SX1276 FIFO buffer. So, 12 bytes of typical data packet equals 24 SPI transaction… Looks like I will have to do some low-level coding I wanted to avoid in the beginning… Oh well…
Arduino LoRa is a great library that brings LoRa support (SX1276/SX1277/SX1278/SX1279) to Arduino world. I'm using it in my Crossbow LRS project (still not stable enough for flight, work in progress). Until now, the biggest problem with this library I've found is that examples suggests that heavy protocol processing inside interrupt callback is fine.
Unfortunately, it is not. It can lead to unexpected processing delays, create conflicts with other interrupts, bus clashes and other hard to debug things. This is why, the better way is to do packet reading (and processing) inside main loop and use read callback only to set a flag. Like this:
Only please remember to set all variables modified in ISR routine as volatile.
So, you want to build your own RC radio system? Long range maybe? Cool, I want to do it too. Since I'm pretty deep in that topic now, I can give you a hint or two. For example, have you thought about a protocol your radio system will implement?
Or rather should I say: protocols? Why plural? If you want to do a RC link that talks with popular radios like FrSky Taranis on TX side and servos or flight controllers on the RX side, it will have to implement at least 2 different protocols. More likely 3. And if you will want to add telemetry downlink, 4 or even 5…
Idea for Crossbow, DIY LRS system did not appearned in my mind out of nowhere. All my previous LoRa attempts were aimed at telemetry purposes only. E45-TTL-100 are cool, but bulky. If I would want to use them, I would either have to attach Arduino to it or hack it open and reprogram onboard CPU (like Qczek LRS does). Somehow it was not something what suited me very much.
But then I came across Adafruit Feather LoRa32u4 RFM95. Awesome idea. ATmega32u4 and HopeRF RFM95 LoRa module on one PCB, Arduino compatible, reasonably small and light. As a bonus, can be LiPo battery operated and has own 1S LiPo chanrger. The only thing I did not liked (OK, not the only one, but that was the biggest one) was price tag: $34.95 is somehow slightly more than I'm willing to pay for ATmega32u4. Even with radio module. So, after some digging on eBay I've found something that looked like a clone of Adafruit Feather LoRa32u4 RFM95: BSFrance LoRa32u4 II.
Looks like crappy range problem from previous post is fixed now. Today I managed to reach 2.8km range with better antennas. The ones I got from LoRa32u4 supplier were NOT 868MHz antennas for sure! 2.4GHz/5GHz probably, hard to tell. Traces on PCB are ~60mm long, so perhaps those are loaded 3/2 monopoles for 2.4GHz or 1.2GHz? No idea.
Anyhow, I soldered 78mm long copper wires to both TX and RX and did the same route as yesterday. At 500m link was solid. At 2.8km, link was solid when antenna polarizations were matched. With 40dB of link budget still to spare. Quite nice!
LoRa modulation was set to:
Coding Rate: 2
Spreading Factor: 8
Receiver Sensitivity (computed): -131dBm
Transmit Power: 17dBm (50mW)
Total link budget: 148dB
Payload: 13 bytes per frame
Now it's time to optimize air protocol a little and shave a byte or two…