LeCroy 6000 SERIES, Руководство оператора, Страница: 285 / 409

WR6K-OM-E Rev A ISSUED: October 2003
283
to show several versions of a function at the same time, without having to set up a separate script
for each one.
If your program structure is complicated, consider typing all the IFs, ELSEIFs, ENDIFs, FORs,
NEXTs, etc and then clicking Apply. You wont get any output, but the system will tell you if the
structure is acceptable. Then you can insert the actual program statements.
Always try to make the script as independent as possible of variables such as V/Div, T/Div, and
memory length, unless that would make it harder to understand. If so, give some values as
examples, and explain how the script would have to change if the variables changed.
ERRORS
The instrument VBS tries hard to help you when errors occur.
Errors may be of two main types:
•
The script may not be usable because the interpreter cannot construct a logical structure
from it.
•
The script may be usable, but may fail while running because an incomputable function has
been requested.
Sometimes the line number given for an error is wrong. This can happen when the error is of this
general type:
Missing "Next" Missing "End If"
Extra "Next" Missing "Until" etc.
This happens because VBS cannot know where you should have put the statement.
If at some point during the calculation of an output array, a value goes outside the allowed range,
the calculation will stop, and you will see the new values up to the point of the stoppage. To the
right of that point, the trace will display the previous values. In fact, if you deliberately recalculate
only a part of a trace, you can have a mixture of new and old values.
In the figure below is a type of error message that you may see if one of your calculations has
tried to set a value outside the range -32768 to +32767. It takes extra time to guard against this,
but unless you are sure that it will not happen, you need some kind of check. In the example on
the next page, the red trace has gone outside the allowed range at the beginning, resulting in the
message at the bottom of the instrument screen: This array is fixed or temporarily locked:
OutResult.DataArray
.