4G6S (2610S) Pitch Servo Jump

I just downloaded this software to my Devo 8s and I must say it is nice to be able to control all of my helicopters from this controller. I downloaded the 4G6 profile a few pages back and had to change a few settings and I was able to come up with a working solution, but I experience a large servo jump on the pitch servo near center. I haven't been able to find a solution so I tried a nightly build from sunday to see if it would correct the issue, which it would not. Anyone have a solution? Other than that this profile seems to work.

In the past there were reported some errors in conjunction with the WK2601-protocol.
Have you tried it with WK2801 and 6 channels? If not, did you play with the different modes for WK2601? I think I have heard "heli" should be used instead of "6+1".

Ive tried WK-2801 mode on 6 channels and the 2610S receiver will not connect. In WK-2601, Heli mode nothing seems to work properly and the heli will spin up even with the throttle hold on and the throttle lever has no effect on controlling the throttle. Ive got it set to WK-2601 6+1 mode and it seems to work fine besides the pitch servo jump near mid-stick. WK-2601 5+1 stops the pitch servo from working entirely. Does anyone have any more things I should try before we call this a bug?

I believe to remember we had a similar discussion for this or other Walkera rx with the WK2601-protocol. PhracturedBlue often told us that there are problems with it.
I don't remember these discussions in particular, but you will find them when you look for threads with helis like V120, 4G3, 4G6, V200. I am not sure but there is a good chance you will find additional hints there.

haykeye13 wrote: Ive tried WK-2801 mode on 6 channels and the 2610S receiver will not connect....

This is strange because with the WK-2801, you could bind in 2801 mode, change pitch ST1 curve by modifying the throttle curve, then you would switch to 2601 mode to fly.

cf this post on RCG :

"Note:
You can't adjust the throttle curve in normal mode or ST1 mode.
Throttle curves are hard coded. There appears to be no way to adjust the throttle curve with this Rx.
So you adjust throttle curves to adjust the pitch curves.


The plain fact is the throttle curves are hard coded into the 2610S Rx. There appears to be no way to adjust the throttle curve with this Rx.

PLT is to set your top and bottom pitch in Idle-up. PIT is to set your hover pitch in Nor flight mode.

Adjusting throttle curve in 2801 NOR affects pitch curve in 2601 NOR.
Adjusting throttle curve in 2801 St1 affects pitch curve in 2601 Idle-up (3D).


PLT controls the amount of +/- pitch you have in Idle-up while PIT adjusts how much pitch you have in Nor flight.
The lower (more "-") you add to PLT, the less max pitch you will have. You can also then adjust the Idle-up pitch curve
itself (if you have a 2801Pro) by switching to 2801 mode and adjusting the throttle curve and going back to 2601 stick mode.
Manny and I use this option to smooth out the curve so it "feels" right in flight. The higher you make PIT value (more "+") the
less pitch you have at start-up and Nor flight. So in order to have "0" pitch at mid-stick, the values are roughly what you have.
If you keep PLT at "0", the pitch curve is too steep and you end up with way too much pitch (at top and bottom collective stick) that
will bog the motor in Idle-up flight mode. If you leave the PIT at "0", you will have too much pitch at 1/4 to 1/2 stick in NOR flight
mode which makes it harder to control and land without cutting the motor out.


Throttle Hold does not work in ST-1 or ST-2, only in Norm mode. The flight mode is to go into 3D mode and gives constant
throttle with pitch control (collective).

Here are the settings I am using.

Under GyrPat I have
PLT -124 ATS 0%
Pit +500 SEN 23%
Exp1 0
Exp2 0

The throttle curve is very aggressive in stunt modes as soon as you leave center stick pitch comes in really quick so I went under Stick put it in 2801 mode
then went under Throttle curve and this is what I have my ST-1 set to.

ST-1 0 38 50 62 100
This will change your pitch curve in ST-1 in 2601 mode to make it less aggressive.

Now on the on the RX if you look at it down from the front of the heli it is set up like this.

Bal Delay is set to 8:30
Elev gyro 11:30
Aile gyro 12:30
Elev/Aile EXT is maxed out.

Also make sure that the heli is perfectly balanced because any vibrations and the gyros will make the swashplate move around."

From TomZ sticky settings post : www.rcgroups.com/forums/showpost.php?p=16328063&postcount=2


.... Ive got it set to WK-2601 6+1 mode and it seems to work fine besides the pitch servo jump near mid-stick.

With the 4G3 and the 2601 TX, you must set the Helicopter mechanically at ST1.

As per this post from Ampdraw in the 4G3 thread :

"Firstly I worked out which aspects were, and more importantly, were not, able to be changed via tx settings in regards to pitch as I wanted no or very little pitch change when switching in flight from norm to idle up (stunt).

In regards to pitch:
The V1 knob adjusts the pitch in normal mode so we can achieve the desired 0* midstick wheras V2 adjusts the pitch entire range in a linear fashion.....here is the important part......the amount of pitch set at midstick with the V1 knob has no effect on the amount of pitch in idle up at midstick so it is imperative the mechanical setup is done for midstick in idle 1."


www.rcgroups.com/forums/showpost.php?p=12833287&postcount=5121


Maybe the same applies to the 4G6 with 2610S RX?

EDIT: The Wk-2801 is a 8ch protocol, is there a reason you would set the number of channels to 6 ?

Maybe the receiver is expecting to see 8ch when it receives the "flag" for the WK-2801 proto ?

Then sees only 6ch and doesn't bind ?

I have the same Problem with my HM4G6S (RX-2610S-1). Created a config to control each channel (Ch1, Ch2, Ch4, Ch6) directly. The movements of the ELV and AIL servos is very short. The PIT makes double the movement and is jumping around the zero point. This is the same behavior i can see with the heli config. Not sure if this comes from the protocol or the TX. Heli and 6+1 shows the some behavior. With 5+1 the PIT servo does not move at all.

Heli Config


Test Config

I just gave up and use my wk-2801, the 2601 protocol is the worst thing ever born...

I think for this to work you have to emulate the following from the 2601 proto that the 26xx series and 2801 transmitters had :

Step 6. Go into GYRPAT and set to:

PLT -124 ATS 0%
Pit +500 SEN 23%

I’m actually using the HM4G6 with the WK2801Pro. It is working fine there but I don’t do 3D so an easier setup will work for me. If I watch the behavior of the channels in the monitor of both TX they look to be the same. What the receiver and servos are doing is not correct with the Devo 10. Looks to be something is affecting the results on its way (additional mixing in the transmitter code for 2601 or in the RX itself)? ELV and AIL servos only move about ¼ or 1/3 of the way. The PIT servo is using nearly the full way and is jumping around the zero point. All servo directions are working as expected. This is very strange.

I will try to get it to work. I already have looked into the code (wk2x01c) and installed the build environment. I already build the deviation firmware successful. My plan is to add an additional channel mode for the 2601 protocol in addition to the 3 existing ones (i.e. "6") which does not manipulate the channel 6 in the transmitter code. The actual question is how I get the source code for the 3.0 release build. I would like to avoid to work with the development code to reduce other side effects. Any help would be appreciated. Thanks.

When you installed your build environment you have the necessary preconditions.
Make a clone of a repository (you will take the actual one from PhracturedBlue). I would recommend to copy the repo from PB to a new one for yourself via bitbucket (get a bitbucket account, got to PBs repo and fork it to a new one).
Ok, back to the clone: clone PBs or your new repo into your build environment. You will get the actual development state.
Again a recommendation: take this as base. It might be hard to rework your changes when it is time to integrate it into the main deviation code when the base versions are too far away... and I won't expect side effects because the wk26xx-code wasn't affected recently (last changed in February, look here: history wk2x01.c ).
If you still want to take the deviation-3.0.0-code as base, run "hg update --rev v3.0.0". This will revert your working copy to the v3.0.0-code.

Thanks for the information. With side effects I meant changes which are done in the whole code since the release. I don’t expect changes outside the wk2x01.c file for now. Looks to be everything which is not working for the HM4G6S is related to the manipulating done in the code there. If I have success I will send the updated wk2x01.c file.

I'm regaining hope

Started the first tests with modified protocol code. Adding an additional mode was no problem. Tested a few different code variants without much success yet. Ma be we will not get around to log and analyses the protocol with the proper setting for the model with a wk260x or a wk2801. Unfortunately I don’t have the required equipment for such a procedure. For me it looks to be the receiver can be switched into different modi from the transmitter which influences the servo output. Proceed with some more testing now.

Any news? I have the same problem. I would Love to fly my 4g6s with Deviation.

Unfortunately i have no news. My last test don't show any other results.