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
matador43: Weebyx, I've installed CT 6.00 and changed the USB port (it then detected new material and installed beo5 driver). But unfortunately the same problem remains. "Battery too low"…
Weebyx,
I've installed CT 6.00 and changed the USB port (it then detected new material and installed beo5 driver).
But unfortunately the same problem remains. "Battery too low"…
Damn. You are really unlucky here. And this is the same issue with both remotes ?
I would be happy to try to get them back to life for you, but that means sending them to Denmark.
/Weebyx
Yes, I think so too!
The new, overnight charged battery shows up as discharged on the silver remote (the one working but with unresponsive screen).As you previously said that update may drain a lot batteries, I'm not worried still. I've put it in charge through the power adapter.
In the meantime, thank you for your offer: I will check postage rates and let you know.
Regards,
M.
I apologies if I post too much frenetically but "I want to believe" .
UPDATE
I've been charging the battery through the silver remote until it shows as fully charged.
Then I tried to update with CT 6.00. It goes until firmware update where it stopped after various bips indicating USB reconnection and reconnection.At the same time an alert telling a new material was detected pop up and the arrows gone red. The remote was left with the same "no valid config" message as the gold one.
So I trusted the OS and installed the proposed driver.Thats where interesting things starts to happen again. The remote was for the first time seen are a Beo6 and not as previously a Beo5.
In CT 6,00 I created a new simple config and tried to upload it again and it works!. The screen is still unresponsive but it display the config name I choose.
I quiclky swap the remotes and tried again with the gold one but no luck, the "low batt" alert came again.
I'm now charging the battery with the wall charger again through the Gold remote to see if the miracle happen again.
A little bit of hope at least. To be continued!
And… It… Works !!!!!
I first really want to thank you Weebyx again for your constant encouragement and advices, pushing me to try again!
And of course to Mike who did this possible!
Well, details:
After putting the remote to charge with the adapter I tried to update with CT6.00.
-Fisrt step went well as usual,-Second Step: BeoLO did went through without battery alert.-Third step was uploading configuration, went quick still no alert.-Fourth step was Wifi Firmware where i finally could see the 8 bits Weebyx was referring to. It did stuck for a little while but went through once again.-there was a fifth step i dont remember the name which was not the longest in real but the longest in perception until the "Done" button did finally highlight.
The name I choose for the config appears on the menu and I as able to start my Beocenter 6 and even drive the Apple TV hooked in the back of the set.
The screen seems to respond even if I feel like a little lag in the commands.
I can't say how great that forum can be. I won't say thank you again because you guys must be tired of reading it but Merci to everyone who supported.
Now lets put back all the remote guts into their housing and start playing with programming, xml's, and tiny pictures files!
matador43: And… It… Works !!!!! I first really want to thank you Weebyx again for your constant encouragement and advices, pushing me to try again! And of course to Mike who did this possible! Well, details: After putting the remote to charge with the adapter I tried to update with CT6.00. -Fisrt step went well as usual,-Second Step: BeoLO did went through without battery alert.-Third step was uploading configuration, went quick still no alert.-Fourth step was Wifi Firmware where i finally could see the 8 bits Weebyx was referring to. It did stuck for a little while but went through once again.-there was a fifth step i dont remember the name which was not the longest in real but the longest in perception until the "Done" button did finally highlight. The name I choose for the config appears on the menu and I as able to start my Beocenter 6 and even drive the Apple TV hooked in the back of the set. The screen seems to respond even if I feel like a little lag in the commands. I can't say how great that forum can be. I won't say thank you again because you guys must be tired of reading it but Merci to everyone who supported. Now lets put back all the remote guts into their housing and start playing with programming, xml's, and tiny pictures files!
Great to hear they are back to life. This is why a lot of remotes that "dies" and are sent back to B&O for fixing, ends up with a new screen instead of just fixing them. It is a matter of fails and tries before the right combination of stuff is there. And a lot of times, even a new screen will not fix it if it is not running the latest FW.
Before you spend a lot of time, get them back together, and now they are alive, do the update with 6.84. It contains the latest FW that fixes the "dead" bug you have just experienced. So create the dummy config in 6.84 and do the update, it will update FW again, and maybe WiFi ;)
Weebyx: …do the update with 6.84. It contains the latest FW that fixes the "dead" bug you have just experienced.
…do the update with 6.84. It contains the latest FW that fixes the "dead" bug you have just experienced.
Done! The remote SW is now 3.40a. Updates seems to be flawless now.
matador43: Weebyx: …do the update with 6.84. It contains the latest FW that fixes the "dead" bug you have just experienced. Done! The remote SW is now 3.40a. Updates seems to be flawless now.
You will probably never have issues with them again :)
Hi guys,
So, I just got myself a Beo6 remote. I wish I had read this forum BEFORE I started playing around but hey-ho, nothing I can do now.
Powered on unit with (nearly) dead batteries. Programmed/updated firmware using CT 6.84 -- working fine.
Went to change the config file, CT said writing 0 bytes and then I looked at the display --- absolutely dead/blank screen :(
Came to realisation that batteries needed changing... got new batteries, took unit apart to replace. Installed but batteries but they only have about 1.31v in them.
Batteries obviously do something, since when on the dock the little red light on the back turns on - but (assumed) not enough power to wake it from deep sleep.
Looking for specs/help to charge the batteries and get this little remote alive again.
Also looking for a copy of CT 5.12 as I have 4.11, 6.00 and 6.84... and I don't think 4.11 was compatible with Beo6
@Weebyx, did try to send you a couple of messages as the seasoned expert in these matters :)
Any help anyone can provide is very much appreciated... Currently remote all in bits awaiting charged batteries :(
Cheers all :)
So now it is me who is experiencing weird sh... with 2 Beo6's.
One will not load configuration, just shows "No configuration", and when trying to upload, it is stuck on BeoLo writing. The remote disconnects the instance the BeoLo starts, and reconnects, but BeoLo is never written.
It connects to 6.00, 6.62 and 6.84 fine, and under settings it shows 3.40, but BeoLo and animation is missing, and also serial number ? Very strange.
The other one, works fine, and has latest FW and BeoLo/Wifi/Animation is correct, but it will not accept and charge the battery, no matter how long it is in the charger, when removing from charger, it shows a dead battery in info, and powers off after a few seconds. I am sure the battery is fully charged, and have tried all batteries from the other remotes I have, I have also tried with a new flex cable between button PCB and display PCB, just in case there is something wrong with the sensing of battery voltage, but still no success.
These remotes are very weird sometimes :)
Weebyx: So now it is me who is experiencing weird sh... with 2 Beo6's. One will not load configuration, just shows "No configuration", and when trying to upload, it is stuck on BeoLo writing. The remote disconnects the instance the BeoLo starts, and reconnects, but BeoLo is never written. It connects to 6.00, 6.62 and 6.84 fine, and under settings it shows 3.40, but BeoLo and animation is missing, and also serial number ? Very strange. The other one, works fine, and has latest FW and BeoLo/Wifi/Animation is correct, but it will not accept and charge the battery, no matter how long it is in the charger, when removing from charger, it shows a dead battery in info, and powers off after a few seconds. I am sure the battery is fully charged, and have tried all batteries from the other remotes I have, I have also tried with a new flex cable between button PCB and display PCB, just in case there is something wrong with the sensing of battery voltage, but still no success. These remotes are very weird sometimes :) /Weebyx
One remote fixed, it was actually a problem with the flatcable, tried with yet another from a known working remote, and now it will accept charge and battery status :)
"No configuration" remote, still has to come back to life.
Hi
I have the same problem
Sent you an email as well but i am not sure you received it
I got a beo 6 from a friend from Belgium , it was working when he shipped it but when i got it , it was dead
i said batteries died and ordered new pack . After installation it is still dead . when i plug it in my laptop it recognize it but it says it needs a driver update . how can i find it ? my actual driver is 1.1.10.0 from 27.04.2012. Can you help please what should i do to get it back working?
Thanks
Regards Petri
Which configuration tool are you using?
Stoobie