Jump to content

todd

Members
  • Posts

    335
  • Joined

  • Last visited

  • Days Won

    13

Posts posted by todd

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

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

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

  4. I don't have LV7.1 installed right now so someone else will be more specific to your vi. However, if you want to view binary data in Excel, use an array of hex strings ("format into string.vi" format string = %x). Convert the array of strings to one string delimited with comma (for one Excel row) or CRLF (for one Excel column) and write the string of characters to a file. Excel functions HEX2DEC() and HEX2BIN() may be useful, too.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.