SemiArticulate Veteran Location: On Location
| "In an ECCPM setup, as you call it, the individual servos movements are obviously divided between cyclic and collective functions."
No, that is MCCPM. The freya, raptor, etc. are ccpm systems. CCPM just means collective cyclic pitch mixing. So basically if your swash moves up and down to control collective, it is ccpm. MCCPM is not the issue. They are among the best control systems. ECCPM is where the servos all act together to control both cyclic and collective. On 120 degree ECCPM, you can't make a cyclic input without changing all three servos. You can't make a collective input without changing all three servos. You also need to change all three for combinations of the two. If you give it forward cyclic, the front servo pulls down and the two toward the back must move up a little or you will reduce collective. Now I fully agree that if you exhaust the travel of the servo for any function, you will affect the travel of the other functions. That is a design issue. The thing about linear servos is that nothing else on the heli moves in a straight line. Just like Steve Campbell2 pointed out about the tail. The rotating servos lead to rotating parts. So if you want to put a linear servo on the swash, its output can not be "linear". We are using the word "linear" two different ways. One being moving along straight line, the other describing the relationship of the ouput. For example, lets say you want to tilt a swash one degree per second with a hydraulic cylinder. The hydraulic cylinder can only move in a straight line but pivots at the rod end and blind end. The rod end is attached to the swash, the blind end is attached to the frame. In order for the swash to rotate one degree per second the change in the length of the cyclinder can not be fixed. Its rate of change will be different (non-linear). Now put two more on the swash 120 degrees apart and have them not only change the cyclic but also the collective. The mathematical model would probably not be very difficult but it gets more difficult when you realize that not every company will want to stick the servos in the same exact spot with the same size swash. That is the rub. So if you want the best ECCPM system in the world, you would have an accurate math model for the specific machine and servos and you would send all three servos their commands at the exact same time. While your at it, you should also account for the transit time of each servo to ensure no interaction while the servos are moving. But now we are getting silly. With MCCPM, when each servo has a dedicated funtion, you should not have to worry about interaction. If you have any, it is the fault of the design. What I don't like about ECCPM is that if you have control interaction it is supposedly your fault because you set it up. I however think there may be other things to blame. |