Why does Labview Server shutdown during TestStand execution

Greetings All,
     Please forgive me if this question should've been posted on the TestStand side.
     What would cause the Labview Adapter Server to shutdown?  I've noticed that each time I click the Test UUT's (green execution arrow) button that during the analysis part before the client actually brings up the serial numbers screen, the Labview Adapter Server initializes.  The task bar would always show TestStand 2010 and Labview 2010 (Getting Started screen).  We are running a batch sequence that is monitoring four (4) uut's during an ESS profile and performing various testing at three (3) different temperature levels.  The process is kind of lengthy (2-1/2 days).  From what I could see the test was in a loop, as usual, waiting for a response from the thermal chambers internal relays which tell the TestStand program that the chamber has begun to move to the next temperature.  I notice that there was an ERROR displayed on the side of one of the batch sequences which was reading one of the PXI-6509 inputs.  I took a screen capture at that point before doing anything further.  I didn't notice it at first but looking at the screen capture again I noticed that Labview was missing from the task bar.
     I am wondering what could have caused this and if there is anything to prevent this from bitting me again.  This client sequence was running well for two (2) days and this happened with less than 12 hours of testing to go.  Thank you for any information that you provide with regards to this question.
Regards,
Scott

Hi snowpunter,
     Sorry I didn't get back to you sooner.
     Unfortunately there are too many users that think too much and close things before my team has a chance to look at the failure when it happens.  There is a remote possibility that someone closed the Labview application by accident.  There are many times that the Labview screen pops up in front of the TestStand screen while the sequence running and someone closed out Labview because they couldn't see the execution.
     It doesn't appear that there are multiple threads trying to access the PXI-6509.  The contractor that did most of the programming utilized a lot of Batch Synchronizations to prevent this kind of thing from happening, not that it isn't possible.
     I'm wondering if there is a way to disable the operator from shutting down Labview, whether by the RED "X" in the top right corner or Menu-File_Close.  If so, How would I accomplish this?  Thanks in advance for any reply you have to offer.
Thanks,
Scott

Similar Messages

  • Why does LabVIEW allow me to have 2 controls with same name

    Here's a general LabVIEW question:
    Why does LabVIEW allow me to have 2 controls with the same name in the same VI?  It seems like this only increases the chances of confusion.  Especially when someone is just looking at a block diagram (or documentation of a block diagram).
    No other programming language that I know of allows this.  I realize that uniqueness of name is not as critical in LabVIEW as it is in any text based language.  For example, in a text based language, if I had 2 variables called abc and I wrote a statement
    abc = 12;
    the compiler would not know which abc was being referred to.  In LabVIEW, if we had 2 controls called abc, the equivalent of doing an abc=12 is writing to a local variable (which is always linked to one of the controls) and there is no ambiguity.  Still, someone looking at the code cannot figure out which abc is linked to unless he does a right click>>Find>>terminal (or a double click).
    Even though I have never and never will name 2 controls the same, I think it would be a nice constraint to see enforced by LabVIEW.
    Any input from NI engineers on this?
    Message Edited by S G on 12-18-2007 03:38 PM
    S G
    Certified LabVIEW Architect, Certified TestStand Developer, Certified Professional Instructor
    Attachments:
    Trial1.JPG ‏21 KB

    I know when you copy and paste a control or indicator, LabVIEW automatically increments the label. But since you can hide the label, and show or hide the caption, there must be another mechanism that LabVIEW uses to keep track of all the controls. I thought I remember back in the "old days" (ver 6 or 6i) LabVIEW would give you an error if you tried to make two controls with the same name. Perhaps that was LabWindows/CVI.
    I don't know where the index is actually stored, but if you look at a property node linked to the Pane, you will see an array of references to the controls and indicators. Since the references are stored in an array, I assume that any local variables are tied to the index of that array. Since the labels themselves are properties of the control, I guess there's no reason to limit what that label is. They all have a unique index number.
    Interestingly, this array of references grows from the beginning. That is, any new control or indicator is put at index 0, not the end of the array.
    B-)
    Message Edited by LabViewGuruWannabe on 12-18-2007 08:45 PM
    Attachments:
    Labels.png ‏12 KB

  • Why does Labview allow a cursor in a indicator?

    Hello,
        Why does Labview allow the user to position the cursor with the mouse inside a numeric indicator? Users think that just because they can put a cursor they should be able to type something and enter data. Is there a way to disable/stop the user from putting the cursor in a numeric indicator?
    Regards,
    Kaspar
    Solved!
    Go to Solution.

    Disabling the indicator satisfies your requirements, but this is funnier.  It would be even better if I calculated the position of the indicator and the "entry point" and just kept the mouse from entering, but I have a project to finish... 
    Message Edited by jcarmody on 03-27-2009 11:58 AM
    Jim
    You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
    Attachments:
    move.png ‏4 KB
    test.vi ‏9 KB

  • Why does my computer shutdown while entering my email address after downloading x?

    Why does my computer shutdown while entering my email address after downloading x?

    Why does my computer shutdown while entering my email address after downloading x?

  • For Experts: Why does LabView cause System reboot while accessing hardware with driver?

    Hello NI Developers!
    I use LabView 7.1 under Windows XP
    I have a programm console application which accesses through Jungo Windriver PCI-E board.
    This program works fine - and performs DMA data transfer between PC and Board's memory.
    In order to implement this console application work together with LabView I did following:
    1) Added this function inside the source:
     _declspec(dllexport) void LVMainFunction(uInt32 *IntValue);
    _declspec(dllexport) void LVMainFunction(uInt32 *IntValue)
        AllocConsole();                   //Open new console window
        SetConsoleTitle(L"Debug Window"); //Set a title for console window
        freopen("CONOUT$","a+",stdout); //redirec standard output stream to current window so
                                        // so we are able to see "printf" outputs
       freopen("CONIN$","a+",stdin);    //redirec standard input stream to current window so
                                        // so we are able pass inputs from keyboard
       main();                          //Call applications main function which does all the work
    2) Compiled this new source as DLL library
    3) Call  LVMainFunction(...) function from LabView using Call Library Node
    In the result: Executing VI - opens new console window, shows debug outputs and receives keyboard inputs.
    It works fine till the last function, which perform DMA data transfer - and reboots PC.
    1) Why does this happen?
    2) I understand that opening console from Call Library Node, attaches together this console window and running VI. So If I close one of them - both windows closes.
         So does LabView have somekind of restrictions of accessing Hardware's functions? 
    I can read Board's resource information and view size of memory on board, interrupt functions and other information about device, but when I try to reach
    DMA my system reboots. And I understand that this should be some kind of LabView problem, cause I tried different implementations, even without use of
    console window - and the result is the same.
    3) Should I split the program in to two separate processes and perform data exchange using Sockets or Pipes techology?
    Thank you in advance!
    ACiDUser
    Message Edited by ACiDuser on 11-13-2008 09:37 AM

    Hello!
    At LAST!!!
    I solved this problem!
    From the beginning I was following National Instruments manual on how to build DLL with external IDE:
      http://zone.ni.com/reference/en-XX/help/371361A-01​/lvhowto/building_library_project/
    Set the Struct member alignment control to 1 Byte.
    Now this option caused my PC to reboot!
    So could someone explain  why this happened? and If it is a bad tip, so it's better to remove from manual. Then other people will not have such problems as I did
    - wasting 2 monthes of time determining the problem. 
    I changed it to  Set the Struct member alignment control to DEFAULT.
    and now everything works fine.
    Regards
    Message Edited by ACiDuser on 11-13-2008 11:14 AM

  • Why does my system freeze during reader install on windows 7

    why does my windows 7 system freeze during adobe reader installition

    Is is hard to say. It could be anything from a corrupt font, interference from virus protection, corruption due to a virus, hard disk directory problems, etc. Are you able to download the full installer? Did you have a previous version of Reader on your System? What version of Reader are you trying to install?
    Generally, if you clean your system of previous versions and bad installs:
    http://labs.adobe.com/downloads/acrobatcleaner.html
    You can then install. Try using this installer:
    http://get.adobe.com/reader/enterprise

  • Why does LabView crash when unloading my DLL (reentrant calls)?

    I have written a DLL in Borland Delphi using multiple threads that exports several functions (stdcall). I am using LabVIEW 6i on a WinXP machine.  All functions in the DLL work as expected and return correct values. Everything works fine if I set all Call Library Function Nodes to 'UI-Thread', but as soon as I set one Function Node to 'Reentrant', LabView crashes when I close the VI after it has been executed. I assume the error is caused by the DLL unloading mechanism of LabView. Other C++/Delphi programs using the DLL reentrantly work fine, this only occurs in LabView. In which thread does LabView call FreeLibrary/DLL_PROCESS_DETACH? Has anyone experienced similar problems?

    I have never run into this situation myself, but I do know that calling a multi-threaded DLL or CIN from LabVIEW does depend upon the following criteria:
    If your CIN/DLL doesn't have any global data storage (global variables, files on disk, etc.), AND it doesn't access any hardware (register-level programming) AND it doesn't call any functions/DLLs/Drivers that are thread-unsafe.
    OR
    Your CIN/DLL protects (with semaphores or mutex's) access to those global resources.
    OR
    Your DLL is only called from one, non-reentrant VI
    OR
    Your CIN is only called from one, non-reentrant VI AND you don't access any global resources from CINInit, CINAbort, CINDispose, etc. procedures.
    Hopefully this information can help you out in some way.
    J.R. Allen

  • Why does the server hang while starting up or the "csdb recover" hang when it is run?

    Sometimes after iPlanet Calendar Server crashes, the server hangs during
    startup or the csdb
    utility hangs when I execute the recover
    command.
    <P>
    One possible solution is to delete all of the .share
    files in the same directory as the
    Calendar Server database. In most cases, the server will successfully start up
    again.

    When you start up in Safe Mode various things aren't loaded at startup, Bob.
    Have a thinbk about which of the following may be involved in your own case:
    It forces a directory check of the startup volume.
    It loads only required kernel extensions (some of the items in /System/Library/Extensions).
    It runs only Apple-installed startup items (some of the items in /Library/StartupItems and /System/Library/StartupItems - and different than login items).
    Mac OS X 10.4 Tiger only: It disables all fonts other than those in /System/Library/Fonts .
    Mac OS X 10.4 Tiger only: It moves to the Trash all font caches normally stored in /Library/Caches/com.apple.ATS/(uid)/ , where (uid) is a user ID number such as 501.
    Mac OS X 10.4 Tiger only: It disables any Login Items.
    (from http://docs.info.apple.com/article.html?artnum=107392)
    Have a look at http://docs.info.apple.com/article.html?artnum=106464 for some more possibilities.
    You may find it worth while using System Prefernces/Accounts to creat a new admin user account and see if the problem persists with it. THis may help you narrow down the problem further.
    Cheers
    Rod

  • Why does Labview VI pause intermittently during motor control while loop?

    I'm performing some biomechanical testing using Labview to control stepper motor actuators. I have a PCI-7334 controller card and a MID-7604 driver. The testing is run in load control using a while loop that sends a number of steps to the stepper motor that is proportional to the difference between the actual and desired load. The VI intermittently pauses though and sits in active for several seconds (~5 sec to 20 sec). What could cause this problem?
    Thank you in advance for your assistance.

    Without the subVIs it is hard to see what is going on.
    Some general comments:
    1. Block diagrams should be limited to the size of one screen.  Yours is over 4 times as wide as my 27" screen.
    2. Sequence structures should be avoided.  LabVIEW is a datflow language and only rarely are sequence structures required. There is almost certainly a way to write your program without them.
    3. The use of local variables should be avoided.  Again, they have a place but most likely they are not needed in your program. They are prone to race conditions, make extra data copies, and force execution in the UI thread.
    4. Floating point data types are not recommended as case selectors. They will be rounded and coerced to integers.
    5. Learn about the Producer/Consumer Design Pattern and state machines.  
    One possible cause of your slowdown is having the Write to Spreadsheet File.vi inside the while loop. This VI is convenient to use but it opens, writes, and closes the file each time it is called.  I have no way to tell how much data you write on each iteration but as the file grows the OS may need to re-allocate space for the file or fragment the file. These operations can be slow.
    Do you really want to Abort the program in the False case?  This will leave any outputs in the last state they had been set. This could have your motor(s) running, clutch engaged, ...  In programs which control physical hardware an orderly shutdown procedure is usually better: set all outputs to a safe condition, close files, close DAQ tasks, and indicate the status to the user.  Calling Stop allows none of this to happen.
    Lynn

  • Why does Labview hang when switching from one TestStand application to another?

    I have several 2013 TestStand applications that use a number of LabView 2013 VIs on a test computer.  When the operator closes one TestStand program and opens another often Labview does not close properly and so when TestStand tries to load the LabView VIs it hangs or just runs and every test that is affected by LabView fails.  The only potential issues that I know about are that two of the applications were created in LabView 2009 and then updated to 2013.  Then two other TestStand applications that were created in 2013 use the function "UnloadAllModules". 
    Are there any known issues with LabView 2013 that cause this or any ideas of what I might be doing wrong?
    Solved!
    Go to Solution.

    Hello Michael,
    I did find my issue.  In my case a VI was not getting closed properly in cleanup due to the previous command not passing the handler out correctly.  Thus this VI would remain open and when I ran another TestStand Sequence, when it tried to load that LabView VI it would just hang.  But the result of this error could be seen when I closed TestStand and LabView stayed open (since it was frozen) or when done running the sequence and closing it.  Then if you tried to pop-up LabView it would not show the starting splash screen because it had froze.
    I found the problem by turning on the show VI front panel option in TestStand for all of the VI calls.  The VI that stayed open was the problem VI.
    Thanks everyone who responded for your help!
    Kurtus

  • Why does DNS server entry in ipconfig break point-to-point ethernet?

    My application uses a panel pc as the user interface for a cRIO controlling a medical device.  The panle pc and cRIO communicate using shared variables.  During development, both devices (panel pc and cRIO) were on our company network.  Curiously, when I connected them point-to-point with a crossover cable, they refused to communicate when running their LabVIEW application code.  Pings from the panel pc to cRIO were successful.  Much troubleshooting ensued.
    Long story short, the fix was to simply delete the DNS server IP entry from both the panel pc and the cRIO ipconfig tables (see attached pic for the WinXP version of this table).  If either of them had our company's DNS server IP address fillied in, my LabVIEW application would fail.
    This leads me to suspect that there is something in my LabVIEW executables that wants to touch the company network.  Apparently, if there is a DNS server entry in the ipconfig table, this something thinks it has a chance to "phone home" and it tries to do so.  When this happens on the panel pc end of the crossover cable, the machine acts like it's locked up, but the task manager shows the CPU to be ~98% idle.
    If there is no entry for a DNS server, I guess this something realizes that there is no way to "phone home", so it doesn't try and my application works great.  Since the application works with no DNS server table entry, I think my crossover cable is working correctly.
    Does anyone have any idea what this something might be?
    Jeff
    Climbing the Labview learning curve!
    Sanarus Medical
    Pleasanton, CA
    Attachments:
    IPform.gif ‏12 KB

    You've hit the nail on the head Ben.  For point to point communications, the IP addresses should be fixed, therefore there is no need for DNS.  If a DNS is configured, the NIC (Network Interface Card) drivers will try to contact it.
    In my test system, I need DNS for the test computer, but I am communicating with a dedicated Spectrum Analyzer over TCP/IP.  So I added a second NIC.  The main NIC is configured for DNS and all that jazz.  The second NIC (plugged into PCI slot) is configured with a hard coded address, no DNS, no Gateway, nothing else.  I connect that NIC to the spectrum analyzer using a crossover cable.  The analyzer is configured with a hard coded address also.  Now my computer can get on our company network, and the spectrum analyzer is isolated from the network, so it can't catch any viruses, etc., and it still talks to the computer.  When using a configuration such as this, it is best to use a dedicated address for the 2nd NIC and spectrum analyzer in the range of 192.168.100.0 to 254
    - tbob
    Inventor of the WORM Global

  • Why does labview close whilst my program is running?

    I am running a program doing data acquisition using the PCI-6602 cards. Everything works fine but somehow after I have been doing acqusition and saving the data for approximately 2 days, I find out that the program has been stopped by LabVIEW and find all the windows closed including labVIEW. In my program I did not use any of the exit functions provided with LabVIEW but somehow, labVIEW exits by itself without issuing any error messages. Why is this happening?

    I experienced a problem with LabVIEW 7.0 shutting down unexpectedly.  It may be completely unrelated, but I thought I'd mention it just in case.  My problem was that I was calling a DLL that used a reference handle.  At the end of my test (using TestStand), the test closed, and thus the DLL was unloaded from memory as well.  Because there was still a handle open to this DLL, LabVIEW must not have known how to handle this and shut down (or it confused Windows and it shut down LabVIEW).  In any case, the solution was to have a VI stay in memory which calls this DLL, and put the DLL in a the true case of a case statement wired with a constant false.  Thus, the DLL is never actually called by this VI, but it keeps the DLL in memory.
    So if you call any VIs dynamically, etc., where a VI could be unloaded from memory, check those VIs and make sure you aren't leaving any references open or something like that.
    Hope this is in some way helpful.
    Tom

  • Why does while loop pause during operation

    Hi everyone,
    I have written the attached code which will eventually be a part of a bigger program. The program is intended to log some test value, in this case just the date and time  to a csv file  when a button is pressed (log in WHITE, loop1).  Loop2 is intended to read a test value from a line in the first csv file and then add an extra test value to the end of that line when the serial number matches and then saves that line to a new csv file. This all works well but loop2 seems to pause a few times before continuing when either of the log button is pressed. I tried putting the code in 1 while loop with no success. Can anybody see what I am doing wrong?
    Attachments:
    ResinV10_csv.vi ‏25 KB

    Maiz wrote:
    Can anybody see what I am doing wrong?
    In addition to waht has been said already, your code is extremely convoluted.
    How often does the "read" file change? Do you really need to read the entire file with thousands of rows every ms just to look at one row?. If the file never changes, you could read it once before the loop.
    The way do do array opearions is mind boggling. You take one row, Index out the first element twice in parallel (once is enough!), then you index out the first element, built it into an array of one element, and compare that array with a scalar. Would't comparing the orignal element with the scalar be equivalent?
    Index array is resizable, you only need one instance.
    Getting five elements in a row just to build them back into a 1D array seems rather pointless. If the array has only five elements, there is nothing to do, and if it has more elements, you cold use "array subset", and if it has fewer elements, use "reshape array" to size 5.
    The correct format for reading strings is %s (not %.10f).
    Since you want both loops to run at the same speed, why don't you put it all in one loop? (this even eliminates the local variable) Then you could use a parallel loop for the file saving, using queues in order not to slow down the main loop. In the parallel loop, open the files before the loop, use lowlevel writes inside the loop, and close the files once the program stops.
    Can you explain your setup and what the program is supposed to do? I am sure it could be done with 20% of the current code.
    LabVIEW Champion . Do more with less code and in less time .

  • Why does Vine Server not start with this script and work with the other?

    I have the preferences of Vine Server set to start/run automatically when opening the programme.
    If I double click the icon it works. Opens and starts.
    If I use
    activate application "Vine Server"
    it opens but does not start.
    If I use:
    tell application "Finder"
    activate
    open application file "Vine Server.app" of folder "Vine Server 3" of folder "Applications" of startup disk
    end tell
    it opens and starts.
    Anybody any idea as to why?
    This seems to happen since I upgraded form 10.4 to 10.5.

    Hello
    Do you have multiple versions of Vine Server application, perhaps?
    If so, that might cause the described behaviour.
    You may try using full path to the current Vine Server application such as -
    activate application "/Applications/Vine Server 3/Vine Server.app"
    or -
    tell application "/Applications/Vine Server 3/Vine Server.app" to activate
    H

  • Why does LabView dll not work in C Thread?

    Hello Everybody,
    I want to use a LAbView Application as Dll in a Console Application.
    There is an Example Available (DLL_Example.zip)in (Displaying the Front Panel of a LabVIEW-Built DLL Function)
    When I use this Example in a Windows Console Application, it Works fine (It is important for me, to see the LV Window!)
    Code example:
    /* Example Start *******************************************/
    int main(int argc, char* argv[])
    double Y = 4;
    double X = 5;
    double Result = 0;
    SimpleCalculator(1, Y, X, &Result);
    printf("Result = %f", Result);
    return 0;
    /* Example Stop *******************************************/
    When I use the function "SimpleCalculator" in a Thread, the LabView Window never appear, what's wrong?
    Code example:
    /* Example Start *******************************************/
    DWORD WINAPI LVThread(LPVOID lpParameter)
    double Y = 4;
    double X = 5;
    double Result = 0;
    SimpleCalculator(1, Y, X, &Result);
    printf("Result = %f", Result);
    return 0;
    int main(int argc, char* argv[])
    DWORD ThreadID;
    CreateThread(NULL,0,LVThread, NULL, 0, &ThreadID);
    getchar();
    return 0;
    /* Example Stop *******************************************/
    I'm using Microsoft Visual Studio 6.0. and LabView 7.0
    Thanks for every help.

    bobby wrote:
    Hello Everybody,
    I want to use a LAbView Application as Dll in a Console Application.
    There is an Example Available (DLL_Example.zip)in (Displaying the Front Panel of a LabVIEW-Built DLL Function)
    When I use this Example in a Windows Console Application, it Works fine (It is important for me, to see the LV Window!)
    Code example:
    /* Example Start *******************************************/
    int main(int argc, char* argv[])
    double Y = 4;
    double X = 5;
    double Result = 0;
    SimpleCalculator(1, Y, X, &Result);
    printf("Result = %f", Result);
    return 0;
    /* Example Stop *******************************************/
    When I use the function "SimpleCalculator" in a Thread, the LabView Window never appear, what's wrong?
    Code example:
    /* Example Start *******************************************/
    DWORD WINAPI LVThread(LPVOID lpParameter)
    double Y = 4;
    double X = 5;
    double Result = 0;
    SimpleCalculator(1, Y, X, &Result);
    printf("Result = %f", Result);
    return 0;
    int main(int argc, char* argv[])
    DWORD ThreadID;
    CreateThread(NULL,0,LVThread, NULL, 0, &ThreadID);
    getchar();
    return 0;
    /* Example Stop *******************************************/
    I'm using Microsoft Visual Studio 6.0. and LabView 7.0
    Thanks for every help.
    Check out luciangeeks's explanation elsewhere on this forum in several threads about the message loop needing to be pumped by the intial thread starting up the LabVIEW runtime system. In Windows console applications the hidden startup code linked in from the C runtime library to intialize the environment before passing control to the console applications main function also contains a message loop, polling the Windows message queue to among other things translate those messages into keychars so that the C runtime library function getchar() and friends can work as expected. It also makes the console application look responsive to the Windows system so that Windows doesn't think it would need to shutdown the application. LabVIEW DLLs really running as GUI components can't work without an active message loop making sure those system messages are retrieved and distributed to the according (usually hidden) VI windows. However the setup in Windows makes it such that a DLL sort of inherits the message loop of the thread which first entered that DLL. If that thread does not have a message loop, LabVIEW windows simply can't work properly and this means that the LabVIEW code is not managed properly and therefore won't run.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

Maybe you are looking for