VXI-MXI-2 Card Part Number 183345L-01L versus 777178-01

[PeggyC]

We are currently investigating into an issue that VXI chassis loading issue.  And, as part of the investigation we found out that, although we all ordered the same part, but the physical VXI-MXI-2 extender card label have different part numbers: 183345L-01L, 183345K-01, 183345H-03. 

What are the part number on the label mean?

Would there be potential compability issue between different part numbers?

Thanks

Peggy

[Shalini.M]

Hi PeggyC, 

The different letters on the part numbers represent different revisions of the same product and there should not be any compatibility issue between those different parts. 

Regarding your VXI chassis loading issue, in case you haven't already seen it, the following link provides some troubleshooting steps to try: https://www.ni.com/support/vxi/debug_troubleshoot.htm

[PeggyC]

Thanks, Shalini.

The issue that we are having is strange that we have test station with VXI chassis setup and have been running fine for about a year or so.  And for some unknown reason, we first could not see any VXI in the Measurements&Automation.  After couple power recycle on the computer, VXI instrument scan would take really really long time.  Then, sometimes, after power recycle, everything would function normally for a while.  We are trying to find more spare hardware to swap to check if the hardware could have issue, so far we couldn't find anything yet except for this part number difference.

[ashley_gee]

Hi Peggy,

Like Shalini said, the part number does not matter for compatability. 

Can you identify anything that changed between when the system was working and when it first started having problems? Were there any OS updates, code changes, hardware changes, etc? 

Finding different hardware to swap out is definitely a good next step. If you can swap out each piece (chassis, modules, cables, PC) one at a time, you can sometimes narrow down where the problem is coming from. This will be a little more complicated because the issue is not consistent (it resolves after a power cycle), so keep that in mind!

You can also always create a service request with us to troubleshoot this further.