TIME DIFFERENCES CAUSING ISSUES

[Richard Sands]

[Richard Sands]

[Jason Poitras]

Hi Richard,

I will test this today using your time zone to see if I can reproduce it. I'll let you know what I find.

[Jason Poitras]

I tested using your time zone and I did find that when I sync up the Tracker Xtreme, I always get the warning that the time differs by more than two minutes.

I then set an Archer and an Allegro to the your time zone and synced, and I didn't receive any time warnings.

So the conclusion is that this is a Tracker Xtreme only problem and we'll log it a bug. We'll look at it next time we update the MicroSurvey Transfer program.

For now, you have to live the message.

[Richard Sands]

Thanks Jason
Good to know whats going on.
regards
Richard

[Richard Sands]

[Richard Sands]

I've played around with this and unticked daylight saving, reset the clocks to the exact second, (Haven't tried complete timezone change) and it still persists.
Is this just a Tracker Extreme issue?

[Richard Sands]

The time differences issue is a real PAIN!
It strips the linework from the imported FG data and I just end up with points.
I allowed MSCAD and MS transfer to do its default stuff and the linework just doesn't feature at all.
I then started a new 2009 job and imported the data from the raw file.
The thing fell over as there were missing points. (in the raw data ie - not in the FG job on Tracker)
I chased those up from Field Genius and ran the raw data file.
Due to my using Multishots for all my traverse work it stalled at every Multishot and asked what I wanted to do.

It'd be nice to be able to have my linework back all connected as per my field survey and for MSCAD to recognise its own 'first cousins' command of Multishots.

I know the linework issue resolves when daylight saving ends but I cant go on leave that long.

As mentioned before the times are same to the second and same time zones on PC & Tracker.

regards
Richard

[Richard Sands]

So the conclusion is that this is a Tracker Xtreme only problem and we'll log it a bug. We'll look at it next time we update the MicroSurvey Transfer program.
For now, you have to live the message.

What is the current version of MS Transfer? I couldn't find reference to it in the Helpdesk. I;m running Oct 28, 2008.

I don't really care about the message but I do about the stripping of the linework.

Do you still have Trackers (Extremes) you can test this out on?

Since the last FG update FG has behaved oddly on my Tracker - Number pad freezes but only in FG - other applications work fine whilst FG is not.
Only way to fix it is to turn off and remove batteries.
I now find also if I want to survey ARCS that if I invoke an ARC then take the shot it changes to a LINE. I change it back to take the next shot and its reverted to LINE again. This since last update.
regards
Richard

[Jason Poitras]

Hi Richard,

You have the most recent version of the Transfer program.

We don't use the system time for anything during import, so I highly doubt that the time warning is causing any issues with the linework.

Also your explanation of what happens when you use the three point arc toggle is working correctly. We automatically switch back to line after you shoot the mid point. It has worked like this for at least two years now.

[Richard Sands]

[Matthew Fore]

[Jason Poitras]

[Richard Sands]

another year and this issue is still about but with a difference.
This year I deliberately didn't change the setting in the Tracker when daylight saving started.
I downloaded into Win 7 on daylight saving time (1 hr ahead of the Tracker) and there was no prompt re time differences.
I left it for a few days and repeated - still no prompt. I then changed the time zone to reflect the current here on Tracker and Win 7 didn't flag anything.

I then downloaded to my Laptop that is Vista and same AEST (daylight saving) and Tracker on AEST (daylight saving) and the prompt re time differences popped up.
Previous years it has been XP Pro and Vista, this year 7 Pro and Vista Business.
It sure is weird.