Annotation off center

[donboy]

I'm using the latest version 4.1.10188 - It seems that if I'm too quick to click the annotation button then it will center on the plate solve position and eventually it will pick up on the recentered position. So it looks like I need to be patient before pushing the button.

Regards.

Don

[donboy]

Update.

I just used HC to goto NGC2903 and the Annotation centered on and stayed on the plate solved position which was off center. I then redid a plate solve and the annotation centered on the recentered NGC2903.

Annotation OFF.txt

(234.15 KiB) Downloaded 31 times

NGC2903_00001__WithAnnotations by donboysail

NGC2903_00001__WithAnnotations by donboysail

Regards,

Don

[admin]

Hi Don,

I think it is definitely timing issues of some description - looking through the log I can see that the co-ordinates reported from the mount don't update immediately, so for instance the mounts co-ordinates do not change when the Sync is sent, but a few seconds later after the GOTO command is sent, the mount's co-ordinates read back as the sync co-ordinates.

Code: Select all

Info    00:33:22.301182 #1  Mount reports JNOW, converting results position from RA=09:32:33,Dec=+21:30:48 (J2000)                                  
Info    00:33:22.380020 #1  Conversion result is RA=09:33:53,Dec=+21:24:38 (JNOW)                                                                   
Debug   00:33:22.384800 #1  Notification (Status=OK): Plate solve succeeded, position found to be RA=09:33:53,Dec=+21:24:38 (JNOW, offset of 0.09 de
Info    00:33:22.385035 #1  Field solved to RA=09:33:53,Dec=+21:24:38, field Size {Width=0.8391404, Height=0.5610582}                               
Info    00:33:23.389855 #1  Before Sync mount is at RA=09:33:30,Dec=+21:23:48                                                                       
Info    00:33:24.726613 #1  After Sync mount is at RA=09:33:30,Dec=+21:23:48                                                                        
Info    00:33:24.728828 #1  Frame center calculated at RA=09:32:33,Dec=+21:30:49 (J2000)                                                            
Info    00:33:24.729083 #1  Frame center converted to JNOW : RA=09:33:53,Dec=+21:24:38                                                              
Info    00:33:24.734066 #1  Plate solve info with center at RA=09:33:53,Dec=+21:24:38 recorded against mount position RA=09:33:30,Dec=+21:23:48, map
Debug   00:33:24.734270 #1  Notification (Status=OK): Mount synced to RA=09:33:53,Dec=+21:24:38, re-centering on target at RA=09:33:30,Dec=+21:23:48
Info    00:33:25.746301 #1  Before Slew mount is at RA=09:33:30,Dec=+21:23:48                                                                       
Info    00:33:27.453148 #1  Toolbar/Menu input : SharpCap.ViewModels.Actions.AnnotateDeepSkyAction  executing                                       
Info    00:33:27.525377 #1  Toolbar/Menu input : SharpCap.ViewModels.Actions.AnnotateDeepSkyAction  complete                                        
Info    00:33:27.577447 #1  After Slew mount is at RA=09:33:53,Dec=+21:24:38                                                                        

You can see above that the 'before sync' and 'after sync' readings from the mount are the same, as is the 'before slew', but 'after slew' shows the co-ordinates that were sent with the sync.

I suspect some additional delays in the process - which would let the ASCOM driver 'catch up' with movements of the mount - would help, but I need to think about ways to do that, since I don't want to delay everyone's progress by a few seconds just to fix an iOptron specific issue.

cheers,

Robin

[donboy]

No problem.

Thanks,

Don

[admin]

Hi Don,

I have made some changes that I hope will help here - basically making sure that the mount co-ordinates get updated after the sync and slew steps are complete, these will be in next week's update. Also there is now a 'mount settling time' setting which can be used to add a delay after the slew. I suppose it is still possible that we might have an issue if the mount responds to the sync in a delayed manner - we will have to see.

cheers,

Robin