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

Similar Messages

  • 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 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 .

  • 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

  • NI Vision Builder vs. LabVIEW RT + NI Vision Assistant

    Hello
    I’m designing a vision application which should be able to run stand-alone (EVS-1463RT). The app will have up to 30 inspection states (read gauge value, checking for the presence specific objects, etc.) approximately. The second requirements are the communication ability with other devices not NI via TCP/IP and logging pictures in FTP.
    Now I’m thinking about the two possible solutions.
           Create an AI with NI Vision Builder
           Create LabVIEW RT app and with using NI Vision Assistant build inspection states
    A have to say that the first solution is not my favorite because I tried to implement the TCP/IP communication in NI Vision Builder and it was function but the using of the server is limited. In the other hand the building the inspection is “easy”.
    The second solution has following advantages for me: better control of the app, maybe better possibility to optimize the code, implementation my own TCP/IP server. My biggest concern is the using NI Vision Assistant to generate the inspection states.
    In conclusion I have to say that I’m not experience in the vision app but the LV RT is no problem for me.
    Thanks for any opinions
    Jan

    Hi Jan,
    > A have to say that the first solution is not my favorite because I tried to implement the TCP/IP communication in NI Vision Builder and it was function but the using of the server is limited.
    Could you give more feedback on this point? What do you mean by "using of the server is limited". More precise feedback and suggestions would help us improve the functionality.
    What I would recommend you look into is the use of the VBAI API. You can find examples in <Program Files>\National Instruments\<Vision Builder AI>\API Examples\LabVIEW Examples
    This features allows you to run VBAI inspection within your LabVIEW application, an retrieve results that you can send using a TCP implementation of your own in LabVIEW, without having to use the VBAI TCP functionality.
    You retain the configuration feature of the Vision part of the application, and can add extra code in LabVIEW.
    The API functions allow to basically open an VBAI inspection file, run it synchronously or asynchonously, and retrieve images and results.
    As you mentioned, the other solution is to implement your state diagram in LabVIEW and use the Vision Assistant Express VI in different states. What VBAI give you that Vision Assistant doesn't is the pass/fail limits for each step (and the state diagram).
    Best regards,
    Christophe

  • NI Vision Assistant - "Create LabVIEW VI" produces a blank VI

    Hello, I'm using:
    - LabVIEW 2011 SP1 v11.0.1 32bit
    - Vision Assistant 2011 SP1 Build 20111212112331
    When I create a simple script in Vision Assistant and click on "Create LabVIEW VI", the VI file is created, but when I open it, I can only see a blank VI.
    I really hope someone could help me, I don't know how to solve this problem.
    If you need more informations, I'll provide them.
    Thank you!

    Hi Claudio, I added the following Express VI in a blank block diagram, like you suggested:
    "Prompt User for Input"
    "Vision Acquisition"
    No error messages appeared after having placed them in the block diagram, or after their configuration.
    However, if I place a "Vision Assistant" Express VI, I still receive the following message error after having configured it:
    "There was an error in the process of creating the Express VI's code"
    Moreover, I tried to repair the following modules, in sequence:
    NI Vision Common Resources 2011 SP1 f1
    NI Vision Assistant 2011 SP1
    NI Vision 2011 SP1
    For each of the 3 reparations, I had to reboot the PC. However, the problem hasn't disappeared, I'm still unable to generate a VI by using Vision Assistant.
    I really hope to solve this annoying problem, because the day of my exam is getting closer... so suggestions are more than appreciated, at this point I don't know how I could fix that.
    In attachment you can find a simple Vision Assistant script, and the blank VI produced. Please note that Vision Assistant always produces a blank VI, no matter of the script, like I stated earlier.
    A final note, I tried to generate C and .NET code for the script in attachment while using Vision Assistant, and it seemed to work (no message errors or blank C/.NET files produced), so this is a problem related to LabVIEW code generation only.
    Attachments:
    Simple_script_but_still_not_able_to_produce_a_VI.vascr ‏2 KB
    Blank_VI_produced_by_Vision_Assistant.vi ‏5 KB

  • So I want to use an imaging device with Vision Assistant then incorporate that into my LabView 8.6 code. How can I do this?

    So here's what I have so far written, I have LabView program to interface with my microscope stage, autofocus. I want to try now to interface the camera using Vision Assistant.
    The procedure I want the program to perform is taking this CR-39 detectors and placing them on this stage and the camera to take images of this detector frame by frame. So I want the program to go to the very top corner of the detector on the stage. Then the camera would autofocus (if needed) and take an image. So this would take an image for every micron of the detector on that row. Then move to the next  and so on. Until it has successfully imaged the whole detector.  Is anyone well versed on Vision Assistant and willing to give some advice on this? It would be greatly appreciated.
    The purpose is eliminate the previous method of acquiring images by manually focusing on the tracks created by the particles. I want to this program to run itself without a user being present, so just pressing a button would send the program into autopilot and it would perform the procedure.
    What are CR-39 detectors?
    Allyl Diglycol Carbonate (ADC) is a plastic polymer. When ionizing radiation passes through the CR-39 it breaks the chemical bonds of the polymer and it creates a latent damage trail along the trajectory of the particles. These trails are further ethced using a chemical solution to make the tracts larger which can finally be seeing using an optical microscope.
    Thank you,
    HumanCondition

    Hi Justin,
    Yes I already have a vi that controls the stage.
    So the camera is stationary above the stage. Now what I want to do is get the camera to take the pictures of the detector by moving the stage frame by frame for example starting from the top right corner of the detector (by taking an image) then ending on the top left corner of the detector (by taking an image) then having the stage move down a row and starting the process over again until each frame (or piece) has been imaged.
    My goal is while the stage is moving to every little frame of the detector I would like for it to autofocus if necessary, and take a image to be for each frame of the detector.
    Using the auto focus requires the moving of the stage up and down.
    HumanCondition

  • Vision assistant problem

    Hi guys,
    I am having a problem with vision assistant when i run the script within vision assitant it locates all of my patterns and finds the template file paths etc and all is good. However, when i run my application the vision assistant fails to locate the patterns or the template file paths. Any help in why this is happening woud be of great help.
    Regards,
    Damien
    Solved!
    Go to Solution.

    Hi,
    Thank you for replying. Yes i created inputs paths and i believe the paths are correct. The strange thing is i have a number of inspections that work using vision assistant but for this one inspection it wont work. I have attached a screenshot of the vi with file paths etc. It is the same as other inspections that work so i am lost as to why this particular vi wont locate the templates/patterns.
    Damien
    Attachments:
    Doc1.docx ‏227 KB

  • Vision assistant or builder tools into LabView

    hi, I just wanted to know if anyone knew how to use a vision assistant or vision builder into labView using a live image from a camera, that is already installed as a visa resource. Cheers

    Hi reivaxseniab,
    I think the best place to start would be one of the tutorials (link below).
    http://digital.ni.com/manuals.nsf/websearch/7449F8D894ED3F9D8625745100771596
    This should help you with using a live image from a camera in LabVIEW.
    Kind regards,
    Josh E
    Applications Engineer
    National Instruments UK & Ireland

  • 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

  • Vision assistant in LabView

    Dear All,
    I am not that familiar with LabView yet, and would really appreciate some help.
    I have attached to this message three documents. the first one represents the block diagram of how I can use a few tools from labview with my thermal camera. All this works fine for this one. The second one, is a tool developped from Vision Assistant, but created as a LabView VI, so same in the block diagram. And in the third one, is the block diagram of the two (the first which corresponds to image and few data from the camera, and the second one the tool developped in Vision assistant) together. Bacsically my question is, could you help me or show me how to link the two, so that I can use the tool developped in Vision Assistant with my image from the thermal camera (file 1). Link file 1 and 2 together basically.
    Many thanks for your time
     reivaxseniab
    Solved!
    Go to Solution.
    Attachments:
    GetImageExample.vi ‏32 KB
    trial 1.vi ‏68 KB
    trial 2.vi ‏94 KB

    Hi Xavier,
    I am not really sure what you mean by it doesn't seem to work, it looks to me like the VISA reference wire is going into the "Close.vi" fine, are you referring to how there is a broken run arrow up the top left of the program, not allowing your program to run?
    If you click on that broken run (or hit ctrl+r) arrow it will automatically give you an error list of items to fix like the first attachment.
    In your case you wont have the errors where subVI's are missing, but you will have the errors of tunnels not being wired together correctly, if you double click on that error it should take you to the area on your block diagram where the error occurs. Your VI's have a couple of tunnels hidden behind each other like the second attachment.
    You may want to move these out from each other so that they are easier to wire into individually, like the third attachment.
    You want to make sure that each of these terminals have data wired in to them in each one of your cases so that they do not appear as an empty shell, but as a solid colour.
    These links are good for understanding case structures and terminals a bit more.
    These are all subjects covered in LabVIEW Core 1, I would suggest Xavier that if you are looking to use LabVIEW more in the future it is often more beneficial to sit down and dedicate three days to learning these principles with exampls and excercises than struggling to piece together code, if you're an academic in the UK training is at a discounted rate. Let me know if you're interested.
    Best regards,
    Mark W
    Applications Engineer
    National Instruments UK & Ireland
    Attachments:
    Error list.PNG ‏33 KB
    Terminals clumped.PNG ‏2 KB
    Terminals neat.PNG ‏2 KB

  • Make a Line Fit with Vision Assistant for a polynominal function?!

    Hello
    I do have following problem to solve: I do have a laser spot which draws a line (non linear) to a wall. For this line I need to know the (exact) mathematical
    function. Therefore I can get an image of the line but I do not know how I can extract the mathematical function with a line fit for example. If I could "convert"
    the line into points I would use the line fit function of LabView which should work without problem.
    Is there a way to solve the problem with the vision assistant or..?
    Thanks in advance
    Solved!
    Go to Solution.

    Hello,
    by now I have learned that (almost) anything is possible. You can achieve this using Labview, Matlab, C++, etc... In any case, getting the coordinates of a single laser line (single laser line - you don't need to find correspondences, as opposed to multi-line projection) should be really simple. If you place an apropriate filter in front of the camera, it is even simpler!
    If you want proof it can be done (and the description/procedute I used), check out the link in my signature and search for laser scanner posts (I think there is three of them, if I remember correctly). I have made a really cheap scanner (total cost was around 45 eur). The only problem is that it is not fully calibrated. If you want to make precise distance measurements, you need to calibrate it, for example using a body of known shape. There are quite a few calibration methods - search in papers online.
    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."

  • Profile Performance in LabVIEWvs Performance meter in Vision Assistant: Doesn't match

    Hi everyone,
    I faced a strange problem about performance timing between these two measurements.
    Here is my test
    -used inbuilt example provided by labview in vision assistant-Bracket example-Uses two pattern matches, one edge detection algorithm and two calipers(one for calculating midpoint and other for finding angle between three points.
    -When i ran the script provided by NI for the same in vision assistnat it took average inspection time of 12.45ms(even this also varies from 12-13ms:my guess is this little variation might be due to my cpu/processing load).
    -Then i converted the script to vi and i used profile performance in labview and surprisingly it is showing way more than expected like almost ~300ms(In the beginning thought it is beacuse of all rotated search etc..but none of them make sense to me here).
    Now my questions are
    -Are the algorithms used in both tools are same? (I thought they are same)
    -IMAQ read image and vision info is taking more than 100ms in labview, which doesn't count for vision assistant. why?( thought the template image might be loaded to cache am i right?)
    -What about IMAQ read file(doesn't count for vision assistant?? In labview it takes around 15ms)
    -Same for pattern match in vision assitant it takes around 3ms(this is also not consistant) in labview it takes almost 3times (around 15ms)
    -Is this bug or am i missing somethings or this is how it is expected?
    Please find attachments below.
    -Vision Assistant-v12-Build 20120605072143
    -Labview-12.0f3
    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
    Attachments:
    Performance_test.zip ‏546 KB

    Hmm Bruce, Thanks again for reply.
    -When i first read your reply, i was ok. But after reading it multiple times, i came to know that you didn't check my code and explanation first.
    -I have added code and screenshot of Profile in both VA and LabVIEW.
    In both Vision Assistant and Labview
    -I am loading image only once.
    Accounted in Labview but not in VA, because it is already in cache, But time to put the image into cache?
    I do understand that, when we are capturing the image live from camera things are completely different.
    -Loading template image multiple times??
    This is where i was very much confused. Beacuase i didn't even think of it. I am well aware of that task.
    -Run Setup Match Pattern once?
    Sorry, so far i haven't seen any example which does pattern match for multiple images has Setup Match Pattern everytime. But it is negligible time i wouldn't mind.
    -Loading images for processing and loading diffferent template for each image?
    You are completely mistaken here and i don't see that how it is related to my specific question.
    Briefly explaining you again
    -I open an image both in LabVIEW and VA.
    -Create two pattern match steps. and Calipers(Negligible)
    -The pattern match step in VA shows me longest time of 4.65 ms where as IMAQ Match pattern showed me 15.6 ms.
    -I am convinced about IMAQ Read and vision info timing, because it will account only in the initial phase when running for multiple image inspection.
    But i am running for only once, then Vision assistant should show that time also isn't it?
    -I do understand that, Labview has lot more features on paralell execution and many things than Vision Assistant.
    -Yeah that time about 100ms to 10ms i completely agree. I take Vision Assistant profile timing as the ideal values( correct me if i am wrong).
    -I like the last line especially, You cannot compare the speeds of the two methods.
     Please let me know if i am thinking in complete stupid way or at least some thing in right path.
    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 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.

Maybe you are looking for