Sync issues after Plate Solving

A place to report problems and bugs in SharpCap
Forum rules
Please read about Troubleshooting USB Issues before posting.

*** Please do not post license keys - please report any problems with licensing to 'admin' by PM ***

Please include the following details in any bug report:

* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
nm1213
Posts: 33
Joined: Mon Feb 19, 2018 1:47 am

Re: Sync issues after Plate Solving

Post by nm1213 » Wed Sep 12, 2018 6:14 am

Robin,

I spoke too soon. No luck I'm afraid, even with the latest test build of Synscan. I'm using the latest beta of Sharpcap (3.2.5747.0). A plate solve is successful, but then I get some kind of logic error in the Sharpcap logs. This is the same error I also get in the latest official 3.1 version. I tried both.

Info: 14:07:31.7044925 Thread:#1 SharpCap.ViewModels.PlateSolveAndResync+<SolveAndSync>d__7.MoveNext() :: Field solved to RA=20:01:13,Dec=23:12:21S, field Size {Width=2.30578, Height=1.30471}
Info: 14:07:35.2116419 Thread:#1 SharpCap.ViewModels.PlateSolveAndResync+<SolveAndSync>d__7.MoveNext() :: Before Sync mount is at RA=19:51:18,Dec=28:41:39S
Info: 14:07:35.3076386 Thread:#1 SharpCap.MountProxy.ASCOM.MountWrapper.SyncTo(Double actualPositionRightAscension, Double actualPositionDeclination) :: Performing Alt/Az Sync to 20.0205516876564, -23.2059473636352
Info: 14:07:35.3086363 Thread:#1 SharpCap.MountProxy.ASCOM.MountWrapper.SyncTo(Double actualPositionRightAscension, Double actualPositionDeclination) :: Site Info: 10m, 1.29888888888889 (N/S), 103.857777777778 (E/W)
Info: 14:07:35.3386369 Thread:#1 SharpCap.MountProxy.ASCOM.MountWrapper.SyncTo(Double actualPositionRightAscension, Double actualPositionDeclination) :: Resolved to Alt/Az : -21.9112201804273, 114.563786967067
Info: 14:07:35.3676732 Thread:#1 SharpCap.MountProxy.ASCOM.MountWrapper.SyncTo(Double actualPositionRightAscension, Double actualPositionDeclination) :: Mount position before SyncToAltAz : -18.9065742843828, 119.984169899903
Warning: 14:07:35.4446755 Thread:#1 SharpCap.Base.Utilities.Logger.Warn(Exception e, String action, String additionalInfo, Boolean stackTrace) :: Exception of type InvalidValueException from Mount claimed it could SyncAltAz, but command failed... Reverting to attempting to Sync to equatorial coordinates. : set - '' is an invalid value. The valid range is: .
Stack Trace: at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in c:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 553
at ASCOM.DriverAccess.MemberFactory.MethodTargetInvocationExceptionHandler(String memberName, Exception e) in c:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 678
at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in c:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 422
at ASCOM.DriverAccess.Telescope.SyncToAltAz(Double Azimuth, Double Altitude) in c:\ASCOM Build\Export\ASCOM.DriverAccess\Telescope.cs:line 1119
at SharpCap.MountProxy.ASCOM.MountWrapper.SyncTo(Double actualPositionRightAscension, Double actualPositionDeclination) in C:\Documents\Source Code\SharpCap\src\SharpCap.MountProxy.ASCOM\MountWrapper.cs:line 460
Warning: 14:07:35.4456768 Thread:#1 SharpCap.Base.Utilities.Logger.Warn(Exception e, String action, String additionalInfo, Boolean stackTrace) :: Inner Exception : ASCOM.InvalidValueException: unspecified
at ASCOM.SynScanMobile.ConversationManager.ConverseStaticInternal(IComm comm, CommunicationStats cs, ResponseCache responseCache, CallerType callerType, Command command, ArgsChecker argsChecker, ConverseParams convParams)
at ASCOM.SynScanMobile.Telescope.SyncToAltAz(Double Azimuth, Double Altitude)
Info: 14:07:35.4996796 Thread:#1 SharpCap.ViewModels.PlateSolveAndResync+<SolveAndSync>d__7.MoveNext() :: After Sync mount is at RA=19:51:18,Dec=28:41:39S
Info: 14:07:35.5446965 Thread:#1 SharpCap.ViewModels.PlateSolveAndResync+<SolveAndSync>d__7.MoveNext() :: Before Slew mount is at RA=19:51:18,Dec=28:41:39S
Info: 14:07:35.6247950 Thread:#1 SharpCap.ViewModels.PlateSolveAndResync+<SolveAndSync>d__7.MoveNext() :: After Slew mount is at RA=19:51:18,Dec=28:41:38S


The ASCOM logs for the same period as follows:

14:07:35.016 TrackingRate Get driveSidereal
14:07:35.187 RightAscension Get - 19:51:18
14:07:35.210 Declination Get - -28:41:40"
14:07:35.220 CanSlewAltAz Get - True
14:07:35.224 CanSyncAltAz Get - True
14:07:35.300 SiteElevation Get 10
14:07:35.303 SiteLatitude Get 1.29888888888889
14:07:35.306 SiteLongitude Get 103.857777777778
14:07:35.352 Altitude -18.9065742843828
14:07:35.367 Azimuth Get 119.984169899903
14:07:35.466 SyncToCoordinates
14:07:35.483 RightAscension Get - 19:51:18
14:07:35.498 Declination Get - -28:41:39"
14:07:35.529 RightAscension Get - 19:51:18
14:07:35.543 Declination Get - -28:41:39"
14:07:35.564 SlewToCoordinatesAsync
14:07:35.598 RightAscension Get - 19:51:18
14:07:35.623 Declination Get - -28:41:39"
14:07:35.922 AtPark Get - False
14:07:35.941 Altitude -18.9048859629713
14:07:35.956 Declination Get - -28:41:39"
14:07:35.970 Azimuth Get 119.98369229368
14:07:35.985 RightAscension Get - 19:51:18
14:07:35.987 CanSetTracking Get - True
14:07:35.992 Tracking Get - True
14:07:35.995 TrackingRate Get driveSidereal
14:07:35.997 CanSetTracking Get - True
14:07:35.998 Tracking Get - True
14:07:36.000 TrackingRate Get driveSidereal
14:07:36.002 CanSetTracking Get - True
14:07:36.004 Tracking Get - True
14:07:36.005 TrackingRate Get driveSidereal
14:07:36.007 CanSetTracking Get - True
14:07:36.009 Tracking Get - True
14:07:36.011 TrackingRate Get driveSidereal
14:07:36.924 AtPark Get - False
14:07:36.942 Altitude -18.9013313382905
14:07:36.972 Declination Get - -28:41:39"
14:07:36.992 Azimuth Get 119.983041389371
14:07:37.018 RightAscension Get - 19:51:18

User avatar
admin
Site Admin
Posts: 2143
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Sync issues after Plate Solving

Post by admin » Wed Sep 12, 2018 6:18 am

Hi,

now it looks like SyncToAltAz is failing in the ASCOM driver with an error rather than quietly doing nothing. An improvement I guess, if not the one we wanted!

It may be something to do with the fact that your altitude is negative (both before the sync and the plate solved location). I can imagine the developer of the ASCOM driver writing code to give an error if the altitude of a sync is negative. I'd certainly try with a target above the horizon!

cheers,

Robin

nm1213
Posts: 33
Joined: Mon Feb 19, 2018 1:47 am

Re: Sync issues after Plate Solving

Post by nm1213 » Wed Sep 12, 2018 7:55 am

Hi Robin,

Testing during the day, so don't know where any objects are. :) Will try again tonight, hopefully the clouds will clear. Tough to do all this testing during monsoon season.

N.

User avatar
admin
Site Admin
Posts: 2143
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Sync issues after Plate Solving

Post by admin » Wed Sep 12, 2018 6:56 pm

Here's the trick for testing...

Set up mount indoors, align roughly with N/S and perform any alignment steps necessary so it thinks it is aligned.
Find an image of a target that is above the horizon.
Load the image into the SharpCap test camera 1 (you can choose the image it shows)
Connect the mount to SharpCap
Get the mount to goto that target using your planetarium software
Move a little off target so the plate solve sync has some work to do
Press the plate solve button.

Since you are already 'on target' to what you are going to plate solve the 15 degree limit is not a problem.

cheers,

Robin

nm1213
Posts: 33
Joined: Mon Feb 19, 2018 1:47 am

Re: Sync issues after Plate Solving

Post by nm1213 » Thu Sep 13, 2018 4:05 am

Hi Robin,

There's still something wrong with SynctoAZ, so having a toggle to use SynctoAZ or SynctoRADEC will still help.

Thanks!

N.

User avatar
admin
Site Admin
Posts: 2143
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Sync issues after Plate Solving

Post by admin » Thu Sep 13, 2018 5:11 pm

Actually, now that your ASCOM driver fails with an error on SyncToAltAz, SharpCap falls back to doing an RA/Dec sync which also seems to have no effect.

Unfortunately the logging from the ASCOM driver is a bit basic - it's not logging the attemt to SyncToAltAz at all and it's not showing anything about why the second sync fails.

I would suggest going back to the Syncscan devs and telling them their fix is still not working correctly, as I think I am pretty much out of things to try at this end without a mount to experiment on :(

cheers,

Robin

nm1213
Posts: 33
Joined: Mon Feb 19, 2018 1:47 am

Re: Sync issues after Plate Solving

Post by nm1213 » Mon Sep 17, 2018 3:12 am

Hi Robin,

I've been doing some more testing:

1. The Synscan app has it's own "emulator" mode that exhibits the same behaviour as with a real mount. You just need to download and install the latest Synscan app (http://www.skywatcher.com/download/soft ... nscan-app/), then go into settings, connection settings, and click the "Emulator" button next to UDP. You can then simply click connect and it will ask you for either Az or EQ mode. Note that the latest firmware available online is 1.10, which does not have the AZ sync fixes. That is a separate build (1.10.1) not released yet, but I have a copy from the app dev team.

2. I've tested the latest Sharpcap beta, and plate solve and sync does work even in AZ mode, so that's good news! However, I'm seeing some odd behaviour from Synscan that I still cannot explain.

3. The first thing I notice is that I will align the mount via a 1-star or north-level align. I'll then goto a random object from the object picker. I'll then solve and sync either using All Sky Solver. The reason for this is that Sharpcap limits the solve search radius. All sky is successful, and it is also able to sync correctly. Note, I don't do a re-slew after sync.

4. I now wait for a random amount of time... and the previous sync co-ordinates that were successfully applied now disappear, and are replaced by some random co-ordinates. I then need to run a solve + sync again, and the sync co-ordinates once again get applied. Sometimes the random co-ordinates appear after a minute or two, while other times it takes up to 45-60 min for the synced co-ordinates to be lost.

5. Once the sync is successful, slewing seems to get messed up. I'll keep the slewing button pressed (in any direction), and the co-ordinates will increment/decrement as expected for a couple of seconds, and then it will again suddenly jump to random co-ordinates. I can slew in the opposite direction, and after a couple of seconds, it will get back to the synced co-ordinates. So, it clearly keeps the sync co-ordinates stored somewhere, but it gets lost for some reason.

6. I can repeatedly sync, slew, etc for a few times... until the sync suddenly stops working, and any attempt to sync is just ignored. At this time I need to redo a one star alignment, and sync starts working again...

7. This behaviour is present both in AZ and EQ modes. It seems like the mount is using these sync co-ordinates in some strange additive way with it's alignment/pointing model.

8. Also note that you must disconnect the mount within All Sky Solver once you sync due to a defect where All Sky keeps setting tracking ON after a sync. This overwhelms the mount and will not allow it to slew or GOTO unless it is disconnected from All Sky.

I'll continue to work with Synscan dev on these issues, but thought I'd give you an update on where we are. To summarise again, Sharpcap sync does work. However, it is intermittent, and sometimes syncs are ignored until I redo at least a 1-star align. Furthermore, an emulator is built-in to the Synscan app, which means you don't need a physical mount to test/repro.

Thanks in advance!

N.

User avatar
admin
Site Admin
Posts: 2143
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Sync issues after Plate Solving

Post by admin » Mon Sep 17, 2018 5:52 am

Hi,

thanks for the hint about the emulator - that sort of thing is very useful to know. It does sound like a bug in the ASCOM driver that is perhaps triggered by the Sync functionality - hope that you succeed in getting it fixed.

cheers,

Robin

TheSeapiglet
Posts: 3
Joined: Tue Jul 31, 2018 7:58 pm

Re: Sync issues after Plate Solving

Post by TheSeapiglet » Sat Sep 29, 2018 10:17 pm

NM1213, I've been having a similar issue with the plate solving not syncing with the AZ EQ6-GT. Looking back through these posts it sounds like it isn't a Sharpcap issue, but if you resolve it would you mind posting about it here? I'm getting sick of the mental arithmetic every time I need to correct by a degree or two!

User avatar
oopfan
Posts: 387
Joined: Sat Jul 08, 2017 2:37 pm
Location: New York
Contact:

Re: Sync issues after Plate Solving

Post by oopfan » Mon Oct 01, 2018 12:48 pm

N.,
I've configured the mount to 1.17.55N and 103.51.28E. Not sure why that translates to 1.29N in the mount. I'll double check.
My guess is that "1.17.55N" is in units of degrees, minutes, and seconds whereas "1.29N" is degrees. To translate do this calculation:

deg + (min + sec / 60) / 60
= 1 + (17 + 55 / 60) / 60
= 1.2986

That is pretty close to "1.29N". Good enough for government work as they say.

Brian

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest