Exit behaviour labVIEW 8.2.1.
Hello,
is there a major change regarding the EXIT-Function behaviour from LabVIEW 8.0 to 8.2.1 ?
i recently switched to 8.2.1 but my application exit behaviour is really strange after the upgrade.
I am using the EXIT LabVIEW Function (True-signal connected to the EXIT Function)
pre-description:
* user pressed EXIT
* Are you sure dialog
* Application get closed....no more windows viewable.
post-description:
* user pressed EXIT
* Are you sure dialog
* Application is ended. Application windows / Frontpanel is still viewable and Top Bar shows the stopped icon.
why is the offcially EXIT function no longer working as supposed ?
any suggestions ?
Best regards
f.poeck
Hi,
ok my first description was maybe a bit short, sorry.
In my last release (*.exe, created using Application Builder) of my LabView 8.0 (now 8.2.1) project the user had a EXIT Button.
If that button was selected a dialog poped up with the "Are you sure"-dialog. That part was handcreated in LabView and has notihng to do with the LabVIEW-EXIT Function i am using in the next step.
NOW (next step)
If the user answers YES a true-constant is passed to a LabVIEW-function called "Quit LabVIEW". Big EXIT Text on it.
in 8.0 that true constat was enough to close my application and close the appluication windows.
in 8.2.1: the application get closed, but still displays the application windows as non-running application.
Was that enough as description ?
Sorry but i cant post the full-program-source here...would mess everything up i guess regarding size etc...
I have already noticed that some other LV users (german unofficial forum) seem to have a problem with the new function of EXIT / Quit LabVIEW thing.
Best regards
f.poeck
Similar Messages
-
I am working with drivers of a instrument in LABview and want to completely exit/stop the whole Labview program is something goes wrong. Like, indefinate execution of some while loop..etc.. How can I do that?
This is exactly the discussion I was hoping to stimulate. (I
hope interesting, educational and possibly controversial). I think that the
most valuable part of the discussion to date is your experience and issues with
the application of the Exit vi.
I suspect I may be about to commit heresy to many. But in suggesting what
follows, I hope you will keep in mind a British comedy that I like called
'Black Adder' with Rowen Atkinson. I am applying this to many levels in this
response. I admit to brevity again here....
He is struck with a dilemma of forbidden love and cares what the world will
think and goes to the 'Wise Woman' for advise on his problem: -
She gives him three possible solutions: -
Kill yourself - 'No' says he.
Kill the object of desire - 'Not really' says he.
Kill everyone else - 'Not really practicable' says he.
He elects not to take the advice of the 'Wise Woman' - It transpires that there
was a solution, as there was an error - he just didn't have all the
facts..........
To add one small part to the story, I would like to add that everything dies
eventually!
So here it comes.... Everyone SHOULD be putting in at least one EXIT vi in a
production application!
Still sat in your seat?
I propose - For exactly the reason that has been pointed out with regard to the
hardware and safe shut down. That is to allow the software (LabVIEW) to do the same. To
explicitly and formally state when and where the application terminates - Even
if in principle it is not actually intended that it should - the exit point and
software shut down sequence should be clearly indicated. I would suggest there
should be normally one exit point for a classical application.
To this end the example posted would be modified to include the EXIT vi - when
the designer has, resolved all issues or just can't cope any more.
What one tends to see, both in this forum and in released applications; is
development code or applications that were never reviewed to completion. Effectivley Beta applications.
NI don't put the EXIT vi's in Examples; as it, of course, EXIT's LabVIEW
cleanly and completely!!!! (bit of a pain for a novice). But as a result neither do many others.
So are you a convert to the cause?
Now my questions to the forum are: -
Do you allow for and provide, a single point of software shutdown;
clearly stated and explicitly defined for production applications (would you
admit you don't / haven't)?
If you don't; what do you do?
How do you go about trying to assure clean up of any problems (I have
yet to meet the perfect systems designer, I live in hope). -
I have a probelm when I use the "tool/import shared library(.dll)" wizard to generate the API from C.
The API works correctly when I complete the wizard, but after I exit labview and re-start labview to run the API again. The error 1097 code "......this might corrupted LABVIEW's memory.............."appears.
The only solution now is to re-generate or update the wizard to generate the API.
I try to find the answer in
http://digital.ni.com/public.nsf/allkb/58596F5D41CE8EFB862562AF0074E04C?OpenDocument
The paragraph in above article shows
"LabVIEW does not crash until it is closed
The most likely problem is that the DLL function being called has corrupted the memory. If you pass arrays or strings to the DLL, the DLL function cannot dynamically resize the array. Writing beyond the last element of the array or string could corrupt the memory and this may not be obvious until LabVIEW is closed."
But it doesn't match my case. Does someone have idea about this? I Attach my .h file for reference
Attachments:
test_api.h 1 KB
link_test_api.h 1 KBwewe1215 wrote:
I have a probelm when I use the "tool/import shared library(.dll)" wizard to generate the API from C.
The API works correctly when I complete the wizard, but after I exit labview and re-start labview to run the API again. The error 1097 code "......this might corrupted LABVIEW's memory.............."appears.
The only solution now is to re-generate or update the wizard to generate the API.
I try to find the answer in
http://digital.ni.com/public.nsf/allkb/58596F5D41CE8EFB862562AF0074E04C?OpenDocument
The paragraph in above article shows
"LabVIEW does not crash until it is closed
The most likely problem is that the DLL function being called has corrupted the memory. If you pass arrays or strings to the DLL, the DLL function cannot dynamically resize the array. Writing beyond the last element of the array or string could corrupt the memory and this may not be obvious until LabVIEW is closed."
But it doesn't match my case. Does someone have idea about this? I Attach my .h file for reference
Which of the 2 functions do you call? How?
The documentation of InitSocketEx() seems to indicate reversed parameter order than what the function prototype looks like!
I indeed do not see much possibilities to pass in to small a buffer that the DLL function might be overwriting past the end. This really only leaves one more possibility:
Your DLL is doing something largely illegal somehow. Maybe something as silly as storing the reference to the ipAdress instead of the address itself. The memory passed as parameters into a C function is generally only valid for the duration of the call. This is especially true if you use LabVIEW since LabVIEW will re- and deallocate memory buffers frequently as soon as they are not used anymore and the parameter to a Call Library node is considered to not be required anymore after the function returns.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
Which command I can use to exit from a subvi without exiting from labview in run-time?
Similiar to 'Exit Sub' command in Visual Basic.
> Similiar to 'Exit Sub' command in Visual Basic.
There isn't a command to do this. Since LV is a dataflow language, it
is important that all the data be delivered to the output terminals.
BASIC is a procedural language, with all sorts of control flow commands
like this, and if you are using a functional language or a dataflow
language, you simply focus on getting to the end of the function. If
you are in a while loop, you terminate the while loop by the value going
to the conditional terminal. If you are in a For loop and need to exit
early, perhaps it should have used a while loop. If there is code in a
normal diagram that you sometimes do not want to execute, it should
probably go in a case structure.
The other reply has some good suggesti
ons in that you probably have a UI
or a sequence that you want to exit out of. Organizing your code so
that you are in a button handling state or exiting state will help you
organize how you think about the transitions between states. On the
other hand, there lots of examples and user contributed VIs to look at.
I'd recommend you get comfortable with a few of them since the state
machine is just one programming tool, just like the loop and case
statement that it is built from.
Greg McKaskle -
Run-time error R6025 exiting Labview
After I modify a VI and/or Project, I exit from labview by clicking on file->exit. It will generate a R6025 run-time error. If I just open and close labview, this will not occur.
I am running Labview 8.0.1 on windows XP.Humm…..
Sorry to hear that the Norton configuration is locked down,
because we have about half a dozen instances of this error occurring and all
but one were fixed by changing the Norton settings.
There are a couple of other questions that I didn’t ask but
might be relevant if there is to be any workaround. Are you running any VIs
before closing LabVIEW, or just modifying them?
Does this happen on every VI you use, or just on a particular VI? Is there anything else unusual about the
development machine – do you have a different version of Win XP (such as media
edition, or tablet)? Do you have the
same problem with other computers? Would
you be allowed to temporarily disable the script blocking in Norton while you
work in LabVIEW?
I don’t know what role (if any) NI Serial might have in
this, but if you are interested in getting that driver, you can find it here: http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BE600707F28?opendocument&node=1...
Thanks again for the reply, let me know how things go-
Travis M
LabVIEW R&D
National Instruments -
We installed the LabView7.0 on Windows XP pro.
After we run the application and upon exit from LabView itself we are getting the error message saying:
The instruction at "0x64480386" referenced memory
at"0x00000004" . The memory could not be "read".
It never happened before on Win 2000 or NT.
What could be wrong?Hi Canadian,
If you search for "the instruction at" among the KnowledgeBases (www.ni.com/kb), you will find this KB that might help you solve your issue:
LabVIEW Application Error: The instruction at "[address x]" referenced memory at "[address y]". The ...
Let me know if you have any luck with nailing the issue, thanks.
- Philip Courtois, Thinkbot Solutions -
Stopping labview loop when terminating teststand
Hi,
If I have a labview step which is called from teststand, which is in a loop, what property can I query (or does one exist), where I can conditionally exit my labview loop when the "terminate" button is pushed in teststand? I see there are "termination monitor" tools in the teststand palatte in labview, but the "terminating" boolean does not go true when I initiate the terminate in teststand. I have a simple test vi set up to test it, does not seem to function this way.
Thanks
David J.
Solved!
Go to Solution.David
see attached example with TS 2010 and LV 2011. It shows how to use Termination Monitor and how to use LV modules to close asynchronuously running VIs.
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Attachments:
TerminationMonitor.zip 21 KB -
Can the dll built in Labview be called in labview
Hi
i built a Dll for the attached Vi and tried to call it in another vi. When i run this vi in which i called the dll, it exits the labview.
why is it so ?
Attachments:
try.vi 16 KB
tryi.bld 2 KBI have no problem in calling the DLL that's built. Did you specify the datatype correctly when you configured the Call Library Function Node? I've attached a VI that works.
Attachments:
CallDLL.vi 16 KB -
Can you run labview on Windows Tablet PC Edition?
Can you run labview on Windows Tablet PC Edition?...or does LabVIEW executable and Run-time engine operate with this OS?
LabVIEW 7.x will run without any problems on a Windows Tablet PC with SP1. There have been documented issues with Windows XP SP2 and LabVIEW subsequently not exiting properly--LabVIEW's window closes but somehow it is still present in the task manager.
Hope this helps. -
Hello,
Now i have little mosix cluster.
(debian 3.01, kernel: 2.4.20, mosix: 1.9.0)
If run executables from LabVIEW with system exec then
processes migrate fine to other computers.
But i havent Application Builder for Linux and cannot compile any VI.
Can anyone help me?
i need just some compiled vi, what can load processor some minutes. Like
this
for(i=0;i<10000;i++){
for(j=0;j<10000;j++){
for(k=0;k<100;k++){
One question more:
is it possible run LabVIEW on linux without X-windows.
Idea is just run one VI and when VI is complete, exit from LabVIEW
Deniss Karai
[email protected]LabVIEW does require X-windows to run. Also VIs are platform independent so if you can post the VI you want compiled. This way the kind soul that builds it will have a easier task. You should also note what version of LabVIEW you are using.
-
Is anyone else having the following problems? Any solutions?
LabVIEW 2013: Click Exit by any method (right click taskbar then click close, push the "x" button, file-->exit) and LabVIEW 2013 "starting" window remains open and does nothing
LabVIEW 2012: Close Exit by any method and the result is a brand new subVI
I have been resolved to close LabVIEW by ending the process. Surely I am not the only one to deal with this. I looked through forums, but only found close reference and close subVIs and what not.
Remember, code does exactly what you tell it.I realize this thread is a year old, but Labview 2012 is still doing this for me.
I'm on Windows 7 64 bit.
If I CTRL-Q the start page, it opens a new sub-vi. When I exit the sub-vi, it opens the start page. The X button in the upper right does nothing at all to the start page.
I was finally able to get it to fully quit by pressing CTRL-Q multiple times until the windows went away. Is there a fix planned for this, or is there a better way to exit that doesn't involve quitting multiple times or killing the task from the task manager.
Ro ma wa ichi ni chi ni shi te na ra zu -
Is there a way to close the VI front panel from inside the VI? I can
trigger an exit of LabVIEW itself, but can't find an event to close
the front panel.
Thanks.First off if you are going to build this into an exe then don't worry about it. but if want to close the vi programmatically then here is an example.
Hope this helps you out
Joe
Joe.
"NOTHING IS EVER EASY"
Attachments:
Untitled.vi 20 KB -
Okay so heres the problem i have a piece of code to convert a decimal value that a user enters into a binary value. My algorithm works its just when the binary value is displayed only the last element of the binary value to be outputed is displayed. But i want all the values of the binary number to be displayed. I dont know what to do plz help.
the code i am using is:
import java.awt.*;
import java.awt.event.*;
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStreamReader;
import javax.swing.*;
public class conversion extends JPanel implements ActionListener
JPanel board; // Panel for buttons
JLabel canvas; // Text Area for displaying answer
JButton convert, reset; // buttons
JTextField input; //input text box
public conversion()
super(true); // Call constructor of parent
// Standard layout (flow)
setLayout(new FlowLayout());
// Set up two panels, control board and canvas
board = new JPanel(true);
canvas = new JLabel();
board.setPreferredSize(new Dimension(100, 100));
canvas.setPreferredSize(new Dimension(300, 300));
board.setBorder(BorderFactory.createLineBorder(Color.black));
canvas.setBorder(BorderFactory.createLineBorder(Color.blue));
// Create buttons and attach listeners
convert = new JButton("Convert");
convert.addActionListener(this);
reset = new JButton("Reset");
reset.addActionListener(this);
input = new JTextField(8);
add(canvas); add(board);
// Add button to board panel
board.add(convert);
board.add(input);
board.add(reset);
public void actionPerformed(ActionEvent e)
String inputInfo;
inputInfo = input.getText();
if (e.getSource() == convert){ //action on convert button
//algorithm for decimal to binary conversion
int a = Integer.parseInt(inputInfo); //Gets decimal number inputed
if (a > 255){
canvas.setText("Please enter a number below 256");
else {
int b[] = new int[50];
int i = 0;
if (a / 2!=0 || a==1) //Checks to see if decimal number is divisible by 2
{ //Or exactly equal to 1
while(a!= 1) //While loop for when the decimal inputted is not equal to 1
b= a % 2;
a = a / 2; //Check to see if the remainder is divisible by 2
i++;
b[i]= 1;
for(int x=i;x>=0;x--)
//Displays the binary answer
int answer = b[x];
String stringAns = Integer.toString(b[x]);
System.out.println(stringAns);
canvas.setText ("The binary for your decimal is: " + stringAns); // this is the problem here, only the last element is displayed
if (e.getSource() == reset){ //action on reset button
canvas.setText("");
input.setText("");
//Graphics g = canvas.getGraphics();}
public static void main(String[] args)
// Create a Blob entity
conversion b = new conversion();
// Set up outer frame, and its exit behaviour
JFrame frame = new JFrame("Decimal to binary");
frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
// Set the main content frame to be the Blob,
// size the frame (pack) and make it visible
frame.setContentPane(b);
frame.pack();
frame.setVisible(true);pauze wrote:
for(int x=i;x>=0;x--)
//Displays the binary answer
int answer = b[x];
String stringAns = Integer.toString(b[x]);
System.out.println(stringAns);
canvas.setText ("The binary for your decimal is: " + stringAns); // this is the problem here, only the last element is displayed
Each element in the array b contains one digit of the binary representation. You need to convert each digit into a character and then concatenate all the characters into a String before displaying anything. -
Problem with User Data Entry Into a Control
I'm writing some code where the user must correctly enter numeric data for a number of parameters (eg wavelength, time, energy etc) before the program continues (eg via a 'click button when done' type command). I'm using a while loop to lock the done button out and hold progress of the program until all data entered is valid (eg using a boolean AND statement across all data input parameters) For example, the entered time must between 30-60 seconds and a boolean test on the time will remain low until the time is within this band.
Unfortunately, I've noticed that non-labview users do not click away from the control box (or use the tick box) when entering data, and a problem arises when they have establised valid data, bu
t then start to enter stupid data in a control field (eg time = -5 seconds). If they don't confirm the data input (eg by using the tick box) my boolean trap stays high and the done button is available to allow them out of the loop. Unfortunately, once on the other side of the loop, the control carries through time = -5 seconds, which of course screws up the analysis!!!
I have solved the problem in my own way, but my solution is not elegant, and users complain that the controls are 'clicky'. {And no, I can't tell them to enter the data properly!!!}
Has anyone come across a neat solution to this problem?For that specific example where you merely have to check the range, you can set the range properties of numeric controls before entering the loop. Then LabVIEW will automatically coerce user input.
For more complicatated validation, use the trick illustrated in the picture: the Stop button is fed to a shift register so the loop iterates one more time to validate inputs before exiting.
LabVIEW, C'est LabVIEW
Attachments:
validation.png 4 KB -
LV 2009 SP1 corrupts front panel VI during 'save' operation
My best guess is that corruption happens during 'save' operation.
Steps:
1. Slightly modify vi.
2. Run it, then stop and exit with saving of changes. (Saving takes unusual big amount time and cpu/memory resources)
3. Try to open vi and get the message "LabVIEW:Generic error... error code 3:Could not load front panel."
4. Exit from LabView
5. Start LabView and got the message "The last time you ran LabVIEW, an internal error or crash occurred at loaddata.cpp, line 3070"
Tried to reinstall LabView but it didn't help.
Any advice?
Thanks,
BorisThere were a lot of things that you did not post so I skipped through them.
Did a diagram clean-up and saved without issue.
maybe you should duplicate what I did (load with sub-VI and X-Controls adn save) to see if it is still corrupted for you. If not start adding stuff back in until you find what causing the crash.
So no crash on my machine.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction
Maybe you are looking for
-
Opening Closing CD Tray without Apple Keyboard
Hello, this is a simple question but I can't seem to find the answer. I switched to a Logitech G11 Keyboard for using in MSFT XP(bootcamp). I can open the tray by using the iTunes eject button. I have no way to close it except to manually push it in.
-
I have sent the email autentication at least 5 times and i have not received any email about the password reset. Is there anyother way i could do this?
-
I just bought a new Mac and need to download my lightroom without having to buy it again. Any help?
-
We are using 11g Grid Control and observing too many of these entries in emoms.trc file: XMLLoader8 E0_4325_79185.xml] ERROR loader.XMLLoader LoadFiles.792 - Error while processing E0_4325_79185.xml: java.sql.SQLException: ORA-20801: ECM load failed:
-
I guess it is not possible to send notifications to the Android status bar at the top of the screen? Any plans to add this feature to AIR?