PCI-1411 Error 1074397163 and 1074397179

[nexussix]

I have a PCI-1411 installed with a AT-MIO-16XE-50 I have the following configuration:
NI-DAQ 6.52
LabView RT 7.0
NI-IMAQ 2.61
MAX 3.02
NI Session Manager 3.0
Vision 5.0

I am getting the following errors:
Error 1074397163 occurred at CleanUp module
Possible Reasons:
NI-IMAX bad interface

Error 1074397179 occurred at IMAQ Grab Acquire.vi
Possible Reasons:
NI-IMAQ

I believe my problem is the mix and match of software versions I am running. Our system was designed by a third party and we have no way of finding out what NI software we need to run our applicatioin. I have spent much time getting all the bugs worked out with the AT-MIO-16XE-50. Everything is working with it at present.


Please offer any suggestions to this configuration.

Thanks!

Ben LeDUC
bpleduc@bpleduc.com

[ColinAE]

Hello.

That certainly is a very strange mix and match of software versions that you have. Just FYI, the most compatible versions of the drivers to go with your hardware and LabVIEW would be:

NI-DAQ 7.3
NI-IMAQ 3.0
IMAQ Vision 7.1

Based on your versions, I would not be surprised to see a fair bit of struggle!! Now, looking at your errors:

Error 1074397163 occurred at CleanUp module
Possible Reasons:
NI-IMAX bad interface
There is an old KB about this error:
KnowledgeBase 1PEDKU7T

Basically, verify that your interface names are correct. Additionally, run the HL Snap example that ships with LabVIEW (from example finder) to ver
ify that the interface is able to get images.

Error 1074397179 occurred at IMAQ Grab Acquire.vi
Possible Reasons:
NI-IMAQ

There is no formal documentation as to the nature of this error, but I have heard of problems with 10-bit versus 8-bit images. Be sure that your board is acquiring images that match the type of image buffer that you are creating using the IMAQ Create VI. If you feed an 8-bit image buffer into the Grab Acquire VI and you are acquiring a 10-bit image, you will get errors. You can make sure that your interface is acquiring 8-bit images in MAX, or change your IMAQ Create to create a 16-bit buffer.

As a high-level suggestion, I would think about standardizing on some slightly newer software, but I definitely understand that this is not always possible. Finally, rely on the shipping examples to verify that the functionality of the IMAQ driver is working properly, then move into your program.

Good luck with the system!
Regards,
Colin
C.
Applications Engineering

[nexussix]

Thanks for the suggestions. One detail this is running on WIN 98. I cant put the ISA in a newer computer... Will these version you mentioned work with Win 98?

Thanks!

Ben LeDUC

[ColinAE]

Ben,

Hmm, that does complicate things slightly:

Suggestion 1:

Consider upgrading to a PCI E-series board, which is supported in the latest versions of the driver that I mentioned, and in all likelihood will work fine with the traditional DAQ application that you have with the MIO-16XE-50.

Suggestion 2:

Try to get the latest drivers that are supported on Win 98, which are:

NI-IMAQ 2.6.1 (which it sounds like you are using)
NI-DAQ 7.1

Good luck!
Colin C.
Applications Engineering

[carpat]

Hi,

FYI I'm currently running NI Vision 8.6 and IMAQ 4.1.

I'd like to create a vi capable to acquire single images in order to process them later on. Thus, I have two sequence steps, one for the acquisition and the second one for saving and/or processing.

The error is located in the first step of the sequence so no need to pay attention to the second step.

When i launch the vi, i enter into a loop waiting for the user to press an "acquire" switch. If pressed, its value becomes TRUE and it acquires a single snap image and this works just fine. While the switch's value is FALSE, i'd like the vi to grab automatically images in order to allow the user to rotate/focus the camera on live. pressing the STOP button takes us out of the grab loop and enables to snap an image.

That's where the problem is: when i launch the very same VI step by step and highlighting every step, it works just fine. However, when the VI works by itself, pressing the STOP button returns to me the error 1074397163 about a wrong interface or session at the IMAQ grab acquire Old Style...

Can someone help me out on this one pls?

here's the VI i'm working on. Thanks for any help 😃

[carpat]

I managed to work out my problem:

In my previous vi, when launching the vi, one entered a while loop checking whether the user pressed "acquire an image".

If TRUE, the vi acquired an image and passed to the next sequence, no pb.

If FALSE, the vi entered a while loop, grabbing images in order to enable focus of the camera. The pb was when i pressed STOP button, i exit the while loop, then exit the condition structure, then asked again if user pressed "acquire an image" which was most probably still FALSE since i don't have time to press STOP and ACQUIRE so fast.... Therefore, the vi entered once again into the condition structure, then the while loop, and did all the grabbing job again but with an invalid session/interface name since pressing STOP button tells IMAQ close.vi to close the session.

The solution i came up with is to include a condition structure:

Let us enter the while loop asking "acquire an image T/F?"

If TRUE, same thing.

If FALSE, i added a condition structure with a First Call T/F? module. The first launch gives access to the while loop and the grabbing part. When pressed STOP, i exit every loop and ask again "acquire an image T/F?" surely FALSE but this time, it won't be the first call so i won't access the grab loop again with an invalid session name. I would simply highlight the "acquire an image" button, forcing the user to press the button and pass to the next sequence.

I've attached the corresponding vi so you can see by yourselves 😃 i'm aware explaining things like this must be a bit awkward but i'm not a NI engineer so i'm doing my best 😃

[carpat]

:s my VIs have the same name but they actually are different. The older one is of course the trouble one and the most recent one is the troubleshooted one ^^