... in suspicious circumstances :-(

I'd been playing music for a couple of hours, and it seemed to be
working fine. Then, *just* when I had to dish up dinner, and right
between two tracks, the display briefly went funny ("fizzy" feels like
an apt description) and then it went blank, and the audio stopped (or
didn't restart, since it was between tracks). Damn.

Once I'd dished up, I unplugged and replugged the power.  It came back
on, and I was able to carry on more or less where I think I'd left off.
Phew!

But about 30 minutes later, it conked out again, again right at the end
of a track.  I don't think the display "fizzed" this time, it just went
blank, but I wasn't looking straight at it, so can't be completely
sure.

It has refused to come back on since.  I've tried holding down the
power button on the remote, the Add button, the left button; and even
tried the contortions of doing each of these whilst plugging the power
in the back. Not a glimmer. Brightness doesn't help either.  Nor do new
batteries in the remote.

I'm still running the SS fishbone interface; this shows the player and
the playlist, but permanently says "CONNECTING..."; all other pages
(e.g. Settings, Network Health) act as if there's no player there. 
Hardly surprising, I suppose.

The power supply is fine (well, if 5.15V is fine). Each time I plug the
power back in there's a "clunk" through my speakers, which suggests to
me that at least some of the innards are getting power.  The SB3 is
still warm (no more so than usual).

Everything I've been able to find on here (via Google - can't get forum
search to work) suggests that if there's no "splash" screen when the
power is connected, then there's a real problem.

I'd recently rejigged my wireless network, switching to WPA from WEP,
and enabling SSID broadcast. After initial excitement, the SB3 was a
bit huffy about it; sometimes starting up when the server came on,
sometimes needing multiple on-button presses (Waking server...
connecting... <press on>); once - not the first time - I had to walk it
back through the network setup before it would connect. If anything, it
was looking like it was having more trouble connecting than before, but
not by much.

Also, I'd given up trying to deliver FLAC - it just wasn't reliable
enough - and had turned on bitrate limiting. Even 320kbps wasn't
guaranteed, so I dropped to 256; even *then* it would lose it on
occasion (maybe once per day), showing a "Rebuffering..." message that
I'd never seen before. (I'm not entirely convinced this was a network
problem; I had buffer level showing each time, and it went from full to
stuttering and failure instantly. I wonder whether it might've been the
start of something going wrong.)

I don't know if any of that is relevant.

I'm not sure what to do next. I'm in the UK, and from what I've seen
here, there really aren't any repair options.  What else can I try
before deciding it's a write-off? (Opening it up for a look will be a
last resort, for I'll have no idea what I'm looking for!)

I couldn't find any concise troubleshooting information on this
anywhere - least of all on the redirected-to-Logitech FAQ; so there's a
chance I've missed something else to try.

(I will try connecting it to my router by cable, just to rule out the
wireless network.)

I'm pretty much committed to having my music served over the wireless
network. (The idea of a server connected directly to the hifi is
appealing, but it would have to be absolutely quiet  and very small.) 
So if I can't get this SB3 working, I will probably end up buying
another one. But it had better work, and for longer than 1.3 years!

My (work) laptop died today as well. Bloody Friday 13th. :-(

-- Brian


-- 
Brian Ritchie
------------------------------------------------------------------------
Brian Ritchie's Profile: http://forums.slimdevices.com/member.php?userid=2319
View this thread: http://forums.slimdevices.com/showthread.php?t=34441

_______________________________________________
discuss mailing list
[EMAIL PROTECTED]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to