IMAQ USB Snap hangs all of LabVIEW?!?

I am having trouble with my USB cameras hanging a production machine. We are using 4 usb cameras from uEye for inspection and vision correction on a pick and place robot. The application is multithreaded, yet when the SNAP VI hangs, all threads in the application hang.
I can repeat this problem by disconnecting the USB cable to a camera. The system does not recover even after the USB is reconnected.
I have found in the past the Microsofts USB driver power managment seems to have an effect on the reliability of the USB system. The machine is also exposed to vibration which could cause intermittent connections.
While we are trying to solve all of these issues, I seem to have no way to detect if the camera is present before snapping the image. I cannot seem to prevent the system from snapping while the USB is disconnected.
Is there anything than can be done in order to have the SNAP vi return an error rather than hanging, or to tell the status of the device before snapping?
I have attached two example VI's which both repeatably cause the freeze. Just run the sample, plug in the usb camera, then disconnect it.
Im not sure if this is a LVDirectShow level issue, a DirectShow level issue, or a Camera Manufacturer(driver) issue (uEye).
If anyone has another brand of usb camera and can give my tests a quick run I would appreciate the feedback.
Thanks,
-Tim
Certified LabVIEW Developer
Attachments:
ConnectJustInTime.vi ‏55 KB
ConnectJustInTime1.vi ‏55 KB

Oops, I posted the same sample twice. heres the other one.
Attachments:
ConnectSnapDisconnect.vi ‏56 KB

Similar Messages

  • Why is IMAQ USB Snap.vi constantly giving out a 32-bit image?

    Hi.
    I'm using some USB cameras (uEye) with Direct Show. I use the IMAQ USB camera tools (with Labview 7.1, Vision 7.1.1) as in the examples. In particular I'm working in the snap mode.
    I create an U8 image (IMAQ Create) which I use as input to IMAQ USB Snap.vi and I set the camera's video mode to grayscale (Y8) using IMAQ USB PropertyPage.vi
    But, I don't get an 8-bit image out of IMAQ USB Snap.vi. The image is always converted to 32-bit RGB. In principal It works like this, but it costs me valuable time to convert the image to 8-bit at some points of the program where I need the image grayscale array.
    Cheers,
    mirola 
    Labview 5.1 - 2011

    Hi Elmar,
    Thanks for answering.
    Of course, the "not officially supported" thing is a killer argument. But the device shall work with a laptop and, as I know, the firewire cameras need an additional power supply when connected to a laptop 1394.
    The camera I use is grayscale and only works properly when I write 8-bit grayscale in its settings (e.g. using IMAQ USB PropertyPage.vi).
    As I said, everything I can set is set to 8-bit. The Snap.vi converts the input IMAQ image to 32-bit.
    But maybe you are right and it's just that NI's USB Direct Show dll is not treated with high priority (note: I use the most recent one, although I combine it with older LV and Vision versions.) Otherwise I guess I would get more answers here.
    On the other hand, if I ask the manufacturer he will probably say I should use his SDK which I don't want at this point.
    Best regards,
    mirola 
    Labview 5.1 - 2011

  • IMAQ USB Snap.vi time out

    I'm trying to capture an image in LabView using a veo stingray webcam.
    I'm using LabView 7.1 with Vission Assistant 7.1. I've attached my
    block diagram. When I press run LabView recognizes my camera, but I
    always get the following error.
    Error -1074396030 occured at IMAQ USB Snap.vi Time Out.
    Any suggestions would be appreciated.
    Attachments:
    labview.JPG ‏30 KB

    The QuickCam is indeed USB. The error appears when the vi is closed without using the IMAQ USB Close.vi (for instance when aborting the execution using the toolbar stop button). So, problem solved. Unfortunatelly this was not the only issue : Now my vi does not crash LV... but returns only a black image...
    For professionnal use, I have several NI frame grabbers. For teaching, I don't have a budget for 16 firewire adaptators and cameras . I'll try re-installing the software one more time.
    This is not a big problem because as I said before, the grab function is working. However, I don't like giving my students the idea that sometimes only 50 % of LabVIEW functions are working properly.
    Chilly Charly    (aka CC)
             E-List Master - Kudos glutton - Press the yellow button on the left...        

  • Error 0xBFF60492 on IMAQ USB snap.vi RT Video not support displaying selected color depth

    Attempting to snap a picture with NI-IMAQ for USB in LabVIEW 8.0  using the following procedure.
    1)I get the first enumerated camera, 2) open a session, with returned
    string [0], 3) start a session, 4) snap a picture and 5) close
    vi.  My problem is that in step 4 with the IMAQ USB Snap.vi, I get
    the following error.
    Error -1074396014 occurred at IMAQ USB snap.vi
    The image passed is not valid.
    Possible Reasons(s):
    IMAQ Vision: (Hex 0xBFF60492) RT Video Out does not support displaying the supplied image type at the selected color depth.
    I give the snap.vi an Image in from rightclick->Create->Control
    or rightclick->Create->Constant.  The output image (on the
    Front Panel) created by rightclick->Create->Indicator.
    LabVIEW should insert the correct data structure to match the expected
    input/output, and there is nothing I can that changes he color
    depth.  The GetImageInfo.vi reports that the camera is set up for
    4 Bytes Per Pixel, with the rectangle 352x288.
    Also the error message refers to RT Video Out, but I am using USB.  This distinction is significant in NI Vision Assistant.

    Hello together,
    I wanted to use a Sanyo Xacti CG 10 video camara in LabView.
    By using the NI-IMAQ for USB Snap I get the following error: IMAQ Vision: (Hex 0xBFF60492) Ungültige Blit-Funktion des Videoausgangs.
    Is it possible, that I can not use this camera in LabView?
    Thanks a lot for your reply

  • Error 1074396024 occur at imaq usb snap.vi

    hallo, ich habe labview 8.0 mit dem vision development modul und
    benutze eine logitech webcam zur bilderfassung. ich habe ein vi
    erstellt das im zeitraum von 1s ständig neue bilder macht und diese mit
    einem referenzbild vergleicht. mein problem ist das so bei ungefähr
    1000 vergleichen eines neuen bildes mit dem referenzbild der fehler
    1074396024 occur at imaq usb snap.vi auftritt und ich aber nicht weiß
    warum.  würde mich freuen wenn mir jemand helfen kann

    Please have a look at this thread which discusses similar issues in detail.
    Best regards,
    Jochen Klier
    National Instruments Germany

  • USB SNAP + colour pattern matching ( IMAQ)

    I am new to LAbView and currently  I am working on colour pattern matching with USB snap. My problem is this program keep prompt me on the IMAQ Learn Colour Pattern. I need someone to help me solve that problem.
    Another question is 'Are colour pattern matching require us to save and load file before learn a template?'
    I am using LabView 7.1 and I would appreciate anyone who help me. Thanks
    Message Edited by Chee Hou on 09-16-2009 03:46 AM
    Attachments:
    Untitled.vi ‏189 KB

    Hello Chee Hou,
    Have you tried to run the example to do color pattern matching?
    From the example, you do need to have a template picture ready when you are using the colour pattern matching.
    You need to Learn Colour Pattern and then load the pattern to do color pattern matching.
    Hope this helps.
    James
    - Meadow -
    LabVIEW 7.0 - 2011, Vision, RT, FPGA
    TestStand 3.0 - 4.5

  • IMAQ USB Grab.vi not collecting image, USB Snap.vi does

    I am trying to continously collect video data using a USB device.  the USB Snap.vi does great at capturing a single image, however USB Grab.vi returns a blank image.  I don't get any errors when I run the Grab.vi, just no image.  Any help would be appreciated.

    This works for me.
    Message Edited by rpursley8 on 07-13-2009 03:42 PM
    Randall Pursley
    Attachments:
    Untitled 1.vi ‏44 KB

  • What is USB Camera Name in IMAQ USB-Init.vi?

    Hi,
    The subject of this message explains my question. In addition, I was wondering if someone could tell me whether the "USB Camera Name" can take any name or not. Finally, when I run my program, I get an error indicating that "Filter name not found". Can somebody tell me what the Filter name is?
    Thank You

    Yes, it does matter what you use as a camera name. Use the IMAQ USB Enumerate Cameras VI to get the names of all the connected cameras. Then feed in the one that you want to use.
    Hope that this helps,
    Bob
    Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
    DISTek Integration, Inc. - NI Alliance Member
    mailto:[email protected]

  • Imaq usb palet doesn't appear

    Hi all,
    Are anybody maybe encounter with problem after installation of imaq usb driver, the usb imaq palet doesn't appear :-(
    Outside the Labview I succeed to connect by Vision Assistant but in VI Vision Assistant doesn't see usb  camera.
    Thank you in advance fore help.
    Yan

    Hi Yan,
    This happened to me also. I have two versions of LabView, 8.5.1 activated and 8.6 Evaluation. I installed the driver like three times but I only tried with LabView 8.6 and no palet appeared. Finally, i tried in 8.5.1 activated and it was fine and working properly. If you have more than one version of LabView, my advice is to check them all and see in which one the palet is visible. Other than that, i can't really think of anything else.
    Hope this helps,
    Sabin

  • Phoenix 1280 USB camera gives IMAQ USB Init error?

    We're trying to use a Phoenix PC-1280 USB video camera with either Labview or the Vision Assistant. In both cases we get an error in the IMAQ USB Init.vi (eg, "IVA Acquisiition Tools palette.vi was stopped at node 0x140 of subVI IMAQ USB Init.vi"). We have the latest version of labview and the vision module. The Mutech people are being totally useless, but I suspect the problem is in their driver which is supposed to use DirectShow and should be compatible. Before we toss this $1000 camera in the trash, can someone suggest a quick fix? ...or even a slow one
    PS -- it's not the language problem, we're all in english

    Hi Cyndeigo,
    One thing to check is to see if your camera is being recognized
    by LabVIEW.  One way to do this is to use
    the USB enumerate cameras.vi.  If this is
    sending back the camera name, then make sure you are connecting the USB Init.vi
    as shown in the attachment.  If the USB
    enumerate cameras.vi isn’t feeding back any data then there is probably something
    wrong with the driver.  I hope this
    helps.   Keep me posted.
    Regards,
    GG 
    Attachments:
    usbinit.jpg ‏4 KB

  • How to set the exposure time and the gain of a connected camera with IMAQ USB

    A camera was connected to my computer with USB port and we can acquire the image through IMAQ USB.  Now we have to set separately the exposure time and the gain with the camera's driver software provided by the manufacturer.  My question is: how to set directly the exposure time and the gain of this camera in Labview?

    Hi Frank
    Welcome to the forum. Have fun
    FranklinT wrote:
    My question is: how to set directly the exposure time and the gain of this camera in Labview?
    I think its not possible for USB Cameras. 
    Previous threads for your ref
    http://forums.ni.com/t5/Machine-Vision/How-to-control-property-nodes-for-USB-camera/td-p/970306
    http://forums.ni.com/t5/Machine-Vision/imaq-USB-property-page/td-p/926034
    Sasi.
    Certified LabVIEW Associate Developer
    If you can DREAM it, You can DO it - Walt Disney

  • IMAQ USB Close leaves the camera open

    Hi,
    I hope somebody can help me with that one. I have a DirectShow compliant USB camera, that I got to work with the IMAQ USB VIs. I can acquire images, enumerate the devices and get the options dialog. However calling the IMAQ USB Close VI does seem to have any effect. As the next time I try to call IMAQ USB Open afterwards I got error -1074396024 until I terminate the host process and restart LabVIEW again.
    I am using LabVIEW 8.0, on W2k German
    I also tried the samples (e.g. Grab.vi) provided with the same effect.
    Running a tool that collects system debug messages (send via OutputDebugString) I got 'Export: Break Connect' coming from the IMAQ USB Close VI, but I also see, that the underlying DirectShow Interface doesn't receive any close call. Is there an Interface missing in the DirectShow interface (which?) or is this a bug in the IMAQ USB Interface (not very likely as a lot of guys seem to be happy with it)?
    Can anybody help please?
    Greetings,
    Stefan

    Stefan,
    below is an excerpt about the system requirements for IMAQ USB:
    - Windows 2000/XP (English, Italian,
    Japanese, French, Italian, Norwegian, Dutch, Spanish/Portuguese,
    Russian, and simple Chinese)
    - LabVIEW 7.0 or higher with NI Vision 7.1 or higher for the USB LabVIEW support.
    - Vision Assistant 7.1 or higher for the USB Vision Assistant plugin module.
    In general IMAQ USB is not supported but I will forward the information to R&D.
    The following link povides other possibilities:
    http://digital.ni.com/public.nsf/allkb/274a74a901399d0486256f32007295f9
    Regards,
    ThSa
    http://www.newgistics.com

  • Mightex camera not identified by max or Imaq usb enumerate camera vi

    Hi all,
    I am using Mightex S-Series Ultra-Compact USB2.0 camera, I am finding it difficult to identify the camera in MAX or with IMAQ usb enumerate camera vi, I do have loaded the drivers but still couldnt get the camera working , please let me know if there is anything else I need to upload.
    Thanks,
    Ankit Gupta

    Hi AnkitG,
    Sorry to hear that you are having problems with your camera. We have recently seen several other instances of Mightex's cameras causing issues when trying to interface with it through IMAQdx, and have been in touch with Mightex regarding these issues. We suspect that the issues all come from differences in the way NI and Mightex handle DirectShow compliance. I'll make sure to communicate this issue to them as well, and I'll let you know what we find. 

  • Error from IMAQ USB Grab Setup in executable

    I created an executable that returns
    Error 1074396024 occured at IMAQ USB Grab Setup.vi
    IMAQ Vision: Minimum coverage value should be greater than zero.
    I developed the executable on a 32 bit machine with LabVIEW 2009 and the Vision Development Module 2012 SP1. The target computer has LabVIEW Vision Development Module 2012 and LabVIEW Run-Time Engine 2009 SP1 (32-bit Standard).
    Other people on the forum have had this error, and I tried everything they suggested. I continue to get the error. I have also tried downloading IMAQ and Vision Aquisition Software, but I get the same message. Some people have had problems with versions of LabVIEW in different languages, but I am only using english. Is this problem caused by not having the correct run-time engines?
    Any help would be greatly appreciated.
    Thanks!
    Solved!
    Go to Solution.

    Hello Eckman,
    Do you have the Vision Development Module Run-Time Engine (VDM RTE) installed on your target machine? You will need the RTE to run vision applications as a deployed executable. 
    Vision Development Module Run-Time Engine 2012 SP1
    Please let me know if you install the run-time engine (or already have) an still receive the same error message.
    Regards,
    Ian K.
    Applications Engineer
    National Instruments

  • IMAQ USB CAMERA BLINKING

    I'm trying to do a real time inspection with Vision Assistant 8.6 and when I start capturing with IMAQ USB GRAB inside Labview 8.6 the video starts blinking and I can't see for sure what is happening.
    Is there any solution to stop it and make the image smooth without blinking?
    There is an image below showing the block diagram.I'd appreciate if someone could help me.

    Hi, Alex,
    You have clear race conditions between Grabbing/Processing/Visualization.
    Try to copy image to other buffer, then "blinking" should goes away.
    Something like that:
    Also remember, that at first grab iteration your image is not valid, because grab occurred after processing.
    Andrey.

Maybe you are looking for

  • How do I maintain the configuration of my current Catalog in PSE9 when moving it to a new computer?

    While the Version Sets in my current catalog are collapsed, the version sets in the Catalog on the new computer have all become 'expanded'; this is unacceptable to me, as many of the pairs that are stacked as Version Sets have become separated.  Whil

  • Master detail form - drop down list in detail (ADF)

    Hi, Been racking our brains for a few days/weeks about this one, and would be grateful for any pointers why this does not work. We have developed an in-house application for dealing with risk and chemical assessments. The process we have adopted allo

  • How to create Tree format in Table Rn in one Column having data?

    Hi Gurus, i got the new requirement it's very interesting pl z help me... My Requirement is i have one Table Rn in Table Rn having 5 columns There here one column name is 'Competencies ' That Competencies column having the more rows liki FUNC.ADMIN.A

  • Imac freeze using photoshop cs4

    Hi All, I'm really hoping someone can point me in the right direction. When using Photoshop CS4 my imac keeps repeatedly freezing, this seems to happen whilst moving the image around. I also get some of the same crashes using bridge. I have previousl

  • Essbase Clac Question

    I have the following structure of a BSO Cube: Accounts Time Dense1 Sparse1 Sparse2 Sparse3 Sparse4 I need to roll up the cube for One level 0 member of the accounts dimension, a given month and a Given Dense1 Member (thse are all level 0). What would