Instalacion en Linux NI LabVIEW 2013

Buen Día.
Estoy intentando, Instalar el LabVIEW 2013 desde un CDROM original proporcionado por mi institución educativa,
tengo sistema LUBUNTU 14.04 pero no logro ni montar el CD mediante "apt-cdrom add" me gustaria recibir
información sobre la manera de instalar.
Soy novato en linux, Gracias.

Que tal LuisJaquez Buenos Días:
La versión de LabVIEW para Linux no soporta oficialmente Ubuntu ni LUBUNTU. Te envío una páagina donde se mencionan los sistemas operativos soportados y también los que están soportados en Linux.
http://www.ni.com/labview/requirements/
http://www.ni.com/labview/os-support/
http://digital.ni.com/public.nsf/allkb/4857A755082E9E228625778900709661
Algunos de nuestros usuarios han logrado instalarlo en UBUNTU pero por el momento no tenemos nada documentado si alguien ha hecho pruebas con la versión Light. Te envío la comunidad donde se ha realizado esta instalación y donde puedes apoyarte de algunos de los usuarios de Linux pero nosotros no podemos ofrecerte ayuda ya que se encuentra fuera de los sistemas operativos soportados.
https://decibel.ni.com/content/groups/linux-users
https://decibel.ni.com/content/docs/DOC-22321
Cualquier otra pregunta estoy a la orden
Que tengas un Excelente día
Juan Arguello
National Instruments México y Latinoamérica
Applications Engineer

Similar Messages

Install LabVIEW 2013 on Scientific Linux 6.4

Has anyone successfully installed on SL6.4? I install and no response - try to start using icon but no errors or slash screens. Did put the 32 libc2 on the machine. It asked for kernel sources, but for 64 bit?. What is correct?
Thanks,

Zander,
I have not installed LabVIEW 2013 on Scientific Linux 6.4 before, but I will see if I can help you out. First did you install LabVIEW 2013 32 bit or 64 bit? Second does just the LabVIEW shortcut on the desktop not work (icon) or can you just not load LabVIEW at all?
Thanks

Can I use Labview 2013 on 64bit and 32bit PC interchangeably?

Hello,
I am currently running Labview 2013 base package on Windows 7/64 bit laptop PC, which is not permanently kept in the lab. I need to buy a 32-bit desktop PC to operate a non-Labview application, but, it would be very convenient to use the new 32-bit machine to run Labview also, since it WILL BE permanently in the lab. Then, I wouldn't have to be connecting/disconnecting the laptop in the lab every time I am doing system development.
Can I load my version of Labview 2013 on a Windows 7/32-bit desktop system and write/run VIs the same way I currently do on my Windows 7/64-bit laptop?
If the 32-bit and 64-bit are interchangeable, then, I would get a higher end 32-bit system. If they are not, then, I will get the cheapest 32-bit system available, and dedicate it to the non-Labview application.
Thanks,
Dave
Solved!
Go to Solution.

dav2010 wrote:
I am currently running Labview 2013 base package on Windows 7/64 bit laptop PC, which is not permanently kept in the lab. I need to buy a 32-bit desktop PC to operate a non-Labview application, but, it would be very convenient to use the new 32-bit machine to run Labview also, since it WILL BE permanently in the lab. Then, I wouldn't have to be connecting/disconnecting the laptop in the lab every time I am doing system development.
You seem to be confusing a few things.
A typical PC can run either a 32 bit windows or 64 bit windows 7. The 32 bit version can only support up to 4GB of RAM, while the 64 bit does not have this limitation.
Both versions can run 32 bit applications and most applications are still 32 bit. (In contrast, a 64 bit application cannot run under a 32 bit OS).
With respect to LabVIEW, a typical installation uses LabVIEW 32 bit, independent of the bitness of the OS. (There are very few specializes scenarios where 64 bit LabVIEW is even useful). I assume that your LabVIEW is 32 bit on your current 64 bit PC. Is this assumption correct?
With the current RAM prices, and keeping memory upgrades in mind, it does not make a lot of sense to even install a 32bit OS (except maybe on a cheap netbook). 64bit Windows can run 32 bit applications just fine. Are you sure that your special application is an exception here?
In any case, VIs are freely interchangeable between LabVIEW 32 and 64 bit (and even mac and linux). When moved to a new platform, they simply recompile automatically.
dav2010 wrote:
Can I load my version of Labview 2013 on a Windows 7/32-bit desktop system and write/run VIs the same way I currently do on my Windows 7/64-bit laptop?
If your version is Labiew 2013 (32 bit) (and I assume it is!), you can run it on both systems. If you are currently using LabVIEW 64 bit (unlikely), you need to install LabVIEW 32 bit on the 32 bit machine. Even in that case, theVIs are fully interchangeable.
LabVIEW Champion . Do more with less code and in less time .

Windows 8 and Labview 2013 FPGA

I installed Labview 2013 including the FPGA design suite on a Windows 8 (x64) host. I was surprised to see Windows 8 on the list of supported OS as I was aware that up to this day no Xilinx design suite supported Windows 8.
But as a matter of fact it didn't took long before I hit:
ERROR: Simulator:861 - Failed to link the design
following this tutorial while clicking on check syntax (using one of the VHDL file provided with the tutorial). The error is clearly linked to a lack of Windows 8 compatibility from the XIlinx tools running underneath. Is there a known workaround? Thanks.
Solved!
Go to Solution.

That I could do but Linux is not listed here ... but Windows 8 is listed as supported for the farm server and not for the development environment. Isn't is the other way around? On top of that it looks like we should read GB instead of MB for the farm toolkit.

Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop).

Hi all. Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop). This really slows things down! Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini. Has anyone seen similar, and/or any hints towards a solution?

Jeff-P wrote:
As a side note, LabVIEW.ini is a file that gets generated by LabVIEW when it is launched if the file does not exist. So if you are missing the 32-bit ini file, launch 32-bit LabVIEW and that file should be created.
I thought that the message: "Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini" might indicate that the labview.ini file cannot even be created... strange...
LabVIEW Champion . Do more with less code and in less time .

Report Generation Toolkit labview 2013 64bits?

Muy buenas tardes.
Estoy buscando el Report Generation Toolkit para labview 2013 64bits, lo he buscado pero no logro encontrarlo y con este mismo pero de 32 bits me marca error al instalarlo.

Hola Antonio,
Intenta con esta liga : http://www.ni.com/gate/gb/GB_EVALTLKTREPGEN/US
Espero que por aqui lo puedas descargar,
saludos
Erwin Franz R.

Report Generation Toolkit failure with Win 7 and Labview 2013

I recently had my computer updated to Windows 7 and am now seeing a problem with the Report Generation toolkit (version 2013) when working with Excel files. If I try to run the New Report.vi with report type Excel selected I get error -2146777998. Doing the same thing with Word selected eventually opens Word, although this takes about ten seconds, but it does not generate an error. Selecting Standard Report or HTML also run without errors.
I've researched this error on line but I keep ending up .NET and C# forums where everything goes over my head. Has anybody got any suggestions?
Solved!
Go to Solution.

I found the solution to this particular source of error code -2146777998. There are two template files that reside in C:\Program Files (x86)\National Instruments\LabVIEW 2013\templates\Report by the name of MSOffice_RGT_Template.dot and MSOffice_RGT_Template.xlt. The problem came down to that these templates got corrupted somehow during the fresh install. As soon as I replaced them with versions from another machine the problem disappeared.
Just as a side note, I discovered the problem by kicking off the MS Office Report Express vi and out came a much clearer message that aimed me at the templates. Not quite sure why that message isn't echoed into the individual subvi's on the pallette, but life is a mystery.

Labview 2013 report generation toolkit word 2010 insert table problem

Hi,
I am currently evaluating LV2013 with respect to the report generation toolkit for use with word 2010. My Vi/program won't insert the correct table and gives me an error message. see below:-
Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table.vi->NI_Word.lvclass:Append Text Table to Report.vi->Word Table save.vi
I have since run the following word example.vi provided by NI within LV2013 office examples:- Growable table.vi. this gives me the same error!
Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table.vi->NI_Word.lvclass:Append Text Table to Report.vi->Growable table.vi
It would seem that regardless of my own Vi there is a fundamental problem in the office example vi.
I have found examples of a similar problem in LV2011/2012 but the work around code doesn't seem to match the LV2013 vi's code for a direct replacement.
Can anyone help/shed some light on this?
Thanks in advance,
Dan.

Because the upgrade of Word from 2007 to 2010 I needed to upgrade an existing application from LabVIEW 2009 to 2013. This didn't work because of the insert table error. I discovered that the problem is the vi called "Word_Insert_Table.vi" located in the ..Program Files (x86)\National Instruments\LabVIEW 2013\vi.lib\addons\_office\_wordsub.llb. There is a "Cut" command implemented, this command removes the created cell instead of clearing it. Therefore the table will be filled half and then returnes with an error. I have removed this command. I have posted the changed vi (LV 2013).
Attachments:
Word_Insert_Table.vi ‏30 KB

How can I build a LabView application that uses the 2012 runtime, on a development system with LabView 2013 or 2014 installed?

I need to build a LabView application .exe to run with the 2012 Runtime, for legacy support. I currently have LabView 2013 installed on my development system, and have 2014 available. How can I build an application that uses the 2012 runtime on this development system? Do I have to downgrade to 2012? Thank you.

We have existing customers that have installed our application that was originally built with 2012 (provided by a contractor that is no longer available). Due to IT regulations, it is far easier to update these customers by simply replacing the .exe file, than creating an install that their IT department must run.
If I have to downgrade to LabView 2012, where can I get the installation for this?

LabVIEW 2013: An error occured trying to load the assembly

Hey all,
I'm trying to load a .NET 4.5 dll into LabVIEW 2013.
When I place any of the .NET VIs and try to select the one I'm after it says "An error occured trying to load the assembly" and won't let me load it.
I also tried importing the dll, but that gave errors too.
It's defintely a .NET 4.5 dll as the .NET reflector gives me
[assembly: ComVisible(false)] [assembly: TargetFramework(".NETFramework,Version=v4.5", FrameworkDisplayName=".NET Framework 4.5")] [assembly: SecurityRules(SecurityRuleSet.Level1)] [assembly: SecurityPermission(SecurityAction.RequestMinimum, SkipVerification=true)]
To try and get around the import issue, I added the following to my LabVIEW.exe.config file
<?xml version ="1.0"?>
<configuration>
<runtime>
<loadFromRemoteSources enabled="true" />
</runtime>
</configuration>
but it made no difference.
Any suggestions? All the things I've read so far are for 2010.
Solved!
Go to Solution.

Hornless.Rhino wrote:
Wart wrote:
I had the same issue a while back. Unfortunately mine magically resolved itself, but I made a post with what I'd been reading and got a reply with another suggested link. It sounds like you've gone down the same road, but I figure every little bit helps:
http://forums.ni.com/t5/LabVIEW/Error-Loading-NET-Assembly-in-2013/m-p/2521098
Thanks.
Hopefully mine will resolve itself too. LV2013 is meant to support the newer stuff without me having to mess about.
We shall see...
So far no dice.
It's really bizarre. It works with sample c# code in visual studio (see link below), but for some reason LabVIEW doesn't like the dll (tried both LV 2012 and 2013).
Sample code (not mine) is available at http://elbruno.com/2013/12/01/kinectone-hello-world-with-kinectsdk-v2-body-count/

Conversion of VIs from LabView 2013 to 2011

Hi,
I would be grateful for conversion of zipped VIs from LabView 2013 to 2011.
Thank You,
Michal
Solved!
Go to Solution.
Attachments:
main VIs.zip ‏38 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Attachments:
main VIs 2011.zip ‏27 KB

FPGA FlexRIO SCTL LabVIEW 2013 Compilation Problems

Hi,
I have an FPGA FlexRIO (7962R) VI that interfaces to a 6585 LVDS board that consists of a SCTL running at 200MHz and using a Xilinx Coregen FIFO.
In LabVIEW 2012 using Xilinx 13.4 I have had no problems compiling this at 200Mhz, but in LabVIEW 2013 using Xilinx 14.4 I am unable to get it to compile reliably about about 170MHz with absolutely no modifications to the code.
The Xilinx FIFO is probably irrelevant as I have tried cloning the VI and removing the FIFO and still get the same problem.
Any ideas, things to try or solutions?
Thanks,
Dave
David Clark
CLA | CTA
CLA Design Ltd
Hampshire, England

Have you tried optimising the Xilinx compiler for Timing?
You can't modify the Xilinx compile options of a FlexRIO target.
In LabVIEW 2012 using Xilinx 13.4 I have had no problems compiling this at 200Mhz, but in LabVIEW 2013 using Xilinx 14.4 I am unable to get it to compile reliably about about 170MHz with absolutely no modifications to the code.
What compile error are you getting? Does not reliably mean that sometimes it does compile correctly? Can you upload a simple example of a piece of code that works in 2012 but not 2013?
National Instruments
FlexRIO Product Support Engineer

DAQMX vi files missing in Labview 2013

I try to open this file slinger-logger.vi [see attachment], but I can't open it, because it is missing files such as DAQmx Clear task.vi
I already tried to install several versions of DAQmx (14.1, 9.9, 9.4):
http://digital.ni.com/public.nsf/allkb/B0D5630C0A50D5C6862578E800459248
But I couldn't get the file working without those missing vi errors. Can anyone get this file working in Labview 2013? Or Labview 2012?
Attachments:
Slinger-logger.vi ‏70 KB

kihans wrote:
I already tried to install several versions of DAQmx (14.1, 9.9, 9.4):
http://digital.ni.com/public.nsf/allkb/B0D5630C0A50D5C6862578E800459248
But I couldn't get the file working without those missing vi errors. Can anyone get this file working in Labview 2013? Or Labview 2012?
Why do you install random version of DAQmx, especially since 9.4 does not even support the LabVIEW 2013 or 2012 versions you mentioned. You even show the link outlining that! Pick the neswest one only!
Tell us exactly what you did:
Did you install DAQmx after installing LabVIEW and did you select support for the installed LabVIEW version?
Did you reboot after installation?
LabVIEW Champion . Do more with less code and in less time .

Labview 2013 executable works only on develoment machine?

Hi all
I created an executable so as to distribute my test software but it only runs on the development machine. I have successfully distributed my executables before with labview 2012 on target machines by simply creating the .exe in project explorer and then installing the nessary labview drivers and run time engine without problems. Now I created a new test programme with Labview 2013 and I can't get my new .exe test software application to run on the target machine. Has anyone seen this type of problem before? Any assistance will be appreciated.
Thanks
Solved!
Go to Solution.

In addition to the run-time engine you are likely missing some other installers. Lets say you used RS-232 code in your EXE well now you need to install VISA run-time on the new machine. Did you use DAQ? Now you need DAQmx. Did you use NI-Scope? NI-DMM? NI-Power? NI-Switch? You'll need to install those as well.
In 2013 the process of making an installer can detect what installers you need. In previous versions you just have to know which you used and select them in the Additional Installers section.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Slow LabView 2013

Hi
I have Labview 2013 Professional Dev Sys SP1 ver 13.0.1f2 (32-Bit) and it is slow when I develop any aplication.
For example, if I have a tab control and I change to another tab, it takes about 2 seconds to change tab after I click it.
If i wire a new line, it takes 2 seconds to appear that line in block diagram, and so on.
I have a new computer Dell Optiplex 7010, i7 Processor 3.40Ghz, 64-Bit, 4Gb RAM, WIndows 7 enterprice SP1
If i run Windows task manager it shows 17% CPU usage and 2.14 GB Memory.
If I run for example, excel 2013 it does not seems slow.
Do you have any suggestions ?
Regards
Solved!
Go to Solution.

EDGAR_PLATRONICS wrote:
Hi Yamaeda:
I am not sure about mass compile. You mean rewrite code ? Or create exe file and test?
A this moment I have checked with only one Vi but it is very large. Many sub VIs and code.
Actually it worked correctly in labview 8.5 but i converted to LV 2013.
I will research about transparent borders overlapping.
Hi Altenbach:
17% is overall. 3 cores are high % than others.
The problem is at edit mode and also when I run program.
Yes I have many front panel indicators, but I do not think they have tons of data but I will double check.
When I open my VI in labview it shows 118 MB memory when running and 124MB at edit mode
By the way, last week when by mistake I moved a part of code to some centimeters below, block diagram was frozen and was been updated to new position but line by line until complete full screen. I took about 5 minutes to work normally.
I am using 2 monitors in my PC. One to display LV panel and one for LV code.
I meant Tools -> Advanced -> Mass compile and recompile your upgraded code. In the same manner a ctrl+run array will force recompile your program. It can help. Else you're down to e.g. using VI analyzer tool to find the culprit, it might be some VI that's corrupted and needs to be moved to a new VI.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Instalacion en Linux NI LabVIEW 2013

Similar Messages

Maybe you are looking for