Version conversion 7.0 to 2012

[ErikSBUC85]

Hi,

Could someone give me a hand with updating this Vi(version 7.0) to 2012 version?  I get an "enumeration conflict" in one of the sub Vi's, and it seems starting from the ground up is my only option without updating.

Thanks!!

[K C]

Hi,

This board is only for conversion. Please ask your question about your program at another board.

I did have a look at your program but the VI's are password protected. Remove the protection so we can actually help you with this.

Kees

[ErikSBUC85]

Hi Kees,

I misunderstood. My version works perfectly on 7.0 but has many errors on 2012 which I believed was a conversion issue. I've removed the password.  Any suggestion on the right approach to address this, or how I should pose this question in another board, would be great help, thank!

[chembo]

I don't have LabVIEW 2012, but I can load your VIs in LabVIEW 2011 and LabVIEW 2013 without any errors.

There is just one warning:

C:\___temp\IOPFlow_VI_with_LISST_9_12_2011_4_48_pm.llb\Details Display Dialog.vi (Details Display Dialog.vi)
    - The control expected to be at "C:\___temp\IOPFlow_VI_with_LISST_9_12_2011_4_48_pm.llb\eventvkey.ctl" was loaded from "C:\Program Files (x86)\National Instruments\LabVIEW 2011\vi.lib\event_ctls.llb\eventvkey.ctl".

[Kelle]

Erik, I downloaded and openned your VI in LabVIEW 2012 32-bit.  Same warning as Kees, but I don't think that should be an issue... Can you attached a screenshot?  Here is something on "enumeration conflict": http://zone.ni.com/reference/en-XX/help/371361H-01/lverror/edenumconflict/

What do you mean by conversion issue?  Did you try to convert it or are you saying you are getting errors just openning this VI in 2012?

[ErikSBUC85]

The odd thing I encountered was that I don't have this "enumeration conflict" when operating with version 7.0.  When the VI is opened and run in 2012 this error occurs.   My buest guess was there was some varations made over the years to the function inputs which made the enumeration definition less critical? 

I'm mainly curious if anyone had seen this when porting a VI written on an old version(7.0), to a new one; where the output from an Event Data Node, or expected input for compatReturnToEnter.vi had changed. I read somewhere that removing the .lib files associated with the .llb may force a newer library to be used, but that could be a whole other can of worms.

[Kelle]

I guess one of the issues with us trying to figure out why this error is happenning for you is that we cannot reproduce this error.  We are getting the warning because you have packaged in your llb VIs that come with LabVIEW, so it is taking those that are in the LabVIEW path versus your library.  It really shouldn't be an issue unless you changed these files in the library that you made.  Is IOPFlow_VI_with_LISST_9_12_2011_4_48_pm.vi the only VI that you created/have made changes to? I didn't go through every VI in the llb, but they seem to all be LabVIEW ones... 

I actually openned your VI again, and here are a list of warnings I got this time around, it gives more info... stuff you may be interested in

C:\Program Files (x86)\National Instruments\LabVIEW 2014\vi.lib\_oldvers\_oldvers.llb\compatReturnToEnter.vi (compatReturnToEnter.vi)
    - The control expected to be at "<vilib>:\event_ctls.llb\eventvkey.ctl" was loaded from "C:\Users\____\AppData\Local\Temp\IOPFlow_VI_with_LISST_9_12_2011_4_48_pm-1.llb\eventvkey.ctl".
C:\Users\____\AppData\Local\Temp\IOPFlow_VI_with_LISST_9_12_2011_4_48_pm-1.llb\Details Display Dialog.vi (Details Display Dialog.vi)
    - The Event structure now differentiates the <Enter> key from the <Return> key.  This may cause some key events not to work as they did in previous versions.
    - The property for key navigation has changed for Boolean controls.  Previously, this key would toggle and focus the Boolean control.  Now it will only focus the control.  Use the Toggle Key Binding property for the previous behavior.
    - The property for key navigation has changed for Boolean controls.  Previously, this key would toggle and focus the Boolean control.  Now it will only focus the control.  Use the Toggle Key Binding property for the previous behavior.
C:\Users\____\AppData\Local\Temp\IOPFlow_VI_with_LISST_9_12_2011_4_48_pm-1.llb\General Error Handler CORE.vi (General Error Handler CORE.vi)
    - LabVIEW changed a constant that was wired to a Case structure to a hidden control to maintain compatibility with LabVIEW 7.1 and earlier.
C:\Users\____\AppData\Local\Temp\IOPFlow_VI_with_LISST_9_12_2011_4_48_pm-1.llb\Open File+.vi (Open File+.vi)
    - The File Dialog function now outputs an error cluster.  An Unbundle function was inserted to maintain compatibility.
C:\Users\____\AppData\Local\Temp\IOPFlow_VI_with_LISST_9_12_2011_4_48_pm-1.llb\Three Button Dialog CORE.vi (Three Button Dialog CORE.vi)
    - The property for key navigation has changed for Boolean controls.  Previously, this key would toggle and focus the Boolean control.  Now it will only focus the control.  Use the Toggle Key Binding property for the previous behavior.
    - The property for key navigation has changed for Boolean controls.  Previously, this key would toggle and focus the Boolean control.  Now it will only focus the control.  Use the Toggle Key Binding property for the previous behavior.
    - The property for key navigation has changed for Boolean controls.  Previously, this key would toggle and focus the Boolean control.  Now it will only focus the control.  Use the Toggle Key Binding property for the previous behavior.

[chembo]

You could check the VI hierarchy of your main VI (disable the 'Include VIs in vi.lib' option). I would leave all listed VIs in the .llb and remove all others, which are part of the vi.lib. When you open the main VI again it will load all needed VIs for the current vi.lib.

[ErikSBUC85]

Thanks guys,

I see what you're getting at with potential alterations to the VI's in the library.  I have not made any alterations to sub Vi's, but another person which is no longer with us assembled most of program and there are several custom sub VI's designed for the system.  He could have tinkered with several VI's, and I don't have the road map unfortunately. 

What got me were the warning statements as mentioned:

"The property for key navigation has changed for Boolean controls.  Previously, this key would toggle and focus the Boolean control.  Now it will only focus the control.  Use the Toggle Key Binding property for the previous behavior."

"LabVIEW changed a constant that was wired to a Case structure to a hidden control to maintain compatibility with LabVIEW 7.1 and earlier."

"The property for key navigation has changed for Boolean controls.  Previously, this key would toggle and focus the Boolean control.  Now it will only focus the control.  Use the Toggle Key Binding property for the previous behavior."

It seemed like I needed to retain the exact library to retain all the capability of the main VI.  I'm not any expert at this, so I admit that my conclusions could be innacurately founded.

Thanks again for the suggestions.

[Kelle]

Erik, I think I had the password protected one open when I got all those warnings... I openned the non-password protected one and I am getting the same single warning as Chembo.  I had referenced Kees earlier, but I actually meant Chembo.  I would try out what Chembo suggested with the llb.