LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

application deployment

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....................

0 Kudos
Message 1 of 9
(4,157 Views)

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

National Instruments
Senior Systems Engineer
0 Kudos
Message 2 of 9
(4,124 Views)

2010 for both......I did but it does not show the vi's that are not functioning,......

0 Kudos
Message 3 of 9
(4,119 Views)

By not functioning, do you mean that they do not show up on the block diagram?

 

Lynn

National Instruments
Senior Systems Engineer
0 Kudos
Message 4 of 9
(4,117 Views)

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????????????????????????????????????

0 Kudos
Message 5 of 9
(4,098 Views)

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

National Instruments
Senior Systems Engineer
0 Kudos
Message 6 of 9
(4,081 Views)

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.

0 Kudos
Message 7 of 9
(4,064 Views)

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?

National Instruments
Senior Systems Engineer
0 Kudos
Message 8 of 9
(4,039 Views)

The issue was resolved as the template path in vi named IVB Build Template Path was pointing to another folder. 

0 Kudos
Message 9 of 9
(3,979 Views)