Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Restaurant at the End of Universe Hitchhikers - Meridian Equipment WTB: Cheap Meridian Processor?

the 512 and dsp33's does not need a processor just a source connected.

I know that, but we have a HD621 in the chain and attaching the 512 to that, but surely the units still think there is a controller in the system somewhere unless it has been told otherwise??

Look at it this way, on my system I have a 568.2 and 3 x 5Ks, I have the 568 as the 'controller' and not any of the speakers, when I take out the 568 the speakers still don't work until I tell the system to treat one of them as 'controller' in the set up.

Plugging the 512 straight into the 33s should be fine, but going via the HD621 will probably throw things out? I haven't a clue and just thinking out loud, but I would try setting up a new config and telling it there is a HD621 and a pair of 5000's and seeing what happens.

I think Gizze may be right. That's one of the many reasons I got rid of my DSP33's. They are a PITA in this regard. You have no idea if they are on and what volume they are at either. I'm amazed Meridian went down this route again with the 3200's.

well, I would hook the 512 up to the DSP33's but I've not got the D5 cable, nor does anyone seem to know how to make one, so I'm trying to find alternatives here.

I know what you mean about the HD621 not being the controller, but can it be configured to be a controller? the Meridian config program does list it under "controllers" but I can't see any config to set it as a controller. nor does it then allow me to add speakers.

The HD621 manual does say (on page 8) that the HD621 can act as a controller if used in a non-Meridian system, but doesn't really tell me how to do it. if I could config it as a controller, would it then accept IR commands from the 512?

ed_t: Thanks, she's still in neo-natal at the moment, due to being seven weeks premature, but she seems to be doing fine which is the important thing.

george: I agree, it's the most frustrating thing about the DSP33's and don't get me wrong, I'd love a pair of 3100's or 5000's or whatever. but the 33's were what I could afford and with the arrival of a new baby, I'm not really in a position to upgrade now, as much as I'd like to. if I can somehow get all this working, then I could send the G68 into the mothership for some TLC and then get my system working properly!

I do kind of wonder if I've done the right thing investing into the bottom end of Meridian at this stage, with all these issues, but I guess I'm here now so I've got to work through it as I can't afford to change it all now.

dave

What I meant was, use the config to tell it you have a G68, HD621 and a pair of 5000's and set the 5000 as the controller, then see if the remote works via the HD621.

In other words try an trick it.

so config it with a G68, HD621 and DSP5000 but have it physically configured with the 512 plugged into the HD621 plugged into the DSP33's? I'll give it a go tomorrow, but I'm not sure I can see why it would work.

I feel like it might work if I can set the HD621 as a controller... maybe.

of course, if we knew how to wire a D5 cable, then I could let the DSP33's be the controller...

Isn't the D5 cable just a Y cable that has a male end that goes into the 33 and two female ends that allow you to plug in an the comms cable from the 512 and from say a 508??

I would just make one up and try the various wire combos in the female end, can't see it damaging anything, what voltages are we talking about over comms?

err.. potentially. I'm not really a wiring up plugs kinda guy, nor do I have the bits sadly.

Looking at the diagram on page 17 of the DSP33 userguide, it looks like a Y cable where the single end plugs into the DSP33 comms input port (180 degree din?), and the other 2 ends are female's that accept the cable from the 512 (240 degree din is it? it plugs into the DIN port on my HD621 anyways) and the other end of the Y is accepts a connection from an M5 lead.

to those who wire plugs, does that make any sort of sense?

dave

Just a reminder for you Dave; anyone got a D5 lead, once found I can upload pinouts to Duncans site, available to all then

Regards I

OK, I'm getting to the point where I might want to cry soon!

I have acquired the mystical D5 lead! this combined with my 33's should allow me to hook up a pair of 33's, the d5, the 512 and my HD621 into a HDMI accepting stereo system. and I'm pretty sure I managed to get it working briefly but it won't work anymore. Has anyone else used dsp33's with a 512 and am I missing something key?

I've been trying to config the 33's on the rs232 port to be a controller and to accept input from the 512 and it's just not doing it. I've tried using different 33's as the master (I have 3). I tried upgrading the firmware on one just in case (and now it won't respond on the serial port at all and I'm hoping it's not now a brick!).

so, questions.

1) can I use the DSP33's+512 with a non-Meridian source? the manual says I can but then doesn't tell me how to do it. in this scenario, there would be no M-lead so how does a speaker know it's the master?

2) do I need to config the DSP33's in a particular way to be used with a 512? I've set the option for control via 512/rs232 in the legacy config program but it doesn't seem to make a difference. do I need to do anything else? what about controller status? volume control (it never seems to remember this). In the sources section, should I set a comms type?

3) if I tell the DSP33 that it should be controlled via a 512/rs232, then will having an rs232 plugged in override the 512? ie, does it have to be one or the other?

4) I think I should be able to get the DSP33's to control the HD621, do I need to set anything special there regarding comms? I think that the one time I got it to work was with an M5 lead going from the HD621 to the DSP33 (via the D5 lead). I can't seem to get this to work again...

5) how do I recover my brick-like DSP33? I don't have a reset pin...

6) I don't suppose there are any Meridian owners near warrington who have both a processor and some DSP speakers that might like to help me work out where I'm going wrong are there? I think it might be useful to plug bits of my system into known working components so I can see what is working and what isn't.

I normally think of myself as being pretty technically savvy, and I've had all this working before, but for some reason, I just can't seem to work out where I'm going wrong atm

many thanks
David

Just to kick this off again I shall chip in but unfortunately it's been too long since I configured a pair of 33's and it was just done the once configured to an M processor as controller so probably cannot give definitive answers on most of your questions.

However it does sound like you may have bricked on of your DSP's during flash. This is normally not permanent and keep trying to reflash normally recovers it even if it means trying a different pc. The bios is independent of the firmware so bridling the firmware the bios will still be intact - unless you have suffered a hardware failure.

The reset for a dsp33 is a special din plug. I never needed to use this so don't know exactly what it resets.

Have you tried to Meridian controller program that works with a pc connected to the serial port? It emulates the msr remote. You may find this useful to gain initial control over the speakers.

Presumably you have set all sources to use d1 input so even if source does accidentally change you will still be using correct physical input.

Hi

What does 'bricked on of your DSP's during flash' mean?

What does 'bridling the firmware' mean?