matador
Forum Replies Created
- Posts
-
Same here with BC2300, BC6 and 1611.It made nothing appart the long press shutdown.
It could be connected to both video and audio AAL at the same time, hence this diagram in the ML handbook.
Of course idiot me. I forget it even if it was this diagram that started the dual input trick.
the PL trigger voltage seems to force BL1611 into audio mode.
Seems logical since this is why a powerlink was fitted to the converter, to “tell” the masterlink source, audio was started localy from the AAL side.
which is only then cleared with a power cycle.
This is less logical. Or maybe not: the converter was meant to be connected to a Video AAL or Audio AAL, but not both at the same time. Then without Y splitting adapter or similar in which scenario would the converter need to revert to video mode after have been triggered by Powerlink?
Whilst a lot of people talk about the 8 pin din being a PowerLink socket we all know that is not really true. It just used the old MCL din socket so that a new module would not need to be designed.
I don’t understand.
Apparently, MCL Beolabs can be started with a 5V trigger voltage. MK2 (or beyond a certain SW can’t). But it is often mentioned that the DIN socket was changed from MCL to Powerlink to comply with Beolink Wireless 1, even if the BLW1 guide say it must be connected through ML and not PL.
So the question is what is this socket, what was it along the evolution of the speaker and what is it for?
Please note that this is just out of curiosity since I now know that the 3500 will never be as better as with a 1611 to drive it!
There seems to exist a ‘converter’
Didn’t remember that one! Thanks Tignum.
A Terminal 5000 can’t be used?
A far as I know Terminal is only for daily operation like source selection and volume control.
OK so Test 7 ongoing – I had to tidy my test setup!
So cute, you didnt vacuum today but you still protected the carpet under the converter and the 2000! 😀
I have no intention of going anywhere near a Wireless 1
Unless SW 3.3 make the powerlink socket behave like we are used to…
That’s a great idea. Between Keith among us and your test report I feel compelled to wear a white blouse to do next tests (aren’t they brownish at B&O?).
Guy two things:
Point 3: maybe you should mention that with SW > 2.1, PC is normally displayed on the Beolab.
Point 5: Beoport + 3500: do the 3500 receive the IR commands and pass them to the computer?
I am now trying the BL3500 with BL1611 and it seems to behave exactly as Matador’s.
Guy, do you have a Beolink Active 1636 (or 163x)?
I was told 163x converter replaced 1611 😉 and I would like to know if it can drive the 3500 as standalone the same way the 1611 does.
I think yours may be SW2.1, whereas mine is 2.0.
One is labelled SW 3.1. The other (the one I use for tests) does not show SW version on the sticker, but I will check it next time I plug it
About the price of 60kWh of electricity.
God, with those price it almost worth moving to your region!
Hi Beitie,
Thank you for sharing your work. May I suggest that you add your pictures in the post by clicking in the little framed mountain, last button in the window where you type your message? Better than as attachement because they will show up in the thread bigger than the little preview of an attached picture.
Thank you.
Is that the same on yours Matador?
I can’t say, you’ll have to wait I replug the whole thing (I disconnect everything after each experience and don’t use it daily). PC shows PC and open the audio/audio port of the 1611.
Just guessing but wasn’t the PC command added for the Beoport or when computers became an usual source of sound? Then it would make sense it shared the V.AUX entry like if it was the audio part of an AV source (sound plus picture i.e computer screen). Maybe related to the beomedia implementation? I don’t know.
It would be interesting maybe to have a little timeline with beosources names changes and equivalent over time?
I have an energy counter plug. I will check if power consumption change between on, muted and off. would be sad and surprinsing that there is no standby mode even if I dont hear any click when the speaker turns on.
A.AUX doesn’t work (nor does PC)
I don’t understand: is it that the commande from remote does not call an audio source?
she doesn’t like the look, and thinks there’s something missing from the middle.
Honestly? she can’t be more right, I feel the same. Just put an iPod on dock or better a cactus in the middle!
One of my first tests will be the BL1611 ‘dual-input’ to the BL2000,
Selectable with the front key!
Congrats on your new toys, may we make the interest to this understated speaker rise, make it the poor man’s Beosound 35…
Burned!
Yes stupid me about ML over PL… Anyway, falling is sometimes discovering.
SO, guys, THREE sources on a Beolab 3500, yes three!
Source 1 from audio input of the 1611 converter.
Source 2 from video input of the 1611 converter.
Source 3 from the PL path “Menu 0 4 GO”. But there is a little background hiss, hopefully from too quick wiring, Steve should tell us.The three sources are working altogether. Of course touching any control on the remote turn off the speaker when on PL mode.
I’ve tried wiring the Matserlink input along with the converter and guess what happened? A “mix” of the two sources of course (Master link from the hack and Masterlink from the converter)!
As for the 5v triggering, I’ve talk with the (sympathetic) guy and tried and it works for him (MK1, which has MCL engraved under the DIN socket), but not for me (MK2).
Unless it is another fault, it’s a quite cheap and not so complicated task to refoam it.
What I wonder is if it would be possible to have a stereo jack to Masterlink wire and then have a third input. Imagine:
A.AUX = Airplay (Multiroom), volume control from the remote.
DVD = Turntable through integrated or external RIAA, volume control from the remote.
“Menu 0 3 GO” = Bluetooth Receiver, volume control from the device (which make sense since it will often be a phone, and the symmetrical to asymmetrical loss will be less sensible because of BT).From my readings in the forum, it allows to the linked device to know when you turn on or alter volume on a master unit like the BC2300, from its local controls, A.AUX.LINK not carrying volume or On/Off information.
Therefore the Powerlink socket just has the data pins connected and no sound pins connected at all.
