Advanced Search

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

I'm looking around and there's not a download of 5.0 for my F12e.
Does anyone know where all the downloads are?
I wish I knew that this before I bought this. This place was booming with life a few years ago.

I haven't been here for awhile. I modded a F12e with a 4 n 1 and it was stolen so I bought another F12e and I am wondering if there is anything newer than the 4 in 1 module that I should buy to install for deviation?

Thanks in advance. this is such a great project, I hope it's still going.

Hello everyone, Im an old new guy in here
I have had my 12s for a long time and blew up my rx1202. so now i am looking at upgrading the 12s for othr protocols. but dont know what exactly is needed. i have some tinkering experience in soldering. I tried a few times to install deviation on it also with no success, all i would get is slanted lines on the screen.
I would greatly appreciate some help on this as i do love this 12s nd at the time it wasnt cheap.
I am also on Facecrap under the screen name unstopabul. feel free to message me there too.
Thanks everyone
George Arneth. the one with the army patch. other one is inactive but am locked out of that one.

There's just a couple sentences about it in the User Manual in the CRSF section: "The CRSF protocol sends Crossfire protocol serial data on the transmitter’s trainer port (tip connector). The trainer port ring is ground. To enable telemetry the serial input must be tied to serial output. For the trainer port tie tip to ring1."

Easiest would be to make an adapter cable with a stereo (three-wire) plug to insert into the trainer jack on the devo 10. Tie the tip and ring1 together and connect to the CRSF pin on your ELRS module. The outside ring wire goes to the ground pin on the ELRS module.

Hello everyone.
I have a Devo 10 and I'm delighted with it.
I want to add an external ELRS module and I don't know which one to buy to add it.....
I also have a Jumper T Lite JP4in1, to play in simulator mainly and I would prefer to be able to share the module between both.
On the other hand, the subject of the connection to the module, is it documented somewhere?

What model t8sg do you have?
What firmware did you install?

I'm having the same issue, I used to have my Aux 4 set up as a switch to my mix, but now it doesn't work anymore I don't really know what to do with it besides using a different channel or trying to use trims as switches

Yes, ELRS is supported but the version to use is found under Downloads, Test Builds, [hexfet]nightly_build . Unfortunately the automated nightly builds from github are not working.

Current link is [hexfet]nightly_build but the url will change next time the files are updated.

Hello everyone! I just got my betafpv micro 2.4 500mW module, and currently trying to use it with my T8SG V2 (non-plus). I have updated the firmware to the latest version and using the crossfire protocol. I'm trying to bind to the built in module on Matek f405 WTE board labeled as DIY 2.4. It seems that after flashing both the TX and RX they bind together for a bit, but then become disconnected and go in wifi mode. It also seems like when I bind the TX and RX for that short amount of time I don't have any link with the module and the transmitter, as if they're not talking to each other. Question is, can you use modern ELRS systems with the T8SG V2 with the new firmware installed?

hexfet wrote: New nightly build has a fix for this.

Problem turned out to be special Lua characters sent by ELRS in the Pitmode option list. Deviation doesn't know Lua special characters. For now I've replaced the up-arrow with 'u' and down-arrow with 'd'.

Confirm that the crashing is resolved now. I need to test the channel changing later but everything looks smooth and no more errors in the menus.

New nightly build has a fix for this.

Problem turned out to be special Lua characters sent by ELRS in the Pitmode option list. Deviation doesn't know Lua special characters. For now I've replaced the up-arrow with 'u' and down-arrow with 'd'.

Unfortunately the automated nightly build is broken. I've been making a build but url changes with every update. Current is https://www.deviationtx.com/downloads-new/category/2877-hexfet-nightly-build

Best to go to the Downloads link in the left column, then Test Builds and look for "[hexfet]nightly_build"

I will take a look. Likely the config menus have grown and are overflowing buffers.

Edit: confirm I can duplicate the problem

Thanks so much! No idea why but i only got a blank page from the link above.

Is this what you searching for?

www.deviationtx.com/downloads-new/category/13-nightly-builds

hexfet wrote: Builds of the latest software are here . The repo automated build is not currently working.

For Frsky both versions of ACCST (D16) are supported. ACCESS is not supported. Not sure what's new for Futaba but haven't been any recent changes in that protocol in Deviation.

Update history is here. There've been a few recent updates.

Hi,

Just checking in for the first time in a while to see if I should do an update to the latest nightly.

The link above to the latest nightly updates take me to a blank page.

Could someone please link me to the latest nightly updates since the automated system isn't working?

Thanks so much.

Zap

hexfet wrote: Please post anything more you learn. Won't be able to try 3.0 myself till mid-October.

Running on eLRS v3.0.1 now and your last build. Everything is working well except when I enter the VTX Admin menu.... Trying to do anything in the VTX admin causes the radio to power off!

I am using the BetaFPV 1W Micro TX and I've flashed the backpack. Under EdgeTX this allows the user to pick band/channel/power and attempt to send it. Goggles and quad should then update VTX settings.

Never seen a bug that caused the radio to totally power off before, not a freeze but totally shutdown.

Bonjour
je viens de me rendre acquéreur d'une radio TX 8
Bien[ évidemment j'ai connecté celle ci avec une batterie 2S
Au démarrage, pour la première fois j'arrive tout de suite sur USB protocol?? et non pas sur la page menu model .. pour configurer un avion
Que faire pour venir la page menu modèle ??
dans l'attente
merci
cdt
JJ GEOFFROY

Unfortunately I don't have a tip where to buy a touchscreen for the 8s. The number of dealers has also become very scarce. One option would of course be to buy a used working 8s and use it as a spare parts stock.

However, your description of the error has triggered the thought in me that this could be a purely mechanical influence and not a defect of the touchscreen. Such an influence could be caused by dirt, foreign objects, a twisting of the screen or a pressure point in the screen's frame.

In your case, I would demount the 8s, completely remove/expose/examine/clean the screen (if you haven't already tried this) and reconnect the components so that a test of the screen is possible outside the case of the 8s.

It may also be oxidation in a connector or a connector has come loose. For a touchscreen that operates with resistance changes, that would be a possible explanation for the problem.