Previous Topic

Next Topic

Book Contents

Book Index

Integrity Monitor Properties - General Settings

When you add the Integrity Monitor module, the Integrity Monitor Properties dialog appears with this tab.

If you select the module in the Tree view after you have added the module, the categories and settings of this tab appear in the Properties view.

The General Settings tab refers to the coordinate system, the adjustment, and the alarm generating functionality of the Integrity Monitor module in combination with the Alarm Manager module. Use it also to start position output.

Note - The number and types of properties which are necessary and available for setting up a specific Integrity Monitor module depend on the type and setup of the parent module.

Adjustment category

The Adjustment category pertains to the (eventually combined) Trimble 4D Control Server fully constrained adjustment of processed network baselines and site points. The availability of adjustment properties depends on the parent module.

Fixed points: Only available, if the Integrity Monitor module is located below a Terrestrial Engine. Specifies the number of currently fixed points. To view the selection of fixed points or to change the selection, click the browse button. The Select Points dialog appears, which displays a list of all points sent by the parent for selection. Backsight points are pre-selected, but you may change the selection status. At least two points must have control coordinates and be held fixed.

Fixed stations: Only available, if the Integrity Monitor module is located below a GNSS processing engine (for example, the Integrated Survey Engine). Specifies the number of currently fixed stations. To view the selection of fixed stations or to change the selection, click the browse button. The Select Stations dialog appears, which offers all stations passing the parent Synchronizer module for selection. At least one station must be held fixed. With only one station fixed, the redundancy is equal to zero, and residuals cannot be distributed.

Exclude outliers: If set to Yes, GNSS position outliers are not respected for the adjustment and will not be logged into the database. Any result with a 3-s value beyond the value defined by the disarming threshold (see the Alarming thresholds section below) is considered to be an outlier. When the Integrity Monitor (re-)starts processing with Exclude outliers set to Yes, its Tree view icon shows the alarm status during initialization time. As soon as the position of at least one station has converged to be inside the disarming thresholds, the module status will be fine. Default setting: No. - Not available for a terrestrial engine.

Note - If the parent module stops providing data for all of the fixed points or stations, the adjustment cannot be performed.

Weighting Scalars sub-category - Scaling a priori standard deviations

When performing an adjustment with observations and measurements derived from different types of data sources, one has to deal with the fact, that the variabilities (expressed in the standard deviation) of data types differ. In an approach that does not respect these differences, the adjustment may result in incorrect values. Introducing weighting scalars, however, allows optimizing the adjustment process and leads to a better error estimation.

Using the Integrity Monitor export function and the Trimble office software Trimble Business Center in combination with the Trimble 4D Control Server coordinate system definition, one may estimate weighting scalars. Each weighting scalar value will be applied as factor to the a priori standard deviations of all members of the respective observation or measurement group. When estimated in a Trimble Business Center project, one may copy weighting scalar value(s) and add them to the Integrity Monitor configuration by copying each value into the respective property field of the Integrity Monitor Weighting Scalars (sub-)category.

Values between 0 and 1 will increase the importance of these observations, values higher than 1 will reduce their weight. A weighting scalar of 1 does, of course, not change the a priori standard deviation. Negative values are not allowed.

RTK vectors: Specifies the scalar for the a priori standard deviation of RTK vectors. Only available for the Integrity Monitor below a processing engine processing GNSS data in baseline mode (for example, Integrated Survey Engine, NMEA Engine, and RTK Engine in Baselines mode).

Horizontal angles: Specifies the scalar for the a priori standard deviation of horizontal angles. Only available for the Integrity Monitor below a processing engine processing terrestrial data (for example, Integrated Survey Engine, Terrestrial Engine RT, Terrestrial Engine PP).

Vertical angles: Specifies the scalar for the a priori standard deviation of vertical angles. Only available for the Integrity Monitor below a processing engine processing terrestrial data.

Slope distances: Specifies the scalar for the a priori standard deviation of slope distances. Only available for the Integrity Monitor below a processing engine processing terrestrial data.

Tip - For not applying a weighting factor on the standard deviations of observations of a group, set the respective weighting scalar to 1.

Alarming thresholds not anymore emb because of axis

Alarms can be triggered on the displacements in one or more of the following directions:

Grouped alarming thresholds

If at least one point belongs to a point group, the threshold properties are grouped in sub-categories named according to the specified point groups. For each point group, you can set their own thresholds. If the properties of a point group are collapsed, double-click the sub-category name to expand the properties.

Disarm Thresholds category

The settings of the Disarm Thresholds category let you set reliability thresholds for computed displacements for each coordinate component, and in plane as well as in space.

Note - Disarming alarms is useful for times of GNSS processor initialization. Since Terrestrial Engines obtain reliable results at once, disarming alarms is not necessary. For a Integrity Monitor module below a Terrestrial Engine, therefore, the properties of the Disarm Thresholds category are not available.
With the Integrated Survey Engine, which combines terrestrial and GNSS measurements in one process, the properties of the Disarm Thresholds category are available for editing. However, for points only measured by an optical instrument, the disarming is not applied.

The processor uses the same 3-s limits for warning and alert. Warnings or alerts are triggered if the3-s values are below the limits (and if the alert or warning thresholds are exceeded). You can also configure the Alarm Manager module to keep the operator informed, if any of the 3-s values exceed the thresholds set here.

Note - For receiving alarms neither too often nor too seldom, it is very likely that you need to adjust the threshold values depending on the parent module, the selected period of contributing data, or on other internal and external factors.

Resetting threshold values to their defaults

You can easily restore the default thresholds for each Integrity Monitor module. To do so, right-click the Integrity Monitor module in the Tree View to open its shortcut menu and select the Reset All Threshold Values to the Default Thresholds command.

NMEA Output category - Setting up NMEA output

If NMEA output is enabled, Trimble 4D Control Server outputs NMEA strings containing individual position solutions for each selected station to outgoing connections. Thus, third party software can use the data outside of Trimble 4D Control Server.

Enable NMEA output: If set to Yes, additional properties are available to define the NMEA output. Default: No.

NMEA string type: Specifies the output type, either GGK (containing the time of day) or GGQ (additionally containing the date). Default: GGK.

NMEA interval: Specifies the output interval. Several selections between 20 Hz and 10 minutes are available. If the output interval by a parent Synchronizer module is less than the interval defined here, the NMEA output, of course, cannot send more data. Default: 1 Hz.

Configure outgoing connections: Lets you view the number of stations currently available for data output.

If you set the focus onto the Configure outgoing connections setting and click the browse button, the Configure Connections dialog shows up. This dialog serves a twofold purpose. Use the dialog to:

Select those stations, which will output their positions as NMEA GGK or GGQ strings using the outgoing connection.

Note - NMEA output is available for Integrity Monitor modules under engines processing GNSS data.

Logging Settings category

Use logging filter: If set to No, the processing results are written into the database with the highest available data rate. If set to Yes, the additional Logging data rate property will be available, which lets you specify a data rate at which the processing results are stored in the database.

Logging data rate: Only available, if the Use logging filter property is set to Yes. Lets you select a rate at which the processing results are written into the database. If the input data is coming at a higher rate, the written values will be mean values. If it is coming in at a lower rate, the logging data rate is reduced to the incoming data rate. Available data rates are between 20 Hz and 10 minutes (Default: 15 seconds).

Note - The logging settings only apply for GNSS processing results. They do not reduce results from optical or other measurements.

See Also

Select Points dialog

Alarm Manager

Total station data processing using the Terrestrial Engine PP

Point Information dialog

Point Groups dialog

Adjustment functionality in Integrity Monitor

Coordinates and coordinate systems