LabVIEW car project monitoring

Similar Questions

• Exeuting my labview on two monitors project

  Hey guys,.

  I have the license on my laptop, but once I have the finished code, I am looking to just run the code on two monitors in the testine automated rather than upgrade the license on these screens. Is it possible and if yes, how can I achieve this? Thank you

  Damien

  Hi Damien,.

  Do you mean that you want to run code on machines as the development machine?

  If you plan to develop an executable and this deployment on other computers, you should be fine with just a dev license (However, some tool boxes require a deployment license, such as the audio and vibration package). You can create executable files and installers of in a LabVIEW project. All you need to run these on another machine is the relevant LabVIEW runtime engine.

  Does that answer your question?

  Thank you

• labview deployment project has conflicts

  I'm having a problem with a deployment of teststand (2013 Teststand, LabVIEW 2013)

  I have a deployment that deploys my project LabVIEW that contains all of the drivers (classes and lvlibs) for use in my sequences.

  During deployment (LabVIEW options), I uncheck "exclude vi.lib", "exclude user.lib" and "exclude instr.lib" because the deployment should also work on a PC that has only some runtimes and an operator interface.

  The build is complete without errors, but I can't open the deployed project...

  --> not on a development PC because it detects conflicts (XNodeSupport and some in vi.lib picture.llb of the vi)

  --> not on lifetime PC (file not found)

  Else you have noticed the same behavior?

  He works with LabVIEW and TestStand 2010.

  Thanks in advance for your help, advice and tips :-)

  (Cross post, also on Lavag.org: here )

  NEITHER of the spirit together, we have identified the problem.

  The GDS (suite Goop development) causes conflicts.

  The problem is identified, the solution is underway.

  See you soon,.

  Wim

• Labview 2011 project with sbRIO cannot build app with Lv 2014 RT: error 1003

  Hello

  I have a project developed with labview 2011. It contains a PC application and a SbRIO-RT-FPGA app.

  I made a simple change in a RT VI. then I tryied to build the new application for my SbRIO.

  the problem is when I click on 'Build', an error dialog box appears saying that there is a VI with broken arrow. but my VI are OK.

  Can you help me please!

  Best regards

  

  
  

• Why LabVIEW example projects using Global Variables?

  I'm puzzled.  I've been pretty good programmers LabVIEW talks (including some who work for the OR) and came away with the impression that Global Variables should, as a general rule, be avoided, with functional Global Variables (alias VI Globals) generally preferred for "local memory".

  I have studied some of the example distributed with LabVIEW, 2012 and 2013, in particular the proposed acquisition in real time and am struck by the use of Global Variables, where I'd be inclined to use instead a FGV.  For examples, to stop all the loops on the RT target, the overall "All the RT loop Stop" is defined; 'Constants' of configuration (such as timeouts, Streme network names, the names of the journal folder) are kept as Globals; Streme network endpoints are stored in Globals.

  [Note - there is a weird spelling of the second word of the network Streme, above - when I tried to post with the correct spelling, I got an error message saying this word is 'not allowed in this community".]  I apologize for the offense, but I must confess that I do not understand what the problem with the help of the spelling of this word...]

  Why use Globals in these cases, rather than write a bunch of VIGs to hold these data?  Note that almost all these Globals are 'Read' essentially (written once when a resource is acquired, for example) or "Read Only" (treated as if they were a constant).  Indeed, read-only variables can be written as a Subvi with only an output terminal, acting as a (visible, due to the icon) constant.

  I can see advantages to this approach.  On the one hand, VIGs can have error bounds who run the data flow (I just spotted a bug "data flow" in code, I am developing that is based on this model, to read configuration data to an XML file in a world and in the same VI, Global wiring to a "use - me" terminal, but with no guarantee that I'll read the overall after I write it).

  It is, I suppose, a matter of 'speed' - perhaps Global Variables are 'faster' than VIGs (especially if the VIG 'sits' on an error line).  My thought, however, is that this difference is likely to be trivial, especially as these VIGs (or Globals) tend to become "occasional" calls (with the exception of the indicator 'all the loop Stop' which is called once per line).

  Are there other arguments or considerations that make a Variable global to a better choice than a VIG?  Is there a reason that LabVIEW developers put in these start-up of projects LabVIEW?

  BS

  I have to ask, how do you use functional Global Variables?  Like just a Get and Set?  If so, you can use a global variable.

  Yes, globals are faster and use much less overhead.  At the summits of CLA in recent years, we talked about using globals.  The most common use is for Write-Once-Read Many and writing-never-Read Many with configuration data.  It's a good idea to use globals with the constants that can change on you.  It turns out that the world will have the same performance as a constant in this case.  This is done so that you don't have 1 place to edit the 'constant '.

  The rule on "Globals are evil" actually goes back several years when NEITHER had the huge "people of the country are bad" vendata.  But NEITHER explains well how to do things properly.  So I found people, instead of using local variables, using the value property node.  It's even worse because the property causes thread swaps and kills your performance.  It wasn't until I shouted to people to use wires and shift registers I have seen improvements in the way in which people wrote their code.  So people are always riffling in the use of globals and decided to use FGVs with the EEG and fixed rather cases.  But this does not solve the problem of the conditions of race with critical data and you cause an additional burden.

  So from my experience, I use globals all the time for configuration data.  Yes, you must be careful about the race conditions.  But as long as you understand that it is a common and useful practice.

  I would not use a global variable for data that are constantly changing (use registers to offset or Action motor) and/or processes that have critical sections of code (use a motor of Action).

  NOTE: I use the definition of Mercer to FGV (a Get/Set only) and motor Action (many cases which specifically affect the data).

• Why the continuous measurement and Logging in LabVIEW 2012 Project uses strings instead of Enums and orders from the queue?

  Hello!

  I noticed that the continuous measurement and a project in LabVIEW 2012 Logging using chains instead of enums and orders from the queue. I wonder if there is a good reason for it?

  Kind regards

  Anguel

  First, string vs enum debate is probably the version of LabVIEW vim vs emacs. There are good arguments on both sides, and I doubt that there is always a "winner".

  A brief summary of our reasoning for the current state of the project examples:

  1. We used enums for the state machine because it is self-contained. A state machine will never tell himself to enter a State, he does not know. Knowing (as the programmer) all possible States with the help of an enum allows you to enlist the compiler in order to help us avoid mistakes to change the time (because you can't quite out an enum and LabVIEW can be said if you are not covering all cases to a structure of the case, etc..).

     Enums provide greater protection and rigidity by ensuring all withdrew at the time of publishing. This is often the 'default' recommendation that we do.

  2. We used strings for messages in queue manager because the producer of message and the message handler could be independent processes that are reused or traded. Channels avoid the need for the compiler to be able to connect the orders and push this responsibility to the programmer. This allows you to develop some sub-components independently as long as you agree to a series of channel commands that you can manage - you need not to share a file 'messages.ctl' or 'states.ctl '. It is conceivable a loop of message management a message it does not, how you can decide to either silently ignore it or will trigger an error (as we do in the model). The strings make it also easier if you want to swap the queues of LabVIEW outside by a TCP implementation for network vacilitate or intra-Processuse communication where the other end may or may not be written in LabVIEW.

     Channels to provide more flexibility (that is, you can add new commands to an existing via plugins system, you can pass parameters as part of the string, etc.) at the expense of pushing her potential errors at run time and to put more responsibility on the programmer.

  3. The actor's gifts frame a 3rd option - using classes such as messages. For me, it combines many of the advantages of these two enumerations (strictly typed, change errors) and strings (flexible and scalable), but with the disadvantage of being somewhat less transparent (you understand OO, be comfortable to navigate through a multitude of screws, legacy of understanding, etc.).

  I don't know there are other reasons, others to the breast OR had or seen as we validated models and examples of projects in-house, but here are my reasons. We know that we can not design for each situation there - our goal is to get useful models against new users to make them aware of what well thought LabVIEW programs are similar to experienced users know their applications better and I hope they do not hesitate to change what we provide or create their own designs, when they feel it's necessary. (On a side note, please share what you come up with - a community of experts sharing models would be really useful to us all LabVIEW users).

  Best regards

  Simon

• Which supplier Source control would you recommend for a single developer on a labVIEW project moderately important

  I have not used a front Source control provider.  My hope is that I don't have to deal with a large learning curve in using the basic features of a source control provider.

  Also curious is the most popular provider used by LabVIEW developers.

  Thank you.

  If you are getting started with Subversion (Tortoise SVN is the 'client' to a Subversion server), you have the choice between three options:

  1. Use a server Subversion maintained by your company or your University.  (I, fortunately, put at my disposal one).
  2. Use a commercial Subversion server.
  3. 'Rolling' (which means that the other host a server yourself, on your PC or on another PC, or simply use a 'local' repository).

  I listed them in the following order (according to me) that it is "desirable".  I, myself, would be enough worked to avoid Option 3, because it puts all the "eggs in one basket', in other words, you must assume the responsibility of not only keep your code Committed/updated the repository, but you must keep secure, backed up repository, and 'remote' (if your house burns down and the external unit containing the repository also goes up in flames you lost everything).

  I recently started a collaboration with a colleague in the Canada.  Because of institutional policies, I couldn't access our server local to Subversion, but found that assembled (www.assembla.com) offered a Subversion server access at a reasonable cost.

  Once you have identified a server, get your created repository and your project saved in the repository is not too difficult.  A practice I found works well is to organize the filing of LabVIEW, one project per repository projects, with the name of deposit is the name of the project.  I have adopted the model of trunk/branches/tags subfolder for the repository (i.e. the filing "Of Bob Project" will have a trunk, a branches and a subfolder of tags), with most of the activity taking place in the trunk.  I try to use the branches almost never, but that's another story.

  There are a number of tools to put "hooks" in Subversion in LabVIEW.  My personal preference is to do all my work of Subversion at the level of the Explorer of Windows files, validation and updating of entire projects to the end and beginning of work sessions (commit to the end, updated at the beginning).

  Bob Schor

• LabVIEW 8.6.1 project causes the slow open VI reference

  I have a strange problem with 'Open VI Reference.vi'.

  Case 1.

  • Open a project in LabVIEW that contains "Main.vi".
  • Open 'Main.vi '.
  • Run "Main.vi".
  • Execution of "Open VI Reference.vi" take about 2, 000ms

  Case 2.

  • Open "Main.vi" - open LabVIEW No. project
  • Run "Main.vi".
  • Execution of "Open VI Reference.vi" take about 100ms

  I converted the project to 8.5 and the problem goes away. I have not all machines with 8.6.0 to test if there is a problem with 8.6.1 only.

  Has anyone else seen anything like this?

  
  

• test transistor using labVIEW project

  Hi all. I'm new in labview... pls guide me... Thank you...

  I am a student and I have to do a project on labview, my project is: "DEVELOPMENT OF AUTOMATED TEST SYSTEM for TRANSISTOR USING LabVIEW.

  I already installed labVIEW 8.5... can someone give me a tips to get started on my project?

  I need to find a coding for CC, Osciloscope and Transistor power...

  Thank you...

  Start by writing a project plan.

  What do you want the program to do?  What are the tests that you must run on this transistor?

  What are their contributions, what are its results?

  What are the series of steps you have to do to go from A to B?

  What material did you use?  You mentioned a DC power supply and an oscilloscope, which brands and models?  You use data acquisition cards?

• Simulation Serial Monitor of the Arduino with Labview?

  Objective: Simulate Serial Arduino using Labview base series Monitor write and Read.Vi.

  Problem: When a stream of ASCII data is sent to the base series writing and Read.VI it stops playing after about 3 seconds.  Whereas that must be continually read data even when there is more data that can fit in the reading string indicator. Ideally, it should push the old data from the top of the screen and display the data again at the bottom of the screen.

  What changes should I do at the base series write and Read.VI to simulate Serial Monitor of Arduino?

  Howard

  
  

• I can force a CVI DLL for download with a deployment of labview rt on target project?

  Y at - it a method to force a CVI DLL (referenced via Lib Func call in subVIs) can be unloaded when a labview rt project is deployed to the target, instead of through FTP dll in the RESP folder (System)?  I have clients who do not seem to grasp the concept, and I will provide documentation written for an easier method, as appropriate.

  You include your dll in your project?  If it's in your project, you have the possibility to put the dll in the section still included the build.  It will be in the executable and you shouldn't over ftp.  I've tested this and the dll has been added to the building when I tried it.  Which the dll does not appear in the project?  She is explicitly under the target, or it is under dependencies?

• LabVIEW Web Services: How "undeploy" web services

  I created the example of web services:

  Address book in book labview\examples\comm\webservices\address project for an example of a Web service that handles to publish data, streaming output, static content and HTML Forms.

  Weather project monitor labview\examples\comm\webservices\weather monitor

  for an example of a Web service which publishes simulated weather statistics.

  Using the generator of the user Web interface, they are still included in the list of available web services when I import Web services.

  How can I get rid of them?

  My OS is Windows Server 2003

  C:\Documents and Settings\All Users\Application Data\National Instruments\WebServices\aws

  Has been able to manage web services via the System Manager.

  Thank you

• Software FPGA with LabVIEW 2013

  I have a system with a rotating computer "development" under Windows 7 and an NI PXI-1036 chassis with a PXI-8101 controller as well as a card FPGA PXI-7853R. Recently, I upgraded to LabVIEW 2011-2013 of LabVIEW. I kept LabVIEW 2011 installed just to make sure everything is still working on the new LabVIEW.

  Now, when I open my project in LabVIEW 2013 Project Explorer, my FPGA comes with a warning triangle yellow next to him (see attached photo). The warning says:

  "Software support for this target FPGA is not installed on the computer. You can view and copy elements into the project, but you can not compile any screw under the FPGA target, until you install support for the target. Refer to the documentation of specific material for more information on the proper drivers and for more information about the installation and configuration of the target FPGA ".

  Regarding the installed software, I have LabVIEW SP1 of 2013, 2013 of LabVIEW FPGA Module SP1, SP1 of Module 2013 LabVIEW Real-time, and Xilinx Compilation tools 14.4. On the chassis of the TARGET (with the PXI-8101 controller), I have attached a list of installed software.

  Interestingly, when I open the project in LabView 2011, no errors or warnings are present with the FPGA card. It is only under LabVIEW 2013 I see the warning. Did anyone see a glaring omission of software that could be the cause of LabVIEW raise this error? Thank you for your help.

  

  

  Best guess is that're missing you the driver for your FPGA device. Try to install the latest version of NOR-RIO (or at least the version supplied on your 2013 SP1 install disks). Have you installed device drivers at the time that you have installed SP1 2013 LabVIEW?

• Need help of LabView on loops

  I'm doing a LabVIEW MyRIO project on how to display the values. Basically, I give myself a LCD screen and a keyboard. I'm supposed to show three sequences in the order. First, it must ask the user to enter a number on the keyboard to choose his field of interest. Then depending on the number, the user is prompted again to choose another number to specify the particular value he or she wants to watch. Finally, the value is displayed and the user can choose to return to the previous sequence interface by pressing a key. Each of the three sequences are able to "hold" until the user presses a button.

  I am able to attend the second interface using all loop inside a structure of the case, but I don't know how to start pressing a button to return to previous sequences. I need help on this particular part.

  Thanks in advance!

  The code that looks way too complicated for the problem you described.  Where is the state machine that we suggested to you?  Why so many useless people sequence structures?

• Application Builder-how to get rid of the savings going to project after generation?

  Hello

  I'm using LabView to project continuous integration with Jenkins. I have a vi that runs test cases is build of the project, then bed information on the results of Jenkins.

  After a success, there is a warning that I have unsaved changes in the project that I wanted to build. This message is to close labview and jenkins of the display of the results

  Here I found information about this warning at the first "Note".

  http://FTP.datx.com/public/DataAcq/LV-link/LVLinkWebHelp/Building_and_Distributing_an_Application.ht...

  How to get rid of this warning, or save changes automatically, so that I don't have to click 'Save' after each generation?

  Thank you

  Karol

  First of all, you don't want to get rid of this warning. It is this backup which makes the work number version auto-incrémentées. LV has to save the new version number in the project.

  Yes, you can make a backup. Somewhere, to do the code LV, who runs a program generation. At the end of this process, you need to save the project. There is a method to do project.

  I wrote a small program for me to open a project, perform the selected builds and copy the installer resulting in a USB key.

  Mike...