Bend contour (assistant vs labview vision)

Similar Questions

• Cannot get out of Vision Assistant 2009 LabView code

  I use Labview 2009 in my laptop lenovo X 61 with Windows 7 (64-bit) is installed.

  I played a bit with Vision Assistant 2009 and results with my images are good enough. Now, I would get the same functions to work in LabView. I try to make 'tools' - 'create labview VI... '. "in the wizard of vision. All is well, to the point I should see the code. Vision Assistant opens the "Getting Started" Labview, but then nothing happens. I don't see VI in my folder specified and all stop there.

  If any of you have an idea how to solve this problem, I would be very happy.

  Tommi

  There is a known problem with the generation of code in Vision Assistant 2009. Check out this KB:

  http://digital.NI.com/public.nsf/allkb/DFB0B9C7F817D66386257626005A5825

  In addition, LabVIEW options (Tools > Options) make sure you Protocol ActiveX are activated and grant access to a VI called 'IVA create LabVIEW VI.vi' in the list of exported screws.

  -Christophe

• I built a simple motion using LabVIEW Vision Assistant detector. Could someone suggest improvements to it?

  This is one of my first projects LabVIEW, and it's just a simple motion detector.

  Could someone suggest improvements, please?

  As to improve the clarity of the image, reduce noise, etc.

  I used the truncated FFT and it reduces noise well, but moving objects is reduced to blobs.

  My included VI has 2 main controls:

  (1) multiplier brightness (default: 1)

  (2) gain (default: 10)

  Hello

  You'll find them at the stage of analysis of particles

  .

• count pixcel labview vision 2013

  Hi gays

  I need your help I want to count number of pixel with model mink labview 2013

  Thank you

  Try the VI IMAQ number of 2 objects in motion and Vision > visionique > count and measure objects palette.

  If that is not exactly what you want, you can always choose to pass inspection VBAI to LabVIEW (Tools > Inspection migrate for LabVIEW of VBAI) and look at the generated code. It will produce exactly the same results as in VBAI. The only thing is that the generated code is complex.

  I hope this helps.

  Christophe

• Cannot get DAQ Assistant in Labview to cDAQ 9184

  I am trying to build a system for the acquisition of data with one NOR cDAQ 9184. I installed the drivers for the system and I'm able to get to the DAQ system using NI Max (under my system - devices and Interfaces - devices on network) and all channels appear well, however, I tried to follow the procedure described in http://www.ni.com/white-paper/11703/en/#toc2 to integrate my system with LabView and I am unable to find the tab software under the unit to be able to write the RIO 3.5.1 on the appliance and cannot find the device to through the LabView project.

  Your real problem is error-50103.  This is a common mistake, and you can find the answers for it if you are looking for in the forums.

  The problem is that you can't have several tasks (or several assistants DAQ) try to access the same device at the same time.

  Make a DAQ assistant who has all defined channels you wish to purchase.

• LabVIEW Vision will not create large AVI file

  Good afternoon

  I'm having a problem with my camera data storage in an AVI file for further processing.

  Installation of equipment:

  Camera of the Grey Gazelle edge

  2 cables of camera Link

  Card PCIe-1433

  Software:

  LabVIEW 2013

  Module vision 2013

  Computer:

  Dell Inspiron

  Windows 7 Professional

  NTFS drive - 1 TB

  16 GB OF RAM

  X 4 PCIe bus does support speed

  Now the camera captures approximately 280 fps.

  I have a LabVIEW application that captures the image and writes it to an AVI file.

  I use 1 buffer IMAQ and the loop runs so fast that he has an image to store.

  I found the best performance using the codec uncompressed Y800 gray.

  First series of tests, with only 8 GB of RAM.

  When I run 10 seconds, everything is good.  I get about 2800 stored images.

  When I tried to run for 20 seconds, it would go well for about 12 or 13 seconds and then go very slowly (50 images per second).

  I assumed it was eating to the top of the available RAM.

  So, I replaced the 8 GB of RAM with 16 GB.

  Everything seemed to work as before.

  I ran the routine of capture of data for 10 seconds, he collected all the images, everything is good.

  I then tried to run entering data for 20 seconds.

  It seemed to work very well, the image is displayed on the screen, the gauge of speed indicated that he was turning to about 280 fps.

  When I open the AVI file, he had only 3846 stored images, about 13.7 seconds.

  I ran once again, the capture of data for 30 seconds.

  It seemed to work very well, the image was correctly displayed on the screen, gauge speed indicated that he was turning to about 280 fps.

  When I open the AVI file, he had only 3846 stored images.

  When I checked the hard drive directory, these two test files are the same size.

  2 065 819 KO.

  With the NTFS file system, there should not be a limit to the size.

  And the LabVIEW does not plant when she was doing writing to AVI function.

  Y at - it a maximum size for the AVI file, I run in to?

  Or something else?

  Thank you
  Jeff

  
  

• I need assistance with LabVIEW RT and dll

  Hello!

  I'm new to LabVIEW but I am facing something very difficult.

  I develop with LabVIEW 2012 on a cRIO-9082, and I would use a specific DLL in a VI. The DLL is called TcAdsDll.dll and it is used to communicate with a PLC. (This DLL is provided by Beckhoff, for more information: http://infosys.beckhoff.com/index_en.htm TwinCAT > TwinCAT system > TwinCAT connectivity > TwinCAT ADS).

  When I use the 'library of the call' function with the DLL, I get an error 7. I'm just trying to call a simple function of the DLL.

  I know that in LabVIEW RT (Pharlab) only certain DLLs are supported. I also checked the DLL with the tool of NEITHER, but after the 10th dependend DLL calling it just hangs.

  If someone is able to provide assistance, I would be very grateful!

  Does anyone know, what are the rules for the dll must be met to use in LabVIEW RT?

  Thanks in advance!

  A DLL must call only Win32 API supported by the Pharlap ETS system in question in the first place. Since NO guard updated the ETS with almost every new version of LabVIEW it depends actually. DLL checking tool is the only way I know to check this. If this DLL checking failures, or as in your case tool breaks down, the DLL is not justifiable on the RT system. The Beckhoff ADS DLL is a complex beast with many dependencies on any other DLLs Beckhoff and what else, and as such a bad candidate to run on NI RT systems.

  In addition to this fundamental questions, you have additional problems with the Microsoft c runtime library in his infinite wisdom, has decided to create a new C runtime library version with each new version of Visual C. It is already a problem for a developer when deploying to standard PC Windows, but gets a problem almost unmanagabel when targeting something as Pharlap ETS. NEITHER seems to have paid the MS C runtime for their version of the toolchain Visual C of choice for LabVIEW RT system, but this isn't an option for you. If the 3rd party DLL to be used has been compiled in a version of Visual different C that ANYTHING used for the RT version you want to use, then you almost certainly run into trouble, unless the DLL was created with Visual C 6.0 (now a very old version)!

  I've created in the past as a VI based entirely the LabVIEW ADS communication library. It is a tedious job to know the actual byte stream protocol. Unfortunately it is not something that I can share with the community.

  Your best bet would probably be to use the cRIO Ethercat solution and go with an Ethercat on your PLC interface. EtherCAT is sort of a superset of the ADS interface.

  Maybe you can also talk with these guys here. They have a few ADS LabVIEW library and Ethercat libraries too. Not sure if they are basic DLLS and if they would be compatible with LabVIEW RT well.

• Migrating to labview vision Builder... Many VI

  Hello

  I use the latest version of labview and OR vision builder. Using Vision builder get the coordinates X and Y of the object in this area. I need to export this to labview. I tried going in "Migrating to labview. I created a new folder then I gave the name. When I click OK. It creates many VI. I need this in VI only. When I opened the "main.VI", I see that "make, start." When I check the block diagram. I couldn't find the programe I needed for it.

  Hope you understood my question.

  Can you please help me.

  Thanks in advance

  Another option, which could be used in conjunction with the API mentioned Christophe solution is to your X / Y values the variables that you update your VBAI inspection and then read in your code LV. Here's a tutorial on the use of shared variables to communicate the results to the LV of the VBAI:

  http://digital.NI.com/public.nsf/allkb/D492139A746F91A8862576E80051BBCE

  Here is a video showing how to use the API that Christophe has mentioned:

  http://zone.NI.com/WV/app/doc/p/ID/WV-2424

  Here's a video of the use of shared variables (demo shows using targets of the RT, but the same idea might work locally):

  http://zone.NI.com/WV/app/doc/p/ID/WV-2423

• How to find the DAQ Assistant in LabVIEW student 2009 Edition

  I got 1 Core and Core 2 in LabVIEW 2009 prices in June. When I went to use the student edition I have LabVIEW 2009, I couldn't find the DAQ Assistant. This will present a problem when I come to use it in class this fall. It works fine on my version 8.5.

  You must install DAQmx, just like you had to do with 8.5.

• Cannot start assistant in LabVIEW DAQ

  Hello

  I can't launch the LabVIEW DAQ assistant, but I can do it Max MAX DAQ's not flexible because I can't custom code or convert.  I tried all different ways to open the DAQ assistant and I finally realized something, on the block diagram, I open Tools/Advanced/Edit palette/Express/entry/data acquisition is missing (question mark) and many more functions are missing.

  I use the Labview 8.6 and NIDAQmx 8.7.1 evaluation software

  Can you please tell me what the problem is. I really need to launch of NOR-DAQmx, LabVIEW.

  Rgds

  Paul

  Hi Christ,

  Thanks for the fast service, I did as you said, but it didn't fix it. Basically, there are many media NI LV (8.5 and down) any brand with an X, I selected (highlighted) of Labview Signal Express support, since it was just the support NI LV as you said in the email (there is a message of side will not install it) then I click Next and finish ,. Reboot, lauch labview, move on to block diag/check on Experss VI on the function palette/entries, but lack even). I have als don't have reinstall Labview.

  I don't know if you have a plan B, because I'm stuck or if you can send me a screen shot or dialog of what I do; that will be great.

  Thank you

  Paul

• Why are some attributes of 1394 camera Max writable yet Enumerate in LabVIEW Vision as unwritable

  I know that this room sees its fair share of issues of setting attribute camera but I hope that it is sufficiently different to justify an exchange of views.

  I'm in the middle of a piece of code that used to use IMAQ Legacy 1394 to IMAQdX since NEITHER decided to drop the single 1394 support portage.  I ran into an interesting problem.  When you work with a DCAM 1.3 complient camera (Prosilica E1360C, firewire) I find that it is possible to manually set the Max gain, but when you list the attributes of the camera in LabVIEW using the enumeration Attributes.vi, CameraAttributes::Gain: Value rises only not available in writing.  How did MAX OR move it?  I tried to write the gain using the gain writing Register register manually by referencing the DCAM 1.3 Spec document and then using the Register.vi to write, but I had no luck.  The same is true when you're just trying to write the CameraAttributes::Gain: Value by using the attribute writing property node.

  Does anyone have a suggestion?

  
  

• Server error VI Assistant vision

  Hello

  For a vision of small machine using myRIO application I use FPGA to pre-process images. For this I do via Vission Wizard to generate the FPGA code, but it seems that the VI server is not configured correctly.

  Tools > Options > VI server, I checked TCP/IP (with port number 3364) and have also added the VI mentioned in the error to the exported screws and gave access. Assistant to the Vision still don't generate FPGA code and giving the same error.

  Attached screenshots.

  Kind regards.

  I see that the TCP port is 3364. Can you please try to change it to 3363 and let us know if it works?

  I apologize for thinking that 3 months later.

  Thank you.

• missing 2013 LabVIEW daq Assistant

  I do not see the DAQ assistant in Labview 2013!

  LabVIEW 2013 + real-time + fpga

  Max 5.5.1

  Visa 5.4.0

  August 2013 device driver

  Why?

  Thank you

  
  

• The USRP CSD requires the LabVIEW Communications?

  I recently installed LabVIEW 2013 on my machine, as well as a whole bunch of toolboxes:

  LabVIEW English 2013
  VI Package Manager
  Module LabVIEW Control Design and Simulation 2013
  2013 LabVIEW Datalogging and Supervisory Control Module
  2013 LabVIEW MathScript RT Module
  NI LabVIEW 2013 LEGO (R) MINDSTORMS (R) NXT Module (in English)
  Module OR Vision Development 2013
  Module LabVIEW FPGA of 2013 (English)
  Xilinx toolchain 14.4
  Module time real LabVIEW 2013 (English)
  2013 LabVIEW Touch Panel module
  2013 LabVIEW Robotics module
  Software OR SignalExpress 2013
  LabVIEW Sound and Vibration Measurement Suite 2013
  Module LabVIEW Statechart of the 2013
  LabVIEW 2013 for myRIO Module
  Toolkit OR run real time Trace 2013
  2013 LabVIEW System Identification Toolkit
  LabVIEW Toolkit 2013 Digital Filter Design
  4.3.4 for LabVIEW Modulation Toolkit
  2013 LabVIEW VI Analyzer Toolkit
  2013 LabVIEW Database Connectivity Toolkit
  2013 LabVIEW Report Generation Toolkit for Microsoft Office
  LabVIEW Spectral Measurements Toolkit 2.6.4
  2013 LabVIEW Advanced signal processing Toolkit
  LabVIEW 2013 PID and Fuzzy Logic Toolkit
  Kit filter LabVIEW Adaptive, 2013
  Toolkit LabVIEW DataFinder of the 2013
  2013 LabVIEW Desktop Execution Trace Toolkit
  LabVIEW 2013 Multicore analysis and matrices hollow Toolkit
  LabVIEW 2013 power electric Suite
  Toolkit LabVIEW 2013 GPU analysis
  Biomedical Toolkit LabVIEW 2013
  Module LabVIEW 2013 OR SoftMotion
  NEITHER Motion Assistant 2013
  NEITHER Vision Builder for Automated Inspection 2012 SP1
  OR DIAdem Professional 2012 SP1 (English)
  LabWindows/CVI 2013 development system
  Module time real LabWindows/CVI 2013
  LabWindows/CVI Spectral Measurements Toolkit 2.6.4
  Spectral measures of LabWindows/CVI DURATION 2.6.4
  LabWindows/CVI SQL Toolkit 2.2
  Toolkit for processing Signal of LabWindows/CVI 7.0.2
  LabWindows/CVI PID Control Toolkit 2.1
  Execution of LabWindows/CVI Profiler 1.0
  Measurement Studio Enterprise Edition for Visual Studio 2012 2013
  General safety NI Patch 2nd quarter of 2013
  NEITHER TestStand 2013
  NEITHER ELVISmx 4.5
  NOR-DAQmx 9.7.5
  Xilinx 10.1 Compilation tools (requires the build tools additional Xilinx DVD)
  Device drivers or - February 2013

  I tried to follow this tutorial with the USRP 2932, coming soon, but I found out later that I have seem to have none of the LabVIEW Communications. No not those who prevent me from using the USRP radio? If not, then is there any restrictions on what I can do with the radio without communication?

  Hi BreadLB,

  The link to the tutorial you posted is based on LabVIEW Communications System Design Suite, a new software environment designed to accelerate the prototyping of the algorithm and stable air.  It is a completely separate and independent of LabVIEW environment.  See my post here for more details.  You can also download a free 30 day trial copy here.  Your hardware is supported with LabVIEW and LabVIEW Communications.

  The 2932 NOR is a network based USRP, and there a small on-board FPGA.  For this reason, the FPGA on that specific product is not a target of LabVIEW FPGA.  The NI 294 x / 5 x family has a large Kintex 7 FPGA and can be programmed using LabVIEW FPGA and LabVIEW Communications, as in the tutorial you posted.  The 2932 OR can be used with your host PC and LabVIEW for a variety of applications.  Unfortunately the tutorial that you have linked to your post requires the NI 294 x / 5 x hardware and Communications of LabVIEW.  If you have questions about a specific application for your 2932, please post more details and we would be happy to help you.

• The trio of Labview, card PT and Basler A - 610 camera F gray

  Hi all

  I'm doing a project on the merger of the camera with a PH d teacher. As I am the research assistant I can make all preliminary ups. in any case its very annoying that I'm stuck on the first step. Which is simply the video detection from one camera on LabVIEW. The equipment I use is an A-610f "basler" firewire camera, a gray PT 1394b PCI Express Card (http://www.ptgrey.com/products/firepro/index.asp).

  The basler connects with gray map of PT via a firewire cable. Now that the card is not an OR product it is not shown in the MAX I just need to get the video of LabVIEW, but I don't know where I have to access the camera from.

  I'm using LabVIEW 8.2.1 and I Vision Assistant and Toolkit Vision and Motion installed on my machine. In addition I just download demo version of the Vision Development module as well. Again for the clarification that I just need to acquire video from my camera.

  Finally ive it resolved myself!... .. The main problem was with the son of the late himself! .. I was amazed when gray pt was charging me $75 for a firewire cable because it was available in my country of origin for Rs 250 to the free market. I bought one and then started five days of immense struggle and re struggle. Finally, I thought that ive tried all means why not give it a last try and buy the original cable. I borrowed it from a firm surface and 'khatttaaaaaaak'... it works! Although I had to install the SDK of basler to view the video stream. Once the entrance to the camera was visible on the SDK. It was smooth then leave. IMAQ Max was able to detect the camera. The right software was all that remained to be installed. Once the right software has been installed using MAX. It was all great. The power of the camera was visible on max as well. I opened the Vision Assistant and he began to take the camera feed as well.

  I decided to transfer to another device in the PCI card and hooked to another quality firewire cable. The repeatition of above process ensures that the camera is fed was visible on SDK, MAX and Vision Assistant. Although permitted high-speed bandwidth continues to be a problem. Another problem which forced me to bite the nail outlet there is over and done.

  Moral of the story: use the original substance