Major Glitch in a Futaba SS system!!
01-17-2008, 12:40 PM
#326
Join Date: Mar 2004
Location: Orange County,
CA
Posts: 5,312
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: Flying Geezer
The radios that can download programing, 12Z, 12FG, 14MZ, MAY be protected by a new program download. Since I have a 12FG I hope this will be done.
The radios that can download programing, 12Z, 12FG, 14MZ, MAY be protected by a new program download. Since I have a 12FG I hope this will be done.
01-17-2008, 03:18 PM
#330
My Feedback: (24)
Join Date: Jan 2004
Location: Peachtree City,
GA
Posts: 1,351
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
I have had the module for a week. Now we have to get them tested!! We also have to worry about turning the TX off too soon!! I'm sitting here retracing my steps to see if I may have cycled my TX on and off too fast!
Does this mean that not only do I have to get my module tested, but I also have to worry if the guy flying next to me had his tested?
Does this mean that not only do I have to get my module tested, but I also have to worry if the guy flying next to me had his tested?
01-17-2008, 03:31 PM
#331
RE: Major Glitch in a Futaba SS system!!
You would know if you reset your GUID as your reciever would no longer respond and you would have to re-bind it to the transmitter. This should never happen and may indicate that your tx code reverted to 00000000.
As long as your radio checks out then you do not have to worry about anyone elses radio as it takes two radios witht he same GUID to interfere with each other.
Stuart
As long as your radio checks out then you do not have to worry about anyone elses radio as it takes two radios witht he same GUID to interfere with each other.
Stuart
01-17-2008, 03:32 PM
#332
RE: Major Glitch in a Futaba SS system!!
If I understand correctly, there has to be (at least) two radios operating within range that have both had their GUIDs reset to have a problem.
01-17-2008, 03:36 PM
#333
My Feedback: (24)
Join Date: Jan 2004
Location: Peachtree City,
GA
Posts: 1,351
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
Is it a sure thing that if I turn my TX off before the system"boots up", that my GUID will be reset?
If it means anything, I have the 9C with a 7 channel module.
If it means anything, I have the 9C with a 7 channel module.
01-17-2008, 03:57 PM
#335
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: Hill202
I think I'm beginning to "Feel the Difference"
I think I'm beginning to "Feel the Difference"
01-17-2008, 04:23 PM
#336
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!!
There still seems to be some confusion with some people about what can interfere with what so I repeat the post below (modified slightly to match the official announcement) .
If you do NOT have a faulty TX (only 6 ex and 7C have any record at the moment) you are fine and will not be interfered with even if a faulty set switches on.
You can have a faulty set and fly perfectly safely, providing no one else has one.
Info says that the 12 and 14 units do NOT suffer from the 0000 GUID. This means you are safe, even if 1 or 2 (or more) faulty sets are present and turned on.
The 7 and 8 modules can theoretically suffer the same problem but due to how they work it is far less likely.
No recorded case has been found even in checked stock at Futaba and others ( Ia m told).
So at present the ONLY risk is if 2 faulty sets are at the same field and try to fly together, they will interfere with each other but NO OTHER FASST system.
As I indicated earlier, a quick check of these sets on the ground can confirm that you do not have TWO faulty sets present (or do have, as the case may be).
14,12, module users can continue as normal.
Futaba are recommending checking the 7 and 8 modules to be ultra cautious.
Hope that is clear
Paul
If you do NOT have a faulty TX (only 6 ex and 7C have any record at the moment) you are fine and will not be interfered with even if a faulty set switches on.
You can have a faulty set and fly perfectly safely, providing no one else has one.
Info says that the 12 and 14 units do NOT suffer from the 0000 GUID. This means you are safe, even if 1 or 2 (or more) faulty sets are present and turned on.
The 7 and 8 modules can theoretically suffer the same problem but due to how they work it is far less likely.
No recorded case has been found even in checked stock at Futaba and others ( Ia m told).
So at present the ONLY risk is if 2 faulty sets are at the same field and try to fly together, they will interfere with each other but NO OTHER FASST system.
As I indicated earlier, a quick check of these sets on the ground can confirm that you do not have TWO faulty sets present (or do have, as the case may be).
14,12, module users can continue as normal.
Futaba are recommending checking the 7 and 8 modules to be ultra cautious.
Hope that is clear
Paul
01-17-2008, 04:55 PM
#337
RE: Major Glitch in a Futaba SS system!!
If this is NOT the most convoluted thread I have ever seen!
The issue -I thot -- was a(some) radios changing from INTENDED codes ---accidentally
This could cause POSSIBLE interferrence with others rx
Is this correct?
Now the Futaba advisory cautions -fiddling with the ON/OFF switch.
OK- -but everybody does it at one time or the other . To think an advisory will change that is wistful thinking.
Is that switch advisory relevant in the original issue (loss of correct code.) ?
None of my business?
OK--- but I would sure like to know how they relate!
The issue -I thot -- was a(some) radios changing from INTENDED codes ---accidentally
This could cause POSSIBLE interferrence with others rx
Is this correct?
Now the Futaba advisory cautions -fiddling with the ON/OFF switch.
OK- -but everybody does it at one time or the other . To think an advisory will change that is wistful thinking.
Is that switch advisory relevant in the original issue (loss of correct code.) ?
None of my business?
OK--- but I would sure like to know how they relate!
01-17-2008, 04:57 PM
#338
Senior Member
My Feedback: (133)
Join Date: Dec 2001
Location: Bakersfield,
CA
Posts: 1,243
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
Paul, you are a voice of reason in a panicked crowd. A sparrow in a hurricane..............
I am as concerned about this as anyone - I sold off all my 72mhz stuff and bought a total of 10 new Futaba 2.4 rxs. Futaba has announced what the issue is, and how to avoid it. They have also made it clear that if your Tx STOPS working the rxs you already have linked to it - THERE IS A PROBLEM.
Suppose I buy a new 6 or 7 ch Futaba 2.4 TODAY at my LHS. If I do so, we will check it against a known 00000000 rx at the shop. Passes the test, 'cuz it won't work the test rx without binding them. I take it home, fly it for week/months/years, then grandson gets hold of it and plays with the power switch. Next time I go fly, my Tx won't work my rx(s). It'll have to go back - but even then, I COULD WALK THE LINE AND ADVISE OTHERS THAT I'LL BE FLYING WITH A DEFAULT SETUP, rebind my rx, and fly. If there are more than one of us in the same boat, we have to take turns - like we were both on ch37 or such. Basicly, 2.4 gives us 100,000,000 different channels, numbered 00000000 to 99999999. That's a lot of clothespins, but the only conflict that should ever occur would be on 00000000 - with two sets that had both been reset.
Folks - quit panicking. If in doubt, ship your Tx to the distributor. They'll check it, replace it if it's bad, and ship you a new one. If it suddenly quits working the rxs that it worked before, send it in. If you are a fidgiter who likes to turn their Tx on and off frequently for half-second intervals, seek help. Remember, it takes a short boot-up to cause it, which is also not good for your home PC. It's not going to happen while you are flying, and as long as you have passed the test, and not subsequently had to rebind your rxs, you are good to go.
I am as concerned about this as anyone - I sold off all my 72mhz stuff and bought a total of 10 new Futaba 2.4 rxs. Futaba has announced what the issue is, and how to avoid it. They have also made it clear that if your Tx STOPS working the rxs you already have linked to it - THERE IS A PROBLEM.
Suppose I buy a new 6 or 7 ch Futaba 2.4 TODAY at my LHS. If I do so, we will check it against a known 00000000 rx at the shop. Passes the test, 'cuz it won't work the test rx without binding them. I take it home, fly it for week/months/years, then grandson gets hold of it and plays with the power switch. Next time I go fly, my Tx won't work my rx(s). It'll have to go back - but even then, I COULD WALK THE LINE AND ADVISE OTHERS THAT I'LL BE FLYING WITH A DEFAULT SETUP, rebind my rx, and fly. If there are more than one of us in the same boat, we have to take turns - like we were both on ch37 or such. Basicly, 2.4 gives us 100,000,000 different channels, numbered 00000000 to 99999999. That's a lot of clothespins, but the only conflict that should ever occur would be on 00000000 - with two sets that had both been reset.
Folks - quit panicking. If in doubt, ship your Tx to the distributor. They'll check it, replace it if it's bad, and ship you a new one. If it suddenly quits working the rxs that it worked before, send it in. If you are a fidgiter who likes to turn their Tx on and off frequently for half-second intervals, seek help. Remember, it takes a short boot-up to cause it, which is also not good for your home PC. It's not going to happen while you are flying, and as long as you have passed the test, and not subsequently had to rebind your rxs, you are good to go.
01-17-2008, 05:12 PM
#339
Senior Member
Join Date: Jan 2007
Location: , GERMANY
Posts: 184
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
If you are a fidgiter who likes to turn their Tx on and off frequently for half-second intervals, seek help. Remember, it takes a short boot-up to cause it, which is also not good for your home PC.
My TX lost its GUID after I switched it on exactly the way I did hundreds of times before during the last 6 months.
01-17-2008, 05:26 PM
#341
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: dick Hanson
If this is NOT the most convoluted thread I have ever seen!
If this is NOT the most convoluted thread I have ever seen!
"Futaba gets it right the first time.
Futaba takes great pride in making sure that every new product performs flawlessly before it's offered to our customers. Others hesitate to invest so much effort in testing. Some may even consider their "first run" products a step in the process of working out bugs, using feedback from the earliest buyers. Futaba is different. When you choose a Futaba 2.4GHz FASST radio system or module/receiver set, you've selected a fully tested, well-engineered, totally reliable product – one that's absolutely ready to give demanding R/C hobbyists the performance they expect. Our hands-on experience with 2.4GHz technology stretches back 15 years, long before anyone considered its value in hobby applications. That's when engineers in Futaba's industrial R/C division – designers of radio-control tools for construction, civil engineering, and similar uses – began employing and perfecting their own 2.4GHz equipment. Those same engineers were brought in to share their knowledge as soon as we were comfortable that 2.4GHz technology had perfected for the unique demands of R/C hobby applications. No other radio manufacturer had such an instant supply of expertise."
I have a bunch of FASST stuff on backorder, but I'm wondering if it's time to cancel the order and "feel the difference" again.
While we keep hearing it's only a small number of units impacted by this, I seriously doubt we'll ever be told the truth.
1) The improved manual for the 14MZ (which I recall was promised) has never materialized and I doubt it ever will.
2) After the problems with the 5014 RX we were told there are no problems with the RX, but the eventually come out with a 5114 RX. We're told it's only a component change, but this RX mysteriously has a new feature (Mode A/B). Yeah, just a component change. Yeah, right.
3) They make the same statement with the 607/617 RXs (see item 2 above).
4) Not the FASST fiasco. It's actually quite funny. They ship the long delayed TM-14 FASST module and folks are getting them, but can't use them because they haven't shipped the software yet and it takes several days before the software is available.
So what's the long term solution to the power off problem? Does someone need to be concerned every time they turn off their TX now? Is that really progress? At least before you knew who could potentially shot you down. Now you have no clue. Yeah, so much for progress....
01-17-2008, 05:31 PM
#342
My Feedback: (24)
Join Date: Jan 2004
Location: Peachtree City,
GA
Posts: 1,351
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: shakes268
I know I did when I had to remove 8 8611As from a plane and send them back due to defective motors.
ORIGINAL: Hill202
I think I'm beginning to "Feel the Difference"
I think I'm beginning to "Feel the Difference"
01-17-2008, 05:36 PM
#343
RE: Major Glitch in a Futaba SS system!!
I fly at the Yuma Aeromodelers field where this originally was discovered. Our Pres. just sent out a link to a Futaba Tech. Support message ... Here it is if you haven's seen it already ... http://2.4gigahertz.com/techsupport/...m7-7c-6ex.html It is worth a read. My understanding is that Futaba is also replacing the plane that went down when the problem occurred.
Fly safe and be aware of what is going on around you.
Fly safe and be aware of what is going on around you.
01-17-2008, 05:45 PM
#344
Senior Member
My Feedback: (133)
Join Date: Dec 2001
Location: Bakersfield,
CA
Posts: 1,243
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: Ace Dude
Not the most convoluted, but it's close.... This whole thing is a complete mess. I can't help but laugh my you know what off when I read the Futaba propaganda on http://2.4gigahertz.com
"Futaba gets it right the first time.
Futaba takes great pride in making sure that every new product performs flawlessly before it's offered to our customers. Others hesitate to invest so much effort in testing. Some may even consider their "first run" products a step in the process of working out bugs, using feedback from the earliest buyers. Futaba is different. When you choose a Futaba 2.4GHz FASST radio system or module/receiver set, you've selected a fully tested, well-engineered, totally reliable product – one that's absolutely ready to give demanding R/C hobbyists the performance they expect. Our hands-on experience with 2.4GHz technology stretches back 15 years, long before anyone considered its value in hobby applications. That's when engineers in Futaba's industrial R/C division – designers of radio-control tools for construction, civil engineering, and similar uses – began employing and perfecting their own 2.4GHz equipment. Those same engineers were brought in to share their knowledge as soon as we were comfortable that 2.4GHz technology had perfected for the unique demands of R/C hobby applications. No other radio manufacturer had such an instant supply of expertise."
I have a bunch of FASST stuff on backorder, but I'm wondering if it's time to cancel the order and "feel the difference" again.
While we keep hearing it's only a small number of units impacted by this, I seriously doubt we'll ever be told the truth.
1) The improved manual for the 14MZ (which I recall was promised) has never materialized and I doubt it ever will.
2) After the problems with the 5014 RX we were told there are no problems with the RX, but the eventually come out with a 5114 RX. We're told it's only a component change, but this RX mysteriously has a new feature (Mode A/B). Yeah, just a component change. Yeah, right.
3) They make the same statement with the 607/617 RXs (see item 2 above).
4) Not the FASST fiasco. It's actually quite funny. They ship the long delayed TM-14 FASST module and folks are getting them, but can't use them because they haven't shipped the software yet and it takes several days before the software is available.
So what's the long term solution to the power off problem? Does someone need to be concerned every time they turn off their TX now? Is that really progress? At least before you knew who could potentially shot you down. Now you have no clue. Yeah, so much for progress....
ORIGINAL: dick Hanson
If this is NOT the most convoluted thread I have ever seen!
If this is NOT the most convoluted thread I have ever seen!
"Futaba gets it right the first time.
Futaba takes great pride in making sure that every new product performs flawlessly before it's offered to our customers. Others hesitate to invest so much effort in testing. Some may even consider their "first run" products a step in the process of working out bugs, using feedback from the earliest buyers. Futaba is different. When you choose a Futaba 2.4GHz FASST radio system or module/receiver set, you've selected a fully tested, well-engineered, totally reliable product – one that's absolutely ready to give demanding R/C hobbyists the performance they expect. Our hands-on experience with 2.4GHz technology stretches back 15 years, long before anyone considered its value in hobby applications. That's when engineers in Futaba's industrial R/C division – designers of radio-control tools for construction, civil engineering, and similar uses – began employing and perfecting their own 2.4GHz equipment. Those same engineers were brought in to share their knowledge as soon as we were comfortable that 2.4GHz technology had perfected for the unique demands of R/C hobby applications. No other radio manufacturer had such an instant supply of expertise."
I have a bunch of FASST stuff on backorder, but I'm wondering if it's time to cancel the order and "feel the difference" again.
While we keep hearing it's only a small number of units impacted by this, I seriously doubt we'll ever be told the truth.
1) The improved manual for the 14MZ (which I recall was promised) has never materialized and I doubt it ever will.
2) After the problems with the 5014 RX we were told there are no problems with the RX, but the eventually come out with a 5114 RX. We're told it's only a component change, but this RX mysteriously has a new feature (Mode A/B). Yeah, just a component change. Yeah, right.
3) They make the same statement with the 607/617 RXs (see item 2 above).
4) Not the FASST fiasco. It's actually quite funny. They ship the long delayed TM-14 FASST module and folks are getting them, but can't use them because they haven't shipped the software yet and it takes several days before the software is available.
So what's the long term solution to the power off problem? Does someone need to be concerned every time they turn off their TX now? Is that really progress? At least before you knew who could potentially shot you down. Now you have no clue. Yeah, so much for progress....
01-17-2008, 05:47 PM
#345
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: davebart
I fly at the Yuma Aeromodelers field where this originally was discovered. Our Pres. just sent out a link to a Futaba Tech. Support message ... Here it is if you haven's seen it already ... http://2.4gigahertz.com/techsupport/...m7-7c-6ex.html It is worth a read. My understanding is that Futaba is also replacing the plane that went down when the problem occurred.
Fly safe and be aware of what is going on around you.
I fly at the Yuma Aeromodelers field where this originally was discovered. Our Pres. just sent out a link to a Futaba Tech. Support message ... Here it is if you haven's seen it already ... http://2.4gigahertz.com/techsupport/...m7-7c-6ex.html It is worth a read. My understanding is that Futaba is also replacing the plane that went down when the problem occurred.
Fly safe and be aware of what is going on around you.
01-17-2008, 05:49 PM
#346
Junior Member
Join Date: Aug 2007
Location: liverpool, UNITED KINGDOM
Posts: 16
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
This seems to be getting out of hand....futaba must sort it out soon..seems everybody has different veiws as to what might and might not happen..and what if this and what if that...i am sure Futaba dont want this problem to rubbish their good name,so they are bound to want to sort it out asap.lets see.i switch my tx on and off all the time,if i reset the trims or the rates or the reverse servos,i swich the set off then straight back on,but it has always binded with the rx every time.
01-17-2008, 05:57 PM
#347
Senior Member
My Feedback: (133)
Join Date: Dec 2001
Location: Bakersfield,
CA
Posts: 1,243
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: bailey37
This seems to be getting out of hand....futaba must sort it out soon..seems everybody has different veiws as to what might and might not happen..and what if this and what if that...i am sure Futaba dont want this problem to rubbish their good name,so they are bound to want to sort it out asap.lets see.i switch my tx on and off all the time,if i reset the trims or the rates or the reverse servos,i swich the set off then straight back on,but it has always binded with the rx every time.
This seems to be getting out of hand....futaba must sort it out soon..seems everybody has different veiws as to what might and might not happen..and what if this and what if that...i am sure Futaba dont want this problem to rubbish their good name,so they are bound to want to sort it out asap.lets see.i switch my tx on and off all the time,if i reset the trims or the rates or the reverse servos,i swich the set off then straight back on,but it has always binded with the rx every time.
01-17-2008, 06:17 PM
#348
My Feedback: (6)
RE: Major Glitch in a Futaba SS system!!
"Not the most convoluted, but it's close.... This whole thing is a complete mess. I can't help but laugh my you know what off when I read the Futaba propaganda on http://2.4gigahertz.com
"Futaba gets it right the first time."
WOW! I am not even a Futaba guy and I can not imagine what some of you are thinking. I interpreted their ad campaign to mean they got the 2.4 GHz com thing right the first time due to their experienced 2.4 engineers. The GUID issue is not really closely related to the FASST 2.4 methodology, it is related to the fact that each piece of hardware needs a unique GUID. I am sure every other radio manufacturer has had in the past and will again in the future have small errors like this. They will fix it and implement some way to prevent it in the future and move on.
"Futaba gets it right the first time."
WOW! I am not even a Futaba guy and I can not imagine what some of you are thinking. I interpreted their ad campaign to mean they got the 2.4 GHz com thing right the first time due to their experienced 2.4 engineers. The GUID issue is not really closely related to the FASST 2.4 methodology, it is related to the fact that each piece of hardware needs a unique GUID. I am sure every other radio manufacturer has had in the past and will again in the future have small errors like this. They will fix it and implement some way to prevent it in the future and move on.
01-17-2008, 06:41 PM
#349
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: Teachu2
Answer to #4 - http://www.14mz.com/downloads/2008-0...4MZ_Ver120.zip on http://2.4gigahertz.com/downloads/downloads.html
Answer to #4 - http://www.14mz.com/downloads/2008-0...4MZ_Ver120.zip on http://2.4gigahertz.com/downloads/downloads.html
01-17-2008, 06:43 PM
#350
Banned
Join Date: Mar 2003
Location: Tokoroa, , NEW ZEALAND
Posts: 3,848
Likes: 0
Received 0 Likes
on
0 Posts
RE: Major Glitch in a Futaba SS system!!
ORIGINAL: dick Hanson
I really hope your info is not correct--(even tho I don't use Futaba)
Any design, which would permit operator inputs to setup a "failed to UNSAFE" condition is simply - unacceptable-- I won't bore you with the reasons or court cases which explain why this is the case- but it is.
I really hope your info is not correct--(even tho I don't use Futaba)
Any design, which would permit operator inputs to setup a "failed to UNSAFE" condition is simply - unacceptable-- I won't bore you with the reasons or court cases which explain why this is the case- but it is.
Looks as if they may have rushed this to the market without really doing a proper analysis or testing :-(