Advanced Search

Hi,

what can you see when you look up "Transmitter menu" / "Channel Monitor"? Is the value of CH3 rising from -100% to +100% when you move the Throttle Stick?

What is your TX Type?

Greeting
Dirk

I am a biginner and I would like a template about ESC motor control.
I try to setup it, but my CH3 stick works only from the center to the full throttle
From the down position to the center of the stick the montor don't run.

many thank in advance

Devo f12s doesn't supported by Deviation.

Hey! Im sorry to post in this old post but there is a way to check if UDP messages are the same bits for UART communication between wifi and flight controller (yellow wire)?

C'est ici

www.deviationtx.com/downloads-new/catego...hexfet-nightly-build

bonjour
je recherche un nouveau deviation pour ma radio jumper t8sg v1
je suis actuelement sur deviation-t8sg-v5.0.0-06c2f7d , je voudrai savoir si il y a en un nouveau
si oui , je voudrai bien lien de téléchargement
merci

In general look for "[hexfet]nightly_build" in the list on the Test Builds page . Unfortunately the link to that build changes every time it's updated. I don't have github privileges to update the "official" nightly build link.

The current latest build is [hexfet]nightly_build

Habe die Lösung selbst gefunden. Das upgrade über USB mit kopieren
der Dateien funktioniert nicht. Man muß in jedem Fall eine DFU Installation
mit Walkera DfuSe machen.

Das upgraden von Version 4.1 auf 5.0 bei meiner Devo10 über USB funktionirt nicht.
Es bleibt immer die alte Version 4.1 drauf.
Beim upgraden auf eine Nightly Version wird keine Versionsnummer angezeigt
und es sind keine neuen Protokolle verfügbar
Kann da jemand helfen?

vanuatuian wrote: not sure if this will help, but for me i have the carbon edition radio and i found this version "deviation-t8sg_v2-v5.0.0-60968b7" worked for me in the above link. i was originally using deviation-t8sg_v2_plus-v5.0.0-60968b7 and it was giving me weird artifacts all over my screen.
good luck!

So the version deviation-t8sg_v2-v5.0.0-60968b7 is work for you ? Could you please share the link download for me ?
The link above was expired..

THanks

hexfet wrote: Unfortunately the official nightly builds are not working. Download the latest t8sg_v2 firmware here . This firmware has better support for ELRS and multiple fixes, including for the long name issue.

Jumper setting information is here .

Could you please share new link ? I think that link was expired..
Thanks

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.

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.

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 .

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.

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).

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

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.

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.

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.