labview application.exe

[saidanikhayri@gmail.com]

When testing my program on the LabVIEW Front Panel, it functions correctly. However, when i build it into an executable application (".exe" file), it defaults to a default message from a case structure i created and get stocked there.

[GerdW]

Hi saidanikhayri,

---

saidanikhayri@gmail.com wrote:

When testing my program on the LabVIEW Front Panel, it functions correctly. However, when i build it into an executable application (".exe" file), it defaults to a default message from a case structure i created and get stocked there.

---

And what is your question?

I guess your program does exactly what you have programmed it to do, so you better check what you have programmed and compare that with your requirements!

[Bob_Schor]

Do you have a colleague with any experience in LabVIEW?  Perhaps a classmate taking the same class with you?  Someone with any experience in programming?

Show them your LabVIEW code, explain to them (if they don't know LabVIEW) what all the wires and diagrams mean, and either they will point out your mistake or you will suddenly realize your own error.  Remember, all LabVIEW programs do what you tell them.  Good LabVIEW programmers tell LabVIEW to "do the right things" to accomplish their goals.

Bob Schor

[Michael_Munroe]

There are 2 types of case structures that behave differently.

1. Case structures may have a default case that executes if no other case is an exact match.  Check your code to see what input could cause the default selection 

2. Conditional case structure is a great way to override sections of your code for testing or supporting multiple uses. Create cases using defined symbols and define the symbols to control which case is executed. When compiled into an EXE, the default case is selected because the symbols only exist in the project.

There is also a diagram disable structure, but it does not change when compiled.

Techniques to debug EXE:

1. Add message box to the case selection to show what the value is

2. Add an indicator to the panel to show the selection 
3. Write the selection to a text file

4. Create a Shared Variable for the selection and view it with the Distributed Systems Manager 

[saidanikhayri@gmail.com · Accepted solution]

thank you so much like you said yes, I already solved the problem. Actually, the issue was that I had prepared the program's connection with the PLC (I/O). However, the program was looking for the PLC (input/output) in a specific IP configuration that I hadn't created yet, which is why it gave us an error message.