Urgent&Urgent help needed for mask outside of ROI!!!

[Swedlin@hotmail.com]

Hello,

My ROI descriptor is ready and I tried to mask the outside of ROI in labview but failed to find this ready function since two weeks ago. I do think there is a ready function in labview 6 but after searching and searching, I still can't find it! Unbelievable there is no this ready vi in labview lib. This makes me crazed because my project final meeting will be held less 15 hours later!!

Because of lack of proper masking, my vi works unexpectively slower and unstable!

Tell me please which function is exact for this purpose that mask outside of ROI!

Thank you very much for any comments and help!

Swedlin

[BruceAmmons]

Swedlin,

I think you are looking for IMAQ ROItoMask. It is under the Vision Utilities -> Region of Interest.

Bruce

[Swedlin@hotmail.com]

Thank you very much, Bruce!

I am still blocked in the same problem. Before I post the original question I read the instruction on "IMAQ ROItoMask.vi" times and times and not fully understood how to use it but I thought it's not proper one to my problem. Now I have just tried to use it into my vi and found that I am right and it just exact masks the ROI zone (it shrinked also and this is desired) and it's not desired because the ROI for processing had been exact masked away!

Help me to debug the VIs attached please.

I tried many times to attach my VIs as llb type but failed. But VIs attached is enough for you to open each other.

The bug behaviour is as: I created a ROI descriptor to size a reference image(BckImg5.tif) by using
"IVB Mask from ROI.vi"and saved it as any name you like. Then I use the same ROI descriptor to size a raw Img16.tif and further let them subtraction each other. But "User settingROIs to locate up-down edges 1_00.vi" always alerts with an error of "IMAQ Subtraction imcompatible image size".

I have made as much as possible description in each vi in order to let you easier understand their operation.

I still urgent need to solve this problem in my project. I do believe it should not be difficult but I still failed to solve it. I have almost thought that either I was so stupid or Lavbiew.

Anxiuously to look for you and others help.
Thanks again!
Swedlin