Community Forums

Community Forums

Share:
Notifications
Clear all

SP80 Elevation Error  


P90guy
Posts: 2
Member
(@p90guy)
FNG
Joined: 1 year ago

We're running SP-80s with Survey Pro on Ranger 3s, and keep having an elevation problem. A check with the RTK rover gives us a cut (always about 0.3'). We can't find a setting in either the rover or that data collector that would produce a 0.3' rod-height offset. Only solution so far has been to delete the GPS receiver profile from the data collector and re-enter it. Ran into a similar problem while running 2 rovers off the same base; the guy who started the base checked in fine with his rover on a known point, but the 2nd guy's rover would have the same +/- 0.3' elevation error. Solved that by having both guys start the base, then their rover. Seems likely that the issues are related. Anyone else run into this problem? Know a solution?

4 Replies
Bill93
Posts: 6166
Member
(@bill93)
5,000+ posts
Joined: 10 years ago

I don't know the equipment, but wonder if somehow they end up using different geoid models that might differ by that much.

Reply
Lee D
Posts: 2332
Member
(@lee-d)
1,000+ posts
Joined: 7 years ago

Sounds to me like the erroneous rover is getting a phase center coordinate over the radio and treating it like a position at the ARP.

Reply
1 Reply
P90guy
Member
(@p90guy)
Joined: 1 year ago

FNG
Posts: 2

That's one of my suspicions, too, as the typical error we've seen is 0.28', which is what the software is telling me is the offset difference between the phase center and the ARP. But again, no indication as to why, or what to do about it.

Reply

Javad GNSS

Lee D
Posts: 2332
Member
(@lee-d)
1,000+ posts
Joined: 7 years ago

In the two rover scenario above, did the second guy have the base point in his collector as a control point? If so I'd do a test where the base point isn't present in the rover. I don't know Survey Pro, but it seems like a logical test.

Reply
Scroll to Top