Custom PXI Chassis/Backplane wont show in MAX

[Sagme_Mi]

Hey,

I am trying to connect a custom build PXI Chassis/Backplane to a Windows 7/10 pc (PXIe 8360 / PCIe 8361).

Problem:
The Chassis wont show up in MAX, cards inserted in the chassis do just fine. It just shows the "NI SMBus Controller...:"

If i switch the resource manager to "Keysight Technology" (which i installed) the chassis shows up correctly with the cards underneath and the "NI SMBus Controller..." is gone again.

I am pretty sure I missing just a small part, but cant figure it out yet. Maybe someone stumbled over the same problem in the past and can give me a hint.

br

Michael

[Sagme_Mi]

just to clarify: *thinking loud*

if I am right MAX should at least show an unknown device if the EEPROM of the chassis is correct, even if the descriptor files aren't correct yet.

On the other hand:

if the EEPROM is incorrect MAX should not reach the NI cards which are in the slots

[Robert__R]

Sagme_Mi,

Your "other hand" isn't correct.  MAX will find the cards, even with a bad chassis descriptor EEPROM, as long as PCIe is working.  But it won't be able to group them into a chassis.  So having cards show up doesn't imply anything about your chassis EEPROM.

I don't know much about the rest.  Your checksum needs to be correct.  You could check your algorithm by reading the EEPROM from a chassis that works and see if you calculate the same checksum that's recorded in the EEPROM.

- Robert

[Sagme_Mi]

Hey,

thanks for your answer.

Couldn't figure out where the problem is till now... (maybe a small HW bug)

Also tried to contact other PXIe manufacturer and got different answer if i need a driver for NI MAX to detect their chassis... some were like "no" and the other "recommended" to install some driver package.

But we think we also found a small hardware issue. I will get back if we fixed that "problem", maybe everything is fine by then.

EEPROM on the other hand should not be the problem, we have checked it several times and also tried to put a completely wrong EEPROM on the chip and got some weird errors (which we dont get on the "correct" one)

br

SagmeMi