Trigger time out about agilent DSO5012A scope

[yiweihua2002]

Dear all:

I am using Labview 8.2 control Agilent DSO5000/DSO6000 Series scope through GPIB Bus,when I use this scope to acquire a square waveform which amplitude is 5V,and it frequency is 1KHz.I set the scope for edge trigger and the trigger level is 2.5V. When I use labview to acquire this waveform,the scope can normally acquire the square waveform and transfer to labview through GPIB bus.But if the square waveform not exist,for example the UUT is fault,and can not generate the square waveform.the scope will wait for the trigger waveform until it timeout which I set the timeout time 15000ms in Labview.In this situation the scope will report timeout error,and I can not use labview to Reset or stop the scope,It always wait for trigger waveform until I power off the scope and then power on it.I do not know why.

[NathanT]

Hello Yi,
        It sounds like this is expected behavior for both the scope and LabVIEW.  Have you considered a different type of trigger?  How about reducing your timeout?  Generally scopes will return an error if the trigger condition is not met within a certain period of time.

Cheers,

NathanT

[yiweihua2002]

Thank you NathanT

Yes,I have tried use Auto trigger mode,and it will not report error.But in some situation it need edge trigger model than other model.

The problem for me now is how to dear with this error when the timeout error occur.for example,use labview clear the error message,and reset the scope.Now I can use labview clear the error message,but I can not reset the scope use labview.If I want to use labview to control the scope,I must power off the scope and than power on it.

[NathanT]

Hello Yi,
        It sounds like this is more a product of how the instrument responds to certain commands and situations than with LabVIEW.  I recommend contacting the manufacturer and seeing if they have any ideas for how to help the instrument recover from the timeout error without having to physically power cycle the instrument.  Please let us know if it turns out that there is another command that could be used to avoid this bad situation but still maintain the behavior that you need.

Thanks,

NathanT