Ive just bought another ps3 Eye camera and whenever I activate it, the device version looks like the image below. When i go to activate the camera, the UUID of the camera changes to all 0’s. Each time i plug it in, the UUID changes so its used a number of my activations now, however in my code its never found. IT does connect and work inside the CL Eye Test, but I’m assuming that doesn’t look for any GUID information or number of cameras.

I believe this camera is brand new and what comes shipped with the new ps3 move packs.

Anyone have any solution for this?

Are you connecting the camera directly to the USB port on your PC?
Also make sure it is USB 2.0 port and not 1.1/1.0

This was my initial thought, however every port I have attempted to connect it to hasn’t made any difference. I’ve tried to use it on a number of different machines with the CL-EYE driver and up to date SDK and it seems to be doing the same thing. When I am testing with any other camera everything works as expected. the Device version in the top picture is what always comes up.

When I register the camera and activate it, it succeeds and subtracts a credit, then the UUID then turns to all 0’s. If i unplug the camera and plug it back in the camera then appears with a totally different UUID. I am unsure how the UUID is created/read within the device manager… is it possible that they have changed the specifications of the new cameras?

As stated, it all seems to work fine for the CL-Eye test, anything else(where any other camera has worked) just does nothing.

If I get a moment tomorrow I might try and get a video online for you to see whats happening.

Im trying to exhaust all possibilities before calling this one a dudd. i have a few more brand new cameras arriving in the next few days, so will update with any similarities.

So it looks to me like some of the new cameras are having a bit of an unsuccessful time with keeping a constant UUID within the CL-EYE Device manager. So far I have had 2 Brand new units with the same issue. I will be posting a video soon to demonstrate the problems. All of the other cameras are working and they are being plugged into a USB 2.0 port. Ive removed every other peripheral that might be causing problems. Anyways ill let the video do the rest of the talking.

(Video coming soon)

I dont know if this issue is occuring on the side of the CL-Eye Device Manager or if its an alteration to the new camera models, but would like to know if anyone else is experiencing this issue?

thanks

kshaaban,

Could you please post the model number of your new PS3Eye camera (SLEH-xxxx) as well as serial number.
I’ll try to get the new camera with serial close to what you have and try to track down what is going on with GUID.

AlexP

Hi Alex,

Both of the cameras are SLEH-00448

S/N A70510877
& S/N A60114351

I have a few more on their way (I feel like I’ve bought nearly every single one on ebay!)

Will keep this post updated if there are similarities with the different model numbers.

Thanks for looking into it.

Khaled

I seem to have the same problem.  I have two cameras and one is experiencing the weird device version issue while my other cam is fine.  To make matters worse, I had some code that I wrote using OpenCV to utilize both cameras and it works flawlessly on my Mac with two PS3 eye cams but on Windows, its not able to initialize both cams (only 1 is always initialized).
Peter

kshaaban - 04 October 2010 02:53 AM

Hi Alex,

Both of the cameras are SLEH-00448

S/N A70510877
& S/N A60114351

I have a few more on their way (I feel like I’ve bought nearly every single one on ebay!)

Will keep this post updated if there are similarities with the different model numbers.

Thanks for looking into it.

Khaled

Please download and install the new version of CL-Eye Driver and CL-Eye SDK.
The device manager is updated to support new camera version SLEH-00448.

AlexP

I’ve just downloaded and un-installed the old versions and installed the new version (4.0.2.1005 & 1.2.0.1005).

The Device Version is properly displaying now however the Device UUID is still changing every time I plug and unplug the SLEH-00448 cameras.

khaled

Khaled,

Are you running x86 or x64 Windows? Is it Vista or Windows 7?

AlexP

Alex,

I am running windows 7 X64

khaled

Khaled,

Please try running the file attached below and let me know if there are any problems.
I did some testing and this one should work alright.

AlexP

Alex,

That seems to have done the trick. My account is dead on credits so I cant test the activation (is it possible to get my credits reset once this situation is resolved), but the SLEH-00448 cameras both seem to be keeping their GUIDS.

Look forward to testing the fix on my program.

Khaled

I have updated both CL-Eye Driver & CL-Eye SDK (4.0.2.1005 & 1.2.0.1005) with the latest Device Manager.
If anyone else is experiencing changing UUID with new SLEH-00448 model camera, please upgrade your CL-Eye Driver and/or CL-Eye SDK to the latest version.

Khaled check your PM.

AlexP