Significance of Base Reference Frame

SynGeo

SynGeo

Member
Hi All, I'm running two LS's over LTE and have been experimenting with different settings for the last week. I'm curious about the significance of the base reference frame. For a time, I was using WGS84, because I figured that was the native data state. I switched the NAD83(2011) the other day since that seems to be the standard and started to notice some little differences, but I'm not sure that they are related to the base reference frame as I've been changing other settings as well. The anomaly: When shooting using a boundary profile, I'll let it run for around 60 seconds in beast mode. When I'm comfortable with the stats, I'll stop the shot and accept it, BUT when I hit accept the first time, nothing happens. It will work the second time, maybe 3 or 4 seconds after the shot is stopped. This little delay has me puzzled, since I've had other strange delays in the past, such as the compass and IMU lagging by 30 seconds or more. I should note that I'm using the MSM 2 RTK engine profile.

Does base reference frame have any significance? Can different settings require more computational power, bandwidth, etc?
 
Matt Johnson

Matt Johnson

Well-Known Member
5PLS
SynGeo said:
Does base reference frame have any significance?
Click to expand...

It really only matters that both the base and rover are set to use the same reference frame otherwise the coordinates will be wrong. I wouldn't expect to to affect anything else.
 
Michael Stazhkov

Michael Stazhkov

Developer
JAVAD GNSS
SynGeo said:
Hi All, I'm running two LS's over LTE and have been experimenting with different settings for the last week. I'm curious about the significance of the base reference frame. For a time, I was using WGS84, because I figured that was the native data state. I switched the NAD83(2011) the other day since that seems to be the standard and started to notice some little differences, but I'm not sure that they are related to the base reference frame as I've been changing other settings as well. The anomaly: When shooting using a boundary profile, I'll let it run for around 60 seconds in beast mode. When I'm comfortable with the stats, I'll stop the shot and accept it, BUT when I hit accept the first time, nothing happens. It will work the second time, maybe 3 or 4 seconds after the shot is stopped. This little delay has me puzzled, since I've had other strange delays in the past, such as the compass and IMU lagging by 30 seconds or more. I should note that I'm using the MSM 2 RTK engine profile.

Does base reference frame have any significance? Can different settings require more computational power, bandwidth, etc?
Click to expand...
Are you using the latest Release version of JField and GeoData? Could you send any your project to support (I need your position and your settings to understand the possible reason)?
Projects screen on LS -> "Send Project to Support" button
 
Michael Stazhkov

Michael Stazhkov

Developer
JAVAD GNSS
Now we know the only reason of the performance degradation - it is using of the HTDP transformation especially in specific locations.
 
You must log in or register to reply here.
Top