LAbview RT Deployment licence

I need your help on an issue :
A customer has the following Architecture :
- Host Mahcine running on windows and where he have the CVI and CVI Real Time 8.5
- a PXI system with 8106 controller.
They want to boot their PXI 8106 on RT so they bought the Labview RT Deployment Licence.
What I need from you guys is the following :
- The instalation sequence that they have to perform
- when they started instyalling the CDs they got a messgae saying that the Real Time 8.6.x is required (which is not available at their side).
Thank you
Med Mehdi BOUZID
Field Sales Engineer (Tunisia & Algeria)
National Instruments Arabia Branch
www.ni.com\arabia
Solved!
Go to Solution.

Hi Mehdi,
To set up LabVIEW Real-Time deployment on your PXI-8106 controller, you will need to do the following:
1) Load the BIOS by pressing the DEL key on boot. Verify that you see a "LabVIEW Real-Time" section. If not, you need to update the BIOS from (ftp://ftp.ni.com/support/pxi/pxi-8106/BIOS/).
2) Once you can view the LabVIEW Real-Time section in the BIOS,select to boot into LabVIEW Real-Time safe mode and then continue with booting. You should see monitor output indicating that the target is unconfigured.
3) Use NI Measurement and Automation Explorer from your host machine to configure the LabVIEW Real-Time target. You can set the IP address, load software, etc. After you are finished configuring the PXI-8106 target, you can set the BIOS to boot into LabVIEW Real-Time every time.
4) Develop your CVI Real-Time application and then use the instructions at (http://digital.ni.com/express.nsf/bycode/exn6qb) to deploy the application to the Real-Time target.
Please let me know if you need any additional information, and have a great day!
Regards,
Casey Weltzin
Product Manager, LabVIEW Real-Time
National Instruments

Similar Messages

Deployment licence

Hello,
I have a formal question. I want to deploy code written for cRIO9014 with FPGA 9118. Do I need to purchase deployment licence or this required only for PC based RT targets?
Thank you,
Przemek

Hi Przemek,
I would think you need the AppBuilder license. But to be sure you should just phone your local NI support...
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Deploy licences for Lync server 2013

Hi Guys,
How can i apply or how to put the Licences on Lync server 2013 i have a test lab Lync Server 2013 and i want to put the License on it how to do that? or is it possible i need another installation for it?
Thank you,
This forum really helps a lot.

Agree with Anthony, the only other scenario is if you want to upgrade from the Evaluation to the full version in which case you need a copy of the full version media and follow the steps below:
Insert or mount your full version media on your Lync server.
Open Lync Server Management Shell
Run Get-CsServerVersion to display the current version
Run msiexec /fvomus server.msi EVALTOFULL=1 /qb
You may be prompted to specify the location of server.msi (which can be found in the Setup\amd64\Setup\ folder on your installation media.
Run Get-CsServerVersion to confirm the conversion was successful.
Run Enable-CsComputer
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
www.lynced.com.au | Twitter
@imlynced

Error 1722 in Windows 7 LabVIEW Installation Application Deployment

Hi,
I am using Application Builder in version 8.5 of LabVIEW to deploy my stand-alone executable. I've never had an issue on Windows XP, and have had many successful installation on Windows 7. However now I have a customer who gets the following error in Windows 7 (but the same installation package works fine for him on XP machines):
Currently Installing NI-DIM 1.7.0f0, Part 10 of 19 with Error 1722.
Error 1722. There is a problem with this windows installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Contiunue Y or N.
Anyone (NI application engineers in particular) have any ideas? (My support contract has expired. I think there is a way to report bugs, but is there a way to contact NI support directly in addition to this forum?)
Thanks for any help.
Ed
Solved!
Go to Solution.

UPDATE:
Good news! My customer got back to me and told me it was his anti-virus software (Trend Micro) that caused the error. When he disabled it as I suggested (which I got from a NI knowledge base article on "Error 1722"), the installation was successful.
Thanks all 'till next time...
Ed

What are the different steps to follow in order to develop an application and deploy it into a PAC

Hi,
I developped a program on my computer but in order to deploy it in a PAC , I don't know what are the different steps to follow?
What are the difference between a stand alone application and communication with server mode.
Can the file which will be downloaded into the PAC be in a form othre than (.exe).
what does the deployment licence consist of??? is it a software?
if the file is .exe then how to maintain it?
Thank you for all,
Regards

Hi!
   Since I'm familiar with FieldPoint PACs, I'll refer to that (but maybe it is similar for cRIO...).
   An embedded application (standalone), runs entirely and independently on the PAC, while if you're not doing this, you'll have your computer, with LabView, which is controlling the PAC. In this mode, application is dowloaded in PAC's RAM, so when you reboot controller, application will be lost. If you build an embedded application, you can provide for application to boot authomatically at boot, each time the PAC reboots. These are some basic stuffs on embedded applications with LV.
    To deploy an application to a PAC, you need LabVIEW + Real-Time module. Without it, you can't build an embedded application on PACs.
    usually, the file dowloaded is an .exe, and some libraries. What would you like to have, exactly? For example, I think you can buy a simple .exe, which is universal, which loads VIs dinamically, so you can download directly VIs, but I've never tried this way....
   Deployment license, I think, refer to PCs, id est, when you use a PC or PXI as embedded target, in PACs, you have it bundled (it seems to me) whit the PAC you buy, so you don't have to buy an extra license for every PAC you ship with your application. Otherwise, if you develop a Real-Time application for a PC, you will ship PC + OS licensed + Real-Time extension licensed, but this is not your case, since you'll use PACs.
   The maintain problem... I've already faced with! Simply, for my needs it was enough to make an application which loads configuration files, depending on different task the controller has to do. If you have to dowload a completely new version of VI.... it's better to deploy new application from LV. But maybe you can bypass this problem with dinamic VIs loading...
    Let me know if this help.... Have a nice day!
graziano

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)

Difference between LabVIEW RTE and TS LabVIEW RTE

Ok, this may be an easy one but still I would to have it clear. What is the difference between using LabVIEW RTE and TS LabVIEW Runtime Server to run LabVIEW modules/steps in PC's with TestStand Deployment licences???
Thank you,

Hi,
The TestStand LabVIEW Adapter can run VIs
using any of the following LabVIEW environments, or servers: the LabVIEW
development system, the LabVIEW Run-Time Engine, or a LabVIEW executable built
with an ActiveX server enabled. The Teststand LabVIEW run-time server
(TestStandLVRTS) is a version of the third option written way back at a time before the LabVIEW run-time engine is what it is now.
The only reason you would possibly want to use the TestStandLVRTS is when you
have VIs written with versions of LabVIEW older
than 6.1.
Have a great day,
Ecleamus Ricks, Jr.
National Instruments
Applications Engineer

Labview 7.1 to Labview 8.0 upgrade

Greetings all,
My company has recently aquired labview 8.0 licences and is intending to use it as its development platform instead of labview 7.1. the problem is that all of our customers are currently running executables generated in a labview 7.1 environment and any updated versions of our software that we will send them in the future will most likely be developed in labview 8.0. The question is , other than sending them the executables generated by LV8 along with LV8 RTE are there any problems. did any one see a problem with a conversion like this. i have done alot of reasearch about this and have been testing the converted code from 7.1 to 8 and the executalbes generated by 8.0 and i havent seen any major problems. any feedback on a related probelm would be greatly appreciated.
I am using
Serial communications
LPT ports
udp communications
PCI I/O boards
talking to remote and local data bases (Micorsoft and Oracle)
all on a Windows Xp pro operating system

Hi,
Only thing I've noticed so far is that LV8 uses the show scrollbar setting from it's contained vi and LV7 doesn't. Very minor...
We had some problems with old daqmx that wasn't working with LV8 vi's, and the new daqmx didn't support the hardware. We solved it by copying some LV7 vi's to LV8. I don't know all the details, my colleague worked on it.
I hear some stories about multi platform deployment problems (FPGA, RT..), but I don't know any details.
If all hardware is working, I wouldn't be concerned.
Regards,
Wiebe.
"malyounes" <[email protected]> wrote in message news:[email protected]..
Greetings all,
 
My company has recently aquired labview 8.0 licences and is intending to use it as its development platform instead of labview 7.1. the problem is that all of our customers are currently running executables generated in a labview 7.1 environment and any updated versions of our software that we will send them in the future will most likely be developed in labview 8.0. The question is , other than sending them the executables generated by LV8 along with LV8 RTE are there any problems. did any one see a problem with a conversion like this. i have done alot of reasearch about this and have been testing the converted code from 7.1 to 8 and the executalbes generated by 8.0 and i havent seen any major problems. any feedback on a related probelm would be greatly appreciated.
 
I am using
Serial communications
LPT ports
udp communications
PCI I/O boards
talking to remote and local data bases (Micorsoft and Oracle)
all on a Windows Xp pro operating system

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

LabVIEW 8.5.1 Build Problem With LV2010 Installed

I am experiencing a problem when building an application installer using LabVIEW 8.5.1. I have built this application many time before but since installing LabVIEW 2010 I can no longer build the installer.
I have tried to buiuld the application on a Windows 7 PC and a Windows XP machine. My minimum requirment in my build options was Windows 2000, I changed that to XP but it made no difference.
I get the following error message:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_GetCount.vi
Loading product deployment information
Adding files to installer
*** WARNING ***
Cannot enforce the requested minimum operating system restriction because the deployment engine only supports Windows XP or later. Resetting minimum restriction to Windows XP or later.
Done adding files
Preparing to build deployment
Copying products from distributions
*** Error: Fatal runtime error. (Error code -10)
*** Error Details:
Error in MDF API function: _MDFDistCopyList_GetCount
Access violation! Structured exception code 3221225477
*** End Error Report
Done building deployment
Has anyone else come across this?
Thanks in advance.

Thanks Andrew.
It didn't help. After three days of trying, I did get one system to build without error. I'm currently trying to get another system to build.
It looks like the Access violation is caused by the deployment utility not asking to change to DVD 3 for CVI after the product caches has been cleared (To fix the error code -40 problem). Restoring the CVI runtime (NI LabWindows_CVI 2009 Service Pack 1 Run-Time Engine [9.1.1450]) to the Product Cache seems to fix the problem.
The status log doesn't show enough information to figure out the problems. Looking at the end of the Detailed_Installer.log is pretty much manditory.
My recomendation is to build first with "Install TestStand Engine" and the various "Driver and Components..." turned off and then slowly enable the ones wanted.
Also, it saves a lot of pain and suffering to do at least one deployment with "Copy Installers to Product Cache by Default" turned on before doing an upgrade so you don't have to go search for old DVD's.
After a lot of trial and error, I believe these are the steps I went through to finally get it to work:
1. Close TestStand, LabView, and Deployment Utility
2. Delete all in C:\Program Files\National Instruments\Shared\ProductCache, except the CVI Runtime
3. Delete all in C:\Documents and Settings\All Users\Application Data\National Instruments\MDF\ProductCache, except runtime 7.1.1
There seems to be something wrong with the .NET language pack installation. It always seems to generate errors.
3. Run DotNet20x86langpack.msi on the Device Driver DVD at Products\DotNet20langpack_x86_Installer\ and uninstall.
4. Run DotNet20x86langpack.msi and install.
5. Put DVD 1 back in.
Got an error with the .Net installer so. . .
6. Uninstall at D:\Distributions\LV\Products\DotNet20_x86_Installer\DotNet20x86
7. Install at D:\Distributions\LV_SE\Products\DotNet20_x86_Installer\DotNet20x86
8. Again Install at D:\Distributions\LV\Products\DotNet20_x86_Installer\DotNet20x86
9. Run TestStand, LabView (if using VI's), and the Deployment Utility.
Runtime 8.5.1 should install automatically and ask to reboot the system. Go ahead reboot and run Teststand, etc. again.
10. In global settings, 'clear prompt before'. . . , and select 'copy installers to product cache by default'
11. On Installer Options tab, clear "Install TestStand Engine".
12. Build - ALWAYS 'remove all files from this folder before building'
It "should" build. If not, fix any errors.
12. Select Install TestStand Engine.
13. Select Engine Options... and clear all check boxes (except runtime 7.1.1)
14. Build again (make sure DVD 1 is in)
15. Install other Engine Options, Drivers and Components.
16. Build again (make sure DVD 1 is in)

LabVIEW Software Developer/Hardware Integrator

La Jolla, CA based automation and custom solutions provider seeking LabVIEW software developers.
Job Description
Seeking a National Instruments LabVIEW Software Developer/Hardware Integrator to join our team developing customized automated control and test equipment.
The preferred candidate will have 1-5 years experience in software development and hardware integration using LabVIEW and some experience with embedded C. Candidate must have hands-on experience interfacing and calibrating various transducer signals to both National Instruments and Third Party data acquisition boards.
Software Experience
Programming experience with an understanding of a majority of the items below:
Labview Programming 1-5 years
GOOP/LVOOP
Database Connectivity
RS232 and USB COM programming
Real Time Systems
AIO, DIO, Counter Configuration and Operation
Producer/Consumer Architecture
Queues, Events, Timed Loops, Objects, Multithreading, Hardware Triggering, Variants, Code Interface Nodes, PID
ActiveX, DLL APIs
LabVIEW Application Deployment (building and deploying executables)
*A preference will be given to candidates who have experience in both NI Data Acquisition hardware and Embedded Arm Development.
Hardware Experience
Candidates will have demonstrated experience (or at least a basic understanding of) in the integration of transducers and signal conditioning commonly used in Biomedical/Biotech industries into data acquisition and control systems including but not limited to:
Temperature (TCs, RTDs, and Thermistors)
Photodiodes
pH,DO,ORP Electrodes
Liquid/Gas Valves
Liquid/Gas Pumps/Compressors
Motion (Stepper and DC Servo) including Quadrature Encoders
Pneumatic displacement cylinders
Lighting (Bulbs and LEDs)
Solid State and Mechanical Relays for AC/DC power switching
Thermoelectric Coolers
Digital Switching and Bus Communication (DIO, SPI, Counter, Triggering, etc.)
Education
Some college-level experience in Electrical/Computer/Optical/Bio/Chemical Engineering and/or Computer Science. A formal degree is not as important as capabilities and creativity. Previous Experience with National Instruments LabVIEW Training is highly desired. Understanding of AC/DC circuit basics is a requirement and a preference will be given to candidates with more component level electronics experience.
Positions
We have both part-time and full-time positions available in our La Jolla, CA office. We are a company specializing in the development of custom automation solutions for various clients primarily in the Biotech/Biomedical/Oceanography areas. We are a small, but growing company looking for individuals who like a diverse work environment filled with unique challenges that are constantly changing.
If you enjoy using your creativity and talents in a fun entrepreneurial environment and like the idea of working in the beautiful surf-town of La Jolla, CA then we want to hear from you...
www.labviewautomation.com

Hey, I own a Canadian built sailboat, drink the occasional Canadian beer, watch CKWS on cable, can say Eh! with the best of them, had my first anniversary honeymoon in Ottawa. I even have a loonie in my pocket and $5cdn in my wallet You have to be Canadian? Winters are milder there than where I live too.
Fixed wire, that is for those posters in the other threads that insist on posting for the 3 -4 year old jobs! How else will he get them to apply in a timely fashion?
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Understanding TestStand Debug Deployment License

After reading the License Agreement and the TestStand Help section on licenses I still would like an explanation as to exactly what the license does and does not allow. My understanding is with a TestStand Debug/Deployment license I can install TestStand on a machine, let's call it the development machine, and also install TestStand on another machine, my production machine. The development machine is where I would develop applications to deploy onto my production machine. The production machine is where I would actually test my products. The production machine can also be used as a platform to debug my deployed applications. If this is true then can I develop any additional tests on the production machine, e.g. I found a problem in the sequence so I need to add a new sequence to correct the error? Or I found a problem with a LabVIEW VI and I need to create a new VI to correct it. Can I develop VI's and sequences on the production machine or do I need to develop on the development machine transfer the files over to the production machine and hope it works (this type of process could prove to be very time consuming and tedious)?

Thanks for the info. Now what about LabVIEW. Here are some options I'm considering:
1. Run a LabVIEW Runtime Engine on the production machine and a FDS of LabVIEW on the development machine. In turn run a TestStand Deployment license on the production machine. This seems the most cost effective method. The problem I'm having is some VI's are developed in LabVIEW 6i, 7.0, and 7.1 and the LabVIEW 7.0 RT Engine does not work with TestStand 3.1. It seems only the LabVIEW 7.1 RT Engine will work with TestStand 3.1. But I don't have a LabVIEW 7.1 development license (not sure how the 7.1 VI's came to be, before my time). I've also thought of using standalone LabVIEW applications but the only license I have for Application Builder is from LabVIEW 6i PDS from the Developer's Suite. If TestStand 3.1 is suppose to work with any LabVIEW RT engine then I'm doing something wrong.
2. Run a LabVIEW Development/Deployment license with a TestStand Development/Deployment license. This is the most expensive method but the easiest to implement.
3. Run a LabVIEW FDS and a TestStand Deployment license on the production machine.
A finally question, does NI make available a TestStand Run-time Engine that is available as a free download, similar to the LabVIEW Run-Time Engine?

Data Socket Server installation on Labview run-time PC

How do I install data socket server on a PC with Labview run-time licence only? Is it part of the installer?

Yes, this will install entire DataSocket software. This includes: DataSocket Server, Manager, and Help.
Zvezdana S.

DSN as part of deployment

Hi Everyone,
I'm doing a database application for our shipping department.
It's a simple product location tracker, I want the deployment to function so that no manual intervention is required.
Is there a way that I can include the ODBC DSN in my labVIEW program deployment?

Well you could use the ODBC connection string. A DSN basically is simply a name to a registry location that contains the various settings needed to connect to the database. You can skip the entire DSN and directly pass the full ODBC connection string to the SQL Open function.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Zedboard Xilinx Zync 7000 interface using labview

Hello,
I am doing my thesis in Zedboard for developing an DDR3 memory test and verification. For that I need to implement an LabVIEW dedicated Graphical User Interface base on NI Measurement Studio.
Topic is : Szudy of Algorithmic test setup for DDR3 SDRAM with a Xilinx Zynq SoC.
Here i have done my algorithm in Xilinx SDK. But I need to make a GUI using labview. Which helps to execute these programs. Please let me know how I can do this.
1. Or is it possible to directly access the Zynq SoC using Labview. If yes how?
2. Or if I need to do the coding in Xilinx SDK and How I can run this code using Labview?
Please give me an detailed reply. Since I am new to labview. I m not understanding how to start with. If you have any example design please share with me.
Thanks & Regards,
Nithin Ponnarasseri
Solved!
Go to Solution.

No you can't develop directly in LabVIEW and deploy that program to the Zync board. NI has their own Zync based hardware platform (cRIO and myRIO) but the tools to target those boards are specific to the NI hardware implementation and won't work with other hardware. Developing an interface for another hardware platform is a lot of work and needs to be adapted for every single flavor of a new hardware platform. And NI does not support this for other hardware.
So your option will be to develop an application with the Zync SDK for the Zync ARM controller and supply some form of communication interface (serial port, TCP/IP, or similar) in that application over which you can send commands from LabVIEW to your embedded application.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

LAbview RT Deployment licence

Similar Messages

Maybe you are looking for