We use cookies and similar web technologies to recognize your repeat websites visits and preferences and to analyze traffic. To learn more about cookies, including steps for disabling, view our Cookie Policy. By clicking “I Accept” on this banner you consent to the use of cookies unless you disable them.

Skip to Main Content

RTMS Echo Firmware v1.1 Release Notes


We have added some new features to the RTMS Echo Firmware version 1.1. 

This is a production release for the Echo product line and an optional upgrade for existing Echo sensors and changes made do not effect operation or functionality of existing sensors.


Sx-300 data collection via RS-485

We've added the ability to allow data collection via Serial using a Ethernet to Serial converter. This will allow Echo to act as a drop-in replacement for Sx-300 units installed in the field.

Added azimuth

We added the azimuth information to further simplify the installation process for you by ensuring Echo is aimed perpendicular to the roadway.

Occupancy with Echo API

We have expanded the capable of our queries within the Echo API by adding a separate date range for occupancy data retrieval.

Zone configuration change warning message

We added a warning message that appears when you attempt to make changes on the Zones page to avoid losing desirable traffic data prior to making the changes.

Wavetronix® Protocol Support

The Echo now supports a subset of the Wavetronix protocol which allows the RTMS Echo to integrate into systems that were designed to capture information from Wavetronix units.

Interval Data

We've added the ability to save additional data types in the interval data. The new types are counts binned by speed and counts by direction of travel. The ability to enable the data types will depend on how you configure Echo for data retrieval. See our online help for more details.

Change to the default password

We've updated the default password to be more unique. Web browsers like Google Chrome are now monitoring username and password combinations and comparing them against combinations that have been part of data breaches. Common combinations, like our previous default password, will trigger an alert, so to avoid unnecessary concern it has been changed. As always, we recommend you change your credentials to ensure you remain secure.


Please note that when upgrading from v1.0 to v1.1, protocol settings defaults to "no protocol" and previous protocol settings are lost.