11-25-2008 04:11 PM
11-26-2008 01:37 PM
timmkish,
I am very sorry, but I don't have a solution for you yet. There is unfortunately not one document or person that knows all the answers. In fact, our documentation is very poor for the non-VDM functions for file I/O. I'm still not sure why you cant use some of the VDM file I/O calls, since one of OUR engineers said that it is possible. That is another facet of the problem that I am looking into.
I know that this problem has taken a significant amount of time, which I am sory for. For the time being though, I would reccomend just using the trial version of VDM, which is basically the full version without being activated.
Hopefully I will hear more promising results back from R&D by next week.
12-01-2008 01:56 PM
12-03-2008 01:17 PM - edited 12-03-2008 01:20 PM
Good News. You can use the CWIMAQVision ActiveX control without licensing issues as long as you only call functions that do not require a license. Writing files does not require a license so you can ship Visual Basic executables that use the Vision ActiveX control with the Vision dll and if you only write files/display images, you won't need a Vision license on the machine.
Here's the simple example I tested with:
Private Sub Command1_Click()
If you uncomment the CannyEdgeFilter function, you'll get an error about licensing, but if you leave it commented out, it works great.
Hope this helps,
Brad
12-03-2008 03:10 PM
Brad,
Thanks for the help, but if I even add a CWIMAQVision Object to my form (without even making a function call from the CWIMAQVision Object) upon executing the code, clicking the 'Snap' button, there is an immediate error and the compiler informs me that I have an unlicensed copy of NI Vision.
I check my NI license manager and it says everything is fine.
12-03-2008 03:24 PM
12-03-2008 04:37 PM
Hey timmkish,
I'm wondering if we could have some association problems with your drivers. You need to make sure that you have no conflicting older drivers or versions of vision. Also, you need to make sure you have a license for IMAQdx. I know all of these are simple to look at, but you shouldn't be getting this error. I'm still looking into it for you. Thanks as always for your patience.
12-03-2008 04:43 PM
12-03-2008 04:45 PM
You're sure you have the driver licensed correctly? If you remove the Vision ActiveX control from the Form your application can acquire images without problems? Here is a screenshot of my license manager (tried on a clean machine with just Visual Basic and Vision Acquisition Software), and the VB code I used.
Are you trying this on your machine or deploying it to another machine? If you put it on another machine, that machine needs to have IMAQdx licensed correctly.
12-03-2008 04:58 PM