Known Issues - FreeWaveTechnologies/ZumIQ GitHub Wiki

This document contains known issues of ZumIQ-enabled devices and the ZumIQ development environment. These issues may be addressed in future releases.

Contents

Downgrade 1.0.6 to earlier versions of ZumLink firmware is not supported

Due to significant internal changes to support programmability, downgrade from 1.0.6.0 to 1.0.3.2, 1.0.4.1, 1.0.4.2, 1.0.4.3, or any other earlier ZumLink firmware is not supported. Doing so may render your unit non-functional in a way that is not field-recoverable. Should this occur, please contact FreeWave Customer Support for assistance.

Please note that 1.0.6.0 is fully over-the-air compatible with 1.0.4.* firmware versions.

Downgrade 2.0.x.x to 1.x.x or earlier versions of ZumLink firmware is not supported

Due to significant internal changes to support programmability, downgrade from 2.0.2.4 to 1.2.0.1, 1.1.2.2, 1.1.1.2, 1.1.0.0, or any other earlier ZumLink firmware is not supported. Doing so will render your unit non-functional in a way that is not field-recoverable. Should this occur, please contact FreeWave Customer Support for assistance.

This includes the RTE environment. The Linux RTE 2.0.x.x is only compatible with Device Firmware versions 2.0.x.x. Attempting to run a 1.x.x.x Linux RTE with Device Firmware 2.0.x.x will have unpredictable and unintended consequences.

Please note that 2.0.2.4 is fully over-the-air compatible with 1.1.x.x firmware versions.

The web page isn't available for several minutes after the unit comes up from a reboot

When a ZumIQ-enabled device reboots (especially after a firmware update), there are several background tasks that are executed. Priority is given to getting the data path and network interfaces up and running. The device web services are a lower priority, and can take up to two minutes to be available after network interfaces are restored. This affects both the website as well as the web CLI.

Changing any of the Network TCP port settings require a reboot to take effect

  • Changing the Terminal Server Port number for any of the COM ports.
  • Changing the Modbus TCP and Modbus RTU over TCP ports of the radio in the Modbus tab.

Security page settings require a reboot to take effect

The security settings security.enablePtpInterface and security.enableEthernetLogin are supported at a low level in the operating system and require a reboot to be applied.

RSA (SSH) id changes on firmware upgrade/downgrade

The RSA id will change whenever the main firmware is upgraded or downgraded. This will require you to accept new SSH keys when logging in remotely.

Reboot required after applying a license file

If you apply a license file to a ZumIQ-enabled device (using one of the upload methods listed in Transfer Files), a reboot is required for the licensed features to be activated, even if "systemInfo.license" indicates that the license is present. Either power cycle the unit or issue the reset now command in the ZumLink CLI.

Node-RED website timeout on slow networks

There is a issue in Node.js v8 that can cause the Node-RED website to timeout when accessed on slow or high-latency networks. This can be worked around by replacing Node.js v8 with Node.js v7 using the install-node7.sh script. This script can be run before or after installing Node-RED (using /home/devuser/bin/install-node-red.sh), and will change the default Node.js instance for the entire ZumIQ Linux environment.

Note that even with this fix, the Node-RED website may still take several minutes to load the first time on slow networks (up to 5 minutes on a 115.2 kbps network with compression turned on). Once loaded, subsequent reloads will take significantly less time, since most of the JavaScript files comprising the Node-RED website will be cached in the browser.