Table of Contents
Advertisement
NOTE:
Most valid commands do not echo a response to a command input; the indication that they have been
accepted is a return of the port prompt from the GPSCard. VERSION, HELP and ? are the only commands that do
provide a data response other than the port prompt.
The LOCKOUT and SETHEALTH commands are not for use with GLONASS satellites.
Example:
An example of no echo response to an input command is the ASSIGN command. It can be entered as follows:
COM1>assign 4 120043[Return]
COM1>
The above example illustrates command input to the MiLLennium-GLONASS GPSCard's COM1 port which will
cause the card to assign the satellite with frequency 12 and slot number 43 to channel 14. However, your only
confirmation that the command was actually accepted is the return of the COM1> prompt.
If a command is incorrectly entered, the GPSCard will respond with "Invalid Command Name" (or a more detailed
error message) followed by the port prompt.
After initially turning on the MiLLennium-GLONASS GPSCard, you may find the following logs useful for
observing the MiLLennium-GLONASS GPSCard's activities. While GPSolution is the easiest way to do this, you
can also use DOS or a Windows-based communications program; examples of both are provided below.
•
Use the RCCA log to list the default command settings. The RCCA log is useful for
indicating status of all current command settings. Displaying the RCCA log after a RESET
will show the saved configuration (Refer to the description of the SAVECONFIG command
in the MiLLennium Command Descriptions Manual for more information).
•
Use the ETSA log to monitor the channel tracking status.
•
Use the SATA log to observe the satellite specific data.
•
Use the POSA log to observe the current computed position solutions.
•
Use the DOPA log to monitor the dilution of precision of the current satellite constellation.
•
Use the RVSA log to monitor the receiver status.
•
Use the HELP command to list all available commands.
•
Use the HELP LOG command to list all available logs.
Refer to the MiLLennium Command Descriptions Manual for procedures and explanations related to data logging.
4.3.2 DOS
One way to initiate multiple commands and logging from the GPSCard is to create DOS boot-up command files
relating to specific functions. This will save time when you want to duplicate test situations and minimize set-up
time. Any convenient text editor can be used to create command text files.
Example:
For this example, consider a situation where a PC's appropriately-configured COM1 port is connected to the
GPSCard's COM1 port, and where a remote terminal is connected to the GPSCard's COM2 port. The PC user
wishes to monitor the GPSCard's activity; the following command file could be used to do this.
1.
Open a text editor on the PC and type in the following command sequences:
log com2 sata ontime 15
log com2 etsa ontime 15
log com2 rvsa ontime 60 5
log com2 posa ontime 15
log com2 dopa ontime 15
2.
Save this with a convenient file name (e.g. C:\GPS\BOOT1.TXT) and exit the text editor.
3.
Use the DOS copy command to direct the contents of the BOOT1.TXT file to the PC's COM1 port:
C:\GPS>copy boot1.txt com1
1 files(s) copied
GPS/GLONASS Receiver User Manual Rev 1
4 Operation
27
Advertisement
Table of Contents
