Runing VBAI Inspection of LabVIEW

Similar Questions

• VBAI migration to labview

  Hey guys,.

  I get an error when I run my application the error I get is error-1074396120 was held at IMAQ Image read, it says IMAQ vision is not an image. It works very well in VBAI I have a snapshot of the image, but it gives error in labview, suggestions. Thank you

  Damien

  Found that error had the unit running in another application.

• Error - Vision Builder Inspection to LabVIEW Migration

  
  

  You can verify that you have read/write access to your temporary folder (in general C:\Documents and Settings\Settings\Temp).

  This error is due to the fact that a temporary file (VBAI.bin) is probably not written in this file or cannot be read during code generation. Is it present in this folder after you try to generate the code?

  What privileges you have when you run Vision Builder AI? If you are logged on as administrator? You can try to run Vision Builder with administrator privileges and see if you still get the same error?

  Also, what operating system are you using?

  Thank you

  Christophe

• VBAI

  Hello

  I'm building an inspection in the generator of vision OR for automated inspection. I just downloaded a VI specifying VBAI of Labview. What defines a remote target? Also how to import a folder of the VBAI inspection in LabView.

  If you run an inspection on a real-time target, this is where you can specify the IP address of the target. The drop down menu will automatically fill with all targets detected on the local subnet. Looks like you want to run the engine VBAI on your local machine. You should check the example LabVIEW API example (Local) .vi. It will launch a local VBAI engine and allow you to navigate to an inspection on your machine to open/execute/recover results/images.

  Hope this helps,

  Brad

• What to enter in the "Session of" while doing a VI in labview for inspection... using vbai?

  I want to do a VI for the purpose of inspection using Labview 8.6.
  I am a beginner and I want to know what is meant by session in 'Vbai open inspection'...?
  I use a usb for aquistion camera!

  The open inspection VBAI is a session to a VBAI engine. If you want to perform the inspection on your PC, use the launch room. engine VBAI VI to start a local VBAI engine, then use the VI VBAI to connect to connect to the engine and then you can load inspections, run them and retrieve images of results. See the example for navigation in your VBAI under the API examples/LabVIEW directory. You will need to have an inspection already registered using the ordinary VBAI executable. Make sure that the executable file is closed before you try to use the inspection with the LabVIEW API because a process can use the camera at the same time.

  I hope this helps.

  Brad

• VBAI 2011, possible to migrate directly to LabVIEW 8.6 code?

  Hello

  I was wondering if VBAI 2011 can migrate from the inspections directly to LabVIEW 8.6 code.  I have installed on my computer:

  VBAI 2011

  LabVIEW 8.6

  LabVIEW 2010

  LabVIEW 2011

  Module OR Vision Development 2011

  I don't see the option for LabVIEW 8.6 in my menu.  Any suggestions?

  John Wu

  Riobotics Consulting

  I encourage you to watch the Vision Builder AI LabVIEW API, which is supported in LabVIEW 8.6.

  This feature allows you to control Vision Builder AI of LabVIEW (open inspection, run once, get results etc.)

  Unless your application requires very tight hardware integration, with equipment you can do only in LabVIEW code, the code that you write with the API will be much cleaner to work with generated code, which is somewhat complex.

  Look at the examples located here:

  C:\Program Files (x 86) \National Instruments\Vision VBAI 2011\API Examples\LabVIEW examples

  Best regards

  Christophe

• VBAI Interface - Get Image-> Dest Image inspection

  I have a complete Vision algorithm built in Vision Builder AI and programmed a VI in Labview that started the algorithm and results used to calculate. It works very well. Connection between Labview and VBAI is correct and the results are updated. Now, I want to show the image of the VBAI in my Labview GUI using the VI 'VBAI Interface - get Image Inspection' of the Vision Builder AI toolbox. Everything I try to connect at the entrance of "Image transfer" of the VI I am unable to let it run and give an image appears. See attached screenshot for details.

  -What type of entry how can I put a link to get this working VI?

  -Where can I find more detailed information in the context-sensitive help on all these VBAI VI toolkit?

  You must use IMAQ create to create an image. You can see an example of this in the case of Vision Builder AI under API Examples\LabVIEW Examples\LabVIEW API example (local) .vi

  Hope this helps,

  Brad

• Inspections running in parallel with VBAI via ActiveX

  Hello

  I would like to integrate VBAI inspections in our high level LabVIEW application. However, due to the limits of performance, I need to use all 4 cores of the computer processor. I investigated the possibilities of inspections by ActiveX VBAI running. If I understand correctly, at the same time I can have only one target connected and the target can have only one open inspection. This means running parallel inspection is not possible. Am wrong me or is there anyway how to achieve parallelism?

  EDIT:

  To make it clear, I want to talk to the local target (PC).

  Vladimir

  Hi Vladimir,.

  It turns out that it is indeed expected behavior. The only thing I can recommend is to somehow combine inspections into one (using logic in the State where machine).

• Create an exe to LAUNCH AN INSPECTION in VBAI

  Good day again NI Experts.

  I would like to ask for a solution to a small problem of mine in VBAI. By default, after you have saved a project VBAI, a file EXE will create for this project. When we re - open the EXE file, we will be directed straight to mode 'Configure the control' of this program. What I need now is to create an EXE file to mode "Run the Inspection" of this program so that when our client opens the application, he or she will be able to run the inspection immediately. Of course we do not want our client to have access to the configuration of the program. Please also note that we do not have software to run if there is VBAI. Any help would be much appreciated. Thank you very much.

  Sincerely,

  Andrei K.

  I don't know what you set on EXE files created in VBAI. You're talking about a. File VBAI?

  If you want VBAI to run automatically in the mode of inspection you should go to the configuration Interface, and then select the Tools/Options menu.

  In the startup section, check 'Start Inspection when launched' and select which VBAI inspection must be run at startup.

  After that, restart VBAI will automatically put it into "run mode of inspection.

  Hope this helps,

• Improve the performance of application VBAI

  Hello

  I have a request, I wrote in VBAI and am satisfied. The problem is that it uses VBAI States for circle detection several times (via a loop). This causes a maximum of 300 ms extra use of the CPU by inspection.

  What I was asking is this: if I migrate my VBAI app to LabVIEW, how can I run it again on the target using LabVIEW RT?

  I'm running a smart camera, NI 1752, with clock 600 MHz and 512 MB RAM. Inspection rate required is 1 inspection per second minimum.

  My application inspects a conveyor which shows (0-8) units per inspection. When no unit is present, the inspection time is fine, but when there are 8 units are equal to ~ 1200 ms per iteration. I suspect it's because of me using machines to States VBAI, which introduced a large number of delays. I do not know code LabVIEW would be more effective.

  Thank you

  Hazim Salem

  If the initial inspection took about one second per iteration. I think there is some overhead of reference that we include in these figures that show us who actually don't occur when you run in mode of inspection and this is why there are ~ 7ms General fresh extra time compared to the sum of all stages of inspection. Anyway, I made some minor changes to the step of PM and it took off about 70ms. I also tried to use a stage run LV to do all detections of circle at the time and overlays, so you don't need to make a loop and it saves another 250ms.

  Original time ~ 1000ms

  New time ~ 680ms

  I have attached the LV code used by the step execute LV and updated control. Don't forget to copy the LLB in the folder of the target at c:\User generation live if you need to make changes, update the Circles.vi multiple detect and rebuild the LLB from the project and copy LLB resulting to the target.

  Hope that helps and let me know if you just want to while LV (that would be the fastest), but maybe the modified VBAI inspection is fast enough now.

  Brad

• Multiple instances of VBAI

  I know that we can now acquire multiple cameras in VBAI (thanks!).  However, in my view, what to do so leads to very complex control sequences.  It doesn't look like VBAI has fully embraced parallelism for anything other than the FTP transfer.  What should I do if I have 5 cameras GigE each needs to be raised, and where it is possible that two can be triggered at the same time?  Can I run multiple instances of VBAI on a single PC (hey, it's multi-core)?  I predict that the current response is to use LabVIEW, but VBAI is especially LabVIEW... right?

  I want to retain only the simple, single camera, inspections on the PC.  Running multiple instances of VBAI would allow me to devote an instance for each camera without worrying about what's happening on TSF the other 4 (or more).

  No, I have not tried to do it again.  Currently, I am out of town and away from my vision laboratory.  I thought that if this is possible, it is worth mentioning to the public and if it is not, then, it is worth noting in R & D.  The system I'm imagining would be a future version of a system, we finished just where we had 4 NI Smart Cameras and a GigE camera.  The question is on what to do if all 5 GigE cameras.  Don't worry, we still love the SmartCams!

  On a sequence of validation.

  Dan press

  PrimeTest Automation

  Hey Dan,

  Good question! VBAI supports the acquisition of several cameras, even if they are triggered at the same time. We have a flag in the acquisition stage that allows to specify if you want to wait as the following picture or purchase immediately. Thus, in the case simple two cameras triggered at the same time, you will have an initial state who tried to acquire the camera 1 and if there was a timeout he loop back and try again using the wait for the flag of the next Image. When an image is acquired, you know that the other camera was triggered, so you transisition to another State who acquires the camera 2 with an immediate flag, since we know that the image is already there. You can use the image select to switch between the two images, so it is possible, but not necessarily the cleanest. Even if you had two VBAIs simultaneously, synchronizing is not trivial to make sure you weren't inspect imageN camera1 and imageN + 1 on camera2, but perhaps this would not be the cause of your system. In any case, we don't currently support multiple inspections VBAI operating simultaneously on a system, but it is certainly a feature that we know.

  Thanks for your series of validation,

  Brad

• VBAI running on computers of 32 and 64 bit

  I have a standard VBAI routine developed on a 32 - bit computer, using a lot of files .vi and running on multiple hosts.  To date, all VBAI instances were on 32-bit computers, without any problem, for example, I just copy the VBAI routine to the new machine and run it.

  But the last instance is a 64-bit server, and while VBAI installs and runs locally, he moved to the folder "...\Program Files (x 86)-...» "that throws all my calls file .vi.  I tried to put the .vi files in the folder maintinaing «...\Program Files\...» "the structure folders and it seemed to work, but it wasn't all parameters, and I couldn't change all the steps...

  So here's my question: is there a way to make my VBAI routine standard running on the 64-bit computer, or do I have to load LabView and recompile the routine?

  Thank you

  Eric

  When you say that you can not change the steps, what do you mean? You get an error on the VI is broken when you change a step execute a VBAI LabVIEW VI? I would recommend that you follow the instructions to create your VI in a LLB built for deployment. You will find these instructions when you change the step run a LabVIEW VI, and you go to help > context display help. There will be a link to 'Saving VI for Distribution' in the FAQ tab, which will guide you in how to do a Bachelor's degree in LAW with all the dependencies that are required in a LAW degree who can travel more easily with your inspection when you move systems.

  I also recommend that you include all in the project of LV, the your source required screws through the various stages of LV run in your VBAI inspection, and that you will have a unique LAW degree which is easy to carry. I also recommend that you put this LLB single in a place that will not change when you move from a (64 bit) (32 bit) to another system, so do put it not in your c:\Program Files (x 86). On the RT, we expect in C:\User VIs\, so you can put your LLB at the same location on your windows machine, and then if ever you move RT, it will be very easy to have found LLB.

  It is important to have your source screw in one place (as well as the LV that allows you to create your LLB) and LLB/source distribution generated in another location (e.g. c:\User VIs\) and when you want to change, change your source screws and use the same project for you rebuild LLB VBAI will use. You do not want to edit your distribution of LLB\source built and accidentally put screws in there, vi.lib or good things will break.

  Hope this helps,

  Brad

• 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

• Cannot see interface in mode of inspection inspection on CVS1458rt

  Nice day

  I did a VBAI (with a custom interface inspection) inspection. The inspection runs on a CVS-1458RT and control interface must be visible on a touchscreen connected via VGA to the CVS. But on the screen connected to the CVS is only part of the visible control interface, the last image of acuired. But the control interface also controls and counter part, which are not visible. Even if the VBAI inspection is defined as a start and no other computer is connected remotely to the CVS (without remote) I can't see the interface of any inspection. What I did wrong? If remote control my RESUME while it is inspectiong I can see the interface all inspection on my computer screen and can change the values of the elements of order entry.

  Thanks in advance

  This is the page where you can download Vision Builder AI 2015.

  http://search.NI.com/nisearch/app/main/p/AP/tech/lang/en/PG/1/SN/N8:2235, ssnavdl.

  Give it a try.

  Christophe

• Compatibilidade do com Vision 2010 in NI LabView 8.6

  Good afternoon,

  Estou a ter um compatiblidade between VIsion 8.6 OR LabVIEW 2010 e o o problema.

  Informei me o problema incompatibilidade poderia estar amendments IMAQ. Then, desinstalei:

  NOR-IMAQ

  E/S-OR-IMAQ

  NOR-IMAQdx

  Barbarella estes por each drivers but recent (supostamente compativeis com o LabView 2010):

  NOR-IMAQ 4.5

  NOR-IMAQ IO 2.4.0

  NOR-IMAQdx 3.7

  APOs este processo, renew a dar o mesmo erro compatibilidade. "This inspection of LabVIEW migration requires that you have LabVIEW 7.1 or later version and IMAQ Vision 8.2.1 or above installed on your machine"

  I would then, Sabre will exist some drivers specific pacote para as have assim uma compatibilidade between o e o of Vision 2010 in NI LabView 8.6?

  Obrigado,

  Daniel Carvalho

  OLA Daniel,

  Ah, you don't activate it, but you need to activate the VDM 2010. And the VDM 8.6 is not compatible with 2010.

  Christian