NavCom StarUtil-3000 Rev.G - Manual (Page 98)

StarUtil 3000 User Guide – Rev G
6-96
If the user does not desire the automatic selection of the loaded Geoidal model(s), based
on his geographic position, he can input a specific model. This supersedes the DEFAULT
keyword, which then must be input when automatic selection is desired.
[2DNAVMODE]
This command is used to enable or disable GNSS navigation with height-constrained (2D
navigation) and to set the height constraint when the receiver computes a 2D navigation
solution.

Use 2D navigation mode only when the height can be constrained accurately.
Otherwise, large errors may occur in the position solution.

Upper height limit imposed due to export limitations.
Examples: [2DNAVMODE]AUTO,0.0000
Commands the receiver to automatically transition between 3D (4 satellite
minimum) and 2D (3 satellite minimum) navigation. This can also be determined by
DOP values, even if 5 satellites are available. In 2D navigation, the last valid
computed height measurement is used.
[2DNAVMODE] ALWAYS, 10.5
Commands the receiver to switch to 2D (3 satellite minimum) navigation and set 2D
height to 10.5 meters. The receiver must compute an initial 3D navigation solution
before it transitions to 2D navigation. After 2D navigation is established, the receiver
will not transition back to 3D navigation.

View the PVT tab for the current nav mode and indication of 3D or 2D navigation.
[L1FALLBACK]
This command is typically set to OFF to disable the L1 fallback (or optimized shading) option.
When L1 fallback is ON, dGPS mode precedence is set to Dual 3D  Single 3D  Dual 2D 
Single 2D.
Uploading User Profiles
Avoiding User Profile Loading Errors
StarUtil 3000 v.1.0.0 and later scans user profiles before loading them to adjust port settings
and reduce the likelihood of communication errors. Communication errors still occur, and this
section aids in resolving common issues.
As a user profile is loaded into the receiver, each command line is acted upon as it is received.
A profile loading error occurs if the communication link between the PC and the receiver is
broken before all command lines are received. To avoid this loading error, the best practice is to
preview the control port baud rate in a user profile before loading the profile.
For example, a PC is currently connected to the SF-3050 COM Port 1 at 57600 bps. So, Port 1
is the current control port. In the example in Figure
92 , previewing the profile to be loaded
reveals that the receiver Port 1 baud rate (highlighted) will be changed to 115.2 kbps. If no
adjustments are made prior to loading this profile, all of the commands following the Port 1