Channel config with daqmx

Hi,
how can I set the config for the first, the second and the fourth channel on the daqmx-config?
I tried with dev1/ai0:1,3 but this is not working.
thanks for any help
yves

Hello Yves,
The syntax for a channel list is outlined in the DAQmx help file under "channels, physical syntax" in the index, or by searching the help for "Physical Channel Syntax".
Try following for your configuration:
Dev0/ai0:1, Dev0/ai3
RegardsMessage Edited by Indiana on 04-21-2005 09:14 AM

Similar Messages

  • 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

  • Selecting physical channel from list with DAQmx

    I'm trying to write a simple VI for reading and writing digital data. However, when I have a DAQmx physical channel control, the only options it presents to me are the various analog inputs (and doesn't allow me to type in the port I actually want to use). In other examples, e.g., "Write Dig Port.vi", the apparently identical control instead shows me digital port options rather than the analog in channels. As far as I can tell, there is no real difference between the controls as there is nothing in properties that I can really modify.
    How can I get this control to let me choose the channels I want? Or is there some difference in these controls that I am not aware of?

    The channel lists adapts to the type of DAQmx Create Channel that you use. Do you see the text below the DAQmx Create Channel? If your channel is displaying only analog input channels, then the DAQmx Create Channel type is AI Voltage. If you want to use digital input channels, change the type to Digital Input. Click on the little arrow on the right side. This is called a polymorphic VI selector. You can do the same thing by right clicking on the VI and do a Select Type.
    Mark has a good point. If you change the type of DAQmx Create Channel and you already have a physical channel wired, you will have to go to I/O Name Filtering to change the channel types displayed. If you change the DAQmx Create Channel and then create a channel control by selecting Create Control, you'll get the correct type automatically.
    Message Edited by Dennis Knutson on 03-11-2008 12:12 PM

  • NI-6062E FM signal generation with DAQmx

    Hi everyone,
    I am trying to use the NI-6062E DAQ card to generate an AC voltage signal and I found 2 relevent example:
    (1)Cont Gen Voltage Wfm-Int Clk.vi found in LV7.1 DAQmx examples
    (2)Function Generator with FM.vi also found in LV7.1 examples
    But I have it hard to implement the 2nd vi directly into the 1st one and it looks like I have to make change to the subVIs?
    I am trying to modulate a 500Hz sine wave with frequency of 10Hz, can anyone help?
    Thank you!

    rpursley8 wrote:
    Are you trying to do this as a real-time signal or are you generation the waveform ahead of time and sending it out?
    An FM modulated signal is defined as
    f(t) = A*cos(2*pi*fc*t + m*sin(2*pi*fm*t))
    where
    A = amplitude of signal
    fc = carrier frequency (500 Hz)
    m = modulation index (how big of a swing in frequency that you want)
    fm = modulation frequency (10 Hz)
    pi = pi
    so a formula node might be the easiest way. To generate a complete cycle, you will have to generate 0.1 seconds of data, then you could repeat it continuously without any discontinuitues.
    Clearly the carrier and modulation can be something other than sinusoids, but this is how it is usually represented.
    Attached is an example of generating the waveform.
    Hi Randall,
    Thank you for your reply, yes and I am trying to generate this real time signal on the NI-6062E Analog Output channel, but I find it difficult to insert either your example or the example FM vi from LV7.1 into the following VI?
    I think it also needs to deal with hardware channel config (for sample clock rate) using DAQmx? or I need to make change to the subVI such as Waveform Buffer Generation.vi or even further the Basic Function Generator.vi?
    Thank you for your patient.
    Regards
    Rolly
    Attachments:
    Cont Gen Voltage Wfm-Int Clk.vi ‏83 KB

  • 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

  • Multicam Clip Audio Channel config greyed out

    I shot an interview with two cameras.  One of those cameras had the audio (lav on left, boom on right).  That audio was imported as a stereo track on import, the angles where multicamed, and the edit happened.
    Now I have a timeline with all my audio playing in stereo (lav on left boom on right).  I want to change from stereo to dual mono so I can audio mix properly, but when I select the multicam clip in the timeline, the channel configuation in the inspector lists it as stereo and the dual mono option is greyed out. (don't know why they won't let me change here)
    I can go back to the event and select the multicam clip there and change it to dual mono and it will also change in the timeline.  So that seems like a work around, but I can't select MULTIPLE multicam clips in the event and batch change the channel config to dual mono.  Says "selected clips are from different multicam clips."
    Am I going to have to select every single multicam clip individually in the event browswer and change the channel configuration on each one? 

    As far as I understand it, you cannot switch a "container" clip like the multicam to dual mono since it contains a clip which is stereo inside it. This makes sense, as per se it is not the multicam that is stereo or not.
    You should make the change from stereo to dual mono in the actual AUDIO clip - either before creating the multicam, or after - in this case, after :-)
    Open the multicam clip in Angle Editor (control-click the clip in the timeline and choose "Open in Angle Editor").
    Now select the clip that contains the audio and make the change. Note that this WILL affect the relevant clip even outside the multicam.

  • 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 do I read an AI and DI channel simultaneously in Daqmx?

    I'm trying to do something very simple: read a single AI channel and a single DI channel with Daqmx and display them on a waveform chart. It's not working. I'm doing something wrong and none of the sample codes available in the Knowledge base cover an analog input and a digital input. I'm trying to read continuously at 250 samples per second, align the timestamps and display the result on a waveform chart. The analog data shows up twenty seconds later than the digital data when I get anything at all. Please take a look at my diagram and tell me what is wrong. The device is a USB-6218 running on a laptop running Windows XP and LabVIEW 8.2.
    Attachments:
    Read Daqmx DI and AI channels.vi ‏24 KB
    Align Timestamps.vi ‏15 KB
    Daqmx Globals.vi ‏9 KB

    Could you provide some actual values for sample rate and number of samples instead of those silly globals? Also, you have nothing to configure the digital timing.
    I also don't understand your comment about not being able to find an example. There's one called Multi-Function-Synch AI-Read Dig Chan. It's under Hardware Input and Output>DAQmx>Synchronization>Multi-Function. Try that.

  • Multiple tasks with daqmx

    Hello,
    I am currently working on a Senior Design Project where I have to measure torque, RPM, pressure and temperature.  I am using strain gages, a Hall Effect Sensor, pressure sensor and thermocouples to obtain these readings.  A myDAQ collects the RPM and pressure readings while a cDAQ collects the torque and temperature readings with the NI 9237 and NI 9211 modules.  I created LabVIEW VIs for each sensor and they work.  The problem I am having is when I try create a VI with DAQmx that reads all these sensor values simultaneously.  The VI that I have attached randomly displays one of the measurements while all the other measurements remain blank.  How should I edit my VI so I can display all my readings at once?
    Solved!
    Go to Solution.
    Attachments:
    SD.vi ‏87 KB

    You can form all of your cDAQ readings into a single DAQmx task.  Do the same for the myDAQ channels.  On the read side, you just read multiple channels.  You can then use the Array Index to separate your channel data and do whatever calculations you need.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    Multichannel task.png ‏40 KB

  • Can I measure pulswidths with daqmx base and NI-USB6501

    Can I measure pulswidths with daqmx base 1.4 and NI-USB6501? I can measure edges width this function: DAQmxBaseCreateCICountEdgesChan. But, when using DAQmxBaseCreateCIPulseWidthChan I always get an error message back (DAQmxBase Error: <err>Value passed to the Task/Channels In control is invalid).
    I also cannot find any examples about this topic in the software on CD nor on the internet.
    I also don't know what values to use for the float64 minVal and float64 maxVal arguments when using the pulse width function of above (see the NI-DAQ™mx Base 1.x C Function Reference Help).
    Maybe my device (NI USB6501) cannot measure pulse width's and when it does measure pulse width's, what value will it give back? Seconds or ticks and what is the accuracy?
    Ok, enough questions for now. Thank you in avance for answering.
    D. Stollman

    The USB-6501 counter is capable of falling edge edge counting
    measurements only, so the type of measurement you wish to do is not
    possible with that device.  The data sheet for the USB-6501 can be
    found at the following link:
    http://www.ni.com/pdf/products/us/20054920301101dlr.pdf
    I believe the DAQPad-6015 and DAQPad-6016 USB devices are capable of
    measuring pulse width, as well as many of NI's PCI data acquisition
    devices.

  • Error -200141 when doing buffered events with DAQmx and PCI-6602

    When doing buffered events with DAQmx and PCI-6602 I get error 200141 - Data was overwritten before it could be read by the system.
    This error is generated ONLY with random inputs >200/sec.
    My setup is :
    DAQmxCreateCIVCountEdges(taskhandle,"Dev1/ctr3"....
    DAQmxCG+FGSampClkTiming(taskhandle,"/Dev1/FPI35",...
    DAQmxSetCICountEgdesChan(taskhandlem,"", "/Dev1/80MHZTimeBase")
    DAQmxSetChanAttribute(taskhandlw,",",DAQmx_CI_DataXferMech,DAQmx_Val_DMA,0);
    Can somebody help ?

    i'm getting the same Error-200141, while reading semiperiods. (Meas_Buffered semiperiod continous)
    while loop ex.rate seems to be pulsewidth*no.Samples to read. in my case PW=60ms
    Input buffer size measured with Property node= 10000
    why this error happens?? i cant use any mode other than implicit timing for semi-period measurement right??
    more info: all the ai channels are used ~ 16 differencial.
    i found one solution which is _ reinitializing the whole task if an error occur. is this the right way??
    Kudos always welcome for helpful posts
    Attachments:
    Counter_1_Meas Buffered Semi-Period-Continuous_main_lv09.vi ‏34 KB
    SemiPeriod_Reconnect Counter on Error.vi ‏35 KB

  • Iak file does not change channel config?

    I am relatively new to Lab-View so please bear with me
    I have multiple iak files setup for different vi's that require some different ranges on the AI-100 modules I am using (FP-1601 Ethernet module). My problem is when I start a vi, with the iak file path needed wired to the FP-open tag, it does not change the channel configuration from whatever is currently on the modules themselves.
    Is this correct? I know I can get the channels to update to the iak file by opening it in FP explorer and editing the device clicking on the channel config and syncing to the file. This will be very tedious for the un-trained test monkey these different programs are designed for. Am I missing some option somewhere that syncs the modules t
    o the iak file when you open a field point session?

    From a program perspective, the IAK file is solely used to provide channel mapping information. From a FieldPoint Explorer (or NI-FP) perspective, the IAK file contains all channel naming information, communication mapping information and channel configuration information. In FieldPoint Explorer (3.0.2 or less), the only way to change the channel configuration between IAK's, is to switch IAK's in FP Explorer and right click on each (and every) FieldPoint IO Module, choosed Edit This Device and then choose Channel Configuration. When the dialog box asks you whether to use the Device or File settings, choose File. In NI-FP 4.0, there exists an option to download the entire configuration to an entire bank at a time, but there is still no method of downloading the co
    nfiguration file programmaticly at run time.
    However, another option in the form of the Ethernet Configuration VI's exists. They allow you to programmatically configure each channel (range & attributes). For an understanding of the range and attribute values, you can cross reference the FP-1000/1001 Programmers Reference Manual.
    Regards,
    Aaron
    Regards,
    Aaron

  • An issue with DAQmx Error messages

    Greetings,
    I'm using a 6602 counter board with DAQmx 7.4, ANSI C API.  A strange issue concerning the errors due to faulty attribute values keeps occuring, that being no error is reported when the (faulty) attribute value is set but only when it is read back afterwards.  Shouldn't the faulty value be reported by the Set function?
    To be specific, I'm creating a period measurement counter input channel with implicit timing, sample mode = finite, then setting the number of samples per channel to 0 (bear with me, I know the 0 value makes no sense here, the point is how the errors are being reported so that they can be handled in a reliable and consistent way).  While DAQmxSetSampQuantSampPerChan(taskHandle, 0) does not produce an error, calling DAQmxGetSampQuantSampPerChan(taskHandle, &SampPerChan) for verification on the very next line returns Error -200077 : "Requested value is not a supported value for this property".  So, my question is why the error is reported by the Getter instead of the Setter?  Is this normal behavior (if so why?) or is something amiss here?
    Jeff

    This is the expected behavior. Validating attributes is tricky when attributes are dependent upon other attributes. There are two main approaches that can be taken by NI-DAQmx.
    One, when every attribute is set, NI-DAQmx could verify the value of that attribute in the context of the task (i.e., in the context of all other attributes). This is problematic for at least a couple of reasons. One, validating the task after every attribute is set is time consuming and not efficient. Two, validating the task after every attribute is set requires that customers set attributes in a specific order such that dependent attributes are set after their dependencies. This would dramatically decrease the usability of NI-DAQmx. In fact, if attributes are mutually dependent, this approach is impossible.
    The second approach is that NI-DAQmx doesn't verify the task until it is forced to do so. Starting a task forces it to be validated. Querying an attribute also forces the task to be verified since the value of an attribute may be dependent upon the value of another attribute.
    As you've noticed, we've taken the second approach with NI-DAQmx. This approach leads to a more efficient execution as well as allow customers to set attributes in an arbitrary order. If you want to force the task to be verified in order to check for errors, you can do so explicitly at the desired time. However, the need to check attributes for errors is most often needed when the application is under development and the NI-DAQmx error reporting features makes it easy to determine which attribute has been set to an invalid value even when that error is not reported immediately.
    Now, in reality, the way NI-DAQmx handles attributes is a bit more complicated than what I just described. Since some attributes are not dependent on other attributes or, since some attribute values can never be valid regardless of the values of other attributes, these attributes are verified when they are set and errors are returned immediately. We refer to this as coarse attribute verification. For example, if you set the sample rate to 100 MHz on an E-Series device you will immediately get an error.
    Hope this helps clarify the behavior.
    geoff
    Geoffrey Schmit
    Fermi National Accelerator Laborary

  • 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

  • Solo Button in Channel Strip with Red Line

    Solo Button in Channel Strip with Red Line through it and it won't solo?
    How'd it happen and how do you get rid of it?
    Thanks!

    Try This----From the Manual
    Logic Pro, Express: Solo Safe mode may not remain disabled for a particular channel strip
    Symptoms
    In certain projects, "Solo Safe" mode for a channel strip may enable each time you load the project, even after you disable it and save the project.
    Resolution
    When a channel strip in Logic is "Solo Safe", it remains audible, even when other channel strips are soloed. Solo Safe is indicated by a diagonal red line through the solo button on a channel strip.
    You can manually toggle the solo safe status of a channel strip by Control-clicking its solo button. There are times when you may find that a particular audio channel strip in a project reverts to solo safe mode when you load the project, even after you manually disable solo safe. Here is why that may happen and steps you can take to prevent it from occurring.
    A Logic project contains a special audio channel strip used for pre-listening to audio in the Sample Edit window, Audio Bin, and Loop Browser. When you create a Logic project from one of the factory templates, this channel strip is assigned to "Audio 256". This channel strip stays in solo safe mode so that you can always preview audio. The image below shows the channel strip for a new, empty project.
    If there is no audio channel strip in a project assigned to "Audio 256", Logic will use the highest-numbered available audio channel for pre-listening. When the project is loaded, that channel strip will be put into solo safe mode. You may find this happens in older projects that you open in Logic 8, or in cases where you have deleted the "Audio 256" channel strip in a Logic 8 project. To prevent this from affecting channel strips you are using in a project's arrangement, follow these steps:
    Choose Window > Environment.
    From the Environment window menu, choose New > Channel Strip > Auxiliary. A channel strip will appear in the environment.
    Select the channel strip. It will highlight.
    In the Device parameter box in the upper left of the Environment window, click the arrows to the right of "Channel" and choose Audio > Audio 256 from the menu.
    Select the text tool, click on the name below the channel strip and name it "Prelisten".

Maybe you are looking for