Lock of GPIB measurement device

[srapp@moog.de]

Hello,

I am using test stand 3.1 (multithreading) and I am using the IVI drivers for agilent GPIB measurement devices.

Is it necessary to lock the GPIB hardware for example with the test stand synchronizaions steps to use it only once at one time or is the lock automatically done by the measurement and automation explorer or the IVI driver?

regards

Samuel 

[PeterFoerster]

Hi,

this really depends on how you implement your test:

If you are using batch model, you need to lock the resource with Batch synchronisation steps.

If you are using parallel model, you need to lock the ressource using the lock steps.

Are you espreiencing any problems yet, or are you just asking to avoid problems in the future?

Best regards

[srapp@moog.de]

Hello,

Thank You!

I am asking to know how have to create my sequences 

I am using sequential model, but I am starting a second sequence in a new thread from my main sequence.  The second sequence and the main sequence access on the same hardware which is a power supply. Is it enough to lock the power supply or is it necessary to lock all the devices which read an write on the GPIB bus to prevent data colission or is this ensued by the IVI driver or the Measurement and Automation explorer? 

regards

Samuel Rapp

[PeterFoerster]

Hi,

I am not sure if I understood you correctly. Could you please post an example that demonstrates how your tasks are set up.

It is not necessary to lock the entire communication on the Bus. It will be enough to lock the Part where you write to the power supply for as long as you don't want any change to it.

Best regards,