NIVBAILib.ocx imaq IO state error when loading inspection

[jeremy_]

Hello,

I built a small GUI in visual basic with visual studio 2005

I used some ActiveX objects like NIVBAILib.ocx to control VBAI and  CWIMAQViewer to display images.

I based my work on the InspectionExample from within the Vision Builder 3.0 tree.

I'm able to load example inspections shipped with VBAI 3.0, but as my own inspection is using IMAQ I/O steps,
it crashes within ShowOpenInspectionDialog.

If I sweep this inspection from it's IO step, everything is working well.

I tried to add  CWIMAQIO and CWIMAQ1394 assemblies in the references, but it doesn't fix anything.

Thanks in advance for your attention.

[Matthieu Papaux]

Hi Jeremy,

- Did you receive an error message?
- Did you try to upgrade to the Application Builder 3.0.1?
- What Vision Card do you have on your system, does it support IMAQ I/O steps?

Best Regards.

Matthieu

[jeremy_]

Hello Matthieu

- the message error is inspection.System.Runtime.InteropServices.COMException( 0x800A0005) Invalid procedure call or argument, can't find better for know ...
- I'm using VBAI 3.0.1
- the IO card is an NI-8254R, it works well for more than three month with an inspection using IMAQ-IO steps

I tried my GUI with the floppy disk inspection shipped with VBAI 3.0, it works well,
I simply added a IMAQ-IO step in this inspection, it works well with VBAI 3.0.1, not with my GUI ...

Best regards

[jeremy_]

weird !!!

I'm able to connect to VBAI 3.0.1 trial version using : NIVBAILib.NIVBAITargetVersions.vbaiLatestAvailableVersion

but on my production box where the hardware is, it's failling with a
System.Runtime.TargetInvocationException( 0x800A005): Invalidprocedure call or argument thrown by
NIVBAILib._NIVBAITargetControl.Connect( String Password, NIVBAITargetStatus& Status)

so I'm connected using NIVBAILib.NIVBAITargetVersions.vbaiVersion300 !?!?!

But on this production box have got VBAI 3.0.1 registred.