05-13-2009 06:22 AM - edited 05-13-2009 06:23 AM
Hi,
I am using the IVI Scope Class in TestStand 4.1.1 to do multiple measurements within a short time.
After the first measurement the scope beeps and writes out the message: "measurement already selected" with each measurement.
Sure the message is right because it is the same measurement setting, but this message slows down the measurement by 30%.
Is there a possibility to avoid this "error"?
I am using the scope DSO3102A
Cheers Frank
05-13-2009 01:53 PM
Hello Frank,
Can you please confirm that you have state-caching enabled for your IVI Driver session? State-caching should greatly reduce redudant communication. Also, it is recommended to not repeatedly configure an instrument to the same settings (such as in a loop).
Thanks,
NathanT
05-14-2009 01:20 AM
Hi Nathan,
caching is enabled and I do the configuration step just once.
In the loop is the read step and this causes the "measurement already selected".
Cheers Frank
05-14-2009 09:20 AM
Hello Frank,
Please reduce the code down to the minimum amount that reproduces the problem, take an NI-spy capture of the problem (in a .spy format), and then attach both the code and capture to this post.
Thank you,
NathanT
Performing a Good NI Spy Capture for Debugging/Troubleshooting
05-15-2009 01:06 AM
Hi Nathan,
thanks for your support.
here are the two files you wanted.
Cheers Frank
05-19-2009 11:22 AM
Hello Frank,
Thank you for posting the NI Spy capture and the Sequence. I am running into some problems when trying to reproduce the issue with my DSO3062A, so could you please take another NI Spy capture of the issue with IVI Scope unselected from the "View Selection"? Spy>>Options>>View Selection tab>>Uncheck the box next to IviScope. That will allow us to see the commands that are actually being sent to the instrument.
Thanks,
NathanT
05-25-2009 08:36 AM
Hi Nathan,
here the file you wanted.
Thanks for your help.
05-26-2009 11:06 AM
Hello Frank,
Thank you for attaching the additional NI-Spy capture. It shows that the instrument driver only configures the settings once, starts a measurement, waits for it to complete, and then reads the measurement. I looked through both the programming and user manuals for the instrument and could not find any reference to the error that you are seeing. I also could not find a command to read the error information from the instrument, which in many instruments will give an error code that can be looked up in the manuals to determine what needs to be changed. Did the instrument happen to display an error code in addition to the beep and "measurement already selected" message?
I could not find anything when searching for "measurement already selected" on the Agilent website. If you have time, could you please contact Agilent and see if they have more information about that message and what is causing it?
Thank you,
NathanT
05-28-2009 07:51 AM
Hi Nathan,
no there comes no error code with the beep and the message.
I think i know why you cant reproduce the problem: the message appears just with the newest firmware 04.02.15.
I found a second scopy in my company: old firmware 04.02.10 no message, new firmware 04.02.15 an the message appears.
Can you now see "meassurement already selected" on your scope?
Cheers Frank