PlayStation 3 Bluetooth Remote

[Blight]

There is a very serious issue with this plug-in and Windows 7 64bit (these issues didn't occur in the 32bit).
This is on clear install...

Every 24h or so, I have to restart event ghost because of one of these reasons:
1. CPU maxed out.
2. Memory leak until 2GB of ram is consumed and then freeze.

I can even get EG to go into a looping series of errors until EG freezes by simply removing the batteries from the PS3 remote and then putting them back in.

Here's a screenshot of the errors:


Here's a bigger log that I was able to catch:
http://t.inmatrix.com/ps3remotelog.zip

[scissors]

There is a very serious issue with this plug-in and Windows 7 64bit (these issues didn't occur in the 32bit).

Are you using the one included in the EventGhost package? Try the newer ones posted in the previous pages. I'm using it with Windows 7 x64 that is up 24/7 and haven't noticed any major problems myself.

[Blight]

Are you using the one included in the EventGhost package? Try the newer ones posted in the previous pages. I'm using it with Windows 7 x64 that is up 24/7 and haven't noticed any major problems myself.

Yeah, I was using the included build. I now switched to the 4.0.4 build and while I only had a few minutes to play with it, it doesn't crash anymore when replacing batteries, so I'm being optimistic.

I have a few questions about this version:
1. The new version adds a 'Save Power' function. I'm assuming this button puts the remote into sleep mode (turns off blue-tooth connection), am I right?
2. The biggest problem with the PS3 as a PC-Remote has been the battery drain from the remote not going into sleep mode automatically. This batteries last about 4 days.
Did you get automatic sleep mode fixed so batteries can last longer?

[scissors]

Sorry to say, I personally don't know the inner workings that well. Maybe someone else can answer in depth...

My batteries last much more than that though, so maybe it is working.

[gechu]

PS3 remote with power save on Windows 7 x64 on EventGhost 3.6.1486

(tested with multimeter, current fall down from 10-20 mA to 0.2 mA)

I still continue to use EventGhost 3.6.1486 as it's the last version works with my plugin and all later evolution of PS3 plugin are not fully compatible with mine but I switched to Seven x64 and I needed to investigate a little bit to have it working again.

1st to install Widcomm Bluetooth 5.1.0.1100 you will need "WidcommLicensePatcher.exe" (v1.7) and not patched .dll or .dll patcher (only available for x86)

2nd you will need to self sign the bluetooth drivers file to allow Windows 7 x64 to load it, for this use "Driver Signature Enforcement Overrider" "dseo13b.exe". This software is safe, it don't inactivate driver signature, it just allow you to self sign the files you want. (is it your system yes or not ? who decide which software is allowed to run on it ?)

3rd you will need to copy the Widcomm files "wbtapi.dll" (593 981 bytes) and "WidcommSdk.dll" (581 632 bytes) from the directory C:\Windows\System32 of a 32 bits system (Windows XP for example) with Widcomm installed to the directory C:\Windows\SysWOW64 of Windows 7 x64

Thats all.

I hope one day I will have time to concatenate all the evolution of PS3 plugin to build one fully compatible with all existing version ...

Hi Thierry,

I´ve spend some time investigating how to install the WIDCOMM 5.1 by hacking INF´s, signing driver etc. But it simply doesn´t work. One reason is probably that I don´t understand exactly what is happening.

What parts exists in this solution:
- Widcomm Bluetooth Bus Enumerator version 5.1.0.1100 bluetooth stack?
- USB bluetooth driver. Must the one provided by the Widcomm be used (didn´t work for me)? Or can I use the drivers shipped by the usb BL dongle manufactur (Atheros, model AR3011)?

You mention that you copy filed into certain folders, but that way of installing is very different from the guide I found which was suppose to work with Vista X64, which should be close to windows7 x64 that I am using.

Can you please provide some more details about how you got it working?

Thanks, Erik

[abraxxa]

I had an Asus P8P67 with onboard Atheros AW AR3011 Bluetooth and 7.2 driver version, worked flawless.
Now with the new Asus P8Z68 and also a 7.2 driver version it does one day but not the other.
I can see the PS3 remote connected in the bluetooth control panel but get no event on keypress.
Disabling and enabling bluetooth helps sometimes.

[gechu]

abraxxa, how did you get sleep for the PS3 remote to work with your first AR3011 to avoid battery drain?

[abraxxa]

I'm not sure if I had solved it.
I definitely had the problem with the USB Bluetooth dongle before the P8P67.
Maybe that's still the cause of my current problems.

[mupet0000]

I'm using this new 4.0.4 version from the previous page with the latest EventGhost. I have a an official PS3 BD remote that doesn't have the volume buttons. It's working fine but how do I make sure the remote is using hibernate functions?

I've tried this app: http://ps3remotesleep.codeplex.com/

It seems to hibernate the remote but wake up instantly according to the eventghost log. I can't continue using the remote if it's gonna drain the battery. Does anyone know of a full proof way to make the remote sleep for sure?

[stefstef]

Somebody have tested this : http://forum.melloware.com/viewtopic.php?f=1&t=9713 ?

Edit :
It seems to work !
You had to create a planned tasks with admin rights at session startup for EventGhost and disable sound.

[abraxxa]

For me it seems to work without any additional tool on an Asus P8Z68-V mainboard with the onboard Bluetooth adapter.

[stefstef]

Hi,
With your configuration, can you wake up your computer from standby with the remote ?

[abraxxa]

No, but I didn't need that (nor was I aware that this is possible).
Now I'm using a Rasberry Pi with RASPBMC, a bluetooth dongle and the PS3 remote anyways

[Blight]

I recently encountered a very strange issue.

After a windows update today (maybe unrelated, but happened the same day), after a few minutes with the remote, and suddenly a lot of the buttons show up as if the stop button was clicked.
So if 1 click down on the pad shows up in the log as:

PS3.Button.Down
Zoom Player: Navigational Control Down
Zoom Player: Navigational Control Down
PS3.Button.Stop

And interestingly enough, pressing the up button, shows up as:

PS3.Button.Top
PS3.Button.Stop

What it should be showing is:

PS3.Button.Up
Zoom Player: Navigational Control Up
Zoom Player: Navigational Control Up

I have switched batteries and restarted event ghost several times.
After replacing the batteries, everything works fine for 1-2 minutes and then it enters this mode.

I didn't test uninstalling the windows updates or replacing the bluetooth dongle just yet, before I start breaking things apart, I'm wondering if anyone else experienced anything like this before?

Edit:
I tried uninstalling the windows updates, and switched the bluetooth dongle to a brand new one from a different manufacturer.
I'm experiencing weird effects like the buttons working, but sending the clicks one behind,
If I press down/up, it will only show the 'down' when i press the 'up' and if I then click 'right', it will show the 'up' command.
And I also get spontaneous 'stop' events, even when clicking nothing.

Is the remote dying?

[piipes]

I think that ps3 plugin needs update. There is new Sony PS3 Media Blu-ray Disc Model CECH ZRC1U remote.
Now we can wakeup pc via usb-uirt.

http://www.wirelessgoodness.com/2011/02 ... ny-3d-tvs/

I think that there is some new bluetoot action. Those instant buttons give error in eventgost ps3 plugin.



Edit: Sorry, i find that new plugin in last page. I hope that someone could update first post too.