Using an LS as base

As Galileo, and Biedou get closer to being available, I consider that there are 3 options to be available for a new base.
Right now, we can use T-1M.
Or the LS.
And, in the future, the T-3.
I can see an advantage of getting another LS, with internal radio. 1 watt. (Broadcasting)
If the new constellations prove to help only some, then I can use 2 rovers, with the T-2. This could improve many things.
If the new constellations help a lot, then the base having a LS on it, could simply speed things up. Later, a set of 3 LS's could form a dynamic setup, with 1 on base, and leapfrogging the other 2.
In any case, how hard is it to use an LS on base? Is it as automated as the T-2?
I just want to talk about it, for planning purposes.
What do you think?
Or, buy another LS for base, for now, and a T-3 later. This really could expand the usefulness of things.
Some other users also seem to favor the idea of an LS on base.


Well-Known Member
It's not terribly difficult. It is not the same setup procedure as the T2. The hr or hi and the antenna phase center offset has to be taken care of by the user by adjusting the elevation of the base point to coincide with the apc. It's a simple formula.
Our solution with two LS's is just not to ever set the base up over the mark and use the m-local to adjust as getting the pole height right is easier for us.

We didn't really get all the ins and outs from the guy we bought the LS's off so still learning as we go. We follow the same process as in Adams document to start the base with the added step of recording a point in the collect screen (usually just 10 epochs) of code data (make sure you action profile isn't requiring a fixed solution etc.) and then using the "select from list" option rather than enter "enter position"

Matthew D. Sibole

Well-Known Member
The way I do it is after I start the base I then switch to a WAAS float profile and go into collect on the base and start collecting a point. Then when you are done for the day you stop collecting that point on the base. You then go to files and tap collected with points and transfer the static file of the point you collected with the base to a flash drive.

In the rover you hit one of the RTK points and hit recover base point. Then you attach the static file of the base to that base point. You then hit recover DPOS session and then it can be sent to DPOS.

I know it sounds like a lot but it is pretty fast and works well.
Does it allow the weighted average, between the shots, taken via different rovers?
I can see simply adding a letter designator to the point names. Rover 1 is direct point numbers. Rover 2 is n1..n750, and so forth.
@Matthew D. Sibole , so this is how you get multiple LS's, to post process off the same base file. I'd guess the base NEZ could be slightly different, if some time elapsed, between DPOS sessions. (For the different rovers) In that case, you'd have to assign the base value to some of the sessions.
Great thread guys and all stuff that's been on my mind too moving forward. I have been avoiding using an LS as a base because it had been purported to be not the easiest but it sounds like some of the hurdles have been figured out. Right now we have 2 LS's, a T2 and a T1M. Something's going to change when we get Galileo up and running so I'll be giving this further thought.