Krysta/Bax - would this make FASST safer?
01-18-2008, 12:55 AM
#1
Senior Member
Thread Starter
My Feedback: (133)
Join Date: Dec 2001
Location: Bakersfield,
CA
Posts: 1,243
Likes: 0
Received 0 Likes
on
0 Posts
Krysta/Bax - would this make FASST safer?
Would this simple change in the way most of us learned (Tx on first, rx off first) prevent shoot-downs due to GUID conflicts?
TURN THE PLANE ON FIRST, give it a few seconds, and if the servos start moving DON'T TURN ON THE TX! YOU ARE A ZGUID SYSTEM and there is another one ALREADY FLYING!!!!! This actually works for ANY GUID conflict - like if the factory accidentally duplicated a non-zero GUID. Just have to make sure your motor isn't armed on an electric.
TURN THE PLANE ON FIRST, give it a few seconds, and if the servos start moving DON'T TURN ON THE TX! YOU ARE A ZGUID SYSTEM and there is another one ALREADY FLYING!!!!! This actually works for ANY GUID conflict - like if the factory accidentally duplicated a non-zero GUID. Just have to make sure your motor isn't armed on an electric.
01-18-2008, 02:49 PM
#2
RE: Krysta/Bax - would this make FASST safer?
Trent,
Interesting suggestion. My understanding is that the "0" GUID (or whatever code it goes to when it gets lobotomized by the on/off problem) is just like any other GUID .. it's not like a "master key" that can affect other systems unless they also have the bad code .. and when this bad thing happens .. the systems always go to this code .. and then they step on one another. BTW, we are assuming this "bad code" is "0" but we really don't know.
Is that your assumption .. that the problem systems are like master keys? I am _really_ hoping this is NOT true, since it means that if you are sure you don't have the bad GUID, you won't shoot anyone else down, or get shot down by anyone else.
Dave
Interesting suggestion. My understanding is that the "0" GUID (or whatever code it goes to when it gets lobotomized by the on/off problem) is just like any other GUID .. it's not like a "master key" that can affect other systems unless they also have the bad code .. and when this bad thing happens .. the systems always go to this code .. and then they step on one another. BTW, we are assuming this "bad code" is "0" but we really don't know.
Is that your assumption .. that the problem systems are like master keys? I am _really_ hoping this is NOT true, since it means that if you are sure you don't have the bad GUID, you won't shoot anyone else down, or get shot down by anyone else.
Dave
01-21-2008, 05:26 PM
#3
My Feedback: (11)
RE: Krysta/Bax - would this make FASST safer?
That's a way to check that YOU are not affected. If you have a transmitter with the bad coding, then you could affect others. You'd have to test to make sure your transmitter didn't operate other people's transmitters.
