Bug 6642 - MPQ Receiver/SBR setup: unable to switch from SN to SC7
: MPQ Receiver/SBR setup: unable to switch from SN to SC7
Status: RESOLVED DUPLICATE of bug 6303
Product: SB Controller
Classification: Unclassified
Component: Setup
: unspecified
: All Other
: P2 major (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-17 20:44 UTC by Peter Watkins
Modified: 2008-01-18 09:54 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Watkins 2008-01-17 20:44:14 UTC
I connected an MPQ Receiver to SqueezeNetwork first (after, IIRC, allowing the MPQ SBC to install an update from the network). Unable to play a public MP3 stream (hey, it is the production SqueezeNetwork, maybe I was too optimistic), I decided to start up my local Subversion SC7 daemon and switch the Receiver to that. But how? I've tried pressing the SBR button for a few seconds until it flashed red slowly, but the MPQ SBC doesn't see it in the Set Up Squeezebox screen. I tried what I imagined should be a hard reset on the SBR -- hold the button until it went dark and then started flashing quickly. No luck. I tried a factory reset of the MPQ SBC (holding Add at boot). Still no luck.

Finally I booted my JHB SBC and connected it to my SC7 daemon. WIth the JHB and MPQ SBCs side-by-side, only the JHB SBC listed the MPQ SBR on the Set Up Squeezebox. With the JHB SBC, I was able to connect the SBR to SC7. After doing so, the JHB SBC informed me there was a firmware update, which I installed.

That done, the MPQ SBC prompted for a firmware update. I installed that over the network and now both SBCs see/control the SBR fine.

Sorry I didn't take note of the SBC firmware revisions during this process. :-(

I'm flagging this bug as "major" because it could be a real user experience problem if new Duet owners do as I did and choose to connect to SN because it's the only option if SC7 isn't running or discoverable on the wifi network.
Comment 1 Blackketter Dean 2008-01-18 09:54:53 UTC

*** This bug has been marked as a duplicate of 6303 ***