BL 3500 MCL ON ticking noise

[Lucas Monet]

Hello,

I tried to set my Beolab 3500 mk1 into MCL mode via my beo4.

Done easily with “menu 0 4 Go”

But the speaker seems to be faulty because ticking noise starts immediatly and is accompagnied with a permanent bzzzzzz noise.

If I connect the speaker with ML cable, I have no sound problem.

Do you have an idea how to fix this ?

Thank you in advance

 

[Madskp]

Lucas Monet wrote:

But the speaker seems to be faulty because ticking noise starts immediatly and is accompagnied with a permanent bzzzzzz noise.

That sound like normal behaviour when using the test mode if the BL3500 is not connected to anything. For good measure I just double checked with one of my own BL3500’s and it does the same too. Not very loud though.

Lucas Monet wrote:

Do you have an idea how to fix this ?

I would expect it to go away if you connect something to it. What are you trying to achive?

The Menu + 0 + 4 + GO solution is not very good both because of the cumbersome way to active it + no volume control, and the speaker will go into standby if you press a button on the remote.

A more elegant solution was found in another thread where a 1611 converter connected via Masterlink give two remote controlled inputs to the BL3500. User Matador made a great setup drawing of this concept in this post https://forum.beoworld.org/forums/topic/beolab-3500-and-1611-converter-settings/page/22/#post-42623

Other alternatives are also mentioned in this post https://forum.beoworld.org/forums/topic/bl3500-and-the-mcl-pl-connector/#post-44537

Hope this helps

[Lucas Monet]

Hello,

Thank you for your reply. The ticking and permanent bzzzz are loud in my case. If I connect my 7pin din to jack adapter, the sound is still there and ruins the experience. Even with max volume on my phone, these annoying noises are still audible.

I would like to use the bl3500 has a standalone speaker connecting a bluetooth receiver to the 7pin din-jack adapter.

Anyway, It is not possible to stay with these annoying noises when im not playing music.

[Madskp]

Are you using a standard 7 Pin DIN to minijack adapter or one that is made for a Beolab 3500 MK1?

The reason for asking this is that the wirering of the adapter is different and could affect what you are experiencing

[Lucas Monet]

I tried with a generic 7pin din to mini jack (not made specifically for b&o products). But tic tic and bzzz noises are there when nothing is plugged in too.

[Madskp]

Lucas Monet wrote:

https://forum.beoworld.org/forums/topic/bl3500-and-the-mcl-pl-connector/#post-44537

Then you are most likely missing the ground connection from your bluetooth adapter. You can see the difference in pinout between the cable for a Beolab 3500 MK1 and MK2 (most likely the cable you have) in number 2 post in this thread https://www.hifi4all.dk/forum/forum_posts.asp?TID=32157&PN=1&TPN=30

The specific cable for the Beolab 3500 MK1 are sold by several sellers including one of this sites sponsors Sounds Heavenly https://soundsheavenly.com/airport-express/155-2344-ipodtvairport-express-to-beolab-3500-mk2-cable.html#/2-length-1m/62-beolab_3500_version-mark_1

This will still have the limitations mentioned in my earlier post

[Lucas Monet]

Hello,

I have one 5pin to jack and one 7pin to jack. Non of them solve the ticking noise when plugged in. No music with the 5pin but working with 7pin cable (sound in addition to the ticking noise).

I checked many videos and posts, no one seems to be annoyed with this sound when the din is plugged out. I dont want to buy another cable if the problem comes from the beolab itself.

Record of the ticking noise : https://recorder.google.com/3fe53683-49a2-428d-9450-ebf3b39909b2

https://www.hifi4all.dk/forum/forum_posts.asp?TID=32157&PN=1&TPN=30

Here, the post deals only about 5pin din to jack. That’s not what soundheavenly mentionne in his video.

I could verify if the 2 gnd pin are connect them together to see if the ticking noise stops ?

Next move will be the recycling center 😞

 

 

[Madskp]

Take a look at this thread

https://archivedforum2.beoworld.org/forums/t/35714.aspx

The problem sounds like the one you have, and at some point the original poster confirms that he used a wrong cable to start with, and the right cable solved the problem

[Author]

Posts