cvs 1456 and VBAI Inspection process waits for next part before evaluating

[jimbonic]

I am currently using three CVS 1456 as three independent vision systems using VBAI.  For some reason one of them will not process the current part being inspected until it gets the signal for the following part.  The other two vision systems process and determine the result of each inspection (pass or fail) as soon as it is done processing the steps.  I have them all wired the same way, they all have the same configuration settings as well as the same camera settings.  The unit that is not working properly in Inspection Mode works properly in Configuration mode and run until failure works properly (the part is evaluated and the proper output is attained without the need to run another part through).  But when switched to Inspection mode a part will not be evaluated until the next part triggers the system, therefore, I am always lagging by one part which is causing complications with proper ejection of the rejected part.  I appreciate your time and hope to hear back soon

[RManion]

Hey jimbonic,

How's it going?  That's an interesting problem that you are encountering.  Do you know what software is installed on each CVS?

If I was in your situation, I would first try to format the CVS, install software identical to the other systems, and then copy the VBAI script from the other Compact Vision Systems.  If you are using the same software, the same script, and the same general setup, I can think of no reason that the CVS would wait to process the current image until the next image is acquired.

Give these things a try and let us know how it goes,

Robert

[jimbonic]

Thanks for the input.  I think it is interesting to note that before doing anything, I re-wrote the script exactly the same and it works fine now, however, all the other programs (previously programmed and saved on this unit) are behaving the same way as the bad one was.  So, it's as if I have to redo all the scripts again.  I am concerned that if this continues to occur, am I going to have to re-write all the scripts from time to time?  It doesn't make too much sense to me.  Is there a bug in the software, or hardware that anyone else has experienced like this?  All the CVS' use Vision Builder for Automated Inspections v 2.5. 

[tiocan]

I'm fighting with exactly the same problem that Jimbonic. 

To try to clarify the malfunctioning of CVS1454 , I write the simplest script in VBAI (v2.5) with only 1 step: Acquire Image. The part in FOV trigs TRIG0 which trigs
TRIG1 for flash and TRIG2 for image acqisition by triggered camera Basler 601f. Part Ready is also triggered by TRIG0. In Inspection Mode the result is as follow:
- the fisrt part in FOV is flashed and its image is displayed on the monitor ( Frame index =0)
- the second part in FOV is flashed but not displayed ( Frame index =0)
- the third part in FOV is flashed but it's the second part which is displayed on monitor ( Frame index =1)
This shift in parts sequence goes on with the following parts but remainsat one part.
Please does somebody can help me before I send back to NI this CVS! Thank's

[RManion]

Hi jimbonic,

Thats very interesting.  So VBAI does not exhibit this behavior on scripts that you build now, but it does do it with older scripts?

If it does not do it with newer scripts, or on other VBAI systems, I would try importing a script from either the working system to the problem system, or vice versa and see if the problem appears on the good system or dissappears on the bad system.

I am not aware of any potential bugs in SW or HW that would be causing this.  After giving this a try, please let me know how it goes.

Robert