Conflict Loading Two LLBs

[kevin.key]

Hey,

I'm having a problem calling two separate LLBs from TestStand within the same execution. If I create a sequence file and call one or the other LLBs the execution can run without a problem. If I create a sequence file and call both of the LLBs one of the two LLBs will fail to load and TestSand will give this error message:

I've ensured that all of the VIs created in either project are uniquely named so that they don't conflict when loading. But I'm not aware of what other possible conflicts might exist or a method for diagnosing what is causing the conflict. I know the LLBs both contain some common XNET subVI's and other common subVI's, but they should be the exact same subVI, and I haven't experienced a conflict with other LLBs under similar circumstances.

So, I'm not really sure where to go from here to solve the problem. Any help would be greatly appreciated.

Thanks,

Kevin

[timtamslam · Accepted solution]

Hey Kevin,

It sounds like a namespace problem to me. Even if the VI components are named differently in the LLB, there would likely still be a problem. LLB's will not prevent name collisions.

I would actually recommend changing how you distribute your VI components as .LLB's are a bit dated and have some drawbacks. My recommendation would be to manage your LabVIEW code as project libraries (.lvlib) or packed project libraries. The last post in this thread by user Jervin Justin actually brings up some really good points about this,

http://forums.ni.com/t5/NI-TestStand/What-are-the-advantages-of-using-LabVIEW-projects-in-TestStand/...

Based on this thread (and the information in this white paper on packed project libraries) I would most likely recommend a packed project library approach for a solution to what you're looking for.

Here is some further documentation that you might find interesting:

TestStand Help: LabVIEW Project Libraries: http://zone.ni.com/reference/en-XX/help/370052K-01/tsdeploysystem/infotopics/lvprojectlibrary/

Using LabVIEW with TestStand (page 7-7): http://www.ni.com/pdf/manuals/375070b.pdf

I would honestly try out implementing a packed project library approach for your testing VI's, as opposed to the .LLB's. If this is not feasible for you though, we can try to approach the problem in a different way. Just let me know.

Have a great day!

[kevin.key]

Thanks, I will try switching to packed projects.

[kevin.key]

Switching to packed libraries seemed to solve the problem.

[timtamslam]

Excellent! Thanks for the followup, Kevin.