OPC-UA Timestamp not match with alarm and no millisecond display

[prabhu.natarajan.n@gmail.com]

Dear Team,

We have observed the following issues related to OPC UA alarm timestamps:

1. **OPC UA Timestamp Mismatch**

* The timestamp received through the OPC UA server does not match the corresponding alarm timestamp displayed in the application.
* Please verify whether the timestamp is being sourced from the OPC UA server correctly or if any conversion (timezone, local time, UTC, etc.) is causing the discrepancy.

2. **Millisecond Display Missing**

* Alarm timestamps are currently displayed only up to seconds.
* Milliseconds are not shown, making it difficult to accurately analyze the sequence of events when multiple alarms occur within the same second.
* Kindly enable millisecond (HH:mm:ss.fff) display for alarm timestamps.

Please investigate these issues and provide a resolution or clarification on the expected behavior.

If required, we can share sample OPC UA data, alarm logs, and screenshots for further analysis.

Thank you.

Best regards,
Prabhu Natarajan

• This topic was modified 2 months, 1 week ago by Mikhail.

[Mikhail]

Dear Prabhu,

1. Please provide corresponding screenshots and logs. I’ll be glad to help you figure out the cause.

2. Timestamps are accurately stored in the archive, but are truncated to the second when output. Unfortunately, I can’t provide any guidance on the implementation timeline. If you need it urgently, we can develop a separate report under the contract.

[Author]

Posts