Marcus,
Thanks for your suggestions. Point one already done - agrees totally with yours 227 after two auto calibrates to be sure of consistency.
Point 2 - The Home and park are set to 119 - and I would say are accurate to within a degree. When TSX solves the dome required position and sends it anywhere - say 158 Az - from my markings around the dome lands exactly where it is meant to - within say 10 mm or better - checked this every 10 degrees from 0 to 360!
The alignment misses are only in TSX controlling things and only after a meridan flip where it will be generall around 10 - 15 inches out when close to the horizon; very close to the SCP its about 26 inches - with the DEC arm parallel to the ground - which I infer means it definitely missed the meridan flip!
I might posit your Paramounts have well written drivers that correctly pass on side of Meridan to the SkyX. You'd be pretty upset if $20K of mount and software couldn't understand a Meridan flip wouldn't you!
Software Bisque wrote the ASCOM X2 driver - but for some reason it doesn't support the Vixen SkySensor200-PC ASCOM driver - when you try to connect the software just times out.
I might try it with TSX -> Maxpoint -> SS2K and see if it can connect indirectly through the Maxpoint hub and what its behaviour is around Meridan flips.
Regardless, when it connects to a generic LX200 mount the SS2K can emulate this and point fine - however TSX misses the Meridan flip whilst it appears MaximDL realises that it has happened and accounts for it in the Dome Solve correctly.
So to me the reversal of the Xt parameter alone fixing everything tells me geometry is absolutely correct however algorith is incorrect or relies on a Driver parameter that isn't being set correctly - the TSX perhaps just reads this side of Meridan parameters whilst MaximDL calculates it! The guys who responded to my issue (Chris Rowlands - I believe has written a driver or two so likely knows wat he is talking about).
Matthew
|