Would a Ballard or AIM 1553 Card work in a PXIe-1090

[ADW123]

I have tried an AltaData 1553 card in the PXIe1090, but it didn't work due to the card being a PXIe carrier containing a PCIe-PCI bridge which interfaces to the PCI interface on the module.

There is a mention of compatibility issues with Thunderbolt in the card API manual, so I think I'm out of luck there.

The PXIe-1090 appears to operate correctly with my HP laptop and appears in MAX and Windows Device Manager and while it generates numerous PCI-PCI bridge instances, these are all operating normally. 

Consequently I am looking for alternative solutions.  Has anyone experience in using with the Ballard or AIM 1553 cards using a Thunderbolt controlled chassis.

I believe the Ballard solution is based on modules plugged into a carrier card and I'm wondering whether the same problem would occur there.

Otherwise it will have to be Desktop PCs and PCIe cards which I would also like to work with Labview.

Thanks in advance for any suggestions.

[Captain_K · Accepted solution]

I don't have an AIM module, but my Ballard module works fine in a 1090 chassis.

These modules don't show up in NI-MAX by design, but I can see it in Device Manager and also the BTITS32 application that allows me to successfully run a self test on them.

The one thing to keep in mind is that a successful TBT connection (like all PCIe/MXI extensions) are very host dependent. I'm currently using a Dell Precision 5570

[ADW123]

Thanks for your feedback

I have just had a similar response from Astronics support.  They say that it depends on your Thunderbolt interface and that some computers work while others do not.

It is interesting to see that it doesn't appear in NI MAX.  Have you bought the card direct from Astronics and are using BTIDriver interface rather than NI-VISA?

Edit: Perhaps you mean that the Card appears in MAX, but you can't see the individual modules there.  That would make sense.

Best Regards

[Captain_K]

Sorry for the delay.

The module I have came from NI. The module not showing up in MAX is based on the driver's design. It won't show up in MAX regardless of where the module is purchased from. The only real difference between where the module is purchased from is that modules purchased from NI are keyed to work with LabVIEW. Modules purchased directly from Astronics are not, meaning they will not work with LabVIEW.