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 programmed session will start. Should be greater than or equal to the current day of year. |
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 during 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 Memory |
Enabling this option will allow the receiver to delete the oldest record file when the memory used is almost full (less than 15Mbytes still free). This will allow the receiver to constantly log data without external intervention. |
SES,PAR |
Recording and Output Elevation Mask |
Set the recording elevation mask, in degrees (default: 5°). Data from masked satellites will not be recorded. |
SES,PAR |
Data Type |
A read-only field identifying the type of raw data recorded. |
|
G-File Conversion
Parameter |
Designation |
$PASHS |
Rinex 2.11 |
Use this option to convert G-files to Rinex 2.11 format. |
SES,PAR |
Hatanaka |
This option can be used in conjunction with the previous one to convert G-files to Rinex 2.11, 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. |
SES,PAR |
Delete Original G-File |
Use this option to remove original G-files after they have been converted and compressed. |
SES,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 ProFlex 500 embedded FTP server.
Parameter |
Designation |
$PASHS |
Move Converted Files |
Use this option to ask the receiver to move the record 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 location (see below) once they have been created. |
SES,PAR |
Destination Location |
Tell the receiver where to store record files (in its internal memory or to some connected USB device) |
SES,PAR |
Sub-directory name format |
Tell the receiver how to name the subdirectories it will create to store record files. Use the case-sensitive 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) |
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/
Transfer to External FTP Server
Parameter |
Designation |
$PASHS |
Automatic Transfer |
Enable this option if you want the receiver to transfer automatically record files to the specified external FTP server. |
SES,PAR |
Delete Files After 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 subdirectories it will create to store record files on the external 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) |
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/
Back-up FTP Server
Parameter |
Designation |
$PASHS |
Used When Primary FTP Server Not Accessible / Always Used |
Choose whether the back-up FTP server should always be used as a raw data file repository, or only when the external FTP server, defined as the primary FTP, has become inaccessible 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. |
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
• Meteo Comment
• Meteo Sensor Manufacturer
• Meteo Sensor Type
• Temperature Accuracy
• Pressure Accuracy
• Humidity Accuracy