Page tree
Skip to end of metadata
Go to start of metadata
Dialog releases several updates per year of the SmartServer IoT software to add new functionality, enhance performance, and fix reported problems.  Due to high demand, the SmartServer IoT hardware is built in large production runs.  As a result, when you purchase a SmartServer IoT, it may not come with the latest version of the SmartServer software.  This page describes and provides download links for all the available SmartServer IoT software releases, with the most recent release at the top.  If you receive a new SmartServer IoT, you can compare the software version in your SmartServer IoT to the latest software release identified below.  To ensure you get the best performance and most stable operation, always update to the latest version of the SmartServer software.

Release Summary:

Current Release

Downloads for the current release are available here:

Descriptions and direct links for the current and previous releases are available in the following sections.

SmartServer IoT 3.0

Release Date: November 25, 2020

Versions:

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

Downloads:

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 and do not plug it into 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 Backup Files on the 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 (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)

SmartServer IoT 2.9

Release Date: August 28, 2020

Versions:

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

Downloads:

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

SmartServer IoT 2.8

Release Date: July 20, 2020

Versions:

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

Downloads:

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 Backup Files on the 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.  Backup 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 (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)

SmartServer IoT 2.7 Update 1

Release Date: March 31, 2020

Versions:

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

Downloads:

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)

SmartServer IoT 2.7

Release Date: December 1, 2019

Versions:

  • SmartServer IoT Software: 2.70.015
  • IzoT Net Export Utility: 1.20.280

Downloads:

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

Release Date: November 1, 2019

Versions:

  • SmartServer IoT Software: 2.61.005
  • IzoT Net Export Utility: 1.20.280

Downloads:

Changes:

  • SmartServer startup would fail if a custom application created a large number of IAP/MQ requests immediately at startup.  With this fix, it is still a good idea for custom applications, services, and drivers to throttle traffic during the first 5 minutes after startup.
  • The beta BACnet logger service caused logins to be locked out because it was using a fixed password of "ea888".  The beta BACnet logger has been disabled for this release to prevent lockouts.

Warnings:

SmartServer IoT 2.6

Release Date: October 14, 2019

Versions:

  • SmartServer IoT Software: 2.60.025
  • IzoT Net Export Utility: 1.20.147

Changes:

  • Added event-driven monitoring support for LON devices, in both the DMM and IMM LON management modes.
  • Added CMS and IAP/REST support for Zones and Groups.
  • The outgoing SMTP server used for alarm notifications is now configurable.  To use e-mail notification, you must first configure the SMTP server IP address and credentials.
  • Added the following new beta features:
    • BACnet client for interfacing with BACnet/IP devices
    • OPC UA server for interfacing with OPC UA clients such as Wonderware InTouch
    • U70 PL support for interfacing with LON power line devices using the U70 PL interface with 3-phase PL coupler and power supply
    • CMS Calendar widget for scheduling events
    • IOX I/O Expansion Module support for adding digital I/O, relay outputs, and metering inputs to the SmartServer
  • Bug fixes and performance improvements, including fixes for the following problems:
    • The Schneider PM5563, Schneider PM820, AMIK201 and WattNode Modbus definition files had an off-by-one error in the register numbers.
    • Problems could occur when polling multiple BACnet virtual devices.
    • Datapoint updates from the CMS Datapoint Browser did not work for a device exported by the IzoT Net Export utility if the device had Neuron firmware version 16 or older.
    • The device count would sometimes be incorrect if you imported devices exported by the IzoT Net Export utility multiple times, 
    • The CMS password was not changed if you changed the password from the Configuration web page.
    • Datapoint properties were not correctly updated if a DLA file was imported after Importing a device type package without the DLA file.

SmartServer IoT 2.5 Update 2

Release Date: August 30, 2019

Versions:

  • SmartServer IoT Software: 2.52.002
  • IzoT Net Export Utility: 1.20.147

Downloads:

Changes:

  • Added support for SmartServer updates to images with missing security certificates
  • Corrected power factor reporting for Schneider PM5563 meters
  • Bug fixes and performance improvements

SmartServer IoT 2.5 Update 1

Release Date: July 30, 2019

Versions:

  • SmartServer IoT Software: 2.51.001
  • IzoT Net Export Utility: 1.20.147

Downloads:

Changes:

  • Fixed MQTT broker connection error

SmartServer IoT 2.5

Release Date: July 12, 2019

Versions:

  • SmartServer IoT Software: 2.50.019
  • IzoT Net Export Utility: 1.20.094

Downloads:

Changes:

  • Added a BACnet Server to provide a BACnet compliant interface to the SmartServer IoT
  • Added a BACnet Router to route BACnet communications from BACnet FT devices to BACnet/IP over Ethernet
  • Added an IAP edge device messaging interface
  • Simplified device definition with a new CMS Devices widget
  • Simplified device type definition with a new CMS Device Properties widget
  • Added a CMS Datapoint Browser widget to view and update datapoints on your edge devices
  • Bug fixes and performance improvements

SmartServer IoT 2.4

Release Date: May 17, 2019

Versions:

  • SmartServer IoT Software: 2.41.003 (CMS 2.41.001)
  • IzoT Net Export Utility: 1.20.094

Downloads:

Changes:

  • Initial release



  • No labels