I'm probably just missing something simple, but this behavior suprised me. I'm using LV 2013 32 bit on W7, 64bit. The attached VI shows the problem, and is shown in the image as well: First run the program, with some value (such as 5.43) in the string and NO error. Then check the Error Boolean, and finally while it all is still running, change the string value. (In the screen shot I changed it to 56.22.) The error in to the Scan From String function prevents it from analyzing the string, as I would expect. But the "output 1" retains the previous value of 5.43! I would expect it to go to the default value of 0. I see no mechanism for how Scan From String can be remembering its previous value. Does anyone understand why it behaves this way?I tried wiring the "default value 1" input with a 0, and then it behaves as expected. When there is an error input, I get the default value I specified. Makes sense. By why does it remember a previous value when there IS an error in? I would expect it to use the "default" default, which is 0. Thanks, DaveT

ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

Odd behavior with Error In for Scan From String function

@natasftw wrote:

Does anyone want to clarify how Error In impacting a scan using or ignoring a default value is the "same issue" as a disagreement over how complex numbers should be parsed?

No one said they were. There were separate issues.

Message 11 of 12

(1,028 Views)

@Darin.K wrote:
For example, in LV2014SP1: error out but not default out. Same issue as DaveT.

While I'd agree they're separate issues. I've quoted the post where it was claimed they were the same.

Message 12 of 12

(1,007 Views)

LabVIEW

Odd behavior with Error In for Scan From String function

Re: Odd behavior with Error In for Scan From String function

Re: Odd behavior with Error In for Scan From String function