techuser: I've stayed on 15693 while waiting for the new Broadcom drivers in svn16540+ (no public build yet) since they could fix the droppage issue. 15693 works quite well for me and is pre-loopback issue as well. As thomas just mentioned, 15962 is also fine if you apply the manual loopback fix. After that the build sizes have gone weird (some too large to flash, etc.) so I'd advise holding off if you're looking for something stable.
thomas007: Last Seen will update the next time it sees it, drop in between or not, so unfortunately is not a good way to evaluate uptime. The Time Graph is useful in seeing the drops but 2.0+ limits the graph to the last 5 minutes; see if you can hunt down 1.x as it was longer.
techuser: I've stayed on 15693 while waiting for the new Broadcom drivers in svn16540+ (no public build yet) since they could fix the droppage issue. 15693 works quite well for me and is pre-loopback issue as well. As thomas just mentioned, 15962 is also fine if you apply the manual loopback fix. After that the build sizes have gone weird (some too large to flash, etc.) so I'd advise holding off if you're looking for something stable.
thomas007: Last Seen will update the next time it sees it, drop in between or not, so unfortunately is not a good way to evaluate uptime. The Time Graph is useful in seeing the drops but 2.0+ limits the graph to the last 5 minutes; see if you can hunt down 1.x as it was longer.
Alright found ver 1 - took snapshot then uninstalled ver2 - Ver1 is now running so I will attempt to produce a accurate validation for cfe51.
Ver2 is much nicer also has useful filters, maybe they will extend the time stamp in the next upd.
I will not string this along any more but these efforts have produced results for my wrt160n v3 cfe51.
IMO the signal drop acts like random hardware issues similar to random errors when overclocking with insufficient cooling. There may be firmware / driver issues here but the oem firm also has signal issues. Maybe it is a combination of both but in my case it seems to be resolved as I have been using with out any noticeable drops occurring.
It was stated in the recapping thread that linksys has the tendency to under-power there routers. I agree and by replacing the .5amp (500ma) power adapter with a 1amp (1000ma) power adapter has helped.
Adding additional cooling has been also been beneficial because the cfe51 really gets hot IMO. Could be part of the problem.?
The capacitors chosen for the design are not optimal choice but acquiring quality caps with the right specs resorts to mail order. Mouser electronics or Digicom both have online and down-loadable catalogs.
Adding two ceramic filter caps really help to clean up the power supply before reaching the cfe51 on-board filtering circuit. Note: the additional filtering caps have really help to bring the temp down to a noticeable difference.
A few link of interest regarding capacitors, filtering ect.
Sorry but I do not have the patience to sit here for hours on end and copy the 30min signal timer graph from inSSIDer. However I will paste an hour + worth of graph but I missed the last one by a few minutes.[img][/img][img][/img][img][/img]
heatsink.jpg
Description:
Filesize:
344.62 KB
Viewed:
17681 Time(s)
ventilation.jpg
Description:
Filesize:
215.5 KB
Viewed:
17681 Time(s)
1000ma.jpg
Description:
Filesize:
27.74 KB
Viewed:
17681 Time(s)
Last edited by thomas007 on Wed Apr 06, 2011 18:29; edited 1 time in total
inSSIDER v1 results - sorry you have to have lots of time and patience to not miss the 30 min increments.
[img][/img][img][img][/img]
I will post the last but I missed it by a few minutes so only 1hr 16min can be validated. I would be nice to be able to post several hours but there is no way I am going to sit here for that...
But then one could ask why the issue is common on oem as well. The continual randomness of the occurrence causes me to doubt it is all firmware related. But I am no expert and there are many here who have a solid understanding / education in these issue.
I do not use Tomato firmware and have no intention to change...
The information I posted is only to share but in my case it has produced resolution to my signal dropping. The only prize I received was my signal is reliable.
\Just curious,how are you able to monitor and log the signal connection, for such an extended period of time.
Cheers
Note: there is also a penny on the Broadcom chip as well. Quality thermal compound was used and the hot glue is just there so the penny will not fall off when tilting the router.
Last edited by thomas007 on Wed Apr 06, 2011 18:51; edited 1 time in total
Joined: 09 Apr 2011 Posts: 2 Location: Chiang Mai, Thailand
Posted: Sat Apr 09, 2011 10:47 Post subject: Tomato until . . .
First post and want to say thanks to everyone whose submitted a question and to those who tirelessly provide next steps and solutions. Both have assisted many, including me.
After 100+ pages I'm inclined to suspect software at the radio interface. That backtracking to earlier versions of CFE bins hasn't seemingly helped I'm considering supporting evidence.
My CSE51 drops 'N-only' connections like it's on crack.
I've tried 3 versions of DD-WRT, all recommended versions without taming the beast.
Tomato took 3 min to install and . . . Voila, no more drops.
Its my choice until DD-WRT is viable again.
My configuration is a 160NL with 160N as repeater-bridge. The NL runs Linksys v1.02 firmware without issue.
Kurt _________________ "The perfect is the enemy of the good."
There are definitely features missing in Tomato from the "generic" DD-WRT, nevermind the BS versions . . . but until a new version of DD-WRT is viable . . . TOMATO ! _________________ "The perfect is the enemy of the good."
Last edited by Genghis9021 on Sun Apr 10, 2011 1:54; edited 2 times in total
Posted: Mon Apr 11, 2011 3:38 Post subject: just installe tomato
i have had dd-wrt on my wrt160n v3 for more than a year now, when i first bought it. tried many builds, most recently 16424. i just installed tomato per the instructions, though i ended up not needing the encoded password i had retrieved through telnet. it worked straight away and has fixed my signal dropping, i now have mixed mode wireless, and qos that works. my thoughput in g and n connections has improved. i will try the new ddwrt when the new broadcom build has been incorporated but until then i'm sticking with tomato
Instead of everyone jumping ship to Tomato and filling up the DD-WRT forum with Tomato questions, has anyone tried one of the new builds out yet? ..They now have the newer radio drivers (like Tomato) and may also fix the drop problem (let us know!). I'd test but my unit is unavailable at a family member's house.
At Osmosis suggestion I have loaded DD-WRT v24-sp2 (04/11/11) vpn-small 16773M. I, too, have been having the wifi dropout on a CSE51 s/n. I'll keep an eye on it and report the results.
Edit: @2250 tonight it dropped out for about 1-2 minutes. The wifi light on the router was on during the dropout as were the WAN connect and power lights.
