Thanks for your interest too, TK. I thought of a thing that might be relevant to our query @madskp, and while looking it up saw a thing that might be relevant to @TK too.
At the moment I have no genuine junction boxes in ML cables, so there’s no shorting between pin 3 (wh/bl, ‘ML sensor’) and pin 12 (pink, ‘+supply voltage’), as recommended on pages 34 & 35 of this Masterlink handbook. I should be able to do this fairly easily at my distributor but not for a couple of days. Do you have the short circuit in your setups, @madskp? No idea if this is actually relevant or not.
Secondly, on that page 35 it mentions ‘Data speed is 19200 bits/second. By comparison, Master Control Link data speed is 160 bits/sec’. I’m well out of my depth here, but does that imply that ML and MCL data signals are a different ‘language’, if you’ll excuse the term? And does that imply that the IR signal from a Beo4 / Beolink 1000 is a different ‘language’ too? Here’s my schematic thinking:
Beo4 / Beolink 1000 – Language A
MCL – Language B
ML – Language C
Beomaster 5500 onwards – Language A
So sending a standby signal to the link room in my most recent experimental setup might do this:
Beo4 > Language A > Rectangular IR Eye translates to Language B > MCL2A > Language B > into Beolink Passive acting as ML/MCL converter, which translates to Language C > Beolink Converter 1611 which translates back into Language A > Beomaster 6500
Without the MCL2A this might go:
Beo4 > Language A > Circular IR Eye translates to Language C > Beolink Passive > Language C > Beolink Converter 1611 which translates back into Language A > Beomaster 6500
In my scenarios here it is the translation of the standby signal from A to C in the Round IR Eye that is going wrong and causing the incorrect standby command to reach the Beomaster.
Of course (a) this might all be rubbish, and (b) it doesn’t explain the ‘correct’ behaviour at times when two ML link products are connected.
Location: UK
Favourite Product: Beolab 3000
My B&O Icons:
