I was curious if I was doing something wrong with regards to loading an inspection to a PC from the CVS, then saving an inspection back to a cvs using VBAI 3.0.1 while it is still running another inspection using VBAI 3.0.1.
I have used VBAI 2.6.1 and earlier versions and it was so easy... I would copy the VBAI product file from the ftp of the CVS, import the product inspection into VBAI on my PC and add a simple Simulate Acquisition step after each Acquire Image step. I would run all captured failure images to see why certain parts were failing, make the adjustments as necessary, then remove the Simulate Acquisition step(s) that were added, then I would save it to my products file on PC, copy it to the CVS via ftp site, and then stop the currently running program running on CVS and play the recently added one via the VBAI Inspection Mode screen. Down time=5 seconds tops. All worked well. Why this isn't the same with VBAI 3.0.1 is beyond me; I'm hoping I am just missing something small here.
With VBAI 3.0.1 it would seem I HAVE TO transfer any inspections from a PC to CVS via the Inspection manager, rather than by means of simply copying it to the proper directory via the ftp site of the CVS. This means I have to stop the CVS, go to config mode then inspection manager every time I wish to transfer updated programs? Otherwise if I simply copy the product file from 3.0.1, it isn't in the same file format, and thus the CVS doesn't want to run it. In other words, in 2.6.1 it expected to see one folder containing the following: PNG, TXT, BIN; In 3.0.1, the CVS expects to see a folder containing a .vbai and .png files? or the same as 2.6.1?, but when I make adjustments to a program in 3.0.1 on my computer, it saves it as a single file .VBAI only rather than a folder containg the png, txt, bin, and the CVS won't play it unless I transfer it via inspection manager. I have to be doing something wrong. I understand that PNG files are only there if a template is used, but how do I create the proper txt and bin file from PC without stopping the CVS and going to inspection manager? It is critical that I don't stop the CVS'. I can't believe it wouldn't be as easy as 2.6.1 with copying inspections into the CVS via ftp. Any thoughts are very much appreciated. Thanks for your help.
Also, simulating a product file taken from a cvs running multiple cameras and I/O on 2.6.1 didn't return so many errors as does with 3.0.1 (such as IMAQ I/O errors). Same with simulating it. It seems to me I couldn't get it to overlook these steps no matter what as did occur automatically with 2.6.1. In 2.6.1, you got the one error saying an incompatible step, then that was it until you loaded it the next time. But all would still be overlooked while simulating it. 3.0.1 doesn't behave the same?