what VI logger files to add as source files to application builder stand alone application

[gparant]

I am trying to run VI logger VIs in a Labview application that I have built using the Application builder. However, the VI logger does not seem to run once the application is built. It runs fine when I have not made the application.
I have set up the DAQ tasks on the computer on which the application will run on. However, I am not using the application distribution method. Instead I am running the application of our server. It works fine for all parrallel running VIs that I include in the source files tab of the application builder. I included the VI Logger and VI Logger Data libraries in the source files list, but that has not solved the problem.

Please advise.

Thank you.

[Aashish_M]

Hi Gparent,

Do you get any error codes?

What version of LabVIEW are you using?

I have noticed problems like this appear mainly when the VI Logger End is not called and improper input of task name to VI Logger Get Run Names.vi. Basically an empty string gets passed into it.

Hopefully this helps!

[gparant]

The problem is when I run it without making an executable, it runs fine. No errors. It records the data and stores it in a file just as I programmed it. However, when I make an executable using the NI Application Builder, it does not work anymore. The program itself works, but nothing is measured or written to file. The files are essentially empty. And this only happens for the VI Logger tasks. I wonder if it has anything to do with setting up NI MAX settings. Currently I set up NI MAX manually and have not saved a MAX configuration file. I wonder if there's any way to save the MAX configuration file and include it in the Application build? The other option is to use the Traditional DAQ VIs and rewrite what the VI Logger VIs do for my application but that seems like unnecessary work.

[Aashish_M]

Hi Gparant,

You might want to create a debuggable executable to see what’s going on in the application mode. Try referring to Debugging Applications and Shared Libraries for further help in doing that.

The other problem I foresee is that the VI logger could be logging empty strings of data. This could happen if it logs faster than acquired data appears.

Also, if you are using local variables, make sure that there are no potential race conditions.

Hopefully this helps.