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,
as some of you know, I have some issues with the touchscreen of one of my Beo5s. So I managed to find a used which when I received it turned out to be a Beo6...
And this Beo6 is also faulty (the seller informed that it could be the battery) so I swapped the batteries around but it did not solve the issue, the screen is still black. Then I thought it could be the 3.30 firmware issue so I downloaded Configuration tool and tried to connect it to my computer.
The problem is that the Beo6 only connects for 1-2 seconds at the time and my computer is saying that the USB "equipment" I am trying to attach is not working properly.This made me think that it could be the connector so I switched this one as well bt it was not the issue (Beo5 now have Beo6 connector and vice versa and both are working fine).
So before I try anything else (e.g. switching the Keypad or once again switching the batteries) I would like to know if anyone has solved a similar issue without replacing the display?
(I can see a red LED glowing in the back of my Beo6, not sure if this means that it gets power from the battery)
Best regards,
Riven
My B&O products: Beosound 9000, Beosound 2300, Beosound Century, Beolab 8000, Beolab 6000, Beolab 4000 x2, Beolab 3500, Beolab 2000, Beolab 10, Beolink Active x2, Beotime, Beo5 x2, Beo4, A9 keyring x2, LC2 dimmer x6 and growing....
Hi Riven,
I have had the same issue with my Beo6 about a month since it left the programming realm of my B&O dealer. I ran to him again with the same symptoms - display dead and a red backlight. What he did was he left it running out of power for 3 days until the battery was empty and then he docked it again and charged it. Problem solved
This could well be the issue that was fixed in later firmwares as it causes the remote to get stuck in bootloader mode (which also prevents it from communicating with the software tool).
The only reliable solution I have found is to remove the battery pack and charge it a little externally to the remote before reinstalling it again. Once this is done it usually allows the remote to power on properly (albeit with the usual "recharge battery" message) and will then allow it to be fully charged using the dock.
Once you have removed the battery, you can charge it a little using a pair of AA alkaline batteries (NOT rechargeable batteries) and a couple of length of fine wire (2 cores from solid core cat5 cable are ideal for this)
Simply lay the two alkaline AA batteries end to end like this:-
- [=====}[=====} +
then strip a little of the insulation off of both ends of both wires, and use the 2 wires to connect the red terminal of the beo5 battery pack to the positive end of the two AA batteries, and the black terminal of the battery pack to the negative end. The reason cat5 is ideal is that it is the right size to be poked into the terminals on the beo5 battery plug, meaning you only have to hold the other ends on the AA battery terminals.
Hold them like this for around 30 seconds, and you should find that the battery pack now has enough charge to start the remote when reinstalled. Charge it fully on the dock, then take the opportunity to update the firmware so that you don't have the same problem again in the future.
Hopefully the above description is clear, but if not please let me know.
Kind Regards,
Martin.