Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Systems Comms into DSP9

Reading here the new post about SpeakerLink wiring reminds me that I will lose the BNC comms connection on my DSP7200SE when I trade them in for DSP9. That’s a problem because audio only comes from my DDC through the AES-to-Cat8 cable I made, while control is currently routed through a spare 568.2mm surround unit with a DIN-to-BNC. If DSP9 only gets wired control over SL, or via the supplied B-link adapter for Bluetooth (which needs the RJ45 jack, blocking my audio feed), what options do I have other than another MSR to the speakers’ IR receiver?

Two questions:
Is it possible to make use of the DSP9’s USB maintenance input?
Can a RS232 serial connector be wired to the Cat8 cable for me to continue with vMSR on my iPad?

I don't know.

Yes, see the wiring diagrams that were linked the topic you just read. It details the SL pinouts for Meridian RS232 : Rx, Tx and Ground.

It also details them for Meridian COMMS as well.

SpeakerLink used as Digital Out (XLR or SPDIF) plus COMMS and RS232

Regards,
Carl

Thanks, Carl. I did use those helpful diagrams to successfully wire a Neutrik SLR connector to the Cat8, but have no idea about which pins carry Rx, Tx and ground, or anything else needed, on the male RS232 connector…

On a DB9 pins 2 3 and 5 are used for RS232. 5 is ground. Pins 2 and 3 can be either TX or rx depending upon the application.

I find it shocking that a dealer selling these would not resolve or research any potential comms incompatibility and sort it out before the customer parts with this sum of money.
to have to risk things by going diy is ludicrous at this price level
Rgds
Stuart

You can made a custom cable where 3 pins are used for the AES/EBU audio input and other two pins are used for the comms of your actual system.

I already tested it (the comm part), I cut an CAT6 cable and keep the Pin 1-Master Comms and Pin 2-Ground connected to the MC200. I checked and I was able to turn the speakers on, off and control the volume. If can custom made a cable that goes to you actual controller and connect it with your sound source in the RJ45 that goes to the speakers or you can create an RJ45 splitter, where in one side you only have the audio source connected and in the other only the comms.

I also tried RS232 with the M6, I was able to control it, but the M6 does not transmit the RS232 commands for the right speaker. This way I was only able to turn on/off/vol+/vol- in the master speaker, I don't know if this happens only with the RS232.

One advantage of the RS232 in the case of the M6 is that I can use it to control EBA, EBC, Loudness and others things (but it need to be done one speaker at a time). The MC200 doesn't offers be this kind of sound controls.

Your system is way more new and advanced than mine, but some of the logic might apply even in your system.

Cheers.

I hope it is that simple. Today I use an old-fashioned comms cable with two wires spliced to BNC which also carries commands from a network-to-serial adapter plugged into the 568.2mm RS232 port. Would this adapter connect directly to Cat8, without any M electronics, to send commands?

When I look at RS232 pin assignments, I see more than Tx and Rx: Data Carrier, Set, Ready, Clear etc. and am over my head in understanding how to proceed so that I can sell or redeploy my old surround unit.

You don't need to worry about any of the additional pins in the DB9 connector. Just Rx, Tx and ground.

What gender is the connector on the network to rs232 adaptor?

If it's male, you will be connecting to the 568 using a null-modem cable, and it will have RX on pin 2 and TX on pin 3. You can:
put a male connector on the cat 8 with Pin 2 as Rx and Pin 3 as Tx and continue to use the null-modem cable OR:
put a female connector on the Cat 8 and use pin 3 as Rx, pin 2 as Tx. and plug it straight into the adaptor.

If it's female it will already have Rx on Pin 3 and Tx on Pin 2, so you will need to put a male connector on the Cat8 with Pin 2 as Rx and Pin 3 as TX and either plug it straight in or use an extension cable (not a null-modem cable).

Basically Rx of the Network to RS232 Adaptor goes to Tx of the speaker and vice versa. Null-modem cables just swap pin 2 and pin 3 to achieve this between 2 male connectors.

Hope this helps,

Julian

Thanks!

The adapter ends female to mate with the male built into 568, so I will purchase this DB9 and attach Cat8 wires as you’ve described.

Now I won’t need to tie up an excellent surround unit just for comms because of all of your (plural) help on this forum.

Brad, a Distributor 1 will give you all the connections you need in a nice, neat box that will work without fiddling with handmade cables. My concern is what is the exact command string coming from Virtual MSR for selecting DVD as a source for instance? The reason I ask is that standard Meridian serial commands for selecting DVD as a source "DV\x0A" DO NOT power on a XE speaker from standby. The reply from the speaker in "unknown command". Adding the MSR key emulator command string for selecting DVD as a source "MSR DV \x0A" does turn the speaker on. I so far have not found the actual strings for Virtual MSR but will continue looking.

Upon further testing, I found that every other Meridian speaker I tried responds to the standard Meridian commands as issued in Control window that I assume is the same command protocol used in Virtual MSR. The XE and presumably the DSP9 do not. I will stay on this to find out why.

The short answer is that the DSP8000XE and DSP9 will not work with Virtual MSR or longtime standard Meridian RS-232 commands. A control system such as Crestron or others can still be used to control the newer speakers with RS232, I have demonstrated this with my XE's.

OldDogCan your best bet is to use a 218 which will allow you to use the Meridian Control app which has many more useful features than Virtual MSR. The 218 also has a speakerlink input where you can use your AES to RJ45 cable to insert your audio device into the 218.