High-Speed Digitizers

cancel
Showing results for 
Search instead for 
Did you mean: 

Capturing Existing Data on Agilent 5000 series scope

Hi,

 

I am new to using labview and am trying to capture data on my agilent 5000 series oscilloscope, using the NI drivers.

 

The problem is i can't capture existing data on the scope, I can only capture data after i trigger the oscilloscope again while the program is running.

 

I would like to be able to trigger the scope, then run the program and capture the data, without triggering a second time. I would appreciate any help very much.

 

 

additionally, after i read the data, it erases it from the scope, how can i leave the data on the scope?

 

thank you very much,

 

Ziv

 

 

 

 

 

0 Kudos
Message 1 of 18
(7,416 Views)

Hi Ziv,

 

This document on Triggering High Speed Digitizers might help lead you to some other information. Additionally, you can always refer to some of the related links at the bottom of the page.

 

Cheers,

KyleP
Applications Engineer
National Instruments
0 Kudos
Message 2 of 18
(7,409 Views)

kyle,

 

thanks for the reply. I do appreciate it.

 

Perhaps i was unclear. my problem wasn't triggering the scope. That is fine. I trigger the scope from an external source and it works well.

my problem is reading the data from the scope. i have 2 different issues:

 

1. the read vi (NI for agilent 6000 series) doesn't grab the data displayed on the scope when i run the VI, but if i suddenly trigger the scope externally it will capture the data. I would like my VI to read the displayed data on the scope by my labview command, regardless of the external trigger

 

to be clearer, this is the way i would like my VI to work

 

ext. trigger->data->run VI->labview command->capture data (original data)

 

but, what i am getting right now is 

 

ext. trigger->data->run VI->ext. trigger->capture data (new data because of the second trigger)

 

 

2. After i use the read vi it erases the data displayed on the scope, i would like to keep that data displayed on the scope

 

I do appreciate any help you could give me regading these 2 issues 

 

thank you very much,

 

Ziv

0 Kudos
Message 3 of 18
(7,404 Views)

Hi Ziv,

 

Which driver are you using in this application?

 

Cheers,

KyleP
Applications Engineer
National Instruments
0 Kudos
Message 4 of 18
(7,399 Views)

hi kyle,

 

I am using the agilent 6000 series drivers, i have copied the link below

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=1E5E6D70FCA569A3E0440003BA7CCD...

i also tried the ag6000 driver

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=0D3F5F0998FE61CAE0440003BA7CCD...

(seems to me they are almost the same)

 

thanks

 

Ziv

 

0 Kudos
Message 5 of 18
(7,394 Views)

Have you tried the fetch waveform?

0 Kudos
Message 6 of 18
(7,392 Views)

yes, i have tried the fetch waveform VI and obtained the same issues

 

0 Kudos
Message 7 of 18
(7,386 Views)

Hi Ziv,

 

Could you post a screenshot of your code so that it's a bit clearer what you're doing?

 

Cheers,

KyleP
Applications Engineer
National Instruments
0 Kudos
Message 8 of 18
(7,375 Views)

Kyle,

 

here are a couple of screenshots from 2 different programs i did.

the first using the read vi

the secong using the fetch waveform vi

 

note that i also attached screenshots i obtained while running the program. you can see the green arrow on the read/fetch waveform vi's.

the program remains in that position until it receives the external trigger or until timeout. i would like my vi to read the existing data on the scope and not read the new data obtained as a result of the trigger required for the program.

 

thanks,

 

Ziv

 

0 Kudos
Message 9 of 18
(7,368 Views)

Ziv,

 

I believe that what you are doing is expected behavior. Is there any reason that you can't have the program running before the data is generated?

 

Cheers,

KyleP
Applications Engineer
National Instruments
0 Kudos
Message 10 of 18
(7,338 Views)