SignalExpress

cancel
Showing results for 
Search instead for 
Did you mean: 

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.

Can you reattach the settings from your system as described in Message 23? I could not open the file you attached.

 

Were you able to test acquiring signals from another scope?

 

I would recommend updating your IVI  Compliance Package. This contains the IVI class drivers and the support libraries necessary for the development and use of applications for IVI instruments. The latest version 4.5 is available at the link below.

 

http://joule.ni.com/nidu/cds/view/p/id/3065/lang/en

 

 

Regards,

Anjelica W.
National Instruments
Product Marketing Manager
FlexLogger and TestStand
0 Kudos
Message 31 of 53
(4,021 Views)

The various files form the saved projects are being rejected when I try to attach them. Do you have any suggestions to get around this other than compressing into one file? Check with your IT group and see if they have something to open the 7zip file that I sent previously.

I have not aquired another TDS2014B scope, yet. We may rent another one from the same vendor to eliminate this one as defective. Remember, though, that I have gotten the same results running the TDS2000 IVI. I was able to get continuous samples in using IVI but only beyond a certian horizontal sweep frequency. I think it's noted in a previous post.

I believe I was using the latese IVI class drivers but I will verify after the holiday.

0 Kudos
Message 32 of 53
(4,016 Views)

Hello,

I have made a capture of my own NI I/O Trace and will need to run it by some people in R&D. I'll keep you posted on what we find. Were you able to get a continuous reading with the exact settings that I posted earlier? When would you be able to get a hold of a second scope to test?  

Jacob R. | Applications Engineer | National Instruments

0 Kudos
Message 33 of 53
(3,880 Views)

Unfortunately, I was not able to duplicate a continuous trace result even using the exact settings you provided (even down to the seemingly arbitrary trace position of -0.68 div). I have also failed to get the desires result using a 23 bit Windows XP SP3 machine.

 

I hesitated to rent another scope based on the fact that I saw discontinuous traces running in virtual interface mode, as well. It is not that expensive, so, I will order one tomorrow if you think it would be worthwhile.

0 Kudos
Message 34 of 53
(3,871 Views)

Before you go ahead a rent anything. Can you elaborate more on the discontinuous traces you saw running in virtual interface mode? Are you referring to when you simulated an IVI Scope and briefly saw a discontinuity at the beginning of your acquisition, before you read a continuous trace? Can you attach a screenshot of this behavior?

Jacob R. | Applications Engineer | National Instruments

0 Kudos
Message 35 of 53
(3,868 Views)

Also, what is the IVI  Compliance Package version on both machines?

Jacob R. | Applications Engineer | National Instruments

0 Kudos
Message 36 of 53
(3,825 Views)

Both machines are running IVI Config server 1.3.2.4 and IVI compliance package 3.1. LabVIEW version is 2.5.1. I am attaching some virtual signal screen shots and live data from the TDS2014B. The SignalExpress settings are identical to those shown in message 17. One small difference is my signal source is peaking around 350mV. By the way, we have been puttering away at this so long, my 64 bit machine is now out of it's evaluation period.

 

The screen shots here are from the 32 bit unit (which still has about 15 days left.

0 Kudos
Message 37 of 53
(3,786 Views)