Tektronix TDS2014B. The scope free runs just fine under it's own control but under SignalExpress control it repeatedly triggers creating a recording that is discontinuous bursts of data.

[Jacob_R]

I did not test a set up like that. It looks like the device is not even showing up as a USB device. Would you be willing to install our DAQmx driver, which installs the latest version of MAX?

[DrElectrode]

I am more than willing to install DAQmx. Also, I really appreciate the help from you and others at NI.

[DrElectrode]

I installed the recommended software and I am still getting the same results. The scope does show up in Devices now, though. The attached files were created with settings identical to those you used and are shown in a previous post. The only difference is the serial number of the scope. Oh, and this is running on a 64 bit machine.

[Jacob_R]

Is it a windows 7 64 bit? I will need to set up a system with 64bit to try it out. Do you have a different 32bit machine that you can try?

[DrElectrode]

The only 32 bit machines I have access to are running XP Pro. I will try one in the morning, anyway. Just to verify, how long did you let SignalExpress run the recording of the 1KHz trace? Or perhaps I should ask, how long could you have let it run without inturuption and still get a continuous trace?

[Jacob_R]

I have been recording the trace for over an hour without any discontinuity. Try recording the data in the recording options to see whether it is just a user interface updating issue.

[DrElectrode]

I have been delayed working on this problem as the scope had to go out for A2LA acredited calibration. It was found to be functioning within parameters. However, this does not cover USB communication! I have been able to set up and run on a Dell Latitude D510 laptop running a Pentium (R)M 1.73GHz with 1GB of memory (FSB speed unknown) running XP Pro Ver. 2002 Service Pack 3 and I am experiencing the same pattern of trigger, aquire, waiting for trigger, trigger, aquire, waiting for trigger,etc. The processor loads up to about 55% during aqusition. The memory usgae remains at 435 MB.

I am using the probe compensation square wave signal provided on the front of the scope and also external sine wave signal generation. In all cases, I have been keeping to the same 1000Hz signal frequency.

I am trying to locate a similar scope that I can try on my various setups to try to eleminate this scope as the source of the problem.

Is there any way to force the SignalExpress software to only "listen" during a recording session? I have tried unchecking the "SignalExpress controls instrument" checkbox but it still triggers repeatedly.

[DrElectrode]

Would an NI I/O Trace File yield any clues? Please see the attachment.

[Jacob_R]

Thank you for posting the NI I/O Trace. Having an initial look, it seems that every 3 seconds there are several viRead function calls in a row before the next viWrite. I will need to look into this more to figure out what may be happening.

This is what I found in the read-me about the 64-bit OS:
Note On Windows Vista x64 Edition, the 64-bit version, USB plug-and-play functionality does not work because LabVIEW SignalExpress Tektronix Edition is a 32-bit application.

Was the NI I/O Trace from the 32 bit machine?
Have you also taken a look at capturing the report?

[DrElectrode]

Yes, this was run on the 32 bit machine described in the 11/19 post. I have attached an NI_support report from this same PC for you review.