I'm having a similar problem, and from reading the above, it's not clear what one is to do if the chassis and link vendors say "there are no driver files, and none are needed" and NI says, "you must have the appropriate files, which are provided by the vendor." Specifically, I have a Jasper Electronics PXI chassis and a Hartmann StarFabric link (PCI bridge). My NI devices in this chassis (6071E, 6533) have always worked fine, and MAX displays them correctly under Traditional Devices and under DAQmx Devices. The PXI chassis shows up as "unidentified" in MAX, but this has never caused any problems before (and I've seen the same benign error with other non-NI PXI chassis). However, now that I'm using DAQmx, I'm trying to do the following:
DAQmxConnectTerms("/Dev3/PXI_Trig0", "/Dev3/PFI5", DAQmx_Val_DoNotInvertPolarity);
where Dev3 is a PXI-6533. When I start my task, I get the error message "Driver cannot complete the route, because the only way to make the route requires a trigger bus line, and no trigger bus has been configured in MAX for this device." The documentation seems to imply that identifying the chassis will automatically create or recognize the appropriate PXI trigger lines. Since the vendors don't supply any ini files, I tried faking it out as as PXI-8150 system with a PXI-1000 chassis, using the NI ini files; this resulted in entries for both NI cards appearing under "Chassis 1 (PXI-1000)", e.g.
PXI5::11::INSTR (PXI-6533)
PXI5::12::INSTR (PXI-6017E)
although their properties (in the pane to the right of the tree view) show their chassis and slots as "unknown." When I run my code, I still get the error message about needing to configure a trigger bux in MAX. Just for grins, I tried the same thing but with RTSI0 instead of PXI_Trig0, and got the same error. I created an RTSI cable under DAQmx Devices in MAX, and that made no difference. Help!
Thanks,
Larry
