SharpCap Forums

Hello,

I have a problem with my AZ-GTi mount and Sharpcap.

The problem:
Plate solving is working, the offset is found, but at the point where my other mounts begin to slew to the target (e.g. EQ5 Goto) nothing happens with the AZ-GTi... mount does not slew but there is also no error.

In the log I found the following:
Info 00:52:18.647410 #1 Plate solve info with center at RA=23:39:39,Dec=+40:34:15 recorded against mount position RA=23:52:48,Dec=+41:00:35, mapping data is 0,0002216022,-0,0002476628,-0,0002476677,-0,0002215871,354,6592,40,37498; {X=2130,216, Y=1155,42}; 0; False, orientation is 311.82009574885 in void SharpCap.Models.PixelPositionProvider.LogMapping()
Debug 00:52:18.649404 #1 Notification (Status=OK): Mount synced to RA=23:39:39,Dec=+40:34:14, re-centering on target at RA=23:52:48,Dec=+41:00:35 (offset of 2,53 degrees) in void SharpCap.UI.NotificationViewModel.DisplayMessage(NotificationMessage message)
Info 00:52:19.662286 #1 Before Slew mount is at RA=23:52:48,Dec=+41:00:36 in async Task<bool> SharpCap.ViewModels.PlateSolveAndResync.SolveImpl(bool gotFrame, string tmpFile, CancellationTokenSource tokenSource, IMount model, SizeF? imageSize, PostSolveActions action)
Info 00:52:20.786928 #1 After Slew mount is at RA=23:52:48,Dec=+41:00:36 in async Task<bool> SharpCap.ViewModels.PlateSolveAndResync.SolveImpl(bool gotFrame, string tmpFile, CancellationTokenSource tokenSource, IMount model, SizeF? imageSize, PostSolveActions action)
Info 00:52:20.789921 #1 Toolbar/Menu input : SharpCap.ViewModels.Actions.SolveAndResyncAction complete in async Task SharpCap.ViewModels.UIAction.Execute()

The mount is connected to Sharpcap correctly and I can manually control the mount via Sharpcap without an issue.
I have up to date Sharpcap Version 4.0.9562.0 and SynScan App 2.3.9.

I use the mount with the newest V3.40 firmware, right arm in AZ mode.

I also tried to connect Sharpcap and the mount with the Ascom Device Hub but this leads to the same behaviour.

If you need the log, let me know.

Do you have any idea whats going wrong?

Many thanks!

All the best,
Philipp

Hi Philipp,

this same problem has popped up 3 times on here in the last few days - it seems that Syscan.App is ignoring the sync command (not giving an error, but not actually changing the mount co-ordinates either). That means that the GOTO movement has nothing to do because the mount already appears to be at the right co-ordinates.

I'm not sure if there are options in the Synscan app or ASCOM driver that would fix this - I have not used it and no one else has reported back on finding any workaround. There is a workaround in SharpCap to adjust the option of what to do with the plate solving result to 'Offset the mount to recenter the target' - see https://docs.sharpcap.co.uk/4.0/#Config ... %20Solving

cheers,

Robin

Hello Robin,

yesterday I had the possibility to try the 'Offset the mount to recenter the target' Option, but this also does not work.
I get an error that the conversation to the mount timed out.

Also did not find any other solution.

All the best,
Philipp

Hi,

the new error is quite different - a 'conversation timeout' message indicates that the communications between the PC and the mount is not working properly. The ASCOM driver is sending commands to the mount and not getting a reply.

If you are using a wireless connection (bluetooth, wifi) then check signal strength and move things closer together if possible. Even better, switch to a wired connection as they cause far fewer errors like this.

If you are using a wired connection then check cables and settings. Also make sure you have the latest version of the ASCOM driver and that the mount firmware is up to date, in case there were issues in older versions.

cheers,

Robin

Hello,

it definitely has to do with plate solving.
If I do not plate solve and only work with the SynScan App to move the mount everything is working fine for hours.
Only if I try to connect with Sharpcap and/or also with Stellarium the connection to the mount gets messed up.

The same thing happens if I connect from my android phone. If I use the SynScan App only everything is working fine. As soon as I connect with SkySafari 6 or 7 the App crashes and the API is not responding any more.

The workflow works with my EQ5Goto Setup without problems. Therefore I think the SynScan App and the API which comes with it is not working correctly and crashes the application when used.

All the best,
Philipp

Hi Philipp,

there was another post a couple of days ago from someone who had similar issues and had tracked it down to the Synscan app stopping responding to requests without warning or any good reason - see viewtopic.php?p=37846#p37846

I wonder if what is happening to you is similar? It certainly seems that there are glitches in the Synscan App at the moment

cheers,

Robin

Hi,

There are buggy Syscan apps ... For years, I use the old v 1.19.12 Pro without any issues (also with AZGTi, and with a Skywatcher Flextube 250). Have a look viewtopic.php?p=36892#p36892

Christian

Hi all,

I have roughly the same problem (Az-GTiX mount not responding to SharpCap slew after plate solve, although the offset option seems to work to some extent). Judging by the forum post linked above it looks like perhaps the SynScan app stops listening for the Ascom driver, if I'm interpreting this correctly.

Is there any way of bypassing the Synscan app altogether - any software that can control the mount directly to do alignment etc (in alt-az mode) and interface with the Ascom driver? I'm guessing not but worth an ask!

Bernie

Hi Bernie,

if you have a physical hand controller for the mount then you may be able to use the 'ASCOM Driver for Synscan Hand Controller' from http://www.skywatcher.com/download/soft ... om-driver/

If you don't then you *might* just get EQMOD to work - it connects direct from PC serial port to mount (no idea if it will work in AZ mode, but for those who use an EQ mount it should be OK).

cheers,

Robin

Hi Robin

Unfortunately I don't have the handset. I guess I could look into the EQMOD cable.

But - thinking about this some more - if the Synscan app is responsible for the problem, by failing to listen for the ASCOM driver input, then why is Sharpcap able to get the mount to offset? I can also successfully get Sharpcap to 'click to recentre'. It's just the Solve/Sync/Slew that isn't working (the mount doesn't do anything). I assume Sharpcap has to be communicating with the Synscan app via the ASCOM driver successfully to get it to move at all? Or am I misunderstanding something about how this works?

Cheers
Bernie