LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Different behavior with same exe on different computer

Solved!
Go to solution

Hello,

 

I have a problem with a labview executable.

 

On my development pc the source and exe work perfectly fine as intended.

On the deployed pc the executable starts, but some of the input fields are reseted every 2-3 loop.

 

Labview 2018 Sp1

Windows 10 pro

0 Kudos
Message 1 of 8
(185 Views)

Hi folder,

 


@Localfolder wrote:

On my development pc the source and exe work perfectly fine as intended.

On the deployed pc the executable starts, but some of the input fields are reseted every 2-3 loop.


Error analysis: you made something wrong.

Suggestion: you need to debug your program!

 

What kind of suggestions do you expect when you provide so less information?

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2020 sometimes) on Win10+cRIO
0 Kudos
Message 2 of 8
(178 Views)

Hi Captain,

 

What i don't understand, is that my executable starts on both computer but have different behavior on these computers.
What component is not included in the runtime engine that can produce this kind of reset ?

 

Regards,

L

0 Kudos
Message 3 of 8
(164 Views)

Probably a race condition 

Certified LabVIEW Architect
Message 4 of 8
(156 Views)

Hi L,

 


@Localfolder wrote:

What component is not included in the runtime engine that can produce this kind of reset ?


How should we know? We don't know your program as you don't provide any neccessary information…

 

Which results does your error handling/logging provide?

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2020 sometimes) on Win10+cRIO
0 Kudos
Message 5 of 8
(155 Views)

hi,

 

I wired all my function into one error handler to see what happen:

 

On the dev pc : no error, executable or runned

On the other pc : "Error 85, scan from string (arg 1)" in a vi from a GPIB driver for my Wayne Kerr 3260B

 

I can provide the dll form the driver but i dont understand why i dont have the error on my dev pc.

 

 

0 Kudos
Message 6 of 8
(110 Views)
Solution
Accepted by Localfolder

Hi L,

 

does the "other pc" use the very same decimal separator as your "dev pc"?

Most device drivers I encountered don't handle other regional settings than "English" very well…

 

Which VI does give that error? Which response string is giving the error?

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2020 sometimes) on Win10+cRIO
Message 7 of 8
(107 Views)

Hi,

 

That was that ! the decimal separator was different "," and "."

Both system are in english but the separator was not "." causing my issue.

 

Thank you very much !

 

Regards,

 

C

0 Kudos
Message 8 of 8
(103 Views)