Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Downloads for the current stable release (SmartServer IoT 3.12) are available here:

...

SmartServer IoT 3.2

Release Date: 

Linux and Base Platform Component Versions:

...

 May 19, 2021

Versions:

  • SmartServer IoT Software: 3.20.119
  • IzoT Net Export Utility: 1.30.335
  • Platform
    • Ubuntu Linux: 20.04
    • Ubuntu kernel: 5.4
    • Node.js: 14
    • Java

...

    • VM

...

    • : 11
    • Python: 3.8
    • PHP: 8.0
    • NginX: 1.18.0

Versions: 

Downloads: 

Changes: 

Warnings: 

SmartServer IoT 3.1 Update 3 Beta

Release Date: March 9, 2021 (beta release)

Versions:

  • SmartServer IoT Software: 3.14.004
  • IzoT Net Export Utility: 1.30.335

Downloads:

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:

...

 

  • The Ubuntu Linux operating system on the SmartServer has been updated to version 20.04.  Several platform components such as the Node.js, Java VM, Python, and PHP components have also been updated.  The Release Notes now list the key platform component version numbers. (AP-8056 and AP-8057)
  • You can now discover BACnet devices without first creating a BACnet device interface (XIF) file.  When the SmartServer discovers a BACnet device, if a BACnet XIF file does not already exist for the device, the SmartServer automatically uploads the BACnet XIF definition from the BACnet device. (AP-5210 and AP-7550)
  • You can now modify a device interface (XIF) definition that you have created for a BACnet or Modbus device.  For example, you can change or delete a block or datapoint on a provisioned device to correct or enhance the original device interface definition. (AP-8067)
  • Datapoint naming in the user interface and programming APIs has been updated to improve consistency and usability.  (LUM-7848)
  • Errors generated and reported by the SmartServer CMS are now included in the CMS Alarms widget to provide a single interface for viewing summary alarm status and for viewing and clearing alarms. (LUM-7870 and LUM-7877)
  • You can now disable IP-852 checksums to provide compatibility with third-party IP-852 routers and devices that do not correctly implement IP-852 checksums. (AP-7766)
  • The SmartServer uses the Ready LED to provide a visual indicator that the CMS is ready after initial startup. (AP-8061)
  • You can now load applications into LON devices where the application has a different program ID than the application already loaded in the device. (AP-8026)

Warnings: 

  • 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)
  • 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 SmartSever 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 Backup Files on the 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 and do not plug it into a USB hub.

SmartServer IoT 3.1 Update 3 Beta

Release Date: March 9, 2021 (beta release)

Versions:

  • SmartServer IoT Software: 3.14.004
  • IzoT Net Export Utility: 1.30.335

Downloads:

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 Backup Files on the 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 and do not plug it into a USB hub.

SmartServer IoT 3.1

Release Date: December 23, 2020

...

SmartServer IoT 2.6

Release Date: October 14, 2019

...