Page Comparison

• Prepared by a network integrator, or created automatically during device discovery
  
  

• BACnet must first be enabled using the Add a BACnet Interface before importing files
  
  

• CSV format

See (Optional) Creating a BACnet Device Interface (XIF) Definition.

.ENO or eno
(cannot use .eno.csv)

• Requires EnOcean driver to be enabled. See (Optional) Add a Local EnOcean Interface.
  
  

• CSV format

See (Optional) Creating a Local EnOcean Device Interface (XIF) Definition.

• Requires EnOcean driver to be enabled. See (Optional) Add a Remote EnOcean Interface for SmartServer IoT.
  
  

• CSV format

See (Optional) Creating a Remote EnOcean Device Interface (XIF) Definition.

LON XIF definition

• Provided by the device manufacturer, or created by the LON Compiler (NodeBuilder) or by NodeUtil

See (Optional) Creating a LON Device Interface (XIF) Definition

• 
  
• If the device uses custom resource files set, then you will also need to convert the resource files set to .xml files and import them into the SmartServer prior to importing the .xif file, or as part of a .dtp file with both the .xml and .xif files.

See (Optional) Creating a LON Device Interface (XIF) Definition.

See (Optional) Creating IAP Resource Definitions (XML)

BACnet device interface (XIF) definition

.

LoRaWAN XIF definition

• Requires a LoRaWAN Gateway to be set up, the LoRaWAN driver to be enabled, and ChirpStack to be installed. See (Optional) Add a LoRaWAN Interface or (Optional) Add a LoRaWAN Interface for SmartServer Pi (Release 4.2) depending on your environment.
  
  
• The base name is the part of the XIF filename that precedes the extension.
  • Example: if the XIF filename is NetvoxR712V2.LoRaWAN, then the base name is NetvoxR712V2 and the extension is .LoRaWAN. 
  • If NetvoxR712V2.LoRaWAN and NetvoxR712V3.LoRaWAN are identical in content including the program ID, then they will be treated as two different XIFs because of the different XIF filenames.
    
    
• The filename must match the device profile name in ChirpStack.
  
  

• CSV format

See (Optional) Creating a BACnet LoRaWAN Device Interface (XIF) Definition

Modbus device interface (XIF) definition 

.

Modbus XIF definition

• Prepared by a network integrator
  
  

• CSV format

• Valid extension: .mod (cannot use .mod.csv)

See (Optional) Creating a Modbus Device Interface (XIF) Definition.

Neuron firmware or application image file for a LON device that supports downloadable firmware

• Supplied by LON device manufacturers, or automatically produced by your development tools if you are developing LON devices

• Valid extension: .apb

See Collecting or Creating Device Definitions.

BACnet type mapping definition

• Allows BACnet tools to see non-BACnet devices (e.g., LON, Modbus)

  • Provides a BACnet interface to any field devices available on your SmartServer, independent of the protocols used to communicate with the devices

  • Provides a customized BACnet interface to BACnet devices provisioned on the SmartServer
    
    

• Prepared by a network integrator
  
  

• BACnet must first be enabled using the Add a BACnet Configuration pageInterface before importing files
  
  

• CSV format

• Valid extension: .btm (cannot use .btm.csv)

See (Optional) Setting up BACnetSee Add a BACnet Interface.

Datapoint logging and alarming definition

• Defines the initial value, logging, and alarming requirements for datapoints
  
  

• Created manually or using the CMS Datapoint Properties widget
  
  

• CSV format
  Valid extension: .dla

See Defining Datapoint Properties.

Device type definition 

• Lists the device type names, program identifier (ID), application image names, and graphics assets to be used as icons for specified device types
  
  

• Created using the CMS Device Types widget
  
  

• CSV format
  Valid extension: .dtd

See Defining Device Types.

Connection definitions

• Define connection templates that specify how datapoint outputs are connected to datapoint inputs
  
  

• CSV format

• Valid extensions: .con, .csv, .con.csv

See Setting up Datapoint Connections.

Graphics file

• Customizes the image displayed for a device type

• Valid extensions: .jpg, .png
  (.jpg extensions are interpreted as jpeg files)

See Collecting or Creating Device Definitions.

• Define a "sequence of operations" (i.e., flows) and dashboards to automate everyday tasks
  
  

• Create instrument panels and dashboards for visualization
  

• Valid extension: .json

See Creating Sequence of Operations and SmartServer IoT Node-RED Tutorial.

Device type package

• Provides a single-file package that contains multiple files for defining device types and datapoint properties in a single step using the CMS Devices widget
  
  

• Created using the Export feature on the Device Types widget
  
  

• ZIP format
  Valid extensions: .dtp,  .gdtp, .zip, .gzip, .dtp.zip

See Defining Device Types.

• Provides a file defining the datapoint properties (such as device, block, block index, datapoint, datapoint XIF name, datapoint type, and so on)
  
  

• Can be used to change the datapoint type

• Valid extension: .data.csv

See Modifying Datapoint Types.

SmartServer software update/reimage

• SmartServer software file used for system update or re-imaging performed using the SmartServer console or System Configuration UI
  
  

• You can download the files from the Flash Drive Image links provided in the SmartServer IoT Release Notes section
  Valid extension: .zip

See Updating with the SmartServer Console and Updating with the SmartServer Configuration Page.

SmartServer software update

• SmartServer software file used for system updates performed through the SmartServer CMS
  
  

• Points to the .glpi file, which controls update process
  
  

• Files may be downloaded from the Software Downloader links provided in the SmartServer IoT Release Notes section
  Valid extension: .glpo

See Updating using the SmartServer CMS.

SmartServer software update

• SmartServer software file used for system updates performed using the SmartServer CMS
  
  

• Controls the update process
  Valid extension: .glpi

See Updating using the SmartServer CMS.

SmartServer system backups

• File creation date is included in the name in the following format: SmartServer-System-Backup-yyyy-mm-dd-hhmmss.tgz
  Valid extension: .tgz

See Backing Up, Restoring, and Cloning the SmartServer.

SmartServer database backups

• File creation date is included in the name in the following format: SmartServer-DB-Backup-yyyy-mm-dd-hhmmss.zip
  Valid extension: .zip

See Backing Up, Restoring, and Cloning the SmartServer.

Software executable

• Contains a software program
  

• Valid extension: .exe

.tar.gz

.deb

SmartServer Pi software file used for system installation or update

See Installing SmartServer Pi and Updating the SmartServer Pi.