'Dead 'Classic' - no connectivity to Squeezecenter / no display etc

[Deepbluesky]

Hi Guys,
I'm new to the Squeezebox world and decided to decided to take the jump with a SB3 'Classic' I bought the unit second hand, knowing the unit had a display issue but was told that it worked OK just no picture.

The unit is working I can see power to the Optical output the unit feels warm.

The problem is I cannot get it working on my network I guess this is a combination of not being able to set-up the unit due to no display and the Squeezecenter asking for a pin from the 'Classic' that I cannot supply as I cannot see it.

I have read through the user forums and can see the display issue is not uncommon. I have read this can be down to:

1. The power supplies sold in NZ / Australia having issues mine is 2A which I think is OK (I also bought an after market 5V2A without any luck)
2. Historical Firmware update - read that there was a release that blanked the screen.
3. Possible internal component failure.

But there is nothing concrete on the exact reason.

I'm thinking it maybe Number 2, but I see I cannot upgrade the firmware until I can associate the unit with the SqueezeCenter; I have tried both WIFI and Ethernet, the Ethernet port works but doesn't seem to be returning data to identify itself to the network bit of a catch 22.

If you feel its Number 3. if there is a known issue can anyone supply a circuit diagram and or list the problem component and I'll get it fixed.

I'm from New Zealand so sending the device to Slim Devices is out of the question plus it would be out of warranty.

Note I have also sent an email to Slim Devices waiting on a response but though the community may have another viewpoint on this issue the more Brains the better.

Bottom Line I was really looking forward to streaming my media collection so this is a bit of a let down any assistance would be appreciated.

Kind Regards and thanks in advance )

[JJZolx]

Hopefully, it's just the screen. If you enable logging you might see the protocol negotiation with the player. Without being able to establish a connection with the server, this might be your only evidence that the device is alive. Go to Settings > Advanced > Logging, and setting network.protocol.slimproto to 'Debug'.

Forget trying to set it up using wireless. Too many steps to go through blind and you'll never enter the wireless password correctly. You'll have to use ethernet and make sure you have DHCP working on your network.

Try the following. It's worth a shot, anyway. Tested on an SB2, which uses the same firmware as the Classic. I was actually able to walk through the process with the display covered up.

1. Plug in the ethernet cable and pull out the power plug.
2. Do a factory reset. Point the remote at the display while pressing the ADD ("+") button. Plug in the power plug and count to 7, then release the ADD button on the remote.
3. Welcome to Squeezebox. Wait 15 seconds and it will push right by itself.
4. Language selection. Press right-arrow to select English.
5. Set up networking. Press right-arrow.
6. Choose wireless or ethernet. Press down-arrow once, then right-arrow for ethernet.
7. IP address. Press right-arrow to choose DHCP.
8. Wait 30 seconds. Press right-arrow to select your SqueezeCenter server that (hopefully) it will have found.

The timing isn't really critical. For the factory setup you have to hold the button pressed for (I'm guessing) at least 5 seconds, but if you hold it too long you end up forcing another factory reset after it reboots. The 15 seconds just means wait at least 15 seconds. DHCP negotiation usually takes only a few seconds, but I've sometimes seen it take 10-20 seconds on my network.

Factory reset, right, right, down, right, right, right.

Good luck.

[Mnyb]

If one can get it to factory reset , can one use the NET-UDAP perl script for setup ?
I saw somewhere that this would work for all players not only the receiver ?

Worth the effort to try anyway.

[Deepbluesky]

Thanks JJ, I tried but no luck will try again once I get another set of batteries for the remote.

Mnyb - i will look at the perl script too once I get some life out of the box .

I have news that the help desk is getting teer 2 support look at the issue so if I find out anything I'll post and let everyonee know .

Cheers
Thanks guys for you help so far.

[fcm4711]

Hi there

Mnyb is correct, all players can be setup via NET-UDAP, but only if they have the correct (recent enough) fw. (SB3: >= 98, TR >= 46, SBR: all, SBB >= 19).

Since you don't have visual it will be difficult to confirm what fw is on your SB3 but maybe the seller can tell you. If the fw is newer you could give it a try, if it's older NET-UDAP won't work.

Another option would be to open up your SB3 up and check if:

1) It runs if you remove the wireless card (wlan card could be dead)
2) Check if the processor daughter board is connected firmly with the main board. (sometimes the connector comes loose.)

Hope this helps
Felix

[sander]

Just out of curiosity is this a wifi Classic? I bought a used Classic which exhibited the same symptoms, and I removed the wifi card and it worked.

[AnotherTribe]

My SB3 Classic became comatose a few weeks ago, no sign of life whatsoever, not even a pleasing red glow from the optical out. I removed the WLAN card and viola!, it lived, albeit now a wired SB3 only. So, assuming your SB3 is also a wireless version then this may be something to try along with your natural Kiwi ingenuity.

[Deepbluesky]

I have a small win,
Bought new Batteries for the remote then tried again, NO LUCK.

Removed WIFI card thanks guys, then used JJZolx's procedure to reset the device thanks JJ and can report I now see the Squeezebox returning an IP address, it shows up in the routers DHCP table as Unknown device, I can also ping it.

The reason its a small win is that Squeeze Center still cannot see the device.

Seeing that I can ping the Squeezebox I'm going to look at the NET-UDAP mentioned here.

[peterw]

The reason its a small win is that Squeeze Center still cannot see the device.

Seeing that I can ping the Squeezebox I'm going to look at the NET-UDAP mentioned here.

Are you sure that your Squeezebox can see SqueezeCenter? It could be that a firewall device or firewall/security settings on the PC running SqueezeCenter are blocking connection attempts coming from the Squeezebox. Ideally you want to allow inbound TCP to ports 9000 and 3483, and inbound UDP port 3483.

[Deepbluesky]

Thanks Peter, I have checked the firewall it looks OK, plus I have opened up the router to allow port forwarding for the ports in question.

This is what the server log is returning as you can see it sees the SB, any help deciphering what is happening would be helpful.

***SNIPPET****
[09-05-14 14:05:29.6830] Slim::Utils::PluginManager::enablePlugins (440) Enabling plugin: [Slim::Plugin::Slacker::Plugin]
[09-05-14 14:05:29.7263] Slim::Utils::PluginManager::enablePlugins (510) Adding HTML directory: [C:\Program Files\SqueezeCenter\server\Slim\Plugin\Slacker\HTM L]
[09-05-14 14:05:29.7274] Slim::Utils::PluginManager::enablePlugins (440) Enabling plugin: [Slim::Plugin::SlimTris::Plugin]
[09-05-14 14:05:29.7475] Slim::Utils::PluginManager::enablePlugins (435) Skipping plugin: Slim::Plugin::Snow::Plugin - disabled
[09-05-14 14:05:29.7483] Slim::Utils::PluginManager::enablePlugins (440) Enabling plugin: [Slim::Plugin::SongScanner::Plugin]
[09-05-14 14:05:29.7712] Slim::Utils::PluginManager::enablePlugins (440) Enabling plugin: [Slim::Plugin::Sounds::Plugin]
[09-05-14 14:05:29.7950] Slim::Utils::PluginManager::enablePlugins (510) Adding HTML directory: [C:\Program Files\SqueezeCenter\server\Slim\Plugin\Sounds\HTML]
[09-05-14 14:05:29.7961] Slim::Utils::PluginManager::enablePlugins (440) Enabling plugin: [Slim::Plugin::Visualizer::Plugin]
[09-05-14 14:05:29.8193] Slim::Utils::PluginManager::enablePlugins (440) Enabling plugin: [Slim::Plugin::iTunes::Plugin]
[09-05-14 14:05:29.8807] Slim::Utils::PluginManager::enablePlugins (510) Adding HTML directory: [C:\Program Files\SqueezeCenter\server\Slim\Plugin\iTunes\HTML]
[09-05-14 14:05:29.8817] Slim::Utils::PluginManager::enablePlugins (435) Skipping plugin: Slim::Plugin::xPL::Plugin - disabled
[09-05-14 14:05:30.1060] Slim::Utils::PluginManager::writePluginCache (173) Writing out plugin data file.
[09-05-14 14:05:30.1199] main::init (432) SqueezeCenter Jive init...
[09-05-14 14:05:32.2500] main::init (435) Remote Metadata init...
[09-05-14 14:05:32.3481] main::init (444) SqueezeCenter checkDataSource...
[09-05-14 14:05:32.4435] main::init (448) SqueezeCenter persist playlists...
[09-05-14 14:05:32.4444] main::init (463) SqueezeCenter HTTP enable...
[09-05-14 14:05:32.4516] main::init (467) mDNS startAdvertising...
[09-05-14 14:05:32.4524] main::init (475) SqueezeCenter done init...
[09-05-14 14:05:32.4555] Slim::Networking:iscovery::gotTLVRequest (156) discovery packet:"eIPAD\0NAME\0JSON\0"
[09-05-14 14:05:32.4562] Slim::Networking:iscovery::gotTLVRequest (173) TLV:IPAD len: 0
[09-05-14 14:05:32.4567] Slim::Networking:iscovery::gotTLVRequest (173) TLV:NAME len: 0
[09-05-14 14:05:32.4579] Slim::Networking:iscovery::gotTLVRequest (173) TLV:JSON len: 0
[09-05-14 14:05:32.4585] Slim::Networking:iscovery::gotTLVRequest (194) sending response
[09-05-14 14:05:32.4593] Slim::Networking:iscovery::gotDiscoveryRequest (87) gotDiscoveryRequest: deviceid = 4, revision = 5.1, MAC = 00:04:20:12:38:26
[09-05-14 14:05:32.4604] Slim::Networking:iscovery::gotDiscoveryRequest (99) It's a Squeezebox
[09-05-14 14:05:32.4611] Slim::Networking:iscovery::serverHostname (53) calculated WideBoy length: 17
[09-05-14 14:05:32.4619] Slim::Networking:iscovery::gotDiscoveryRequest (110)gotDiscoveryRequest: Sent discovery response.
[09-05-14 14:05:32.4629] Slim::Networking:iscovery::gotDiscoveryRequest (87) gotDiscoveryRequest: deviceid = 4, revision = 5.1, MAC = 00:04:20:12:38:26
[09-05-14 14:05:32.4634] Slim::Networking:iscovery::gotDiscoveryRequest (99) It's a Squeezebox
[09-05-14 14:05:32.4640] Slim::Networking:iscovery::serverHostname (53) calculated WideBoy length: 17
[09-05-14 14:05:32.4647] Slim::Networking:iscovery::gotDiscoveryRequest (110)gotDiscoveryRequest: Sent discovery response.
[09-05-14 14:05:32.4656] Slim::Networking:iscovery::Server::gotTLVResponse (161) discovery response packet:
[09-05-14 14:05:32.4662] Slim::Networking:iscovery::Server::gotTLVResponse (177) TLV: NAME len: 7, WideBoy
[09-05-14 14:05:32.4667] Slim::Networking:iscovery::Server::gotTLVResponse (177) TLV: JSON len: 4, 9000
[09-05-14 14:05:32.4673] Slim::Networking:iscovery::Server::gotTLVResponse (197) Discovered server WideBoy (192.168.1.10), using port 9000
[09-05-14 14:05:34.7713] Slim::Networking:iscovery::gotDiscoveryRequest (87) gotDiscoveryRequest: deviceid = 4, revision = 5.1, MAC = 00:04:20:12:38:26
[09-05-14 14:05:34.7720] Slim::Networking:iscovery::gotDiscoveryRequest (99) It's a Squeezebox
[09-05-14 14:05:34.7726] Slim::Networking:iscovery::serverHostname (53) calculated WideBoy length: 17
[09-05-14 14:05:34.7733] Slim::Networking:iscovery::gotDiscoveryRequest (110)gotDiscoveryRequest: Sent discovery response.
[09-05-14 14:05:34.8125] Slim::Plugin::InternetRadio::Plugin::cacheIcon (204) Caching remote icon http://www.squeezenetwork.com/static...cons/picks.png as
C:\Documents and Settings\All Users\Application Data\SqueezeCenter\Cache\icons\picks.png
[09-05-14 14:05:34.8388] Slim::Plugin::InternetRadio::Plugin::cacheIcon (204) Caching remote icon http://www.squeezenetwork.com/static...radiolocal.png as C:\Documents and Settings\All Users\Application Data\SqueezeCenter\Cache\icons\radiolocal.png
[09-05-14 14:05:34.8477] Slim::Plugin::InternetRadio::Plugin::cacheIcon (204) Caching remote icon http://www.squeezenetwork.com/static...radiomusic.png as C:\Documents and Settings\All Users\Application Data\SqueezeCenter\Cache\icons\radiomusic.png
[09-05-14 14:05:34.8564] Slim::Plugin::InternetRadio::Plugin::cacheIcon (204) Caching remote icon http://www.squeezenetwork.com/static...radioworld.png as C:\Documents and Settings\All Users\Application Data\SqueezeCenter\Cache\icons\radioworld.png
[09-05-14 14:05:34.8663] Slim::Plugin::InternetRadio::Plugin::cacheIcon (204) Caching remote icon http://www.squeezenetwork.com/static...ns/radioio.png
as C:\Documents and Settings\All Users\Application Data\SqueezeCenter\Cache\icons\radioio.png
[09-05-14 14:05:34.8882] Slim::Plugin::InternetRadio::Plugin::cacheIcon (204) Caching remote icon http://www.squeezenetwork.com/static...oproviders.png as C:\Documents and Settings\All Users\Application Data\SqueezeCenter\Cache\icons\radioproviders.png
[09-05-14 14:05:34.8974] Slim::Plugin::InternetRadio::Plugin::cacheIcon (204) Caching remote icon http://www.squeezenetwork.com/static...ns/radiosearch.
png as C:\Documents and Settings\All Users\Application Data\SqueezeCenter\Cache\icons\radiosearch.png
[09-05-14 14:05:37.0816] Slim::Utils::Cache::cleanup (271) Cache purge: FileCache - skipping, purged recently
[09-05-14 14:05:37.0827] Slim::Networking:iscovery::gotDiscoveryRequest (87) gotDiscoveryRequest: deviceid = 4, revision = 5.1, MAC = 00:04:20:12:38:26
[09-05-14 14:05:37.0834] Slim::Networking:iscovery::gotDiscoveryRequest (99) It's a Squeezebox
[09-05-14 14:05:37.0839] Slim::Networking:iscovery::serverHostname (53) calculated WideBoy length: 17
[09-05-14 14:05:37.0846] Slim::Networking:iscovery::gotDiscoveryRequest (110)gotDiscoveryRequest: Sent discovery response.
[09-05-14 14:05:40.0455] Slim::Networking:iscovery::gotDiscoveryRequest (87) gotDiscoveryRequest: deviceid = 4, revision = 5.1, MAC = 00:04:20:12:38:26
[09-05-14 14:05:40.0464] Slim::Networking:iscovery::gotDiscoveryRequest (99) It's a Squeezebox
[09-05-14 14:05:40.0470] Slim::Networking:iscovery::serverHostname (53) calculated WideBoy length: 17
[09-05-14 14:05:40.0477] Slim::Networking:iscovery::gotDiscoveryRequest (110)gotDiscoveryRequest: Sent discovery response.
[09-05-14 14:05:43.0533] Slim::Networking:iscovery::gotDiscoveryRequest (87) gotDiscoveryRequest: deviceid = 4, revision = 5.1, MAC = 00:04:20:12:38:26
[09-05-14 14:05:43.0542] Slim::Networking:iscovery::gotDiscoveryRequest (99) It's a Squeezebox
[09-05-14 14:05:43.0548] Slim::Networking:iscovery::serverHostname (53) calculated WideBoy length: 17
[09-05-14 14:05:43.0555] Slim::Networking:iscovery::gotDiscoveryRequest (110)gotDiscoveryRequest: Sent discovery response.
[09-05-14 14:05:46.0484] Slim::Networking:iscovery::gotDiscoveryRequest (87) gotDiscoveryRequest: deviceid = 4, revision = 5.1, MAC = 00:04:20:12:38:26
[09-05-14 14:05:46.0493] Slim::Networking:iscovery::gotDiscoveryRequest (99) It's a Squeezebox
[09-05-14 14:05:46.0498] Slim::Networking:iscovery::serverHostname (53) calculated WideBoy length: 17
[09-05-14 14:05:46.0506] Slim::Networking:iscovery::gotDiscoveryRequest (110)gotDiscoveryRequest: Sent discovery response.
[09-05-14 14:05:49.0562] Slim::Networking:iscovery::gotDiscoveryRequest (87) gotDiscoveryRequest: deviceid = 4, revision = 5.1, MAC = 00:04:20:12:38:26
[09-05-14 14:05:49.0570] Slim::Networking:iscovery::gotDiscoveryRequest (99) It's a Squeezebox
[09-05-14 14:05:49.0576] Slim::Networking:iscovery::serverHostname (53) calculated WideBoy length: 17
[09-05-14 14:05:49.0583] Slim::Networking:iscovery::gotDiscoveryRequest (110)gotDiscoveryRequest: Sent discovery response.
[09-05-14 14:05:52.0504] Slim::Networking:iscovery::gotDiscoveryRequest (87) gotDiscoveryRequest: deviceid = 4, revision = 5.1, MAC = 00:04:20:12:38:26
[09-05-14 14:05:52.0512] Slim::Networking:iscovery::gotDiscoveryRequest (99) It's a Squeezebox

[peterw]

This is what the server log is returning as you can see it sees the SB, any help deciphering what is happening would be helpful.

That log is encouraging. Earlier you wrote that "Squeeze Center still cannot see the device." Can you try to describe exactly what does and doesn't work? You're what, using the :9000 web address to try interacting with the SB? Is the SB listed there?

I wonder if the SB might be stuck waiting for a firmware update. I thought there was a setting in SqueezeCenter to push firmware updates "automatically" (not require you to hold the Brightness key on a real Slim Devices remote), but I can't find that now in my 7.4 instance.

[Deepbluesky]

OK the device works to the point of seeing the network it can be pinged and can be seen in the earlier logs.

The remote seems to access the device as the reset procedure by written by JJZolx works this also suggests the device is accepting commands.

What does not work is that the screen is blank and that the device is not seen buy Squeeze Center.

I have checked using 'SoftSqueeze' that the Squeeze Center set-up is working I can listen to stations etc.

I have also tried the NET-UDAP program but cannot find the Squeezebox. My network consists of a PC connected to a Linksys WAG200G via Ethernet using a Static IP address the Squeezebox is connecting through DHCP also by Ethernet at the moment.

I would like to know how to push a firmware update out to the device not using Squeeze Center I think this would help greatly. Or even better still have the Squeeze Center see the Squeezebox so the firmware can be updated.

[rickwookie]

Hi guys

Just a thought, if the formware did need updating, I think it would still show up in the SqueezeCenter web interface under players I think with a message in the playlist area informing of the need for a firmware update. You could try holding down the brightness button on your IR remote (while pointing it at the Squeezebox of course!) for about five seconds, then waiting a couple of minutes. If there were a firmware update pending, this should run it.

If there are no players showing up, then the problem is probably something else. The player not showing up is strange though since the log seems to indicate the the Squeezebox has been detected.

[Deepbluesky]

OK A Win I forced a firmware update, I worked it through in my mind that if the device could accept a factory reset it should accept a firmware update, and so it did.

The brightness control method worked, now I have a working device. With no WIFI or display.

So this is next on the hit list, I would love any ideas re the display.

Cheers and thanks guys for you all your help.

[rickwookie]

Since it doesn't seem to be the WiFi that was causing your display problem, you should be able to put the WiFi (card?) back in the SB (if you haven't alredy done so). Then you should be able to use NET-UDAP to set it up if you really need to use the device via WiFi, although if wired works for you that's a better method anyway (more bandwidth, more reliable, etc.).

How does the unit sound? :-)