So it's fixed a few issues but created a new one. Previously when a new update was released, it was installed then the first time opened on my Android phone, a message appeared saying "checking data integrity, it'll take several minutes" just once. Now this message appears every time I launch the app. It adds around 10 seconds to the start up time. I have heard from over 20 other users with the same issue so far on facebook. This doesn't appear to affect ios devices.

I'm having the same problem. It runs the data integrity check every time znd takes close to a minute on my tablet. That's too long to wait every time I start up standing next to the scope in below freezing weather,

Unfortunately the update broke the canon 550d integration. The color channels are not saved correctly anymore (I think red and green are flipped) and there is a strange moire effect in the images. For the live stacking the old darks, flats and biases are not working anymore (it said it did not match the settings despite having the same, I suspect it's because of the mixed up color channels).

Gandalf000 same here

philipp I just confirmed the color channel swap, green and red color channel are flipped

Kevin_A So the slewing speed decrease is used for the initial target selection (i.e. slew to target) or does it have any bearing on tracking/guiding accuracy? I was wondering if there's any connection with another new feature, guide speed setting. The assumption being that with a high-inertia load and fast guide speed the mount might easily be over-corrected or sent into oscillations (which then appear in guide logs as a second order harmonic).

KF7DS I'm glad you got it to work, but it didn't for me. When you say you did a factory reset was that the firmware reset option from the app? That is what I did. I did at some point get the USB stick to work but not the camera guide camera or EAF. I know it has some type of connection because the cooling fan comes on even if it says there is no camera. I also get the "checking data integrity" msg.

Of course tonight is going to be the best conditions we've had in a couple of months and no camera :-(

Any other ideas?

Hi guys,
Can I run asiair software without the device itself ?
I want to figure out the functions without damaging any real setup.
Is ZWO ASI 585MC PRO added?
If something goes wrong can I go back to the previous version?
Thank you

Is this update happening by itself or I have to do it?
BTW I don't want to do it.

johnpd thank you very much for the info.

The location Info refresh button doesn't refresh. It shows always a wrong location. (Latitude/Longitude) on Android version 2.1.2.11.01

The Samsung tablet knows the location and show it correctly on other apps. The AM5 mount app shows the right location. It's an ASIAIR App issue.

Second problem, the app is checking data integrity from 0 to 100% on every start.

DeepSkyOne

I was told uninstall the update and download it from the zwo website. This fixed my issues

The new Android 2.1.2-11.01 public released firmware is very bugy!

Where can i download the previous version app 2.1.1-10.74 or 2.1.1-10.99? I can't find any 2.1.1 version on the ZWO officialy or beta web site.

Encountering an Autorun issue. I’ve been building a darks library with Autorun. I’ve tested this issue a couple of times now. If I set main camera gain to ‘M’ for 100 (2600mm), go to Autorun and build a schedule for X number of darks at Y exposure, but set the Gain to zero (0), and then schedule another set of darks but leave the gain at ‘Default Gain’ (changed from Global Gain in this version), it appears that the previous schedule of gain0 has been inherited as the default value rather than it being constrained to just that scheduled set. So, if I created fifty 600s subs at gain0 with first schedule, a subsequent schedule of same values but left at default gain will create a repeat of the previous set. If specify a gain value, all schedules after need to have a specific value set also. Previously, the actual gain on the camera page didn’t alter after a gain0 set and global gain remained at whatever was hard set on the camera page.

I can confirm a problem with the latest release 2.1.2 11.01 with my Canon 2000D (identified as a1500D in the Asiair)
The dimensions of the fit files are now 6020x4015 instead of 6020x4016 with previous Asiair versions. This result in a bad debayering in the Asair Apps preview but also when you process these files later.