Licence TestStand inactive

Hi,
The TestStand licence I have become inactive and I don't know why. I've noticed that the computer ID in the licence manager sometimes changes, and I suppose it's the reason of my problem; so I can't open any TestStand's files anymore.
I have to take another licence activation code on the Internet to be able to use my software again. And few weeks later, the computer ID has changed another time..
What the computer ID is based on? I asked the software department of my office, they don't knowy this kind of number.
Thanks for your help.
Best regards
J. Fournier

The computer ID takes some system components into account. Those components are either the MAC address of your network device or the serial number of your harddrive.
So if you change for instance the network device, there is a "good" chance that the computer ID changes as well.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Similar Messages

Code could not be generated because an external component or driver is missing

Greetings All,
     I've using Labview for a little over a year and I have an interesting situation with regards to Labview that I came across today. When I left off yesterday (01/11/12) my TestStand sequence was compiling fine. Today for some reason the compiler told me that one of the VI was broken or missing a sub vi. When I made my way through all the sub vi's in the vi that seemed to be a problem I came across "Code could not be generated because an external component or driver is missing".
     The problem started on the computer (NI PXI-8101 with WinXP and Labview 2010) located in a PXI-1044 that is in my Test Stand.  I have a complete backup on my laptop and my desktop computer which both compiling successfully with no errors. I tried installing the directory on another PXI-8101 and got a different set of results.  The first PXI-8101 gave 100+ errors in TestStand pointing to one of my vi's and the other PXI-8101 reported only one (1) error. The vi is basically using DAQmx vi's to create a "write to one line" action. I'm kind of stumped as to why it works on the laptop/desktop and not the PXI computers. All four computer are WinXP professional and Labview 2010. I saw somethings through google search engine but nothing conclusive. I'm hoping that someone can give me an explaination as to what is causing the error as described. Even if I copy over the directory it doesn't fix the problem. Thank you in advance for an information you provide with this rather interesting problem that I've encountered. If you require addition information let me know.
Regards,
Scott
Solved!
Go to Solution.

Greetings Beau,
     Thank you for the reply.
     I loaded the offending VI into Labview (2010) with TestStand inactive. Of course this was after I completely shutdown the computer and re-booted to ensure that nothing was resident in memory. I've included a couple of the error list boxes in this post.
     It comes down to a subvi that is two (2) subvi's deep. All these vi's are doing is commanding a write or read to and from the PXI-6509. When I check the VI at the level that has no broken run arrows (named below), nothing in the block diagram looks out of place as it should since these were installed by Labview installation. The vi that uses these vi's looks total normal and its block diagram doesn't have anything out of the ordinary yet the run arrow is broken. The odd part of this is that the top of the window that states the filename of the vi has an astrex at the end of the filename, even though nothing has changed in that vi.
Here is a list of the deepest level that has no broken run arrow:
DAQmx Create Channel (DI-Digital Input).vi
DAQmx Start Task.vi
DAQMX Read (Digital Bool 1Line 1Point).vi
DAQmx Clear Task.vi
DAQmx Create Channel (DO-Digital Output).vi
DAQmx Write (Digital U8 1Chan 1Samp).vi
     I guess the real question is what is the error message ("External component or driver missing") really telling me if all of the vi's look right. I appreciate any information you can send my way that will give me a better understanding of where this error is coming from. The program I developed had been running without a hitch for a month an all of sudden crash.
Thank you for your time in this matter.
Scott
Attachments:
Write to one port broken VI error list.JPG ‏47 KB
Readfrom one line broken VI error list.JPG ‏46 KB
Broken_VI_Error_Screen.JPG ‏56 KB

Inactivity timeout for TestStand user credentials

Hello all,
I'm curious if anyone has done any work on inactivity timeouts for TestStand user credentials; I am looking for some solution that will allow windows to lock, but if i have a test running and I walk away, my credentials will lock after the test has finished. Anyone have any ideas on where I can start some research into this?
-Bill
John 3:16

Hi Bill,
In order to programmatically log out of TestStand, you first have to programmatically shut down the TestStand Engine. To execute the FrontEnd Callback to log out of TestStand, you will have to create a Property Object to pass to the LoginLogout Callback.
Locals.PropObj = RunState.Engine.NewPropertyObject(PropValType_Container,False,"",0),
Locals.PropObj.AsPropertyObject.SetValBoolean ("logoutOnly", PropOption_InsertIfMissing, True),
Locals.PropObj.AsPropertyObject.SetValBoolean ("isInitialLogin", PropOption_InsertIfMissing, False),
RunState.Engine.CallFrontEndCallbackEx("LoginLogout",Locals.PropObj.AsPropertyObject,ConflictHandler_Prompt,0)
You will also have to develop a code module to poll for UI messages after calling the first Shutdown sequence.
Are you intending to run a test, walk away, and come back hours later to a completed test and TestStand idle? Or are you wanting to abort an abandoned test and reset to the initial login screen? This is going to be a fairly complex implementation, so I'm trying to make sure of your intentions.
Regards,
Alexandra
National Instruments
Applications Engineer

Deciding whether TestStand is the right solution for my company

I'm working at a growing company and we recently started a push in our Test group to try and standardize our future development as much as possible to allow as much re-use of code as possible. I don't want to say exactly what it is we make for confidentiality reasons, but let's just say that 90% of what we make is the same basic type of product, but it comes in literally hundreds of models ranging in size from about the size of a dime to the size of a small washing machine. We're considering switching to TestStand on all new stations and on all updates of previous stations to assist in rapid development with increased efficiency.
Over the years we've made about 20 or so test stations as new versions of our product came out, each able to fit products of a different size and with different test requirements, but because our main products are all so similar to each other, there's only a pool of about 6 different types of tests we need to run, with some products needing only one of those tests and others needing all 6, and plenty in the 2-5 range. The size differences among different products also mean we have a large amount of different power supplies, and for various other reasons the measurement devices for the test stations aren't terribly standardized as well.
Step 1 was that we standardized the database we used to store all of the test data. We now have one database that can store data from all of our test stations in the same way. A few of the old stations had to have some creative workarounds done (i.e. instead of rewriting their current test program, write something that takes their old output format and converts it to the new database format, then upload it), but this step is 100% complete.
Step 2 was to abstract out the most common pieces of hardware, so we have started basically putting the IVI types in a LVOOP wrapper. Now instead of being limited to interchangability among IVI devices we can also swap in any of the other assorted devices we've accumulated over the years, many of which don't have IVI drivers and even a few that don't follow SCPI standards, as this is a great use of inheritance and overrides. We're also implementing a few device types that don't have IVI classes. This effort is already well underway and we're OK here.
Step 3 is where we're at now. As we standardized on hardware interfacing, we also figured it would be a good idea to attempt to effectively write each of the 6 or so tests one last time each with very flexible setup parameters as inputs, using the abstracted hardware classes so that it wouldn't matter which hardware we had, so that all the tests would run the same way. So we started looking at solutions to some form of sequence management, and we came up with a couple of possibilities for homegrown versions but after debating those for a while we started to ask ourselves, "Are we just re-inventing TestStand here?"
We use TestStand on a few stations here already so we had licences for development, but the stations we use it on at the moment fall into the 10% of outliers that we have and are somewhat non-standard. So none of the 6-ish usual tests were used on them and they're for a very different product type, so we never tried to use them with our standardized database. They also were all made before I came on board here, so I don't have much experience with TestStand myself, and I've run into some roadblocks when trying to come up with a framework for how to integrate our standard database and our standard instrument LVOOP classes into a TestStand environment that meets our current and future test requirements.
The first roadblock is that our database standardization and TestStand's built-in reporting don't mesh at all. Right now, all of our test stations use the same "mega-cluster" to store their data in, which is a type-def cluster of all the things our products could ever be tested for on any of our stations. We pass it to a common database write function that writes everything that has changed from the default values (NaN and blank strings\arrays) and ignores the rest, so we don't fill the database with zeroes for the tests we don't do. I do want to emphasize how big this cluster got in order to have all of the potential save values we might ever need in it. It is a cluster of 13 other clusters, the largest of which has 10 items in it, and one of those is a 1-D array of another cluster with 19 elements in it, and one of those elements is another 1-d array with a cluster of 24 units in it. If all of the controls in the mega-cluster are shown on the front panel at once, I can't fit them on 2 full-size 1080p screens at the same time. The context help for the main cluster is 5 screen heights tall just for the listing of all of the elements.
So I really can't see this being integrated with the built-in TestStand reporting system. Additionally, the "Type" system in TestStand appears to be unhelpful when attempting to pass this cluster between steps, and even worse when trying to pass it between sequences. When I add the mega-cluster to it, it also creates over 30 other types, one for each of the other clusters contained inside of it. Within LabVIEW alone this is pretty easy to manage, as we just have a centralized repository of typedefs in source control that gets checked out to a common directory on each computer, as we do minor changes to acommodate new products a few times a year. However, on TestStand, I can't find a method that's the equivalent for just storing a bunch of .ctl files in the same shared directory like we do with LabVIEW. I see that they can be stored in certain INI files or in sequence files. The INI files appear to all be station-specific, and since all of our 20ish test stations have different hardware and capabilities, we can't just synchronize those files. And if I want to pass the mega-cluster type between sequence files that call sub-sequence files, every one of those files will need to be manually updated to get their types to match... and we'lll be needing at least 200 sequence files when we're done, at a guess. Unless there's some method I'm missing here, I don't see how to use TestStand to move this data around. We could use something like just passing it by reference, but then if we do that I don't actually see much of a benefit here of using TestStand instead of just pure LabVIEW as two of the things that TestStand is supposed to handle (reporting steps as pass/fail against limits and reporting and logging the results afterwards). Plus then we have the additional burder of making sure the module holding the reference in LabVIEW doesn't unload before we're done using it.
Is there some better way of handling massively complex types in TestStand that I am not seeing?
There may be more that I'm not seeing yet, but if there isn't a way to handle these massively complex types in TestStand, all we'd be getting out of it is a slightly easier method of managing sequencing than we have now, which I don't see as being worth the investment in time and licenses it would take.
I'd be grateful for any feedback. Thanks!

Considering you already seem to be leveraging LabVIEW heavily and before jumping into TestStand I would look at the PTP Sequencer. This seems to be a cutdown version of TesStand but inside LabVIEW and is a simple install from the LabVIEW Tools network using VIPM.
If you are happy to look at alternative representations then maybe check out NI's StateChart Module or the Open StateChart by Vogel (available as an install from VIPM).
The advantages of any of the above is they will be alot cheaper than TestStand and the required run time licences if you don't require all the power of TestStand (extensible everything).

PLC application validation using OPC and teststand

Hello
I want to test a PLC application using teststand as script generator. My idea is to use TestStand to generate testcases and verify answer (read status variables, tags)
from the PLC to confirm its code meet requirements.
So question is, can TestStand read ad write PLC tag variables, using an OPC server ?
Did anybody else use this strategy before ?
Pierre Danis

Pierre,
For your information, there is a new TestStand Add-on "OPC DA Connect" which adds a StepType Palette dedicated to OPC Data Access.
You can configure each step by browsing the OPC servers on your network and browsing variables within these servers.
This toolkit has free deployment licence.
Hoping this helps.
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)

TestStand 3.1/3.5 under WIndows 7

Anyone has solved or patched the annoying problem of the sequenze menu ring of TS 31 and TS 35 under Window 7 ? I'm referring to the problem in scrolling, when you expand the menu only one row is deiplayed and you have to scroll on one row !!! I'd like to explain to National Instrument that many customer has PC with windows 7 but they have to use old version of TS (like 3.1 or 3.5) and this is a very big problem in developing apps.
Thank you to all.
Massimo Ponte

Hey Massimo,
I agree with you that it could be difficult to plan a system upgrades on several hundreds of machines. The upgrade/maintenance for a software framework is a very critical task for a company. However it doesn't explain how your company upgraded your Operative Systems without worrying about the Development System's compatibility. Anyway, you can easily workaround your issue by installing a Virtual Machine containing an XP OS and TestStand 3.1/3.5. Refer to following useful links:
WMware - Support and Licence
Have a nice day!
Bye
Matteo C. - Test Engineer

Data access in Teststand/LabVIEW through OPC connection

We are using TestStand 2.0 and LabVIEW6.2 and following problem occurs when accessing the datas from UUT through OPC.
For the first UUT i get the measurement datas but starting the next UUT causes a system hang up. The corresponding LabVIEW VI stops at the connect to the OPC Server it doesn't read the selected item. Only with LabVIEW there is no problem launching OPC data access for multiple times. Does anyone have expierence with this configuration: TestStand-LabVIEW-OPC?

For your information, there is a new TestStand Add-on "OPC DA Connect" which adds a StepType Palette dedicated to OPC Data Access.
You can configure each step by browsing the OPC servers on your network and browsing variables within these servers.
This toolkit has free deployment licence.
Hoping this helps.
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)

Disconnection leaves inactive sessions

Hi I am new to this forum, I have looked but cannot find any reference to my problem, apologies if it has been discussed earlier.
When in SQLDev (EA2 and also earlier versions) on windows2000prof v5 sp4, when I disconnect from a connection inactive sessions are still on the DB (9i r2), this for reasons I won't go into here causes us problems. We have to save all our work and exit sqldev then restart to ensure connections disappear.
I assume this is so connections are reused if you reconnect, and on the face of it seems reasonable, however, it is a problem for us.
Is there some config I can do to stop this behaviour either by connection or for all connections ?
Help appreciated.
btw really like this product, EA2 now has support for AQ's and Materialised views which we use ( we have now decided not to renew TOAD licences because sqldev seems to be mature enough for our purposes now - and is cheaper :-) )
Message was edited by:
CharlieColson

Many thanks for your reply.
I am not doing anything special, it must be designed behaviour because as soon as I exit sqldev the sessions are gone :-
open a connection
run some sql in a worksheet, close worksheet
disconnect from the connection using the connection tree
inactive sessions remain on the database, one for connection and one for insight.
I was hoping that there is some java/config/connection setting I could use, it dosen't happen from TOAD so I can't think it is server behaviour ( and neither does my DBA ).
Cheers

Erreur -19050 lors de la compilation avec Deployment Utility/TestStand

Bonjour à tous,
Je souhaite créer un exécutable incluant des séquences TestStand avec des VIs Labview. Je suis tombé sur l'outil Deployment Utility qui a l'air de correspondre à ce que je souhaite faire.
J'ai donc essayer de construire un installateur avec cet outils qui inclut mes séquences et mes Vis etc..
Le problème arrive lors de la construction, une erreur apparait mais ne me donne pas plus de détails que ceci:
"error -19050: The bitness of LabVIEW does not match the bitness of the deployment utility."
J'ai essayé de chercher d'où vient le problème mais je suis au point mort la, je ne sais pas du tout où je dois regarder pour régler ce problème.
J'utilise les versions 2014 de LabVIEW et TestStand. Mes séquences fonctionnent correctement.
Merci de votre aide
Mehdi

Bonjour,
Je pense que tu risques d'avoir queslques difficultés pour exécuter ton application de test en distribution. Pour la distribution, il te faut effectivement au moins une licence Run-Time de TestStand et je pense que tu veux te passer de la licence LabVIEW.
Si j'ai bien compris, tu veux une distribution avec un installer de ton application TestStand. Tu as des séquences en TS2014 64 bits et tes codes modules LabVIEW sont en LabVIEW 32 bits pour le développement. J'imagine que ton adapter LabVIEW est configuré pour fonctionner avec LabVIEW en développement.
Première étape, as tu essayé de passer ton adapter LabVIEW en run-time ? A mon avis,ca ne va pas fonctionner d'parès cette KB .
Il faudrait que tes modules LabVIEW soient en LabVIEW 64 bits.
Le Run-Time TestStand n'est pas l'éditeur de Séquence. TestStand est un serveur ActiveX, et si tu as créé une interface opérateur spécifique, tu n'as pas besoin d'avoir l'éditrru de séquence pour exécuter ton application. SI tu veux les éditer ou l'exécuter depuis la même interface que celle que tu as en développement, il faut installer au moins le séquence Editor qui est disponible dans les "Optional TestStand Features..." lorsque tu coches Install testStand Run-Time. Pour l'acitvation de la licence, au pire, lors du premier lancement de ton application, il proposera de l'activer. Pense a ajouter le run-Time LabVIEW dans ton installeur si tu veux que ca installe tout d'un seul coup.
Mais je pense qu'avant de réussir tout ca, il faudrait vraiment vérifier l'exécution en Run-Time LabVIEW au niveau de l'adapter.
Petite question de curiosité, pourquoi tu chsoisis d'utiliser TestStand 64 bits ?
Cordialement

TestStand Deployment Query

Hi,
I have TestStand 3.0 development licence and once my development is finished i need to deploy my software to client machine. Do i need to purchase TestStand Base Deployment Utility,TestStand Debug Deployment Utility or can i can deploy by suing the option present in Tools->Deploy TestStand System.
If i need to buy Base or Debug Deployment utility then what is the purpose of this option Tools->Deploy TestStand System ??
Thanks in advance,
-Anil
Anil-B'lore

Hi Anil,
The Deploy TestStand System is very good at organizing every code module and component that you need for a deployed system. It will find all of your VIs (if you use LabVIEW), and all of your other code modules. It will create a single installer that will include the TestStand Engine. However, you will still need to a license to run TestStand on the deployment machine. So you will use both the Tools >> Deploy TestStand System along with purchasing a deployment license for using TestStand on another machine.
Allen P.
NI

Any way to test teststand deployment without base deployment engine?

Hello,
I am currently working on a teststand/labview program for the manufactuerer for my company. I would like to test the deployment files I have created but we do not have a base deployment engine license. Is there a way to get around this for testing purposes? I would like to be able to deploy this to a PC without the teststand/labview development system since that is what I will be deploying it to eventually.

Once you have created you deployment image you can deploy this on any system. Obvious you will not beable to test this if you haven't
a) already deployed the teststand runtime engine and user interface
b) and also the LV RTE.
But you can check that files should go to the desired location and that you have all the expected files.
But also you should a one deployment licence with the Developement TestStand System you brought.
Regards
Ray Farmer

What do you need to deploy the Teststand Engine?

I just received TestStand 3.5 (semi familiar with 2.1) and am trying
out the "Common Deployment Scenarios" described in the TestStand
Reference Manual. Unfortunatly I am not completely seing what is
described in the manual. Specificaly, the "Deploying the
TestStand Engine" and "Distributing Tests From a Workspace" contain
steps that instruct to check the option to add an operator interface in
the "TestStand Engine Options" dialog box.
Why am I not seing this option? Did something change in 3.5 that
didn't get change in the manual? Am I missing a licence?

Not unless you are using TestStand wich I don't think you are. From this post and your other post on the forum it looks like you are just working with LabVIEW at this time. TestStand is a seperate appliation for quickly creating sequences for automated test.
Your best bet would be to keep posting in the LabVIEW forum and I would recomend starting a new post of your own too. Replying to old post with new questions get things side tracked.

How to find licence number to activate software ?

I have just bought the Adobe creative Cloud for enterprise.
I had download the creative cloud and now each software is asking for a licence number but I can't find it.
And I have no acces to Adobe Licensing website to get one.
Can you help me?
Thanks.

Hi Berengere,
Welcome on the Adobe Forums!
There is no serial number needed to activate the Creative Cloud, the Adobe ID will be used to activate the product.
As the product mentioned is Cloud for Enterprise, you have to verify first if your Adobe ID (email address) has been assigned to the user rights.
You will find more information in the following link: http://helpx.adobe.com/creative-cloud/help/manage-creative-cloud-teams-membership.html
If you have already proceeded the the previous steps, please try the steps below then:
1. Clean Up cached user login information
Close the Creative Cloud application.
Navigate to the OOBE folder.
Windows: [System drive]:\Users\[user name]\AppData\Local\Adobe\OOBE
Mac OS: /Users/[user name]/Library/Application Support/Adobe/OOBE
Delete the opm.db file.
Launch Creative Cloud.
2. Reset the Hosts file
Windows
Choose Start > Run, type %systemroot% \system32\drivers\etc, and then press Enter.
Right-click the hosts file and select Open. Select Notepad for the application to open the hosts file.
Back up the hosts file: Choose File > Save As, save the file as hosts.backup, and then click OK.
Search the hosts file for entries that reference Adobe (for example, 127.0.0.1 activate.adobe.com) and delete these entries.
Save and close the file.
Mac OS
Log in as an administrator to edit the hosts file in Mac OS.
In a Finder window, choose Go > Go To Folder.Type /etc.
Select the hosts file and open it.
Back up the hosts file: Choose File > Save As, save the file as hosts.backup, and then click OK.
Search the hosts file for entries that reference Adobe (for example, 127.0.0.1 activate.adobe.com) and delete these entries.
Save and close the file.
Please, let us know how it goes.
Thank you.
Arnaud.

IF-statement in Personas that is checking if control is inactive?

Hi,
I have this simple script in screen personas that is clicking the option: "Attachment list". Everything is working great if there is attachments.
If there are no attachments the option is "inactive" or "greyed out". This will result in a script error.
I thought this was going to be an easy fix by adding IF statement to the the script. But howerver I specify the critera for the IF statement the script will always try to click the Attachment list. The condition will simply always be TRUE.
Am I missing something here or is it not possible at this time to script an IF statement that is checking if the control is inactive or similar?
Best Regards,
Oskar Söderlund

There is another way, but it will get a little tricky.
Outside of the transaction IE03 you can check for the existence of attachments for a piece of equipment by looking in table SRGBTBREL. Field TYPEID_A will be "EQUI" and field INSTID_A will be the equipment number, zero-padded on the left to 18 characters long. Use SE16 to look in the table and you'll get the idea.
You could wrap this test in an RFC-enabled ABAP function and call that from your Personas script button. Use the return value from that RFC to decide if attachments exist or not and how the script should respond. Details for how to write such an RFC and call it from a Personas script are in this blog: Calling RFCs from a Personas script.
Like I said, this isn't straightforward and perhaps Personas scripting should include an active/inactive test in addition to the exists/doesn't exist test. Until then, however, there is a way if you don't mind a bit of ABAP programming.

How can I create a Teststand (1.0.3 or 2.0) distribution without having all of the VIs (6.0.2 or 6.1) in the same directory?

How would I create a Teststand distribution of LabVIEW VIs and maintain the test VI directory structure that I want?
I know that I have to use the application builder to build the custom operator interface, configure it as an ActiveX server, and launch the Teststand engine installation.
The only problem that I have is using the VI packager which puts all of the test code and sequences in a single directory.
This gets quite messy. There are just over 1000 files in the neatly orgainzed directory structure that I have now. (this includes support files, dll's and such)
I have read brief appnotes on configuring the ini file(s) to use
the vi search path that I want, but have not been able to get this to work. Maybe I'm not updating the correct ini? or have to include each subdirectory?
I have currently upgraded from LabVIEW 6.0.2 to 6.1
I am currently using Teststand 1.0.3
I have not upgraded to Teststand 2.0 yet because I have not decided if I want to build at this revision or go through the extra work to mass compile Teststand at LabVIEW 6.1, install the LabVIEW 6i VI Packager Fix, and update the new Teststand LV operator interface with my changes.
At present, I'm not getting the results I want and am quickly running out of time. I have to deliver the project by the 14th of July 2002.
Sorry for the long question and thanks for you help.

Hi,
I dont think the problem is really related to using the VI Packager but more to how the OI interface applications relates to labVIEW File constants.
If you are using the LabVIEW as the ActiveX Server then there should be no problems. But if you are using the Runtime LabVIEW server such as 'TestStandLVRTS' then the file constant would return different paths.
eg for the Default Path you would get 'C:\TestStand\Components\User\RuntimeServers\LabVIEW' instead of 'c:\Program Files\National Instruments\LabVIEW'.
Attacted is an example to show how to change these paths when using your runtime server. Unzip this into your teststand examples folder
Put the INI file in the location of the \user\runtimeservers\labview folder.
Change the labview adapter t
o use TestStandLVRTS.exe. You can run the example sequence from either the OI or seqeditor.
I hope this helps
Regards
Ray Farmer
Regards
Ray Farmer
Attachments:
UsingLVOI.zip ‏20 KB

Licence TestStand inactive

Similar Messages

Maybe you are looking for