LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

End of file encountered on FormatIntoSting

As I was saying earlier, units are buggy.  You are best off stripping out the units.

 

Taking your crash2.vi, I made a simple modification that converted meters to micrometers, effectively stripped the units, and added um to the format code so the units would show up there.

 

Any where you need to format a number with units into a string and you get thus error message, you only need to make 2 modifications to your VI.  1.  Add the Convert Units function just before the format into string.  2.  Edit the Format String constant.

 

 

I think this is the best you can do to work around this bug whenever you are still forced to be using units by your colleagues.

 

 

Message 11 of 13
(768 Views)

There seams to be a bug.  Precision and casting units works for everything but %f  but Significant Digits and units work fine.  e.g. %_8{um}f displays     "h initial scan complete, FWHM = 4765548.8 um"


"Should be" isn't "Is" -Jay
0 Kudos
Message 12 of 13
(762 Views)

Yes, I've been down that road already.  Fixed a VI with that problem, rerun, errors out somewhere else, fixed that VI, etc.  

Things work but I'm patching a basic problem as I go along changing VIs without understanding what is going on.

 

I already found the source of the problem, which points out with another LabVIEW problem with cascading typedefs with units.

0 Kudos
Message 13 of 13
(755 Views)