Forum Replies Created
-
AuthorPosts
-
17 May 2026 at 20:50 in reply to: cd6500 unable to propery adjust laser mV (and other issues) #123645
TK
BRONZE MemberJust an update to close this out – after a few days of taking the laser apart and reassembling, and making several adjustments, it appears to be working now. Near as I can tell, the laser assembly was at some point jarred and was unable to travel through its full range of focus. The act of disassembly/reassembly has freed it, and now it works properly. This has also resulted in fixing the issue of R3142 getting hotter than usual. I’m still wondering if there are other weak components on the Servo board, but I’ll take the intermediate win and call it good for now.
Just a comment with respect to what I’ve seen elsewhere and on other more experienced channels with Philips repairmen – adjusting the Laser and focus pots are fairly straightforward if you have the proper tools to measure the results. As a general piece of advice I’ve discerned- if you don’t know if the system is set properly, start in the counter-clockwise position first for the laser power, and sssss-lo00000ow-ly tick it to the right, just a slight nudge of a few degrees at a time, and allow the reading to stabilize before making further adjustments.
Also a curiosity, I discovered that some working Philips laser components and servo boards are occasionally worth considerably more than the cost of an entire Beogram CD player. There’s a real fondness for the TDA1541A among enthusiasts, who praise it for its “analog-ness”. I had not considered this when I first started fiddling around with these players. It’s akin to “buy the stylus cartridge, and get the turntable for free”.
TK
BRONZE MemberMy understanding is the same as @Madskp – there is no “on-off” single voltage signal as there is on a Powerlink system.
If I have time tomorrow I’ll check and see if the 3500 will respond to a few commands sent via Datalink. I’m now wondering if I mis-remembered activating it using Datalink, or a Beo4, and then just mistaking the data as being a relay of Beo4 commands from the 3500 over MCL2. The talk about needing the timer to be active makes me think it is not programmed to respond to all generic MCL2 commands via the Datalink pin.
That said, since the 3500’s IR channel is also MCL2, if my experiment fails, there’s probably a way to inject incoming Datalink signals via the IR gateway – without scouring over a schematic, Id imagine thats probably more trouble to engineer than it’s worth.
TK
BRONZE MemberJust based on my own limited experiments, the 3500 does decipher and respond to Datalink 86 (MCL2), at least to an extent. Penta status updates seemed to provide 3500 screen updates. and I think I recall an On/Off trigger. At this point I stopped looking at it. Also of note, there is no “5V” injection option here, as there does not appear to be an “active” pin or similar that one sees on a proper Powerlink speaker. So to have any chance to wake up the speaker via ML/MCL, one would need to address it appropriately- for example using a properly formatted MCL2 command.
In my limited testing, I seem to recall that I could send an MCL2 signal to turn it on and off, and update the source on the screen. I don’t recall if I could send MCL2 that would manipulate the volume. I spent a total of 10 minutes on it, so my memory may be a bit hazy.
All that being said, I do not know which 3500 firmware version- if any- is coded to respond to a signal to control ALL of it’s features (On/Off, VolLvl, Mute). The 3500 I have at the shop is on FW 1.0, so it may fall into the “not yet implemented” category and not indicative of the later variants.
TK
BRONZE MemberI’m restoring another 5005, and I elected to try another technique for retrofitting a TR11 BC547 transistor into the datalink path of PCB1.I started with a new BC547 transistor I bought from Mouser. When looking at the flat face, the pins from left to right arre (C) Collector (B) Base and (E) Emitter.I unsoldered R42 on the side nearest the I/O cable, and drilled a small hole 2-3cm from it, taking care not to pierce any existing traces, or the adjacent R45 resistor.Next, I took the BC547 and placed the (C) pin through the vacant R42 hole, and the (B) pin through the newly drilled hole. I bent the (E) pin towards the R42 resistor.Turning the board over, I unsoldered the jumper adjacent to R30, and squeezed a 10K resistor through the hole. Theere was just enough room to have both the resistor and jumper in the same hole, which I resoldered in order to make a permanent connection.I covered the resistor lead with heat shrink, and soldered the end to the (E) pin of TR11. This heat shrink is just a security blanket to prevent future shorts on the board.I finished with attaching the TR11 (E) pin to the R42 resistor, and covered the end with a piece of heat shrink. IMHO, this looks much nicer than the other solution.TK
BRONZE MemberDo the two red LEDs on the volume bar light up when you turn the knob, and you just don’t see any green volume level indicators? Or do you truly see nothing at all – including the two red LEDs – when you turn the volume knob.
What if you play a tape, and hit the FF button – do you see the lights strobe in one direction?
What if you try to set the bass level – anything light up then?
The volume knob has two inputs, as you have discovered. The micro switch’s role is to simply let the processor know that the knob is being turned, and which way it’s turning. This alone would trigger the two red LEDs. The green LEDs signifying level are controlled by the optic sensor.
If the LEDs dont illuminate when you hit FF (or bass or status), then Id venture to say that your issue does not lie with the wheel sensors, but elsewhere in the circuitry.
If they otherwise light up given the inputs above, but you are not even getting any red LEDs when you turn the knob, I’d take that to mean that the CPU is for some reason not being told that the knob is turning via the microswitch, and then you would likely not get any green level LEDs displayed anyways. The microswitch basically facilitates a pull-down of the pin to ground, and that is fed directly into the CPU, so if it has continuity then there’s not a whole lot that can go wrong, apart from the possibility that its not grounded properly.
If the two red LEDs do illuminate, but you are not able to adjust the level, then that point to the opticoupler circuit,which contains a few transistors and an opamp in addition to the opticoupler, which can also be a possible failure piont..
11 April 2026 at 15:57 in reply to: Connecting a BeoMaster 5500 to a Beolab 2 subwoofer and Beolab 3 speakers #123278TK
BRONZE MemberI don’t know that Sounds Heavenly sells to anyone outside of Europe, just based on his site. It does sound like you have a few skills with a soldering iron, so you will likely be able to fashion something together that will work.
I have a topic that touched on some of the information you seek, which likely could benefit from a bit more clarity on how to accomplish the task of adding Powerlink to a BM5500. There are other discussions as well. I’ve included the link below.
Do you have any unused source receptacles on your BM5500, apart from Phono? If yes, then you’ll have access to pretty the audio and control signals you need to make a Powerlink output – although I have not researched whether the “sensor on” pin will work as a “power on” signal. There may be one or two signals that will require you to add a jumper cable to the BM5500 I/O board in order to have it work properly.
The process I was considering in order to prototype the Powerlink output was as such:
- Buy a fully wired Din-8 cable
- Remove one end plug
- Strip back the cable cover 6-12″
- Attach pins to all the individual wire ends (using barrel-style contact pins from Amazon)
- Insert the individual ends into the appropriate pin locations on the BM5500
- See what happens
I’ll give this a try next week and post results on the thread below, with the exact pin-outs that I used.
TK
BRONZE MemberMore “remote” work – today it’s a Master Control Panel 7700, which may have been living in a moldy attic for a few decades. Seems to mostly function, with a few non-working buttons. I thought I’d try my hand at ribbon replacement, given the crusty and brittle original ribbon cables. I did the easy one first, just to see how it would go.
On to the more complex cable controlling the LCDs … big mistake. One dead LCD later, I concluded that there’s no obvious way that I can see to replace the connection to the LCD screens except to splice into the existing ribbon cable. The LCDs seem to be connected to the ribbon cable using some sort of random membrane that I cant make sense of. Oh well – thankfully this was just a poor-condition unit I acquired to verify the MCL output, which still works.
TK
BRONZE MemberThanks for the document, @pl212. You’ve probably seen the MCL’82 protocol document (attached) that I uploaded a few months back. It represents the final variant of MCL1 before the release of MCL2 (Datalink ’86). There was almost no documentation that I could find when I assembled this protocol document, which was created mostly by me spying on the messages being passed between a Beomaster 5000 and MCP 5000. There are still a few straggler messages whose meaning I have yet to fully decipher, which I hope to get to some day.
I recently acquired an original MCP, designed for use with the Beocenter 7700 (which I don’t yet have). Just based on the jumpers I see in the 2041 relay boxes, I’m thinking the MCP instruction set is unique to the 7700 – or at least the response messages will be – but I’d venture to guess there will be some overlap in the command set between the MCP and MCP 5000. Having just the MCP, I’ll be able to verify outbound commands for starters. If you happen to have a Beocenter 7700, perhaps you can add to the knowledge-base by providing the responses for the documentation.
I’m in Marin, so we’re close by each other, and can get together to compare notes over lunch, if you’re interested.
Attachments:
You must be logged in to view attached files.TK
BRONZE MemberThere’s a nice project on GitHub called Beomote which is along similar lines to what you are looking to do, and might help get you started.
As to potential hurdles, if you are only looking to do one-way stateless with a URL callable interface (for example), your life will be much simpler. A 2-way application will need to remember some semblance of system “state”, and occasionally have to sync its internal state condition with whatever system its controlling. B&O provided a “status” query in the early 2-way protocols, which makes things a bit more manageable, but the entire “state” of the Beomaster is not queryable all at once, so you have to keep careful track of the sporadic incoming status messages to keep track of where things stand. Something to consider during design.
For fun, I’m working on a project I call BeoBabble which facilitates 2-way comms between the early pre-Masterlink units, and runs on an Arduino. I had to shelve it for a while as it was taking up a bunch of time, but I plan to dust if off in a few weeks time when things calm down. At some point I’ll add an IR interface, because it appears to be the same decode/encode pattern from what I can see, but that interface won’t be available for a while. I only mention it here because Beo4 is straight Datalink ’86 in it’s most basic form, which is one of the early protocols BeoBabble supports. If I can be of any assistance in that specific arena, I’m happy to help.
TK
BRONZE MemberA Beolab Terminal that I bought for $50 had lost a battle with a glass of some sort of sticky cocktail. Half the buttons were non-responsive, so I took it apart and bathed the components in Iso. Luckily all the traces were undamaged and tested fine.
Everything looked and worked great after re-assembly.
I still need to re-tape the button pad. The original is very much a one-time-use material. Does anyone have a “favorite tape-medium” they use for this purpose? I was just thinking clear or perhaps thin black packing tape would work fine, and provide a bit of protection.TK
BRONZE MemberReceived a complimentary Form1 with another purchase, it the usual condition – without foam. After reading the archives on the issues everyone was having with the original foam, I bought a cheap set of Logitech 150 foam replacements for $10-for-2-sets, and affixed them with trim adhesive. Not ideal nor exact replacements, but serviceable given the time and effort I was willing to put into it. If someone ever has a better solution, I can always shave them off. Unit seems to work fine without the upper cushions, but then, I’m not overly concerned with comfort, fit and finish of this particular headset. Hopefully someone else can find this information useful to repair their sets without foam.
TK
BRONZE MemberJust to document the needed changes to add discreet “Play/Off” function to an early Beogram, these are the steps.
The “Play” button is fixed in place with a black bracket, which holds the button in the appropriate place on the front panel.
It’s wired directly to the “Play” button on the top surface, so it only can perform the same function as the “Play” button under the cover. The large PCB3 is removed by carefully moving the 4 black tabs that hold it firmly in place, and wiggling the PCB up and back out of its mount.I was surprised to see that these buttons were exposed – typically, they are covered with black tape to help hold them in place (and probably also to keep moisture and debris out from them – they are a slightly cheap design, and can easily be made inoperable with a bit of contaminant). I fixed the vulnerability by adding a bit of electricians tape myself. Next, I severed the connections of the small PCB, and added two additional wires to it, per the new design specification.Last, I ran these new wires back through the cover, using the same clamps used for the existing wires. A bit of trimming later, and everything was hooked up per the late-model specifications. A fairly straightforward modification.I’ve elected to not add an RIAA to this unit, as I need something I can use to test with earlier variants of Beomasters with built-in RIAA. So this unit is upgraded as much as it can be, and ready for work.TK
BRONZE MemberI took delivery of another late-model PCB1 control board (with the discreet Play/Off hookup), so I decided to replace PCB1 on my 5005, and do a bit more analysis of this late-model feature.
This additional feature basically provides continuity over the component range, as compared to the earlier Beograms where the button was a mere extension of the “Play/Repeat” button located inside of the cover. The original Datalink status sent by the original Beogram 5005 thru 5500 was “Play/Repeat” is a single Datalink command “Beogram.Status.Playing” when first pressed. Subsequent presses of the “Play” button put the Beogram in ‘Repeat’ mode, and were handled without sending any additional information back to the Beomaster. In fact, this was a missed opportunity by B&O to send a ‘Status.Counter’ to update to the MCP on any ‘Status’ request, showing the number of queued repeats – for example, the Beogram could easily have been coded to send “Beogram.Status.Counter ‘C 03’ “, reporting back to the MCP screen the number of record plays remaining – a trivial code addition which could have provided some visual feedback to the listener as to the number of repeats remaining.
Conversely on the late PCB1 board, the pressing of the front button while the Beogram is playing sends two Datalink commands: “Beogram.Status.Standby”, followed a few seconds later by “Beogram.Status.Stopped” when the platter stops spinning. Sending the Standby command will cause the Beomaster to act accordingly.
If I ever find the time to create a replacement microcontroller for the Beogram, I’d like to add a feature-set which provides more status reporting to the listener. Repeats, song count (based on 3 seconds of silence, for example), 33/45 selection via the MCP, and things of this nature would make excellent upgrades to the base system.
TK
BRONZE MemberOn to the final steps – finish routing the wiring, and connecting the RIAA. The original wires ended up being just a bit short to wire around the underside of the board as I would have liked, but at this point I didn’t care – I wanted to see if my upgrade had worked!
With the wiring complete, I re-calibrated the board based on the service manual (recall, I had swapped out the original 5500 board with a later board that had a discrete “Play/Off” feature, like the Beogram 7000).Moment of truth! Triple check to make sure everything was as-planned, and hook it up to my Beomaster 7000. Everything worked as expected – Lovely! Special thanks to @adyan for making a few RIAA boards for this project. I have no doubt the TX-2 will work as well, but I’ll go through the steps to document the process.TK
BRONZE MemberOn reading, re-reading, and re-re-reading the latest version of the service manual RIAA schematic, I came to the conclusion that the “Old Version” PCB 11 would need a modification in order to electrically emulate the “New Version” mute circuit. The original PCB11 is wired such that LG and RG from the stylus are not connected to chassis ground or shield ground until the wiring reaches the Beomaster. Further, the mute circuit is implemented by grounding the L and R to LG.
New boards designed for dual use as RIAA or non-RIAA implement a sightly different protocol, which necessitates the cutting of a wire bridge between some of the solder pads to achieve the desired circuit. Also, the LM and RM wires work a bit in “reverse”, where the mute circuit acts to ground the amplified signal on mute activation, before it reaches the output cable. The only way I could see to mimic this implementation was to grind a cut on the PCB itself, isolating L and R from the original mute circuit. [EDIT – I’ve made a small change to the schematic, and included both versions for comparison]
Original Version combines L+ R during ‘unmute’ – potentially undesirable:
Final Version – isolates L&R outputs during ‘unmute’:With that mental hurdle cleared, all that remained was to wire PCB11 with a jumper between LG, RG, and chassis ground, which meant that the mute circuit was now also connected to chassis ground. I considered that LM and RM are really the same signal and could actually just be activated together using a single wire [EDIT – I’m not actually sure this is 100% true in all scenarios, although it did appear to function correctly], but I went ahead and wired a separate LM and RM to the mute switch, per the schematic. [EDIT – even though the Original Version worked as wired, I realized later that I’d connected L+R in a way that might lead to some odd behavior when unmuted, so I moved one of the channels to a new position, where they would be isolated during ‘unmute’. The original wiring solution didn’t seen to affect the performance of the circuit, but the final version is representative of the original schematic] With L & R inputs reattached in their original spot, I was set to finish wiring up the RIAA.Original Version:Final version:Admittedly sloppy, but it all toned out properly, so I left it as-is, and re-installed PCB11.TK
BRONZE MemberI decided I’d upgrade the 5500 first, on the thought that the wiring would be a bit easier. This proved to not be the case – B&O supplied the original output cable with an extra unattached blue wire, which was not connected to pin 7. I made the decision to disassemble the Din connector to attach it. This is strictly not necessary for my planned use, but I wanted to observe the convention that “Beograms with RIAA run Datalink on Pin 7”.
Upon disassembly, I found that not only was the blue wire not attached, it was truncated to the point where I’d have to un-solder all the pins and re-cut them to the new length. This is fiddly work which I’m personally not terribly fond of. I just happen to appreciate the coolness of a removable pin 6 and 7, and want to preserve that feature. I wired up both pin 6 and 7 with the blue and yellow wire. Without thinking about it first, I moved the yellow wire to pin 7, and soldered the blue wire to pin 6. Inside the turntable I’ll have the blue wire available on pin 6 for a future new project I’m dreaming about.
After a bit of squinting, cursing, and double checking my work for shorts, I was ready to reassemble the connector. Then came the “one-way” step of snipping the cable at a point I thought would provide enough wire on either side of the RIAA card to connect everything together using the original wires.
TK
BRONZE MemberI’ve used both Vishay 47uF 25v (MAL202136479E3) and 33uF 16v (MAL203035339E3), and both single-cap changes alone have restored the individual players to full operation. I can’t speak to whether these are the best brand/model choices, or whether a 47uF provides better tracking, but some have reported better results using a 47uF, saying that they are better equipped to read more modern discs. This has all been in the last year, so I have no longevity data.
I also don’t have a list of “while you’re at it” parts swaps, which would be a nice thing to have, if others have a list.
TK
BRONZE MemberNext step is adding a power plug for the RIAA amps I purchased from adyan. His design mimics the original RIAA boards used in the 6500-7000 models, and therefore also needs a 22V and 12V supply, which it gets from the transformer on a plug from PCB2. None of my US-Spec TX2 transformers – early or late models – have this 2-pin plug, so I had to tap into the PCB at the correct spots. Here again I contemplated drilling PCB2 to add a surface-mount plug. And once again, for simplicity I opted to add a pre-wired 2-pin connector instead. I attached the red wire lead to the existing 12V wire hookup (post IC), and the black wire lead to the 25V output from the rectifier. This way, Red would consistently be the 12V supply. The plugs are male/female, so there’s no way anyone could accidentally feed a 25V input to PCB1 ground by mistakingly hooking up the incorrect plug.
With these straightforward updates completed, I’m ready to tackle installing the RIAA board. I’ve opted to upgrade my 5500 and TX-2 simultaneously, in order to teach myself a bit about both upgrade paths.TK
BRONZE MemberHere’s a “Old vs. New” 59XX schematic connecting the CPU to the Datalink bus. The new schematic includes a 547 transistor and 10K resistor hardwired to 5V, so it will be active as soon as the Beogram is plugged into power.
OLD SCHEMATICNEW SCHEMATICIt turned out to be a fairly straightforward process adding a transistor to PCB1. I took a 547 equivalent transistor, and soldered a 10K resistor to the B pin, and added a bit of heat shrink to prevent a short. Next, I repositioned R42 by removing the Datalink bus leg from the board, and soldering it to the C pin of TR11. Last, I placed the TR11 E pin into the now-empty hole which previously connected R42 to the Datalink bus, completing the circuit. I contemplated drilling holes in the board and routing the wire underneath the board, but in the end my eventual solution was much simpler to execute, and I think it turned out looking OK – the parts are basically in the same spot they would appear in a later board, so it will be simple enough to understand what the retrofit’s purpose is. This is a picture from a 5005 board I had retrofitted earlier:
TK
BRONZE MemberWith the Beogram power supply, the story is much the same as the main PCB – the supplies all have the same basic capability across models, but depending on the model and region, the way they were wired varies slightly. With the deployment of an On-board RIAA of the 6500, it became necessary to power the IRAA via two power feeds from the PS. This necessitated the inclusion of a small 2-wire pin to the PCB, from where the RIAA could be powered
Of the US-based TX-2 that I’ve seen, it appears that both early and late examples utilized the power supply setup as seen below, irrespective of which generation main PCB was installed. This supply was wired for 120V, with a large fuse taking up much of the PCB #2 real estate, and no support for an RIAA hookup:
Later Euro TX-2 examples appear to have the 2-pin RIAA hookup, as shown here (photo 1 supplied by adyan, who has extensive knowledge on RIAA for these systems, and has supplied me with a pair of boards for this upgrade)Here is a picture of a BG 6500 PS, which resembles the example that adyan has in his late TX-2, and also has the 2-pin power hookup.:These 2-pin RIAA hookups draw from power points which are readily accessible from any of the TX-2/5500 ps, but it does require a bit of retrofit work to tap into them. My plan is to solder a plug onto the board that will allow access to the same power that the boards with built-in RIAA hookups have. On the board below, soldering a hookup to the bus leading to pins labelled 1 and 3 (center of board) of the IC I/O will give the needed result of having a 22V and 12V supply, respectively. -
AuthorPosts