The latest stable builds listed in the last few pages of the original thread are the one to be using "at least for now".
Adding a 1000ma power supply as well as the two ceramic capacitors have made the signal drop issue unnoticeable "at least for me".
there is no real way "that I know of " to monitor the signal drop..unless you just happen to be at the terminal. I wold gladly post time up if I had a means to log it. Needs to be a win platform.
The dropout problem is (certainly) a software (driver) only problem, so just wait for a dd-wrt version with the new Broadcom driver, or install Tomato.
One can verify this problem is common to both oem and dd-wrt firmware. I am unable to commit on the tomato firmware but have only seen your feedback.
Many people on this board, have documented the signal dropping issue. Some have claimed it to drop a couple times an hour and some every hour or so.
I have also had some issues but not enough to scrap the router, however my efforts IMHO have been an improvement, at least for me.
I have included a s.s of just under 4 hr with no signal drop and will leave inSSIDR 2.0 running to validate a longer span of time.
IMHO the 1000ma power supply and the two ceramic caps in parallel serve to send really clean power to the router by reducing the noise and unwanted esr in the supply voltage.
Just under 4 hr[img][/img]
The S.S is for the 40mhz band in my area. By the way inSSIDR produces a huge log file! in short period of time.
thomas that screenshot only shows 5 minutes of snapshot. See if you can get a pre-2.0 version of inSSIDer, as it tends to cram in more time.. 2 hours or so if I recall correctly.
No it doesn't. It shows 12:12 to ~12:17 in the Time Graph. First Seen and Last Seen don't count for uptime since even if it drops and comes back the Last Seen will continue to update once it's back.
Your latest pic shows ~7:35 to 7:40. Again, get the old inSSIDer (before 2.0) if you can, since it crams about 2 hours or so into the Time Graph IIRC and would be better to evaluate the drops.
Also, please resize your pics so that they don't oversize the forum table.
No. The loopback fix is currently manual. As mentioned in the build thread, the loopback thread and this thread in the first post. Happy?
I'm not being a smartass. The reason for this perceived backlash is these 'new people' expecting to not to have to read anything, even when they have explicitly been directed to; there is perfectly good information EVERYWHERE that they are ignoring.
Last edited by on Wed Apr 06, 2011 1:54; edited 1 time in total
The reason I asked was if I should go back to 15962/3 which is what is mostly recommended and if that does not have any issues rather than stay with 16214. Dont want newer unknow/untested problems and would like to stick with the version that most are using.
Sorry I see what you are looking at - I am unsure of why the time graph does not reflect the same as the first and last.
Why is the first and last not sufficient for validation? Is this not the first time inSSID sees the signal and the last time that reference was updated?
Does anyone know if 16214 mega has loop back fix applied and any disconnection issues that anyone encountered and should I keep it at this level ?
I think there is a sticky regarding the manual loop back fix. Phuzion posted the first fix then Frater posted a different approach.
I am using std-nokaid-small - build 15962 which is stable for me. I did revert back to this build after having issues with more recent ones. If you check the original thread on the last few pages you can see Ducanhoe post with his signature of current version. He was pretty steady at only keeping stable builds and not the most recent.
