Vision Assistant 2013 returns faulty Kernel Sizes

When playing around with custom kernels in Vision Assistant 2013 I noticed that in the function "Filters" unter "Convolution - Custom", the size shown in the "Kernel Size" Control does not match the size displayed in the matrix view on the right of the control, as displayed in the attached picture #1.
Sizes larger that 5 grow to 17 instead of 7, 21 instead of 9, 25 instead of 11 and so on. When I hit OK and re-enter into the setup dialog, the Kernel size control shows "17" when I left it before with 7. I can then decrease the size from 17 to 7 and will finally get my 7x7 kernel.
Also, when using "Convolution Custom", and entering the first "customized" value, the focus in the filter selection list suddenly jumps to "Convolution - Highlight Details". If I decide that this shall not disturb me much and keep on entering the values, all is fine. Until I hit ok and then realize, I might have made a mistake, which makes me doubleclick the Filter Setup again. this results in a total change of the kernel I entered into the standard "Convolution - Highlight Details" with all those -1 s and the high positive number in the middle, see attached pictures #2 and #3.
Can anyone confirm this odd behavior?
Attachments:
20140214_VAS2013#1.png ‏14 KB
20140214_VAS2013#2.png ‏61 KB
20140214_VAS2013#3.png ‏75 KB

Dear comrade,
I reproduced this issue like you described and it definitely looks like a Bug in the Vision Assistant 2013 Software.
So I will write a CAR which will be forwarded to R&D.
Thank you very much for your support
Kind Regards,
Oleg Scherling, M.Eng | Applications Engineering | National Instruments | NIG |

Similar Messages

  • Problem with advanced threshold in OCR - Vision Assistant 2013

    I'm facing a problem with Vision Assistant 2013
    The OCR charter set file advanced threshold data is always fixed at 255 upper value and optimize for speed is checked.
    I edit them and reopen the file but no change.
    anyone facing the same problem ?
    Attachments:
    Untitled.png ‏7 KB

    Hi Paolo,
    Thanks for your answer. Yeah I have seen the examples and I´m familiar with the use of the OCR VI. I have use it a couple of time already with good results.
    My problem came last week. While I was trying to run OCR on my image in my LabVIEW code. The algorithm did not detected what I was expecting.
    I decided to run the test on the vision assistant and it worked perfectly. I assumed my code had different parameters, so I decided to generate a VI from the vision asssistant and run it on LabVIEW for the same image to verify.
    I did not change anything on the VI (all parameters are the same), and used the same image. Surprinsingly the results are different between the assistant and the VI. That strikes me a lot!
    I´ll start a new thread as you recommended. Hope to find the solution soon. Thanks  
    Regards,
    Esteban

  • Vision Assistant - .bin not found

    Thought I'd try here first before raising a support call on the off chance someone's come across it before.
    Running Win7 64bit and LV 2013 SP1 (via 2014 DS SP1), with the Vision Development System installed. I have a fully-populated Vision palette, and can use the low level Vision VIs to my heart's content...
    However, I can't seem to run Vision Assistant. On dropping the Vision Assistant from the palette, I get the following two errors:
    I am also unable to open previously configured Vision Assistant instances in other code, although no errors are returned - the VA just doesn't run.
    I also have LV 2012 SP1 installed (amongst other older versions) and now get the same error with that. I haven't tried to use VA since I switched to LV 2013 several months ago.
    Has anyone come across this before?
    I'm just trying to repair Vision Assistant 2013, which I'd like to think will fix it, but we shall see. I'll let you know when all 117 of the requisite components are also finished repairing
    CLD
    Solved!
    Go to Solution.

    The repair solves it.
    Sadly, that involved repairing components for 2013, 2012, 2011, 2010... but still, at least I got to put my feet up for a little while whilst it was completing.
    Will mark as solved in case anyone else has the same issue.
    CLD

  • Vision DevMod: How to create large Gaussian filter kernels with integer values like Vision Assistant uses

    Hello,
    in Vision Assistant it is possible to create filter kernel of arbitrary size, like e.g. a 75x75 Gaussian kernel. These kernels feature integer-only elements. I tried to find a function in the Vision Development Module, but have been unable to find something so far. So I still create a Vision Assistant script with such a kernel and export it to a LabVIEW VI in order to abtain such a kernel. Any ideas on how to create such kernels programmatically?

    -You can generate custom kernels in LabVIEW also, but you need to have either string or numerical of that kernels. Without these two, i am not sure of how to do this.
    -Please check this for building kernels.
    http://zone.ni.com/reference/en-XX/help/370281M-01​/imaqvision/imaq_buildkernel/
    -Let's say you are able to programmatically generate kernel string, it will convert to kernel in double format automatically and connect this to convolute vi.
    Thanks
    uday,
    Please Mark the solution as accepted if your problem is solved and help author by clicking on kudoes
    Certified LabVIEW Associate Developer (CLAD) Using LV13

  • Vision assistant structuring element

    HELLO,
     I am a new bee to labview.My objective is to "ERODE OBJECTS" through  "BASIC MORPHOLOGY"  in vision assistant  using a 2 x 28 structuring element filter.But vision assistant only provides 3 x 3 , 5 x 5 and 7x 7 order structured elements erode object filter. Is there any way out??
                                                                           Thank you

    The latest version of Vision Assistant 2011 SP1 lets you specify much bigger kernels, but unfortunately, they still have to be the same size in X and Y. Thanks for the feedback. We might consider letting the user specify different sizes in X and Y in a future version.
    As Bruce mentioned, you will have to generated the code and do it in LabVIEW.
    Alternatively, you can just create that VI from LabVIEW using the kernel you want, call it using the Run LabVIEW step, and still do the rest of your prototyping in Vision Assistant.
    Christophe

  • Kinect - Vision Assistant

    Hi all,
    I am about to start working on a project with Kinect and Vision Assistan (and later with LabView) and I would appreciate if you could give me some advice on what should I do in order to make Vision Assistant let me acquire images with the Kinect camera.
    I have already installed on my computer both "Kinect SDK" and "Kinect Developer Toolkit" (versions 1.7 and 1.7.0 respectively) as well as LabView 2013 and the Vision Development Module, version 2013 too.
    I have also installed the correspondent drivers from this link: http://joule.ni.com/nidu/cds/view/p/id/4409/lang/en
    Kinect camera is recognised properly by the computer, as it is shown on the Device Manager of the Control Panel. I have even tried the Kinesthesia example VI, and it works alright, so I guess the issue of not being recognised on Vision Assistant has nothing to do with the installation of the camera.
    Any help would be really appreciated
    Best regards!

    Hello,
    you can also use PCL (point cloud library - search google) to build a DLL (dynamic link library), which you can call in Labview. For example:
    https://decibel.ni.com/content/blogs/kl3m3n/2013/01/08/using-microsoft-kinect-to-visualize-3d-object...
    In this way, you can obtain both RGB and calibrated XYZ data (i.e., point cloud with texture).
    Best regards,
    K
    https://decibel.ni.com/content/blogs/kl3m3n
    "Kudos: Users may give one another Kudos on the forums for posts that they found particularly helpful or insightful."

  • Vision Assistant 2014 (and DLL inside of LV) repeatedly crashes while reading multiline OCR

    I am working on an OCR application. With certain files (not all) the multiline function just crashes. No questions asked.  I set the ROI area to the targeted text and without fail it causes a crash.
    Is anyone aware of this problem, and if so is there a solution?
    Additional information:  My .abc file is from scratch with default settings and trained characters. Nothing in it should be causing the crash.  Images are simple scanned jpg files.
    Edit: I tested it. Crash still happens without any character set loaded, and no changes to threshold, size, or read options.

    I cut out an offending section of one of the files. It is attached.  To replicate the error:
    1. Load image
    2. Identification -> OCR/OCV
    3. New Character Set File...
    4. Select entire text.
    NI Vision Assistant 2014, 64 bit. 
    Edit: Posted this before I saw your request   On the "Full sized" image, it crashes always - even when it is called from inside of LabVIEW (the DLL crashes then).  It is how I noticed the bug - my program kept crashing.  Tor this image, it seems to only crash for me inside of the training assistant, but is again reliable.
    Attachments:
    crash.png ‏731 KB

  • No Image - 1473R With Vision Assistant

    Hopefully this is a simple fix and I'm missing something very obvious, so here is what's up. I'm originally a text programmer but for this project I'm stuck using LabVIEW which is completely unfamiliar; I've been working on this for days with no progress so I thougt I'd see if anyone had some pointers. The goal of the project is to use the PCIe-1473R FPGA to do live gain control, overlay, and maybe some recognition.
    I started with the "Image Processing with Vision Assistant on FPGA" example and made a few simple changes to just attempt to get a video feed through. The camera we are using is a Pulnix TM 1325 CL, which outputs a 1 tap/10 bit Camera Link signal. Since this example VI is originally configured 1 tap/8 bit I changed the incoming pixel to be read as 1 tap/10 bit and compiled and tested. When I try to start video acquisition I get no errors but no frames are grabbed. The frame's acquisitioned count does not increase and nothing is displayed. If I switch to line scan I get a scanning static image, but this is not a line scan camera and my other NI frame grabber card shows an image from the camera fine.
    I wasn't all that surprised with this result, as the input is 10 bit and the acquisition FIFO and DMA FIFO are both 8 bit orginally. So, I changed them to U16 and also changed IMAQ FPGA FIFO to Pixel Bus and IMAQ FPGA Pixel Bus to FIFO blocks on either side of the Vision Assistant to U16. With this configuration, I again get no image at all; same results. I suspect this is because the incoming image is signed, so the types should be I16 instead. However, there is no setting for I16 on the Pixel Bus conversion methods. Am I not understanding the types happneing here or is there an alternative method for using Vision Assistant with signed images? I'd think it'd be odd not have support for signed input.
    Anyway, I've tried all the different combos of settings I can think of. Does anyone have any input? I feel like it must be either a buffer size problem or a signing problem, but I don't really know. Any and all input is welcome!
    Thanks for helping out a new guy,
    Kidron

    I ended up resolving this issue by switching cameras. The end goal was to use a FLIR SC6100, so I switched to it and was able to get things working shortly. The FLIR does use unsigned ints, so I believe that's what resovled the issue for anyone running into this in the future.

  • Intégrer le code généré par NI vision assistant à mon programme codé sous LabWindows CVI

    Bonjour à toutes et à tous,
    Dans la cadre d'un projet je doit faire de la vision par ordinateur via le logiciel National Instrument (NI) "Vision Assistant". Les fonctions de l'assistant dont je veux me servir seront simplement "Histrogramme", "thershold" et "circle detection".
    Mon problème, c'est que j'aimerai intégrer véritablement, l'image donné en direct de ma camera, les outils (boutons) de sélections sur l'image et les résultats obtenus après traitement (que l'Assistant donne) à mon programme déjà existant (sur l'UIR du programme) !
    Je ne comprend pas (j'ai bien lu le tutoriel Vision assistant to cvi sans succès) comment utiliser le code généré par l'assistant dans CVI pour faire apparaitre ce dont j'ai besoin (l'image donnée par ma camera, les boutons de selections de l'assistant et dans mon programme déjà codé.
    De plus si je compile directement le code que l'assistant me genere (seul), il y a des erreurs liées a la bibliothèque <nimachinevision.h> : "redlacaration of variables..." bibliothèque que je doit donc enlever du code généré pour qu'il compile correctement !
    Si l'un d'entre vous est déjà passé par là, son aide me serait très précieuse !
    Merci beaucoup !

    Bonjour Pooty,
    Pourriez vous indiquer de quel tutorial vous-êtes vous inspiré ?
    Merci d'avance.
    Mathieu_T
    Certified LabVIEW Developer
    Certified TestStand Developer
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    LabVIEW Tour
    Journées Techniques dans 10 villes en France, du 4 au 20 novembre 2014

  • Vision assistant - Sequence acquisition

    I just sarted using Vision assistant and when I want to do a sequence acquisition, the sequence acquisition wizard only shows the input of the number of frames only. How do I set the Skip Count?, Line, triggering action, timeout and polarity? I only have that one option of Number of frames and then have to click next and finish. Do I do these settings in Vission assistant?, if so, how? Or I have to set all this in MAX? am using labview 2013. If I get a time-out error do I set it in MAX as well? Could not acquire (ROI) whilst acquiring continous images. do I need to install some drivers or all this I set in MAX?
    Rose 2010

    Unfortunately, in the Acquire Image (1394, GigE, or USB) step, the sequence acquisition feature does not allow you to specify a skip count.
    I filed CAR 488272 to address that request in a future version of the software.
    The step should use the Max configuration, or the attributes you specified in the Attributes tab, as for the trigger configuration.
    That configuration should be used for the sequence acquisition.

  • Upgrade issues with Vision Assistant

    Hi Guys,
    I have encountered a problem with finding and analysing data from vision assistant since I upgraded to the new labVIEW 2013 SP2 a couple of weeks back. Within my application I perform countless camera inspections using vision assistant however i have noticed that for 4 particular inspections my vision assistant does not perform as it should. All other inspections have worked perfectly which is quite strange. Even the scripts are the same along witht the file directory locations. The first error was -1074396120 IMAQ Match Pattern3 saying the possible error was because it was not an image etc. However, after instancing a known working script into vision assistant for that inspection i receive an image but I dont receive an output from visin assisant that I am looking for.
    Within my inspection I look for 4 templates and an OCR check etc and perform boolean logic to give me a true/false result. When i run my application i always get a false result, even my probes tell me there was no template match etc but when i open up the script and run it all the templates are picked up! I created a new less complicated inspection where i only look for one pattern and again i get a false result. Has anyone got any ideas? I am a bit lost at the moment considering non of the other inspections have been affected. Even creating new file paths for directories but no joy!
    Thanks in advance guys! 

    Hi Chris,
    I was away for a few weeks. I have attached an image with template. The version I currently run is Development 2013 SP1 and the Vision Development module 2013 SP1 see attachment (Doc1). The executable runs perfectly for all of my inspections which is over 100 and only 2/3 fail because it will not find the template. The template has the same file paths as all the other inspections. When running the application i receive a fail because it doesnt see a template i believe. However, when i open the vision assistant express VI and run through the script it finds the templates no problem. Any advice is welcome.
    Damien
    Attachments:
    230.png ‏2220 KB
    Edge Template2.png ‏223 KB
    Doc1.docx ‏115 KB

  • USB camera "could not be initialized properly" in vision assistant, error code unknown

    Hi All,
    I was working on a project with Labview 2011, and VDM 2014 (vision developement module), and VAS 2014_August (vision aquisition software).
    I finished my project well including the use of vision assistant!
    but when the temporary licenses expired for the VDM and VAS, then I want to activate the purchased licenses for both of them, I should use the VAS 2014_februar not augest!!!
    then I uninstalled the 6 drivers included for the VAS_2014_August IMAQ & IMAQ Runtime, IMAQ I/O and IMAQ I/O Runtime, IMAQdx & IMAQdx Runtime, then installed the VAS_2014_02 February!
    but the vision assistant stopped working!
    as attached in the files, when I try to aquire an image from there, I get "The specified aquisition device could not be initialize properly"...
    and if I am trying to press on grab I get the same!
    I tried a lot of things like to remove drivers for the VAS_2014_08 then to install even the 2015 then to uninstall 2015 then to install again 2014 february...
    also in the NI MAX I can find the camera and to activate to grab and snap! but not in the vision assistant!
    what can you suggest for me as solution?!
    Thanks.
    Attachments:
    USB Camera 1.jpg ‏140 KB
    usb camera 2.png ‏167 KB

    For the past several years, LabVIEW was released in August, with a Service Pack (SP1) released in February.  Thus LabVIEW 2014 was released in August 2014, LabVIEW 2013 was released in August 2013, and LabVIEW 2013 SP1 was released in February 2014.
    You cannot depend on the year to know the LabVIEW Version!!
    Also, LabVIEW is not really backward-compatible.  If you are doing serious Development work, you want LabVIEW and all of the relevant Toolkits and Modules to be the same Release (e.g. 2011, 2013, or 2014 -- don't "mix and match").  If you have NI Update installed, it should help you "migrate" to Service Pack 1, if necessary.
    BS

  • How do you track a moving object using Labview and Vision Assistant

    I am using Vision and Labview to create a program that tracks and follow a moving object using a high end camera. Basically what it does is it detects a foreign object and locks on to it and follows it where ever it goes in a control sized room.
    I have no idea how to do this. Please help. Or is there an available example.
    Thanks.

    Hello,
    It sounds like you want to look into a Vision technique called Pattern Matching.  Using our Vision tools, you can look for a image, called a template, within another image.  Vision will scan over the entire image of interest trying to see if there are any matches with the template.  It will return the number of matches and their coordinates within the image of interest.  You would take a picture of the object and use it as the template to search for.  Then, take a picture of the entire room and use pattern matching to determine at what coordinates that template is found in the picture.  Doing this multiple times, you can track the movement of the object as it moves throughout the room.  If you have a motion system that will have to move the camera for you, it will complicate matters very much, but would still be possible to do.  You would have to have a feedback loop that, depending on where the object is located, adjusts the angle of the camera appropriately.
    There are a number of different examples a that perform pattern matching.  There are three available in the example finder.  In LabVIEW, navigate to "Help » Find Examples".  On the "Browse" tab, browse according to "Directory Structure".  Navigate to "Vision » 2. Functions".  There are examples for "Pattern Matching", "Color Pattern Matching", and "Geometric Matching".  There are also dozens of pattern matching documents and example programs on our website.  From the homepage at www.ni.com, you can search in the top-right corner the entire site for the keywords, "pattern matching". 
    If you have Vision Assistant, you can use this to set up the pattern matching sequence.  When it is complete and customized to your liking, you can convert that into LabVIEW code by navigating to "Tools » Create LabVIEW VI..."  This is probably the easiest way to customize any type of vision application in general.
    I hope this helps you get started.  Take care and good luck!
    Regards,Aaron B.
    Applications Engineering
    National Instruments

  • LabVIEW Vision Assistant的图像处理,NI视觉助手教程免费阅读

     附件里面比较全，因为发不了那么多字
    http://shixinhua.com/  石鑫华主页
    http://shixinhua.com/imganalyse/2013/09/762.html  全文网站
    《基于Vision Assistant的图像处理是实用教程》
    第二章 界面与菜单       67
    第一节 启动欢迎界面  67
    http://shixinhua.com/imganalyse/2013/01/278.html
    第二节 功能界面  73
    http://shixinhua.com/imganalyse/2013/01/280.html
    Acquire Images采集图像界面       73
    Browse Images浏览图像界面       77
    Process Images处理图像界面       79
    第三节 File文件菜单    86
    http://shixinhua.com/imganalyse/2013/01/283.html
    Open Image：打开图像          86
    Open AVI File：打开AVI文件         87
    Save Image：保存图像  87
    New Script：新建脚本   91
    Open Script：打开脚本  92
    Save Script：保存脚本   92
    Save Script As：脚本另存为  93
    Acquire Image：采集图像     93
    Browse Images：浏览图像   93
    Process Images：处理图像   94
    Print Image：打印图像 94
    Preferences：优先参数选择 95
    Exit：退出       97
    第四节 Edit编辑菜单   97
    http://shixinhua.com/imganalyse/2013/01/284.html
    Edit Step：编辑步骤       97
    Cut：剪切       97
    Copy：复制     98
    Paste：粘贴   98
    Delete：删除 98
    第五节 View查看菜单 98
    http://shixinhua.com/imganalyse/2013/01/286.html
    Zoom In：放大        99
    Zoom Out：缩小     99
    Zoom 1:1：原始图像      99
    Zoom to Fit：适合窗口  99
    第六节 Image图像菜单        99
    http://shixinhua.com/imganalyse/2013/01/288.html
    Histogram：直方图 101
    Line Profile：线剖面图   101
    Measure：测量      101
    3D View：三维视图        101
    Brightness：亮度   102
    Set Coordinate System：设置坐标系    102
    Image Mask：图像掩码         102
    Geometry：几何    102
    Image Buffer：图像缓存        102
    Get Image：获取图像   102
    Image Calibration：图像标定        102
    Image Correction：图像修正         102
    Overlay：覆盖         102
    Run LabVIEW VI：运行LabVIEW VI       103
    第七节 Color彩色菜单 103
    http://shixinhua.com/imganalyse/2013/01/289.html
    Color Operators：彩色运算  104
    Color Plane Extraction：彩色平面抽取          104
    Color Threshold：彩色阈值   104
    Color Classification：彩色分类      105
    Color Segmentation：彩色分段     105
    Color Matching：彩色匹配    105
    Color Location：彩色定位      105
    Color Pattern Matching：彩色模式匹配       105
    第八节 Grayscale灰度菜单 105
    http://shixinhua.com/imganalyse/2013/01/291.html
    Lookup Table：查找表    107
    Filters：滤波  107
    Gray Morphology：灰度形态学     107
    Gray Morphological Reconstruction：灰度形态学重建        107
    FFT Filter：快速傅立叶变换滤波  107
    Threshold：阈值     107
    Watershed Segmentation：分水岭分割        107
    Operators：运算    107
    Conversion：转换  107
    Quantify：量化       108
    Centroid：质心       108
    Detect Texture Defects：检查纹理缺陷       108
    第九节 Binary二值菜单        108
    http://shixinhua.com/imganalyse/2013/01/293.html
    Basic Morphology：基本形态学    109
    Adv. Morphology：高级形态学      109
    Binary Morphological Reconstruction：二值形态学重建     109
    Particle Filter：粒子滤波        109
    Binary Image Inversion：二值图像反转        110
    Particle Analysis：粒子分析  110
    Shape Matching：形状匹配  110
    Circle Detection：圆检测       110
    第十节 Machine Vision机器视觉菜单 110
    http://shixinhua.com/imganalyse/2013/01/295.html
    Edge Detector：边缘检测     111
    Find Straight Edge：查找直边        112
    Adv. Straight Edge：高级直边        112
    Find Circular Edge：查找圆边        112
    Max Clamp：最大卡尺  112
    Clamp(Rake)：卡尺（耙子）         112
    Pattern Matching：模式匹配         112
    Geometric Matching：几何匹配   112
    Contour Analysis：轮廓分析 112
    Shape Detection：形状检测  112
    Golden Template Comparison：极品模板比较     113
    Caliper：测径器、卡尺 113
    第十一节 Identification识别菜单         113
    http://shixinhua.com/imganalyse/2013/01/296.html
    OCR/OCV：光学字符识别     114
    Particle Classification：粒子分类  114
    Barcode Reader：条码读取  114
    2D Barcode Reader：二维条码读取     114
    第十二节 Tools工具菜单      114
    http://shixinhua.com/imganalyse/2013/02/297.html
    Batch Processing：批量处理          114
    Performance Meter：性能测量     120
    View Measurements：查看测量   120
    Create LabVIEW VI：创建LabVIEW VI代码 121
    Create C Code：创建C代码 121
    Create .NET Code：创建.NET代码        122
    Activate Vision Assistant：激活视觉助手     123
    第十三节 Help帮助菜单       124
    http://shixinhua.com/imganalyse/2013/02/298.html
    Show Context Help：显示上下文帮助  124
    Online Help：在线帮助  125
    Solution Wizard：解决问题向导   125
    Patents：专利         125
    About Vision Assistant：关于视觉助手         125
    第三章 采集图像  126
    第一节 Acquire Image采集图像  127
    http://shixinhua.com/imganalyse/2013/02/299.html
    第二节 Acquire Image(1394,GigE,or USB)采集图像（1394、千兆网、USB） 128
    http://shixinhua.com/imganalyse/2013/02/301.html
    Main选项卡   129
    Attributes属性选项卡   138
    第三节 Acquire Image(Smart Camera)从智能相机中采集图像 143
    http://shixinhua.com/imganalyse/2013/02/302.html
    第四节 Simulate Acquisition仿真采集 145
    http://shixinhua.com/imganalyse/2013/02/304.html
    第四章 浏览图像  150

    Wetzer wrote:
    You can think of the purple "Image" Wire as a Pointer to the Buffer containing the actual Image data.
    That's what I thought too, but why would it behave differently during execution highlighting? (sorry, I don't have IMAQ, just curious )
    LabVIEW Champion . Do more with less code and in less time .

  • Labview Vision Assist IDS camera

    I ordered a camera from IDS, the 3360CP. This is for my thesis. IDS has there own VI's for labview for the camera.
    The problem is that the image which is generated with those VI's is not compatible with the
    vision assistant module in labview 2013. I'm looking for a way to convert the image.
    I included the VI. If it doesn't open propperly the flowwing link can be used to install the labview VI on your pc.
    https://en.ids-imaging.com/download-ueye-interfaces.html
    They can be found under program files/IDS/uEye/otherdrivers/labview.
    Kind regards,
    Maarten Vanoverberghe
    Attachments:
    uEye_SimpleLive.vi ‏104 KB

    The IDS cameras that require use of their SDK (the VIs they supply) are not directly compatible with IMAQdx, and hence, not suitable as image acquisition devices for use in Vision Assistant, and Vision Builder for Automated Inspection.
    You will need to incorporate the IDS VIs into your pipeline in a way that makes the acquired image available to the script.  Most likely, this would be by writing the image to disk, and then signaling the script that the image is ready. If you need fast frame rates, and are not able to do everything in pure labview, I recommend looking at a different camera.
    Machine Vision, Robotics, Embedded Systems, Surveillance
    www.movimed.com - Custom Imaging Solutions

Maybe you are looking for