The scriptVar.save() command saves the script to nonvolatile memory, which makes the
change persistent through a power cycle. See Save a user script to nonvolatile memory (on page
8-10) for more detail.
Example: Set a script to run automatically
Assume a script named test5 is in the runtime environment.
The next time the instrument is turned on, test5 script automatically loads and runs.
Working with scripts in nonvolatile memory
The Fundamentals of scripting for TSP (on page 8-1) section in this manual describes working with
scripts, primarily in the runtime environment. You can also work with scripts in nonvolatile memory.
The runtime environment and nonvolatile memory are separate storage areas in the instrument. The
information in the runtime environment is lost when the instrument is turned off. The nonvolatile
memory remains intact when the instrument is turned off. When the instrument is turned on,
information in nonvolatile memory is loaded into the runtime environment.
Save a user script
You can save scripts to nonvolatile memory using commands or TSB Embedded.
Only named scripts can be saved to nonvolatile memory. The anonymous script must be named
before it can be saved to nonvolatile memory.
If a script is not saved to nonvolatile memory, the script is lost when the instrument is turned off.
To save a script to nonvolatile memory from a remote interface:
1. Create and load a named script (see Create and load a script (on page 8-3)).
2. Send the command scriptVar.save(), where scriptVar is the name of the script.
To save a script to nonvolatile memory using TSB Embedded:
Select Save Script.
Example: Save a user script to nonvolatile memory
To Next Page
Loading...
Need help?
General
