Download GNSS Receiver External Interface Specification

Chapter 2
RECEIVER INPUT LANGUAGE
This chapter describes the syntax and semantics of the receiver input language. We
begin with some examples to give the reader a feeling of the language, then turn to
detailed syntax definition, and then describe all the defined commands along with their
semantics.
2.1 Language Examples
Here are a few examples of real statements receiver understands along with receiver
replies. You will find more examples of using particular commands in corresponding
subsections. The input to the receiver is marked with the ⇒ character, while receiver
output is marked with the ⇐ character:
Example:
Ask receiver to print its electronic ID. Receiver generates the reply message shown:
⇒ print,/par/rcv/id<CR>
⇐ RE00C QP01234TR45<CR><LF>
Example:
Ask receiver to set the baud rate of its serial port A to 9600. Receiver successfully executes the command and doesn’t generate any reply.
⇒ set,/par/dev/ser/a/rate,9600<LF>
Example:
Use the same command as in the previous example, but force receiver to generate reply
by means of using the statement identifier.
⇒ %set_rate%set,/par/dev/ser/a/rate,9600<LF>
⇐ RE00A%set_rate%<CR><LF>
Example:
Try to set too high baud rate. Receiver replies with the error message even though we
used no statement identifier.
⇒ set,/par/dev/ser/a/rate,1000000<LF>
⇐ ER016{4,value out of range}<CR><LF>
z
Note:
GREIS
Receiver always puts its normal and error replies into two standard messages, [RE] and[ER],
respectively. For more information on the format of GREIS messages, refer to “General Format
of Messages” on page 280. The [RE] and [ER] messages themselves are described in “Interactive
Messages” on page 320.
www.javad.com
23