Topcon PC-CDU - Running Scripts from Windows Explorer

83
%%set,dev/ser/@1/rate,9600
%%set,/par/pos/mode/cur,cd
%%em,,/msg/nmea/GGA:1
@exit
After these lines are saved to a file (e.g., beacon.jpc), you then can type in the command line:
@beacon and press Enter to instruct the receiver to input RTCM corrections from serial port C and
output NMEA messages to the current terminal. If one wants to use serial port B for inputting cor-
rections, type @beacon b and press Enter.
The following example illustrates how the goto command and labels are used in scripts intended for
work with different receiver models.
%/par/rcv/model%print,/par/rcv/model
@goto Is@0
@echo Unknown receiver model.
@stop
@:IsOdyssey
@echo Receiver is Odyssey!
@goto end
@:IsLegacy
@echo Receiver is Legacy!
@goto end
@:IsEurocard
@echo Receiver is Eurocard!
@:end
@stop
Running scripts from Windows Explorer
Files with the extension .jpc are automatically associated with PC-CDU. It means that you can
launch PC-CDU (specifically in Manual mode) by clicking on a script in the file/directory tree. It
can be achieved with the use of Windows Explorer, My Computer or some other Windows file man-
ager. After the Connection Parameters dialog box pops up, you press the Connect button
to open PC-CDU’s Manual Mode window. Note, however, that the script you selected will not
start automatically so that you should type the name of desired script in the command line or select
the script through the Load script button. After exiting manual mode, you can continue working
with PC-CDU in the usual way.