Heat and 2.4GHz Receiver Issues/Shut Down
#1
Tech Adept
Thread Starter
Heat and 2.4GHz Receiver Issues/Shut Down
Dear All,
As you already know, the 2.4Ghz DSM radio signal started a real revolution a few years ago...
But this technology also has its weak point. I'm thinking about the OVERHEATING CUT. You know, when you're in the middle of your run and suddenly.... ...Paff!!! Your 2.4GHz receiver decided to shut down because of too much heat...
So, in this new thread, I would like you Guys to share your experience with overheating issues.
Could you tell us under which temperature, with which brand/module/receiver partnumber, etc.
Thanks a lot for your cooperation.
Cheers
Slide
As you already know, the 2.4Ghz DSM radio signal started a real revolution a few years ago...
But this technology also has its weak point. I'm thinking about the OVERHEATING CUT. You know, when you're in the middle of your run and suddenly.... ...Paff!!! Your 2.4GHz receiver decided to shut down because of too much heat...
So, in this new thread, I would like you Guys to share your experience with overheating issues.
Could you tell us under which temperature, with which brand/module/receiver partnumber, etc.
Thanks a lot for your cooperation.
Cheers
Slide
#2
just heard about this issue now...i hope not happened to my Fasst someday...
#4
Have heard 140 was a magic number for the FAST systems. at our 5th scale race some of the california guys had novak fans on their receiver boxes.... not sure if it helps, we also had a 10th scale car at the regionals this last weekend that had the same re-boot issues.
drove the guy nuts trying to find the problem.
TZR
drove the guy nuts trying to find the problem.
TZR
#5
I have seen this happen a couple times... It was with a guy running the Futaba Faast stuff... He was running it in his 1/8th Buggy and after about 20 minutes it would get so hot it would shut off. He even tried putting a fan on it and it still didn't work. It seems like it was only affected when running long run times, when used in his Touring Car it was fine...
#6
Tech Adept
Thread Starter
Thank you Guys for your quick replies !
Yes, the real symptom is more a "re-boot" than a real temp cut like would make a speedo. When a speepo has a temps cut, the steering are still operational and allows you to put the car in a safe zone.
But when the receiver suddenly shut down, you can not do anything at all.
After a few seconds, the receiver is ok again and work normally but the crash and the wasted time are enough to ruin your qualify race or main final.
I met the problem many times during 2 races under very hot conditions (38°C/100.4°F in the pit area and up to 60°C/140°F on the track).
I tried many other locations with fans on the chassis, as far as possible from any heat source. Even on the steering servo (1/10 Touring car), it happened as well.
Many other guys using Futaba 3PK 2.4GHz and R603FS receiver met exactly the same problems during these 2 races. It also drove us nuts !!
New Futaba 4PK and R604FS receiver owners didn't meet any problem, even when the receiver was directly flat taped on the chassis.
So, I would like to know if someone already met the same issue with different radio brand, Futaba with Spektrum Module or Sanwa DSSS or Sanwa with Sprektrum modules, etc.
Any info or tips are welcome !!
Slide
Yes, the real symptom is more a "re-boot" than a real temp cut like would make a speedo. When a speepo has a temps cut, the steering are still operational and allows you to put the car in a safe zone.
But when the receiver suddenly shut down, you can not do anything at all.
After a few seconds, the receiver is ok again and work normally but the crash and the wasted time are enough to ruin your qualify race or main final.
I met the problem many times during 2 races under very hot conditions (38°C/100.4°F in the pit area and up to 60°C/140°F on the track).
I tried many other locations with fans on the chassis, as far as possible from any heat source. Even on the steering servo (1/10 Touring car), it happened as well.
Many other guys using Futaba 3PK 2.4GHz and R603FS receiver met exactly the same problems during these 2 races. It also drove us nuts !!
New Futaba 4PK and R604FS receiver owners didn't meet any problem, even when the receiver was directly flat taped on the chassis.
So, I would like to know if someone already met the same issue with different radio brand, Futaba with Spektrum Module or Sanwa DSSS or Sanwa with Sprektrum modules, etc.
Any info or tips are welcome !!
Slide
#7
Tech Adept
Thread Starter
I guess it's only because of a tricky component that doesn't stand too much heat.
Slide
#8
from what I have seen it looks like the first batches of 3pk 2.4 recv were fine, but the recent batches have had issues. I have 3 recv from the first days and they are perfect in 140+ track temp for 30+mins in nitro. But I have seen many issues, at least 3, with ones purchased recently.
#11
Tech Elite
iTrader: (26)
I had the reboot issue on one race day early in the summer when it was quite hot (R603FF FASST). It happened several times that day. I sent the rx in, they replaced it, and I have had no further problems, even on very hot days here in socal. I run several of these receivers and only had a problem that one day.
#12
it was a 4pk transmitter that had problems this weekend, not sure if was the recivier that came with the 4pk or did he have one from his earlier stuff????
#13
Tech Adept
Thread Starter
I don't know if it's on FASST system only, but most of the time the complains came from 3PK FASST owners. Sanwa DSSS are safe so far but I don't know about Spektrum DX3 system or the module/receiver they build for tier brands.
the symptom is more like a "re-boot" than a real temp cut like would make a speedo. When a speepo has a temps cut, the steering is still operational and allows you to put the car in a safe zone.
But when the receiver suddenly re-boot once it's too hot, you can not do anything at all.
After a few seconds, the receiver is ok again and work normally but the crash and the wasted time are enough to ruin your qualify race or main final.
That's how I experienced the problem.
Slide
#14
Tech Adept
Thread Starter
Slide