[g__day (Matthew)]

So more help for Software Bisque - trying to solve a Tracking test that Conform testing says Tracking is false for this driver accesses via TSX ASCOM X2 driver...

As requested I ran the ASCOM Conformance checker – I suspect line 102 may be the error.


Is there any way in TSX itself to see (and share to a user) what it believes the value of Tracking is from the Meade Instruments LX200 driver?

So asking Confrmance to test the X2 interface to TSX the results are below – is it line 102 in this report that is the issue – namely
14:13:26.379 Tracking Read OK False

Ivo the developer of APT sees it wants to see Tracking as reported as True to allow event trigger autofocusing to occur.

Is there any way for TSX to override the LX200 driver if it forgot to set that value and set it to true for me – so X2 interface can pick it up and pass it to APT camera and focuser control?

* * * * *
from the file (if you need the full file):
ConformanceCheck ASCOM Device Conformance Checker Version 6.6.8048.17861, Build time: 13/01/2022 10:55:24 AM
ConformanceCheck Running on: ASCOM Platform 6.6 SP2- Early Access 6.6.2.3695
ConformanceCheck Driver ProgID: ASCOM.SoftwareBisque.Telescope


* * * * *

SB keep asking me to independently Conform test the ASCOM Meade Lx200 driver - and I keep telling them this driver has never, ever worked for me - I only use the Meade Instruments (non ASCOM driver written by Meade for TSX) and I connect to TSX using the ASCOM X2 interface they created.

Hence I have stated this again as clearly as I can to all involved and shared the following screen shot - that if Software Bisque can get this driver when queried by X2 interface to return Tracking Ok and True - we are good!