Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

IMAQ3.1 Installed and VIs with big red X

I installed IMAQ3.1 that came with PCI 1426 card. After installation I found some VIs with big red X on its icons and I tried running the application and it failed saying "The labview memory is corrupted and move to different folder and try again" (The application was running in Imaq3.0). The application shows the error in the IMAQ Snap vi which inturn uses IMAQ Setup which has a big red X on it. Imaq snap VI itself has a different block diagram in IMAQ3.1 and even uninstallation of IMAQ3.1 and Installation of IMAQ3.0 dint help. Even then the VIs are marked with red X.

In the IMAQ3.1 cd its mentioned the IMAQ copy VI will have big red X because its been deprecated and I have the mark of red X in other VIs(IMAQ Setup Still Attribute.vi)which are no way related to the IMAQ Copy.

Its mentioned even if VIs are deprecated they are still included and so applications will continue to work but it dint happen so in my case.

Can anyone help me?

Thanks,
Vivek
0 Kudos
Message 1 of 9
(4,430 Views)
Vivek,

I've got nearby the same trouble with IMAQ Copy (application was running with IMAQ 3.0, and crashed with 3.1). I guess, there are some troubles with compatibility. I have replaced IMAQ Copy.vi with IMAQ Copy Acquired buffer.vi in my application, and it works now. Of course, that was not "direct" replacement, because connector pane was changed, but usage of IMAQ Copy acquired buffer is more easy.

with best regards,

Andrey
0 Kudos
Message 2 of 9
(4,423 Views)
Thanks Andrey.

But the surprising thing is i haven't used IMAQ copy VI in my code and then why should the my code have problem in running? And even the icons that I see with red X dont have IMAQ copy.vi in their sub VIs list.

If I view the block diagram of IMAQ Snap.vi, it has a IMAQ Still Color Setup.vi with big red X. Thats were my code stops popping the error.
0 Kudos
Message 3 of 9
(4,404 Views)
Soliton,
Can you please let us know what version of LabVIEW and Windows you are using? Could you also please attach the simplest piece of code you can that displays this error?

This will greatly help us troubleshoot this error.

Nicholas C
National Instruments
Applications Engineering
0 Kudos
Message 4 of 9
(4,392 Views)
I'm using Windows XP, Labview 7.0, NI-IMAQ 3.1, Vision 7.0 and MAX 3.1.1.

I have somthing similar with a big red X over IMAQ copy.

Moreover I'm having some troubles because setting the black and white voltage level from MAX (also from Labview) of my PCI 1407 an error occurs when the value are not inside the correct range.

I don't understand why this doesn't occur when I use an old computer with a PCI-1408, Labview 5.0, Windows 95 and an older NI-IMAQ.

Maybe it is related to this big red X?

If someone could help my...let me know,

GcDago
0 Kudos
Message 5 of 9
(4,377 Views)
GcDago,
Does this Red x show up on your "IMAQ copy" VI in your functions palette? Or is just when you open an older VI with the IMAQ copy VI? I think this might be remedied by opening your older VI and replacing the copy VI with a VI directly off your functions palette.
So your voltage levels give you an error when they are out of range? This sounds like correct behavior. If it worked before it was probably due to a lack of error checking in an older version of the driver. Meaning the newer version of the driver is more robust and gives an error when your values are out of range.

Nicholas C
National Instruments
Applications Engineering
0 Kudos
Message 6 of 9
(4,373 Views)
Dear Nick C,
- I replaced the IMAQ copy with a big red X with the correct one coming from the palette (where the IMAQ copy has not the big red X) and all seems going well.

- I don't think the new driver is more robust. I think it is the contrary because in the old version the reference voltage levels were coerced to the right ones. I mean that once you wanted to go out of range you were not allowed to do it. .

- Actually I remember that when I installed my old software a warning massage told me that something it has happened in coercing some valu, I don't know, I'm a bit confused.

Could you kindly confirm me that the new version has been designed in this way? If this is the case I will try to coerce these values in my labview software.

Any way thank you very much for your useful support.

Gc Dago
0 Kudos
Message 7 of 9
(4,367 Views)
GcDago,
I've looked through a good bit of the documentation and the only thing I can find in reference to driver changes to the black and white voltage levels is an old document for NI-IMAQ 2.0.

"IMAQ_1408 Setup Analog has been removed. IMAQ_1408 Setup Analog
allowed the white and black reference levels to be set in volts. Use the
IMAQ Attribute VI to achieve the same functionality. The White
Reference Level and Black Reference Level attributes in NI-IMAQ 2.0
are now set in volts instead of steps."

This is from page 3 of the document linked below.
http://www.ni.com/pdf/manuals/321326c.pdf

With that said, you can coerce your values in LabVIEW. The first way is by doing it on your front panel by creating a numeric control and setting the max, min and out of range action properties. You can do this by right-clicking on the control and going to the properties page.

The second way is to do it on your block diagram by using the "In Range and Coerce.VI". Which can be found on the "All Functions->Comparison" palette.

Nicholas C
National Instruments
Applications Engineering
0 Kudos
Message 8 of 9
(4,357 Views)
Thank you,
I've followed your suggestions.

GcDago
0 Kudos
Message 9 of 9
(4,336 Views)