Results 1 to 4 of 4

Threaded View

  1. #1

    Default Spurious error: Property write Tracking is not implemented in this driver

    Occasionally, seemingly randomly, I am seeing this error when Scheduler tries to initiate the first autofocus of the night. It causes a dead scheduler, so I have to really watch at the beginning of the night to make sure observing starts as planned.

    If I disconnect the telescope in ACP and then go to the ASCOM configuration (TheSky driver), the "can set tracking" box is checked. Simply reconnecting the telescope to ACP and then enabling Scheduler again results in autofocus and observing starting normally, having changed nothing in the driver setup.

    I searched other threads, and there were suggestions that running a TPoint model would cause this error on a subsequent Scheduler run. I've not run a TPoint model in months. This was on a "fresh" start of all apps (ACP, Scheduler 8.3.2, TheSkyX 10.5.0, MaxIm 6.23, and FocusMax, i.e., these apps weren't left running from the previous night.

    I'm not sure if this is a Scheduler, ACP, or ASCOM bug, but it's a bug. I haven't spotted the pattern yet of when this bug will occur vs. when it will not. I'm sure there's a deterministic cause, but it seems completely random at the moment.

    Log attached.

    Attached Files Attached Files



Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Run-time error: Unable to write data to the transport connect
    By Claire Hills in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 8
    Last Post: Aug 21, 2019, 11:28
  2. AP V2 Driver - note re: tracking
    By Jim McMillan in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 1
    Last Post: Jan 14, 2010, 18:44

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts