...

• SmartServer IoT Software Downloader (see Updating with the SmartServer CMS)

• SmartServer Pi Software Downloader (see Install SmartServer Pi)

• SmartServer Remote CMS (see Local CMS vs. Remote CMS)

• IzoT Net Export Utility (see Importing LON Devices from an LNS Network)

• SmartServer IoT Flash Drive Image (see Updating with the SmartServer Configuration Page and Updating with the SmartServer Console)

• SmartServer XIF File (see (Optional) Creating a LON Device Interface (XIF) Definition)

• SmartServer Lock Code Generator (for offline activation; see Activating Capacity Licenses Offline Using the License Customer Portal)

• IOX I/O Expansion Module (see IOX I/O Expansion Module)

• Example Applications, Drivers, and Web Pages (see SmartServer IoT Developer's Guide)

• SmartServer Custom Driver Template

Changes: 

• TBDAccelerate device discovery with a new capability to select the protocols for the SmartServer to use for discovery. By default, the available protocols supporting discovery are BACnet, EnOcean, LON, LoRaWAN, and Modbus. Once you start discovery, you now see a summary of how long discovery has been active for each of your selected protocols, and you can now request the SmartServer to stop waiting for discovery to complete before going on to other tasks. See Discovering, Defining, or Importing Devices for more information. (AP-13036)

• The OpenJDK, PostgreSQL JDBC, OAuth, and SAML software components have been updated to address security vulnerabilities in the earlier versions. (AP-13188, AP-13499)

• Simplify datapoint logging setup with new default log parameters. (AP-12779)

• SmartServer Pi now notifies you to change firewall configuration of your host when you enable BACnet. (AP-12963)

• The following problems have been fixed:

  • In some cases, if you provisioned a LON device the provisioning failed if the device was on the far side of a LON router. (AP-13691)

  • In some cases, the CMS restarted multiple times after updating or re-imaging the SmartServer. (AP-13509)

Warnings: 

• TBD

• For additional warnings, see SmartServer 4.3 Update 1.

...

• You can update an installed SmartServer running an earlier release of the SmartServer software to the 3.2 Update 2 release.  However, you cannot go back without clearing all devices out of the SmartServer.  If you attempt to load an earlier version of the SmartServer software on a SmartServer with 3.2 Update 2 and provisioned devices, the earlier software is not compatible with the 3.2 Update 2 database and will fail to run.  Always backup your SmartServer prior to updating it to the 3.2 Update 2 software.  If you have to go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page.  Links to prior releases are available on this page. (LUM-8271)

• In some cases, the SmartServer 3.2 Update 2 software will fail to run on SmartServer hardware with a dual core processor.  You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that is not compatible with this release. 

• IzoT CT 4.2 or a newer version, or IzoT Net Server 4.2 or a newer version, is required to use the IzoT Net Export Utility.

• The SmartServer may fail to communicate with LON devices when using LON independent management mode (IMM) and changing a SmartServer network interface after importing an IzoT Net Server or LNS database. If you lose communication with LON devices in IMM after changing a network interface, backup your SmartServer and then reset your databases as described in Resetting the SmartServer to Factory Defaults. (AP-8563)

• If your SmartServer has any BACnet devices with a discovered device interface (XIF) and you export your device types using the Settings button or the Devices Widget Export action, your discovered BACnet XIF will not be included in the export.  You can get a copy of the discovered XIF in the BACnet XIF file with a BAC extension in the /var/apollo/data/bacnetrouter/res directory on your SmartServer. (LUM-8265)

• You cannot include leading zeros in the device unique ID (UID) and the BACnet object instance numbers that you specify in the BACnet XIF (BAC) file.  The CMS will accept the definitions, but some operations will fail due to the leading zeros. (AP-8018)

• You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events.  You can update IAP input datapoints (which are the same as BACnet output datapoints).  This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)

• In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned.  You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)

• In some cases, the CMS displays stale data after you make a change.  If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers).  If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)

• The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB.  For optimal performance, keep logged data below 100 MB.  The SmartServer includes a 32 GB SD card.  You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB.  The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration.  You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance.  If required, you can free up space on the SD card by deleting backups.  To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)

• If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.

SmartServer IoT 3.2 Update 1

...

• Limited testing has been completed for this release.  The fix for routing 222-byte LON NVs has been verified, but there has been no regression testing completed for this update.  If you are looking for a fully tested stable release, use SmartServer 3.2.

• You can update an installed SmartServer running an earlier release of the SmartServer software to the 3.2 release.  However, you cannot go back without clearing all devices out of the SmartServer.  If you attempt to load an earlier version of the SmartServer software on a SmartServer with 3.2 and provisioned devices, the earlier software is not compatible with the 3.2 database and will fail to run.  Always backup your SmartServer prior to updating it to the 3.2 software.  If you have to go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page.  Links to prior releases are available on this page. (LUM-8271)

• In some cases, the SmartServer 3.2 Update 1 software will fail to run on SmartServer hardware with a dual core processor.  You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that is not compatible with this release. 

• The source of datapoint names has changed with this release to make the names easier to understand and recognize.  If you update a SmartServer with a prior release, the datapoint names may change for any new devices you install, whereas they will stay the same for devices you installed with the previous release.  Both sets of names will appear in the CMS Datapoint Properties widget, but only the new names will work for any new devices you install.  To simplify system maintenance, redefine your datapoint properties, calendar events, and Sequencing widget flows to use the new datapoint names.

• You cannot use the apollo-reset command from the SmartServer console.  The command is available from the console, but if you enter the command your SmartServer may fail or become corrupted.  To reset the SmartServer database, or to return a SmartServer to factory defaults, follow the procedure at Resetting the SmartServer to Factory Defaults. (AP-8427)

• You cannot view logged data in the CMS Datapoint Browser.  Logged data is available to custom applications and web pages that use IAP/REST or IAP/WS to view the data log contents. (LUM-8529)

• You cannot include leading zeros in the device unique ID (UID) and the BACnet object instance numbers that you specify in the BACnet XIF (BAC) file.  The CMS will accept the definitions, but some operations will fail due to the leading zeros. (AP-8018)

• You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events.  You can update IAP input datapoints (which are the same as BACnet output datapoints).  This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)

• If you create a calendar event with a sunset or sunrise time, in some cases you will not be able to edit the event after you create it.  If you cannot change an event that requires a change, delete the event and create a new one with your desired changes. (LUM-8268)

• In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned.  You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)

• If your SmartServer has any BACnet devices with a discovered device interface (XIF) and you export your device types using the Settings button or the Devices Widget Export action, your discovered BACnet XIF will not be included in the export.  You can get a copy of the discovered XIF in the /var/apollo/data/bacnetrouter/res directory on your SmartServer. (LUM-8265)

• In some cases, the CMS displays stale data after you make a change.  If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers).  If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)

• The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB.  For optimal performance, keep logged data below 100 MB.  The SmartServer includes a 32 GB SD card.  You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB.  The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration.  You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance.  If required, you can free up space on the SD card by deleting backups.  To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)

• If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.

SmartServer IoT 3.2

Release Date: May 19, 2021

...

• You can update an installed SmartServer running an earlier release of the SmartServer software to the 3.2 release.  However, you cannot go back without clearing all devices out of the SmartServer.  If you attempt to load an earlier version of the SmartServer software on a SmartServer with 3.2 and provisioned devices, the earlier software is not compatible with the 3.2 database and will fail to run.  Always backup your SmartServer prior to updating it to the 3.2 software.  If you have to go back to an earlier release, either restore one of your backups with the earlier release, or re-image your SmartServer with a clean version of the earlier release as described in Updating with the SmartServer Configuration Page.  Links to prior releases are available on this page. (LUM-8271)

• In some cases, the SmartServer 3.2 software will fail to run on SmartServer hardware with a dual core processor.  You can determine which processor you have by reading the label on the bottom of the SmartServer. The serial number printed under the product name includes one letter. If the letter is F or later, you have a quad core processor. If the letter is A through E, you have a dual core processor that is not compatible with this release. 

• The source of datapoint names has changed with this release to make the names easier to understand and recognize.  If you update a SmartServer with a prior release, the datapoint names may change for any new devices you install, whereas they will stay the same for devices you installed with the previous release.  Both sets of names will appear in the CMS Datapoint Properties widget, but only the new names will work for any new devices you install.  To simplify system maintenance, redefine your datapoint properties, calendar events, and Sequencing widget flows to use the new datapoint names.

• You cannot use the apollo-reset command from the SmartServer console.  The command is available from the console, but if you enter the command your SmartServer may fail or become corrupted.  To reset the SmartServer database, or to return a SmartServer to factory defaults, follow the procedure at Resetting the SmartServer to Factory Defaults. (AP-8427)

• You cannot view logged data in the CMS Datapoint Browser.  Logged data is available to custom applications and web pages that use IAP/REST or IAP/WS to view the data log contents. (LUM-8529)

• You cannot include leading zeros in the device unique ID (UID) and the BACnet object instance numbers that you specify in the BACnet XIF (BAC) file.  The CMS will accept the definitions, but some operations will fail due to the leading zeros. (AP-8018)

• The SmartServer LON IP-852 router will not work with LON datapoints with a size larger than 198 bytes. (AP-8426)

• You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events.  You can update IAP input datapoints (which are the same as BACnet output datapoints).  This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)

• If you create a calendar event with a sunset or sunrise time, in some cases you will not be able to edit the event after you create it.  If you cannot change an event that requires a change, delete the event and create a new one with your desired changes. (LUM-8268)

• In some cases, when you create a connection between two LON datapoints, the devices involved in the connection may be deprovisioned.  You can recover by reprovisioning the devices after they become deprovisioned. (AP-8360)

• If your SmartServer has any BACnet devices with a discovered device interface (XIF) and you export your device types using the Settings button or the Devices Widget Export action, your discovered BACnet XIF will not be included in the export.  You can get a copy of the discovered XIF in the /var/apollo/data/bacnetrouter/res directory on your SmartServer. (LUM-8265)

• In some cases, the CMS displays stale data after you make a change.  If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers).  If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7145, AP-7677)

• The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB.  For optimal performance, keep logged data below 100 MB.  The SmartServer includes a 32 GB SD card.  You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB.  The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration.  You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance.  If required, you can free up space on the SD card by deleting backups.  To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)

• If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.

SmartServer IoT 3.1 Update 3 Beta

...

• Software Downloader (see Updating with the SmartServer CMS)

• IzoT Net Export Utility (see Importing LON Devices from an LNS Network)

• Flash Drive Image (see Updating with the SmartServer Configuration Page and Updating with the SmartServer Console)

• SmartServer IoT XIF File (see (Optional) Creating a LON Device Interface (XIF) Definition)

• Example Applications, Drivers, and Web Pages (see SmartServer IoT Developer's Guide)

Changes:

• Added configuration option to disable IP-852 CRC checking for compatibility with IP-852 devices and routers that do not implement IP-852 CRC checking such as devices based on the Niagra platform. (AP-7776, AP-8115)

• Added Linux kernel support required for OpenVPN installation. (AP-8135)

• Bug fixes and performance improvements, including the following:

  • Improved detection of device failure and reporting of devices that recover from failure. (AP-8035, AP-8141, AP-8142, AP-8155, AP-8159, AP-8160, AP-8171, AP-8173, AP-8184, AP-8192)

  • Fixed problems with provisioning and monitoring LON PL device devices when PL repeating is enabled. (AP-8023, AP-8048, AP-8058, AP-8073, AP-8127, AP-8139, AP-8152, AP-8161, AP-8182)

  • Improved BACnet COV performance. (AP-8027)

  • Improved IOX configuration from the CMS Datapoint Browser (LUM-8001)

  • Node-RED nodes were sometimes deleted when updating the SmartServer software (AP-8153)

  • In some cases, calendar events could not be created that ended at midnight or were less than one hour. (LUM-7890, LUM-7891, LUM-7894)

Warnings:

• You cannot include leading zeros in the device unique ID (UID) and the BACnet object instance numbers that you specify in the BACnet XIF (BAC) file.  The CMS will accept the definitions, but some operations will fail due to the leading zeros. (AP-8018)

• Automatic application image loading for field devices may fail if you use the manual option to create the device and the program ID in the device does not match the program ID specified for the device interface.  You can use automatic application image loading with guided device discovery. (AP-8026)

• You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from calendar events.  You can update IAP input datapoints (which are the same as BACnet output datapoints).  This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)

• Historical data logs may contain adjacent duplicate entries when you specify the option to only log values after a change in value. (LUM-7831)

• In some cases, the CMS displays stale data after you make a change.  If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers).  If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7107, LUM-7104, LUM-7145, AP-7677)

• The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB.  For optimal performance, keep logged data below 100 MB.  The SmartServer includes a 32 GB SD card.  You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB.  The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration.  You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance.  If required, you can free up space on the SD card by deleting backups.  To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)

• If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.

SmartServer IoT 3.1

Release Date: December 23, 2020

...

• Software Downloader(see Updating with the SmartServer CMS)

• IzoT Net Export Utility (see Importing LON Devices from an LNS Network)

• Flash Drive Image (see Updating with the SmartServer Configuration Page and Updating with the SmartServer Console)

• SmartServer IoT XIF File (see (Optional) Creating a LON Device Interface (XIF) Definition)

• Example Applications, Drivers, and Web Pages (see SmartServer IoT Developer's Guide)

Changes:

• Added beta support for event-driven monitoring of BACnet devices using BACnet COV.

• Added beta support for event-driven updates from the SmartServer BACnet Server to BACnet workstations and other BACnet clients.

• Added Docker support. (AP-7848)

• Added support for custom names for BACnet datapoints defined in the BACnet XIF (BAC) file.

• Bug fixes and performance improvements, including the following:

  • Provisioning a Modbus device with incorrect Modbus register specifications sometimes caused a cryptic error message to be reported to the user. (AP-7924)

  • Importing a LON XIF file with an integer XIF version number failed.  (AP-7915)

Warnings:

• If you use the beta BACnet COV support in the SmartServer BACnet Server to subscribe to a SmartServer BACnet Server datapoint from a BACnet workstation, COV updates may be delayed by up to one minute, (AP-8027)

• You cannot include leading zeros in the device unique ID (UID) and the BACnet object instance numbers that you specify in the BACnet XIF (BAC) file.  The CMS will accept the definitions, but some operations will fail due to the leading zeros. (AP-8018)

• Automatic application image loading for field devices may fail if you use the manual option to create the device and the program ID in the device does not match the program ID specified for the device interface.  You can use automatic application image loading with guided device discovery. (AP-8026)

• You cannot update IAP output datapoints (which are the same as BACnet input datapoints) from schedule events.  You can update IAP input datapoints (which are the same as BACnet output datapoints).  This includes writes to BACnet inputs such as BACnet AI and BI objects. (LUM-7839)

• Historical data logs may contain adjacent duplicate entries when you specify the option to only log values after a change in value. (LUM-7831)

• In some cases, the CMS displays stale data after you make a change.  If a datapoint value, context, preset, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers).  If you are using the CMS Datapoint Browser, you can click the Refresh button in the upper right corner of the widget. (LUM-7107, LUM-7104, LUM-7145, AP-7677)

• The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB.  For optimal performance, keep logged data below 100 MB.  The SmartServer includes a 32 GB SD card.  You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB.  The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration.  You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance.  If required, you can free up space on the SD card by deleting backups.  To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)

• If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.

• You cannot install more than a total of five network interfaces (U60 or U70) and IOX modules in a single SmartServer.  If you have five total, or if you have four and require a spare USB port, use a powered USB 3.0 compliant hub and plug all the U60 and U70 network interfaces into the hub.  Always plug any IOX modules directly into the SmartServer and do not plug them into a hub.

...

• Software Downloader(see Updating with the SmartServer CMS)

• IzoT Net Export Utility (see Importing LON Devices from an LNS Network)

• Flash Drive Image (see Updating with the SmartServer Configuration Page and Updating with the SmartServer Console)

• SmartServer IoT XIF File (see (Optional) Creating a LON Device Interface (XIF) Definition)

• Example Applications, Drivers, and Web Pages (see SmartServer IoT Developer's Guide)

Changes:

• BACnet support enhancements and fixes

  • Device discovery for the BACnet Client

  • Multi-state object support for the BACnet Server

  • Scheduler and Calendar object support for the BACnet Server

  • Intrinsic reporting for the BACnet Server

  • IAP block naming for the BACnet Client

  • Multi-protocol support for connections with BACnet datapoints

• OPC UA override support

• Simplified custom driver support with a new IAP Driver Library (IDL)

• STIG compliance improvements

• OAuth authentication support

• The following beta features have been released and are no longer in beta:

  • BACnet client for interfacing with BACnet/IP devices

  • IOX I/O Expansion Module support for adding digital I/O, relay outputs, and metering inputs to the SmartServer

  • CMS Sequencing widget

Warnings:

• If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.

• You cannot install more than a total of five network interfaces (U60 or U70) and IOX modules in a single SmartServer.  If you have five total, or if you have four and require a spare USB port, use a powered USB 3.0 compliant hub and plug all the U60 and U70 network interfaces into the hub.  Always plug any IOX modules directly into the SmartServer and do not plug them into a hub.

• The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB.  For optimal performance, keep logged data below 100 MB.  The SmartServer includes a 32 GB SD card.  You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB.  The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration.  You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance.  If required, you can free up space on the SD card by deleting backups.  To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)

• In some cases, the CMS displays stale data after you make a change.  If a datapoint value, context, or other value is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). (LUM-7107, LUM-7104, AP-7677)

• When you edit a preset value in the CMS Datapoint Properties with a localization rule, the CMS may save a slightly different value than the value you entered. For example, if you enter 35 for a preset value, the CMS may store 35.1 instead of 35. (LUM-7315)

...

• Software Downloader (see Updating with the SmartServer CMS)

• IzoT Net Export Utility (see Importing LON Devices from an LNS Network)

• Flash Drive Image (see Updating with the SmartServer Configuration Page and Updating with the SmartServer Console)

• SmartServer IoT XIF File (see (Optional) Creating a LON Device Interface (XIF) Definition)

• Example Applications, Drivers, and Web Pages (see SmartServer IoT Developer's Guide)

Changes:

• Quad core support!  Starting with Revision F of the SmartServer IoT, all SmartServer IoTs now include a quad core ARM processor.  Earlier SmartServer IoTs included a dual core processor.  The result is better performance at the same price.  You can now monitor up to 40 events per second with the new quad core hardware–the dual core hardware was limited to 20 events per second.  You can determine which processor you have by reading the label on the bottom of the SmartServer.  The serial number printed just under the product name includes one letter.  If the letter is F or later, you have a quad core processor.  If the letter is A through E, you have a dual core processor.  Starting with SmartServer 2.9 software, the software supports both the dual core and quad core versions.  Older versions of the SmartServer software will not work on the quad core hardware.

• The performance warning threshold in the CMS Datapoint Properties has been increased from 20 events per second to 40 events per second due to the higher performance of the quad core SmartServer.

• The following beta features introduced in previous releases are still in beta:

  • BACnet client for interfacing with BACnet/IP devices.

  • IOX I/O Expansion Module support for adding digital I/O, relay outputs, and metering inputs to the SmartServer.

  • CMS Sequencing widget

• Bug fixes and performance improvements, including the following:

  • Changing the SmartServer hostname sometimes resulted in an unexpected This Site Can't be Reached error message. (AP-7470)

  • Secure browsing sometimes failed when you enabled signed security certificates. (LUM-7437)

  • Updates sometimes failed if you have a large amount of data log data on your SD card. (LUM-6493)

  • On-demand monitoring sometimes failed with BACnet devices. (AP-7568)

  • Datapoints were not consistently sorted in the CMS Datapoint Properties. (LUM-7376)

  • Datapoint value localization was sometimes disabled when it should have been enabled. (LUM-7370)

  • The CMS Devices Test command sometimes returned an incorrect result for BACnet or Modbus devices. (AP-6239)

Warnings:

• If you are using an IOX I/O Expansion Module, always plug the IOX into a USB port on the SmartServer instead of port on a USB hub.

• You cannot install more than a total of five network interfaces (U60 or U70) and IOX modules in a single SmartServer.  If you have five total, or if you have four and require a spare USB port, use a powered USB 3.0 compliant hub and plug all the U60 and U70 network interfaces into the hub.  Always plug any IOX modules directly into the SmartServer and do not plug them into a hub.

• The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB.  For optimal performance, keep logged data below 100 MB.  The SmartServer includes a 32 GB SD card.  You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB.  The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration.  You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance.  If required, you can free up space on the SD card by deleting backups.  To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)

• In some cases, the CMS displays stale datapoint values and context information.  If a datapoint value or context is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). (LUM-7107, LUM-7104)

• If all the widgets in the CMS disappear from your CMS dashboard, click any widget name in the list of widgets on the left side of the dashboard. (LUM-7324)

• When you edit a preset value in the CMS Datapoint Properties with a localization rule, the CMS may save a slightly different value than the value you entered. For example, if you enter 35 for a preset value, the CMS may store 35.1 instead of 35. (LUM-7315)

• When you modify a preset value or localization rule in the Datapoint Properties, click the Refresh button in the upper right of the Datapoint Browser to activate the change. (LUM-7145)

• In some cases, connections to BACnet devices do not function correctly. (AP-5906)

...

• Software Downloader (see Updating with the SmartServer CMS)

• IzoT Net Export Utility (see Importing LON Devices from an LNS Network)

• Flash Drive Image (see Updating with the SmartServer Configuration Page and Updating with the SmartServer Console)

• SmartServer IoT XIF File (see (Optional) Creating a LON Device Interface (XIF) Definition)

• Example Applications, Drivers, and Web Pages (see SmartServer IoT Developer's Guide)

Changes:

• Modbus device discovery has been added.  To discover a Modbus device, you must have a Modbus XIF file with markers that identify fixed datapoints that the SmartServer can use to identify the device.

• A new Planning widget has been added that simplifies organization of large systems by allowing you to define campus, building, area, and room contexts.

• You can now set an override priority when updating a datapoint value in the CMS Datapoint Browser.  If you update a datapoint on a BACnet device, the SmartServer updates the priority array on the device if the device has a writable priority array. (AP-7221)

• The connection (CON) file format has changed. Leave the Area Scope, and Zone Scope fields blank in when specifying a Device Name.

• Defining monitoring for a datapoint in either the Datapoint Properties widget or the Datapoint Properties (DLA) file has been simplified with a new Monitored property. (LUM-7054)

• You can now specify the polling interval from the Datapoint Properties widget or a Datapoint Properties (DLA) file using the same method for BACnet, LON, and Modbus devices.  Previously, the polling interval for a BACnet device had to be specified in the BACnet XIF (BAC) file. (AP-5769)

• Documentation has been added for using web sockets in custom web pages.

• The following new beta features are available with this release:

  • Sequencing and Web Page Builder – a new Sequencing widget is available in the CMS that you can use to build sequences of operation using the built-in Node-RED flow editing and web page design tool

  • Presets – you can now define and use presets.  A preset is a normalized value for a datapoint that you can use for scheduling, alarming, logging, displaying, and sequencing datapoint values from datapoints on devices with different data types, potentially using incompatible data types or using different transformation rules for the data types. 

  • Datapoint Localization – you can now define datapoint localization transformation to convert the SI units used by the SmartServer into Imperial units.  For example, you can use a localization rule to convert a temperature value reported in Celsius to a temperature value reported in Fahrenheit.

• The following beta features have been released and are no longer in beta:

  • OPC UA server for interfacing with OPC UA clients such as Wonderware InTouch – the number of datapoint subscriptions supported by the SmartServer OPC UA Server has been increased from 1000 datapoints to 10,000 datapoints. (AP-6824)

  • U70 PL support for interfacing with LON power line devices using the U70 PL interface with 3-phase PL coupler and power supply (the optional U70 PL USB Network Interface module is required)

  • CMS Calendar widget for scheduling events

• The following beta features introduced in previous releases are still in beta:

  • BACnet client for interfacing with BACnet/IP devices

  • IOX I/O Expansion Module support for adding digital I/O, relay outputs, and metering inputs to the SmartServer

• Bug fixes and performance improvements have been implemented for the BACnet Server, alarm management, and scheduling.

Warnings:

• You cannot change the host name for a SmartServer from the default.  Each SmartServer has a unique hostname printed on the bottom label.  Some operations will fail if you change the host name. (AP-6914, AP-7470)

• The SmartServer requires free space on the SD card for normal operation and requires logged data to be less than 8 GB.  For optimal performance, keep logged data below 100 MB.  The SmartServer includes a 32 GB SD card.  You can run out of free space on the SD card if you create many backups or retain too much data in the data log, and performance will degrade if the storage for logged data exceeds 100 MB, and will degrade significantly if the storage for logged data exceeds 8 GB.  The Datapoint Properties widget displays an estimate of how much SD card space will be required for logged data based on your data log configuration.  You can use this value to manage the space required for data logs and keep the size below 100 MB for best performance, or keep the size below 8 GB for acceptable performance.  If required, you can free up space on the SD card by deleting backups.  To delete backups from the SD card, see Managing the SmartServer SD Card. (LUM-7271)

• If you update your SmartServer from the CMS, the update may fail if you have a large amount of data log data on your SD card.  Back up your SmartServer before doing an update.  If the update fails, re-image your SmartServer from the console interface as described in Updating with the SmartServer Console. (LUM-6493)

• The Devices widget Test command may sometimes return an incorrect result for BACnet or Modbus devices. (AP-6239)

• The order of datapoints in the Datapoint Browser sometimes changes.  Verify you have the correct datapoint before changing a datapoint value. (LUM-7376)

• In some cases, the CMS displays stale datapoint values and context information.  If a datapoint value or context is not displayed as you expect, refresh your browser window (Ctrl-F5 in many browsers). (LUM-7370, LUM-7107, LUM-7104)

• If all the widgets in the CMS disappear from you CMS dashboard, click any widget name in the list of widgets on the left side of the dashboard. (LUM-7324)

• When you edit a preset value in Datapoint Properties with a localization rule, the saved value may be slightly different than the value you entered. For example, if you enter 35 for a preset value, the saved value may be 35.1. (LUM-7315)

• When you modify a preset value or localization rule in the Datapoint Properties, click the Refresh button in the upper right of the Datapoint Browser to activate the change. (LUM-7145)

• In some cases, connections to BACnet devices do not function correctly. (AP-5906)

...

• Software Downloader (see Updating with the SmartServer CMS)

• IzoT Net Export Utility (see Importing LON Devices from an LNS Network)

• Flash Drive Image (see Updating with the SmartServer Configuration Page and Updating with the SmartServer Console)

• SmartServer IoT XIF File (see (Optional) Creating a LON Device Interface (XIF) Definition)

• Example Applications, Drivers, and Web Pages (see SmartServer IoT Developer's Guide)

Changes:

• A new beta feature is available that simplifies replicating a SmartServer image to multiple SmartServers.  You can use this feature to create a golden image that you deploy to many SmartServers.

• Added support for power line LON devices, including support for power line devices with repeating functionality using the Enhanced LonTalk Proxy Protocol.  Peer-to-peer connections are not supported with Enhanced LonTalk Proxy Protocol repeating enabled.

• The default datapoint priority for events in the Calendar widget has been changed to the Normal priority.  This is the same priority used by the Datapoint Browser widget so you can override a scheduled event from the Datapoint Browser, and the next scheduled event will overwrite the override.  You can create override events in the Calendar by assigning a priority from 1 to 16.  You cannot override these higher priority events from the Datapoint Browser.

• The following changes were implemented for the IzoT Net Export Utility:

  • Support for both 32-bit and 64-bit Windows.

  • Support for IzoT Net networks with multiple SmartServers.  An exported subsystem can only contain one SmartServer.

  • Subnet and node IDs are now exported from the IzoT Net database to the SmartServer.

  • Virtual devices hosted on the SmartServer can now be placed in any subsystem in IzoT CT.

  • Export time has been reduced in some cases.

• Bug fixes and performance improvements, including fixes and improvements for the following:

  • The Reset to Defaults command on the SmartServer Configuration System webpage would corrupt the SmartServer if you entered the wrong password.

  • You could not change the filename of a previously imported BACnet, LON, or Modbus XIF file.

  • You could not modify a previously defined connection.

  • The BACnet client driver did not respond to on-demand poll requests.

  • External BACnet clients could not update datapoints published by the SmartServer.

  • Modbus device polling would fail if the device was was disconnected and re-connected.

  • Modbus devices would sometimes be reported as offline when they were online.

Warnings:

• You cannot change the host name for a SmartServer from the default.  Each SmartServer has a unique hostname printed on the bottom label.  Some operations will fail if you change the host name. (AP-6914)

• You can only enter an integer alarm limit as an integer value.  For example, you can enter 85 as a temperature alarm value, but you cannot enter 85.00. You can enter a fractional value as a fractional value.  For example, you can enter 85.5 as a temperature alarm value.  (LUM-6679)

• The OPC UA Server is limited to 1000 datapoints. (AP-6824)

• XIF file and device type names are case sensitive.  Do not create two XIF files or two device types with the same name but different case. (LUM-6554)

• Meta data in type files cannot contain spaces. (LUM-6312)

• In some cases, if you specify a stagger value in a Calendar event definition, the stagger will not be implemented. (AP-6546)

• In some cases, connections to BACnet devices do not function correctly. (AP-5906)

• Re-provisioning a de-provisioned BACnet device does not work sometimes. (AP-5742)

• The BACnet Server trending service is disabled.

• The BACnet Server scheduling service is read-only.

• You may see an unrecoverable error if you unplug an IOX device less than 15 seconds after powering it up.  To prevent this problem, always wait at least 15 seconds before unplugging an IOX. (AP-4986)

...

• Software Downloader (see Updating with the SmartServer CMS)

• IzoT Net Export Utility (see Importing LON Devices from an LNS Network)

• Flash Drive Image (see Updating with the SmartServer Configuration Page and Updating with the SmartServer Console)

• SmartServer IoT XIF File (see (Optional) Creating a LON Device Interface (XIF) Definition)

• Example Applications, Drivers, and Web Pages (see SmartServer IoT Developer's Guide)

Changes:

• Maximum sustained throughput has been improved by 250% – sustained throughput is now 40 events per second

• Device capacity has been increased to 1000 devices

• Released the Calendar widget introduced as a beta in 2.6; added support for scheduling based on sunrise and sunset

• Added LON device discovery to simplify provisioning of existing LON networks

• Added a pause/resume button to the Devices widget to temporarily pause background polling to reduce overhead during system provisioning

• Bug fixes and performance improvements, including the following:

  • IP-852 communication stopped when IP network communication was temporarily disrupted.

  • IP-852 port value was limited to 1500-1700.

  • CSV file metadata formatting was inconsistent. 

  • The Expected Interval value for a datapoint had to be set to a non-zero value to enable logging.

Warnings:

• The BACnet Server trending service is disabled.

• The BACnet Server scheduling service is read-only.

• CSV file metadata tags must be in a separate cell from the metadata values.  For example, the metadata tag to specify the file type for a file is #filetype, without quotes.  The metadata value to specify a Modbus XIF file is Modbus_xif, without quotes.  The metadata tag and the metadata value must be separated by a command.  For example, the complete metadata entry for a Modbus XIF file embedded in a CSV file is #filetype,Modbus_xif, with no quotes.  If you open the file in Excel, the tag and value will appear in two adjacent cells.  Be sure not to combine the two cells into one.  Some of the example CSV files from earlier releases incorrectly used quotes and must be updated for the 2.7 release.  

SmartServer IoT 2.6 Update 1

...