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
• Cisco SSO Login Experience (New Feature)
  • IoT Operations Dashboard is integrated with Cisco Customer Identity (CCI) for an improved and seamless login experience. Cisco Customer Identity (CCI) is an identity provider managed and used by Cisco. Most users are already familiar with CCI and using it for logging into Cisco.com. This integration of IoT OD with CCI provides enhanced secure authentication and enables users to navigate across multiple Cisco applications and websites with one set of login credentials ensuring seamless operation. Refer CCI Integration.

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

• See 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.