LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

i have a main VI and a subvi.the main vi calls the subvi which runs perfectly some times but not always. how can i make the subvi reliable?

the input to the subvi is the path of an image. the image is created and processed by the subvi and then outputs an image.the problem is that this subvi not always give the output even if the image path is kept constant. can anybody suggest me what should i do to solve this problem.
0 Kudos
Message 1 of 4
(2,756 Views)
Hi,

It's difficuilt to see what the problem could be. I suggest you attach your VI's, if thats possible.
If not more information but what the subvi is doing.
What error conditions are you seeing?
Any hardware involved, before the call to subvi, during call to subvi?
What are the condition before you call the subVI?
What error trapping are you doing?

Regards
Ray Farmer
Regards
Ray Farmer
Message 2 of 4
(2,756 Views)
hi,
thanks,
as soon as the main program starts the subvi is the called by passing on the image path to it. hardware is no where related to the subvi.the subvi generates an image. it processes it to read the barcode and return barcode and original image.the ROI in the read barcode even though is correct, it is not necessary that the barcode is read every time.
0 Kudos
Message 3 of 4
(2,756 Views)
Something is definitely wrong, but we cannot tell without seeing the code.

In how many other places it this subVI called? Does it have uninitialized shift registers, case structures, etc? Is all strictly done with wires or do you use value references or local variables.
What else does the calling program do with the image indicator?

Open the subVI and place a few probes. Do they have the expected values?
Message 4 of 4
(2,756 Views)