I've encountered a bug in Zenon Logic where the timestamp of an internal variable (Driver for internal variables) is not updated when the variable's value is changed from within Zenon Logic.
This leads to several issues:
Alarm message list displays incorrect timestamps for when the alarm occurred.
The alarm duration is shown as 0 seconds once the alarm is cleared.
An archive configured with "on change" mode is likely storing the value with an incorrect timestamp, resulting in misleading trend displays.
The project settings are correctly configured to enable timestamps for the internal driver. A screenshot of the settings is attached. Additionally, I have recorded a short video demonstrating the issue.
This document governs the use of our Community Forum. By registering and using the platform, you accept these conditions.
The COPA-DATA Community Forum serves to encourage the exchange of information and experience about the zenon software between forum users respectively zenon users.
Please mind that any published information on the Community Forum is the subjective opinion and view based on the experience and the level of knowledge of the author. COPA-DATA does not overtake any responsibility for the content and the accuracy of the shared information.
Users of the Community Forum are encouraged to share only well-founded experiences and to point out any risks associated with the implementation of proposed solutions to problems. COPA-DATA at its absolute discretion, reserves the right to moderate the forum. In this connection COPA-DATA may remove any information containing false facts, potentially dangerous solutions, bad language or content that may insult, degrade or discriminate others. COPA-DATA may block a non-complying user from forum access if the user violated this provision.
COPA-DATA reserves the right to change this document from time to time at own discretion.
Ing. Punzenberger COPA-DATA GmbH
Karolingerstraße 7b · 5020 Salzburg · Austria
www.copadata.com