I've been having problems with an ASI 178C captures stopping in the middle of a guiding session. This is with a setup that was working really solid for several months. Here's the setup:

RPI4 USB 3 -> ASI 1600MM Pro -> ASI 178C

I'm seeing this in the logs, not sure if it's related:
2020-02-01T07:27:43: ZWO CCD ASI178MC: [ERROR] ASIGetDataAfterExp (3096x2080 #1 channels) error (11)

The only thing that has changed since it was working solid:
-Switched to tagged release version of indi - "INDI full v1.8.3 release" - I build from scratch and keep up to date with the git repo tips, but I decided that I should switch to a tagged release to make things more stable

I'm trying to repro it today running it inside, and so far it is running fine. I think that It's just waiting till I get a clear night with perfect RMS and a beautiful target before it decides to act up.

Any ideas? I guess that I could try and go back to tips.

Jamie

OK, so I caught it in the act. I don't see that error in the log, and I don't see any errors. I had phd2 guiding on a hot pixel, and Ekos doing a looping download of 180s images . Both just stopped, and I don't see anything obvious in the logs, there are a couple of errors, but those happened before the captures started. Strangely I don't see anything in the log about the 178 doing a capture even though it was working.

2020-02-03T17:27:09: SkySafari: [INFO] Loading device configuration...
2020-02-03T17:27:09: SkySafari: [INFO] Device configuration applied.
2020-02-03T17:27:09: ZWO CCD ASI1600MM Pro: [INFO] Loading device configuration...
2020-02-03T17:27:09: ZWO CCD ASI1600MM Pro: [INFO] Upload settings set to client only.
2020-02-03T17:27:09: ZWO CCD ASI1600MM Pro: [ERROR] Invalid frame requested (0,0) (0 x 0)
2020-02-03T17:27:09: ZWO CCD ASI1600MM Pro: [ERROR] CCD_VIDEO_FORMAT: newSwitchVector with no valid members
2020-02-03T17:27:09: ZWO CCD ASI1600MM Pro: [INFO] Device configuration applied.
2020-02-03T17:27:09: ZWO CCD ASI178MC: [INFO] World Coordinate System is enabled.
2020-02-03T17:27:09: ZWO CCD ASI1600MM Pro: [INFO] World Coordinate System is enabled.
2020-02-03T17:27:11: GPSD: [INFO] GPS disconnected successfully.
2020-02-03T17:39:27: ZWO CCD ASI1600MM Pro: [INFO] Taking a 9.1 seconds frame...
2020-02-03T17:39:37: ZWO CCD ASI1600MM Pro: [INFO] Exposure done, downloading image...
2020-02-03T17:39:37: ZWO CCD ASI1600MM Pro: [INFO] Download complete.
2020-02-03T17:40:08: ZWO CCD ASI1600MM Pro: [INFO] Taking a 180 seconds frame...
2020-02-03T17:43:08: ZWO CCD ASI1600MM Pro: [INFO] Exposure done, downloading image...
2020-02-03T17:43:08: ZWO CCD ASI1600MM Pro: [INFO] Download complete.
2020-02-03T17:43:10: ZWO CCD ASI1600MM Pro: [INFO] Taking a 180 seconds frame...
2020-02-03T18:33:50: ZWO CCD ASI1600MM Pro: [INFO] Taking a 180 seconds frame...


It's doing it again just now, This time ekos is in the middle of downloading an image, and it's showing 173s left for ever.

Jamie

OK, I'm going to just switch to git tips and see if it continues.

Jamie

Well, I guess I'm just talking to myself. I'm used to it:)

So switching to indi tips, and recompiling everything seems to do the trick. I'm not sure what the issue is, but my rig has been happily capturing guiding and main camera images for hours with no glitches.

Jamie

I'm imaging tonight. Things seemed mostly good, until the 178 started acting up again. The camera just stops capturing in the middle of guiding and I see this:

2020-02-05T06:25:52: [ERROR] ASIGetDataAfterExp (3096x2080 #1 channels) error (11)

Looks like switching to tips did not fix the issue.

I saw this yesterday as well for the first time ever. Most likely related to the latest ZWO SDK.

I have had the same ASIGetDataAfterExp error with the ZWO ASI120mm mini.

Once I get that error, I have been unable to capture any images with the 120mm. No amount of rebooting, settings change would bring it back to capturing again until I went to the INDI control panel and clicked on STREAM ON.

Suddenly the camera came to life and I was able to see the video from the 120mm. I then closed the video window feed and then it would Loop in the guide window. It would then work until I tried to plate-solve and it would stop again.

I was able to get it somewhat stable later last night by resetting everything, then turning the usb bandwidth all the way down. I'm not sure if I was just lucky, or if that made a difference.

As for the 120, I've got one of those and it has never worked well. It often has split screens, and that drives guiding crazy.

I've never had the split-screen issue but have seen it mentioned. The camera works flawlessly on RPi3 and Stellarmate 1.4.6.

I have yet to have that it work on RPi4 after plate-solving and hoping 1.4.7 beta updates has resolved it.

I can launch plate solve and it fails indoors, which I've done many times but putting real stars to solve, it will suddenly stop working, throw odd errors and never connect again, always failing to expose.

OH, I've got the older USB 2 version. You probably have the USB 3 version. I don't think that one had the same issues.

It is USB 2 version. It was sold with a Stellarmate Rpi3 bundle from Optcorp

OH, weird. Mine has never worked right. I tried different firmware etc, just couldn't get it to work without the occasional split screen. Maybe they have a new firmware fix?