AI Waveform Scan Conversion of VI to LaqbVIEW 7.1

Hi,
I have a labVIEW program written in version Labview i think 5.1 or 6.0.  Im using labVIEW Version 7.1 and when I run the simulation it gives me error 10401.  I dont really understand what it means, but I am assuming that I cannot use AI Waveform Scan VI, therefore I must replace it.
Does anyone know any VI for the DAQmx that has the same properties such as channels, number of scans, scan rate,???
I would appreciate any help Thanks
Sophie

Sophie,
Can you verify that you have traditional DAQ installed?  If you open MAX, then expand the software tab do you have "Traditional NI-DAQ" listed?  If not, then this would explain why you are seeing the -10401 error.  If you do not have it installed you should be able to download it from this site:
http://digital.ni.com/softlib.nsf/websearch/C36A54ADDA3DC33D86257038004E55E6?opendocument&node=13206...
If it is installed then when you expand the "Devices and Interfaces" tab, you should have 2 categories, DAQmx devices and traditional DAQ devices.  You should expand the traditional daq devices tab.  From here you should be able to run Traditional DAQ's test panels on the device.  If this works, then you have verified that your drive is installed correctly and that your device is also functioning.  If this is the case, then something you are inputting in your VI is likely in error.  If this is the case, feel free to save the VI (make the values you are attempting to use default before saving) and post it here.  Also, if you could post the version of NI-DAQ you have installed as well as the hardware you are using it may be helpful.
Hope this helps,
Dan

Similar Messages

  • AI Waveform Scan(scalled array).vi

    I am getting data from AI Waveform Scan(scalled array).vi; the output is 2-D array, which I pass through Index array (with index value 0) to get data from one channel. It's output (1-D array) I pass to subvi which is only formula node within while loop(which was implemented for further development).
    So what I expected to see on my formula node input was 1-D array of DAQ AI data(at least 1000 as this sets number fo scans value)
    To my suprise I can see only one input value.
    The application flow is as follows:
    - While loop is preparing array of sinusiod data
    - Sinusoid data are passed one at a time to AO using sequence loop
    -  Next sequence reads data from AI
    From above description it's obvious, that 1-D array can only be represented as one value at each loop execution.
    My question is how to store in memory all consequtive AI data to array of i.e. 1000 samples and then process the data further?
    Thanks
    robert

    Hello,
    It sounds like you may be using a FOR loop and it auto-indexed the array by default at the input.  Either that, or you are having trouble passing the array to your formula node.  If you are trying to pass an array into the FOR loop and avoid the auto-indexing, you simply need to right click on the array's tunnel into the loop and select "Disable Indexing" - SEE THE ATTACHED SCREENSHOT.  For help with formula node syntax, you'll find great documentation in the LabVIEW Help, which is linked from the Context Help (just click CTRL+H and hover over the formula node).
    I hope this helps!  If you continue to have trouble, please try to be as specific as possible about which function or structure you are having trouble with, and perhaps attach a screenshot with an explanation.
    Thank you,
    Best Regards,
    JLS
    Message Edited by JLS on 04-19-2006 03:35 PM
    Best,
    JLS
    Sixclear
    Attachments:
    autoindexing.JPG ‏12 KB

  • How do you clear the chart in an AI Waveform Scan VI upon program start?

    I am using a waveform scan vi in a program. The output of the vi is set to "Waveform". What I want to do is have the program automaticly clear the waveform chart each time the program starts. Currently I must start the program, right click on the chart and select clear. I have attempted to use the chart history property node, which I assumed is the correct path to take but so far my attempts have been unsuccessful.

    Ahhh, waveforms... These got better in LV 7 I hear.
    Will this do it?
    2006 Ultimate LabVIEW G-eek.
    Attachments:
    Problem_example.vi ‏41 KB

  • "AI Waveform Scan" family of VI's is in what LLB?

    MY LV 7.0 VI is requesting some VI's not installed in LV8. They are:
    "AI Waveform Scan",
    "AI Waveform Scan (waveform)"
    "AI Waveform Scan (scaled array)"
    In what LLB are they located, or where do i get them???
    Thank You.

    They are part of the traditional NI-DAQ libraries as answered in your other post. Install traditional DAQ from your Drivers CD or download the latest.

  • DVI scan converter for under $1000?

    I've just gotten some e-mails which indicate DVI scan converters are downright expensive. Considering many DVI HD-TVs are now well under $1000, you'd think that you could get a scan converter for less. Sure there is DisplayConfigX and SwitchResX, but they are complicated to setup, and it appears not all HD-TVs respond well to them. So here's the question, anyone know of a simple DVI based scan converter that will reduce the picture so that all four sides of the screen which are overscanned on my set actually appear on my HD-TV? I don't want to have to step down to VGA just to do scan conversion. Right now the VGA scan converters are only $200 to $300 depending on where you look. Why some companies charge as much as $12,000 for DVI versions is beyond me!

    there are scan converters that do the simple job of converting a signal from 1 format to another then there are converters (scalers) that are designed to take NTSC (or PAL, SECAM, etc...) material and upconvert it to a higher resolution. back in the day when we used to deal with $50,000 9" gun CRT front projection systems, they often used $30,000 boxes that did the scan conversion. with CRT based systems on a large projection screen, you can actually see the black gap between the scan lines of the electron beams. the original reason to upscale NTSC video to different formats (differente VGA resolutions, really) was to increase brightness, not increase detail... for the higher the resolution, the smaller the black lines in between the scan lines on the screen. the reason that this is not so easy to accomplish is because film, which was originally shot in 24 frames per second, is being asked to play back on a device that is 60, 80, or higher frames per second (the vertical refresh rate). when dealing with film, you are of course dealing with people who are very critical with all technical processes being applied (rightfully so) and the same with the viewers. when done incorrectly or without proper processing, this scan rate conversion is visible by "rips" or jittery motion artifacts during playback.
    because more and more of today's modern sources are digital (DVI and HDMI) and the display devices are also digital (LCD, DLP, and plasma) scan converters and scalers are somewhat obsolete. it is still downright confusing, though. 1080i from an HD-DVD is played back at 1080p. 1080p from a Blue Ray player is played back at 1080p. HDMI, while supposed to make life simpler, actually has a whole list of incompatible sources and display devices with more HDMI #.# versions to come.
    i retract my statement, scan converters are no longer obsolete, they are just packaged with the display devices and sources so there is no market for them. a 480p DVD player with DVI out does not really give you a 480p output direct from the 480p MPEG stream. the video DSP takes the MPEG, internally outputs 480i, then the built in converter processes it back at 480p. seeing how these DVD players are very cheap, there no longer is a market for affordable scalers. you now have the all or nothing scenario where the only vendors alive rely on high end clients that want to pay for the best and not settle with what is bundled.
    anyways, some of the companies still in the business...
    Faroudja (recently bought by Meridian UK)
    DVDO
    Silicon Image
    Focus Enhancements (exiting / exited the market?)
    Snell and Wilcox
    gefen (is a newcomer beginning to offer some product)
    i'm sure that i'm missing a bunch, but these are the ones that i recall off the top of my head

  • Mini to Analog TV...

    Which apple adapter would one need to connect the new early 2009 Mac Mini to a TV using RCA video cable?
    I have a Mini DVI to Video adaptor but that does not work.
    Appreciate any info.

    Based upon the discussion in this thread:
    http://discussions.apple.com/thread.jspa?threadID=1926928
    I doubt that setup is going to work. A standard definition TV is a poor computer monitor anyway, since (as I noted in that thread) the effective resolution is 640x480. I suspect the problem with using the setup may be a lack of scan conversion, since a simple conductor swap or merge will not compensate properly for the fact that the TV uses an interlaced scan and computers use progressive scan.

  • Mac connect to Tv using RCA

    Hello  Guys,
    thanks for reading this post.
    01. I have old Macbook 2.16 Black running 10.6.8 and I want to connect the My OLD tv in to this Macbook,
    I already tried to bought the Mini DVI to RCA converter and it didnt work, then i found out some of macs are not compatible with that adapter
    I have another adapter which is mini DVI to DVI, so i am thinking to use this adapter as following method
    01. buy new DVI-I Male To 3 RCA Female Component VIDEo Adapter Converter that connect with cables to tv
    somehting like this :--> http://www.ebay.com/itm/DVI-I-Male-To-3-RCA-Female-Component-VIDEo-Adapter-Conve rter-/400404289012
    02. Connect that in to mini dvi to dvi  conveter which is fixed to mac,
    So the Question is , Will this setup works ? maybe anyone tried this before ?
    Thanks in Advance

    Based upon the discussion in this thread:
    http://discussions.apple.com/thread.jspa?threadID=1926928
    I doubt that setup is going to work. A standard definition TV is a poor computer monitor anyway, since (as I noted in that thread) the effective resolution is 640x480. I suspect the problem with using the setup may be a lack of scan conversion, since a simple conductor swap or merge will not compensate properly for the fact that the TV uses an interlaced scan and computers use progressive scan.

  • How can i use two channels to show different voltages in DAQ ?

    my problem is that when i choose different channels to read the outputs from my sensors, it ignores the channels which i have choosen 0 or 1 and it puts 0 channel only for both sensors. and the result is one same reading at both output guages, one reading is steady and the other is fluctuating. how can i make it recognize each one differently, is the proplem at my programme ? help me please
    Attachments:
    fin.vi ‏58 KB

    Greetings,
    AI Waveform Scan.vi and AI Sample Channel.vi each have a Channel(s) input. You do not have anything wired to these inputs. By default, these inputs are both Channel 0. You should wire "0" to one of these inputs and "1" to the other.
    Good luck with your application.
    Spencer S.

  • Version 6 AI in version 8

    I am trying to create modify a VI that was created using labview v6.0.  I am modifying it in 8.0.  The old program uses the Analogue input VI called 'AI Acquire Waveforms'  I just uses a device number with the appropriate count, rate and other settings.  Instead I want to use a VI in the Universal Library for LabView with version 8.0 program.  The VI I specifically want to use is called AI Sc Fgd i think.  Same sort of idea, uses a 'Board number' instead of device number.  The main difference is that on the 'AI Acquire Waveforms' VI, the output wire type is a 2D array, an Actual period time, and an error out.  On the other AI Sc Fgd it has a single array of ADData type, an Actual rate, and an error out.  The 2D array must be transformed in order to be graphed.  So to ge to the point here, the old version does the transform and uses two Array Index VIs for index 0,1.  How can I make the same output for the AI Sc Fgd?  Thanks,
    -Tekky

    Hello Tekky,
    I can't find the 'AI Sc Fgd' VI you referenced.  Can you tell us where its located on the function palette?  The AI Acquire Waveform VI is a Traditional NI-DAQ VI that is available in LabVIEW 8.0.  It is found in the functions palette under Measurement I/O > Data Acquisition > Analog Input.  If you don't have this palette, you may need to reinstall Traditional NI-DAQ 7.4.1 and make sure support is enabled for LabVIEW 8.0.  The AI Acquire Waveform VI can either output a 1D array of DBLs or Waveform data, and you can select which format to output data by right-clicking on the function and choosing Select Type.  The AI Acquire Waveform VI is a top level VI that contains the AI Waveform Scan subVI, which outputs a 2D array of DBLs.  The Index Array function is used to extract the first column of data, since its assumed that your only acquiring from a single input channel.  If the data from your function is already a 1D array, you should just be able to pass that directly to a waveform graph or numerical array indicator.
    Also, all these functions are Traditional NI-DAQ VIs.  Have you considered using the NI-DAQmx driver and function calls?  These functions are much easier to use and actually operate more efficiently.  More information about the NI-DAQmx functions can be found here:
    Learn 10 Functions in NI-DAQmx and Solve 80% of Data Acquisition Applications
    Also you can check to see if your DAQ device is supported under the DAQmx driver here:
    NI-DAQmx Driver Support Versions
    I hope this helps,
    Travis G.
    Applications Engineering
    National Instruments
    www.ni.com/support

  • Can version 7.1 work with a PCI-6024E?

    Hi! I've been trying to run a VI which is being successfully used in my lab to acquire data. However, whenever i try to run it i get stuck when the AI Waveform Scan VI file is being searched. Following your replies to similar questions i've made sure that the traditional NIDAQ is properly installed. is it possible that my data acquisition card (PCI-6024E) cannot support ver. 7.1? what do i do next?
    Thanks,
    Tamar

    from what i understand from your post, your problem has nothing to do with the card.
    your vi cannot run because a subvi is missing: AI Waveform Scan. it is probably in a different library than on the original computer (i would guess the original computer has a different version of LV installed). maybe it is one of the examples in a previous LV version?
    Either way, the easiest solution for you is to go to the original computer, save your vi with all dependencies (as an llb for example), and try again on the new computer.
    ... And here's where I keep assorted lengths of wires...

  • How do I update a program written for a Legacy DAQ into one for a USB DAQ?

        I am trying to rewrite a program, replacing all of the AI Waveform Scan and AO Update Channel VIs in it with DAQmx VIs. This seems to be the only way for the USB DAQ to respond to the program and not get any errors. I was just hoping for some help in how to replace those VIs with updated DAQmx ones. Attached is the part of the program that I am working on. There is a slight error because of some changes I have made, but the gist of the program is still there.
    Thanks!!
    Attachments:
    DAQdriver.vi ‏52 KB

    What I would suggest is that in either your init state or outside the loop, create two separate tasks for the analog in and the analog out. This means using separate DAQmx Create Channel, DAQmx Timing, DAQmx Start Task, etc. Then, you would have the tasks in your shift registers and pass just the appropriate task to either a DAQmx Write or DAQmx Read. No need to pass channel or device. In the End state, you would add a DAQmx Clear Task for each.

  • Unable to reset DAQ error -10441 on PCI6111E

    Hi all,
    We have a problem with our PCI6111E (+ NIDAQ v6.9.1f28 + MAX 2.1.3.14 + LabVIEW 5.1) where while acquiring data we occasionally get -10441 & -10444 errors. When this happens the DAQ device reset, or restarting LabVIEW doesn't help & we have to restart the computer.
    Does anyone have any idea how to clear this error?
    I am using "AI Waveform Scan.vi" and "Device Reset.vi" from LabVIEW 5.1
    Thanks

    These are errors involving memory.
    Try adding more memory to the machine,
    or
    Reduce the number of samples to be read,
    or
    reduce the sample rate,
    or
    break your acquistion into multiple parts,
    or
    do continuous double buffered Acquisition.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Multiple AI channel reads with differant input limits

    I want to aquire two high frequency AI channel signals from my SCB-68 at the same time. The signal is coming from two seperate pressure transducers. One needs to be sampled at 2000Hz with a voltage range of -10V to 10V and the other sampled at 200000Hz with a voltage range of 0V to .12V. I have been using the AI Waveform Scan.vi to aquire the two channels. But that requires two seperate case structues and activating them in sequence.

    SCB-68 is just a connector block so it has nothing to do with your acquisition challenge. Some DAQ devices can be set up for different gains per channel, but others cannot. If your device cannot have different gains per channel, then you either need to do all the acquisition at +/-10 V and give up resolution on the other channel or use an external amplifier on the low voltage channel.
    Similarly, most DAQ devices cannot sample two channels at different rates. Acquire both channels at 200 kHz and use decimation or other processing to reduce the data to the equivalent of 2 kHz for the slow channel.
    Another option would be to use two DAQ boards and set the gains and sampling rates differently on each. The acquisitions could use a common trigger and with a sepa
    rate frequency divider could have synchroized clocks if that is important.
    Lynn

  • How to combine Digital Output, a delay and Analog Input in a fast loop

    I need to develop a process loop that runs at least at 250 Hz that performs a Digital output, than a delay of 50 microseconds and than an analog input of all the channels. All will be done using ATI MIO 64E3 card. Of course, the acquired data will be processed, displayed and saved. The loop will be running for several minutes until user stops it.

    The fastest and most precise timing will occur if you use hardware timing. You can apply hardware timing to analog input on the E Series boards, but not the digital lines. Let's focus on the analog input first. Continuous waveform scanning uses a scan clock, which can be the board's internal one or an external one which you apply. If you want to scan all the channels 50 microseconds after a digital rising edge, then you need an external signal to signify that scan clock.
    The E Series boards also have 2 counter/timers onboard that you can use for this purpose. You can set up a retriggerable pulse generation operation, where the counter receives a trigger and then on the user specifications, produces a pulse. You can have that route to the analog input scan clock.
    The trigger signal for the counter is that digital pulse. As I mentioned earlier, there is no hardware timing for the digital lines on an E Series board. We do have other digital boards (653x family) that have hardware timed operations if precision is important. If you are satisfied with software's resolution (in the milliseconds), then you can call the E Series board digital function in a loop with a software timer. That digital line can route to the counter to act as the trigger.
    So, on the programming side, you can have three separate and independent operations in parallel. One is for the digital function to output on that line every so often. Another is for the counter set at the retriggerable pulse generation. The last is for the analog input. I will describe this in terms of LabVIEW, but it can be done in a similar fashion with the NI-DAQ function calls or Measurement Studio.
    The digital examples are in the LabVIEW >> Examples >> Daq >> Digital >> E-Series directory. The Generate Retriggerable Pulse example is in the LabVIEW >> Examples >> Daq >> Counters >> DAQ-STC directory. The E Series boards use the DAQ-STC timing chip.
    Go to the LabVIEW >> Examples >> Daq >> anlogin >> strmdisk.llb directory and start with the Cont Acq to Spreadsheet File. This shows how to continuously acquire data and stream it to disk while displaying the data on a chart. Streaming to disk is the efficient way to save data while you are acquiring, as it eliminates the overhead of always opening and closing the file through the iterations of the loop. This saves to a file that can be opened by other applications (Excel, Word, etc.), but it is not as fast as writing to a binary file, which must be opened and read back through LabVIEW. However, for your ~250 Hz rate, it should be fine. Then, go to the LabVIEW >> Examples >> Daq >> anlogin >> anlogin.llb and look at the Acquire N Scans -ExtScanClk example. This shows how to apply the scan clock. Here, the AI Start that you saw in the previous example is replaced by 4 VIs (3 AI Clock Config's and the AI Control). Make those changes to the first example and then add a constant 0 to the AI Control parameter for total scans to acquire. That specifies the continuous operation. The File >> VI Properties >> Documentation menu item of the example describes the physical connections.
    If you aren't using LabVIEW, use the NI-DAQ User Manual and the NI-DAQ Help file installed on your machine. You can look at your AT E Series User Manual at the http://www.ni.com/manuals pages for more information on the hardware. Also, if you want to route those signals internally on the board, you can find some entries in the KnowledgeBase at the http://www.ni.com/support pages.
    Regards,
    Geneva L.
    Applications Engineering
    National Instruments
    http://www.ni.com/ask

  • ErrorsI after NI-DAQ 6.9.1 Upgrade

    I have LabView 6.0, Student Edition.
    With NI-DAQ 6.8 that came with it, I can open vi's created with the Solution
    Wizard just fine.
    But whenever I try to upgrade to NI-DAQ 6.9.1 to get full support for my
    DAQCard 6024E, I get errors about missing subVi's.
    These are the steps I take:
    * Launch LabView
    * On the initial dialog, I click on DAQ Solutions
    * Click Next
    * Choose Custom DAQ Applications, and click Next
    * Select Digital Input, and select Single Digital Line and the appropriate
    Digital Input Device and Line as configured in MAX. Click OK.
    * Click Open Solution
    The resultant VI won't run, I get errors:
    * Get Channel Information.vi subVi is missing
    * Read from Digital Line.vi is missing
    In fact, all solutions a
    re broken. If I choose the Digital Multimeter, for
    example, I get the errors
    * 'dmm acquire 5.vi' is not executable
    * AI Waveform Scan.vi subVi is missing
    These solutions all work OK, until I upgrade to NI-DAQ 6.9.1. I have
    reinstalled everything from scratch several times, same results.
    Any ideas?
    thx
    Jeff

    It comes with the book Learning with LabView, ISBN 0-13-032550-3
    Jeff
    "Jim Adams" wrote in message
    news:9f6kgv$o3e$[email protected]..
    > Jeff,
    >
    > I'm most interested in your opening statement.. "I have LabView 6.0,
    Student
    > Edition". I wanted to buy a 6.0 student edition for a summer intern that
    I
    > am mentoring, but was told that the PC version is out of print, and only
    the
    > Mac version is available. So my question to you... is your platform Mac
    or
    > PC. And if PC, could you shed some light as to where you purchased your
    > student edition?
    >
    > Thanks,
    >
    > Jim
    >
    >
    > JeffD wrote in message
    > news:JZxP6.30465$[email protected]..
    > > I have LabView 6.0, Student Edition.
    > >
    > > With NI-DAQ
    6.8 that came with it, I can open vi's created with the
    > Solution
    > > Wizard just fine.
    > >
    > > But whenever I try to upgrade to NI-DAQ 6.9.1 to get full support for my
    > > DAQCard 6024E, I get errors about missing subVi's.
    > >
    > > These are the steps I take:
    > >
    > > * Launch LabView
    > > * On the initial dialog, I click on DAQ Solutions
    > > * Click Next
    > > * Choose Custom DAQ Applications, and click Next
    > > * Select Digital Input, and select Single Digital Line and the
    appropriate
    > > Digital Input Device and Line as configured in MAX. Click OK.
    > > * Click Open Solution
    > >
    > > The resultant VI won't run, I get errors:
    > >
    > > * Get Channel Information.vi subVi is missing
    > > * Read from Digital Line.vi is missing
    > >
    > > In fact, all solutions are broken. If I choose the Digital Multimeter,
    for
    > > example, I get the errors
    > >
    > > * 'dmm acquire 5.vi' is not executable
    > > * AI Waveform Scan.vi subVi is missing
    > >
    > > These solutions all work OK, until I upgrade to NI-DAQ 6.9.1.
    I have
    > > reinstalled everything from scratch several times, same results.
    > >
    > > Any ideas?
    > >
    > > thx
    > >
    > > Jeff
    > >
    > >
    > >
    >
    >

Maybe you are looking for