changes in labview vi

Similar Questions

• Change of LabVIEW VeriStand system definition

  Hi all

  I have a project where I need to be able to change the drawn in LabVIEW VeriStand system definition.  The project will use a LabVIEW user interface and I would like to be able to programmatically change of LabVIEW VeriStand system maps (unloading and loading mapping .txt files via LabVIEW System).

  It seems that the SystemDefinitionAPI contains the methods I need, but I can't figure out how to get a reference for VeriStand.SystemDefinitionAPI

  If there is an easier or simpler way to do this, please let me know.  Thanks for your help,

  Phil

  A bit more info that may be useful...

  The examples referenced by Jarrod contain a constructor .NET to create a file system definition by giving a name, description, creator, version, etc...  If you double-click on the node in the constructor it will bring up a dialog box that shows all the manufacturers of the SystemDefintion object.  You should see another manufacturer that only requires a string entry "nivssdfFile".  Use this constructor and provide a path to your nivssdf file to open your SysDef existing (instead of creating a new).

  Remember, you should always call the SaveSystemDefinitionFile method when you finish your changes to commit everything on the disc (such as demonstrated in the example).

• Can I still change a LabVIEW program even if device drivers are not installed on the computer used for editing?

  Hello

  If I do not install device with LabVIEW drivers can I still change any given LabVIEW program created with this version?  Or do I need to install device drivers if I'm editing a program that uses these drivers?

  Thank you

  Dave

  What you reinstall? The dll is part of the traditional DAQ driver.

• Error 1026 "VI reference is invalid" after the upgrade from 2015 to 2016 LabVIEW LabVIEW

  I just upgrade to LabVIEW LabVIEW 2015 2016 and met a "1026 error".

  Main program calls a VI sub that contains a server VI reference "VI this" connected to a Refnum output on the pane. The Refnum of the output of the Sub that VI is then used to get the 'name of vi", which is used as an input in the node"Reference VI"open. The program works very well in 2015 from LabVIEW.

  For some reason, in labVIEW 2016, the Refnum of the Sub output Vi returns a "step A Refnum", when it is used to get the name of 'Vi', issuing an "error 1026". On the other hand, if I open the sub first Vi (therefore in the meory), then run my main program, it works fine.

  Can someone explain what has changed between LabVIEW 2015 and 2016 that can lead to this issue.

  Thank you.

  Ian

  This code will result in the sub VI being released in ' reference to ' instead of having to use the server reference VI as an input for the property node. You can simply delete the VSR to reference to.

  

  See you soon!

  Ryan

• Difference between the version of the Runtime and Developer version of LabVIEW.

  What is the LabVIEW Version called the runtime?

  Is this only for the visualization of the screws built in developer version LabVIEW?

  Can't we develop or modify TENS of LabVIEW version screws?

  vaibhavinegi wrote:

  What is the LabVIEW Version called the runtime?

  There is a version of the separate Runtime for each version of LabVIEW.  You can open NI MAX and develop software to see what is installed on your computer.

  Is this only for the visualization of the screws built in developer version LabVIEW?

  Without the development environment, you cannot change screws LabVIEW.  The runtime engine is responsible for actually running the code in order to integrate LabVIEW executables and run them on other machines without the development environment.

  Can't we develop or modify TENS of LabVIEW version screws?

  NO.

• Try to use my computer LabView code to control 4 LED

  Hello

  I'm a student working on a project at Boulder CU and I need a little help. I'm kind new to LabView but, I created a code that will create a random number, which one of the four LEDS will light, and then, if the LED turns off after a slide bar senses (accelerometer) a value greater than 5 (this value will change after certain data from the accelerometer). After this process, the random number generator generates a new number for a new light. I wonder how to tell the computer what LED icon indicates what LED to real life. Is there a way to connect my LED without changing my LabView code? I have to create a Wizard outputs digital DAQ? Please see the attached labview code and hopefully, you can help out me. We had major problems, trying to get our accelerometer to read a constant logical value and have just meet our problem of LED.

  Thanks, Zack

  Hi Zack,

  your VI is somehow Award nomination for Rube Goldberg...

  "How do you tell the computer what LED indicates which LED to real life."

  Well, you have to decide where the "hook" these LEDs 'real life '. When you have made your decision, you will need some hardware driver to switch the LEDs. A Wizard of data acquisition can be a good choice when you use material. Otherwise, use the pilot to come with your hardware...

  "Is there a way to connect my LED without changing my LabView code?

  LEDs 'Real life' no real hardware drivers need...

• What version of VxWorks operating system is used by the Module of Realtime LabVIEW 8.6

  I have in the past created VxWorks shared libraries for use with the Module of Realtime LabVIEW 8.2 and 8.5 and there are various required tools due to the change in versions of VxWorks by these two Versions of LabVIEW.

  For your information, I would be interested to know if changing to LabVIEw 8.6 Realtime Module will require still a new compilation, or if this version is always based on the same core VxWorks 6.3 and my shared lib would therefore simply continue to work?

  Rolf Kalbermatter

  Hi Rolf,.

  Great news; VXwork version is still 6.3, so we have no problem with the migration to this version.  Please let me know if there is.

  Best regards

• Display 1-bit depth BMP file in LabVIEW

  I'm reading a depth of 1-bit BMP file in LabVIEW, but using 2D image control, it keeps out of the black.  It opens fine in painting/PhotoImpact applications and I can see the image as an array of Boolean (1 - bit pixmap) by using the code below - so, how can I display the BMP using LabVIEW?  NOTE: The attached ZIP file contains the offending image BMP - is not allowed to attach files BMP directly - odd thtat?

  

  

  Your colors are not RGB, but 32-bit. White is defined as xFF000000 instead of x 000000 and black is defined as 0xFFFFFFFF instead of 0xFFFFFF.

  If you rewrite properly to the palette of colors, the image looks OK, see change enclosed (LabVIEW 2010). I don't know enough about the situation to decide if this is a bug or not.

  

• reset the ftp labview 2011

  Hi, I was working with LabVIEW 2010 and I have programmed a VI to transfer a file and check containing the path remote, everything was fine. Now, I've changed to LabVIEW 2011 and I can't find the function "reset ftp" and my VI no longer works. I'm not sure of the origin of my problem, I guess that it is not working because I do not have anything to reset the conection or if I need to use the other function to fix this.

  I have programmed a new LabVIEW VI 2011 without the function "reset ftp" and it does not work in any case.

  I hope you can help me.

  Hi Eric_NI, I solved my problem. I checked the block diagram of the "get file" function and I found the correct way to implement FTP. Also, I use 'active = False' for all the functions that have the "active" option

• format of binary data in labview 8.6 or more

  I'm writing a binary file in LV8.6 to an array of clusters in which each cluster has many types of data in it including more tables and clusters. I want to read that data in a MatLab program, but nothing is read correctly.  It seems also that there is change between after labview 7.x where the type defs have been written in 16-bit before now are 32-bit. and I can find no documentation on how the binary write function stores the data of complex data types.  Any search for documentation on the site of labview brings just hundreds of visits irrelevant.  I try to read the binary file in matlab and I don't see any numbers expected coming out.

  Someone at - it a link to where I can get the specifications for LV > = 8.6 binary formats.  Or full of info on flatten channel for new versions of labview.

  Thank you.

  The format of the flattened data is documented in the help of LabVIEW. In the contents tab, expand Fundamentals-> how LabVIEW stores data in memory-> Concepts-> data flattened.

  The flatten the string function only saves the data, not the structure. You think of Type descriptors. Yes, it has changed in LabVIEW 8. BT 7, they were 16-bit. BT 8, they are 32-bit. It is also documented in the help of LabVIEW.  Fundamentals-> how LabVIEW stores data in memory-> Concepts-> Type descriptors.

• LabVIEW 2014/2015 break with my library of wrappers

  I have a lot of LabVIEW package screws saved in LV8.6 library, they almost all containing call library function node. Recently, I was working on a new program that uses these library live I have found that when you use these screws it causes LabVIEW to crash. Accidents are not due to errors of execution, but can occur during execution and development (is not running).

  Here's my sympthoms with different versions of labVIEW.

  • LabVIEW 2010 - these accidents do not happen at all.
  • LabVIEW 2014 - blocks most of the 3 versions I tested it. LabVIEW has crashed on me when you press "save all", "run", "exit / close ', double click on a Sub VI to open it (the library VIs and SubVIs new for the new program).
  • LabVIEW 2015 - seems to be a bit more stable then 2014. I only noticed crashes when you press "save all" and "exit/close.

  I tried the following

  • I read on the forums that opening the screw with a new version, massive compilation and save for precedent could solve the problem. I tried with no luck.
  • Mass, compilation of all screws of 8.6 library into the new version of LV before trying to use them in an application. This has no effect either.

  Is labVIEW a problem or a problem with my screws?

  And how assign you the string that you pass to the second parameter? All wiring a string constant empty for her? While in the LabVIEW code you don't have to worry about memory allocation before calling some other VI, it is certainly not true when calling C functions. Function wants to write information in this string, and for that to work (You on the LabVIEW diagram) caller must allocate sufficient storage space for it.

  We must know in the documentation of the API, which is the maximum size of the buffer and allocate only a large part of the size of the string. There are two ways to do

  (1) use a table this is initialized with a U8 as input and the right type amount for the size of memory buffer and dressed it with an array of bytes to the node of the chain.

  (2) see you Minimum size in the configuration dialog box? Enter the number of bytes that the string must have at least according to the documentation.

  To answer the inevitable question immediately. Yes, he didn't plant in LabVIEW 2010, but did corrupt the memory and anyway somehow there yet. Any alteration of the memory immediately translates into an accident. There are several possible outcomes of these corruptions and they can change according to the computer that you run your application, the amount of available memory, the moon phase and how your emotional state is right now (the last two are not very serious but also quite unrtrue). The layout of memory at the moment when your running can much influence what happens to these alterations. It can produce results strange and inexplicable in your program when the actual data values that are store values in wires are crushed, or your screws can get corrupted and if save you them to the disc later get unreadable, or the computer produces a dialog error box much later, when you try to stop your app and LabVIEW , or it seems nothing happens (but is still of corruption there not only to bribe vital data in memory).

  With the change to LabVIEW 2014 layout changed memory somehow, perhaps due to optimizations more aggressively in this new version and all of a sudden your DLL overwrites a memory very vital for the operation of your application in LabVIEW.

• LabVIEW 8.6.1 AMD Multi Core Crash with call loops

  Hi all

  I tried, but I couldn't find all the messages with my exact situation.  Here it goes:

  I have a multi-core AMD Phenom 64 processor and I'm running Windows 7 64 and I am running an application in LabVIEW 8.6.1 in compatibility mode.  (I know, not a good idea)  I have a pretty complex application with several timed loops and the different ways to talk to FieldPoint (FieldPoint 6.0.6 and experimentation with Modbus talk to cFP-180 x).  You may be wondering why I'm using call loops.  It is an application of RT which can also run on Windows using structures conditional disable, etc.

  I had met sporadic crashing earlier in my files executable for more than a year and used a lvalarms.dll in only patched version my executables.  It was on a totally different processor and we were running Vista at that time.  Now, I notice a very similar behavior on 8.6.1, except now the development environment all crashes or breaks down my executable compiled as well.

  I found this KB, but he was referring to problems observed on LabVIEW 8.5, and the utility of the OS is only for Windows XP.  As recommended in the KB, I used BCDEdit to set the flag onecpu and now everything seems to work normally.  My PC is now significantly slower, however, and I wonder if there is another workaround solution that I might be able to try.

  If you have read so far and who have followed my description you already have my gratitude.  If anyone else has experienced this?  Someone at - it ideas?

  Thank you very much

  Jim

  Alright.  In case someone else runs into this apparently dark scenario, here's workaround solutions I've found:

  1. see if the problem goes away by setting the processor affinity using the Task Manager. Open the Task Manager, look under the "Processes" tab and right-click on the process. (for example LabVIEW.exe or your executable)  Under the context menu which select "set affinity...". "and select only the CPU 0.  In my case, I have a quad-core processor, so I up to four logical processors that are displayed in the dialog box that results.

  Run your application code or the executable file for a while, and if everything seems to be stable, it would seem that you have isolated the problem successfully.

  2. one of the solutions is to disable additional logical processors for the entire operating system, although there may be negative implications on performance.  In this case, try the steps in the lower part of this KB.  I have Windows 7, so I used the utility of command-line bcdedit with no problems.

  3. Finally, a really interesting option that is well worked for me should automatically set the affinity of the processor for each individual process.  There is at least a utility available to achieve this.  I've now changed my LabVIEW 8.6 shortcut to call RunFirst, which sets the processor affinity for LabVIEW to automatically use the first logical processor.  This way I can still use my processor image for all it's worth except in applications that have problems with it.

  I hope this helps someone else out there one day.

  Jim

• LabVIEW FPGA SP1 2012 & EVS1464RT FPGA IO

  Hello

  There seems to be problems with the new Labview FPGA 2012 SP1 in combination with an EVS1464RT embedded Vision system, which took place only after upgrading to SP1 2012 Labview:

  • While trying to compile our code for the EVS1464RT FPGA or (Vision system embedded with e/s based on a FPGA Virtex-II FPGA) Xilinx tools (V10.1, since it's a Virtex-II FPGA) has reported an error saying that the compilation work has tried to set the property 'Data (output events)', which does not exist, so the Xilinx tools just quit with an error.

    A complete uninstall and reinstall 'clean' do not solve the problem.

    Research has shown that there is a property correct for Xilinx tools, called "done (output events)." An extended search in the Labview upwards 'incorrect data (output events)' some text files in 2 files "resource.xml" in the directories '...\National Instruments\LabVIEW 2012\Targets\NI\FPGA\IMAQIO\IMAQIO-1 "and '...\National Instruments\LabVIEW 2012\Targets\NI\FPGA\IMAQIO\IMAQIO-5' (and nowhere else).". " Change these 2 texts to 'Done (output events)' corrected the error and allowed to compile the code again.

  • Another problem is that you can not start the VI FPGA-interactive (for example by clicking the Run button). This product just another error message saying that the VI '...\National Instruments\LabVIEW 2012\vi.lib\FPGAPlugInAG\IMAQIO-5\niFpgaOpenAndRun_IMAQIO-5.vi' could not be found (and there really is not anywhere on the hard drive).

    The FPGA VI can be started from an another VI on the target host by using the function "Reference open FPGA". Then it works without any problems, so the bitfile has been obviously compiled correctly.

  All of this worked out of the box without any problems on my old installation of Labview (before 2012 SP1 update).

  The first problems now seems to be a simple typo, and using the function "Open FPGA reference" is a workaround for the second problem. But I'm very angry that National Instruments does not seem to test their software before releasing. A service pack should never break things that worked before.

  Find these alternatives cost me 3 days, which, in my opinion, could be acceptable for open-source software, but not if you pay hundreds of euros per year for a "Standard Service program. For that kind of money, I expected NOT to test all the changes that they do well.

  Best regards

  Dr. Merlin Welker

  Hello Mr. Welker.

  First of all, thank you for your comments. I'm really sorry that you stumbled on this issue. Please let me give you some background information on it.

  You are right that the update for the versions of service pack is to address reported problems and he should never break things that worked before. Unforunately, a change in LabVIEW FPGA exposed an underlying issue with e/s NOR-IMAQ driver FPGA compilation. We have identified this issue and addressed it in the Acquisition of Vision Software communicated in February 2013, including e/s NOR-IMAQ 2.6.1.

  It is now available in the Update Service of NOR. We also found and addressed the issue with the FPGA Open running and run interactively in the thatsame release.

  We recommend the upgrade to use the latest version of driver, whenever you upgrade from versions of LabVIEW, to ensure better compatibility between them. Please note that whenever you upgrade LabVIEW FPGA or Vision Acquisition Software, you should also recompile your LabVIEW FPGA projects.

  While these issues were found and corrected in the latest version, we are now reminded our development and testing processes for future versions. Please accept our apologies for the inconvenience. National Instruments is committed to your satisfaction and to maintain your confidence in our products.

  Thank you

  Elmar

• How to avoid the launch of Labview VI when he invokes in Teststand environment?

  Hi, friends.

  I am a student of teststand. I wrote a few screws by Labview. Now, I want to invoke in teststand environment.

  But when I run the sequence. LabVIEW automatically launches.

  How to avoid the launch of Labview when I run the sequence?

  Thank you.

  LabVIEW programs require a runtime engine. Under the TestStand configuration drop-down, select adapters. You can change the LabVIEW adapter to select the runtime rather than the development system.

  This should prevent the main screen of LabVIEW to appear, but you will not be able to change your LabVIEW VIs while they run of TestStand using the runtime engine.

• error 10109

  I use labview to control a couple of engines Thorlabs APT in sequence with some other machines and I'm unable to communicate with engines. Previously (last week), I could appeal successfully, to connect and manipulate the engines through labview. Now without changing the labview program, I'm getting and error code (error 10109) who told me that control of the hardware has been disabled. I can control the motors very well through APT interface software that comes with engines so I know that the computer connects to them but I don't know why the engines are suddenly inaccessible.

  The attached program has worked in the past until today without modification made to it. That's all just a loop that tells a motor to move in steps between steps of the other engine.

  Hello Kai,

  Thanks for posting on our forums. After searching around this error 10109 you receive, it seems that we have no documentation or resources to help explain or correct this error. This most likely means it is thrown by the Thorlabs since nodes invoke engines in your program. It would certainly be useful to contact Thorlabs and see if they have any documentation on this error.

  Other than that, the best advice, I have to offer is first double check and make sure you use actually the serial number of the correct material (which is since the interface APT software). I would also close all your programs down, restart your computer and then just pull the top of your LabVIEW program and try and run it again.

  I suggest this because this error could possibly result from having both your LabVIEW open program and software Interface APT. This can cause an error to have reserved references and having two programs trying to call him.