link

But unfortunately the commands only startup the BM in muted state and I can´t get it to unmute

Hi! Maybe I can jump in here. Was busy with ML lately and haven't had a deep dive in the  DL'86 protocol yet. What I would try first is just sending it a virtual volume or mute key stroke. So similar to this But instead of the 0x09 at the end (digit-9) give it a try with 0x60 (volume up) or 0x0d (mute toggle). Maybe it will then leave the muted state it started up with.  

Hi,

I'm not too familiar with the DL'86, as my projects uses DL'80.

The easiest way to achieve control of your BM6500 might be to send the control codes over IR, that way you can just duplicate what your remote is sending.

link

But unfortunately the commands only startup the BM in muted state and I can´t get it to unmute

link

But instead of the 0x09 at the end (digit-9) give it a try with 0x60 (volume up) or 0x0d (mute toggle). Maybe it will then leave the muted state it started up with.

Did a quick test run today. I wasn't able to get it out of the initial muted state as well when started through DL'86 commands. By commands on the Audio Aux Link connector I mean. As soon as you touch a key on the remote or on the device directly it will unmute. Sending virtual volume keys works and you can see the volume on the device is changing. Nevertheless it stays muted. The 0x0d mute command is ignored and does nothing. Maybe there is some kind of hidden command somewhere to enable the output but I couldn't find that yet. So if you want to stay with the cabled version maybe just try shorting the DL80 and the DL86 pins together. Then you can send a DL80 switch on" command (which doesn't mute the unit by default) and then switch over to DL86 for having the convenience of a more advanced protocol. Looking like sending DL86 commands into one of the DL80 connectors does trigger nothing. So any additional unit connected there might just happily ignore it. At least worth a try.

link

Please start a new thread in order not to “hijack” Pilatomic original thread.

Sorry this was not my intend! I started a new thread . But thanks for the input anyways, much appreciated!  

Received my Beotooth 5500 kit in the mail today and have assembled it.

First test om my BM 7000 was impressive. Connected with my iPhone on bluetooth with no problems.

As player I've tested both my iPhones own player and the spotify app with success and could control the playlist as Pilatomic have shown in his videos.

Thanks Pilatomic for a fantastic project. It gives the tape input on our beloved B&O systems a new life :-)

 

/steffen

I have also received mine now and got it up and running.

Very nice and very good quality. and attention to detail for easy assembly.

I have testet it on both a Beosound Ouverture (Tape2), a Beomaster 4500 (Tape1 and Tape 2) and a MCL2AV (Tape), and from my little testing it seems to work flawless with the Beotooth 5500 activating all of the above when playing music from my phone, and also all of the systems being able to control the music (start, stop and skip) via the B&O remote and local control on the music systems.

Based on my little time with it till now I can only reccomand it.

Thanks to Pilatomic for making our old systems even more usefull :-)

 

I received mine almost two weeks ago, here's finally my two cents on the product (it's awesome!).

Here are the contents of the kit waiting for assembly:

Login to view image

The assembly is described in detail in the supplied manual. Basically it's just soldering the cable (connector and PCB) and the LED and fitting it all inside the case. If you have never soldered a DIN connector it can be a bit tricky at first but that's really the hardest part. Using a small flat-top LED and a custom 3D-printed cable holder / strain relief really shows the attention to detail of the kit (fun fact: during playback the LED flashes to match the real Beocord's track indicator).

 

Login to view image

The finished product has a very B&O'ish style (perhaps reminding of the LC1 with a silver top and a black plastic case).

 

Login to view image

Here connected to my BM7000's TAPE1 and showing the time display real-time on the MCP6500. I have a weak spot for the 2-way remotes and I really like how the Beotooth supports that! (This also lead me to finally building a new battery pack for my BL7000). I am also hoping to experiment using the Beotooth over MCL2 in a link room (with 2-way comms).

I had prompt replies from pilatomic and he even made two firmware updates regarding some small things I observed in my testing (difference between STOP and PAUSE commands in certain situations and a small issue with rewind/fast forward commands), so customer support was also really top notch. Also a note that not all apps that control playback over Bluetooth are not created equal (my phone's default media app had inconsistent issues with playback controls working or not whereas my MacBook+iTunes always worked flawlessly).

This is a very useful little addition to any Datalink-equipped BM/BC. While using a Bluetooth receiver for audio on a vintage system is nothing new, the Beotooth does it well and the seemingly small addition of Datalink commands really makes it feel so much more integrated. Especially on pilatomic's level of detail on everything.

I hope we will see more DIY-projects utilizing the Datalink bus in the future for something neat that keeps adding to the magic of B&O's truly ageless designs.

I also received the Beotooth 5500 (fully assembled) and am looking forward to give it a try on my BeoMaster 6500!

Regards, Johan

Hello, Quick update for those who already own a Beotooth 5500. Firmware V1.3 is now available, with the following changes :

• Fix playback not resumed when switching from Beogram to Beotooth (I was not processing that datalink command)
• Prevent transmitting AVRCP (Playback control) commands to Bluetooth player when player is not sending audio. This fixes an issue where I was listening music on my computer though the Beotooth, then switched to a headset. A few minutes later, The Beomaster would, rightfully, go to sleep, but that caused a "pause" AVRCP command to be emitted, pausing the playback. "Play" commands are still sent unconditionally, to be able to resume playback.

If you are interested to get that firmware update, contact me via private message. In other news, I am still in contact with Microchip, diagnosing why the AVRCP Browsing feature is not working. Once that is solved, I should be able to support selecting a track by its track number directly.