NI 1433 board listed but cannot be configured

[MengHuiHanTang]

I installed the latest Vision Acquisition drivers, plugged in the PCIe 1433 board into one of the PCIe X 16 slot. When I opened MAX, I saw the PCIe 1433 board listed, but followed by a long list of hardware info. No camera detected, and I cannot change the board name either. 

So what caused this issue? Why MAX found the board correctly, but cannot configure it? 

Please help. 

[Andrey_Dmitriev]

This is a Camera Link frame grabber, which is digital and does not have a channel to detect an attached camera. Unfortunately, I don’t have a similar device on hand, but as far as I remember, the camera will never be automatically detected. You have to select it manually, or you should have an *.icd file if the camera is not listed. Also, the name of the device usually cannot be changed, so it may be normal to see the VEN/DEV string here.
Another suggestion: you have a very recent version of IMAQ, which might not support PCIe-1433 any longer. Check whether the installed IMAQ version supports PCIe-1433; you may need to downgrade (or upgrade) to a compatible version.

[MengHuiHanTang]

Thanks for your help. I posted this a few days ago, but did not get any feedback from NI team. Sad.

As you suggested, I checked the 'readme' of the latest IMAQ driver. I did not find any direct evidence that PCIe 1433 support has been dropped. Actually the board is listed for sale, and price has been increasing. So I don't think the driver is the issue here. 

It is more likely the computer itself. This is a DELL QBT1250 computer. After I installed all the vision acquisition drivers and plugged the board into the X16 PCIe slot, I got the following message.It seems that the board is not even started in that slot. 

So now I am not sure if it is a faulty computer or something else. 

[MengHuiHanTang]

As comparison, when the board is installed properly, it should look like below

in MAX, it should be clearly listed as a PCIe1433 board, not followed by its hardware identifiers. 

[MengHuiHanTang]

More Update from this morning

I rolled back the IMAQ driver to 2020 version, and the board was detected, configured correctly, both in Windows and in MAX. So it seems to be the driver issue, right?

No, I started to update the driver to 2023, 2025 Q1, 2025 Q3, and 2025 Q4. All the drivers found, installed and configured the NI-1433 correctly. 

So I don't know why it did not do the same thing before. Weird and frustrating. Now IT team think I am out of my mind. 

See the Event records for this card in this computer. Every driver update works fine. 

compared to this

[Andrey_Dmitriev]

Usually in similar situations I startung with clean install from the scratch (means from Windows reinstall). From my experience with IMAQ PCI - I have had Asus motherbord, which lead to reproducible BSOD when IMAQ 1405 was inserted, but it was a very long time ago. And another case was related to installation - I need to install lot of NI software, and after each installation of the driver or Run-Time, etc I did not performed rdcommended restart (because was too lazy and do not want to waste time). Once restarted after all installation, nothing didn't work as expected, no image from framegrabber, everything was messed, so I reinstalled everything accurately, and performed every recommended restart, then all was OK after that.