LLB file problem (Labview 2013)

[std]

I have made labview project that builds a LLB file.

It contains my "test VIs"(auto-populating dir) and all Dependencies(user.lib, vi.lib....)

Building the LLB file goes fine.

But when i try to run the "test VIs" in the LLB file using an .Exe that uses "open VI reference -> invoke node "Run VI" i get a broken arrow and error 2002200....

Opening the "test VIs" in the LLB with Labview, the path for some of the sub VIs do not point to the LLB.  It still points to the original VI (in user.lib, vi.lib....) causing the "test VI" to not be executable . ("test VIs" where all sub VIs points to LLB woks)

what am i doing wrong/how do i fix this?

/J

[std]

Never mind the previous post.

After closing labview and opening the project again trying to figure out the problem i got lot of "conflicts" in project. wasn't there before...

/J

[std]

After some investigation.

Using Projec Explorer building a "Source Distribution" LLB Then calling my "test VIs" in the LLB file using an .Exe that uses

"open VI reference -> invoke node "Run VI" i get a broken arrow and  message  "VI has an error of type 2002200. The full development version of LabVIEW is required to fix problem"

The functions are in "Programming->File I/O-> Configuration file VIs" menu
(Directory C:\Program Files (x86)\National Instruments\LabVIEW 2013\vi.lib\Utility\config.llb\)

Below VIs generates the error
Get Key Names.vi
write key.vi
Remove Key.vi
Remove section.vi
Read key.vi (boolean)
Read key.vi (Double)
Read key.vi (I32)
Read key.vi (path)

But these works in llb
Open config data.vi
Get section names.vi
Read Key.vi (string)
Close config data.vi

I cant find any reason why some works and some dont.
is there someone how knows how to fix this?

/J

[JÞB]

Two things come to mind immediately:

• Why are you using a llb?  they are really obsolete
• Since you are using a llb I'm going to ask what LabVIEW version the original source was written in.  Was it 8.6 or older?  2009 introduced a rewrite of the ini file API and, the two versions (Pre and Post 2009) do not mix and match at all.

[Dennis_Knutson]

It is also a very bad idea to include VIs from vi.lib.

[std]

yes the base code was done with LV 6.0.2.
Updated to from LV 6.0.2 to 2012 to 2013

The Exe is "test sequencer" that reads a txt file with the list of file names(the "test VIs" in the LLB) and calls the "test VIs" in the LLB. This way i could use the same Exe for different test setups.

If you by "ini file API" mean the "configuration file VIs".
These files did not exist in LV 6.0.2. so i had to make my on versions. After updating to LV 2013 i found these new VIs and thought i should start using them instead.
so the VIs have not been updated from pre 2009

what i mean is that VIs in vi.lib, user.lib, instr.lib.... are automaticly included in the list of "Dependencies" in the project when buliding a "Source Distribution" and added to the LLB. I have not added them manually.

/J

[JÞB]

---

so the VIs have not been updated from pre 2009

what i mean is that VIs in vi.lib, user.lib, instr.lib.... are automaticly included in the list of "Dependencies" in the project when buliding a "Source Distribution" and added to the LLB. I have not added them manually.

/J

---

---

Sid, one thing to say...plvlib

llbs are really that obsolete...Dennis gave you some good advice.

[std]

---

@JÞB wrote:

---

so the VIs have not been updated from pre 2009

what i mean is that VIs in vi.lib, user.lib, instr.lib.... are automaticly included in the list of "Dependencies" in the project when buliding a "Source Distribution" and added to the LLB. I have not added them manually.

/J

---

---

Sid, one thing to say...plvlib

llbs are really that obsolete...Dennis gave you some good advice.

---

sorry if i am not being clear.

what i meant with "so the VIs have not been updated from pre 2009"
is that the VIs that do not work is not updated from pre 2009 they are added to the proj using LV 2013.

with plvlib you mean "Packed library" (.lvlibp) right?

/J