Problem with inconsistent behaviour of a VI file in Labview 7.1

[Wall-e]

Hi all,

I am initiating a .vi file from a program I use to log data from a device.  When the .vi file is first executed from a process by the main visual c++ program, the behaviour is as expected, with all channel results logged to text-files (I use triggered, sequential loggging of the channels with the logging starting on the first activity on the channel) .  When the application is again run after that, only the first channel is logged.  This remains to be the case until I open the .vi file directly without the use of a process and save it (with no changes made).  The next execution (when run as a process) is again as expected and defined.  The execution after that only logs the first channel yet again.  The channels logged produce consistent behaviour, so it has to be an issue with the .vi file or the execution thereof.

I end the Labview 7.1 process properly, using shortcut keystrokes, so I have no idea why this behaviour is occuring. 

Does anybody have any explanation on this?

Thanks is advance

[JB]

You should post this question to the LabVIEW board.

[altenbach]

I am replying here, in the hope this thread will be move to the LabVIEW forum.

---

Wall-e wrote: 

I am initiating a .vi file from a program I use to log data from a device.  When the .vi file is first executed from a process by the main visual c++ program, the behaviour is as expected, with all channel results logged to text-files (I use triggered, sequential loggging of the channels with the logging starting on the first activity on the channel) .  When the application is again run after that, only the first channel is logged.  This remains to be the case until I open the .vi file directly without the use of a process and save it (with no changes made).  The next execution (when run as a process) is again as expected and defined.  The execution after that only logs the first channel yet again.  The channels logged produce consistent behaviour, so it has to be an issue with the .vi file or the execution thereof.

I end the Labview 7.1 process properly, using shortcut keystrokes, so I have no idea why this behaviour is occuring. 

Does anybody have any explanation on this?

---

 There is a lot of missing and conflicting information, but most likely your program has some race condition. Can we see some code?

 You talk about initiating a vi from a C++ process, but then you talk about running the application again. Is the LabVIEW code a built standalone application? Are you later opening the VI in the development system? Does it show dirty (* in the window title bar)? What changes are listed in the properties? Does the VI leave memory between runs? How exactly do you end the LabVIEW process? What shortcut keys?

... so many questions... 😉 

Is this under windows, mac, or linux? 

Message Edited by altenbach on 03-19-2010 08:19 AM

[JB]

---

altenbach a écrit:

I am replying here, in the hope this thread will be move to the LabVIEW forum.

---

Note : The message was initially posted in the Breakpoint board. Now it has been moved, my previous message can be ignored.