CCPM for Taranis

[ArchmageAU]

CCPM for Taranis

After helping numerous people on HeliFreak with CCPM on Taranis, I have decided to put together a lesson on how to do it.

My heli setup is fine. Why do I need this CCPM stuff?

In short, you probably don't. CCPM mixing in the transmitter is only required for flybared helicopters where the receiver directly controls the swash servos OR particular flybarless controllers (like 3GX) that derive inputs from a CCPM mix.

Most FBL controllers (BeastX, AR7200BX, vBar, iKon, Skookum, Naza, Bavarian Demon, Spirit, AS3X, etc..) DO NOT need transmitter CCPM .

For those that need transmitter CCPM, what is this post really about.

The objective of this lesson is to be able to set up a Taranis model with CCPM 120 instead of the standard Aileron, Elevator and Collective controls.

You will first need OpenTX 2.0.13 or later and Companion to create edit the model.

This is quite detailed and does go through everything about how CCPM works for Taranis.


Quick list for the impatient
This is for those that know all about CCPM, but just want a checklist of what to do and where to change stuff.

1. Program Ail, Ele and Col independent of mixing (-100 to +100)
2. Assign phantom channel in Mixes to adjust weight of collective. (Col pitch/Col+Cyc pitch)
3. Change weight of Inputs for Ail and Ele. (Cyc pitch/Col+Cyc pitch)
4. In Heli screen set swash type (ie. 120), collective channel input and optionally swash ring.
5. In Mixes set 100 weights for Cyc1, Cyc2 and Cyc3 on the channels that control the cyclic servos. Cyc1 must be on the center line of the helicopter.
6. Bind to heli and on the Servo screen reverse one channel if there is an “odd man out” when moving collective.
7. Use the Heli page reverses to make the blade angles move in the expected manner for the controls (up/down, forwards/backwards, left/right).
8. Use the Servo page to set PPM center at mid collective so servo horns are 90 degrees to pushrods (zero out cyc1, cyc2 and cyc3 temporarily to assist with this).
9. Mechanically adjust swash height to mid-travel by altering servo/swash pushrod lengths.
10. Mechanically adjust mid-collective pitch by altering swash/grip pushrod lengths.
11. Use the Servo page to adjust min and max servo values for cyclic servos to obtain desired min and max collective pitch (remove the zeroing out of cyc1, cyc2 and cyc3).
12. Test the cyclic pitch is as expected at min, mid and max collective pitch. Adjust by changing the collective weight and the cyclic weights.

What is CCPM.

For collective pitch RC helicopters, the direction the helicopter will travel and the amount of lift is governed by a swash plate. The bottom part of the swash plate stays aligned with the helicopter body, the top part of the swash plate turns with the helicopter blades. The top part of the swash plates determines the angle of the blades on each rotation of the blades.

Three or more servos vary the height and angle of the swash plate. The group of 3 or more servos that change the swashplate height and angle are called cyclic servos. This causes a problem with raw signals. For example, a single elevator signal one cyclic servo must go up and another must go down. This changing of the control signals to cyclic signals is called CCPM.

CCPM is cyclic collective pitch mixing. Strictly speaking, cyclic is the combination of Aileron and Elevator. Collective is the angle of the main blades.

But I said before that the 3 servos are called cyclic servos and cyclic is only the combination of aileron and elevator. In older helicopters, cyclic used to just change the angle of the swash plate using 2 servos (one lateral, one horizontal) and a separate mechanical servo used to raise and lower the entire swash cyclic mechanism. To simplify the mechanism, instead of mechanically moving servos (which takes a lot of power), all servos were linked directly to the swash plate and the vertical movement was added to the mix. So all 3 (or more) servos together control the cyclic, so cyclic servos.


The boring math bit of 120 CCPM.

You can skip this if you want, but some want to know how you change aileron(x), elevator(y) and collective(z) signals into cyclic signals (cyc1, cyc2 and cyc3) for servos spaces at 120 degrees around the swash plate.

Imagine a circle marked in compass points North is 0 degrees, East is 90 degrees, South 180 degrees and West 270 degrees. Now imagine cyc1 connected to North (0 degrees), cyc2 connected at ESE (120 degrees) and cyc3 connected at WSW (240 degrees).



If we push elevator forwards (positive), cyc1 will go down (negative) and cyc2 and cyc3 will go up (positive). So:

cyc1 = -cos(0)*ele
cyc2 = -cos(120)*ele
cyc3 = -cos(240)*ele

Remember from trigonometry from school.

cos(0)=1
cos(120) = -0.5
cos(240) = -0.5

Now if we pull aileron left (positive), cyc1 will stay level, cyc2 will go up (positive), cyc3 will go down (negative). So:

cyc1 = sin(0)*ail
cyc2 = sin(120)*ail
cyc3 = sin(240)*ail

Remember from trigonometry from school.

sin(0)=0
sin(120) = 0.866
sin(240) = -0.866

Now if we push collective up, cyc1, cyc2 and cyc3 will go up. So:

cyc1 = col
cyc2 = col
cyc3 = col

So if we add all the formulas together, we get:

cyc1 = (-cos(0)*ele) + (sin(0)*ail) + col
cyc2 = (-cos(120)*ele) + (sin(120)*ail) + col
cyc3 = (-cos(240)*ele) + (sin(240)*ail) + col

or when reduced for 120 CCPM:

cyc1 = col - ele
cyc2 = col + 0.5*ele + 0.866*ail
cyc3 = col + 0.5*ele - 0.866*ail

This is the current CCPM mix in OpenTX.

In OpenTX, you can reverse the inputs of aileron, elevator or collective. These reverses are done prior to the CCPM mix. This comes in important later when getting the orientation of the servos right.

As an aside, with this mathematics, you can change the position angles and find values for any positions (or even add phasing). 120X would be (90, 210, 330), 140 would be (0, 110, 250), 130 would be (0, 115, 245), 120 with 5 degree phasing would be (5, 125, 245). Remember, the CCPM number is the angle difference between the two aileron servos (so 140 = 110, 140, 110 as angles between cyc1:cyc2, cyc2:cyc3 and cyc3:cyc1 respectively)

From this, for CCPM 120, you also note that cyc1 is directly related to elevator and not concerned with aileron. For the CCPM 120 mix, the cyc1 servo must be in line with the mid-line of the helicopter.

One problem with the current OpenTX implementation is that there are no weights for the CCPM mix. cyc1, cyc2 and cyc3 are limited to -100/+100 (even with extended limits). ail, ele and col are also limited to -100/+100. If col is +100 (max pitch) and ele is -100 (full nose up), then cyc1 = 100 + 100 = 200, but this is then clipped to +100 (as it cannot go higher). So to keep resolution you need to manually reduce aileron, elevator and collective before they can be used in the calculation. Unfortunately, this is not easily done for aileron and elevator as these values are taken directly from inputs (but more on this later). There is an open issue with OpenTX development (issue #2032 - https://github.com/opentx/opentx/issues/2032 – Please add a support comment if you want the resolution to this raised in priority for a subsequent build).


Programming the model.

Theory and math out of the way, down to brass tacks.

I assume you have a model that has elevator, aileron and collective programmed.

1) Adding weights

First we need to program around the lack of weighting in the CCPM mix (issue #2032 - https://github.com/opentx/opentx/issues/2032 – Please add a support comment if you want the resolution to this raised in priority for a subsequent build).

How to determine the weights? If you want a collective pitch of 12 degrees and a cyclic pitch of 6 degrees, this is a total of 18 degrees. So 66.6% will be collective and 33.3% will be cyclic. Therefore the cyclic weight should be 66% (round collective down) and MAX cyclic DR (elevator or aileron) should be 34% (round cyclic up). To avoid clipping collective plus cyclic should be no more than 100.

To add weight to collective, create a phantom collective channel. For the example I will use channel 20. This channel takes the collective channel as an input and just reduces it's throw with a weight. Make it's input the mixed collective channel (output of all the curves) and set that as the input to the weight channel. Set the weight to 67%.



To add weight to cyclic is trickier. CCPM input is taken from the LAST channel to use the stick input. So if you use multiple inputs that draw weight from Ail, the last one will be used for input to the CCPM algorithm. If you want to use a buddy box, you cannot fulfil this criteria, so if using buddy box the slave must send a CCPM mixed signal to be used (less than desirable).

Lets assume you use max DR on one of your aileron and elevator inputs. For each of these, set the weight to 34%.

If you have multiple weights, like DR 100, 90 and 80. The weights would be 34%, 31% and 27% respectively (34 * 100%, 34 * 90% and 34 * 80% respectively).



While tuning CCPM it is highly advised to have only 100% DR on cyclics with 0 expo. Once you have finished CCPM setup, then add in more and varied DR and expo on cyclics to taste.

You may also notice I have NoTrim for the collective inputs. This prevents any trim entered by the trim added through the throttle trim tab from affecting collective. I also do the same for throttle. This will come in more important in the lesson on internal combustion (Nitro) helicopter setup.


2) Setting the Heli mix

You have the weights entered, next is the swash type on the heli screen.



None means no mix (the normal). Otherwise is supposed to represent the degrees between the aileron servos. 120 is evenly spaces around the swash, 140 is a spacing of 110 between cyc1 and cyc2 (or cyc3), 90 is a spacing of 110 between cyc1 and cyc2 (or cyc3). 120X means cyc1 is rotated 90 degrees (so aileron is in line with cyc1 instead of elevator movement). The formula for this is 180 - (degrees / 2). So for 140 spacing = 180 – (140 / 2) = 180 – 70 = 110.

(I say supposed to as there is another outstanding issue that needs solving: #2042 - Helicopter CPPM140 not correct - https://github.com/opentx/opentx/issues/2042)

From here on I assume you will be using 120 (as it's the one that works :-) ),

Next tell the Heli screen which channel is the collective channel source. (In the example I use CH20).

Lastly is the swash ring.

Swash ring ensures the combination of aileron and elevator STICKS, excluding trim, are no more than the distance specified from the center. It's exactly like you have put a virtual limiting ring over a mode 2 right stick (ail and ele on the one stick). The way it does this is check the non-trim value of the sticks. If (Ail * Ail) + (Ele * Ele) > (ring * ring), then do some math magic to reduce Ail and Ele to fit.

The advantage of swash ring is that is can prevent binding (as long as you only use none or positive expo). The disadvantage is that if positive expo is used, then the only place you can reach limits is on Elevator only. As ring only affects pre-expo (and pre-trim) inputs, both expo and trim can push outside the swash ring imposed limits.

I use a swash ring of 100. It is personal preference as to what you want to use.

The reverses will be dealt with later.


3) Setting the Mixes

Now that the swash type has been set to 120 and the collective input has been set, now is time to configure the mixes to send the output of the swash mix to the servos.



OpenTX uses CYC1, CYC2 and CYC3 as the outputs of the swash mix. These need to be assigned to channels in the mixer. Always assign these at weight 100% and offset 0. These are never mixed with anything else. Remember each one of these outputs has an effect on collective and cyclic response of the model.

If you need to limit the results of the CCPM mix, it is done in the Servos tab (and is done so evenly). If you want to alter the mix of elevator to aileron, it is done in the Inputs tab.

For Spektrum, the normal order is Ail is assigned CYC2, Ele is assigned CYC1 and Col is assigned CYC3. The most important part is that the CYC1 channel is the one that controls the swash point on the center line of the model.


4) Setting the Servo reverses

Now that the mixes have been done, it's time to turn on the helicopter and test the swash directions.

Ensure the motor of the model cannot turn the blades (for an electric heli with BEC (no separate receiver battery), the easiest way is often to disconnect the motor from the ESC). Leave the rotor blades on (as they will assist in determining blade pitch). Make sure that your transmitter is bound to the receiver.

Download the programmed model from Companion into your transmitter. Bind the transmitter to the model as setting the following steps needs to be done on the model to ensure correctness.

Once the transmitter is turned and bound to the model you need to navigate to the Servo page.

Move the collective up and down to determine if there is a servo that moves in an opposite direction to the other two. If so, reverse the one servo that goes the wrong way in the servo tab. Only change one servo, even if all servos then seem to travel in the wrong direction. This is also known as finding the “odd man out”.


You could do 0 pitch adjustment here, but ideally this should be done a little later once movement directions are all correct.


5) Setting the CCPM reverses

Now you are going to make the swash move in the right direction. Do not move to full limits of the sticks when doing this as the servo weights have not been set.

On the transmitter use long press on the “page” button to go back to the heli page.

Use the pitch of the blades to test direction, not the swash. Some configurations, the swash will move in an opposite vertical direction due to flybar mechanisms (Blade 450 3D comes to mind). Left/right, forward/backward can be reversed too dependant on leading or trailing edge control of the grips. In short, do not trust the swash, trust the blades. (Remember for cyclics, max pitch change happens approximately 90 degrees BEFORE where it will be observed for movement on a heli. ie. On CW swinging blades, to go forward, max pitch occurs on the right.)

First test up and down. If at up collective, the blades reduce pitch (leading edge twists down), change the “Coll. Pitch direction” to “INV”. Change should happen immediately. Try again and confirm correct.

Next, center the collective and test nose up, nose down on the elevator control. Move the blades so a blade is 90 degrees to the normal direction of travel with the leading edge of the blade facing toward the nose of the helicopter. Elevator stick down (nose up) should twist the leading edge of this blade up. If the blade twists opposite to the expected direction, then change the “Long. Cyc. direction” to “INV”. Change should happen immediately. Try again and confirm correct.

Lastly confirm the aileron control is correct. Move the blades so a blade is directly over the tail boom. Move the aileron stick in the opposite direction of the leading edge of the blade (for a heli who's main blades rotate CW this is right, for a heli who's main blades rotate CCW this is left). This should tilt the leading edge of the blade up. If the blade twists opposite to expected, then change the “Lateral Cyc. direction” to “INV”. Change should happen immediately. Try again and confirm correct.




6) Setting the Servo limits

Now that the directions are set, it's time to set the servo limits. This is also the ideal time to level the swash and mechanically set the swash limits.

First operation is to level the swash at mid-collective. To help with this, temporarily set the weights for cyc1, cyc2 and cyc3 to 0 on the Mixer page.



Now navigate to the Servo page on the transmitter so the PPM center can be adjusted for the CCPM channels. Use PPM center, not sub-trim as sub-trim will move the center and not the limits. PPM center moves the center and the limits.

For each servo, the servo arm should be 90 degrees to the servo/swash pushrod. First re-mount the servo arm as close as possible to 90 degrees so the PPM center adjustment is as small as possible (if required). Once the servo arm is adjusted to 90 the degrees, the servo/swash pushrod lengths should be adjusted to level the swash in the middle of its maximum negative/positive movement range.

Once the swash mid-height is adjusted, then the swash/grip link lengths should be altered to ensure the desired blade pitch is attained at mid-collective. For most RC heli pilots, this would be 0 degrees blade pitch, for scale pilots who may have blade pitches like -3 to +9, mid collective would be +3 degree pitch. Test pitch on each blade to help ensure tracking is correct, adjust by altering the swash/grip link lengths (I assume you had previously matched the weights and CoG of each blade).

Now that mid-collective is done, navigate back to the Mixer page and adjust the weights of cyc1, cyc2 and cyc3 back to 100.



Next step is to ensure max and min collective pitch are correct.

Navigate back to the Servo page and put the collective stick to it's bottom level (ensure you are in a flight mode that will give the lowest collective pitch pre-mixing). While at this state, ensure that the same expected low pitch is maintained by all swash servos. Adjustments can be made to this by altering the Servo Min (or Max if “Coll. Pitch direction” is set to “INV”).

Next move the collective stick to the maximum positive collective (in a flight mode that will allow greatest positive collective pre-mixing). While at this state, ensure that the same expected high pitch is maintained by all swash servos. Adjustments can be made to this by altering the Servo Max (or Min if “Coll. Pitch direction” is set to “INV”).

If you find that you cannot get the pitch you desire by adjusting Min and Max servo signals, you may need to move the ball links on all the cyclic servos further towards the end of the servo arms (lengthen distance from servo hub to ball).

Similarly if you find that you need to reduce the Min and Max servo signals in too much, you may need to move the ball links on all the cyclic servos further towards the servo spline (shorten distance from servo hub to ball).

This shortening and lengthening works even if using a bell crank servo with 2 attachment points as a cyclic servo will usually only move, at most, between -60 and +60 degrees.

With servos, you want the greatest amount of movement being used because this gives greatest control resolution. Servos are rated on speed to move 60 degrees. A cyclic servo on an RC helicopter should be no slower than 0.15s to move the full 60 degrees. Most like cyclic servos to move a little faster at around 0.10s. Too slow and the controls will feel sloppy. Tail servos should be faster again (0.10s to 0.05s).

If you alter the ball links on a cyclic servo, you should do it on all cyclic servos to maintain control resolution. Also, you will need to go through the levelling process again to ensure center and travel are to the expected limits.


Since servo extents have now been set, you can check for cyclic pitch are max, mid an low collective. While still at maximum collective, test the max cyclic pitches work as required and there is no mechanical or servos binding in any direction. Then move to mid-collective and re-test, then finally at minimum collective.

Should the cyclic pitch variations be incorrect and less than required, the ratio between the collective pitch and the cyclic pitch must be re-calculated and applied. The reason why is because the Taranis CCPM mix is limited to -100/+100. This may require a re-adjustment of the servo limits too.

Should the cyclic pitch variations be incorrect and more than required, the collective pitch can be adjusted down by altering the Ail and Ele Input rates. The reason why more does not need re-adjustment is that reducing Ail and Ele Input rates will not hit the limits of the CCPM mix. If it is a long way out, then you way want to re-calculate the weights and re-balance to regain resolution.


Congratulations. CCPM mix is complete.



Lets see If you have been paying attention.

Pop quiz.

1. What is CCPM?
2. What should you alter to adjust the servo midpoint in OpenTX?
3. In CCPM, what is “the odd man out”?
4. What would be CCPM weighting ratio for a collective:cyclic pitch of 10:6?
5. Why should you test CCPM directions against blade pitch, not swash?

Answers.

1. Cyclic, Collective Pitch Mixing (controlling the swash plate movement using only servos and no other mechanical method).
2. Servo tab, PPM Center
3. The method for determining which one of the cyclic servos needs reversing, if required. CCPM should only need at most one cyclic servo reversed since the collective input can be reversed before processing by the CCPM equations.
4. 10:6 = 62:38
   (10/(10+6)*100 : (6/(10+6))*100 = (10/16)*100 : (6/16)*100 = 0.625*100 : 0.375*100
5. Some helicopter head mechanisms require swash movement down to add collective. By testing against the blade movement ensures the controls will make the helicopter do what is intended.

References:

Here are some links that might come in handy:

“Newbies guide to the DX6i for RC helicopters” – https://www.helifreak.com/showthread.php?t=580508
“Beginners Taranis programming guide for RC helis” – https://www.helifreak.com/showthread.php?t=598718 (Although this is for another make of transmitter, it covers all the concepts as to how and why a transmitter works in relation to an RC helicopter).
“HeliFreak” – RC helicopter specific resource on the net – https://www.helifreak.com/
“HeliFreak OpenTX forum” – https://www.helifreak.com/forumdisplay.php?f=353
“RC Groups” – Lots of discussion on RC aircraft and helicopters – http://www.rcgroups.com
“FrSky Taranis with OpenTX 2.0 and beyond” – http://www.rcgroups.com/forums/showthread.php?t=2178865
“FRSKY Taranis ‘How to’ Thread” – http://www.rcgroups.com/forums/showthread.php?t=1914834
“Freddy Can Fly – 3GX setup video series” -

Align 3gx full setup video 1 (freddy can fly) (14 min 9 sec)

EEPE

CCPMTemplate.eepe

2 models.

CCPMHeli – One used in the lesson
CCPMHeliFM – CCPMHeli set up with flight modes and volume max once hold released.

(PS. Please leave feedback on what you think and any edits you think should be made).
(PPS. As an admin I stickied this thread, I will un-sticky if requested).

[rob221]

Fantastic effort
Dont know what the heli / taranis users would do without your help

[ArchmageAU]

Originally Posted by rob221

Fantastic effort
Dont know what the heli / taranis users would do without your help

Fly quads and/or planes instead (or work it out for themselves)

Just trying to make cheaper, more flexible alternatives, accessible to the majority (in my own way).

Hope this helps people. I like to see more people flying with less costly mistakes.

If OpenTX can keep momentum, hopefully we can get the physical TX's even better than the Taranis still at low cost (better switch quality, hall effect gimbals, etc..). If a TX manufacturer does not have to worry about firmware, they can produce better physical product at a lower cost.

[gadorey]

Brilliant! Thanks!
I have set my helis with Taranis with a NazaH or Spirit, but a mate of mine has a 3GX on his 600. I convinced him to change over to the Taranis, but I got stuck with the programming and setup for him, so I was having some difficulties until I found your thread. Saved me a lot of head scratching.
Cheers!

[gadorey]

I'm a bit confused, so time to ask for some help. I followed the instructions above and basically everything is working. However, as I try to setup the 3GX cyclic pitch setup and give right aileron I am only getting about 4 deg on the front blade. The 3GX requires 8. I tried everything but somehow I cannot get more than 4 deg on full aileron stick. Any ideas?

[piotrkundu]

I always wondered why you need global variables until today. I needed to adjust the roll rate for my V922, which uses 120 eCCPM swash mix. Somewhere between 30-40 is a good value and 30 it feels very docile and soft. Instead of changing CYC1, CYC2, CYC2 weight ratio I used GV1 (global variable) and mapped that across all the flight modes (FM0-FM3 = Norm, Hold, IU2, IU2). In Normal mode you can choose "Own value", but there are value boxes available in Companion (on Mac OSX). GV1 cannot be set, but is defaulted to 1024. In the radio you can make that change, but not in the companion. So i set it to 40 and copied the config to my computer. What happend was that I got my pitch and throttle correct in Hold, IU2, IU2, but in Normal the CYC1/2/3 were maxed out, regardless of my pitch which is on CH10.

I spent hours messing with my flightmodes and everything possible. Then I decided to test if GV1 might be used in a special way (since you are not allowed to edit in Companion) and set my CYC1/2/3 weight to GV4 and MAGIC, it worked. Seems to be something going on with GV1 that I missed in the manual somehow!

[gadorey]

Originally Posted by gadorey

I'm a bit confused, so time to ask for some help. I followed the instructions above and basically everything is working. However, as I try to setup the 3GX cyclic pitch setup and give right aileron I am only getting about 4 deg on the front blade. The 3GX requires 8. I tried everything but somehow I cannot get more than 4 deg on full aileron stick. Any ideas?

Update: not sure what I did, but I got it working. The only thing I can think of, is that I decreased the Wgt of the colective channel a lot in order to get +/- 12deg. I'm down to about 30%. My wgts on Ele & Ail in the Inputs Menu are also down to a little over 30% to get the 8deg pitch on cyclic. I haven't really understood it completely, but the calculation at the beginning of this thread for the 12deg+6deg = 18 which translates to 66% collective and 34% for the cyclics didn't quite work for me.

[Jermo]

Originally Posted by gadorey

Update: not sure what I did, but I got it working. The only thing I can think of, is that I decreased the Wgt of the colective channel a lot in order to get +/- 12deg. I'm down to about 30%. My wgts on Ele & Ail in the Inputs Menu are also down to a little over 30% to get the 8deg pitch on cyclic. I haven't really understood it completely, but the calculation at the beginning of this thread for the 12deg+6deg = 18 which translates to 66% collective and 34% for the cyclics didn't quite work for me.

Correct, to adjust cyclic you change the weights on the input menu for aileron or elevator, to adjust pitch you change the weight on the input menu for your pitch channel. I personally use GV for the weights as I plan to write a lua panel after more of the functions we need are in Lua.

[ArchmageAU]

Originally Posted by gadorey

Update: not sure what I did, but I got it working. The only thing I can think of, is that I decreased the Wgt of the colective channel a lot in order to get +/- 12deg. I'm down to about 30%. My wgts on Ele & Ail in the Inputs Menu are also down to a little over 30% to get the 8deg pitch on cyclic. I haven't really understood it completely, but the calculation at the beginning of this thread for the 12deg+6deg = 18 which translates to 66% collective and 34% for the cyclics didn't quite work for me.

Depends on how your setup is. The numbers are a guide (first pass). You can (and should) tweak to fine tune the pitches you need.

The constants are:
- CYC1, 2 and 3 stay at 100%
- Servo limits are configured in servo tab for each cyclic servo.
- Max of Ail/Ele weight + Collective weight should be 100 (or less).

The core principal is to give max throw on the servos without binding and find the appropriate mix input balance to give the desired collective and cyclic pitch ranges.

[hursto75]

I tried this set up and the ccpm does not seem to be working on version 2.1.5? Has anyone else had this issue? There is a different screen now for the Heli, with swash type, Swash Ring, Long. cyc, Lateral cyc, and Collective . Does anyone have this figured out?

Thanks,
Brad

[ArchmageAU]

Originally Posted by hursto75

I tried this set up and the ccpm does not seem to be working on version 2.1.5? Has anyone else had this issue? There is a different screen now for the Heli, with swash type, Swash Ring, Long. cyc, Lateral cyc, and Collective . Does anyone have this figured out?

Thanks,
Brad

Project for this weekend.

Effectively you set up inputs for "Ail", "Ele" and "Col" and use this as the inputs to CCPM as "Lateral cyc", "Long. cyc" and "Collective" respectively.

Set all to 100 and the guide works as planned.

Having weights allows you to resolve some of the "work around"'s mentioned in the guide. (But I do not have time now to expand on this - ie. weekend project).

[hursto75]

I have everything working.... i thought. when i move the Elevator only 2 servos move, not sure why the other is not mixing in?

Brad

[ArchmageAU]

Originally Posted by hursto75

I have everything working.... i thought. when i move the Elevator only 2 servos move, not sure why the other is not mixing in?

Brad

Post your .eepe and I will have a look.

Also what does the monitor screen show?

On normal CCPM 120 elevator (long. cyc) should move 3 values (CYC1, CYC2 and CYC3).

On normal CCPM 120 aileron (lateral cyc) should move 2 values (CYC2 and CYC3).

[hursto75]

It was user error, I had the wrong value in the Long servo value wrong, that is why one servo wasn't working. Thank you for your help, great how tos.

Brad

[Gmoore]

I thank you all for the help I am trying to setup ccpm for my 3gx on my trex 450 I have been stone walled will trying to setup ccpm when I go to mixes to setup the collective channel on channel 20 I cannot find (I)col anywhere what am I doing wrong and my heli setup screen looks much different from the one you show with many more options thanks in advance

[Tron]

Can someone explain the use of 'NoTrims' in the Inputs for Collective and Throttle?
I'm setting up ccpm in a nitro, flybar SDX.
Thanks

It is stated by Archmage:

You may also notice I have NoTrim for the collective inputs. This prevents any trim entered by the trim added through the throttle trim tab from affecting collective. I also do the same for throttle. This will come in more important in the lesson on internal combustion (Nitro) helicopter setup.

[JuanRodriguez]

Originally Posted by Tron

Can someone explain the use of 'NoTrims' in the Inputs for Collective and Throttle?
I'm setting up ccpm in a nitro, flybar SDX.
Thanks

It is stated by Archmage:

You may also notice I have NoTrim for the collective inputs. This prevents any trim entered by the trim added through the throttle trim tab from affecting collective. I also do the same for throttle. This will come in more important in the lesson on internal combustion (Nitro) helicopter setup.

I may have misunderstood your question but doesn't the quote by Archmage you provided answer the very question you are asking ???

[Tron]

Yes, I see how NoTrims on collective would be useful.

To clarify, I'm wondering why it is used on Throttle as indicated. I thought you would want to have trim ability on Throttle (say to adjust idle point on the nitro engine).

[ArchmageAU]

Originally Posted by Tron

Yes, I see how NoTrims on collective would be useful.

To clarify, I'm wondering why it is used on Throttle as indicated. I thought you would want to have trim ability on Throttle (say to adjust idle point on the nitro engine).

You do the idle trim on throttle a different way for a Nitro Heli vs a Plane on OpenTX.

On a plane, you can use a special option (Throttle Trim Idle Only) to allow -100 on throttle stick to have an idle value altered by trim. Unfortunately this affects ALL Thr values and messes with collective.

The better way to do this is a mix function that uses both Thr and TrmT only on the throttle input.

CH1: [I1]Thr Weight (+100%)
*= CH17 Weight (+100%)
+= CH18 Weight (+100%)
:= MAX Weight (-100%) Switch (SAdn) ** Cut **

CH17: TrmT Weight (-25%)
+= MAX Weight (+75%)

CH18: TrmT Weight (+25%)
+= MAX Weight (+25%)

Note:

• [I1]Thr has no trim.
• CH1 is the throttle
• CH17 is the total distance on the active Thr channel
• CH18 is the idle space at the bottom of the Thr channel

This way you get a throttle trim and a linear throttle from idle to max.

[robblot]

I have a flybar FHH 250 heli.I tried setting up the CCPM per instructions, but can't get the sim to work. No collective and no ail or elv. Here is my file, and any help would be greatly appreciated.