Major Glitch in a Futaba SS system!!
#127
My Feedback: (21)
Join Date: Aug 2005
Location: EdmontonAB, CANADA
Posts: 571
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
For what it's worth I just called Hobbico and they simply don't believe this is a problem. They did say they are waiting for the transmitters to come back... their advice was not to worry in the mean time.
#129
My Feedback: (20)
Join Date: Apr 2003
Location: Buena Park,
CA
Posts: 365
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
I'll bet they are waiting for the transmitters to come back! That is like the DA sending all the evidence to to the defendant to examine. I sent an OS engine in when the chrome started flaking off the cylinder and the engine froze. They said they could not find anything wrong with the engine but sent me a new engine just to be sure. I had taken the engine apart and saw the flaking.[8D]
Bob
Bob
#130
My Feedback: (12)
Join Date: Dec 2002
Location: Medford,
OR
Posts: 39
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
I bought a new Futaba FAAS system t6ex from Tower October 11, 2007. The radio arrived, worked for a short time then frizzled. The green/red light on the back would never go green, it always alternated. I sent it back on November 12th, 2007 and was EVENTUALLY told that it checked out on the bench. I pissed and moaned and pitched a fit and finally ended up with a new , working, radio. I am not convinced of the reliability of these things , yet, either. I wish all of you good luck.
Rick
Rick
#131
Member
Join Date: Dec 2002
Location: CO
Posts: 55
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: d_wheel
The simplest way is to turn your receiver on while someone else is flying. If your control surfaces follow the other transmitter, you both have a problem. Quoted below is the best solution as far as I can see:
"Get all 2.4 FASST systems in your club together and carry out the following test.
Switch on your TX and all other RX’s, see if any other system will respond, if not then repeat with all other TX’s one at a time. Remember, only 1 TX at a time.
What this will do will show that all the TX’s in your club are not interfering with each others rx, therefore you do not have more than ONE faulty TX present. However if a new TX or module turns up then you MUST repeat the test, because one of your TX’s may have been faulty but it would not show unless 2 or more are present. (Bit of a pain but you can at least continue with safety until Futaba give a heads up on this and resolve/replace the faulty TX’s."
Later;
D.W.
The simplest way is to turn your receiver on while someone else is flying. If your control surfaces follow the other transmitter, you both have a problem. Quoted below is the best solution as far as I can see:
"Get all 2.4 FASST systems in your club together and carry out the following test.
Switch on your TX and all other RX’s, see if any other system will respond, if not then repeat with all other TX’s one at a time. Remember, only 1 TX at a time.
What this will do will show that all the TX’s in your club are not interfering with each others rx, therefore you do not have more than ONE faulty TX present. However if a new TX or module turns up then you MUST repeat the test, because one of your TX’s may have been faulty but it would not show unless 2 or more are present. (Bit of a pain but you can at least continue with safety until Futaba give a heads up on this and resolve/replace the faulty TX’s."
Later;
D.W.
and even if you've tested them all, you could still have one ZGUID Tx in the group (and there's no way to know which one). A new guy shows up, tests his Tx against
5 out of 6 of the FASST systems and is ok. 6th guy shows up, thinks he's ok, because he's already tested against everyone else, switches on, new guy falls
out of the sky.
If you had a *known* ZGUID bound Rx, then everyone need only check against that single receiver, and if they can't control it, then they
know that they do not have a ZGUID Tx. Doesn't get much simpler than that. And even if Futaba doesn't supply people with these Rxs
for testing, as soon as another ZGUID Tx is identified (such as those at the start of this thread) those could be used to
bind a bunch of Rxs to send to people (you send em your Rx, they bind it, and send it back, and as long as you don't rebind it, you can
use it for testing for ZGUID Txs at your club for as long as you want ).
ian
#132
Senior Member
Join Date: Jan 2003
Location: Deep in the Heart Of, TX,
Posts: 602
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: Daemon
If you had a *known* ZGUID bound Rx, then everyone need only check against that single receiver, and if they can't control it, then they
know that they do not have a ZGUID Tx. Doesn't get much simpler than that. And even if Futaba doesn't supply people with these Rxs
for testing, as soon as another ZGUID Tx is identified (such as those at the start of this thread) those could be used to
bind a bunch of Rxs to send to people (you send em your Rx, they bind it, and send it back, and as long as you don't rebind it, you can
use it for testing for ZGUID Txs at your club for as long as you want ).
ian
If you had a *known* ZGUID bound Rx, then everyone need only check against that single receiver, and if they can't control it, then they
know that they do not have a ZGUID Tx. Doesn't get much simpler than that. And even if Futaba doesn't supply people with these Rxs
for testing, as soon as another ZGUID Tx is identified (such as those at the start of this thread) those could be used to
bind a bunch of Rxs to send to people (you send em your Rx, they bind it, and send it back, and as long as you don't rebind it, you can
use it for testing for ZGUID Txs at your club for as long as you want ).
ian
Personally, it won't slow me down all that much. I'll just be a little extra careful (check as many transmitters as possible and watch new ones like a hawk) and go ahead and have fun. After all, only 2 cases worldwide that we know of and neither has been properly diagnosed yet. When we start seeing more cases I will become more concerned.
Later;
D.W.
#133
Join Date: Oct 2003
Location: Dunstable, UNITED KINGDOM
Posts: 3,601
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
An update.
I have received other info today, it is unofficial but from a good source.
Futaba are sure they know how this has happened and are putting together an announcement for release shortly.
My info tells me is that the 12 and 14 channel units are not vulnerable to this problem.
What I mean is that they will not suffer from,
1) 000000 coding in themselves
2) Because of this they are not vulnerable to anyone’s set that is faulty
So that is good news.
(This must however still be confirmed by Futaba)
The 8 channel modules are not out in the UK , but the error will be checked for and corrected should it exist in them. (No evidence at this time that it does)
The feeling is it will not.
The 2 systems that are definitely vulnerable are the 6 and 7 channel systems.
I have no confirmation yet as to the situation on the 7 channel modules.
I will keep you informed as and when I get any further reliable data.
Regards
Paul
PS as for Hobbico not believing it is a problem, well they are either in denial, or not well informed.
I have received other info today, it is unofficial but from a good source.
Futaba are sure they know how this has happened and are putting together an announcement for release shortly.
My info tells me is that the 12 and 14 channel units are not vulnerable to this problem.
What I mean is that they will not suffer from,
1) 000000 coding in themselves
2) Because of this they are not vulnerable to anyone’s set that is faulty
So that is good news.
(This must however still be confirmed by Futaba)
The 8 channel modules are not out in the UK , but the error will be checked for and corrected should it exist in them. (No evidence at this time that it does)
The feeling is it will not.
The 2 systems that are definitely vulnerable are the 6 and 7 channel systems.
I have no confirmation yet as to the situation on the 7 channel modules.
I will keep you informed as and when I get any further reliable data.
Regards
Paul
PS as for Hobbico not believing it is a problem, well they are either in denial, or not well informed.
#134
Join Date: Oct 2003
Location: Dunstable, UNITED KINGDOM
Posts: 3,601
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: Daemon
The problem with that is that it's not "simple" in any way shape or form. You still have to check every single Tx/Rx against every other Tx/Rx in the whole club
and even if you've tested them all, you could still have one ZGUID Tx in the group (and there's no way to know which one). A new guy shows up, tests his Tx against
5 out of 6 of the FASST systems and is ok. 6th guy shows up, thinks he's ok, because he's already tested against everyone else, switches on, new guy falls
out of the sky.
If you had a *known* ZGUID bound Rx, then everyone need only check against that single receiver, and if they can't control it, then they
know that they do not have a ZGUID Tx. Doesn't get much simpler than that. And even if Futaba doesn't supply people with these Rxs
for testing, as soon as another ZGUID Tx is identified (such as those at the start of this thread) those could be used to
bind a bunch of Rxs to send to people (you send em your Rx, they bind it, and send it back, and as long as you don't rebind it, you can
use it for testing for ZGUID Txs at your club for as long as you want ).
ian
ORIGINAL: d_wheel
The simplest way is to turn your receiver on while someone else is flying. If your control surfaces follow the other transmitter, you both have a problem. Quoted below is the best solution as far as I can see:
"Get all 2.4 FASST systems in your club together and carry out the following test.
Switch on your TX and all other RX’s, see if any other system will respond, if not then repeat with all other TX’s one at a time. Remember, only 1 TX at a time.
What this will do will show that all the TX’s in your club are not interfering with each others rx, therefore you do not have more than ONE faulty TX present. However if a new TX or module turns up then you MUST repeat the test, because one of your TX’s may have been faulty but it would not show unless 2 or more are present. (Bit of a pain but you can at least continue with safety until Futaba give a heads up on this and resolve/replace the faulty TX’s."
Later;
D.W.
The simplest way is to turn your receiver on while someone else is flying. If your control surfaces follow the other transmitter, you both have a problem. Quoted below is the best solution as far as I can see:
"Get all 2.4 FASST systems in your club together and carry out the following test.
Switch on your TX and all other RX’s, see if any other system will respond, if not then repeat with all other TX’s one at a time. Remember, only 1 TX at a time.
What this will do will show that all the TX’s in your club are not interfering with each others rx, therefore you do not have more than ONE faulty TX present. However if a new TX or module turns up then you MUST repeat the test, because one of your TX’s may have been faulty but it would not show unless 2 or more are present. (Bit of a pain but you can at least continue with safety until Futaba give a heads up on this and resolve/replace the faulty TX’s."
Later;
D.W.
and even if you've tested them all, you could still have one ZGUID Tx in the group (and there's no way to know which one). A new guy shows up, tests his Tx against
5 out of 6 of the FASST systems and is ok. 6th guy shows up, thinks he's ok, because he's already tested against everyone else, switches on, new guy falls
out of the sky.
If you had a *known* ZGUID bound Rx, then everyone need only check against that single receiver, and if they can't control it, then they
know that they do not have a ZGUID Tx. Doesn't get much simpler than that. And even if Futaba doesn't supply people with these Rxs
for testing, as soon as another ZGUID Tx is identified (such as those at the start of this thread) those could be used to
bind a bunch of Rxs to send to people (you send em your Rx, they bind it, and send it back, and as long as you don't rebind it, you can
use it for testing for ZGUID Txs at your club for as long as you want ).
ian
Paul
#135
Senior Member
Join Date: Oct 2002
Location: St.Paul,
MN
Posts: 119
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
Thanks alot for the updates Paul. I just got my 12FG with the TM-14 when these threads popped up a bit ago. Been following fairly closely and this is a slight sigh of relief and it will be even more of one once Futaba deciedes to do an announcement.
Harry
Harry
#136
Senior Member
My Feedback: (1)
Join Date: Sep 2004
Location: Seattle,
WA
Posts: 170
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
Wow, what a mess. This is a serious error and oversight from Futaba. It does not inspire confidence in any of their SS products or software updates. If something as significant as identical GUID codes passed QA then that really says something.
Easy for them to say!
nick
For what it's worth I just called Hobbico and they simply don't believe this is a problem. They did say they are waiting for the transmitters to come back... their advice was not to worry in the mean time.
Easy for them to say!
nick
#138
Join Date: Sep 2002
Location: Dearborn, MI,
Posts: 362
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
I just took delivery of the 7c fasst after MUCH deliberation in deciding between it and the dx7. I'm sick to my stomach over this. Even if mine isn't affected, this whole thing leaves a bad taste in my mouth. I'd like to know soon from Futaba, as I still have time to return the 7c and purchase the dx7. Oh the fickle finger of fate!
What to do but wait?
What to do but wait?
#139
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: canavanbob
I'll bet they are waiting for the transmitters to come back! That is like the DA sending all the evidence to to the defendant to examine. I sent an OS engine in when the chrome started flaking off the cylinder and the engine froze. They said they could not find anything wrong with the engine but sent me a new engine just to be sure. I had taken the engine apart and saw the flaking.[8D]
Bob
I'll bet they are waiting for the transmitters to come back! That is like the DA sending all the evidence to to the defendant to examine. I sent an OS engine in when the chrome started flaking off the cylinder and the engine froze. They said they could not find anything wrong with the engine but sent me a new engine just to be sure. I had taken the engine apart and saw the flaking.[8D]
Bob
#141
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: yakman
Interesting that there has been no word either way from futaba
Interesting that there has been no word either way from futaba
http://www.rcuniverse.com/forum/fb.asp?m=6881495
#142
My Feedback: (14)
Join Date: Apr 2003
Location: Bowling Green,
KY
Posts: 1,326
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
There has been a response from Futaba. Krysta posted from Hobby Services has post, either on this thread or the one in the Futaba support forum.
She said they had asked the affected modelers to send their TX's in to be examined. The owners of the TX's are the one holding things up due to paranoia that they will be lied to.
I don't care if the Spectrum/JR children gloat. After all they've been through, they really need this.
She said they had asked the affected modelers to send their TX's in to be examined. The owners of the TX's are the one holding things up due to paranoia that they will be lied to.
I don't care if the Spectrum/JR children gloat. After all they've been through, they really need this.
#143
Senior Member
Join Date: Jan 2003
Location: Brisbane, AUSTRALIA
Posts: 159
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
We have asked the users in North America to send their systems to us so that we can verify the problem.
Considering the problem and its consequences I believe Futaba should be more pro-active.
As I have been flying non-asian radios for the last seven years I am on neither side od the fence. This just my opinion.
#144
Senior Member
Join Date: Jan 2005
Location: Fairview,
TN
Posts: 1,320
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: yakman
Considering the problem and its consequences I believe Futaba should be more pro-active.
As I have been flying non-asian radios for the last seven years I am on neither side od the fence. This just my opinion.
We have asked the users in North America to send their systems to us so that we can verify the problem.
Considering the problem and its consequences I believe Futaba should be more pro-active.
As I have been flying non-asian radios for the last seven years I am on neither side od the fence. This just my opinion.
They also stated they tested the same situations and couldn't duplicate the problem. As a programmer, its nearly impossible to fix a problem in which you don't have enough information and can't duplicate the problem. For them to correctly duplicate it, they need the equipment in question.
Maybe the black helicopters should descend on these folks home with warrants to turn over their hobby equipment.
#145
RE: Major Glitch in a Futaba SS system!!
Wow, Futaba loyalists ARE the same as JR(Spektrum)...reminds me of Democrats vs Republicans....politics as usual...
Lets wait to see how Futaba addresses the speculation, issue, problem...
Lets wait to see how Futaba addresses the speculation, issue, problem...
#146
Join Date: Oct 2003
Location: Dunstable, UNITED KINGDOM
Posts: 3,601
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
Futaba USA may not have the faulty units from you guys yet, but Futaba Japan DO have the faulty UK units and HAVE seen the fault.
Ripmax UK have found faulty stock (as indicated in previous posts), what % is not known at this time.
An announcement and solution is imminent whether Futaba USA says so or not!
Paul
Ripmax UK have found faulty stock (as indicated in previous posts), what % is not known at this time.
An announcement and solution is imminent whether Futaba USA says so or not!
Paul
#147
Member
My Feedback: (4)
Join Date: Mar 2005
Location: Dalton,
GA
Posts: 90
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
I was hopeful to get some good information here. All I read is endless rambling and speculation by the uninformed. Kinda like the Rush Limbaugh show of RC.
#148
Senior Member
Join Date: Jan 2005
Location: Fairview,
TN
Posts: 1,320
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: ShineyObject
I was hopeful to get some good information here. All I read is endless rambling and speculation by the uninformed. Kinda like the Rush Limbaugh show of RC.
I was hopeful to get some good information here. All I read is endless rambling and speculation by the uninformed. Kinda like the Rush Limbaugh show of RC.
At least I'm home with the flu and stocked up on my popcorn.
#149
Join Date: Jan 2008
Location: Manchesterlancashire, UNITED KINGDOM
Posts: 77
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
I can undersannd that two tx's would control the same rx if the Guid codes are the same but why should a the second tx to be switched on cause a model to crash as the system in addition to the guid code is supposed to check on switch on for an unused channel & only transmit on an unused channel so even if the Guid codes were the same two tx should not interfere with each other & each ?
#150
Senior Member
Join Date: Jan 2005
Location: Fairview,
TN
Posts: 1,320
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
My guess is that with channel hopping at 2ms on each radio, they are bound to step all over each other. They get crossed up. Its not like one is controlling the other - its more of interference. Yea, there's control in 2 ms time frames but not sure which transmitter has control.