Importing labview code into labwindows

[jagadeesh]

Hi all,

I have the code devloped using labview evaluation version and the code runs nearly 15 files connected and now there is a requirement to change over to labwindows 7.1 full vesion? can any one suggest me to come out of this problem? I am new to both these fileds.

thanks
Jagadeesh Raju

[LV_Pro]

Depending on what you have developed in LabVIEW it may be that you can use some (if for instance you created .dll's. Otherwise I think that you may end up just using the knowledge gained when you rewrite the code in LabWindows/CVI. LabWindows is just a nice environment to develop C code in. While they both have controls available that resemble each other the final product (code) is very different.

What is driving the "conversion" from LabVIEW to LabWindows?


Putnam Monroe

[jagadeesh]

Thanks for your suggestion Putnam Monroe,

I have used the basic functionalities in labVIEW like tree structure event cases and so on... I am able to convert it into .llb but I think it only wraps all the files in a directory.

The intension of switching over is due to the requirments by our project lead.

can anyone suggest a solution

thanks
Jagadeesh Raju

[tst]

He said DLL, not LLB. A DLL is a library of functions which can be called from any application.
This means you compile your LV code into an executable (the DLL) and the functions in that DLL will be called from CVI, but executed by the LV run time engine, so at least you don't need to rewrite the code. It's actually quite a good idea, provided your code is finished and it works.
You can create a DLL with the application builder. There should be some information on this site for how to build DLLs.

[Dennis_Knutson]

As everyone has said, your only option to use already developed LabVIEW code in LabWindows is to create a DLL that LabWindows can call. However, since you only have the evaluation version of LabVIEW, you don't have the necessary option (app builder) to create a DLL. That leaves you with two options. You can buy the professional version of LabVIEW that comes with the app builder or ask very nicely and see if someone here will create the DLLs for you. If you select option 2, then if you find any bugs or need to make changes, you would have to ask again for help in creating a DLL and hope that the evaluation version of LabVIEW hasn't expired so that you can actually make the changes. The way I see it, your only real options is to abandon the LabVIEW code or buy a copy of LabVIEW.