Problems with ASI120MM and Windows 10

joachimh

Hello,

I am using for 2 years the ASI120MM in conjunction with a Windows 7 64bit and it works in every Situation very well.

Regarding the age of my Notebook and because, I am afraid, that it fails soon, I bought a new one with the OS Windows 10 Home 64bit. And now, using this camera, I have very big Problems to use them with FireCapture (and additionally SharpCap).

I installed FireCapture Versions 2.2, 2.3, 2.4 and 2.5beta (I tried both the 32bit and the 64bit Version).

Following Problems occur:

Capture failed very very often.

I reduced USB-traffic to 40. But only very small ROIs (120x128 until sometimes 320x240) are working. Oftenly Capture failure appears and/or the Frame rate is reduced to Zero or 3 until 5 fps. But the expectation should be 50 to 60 fps depending on the ROI. And sometimes, fps jumps between high fps and low 3 or 5 fps for small ROIs.

The Java Version, I use, is Version 8 Update 77 (Build 1.8.0_77-b03), if it is important for the discussion.

Furthermore, I use the newest Firmware for the 120MM.

I have no idea, how to solve this.

Unfortunately, I wanted to buy a ASIxyz-USB3.0 camera, but now, I am afraid, that I will get the same Problems.

Is there anyone, who had the same Problems and knows a solution?

I would be very grateful for fruitful hints.

Best regards

JoachimH

riklaunim

Are you using a HDD or SSD? are there any disk intensive apps running ? Like anti-virus? Such apps either eat HDD bandwidth or scan the incoming video stream making it slow to record.

joachimh

Hello,

Yes, I have a SSD and HDD; FireCapture is installed on the HDD and the record folder is also on the HDD.

Yes, McAffee is always running - but that was the same on my Windows 7.

Maybe, McAffee behaves on the Win10 a little bit different, because it is a new version on my Win10.

I didn't know that the incoming video is also be scanned by McAffee. But otherwise, all my notes concerned only the preview window - I didn't made any attempt to record a video file, because of the bad values during the preview.

I will check your hints in the evening and will post the feedback here...

Thank you very much, so far...

JoachimH

joachimh

Okay,

as I promised, here my feedback to additional tests...

You proposed, that I stop the antivirus Scanner - so I stopped the realtime scan mode.

-> no solution!

Then, I installed FireCapture on my SSD (here partition c:)

-> no solution

-> In every case, the preview window shows capture failure (for high ROIs) or multiple splits on the window with very low fps (for low ROIs), e.g. 3 or 5 fps. USB-traffic is reduced to 40.

Sometimes, it seems that it works - but only for 3 sec. Then, the preview stops and fps is very low.

Sometimes, it seems, that I have to increase the USB-traffic - but only for 1-2 sec.

Then, I used RAM buffering with max. capacity

-> no solution

Then, I changed the display resolution from HD to 1280x1024

-> no solution

Cable change

-> no solution

In our observatory, we have all computers changed to Win 10 - up to now, i cannot recommend the use of the ASI-camera.

I hope, there will be a solution soon - Mercury transit is coming and that will be a great public event at our observatory (for that, I wanted to buy a USB3.0 ASI-camera for operation at a Lunt Halpha).

But now, this buying will fall into water - very disappointing...

JoachimH

PS: I will post a screenshot - maybe, someone can see some interesting...

joachimh

Screenshot.jpg

joachimh

Be aware, that the ROI is very low and the fps is incedible low too.

For a test, I increased the USB-traffic, as I described before, but the result is the same as for the value of 40.

Look at the multiple splits in the preview window (an AVI shows the same).

Additionally I showed the task manager with the very low loads of CPU and disk.

Best regards

JoachimH

Sam@ZWO

I think maybe the problem is due to the firmware upgrade

you need to use the firmware name without compatible

the compatible firmware may runs slower in some computers

joachimh

Hello Sam,

Can you explain me, what I have to do? I do not understand...

Do you mean the camera firmware? I installed that firmware, the last one, I got from your website.

What do you mean with "without compatible" and where can I get this firmware?

Thank you for your help...

Joachim

joachimh

Hello Sam,

Update to my last post: I now know, what you mean...I have installed the firmware twice again; first without the extension -compatible -> no change in the behaviour

2nd again with the extension -compatible -> also no change in the behaviour

The behaviour in FC 2.5beta looks like:

lowest ROI -> all Okay, nearly 200 fps

Increasing ROI bottom-up: at 512x400 I got first problems; for ca. 8 sec I have ca. 60 fps (everything seems Okay) and then, Capture preview suddenly stops -> Capture failure -> waiting for a while, Preview capturing continues for some little fps and stops again.

Sometime, even when I try higher ROIs, FC shows the message, that it has loosed the connection to the camera...then I can choose Connecting or Break.

Any idea?

Joachim

Sam@ZWO

I think it's compitable problem if your win7 laptop runs good

sometimes, some usb3.0 host may have such compitable problem

this is not a problem of software but hardware

but our usb3.0 cameras should have no such problem

arkady

Hi. I have the same problem with ASI 120MC and my brand new notebook on I7 cpu and Windows 10. My aged and weak netbook as well as desktop on Windows 7 work ok.

I plugged the camera both to USB 3.0 and USB 2.0 sockets on my new notebook and saw no difference.. So it may not by usb 3.0 host problem?

kmmathews

I have an ASI174 M/C running on a MSI G72 I7-4240HQ CPU 2.60GHz 16.0 GB RAM, 64-bit operation system x64 based processor all USB 3.0 ports with Windows 10. FC 2.5x64 will generally run the first capture at full resolution 1936x1216 at 60 fps capture 1000 frames next attemp frame rate does not drop but only 50 frames captured and then stop same for AVI,SER and FITS. If I reduce the ROI down below 700 x 600 no problems. Have no solution for you though. It pushes me to use SharpCapture 3.0