expressLRS

Hi,

Despite many attempts I couldn't make ELRS TX module connected to DEVO 7E to bind with the receiver. I have:

- Happymodel ES24TX module
- SPI ELRS receiver built in BetaFPV 1-2S 12A FC
- I am using the latest "deviation-devo7e-v5.0.0-987234e" nightly build on Devo 7E.
- I've tried both ELRS 2.0 and ELRS 2.5.1 on TX side,
- on RX side it is ELRS2.0 I assume, since FC is flashed with Betaflight 4.3.0, official release
- I tried both UART inverted and not inverted option (don't know if it is important any more)
- On Devo7E CRSF protocol is chosen.
- Binding phrase is set on TX and it is also entered to SPI receiver using Betaflight CLI command (set expresslrs_uid =...)
- TX signal input is connected to tip point on DEVO 7E 3.5mm interface. It is also checked with oscilloscope and signal is present. LEDs in TX module are turned on, showing it is powered.
- The same TX module connected to Jumper T-Lite works fine with the same receiver

Do you guys have any idea what I am doing wrong?

Thanks.

Slawyn41 wrote: I DUNNO HOW TO ENABLE EXTERNAL RF AND I DIDNT FIND ANY INFO ON IT ONLINE

Deviation doesn't have control of the expansion bay power pin. You should see a little less than battery voltage on the JR bay power pins whenever the radio is powered on.

Did the radio come with a standard build of deviation, or did Radiomaster make some changes? What version (including radio model) did you install?

estojicmm wrote: Hi,

- I tried both UART inverted and not inverted option (don't know if it is important any more)
- The same TX module connected to Jumper T-Lite works fine with the same receiver

Do you guys have any idea what I am doing wrong?

Thanks.

Most of the configuration looks fine to me. The UART setting needs to be non-inverted for ELRS 2. With ELRS 3 or later and a TX with an ESP32 processor the inverted setting doesn't matter .

Are you using the model match feature? If so try turning it off. Since the 7e doesn't have enough memory to support CRSF configuration it also can't tell the TX at startup time which model match ID to use. I don't know if the TX powers up with the model ID it was previously using or not.

Thanks Hexfet for the quick reply. I am not using model match feature.

It is important information that Uart should be non-inverted on ELRS2.0. I am stuck with 2.0 because I have only SPI receivers. I have one regular receiver on the way, so I'll try with it as well once it arrives.

Might want to check the timing on the tip signal matches the bit rate you have selected for CRSF. And it looks strong with little noise? I'd stick with 400K bit-rate setting on CRSF until it's working. And 2.25M requires ELRS 3.

Hi
I have 7e 256 and R9M and R9M lite modules( elrs2.1). Can I use those? If so, which nightly should I use?
Thx

hexfet wrote: Might want to check the timing on the tip signal matches the bit rate you have selected for CRSF. And it looks strong with little noise? I'd stick with 400K bit-rate setting on CRSF until it's working. And 2.25M requires ELRS 3.

The signal is strong with little noise. Signal periods in 400K seems to be in exact inverse proportion to 2.25M (approximately 5 times longer).

Seems that my Devo7E doesn't communicate with HM ES24TX module. When this TX module is just plugged in powered Jumper T-lite I see substantial RF power emission on my DIY RF power meter, even without any receiver bound. That is not happening if TX module is connected with Devo7E.

gittaimi wrote: Hi
I have 7e 256 and R9M and R9M lite modules( elrs2.1). Can I use those? If so, which nightly should I use?
Thx

Deviation CRSF will support ELRS configuration on the 7e-256. I don't know about putting ELRS on that hardware.

The current nightly build is here .

estojicmm wrote: Seems that my Devo7E doesn't communicate with HM ES24TX module. When this TX module is just plugged in powered Jumper T-lite I see substantial RF power emission on my DIY RF power meter, even without any receiver bound. That is not happening if TX module is connected with Devo7E.

If you have a logic analyzer or FTDI you could check the validity of the CRSF data. I tested a build in my t8sg with telemetry and config disabled which is as close as I can get to a 7e. The TX and RX connected fine as long as model match was off so I think the 7e CRSF output should be fine.

If you enable the auto-wifi on the TX does it go into wifi mode after the timeout? That would indicate it's not receiving a CRSF signal.

That is the firmware I am using.
I don't have logic analyzer.
TX goes into wifi mode after the timeout.

Some people reported successful connection with Devo7E, so I am probably doing something wrong, but failing to find out what is the problem. I checked many times that everything is connected correctly. For now I am giving up.

Thank you very much for your development and your support.

New nightly build is available with some changes in CRSF.

* New telemetry sensor decoding for CRSF_VARIO, BARO_ALT (with vario), TX_ID, and RX_ID.
* Fix for CRSF menu COMMAND options that may change dialog type during operation
* Extend max dialog prompt length from 19 to 39 characters

The dialog fixes may not affect ELRS. Noticed the problem with TBS "Set Failsafe" command.

Users manual is updated. Since I can't update the official links I've used Github Pages to make a page with links to the latest Deviation build and manuals.

Deviation uploader 0.9.0 will not unpack the newest T8SG-V2 zip file. Downloaded several times with same result.
Still unpacks all previous firmware builds. Also unpacks newest T8SG-V2-Plus and 7e-256 files, just not T8SG-V2
Anyone else having same issue?

rc manic wrote: Deviation uploader 0.9.0 will not unpack the newest T8SG-V2 zip file. Downloaded several times with same result.
Still unpacks all previous firmware builds. Also unpacks newest T8SG-V2-Plus and 7e-256 files, just not T8SG-V2
Anyone else having same issue?

Are you using the DFU file inside to upgrade? That should work for firmware update.

The Deviation uploader should automatically extract the DFU from zip file. However, I also extracted and tried to load the DFU , did not work.

The dfu in the t8sg_v2 archive is zero length. Sorry about that. My build box has been crashing and must've interrupted that build.

I've rebuilt and re-uploaded. New download link is here

No issue at all. Thanks Hexfet, your work has allowed the Deviation program to live on.

You're welcome, and thanks!

Hi everyone,
I have DEvo F12E and I upgraded it with 8mb memmory and deviation-devof12e-v5.0.0-c84450e firmware. Is there anyone who success upgraded it with ELRS module ? What is steps ? I want to add Nano ELRS Tx Module 500mW ?

hexfet wrote: You have not done anything wrong. The Devo 7E does not have enough program memory in its processor to hold the CRSF telemetry or parameter code. These features are not available on the 7E.

Fun to hear someone is using CRSF through the trainer port.

Hi Hexfet,
I got same problem on my Devo F7 & Devo 8S , is that mean both TX have not enough memory for CRSF telemetry?
Thanks