todd

How about this. From left to right: "Gaussian White Noise.vi", "Auto Power Spectrum.vi" and "Harmonic Analyzer.vi"

I haven't seen any trouble yet.

Yes to both: using the nVidia desktop manager, or whatever it's called.

I thought you were looking for gaussian noise. If that had been true, the number of samples for "Gaussian White Noise.vi" could be set to the number of samples in your data set before adding. My mistake.

I wonder if you have access to "Gaussian White Noise.vi".

Excluding ActiveX, MATLAB 6.1.0.450 help says the only way to call external code is with a MEX file (dll, for windows). Unfortunately, App Builder is needed to make a dll from LabVIEW. If you find an acceptable method of using the LabVIEW runtime engine, .m files can be called in batch mode using "System Exec.vi".

Right-click on the array constant to change its "Representation". Right-click on the while loop border to "Add Shift Register". Add a Waveform Graph on the front panel.

I dislike IVI, too: half of my instruments have functionality not exposed with IVI. I had some trouble with a similar Keithley instrument. The read command (:Trace:Data?) gave an error unless all of the setup commands were exactly right. Step through the examples again.

Are you using the USB-TMC spec?

No. It would execute again If the property was 'Value (Signaling)' instead of 'Value'. I haven't yet installed 7.1.

Here's how I reset the button and catch errors.

Have you enabled serial port support in the application builder?

How does the load box connect to the computer?

Perhaps you could use "Position" and "Legend -> Position" waveform graph properties. I use these to calculate a new position for the legend when programmatically adding plots to a graph.

Close all vi's that call the old subvi. Rename the new subvi so it has the same name as the new subvi. Open all vi's that call the old subvi. Open the new subvi (that currently has the old name) and save it with the new name. All calling vi's will update their paths to the subvi.

Perhaps you can use MATLAB batch mode. http://messages.info-labview.org/2004/07/16/22.html

It sounds like you're distributing a built exe. Make sure to enable the ActiveX server in the build options.

Make sure MATLAB works without LabVIEW (to check licensing issues). Which version of MATLAB are you using?

I'm sure you know that you can right-click on a cluster and 'Reorder Controls in Cluster...'. Your efficiency now has the higher cost of making sure each new cluster element has the largest cluster index. This may beg for a LV2 global with a strict type def enum that chooses which global element gets accessed.

Here's something for the Keithley 2400. Download File:post-107-1095458871.llb

'Rotate 1D Array'?

You shouldn't be getting -2 for row or value. Here are a couple of pictures that may help.

Perhaps this answer is too simplistic: Using the MATLAB Script node, if you only need one value at a time, index the array of data and send one value at a time. (This can't be right.) Using MATLAB batch mode, you can call a .m file that opens the data file and writes an output file. Use "System Exec.vi" to call MATLAB with the /r flag for Windows (-r for *nix) and the name of the .m file.

It turns out that I've always hit ctrl-R (Run Without Pausing) to get past a cleared breakpoint. This leaves the vi in debug mode even on subsequent calls (execution will be paused). The 'Continue' button works. I was a LV genious until I talked to other users.

I can't find info on this in any of the standard locations: Place a breakpoint in a subVI. Run the code, allowing the breakpoint to be hit. Clear the breakpoint (before or after completing an execution). From idle, run the top level vi again. Execution pauses at the first object in the subvi that had the breakpoint. I then have to step out of every vi in the heirarchy before all will run without pausing. Is there a way around this behaviour?