CODAC Core System 5.3 CS-Studio Release Notes

advertisement
IDM UID
SMSET5
VERSION CREATED ON / VERSION / STATUS
23 Jun 2016 / 1.1 / Approved
EXTERNAL REFERENCE / VERSION
User Manual
CODAC Core System 5.3 CS-Studio Release Notes
In CODAC Core System 5.3, CS-Studio 4.3 with some ITER specific add-ons has been
released with the following new features, bug fixes and known problems.
Author
Co-Authors
Reviewers
Approver
Read Access
Name
Utzel N.
Approval Process
Action
23 Jun 2016:signed
Affiliation
IO/DG/COO/SCOD/CSD/CDC
Di Maio F.
Park M.
23 Jun 2016:recommended
IO/DG/COO/SCOD/CSD/CDC
27 Jun 2016:approved
IO/DG/COO/SCOD/CSD/CDC
Document Security: Internal Use
RO: Stepanov Denis
AD: ITER, AD: External Collaborators, AD: IO_Director-General, AD: EMAB, AD: OBS - Control System
Division (CSD) - EXT, AD: OBS - CODAC Section (CDC) - EXT, AD: OBS - CODAC Section (CDC), AD:
Auditors, AD: ITER Management Assessor, project administrator, RO
PDF generated on 27 Jun 2016
DISCLAIMER : UNCONTROLLED WHEN PRINTED – PLEASE CHECK THE STATUS OF THE DOCUMENT IN IDM
Change Log
CODAC Core System 5.3 CS-Studio Release Notes (SMSET5)
Version
Latest Status
Issue Date
v0.0
In Work
20 Jun 2016
v1.0
Signed
21 Jun 2016
v1.1
Approved
23 Jun 2016
Description of Change
Description of the new features, main bug fixes and known bugs and
limitations
Some typos fixed and update version for HTML as some character and
format were not properly converted
PDF generated on 27 Jun 2016
DISCLAIMER : UNCONTROLLED WHEN PRINTED – PLEASE CHECK THE STATUS OF THE DOCUMENT IN IDM
Table of Contents
1
2
Introduction .........................................................................................................................2
1.1
CODAC Core System Context...................................................................................2
1.2
Purpose.........................................................................................................................2
1.3
Scope.............................................................................................................................2
1.4
Related documents ......................................................................................................2
New Features........................................................................................................................3
2.1
Navigation Pane ..........................................................................................................3
2.2
Alarms List ..................................................................................................................4
2.3
OPIs Map.....................................................................................................................5
2.4
Alarm Page ..................................................................................................................6
2.5
New LED representation ............................................................................................6
2.6
Text input new label property ...................................................................................7
2.7
Standard Analog and Digital faceplates ...................................................................7
2.8
OPIs path in development and runtime environment .............................................8
2.9
Miscellanea features....................................................................................................8
3
Main bug fixes......................................................................................................................9
4
Known Bugs and Limitations ...........................................................................................10
4.1
Icons too small on 4K screen....................................................................................10
4.2
The flash timing of symbols is not synchronised for all flashing states ...............10
4.3
Connection between widgets in different linking containers ................................10
4.4
Issue with archived data retrieval ...........................................................................10
CS-Studio Release Notes
Page 1 of 10
1
Introduction
1.1
CODAC Core System Context
In CODAC Core System 5.3, CS-Studio 4.3 with some ITER specific add-ons has been released.
1.2
Purpose
The purpose of the Release Notes document is to communicate major new features and changes in this
release of the CS-Studio as integrated in CODAC Core System 5.3. It also documents known problems
and workarounds.
1.3
Scope
This document describes CS-Studio 4.3 for ITER which includes:





1.4
Operator Interface (OPI) – BOY - that connects to the control system, animates graphical
widgets according to EPICS process Variable (PV) value, alarm status/severity and
connection/RW status, shows PV’s range and alarm limits definition and allows the operator to
interact with the process by providing input data and sending commands,
Alarm System – BEAST - that monitors alarm triggers in the control system and provides
essential support to the operator by warning him of situations that need his attention, showing
guidance, allowing him to open dedicated displays, execute commands and acknowledge raised
alarms,
PON Archive System – BEAUTY - that monitors archived EPICS PVs in the control system
and provides a graphical user interface for displaying live and historic data in a plot, making
some computation, adding annotations and exporting samples into different file formats such as
Excel spread sheet or Matlab,
Electronic Logbook – OLOG - that registers events entered manually or generated
automatically during operation to keep track of problems, human decisions or actions which
were taken during the course of the activity and which may have had an impact on the outcome
of the activity.
Sequence of EPICS commands automation – SCAN.
Related documents
[RD1] CODAC Core System CS-Studio User Guide (QVBYD8 v1.0)
[RD2] CSS all in one (BFGP5Q v1.8)
CS-Studio Release Notes
Page 2 of 10
2
New Features
2.1
Navigation Pane
The navigation button animation reflects the highest severity of the corresponding alarm tree CBS node
in order for the operator to navigate quickly on the area in active alarm state as illustrated on Figure 2-1,
which shows that in CBS2 BUIL-B55 there are 2 areas in MINOR active alarm state. If an alarm
requires to be acknowledged, the button is flashing at 2Hz.
Figure 2-1 CBS3 BUIL-B55-CW and BUIL-B55-VA are in MINOR active alarm state
Hovering the mouse over a navigation button, the tooltip will show the number of latched alarms on the
corresponding alarm tree node as illustrated on Figure 2-2.
Figure 2-2 Navigation button tooltip includes the number of latched alarms information
Finally, making a right-click on a navigation button will allow the operator to acknowledge directly the
alarm node and subsequent alarms as illustrated on Figure 2-3.
Figure 2-3 Navigation button “Latched Alarm” context menu
CS-Studio Release Notes
Page 3 of 10
2.2
Alarms List
The Alarms List provides the operator with a list of all latched alarms and provides the functionality to
navigate through the alarms tree and view additional information about alarms. A latched alarm is the
first highest occurrence of an un-acknowledged alarm. If an alarm goes from minor to major state, the
latched alarm will correspond to the major state, time and value. If an alarm flickers between cleared
and alarm states, the latched alarm will correspond to the first time the highest alarm was triggered.
Each entry in an alarm list shows:








Tick box to acknowledge the alarm,
Alarm priority symbol – major
, minor
, major cleared but not yet acknowledged
,
minor cleared
, major acknowledged but not yet recovered
, minor acknowledged
.
Disconnection/Invalid alarm symbols - , , ,
Alarm description,
Date and time,
Current severity and status. This information could be [OK – NO ALARM] if the condition that
triggered the alarm has returned to normal. Such cleared alarm will remain in the list until
acknowledged by the operator (latched behaviour) but displayed in reverse video,
Alarm PV,
Value of the setting transgressed,
Alarm ID.
The background colour of the alarm message reflects the priority of the latched alarm and the alarm
priority symbol flashes at 2Hz until acknowledged by the operator.
The Alarms List is using the standard operator user interface layout with the following specific zones:



Status Bar which provides the user with a high-level overview of ITER’s overall status,
Alarms List which lists all latched alarms on the given alarm tree CBS node,
Navigation Pane extended to the screen width that allows the user to navigate through the alarm
tree based on the CBS, and this in 5 clicks maximum.
The new Alarms List as illustrated on Figure 2-4 can be opened from any navigation button by a rightclick Actions  Open in a new window the Alarms List.
Figure 2-4 Alarms List on CBS2 BUIL-B55
CS-Studio Release Notes
Page 4 of 10
2.3
OPIs Map
The OPIs Map provides the operator with a structured list of all OPIs used in the navigation. The map
includes drop-down menu buttons that allow the operator to open directly the OPI, open the alarms list
related to this OPI or open another OPIs map with the selected OPI highlighted.
The animation of the drop-down menu button is similar to a navigation button: the foreground colour
reflects the highest severity of the corresponding alarm tree CBS node/leaf in order for the operator to
see quickly which area is in alarm state, the tooltip shows the number of latched alarms on the
corresponding alarm tree node, a context menu is available to acknowledge directly the alarm tree node
and subsequent alarms.
The new OPIs Map as shown on Figure 2-5 can be opened from any navigation button by a right-click
Actions  Open in a new tab the OPIs Map.
Figure 2-5 OPIs Map buttons reflect the highest severity of the alarm tree CBS node
CS-Studio Release Notes
Page 5 of 10
2.4
Alarm Page
For each defined alarm, an alarm page has to be designed according to a standard layout accessible from
boy  templates  Alarm.opi and AlarmPage.opi.
To ease the development, SDD is generating for an I&C project all ITER-{pv_name}_Alarm.opi and
prepares the alarm description in ITER-{pv_name}_AlarmPage.opi.
What remains to be designed is the alarm procedure and PV trends as illustrated on Figure 2-5.
Figure 2-6 Alarm Page for the PV UTIL-S15-BG93:MUT2-ET4
2.5
New LED representation
As requested by Operation, the LED widget default properties and behaviour have changed:

Off state colour
= light brown




On state colour with no alarm
On state colour with minor alarm
On state colour with major alarm
On/Off disconnected state colour
= Green
= Yellow
= Red
= Magenta
Two standard rules have been attached to the LED widget as illustrated on Figure 2-7.
Figure 2-7 Standard rules for the LED ON and OFF properties
Figure 2-8 gives the details of the Alarm LED ON State Color rule definition.
CS-Studio Release Notes
Page 6 of 10
Figure 2-8 LED On Color property rule definition
Tip: To add the rules on existing OPI, just validate the OPI and make a quick fix.
2.6
Text input new label property
It is now possible to add directly a label to an input field instead of adding a Label widget to the Text
Input widget. By default, the label position is above the entry field as illustrated on Figure 2-9.
Figure 2-9 Text input label above the entry field
2.7
Standard Analog and Digital faceplates
Standard faceplates have been designed to display PV and alarm information for analog / digital input
and output as illustrated on Figure 2-10.
Figure 2-10 Analog and digital input standard faceplate
CS-Studio Release Notes
Page 7 of 10
They are accessible from boy  templates  faceplates and can be integrated as any faceplate by
defining an action as illustrated on Figure 2-11.
Figure 2-11 Analog input faceplate action
2.8
OPIs path in development and runtime environment
To standardise the OPI path between development and runtime environment, a new linked boy folder is
created under the I&C project folder which points to src/main/boy folder during the development phase.
This linked folder is mainly used to refer to an alarm page as /{I&C project}/boy/ITER{pv_name}_Alarm.opi in order to open it within the workspace from the alarm pane and the alarms list.
2.9
Miscellanea features
The faceplate demo resources make use of control native widgets in order to have the next focus feature
with the TAB or ENTER keys to go to the next entry field or control button.
The period for repeated annunciation of active alarms has been disabled (nagging period).
CS-Studio Release Notes
Page 8 of 10
3
Main bug fixes
The issue with modal dialogs in full screen have been fixed. In 5.2, popup windows such as “Show
macros”, “Dump PV List” or any error messages were displayed behind the OPI running in full screen
which prevented to validate and close the dialog.
The alarm pane connection/disconnection issue in case of alarm server timeout is solved. In case of
disconnection, the alarm pane is now disabled and a “Disconnected” message is displayed on top of the
table. When the alarm server is back online, the alarm pane reconnects automatically to the list of
alarms and is enabled.
The action label “Go to” on navigation buttons was incomplete. The description of the CBS as defined
in the navigation xml configuration file has been added. Example: “Go to Monitoring of Cooling Water
System”.
CS-Studio Release Notes
Page 9 of 10
4
Known Bugs and Limitations
4.1
Icons too small on 4K screen
This a known issue of Eclipse and shall be resolved in the next release.
4.2
The flash timing of symbols is not synchronised for all flashing states
This issue will be solved for the next release.
4.3
Connection between widgets in different linking containers
The problem occurs only if the default routing is changed by the developer.
Figure 4-1 shows two super object valves in two different linking containers and standard / nonstandard routing connections between widgets. Once the mimic is integrated into the canvas, the nonstandard routing connection goes outside the frame.
Figure 4-1 Non default routing issue
This issue will be solved for the next release.
4.4
Issue with archived data retrieval
It could happen that no archived data are retrieved and plotted due to a database error traced in the
console - org.postgresql.util.PSQLException: ERROR: portal "C_n" does not exist.
This issue will be solved for the next release.
CS-Studio Release Notes
Page 10 of 10
Download