Problem with DAQMX on a 6025E !!

Problem with DAQMX on a 6025E
I work on a DAQ 6025E and I can't use the example "Write Dig Port.vi" and all others example on digital output with DAQMX. There isn't any hardware failure because the same installation functions correctly with the traditional DAQ. I want to use these channel parameters: Dev1/port2.
I already tested to make a reset device and use "line or port configuring vi" but without successes.
Thanks for your help!
Attachments:
Write_Dig_Port.vi ‏48 KB

I took a look at the example you attached and it looks fine. Here are a few things to try out BEFORE running the example from MAX:
1) Remove any SCXI, SCC, and accessories from the configuration in MAX so that no DIO lines are reserved for communication.
2) Reset the driver to work in DAQmx mode for your board. To do this, first right-click the "Traditional DAQ Devices" and say "Reset Driver" and then right-click your 6025E under DAQmx Devices and say "Reset Driver" again. This should enable the driver for DAQmx.
3) In MAX, under DAQmx Devices, run the test panel and make sure you can read/write all the DIO lines there first. If that works fine you should be able to run the example.
Remember that the port names for the 6025E are Port 0, Port 2, Port
3, and Port 4 (no Port 1).
Good Luck!!!
Sincerely,
Brooks Bailey
Application Engineering
National Instruments

Similar Messages

Problem with DAQmx and Real Time PCI-7041/6040E.

Problem with DAQmx and Real Time PCI-7041/6040E.
I have a problem with the Real Time card PCI-7041/6040E, I think it is properly installed because my software run with the traditional NI-DAQ. When I try to use the new DAQmx to acquire one signal, Labview doesn't see any device for de DAQ card 6040E.
Information, I work on Windows XP and LabView v7.0.0 (NIDAQ RT v7.0.0, NI-Serial RT v2.5.2, NI-VISA v3.0.1 and NI-Watchdog v2.0.0).
Could Labview RT run with new DAQmx ?
What can I do to use DAQmx with PCI-7041/6040E?
Thanks for your help !

Hello,
I refer to your posts because i am using the PCI 7041/6040E card as
well but without any success to make it work. The problem I have
already described in the following thread:
http://forums.ni.com/ni/board/message?board.id=170&message.id=120198
Would be nice if you had a look on it, maybe you can help me. BTW, the
thread starts with a problem of someone else, the difficulties I
encountered are to be found a little bit to the bottom of the thread's
page.
Thank you!
Dirk Völlger
Darmstadt
Message Edited by ratschnowski on 07-28-2005 07:14 AM

Problem with DAQmx Physical Channel control

Dear LabVIEW community!
I have installed LabVIEW, v13.0f02, 32-bit on my PC. The problem, which I face, is that DAQmx Physical Channel controls, which are used in VIs inside the LV projects, sometimes don't show me the list of DAQ devices - I can't expand the list at all. I push the button to expand the list, but nothing helps.
But when I create VIs outside the project, and put there DAQmx Physical Channel control - everything works well.
Note: devices are simulated via MAX.
Is it some kind of bug in 2013 vesrion of LabVIEW? Because while using LV 2012 I didn't have such headache.
The only thing that helps now - is to restart PC (laptop) several times; b/c restart of LV doesn't help.
Can anyone suggest, what it can be, and how to fix this problem?
Thank you very much in advance!

Thank you for your answer!
The point is, that this bug is independent from the code. DAQmx Physical Channel controls don't work even when I'm trying to use NI examples - for instance, Strain - Continuous Input.vi; Voltage - Continuous Input.vi, etc.
I have such simulated via MAX devices: NI USB-9213, NI USB-9201, NI cDAQ-9172 with NI 9217, and 4 NI PXIe-4331 modules.
Also, what I have noticed - front panel doesn't visualized fully (I send you the screenshot). When I'm moving mouse pointer over it, those part, which were under the mouse pointer, became clearly seen. And when I minimize, and then restor FP, it becomes fully clear visible.
And also, this story happens when LV project is open. If I close opened projects, and open only single VIs, everything works smooth.
Thank you very much, I hope, that this information will be useful to solve this problem.
Attachments:
Screen 1.PNG ‏87 KB
Screen 2.PNG ‏107 KB
Screen 3.PNG ‏129 KB

Problem with DAQmx BASE

Hi,
I'm able to create a task with using NI-Daqmx Base Task Configuration utility. I'm trying to create a DIO task for my application, when i set the output port as 0. The application works. But, when i change the output port as 1,2 and 3. It doens't work. Anyone know why is this happening?
Thanks.

Duplicate thread
http://forums.ni.com/attachments/ni/70/8472/1/movement.vi</msg_body>
Please only post in one forum thread at a time
Rob L
NI Applications Engineer
UK & Ireland
It only takes a click to rate this message ;-)

Reservation problem with DAQmx

Hi there,
I'm using LV 8.5.1 and a NI USB-6210 Device. In a small app I want to generate two dig. signals, configured in one task. After configuration the task an error occures at "DAQmx Start Task.vi" with error code 50103 Device is reservated, can't go on (translated from used language). On this PC, there's only this USB device in use and only this small app is running.
So my question, how can I find out which app is reservating my device (in LV) and/or can I force to reservate my app for this device?
thx in advance

Hi Dennis,
thanks for your reply. I started to examine my app step by step. Know I know, the error occurs when I set more than one samples per channel in "DAQ MAX Timing (implicit).vi"
I use this app to control startup-conditions on power supplies, just for info.
Attachments:
6210_Dig_Sync_Sig_.vi ‏40 KB

A problem with data acquisitioning in LV 7.1 (transition from Traditional NI-DAQ to NI-DAQmx)

Hi to everyone,
I have a problem with data acquisitioning in LV 7.1.
I made a transition from Tradiotional NI-DAQ to NI-DAQmx in my LabVIEW application.
The problem I have is that when I acquire data in Traditional (without writing somewhere -
just reading) then there is no scan backlog data. But when I acquire data in application that
acquisition is based on DAQmx than a scan backlog indicator shows numbers from 20 to 50 for
about 6 min and then that number quite quickly increases until I get an error (unable to
acquire data. The data was overwritten).
Acquisition settings are the same in both cases. When I acquire with DAQmx I use a global
channels. Is a reason for that phenomenon in global channels data procesing? But it seems
strange why does it flows quite smoothly for about 6 min and then it stucks?
Best regards,
Ero

If you have an old Daq unit it may not be compatible with DAQMX. Which DAQ unit do you have? I think NI have a list showing which DAQ driver you can use with your card
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

RE: Problem with settling time in DAQmx Assistant

Good day.
I am a postgraduate student at the University of Pretoria. We are using a PCI 6229 ADC, SCXI 1001 chassis, SCXI 1102C amplifier and SCXI 1303 terminal block for experimental measurements. We want to take thermocouple measurements at high sampling frequencies but at the moment we cannot log data at more than 500 Hz before the MAX warns of possible inaccuracies due to problems with the settling time. MAX recommends reducing the sampling rate to address this issue.
However, it seems strange to be limited to 500 Hz sampling rate considering that all the aforementioned hardware specifies much greater sampling capabilities; less than half of the SCXI 1001 chassis ports are currently in use. I would like to know whether there are any software and/or background processes inhibiting the obtainable sampling rate? Also, is there any way to work around the settling time problem of the amplifiers to increase the sampling rate that can be accurately achieved?
All help will be greatly appreciated.
Thank you.
Regards,
TUKS_student

Hello TUKS,
Are you currently using a Thermocouple task? Does this problem occur if you were to just get raw voltage from those channels? This may be a limitation of the task in software itself, thermocouple measurements are meant to be slow since temperature does not change quickly. If you want to go faster you may have to acquire raw voltage along with the voltage from the cold junction channel and calculate temperature by hand. I would like to note that if you were to sample faster that you would have a considerable amount of data that does not change much at all, is there a reason why you have to go so fast?
Regards,
-Travis E
National Instruments
Applications Engineer

Some problems with 3 counters on PCI 6601

Good afternoon,
after a lot of time i'm here yet.
The problem with the PCI 6601 aren't finished in sense that i have tried a lot of solution but my sistem crashed after some acquisition.
The code that had write on Visual Basic 6 are :
'Inizializzo la scheda PCI-6601
Public Sub init_6601(NumSens As Integer)
Dim edge As DAQmxEdge1
On Error GoTo ErrorHandler
    MyChannel(NumSens) = "My Channel" & NumSens            'Definisce il nome per il canale (optional)
    'Creo i tre task che servono per il funzionamento del programma
    DAQmxErrChk DAQmxCreateTask("", taskHandle(NumSens))
    'Questa funzione serve a creare il canale dalla quale poi viene effettuata la misura
    If (NumSens = 0) Then
        DAQmxErrChk DAQmxCreateCIPulseWidthChan(taskHandle(NumSens), "Dev1/ctr1", MyChannel(NumSens), 0.00001, _
        0.0009, DAQmx_Val_TimeUnits3_Seconds, DAQmx_Val_Edge1_Rising, "") ' DAQmx_Val_TimeUnits3_Ticks, DAQmx_Val_Edge1_Rising, "")
    ElseIf (NumSens = 1) Then
        DAQmxErrChk DAQmxCreateCIPulseWidthChan(taskHandle(NumSens), "Dev1/ctr2", MyChannel(NumSens), 0.00001, _
        0.0009, DAQmx_Val_TimeUnits3_Ticks, DAQmx_Val_Edge1_Rising, "") 'DAQmx_Val_TimeUnits3_Seconds, DAQmx_Val_Edge1_Rising, "")
    Else
        DAQmxErrChk DAQmxCreateCIPulseWidthChan(taskHandle(NumSens), "Dev1/ctr3", MyChannel(NumSens), 0.00001, _
        0.0009, DAQmx_Val_TimeUnits3_Seconds, DAQmx_Val_Edge1_Rising, "")
    End If
    DAQmxErrChk DAQmxSetReadReadAllAvailSamp(taskHandle(NumSens), False)
    'Con questa funzione si sincronizza il timebase della scheda con il segnale da leggere
    DAQmxErrChk DAQmxSetCIPulseWidthDigSyncEnable(taskHandle(NumSens), MyChannel(NumSens), True)
    'DAQmxErrChk DAQmxSetReadOverWrite(taskHandle(NumSens), DAQmx_Val_OverwriteMode1_OverwriteUnreadSamps)
    'DAQmxErrChk DAQmxCfgSampClkTiming(taskHandle(NumSens), "", 100000, DAQmx_Val_Rising, DAQmx_Val_AcquisitionType_ContSamps, 10000)
    'provare queste due funzioni per aspettare che il campione sia realmente disponibile.
    'La seconda èdovrebbe essere quella che da il migliore compromesso tra uso CPU e velocità.
    'DAQmxErrChk DAQmxSetReadWaitMode(taskHandle(NumSens), DAQmx_Val_WaitMode_WaitForInterrupt)
    'DAQmxErrChk DAQmxSetReadWaitMode(taskHandle(NumSens), DAQmx_Val_WaitMode_Yield)
    'Setta il numero di campioni da acquisire ogni volta che va in lettura e
    'il modo di lettura. Si è impostato "contsamps" per avere la lettura continua
    'La dimensione del buffer è determinata da quel 10000 che va messo così secondo le specifiche del daqmx
    DAQmxErrChk DAQmxCfgImplicitTiming(taskHandle(NumSens), DAQmx_Val_AcquisitionType_ContSamps, 10000) 'DAQmx_Val_AcquisitionType_ContSamps
    'La scheda NI PCI 6601 ha soltanto un canale per il DMA (Direct Memory Access) quindi non riesco a leggere
    'contemporaneamente tre task per volta. Quindi devo attivare un meccanismo diverso per la lettura
    'basato sugli interrupt, ogni volta che ho una lettura automaticamente leggo il dato
    DAQmxErrChk DAQmxSetCIDataXferMech(taskHandle(NumSens), MyChannel(NumSens), DAQmx_Val_DataTransferMechanism_Interrupts)
    'La funzione di seguito serve semplicemente per leggere il campione più recente generato
    DAQmxErrChk DAQmxSetReadRelativeTo(taskHandle(NumSens), DAQmx_Val_ReadRelativeTo_MostRecentSamp)
    'La seguente funzione è complementare ad una utilizzata nell'inizializzazione e serve per impostare la lettura
    'sull'ultimo campione generato
    DAQmxErrChk DAQmxSetReadOffset(taskHandle(NumSens), -1)
    DAQmxStartTask taskHandle(NumSens)
    taskIsRunning(NumSens) = True
Exit Sub
ErrorHandler:
    For i = 0 To 2
        If taskIsRunning(i) = True Then
            DAQmxStopTask taskHandle(i)
            DAQmxClearTask taskHandle(i)
            taskIsRunning(i) = False
        End If
    Next i
    MsgBox "Error: " & Err.number & " " & Err.Description, , "Error"
End Sub
For the reading i use :
        DAQmxErrChk DAQmxReadCounterF64(taskHandle(NumSens), -1, 0.5, temp(NumSens, 0), 10000, ReadSamp(NumSens), ByVal &O0)
Well, my problem are very simple, I want an continuos acquisition on three channel and the input signal's frequency that i have to measure is 1 kHz .
when i try to keep 2 channel after some cycles appears the error -200141 (buffer overwriting). Why?
The read function is called some times every ms and evry time keep out an different value, even if that are impossible because the input signal is at 1 kHz, and why the buffer fill up? What is wrong in my code?
Thanks in advance for your help
Have a nice day!!
Igor Piero Prato

HI Igor84,
Error 200141 occurs when the data acquisition device acquires data faster than the computer can read it from the FIFO (first-in-first-out) input buffer.
You can see this document:
Error 200141 Occurs When Doing Buffered Event Counting
http://digital.ni.com/public.nsf/allkb/83656593DCF1FB0F862570B6004D7222?OpenDocument
and this forum :
Buffer Overflow -200141
http://forums.ni.com/t5/Measurement-Studio-for-VC/Buffer-Overflow-200141/m-p/607234
I hope that these links can help you.
Regards

With DAQmx, how to use AO start trigger for AO/AI synchronization with finite AI sampling

I am a new user to DAQmx and I am trying to synchronize AI (finite samples) with AO in LabVIEW 7.1 using a PCI 6229 card. I want to generate a finite waveform (AO) and, subsequently, collect a finite number of voltage samples (AI). I would like to repeat the AO-AI cycles in a while loop.
Alternatively, I could use an infinite AO generation and collect finite number of voltage samples on AI but always exactly at the same spot of the AO buffer.
Using traditional DAQ and a 6024E card, I used a counter triggered by AO start trigger signal (example attached). I have problems with translating this example into DAQmx.
Please help!
Ruber
Attachments:
AIAODelay_traditional_Eseries.vi ‏155 KB

Lesley,
Thank you very much for your suggestion. Late last night I actually tried a to use AI start trigger instead of AO start trigger and it worked (since I tried the AI & AO to start simultaneously, it does not matter what triggers what), even in the loop. The devil is in details, as I had to carefully wire the number of data points and what to place inside/outside the loop.
The problem with shared clock is that I need to sample the AI and AO at different rates but using AO and AI clock separately did not seem to affect the performance.
I still want to try to use the AO start trigger (as you suggest) because I would like to delay the AI by a few ms from the AO. Is there a simple way to to that?
I suppose, switching from traditional DAQ to DAQmx requires your brain to be rewired - after playing with it for a couple of days and nights I developed a "feeling" for it. One of the differences was that, in order to use this example in the loop, one has to use 'stop task' inside and 'clear task' outside the loop.
Thanks again!
Radek Uberna

Problem with generate sine 50 Hz

I have a problem with generate sine voltage with freq 50 Hz.
I form waveform with this frequency and sent in to the "AO Write" with update rate equal waveform lenght*frequency. And so I have a cycle of my program 20 ms, but I need a cylce 5 ms.
How I can make it right?
I forming my waveform "Basic Function Generator" with sampling Info equal my waveform lenght.
Message Edited by Unk on 09-28-2005 02:36 PM

The
amplitude
phase
frequency
of the signal are independent parameters.
You can generate the relevant signal using Basic Function Generator VI, then supply this waveform to your AO operation (DAQmx write is polymorphic and allows you to use a waveform directly as the input - those guys at NI are clever )

Can read TEDS in MAX but not with DAQmx VIs

Hi,
I have a cdaq 9181 with a 9234 accelerometer module. I have 3 teds equipped accelerometers connected to ai0, ai1, and ai2 repectively. In MAX, when I reserve the chassis I can read all three teds, no errors. When I do the same thing in labview (ie reserve the chassis, create a daqmx task, associate teds data with each physical channel, all with daqmx VIs) I can only read two out of three teds. The third one throws a "no teds sensor detected" error. This code has been in use for about four months now, though I just rewrote the calling VIs, and hasn't displayed this problem. I've attached a snippet of the task building VI for reference.
Any ideas what's going on?
Thanks.
Using LV2012 and MAX 5.3.1 running on Windows 7 32 bit.
CLAD
Attachments:
Build Daq Task Snippet.png ‏58 KB

Nope. That's a delete from array, length 1, index 3.
In any case, I eliminated that block since the string array wired to the for loop controls how many devices the VI attempts to configure. Same result, verified it was trying to configure ai2. Here's the updated snippet:
CLAD
Attachments:
Build Daq Task Snippet v2.png ‏54 KB

Pulse Generation application with DAQmx and a PXI-6624 module?

What is the best implementation method for the following pulse generation application
using LabVIEW, DAQmx and a PXI-6624 counter\timer module?
I have two rising edge trigger signals (Trigger-1 and Trigger-2).
There is ample spacing between each trigger. They never occur at the same time.
I need to generate a single pulse (fixed width, variable delay) whenever Trigger-1 occurs and
a finite pulse train (fixed width, variable delay, N-pulses) whenever Trigger-2 occurs.
However, the output must appear on one counter output because this composite signal
will be used as a trigger source for another PXI module in the rack.
With DAQmx and a TIO counter\timer can I use both the GATE (for Trigger-1) and
AUX (for Trigger-2) at the same time on the same counter to gate out the desired pulses?
Trigger-1 would be wired to the GATE of CTR0. One Trigger-1 event would generate one pulse on the output of CTR0.
Trigger-2 would be wired to the GATE of CTR1 and the output of CTR1 would be routed to the AUX input of CTR0.
One Trigger-2 event at the GATE of CTR1 would generate multiple pulses on output of CTR0.
Would DAQmx and the PXI-6624 TIO support this implementation?
What is the best way to accomplish the task at hand.
Thank You.
Best Regards,
Scooby

Hi Scooby,
I have looked into the application you have described and I see a potential problem with what you describe. In DAQmx, it is not possible to call the counters of the same DAQ device in the same task, so you cannot have the finite pulse train generation and the single pulse generation tasks running at the same time. What you can do, since you mention the triggers will not occur at the same time, is to stop one counter task while you are triggering another. The way I would suggest you merge the outputs is with a two input Or logic gate to avoid damaging your counters. Your signals will effectively be added together by this logic gate. I do not see any way to merge the outputs internal to the DAQ device.
Please let me know if I can be of additional assistance.
Laura

How to configure a continuous pulse generation that doesn't end after the VI exits with DAQmx?

Hi,
I'm just learning the DAQmx and I have run into a problem.
With the legacy DAQ API I could configure a counter to create continuous pulses and
when I needed change the freq or duty cycle, I would just call the the configuration function
again. The pulses were generated even after I closed LV, so it was all in the hardware.
Now, with DAQmx api, it seems that this is not possible. I read a forum post saying that
LV will end the pulse generation after the VI exits. Is there a workaround for this?
I could ofcourse create a LV thread for this, but I liked the old one better
It was simpler and I didn't need to worry about threads so much.
All LV operations are going to be inside a DLL that is called from outside of LV, so I can't
use LV threads in a simple way, e.g. putting things inside a while loop. Just that you'll
know why I wan't to avoid using the threads.
Thanks.

It is possible to achieve this behavior using the DAQmx API by using the DAQmx Create Task VI to explicitly create the task (rather than relying on DAQmx Create Channel to do it implicitly) and setting the AutoCleanup attribute to False. This method prevents LabVIEW from automatically clearing the task when your VI (or the function you'll be exporting to your C .dll) finishes executing. The disadvantage is that you might accidentally "leak" a task if you're not careful. In order to stop the pulse generation on command, you can either reset the device or somehow store the task name you created and come back later to call DAQmx Stop and/or Clear Task.
Here's how you would start the generation:
...and how you could come back and stop it later, using the task name you created:
Hopefully this helps-
Message Edited by Tom W [DE] on 11-16-2007 07:54 AM
Tom W
National Instruments
Attachments:
autoCleanup.JPG ‏17 KB
clearTask.JPG ‏4 KB

How to generate sequence of pulse trains with DAQmx?

I need to generate a sequence of pulse trains with DAQmx (the card I have is a PXI-6229 card). As an example:
- 10'000 pulses at 20kHz every 5 seconds with an initial offset of 2 seconds (let's say 10 pulse trains in total).
If I use the CreateVirtualChannel.vi in "CO pulse ticks" mode, I can only specificy offset, high ticks and low ticks, but not that the sequence of pulses should be repeated after some time.
Now I thought that I could solve this problem if it were possible to multiply two counter outputs: the first counter would generate the pulses (continuously) whereas the second one would switch between low and high on a slower timescale in order to gate the first counter, thereby providing an initial offset and the "off" phases between the pulse trains.
Is it somehow possible to multiply two outputs with DAQmx and the card I have? Or is there another solution to the problem?
Thanks a lot in advance for any hints!

Hi dlanger,
what you want to do requires a little bit more work.
First look at the example "Gen Dig Pulse Train-Continuous.vi" from the LV example finder.
This example generates a continuous* pulse train. As you see, you need a sample clock VI for setting the sample mode.
* NOTE: Generating a finite pulse train with a M-series card requires 2 counter.
With a pause trigger (DAQmx trigger property node) you can gate the output of that counter.
Now you have to generate a gate-signal with the the 2nd counter. That means, only if Ctr1-out is high Ctr0-out outputs the 20 kHz-signal.
Maybe you have to adjust the times in my example a bit.
Unfortunately there is just one "small" problem: "let's say 10 pulse trains in total"
This is not possible, because a 3rd counter would be necessary (*).
As a workaround you can modify the while-loop that both tasks are cleared after 50s. This is not brilliant, but should work fine for you.
A more sophisticated way is to perform a correlated DIO. So you can generate custom pattern for multiple outputs.
A good example can you find here:
Retrigger and Repeat Finite Digital Pulse Train in LabVIEW
http://decibel.ni.com/content/docs/DOC-8473
or here:
Generating More Than 2 Pulse Trains Using CompactDAQ
http://decibel.ni.com/content/docs/DOC-2167
Hope this helps.
With best wishes,
Ralf N.
Attachments:
Gen Gated Dig Pulse Train-Continuous.vi ‏38 KB

Pci 6602: configuring a frequency-divider with daqmx using labview7.1

i´m using labview 7.1 and the pci6602 counter-board. i want to configure a counter as an frequency-divider with varaibale division-rate, witch is a easy thing to do with the classic "old" daq-driver.
it´s recommended to use the "new" daqmx-driver, and i want to do so, cause i´m using also other ni-devices and want to use the same driver for all of them, but i can´t find any possibility in the daqmx-vi´s to configure such a frequency-divider.
i also couldn´t find any example-code for this problem.
please help me!!

hi, thanks for the answer, but unfortunatly it´s not what i ment.
i need to configure a counter on the pci6602 wich divides down the frequency "f_in" of the square pulses connected to it´s "source" pin by "divisor" and puts out square pulses with frequency f_out=f_in/divisor at another pin. That process should take place only on the 6602-board without using the cpu.
i´ve found the solution already, how to configure a counter on the pci6602 with daqmx like described above. see attachment.
servus
markus
Attachments:
Divider_Config_mw.vi ‏40 KB

Problem with DAQMX on a 6025E !!

Similar Messages

Maybe you are looking for