02-17-2010 11:21 PM
Hi,
My computer used to recognize the IMAQ PCI-1407 and all of a sudden the labview program that used to run very well didn't work any more. I install the IMAQ 3.1.3 and reinstall the driver for PCI-1407. But I kept receiving the error message with error-1074397163. I looked up some discussion on this forum that error-1074397163 has to do with a wrong interface value assignment. Under Deivce Manager, it shows that PCI-1407 is working properly(fig.1) but under MAX the PXI is marked "unidentified"(fig.2) and I don't know how to change the so called interface ID. I also attached the MAX report. Can somebody help me with this? Thanks in advance!
02-19-2010
11:57 AM
- last edited on
06-18-2024
06:57 PM
by
Content Cleaner
Hi kauntum,
What version of LabVIEW and Operating System are you using? Make sure you check the LV and OS compatibility with the driver version before installing the latest driver.
It looks like the 1407 is simply not showing up in Measurement & Automation Explorer (MAX). The 1407 is supported by the latest IMAQ driver (version 4.3.1), which is a part of Vision Acquisiton Software 2009.11. Install this newest driver. If it still does not show up in MAX, you probably need to "Update Driver" from Device Manager. Right-click on the 1407 in Device Manager and select "Update Driver." Then go through the wizard, choosing the last option in every menu.
Kristen H.
04-29-2010 11:29 AM
Hi,
I have a similar problem with the PCI-1407. When I opened MAX, it gave me the error 0xBFFF8013 and the note "Could not file a valid camera file for this device in the NI-IMAQ/data directory". I checked to make sure that NI-IMAQ were NI-VISION installed with no error, and the drivers for PCI-1407 is the most up-to-date. What should I do to solve this problem? Thank you in advance.
04-30-2010
04:39 AM
- last edited on
06-18-2024
06:58 PM
by
Content Cleaner
04-30-2010 12:35 PM
hi tam_2407,
I recommend reinstalling Vision Acquisition Software. I found another case with this error and reinstallation solved the issue. They tried other methods, such as replacing the folder, but the did not help. Reinstallation was required. Please let me know if reinstallation does not solve the issue and we can dig deeper.
04-30-2010 02:48 PM