LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Difference between Build/development environment

I have a problem when I want to read an SSH network log in a created Labview project. The SSH log is sometimes not read, but when I debug in the development environment it does not happen. Now I would like to know what is the difference between build/development environment?

0 Kudos
Message 1 of 6
(2,301 Views)

Hallo Anfänger beim EFZ,

 


@AnfängerEFZ wrote:

Now I would like to know what is the difference between build/development environment?


The main difference is the debugging code (most often/by default) not included in the built executable…

 


@AnfängerEFZ wrote:

The SSH log is sometimes not read, but when I debug in the development environment it does not happen.


Did you check for error codes? Do you get any errors when the log file "sometimes is not read"?

Best regards,
GerdW


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

Hi GerdW

 

there isnt any error. 

 

I'm sorry, it's not an SSH protocol, it's an xml file that I have to read! 

AnfngerEFZ_0-1630312775334.png

If there is an error it should get out of while-loop at least.

 

Could it probably be a timeout problem? 

0 Kudos
Message 3 of 6
(2,283 Views)

Hi Anfänger,

 


@AnfängerEFZ wrote:

there isnt any error.

I'm sorry, it's not an SSH protocol, it's an xml file that I have to read! 

If there is an error it should get out of while-loop at least.

 

Could it probably be a timeout problem? 


There are several subVIs in this loop which seem to be your own implementations: what happens inside them?

 

When you want to read a file, but you can't, then you should get an error message!

When it is a timeout "problem" then you should get either a timeout error, a timeout warning or a dedicated output on any of those subVIs to flag the timeout…

Best regards,
GerdW


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

I am just going to throw this out there... The most common reason a program that runs fine in the development environment and fails when it is a compiled EXE, is race conditions in your code.

 

Probably a near second that might be more applicable here, is hard coded file paths that are not present when running a compiled EXE.

 

But of course since you have not posted any of your code all we can do is guess what you did wrong...

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 5 of 6
(2,233 Views)

@AnfängerEFZ wrote:

I have a problem when I want to read an SSH network log in a created Labview project. The SSH log is sometimes not read, but when I debug in the development environment it does not happen. Now I would like to know what is the difference between build/development environment?


There is no way for us to debug this from a picture. (I notice a coercion dot, but the rest is opaque).

 

You say "sometimes" it does not work and I understand from this that "sometimes it works" in the executable. This basically leaves us with a race condition or permission issues. Could it be that some other program is accessing and locking the file at the same time? What is the exact error you are getting?

 

(If it "never" works in the exe, the causes are often simpler. For example relative paths to external files are different in the two scenarios. Is that "SSH network log" located on the local computer or a network location?)

0 Kudos
Message 6 of 6
(2,219 Views)