Advanced Search

Does anyone know the protocol for the Twister range of helicopters?

Try the drivers offered by the Zadig program if you're using Windows. Another user reported Windows 11 doesn't work for running dFuse.

Test build is updated - 46e93f1 . This version has a change to fix the CRSF parameter pages getting stuck on LOADING at 400Kbps and 500Hz packet rate. In these conditions ELRS splits CRSF messages into more chunks than usual. Deviation had only allowed for a max of 5 chunks but ELRS was sending 6. Increased the limit in Deviation to 10.

Another issue may be in play as well. The ELRS master branch has a fix for a glitch on the serial line when the UART is not inverted. That fix is not included in the 2.X maintenance stream so is not in 2.3.0. The glitch may also cause errors when loading parameters. If the CRSF config menus still don't behave well with the above test build, please try it with an ELRS build from the master branch.

I'm in the same boat. Did you have any success in solve it?

How do you manage to install the correct drives? I 've been had a hard time to fix it.

Not a problem. I've added the non-plus version to the current test build directory.

Ah.. sorry... I meant elrs v1.0 using the deviationtx build provided by Phobos indeed.. I'll update everything in the next couple of days..

By the way.. you're compiling it for the 'plus' version, with the oled screen, no? I've got the Carbon looking 'v3' which uses the 'non plus' firmware.. it's got an lcd screen if it's not too much to ask maybe for your next build, build one for the 'non plus' version as well? If that's too much of a hassle, I'll understand!

Cheers, Ton

hexfet wrote:

tonh wrote: Hey guys..

I've been happily flying elrs 1.0 for a long time now. Why update if it works, right? I've had some spare time last couple of days.. (caught covid... time to update everything... ) ...Been reading up on this. Am I correct in understanding that with 1.0 (Phobos' DeviationTX build) I'm not actually running 500hz? If that's the case, then I'm really going to need to update this. Really appreciate the tlc deviationtx is getting, Hexfet! thanks!!!!

Thank you! I'm a little uncertain about the version numbers you're giving. You should be using ELRS 2.X version else the config pages won't work.

I think you might be using "1.0" as the change Phobos made in Deviation. That change adds support for multiple packet rates including 500Hz. However it did not implement full CRSFshot. I saw an ELRS change go by a few weeks ago that I think made CRSFshot required, but I didn't look into what ELRS does if it's not there.

There are several other improvements as well and you should definitely upgrade. Latest test build - d3964e5 .

Okay, that is the same behavior I see. I'll look into what's happening in the next couple days.

So, looks like tx/rx connected at appropriate rate. However tx elrs menu gets stuck in updating good/bad packet rate display, states LOADING and stays there.

Rx elrs menu shows correct good/bad packet rate and connection status.

TLM 1/64
Occurs with rx on/off.

tonh wrote: Hey guys..

I've been happily flying elrs 1.0 for a long time now. Why update if it works, right? I've had some spare time last couple of days.. (caught covid... time to update everything... ) ...Been reading up on this. Am I correct in understanding that with 1.0 (Phobos' DeviationTX build) I'm not actually running 500hz? If that's the case, then I'm really going to need to update this. Really appreciate the tlc deviationtx is getting, Hexfet! thanks!!!!

Thank you! I'm a little uncertain about the version numbers you're giving. You should be using ELRS 2.X version else the config pages won't work.

I think you might be using "1.0" as the change Phobos made in Deviation. That change adds support for multiple packet rates including 500Hz. However it did not implement full CRSFshot. I saw an ELRS change go by a few weeks ago that I think made CRSFshot required, but I didn't look into what ELRS does if it's not there.

There are several other improvements as well and you should definitely upgrade. Latest test build - d3964e5 .

rc manic wrote: 500 Hz packet rate cannot be selected unless baud rate set to 1.8M or higher. According to ELRS website, 500Hz should work with 400k baud rate?

I don't see this behavior. What are your other ELRS settings? Are you testing with receiver connected or not?
I'm able to select 500Hz with bitrate 400K on ELRS 2.3. The only problem I saw happened when switching from 1.87M to 400K while the packet rate was 500. In that case the ELRS info message didn't seem to be working (haven't debugged yet). But otherwise I didn't have any issues with 500Hz at 400K.

With tx model ID limited to 0-63, if you do NOT want to use model match, my receivers have required model ID to be set at 255. Is this is in accordance with ELRS design specs? I was getting a model mismatch EVEN IF model match was set to off. People should be aware you have to set rx to model ID 255, or you will get a model mismatch error..

That sounds consistent with what's described in the Model Match section on this page .

Hey guys..

I've been happily flying elrs 1.0 for a long time now. Why update if it works, right? I've had some spare time last couple of days.. (caught covid... time to update everything... ) ...Been reading up on this. Am I correct in understanding that with 1.0 (Phobos' DeviationTX build) I'm not actually running 500hz? If that's the case, then I'm really going to need to update this. Really appreciate the tlc deviationtx is getting, Hexfet! thanks!!!!

Had a couple of brief flights last weekend. Everything seemed to work well. I am having issues with consistent random link loss using a HM ES24tx and betafpv 2.4 lite rx, but I think it's a hardware issue with the rx. Running ELRS 2.3

Few things noticed:
500 Hz packet rate cannot be selected unless baud rate set to 1.8M or higher. According to ELRS website, 500Hz should work with 400k baud rate?

With tx model ID limited to 0-63, if you do NOT want to use model match, my receivers have required model ID to be set at 255. Is this is in accordance with ELRS design specs? I was getting a model mismatch EVEN IF model match was set to off. People should be aware you have to set rx to model ID 255, or you will get a model mismatch error.


Yet to do more testing with betafpv micro 500mW tx to see of everything still works, once I get a new receiver.

Hello, where did you connect the 3 essential wires for the functioning of the module on the I need to have the ppm? Please let me know!!!

Good morning to please tell me how you connected the power supply and the ppm of the module on the radio do I have to? I would like to install in the module irx4 + my must f12 which does not support deviationetx

Deviation doesn't support flashing the receivers. An opentx/edgetx transmitter can do it. There's also some flashing software out there but a little circuitry is needed. That's at the bottom of the attached doc.

Hello. thanks for answering.

I would be ok re-flashing the XSR receiver, can I do it with my jumper T8SG V2 plus with the pins behind? Or do I need a more advance transmitter like the Radiomaster TX16S?

thanks

The R-XSR can work but the firmware version on it matters. The page doesn't have that information but there's one comment from someone who needed to re-flash the R-XSR.

Deviation supports the ACCST firmware, both versions 1 and 2. It does not support the ACCESS firmware. If you're comfortable re-flashing the XSR you can make it work.

Hello.

I've been googling like crazy but I can't find a solid answer.

I want to use my Jumper T8SG V2 with this drone which has a FrSky R-XSR Tx:

GEPRC CineLog 25

It seems like it should work, but I want to be sure before buying it.

Thanks

New test build is available - d3964e5 . This has some UI improvements for the Fixed ID, which is now limited to a max of 63 in the editor. Also an update to handle new info that's being added to the ELRS info message. Please post if you have any feedback.