Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

VB AI 3.0 custom step

Hi,

I've been developping some custom step for Vision Builder AI 3.0 (in LV 8.0.1)

Sometimes the custom steps works in debug mode but not when built into *.bin file and use in "normal mode" in VB AI 3.0.
First I thought that we were limited to 3 levels of subVIs inside the custom step, but with an empty custom step I demonstrated that the number of  subVI level was not the source of the issue ; I then wondered if the it was the fact I had 3 nested for loop or that I was using, only inside of the custom step, complex data array (2D array of cluster).

In the end I couldn't clearly identify the source of the issue but sometimes the step I develop work *only* in debug mode... and it bugs me !

What are the restriction (such as forbidden functions, data type, other...) I should be aware of for my custom steps to work both in debug and normal mode in VB AI 3.0 Smiley Surprised ??

Thanks in advance for any help

We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

0 Kudos
Message 1 of 3
(3,493 Views)

Sorry for the late reply. If you use VIs that belong to LabVIEW libraries (.lvlib), you might run into issues like what you're describing. If possible, make a copy of the VIs that live inside lvlibs into your custom step llb, rename them by prefixing them with your llb's prefix and disconnect them for the LabVIEW libraries. We're looking into fixing that issue in the next release.

If there is no proprietary IP in the step you're developing, please attach it to the thread and I'll be able to tell you exactly the source of the problem.

If you can't make it public, please let me know and if that's OK with you, we can get in touch directly to try to solve your issue.

Thanks,

Christophe

Vision R&D

0 Kudos
Message 2 of 3
(3,444 Views)
Hi Christophe,

Here is the latest issue we are facing with a custom step for VB AI 3.0, when using OpenG VIs (Variant config palette -> "write section cluster") it CAN create problems. The "read sction cluster" never caused any trouble but when using several time in a row the "write section cluster" OpenG VI, the step only works in debug mode... Smiley Surprised

Here is a screen shot of a part of the custom step, if I remove this part, the step always works, if I put it back it only works in debug mode.



Any idea ?

Thanks alot for your time.


Message Edité par TiTou le 07-30-2007 09:12 AM


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

0 Kudos
Message 3 of 3
(3,393 Views)