Interfacing Vision Builder with Labview version 7.1

i can't export my design in Vision Builder version 7.0 to Labview version 7.1 using the Create Labview VI under the Tools tab as taught in the demo on this website. please advise. thanks.

Hello,
Most likely, this is due to having a version of Labview that is newer than your Vision Builder / Vision Assistant software. There are updates available for both Vision Builder and Vision Assistant. These updates can be found at:
Vision Assistant 7.0.1 if you previously had Vision Assistant 7.0
Vision Builder for AI 2.0.2 if you previously had Vision Builder AI 2.0
After installing one of the above, everything should work as you saw in the online demonstration.
Hope this helps,
Robert

Similar Messages

When I try to migrate vision builder to labview I get an error message

when I try to migrate vision builder to labview I get an error message "Error at Labview code creation step #6"

Does the error seem to be occurring at the same step in your Vision Builder AI script? See if you can determine if a certain step introduces the error by trying different modifications of your script and/or generating LabVIEW code from a Vision Builder AI example inspection. Also, are you using IMAQ Vision 7.0 for LabVIEW or a previous version of the Vision software?
Best regards,
Dawna P.
Applications Engineer
National Instruments

Interfacing of hardware with labview

can u pls tell me the steps for interfacing a hardware wiht labview........ i mean to say the detailed descrpition....... for ex: interfacing keithley sourcemeter with labview....... pls do give me a detailed steps of interfacing

Start by downloading the LabVIEW driver, which is available in http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=7117
You should also make sure that the VISA driver is installed. It should have been part of your LabVIEW installation.
Or a shortcut location from the Keithley website is here:
http://www.keithley.com/support/data?asset=51950
Message Edited by Ray.R on 04-11-2010 05:42 PM

Problem with Vision Builder and LabView: Error -1074395995, File not found

I have created an inspection with Vision Builder AI 2009 SP1. In it I load some pictures from the HDD and run some checks over it. It works fine. Then I have migrated it to LabView 2010, I get a message that the migration is successfull, but when I run the VI on LabView I get a fail status. I have been checking my program and I have found and error when I try to load the picture from file: Error -1074395995 occurred at IMAQ ReadImageAndVisionInfo
Possible reason(s): IMAQ Vision: File not found.
But I am not sure which file it refers to. At first I thought it was the picture I wanted to load, but I have checked the path and it is correct, so maybe it refers to another thing. What puzzles me most is that it works perfectly on Vision Builder and I have changed nothing in LabView, maybe it is a problem with the migration. Any clues?

Here's a screenshot of what I'm talking about. Put a break point here and see what the path is and compare that with what Vision Builder AI is using (described where to find this in the previous post). You could find where this global is used to make debugging easier.
Hope this helps,
Brad
Attachments:
Generated Code.png ‏43 KB

Building classes with labview (version 8+).

Just wondering if it is possible to build classes with labview and how this applies, starting a new project and want to design the software to be easily maintained. I would like to be able to Inherit vi modules and possibly override portions of the inherited vi. Also if anyone has any experience trying to impliment OOD features and can provide any feedback. In addition are there any suggested standards to adhere to for labview development that might increase readability. thanks Paul.

svt4cobra6 wrote:
Just wondering if it is possible to build classes with labview and how this applies, starting a new project and want to design the software to be easily maintained. I would like to be able to Inherit vi modules and possibly override portions of the inherited vi. Also if anyone has any experience trying to impliment OOD features and can provide any feedback. In addition are there any suggested standards to adhere to for labview development that might increase readability. thanks Paul.
Come on now! Do you you really think you can get a good answer with such a broad question?
If you are uisng LabVIEW 8.2 or better then LVOOP is what you want to look into.
LAVA has a forum devoted to OOP in LV and can be found here. If you are not uisng LVOOP then that site is your best resource for help.
At this link you will find a document that talks about what went into LVOOP.
If you are an old time OOP type you will probably be disapointed that the is no "call by refence" (yet) and you will have to "roll-your-own" if you want a design that uses Active Objects.
I believe there is a style guide built into the LV help.
Did I cover the main points?
Ben
BTW "LVOOP" = LabVIEW Object Oriented Programming and is often pronounced like it is a french word "la-voop".
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Vision Builder Crashes Labview

I have an application where I need to acquire and inspect many high resolution images 3Mp at high throughput.
I'm using:
LabVIEW 8.5.1
NI-Imaq 4.1
Imaqdx 3.2
Vision Builder AI 3.6
ISG 3Mp Camera through Startech 1394a PCI card
In order to meet the cycle rate, I'm trying to multi-thread the application by having one thread that acquires images and enqueues them into another thread that saves them to the hard drive then runs the VBAI inspection. The VBAI inspection then uses the "simulate acquisition" step inorder to load the image from the hard drive and make the appropriate measurements. I've run the application and monitored the processor usage, and the processor seems to stay within 0-80%. However, my application will crash intermittantly.
I've been able to repeat the behavior pretty reliably if I activate/toggle a ring control on my front panel while the cycle is running, and I can't do so if the VBAI thread is not running.
I understand that this is could be a difficult problem to help debug remotely. I'm wondering if there is anyone with similar experience, or some better way for me to creat a high throughput machine vision app with VBAI.
Thanks,
Ryan

Dear Ryan,
You are right, this is difficult to debug remotely, but I can make a suggestion or two. Perhaps you've taken care of these, perhaps not...
One potential downfall with this setup is running into a race condition. If you don't establish data dependency, and make sure that you save and close a particular image before trying to open back up again with VBAI, you could cause the behavior described. Race conditions would be even more of a concern if you were using a certain number of files as an image buffer, and then recycling through them.
What in this ring control? What does the ring control do?
Have you tried generating LabVIEW code from your VBAI inspection, and then encapsulating the VBAI code in a subVI, and just passing your images into that instead of saving them to disk? I would suggest doing this to see if you still experienced the crashes when you are only working in LabVIEW, and without saving and opening images from disk.
Let me know how things go; I hope the above suggestions provide some help.
Best Regards,
~Nate

Migracion de Vision Builder a Labview

Buen dia
stoy realizando una inspeccion de una pieza en Vision Builder donde genero steps de Calipter para verificar dimensiones horizontales y verticales.., estos arrojan el resultado en pixeles..
Al migrarlo a LabView, se genera todo normal... pero en ningun lado aparece el dato de los pixeles...
Quisiera saber si estoy omitiendo algun paso..?' o hay que programar algo en labview??..
Muchas gracias,...
Envio un rar con la migracion a LabView 2010 sp1
Attachments:
Inspect Main.vi ‏98 KB

Hola Morenita, gracias por contactarnos,
El problema podría estar en que al momento de generar el código para LabVIEW, Vision Builder pide varios parámetros, como indicadores que va incluir el código. Probablemente te esté faltando activar algún indicador que muestre la información de píxeles que deseas. Si gustas enviarme tu aplicación de Vision Builder y lo revisamos. Te anexo también un tutorial en 3 partes para que tengas documentación a la mano.
Customizing the Inspection Interface in NI Vision Builder for Automated Inspection:
http://www.ni.com/white-paper/6714/en
Saludos!
NavasMonk
National Instruments, México
ELP Support Engineer
www.ni.com/soporte

Migrating inspection from Vision Builder to Labview

When I migrate my inspection, which includes an Acquire Image function, from Vision Builder for AI 2.0 to Labview 7.0, it asks me to find a bunch of *.vi and *.ctl files such as "IMAQ Resource Manager.vi", "IMAQ Configure Buffer.vi", "IVB Image Providers Manager Function.ctl" etc. I cannot locate these files so I just hit "Cancel" when these messages pop up, and the migration is said to be successful but the resulting vi can not be run in Labview. What's wrong? I do have IMAQ Vision 7.0.1.

All of the Vision Builder AI generated VIs are typically installed in the following directory: C:\Program Files\National Instruments\Vision Builder AI 2.0\LV\SubVIs. Within that folder you should have approximately 25 VI libraries (such as Common.llb, IVB Match Pattern.llb, etc.) and several other VIs (i.e. Inspect Result.vi and Inspect Setup.vi, etc.).
Did you install Vision Builder AI to a different directory than the default location? Have you tried repairing/reinstalling Vision Builder AI?
Best regards,
Dawna P.
Applications Engineer
National Instruments

From vision builder to labview

Would anyone possibly know how to convert a tool developed in vision builder for automated inspection into labview so that when we connect a thermal camera and have a live image, the tool from vision builder analyses the image on labview?
Thanks for the help

It is very weird, this is what I get as a reply when I try to convert from VB AI to LabView
And here is also a picture of my NI License Manager, from where I have activated "successfully" VAS and VDM...
I don't understand why it won't work...
Attachments:
conversion impossible.png ‏259 KB
NI license manager.png ‏107 KB

Interfacing Beckhoff EK1100 with LabVIEW without using any other hardware

Hello All,
I'm new to Beckhoff & I have EK1100 with EL2809 & EL3054. I want to interface with EK1100 with LabVIEW with PXI or cRio or any other hardware.
Is there anyone who can explain how?
I'm using the following sofwares & drivers.
LabVIEW2012
EtherCAT Acquisition Driver
EtherCAT Acquisition Library for LabVIEW
TwinCAT ADS Library v3.0.3
Please suggest at the earliest.
Regards'
Love Diwan |+91-9810013576

cross post
Jesse Dennis
Design Engineer
Erdos Miller

Interfacing dolphin 6500 with Labview and windows 7

Hi,
someone has created and installed a application of labview in device dolphin 6500.
I need to develop a aplication for capture data in honywell dolphin 6500 with labview but I have trouble to connect the device with my windows 7 for send the app.
Any thoughts or assistance would be greatly appreciated.

Hi,
http://www.ni.com/white-paper/4577/en/
Please refer this link. Also please send screenshots of any error messages if you get.

Report builder with Oracle Version

Hey every one
I would like to know that which oracle version comes with Report Builder?
..Enterprise...Developer or standard???
Thank you

Reports comes with the Oracle PL/SQL compiler, no database. You can check versions by going to help->About Reports Builder. There is no Enterprise, Developer or Standard version.

Interfacing Microchip ICD3 With Labview.

I need to select/browse the hex file from labview and need to dump on PIC IC. Is there any way to acheive this using labview? What are the different hardware we need for that. I do have a ICD installed in my PC.
What I need is for browsing and dumping the code I should use LV UI.
Kudos are always welcome if you got solution to some extent.
I need my difficulties because they are necessary to enjoy my success.
--Ranjeet

Ralok wrote:
Example using the ICD3CMD.exe with system exec.vi call:
Simply call the ICD3CMD.exe with /? from cmd for full list of programing options.
edit: As for hardware you would need an ICD3 or PICkit3.
Thanks for the reply. I have ICD3. Do I need to set a path? What is the input to the path input?
Kudos are always welcome if you got solution to some extent.
I need my difficulties because they are necessary to enjoy my success.
--Ranjeet

Has anyone interfaced a HP3585a with LabView 5.x Vi succesfully?

I have a HP3585a Vi made up but am having timing problems.If someone is interested I can E-mail the Vi to You.Using GPIB bus.Thanks Mike!

Try to searh in user manual for details regarding any GPIB "not usual" settings.

How to build demo versions with Labview ?

Hello,
is it possible to design Labview applications in a kind,
that it is possible to generate "demo versions" of it ? Demo version in the means of feature-limited crippled versions of a full instrumentation software, where SOME hardware access is denied, but you can load and view and analyse data.
Of course it might be useful to compile this demo version with the Labview Application Builder,
What might be the business modell for demo versions:
A hardware manufacturer creates a Labview application which controls the manufacturer's components, and allows instrumentation and data recording. The application is not free but sold for extra money.
As pre-sales benifit, the manufacturer would like to send the (compiled) Labview application to future customers.
Now the problem is, that the customer has not (all) the external devices or PCI/USB devices,
on the other hand the hardware manufacturer does not want to give the "full application" as gilft to the customers.
Now with traditional software development with C++, Java, C#,
either a demo version is gained from the full version by replacing some module with hardware access by modules wth "empty" function body or with function body which return constant values instead of accessing the hardware.
In the world of process industry, usual process control systems may supply "alternative" values if the original device is not available.
What kind of software structure must I build with Labview, to do the same ?
Now the problem with Labview applications is
Labview applications depend on drivers. Drivers depend on hardware.
So if the FULL commercial version of the Labview program accesses a DAQmx driver, GPIB driver or any other hardware driver by a VI,
and often this means that a special manufacturer VI is used in the Labview program which does the actual hardware access,
how to modify the software to make a demo version
a) so that IF the customer buys the hardware and gets the hardware driver, he still does not have the full version
b) so if the customer neither has the hardware nor the driver, he still can run the Labview software and load an view data, push buttons, can execute menu items even can manipulate data ect, can use the manufacturer's VI
Unfortunately, it is no solution just to delete "some" of the VIs with hardware access from the distribution of the demo version, as this just causes error messages during the loading of the (compiled) Labview demo application.
Message Edited by hemmerling on 01-11-2007 12:35 AM
Message Edited by hemmerling on 01-11-2007 12:37 AM

Thanks alot.
Conditional Disable and Diagram Disable Structures
http://zone.ni.com/reference/en-XX/help/371361B-01/lvconcepts/cond_diagram_disable/
are indeed at least a part of what I wanted.
Anyhow, as such "suspended" VIs are often the *source* of signals,
so there must be an addtional method how to provide "alternative" signals for the demo version,
which does not make the administration / further development the full version too complicated...
For example: The VI for an external signal generator device is disabled, but alternatively it would be nice if the users of the demo version can get a fixed sinus signal instead...
How to do that with Labview and the "Conditional Disable and Diagram Disable Struktures",
and can I test this all even without Labview Application Builder, in the full development system ( so that I don´t need the compiler for frequent checking ) ?
Btw, with what version was this "Conditional Disable and Diagramm Disable" feature introduced ? Is ist already available with Labview 7.0, /.1 ?
Sincerely
Rolf

Interfacing Vision Builder with Labview version 7.1

Similar Messages

Maybe you are looking for