07-08-2009 09:57 AM
Hello,
I am using the IVI Scope Step (within a separate threat) to wait for a trigger event. In case an other event appears, I have to stop the scope step (or the whole threat where this step is in) but I don't know how to do this. Terminate() and TerminateAll() doesn't work.
Cheers Frank
07-09-2009 12:32 AM
Hi Frank,
I think stopping the Ni-IviStep will not work, because you have to monitor the termination state in the step itself
and this is not implemented.
If you like to do this you have to rewrite the source of Ivi Steptype.
http://forums.ni.com/ni/board/message?board.id=330&message.id=2149&query.id=155821#M2149
There is a old thread from Ray dealing with thread and executions
http://forums.ni.com/ni/board/message?board.id=330&message.id=1554&query.id=154411#M1554
I think here you will find the answer on stopping theads and executions
Hope this helps
juergen
07-09-2009 01:24 AM
Thanks juergen!
How can I rewrite IVI steps? Where can I find the source code?
07-09-2009 03:53 AM
Hi,
If you are using TS4.0
you will find it under:C:\Programme\National Instruments\TestStand 4.0\Components\NI\StepTypes\IVISteps\Scope
It is written in Basic.
An other thing you could think about is to obtain the current IVI-Handle for the Scope.
If you get this you could use your favourite CodemoduleAdapter and write your own special code.
But i never tried this.
Maybe other people out there know how to extract the IVI handle from IVI StepType.
Lets wait
Juergen
07-10-2009 01:45 AM
Hi,
I am using TestStand 4.1.1 and there is no folder like you described. I have a folder:
C:\Programme\National Instruments\TestStand 4.1.1\Components\StepTypes\IVISteps but there is no basic code or other source code.
It seems that there is no source code for the IVI steps in my TS Version.
Frank
07-15-2009 12:31 AM
Is there nobody who knows to stop the scope while it waits for the trigger event?
07-15-2009 12:54 AM
07-15-2009 01:08 AM
I am using an Agilent Scope series DSO3000 which is connected via GBIP.
I was thinking about to write a small script which checks the trigger status.
But then I can't interchange the instrument as easy as before.
07-15-2009 06:15 AM
Hi Frank,
Yes you are right! Interchangeabitiliy is THE feature of ivi.
So i would suggest to use instead of the ag3000_32 .dll (thats why i asked for the hardware) the iviscope.dll
you can use it with the Dll-Adapter in TestStand.
So you can write your script in TS.
Juergen
07-15-2009 09:42 AM
Have you tried running the IVI Scope Abort function when the sequence is terminated?
Or, instead of modifying the IVI step, use the IVI Scope class in a code module. You can still interchange instruments and you can monitor the termination status.