deployment licenses

Similar Questions

• TestStand Debug Deployment License Question

  I'm a little confused by the licensing OR and need advice...

  I have a PC that I use with a contract manufacturer that is set up to run LABView and Teststand
  applications.

  It was working fine until recently, I've updated this PC and receive the following backup TestStand license
  screen every time I run the TestStand on this PC application:

  

  When I try to activate this product online, I get the following screen:

  

  On this PC I have not loaded development system but I buy and had installed on this PC, a copy

  of the TestStand Base Deployment Engine. I don't know what is the debug deployment environment or how

  He got on this PC.

  If these are the same package, where can I find the serial number for the TestStand Base Deployment Engine on my

  2013 developer Suite CD?

  If these are not the same, How can I remove this backup reminder now so I can make sure I can run again TestStand

  applications on this PC (that I need to send it back to a remote site before 5 days)?

  Thank you

  Just delete the license files according to the link I mentioned earlier.  Then you should be able to activate correctly again.

• LAbview RT deployment license

  I need your help on a question:

  A client has the following Architecture:
  -Accommodate Mahcine running on windows and where they have the CVI and CVI Real Time 8.5
  -a PXI system with controller 8106.

  They want to start their PXI-8106 on RT, so they bought the license for Labview RT deployment.

  What I need from you guys is the following:
  -The sequence of the instalation they have to perform
  -When they started instyalling the CD they got a messgae saying that time real 8.6.x is required (which is not available at their sides).

  Thank you

  HI Maria,

  To configure the deployment on your controller PXI-8106 to LabVIEW Real-time, you will need to do the following:

  (1) load the BIOS pressing the del key at startup. Make sure you see a section "LabVIEW Real-time. If this isn't the case, you must update the BIOS (ftp://ftp.ni.com/support/pxi/pxi-8106/BIOS/).

  (2) once you can view the LabVIEW Real-time section in BIOS, select this option to start in SafeMode in time real LabVIEW and then continue with the startup. You should see monitor output indicating that the target is not configured.

  (3) using NI Measurement and Automation Explorer from your host machine to set up the target time LabVIEW Real-time.  You can set the IP address, load software, etc. When you have finished configuring the PXI-8106 target module, you can set the BIOS to start in LabVIEW Real-time each time.

  (4) develop your application in real-time of the CVI and then follow instructions to (http://digital.ni.com/express.nsf/bycode/exn6qb) to deploy the application on the target in real time.

  Please let me know if you need additional information and have a great day!

  Kind regards

  Casey Weltzin

  Product Manager, LabVIEW Real-time

  National Instruments

• VLM - Testers checking debug licenses instead of deployment.

  We currently use VLM 3.1 with a limited number of licenses of debugging, and a large number of deployment licenses.  Some of our testers seem to insist on pulling debug licenses, even when running through the interface of the user logged in as operator.  The two switch Executive 3.0 and teststand 3.5 seem to be guilty of this.  VLM is currently the Setup based on computer, not the user.

  Hey Bob73

  I did a little more research into what happened with your deployment/debug licenses.  I have come across some good information on why this is happening.  We have an internal document that indicates that it is a known problem in TestStand 3.5.  It has to do with the operator TestStand 3.5 Interface correctly attempts to extract the TestStand_InstEngine in the license of the Package of basic deployment, but incorrectly then try to check a feature available in the TS Debug Deployment license.

  This will happen only if one of the following conditions is met:

  • The VLA has unmanaged for debugging concurrent licenses.
  
  
  • The computer/user who tries to order the license has permissions for a license with the option to deploy.

  To solve this problem you will need to create a service request.

  I'm sorry that I didn't connect the dots earlier.

• LabVIEW and TestStand licenses

  Hello everyone, I did a lot of reading through the info OR on the case, but thought someone here could explain a little more clearly. Basically, I would like to know what is the licensing for Lv and TS applications, if I understand correctly, I will require an individual license for deployment on each machine that I want to run an application of TS, regardless of whether or not I have the software but launch an executable instead.

  In regards to LabVIEW, is the way to understand it, it seems to me that if a machine without LV who has LV runtime can run my executable, it does not require a special license? Can anyone shine some light on the matter?

  All this comes from the fact that my current job could ask implement TestStand and LabVIEW, as our current sequencer is simply too basic and rudimentary to the applications that we expect. It's a place big enough then, what would the licensing conditions? Runtime engine just for what works and a deployment of TS for stations that run it?

  ATTENTION: OR licenses are business of OR to keep up with your Rep OR!

  But in a word (as I navigate these waters for a living)

  • The LV runtime is all that is required to run that a LabVIEW built applications or LabVIEW modules called by TestStand in most cases.  The RTE LV is provided with an end-user license agreement, but the license is free.  OK OK... some LsbVIEW SDK may require additional deployment licenses.  I think that the Vision is one of those rare "needs a key deployment that is not free" toolboxes.  I've never deployed an executable LV requiring a deployment Toolkit cost-once again, check with your representative.
  • TestStand deployment licenses cost by target computer.  There are several options to the less expensive, the deployment of Base, more flexible options as a deployment "Debug" to risk mitigation, workflow of your compay, number of test stations and familliarity with deployment options, maturity of the Test system is expected to help guide the process of voluntary decision.

  Since it is a new path for your company, consult with an Alliance partner with experience in assessing your needs, regulatory environment, level of skills and practices.  (And no, TestStand deployment methods assessment is not a base of 8-Ball consulting so compentancy think not that I am marketing here)  You ask OR Rep and look the Alliance Partner Locator

• TestStand on Windows 2K 3 x 64 deployment issues

  Holil:

  I hope that there can someone advise me.

  I recently tried to build an application TS to deploy on a server running WIndows Server 2003 x 64, and I ran into some difficulties.  On my development system, (32-bit Windows XP pro), I built a deployment TS Installer.  I transferred to the destination machine.  Installation failed... He says that many files were missing from different CAB files.  I tried again... the second time I had more luck... the installation seems to take.  Using the License Manager, I turned on my setup using my development license (my deployment license has not yet arrived).  I tried to run my application and I get an exception that seems to indicate that the ActiveX DLL are not saved:

  Unhandled exception: System.Runtime.InteropServices.COMException (0 x 80040154): C
  Lass did not registered (Exception from HRESULT: 0 x 80040154 (REGDB_E_CLASSNOTREG))
  at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance (Guid & clsid, Obj
  ECT punkOuter, Int32 context, Guid & iid)

  I tried to register these manually to help

  regsvr32 "D:\Program NIUninstaller Instruments\TestStand 4.1\API\DotNet\Assemblies\CurrentVersion\NationalInstruments.TestStand.Interop.UI.AxControls.dll"

  but he complains that this DLL has no DllRegisterServer entry point.  (Is this the wrong DLL to register?)

  I tried to uninstall my deployment and installation the teststand full... and the SeqEdit seems to work fine.  (He must have registered the DLLs required, no?)  My app, however, still does not. I try to install Visual Studio to see if I can rebuild the application on this system with better results.

  I missed an important step?

  Thank you!

  Tom MacLean

  I think the problem was I have to target the solution for a x 86 platform... not any platform.  If I have other problems with this particular application, I was able to recreate the example Simple OI in a new project with the same exception that I had with mine, and change the target platform does the job.

• How to get the license information on VxWorks?

  Wind River requires a few details of the license before allowing access to their programming documents. Presumably, the purchase of a controller for crio running VxWorks includes a license for the operating system. How can I get information on this license?

  Thank you

  Chris

  Hello Chris,

  When you buy a goal based on VxWorks you get only one deployment license, which means that you can deploy to the VxWorks target, but you don't have access to the support or documentation.

  Access to their programming documents requires a development license, usually coupled with Wind River VxWorks Workbench.

  See you soon.

• Executable test sequence TestStand deployment

  Hello

  I would like to automate my test using TS environment and the BT.

  My goal is to have one machine with the development of TS (Inc. LV) for construction of test software that is compiled in one .exe file to run on the tested machine that does not have TS or LV

  Can I use the software for this task?

  It is for the main development computer:

  
  
  
  
  
  
  
  
  
  
  
  
  
  

  779601 35	NEITHER Developer Suite, English, include 3 years SSP	1
  779602 35	NEITHER Developer Suite Automated Test Option, include 3 years SSP	1

  It is for the machines to run the tests on:

  777774-3505 NI TestStand Base Deployment Engine License 5 unit Bundle

  I would like to have an option to monitor the performance of the tests on each machine and if necessary to perform debugging on the tested machine operations.

  If the package above will provide this capability so where can I find the documentation to create .exe files to run on test computers?

  If not, what software will provide this capability?

  Thank you

  His Lev

  Lev,

  These are the correct packages for TS development and deployment.  The only thing is that you have little debugging with the deployment license features.  If you want to debug, so instead of the deployment license they have licensed TestStand Debug.

  http://www.NI.com/TestStand/deploy-compare/

  More about licenses: http://digital.ni.com/public.nsf/allkb/B4B7C4ADB9B21B3F86256D360061891F

  One thing you should realize is that TestStand creates no executables.  Because TS is essentially a scripting language, you deploy the raw files.  These raw files feeding the TestStand engine and execute the steps in order.

  TestStand comes with 10 different (fully customizable) User Interfaces.  What are executables and run above the TestStand engine.  They allow you to run your sequence files (mostly scripts).  You will only need to use 1 of them.  The User Interface is so technically the executable for a deployment machine.

  More information on automation TestStand deployment:

  http://digital.NI.com/public.nsf/allkb/EE3382373D209449862570A5006572F0

  Chapter 14 of the reference manual: http://www.ni.com/pdf/manuals/373435e.pdf

  Interfaces user is in Chapter 1 to chapter of the major components:

  http://www.NI.com/PDF/manuals/373435e.PDF

  I hope this helps.

• With the help of dynamically called screw in TestStand deployment

  I write code to interface with a & Rohde Schwarz ZNB Network Analyzer.  I use LabVIEW 8.2 and TestStand 3.5.  For reference the ZNB driver is available here: R & S of ZNB Driver.  I use a slightly older version of the driver, some before they needed to LabVIEW 2009.  I am writing all the code on a development machine that has the full version of TestStand/LabVIEW and it works on another machine that has the TestStand deployment license.

  This driver is dynamically linked to some things he needs.  I am able to operate with simple LabVIEW EXEs but not in TestStand deployments.  The following excerpt comes from their documentation, explaining a little about how the driver works and how to use in LabVIEW EXEs.

  3.4.2 How to generate executables or libraries in LabVIEW driver kernel drivers instrument based on attributes is dynamically bound to any VI performed during execution. This can be recognized by the LabVIEW application builder. The LabVIEW application builder follows all the static dependencies and include them in the package distributed at the generation of an executable file.

  To create an executable in LabVIEW, please manually add all the screws in the \PREFIX \_utility\callbacks folder to the LabVIEW project. In the case of project based please add private to your project folder. With this reference manual, the driver core is included in the compilation and the driver core is accessible during execution.

  I can't get this to work in TestStand deployments at all.  I can't even connect to the device since the VI Init has these issues.  I get the same error for all the various attempts that I made.  The same error is that when you add manually the screws for the LabVIEW EXE.

  Error-1073807346

  Property in Rohde & Schwarz Vector Analyzer.lvlib:rsidr_core_session_fgv.vi-> network node

  Rohde & Schwarz Vector Network Analyzer.lvlib:rsidr_core_check_error.vi->

  Rohde & Schwarz Vector Network Analyzer.lvlib:rsidr_core_attribute_write_int.vi->

  Rohde & Schwarz Vector Network Analyzer.lvlib:rsidr_core_attribute.vi:3->

  Rohde & Schwarz Vector Network Analyzer.lvlib:rsvna.vi:2->

  Example 1 setting of the Instrument 24Default .vi:1->

  Rohde & Schwarz Vector Network Analyzer.lvlib-> efault Instrument Setup.vi

  Rohde & Schwarz Vector Network Analyzer.lvlib:Reset.vi->

  Rohde & Schwarz Vector Network Analyzer.lvlib:Initialize.vi->

  Connection of ZNB testing.VI

  VISA: (Hex 0xBFFF000E) the given reference of session or the object is not valid.

  So far, I tried the following, all solutions producing this same error.  I struggled with this and turned off for awhile then maybe there are other solutions attempts I forget.

  (1) it looked like a lot of the report to go to the private folder were finished in SupportVIs.  I manually pasted the rest there, too.

  (2) I added all driver files on my workspace and included in the files with the rest of my deployed screws.

  (3) I added all driver files on my workspace and said pilot TestStand to deploy them to the original location in Program Files.

  Someone at - it ideas?  R & S didn't even know what was TestStand, so that they could not help me.

  I was finally able to solve this problem on mine, the other day.  I brought the Network Analyzer to my office and did a lot of tests in this way.  Eventually, I discovered that I needed to include the folder private pilot deployment, what I was doing in one of previous attempts.  It turns out that you must also maintain the original of this file directory structure when you include it, otherwise dynamic calls are not looking in the right place.  Once it worked on my PC, I got it on the machine test and worked as well.

• NI-VISA licensing policy

  Hello

  I would use NI-VISA for my current project, but I'm a bit confused when it comes to licensing policy. Please help me determine whether or not I have to acquire developer NI-VISA and/or deployment license.

  In my scenario, I need to write an application Windows (using Embarcadero Delphi IDE) who will control the Tektronix TDS 2000 oscilloscope series via USB. For the control of low level of oscilloscopes, I like to use NI-VISA software.

  I have to buy a NI-VISA license?

  Thanks in advance

  Ivo

  Hello Ivo,

  license for NI-VISA is included in the price when you use some sort of application development environment, that is. LabVIEW or LabWindows/CVI. Other cases, is that you have hardware that you control with NI-VISA, the license for NI-VISA is included in the price of the material. In the case where you use OR development environment or material, you must purchase the license to use NI-VISA. For details please see page ni.com/visa/license.htm.

  Please let me know if I can help you more, or mark my answer as being correct.

  Thanks, have a nice day.

• Y at - it a term of license necessary for MStudio 8.6?

  Hello

  I recently downloaded MStudio 8.6. Before making the decision to buy it, require a deployment (such as VDM) other than the Licnse development license? Thanks in advance

  Hi Wade,.

  There is no deployment license, you must purchase to distribute Measurement Studio applications. All license information gets incorporated into your EXE. See also the Conditions of licence to distribute the Studio Applications measure KB.

  Best regards

• What license do I need during sequences of script

  Hello!

  I am currently working on a sequence that will be deployed on the production test benches (testbeds #20).

  This sequence will be in charge of a test sequence specific for each product that can be tested to the single test of script.

  I noticed that when I script my test sequences, TS is checking the type of my driver's license. So I guess that a specific license is required to do this. Should what type of license I buy for this sequence on the benches of my test?

  I think that if you're just scripting generating the sequence files you just need one deployment license. At least technically. I'm not an expert on the legal requirements of our licenses then maybe someone else to answer from a legal point of view. That said, you can do work without saving the file by directly setting the Execution.ClientFile to your file dynamically created things and what makes your file dynamically created directly be the customer file (any file client stub required).

  Make sure you read the help of the API for Execution.ClientFile that there are some pitfalls in using this API.

  Alternatively, you can look at the example:

  \Examples\DynamicClientSequenceFile

  Hope this helps,

  -Doug

• ACS 5 + license - maximum supported of the unique IP addresses?

  Hi all

  I have a question about ACS 5 + license. Here:

  http://www.Cisco.com/en/us/prod/collateral/netmgtsw/ps5698/ps6767/ps9911/product_bulletin_c25-616320.html

  There is this statement:

  With the basic licence, Cisco Secure ACS 5.2 devices or machines virtual software can support deployments of up to 500 devices of network (authentication, authorization, and client accounting [AAA])

  ......
  

  The optional add-on of large deployment license allows deployment to support over 500 network devices. Deployment license important that one is required per deployment as it is shared by all instances.

  Does anyone know how many devices is supported with large deployment? I understand that more than 500, but how much more (with reconciliation)?

  Thank you and Bravo,

  Hug

  It's unlimited - but they way ACS he treats can be very simple.

  For example.

  When I add 1 device with a single IP address he uses 1 500 guests allowed (on the standard license)

  If I add a 24 network range it is still a record but uses 255 guests

  If I add a 16 network range this new is still a record but would use 65535 hosts (and of course you can do it on the base license)

  By experience, it is difficult to manage unique devices in ACS and instead has a lot simply to group these features in IP address ranges.

  Therefore, you could have technical network 255 x 8 lines covering all areas of using 4 billion possible IPv4 addresses + host records, but always in just 1 record on ACS

  Paul

• ISE HA / node licenses group

  I have a single ISE 3355 with 2200 basic licenses.

  I intend to buy an another 3355 for redundancy purposes.

  Just add this in the node group and the license pool is shared between the nodes? I can't imagine that I have to rebuy all licenses for the 2nd device.

  Thanks in advance.

  That is right.  There is not need to purchase licenses additional paks.  ISE deployment licenses are based by endpoint, not by the node of the ISE.  You can simply add the new node to the existing deployment.

  You have probably already seen this, but here's a guide for distributed deployments:

  http://www.Cisco.com/c/en/us/TD/docs/security/ISE/1-2/user_guide/ise_user_guide/ise_dis_deploy.html

  Please rate useful messages and mark this question as answered if, in fact, does that answer your question.  Otherwise, feel free to post additional questions.

  Charles Moreton

• ACS 5.2 Licenses

  Hi all

  I need help on my licenses

  Here's my situation:

  -Today, we have an ACS 5.2 VM with the base 500-device license and we must go beyond this threshold.

  -We will install a second ACS 5.2 VM for redundancy, but it's still a few months.

  -We bought new licenses: a new 500-unit basis for the second ACS license and important deployment license that will allow both over 500 devices.

  -We received a single PAK file with these two licenses: background and deployment

  -the second implementation of GBA is still a few months, but I need to install the new license of deployment as soon as possible.

  My questions are:

  Can I deploy existing GBA only the part important deployment of the PAK file I received and when the new ca is implemented, deploy the other half of the license file, with only the basic licence?

  Can I install the new license file PAK with these two background licenses and deployment on the existing server, and then delete the original base license so I can install it in the future when the new ca is implemented?

  I need to understand how to proceed.

  Thanks for your help.

  José Ribeiro

  Ideally, you want to install on your existing ACS deployment license and the other base on the new CAs license. When the new CAs joined the deployment with the large deployment license already installed, it will go get the grand license deployment of the configuration database.

  You said that you have received these two licenses in a single PAK file. If try to install both the existing GBA, I think he's going to complain that a base license is already installed. Not sure if this would avoid the important installed deployment license.

  However, if you look at the file, the two licences should be separate elements in the file each with their own separate data. It should be possible to duplicate the PAK file and then change each of the copies so that they only contain one of the licenses