Main > Main Forum
Griffin Powermate (Update OCT 14, 08)
<< < (8/11) > >>
sewerrat:
Did you install the drivers the way I had suggested rather than letting the setup routine install them?

Load up the Device Manager and look for the Human Interface Device with the hardware ID "USB\VID_077D&PId_0410". Choose to update the driver, and browse your computer for the driver software. Opt to pick from a list of device drivers on my computer, and then click on the "Have Disk" button. Select the C:\Program Files\Griffin Technology\PowerMate\Driver sub-directory with the PowrMate.inf and PowrMate.sys.

I found this on numerous other forums and it worked perfectly for me
DaOld Man:
Thanks sewerrat, actually, I did not try the method you just outlined.
But I will try it..

After booting up by turning on mains power to the PC several times, the powermate has only failed to initialize once.
But I would really want it to work every time.
I will see if your method works for me. Thanks again.
DaOld Man:
I dont have a driver folder:
C:\Program Files\Griffin Technology\PowerMate\Driver

The only sub folder I have under powermate is plugins.
C:\Program Files\Griffin Technology\PowerMate\Plugins

I have view set to show hidden folders and files.
I have version 2.0.1 software Build 61
if that helps any.
DaOld Man:
I made a time delay circuit to apply power to the powermate about 25 seconds after computer powerup.
This sometimes works, sometimes doesnt, so a time delay circuit is basically useless.
I have found out that if I dont use the extension cable that came with the powermate, it boots up correctly a lot more times than not.
I used the extension cable to connect to my 556 timing circuit, and I have to say the wires in the cable are very small.
I think Mountain mentioned in his juke box thread that he replaced the cable on his PM with a higher quality usb cable. So he may be on to something.
I think I will dissect the PM, and attach a usb cable that has heavier gauge wires in it.
Stay tuned..
mountain:
leapilew actually mentioned that he suspected it could be the cheap ass cable they use. I planned on cutting the length down anyway, so because of his suspicions, I replaced it.

I think it is one of two things: it's either a conflict between the different hardware versions of the PM and drivers available or simply the cable itself.  Seeing as how you have done a lot of testing with your version of the PM, it will be interesting to see what you come up with after swapping the cable out.
Navigation
Message Index
Next page
Previous page

Go to full version