TEDS data

[MEastwood]

Hi,

Im currently using two Transducer Techniques sensors (TRT-25 and THC-1K-V) which both support TEDS (Transducer Electronic Data Sheets). Im also using a NI9237 module with the NI cRIO-9002, which is TEDS compatable. Im using Labview 8.5 with the TEDS library installed.

My problem is when I run the attached vi, I only get some of the information from TEDS, the information I get can be seen in the attached image file. Transducer Techniques state I should be getting more than this information, which can see at the following link http://www.transducertechniques.com/Learn-about-plug-and-play-smart-sensors.cfm. What am I doing wrong? I have tried numerous different methods using all the VI's that come with the TEDS library and cannot seem to get any more information.

I have spoke to Transducer Techniques technical support and they suggest its a problem with the hardware/software that is getting the information out of the sensors and not the sensors themselves, which does make sense as both sensors give the same results.

I have also attached to FPGA vi just incase anybody would like to view it.

Any help would be much appriciated.

Thank you,
Mark

[rstebner]

Mark,

I didn't try running your VI's, but I have a feeling I know what the problem is based on the fact that I had the same issue as you just a couple weeks ago (using two NI9237 modules in a cRIO-9004).  The information you are getting from the TEDS EEPROM is the basic information.  In order to decipher the rest of the data you need to be able to open the corresponding TEDS template.  On your development PC the templates are located here:

c:\program files\national instruments\shared\teds\templates\

When your cRIO runs the VI it tries to find that path on it's own drive space rather than looking at the hard drive of your development machine.  There are two ways to fix this:

1. Change the path to include the UNC path to access that folder on your development machine.

2. Save the NI_IEEE_Standard.tdl template on the cRIO itself and just use c:\ as your path.

I went with option two because it was quick and easy.  Post back here if it doesn't work and I'll take a look at your VI's.

~Russ