Apology and Update on Version 2.4 Issues - Stable Version 2.3.3 Available: Page 4

Apology and Update on Version 2.4 Issues - Stable Version 2.3.3 Available

Corsair

To downgrade/rollback on Android look at this thread:

https://bbs.zwoastro.com/d/18885-how-to-downgraderollback-asiair-app-firmware-with-android

Corsair

bobpowell@northstate

https://bbs.zwoastro.com/d/18885-how-to-downgraderollback-asiair-app-firmware-with-android

Corsair

Mv9VA1ec
Android? https://bbs.zwoastro.com/d/18885-how-to-downgraderollback-asiair-app-firmware-with-android

R0k9pZfT

magore Have you tried 2.4.1? It works for me in Southern California. Turn on tracking if it doesn't turn on by itself for all sky PA. There's a whole new thread for the new beta.

magore

R0k9pZfT
I will check the tracking status. Thanks for the tip

PMTeam@ZWO

magore v2.4.1 solves the PA plate solve failure caused by exposure time limitation. You can try the latest version v2.4.1, which is currently in the testing stage. Thank you!
iOS > TestFlight https://testflight.apple.com/join/6uEyoSl3
Android > https://pgyer.com/air_beta_android

magore

PMTeam@ZWO
I was able to align tonight by slewing to Deneb without sync and manually centering by adjusting the mount. Kludge but working.

Will try 2.41.
Has 2.41 been tested for allsky pa if the pa process crossed the Meridian?

magore

PMTeam@ZWO
I am not having exposure issues with my present filters when doing PA.
However when doing a sequence in the past I switch filters to a wide uvir filter and do a dummy 1 second image at the end of a plan sequence.
Then when it slews to the next target it's not using a narrow band filter.
Would be nice to have a filter setting for slew to target plate solving.
You could avoid unneeded focusing when switching filters by offering filter offsets as as an Alternative.

R0k9pZfT

magore I've crossed the meridian in 2.3.3 and 2.4.1 during all sky polar and never had an issue. At least I think I did--the mount was at a negative angle!

PMTeam@ZWO

magore Thank you for your suggestion. We will think about how GoTo can avoid the plate solve failure caused by using filters. The filter offsets has been planned in the next iteration.
In addition, are you using v2.4.1? Are there any other problems?

magore

PMTeam@ZWO
I hope to try 2.41 tonight.
I was running 2.4 but the All Sky PA RA/DEC changing just by refreshing and without any mount adjustment wasn't new, rather it has been a reported issue by others for a long time. It may be related to the position of the first star - which is why I gave exact details in my report. I will need to check the tracking status as had been suggested when i try tonight.
Hope to have more news soon
Thanks

magore

PMTeam@ZWO
I found a new bug in 2.41

Before I started I verified I had a good GPS fix on my phone.

Next I started the asiair 2.41 app and checked my AM5 mount location settings as I always do.

It showed utc-5 rather then the correct utc-4.
Multiple sync attempts and asiair app restarts did not fix the error in UTC offsets. I tried over period of about 10 minutes.

What fixed it was simply to open the zwo sky Atlas app and only look at the AM5 settings, which showed utc-4.
Next without changing anything I exiting the Atlas

Lastly I opened the asiair app and now it was showing the correct utc-4 in the AM5 mount settings.

Here are screenshots unfortunately they are out of order as a result of the upload. The utc-4 is the last one. The utc-5 ones preceded that.

magore

PMTeam@ZWO

Tried all sky pa on 2.41

Still has the RA and dec issue changing on refresh without mount adjustment.
Submitted bug report with images and logs
Same as with 2.40 see previous bdetailed report about with my location time and target of Deneb in this thread. Except tonight was just before 11pm edt

On last comment. My mount is adjusted so that the slew from AM5 mount home to Deneb results in almost no adjustment.
The recommended correction are way to extreme. If I slew from park to Deneb it barely moves after first correction from plate solve and I have little drift

shamrock

magore

please keep us posted on this, magore – it is such an annoying bug.

jimw85044

I stepped back to 2.3.3. A bug in this release and I expect the next release. ASIAIR will not allow you to use 'Approximate Location' when starting up. I do not want my exact location stored which includes my street address used. Please fix this bug.

Jim Waters
Phoenix, AZ

Javier_Covancho

The version that is in the play store is still 2.4

R0k9pZfT

2.4.1 is in beta and available in the related discussion. https://bbs.zwoastro.com/d/23627-asiair-v241-public-beta-released

R0k9pZfT

magore Is your mount firmware up to date? If memory serves, I think 1.7.3 is the latest?

R0k9pZfT

You might move this to the 2.4.1 discussion where it'll get more visibility. I just checked my AM3 and it's showing UTC-8 appropriately.

« Previous Page