LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

String Error(85) with ALICAT MASS FLOW Controllers

Solved!
Go to solution

There is a consistent error occurrence (85) for the Parse Data Frame.VI . It appears that the scan from string function cannot convert the data that is incoming from the Data Frame Input. The Frame input data is {B\s+013.22\s+041.03\s+0.0001\s+0.0001\s+0.1000\s+0000.002\s\s\s\s\sN2\r}. How can i solve this? I have attached the VI below

0 Kudos
Message 1 of 6
(853 Views)

Hi John,

 


@johnsnowysnow wrote:

It appears that the scan from string function cannot convert the data that is incoming from the Data Frame Input. The Frame input data is {B\s+013.22\s+041.03\s+0.0001\s+0.0001\s+0.1000\s+0000.002\s\s\s\s\sN2\r}. How can i solve this?


For me ScanFromString is perfectly fine with your input data:

 

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 6
(786 Views)
Solution
Accepted by topic author johnsnowysnow

@GerdW wrote:

 

For me ScanFromString is perfectly fine with your input data:

But while you use a German locale setting you explicitly specify in the format string to use decimal points. The driver in question seems to have forgotten to add that to the format strings!

 

If the OP uses a locale that specifies a decimal comma as standard decimal indicator, the driver has to fail in parsing the responses correctly.

 

Quick fix would be to go into the LabVIEW configuration settings and disable under General the settings "Use localized decimal point" and restart LabVIEW. This will however mess with every single string formatting that does not explicitly select a specific decimal point, so if you then write something to a text file and try to load it into Excel the number will be misinterpreted as Excel uses the localized decimal point.

 

Proper fix is to prepend all format strings in the driver with a %.; for any Scan From String and Format into String that contains at least one floating point parameter.

Rolf Kalbermatter
My Blog
0 Kudos
Message 3 of 6
(779 Views)

We changed the scans from  %f  to %f %s. Now it works fine, thank you for your input.

0 Kudos
Message 4 of 6
(769 Views)

Hi John,

 


@johnsnowysnow wrote:

We changed the scans from  %f  to %f %s. Now it works fine,


This sounds like a workaround,but not like a solution… 😄

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 5 of 6
(758 Views)

Hi i am also working with the same Alicat MFC. Just started to build. Can you share your both block diagram and front panel vi, if possible. It would be very help full. Thanks 

0 Kudos
Message 6 of 6
(336 Views)