NI generated configure range VI provides error

[Daddy-O]

I am trying to use the fp configure range vi to configure the range on a FP-RTD-122. In Measurement Automation eXplorer it shows me that the values I should send to the device are 26 (73-1125K), 27 (-200 to 850C), 28, (-328 to 1562F), 30 (0-400 Ohms), and 31 (0-4000 ohms) based on my desired range.

When I run the "config range.vi" the associated values in the ring enum are 38,39,40,48,and 49 (in the same order as those listed above). SO at first I figured I would just rearrange the order of the items in the enum to get the desired, matching output.

There is a sub-vi withing the config range.vi called Get FP Channel Info.vi (not editable, and password protected) that requires me to select the device type, in this case a FP-RTD-122. When this device is selected, the enum values it generates are 5, 39, 38, 40, 48, and 49, in that order. Since I can't look at the block diagram for this sub-vi I have no idea what the numbers are associated with, or anyway to change them.

To top it all off, within the Configure Range vi there is a check to make sure that the values are valid for the device... Well, of course they are not, so it throws an error.

Has anyone run into this before?

Thanks, in advance.

[Wayne.C]

Daddy-O,

If you open up Configure Range.vi there is a subvi named Get FP Channel Info.vi that is going out and reading the module to create the array of possible values.  You might run just that vi and take a look at the array of available options it returns for the I/O channel.  Compare those numbers against the documentation and MAX.  You might be able to figure out which documentation is correct.

It also looks like the Get FP Channel Info.vi returns the current settings as well.  A little trial and error should let you come up with the correct constants to apply for the different ranges you need.

I just figured out what is causing all the confusion.  The help file for this shows allowable values for the FP-RTD-122 to be 26 - 31.  The fine print adds that these are HEX values.    The index in the enum is not setup for hex display.  And hex 26  = decimal 38.

Message Edited by centerbolt on 04-23-2008 08:05 AM

[Wayne.C]

Daddy-O,

To further clarify my previous edited post.

I just figured out what is causing all the confusion.  The help file for this shows allowable values for the FP-RTD-122 to be 26, 27, 28, 30, 31.  This would seem to match what you saw in MAX.  The kicker is that the fine print adds that these are HEX values.    The index in the enum is not setup for hex display so it will have index values of 38, 39, 40, 48, 49.