Labview inconsistently crashes, Zaber T-LSM linear stages

Hello All,
I am trying to run 2 Zaber linear stages for a 24 hour period using the attached VI (relevant portion is the second while loop), but the VI has failed at various times after initiating the program. The longest they're run without interruption is 6.5 hours, but it often fails anywhere between less than 1 minute to over an hour. I've also gotten a blue screen immediately after clicking run on one occasion. When the VI fails, the run arrow at the top left of the screen is solid black, but whenever I click on pause or abort the program doesn't respond. The only way to get Labview running again is to close the program using task manager and restart the computer.  I'm thinking it might be an issue with the computer I'm using, but I'm not sure. Any advice would be greatly appreciated.
Sincerely,
Tom
Attachments:
cycle3.vi ‏40 KB

Hi tseykora,
Thanks for posting. I'm running a test here with your code on some Zaber devices to see if I can reproduce the issue. 
A note on the other comments, for this application there is a purpose for the two-way 'Request' vi followed by a 'Read' vi. For Zaber devices, Device 0 is used to send the same command to all connected devices. The Request vi waits for the first response (after one axis completes it's movement) and the Read waits for the second response. An alternate way of handling it is to change the final '1' in the input clusters of the Requests to '2'. This input indicates how many responses are expected. 
Waiting for these responses that come at the end of a movement allows the loop to pace itself; the commands are not being sent as quickly as possible in the main loop of your VI.
The initial loop is not set up optimally though. As gregoyj noted the initialize should come before the loop, and the Move Absolute command only needs to be sent once.
I've attached the slightly modified VI. These differences shouldn't have caused a crash as you were seeing though. I'll post again some time between 6 minutes and 24 hours from now.
Mike McDonald
[email protected]
Applications Engineer
Zaber Technologies 
Attachments:
cycle3.vi ‏38 KB

Similar Messages

  • Looking for a motorized linear stage actuator to travel 4cm.

    Hello.  I am looking for a motoized linear stage or actuator and I want to use Labview to control the motion since I am comfortable with it, so I thought what better place to ask for help!
    I will need everything (motor, drive, cables, etc) since I have never done this before.  I am currently trying to find a motorized solution that will move horizontally 4cm, and will quickly stop and start ~50 times during the motion.  I have looked at several linear stages and actuators, and it looks like a stepper motor with open loop feedback will be best fit my needs since the position accuracy isn't much of concern.  Let me breifly describe some of the requirements: It needs to complete a 4cm total distance in only a few seconds (at least less than 5s but less is better), the position accuracy/resolution only needs to be 0.1mm, I would like to use  Labview to easily programically control the entire motion, the total cost (drive, motor, cables, etc.) should be low, the total load is only a few pounds, and it should have a small footprint.
    So far the best solution I have found is the Zaber motorized linear stage part number KT-L-SQ75D for $2,025.00  http://www.zaber.com/products/product_group.php?gr​oup=T-LSQ  An engineer from Zaber performed the following test: Each move distance was set at 0.8mm (total of 4cm). Using the fastest speed setting (595mm/s), the stage was able to complete the entire move sequence in about 2.75s.  So far this is the best I have been able to come up with by myself and I would greatly appreciate anyones advice on a better solution or their own experience with this product/company.  Thanks for your input.
    Kevin

    Hello again everyone.  I just wanted to provide an additional update to my last post.  I have also been talking with someone who suggested a Parker stepper driven lead screw stage, model:  Promech LP28 with 50mm travel with limit switches http://divapps.parker.com/divapps/emn/pdf/PROmech.​pdf.  The suggested that I could use the IMS MForce Microstepping Drive as the most economical drive solution http://www.imshome.com/products/mforce_microdrive_​mfi.html, or a galil driver.  It seems that the IMS doesn't have as much labview support (only a few VI's) http://www.imshome.com/support/mdrive/programs/MCo​de_LV_86.zip, but the Galil drivers seem to be very easy to use with labview http://www.galilmc.com/support/appnotes/software/n​ote4414.pdf.  I don't know how much the Parker Promech stage was quoted at $600, the IMS drive at $250, and I don't know what the Galil driver cost but I was told it is more, and ~350 for cables and a power supply.  
    The reason why I hesitate to use this is because it seems to not be in a single package like the Zaber product I mentioned in my last post, and I don't know if it will be as quick.  The engineer that is trying to sell the Parker stage said that it should be able to move 0.8mm in 0.08s, but how long would it take to make 50 consecutive 0.8mm movments?  Would it be 0.08s*50=4s?  Also even then it takes longer than the 2.75s than the Zaber product, so I wonder if it could move faster?  Anyone use this product to know the fastest it should be able to make this motion.  Also I am not very concerned with the stability when it is stopped and started, because even if it vibrates a few microns it shouldn't be a problem since my resolution/accuracy concerns are on the order of 0.1mm not microns.
    Thanks again for any other suggestions that would also work, or any first hand knowledge of any of these products would be greatly appreciated so I can decide which to purchase.
    Kevin 

  • Stepper Motor with Linear Stage (Position Control and Data Acquisition)

    Hey All,
    So.. I've attached a stepper motor to a linear stage and so far it's working pretty well.  Using a stepper motor driver from Pololu, I've simplified the control of the motor by just using output pulses from the counter output of a PXI-6143.  I've tested the motor using the Pulse Train examples in LabVIEW and all is working well.  
    My goal now is to allow the user to collect data from a pressure sensor, attached to the linear stage, every X number of steps.  From what I can tell so far, and please correct me if I'm wrong, the motor step movement is synchronised with the pulse train input.  That is to say, if I give the motor a 200 step pulse train, the pulse train ouput is completed at the exact time the motor has moved 200 steps.  From this, I've created a VI that moves the motor X steps, aquires the data point, and then repeats this process for the required amount of data points.  The problem with this is that the motor movement is not continuous; it stops for a split second to take the data point.
    How can I have labview ouput a pulse train of say 1000 steps and record a data point every 50 steps?
    Two ideas that came to mind were:
    1. Use the counter input port on the card to count the pulses being sent to the motor.  
    2. Use an encoder connected to the motor shaft.
    I wanted to stay away from theses ideas though since they require resources from the DAQ card.  
    Thanks,
    Ryan

    Hi Ryan,
    Just to cover all the bases, what version of LabVIEW are you using and can you attach your VI? Initially your ideas sound like they should work, do you expect to be nearly maxing out the DAQ?
    Thank you,
    Deborah Y.
    LabVIEW Real-Time Product Marketing Manager
    Certified LabVIEW Architect
    National Instruments

  • LabVIEW is crashing when i am trying to build the exe

    I am trying to build an executable from a program in which i am communicating with several instruments, whenever i am trying to build an exe labview is crashing and i am getting the error Exception: access violation(0xc0000005)at eip=0x10054DD1.
    after reading some posts on forum i tried builduing an exe on other system also, but still i am getting the same error.
    below i am attaching the program and the image of the error i am getting.
    Attachments:
    labview crash.png ‏53 KB
    automation.zip ‏4455 KB

    Ritu wrote:
    waiting for the reply....
    Realize this community is by a large majority volunteer based.  If you need urgent support contact NI directly 
    http://sine.ni.com/apps/utf8/nicc.call_me?loc=en-US
    That being said I would try to disable the large amount of code.  Say you have a Main that launches a bunch of stuff, put a disabled diagram code around the launching part and then try to rebuild.  It is a very slow process (especially when the build takes a while to fail) but by doing this you can more isolate the parts of the code that can cause the crash.  The only time I've seen a crash on build like you described, I simply rebooted and it was fine.  Usually because of my own fault by stopping code in a bad way previously leaving things in memory.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

  • LabVIEW 2009 crashes at startup with the presence of a certain CRT version on the system

    When installing our LabVIEW integration package on a system running
    LabVIEW 2009 LabVIEW will crash at startup afterwards. Using 'dependency
    walker' reveals, that 'nicont.dll' causes this crash because of a
    side-by-side configuration problem. After some debugging I found out
    that on this particular system installing a certain version of the
    Microsoft CRT will stop LabVIEW from functioning. My fix now is to
    recompile our code with a newer version of VS. I now ship a VS9 version
    of the runtime and everything is working as expected.
    However
    I guess the real problem lies within the LabVIEW installer. I guess a
    needed version of the CRT is not installed by LabVIEW. It still works
    because due to some policy files on the machine it gots defaulted to a
    compatible version at startup. However when I install the following 2
    merge modules on the target system LabVIEW does no longer work:
    Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.762)
    policy_8_0_Microsoft_VC80_CRT_x86.msm (file version inside: 8.0.50727.4053)
    Renaming
    the *.policy file in the SxS dir on the target system gets LabVIEW back
    to run, but of course other SW needing this file does not run then
    I was using XP, 32 bit SP 3
    I can provide additional information if needed. Is this a known problem? Is there a fixed version of LabVIEW already?
    Message Edited by anotherStefan on 02-05-2010 05:44 AM

    Sure! I tried to attach the installer causing the problem to this message.
    However I failed miserably(BAD GATEWAY from the upstream server). Where can I upload the installer to or what do I need to do?
    It will install some other stuff as well (A bunch of VIs, a DLL and an
    OCX(this needs the CRT I have trouble with)and the CRT and MFC runtimes I
    mentioned. An updated version of the installer can be obtain here(however it does no longer show the issue):
    http://www.matrix-vision.com/functions/count.php?url=products/hardware/family/SC/mvBlueFOX/LabVIEW_a...
    The only difference between the two packages is, that the OCX in the
    attached file has been build using VS2005SP1 and in the package the link
    points to I did use VS2008. Apart from that I changed the 2 merge
    modules from Microsoft (CRT and MFC)

  • Running the VI causes LabVIEW to crash

    Hello
    While debugging a SW, I found that a particular VI, when run, causes LabVIEW to crash. This happens whether this VI is called while executing an exe or called by higher VI or even when it is run separately.
    The VI to be run is NLD_Test_PP_Plot.vi present in the folder "Generic VI's".
    The input for this VI is .csv file, which is attached. The csv file needs to be placed in a separate location and that path needs to be entered in the string constant in the VI.
    Note: This VI is developed and run in LV v2009.
    Thanks
    Sharath
    Attachments:
    SpecimenCW_20150407_193059.csv ‏67 KB
    NLD_Test_PP_Plot Folder.zip ‏208 KB

    LabVIEW did not crash for me (nor did it throw an error).  It made a bmp of your data and then exited.  I am using LV 2013.
    Did it actually crash or did it throw an error?  If it crashed, do you have the crash zip file?
    Bill
    (Mid-Level minion.)
    My support system ensures that I don't look totally incompetent.
    Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

  • Deny Access function with invalid file refnum causes LabVIEW to crash

    Hi folks,
    I have LabVIEW 8.5, and today encountered something interesting that consistently causes LabVIEW to crash.  Essentially, if you find the "Deny Access" function under the advanced file IO palette and wire up an invalid refnum, Windows (XP in my case) reports that LabVIEW has to close.  I checked in task manager, and the LabVIEW process is still active and using a disproportionate amount of the CPU.
    To reproduce the issue, simply drop the function on your block diagram, create a constant from the refnum input terminal, and run the VI.  Has anyone else seen this behavior?
    Thanks,
    Jim

    Hi Carla,
    I'm glad to help, and thanks for looking into it.  The way I ran into the bug was while I was working on an action engine VI to log certain text values (see attached picture).  While logging, I didn't want other programs to access the file.  When a new file had to be generated, I wanted to stop denying access and close the reference.  However, if the value on the shift register was invalid, LabVIEW crashed instead of throwing an error (I guess a crash qualifies as an error).
    If you look at the attached picture, my workaround was to use the "Not A Number/Path/Refnum?" function.  If the reference is bad, I don't try to use the "Deny Access" funtion or close the file.  That worked just fine and seems like a good solution for now.
    Jim
    Attachments:
    Logger.png ‏6 KB

  • Flash Crashes on clicking import to stage

    I'm having an issue with a blank open document, clicking on 'import to stage' will crash the program or clicking on 'import to library' will crash the program.  I have tried uninstalling CS4 and re-installing CS4. The problem remains the same.
    Any ideas, I'm desparate.
    Thanks.
    Al

    Hi Peter,
    Thanks for the reply, and yes I can copy and paste. I did find a post that
    mentioned compatibility mode which I did try and it cleared everything up.
    The strange part to this is that everything worked fine until a few days
    ago. I think it may have to do with all the security patches that the
    company I work for jams down our systems on what seems like a weekly
    basis. But thanks for the reply, I do appreciate it.
    Al
    From:
    PJSB_DK <[email protected]>
    To:
    Alan Fiterman <[email protected]>
    Date:
    08/19/2010 02:54 PM
    Subject:
    Flash Crashes on clicking import to stage
    Hi
    Will it crash if you try copy/paste?
    Have you applied the latest patches/upgrades?
    Best regards
    Peter

  • Labview 2013 crashing when restarting VI

    My VI runs and I have no problems.  
    If I stop then Vi and re-run it, pretty much every second time it crashes.  It does not point to anything and the only message I get is:
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: LabVIEW.exe
    Application Version: 13.0.0.4051
    Application Timestamp: 525595c6
    Fault Module Name: NiViPxi.dll
    Fault Module Version: 5.4.0.49152
    Fault Module Timestamp: 51c243ad
    Exception Code: c0000005
    Exception Offset: 0000bbe0
    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 6153
    Additional Information 1: 0a9e
    Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
    Additional Information 3: 0a9e
    Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt
    This only clue in the above I can find is NiViPxi.dll
    I am using a PXI rack so maybe it is to do with one of the devices?
    I would be nice to have more clues, does anyone know why labVIEW keeps crashing?
    Rgds,
    Sean
    Solved!
    Go to Solution.

    Hi jinfone.t
    I managed to root cause it to a netway 72 PXI dll and have fixed the issue, (took a lot of effort!)
    - Does the crash only occur when you re run this particular VI that you are talking about?
     Yes
    - Is there any crash logs generated?
     None that I know of apart from the output I pasted on the screen.  It's possible there is something in the event monitor
    - What does your VI do? 
    It function tests our product, (IOT)
    - Would it be possible to show the code? 
    I'm afraid not as it is proprietary.  However, the issue appears to be due to the dll.  Netway may release the VIs but I believe you are required to buy hardware/ software.
    The issue I have is that LabVIEW is not handling this crash well at all.  It does not point to the problem dll nor does it drop a fail log that I know of.
    Thanks for the feedback.
    Ciao,
    Sean

  • Minimize the chattering of a linear stage driven by a voice coil actuator(V​CA)

    I have a linear stage driven by a voice coil actuator (VCA), a capacitive probe is used to measure the movement of the stage. A picture is attached to show the basic mechanical design of the stage. Even though the resolution of the VCA is 0.5 um, the overall resolution of the stage is not that good. When I use controllers to achieve position controller of the stage, the stage is always chattering around the set value. It can only achieve 5 um in open loop and around 10 um in PID control. Is there any method to improve the performance by modifying the controlling VI? 
    I am using NI 6363 to give voltage signal to a LAA amplifier and the amplifier will convert the voltage signal to current signal and drive the VCA. It seems that the output of the LAA amplifier is not constant and it is the LAA amplifier that generate those chattering. The command voltage given to the amplifier is extremely constant with error less than 2mv, which will cause only 0.5 um displacement of the stage by theory. Such kind of motion is similar to the resolution of the sensor but it is only 1/10 of the actual motion noise which is on the scale of 5 um.
    The stage has a natural frequency of 30 Hz, which is determined by the stiffness of the springs and the mass of the moving stage. When I use FFT to analysis the movement of the stage, I found that the main noise comes from 30 Hz and 50 Hz (both for open lood and close loop PID). I also use FFT to analysis the command voltage given to the VCA in close loop PID control, the peak frequencies are 10 Hz, 30 Hz, 40 Hz, 50 Hz, 70Hz, 90Hz....
    Do I need to use some filter between the amplifier and VCA so that it can reduce the noise without influence the accuracy? Or I can reduce such noise just by using some noise block in the VI program?
    Thanks
    best
    Attachments:
    VCA stage.png ‏160 KB
    FFT of Error motion with constant voltage_f1.jpg ‏1782 KB
    FFT_command voltage_PID_f1.jpg ‏444 KB

    Hi Paolo,
    It seem the influence from the magnetic field is not a big issue in the position control of a voice coil stage(VCS). I attached some picture of the commecial design of similar VCS and all these stages do not shield the cable connecting the VCA and controller. Anyway, I will try this method to see if it can make the result better.
    BTW, for the filter, could you please recommend some model for me? As the current noise is just around the level of 1 mA, I think I may need a very precise filter.
    Thanks
    best
    Attachments:
    vcs 1.jpg ‏49 KB
    vcs 2.jpg ‏54 KB
    vcs 3.jpg ‏22 KB

  • Labview 8 crashes when saving a vi with a 'Bundle By Name' function

    We have a working vi (Get_AN_Fast.vi), created with Labview 7.1.
    Trying to open this vi with Labview 8 crashes Labview.
    Problem seems to be related to a 'Bundle by Name' function, but it is not that simple as using this function by itself wirks fine.
    Any ideas would be a help.
    Attachments:
    Labview_Upgrade_Crash.zip ‏117 KB

    Sorry for the delay, I have been testing on other machines.
    We can reproduce the error on other machines, with completly fresh installs of Labview 8.
    The ActiveX Object we are connecting to is our own COM server, for interfacing to USB based data acquisition devices.
    I have found that when our COM server is not installed on a computer, then the VI will open, but with errors related the the missing COM Server.
    When the COM Server is installed, Labview 8 crashes when opening the vi.
    I realise that our COM server might have bugs, but it worked fine with Labview 6 and 7, and it is Labview 8 that gives the error, not our COM Server (which is a stand-alone executable).
    I have attached a zip file with our COM server, it just needs to be unzipped to a temporary file, and then run the 'register.bat' file to register the server.
    It will not install any other files on your computer and, can just be deleted when you are finished.
    Thanks
    Charlie.
    Attachments:
    COM_Server.zip ‏659 KB
    Labview_Upgrade_Crash.zip ‏117 KB

  • Labview 2014 crashing(windows 7)

    Hello for some reason my labview 2014 crashes when i try to open the labview application. It was working fine until yesterday but not having any luck today. Also i cannot see my labview software in the programs and feature section on the control panel even though i have administrative privileges in my computer. I have attached my error report below.Any help would be appreciated.
    Attachments:
    crash_report.PNG ‏109 KB

    Hi go_sa,
    In Programs and Features are you looking under National Instruments Software for LabVIEW 2014? If so, and LabVIEW is not listed, have you tried re-installing the software?
    If it is listed under National Instruments Software, it sounds like there may be some software corruption causing the error. The next step would be to try repairing the program. If this does not work, you can try force re-install the program (link below) or uninstalling and reinstalling it.
    http://digital.ni.com/public.nsf/allkb/ADD22E807D5A12AD862579EC00760F79
    Julia P.

  • LabVIEW IDE crashing!

    Hi there,
    I have just run into some very strange behaviour in LabVIEW (7.0 on Win2k with service pack 2).
    I have an event structure with several user events (about 12) listed in it. Everything was working fine yesterday. Today I tried to add another user event to the structure and LabVIEW crashed (giving usual cryptic error message saying referenced memory could not be read).
    Now, I have experimented quite a bit, and have the following observations to give:
    LabVIEW is happy adding more events until I try and add an event if the currently selected event is a Filter event (i.e Mouse Down?).
    I have a certain Mouse Down? filter event, and if I change this to a non-filtered Mouse Down event then LabVIEW lets me add more event cases as normal. However, I need this to be a filtered event (i.e with the "?"), and in this case, the next I try and add results in the LabVIEW IDE crashing. I can add more events as long as I dont have a filtered event case currently selected, so I suppose this is a work-around.
    To clarify, this occurs when I am trying to add events at design time, not at run time.
    I tried to replicate this in a new VI, and everything works fine as expected :-(
    I can't really attach the VI.
    Has anybody else noticed behaviour like this???
    nrp
    CLA

    hi there
    thanks for your suggestions
    >> A couple of suggestions:
    >>1. Try opening the VI on a different computer\LV version.
    >>2. Try copying all the code in the VI into another VI and see if this still happens.
    >>3. Start deleting pieces of the VI until it stops (or there is nothing left).
    I tried options 2 (same crash) and option 3 (crash stops when I delete the Filter events) before I posted the question.
    I have tried opening the VI on another PC (also Win2k) with the same version of LabVIEW and it also crashes.
    sigh...
    I suppose I am just going to have to work around it for now... strange bug...
    nrp
    CLA

  • Linear stage and Labview SmartMotor driver

    I am seeking a solution of controlling a linera stage with Labview:
    Stroke ~ 18 inch
    Resolution ~ 0.1 mm
    Low price.
    Do you have any recommendation on HW and SW? We are evaluating Animatics SmartMotor. Do you have a Labview for it? How EASY to program it for a simple scan motion? Thanks.

    You are trying to complete a force feedback application in a non-deterministic system (Windows) which may or may not work well depending on your control timing requirements. 
    You will need to use the DAQmx driver to acquire signals from your X Series device continuously at a set sample rate. See the LabVIEW example finder for a ready made example of how to do this.
    The values you read will have to be compared to your desired setpoint like you mentioned.
    The output of this comparison should be used to control the movement of the actuator. The actuator you are using looks like it has a LabVIEW driver.
    You can set up the motion of the system in a few different ways. One way (probably better with a windows system)
    perform a small incremental move with the stage
    measure the load and compare to desired value
    perform another small incremental move, or hold current position depending on the feedback
    Another way:
    perform a slow continuous move while continuously monitoring your feedback signal (loadcell)
    When the loadcell reaches a certain value, stop the move and hold current position
    The recommended way to do this as accurately and with as much flexibilty as possible would be with a deterministic real-time system where you are using the load cell as the primary feedback device to the motion control system. This is called a force feedback application. With this type of setup, you can actually define your setpoint in terms of force instead of position. This lets you do things like define a force profile to follow, and other more advanced concepts. All your sampling rates are higher, and the system must be deterministic to properly maintain a stable motion torque control loop.
    My recommendation would be to start with the DAQmx example, add in the comparison code, and then add in the commands to the actuator based on your logic. 
    Good Luck!
    ~Nate

  • Bind FPGA host reference to type definition in labVIEW 2012 crashes labVIEW

    Hi,
    I am using FPGA target device 5641R and labview FPGA 2012 with 5640R ver 1.7.
    On the configure window of open FPGA VI reference function, choosing the dynmaic mode shows broken arrow when wired to the 5640R configuration VIs (i.e. Configure timebase, Configure ADC default, Configure ADC NCO functions). So i tried the other option which is binding the FPGA host reference to type definition and choose the control from path C:\Program Files\National Instruments\LabVIEW 2012\instr.lib\ni5640R\Configuration\NI-5640R VIs\ni5640R FPGA VI Reference.ctl. But after that when i try to save the VI on which open FPGA VI reference function is placed, labVIEW crashes. I am unable to figure out the reason. Earlier I was working with labVIEW 2011 and it was working fine there. Any suggestions would be highly appretiated. 
    Please see the attached images for more details.
    Thanks
    Attachments:
    1.png ‏33 KB
    2.png ‏71 KB
    3.png ‏40 KB

    Check out this thread.  It looks like someone else ran into a similar issue and made changes that fixed their application.
    http://forums.ni.com/t5/IF-RIO/correct-5640r-template-use-recommendation/td-p/1331918
    Jeff B.
    Applications Engineer
    National Instruments

Maybe you are looking for