...
Device interface definition files, such as exampledevice.xif, should be copied to the /res/ sub-directory specified in the configuration file above. As mentioned in IDL Driver File Locations, the SmartServer IoT’s CMS does not currently copy custom device interface definition files automatically into the custom driver resource directory if the file is imported into the CMS using the Device Types widget (LUM-7757). This example device interface file includes the definition for a simulated device that contains four, simple counter data points. There are certain data point property columns that are mandatory to include in a custom device interface file, which includes the DataPoint Name, IAP Type, Write Enable, & Address columns. Details on these mandatory column properties can be found in Collecting or Creating Device Definitions. Drivers to other protocols may need additional columns to define all of the necessary properties required to access data points using these custom protocols. Custom columns can be added to the definitions for datapoints in a device interface definition file as shown in the example below, however the SmartServer does not currently pass these custom parameters to the driver itself via the device create callback function (AP-7698). For reference, see the *xif_dp_array parameter in the device create callback function described in /wiki/spaces/DrftSSIoT/pages/1477491Device Create Functions.
| Code Block | ||
|---|---|---|
| ||
#filetype,example_xif #program_ID,9B0001050004EC00 #manufacturer,EnOcean #description,exampledevice xif Datapoint Name,IAP Type,Write Enable,Address,Myfield1,Myfield2 Counter_A,SNVT_count,-,0,F6,02 Counter_B,SNVT_count,-,1,F6,02 Counter_C,SNVT_count,-,2,F6,02 Counter_D,SNVT_count,-,3,F6,02 |
...