Labwindows to Labview programmming

[billko]

---

@GerdW wrote:

Hi Anand,

Is there any tool available to convert Labview vi to .c source code. This for my understanding going forward.

There is a tool(kit).

But I guess you don't want to pay >10k$ just for "going forward"…

---

If you've already paid $5k for a LV pro license, maybe another $10k isn't such a big deal.  😉

[GerdW]

Hi,

I never needed this toolkit but NI offers it.

Well, the OP can always call its local NI sales rep and ask for price and availability…

[Kevin_Price]

I just want to expand on one little part of the truly excellent summary from BowenM.

Use sub-vis regularly.  Even though each sub-vi is a separate file, think of them in terms of functions rather than files.  

Another incredibly useful feature of subvi's that I tend to take for granted after years of using them is this:  you can open and run them all by themselves, and you'll already have a gui available to let you change the inputs and observe the resulting outputs! 

   It doesn't matter if it's a subvi that's several layers of calls below the "main" startup vi.  You can open it and run it all on its own.  And you *should*.  Making each small simple subvi work correctly as it's being built saves untold amount of later debugging in the bigger, more complex full application.

-Kevin P

[BowenM]

---

@AnandR wrote:

Is there any tool available to convert Labview vi to .c source code. This for my understanding going forward.

---

There is.  It is not useful as a learning tool.

The code produced by the c generation toolkit is technically c (it will compile!), but is programmatically generated stack based c.  This means it is efficient, etc but not exactly human readable.

The c generation toolkit also doesn't support a lot of LabVIEW's core functionality such as event structures, timed loops, and cluster data types.