LVOOP HAL Deployment for Teststand

[Mwcmwc11]

Hello All:

I have a Labview HAL Project using LVOOP

Class Tree

I have tested this out in TestStand and Labview in project development mode and everything works ok.  However, I am unsure of my next steps for deployment for use in Teststand as I don't want to let Teststand reference the LVProj in order to use the functions.  I tried building each individual lvlib as a Packed Project Libary (PPL) but everything breaks, main issue lies with my Dynamic Dispatch Factory VI doesn't know how to reference my classes.  I tried  using "Get Exported File Path" on the PPLs to pass it to the factory pattern but I end up getting some error with lvclass instance cannot be referenced.

I am unsure at this point if a plug-in architecture is the the right solution, if so, I am unsure how to execute it.   Hope someone can shed some light.

Regards,

Mike

[crossrulz]

I am currently using PPLs for my HAL for use with TestStand.  What I do is make sure I keep a good directory structure.  For instance, all power supply PPLs are in a specific folder.  So then in my "Initialize" of my power supply library, I can do a simple "get folder" and then build the path to the class I actually want to use.

Do note that you will need A LOT of projects in order to properly use PPLs.  I have a project for all of my "base classes" and then a project for each of those types for the children class so that they can properly reference the parent that is to be in a PPL.

[Mwcmwc11]

Hi crossrulz:

Have you had any bugs in the past you with snippet?  I tried using it but would get cases where it "finds" a lvlibp where one doesn't exist.

Thanks!

Mike

[Mwcmwc11]

Figured it out, it was an issue with the project I was calling into.