build exe

[DoctorG]

Hi there,

I'm trying to build an exe from my vi. When I test it on my machine (labview 2010 installed) everything is ok, but when I run it 

in a machine with labview run time 2010 it sems doesn't work. I can send you my vi and I hope someone of you will be able to get it works.

thank

G.

[RavensFan]

What do you mean by "it doesn't work"?

Do you get an error message?  Does the PC blow up?

What actually happens when you try to run it?

[altenbach]

Did you really install the std 2010 run time engine (171MB). (The min version (40MB) will most likely not work.)

Did you use LabVIEW 32 or 64 bit to build the exe?

(You might also brush up on your LabVIEW skills, because your code seems pretty useless. Why is there a 2 second delay in the inner loop? Why is there even an outer loop? Never operate on paths as strings, etc. Since everything happens in the inner loop, the stop button does not really do much)

[DoctorG]

What the iv should do is to select all the  .edf file from a specific folder and convert them in TDMS file.

The outer loop is used to stop the vi after it finish to convert the last file and the delay.....I forgot them there....what do you mean "Never operate on paths as strings".

However, I used labview 32 bit to bild the .exe file, and I installed the  std 2010 run time engine 171MB.

[DoctorG]

The .exe file do  not create the TDMS file.

[altenbach]

---

@DoctorG wrote:

What the iv should do is to select all the  .edf file from a specific folder and convert them in TDMS file. 

---

You convert them to tdms with an *.edf extension, then add a second .tdms extension (source and target paths are the same!). Wouldn't it make more sense to edit the target file path instead instead of editing the output? Shouldn't the file dialog be configured to only select existing folders?

---

DoctorG wrote:

The outer loop is used to stop the vi after it finish to convert the last file and the delay.....I forgot them there

---

The delay in the outer loop runs in parallel to the inner loop and is thus meaningless. The outer loop never spins more than once and if you would delete it, nothing would change. The stop button is useless too, because the loop will stop after one iteration no matter what, and while it is processing the inner FOR loop, the stop button is ignored anyway.

---

@DoctorG wrote:

....what do you mean "Never operate on paths as strings".

---

In this particular case it does not make a difference, but path to string and string to path often introduces incompatibilities between platforms. Typically you would use "strip path" to get the file name, edit the file name, then use "build path" to make the new path.

---

@DoctorG wrote:

The .exe file do  not create the TDMS file.

---

Is the folder writeable? What happens of you add an error indicator to the error output of the convert tool? Does it show anything interesting? Any other error messages?

Did you build an installer or did you simply move the exe to a new machine. Don't forget to also copy the "data" folder.

[DoctorG]

I take the advice of removing the outer loop.

This is the error message:

Node method in _openDataStorage.vi->_openWithRoot.vi->_openStorageWithRootNoPluginCheck.vi->_openStorageWithRootAutoDetect.vi->Convert to TDM or TDMS.vi->EDF-TDMS Converter GC.vi Connect data storage

When i create the exe file I notice that labview didn't create the data folder.

In other cases when I created an exe file I saw this folder

Does it help?

[Yamaeda]

It sounds like you'r creating a faulty file/path or dont have access rights to the file/folder.

/Y

[DoctorG]

I don't think so....the iv found the file and it seams it convert it, but it doesn't write them?

I sent you the edf file so you can play with it.

[Yamaeda]

I got an error message saying i dont have the EDS plugin. Do you on target computer?

/Y