Table of Contents

Session Settings

The Session Settings page is used for various purposes. These are listed below:

   Enable or disable the execution of programmed sessions

   Define the day when programmed sessions will start

   Define the conditions in which data will be collected during programmed sessions (site name, storage media used, masks, ring file memory)

   Manage record files (file conversion, file transfer, file deletion). Files can be transferred to an external FTP server or to the selected receiver memory (internal or USB) for further access through the embedded FTP server.

   Defining optional parameters the receiver will insert into the header of all RINEX files it will generate from G-files.

General Settings

Parameter

Designation

$PASHS

Run Sessions

Use this button to enable or disable the execution of the programmed sessions.

SES,ON

SES,OFF

Reference Day

Enter the day of year (1-366) when the first pro­grammed session will start. Should be greater than or equal to the current day of year for a postponed start, otherwise “1” for immediate start.

SES,PAR

Offset per Day

Use this field if you wish to introduce minutes and seconds of time shift so that every day, the same GPS constellation is visible from the same site dur­ing the same session (typical value: 4 minutes).

SES,PAR

Site Name

Give a name to the site where data are recorded. G-file names will be derived from this name.

SES,PAR

Storage

Choose the storage media where record files will be stored.

SES,PAR

Ring File Mem­ory

Enabling this option will allow the receiver to delete the oldest record file when the memory used is al­most full (less than 15 Mbytes still free).

This will allow the receiver to constantly log data without external intervention. When this function is enabled/disabled for sessions, it is as well for “con­ventional” recording.

RFM

Power Off Re­ceiver Between Sessions

Enabling this option will allow the receiver to switch automatically to sleep mode at the end of each ses­sion and to be woken up just before the next session starts.

With this option disabled, the receiver will stay pow­ered up even between sessions.

SES,PAR

Recording and Output Eleva­tion Mask

Set the recording elevation mask, in degrees (de­fault: 5°). Data from masked satellites will not be re­corded.

SES,PAR

Data Type

A read-only field identifying the type of raw data re­corded.

 

 

G-File Conversion

Parameter

Designation

$PASHS

RINEX 2.11

Use this option to convert G-files to RINEX 2.11 for­mat.

SES,PAR

RINEX 3.01

Use this option to convert G-files to Rinex 3.01 for­mat.

SES,PAR

Hatanaka

This option can be used in conjunction with one of the previous two ones to convert G-files to Rinex 2.11 or 3.01 in Hatanaka format.

SES,PAR

Tar.Z

Use this option to compress G-files in Tar.Z format. Can be used together with option Rinex 2.11 or 3.01.

SES,PAR

Delete Origi­nal G-File

Use this option to remove original G-files after they have been converted and compressed.

SES,PAR

Change Rate

Enable this option if you wish to use a measurement period different from the one used in the G-file

RXC,PAR

Rate

This field will appear if you have enabled the Change Rate option. Enter the new measurement period that will be used when converting the G-file to a RINEX file.

RXC,PAR

Create 2nd RINEX File

Enable this option if you wish to create two RINEX files, instead of one, when converting the G-file.

SES,PAR

Second Rate

This field will appear if you have enabled the Create 2nd RINEX File option. Enter the measurement pe­riod that will be used when converting the G-file to a second RINEX file.

SES,PAR

Disable GLONASS

Enabling this option will result in rejecting all GLONASS measurements from the RINEX conver­sion.

RXC,PAR

Disable SBAS

Enabling this option will result in rejecting all SBAS measurements from the RINEX conversion.

RXC,PAR

Disable GALI­LEO

Enabling this option will result in rejecting all GALIL­EO measurements from the RINEX conversion.

RXC,PAR

 

File Move

Set this pane when you wish to store record files locally so that users can download these files through an IP connection using the embedded FTP server.

 

Parameter

Designation

$PASHS

Move Converted Files

Use this option to ask the receiver to move the re­cord files to the specified location (see below) once they have been converted to the specified format (see table above)

SES,PAR

Move G-Files

Use this option to ask the receiver to move the original record files (G-files) to the specified loca­tion (see below) once they have been created.

SES,PAR

Destination Loca­tion

Tell the receiver where to store record files (in its internal memory or to some connected USB de­vice)

SES,PAR

Sub-directory name format

Tell the receiver how to name the subdirectories it will create to store record files. Use the case-sen­sitive syntax presented in the table below to name these subdirectories (default: Y/D).

SES,PAR

 

Subdirectory naming conventions:

 

Character

Description

s or S

4-character sitename

Y

4-digit year (2010= 2010)

y

2-digit year (10= 2010)

m

2-digit month (01= January)

M

3-character month (Jan= January)

d

2-digit day in month (1-31)

D

3-digit day in year (1-365)

p or P

data_<d> or DATA_<d>, where <d> is the period in seconds

 

Example: Using “Y/M/d/s” would create the following three subdirectories for files recorded in Lisbon on February 21, 2010:

   /2010/Feb/21/LISB/

When two RINEX files are created with different periods, character “p” or “P” should be used so the receiver can store the two types of RINEX files in different directories.

If the subdirectory format is  “s/Y/D/p” then the files logged at 1 second recording interval, on site “CARQ”, on Feb 1, 2012 (day 32) will be pushed to the folder named “…/CARQ/2012/32/data_1” and the files logged at 30 seconds will be moved to the folder “…/CARQ/2012/32/data_30”.

 

Transfer to External FTP Server

Parameter

Designation

$PASHS

Automatic Transfer

Enable this option if you want the receiver to transfer automatically RINEX  files to the spec­ified external FTP server. The transfer is effec­tive only if a G-file conversion has been activated to generate RINEX files from G-files.

SES,PAR

Delete Files Af­ter Transfer

Enable this option if you want the receiver to delete record files from its memory once they have been transferred to the external FTP server.

SES,PAR

FTP Server

External FTP server IP address or hostname (URL)

SES,FTP,PAR

Port

External FTP IP port (default is “21” according to convention)

SES,FTP,PAR

Login

External FTP server login

SES,FTP,PAR

Password

External FTP server password (always hidden; “*” characters appear instead)

SES,FTP,PAR

Path

Enter the path on the external FTP server where the receiver will be allowed to upload its record files as they are created.

SES,FTP,PAR

Sub-directory Name Format

Tell the receiver how to name the subdirecto­ries it will create to store record files on the ex­ternal FTP server. Use the case-sensitive syntax presented in the table below to name these directories.

SES,FTP,PAR

 

Subdirectory naming conventions:

 

Character

Description

s or S

4-character sitename

Y

4-digit year (2010= 2010)

y

2-digit year (10= 2010)

m

2-digit month (01= January)

M

3-character month (Jan= January)

d

2-digit day in month (1-31)

D

3-digit day in year (1-365)

p or P

data_<d> or DATA_<d>, where <d> is the period in seconds

 

Example: Using “Y/M/d/s” would create the following three subdirectories for files recorded in Lisbon on February 21, 2010:

   /2010/Feb/21/LISB/

When two RINEX files are created with different periods, character “p” or “P” should be used so the receiver can store the two types of RINEX files in different directories.

If the subdirectory format is  “s/Y/D/p” then the files logged at 1 second recording interval, on site “CARQ”, on Feb 1, 2012 (day 32) will be pushed to the folder named “…/CARQ/2012/32/data_1” and the files logged at 30 seconds will be moved to the folder “…/CARQ/2012/32/data_30”.

 

Back-up FTP Server

Parameter

Designation

$PASHS

Used When Pri­mary FTP Serv­er Not Accessible / Al­ways Used

Choose whether the back-up FTP server should always be used as a raw data file re­pository, or only when the external FTP server, defined as the primary FTP, has become inac­cessible for some reason.

SES,FTP,PAR

FTP Server

Back-up FTP server IP address or hostname (URL)

SES,FTP,PAR

Port

Back-up FTP IP port (default is “21” according to convention)

SES,FTP,PAR

Login

Back-up FTP server login

SES,FTP,PAR

Password

Back-up FTP server password (always hidden; “*” characters appear instead)

SES,FTP,PAR

Path

Enter the path on the back-up FTP server where the receiver will be allowed to upload its record files as they are created. The same convention as in the primary FTP is used for naming subdirectories in the backup FTP (see “Sub-directory Name Format” field above).

SES,FTP,PAR

 

RINEX File Info

You can define the following additional and optional parameters for insertion into the header of every single RINEX file the receiver will generate:

   Agency

   Observer

   Marker Name

   Marker Number

   Observation Comment

   GPS Navigation Comment

   GLONASS Navigation Comment

   SBAS Navigation Comment

   GALILEO Navigation Comment

   Meteo Comment

   Meteo Sensor Manufacturer

   Meteo Sensor Type

   Temperature Accuracy

   Pressure Accuracy

   Humidity Accuracy