Yesterday I set up the base on a known point. I did not set the control point option on the log screen, with the idea to set it as a CP in GNSS. The file name [which is auto set by the system] gave a previous day session (say ..C06.069)name extension. The rover file name came up ok (..A06.071).I noted this at the time & thought I could sort it out back at the office. I went to GNSS to process & noted that the base & rover files do not line up. I tried to rename the .069 files to .071, but that not work. In other words, data recorded yesterday was considered to be recorded at a different time. How can I correct this to process yesterdays data?

Unfortunately the solution is to make sure the clock is set properly before going into the survey program.

You will find some previous discussions on this same subject here on the message board.

I just turned on my 3 PM2s. All had the correct time instantly. One however was set to EDT not EST. That has never affected my post processing. How did Thales manage to go backwards in the progress department?

Paul in PA

In the category of "Things My Momma Never Told Me".

You can change the file extension on "B", "D" & "E" files and the date on the data does not change. Solutions still puts it on the ld date. If I open the 3 files with Wordpad I cannot see an obvious date. Here is a suggestion. Rinex the offending file, then open the "O" file in Wordpad and look at the date for each epoch of observation. If the date changes during the observation, delete the early wrong data, change the observation start time and saveas with a different name. Now bring this new Rinex file in and see if it works. If you definitely need the early data try editing each epoch date.

The date is also on the first line of each epoch in the "N" file.

If you want send me that "B", "D" & "E" file.

Paul in PA
Modified By Lawrence Paul Lopresti on 3/13/2006 at 8:55 AM

you might want to RINEX the file and chage EACH AND EVERY date reference with a simple search & replace.

I've done this in the past and it works.

A firmware upgrade would be nice to fix what appears to be a flag problem in the firmware.

BTW . . . I ca virtually "gurantee", that when the PM3 is turned on, it knows the date.

Try a little experiment:

turn on the PM3, press the settings iocn ONE TIME ONLY, press [ENTER], the press date & time . . . and virually 100% of the time, you will have the wrong date & time.

DO EXACTLY THE SAME THING ON ANOTHER DAY . . . EXCEPT, instead of hitting the settings icon once, hit one of the other icons first . . . ONLY ONE TIME, then hit the settings icon and continue through the process and the date & time will be correct.

that "deliberate" key-strokes and visual confirmation of storage information will go a long way.

Don't just "hit" the key-stroke, don't just "hit", the "hot" button . . . know that the procedure took place by looking.

When you go into a static or S & G session . . . LOOK at the file that's going to be saved and take note that it is for the right date.

These 2 things will almost ensure that the day's data will be correctly recorded and stored.