![Dynalab NX Series Скачать руководство пользователя страница 19](http://html.mh-extra.com/html/dynalab/nx-series/nx-series_user-manual_2547775019.webp)
Dynalab Test Systems
NX Tester User’s Guide
17
Copyright 2011
Revised 04/27/2011
CONFIGURATION
>RESTRICTIONS
DIAGNOSTICS
AUTOLEARN
RESTRICTIONS
>FILE ACCESS
FILE MODE
RESTRICTIONS
>FILE ACCESS
FILE MODE
FILE ACCESS
>*NO RESTRICTION
SUP KEY REQUIRED
RESTRICTIONS
FILE SELECTION
>FILE MODE
FILE MODE
>*MULTIPLE FILES
ONE FILE
ONE-DELETE ON END
Erase all files
Except the currently
Selected file ?
GREEN=YES RED=NO
RESTRICTIONS
The RESTRICTIONS function is accessible from the SETUP menu as shown above. Two selections are
available.
FILE ACCESS
This function is used to restrict (or un-restrict) access to the program SELECT menu based on the
presence of the Supervisor Key. Use the Up/Down Arrow buttons to select NO RESTRICTION if
access to the SELECT menu is unrestricted, or to select SUP KEY REQUIRED if access to the SELECT
menu is to be restricted based upon the presence of the Supervisor Key. Press the Green button to
confirm the selection. Press the Red button to exit.
FILE MODE
By default, the NX Tester can store as many program files as can fit into its 1.3Mb of program storage
area. This corresponds to the MULTIPLE FILES selection.
In some cases, it may be desirable to allow the NX Tester to store only one test program at a time. To
enable this capability, select ONE FILE in the FILE MODE menu. Press the Green button to confirm
the selection. If ENABLED, after pressing the Red button to exit, if there is more than one program
currently on the NX Tester, the following screen will appear:
Upon pressing the Green button, the NX Tester will delete all files except the currently selected file, and
will place the NX Tester into One File Mode. Upon pressing the Red button, the NX Tester will delete
no files, and the One File Mode will remain DISABLED.
The selection labeled ONE-DELETE ON END is similar to the ONE FILE mode, with the additional
feature of automatically deleting the program file after execution, providing that the program reaches a
END workflow item. This may be useful in conjunction with using the NX Server as source of all
program files, ensuring that program files are only available from the NX Server.