EasyManua.ls Logo

Topcon PC-CDU - Receiver Commands

Topcon PC-CDU
96 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
82
>a text
Example 2:
Assign the current terminal's baud rate to @2:
%%print,/par/cur/term/rate
@set @2 @0
sleep integer number of milliseconds PC-CDU interrupts script execution for specified time interval.
stop Stops script execution.
stoponerrors on
off
Enables/disables PC-CDU'
stop-on-error
option. This indicates
whether PC-CDU will stop script execution after getting an
ERxxx message from the receiver. Default is 'on'.
timeout integer value in milliseconds,
default is 5000
If a receiver command starts with a '%' symbol, PC-CDU will
wait for the receiver to reply within the specified 'timeout'
interval. If a reply is received during this time, it will be
saved to the variable @0.
If no reply is received over the timeout interval, or if after
receiving a few bytes PC-CDU gets no more data for 100+
milliseconds, or if PC-CDU keeps receiving "continuous data"
for more than 100 milliseconds, @0 will be undefined (how-
ever, script execution will continue).
In this you may need to adjust the timeout interval to be
sure that the variable @0 contains correct information.
Receiver commands
Using scripts one can specify receiver commands’ arguments either explicitly or through variables.
When you use variables for this purpose, these will be substituted by PC-CDU for some specific val-
ues before sending the corresponding command to the receiver. If the user sends a receiver com-
mand that starts with '%' (command label), PC-CDU will wait for the receiver to reply and, if a reply
is received, it will save the reply to the variable @0.
Currently the character '@' is used in GRIL commands only to delimit the command checksum. It
should not cause any problems since PC-CDU automatically adds a checksum for every command
sent to the receiver.
PC-CDU
does not interpret
receiver commands. Therefore, if one uses receiver commands that
change the baud rate and/or handshaking for the current receiver port (that is the port to which
PC-CDU is connected), you should either use appropriate @set commands immediately after them,
as shown below:
%%set,/par/cur/term/rtscts,off (this governs the receiver port)
@set rtscts,off (this governs the computer port)
%%set,/par/cur/term/rate,9600 (this governs the receiver port)
@set rate,9600 (this governs the computer port),
or specify such receiver commands at the end of the script, immediately before @disconnect or
@exit. Otherwise, PC-CDU may be locked up waiting for the receiver to reply.
Below will be found some examples illustrating various applications of scripts.
The following script serves the purpose described in the article “Using the Coast Guard Beacon for
Differential Corrections”.
@default @1,c
%%set,dev/ser/@1/imode,rtcm

Table of Contents