Count pixels labview vision 2013

hi
i want to determined percentage of pixels in a region, like function count pixcels in NI Vision Builder AI but in labview vision 2013 

Brad, thanks for the response. I don't have access to the code anymore, I was more just curious about it. One of my old coworkers has actualy been in contact with me recently because he's the one who inherited my code. I had to walk him through how I implemented the VBAI code in to the main application because he couldn't just change a few setting inputs. It was more of just a inconvenience.
I guess my suggestion for the future would be for an option to output the VBAI code as LabVIEW code without all of the subVI hierarchy for those who are used to just using the IMAQ VIs. Just a linear set of code that goes from the start to fnish of the VBAI diagram that I could manipulate the way I want would be nice.

Similar Messages

  • Count number pixcel labview vision 2013

    hi gays 
    i need your help i want to count number of pixel with template in labview vison 2013 
    thanks 
    Solved!
    Go to Solution.

    Try the VI IMAQ Count Objects 2 in the Vision And Motion>Machine Vision>Count and Measure Objects palette.
    If that does not do exactly what you want, you can still choose to migrate the VBAI inspection to LabVIEW (Tools>>Migrate Inspection to LabVIEW from VBAI) and look at the code generated. It will produce exactly the same results as in VBAI. The only thing is that the code generated is complex.
    Hope this helps.
    Christophe

  • I purchased Adobe Acrobat x Pro recently and installed it, I have compatibility issues vision 2013. The adobe pdf converter  plug in stays inactive despite all my efforts to activate it, I need help with this? How can i get the plug in

    I purchased Adobe Acrobat x Pro recently and installed it, I have compatibility issues vision 2013. The adobe pdf converter  plug in stays inactive despite all my efforts to activate it, I need help with this? How can i get the plug in to work with Visio 2013?

    For MS Visio (any version) only the appropriate version of Acrobat *PRO* provides PDFMaker for Visio.
    For Visio 2013 specifically you must have Acrobat XI Pro (updated to at least 11.0.1).
    See: 
    http://helpx.adobe.com/acrobat/kb/compatible-web-browsers-pdfmaker-applications.html  
    Be well...

  • I purchased Adobe Acrobat x Pro recently and installed it, I have compatibility issues vision 2013. The adobe pdf converter  plug in stays inactive despite all my efforts to activate it, I need help with this? How can i get the plug in to work with Visio

    I purchased Adobe Acrobat x Pro recently and installed it, I have compatibility issues vision 2013. The adobe pdf converter  plug in stays inactive despite all my efforts to activate it, I need help with this? How can i get the plug in to work with Visio 2013?

    For MS Visio (any version) only the appropriate version of Acrobat *PRO* provides PDFMaker for Visio.
    For Visio 2013 specifically you must have Acrobat XI Pro (updated to at least 11.0.1).
    See: 
    http://helpx.adobe.com/acrobat/kb/compatible-web-browsers-pdfmaker-applications.html  
    Be well...

  • VBAI vs LabView/Vision?

    I am designing a machine vision system that will use 16 GigE cameras, run on a dedicated PC, and will use standard edge and blob tools to perform a fairly routine set of inspection tasks.  I will not need to code any new special-purpose image algorithms.
    Because of the large number of cameras, I am interested in using parallel processes/threads as much as possible.
    Also, I need to trigger inspections via Ethernet/IP from a Allen Bradley/Rockwell PLC.
    Would there be any obvious advantages to using the Labview Vision Development Module rather than VBAI?

    Here are some things to consider (in addition to what Christophe said).
    1. You had asked about 32 vs. 64 bit OS..even if you're running a 32-bit application, I would always recommend a 64-bit OS. This allows multiple 32-bit applications to each have up to ~4GB of memory, and if you're talking about 16 instances of VBAI running, they can each get up to this limit instead of on a 32-bit OS being limited to the total memory available being 4GB shared between all applications.
    2. Because VBAI only allows 1 instance to run the Ethernet/IP Server, you could use LabVIEW to do the communication over Ethernet/IP and manage triggering/acquiring images in parallel and then use the VBAI API to send the images to the VBAI engines with a set image variable call so the VBAI only has to process the image and send the results back to your LV program. I really liked Christophe's idea of using a network trigger that the PLC controls, but I don't know if your cameras support network triggers or if your PLC would support sending a action command to trigger them...maybe the PLC can just trigger them directly with I/O lines...I assume this isn't an option since you're wanting to use Ethernet/IP to tell another application when to trigger them.
    3. If all your inspections are exactly the same (except for which camera they use), VBAI unfortunately has a restriction that only one engine can open an inspection at a time, so you'd have to make 16 copies of the same inspection and have each VBAI instance load a unique copy of the same inspection.
    4. If this is the case (all your processing is the same), and the inspection is straight forward, I think using LabVIEW to run everything in parallel with a rentrant VI that does the acquisition and vision algorithm might be the simpliest and fastest approach, but it might take longer to develop the code.
    Hope this helps give you some more ideas, and let us know if you have more follow-up questions.
    Brad

  • Labview Vision Assistant Histogramm Problem

    Good Morning,
    i sadly with the Vision Package from Labview. I want to load a picture and interpretation a detail of the picture with black, white and grayvalve. This can i make with the Vision Assistant feature Histogramm. When i build it (the VI with Vision Assistant) comes nothing to the output Histogramm. I have checked the output line Histogramm, but nothing goes out of this.What are my failure?
    Thanks a Lot
    german translation:
    Hallo zusammen,
    ich bin leider noch nicht richtig mit dem Vision Paket vertraut. Ich möchte die Schwarz, Weiß und Grauwerte eines Bildausschnittes auslesen und diese auswerten können. Dank des Vision Assistant, kann ich dies per Mausklicks erzeugen, jedoch erhalte ich am Ende des Vis keine Daten. Selbst wenn ich die Quelle verbinde und ein Anzeigeelement hinzufüge, kommt hinten nichts raus. Was ist mein Fehler?
    Vielen Dank
    -motecpam
    Labview Vision 2011 Servicepack 1
    with Vision Development Modul
    Attachments:
    Screenshot_VI.jpg ‏230 KB
    Screenshot_Vision_Assistant.jpg ‏313 KB

    Hallo Tropper,
    vielen Dank erstmal für die Antwort.
    Leider erhalte ich dennoch keine Ausgabe am Histogramm.
    Das Histogramm wird mir leer angezeigt.
    Ich habe es so erstellt, wie von dir gezeigt.
    Attachments:
    Unbenannt.jpg ‏117 KB

  • Does labview vision support GigE Vision cameras using H264 compressio​n?

    Does labview vision support GigE Vision cameras using H264 compression?
    I'd like to use a GigE Vision compliant camera that encodes its video data using H.264 compression. Can Imaqdx read this stream, decode the H264 compressed frames and write the frames into an imaq image?
    global variables make robots angry

    I have no info whatsoever on your question, but welcome back from your hiatus!
    Spoiler (Highlight to read)
    Actually I know the answer but it is simply more fun sitting back and watching you figure it out yourself. 
    Actually I know the answer but it is simply more fun sitting back and watching you figure it out yourself. 

  • Labview VISION + webcam + find pattern

    Hi all,
    I'm making a job with pattern recognition. Unfortunately, I'm doing a first steps and don't understand everything.
    I found a video regarding of this question > http://www.youtube.com/watch?v=trgCbKZXyUE - it's what I want to build and extend it then.
    The diagram is finished as on the video, but I cannot catch and follow the necessary pattern. It's showing all the current image instead of requested object.
    I think it's not a big issue to find out the problem, but I don't have enough skills to locate it.
    So, please, if you can, correct the diagram, which you can find in attachment and then I can go on with my goal.
    Thank you in advance.
    Regards,
    Michael
    Attachments:
    Object Detecting and Tracking.vi ‏93 KB

    Hi Michael,
    habe you seen that link if you expand the Youtube comment which starts with something Spanish?: "En este ..."
    Community: LabVIEW VISION - Busqueda de Patrones - National Instruments
    https://decibel.ni.com/content/docs/DOC-31880
    Can you make it work if you follow the detailed screenshots shown on the NI community page?
    Best regards,
    Chris

  • Labview vision - while loop + image + shiftregister = 2 times same image.

    Well I got this problem here at home. 
    I've this .vi 
    I've labview 8.6 + labview vision module + labview vision module for usb webcams.
    Well this .vi is pretty simple but it gives me some strange results...
    When I run this I get the same image on "image1" and "image2"... while in fact "image2" should be the "image1" of the last loop. This should be visible when you set the sleep time of the loop higher. Now the problem is is that on my frontpanel "image1" and "image2" are ALWAYS equal... But then when I click on the two wires of "image2" and "image1" then the difference is visible. But on the frontpanel "image1" equals "image2"...
    A couple of weeks ago when I first was testing with labview + vision on my university there was a visible difference between the two images. This was with the same webcam and software.  
    Anyone got an idea how this is possible? 

    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 .

  • How can I determine the liquid level in a bottle (LabView Vision)?

    How can I determine the liquid level in a bottle (LabView Vision)? Does anybody have an example code? The task is, that if liqid level is between two predetermined level, the program writes, that it is correct else it writes incorrect. Thank you.

    here is a little play with your bad picture:
    used only the small field of interest (here a guess) ,
    used only the red channel ( takes out most of the light reflection)
    grey scale, 3x(blurr, median filter) , played with  contrast -gamma - saturation
    now you need to add the edge detection and some sort of scale.
    Greetings from Germany
    Henrik
    LV since v3.1
    “ground” is a convenient fantasy
    '˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'

  • Labview myRIO 2013 stopped working after product activation, system vi files not found, (Hex 0x8004041F)

    Hello,
    My Labview myRIO 2013 had been working while it was in its evaluation period. Recently, I activated Labview 2013 with a 6-month activation code. Now, if I try and create the standard myRIO tutorial starting project, when it tries to load "Main.vi", it stops and says:
    Loading: 
    <vilib>:\myRio\Common\Instrument Driver Framework\myRio v1.0\myRIO v1.0 Reset FPGA.vi
    Searching:
    C:\Prog... \LabVIEW 2013\Targets\instr.lib
    and it pops up a file browser dialog box.
    I found the file in C:\Program Files (x86)\LabVIEW 2013\vi.lib\... , so I manually added that path to Labview's VI search paths, closed everything, and re-opened Main.vi .
    After doing so, I can get Main.vi to load and display properly after taking it's dear sweet time to recursively search vi.lib\* for each vi file, but if I try to run it, I get a crytic and un-googlable error message:
    NI System Configuration: (Hex 0x8004041F) The operation failed because of missing dependency items.
    It gives no further information on what dependency items are missing.
    Why did Labview work before? It had no problem finding dependency vi files before I activated the product. The "Getting Started" demo apps still work fine, reading accelerometer data and controlling the led's on the myRIO, so I know the myRIO itself is working, along with the USB connection. 
    One final note, the "Labview 2013 Real-Time Module" has not been activated. Could that be the problem?

    Hi Mike,
    That Hex error message only occured if I tried to run the VI by clicking on the little "run" button at the top left. Main.vi would open just fine, after locating all of the vi files.
    So I seemed to have fixed my particular issue (for now)... I had noticed after I typed in my activation code that Labview was telling me that I had additional evaluation time available to me. I had been ignoring those messages because, 1. I had an activation code and therefore didn't need additional evaluation time, and 2. Labview was opening and appeared to be running just fine, whereas before I applied the activation code, Labview would not even start. So, towards the end of my adventure after I felt I had applied my forehead to my keyboard a sufficient amount, I finally said "Ok whatever, give me additional evaluation time", and voila, all of my previous issues disappeared. Vi files were being found normally as before, and I was no longer getting that Hex error when I hit the run button. 
    I'm not sure exactly what components I'm getting "additional evaluation time" for, but whatever component it is, it seems to have fixed my problems.
    So anyway, thanks for the support! Hopefully this fixes my problem for good

  • 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

  • Labview Vision

    I'm having trouble finding out what is I would need to purchase to use he vision toolkit in labview 7.1 .
    I've got labview 7.1 + development.
    Now all I need is the ability to use vision tools like "find edge" and "count objects".
    I don't need any extra programs like vision assistent.
    Which of the following do I need.
    Maybe someone can explain to me what the following things mean:
    777859-03 NI Vision Development Module for LabVIEW 1 - 2 2,845
    777860-03 NI Vision Development Module for Measurement Studio 1 - 2 3,045
    778044-01 IMAQ Vision Deployment Engine for One User 1 - 2 320
    778044-00 IMAQ Vision Deployment License 1 - 2 320

    run time engine or kind of .
    You need to by one for each one of your deployed exe...
    Doc-Doc
    http://www.machinevision.ch
    http://visionindustrielle.ch
    Please take time to rate this answer

  • Creating a digital counter in labview

    Currently using a proximity switch connected to an SCC-DIO1 to read pulses from an encoder to develop an RPM measurement ( and angular velocity).  How do I convert my digital pulse into a true numeric count per minute (or millisecond)?  I'm able to detect the pulse from the module in labVIEW but I'm unclear on how to count the pulses per minute.      Currently using labVIEW 7.1.

    If all you're doing is counting pulses, you'd actually be better off
    using the counters on your DAQ card. They automatically track the
    number of pulses and can give other info like frequency. Look in the
    Examples for Counter VIs to show you how to use them. There's a pretty
    good one named "Getting Started Counter.vi".
    If you're set on just using a digital line, the attached image shows
    how to setup a basic 32 bit counter. (but I still suggest you have a
    look at using the Counters)
    Ed
    Message Edited by Ed Dickens on 07-14-2005 03:38 PM
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
    Attachments:
    32 bit Counter.gif ‏5 KB

Maybe you are looking for

  • Can't Print or Scan from your OfficeJet Pro after Upgrading from your Win 8 to 8.1?

    Are you having problems when attempting to print or scan from Windows 8.1 after printing/scanning successfully prior to upgrading to 8.1?  Uninstall/Re-install.  With this, I might suggest going to your product page on HP.com (sample link posted belo

  • Outlook 2007 Contact Notes not showing up on BlackBerry. HELP Please!

    Using BB Desktop Manager 4.5. I have about 75 contacts with notes in the notes field in Outlook 2007 Contacts. I looked at the mapping fields in the Address Book and I do not see one for the NOTES field in Outlook 2007. I have checked the transfer al

  • Account assignment group

    Hi, what is Account assignment category. what is it's purpose. what it controls and where are it's config settings. for instance account assignment category is a cost centre or a sales order. what it means and what it controls as far as a sales order

  • 64 bit windows 8.1 on Stream 7

    will the stream 7 be getting 64bit device drivers? the atom inside this model is x64 based and many of my programs are only in 64 bit. Also thr windows license agreement allows for either a 32 or 64 bit installation. This question was solved. View So

  • Site attributes changed after crash

    Hello, After importing an Edge animate object for testing in my site, Muse crashed as I deleted the object. No error message except the Windows box telling me Muse was closing. After restarting Muse and opening the site, I found, when I viewed it, th