ASIAIR v2.5.2 has been released!: Page 5

ASIAIR v2.5.2 has been released!

6hv2tpLE

Luxo...many want the mount to have a 90° position to close the telescope and have a home position already pointed towards Polaris...just like the possibility you have using a ZWO AM5 or AM7...and on cloudy nights the ZWO technical manager had said they would provide this. It's very convenient...you criticize, but then you will use it too. Please ZWO provide the parking position for non-ZWO mounts...thanks so much...

Luxo

6hv2tpLE

Then I suggest there is no issue.

Mounts like the CQ350 have hard index for the park position, at +/- 90 declination, counterweight down.
Perfect.
On mounts like EQ6/EQ5 that do not have a hard index, do the following:
Using ASIAir, select GO HOME POSITION, wherever that goes we don't care;
unclamp the RA and Dec axes,
set the mount so it is aimed at +/- 90 declination, counterweight down. Use a spirit level to accurately set the counterweight shaft vertical. You could set HOME anywhere you like, and AA wont care.
Tighten the clamps.
In ASIAir, in the mount pane, press "SYNC TO MOUNT".
When you select GO HOME POSITION again, it should return to the position set above.

PMTeam@ZWO

6hv2tpLE Hello,
We have previously looked into adding the park function for non-ZWO mounts. However, numerous compatibility issues have emerged, preventing this feature from working properly with third-party mounts. We sincerely apologize for the inconvenience.

Corsair

Lynx1971 just curious: does 2.4.3 work for you?

Lynx1971

Corsair Nope.. only 2.4.2. Seems like they make some changes related to the mounts..

Moontanner

Luxo On mounts like EQ6/EQ5 that do not have a hard index, do the following:
Using ASIAir, select GO HOME POSITION, wherever that goes we don't care;
unclamp the RA and Dec axes,
set the mount so it is aimed at +/- 90 declination, counterweight down. Use a spirit level to accurately set the counterweight shaft vertical. You could set HOME anywhere you like, and AA wont care.
Tighten the clamps.
In ASIAir, in the mount pane, press "SYNC TO MOUNT".
When you select GO HOME POSITION again, it should return to the position set above.

@6hv2tpLE

PSA: Make sure that new home position allows for the PA routine without slamming the scope into the tripod/pier.

6hv2tpLE

Luxo Luxo...@Montaneer....Luxo...@Montaneer.... I get it this far. Maybe you didn't understand well, people want the AUTOMATIC movement and NOT MANUAL as you described. I repeat on Cloudy Nugyhts the manager of the ZWO technical area had said that they would provide it. For now they have done it for THEIR ZWO mounts (AM5/AM7) and not for other brands. Maybe THEY DON'T WANT TO DO IT because otherwise they don't sell their mounts! It's a shame because I consider ZWO a serious company and I have bought many things from them (like the Seestar S50). However, if they don't provide the Parking Position option in the next upgrade like for the AM5 mount, we will no longer buy their products. I'm good at doing it manually with the AZEQ6GT too!

6XeP1xM5

PMTeam@ZWO Is the drift alignment feature still in your plans?

Moontanner

10 for 10 successful sessions since the latest update. Great work ZWO!

heyjp

PMTeam@ZWO

Could you add the remote timezone (e.g. -6hrs UTC) to the custom remote location? Currently, i have to change my iphone or ipad time zone to the remote location before connecting to my ASIAIR. If i don’t, it uses the new location feature but syncs to my current timezone, not the timezone of the remote telescope.

Thanks! Jim

Luxo

heyjp

What you suggest is a kludge.

The correct way to do this is to determine the country, timezone from the latitude and longitude of the telescope, with daylight saving. What would resolve this properly is a new ASIAir with internal GPS receiver so it is no longer dependent on the app on a phone.

At present ASIAir asumes the device running the app is co-located with the ASIAir and acquires this information from it.

IMHO the reliability of ASIAir is still a long way from being suitable to run remotely.

PMTeam@ZWO

heyjp We plan to add this feature in a future update. Thank you for your feedback.

67DuC4ai

Thanks a lot for the update. Does this update also include support for additional camera models? I'm still waiting for support for the Canon R5 Mark II.
Thanks Tobias

Luxo

Apparently not.

johnpd

Well I tried 2.5.2 for the first time. I set up to do a 1.5hr image of the Rosette using my new ASIAIR Pro. Everything worked pretty good for the first half hour, then the connection dropped. When I went back to my iPad wireless settings, the ASIAIR was still connected. I went outside next to the scope and tried several rescans, but it did not help. So I disconnected the ASIAIR, connected to my local network for a few seconds, then reconnected to the ASIAIR. It reconnected. It happened several times more. I am using the 5GHz connection. I have a TP-Link router that I intended to use a signal enhancer. I will need to get that connected to see if it will help. Otherwise 2.5.2 seems to be working OK

Moontanner

johnpd
I'm guessing you mean the ASIAR PLUS, not the PRO?

My experience is that V2.5.2 hasn't had any connection issues during >10 nights imaging while running multiple units in close proximity.
My Old PLUS, new PLUS, and Mini all connect to my home network through a network extender that has nothing but a sheet of glass blocking the Wi-Fi signal. I did try one of the portable 12v routers directly connected, although I found the signal still dropped out occasionally as it didn't have great range.
For years I never had to use an extender with the old Plus. If I use an app to look at all the network signals in my area, the increase has been huge, so I'd personally look at possible signal interference first. A strong looking signal can still suffer from momentary random dropouts and physical obstructions as the rig moves around.

Luxo

One example of an obstruction is the metal OTA - wifi doesn’t pass through it.

Wifi is basically line-of-sight - if you can’t see the AA expect dropouts.

Mike835

Subject: 2.5.2 – CAA and guide camera disconnect/reconnect issues (Duo)

Hi all,

Since updating to 2.5.2 I’ve started having persistent disconnect/reconnect issues during imaging sessions that were not present in 2.5.1. Update happened last night 16/04/2026.

Setup:
ASIAIR Plus
ZWO ASI2600MC Duo (main + internal guide camera)
ZWO CAA (camera rotator)
ZWO EAF
Celestron CGX mount

Power setup:
All devices powered externally via Pegasus power supply.
Nothing powered from ASIAIR outputs (tested to rule out voltage issues).

Connection layout:
All devices connected directly to ASIAIR USB ports except CAA through camera. May try to connect CAA to ASIAIR and connect EAF to camera USB (2nd USB 3.0 used for external storage)

Issue:
Main camera remains connected and stable
Guide camera (within the Duo) repeatedly disconnects and reconnects
CAA also disconnects and reconnects intermittently
Happens throughout the night, making guiding unreliable

Important observations:
System was stable on 2.5.1 with identical hardware and setup.
Changing power configuration made no difference.
Does not appear to be a full USB reset, as the main camera remains connected.
Issue seems to affect “secondary” devices (guide cam + CAA).
Seems to be a USB hub issue within the Duo.
ASIAIR app showing voltage warning.

Impact:
Guiding drops out due to guide camera reconnecting.
Imaging sessions require constant intervention.
System currently not usable for unattended imaging.

Question:
Is anyone else seeing similar behaviour with 2.5.2, particularly with:

ASI2600MC Duo (guide cam disconnects)
CAA instability

PMTeam@ZWO

Mike835 Hello, We apologize for the unpleasant experience you've had.
Could you please submit a bug report in the app immediately once the problem appears.
We will analyze the report to figure out the cause and find a solution.
If you have any other issues, please feel free to contact me via email anytime. My email address is tianfeng.chen@zwoastro.com.
Thank you for your feedback and your support of ZWO.

R0k9pZfT

Here we go again. I keep reporting this problem in 2.5, 2.5.1, and now 2.5.2. Super easy to reproduce. Take a photo in preview mode on the Android app. The progress circle and countdown around the shutter button disappears at 50% no matter how long or short the length of the shot. This is annoying if taking longer shots for test purposes and you want to know how much time is left. All you need to do is take an image to see it.

If it matters my equipment--I have an AM3 (not 3N), the AA+ 256GB, a 2600MC-Duo, 5-position 2" filter wheel (pre 2025), and my OTA is 448mm in focal length (RedCat 91).

Also in 2.5 and 2.5.1, and I'd bet money it's in 2.5.2 but I haven't had a chance to test. The camera angle isn't in the filename for flats, even though it's everywhere else. I also reported this with the previous releases.

Moontanner

R0k9pZfT Super easy to reproduce. Take a photo in preview mode on the Android app. The progress circle and countdown around the shutter button disappears at 50% no matter how long or short the length of the shot.

I'm running the Android app and can't reproduce this issue. The progress circle keeps counting down to 0 for me in Preview mode.

What sort of Android device are you running?

R0k9pZfT

And as an aside....I'd really like the option to force a meridian flip. Especially if I'm near the scope. I hate having to sit there until that last second when I know I have some wiggle room. Maybe let us choose to flip XX minutes early or something like that.

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.

SKNz57l3

Frames are dropping about 1 in 3. Disconnections with EFW. Just bought a DJI Power 1000V2 for stable power supplies.
All this on the new 2600MM Pro V2 and New EAF. Reset firmware, tried different WiFi, different brand new ZWO 3.0 cables, alternating the ports on ASIAIR Plus 256. Repeated on bench test with only the 2600 connected.....still dropping frames, and stopping the auto-run. Tried 10s, 20s, 30s, 60s, 120s, 180s, 300s exposures.....all around 30% dropped frame rate, and all stopping the auto-run. On top of that, when I redownloaded the app, for android, it's 850MB!!

Since I'm number 98 in posts, this is evident that you are failing at implementation. Trim the fat of your app, listen to your customers, and effect real change. I'm done with ZWO.

P.S.: Remember SONOS?....Ya, I got suckered into that ecosystem too.

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.

PMTeam@ZWO

SKNz57l3 Hello, We apologize for the unpleasant experience you've had.
Could you please submit a bug report in the app immediately once the problem appears.We will analyze the report to figure out the cause and find a solution.
If you have any other issues, please feel free to contact me via email anytime. My email address is tianfeng.chen@zwoastro.com.
Thank you for your feedback and your support of ZWO.

Eric

PMTeam@ZWO

I tried submitting a separate thread with exposure failure issues plaguing my ASI2600mm Air camera, but you won't approve the thread for some reason. Night after night now I get exposure failures during my plan sessions, single target, one filter, one exposure length. No problems guiding, no issues with power supply or anything else, and yet the camera keeps freezing up during the exposure download/processing step and then fails, the plan session ends and the mount gets parked. Last night I got about 2 hours of imaging done before the exposure failure problem, wasted one of he best nights of seeing we've had in 6+ months. I'm beyond infuriated at this point, I can't even submit the bug logs, when I select "bug report" it just says "getting logs..." and then nothing happens no matter how long I leave it. I need an answer for this, this camera is barely 6 months old and should NOT be operating like this. Clear nights are TOO RARE for something like this to be happening with a $2,500 camera.

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.

« Previous Page Next Page »