One of the forum users that has a GC100 explained via PM how he made it work; and it seems that it is a firmware issue as we have done the same thing and he get the green bar and it stayed grey for me.
I will have to have the unit updated, for which global cache charges $35 (+shipping).
861v4 with ID40, DSP8000, DSP5500HC, DSP5500, MC200, Panasonic P-AE4000U, SI Black Diamond 142" screen
Being as you are using the same exact infrastructure that is needed for iRule, any way you can port this over to iRule? It would be AMAZING if you could make this one of the screens in iRule.
Though as I write this, I wonder if I even need iRule now. This, the Sooloos iPad app and the Dune App, are all I really need. Total control!
Primary: MD600, MS200 (SpeakerLink to AES), Trinnov ST-2, Ayre V6-xe, Salk SS8 3x LRC. Secondary: MC600 (whole house). Zone one: 568.2, G57, MS200, Spatial Hologram M2SE. Zone 2-6 (Awaiting assignment).
I can confirm it works in 808.3 and 5 as well as 861v4, 6 and 8, other will be able to fill in the blanks in due course, I guess Rick is best placed to explain exactly what it does?
Can someone please explain what managed comms does and what benefit it offers.
Other than not being supported in 500 series and DSP speakers, does it work with all other devices ie 808.3?
Hi Ian,
The Managed Comms adds processing to the returned RS232 from the Meridian equipment. If it is set to 'off' then the vMSR feedback display will show exactly what is output from the product connected. In development it was found that this can sometimes give spurious or unexpected behaviour.
I'm not going into too much detail here, but a couple of examples:
Particularly when ramping up or down the volume, as the Meridian also echoes the input command, these input commands can become mixed in with the response. This manifests itself as occasional flashes of unwanted text in the feedback box. The Managed Comms handler filters out this unwanted response to make the feedback display more persistent and fluid.
Another good of example of Managed Comms is the '0' conversion. The Meridian 800 series front panel display drivers by default show all zeros as 'slashes zeros'. Meridian didn't like this effect and so changed all zeros to Capital O's before they are sent to the display, so removing the slashes in the zeros. However this change also made its way through to the RS232 port, so vMSR would display all zeros as Capital Os The Managed Comms changes these back to zeros in such places as Bass, Treble, Lipsync, Volume etc. Interestingly we have noticed that Meridian appear to have addressed the volume output in V8.0 firmware I think?
As 500 series and DSP speakers don't have the same form of RS232 output as G and 800 series, the Managed Comms setting is best left off.
Thanks for that Rick. Very helpful and seems like your findings match some of the things that we have been found in testing. The 0/O was on a list of queries so I can tick that one off the list. We weren't sure what managed comms was doing.
Meridian owner since 1992 Prime & PSU, Focal Elear headphones, Roon (ROCK 8Gi5 NUC), Explorer 1 & 2, F80. 200/203, various Sonos (via Roon).