Vision Assistant fails to generate LabVIEW code

[RichardM]

Hi. I am having trouble creating a LabVIEW VI from Vision Assistant. When I choose to "Create LabVIEW VI" the program works almost as it should but generates a blank VI called MyOutput.VI.

I have noted that when Vision Assistant asks for you to choose a file path (step 2) it accepts only a file name of my choice, and not a path (the 'select current dir' option is not there.
I am using LabVIEW 8.0, NI-IMAQ 3.5.2, NI-IMAQ for 1394,  NI-Vision: Image processing and machine vision 8.0.0.7845 and Image Services Library 8.0.0.3393.

I have tried uninstalling everything and reinstalling, including installing LabVIEW 8.0.1. I also tried various permutations of order of installing the software. None of this worked. (I did the uninstall from the control panel add/remove programs).

LabVIEW 8.0 works fine on this machine, and Vision Assistant works fine by itself except for this problem. All the vision functions seem to appear under Vision and Motion in the LabVIEW palette.

Thanks,
Richard

Message Edited by RichardM on 09-04-2006 03:18 PM

[Christopher W]

I've never seen a blank VI called MyOutput.vi when creating LabVIEW code from a script.  Does this happen with all of your scripts or just one specific script?

When the Vision Assitant asks for a path it requires a file name and a path so that it knows what to name the VI.  If you could just select current directory, it wouldn't know what to save the VI as.

With LabVIEW 8.0 and 8.2, the menu has changed from previous versions.  All of the Vision functions are under Vision and Motion.  This is the default menu structure.  You can customize the palette if you want, but this is how it will appear by default.

Christopher W.

[RichardM]

Thanks for your reply.
I get the MyOutput.vi for any script. I also checked in MAX and in Vision Assistant whether I could acquire images over IEEE1394 via my CVS and it worked fine.

I got advice to check the VI server settings (enable FTP and ensure access via *), but this did not help.

A previous setup of Vision Assistant on another machine includes a button marked 'Use Current Dir' (or similar) when going through the process of generating the script. I am not sure if it is a version issue or a problem that I don't see it with the installation I am having trouble with. (The machine I was using underwent a possible HDD failure, so I can intermittently access it).

I included the part about the Vision and Motion palette as these functions did install correctly (interestingly the previous install of Vision Assistant on the other machine generated scripts without problem, and when one went into subVI's I could access many low level functions that for some reason did not appear in the Vision and Motion palette, but that is a separate discussion).

Regards,
Richard

[Christopher W]

I'm not sure why you get a MyOutput.vi when you generate code with all of your scripts.  That is strange and I haven't heard of anything like that before.  If you post a script I could see if it generates the same VI for me.

I checked Vision Assistant 7.1 and saw the same thing as with 8.0.  I don't know why you want to be able to select the current directory since you have to give the VI a name. I don't think that is a bug or problem.

If you think your Vision Functions didn't get installed correctly you could try repairing the driver.  Which functions don't appear on the palette right now?

Christopher W.

[RichardM]

Christopher thanks for your help... Any script will generate this output. For example, if you open an example image (I used a bracket) and then add one or two funcitons to it, then try generate the LabVIEW code, it gives the blank VI called MyOutput.vi My comments regarding 'use current dir' are informational only to try help with the debugging only, and are of no other interest to me. Regarding the tools palette, again that was an observation. All the tools are present in the LabVIEW palette. Problems I had with these were with a previous computer. Richard

Message Edited by RichardM on 09-08-2006 10:47 AM

[Meghan R]

Hi Richard,

I have a few questions to help you solve this issue.  First, when you generate code, are you naming the VI MyOutput?  If not, what are you naming it?  Also, could you attach a script and the resulting MyOutput VI to a post, so I can review them and try to help you further?

Thanks,

Meghan

[RichardM]

Attached is the code. The script is vision test. The LabVIEW vi I tried to create was vision test, but it was not created. In LabVIEW Vision Assistant generated the vi MyOutput, which is not attached as this message board does not allow files without extensions. The original file MyOutput created in LabVIEW was saved to disk as MyOutput with no file extension. In LabVIEW I saved an additional copy (MyOutput2) as an additional copy, and this was stored as MyOutput2.vi, which is also attached.

[Meghan R]

Richard,

I am able to run your script and output a VI. 

I believe a repair of vision should fix your issue.  Open Add or Remove Programs from your control panel.  In National Instruments Software, click on the Change/Remove button.  Scroll through the list and choose the Vision Development Module. Click on the repair button. 

Let me know if you're still having problems after the repair.

Meghan

[RichardM]

Hi, I have tried doing a repair and this did not work. I also did full reinstalls in various permutations. What I am doing now is to do a full removal of all NI software, including all registry entries. Then I will do a completely clean re-install.

[Meghan R]

Please let me know how the reinstall goes and if you are still having the issue after the reinstall.

Thanks,

Meghan