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.