ni.com checkout is currently experiencing issues.
Support teams are actively working on the resolution.
ni.com checkout is currently experiencing issues.
Support teams are actively working on the resolution.
03-23-2012 10:18 AM
I have a client with an older SCXI system that I am upgrading. While replacing the Traditional DAQ options, I would like to code a zero-configuration routine for them (or as close to zero as possible).
I can find the SCXI modules using the DEVICE properties, but I can't seem to pin down exactly which slot they are in. I the aliases are in alphabetical order it works, but not if they mess with them.
Any ideas? MAX seems to know...
Solved! Go to Solution.
03-26-2012 12:36 PM
Hi Jed,
Are you attempting to convert a Traditional DAQ MAX configuration programmatically into a DAQmx MAX configuration or something else? The DAQmx API does not expose the capability to query for an SXCI module slot number. I would suggest taking a look at the NI System Configuration API (http://joule.ni.com/nidu/cds/view/p/id/2613/lang/en). The "System Hardware" class property node from the System Configuration API contains a Slot Number property which should return the correct slot number.
03-26-2012 01:10 PM
Thank you for the info. I am able to find the slot number.
BUT I while I can find the individula components (the SCXI-1000 is listed, as are the individual modules) there doesn't appear to be a way to figure out that they are on the same device. That is, there is no way to find out what modules are on what chassis.
At least, I could not find a way.
Jed
03-26-2012 01:50 PM
Hi Jed,
I cannot seem to find any way to do this programmatically from an API. However, a round about solution could be to generate a MAX XML Report using the Generate MAX Report.vi and parse this report to get the device info. The chassis name of each individual SCXI module is stored in the SCXIModule.Chassis element of each SCXI module.
03-26-2012 03:05 PM
Ha! I will look at that. Most likely, this SW will only be used specifically on machines with one SCSI box. BUT you never know, and I don't want a zero-configuration that can get tripped up.
Thank you.