Hi John
weird thing going on. Here in Australia, the move to Daylight Saving has been delayed by 1 week, because the States are going to synchronise the event.
My computers all changed, so I have moved them back an hour, but in CCDAP, the transit of objects still appears to be behind time. For example, I am tracking one object which is about 10 minutes away from crossing the meridian, at 11.20, but CCDAP is saying that it transits at 10.30..exactly one hour out.

I am not sure what is happening here!

cheers
Martin

Check with Software Bisque - that is where the transit info comes from. I suspect Australia didn't notify them of the last minute change <g>

Oh, I see. thanks John

One other option is to just set the time on your imaging computer to UTC and never have to deal with DST again.

Thanks Jack..that's a good idea.

However John, I have set my imaging PC i.e The Sky, such that the Virtual Sky matches the actual sky to fix this problem. So if that is the case, then why am I still getting transit times 1 hour earlier than scheduled. I mean, even the PIR is rotating 180 degrees because it thinks the object has gone across the meridian. Surely, if the time on the PC, matches local time, and the virtual sky matches the actual sky, this should not occur?
cheers
martin

Jack/John
I tried your suggestion...but CCDAP still has local times showing, not the new UTC times.

Martin,

CCDAP gets the time from the PC in whatever format the PC is set up for. There are no time conversions in CCDAP. Perhaps another CCDAP user with a GMT setup can jump in.

On our scopes in SkyNet we just set the computer that controls the scope to UTC. But there is a trick<G>. Then go into The Sky and go to Data and Location. If you scroll down and select User Location you can put in your Obs Lat and Long, THEN on the right side yo see a Time Offset box that will be set to the time zone corresponding to your location. Set that to Zero (0). You should now run off UTC which at first is a little cumbersome but you soon get used to it.

Clarification (since I had not done this in awhile). Select Data/Location on The Sky. Have your Obs location entered on the initial window. NOW select the Tab "User Defined". Here you can enter the elevation of the Obs and also type in the time off set of 0 to get UTC. Sorry if the above post was confusing.

Hi Jack/John and thanks for the advice...thought I would close this off.

The core problem was that the transit times in CCDAP were all 1 hour out...so consequently I lost data or could not set up a sequence until I sorted it out.

Thing is...I did sort out the problem...that was fairly easy to do since the real sky view mirrored the virtual sky view, however, despite that the transit times were still wrong. It was not until I quit the CCDAP program and restarted it (rather than just expecting the timings to refresh by disconnecting and then reconnecting) did the changes reflect in that program. Oh hum.

sorry to have bothered you

Martin