Stop LabVIEW

Similar Questions

• Is it possible to stop labview data hex autoconverting to a SQL database in ascii?

  Hi all

  I is currently working on a program that ask a SQL database for the data from the sensors and converts these data into a spreadsheet for future use.

  My problem is the following:
  I can access and read the data very well; However, the data I'm after are stored in the database as a hexadecimal number (example: "0 X 5727000...) ». When I pass this through this vi "DB Tools Fetch Item Data", he captures the data and the autoconverts it in ascii. It is a huge problem because the data contains several pieces of information and must be analyzed before his conversion in order to achieve the correct value (and wrong format in ascii).

  Is it possible to recover the data as a string containing only the hexagonal information? I already have the code that converts it to; I need as hexadecimal values and not ascii he tries to AutoFormat to.

  Your data are permanently binary.  And how it is stored in the database is a function of some program put in there.  It is not a case of LabVIEW doing any "autoconverting".

  "more labview uses the display format Hex to work more on television anyway.

  So the next question is what is the continuation of the work you want on these data?  There is a function call "String to Byte Array" that converts the characters in a table of U8.  So now, you have a table of numbers of U8.  What you then do with that depends on what all these data are supposed to represent.

• How to reset the LED after pressing the stop button?

  Hello

  I use vi of green LED to indicate if the data has been loaded correctly. However, if I run the same labview program several times online, then the Green LED is always on because "value that data has been correctly loaded" crashes it since the previous session. Is it possible to reset all of the screws LED after pressing the button STOP (stop labview program).

  Thank you for the answers.

  Hope this helps:

• Program LabVIEW will hang between 33% and 50% of the time.

  I have a problem with a Labview program, I did. I have two programs that do the same thing. One is as a flat sequence, and the other is in the form of State machine.

  As explained in the link below, I would like to use a microcontroller to perform wiring for automation of a measurement process. A separate current source and volt meter will be used.

  https://forums.NI.com/T5/LabVIEW/sequence-a-good-idea/TD-p/2601333

  I did some simple test programs that I join since then. The problem is when running, that the labview program crashes, but not all the time is to run the program.

  For example: Hall 1.2.vi will correctly work twice with the third time, he is executed, it crashes. If Cancel you and try again, it will run again twice without any problem with the third hanging. It is in the flat sequence format (was in a flat sequence, but merged windows because I thought that was the cause). From what I can tell, the program crashes when calling Keithley 6517 unique Read.vi. Two connected Keithley devices are connected to the computer via GPIB to 16 and 27. The way I checked if it was this vi the cause or contributed to what I deleted the program never hung and it. I find it very strange that it crashes exactly on the third attempt every time.

  Simple.VI Hall 1.3 will work the first time and hang the second time. If it works 50% of the time. It is in the format of State Machine. It hangs in the case entitled "Measurement 1" that contains the Keithley 6517 unique Read.vi.

  I used the running highlight button and watched the program to run. Curiously, it only crashes when you use this button. So I tried to add some delays/waiting in different places without success.

  This could be the cause? As a side note, I say that the program is suspended for two reasons. The principal is the program does not run so the execution arrow is always black. The second thing is that if you notice at the end of the labview program, I have a block he who turns to the power source which does not happen when it crashes. I have to turn it off manually, and then click the abort program button to stop labview.

  
  

• Problem exporting to tiara

  Hello

  I use a data acquisition card 6070E read the output of a sensor. I have a problem, export the data from the labview to tiara program.

  When my vi stops running, it displays the information on a waveform graph. I right click on the waveform graph and select "Export data to DIAdem", it opens the tiara, but randomly sets some values to zero, the duration and the actual values... It is sometimes only one or two data points, but sometimes (as pictured), it completely distorts the data. I have attached the vi and also an image of how it exports to tiara... The diagram should be with 10 cycles of a sinusoid of 10 Hz.

  Is there something I can do?

  Thanks in advance.

  Hi Sadegh,

  It of about a year since I looked into it, but I think all you need to do is to completely stop LabVIEW, use the attachment VI to replace the existing file on your hard disk, and then restart LabVIEW.

  ...\LabVIEW 2010\vi.lib\ExportToExcel\exportToDIAdem.vi

  Let me know if this doesn't

  Brad Turpin

  Tiara Product Support Engineer

  National Instruments

• Prompt the user for entry as a vi

  I have a weird problem.

  When I run a program that has two under 'interrogate the user entry' vi in a row, one does exactly what it's supposed to.  The second opens as a Labview VI.  This means you cannot use it as planned and so it is a part of the overall program cannot run.  I think that this problem began to spontainiously as I have not change this part of the program at all.   I even tried to delete the old under vi and replace it with a new and the problem persists. Any ideas on that? Joined the program and looks like a picture of what the error. Sorry the program is great, but the problem occurs in the early stages.

  Thank you

  JO

  Hi John,.

  The problem probably isn't with your user to enter vi, it's probably in the upper loop of your program.  I think that your second entry vi opens, then your upper loop begins to run before the user can enter anything, there is a mistake in the upper loop that stops LabVIEW and let your dialog box open.  You can watch this happen if you open the block diagram and turn on "highlight the execution."

• The MAX properties of the device button is disabled / grayed

  Hello

  I am in the process of commissioning of a Labview test bench controlled so looking for conditions in which the system can become dangerous.

  If I simulate a computer/software crash by stopping LabVIEW (using the windows Task Manager) exits Digital remain frozen in their last State before shutdown. I need them all to become 'low state' (off) because that would make the safe test bench. How can I do this?

  After doing some reading, I tried to define the type of MAX, by going to the INTERFACES AND DEVICES, select the device, and then click PROPERTIES. However, the properties button is disabled / grey so I can't access the properties.

  I use the following software versions: Labview 8.6, MAX 4.7.1 and NOR-DAQmx 9.2.1

  The material is: cDAQ NI9178 (chassis) and NI9481 (electromechanical relay module).

  Thank you very much

  Loss of power of the computer, the relay will revert to their default open State.  Even if the device is disconnected from the computer.  This is where the power is connected to the computer, but the application crashes that you will need to take another way to reset the relay.

• VI crashes but highlight execution works without error

  I designed a VI for my business and unfortunately I can't post any code due to the nature of the project.  However, I developed a VI that works with a Lua script, communicate in a way hand-shake-accused of receiving over TCP.

  Basically I have a typical State Machine that goes around where the main report for a TCP command, then once, he gets one, the Lua script waits for a response than the finished LabVIEW acknowedging.  Then the LabVIEW waiting again for another command.  It just goes back until I get out.

  When I run the VI with my script, it crashes.  I see no error message or anything. the LabVIEW program ends completely.  However, if I use the execution to highlight, it works 100% as planned and I can't visibly see all problems.  I also ran through the entire program, using "Step-Through" and who also worked 100%.

  I tried to get the information from 'error', but there is none.  If I run this, it just completely stop LabVIEW on crash with no notifcation at all.  If I run it using one of the methods above, the error Out reported no errors.

  I use not all local variables, or anything that might cause a race condition (to my knowledge).  Except wait for a command by sending one to the end, the code works sequentially and even the communicaton is relatively sequential (since both programs block / busy wait until they receive the order).

  Does anyone have any additional suggestions on how can I debug this problem?

  Looks like that it comes with Developer Suite 2009.

  Do not attempt to teach you to suck eggs here, but you can strip enforcement up to the bare bones to try to isolate the problem.

  Keep the feature to cut until it no longer hangs and then build up until the problem reappears to try to limit.

• Question re: display globals in the hierarchy of the vi

  I am an older (LV2009) application debugging which was written by another developer and includes a large number of global variables (~ 100).   When I discovered the hierarchy VI for the (rather large) VI of high level and I have the option "Include Globals", I notice that the icons for the various globals generally - but not always - have a number superimposed on them.  It does not correlate with the number of callers, the number of institutions, or level in the hierarchy, so I'm curious to know what it is supposed to represent?  Seems like this should be a trivial matter that it is easy to find an answer to, but I checked the forums help and discussion of LV and found exactly so far nada.

  

  Can someone enlighten me?

  Bob_Schor wrote:

  When you create a Global Variable, you end up saving them as a VI, with the default name Global 1(vi).  As with every VI that creates LabVIEW, it creates a default icon, and as it does for all the default icons, he assigns a number, starting with 1.  If you create several Global screws in a single session of LabVIEW, the default icons will be numbered 1, 2, 3...  However, if you stop LabVIEW after you have created the global with global icon 1, and then restart LabVIEW and create another world, its VI (which must have a different name) will have the same global icon 1.

  Bottom line - do you a favor and change the default icon LabVIEW to create so that the icon means something to you.

  BS

  In fact, I think that the OP has already done this.  I think it's the reason for the confusion in the first place; the OP was not used to seeing a default icon.  In fact, I was momentarily confused until I created a world as an experience.  Then I got a good laugh.

• Network Variables custom control Option Disabled

  Hi all

  I am creating a network variable in a cRIO project using a predefined custom control... I've done this hundreds of times before in other projects... For some reason any "custom control" option at the bottom of the drop-down list data type is disabled...!

  I'm sure it's something very simple, but I'm well and truly stuck now... I'm not still connected to my RIO? I have not activated the network connection again...

  See you soon

  Harry

  Well,.

  I have now found the solution... This is a bug... Just stop LabVIEW (completely, not only the project) and restart and voila... the option to wake up...

  See you soon,.

  Harry

• Screws of demolition, but none are running

  So I have a strange and it is difficult to isolate the problem.  Initially, I had a support project size, with 8 players age or so using events user to communicate between modules.  I had several user interface elements that can spawn brat screw for insertion in sub-panels or float and is not.  Each time, I ran my main VI and then when to stop LabVIEW pop - up would be a dialog box indicating

  "Quitting smoking will stop running all the screws", with an option to exit or cancel.  I thought it was weird because none of my screws were still ongoing enforcement.  So I thought that maybe an of my asynchronous process began and for some reason any missed quite command.  So I started disabling some parts of my code for this error to go away.  It was a little long because I had to completely quit LabVIEW, launch it, open the project, disable something, run the VI, then stop it (through the cleaning process) then leave LabVIEW to see if said dialog box still ran a few screws.

  After stripping the VI over I me finally at a place where my main VI was just a giant off diagram structure, without code in the active code, only in the case of people with disabilities.  Running this always caused LabVIEW VI to think a VI was running, and that smoking LabVIEW would he abandoned.

  I tried to copy the comics for a new VI, but he also had the same behavior.  If I deleted the diagram (and then all the code in it) dialog resignation wouldn't be here.  I tried to force a re - compile of the VI of hand, and who had inconclusive results.  The VI I copied the comics to quit without the dialog box, but the main original has not.  I'm having a real hard time isolating and I can just re - create the VI from scratch in the hope, as he goes.  Has anyone see something like this where you know, no screws aren't running, but the tobacco cessation invites you to stop?  Sorry I do not post something easier, due to the complexity, dependencies and inconsistencies in all of this.

  EDIT: Sorry I forgot LabVIEW 2015 32-bit Windows 7 x 64

  Another developer here asked me about the same problem earlier this week.

  I don't think that he figured it out but I recommend go to the hierarchy screen VI then to do a ctrl - a to display all the screws that can give you a clue.

  Otherwise I can meditate only if there is a X-Control involved.

  Made with my thoughts.

  Please let me know if figure you it out.

  Ben

• configuration of Web page tool freezes to the 8.6 with DSC

  I'm developing an application of DSC in LV8.6.   I have no problem with the configuration of the server web page for test applications small including those using a hypertrend control.  A problem with my larger application with shared variables, IO etc. servers.  When I open the Web server configuration tool, it is practically non-functional.  I put an option on the first page and then it freezes and I need to stop LabView by using the Windows Task Manager to get out of the State.   Are there portions of LabView or DSC, which can damage the configuration web page tool?

  Thanks for your help.

  Len

  Nathan,

  I now have a working web page. Thank you for your help.  It took a long time to build, but the result is a Web page that works as expected.  I'm still in the dark as to why my request takes so long to start and why the web tool has taken so long to do its job.  Two things may be related.  Is there an obvious way to start debugging to determine the elements of the slow loading?

  Kind regards

  Len

• Why use 100% of a CPU (1 of 8) when it does nothing

  There is no VI running and LabVIEW uses 100% of CPU 7.

  When I run LabVIEW, open a project.  Everything is fine.  When I run the project without problem.  Once the project is stopped, 7 CPU goes to 100%.  I leave LabVIEW to stop LabVIEW using the CPU.

  I created a VI to ensure that no VI turn crazy on my computer.  There is no running VI...  What the... .CK

  Nitrof

  

  LabVIEW open for more than a day, huh?

  If so, it's a known issue. Workaround will charm you! NOT

  http://www.NI.com/white-paper/13994/en#387557_by_Category

• Using intermittent problems "invoke the node-> default reset" command to delete a table

  I use the 'default' reinitalization invoke the node to clear a table after sending the data to a file. The next time that the vi is called the table should appear all items, set the default values. However sometimes the picture is not deleted and data since the previous call of the vi are still in the arrary, or at least it appears that way, since the same data for the previous time called appear in the file when new values are added to the file. New data looks good, as the data points in the table that I don't update appear with the old values. And again, it is an intermittent problem. I can solve this problem for a while in any case stop labview and re-run it.  Any ideas what's happening?

  Thank you.

  Chuck

  
  

• Close the database/resources

  It's very specific. I open the database of an MSI file, but cannot change the file until it stops labVIEW.

  I tried different strategies such as use of a node to invoke nearby, or simply close reference, and doesn't work.

  It is clear to everyone what I'm doing wrong?

  

  Thanks a bunch, it is logic that you guys mentioned. I'll try to implement.

  Thank you!

  Nyne