DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Building DQMH based HAL into NI packets

Hi

 

I have a HAL built up around a class setup (instrument class -> PSU API class -> Specific PSU driver class) which I would like to built into a set of NI packages to be able to install on our distributed test systems. The API class has an accompanying API build on DQMH and a set of TestStand sequences which wraps the DQMH request calls for ease of use by our TestStand developers.

As the systems use different PSUs, I would like to build different packages; one for the Instrument class, one for the PSU API, and one for each of the specific PSU drivers.

 

As LabVIEW automatically adds the classes you inherit from to your packages, it seems that I will have to build the classes into PPLs in order to be able to exclude them from the depending packages.

 

This is causing me some trouble, as the DQMH main.vi won't find the installed PPL version of the class when installed from a package.

 

In my LabVIEW project, the main.vi has no problems finding the PPL version of the class.

 

This is all built in LV 2018 and TestStand 2017, so I can't seem to use NI Package Builder - if that would help me.

 

Any of you clever people in here who have more knowledge than me on how to do my build?

 

Cheers

Martin

0 Kudos
Message 1 of 1
(243 Views)