Karissap

Here's a VI that I created for a project, it uses the NI IMAQ USB library, I've used a Logitech QuickCam IM with this and it works. I think the problem in your original implementation was the "USB Camera Name" input might not have been right, this VI selects the name from a list.

http://forums.lavag.org/index.php?act=attach&type=post&id=6012

The OpenG library has some useful file tools. Here is a vi "Delete Old Files Recursive.vi"

http://forums.lavag.org/index.php?act=attach&type=post&id=5984

I created this vi by modifying the "Delete Files Recursive.vi" from the OpenG library to only delete files modified after a certain date.

If you don't need to continuously record you could try using the acquire sound express vi, this would the easiest way to do it. This will acquire sound from a sound card for a certain period of time and output a waveform. If you do need to continuously record the input look at the "Continuous Sound Input.vi" in the NI Example Finder.

I'm not sure about the format of data in your table so can't give you an exact solution but basically you need to convert the table of strings to numbers using the sting/number convesion or scan from string. If the graph contains x axis data and y axis data you can use the xy graph indicator. This indicator can be used different ways but basically you need a cluster of arrays or arrays of clusters of xy data. For example if the first column was X data and the second column was y data the output of the block diagram could look like this:

http://forums.lavag.org/index.php?act=attach&type=post&id=5958

If there were more datasets in the table you could use an array of clusters etc.

If you're interested in making a graph in the excel file instead of the front panel you could use a macro (Check out the Excel Macro Example.vi in the NI Example Finder).

I have a program which needs to run continuously unattended. However, it crashes after random periods of time. I get the error in external code at 0x00 in the vi which uses a particular Labwindows function. It will run the function in the dll fine for half a day or so then crash, which makes me think that it is a memory problem (the function does use malloc and free). Is there a way to catch exceptions in dlls to prevent the Labview program from stopping? I am running a batch file that will restart the vi if it closes but if this dll error occurs the program stops but stays open so won't restart so even a way to close labview entirely if the error occured would be OK. Also, what do people think is the best way of detecting memory leaks in applications?