Jordan Kuehn

You wouldn't happen to be writing 2D data and performing a transpose before the write?  And on version I think 2011 or older?

 

http://forums.ni.com/t5/LabVIEW/WARNING-TDMS-memory-leak-in-LV-2010/td-p/1874575

 

That was a nasty one that got me all the time.  If you can isolate it like that user we can get NI working on it, or testing it on different versions of LabVIEW.  What version are you using for this by the way?

I've nearly abandoned TDMS for these reasons except for in special cases.

This is amazing!

I have no idea how LabVIEW will tolerate concurrent access to the settings. I don't anticipate well.

LabVIEW and Dropbox frequently fight when building executables on my machine.  If I forget to turn off the syncing, often I get file permission errors while dropbox is trying to copy the file and labview is trying to delete the temporary file.

http://www.ni.com/example/27568/en/

First link is a bit dated.  Check out these options, but you are looking for standard reports generated by the Report Generation Toolkit.

http://www.ni.com/white-paper/13926/en/

Here is a simple snippet that I have used for a similar task before.  There are many many ways to process the data, but with signals like what you have I've found that selecting a nominal location for where the 'reflection' should be as well as a window size to search in, you can pretty directly find what you are looking for.  The peak may not be what you want, but this is a starting point.  You have good SNR so that helps a lot.

I would guess that rather than trying to write a file to the card, he is attempting to apply an image to the card. 

Do zombies even live for 11 years?

Do they ever live?

Where is the zombie smiley?

Saw this article and thought of this discussion.  Don't have time to investigate the actual hardware or vendor, but it's an interesting take on bluetooth tracking.

I don't know of a good list that says X vi needs a license and Y vi doesn't.

See the linked document above.  I believe it is comprehensive.

I think the free part of the vision toolkit is called VAS, Vision Acquisition Software.  There was a thread on LAVA at one point talking about it but I can't seem to find it.

You might be referring to this thread.  Regardless, I linked at the end to the free vision functions which I think is what the OP is looking for to get started.

Coming from a different point of view, I have spent a lot of time helping out with FRC.  Yes, the code base helps greatly and takes care a lot of issues to minimize what high school kids need to know about labview.  The code base tends to break dataflow with heavy reliance on Globals.  In addition, I've seen many many times people try to implement code with local variables and have it perform poorly.  A simple latch for a button press is an example.  The point is that new programmers have a pretty big learning curve jumping into g-code, despite our best efforts they will try to apply their text-based variable-centric strategies, and that shouldn't stop them from getting something to work (i.e. a mysteriously broken VI).  A warning would be fantastic.  It also needs to be accurate.

From the point of view of an experience programmer I think the tool would need to be very intelligent for it to be helpful.  Without knowing the details about how you envision this working, I imagine it would be quite good at catching your alpha/beta loop counter races, but so am I.  Experienced programmers are quite good at creating very clever race conditions.  Code reviews are good for helping with these.  Again, I don't think breaking the VI is the right way to go.  A good warning that can be dismissed would be nice and that's with it working well.  If it erroneously found race conditions I'd be likely to just turn it off.  Much like the auto-insert feedback node 'feature'.

Are you running an eval version of the FPGA module?

Like who's Simon, and why does he have his own gauge? 

https://decibel.ni.com/content/people/SimonH?view=profile

https://decibel.ni.com/content/groups/ui

I believe he was also heavily involved with VI Snippets.

Agreed with everything Rolf said.  Go look at an old IDE HDD for an easy example of a male connector being used and the motherboard connection.  A ribbon cable is the easiest way to connect to it, but for just a few channels look at these jumper cables.  They fit nicely on each pin.  

But I do have a couple more questions: the evaluation kit is basically an sbRIO-9636 with an additional board on top, right? If that's the case, then what's connected to analog inputs 8-15, and analog outputs 2-3? Both LabVIEW and NI's page about the sbRIO-9636 say they exist, but I can't find any terminals for them, or anything that says what they're connected to. Was there not enough room for the terminals? Is the only way to access them by removing the top board, which would also free the DIO 4-27 and AI 6-7? The same questions apply to the three COM ports listed in MAX as well. I don't think I would really have a need to, at least not any time soon, but in case it comes up, the top board can be removed without damaging either board, and I could later put it back, right?

I don't have that exact same eval kit, but yes, you can remove the daughter board without a problem.  If you have the 50 pin connectors you can easily use ribbon cables to connect to each pin.  Otherwise jumper wires are useful for individual connections.  They likely only exposed some of the channels in the daughter board to keep the size down.  The manual will list which channels are routed to which pins in the connectors.  

I'll bring this back to life one more time.  I'm trying to use the webpanel demo, but I'm getting errors in the browser that suggest that jQuery is not being included correctly in the SVG file.  I've attempted to modify the SVG file to include the libraries, but this generates other errors.  Google suggests that jQuery assumes that it exists in HTML rather than SVG which may be causing the problems.  Is this an issue that others are encountering?  Could this simply be that I have up to date browsers and javascript installed and support broke along the way or am I doing something stupid?  I can navigate to 127.0.0.1:81 in Chrome and it begins downloading data and the VI shows a connection, so I think things are ok on that end.

ReferenceError: $ is not defined webpanel.js:34

Edit//

By downloading jQuery 1.9.1 and changing line 1321 from

if ( !all || !a || !all.length ) {

to

if (!all || !a || !all.length || !a.style) {

as described here I was able to get WP_jQuery.svg to work.  This page suggests it is a jQuery bug that may not have affected older browsers.  Perhaps a new release with the modified jQuery source is in order.

The myDAQ is  A/D IO only and what they used to call Elvis.

 myDAQ != Elvis.

crossrulz is brave

Try this link: http://ftp.ni.com/evaluation/labview/ekit/other/downloader/2013GPUAnalysis-32bit_downloader.exe

You can find some software at ni.com/downloads which is where I was able to get this link.

*woosh* I completely missed that.

At risk of sounding stupid, which book are you referring to?

Could you post some code of your write operation?  Are you doing any buffering of the data between acquisition and writing to disk (well USB)?

Thanks!

Brought the camera, but found out the power cable was not in the bag. Mark will be on his own unless I can find a sony video camera power cable. Would have liked to share a couple sessions from yesterday.