need help converting VI to a newer version

[Kyle B]

Hey everybody.  I need some help converting a VI that was created in LabVIEW 6.1.  The next newest version I have is v8.0.  I don't think that 8.0 will convert a 6.1 VI, am i correct?  I think the furthest it will go back is v7.0.  Let me explain what I'm doing first before asking the question.  I work in a research lab (college) and we have a program written in 6.1.  We are upgrading the computer and i need to move this VI (as well as the hardware it ran) to a new PC. 

As far as i know, all that needs to be done is:  Open the VI in v7.x, convert it, and then open that VI in 8.x. ?

any help or advice would be appreciated.  If someone can convert them for me let me know and i will upload the VI.  Thanks in advance

[MikeS81]

Hi Kyle B,
i think to open a 6.1 vi in 8.0 is no problem. Did you try it?

Mike

[Kyle B]

I have tried it but it comes with alot of errors.  Maybe since 6.1 a few subtle things (like snytax) have changed?  It may be a problem with actually moving the file.  I've copied the entire lib. that it needs to the new computer.  I'm suspecting that i will have to re - tell the program where to look for the hardware since they are probably different in the new machine than in the ol one..

sound good?

[MikeS81]

Hi Kyle B,
if it is not possible to open your vi, you will get the message that the vi as saved for a to old version. I think you are in another situation. If you want, you can upload it, then i can try it.

Mike

[smercurio_fc]

---

@Kyle B wrote:

I have tried it but it comes with alot of errors.  Maybe since 6.1 a few subtle things (like snytax) have changed?  It may be a problem with actually moving the file.  I've copied the entire lib. that it needs to the new computer. 

---

What kind of errors? File not found? Do the VIs actually open and show up with broken arrows? What? Yes, there have been changes to functions, but with each version NI created wrapper VIs to allow older code to still be opened.

---

@Kyle B wrote:

I'm suspecting that i will have to re - tell the program where to look for the hardware since they are probably different in the new machine than in the ol one..

---

Was the code using DAQ? If so, it was probably using the "Traditional" DAQ. With LabVIEW 7 NI started to shift towards DAQmx, which is a different library. You can still install Traditional DAQ.

[Kyle B]

Ok, I was able to spend some time re-programming some stuff in the program written in 6.1.  The program is now fully functional and works wonderfully (and much faster) on the new machine.  However, when i attempt to open the file in 8.0 I get a long list of errors, regarding many of the sub VI's in the program.  I'm going to post a list of them below.

When i first open the program i get this warning.

"Open File+.vi
    - The File Dialog function no longer supports the datalog type input.
    - The File Dialog function now outputs an error cluster.  An Unbundle function was inserted to maintain compatibility."

After clicking the ok button to get it out of the way I try to run the program (note that there is a broken arrow so that it will not run)  I get another list of errors:

they all have this in common (this is the common error): "The subVI is not executable. You must fix all errors in the subVI before this VI can run."

this happens with these VI's:

Write to spreadsheet file.vi

Read from spreadsheet file.vi

Simple error handler.vi

Read lines from file.vi

Read characters from file.vi

Error code database.vi

General error handler.vi

Thanks in advance!

Kyle B

[smercurio_fc]

The first part with the Open File+ is not an error - they're warnings. The interface for that VI changed. Actually, that VI was replaced, but a wrapper exists, as I mentioned. The warnings tell you what was changed, in case this affects your code. More than likely it won't. The first warning is telling you it no longer supports a specific type of input. The second is probably due to the 6.1 version having a numeric output for the error code rather than the full error cluster. It's just telling you what it did.

The others seem to imply that you have a VI with the same name as one of the VIs in the LabVIEW vi.lib directory. Simply listing the VIs with errors is not enough. When you click on each VI in the Error List dialog box you will get the list of errors, like this:




Message Edited by smercurio_fc on 06-12-2008 04:24 PM