Hi John, Thanks for your thoughts. My version of CdC is 3.0.1.4, ASCOM V5.0 with MeadeClassic V5.0.0
I have experimented a bit, results are: 1. Changing coordinate management in POTH ( it was on 'local')does not change where the telescope goes when driven from CdC, still always slews to to J2000 coords. Isn't POTH just an on-screen hand piece + dome control + focuser control driving the scope via ASCOM. Also acting as a hub for several inputs. I can find no specific mention of the coordinates setting in POTH Help, but I understand it only indicates scope capabilities and does not affect anything. 2. Using the CdC 'Meade.tid' plug-in (not using ASCOM at all), the scope still goes to J2000. 3. Using the ASCOM driver with HNSky (www.hnsky.org), the scope goes to 'apparent', as it should. I think this issue has nothing to do with the ASCOM driver, but with the coordinates sent by CdC. I have ticked the 'Apparent' setting in the CdC setup, whatever I select makes no difference, ASCOM or meade.tid. Using 'Expert Mode' with current data: Still slews to J2000, but calculates correct apparent coordinates as can be seen in 'About xxx' after selecting an object. I have posted a report on the Skychart bug_tracker. So far no reaction. Maybe this is an intentional feature for reasons unknown to me? There's a bloody awful lot I don't know! Annoying to some degree, as I have spent a lot of effort to get the LX200 pointing much better than Meade-usual. And I like the feel and functionality of CdC a lot. Cheers Rudi --- In [email protected], John Mahony <[EMAIL PROTECTED]> wrote: > > I believe I've seen this issue (J2000 vs apparent) mentioned in ASCOM documentation somewhere, so you might dig around in the settings for the LX200 driver and see if there's a setting for it. > > Since ASCOM (and many charting programs) was originally developed starting around 2000, I guess this is an issue that wasn't considered too important originally, but it will gradually become more relevant. > > I was just browsing through some other ASCOM drivers and noticed that if you connect via POTH there's a setting under "coordinate management" where you can choose the epoch, or "local". If you haven't used POTH before, it acts as a hub so you can have several programs all connected to the same scope. So in CdC you use the POTH driver, and then in the POTH settings you choose the LX200 driver. > > -John
