Incomplete Device information

[Chris_Co]

Hello,

I am making a hardware viewer that is much like MAX. It will have additional functionality of showing all pertinant properties like acquisition speed limits, frequency filters, current draw capabilities, voltage ranges etc. However when I query the device propertie nodes, the device SCC 2345 Carrier does not show up at all but the modules themselves do. How can I know which module is attached to which carrier. And futhermore how can I know to which device it is assigned to. I have been doing a task error test to find which device but without knowing all modules associated with a certain carrier this is daunting because it will have to be done for each module. And to top it off I cannot parse module names to classify them to a certain carrier. If a module is attached to a global channel and the carrier is renamed, the old modules do not update to the new name.

I have found a file that shows promise to show alot of answers.A file in the MAX report.zip.  If you have the patients to read it you sort of get the jist of what NI is doing here. The question I have is why are there repeats in the file and is this a reliable file.

Message Edited by Chris Co on 11-24-2007 11:06 AM

[Chris_Co]

Does someone have a decoder ring for the max report file. So far I have determined that spaces determine the heiarchal level of the classes. Each class shows properties appliciplacable to the class including an ID # for the class name, ID # for a parent, ID # of a VIT that perhaps is launched with the property values etc. There are over 2551 classes in the file and over 40,000 lines in the file. I need help or a better way to get my information.

I'll narrow down exactly that. I want to view ALL devices, ALL Modules, ALL accessoreis, Voltage ranges for every device that measures voltage. This requirement is NOT acheivable via property nodes. In fact, there is only one file I have found that can answer it, but I do not know how to decipher it. Since MAX uses this file it seems that there are already dll already written to do just that.By the way, when NI creates a dll they use where do i go to find the documentation on them.

Thanks,

Chris Co.

[Paul_C.]

Hi Chris,

I see that you have opened a service request with National Instruments for support.  I've done a little research and it looks like the MAX report file may be the best way to determine the actual setup of your accessories.  The properties in LabVIEW will allow you to determine all the devices, modules, and voltage ranges through DAQmx system and device property nodes.  Unfortunately, I don't see any properties that would allow you to determine which accessories (SCC-2345) are connected each device.  To determine the accessories and how they are connected you could in fact use the max report file.  I understand that this file may be difficult to parse through.  I've done some research and we currently don't provide any documentation for a better way to parse through or use this file.  We are going to continue work on this issue through the service request.  For other readers of this thread, I will post if a better resolution to the issue is found.

Thanks,
Paul C.

[Chris_Co]

Hi Paul,

Thanks for responding. I agree with everything except the voltage ranges in property nodes. If you will notice there is no voltage for an SCC SG24 given by a property node, however I know the range to be +- .100 Volts, and any other attempt outside of that range will throw an error (as it should).

I will give the file some more time. Does NI have some master table of this info on thier web server (I'm thinking datasocket read and parse).

Thanks, let me know of any developments

Chris Co.

[Paul_C.]

Hi Chris,

I don't believe the voltage ranges property node works with SCC modules.  I have only tested this with a few simulated devices (SCC-AI01, SCC-AI06, and SCC-SG01).  Let me know if you are seeing different behavior.  In regards to your second question, we don't have a master table with the voltage input ranges as you describe.  This table could be comprised using the manual(s) and used to cross reference module number(s) to determine the input range for the SCC modules.   However, we do not currently have this available on our website in a single table. 

I hope this helps,
Paul C.