Jordan Kuehn

You may have some luck with getting your local sales guy to put you in touch with R&D to give you an "unofficial" max limit on the hardware that will at least give you an idea of how terrible that current will be for that short duration and possibly an idea of what components could fail. Worst case they'll tell you that you absolutely cannot exceed the specs listed. I agree with Hooovahh that these specs seem a bit different than the typical spec sheet.

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

This is amazing!

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 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.

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

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?

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.

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.

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!