Ni Vision Development Module
Bertoldo Beyer
The Vision Development Module helps you develop software for machine vision and image processing applications. You can use it with the LabVIEW graphical programming environment, C, C++, and C# for Windows systems and LabVIEW for real-time systems. Choose from hundreds of image processing algorithms including filters, morphologies, pattern matching, and classification. The module includes IP for targeting both processors and FPGAs and features model importers for performing inference using deep learning models developed in TensorFlow.
I working in LV 2010. Everything was working fine. Full vision development was working fine. I had access to all of the edge detect, gap measure VIs, etc. Then in a moment of stupidity I installed 2014 vision development. Now I realize that was only a trial version so I got rid of it. Now though when I open and use LV2010 it don't show all of the vision functions in the pallete. It just shows the basic vision functions (grab, snap, etc..) I can see that that vision folder still exists, I can see that I still have a full version on 2010 vision in the license manager, and it says it in installed and fine. How do I get LV2010 to once again look in the right place? BTW, when I open a VI I had written using the measure vertcal gap function it stops and asks me to find the "NI_Vision_Development_Module VI. Which I cannot find BTW.. Your help is appreciated.
Before I removed the 2014 version, I looked around to make sure I wasn't deleting anything I need. It appeared that everything for 2014 went into it's own folder and it didn't appear to mess up anything in the original vision folder. I understand I may have missed something.
As you have found out, LabVIEW can be very "version-specific". LabVIEW, itself, installs in its own directory (e.g. LabVIEW 2010, LabVIEW 2011). However, some toolboxes (in particular, IMAQ and IMAQdx) install "globally" in their own folder. This means that when you install IMAQdx for 2014, it overwrites IMAQdx for 2010. I don't know if this should be considered a "bug" or a "feature", but it explains your situation, and the necessity for doing the re-install of LabVIEW 2010.
You might be able to get away with "merely" reinstalling the 2010 Vision Toolkit(s). However, you would need to get the current files and folders removed properly, which might be difficult (because there may be hidden "hooks"). If you have a current 2010 license, you should be able to get NI to supply the disks (or a download) ...
Please name all of the Modules and Toolkits you are trying to install. Did you notice that the Error message had the term "FPGA" listed? Have you specified code that supports FPGA (I can't tell you what Modules or Toolkits this requires, as I'm not currently doing FPGA work)?
Firstly I want to open Labview project from Help> Example (Image Processing with Vision Asisstant on FPGA). But, I can't open the example because its say that it requires an add-on toolkit, which is vision development module. For your information I already installed FPGA development and real-time modules. Where my mistake?
The major difference I see between your installation of LabVIEW 2018 (where VDM 2018 doesn't work) and mine (where it does) is that I have only 32-bit LabVIEW installed (I'm running on 64-bit Windows 10). I haven't checked recently, but I recall that not all of the Toolkits and Modules worked with 64-bit LabVIEW.
I hesitate to make that recommendation. Two or three years ago, I would have said "Yes, LabVIEW 64-bit does not play well with others, including 32-bit LabVIEW and Vision", but I understand that there have been definite "improvements" with more recent releases. Also, doing a complete removal of LabVIEW has become a little more difficult (in my humble opinion) with NIPM.
What I might suggest you try first is the following "proof of concept" -- get your hands on a PC (or VM) that does not have LabVIEW installed. Install LabVIEW 2018, 32-bit (only), and install the other Modules/Toolkits/Drivers you need. Be sure to include the Vision Development Module and Vision Acquisition System (Drivers). This will mimic the system I have (running in a VM), which works. If this also works for you, you might consider following the "uninstall/reinstall" pattern.
One other thing to consider -- in my "LabVIEW Installation" experience (which, thus far, is limited to 32-bit LabVIEW), I'm very aware of an "order" requirement, stated most simply as "Install the Oldest Version first". In some really old LabVIEW Versions, such as LabVIEW 7, my mentor told me the order I had to use when installing individual Modules/Toolkits, and "Install Device Drivers last" (and my own Rule of Thumb, "Reboot Often"). If I was going to do a 32/64-bit Dual Install, in the absence of specific recommendations (which may be out there, I just don't know), I would install LabVIEW 32-bit, Tools, Modules, and Drivers, reboot, verify functionality, then install LabVIEW 64-bit.
Finally, if you do decide to go this route, before starting the "uninstall", I would recommend placing a Support call to NI (assuming you are under Support). Their Applications Engineers are pretty sharp, and have helped me out of many holes ...
Your error screenshot doesn't show your full window so I can't see which version of LV you're running. Given what else I've seen, I'm guessing you installed LV 32-bit, the toolkits/modules, and then LV 64-bit.
I don't know why this warning appears after I have installed the correct module. I am trying to open a project developed by a previous employee in LabVIEW 2013. There were numerous other warnings and errors which I was able to correct simply by installing the required modules and packages.
Did you by any chance install the Vision Development Module first? (Before LabVIEW 2015). Even if you installed it second, I would just re-install the Vision Development and triple check that "support for development" (or something along those lines) is checked when you install it.
I installed LabVIEW 2015 before installing NI Vision Development module. I will uninstall and re-install NI Vision Development module and pay close attention to the installation options and will post the results. Thanks for the suggestion.
I have fixed the NI Vision warnings that I was having before. Unfortunately, I performed several package installations before loading the project again so I can't say which fixed the issue. To answer your questions anyways:
Thank you for your suggestions. Im glad the issue was resolved, but it is a bit frustrating that I don't know what the fix was. Basically I found a folder on the company drive that containted several packages. So I installed them all and after that was able to open the project without any warnings. I will now try to build, hopefully that goes smoothly. FYI this is my first experience with LabVIEW, which might help explain my lack of knowledge about the problem and what fixed it.
I am having the same problem and am having no luck with a solution thus far. NI-MAX even recognized the driver as being there but when I go to run a specific VI, requiring the "Vision Development Module support for labview 2015" it gives me this warning. Any other ideas what I'm missing?
If you open an new VI do you have a Vision and Motion palette on your block diagram? If you take a screenshot of that palette we should be able to figure out whether LabVIEW thinks the toolkit is there.
The Vision Development Module (VDM) provides machine vision & image processing functions for LabVIEW, C/C++, Visual Basic, and .NET. In general, VDM functions are to be used for post processing images. Some example functions are: pattern matching, particle analysis, edge detection, thresholding, histograms, and optical character recognition. In addition, VDM includes Vision Assistant, a prototyping and code generation tool similar to VBAI in its menu-driven interface. Vision Assistant is a useful tool for developing and testing a series of image processing steps from which code can then be generated. VDM is supported on Windows and LabVIEW Real-Time. This means you can use VDM on remote targets such as the CVS (Compact Vision System) and the Smart Camera provided you are also using the LabVIEW Real-Time Module.
Furthermore, the Vision Development Module includes a license for NI Vision Acquisition Software (VAS). The NI Vision Acquisition Software is a set of drivers and utilities with functions to acquire, display, and save images from any NI frame grabber, GigE Vision camera, or IEEE 1394 (Firewire) camera. VAS is included in both VDM and VBAI and is a bundle of three drivers:
The Vision Run-Time Engine must be installed and activated on the target PC when deploying an application built using Vision Development Module (VDM). If the programming environment used was LabVIEW, the LabVIEW Run-Time Engine needs to be installed.
Note: As of August 2009, the NI-IMAQdx driver, which is part of the Vision Acquisition Software, can be activated with the Vision Run-Time Engine license, so no additional Vision Acquisition Software license needs to be purchased. If the application was built in a version prior to Vision Development Module 2009, then a license for both the Vision Acquisition Software as well as the Vision Run-Time Engine will be required for the target machine.
If the NI-IMAQ driver is used in the application (for acquisition from NI frame grabbers, as well as general display, file saving and acquisition functions), then you would need to have NI-IMAQ installed on the target machine as well. NI-IMAQ does not require any activation.
1. In the Project Explorer window, right-click Build Specifications and select New Installer.
2. Select Additional Installers from the Category tree of the My Installer Properties window.
3. Place a check mark in the NI Vision Run-Time Engine X.X checkbox as seen in the image below. (Note: The installer will attempt to locate the run-time engine from the same directory where NI Vision Development Module was installed. If you no longer have this distribution you can download the run-time from Vision Development Module Runtime. Search for Vision Run-Time and download the proper version for your application.)
4. Place a check mark in the NI-IMAQdx X.X checkbox, as seen in the image below, if you used any of the NI-IMAQdx VIs in your application.
5. Place a check mark in the NI-IMAQ X.X checkbox, as seen in the image below, if you used any of the NI-IMAQ VIs in your application.
6. Configure your installer as you would normally and click OK. LabVIEW will create your installer including the Vision Run-Time Engine and any other additional installers as a self extracting executable. The Vision Run-Time Engine and other installers, like NI-IMAQ and NI-IMAQdx, will install when the application installer is executed. After installation, you will be prompted to activate the Vision Run-Time Engine and NI-IMAQdx if installed.