EI 1.16.0 - Nov 08, 2023

New and Revised features

• Support for 2020 version of J2735 for NTCIP 1202 and RSU Connector
• UI/UX Enhancement
• NB API Implementation Phase 2
• Enhancements to internal performance when establishing connections and transmitting messages to Azure IoT Hub

Supported IOx and IOS versions

Open caveats

• NTCIP 1202 Asset configured with SNMP V3 version will not be able to receive SNMP V3 trap messages but it can receive V1/V2 trap messages because of backword compatibility, for Polling attribute SNMP V3 version will be able to receive all V1/V2/V3 polling messages.
• SNMP standard trap port 162 is not supported as it is reserved by IOX/IOS so it can not communicate for trap messages if it is configured in NTCIP Asset model.
• Multi topic is not supported on IBM Watson.
• Protobuf: Support for precision upto 2^53 for 64bit prototypes.
• Protobuf: Default values (e.g. 0, false, '') are automatically encoded, to avoid this behaviour, null must be assigned to attribute.
• There won't be a BACKPRESSURE OK event generated for a specific pipeline, if the last event was BACKPRESSURE_UP or BACKPRESSURE_DROP and the pipeline is undeployed (for any reason).
• In the UI event log for Azure Link, data drops are recorded as events when the transmission fails due to a timeout. Even in low-bandwidth scenarios, you may encounter "Dropping message. Delivery failed due to timeout." messages in the health status path.
• If the UI does not specify a sampling interval, it will default to 0 seconds, which can lead to crashes if there are many attributes from the southbound. To avoid this, it's essential to set the sampling interval based on the input size.

Resolved Caveats

Recommendations

• Please go through the EI documentation for more details.

EI 1.14.0 - Aug 08, 2023

New and Revised features

• SNMP Enhancements for NTCIP - Wrong Way Driver devices:
  • Enable connection of basic SNMP devices using NTCIP-1202 connector
• Clone and Publish Data Logics through the Cloud UI:
  • Create and deploy new pipelines without VS Code
• Basic Cloud API Access for EI Services:
  • Implement API platform with initial endpoint for retrieving status information about Agents

Supported IOx and IOS versions

Open caveats

• NTCIP 1202 Asset configured with SNMP V3 version will not be able to receive SNMP V3 trap messages but it can receive V1/V2 trap messages because of backword compatibility, for Polling attribute SNMP V3 version will be able to receive all V1/V2/V3 polling messages.
• SNMP standard trap port 162 is not supported as it is reserved by IOX/IOS so it can not communicate for trap messages if it is configured in NTCIP Asset model.
• Multi topic is not supported on IBM Watson.
• Protobuf: Support for precision upto 2^53 for 64bit prototypes.
• Protobuf: Default values (e.g. 0, false, '') are automatically encoded, to avoid this behaviour, null must be assigned to attribute.
• There won't be a BACKPRESSURE OK event generated for a specific pipeline, if the last event was BACKPRESSURE_UP or BACKPRESSURE_DROP and the pipeline is undeployed (for any reason).
• In the UI event log for Azure Link, data drops are recorded as events when the transmission fails due to a timeout. Even in low-bandwidth scenarios, you may encounter "Dropping message. Delivery failed due to timeout." messages in the health status path.
• If the UI does not specify a sampling interval, it will default to 0 seconds, which can lead to crashes if there are many attributes from the southbound. To avoid this, it's essential to set the sampling interval based on the input size.

Resolved Caveats

Recommendations

• Please go through the EI documentation for SNMP Connector Utilizing NTCIP1202.

EI 1.12.0 - May 11, 2023

New and Revised features

• Metrics Collection -
  • This feature will provide detailed information on the application's resource usage, i.e., the application's CPU, memory, network utilization, and much more.
  • The name of the CSV file in which the data will be saved as a comma-separated variable is "metrics_collect.csv".
  • The current CSV file will be compressed and a new CSV file created every day at 11:59 PM.
  • The application saves files for seven days. After seventh day, a new file will replace the older one.

Supported IOx and IOS versions

Open caveats

• Multi topic is not supported on IBM Watson.
• Protobuf: Support for precision upto 2^53 for 64bit prototypes.
• Protobuf: Default values (for example, 0, false, '') are automatically encoded; to avoid this behaviour, null must be assigned to the attribute.
• There won't be a BACKPRESSURE OK event generated for a specific pipeline, if the last event was BACKPRESSURE_UP or BACKPRESSURE_DROP and the pipeline is undeployed (for any reason).
• We are transmitting data drop as an event for Azure Link in the UI under the event log, however in a scenario with low-bandwidth, we can still see "Dropping message. Delivery failed due to timeout." messages in the health status path.
• If no sampling interval is specified in the UI, it will use the default value of 0 seconds, which may cause the links to crash if there are many attributes from the southbound. The sampling interval has to be used based on the input size.

Recommendations

• For detailed explanation of Metrics Collection please go through the documentation. See Documentation for Metrics collection.

EI 1.10.2 - Mar 01, 2023

New and Revised features

• EI agent on IE3400
• Protobuf support in EI agent
• Multi-topic support:
  1. Ability to publish data on different topics to MQTT destination using Datalogic script.
  2. Support for subscription of multiple MQTT topics using Datalogic script.

Supported IOx and IOS versions

Known issues and limitations

• Multi topic is not supported on IBM Watson.

• Protobuf: Support for precision upto 2^53 for 64bit prototypes.

• Protobuf: Default values (e.g. 0, false, '') are automatically encoded, to avoid this behaviour, null must be assigned to attribute.

• There won't be a BACKPRESSURE OK event generated for a specific pipeline, if the last event was BACKPRESSURE_UP or BACKPRESSURE_DROP and the pipeline is undeployed (for any reason).

• We are transmitting data drop as an event for Azure Link in the UI under the event log, however in a scenario with low-bandwidth, we can still see "Dropping message. Delivery failed due to timeout." messages in the health status path.

• If no sampling interval is specified in the UI, it will use the default value of 0 seconds, which may cause the links to crash if there are many attributes from the southbound. The sampling interval has to be used based on the input size.

• After upgrading from EI_1.8.0 to EI_1.10.0, the following parameters will not be part of dslink.json for azure or MQTT link by default; if the default values for any of the following parameters need to be changed, they must be manually added to the dslink.json file with the necessary values, and then the link must be restarted.

  Configuration: "max_cir_queue_count": {
  "type": "int",
  "default": 1024
  },
  "max_cir_queue_size_mb": {
  "type": "int",
  "default": 10
  },
  "sdk_queue_size": {
  "type": "int",
  "default": 64
  },
  "drop_event_init_interval_sec": {
  "type": "int",
  "default": 60
  },
  "drop_event_final_interval_sec": {
  "type": "int",
  "default": 600
  }
  

PS: We should eliminate these unnecessary parameters before downgrading from EI 1.8.0. If you don't, azure and MQTT links will fail to start on the downgrade.

Recommendations

• Please go through the EI documentation for protobuf sample datalogic script.

EI 1.10.0 - Nov 16, 2022

New and Revised Features

• Detecting data delivery impacts in NB links of an EI agent and inform the user about the occurrence and its impacts.
• EI agent on Aventus IR1800.

Supported IOx and IOS versions

Resolved Caveats

Known issues and limitations

• If for a given pipeline the last event is BACKPRESSURE_UP or BACKPRESSURE_DROP and if the pipeline is undeployed (due to any reason) there won't be an BACKPRESSURE_OK event generated after this.

• For azure link , we are sending data drop as an event in UI under event log. But during low bandwidth scenario, we can still see "Dropping message. Delivery failed due to timeout." messages in health status path.

• If sampling interval is not provided in the UI it would take the default value which is 0 s, in this case if there are many attributes from south bound then the links can crash. Sampling interval have to be used based on the input size.

• After upgrade from EI_1.8.0 to EI_1.10.0, below parameters will not be part of dslink.json for azure or MQTT link by default, if incase there is a need to change default values for any of the below parameter then these must be added into dslink.json file manually with required values and restart the link.

  Configuration: "max_cir_queue_count": {
  "type": "int",
  "default": 1024
  },
  "max_cir_queue_size_mb": {
  "type": "int",
  "default": 10
  },
  "sdk_queue_size": {
  "type": "int",
  "default": 64
  },
  "drop_event_init_interval_sec": {
  "type": "int",
  "default": 60
  },
  "drop_event_final_interval_sec": {
  "type": "int",
  "default": 600
  }
  

Note: While downgrading from to EI_1.8.0 we should remove these extra parameters before downgrading, failing to do so, will cause azure and MQTT links fail to start on downgrade.

Recommendations

Upgrade Cisco Edge Intelligence extension for Microsoft Visual Studio Code (VS Code).

1. Search for the "Cisco Edge Intelligence" extension Visual Studio marketplace.
2. Follow the prompts to install the extension.
3. Once installed, "CISCO EI" appears in the explorer bar.

EI 1.8.0 - June 29, 2022

New and Revised Features

• Previously, the log rotation was based on time, and it is now changed based on the size limit. Once the file size reaches the max size limit, the log file is compressed using gzip algorithm and it is rotated. The archived files will have a timestamp and the log file's name. The algorithm uses 50% of disk space by default and calculates the max size of the file with the default number of files as 10 for each link.

• In addition to the existing global trigger properties - device_name and field_name, and timestamp is added.

• The trigger.timestamp is updated with the time while reading the data from source and is made available to the datalogic engine.

• This timestamp is used in datalogic script and added to the payload on demand.

• The timestamp is maintained in Zulu.

Supported IOx and IOS versions

Resolved Caveats

Known issues and limitations

• Global objects (e.g. "performance", "output", "parameters", "trigger”) provided/implemented by Scripting Engine are not iterable and accessing the internal properties such as “_name” and “0” will lead to run time java script error.
• Low network bandwidth can cause memory crunch hence resulting in restarting the process. This can be resolved by increasing the network bandwidth or by increasing the sampling interval.
• Device Model attribute names must not start with a number.

Required Action

• If Timestamp is required in attributes:

1. In addition to existing global trigger properties - device_name and field_name, timestamp is added.

2. The trigger.timestamp is updated with the time while reading the data from source and is made available for the datalogic engine.
   For example:

   function on_update() {

   device = trigger.device_name;

   attribute = trigger.field_name;

   value = akmqtt[attribute];

   timestamp = trigger.timestamp;

   // logging only

   logger.info("device name: " + device);

   logger.info("attribute name: " + attribute);

   logger.info("attribute value: " + value);

   logger.info("attribute value timestamp: " + timestamp);

   // construct JSON object

   data = new Object();

   data["v"] = value;

   data["ts"] = timestamp;

   telemetry = new Object();

   telemetry[attribute] = data;

   msg = new Object();

   msg[device] = telemetry;

   logger.info(JSON.stringify(msg));

   publish("output", msg);

   }

3. This timestamp can be used by the customer in datalogic script and added to the payload on demand.

4. The timestamp is maintained in Zulu.
   

   For example: 2022-05-06T12:57:17.461Z

• Following steps need to be performed to upgrade EI from v1.6.x to v1.8.0:

1. After upgrading EI agent, we should map our ports again.
2. Redeploy that pipeline.
3. Also, we can reset the agent in UI.

Recommendations

Upgrade Cisco Edge Intelligence extension for Microsoft Visual Studio Code (VS Code).

1. Search for the "Cisco Edge Intelligence" extension Visual Studio marketplace.
2. Follow the prompts to install the extension.
3. Once installed, "CISCO EI" appears in the explorer bar.

EI 1.6.2 - May 2, 2022

Supported IOx and IOS versions

Resolved Caveats

Known issues and limitations

• Global objects (e.g. "performance", "output", "parameters", "trigger”) provided/implemented by Scripting Engine are not iterable and accessing the internal properties such as “_name” and “0” will lead to run time java script error.
• Low network bandwidth can cause memory crunch hence resulting in restarting the process. This can be resolved by increasing the network bandwidth or by increasing the sampling interval.
• Device Model attribute names must not start with a number.

Required Action

Steps to follow for data rules/logic using MQTT destination during upgrade from 1.4.X to 1.6.X:

• Undeploy the current running pipeline in 1.4.X.
• Upgrade the EI agent version to 1.6.X.
• Deploy again the same pipeline to the newly upgraded EI agent.

Recommendations

Upgrade Cisco Edge Intelligence extension for Microsoft Visual Studio Code (VS Code).

1. Search for the "Cisco Edge Intelligence" extension Visual Studio marketplace.
2. Follow the prompts to install the extension.
3. Once installed, "CISCO EI" appears in the explorer bar.

EI 1.6.0 - March 10, 2022

New and revised features for EI

• EIP/CIP asset type with single and multi level tag support
• Roadways (Trafficware and Econolite binary streaming to SAE J2735 SPAT and J2735 SRM/SSM to NTCIP 1211)
• Reset option to clear all the data policy deployment information of the EI Agent
• Events option to track the health status of the system, an EI agent, or a data policy

Supported IOx and IOS versions

Resolved Caveats

Known issues and limitations

• Global objects (e.g. "performance", "output", "parameters", "trigger”) provided/implemented by Scripting Engine are not iterable and accessing the internal properties such as “_name” and “0” will lead to run time java script error.
• Low network bandwidth can cause memory crunch hence resulting in restarting the process. This can be resolved by increasing the network bandwidth or by increasing the sampling interval.
• Device Model attribute names must not start with a number.

Required Action

Steps to follow for data rules/logic using MQTT destination during upgrade from 1.4.X to 1.6.X:

• Undeploy the current running pipeline in 1.4.X.
• Upgrade the EI agent version to 1.6.X.
• Deploy again the same pipeline to the newly upgraded EI agent.

Recommendations

Upgrade Cisco Edge Intelligence extension for Microsoft Visual Studio Code (VS Code).

1. Search for the "Cisco Edge Intelligence" extension Visual Studio marketplace.
2. Follow the prompts to install the extension.
3. Once installed, "CISCO EI" appears in the explorer bar.

EI 1.4.16 - September 29, 2021

New features for EI

• EIP/CIP asset type (under feature flag)
• Bulk Import and EI Agent Mapping of Assets via CSV
• Improvement Overall System Health Overview
  • Added EI Agent Management capabilities from within Edge Intelligence for EDM (Edge Device Manager) managed devices.
  • Added and improved Data Rule and Data Logic health UI views.
  • Multiple UI improvements for better viewing of the overall system health status
• RSU connector (under feature flag)
  • Support for Probe Vehicle Data (PVD)

Supported IOx and IOS versions

Resolved Caveats

Cloud bug fixes

Fixed multiple issues with list requests in Cloud Broker which were leading to missing status updates.

Known issues and limitations

• Global objects (e.g. "performance", "output", "parameters", "trigger”) provided/implemented by Scripting Engine are not iterable and accessing the internal properties such as “_name” and “0” will lead to run time java script error.
• Low network bandwidth can cause memory crunch hence resulting in restarting the process. This can be resolved by increasing the network bandwidth or by increasing the sampling interval.
• Device Model attribute names must not start with a number.

Required Action

If you are not using the RSU connector, no action is required. For the RSU connector, upgrade to EI Agent 1.4.16 to support the new features.

Recommendations

Upgrade Cisco Edge Intelligence extension for Microsoft Visual Studio Code (VS Code).

1. Search for the "Cisco Edge Intelligence" extension Visual Studio marketplace.
2. Follow the prompts to install the extension.
3. Once installed, "CISCO EI" appears in the explorer bar.

EI 1.4.14 - August 31, 2021

Supported IOx and IOS versions

Resolved Caveats

Known issue and limitation

• Low sampling interval can sometimes result in out of memory. This can be mitigated by either allocating more memory to the application or increasing the sampling interval.

EI 1.4.12 - July 20, 2021

Resolved Caveats

EI 1.4.10 - June 21, 2021

New and revised features

• Serial Data Model Binary Data Improvements​
• MQTT Destination Cloud to Datalogic Command Channel​
• IBM Watson – Automatic Device Instance Creation​
• EI Agent Management

Known issues and limitations

• Global objects (e.g. "performance", "output", "parameters", "trigger”) provided/implemented by Scripting Engine are not iterable and accessing the internal properties such as “_name” and “0” will lead to run time java script error.
• EI agents with $ in their name are not detected, avoid using $ in agent names.
• Device Model attribute names must not start with a number.

Resolved Caveats

EI 1.2.20 - April 12, 2021

Known issues and limitations

• Global objects (e.g. "performance", "output", "parameters", "trigger”) provided/implemented by Scripting Engine are not iterable and accessing the internal properties such as “_name” and “0” will lead to run time java script error.
• An error might occur when undeploying a pipeline "invalid path / not found". If this error occurs, undeploy the pipeline again.

Open Caveats

Resolved Caveats

EI 1.2.18 - March 10, 2021

Known issues and limitations

• Global objects (e.g. "performance", "output", "parameters", "trigger”) provided/implemented by Scripting Engine are not iterable and accessing the internal properties such as “_name” and “0” will lead to run time java script error.
• An error might occur when undeploying a pipeline "invalid path / not found". If this error occurs, please undeploy the pipeline again.

Open Caveats

Resolved Caveats

EI 1.2.14 - February 02, 2021

Known issues and limitations

• Global objects (e.g. "performance", "output", "parameters", "trigger”) provided/implemented by Scripting Engine are not iterable and accessing the internal properties such as “_name” and “0” will lead to run time java script error.
• An error might occur when undeploying a pipeline "invalid path / not found". If this error occurs, please undeploy the pipeline again.

Open Caveats

Resolved Caveats

EI 1.2.6 - December 15, 2020

Upgrade requirements

All EI Agents must be updated to the latest version to ensure full feature compatibility with the Cisco EI cloud software. For example, upgrading the EI Agent allows you to use new connection types for Assets and Data Destinations and perform all Data Policy management actions.

In this release, you must manually upgrade the EI Agents using GMM/FND/Local Manager. Because this upgrade process removes all data policy information from the agent, you must also download a summary of your Data Policies, un-deploy the policies, upgrade the EI Agents and then redeploy the policies to the same EI Agents.

• Upgrade EI Agents instructions
• Download the EI Agent software

New and revised features

Support for new Asset Types and Assets

• Serial

Data Destinations enhancements

• Enhancements to Generic MQTT destinations
• IBM Watson (telemetry)
• Cumulocity IoT (telemetry, dynamic provisioning)
• AWS IoT Core (using Generic MQTT, telemetry, just-in-time provisioning)
• Azure IoT Central Telemetry support using Azure IoT Hub

Data Logic enhancements

Data Logic now supports the following:

• Read data from multiple asset types (one asset per type)
• Write back into a subset of supported devices that support writable attributes (Local Action)
• Transfer files using the Data Logic script
• Ability to define the structure of output of a Data Logic within the script
• Improved configuration and deployment workflow for Data Logic based policies

Known issues and limitations

• The latest features and enhancements are available only if all EI Agents are upgraded to the latest release.
• File transfer feature in the Data Logic script has the following limitations:
  • Currently, the maximum file size supported is 30 MB.
  • At any given point of time, only one data logic script which is doing file transfer should be running on an EI Agent.
• EI agents with $ in their name are not detected - workaround: do not use $ in the name of an EI Agent.
• Global objects (e.g. "performance", "output", "parameters", "trigger”) provided/implemented by Scripting Engine are not iterable and accessing the internal properties such as “_name” and “0” will lead to run time java script error.

Updated network device requirements and caveats

See Supported network devices and firmware for information on the supported IOS/IOx versions and caveats for this release.

Open Caveats

Resolved Caveats

EI 1.0.4 - September 15, 2020

New and revised features

The following production server URLs are now supported when logging in to Cisco IoT from the VS Code app:

• https://eu.ciscoiot.com
• https://us.ciscoiot.com

See Data Logic for more information.

EI 1.0.2 - August 6, 2020

New and revised features

• EI now supports the IR1101 gateway.
  • See Supported edge devices and firmware for more information.
  • Download the EI Agent from the Cisco Download Center.

Resolved caveats

EI 1.0.0 - July 22, 2020

Supported Features

Known issues and limitations

• The attribute names of asset model definition should be alphanumeric and can contain underscores. The names should not contain hyphens.

• There is no limitation on the attribute label naming convention.

Open Caveats

EI Agent ( IOx Platform) Caveats