GOTO's UPDATE WHAT?
Re: GOTO's UPDATE WHAT?
I'm using the following mount..
iOptron HAE69 B/C .
It was modded by iOptron to give me a WIFI connection other than the iMate WIFI.
It has been flawless for two years.
Unless SharpCap is reaching for Astap which is left over from the time before the SharpCap plate solve.
I have no idea what star map/ plate solve it would be using.
I'll check for the settle times and adjust it a tad to see if that may help.
Thanks and next clear night I get I'll check it again.
iOptron HAE69 B/C .
It was modded by iOptron to give me a WIFI connection other than the iMate WIFI.
It has been flawless for two years.
Unless SharpCap is reaching for Astap which is left over from the time before the SharpCap plate solve.
I have no idea what star map/ plate solve it would be using.
I'll check for the settle times and adjust it a tad to see if that may help.
Thanks and next clear night I get I'll check it again.
- admin
- Site Admin
- Posts: 17580
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: GOTO's UPDATE WHAT?
Hi,
I checked your log from the other day and can see that SharpCap is using its own plate solving engine (SharpSolve), not Astap, so that is fine. Anyway, Astap will produce correct results if it is configured.
One thing you can try is to turn on the option to log additional information about plate solving (bottom check box of the list in the 'Logging' page of the settings). Once that is on, SharpCap will save the images sent to the plate solving engine along with additional logging of the plate solving results, etc. This helps gather together everything needed to check plate solving is working OK. With this on, SharpCap will save all the information for each plate solve in a folder named something like
If you can send me the files from one of those folders corresponding to a failed attempt to center, and the main SharpCap log, I can hopefully dig a little deeper.
thanks,
Robin
I checked your log from the other day and can see that SharpCap is using its own plate solving engine (SharpSolve), not Astap, so that is fine. Anyway, Astap will produce correct results if it is configured.
One thing you can try is to turn on the option to log additional information about plate solving (bottom check box of the list in the 'Logging' page of the settings). Once that is on, SharpCap will save the images sent to the plate solving engine along with additional logging of the plate solving results, etc. This helps gather together everything needed to check plate solving is working OK. With this on, SharpCap will save all the information for each plate solve in a folder named something like
Code: Select all
C:\Users\<your user name>\Desktop\SharpCap Captures\PlateSolveImages\SharpCap 4.1.14247.0 started at 2026-03-31T16.44.50.1874364+01.00
thanks,
Robin
Re: GOTO's UPDATE WHAT?
Have added another log from another night of trying to figure this out. I have shipped the mount back even though I do not think it has any issues. iOptron HAE69 B/C has been a great mount so far.
Going to wipe out ASCOM and SharpCap now. Regedit here I come.
Funny thing about all this. SharpCap complains once in a while about the mount yet I never lose connection ( WIFI CONNECTED ) with Commander and or ASCOM. That is a little strange too. I say that because SharpCap never loses the connection either. It slews the mount all around to each target just fine until time for a plate solve. Most the time stars are centered in the cross hairs and then after a few seconds SharpCap recenters the star off center. I can even place the star dead center with the controls myself. As soon as I do that SharpCap again moves the star or object back off center. SharpCap has a different idea of what is the plate solve center for the image.
I basically give up on this.
When the mount comes back we will see ,but I truly have doubts about it being the mount and or anything else but SharpCap at this point.
Again I did add this one last log from my work on the issue last night.
I also haven't done this one yet but will next outing.
" One thing you can try is to turn on the option to log additional information about plate solving (bottom check box of the list in the 'Logging' page of the settings). Once that is on, SharpCap will save the images sent to the plate solving engine along with additional logging of the plate solving results, etc. This helps gather together everything needed to check plate solving is working OK. With this on, SharpCap will save all the information for each plate solve in a folder named something like "
Code: Select all
C:\Users\<your user name>\Desktop\SharpCap Captures\PlateSolveImages\SharpCap 4.1.14247.0 started at 2026-03-31T16.44.50
Going to wipe out ASCOM and SharpCap now. Regedit here I come.
Funny thing about all this. SharpCap complains once in a while about the mount yet I never lose connection ( WIFI CONNECTED ) with Commander and or ASCOM. That is a little strange too. I say that because SharpCap never loses the connection either. It slews the mount all around to each target just fine until time for a plate solve. Most the time stars are centered in the cross hairs and then after a few seconds SharpCap recenters the star off center. I can even place the star dead center with the controls myself. As soon as I do that SharpCap again moves the star or object back off center. SharpCap has a different idea of what is the plate solve center for the image.
I basically give up on this.
When the mount comes back we will see ,but I truly have doubts about it being the mount and or anything else but SharpCap at this point.
Again I did add this one last log from my work on the issue last night.
I also haven't done this one yet but will next outing.
" One thing you can try is to turn on the option to log additional information about plate solving (bottom check box of the list in the 'Logging' page of the settings). Once that is on, SharpCap will save the images sent to the plate solving engine along with additional logging of the plate solving results, etc. This helps gather together everything needed to check plate solving is working OK. With this on, SharpCap will save all the information for each plate solve in a folder named something like "
Code: Select all
C:\Users\<your user name>\Desktop\SharpCap Captures\PlateSolveImages\SharpCap 4.1.14247.0 started at 2026-03-31T16.44.50
- Attachments
-
- Log_2026-04-08T14_23_11-2200.log
- (29.92 KiB) Downloaded 4 times
-
- Log_2026-04-08T00_09_12-2720.log
- (355.19 KiB) Downloaded 4 times
- admin
- Site Admin
- Posts: 17580
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: GOTO's UPDATE WHAT?
Hi,
in the larger of the two logs, the attempt by SharpCap to send a sync command to the mount is being rejected by the ASCOM driver. I think this is because you are carrying this out really close to the celestial pole, and with a bit of polar alignment error, the co-ordinates from the plate solve have a very different RA value to the ones that the mount thinks it is pointing at. This is purely an issue because you are testing close to the celestial pole - it wouldn't happen elsewhere in the sky. Because the sync command is being rejected, SharpCap cannot then recenter the mount onto the true target co-ordinates.
The smaller log cuts off early with no useful information related to plate solving or GOTO movements.
One more thought that occurred to me on reading your post above - the fact that targets seem to land in the right position and then move off center... This could be down to two things
1) SharpCap doing the plate solve + sync + re-goto and that moving the target off center
or
2) some sort of backlash in the movement of the mount, which might get taken up once the mount settles back into tracking.
When you have the mount back with you, you could test by unticking the sync/regoto option and seeing if the effect persists or not.
cheers,
Robin
in the larger of the two logs, the attempt by SharpCap to send a sync command to the mount is being rejected by the ASCOM driver. I think this is because you are carrying this out really close to the celestial pole, and with a bit of polar alignment error, the co-ordinates from the plate solve have a very different RA value to the ones that the mount thinks it is pointing at. This is purely an issue because you are testing close to the celestial pole - it wouldn't happen elsewhere in the sky. Because the sync command is being rejected, SharpCap cannot then recenter the mount onto the true target co-ordinates.
The smaller log cuts off early with no useful information related to plate solving or GOTO movements.
One more thought that occurred to me on reading your post above - the fact that targets seem to land in the right position and then move off center... This could be down to two things
1) SharpCap doing the plate solve + sync + re-goto and that moving the target off center
or
2) some sort of backlash in the movement of the mount, which might get taken up once the mount settles back into tracking.
When you have the mount back with you, you could test by unticking the sync/regoto option and seeing if the effect persists or not.
cheers,
Robin
Re: GOTO's UPDATE WHAT?
Robin
Thanks for the information. I played with the setlle times a lot. Didn't seem to change anything. I have no idea what other date base it could be trying to use. The only thing I have on the PC is SharpCap for platesolving and Stellarium for a sky atlas only. I don't even use it to connect to the mount.
Right now I have to wait on this issue until iOptron sends my mount back. Wont take long.
I'm starting to think maybe iOptron Commander and ASCOM are trying to use Commanders data base and possibly confusing things with SharpCap.
I do not know and that is a wild guess.
If it would just stop that last move it makes once it has the target centered things would be great as they always were before this issue started.
Will see if by chance iOptron finds anything with the mount.
Until then.
Thanks for your input on this.
Thanks for the information. I played with the setlle times a lot. Didn't seem to change anything. I have no idea what other date base it could be trying to use. The only thing I have on the PC is SharpCap for platesolving and Stellarium for a sky atlas only. I don't even use it to connect to the mount.
Right now I have to wait on this issue until iOptron sends my mount back. Wont take long.
I'm starting to think maybe iOptron Commander and ASCOM are trying to use Commanders data base and possibly confusing things with SharpCap.
I do not know and that is a wild guess.
If it would just stop that last move it makes once it has the target centered things would be great as they always were before this issue started.
Will see if by chance iOptron finds anything with the mount.
Until then.
Thanks for your input on this.
- admin
- Site Admin
- Posts: 17580
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: GOTO's UPDATE WHAT?
Hi,
just an update that I got my ioptron CEM70 mount installed over the last week or so. In the first proper test last night, I noticed that on a couple of occasions the annotation of targets on the image in SharpCap (using the deep sky annotation tool) was off after using the plate solve and resync feature. The actual stars/galaxies were in the right place but the labels were off. I don't think this is quite what you were seeing, but interestingly similar.
I tracked the problem down to SharpCap sending the 'sync' command to the mount and then expecting the mount ASCOM driver to update immediately to take account of that. I suspect that the iOptron ASCOM/Commander system only updates the status of the mount maybe once or twice per second, so it was sometimes being requested before the update from the 'sync' had taken effect. I now have a fix for this that is in the very latest version of 4.1 (at least, I hope it will fix the issue - this sort of thing is very hard to test without clear night skies...)
Another thing that might help in your case is that after I had spotted the problem happening once, I started using screen recording software (I use OBS Studio) to record the screen showing SharpCap during each GOTO/solve/sync/recenter operation. Then, once I caught it failing again, I could go back and re-watch the recording of the problem happening alongside the SharpCap log showing what the software thought it was doing. Might be a handy trick.
cheers,
Robin
just an update that I got my ioptron CEM70 mount installed over the last week or so. In the first proper test last night, I noticed that on a couple of occasions the annotation of targets on the image in SharpCap (using the deep sky annotation tool) was off after using the plate solve and resync feature. The actual stars/galaxies were in the right place but the labels were off. I don't think this is quite what you were seeing, but interestingly similar.
I tracked the problem down to SharpCap sending the 'sync' command to the mount and then expecting the mount ASCOM driver to update immediately to take account of that. I suspect that the iOptron ASCOM/Commander system only updates the status of the mount maybe once or twice per second, so it was sometimes being requested before the update from the 'sync' had taken effect. I now have a fix for this that is in the very latest version of 4.1 (at least, I hope it will fix the issue - this sort of thing is very hard to test without clear night skies...)
Another thing that might help in your case is that after I had spotted the problem happening once, I started using screen recording software (I use OBS Studio) to record the screen showing SharpCap during each GOTO/solve/sync/recenter operation. Then, once I caught it failing again, I could go back and re-watch the recording of the problem happening alongside the SharpCap log showing what the software thought it was doing. Might be a handy trick.
cheers,
Robin
Re: GOTO's UPDATE WHAT?
Robin
OK the mount came back from iOptron with no issues found. They did update the firmware and software of the HC. That's about it. They sent me a video of it all working properly. The mount can be ruled out. Once I get things set back up I'll try things again. I have wiped out ASCOM and ShrapCap from the registry completely and reloaded things again a day later. That was a week ago.
I will try the screen recording option also and we can see how it does.
This being a strainwave mount it really has no backlash ,so I kind of don't think that could be an issue either.
My hope is your latest update of SC might solve this issue.
I will try with my current version and then update to the newest version if that fails.
So many things to do and not enough clear skies.
OK the mount came back from iOptron with no issues found. They did update the firmware and software of the HC. That's about it. They sent me a video of it all working properly. The mount can be ruled out. Once I get things set back up I'll try things again. I have wiped out ASCOM and ShrapCap from the registry completely and reloaded things again a day later. That was a week ago.
I will try the screen recording option also and we can see how it does.
This being a strainwave mount it really has no backlash ,so I kind of don't think that could be an issue either.
My hope is your latest update of SC might solve this issue.
I will try with my current version and then update to the newest version if that fails.
So many things to do and not enough clear skies.
- admin
- Site Admin
- Posts: 17580
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: GOTO's UPDATE WHAT?
Hi,
glad to hear that you have the mount back and hopefully you will get a chance to test soon.
If it now works - great, no problem. If it doesn't, the best bet to track down the cause is to combine a screen recording showing the problem with a detailed SharpCap log - the things I can think of to set up before doing this are as follows
1) Adjust the settings for the windows clock at the bottom right so that it shows seconds as well as hours/minutes. This means we can pin down stuff in the screen recording to the nearest second
2) Make sure you record the whole screen to show the clock!
3) Turn on the option in the 'Logging settings' page to log additional info about mount hardware communcation. Do this before opening the camera or connecting to the mount on the run where you intend to record the problem happening. That will create a much bigger log with all the to/from messages between SharpCap and the iOptron ASCOM driver recorded. Turn this setting back off again once you have captured your recording and log of the problem happening.
cheers,
Robin
glad to hear that you have the mount back and hopefully you will get a chance to test soon.
If it now works - great, no problem. If it doesn't, the best bet to track down the cause is to combine a screen recording showing the problem with a detailed SharpCap log - the things I can think of to set up before doing this are as follows
1) Adjust the settings for the windows clock at the bottom right so that it shows seconds as well as hours/minutes. This means we can pin down stuff in the screen recording to the nearest second
2) Make sure you record the whole screen to show the clock!
3) Turn on the option in the 'Logging settings' page to log additional info about mount hardware communcation. Do this before opening the camera or connecting to the mount on the run where you intend to record the problem happening. That will create a much bigger log with all the to/from messages between SharpCap and the iOptron ASCOM driver recorded. Turn this setting back off again once you have captured your recording and log of the problem happening.
cheers,
Robin
Re: GOTO's UPDATE WHAT?
Was able to work with it tonight. Clouds got me after a couple hours. Things are better and it works to a point of usefulness now I guess.. That said it is still not nearly as good as before. It was dead center every time on each goto all night long. Having deleted everything and put it all back seems to have helped though.
Now at least it is inside the circle on the cross hairs. May be on the edge but always in the circle. I can then hit the mount controls button in SC and solve and re sync and it puts it in the center now. Did not do that before. Before there was no telling where it would put the object. I have again attached the logs. I also after trying the current version of SC I already had from a few weeks back updated to your current version. Made no difference. At least now I'm somewhere in the ball park and not half way off the screen. If there is some fine adjustment to that last move to solve and sync I'd surely like to know.
I posted the log files but had to zip one down to post it. The two video files were too large. So I posted links to them.
https://youtu.be/MlJe0QDchlg first video
https://youtu.be/idmldADfs8A second video.
Now at least it is inside the circle on the cross hairs. May be on the edge but always in the circle. I can then hit the mount controls button in SC and solve and re sync and it puts it in the center now. Did not do that before. Before there was no telling where it would put the object. I have again attached the logs. I also after trying the current version of SC I already had from a few weeks back updated to your current version. Made no difference. At least now I'm somewhere in the ball park and not half way off the screen. If there is some fine adjustment to that last move to solve and sync I'd surely like to know.
I posted the log files but had to zip one down to post it. The two video files were too large. So I posted links to them.
https://youtu.be/MlJe0QDchlg first video
https://youtu.be/idmldADfs8A second video.
- Attachments
-
- Log_2026-04-20T22_45_37-15384.zip
- (95.2 KiB) Downloaded 5 times
-
- Log_2026-04-30T21_01_54-5448.log
- (732.04 KiB) Downloaded 4 times
- admin
- Site Admin
- Posts: 17580
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: GOTO's UPDATE WHAT?
Hi,
thanks for sharing - interesting to see what is going on.
Unfortunately I can't line up the logs with the videos - the videos show an initial offset of 2.77 degrees in one and 2.69 in the other, and those values don't show up in the logs.
However, I can see from the logs that the mount co-ordinates seem to be responding as expected during the actual plate solve/recenter operation, but from the videos something odd is going on...
In video 1, at about 33 seconds when the resync/regoto has just completed, the DEC is showing as +19:03:27, but a few seconds later at 49 seconds in, it is +19:03:33. You haven't done anything in SharpCap to move the mount in that period, so I am guessing that maybe the guiding application is commanding movements when re-enabled. I would suggest not running PHD2 at all the next time you test to simplify matters.
I'm also thinking that your initial GOTO accuracy is pretty poor in the logs and the videos - typically around 3 degrees off target when you are making a long GOTO move. While the plate solve should correct for that properly in one go, in your situation where it isn't quite working properly, reducing the initial error will help reduce how far off it is after the first resync/re-goto.
Given that the mount has tested out OK and we can therefore assume that it is moving as it should, a large GOTO error would most likely be caused by one or more of
* Poor polar alignment
* Significant cone error
* Mechanical flex somewhere betweent he mount and the camera as the telescope moves around the sky
It's definitely worth checking all of those 3 out, as they will all be specific to your equipment on the mount, so would not have shown up in the same way when the mount was tested by iOptron.
Happy to continue looking at videos/logs as we close in on the cause of this one.
cheers,
Robin
thanks for sharing - interesting to see what is going on.
Unfortunately I can't line up the logs with the videos - the videos show an initial offset of 2.77 degrees in one and 2.69 in the other, and those values don't show up in the logs.
However, I can see from the logs that the mount co-ordinates seem to be responding as expected during the actual plate solve/recenter operation, but from the videos something odd is going on...
In video 1, at about 33 seconds when the resync/regoto has just completed, the DEC is showing as +19:03:27, but a few seconds later at 49 seconds in, it is +19:03:33. You haven't done anything in SharpCap to move the mount in that period, so I am guessing that maybe the guiding application is commanding movements when re-enabled. I would suggest not running PHD2 at all the next time you test to simplify matters.
I'm also thinking that your initial GOTO accuracy is pretty poor in the logs and the videos - typically around 3 degrees off target when you are making a long GOTO move. While the plate solve should correct for that properly in one go, in your situation where it isn't quite working properly, reducing the initial error will help reduce how far off it is after the first resync/re-goto.
Given that the mount has tested out OK and we can therefore assume that it is moving as it should, a large GOTO error would most likely be caused by one or more of
* Poor polar alignment
* Significant cone error
* Mechanical flex somewhere betweent he mount and the camera as the telescope moves around the sky
It's definitely worth checking all of those 3 out, as they will all be specific to your equipment on the mount, so would not have shown up in the same way when the mount was tested by iOptron.
Happy to continue looking at videos/logs as we close in on the cause of this one.
cheers,
Robin