Advanced Search

Yes, i have set the option to Minima (the other one is optima, for receivers with telemetry as far as i know). Also, my firmware is devo10-v5.0.0-c45cc8b, which is a bit old, but it dates well after the Hitec protocol was implemented. So, it must be ok.

You mentioned the fine tuning but not the format option. Do you have format set to Minima? Only guessing as I don't have these receivers. Don't know of any problems with the protocol but hopefully someone with the receivers will post.

Hello everyone. So many years after, i still fly with my trusted Devo 10. Recently i got chance to try a couple of Hitec Minima 6E receivers. Deviation supports the protocol, and although i manage to bind successfully, the motor never works the way it should with either the receivers. At the beginning it won't start, then if i keep the throttle up at somepoint it initiates, then works abnormally. I have tested all other components with other type of protocols (like DSM2, DSMX, Flysky), an everything works ok (all escs, and motor tested worked fine) but with the Hitec Minima receivers the motors (or maybe it is the escs) fail to work properly.

What am i missing? It must be something to do with the protocol, or a parameter i don't take into account. Note that i have tried the frequency fine tuning thing, it isn't the problem. Is there a known problem with Hitec protocol or Hitec Minima receivers? Thank you.

The multimodule was already installed several years ago.
By mistake I have formated the device, and wanted to recover it.
It's my dads devo, I can't bind 977 with transmitter.
Somebody know how I should do it?

Maybe this post will help. Generally it's just power on the heli and press the Bind button in Model Setup. I probably still don't understand what you're asking and don't have this heli. Search the threads here or rcgroups.

You didn't understand me. I need an instruction of process.

The v977 uses the KN protocol so you'll need an NRF24 device in your devo10. This post has a v977 model file for t8sg that you can adapt - just change the switches. There's some other posts about v977 - use the search button above to find them if you have trouble.

Hi guys, I bought new 977, and I have devo 10. I don"t know how it can be binded.

Help me please.

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.

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?

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!

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.)

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.

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

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.

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 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.

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.

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 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?