Compare Labview 11.0 with Labview 8.6

Dear All
Can any one give me a crisp comparison between Labview 11.0 and Labview 8.6 in terms od adding new feture and other things.
Vikas

http://www.ni.com/labview/whatsnew/features/
Was that so hard?

Similar Messages

LabView TestStand interoperability with LabView runtime adapter

I would like to get some background information on how the interoperability of LabView and TestStand works.
We are using LabView steps mainly for some minor tasks in TestStand projects.
We do not use the regular deployment way as proposed by NI, but simply use one or more VI folders from which we reference LabView steps.
Deployment is done by copying the whole TestStand/LabView folder structure to the target machine.
We use the LabView runtime adapter within on our deployed systems.
We never mix LabView versions within one project.
Now, we frequently face the situation that the exact same project structure on two different machines has problems with the LabView steps.
So one changed VI runs on one target machine while the other after copy deployment is broken. Due to the same project structure and the virtual drives the paths must be the same.
A mass compile usually solves the situation.
So this is mystery number 1.
Today, I had the same problem, however I did not mass compile the full VI folder but simply some folders which I assumed had changed.
One VI which was referenced by TestStand was not mass compiled and was declared as broken by TestStand.
All I did was opening the broken VI in LabView Development System and nothing was obviously changed by LabView.
I closed the VI and pressed the Reload VI button on the TestStand step and the VI was working again, however the sequence file now had changed somehow (* at file name).
Another phenomenon:
An existing project on a machine was running with a certain user.
After switching the user, the VI steps of the project were suddenly broken.
My questions?
1) Why do VIs which run in the development system flawlessly become broken in the runtime?
2) Does the runtime use different search paths than the development system?
3) What kind of information does the mass compilation produce and where is it stored.
4) What kind of information does TestStand store along with the VI?
5) Is there a way to diagnose the problem with the runtime adapter ? With the runtime adapter I cannot open the VI to see what is the problem and in the developer mode it works.

First, to clarify a few points:
1) It is not necessary to use a workspace for TestStand deployments. You can specify a directory of source files for a TestStand deployment.
2) TestStand licensing should not be affecting this issue in any way. TestStand licenses do not have any impact on LabVIEW VI execution in TestStand.
Thorsten,
The issues you are describing are likely being caused by the LabVIEW VIs needing to be recompiled. The runtime engine is not able to recompile VIs, but the LabVIEW Dev System can, so this explains why you are able to execute again after opening the VIs in LabVIEW Dev. it also explains why a mass compile fixes the issue.
There are a variety of reasons why this could be happening. One scenario that could cause this to happen is that you make a change in one VI, but the change causes a second VI to need to be recompiled. This could cause a problem if you redeploy only the VI that you changed, because it will not be able to work properly unless the second VI is recompiled, which cannot be done by the LabVIEW RTE alone. This can happen because the LabVIEW compiler will optimize certain operations in the compiled code depending on where data is used--for example, the compiler will try to avoid allocating a copy of an array if it does not need to be accessed by multiple pieces of code at the same time. As you can imagine, this type of optimization might be appropriate for one version of your code, but might not be appropriate if a subVI changes such that it needs access to the array in parallel with the rest of the code.
The specific example I mentioned is called the Inplaceness Algorithm, and is described along with much more information about the LabVIEW compiler in this whitepaper. This might help explain the reasons a LabVIEW VI would need to be recompiled.
One potential solution to your problem that would allow you to keep your current deployment method would be to use packed project libraries (PPLs). You could have multiple PPLs for different parts of your code that you want to be able to update individually, which would allow you to make small changes to your codebase without having to deploy the entire set of code at once. A PPL is a self-contained set of compiled code that does not change, which should avoid the recompile issue from occurring.

Qual a diferença do LabVIEW FPGA e o LabVIEW REAL- TIME?

Hello,
Could anyone help me? This question arose in my work and could not answer. Does anyone know tell me?
Thank you.
Solved!
Go to Solution.

Olá,
Com o LabVIEW FPGA você programa diretamente o chip FPGA presente no chassis cRIO, placas da NI Série R e single Board RIO. Você programa as E/S diretamente no chip, sendo assim uma programação de mais baixo nível. A grande vantagem do FPGA é o "paralelismo real", o que garante altas velocidades na execução das rotinas programadas.
Assista ao webcast Introduction to LabVIEW FPGA
Com o LabVIEW Real-Time você desenvolve aplicações que são críticas em relação a "tempo". Chamamos de aplicações "deterministicas". A idéia é que, se você tem uma rotina que deve ser executada em um tempo determinado, a diferença entre o tempo real e o que você programou seja o menor possível. Aplicações em Computadores comuns não são deterministicas, pois enquanto o LabVIEW executa uma certa rotina programada, o Windows está executando outras tarefas, monitorando a utilização de periféricos, atualizando a tela, etc.
Real time não significa "Velocidade", mas "Confiabilidade".
Assista ao webcast LabVIEW Real-Time: Graphical Development, Hard Real-Time Performance
Hello,
With LabVIEW FPGA you program the FPGA chip itself. The FPGA chip is found into cRIO chassis, NI R-Series Boards, and NI Single board RIO. You program the I/O directly in the chip, so we consider this as a low level programing. The main FPGA advantage is the "Real Paralelism", which guarantees high speed execution programming.
Whatch Introduction to LabVIEW FPGA webcast
With LabVIEW Real-Time you develop called "time crictical" or "Deterministics" applications. In case of you routine must be executed in a specified period of time, the difference between the real time execution and the time you programmed is as low as possible. Commom computers programming are not deterministic, because in the meantime of executing a certain programmed routine, the OS (e.g. Windows) is running other appication tasks, monitoring peripherals like mouse and keyboard, uptading screen, etc.
Real-Time doesn't mean "faster" but "reliable".
Watch LabVIEW Real-Time: Graphical Development, Hard Real-Time Performance webcast
I hope the information helps you!
Best Regards
Felipe Flores
Engenharia de Aplicações
National Instruments Brasil

Integrating TortoiseSVN with LabVIEW's Compare tool

I’m trying to set up the TortoiseSVN Diff tool, as described:
https://decibel.ni.com/content/docs/DOC-12175 and
http://digital.ni.com/public.nsf/allkb/3BEC521972301FF2862576EA00609CA6
To configure TortoiseSVN to use LabVIEW’s compare tool I added the following for “.vi” file extensions:
"C:\Program Files (x86)\National Instruments\Shared\LabVIEW Compare\LVCompare.exe" %mine %base -nobdcosm –nobdpos
The links above tell you use “Program Files,” but on my system the LVCompare.exe is located in my “Program Files (x86)” directory.
When I try to run the diff tool (right click on the file in question -> TortoiseSVN -> Diff with previous version), I get the following error:
I cannot get the LVCompare tool to work with the command prompt either, as described:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configlvcomp_thirdparty/
I did notice that it mentions the Compare tool is only available with LabVIEW Professional Development System. Does this apply for using it with TortoiseSVN as well? I am running LabVIEW 2011 Full Development System on Windows 7 (64 bit). The version of TortoiseSVN I am using is: TortoiseSVN 1.7.6, Build 22632 - 64 Bit , 2012/03/08 18:29:39 Subversion 1.7.4.
Any help getting the LVCompare tool integrated with TortoiseSVN to work would be greatly appreciated!
Thanks!
Lauren

Lauren_CPC wrote:
I cannot get the LVCompare tool to work with the command prompt either, as described:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configlvcomp_thirdparty/
I did notice that it mentions the Compare tool is only available with LabVIEW Professional Development System. Does this apply for using it with TortoiseSVN as well? I am running LabVIEW 2011 Full Development System on Windows 7 (64 bit). The version of TortoiseSVN I am using is: TortoiseSVN 1.7.6, Build 22632 - 64 Bit , 2012/03/08 18:29:39 Subversion 1.7.4.
Yes it does. LVCompare is only a simple wrapper executable that eventually tries to run a VI in the LabVIEW installation directory. And this VI will not work if the LabVIEW installation is not licensed as Professional Development system.
Note to the AEs: In the second link of Laura's post, it states incorrectly: Primary Software: LabVIEW Development Systems>>LabVIEW Base Package
This is completely contradictory to the note in the last link, that states that the Professional Development System is required. A documentation correction request seems in order.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How can I create a scene and move 3D models in INSIGHT with Labview?

Hi!
I need some help in doing a LabView application. What i have to do is controlling a 3D model represented in Insight with Labview. Something similar like the six-axis-robot example. I follow the insight configuration wizard, but nothing moves. Comparing the ".cis" files in my program and the one from the six-axis-robot, i found that in the six-axis-robot file contains something called localsystem and the one made by me, doesn't. Can be this the problem? How can I make it work? I would need some kind of step-by-step response, because i'am a beginner with Insight and 3D models. Thanks in advance!
Regards!
Juan

Thanks for the advice!
I'm actually finding the next problem. Although in my VRML file the objects are defined separately in a jerarchy tree, I can't move(rotate, translate) each object individually. I have noticed that when i define a new local system and asign it the points of the object i want move in the way you explain (right click, and then dragging the points to the new local axis), the movement of this object is dependent of the other local systems i have defined for other objects , specially if the slave nodes of the .cis file has a lower numeration than the object i want to move. The fact is, the movements assigned , for example to the nodes 1 to 100, will affect to the rest of the nodes if i also define for the rest of the nodes other movements. How can i solve this? I send you my .cis file, just in case my explanation is not enough clear. In this file you can see that movements assigned to nodes 1 to 4078, will also affect to nodes 4079 to 7168, and what i would like to do is define a movement for each obeject independently.
Thanks again!
Attachments:
ring.zip ‏2 KB

NI-Motion with Labview 5.0.1

Hi,
I'm trying to setup my pci-flexmotion-6c board under Labview 5.0.1 on a
Windows 98 box. When I go to the recommended drivers page on NI.com it
directs me to the NI-Motion 5.0.1 driver. When I try to install the
software on my system, it only seems to provide drivers for Labview
5.1, not Labview 5.0. Help!
Rich_N

Hello Rich,
You are correct that Motion 5.0.1
installs with 5.1 or 6.x. This is
because this version of our motion driver was released around the same time as
LabVIEW 6.1; therefore it provides support for the three most current versions
at that time. To use this hardware, you
would need to use one of these three versions of LabVIEW. We do offer comparable current versions of
software and hardware particularly the 734x series controllers which can be
found at Motion Hardware. If you would like to continue using LabVIEW
5.0 you could either look into using our older ValueMotion drivers or create a
function library that you can call. Also in order to prevent future complications,
I would like to inform you that the pci-flexmotion-6c board is not compatible with
NI-Motion 5.2 driver and later. I hope
this answers your question. Please let
us know if you would like further clarification or assistance.Regards,
Vu D
Applications Engineer

Replacing a PLC with LabView Article

I just read the article "Replacing a Programmable Logic Controller (PLC) with LabVIEW and FieldPoint for Composting Plant Automation ". I am very concerned by the author's lack of knowledge about current PLC's. This article does not fairly compare the two platforms and is not accurate. For example, the author states that 100 msec is a typical response time for a PLC. This is absurd. Today, even low end PLCs can achieve responses time below 10 msec and high end PLCs even as low as 1 msec. It all boils down to specifying the right hardware for the application. One real danger the author does not address with building a "soft PLC" is the potential for the I/O not to fail to a safe condition if the operating system (Windows) lock
s up. This can be disastrous and unsafe for many control applications. I would suggest any reader that is seriously considering replacing a PLC in an industrial environment with a "soft PLC" watch out for this potential shortcoming. Readers can visit www.isa.org to find additional information on this issue.
I would not dispute that for a pure data acquisition application LabView can offer a superior solution. The safety conern can be mitigated if there is a "hard wired" safety system that has been properly designed. However, many times the PLC may provide safety shutdowns that depend on its true deterministic operating system and high reliability.
I hope that readers will not interpret this as a slam against LabView but as encouragement research this issue further from a different perspective.

I can see from your comments that you have a firm grasp of the PLC/vs PC concept, and agree with your comments. I have been an instrumentation developer/integrator for 36+ years, and have first hand experience with the situation(s) to which you refer. I have found the optimum solution has been a combination of PC/MMI software and PLC hardware. I have many such systems up and running in different industries, and have found this to be the best overall solution. Let the PC do what it does best(MMI display, complex calculations and decision making), and the PLC what it does best(solid deterministic control, with a non-windows operating system). I usually use an OPC server for communication between the two units, and with proper software design on both ends,
and a hardwired E-Stop system, excellent overall opertion/safety is achieved.
Your comments should serve as good stimulus for other developers.
Dave

Webcam interface with labview

Hello all,
I need to interface webcam with labview 2011,
My requirement is as follows,
1. Capture the image read by webcam using labview.
2. Store it in local harddisk
3. Compare it with standard image stored in PC and decide whether read image is OK or not.
I am completely new to IMAQ and went through forum also. Can you tell me what are the steps to do this, how to getting started. What software I need to install for this,link and which webcam is good for this.
Thanks
Kudos are always welcome if you got solution to some extent.
I need my difficulties because they are necessary to enjoy my success.
--Ranjeet

1. If you are using a webcam, ensure that the camera is compatible with DirectShow, and that the camera driver is installed and functioning.
2. You will need to install the Vision Acquisition Software. The software features the activation-based NI-IMAQdx driver for acquiring from DirectShow-compliant devices. A license for this software is included with all NI vision hardware and all NI vision software licenses, and is also sold separately for applications that do not require image processing or specialized hardware.
3. I am not sure how you are 'comparing' the acquired image with the image that is stored in the harddisk. But, if you want do machine vision & image processing, then you will need the Vision Development Module. In general, VDM functions are to be used for post processing images. Some example functions are: pattern matching, particle analysis, edge detection, thresholding, histograms, and optical character recognition. This module includes the VAS that was described earlier.
4. There are lots of examples that are shipped with the software to help you understand and achieve what you are trying to do.
Here is a good article that describes the different vision software provided by NI:
What is the Difference Between Vision Software VDM, VBAI, and VAS?
NI Vision Software Comparison
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Labview dsp module with tidsk 6713

Hi,
I'm working with TI DSK6713 board on Labview 8.6.1 version with the Labview dsp module 8.6.
The idea is to delegate computationally heavy FFT operation to DSP processor computing it many times in a loop.
As FFT is tailored for DSP and, in fact, Labview DSP tool has build-in FFT module, it should operate much
faster on DSP rather PC. So I expect to have acceleration here, and I don’t see that so far.
Does anyone observe performance accelaration with labview dsp compared to labview only performance ? What are the tools for measuring timing statistics on labview dsp ?
Thanks.

Hey Salander,
I am an applications engineer here at National Instruments and would like to get a little more information from you to see if I can help you with your issue. I am not particularly familiar with the TI DSK6713 as it is a third party product. It seems to me like you think that since the TI DSK6713 has a DSP processor it should hypothetically run LabVIEW DSP faster than your PC. I am wondering if the TI DSK6713 is fundamentally different than any other board.
Here is a link to the manual for LabVIEW DSP that might have some helpful information for you that could shed some light on your issue:
http://digital.ni.com/manuals.nsf/websearch/AB1AC84DD6DD3CEF86257456006B1FF0
Good Luck,
Doug B
Applications Engineer
National Instruments
Applications Engineer
National Instruments

Analog filtering with Labview versus electronic filtering

I have been into signal conditioning with LabView. I want to discuss with you guys software conditioning versus hardware coditionin, especially filterinf (i.e. bandpas filtering) an analog signal. Is there anybody out there who uses LabView for sotware conditinin and/or who compared software conditioning (implementing bandpass filter in Labview) to hardware conditioning (filter the signal electronically before data acquisition)? How satisfactory are LabView results?
Thank you guys. I am looking forward to reading your ideas.

If all your signals are well within the sampling rate of your digitizer, digital filtering is OK. Analog filtering is required if the raw signal contains frequcies that are higher than the Nyquist frequency, because they would show up aliased to lower frequecies and no digital filter will later be able to differentiate them from a real frequencies.
LabVIEW Champion . Do more with less code and in less time .

BASYS 2 Spartan3 interface with labview

Hi I am new to xilinx. but unexpectedly i am in a situation to work with BASYS 2 Spartan3 board from digilent.
Please help me to interface BASYS 2 Spartan3 with labview 2012.
Thanks in advance.

1. If you are using a webcam, ensure that the camera is compatible with DirectShow, and that the camera driver is installed and functioning.
2. You will need to install the Vision Acquisition Software. The software features the activation-based NI-IMAQdx driver for acquiring from DirectShow-compliant devices. A license for this software is included with all NI vision hardware and all NI vision software licenses, and is also sold separately for applications that do not require image processing or specialized hardware.
3. I am not sure how you are 'comparing' the acquired image with the image that is stored in the harddisk. But, if you want do machine vision & image processing, then you will need the Vision Development Module. In general, VDM functions are to be used for post processing images. Some example functions are: pattern matching, particle analysis, edge detection, thresholding, histograms, and optical character recognition. This module includes the VAS that was described earlier.
4. There are lots of examples that are shipped with the software to help you understand and achieve what you are trying to do.
Here is a good article that describes the different vision software provided by NI:
What is the Difference Between Vision Software VDM, VBAI, and VAS?
NI Vision Software Comparison
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Reading teststand variables with labview??

I'm trying to create a vi that will read the uut serial number from teststand and compare it to a second scan from the operator. Is there a function I can put on the block diagram to read the teststand variable? I've read the using teststand with labview but it's still unclear how to do this. Could I just pull the serial number from the UUT dialog that the user starts the test with instead? The other problem is this is a 4 uut test panel so I need to make sure I compare the correct uut serial number info. Any ideas?

The name of the variable is RunState.Root.Locals.UUT.SerialNumber. When you create your VI, have a string control that you pass this in. This is done when do the Specify Module as shown below. Here's an example sequence and VI as well. You can also make it a bit more complicated by using the sequence context and the TestStand Get Property Value function.
Message Edited by Dennis Knutson on 05-01-2007 04:16 PM
Attachments:
Specify Module.PNG ‏29 KB
TestStand Example.zip ‏9 KB

Strange math-problem with LabVIEW 7.1

Hello!
I am using LabVIEW 7.1 and I came to this strange math-problem. Could it be that it is a problem of LabVIEW 7.1?
Ok try this with LabVIEW 7.1:
open a new VI
place a subtract-VI (pallet numerical) on the block diagram and try to subtract 0.2 from 1.6
place a less-VI (pallet compare) on the block diagram and wire a numerical constant 1.4 to input x
wire the result of the subtraction to input y of the comparison
place an LED to the output of the comparison
and start this.
What does it say?
The LED should turn on and this means here that 1.4 would be less than 1.4 .
But I would have expected that 1.4 is not less than 1.4 .
This works also if you add or subtract upto 0.2 to/from the values 1.4 and 1.6 (or equivalent with 0.2) .
If you change the inputs of the comparison then the result is as expected and 1.4 is reported not to be less than 1.4 .
If you compare two constants with the same value 1.4 you will not get the same strange result.
Does anybody have an explanation for this?
Espelkamper

Hello,
For floating point math: Rounding to multiples of 0.1 is problematic as
those numbers are infinite fractions in base2 representation...
So maybe you should change your numbers to integers using fixed point math. If all your input values are in the range of 1.4 to 1.8 you can multiply by 10000 and round to next integer. Then do your comparison on that integer (there's also an 'InRange' function in the comparison palette).
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Configuring ClearCase with LabVIEW SCC

Hi,
I am developing VIs with LabVIEW pro. We are using ClearCase for SCC and I would like to configure LabVIEW with ClearCase.
VIs are stored under vobs on a world wide network.
Does anyone know how I can do?
Second question, is it possible to configure ClearCase to use the LabVIEW pro compare tool? This will give ClearCase the capability to compare VI versions.
BR,
Pascal.

Hello,
ClearCase is not supported by LabVIEW, if you want to use a SCC, you can perform this task with the following SCC providers: Perforce and Visual Source Safe and Built-in.
Built-in SCC is recommended only for small projects and is available in LabVIEW at no additional cost. “Microsoft Visual Source Safe” and “Perforce SCM” are complete SCC tools that are fully integrated into LabVIEW but must be purchased from the corresponding vendor.
You can find more information at the following link:
http://zone.ni.com/devzone/conceptd.nsf/webmain/69ea27204d24f78586256e2400773abe
If you really want interfacing LabVIEW and ClearCase, VI Engineering can perhaps help you:
http://zone.ni.com/devzone/conceptd.nsf/webmain/ddaa22e726919f118625700000009ca9
Best regards
Alexandre D
AE, National Instruments

Open and close multisim contact with LabVIEW

Can I open and close multisim contact with labview and read the receptor estatus (p.e. lamp)?
Thanks.
Attachments:
Dibujo.JPG ‏13 KB

Hi Guddan,
I created a RFC having a query which is taking a long time to execute. So i want to close RFC connection with portals which is via java connector(JCO) before that query and open the connction again after that query.
I guess i will need to understand your requirement a little more in detail, as i understand you have an RFC which has a query within to fetch some data and is taking a long time to do so. In the meantime you don't want to keep the connection open?
My question would be, Is the role of this RFC to only execute the query and fetch the data or does it do something else?
If it does other things and these are independent of the query execution, then you can span a parallel call within the RFC to execute the query and in the meantime the RFC does the other things (or vice versa) hence reducing the overall time taken.
If the sole purpose of this RFC is to execute the query, then you will not be able(i mean to say there is no simple and direct way of doing this) to close the connection after the Query is started and re-establish the connection after its execution, for a simple reason that - how will you know if the query has completed it's execution, so that you can establish the connection back.
Alternate solutions, make this a two way asynchronous call, 1) You invoke the RFC asynchronously and close the connection, the RFC in turn will execute the query and transfer the data to JCO via another RFC call.
If this needs to be a synchronous call, then you will need to optimize the query to its best.
Regards,
Chen

Compare Labview 11.0 with Labview 8.6

Similar Messages

Maybe you are looking for