EventGhost

which version of the pluging are you using? It has been a while but that sounds like a problem that occurred with an older version. Note that the version that come with EventGhost is out of date.

Yes, thatÔÇÖs it.
IÔÇÖve downloaded plug-in from 4th page of this tread and everything is working great now. Thank you very much for your help.
While IÔÇÖm here, is it possible to wake computer from sleep with this remote?

I'm 99% sure that it is not.

Can I use this plugin to send commands to the PS3 from the PC (EG) ?

no

Does anyone know if version 4.0.1 of the ps3 remote plugin is the latest one?

found here: http://eventghost.net/forum/viewtopic.p ... 105#p14593

I have a few questions, please respond even if you only know one of the answers. I think this is a very important plugin for EventGhost.

-Are there any problems with this version?

-Who was the last to edit this code?

-Does power-saving work reliably if you have the widcom stack.

-Does the plugin work reliably (but without power saving) if you have another stack such as Microsoft or Bluesoleil.

I would like to get Pako add this plugin to the standard install of EventGhost because the one that ships now doesn't seem to work at all, but I would like to verify the reliability of this version first, before I create extra work for Pako.

okay okay, don't everybody answer this one at once.

I have briefly tested it and it seems to work fine on my win7 32bit laptop, but with no power-saving even though I have a widcomm stack.

Given that the default plugin that ships with eventGhost doesn't seem to work at all, I think this one should probably be used instead.

jitterjames wrote:okay okay, don't everybody answer this one at once.

I have briefly tested it and it seems to work fine on my win7 32bit laptop, but with no power-saving even though I have a widcomm stack.

Given that the default plugin that ships with eventGhost doesn't seem to work at all, I think this one should probably be used instead.

My System: Win7 64-bit, IOGEAR USB 2.1 Bluetooth Micro Adapter GBU421 (bought from Amazon), Widcomm drivers from IOGEAR Website, Latest EventGhost 0.3.7.r1486, PS3 Remote Plugin 4.0.1

I'm not a programmer, but looking at the PS3 Remote Plugin 4.0.1 code it seems that the sleep time and hibernate times are not used at all to trigger the PowerSave action.
So getting a hint to add a sleep timer from http://www.eventghost.org/forum/viewtopic.php?f=2&t=137

I first added the included 'Timer' plugin, then created a macro with a "Start Timer" action and a 5 second duration. Let the macro get triggered by every event the remote might give, by using the wildcard-event-name "PS3.*" to trigger on all PS3 button presses. Enter a name for the event that the Timer action will trigger after 5 seconds. (i.e "blahblah")
(So this timer will get started/restarted on every button press and if the configured time exceeds it will trigger an event (it shows up as Timer.blahblah) which you can use to start your "Save Power" macro.)

Finally, use the Timer.blahblah event to trigger the PS3 plugin "Save Power" action.

To be honest I haven't tested it out fully yet, but if the "Save Power" action works fine, I think it should work out. (I hope it does.. batteries at level 2 after 6 days)
Lastly, thanks to everyone who has made this fantastic program possible, and remember to manually put in the bluetooth address in the PS3 plugin code.

EDIT: Now that I've re-read peterm's post, it seems this is how the plugin was intended to be used.

as far as I can tell the powersave function doesn't actually do anything. I would like to hear if others have found that it actually does.

If I put the remote to sleep by holding down the ps3 second for three seconds I can tell it is going to sleep properly because a subsequent keypress will take a small but noticeable amount of time to register. When I try to execute the plugin sleep action, a subsequent keypress registers instantly, indicating that the remote did not sleep.

I am using widcomm 6.2.1.800 because that is what came installed on my system, and I don't intent to go back to 5.1 on the off chance that it might let my ps3 sleep.

I guess everyone wasn't kidding when they said you needed the Widcomm 5.x stack.
SetSniffMode is not supported in the Widcomm 6.x stack?

I have no idea, but I was hoping someone could confirm whether it is actually working on 5.1

I would like some help with a cheesy, but (in my opinion acceptable) attempt at a hack.
It's based on the observation that once you have the remote paired to the PC, if you yank out the batteries OR the bluetooth dongle and then put them back in, the remote initially starts in low-power mode and doesn't begin to pull the battery-killing 3mA current until a button is actually pressed. I am assuming that the remote is indeed in low-power mode by merely measuring the current from the batteries with a multimeter.

So we can do one of two things to get into low-power mode:
Option 1. If you have built a switch into the remote (like here), you can switch off the remote, wait for about 5 seconds until the connection is severed, and then switch the remote back on.
Option 2. Disable and then re-enable the PC bluetooth radio, which can be done physically or through the Device Manager.

With option 2 as the method of choice, it is now a simple matter of doing this through EventGhost.
Windows provides a program called 'DevCon' as a free download, which is a command-line utility that functions as an alternative to Device Manager.
You could then just use: devcon disable "HARDWARE_ID"or devcon enable "HARDWARE_ID".

My problem is that DevCon requires Administrator Privileges to run, so EventGhost keep giving me a "The requested operation requires elevation" error.
I could create a batch file with "runas /savecred" commands but from what I can gather this is a security risk.
A search on the forums did show someone using CPAU.
http://eventghost.org/forum/viewtopic.p ... e082#p4652

What I am getting to is, that I would like any suggestions on an elegant way to disable hardware through EventGhost.
It seems to me that this would be the last hurdle to overcome the short battery life, regardless of 32-bit/64-bit os or widcomm/microsoft stack.

Thank you.

REFERENCES:
On getting the latest version of DevCon: Download Windows Driver Kit (WDK), and install just the Tools subfolder. You can then get both 32-bit and 64-bit versions of DevCon.
http://social.technet.microsoft.com/wik ... n-exe.aspx

Examples on how to use DevCon to disable devices:
http://msdn.microsoft.com/en-us/library ... tern_tools

How to run programs as Administrator
http://www.sevenforums.com/tutorials/11 ... rator.html

I wish I had this 'problem' Unfortunately it seems Power Management Tabs are only for built-in bluetooth devices.
http://sherylcanter.com/wordpress/2010/ ... n-no-more/

Dear Sony, look at this. Firmware solution to battery draining on Apple bluetooth keyboard.
http://support.apple.com/kb/ht4010

System: Win 7 Pro SP1, Bluetooth USB Dongle IOGEAR GBU421, EventGhost 0.3.7.r1486.

Someone has already implemented a solution similar to this (sorry I can't remember off the top of my head who or what it was called), but it was buggy and afaik they abandoned development, without ever sharing their code. It think it worked ok on x86 systems, or maybe only on Vista... ah, it's been a while. sorry.

The main objection that I have to this method, is that if you have any other devices connected though the same bluetooth dongle, you are killing them all, and in the case of keyboards and mice, having them disconnect for a few seconds when you are trying to use them is not much fun. If you only have the ps3 db remote running on that particular dongle then I guess this is not an issue.

oh ya, his named just popped into my tired old head.... a miracle!

Superarcan

a quick google of that gave me this...

http://forum.softpedia.com/lofiversion/ ... 36549.html

and this

http://forum.xbmc.org/showthread.php?t=38333&page=13

jitterjames wrote:The main objection that I have to this method, is that if you have any other devices connected though the same bluetooth dongle, you are killing them all, and in the case of keyboards and mice, having them disconnect for a few seconds when you are trying to use them is not much fun. If you only have the ps3 db remote running on that particular dongle then I guess this is not an issue.

Yes, I am assuming that you are using a separate dongle for only the remote. Another downside is that on the off-chance that you pressed a button while the bluetooth radio was re-enabling, the button would not register. But I think it is a worthwhile endeavor for 64-bit os / microsoft stack users who have no options as of now!