ARCHIVED FORUM -- March 2012 to February 2022READ ONLY FORUM
This is the second Archived Forum which was active between 1st March 2012 and 23rd February 2022
hi,
We just have been given/bought a B&O system consisting of Beomaster 5500 and Beo Master Control Panel, plus Tape recorder/player, B&O 5500 CD player (bit broken) and B&O turntable. And the BeoVox speakers of course.
We won't use all of them but the main question is, trying to set up what is working, we keep receiving the message from the Master Control Panel "no contact". Occasionally it worked so we could set the clock which gave it initial connection to the Beomaster. Beomaster works, emote works, speakers work, turntable work (although poor stylus)
We have a remote control that works so we can play music, but the Master Panel keeps flashing No Contact... Anyone any clue what to do to make the Control Panel and the Beomaster work together? Apparently these two form the heart of the entire system; so rather important to find out how to work this...
PLEASE HELP!
There's a few faults that may cause those problems with the Master Control Panel, most of which can be found by a quick search on the forum - search for 'MCP5500 no contact'. It could (for example) be opto-coupler or capacitor related.
But in the first instance, have you tried fresh batteries in the MCP? It's quite sensitive to poor battery charge levels.
(EDIT: Meant to add - welcome to the forum! )
Thank you Guy.
Yes, we had changed the batteries; the system hadn't been used for years, so there were very dead.
In the mean time we've tried several times and things seem to work at the moment. I will certainly look on the forum as you suggested, now that I know what to search for.
Thanks for your help.
Dust on the IR components in the Beomaster front panel.Bad capacitors in the Beomaster front panel and power supply regulator circuits.Misaligned IR receiver filter.Bad processor.
Martin
Thanks Martin.
We think it had to do with the position of Control Panel and Beomaster; they couldn't communicate properly. Problem fixed now!