Jump to content

  •  

CNers have asked about a donation box for Cloudy Nights over the years, so here you go. Donation is not required by any means, so please enjoy your stay.

Photo

Ascom error

  • Please log in to reply
8 replies to this topic

#1 aneeg

aneeg

    Apollo

  • -----
  • topic starter
  • Posts: 1,319
  • Joined: 24 Jan 2016
  • Loc: Nesodden, Norway

Posted 31 March 2020 - 07:32 AM

I use CdC to controll my mount but gets the following error: The ASCOM driver reort an error: SyncToTarget failed.

 

 

Arne



#2 PDB

PDB

    Vostok 1

  • -----
  • Posts: 111
  • Joined: 18 Nov 2016

Posted 31 March 2020 - 08:10 AM

This means that the mount refuses the sync command sent by CdC. Not all mounts can sync on every location/object in the sky.

 

EQmod usually can, but if you have to many syncs, conflicts can arise.

SynScan normally will only sync to the list of known objects in the mount, and I doubt if it can accept more than 3 syncs. (Not sure never tested)

 

Paul



#3 pkrallis

pkrallis

    Mariner 2

  • *****
  • Posts: 261
  • Joined: 06 Oct 2007
  • Loc: Colorado Springs, CO

Posted 31 March 2020 - 09:48 AM

When I first started using EQASCOM I recall using up to 10  but eventually realized  more than 4 was a waste of viewing time.



#4 555aaa

555aaa

    Vendor (Xerxes Scientific)

  • *****
  • Vendors
  • Posts: 1,666
  • Joined: 09 Aug 2016
  • Loc: Lynnwood, WA, USA

Posted 31 March 2020 - 10:39 AM

Most ASCOM drivers have an error logging check box in the dialog box that appears in the ASCOM chooser window. This is built into the ASCOM mount driver template. So turning logging on will capture what has happened in the mount upto the error event.

#5 aneeg

aneeg

    Apollo

  • -----
  • topic starter
  • Posts: 1,319
  • Joined: 24 Jan 2016
  • Loc: Nesodden, Norway

Posted 31 March 2020 - 12:33 PM

I have used this combo ( ascom + cdc ) for several years with no problems.

Now something went wrong.

 

Arne



#6 mclewis1

mclewis1

    Thread Killer

  • *****
  • Posts: 19,969
  • Joined: 25 Feb 2006
  • Loc: New Brunswick, Canada

Posted 31 March 2020 - 01:38 PM

Arne,

 

In order to save some time I might just un install and re install CdC, ASCOM, and the telescope device driver, and see if that fixes things. If it doesn't I would capture the error log as 555aaa mentioned and submit a question with the log in the ASCOM Talk forum on GroupsIO.



#7 aneeg

aneeg

    Apollo

  • -----
  • topic starter
  • Posts: 1,319
  • Joined: 24 Jan 2016
  • Loc: Nesodden, Norway

Posted 31 March 2020 - 01:44 PM

I was thinking about doing the same, Mark.

Thanks!
 

Arne



#8 aneeg

aneeg

    Apollo

  • -----
  • topic starter
  • Posts: 1,319
  • Joined: 24 Jan 2016
  • Loc: Nesodden, Norway

Posted 01 April 2020 - 12:52 PM

I realised that my iOptron driver has not been updated.

 

Arne



#9 aneeg

aneeg

    Apollo

  • -----
  • topic starter
  • Posts: 1,319
  • Joined: 24 Jan 2016
  • Loc: Nesodden, Norway

Posted 02 April 2020 - 08:20 AM

It was the iOptron driver. Ready for the comet tonight!
 

Arne


  • mclewis1 and Raginar like this


CNers have asked about a donation box for Cloudy Nights over the years, so here you go. Donation is not required by any means, so please enjoy your stay.


Recent Topics






Cloudy Nights LLC
Cloudy Nights Sponsor: Astronomics