Building Executables - performance etc.

[Maddack]

Hi. I am making a (quite simple) motion simulator for a company. Since we have Labview 8.0 professional I decided to use it for this. I haven't received the hardware (NI USB-6008) yet (it is due in a week).

So I want to try the stuff I've done so far by building an executable. So I followed the instructions in this link.

[link removed]

I mainly have some file open and file scan routines in my application.

When I build my project it apparently wants to include a bunch of existing VIs, such as "Complex Back Transform Eigenvectors", "A x Vector" etc. from the vi.lib directory. I assume these are used by the various "File I/O" functions. It tells me that these VIs are not up to date and that I need to save them. When I do that it says I don't have permission to save (I am not administrator so I figure that's why). So I select the option "continue without prompts".

Question #1: Is it ok to do that? (It says build successful after, BUT the exe doesn't behave the way it is supposed to. Specifically it seems to run my while loop only once. But it still sits in the program eating cpu power.)

Question #2: If I run the simulator software, which runs at 50 FPS, and start the "data expraction exe" (described above), the FPS goes down to about 10. I figure solving question 1 would solve this one too, because when I run simulation software with the VI from LabView, there is no FPS problem. Would you recommend me to use two computers?

Question #3: Just to confirm: I need to buy a license for the Real time run engine (approx. $100) to install on the customer's computer, right?

Also we have Labwindows/CVI here too. Maybe someone would recommend me to use that instead?

Thank you for replies /Ville

[Maddack]

Anyone care to answer my questions?

[TCPlomp]

It seems like you have LV 8.0.1 but haven't mass compiled, do that first (options->advanced->mass-compile, make sure you select the right vi.lib

Q1 (run only once and stalling your CPU) is probably a bad program....
Q2 (FPS),  probably as Q1
Q3, no since you are using the Run time and not Real time (assumingly)

For Q1, make a new thread, describing the problems, and post some code, but firstly try to overthink the program and why it stops.

You can also try searching this site and google for LabVIEW tutorials. Here, here, here, here and here are a few you can start with and here are some tutorial videos. You can also contact your local NI office and join one of their courses.
In addition, I suggest you read the LabVIEW style guide and the LabVIEW user manual (Help>>Search the LabVIEW Bookshelf).

Ton

[Maddack]

Actually, after I got administrator access on this computer, it all worked perfectly!

But thanks for the info on run time vs real time engine. I will keep that in mind.