ankit, aaichert, I assume you are running the CLEyeMulticamTest to test this, because you are talking about using multiple cameras. Is that correct?
What is the exact setup you are using? What program are you using to test this? CL-Eye Test (DirectShow) or CLEyeMulticamTest from the SDK?
One simple way to test the premise that the driver v3.0.0.0901 is more stable than v4.0.1.0217 is to uninstall v4.0.1.0217 and install the driver v3.0.0.0901. Then install the SDK and test the multicam programs again. Are the cameras running under multicam program more stable now? Could anyone test this?

Hi Alex,
Thanks for looking into this. Yes i have tried all possible permutations and combinations earlier:). if i uninstall the driver v4.0 and install driver v3.0 things are much more stable with the SDK as well as with CL-EyeTest-Directshow.

ankit, so here is the thing. Looking at the SDK alone and having two different versions of drivers to test, you are saying that the driver v3.0.0.0901 with the lastest SDK is more stable than the driver v4.0.1.0217 with the same SDK version. This is kind of puzzling since the changes in the driver that affect the SDK are very minor and the only major change is that the driver v4.0.1.0217 uses the latest version of winusb. So it might be that this is the cause of the stability issues you are experiencing.
Can you positively confirm that this is the case with the latest SDK on multiple hardware that you have?
If this is truly a case, I will simply roll back the winusb in the driver and fix the issue.

AlexP

Alex, Yes i have checked this quite a number of times, it is just the driver the culprit according to me. and your WinUSB related change might be the main culprit. Could you compile it with the older winusb version and send me a test release of the driver i can test it and confirm.

ankit, I thought you said you tested it already. All you have to do it install the older driver and keep the latest SDK. Let me know what you find.

Hi, tried to write Alex a private message, guess it’s blocked. Here is the info I can post in the forum

- No latency measurements yet, CPU usage depends on program and computer. But freezes occur also when low.
- I use 2Ghz core duo with 2GB ram no other USB devices and when I work on it I run WinXP that is “up-to-date”
- At work I have several different Dell computers, all Intel and slowish.
- Ordered a new machine for work, due to arrive.
- Camera freezes depend on hardware, fast hardware is more stable but eventually freezes (sometimes runs about 10 minutes even)
- On old dell computers it freezes within the minute and problem occurs also with just one camera
- When I try, like, 75 frames VGA/bw it freezes almost instantly (less than a second). Doesn’t that mode freeze for you? I understand the bandwidth issue, shouldn’t it just drop frames, though?
- Let’s focus on one camera, simple setup? Should be enough to find the problem. Let me know if/how I can be of help.
- I use my own software, grabbing 30 or 60 fps gray in a thread, visualizing using GL in another (60frames with vsync) but freezes also occur in test-apps and on both 30 and 60.

I am going to use at least 3 cameras in my setup, but I’ll probably do IR tracking on a server, so only two cameras will be connected to one computer at a time. Might use CL-Eye for more tracking in the future.

Sorry aaichert, the PM is not blocked its just that it was 5am here when you sent the message.

I am waiting for ankit to do some test and reports what he finds. In the mean time I suggest you run the DPC latency tool while running you app and observe for any spikes.
In general the PS3Eye requires faster hardware to operate and there is no way around that. This is because of the way the data is being sent through USB bus. Moreover since there is no handshaking, any packet that is lost will prevent camera from streaming data. For more info please read this article.

If you want you can try to install driver v3.0.0.0901 while keeping the latest SDK and see if that will make any difference.

Please check out the latest CL-Eye Platform Driver. The stability issues were specifically addressed in this release.

AlexP

Thanks Alex, I have been travelling. Once i’m back i’ll let you know about the tests you asked and will also test this new driver

Hi Alex, I have encounter the same problem with ankit. And I performed the following experiments, maybe the result is helpful.

#test 1
Install CL-Eye-Driver-4.0.1.0501, and CL-Eye-Platform-SDK-1.1.0.0220
#result
CL-EyeTest.exe seems more stable than before, it does not freeze in 20+ minutes.
But the program(writen by me) based on openframework does freeze in a few minutes.
#test 2
Install PS3Eye Camera Setup v3.0.0.0901, and CL-Eye-Platform-SDK-1.1.0.0220
#result
The AMCAP.exe runs stable in about 20+ minutes.
The CL-EyeTest.exe freezes in a few minutes.
My software freezes in a few minutes.

So, I think there is something wrong with the SDK.

Test environment:
laptop with Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz 2.10GHz, 3.00GB RAM, Win7 32Bit Edition(Chinese)
CLEYE_MONO_RAW, VGA, 60fps

It is a really good job except the freezing.

The problem was addressed in the CL-Eye Driver. As long as the new “CL-Eye Test.exe” (driver v4.0.1.0501) runs good that’s what its important. The updated SDK is coming soon.

Great. Can’t wait to go to work tomorrow!

Hi Alex, I just test the latest driver(CL-Eye-Driver-4.0.1.0501) with Direct Show, and it runs stably for more than 1 hour.
(openframework + direct show)

Waiting for your new SDK

Alex, yes it seems to be working without any trouble with a single camera atleast. Multi camera i can only test once you release the SDK

Glad to hear that the driver runs on your systems with no issues. I am testing the SDK right now on a couple of machines making sure that everything runs smooth. The update is coming soon.