Weird.

Can you try replacing ".negro" with the dot include with "43" all attached?

I have a broken BEO6 and so the docking station is of no use to me.  I would be happy to send it to you free of charge if you send me your address.

That's a very kind and generous offer, thank you.

Email sent.

Good morning Guys,

Some news about the Beo6!

First I want to thank Weebyx for his hopeful help and advices and Mike Muller for his kind offer two posts above.

So! Yestreday I received in my mailbox, direct from Switzerland, not only a Beo5 Dock and charger but also a Beo6 in Silver finish Login to view image.

It allowed me to confirm that my first remote is actually Gold. So far I've found it "Goldish" so I wasn't sure if it was really  gold or just the aluminium who had a light yellow tint:
Login to view image 

After checking the base and charger were delivering 5V which they are, I put the silver remote on the base for a couple of hours.

The silver remote was given as "faulty display". The Gold one problem is unknown so first thing I tried was swap the main PCB.
While the remote was open, i check the battery voltage: 1.2 v which is alf the power needed. Anyway, I assumed that little tension and the dock while made the remote start if it should. But nothing happened!

I'm not worried still as Weebyx already warned me about the deep sleep issue when the battery is too much discharged.

Next I tried to plug it to my computer (MAC) but again nothing happened: no mention of any usb device on the system report.
After installing CT on a virtual Windows 8, I could start the program but it show little arrows cross marked in red which, I believe should stand for "No Communication". Is it?

I've read post about Virtualization, windows 8, 32 & 64 bits and USB3 vs USB2 but I'm not into thoses problems yet and I know it will not be simple.

I suppose next step is to replace the battery. But I'm surprise by the invisibility in the USB bus as I read about remotes which were working on the base even when the battery was dead low.

Does anybody have any suggestion something to check or try. Any help from somebody using a Mac with a virtual windows will be welcome too.

A warm thank you to anyone who will help and again to the ones who already did, very generously!

Yes, the red arrows indicate no connection to a remote.

Does windows find the remote under device manager when you dock it ? The first thing is to just leave config tool closed, and get windows to display the Beo under Device Manager. Sometimes it cannot find the driver automatically, so you just select the remote under devices and manually point driver to the BeoDriver folder under the installation path.

/Weebyx

Weebyx wrote:

Yes, the red arrows indicate no connection to a remote.

Does windows find the remote under device manager when you dock it ? The first thing is to just leave config tool closed, and get windows to display the Beo under Device Manager. Sometimes it cannot find the driver automatically, so you just select the remote under devices and manually point driver to the BeoDriver folder under the installation path.

/Weebyx

Hi Weebyx,

I'll try this later today. As you know, i'm on Mac, so I have to first install a virtual machine on an old Laptop to avoid the USB 3.0 issue I read about.

So far I've tried on a virtual Windows 8.1, with the Keith Saunders workaround about "Driver Signature Enforcement" but on a USB 3.0 laptop and without any success.

Of course all tips and tricks about Windows Use are more than welcome.

M.

Which devices you want to control with the Beo6?

Weebyx wrote:

Yes, the red arrows indicate no connection to a remote.

Does windows find the remote under device manager when you dock it ? The first thing is to just leave config tool closed, and get windows to display the Beo under Device Manager. Sometimes it cannot find the driver automatically, so you just select the remote under devices and manually point driver to the BeoDriver folder under the installation path.

/Weebyx

Ok, I've installed a fresh new Win XP on an USB 2.0 (Mac) Laptop. I've tried to explore de Device Manager without any luck (please see screenshot below). Tried to Install CT 5.12 to see what happen but nothing happened.

One question thought, because I have not replaced the battery yet: Does the battery be healthy when the remote is docked and the USB power supply will power the electronics or do I need to replace the battery first thing first? The battery is 1.2 V over the 2.4 by design.

Thanks.

Something happened !!! 🤩

I teared appart the Beo6 in four part: screen, PCB, dock connector and battery and i fueled the PCB with 2AA batteries (again!), connected all things and docked the connector to the base. As soon as I connected it to the Mac it showed up in the Mac Device Manager equivalent.

Then I tried on my virtuel win XP where it show up too, was able to install driver with the Weebyx method above…
And, Voilà ! the arrows in the CT windows loose their red cross! 

Registered the remote, created a new zone and added a new device. Uploaded to the remote in CT 5.12.

Thats where I'm stuck now. It did send some data but stop on the "Writing Wifi Firmware" and get stuck there for more than 30 min (yet knowing old laptop and virtualization is slowing down everything). 

Any advice? Thanks

matador43 wrote:

Something happened !!! 🤩

I teared appart the Beo6 in four part: screen, PCB, dock connector and battery and i fueled the PCB with 2AA batteries (again!), connected all things and docked the connector to the base. As soon as I connected it to the Mac it showed up in the Mac Device Manager equivalent.

Then I tried on my virtuel win XP where it show up too, was able to install driver with the Weebyx method above…
And, Voilà ! the arrows in the CT windows loose their red cross! 

Registered the remote, created a new zone and added a new device. Uploaded to the remote in CT 5.12.

Thats where I'm stuck now. It did send some data but stop on the "Writing Wifi Firmware" and get stuck there for more than 30 min (yet knowing old laptop and virtualization is slowing down everything). 

Any advice? Thanks

The WiFi update is only 8KB or something if I remember, but it can take a very long time(I have seen more than 30 minutes on a "real" windows pc). If the battery for the remote is not fully charged, it might fail because of low battery, but it will say so in the config tool.

If the screen came to life when you did the update with tool 5.12, I would try with 6.00 and do the update again.

What I usually do with these remotes, is that I have a new batterypack(created by my self from a old not working), that I have in a working remote with loose keyboard so I can change the battery pack quick. This remote is used just for charging the battery pack used in the remotes I get to life :)

/Weebyx