Home

User`s Manual V 3.2.0

1. cccceeeeeeeeeeeees 6 system integration tools ee 5 T Db EE 100 terminate GBSS era 6 EE A RR TR 85 atrape e a n a 33 o EE 6 is A a aes 31 TAL MOIS sessao dai EE 6 translated run time en J2 trap communication data 21 Tape o a ene CARD ere 29 ee e cad 18 U underscore character c ooccccocccnoncccnnoccnnns 19 uninstall EE 5 UNI pra O a T EE EE 46 unrecognized messages 66 UPLOAD BAT a 55 uploading a script file 12 user corrected GPS time 41 user entered GPS Time ou e cence 4 SERIO Set Gare Rn cee eo AE T 85 BU LG E A IRD E A 42 ULA PrOSTAMS ad 6 W WAN ia ade 5 40 EE 18 WGS 84 position cocccccncncnnnnnnooonncccnncncnononons 20 WS FIR Pr unta lis 85 X XYZ SOLCES MO medi 87 AYZASMRX BMP incide 90 XYZASHR XEXE iS 51 XAYVLASORA EX E ainia 52 90 XAZASOR IND add 90 Y Weal Ol SESSION aiii 102 Z TNS a 70 TN ee 15
2. Eiremoteiremote exe C 4 D 0 02 HE decomp bat pat klen Eiremoteidecomp bat 3 ves Enremote delete bat ES ves Mouer bat Evremote das2 77 FPDD 4 OK Edit Copy Hew Delete import Export Cancel Figure 3 21 Post Session Commands Window 42 This window provides the set of commands that will be launched upon completion of a session The end of a session occurs when the File Duration is reached see Section 3 1 4 10 Furthermore this window shows the order in which the commands will be launched Notice that each command has the components described in Table 3 2 Table 3 2 Command Components Cmd The command number The order of the commands specifies the order in which each post session command will be launched Enabled Indicates whether or not the command is enabled for execution at the end of the session Indicates whether or not the command processor of GBSS when it is executing the post session commands is to wait for the current command to complete before launching the next command Indicates whether or not there are any detected warnings in the post session command The text of the post session command The following describes the functionality of each button of this window OK al changes made to the post session commands including any imported commands Edit Begins the editing of a highlighted post session command Simply use the mouse cursor to sele
3. When you desire an alternative configuration for example to support two GBSS installations simultaneously you should copy the following files to another directory XY ZAshRx INI XY ZAshRx EXE XY ZAshRx BMP By doing this you create an independent copy of the INI file Launching the program XYZAshRx EXE in this copied directory causes the program to use the INI file in that directory This copy would utilize a configuration that is independent of the other copy that is the master copy of XYZAshRx on your computer In contrast launching two copies of the XYZAshRx from the same directory access the same INI file The configuration stored at the end of the runs of the programs is highly dependent upon which copy of the program terminated first Needless to say you are strongly advised not to launch more than one copy of XY ZAshRx from the same directory unless both copies will use the exact same configuration information Launching several copies of XYZAshRx each originating from its own directory is perfectly acceptable and encouraged 90 E 3 1 Manual GUI Approach Upon starting XYZAshRx without command line parameters the screen shown in Figure E 1 is displayed EA AO AAA TA Un Re EE es AAA A Figure E 1 Ashtech Raw to RINEX Window 1 Presented above are the Main Window of the program and the File Selection Window The File Selection Window is presented automatically at the start of the program as a means of saving time and w
4. 3 1 1 Communications Communication Settings The Communications Configuration window Figure 3 2 allows you to set the following communication parameters 1 The PC communication port labeled Port 2 The PC communication speed labeled Speed and 12 3 Expected RS 232 status lines Communication Configuration Port com bul Speed 57600 S MW Use CTS RTS Hardware Handshaking W Use DTROSR Hardware Handshaking Figure 3 2 Commumnication Configuration Window 3 1 1 1 Configuration Comms Port The port selection allows the operator to specify the communications port of the computer used to communicate with the Ashtech receiver The permissible values are COM1 COM2 COMB through COM16 3 1 1 2 Configuration Comms Speed The speed selection allows the specification of the communications speed of the communications port of the computer used to communicate with the Ashtech receiver The permissible values are 300 600 1200 2400 4800 9600 19200 38400 57600 and 115200 When GBSS is in Active Mode see Section 3 1 2 1 it will command the receiver to the baud rate you select here 3 1 1 3 Configuration Comms Use CTS RTS Hardware Handshaking The CTS RTS Hardware Handshaking checkbox allows you to specify whether or not the normal CTS RTS hardware flow con trol handshaking is enabled In most configurations this checkbox should be checked Those who uncheck this checkbox should have
5. Table F 1 Additional Header Line CENTER OF MASS XYZ Current center of mass of vehicle in body fixed coordinate system 3F 14 4 meters same system as used for attitide 124 In order to distinguish between L1 CA and L1 P1 we define LA and SA as new observation types Table F 2 Table F 2 Types of Observation 1H TYPES OF Number of different observation types stored in the file 16 9 4X A2 9 4X A2 OBSERVI Observation types 6X HAMAS If more than 9 observation types Use continuation line s The following observation types are defined in RINEX Version 2 20 Ed L2 Phase measurements on L1 and L2 L1 being derived from P Y code LA Phase measurements on L1 derived from C A code tracking Use L1 if origin is not known Cl Pseudorange using C A Code on Ll Pseudorange using P Code on L1 L2 Doppler frequency on L1 and L2 Transit Integrated Doppler on 150 T1 and 400 MHz T2 Raw signal strengths or SNR values as given by the receiver for the L1 L2 phase observations Raw signal strength or SNR for LA Receiver channel number A future C A code derived phase observation on the second frequency could be called LB with the associated signal strength or SNR value called SB As there are new header records and a new observation type defined we will have to increase the RINEX version number from 2 10 to 2 20 Signal strength data can be stored into the RINEX file using the S1 or SA and S2 observati
6. File Duration 1 2 3 4 5 6 GBSS will call CGREMOTE EXE an Ashtech program for remote receiver control to dial a remote GPS receiver and download its data GBSS will call a batch file created by CGREMOTE EXE to decompress the data downloaded from step 1 into Ashtech formatted GPS data files GBSS will delete via a batch file the receiver image file downloaded in step 1 GBSS will move via a batch file the data files created from step 2 to the same directory in which GBSS is storing data from a local receiver GBSS will call XYZASHRX EXE to convert the data files from step 4 to their associated RINEX counterparts GBSS will copy the created RINEX files of step 5 and those created by GBSS through its connection to a local GPS receiver to the target network directory Throughout this example we make the following assumptions 1 2 3 4 5 6 7 The reader is familiar with the utility programs and their command line parameters called through these post session commands for example CGREMOTE EXE and XYZASHRX EXE The reader is familiar with MS DOS batch command files The directory in which REMOTE EXE is stored is EAREMOTE The directory in which XYZASHRX EXE is stored is C Program Files Ashtech GBSS UTILS All of the GBSS output files of interest that is the files to be transferred to the shared network drive are stored in the GBSS Primary Output Data Directory The target n
7. In this case you will need to change the xxx xx part of the command to contain a valid epoch interval before sending the com mand Entered commands are sent using the Send Command Button To determine valid commands you must consult the appropriate receiver manual You do not need to supply the lt CR gt lt LF gt that is carriage return line feed sequences required at the end of the messages GBSS will add those for you The upper middle portion of the window displays the commands that you have sent to the receiver This area will also show the commands sent to the receiver and they will be shown as they are sent when the file upload capability has been enabled see Section 3 1 2 6 The lower middle portion of the window displays the data being received from the Ashtech receiver Notice that in the above example that most of the data is not in a normal human readable form This 1s because in this example the display is showing epoch data received from the receiver This epoch data like that of some other message data is communicated in a binary form GBSS will show only the ASCII portions of those messages when the Show ASCII only checkbox is checked When this checkbox is unchecked the non ASCII data is shown in a hexadecimal representation of the data that is Ox followed by the hexadecimal number of the character being represented It is important to note that GBSS will continue to log all epoch data normall
8. ddd is the day of the year For example a file named C97233 NMA is a NMEA message capture file for session C of day 233 of 1997 Like the data file names the NMEA capture file names depend upon the File Duration parameter see Section 3 1 4 10 and the current corrected CPU GPS time see section 3 1 7 82 UPLOAD FILE FORMAT Sections 3 1 2 6 and 4 5 of this document describe how a file can be uploaded to an Ashtech receiver This section describes the required format of those files The general format of the Upload File is ASCII text However some messages sent to an Ashtech receiver may contain binary data Almost every message sent to an Ashtech receiver requires the lt CR gt lt LF gt carriage return line feed sequence at the end of the message For these reasons we need a means of entering binary data into the upload file Additionally there are cases where a pause in uploading data 1s required before sending the remaining data To accommodate all of these needs the upload is sent through an interpreter imbedded in GBSS This interpreter sends all ASCII text until it meets with a special escape charac ter After these escape characters will be other characters that describe the information to be sent or the processing to take place Once the escape processing is handled GBSS will resume sending the ASCII data in the file The special escape character is If this character is followed by a character then the
9. Example 5 XYZAshRx I BN102A97 323 EN102A97 323 SN102A97 323 T DARINEX OUT The converter uses the files BN102A97 323 EN102A97 323 and SN102A97 323 from the current working directory as the input B E and S Files respectively Because no O or N parameters were specified XYZAshRx will automatically name the RINEX observation and navigation output files but will place these files in the directory D RINEX OUT Example 6 XY ZAshRx I BN102A97 323 EN102A97 323 O OBS DAT N NAV DAT T EARINEX OUT The converter uses the files BN102A97 323 and EN102A97 323 from the current working directory as the input B and E Files respectively Because no S FILE was specified the converter will use the site related data stored in the program s configuration file for site related data Because the O parameter was specified the converter will output the Observation data to the file OBS DAT The N parameter specifies that the Navigation RINEX data will be output to the file NAV DAT The output files will be placed in the directory E RINEX OUT The S option allows you to specify whether the converter will output smoothed codephase measurements Permissible values for this parameter are 0 and 1 the value 1 directs the program to output the smoothed codephase contained in the Ashtech B File When the S option is not specified XYZAshRx will apply the smoothing as if S 1 were specified on the command line The C option is used to spec
10. Geodetic Base Station Software User s Manual V 3 2 0 Copyright Notice Copyright O 1998 2002 Magellan Corporation All rights reserved No part of this publication or the computer programs described in it may be reproduced translated stored in a retrieval system or transmitted in any form or by any means electronic mechanical photocopying recording or otherwise without prior written permission of Magellan Your rights with regard to this publication and the computer programs are subject to the restrictions and limitations imposed by the copyright laws of the United States of America U S A and or the jurisdiction in which you are located For information on translations and distribution outside the U S A please contact Magellan Printed in the United States of America Part Number 630248 Revision B January 2002 Trademark Notice GBSS is a trademark of Magellan Corporation All other product and brand names are trademarks or registered trademarks of their respective holders SOFTWARE LICENSE AGREEMENT IMPORTANT BY OPENING THE SEALED DISK PACKAGE CONTAINING THE SOFTWARE MEDIA YOU ARE AGREEING TO BE BOUND BY THE TERMS AND CONDITIONS OF THE LICENSE AGREEMENT AGREEMENT THIS AGREEMENT CONSTITUTES THE COMPLETE AGREEMENT BETWEEN YOU LICENSEE AND MAGEL LAN CORPORATION LICENSOR CAREFULLY READ THE AGREEMENT AND IF YOU DO NOT AGREE WITH THE TERMS RETURN THIS UNOPENED DISK PACKAGE AND THE ACCOMP
11. menu item XYZAshRx will display a window containing information about the program In response to selecting the Command Line Parameters item XYZAshRx will display a window describing how to invoke the Command Line Mode of the program The command line mode is further documented in Section E 3 2 of this manual E 3 1 1 File Selection Window The File Selection Window is displayed in response to the Convert To RINEX selection from the program s main menu Fig ure E 5 provides an example of the File Selection Window RINE Conversion File Selection Window Source Files E HA Browse Sl Ea sss Browse I Browse RIHES Output Options O Ka sampleta3390521 980 Browse H Ko sampletai3208 21 98H Browse G ai sample aaaatz 30 02 Browse OOK X Cancel xYZ s of GPS Figure E 5 RINEX Conversion File Selection Window Table E 1 describes the fields in this window Table E 1 Edit Fields There are seven edit fields in this window The first four correspond to the following input file names a AIN Input Ashtech formatted I File ionospheric data IICA ETC Ir Output RINEX GLONASS Navigation File XYZAshRx seeks to help with the file naming by keying off of the source B File Each time the edit field of source B File 1s changed and contains a valid B File name that 1s the file exists on disk XYZAshRx will automatically fill in the other input 93 file names for
12. sions of the data files will be stored This directory indicates where files will be stored when the file s Secondary checkbox of the File Compression Selections is checked see Section 3 1 4 8 Please note that the secondary compression directory should not be confused with the secondary output directory GBSS allows you to specify separate directory paths for the secondary out put directory and for the secondary compression directory For example you might specify the following Secondary output directory of C SEC_DIR Secondary compression directory of D SEC_COMP The secondary output directory and the secondary compression directory are related only in that the creation of a file needs to be enabled in the secondary or primary output directory before it can be compressed in the secondary or primary compression directory To change the secondary compression directory you can manually edit the output path or use the browse feature To use the browse feature click on the BROWSE button to the right of the text Secondary File Compression Path Upon selecting this button you will be provided with a window that is capable of navigating over the entire set of directories of your computer Use that window to select the desired secondary compression directory If the desired directory does not exist simply use the New Folder button in the upper right corner of the directory selection window to create it Please note that
13. Before beginning the playback or simulation GBSS attempts to determine the start time of the Trap File data for proper output file naming and ogging session purposes Trap Files generated by GBSS version 3 0 00 and higher contain a special time stamp header earlier versions do not If GBSS cannot locate this header in the Trap File you will be prompted to enter a start time of the Trap File data An example of this window is shown in Figure 4 15 Enter Start Time of The Simulation File The file you selected for simulation playback does not contain a start time header record You will need to supply the start time of the file H you do not know the start time of the file simply enter an approximate value Playback the file and observe the time of the first few records Then playback the file again and enter the correct start time of the file Simulation Playback File Hame Enmtemp1isave org Trovurm97 360 Start Time of Data Session Start Time Year Month Day Hr Min fi 997 E 26 jo jo jo GPS Week Seconds of Week 937 432000 Figure 4 15 Simulation Start Time Window When this window is displayed GBSS will gain as much information as possible about the start time of the Trap File based upon the name of the file However that information 1s usually limited to the nearest day You should enter the correct start time of the Trap File If you do not know the exact start time run the program in Simulation Mode th
14. CARD AND B THAT YOUR SOUND CARD IS CAPABLE OF PLAYING WAV FILES If your computer does not have a sound card it is suggested that you not attempt to play any sounds that is that you leave the Play sound file on Warning and Play sound file on Alert checkboxes unchecked To play a sound file on the Warning condition ensure that the Play sound file on Warning checkbox is checked and you use the associated Select File to select the desired WAV file Upon making your file selection GBSS will test play that selected sound file To play a sound file on the Alert condition ensure that the Play sound file on Alert checkbox is checked and you use the asso ciated Select File to select the desired WAV file Upon making your file selection GBSS will test play that selected sound file When either a warning condition or an alert condition exists GBSS will attempt to play the selected sound files repeatedly with about a 1 5 second timing While GBSS will play sound files over 1 5 seconds you are advised to keep your warning and alert sound files to less than 1 5 seconds 3 1 7 GPS Time Many sections of this document refer to a corrected CPU GPS time This section describes how GBSS can be configured to determine this time It can be a difficult subject to explain but it all boils down to the following simple facts 1 GBSS needs GPS time to properly name files 2 Your CPU has a clock that is not normally syn
15. Figure 3 12 File Output Contiouration Window 6 unica a 25 Figure 3 13 File Output Configuration Window 7 ccccccoooooocnnnnnnonnnononononnnnnnonnnnnnnonnnnnnnnnnnnan non nnnnnnnnnnnnnn non cnn 21 Figure 3 14 Compression Program Configuration Window cccccnnnnoooconnnnnnnnonononononnnncnnnnnnnnnnnnnnncnnnnnonnnonnnnnos 31 Figure 3 15 Session Programming Window cccccccccnnnnnnnnnnonononnonnnonononnnnnnnnnnnnnnnnnnnnnnnnnnn no nnnnnnnnnnnnnnnnnnnnnnnnnns 34 Figure 316 Edit Sesston Wind Wel ria eses 37 Fase 3 17 Edit Session WINOWEZ cti aa A 38 Figure 3 ES Edit SESSION EEN ee EE 38 Figure 3 19 Other Configurations Options Window ccccccccccccsssssssseeeeeeeeesssessneceeeeeeseeeessneeeeeeeeeesessaaaaes 39 Figure 3 20 GPS Time Configuration Window ns A ai 41 Figure 3 21 Post Session Commands Window occccccnnnooooonnnnnnnnnnnononnnnnnnnnnnnnnnon ono rnnnnnnnnnnnn non nnnnnnnnnnnnnnnnnnnnos 42 Figure 3 22 Post Session Command Line Edit Window ccccccnnnnnonononononononononononnnnnnnnnnnnann non nnnnnnnnnnnnnnnnnos 44 Figure 3 23 Post Session Command Line Editor iii iia 45 Fi ute 3 24 External Module liter dee sin aad a Gu 56 Figure 3 25 Interface with Multiple External Programs 56 Figure 3 26 Third General Form for External Interface circinera a a a a a 57 Figure 3 27 Real Time Interface Configuration Window cccccccnnoooononcnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnonnnnnnnnnnnannnnnnos 58 Figure 3 28 External Modules Configuration Wi
16. W4GS 84 Site AAAA Clock Offset 2170944531 Ai 1087558 471 Clock Drift 320 9159 Y 1880791 195 Hum Sats G E S945865 306 POOP df Base Station Reference Position WIGS 84 Xx 1087526 517 Y 10844215 f 3945978 946 Figure 4 6 ECEF Position Window Like that of the Geodetic Position window this window is divided into two parts 1 the epoch point position and 2 the base sta tion reference position The upper portion that is that which is labeled Epoch Point Position contains information obtained from the most recent point position solution provided by the receiver in the SPASHR PBN message The lower portion of the window contains the site position information that was passed to the receiver see Section 3 1 3 The receiver ultimately requires that the X Y and Z components be converted to latitude longitude and height As such when a latitude longitude or height component of the site position has a zero value this lower portion of the window will display Partial implying that only a partial position was entered for that all components When all components have a zero value then all will be displayed as none that is no fixed position entered As with all other windows in the program GBSS will show the units of a displayed field if you rest the cursor over that field for a couple of seconds 4 3 3 Channel Summary Window Figure 4 7 is an example display of the Channel Summary window from
17. deactivated through the GBSS point and click interface Data files can be automatically stored in any one of four user selectable directory structures GBSS supports creation of the following different file types e Dual frequency Ashtech format GPS e Single frequency Ashtech format GPS e Dual frequency RINEX format GPS e Single frequency RINEX format GPS e Dual Frequency Ashtech format GPS GLONASS e Single frequency Ashtech format GPS GLONASS e Jonospheric model file e Trap File described later e NMEA file e Diagnostic log file e Compressed files Please note that all of the files supported by a particular receiver can be created simultaneously by GBSS For instance the GBSS software allows you to simultaneously log dual frequency and single frequency Ashtech GPS data and dual frequency and sin gle frequency RINEX files while connected to only one dual frequency receiver GBSS accomplishes this by automatically split ting the dual frequency data stream into dual frequency and single frequency components and then storing each component in separate files which could then be stored in different directories All of the above files can be automatically compressed by GBSS This feature facilitates archiving of data and automated FTP transfers where file size 1s important In addition GBSS can be configured to automatically create different epoch intervals for the same time period For example a 1 hour dual frequency R
18. see Section 3 1 8 4 1 With this feature for example one could effectively create data files of 30 15 10 5 3 and 1 sec ond epochs each placed in their own directory structures Please note that the Trap File bytes are written before GBSS has a chance to interpret them However the trap feature has been designed to ensure that the epoch data of a Trap File coincides with the epoch in the associated B E and S Files Trap Files can be concatenated through a simple MS DOS command For example suppose that it 1s desired to playback three Trap Files from a receiver on a given day Further suppose that those three Trap Files were named TXYZ A97 035 TXYZ B97 035 and TXYZ C97 035 Issuing the following DOS command can create a single Trap File COPY TXYZ_A97 035 B TXYZ_B97 035 B TXYZ_C97 035 B TRAPDATA The file TRAPDATA will contain the concatenation of the three files This TRAPDATA file can now be played back through GBSS to create the desired GPS data files 3 1 4 6 Configuration Output Files Primary Compression Directory The Primary File Compression Path edit field 1s used to specify the top level primary directory where compressed versions of data files will be stored This directory indicates where files will be stored when the file s Primary checkbox of the File Com pression Selections is checked see Section 3 1 4 8 Please note that the primary compression directory should not be confused with the
19. target directory n Return Code Error Code Message string Line string Rationale The above message is displayed because ASHFTPMD cannot perform the change directory com mand Notice that the target directory of the command is displayed 4 Message ASHFTPMD Create Directory Failure Failure status information Target Dir target directory n Return Code Error Code Message string Line string Rationale The above message 1s displayed because ASHFTPMD cannot get FTP to create a new directory Notice that the target directory of the command is displayed 86 D UTILITY PROGRAM GNSS2GPS D 1 Introduction to GNSS2GPS Program GNSS2GPS EXE was developed by The XYZ s of GPS Inc in direct support of the Ashtech Geodetic Base Station Software GBSS GNSS2GPS was developed as a 32 bit Windows program that creates GPS only Ashtech data files from Ashtech GPS GLO NASS observation and navigation Files This program specifically supports the Ashtech Geodetic Base Station Software GBSS The program is invoked via command line parameters D 2 System Requirements GNSS2GPS imposes the following requirements but does not necessarily report any errors if the requirements are not met 7 Windows 95 or Windows NT on and Intel 486 compatible or higher 8 Atleast 1 Mbytes memory 9 Atleast 1 Mbyte disk space in order to store the program 10 A GBSS Software Sentinel Key Notice that a software sentinel
20. 1 page page 15 When the receiver is in Passive Mode it is VERY IMPORTANT that GBSS know the exact receiver type to which it is connected Because the software cannot determine the receiver type with out sending commands to the receiver and because the software needs to know the receiver type to know how to interpret data from the receiver the Receiver Type edit field must be set correctly for passive base station operations Failure to provide the correct receiver type may result in incorrect outputs The Receiver Channel Software Version Labeled Channel edit field will take any 4 character sequence This field allows the specification of the Ashtech receiver s channel software version and is stored within the output B File The Receiver Navigation Software Version Labeled Navigation edit field will take any 4 character sequence This field allows the specification of the Ashtech receiver s navigation software version and is stored within the output B File While the channel and navigation version information is not needed for the operation of the base station software it is useful in troubleshooting receiver problems That is if data from this program is ever provided to Thales Navigation to analyze a problem providing incorrect receiver software ver sion information could mislead the engineers and delay the isolation of the problem When the base station software is in Active Mode that 1s GBSS can send commands to the re
21. 1 4 10 In this use we recog nize that files are closed at the specified duration and the session codes used to name the files see Appendix A are based upon the Corrected CPU GPS Time see Section 3 1 7 The other use that is logging sessions described in this section is used to describe the periods during which data are actually recorded into files independent of the file naming and closure mecha nisms Upon selecting the Configuration option from the main menu and then selecting the Logging Session sub menu option you will be presented with a window similar to Figure 3 15 Session Programming Window ES Warning Please See User s Guide For Detailed Instructions Session Controls Sessions Enabled Type Session Start Session End Duration Daily 11 00 00 12 00 00 01 00 00 Yes Daily 13 00 00 14 00 00 01 00 00 3 Yes Weekly Wed 17 00 00 Wed 22 00 00 0 05 00 00 Yes Special 1999 03 17 17 05 00 11999 03 27 18 05 00 40 01 00 00 Figure 3 15 Session Programming Window Through this window you can create edit delete copy import and export logging sessions These logging sessions describe the periods during which GBSS will actually record data When the Activate Session Programming checkbox 1s unchecked and or there are no programmed logging sessions then the Logging Sessions feature also referred to as the Session Programming fea ture of G
22. 100 NAME TOMMAL os 25 naming output files ococcccccncnnnnnos 6 navigation data occccccccnnnnnnnnnnnnnnnnnnnnnnnnnoss 16 navigation software Version oocccccccccccos 18 new data formats occcccccnccccnccncnnnnnnnnnnnnnss 2 NMEA ad tes iui a 1 2 20 NMEA capture Die 81 101 NMEA TOS TINGS assenta aaa 31 NMEA XDR an 31 normal termination occcccccnnnnnnnnnnnnnnnnnes 11 a or 63 O OGD UE 100 octal representation occccccnnnnnnnnnnnnnnnnnnnnnoos 83 output data files cccccnnnnnnnnnnmmmmmmm 24 QUEUE TITIES dat 33 P passive base station operations 18 DASSIV MOUE geseet regen 17 PASS W EE 85 Peripheral devices deca 8 permanent reference station sites 6 pipe identification ooooooononononanccnncconcccnnnons 58 PIDE NANDO A 58 ER MARE TIG ista 31 PR ZIP D O retas O O 31 plug and play ani 8 post session commands 43 54 power failures eirio rn an 6 primary output directory ccccccoccccco 26 R AAA a 9 o Ze 17 radio Modem sis 13 RAM ege 15 raw CPU TME deis 41 raw data output oeieo aAA 29 raw data stream da 33 E EE EE 33 read only atributos cds 8 real time data occonnccnnnccccnicccn 6 18 33 55 realtime data EE 57 Tea late Mtra unio 7 receiver Image file sanien pienie 51 SEET 12 receiver reference position 17 receiver simulation 12 receiver UMELAS etarra 41 FECCI
23. 23 0 one day file day of the year 4 character ID for the LEO receiver antenna For the 15 minutes high rate ground station tracking data we recommend the following extended filenames ssssdddhmm yyo two digit year starting minutes within the hour 00 15 30 45 character for the starting hour in the day a 00 b 01 x 23 day of the year 4 character ID for the LEO receiver antenna Consequences for Ground Based Data Files Basically no changes are mandatory for ground based GPS GLONASS observation data files However the MARKER TYPE header record could be a valuable addition to the current version 2 10 to better characterize the marker vehicle on which the receiver has been mounted Depending on the feedback especially from receiver manufacturers the LA and CH observation types could either be recom mended to be used by ground based receivers too or to be restricted to space borne receivers only RINEX reader programs should be prepared to at least skip uninterpreted header records modify LA into L1 or skip LA and apply the OBS SCALE factor if present Implementation Plan The proposed modifications have been accepted by the International GPS Service LEO Working Group in February March 2001 to be used within the IGS LEO Pilot Project for space borne GPS data We are now requesting comments from the wider GPS GLONASS community to what extent the proposed modifications espe cially the MARKER TYPE OBS SCALE FA
24. 3 1 2 3 Leap Seconds UTC to GPS Conversion Two key facts must be considered when converting the NMEA capture file created by GBSS 1 the NMEA GXP message con tains only time of day time tags and 2 the message contains UTC time tags In this Section we address item 2 item 1 is addressed in Section E 3 1 2 2 The RINEX standard requires that the time tags of the meteorological data be in GPS time The NMEA GXP message that is the message used to time tag the meteorological data contains UTC time stamps As such we must convert the times to GPS The Leap Seconds data entry field of the window allows you to specify the delta between GPS and UTC As of January 8 1999 there are 13 leap seconds between UTC and GPS That is UTC 13 GPS time The value of the Leap Seconds field will be saved between runs of the program Furthermore it will be used during the com mand line conversion of meteorological data see Section A 3 E 3 1 2 4 Specifying the Output RINEX Meteorological Data File The output file name is specified in one of 4 ways 1 The input meteorological data file name complies with the Ashtech naming convention 2 You cursor through or edit any of the Start Day of Data edit fields 3 You manually enter the output file name and 4 You use the Browse button next to the edit field pertaining to the output file name When approaches 1 or 2 are used the output file name will comply with the RINEX file naming
25. 999 At this point the increment causes a rollover where s is set to B and ddd is reset to 000 This roll over process continues until s reaches Z and ddd reaches 999 At this point each time ddd reaches 999 it is simply reset to 000 Under the extended naming form and with the File Duration less than 1 hour the session code s becomes a three character field It has the form hmm where A is the hour code that is A to X and mm represents the start minute of the hour Because the File Duration parameter has a lower limit of 0 05 that 1s 3 minutes independent file names will be generated See Appendix F for a complete description of the extended RINEX naming convention Please note that there are both advantages and disadvantages of each mode For example many processing programs expect an 8 3 file name format and do not support the 10 3 format created in the extended naming modes However 1t 1s difficult using a directory listing only to determine the approximate start times of classic file names generated when the File Duration is less than 1 0 In summary most users will not need to worry about the file naming approach that is those users that set the File Duration parameter to 1 0 or greater Those users that need smaller File Durations must weight the naming options For details on file naming conventions please see Appendix A 3 1 4
26. GBSS calls the batch command file RXASHSES BAT to rename the RINEX files such that their session codes to exactly match that of the B E and S Files We call the same batch file as was called under step 1 but are performing the operation for the files stored in the GBSS Secondary Data Directory Step 3 GBSS calls the utility program ASHFTPMD EXE to create a directory on the remote FTP server This particular utility program will only attempt to create the directory if 1t does not already exist on that server Steps 4 to 6 GBSS calls FTP95PRO EXE to push the B E and S files created by GBSS For example in step 4 we use the mne monic BFP which contains the full name and path of the B File created by GBSS We also use the mnemonic BF which contains only the name of the B File and not any drive or path information Step 7 GBSS calls the batch file name UPLOAD BAT to push the renamed RINEX files to the remote FTP server The con tents of the batch file are as follows REM 1 BFILE SESSION CODE REM 2 SOURCE DAY OF YEAR 3 DIGIT REM 3 SOURCE 2 DIGIT YEAR REM 4 SOURCE PATH REM 5 DESTINATION PATH o d condorsST 5 C FTP FTP95PRO exe i ashtech ini p condorST s local 4NCNDR 2 1 2 1 n d condorST 5 C FTP FTP95PRO exe i ashtech ini p condorST s local 4CNDR LA w In this case we did not need to use a batch file to perform the operations but did so for the instructive purposes of the example W
27. GPS receiver to send the NMEA messages to GBSS 3 1 4 10 Configuration Output Files File Duration The Other File Output Options area at the bottom of the File Output Configuration window contains five user configurable parameters controlling various aspects of file creation These fields are as follows e File Duration hours e File Re Open Rate seconds e Epoch Filtering seconds e File Deletion Age days e Use Ashtech Subdirectory Structure On OFF Please note that the Other File Output Options fields will appear at the bottom of the Compression Files tab the NMEA Cap ture File tab as well as the Data Files tab Changes to any of the fields in these five fields affect all three tabbed areas equally That is these Other File Output Options are global file creation parameters The File Duration parameter specifies the duration in hours of the files logged A value of 1 disables the File Duration option A disabled File Duration implies that the files are closed only after GBSS 1s disconnected from the receiver When the File Dura tion is enabled that is not 1 and the File Duration is reached GBSS automatically closes all files currently being recorded and then automatically opens new files such as the B E S RINEX Trap Files etc Each time the output files reach their dura tion based upon the GPS time embedded in the data received from the receiver they are closed and the files for the next
28. NMEA messages in the Write selected NMEA messages to capture file area of the menu It is important to stress that enabling the capture of any NMEA messages to a file does not cause GBSS to request these mes sages from the GPS receiver That is it is up to the operator to command the receiver either through GBSS Terminal Window commands File Upload commands or through the front panel of the GPS receiver to send the NMEA messages to GBSS 3 1 4 9 3 Write Selected NMEA Messages to Capture File This Write selected NMEA messages to log file field allows you to enable or disable the capture of 21 individual NMEA mes sages These messages are GLL APA DAL GRS SAT GXP ALM GSA UTM GGA MSV GSV VTS VTG XTE TTT XDR GSN BWC RRE and POS The capture of an individual NMEA message will be enabled if the box to the immediate left of it has been checked If the box to the left of it has not been checked then the message will not be captured by GBSS The Write all received NMEA messages to capture file field immediately above this field allows you to select all 21 NMEA mes sages with the click of a mouse button It is important to stress that enabling the capture of any NMEA messages to a file does not cause GBSS to request these mes sages from the GPS receiver That is it is up to you to command the receiver either through GBSS Terminal Window com mands File Upload commands or through the front panel of the
29. Renaming the RINEX files created by GBSS such that their session codes precisely match those of the session codes for the Ashtech B E and S Files and 53 2 Upload all of the data files created by GBSS including the renamed RINEX files to an FTP server Throughout this example we make the following assumptions l J The reader is familiar with the utility programs and their command line parameters called through these post session commands for example FTP95PRO EXE The reader is familiar with MS DOS batch command files The directory in which the batch file is stored is CABATCHES The target directory structure on the remote FTP server will be cors data mmmY Y Daydd where mmm is the 3 character month of the data YY is the 2 digit year of the data and dd is the 2 digit day of the month Permission to create directories and store files on the remote FTP server has been granted for the accounts we are using The following lists the post session commands for this example each of which are created on a wait for complete basis With each we list the GBSS post session command and its associated working directory C1 C2 C3 C4 C5 C6 C7 CA BATCHES VRxASISes Bat SEPDDS SSITES Soo S RXOS Working Directory C BATCHES CIABATCHESNRXASHASes Bat SESDDs SSITES 959 SRxXSS Working Directory C BATCHES c ftp ashftpmd exe ftp ourserver com usrname passwd cors data SMMMSSYYS DAYSDDS W
30. System Requirements diia 87 DS EE EE asa SD OR Sa ee es 87 Appendix E UTILITY PROGRAM XYZASNIRX sais ee eege deeg ge RES 89 Bol INTRODUCTION E E GEET 89 EAL eer EIER eege 89 Ee Demo VER Lt EE 89 E2 INSTALLATION OVERVIEW EE 89 Po RUNNING ZAS EE 90 EL Mana EN hi nee ei E 91 E 3 1 1 File Selection Window c cccccceccsccsccececaccsccscescsccscecsccscescescscescascscescscscescscascaceecs 93 E 3 1 1 1 RINEX Header Data Edit Window 94 E 3 1 1 2 RINEX Site Position Window 0 ccccsceccsccsceececcscscaccsccscaececcscecsccscascsccscescacens 96 E3312 RINEX Meteorological Plus 96 E 3 1 2 1 Specifying the Source Meteorological Data File oonnnnnnnnnciconencccncccnnnononnarcnrno ooo 97 E 3 1 2 2 Start Day of the Meteorological Data File ccococononnnononononoonccncncnnnononnnnnonononononnnnnnnnos 97 E 321 2 5 Leap Seconds UTC to GPS CONVENIR anda 98 E 3 1 2 4 Specifying the Output RINEX Meteorological Data File ccccccccccccnnnnnnnnmmmmmmm 98 ES 25 Enterme the RINE X Tleader Dala nad 99 E32 Command Ene APPO AA 99 IER Ee E TEE 103 Appendix F RINEX FILE FORMATS suso 103 IC RE EIER EAR TTC 104 AO A A a RE DE 104 Eater REVISIONS POCA PRADO OO O O RAGE SS TS ee A 104 URNA EN TE LO DECO caspa A dos 104 GLONASS EE nico 104 The Phitosopa OL RICA E ee 105 GENERAL FORMAT DESCRIPTION cia a 105 DetimtomOr TAS OI de 105 THe Exchange OL EE 106 E a EE Ehe 107 SE el 107 Order ot
31. When GBSS is called it employs the configuration contained in the files GBSS INI and GBSS SES To set features used during the automatic playback which are different than those normally run for GBSS one would need to make a copy of the files GBSS exe GBSS ses and GBSS ini in a different directory such as the SCNDGBSS directory above Again the reason is that the configuration is stored in the files GBSS INI and GBSS ses By copying the files to a new directory you are essentially mak ing an independent configuration of GBSS You will then need to set the configuration of the copied GBSS using its configura tion windows that is thereby setting the independent configuration You do not need additional sentinel keys to run additional copies of GBSS For the purposes of this discussion assume that the normal GBSS exe and GBSS ini files are in the C Program Files Ash tech GBSS Further assume that you make copies of the files GBSS exe and GBSS ini in the directory DASCNDGBSS You 48 should then launch that is execute the copy of GBSS in the DASCNDGBSS directory and configure the program as desired using the normal menus of GBSS After changing the settings of the copy as desired exit GBSS this will save the configura tion When you initiate the Automatic Playback feature be sure to call the one in the DASCNDGBSS directory In this exam ple you configure your normal copy of GBSS that is the one in the directory C Program Files Ashtech G
32. and store this delta In this 41 context store is meant to imply that the information will be stored as part of the GBSS configuration data Thus if GBSS is exited and then started at a later time these parameters will be recalled including the computed delta One final point Some purists view GPS time as a quantity that can only be expressed as a GPS week seconds of GPS week couple This is not our view For easy interpretation we express GPS time in the format of UTC Hopefully it is clear that the time is not UTC GPS and UTC differ by leap seconds and in other small ways 3 1 8 Post Session Commands Before describing the post session command feature it is important to make a distinction between the terms session and log ging sessions In this manual we refer to sessions and logging sessions as independent concepts Both are related to a period over which data are collected The term session by itself 1s related to the File Duration described in Section 3 1 4 10 In this use we recognize that files are closed at the specified duration and the session codes used to name the files see Appendix A are based upon the Corrected CPU GPS Time see Section 3 1 7 The other use that 1s logging sessions is used to describe the periods in which data are actually recorded into files see Section 3 1 5 independent of the file naming and closure mechanisms GBSS allows you to specify
33. applications would need to build their own inter program interface to do so The third general form is depicted in Figure 3 26 56 GPS Software Interface 1 Receiver External Program GPS Software Interface n RS 232 n R gt eceiver Figure 3 26 Third General Form for External Interface In the above figure we depict one external program interfacing with many copies of GBSS each of which is communicating with a single receiver To be clear GBSS communicates with a single receiver a single copy does not communicate with multi ple receivers simultaneously When configured in this third form each copy of GBSS must originate from its own copy in its own directory on disk That is one must copy GBSS exe and its configuration files GBSS INI and GBSS SES to another direc tory one for each multiple copy desired The rationale for this copying is that the configuration for a single copy of GBSS is stored in its configuration files GBSS INI and GBSS SES Launching multiple copies of GBSS from the same directory loca tion would cause a contention between these copies in terms of their configuration Thus each copy of GBSS could be config ured independently by placing these files in separate directories It is particularly important to note that in the third form shown in the above figure that there are multiple interfaces to the single external program one for each copy of GBSS These interfaces are truly independent ea
34. are converted to L2 or P2 and flagged with bit 2 of loss of lock indicator see Table A2 Units Phase full cycles Pseudorange meters Doppler Hz Transit cycles The sequence of the types in this record has to correspond to the sequence of the observations in the observation records INTERVAL Observation interval in seconds TIME OF FIRST OBS Time of first observation record 4 digit year month day hour min sec Time 516 F12 6 system GPS GPS time system GLO UTC time system Compulsory in mixed 6X A3 GPS GLONASS files Defaults GPS for pure GPS files GLO for pure GLONASS files TIME OF LAST OBS Time of last observation record 516 F12 6 4 digit year month day hour min sec 6X A3 Time system GPS GPS time system GLO UTC time system Compulsory in mixed GPS GLONASS files Defaults GPS for pure GPS files GLO for pure GLONASS files LEAP SECONDS Number of leap seconds since 6 Jan 1980 Recommended for mixed GPS GLONASS 16 files OF SATELLITES Number of satellites for which observations are stored in the file PRN OF OBS PRN sat number number of observations 3X A 1 12 916 for each observation type 3X A1 12 916 indicated inthe TYPES OF OBSERV record 6X 916 If more than 9 observation types Use continuation line s 6X 916 This record is these records are repeated for each satellite present in the data file END OF HEADER Last record in the header section Records marked with are o
35. be created into the primary or secondary data directory structures then that particular file will NOT be available for compression into the primary or secondary compression directories For example the Compress Ashtech formatted B E and S File checkboxes will be dis abled when neither of the Output Ashtech formatted B E and S File checkboxes is selected All of the files selected for compression into the Primary Compression Directory will be stored into a single primary file for the current session Likewise all of the files selected for compression into the Secondary Compression Directory will be stored into a single secondary file for the current session Compression file names are of the following form when file duration is 1 hour or greater syyddd ZIP where s 1s the session code yy is the last two digits of the year and ddd is the day of the year Under the extended naming form and with the File Duration less than 1 hour the session code s becomes a three character 30 field It has the form hmm where A is the hour code that is A to X and mm represents the start minute of the hour Because the File Duration parameter has a lower limit of 0 05 that 1s 3 minutes independent file names will be generated Like the data file names the compression file names depend upon the File Duration parameter see Section 3 1 4 10 and the current corrected CPU GPS time see Secti
36. button you will be presented with a file selection window in which you will enter and or browse for the name of the file containing logging sessions to be imported Export Export pressing this button you will be presented with a file selection window in which you will enter and or browse for the name of the file in which to write the exported ogging sessions Cancel Cancels all changes to the logging sessions After editing each logging session GBSS will automatically sort them The primary sort key used is the file type where the order is Daily Weekly and then Special The secondary sort key is the start time of the logging session 3 1 5 1 Editing a Single Logging Session Section 3 1 5 describes which actions cause the editing of a particular logging session Here we seek to discuss only the particu lars regarding the editing of a given logging session After taking the required action to edit a logging session you will be pre sented with a screen similar to one of the three that follow The format displayed will depend upon the type of logging session being edited Edit Session E Session Scheduling session Type Daity Session Enabled Daily Session Information Session Start Time Hr Min E D jo Session Duration Hr Min E fi fo Session End Time Hr Min fz fo Figure 3 16 Edit Session Window 1 37 Edit Session Session Scheduling Session Type Weekly W Session Enabled Weekly
37. convention for details on the file naming convention see the GBSS User s Manual To select the source meteorological data file simply type its name in the first prompt field provided or use the Browse button next to that field By pressing the Browse button you will be provide with a file selection window similar to that available in other Windows type programs 98 E 3 1 2 5 Entering the RINEX Header Data After pressing the OK button of the window in which you specified the source and target files you will be provided with a window similar to Figure E 10 RINES Meteorological Header Data E Station Hame AAAA Station Humber Station Humber AY TT Creating Agency The AY CS of GPS Comments Test data collected for documentation purposes Sensor Information Pressure Temperature Humidity Model Paroscientific Type Digiquartz Accuracy 0 1 Approximate Position Sensor Position X 1087589 2181 Y 4880918 5164 Zi 3945968 8711 Edit Position v Op SS xYZ s of GPS Figure E 10 RINEX Meteorological Header Data Window In this window you can edit all of the data related to the header data of the output RINEX meteorological file To obtain the spe cifics of the meanings of each of these files it is suggested that you consult the RINEX standard documentation The data of this window will be saved between runs of the program Furthermore this data will be used in the command line
38. create directories that do not exist This is particularly useful when used in conjunction with GBSS That 1s you can repeatedly pass ASHFTPMD the same target directory structure such as the Ashtech sub directory structure for GBSS that is day of the month based with each session closure ASHFTPMD will only attempt to create the direc tory if that directory is not present ASHFTPMD allows you to specify directories that are more layers deep that currently on the remote system that is ASHFTPMD will attempt to create every non existing sub path directory in the entire path C 4 Troubleshooting The following lists the error messages output by ASHFTPMD 1 Message Memory Allocation Error Cannot create memory needed to manage the FTP connection Rationale The above message 1s displayed because Windows 95 or NT has lead ASHFTPMD to believe that too much memory was being used To clear the problem try exiting any background tasks or threads under your control and then re run ASHFTPMD 2 Message ASHFTPMD Connection Failure Connection failure status information Return Code Error Code Message string Line string Rationale The above message is displayed because ASHFTPMD cannot establish a connection with the remote system This message will most often occur when you do not provide enough information to com plete the transaction 3 Message ASHFTPMD Change Directory Failure Failure status information Target Dir
39. epoch of data then the Upload site data to receiver checkbox of the Configuration GPS Receiver menu must be checked see Section 3 1 2 5 for further details When using the built in RINEX converter all of the information in this menu will be stored as part the RINEX file header data see Section 3 1 4 5 3 1 3 1 Configuration Site Site Name The Site Name edit field allows the entry of any 4 non blank characters for the site name With the exception of the charac ter each of the four non blank characters must be legal characters in MS DOS file names Any character in the file name will be translated to the underscore character This parameter may be used for three purposes The first purpose depends upon whether or not the Upload site data to receiver checkbox of the Configuration GPS Receiver menu see Section 3 1 2 5 has been checked If it has and GBSS is in Active Mode GBSS commands the receiver to place this site name in each epoch of the B File data This command will be sent to the receiver each time GBSS is connected to the receiver see Sections 3 2 4 1 4 6 and 4 7 The second purpose of this site name is in the creation of the names of the output B E S and Trap Files Ashtech file names are of the form tnnnnsyy ddd where t is the file type B E S or T nnnn is the 4 character station name S is the session code yy is the last two digits of the ye
40. escape sequence is considered to be delay processing A delay sequence is of the form time where time is the number milliseconds the interpreter should delay before continuing with the upload If the character following the escape character is 0 that is the zero character then GBSS is to translate the octal escape sequence into a binary character to be sent For example 015 is the octal representation of the carriage return character To send a V character the character immediately following the V must be a V Finally the carriage returns or any line feed characters that are normally part of an ASCII file are not sent as part of the uploaded data to send these characters you must use the octal representation of the characters The following provides an example upload file PASHS RCI 5 0 015 012 100 PASHQ RID 015 012 100 PASHQ RAW 015 012 100 PASHS RCI 15 0 015 012 1000 The interpreter translates the above file as follows SPASHS RCI 5 0 lt CR gt lt LF gt wait 100 milliseconds SPASHQ RID lt CR gt lt LF gt wait 100 milliseconds SPASHO RAW lt CR gt lt LF gt wait 100 milliseconds SPASHS RCI 15 0 lt CR gt lt LF gt wait 1000 milliseconds 83 84 UTILITY PROGRAM ASHFTPMD C 1 Introduction Program ASHFTPMD EXE was developed by The XYZ s of GPS Inc in direct support of the Ashtech Geodetic Base Station Software GBSS ASHFTPMD EXE is a 32 bit Windows program that ut
41. failures and will automatically re start after a power failure Please note that there are some special installation instructions described in Sections 2 5 and 2 6 for various configurations of GBSS Although you may not need to use these special instructions it is strongly advised that you familiarize yourself with them before completing the GBSS installation process Finally after installing GBSS and before collecting data operationally it is suggested that you collect some sample GPS data for about 5 minutes and then terminate GBSS through its normal termination methods described later in this manual The reason 1s simply that GBSS collects information about your computer and receiver to which GBSS 1s connected and then stores that infor mation in its configuration files This information 1s primarily used in the naming of output files If you do not follow the proce dure you could have some incorrectly named files 2 2 GBSS Support Utilities GBSS comes standard with three stand alone utility programs These programs are installed into the utils sub directory of the GBSS installation directory In order for these programs to function properly the location of the utils directory must be made known to the Windows operating system This can be accomplished by adding a statement to the Path indicating the location of the utils directory Please contact your system administrator or MIS department for complete instructions on h
42. for Auto Startup GBSS can be setup to automatically connect to the GPS receiver once your operating parameters have been set When this fea ture is enabled the base station software will automatically startup and connect to the GPS receiver when Windows is started This is particularly useful for example when it is desired that data logging be continued immediately after a power failure To accomplish this the base station software must first be configured to your specifications Connect GBSS to your GPS receiver and verify that all parameters are set correctly Then complete the instructions that follow During the installation of GBSS you were asked if you wanted GBSS to automatically startup each time Windows is started If you answered yes to that question then most of the manual steps described herein have already been done for you To set GBSS to automatically start when Windows starts follow these steps 1 Determine the drive and folder in which GBSS EXE is stored this can be done by using the Windows 95 or NT Start Find Files or Folders feature 2 Add GBSS EXE to the Windows Start Up folder a Press the Windows 95 or Windows NT Start button b Select Settings c Select Taskbar 1 When the Taskbar Properties window is shown select the Start Menu Programs Tab 60 11 Press the Add button 61 iii For the Command line enter the complete path of GBSS EXE found u
43. has meaning when GBSS is in its Active Mode see Section 3 1 2 1 It does not apply when GBSS is in its Passive Mode Placing a check into this box instructs GBSS to command the receiver to stop recording epoch and navigation data to the receiver s internal memory but the receiver will still output epoch related data to GBSS This command will be sent to the receiver each time GBSS is instructed to Connect to the receiver see Sections 4 1 3 2 4 6 and 4 7 16 3 1 2 4 Configuration Receiver Receiver Outputs lts Compressed Data Records The Use compressed epoch measurements checkbox is available and has meaning when GBSS is in its Active Mode see Sec tion 3 1 2 1 It does not apply when GBSS is in its Passive Mode Placing a check into this box instructs GBSS to command the receiver to use its compressed observation message format for example DBEN and MACM At times it can be advantageous to have the GPS receiver output in 1ts compressed message format A limited bandwidth radio link is such an example Please note that some receivers do not support these formats and you should consult your receiver operations manuals for details 3 1 2 5 Configuration Receiver Upload Site Data to Receiver The Upload site data to receiver checkbox 1s available and has meaning when GBSS is in its Active Mode see Section 3 1 2 1 It does not apply when GBSS is in its Passive Mode Placing a check into this box instructs GBSS to up
44. is reached that is for hour 23 of the day However when the File Duration is less than 1 0 71 hour this form of human readable discernable file names can no longer be used Therefore GBSS provides three file naming modes 1 Classic GBSS Names 2 Classic Ashtech Names and Extended RINEX names 3 Extended for both Ashtech and RINEX Names As can be seen there are two choices containing classic naming and two choices where extended naming 1s available Under the classic naming form with the File Duration less than one hour the normal file naming convention does not apply in that the s that is session and ddd that is day of year codes become incrementors At the start of logging the session code s becomes A and ddd becomes 000 As the File Duration is reached the files are closed and new ones are opened with the s set to A and the ddd becomes 001 With each File Duration this process continues until s is set to A and ddd is set to 999 At this point the increment causes a rollover where s is set to B and ddd is reset to 000 This rollover process continues until s reaches Z and ddd reaches 999 At this point each time ddd reaches 999 it is simply reset to 000 Under the extended naming form with the File Duration less than one hour the session code s bec
45. key protects GNSS2GPS When distributed with Asthech s GBSS GNSS2GPS will use the same sentinel key as is provide with GBSS D 3 Using GNSS2GPS Again GNSS2GPS was designed to create GPS only Ashtech files from Ashtech GPS GLONASS receiver data files B and E Files At the time this documentation was published GNSS2GPS was tested on Ashtech GG 24 and Z18 receivers The syntax of the command line call to create GPS only data files from GPS GLONASS data files is as follows GNSS2GPS B src_bfile tgt bfile E src_efile tot efile To create a GPS only B File from a GPS GLONASS B file use the B option followed by a source src_bfile and target tet bfile B Files To create a GPS only E File from a GPS GLONASS E file use the E option followed by a source src_efile and target tgt efile E Files You can in a single run create both B and E files by using both the B and E options Examples gnss2gps B BREMDA98 093 C GPSOnly DAT BREMDA98 093 Creates the GPS Only B File CAGPSOnly DATBREMDA98 093 from the source GPS GLONASS B File BREMDA98 093 stored in the current working directory enss2gps E EREMDA98 093 C GPSOnly DAT EREMDA98 093 Creates the GPS Only E File C GPSOnly DAT EREMDA98 093 from the source GPS GLONASS E File EREMDA98 093 stored in the current working directory gnss2gps B BREMDA98 093 BREMDAv8 093 E EREMDA98 093 EREMDAv8 093 Creates the GPS Only B File BREMDAv8 093 from the source GPS GLON
46. later in the parallel sequence for example you could attach the sentinel key to a DB 25 male to DB 25 female cable which 1s connected to your computer s parallel port E 3 RUNNING XYZAshRx XYZAshRx creates RINEX Version 2 0 files from Raw Ashtech Observation files The program can be manually instructed to convert files or can be called directly from the command line This latter method allows programs to invoke the converter with out the need of human intervention Throughout the remainder of this documentation we will call the former approach the Man ual GUI approach and the latter will be called the Command Line approach Both the Manual GUI and the Command Line approaches rely upon configuration information contained in the INI file associ ated with the converter program This INI file is called XYZAshRx INT and is stored in the same directory as the main pro gram Changes to this configuration file occur whenever the user changes configuration using the Manual GUI approach That is when desiring to use the Command Line mode you should pre set the configuration using the Manual GUI approach Sec tion E 3 1 will describe the Manual GUI approach to using XYZAshRx and Section E 3 2 will describe the Command Line approach to using XY ZAshRx It is important to re state the fact that the configuration information is stored in the file XYZAshRx INI which is stored in the same directory as the program file that is XYZAshRx EXE
47. line feature see Section 3 1 5 you have complete control over file names created using PKZIP or PKZIPC Furthermore you have complete control over the target directories of the output compression files and the input files compressed by these programs including any files that may not have been generated using GBSS A 7 NMEA Output File Naming Approach NMEA Message output or capture file names of the following form syyddd NMA where s is the session code yy is the last two digits of the year and ddd is the day of the year For example a file named C97233 NMA is a NMEA message capture file for session C of day 233 of 1997 Like the data file names the NMEA capture file names depend upon the File Duration parameter see Section 3 1 4 10 and the current corrected CPU GPS time see section 3 1 7 A 5 LOG File Naming Approach The GBSS Log file names are of the following form yyddd LOG where yy is the last two digits of the year and ddd is the day of the year For example a file named 97233 LOG is a GBSS Log file for day 233 of 1997 In the year 2000 the file name would begin with 00 Like the data file names the compression file names depend upon the File Duration parameter see Section 3 1 4 10 and the current corrected CPU GPS time see Section 3 1 7 81 A 6 Compression File Naming Approach Compression file names are of the following form for files of 1 hour duration or greater syyddd ZIP wh
48. menu labeled Entry in Modules Menu allows you to specify whether or not you want an entry in the Modules item of the GBSS main menu That is once you allow real time interface with external programs a Modules entry will be added to the GBSS Main menu as shown in Figure 3 29 EM Geodetic Base Station Software File View Modules Configuration Help Figure 3 29 Modules Addition to Main Menu By configuring an Entry in the Modules Menu you then are specifying whether or not you want an entry in the Modules menu The above example would add the following to the Modules Menu Figure 3 30 59 ER Geodetic Base Station Software File View Figure 3 30 Added Modules The Command Line area of the External Modules Configuration window allows you to specify how GBSS is to launch the external module You MUST provide BOTH the Command Line and the Working Directory Failure to do so could result in erroneous behavior of the external module When supplying the text of the command line not the working directory you should use quotation characters to clearly state path names with spaces in them Notice in the example provided that the entire command line is quoted This is because we are quoting the entire full path to the executable Meteorological Module program When the command line is used to call an external program with additional command line options only the entire full path of the execut
49. minute second SV clock bias sec TauN SV relative frequency bias GammaN message frame time sec of day UTC Broadcast Orbit 1 Satellite position X km 3X 4D19 12 velocity X dot km sec X acceleration km sec frequency number 1 24 Broadcast Orbit 2 Satellite position Y km 3X 4D19 12 velocity Y dot km sec Y acceleration km sec frequency number 1 24 Broadcast Orbit 3 Satellite position Z km 3X 4D19 12 velocity Z dot km sec Z acceleration km sec frequency number 1 24 121 Table F14 GLONASS Navigation Message File Example ac Ra s 2109 3 022s ac 0822 3 5 0 eeben en GLONASS NAV DATA ASRINEXG V1 1 0 VM AIUB STATION ZIMMERWALD L998 2 16 RINEX VERSION TYPE PGM RUN BY DATE COMMENT CORR TO SYSTEM TIME END OF HEADER VO FEB 20 PUSO 0 379979610443D 06 J DOS e do OU O gt Bak JS Oo LOG2Z1 S903 520 DFU Ui 0 944422070313D 04 0 Osa Ee Us de 2 15 ls Dao Os Os 262136621004DF04 0 Us Soo LIZA VA 1D 00 Et Ud 62593291015 6D 04 Os DO a En e DDD US Voodoo 00D TO a 0210636037 54683D05 0 Kl 1025504 45D 05 O Z 45 0 do Dub Us sLOLiSsletoe40eD 05 0 LL LAS TSS ZOD GE ODO MZ Dar AU 16352334294 1D 03 O 348924636841D 00 0 ZOCLO38 56 94D701 00 144599342346D 01 0 LIBS ISVS Eeler U 2590740977 66D 00 0 LOZZO3Z25966 eDr0L U 3392597907300 ADA DON 212040410532 D ZO 5 39Z01 266460701 Ox TE2ZIZ3 507 690 D701 44 7064399719D 00 0 199414789
50. pertain to the drives speci fied for the Primary and Secondary Data directories see Sections 3 1 4 3 and 3 1 4 4 That is the specified Primary and Sec ondary Data directories also contain drive letters The drive letters of these two directories even if they are the same are used as the primary and secondary drives of this display It is important to note that GBSS also has Primary and Secondary Compression directories GBSS makes no effort to display the available disk space of drives specified by these two directories unless they are duplicated by the drives specified for the Primary and Secondary Data directories In some situations this might encourage a user to place the compression directories on the same drives as the data directories The available disk space is shown in units of Kilobytes that is the number of bytes divided by 1024 4 2 5 RS 232 Line Status Indicators The RS 232 Line Status Indicators are located at the upper right of the GBSS window and are used to provide a positive indica tion of the RS 232 status lines They are only active when GBSS is connected to an Ashtech receiver that is just because a receiver is connected to the computer does not imply that GBSS recognizes the receiver you must instruct GBSS to connect to the receiver before these status lines become active Normally both the DSR and CTS indicators are green Typically when the DSR is green and the CTS is not then the connection is failing at th
51. programs to be called at the completion of a session that is when the File Duration expires Through this feature you can have GBSS pass information created from within GBSS to other programs For example you can have GBSS call an FTP program to distribute all of the files just collected to several Internet FTP sites This simple feature pro vides you with a very powerful system integration capability that exploits programs supporting command line parameters or scripting Before continuing however it is important to state that the Post Session Command feature provides great flexibility and power With this flexibility and power comes the potential to incorrectly call programs external to GBSS This is because GBSS has no knowledge of correct vs incorrect calls to external programs and cannot therefore provide any checks of correctness before the calls to these external programs are actually made Only advanced knowledgeable users should exploit the Post Session Com mand feature Presented in Section 3 1 8 3 of this document 1s an additional set of warnings regarding the Post Session Com mand feature that should be reviewed 3 1 8 1 Post Session Commands Window The Post Session Command Window Figure 3 21 is the window through which you enter modify order and delete post session commands Post Session Commands Window Warning Please See User s Guide For Detailed Instructions Crd Enabled wait warn Command fa ves
52. receiver Geodetic Position Window Earth Centered Earth Fixed Position Window Channel Summary Window Diagnostic Messages Window Logging Summary Window Post Session Command Summary Window oe ee eS T Time Display Window Each of these windows is accessed via the View menu selection from GBSS and then selecting the appropriate display You are free to resize all of these windows as desired To return any window to its default size with the exception of the Diagnostic Mes sage window simply right click within the display area of the window and chose the Window Size to Default option Section 4 2 9 describes moving these windows within the area provided by the main window 67 4 3 1 Geodetic Position Window Figure 4 4 provides an example of the Geodetic Position window Geodetic Position Epoch Point Position W4G5 84 Site Id AAAA Latitude 38 464663 36 27 52 79124 East Long 282 56118299 282 33 40 25876 West Long 77 43881701 E 26 19 74124 Ellipsoidal Height 32 6696 Clock Offset 92746 6434 Hum Sats 5 Clock Drift 316 0817 PDOP 5 3 Base Station Reference Position GS 34 Latitude Hone East Long Hone West Long Hone Ellipsoidal Height Hone Figure 4 4 Geodetic Position Window Notice that the window is divided into two parts 1 the epoch point position and 2 the base station reference position The upper portion that is that which is labeled Epoch Point Position contains in
53. remote or host computer Almost all FTP host sites require some form of login WS FTP Pro allows one to specify information needed to fully establish a connec tion with a host system Among the information specified 1s the host name normally some form of an Internet address the user login name and a password for that user Likewise ASHFTPMD needs this same information WS FTP stores the needed information as part of its initialization file or INI file However that information is encrypted and therefore unavailable to ASHFTPMD In short both WS FTP Pro and ASHFTPMD will require the same entries for the host name user name and user password Both programs will require that entry Pan gee ee The command line call to create a directory using ASHFTPMD 1s as follows ASHFTPMD host userid password tgtdir L logfname where host is the host name of the target system on which ASHFTPMD will make a directory userid is the user ID for logging into the designated host password is the password associated with userid tetdir 1s the target directory on the host computer logfname which is optional is the name of the file in which to log all FTP transactions using this program Please note that the call assumes that the underlying Internet connection has been established and that there is a WinSock like interface running and available to ASHFTPMD such as an Internet dialer available under Windows NT 85 ASHFTPMD will only attempt to
54. section of BOOT INI See the example below for more information 6 Save BOOT INI and exit Notepad 7 Restore the hidden system and read only attributes to the BOOT INI file determined under step 2 The following example shows modifications made to a BOOT INI to prevent the detection of serial mouse devices boot loader timeout 5 default multi 0 disk 0 rdisk 0 partition 1 WINDOWS operating systems multi 0 disk 0 partition 1 WINDOWS Windows NT Workstation Version 4 00 NoSerialMice multi 0 rdisk 0 partition 1 WINDOWS Windows NT Workstation Version 4 00 VGA model basevideo sos NoSerialMice Complete documentation on preventing the detection of the serial mouse can be found on Microsoft s home page at htip www microsoft com under Article ID Q131976 As per that article the syntax of the NoSerialMice is as follows NoSerialMice Disables the detection of serial mice on all COMM ports NoSerialMice COMn Disables the detection of serial mice on COMM port n where n is the number of the port NoSerialMice COMx y z Disables the detection of serial mice on COMM ports x y and z The final item in the list of special Windows NT installation instructions has to do with Windows NT s multi tasking environ ment Windows NT drivers and the Auto Connect feature of GBSS Specifically the Rainbow sentinel drivers which are installed as part of the automatic installation are started and initialize
55. sinais 76 CNCA iis a E 29 CONEA O ad 11 COMME UTA OM file o id 5 129 connecting tO a receiver cccccccncnnnnnnnnnnnnnnnns 12 connection failure iia 86 continuous reference station 6 convert B E and S files 28 current corrected CPU GPS time 81 current CPU UME aida 102 current epoch time occcccnnnnnnnnnnnnnnnnnncnnnnoos 36 currently selected upload file 17 data lesionada 20 Gay OL VOAR Juss RERA 102 DB aa 7 11 A A 17 Gel aUulPOPlONS noia 6 delay SEQUENCO a idad 83 diagnostic log file cccccccnccnccnnnnnos l diagnostic Messages ini 39 directory structures ccccncnnnnnnnnncnncnnnnnnnnos Pes SK SPACE aia dias 87 dual requenoy s n l dual frequency file set 28 E edit output path eet 26 29 epoca CANSO io ia 33 epoch filtering rate ooccccccncccncnccocicinnnos 24 Epoca Miera oi l erroneous data vismannen n 65 escape CHALACUED arerioen 83 ESCAPE SEQUENCE eege eege 83 executable program oocccccccnccncccccccnnininininos 5 expanded aid 46 external modules 55 58 external program interfacing 6 external program modules 58 external programs ccoccccccccncccccccncnicininos 7 55 EN SLAUUS seta 86 PAT Sisa 24 33 fatal system CILOR iria 33 MICAEL EE 2 Aae E EE 2 TING TSOP CM TAE aoia 33 A E E eter a l EN Cc Aa 0 E EEE TE A AT 1525 first time run GBSS oocccccccnn
56. so II SR a 40 Eege 42 Lol Post session Commands Window Ate dee 42 3 1 8 2 Post Session Command Line Editor Window oooocccnnnnnnnncncncnnnnnnnnnononnnnnnnnnnnnnnnnnnnnnnnnnnnnnns 44 3 103 6B55 and Post Session Commands ni A 46 3 1 8 4 Post Session Command Line Examples ooooooonnnnnnnnnnnnnnnnoncccnnnnnnnnnononococnnnnnnonnnnonncnnnnnnnos 48 519 extemal Modules Comme A o 55 3 1 9 1 Conceptual View of the External Module Interface oooonncnnnncnnncnooonnnccnnnnnnnnononocccnnnnnnos 56 3 1 9 2 Configuration Description Through an Example ccccccccnnnnnnnnnnnnnnnnononcncncncncnnnnnnnnnnnonoss 57 32 Conncurme GBSS tor AULO SLartip sas vise dled rasta datas ai go ada ai Da a aac 60 Chapter 4 RUNNING THE GEODETIC BASE STATION SOFTWARE 63 4 0 RUNNINGGBSS OVERVIEN tp E E ac ide 63 4 1 Connecting To and Disconnecting From the Receiver nnnnennnnnnssssssssssetttrrrenonsnsssssssssssssens 63 AD va Display W Ind OWN 64 AD POCO COUMMICIS stand SD DA aii Sa 65 Az 2 Broadcast IES CONES a Aa RA Aga O SO 65 AS Or EE 65 ADA E ER ET ge 65 AD e GR Line Status INGICAIONS EE 65 420 Logomo Status EEN 66 AD COMME CUS LAU RR RE DO PR isc 66 42S Epochr Time Eelere eege 66 4 2 9 Sub Window AAA A ee 66 A210 TOS CIs Sessions AUS Baran bashes aes aiii E RAD RG 66 4 3 status and Display SUD WINdOWS riera ladra SER anda 67 Al CAC OCS MC Position WINdOW aii 68 4 3 2 Earth Centered Earth Fixed Position Wind
57. station name S is the session code yy is the last two digits of the year and ddd is the day of the year In this classic form the session code is usually a letter Under this approach and with a File Duration of 1 0 hour the session code can start at A that is for the 0 hour of the day increment to B on the next session that is for hour 1 of the day and continue with each session until X is reached that is for hour 23 of the day However when the File Duration is less than 1 0 hour this form of human readable discernible file names can no longer be used Therefore we have provided three options 1 Classic GBSS names 2 Classic Ashtech names and Extended RINEX names 25 3 Extended names for both Ashtech and RINEX As can be seen there are two choices containing classic naming and two choices where extended naming is available Under the classic naming form and with the File Duration less than 1 hour the normal file naming convention does not apply in that the s that 1s session and ddd that is day of year codes become incrementors At the start of logging the session code s becomes A and ddd becomes 000 As the File Duration is reached the files are closed and new ones are opened with the s set to A and the ddd becomes 001 With each File Duration this process continues until fs is set to A and ddd is set to
58. step 5 and those created by GBSS through its connection to a local GPS receiver to the target network drive directory The content of the batch file called is as follows REM FILE COPIER BAT REM 1 GBSS Data path REM 2 2 digit Year REM 3 Month REM 4 2 Digit Day REM REM SYNTAX copier bat SFPDDS SYY SMMMS SDDS REM mkdir e RefData 2 mkdir e RefData 2 Month 3 mkdir e RefData 2 Month 3 Day 4 copy 1 e RefData 2 Month 3 Day 4 del Q 1 The batch file first attempts to make the target directory on the network drive Notice that if the target directory already exists the mkdir commands which is also an MS DOS intrinsic command will fail but will not cause the batch file execution to termi nate Next the batch file calls an MS DOS intrinsic command to copy all of the data from the source directory that is the GBSS Primary Data Output Path to the target network drive The batch file then deletes in the no confirmation asking or quiet mode the files in the GBSS Primary Data Output Path As you can see by the documentation of the batch file that 1s the text immediately following REM on the first eight lines of the file that there are four arguments passed to this batch file These arguments relate in order to the parameters expressed in the last post session command 3 1 8 4 4 RINEX Session Rename and Push to an FTP Server Example The primary objectives of this example are 1
59. the Activate Session Programming checkbox Type Describes the type of logging session 1 Daily 2 Weekly or 3 Special Session Start Describes the start of the logging session for the given type The format of the column differs depending upon the logging session type For Daily types you see the hours minutes and seconds that is in the HH MM SS format For Weekly types the time is expressed in day of week hours minutes and seconds that is in the ddd HH MM SS format For the Special logging sessions the time is expressed by year month day hour minutes and seconds that is in the YYYY TT DD HH MM SS format Session End Describes the end time of the logging session The format of the column differs depending upon the logging session type For Daily types you see the hours minutes and seconds that is in the HH MM SS format For Weekly types the time is expressed in day of week hours minutes and seconds that is in the ddd HH MM SS format For the Special logging sessions the time is expressed by year month day hour minutes and seconds that is in the YY YY TT DD HH MM SS format GBSS will record data up to but not including the logging session end time Duration Describes the duration of the logging session The format of the column differs depending upon the logging session type For Daily types you see the duration expressed as hours minutes and seconds that is in the H
60. the file A99005 NMA from the current working directory as the input meteorological data file The output RINEX meteorological data file will be placed in the file N1020051 99M Furthermore the converter will use the GPS time 991 176752 that 1s the GPS week and seconds of GPS Week respectively to designate the start day of the source meteorological data Notice that 176752 does not fall on an exact day boundary This is acceptable because the source data is time stamped with time of day Therefore the specified GPS time need only be accurate to the day in which the data falls as the converter will resolve the time of day within that day Again the value stored for the leap seconds parameter from the last GUI run of the program will be used to convert UTC time tags to GPS time see Section E 3 1 2 Finally please notice that using the command line approach allows you to use the post session commands of GBSS to automati cally convert your meteorological data to RINEX when GBSS ends a collection session The following 1s an example ofa GBSS post session command Command C Program Files ASHTECH GBSS UTILS XY ZAshRx exe M NFP SITES DDD S Y Y M GPW GPS Working directory of the command C Program Files ASHTECH GBSS UTILS In the above example the name of the NMEA capture file including its full path is passed to the conver sion program using the GBSS mnemonic SNFPS The output file name is created by concatenating several mnemonics an
61. the same receiver they should be applied In this case the respective code and phase observations have to be corrected too c bias if expressed in meters Unknown such biases will have to be solved for during the post processing The small differences modulo 1 second between GLONASS system time UTC SU UTC USNO and GPS system time have to be dealt with during the post processing and not before the RINEX conversion It may also be necessary to solve for remaining differences during the post processing Pseudorange Definition The pseudorange code measurement is defined to be equivalent to the difference of the time of reception expressed in the time frame of the receiver and the time of transmission expressed in the time frame of the satellite of a distinct satellite signal If a mixed mode GPS GLONASS receiver refers all pseudorange observations to one receiver clock only the raw GLONASS pseudoranges will show the current number of leap seconds between GPS time and GLONASS time if the receiver clock is run ning in the GPS time frame the raw GPS pseudoranges will show the negative number of leap seconds between GPS time and GLONASS time if the receiver clock is running in the GLONASS time frame In order to avoid misunderstandings and to keep the code observations within the format fields the pseudoranges must be cor rected in this case as follows PR GPS PR GPS c leap seconds if generated with a receiver clock running i
62. this Epoch Filtering feature This feature of GBSS very useful when you wish to post data with a low epoch rate say 30 seconds yet retain the possibility of turning the same session data into a higher epoch rate say 1 second at a later date This can easily be done with GBSS and the epoch filtering feature combined with the Trap File feature For example if the epoch filtering value is set to 30 0 seconds and the receiver 1s set to output real time data at 1 second then GBSS will store the raw trap data unfiltered and then create 30 second epoch B File and RINEX files Later you can use the playback feature of GBSS and the Trap Files to obtain Ashtech Format files and RINEX format files with true epoch intervals at up to a 1 second rate The range of acceptable values for this field are 1 and 0 01 3600 seconds A value of 1 disables epoch filtering that 1s all received epochs are output to the B File 33 3 1 4 13 Configuration Output Files File Deletion Age The File Deletion Age parameter instructs GBSS to delete files older than a given number of days In determining if a candi date file can be deleted GBSS uses the name of the file and the current corrected CPU GPS time see Section 3 1 7 GBSS will only select candidate files that meet the Ashtech naming convention Additionally the candidate files come only from those directories specified in the primary and secondary data and compression directories and any subdi
63. will be displayed in the Post Session Command Summary Window in the Diagnostic Message Window and in the Log file The time at which the command was launched in seconds of GPS week will be reported to the Diagnostic Message Window and the Log file It is important to note that when GBSS is operating in the Simulation Playback or Auto Playback modes and the end of a File Duration is reached all post session commands will be completed from the perspective of GBSS before continuing the simula tion playback Additionally regardless of the Wait flag on each command each command will be launched in a wait for com plete mode that is as if the Wait flag was set for each command The following lists some miscellaneous topics and warnings related to the Post Session Command feature 10 GBSS will permit 100 post session commands GBSS cannot verify the complete correctness of any Post Session Command As such users should fully checkout their post session commands and the impacts of these commands upon other components of their system before allowing the post session commands to become part of operational environments Users should fully checkout their post session commands before allowing them in operational environments The checkout should include implementing the commands in the GBSS environment Command line sequences which take more than the File Duration to complete from both the perspective of GBSS and Windows shoul
64. 000000D 00 sso 2000000000D703 sa es 18925222 ses a e e a e 119 Table F 11 Meteorological Data File Example SSS ae A o o kees 2 METEOROLOGICAL DATA RINEX VERSION TYPE XXRINEXM V9 9 ATUB 3 APR 96 00 10 PGM RUN BY DATE EXAMPLE OF A MET DATA FILE COMMENT A 9080 MARKER NAME 3 PR TD HR TYPES OF OBSERV PAROSOCIENT LE IC 740 16B J SENSOR MOD TYPE ACC HAENNI SENSOR MOD TYPE ACC ROTRONIC 1 240W SENSOR MOD TYPE ACC Kach 0 0 SENSOR POS XYZ H END OF HEADER IG te QS DAS Ol TOG od 916 d Oe SO GOTA VOLEI SE SES LL W o Gray ch dck od heeten Table F 12 Glonass Navigation Message File Header Section Description Header Label Columns 61 80 RINEX Version Type Format version 2 01 F9 2 11X File type G GLONASS nav mess data A1 39X Pgm Run By Date Name of program creating current file Name of agency creating current file Date of file creation dd mmm yy hh mm Description Corr to system time Time of reference for system time corr year month day 316 3X D19 12 Correction to system time scale sec to correct GLONASS system time to UTC SU TauC End of header Last record in the header section Records marked with are options 120 Table F 13 Glonass Navigation Message File Data Record Description OBS RECORD DESCRIPTION FORMAT PRN EPOCH SV CLK Satellite almanac number 2 Epoch of ephemerides UTC 513 year 2 digits F5 1 month D19 12D19 12 day D19 12 hour
65. 1 Specifying the Source Meteorological Data File To select the source meteorological data file simply type its name in the first prompt field provided or use the Browse button next to that field By pressing the Browse button you will be provided with a file selection window similar to that available in other Windows type programs The file type you will be looking for will normally have a NMA extent This is because the file is actually created by GBSS and stored in the Ashtech NMEA file format This is important because you must instruct GBSS to store the NMEA file via its Configuration File Outputs menu options Furthermore GBSS must be configured to store the XDR and GXP NMEA mes sages This is because the XDR message will contain the meteorological sensor data and the GXP message will contain the time tag associated with the XDR message Please note that XYZAshRx assumes that the Meteorological data is sampled near the time stated in the GXP message That said it should be clear that the accuracy of the time tag as it relates to the XDR message is the rate at which the GXP messages are being output E 3 1 2 2 Start Day of the Meteorological Data File Two key facts must be considered when converting the NMEA capture file created by GBSS 1 the NMEA GXP message con tains only time of day time tags and 2 the NMEA GXP message contains UTC time tags In this Section we address item 1 item 2 is addressed in Sectio
66. 18 Table F 10 Navigation Message File Example Sheet 2 N GPS NAV DATA XXRINEXN V2 0 ATUB EXAMPLE OF VERSION 2 FORMAT LO ToD 07 se O Debi ch Ee 1192006 JL 208D 0 6 e Ee gt 13100506 1960DFD6 TON BETA SST LAS ADUD D6 POTAOIS oe TO UD 292960 DELTA UTC AO AL T W 6 LEAP SECONDS END OF HEADER RINEX VERSION TYPE PGM RUN BY DATE COMMENT ION ALPHA EASE 90 522 6 90 Do ZL DA 4440 910000000000D 02 484101474285D 05 409904000000D 06 eI TS 41e663136D 0i1 sS071L55651409D 09 000000000000D 00 406800000000D 06 o ee BO Ye Dal 133000000000D 03 498816370964D 05 414000000000D 06 LLOTI ADO OND a O DRE o po a OL De LDL 000000000000D 00 410400000000D 06 SD USC OS DDS 294062500000D 02 6260740418375D 02 242143869400D 07 ZOO O DR 000000000000D 00 000000000000D 00 MIJOA SOL 7 LOZD 03 e 203 129000000 DF02 200239347760D 02 AO PO VILO Je YA e LLG 7 OO00V00DF0S 0QO0000000000D 00 200000 0000000D 4 00 16998021030 ADALU 116040547840D 08 sO9Z1IZ066746D 05 329237003460D 00 ADO OZ OSO DO 99 L000000000D 05 000000000000D 00 20U4603050 7699D 11 146970407622D 08 coz SL 500 E Let CASO EIo pA DFO RE RO 199 L000000000D 03 000000000000D 00 V00000000000D 00 162092304801D 00 9015365489006D 04 9096046447754D 07 OSOS LAZO US 000000000000D 00 210000000000D 02 000000000000D 00 KZ OZ 9 OI Ee ER 9015328476143D 04 390 193544 769D 07 SOLO LO SOS MS 000000
67. 23 186696 400 LIO O ZO LIADO ODA DUO 25 s 000 322000 25844592 349 25844601 444 25844634 056 4 000 LISO LOO S250 26 FOZ 1989323099336 199343 92a 1687 448 000 394 000 ZO 1MOZ Oe IZA Zot LOZ TA OTS ZO LOZ GOs TOS 6 000 94000 2069 13127600 ZVOS 737 22514 BOOS OT Oe AS 295 4000 254 000 ad e dd Or A 21449267 180 21449267 588 21449270Z O 27 SOE COOL ts a Ce EE 1693000 LOO SOIL LISO ODO LI io ZLILADI ID O 22314854 143 22314856 548 C9Z0 710 OZ 374 000 94 000 ERR 4965160 004 386 6954 973 ZIG Re OM RES ZO 2 LIO LOS E e E Ee A 4965160 003 109000 20 000 30 000 LASSZS TEU TZ LIZ071 49 974 LIDIA ADO LOSADA DOS ZO GLOGS EE 143823 154002 80 000 3000 10 000 LEO UL LA SA DO ESA e 19849974 840 19849974 231 LICL Io da OL 3UZLOO 693912 834 000 444 000 384 000 1559 50 94 1212120230 APA E RASO ZO TAG oO ZVI ZO Os LIZ 595907 949 691000 284 000 241 000 00 FO 0 20 0000000 O 6 4 25 FT 49 LL 16 5582917 443 AI IU OO 21429471 814 21429472 290 21429474 716 30823911 4 74 330 000 167000 15332000 90962092152 17087949 770 2228143175 102 LL SAD OS Zu LOLA UL 2900620 E 3P FGU HE RE Pir SOO SLO 97 16 403 4051727 634 238753604 448 LIO 13304 2521 LIO ISO O AO LIA LS IO 1990000 24 000 dks 000 14730992 6935 LIATOTZS SE A OL E ZIMIO OS A UN EAS TAS OO Aa 49 000 ODO 94000 L7664730629 1376470 294 ZOTOO E 20766909 047 Z0766912 143 LT664 73 029 6632000 20620000 236 000 e A AY DES Y Ml 2 LO e 073709 1980390108 241 190090669 701 TIOS LO EZ Lo ARAS
68. 3 1 1 for the specifics in this area as they also apply under the Command Line approach The general form of the command line call to XYZAshRx is as follows XYZASHRX EXE I bfile efile sfile ionfile options Notice that you are minimally required to use the I option and specify the names of the B and E Files parameters bfile efile respectively All items enclosed in and are optional For example the names of the S File and I File are optional When specifying the input file names 1t is assumed that either the current working directory contains the source data files or the full path to the files is specified as part of each file name For example the following call assumes that the input B E and S Files come from the current working directory Example 1 XYZAshRx I BN102A97 323 EN102A97 323 SN102A97 323 In the following example the B file comes from the directory DABDATA and the S file comes from the directory E EDATA notice that no S File is specified Example 2 XY ZAshRx I D BDATA BN102A97 323 E EDATA EN102A97 323 The list of options for the program can be combined in any order and are as follows O obsfile N navfile T path S smooth C change When neither the N nor the O options are specified XYZAshRx will automatically create the names of the output RINEX Navigation and Observation files Additionally in this case XYZAshRx will place these output files in the curr
69. 3 Configuration File Outputs Primary Output Path The Primary Output Path Edit field is used to specify the top level primary directory where data files will be stored This directory specifies where files will be stored when the file s Primary checkbox of the File Output Selection is checked see Section 3 1 4 5 To change the directory you can manually edit the output path or use the browse feature To use the browse feature click on the BROWSE button to the right of the text Primary Output Path On selecting this button you will be provided with a window that is capable of navigating over the entire set of directories of your computer Use this window to select the desired primary output directory If the desired directory does not exist simply use the New Folder button in the upper right corner of the direc tory selection window to create it Once you have identified a Primary Output Path then any data type that has the Primary field checked alongside 1t will be stored in that directory Consider the example shown in Figure 3 13 26 File Dutput Configuration H ES File Modes Data Files Compression Files NMEA Capture File ASIM Files Primary Output Path Browse EPRI DIR Secondary Output Path Browse ESEC DIR File Output Selections Output Directory La Primary Secondary Output Ashtech formatted B E and S Filez Output L1 Only Ashtech formatted B E and S F
70. 324530 0 70 Diagnostic Messages Figure 4 9 Diagnostic Messages Window The amount of messages displayed through this window is controlled by the Display verbose diagnostic messages checkbox on the Configuration Other Options menu see Section 3 1 6 4 3 5 Logging Summary Window The Logging Summary window Figure 4 10 provides a summary of the data being logged from the receiver The following shows an example of this window when there are no files selected for output to the secondary data directory E Logging Summary Figure 4 10 Logging Summary Window 1 71 In the example shown in Figure 4 11 both the primary and secondary directories have data being written to them Logging Summary File Duration E hours Fitering Hone Sec Interruptions 9 Logging Since 041308 18 16 14 GPS Last Interruption 05 08 98 02 34 17 GPS Epoch Interval 5 00 sec Elevation Mask 0 deg Primary Directory EPRI_DIR May98 Day1 EU secondary Director ENSEC_DIRiMay98 Dayl Ai Ashtech Files BAAAAS98 133 EAAAAS98 133 SAAAAS98 133 L1 Ashtech Files lt BAAMASX8 133 EAAAASX8 133 Jonas Ashtech lon File omg Ashtech Trap File TAAAAS98 133 RINEX Files AAAAI33980 AAAAIS3 98N RINEX L4 Files ananga AAAA133 X8N Figure 4 11 Logging Summary Window 2 The text of the paths and the names of the output files are color coded to show which files are targeted for which directories Those fil
71. 67 7D 04 0 st I ZoZcIOZIS646D 06 LISIS Ee De U ZOO LOU ALIADO 559808686376D 04 0 143945598602D 01 O SOS PISO IVS DELL DOLLS AZ TEO le Joa Aa POLIDO 186264514923D 08 000469124 Des EK 9313272 OR E TILL O AO LODOS 000000000000D 00 GE 220 70 oD 09 000000000000D 00 186264514923D 08 Lo Lle99940 gt 3D 11 GE 1 461 5D 09 9515225974 610D 00 ER 000000000000D 00 21 0000000000D 02 S00000000000D F01 122400000000D 05 000000000000D 00 TZODO 00D OU EEN S00000000000D 01 A08600000000D 0S 000000000000D 00 400000000000D 01 200000 000000D 01 108900000000D 05 000000000000D 00 220000000000D 02 S00000000000D F01 O o o Ch Ch CO ooo ooo CH CH CH 108000000000D 05 103 2 0 53 q O a O a o lt a ee RINEX Version 2 20 Modifications to Accommodate Low Earth Orbiter Data KOK K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K FK K ole K FK 2K ole fe oe ok Werner Gurtner lt gurtner aiub unibe ch gt Lou Estey lt lou unavco ucar edu gt April 12 2001 Summary In order to accommodate GPS data from LEO satellites some moderate modifications of the RINEX Version 2 10 format are pro posed New header records for marker vehicle characterization antenna position and orientation increased precision of the phase observations Two new observation types 122 LA for L1 phase derived from C A code tracking SA for SNR of L1 phase derived from C A code
72. 8 4 1 provides an example of the Automatic Playback feature as 1t 1s used in conjunction with the Post Session Com mand feature Please review this section carefully if you wish to use this feature 76 FILE NAMING APPROACH Almost every Ashtech file 1s named based upon some value of GPS time Because GBSS opens many files before connecting to the receiver it needs a good approximation of the current GPS time that is it cannot ask the GPS receiver for the current GPS time For this reason the Configure GPS Time menu is provided see Section 3 1 7 to allow GBSS to generate a corrected CPU GPS time Using the corrected CPU GPS time GBSS can generate the names of data files GBSS will create the file names based upon this corrected CPU GPS time of the computer not the receiver provided time but files are closed based upon the time stored within the GPS data received from the receiver The File Duration parameter of the Configuration File Outputs Menu see Section 3 1 4 10 specifies the duration in hours of the files during the logging A value of 1 disables the File Duration option When output files reach their duration they are closed and files corresponding to the next session are automatically opened Each time the output files reach their duration based upon the GPS time embedded in the data received from the receiver they are closed and the files for the next session are opened Please see Section 3 1 5 for a distin
73. 94 East Longitude 252 7849427168 282 far 5 793761 West Longitude 77 2150572832 ez hz 54 206219 Ellipsoid Height bam ECEF X ECEF Y ECEF E 096351 4093 Lan 45 5222 1003607 4647 Figure E 7 RINEX Site Position Window The RINEX Site Position Window allows you to specify the position of the receiver to be output as part of the RINEX header data The RINEX specification indicates that this position need only be approximate and provides no specifics on the required accuracy of the approximation The position written as part of the header data can come from a manually entered position or from a weighted average of the position and PDOP data of the B File To specify that the approximate position 1s to come from the weighted average of the B File position data check the Get Position form B File Data checkbox Otherwise uncheck the box and enter the approximate position in the window Like the RINEX Header Data Edit Window the data entered into this window will be saved as part of the configuration informa tion for the program If the Get Position form B File Data checkbox is checked then XYZAshRx will obtain the approximate position from B File on the current and later runs E 3 1 2 RINEX Meteorological Files Before continuing it must be noted that the meteorological option of the RINEX converter is not available unless the presence of a software sentinel key coded for the GBSS Meteorological module ca
74. A AND HEREBY EXPRESSLY DISCLAIM ANY WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND NONFRINGEMENT LICENSOR AND ITS THIRD PARTY SUPPLIERS DO NOT WARRANT THE PRO GRAM WILL MEET YOUR REQUIREMENTS OR THAT ITS OPERATION WILL BE UNINTERRUPTED OR ERROR FREE LICENSOR its third party suppliers or anyone involved in the creation or delivery of the Program or Documentation to you shall have no liability to you or any third party for special incidental indirect or consequential damages including but not lim ited to loss of profits or savings downtime damage to or replacement of equipment or property or recovery or replacement of programs or data arising from claims based in warranty contract tort including negligence strict liability or otherwise even if LICENSOR or its third party suppliers have been advised of the possibility of such claim or damages The liability of LICEN SOR and its third party suppliers for direct damages shall not exceed the actual amount paid for this Program License Some states do not allow the exclusion of limitation of implied warranties or liability for incidental or consequential damages so some of the above limitations or exclusions may not apply to you U S GOVERNMENT RESTRICTED RIGHTS The Program and Documentation are provided with RESTRICTIVE RIGHTS Use duplication or disclosure by the Govern ment is subject to restrictions as set forth in subdivision c 1 11 of the Rights in
75. ANYING ITEMS TO THE PLACE WHERE YOU OBTAINED THEM FOR A FULL REFUND LICENSE LICENSOR grants to you a limited non exclusive non transferable personal license License to 1 install and operate the copy of the computer program contained in this package Program in machine acceptable form only on a single computer one central processing unit and associated monitor and keyboard and 11 make one archival copy of the Program for use with the same computer LICENSOR and its third party suppliers retain all rights to the Program not expressly granted in this Agreement OWNERSHIP OF PROGRAMS AND COPIES This License is not a sale of the original Program or any copies LICENSOR and its third party suppliers retain the ownership of the Program and all copyrights and other proprietary rights therein and all subsequent copies of the Program made by you regardless of the form in which the copies may exist The Program and the accompanying manuals Documentation are copyrighted works of authorship and contain valuable trade secret and confiden tial information proprietary to LICENSOR and its third party suppliers You agree to exercise reasonable efforts to protect the proprietary interests of LICENSOR and its third party suppliers in the Program and Documentation and maintain them in strict confidence USER RESTRICTIONS The Program is provided for use in your internal commercial business operations and must remain at all times upon a s
76. ASS B File BREMDA98 093 Also creates the GPS Only E File EREMDAv8 093 from the source GPS GLONASS E File EREMDA98 093 The input and output directories are the current working directory 87 88 UTILITY PROGRAM XYZAshRx E 1 INTRODUCTION TO XYZAshRX XYZAshRx EXE written by The XYZ s of GPS Inc was designed to convert Ashtech raw GPS observation files to the Receiver INdependent EXchange format RINEX The RINEX format is described completely in Appendix F The program has been designed to operate on a Windows 95 or NT platform To facilitate a wide variety of users XYZAshRx can be config ured and run through normal Windows Graphical User Interfaces GUI or launched directly from the command line That is a user can use the conversion program just like most other Windows programs or the converter program can be executed without need of human intervention from other programs such as the Ashtech Geodetic Base Station Software from a DOS command line or from batch files XY ZAshRx currently supports the Ashtech GPS and GPS GLONASS receivers Data are output in the RINEX Version 2 0 for mat The specification for this version of RINEX came from Dr Werner Gurtner s paper RINEX The Receiver Independent Exchange Format Version 2 Revised in July of 1998 reproduced in Appendix F E 1 1 Minimum System Requirements XY ZAshRx requires the target platform to be a Windows 95 or Windows NT based computer While XYZAshRx r
77. Administrator account If you attempt to install GBSS under an account that does not have full administrative rights GBSS will not install and run properly This is because the GBSS installer needs to add device drivers for 1ts sentinel key During the installation of GBSS the following major components will be installed e GBSS Program files e Sentinel Drivers e GBSS Sound Files e Stand alone RINEX converter e Stand alone FTP program creates directories on remote computers e Stand alone GPS GLONASS gt GPS conversion program The program files include the executable program its configuration file and a simulation test file The sentinel drivers are required to allow GBSS to communicate with its sentinel key without these drivers GBSS may not run This sentinel key comes standard with your copy of Geodetic Base Station The sentinel key allows GBSS and its support utilities to run on a sin gle workstation Please note that multiple copies of GBSS can be run on a single workstation with a single sentinel keys The GBSS sound files are a set of WAV files that GBSS can be configured to play when certain events occur see Section 3 1 6 3 You select which sound files to play during the configuration of GBSS The stand alone support utilities are all 32 bit in nature and are command line driven These support programs provide powerful system integration tools to the base station operator and facilitate many specialized applications The st
78. Answering no to any of these questions does not prohibit you from later manually activating or deactivating the features Like wise answering yes to any of these questions will not prohibit you from manually deactivating the features Manually activating and deactivating these features can be accomplished through standard Windows configuration parameters such as creating short cuts If you decide to add GBSS to the Windows Start Program menu then you will be able to quickly launch GBSS using the Win dows Start button If you decide to add a shortcut to GBSS to your Windows desktop then you will be able to quickly launch GBSS by double clicking the its icon on you Windows desktop If you choose for GBSS to be automatically started with Windows then each and every time you start Windows GBSS will be launched and will attempt to automatically connect to a GPS receiver Please note that this feature should only be enabled for users who wish GBSS to connect without human intervention such as permanent reference station sites Unless you have some alternative power supply your computer will shut down whenever there is a power failure When the Auto Connect feature is enabled your computer will automatically start Windows which in turn will then automatically start GBSS which will then re connect to the GPS receiver This feature provides the base station operator with the assurance that the continuous reference sta tion will weather power
79. BSS to call the second copy of GBSS at the completion of the session via the following Post Session Command D SCNDGBSS GBSS exe P GPW GPS TFP Obviously the working directory of this command should be D SCNDGBSS This will have the primary copy of GBSS that is the one in the C Program Files Ashtech directory call the second copy of GBSS that is the one in the DASCNDGBSS direc tory which will use its own independent configuration that is stored in the file D SCNDGBSS GBSS INI Two independent copies of GBSS will be running simultaneously one copy will be communicating with a receiver and one will be in playback mode You might ask why would you want GBSS to call a copy of itself Suppose that your objective was to create 30 second epoch data and 1 second epoch data files from the same receiver and you wanted to store that data into different directories To do this you would have the primary copy of GBSS communicate directly with the GPS receiver requesting it to output 1 second data Further this copy should be set to output a Trap File The second copy should then be configured to output the data to a different directory via the Configuration Output Files menu and have its epoch filtering set to 30 seconds see Section 3 1 4 12 Finally you should have the primary copy of GBSS configured to call the second copy of GBSS via Post Session Commands as shown in the example of this Section 3 1 8 4 2 Directory Creation on a
80. BSS 1s said to be disabled When disabled GBSS will collect and record all data received When the Session Pro 34 gramming feature is enabled the periods describe by each logging session indicate when data will actually be written to files It is important to note that enabled logging sessions do affect the contents of the Trap Files see Section 3 1 4 5 That is when enabled ogging sessions are encountered only data that falls within the logging session periods will be written to the Trap Files that is the data in the Trap Files will correspond with the associated data stored in the other output files There are three categories of logging sessions 1 Daily 2 Weekly and 3 Special Each of these categories is defined by a start time and duration Upon reaching the start time of a logging session GBSS will begin to write the data and will stop writing data upon reaching the duration or end time Daily logging sessions are defined by a start time of day and duration Weekly logging sessions are defined by a start day of week time of day and duration With Daily Weekly logging sessions you are permitted to have the start lie within one day week and end in the next day week Daily Weekly logging sessions are recurring in that they will repeat each day week The special logging session is defined by a start year month day time of day and duration These special logging sessions are nonrecurring that 1s they will occur on
81. CTOR header records and the LA and CH observables should be used by non space applications We also like to get comments about the proposed MARKER TYPE classes Depending on the results of the poll the modifications will be restricted to MARKER TYPE SPACEBORNE or opened to all classes 126 Example Seeerei TESTRINEX TEST DATE EXAMPLE OF LEO EILE CHAMP 00039B SPACEBORNE GFZ Main Blackja POD Antenna unknown 1 4880 00 00 0 0000 0 000 TOS 000 d E O J LA L2 GL 1 2 LA LL 2000 8 d 0 UU 8 7 0 0 0 0000000 AOS Al 4183922 25509 354 6 10 SS EE C517 E 0 T429 LIDO SAO ATSS TOA TOS 3688647 4133104 186 199 14033524 436 10935414 14033524 414 SU ALLA ZA DO OLA ADA 8 39 9550410 4 LE 74466001 E EEN Ton 1348503435 POS OO U s 13485052456 90 DO 7 0 O20 0000000 mod oo sa TLS A ZOUZ 7 Os OBSERVATION DATA ck O O al L2 404 000 Do 000 LLO 000 ZN 000 610 000 916 000 864 000 egito RINEX VERSION TYPE 07 AUG 00 00 44 01 PGM RUN BY DATE COMMENT MARKER NAME MARKER NUMBER MARKER TYPE OBSERVER AGENCY RA O RS REC TYPE VERS ANT TYPE 0 3928 ANTENNA DELTA X Y Z 1 0000 ANTENNA B SIGHT XYZ INTERVAL WAVELENGTH FACT L1 2 P2 al SA S1 S2 TYPES OF OBSERV OBS SCALE FACTOR 0 0000000 TIME OF FIRST OBS END OF HEADER Arado E 49 LO dd dl ZLIATOLIL 462 LULA 0 le Bales oe 21470114 496 LO TER 148 000 22348706 474 22348706 684 22348709 446 DS OO e e DO
82. E April 1997 Redefinition of sv clock params in GLONASS Nav Mess Files March 1998 Naming conventions for compressed RINEX obs files March 1998 GPS week No roll over continuous number March 1998 Error in compressed DOS file naming convention July 1998 Table A13 contained blank satellite identifiers Sept 1998 Discrepancy between Tables AS and A9 removed Sept 1998 103 INTRODUCTION First Revision This paper 1s a revised version of the one published by W Gurtner and G Mader in the CSTG GPS Bulletin of September Octo ber 1990 The main reason for a revision is the new treatment of anti spoofing data by the RINEX format see chapter 7 Chap ter 4 gives a recommendation for data compression procedures especially useful when large amounts of data are exchanged through computer networks In Table A3 in the original paper the definition of the PGM RUN BY DATE navigation header record was missing although the example showed it The redefinition of AODE AODC to IODE IODC also asks for an update of the format description For consistency reasons we also defined a Version 2 format for the Meteorological Data files inclu sion of a END OF HEADER record and an optional MARKER NUMBER record The slight modification or rather the definition of a bit in the Loss of Lock Indicator unused so far to flag AS data is so small a change that we decided to NOT increase the version number Later Revisions URA Clarif
83. E MARKER NUMBER ANTENNA DELTA H E N A 9080 9080 1 34 USO LS THE START OF A NEW SITE lt COMMENT 0000000 O 4G610G12G 66 9 Pa o Ml O 19102 nos 2200024 254 2093 17 e264 92 ones ER 72141 846 6 7 7 e VO DOVO 0 36 SLOSS I O 1 E SEL ZA Lo ke 00 E 384 LIDO LADO 2002 IS SS 2039643393093 Sur o Ze Ls Lo d 41259453099 E TOR LO 23578244 398 ZUGZI2Z2Z5 2199 20864545 945 LAO TO 4 AN EVENT FLAG WITH COMMENT 3 24 13 14 12 0000000 0 SES 20 Jo MINO YA A O FALLO LOs L0 7 3335 020 2093 6 ZL PA Mec oh d 4 SIGNIFICANT EPOCH 4G16G12G 9G 6 E Os p264 SE MOIS LOL LAO a ET IAG Te OSL 90 Se boa 56012 Z 11249692 133 LIO TL IDA 20828010 354 206509444902 E TL LOA LIA LOS L AVEZOOL TZ 20000390 SOS kkK ANTISPOOFING ON G 16 AND LOST LOCK COMMENT 90 90 21128904 ZA OSA 20817844 ZUOD SOL Na ae IES A A dis E De e 045 WER 995 kk SATELLITE G 9 EN Ea LOST LOCK 12 0000000 6 26106 9 LLANO OO TO OIADA O ENER SE 4 2 CYCLE SLIPS THAT HAVE BEEN APPLIED TO THE OBSERVATIONS 48 0000000 O 4G16G12G 9G 6 LOLAS LAA Y DO OLD O EN AS AN SA EI AS MS SIVA 22920 LOTTO OO LL 20690 7 20254 4 4 THIS EPOCH ON WLFACT 1 AND THIS EPOCH ON WLFACT 2 OPPOSITE TO PREVIOUS SETTINGS 2061 7891 L2 L2 Z1128600 23487146 Sas LUGOSI Ox COMMENT COMMENT 7764 1459 869 COMMENT COMMENT COMMENT UL MOS O A o Beete Eeer 1
84. El o2 OO 438 000 207 000 Save SSO sae 21055 8 0 jes 0s s 5102 010 a Rd 128 INDEX Symbols DCTP EE 102 EM EE 102 SPASHR ION anida 28 A er Re in 54 A II A 54 IN OS cosas a a 90 A administrative privileges cccceeeeeeees 5 Ae Ol IMCS uai ola dna uE A 24 antenna height 00as00000000000000eeo 17 18 20 Applied Geomechanics seeseeeeseseseeeeeeeeee 7 archiving of data cooooconncnncnananannanananananrrrnnn noo l A a Sa a 11 83 PASI PMD E 49 85 ASHFTPMD EXE 5 49 55 Ashtech Tormat E l Ashtech naming convention 34 ASSUMIPMOMS ala 54 automated data distribution 2 automated FTP transfers cc eeeeeeeeeeees l automatic file deletion ooooonnnnnnnnnncnonaaann noo 2 auxiliar SENSOLS ansiada dias 31 B backup Copy iaa 11 BAT CxtemsiOn aaa 48 EE GE 48 Nee 18 19 BOOT INE tati 8 C C CMAN OS ansaa dead 100 calls to external programs 42 cancel post session commands 46 capture NMEA messages oooocccccccncncnnnnnnno 31 COREMOTE AXE Ae 51 change configuration ooccnnnnnnnnnnnninininininos 12 channel and navigation version 18 channel software version cccceeeeeeeeee 18 Sea TR Renee RD ENE OE 59 compressed ES eege l compressed message format 17 compression files sumsansicanieniiniiniassisasdacaesnis 20 CONCERNE
85. GREMOTE to dial the remote receiver download receiver image files and create the batch file needed to decompress the image files Step 2 We call the batch file created under step 1 to decompress the receiver image files downloaded under step 1 The decom pressed files will be the normal Ashtech processing data files for example B E and S Files Notice that we have included the BAT extension when calling the batch routine This is required by the operating system and should be included with any post session command call to a batch file Step 3 We call the batch command file DELETE BAT to delete the downloaded receiver image file as it is no longer needed Notice that in the post session command that we again include the BAT extent of the batch file The contents of the called batch file are as follows REM FILE DELETE BAT cdi cd remote del revb2 This is a particularly noteworthy batch file in that it contains an MS DOS intrinsic command see Section 3 1 8 3 Intrinsic MS DOS commands cannot be directly called from a GBSS post session command Windows permits GBSS however to launch a batch file that contains these intrinsic commands This is why we did not call the del command directly from the post session command Step 4 GBSS calls the batch command file MOVE1 BAT to move the data files created under step 1 The contents of the batch file are as follows REM FILE MOVE1 BAT REM 1 TARGE
86. H MM SS format For Weekly and Special types the duration is expressed in days hours minutes and seconds that is in the DD HH MM SS format The duration for Weekly ogging sessions are limited to 24 hours Weekly ogging sessions are limited to seven days and Special logging sessions are limited to 35 days The following describes the functionality of each button of this window Ge A changes made to the logging sessions including any imported logging sessions le the editing of a highlighted logging session Simply use the mouse cursor to select the log ging session to be edited and then press this button You can also begin editing a logging session by double clicking on the desired entry The actual editing takes place using the Logging Session Editor window described in Section 3 1 5 1 Copy W nie the highlighted logging session to the end of the set of logging sessions and begins editing that logging session by launching the Logging Session Editor window described in Section 3 1 5 1 Up to 50 logging sessions are supported by GBSS H Mew ates a new logging session at the end of the list of Jogging sessions After creating the new log ging session you immediately begin editing the new command using the Logging Session Editor window described in Section 3 1 5 1 Up to 50 logging sessions are supported by GBSS Delete l i Delete E the highlighted logging session 36 Import ii Upon pressing this
87. INEX file could be created at a 1 second interval a 20 second interval and a 30 second interval with no interpolation of data points This feature allows the base station operator to post data from the same time period at different epoch intervals The Post Session Command feature allows you to create even more file types than those listed above Any third party command line driven program can be called by GBSS This feature allows you to call such a program to automatically do work on one of the above files This results in entirely new data formats not directly supported by GBSS Many file management tools have been built into GBSS and these tools provide sophisticated control over the collected data GBSS comes with four user selectable directory structures For example dual frequency RINEX data can be stored in the Pri mary directory structure and single frequency RINEX data can be stored in the Secondary structure These file management tools thus allow the GBSS operator to provide different users with different file types GBSS allows you to set the File Duration file length to a value between 3 minutes and 84 hours Each copy of GBSS also comes with a user selectable automatic file deletion feature This feature automatically deletes any file older then the user spec ified age For example if the File Deletion Age is set to 30 days any file created by GBSS older then 30 days will automatically be deleted GBSS also allows you to effectiv
88. L1 Only B E and S Files to RINEX e Output Ashtech Ionospheric Model File e Trap communication data to file The left most checkbox of each is labeled with a heading of Primary and the right most checkbox is labeled with Secondary When a check is placed into the Primary column GBSS will output that file to the Primary Output Path When a check is placed in the Secondary column GBSS will output that file to the Secondary Output Path Please note that no file can be simultaneously output to the primary and secondary directory GBSS protects the user from setting this illegal combination The format of the B E and S Files will depend entirely upon the connected Ashtech receiver Please see the Ashtech GPS receiver manual for the structure of your B E and S files For example see the Ashtech Continuous Geodetic Reference Station CGRS manual for information on the dual frequency data files or see the Ashtech Super CA manual for information on the sin gle frequency data files Please note that if your GPS receiver is of dual frequency type then files output when one of the Out put Ashtech Formatted B E and S Files checkboxes is checked then the output B E and S files will be dual frequency Likewise when connected to a single frequency receiver then a check in the same checkboxes will cause GBSS to output L1 only B E and S files GBSS can create the L1 Only versions of the B E and S Files when connected to a dua
89. SION TYPE GPS E GLONASS LT TRANSITI M MIXED COMMENT ATUB ZO ABRES T2443 PGM RUN BY DATE MARKER NAME MARKER NUMBER ABC INSTITUTE OBSERVER AGENCY XX REC TYPE VERS YY ANT TYPE 587466 4589095 APPROX POSITION XYZ 0000 0000 ANTENNA DELTA H E N WAVELENGTH FACT L1 2 6 G14 G15 G16 G17 WAVELENGTH FACT 11 2 El 152 P2 TYPES OF OBSERV INTERVAL 24 Le 10 36 000000 TIME OF FIRST OBS END OF HEADER 90 324 Lo 101 S6 0000000 0 36126 96 06 ELA 56769 LOLA 20891534 2060 7 600 GE 648 183 3008 2550 ZIO2ZIS04 EM ESLa g Y DO 206 LIA LL 292 PO OR 994 20607605 646 4 90 35 28 13 10 50 0000000 4 E 2 ZOOL IOI Du 202360755 ZOO LAOS Z 21345678 LLEVADO OO Be ZA LS dA 450 667 689 SELO Loo G 9 G12 WAVELENGTH FACT 11 2 WAVELENGTH FACTOR CHANGED FOR 2 SATELLITES COMMENT NOW 8 SATELLITES HAVE WL FACT 1 AND 2 COMMENT COMMENT OO e 24 O LO SE 000000 IGLZG SG ORAZ TRA SE de Sh SO Oy 1 Ons SAL OL goo ZS OL O MLZ 006 SLZ0000 S22 5044550 20886092101 LOZA LAZU EO 20611078 410 12345 23456 0 0000000 117 Table F 9 Observation Data File Example continued kk COMMENT ASS 6109 FROM NOW ON KINEMATIC DATA 3 24 13 11 48 0000000 0 4G16612G 9G 6 ARO L6LI9 960 LADO Doo oo 2 15090 d SE SA oO SALDO po 800410920 UZ Lod DT Ro da 3 90 ZA MO Oe 23588424 20869878 20621643 ZA ODS 23588439 20869884 20621649 441 570 90 276 MARKER NAM
90. SS can then push any of its files to these directories on the remote computer The end result is that it appears that the remote FTP site is directly connected to a GPS station even though it is not Data files created by GBSS can also be made passively available to other users via Windows NT Server GBSS has been specif ically designed to work in concert with the FTP and Web page utilities that come standard with NT Server Windows NT allows the user to provide the right subset of GPS data to the right group of users For example the system administrator may wish to grant access to the single frequency data but restrict access to the dual frequency data This is accomplished by setting up differ ent access levels for different users For example dual frequency RINEX data can be placed in the Primary directory structure and single frequency RINEX data can be placed in the Secondary directory structure Windows NT Server then allows you to define different permissions to these different directory structures For example the single frequency data could be made avail able via anonymous FTP whereas the dual frequency could be made available via restricted logon Users can then access this data through an FTP connection or through a Web page interface Because of the multi tasking and multi threading nature of Windows NT Server Version 4 0 multiple users may access the data simultaneously Windows NT Server can be easily setup with the NTES file structu
91. Session Information Session Start Time Day Hr Min Wednesday nr lo Session Duration Days Hr Min o 5 lo Session End Time Day Hr Min Wednesday 22 lo qt Ashiech Figure 3 17 Edit Session Window 2 Edit Session Session Scheduling Session Type Special bd kd Session Enabled Special Session Information Session Start Time Year Month Day Hr Min i 999 E hr nz f GPS Week Seconds of Week p 001 320700 Session Duration Days 7 Hr Min h H i lo Session End Time Year Month Day Hr Min ji 999 E 27 E 5 GPS Week Seconds of Week A 002 583500 PA Ashiech Figure 3 18 Edit Session Window 3 If the desired logging session type is not shown when you begin editing simply change its type using the drop down list box labeled Session Type For each type you enable disable the logging session using the checkbox labeled Session Enabled It should be clear that the logging session is enabled when the Session Enabled checkbox is checked and disabled otherwise 38 Also for each type you defined the start time and the duration these components of the logging session are described in Section 3 15 Upon completing the editing simply press the OK button If you want to abort any changes simply press the Cancel button 3 1 6 Other Setup Options The Other Configuration Options window Figure 3 19 allows the operator to set the follow
92. T DIRECTORY move CVB2 1 This is another particularly noteworthy batch file in that it also contains an MS DOS intrinsic command see Section 3 1 8 3 Intrinsic MS DOS commands cannot be directly called from a GBSS post session command Windows permits GBSS however to launch a batch file that contains these intrinsic commands Also to be noted is the use of argument passing into a batch file that is the use of the 1 For explanations of this parameter passing mechanism please consult other references on MS DOS batch programming Step 5 GBSS calls the program XYZAshRx EXE to convert the Ashtech formatted files of step 4 to RINEX In this post ses sion command we use the GBSS mnemonics listed in Table 3 5 52 Table 3 5 GBSS Mnemonics Mnemonic Description FPDD The drive and directory of the current GBSS Primary Data Output Path S The session code of the files to be converted to RINEX YY The 2 digit year of the files to be converted to RINEX DDD The 3 digit day of the year of the files to be converted to RINEX Through this post session command we construct the full name of the files needed to convert the B E and S Files to the RINEX Observation and Navigation data files It is important to note that through the mnemonics of the post session command feature you can create tailored directory and file names Step 6 GBSS calls another batch file to copy the RINEX files of
93. Technical Data and Computer Software clause at DFARS 252 227 7013 or subdivision 9 C 1 and 2 of the Commercial Computer Software Restricted Rights 48 CFR 52 227 19 as applicable Should you have any questions concerning the License Agreement or the Limited Warranties and Limitation of Liability please contact in writing Magellan Corporation 471 El Camino Real Santa Clara CA 95050 CONTENTS Chapter 1 INTRODUCTION TO GEODETIC BASE STATION SOFTWARE GBSS 1 O CUS a dd a a a EE a l lk isin System REQUIEM a 3 EE EIERE Egeter ee 3 L3 Demo Versions Of IBSN A Ra 4 Chapter 2 INSTALLATION INSTRUCTIONS cooccoccconcccocconcccnncconaconanonanonancnnnronanenarenarenanenzanonars 5 O E 5 A ia A 5 22 OBSS AA o ensued UUs teat lated alias tute 6 2 Ee 6 2 4 Imstallimo the Sent Key sida Ep AEN 7 2 5 Windows 95 Specific Installation Instructions ooooccnnnnnnnnnnnnonnccnnnnnnnonononococonnnnnnnnnnornccnnnnnnnnnnanono 7 2 6 Windows NT Specific Installation Instructions ccccnnncnnnnnoonnccnnnnnnnonononocccnnnnnnonnnonncccnnnnnnnnnnnnons 7 ZA Umpane GBS S eelere ee 9 Chapter 3 CONFIGURING THE GEODETIC BASE STATION SOFTWARE 11 0 EEGENEN a a a oe 11 Ll CORAL On MENUS aid Ad ti 11 3 1 1 Communications Communication Settings ooooooononnnnnnnnnonnnnnonnnnnnnnnnnnnnnonononnnnnnnnnnnnnnnnnnnnnnns 12 sl Contiouranon ENEE anni A DI e 13 1 12 ConHourati n Comms Speed ee ee 13 3 1 1 3 Configurati
94. VCR Wy De cria 18 re connect to receiver ooocccnnoccncniccnnnnocononoso 6 record received data ocooocccnnniccnnnicccnonoconon 36 recording interval edit 16 reference Stato tada 20 REG SL a aa 8 remote COMPU idos 2 remote FLE ai 55 remote SVS LEU ad 86 REMOTE EXE uai sora dia 51 re start after power failure 008 6 RID O ape e DAR CARD AD RR 18 UNOS dci 1 6 RINEX GREEN 5 RINEX header 19 A Sonda OA 26 SED EE 8 63 A ra tert 20 PRU toba 17 RIO EEN 17 RXASHSES BAT cnnoccccnnoccnnnicccnnniocicnnaninss 55 S A aap reomtese 100 save configuration files ccceeeeeeees 11 Ss A rer RU 7 9 11 87 Mn sussa A ad Sd 5 Sena LUTADOR tildado 6 SESSION code sn Sec aaa 25 54 102 SESSION codes cooocccnnnocononiccononocononicicnnancononoso 53 simulati n luisana ais 18 simulation mode 18 simulation test file occcnncccnnnoccnonocon 5 Sine Ee E ssa is Aenea l 131 Ste TES seat ia El d 20 SINES tae erio ES 17 19 SILG SPCCIIIC data ais 17 18 SINA Y MESSAGES it 41 socket connection to Internet 85 SOLmAre VELSION estancia 18 sound ICS a ci a 5 39 special installation instructions 6 speed of simulation ooocccccccnnnnnnnnnnnnnn s 75 Speed seleciona ccd des nina 13 GUAGE GAY iia 102 Stare 06 5 6 nda 6 Startup delay ett 9 sub directory creation cccceeeeeeeeeeeeeees 2 Support utilities 0 eee 5 6 11 system administrator
95. X Observation and Navigation files The 4 character station name is obtained from the Configuration Site Site Name menu see Section 3 1 3 1 The session code depends upon the File Duration parameter of the Configuration File Outputs menu see Section 3 1 4 10 and upon the corrected CPU GPS time The corrected CPU GPS time is also used to determine the year and day of the year Again GBSS avoids overwriting files with the same name and does not append to existing files with the exception of Log files This is particularly important for cases where GBSS is terminated indirectly such as for a power failure When GBSS is restarted after one of these indirect terminations it may generate output file names for files that are already on disk for example GBSS is terminated in the middle of a File Duration and is restarted within the same File Duration When this occurs GBSS attempts to rename the files already on disk It does this by appending a Z to the tail end of disk resident file name If there is already a file on disk with this Z at the end of the file name that is GBSS has already been through this re name process at least once GBSS will attempt the rename process using the letter Y This rename process will continue until either GBSS finds an available name or all letters of the alphabet are used in which case GBSS will start to overwrite older files with the same name Under Windows 95 GBSS alte
96. a Z 12 receiver Channel Summary satelite PRN ri l laf Jel f l licasm 242 wem am mi Mes 240 faa ar ass ass o Dodo L2PSH un agr 48 mm agg Po lo Elevation 68 32 so 58 a3 o Azimuth 28 ez 0 ml mm Haage 2 2 2 2 21 Figure 4 7 Channel Summary Window 1 The information in this window is displayed based upon channel numbers which are shown across the top of the window The row labeled Satellite PRN is used to show which satellite by its Pseudo Random Noise number is being tracked on each chan nel Obviously empty columns imply that no satellite is being tracked on that channel The rows labeled with L1 C A S N L1 P S N and L2 P S N display the signal to noise value reported by the receiver for that satellite on the L1 C A Code 69 tracking loop the L1 P Code tracking loop and the L2 P Code tracking loop respectively The Elevation row displays the ele vation degrees of the satellite being tracked The Azimuth row displays the azimuth degrees of the satellite The Nav Age column indicates how long ago in minutes that a navigation message for that satellite was received Figure 4 8 shows an example of this window when connected to an Ashtech Z 18 receiver Channel Summary Channel 2 3 4 5 G d 2 d 10 11 12 Satellite PRH EA MI E O ES O E casn a REG UNE a Lipsm 36 n a AA Lepsa 3 n a a 39 am Elevatio
97. a window that is capable of navigating over the entire set of directories of your computer Use that window to select the desired secondary output directory If the desired directory does not exist simply use the New Folder button in the upper right corner of the direc tory selection window to create it Once you have identified a Secondary Output Path then any data type that has the secondary field checked alongside it will be stored in that directory In the example of Section 3 1 4 3 the Secondary Output Path is E SEC_ DIR and the following files types have been selected for output to the secondary directory e LI only Ashtech Formatted B E and S Files e Trap communication data to file Please note that it is permissible to use the same directory for both the primary and secondary output directories 27 3 1 4 5 Configuration File Output File Output Selections The File Output Selections area of the Data Files screen is used to specify which data files will be created and whether they will be stored in the Primary or Secondary Output paths The File Output Selections is composed of two columns of checkboxes The left most column of checkboxes 1s for the Primary Output Path and the right most column of checkboxes is for the Second ary Output Path These items are labeled as follows e Output Ashtech Formatted B E and S Files e Output L1 Only Ashtech Formatted B E and S Files e Convert B E and S files to RINEX e Convert
98. able program should be quoted that is the quotation should not include the options unless the options of that program requires some quotation of parameters The meaning of the checkbox labeled as Start module whenever GBSS is that GBSS will launch the external module whenever GBSS itself is started Additionally when you leave this configuration screen and the Real Time Interface Configuration Screen and this checkbox is checked GBSS will immediately attempt to launch the external module Please note that whenever GBSS starts an external module 1t writes a message to its Diagnostic Message window indicating the success or failure to launch that module When having difficulty launching an external module you should consult the Diagnos tic Message window to determine why Again it is important to stress that the use of this external module interface start up mechanism be restricted to external programs that fully implement the GBSS interface The interface is defined such that GBSS is aware of any external modules that may be communicating over that interface Upon starting an external program GBSS awaits a response from that module through its interface indicating the successful start up of that module The lack of a response among other responses is deemed an errone ous condition Failure to comply with this warning could lead to erroneous behavior of GBSS and or any external programs called through this mechanism 3 2 Configuring GBSS
99. al definition asked for TauN GammaN TauC See paragraph 8 2 To avoid problems with files created with the original definitions a real valued version number 2 01 has been introduced for GLONASS nav mess files IGS decided to use the Hatanaka compression scheme for RINEX observation files Below the corresponding RINEX file name conventions are included as recommendations The DOS naming extension yyE was wrongly set to yyY in the March 1998 version of the document GPS week The GPS week number in all RINEX files is a continuous number not affected by the 1024 roll over it runs from 1023 over 1024 to 1025 etc A descrepancy between the definition of the header line fields of met sensor description and position in Table AS and the example in Table A9 was removed The latter was correct 104 The Philosophy Of Rinex The first proposal for the Receiver Independent Exchange Format RINEX has been developed by the Astronomical Institute of the University of Berne for the easy exchange of the GPS data to be collected during the large European GPS campaign EUREF 89 which involved more than 60 GPS receivers of 4 different manufacturers The governing aspect during the development was the following fact Most geodetic processing software for GPS data use a well defined set of observables the carrier phase measurement at one or both carriers actually being a measurement on the beat frequency between the received carrier of t
100. al for the phase and range measurements and is identical for all satellites observed at that epoch It 1s expressed in GPS time not Universal Time 105 PSEUDO RANGE The pseudo range PR is the distance from the receiver antenna to the satellite antenna including receiver and satellite clock off sets and other biases such as atmospheric delays PR distance c receiver clock offset satellite clock offset other biases so that the pseudo range reflects the actual behavior of the receiver and satellite clocks The pseudo range is stored in units of meters See also clarifications for pseudoranges in mixed GPS GLONASS files in Chapter 8 1 PHASE The phase is the carrier phase measured in whole cycles at both L1 and L2 The half cycles measured by sqaring type receivers must be converted to whole cycles and flagged by the wavelength factor in the header section The phase changes in the same sense as the range negative doppler The phase observations between epochs must be connected by including the integer number of cycles The phase observations will not contain any systematic drifts from intentional offsets of the reference oscillators The observables are not corrected for external effects like atmospheric refraction satellite clock offsets etc If the receiver or the converter software adjusts the measurements using the real time derived receiver clock offsets dT r the consistency of the 3 quantities phase pseud
101. and alone RINEX con verter can be used as a command line driven program or as a standard Windows menu program For example the RINEX pro gram can be called from the GBSS Post Session Command feature for special RINEX applications not supported by the built in RINEX converter in GBSS Alternately the RINEX converter can be used to manually RINEX data through a simple Windows interface The stand alone FTP program is used when it is necessary to automatically create any of the four GBSS directory structures on a remote FTP server or really any directory structure on a remote FTP server This FTP program is called ASHFTPMD EXE and was developed to work in tandem with WS FTP Pro not supplied with GBSS ASHFTPMD EXE is called from the Post Ses sion Command feature and can automatically create the four GBSS directory structures on any remote FTP computers Further more ASHFTPMD EXE can be used to automatically create many different directory structures For example ASHFTPMD EXE could be used to automatically create a directory structure on the remote computer based upon site name year and month rather than year and month alone ASHFTPMD EXE supports these specialized applications For additional infor mation please see Appendix C The stand alone GPS GLONASS gt GPS program allows you to take GPS GLONASS data files and convert them to GPS only data files This program is called GNSS2GPS EXE and is command line driven There is no graphical Wi
102. ar and ddd is the day of the year See the Appendices for complete details on file naming The third and final purpose of the entered site name is that it will always be output as part of the RINEX header 19 3 1 3 2 Configuration Site Antenna Height The Antenna Height edit field allows the entry of the vertical antenna height offset from the mark that is the HI This param eter may be used for three purposes The first purpose depends on whether or not GBSS 1s configured to output Site files see Section 3 1 4 5 That is if GBSS is configured to create Site files the antenna height value entered on the site menu will be placed into the vertical antenna height field of the Ashtech Site file Secondly the antenna height parameter will be sent to the receiver if the Upload site data to receiver checkbox of the Config uration GPS Receiver menu see Section 3 1 2 5 is checked This antenna height information will be sent to the receiver each time GBSS is connected to the receiver see Sections 3 2 4 1 4 6 and 4 7 The third and final purpose of the entered antenna height is that it will always be output as part of the RINEX header see Section 3 1 4 5 3 1 3 3 Configuration Site Site Position The WGS 84 position of the reference station can be entered through the position related entry fields on the Site Configuration menu When entering positional data the other components will automatically be up
103. ary As the output format for the receiver derived clock offset is limited to nanoseconds the offset should be rounded to the nearest nano second before it is used to correct the observables in order to guarantee correct reconstruction ADDITIONAL HINTS AND TIPS Programs developed to read RINEX Version 1 files have to verify the version number Version 2 files may look different version number END OF HEADER record receiver and antenna serial number alphanumeric even if they do not use any of the new features We propose that routines to read RINEX Version 2 files automatically delete leading blanks in any CHARACTER input field Routines creating RINEX Version 2 files should also left justify all variables in the CHARACTER fields OS and other files may have variable record lengths so we recommend to first read each observation record into a 80 character blank string and decode the data afterwards In variable length records empty data fields at the end of a record may be missing especially in the case of the optional receiver clock offset RINEX UNDER ANTISPOOFING AS Some receivers generate code delay differences between the first and second frequency using cross correlation techniques when AS is on and may recover the phase observations on L2 in full cycles Using the C A code delay on L1 and the observed differ ence it is possible to generate a code delay observation for the second frequency Other receivers recover P code observat
104. ary Window 4 3 7 Time Display Window Figure 4 13 shows an example of the Time Display window us Time Display CPU Time Raw May 13 1993 14 22 33 Wk 957 Sec 310953 Corrected GPS May 13 1998 18 24 22 Wk 957 Sec 325462 Local May 13 1993 142422 Wk 957 Sec 311062 Set Zone Local Time Zone Figure 4 13 Time Display Window In order to understand this window you need to be familiar with the concept of the corrected CPU GPS time which is described in Section 3 1 7 All of the times displayed in this window are related to the CPU time that 1s not epoch time The time displayed with the Raw label is the raw that is unmodified time from your computer s clock The time displayed with the GPS label is the corrected CPU GPS time The time displayed as Local is the corrected CPU GPS time plus the value of the Local Time Zone You are free to change the value of the local time zone but those changes do not take effect until the Set Zone button 1s pushed It is important to note that the update of this window is considered to be of low priority As a result when receiving data from a receiver configured to output epoch data frequently say an epoch interval of 2 seconds or less and depending on the speed of your computer the update of this display may appear sporadic 4 4 Terminal Window The Geodetic Base Station Software 1s equipped with a terminal window that allows you to send co
105. at is not Play Back Mode enter an approximate time press OK and note the time of the first epoch retrieved from the file You may need to wait until receiving both an epoch and a navigation message to determine the GPS week of the data but you should used the time associated with the first epoch received Then you can terminate the simulation re run in either the Simulation or the Play Modes and enter the cor rect start time of the file The Play Back and Simulation modes only differ in the speed at which the file is played back trough GBSS In the Simulation Mode you are provided with slide bar which controls the speed of the simulation The slide bar Figure 4 16 is found in the tool bar which 1s just below the program menu bar and is used to control the speed of the simulation The Play Back mode provides 75 no user control of the speed at which the file is played back through GBSS a eens LESS oe cece Wi PTE Eed A O el E VAR S ee E Ge A lisa es isuri E H Za Simulation Speed EI Figure 4 16 Simulation Speed Slide Bar GBSS is capable of re playing Ashtech receiver output data trapped by other programs such as ProComm or SmartComm In these cases you MUST specify the type of receiver that the file was created from in the Configuration Receiver menu see Section 3 1 2 7 Failure to do so could result in incorrectly interpreted data To specify the correct receiver type you may need to place GBSS into the Pas
106. ation versions This document applies to both con figurations Demonstration versions which are freely distributed over the Internet or provided on diskette have a greatly reduced capability when compared with a fully operational version Demonstration versions will only allow a 30 second epoch interval log a maximum of 100 epochs and will not perform file compression Most importantly demonstration versions do not allow Post Session Commands to be executed nor is the passive mode permitted see Section 3 1 2 1 To learn more about the Post Session Command feature please contact Thales Navigation for more details Please note that the installation instructions documented herein apply to both configurations You can obtain a demonstration version from the Thales Navigation web page at the following address http www ashtech com INSTALLATION INSTRUCTIONS 2 0 Overview For most users of GBSS the installation is very straightforward The installation diskettes use an industry recognized installer program If for any reason you decide to remove GBSS such as to install an upgrade to GBSS it can be removed and all of its support components using normal Windows 95 or Windows NT software uninstall mechanisms Please see the end of this sec tion for details on uninstalling GBSS Please note that when installing GBSS on a Windows NT machine it is necessary to install GBSS under an account that has full administrative privileges such as the
107. basic checks of the commands Post Session Command Line Editor Command Line E FTPWS_FTP exe T BFP R GBSS_HOST Command Working Directory EF TP 4 Enable Command hd Wait for this command to complete before issuing the next command Mnemonic Description FEFPS B File Name includes path Warnings Warnings Hone Hext Warning Position Within Command Line er Reason for Warning tL OK Verify Cancel Figure 3 22 Post Session Command Line Edit Window 44 There are basically four parts of a command line command 1 the command line command text 2 the working directory of the command 3 the command enable disable indication and 4 the wait for complete indication When entering the text of the command you are free to use the GBSS command line mnemonics The valid mnemonics are listed in the scroll box of the window Mnemonics are placeholders for actual values that can only be definitively determined at the completion of a session For example the B File mnemonic inclusive of the directory in which the file is stored is SBFPS When the post session command is entered the placeholder for the B File name and directory is entered as BFP Just before the command is executed at the end of a session GBSS substitutes the mnemonic with the actual name of the B File including the directory in which it is stored The working directory is the directory you want passed to Wind
108. be a Windows 95 or Windows NT based computer While GBSS requires less than 5 mega bytes of memory to run Windows 95 and NT impose higher minimums It is recommended for performance reasons that your computer has no less than 16 megabytes of RAM memory for Windows 95 and no less than 24 megabytes of RAM memory for Windows NT Thales Navigation strongly recommends a Windows NT platform Your disk space requirements will vary depending upon your unique configuration of GBSS GBSS actually requires less than 10 megabytes of disk space to store the program and its ancillary files but it is recommended that your available disk space be much larger to accommodate your data storage needs Because GBSS can create so many files simultaneously Thales Navigation rec ommends installing a large hard drive for users who need to create multiple files To optimize the performance of GBSS please give special consideration to the PC you choose to run the software It is important to choose a leading brand system to avoid cheap components such as serial cards often found in off name brands Although GBSS will run on most all Intel processors 486 and up it s performance will be maximized on a well built Pentium system spe cifically designed for NT 1 2 Special Requirements If you desire to use the file compression capabilities of GBSS you will need to have a valid copy of PKZIP 2 04g or PKZ IPC EXE from the PK ZIP 4 5 Suite for Windows installed on your c
109. ceiver this menu parameter 1s ignored That is the program can query the receiver and determine its channel and navigation software versions When this pro gram cannot send commands to an Ashtech receiver or when the program is in simulation mode and the simulation file does not contain the RID packet from the receiver the values of the Channel and Navigation edit fields will be used For Z XII receivers the navigation and channel software versions can be obtained by turning on your Ashtech receiver and selecting menu 0 zero The right side of the second line from the bottom contains a number of the form NNNN CCCC where NNNN is the navigation software version and CCCC is the channel software version 3 1 3 Site Site Settings The Site Configuration window Figure 3 6 allows you to enter the following site specific data 1 4 character site name 2 Antenna height and 3 WGS 84 position of the site 18 Site Configuration El ES Site Data Site Hame nana Antenna Height 0 000 Horth Latitude 38 4639826300 ps pr 50 337488 East Longitude 282 5609583500 pao bo 39 450060 West Longitude 77 4390416500 be ps 20 549940 Ellipsoid Height EXE ECEF A ECEF Y ECEF Z fi 057529 7291 Laag bh 90 3945963 7867 Figure 3 6 Site Configuration Window Please note that if you wish to send the information on this menu to the receiver for example to set the 4 character site name output with each
110. ch of which originates from a single copy of GBSS Presented above are the general forms of the interfacing mechanism Combinations of the above forms can be exploited to take full advantage of the data made available from GBSS through this interface However with the flexibility comes complexity This complexity is manifested into a requirement that might confuse the novice user We have sought to reduce that complexity to a few key configuration items The most notable of which is the requirement that users provide an interface name This name does nothing more than identify the interface to both GBSS and its associated external program s That is the interface identi fier which is simply an 8 character text string of your choice must be supplied to both GBSS through its external module con figuration and to all external programs using data from that single copy of GBSS Further each copy of GBSS must have its own interface identifier That is if two copies of GBSS are given the same interface name then one copy of GBSS will report an error and disallow any transactions over that interface 3 1 9 2 Configuration Description Through an Example As was stated earlier we will present the configuration approach through an example We will use the GBSS Met module which was designed to facilitate the collection and archival of meteorological data using GBSS a GPS receiver and a meteorological sensor Presented here will be the configuration fro
111. chronized with GPS clocks GBSS must open files before 1t connects to a receiver To open those files it needs to know how to name them Those names are supposed to be based upon the current GPS time As such GBSS needs the value of GPS time GBSS receives data from the receiver that contains the current GPS time GBSS is capable of determining the delta between the Raw CPU clock and the received data Then when GBSS needs the current GPS time it can apply this delta to the raw CPU time thereby generating this corrected CPU GPS time There are three ways of determining this delta and ultimately the corrected CPU GPS time 1 No delta at all GBSS is to treat the raw CPU time as GPS time 2 A manually entered delta 40 3 Let GBSS determine the delta between the time stamp of the data received and the raw CPU time The GPS time configuration menu allows one to specify one of these three methods This manual refers to this corrected CPU GPS time and is applicable under all three options that is under option 1 the delta is simply zero It is important to note that GBSS uses the corrected CPU GPS time for file naming purposes only and that files are closed based upon the time stamps within the actual data received from the GPS receiver Figure 3 20 provides a sample of the GPS Time Configuration window GPS Time Configuration EE User Corrected GPS Time Gregorian Y 1998 m fs D 13 H D M E 5 57 GPS Week asi Seconds of We
112. cified without the delay parameter GBSS by default waits 30 seconds It is permissible to specify wait periods less than 30 seconds It is recommended that you find the minimum C delay parameter that your computer can use and then set the value to 10 seconds above that value You can tell when you have fallen below the minimum That is upon boot up of your computer and the auto matic startup GBSS informs you that it cannot locate initialize the sentinel and the sentinel key is present or 1t cannot open the specified communication port and the specified port is a valid port on your computer There are some special automatic startup concerns for Windows NT machines These start up concerns are detailed in Section 2 6 Failure to address the special start up concerns may prevent GBSS from automatically starting with each start of Windows NT 62 RUNNING THE GEODETIC BASE STATION SOFTWARE 4 0 RUNNING GBSS OVERVIEW This chapter provides a description of GBSS once it has been configured Before actually running GBSS you will need to have installed the software sentinel key and then have configured GBSS Chapter 3 provides a description of the configuration pro cess 4 1 Connecting To and Disconnecting From the Receiver GBSS can be connected to a receiver through one of two primary means 1 Manually connecting to the receiver through the File Connect menu options or 2 Automatically connecting to the receiver as is described i
113. clear rationale as to why they should eliminate the CTS RTS hardware handshaking For example there are certain Ashtech receivers that do not employ the CTS RTS hardware handshaking In these cases GBSS needs to be made aware of the differ ence 3 1 1 4 Configuration Comms Use DTR DSR Hardware Handshaking The DTR DSR Hardware Handshaking checkbox allows you to specify whether or not the normal DTR DSR hardware flow con trol handshaking is enabled In most configurations this checkbox should be unchecked Those who check this checkbox should have a clear rationale as to why they should enable the DTR DSR hardware handshaking For example there are certain radio modems that implement the DTR DSR hardware handshaking In these cases GBSS will not communicate with the connected receiver unless the DTR DSR handshaking 1s enabled 3 1 2 GPS Receiver Receiver Settings The Receiver Configuration window Figure 3 3 allows you to do the following l Place GBSS is in Active or Passive mode 2 Command the receiver s recording interval and elevation mask 3 Command the receiver to use its compressed message format 13 ao ER E Command the receiver to disable storage of data to the receivers internal memory Upload the site data to the receiver Upload a script file to the receiver at connection time Enter information about the GPS receiver if GBSS 1s placed in Passive mode GPS Receiver Configuration po Ej Ad TE GEHORE TEQu
114. cnccccononinininininnns 41 TORA A et Reena ere ner ene 125 Ee 2 5 49 54 85 FU POS PRO EX E associada 50 55 EE POS PRO UE AE cutis 55 G GBSS EXT rota 11 GBSS Met Module eee 57 GBS Met module id 55 CBS S serial number tancia oca 6 GBSS will not install 2 0 eee 5 OBSS EXE ti 60 IB SOUND E 11 48 GBSS A hee e 11 48 GB SS MO EE 58 ES tee 46 GINS S ZOO PS addict 87 ONSSLOPS E EE 5 GPS UME pessoas fada aca ss USD 35 42 GPS onhy data les ta ias jason 5 A eebe 102 DIOSES ci 102 H handshaking oocccccccccnnncncnocicinoninines 13 65 Bee a T 85 reia ricos 7 11 incorrectly named files occnnnnnnnnnnnnn 41 e 2 interpolation of data points l ionospheric model 127 28 ionospheric model file o nnnnnnnnono 28 IPS witch MO PEN PRO N 2 L Is WEE 28 legal Characters ninia 19 locaton OL WHS tos 6 log FTP transactions 85 SMS ina ae 85 BOTS SESSIONS iii 2 l ng file NAMES iii 31 M MAC E 17 major COMPONENTS a ndo iai 5 making configuration changes 11 MESSA COS tas 63 MIES oia 6 130 MET d 6 meteorological data ocoocccncnnnnnnn 55 Meteorological Module 6 57 Microsoft home page cccccccccnnccncnnnnnicinininos 8 DOEMOS ti 46 MS DOS file names cccccccccnnnnnnnnnnnnnnnnnnns 19 MS DOS intrinsic command 52 multas KINO api ideo l multado aia l N NDN coa EOI
115. ct the command to be edited and then press this button You can also begin editing a command by double clicking on the desired command The actual editing of a command takes place using the Post Session Command Line Editor window described in Section 3 1 8 2 Copy PF ie the highlighted post session command to the end of the set of commands and begins editing that command by launching the Post Session Command Line Editor window described in Section 3 1 8 2 Up to 100 post session commands are supported by GBSS Hew Creates a new command at the end of the list of post session commands After creating the new command you imme diately begin editing the new command using the Post Session Command Line Editor window described in Section 3 1 8 2 Up to 100 post session commands are supported by GBSS Delete a l Deletes the highlighted post session command import impor pressing this button you will be presented with a file selection window in which you will enter and or browse for the name of the file containing post session commands to be imported import Upon pressing this button you will be presented with a file selection window in which you will enter and or browse for the name of the file in which to write the exported post session commands Cancel Cancels all changes to the post session commands The order of the commands can be changed through this window by selecting with the mouse the command to be
116. ction between the terms session and logging session Again the computation for file closure is based upon the Time of GPS week from the data received That is if the duration is one hour file closures will occur on the hour boundary that is the first set of files after a Connection to the receiver is estab lished may not contain one whole hour of data In each of the following sections the phrase corrected CPU GPS time is used to refer to the CPU time corrected to GPS time described in Section 3 1 7 Additionally GBSS avoids overwriting files with the same name and does not append to existing files with the exception of Log files This is particularly important for cases where GBSS is terminated indirectly such as for a power failure When GBSS 1s restarted after one of these indirect terminations it may generate output file names for files that are already on disk for example GBSS is terminated in the middle of a File Duration and 1s restarted within the same File Duration When this occurs GBSS attempts to rename the files already on disk It does this by appending a Z to the tail end of disk resident file name If there is already a file on disk with this Z at the end of the file name that is GBSS has already been through this re name pro cess at least once GBSS will attempt the rename process using the letter Y This rename process will continue until either GBSS finds an available name or all letters of t
117. d by Windows each time NT is started When Windows NT automatically starts GBSS it first attempts to connect with its software sentinel and assumes that the sentinel driver is fully ini tialized However because of the multi tasking nature of Windows NT those drivers may not initialize before GBSS actually tries to interface with them In other words in some instances GBSS will attempt to communicate with the sentinel drivers before Windows has a chance to fully initialize those drivers To prevent this race condition the command line call to GBSS in the Start Up folder can specify a delay that GBSS will exercise before attempting to communicate with the sentinel device Most Windows NT users will not need to change the automatic Start Up However if you experience sentinel related errors when GBSS automatically starts you may need to increase the automatic startup delay Section 3 2 on page 60 provides com plete details on setting this delay 2 Uninstalling GBSS GBSS and all of its components can be uninstalled via the Add Remove Programs feature of the Control Panel in Windows Please note that GBSS must be removed prior to installing a new version The Install Shield program that installs GBSS does not detect and remove old versions 10 CONFIGURING THE GEODETIC BASE STATION SOFTWARE 3 0 Configuration Overview Before actually running GBSS you will need to install the software sentinel key Please note that GBSS will not
118. d must correspond to the sequence of the mea surements in the data records If more than 9 types of observation types are being used use continuation lines with format 6X 9 4X A2 115 Table F 7 Meteorological Data File Header Section Description continued Header Label Columns 61 80 Description Sensor Mod Type Acc Description of the met sensor A20 A20 6X F7 1 4X Model manufacturer A2 1X Type Accuracy same units as obs values Observation type Record is repeated for each observation type found in Types of observ record Sensor pos XYZ H Approximate position of the met sensor 3F14 4 1F14 4 1X A2 Geocentric coordinates X Y Z ITRF or WGS 84 1X Ellipsoidal height H Observation type Set X Y Z to zero if not known Make sure H refers to ITRF or WGS 84 Record required for barometer recommended for other sensors End of header Last record in the header section 60X Table F 8 Meteorological Data File Data Record Description Epoch Met Epoch in GPS time not local time Year 2 digits month day hour min sec Met data in the same sequence as given in the header mF7 1 More than 8 met data types Use continuation lines 4X 10F7 1 3X 116 Table F 9 Observation Data File Example A A o o a kees 2 BLANK OR G XXRINEXO V9 9 EXAMPLE OF A MIXED RINEX FILE COMMENT A 9080 9080 1 34 BILGE METH X1234A123 234 SOL Tas 29030 1 i 4 KG 1990 dE 2 OBSERVATION DATA M MIXED RINEX VER
119. d not be used That is GBSS will not launch the commands of a given session 1f from the perspective of GBSS the commands from the previous session have not completed Furthermore users should ensure that their post session commands from the perspective of Windows complete before the subsequent File Duration period is over Failure to do so could cause GBSS to launch more processes than your computer can handle IT IS UP TO YOU THE USER TO MAKE SURE THAT THIS DOES NOT HAPPEN Programs that access the communications port to which GBSS is connected must not be used When the user manually terminates a session either by Disconnecting or exiting GBSS the post session commands for that session will not be launched If there are any commands that have not completed from the perspective of GBSS at the manual termination of a session that is commands from the session just prior to the one just terminated are still running then GBSS will automatically terminate those commands When the Auto Playback feature of the GBSS is invoked GBSS will wait for all post session commands to finish from the perspective of GBSS before continuing the simulation into the next session When a session is terminated due to a system failure such as a power failure GBSS will not launch the post session commands for the terminated session Note if GBSS is restarted within the same session timeframe the files before the failure will be renamed and GBSS co
120. d other characters That is we concatenate SSITES SDDDS S that is the period character SYYS and M that is the character M to get SSITESSDDDSSSS SYYSM The mnemonics and their meanings are as follows Solis The four character site name of the file SDDDS The three digit day of the year SSS The single character session code of the file SYYS The two digit year of the session Because we did not specify the directory of the output file XYZAshRx uses the same directory as the input file Finally we have also used the mnemonics for the time of the start of the session Specifically we have used SGPWS and SGPS for GPS Week for the start of the session and seconds of GPS week for the start of the session respectively 102 RINEX FILE FORMATS RINEX VERSION 2 RINEX The Receiver Independent Exchange Format Version 2 Werner Gurtner Astronomical Institute University of Berne Revision April 1993 Clarification December 1993 Doppler Definition January 1994 PR Clarification October 1994 Wlfact Clarification February 1995 Event Time Frame Clarification May 1996 Minor errors in the examples A7 A8 May 1996 Naming convention for compressed met files January 1997 Continuation line clarifications April 1997 GLONASS Extensions April 1997 Met sensor description and position records April 1997 Wavelength factor clarifications April 1997 Error in example A12 CORR TO SYSTEM TIM
121. dated as data is entered For example enter ing a value for decimal degrees West Longitude will cause the Degrees Minutes and Seconds fields of West longitude to be updated as well as all components of East longitude Additionally the Earth Centered Earth Fixed positional components will also be updated The entered positional data will be sent to the receiver each time GBSS is connected to the GPS receiver see Sections 3 2 4 1 4 6 and 4 7 The entered positions are ultimately converted to North latitude East longitude and Ellipsoidal height which are the values sent to the receiver Additionally all positional data entered will be output as part of the RINEX header data see Section 3 1 4 5 3 1 4 File Outputs File Output Configuration The File Outputs Configuration window provides a simple point and click interface for file creation settings and file manage ment settings GBSS allows you to store a wide variety of GPS data in up to four user selectable directory structures Storing a particular file type in any one of the four directory structures is as easy as enabling that files checkbox GBSS allows you to create the following different file types e Dual frequency Ashtech format GPS e Single frequency Ashtech format GPS e Dual frequency RINEX format GPS e Single frequency RINEX format GPS e Dual Frequency Ashtech format GPS GLONASS e Single frequency Ashtech format GPS GLONASS e Jonospheric m
122. df yyG Z ssssdddf yyM_Z DOS ssssdddf yyY ssssdddf yyX ssssdddf yyV ssssdddf yyW Proposed naming conventions for observation files compressed using the Hatanaka file compression scheme System Obs files UNIX ssssdddf yyD Z VMS ssssdddf yyD Z DOS ssssdddf yyE References for the Hatanaka compression scheme See for example ftp igscb jpl nasa gov igscb software rmxcmp docs IGSMails 1525 1686 1726 1763 1785 Rinex Version 2 Features The following section contains features that have been introduced for RINEX Version 2 Satellite Numbers Version 2 has been prepared to contain GLONASS or other satellite systems observations Therefore we have to be able to dis tinguish the satellites of the different systems We precede the 2 digit satellite number with a system identifier snn S satellite system identifier G or blank GPS R GLONASS T Transit nn PRN GPS almanac number GLONASS or two digit Transit satellite number Note G is mandatory in mixed GPS GLONASS files blank default modified in April 1997 Order of the Header Records As the record descriptors in columns 61 80 are mandatory the programs reading a RINEX Version 2 header are able to decode the header records with formats according to the record descriptor provided the records have been first read into an internal buffer We therefore propose to allow free ordering of the header records with the following exceptions The RINEX VERSION TYPE record must be the f
123. e File Duration to expire before GBSS actually compresses files For con figuration testing purposes you can initially speed this process by setting the File Duration parameter to 0 1 thereby setting the File Duration to 6 minutes 2 6 Windows NT Specific Installation Instructions These special NT installation instructions should only be followed if you want GBSS to automatically start with each start of Windows Section 2 1 explains that a fundamental decision needs to be made regarding whether GBSS is configured to automat ically start with Windows or not If the decision to automatically start GBSS is made then a special installation procedure must be accomplished because of the following 1 When Windows NT is started you are normally required to follow a logon process where you must type your account name and password 2 Windows NT has a built in plug and play feature that may incorrectly detect your GPS receiver as a serial mouse 3 Windows NT may not completely initialize hardware and device drivers before GBSS is started If it is not clear why item 1 1s important remember that you may not be present when your computer is re started for example because of a momentary power failure To overcome the Windows NT login requirement you can edit the registry to allow auto matic logon for the computer The procedure 1s as follows Start the Registry Editor by clicking on the Start button click on Run and type regedi
124. e are simply pushing the RINEX Observation and Navigation files to the remote FTP server using FTP95PRO EXE Please pay particular attention to the mnemonic used for the session code in the post session command S Is the mnemonic for the session code of the Ashtech processing B E and S Files Here we are using this mnemonic because we have already renamed the RINEX session codes to exactly match that of the B E and S Files 3 1 9 External Modules Configuration Built into GBSS 1s a real time interfacing capability specifically designed to provide external programs with real time data col lected through GBSS This allows you to develop applications using GPS data without concern for the details associated with communicating with the different receiver variants and the file management associated with archival of that data Next we will present a conceptual view of the interface mechanism Most users of GBSS will not be concerned with this concep tual view However the explanation will help explain the rationale behind the configuration needs and configuration approach within GBSS as it relates to the external programs termed external modules Later we will present the configuration approach through an example We will use the GBSS Met module as our example This module was designed to facilitate the collection and archival of meteorological data using GBSS a GPS receiver and a meteoro logical sensor 55 3 1 9 1 Conceptual View o
125. e change records written to the output RINEX observation file To convert a meteorological file stored ina NMEA capture file from the command line use the following form to call XYZA shRx XY ZAshRx M inmetfile outmetfile gpswk gpswksec where inmetfile The name of the input meteorological file If no path is provided it is assumed that the file will come from the current working directory outmetfile The name of the output RINEX meteorological file If no path is provided it is assumed that the file will be output to the same directory in which the input file is stored gpswk Specifies the start day of the input file This field allows you to specify the GPS week component of time 101 gpswksec Specify the start day of the input file This field allows you to specify the seconds of GPS week component of time Notice that the gpswk and gpswksec parameters are optional However if you specify either then you must specify both even if gpswksec is zero If you choose not to specify the start time of the file the program will use the current CPU time to determine the start day of the data you are strongly encouraged to avoid this approach All other parameters used in the conversion such as leap seconds and header data see Section E 3 1 2 will use values main tained from the last GUI run of the program The following provides an example XYZAshRx A99005 NMA N1020051 99M 991 176752 In this example the converter uses
126. e launched in accordance with the File Duration setting One example of the Post Session Command feature is automated file distribution Thales Navigation has worked with Ipswitch Inc to develop an automated data distribution system using Ipswitch s WS FTP Pro program GBSS can be pro grammed by the operator to open up an FTP connection at the end of each session and push the data to any remote FTP site in the world Consider the example where GBSS is configured to create 1 hour files and has FTP Post Session Commands enabled At the end of the 1 hour file session GBSS will launch the FTP Post Session Command and automatically distribute the data to remote FTP servers Any of the files created by GBSS can thus be automatically pushed around the world to remote users This feature provides the ultimate in data management and distribution over the Internet In addition any of the four user selected directory structures on the local PC running GBSS can be replicated on remote FTP sites GBSS can be programmed by the operator to automatically open an FTP connection to a remote FTP site and then auto matically create the same directory structures that are currently present in GBSS This process occurs in accordance with the File Duration parameter For example if the file interval is set to 1 hour GBSS will open the FTP connection every hour and create the GBSS directory structures on the remote FTP site Once these directory structures are created GB
127. e name including path in the command line text For example C Program Files Ashtech GBSS Utls AshFTPMD exe contains a space To assist the interpreter enclose the entire program path in quotes for example C Program Files Ashtech GBSS Utls AshFTPMD exe You should not however place quotes around the working directory of the post session command 12 When testing your post session commands it is suggested that you enable the Log file and use a simulation file see Sections 4 6 and 4 7 The rationale for this suggestion is that the simulation file will play back faster than real time and allow you to see the commands execute sooner than 1f you waited for the session to end in a live connection Again the log file will contain the fully expanded commands for those commands that properly executed and any errors detected for those commands that failed to launch 13 MS DOS Batch files can be called from GBSS as well When batch files are called from within GBSS Windows creates a command interpreter window and runs the batch file in that environment You must however clearly state in the text of the command line call that the file being executed 1s a batch file You do this by appending the file type to the execution command For example suppose you had a batch file named RENAMER BAT in the directory C BATCHES Your command line text should look something like the following C BATCHES RENAMER BAT Notice that the BAT ext
128. e receiver side of the RS 232 connection Otherwise the con nection failure is most likely near or along the line where the computer connects to the RS 232 cable Please note that if you disable the CTS RTS hardware handshaking see Section 3 1 1 3 then the CTS indicator will not illumi nate Likewise if you disable the DTR DSR hardware handshaking see Section 3 1 1 4 then the DTR indicator will not illumi nate 65 4 2 6 Logging Status Icon The logging status Icon changes color and flashes based upon the current communication status of GBSS The Icon contains no color when GBSS is not currently connected to the receiver Once GBSS is connected to the GPS receiver see Sections 3 2 4 1 4 6 and 4 7 the Icon will be in one of three states 1 Green Triangle 2 Yellow Flashing Triangle 3 Red Flashing Triangle It is important to remember that the color of the icon relates only to the current status that is it does not consider the historical performance of the communication with the receiver beyond the past few epochs of data The green triangle solid green implies that GBSS 1s currently operating without any obvious problems The Yellow Flashing Icon is displayed when 4 of the recent bytes received from the receiver cannot be interpreted by GBSS The Red Flashing Icon is displayed when 30 of the recent bytes received from the receiver cannot be interpreted by GBSS or there is an unexpected change in the RS 232 line status such a
129. e stored as TauN GammaN TauC The time tags in the GLONASS navigation files are given in UTC that is not Moscow time or GPS time Filenaming convention See above 109 REFERENCES Evans A 1989 Summary of the Workshop on GPS Exchange Formats Proceedings of the Fifth International Geodetic Symposium on Satellite Systems pp 917ff Las Cruces Gurtner W G Mader D Arthur 1989 A Common Exchange Format for GPS Data CSTG GPS Bulletin Vol 2 No 3 May June 1989 National Geodetic Survey Rockville Gurtner W G Mader 1990 The RINEX Format Current Status Future Developments Proceedings of the Second Interna tional Symposium of Precise Positioning with the Global Positioning system pp 977ff Ottawa Gurtner W G Mader 1990 Receiver Independent Exchange Format Version 2 CSTG GPS Bulletin Vol 3 No 3 Sept Oct 1990 National Geodetic Survey Rockville RINEX VERSION 2 FORMAT DEFINITIONS AND EXAMPLES 0 in L2 Single frequency instrument Table F 1 Observation Data File Header Section Description Header Label D ipti Columns 61 80 Ke id Format RINEX VERSION TYPE ormat version 2 16 14X A1 19X File type O for Observation Data A1 19X Satellite System blank or G GPS R GLONASS T NNSS Transit PGM RUN BY DATE Name of program creating current file Name of agency creating current file Date of file creation A20 A20 A20 COMMENT Comment line s MARKER NUMBER Numb
130. ek posar User Entered GPS Time Gregorian Y 1998 m f D E H E M B 5 53 GPS Week ber Seconds of Week boer Y Use receiver timetag when available to compute correction Zero Offset X Cancel Ee SEH Figure 3 20 GPS Time Configuration Window The upper portion of the screen labeled User Corrected GPS time shows the current corrected CPU GPS time in both the Gre gorian and GPS systems The section labeled User Entered GPS Time allows a choice between Options 2 and 3 That is when the Use receiver timetag checkbox 1s checked GBSS will use the time tags within the data received to compute the correc tion Note that when this check box is checked the edit fields for the User Entered GPS Time become disabled Also disabled is the Zero Offset button which will be explained shortly When the checkbox is unchecked the edit fields for the User Entered GPS Time become enabled To set a desired time enter a time that is in the very near future When that time arrives press the OK button and GBSS will compute the delta The Zero Offset button is used to implement Option 1 described above That is pressing this button forces GBSS to use the RAW CPU time as the corrected CPU GPS time When using option 3 that is the Use receiver timetag checkbox is checked GBSS must collect some data to compute the offset Upon initially selecting this checkbox or immediately after installing GBSS the of
131. elta between GPS time and UTC into the RINEX Navigation File When the I File is not present these header components will not be output to the RINEX Navigation File Notice that in the output file table above the output RINEX Navigation and Observation files appear to be both optional and required This is because at least XYZAshRx requires one of the output files Once the file names are entered press OK and a window allowing you to edit change the header data is displayed See Section E 3 1 1 1 E 3 1 1 1 RINEX Header Data Edit Window The RINEX Header Data Edit Window is displayed in response to pressing the OK button on the File Selection Window See Section E 3 1 1 Figure E 6 provides an example of this window RINEX Header Data Options x Station Hame Station Position x 1078329 5143 y 4829586 2882 z 4010719 2041 Edit Position Station Humber Station Humber XYZTT Observer s Hame LU Observing Agency The XYZ s of GPS Inc TEST CODE Creating Agency The XYZ s of GPS Receiver Type Ashtech 218 Receiver Serial Number Antenna Type Ball MciroStrip Antenna Serial Number EM Comments This is the contents of comment line number 1 This is the contents of comment line number 2 Antenna Offsets Output Data Type Horth 0 0000 Slant 0 0000 L4CP_L2P L1 C A L1 P Code and L2 P Code y East 0 0000 Radius 0 0000 Delta Vertical 0 0000 Optional Headers Options V Output Epoch Inter
132. ely automated data management When the Automatic Sub direc tory feature 1s enabled new subdirectories are created at the beginning of each day and at the beginning of each month For example if your primary directory is C PRI_ DIR and you are logging data on Nov 16 1997 then the your data will automat ically be stored in the following directory structure C PRI_DIR Nov97 Day16 If you re logging data on March 21 1998 and your secondary directory is D SEC_ DIR then your data will automatically be stored in the following directory structure D SEC_DIR Mar98 Day21 The automatic subdirectory feature conforms to the following structure mmm YY DAY dd where mmm is the 3 character month of the year YY is the last two digits of the year and dd is the day of the current month Please note that when this subdirectory feature 1s not enabled box unchecked no automatic subdirectory creation will occur That is all data files will be stored directly in the user specified Primary and Secondary directories For example if you specify C PRI_ DIR as the Primary directory then data will be stored in C NPRI DIR See the Appendices for complete details on subdirectory naming 24 3 1 4 2 Configuration File Outputs File Modes When the File Modes tab is selected the File Output Configuration window will have an appearance similar to Figure 3 12 File Dutput Configuration H ES File Modes Data Files Compression F
133. ely manage any incoming NMEA messages These incoming NMEA messages are automati cally culled into their own NMEA files This feature is especially useful when interfacing GBSS with tiltmeters meteorological stations digital seismometers or any other digital instrument outputting industry standard NMEA messages GBSS provides an extensive Session Logging Programming capability Through this feature you can configure GBSS to record data only during specified time periods These logging sessions can be both recurring and nonrecurring The recurring logging sessions repeat on a daily or weekly basis For example GBSS can be configured to record data only on Mondays Wednesdays and Fridays between the hours of 9 00 AM and 5 00 PM The nonrecurring ogging sessions which occur once are defined by a start time that is year month day hour minute and a duration For example GBSS can be configured to start recording data on November 12 2002 at 03 00 and continue to log for 10 days An automatic sub directory creation feature can be enabled for each of these directory structures Data are automatically stored in daily sub directories eliminating the confusion of storing all data in a single directory Furthermore the Post Session Com mand feature provides virtually unlimited file management tools by allowing the user to tailor the software for individual appli cations The Post Session Command feature allows command line driven programs to b
134. ension has been added 14 Intrinsic MS DOS functions cannot be directly called from the command line of GBSS Intrinsic MS DOS functions have no associated EXE file on your hard drive Examples of these functions are del rename copy and mkdir If you wish to use an intrinsic MS DOS function post session you must embed it in a batch file and execute the batch file using a post session command 3 1 8 4 Post Session Command Line Examples In this section several post session command examples are presented Many assumptions are made in these examples and will therefore not necessarily work verbatim in your environment These assumptions include such things as hard drive letters and directories in which files are stored Thus if you wish to use the examples you must tailor them to your computer system envi ronment 3 1 8 4 1 Trap File Auto Playback Example The Automatic playback feature was specifically designed to support the Post Session Command Line feature This is why GBSS accepts the GPS week and Seconds of GPS week for the start of the Trap File in the automatic playback mode see Section 4 7 The Post Session Command mnemonics GPW and GPS represent the GPS week and the Seconds of GPS week respectively The following shows an example call that could be entered into GBSS using the GBSS Post Session Commands feature to invoke the Automatic Playback feature of GBSS D SCNDGBSS GBSS exe P GPW GPS TFP
135. ent of the file naming and closure mechanisms 3 1 4 11 Configuration File Output File Re Open Rate The File Re Open Rate parameter specifies how often the File Allocation Table FAT is updated The FAT which is disk resi dent contains information describing the content of the file to the operating system Among this information is the length of the file When a fatal system error occurs such as a system or power failure the operating system is not given a chance to update the FAT Unfortunately the FAT is not normally updated until the file is closed The file re open rate specifies how often the data files will be closed and then re opened in append mode thereby updating the FAT with each re open In this way the possible data loss is limited to the amount of data collected since the most recent FAT update One must be cautioned that the re open rate does affect the performance of your computer That is the faster the re open rate the more computer resources such as CPU time and disk access time required by GBSS Specifying too fast a re open rate can degrade system performance and possibly cause loss of data over the RS 232 ports which the base station software will report It is recommended that the File Re Open Rate be set to 60 seconds If a faster rate is desired it is recommended that the desired rate be tested ON THE TARGET COMPUTER in its operational configuration before it is selected as a permanent setting The range o
136. ent working directory When either the N or the O parameters are specified XY ZAshRx will only output the associated file type Some examples are listed below Example 3 XY ZAshRx I BN102A97 323 EN102A97 323 SN102A97 323 The converter uses the files BN102A97 323 EN102A97 323 and SN102A97 323 from the current working directory as the input B E and S Files respectively Because no O or N parameters were specified XYZAshRx will automatically name the RINEX observation and navigation output files The output files will be placed in the same directory as that of the B File which is the current working directory in this case Example 4 XY ZAshRx I BN102A97 323 EN102A97 323 O OBS DAT N NAV DAT The converter uses the files BN102A97 323 and EN102A97 323 from the current working directory as the input B and E Files respectively Because no S FILE was specified the converter will use the site related data stored in the program s configuration file for site related data Because the O parameter was specified the converter will output the Observation data to the file OBS DAT The N parameter specifies that the Navigation RINEX data will be output to the file NAV DAT The output files will be placed in the same directory as that of the B File which is the current working directory in this case The T parameter allows you to specify the target path of the output RINEX files Some examples are listed below 100
137. equires less than one megabyte of memory to run Windows 95 and NT impose higher minimums You should consult the appropriate Microsoft documentation to determine the minimum system requirements for Windows XY ZAshRx requires less than 2 megabytes of disk space However XYZAshRx creates ASCII output files from your Raw Ash tech Observation files As a general rule of thumb ASCII RINEX files require approximately 1 5 times the space required by Raw Ashtech Observation Files E 1 2 Demo Versions There are two basic configurations of XY ZAshRx fully operational and demonstration versions This document applies to both configurations Demonstration versions which are freely distributed over the Internet or provided on diskette without accompa nying sentinel keys will not be nearly as capable as the operational versions For example demonstration versions will only create RINEX output files of 100 epochs or fewer This document will not seek to delineate the specific differences between the demonstration and the operational versions It is important to note however that the installation instructions documented herein apply to both configurations E 2 INSTALLATION OVERVIEW XY ZAshRx is currently distributed as part of GBSS The program will be installed in the Utils sub directory of GBSS For example if during the installation of GBSS you chose that GBSS be installed into the D Program Files ASHTECH GBSS directory then XYZAshRx wou
138. er of antenna marker OBSERVER AGENCY Name of observer agency A20 A40 REC TYPE VERS Receiver number type and version 3A20 3A20 Version for example Internal Software Version ANT TYPE Antenna number and type 2A20 APPROX POSITION XYZ Approximate marker position WGS84 3F 14 4 ANTENNA DELTA H E N Antenna height Height of bottom surface of antenna above marker 3F 14 4 Eccentricities of antenna center relative to marker to the east and north all units in meters 216 WAVELENGTH FACT L1 2 Wavelength factors for L1 and L2 1 Full cycle ambiguities l 167 3X A1 I2 2 Half cycle ambiguities squaring 0 in L2 Single frequency instrument Number of satellites to follow in list for which these factors are valid 0 or blank Default wavelength factors for all satellites not contained in such a list List of PRNs satellite numbers with system identifier Repeat record 1f necessary 110 Table F 1 Observation Data File Header Section Description continued Header Label sea Columns 61 80 Description Format 4 TYPES OF OBSERV Number of different observation types stored in the file 16 Observation types 9 4X A2 If more than 9 observation types 6X 9 4X A2 Use continuation line s Cl Pseudorange using C A Code on L1 Pl P2 Pseudorange using P Code on L1 L2 D1 D2 Doppler frequency on L1 and L2 T1 T2 Transit Integrated Doppler on 150 T1 and 400 MHz T2 Observations collected under Antispoofing
139. er of satellites for which there is data in the epoch obtained from the receiver 4 2 2 Broadcast Message Counters These Broadcast Message Counters keep track of the number of satellite broadcast messages also known as satellite navigation messages or nav messages received from the receiver since the connection to the receiver was established and since the start of the current file set The Total and File fields have similar meaning as those of the Epoch Counters see Section 4 2 1 but pertain to the Broadcast messages 4 2 3 Error Counters The Error Counters keep track of the number of messages that have been received from the GPS receiver that were in error that is their checksums were invalid The Total and File fields have similar meaning as those of the Epoch Counters see Sec tion 4 2 1 but pertain to the number of erroneous messages received It is important to note that while GBSS may report the detection of errors 1t will not write erroneous data to the Ashtech observa tion files B E and S Files That is the receiver sends GBSS several packets of data per epoch GBSS will save and write to the observation files all packets that are valid and discard any that are not It is also important to note that even invalid packets are written to the Trap File see Section 3 1 4 5 4 2 4 Available Disk Space The Available Disk Space area is divided into primary and secondary disk drive space These drives
140. ere s is the session code yy is the last two digits of the year and ddd is the day of the year Compression file names are of the following form for files of less than 1 hour duration hmmyyddd ZIP where h is the hour of the start time of the contained files A 0 X 23 mm is the minute of the start time of the contained files yy is the last two digits of the year and ddd is the day of the year For example a file named C97233 ZIP is a compression file for session C of day 233 of 1997 A file named A3002233 ZIP is a compression file for a session that began at hour 0 minute 30 of day 233 of 2002 Like the data file names the compression file names depend upon the File Duration parameter see Section 3 1 4 10 and the current corrected CPU GPS time see section 3 1 7 Some users have expressed the desire for GBSS to employ a different compression file naming approach Please be clear that through the post session command line feature see Section 3 1 5 you have complete control over file names created using PKZIP or PKZIPC Furthermore you have complete control over the target directories of the output compression files and the input files compressed by these programs including any files that may not have been generated using GBSS A 7 NMEA Output File Naming Approach NMEA Message output or capture file names of the following form syyddd NMA where s 1s the session code yy is the last two digits of the year and
141. erpreted by GBSS The Trap File is an extremely powerful feature that enables you to create multiple files for the same time period by recycling them through GBSS Using the Trap File feature each of these files from the same period can have different recording intervals For example you can set the fundamental data rate of the receiver to 1 second and enable the creation of a Trap File see Section 3 1 4 5 This Trap File will open and close in accordance with the File Duration parameter as is done with all other data files but it will store the raw data stream output by the receiver You can then use the Epoch Thinning feature within GBSS see Sec tion 3 1 4 12 to thin this raw data stream to 30 seconds for the creation of your Ashtech formatted files and your RINEX format ted files You will then have formatted Ashtech and formatted RINEX files at a 30 second epoch interval but you will have a Trap File at a 1 second interval These 1 second Trap Files can then be used in three different ways e Automated Playback mode e Manual Playback mode e Manual Simulation mode In Automated Playback Mode GBSS can be configured to automatically create files for the same time period with different epoch intervals This is because GBSS EXE can also be run in command line mode One can configure GBSS to play back the Trap File through a second copy of GBSS having a different epoch filtering to create output data files with different epoch inter vals
142. es that are being written to the primary data directory will be displayed in navy blue Those that are being written to the secondary directory are displayed in purple For an explanation of the output paths and the names of the files see Chapter 3 Table 4 1 lists the remaining parameters in this window Table 4 1 Remaining Parameters This field merely echoes the value set on the Configuration Output Files menu see Section 3 1 4 10 This field merely echoes the value set on the Configuration Output Files menu for Epoch Filtering see Section 3 1 4 12 Epoch Interval This field merely echoes the value set on the Configuration Receiver Settings menu see Section 3 1 2 Please note that if GBSS is in its Passive mode see Section 3 1 2 1 or the Command recording interval and elevation mask checkbox of the Receiver Settings menu is unchecked then the value displayed here will be UNKN for unknown Elevation Mask This field merely echoes the value set on the Configuration Receiver Settings menu see Section 3 1 2 Please note that if GBSS is in its Passive mode see Section 3 1 2 1 or the Command recording interval and elevation mask checkbox of the Receiver Settings menu is unchecked then the value displayed here will be UNKN for unknown Logging Since Displayed in this field is the corrected CPU GPS time see Section 3 1 7 when the current connection to the receiver was established Interruptions Displayed i
143. esuna Dede data DDT aS SS st Le Anie pais Navigation CJ Figure 3 3 GPS Receiver Configuration Window 1 14 3 1 2 1 Configuration Receiver Active or Passive Mode Checking the Allow Commands to Receiver checkbox places GBSS in the ACTIVE mode and allows the software to send commands to the receiver These commands include the following e Query of receiver type e Setting receiver s communication speed e Enabling and disabling real time outputs e Setting receiver s elevation mask angle e Setting receiver s recording interval e Enabling requests for latest satellite navigation messages e Enabling requests for ION messages e Disabling receiver s internal RAM storage of epoch data e Uploading site data to the GPS receiver e Uploading commands placed in the upload file The factory default for this setting is the ACTIVE mode which Magellan recommends for most users When the check is removed from the check box thereby placing the program into the PASSIVE mode no commands can be issued to the receiver If GBSS is placed in PASSIVE mode the receiver must be configured independently of GBSS to the desired communication speed and configured to transmit the binary MBEN PBEN and SNAV messages In brief one must have a priori knowledge of the receiver settings for example baud rate and then enter or select the corresponding values within GBSS For instructions on configuring the receiver manually
144. etwork drive for all of the files of interest is drive E The target directory structure on that drive will be Refdata YY Month mmm Day dd where YY is the 2 digit year of the data mmm is the 3 character month of the data and dd is the 2 digit day of the month The File duration used by GBSS maps one to one with the sessions programmed in the receiver This ensures that the session codes for Ashtech formatted data files generated by GBSS will be the same as those generated by the remote receiver via CGREMOTE EXE The following lists the post session commands for this example each of which are created on a wait for complete basis With each we list the GBSS post session command and its associated working directory Cl e Remote cgremote exe C 1 D 2 S HS DECOMP BAT Working Directory e Remote C2 e Remote DECOMP BAT Working Directory e Remote C3 e Remote DELETE BAT Working Directory e Remote C4 e Remote MOVE1 BAT FPDD Working Directory e Remote C5 C Program Files ASHTECH GRSS UTIIG XYZASHRx exe SP PDDS BCVB2Z5 52 gt Lio DDD EE O Lise DDD EE OS Loo DDDS SL EG O 51 Working Directory C Program Files ASHTECH GBSS UTILS C6 E REMOTE Copier bat SFPDDS SYYS SMMMS SDDS Working Directory e Remote We will now describe each step in more detail Step 1 There are no mnemonics from GBSS required to call CGREMOTE EXE We simply use the normal command line for mat of C
145. f acceptable values for this field are 1 and 1 3600 seconds A value of 1 disables the File Re Open Rate option that is the FAT 1s updated when the file is closed at the end of the session The choice of 0 zero is expressly disallowed 3 1 4 12 Configuration Output Files Epoch Filtering The Epoch Filtering parameter specifies the rate at which epochs will be stored in the following output files Dual frequency Ashtech format GPS e Single frequency Ashtech format GPS e Dual frequency RINEX format GPS e Single frequency RINEX format GPS e Dual Frequency Ashtech format GPS GLONASS e Single frequency Ashtech format GPS GLONASS Please note that the Epoch Filtering feature has no impact on data stored to the Trap File Epoch filtering allows GBSS to accept the raw data stream coming in over the RS 232 port write that raw data to the Trap File and then thin that data when writing it to the output B Files and RINEX files For instance if the raw data stream has been set to 1 sec ond see Section 3 1 2 2 and the Epoch Filtering feature is disabled set to 1 then the above data files will contain 1 second epoch data But if the Epoch filtering feature has been set to 30 seconds then the output files will contain 30 second epoch data It is very important to note however that the Trap Files will always contain the entire raw data stream coming in over the RS 232 port The Trap File will never be thinned through
146. f the External Module Interface Conceptually this interface has the appearance depicted in Figure 3 24 GPS External Software Interface o Receiver Program Figure 3 24 External Module Interface GBSS manages all that is needed to set up for and initiate the transfer of data from the GPS receiver Also GBSS through its normal configuration can archive and manage various data collected from the receiver When configured to do so GBSS can initialize and communicate through an interface to external programs There are a variety of ways to configure the relationship between one or more external programs a single or multiple copies of GBSS and one or more GPS receivers The simplest form is depicted above That is a single external program communicating with a single copy of GBSS with a single receiver Consider the second general form depicted in Figure 3 25 External Program 1 GPS Receiver Software Interface External Program n Figure 3 25 Interface with Multiple External Programs In the above depicted configuration there are many applications or external modules interfacing with a single copy of GBSS over a single software interface Each external program through this interface can send commands to and receive data from GBSS Although the figure gives the appearance that the external programs can communicate with one another through this interface they cannot the developers of the external
147. face to external program modules such as GBSSMet you must select the checkbox labeled Allow real time interface with external programs Once you select this checkbox the 8 character pipe identification field and the Configure External Modules button become active The 8 character pipe identification 1s used to identify the data stream from this copy of GBSS to external modules For example if you will be running multiple copies of GBSS on a single computer and wish to provide real time data to external modules then each copy of GBSS should use its own 8 character pipe name You can choose the names but make each one different and do NOT use any space or other special characters For most installations the default pipe name is sufficient For most installations of the Meteorological Module you will simply need to set the checkbox labeled as Allow real time inter face with external programs That is set this checkbox and then press the OK button However there are times when a more detailed configuration is required This is described below By pressing the Configure External Modules button you will be given an opportunity to provide GBSS with information about the external program module Upon pressing this button you will be presented a window similar to Figure 3 28 58 External Modules Configuration GBSS Client Identifier Client ID GBSSMETS Entry in Modules Menu e Show item on Modules Menu Me
148. figuration Zip using PKZIP Version 2 049 style command calls Ce Zip using PKZIPC Version 4 50 style command calls Full Path to the Zipping Program Figure 3 14 Compression Program Configuration Window Through this window you can select which compression program will be called and the path where that program is located Please note that it is essential that the correct form be selected Furthermore PKZIPC supports long file names where PKZIP 2 04g does not If you select a GBSS file naming mode that sup ports long file names see Section 3 1 4 2 you will need to use PKZIPC instead of PKZIP 2 04g 3 1 4 9 Configuration Output Files NMEA Capture File The NMEA Capture screen is accessed through the File Output Configuration window Once in the File Output screen simply click the mouse pointer on the NMEA Capture File tab to open the NMEA Capture parameters The NMEA capture parameters allow you to capture up to 21 different NMEA messages into log files NMEA messages are industry standard messages that contain a wide variety of information The NMEA capture feature is extremely useful for capturing data from auxiliary sensors such as meteorological stations and tilt meters The output from these sensors is stored in the NMEA XDR message NMEA log files will be opened and closed on the same interval that you have specified for the primary output directory files It is important to note that enabling the capture of any NMEA messa
149. formation obtained from the most recent point position solution provided by the receiver in the SPASHR PBN message The lower portion of the window contains the site position information that was passed to the receiver based on user supplied values see Section 3 1 3 As shown in the above example when a latitude longitude or height component of the site position has a zero value this lower portion of the window will dis play none implying that no position was entered for that component Figure 4 5 shows the same wi ndow with a position hav ing been entered through the Configuration Site Data window Geodetic Position Epoch Point Position WGS 84 Site Id AAAA Latitude 38 46384002 36 27 49 82407 East Long 282 56162701 282 33 41 85722 West Long 17 43837299 TE 26 18 44278 Ellipsoidal Height 49 3636 Clock Offset 253706 4375 Hum Sats 6 Clock Drift 321 4183 PDOP 2 7 Base Station Reference Position GS 34 Latitude 36 16466451 38 27 52 79224 East Long 262 561168259 282 33 40 25731 West Long FERAS Tf 26 19 74269 Ellipsoidal Height 32 21340000 Figure 4 5 Configuration Site Data Window As with all other windows in the program GBSS will show the units of a displayed field by resting the cursor over that field 68 4 3 2 Earth Centered Earth Fixed Position Window Figure 4 6 provides an example of the Earth Centered Earth Fixed Position display window ECEF Position Epoch Point Position
150. fset is not known GBSS needs to col lect some data to compute the offset Thus the first time you run GBSS with this feature enabled the files created may have incorrect names Therefore it is suggested that after selecting the Use receiver timetag option or after initially installing GBSS you collect data for several minutes to allow GBSS to calculate the offset terminate GBSS and then restart it This will ensure that when you start to log data operationally the files are named correctly Failure to follow this procedure could lead to some incorrectly named files It is important to note that there is a caveat in using the Use receiver time tag when available to compute correction checkbox That is GBSS must receive both epoch data and broadcast message data to determine the GPS time When GBSS is in its Active mode see Section 3 1 2 1 there should not normally be a problem However when in the Passive mode GBSS may not receive broadcast messages that is SNAV messages and because it is in the passive mode GBSS cannot request the receiver to send the needed messages When this occurs GBSS will not be able to correctly determine the delta This is why the manual entry of GPS time is provided It is also important to note that GBSS will store whatever options are selected from this menu If GBSS through this menu 1s instructed to compute the delta from the time tags within the data GBSS will continually compute
151. ges to a file does not cause GBSS to request these messages from the GPS receiver That is it is up to you to command the receiver either through GBSS Terminal Window commands File Upload commands or through the front panel of the GPS receiver to send the NMEA messages to GBSS 31 3 1 4 9 1 NMEA Capture File Directory The NMEA Message Capture File Directory allows you to select whether or not you want to activate the NMEA log files feature and if so where the resultant files will be stored NMEA files can be stored in either the primary or the secondary output direc tory To activate NMEA messages use the mouse to check either the primary or secondary directory checkbox Please note that if neither one of these fields are checked no NMEA files will be created Also note that only one of these fields can be checked at any given time It is important to stress that enabling the capture of any NMEA messages to a file does not cause GBSS to request these mes sages from the GPS receiver That is it is up to the operator to command the receiver either through GBSS Terminal Window commands File Upload commands or through the front panel of the GPS receiver to send the NMEA messages to GBSS 3 1 4 9 2 Write All Received NMEA Messages to Capture File This field allows you to enable the capture of all NMEA messages with the click of a mouse button When this field 1s checked checks will automatically appear next to all of the individual
152. he alphabet are used in which case GBSS will start to overwrite older files with the same name Under Windows 95 GBSS alters the renaming process described above because Windows 95 does not permit file name exten sions greater than three characters Under Windows 95 rather than appending the rename character to the end of the file GBSS replaces the last digit of the year in the file name with the rename character Finally GBSS supports three file naming modes see Section 3 1 4 2 As was Section 3 1 4 2 details these naming modes are indistinguishable when the File Duration parameter see Section 3 1 4 10 is set to 1 or between 1 and 84 However when the File Duration parameter specifies a duration that is sub hour the file naming convention must be changed to support numerous files opened and closed within an hour that is a single letter session code is not enough The classic Ashtech file names follow an 8 3 name format tnnnnsyy ddd where t 1s the file type B E S or T nnnn is the 4 character station name S 1s the session code yy is the last two digits of the year and ddd is the day of the year In this classic form the session code is usually a letter Under this approach and with a File Duration of 1 0 hours the session code can start at A that is for the O hour of the day increment to B on the next session that is for hour 1 of the day and continue with each session until X
153. he name and path of the file created by GBSS and not the file itself SEFS The name of the E File created by GBSS but does not include any drive or path information It is important to stress that we are referring to the name of the file created by GBSS and not the file itself SFP The name of the S File created by GBSS including full drive and path to that file It is important to stress that we are referring to the name and path of the file created by GBSS and not the file itself SSES The name of the S File created by GBSS but does not include any drive or path information It is important to stress that we are referring to the name of the file created by GBSS and not the file itself ROFPS The name of the RINEX Observation File created by GBSS including full drive and path to that file Itis important to stress that we are referring to the name and path of the file created by GBSS and not the file itself ROFS The name of the RINEX Observation File created by GBSS but does not include any drive or path information It is important to stress that we are referring to the name of the file created by GBSS and not the file itself RNFPS The name of the RINEX Navigation File created by GBSS including full drive and path to that file It is important to stress that we are referring to the name and path of the file created by GBSS and not the file itself RNF The name of the RINEX Navigation File created by GBSS but does not include any drive
154. he satellite signal and a receiver generated reference frequency the pseudorange code measurement equivalent to the difference of the time of reception expressed in the time frame of the receiver and the time of transmission expressed in the time frame of the satellite of a distinct satellite signal the observation time being the reading of the receiver clock at the instant of validity of the carrier phase and or the code mea surements Usually the software assumes that the observation time is valid for both the phase AND the code measurements AND for all sat ellites observed Consequently all these programs do not need most of the information that 1s usually stored by the receivers They need phase code and time in the above mentioned definitions and some station related information like station name antenna height etc GENERAL FORMAT DESCRIPTION Currently the format consists of four ASCII file types 1 Observation Data File 2 Navigation Message File 3 Meteorological Data File 4 GLONASS Navigation Message File Each file type consists of a header section and a data section The header section contains global information for the entire file and is placed at the beginning of the file The header section contains header labels in columns 61 80 for each line contained in the header section These labels are mandatory and must appear exactly as given in these descriptions and examples The format has been optimized for mi
155. he year and ddd is the day of the year For example a file named 97233 LOG is a GBSS Log file for day 233 of 1997 In the year 2000 the file name would begin with 00 80 Like the data file names the compression file names depend upon the File Duration parameter see Section 3 1 4 10 and the current corrected CPU GPS time see Section 3 1 7 A 6 Compression File Naming Approach Compression file names are of the following form for files of 1 hour duration or greater syyddd ZIP where s is the session code yy is the last two digits of the year and ddd is the day of the year Compression file names are of the following form for files of less than 1 hour duration hmmyyddd ZIP where h is the hour of the start time of the contained files A 0 X 23 mm is the minute of the start time of the contained files yy is the last two digits of the year and ddd is the day of the year For example a file named C97233 ZIP is a compression file for session C of day 233 of 1997 A file named A3002233 ZIP is a compression file for a session that began at hour 0 minute 30 of day 233 of 2002 Like the data file names the compression file names depend upon the File Duration parameter see Section 3 1 4 10 and the current corrected CPU GPS time see section 3 1 7 Some users have expressed the desire for GBSS to employ a different compression file naming approach Please be clear that through the post session command
156. ic Message Window echo that warning error in the log file and terminate any and all post session commands for the current session Most of the mnemonics are clearly defined in the Description part of the mnemonic table of the Post Session Command Line Editor window However Table 3 3 describes some of the special mnemonics Table 3 3 Special Mnemonics Expands to the character Toggles On and Off the translation of the backslash character to the forward slash character For example suppose that the full primary directory path without the drive is GPS_Data May98 Day12 The post session command C Utl GetFiles exe NDFPDD would translate to C Utl GetFiles exe GPS_Data May98 Day 12 While the post session command C Utl GetFiles exe V NDFPDD V would translate to C Utl GetFiles exe GPS_Data May98 Day 12 This backslash to forward slash translation is useful when interfacing with UNIX Please note that mnemonics can be chained together to form a single command line token For example assume that the cur rent session is session C on Jan 9 1998 for site REMD then the following post session command C GPPS Makeufil exe BFP USSITES S Y Y DDD would translate to C GPPS Makeufil exe D GPS_DATA Jan98 Day09 BREMDC98 009 UREMDC98 009 3 1 8 3 GBSS and Post Session Commands The purpose of this section is to provide miscellaneous information regarding the Post Session command feature of GBSS Befo
157. ication 10 Dec 93 The user range accuracy in the Navigation Message File did not contam a definition of the units There existed two ways of interpretation Either the 4 bit value from the original message or the converted value in meters according to GPS ICD 200 In order to simplify the interpretation for the user of the RINEX files I propose the bits to be converted into meters prior to RINEX file creation GLONASS Extensions In March 1997 a proposal for extensions to the current RINEX definitions based on experiences collected with GLONASS only and mixed GPS GLONASS data files was circulated among several instrument manufacturers and software developers The results of the call for comments have been worked into this document A separate document glonass txt summarizes just the necessary extensions A blank satellite identifier is allowed in pure GPS files only Met sensor description and position records were added to facilitate the precise use of met values Description and examples for wavelength factors and their temporary changes bit 1 of LLI clarified The RINEX documentation distributed in spring 1997 contained definitions for the GLONASS satellite clock offset and drift with the intention to have them defined identically to the GPS values Unfortunately the GLONASS Interface Document con sulted had a sign error in one of the formulae The values should be stored into the RINEX file as TauN GammaN TauC The origin
158. ify whether or not the site name change records are to be written to the output RINEX Observation file Permissible values for this parameter are 0 and 1 the value 1 directs the program to output the site name change records When the C option is not specified XYZAshRx will output site name change records as if C 1 were specified on the command line Some examples are listed below Example 7 XY ZAshRx I BN102A97 323 EN102A97 323 SN102A97 323 S 1 The converter uses the files BN102A97 323 EN102A97 323 and SN102A97 323 from the current working directory as the input B E and S Files respectively Because no O or N parameters were specified XYZAshRx will automatically name the RINEX observation and navigation output files The output files will be placed in the same directory as that of the B File which is the current working directory in this case Additionally the S parameter specifies that the converter will output Ashtech smoothed codephase observations Example 8 XY ZAshRx I BN102A97 323 EN102A97 323 p D RINEX OUT C 0 The converter uses the files BN102A97 323 and EN102A97 323 from the current working directory as the input B and E Files respectively Because no O or N parameters were specified XY ZAshRx will automatically name the RINEX observation and navigation output files but will place these files in the directory D RINEX OUT Additionally the C parameter specifies that there will be no that is 0 sit
159. iles Convert B E and S files to RIHEX Configure RIHEX Convert L1 Only B E and S files to RIHEX Output Ashtech lonospheric Model file Trap communication data to file mm lc ju la st KE MM ra ju Other File Output Options File Duration fi hours Epoch Filtering E seconds File Re Open Rate Di seconds File Deletion Age E days kW Use Ashtech Subdirectory Structure e OK x Cancel Figure 3 13 File Output Configuration Window 7 qt Ashiech The above example displays a configuration where the primary directory is E PRI DIR and the following file types have been selected for output into the primary directory e Ashtech Formatted B E and S Files e Ashtech Ionospheric Model File Please note that it is permissible to use the same directory for both the primary and secondary output directories 3 1 4 4 Configuration File Output Secondary Output Path The Secondary Output Path edit field is used to specify the top level secondary directory where data files will be stored This directory indicates where files will be stored when the file s Secondary checkbox of the File Output Selection is checked see Section 3 1 4 5 To change the directory you can manually edit the output path or use the browse feature To use the browse feature click on the BROWSE button to the right of the text Secondary Output Path On selecting this button you will be provided with
160. iles NMEA Capture File RASIM Files Output File Haming Mode Classic GBSS File Haming Approach C Classic Ashtech Hames and Extended RIHEZ Hames Extended for both Ashtech and RIHEX Hote When File Duration 1 0 hours all file naming modes are equivalent Distinction between modes occurs when File Duration 1 0 hour Please see the User s Manual for details Other File Output Options File Duration fi hours Epoch Filtering E seconds File Re Open Rate Di seconds File Deletion Age E days Y Use Ashtech Subdirectory Structure Ae OK x Cancel Figure 3 12 File Output Configuration Window 6 prt 7 Ashtech Notice in the sample window provided there are three file naming modes Most GBSS users will not see any difference between the file naming modes This is because most GBSS users desire files of 1 0 or more duration That is most GBSS users set the File Duration parameter see Section 3 1 4 10 to 1 0 or larger If you need to have files of lesser duration for example it is desired to close out a data logging period and fire the post download commands every 30 minutes then you must decide upon the file naming approach that will be used Basically the problem boils down to the idea of independent file names that are human readable For example classic Ashtech file names follow an 8 3 name format tnnnnsyy ddd where t is the file type B E S or T nnnn is the 4 character
161. iles are named using the following naming convention nnnnddds yyt where nnnn 1s the 4 character station name ddd is the day of the year S is the RINEX session code yy is the last two digits of the year and t is the file type N for Navigation and O for Observation For files of less than 1 hour duration the RINEX files are named using the following naming convention 1f one of the two the Extended RINEX names check boxes is checked as described in Section 3 1 4 2 nnnnddds yyt where nnnn 1s the 4 character station name ddd is the day of the year h is the hour of the start time of the file A 0 X 23 79 mm is the minute of the start time of the file yy is the last two digits of the year and t is the file type N for Navigation and O for Observation For example a file named RK122333 970 is a RINEX Observation file taken in session C of day 233 of 1997 Notice that in this case the session was translated from a C to the number 3 This is because by convention 1 hour RINEX sessions start with the number 1 and work to 9 then roll over to A and then increment from A That is the Ashtech B File names for Ash tech sessions A to I map to RINEX sessions 1 to 9 and Ashtech sessions J Z map to RINEX sessions A to S Both the Ashtech and RINEX file names use the 0 session code that is the number zero to denote an entire 24 hour data set Using this convention GBSS creates the names of the RINE
162. ilizes WS FTP Pro developed and sold by Ipswitch Inc to create direc tories on a remote that is host computer More specifically ASHFTPMD was designed to support the Ashtech Geodetic Base Station Software GBSS by allowing one via the GBSS Post Session Command feature to create directories on a remote sys tem and then use WS FTP Pro to transfer collected GPS data to those remote system directories via FTP C 2 System Requirements ASHFTPMD imposes the following requirements but does not necessarily report any errors if the requirements are not met Windows 95 or Windows NT on and Intel 486 compatible or higher At least 4 Mbytes memory At least 1 Mbyte disk space in order to store the program WS FTP Pro Version 4 5 or higher and Underlying socket connection to the Internet 6 A GBSS Software Sentinel Key Notice that a software sentinel key protects ASHFTPMD When distributed with Asthech s GBSS ASHFTPMD will use the same sentinel key as is provide with GBSS C 3 Using ASHFTPMD Again ASHFTPMD was designed to create directories on remote systems if they do not already exist using the File Transfer Protocol or FTP Before continuing one must understand that ASHFTPMD and WS FTP Professional are two independent software programs Each one of these programs is designed to connect to some FTP site and perform some operations via FTP commands In order to perform their operations both of these programs must connect to the
163. ill be described in more detail in Section E 3 1 1 For now we will assume that the File Selection Window has been closed to facilitate the description of the program s main window The main window of the program 1s shown in Figure E 2 91 l Ashtech Raw to RINEX Converter 32 bit The X 2 s of GPS Inc Convert Help He A ES OA ES ME He A SOS ES ME INE ANTAS O ING ATAES OPSPS INE INE AYZS OLGSP gt S 10 EA tHe Ares OL ors ine he Ares OF er ine INE AY S O INE MATAS OHSPS INE INE MATAS OFS SANG INE ATA SO Figure E 2 Ashtech Raw to RINEX Window 2 Notice the program has only two main menu items When you select the Convert menu item you will be presented with the following drop down menu Figure E 3 Figure E 3 OBs and Met Drop Down That 1s you can only Convert To RINEX using XYZAshRx Upon selecting the Obs and Nav to RINEX option you will be presented with the File Selection Window presented in Section E 3 1 1 Upon selecting the Met to RINEX option you will be presented with the RINEX Meteorological File Selection Window presented in Section E 3 1 2 Through both of these win dows you will select the input and output files of a single conversion run When you select the Help menu item from the main menu you will be presented with the command line help drop down menu Figure E 4 About Figure E 4 Command Line Help Drop Down 92 When you select the About
164. ing options Whether or not and how verbose diagnostic messages will be written to a log file Whether or not the verbose the diagnostic messages will be displayed on the screen Whether or not sound files if any will be played when alert or warning conditions arise Other Configuration Options EE Diagnostic Messages Primary Secondary IR E Output Diagnostics Message Log File teg 97233 L0G ef Write verbose diagnostic messages to log File ri Display verbose diagnostic messages Alert Sounds W Play sound file on Warning Select File Disourceiash gbss SoundsBFWarn wau J Play sound file on Alert Select File Disourceiash ghbss Soundsijfdanger wau iscellaneous Options Display the Background Bitmap x Cancel Figure 3 19 Other Configurations Options Window 3 1 6 1 Configuration Other Options Logging Diagnostic Messages Within the Other Configuration Options Menu is a checkbox labeled Primary and one labeled Secondary Jointly these two checkboxes specify if and where a Log file will be written When Primary is checked the Log file will be written to the Pri mary Data Directory see Section 3 1 4 3 When Secondary is checked the Log file will be written to the Secondary Data Directory see Section 3 1 4 4 When neither is checked no Log file will be written When either is checked diagnostic mes sages will be written to the Log file Some of these diagnostic messages may not be of intere
165. ing the Sentinel Key Before actually running GBSS you will need to install the software sentinel key Please note that GBSS will not run without this sentinel key Also note that you cannot start GBSS with the key and then later remove the key while GBSS is running The soft ware sentinel key is installed by attaching the end of the sentinel key labeled AX COMPUTER to a parallel printer port of your computer Please tighten the screws of the sentinel key to securely connect the key to your computer Ifa printer is connected to your computer attach that cable to the sentinel Ifthe sentinel cannot be installed because of an obstruction behind the computer you can place the sentinel key later in the parallel sequence for example you could attach the sentinel key to a DB 25 male to DB 25 female cable which is connected to your computer s parallel port To ensure a good connection between the computer the sentinel key and other parallel devices use only IEEE standard parallel printer cables The sentinel key allows GBSS and its support utilities to run on a single workstation Multiple copies of GBSS can be run on a single workstation without need of additional keys 2 5 Windows 95 Specific Installation Instructions The only special installation that you must perform under Windows 95 depends upon whether or not you will be using the com pression capability that is PKZIP or PKZIPC This section assumes that PK ZIP or PKZIPC has already been ins
166. ingle computer owned or leased by you You may physically transfer the Program from one computer to another provided that the Program is operated only on one computer at a time You may not operate the Program in a time shar ing or service bureau operation or rent lease sublease sell assign pledge transfer transmit electronically or otherwise dispose of the Program or Documentation on a temporary or permanent basis without the prior written consent of LICENSOR You agree not to translate modify adapt disassemble decompile or reverse engineer the Program or create derivative works of the Program or Documentation or any portion thereof TERMINATION The License is effective until terminated The License will terminate without notice from LICENSOR if you fail to comply with any provisions of this Agreement Upon termination you must cease all use of the Program and Documen tation and return them and any copies thereof to LICENSOR GENERAL This Agreement shall be governed by and construed in accordance with the Laws of the State of California and the United States without regard to conflict of laws provisions thereof and without regard to the United Nations Convention on Con tracts for the International Sale of Goods DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITY LICENSOR AND ITS THIRD PARTY SUPPLIERS MAKE NO WARRANTIES OR REPRESENTATIONS EXPRESS OR IMPLIED REGARDING THE PROGRAM MEDIA DOCUMENTATION RESULTS OR ACCURACY OF DAT
167. interval and elevation mask to the values displayed in the Recording Interval and Elevation Mask edit fields These commands will be sent to the receiver each time GBSS 1s connected to the receiver see Sections 3 2 4 1 4 6 and 4 7 The Recording Interval and Elevation Mask edit fields are editable and have meaning when the Command recording inter val and elevation mask checkbox is checked and active It is important to note that the permissible values in the Recording Interval edit field may be different than that available for your receiver type For example some Z XII receivers are not capable of a 0 1 second epoch interval but the edit field will still permit the entry of a 0 1 second epoch interval This is because GBSS supports a wide array of Ashtech receivers and must support the maximum range of values found across the Ashtech product line Sending an illegal epoch interval to the receiver will result in the receiver rejecting the command In this case the receiver will continue with its current recording interval and NO error message will be generated by the receiver or GBSS As such it is up to the operator of GBSS to ensure that only legal values for the recording interval are properly entered into the Recording Interval edit field 3 1 2 3 Configuration Receiver Disable Receiver Epoch Storage The Command receiver to disable storage of data to receiver s internal memory checkbox is available and
168. ions by breaking down the Y code into P and W code Most of these observations may suffer from an increased noise level In order to enable the postprocessing programs to take spe cial actions such AS infected observations are flagged using bit number 2 of the Loss of Lock Indicators that is their current values are increased by 4 GLONASS EXTENSIONS RINEX Observation file Time System Identifier RINEX Version 2 needs one major supplement the explicit definition of the time system GLONASS is basically running on UTC or more precisely GLONASS system time linked to UTC SU that is the time tags are given in UTC and not GPS time In order to remove possible misunderstandings and ambiguities the header records TIME OF FIRST OBS and if present TIME OF LAST OBS in GLONASS and GPS observation files can_ in mixed GLONASS GPS observation files must contain a time system identifier defining the system that all time tags in the file are referring to GPS to identify GPS time GLO to identify the GLONASS UTC time system Pure GPS files default to GPS and pure GLONASS files default to GLO 108 Format definitions see Table Al Hence the two possible time tags differ by the current number of leap seconds In order to have the current number of leap seconds available we recommend to include a LEAP SECOND line into the RINEX header If there are known non integer biases between the GPS receiver clock and GLONASS receiver clock in
169. irst record in a file The default WAVELENGTH FACT L1 2 record if present should precede all records defining wavelength factors for indi vidual satellites The OF SATELLITES record if present should be immediately followed 107 by the corresponding number of PRN OF OBS records These records may be handy for documentary purposes However since they may only be created after having read the whole raw data file we define them to be optional Missing Items Duration of the Validity of Values Items that are not known at the file creation time can be set to zero or blank or the respective record may be completely omitted Consequently items of missing header records will be set to zero or blank by the program reading RINEX files Each value remains valid until changed by an dditional header record Event Flag Records The number of satellites also corresponds to the number of records of the same epoch followed Therefore it may be used to skip the appropriate umber of records if certain event flags are not to be evaluated in detail Receiver Clock Offset A large number of users asked to optionally include a receiver derived clock offset into the RINEX format In order to prevent confusion and redundancy the receiver clock offset if present should report the value that has been used to correct the observ ables according to the formulae under item 1 It would then be possible to reconstruct the original observations if necess
170. is Z at the end of the file name that is GBSS has already been through this re name process at least once GBSS will attempt the rename process using the letter Y This rename process will continue until either GBSS finds an available name or all letters of the alphabet are used in which case GBSS will start to overwrite older files with the same name Under Windows 95 GBSS alters the renaming process described above because Windows 95 does not permit file name exten sions greater than three characters Under Windows 95 rather than appending the rename character to the end of the file GBSS replaces the last digit of the year in the file name with the rename character Additionally when recording dual frequency and single frequency data as described in Section 3 1 4 5 GBSS distinguishes between the two types of file sets by altering the convention for the L1 only data files Here GBSS simply alters the century digit of the year to an X For example suppose the dual frequency B File name is BASHTA99 312 the corresponding single frequency file name would be BASHTAX9 312 Finally there is a distinction between the terms session and logging session used throughout this documentation The distinction is detailed in section 3 1 5 A 3 RINEX File Naming Approach GBSS used the same information that was used to generate the B file name to generate the RINEX output file names For files of 1 hour duration or greater the RINEX f
171. it is permissible to use the same directory for both the primary and secondary compression directories 3 1 4 8 Configuration Output Files File Compression Selections The Output Files Configuration menu 1s used to specify if or where selected compression files will be stored This part of the menu consists of two checkboxes per item These items are labeled as follows e Compress Ashtech Formatted B E and S Files e Compress L1 Only Ashtech Formatted B E and S Files e Compress RINEX Data e Compress L1 Only RINEX Data e Compress Ashtech Ionospheric Model File e Compress communication Trap file The left most checkbox of each is labeled with a heading of Primary and the right most checkbox 1s labeled with Secondary When a check is placed into the Primary column GBSS will add that file into the compression file placed into the primary com pression directory When a check is placed in the Secondary column GBSS will add that file into the compression file placed into the secondary compression directory Please note that a file cannot be compressed and output to the primary and secondary com pression directories simultaneously GBSS protects you from setting this illegal combination The checkboxes of the File Compression Selections section are only available if their corresponding files have been enabled in either the primary or secondary output directories In other words if you have not enabled a particular file to
172. l frequency receiver or a single fre quency receiver This data is created from the L1 C A observations reported by the receiver These Ll only files can be created regardless of the receiver type Please note that GBSS allows you to simultaneously create dual frequency and single frequency GPS data files while connected to a single dual frequency GPS receiver It is also important to note that if GBSS is connected to a single frequency receiver only single frequency files will be created In this case if both the Ashtech formatted B E and S files and the L1 Only Ashtech Formatted B E and S files checkboxes are checked then you will be creating two identical single frequency data sets Conversely if you are connected to a dual fre quency receiver and both the Ashtech formatted B E and S files and the L1 Only Ashtech Formatted B E and S files check boxes are checked then you will be creating a dual frequency file set and a single frequency file set The format of standard RINEX files is defined in the paper entitled RINEX The Receiver Independent Exchange Format Ver sion 2 Dr Werner Gurtner University of Berne revised in July of 1998 There is also now an extended RINEX format version 2 2 which handles files of less than one hour duration These formats are described in Appendix F As noted above GBSS gives you the option of using either of these formats Please note that the RINEX files can only be created if the correspo
173. ld be installed into the directory C Program Files ASHTECH GBSS Utils The automatic installation of GBSS does not put XYZAshRx into the Windows search path One can add XYZAshRx to the Windows search path by right clicking on My Computer selecting the Properties menu item selecting the Environment tab selecting the Path system variable and then editing the Value field to include the directory in which XY ZAshRx is stored Additionally the automatic installation of GBSS does not put an icon onto the desk top nor in the Start Menu bar To create a program icon on the desktop simply find the program file XY ZAshRx EXE using My Computer right click and drag the icon to the desktop and select Create Shortcut Here For details on how to add a program to the Start Menu consult Windows Help searching on Start Menu and selecting the topic dealing with adding menu items to the Start Menu Finally XY ZAshRx is protected by a software sentinel key the same key as is used by GBSS The software sentinel key is installed by attaching the end of the sentinel key labeled ACOMPUTERA to a parallel printer port of your computer Tighten the screws of the sentinel key to connect the key securely to your computer Ifa printer was connected to your computer attach that cable to the sentinel If the sentinel cannot be installed because of an obstruction behind the computer you can place the 89 sentinel key
174. le Header Section Description oocococccnooooonononnno noo 113 Table F 4 Navigation Message File Data Record Description 113 Table F 5 Meteorological Data File Header Section Description cccccccnnnnnncnnnnnonos 114 Table F 6 Meteorological Data File Data Record DescrIptiON ooooncnnnnnnnnnnnnaooononnno noo 115 Table F 7 Meteorological Data File Header Section Description 115 Table F 8 Meteorological Data File Data Record DescrIptiOM ooooconnnnnnnnonnononooonno noo 116 Table F 9 Observation Data File Exame 117 Table F 10 Navigation Message File Example nn000000onoooonnnnnnennnnnnessssssssssssssssen 119 Table F 11 Meteorological Data File Example eee 120 Table F 12 Glonass Navigation Message File Header Section Description 120 Table F 13 Glonass Navigation Message File Data Record Description 121 Table F 14 GLONASS Navigation Message File Example nn000000000000000010e0000s 122 Table FI Proposed Marker Type Header 124 Table F Additional Header E TO ai 124 Table F2 pes Om Observa Oss dee 125 111 INTRODUCTION TO GEODETIC BASE STATION SOFTWARE GBSS 1 0 Overview Thales Navigation Geodetic Base Station Software GBSS is a PC based program that has been specifically designed for contin uous logging of high quality GPS data The GBSS software provides the user with sophisticated file creation file manage
175. lections would not be available for some receiver types For example if the input data is from a G 12 receiver a C A L1 only Code and Carrier receiver the selectable output data types for the receiver will not include any of the P Code or L2 observables By default the selection will be set to output all possible observation types for the input receiver type The receiver position labeled as Station Position on the window will come from either the B File data or from a user entered position This decision is made using the Site Position Window which is accessed by pressing the Edit Position button on this window For further details on the Site Position Window see Section E 3 1 1 2 Remember the changes entered into this RINEX Header Data Edit Window will be saved as part of the program s configuration data that is stored in the program s INI file In this way the header data need only be configured once Minor changes to the output header data can then be made during each subsequent run of the program 95 E 3 1 1 2 RINEX Site Position Window The RINEX Site Position Window permits you to select the source of the position data output as part of the RINEX header data This window 1s accessed from the RINEX Header Data Edit Window see Section E 3 1 1 1 Figure E 7 1s an example of the RINEX Site Position Window RINEX Site Position ES Approximate Position Horth Latitude 39 1301210262 39 D 48 4356
176. load the GBSS stored site specific data to the receiver The site specific data is entered through the Configuration Site GBSS menu see Sec tion 3 1 3 This site data will be sent to the receiver each time GBSS instructed to Connect to the receiver see Sections 3 2 4 1 4 6 and 4 7 The site data consists of the site name the antenna height and the GPS receiver reference position 3 1 2 6 Configuration Receiver Upload File to Receiver The Upload file to receiver checkbox is available and has meaning when GBSS 1s in Active Mode see Section 3 1 2 1 It does not apply when GBSS is in its Passive Mode Placing a check into this box instructs GBSS to upload the data stored in the specified upload script file each time GBSS is instructed to Connect to the receiver see Sections 3 2 4 1 4 6 and 4 7 This feature enables you to maintain a directory on your PC with a variety of script files for different applications For example you might define a script file named RTCM TXT that contains the commands needed to configure the GPS receiver to output RTCM Type 1 corrections on a specified port and baud rate Alternately you might have a script file named RTK TXT that con figures the GPS receiver to output RTK corrections on a specified port at a specified baud rate This feature enables you to pre define an unlimited number of configurations that are then always available for rapid use at a later date The Select File B
177. ly once The following are some important notes related to the logging sessions 1 All start and end times defining the logging sessions are in the GPS time system Even though we express them in a Gregorian that is UTC like format the times governing the logging sessions are in the GPS system time frame Obviously then if your needs are expressed in a local time system you must convert them to GPS time before entering them into GBSS 2 GBSS will not write to its output files the epoch with a time equivalent to the end time of a logging session unless it is overlapped by another logging session That is GBSS will record data up to but not including the logging session end time 3 Itis permissible to overlap logging sessions That is GBSS does not prohibit you from creating logging sessions that overlap 35 4 IfGBSS connects to a receiver and begins receiving data such that the current epoch time falls within an existing logging session GBSS will operate as expected that is GBSS will record the received data until the end of the logging session In the above example window one can see that there are basically five components of each logging session These are described in Table 3 1 Table 3 1 Components of Logging Session Enabled Indicates whether or not the logging session is enabled Note you can individually enable and disable each logging session as well as globally enable disable all logging sessions using
178. m the GBSS perspective and we will not describe the configuration require ments of the GBSS Met Module For a detailed description of the GBSS Met Module configuration process please consult the appropriate documentation for that program GBSSMet depends upon GBSS providing it with real time data Because GBSS and the Meteorological Module that is GBSS Met have been designed to allow multiple copies of each program to be running at one time one must specify which copy ies of GBSSMet runs with a single copy of GBSS the rationale for which was described in Section 3 1 9 1 GBSS does this by essentially naming a real time data pipe This same pipe name is then used in the Meteorological Module To configure the real time outputs for GBSS one must run GBSS and select the Configuration Real Time Interface menu item Upon selecting this menu option you will be presented with the menu shown in Figure 3 27 57 Real Time Interface Configuration Ed ES Warning This option should only be manipulated by those who have purchased external modules from Ashtech Furthermore you are strongly urged to consult external program documentation when making in changes to the External Modules Real Time Interface Configuration cessoooo The amp character name used to identify the real time interface to external modules Commgure External Modules Figure 3 27 Real Time Interface Configuration Window To enable the real time inter
179. ment and file distribution In addition all copies of GBSS software come with a Post Session Command feature The Post Session Command feature allows powerful system integration tools to be deployed and extends tremendous flexibility to the base station operator The result is an advanced and automated continuous reference station system capable of creating multiple files simulta neously even compressed files and automatically distributing them anywhere in the world GBSS will operate on a Windows 95 98 NT or Windows 2000 platform However the Windows NT Workstation and Windows NT Server or Windows 2000 are strongly recommended over Windows 95 98 Windows NT Server Version 4 0 or higher 1s recommended for users desiring to make their data available via FTP or via Web pages GBSS is 32 bit in nature and takes full advantage of NT s preemptive multi tasking and multi threading capabilities These features provide a stable and secure base station platform that requires minimal maintenance GBSS currently supports the following Thales Navigation GPS receivers e All Z 12 receivers e All Z Surveyor receivers e All Z FX receivers e All uZ receivers e All Super C A receivers e The Z Xtreme receiver e The G12 receiver e The GG 24 single frequency GPS GLONASS receiver e The Z 18 dual frequency GPS GLONASS receiver GBSS allows you to simultaneously create a wide variety of different file types Each of the file types are easily activated and
180. mimum space requirements independent from the number of different observation types of a specific receiver by indicating in the header the types of observations to be stored In computer systems allowing variable record lengths the observation records may then be kept as short as possible The maximum record length is 80 bytes per record Each Observation file and each Meteorological Data file basically contain the data from one site and one session RINEX Ver sion 2 also allows to include observation data from more than one site subsequently occupied by a roving receiver in rapid static or kinematic applications If data from more than one receiver has to be exchanged it would not be economical to include the identical satellite messages collected by the different receivers several times Therefore the Navigation Message File from one receiver may be exchanged or a composite Navigation Message File created containing non redundant information from several receivers in order to make the most complete file The format of the data records of the RINEX Version 1 Navigation Message file is identical to the former NGS exchange format The actual format descriptions as well as examples are given in the Tables at the end of the paper Definition Of The Observables GPS observables include three fundamental quantities that need to be defined Time Phase and Range TIME The time of the measurement is the receiver time of the received signals It is identic
181. mmands to the GPS receiver and view the responses This window is particularly useful for sending special commands to the GPS receiver You can also send special start up commands to the GPS receiver when GBSS is started see Section 3 1 2 6 In order to use this feature GBSS must be in its active mode see Section 3 1 2 1 and communicating with an Ashtech receiver that is you must have selected File Connect To launch this window select File Terminal menu option and you will be presented with a window similar to Figure 4 14 73 Terminal Window El EG Command SPASHS RCI 30 0 v SPASHS RCI 30 0 SPASHR PRT A 9 SPASHR RID ZM 30 1F60 C01 1D02 57 z 6C gt E Hp 64n Q SPASHR MPC QA mY A SmA A7 0 4 SPASHR MPC GI 42905 Vt 9 G Qk 98 2 SPASHR MPC IJ dE x ARSCH D amp Qg 1 m SPASHR MPC 9 B Ts 9 U ss 3hir2 W JDk SPASHR PBN n ARAAAO amp RS AN tjH lt gt G SPASHR RID ZM 30 1F60 C01 1D02 57 SPASHR RID ZM 30 1F60 C01 1D02 57 SPASHR PRT A 9 Y Show ASCII Only Figure 4 14 Terminal Window In the upper area of the window that is the area labeled with Command you can enter the command you wish to send to the receiver or you can use the drop down list to select a message template If you select a message template you may need to mod ify it before sending the command to the receiver For example the template for the RCI command is SPASHS RCLxxx xx
182. mode when creating the output file E 3 2 Command Line Approach The Command Line approach to running XY ZAshRx is invoked by calling the program with the command line parameters listed in this section The Command Line approach permits automatic conversion to RINEX of raw Ashtech data files without human intervention In this way programs or batch files can automatically convert Ashtech data files to RINEX Sections E 3 1 1 1 E 3 1 1 2 and E 3 1 2 5 discuss information that is written to the RINEX header when using the Manual GUI approach This RINEX header information is also written to the output files when using the Command Line approach but it is assumed that you have pre configured the program with the desired information The pre configuration is performed by using the Manual GUI method described in Sections E 3 1 1 1 E 3 1 1 2 and E 3 1 2 5 Once the configuration has been entered using the menus of Sections E 3 1 1 1 E 3 1 1 2 and E 3 1 2 5 and you have exited the Manual GUI run of the program the configura tion will be saved and usable from the Command Line approach Before continuing it is important to re state that the S File and I File inputs are optional However the I File is required when converting GPS GLONASS data files As is discussed in Section E 3 1 1 the absence or presence of the S File and or the I File 99 affects header data that is output to both the RINEX Navigation and Observation Files Please consult Section E
183. moved and then dragging that command to the desired location within the list of commands Again GBSS supports up to 100 post session commands 43 The wait flag indicates whether or not the command directly following the current command will be launched immediately after launching the current command or only after the current command has completely finished its execution That 1s the command wait feature is used to enforce a dependency of one command upon another in terms of when they are launched The wait flag is changed through the Post Session Command Line Editor window see Section 3 1 8 2 that 1s launched by selecting the desired command and pressing the Edit Button Whenever GBSS detects any warnings associated with a particular command line the column labeled Warn for the command contains the value Yes When GBSS detects no errors with the Post Session Command the Warn entry for that command is blank However one should not be lulled into a false sense of security with respect to the lack of any warning indication Specif ically GBSS can only perform limited checks on the commands Furthermore some checks cannot occur until the command is actually launched Therefore the command may contain errors that GBSS cannot detect To determine the rationale for the warnings detected by GBSS one should highlight the offending command press the Edit button and then press the Verify button of the displayed Pos
184. n File Outputs Primary Output Path arena 26 3 1 4 4 Configuration File Output Secondary Output Path erre Zh 3 1 4 5 Configuration File Output File Output Selections oooccccccnncnnnnnnnnnononnnnnnnininininininins 28 3 1 4 6 Configuration Output Files Primary Compression Directory ooccccccccnnnnnnnnnnnnnnnnnos 29 3 1 4 7 Configuration Output Files Secondary Compression Director 30 l 3 1 4 8 Configuration Output Files File Compression Selections cocccccccncnnnnnnnnnnnnnnnnnnnnnss 30 3 1 4 9 Configuration Output Files NMEA Capture File erre 31 3 1 4 10 Configuration Output Files File Duration ccccccncnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnonononnnnnnnnns 32 3 1 4 11 Configuration File Output File Re Open Rate eee 33 3 1 4 12 Configuration Output Files Epoch Filtering 33 3 1 4 13 Configuration Output Files File Deletion Age oooooonocooonccccccnnnnnnnnnnnnnnnnnnnnnnnnnnnnos 34 3 1 5 Logging Sessions Recording Periods dci 34 lol Edite a IN Cle TOS SIND SESSION sai chante do ld SC VLEO Other Setup Ee EE 39 3 1 6 1 Configuration Other Options Logging Diagnostic Messages coooooonnnnnccncnnncnnnnnnnnnnnnnnnnss 39 3 1 6 2 Configuration Other Options Diagnostic Message Display cccccccccccccnnnnnnnnnnncnnoos 39 3 1 6 3 Configuration Other Options Warning and Alert Sounds ooooooononcnccccnnnnnnnnnnnnonnninnnnnss 40 e CDS MMM
185. n the verification that GBSS performs on the entered commands is limited The lack of a negative indication regarding a command does not imply that it is error free When GBSS detects an error it will attempt to show the location of the violation in the text box labeled Next Warning Position Within Command Line The location is indicated using 3 carat symbols that is MM placed before the problematic entry The rationale for the warning will be displayed in the text box labeled Reason for Warn ing Figure 3 23 provides an example of the window with a warning indication Post Session Command Line Editor El Command Line EsFTPwS_FTP exe T TFP R GBSS_HOST Command Working Directory emm Y Enable Command IV Wait for this command to complete before issuing the next command BFP B File Name includes path B File Name without path E File Name includes path E File Name without path S File Name includes path S File Name without path gt SF Warnings Warnings 2 Hext Warning Position Within Command Line ESFTPWS_FTP exe T TFP R GBSS_HOST Reason for Warning Mnemonic does not agree with selected configuration Verify Cancel Ashtech Figure 3 23 Post Session Command Line Editor 45 Notice in the above example that the position of the warning appears to be the mnemonic TFP Currently there a
186. n 145 e ee e azimuth 102 mu ao ta te nm Hen Age o o o papa ss Channel i4 15 22 oo Satellite PRN Se OA Co E O A A acas 3 ra mesa 2 a lala ELE 40 488 E A l Elevation 13 60 njaj Azimuth 412 56 mmm 0 0 D Hen Age 99 99 s s ff Figure 4 8 Channel Summary Window 2 Notice in the above example screens that the GLONASS satellites are displayed in dark red and have the letter R after their satel lite numbers Also notice that in this display the GLONASS satellites have a navigation age of 99 This is because at the time of the screen capture GBSS had not received the navigation message for these satellites from the GPS receiver Please note that the 99 is not restricted to just the GLONASS satellites that is whenever any navigation message has not been received from the GPS receiver the Nav Age will be 99 As with all other windows in the program GBSS will show the units of a displayed field if you rest the cursor over that field for a couple of seconds 4 3 4 Diagnostic Messages Window The Diagnostic Message Window Figure 4 9 displays real time textual messages that provide information on the current activi ties of GBSS Most messages are time tagged with the seconds of GPS week of the most recent epoch These time tags are enclosed in the and characters In the example that follows GBSS received its first SNAV message at
187. n E 3 1 2 3 Because the NMEA GXP message that is the message used to time tag the meteorological data contains only time of day we must resolve the start day of the data file It is for this reason that the Start Day of Data prompts are provide in the file selec tion window You can specify the start day either through GPS time or through a Gregorian time When you specify the GPS time you need only be accurate to the day in which the data starts If you specify a seconds of GPS week which falls within the day that is 1t does not specify a time that is on the exact start of the day the program will be able to resolve the actual start time 97 of the file That 1s simply specify a time that falls within the correct day in which the start of the file belongs If the file contains data from multiple days of data the program will be able to resolve those day changes as well If the input meteorological data file name is in the Ashtech file naming format the program will be able to resolve the start time of the data without needing your assistance but still giving you the chance to override the start time of the file Once you spec ify the name of the file the program will parse that name and determine if it fits the proper naming convention and if so it will fill in the fields with the start time of the file Otherwise the program will default to a start time based upon the CPU clock which you should override if 1t not correct E
188. n Section 3 2 To manually connect to the receiver select the File menu option from the menu bar of GBSS This will call the drop down menu shown in Figure 4 1 Connect Ctrl C Disconnect Elo Upload le tet Play Back Ctrl F Simulation ht emita ital E sit Figure 4 1 Manual Connect Drop Down Menu 99 From this menu simply select Connect Once connected to a receiver you can manually disconnect by selecting Disconnect from this same menu Also once connected you cannot alter the configuration of GBSS That is GBSS 1s designed such that it is pre configured and then you connect to the receiver Chapter 3 describes how to configure GBSS Again you can have GBSS automatically connect to the receiver each time Windows is started See Section 3 2 for details on how to configure GBSS to auto connect to the receiver in this way In either case you must physically connect the Ashtech receiver to the computer using an Ashtech NULL modem RS 232 cable Numerous message errors may be reported 1f you fail to use a cable that meets or exceeds the specification of Ashtech cables 63 4 2 Main Display Window Figure 4 2 labels each area of the main window and provides an example of the main GBSS display Epoch Available Disk GBSS Window o Message RS 23 Line Menu Bar EMEA Status Error Logging Status Geodetic Base Station Software la Fa Ele view Dance Hep Aff II Ad DER oO i ass Ashe Epochs BC Msgs Erro
189. n be found To convert collected meteorological data to RINEX using the manual approach simply launch the program XYZAshRx with no command line options On doing so you will be provided with the main program screen Using the main menu of the program select the Convert menu option and then select the Met to RINEX sub menu option Figure E 8 E Ashtech Raw to RINES Converter 32 bit The XYZ s of GPS Inc Convert Obs and Nav to RIN EX Met to RINE Pony ep es ne E Ol ors ane Figure E 8 Met to Rinex Option 96 Selecting this sub menu option will provide you with a screen that looks similar to Figure E 9 RINES Meteorological File Selection KX Source Meteorological Data File b ssourceiAsh_RINXttestiA99005 nma Browse Start Day of Data GPS Week 991 Seconds of Week 172600 Year aa Month fi Day f Leap Seconds UTC To GPS 13 Target RIHES File D source Ash_RINX test AAAA0051 99M Browse x Cancel X cancel w re of GPS Figure E 9 RINEX Meteorological File Selection Window The primary components of this screen are 1 The source meteorological data file name 2 Start day of the source meteorological data file 3 Leap seconds for converting UTC to GPS times 4 The target RINEX meteorological data file name Upon completing the edits press the OK button to enter edit the header data related to the output RINEX meteorological data see Section A 2 5 E 3 1 2
190. n the GLONASS time frame PR GLO PR GLO c leap seconds 1f generated with a receiver clock running in the GPS time frame to remove the contributions of the leap seconds from the pseudoranges leap seconds is the actual number of leap seconds between GPS and GLONASS UTC time as broadcast in the GPS almanac and distributed in Circular T of BIPM More Than 12 Satellites Per Epoch The format of the epoch satellite line in the observation record part of the RINEX Observation files has only been defined for up to 12 satellites per epoch We explicitly define now the format of the continuation lines see table A2 RINEX Navigation Files for GLONASS As the GLONASS navigation message differs in contents from the GPS message too much a special GLONASS navigation message file format has been defined The header section and the first data record epoch satellite clock information is similar to the GPS navigation file The follow ing records contain the satellite position velocity and acceleration the clock and frequency biases as well as auxiliary informa tion as health satellite frequency channel age of the information The corrections of the satellite time to UTC are as follows GPS Tute Tsv af0 afl Tsv Toc AO leap sec GLONASS Tutc Tsv TauN GammaN Tsv Tb TauC Tn order to use the same sign conventions for the GLONASS corrections as in the GPS navigation files the broadcast GLONASS values ar
191. n this area is the total number of interruptions since the Reset button on this window was pressed GBSS keeps track and of interruptions by periodically storing data into a specific file When a connection is correctly terminated for example as Last Interruption described in Section 4 1 or when the program terminates normally the data in that file is removed If your computer fails and is restarted GBSS can detect that residual data and determine within 5 minutes when the interruption occurred Please note that while this window displays only the last interruption the Log File see Section 3 1 4 5 keeps track of every interruption 4 3 6 Post Session Command Summary Window The Post Session Command Summary window provides a description of the Post Session commands as they are executed This window will show each command as it executes and will display the full text of the command that is the mnemonics will be replaced by their translated run time values Please note that the fully expanded text will also be written to the Diagnostic Mes sage Window see Section 4 3 4 and if enabled to the Log file see Section 3 1 6 1 12 Figure 4 12 provides an example of the Post Session Command Summary window Post Session Command Summary ES Total Commands q state Running Current Command 1 Enabled Yes Text of Current Command ESFTPWshFTPMd test ashtech com quest tester PRI COMP Figure 4 12 Post Session Command Summ
192. nd Transfer to an FTP Server Example Appendix C documents a utility program supplied with GBSS with the name of ASHFTPMD EXE This utility program was specifically designed to create directories on an FTP server which grants permission to do so We have also discussed the use of WS FTP professional an FTP program used to transfer files to FTP servers which grants permission to do so In this exam ple we use the program ASHFTPMD to create directories on the remote FTP server if those directories do not already exist and then transfer GBSS collected files to those directories Furthermore on the target FTP server we wish to store raw Ashtech receiver file data in one directory while storing the RINEX counterparts in another directory We will assume that the directory in which ASHFTPMD EXE and FTP95PRO EXE are stored is CAFTP As such the working directory of each post session command is CAFTP With these assumptions consider the following post session commands each of which are created on a wait for complete basis c ftp ashftpmd exe ftp server name usrid passwd pub ashtech S Y Y Y Y MMS DD 2 c ftp ashftpmd exe ftp server name usrid passwd pub rinex Y YY Y MM _ DD 3 c ftp ftp95pro exe i ashtech ini p ash u s local BFP d ash u pub ashtech Y Y Y YS MM DD BF 4 c ftp ftp95pro exe 1 ashtech ini p ash_u s local EFP d ash u pub ashtech Y Y Y Y MM _ DD EF 5 c ftp ftp95pro exe i a
193. nder step 1 followed by C For examples you could enter the following C Program FilestAshtechiGBSS C NOTE there is a space before the C It is important to note that on some computer platforms in this automatic connection mode that GBSS may attempt to access the hardware for example the software sentinel or the communication ports before Windows has fully initialized that hardware and or pertinent device drivers This is due to the multithreaded nature of Windows NT In other words Windows NT may launch all initialization and Startup applications simultaneously upon the start of Windows NT It is therefore possible and probable that GBSS will finish initializing and begin searching for the software sentinel drivers before Windows has finished loading Because of this we may need to instruct GBSS to delay sometime before attempting to utilize the sentinel drivers that is to give NT enough time to complete the initialization of the drivers We instruct GBSS to delay using the command line C parameter This delay parameter instructs GBSS to wait before attempting to access the hardware and device drivers The delay is entered as shown in the following example C Program Files Ashtech GBSS C 45 NOTE there is a space before the C and before 45 In the above example GBSS EXE would wait 45 seconds before attempting to establish a connection with its sentinel and com munication ports Whenever the C parameter is spe
194. nding B E and S files are being created For instance if you are connected to a dual frequency receiver and you wish to create dual and single frequency RINEX files then you must enable the following checkboxes e Output Ashtech Formatted B E and S Files e Output L1 Only Ashtech Formatted B E and S Files e Convert B E and S files to RINEX e Convert L1 Only B E and S Files to RINEX The corresponding Ashtech formats must be created first in order for their RINEX counterparts to be created If you do not wish to keep the Ashtech formatted files you can have GBSS automatically delete them through the Post Session Command feature see Section 3 1 8 The Ionospheric Model file will only be created when GBSS is in active mode This is because the ION data must be requested from the receiver through a command and the passive mode does not permit commands to the receiver The Ionospheric Model file is a binary disk file which exactly replicates that which is described in your receiver manual for the PASHR ION message less the PASHR ION header and checksum information that is the file is exactly 74 bytes long 28 The Trap file records all of the bytes that enter into GBSS via the communication port that is a capture of ALL raw communi cation activity between the GPS receiver and GBSS In other words the Trap File is simply a byte for byte copy of all of the data received over the communication port before it is int
195. ndow ccccccccssssssccceceeeessessssneeeeeesessesssaeeeeeeessseesnaaees 59 Figure 3 29 Modules Addition to Main Menu cccceccssssccccceeeesssssnneeeeeeeeesesssneeeeeeesesesnsaeeeeeeeesesesnaaaes 59 Figure 3 30 Added Modules cias 60 Figure 4 1 Manual Connect Drop Down Menu cccccccccccceessssssseeeeeeeeeesesesseeeeeeesesesesnsaaeeeseesessessaaees 63 Fi ute 42 GBSS Main Window sia A AAA 64 Figure 4 3 Logging SESSIONS Status Bart AAA 67 Figure 44 Geodetic Position Window a 68 Figure 4 5 Configuration Site Data Window cccccccnnnnononononononnnnnononononnnnnncnnnnn nono nnnnnnnnnnnnn ono nnnnnnnnnnnnnnnnnnnos 68 Fisute 46 ECE EP POStttOm WINGO Ww lt A A A 69 Figure 4 7 Channel Summary Window 1 ccccccccssssssesccccesssesssecesecccessssssscenceeccceesseesccceceeceesssescenecenses 69 Figure 4s Channel Summary Window ee 70 Figure 4 9 Diagnostic Messages Window occccccccccnnnnnnnnnonononoonnnnnnnonnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnns 71 Fiour 410 Losine Summary Window E is iii ADO 71 Figure 4 11 Logging Summary Window 2 ooooooooconccccnnononononnnnnnnnononnnononnnnnnnnnnnnn nono nnnnnnnnnnnnn non nnnnnnnnnnnnnnnnnnnnos 12 Figure 4 12 Post Session Command Summary Window occccccnnnnnooonnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnncnnnnnannnononnnos 73 Figure 4 13 Time Display Window AAA a E EEN 73 Fiure 414 ee ER le 74 Figure 4 15 Simulation Start Time Window c oooooccccccnnnnnnnoooon
196. ndows user interface for GNSS2GPS EXE Appendix D provides detailed documentation on this program 2 1 The Installation Process To install GBSS onto your computer insert the GBSS installation diskette labeled GBSS Install Disk 1 into the A or B drive of your computer Press the Start button and select Run Use the Browse command to locate and run the Setup program on the diskette located in the A or B drive of the computer The install program guides you through the installation of the GBSS software At each step you will be given an opportunity to accept default options or tailor these to your individual needs You will be required to enter your 8 character serial number This serial number is located on each of the GBSS installation diskettes The GBSS serial number is the first eight characters located on your installation diskettes For example your diskette may be labeled as follows KF004561 GBSS00 041698 For this example the GBSS serial number is KF004561 Please note that without the proper serial number you will not be allowed to continue the GBSS installation Upon completing the installation of the GBSS program and data files you will be asked three questions 1 Whether or not you want a GBSS entry in the Windows Start Program menu 2 Whether or not you want a shortcut to GBSS added to your Windows desktop 3 Whether or not you want GBSS to be automatically started with each start of Windows
197. nonnnnnnnnnnnnnonnnnnnnnnnnnnn nn nnnnnnnnnnnnnn nn nnnnnnnnnnnnnnnnnnnns TS Figure 4 16 Simulation Speed Slide Bar as 76 Figure E 1 Ashtech Raw to RINEX Window 1 91 Figure E2 Ashtech Raw to RINEX Window 2 ui A 92 Figure E 3 OBs and Met Drop Down ccccccsssssessnencccccsssessencnncccceesssescencnsscceesssesssenensseceesesssnseeenaes 92 Figure EA Command Line Help Drop Down Sa 92 Figure E 5 RINEX Conversion File Selection Window cocccccnnnnonononnnnncnonnnonnnnnnnnnnnnnnnnnn nono nnnnnnnnnananonnnos 93 Fistire B 6 RINEX Header Data Edit WINDOW as 94 Figure E 7 RINEX Site Position Window ccccccsssscesscccecsesesssncecccccesessessenesssccessessssnuenseceeesesesseeeenses 96 Figure E 8 Met to Rinex Option oooooooccccnccnnnnonononnnnnnncnnnnnnnss Figure E 9 RINEX Meteorological File Selection Window ccccccccccccsssesssseeeeeeeceessessseeeeeeeeeessensneees Figure E 10 RINEX Meteorological Header Data Window LIST OF TABLES Table 3 1 Components of Logging SESSION ii 36 Table 3 2 Command Components sereni rE 43 Table 3 3 Special NINCM NICS laa 46 Table 3 4 Post Session MAS MODISTAS 50 Table 325 GBSS MOMO ns 53 Ke NR DEE EE I2 KO re EE 93 Table E 2 OUP DIT TE iia 95 Table F 1 Observation Data File Header Section Description oooooooonnccnnnnnnnnnnnnnno o 110 Table F 2 Observation Data File Data Record Description ccccccncnnnnnoocccnnnnnnnnnnnnnos 112 Table F 3 Navigation Message Fi
198. ntinues to store data in the files named for the current session At the completion of this session GBSS will execute the post session commands on the files for the current session that is these will not include the renamed files It is recommended that the user provide an Uninterruptible Power Supply UPS for the computer for any mission critical uses of GBSS to prevent any problems with lost data When the post session commands for a session are terminated due to a system failure such as a power failure GBSS will not restart those commands on the restart of GBSS The commands will however be started at the completion of 47 the subsequent session It is recommended that the user provide an Uninterruptible Power Supply UPS for the computer for any mission critical uses of GBSS to prevent any problems with lost data 11 Itis recommended that you not use post session commands with embedded spaces in the paths For examples many programs are automatically installed in the Program Files directory While GBSS has been tested with and does operate properly with paths containing spaces this author has seen the Windows command processor become confused with paths containing spaces For this reason it is recommended that you not use paths with embedded spaces that is copy or move programs to paths that do not contain spaces Additionally you can assist the command interpreter by placing quotes around the executable program name or batch fil
199. nu Entry Meteorological Module Command Line D Source GBSSMet GBSSMet exe Command Working Directory 0 Source GBSSMet Start module whenever GB55 is started lt lt Prev fo OK X Cancel Am ech Figure 3 28 External Modules Configuration Window Each copy of GBSS will support up to ten external program modules The Next gt gt and Prev lt lt buttons let you scan through the configuration of each of the ten modules Certain external modules are specifically identified to GBSS by a Client ID This ID 1s used primarily to prevent multiple cop ies of the same program from automatically being launched by GBSS The developer of the external module defines the ID For the case of the Meteorological Module the Client ID is GBSSMETS The entry is case sensitive Please note that this discus sion assumes that the external program being called implements the interface to GBSS That is one could through this external modules feature have GBSS launch an external program that does not implement the GBSS real time interface However because that program is not communicating with GBSS through this interface GBSS will continuously assume that it failed to launch the external program This could lead to GBSS inadvertently launching many copies of the external program Therefore it is suggested that this mechanism be used only for external programs that fully implement the GBSS interface The area of the
200. number not mod 1024 Leap seconds Delta time due to leap seconds 16 End of header Last record in the header section 60X Table F 4 Navigation Message File Data Record Description PRN EPOCH SV CLK Satellite PRN number Epoch Toc Time of Clock year 2 digits month day hour minute second FS 1 SV clock bias seconds 3D19 12 SV clock drift sec sec SV clock drift rate sec sec Broadcast Orbit 1 IODE Issue of Data Ephemeris 3X 4D19 12 Crs meters Delta n radians sec MO radians Broadcast Orbit 2 Cuc radians 3X 4D19 12 e Eccentricity radians Cus radians sqrt A sqrt m Broadcast Orbit 3 Toe Time of Ephemeris sec of GPS week 3X 4D19 12 Cic radians OMEGA radians CIS radians 113 Table F4 Navigation Message File Data Record Description continued Broadcast Orbit 4 Broadcast Orbit 5 Broadcast Orbit 6 Broadcast Orbit 7 Header Label Columns 61 80 10 radians Crc radians omega radians OMEGA DOT radians sec 10 radians sec Codes on L2 channel GPS week to go with TOE continuous number not mod 1024 L2 P data flag SV accuracy meters SV health MSB only TGD seconds IODC Issue of Data Clock Transmission time of message sec of GPS week derived for example from Z count in Hand Over Word HOW spare spare spare Table F 5 Meteorological Data File Header Section Description Description RINEX version type Fo
201. o a live receiver this area of the window shows COMx nnnnn where x is the communication port of the receiver and nnnnn is the BAUD being used to communicate with the receiver When GBSS is in its simulation or play back modes the connect status shows Simulated while the simulation is in progress and Disconnected when the simulation completes 4 2 8 Epoch Time Display The lower status bar of the GBSS main window contains status information among which is the GPS time of the last epoch received When GBSS is not connected to a receiver or simulating a receiver this area of the display is left blank Again the GPS time of the epoch is displayed in a Gregorian fashion and should not be confused with UTC that is the time displayed is in the GPS system and not UTC 4 2 9 Sub Window Display Area The sub window display area of the main window is used to display all of the status windows described under Section 4 3 You are free to move all of the sub windows within this area Moving a window beyond the display region of this area will cause scroll bars within this area to be displayed These scroll bars will allow you to scroll through the display area 4 2 10 Logging Sessions Status Bar The logging sessions status bar will be visible only when the Logging Sessions Session Programming feature of GBSS has been enabled see Section 3 1 5 When visible the text at the left of the status bar that is Logging Sessions Acti
202. o range epoch must be maintained that is the receiver clock correction should be applied to all 3 observables Time corr Time r dT r PR corr PR r dT r c phase corr phase r dT r freq DOPPLER The sign of the doppler shift as additional observable is defined as usual Positive for approaching satellites The Exchange Of Rinex Files We recommend using the following naming convention for RINEX files ssssdddf yyt ssss 4 character station name designator ddd day of the year of first record f file sequence number within day 0 file contains all the existing data of the current day yy year t file type O Observation file N Navigation file M Meteorological data file G GLONASS Navigation file To exchange RINEX files on magnetic tapes we recommend using the following tape format 106 Non label ASCII fixed record length 80 characters block size 8000 First file on tape contains list of files using above mentioned naming conventions When data transmission times or storage volumes are critical we recommend ompressing the files prior to storage or transmis sion using the UNIX compress und uncompress programs Compatible routines are available on VAX VMS and PC DOS systems as well Proposed naming conventions for the compressed files System Obs files GPS Nav Files GLONASS Nav Files Met Files UNIX ssssdddf yyO Z ssssdddf yyN Z ssssdddf yyG Z ssssdddf yyM Z VMS ssssdddf yyO Z ssssdddf yyN Z ssssdd
203. odel file e Trap File e NMEA file e Diagnostic log file e Compressed files The Post Session Command feature see Section 3 1 8 allows you to create even more file types than those listed above Any third party command line driven program can be called by GBSS This feature allows you to call such a program to automati cally do work on one of the above file formats The result can be an entirely new data format not directly supported by GBSS The File Output Configuration window contains five different sections that are accessible via the five tabs located at the top of the window These tabs are as follows e File Modes tab e Data Files tab e Compression Files tab e NMEA Capture File tab RSIM Files tabs 20 Figure 3 7 through Figure 3 11 show five examples of the File Outputs Configuration window one for each of these tabs File Dutput Configuration File Output Configuration EPRDR 7 A as Ia ta le im ka m fes je Figure 3 8 File Output Configuration Window 2 21 File Output Eae bi les des Jum fes qua fes m m des qu dos je Figure 3 9 File Output Configuraiton Window 3 File Output Configuration lt lt lt a 4 a lt lt al lt a lt lt a lt lt lt a lt lt lt a Figure 3 10 File Output Configuration Window 4 22 File Output Configuration Figure 3 11 File Output Configuration Window 5 To move between each of these three sc
204. omes a three character field It basically has the form hmm where A is the hour code that is A to X and mm represents the start minute of the hour Because the File Duration parameter has a lower limit of 0 05 that is 3 minutes independent file names can be generated In the sections that follow the classic naming modes are detailed When and extended naming form is selected the session code of the file name changes as described above A 1 Ashtech Subdirectory Naming Approach The Use Ashtech Subdirectory Structure Checkbox of the Configuration File Outputs menu see Section 3 1 4 1 indicates whether or not the Ashtech subdirectory naming structure will be employed When checked subdirectories from those speci fied in the Primary and Secondary directories both data and compression will automatically be created and filled When unchecked the created files will be stored in the directories specified as Primary and Secondary The Ashtech subdirectories are of the form mmm YY DAY dd where mmm is the 3 character month of the year YY 1s the last two digits of the year and dd is the day of the current month Example 1 The corrected CPU GPS time indicates that the day is Oct 28 1997 the Use Ashtech Subdirectory Structure Checkbox is checked and the Primary Subdirectory is E SITTE1 DAT GBSS would create the following Primary directory E SITE1 DAT Oct97 DAY 28 All of the data slated for outp
205. omputer Additionally your PATH must be configured to provide programs access to the PKZIP or PKZIPC programs These programs are off the shelf packages and are not provided as part of GBSS If you plan on using the long file name options of GBSS see Section 3 1 4 2 page page 25 you will need to use PKZIPC exe from the PKZIP 4 5 Suite for Windows If you will be using the Auto Startup feature of GBSS see Section 3 2 page 60 and are installing GBSS on a Windows NT plat form you will need to bypass the Windows NT logon screen For this you will need to edit the registry to allow automatic logon This is described in Section 3 2 If you desire to use the automated FTP push feature of GBSS it is necessary to purchase WS FTP Professional Version 4 53 from Ipswitch Inc WS FTP Pro is not distributed with GBSS because Thales Navigation does not own it WS FTP Pro can be purchased from Ipswitch Inc at the following Internet address http www ipswitch com During installation it is highly recommended that you not install WS_FTP Pro into a directory that has spaces in directory names such as the default directory Program Files WS_ FEIDT This is because Windows NT and Windows 95 have difficulty inter preting some command line calls containing spaces in path names Note the location of FTP95PRO must be in the PATH of your system 1 3 Demo Versions of GBSS There are two basic configurations of GBSS fully operational and demonstr
206. on Comms Use CTS RTS Hardware Handshaking 13 3 1 1 4 Configuration Comms Use DTR DSR Hardware Handshaking cocccccnncnnnnnononnnos 13 liza GEO Receiver RECCIVEl E lol 13 3 1 2 1 Configuration Receiver Active or Passive Mode nnsnnnnnnnnnnnnnnsenessnsssssssssssesseerereeeseo 15 3 1 2 2 Configuration Receiver Epoch Interval and Elevation Mask ssssooosoossssosssssssssssssssses 16 3 1 2 3 Configuration Receiver Disable Receiver Epoch Storage ooooooonnnnnccccnncnnnnnnnnnononnnnnnnss 16 3 1 2 4 Configuration Receiver Receiver Outputs Its Compressed Data Records 17 3 1 2 5 Configuration Receiver Upload Site Data to Receiver ooooooocooononcccnoncccncconnnonononnnnnnnos 17 3 1 2 6 Configuration Receiver Upload File to Receiver oooooooooooooonccccccncnnnnnnnonnnnnononononononons 17 3 1 2 7 Configuration Receiver Passive Mode Receiver Information 18 A og Le capt A ne QD PE SR RR eee 18 SL COMM Surarion Site SHO E 19 3 1 3 2 Configuration Site Antenna EE 20 3 1 3 3 Configuration Site Site Position ooooooooooooooooccnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnss 20 3 1 4 Pile Outputs File Output Contieuration esiansasastes ines asas ieniana nad l eas EENEG aa d da aw 20 3 1 4 1 Configuration Output Files Ashtech Subdirectories ccc eee 24 3 1 4 2 Configuration File Outputs File Modes 25 3 1 4 3 Configuratio
207. on 3 1 7 Unlike the data files however the compressed versions of these files are created AFTER the associated data files are CLOSED No attempt is made to compress a file until after 1ts File Duration period has passed As such depending upon the speed of your computer and its processing load compression of recently closed session files may not complete for quite some time after the data files for that session were closed The appendices provide a complete description of the file naming conventions used by GBSS 3 1 4 8 1 Configuration Output Files Selecting PKZIP or PKZIPC Compression GBSS is designed to call PKZIP or PKZIPC from PK WARE Inc to perform the compression of data files GBSS does no checking to ensure that PKZIP 2 04G or PKZIPC exe from the PKZIP 4 5 Suite for Windows 1s installed onto your computer Nor does GBSS ensure that PKZIP or PKZIPC are callable that is 1t does not check to ensure that PKZIP or PKZIPC can actu ally run As such GBSS will still permit the selection of the compression options even though PKZIP and PKZIPC cannot be called IT IS UP TO YOU TO INSTALL PKZIP OR PKZIPC ONTO YOUR COMPUTER AND ADD PKZIP OR PKZIPC TO YOUR PATH To configure which form of PKZIP that is PKZIP 2 04g or PKZIPC exe that GBSS will use press the button labeled Config Compression Upon pressing this button a window similar to Figure 3 14 is displayed Compression Program Configuration Compression Program Con
208. on types the format F14 3 is good enough to handle all requirements regarding the maxumum range and precision Receiver channel numbers can be stored as special observations CH Lowest channel number allowed is re number channels beforehand if necessary In case of a receiver using multiple chan nels for one satellite the channels could be packed with two digits each right justified into the same data field order correspond ing to the order of the observables concerned Format according to lt 5 nc gt 2X lt nc gt 12 2 0005 nc being the number of channels Restriction Not more than 5 channels and channel numbers lt 100 Examples 0910 000 for channels 9 and 10 010203 000 for channels 1 2 and 3 F 4 3 We propose to convert the open loop data into standard phases and signal strengths before reformating the data into RINEX files for data exchange This proposal does not handle data collected by one receiver and multiple antennas In this case the data have to be stored in separate RINEX files one per antenna 125 FILENAME RECOMMENDATIONS We propose to use the standard file naming scheme for LEO POD tracking data by defining a 4 character code for each LEO receiver or receiver antenna combination The RINEX data should be distributed in daily files Faster data exchange could use hourly files if necessary ssssdddh yyo two digit year character for the starting hour in the day a 00 b 01 x
209. or more than one antenna at the same time Data on more than one channel to the same satellite can be stored however the channel information gets lost 7 It was noted that for some applications both possible phase observations on the first frequency L1 CA as well as L1 P1 should be stored in the RINEX files 123 Proposed Modifications In order to indicate the nature of the marker spaceborne receiver anew MARKER TYPE header record has been defined as deefined in Table F 1 Table F 1 Proposed Marker Type Header Marker Type Curently defined are A20 40X GEODETIC Earth fixed high precision monumentation NON_GEODETIC Earth fixed low precision monumentation SPACEBORNE Orbiting space vehicle AIRBORNE Aircraft balloon etc WATER CRAFT Mobile water craft GROUND CRAFT Mobile terrestrial vehicle FIXED BUOY Fixed on water surface FLOATING BUOY Floating on water surface FLOATING ICE Floating ice sheet etc BALLISTIC Rockets shells etc ANIMAL Animal carrying a receiver HUMAN Human being Record required except for GEODETIC and NON GEODETICC marker types Attributes other than GEODETIC and NON GEODETIC will tell the user program that the data were collected by a moving receiver The inclusion of a start moving antenna record event flag 2 into the data body of the RINEX file is therefore not necessary Event flags 2 and 3 are still necessary to flag alternating kinematic and static phases of a moving receiver h
210. or path information It is important to stress that we are referring to the name of the file created by GBSS and not the file itself Let us suppose that the file is session B RINEX session 2 on December 14 1999 Further let us suppose that the Ashtech sub directory structure has been enabled in GBSS and that the files of interest are stored in the Primary Data Directory having a root directory of E GPSDATA The third command would be translated by GBSS as follows 3 c ftp ftp95pro exe i ashtech ini p ash u s local E GPSDATA DEC99 DAY 14 BSITEB99 348 d ash u pub ash tech 1999 12 14 BSITEB99 348 Using the same supposition the sixth post session command would be translated as follows 6 cifipftp95pro exe i ashtech ini p ash u s local E GPSDATA DEC99 DAY 14 SITE3482 990 d ash u pub rinex 1999 12 14 SITE3482 990 50 We have shown the translation for the remaining post session commands because they are similar to those already described 3 1 8 4 3 A Remote Receiver and a Network Directory Example In this example we seek to copy all data stored by GBSS to a network drive Further it is desired to have GBSS using another program dial a remotely located GPS receiver to retrieve 1ts data convert that data to RINEX and then store the downloaded and converted data onto the network drive To accomplish this the following steps are to be performed through GBSS post session commands at the completion of each
211. orking Directory C FTP c ftp ftp95pro exe 1ashtech imi p condorST s local SBFPS d condorST cors data SMMMSSYYS DAY SDDS SBES Working Directory C FTP c ftp ftp95pro exe iashtechini p condorST s local SBFPS d condorST cors data SMMMSSYYS DAYSDDS SHES Working Directory C FTP c ftp ftp95pro exe 1ashtech imi p condorST s local SBFPS d condorST cors data SMMMSSYYS DAYSDDS SSF S Working Directory C FTP C BATCHES UPLOAD BAT SSS SDDDS SYYS SFPDDS cors data SMMMSSYYS DAYSDDS Working Directory C BATCHES We will now describe each step in more detail Step 1 GBSS calls the batch command file RXASHSES BAT to rename the RINEX files stored in the GBSS Primary Data Directory such that their session codes to exactly match that of the B E and S Files The contents of the batch file is as follows REM 1 THE DIRECTORY IN WHICH THE RINEX FILE TO BE RENAMED RESIDES REM 2 THE 4 CHARACTER SITE NAME OF THE FILE REM Si THE B FILE SESSION CODE REM 4 THE GBSS GENERATED RINEX SESSION CODE REM rename 1 2 7 4 2 7 272727 3 Here we are calling the MS DOS intrinsic command rename as such we have placed it into a batch file Notice in the post ses sion command that we are using the mnemonics S and RXS SSS is the mnemonic for the session code of the Ashtech processing B E and S Files and SRXSS is the mnemonic for the session code of the RINEX files 54 Step 2
212. ow ccccccccncnccnnnncononnnononncnnnnnnnnnnnnnnnnnnnnnnnnnnnnnonananos 69 43 Channel Summary tee 69 4 5 4 Diagnostic Messages WINdOW a AAA 70 Aldo OSs me samman WINdOW aestus een tas aides av a ee ea 71 4 3 6 Post Session Command Summary Window oocccncnnnncnnnnnnnnnnnnncnnnnnnnonnnnnnnnnnnnnnnnnnnnnnnnnnnonnnnnnnnns 12 AS A Da me nee ee 73 44A SN EE 73 40 Uploading a Command Fileto RE 74 4 6 Running a Simulated Connection to a Receive ii 75 4 7 Automatic Playback from the Command me 76 Appendix A FILE NAMING APPROACH nncocconconnconconcnnncnncnnccnncnnroncnnncnnronrrnncnnronrnanranrnarennes Uf A l Ashtech Subdirectory Naming Approach 78 AZ ByE Sand Trap rile Namie Ap prod cia 78 Ao RINEX FileName ApprodC h Eege eegen egen 79 Ace JON Pile Enner EE SU e LOS Pl NA A EE 80 Ao Compression File Nanne ADEGA ebe E eines 81 A 7 NMEA Output Fil Namino Approach assassinas eeh ebe 81 AS LOG Pile Namins APPEAR SEO ta 81 Ao Compression File Naming AP at 82 A 7 NMEA Output File Naming Approach 82 Appendix B UPLOAD FILE FORMAT ccccccceeccecceeeeeeeeeeeeseneeneeesseneeneeaseaneensenssanseneseees 83 Appendix C UTILITY PROGRAM ASHFTPMD aii 85 CL MIG OCC Te da each acta an seo pe esis wt aoe cess nee Se De E O eee a RR 85 DAS ON UE EE 85 E UsncA SE COMI cial Iii 85 e bn c a 5 och BOONS ege 86 Appendix D UTILITY PROGRAM GNSS2GPBS ERKENNEN ENNER EREN REENEN REENEN EN RENE RENE 87 DL Introduction to ONSS2GES EE 87 DZ
213. ow to make these utilities available for your use These support utilities are documented in the appendices of this manual Further installa tion instructions on these utilities can be found in those sections 2 3 External Modules GBSS also has a real time external program interfacing capability This feature provides applications external to GBSS with the ability to obtain the real time data collected by GBSS There are two such programs currently available from Thales Navigation 1 the GBSS Meteorological module and 2 the GBSS Tilt module The GBSS Meteorological module is used when connecting a Paroscientific MET3 or MET3A station The Meteorological module permits the automatic collection conversion and archival of meteorological data including the creation of RINEX meteorological files The Tilt Module integrates a tilt meter supplied by Applied Geomechanics Inc With this module one can monitor and record the tilt information output by a tilt meter attached to the GPS receiver To install any of these modules first complete the installation of GBSS and then follow the installation instructions supplied with that external module Section 3 1 9 provides some information about configuring GBSS for external modules The information in that section is generic for all external programs using the real time interface of GBSS For specifics on each module supplied by Thales Navigation please consult the documentation for that module 2 4 Install
214. owever The following new optional header fields have additionally been defined ANTENNA DELTA X Y Z Antenna position in body fixed coordinate system meters 3F 14 4 ANTENNA B SIGHT XYZ Boresight of antenna Direction os the antenna axis towards the GPS satellites Corresponds to the ver tical axix on earth bound antenna Unit vector in body fixed coord system OBS SCALE FACTOR Factor to divide stored observations with before use 16 16 8 4X A2 Number of observation types involved List of observation types Repeat record 1f different factors are applied to different observation types Attributes other than GEODETIC and NON GEODETIC will tell the user program that the data were collected by a moving receiver The inclusion of a start moving antenna record event flag 2 into the data body of the RINEX file 1s therefore not necessary Event flags 2 and 3 are still necessary to flag alternating kinematic and static phases of a moving receiver however The following new optional header fields have additionally been defined The OBS SCALE FACTOR record allows for example to store phase data with 0 0001 cycles resolution 1f the data was multi plied by SCALE FACTOR 10 before being stored into RINEX file As the antenna position data could be given in a body fixed coordinate system with the origin not coinciding with the satellite s center of mass we have to define an additional header line with the current center of mass coordinates
215. ows as the working directory of the command For most calls it is the same directory as the directory in which the program you are calling is stored In the above example the program is stored in the directory E FTP as such we set this directory as the working directory All text entered into this field for the working directory 1s treated verbatim GBSS does not interpret translate any mnemonics found in the entry of the working directory field The Enable Command checkbox is used to enable disable selected commands This feature 1s particularly useful when you are testing your post session commands because you can disable the commands that are not directly part of your test The wait for complete indication is used to indicate whether or not GBSS will wait for the current command to complete before launching the next command in the set of post session commands Checking this checkbox allows you to specify the dependency of later commands upon the completion of the current command If there are no later dependencies then the checkbox labeled Wait for this command to complete before issuing the next command does not need to be checked However if you want to ensure that each command is launched only after the completion of the last command make sure that the wait for complete checkbox is checked on each command The lower half of this window displays any warnings detected by GBSS as a result of pressing the OK or Verify Buttons Agai
216. please consult the appropriate receiver manual When in Passive mode you must set the communication speed of GBSS under Configuration Comms Speed Additionally GBSS must be configured to identify the receiver type and receiver software version numbers see Section 3 1 2 7 Failure to properly identify receiver type and software version numbers could result in unusable output data files Section 3 1 2 shows GBSS configured for Active Mode Figure 3 4 shows GBSS in Passive Mode and connected to a Z FX GPS receiver 15 GPS Receiver Configuration El ES Receiver Commands i Command recording interval and elevation mask Recordma Intervalo 11 00 seconds Elevation Mask 14 degrees P Use compressed epoch measurements UGE i command receiver to disable storage of data to receivers internal meno I Upload site date to receiver Upload ile to receiver DD Upload ile BEFORE requesting real time data select Hle DSc teas gbs uploadist Passive Mode Receiver Information Receiver Type UZ 12 Receiver Software Version Channel 0416 Havigation CJ Figure 3 4 GPS Receiver Configuration Window 2 3 1 2 2 Configuration Receiver Epoch Interval and Elevation Mask The Command recording interval and elevation mask checkbox 1s available and has meaning when GBSS 1s in 1ts Active Mode see Section 3 1 2 1 Placing a check into this box instructs GBSS to set the receiver s recording interval or epoch
217. primary output directory GBSS allows you to specify separate directory paths for the primary output directory and for the primary compression directory For example you might specify the following Primary output directory of C PRI_DIR Primary compression directory of D PRI_COMP The primary output directory and the primary compression directory are related only in that the creation of a certain file needs to be enabled in the primary or secondary output directory before 1t can be compressed in the primary or secondary compression directory To change the primary compression directory you can manually edit the output path or use the browse feature To use the browse feature click on the BROWSE button to the right of the text Primary File Compression Path Upon selecting this button you will be provided with a window that is capable of navigating over the entire set of directories of your computer Use that window to select the desired primary compression directory If the desired directory does not exist simply use the New Folder button in the upper right corner of the directory selection window to create 1t Please note that it is permissible to use the same directory for both the primary and secondary compression directories 29 3 1 4 7 Configuration Output Files Secondary Compression Directory The Secondary File Compression Path edit field 1s used to specify the top level secondary directory where compressed ver
218. ptional 111 The following observation types are defined in RINEX Version 2 L1 L2 Phase measurements on L1 and L2 Table F 2 Observation Data File Data Record Description Obs Record EPOCH SAT OR EVENT FLAG OBSERVATIONS Epoch year 2 digits month day hour min sec Epoch flag 0 OK 1 power failure between previous and current epoch gt 1 Event flag Number of satellites in current epoch List of PRNs sat numbers with system identifier see 5 1 in current epoch Receiver clock offset seconds optional If more than 12 satellites Use continuation line s If EVENT FLAG record epoch flag gt 1 Event flag 2 start moving antenna 3 new site occupation end od kinem data at least MARKER NAME record follows 4 header information follows 5 external event epoch is significant same time frame as observation time tags 6 cycle slip records follow to optionally report detected and repaired cycle slips same format as Observation redords slip instead of observation LL1 and signal strengthe blank Numver of satellites contains number of records to follow 0 for event glags 2 5 Observation rep within record for each obs type same seq as given in header LL1 Signal strength If more than 5 obaservation types 80 char continue observations in next record This record is these records are repeated for each satellite given in EPOCH SAT record Observations Phase units in whole c
219. r files are closed based upon the time stored within the GPS data received from the receiver In naming the files the ses sion will be based upon the hour of the corrected CPU GPS time and the File Duration parameter of the Configuration File Outputs Menu see Section 3 1 4 10 For example if the File Duration is set to one hour then the session code will relate to the hour in which the file is opened A hour 0 B hour 1 C hour 2 etc With each file closure the session will be incre mented When the File Duration is set to 24 hours the session for every file will be 0 that is zero Sessions are closed and new ones opened based upon the GPS time tags of the data being received from the receiver GBSS uses the correct CPU GPS time only for file naming purposes Again GBSS avoids overwriting files with the same name and does not append to existing files with the exception of Log files This is particularly important for cases where GBSS is terminated indirectly such as for a power failure When GBSS is restarted after one of these indirect terminations it may generate output file names for files that are already on disk for example GBSS is terminated in the middle of a File Duration and is restarted within the same File Duration When this occurs GBSS attempts to rename the files already on disk It does this by appending a Z to the tail end of disk resident file name If there is already a file on disk with th
220. r Count Wailable Disk Space O Total File Time EE Total File Total File Primary E 590016 a La 7 im197 00 4 44 4 o 0 Secondary E 590016 TA Logging Sessions Active Within a Session C0M10 3600 Epoch GPS Time Mar 24 1999 14 39 30 00 Wk 1007 Sec 311970 00 wy Connect Status Logging Sessions syb Window Work Last Epoch Status Bar Figure 4 2 GBSS Main Window With the exception of the Main Window Title and the Menu Bar items the sub sections which follow describe each of the above labeled items 64 4 2 1 Epoch Counters During the logging of receiver data the Epoch Counter area of the main window will display information pertaining to the cur rent epoch of data Depending upon the selected File Duration option see Section 3 1 4 10 files are closed and new ones are opened at a specified interval As such it is sometimes beneficial to know the epoch status since connecting to the receiver as well as the epoch status in relation to the current file set To this end the epoch counters are labeled as Total and File The Total counter shows the total epochs received since the connection to the receiver was established and the File counter shows the number of epochs written to the files of the current file set since they were opened The Time field shows the time in seconds of GPS week of the epoch data received from the receiver The SVs field shows the numb
221. re continuing with the discussion it is important for the reader to understand what it means for a command to be com pleted The completion of a command is dependent upon the perspective from which you view the command That is from the perspective of the operating system that is Windows a command is viewed complete when the program actually finishes However there are cases where the command will be completed from the GBSS perspective even though it has not completed from the perspective of Windows For example if the Post Session Command Line Editor window dialog item Wait for this command to complete before issuing the next command was NOT checked for a command when GBSS launches the command 46 it will not wait for Windows to return a complete indication before launching the next command From the perspective of GBSS the command has completed However from the perspective of Windows the command may still be executing When GBSS reaches the end of a File Duration it begins launching the Post Session Commands The command being exe cuted or any errors encountered while attempting to start the command will be sent to the Diagnostic Message Window and the Log file That is if you encounter errors in your post session commands ensure that the Log file is turned on see Section 3 1 6 1 and then run GBSS again Any errors will be reported in the Log file and in the Diagnostic Message Window Success ful command launches
222. re for added security GBSS can be configured to work with a BBS system There are many off the shelf packages that provide a means to call in via telephone line and download data It must be emphasized that GBSS does not by itself contain all of the tools necessary for automated Internet and BBS operation Rather it has been designed to work m concert with such packages For example in order to employ the automated FTP distri bution you must first purchase the program WS FTP Pro from Ipswitch Inc Ipswitch Inc can be reached at the following Internet address http www ipswitch com GBSS also has a real time external program interfacing capability This feature provides applications external to GBSS with the ability to obtain the real time data collected by GBSS In fact currently available are two specialized program modules available from Thales Navigation that exploit this interface 1 the GBSS Meteorological module and 2 the GBSS Tilt module The GBSS Meteorological module is used when connecting a Paroscientific MET3 or MET3A station The Meteorological Option permits the automatic collection conversion and archival even RINEX Met Files of meteorological data The Tilt Module integrates a tilt meter supplied by Applied Geomechanics Inc With this module you can monitor and record the tilt information output by the tilt meter attached to the GPS receiver 1 1 Minimum System Requirements GBSS requires the target platform to
223. re only four warnings displayed by GBSS These are 1 Epansion of mnemonics causes command line length to exceed 256 character maximum 2 Mnemonic does not agree with selected configuration 3 Badly formed or unrecognized command line mnemonic 4 Invalid working directory for the program The first warning occurs when the expanded form of the command line causes the command line to exceed 256 characters that is 256 characters is the DOS maximum per command The second warning occurs when the current configuration of GBSS conflicts with the command line mnemonic For example your command line uses a mnemonic which represents Trap Files but you have not selected Trap Files for output by GBSS in the Configuration Output Files menu The third warning occurs when GBSS does not recognize an entered mnemonic that is the characters between two and including the characters The final warning occurs when you specify a working directory that does not exist on disk Note that even though a command contains a warning GBSS permits the acceptance and storage of that command If by run time the cause of that warning 1s not corrected and that command is enabled GBSS will cancel all post session commands until the set of enabled commands are completely warning free Additionally GBSS can detect other warnings errors at run time When any such warnings errors are detected GBSS will display the rationale for the warning error in the Diagnost
224. rections from port C at a 3 second rate The format of the upload file is described in Appendix B 4 6 Running a Simulated Connection to a Receiver As stated in Section 3 1 4 5 GBSS is capable of creating communication Trap Files A Trap File can be played back through GBSS in such a way that simulates a connection to the receiver GBSS can perform this play back in one of two modes Play Back and Simulation Neither mode simulates the exact timing of the data received They are designed simply to allow GBSS to interpret the data as if 1t were actually received from a receiver Obviously any commands issued by GBSS when operating in these modes are in vain as there is no receiver actually connected to GBSS It should also be obvious that setting the epoch inter val on the Configuration GPS Receiver menu see Section 3 1 2 2 has no impact in the data received from the Trap File That is GBSS does simulate a GPS receiver but can only do so by using the data that is available in the Trap File The Play Back mode is started by selecting File Play Back from the GBSS menu bar The Simulation mode is started by selecting File Simulation After selecting either of these you will be provided with a file selection window through which you can specify the file to be played back through GBSS Once started you can terminate either mode by terminating the pro gram or selecting File Disconnect from the GBSS menu bar
225. rectories automatically created by GBSS After deleting files from any Ashtech named subdirectory GBSS will attempt to remove these subdirectories if they are empty GBSS can take up to and not exactly 2 days beyond the value specified for the deletion age This is because GBSS does not delete files until at least one day after the end of the day in which the file is named For example suppose that we set up 1 hour sessions we have a deletion age of 5 days specified and file BMEGFA97 233 is created GBSS does not consider the deletion of this file until day 240 that is day 233 does not complete until day 234 begins and GBSS adds 1 day to the 5 as described above thus 234 6 The range of acceptable values for this field are 1 and 1 180 days A value of 1 disables the deletion of aged files 3 1 5 Logging Sessions Recording Periods GBSS can be configured to record data only during specified periods For example if you need only record data from 9 00 AM to 5 00 PM Monday through Friday each week then you can use the Logging Sessions feature to achieve this goal Before continuing however it is important to make a distinction between the terms session and logging sessions In this manual we refer to sessions and logging sessions as independent concepts Both are related to a period over which data are collected The term session by itself is related to the File Duration described in this Section 3
226. reens simply click on the tab of the screen you wish to go to It 1s important to note that there is a close relationship between the Data Files screen and the Compression Files screen Files cannot be compressed unless they have been first enabled in the Data Files tab 23 The following lists the types of parameters not an all inclusive list that can be set through the Output Files Configuration win dow e File Output Naming Modes e Primary data file output directory e Secondary data file output directory e Primary compression file output directory e Secondary compression file output directory RINEX file outputs RINEX header information e Which output data files to store and in which directories e Which compression file to create and in which directories e Whether or not to use the Ashtech automatic sub directory creation feature e The duration of data collection sessions e The rate at which the FAT that is the File Allocation Table is updated e The epoch filtering rate and e The age of files to be automatically deleted from the system 3 1 4 1 Configuration Output Files Ashtech Subdirectories The Use Ashtech Subdirectory Structure checkbox is located at the bottom of the File Output Configuration window and controls the automatic subdirectory creation feature When enabled this feature will automatically create new subdirectories for file data management purposes and provide you with complet
227. rmat version 2 File type M for meteorological data PGM Run By Date Station name preferably identical to marker name in the associated Observation file A60 20 Name of program creating current file Name of agency creating current file Date of file creation Station number preveravbly identical to marker number in the associated Observation file Types of observ Sensor Mod Type Acc Number of different observation types stored in the file Observation types The follofing meteorological observation types are defined in RINEX Version 2 PR Pressure mbar TD Dry temperature deg Celsius HR Rekative humidity percent ZW Wet zenith path delay millimeters for WVR data The sequence of the types in this record must correspond to the sequence of the measurements in the data records If more than 9 types of observation types are being used use continuation lines with format 6X 9 4X A2 Description of the met sensor Model manufacturer Type Accuracy same units as obs values Observation type Record is repeated for each observation type found in Types of observ record 114 Format 3X 4D19 12 3X 4D19 12 3X 4D19 12 3X 4D19 12 Format 16 14X A1 39X A20 A20 A20 A 16 9 4X A2 A20 A20 6X F7 1 4X A2 1X Table F 5 Meteorological Data File Header Section Description continued Header Label Columns 61 80 Description Sensor pos XYZ H Approximate position of
228. rrect The second command is translated by GBSS as follows 2 c ftp ashftpmd exe ftp server name usrid passwd pub rinex 1999 12 14 This command will launch the program ASHFTPMD and create the directory pub rinex 1999 12 14 on the FTP server Our intent with this command is to create a directory in which to store the GBSS created RINEX files Again that directory will only be created if 1t does not already exist on the FTP server In the remaining post session commands of this example our intent is to use the program FTP95PRO EXE to transfer files to the FTP server please consult the manual for that program for details on its command line structure and options In each of these commands we push the appropriate files to the directories previously created To do this we use several mnemonics which are described in Table 3 4 Table 3 4 Post Session Mnemonics Mnemonic Description BFP The name of the B File created by GBSS including full drive and path to that file It is important to stress that we are referring to the name and path of the file created by GBSS and not the file itself BF The name of the B File created by GBSS but does not include any drive or path information It is important to stress that we are referring to the name of the file created by GBSS and not the file itself EFP The name of the E File created by GBSS including full drive and path to that file It is important to stress that we are referring to t
229. rs the renaming process described above because Windows 95 does not permit file name exten sions greater than three characters Under Windows 95 rather than appending the rename character to the end of the file GBSS replaces the last digit of the year in the file name with the rename character Additionally when recording dual frequency and single frequency RINEX data as described in Section 3 1 4 5 GBSS distin guishes between the two types of file sets by altering the convention for the L1 only data files Here GBSS simply alters the century digit of the year to an X For example suppose the dual frequency RINEX file name is ASHT3121 990 the corre sponding single frequency file name would be ASHT3121 X90 Finally there is a distinction between the terms session and logging session used throughout this documentation The distinction is detailed in section 3 1 5 A 4 ION File Naming Approach The Ionospheric Model file names are of the following form IONyy ddd where yy is the last two digits of the year and ddd is the day of the year For example a file named ION97 233 is an ionospheric model file for day 233 of 1997 Like the data file names the compression file names depend upon the File Duration parameter see Section 3 1 4 10 and the current corrected CPU GPS time see Section 3 1 7 A 5 LOG File Naming Approach The GBSS Log file names are of the following form yyddd LOG where yy is the last two digits of t
230. rts 3 1 Configuration Menus Most GBSS parameters are set through the main menu Configuration option The Configuration drop down menu is divided into 9 different selections These 9 selections become available when Configuration is selected calling the drop down menu shown in Figure 3 1 11 Communications GPS Recelwer Site File Outputs Logging Sessions Other Options GFS Time Post Session Commande Real Time Interface Figure 3 1 Configuration Drop Down Menu The following sub sections describe each of the nine configuration windows GBSS is designed such that the software is configured before connecting to a receiver It 1s important to note that GBSS also needs to be configured before using the receiver simulation capability see Sections 4 6 and 4 7 page 75 Once GBSS is con nected to a GPS receiver the GBSS Configuration screens are not editable GBSS must be disconnected from the GPS receiver before the Configuration screens become accessible again You can however change the configuration of the receiver while GBSS is connected to that receiver Special features have been built into GBSS to change the GPS receiver s parameters while GBSS is still connected to the GPS receiver The receiver s parameters can be changed by sending commands through the terminal window or by uploading a script file These features are covered in Sections 4 4 page page 73 and 4 5 page page 74 respectively
231. run without this sentinel key Also note that you cannot start GBSS with the key and then later remove the key while GBSS is running The soft ware sentinel key is installed by attaching the end of the sentinel key labeled ACOMPUTERA to a parallel printer port of your computer Please tighten the screws of the sentinel key to connect the key securely to your computer Ifa printer is connected to your computer attach that cable to the sentinel If the sentinel cannot be installed because of an obstruction behind the computer you can place the sentinel key later in the parallel sequence for example you could attach the sentinel key to a DB 25 male to DB 25 female cable which is connected to your computer s parallel port To ensure a good connection between the computer the sentinel key and other parallel devices use only IEEE standard parallel printer cables The sentinel key allows GBSS and its support utilities to run on a single workstation Multiple copies of GBSS can be run on a single workstation without need of additional keys Prior to connecting to the GPS receiver GBSS needs to be configured to suit your data collections needs Please note that this configuration process is extremely important as the GBSS factory defaults will more than likely not meet your needs The GBSS configuration information is stored in two files GBSS INI and GBSS SES which are located in the directory in which the GBSS EXE program resides GBSS INI contains mo
232. s a break in the RS 232 line GBSS is not designed to interpret all possible messages from an Ashtech receiver As such you may have special configuration needs that cause data to be output to GBSS from the receiver For this reason GBSS will not terminate based upon any value of invalid bytes received from the receiver Furthermore you may have configured the GPS receiver to output messages that GBSS does not interpret In this case GBSS will report either the Yellow or Red flashing icon will be recording B and E files and assuming that the Trap File feature is turned on will be recording all data including the unrecognized messages to the Trap File GBSS can be configured to play a sound file when a yellow flashing Logging Status Icon is displayed It can be configured to play a different sound file when a red flashing Logging Status Icon is displayed Refer to Section 3 1 6 3 for more details on con figuring GBSS to play sound files This feature is especially useful for continuous operation when the monitor has been turned off to conserve power For these situations the audible alarm rather then the flashing indicator provide the first clue of any problems 4 2 7 Connect Status The lower status bar of the GBSS main window contains status information among which is the connection status When GBSS is not connected to a receiver and not simulating a receiver this area of the window displays Disconnected When GBSS is connected t
233. session are opened The computation for file closure is based upon the GPS time obtained from the received data That is if the File Duration is one hour file closures will occur on the GPS hour boundary that is the first set of files may not contain one whole hour of data The range of acceptable values for this field are 1 and 0 05 84 hours Please note that GBSS will accept values for the File 32 Duration that are greater than zero but less than 1 but these values impose the special file naming described in Section 3 1 4 2 During initial installation setup and or experimentation values in the range of 0 05 to 1 0 can be used to facilitate testing espe cially the Post Session Commands described in Section 3 1 8 in that they will cause completion of sessions more frequently In GBSS there are two uses of the term session In this manual we refer to sessions and logging sessions as independent concepts Both are related to a period over which data are collected The term session by itself is related to the File Duration described in this section In this use we recognize that files are closed at the specified duration and the session codes used to name the files see Appendix A are based upon the Corrected CPU GPS Time see Section 3 1 7 The other use that is og ging sessions is used to describe the periods in which data are actually recorded into files see Section 3 1 5 independ
234. shtech ini p ash_u s local SFP d ash_u pub ashtech Y Y Y Y MM _ DD SF 6 c ftp ftp95pro exe i ashtech ini p ash u s local SROFPS d ash_u pub rinex Y Y Y Y MM _ DD ROF 7 _c ftp ftp95pro exe i ashtech ini p ash_u s local RNFP d ash_u pub rinex Y Y Y Y MM _ DD RNF In each post session command the mnemonics Y YY Y MM DDS are used In each case these mnemonics represent the time of the session as 4 digit year 2 digit month and 2 digit day of the month respectively For example suppose that the ses sion of data occurs on December 14 1999 then when launching the post session commands GBSS will translate first post ses sion command as follows 1 c ftp ashftpmd exe ftp server name usrid passwd pub ashtech 1999 12 14 This command will launch the program ASHFTPMD and create the directory pub ashtech 1999 12 14 on the FTP server Our intent with this command is to create a directory on the FTP server in which to store the raw Ashtech formatted files Again 49 that directory will only be created if it does not already exist on the FTP server Of course this assumes that the parameters passed to ASHFTPMD define the correct FTP server user name and password and that the FTP server grants that user name permission to create directories Throughout the remainder of this example we will assume that the FTP server grants the per missions needed and that the account information 1s co
235. sive mode see Section 3 1 2 1 Section 3 1 4 5 of this document describes the format of the Trap File as well as how to concatenate several Trap Files 4 7 Automatic Playback from the Command Line Sections 4 6 and 4 7 of this manual both describe simulated connections to GPS receivers As Section 4 6 states the simulation playback feature of GBSS allows one to replay a Trap File using other features configuration values of GBSS The Automatic Playback feature enables one to playback a Trap File through a command line call When GBSS is executed in this fashion it will automatically playback the file and will terminate upon completion of the playback This feature in conjunction with the normal data logging can be used to create output files with various GBSS controlled attributes such as epoch intervals For example one could in normal data logging collect 1 Hz data in a Trap File and then use the Auto playback feature to created B Files with 30 20 15 10 5 and 1 second epochs The Automatic Playback feature 1s invoked as shown in the following example command line call GBSS P 944 226320 D GPSData TARC1K97 041 The syntax of this call is as follows GBSS P GPSWk GPSWkSec TrapFName Where GPSWk The GPS Week of the start of the Trap File specified by TrapFName GPSWkSec The Seconds of GPS Week of the start of the Trap File specified by TrapFName TrapF Name The name of the Trap File to be used in the playback Section 3 1
236. st of the GBSS configuration information GBSS SES contains config uration data that is specific to the Logging Sessions feature described in Section 3 1 5 page page 34 GBSS automatically updates the contents of these files as you make changes using the configuration menus of GBSS Changes in the configuration of GBSS are written to its configuration files GBSS INI and GBSS SES so that the configuration may be recalled at the start of the next run of the program In this way once the desired configuration is set the operator no longer needs to change it unless or course it needs to be altered to support a new configuration The majority of these parameters are set using the Con figuration sub menus Details of the contents of the Configuration sub menus follow Since GBSS INI and GBSS SES are ASCII text files the configuration can also be modified with any text file editor How ever you are strongly discouraged from making configuration changes using this is approach In fact after you get GBSS config ured to meet your needs a prudent computer procedure would be to make a backup copy of the configuration files After configuring GBSS and before collecting data operationally it is suggested that you collect some sample GPS data for about 5 minutes and then terminate GBSS through its normal termination methods described later in this manual This will save the configuration files so that they will be available the next time GBSS sta
237. st to some users For this reason you are provided a means of stripping the diagnostic messages down to only those that are critical The checkbox labeled Write ver bose diagnostic messages to log file when unchecked keeps the diagnostic messages to their minimum Log files contain the diagnostic messages generated by GBSS for an entire GPS day The format of the Log file name is described in the appendices 3 1 6 2 Configuration Other Options Diagnostic Message Display The Display verbose diagnostic messages controls the level of diagnostic messages written to the Diagnostic Messages win dow see Section 4 3 4 Some users may not be interested in seeing all of the diagnostic messages Leaving this checkbox 39 unchecked keeps the diagnostic messages to a minimum that is displaying only critical messages The system resources for example CPU time of some older computers may be severely taxed when updating the Diagnostic Messages Display window Leaving this checkbox unchecked will help to free up some of these resources 3 1 6 3 Configuration Other Options Warning and Alert Sounds GBSS is capable of playing WAV files when an alert or warning condition arises see Section 4 2 6 for an explanation of these conditions The Other Configurations Menu allows you to set the sound files to be played when the alert or alarm condition arises IT IS IMPORTANT TO NOTE THAT GBSS DOES NOT CHECK TO ENSURE THAT A YOU HAVE A SOUND
238. t Session Command Line Editor window During run time GBSS records information about the post session commands in the output Log file when it is enabled see Sec tion 3 1 6 1 This information will include the fully expanded post session command or the rationale as to why the post session command failed The post session commands will only launch if at run time there are no warnings in the set of enabled post session commands Additionally GBSS will terminate the set of post session commands upon receiving an error from the oper ating system on any command If you enabled the GBSS Log file see Section 3 1 6 1 information on all post session commands will be written to that file The Log file can be very helpful in testing your entered post session commands That is when testing your post session com mands it is suggested that you enable the Log file and use a simulation file see Sections 4 6 and 4 7 The rationale for this sug gestion 1s that the simulation file will play back faster than real time and allow you to see the commands execute sooner than if you waited for the session to end in a live connection Again the log file will contain the fully expanded commands for those commands that properly executed and any errors detected for those commands that failed to launch 3 1 8 2 Post Session Command Line Editor Window The Post Session Command Line Edit window Figure 3 22 allows you to edit post session commands and perform
239. t in the window that appears l In Registry Editor select the following subkey HKEY LOCAL MACHINE Software Microsoft Windows NT CurrentVersion Winlogon Add a new string value entry named AutoAdminLogon of type REG SZ and specify a value of 1 Do this using Edit New String Value to create the new value Then highlight the new value and use modify to specify the value Add a new string value entry named DefaultPassword of type REG SZ and enter the password of the user who is listed under the value of DefaultUserName Item number 2 is important because the RS 232 lines are set high by a powered Ashtech receiver and can be misinterpreted by Windows NT when Windows is started That is each time Windows NT is started its plug and play feature looks for any new peripheral devices that may have been recently connected This feature may inadvertently determine that the GPS receiver con nected to a communication port is a serial mouse device To prevent this you must modify your BOOT INI file as described in the following steps Make a backup copy of the BOOT INI file 2Determine the existing hidden system and read only attributes from the BOOT INI file that is write them down somewhere 3 Remove the hidden system and read only attributes from the BOOT INI file 4 Using a text editor such as Notepad exe open the BOOT INI file 5 Add the NoSerialMice option to the end of each entry in the operating systems
240. talled onto your computer and that your PATH is set appropriately Again neither PK ZIP nor PKZIPC are installed as part of and do not come with GBSS When GBSS compresses files it uses PKZIP 2 04g or PKZIPC EXE from the PKZIP 4 5 Suite for Windows Because PKZIP 2 04g is an MS DOS program when GBSS calls PKZIP or PKZIPC an MS DOS prompt window is created it is opened as a minimized window that is the only sign of the MS DOS window 1s an icon on the task bar By default Windows 95 does not close this window when PKZIP or PKZIPC terminates To solve this problem you will need to run GBSS and wait until 1t com presses files for the first time Once the task bar icon for that window is created simply follow these steps Click on the icon and the window will become maximized 2 Put your cursor into the title bar of the window that is the top of the window which is normally blue and press the Right not left button on your mouse This will cause a pop up menu to appear 3 Select the Properties option on the pop up menu This will cause a new window to appear 4 Inthe newly created window select the Program Tab 5 At the bottom of the program tab is a checkbox labeled Close on Exit set it to checked and press the OK button GBSS compresses files based upon your selected compression options see Sections 3 1 4 5 to 3 1 4 8 and the File Duration see Sections 3 1 4 10 You will need to wait for th
241. the Header Records data did E 107 Missing Items Duration of the Validity Of Values ds 108 Event elas RECO ri 108 Receiver COCK OBSC nas ces A es Odd 108 ADDIHMIONAC HINISANDTIES pirani 108 RINEX UNDER AN TIS POOR TING IAS sia 108 GLONASS EXTENSIONS aa iO 108 RINEX Observation lat A 108 Time System Identidad S 108 A Te EE 109 More Than 12 Sate Waites Per EPOCA nal da 109 RINEX Navicanon Files tor LONAS 109 REFERENCES peso AAA S 110 RINEX VERSION 2 FORMAT DEFINITIONS AND EXAMPLES cocccccccnnnnnnnnnnnanananononcncncnnnnnannnnnonons 110 RINES VEO ta berg 122 EE Renee 122 tere te DEE 123 Proposed MOCOS ti O iii 124 FILENAME RECOMMENDA TIONS ssa ada 126 Consequences for Ground Based Data Fues 126 il AAA a E AN 126 Pap a a 127 LIST OF FIGURES Figure 3 1 Configuration Drop Down Menu oooccccccccnnnononononnnnnnnnnnnnnononnnnnnnnnnnnnn non rnnnnnnnnnnnnn ono nnnnnnnnnnnnnnnnnnnos 12 Figure 3 2 Commumnication Configuration Window oooooccccccnnnnoooononcnnnnnnnnnnnnnonnnnnnnnnnnnnnn ono nnnnnnnnnnannn nn nnnos 13 Figure 3 3 GPS Receiver Configuration Window le 14 Figure 3 4 GPS Receiver Configuration Mentee 16 Fiems 3 Select Fileto Upload DEE 17 Figure 3 6 Site Confiouranion ME 19 Figure 3 7 File Output Configuration Window 1 21 Figure 3 8 File Output Contiouratiom Window 2 a eege 21 Figure 3 9 File Output Configuraiton Window 3 22 Figure 3 10 Fil Output Config tation Window ai 22 Figure 3 11 File Output Configuration Window 3 23
242. the files that exist on disk and will automatically create the output file names In the sample window above the user used the Browse button of the B File to select input B File and XYZAshRx found associated E and S Files on the disk but not an associated I File and automatically named the output RINEX Observation and Navigation files In the input file table above notice that the S and I Files are optional When these files are not specified XYZAshRx automati cally makes changes necessary to output header data in the associated RINEX files In particular when the S File 1s specified XYZAshRx sets certain default values for the output RINEX header based on data contained in the S File When the S File name is not provided the site related header data is obtained from and saved to the configuration file The RINEX header data affected by the presence of the S File are as follows Station Name Observer s Name Receiver Serial Number Antenna Serial Number Antenna Offsets Slant Radius and Delta Vertical Obviously the above information would be obtained from the S File if it were present Similarly the presence of the I File affects the header of the output RINEX Navigation File For GLONASS RINEX conver sions the I File is required When the I File is present XYZAshRx places the ionospheric header data containing the model alphas and betas and the leap second header data that is the data needed to determine the time d
243. the met sensor 3F14 4 1F14 4 1X A2 Geocentric coordinates X Y Z ITRF or WGS 84 1X Ellipsoidal height H Observation type Set X Y Z to zero if not known Make sure H refers to ITRF or WGS 84 Record required for barometer recommended for other sensors End of header Last record in the header section 60X Table F 6 Meteorological Data File Data Record Description 613 Epoch Met Epoch in GPS time not local time Year 2 digits month day hour min sec Met data in the same sequence as given in the header mF7 1 More than 8 met data types Use continuation lines 4X 10F7 1 3X Table F 7 Meteorological Data File Header Section Description e Description Format Columns 61 80 P RINEX version type Format version 2 16 14X A1 39X File type M for meteorological data PGM Run By Date Name of program creating current file A20 A20 A20 Name of agency creating current file Date of file creation Station name preferably identical to marker name in the associated Observation file Station number preveravbly identical to marker number in the associated Observation file Types of observ Number of different observation types stored in the file 16 9 4X A2 Observation types The follofing meteorological observation types are defined in RINEX Version 2 PR Pressure mbar TD Dry temperature deg Celsius HR Rekative humidity percent ZW Wet zenith path delay millimeters for WVR data The sequence of the types in this recor
244. tracking CH for the receiver channel numbers File naming recommendations format for hourly files format for 15 minute files The modifications have been accepted for LEO data used in the IGS LEO Pilot Project by the IGS LEO Working Group The modifications are only necessary for RINEX files containing LEO data Some of the modifications could be a valuable extension for ground based GPS data too We are looking for comments about the implementation of the modifications for ground based data Introduction The current RINEX Observation File definition does not fully accommodate data from low earth orbiters equipped with GPS or GPS GLONASS receivers The following deficiencies have been defined 1 The RINEX file should show the nature of the antenna marker receiver carrier that is if the receiver antenna are mounted on a satellite or another non typical marker 2 Antenna position w r to the center of mass should be stored 3 Antenna boresight in body fixed coordinate system has to be known 4 Attitude data It is proposed to put satellite attitude data into a separate file 5 Precision resolution of the data fields As the format is fixed that 1s F14 3 the resolution of 0 001 cycles 0 2 mm might not fulfill all future requirements 6 Some receivers track satellites on more than one antenna or assign more than one channel to the same satellite on the same or on different antennas The RINEX obs format does not allow f
245. ut to the primary directory on Oct 28 1997 will be placed in that primary directory Example 2 The corrected CPU GPS time indicates that the day is Sept 7 1997 the Use Ashtech Subdirectory Structure Checkbox is NOT checked and the Secondary Subdirectory is C GPSDATA GEO1 GBSS would place all of the data for every day in the following directory C GPSDATA GEO1 A 2 B E S and Trap File Naming Approach GBSS depends upon several sources of information when generating Ashtech file names The Ashtech files are named using the following naming convention tnnnnsyy ddd where t is the file type B E S or T nnnn is the 4 character station name S is the session code yy is the last two digits of the year and ddd is the day of the year 78 For example a file named BRK12C97 233 is an Ashtech B File for site RK12 taken in session C of day 233 of 1997 Using this convention GBSS creates the names of B E S and Trap Files The 4 character station name is obtained from the Configu ration Site Site Name menu see Section 3 1 3 1 The session code depends upon the File Duration parameter of the Con figuration File Outputs menu see Section 3 1 4 10 and upon the corrected CPU GPS time The corrected CPU GPS time is also used to determine the year and day of the year It should be clear that GBSS creates the file names based upon this corrected CPU GPS time of the computer not the receiver Howeve
246. utton and the text to the right of the button are only enabled when the Upload file to Receiver checkbox is checked and GBSS is in Active Mode It does not apply when GBSS is in its Passive Mode When enabled the text to the right of the Select File button describes the file currently selected for upload to the receiver on the next connection to a receiver To change the currently selected upload file press the Select File button and select the desired file from your hard drive Fig ure 3 5 provides an example of the file selection window that is displayed when an active Select File button is pressed Select File to Upload To Receiver Upon Connect Look im 69 MENTA 7 etc 9 Mamput C host news LIM y Installations HA lomg_nt E Pkware C i 1 Power 3 E perns 3 Pri_dir LO Marge E Program Files File name upload tst Files of type JA Files b Cancel Figure 3 5 Select File to Upload 17 The Upload file BEFORE requesting real time data checkbox allows you to specify whether or not the script file is uploaded before or after GBSS issues the real time data request commands The format of the upload file is described in Appendix B 3 1 2 7 Configuration Receiver Passive Mode Receiver Information The information within the area entitled Passive Mode Receiver Information 1s only editable and will only have meaning when GBSS is in Passive Mode see Section 3 1 2
247. val Header Y Clock adjustments in Code and Carrier Y Output Satellite List and Number of Observations Y Output Smoothed Codephase Y Output Site Hame Change Records Y o X comeet XYZ s of GPS Figure E 6 RINEX Header Data Edit Window 94 With the exception of the Output Data Type the data of each field comes from either the Site File or from the saved configura tion data of the program that is stored in the INI file of the program When the Site File is not used as input to the program all of the data for this window with the exception of the Output Data Type comes from the saved configuration data When the Site File 1s used as input the following fields come from that file Station Name Observer s Name Receiver Serial Number Antenna Serial Number l Antenna Offsets Slant Radius and Delta Vertical The Output Data Type field is used to specify which RINEX observation fields will be output to the RINEX Observation file The Output Data Type can be one of those listed in Table E 2 Table E 2 Output Data Types Selection Output Data Types L1 C A Carrier and Code includes Doppler L1CP L2P L1 C A El P Code and L2 P Code Carrier and Code includes Doppler CDPHASE L1 C A Codephase only L1CP L1 C A and L1 P Code Carrier and Code includes Doppler LIC L2P L1 C A and L2 P Code Carrier and Code includes Doppler It should be clear that some se
248. ve will flash The text to the right of the active indicator will either contain the words Within a Session as shown in the screen capture of Section 66 4 2 or Not Within a Session as shown in Figure 4 3 Logging Sessions Active HOT Within a Session Figure 4 3 Logging Sessions Status Bar GBSS changes the text according to the last epoch received from the receiver Whenever the current GPS time as determined from the last received epoch falls within a ogging session the text displayed shows the Within a Session state Conversely when a received epoch time falls outside of the logging sessions the text displayed shows the Not Within a Session state Please note the distinction between the epoch time and the current GPS time That is GBSS determines the state of the logging session status bar using the most recent epoch received from the receiver and not the current time of the GPS constellation Also notice that the text of the logging session status bar appears to use the term Session and not Logging Session the distinction is detailed in Section 3 1 5 However no inference to the term Session is implied That is when Within a Session or NOT Within a Session is displayed it is meant to imply that the data received falls inside or outside of respectively a logging ses sion 4 3 Status and Display Sub Windows GBSS provides the following sub windows that can be displayed while connected to a
249. y while the terminal window is active unless you issue the command using this window to stop the receiver from sending epoch data Also if the Trap File capability is enabled see Section 3 1 4 5 all bytes received from the receiver will be output to the Trap File Finally this window is a lower priority than the tasks that handle the actual data received from the receiver As a result when receiving data from a receiver configured to output epoch data frequently say an epoch interval of 2 seconds or less and depending on the speed of your computer the update of this display may appear sporadic and may appear as if GBSS is loosing data However the display update is at a low priority and may depending upon the system load not have enough time to display all of the data 4 5 Uploading a Command File to the Receiver There are two separate points in the operation of GBSS where a command file may be uploaded to the receiver The first is when GBSS established the connection with the GPS receiver as described in Section 3 1 2 6 In the second case a command file may be sent by GBSS to the receiver at any time during data logging GBSS must be in its Active Mode This file can be used to provide the GPS receiver with information and configuration data that is specific to your particular needs at that time For example you can create a file that contains the commands necessary to cause the GPS receiver to start sending differential cor 74
250. ycles of carrier Code Units in meters Missing observations are written as 0 0 or blanks Loss of lock indicator LL Range 0 7 0 or blank OK or not known Bit 0 set Lost lock between previous and current observation cycle slip possible Bit 1 set Opposite wavelength factor to the one defined for the satellite by a previous WAVELENGTH FACT L1 2 line Valid for the current epoch only Valid for the current epoch onlyh Bit 2 set Observation under antispoofing may suffer from increased noise Bits 0 and 1 for pahse only Signal stength projected into interval 1 9 1 minimum possible signal strength 5 tthreshold for good S N ratio 9 maximum possible signal sgtrength 0 or blank not known don t care 112 Table F3 Navigation Message File Header Section Description Header Label Coumns 61 80 Description Format RINEX VERSION TYPE Format Version 2 16 14X File type ONT for Navigation data A1 19X PGM RUN BY DATE Name of program creating current file A20 Name of agency creating current file A20 Date of file creation A20 COMMENT Comment line s A60 ION ALPHA Ionosphere parameters A0 A3 of almanac page 18 of subframe 4 2X 4D12 4 ION BETA Ionosphere parameters BO B3 of almanad 2X 4D12 4 DELTA UTC A0 A1 T W Almanac parameters to compute time in UTC page 18 of subframe 4 3X 2D19 12 A0 A1 Terems of polynomial 219 T Reference time for UTC data W UTS reference week number Continuous

User`s Manual V 3.2.0

Contents

Download Pdf Manuals

Related Search

Related Contents