New "nightly build"

bce9b99 This is in the test builds folder. The github nightly build is broken and I don't have access to fix it.

• PR1043 by bnmoore fixed an issue with number parameters in CRSF configuration
  
• PR1040 by phantom-8 fixed bug with audio when shutting down
• PR1044 added CRSF V3 speed negotiation and support for 2.0Mbps data rate with TBS XF Transmitter. If the model data rate is set to 400K the rate will be negotiated up to 2.0Mbps. But just select 2.0Mbps as the model data rate with TBS and the XF module will auto-baud immediately.
• PR1045 added support for Flysky AC type telemetry ("extended" telemetry) sensors. Tested by Pavel with altitude and temperature sensors. Added "max altitude" telemetry value to FrSky telemetry. On Telemetry test page the value is in the last row right-most column. Available in telemetry config as "MaxAlt". Reset to 0 by long press of UP on Telemetry test page.
• PR1046 CRSF configuration menu improvements
** When a parameter is changed, all elements of the current folder and the folder itself are reloaded. This handles dynamic changes to parameter names and options caused by changes to other parameters. For example, with ELRS changing the packet rate can cause the available switch mode options to change. This can be a little slow at 400Kbps data rate so be sure to use 1.87Mbps(ELRS) or 2.00Mbps(TBS).
** Parameters where the label + value lengths are wider than the screen are split into two rows. This fixes an issue with values partially overwriting label strings in the display.
** When navigating between folders the current selection in a folder is remembered. If the folder is opened again the same row will be selected.

Wow, wow, thank you very much for your efforts. I thought this project would become history:P

You're welcome. From your tx list looks like I need to add the latest stuff to the color screens too

I like my devo10 and t8sg, and I'm using ELRS so will keep up with CRSF.

Thank you hexfet for single-handedly carrying on the deviation legacy !!

0864258

PR1047
- hidden flag was not set correctly
- TBS param echo caused page update problem
- Fix overlap by a few pixels
- Add Show Hidden protocol option to display CRSF config parameters even when they're marked hidden.

The only place I know hidden parameters are used is in the TBS Radio Settings folder. Setting the Region to anything but Open changes the Region and Frequency parameters to hidden. The Multi-Bind option is hidden unless the tx is registered with TBS.
The Show Hidden option can be used to change the Region even if was previously changed to something other than Open. Changing the Multi-Bind option has no effect - the display will change back to Disabled after the change is sent to the tx. It can only be Enabled if the tx is registered. Changes to the Frequency when the Region is not Open appear to be accepted by the tx but did not test if the changes have any effect.

PR1048
- Add max altitude to Frsky telemetry to color screens, placed just right of regular altitude value.
- Bring color screen up-to-date with CRSF changes
- Remove support for LOLI protocol to free space for 256K processor builds

4d478f4

Couple of bug fixes for CRSF configuration. Commands and long folder names.

I have a devo10 I am try to get this to work. One problem after install my display is all messed up like this guy deviationtx.com/forum/3-feedback-questio...ating-nightly-builds and then when I try to rewrite the files and restart the transmitter I am asked to format my usb. I also tried nightly builds from 2021 same issue. I am on build 5.0 stable.

Jay1978 wrote: I have a devo10 I am try to get this to work. One problem after install my display is all messed up like this guy deviationtx.com/forum/3-feedback-questio...ating-nightly-builds and then when I try to rewrite the files and restart the transmitter I am asked to format my usb. I also tried nightly builds from 2021 same issue. I am on build 5.0 stable.

I think you may not have moved the compressed file to the main directory of the remote controller's built-in storage.

Jay1978 wrote: I have a devo10 I am try to get this to work. One problem after install my display is all messed up like this guy deviationtx.com/forum/3-feedback-questio...ating-nightly-builds and then when I try to rewrite the files and restart the transmitter I am asked to format my usb. I also tried nightly builds from 2021 same issue. I am on build 5.0 stable.

I just upgraded my Devo10 to the latest nightly and everything is fine. Maybe try the steps in the post you linked as it seems your filesystem is corrupted somehow.

CRSF protocol updated to support ELRS alternate arming method that will become available in ELRS version 4. Nightly build is here

ELRS version 4 will be adding a new arming method that doesn't use channel 5 (CH5) for arming. When the alternate method is used channel 5 can be used for full range in full-res modes. Details are available here .

This change adds a CRSF protocol option to support the new arming method. In the CRSF config model device the new option is "ELRS Arm". The default value is CH5 to maintain backward compatibility - CH5 is used for arming the same as in previous ELRS versions. The option can be changed to select the arming channel as any virtual channel (Virt1-Virt10). Then the virtual channel mixer output becomes the arming channel. Set the virtual channel mixer to output greater than zero to arm, less than zero to disarm. For example use the default simple mixer and set the Src to the switch to be used for arming. Note that changing the mixer name (e.g. "Virt1" to "ARM") will not change the channel name displayed in the protocol options.

The protocol option only has an effect if the radio module is running ELRS version 4.0.0 or later. The option is ignored for ELRS v3 where CH5 is the only arming method supported.

Thanks for your great work!
It's my first time to post here, though I have used the Deviation on Devo10 for about 5 years. The transmitter has satisfied my need for a long time, until I got a new bird, the K170 of WLtoys.
I have read the thread of K170 on RC groups and found that the DIY-Multiprotocol-TX-Module add support for the K170's protocol in January.
github.com/pascallanger/DIY-Multiprotocol-TX-Module/issues/1068

With a 4-in-1 moudule in my devo10, will the Deviation support it in the future?
The Devo10 has been my primary and only transmitter since 2018. Deviation firmware has extended its lifespan significantly.

Thanks, I appreciate it.

From the info in the link I can add support to Deviation. I'm currently traveling so it might be a few days. I'll post here when the build is updated.

Had some downtime so went ahead and made the changes. Found some interesting differences between deviation and MPM in the existing HonTai protocol implementation so this may take some testing. Please try the build here . Once it's working I'll merge and update the "nightly" build.

The HonTai protocol has a new format option XKK170.
I'm not sure about the channel scaling so please let me know if the AETR controls work correctly.
Channel 5 is gyro calibration. The MPM code notes this as "momentary".
Channel 6 is takeoff/landing. Also momentary.
Channel 7 is emergency. Also momentary.

Deviation doesn't implement rate selection in these protocols. The rate is fixed at high and the mixers should be used to tone down the flight controls as needed. Let me know if that causes a problem.

The videos I watched did not show any activation of "emergency" so don't know what that does. The videos also showed stick commands for gyro calibration and takeoff on the stock transmitter. But also show a takeoff/landing button so don't know what the difference is there.

Thanks.
In fact, the FC board of the K170 is similar to a drone's, with 6G mode and 4-channel helicopter controls, even though it has 3 servos and a mechanism identical to the K124. However, it lacks a 3D mode. Because of this, some hobbyists replace the stock FC board with one from a K124 or K110.

Unlike the 911S, the K170 cannot shut off the motor immediately by lowering the throttle stick. Instead, it uses two buttons on the stock transmitter for emergencies—pressing both simultaneously stops the motor.

Like a drone, it takes off and lands automatically:
you can’t take off immediately even if the blades are spinning at high speed. You must hold the throttle stick for about a second, after which it takes off automatically. Landing works the same way—you can’t land instantly; you need to hold the throttle stick down for a similar duration.
So to do the same thing it also use a button for one-key takeoff/landing.

It’s been a long time since I last flashed the firmware.
So it may take me some time to complete the task: backing up the firmware, models and settings files, but I will try my best.
Also, is there a K170-like model available? If so, I could copy it with minor modifications; otherwise, I would have to create a new one from scratch.

I flashed the test firmware on the transmitter. Here are the steps I followed:
1. Flashed the .dfu file using the Walkera DfuSe tool.
2. Copied the files and directories from the .zip package to the transmitter. (not include the .dfu file and the .zip file)
3. Restored my backup files and directories: `tx.ini`, `hardware.ini`, and the `models` folder.
It works well with the K110 using my old model settings, but I can't find the new protocol you mentioned. Also the HonTai protocol doesn't seem to work.

Which protocol should I choose? Did I do something wrong in the steps?

For the K170, select the HonTai protocol in the model setup. Then click on the protocol name to access the protocol options. Format is the only option. Scroll right until it displays XKK170. Then exit back to setup, power on the K170, and click Re-Init on the tx. Hopefully the copter will bind.

I don't know of an appropriate existing model. Standard airplane model should work. AETR on first four channels, and put channels 5, 6, and 7 on switches. The devo10 doesn't have pushbuttons so just toggle the switches for testing. Section 11.3 of the manual describes how to make momentary switches.

Now that you're running the latest version, for future builds you'll only need to flash the dfu.

I found the K170 protocol and tried to use it, but the binding failed.

I also followed the instructions from this link to set up the model:
www.rcgroups.com/forums/showthread.php?4...7s%20instructions%3A
I set AETR as instructed, but it still didn’t work.
For now, I’m just using regular switches for channels 5-8, since setting up momentary switches seems too complicated for me at the moment.
Here's the picture I attached.

With the stock transmitter, after turning on both the radio and the helicopter, I quickly push and pull the throttle stick and they bind.

Thanks for the feedback. I reviewed the code and found a couple spots I had missed a required change, and it would prevent binding. Please try this updated build b3f4392 .

Using the rcgroups post as a basis for the model is fine. Except in deviation the gyro calibration is on channel 5 and there is no channel 8. The rate is fixed at high - use the mixers to tone down the controls as necessary.

Thanks for your hard work.

I flash your new firmware.
Still using the previous model and haven't changed any settings.
Binding works, it's great, but the connection is unstable. The LED on the FC board occasionally flashes, indicating signal loss.
Also the AETR channels aren't functioning properly either - the servos behave erratically.

Thanks. Since this may take some back and forth I opened another topic just for the K170. Let's continue there.