Hello ASIAIR Users,
I had previously posted a similar AB Forum topic and it did not (as far as I know to date) receive feedback / commentary. This entry adds a bit more info. A few weeks ago, I also posted a like entry on the ZWO ASIAIR Forum, and have not seen any response. Not receiving any feedback / comment / correction from ZWO is particularly disconcerting. I am a "traveler" and rely solely on my ASIAIR-Plus to accomplish my data acquisition. Since 2021, my ASIAIR functioning has been rock-solid. It has done everything I need.
One night - a little while back, I forgot my tablet at home and used my iPhone to run that night's session. The software required that I update to v2.1.2. During the session, there were a few glitches, which I attributed to using my phone. The next night out, my tablet had to update to v2.1.2 ... and the real problems began ....
Specifically, my ASIAIR-Plus Autorun session was (quite often) interrupted with an error message informing me that my EAF had disconnected, and that it needed to be (physically) re-connected. My EAF was not physically disconnected, but I re-connected it in the software. My cables are good. Simultaneously, my Autorun sequence stopped and reset to "0." My main camera disconnected in the software and the main screen returned to Preview. After that night, I saw that v2.1.4 had been released and hoped that whatever the problem was that I was experiencing would have been corrected. It was not, so I reverted to using my ASIAIR-Pro, which - for some reason unbeknownst to me - did not need to update. That night went perfectly ... and I thought that perhaps my ASIAIR-Plus had seen a better day .... Even so, a few days ago, I saw that v2.1.5 had been released, and once again I updated hoping that the issue(s) would be resolved.
A few nights ago, I brought my ASIAIR-Pro with me (I didn't want to take the chance), but it then needed to update to v2.1.5. Alas, my ASIAIR-Pro also experienced the exact same problems. At this point, I am thinking that the issue is clearly in the software.
Has anyone else experienced these issues after updating to the v2.1.2 (and subsequent) firmware? If so, is there a known remedy?
Thank you,
Jay
I had previously posted a similar AB Forum topic and it did not (as far as I know to date) receive feedback / commentary. This entry adds a bit more info. A few weeks ago, I also posted a like entry on the ZWO ASIAIR Forum, and have not seen any response. Not receiving any feedback / comment / correction from ZWO is particularly disconcerting. I am a "traveler" and rely solely on my ASIAIR-Plus to accomplish my data acquisition. Since 2021, my ASIAIR functioning has been rock-solid. It has done everything I need.
One night - a little while back, I forgot my tablet at home and used my iPhone to run that night's session. The software required that I update to v2.1.2. During the session, there were a few glitches, which I attributed to using my phone. The next night out, my tablet had to update to v2.1.2 ... and the real problems began ....
Specifically, my ASIAIR-Plus Autorun session was (quite often) interrupted with an error message informing me that my EAF had disconnected, and that it needed to be (physically) re-connected. My EAF was not physically disconnected, but I re-connected it in the software. My cables are good. Simultaneously, my Autorun sequence stopped and reset to "0." My main camera disconnected in the software and the main screen returned to Preview. After that night, I saw that v2.1.4 had been released and hoped that whatever the problem was that I was experiencing would have been corrected. It was not, so I reverted to using my ASIAIR-Pro, which - for some reason unbeknownst to me - did not need to update. That night went perfectly ... and I thought that perhaps my ASIAIR-Plus had seen a better day .... Even so, a few days ago, I saw that v2.1.5 had been released, and once again I updated hoping that the issue(s) would be resolved.
A few nights ago, I brought my ASIAIR-Pro with me (I didn't want to take the chance), but it then needed to update to v2.1.5. Alas, my ASIAIR-Pro also experienced the exact same problems. At this point, I am thinking that the issue is clearly in the software.
Has anyone else experienced these issues after updating to the v2.1.2 (and subsequent) firmware? If so, is there a known remedy?
Thank you,
Jay