10-01-2005 04:53 PM
10-03-2005 09:41 AM
10-04-2005 11:32 AM
Tom, Thanks for the reply.
But I think that your statement that DAQmx handles TEDS directly is misleading. Consider the following:
Since I'm working with SCXI-1520 and SCXI-1314T hardware my discussion be slanted towards strain gages. I've configured 4 different TEDS EEPROMS with the strain gage template (ID=35), with unique values for physical min/max, electrical min/max, nominal excitation, and bridge resistance. I have a simple VI that consists of a DAQmx Create Task followed by a DAQmx Configure TEDS followed by a DAQmx Create AI Channel TEDS(sub) (I extracted this from the DAQmx Create Channel (TEDS-AI-Strain-Strain Gage) to eliminate the effects of the property node in the parent VI) followed by a channel property node (to observe the min/max, bridge resistance, etc.) followed by a DAQmx Clear Task. When I run this VI on one of my channels, it is clear that the physical min/max and excitation levels from the TEDS are not propagated to the channels properties by DAQmx (based on the property node in DAQmx Create Channel (TEDS-AI-Strain-Strain Gage) this is what I would expect), but the bridge resistance is (i.e. the value from the TEDS is displayed).
Another situation arises when dealing with the Gage Type and Type of Bridge entries from the template. The Type of Bridge is straight forward, either quarter, half, or full. But the Gage Type values available in TEDS provide many more possibilities than the types provided in DAQmx (Full Bridge I, II, III, etc.). If I set up a TEDS template for rosette, I get readings from the VI, but don't know if it's really using the information from the template.
So when I'm using the DAQmx Create Channel (TEDS-AI-Strain-Strain Gage) in my code, do I assume that the only parameters I need to pull out of TEDS myself are those necessary for the inputs on this function and it will extract any other fields it needs itself? How can I tell which fields from the template are being used by DAQmx? Do I need to explicitly pull out all the fields that apply and use property nodes to get these values into DAQmx?
I think most of this all boils down to a lack of detailed documentation. I could run lots of experiments, but can't afford to invest the time. So it looks like I'll have to pull all the fields from TEDS myself and use DAQmx function inputs and property nodes to try and make sure each channels is configured correctly. But if I have to do that, what's the point of having the TEDS variations in the DAQmx Create Channel function?
10-04-2005 12:29 PM - edited 10-04-2005 12:29 PM
Message Edited by Tom W. on 10-04-2005 12:29 PM
10-04-2005 04:41 PM
Tom,
I commented to several R&D engineers last year about the state of the documentation but not much has changed since then (my guess is because TEDS isn't a big part of NIs business, so resources have been re-allocated to other areas and there isn't any ongoing development/improvement).
Ok, I'm done whining, I'll go finish my code now.
10-05-2005 03:28 PM
Hi DAD-
I can understand your frustration, but I would still encourage you to file your request online. Product Suggestions are forwarded directly to the decision makers within the R&D structure. That would definitely be the best route to have your requests heard.
Thanks again and best of luck with your app-