Tim_S

Any idea what I might be doing wrong?

You made the classic mistake of not trying it out before selling it. I'd say I'd invented that one, but I'm not that old.

Thanks for locating that. I must have typed in wrong search parameters. :/

Hrm... I see how the solution is done, but I'm starting to think using a listbox and may be more desirable.

Hopefully someone has a solution to this in their back pocket. I'm working on a user interface where the operator will be editing an array of numbers. The behavior I am trying to create is, when the user adds a number to the array, the keyfocus goes to the element in the array. I've been trying to do this with an array of numbers without any success. I would rather avoid using a text-entry control (e.g., table), but that may be the option I have.

Any thoughts?

The DMM is reading what I would expect. A DMM will report a time-averaged signal, hence your pulsing DC will go through a strait average (DC measurement) or RMS average (AC measurement). This is a matter of using the proper tool for the job.

I'd double-check the DMM was reading correctly using something like a battery. What type of signal are you trying to measure?

This is likely not due to input impedance. Have you verified the oscilloscope is configured for a x100 probe? Is the probe switch-selectable for different ranges? Does the DMM or oscilloscope read what you expect?

Typically we just use the context help. If you enter a description for a control/indicator, that will show up in the context help window. You can programmatically show/hide that. So you just have a help button that pops it up. Then when they hover over a control/indicator the description shows up in the context help window.

Is the context help box available in an executable?

You could change the resolution to something lower (usually not as good looking as native resolution), use a separate monitor, or get IT to buy you something like a LCD monitor magnifier (yes, this is a real product).

I built up a treeview class some time ago that uses attributes in a variant to keep track of the UIDs, their parent, etc. This gave me better performance and much simpler code than parsing through the tree. I've reused that code a fair amount, though it's always been for small data sets.

Excellent. You just need a moat and this: http://www.thinkgeek.com/product/81e6/

Have you tried calling NI? I don't expect the cables are fire retardant, however I believe you'll need to describe your application to answer if they meet you need.

I assume the numbers are coming across as ASCII "234"... This would make typecast the wrong primitive to use. You would want Decimal String to Number under the String -> String/Number Conversion pallet.

I would also recommend using Match Pattern->Decimal String to Number->cluster instead.

I second asbo's statement with the comment that the unfiltered data may be required; you're sampling at 10kHz, but filtering out everything above 20Hz quite harshly.

The problem is that the frontpanel of my application is hidden and when I dobble click the Icon in the tray, the Password VI popup but it is not the active window!

You will need to make some calls to reorder the windows. User32.dll has "SetFocus", "ShowWindowAsync" and "SetWindowPos" functions in it. I've not found a foolproof way to get a window on top and with focus, but those are what I'm using.

Are you collecting the data by setting the number of samples in the DAQ Read or are you waiting for 1 second then collecting the data points present?

Your absolutely right, but after that first time you can look at the Doc Open event

The number hours I could have saved using that...

You don't really need to have an add_file program. When you double-click on the file you can pass the file path directly to the viewer as a command-line argument which can be read by LabViEW.

That would work with the first instance of data_viewer.exe, but not if it was already open (since there is a single instance requirement). The data_viewer.exe could allow multiple instances, pass off the command line through another method to an existing instance, then self-terminate. This could be low-overhead if it was done similar to a splash screen.

I don't have a computer that has LabVIEW to open the 1D <-> 2D, so you may have to forgive the question: How are these different than Reshape Array?

I've implemented a similar structure with a waveform viewing application. There were multiple user-selectable user interfaces that all used a single action loop to do the work. I passed a DVR to the UI on initialization containing the data and then sent an event back to the UI that the data had been updated inside the DVR. I did a test where 10,000 waveforms of 4096 points were loaded and displayed, and did not see a performance issue (the graph does slow down at that point).

... that make our clients happy.

Happy clients? I have some unobtainium for sale...

Well. I deal with automation machines and if it doesn't work there are penalty clauses. The clients are only interested in what day it will go into production and plan infrastructure, production schedules and throughput based on them being 100% operational on day 1. Deficient software is something desktop users have gotten used to and have been trained to expect. Software is the only discipline where it is expected to be crap when new. Imagine if an architect said "here's your new skyscraper, There's bound to be structural defects, but live in it for a year with a hard-hat and we'll fix anything you find".

My clients would like 100% operational on day 1, but 50 custom assembly, gauging and test stations with PC and PLC software all trying to dance together with operator interaction just doesn't give you that option (especially with decreasing time to market). The operator will do something that causes the programmer to stare, blink and go, "why would you ever do that?" All of the stations do go through debug and testing on our floor and the customer's floor, so we shake out most of the bugs, but it's impossible to get them all.

The program will have the same privileges as the operator unless you have the program run under a different login. That would be a reasonable way to go about it.

Another way would be to provide a viewing window/application that only allows viewing then not tell the operator where the file is located.

You are welcome to do as you please, but why even post an image of this tool, if you are unable, or unwilling to share it?

"Barely imperceptible sadistic tendencies."

If you have that many instances of this behavior it would be worth your time to create an Xcontrol.

Have you looked at using the "Key Down?" event?

The closest you're going to get to an all-inclusive, exhaustive list is from the error code files on your computer: http://digital.ni.com/public.nsf/allkb/6077DBEDA4F9FEE3862571F600449501

and the manual: http://zone.ni.com/reference/en-XX/help/371361B-01/lverror/error_code_ranges/

For practical purposes, I'd follow rolfk's advice.