DAQmx Read changes DIO to output?

wow, it's been a looong time - been doing PCB design (yuk!) but I'm glad to be doung some LabVIEW again... anyway, on to the question.
Using a 6025 DAQ card, and an express vi (built from DAQ assistant), I'm sending a True to a specific Line of a Port. Next, I want to read that same Line on that Port. However, when I read it, the "bit" is reset - reads False. I think what is happening is, the direction of the DIO changes to an output when you read the Line / Port. Is that correct? So, how would I read that bit after setting it, without "resetting" it??? Seems like LabVIEW 101, but I'm stumped.
Thanks,
Richard
LV 7.1
Richard

I think what is happening is, the direction of the DIO changes to an output when you read the Line / Port. Is that correct?
You would have configured the Line as a Digital output, when you do a DAQ assistant 'write' to a digital line.
When you try to read it, DAQ assistant will reconfigure it as a Digital Input and reset it to its default value.
So, you cannot set a line and read its boolean value as you are trying to do.
What you could do is make one line on port Digital Output ( write to it) and configure other Line as Digital input ( read on it)
Hope this helps,
Regards,
Dev

Similar Messages

Change the precision of waveform data or daqmx read

Hi all,
I am currently using daqmx read and writing the data to a tdms fiile. I would like to change the precision of the data if possible.
Any advice?
Thanks,
Matt

matt198717 wrote:
James,
I did however have another question. If i log data to a table indicator on my front panel, using a shift register to fill the table every data point, will this eventually become a burden on the CPU, and if so whats the largest table i should have on my front panel?
Thanks,
Matt
Just saw that you asked another question. Yeah, your table will get bigger and bigger and is what we like to call a "memory leak". You can go pretty big and be fine, but it's really just a play-it-by-ear type of thing. Think about how your end user is going to need to see the data. If they onlyy need the last hour of data on the table, then cut it off at an hour of history. If they need the last day, maybe it can handle it, but you might want to look in to limiting what's displayed or something like that.

Posttriggered DAQmx Read output if no trigger received.

I am running a posttriggered analog voltage input on a PCIe-6251 via DAQmx and I need to know what voltage Labview bins if no posttrigger is received and I set the timeout response to "cancel error on match."

MikeK,
I am not sure what you mean by post-triggered. Are you referring to a reference trigger, which keeps a buffer of data so that after it is triggered that buffer of data can still be recorded?
Please attach a snippet of code.
If you are in fact using a reference trigger and the DAQmx Read times out and the error is ignored by your error handler, no voltage data should be recorded. If you have this running, you can easily test this by creating an indicator on your DAQmx Read output and verifying that nothing is recorded.
Best.
Joey S.
Software Product Manager
National Instruments

Change form of output signal without initializing new process of output signal

Hello!
How to change form of output signal produced on the output channel without initializing new process of output signal?
Thanks
Message Edited by _Pavel_ on 10-28-2009 05:21 PM
Solved!
Go to Solution.

I'm working with LabView 8.5.1.
I have periodic TTL impulse with constant frequency – signal to start , which I'm used to start data acquisition (PCI-6251)and generation signal (PCI-6221).
When TTL signal a detection, necessary generation some analog signal (PCI-6221) and acquisition other analog signal (PCI-6251). Then wait following TTL signal.
At this moment I write the part of the program which is responsible for data acquisition. Function retriggering (In examples C:\ProgramFiles\National Instruments\LabVIEW8.5\examples\DAQmx\Synchronization\Multi-Function.llb\Multi-Function-CtrRetrigg Pulse Train Generation for AI Sample Clock.vi) is used. This function necessary,because we start data acquisition each time on arrival TTL impulse, andrepeated creation of the virtual channel of data acquisition with the newtrigger spend a lot of time.
The problem consists in the following. Generation of the data from other card should occur on the same impulse TTL as for the data acquisition card and then generation zero value.
How I can realize it? I planned to change the form of an impulse of generation when detected TTL an impulse, without reinitialize process.

Error code -200088, accessing DAQmx read function in fncB from fnc A

Hi,
I am using NIDAQ 6229, and C code.
My c code is as follows:
#define DAQmxErrChk(functionCall) { if( DAQmxFailed(error=(functionCall)) ) { goto Error; } }
int main()
TaskHandle aiTaskHandle;
// and the variables whatever used in the API's declaration below done here and initialised
DAQmxStartTask (aiTaskHandle);
  DAQmxErrChk (DAQmxCreateTask("AI Task",&aiTaskHandle));
  DAQmxErrChk (DAQmxCreateAIVoltageChan(aiTaskHandle,AIChannelList,AINameList,DAQmx_Val_RSE,0.0,10.0,DAQmx_Val_Volts,NULL));
  DAQmxCfgSampClkTiming(aiTaskHandle,"OnboardClock",AIRate,DAQmx_Val_Rising,DAQmx_Val_ContSamps,AISamplesPerChannelAcq);
while(1)
            fncB( );
fncB( )
            DAQmxErrChk (DAQmxReadAnalogF64
              (AITaskHandle,DAQmx_Val_Auto,timeOut,DAQmx_Val_GroupByScanNumber,AIReadArray,AIarraySizeInSamps,&AISampsPerChanRead,NULL));
This Code builds without errors and runs. But the problem is with calling the fncB( ) where the DAQmx read for aiTaskHandle is executing.
The DAQ read works fine for one time, but in the second call of fncB it gives error " task specified is invalid or does not exist" with error return code: -200088.
why for the second call , the task specified becoming unknown is not yet all clear.
the ni error codes document doesnot list this error code yet all.
i have tried in declaring aiTaskHandle variable global, then in the first time of calling fncB it gives the error as mentioned above.In my application i cant use DAQRead in the same function where i declared the taskHandle , so i have to call it from the function.
Does some body help in calling the DAQread from another function, and why this task is becoming invalid for the second call,.
Thanks ,
vishnu
Message Edited by gkvishnu on 10-12-2005 08:10 AM

I found where does my error come from.
I configure my task from a other function and call this callback to start acquisition (get partly from NI examples)
I get the error on the Start_AI_Clk(taskAIClk); call.
int CVICALLBACK AI_TrigStartCallback(int panel, int control, int event, void *callbackData, int eventData1, int eventData2)
   int32       error=0;
     char        Chaine[500],Chaine1[500],ChaineFormateur[500];
   int32       numRead;
   float64     *data=NULL,*dataMoy=NULL;
   int         i,j,Checked;
   double       LocValeurLue,TempsDebut,TempsTotal,TempsEnCours;
   long int    NbMesTotale = 0;
   FILE        *TempFile;
   if( event==EVENT_COMMIT ) {
        if( (data=malloc(NbMes*NbChanAIClk*sizeof(float64)))==NULL ) {
           MessagePopup("Error","Not enough memory");
           goto Error;
        TempsDebut = Timer();
       TempsTotal = TempsDebut;
       TempFile = fopen("TempoResult.txt","w");
       Start_AI_Clk(taskAIClk);
       ProcessDrawEvents();
       gRunningTrig = 1;
       while( gRunningTrig )
           DAQmxErrChk
(Read_AI_Clk(taskAIClk,NbMes,data,NbMes*NbChanAIClk,&numRead));
            ProcessSystemEvents();
             /*data treatment*/
       TempsTotal = Timer() - TempsTotal;
       fprintf(TempFile,"Temps total:%.3f - Nb Mes totales : %d",TempsTotal,NbMesTotale);
       fclose(TempFile);
Error:
   if( DAQmxFailed(error) )
       TraitErreurCarteDAQmx("Lecture AI horloge externe",error);
   if( taskAIClk!=0 ) {
       Stop_AI_Clk(taskAIClk);
   if( data )
       free(data);
   return 0;
What happen is when I click on my start button, my function is executed
once before a EVENT_COMMIT came, so it jumps directly to the Error part,
then as the taskHandle is not null, it stop the task
if( taskAIClk!=0 ) {
       Stop_AI_Clk(taskAIClk);
Then it executes the if(event==EVENT_COMMIT) part and as the task has been stopped, it give the -200088 error code.
To correct this, I change the Error treatment like this:
if( DAQmxFailed(error) )
    TraitErreurCarteDAQmx("Lecture AI horloge externe",error);
    Stop_AI_Clk(taskAIClk);
Yop!
DanY

How to run two DAQmx Read (Counter in + Digital in) simultaneously?

Hello to all, i have following issue:
I want to acquire a digital (UART like) bus signal. For this purpose i use a DAQmx Card (PXI 6070e). I need precise time information about time lenght of 0 and 1, so i use a counter. The counter is adjust to CI Semi Period(continuous samples) -> on the edge change i'll get a new measured time value. It works perfectly, but i newer know what kind of state (0 or 1) actually belongs to current value. Of course they changing with each edge, but i need to know that exactly. So i should take a digital input which watching the current state. Unfortunately i can not synchronise two DAQmx-reads.
Finaly i should get two values:
time value(counter) and his state(digital in
) to work with them. How can i do this?
I use LabView 7.0

[SRQ 211371]
This is not a trivial taks but here is one way to do what you explained with a PXI-6070E and some external circuitry:
1. Use buffered semi period measurement to measure the width of your pulses.(Meas Buffered Semi-Period-Continuous.vi)
2. Use a buffered continuous analog data acquisition with external scanclock (e. g. Cont Acq&Graph Voltage-Ext Clk.vi). Maybe you should use a triggered example to start the acquisition at a defined time.
Now you could connect your signal to the ScanClock input (PFI7) of the 6070E but then you only would acquire only a sample at either the rising or the falling edge. As you need a sample at both edges you need some external circuitry that generates a short positive TTL pulse at each edge (rising and fa
lling).
Sorry that I can't provide a solution for this circuitry but I'm pretty sure something like this should be available as a low cost IC.
You may want to allow your signal some settling time after the scanclock pulse has occurred. In this case simply acquire data on two AI channels. The first channel is only a dummy channel. Connect your signal to the second channel. The delay can be adjusted with the interchannel delay.
If anybody knows a good solution for the external circuitry or if anybody has a better approach please post it here.
Best regards,
Jochen Klier
NI-Germany

DAQmx: Numerical indicators go blank intermittently using DAQmx Read

Hello everyone,
I was wondering if anyone else has ever fought this issue and won. I have a loop (I will attempt to attach an image of the block diagram) which performs a DAQmx Read operation. The loop employs a 200 millisecond wait. The loop scales the data, sends all of the values to little indicators in an array, picks out a few critical values to display on duplicate large indicators, and optionally logs the data by streaming it to disk. The task will usually (99.9% of the time) be run at 100Hz. So, I was figuring I could do a "Read All", since at 200 ms of wait time due to the millisecond multiple wait function, I should always have around 20 points to read in the buffer the next time around. This would allow me to have very current readings in my displays. I could do a partial read, but then I figure I would have a lag between the displayed values and the reality of what's going on in the test. Having current readings, as current as can be, is highly desirable for this application.
I figured everything was good with what I was doing, especially when I tested it with a simulated device (I know a simulated device behaves much differently than a real device, especially at start up). Everything seemed to work well. When I go to the real hardware, though, I intermittently get blank indicators. Actually, it is more like intermittent numbers in my indicators. Most of the time, the DAQmx Read operation returns a null, empty array (no data available in the buffer). I must be missing something, because I figured that a 200 ms wait would allow another 20 samples to be collected.
If someone could please just ease my conscience and let me know that I haven't done something very fundamentally wrong in this code, even if you couldn't help me with a solution, I would very much appreciate it. I feel that this code should work, keeping data in the indicators at all times, and don't know why it doesn't work. If you could offer me the solution, even if it is to point out that I did something very wrong, I would much appreciate it.
I am just writing this code, and still have some icons to make, so the sub VI's still have the default icons. Sorry about that. Basically all those do is get array subsets, or scale data, or write data to the data files. If you need to ask questions about the code, I can understand. I am not the greatest yet at writing self documenting code yet. And if you need to know what that event structure does, it watches the two boolean button controls to determine what state in the state machine to go to next, and the time out case of the event structure highlights a data value if it goes out of bounds.
Sorry if I am too wordy. I have been accused of that before. I just notice a lot of "Help! DAQ doesn't work. How do I fix?" posts, and I don't see how I or anyone else could help that person at all.
I am using LV8.2, with DAQmx 8.3.1, on Windows XP, 1GB of RAM, and a fairly healthy Duo core processor. I have a workaround where I throttle back the read operation, only reading 55% of the available samples, as reported by a DAQmx Read property node (the highest percentage I found that prevents the indicators from going blank). This introduces a small lag between the real world and the data on display, however. Also, it seems like a processor dependent solution. I would have to tweak this percentage for every machine I run this on.
If I have left anything important out, please let me know, and I will do my best to clarify, and thank to anyone who reads this, and a big thank you to anyone who takes the time to reply. Again, I would be real happy with a "That code looks good to me, and your thinking is correct", if that indeed is the case.
Thanks.
Attachments:
Log Monitor Block.JPG ‏292 KB

Yeah, as you and Erik said, just specifying (Sample Rate / 5) as the '# to read' could do the trick. Then you can ditch the 'Wait (msec multiple)' function. I don't think I'd recommend the -1 = infinite timeout though. I'm pretty leery of stuff that can lead to an infinite wait or an infinite loop. Even a 1 sec timeout should easily be way more than enough. Note however that this method depends on all your processing code executing in under 200 msec on average. Otherwise, your reads will fall behind and you'll eventually get a DAQ buffer overflow error. My earlier suggestion to first query for # available samples and then read the MAX of (# available, SampleRate/5) will prevent cumulative fall-behind effects.
There's too many unknowns to speculate with any confidence on exactly why the software timing method didn't work. I can point out some additional things that bear greater scrutiny though.
1. You've got some sort of function dealing with file streaming that takes a path input and produces a path output. This probably means that every loop iteration you're using the path to open a file, write data, and close the file again. This actually may consume more than 200 msec, at least some of the time. Because this runs in parallel with the msec wait function, something like the following could be happening:
A. Iteration 1 proceeds as expected. The DAQ read collects 20 samples, the file write consumes only 100 msec, and the wait msec function ends after 160 msec in order to end on a 200 msec multiple. The wait function took longest, so your whole loop ends on a 200 msec multiple.
B. On iteration 2, the wait msec function ends after 200 msec on the next 200 msec multiple. The DAQ read collects another 20 samples (because it's been pretty much exactly 200 msec since the previous loop iteration started) right away. However, Windows was busy messing with the file cache so this time your file write consumes 375 msec. The file function took longest so your whole loop ends 175 msec into the next 200 msec multiple.
C. On iteration 3, the wait msec function ends after 25 msec on the next 200 msec multiple. The DAQ read collects 37 samples that have come in since the prior call 375 msec ago. The file function consumes only 50 msec this time, ending the loop 25 msec into the next 200 msec multiple.
D. On iteration 4, the wait msec function ends after 175 msec at the next 200 msec multiple. The DAQ read collects the 5 samples that have come in since the prior call 50 msec ago. Uh oh, not enough samples...
One possible fix is to open the file outside the loop and leave it open until after the loop is done. Opening and closing files has quite a lot of overhead. Inside the loop, you'd be passing around the file refnum. Doing this one thing alone might also be a way to fix your timing problem. Along similar lines, you could write the data to a queue and then do your file writes in an independent loop that reads the data out of the queue. You can search here for "producer consumer" for more info.
-Kevin P.

Change RFQ & PO output from fax to e-mail

Change RFQ & PO output from fax to e-mail

You can set this up in NACE as a default or you can also set up condition records to specify if the form should be print, fax, or email. See if the NACE transaction works for you..use Application EF for Purchase Orders and Application EA for RFQ's. Hope this is helpful.

Daqmx read.vi timestamp incorrect problem (storing the timestamp from start task)

Hello,
I have a state machine with 1st state: configure DAQ where i have [daqmx create channel.vi --> daqmx timing sample clock--> DAQmx start trigger--> daqmx start trigger] connected in order
sample clock in continuous mode, 10000 samples to read and sample rate 1000 Hz ,
start trigger has rising edge selected with a dev1/PFI0 from a daq board.
next state of SM is read channels which has daqmx read.vi set to 1d waveform Nchan Nsamp.
and the program first configures and goes to read channels state and is just waiting for the true value on PFI0,
but the time stamp is not updated to current time/ when daqmx read starts instead it is getting the initial t0 from the time when it was in configure DAQ state of my SM in other words it stores the starting time when strart task.vi was run and then updates from then on.
so in effect i am not getting the exact time stamp values while i am running the vi.
i tried to build waveform by inputting the actual current time but the chart doesnot scroll and shows only few values each reading, when i tried to input the t0 from the waveform given out by read daqmx. vi, it then behaves normally..
option #1 from this link says
http://forums.ni.com/ni/board/message?board.id=250&thread.id=47648&view=by_date_ascending&page=2
Try and do exactly what the driver does. This
will require you to do exactly what you are doing in the posted
example. Call the current system time immediately prior to calling the
DAQmx Read and subtract dt * x where x is the number of samples already
acquired. This will require you to know exactly how many samples have
been acquired. This can be found by calling the Total Samples Per
Channel Acquired property immediately prior to the DAQmx Read. This
introduces some points of innaccuracy. For example, you're system time
is already innaccurate to some amount. In addition, it takes some time
between calling system time, calling the total samples acquired, and
calling the DAQmx read. If 2 samples are acquired between calling the
system time and total samples acquired, you could be off by a few
samples. For slower clock rates, you will have more accuracy.
but there are no samples that are acquired until the rising edge, so the number of samples is always zero before the read operation
http://digital.ni.com/public.nsf/allkb/5D42CCB17A70A06686256DBA007C5EEA
this link says that
and the number of samples in my waveform is constantly changing around 20-40, so i cannot really input the current time to build the waveform, thats what i can figure out for now..
can somebody tell me why this is happening or is there any fix around this, how to get the current time into my daqmx read.viso it displays the currect time on my waveform chart
Thanks,

thanks,
im using LV 8.6, daqmx driver 8.9.5.
yes the program u posted get the currect time. but see attached program thats what i have in my program exactly
if you took out the time to using the get waveform components using the waveform from daqmx read. i still have the timestamp as the application start time. plz see attached code 8.2v and FP
the waveform time x axis is not current, it is starting from the application start time.
PS: samples to read = 10,000 and sample rate = 1000
plz help..
Attachments:
daqmx read problemp.png ‏8 KB
daqmx read problem.vi ‏36 KB

[solved] NFS: "ls: reading directory .: Input/output error" after time

Hello,
I got the following configuration:
NFS-server: Always on, connected via LAN.
NFS-clients: 2 computers, connected via LAN and WLAN. On standby: auto umount NFS-share via system-sleep-hook with systemd.
This works flawlessly some hours or even days. But after some time, the following happens:
1. mount nfs-share: no error message
2a. trying to access that folder via filemanager, e.g. thunar: folder seems to be empty (it isn't on server!), but the correct freesize of the NFS-share on server is displayed in the statusbar.
2b. trying to access that folder via commandline:
$ ls
ls: reading directory .: Input/output error
The very same worked just a few hours before, I haven't changed anything meanwhile. Apart from standby (--> auto umount NFS-share) and resume (manual mount NFS-share) on the clients which worked before, too.
Any idea what's going wrong?
additional info:
server:
/etc/exports
/srv/nfs/myshare 192.168.2.0/24(rw,all_squash,anonuid=33,anongid=33,no_subtree_check)
(yes, the mapping is needed and right.)
clients:
/etc/fstab
servername:/srv/nfs/myshare /home/carl/nfs nfs4 noauto,soft,user,_netdev,timeo=14,rsize=8192,wsize=8192 0 0
/usr/lib/systemd/system-sleep/umount-nfs
#!/bin/sh
case $1 in
pre)
umount -f /home/carl/nfs
esac
Last edited by Carl Karl (2014-09-21 17:07:47)

Indeed, there could be something interesting in dmesg on the server:
[ 4.190117] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 4.190596] NFSD: starting 90-second grace period (net ffffffff818a9540)
[ 5.445237] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[ 5.895519] r8169 0000:04:00.0 enp4s0: link up
[ 5.895529] IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
[72346.265850] usb 3-1: USB disconnect, device number 2
[72346.670926] usb 3-1: new SuperSpeed USB device number 3 using xhci_hcd
[72346.684585] usb-storage 3-1:1.0: USB Mass Storage device detected
[72346.684716] scsi5 : usb-storage 3-1:1.0
[72347.686518] scsi 5:0:0:0: Direct-Access WD Elements 1048 1022 PQ: 0 ANSI: 6
[72347.687606] sd 5:0:0:0: [sdc] 976769024 512-byte logical blocks: (500 GB/465 GiB)
[72347.690295] sd 5:0:0:0: [sdc] Write Protect is off
[72347.690301] sd 5:0:0:0: [sdc] Mode Sense: 47 00 10 08
[72347.692981] sd 5:0:0:0: [sdc] No Caching mode page found
[72347.693025] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[72348.135398] sdc: sdc1
[72348.141458] sd 5:0:0:0: [sdc] Attached SCSI disk
[72348.455737] EXT4-fs (sdc1): recovery complete
[72348.455919] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
[74276.020331] EXT4-fs error (device sda1): ext4_find_entry:1310: inode #14024711: comm nfsd: reading directory lblock 0
[74276.021107] EXT4-fs error (device sda1): ext4_find_entry:1310: inode #14024711: comm nfsd: reading directory lblock 0
(last one repeats several times...)
Indeed, the NFS-share resists on a external WD harddrive connected via USB, /dev/sdc1.
As suggested in the NFS wiki article, the NFS-share is a bind-mount:
/etc/fstab on server:
# fake-root for NFS
/magnet/owncloud/data/carl/files /srv/nfs/myshare none bind,noauto,x-systemd.automount
while /srv is on /dev/sda1.
The external harddrive has an auto-standby (NOT hdparm...) which isn't causing troubles with other services.
So it seems to be a problem connected to this bind-mount to external USB setup....
I'll try to find out whether there is a way to avoid that.
Thanks so far!
Last edited by Carl Karl (2014-09-16 14:30:02)

Is DAQmx Read limited to 9 digital channels?

I'm trying to read multiple digital channels with DAQmx Read (Digital 1D Wfm NChan NSamp). The output the DAQmx Read vi is a 1D array of digital waveforms. If I put that output through Array to Cluster the resulting cluster seems to be limited to 9 elements, data[0] through data[8]. Is the DAQmx Read output limited to 9 digital waveforms? I'm using Labview 2009.
Solved!
Go to Solution.

Converting an array to a cluster to use unbundle to break out the elements of the array is a hack.
You should be using Index Array to get the elements. You can resize that function so that you can have additional outputs. You won't even have to wire up any constants for the indices usually. The top element will be element 0, the next element 1, element 2, and so on down to the bottom of the function.

Change log for outputs

Hi,
How to check change logs for output condition records ?
Thanks
Rama

use txn OY18 and insert table name NACH.
Search for tables and execute the same and then use details for further information.

Clearing daqmx read value

Hello,
When doing a single sample counter read using DAQmx in a while loop, is there any way to reset the data output on the DAQmx read task? For instance, say the value is 200, is there any way I can keep the task open and running and reset it to read zero?
Thanks,
David Joseph
Message Edited by KY Wildcat on 11-16-2007 10:57 AM

Hi KY
There isn't a property or method in DAQmx for setting or resetting the count value when a task is running. You need to Stop and Start the task again. Otherwise, you can
create your counter in software. If you wire the counter output to an indicator, you can then create a local variable and create the logic that will
programmatically reset its value, e.g. when it exceeds 200.
http://digital.ni.com/public.nsf/allkb/65E3DBC715998C3286256E900075B7F8
I hope that helped,
KostasB
NI Applications Engineer

DAQmx read progress

I am collecting 5000 samples per channel on 16 channels using the DAQmx VI's. I would like to have a progress bar that is updated as the data collection takes place. I have attempted to use the "Current Read Position" property node, however it only outputs the total number of samples taken once the task is complete rather that constantly updating. Thanks.

Try using the DAQmx Read property Available Samples per Channel. This will give you the right numbers. Attached is an example (in LV8.5). I will also attach a pdf with the block diagram in case you do not have 8.5.
Message Edited by rpursley8 on 01-09-2008 08:00 AM
Randall Pursley
Attachments:
DAQMX test.vi ‏41 KB
DAQmx Test.pdf ‏49 KB

Acquisition DAQmx read

Bonjour,
Je suis en train de réaliser une application qui fait l'acquisitionde deux signaux en sortie d'accéléromètre!!
Mon problème est quand je fais le contrôle du bruit j'ai une erreur qui s'affiche (voir capture), et ça vients de mon DAQmx Read
Les deux vi en piece jointe sont pour l'acquisition d'une des voies, et en faite j'ai exactement les mêmes pour l'autre voie j'ai juste changé la chaîne que je lis!!!
Si vous avez une idée merci
Arnaud
Pièces jointes :
Essai Projet final.zip ‏32 KB
Acquisiton.JPG ‏15 KB

Je viens d'utiliser ton vi qui marche plutôt bien!!! Par contre je vois pas trop comment faire pour indexer mon tableau!!
Après mon traitement du signal, j'ai un 1D array of Cluster of 3 éléments et je sais pas comment choisir ma courbe a afficher!!!
Pièces jointes :
Affichage.JPG ‏192 KB

DAQmx Read changes DIO to output?

Similar Messages

Maybe you are looking for