Under resource constraints, the tags may be repeated with different timestamps within the same packet. This behavior can happen temporarily under sudden spike in resource usage of other processes limiting the resources availability for SLMPConnector. To reproduce this scenario, follow these steps:
- Configure an IED VM with 1CPU core count and 2GB RAM.
- Install SLMP Connector IE Databus, IE Flow Creator, and IE Cloud Connector applications.
- Configure data points in SLMP Connector with low acquisition cycle supported by the connection.
If tags are repeated and you are interested only in the newest data available in the packet, then follow these steps:
- Parse the tag data packet received from the broker.
- Create a map with "id" as the key to hold the unique tag values.
- In case "id" is repeated, replace the tag data which has maximum "ts" value in the packet.
If tags are repeated and you are interested in all the packets with no data loss, then follow these steps:
- Parse the tag data packet received from the broker.
- Create a multi-map with "id" as the key to hold the multiple tag values for the same tag.
- Sort the tags with increasing order of timestamp before processing/storage.