Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Systems Anyone running an AC200 with legacy speakers? I have no comms.

Is anyone running an AC200 with non-SpeakerLink speakers?

I have made up cables, used a reviver, but I simply can't get comms to talk to an SW1600 sub at all.

Direct from AC200 or daisy chained from a DSP3200.

I just can't understand why it won't control the volume. I have advertised the sub after seeing people say they have the same issue, but it is doing my head in and I would like to try and understand why it doesn't work.

I would just like to hear if anyone has used an AC200 with legacy speakers, or if someone who has both in their house if they could possibly try it for me?

It makes no sense to me, if the AC200 has comms, albeit on speakerlink, and the SW1600 has comms, albeit din or BNC, then why can't the AC200 control the subs volume?

I also gave up on getting my DSP subwoofer to work with my AC200/DSP33 setup. Initially when I purchased the sub I thought it was defective until I hooked it up to my 800 series and 500 series systems.

I just don't get why it doesn't work though.

Meridian have just said "It is a legacy product, buy a DSW for £3750."

But at the same time they say legacy speakers can be used with the AC200 using an AC12.

I don't get what the difference is between the comms on a pair of pre-SpeakerLink speakers and the SW1600 sub?

If the comms on the AC200 controls the legacy speakers why don't they control the SW1600?

If I put in say an 218, would that work? Or will it be more of the same?

Obviously there is no help from Meridian any more on this. It seems that my premium partner can't get any info back from them either, and I can feel their frustration. But I would love to get this working rather than sell it.

Is the width control in the AC200 or the DSP3200? This adds so much to the package as I am using it for a stereo pair either side of a TV in the conservatory. The way it spreads the soundstage the full width of the room is very impressive.

Oh, just clicked you have been running DSP33's with the AC200 Carlton.

So legacy speakers do work then.

I wonder what it is that stops the SW1600 comms working then?

Very bizarre.

I also could not get my SW1600 working with my AC200/DSP3200 system. I tried using an AC12, no idea why it shouldn’t work. I ended up buying a used DSW sub.

I just don't understand why it won't work, unless the SW1600 only sees a legacy comms protocol that the AC200 does not give out?

What else can it be?

Hi,

Just to confirm that the AC200 works fine with legacy products, I have mine attached to a DSP5000 (smiley face) pair via a 'Reviver" and all works fine. It also works with DSP33, although I had to connect the comms in to the out port on the DSP33 (usual trick with the DSP33).
I wonder if the same thing might have some effect with your situation?

I haven't tried a sub on that system.

Brian

Thanks Brian,

Yeah, I tried connecting to the output, just on the off chance.

It is the most bizarre thing.

Which legacy speakers are you trying to use with the AC200?

I just wonder if you might have to configure the speaker to be aware of the sub. The DSP5000s have two sub setting options which need to be set up to get the correct integration - perhaps that might influence the comms.

Does the AC200 have any sub-related configuration like the 818v3?

I'm using DSP3200 speakers with it, and I presumed, with an AC12/Reviver I would be able to hook in an SW1600 sub.

But it won't play ball. Not daisy changed from a DSP3200 out or direct from the AC200, master or slave out.

The AC200 does have a sub setting but that is just telling the sub and speakers to play full range, crossover at 80hz and crossover at 100hz I think it is.
But that was added in a later firmware update and is designed more for the DSW sub.

I wonder if an earlier firmware might resolve the issue?

Can the firmware be rolled back on these?

I was trying to find out if the comms address has changed? When we set speaker for 500, G, SLS etc. is that changing comms addresses?
Maybe the SW1600 is set at 500 comms and no way to change it?

Are you using an AC12 or a Reviver?

I vaguely remember that there were different flavours of Reviver depending on application so perhaps you have the wrong one?

I would put a multimeter on the legacy comms outputs and see if anything is getting through.

Similarly connect an SPDIF device up to see if any sound signal is getting through.

Cheers Gianni.

I am using a Reviver, that was for going into legacy speakers, no joy.

I also made up a cable, firstly with BNC and then with the DIN, with the link wired etc.

It seems I am not the only one though, a few have said they had the same issue trying to get the sub running with the AC200 and DSP3200s.

If I put a multimeter on the BNC, DIN etc., I do get a change as the volume button goes up and down.

I have resigned the fact it is not going to work, but I would still like to understand why that is.

Edit: There is sound, but there is no volume control.