I'm experiencing a lot of wireless network problems with the Duet
Controller.
The controller drops the network connection, won't reconnect and
becomes unresponsive for all menu-items that require data from the
network.
The icon at the bottom of the screen is mostly white with all three
bars lit - even with network problems going on - but it often turns
blue aswell ("A
blue icon indicates your Squeezebox Controller is connected to the
network, but cannot find its music source.").
Pinging the receiver (with "-t" option for continuous pinging) always
shows perfect results. Pinging the controller shows a *lot* of
timeouts.
I've tried two different wireless routers and currently the router is
placed in the line-of-sight of both the receiver and controller.
However what I've noticed today is that if I turn off "Wireless Power
Save" (WPS) under "Settings / Advanced / Factory Test /Power
management" is that
ping results improve tremendously and - with what little time I've had
to test this - the controller all of a sudden works perfectly!
Here is a typical ping result with WPS turned on (default setting):
Reply from 192.168.0.33: bytes=32 time=7ms TTL=64
Reply from 192.168.0.33: bytes=32 time=6ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.33: bytes=32 time=246ms TTL=64
Request timed out.
Typical ping result after turning WPS off:
Reply from 192.168.0.33: bytes=32 time=7ms TTL=64
Reply from 192.168.0.33: bytes=32 time=7ms TTL=64
Reply from 192.168.0.33: bytes=32 time=7ms TTL=64
Reply from 192.168.0.33: bytes=32 time=8ms TTL=64
Reply from 192.168.0.33: bytes=32 time=3ms TTL=64
Reply from 192.168.0.33: bytes=32 time=7ms TTL=64
Reply from 192.168.0.33: bytes=32 time=7ms TTL=64
Reply from 192.168.0.33: bytes=32 time=7ms TTL=64
I would have expected a power save feature to go into effect after some
idle time (eg. during "Screen Dimming" or "Screensaver") but this
indicates that
at least /this/ setting goes into effect right away - even while the
controller is being used.
Another observation: if WPS is on (ie. bad pings) putting the
controller into the cradle will instantly result into good pings. Seems
logical though
since the controller now has full current.
I've tried a *lot* of things to remedy the network problems, so my
current setup uses one of the latest nightly builds:
* SqueezeCenter-7.1-19366 installed on Vista
* SqueezeNetwork as primary music source
* Controller: 7.1 r2291 [EMAIL PROTECTED] #50 Sat Apr 19 02:01:27 PD 2008
* Receiver: Firmware 23
* All-Wireless Network Configuration (although at one point I suspected
a "Bridged Network Configuration" gone wrong, ie. Controller
==wireless==>
Receiver, Receiver ==wireless==> Router, if that's at all possible but
I could never figure out how / where I could see the actual
configuration used)
If this keeps up for the next few days, I'll try to go back to the
official version.
While I've been writing this I've had continuous ping running and it
looks good compared to before: typical ping is 2-8 ms, a single 15-20
ms ping every
20 or so pings and a single timeout every 160 or so pings.
Also I've been using the controller and whereas before I would have
experienced network issues it's been working perfectly.
The only thing I've noticed is that the battery indicator is now at
50%.
I can live with having to place the controller in the cradle when not
in use (as a work-around) if this is a fixable issue.
If you're experiencing network problems with your Duet Controller try
to disable the WPS aswell and let me know how it works out for you.
/John
--
zzap
------------------------------------------------------------------------
zzap's Profile: http://forums.slimdevices.com/member.php?userid=17307
View this thread: http://forums.slimdevices.com/showthread.php?t=47190
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
