cvs inspection select

[MartyP]

When using the select inspection state in VBAI to switch between inspections I can select the initial inspection that I want to run using iso inputs 0-4, but I can't change to another inspection when the current inspection is running. On power up it runs a blank inspection with only the select inspection state programmed. I can then select the inspection I want with the correct input. Do I need to shut down the CVS or use the external shutdown control (iso input 11) before selecting a different inspection?

[scott_7723]

Which version are you using?  If 3.0, are you using the "Latched" or "current" when reading ISO 0-4?  I personally am finding I have to keep it at "Current" (or not latched to ISO 5) to have it change automatically.  But, the lines must remain at that state.  So, say you assign 1 to part a, so you need ISO IN 4 to be high, and remain high, and the others to remain low for as long as you want that inspection to run.  When it is latched, I believe ISO IN 5 has to detect a rising edge, otherwise a re-power.  Do you have it set to load on startup in the remote target options?  I had to enable it in the remote target options to automatically load a program on startup in 2.6 for these lines to function desirably.  In 2.6.1 the inspections changed for the existing part being inspected dependant on the current state of lines 0-4; in 3.0.1, it takes effect after the next part.  In other words, if I run inspection 1, then change ISO in 0-4 to say 2, the next part being evaluated is still going to be evaluated as inspection 1, then it changed over to inspection 2 for the next part (in 3.0, but not 2.6).  This is unfortunate for that one part.  If you or anyone knows a way to have product selection for 3.0.1 behave like 2.6.1, please let me know.  Can I have it check this before it inspects rather than after?  Not sure if this helps, MartyP.  Good luck.

[MartyP]

Scott,

Thanks for your reply.

Since I posted this question I've discovered the problem. I had a transition back to a state where I would trigger my inspection and I never went to the end of my inspection. After I changed this it worked fine except for the problem you encountered where it would run once more  in the previous inspection before changing to the new inspection. To fix this problem I setup a state looking for input 8 as a trigger and inputs 0 thru 4 for my selection. I then used three logic steps, the first looks for input 8 to be true and  input 0-4 equal to 1. The second input 8  and 0-4 equal to 2. The third input 8 and 0-4 equal to 3. I then set up my inspections in separate states and configured my transitions based on the logic calculator steps 1,2 or 3. It seems to work OK and takes about 1/2 second to run. 

[scott_7723]

So, you just have one inspection that just branches out dependant on the reading of ISO 0-4 when ISO 8 goes high.  I thought of doing this but I have about 10-20 different inspections on 3 different CVS' each with there own programs (upgraded to 3.0.1 from 2.6.1 only recently).  I am not aware of a way that I could simply cut entire programs and paste them within another using VBAI.  If I was using LV, then yes, but, ugh.  Also, I wonder how many branches, or states, I can have in one program.  Do you know the limits off hand?  I was hoping there was another way, but, you may be doing it the best way.  Thanks. 

[MartyP]

You can copy and paste entire states and whatever is configured in the state will be copied. However you will have to modify your inspection because if you have a display image it will look for the image acquired in the state you copied from. Set coordinate system also had to be opened and resaved without modifying. Still this was easier than starting from scratch. I didn't try to copy transitions or entire inspections.Good luck finding out hoe many branches or states you can have. It's pretty difficult to find this kind of information. I would think you would be limited by available memory. You might also be limited by how much space you have on the configuration screen. My next application will have to include image transfer to a remote hard drive. I'm notlooking forward to that as it will have to be done in Labview unless I can create the FTP transfer in Labview and import it into VBAI. More likely it will be the other way around. Migrate the VBAI inspection into Labview. If anyone has any ideas on this I could sure use some help.

[scott_7723]

I guess I should have atleast tried before asking, but very good then.  Copy and paste does work.  Thanks MartyP.  Have you had any issues with the CVS or software locking up when you make a change in config mode then switch to inspection mode?  It seems to be happening often for me over here.  I know if product select is enabled it loads the default program first, then reads the ISO 0-4 lines, then changes to desired program, which would no longer be an issue if I did what was just discussed in previous reply, but wondered if that was an issue for you...software lock up.  Closing VBAI and reloading it didn't always take care of issue, I had to reboot the CVS then re-open VBAI in config mode then switch to Inspect mode.  I'm sure it's due to Waiting for a trigger.   Wonder what the minimum PC requirements are for this stuff.  Furthermore, have you mangaged to get an inspection to stop when you press stop rather than having to wait to trip it again?  Of course, assuming you are acquiring images, not simulating.  Seems I've seen something on this else where, I'll dig.  Easy enough to do in LV, just think stop should stop as soon as you press it regardless of waiting for triggers and such.

[MartyP]

I did have the CVS lock up on me on several occasions.  You also should to be aware that it will ask you if you want to save when shutting down or switching to configure mode. Don't say no or you will lose the program in the CVS.  I would make sure you have a copy on your pc. At least I know it isn't just me that  is having these problems. I am acquiring images with a firewire camera, constantly running so that I don't have to use an external trigger for the camera.