7½ Digit Graphical Sampling Multimeter Reference Manual  Section 9: 
Frequently asked questions (FAQs) 
 
DMM7510-901-01 Rev. B / May 2015  9-9 
 
What is a configuration list? 
A configuration list is a list of stored instrument settings. You can restore these instrument settings to 
change the active state of the instrument. Configuration lists allow you to record the active state of the 
instrument, store it, and then return the instrument to that state as needed. 
If you are using TSP, configuration lists run faster than a script that is set up to configure the same 
settings. 
The Model DMM7510 supports measure configuration lists, making it possible to sequence through 
defined measure settings. 
Each configuration list consists of a list of configuration indexes. A configuration index contains all 
instrument measure settings that were active at a specific point. You can cycle through the 
configuration indexes using a trigger model. 
For more detail, see Configuration lists (on page 3-37
). 
 
Why do I keep seeing the "Undefined header" error? 
When you are using the SCPI command language, you may see the –113, "Undefined header," error. 
This error indicates that what you sent to the instrument did not contain a recognizable command 
name. The most likely causes for this are: 
•  A missing space between the command and its parameter. There must be one or more spaces 
between the command and its parameter. For example, 
:disp:volt:digits5 
The correct entry is 
:disp:volt:digits 5 
•  Incorrect short or long form. Check the SCPI command reference (on page 6-1) documentation 
for the correct command name. 
•  Spaces in the command name. You cannot use spaces in the command name. For example: 
syst: err? 
The correct entry is: 
:syst:err? 
 
Why do I see the "Query interrupted" error? 
This error occurs when you have sent a valid query to the instrument, then send it another command 
or query or a Group Execute Trigger (GET) before it has had a chance to send the entire response 
message (including the line-feed/EOI terminator). The most likely causes are: 
•  Sending a query to the instrument and then sending another command or query before reading 
the response to the first query. For example, the following sequence of commands causes an 
error -410: 
syst:err? 
*opc? 
 
You must read the response to syst:err? before sending another command or query. 
•  Incorrectly configured IEEE 488 driver. The driver must be configured so that when talking on the 
bus it sends line-feed with EOI as the terminator, and when listening on the bus it expects line-
feed with EOI as the terminator. See the reference manual for your particular IEEE 488 interface.