Using LabVIEW Packed Library within TestStand Deployment Tool

I am wondering what could be the interest of generating Packed Library within the TestStand Deployment Tool since the sequences using these VIs will not be able to find the dependant VIs included into the build Packed Library on the deployment target.
Any experience using Packed Library within TestStand Deployment Tool ?
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)

Jiggawax,
Sorry for the confusion,
My question concerns the developement of Custom Step Types.
For example, within a project or as an independant product.
The best practices is to avoid using main module when developing CST in order to preserve evolutivity (main module calling paramters are copied within CST instances and could need prototype updating). I prefer using PostStep (as NI does for its own CST).
Thus, when creating the CST palette, I have to configure the EditStep and the PostStep and define each VI call.
If I want to distribute these VIs through a .lvlibp, then I need to build a .lvlibp very early and use it within my CST palette.
This .lvlibp will be used on deployed benches and may not contain VI diagrams and debug options (best performance).
But during the development of my CSTs, if I need to debug the VIs called when using CST whitin a sequence, and if I don't want to change the called VIs defined in my CST palette, then I need to regenerate this .lvlibp with debug option (different from the deployment .lvlibp) in order to allow debug.
May be it could be interesting that the TestStand deployment tool take into account SubSteps when selecting the Packed Library option. This tool is able to modify sequences, it could be able to change also palette configuration file.
This will allow to have only two levels :
> Source and Debug (VIs)
> Deployment (.lvlibp)
instead of three :
> Source (VIs)
> Debug (.lvlibp with debug option)
> Deployment (.lvlibp)
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)

Similar Messages

Using LabVIEW OOP Objects with TestStand 2010

I need to use labview classes in Teststand 2010. I am not able to pass reference between Labview and Teststand.

Or leave it in Labview and use an action engine.
http://forums.ni.com/t5/LabVIEW/Community-Nugget-4-08-2007-Action-Engines/m-p/503801?view=by_date_as...
That's what I have done.
Regards
Ray Farmer

Use of Build Specifications for TestStand deployment Target

Hi everyone,
I currently use NI Internet Toolkit in one of my VI to build a code module for TestStand.
The matter is that de deployment target doesn't have the NI Internet Toolkit.
So I would like to build the VI in such a way the deployment target wouldn't need the Toolkit to use the VI.
Does anyone knows a way to that ?
Thanks to all...
Solved!
Go to Solution.

I got some matter with my outputs types (string array):
- It generates an error while creating the dll with .NET interop.
- Couldn't manage with share library .dll cause of array bounds couldn't be specified (array of array of char).
Thus I just change my data type to be of simple types, and it working quite well...
Thanks to Mr Dennis Knutson !

How to build a TestStand 2012 workspace ( insert a project / insert a folder) programmatically using LabVIEW 2012 and the TestStand API.

Hi everybody!
I am just trying to find out how to create a TestStand workspace … in LabVIEW using the TestStand API.
To create a new workspace was quite easy. Unfortunately I am not successful to insert a new or existing project to the workspace.
Furthermore I have to insert a folder from disk to the new or existing project in the way that I can use an absolute path for the directory …
Maybe someone had already solved this problem, in any case I am thankful for any hint.
Greetings from Germany,
Norbert

Have you find out how to add a folder to a project? I'm looking for this to... I tried WorkspaceObject.NewFolder[Name]whitout success...
For creating Workspace and project see the newer resolved thread I created.
Martin

Using ASA as an Anyconnect profile deployment tool

I have a requirement to use an ASR router as a IKEv2 headend for Anyconnect clients. For ease of deployment, I want to use the ASA firewall to enable users (multiple OS - Win/Mac/Linux) to download their respective Anyconnect clients as well as the profile needed to connect to the ASR. Note that the ASA is only used for AC and AC profile downloads, it takes no part in any VPN termination. Users will just point their browser to the ASA firewall web page and download both the AC client and the profile, then they will launch the AC and connect to the ASR router.
My question is, can this be done?
Thank you!

Yes, I want to deploy the software independant of any ASA VPN connection. From the Admin guide:
When deployed from the ASA, remote users make an initial SSL connection to the ASA. In their browser, they enter the IP address or DNS name of an ASA configured to accept clientless SSL VPN connections. The ASA presents a login screen in the browser window, and if the user satisfies the login and authentication, downloads the client that matches their computer's operating system. After downloading, the client installs and configures itself and establishes an IPsec (IKEv2) or SSL connection to the ASA.
On the last sentence, I need the client to establish an IPSEC connection to the ASR, not the ASA. Just wanted to confirm that this can be done.
Thank you

TestStand Deployment build error

Hi,
I am using TestStand deployment tool for the first time. I am getting an error and I am not able to fix it. It is a reference to Query Available Printer.vi (which I don't use in my projet, unless one of the instrument driver is using it). I checked the file and it is not broken. If I just perform the analysis, everything is fine though. It is only when I build that I run into it.
I am not including any of the TestStand or System32 files in the build. I am not including User Interfaces file either. Finally, I don't install TestStand Engine or any other Drivers or Components.
Thanks
Alexandre Boyer
Here is the deployment log file :
Starting Log.
Starting Analysis
Starting to process workspace file
Done processing workspace file
Finished Analysis
Building...
1:46 PM
An installer was not created due to an error
The build is finished
1:50 PM
Aborted
Warning: You may need to add any sequence file(s) referenced by the following expression(s):
RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'TestComponent', sequence file 'C:\Projets\Opnext\OTM-440 Manufacturing Test Stations\Trunk\Technical\D - Execution\TestStand 4.0\Components\User\Models\TestStandModels\ProligentSequentialModel.seq'
RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Routing Entry Point', sequence file 'C:\Projets\Opnext\OTM-440 Manufacturing Test Stations\Trunk\Technical\D - Execution\TestStand 4.0\Components\User\Models\TestStandModels\ProligentSequentialModel.seq'
RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Test UUTs', sequence file 'C:\Projets\Opnext\OTM-440 Manufacturing Test Stations\Trunk\Technical\D - Execution\TestStand 4.0\Components\User\Models\TestStandModels\ProligentSequentialModel.seq'
Locals.ModelPath in step 'Call PostUUT of the Process Model', sequence 'PostUUT', sequence file 'C:\Projets\Opnext\OTM-440 Manufacturing Test Stations\Trunk\Technical\D - Execution\TestStand 4.0\Components\User\Callbacks\Station\StationCallbacks.seq'
Locals.ModelPath in step 'Call PreUUT of the Process Model', sequence 'PreUUT', sequence file 'C:\Projets\Opnext\OTM-440 Manufacturing Test Stations\Trunk\Technical\D - Execution\TestStand 4.0\Components\User\Callbacks\Station\StationCallbacks.seq'
Locals.ModelPath in step 'Call PostUUT of the Process Model', sequence 'PostUUT', sequence file 'C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.1.1\Components\Callbacks\Station\StationCallbacks.seq'
Locals.ModelPath in step 'Call PreUUT of the Process Model', sequence 'PreUUT', sequence file 'C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.1.1\Components\Callbacks\Station\StationCallbacks.seq'
Warning: The following dependencies were detected but not selected; you must decide if they should be included:
C:\WINDOWS\system32\kernel32.dll
C:\WINDOWS\system32\user32.dll
C:\WINDOWS\system32\advapi32.dll
C:\WINDOWS\system32\ole32.dll
C:\WINDOWS\system32\version.dll
C:\WINDOWS\system32\SHLWAPI.dll
C:\WINDOWS\system32\msvcrt.dll
C:\WINDOWS\system32\mscoree.dll
C:\WINDOWS\system32\KERNEL32.dll
C:\WINDOWS\system32\ntdll.dll
C:\WINDOWS\system32\USER32.dll
C:\WINDOWS\system32\GDI32.dll
C:\WINDOWS\system32\ADVAPI32.dll
C:\WINDOWS\system32\RPCRT4.dll
C:\WINDOWS\system32\Secur32.dll
Error: Unable to find all subVIs from saved VIs, either a subVI is missing or the VI is not saved under the current LabVIEW version.
The missing file path is:C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\printing\Query Available Printers.vi
while Processing VIs...
+++++++++++++++++++++++++++++++++++++++

Do you have the sequence files in your project that it lists?
C:\Projets\Opnext\OTM-440 Manufacturing Test
Stations\Trunk\Technical\D - Execution\TestStand
4.0\Components\User\Models\TestStandModels\ProligentSequentialModel.seq
I recommend going over chapter 14 of the TestStand reference manual with a clean sequence and attempting to deploy to a clean computer. Once you can get that to work, deploying with your actual code is much easier.
http://digital.ni.com/manuals.nsf/websearch/D4A50986EECCF7218625757C00697617
Richard S -- National Instruments --Applications Engineer -- Data Acquisition with TestStand

Using labview global in test stand sequence steps

If I have to pass data between different steps ( only labview vis) within same Main sequence, is it right using LabVIEW globals, rather than TestStand globals?
in one step, I will be writing data to the Global.
In a later step, I will be reading the global to access that data.
Example sequence:
I am more comfortable with using Labview globals than Teststand variables. Labview is the only adapter in my sequence.

If it is just within one sequence, then I would use the TestStand variables. The reason is because you are limiting your possible reuse of those VIs by using the global. If you pass in the value, you have a better chance of being able to reuse the VI.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Packed library and SQL Toolkit

Hi
I have labview development studio and I have made some test software that runs a test and posts the results to a database.
I have built the functions of the test in to a packed library
Another company will be using the packed library to test some pcb's for us. The problem is that they do not have the database module in their labview and so the database section of the code does not work.
Is there a run time program for the SQL toolkit I can give them?
Solved!
Go to Solution.

No, but you can replace them with these drivers and not have to worry about toolkits. Be sure to read the discussion too - it will give you other reasons why you are better off without the DCT. The download link for a current version of LV is on the last page of the discussion.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Having difficulty creating MNU for packed library

Hello All,
I am using a packed library and I am attempting to create a .mnu for it.
I want to be able to drop my packed library into the user.lib or vi.lib folder so my coworkers and I can use common VI's.
Every time I create the .mnu and add it to my packed library, my links get broken.
I can create a .mnu using the Edit Palette Set.
I can add the .mnu to my packed library.
I can import the packed library .mnu using the Edit Pallete Set. But at this time, any VI's inside that menu are now just broken links.
I have tried multiple processes. What I have observed is I cannot import VI's from the library. I have to import them prior to being packed. So I copy all my VI's to my user.lib folder.
However, the path does not match the packed library.
How do I make a .mnu for a Packed Library with subdirectories and no broken links?
I need to be able to put it in any folder with the links of the packed library not being broken.
I would like to use subdirectories for easy navigation.
Do I need to put the VI's into a folder named the same file name as my packed library to preserve the relative paths?
I have searched the forums and the help and I am missing something. Perhaps I am doing things out of order.
Any advice would be helpful.

I sort of answered my own question. Here is what I did, for those who have similar issues.
1.) Opened my packed library project.
2.) Selected the top level project item.
3.) When to tools -> advanced -> edit palette set. (This is why I selected the top level item. for me, this option does nothing unless I select a VI or some sort of project in the file tree first. I can also do it inside a VI with no problems.)
4.) Under the user libraries, I created a new subpalette.
5.) Under new subpalette, I selected the fourth option (link directly to directory)
6.) I browse to the directory where I stored my VI's in the packed library. I DID Not move them to the user.lib folder.
7.) Once the import was completed, the VI's appeared in my control panel under user libraries. I also customized my Icons and directory names at this point.
8.) A dir.mnu file is created as part of the import inside the folder my VI's are contained in.
9.) I right click on the top level library in the project viewer, and select properties. I set the dir.mnu file as the default .mnu
10.) I build the library
11.) I copy my packed library into the user.lib folder.
12.) I once again go to edit palette set, I remove the palette created in step 5.
13.) I create a new palette, this time choosing option 5 (link to palette file in a project library). The packed library is now part of my control panel. My Icons and directories are preserved.
My project structure is to create a folder with the packed library project. I then have a subfolder called VI. Inside that volder I store all of my VI's that are part of the packed library project.
This seems to work. But I need to do more testing. I used basic structures. I have not done one yet with a more elaborate scheme such as sub palettes.

I want to make a web page using labview.

I want to make a web page using labview. I have the internet tool kit. Where do I start. Till now all I have used labview is for industrial I/O and mmi. I have used various TCP UDP comms for network purposes, but I haven't ever done anything with Web page design.

The internet toolkit has some functions for generating and manipulating HTML, but it isn't really intended as a Web page authoring tool. I personally wouldn't use it for such a purpose, and I've done a good bit of Web programming in various different environments, including LabVIEW.
The true power of the internet toolkit lies in its ability to create LabVIEW VIs to handle CGI requests, the way that perl or PHP might be used in more traditional Web development. In the old days, this was really the only way to provide Web interactivity with LabVIEW on the back end. Here is a document that outlines how to start up the toolkit's Web server and check out the CGI examples that ship with LabVIEW. This is the best jumping-off point for creating your own pages, if you are planning to use the CGI functionality in the internet toolkit. Just examine how the HTML pages and the CGI VIs in the examples work together and begin to try out your own VIs.
Since LabVIEW 6i, LabVIEW has shipped with Remote Panel functionality that allows you to publish any LabVIEW VI in a Web browser without the burden of creating special CGI functionality. Furthermore, users can fully interact with the VI--buttons, graphs, string controls, etc. That's really a better solution if you want to make VIs available via the Web and aren't so much interested in CGI/transactional behavior. Check this out by choosing Tools >> Web Publishing Tool from LabVIEW.
I hope this info gives you some ideas about starting points for Web functionality in LabVIEW. Please follow up if you have more specific questions.
Best Regards,
John

Storing labview TCP connection in TestStand object reference

I have a LabVIEW routine (GetFileGlobal) that uses the TestStand SequenceContext->FileGlobals to do a lookupString and determine the GetType if the string 'Exists'. I have a LabVIEW case statement that captures values of '1' for GetValString, '2' for GetValBoolean, and '3' for GetValNumber. I have a LabVIEW TCP connection that gets opened that we need to store in TestStand in a FileGlobal. What type is necessary in TestStand to store a TCP Conn? AND, given the (tbd) type in TestStand, what is the value I would need in my case statement to capture this new (tbd) type coming out of the GetType?

I've asked this on another thread, but I'm just not understanding the exact implementation. In TestStand, the LabVIEW IO Controls type is made up of a DeviceName and a SessionNumber, but in LabVIEW I have a TCP Network Connection. I have routines that let me Get/Set TestStand File Globals if they are Boolean, String, or Number. Now, if I use LabVIEW IO Controls in TestStand, what is the exact way I stuff a TCP Network Connection in there. I've attached a VI that I use to GET the FileGlobal value from TS. I need to grow it to allow me to get the TCP connection (i.e. LabVIEW IO Controls), but I'm not sure how to do that. The types are messing me up. Also, I'm not sure what the 'GetType' wants to see
Attachments:
FTW_ATE_UTIL_GetFileGlobal.vi ‏25 KB

Labview External library Call

Hello,
I am using CAN board provided by ESD which supports LabVIEW 6. I am able to communicate with the board using the Call Library Function in LabView using ntcan.dll. I have also purchased canopen library from ESD itself. Now I want is to use those canopen functions of ESD in LabView. I got .lib files and header files for CANopen. So how can I include these additional lib files or header files, or Is there any other solution.

lib files and header file are for text based languages, such as C, C++, & C#.
You should have a dll file come with lib files. Usually with the same file name, only the extension is dll, instead of lib.
Use LabVIEW Call Library Function to call the functions in the dll. You can find the parameters for the function in the header file.
LabVIEW Call Library Function doesn't support complicated data structures (such as cluster of pointer to another cluster) and call back functions.
In this case, you have to use C/C++ to create a wrapper dll.
George Zou
http://www.geocities.com/gzou999/
George Zou
http://webspace.webring.com/people/og/gtoolbox

TestStand Deployment Error Code 1055 when using LabVIEW Storage VIs

After a couple of days of playing with the TestStand Deployment. I final tracked down the VI that was causing this Error.
It was using thethe LabVIEW Storage VIs to save data to a TDM file.
My work around at the moment is to use a Wrapper VI and call this VI by reference.
That way the TestStand Deployment can't detect the Storage VIs.
I'm using LabVIEW 8.6.1 and TestStand 4.1.1 does anyone know if this issue has been address in TestStand 4.2?
Looks like the upgrade might be worth it.
Simon Holman
Software Engineer
Certified LabVIEW Developer
Certified TestStand Developer
measX GmbH & Co. KG.
http://www.measx.com
Solved!
Go to Solution.

Hi Simon,
I tested your sequence file in TestStand 4.2 and I didn't get any error! Which version of TestStand do you have? Can you post a screenshot of the complete internal error pop up?
Usually internal errors can be eliminated with the Clean Reinstall Procedure.doc, where you will remove all NI software and all references to NI software from your computer to start over with a fresh installation!
I hope these informations help you!
Best regards
Suse
Certified LabVIEW Developer (CLD)
Attachments:
Clean Reinstall Procedure.doc ‏32 KB

Using LabVIEW RTE vs. LabVIEW ActiveX Automation Server (TestStand LVRTS) for a TestStand Deployment and experienceing Unabel to Launch LabVIEW.Application ActiveX Automation Server Error 18001

I am developing in TestStand 4.2.1 and LabVIEW 2009, I have accomplished the following:
1. Deployment package is built and deployed on PC
2. PC has activated TestStand Deployment License
3. LabVIEW 2009 RTE was selected as the adapter for the sequence and thus I believe the deployed testexec.ini contains this.
I am experiencing the following error: "see attachment".
Is the LabVIEW RTE the right selection?
Is there something I may have missed in building the deployment?
Do I need to register the ActiveX server.
THere seems to be conflicing solutions based on Version of TestStand and LabVIEW!!
Thanks!!
Attachments:
TS_LV ActiveX Error.doc ‏77 KB

Howdy mobiux,
Please consider KnowledgeBase 4V58058Z: -18001 Errors in TestStand. If you're using Vista or Windows 7, then this may apply as well. You might also consider ensuring you have the proper LV version active in the TS Adapter Options.
Warm regards,
pBerg

Deployment of TestStand 3.5 sequences using LabVIEW 8.0 vi's

I have LabVIEW 8.0 and TestStand 3.5. I currently haev this installed on the PC running the test sequences for our automated test programs. I've read the manuals and it appears that I can create a deployment to run the test sequences on another PC. Do I need an additional license for this? Is it the TS deployment license, or do I need a LV deployment license also?
I attempt to create a deployment package on the PC with the development license. I checked the box that indicated to thave the TestStand runtime system included, which (I believe) included the LabVIEW 8.0 runtime. However, when I installed this on a target machine, the sequences and vi's don't seem to have any executable associated with them. Is this because I haven't activated a deployment license on this machine? I had thought that there was a 7 day demo license in effect automatically.
Thanks, Blair

For some reason when I go to deploy a TestStand system I don't have the option of selecting an operator interface.
I have attached the options shown to this message.
Do I have the wrong license for TestStand? I'm stumped. My license indicates that I have a development system.
Thanks,
Blair
Attachments:
TS Engine Options.rtf ‏4542 KB

Using LabVIEW Packed Library within TestStand Deployment Tool

Similar Messages

Maybe you are looking for