NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible to build PPL with NI Package Builder

Solved!
Go to solution

hello

 

I'm trying to use NI Package Builder to build a package to distribute Code for my TestStand Bench.

 

I'm surprise that I can't select to build a lvlibp from the LabVIEW Options window 

 

LabVIEW VI Options - NI

 

Do I miss something ?

Maxime R.  

  CLA - Certified LabVIEW Architect / Architecte LabVIEW Certifié
  CTA - Certified TestStand Architect / Architecte TestStand Certifié

0 Kudos
Message 1 of 3
(667 Views)
Solution
Accepted by topic author MaximeR

Take a look at the TestStand Support page in the NI Package Builder manual which had the below rows outlining the TestStand/LabVIEW support. There are a few rows that are supported and not supported. NI Package Builder only supports projects that already define a packed project library. I assume you are asking about either support for placing loose VIs from a project or on disk automatically into a PPL 

 

Feature Comparison Between TestStand Deployment Utility and Package Builder

Scott_Richardson_0-1689644612850.png

 

Scott Richardson
https://testeract.com
0 Kudos
Message 2 of 3
(646 Views)

Hi Scott,

 

thanks a lot for your quick reply. It can be a good idea to review and explain to customer the global strategy from NI for deploying code.

According to my previous post understanding the way to configure steps and deploy code is not really clear. Using override code module is not a satisfying solution if you don't want to deploy source code (even protected) on your deployment system.

 

NI Package builder provides new features but seems to be more in harmony with overide code module feature to deploy code in PPL.

 

So we can't have better of all word. Working in sources with TestStand and LabVIEW and distribute easily builded PPL for deployment.

Please Stop multiplying tools and make one efficient and coherent.

 

User says at the end, build your own PPL, call it from TestStand and you will be happy. I don't think I will be happy with that. I like to be able to debug and build my labVIEW code when writing TestStand Code then deploy builded code. You don't distribute your LabVIEW application in sources, you provide an executable.

Maxime R.  

  CLA - Certified LabVIEW Architect / Architecte LabVIEW Certifié
  CTA - Certified TestStand Architect / Architecte TestStand Certifié

0 Kudos
Message 3 of 3
(632 Views)