Support for wltoys K170 copter

Thanks for the update. I made a new build that simplifies things a bit and better matches the MPM channel scaling. Please let me know how this works. build e345a87 .

Can you better describe the servo behavior? For example, do you see the blades make a sudden jump from one position to another as you move the stick through the center point? or at any other point in the movement?
Some other things to note, though I'm not sure how the copter's flight controller might influence these::
- Moving the rudder stick should not cause any change in the main blades
- Moving the throttle stick should only cause the swash plate to move up and down, not changing any tilt

I didn't spot anything that might cause the connection to be unstable. Are the flashes of the FC LED related in any way to stick movements? Try changing the models Fixed Id and see if that makes any difference.

I flashed the newest firmware.

It's hard to describe the servos' behavior, you'd better watch the third video I attached.
youtube.com/shorts/0ZPWRLH8e2Q?feature=share
youtube.com/shorts/mgZZC7oMiT0?feature=share
Now it can turn on the motor but cannot shut it down like the stock one -- On the stock transmitter, you can turn on the motor by moving the left stick to the bottom-left position and the right stick to the bottom-right position (but you cannot shut it down this way).
If the motor spins for a while and the helicopter doesn't turn off, it will shut down automatically.

The links blow show the behavior with the stock transmitter.
youtube.com/shorts/F4UrrwIGkfc
youtube.com/shorts/BcVnIxc1fCM
You can find more details in the instruction mamual. Here you can find the pictures of the manual.
www.rcgroups.com/forums/thumbgallery.php...roup=none&starter=no

I've also attached my K170 settings file.

I used a fixed ID in Deviation, but the LEDs just behave the same as before.

(There is no initialization button on the FC board. I may lost the board if I forgot the Fixed ID during the test. The stock transmitter cannot help until I try the right ID on the deviation.)

Thanks, the videos are helpful. However it's uncertain what the switch settings were during the test so please try the updates below.

Normally the stock transmitter stick commands do not work in deviation (or MPM) unless you implement it in a mixer. For example, the gyro calibration is initiated by switch, not moving both sticks down-right. Same with takeoff/landing and emergency. The exception to this may be throttle up/down after binding.

I've attached an updated model file that moves the channel 8 mixer to channel 5. Deviation does not implement rate control on these protocols. So the switch controls in this model are:
* gyro calibration - move GEAR switch from GEAR1 to GEAR0 until aircraft acknowledges calibration (swash moves up/down), then back to GEAR1.
* takeoff/landing - move RUDD D/R switch from 1 to 0 until aircraft starts takeoff/landing, then move back to 1.
* emergency - move ELEV D/R switch from 1 to 0 until aircraft starts emergency response, then move back to 1

The model file you uploaded has the "off" position of the switches as the 1 position and I did not change that. I did change the power setting to 1mW - higher powers can overwhelm receivers at short distance.

Please make another video with devo10 where the aircraft (frame is sitting on the table. This will minimize servo movements created by the flight controller. Position the aircraft so the swashplate movements will be clearly visible Then:

1. Ensure GEAR, RUDD D/R, and ELEV D/R are all in the 1 position
2. Power on devo10, then plug in the aircraft battery. If the devo bind dialog disappears before the aircraft is powered, click on Re-Init to restart the bind. Throttle up/down may or may not be needed to complete the bind.
3. Use the GEAR switch as described above to initiate the gyro calibration. Hopefully the model will respond appropriately.
4. Move the rudder stick full left, then full right, then back to center. Move smoothly over a couple of seconds to make any servo movement more visible.
5. Repeat for elevator stick
6. Repeat for aileron stick.
7. Move the RUDD D/R switch to 0 to initiate takeofff (hopefully). Move back to 1 position after motor starts.
8. Repeat the rudder, elevator, and aileron stick movements.
9. Move the RUDD D/R switch to 0 to initiate landing. Move back to 1 position after motor stops.

Thanks for the testing!

Thank you.
I used your new settings. After binding at 1mW, the LED flashed, indicating an unstable connection, so I increased the power to 25mW. The behavior improved, though it remained unreliable (meaning some of my commands may not have reached the flight controller).

With your new settings:
- The motor activates when the left stick is held bottom-right and the right stick is held bottom-left.
- Rapidly toggling the gear switch up/down causes the LED to flash rapidly, indicating successful gyro calibration (though it occasionally fails, likely due to connection instability). , at about 30 seconds.
- At 30 seconds in the video, youtu.be/l3rT4cPD4Octhe . Takeoff sequence appears to work—all three servos respond simultaneously—but this is difficult to replicate.

The key issues seem to be:
1. the connection
2. the AETR channels
3. testing the other three channels is less urgent, and using momentary switches would be better.
The servos operate autonomously and show minimal response to AETR stick commands.
See the video .

By the way, can you generate several .dfu variants with different settings for better testing?

Sure, I will make multiple dfus if there are different changes to test.

I uploaded one new version. This fixes the channel scaling for AER - throttle was already correct. I'm hopeful this will help with link stability also since some invalid channel values were being sent. build eb7bd45 . Please try the same test routine with this build.