Section 7: Introduction to TSP operation
Model 2450 Interactive SourceMeter® Instrument Reference Manual
7-38
2450-901-01 Rev. B/September 2013
13. In the Storage area of the Script Attributes tab, select
Volatile
or
Non-volatile
. For products that
support autorun scripts, if you select Non-volatile, you can select
Auto Run
to have the script run
automatically when the instrument is turned on.
Note that all scripts are initially stored in the instrument's volatile memory and are lost if you turn
the instrument power off and then on again. If you want to keep the script on the instrument
through a power cycle, select
Non-volatile
storage.
14. In the Debug area of the Script Attributes tab, you can select
Generate Debug File
. When you
select this option, a Debug subfolder is created in your test folder, and a file with a
.DBG
extension is created in that folder. Note that this is a feature of the Eclipse platform, and you will
not use this file to debug your script. It simply contains all the scripts in your run configuration, so
that you can see them together in the order in which they will load.
15. Click
Close
or
Run
. The run configuration is added to the run configurations list.
To run the last used run configuration, click the
Run
icon in the main TSB toolbar. To run a
different run configuration, right-click in the script editor area and select
Run As > Run
Configurations
. Select a different run configuration, and then click
Run
in the Run Configurations
dialog box.
Memory considerations for the run-time environment
The Model 2450 reserves 32 MB of memory for dynamic run-time use.
Note that the run-time environment includes user-created reading buffers and active sweep
configurations. The amount of memory used by a reading buffer is approximately 30 bytes for each
reading.
For example, assume two reading buffers were created. One of them was created to store up to
1,000 readings and the other to store up to 2,500 readings. The memory reserved for the reading
buffers is calculated as follows:
(1000 * 30) + (2500 * 30) = 105,000 bytes or 105 kilobytes
Reading buffers for remote nodes consume memory on the remote node, not the local node.
The amount of memory used by a sweep configuration is based on the number of source points. The
actual memory consumption can vary greatly depending on how often the source-measure unit
(SMU) take readings during the sweep, but as a general rule, each source point can be expected to
consume at least 24 bytes.
It is possible for the memory used for the run-time environment, sweep configuration and reading
buffers to exceed 32 MB. When this occurs, there is a risk that memory allocation errors will occur
and commands will not be executed as expected.
If the instrument encounters memory allocation errors when the memory used is above 95 percent,
the state of the instrument cannot be guaranteed. After attempting to save any important data, turn
off power to the instrument and turn it back on to reset the run-time environment and return the
instrument to a known state. Unsaved scripts and reading buffers will be lost.