Jump to content


Photo

VI Package Builder error


  • Please log in to reply
11 replies to this topic

#1 jkittle

jkittle
  • Members
  • 5 posts

Posted 15 November 2012 - 06:25 PM

When trying to build a VI package I get this error (abort message):

VIPM could not determine the LabVIEW version of the selected files. The package building has been aborted. Please try another folder.

I have only LabVEIW 2011 installed. All vi's were created/compiled with 2011. I'm using VIPM 2012. The package is a .lvlib which points to a number of vi's in a subdirectory.

Any ideas on why I'm getting this?
  • 1

#2 Ashish

Ashish
  • JKI Team
  • 256 posts
  • Gender:Male

Posted 15 November 2012 - 06:58 PM

Do you see LabVIEW 2011 in the "LabVIEW versions list" in VIPM 2012?

If not, here is an article on how to fix it: http://support.jki.n...ew-version-list
  • 0
Ashish Uttarwar
Product Support Engineer and Certified LabVIEW Developer, JKI

#3 jkittle

jkittle
  • Members
  • 5 posts

Posted 15 November 2012 - 07:59 PM

Do you see LabVIEW 2011 in the "LabVIEW versions list" in VIPM 2012?

If not, here is an article on how to fix it: http://support.jki.n...ew-version-list


Yes, 2011 is listed and is the only version listed and installed on my machine. Here is the settings.ini info

[Targets]
Names.<size(s)>="1"
Names 0="LabVIEW"
Versions.<size(s)>="1"
Versions 0="11.0"
Locations.<size(s)>="1"
Locations 0="/C/Program Files (x86)/National Instruments/LabVIEW 2011/LabVIEW.exe"
Ports="<size(s)=1> 3363"
Tested.<size(s)>="1"
Tested 0="FALSE"
Disabled.<size(s)>="1"
Disabled 0="FALSE"
Connection Timeout="120"
Active Target.Name="LabVIEW"
Active Target.Version="11.0"
PingDelay(ms)="-1"
PingTimeout(ms)="60000"
  • 0

#4 Michael Aivaliotis

Michael Aivaliotis
  • JKI Team
  • 501 posts
  • Gender:Male

Posted 16 November 2012 - 05:59 AM

I assume you are getting this message after you browse to the package source folder?


When you do this, VIPM scans your source to determine the LabVIEW version for building. VIPM does this by reading the version info of the VI. It's possible that the VIs are not in LV2011? I would try doing a mass compile on the source folder. In LabVIEW goto Tools>>Advanced>>Mass Compile.

If that doesn't fix the issue then you could zip up your source and submit it to us for testing. We can quickly figure out the problem. You can use our contact form here:
http://support.jki.n...us_requests/new
  • 0
Michael Aivaliotis - VIPM Product Manager

VIPM Idea Exchange <<-- Post your VIPM Feature Requests Here
VIPM Online Documentation
JKI Product Support <<-- For urgent requests, submit a ticket

#5 Bjarne J

Bjarne J
  • Members
  • 6 posts

Posted 30 November 2012 - 07:16 AM

Did you find a solution for this problem.
I got it too :(

regards Bjarne
  • 0

#6 Ashish

Ashish
  • JKI Team
  • 256 posts
  • Gender:Male

Posted 30 November 2012 - 08:16 PM

We have recorded this issue as Case 13848 for consideration in future release of VIPM.

Thank you.
  • 0
Ashish Uttarwar
Product Support Engineer and Certified LabVIEW Developer, JKI

#7 Bjarne J

Bjarne J
  • Members
  • 6 posts

Posted 07 December 2012 - 09:11 AM

We have recorded this issue as Case 13848 for consideration in future release of VIPM.

Thank you.


Hi

Is it a bug in the latest version and in that case, can I dowload an older and get rid of the problem?

Regards
Bjarne
  • 0

#8 Ashish

Ashish
  • JKI Team
  • 256 posts
  • Gender:Male

Posted 10 December 2012 - 09:55 AM

Bjarne,

This capability is not yet available in VIPM.
  • 0
Ashish Uttarwar
Product Support Engineer and Certified LabVIEW Developer, JKI

#9 Michael Aivaliotis

Michael Aivaliotis
  • JKI Team
  • 501 posts
  • Gender:Male

Posted 10 December 2012 - 07:27 PM

This is not a bug in this latest release. This issue has always been there.
  • 1
Michael Aivaliotis - VIPM Product Manager

VIPM Idea Exchange <<-- Post your VIPM Feature Requests Here
VIPM Online Documentation
JKI Product Support <<-- For urgent requests, submit a ticket

#10 Michael Aivaliotis

Michael Aivaliotis
  • JKI Team
  • 501 posts
  • Gender:Male

Posted 11 December 2012 - 07:55 PM

Just to follow up on this.

We had a customer that experienced this issue and submitted their code through our support form. Based on our analysis, we were able to determine the reason for this error in his case. This does not necessarily mean it will fix your issue but this is something to look at:

If you have your code inside an LLB and there is an lvclass inside the LLB, you will get this error. VIPM tries to read that lvclass file and fails because it's inside an LLB and VIPM has a problem with that. Posted Image

As a workaround, remove the lvclass file from the LLB or better convert the LLB to a folder. This should allow you to build the package. We will add a fix in the next release of VIPM for this issue.

If you really need those files in an LLB you can instruct VIPM to do that during build by defining a destination as an LLB (see image):

2012-12-11_1157.png

  • 2
Michael Aivaliotis - VIPM Product Manager

VIPM Idea Exchange <<-- Post your VIPM Feature Requests Here
VIPM Online Documentation
JKI Product Support <<-- For urgent requests, submit a ticket

#11 Phil J

Phil J
  • Members
  • 1 posts

Posted 13 December 2012 - 01:41 AM

I had the exact problem Michael described (lvclass in LLB, etc, etc). Thanks for the workaround, I was able to build successfully with your instructions. But even more, good luck fixing this issue, it would be nice to have that fix. :)
  • 0

#12 Bjarne J

Bjarne J
  • Members
  • 6 posts

Posted 20 December 2012 - 12:20 PM

I had the exact problem Michael described (lvclass in LLB, etc, etc). Thanks for the workaround, I was able to build successfully with your instructions. But even more, good luck fixing this issue, it would be nice to have that fix. :)

It solved my problem too :)

Thank you.
/Bjarne

Edited by Bjarne J, 20 December 2012 - 12:20 PM.

  • 0