Changes/Logging of Wind Threshold Values BGS, BGT, GTS
Problem
As of BGS SW V2.8, BGT SW V3.7, GPA V2.6
:- Changes to wind limit values on
the BGS user interface are protected by the password "49" - Previously, changes to wind limit values were not logged. Now, an entry is made in the log of the operator terminal (BGS or BGT) on whose user interface a wind limit value change was made: A change is displayed in the command log on the user interface and also logged in the CSV log file.
- The log entry includes the ID of the triggering operator terminal, the ID of the affected Flex module, the limit value number, and the two limit values before and after the change.
- CSV files containing such log entries for wind limit value changes can be analyzed using the GPA starting with version 2.6.
Starting with BGT SW V3.8, GTS SW V2.2, GPA V2.7
:- BGT and BGS log wind limit value changes on their own user interface as before. Additionally, BGT and GTS log wind limit value changes made on another Griesser Link participant (BGT or BGS), though with certain restrictions:
For each change (alarm or reset limit value), one log entry is created with the alarm limit value and one log entry with the reset limit value following the change.
From these two log entries, it can therefore only be deduced that one of the two values was changed, but not which one or by how much.
The limit value number is also included in these entries, but the ID of the triggering operator terminal and the ID of the affected Flex module
are unknown.CSV files containing log entries for all wind limit value changes can be analyzed using the GPA starting with version 2.7.
Workaround
- Make the wind limit value change in FlexTool if it is not yet supported on the BGS or BGT.
- Obtain wind limit value changes from the log of the BGS or BGT on which the change was made, if the logs of other Griesser Link participants are not yet supported or are not sufficiently informative.
Occurs in version
- 242.V1.3.V2.8
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