I have been using the PM3 in a ot of "psuedo" S & G. It's great to walk to a pin, set the unit up and be off to the next point with 5-10 minutes on site.

I wonder . . . between S & G(and potential loss of lock with a reinitialization), which method would be most viable in areas which are partially open(with "adequate" sat coverage(i.e. no lock-loss on the particular points, but possible lock-loss, between points)?

Good question. I don't have a clue. Keep the unit running or start a new session at each point? I'd like to know that myself.

Hi John,

I'm interested in knowing how the new software provided with the PM3's performs with S&G, particularly the feature I seem to remember, that being the ability to finish your session with an initialization, thereby covering a loss of lock, and whether or not that terminating intialization will reach back through several, or all of the lock losses that occurred in the session. That feature would seem to favor S&G over fast static, at least to my way of imagining myself burning through a ton of shots, not caring about loss of locks beyond turning off the alarm. Then I'd be interested in knowing if it would provide the same utility for PM2's...

Good point William. Dad just offered the same theory.

I don't know that reverse processing will fix all loss of locks. You will still have to have enough uninterrupted time between loss of locks for the software to regain lock. At least that's what I'd think. But I think you are definitely on to something.

I have used the PM2 through loss-of-lock many times.

Each time, my data AFTER loss of lock would be "shifted", but otherwise good. Of course, I never worked through "multiple" losses of lock.

I'm thinking that the PM2 can be used S & G with "on-the-fly", initialization(I've done it many times), and that SINGLE loss of lock(and subsequent "shift") can often be resolved after the session is over. BUt, that in the PM2(& A.S.), a multiple loss would become very burdenson to "fix".

I like the GNSS with the S&G, but I'm beginning to absolutely hate the PM3 data with PM2 data. Sometimes, I think the GNSS & PM3 data, has an adverse effect on the PM2 data. Enough such, that I often compute the PM2 data separately, before using it in the GNSS program.

Also, the mixture of PM2 data with PM3 data means turning off a lot of vectors, since one of the main benefits of the PM3, is to get off a point faster(too fast for PM2 data).

I now understand that the GNSS software is designed primarily for the PM3’s and supports some additional data collected by the PM3’s.

From what I have observed using data collected by PM’2 only, but processed in both AS 2.6 & GNSS Solutions is that AS 2.6 is a far superior processor for the PM 2’s. I have S&G data sets that process perfectly in AS 2.6 and fail completely in GNSS .

I guess this should not be totally unexpected. The software essentially matches the receiver. I think mixing PM2 & PM3 data may be problematic especially if the stop and go is provided by PM2s.

I assume AS 2.6 will download and process PM3 data. How well does a PM3 Stop & Go session process in AS 2.6?

A.S. will not import PM3 data without conversion(Rinex).

In the future, I think I will reserve my PM2 to use with long-occupation PM3 data. Otherwise, I seem to have to turn off too many vectors. In fact, sometimes it seems I have to turn off almost all my PM2-PM3 vectors.

Good night all
I'd like to but in with a newbie question:-
Does the mention of GNSS processing mean that the PM3 reads the GLONASS sats as well?

no GLONASS in the PM3.

if I want to do control in s&g mode, there's no distance counter like in Static, so how long to occupy?

In Trimble a 3 minute PPK shot equals a Faststatic position. Not much point in S&G if you have to initialize every shot but if you had a bunch of walk-to (or slow drive-to) monuments without loss of lock issues, S&G could be very fast and slick.

Thanks David

John,
Am I correct to assume then that PM3 stop & go data imported as Rinex into AS 2.6 loses its stop and go character?

You can actually bring PM3 data directly into A/S 2.7 without doing a RINEX conversion. I have done it two or three times.

Of course, there's not much point in bringing occupation files that are of too short a duration for successful processing in A/S but you can definitely bring them staight in.

I haven't done much of it and it may not be recommended, but I like the fact that you can switch between static and stop & go in the same session without closing the session.

The more hands-on I get with the PM3's, the better I like them.