
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
I agree with Peter here. Century shows in their instructions how to set it up with a 4 channel radio. That does not mean that that is the best or easiest way (we used to set them up that way for years before heliradios came on the scene). But believe me, you can do so MUCH easier and MUCH better with a radio that has the heli-software in them. NOTE: You didn't say what TX's you have, but there are a number of airplane radios on the market today that DO already have the heli-mixing software in them. Maybe one of yours does. Phil Noel Leisure-Tech Products www.leisuretech.ca "Beav" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > "Peter" <slick@ golden.net> wrote in message > news:[EMAIL PROTECTED] > > Depends on the heli you buy! > > Century has heli's that ca be built/flown with a standard 4 channel > airplane > > radio > > No Century heli is any different than any other heli in that regard, because > ALL heli's can be built to fly on 4 channels with a simple "Y" lead > connecting two servos (throttle and collective) to one channel (the throttle > channel). This isn't a "Century Feature", it's just that Century latched > onto the idea of SAYING it is. > > Now as to whether or not it's a good idea to use a "Y" lead and a plank > radio, that depends on the budget and aspirations of the man with the 4 > channel radio. A SERIOUS wannabe heli flyer will always look at a heli radio > because of the ability to trim EVERYTHING independently which isn't possible > with a 4 channel "Y" lead set up (well not from the Tx anyway) > > With good quality heli radio's at their current prices, I wouldn't even > consider using a 4 channel plank radio, in the same way that I won't use PPM > receivers when there are PCM receiver available. > > > -- > Beav > > > Please note my E-mail address is "beavis dot original at ntlworld dot com" > (with the obvious changes) > > Beavisland now lives at > www.beavisoriginal.co.uk > >
| <-- __Chronological__ --> | <-- __Thread__ --> |