LabVIEW
Serial Communication fails after a minute or so of running
Solved!
@Nadweb wrote:If I'm not in \ view, should I just see KRDG A? I will also have to check what view I'm in and verify what the string is.
If you're not in \ view, it's a bit tricky if you're inputting the termination character in the string because it's whitespace, so you can't see it well. You'll see the string and then an empty line, but the empty line is invisible!
If you follow the VB example in the manual, you see that they append the termination characters (they use both, it's not clear to me if this is required or optional) to the supplied user string.
You could do this in LabVIEW using Concatenate Strings, and then not input any line end characters in the control (I'd generally suggest that if you're writing a library to simplify the user of the instrument in other 'application' code).
@Nadweb wrote:
I feel like it must be optional. The terminator settings on the 340 are CR, LF, CR LF, and LF CR, so they should all be valid for any program. Currently it's set to LF, ...
Ah, so there's a configurable value on the device that allows you to choose? Good to know - in that case, you could pick whatever you want, but a) make sure you match that in LabVIEW, and b) if you choose a single character it will be easier, so your LF choice is probably the best option.
@Nadweb wrote:
I can [...] append them as you suggested, so the command control is just KRDG A? and the block diagram adds a [
\r and then a] \n.
I'll have to report back what I learn
If you have it set to use only LF, then stick with that. But yeah, exactly as you said here, writing just the "command" bit and then using constants on the Block Diagram with Concatenate Strings (or Format into String, as appropriate, depending on how you're already set up for adding numeric values etc) can be a nice choice to simplify usage (and avoid your "user" - perhaps also you, but anyway... - having to know too much about underlying details).
