Keithley SourceMeter 2600 Series Reference Manual page 96

2-44 TSP Programming Fundamentals
Saving a user script
A created and loaded script does not have to be saved in non-volatile memory of
the Series 2600 before it can be run. However, an unsaved script will be lost when
the Series 2600 is turned off.
Saving a named script
Only a named script can be saved in non-volatile memory of the Series 2600. After
creating and loading a named script, use one of the following commands to save it.
myscript.save()
myscript.save("name")
where:
Either of the above save commands will save the script in non-volatile memory. If a
script is not saved in non-volatile memory, the script will be lost when the Series
2600 is turned off.
The
myscript.save()
originally created and loaded. The
used to save the script under a different name. If you save the script to a name
that already exists in non-volatile memory, it will be overwritten.
Examples:
1.
2.
Running a user script
Running an unnamed script
There can only be one unnamed script in the run-time environment. If another
unnamed script is created and loaded, the previous unnamed script will be
removed from the run-time environment. Use one of the following commands to
execute the chunk of the last loaded unnamed script. Both commands perform the
same operation.
run()
script.run()
2600S-901-01 Rev. A / May 2006
Series 2600 System SourceMeters Reference Manual
is the user-defined name of the script.
myscript
is a new name for the script that is assigned by the user. Using this
name
function is equivalent to the "Save As" file menu item in the Test Script
Builder.
command saves the script under the name that it was
Assume a script named "test1" has been created and loaded. The following
command saves the script in non-volatile memory:
test1.save()
To save the script named "test1" under a new name ("test2") in non-volatile
memory, send the following command:
test1.save(test2)
Return to
myscript.save("name")
Section 2 topics
shell command is