LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Time Delay NIScope not working

Dear NI Community, 


I am developing a TestStand sequence where I capture 2 waveform with my scope. I am using a PXIe5110 and NI Scope for that. I have noticed that the Time Delay between the 2 channels couldn't be measured and it leads to an error. Going in InstrumentStudio to visualize the waveforms, I have noticed that regarding the acquisition was going well. Using the cursors, I also obtain the value that I want. 

 

al0909_0-1763469159431.png

 

However, when I try to measure it through the measurement window below, nothing appears for the Time Delay. 

Is there something in the configuration that I can do with NI Scope to correct that ?

Thanks in advance for your answer !

0 Kudos
Message 1 of 5
(126 Views)

How exactly are you using the NI Scope driver to capture the signals? did you code anything in one of the supported ADEs (LV, Py, C# etc.,)?

 

Please share your code and how you measure the time delay.

Santhosh
Soliton Technologies

New to the forum? Please read community guidelines and how to ask smart questions

Only two ways to appreciate someone who spent their free time to reply/answer your question - give them Kudos or mark their reply as the answer/solution.

Finding it hard to source NI hardware? Try NI Trading Post
Message 2 of 5
(122 Views)

Dear santo_13, 

 

Thanks for your answer. I am using NI-Scope drivers in generic steps as I am working with a Hardware Abstraction Layer, that's why it is complicated to share the code entirely. 

 

However, by equivalence, I developed quickly a VI reusing NI-Scope the same way I used it in the HAL and in my TestStand sequence. As you can see, I am using the Read Single Measurement to retrieves the Time Delay. In my sequence, this function causes an error. And in InstrumentStudio, I don't see any results as the picture showed it.

 

Thanks a lot in advance

0 Kudos
Message 3 of 5
(74 Views)

Try this modification. 

I used multi read measurements and used fetch data to read the raw data 

(both read measurements start the reading, your example maybe read 2 times 😉 )

 

I only tested it with a simulated 5922 I already had ...

 

I think the time delay measurements needs to know the second channel read ... 

 

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


0 Kudos
Message 4 of 5
(47 Views)

Another try : I added a property node to tell the measurements engine what other channel to use and switched back to single measurement. no error on my side..

 

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


0 Kudos
Message 5 of 5
(44 Views)