26 replies to this topic

[Tkall]

Has anyone had issues after the recent firmware update?  My mount acted like it was possessed with a demon after the update.  

[starrycanuck]

This is the. 2.1.4 update?

Which mount were you using?

[Tkall]

2.1.4. Pretty sure that was it.

Losmandy g11

[shawngano]

Be sure to double-check your location within the app.  I had the same thing happen and everything seemed backwards; after manually setting the location it worked much better.

[Tkall]

I saw that last night and set it back to the correct location.  It was still not working correctly.  For example when aiming for m106 it was pointing at the horizon instead of straight up. 

[TXLS99]

Did you plate solve before attempting goto?

[Tkall]

Did you plate solve before attempting goto?

Of course.  It would take a shot, plate solve and state that the target was centered. The target was nowhere near the field of view. Neither the sky atlas nor an actual image would point the scope correctly.  I hope this is a mistake I was making and not a bug in the update.

[PIEJr]

I have come to absolutely hate updates. Especially anything from Windoze.

Windows blows holes in drivers from most things not from them. So apps have to be fixed or replaced.

No idea about your ASI Air. I use a Powered hub and control from a laptop.

There will be an update to the update you updated to fix the update you updated.

Watch for it.

[LiquidMan]

Any chance the date or time might be set incorrectly? I use an old tablet to connect to my ASIAir, which I basically only use for astrophotography. Sometimes if it dies while I’m out in the field, but I don’t turn it on at home and allow it to connect to WiFi, the date and time will be off. That’s caused very similar issues for me in the past. Hopefully it’s something as easy as this!

[Tkall]

Any chance the date or time might be set incorrectly? I use an old tablet to connect to my ASIAir, which I basically only use for astrophotography. Sometimes if it dies while I’m out in the field, but I don’t turn it on at home and allow it to connect to WiFi, the date and time will be off. That’s caused very similar issues for me in the past. Hopefully it’s something as easy as this!

I will check that again.  The update changed my location lat and long to somewhere in the further regions of experience.

[TXLS99]

Of course.  It would take a shot, plate solve and state that the target was centered. The target was nowhere near the field of view. Neither the sky atlas nor an actual image would point the scope correctly.  I hope this is a mistake I was making and not a bug in the update.

So strange.   After it plate solved and told you that successfully centered, was the sky atlas showing were the scope was truly pointing physically, or was the sky atlas thinking it was actually pointing at the target?

[Tkall]

It showed it was centered on the target in the sky atlas but was nowhere near it.  In fact the scope might not even move and it would plate solve and say the target was centered.  Bizarre right?

[unimatrix0]

I imaged last night and I saw the update when I turned on the AA+, but I had no issues afterwards.   

 

It's a good practice to turn off and turn back on after an update,  and resync the time and date from the app to the mount. It's possible your mount or the AA+ lost your GPS coordinates and synced the wrong location and time to the mount. 

[Tkall]

I did reset the coordinates,  maybe the time was off.

That sure doesn't explain the plate solving error though.

Edited by Tkall, 25 May 2024 - 01:42 PM.

[Bob_Gardner]

FWIW, I asked a question about this update the day before your post and received these positive responses:

 

https://www.cloudyni...iair-v214-1105/

[Tkall]

FWIW, I asked a question about this update the day before your post and received these positive responses:

 

https://www.cloudyni...iair-v214-1105/

Thanks Bob.

The update worked fine as did PA.  I didn't see the problem until I tried to goto a target.  For sure the update changed my settings and when I issued a goto, the scope did not move, it plate solved and said the target was centered.  I can understand the settings being wrong and sending the scope to a location based on those settings.  I am confused about the plate solving showing the target being centered when it was not.  As soon as it clears up I am going to take it for a run again to figure out what I am doing wrong. 

[Sam Danigelis]

Tkall, I don't think you're imagining this.  I had the same problem tonight.  Until now, my ASIAIR Plus has been seamlessly working on my Samsung tablet.  I updated my firmware to version 11.06, and immediately have had problems with location.  There is a default location that is in the firmware, approx 34 deg N latitude, 113 degrees east longitude.  I checked, and this is somewhere near Zhengzhou, China.  Very curious.  Even after "syncing to mount," and manually inputting my correct coordinates, the firmware reverted back to the default (my location was basically 34 deg N. latitude, 94 degrees W longitude).

 

Eventually, after a lot of unplugging, restarting, etc., I was able to get things to work, by installing the ASIAIR app on my Samsung phone.  Maybe my phone has location info, where my tablet may not.  But I'm pretty sure that previously, ASIAIR got location info from the CEM40 mount, which has a GPS dongle.

 

All I know is that it was working fine until I decided to go with the update.

[Zambiadarkskies]

Tkall, I don't think you're imagining this.  I had the same problem tonight.  Until now, my ASIAIR Plus has been seamlessly working on my Samsung tablet.  I updated my firmware to version 11.06, and immediately have had problems with location.  There is a default location that is in the firmware, approx 34 deg N latitude, 113 degrees east longitude.  I checked, and this is somewhere near Zhengzhou, China.  Very curious.  Even after "syncing to mount," and manually inputting my correct coordinates, the firmware reverted back to the default (my location was basically 34 deg N. latitude, 94 degrees W longitude).

 

Eventually, after a lot of unplugging, restarting, etc., I was able to get things to work, by installing the ASIAIR app on my Samsung phone.  Maybe my phone has location info, where my tablet may not.  But I'm pretty sure that previously, ASIAIR got location info from the CEM40 mount, which has a GPS dongle.

 

All I know is that it was working fine until I decided to go with the update.

This is weird.  So I had exactly the location problem issue you describe (including being in Zhengzhou) with the previous firmware. It was driving me mad.  The current firmware update seems to actually have fixed my issue.  

[Tkall]

And I thought I was crazy....now how do I get out of this straitjacket?

[mrlovt]

Just another data point:  When I start the ASIair it always reverts to coordinates showing N 39 54'35"  E 116 23' 50", somewhere in Beijing, China (I'm near Nashville TN, USA).  Oddly enough, it doesn't change the time zone from -6, obviously incongruent with the location.  I'm connect to the ASIair via my Windows computer using the Andriod emulator Bluestacks.

 

I have my location set correctly inside bluestacks and in Windows, and location service is allowed.  If I tell the AIR to refresh location, the popup indicates that it has success, but it still shows the incorrect Beijing coordinates.  When I correct the coordinates manually, it remains correct when I proceed, but any restart of the device means I have to manually enter the coordinates again. 

 

I'm not aware of any way to have the AIR retrieve coordinates from the mount.  The synchronize button sends the the ASIair location info to the mount.

 

Mount (Losmandy G11G with Gemini II) and ASIair are connected via Ethernet. I had no issues for years.  The change happened when I  had a hard drive crash and Windows re-install, which meant a re-install of everything, including bluestacks and the new version of ASIair.  I haven't changed any settings that I'm aware of, and it's simple enough software so I  have thought I'm probably missing something obvious. Seeing that others have had the same issue, now I wonder...

[mrlovt]

I just got a message from Tech@ZWO: "Sorry for the trouble, this is the bug in V2.1.4, we will fix it and release the new version as soon as possible."  So, it's on their end for sure, and on their radar.

 

For anyone reading this thread who has encountered the same problem, you aren't alone.  ASIair and Losmandy have (until this update) worked very well together.  Once the mount is set up and ASIair connected, you should be good to go. 

 

If you are having problems with the ASIair, reach out to the ZWO user group.  ZWO support gave me that answer within a couple of hours. 

 

In the case of questions about Losmandy/Gemini check out the Losmandy user group and the Gemini II user group.  For all of these, I have always had a pretty quick answer to any question I've had from knowledgeable users and manufacturer's representatives.

[Sam Danigelis]

I just got a message from Tech@ZWO: "Sorry for the trouble, this is the bug in V2.1.4, we will fix it and release the new version as soon as possible."  So, it's on their end for sure, and on their radar.

 

Thanks for the link to ZWO user group.  Browsing through the posts, this problem is mentioned by users, and acknowleged by ZWO tech, as you said.  Let's hope they fix it soon.

[DeepSky Di]

There was an update for me last night, 2.1.5, which claimed to have bug fixes

[GiffS]

I got that update as well. Happy to report that although I had some odd plate solving issues during my PA routine once that was sorted out, everything including guiding was excellent.

There was an update for me last night, 2.1.5, which claimed to have bug fixes

[Astro Sky]

Did update 2 night ago. Work great,zero problem. Thanks ZWO team.