Heads-up: FrSky FASST Compatible receiver advisory

Your Reviewer

My Credentials
So who's doing this reviewing then?

Well I've been building and flying or driving radio controlled models for over 40 years and during that time I like to think I've built up a reasonable amount of knowledge.

I'm also a qualified electronics engineer who has worked in radio frequency, analog, digital systems and software for more than three decades. In fact I designed and built my first RC set back in 1969.

For the past nine years I've also been involved in the design and manufacture of some rather sophisticated engine technology and UAV flight control systems.

So, chances are I've been there, done that and have a huge pile of tee shirts to prove it.

Right now I'm heavily into 3D flying and enjoy all aspects of the RC hobby. I may be old but I don't feel it.

In the Pipeline

Here's just a little bit of what's to come on this site...

RC explained: Demystifying terms such as PCM, PPM dual conversion, single conversion, full-range etc., this feature will explain it all.

Cheap Chinese Engines: Just how good are those cheap Chinese glow and gas engines that sell for half the price of their "brand-name" equivalent? I put several to the test.

Build your own radio gear?: Back in the old days, building your own RC gear was not uncommon and now the arrival of 2.4GHz has made it practical again.

Heads-up: FrSky GUID caution

IT'S A LONG-SHOT BUT

Dated: 1 Dec 2010

Follow the forum discussion.

At a large fly-in last weekend it was discovered that two FrSky 2.4GHz systems were interfering with each other.

On closer examination, it appeared that both systems had the same GUID which resulted in one flier's transmitter affecting the other flier's receiver.

Fortunately, due to effective failsafe settings, no models were significantly damaged in the clash but it was a scary incident and I have contacted FrSky about the issue.

Until the exact cause and a remedy are established, FrSky users are advised to check that there is no conflict between their own FrSky system and any other FrSky system they may be flying along-side.

It is possible that this is a "one in a very large number" incident as FrSky have advised that their GUID is a 16-bit randomly-assigned number and because of this, there is always a (very small) chance of a clash.

FrSky also advise that the 2-way system (when used with a telemetry-enabled receiver) has no risk of a GUID clash.

I'll keep everyone informed as information comes to hand but this doesn't seem to be a "sky is falling" incident as there have been no other reports of such clashes within the ranks of FrSky users. At our club there are presently half a dozen FrSky users who regularly fly alongside each other without any issues.

RCModelReviews will be following this issue and posting any new advisories or information about this situation.

Based on experience to date I am confident that FrSky will not take long to provide answers and, if necessary, updates to their systems.