‎12-07-2010 08:01 AM
I have migrated a Vision Builder application into LabVIEW. Created an application to deploy on a target but not all the dependencies vi's function/work. The main vi functions properly but the executable doesn't, even on the application development pc. ANY HELP WOULD BE APPRECIATED........
Thanks....................
‎12-08-2010 01:52 PM
Hi,
What versions of LabVIEW and Vision Builder are you using? Are you able to 'Enable Debugging' for your executable to determine which VIs function properly and which do not?
Lynn
‎12-08-2010 01:56 PM
2010 for both......I did but it does not show the vi's that are not functioning,......
‎12-08-2010 01:57 PM
By not functioning, do you mean that they do not show up on the block diagram?
Lynn
‎12-09-2010 07:56 AM
Lynn,
The source vi does function but the stand alone application executable does not. I stripped the source to only include the step "Detect Defects". Detect defects is a step generated using vision builder. There is a something amiss. What that is I do not know. I am currently working with one of the application engineers but he can't make sense out of this matter. Who else can help????????????????????????????????????
‎12-09-2010 11:34 AM
Could it possibly be due to a corrupted VI? Have you tried copying the block diagram to a new VI, building an exe, and running it? I'm curious to see if that works.
Lynn
‎12-09-2010 04:00 PM
Yes, tried with no avail. Have tried several executables with other inspection algorithms with success. The only one is the detect defects step that causes the grief.
‎12-10-2010 02:21 PM
Does your VI acquire images from a camera or simulate images? If you try the other option and create a VI and executable are you able to run it?
‎12-21-2010 02:45 PM
The issue was resolved as the template path in vi named IVB Build Template Path was pointing to another folder.