LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

triggered acquisition slope problems

Hi all,
 
I have a desperate situation.  I have a production test station that stopped working after reinstalling LV7.1.  My application uses a triggered acquisition to get data.  It is triggered on a square wave.  Depending on the product being tested, it needs to trigger on either the rising edge or the falling edge.  After the reinstall, it no longer changes acquisition mode.  I am using AI Read VI that came with LV.  When I open the AI Read VI it clearly shows that it has been set to trigger on the rising slope, but the data shows that it is still triggering on the falling edge. HELP!!
 
Jim
Jim

LV 2020
0 Kudos
Message 1 of 5
(2,937 Views)
Hi Jim,

The reinstall of 7.1 would not change the way the AI Read VI works.  I assume this is the Traditional DAQ VI that you can select out of the function pallette and place down.  The triggering characteristics of the data acquisition are determined by a different VI called AI Trigger Config. 

I want to make sure we are clear on the terminology.  When you say trigger, that would mean the initial acquisition would occur based on either the following or rising edge of the first square wave pulse.  After that the internal clock just continues to acquire based on the setting you have input.  The other option though is that you want to set which edge of the square wave every sample acquisition is done on and your clock for the acquisition is the external source.  If that is the case, then I can see what you are reffering to in the AI Read.The conditional retrieval cluster, where the slope is located has a mode.  Have you set that mode to on? That is something I could see affecting the behavior of your VI.  Make sure when you save this VI, that you save it as another VI, and not actually save the VIlib file.  Please let me know if there are further problems with this issue.

Have a great day,

Michael Denton
Applications Engineering
Nationa Instruments



0 Kudos
Message 2 of 5
(2,920 Views)

Hi Michael,

Thanks for the reply.  For some reason I didn't get an email notification.  It actually turned out to be a problem with the coupling.  It had somehow gotten changed to DC coupling, and it needs to be AC coupled.

 

Jim

Jim

LV 2020
0 Kudos
Message 3 of 5
(2,890 Views)
Hi Jim,

Sorry you never got a notification email.  I just wanted to be clear that you have gotten it back to being an AC coupled input and everything is working fine again.  If you are needing to set this up please let me know.

Have a great day,

Michael D
Applications Engineering
National Instruments
0 Kudos
Message 4 of 5
(2,881 Views)

Hi Micheal,

Thank you.  Yes once I saw that that Vi had the coupling set different than the other test set I changed it and everything is working fine with regard to that.

 

Jim

Jim

LV 2020
0 Kudos
Message 5 of 5
(2,876 Views)