09-09-2009 11:48 AM
It sounds like you may be running out of memory on the CVS if a simple inspection works and a more complex one (especially with color images and Vision Assistant Steps) causes problems. Unfortunately when you run low on memory with the CVS, it can take many forms and have diffferent bad behavior that makes it difficult to know this is the problem. You can go to Target>>Target Information to see how much memory is available. When you run the full inspection (the top run button in Configuration mode), you'll notice the available memory starts going down because the inspection is opened on the target and starts running. If it gets below 5MB, this i likely the problem. If you could send the inspection, I might be able to help you reduce the memory requirements. One easy fix is to go to Target>>Target Options and go to Video Mode and choose 16-bit instead of 24-bit. I will be out later this afternoon and will return Monday.
09-09-2009 12:21 PM
I tried that and the lowest it gets to is 36mb so I don't think that's the problem.
Could somehow the inspection files have gotten corrupted? Wondering because it works ok with an older version of the same program which is very similar structurally.
Thanks,
Mike
09-09-2009 01:08 PM
Could be, but i would expect to get an error opening the insepction if that was the case. You could try to copy the inspection to Windows (using VBAI under Target>>Add/Retrieve Inspections) and then open the inspection you copied to winodws in CVS emulation mode, save it with a different name and copy it back to CVS using the Add/Retrieve inspections and see if that works any differently. If it still causes problems, please send the inspection and the slightly modified one that works. (you can copy the files from RT and zip them up to attach to this thread). I'll be back on Tuesday.
Thanks,
Brad