Geodetic Base Station Software (GBSS™)

1. Geodetic Base Station Software (GBSS™) GBSS Training

2. May 2002 Basic Agenda • Purpose of GBSS • GBSS Program Configurations • Installation and Un-installs • General and Detailed Program Use • Miscellaneous Topics

3. May 2002 Purpose of GBSS • Continuous logging of GPS Data • Multitasking/Multithreaded (i.e., can be run in concert with other programs on the computer) • Can operate in concert with FTP, WWW or BBS systems.

4. May 2002 High-Level Features • Windows 9x/NT interface • Logs data in up to 4 directories simultaneously • Provides PKZIP or PKZIPC compression • Can generate both single-frequency and dual- frequency data files from a single dual-frequency receiver • Logged data accessible via other software (e.g., FTP, WWW, and BBS) • Full user control over file closures • Terminal window • Can be configured to automatically connect on boot-up

5. May 2002 GBSS logs data from any Thales reference receiver to a PC One copy of GBSS controls only one reference receiver PC must be co-located with receiver Micro-Manager Pro controls only MicroZ-CGRS receivers Micro-Manager Pro controls multiple uZ-CGRS receivers Receiver(s) may be remotely controlled via a modem GBSS vs. Micro-Manager™ Pro SW

6. May 2002 Installation • Installation follows normal software installation procedures • Run “Setup.exe” • Follow remaining instructions • Software “Uninstalled” using normal uninstall procedures

7. May 2002 Installation Procedures(continued) • After installation, choose the option to reboot. • Failure to reboot may lock your computer if you attempt to run GBSS (sentinel drivers not fully installed) • Rebooting allows the sentinel drivers to be fully installed

8. May 2002 Installation Procedures(continued) • Attach the Software Sentinel to the Parallel Port. • Install as close to the computer as possible.

9. May 2002 Windows 95 Specific Installations • Why? • GBSS uses MS-DOS version of PKZIP (temporarily) and the MS-DOS Window created by GBSS does not close when zipping has completed. • How to Fix • When the first MS-DOS window for PKZIP appears, use the Properties button to set the “Close on exit” checkbox of the “Program” Tab. • What does this do? • Creates a PIF file in the directory pointed to by your “TEMP” environment variable.

10. May 2002 Windows NT Specific Installations • Only Needed When using the Auto-Connect Feature • Why? • Windows NT requires someone to logon in order for Windows to start. • Windows Plug-and-Play feature may misinterpret a powered Thales receiver as a serial mouse. • How to Fix (Logon issue) • Modify Registry to remove Login requirement (detailed in Manual) • How to Fix (Plug-and-Play issue) • Modify BOOT.INI with “/NoSerialMice” (See User’s Manual for details)

11. May 2002 Uninstall Procedure • Follow Normal Uninstall Procedures • From “My Computer” Select “Control Panel” • From “Control Panel” Select “Add/Remove Programs” • Select the item related to GBSS and then press the “Add/Remove” button. • Follow remaining instructions.

12. May 2002 Program Use Topics • Configuring GBSS • Connecting to and Disconnecting from a Receiver • Display Windows • Terminal Window • Simulation/Playback • Uploading a File to the Receiver

13. May 2002 Configuration Menus • Configuration Menus are Active (i.e., allow editing) only when not connected to a receiver (i.e., all setup must occur prior to connecting to the receiver). • Menus • Comms • Receiver • Site • Other Options • GPS Time

14. May 2002 Configuration Menus(continued) • All editing on the menus accepted by pressing the “OK” button. • All edited values are discarded, without warning, when the “Cancel” button or the “X” button (to close the window) is pressed.

15. May 2002 Communication Configuration • Choose correct port • Configure as shown for MicroZ CGRS

16. May 2002 Configure Receiver

17. May 2002 Configure Receiver • Active Mode vs. Passive Mode • Active Mode Controls • Command Recording Interval and Elevation Mask • Disable Receiver Storage of Data • Upload Site Data • Upload File (Uploaded when connection) • Passive Mode Information • Receive Type • Channel and Nav. Version

18. May 2002 Site Configuration

19. May 2002 Configure Site Menu • Site name used in B, E, S, and T-File naming (need legal DOS characters, ‘?’ characters translated to ‘_’) • File naming convention detailed in the User’s Manual • All coordinates translated to Lat, Lon, and Ht • If site data is to be uploaded to receiver (as per Receiver Configuration Menu), zero values of Lat, Lon, and Ht will not be sent to the receiver.

20. May 2002 Output Files Configuration • Menu Layout • 5 Tabs • File Modes • Data Files • Compression Files • NMEA Capture File • RSIM Capture File • “Other File Output Options” - Apply Across All Tabbed Areas

21. May 2002 File Modes • GBSS 3.2 supports RINEX 2.2 long file names for sessions shorter than 1 hour

22. May 2002 File Output Configuration • Data Files Tab • Output Directories • Primary Data Directory • Secondary Data Directory • Selection of File Types • Primary vs. Secondary • B, E, and S-Files (S-File information comes from site configuration menu) • L1 Only B, E, and S-Files • Ion File • Trap File

23. May 2002 File Output Configuration (Continued)

24. May 2002 RINEX Configuration • Set up RINEX Options and Headers

25. May 2002 RINEX Configuration (Continued)

26. May 2002 Other RINEX Options Set Within Converter Program (XYZAshRX) • Start XYZAshRx manually • Set Options • Close Program • Future runs will use new settings

27. May 2002 RINEX Output Data Types Options

28. May 2002 File Output Configuration (Continued) • What is a Trap File? • A collection of raw (i.e., uninterrupted) bytes received from the receiver. • Can be played back through GBSS in Playback or Simulation Modes. • The bytes are written before they are interpreted. That is, when File Duration option is used, the beginning and end of each trap file does not necessarily coincide with B, E, and S-Files • Why a Trap File? • You can later play back a trap file with different GBSS parameters. For example, if the receiver is set to output data at 1 Hz. and GBSS is configured to filter the epoch data to 5 seconds, then one can playback the trap file with a different epoch filter rate.

29. May 2002 File Output Configuration (Continued)

30. May 2002 File Output Configuration (Continued) • Compression Files Tab • Output Directories • Primary Compression Directory • Secondary Compression Directory • Selection of File Types • Primary V. Secondary • Types only enabled when associated selection made in Data Files Tab • Uses PKZIP 2.04g or PK250DOS or PKZIPC at the end of the File Duration

31. May 2002 File Output Configuration (Continued)

32. May 2002 File Output Configuration (Continued) • NMEA Capture File Tab • Allows Selection of a File in Which to Place Captured NMEA Messages • One Selects Messages, when captured, to be Written to the Capture File • GBSS Does NOT Issue the Commands to Start NMEA Message Transmission (you can use the terminal window)

33. May 2002 Other File Output Options

34. May 2002 Other File Output Options • Some users require 0.5 or 0.25 hours file duration • Set file re-open rate to 60 sec • May filter to another rate if used at RTK broadcast site • Receiver will be running at 1 Hz • Delete files older than X days (for example 5) • Use Ashtech subdirectory structure for automatic directory naming

35. May 2002 Other Options Configuration Menu • Verbose Diagnostic Messages (displayed in the diagnostic messages window) • Writing Diagnostic Messages to A File • Log File (naming convention in User’s Manual) • Playing Sounds • Warning Sound and Yellow Icon Flash • Occurs when more than 4% of the bytes are unrecognized over a sustained period. • Alert Sound and Red Icon Flash • Occurs when more than 30% of the bytes are unrecognized over a sustained period OR the RS-232 status line changes (e.g., the RS-232 line is disconnected)

36. May 2002 GPS Time Configuration • Check “Use receiver timetag” Option

37. May 2002 Configuring GBSS for Auto-Startup • Rationale: To have GBSS automatically connect and start logging should the computer be restarted (e.g., power failure) • Windows NT Platforms Need Registry edit • Placing GBSS in Start-Up Folder • Setting the Delay • Hardware drivers need to be completely initialized, the delay ensures they initialize before GBSS tries to access them. • e.g., C:\Program Files\Ashtech\GBSS\GBSS -C 45

38. May 2002 Connect/Disconnect • Connect To Receiver by Selecting “File | Connect” • Playback Trap Files (Simulating a Connection to the Receiver) by Selecting “File | Simulation” • Disconnect from Receiver by Selecting “File | Disconnect”

39. May 2002 Display Windows • Display Windows Are Updated Only When Connected to a Receiver • Display Window Types • Main Window • Geodetic Position Window • Earth-Centered Earth-Fixed Position Window • Channel Summary Window • Diagnostic Message Window • Logging Summary Window • Time Display Window • All Windows Moveable and Sizable • Display Sub-Windows can be restored to original size

40. May 2002 Main Display Window • Epoch Counters • Broadcast Message Counters • Error Counters • Available Disk Space • RS-232 Line Status Indicators • Logging Status Icon • Connect Status • Epoch Time Display • Sub-Window Display Area

41. May 2002 Main Display Window

42. May 2002 Geodetic Position Window • Upper Part Displays the Epoch Position • Lower Part Displays the WGS-84 Reference Position • From Site Configuration Menu OR • Receiver Output as Reference Position

43. May 2002 Earth-Centered Earth-Fixed Position Window • Upper Part Displays the Epoch Position • Lower Part Displays the WGS-84 Reference Position • Site Configuration Menu OR • Receiver Output as Reference Position • When all Lat, Lon or Ht positions not entered, position displayed will be “Partial”.

44. May 2002 Channel Summary Window • Shows Status Information Based Upon Channel Index • Satellite PRN • L1 C/A Signal-to-Noise • P1 Signal-to-Noise • P2 Signal-to-Noise • Satellite Elevation and Azimuth • Nav. Age (how many minutes past since nav. message for satellite)

45. May 2002 Diagnostic Message Window • Displays diagnostic messages as they occur • Messages Preceded by [number] indicate the seconds of GPS week when the event occurred • Verboseness depends upon value set in “Other Options” Configuration • Most messages written verbatim to the LOG file (when enabled).

46. May 2002 Logging Summary Window • Current Primary and Secondary Output Data (not compression) Directories • Output files -- color coded with directories to show relationships • When last interruption occurred and the number of interruptions • Information on each interruption is written to the LOG file when enabled • The number of interruptions (and the time of the last interruption) can be reset by pressing “Reset” button

47. May 2002 Time Display Window • Lower Priority Window (i.e., depending upon system load, update of this window may not appear smooth). • GPS Time Shown in Gregorian Format (not to be confused with UTC). • Raw CPU Time Displayed • Local Time Displayed (GPS Time - Zone)

48. May 2002 Terminal Window • Used to allow Commands to Be entered • No need to add the <CR><LF> sequence to commands -- GBSS automatically adds them • Terminal Window Shown Whenever a File is Uploaded to Receiver • Uploaded data shown in the upper display area • Receiver responses shown in the lower display area.

49. May 2002 Simulation and Playback Modes • Use “File | Simulation” or “File | Playback” • Playback mode allows GBSS to convert the Trap file quickly • Simulation mode allows the user to alter the simulation speed • In both modes, GBSS acts as if it were actually connected to a receiver (with the exception of adjusting its CPU to GPS time offset) • Simulation or Playback terminated when end of data reached, user selects “File | Disconnect”, or user terminates the program • Files are named based only upon Raw CPU clock (never related to time stamps within the data)

50. May 2002 Uploading Files To Receiver • Before Receiver Actually Starts To Send Data (i.e., upon establishing a connection) • This file is specified in the Receiver Configuration Menu and is uploaded each time connection is established • During Actual Data Logging • User Selects “File | Upload File” • GBSS Must be in Active Mode