It's a cliche, but perseverance pays!
After my last mail, I decided to inspect the USBs through the device manager on the Core i5 to try to reinitialise them. I discovered that all but one didn't work properly. I also discover to my surprise, that one of the USBs is a USB 3 socket. I also managed to download the ASI120MM driver without error, and I am happy to say that now the ASI120MM works on that laptop.
As to the ASI120MC-S, it has failed to work with FireCapture 2.4 Beta on the 3 computers I have tried it on (Sam, this is the link I have downloaded from: http://firecapture.wonderplanets.de/betas.html
. Is it the right one?). The camera is found by the software but capture fails and eventually FC 2.4 crashes. Interestingly, the camera works in FC 2.2 beta (Build #36).
I have managed to carry out some indoor tests (it's been raining for a few days here).
Here are some results:
I have tested the ASI120 MC-S in Shapcap 2 against the maximum speeds provided by ZWO (ZWO figures). I have tested the camera in RGB and MONO8 codec modes. I have also indicated the fps values provided in "preview mode", when the camera is only reading but not capturing, as well as in capturing mode. The connection is USB3 (Renesas Electronic USB3 Root Hub).
Computer specs: Microsoft Windows 7 Professional 64-bit SP1; Intel Core i5 2410M @ 2.30GHz
Capture mode RGB
1280x960 = 22 fps
1024x768 = 38 fps
640x480 = 89 fps
320x240 = 138 fps
Capture mode Mono8
1280x960 = 47 fps
1024x768 = 65 fps
640x480 = 111 fps
320x240 = 139 fps
Test carried out on 9 July 2014
Exp. = 10.00ms Gain = 40 Gamma = 50 ‘Jupiter’ setting
I have also tested the camera in FireCapture 2.2 beta with the same settings and under the same conditions as above:
640x480 = 117 fps
400x400 = 125 fps
300x300 = 178 fps
200x200 = 224 fps
100x100 = 229 fps
Firecapture seems to be more consistent with the speed values provided by ZWO than Sharpcap (although 1280x960 not being available in FC 2.2, I couldn't test the fps at maximum resolution).
I hope this helps.