RTK Engine Processing Status view

The RTK Engine Processing Status view gives you information on the current status of processing. It displays an overall summary on the number of available baselines or stations, the number of baselines or stations being processed,, and in Baselines mode only, the number of fixed baselines.

Possible reasons for a baseline or station to not being processed include the following:

Change of the Maximum baseline length setting.
Change of the Use redundant baselines setting.
Missing orbit data.
Missing observation data.
In VRS mode: Missing correction data or wrong data format. The module expects RTCM 3.x (including Multi-Signal Messages 4…7).

Use the table of the RTK Engine Processing Status view to find an overview of all baselines the RTK Engine module has created or stations it has processed. Their current fixing status is indicated by their status icons. The view displays the current offsets (D) in numerical form for the following:

In Baselines processing mode, the offsets of the baseline vectors from the given positions of each station.
In VRS processing mode, offsets (D) of the computed positions from the given positions for each station.

Resetting calculations

In Baselines mode

Resetting the calculation of all or selected baselines is available from the shortcut menu. To reset the calculation of one or several baselines, activate the baseline(s) and select the Reset Baseline(s) command. To restart the processing of the whole network, select Reset All Baselines from the module's shortcut menu.

Note - Resetting the calculations affects existing baseline definitions only. To redefine baselines, you can use the parent Synchronizer module and activate or deactivate stations there.

Tip - To reset the calculation of multiple baselines, use the standard keyboard actions for multiple selections.

In VRS mode

Similarly, resetting the calculation of all or selected stations is available from the shortcut menu. To reset the calculation of one or several stations, activate the station(s) and select the Reset Station(s) command. To restart the processing of all stations in one step, select Reset All Stations from the module's shortcut menu.

Available columns in the table:

Column		Description (Baseline mode)	VRS mode (if different)
Status icon	Gray	One or both of the stations defining the baseline does not provide data, although a GNSS Receiver module representing the station(s) is available and selected in the parent Synchronizer module. Status is Paused.	The station does not provide data, although a GNSS Receiver module representing the station is available and selected in the parent Synchronizer module. Status is Paused.
	Green	The baseline has a fixed solution.	The station has a fixed solution.
	Yellow	The baseline has a float solution.	The station has a float solution.
	Red	An error has occurred. See the Status field or the Status Messages view for possible reasons.
Station Code	<Base> - <Station> / <Station>	The baseline vector is defined by the starting (Base) and aiming (Station) reference station. Stations are indicated by their unique Station codes.	Station identified by its unique Station code.
Length	In meters	Calculated from the known positions.	N/A
Status	Status message
Solution	No position	No solution possible.
	No/Old RTK position fixes	Only after reset of calculation. No current solution possible, previous position fixes are kept.
	Float	RTK, Float solution.
	Fixed	RTK, Fixed ambiguities.
Orbit	Combinations of Broadcast, Predicted, or Realtime.	Indicates which orbit types are used for processing.
# Sat	Number of satellites used for processing.
D North, D East, D Height	In meters	Current uni-directional distances to the known positions of the "Station". Updated for each epoch, if no bandwidth restriction applies.
D 3D	In meters	Current three-dimensional distance to the known position of the "Station". Updated for each epoch, if no bandwidth restriction applies.