Unwanted trigger signal on Tek TDS5054, Labview 7.1

[uribarri]

Hi all,

I'm using the tktds5k_32.dll library of functions in Labview 7.1 to download waveforms from my Tektronix TDS5054 scope.  The whole process works beautifully, except that when I use Labview to control the scope (as opposed to using the scope alone) I get a spurious trigger signal from somewhere (presumably in the software) every 10.5 seconds.  This means my data folder fills up with mostly nonsense waveforms. My own software contains no timing at all (it just deals with the waveforms once downloaded), so my guess is there's some timing I can't see somewhere in the library functions.  Anybody experience this before or have suggestions?

Thanks.

[Collin M]

Have you done an NI Spy capture to verify you aren't actually sending a trigger command? Does anything from the NI Spy capture correlate to the scope triggering?

Also, I think in the tktds5k driver package from Tek is included the c file that contains the implementations of all the functions that the LabVIEW driver calls. I wonder if one of Tek's vi's has a side-effect of sending a trigger command to the scope.

[uribarri]

I'll look into running an NISpy on this---at the moment it won't let me because I have a Tektronix version on VISA installed like the scope wants and NISpy wants an NI version of VISA...I'll try to get around that.

I should clarify that I've since realized that the scope isn't actually triggering, but the acquisition process is resetting and downloading traces without a trigger ever happening.  On the face of my scope this looks like a trigger, hence my confusion.  So my search is now not for a trigger signal but for a command that is telling the VIs to reset every 10 seconds.

Thanks!