All acquisitions wait for digital trigger, why?

On one computer I have 2 eseries 6023 daq boards installed. One for a digital triggered acquisition, and the other for a continuous (chart recorder type) acq. When running the two seperate VI's, why does the the cont. acq. VI wait for the trigger on the other VI? Appreciate any help.

Hi digger,
AI Read.vi waits until the samples are in the buffer.
Do following: Call AI Read.vi with 0 scans to read. Look in scan backlog output if any samples are available. If there are samples waiting call AI Read.vi with this output contected to the input scans to read otherwise do nothing.
This prevents AI Read.vi from waiting until samples are in the buffer.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Similar Messages

Using DAQ occurrence to wait for start trigger

Hi,
I'm trying to use digital triggers to start and stop datalogging. Every time start trigger appears, new file is created and data is acquired to file until stop trigger occurs. Now I'm using set DAQ occurrence and wait for occurrence functions to wait for start trigger before creating a new file. The problem is that after first stop trigger this occurrence method doesn't work. I believe it's because AI is not cleared and configured before calling DAQ occurrence again. Number of scans acquired is not zero, if I don't clear and configure AI again? Am I right?
Do I have to clear and init AI everytime before occurrence config or is there a better way to make program wait for start trigger?
Thanks in advance,
Jakke

Hi Matt99eo,
Have you configured your device for triggering? Although you have not mentioned your device specifically, the M series user manual provides a great explanation of digital triggering. Using the DAQ Assistant, this can be configured from the triggering tab. Hopefully this helps!
Regards,
h_baker
National Instruments
Applications Engineer
Digital Multimeter Resources

HT204074 I have just bought an I Pad Air and tried to add to my I tunes it said I have to wait for 90 days why ??

I have just bought a new I pad Air and I tried to add to my I tunes account and it said I have to wait for 90 day why?
also I cant play any music from my libery when my computer is not logged into I tunes Help Please

Have you already logged into one account on it and used iTunes Match, automatic downloads and/or download past purchases from that account ? If you have then it will be associated to that account for 90 days, as mentioned on the page that you posted from. If you can't wait for the 90 days to complete then you can try contacting iTunes Support and see if they can remove the association : http://www.apple.com/support/itunes/contact/ - click on Contact iTunes Store Support on the right-hand side of the page

HSDIO conditionally fetch hardware compare sample errors (script trigger to flag whether or not to wait for software trigger)

I am moderately new to Labview and definitely new to the HSDIO platform, so my apologies if this is either impossible or silly!
I am working on a system that consists of multiple PXI-6548 modules that are synchronized using T-CLK and I am using hardware compare. The issue I have is that I need to be able to capture ALL the failing sample error locations from the hardware compare fetch VI... By ALL I mean potentially many, many more fails than the 4094 sample error depth present on the modules.
My strategy has been to break up a large waveform into several subsets that are no larger than 4094 samples (to guarantee that I can't overflow the error FIFO) and then fetch the errors for each block. After the fetch is complete I send a software reference trigger that is subsequently exported to a scriptTrigger that tells the hardware it is OK to proceed (I do this because my fetch routine is in a while loop and Labview says that the "repeated capbility has not yet been defined" if I try to use a software script trigger in a loop).
This works fine, but it is also conceivable that I could have 0 errors in 4094 samples. In such a case what I would like to do is to skip the fetching of the hardware compare errors (since there aren't any) and immediately begin the generation of the next block of the waveform. That is, skip the time where I have to wait for a software trigger.
I tried to do this by exporting the sample error event to a PFI and looping that PFI back in to generate a script trigger. What I thought would happen was that the script trigger would get asserted (and stay asserted) if there was ever a sample error in a block, then I could clear the script trigger in my script. However, in debug I ended up exporting this script trigger back out again and saw that it was only lasting for a few hundred nanoseconds (in a case where there was only 1 injected sample error)... The sample error event shows up as a 1-sample wide pulse.
So, my question is this: is there a way to set a flag to indicate that at least one sample error occurred in a given block that will persist until I clear it in my script? What I want to do is below...
generate wfmA subset (0, 4094)
if scriptTrigger1
clear scriptTrigger1
wait until scriptTrigger0
end
clear scriptTrigger0
generate wfmA subset (4094, 4094)
I want scriptTrigger1 to be asserted only if there was a sample error in any block of 4094 and it needs to stay asserted until it is cleared in the script. scriptTrigger0 is the software trigger that will be sent only if a fetch is performed. Again, the goal being that if there were no sample errors in a block, the waiting for scriptTrigger0 will not occur.
I am probably going about it all wrong (obviously since it doesn't work), so any help would be much appreciated!

Please disregard most of my previous post... after some more debug work today I have been able to achieve the desired effect at slower frequencies. I did straighten out my script too:
generate wfmA
if scriptTrigger1
clear scriptTrigger0
wait until scriptTrigger0
end if
generate wfmA
scriptTrigger1 = sample error event flag
scriptTrigger0 = software trigger (finished fetching error backlog in SW)
However, I am still having a related issue.
I am exporting the Sample Error Event to a PFI line, looping that back in on another PFI line, and having the incoming version of the Sample Error Event generate a script trigger. My stimulus has a single injected sample error for debug. For additional debug I am exporting the script trigger to yet another PFI; I have the sample error event PFI and the script trigger PFI hooked up to a scope.
If I run the sample clock rate less than ~133MHz everything works... I can see the sample error event pulse high for one clock period and the script trigger stays around until it is consumed by my script's if statement.
Once I go faster than that I am seeing that the script trigger catches the sample error event occasionally. The faster I go, the less often it is caught. If I widen out the error to be 2 samples wide then it will work every time even at 200MHz.
I have tried PFI0-3 and the PXI lines as the output terminal for the sample error event and they all have the same result (this implies the load from the scope isn't the cause).
I don't know what else to try? I can't over sample my waveform because I need to run a true 200MHz. I don't see anything that would give me any other control over the sample error event in terms of its pulsewidth or how to export it directly to a script trigger instead of how I'm doing it.
Any other ideas?

How do I continuously wait for a trigger?

using labview and GPIB to control tektronix 3034B oscope. want to continuously wait for trigger. how do i get rid of timeout? I am using IVI instrument driver for 3034B

Hi,
You can use the low level adquisition VIs. First call Initiate Acquisition. Then use the Acquisition Status VI to determine if the acquistion is complete. This wait you can wait indefinitely.
Of course, you could also set the timeout value of the ReadWaveform VI to something like 86000000 ms, which is aprox. a day of timeout .
DiegoF
National Instruments.

Function module for getting the all PO waiting for release

Hi,
Is there any standard Function module for gettting all the PO's which all waiting for release.
Regards
Bala.

hi Bala,
ECC 6.0 Exits for VA01
go through the above link i think that will help u...
Regards,
sindhu.

App Server Freeze - All threads waiting for replication data

          We are running Weblogic 6.1 SP2, on solaris 8 with jdk1.3 When running load at our
          application - full GC is taking between 15 -20 seconds. At a certain point after
          a full GC on one of the servers in the cluster we see session replication errors
          in the logs. The application eventually freezes - the execute queue is huge on each
          of the JVMS and when we do a thread dump we see that all threads are waiting for
          replication data. All threads have the same stack trace as follows:
          "ExecuteThread: '1' for queue: 'default'" daemon prio=5 tid=0x2c58b0 nid=0xe waiting
          on monitor [0xbf980000..0xbf9819d8]
               at java.lang.Object.wait(Native Method)
               at weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:72)
               at weblogic.rjvm.ResponseImpl.getTxContext(ResponseImpl.java:97)
               at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:80)
               at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:135)
               at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
               at $Proxy74.lookupROIDS(Unknown Source)
               at weblogic.servlet.internal.HttpServer.lookupROIDS(HttpServer.java:761)
               at weblogic.servlet.internal.session.ReplicatedSessionContext.getSessionInternal(ReplicatedSessionContext.java:225)
               at weblogic.servlet.internal.ServletRequestImpl.getValidSession(ServletRequestImpl.java:2130)
               at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1921)
               at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:107)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2467)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


          Yes this is reproducable. We are now working with BEA Support under Case : 321199.
          Thanks
          Anna
          Kumar Allamraju <[email protected]> wrote:
          >You should work with [email protected]
          >Can this problem be reproduced with an isolated test case?
          >If yes, it will be really helpful for them to work with Engg.
          >
          >--
          >Kumar
          >
          >anna bancroft wrote:
          >
          >> We are running Weblogic 6.1 SP2, on solaris 8 with jdk1.3 When running
          >load at our
          >> application - full GC is taking between 15 -20 seconds. At a certain
          >point after
          >> a full GC on one of the servers in the cluster we see session replication
          >errors
          >> in the logs. The application eventually freezes - the execute queue is
          >huge on each
          >> of the JVMS and when we do a thread dump we see that all threads are waiting
          >for
          >> replication data. All threads have the same stack trace as follows:
          >> "ExecuteThread: '1' for queue: 'default'" daemon prio=5 tid=0x2c58b0 nid=0xe
          >waiting
          >> on monitor [0xbf980000..0xbf9819d8]
          >>      at java.lang.Object.wait(Native Method)
          >>      at weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:72)
          >>      at weblogic.rjvm.ResponseImpl.getTxContext(ResponseImpl.java:97)
          >>      at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:80)
          >>      at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:135)
          >>      at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          >>      at $Proxy74.lookupROIDS(Unknown Source)
          >>      at weblogic.servlet.internal.HttpServer.lookupROIDS(HttpServer.java:761)
          >>      at weblogic.servlet.internal.session.ReplicatedSessionContext.getSessionInternal(ReplicatedSessionContext.java:225)
          >>      at weblogic.servlet.internal.ServletRequestImpl.getValidSession(ServletRequestImpl.java:2130)
          >>      at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1921)
          >>      at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:107)
          >>      at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2467)
          >>      at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
          >>      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          >>      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >>
          >>
          >

Waiting for th writer why?

I am trying to burn DVD using Toast 10.It worked OK abut 2 months ago but now you get the statement "waiting for the writer".After about 5 minutes it spits out the blank disk. Nothing gets written. I have tried 2 different brands of blanks and several blanks out of each package. no difference. Any thoughts?
Bob

I tried a cleaner CD, no help. It would play a DVD movie ok. Didn't try to burn a CDI Then I tried Diskwarrior. Now it works perfectly. I swear, Diskwarrior could cure a rainey day!!
Bob

Can trigger wait for another trigger before it is fired?

i have table TAB1
and i have TAB1_HISTORY
when row gets inserted into TAB1 i have some logic in TRIG1 to updated few fields using rowid ARRAYS just to be safly updated everything in case more than one rows gets into TAB1.
now TRIG1_HISTORY suppose to move data from TAB1 into TAB1_HISTORY but some fields are null because TRIG1 may be not finished updating fields yet.
Any way to trig1_history follows trig1? I know one way is to make TRIG1_HISTORY as store proc .
i am usign 10g
thanks

There is no such thing as unassigned rowids.
If there is a rowid, the row exists and it can be updated.
The general strategy for your problem is
before statement trigger: set up an array with empty values.
before or after for each row: do whatever you want, and buffer the primary key (or rowid) in the arrary you set up.
After statement: do anything you want to do with the collected primary keys/rowids.
This is being processed in the correct order and it shouldn't fail.
Hth
Sybrand Bakker
Senior Oracle DBA

Im tired of forums and having to wait for help..why cant we talk to Adobe tech?

Hello, I have a new laptop and cant get the install to complete because it wont accept the DW MX2004 serial number even though the CS4 is serial number is accepted.
thanks for your help

Long shot: try using the MX 2004 serial number listed here
Error: Unable to Activate | Macromedia products

Wait for trigger

Hello
I need help making a VI for waiting for a trigger. I am working with a TDS 2024 scope.
I have to tell the scope how long to wait for the trigger and if it does not find it in that time, then it will tell the user that no trigger was found.
Can anyone help me with this?
xxmidna

Midna19 wrote:
Hello
I need help making a VI for waiting for a trigger. I am working with a TDS 2024 scope.
I have to tell the scope how long to wait for the trigger and if it does not find it in that time, then it will tell the user that no trigger was found.
Can anyone help me with this?
xxmidna
Time to break out the scope manual and see what commands are needed to achieve this. Put a VI together and then we can talk about refining it.
Alternatively, you can see if you can find some drivers for this scope. I think Tektronix has pretty good LV support.
(This assumes you know how to use the scope.)
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Stopping program without waiting for trigger

Hi everybody
I have a problem that I just can't get my head around. I have a program that I use to aquire data. The program goes through the motions of waiting for the trigger, aquiring the data on the appropriate channel, displaying it, and loops back to waiting for the trigger. The problem is That when I want to stop my program while it is waiting for a trigger I must wait for it to recieve a trigger before it will stop excution.
Is there a way for my program to stop the trigger vi when I select to end the program?
Thanks
Beaton
- there is always an easy way, but it is always the hardest to find

Hi Beaton,
you have to split the 'wait for trigger time' into shorter sub-steps.
Let's say you wait 10sec for trigger signal. Make a loop instead waiting 1 second for 10 times! After each iteration you can check for: 'break the loop (end program)' or 'trigger received' or 'any other error occured'. This way you can stop your program very easily - you can also make your own error state saying 'Error number 123456: stopped by user'...
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

NIScope CPU usage 100% when waiting for trigger

Hello, I'm using a NI 5102 DAQ card and want to acquire single bursts. However when the Multi Fetch.vi is waiting for a trigger (and this can be up to a minute) the CPU usage goes up to 100 %. Is there any way to overcome this?
Attachments:
Current_ProjectSWEEP2withoutAgilentNEWScopeWrite_to_FilePOSTED.vi ‏98 KB
ScopeSUB.vi ‏108 KB

Yea, Ive noticed the same thing. The niSope dll in the Fetch.vi grabs 100% CPU if timeout is larger than 1 or 2 seconds.
Has anyone talked to NI about this? The problem is in that dll which is polling the PCI Scope Card. That dll is not giving back any CPU if it waits for more than a second or two.
John Dailing
[email protected]

How to take a single data point for each trigger pulse ( synchronous acquisition).

hi
          im using the pci-mio-16E1 card, with the IDE VC++, so im looking for an example to explicate me how to make an synchronous acquisition data using an external timing, so the idea is to acquire (take) a single data point for each trigger pulse from one input channel ,and saving the data in a file .
now im making a code using the AI_setup and DAQ_op functions, im getting a speed acquisition (it is the start of acquisition data), and it is a synchronous acquisition just for one trigger pulse, and me i looking for an acquisition for each trigger pulse.
so to  understand my problem you can see my code :
iStatus = Timeout_Config(iDevice, lTimeout);
         iRetVal = NIDAQErrorHandler(iStatus, "Timeout_Config", iIgnoreWarning);
   // configuration and selection of signal trigger
         iStatus = Configure_HW_Analog_Trigger(iDevice, ND_ON, iLowValue,iHighValue, ND_ABOVE_HIGH_LEVEL, ND_THE_AI_CHANNEL);
        iRetVal = NIDAQErrorHandler(iStatus, "Configure_HW_Analog_Trigger", iIgnoreWarning);
iStatus = Select_Signal(iDevice, ND_IN_CONVERT, ND_PFI_2,ND_HIGH_TO_LOW);
         iRetVal = NIDAQErrorHandler(iStatus, "Select_Signal", iIgnoreWarning);
    iStatus = AI_Setup(iDevice, iChannel, iGain);
   iRetVal = NIDAQErrorHandler(iStatus, "AI_Setup", iIgnoreWarning);
   while ((iReadingAvail != 1) && (iStatus == 0)) {
/* Wait until reading is available. */
         iStatus = AI_Check(iDevice, &iReadingAvail, &iReading);
        iRetVal = NIDAQYield(iYieldON);
       // Acquire data from a single channel
    iStatus = DAQ_Op (iDevice, iChannel, iGain, piBuffer, ulCount, dSampRate);
   while ((iDAQstopped != 1) && (iStatus == 0)) {
        iStatus = DAQ_Check(iDevice, &iDAQstopped, &ulRetrieved);
        iRetVal = NIDAQYield(iYieldON);
       iStatus = DAQ_VScale(iDevice, iChannel, iGain, dGainAdjust, dOffset,ulCount, piBuffer, pdVoltBuffer);
      iRetVal = NIDAQErrorHandler(iStatus, "DAQ_VScale",iIgnoreWarning);
   /* Set analog trigger mode back to initial state. */
       iStatus = Configure_HW_Analog_Trigger(iDevice, ND_OFF, iLowValue,iHighValue, ND_ABOVE_HIGH_LEVEL, ND_THE_AI_CHANNEL);
/* Set PFI line back to initial state. */
       iStatus = Select_Signal(iDevice, ND_IN_START_TRIGGER,ND_AUTOMATIC, ND_DONT_CARE);
          iStatus = DAQ_Clear(iDevice);
/* Plot acquired data */
      iRetVal = NIDAQPlotWaveform(pdVoltBuffer,ulCount, WFM_DATA_F64);
so this is the data acquired -0.900879,-0.900879,-0.900879,-0.900879,-0.900879,-0.900879,-0.900879,-0.900879 and i think that is a noise because all time i get this data.
tank you very mutch fo your help

Hello,
Please see the responses to this thread at the following post.
http://forums.ni.com/ni/board/message?board.id=250&message.id=13686
Also, please only post one thread per issue.
Regards,
Sean C.

ORA-00060: deadlock detected while waiting for resource with Tbs Read-only

Hi all,
We're using Oracle 10.2.0.1 and 9.2.0.4.
I'm testing the performing of a procedure that inserts, like this:
CREATE OR REPLACE PROCEDURE P$TAD_TEST
IS
TYPE T_T1_C1 IS TABLE OF T1.C1%TYPE INDEX BY PLS_INTEGER;
TYPE T_T1_DT IS TABLE OF T1.DT%TYPE INDEX BY PLS_INTEGER;
P_C1 T_T1_C1;
P_DT T_T1_DT;
P_RESULT NUMBER;
BEGIN
FOR j IN 1..4032 LOOP
P_C1(j) := j;
P_DT(j) := SYSDATE + (j/24/60);
END LOOP;
FORALL i IN P_C1.FIRST..P_C1.LAST SAVE EXCEPTIONS
INSERT INTO T1 VALUES (P_C1(i), P_DT(i));
EXCEPTION
WHEN OTHERS THEN
P_RESULT := SQLCODE;
END;
The table T1 is partitioned across 10 tablespaces. The test consist to take
these tablespace read-only and perform the procedure, and analyze the results,
like erros.
but when I perform the procedure, The alert.log indicates the error
ORA-00060: deadlock detected while waiting for resource.
Why this occurs only the tablespaces are read-only?
thank you!!!!

Hi,
yesterday we got this error again(in fact twice) and we were able to get the trace file. It says this is NOT oracle error. i was wrong in suspecting Oracle. This is the trace file details. i dont know how to debug this. Any help appreciated.
*** 2010-06-15 16:24:29.243
*** ACTION NAME:() 2010-06-15 16:24:29.231
*** MODULE NAME:(JDBC Thin Client) 2010-06-15 16:24:29.231
*** SERVICE NAME: 2010-06-15 16:24:29.231
*** SESSION ID:(482.4266) 2010-06-15 16:24:29.231
DEADLOCK DETECTED ( ORA-00060 )
[Transaction Deadlock]
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-00300021-0000b52d 209 482 X 247 474 S
TX-002a0009-00011b24 247 474 X 209 482 S
session 482: DID 0001-00D1-0000000A session 474: DID 0001-00F7-00000008
session 474: DID 0001-00F7-00000008 session 482: DID 0001-00D1-0000000A
Rows waited on:
Session 474: obj - rowid = 0000CED4 - AAAM7UAAxAAAVgSAAA
(dictionary objn - 52948, file - 49, block - 88082, slot - 0)
Session 482: obj - rowid = 0000D8BF - AAANi/AAuAAB+z/AAA
(dictionary objn - 55487, file - 46, block - 519423, slot - 0)
Information on the OTHER waiting sessions:
Session 474:
pid=247 serial=31796 audsid=25502259 user: 62/USER
O/S info: ....
program: JDBC Thin Client
application name: JDBC Thin Client, hash value=2546894660
Current SQL Statement:
INSERT QUERY1
End of information on OTHER waiting sessions.
Current SQL statement for this session:
INSERT QUERY2
Thanks,
AK

All acquisitions wait for digital trigger, why?

Similar Messages

Maybe you are looking for