Processing Commands

The following commands relate to data processing and are applicable to all projects.

Command

-procmode [input]

Example

-procmode tc

Description

Specifies the type of processing to be performed.

Input

See Table: List of Processing Modes (for -procmode).

Notes

This command determines how the data will be processed. AR will automatically be selected if you have an NRT subscription and a NovAtel receiver. It also affects which commands are available for use. See Table: List of Commands Supported for Each Processing Mode.

Required?

Yes

Command

-proccfg [input]

Example

-proccfg "C:\My Data\Project.proj"

Description

Specifies the project file to be created.

Input

Full file path and name of the PROJ file to be created.

Notes

This command will be used to determine the name of the project file and all other files generated during processing.

Required?

No. If this command is not used, the project files will be given the same name as the remote data file and saved to the same folder.

Command

-procdata [input]

Example

-procdata L1L2

Description

Specifies the type of data to be processed.

Input

See Table: List of Data Processing Types (for -procdata).

Notes

Dual frequency processing is only available if L1/L2 measurements are available at the base station(s) and remote.

Required?

No. If not specified, the utility will scan the input file(s) to determine which data types are available for processing.

Command

-procdatum [input]

Example

-procdatum nad83

Description

Specifies the datum to be used for processing and output.

Input

The name of the datum.

Notes

If this command is not used, the utility will use the default datum. The default can be set via File | Preferences within GrafNav or Inertial Explorer.

Required?

Only required if using -basefile and -basecoord.

Command

-procdir [input]

Example

-procdir both

Description

Specifies if data should be processed in both or multi-pass modes.

Input

both to process the data in the forward and reverse directions independently.

multi to process in multi-pass mode.

Notes

both is applicable to all processing modes.

multi is applicable to all modes except GNSS-only differential and LC differential.

Required?

No. The default is both.

Command

-procint [input]

Example

-procint 1.00

Description

Specifies the data interval at which the data will be processed.

Input

The data interval in seconds.

Notes

Supported values: 0.05, 0.10, 0.20, 0.50, 1.00, 5.00, 10.00, 15.00, 30.00

For PPP, the processing rate cannot be higher than the remote data rate.

For differential, the base station(s) will be resampled to the specified value, if necessary.

Required?

No. The default is to process at the highest rate possible based on the input data.

Command

-procprofile [input]

Example

-procprofile "SPAN Airborne (AG58)"

Description

Specifies the profile from which to load the processing settings.

Input

The name of the processing profile.

Notes

Processing profiles are loaded first and may have their settings overridden by other commands available here.

Required?

No, but strongly recommended. If not used, the utility will attempt to detect the best profile based on the pre-processing checks performed during decoding.

Command

-procprecise [input1] [input2] … [inputn]

Example

-procprecise "C:\My Data\COD17254.clk" "C:\My Data\COD17254.sp3"

Description

Specifies the precise clock and orbit files to use during processing.

Input

Full file paths and names of the SP3 and CLK files or COR files (for TerraStar NRT users).

Notes

This command is mostly intended for PPP, but is available to all projects.

This command can read multiple input files for projects spanning more than one day.

Required?

No. If performing PPP processing and this command is not used, the utility will download the required precise files.

Command

-procstatic [input]

Example

-procstatic fixed

Description

Specifies the mode of processing to use for static data.

Input

float for float static processing.

fixed for fixed static processing.

Notes

Only applicable for static data. See -remstatic for more information.

Required?

No. Default is to perform float static processing.

Command

-procmsg [on/off]

Example

-procmsg on

Description

Specifies whether or not to write all messages to disk.

Input

on to have all messages written to a file on disk (in addition to the console).

off to have all messages written only to the console.

Notes

The output file name will use this convention: "<project name>_ProcMsg.log"

Processing messages will always be written to the console.

The log file will also capture messages relating to any download attempts for base station and corrections data. These messages do not appear in the console.

Required?

No. By default the messages will only be written to the console.

List of Processing Modes (for -procmode)

Processing Mode

Input

GNSS-only differential

dgps

GNSS-only precise point positioning (PPP)

ppp

GNSS+IMU tightly-coupled (differential)

tc

GNSS+IMU loosely-coupled (differential)

lc

GNSS+IMU tightly-coupled (PPP)

ppptc

GNSS+IMU loosely-coupled (PPP)

ppplc

List of Data Processing Types (for -procdata)

Data Processing Types

Input

Single frequency (L1) processing

L1

Dual frequency (L1 & L2) processing

L1L2

Code-only (C/A) processing

CA

List of Commands Supported for Each Processing Mode

 

-procmode

 

DGPS

PPP

TC

LC

PPPTC

PPPLC

basefile#

X

 

X

X

 

 

basetype#

X

 

X

X

 

 

basecoord#

X

 

X

X

 

 

baseant#

X

 

X

X

 

 

baseht#

X

 

X

X

 

 

downloadbase

X

 

X

X

 

 

remfile

X

X

X

X

X

X

remtype

X

X

X

X

X

X

remant

X

X

X

X

X

X

remht

X

X

X

X

X

X

remstatic

X

X

 

 

 

 

snserver

X

 

X

X

 

 

snusername

X

 

X

X

 

 

snpassword

X

 

X

X

 

 

imufile

 

 

X

X

X

X

imutype

 

 

X

X

X

X

imula

 

 

X

X

X

X

imurot

 

 

X

X

X

X

dmifile

 

 

X

X

X

X

dmistddev

 

 

X

X

X

X

hmrfile

 

 

X

X

X

X

hmrla

 

 

X

X

X

X

proccfg

X

X

X

X

X

X

procdata

X

X1

X

X

X1

X1

procdir

 

X

X

 

X

X2

procdatum

X

X

X

X

X

X

procint

X

X

X

X

X

X

procstatic

X

X

X

X

X

X

procprecise

X

X

X

X

X

X

procprofile

X

X

X

X

X

X

procmsg

X

X

X

X

X

X

expprofile

X

X

X

X

X

X

expfile

X

X

X

X

X

X

expla

X

X

X

X

X

X

expsrc

X

X

X

X

X

X

exputmzone

X

X

X

X

X

X

expkml

X

X

X

X

X

X

exprot

 

 

X

X

X

X

expsbet

 

 

X

X

X

X

expsbetkernel

 

 

X

X

X

X

expsbetsmrmsg

 

 

X

X

X

X

expsbetsmrmsgposscale

 

 

X

X

X

X

expsbetsmrmsgattscale

 

 

X

X

X

X

expsbetimuframe

 

 

X

X

X

X

expsbetcustomframe

 

 

X

X

X

X

expsbetutctime

 

 

X

X

X

X

expriegl

 

 

X

X

X

X

exprieglgeodeticsystem

 

 

X

X

X

X

exprieglprojectname

 

 

X

X

X

X

exprieglcompanyname

 

 

X

X

X

X

expriegltimezone

 

 

X

X

X

X

expriegllocation

 

 

X

X

X

X

exprieglnavigationdevice

 

 

X

X

X

X

exprieglposscale

 

 

X

X

X

X

exprieglattscale

 

 

X

X

X

X

expintervaltype

 

 

X

X

X

X

expintervaltime

 

 

X

X

X

X

expintervaldist

 

 

X

X

X

X

1 PPP processing requires dual frequency carrier phase data.
2 Multi-pass will be performed during the GNSS-only PPP portion, not during IMU processing.