Orangerx, OpenLRSng, Naze32 – PPM input
The Problem:
I need to activate PPM input to the Naze32 board from the Orangerx UHF running OpenLRSng. PPM input is needed so I can use RC5 pin to control some WS2812 addressable LEDs.
The solution process:
In the Cleanflight configurator, enable RX_PPM. Connect the receiver Port 6 output to the RC input pin 1 of the Naze32 board. The problem is when I do that, and switch on the transmitter (ie the PPM stream is presented to the Naze32 input), the Naze 32 seems to lag horribly. Connecting it to the configurator takes ages for the screen to refresh.
I found disabling Telemetry in the openLRSng options for the orangerx Tx module seemed to fix the problem of the Naze32 board lagging. Now I can use the RC5 pin on the Naze32 board to control the addressable LEDs (WS2812).
The only remaining issue is that appears after arming once, then disarming, I can't re-arm with completely removing power from the Naze32.
“Start message not received within 10 seconds, disconnecting”
The Problem:
Trying to use the openLRSng Configurator app and connect to my OrangeRx Open LRS 433MHz Transmitter 1W just wouldn't connect and keeps reporting the error "Start message not received within 10 seconds, disconnecting"
The Solution:
- Connect your 3.3V FTDI USB to serial adapter to the pins inside the Tx module. At a minimum you need Gnd <-> Gnd, Tx <->Rx, Rx<->Tx connected.
- Make sure the Vcc pin is disconnected.
- Install the Tx module in your transmitter. I'm using a Taranis.
- With the transmitter turned off, advance the throttle to half. This stops power to the Tx module*.
- In the , openLRSng Configurator app enable the auto-connect check box next to "Connect".
- Turn the Tx turned on.
- Plug in the USB to serial FTDI.
- Wait until you see "Serial port successfully opened with ID: #"
- Pull the throttle down so the Tx initialises.
- There should be a couple of beeps and the configurator continues to connect.
Now you can configure your openLRSng Tx and Rx modules all via the Google Chrome Configurator and even use the Spectrum Analyser function.
* I'm not sure if other transmitter brands have the feature where power isn't applied to the Tx module until the throttle is at zero. I found the timing was important between connecting the USB and activating the Tx. With the Taranis it seemed to be much easier by having the Transmitter in the on state but with throttle up, as soon as the "connecting" message appeared, pull the throttle and it connected.
I did manage to connect without using the throttle up trick but only once and I couldn't get it to do it again. I read a post on rcgroups where a guy said it took him 20 tries before it would connect.
avrdude: stk500():not in sync: resp=0x00
The Problem:
Trying to flash the Hobbyking OrangeRX Open LRS 433MHz Transmitter 1W ( JR Compatible) with openLRS produced the error "avrdude: stk500():not in sync: resp=0x00" in the Arduino IDE.
The solution:
Buy a 3.3V USBAsp board and following the guide here, flash the bootloader to the board. Once the bootloader was installed, the openLRS firmware uploaded without any errors.
OrangeRx Futaba FASST won’t centre
Setting up the Seagull Decathlon radio gear showed the twin elevator servos wouldn't centre when the sticks were released. Swapping out the HobbyKing OrangeRx Futaba FASST Compatible 8Ch 2.4Ghz Receiver for a genuine Futaba receiver showed that the problem wasn't with the servos as the genuine Futaba Rx worked fine. By default the HobbyKing FASST receivers are set to HS Mode for digital high speed servos which is not so great for the analog servos in the Decathlon. The Frsky manual shows how to change between the modes as does this YouTube video.