running problem of exe files

[Alan Cheuk]

Hi,

I am using DataSocket in my VIs to publish and receive data. Both of the VIS are changed to exe files. My problem is that sometimes the VI used for receiving data will stop automatically. Since I need to receive the data continuously, the VI used to receive data cannot stop. Does anyone know why this happen and how can I solve this problem?

Thanks

[pawel]

Hi Alan
What do you mean by "stop automatically". I understand it is not intentional stop? I guess that you will need to post your code to see why this vi stops.

cheers
Pawel

[RayFarmer]

hi,

If its in a continuous loop, what are you using to terminate the loop?


Regards
Ray Farmer

[Ray.R]

Thanks R.Farmer..

You read my mind. There must always be a way to stop a running vi.
Maybe the condition is set for some unexpected reason.

Is it possible to post the vi?

JLV

[Alan Cheuk]

Thank you for the helps.

My situation is that I use a while loop in my VI to receive the data continuously and write the data into a text file. To stop the VI, I only use a stop button in front panel to terminate it (no other condition). Theoretically, the VI must running continuously until I press the stop button in the front panel. Most of the time everything work properly that the VI can running continuously to receive the data. But in some cases, the VI is stopped even nobody press the stop button (after running for an hour). Will this problem related to the network? Will the VI stop if the network is not stable?

Regards,
Alan

[Philip_Courtois]

Hi Alan,

According to your explanation, it sounds very unlikely that the VI will just stop without warning - at least you should get some sort of error.

Please submit the VI or a screenshot of the block diagram. It will then be much easier for us to help you. I'm sure there's a logical explanation for this behavior.

Thanks!

[Ray.R]

As Philip says, it is unlikely that it stops by itself.

An error probably stops the vi. Do you get an error message?

Do you wire an Error-In all the way to the outside of the loop to an Error-Out? If so, what is the message and the error number, if you do get one? Or does it say pass?

Can you post a screen capture of both the loop and the front panel, with the Error Cluster (Error-Out Display).

Thanks,

JLV

[Alan Cheuk]

Hi,

The attached zip file contain the screenshot of my VI.
There are 4 sequence in it. Sequence 0 is to receive the data. Sequence 1 is to unbundle the received data. Sequence 2 is to write the data into text file. Sequence 3 is to make a time delay. Thanks for your help.

Regards,
Alan

[Philip_Courtois]

Hi Alan,

Your issue is very odd. Looking at your code, there doesn't seem to be anything that could cause the application to stop. Frame 1 and 3 are definitely not able to generate an error that would stop the application, frame 2 SHOULD generate a popup dialog (Simple Error Handler.vi) if a file error was detected. Frame 0 should only give an error if the Front Panel Datasocket connection for the P1 cluster is missing. Even when closing the Datasocket Server or specifying a wrong IP address the VI would continue to run.

Are you by any chance controlling this VI dynamically from another VI (VI Server)? Does the screenshots show all the code of the VI? What value is "wait"?

Even though I can't tell you what stops your specific example, there are certain things I would like to point out:

Why do you specify the Datasocket URL and Mode continuously in the loop? Since you are using Front Panel Datasocket, you should just set it up when configuring the Front Panel Datasocket in the Datasocket Connection dialog box.
There's no need for Local Variables in your VI. Instead of Local Variables, connect to the controls and indicators directly. Convert "IP" to a control and disable it if you don't want the user to be able to change the value. To disable a control, right-click and select "Advanced >> Enabled State >> Disabled".
You are over-writing the same file continuously. Is that the intension or do you want to append to the file?

I look forward to your answers...