Reading fpbank.ini file channel type designation

[PhoenixFIF]

The fpbank.ini file located in the system folder of the Field Point contains the all the I/O configuration information.  This includes for each channel a type designation as follows “Item(#).Type=(#)”, the last numeric corresponding to a configuration type (digital counter, analog input, LED, Thermocouple, etc.).  In attempting to get a list of type designations from NI support it was sent up to NI R&D and their response was that this is an internal list that is not for release to customers.  It’s not like I can’t make different configurations and see what type designations come from each one and figure it out my self.  It looks like NI is keeping secrets for no other reason than to keep secrets.  Thanks NI.  Before I go to the trouble of working up all these definitions my self, does anyone out there have even a partial list they have put together that they are willing to share..

Message Edited by PhoenixFIF on 03-30-2007 04:33 PM

Message Edited by PhoenixFIF on 03-30-2007 04:36 PM

[Nadim R]

Hi,

I understand your disappointment regarding the fpbank.ini information.  Let me explain the reasons behind why we do not release this information.  The fpbank.ini file is used internally by the FieldPoint driver, and we cannot guarantee that the next revision of the driver will not change the format of the file or even the name of the file itself.  For this reason, we cannot support accessing or parsing information from this file as part of your application.

However, you can create items in Measurement and Automation Explorer to gain access to most channel/module configuration information using the FieldPoint API.  The only exceptions are custom scaling information and channel ranges.  To get channel range information, you can use a supported PSP call with the DatasSocket VIs.  Unfortunately, there is no supported way to programmatically access custom scaling configurations.  This information is stored in the fpbank.ini file, but if you chose to access this file, understand that your application may not function correctly with future releases of the FieldPoint driver.

If you feel that this is something that should be supported by the FieldPoint API, submitting a Product Suggestion here will make R&D aware of this.  Our R&D group reviews all product suggestions   I will also file an internal product suggestion, but I highly recommend that you file one as well.

If you have other questions or concerns, feel free to post them here, and I will respond as soon as possible.

Regards,

Nadim
Applications Engineering
National Instruments