Update of Labview

Similar Questions

• Error Code HDL with CRio RFP generation after update for LabView 2012

  Hello everyone,

  I use a CRio DP Comsoft master/slave module for my communication with a PLC system. The application worked perfectly under LabView 2011. After the update to LabView2012, I got an error message that the HDL Code generation failed. After that I've updated also the Software NI Profibus CRio in Version 1.3, but this n ' t´t solve the problem. The next step was to use the example of project code "CS_cRIO-PB_DP-MasterExample" which was delivered with the new NI CRio Profibus software. Even with this code example, the problem still exists. For detailed information on the configuration and the error message please refer to the screenshot. Any help or idea would be appreciated.

  Jürgen

  Hi Jürgen,

  I looked inside and could reproduce this error. Somehow the compiler with LV 2012 has problems with the coded 8.5.1 Subvi LV. Please use the attached VI and copy it to the following location. (\\Program Files\National Instruments\LabVIEW 2012\vi.lib\addons\Comsoft.lib\cRIO PB)

  Before do you it please close your LabVIEW.

  Then try to compile again.

  Let me know if it still does not. We are currently working on a new installer that will correct this problem.

  DirkW

• Update of LabVIEW, which updated 9.8 DAQmx. SMU-8101 to 9.4 DAQmx. Difficult how?

  I am trying to use MAX to navigate up to a DAQ SMU-6363 connected to my SMU - 8101 RT connected to my local network, but encounters an error: "error-88716 occurred at communication·entre·dispositifs·de·sante·personnels, or the possible reasons: the requested operation failed because a driver on the local and remote system versions are different."  Updated the driver for versions on both systems are the same.  "Remote system: 172.17.2.65, Incompatible driver: NI - DAQmx Device Driver 9.4.0f0.

  This problem occurred recently when I've updated LabVIEW on my development computer to the latest version (2013 f2), which updated DAQmx on my development for v9.8 machine.

  While I'm not quite there, I intend to analyze an audio signal using the SMU-6363.  I guess I'll need to have all the properly information in MAX before I have a hope of implementation in LabVIEW.

  I am now updating the drivers / firmware on the SMU help system full of communication between my development system and the SMU system and having problems.

  During an attempted 'Select all to install' for 'NOR-DAQmx 9.8.0"in the" Add/Remove software"on the SMU-8101 thanks MAX system, I get the error:

  ---------------------------

  Cannot continue following unresolved dependencies:

  Acquiring dynamic signals 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  Acquiring dynamic signals 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  Counter/Timer 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  Counter/Timer 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  NOR-DAQmx 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  NOR-DAQmx 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  Multifunction 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  9.8.0 multifunction data acquisition requires Intel 8254 x Ethernet Driver 5.0
  CompactDAQ 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  CompactDAQ 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  CompactDAQ 9.8.0 requires LabVIEW time real 12.0.0
  E/s digital industrial 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  E/s digital industrial 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  Analog output series 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  Analog output series 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  OR-653 x 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  OR-653 x 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
  SC Express 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
  SC Express 9.8.0 requires Intel 8254 x Ethernet Driver 5.0

  ---------------------------

  This dialog box does not offer an option to automatically try to download or to locate the missing packets.  Research online revealed no obvious statement upgrade for my particular case.

  I downloaded and installed v9.8 DAQmx as well as RealTime 2013 module on my development machine, and am trying to download the 4 GB device drivers.

  Is there a suggested method for the SMU-8101 software update / firmware must match that of my development machine that does not require me trying decrypt and download the packages manually?

  I've never worked with the SMU (or any remote system) with LabVIEW front and wait it would be an easy fix for someone more experienced in this.

  Owen

  AHA!

  OK, that explains it.  You actually have LabVIEW 2011 on target (SMU-8101) but you have LabVIEW 2013 on the host.  You have all the required software installed on the host computer, but there are conflicts between the required versions of the software on the controller itself compared to what you're trying to install now.  You have 3 ways to do this:

  (1) the cleaner to proceed is to keep track of all the software components that you have installed (version is not important) and then UNINSTALL all the controller software, and then REINSTALL your software (leaving MAX select the latest versions of everything).  This ensures that you'll get the latest components of software.

  (2) the 'simpler' wat to proceed is to pass by and "update" symbolizes all the components with an icon 'Bang' (yellow triangle with an exclamation point) to upgrade/reinstall the latest version found on the host - the icon of 'bang' software currently installed on the target, but more recent versions exist on the host computer.  Version does not update without user intervention, even if the other components require more recent versions.  This lump all your versions later, that's what want the latest version of DAQmx.

  (3) nuclear option - reformat your controller and reinstall all software.  This is not recommended, but this option always exists.

  -Danny

• History of update of LabVIEW

  Hello.

  I do acquisitions image with Camera Link device. Last week I was able to successfully run the screws. But today, there is something wrong. The images are not correctly. I have attached a picture for this post. In this image, you will see a red circle on the right and a gray circle with small rectangles on the left. I'm supposed to get only the red circle and not the gray circle on the left.

  Between last week and today, I change nothing to the VI. It's exactly the same thing. If my conjecture is that there must have been a software update which is to play with the acquisition.

  I already uninstalled all the updates of Windows since last week, but the problem is still there.

  Y at - it somewhere I can find a list of the updates, I made in Labview with the "Update Service OR" in order to cancel the latest updates?

  Thanks a lot for your answers.

  Best regards.

  Luke

  Luke,

  the '' gray circle '' looks more like a mirrowing during image acquisition.

  Are you sure that the physical configuration of the photo/light unit is still valid? Is there maybe some reflective material around?

  What dirt on the lens?

  Note also that the picture you attached is something that is already impaired by the functions of the vision. Is the lag already in the acquired image (as I suggest with my previous questions) or is this a result of the analysis functions?

  Norbert

• update of LabVIEW 2011 & 2012

  I currently have installed LabVIEW 2011 and runs OK on my laptop. Each quarter, it seems that we get a new series of DVD from National Instruments. Currently we have sent a package of DVDs for the first quarter of 2012.  Should I just use these DVDs and reinstall them to help on the current installation of LabVIEW or should I remove the last version before installing the new updates of the new series of DVDs. If I currently have MAX configured for a device group and the tasks that they will remain the same without new installation erase them?  Also, I have a couple of tools, like code capture tool, circular buffer, etc. installed on the laptop, they will always be in the new installation of update or I have to go back and reinstall these tools?

  double post and you marked as resolved. Why ask again?

• Not updated by Labview VI Step property

  Hello

  I am currently using 4 TS and LV 8.2 with Win7 Pro.

  I created a custom step which employs a lower Edit level.

  The lower Edit level name successfully a Labview vi, which allows the user to change the values.

  The intention is to copy the user values in the properties of the custom calling step, using the value property Value.vi of the library of Teststand.

  After that step is changed, the vi is closed and I check the step variables expected variables to be updated, but what I see in the Variables Panel does not always show the new property values of step.

  Called by the lower Edit level Labview vi receives the context of the sequence and the correct step property string name.

  Have I correctly picked the Value.vi property set to the task of updating the step of step of the custom properties?

  In addition, when the properties of the stage show the new value, the sequence containing the custom step does not indicate

  the need to save that is in front of my expectations, else how is remined user to save the changes?

  Thank you

  Gary.

  Gary,

  I recommend most often to developers to interface with the EditSubstep modules using parameters.

  For an input parameter, I pass the current values of the step variables.

  For the output parameter, I connect the same variables that they get old/new values to the EditSubstep module.

  I declare this as my EditSubstep modules normally contain a button "Cancel". If the user presses that, I simply passes the output values that the module received as input values.

  Input values are also used to update correctly orders from the EditSubstep module. Otherwise, the user would see only the default values, but not the values of that step has already been changed.

  Output parameters are important have not changed (cancel) / update the values of the step. By selecting the appropriate container, the values are transmitted with the closure of the EditSubstep, so there is no risk of running into a race condition, which could explain the behavior you're seeing.

  hope this helps,

  Norbert

• Why the activity of the screen or the screen updated slows labview code?

  Hello

  I use the Labview for quite a long time. recently I discovered that updates screen slows down execution of code. is it possible that I can eliminate the delay I get due to the screen updaes or changes?

  
  

• updated 2009 LabVIEW Mathscript

  Hello

  I developed an application in LabVIEW 8.6 who
  contains a large MathScript node. It's time to upgrade to LabVIEW 2009
  and I am facing problems in that. I have the Mathscript RT Module
  installed and enabled on my computer.

  I want to emphasize that
  the application works perfectly at 8.6. After the first performance in
  version 2009, I got 2 errors:

  -90031: "unknown output."
  variable. The variable is a string. He showed up in a red dot
  (see photo). I've never seen this before red dot...

  another
  error in another node:-20104: input parameter have at least a NaN
  element. What is an element of NaN? This error occurs in a line that looks like
  as A = median (B) where B is a vector line.

  also in this second
  node, I have a lot of output shown in the red dots, the string variables
  outputs and some double precision as well.

  What
  are the requirements to upgrade to LabVIEW 2009, insofar the MathScript
  is concerned? There are issues to be addressed? major changes, I should
  Be aware of?

  Thank you very much

  Sam

  Hi Sam,

  You can define variables by their wiring as inputs or by setting them in the script of the node.

  If your solution is still available in 2009. In fact, this looks like the right solution to get the behavior you're looking. I think that the reason that it does not work is that there is still some output variables that need to have your solution that are applied to them. These output variables are currently not be wired in the shift registers MathScript node and are only defined in the case of statements which are false, when your code is running. So, if wire you these variables in the MathScript node, the errors should go away and you will not see the default values.

  Initialization of variables in the upper part of the MathScript is another way to get rid of the error. However, it seems that this is not the best solution in your case because you want the variables to receive the same value they had at a previous time, that run MathScript node. The best way to do is with registered SHIFT wired as inputs to the node.

  The reason for this change in behavior between 8.6 and 2009 is indeed to help users find bugs or logical errors with their code. The new behavior makes it less likely that downstream from the MathScript node code tries to use an output that has an invalid value (by default).

  I hope that this explanation makes things a little clearer.

  Thank you

  jattas

• Ring type constant def not updated for LabVIEW 2010 SP1

  I have a problem with the update of the control ring LV 2010 SP1 constants.  If I change the values or names of elements of a ring of control that has the defined type (type def or type strict def) my constant schema do not update.  The constants are set to Auto-Update of type def and if I right click on the constant, change to a control and then back to a constant, they update very well.  And if I have a control/indicator on the comic it refreshes also very well.

  Anyone else seen this problem or can someone seeks to duplicate?

  LV 2010 SP1 bug?

  Thank you

  Dan

  It is not a bug. See here - http://digital.ni.com/public.nsf/allkb/46CC27C828DB4205862570920062C125

• Histogram updated the LabVIEW Code

  Hi all

  I have a simple algorithm that I need to put in LabVIEW. I already have the pseudocode seized upward, and it works when I coded in Java, but for some reason, the translation into images gives me a hard time. Basically, I want to do some manipulation of table so that I can get a quasi histogram. However, I do not want the histogram to tell me all the occurrences in the table - just how many times it occurs in a row. I'll give you an example below:

  Entry: Fuel = {3900, 3900, 3900, 3900, 3900, 3900, 5000, 5000, 5000, 4000, 4100, 3900, 3900, 3900, 3900}

  Output: Value = {3900, 5000, 4000, 4100, 3900}

  FREQ = {6, 3, 1, 1, 4}

  There is a post over there that tells me how to generate a histogram, however, I need slightly modified so that it is not to go through the entire table, but rather keeps a going against and insert it into a new table whenever he finishes counting how many values have been set in that.

  Here is my start of the solution (see a PNG image and a VI)

  Hi ruthnan,

  It is a simple counting you need:

  

• PROFIBUS in Labview 2011

  Hello

  I recently updated my Labview from 2010 to 2011. And then I tried to install the latest driver for Profibus (DF_PROFI_II_LV_1.36.2.zip) that I downloaded from (http://joule.ni.com/nidu/cds/view/p/id/2687/lang/en). Release date: 10/10/2011

  Normally, this extension must be installed to the location following (C:\Program NIUninstaller Instruments\LabVIEW 2010\vi.lib\addons). However, I did find it in the folder "addons" Labview 2011. There never to this question? To resolve this problem, should I just copy Comsoft.lib in the folder "addons" from 2010 to 2011? Something else I have to do?

  Thank you

  Zhi

  I t looks like that it detected the LV 2010 version as the current and did not install anything in 2011. You should be able to copy files on the same path mentioned.

  DirkW

• Photo ring Type Def not updated

  I have a ring of photo type def.  I used it in an another vi.  At the time, the ring of photography has only 5 photos in there.  Later, I added another image to the ring of pic type def, but not a not updated of the vi.  Why is this?

  Given a ring of photo is just another type of ring, see if these appy son message

  Ring type constant def not updated for LabVIEW 2010 SP1

  strict type of ring bat bug?

  Strict Type def with Menu ring does not automatically update the related constants

• Identify the obscure LabVIEW method

  Hi all

  I update a LabVIEW project that was written in 3.x and I came across a LabVIEW method that I've never seen before and I can't understand what he's doing.

  Any ideas?

  m3rl3n wrote:

  Hi all

  I update a LabVIEW project that was written in 3.x and I came across a LabVIEW method that I've never seen before and I can't understand what he's doing.

  Any ideas?

  

  What 'method' are you talking about? I don't see any.

  For this image, it is enough to click No Subvi and select "enable access to the database.

• Transparency feature for under 2011 LabView touch panel module

  Hello

  I develop applications of touch panel for several years now. With LabView 2011, we can't not, to set the color of the pushbuttons to transparency.

  You have this function lost with Labview 2011? Or have I missed a particular setting?

  With the latest updates to Labview 2009 and LabView 2010, touch panel module has not changed at all.

  Thank you very much

  Magnus

  Hello Magnus,

  After that I tried to reproduce your transparency lost on a touchscreen in LabVIEW 2011

  I had the same green bar instead of a transparent button like you.

  In LabVIEW 2010, the button is transparent.

  I made a type definition with a push button, where I enter a rectangle colored (like your logo).

  but it did not work.

  After that, I asked a specialist of the touch panel in our Department. He said, that

  It often occurs on many touch screens with versions of windows this 5.0 and lower.

  But no solutions yet.

  Sorry I can't tell you more about this problem.

  Perhaps, you take the module LabVIEW touch panel for this project 2010.

  Best regards

  Johannes Winkler

  Application Engineering

  National Instruments

• LabVIEW 2010 executable runs under windows xp, but not in windows 7

  Hi all.  Here's the situation.  We have Labview 2010 professional development on a computer running Windows XP.  I designed all my programs with this PC.  We have another PC which has Windows 7 with no Labview.  I'm trying to make the executable files and put them on the Windows 7 PC.  I have been here three executable files and move the Windows 7 PC.  One of the executables work correctly, the other two interrupt immediately.

  Executables that stop have temperature limits and the program is apparently seen a low temperature and so stop the program.  Yet, these same executables work fine on the PC under Windows XP.  What seems to be the case, is that the program is expelled before allowing himself read the temperatures.  I use the modules of the series C 9213 and 9211 with 9188 Chassis.   My programs are showing 0 for temperatures.  Well, it's certainly in the low temp limit, so the program stops.  However, she should not do this.  I know there is little delay with the playback of all thermcouples in 9213 and 9211 modules, but this was not a problem with Windows XP.  Even if the program starts from scratch on the XP PC, temperatures immediately appear, or appear after a second or two.  Yes, I've rarely seen a temp 0 on the XP PC, but the program doesn't stop; Give it a second or two and the time appear.  Why is it that happens in Windows 7?

  An executable that works has no measure of temperature.  It uses only 9481 modules and run the solenoids at a rate of about 0.2 seconds.  This executable works fine on both computers.

  So what - this on the modules of temperature reading that is causing a problem in Windows 7?

  Other installation data :

  -The XP PC has the updates Labview 2010 is compatible with

  -The PC Win 7 not the latest updates of Labview 2010 there are has compatibility problems.  National Instruments has given me the compatible components, and they has several levels down by the most recent (for example MAX vs MAX 5.6 v14.0)