7: TSP command reference Series 2600B System SourceMeter® Instrument
7-68 2600BS-901-01 Rev. B / May 2013
Example 2
"Test", "DUT1() beeper.beep(2, 500)",
display.SAVE)
Assume a script with a function named
“DUT1” has already been loaded into the
instrument, and the script has NOT been
saved in nonvolatile memory.
Now assume you want to add a test named
“Test” to the USER TESTS menu. You want
the test to run the function named “DUT1”
and sound the beeper. This example adds
“Test” to the menu, defines the code, and
then saves the displayName and code in
nonvolatile memory.
When “Test” is run from the front panel USER
TESTS menu, the function named “DUT1”
executes and the beeper beeps for two
seconds.
Now assume you turn off instrument power.
Because the script was not saved in
nonvolatile memory, the function named
“DUT1” is lost when you turn the instrument
on. When “Test” is again run from the front
panel, an error is generated because DUT1
no longer exists in the instrument as a
Example 3
display.loadmenu.add("Part1",
"testpart([[Part1]], 5.0)", display.SAVE)
Adds an entry called “Part1” to the front panel
“USER TESTS” load menu for the code
testpart([[Part1]], 5.0)
, and saves it
in nonvolatile memory.
Also see
display.loadmenu.delete() (on page 7-69)
display.loadmenu.catalog()
This function creates an iterator for the user menu items accessed using the LOAD key on the instrument front
panel.
Type TSP-Link accessible
Affected by Where saved Default value
Function No
Usage
for displayName in display.loadmenu.catalog() do body end
for displayName, code in display.loadmenu.catalog() do body end
The name displayed in the menu
The code associated with the
displayName
The body of the code to process the entries in the loop
Details
Each time through the loop, displayName and code will take on the values in the USER TESTS menu.
The instrument goes through the list in random order.
To Next Page
Loading...
Need help?
General
