Having problems with auto-script!

[voodoo]

Hi!

We're using an IEEE 1394 noname board (OHCI driver) and a Basler A302f IEEE 1394 cam with vision builder 6.0 and lab view 6.1... The point is, that
there isn't any driver selectable in MAX 2.2 for the cam. But the cam works pretty fine in Vision-Builder in snap or grab-mode, but when the script is transformed into a VI, i always get a an error code, which i don't know exactly at the moment, but it means 'bad interface'...i can post the exact code tomorrow... Maybe you can help me?
Thx for reading!

Stefan

[BruceAmmons]

For firewire cameras, you need the IMAQ for IEEE-1394 drivers. These can be purchased from NI. It is not clear if you have these drivers or not.

Once you have the drivers, they should recognize the camera and create a configuration file for it in MAX.

Bruce

[voodoo]

Mh sorry, im already using the IMAQ for IEEE-1394 driver in version 1.1 but there is no entry in
cam0: Basler ... ->right-click->driver ... (MAX) But the drivers was/is installed properly. Anyway the setup-guide said so!

Stefan

[BruceAmmons]

Stefan,

It sounds like everything is installed properly. If you have cam0: Basler... then MAX is recognizing the camera properly. If you can use the Snap and Grab buttons within MAX then everything should be fine.

It sounds like there is a bug when Vision Builder creates the LabVIEW code. The only thing I can think of is to check if the LabVIEW code is looking for the correct camera. The name in the LabVIEW code has to match the name in MAX.

Bruce

[BruceAmmons]

Another thought -- The code generated from the script may be using the standard IMAQ routines instead of the 1394 IMAQ routines. You may need to replace each one with the equivalent 1394 routine.

Bruce

[voodoo]

Thx for helping Bruce!

I will try that tomorrow afternoon!

[Kyle_V]

Even though you acquire images through a 1394 camera, Vision Builder uses the normal NI-IMAQ VIs when generating LabVIEW code. The NI-IMAQ VIs and the NI-IMAQ for IEEE-1394 VIs are very similar, so it should just be mostly a matter of direct replacement in LabVIEW.

Thanks again, Bruce!

Kyle V

[voodoo]

Thx a lot Bruce - Direct replacement of the IVB with the 1394 functions fixed the problem very easily. Now the cam works pretty fine.

Voodoo