The wlanpoke 0.7 software revisions have added a simple network server,
plus improved statistics. The later versions have much improved recovery
times. A quick recovery method recovers the connection in about 18-19
seconds, but does not always work. The sure-fire full reset takes about
40-44 seconds, perhaps leading to a noticeable interruption in the
music, but which still keeps playing.
The software is designed for troubleshooting as well as mediation in
order to facilitate actually fixing the basic Wireless Connectivity
issue. Enhanced statistics have allowed for improved "tuning" of the
default detection settings. After some testing and analysis, the default
values seem optimum, but there are new options for setting these to
other values for experimentation.
You may wish to analyze or optimize your radios in your particular
environment. This has been made easier by an optional web service that
serves an informative web page of status information. By default, the
server is on port 8080, leaving port 80 alone for a possible future web
remote control. As of 0.7.2, the development branch (for later release)
also supports a quick report suitable for calling from a batch file to
fetch and save the statistics of all your radios within a few seconds.
This has produced output condensed into the following ~25 hour report
for 7 radios:
Code:
--------------------
number of failed pings: ----------------------- ----- quick, full
resets
dev/loc params index: 0 1 2 3 4 5 6 7 8 9 10
Ofc 2S Ping 2s3q6f Fails[9]: 33429 225 1 0 0 0 0 0 0 0 0
bsmt M Ping 2s3q6f Fails[9]: 33381 58 0 0 1 69 2 0 75 3 0
LR 1F Ping 2s3q6f Fails[9]: 32106 178 3 0 4 54 2 0 76 16 0
Kit 1E Ping 2s3q6f Fails[9]: 33261 168 1 1 3 67 1 0 77 5 0
MBR 2E Ping 2s3q6f Fails[9]: 28918 748 58 3 1 36 2 0 53 11 0 (22 hours)
Ofc 2N Ping 2s3q6f Fails[9]: 34452 130 1 1 0 21 0 0 32 10 0
bsmt W Ping 2s3q6f Fails[9]: 7487 14 0 0 0 0 0 0 0 0 0 (<6 hrs)
---- activity ------- ok q f q f
--------------------
A quick reset was performed after 3 failed pings, and a full reset after
6. Array indexes [0 - 7] display the number of failed pings counted
before the system had a successful ping. Array indexes [8] and [9] count
the number of times the quick and full reset actions were performed. The
full reset sets the failed ping counter to 1 (to keep trying), so index
[7] is zero. Index [10] is unused.
By far, the pings succeed with zero intervening failures, so the [0]
numbers are large. The radios had some 1, and just a few 2 ping
failures, which likely would not be noticed. Three ping failures before
recovery were not seen in earlier testing, so the radios performed a
quick reset [8] at the 3rd ping failure. These succeeded most of the
time, with recoveries shown in indexes [3..6]. These lower outages might
not cause interruption. Full recoveries were required in 3/75 to 10/32
of the cases. The reason the quick reset works or doesn't is unknown at
this time. The full recovery has worked reliably for the last 6 months.
The software is located on github. https://github.com/PomDev2/wlanpoke.
This site facilitates all kinds of collaboration. The software is
available in various versions and 'branches.' One can choose to download
a "Release" version (e.g., the latest), or download from one of the
branches. There are currently two branches: "main" and "development."
The development branch has the lastest efforts, but it may not be
complete or in sync with the documentation. If you can't use github,
leave a request to post the latest software here.
------------------------------------------------------------------------
POMdev's Profile: http://forums.slimdevices.com/member.php?userid=70558
View this thread: http://forums.slimdevices.com/showthread.php?t=111663
_______________________________________________
Radio mailing list
Radio@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/radio
