Resolving time jumps in the system and in the log
Problem
In systems with multiple Griesser LINK devices, issues may arise that cause the real-time data used by the system to be incorrect. This condition is recognizable by the fact that all functions dependent on real-time data behave unpredictably. This means, for example, that “time jumps” occur in the logging or in the information regarding the sun’s position, commands are executed at the wrong time, etc.
These effects can occur if the control units have different UTC offsets or if the Griesser LINK-compatible devices were only connected via Griesser LINK after they had already started up. The latter causes system services to no longer be renegotiated, resulting in system services that should exist only once in the system appearing multiple times.
Workaround
If there is a deviation from the principle stated in the safety instructions of the supplementary sheets—namely, to perform final work only when the system is de-energized—it must therefore be ensured that devices (or groups of devices) are connected to an already running system while in a de-energized state. Alternatively, the system can be restarted after installation.
Occurs in version
- .V1.4.V1.17
- 129.V1.x.V1.18
- 298.V1.x.V1.19
- 326.V1.x.V1.20
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article