Equivalent of Split Signals for digital waveform

Hi , I read multi digital waveforms in a loop and I would like to split the channels. For analog waveform I can simply use split signals control. How about digital waveform, is there any equivalent for digital channels?

You can use firstly "Digital to Boolean Array VI" to get a 2D boolean aray equivalent of Digital Waveform samples...!!
But remember at this step, the sampling rate information (dt) will be lost (after you've converted the digital waveform to 2d array of boolean)...
Now next, if I'm not wrong, here each column would represent different waveforms...!!
At last, you can use "Boolean Array to Digital VI" to convert 2d array of boolean back to digital waveform...!! You will require dt (sampling rate info) here at this step...!!
Additionaly to extract sampling rate info from the digital waveform, before you convert it to boolean array, you can use "Get Waveform Components (Digital Waveform) Function"
I am not allergic to Kudos, in fact I love Kudos.
 Make your LabVIEW experience more CONVENIENT.

Similar Messages

  • How to split digital waveform channels?

    Hi , could you please let me know how can I split the digital channels of a digital waveform(Let's say the digital waveform has 6 channels ) and graph them seperately.
    It is very easy to split analog waveform signals ( acquired using N channel N sample) but I don't know how to do it for digital waveforms. 

    tintin_99 wrote:
    Let's say I have acquired the digital signal at 1MS/s / Now I want to decimate the number of samples to 1kS/s. Again I know how to do it for analog signal using the decimate function. Do you know a way to do it on a digital signal?
    Decimation make sense only to ANALOG signals, as ANALOG signal are continuous and can have any value (within defined range) on the other hand, DIGITAL signals can have just two states (0 or 1), so when you talk about decimating a DIGITAL signal, you need to come up with an algorithm, how you want to knock off the sample data points (say every alternate sample)....!!
    I am not allergic to Kudos, in fact I love Kudos.
     Make your LabVIEW experience more CONVENIENT.

  • Digital waveform reference library for windows 7

    Hi,
    Where can i find digital waveform reference library for JTAG/SPI/I2C for windows 7 I was only able to find it for windows vista/XP
    Thanks
    chintan

    Hi chintan,
    What reference libraries are you referring to that are only for XP/Vista and not Win 7? Can you point me to where you found that?  When I searched, I found these three links. Are these the libraries you're inquring about?
    - JTAG Digital Waveform Reference Library
    http://zone.ni.com/devzone/cda/epd/p/id/6157
    - I2C Digital Waveform Reference Library
    http://zone.ni.com/devzone/cda/epd/p/id/6080
    - SPI Digital Waveform Reference Library
    http://zone.ni.com/devzone/cda/epd/p/id/6163
    The VI's listed on these pages were originally written for LabVIEW 8.2, 8.5, and 8.6, but they should still work all versions of LabVIEW up to the most current version 2010 SP1. Are you having problems opening these? Any specific errors you're seeing?
    Also, I'm not sure if you've seen this document yet or not, but this is a tutorial addressing exactly what you're describing.
    - Serial Protocol Communication Reference Design for Digital Waveform Devices
    http://zone.ni.com/devzone/cda/epd/p/id/6200

  • JTAG Digital Waveform transfered using USB or parallel port ?

    Hi all
    I was wondering if there is a way to send JTAG Digital Waveforms generated by LabVIEW into a parallel port or USB port.  I know that there is a way to use DAQmx devices with JTAG Digital Waveforms where DAQmx drivers take JTAG Digital Waveforms and transfer that into physical signals which is then send to UUT.  I really am in a need to try to mimic whatever a DAQmx can do to make that happen with a parallel port or usb port. I would really appreciate if you can help me it is very urgent.
    Thanks

    Hi Cristopher
    I do really appreciate for a quick response. I am full aware of the fact that NI products for digital waveform generation will do the job, plus it is easier to implement them. However my goal is to use an inexpensive device that can generate external timing and my JTAG library and make .exe files from my final code and distribute that setup for several computers in factory. So buying several digital waveform generators from NI for each PC in factory will be a very expensive option. I think now you have a better picture why I am trying to find another inexpensive way to implement these digital waveforms using JTAG library. It would be ideal if I can use parallel port with some external timing to do the trick but I am really not sure where to start. Cirstopher I would really appreciate if you can come up with any suggestions in regards to this problem that I am having.
    Thanks again.

  • Counting number of 1's present in digital waveform obtained by converting the pulse signals.

    Hello,
    I am using Analogtodigital.Vi for converting the pulse sequences into digital.signals.I am able to get the digital waveform representaion of the pulses.
    But how to count the number of 1's present in the converted digital waveform.I want to count the number of 1's present in the converted digital waveform.
    Thanks in Advance.
    Solved!
    Go to Solution.

    Did you try opening the block diagram of Analog to Digital.vi? 
    It creates an uncompressed 2D array of 1s and 0s which represents the 16-bit binary A/D conversion of each element in the Y array of the input waveform. You can use the DWDT Digital to Boolean Array.vi to convert to a 2D array of booleans. Then convert the booleans to 1,0 and sum the array of integers. The sum should be the count of 1s in the digital waveform.
    Lynn
    Note: The attached VI is saved back to version 8.6. When I saved it for Previous Version a warning was generated about possible differences in versions. Let me know if it does not work, and what version of LV you are using.
    Attachments:
    Count bits.vi ‏25 KB

  • Generate digital signal for 6722 or 6221

     Hi,
    first thanks for the help I already got on this board.
    Now I've got the following problem:
    I like to generate a digital signal: high for 300µs, low 300 µs, high 300µs, low 300µs, high for about 2ms.
    I am looking for a solution how to generate this digital sequence. At the same time I will read the information back via an analog input (hopefully I have now a solution for this problem).
    I tried to find examples but I wasn't successful. At the moment I was not able to produce any digital sequence which worked.
    My hardware is either 6722 or 6221 - which should be OK regarding the timing.
    Thanks
    Solved!
    Go to Solution.

    Find attached example.
    I am not allergic to Kudos, in fact I love Kudos.
     Make your LabVIEW experience more CONVENIENT.
    Attachments:
    Digital Waveform [LV 2009].vi ‏14 KB

  • Is it save to use digital output as a digital input signal for another channel

    Hi all,
    I know this is a stupid question, but I do not have other signal generator by hand. So what I want to know is, can I use the digital output signal of my USB-6001 as an input signal for the same device but on other digital port? I did not try out directly because I do not want to burn the device down......
    Thanks
    Solved!
    Go to Solution.

    I do loop backs all the time, especially in my test systems as a way of making sure my signal is making it to the UUT pin.  I typically throw in a 10k resistor just in case, but I have never had an issue.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • How to control individual channel of signal generated from digital waveform generator?

    Digital waveform generator has 8 channels. I need to generate two different signals to HSDIO. How to modify and control two different channels? Also, how to translate pin outs from PXI-6541 to channels? I need to control signal into pin 1,3,29,and 31 individually.
    Thank you!!
    Solved!
    Go to Solution.

    You must combine your individual data into an array.  The digital waveform is simply a digital representation of the binary array.  It still boils down to bit 0 of each array element going to channel 0 (or the first channel you specify in Create Dynamic Channels).  The next bit goes to the next channel.  My last post is quite clear.  To display the array in binary, right click on an array element, then select Display Format, then select Binary.  You can also right click on the element, select Visible, then select Show Radix to display the small b before the number.  One more thing, in the Display Format window, uncheck the box next to Use minimum field width.  Then set the numeric just under the box to 8.  Then select Pad with zeros on left in the box below.
    You should not use waveforms until you learn more about how the HSDIO operates on input data.  It isn't hard to combine waveforms, but it also isn't as clear as using an array of U8 or U16 or U32.
    Trying to explain further.  The first number to be writen to the HSDIO will have this effect:  Bit 0 (LSB) of the number gets written to the first HSDIO channel you specify.  Bit 7 goes to the 8th channel you specify.  If you don't specify 8 channels, the bits get ignored.  So wiring in one number will produce only one bit on each channel.  In other words, the number already combines the bits of all the channels you specify.  You don't combine anything yourself.  Look again at my picture on my last post.  By wiring in an array, you cause a bit pattern to be generated.
    I hope this is more clear.
    - tbob
    Inventor of the WORM Global

  • Using a digital signal for home sensing on NI9512

    I have the following setup.
    cRIO -> NI9512 -> P7053
    I'm using an optical sensor and a flag for doing home sensing.  The sensor outputs high (~4.5V) when the sensor is inactive and Low (0V) when the sensor is active.
    In the axis configuration I have the option for syncing and sourcing only for my home sensor and do not have access to TTL/CMOS for digital logic.
    Is there something I am missing, or does my hardware setup require me to use limit switches for home detection?
    thanks in advance.

    Hi,
    On the MDR connector of the 9512 you have access to the forward, reverse, and home limits on pins 1, 11, and 2, repetitively.  You can see this on page 10 of the manual here: http://www.ni.com/pdf/manuals/374555d.pdf
    What do you mean when you say "TTL/CMOS for digital logic"?  Page 5 of the manual indicates that the limits work off of +5 VDC.  So your sensor should work, the device is not going to be able to tell what the voltage is coming from, whether is be a optical sensor or limit switch.
    Regards,
    Greg H.
    Applications Engineer
    National Instruments

  • Analog Signal to Digital a Primer

    Many users have analog material sitting around, and they would like to get it into digital form, so that it can be edited. As this material is below SD (Standard Definition) quality, I will address the methods for digitizing it, so that it can be best edited in a DV Project. The output can be a DVD-Video, or other format, depending on what one wishes.
    The process of getting this analog material into a digital form, is referred to as Capturing, and it is digitizing the analog material and writing it to a file, that can be edited.
    One will need some method of getting the analog signals into digital form, and for connecting the analog output from their analog playback device to the computer. Though the analog signal could come from all sorts of devices, I’ll use a VHS tape deck in this example.
    Since a VHS tape deck does not have an A-D (Analog to Digital) processor, and also does not have a a digital signal Out, one needs something in between it, and the computer. That “something” serves two needs: mechanical connection of cables and the ability to convert the analog to digital for use in an NLE (Non Linear Editor). That “something” can be a digital video camera with pass-through capabilities, a device, called a “bridge,” or a capture card inserted into a bus slot in the computer. All three have pluses and minuses.
    The first two methods rely on one having a FireWire connection on the computer and will use the Capture module in the NLE software.
    The digital video camera route is good, as one already owns it. Having one with pass-through capabilities is getting more difficult. The camera also has to have FireWire (FW, IEEE-1394a, or iLink) output, and the computer must have a matching connection.
    An A-D bridge will do the same thing: allow one to connect the analog cables to one end/side, process the analog signals to digital and then output via FW to the computer. There are various such bridges available and two of the most often recommended makes/models are: the ADS-Pryo, and theCanopus/Grass Valley ADVC-110. Products, like the Dazzle lineup, just do not seem to work, or work well. I would avoid such.
    A dedicated capture card performs the same task, with one exception. The card will mount into an empty PCI slot on the MoBo, and have inputs for the analog cables. The card will have chips on it, to digitize the analog signals and feed these to the computer via the PCI slot. These do not connect via FW, but have one drawback: they must, in virtually every instance, use additional software to do the actual Capture, as most NLE’s cannot directly see and work with them. Some of the included software Capture programs are better, than others. One common issue with many of these cards is a loss of sync, between the Audio and the Video. This is usually static OOS (Out Of Sync), in that it is usually off by a fixed number of frames, and does not drift over time. This can be fixed in the NLE, but is extra work. This ARTICLE will give you tips on correcting OOS.
    Now, we are ready to begin the Capture, as our equipment and cables are all ready to go. We have a big decision in front of us - what format/CODEC do we use to Capture our digital files? Since we are doing an SD Project with non-HD (High Def) material, there is one fine choice: DV-AVI Type II w/ 48KHz 16-bit PCM/WAV Audio, using the DV/DVC CODEC. These files will be approximately 13GB / hour of Duration. Storage will need to be considered. These files are also I-frame, meaning that each “Frame” is rendered and available, so that frame-accurate editing is possible. The NLE will not need to do any processing, or conversion of these files, as even the Audio is ready for DVD-Video. Note: there will still be Conforming and the generation of PEK (Waveform Display) files, but the NLE will be able to do this quickly and efficiently.
    Using AVI Uncompressed will get you nothing that you can see, other than larger files. Do NOT use any compressed format/CODEC, like MPEG-2, WMV, MOV, etc., as these will loose data from an already inferior source, and will then need conversion to be used, either with a stand-alone conversion program, or internally by the NLE. You loose quality and then have more work to be done. Do not let the temptation of smaller files lure you into using anything but DV-AVI Type II, and just accommodate the larger file sizes.
    With the file format/CODEC decision made, the cables and devices hooked up, we’re ready to start the Capture. The exact operation will depend on what our equipment choice has been. See above for talk about additional Capture software, if one uses a capture card. Otherwise, we should be able to use the Capture module of our NLE. The first issue is that we will NOT have Device Control, as we would with a Capture from a miniDV tape-based digital camera, where we can control the mechanical aspects of the camera, during this process. As our VHS deck is hooked up to the A-D bridge, or digital camera w/ pass-through, via analog cables, our control signals cannot be sent to it. One would cue up the tape in the VHS deck, and then choose Record/Capture in the NLE’s Capture module, starting the Capture. Instantly, they would hit Play on the VHS deck, or via that deck’s remote control. This is easier the second time that one does it. I sit with the mouse in my right hand, poised over the Record/Capture button, and the VHS deck’s remote in my left hand, finger hovering over Play. It’s then a 1 - 2 push, and all starts. One can stop the Capture, if an unwanted section of tape comes up. The Capture module of the NLE will direct us on how to proceed from there, should more Captures be wanted. Some will just start up at a later point, and write an additional file for that portion of the tape, but some might require that one basically sets up a new Capture session One should investigate just what their NLE will require for doing multiple Capture sessions from one VHS tape.
    When done, one closes the Capture module, and then navigates to the location that these DV-AVI Type II files have been stored in, and Imports them into the Project. This differs slightly from doing the Capture from a miniDV tape camera, as those Captured files are already in the Project.
    Edit away, and Export/Share to the necessary output settings, file type and CODEC.
    What about those VHS - DVD decks, the ones that will burn a DVD directly from the VHS tape? They seem so simple to use, and for the most part are. However, those DVD-Video discs, contain pretty heavily-compressed MPEG-2 AV streams. These MPEG-2's, besides being compressed, are in aGOP structure and are muxed (Multiplexed into one file with both a Video & Audio stream), plus there is often some Menus and navigation in the first VOB, the main container components of a DVD-Video. Many NLE’s can Import the VOB’s, and basically rip the MPEG-2 out of them, but that first VOB can be highly problematic, due to the way that most of those decks do the Menus and navigation. It is seldom 100% DVD-compliant by the DVD-specs. This can be a major problem. This ARTICLE will give you some background and tips on DVD VOB's.
    Those dual-decks are good for doing one thing, regarding the DVD’s that they produce - provide one with an archival DVD-Video of the VHS tape, and not to be edited. However, the VHS side of these works well with an A-D bridge, just like a pure VHS deck does. I would strongly recommend that one does NOT use the DVD-Video portion of these, if editing will be desired. They cause many more problems, than they solve - just use them for an “archive” copy of the tape to a DVD-Video, for playback on a computer via DVD software or a set-top player, hooked to a TV.
    What about film? Well, film is obviously analog, and one needs to digitize this to edit on the computer. The process of this digitizing is referred to as telecineing the film. While one can buy equipment to do this, it is expensive, and involves a lot of setup and testing to get the job done. There are many service bureaus, that offer telecining. Some are better than others. The main considerations are: care in handling of fragile film, how the telecining is done, i.e. frame by frame w/ a liquid gate, or just by straight projection, and then output format for the digitized files. Some of these services will offer a DVD-Video disc. Do not be tempted to do this. See above. Others will offer to write these digitized files to a miniDV tape, and this is just fine. One does then need a miniDV camera, or miniDV tape deck, to then do the Capture from, but the quality and editability will be preserved. The final delivery format would be to put these DV-AVI Type II files onto an external HDD. This saves one from having to do the Capture from miniDV tape, having to have a miniDV camera, or miniDV deck, and only Importing of those files would be required to get them into the Project. Many of these service bureaus will either sell you the external, or use one provided to them. Check out specifications for things like format of the external. FAT-32 will limit the file sizes to ~ 4GB max, and NTSF will have no such limitations. However, if the service bureau is on Mac, and you’re on the PC, their Mac’s can ONLY see FAT-32 HDD’s. Talk this over with the service bureau first, so that there are no surprises later on.
    Hope that this helps,
    Hunt
    PS - also see this FAQ Entry for more detail.

    the_wine_snob wrote:
     Products, like the Dazzle lineup, just do not seem to work, or work well. I would avoid such.
    Although I now have a Canopus ADVC300 I previously used a Magix 'Movies on DVD' USB device. I found the results from this to be particularly good and, to my ageing eyes, I see very little quality difference.
    I think this is because Magix use their proprietary high quality codec (from their Pro products) to capture the footage. Like DV-AVI it runs around 10GB+ per hour. This can then, very simply, be exported to DV-AVI Type 2 for use in PRE. Note that there are some sound synchronisation issues with the 'out of the box' settings - but the fix is quick and I posted details to the Magix forum.
    Would I revert if I could return my ADVC300 bridge? Probably not - the firewire connection and the PC seeing the box as a camcorder adds to ease of use. In fact I am pleased to have both. There are some things Magix does better than PRE7 (batch exporting each scene as an individual DV-AVI file being just one) and it has smart-rendering which is handy for quick clip splitting/exporting.
    Cheers,
    Neale
    Insanity is hereditary, you get it from your children

  • How can I record multiple signals for a long period of time?

    Hi, everyone
    I am new at labView I just recentlyl started using it. Right now I am working on this assignment
    that I have to display en record six different signals comming up from a DAQ. so basically What I did
    for my IV is placing a whileloop. Inside the while loop I set up the DAQ assistant and then I send that
    to a split signal function in order to split the signas that are comming from the DAQ ( so those signals
    are EMG1,EMG2, blood flow1, blood flow2, blood pressure, and AM stimulation) after I split the signals
    I send each individual signals to a waveforme graph, but my problem is that I need to record those individual
    signals for a long period of time every second for about 8 hours. so it will be really helpfull if someone can
    guide me through this. Thanks
    Regards

    Hi,
    With your while loop, you'd better use low-level VIs to write your data to a file. Please see attached...I've used text file function but if you need ta save a large amount of data, you may need to use binary file functions instead (nearly the same way to perform this whatever you chose text file or binary file function).
    Best,
    J.
    Attachments:
    RecordData.vi ‏27 KB

  • Simultaneous analog and digital waveform read with PXIe-6361 and BNC2120 ?

    Hi there,
    I am trying to collect both analog and digital signals from a PXIe-6361 linked to a BNC2120, using the attached VI. I am running Labview 2011 64bit. This is the first time I am working with digital input. On the 2120 board, I have the digital input BNC cable connected to User Input 1 and wire between the screw terminal of UserInput 1 and the P0.1 (Digtial I/O) screw terminal.
    I have two questions related to this:
    1) When I try to run the VI in its current state, I get the following error:
    Error -89137 occurred at DAQmx Start Task.vi:3
    Possible reason(s): Specified route cannot be satisfied, because it requires resources that are currently in use by another route.
    Property: RefClk.Src
    Source Device: PXI1Slot2
    Source Terminal: PXIe_Clk100
    Required Resources in Use by
    Task Name: _unnamedTask<6>
    Source Device: PXI1Slot2
    Source Terminal: None
    Destination Device: PXI1Slot2
    Destination Terminal: RefClockInternal
    Can anyone point me in the right direction for troubleshooting this?
    2) I would like to combine my regular waveforms and the digital waveform into one array which would then be written to file. I can't figure out how to combine the two different waveform types...can anyone give me a hint on this?
    Thanks for your help,
    Claire.
    Attachments:
    Export Waveforms To Spreadsheet File (1D)_wo extra line.vi ‏33 KB
    Multi-Device Synch-Analog Input-Finite Acq-Analog Start_Claire_wDigitalin.vi ‏105 KB

    Hi ClaireJ,
    Sounds like a reference clock conflict. This KnowledgeBase (KB) talks about this error when using simultaneous sampling. Also, might want to check the device routes in Measurement and Automation Explorer (MAX) as discussed here. Finally, if you are routing your PFI line over a RTSI connection, this error can occur. This KB discusses it.
    As to your second question, this post should help.
    Bill E. | Applications Engineer | National Instruments

  • Bug in Digital Waveform Graph X-Axis

    Hello,
    I am making separate queried to a database to retrieve analog and digital data over the same time period.  The data were logged at 2 second intervals.  I have verified that both result sets return the same number of values with the same t0 and dt.  I then plot the analog values on an XY Graph and the digital values on a Digital Waveform Graph.  I then use property nodes to sync the two graphs (left and right plot bounds, XScale.Range, and Cursor Position.X).  After doing this, I can see that the datasets do not line up between the two graphs.  The data on the Digital Waveform graph ends several seconds sooner than the analog data.  The x scales of the graphs appear to match but the plots don't align in time.
    Has anyone else observed this behavior?  Is there any work-around?
    Thank you,
    Peter

    There is a much simpler way to synchronize these charts. Just use a stacked chart.
    If you use a bundle function you can take two signals (almost data type) and wire them into a Waveform Chart together.
    Then on the front panel right click on the chart and select Stack Plots
    Since you only have 1 X axis now they are instrincly synched and will always write valules at the same time and update the UI together. You can skip all of the scale synching....
    Since the data you are working with has lincked time stamps, the data will need to be matched, (make sure the samples are anyched and each itteration both would have the same number of samples.
    The last allternative would be to strip the time stamp off of your data then build a new data structure, with the digital data, analog data and 1 set of matched time stamps. You can then plot this on an XY chart using the time stamp for the X axis for both of your other plots.  Let me know if you have other questions.

  • Digital Waveform graph with a lot of samples

    Hi,
    I have to display in a Digital Waveform Graph a lot of data read from a file(2.000.000 of samples for 36 signals). If I read the file and I try to display all the data, the Vi became unusable. For example, to zoom a graph region, it may take 30-40 seconds, scroll is impossible ecc, ecc..
    Apparently LV doesn't perform a decimation of points. In measurements studio 8, this problem doesn't exist...but I have to use LV 7.1..
    any suggestion ?
    At the moment I have developed a DLL in VC++ that perform a decimation of samples, but performance are not very good !
    Thank you for any idea.
    Regards.

    Hi Garraty,
    Excuse me but I have several questions for you.
    1)     Have you tried some kind of incremental approach, starting from 1 waveform and increasing towards 36? Do you experience some kind of on/off degeneration between, les’s say, 34 and 35 waveforms?
    2)     How can you decimate a digital pseudorandom sequence of 2M samples without loosing information?
    3)     Is this 2M samples an unavoidable constraint for your application?. Actually, it seems very difficult to extract some kind of visual information from a pseudorandom pattern of this length?
    Thank you very much.
    Kind Regards
    FiloP
    FiloP
    It doesn't matter how beautiful your theory is, it doesn't matter how smart you are. If it doesn't agree with experiment, it's wrong.
    Richard P. Feynman

  • Memory leak in Digital Waveform

    I have a program with a pretty serious memory leak that uses up all my system RAM and crashes my computer within a few hours of running the program.
    The program takes an array of U16s where each bit represents a digital signal. The VI converts each U16 to a digital array and groups the resulting 16 digital signals into different busses for display on a Digital Waveform Graph. The profiler doesn't show any excessive memory usage in the VI. I put the whole VI into a Diagram Disable structure and moved a few pieces out at a time, and eventually the only thing inside the disable structure was the Digital Waveform Graph indicator. When this indicator is enabled, the memory usage of my system rises slowly and steadily until it uses all available RAM and crashes the system.
    If I replace the Digital Waveform Graph indicator with a cluster, the memory leak still occurs (but much more slowly). I thought using the cluster fixed the leak until I reran the VI overnight while using the cluster instead of the Graph.
    If I stop the VI before all the RAM is used, the RAM will not release until I close LabVIEW entirely. Once LabVIEW closes, the memory is released slowly and exponentially unless I use the "End Process" option in Task Manager.
    This is a continuation of a previous post I made where I thought the memory leak was due to problems transferring data from an FPGA for display.
    I ran the MemLeak vi (attached) on two separate systems, both running LV 2013 SP1, and got the same results. The memory leak is noticeably fast when using the enable structure connected to the Digital Waveform Graph but still present when using the cluster of Digital Waveforms.
    Attachments:
    MemLeak.vi ‏33 KB
    LV shutdown.PNG ‏101 KB

    Thanks for the replies.
    In response to John's points:
    1. The attached VI is a simplification of an FPGA VI that read a fixed number of samples from a DMA FIFO using an FPGA Interface Invoke Method approach. I'm using a card (PXI-7842R) that doesn't allow use of the Acquire Read Region method. In order to allow people without an FPGA card to hopefully see the issue, I replaced it with the for loop. Assuming that this for loop does leak (which I don't believe it does; as altenbach said, it's a fixed size allocation that LV should be able to reuse), why would I see a difference in the leak magnitude depending on which indicator I connect to the array?
    2. I've previously reviewed the document you referenced, and I don't see any errors from it present in my code; do you? I have no global/local variables, strings/arrays displayed on front panel, property nodes, coercion dots, altered memory sizes, resizing/reallocations, etc. I don't see any weird buffer allocations. I used to have the conversion from U16 array to digital waveforms in a subVI but placed it on the same diagram to allow incremental use of the Diagram Disable structure.
    3. The forum post you referenced had many of the items discussed above, plus it was solved using an RT FIFO. I'm not passing data from a producer to a consumer; I'm just displaying acquisition results. I guess you could say I'm processing the data, but I'm really only converting it to a format that the indicator will take; I'm not operating on the data.
    It's good that the leak doesn't show up in 2014, but my SSP runs out in a couple of days; I never got an upgrade to 2014. This is the last item remaining on the development path, and we've already spent ~$4k to upgrade the controllers enough to display the acquisition without dragging down the CPU. I will be in hot water if I spent all that money and then end up having to scrap the display...

Maybe you are looking for