Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Systems 568/562 - Issue when using Control Window & vMSR

Hi all,

Today I installed the needed to operate the vMSR, got it working, but I have a question.

I am using a 568 legacy processor and the keys on the remote MSR are slightly different for the sources to select.
eg. instead of a GAME source it's LD.

Now the vMSR uses the MSR+ keys, problem is I cannot select some of my old sources with equipment behind it (LP, Tape1+2, CDR, LD).

How can I overcome this and still select those sources from vMSR?

Thanks for your assistance.

Guido.

Hi again,

I did some further investigations.
When I use the Control Window application, I also have the problem.

Let me explain more: 562 + 568 setup, connecting the PC with a serial cable to 562, used config legacy program with remote as MSR+ setting.

Selecting the disc source in the Control program produces "error" in the display, which I assume is the same problem vMSR has. Selecting TV works fine.

When we solve this, I presume my vMSR issue is also solved.

Anybody able to help?

The RS232 protocols across different Meridian devices differ slightly, especially with older kit. It may be that 562 is not fully supported with vMSR - think it may have a mode for legacy or non identified devices but its been a while since I had a play and then only with DSP5000's. I'm pretty sure that vMSR wont know what its talking to as I think 562 pre dates the identify command.

Check out the 562 RS232 code list on Duncs website and compare it with devices with known suport and you may see a correlation between codes returning an error and those that work.

Yes I've looked at these technotes.

I know exactly the ones that don't work, it's the sources that have been re-mapped when going from MSR to MSR+ according to this Wiki - MSR Mapping.
I think when I would use a MSR+ on my equipment it would give me the same issue. At least through the control program it is so.

In the legacy configuration program I do have the option to say to both devices which version of remote is being used, but changing this only has an impact on the source naming in the program, nothing else on the equipment, it seems. I would like to confirm this. Is somebody using an MSR+ with an 568+562 combination with Disc+Sat+Game+Tape sources working?

Maybe I would need to re-type them?
Does it make sense?

Thanks for reading.

Hmm strange, I've just tested with a MSR+ to see if what I presumed is the case.

However Disc+Sat+Tape+Game source buttons seem to work fine on the remote, that's not something I would have expected.

I am lost again.

Hi Guido,

What firmware versions are 568 and 562 running?

Regards,
Carl

Hi,

Happy 2015 to all readers!

I am using for the 568.1 v1.55
and the 562 is a v.3 (not firmware up-gradable, I think)


Regards,
Guido

Hi again,

Your 568.1 is on the latest firmware it supports, so that's ok.
May I make a suggestion; reconfigure your system so that the 568.1 is the controller and connect the PC to the 568.1's RS232 port.

Regards,
Carl

Hi,

So tested quickly. The 568 always has been the controller.
Re-checked again using the clear on remote.

Connecting the RS-232 to 568 directly from PC to use control windows gives the same problem:

MSR+ tab using Disc, Tape, Game, Sat gives 'error'
MSR tab all sources work fine.

Maybe this is normal?
But why does a real MSR+ work then? Does it 'emulate' a MSR4 when used with a 568.1? And the vMSR doesn't? Could that be the issue?

For using the vMSR I always used the RS-232 port from the 568 since that was the main controller.

Open to other suggestions, remarks...

A real MSR+ and the vMSR have nothing in common other than the name and what it looks like on screen.

MSR+ uses an IR protocol that is generally common between devices, save for a couple of minor differences that are largely compatible in one form or another across versions.

vMSR protocol is RS232 and it would appear that there is far less control code commonality between versions let alone devices. The vMSR app would needs to map the on screen buttons with RS232 control codes for each different device it is connected to. For some devices this is well documented and they can probably be interrogated by vMSR to automatically determine the device. However, for other devices and versions, this is not the case which sounds to be the case you are finding.

Its not a case of emulating MSR4 codes, it a case of transmitting the set of codes that best match the device RS232 command set and thats only assuming it's able to determine the device its talking to in the first place.