YSI Data Scout Advanced - Manual (Page 49)

YSI Incorporated Data Scout Advanced 45
On the right side of the Edit Tests window, below the four parameters tab, there may be several different special buttons visible,
depending on the state of the selected test.
If the selected test is Active then a single button labeled End Active Test is visible. In this Active state, the only test parameter that can
be changed via the editing process is the End Time of the test. All other parameters are dim and unchangeable. The End Active Test
button is simply a shortcut for setting the End Time to a relative zero value. Clicking the button causes the Time tab to be displayed (if
not already displayed) and its End Time fields are all changed to “pink” as an indication that they have been set to this new edited
value. Select the Send button to transmit this edit change to the transducer(s).
If the selected test is Pending then a single button labeled Begin Pending Test is visible. In this Pending state, the only test parameters
that can be changed via the editing process are the Begin Time and End Time of the test. All other parameters are dim and
unchangeable. The Begin Pending Test button is a shortcut for setting the Begin Time to a relative zero value (0_0:0:0 days_hr: min:
sec). Clicking the button causes the Time tab to be displayed and its Begin Time fields to be changed to “pink” as an indication that
they have been set to this new edited value. Select the Send button to transmit this edit change to the transducer(s). If another test is
Active, pressing this button may cause that Active test to end. If several tests are Pending, only force the “next” test in sequence to start.
If the selected test is in any state other then Pending or Active, then two buttons labeled Get and Put are visible. These buttons are
particularly useful if the test is currently Vacant or Idle and in the in the process of being created. The Put button may be used to save
the current test’s parameters (as is, in original or edited state) to any file in the Data Scout Advanced Ini subfolder. A dialog box opens
to allow the user to save a named test scenario (.tst) file. Later, the user can use the Get button to retrieve a named test scenario file
and substitute it as the current “edited” state of any other test. Clicking Get causes all of the selected file’s substituted test parameters
to be set “pink” to indicate they have been modified. These buttons allow the user to share tests or test fragments between different
transducers. Click the Send button to transmit these edit changes to the transducer(s).
Any or all modified (pink) test parameters are saved only when the Send button is selected. The Exit button will allow the user to
cancel all changes made.
Normally, only changed (pink) test parameters are written back to the highlighted transducer when Send is selected. However, the
Apply To frame (in lower right corner) has an alternate selection allowing the user to broadcast these Test Edit changes to all other
transducers assigned to the Run window (for the same corresponding test number only). This can be a time-saving feature in some
situations.
If any pre-programmed Level Scout(s), which have been loaded with tests, are disconnected from the PC and Data Scout Advanced,
their special AutoLog hardware feature will continue to autonomously “log” (acquire and record) data as programmed as long each
transducer has enough non-volatile memory space available and enough battery power to keep it running. Multiple tests can be
scheduled concurrently. If any test’s begin/end times overlap another’s times you are warned and allowed to abort such changes or you
may choose to proceed anyway. If you allow tests with overlapped times to continue, the starting of a new pending test will terminate any
other test already active. Later, the transducer(s) may be reconnected to Data Scout Advanced. Then, you may Extract (read) the
autonomously “logged” data scans from the transducer(s), and store them as data files on the PC per the instructions in the next
section.