Using my PM2's and PM3's together in A.S., my PM3 files(RINEXED in from my laptop), works great.

Very little in residuals and the repeat vectors are spot-on.

UNTIL, I do an adjustment. Then I get a shift of 3 feet south and 1 foot west with any data associated with the PM3 data.

If I remove the PM3 data, I get no shift. If I isolate the PM3 data, I still get the shift(PM2 base 1/2 mile away with a 1-1/2 hour session a 45 minute break and another 45 minute session).

First off, isn't a 4' shift an awful lot for an adjustment, after what appears to be a tight processing of the data and all fixes and very small residuals?

Could the problem be a possible result of making a Rinex from my laptop?

ON another direction, does anyone know of a way to once and for all, make GNSS use Orthometric and ONLY Orthometric heights, without having to reset the option for each individual project(which I always forget to do)?

I've placed my PM2 data for the day into GNSS. The results are very interesting, in that the "shift"(?), occurs at the processing stage and virtually all the resultant data suffers from much larger residuals(.5' to 4').

I wonder how may Promark users are using 2 or even 3 generations of Promarks in their PostProcessing software?


Modified By John Francis on 11/14/2006 at 11:07 AM

John

we use PM2, PM3 and Mobile Mapper Pro (and Topcon L1/L2) data combined all the time in Ashtech Solutions and have never experienced anything like you mentioned. Although I do have GNSS on the machine, I still use AS for my processing and adjustments.

Is the problem with GNSS?

No.

realistically the problem is with sats 9, 26 & 29. I haven't checked the elevations but venture that these sats were low and full of interruptions.

When I block them, I get the same shift in A.S.. I just get the shift at the processing level(same as GNSS does without blocking those sats).

I'm just surprised at the amount of shift between the two softwares, with the same data. I have a hunch that GNSS, might be correct.

ANYWAY, I just finished traversing all the GPS points(about 2-1/2 miles total) and shall see.

After traversing everything, it looks like the adjustment in A.S., as well as the initial processing in GNSS, is correct(with minor changes in the adjustment).

It's just that I've never seen such a difference after adjustment before. It's always been a few tenths or so, at most.