I'm again facing problems with my ASI120MM. Having connected it directly to my PC and using Telescope Simulator in Kstars/Ekos, I get the following error messages and taking an image is impossible.

2015-08-31T09:07:21: ASIStartExposure error (14)
2015-08-31T09:07:21: ASIStartExposure error (14)
2015-08-31T09:07:21: ASIGetExpStatus timeout out (0)
2015-08-31T09:06:15: ASIGetExpStatus timeout out (0)
2015-08-31T09:05:47: ASIGetExpStatus timeout out (0)
2015-08-31T09:02:41: Device configuration applied.
2015-08-31T09:02:41: ASISetROIFormat (1280x960 @ 1) error (9)
2015-08-31T09:02:41: ASISetROIFormat (1280x960 @ 1) error (9)
2015-08-31T09:02:41: Upload settings set to client only.
2015-08-31T09:02:41: Loading device configuration...
2015-08-31T09:02:41: CCD is online. Retrieving basic data.

The software is up to date from Jasem's ppa and the cam works just fine with oacapture so it isn't a hardware issue.

Any ideas?

Klaus

Yes I can confirm it. It looks like an issue with the x64 static library from ASI as the camera works fine on Raspberry PI 2. I contacted them and waiting for their response.

Got a new driver today and this one gives me images. Just for my curiosity: Did ZWO answer that quick and fixed a bug?
Klaus

Well ASI replied, but I fixed a typo yesterday that's all. Maybe the rebuilt driver worked? I still have the same issue though on x64. Are you using 32bit or 64bit?

I'm running Kubuntu 15.04 64 bit on a Dell Laptop. Just checked again and the cam works fine so far.

I want to use the cam for guiding and played around with 2 seconds exposures. Setting Auto Gain in the cam's controls tab gives me a
2015-09-02T09:11:39: ASISetControlValue (Gain=50) error (16)

Then I set bandwidth down to 50 (clicking the Set button) and take an image. Afterwards some magician has set the bandwidth up to 80 again. Any explanation for this?

And now I'm back to this:

2015-09-02T09:17:04: ASIGetExpStatus failed (0)
2015-09-02T09:17:02: ASIGetExpStatus failed (0)
2015-09-02T09:17:00: ASIGetExpStatus failed (0)

To me it looks like changing gain/bandwith kills the driver.

Klaus

So ZWO got back to me saying it's a USB 2.0 vs USB 3.0 issue and I can confirm, it worked fine when I plugged it into a USB 2.0 port. They are looking into USB 3.0 problem.

But I have no USB 3.0 on my machines! I'm just playing around with the cam (and the default settings) because I want to use it via a powered USB hub. Simply running focus mode infinitely the connection to the cam gets lost after a few minutes. Now I want to check it with direct connection. If this works then changing USB cables is next. Any other ideas for using a hub?

Direct USB connection lost after some minutes:

2015-09-06T10:49:18: ASIGetExpStatus failed (0)

Now switching USB cable to the one delivered with the cam but no success. Connection lost after 15 minutes of continuous 0.5 sec exposures.

2015-09-06T11:12:46: ASIGetExpStatus failed (0)

Jasem: Can you do the same check?

Klaus

Same here Tried ThinkPad R400 and a Fujitsu Lifebook E8310, both ASI 120MM. As there is no source available I was not successful with debugging right now.

Well, I played around with USB cables and this is the current config:

ASI 120MM ----> 2m, shielded, with ferrite core, delivered with cam ----> powerded USB hub ----> 4m, probably unshielded, because it's a flat cable -> Laptop

I had this focusing with 0.5 sec exposure time for more than an hour and the connection was stable this time. But the 2m cable failed early in the day when I used direct connection. Don't know why but if it stays valid on real sessions I'd be more than happy.

Klaus

Difficult... I always use the cable delivered with cam... maybe I should check others too