LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

compile and run hotkey

Every Programming GUI i know has a Compile and Run Hotkey.

Fot LV i only found Ctrl+R for start in Interpreter.

 

But how can i recompile to get usable speed?

================================
system: Win7 and debian stable
0 Kudos
Message 1 of 14
(1,399 Views)

LabVIEW does not run an interpreter. It hasn't used an interpreter since version 1. Your code is compiled as you program it.

 

You can force a recompilation by holding down the control key and pressing the run arrow, but this is rarely required and is usually intended to be used when trying to diagnose potential compiler issues.

 


But how can i recompile to get usable speed?

I have no idea what this means.

0 Kudos
Message 2 of 14
(1,396 Views)

if i press Ctrl+R my VI is extremely slow.

 

if i build a binary (.exe) file it runs something like 100 times faster

================================
system: Win7 and debian stable
0 Kudos
Message 3 of 14
(1,393 Views)

That doesn't mean the code is interpreted. When you build an app certain stuff gets stripped out. For example, the front panel of subVIs. Thus, if you're running in the development environment and you have a subVI open, then there will be a slow-down as the front panel is drawn. How much of a slow-down depends on what's actually on the front panel.

0 Kudos
Message 4 of 14
(1,390 Views)

Since your Executable lacks debugging functionalitys the compiler can optimize the resulting binary.

Assuming you are using LabVIEW 2010 or 11 you can disable Debugging to increase the runtime performance.

To disable Debugging got to File>VI Propertys>Execution "Allow Debugging"

 

0 Kudos
Message 5 of 14
(1,371 Views)

@asdfsfdasdafasdf wrote:

if i press Ctrl+R my VI is extremely slow.

 

if i build a binary (.exe) file it runs something like 100 times faster



A sub-vi has Highlight execution on?

/Y

G# - Award winning reference based OOP for LV, for free! ADDQ VIPM Now on GitHub
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
Certified-LabVIEW-Developer
0 Kudos
Message 6 of 14
(1,369 Views)

Thx was just thinking about Highlight as well, but disabling Debugging will disable Highlight as well Smiley Wink

0 Kudos
Message 7 of 14
(1,367 Views)

@Wetzer wrote:

Thx was just thinking about Highlight as well, but disabling Debugging will disable Highlight as well Smiley Wink



True, the point we're both doing is that one sub-vi OP's probably debugged is in highlight mode. Disabling highlighting as well as disable debugging must be done on a per vi basis.

/Y

G# - Award winning reference based OOP for LV, for free! ADDQ VIPM Now on GitHub
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
Certified-LabVIEW-Developer
Message 8 of 14
(1,352 Views)

Highlight execution is set to off.

Is there a trick, how i can check all sub-vi's at once if its on?

 

================================
system: Win7 and debian stable
0 Kudos
Message 9 of 14
(1,335 Views)

Do you know what highlight execution is? It's the light bulb in the toolbar, and it's only available if you have a block diagram window open.

 

I'm curious as to what your code is doing that you'd see such a huge difference between running it in the development environment and running it as a built app. Care to share?

0 Kudos
Message 10 of 14
(1,327 Views)