Problem with Meridian flip time

StevenEvan

If I'm using Autorun to imaging a target that is east of the meridian, the time to Meridian is displayed at the bottom of the screen. This time is counting down.

I then leave that AAP app on the ipad, or shut the ipad down for some time.

When I return to the app the time displayed tor the meridian flip is not updated. That is, if the time to meridian flip is showing "1 hour" and I leave the app for an 30 minutes it should show "30 minutes" when I return to the app.
However, when I return after 30 minutes, it still shows "1 hour" to the meridian.

The actual flip still occurs at the correct time.

Steve

PMTeam@ZWO

StevenEvan submit the log, we will check it.

StevenEvan

The meridian flip is taking place but the time to Meridian is showing there is 1h 21m 30s to go.

Byrdsfan1948

StevenEvan, I'm sure others here, far more knowledgeable than myself, can diagnose what is happening. When you say you "leave that AAP app, or shut down the ipad for some time" I assume what you mean is that you have disconnected your ipad interface from the ASIair Pro. As I understand it, once the ASIair is programmed to go and running, the ASIair Pro is autonomous. It just continues to chug away not caring that your interface is turned off. Hence it continues to properly count down to the MF etc. When you turn your interface back on I'm guessing that it then needs to update itself with the ASIair. I've noticed some thing like this myself and usually it seems to me that my Samsung Tablet updates with the ASIair as the latest image loads.
In any case for what it's worth, just last night I had the first chance to use the 1.6 update including the multi star guiding as well as programming my imaging session through a MF. All went perfectly. What a pleasure waking up in the morning and finding my scope parked properly in the Home position. The ASIair shut off, and when I looked at the log and guiding no issues. Plus the images were perfect until a tree branch spoiled the last few images. But I can fix that issue with a chain saw :-)) I'm very encouraged so far with update 1.6 and the resolution of so many nagging issues with 1.5.3. Including some MF issues.

StevenEvan

@asiair@zwo the logs are no longer available.
I've given you enough information to easily reproduce the problem.
Steve