#271540 - 2018-01-08 15:17
MC200 comms question
|
Registered: 2007-02-06
Posts: 684
Jon Raines
Paranoid android
|
Paranoid android
Registered: 2007-02-06
Posts: 684
Loc: Peterborough, UK
|
Setting up MC200 with 500 series equipment comms. (565/518 but applies to all 500 series kit) You will need a suitable cable, AC12 or Reviver to make connection. Set up your Sooloos input on MSR+ inputs 1, 2, or 3 only (left to right on the remote) (on the old MSR you may be able to use any input. Experiment.) Failure to do this will mean you have to press Function with any command you want.
On the both 565 and 518 (or 562) set comms to 4C on the Sooloos inputs. I have labeled the 518/565 input jukebox. (choose what you like) Plug your comms lead (comms only) or AC12/ Reviver into the processor and not any other equipment or you will not get the correct response. Turn on all equipment connected via comms, select CD on the MSR+ then press/hold clear and check you only have one controller. (as described in set up manual) Do this anytime you have adjusted anything.
Set the config program for Sooloos on your PC to enable comms and tell it the input number you have chosen for Sooloos. Limit the output frequency if your equipment cannot handle 96 KHz signals. You will now have control via MSR/MSR+ of Play, Stop, Pause, Track Forward and Reverse. Just pressing play on the media core app will turn on your equipment. You will also have volume control of your system via the app and the numbers will coincide.
Selecting Sooloos on the MSR and pressing play will start your Sooloos playlist (if loaded) without the app. Turning off your system will stop Sooloos playing as well. Display will not turn off the Intense LED on MC200 My question is after reading the above is, if I connect the DIN comms from the MC200 to a processor and then use the second DIN on the processor for the master speaker how does my other Meridian kit connect via comms to include the processor? Am I missing something?
596, 504, 568.2mm, 562v2, 551, DSP5Ks smileys+3dB, DSP5.5kHC smiley, DSP420's, DSP33s, DSW1500, Samsung 52", Sky Q, 3x512, 3xKef ceiling speakers, 2xMSR+custom keys, Mac Mini, Modded Edge v1.6, ATV2, vMSR, Amazon FireTV4k. Oppo 203 next
|
Top
|
|
|
#271544 - 2018-01-08 17:35
Re: MC200 comms question
[Re: Jon Raines]
|
Registered: 2011-01-25
Posts: 468
bxd
Paranoid android
|
Paranoid android
Registered: 2011-01-25
Posts: 468
Loc: Southampton, UK
|
I thought you could just insert other 500 series components between the MC200 and the processor, so the MC200 is at the end of the chain. That way, you’d only need one DIN to SpeakerLink comms adapter.
Brian
Main: G65, MD600, MS600, 218, HD621, DSP5200SE, DSP5200HCSE, M6 & D1500. System 2: G91A, MS200, DSP5000 (96/24v1), DSP3300.
|
Top
|
|
|
#271546 - 2018-01-08 18:30
Re: MC200 comms question
[Re: bxd]
|
Registered: 2007-02-06
Posts: 684
Jon Raines
Paranoid android
|
Paranoid android
Registered: 2007-02-06
Posts: 684
Loc: Peterborough, UK
|
Plug your comms lead (comms only) or AC12/ Reviver into the processor and not any other equipment or you will not get the correct response.
This is the part I was referring to, so whether the MC200 is a the end of the chain or not the processor only has two dins one presumably for the speakers and other kit leaving no room for the MC200
596, 504, 568.2mm, 562v2, 551, DSP5Ks smileys+3dB, DSP5.5kHC smiley, DSP420's, DSP33s, DSW1500, Samsung 52", Sky Q, 3x512, 3xKef ceiling speakers, 2xMSR+custom keys, Mac Mini, Modded Edge v1.6, ATV2, vMSR, Amazon FireTV4k. Oppo 203 next
|
Top
|
|
|
#271548 - 2018-01-08 18:41
Re: MC200 comms question
[Re: Jon Raines]
|
Registered: 2004-12-09
Posts: 6,215
ChrisLayerUK
President of the Imperial Galactic Government
|
President of the Imperial Galactic Government

Registered: 2004-12-09
Posts: 6,215
Loc: Colchester, Essex, UK
|
Is the comms expansion box 511, I think, useful here? If I remember correctly the 565 had more comms sockets.
No 18 in the Hall of fame  I have simple tastes; I am content to settle for the best: GIK monster bass panels, rear wall. MC200 500GB, QNAP TVS 471i3. Roon into 2 MS200's. Explorer 2. Bluesound Pulse 2 and Mini. 596 v1.89.2, 518, G61R, M60.2 Rosewood, M33C, M33 Rears, M1500 Sub, Foxsat HD, Sony Blu Ray, Pioneer 5090, 2 Chromecast's for LRB videos.
|
Top
|
|
|
#271551 - 2018-01-08 19:29
Re: MC200 comms question
[Re: ChrisLayerUK]
|
Registered: 2004-07-21
Posts: 1,743
MI'
Knows where his towel is
|
Knows where his towel is
Registered: 2004-07-21
Posts: 1,743
Loc: United Kingdom
|
Hi Chris, 565 had more comms but for speakers
What you may be able to do, and I stress, I have not tried it with MC200 is to use the other comms port and expand that with 240 DIN sockets, one which will accommodate your master speaker, the other sockets could be used for other Meridian legacy equipment.
Regards I
Under review
|
Top
|
|
|
#271585 - 2018-01-09 16:35
Re: MC200 comms question
[Re: ChrisLayerUK]
|
Registered: 2007-02-06
Posts: 684
Jon Raines
Paranoid android
|
Paranoid android
Registered: 2007-02-06
Posts: 684
Loc: Peterborough, UK
|
Is the comms expansion box 511, I think, useful here? If I remember correctly the 565 had more comms sockets. @Chris, the 565 had two DINs for comms (240') and four DINs to act as slaves (180') so similar to the 511.
596, 504, 568.2mm, 562v2, 551, DSP5Ks smileys+3dB, DSP5.5kHC smiley, DSP420's, DSP33s, DSW1500, Samsung 52", Sky Q, 3x512, 3xKef ceiling speakers, 2xMSR+custom keys, Mac Mini, Modded Edge v1.6, ATV2, vMSR, Amazon FireTV4k. Oppo 203 next
|
Top
|
|
|
#271586 - 2018-01-09 16:38
Re: MC200 comms question
[Re: MI']
|
Registered: 2007-02-06
Posts: 684
Jon Raines
Paranoid android
|
Paranoid android
Registered: 2007-02-06
Posts: 684
Loc: Peterborough, UK
|
Hi Chris, 565 had more comms but for speakers
What you may be able to do, and I stress, I have not tried it with MC200 is to use the other comms port and expand that with 240 DIN sockets, one which will accommodate your master speaker, the other sockets could be used for other Meridian legacy equipment. So do you think a spitter cable will work ok if the MC200 must go direct to a processor? So in theory a c/y splitter cable as against the s/y splitter. Jonathan
596, 504, 568.2mm, 562v2, 551, DSP5Ks smileys+3dB, DSP5.5kHC smiley, DSP420's, DSP33s, DSW1500, Samsung 52", Sky Q, 3x512, 3xKef ceiling speakers, 2xMSR+custom keys, Mac Mini, Modded Edge v1.6, ATV2, vMSR, Amazon FireTV4k. Oppo 203 next
|
Top
|
|
|
#271603 - 2018-01-09 21:47
Re: MC200 comms question
[Re: Jon Raines]
|
Registered: 2000-11-01
Posts: 2,596
RobertW
Robert.W
Great Green Arkleseizure
|
Robert.W
Great Green Arkleseizure

Registered: 2000-11-01
Posts: 2,596
Loc: Austria, Europe
|
Jon,
AFIK you can connect all sources to your processors with C-leads (daisy chain). The last in the row get connected to your processor and so you can use the second DIN connection on the 568 for the M-lead to your master speaker.
Example(com only):
Reviver: MC200(SL out)>>(SL in ) reviver(Comms plug) >>>(comms-in)596(comms-out)>>>>C-lead>>>>(comms-in)568(comms-out)>>>M5-lead>>>>(comms-in)Master DSP(comms-out)>>>S-lead>>>other slaves in daisy chain or 511 or distribution box
AC12: MC200(SL out)>>(SL in)AC12(master-Comms) >>>C-lead>>>(comms-in)596(comms-out)>>>>C-lead>>>>(comms-in)568(comms-out)>>>M5-lead>>>>(comms-in)Master DSP(comms-out)>>>S-lead>>>other slaves in daisy chain or 511 or distribution box AC12 have one C-lead more.
Both solutions have full communication, you have to take care in MConfig on the adresses !! And AFIK thats work flawless only when the 568 is the controller. The audio cables get direct connected to the 568.
861v6+ID40/800v3/3x8k.2/3x5k5s  /2x5kC/ 218/Explorer/TT-ELP/Trinnov Amethyst __HB-strip, Ayon/HB/Shunyata/Dream State Audio/Miltzow -- power cables, __Ayon/Jungson/Miltzow --analog, Miltzow-- digital, __WMA/Finalizer- , iPad air, Macbook-pro. Reviver
|
Top
|
|
|
|
4,618 Registered Members
17 Forums
24,671 Topics
252,748 Posts
Most users ever online: 211 @ 2015-05-05 14:40
|
|
|