DAZZLER
TM
system manual Part I : installation & operation 6.2
that the ”rename” operation is atomic (ie. unbreakable) across local area networks. The
implementation to post a request is thus done in two steps:
1. write a temporary file request.tmp. It does not matter if this write operation is inter-
rupted.
2. atomic operation: rename-file request.tmp request.txt.
The above also implies the underlying assumption that a single requestor process is active with
a given Dazzler.
6.2.3 Error handling
Please note that there is no ”error” or ”completion code” returned to the program having
issued the request. The GUI will post appropriate error reports in dialog windows expecting
an operator to be present. The activity will resume once the error is acknowledged unless the
remote requester ”times out”
5
. This unfriendly behavior is corrected in the network remote
protocol, instead of the “fire and forget” behaviour of the ”text file mode”, there is return
information from the Dazzler.
When a new waveform need be sent to the Dazzler, the user program can either generate a
new request.txt with a path to another wave text file, or modify the wave text file and issue
again the same request.txt file. The adequate wave text file can either be generated from the
Dazzler program using the save as menu option or directly written by the user remote control
program.
6.2.4 File C:/dazzler/paths.txt
The file c:\data\paths.txt is a leftover (relict) from early use of the Dazzler in network
configurations. This file is now only an indicator for two paths used by the last Dazzler GUI
having changed its remote enable status. The first two records are set to the ’default directory’
, the third indicates the parameters path: essential for bug reports !. This file resides in
c:\dazzler. Having a single location prevents to use it in two dazzler installations.
6.2.5 Star commands
In the request.txt file, the wave path may be followed by a list of “star” commands
to be performed before the processing of GUI controls. These lines follow the format:
*Command [value]. The main purpose of these “star” commands is to operate the buttons
and other controls which are not accessible by the controls allowed in wave text files. The
commands themselves are not case sensitive
6
.
5
It is not easy to investigate a fault when request.txt has just been deleted! The trick is to disable remote
from the GUI: then request.txt will remain.
6
but for boolean values where lower case ’t’ is the only way to obtain a True value for *cont...
V3.00 - 8
th
April 2019 (ContentsTable) (FiguresTable) 64/94
To Next Page
Loading...
Need help?
General