So this problem has been happening for the last few months, unfortunately we don't get enough consistently clear nights to try different things, but it seems like since v2.5 of ASIAir my 2600mm Air camera (and at times my 2600mc Air camera) has been having exposure failures which result in the premature ending of a plan session. Here is a portion of the log from a few nights back where the issue happens:
2026/04/15 02:08:12 Exposure 120.0s image 89#
2026/04/15 02:10:15 Exposure 120.0s image 90#
2026/04/15 02:12:19 [Guide] Dither
2026/04/15 02:12:19 [Guide] Dither Settle
2026/04/15 02:12:28 [Guide] Settle Done
2026/04/15 02:12:28 Exposure 120.0s image 91#
2026/04/15 02:14:31 Exposure 120.0s image 92#
2026/04/15 02:16:34 Exposure 120.0s image 93#
2026/04/15 02:18:37 [Guide] Dither
2026/04/15 02:18:37 [Guide] Dither Settle
2026/04/15 02:19:07 [Guide] Settle Done
2026/04/15 02:19:07 Exposure 120.0s image 94#
2026/04/15 02:23:23 Exposure 120.0s image 94# failed
2026/04/15 02:23:23 [Guide] Stop Guiding
2026/04/15 02:23:23 [Autorun|End] Pause Autorun
2026/04/15 02:23:23 Pause Plan New Plan
2026/04/15 02:23:24 Turn Off Cooling
2026/04/15 02:23:24 [Guide] Stop Looping
2026/04/15 02:23:24 Stop Tracking
2026/04/15 02:23:42 Mount GoTo Home POS
Log disabled at 2026/04/15 02:23:42
I have seen it happen a time or two while I've been monitoring the imaging plan, the camera will complete the exposure countdown, it'll get to a "preparing" state on the screen, then nothing will happen. It'll just hang for a bit, then eventually fail to download, and the whole plan session will end and park the mount. There's never any rhyme or reason, it'll just happen unpredictably, there doesn't seem to be any issues with any of the other equipment connected (EFW, EAF, CAA), with the guiding, or anything else. It'll just be taking exposures, downloading just fine, then randomly fail to download an exposure and end the session.
It's getting really frustrating and I would like some support from tech support here, I can't be the only person here having this problem. I think my next test will be to roll back the firmware to v2.3.3 and trying imaging all night with that.