JCOP FWWG Meeting
8 February 2022
Participants: Christophe Pires, Wassef Karimeh, Valeri Falaleev, Piero Giorgio Verdini, Geraldine Thomas, Michael Ludwig, Mariusz Suder, Laura Sargsyan, Piotr Golonka, Luís Granado Cardoso, Frank Glege, Juan Manuel Pablo Rodriguez, Clara Gaspar, Fernando Varela, Giovanna Lehmann, Stefan Schlenker, Ivan Atanasov, Raúl Jiménez, Peter Bond, Peter Chochula
INDICO: https://indico.cern.ch/event/1121310/
News on WinCC OA and JCOP Framework
- A new version of fwFSM component (v34r17) is available for download. It contains fixes that are not typically encountered, but spotted at the CMS production system (see the release notes). This version is the recommended one now
- There are a few other issues with fwFSM, also signalled by CMS. They would require an intervention into the very core of the WCCOAsmi, which may also affect stability... therefore it is not planned to have an immediate next release for them.
- fwOpcUaTools vesion 0.2.0 has been released and announced, with new features for the verification/configuration of OPC UA addressing
- It was decided that there will be NO RELEASE of the JCOP Framework for WinCC OA 3.18 any time soon.
This is due to the uncertain plans with respect to the next opportunity for the upgrade and overall wish to run WinCC OA 3.16 in production for "as long as possible". The features of the upcoming 3.19 release are also interesting, and they should be looked at, possibly as soon as preview/beta releases are available. Agreed to review the roadmap for the next upgrade after the LHC restart (ie. when experiments run nominally and everyone has more time).
- There is a patch P030 for WinCC OA 3.16, which passes the smoke tests hence could be used by developers in their setups
- The Installation/Maintenance workshop will happen at the beginning of March.
Proposal of integration of WinCC OA exceptions mechanism into the Framework
- see the documentation attached to the INDICO event
- clarified that, unless decided otherwise by the JCOP, it is not intended to massively modify the existing parts of the framework to use the new mechanism of exceptions. However, it may be considered that certain components may be adjusted to support both methods for exceptions using the "bridge" mechanism
- comment: the new mechanism is aligned with the need for consolidation of log messages
- comment: the stack trace displayed in the notification window may need to be reconsidered, as it may not bring a meaningful information for the operator; clarified that this is the reason why by default it is not shown and a button needs to be pressed. The concern here is that the stack trace may reveal values passed to the functions, which may possibly be a security threat (e.g. for the cases where user credentials are passed in the arguments) - this may need a proper treatment at display. Having the stack traces in the log file should be OK (as it is already the case for errors).
- realizing that this is a busy time, Piotr expects feedback about the component over the next couple of months - a follow up discussion should be expected mid-Spring 2022
AOB and next meeting
- Next meeting scheduled for 22 February 2022 => https://indico.cern.ch/event/1127482/
- Mariusz/Ben to provide update on how the invalid bits for the hardware connected with OPC-UA could reflect the disconnection of a crate, or how they behave after a restart of OPC servers, etc
- ATLAS proposed a presentation of the OPC UA server for the ATCA shelf manager, employing numerous interesting techniques used to implement it
- to complement the above, BE-ICS would present an update on the integration of the ATCA power generators to the framework
There are minutes attached to this event.
Show them.