ASIAIR v2.5.2 has been released!: Page 6

ASIAIR v2.5.2 has been released!

Moontanner

Eric
Have you tried downloading the log file and having a look at it on a PC, Eric?
Something like this?

That sucks that you lost a good imaging night.

Eric

Moontanner
Yup, the logs look like this when the plan session fails due to an "exposure failure":

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 tried two more power configurations, a 12v 10a power supply with a y-splitter so I could run one cable straight to the camera and one to the mount, bypassing the power pass-through in the mount. I'd prefer to use the power pass-through in the mount, but it may not be enough to power the Air camera stably enough. The camera REALLY did not like this arrangement, it had near constant disconnects of the main imaging sensor, the EFW, EAF, and CAA (but strangely kept the guide sensor connected and the mount). So I disconnected that and switched to my EcoFlow River 2 Max, running a cigarette plug (12v 10a ouput) straight to the camera and then a separate DC 5.5x2.1mm power cable from the DC outlet on the battery to the mount. I was able to run a full plan session with no premature exposure failure issues with this configuration, but I was having a really unstable app experience with both my Android smartphone and an iPad mini. Sometimes it would fail to connect to the camera, sometimes it would stop responding, when I finally got it responding and tried slewing to M101 it wouldn't "find" enough stars to platesolve even though there were tons of stars in an exposure and it could "detect" a fwhm/star size from a single exposure. So I parked the mount, restarted the camera again, and after 2-3 restarts it did start acting more normally.

This is just becoming such a battle to get the camera to operate normally. Seems like I had none of these issues before moving to version 2.5.

R0k9pZfT

Moontanner Actually, it turns out with 2.5.2 on mine that there is now NO progress countdown.

I'm running it on two different Samsung tablets. One is Android 14 on the S6 Lite 2022 version. The other is the latest A11+ running Android 16. Both have the latest Play System update available for their respective platforms (this is separate from the OS version) as well as the latest OS patch. Haven't tried it on my Pixel 10 Pro, because the screen is too small to be practical for this use for me. All are US editions if that matters.

I have confirmed the flats do not have the camera rotation in the filename.

Perhaps it is then my combo of imaging hardware triggering the countdown problem. I forgot to mention I also have the previous gen EAF. 5V version.

Moontanner

R0k9pZfT I have confirmed the flats do not have the camera rotation in the filename.

That's weird. I'm currently doing a big clear out of excess gear, so I've tried a bit of everything lately. Android wise I'm running just fine using version 14 through to 16 on various phones and tablets. My ZWO equipment is a mixed bag as well, although I'm not using any of their mounts.

I get the camera angle showing up in the filename for flats. I'm pretty sure they moved it's location further along to stop it messing up the list order after a meridian flip.

One thing that I have found with all of the ASIAIR's I own is that the power supply sockets can be a bit touchy. I've had several sessions glitch due to power supply issues during slewing. The power drops for a split second and everything boots up from scratch.

Regards the dithering thing, I just turned mine off all together as I've found the ASIAIR dithers enough on it's own. The lowest failed plate solve for target centring I've managed to find is a fraction over 1% of the pixels. The 2600's Are roughly 6k x 4k pixels. All it takes is a passing cloud to lose the star, or a temperature triggered refocus and you're dithering plenty. 😃

Clear skies.

R0k9pZfT

SKNz57l3 Is this only with 2.5.2? If so or you're not sure, have you tried backing down to earlier releases without changing your cabling to see where it seems to fail? What does the voltage read in the AA+, and how are you running power to things?

I'm not against using the AA+ for power distribution--I do it. I have everything powered by one 16 AWG power cable I made to the AA+ and then spread out from there. But I ask you for completeness. You might try a heavier gauge power cable if the AA+ reads a bit low.

R0k9pZfT

I posted this again to the 2.5.1 thread for some reason. I meant it for here.

Another issue I continue to bring up, and if I missed a response, I apologize. But I'll past directly from my previous post. As mentioned there, this may be more of an issue on harmonic mounts.

Problem is, after dithering the harmonic mounts don't really "settle" much. Given their design, they continue to have the same uncorrected errors until guiding resumes. But with ASIAir, the settle timing tends instead to time out, then both guiding AND shooting begin simultaneously. Seems to me that the guiding should resume first, then the settle time begins or a second settle time kicks in, and THEN the shooting resumes. I frequently stop shooting, let the guiding settle the mount errors, then manually resume shooting. Very annoying. And I get excellent guiding on my AM3 usually shy of 0.25" on each axis according to the AA+. But the errors don't settle much with these mounts without guiding.

Chrisjuh

My ioptron cem60 mount diconnects when I try to connect. Restart does not help. When I install the 2.4.1 app I am able to connect the mount. I am using the android app.

Chrisjuh

Lynx1971 same issue here with cem60 mount

Lynx1971

Chrisjuh I've reported this problem again and again, we will see their response..

Moontanner

Eric I tried two more power configurations, a 12v 10a power supply with a y-splitter so I could run one cable straight to the camera and one to the mount, bypassing the power pass-through in the mount. I'd prefer to use the power pass-through in the mount, but it may not be enough to power the Air camera stably enough. The camera REALLY did not like this arrangement, it had near constant disconnects of the main imaging sensor, the EFW, EAF, and CAA (but strangely kept the guide sensor connected and the mount). So I disconnected that and switched to my EcoFlow River 2 Max, running a cigarette plug (12v 10a ouput) straight to the camera and then a separate DC 5.5x2.1mm power cable from the DC outlet on the battery to the mount.

You've gotta love those ASIAIR Log puzzles. It's like getting a crossword with only half the clues.
I'd be looking at your power supply setup. Try something other than the EcoFlow River 2 Max (- 512Wh capacity (40Ah) and 500W output).

1000W X-Boost
Run 80% of essentials, such as a travel kettle or laptop
Fastest recharge in only 1 hour
512Wh, 20Ah⎓25.6V

The specs on that thing look like they're deliberately misleading to me. At least run an inline power meter to see what's really happening when your session goes funky.
What your describing sounds very similar to what happens if I use a 25AH 12.8v LiFePo battery. I doesn't last the night on my main rig and I'd be surprised if that EcoFlow does much better with all of the extra peripherals built into a tiny box.
Personally, I run a straight up 100Ah LiFePo 12.8v battery that powers the mount and ASIAIR separately. The ASIAIR powers the camera and 1x low powered dew heater. It's been awhile, but I vaguely remember it maybe working for two long nights at best.
YMMV. Clear skies.

Eric

Moontanner
Keep in mind that this is in my home observatory, the EcoFlow is simply acting as a backup and is plugged into my mains power being charged simultaneously. I've also tried running the whole rig directly off my mains power using a Pegasus 12v 10a power supply.

michael.wells

Moontanner I do the same - I have a 100Ah battery under the tripier and separate heavy duty DC cables running to the ASIAir and the mount. I use a fused connection in line directly from the battery terminals. I don't use the saddle power port because you can see additional voltage drops via that route (I did and A/B test and decided to power directly). I haven't experienced any frames being dropped since I adopted direct power to the kit. It is a shame that there is such doubt about the power delivery as it ought to be forgiving and reliable.

Moontanner

Eric
Fair enough. I thought you were running it off of only the EcoFlow.
I'm seeing a lot of fancy new portable power supplies around that promise the world and fail to deliver in real world situations.
All I know for sure is that I'm not getting any failures with this software release and I've been throwing everything at it for 14 nights now. 3 different ASIAIR's, 2x EFW (OLD/NEW), a CAA, the original 2600mc pro, the newest 2600mmDuo, a 290 mini guide cam, a 178mc, and 2xEAF.
Your problem sounds like a hardware issue if it's acting differently based on the power supply methods.

I hope you get it figured out for your next clear night.
Clear skies.

Moontanner

michael.wells
A simple twist, or gentle tap on the 5.5 input jack on the ASIAIR's and I can often cause a re-boot. Sometimes I find they want a little twist to make them work again if they won't fire up.

Those little Rasberry Pi boards don't have any tolerance for voltage drops. Fortunately, it's rarely an issue these days.

michael.wells

Moontanner Definitely. The 5521 connector is widespread but there are so many better, higher capacity solutions that are robust, eg XT60 springs to mind. Stringing devices in series where the barrel connector is only designed for 3A is inviting problems. It still works, at least for me, but the firmware version wildcard is hard to explain.

Moontanner

michael.wells
It's a tough one with the connectors. I guess the 5521 ticks the most boxes when it comes to the ASIAIR, size and cost being two of the big one's. If you make the connection too rigid, they just fail at the start of the flexible cord eventually. 🤷‍♂️
Good cable management (and maintenance) is definitely a must.

Getting back to the actual firmware update, I'm 15 for 15 sessions now without a software glitch. That's running two ASIAIR's each night. One for imaging and a Mini doing 15s exposures for timelapse allsky imaging/monitoring conditions.
The earlier firmware had my CAA doing all sorts of crazy.

It would be great if the logs showed more information to help self diagnose issues. I gave up going back and forth with support a long time ago, as it's often fruitless.
A separate power log file similar to the guiding log would be great.

Clear skies.

michael.wells

Moontanner +1 from me. A log of guiding, power (volts and amps), storage IO perhaps, wifi strength and potentially other variables - whatever events occur - every 30 seconds would be invaluable.

Eric

Moontanner

Yes, a power log would be valuable for sure. I decided to strip away things and just run the Pegasus 12v 10a straight from my mains power to my 2600mm Air camera, for some reason it did not like that, things disconnected, I was having all sorts of app freezes and wifi problems, super strange behavior. I switched the power supply to powering my iOptron HAE29c-ec and then running power from the saddle output to the 2600mm Air, the saddle output is only rated to 12v 3a though. The camera didn't seem to mind this, in the Air menu I noticed that the camera was reporting closer to 13v, whereas when I was using the EcoFlow and its 12v 10a DC ouput with a cigarette lighter (either connected directly to the camera or to the mount and then the mount to the camera) the Air app was reporting between 12.1-12.4v. I was able to run a plan session all night, single target, without any exposure errors and premature plan ending. I then tried plugging the Pegasus 12v 10a power supply into the AC outlet on the EcoFlow and the camera reports 12.7-12.8v, so still higher than the DC output cigarette lighter connection. No clear nights for a while so I won't be able to test a full night imaging to see if I have any errors.

Using the AC output with the Pegasus power supply is suboptimal, I'll lose a fair bit of backup battery power/time running that configuration vs running the rig off the DC output by itself. I went ahead and ordered a Bluetti Elite 30 which has DC5521 output at 12v 5a (two output connectors, combined up to 8a) and a wider temperature operating range than the EcoFlow to see if that resolves the DC output problem. Supposed to get it today, so I'll report back what the Air reports in terms of voltage input.

Moontanner

michael.wells
Computers aren't my thing, so I'm not sure how hard it would be to implement something without causing more issues than solutions. It sure does seem like it would help reduce the need for support a lot of the time though.

I do wonder how many issues are power related. and not actual firmware issues?

My general rule is:

Check all cords and power supply.
Check my third party mount.
If the problem persists I'll contact support. ( Hello crazy CAA several month ago).

Moontanner

Eric
Have you tried the ZWO plug in power supply? I've had mine since the 2600mc Pro first hit the scene and it's never had a problem powering everything when I'm doing stuff inside. (Outside is too close to my pool for 240V).

2x ASIAIR Plus' give similar results when I use the ZWO supply, or the 100Ah LiFePo.

I've currently got a bone to pick with Pegasus about their 12v power supply cords. These two reacted very badly to a particular socket splitter, and one other is already showing accelerated signs of corrosion in a known good splitter.

« Previous Page Next Page »