The IAP feature (Settings widget) is available with SmartServer 3.2 Update 2 and higher. Prior to SmartServer 4.2, IAP was called IAP Settings.
...
| Anchor | ||||
|---|---|---|---|---|
|
| System Update | Datapoint Naming Operation |
| 2.90 to 3.25 | If you have a SmartServer IoT that is from the factory (out-of-the-box), there are no device types and therefore, no existing datapoint names. You will first need to re-image or update the SmartServer to 3.2 Update 2. At this point, the system will use IAP names. If you prefer to use legacy names (for example, in case you have existing DLA files containing legacy names), then you can use the CMS Settings widget to switch to legacy names (see Switching to Legacy Names) for any future devices that are added. |
3.10 to 3.25 | If you have a SmartServer 3.1 system that has devices using legacy names (any mixture of LON, BACnet and Modbus), and you update to 3.2 Update 2, then the SmartServer will continue to use legacy names for all existing devices and any devices created using SmartServer 3.2 Update 2. This behavior cannot be modified. |
| 3.20 to 3.25 | If you have a SmartServer 3.2 system that has devices using IAP names (any mixture of LON, BACnet and Modbus), and you update to 3.2 Update 2, then the SmartServer will continue to use IAP names for all existing devices and any devices created using SmartServer 3.2 Update 2. This behavior cannot be modified. |
| Reset of 3.2 Update 2 and higher | If you have a SmartServer 3.2 Update 2 system using either legacy or IAP names, and you perform a Reset to Defaults using the System Configuration page (databases or factory reset), then IAP names will be in effect. However, since there are no device types, you can use the CMS Settings widget to switch to legacy names (see Switching to Legacy Names) . |
Naming Considerations for BACnet XIF and Modbus XIF Files
Before creating or editing BAC or MOD files, consider the following:
- Datapoint names in the BAC or MOD file need to be a maximum of 12 characters.
Datapoints with an underscore ( _ ) require a workaround.
Dynamic datapoints with underscores ( _ ) in the name (e.g., DO_0) cannot be added in IzoT CT. In these cases, IzoT CT will strip off the _0 and display DO. Moreover, if you edit the datapoint and and rename it to DO_1, IzoT CT will display the new name, however the SmartServer CMS will maintain the original name. That is, the SmartServer does not have any visibility to dyname datapoint name changes in IzoT CT. In order to add a datapoint name such as DO_0, you will need to add DO_0 with a count of two thats shows DO_0 and DO_1 in the Functional Block (FB), and then delete DO_1.- If you are using shadowConnect.exe (located in the SmartServer GitHub repository), then you need to use device/0 for the {blockName}/{blockIndex} in order to have a connection (CON) file created automatically for you. If you are not using shadowConnect.exe, then you can use any {blockName}/{blockIndex}.
- Once the BACnet and Modbus devices have been provisioned, you can use localDev.exe (from the SmartServer GitHub repository) in order to add an internal device (dyn-1) to access the BACnet or Modbus datapoints.
- Mapping must then be added for LON datapoints to dyn-1 as follows:
- Using IzoT CT, add a single web server FB, or a web server FB for each BACnet or Modbus device, and change the web server FB name to match the device name.
- Using IzoT CT, add dynamic datapoints for all BACnet or Modbus datapoints that you want to access in IzoT CT.
- If you are going to use the same datapoints on multiple SmartServers, then consider creating an IzoT CT stencil for the dyn-1 internal device.
- Manually create a SmartServer connection (CON) file, use shadowConnet.exe, or write an App for dyn-1 to map the LON datapoints to the respective BACnet or Modbus datapoints. In order to manually create the connections file, get the datapoint path from the Datapoints widget details view.
Switching to Legacy Names
...
- Open the SmartServer CMS Settings widget.
- Click IAP.
The IAP settings view appears.
- Enable Use Legacy Datapoint Names.
- Click Save.