Skip to main content
attacama40
Headliner I
March 6, 2017
Question

Connect Amp with Sub+CCM663's cut's out, need an extra amplifier?

  • March 6, 2017
  • 25 replies
  • 1080 views
Morning all, derivative of a question asked many times (also by me) but with new scenario this time.

Have a Connect Amp (actually a new one in this location) to work alongside a Sonos Sub & two pairs of B&W ceiling speakers.

Originally installed 2 x B&W CCM616's but now fitted extra pair of B&W CCM663's & with a view to downgrading the CCM616's to bedroom duty and adding a second set of CCM663's in the kitchen.

They sound great but of course the CCM663's overshadow the CCM616's, hence the adjustments. Just to clarify, it means I have 2 616's & 2 663's working right now with the Kitchen Sonos.

But the Connect Amp cuts out when worked hard. Installed the new speakers December & unusually they not been used so much as normal....daily yes but not worked hard.

A Biffy Clyro, and Gang of Four session yesterday showed the Connect Amp to cut out when driven hard. All other rooms & Sonos boxes worked as normal. I think I'm over working the Sonos box but is opinion not deduction.

If I power down & up, then the Sonos box recovers & continues to earn a decent living.

Have a feeling I need external amplification. Have looked at this before but in the end never needed needless to say, due to more skilled advice on this site.

Would like to understand:

a. If I am over driving the Sonos unit
b. If I have some component mismatch that I'm not understanding
c. If I'm over working the Sonos then can I add a decent quality, small (tiny) footprint amp with ease

Definitely some of you have helped me with this question was way back.....think Buzz and Ratty amongst others. I cannot find that Q just now so must be very old, the scenario was a lot different anyway.

Would very much appreciate a direction on this one.....my Sonos system earns it's crust & then some but it's frustrating a little just now in this area. Many thanks in advance
    This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

    25 replies

    Show previous replies
    attacama40Author
    Headliner I
    March 28, 2017
    Hi Kumar and thanks for the advice.

    It does appear ironically that switching the newly added C:A off and on sorts the problem.

    My earlier network description was slightly wrong (although I don't understand why it would make a difference) ....

    The original C:A is RJ45 connected to a wall plate then back to a Netgear 48 port gigabit switch (with zero config other than vanilla) and then to a Linksys router EA9500, then to a VM Superhub 3 modem.

    The 2nd (newly added one) goes to a Linksys SE2500 simple gigabit hub before going to a second RJ45 wall port then back to the same Netgear 48 port gigabit switch....again neither have any config other than out of the box.

    I don't really understand why that might cause an IP address conflict but there does seem some commonality for sure.

    I wander if having a dedicated switch at the router/modem end purely for Sonos could help eliminate such problems? Or is that just hardware overkill?

    The network does have a lot of stuff on it but all well established and very vanilla, nothing exotic. All Sonos is on RJ45.

    I can set fixed IP's for Sonos is it is required.....I guess I'm just not really understanding why it is required.

    Thanks for your continued support
    Kumar
    March 28, 2017
    With anything more complex than plain vanilla, I am all at sea where networks and routers are concerned, so I will pass on this; someone else should drop in with better advice. Else, Sonos Support.

    On the reserved IP, because IPs are renewed from time to time, not doing so can cause IP address conflicts is about all I know on THAT. And that having done it in my router, my streaming stability has become satisfactory.
    ratty
    ratty
    March 28, 2017
    attacama40

    Switches are in principle layer 2 devices, so would have no intrinsic impact on IP issues. That said, managed switches have an IP address for configuration purposes, so there's a remote chance that one could cause a problem.

    I agree that your reports do suggest a possible IP conflict. A complete network restart is a good first step. Otherwise, sketch out your network topology for us.
    CAW
    Collaborator II
    March 29, 2017
    Since you say both C:As are hardwired, I'd try disabling their WiFi radios. Or at least one of their radios if you rely on that location relaying to another Sonos device somewhere else. This is one of those things Sonos claims is not supported, but it is (and I suspect was added for installers so is unofficially officially suported). Google will quickly give you the info on how to do this.
    attacama40Author
    Headliner I
    June 3, 2017
    Hi folks and apologies for the late reply/feedback.

    It turns out I had a damaged RJ45 feed to one CA from the switch. That was compounded by the Sub that I thought was hardwired actually being on wifi! I'd fed the RJ45 in but due to a decorating project I'd forgot to connect the XXXX thing! Attention to detail!!!

    So the Sub was actually cutting out every now and again on the wifi and the damaged cable meant the 2nd CA was intermittent. Apols for the dropout, (been away on a work project) but many thanks to you both for following up.
    Terms & ConditionsAccessibility statement