Advanced Search

Hello, my name is Bruno Karlsson and I made a mistake when I installed Deviation 5.0.0 in my Devo 8s. By mistake I did not choose all files I should have chosen when installing the program. Now my computer does not recognize the Tx only partially. I does not show up with an E: .However the DeFuse program recognizes the Tx. What can I dp now? Is there some way to delete the Tx memory and start all over again?

Best Regards Bruno Karlsson

Select USBHID as the protocol on the model config page. Here's the description from the manual:

The USBHID protocol will convert he transmitter into a USB joystick. Connecting the transmitter to a PC via the USB cable will enable the transmitter to be detected as a joystick by the computer. This may be used to enable the transmitter to control any simulators that support joystick input. Some initial calibration may be necessary and is accomplished via the control panel applet of your operating system.

hi , i use a walkera devo 8s with deviation tx 5.0 and i am trying to connect as joystick by usb, i dont know which parameter y have to change for use my RC as joystic and connect it by usb.thanks

My much loved Windows 10 laptop recently died and I replaced it with a new laptop that came with Windows 11 pre-installed. Disaster!

I now can't do any upgrades/installs onto my Devo 7e, as Windows 11 either doesn't see STM32 DFU as valid or cannot find a driver for it. Also, from searches on the web, STM32 DFU doesn't seem to be supported on Windows 11 at all and there are various comments about problems with support of USB 3 (and that's what my new laptop has).

Does anyone have any idea how I can still use the tried and tested uploaders I've used in the past with my new Windows 11 laptop? Also, as a general warning to all of you keen hackers out there, stay with your tried and trusted Windows 10. Windows 11 is not the marvellous cure-all Microsoft would have you believe.

Thanks for taking a look. Yes there are a few reasons not to put the bitrate setting with the TX module.

Test build is updated - 9c4e73b . I did decide to change the bitrate settings to use abbreviations - it looks better. This build also has a change to support 1000Hz packet rate. Looks like that will be coming soon in ELRS.

I've seen some videos of the storms over there. Not flying weather.

I installed 0150291 and #1435. All seems to work.

Any bitrate format is fine with me. It fits in the screen so.. You can also say, legacy, megabaud, multimega or something to make it more snappy.

From a ui design it may be nice to have the baud rate setting part of the TX module settings since that is where the setting is for. From a technical point of view that may be tricky so I understand why better not.

We have terrible weather, storm and rain so I am not sure when the next flight is going to be.

New test build is available - 0150291 . It implements the idea in the previous post - it works well. After clicking on the protocol name the current model name will appear at the bottom of the device list. Clicking on the model name allows.the bit rate to be set. I chose to display the model name to emphasize the bit rate is stored separately for each model.

The available bitrates are 400K, 1.87M, and 2.25M. The ELRS PR #1435 is needed to run 2.25M, or just add 2.25M to the baudrates array in the code. This is the fastest I could get the serial link to run.

The ELRS protocol is no longer needed but I left it in the test build so as not to break any model files. It is now identical to CRSF so it needs to be removed before a merge to master. With the test build any models with ELRS as the protocol will revert to 400Kbps. While the rate can be changed with ELRS still set as the protocol, please change to CRSF so models won't be affected by a future upgrade to a nightly build.

Comments invited! Maybe the bitrate selections should use abbreviations instead of showing the full bitrate number?

I have several Devo10's and have the gain set to the highest. I've never had an issue using 3s 2200mh lipo batteries. Always fully charged before I leave for the day. I wonder morenabout the receivers. I currently use 4 or 5 cell nimh. I'd like to switch to LiFe but wonder if I should use a bec set to 6 volts

jfitz66 wrote: Will the extra voltage from the LIFE battery do any harm?

And if so, then you lose the whole model because the Walkera RX fails due to the overvoltage? Is that really worth the risk? What about the electronics connected to the receiver, like servos or an ESC? Can they handle this voltage?

What is the final charge voltage of the LiFe batteries when they are 100% fully charged? I found 3.65V, so that would be 7.3V instead of the 6.6V you mentioned.

My suggestion would be to reduce the voltage safely to 5 volts. Look for so called StepDown or Buck Converters, which always give the same output voltage at different input voltages. There are for example types with 5V / 3A.

Here is an example: www.adafruit.com/product/1385

So call me old school but I've always used NiMH 4.8 volt packs to power my Walkera receivers but can I use 6.6V Life packs instead. The documentation lists 4.8 to 6.0v if I'm not mistaken so I've been cautious about trying a 6.6v LiFe pack on them. Really just want to get away from the NiMH altogether. Will the extra voltage from the LIFE battery do any harm? Is anyone already doing this?

Thanks all! Glad i could help out.

I'm spending some time on getting the CI going but don't have credentials to update the nightly builds page. I can set something up for test builds.

The idea for warning about protocol not matching the module would be nice to have. I'd like to eliminate the ELRS protocol but need a way to set the serial datarate. One thought is to add a "handset" device to the CRSF config page where the bitrate could be set. It makes some sense to put it there because the handset has it's own CRSF device address. In Deviation the bitrate would be stored in the model file.

Thanks for keeping deviationTX alive HexFet!

I've had no problems with recent builds either.

One thing crossed my mind earlier. Maybe ELRS should be disabled/blocked in CRSF and vice versa to be sure people use the optimal protocol.

Hexfet,
Fantastic work! Thanks do much for keeping Deviation alive and well. I've been following this thread since the beginning and using your last 2-3 test builds . I probably should have chimed in earlier, but I didn't have any issues with any of the test builds while flying.
I was considering an open tx radio, but no need now! I've been using my T8v2+ as a daily driver for years, just keeps going.

Thanks for developing! And congrats with the result! I hope many people will enjoy ELRS on T8v2. It's a jump of a light year into the future.

I haven't seen anything disturbing on d00091a for 6 flights and a few hours of clicking around. The flickering menu buildup is not an issue but maybe something to note.
If I notice anything worrying in the future I will let you know here. If you want me to test or develop something for you, you have my email.

Thanks again!
~ Mooiweertje

Any chance of CI-driven builds so this can be accessible to users on the normal download page?

Great. Thanks for all the testing. I've merged the PR. Please let me know if anything crops up.

Need to get the manual updated, and I'm trying to get nightly builds going again. Until then I'll post a test build named "nightly_build".

The parameters that ELRS keeps separate per model id are listed on this page .

Flights went smooth as silk.

So the TX can store setting per model? So over 60 storage places? That makes it a little more interesting. I might want 2 model types, race quad and plane.

Yes, my understanding is that the RX is updated when the TX parameter Model Match is turned on and off. I don't use model match either so it's unfamiliar. One thing I find confusing is that the TX stores some other parameters besides fixed id on a per model basis, like packet rate and telemetry ratio. So those can change when the fixed id is changed.

Shouldn't be any way a parameter would spontaneously change. Is it possible a button was pressed while things were moving around?

Hope the flying goes well!

It seems to work very well. I saw the bad/good and connection in the title of TX and RX page. I'm flying 4 lipo's on quad this afternoon to see if there are any "failsafes".

When I turn off and on model match the RX is updated both on and off. Seems to work perfectly. Is this according the design? I've never used model match before so I don't know what is required/expected.

Something I haven't been able to reproduce yet. I once had during reckless turning of T8, TX, etc during connection that model match spontaneous was turned on, on the T8 and as expected the connection wasn't set up and I got the model match popup.