|
|
|
|
|
|
|
I had obviously incorrectly assumed that GUID codes would stop interfering signals on the same band. They obviously do not. I do not have an understanding enough of the way 2.4 works but if I can be shot down by some guy on a computer a block away(perhaps overly simplified but more than plausible) |
|
|
|
|
You did not assume incorrectly, but oversimplified.
NO RF signal is immune from flooding of a frequency band. That GUID code is supposed to be NEVER the same as another piece of hardware. Futaba messed up if they are the same in some cases. That is not to lead you to assume that a computer WiFi can shoot you down.
It has been said before, but maybe not understood that plenty of these problems WERE evident with 72mhz (and 35, etc.), but are NOW much more understood with the advent of 2.4ghz. I will enjoy my XPS systems where I fly, and MUCH enjoy the removal of checking with other 72mhz fliers for frequency use. In fact, some channels of 72mhz just do NOT work well where I fly, and it is more than 5 miles from ANYTHING that should be an emitter, except for one LORAN tower. Sure there are crashes, and a fair number that lay blame on any specific system are in fact UNEXPLAINED! In the 72mhz world, such crashes were left unexplained, and it was assumed that the crash was from getting "shot down."
PERCEPTION is the big thing that has changes. With 2.4ghz, the assumption in "unexplained" crashes has shifted from "shot down" to "new tech problem." Until a PROOF is provided, they are conjecture.