Vision Builder 2013, windows 8 Compatability?

Trying to run VBAI2013 on windows 8 results in just the splash screen visible. The program never launches, and just sits in the task manager as a process consuming RAM but no CPU.
Tried restarting, compatability modes for Win7 or XP, turned off firewall, UAC, and smart screen, run as admin, etc...... no avail.

VBAI is definitely tested on Windows 8 and does work fine (normally!). This is a problem I have not heard of before, and none of the options you listed as trying should be necessary to run it.
Could you try creating a dump file from task manager for the VBAI process and posting it? We might be able to deduce from that where it is hung and maybe give you a suggestion to try. Also, it might be possible that some dependencies are corrupt on your system. Do you have other NI software pieces installed besides VBAI? This might give us some insight into trying to reproduce the setup. Also, have you tried re-running the installer and selecting a "repair"?
Eric

Similar Messages

Compatibility of developed Vision library with NI Vision Builder AI

We developed a specific Vision library using NI LabVIEW and Vision Toolkit.
My requirement is to identify the compatiblity of this library with NI Vision Builder AI.Can we use the existing VI's with Vision builder?
Please provide me your comments asap.
Regards:
Vaibhav Kanchan
Sr. Engineer
NI Certified LabVIEW Developer(CLD)
NI Certified TestStand Developer(CTD}

There are multiple ways to add functionality to Vision Builder AI using a set of VIs you wrote:
1) Vision Builder AI can run a VI you write that use your VIs using the Run LabVIEW VI step.
2) You can also develop a custom step (that include the configuration page) for a better user experience, using the VBAI SDK, and use your VIs inside.
With these 2 solutions, you will need to use a specific version of LabVIEW to integrate your library, as Vision Builder AI is a LabVIEW application, and VBAI will execute the code from the Run LabVIEW step, or custom step using the LabVIEW runtine engine that it was built with. The version of LabVIEW depends on the version of VBAI. For example, for VBAI 2011SP1, you need to use LabVIEW 2010.
3) You can automate/drive Vision Builder AI from LabVIEW on Windows. (Open an inspection, run once, run continuously, etc, and get the resulting results and image that you can further process using your library. You can use the API on Windows with any version of LabVIEW.
For example, the VBAI 2011 API supports LabVIEW 8.5 through 2011.
You will run your developped application on Windows only, but it will be able to control Vision Builder AI running on remote targets.
If you're running Vision Builder AI on Windows, I see no compatibility issues with any of the above solution, except for using the correct version of LabVIEW in the first 2 solutions I mentioned. Using 1) and 2), you will also be able to develop code that can run on targets that Vision Builder AI supports, like smart cameras, and embedded vision systems.
If you plan to support remote targets, like smart cameras or Embedded Vision Systems, there are things to consider for your library to be compatible:
These targets run different operating systems: some run Pharlap, some run VxWorks, all run LabVIEW real-time on these OSes. If you used LabVIEW and Vision Development module to build you library based on VDM, the only thing to consider is to make sure to use the same version of LabVIEW and Vision Development Module installed on the target. Let me explain:
When you configure one of these remote targets from Vision Builder AI running on the Windows host machine, we install an image that contains a specific version of LabVIEW Real-time and Vision Development Module (For example, in the case of VBAI 2011 SP1, the remote target image has LabVIEW Real-Time 2010 and Vision Development Module 2011). Those should be the versions you need to use to create your VI to run with the Run LabVIEW step or custom step). We ran into some compatibility issues when customers update their Windows machine with a newer version of Vision Development Module, and write a VI or custom step they want to run in VBAI, that uses a new function that is not supported with the DLLs installed on the target.
If your Vision Library uses some other DLLs (code you may have written in text based language or third party DLL), you will have to recompile the DLL for the operating system of the target (Pharlap or VXWorks, depending on the target) for the code to work on the remote target.
Hope this helps and is not too confusing.
Best regards,
-Christophe

Labview 7.0 is compatable with Labview Imaq6.1 , vision builder 6.0 and Imaq run time engine 6.0.

Sir,
My system is PXI 8174 and i an using NI 1411 card for my application. I want to know the compatability of the softwares. Whether Labview 7 is compatable with Labview Imaq 6.1 , vision builder 6.0 and Imaq run time engine 6.0.

Hi,
Assuming you meant IMAQ Vision 6.1 instead of IMAC 6.1, this software was intended to run on LabVIEW 5.1, 6.0, and 6.1. I have heard of it being used with LabVIEW 7 on occasion, so it may be possible to make it work, but this has not been tested and is not officially supported. Vision Builder 6.0 should run; however, it was developed long before LabVIEW 7.x and will not generated code for LabVIEW 7.0 and later. The Vision RTE version should correspond to the version of Vision you are using. For instance, if the program was developed with Vision 6.1, the computer should have the Vision 6.1 RTE installed. With this being said, if you plan to use LabVIEW 7, I recommend updating your other software.
Regards,
Ryan M.
Applications Engineer

Setup Blocked : Windows Program Compatibility Mode

I'm trying to install "Modeling SDK for Microsoft Visual Studio 2013" on Windows 10 Tech Preview Build 10049:
https://www.microsoft.com/en-us/download/details.aspx?id=40754
But always get:
"Setup Blocked"
Windows Program Compatibility mode is on. Turn it off and then try Setup again.
Compatibility tab on the setup VS_VmSdk.exe shows compatibility mode is off. No variation of settings on that tab have any effect.
Is there any way to bypass the compatiblity check on Windows 10 Tech Preview?
Thanks,
Mike

Rick, Have you had any success with this? I'm also trying to run the tfs_VssUpgrade.exe tool on my Windows 8.1 machine and getting the same exception. Greatly appreciate any insight if you were able to get past this issue! Thanks, Steve
Same issue here.
This MS connect thread
is interesting however.
Posted by Microsoft on 9/19/2013 at 2:54 PM
Hello Alxandr,
Thank you for taking the time to submit this issue to Connect. This is a known issue with Windows 8.1 RTM and it will be addressed in a future update of Windows 8.1. In the meantime, you can typically rename the EXE to get it to work correctly.

Windows 8.1 and VS2012 SDK get error "Windows Program Compatibility mode is on. Turn it off and then try Setup again."

When trying to install VS2012 SDK on Windows 8.1 get the error "Windows Program Compatibility mode is on. Turn it off and then try Setup again."
See my blog C# Bits | Twitter @sjnaughton Always seeking an elegant solution.

Rick, Have you had any success with this? I'm also trying to run the tfs_VssUpgrade.exe tool on my Windows 8.1 machine and getting the same exception. Greatly appreciate any insight if you were able to get past this issue! Thanks, Steve
Same issue here.
This MS connect thread
is interesting however.
Posted by Microsoft on 9/19/2013 at 2:54 PM
Hello Alxandr,
Thank you for taking the time to submit this issue to Connect. This is a known issue with Windows 8.1 RTM and it will be addressed in a future update of Windows 8.1. In the meantime, you can typically rename the EXE to get it to work correctly.

Can`t open vision builder 2011

I have some problem about vision builder AI 2011
please help me!!!
Log:
#OSName: Microsoft Windows XP Service Pack 3
#OSVers: 5.1
#OSBuild: 2600
#AppName: Vision Builder
#Version: 10.0.1f3 32-bit
#AppKind: AppLib
#AppModDate: 07/30/2011 12:04 GMT
#LabVIEW Base Address: 0x30000000
2012-2-18 20:41:31.630
c:\builds\penguin\labview\components\LVManager\trunk\10.0\source\LVListMenuImpl.cpp(683) : DWarn: bad itemId (0)
$Id: //labview/components/LVManager/trunk/10.0/source/LVListMenuImpl.cpp#2 $
0x3082FC29 - lvrt <unknown> + 0
0x300D4FF5 - lvrt <unknown> + 0
0x300D9553 - lvrt <unknown> + 0
0x300E5E4F - lvrt <unknown> + 0
0x300E957B - lvrt <unknown> + 0
0x300E9F6A - lvrt <unknown> + 0
0x307D8167 - lvrt <unknown> + 0
0x300281DC - lvrt <unknown> + 0
0x30027FD3 - lvrt <unknown> + 0
0x30028102 - lvrt <unknown> + 0
0x30028150 - lvrt <unknown> + 0
0x00401142 - Vision Builder <unknown> + 0
0x8B560C45 - <unknown> <unknown> + 0
2012-2-18 20:41:32.287
c:\builds\penguin\labview\components\LVManager\trunk\10.0\source\LVListMenuImpl.cpp(683) : DWarn: bad itemId (0)
$Id: //labview/components/LVManager/trunk/10.0/source/LVListMenuImpl.cpp#2 $
0x3082FC29 - lvrt <unknown> + 0
0x300D582F - lvrt <unknown> + 0
0x300D9553 - lvrt <unknown> + 0
0x300E5E4F - lvrt <unknown> + 0
0x300E957B - lvrt <unknown> + 0
0x300E9F6A - lvrt <unknown> + 0
0x307D8167 - lvrt <unknown> + 0
0x300281DC - lvrt <unknown> + 0
0x30027FD3 - lvrt <unknown> + 0
0x30028102 - lvrt <unknown> + 0
0x30028150 - lvrt <unknown> + 0
0x00401142 - Vision Builder <unknown> + 0
0x8B560C45 - <unknown> <unknown> + 0
2012-2-18 20:41:32.287
c:\builds\penguin\labview\components\LVManager\trunk\10.0\source\LVListMenuImpl.cpp(683) : DWarn: bad itemId (0)
$Id: //labview/components/LVManager/trunk/10.0/source/LVListMenuImpl.cpp#2 $
0x3082FC29 - lvrt <unknown> + 0
0x300D5858 - lvrt <unknown> + 0
0x300D9553 - lvrt <unknown> + 0
0x300E5E4F - lvrt <unknown> + 0
0x300E957B - lvrt <unknown> + 0
0x300E9F6A - lvrt <unknown> + 0
0x307D8167 - lvrt <unknown> + 0
0x300281DC - lvrt <unknown> + 0
0x30027FD3 - lvrt <unknown> + 0
0x30028102 - lvrt <unknown> + 0
0x30028150 - lvrt <unknown> + 0
0x00401142 - Vision Builder <unknown> + 0
0x8B560C45 - <unknown> <unknown> + 0
2012-2-18 20:41:32.287
c:\builds\penguin\labview\branches\2010\dev\source\editor\InitMenus.cpp(3194) : DAbort: Cannot call MakeDirectoryListMenus with insAfter==-1
0x300D84DD - lvrt <unknown> + 0
0x300D956B - lvrt <unknown> + 0
0x300E5E4F - lvrt <unknown> + 0
0x300E957B - lvrt <unknown> + 0
0x300E9F6A - lvrt <unknown> + 0
0x307D8167 - lvrt <unknown> + 0
0x300281DC - lvrt <unknown> + 0
0x30027FD3 - lvrt <unknown> + 0
0x30028102 - lvrt <unknown> + 0
0x30028150 - lvrt <unknown> + 0
0x00401142 - Vision Builder <unknown> + 0
0x8B560C45 - <unknown> <unknown> + 0
I don`t want to reinstall the program,and who can tell me how to repair this problem!
TKS!

Log:
#OSName: Microsoft Windows XP Service Pack 3
#OSVers: 5.1
#OSBuild: 2600
#AppName: multisim
#Version: 10.0.1f3 32-bit
#AppKind: AppLib
#LabVIEW Base Address: 0x13080000
2012-2-21 20:31:41.333
c:\builds\penguin\labview\components\LVManager\trunk\10.0\source\LVListMenuImpl.cpp(683) : DWarn: bad itemId (0)
$Id: //labview/components/LVManager/trunk/10.0/source/LVListMenuImpl.cpp#2 $
0x138AFC29 - lvrt <unknown> + 0
0x13154FF5 - lvrt <unknown> + 0
0x13159553 - lvrt <unknown> + 0
0x13165E4F - lvrt <unknown> + 0
0x1316957B - lvrt <unknown> + 0
0x13169F6A - lvrt <unknown> + 0
0x13858167 - lvrt <unknown> + 0
0x130A81DC - lvrt <unknown> + 0
0x130A7FD3 - lvrt <unknown> + 0
0x130A8249 - lvrt <unknown> + 0
0x7C80B729 - kernel32 <unknown> + 0
0x00000000 - multisim <unknown> + 0
2012-2-21 20:31:44.912
c:\builds\penguin\labview\components\LVManager\trunk\10.0\source\LVListMenuImpl.cpp(683) : DWarn: bad itemId (0)
$Id: //labview/components/LVManager/trunk/10.0/source/LVListMenuImpl.cpp#2 $
0x138AFC29 - lvrt <unknown> + 0
0x1315582F - lvrt <unknown> + 0
0x13159553 - lvrt <unknown> + 0
0x13165E4F - lvrt <unknown> + 0
0x1316957B - lvrt <unknown> + 0
0x13169F6A - lvrt <unknown> + 0
0x13858167 - lvrt <unknown> + 0
0x130A81DC - lvrt <unknown> + 0
0x130A7FD3 - lvrt <unknown> + 0
0x130A8249 - lvrt <unknown> + 0
0x7C80B729 - kernel32 <unknown> + 0
0x00000000 - multisim <unknown> + 0
2012-2-21 20:31:44.912
c:\builds\penguin\labview\components\LVManager\trunk\10.0\source\LVListMenuImpl.cpp(683) : DWarn: bad itemId (0)
$Id: //labview/components/LVManager/trunk/10.0/source/LVListMenuImpl.cpp#2 $
0x138AFC29 - lvrt <unknown> + 0
0x13155858 - lvrt <unknown> + 0
0x13159553 - lvrt <unknown> + 0
0x13165E4F - lvrt <unknown> + 0
0x1316957B - lvrt <unknown> + 0
0x13169F6A - lvrt <unknown> + 0
0x13858167 - lvrt <unknown> + 0
0x130A81DC - lvrt <unknown> + 0
0x130A7FD3 - lvrt <unknown> + 0
0x130A8249 - lvrt <unknown> + 0
0x7C80B729 - kernel32 <unknown> + 0
0x00000000 - multisim <unknown> + 0
2012-2-21 20:31:44.912
c:\builds\penguin\labview\components\LVManager\trunk\10.0\source\LVListMenuImpl.cpp(683) : DWarn: bad itemId (0)
$Id: //labview/components/LVManager/trunk/10.0/source/LVListMenuImpl.cpp#2 $
0x138AFC29 - lvrt <unknown> + 0
0x13154B40 - lvrt <unknown> + 0
0x1315585F - lvrt <unknown> + 0
0x13159553 - lvrt <unknown> + 0
0x13165E4F - lvrt <unknown> + 0
0x1316957B - lvrt <unknown> + 0
0x13169F6A - lvrt <unknown> + 0
0x13858167 - lvrt <unknown> + 0
0x130A81DC - lvrt <unknown> + 0
0x130A7FD3 - lvrt <unknown> + 0
0x130A8249 - lvrt <unknown> + 0
0x7C80B729 - kernel32 <unknown> + 0
0x00000000 - multisim <unknown> + 0
2012-2-21 20:31:44.912
c:\builds\penguin\labview\components\LVManager\trunk\10.0\source\LVListMenuImpl.cpp(683) : DWarn: bad itemId (0)
$Id: //labview/components/LVManager/trunk/10.0/source/LVListMenuImpl.cpp#2 $
0x138AFC29 - lvrt <unknown> + 0
0x13154B69 - lvrt <unknown> + 0
0x1315585F - lvrt <unknown> + 0
0x13159553 - lvrt <unknown> + 0
0x13165E4F - lvrt <unknown> + 0
0x1316957B - lvrt <unknown> + 0
0x13169F6A - lvrt <unknown> + 0
0x13858167 - lvrt <unknown> + 0
0x130A81DC - lvrt <unknown> + 0
0x130A7FD3 - lvrt <unknown> + 0
0x130A8249 - lvrt <unknown> + 0
0x7C80B729 - kernel32 <unknown> + 0
0x00000000 - multisim <unknown> + 0
2012-2-21 20:31:44.912
c:\builds\penguin\labview\components\LVManager\trunk\10.0\source\LVListMenuImpl.cpp(683) : DWarn: bad itemId (0)
$Id: //labview/components/LVManager/trunk/10.0/source/LVListMenuImpl.cpp#2 $
0x138AFC29 - lvrt <unknown> + 0
0x13154B40 - lvrt <unknown> + 0
0x13156B9A - lvrt <unknown> + 0
0x1315956B - lvrt <unknown> + 0
0x13165E4F - lvrt <unknown> + 0
0x1316957B - lvrt <unknown> + 0
0x13169F6A - lvrt <unknown> + 0
0x13858167 - lvrt <unknown> + 0
0x130A81DC - lvrt <unknown> + 0
0x130A7FD3 - lvrt <unknown> + 0
0x130A8249 - lvrt <unknown> + 0
0x7C80B729 - kernel32 <unknown> + 0
0x00000000 - multisim <unknown> + 0
2012-2-21 20:31:44.912
c:\builds\penguin\labview\components\LVManager\trunk\10.0\source\LVListMenuImpl.cpp(683) : DWarn: bad itemId (0)
$Id: //labview/components/LVManager/trunk/10.0/source/LVListMenuImpl.cpp#2 $
0x138AFC29 - lvrt <unknown> + 0
0x13154B69 - lvrt <unknown> + 0
0x13156B9A - lvrt <unknown> + 0
0x1315956B - lvrt <unknown> + 0
0x13165E4F - lvrt <unknown> + 0
0x1316957B - lvrt <unknown> + 0
0x13169F6A - lvrt <unknown> + 0
0x13858167 - lvrt <unknown> + 0
0x130A81DC - lvrt <unknown> + 0
0x130A7FD3 - lvrt <unknown> + 0
0x130A8249 - lvrt <unknown> + 0
0x7C80B729 - kernel32 <unknown> + 0
0x00000000 - multisim <unknown> + 0
2012-2-21 20:31:44.912
c:\builds\penguin\labview\branches\2010\dev\source\editor\InitMenus.cpp(3194) : DAbort: Cannot call MakeDirectoryListMenus with insAfter==-1
0x131584DD - lvrt <unknown> + 0
0x1315956B - lvrt <unknown> + 0
0x13165E4F - lvrt <unknown> + 0
0x1316957B - lvrt <unknown> + 0
0x13169F6A - lvrt <unknown> + 0
0x13858167 - lvrt <unknown> + 0
0x130A81DC - lvrt <unknown> + 0
0x130A7FD3 - lvrt <unknown> + 0
0x130A8249 - lvrt <unknown> + 0
0x7C80B729 - kernel32 <unknown> + 0
0x00000000 - multisim <unknown> + 0

Vision builder

Hi there !
I'm new in the field of machine vision and I need your help in my project,I want to build an application that inspects the sealed terminals of automative wires like in the image attaches below, calibration and edge detection and comparing the images in the real time to a standard image ,
I want to know if that is possible ,and if it is how can I do so ?
THANK YOU !
Solved!
Go to Solution.
Attachments:
aaaa.JPG ‏19 KB

Hi layal,
You are certainly on the right track with using the Vision Builder for Automated Inspection (VBAI). For an extensive outline of all the functions available to you, take a look at the VBAI manual here. First, you would typically want to define a reference coordinate system unless you can guarantee that the part will be located in the same position and orientation in the images. This is discussed on page 2-7 of the manual. Then, you could certainly compare the image, or certain portions in a specified region of interest (ROI) of the image to a template and detect the differences, check for gaps and part widths, locate edges relative to the coordinate system, etc. All the features are outlined in the manual in the context of some examples. I highly suggest that you take a look through the manual and also consider evaluating the VBAI software for 30 days if you do not have it already. You can access the download for the evaluation from the 1st link I posted. If you have more specific questions on the inspection, or how to carry it out, please provide more details concerning the pass/fail conditions for your part.
Also, please bear in mind that if you run VBAI on a regular PC running an OS such as windows, the performance will not truly be real-time. To achieve deterministic performance, you would have to deploy this inspection to a real-time target such as the NI EVS, Smart Camera or a PC running LabVIEW Real-Time as the OS. Hope this helps!

Run-time License for Vision builder

HI
I have created a VBAI file for my inspection in, but now I want to transfer the inspection LabVIEW and build an exe to run the application.
Now for running that application do I require a NI Vision Builder for Automated Inspection Run-Time License or a NI Vision Development Module Run-Time License.
Thanks,
Ninad Regundwar
Junior Engineer | ARAV Technologies | www.aravtech.com

Instead of migrating to LabVIEW, you might want to consider automating Vision Builder from LabVIEW and running your inspection by using the VBAI API.
Check out the examples located here: C:\Program Files (x86)\National Instruments\Vision Builder AI 2013\API Examples\LabVIEW Examples.
The VBAI API allows to start a VBAI engine, open and run an inspection and retrieve images and results for each step.
When using this method, if you're running the LabVIEW program on the same machine VBAI is installed, you do not need to purchase the VBAI runtime, neither the Vision Development Module Runtime (unless you wish to process further the image returned by VBAI.
If you need to deploy that LabVIEW application on a different machine, then you'll need to purchase a VBAI Runtime license.
If you choose instead to migrate the inspection to LabVIEW, then you will need to purchase a full license of Vision Development module for your development machine (the code generated uses Vision Development Module VIs).
If you choose to build the resulting code into a LabVIEW application and deploy it on a different machine, you will need a Vision Development Module Runtime License for the deployment machine (but not a VBAI license).
Migrating the code to LabVIEW is recommended only in cases where you need to modify the code generated by VBAI. The code generated is indeed a lot more complex than using the VBAI API that I described in the first option.
Hope this helps.
Best regards,
Christophe

How to use the examples in IMAQ Vision Builder?

I tried many times to use the examples brought in IMAQ Vision Builder(or LabView 6i ?) or download the similar examples from website of NI in order to learn some skills(I am really new with it!). But Whenever I click the example I want to run and a new dialog window always opened and ask me to find a VI named ???(??? is like for emample: IMAQ Windraw) and I always failed to find this VI!!! Where are this VI or How to use those emamples??? Thank you advanced!!!
Swedlin
[email protected]

Hello Swedlin,
IMAQ WindDraw is a VI that is included in the IMAQ Vision toolkit (see http://sine.ni.com/apps/we/nioc.vp?lang=US&pc=mn&cid=1305 for ordering information).
If you are tring to run examples that include IMAQ WindDraw (or any other functions that are in IMAQ Vision), a dialog message will prompt you locate the VI manually (because the initial search failed).
- Installing IMAQ Vision for LabVIEW will remove the message, and the examples will run.

Create parameters sheet in Vision Builder

I'm using Vision Builder AI (Trial), and I found it very interesting.
But, while you can configure complex vision inspection, it seems you can't
set-up one or more parameters sheets to for the user to change some treshold
or some min/max limit.
I saw this example: http://zone.ni.com/devzone/cda/epd/p/id/1705
but it uses Labview to create the form:
1 - I don't want to pay for the labview license only for some parameters settings
2 - The window is continuosly flickering during the execution,so it is very difficult to resize, move,oeven change someting in it!
So,is there any way to set some parameters sheet to let the user easly change inspection tresholds during the execution?
Thanks,
Simone.
Simone

Hey Simone,
Yes, your explanation does clear things up. I think you can achieve what you are looking for using User Input steps in VBAI 3.0 and you could do this by creating an overlay on a black image. The interface would not be very nice and clean though. The only way to do it without the awkward interface is that I recommend purchasing LabVIEW.
If there are only a few parameters you would like to be able to change, then doing it in VBAI 3.0 would be really simple and very clean. Now to have an entire sheet of parameters would be a little overwhelming. Are you familiar with “User Input”? There are ways to save the data acquired but no way to open the data once it has been saved inside an inspection. I would recommend checking out the User Input step, but remember that without LabVIEW you will not be able to open previously saved settings from a file.
This most recent release of VBAI was huge (we added the state diagram functionality) and we are always looking for ways to improve the software. I really like your suggestion and would love for you to create a product suggestion.
Kind regards,
Jordan
Jordan Randall
National Instruments Italy

Iphone and windows 8 compatibility?

When is apple going to fix the iphone and windows 8 compatibility? All I get is the "waiting for changes to be applied" message. I can't sync my phone.

I have no issues with Win 8 working fine with the latest (win 8 compatible )
iTunes

Itunes and windows 8 compatability Hi just bought a new toshiba laptop installed itunes it worked at first now wont play music or movies. ran troubleshooter said its a compatabilty problem suggested turning off itunes compatability or selecting windows 7

itunes and windows 8 compatability
Hi
just bought a new toshiba laptop installed itunes it worked at first now wont play music or movies.
ran troubleshooter said its a compatabilty problem suggested turning off itunes compatability or selecting windows service pack 3 tried both no help
please assist
adam

itunes and windows 8 compatability
Hi
just bought a new toshiba laptop installed itunes it worked at first now wont play music or movies.
ran troubleshooter said its a compatabilty problem suggested turning off itunes compatability or selecting windows service pack 3 tried both no help
please assist
adam

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

How can I see the current script file name in Vision Builder

I would like to not have to remember which script file I have open. Is that displayed somewhere?

Brian,
I have been looking over Vision Builder 6.1, and from what I can tell, the name of the file that you are working on is not displayed on the screen, and there does not appear to be a way to get it to display there.
This seems like a very worthwhile feature to add, and I definitely agree that it would be useful. You may want to consider filing a Product Suggestion by using the Product Suggestion Center (PSC) that is linked below:
Product Suggestion Center
The PSC links directly into our R&D group's suggestion database, and any suggestions entered would be reviewed by the R&D team.
Regards,
Jed R.
Applications Engineer
National Instruments

Windows 8 Compatibility issue -

I just ran the MS Windows 8 compatibility test on my Windows 7 system... a number of programs were flagged, including iTunes.. however, the action to be taken seems vague: a yellow caution symbol was displayed with the words, "remove authorized PCs"
What does that mean? Do I need to deauthorize my PC before doing the upgrade? Do I need to uninstall iTunes? (I am running v.11) And then reinstall it after upgrading to Windows 8?

Ok, no replies.. so here is what I found out....
It seems that you can have up to 5 computers authorized to use iTunes. If one of the computers that is being upgraded to Windows 8 is one of those 5, you may need to deauthorize iTunes before the install. Why? Because apparently the new install treats the system as a new system, so in order to keep your authorized systems under 5, it may be necessary to deauthorize before the install, then reauthorize again after the install.
Of course, if this is the only computer authorized, then no biggie.. you will end up with two authorized systems and everything should still hum along. The only concern is if you already have 5 computers authorized, then you need to use this process to ensure that iTunes will still work after the install.
Odd that iTunes would be so picky... Adobe is infamous about software activations - insisting on the product being deactivated before uninstalling and reinstalling... but no concern here about upgrading to Windows 8
Hope that helps some others that had a question about this item.
Oh, and btw.. make sure your notebook manufacturer has drivers for Windows 8 - Microsoft had stated that the upgrade from Windows 7 to 8 would be smooth and hiccup free.. but no mention of drivers. Seems there could be issues with drivers. I have a relatively new ASUS G53SW, and apparently ASUS does not have any drivers for Windows 8!

Vision Builder 2013, windows 8 Compatability?

Similar Messages

Maybe you are looking for