VBAI 3.6

[Bob Rathbun]

Is there a way to run mutilpe inspections sequencially?

I have 13 or so inspections 9.VBAI file) that  run fine one at a time.

But I would like tobe able to hit one button and go.

I was told that you can not place an inspection with in another inspection, simular to LabVIEW and VI’s. but I was wondering if anyone else has attempted this?

Thanks

bob

[BCho]

Hey Bob,

One option would be to put your various inspections into a single inspection, each in its own state, and then configure the transitions in your overall inspection. This will allow you to go from one 'inspection' to another in the order that you decide. Another option would be to use the Select inspection State to pragmatically go from inspection to inspection based on either user input, a LabVIEW routine, or data I/O. The Select Inspection step can be found in the Inspection Steps»Use Additional Tools»Select Inspection.

Hope this helps.

-Ben

[Bob Rathbun]

Ben.

I have tried to condense the inspections into single states and then move them to one main inspection, but it has become rather large and cumbersome.

But thank you for taking the time to respond. I am currently looking into using Teststand to run multiple test cases in sequence.

bob

[BlueCheese]

Bob,

Ben's suggestion of using the "Select Inspection" step should allow you to do what you want without having to use TestStand externally.

Eric 

[Bob Rathbun]

Eric,

My main issue right now is that I have 10 or so Inspections each with 10's of states in each and within each state are multiple steps.

it is a big chunk of my time condensing these inspections into a single state and the copy/paste to a separate inspection.

 I agree Ben's suggestion would work great, but the work is condensing the inspections.

bob

[Chris_VH]

Hey bob,

This sounds like our ActiveX controls with VBAI could help with.  We have an example at:

C:\Program Files\National Instruments\Vision Builder AI 3.6\ActiveX Support\Examples\LabVIEW

That shows how to communicate from LV to VBAI via ActiveX. While the example is not currently set up to do exactly what you want, some programming could probably get you there. You could change it to a state machine that would go through each inspection for you if you wanted.

Maybe this will work better for you than Teststand or complicated "merging."

[Bob Rathbun]

Chris,

I am attempting to use this VI and I receive "error 3001 occurred at ActiveX Automation not implemented in SimpleExampleCW.vi"

[BCho]

Hey Obi-Bun,

How are you using the example program that Chris pointed out? Where you able to run the example code before making modifications to it? While the example is a great place to start, it is not going to be your end solution. You would need to make some modifications to the example to programmatically run through all your inspections. You will also likely want to take out a few unnecessary steps from the example in your situation.

In regards to the error, are you able to pinpoint where the error is occurring? If you run your code in highlight execution, what part of the code does the error occur. Do you get the error if you ran the example prior changing anything, or did the error only occur after you started making changes?

There isn't a specific definition for error 3001. However there is some information mentioned in this Forum Thread, where someone got the same error. Though the situation may not be exactly the same, this thread may yield some helpful information.

Hope this helps,

-Ben

[Bob Rathbun]

I got it to work, thanks to everyone who helped.

the error was taken care of by reinstalling VBAI.

The association of the vbai files had gotten messed up, so when the Active X portion of the program tried to open the VBAI file it couldn't.

thanks again Ben and Chris