Labview 5.0 compiled code

[grabla]

Hi all

I have a challenge on my hands, to migrate Labview 5 on to a modern platform. The code running is apparently compiled using something called the developer pack, and all I have is a VI file.

In order to move the code from the Legacy PC, will later versions of Labview run the compiled code, or am I looking at trying to get Labview 5 running on Windows 7 64bit, and if that is the case, what are peoples experiences in doing that?

When I do eventually locate the source code, will it need recompiling for a later version of LV, or does LV simply interpret it?

Graham

[RobertoBozzolo]

Hello grabla, you ended up landing on the LabWindows/CVI board with a question on LabVIEW 

I notified the moderators to move your question to the proper board, but in the future pay more attention where you post your questions.

[Mark_Yedinak]

If the file truly is a VI, you should be able to open it in a later version of LabVIEW. It is possible the code will be broken if it is using some old depreciated code. This is generally fairly easy to fix though. Another issue you may run into is if this code is calling other subVIs. You will need to copy those as well to the new computer.

[crossrulz]

---

@grabla wrote:

When I do eventually locate the source code, will it need recompiling for a later version of LV, or does LV simply interpret it?

---

You need an in-between version to upconvert to first.  I tend to use LabVIEW 8.2.1 for such conversions and I then can open the VI in any newer version.

How to Upgrade or Revert a VI to a Different Version of LabVIEW

Or you can post the code to the Version Conversion board and one of us will convert it for you.

[Hooovahh]

Developer Suite?  Never heard of developer pack.  If you have the VI source you should be able to just open it.  There is a limitation on what version of LabVIEW can open what VIs so you may need to either open it in some version in between, or have someone resave it for you after opening it in some version that is compatible.  Generally if you have the VIs then you are good.  If the user put password protection, then you may have more difficulty.  And if the developer removed the block diagrams, then you have no option but to re-write the code, find a back up, or be stuck forever running in the LabVIEW 5.0 runtime.  If you feel like this is a task too large NI recommends contacting one of their alliance partners who can help re-write your code, or redesign your system if you need to.

[Jacobson-ni]

In addition to what others said, until you open the VI up it's hard to know what dependencies you might need. Tracking those down may be just as big of a challenge.