Solved NINA Park fail - updated ASCOM driver 7.1.26. or 7.1.2.5?

I need to correct my previous statement.

In the simulator, both the Park() and FindHome() methods are synchronous. They return only when the action has been completed.
In the documentation of the FindHome() method it is explicitly written "Return only after the home location has been found," in that of the Park() method it is not, but otherwise the method would be called ParkAsync() like the equivalent Slewing ones.
I think this is why the Slewing property documentation does not mention the Park and FindHome methods.

I found a discussion in the "ASCOM Driver and Application Development Support Forum" that highlights this issue. I hope it may be helpful to you. 
Situational awareness during park and homing operations

If you decide not to change the driver, is there any other way to know for sure, from a software application, if the mount is still moving? 
I can modify the behavior of N.I.N.A. for this purpose.

Thank you,
Mauro.

Hi Stefano,
this version works very well, both on Parking and on Finding Home.
Both NINA and a custom utility I've build works as expected.

Only the issue, already present in the previous beta but not on the official release, about ALT-AZ coordinates always zero still exist, as you can see in the attached image.
Anyway it is usefull (I show the current scope position in my control panel) but not madatory.
Slewing to AltAz coordinates work as expected (eg. pointing to Zenit for sky-flat). 

Thanks to you and your developers for the fix.

Clear sky.

Mauro.




 

Hi Stefano,

was this fix already officially released? I currently have version 640 SP7 installed (sent to me by Luciano on the 25.04.) which fixes the AltAz coords always being 0. I'm a bit lost with all the different unofficial versions.
However I think I'm still experiencing the same issue described here, i.e. FindHome ending before the mount has finished slewing, with Starkeeper Voyager.

Best regards,
Samuel

is there going to be a release for this version with the correct alt-az coordinates displayed in the app?

thanks

toriqo wrote:

is there going to be a release for this version with the correct alt-az coordinates displayed in the app?

thanks
 

I would also like to have a new version with both bugs fixed.
It has been more than seven months since the fix and we still have to choose between one bug and the other.

C.S.