Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Systems My slave speaker won’t power up

Hi all,

Never encountered this issue before, but my slave speaker won’t power up with my master speaker.

I recently moved, and I had to pack my speakers and reinstall them at new home. Everything is back to the original setting, but my right slave speaker wont come to power on, and stays in the standby mode.

Digged through manual and retyped both speakers, and made sure left one is master, and the right one is slave.

Sound comes from the left master speaker only, and no sound from the right as it is still in the standby mode... (green light)

Tried to find the solution through searching the posts here, but no luck...

My setup is simple.. MS200 connected to master speaker through reviver, and master speaker is connected to slave speaker with s5 lead.

Could it be faulty cable? Speakers mis-handled when moving? Hope... not.

Please help...

Thank you?

A break in the comms line of the slave lead could do this. Open the DIN plugs at either end and check the connections for any visible damage or broken solder joints. Do you have another slave lead to try? Or a test meter to check the continuity of each connection in the existing slave lead?

Cheers

George

And make sure you have the slave comms lead plugged into the correct sockets on both speakers...

Thank you, just checked the visual observation, and the cables seems good... Also tested with the test meter, and no issues with the cable..

Right.. so for S5 Master (output, output), Slave (input, input) right?

S5 Master: output of MS200 via reviver to Input of Master Speaker.

Master Speaker: Output of Master speaker to Input of Slave speaker.

Cheers
George

Try reconfiguring your current slave as master and vice-versa. Re-wire the cables and comms accordingly and see whether the dormant speaker is working...

Oh and before you do that, make sure your current master-to-slave SPDIF is going into the correct connector on the slave.

Thank you all for you kind help...

It seems it’s not a cable issue, nor the connection issue... there got to be something else...

I have original boxes and fillings, so pretty sure the speakers were well protected during move.

Thank you

Hi All.

Thank you again for reading my problem and providing possible solutions. I love this forum.

I have self resolved the issue, and the problem was that "it was not back to my original setting."

I use lan isolator which improves performance of my MS200. This device need to sit between my router and MS200, but it turned out that I have accidentally installed it between MS200 and the reviver (speakerlink), and created this problem.

My two observations:
- Lan isolators should never be used in speakerlink (guess lan isolators recognized small and weak signals as jitters)
- Lan isolators clearly reduce jitters and digital noise, and does make difference in sound.

Anyways, I am happy that the problem is gone, and continuing to love my built to last DSP6000s.

Well that is a new one.

Congratulations on diagnosing this issue and thank-you for posting the resolution.

Just to be clear, Speakerlink cable can be used either as a LAN cable, or between endpoint/DSPs or master/slave DSPs.

However, don't confuse the messenger with the message - in this case, the LAN isolator wasn't being used in a LAN environment. The MS200 doesn't output LAN data packets to the Master speaker, but rather a balanced digital audio stream. Further, this is likely encrypted with MHR, unless you turned that off for some reason. This is balanced AES/EBU + Comms over Speakerlink.

Your Reviver then, iirc, converts AES/EBU + Comms to SPDIF + Comms and impedance matches also.

This thread has some detail about that conversion - AES/EBU-SPDIF and Reviver

Enjoy your 6Ks - wonderful speakers!