JCOP FWWG 17 Sept 2024
JCOP FWWG Meeting, 17 September 2024
Present (in Person) : Pavel Fiala, Ben Farnham, Mariusz Suder, Stefan Schlenker , Clara Gaspar, Luis Cardoso, Piotr Golonka (chairman)
Telepresent (over ZOOM):
Christophe Menezes Pires, Mateusz Lechman, Raul Jimenez Estupinan, Luis Miguens Fernandez, Piero Giorgio Verdini, Lukasz Goralczyk, Marcin Bes, Maria Toms, Alex Savulescu, Valeri Falaleev, Vazquez, Cristina, Soham Biswas, Michael Ludwig, Ombretta Pinazza, German Martinez, ebru, ebismek
WinCC OA, JCOP Fw & OPC-UA Status report
see the slides in INDICO
Status of the new Trending component
limited to a short summary only due to lack of time. PLEASE SEE THE PRESENTATION IN INDICO for more details.
Discussions, clarifications
OPC Servers:
BenF asked about the need to deliver CanOpen OPC Server on Windows, and if it is acceptable/worth to investigate a solution that would allow to run the Linux version of it in Windows machines, e.g. via containers.
- CMS would like the native version.
- ALICE would also strongly favour a native version as this is what they run now
Discussion of support for non-standard ELMB (and other equipment) that would need to be supported by the CanOpenNG
- There are no non-standard ELMBs in LHCb.
- NA62 has 2 non-std ELMBs and custom boards speaking CANOpen, and needs to have them supported by the CanOpenNG, because the current CanOpen works fine with them
- Stefan Schlenker (ATLAS) explained: the new CanOpenNG really supports the same CanOpen spec as the old server; it is a matter on how things need to be configured. It also depends what one considers to be a "non-standard" equipment
- ELMB with a custom firmware that was an extension of a standard ELMB firmware (e.g. extra functionality, etc) should work just fine, and the automated migration (provided by the fwELMB component) should also work fine.
- Completely custom ELMB firmware - should work fine, but the configuration would need to be done manually
- Other CanOpen devices - similarly to the above; as long as thet behave following the CanOpen specification it should be possible to configure them manually
- After all, it all boils down to the level of support that is expected notably for configuration (or migration of it). The new CanOpenNG should work with all compliant CanOpen devices, yet may require finding out how to configure it to speak properly to non-standard devices.
- When should we expect CanOpenNG OPCUA server working with ANAGATE can-ethernet bridges?
- LHCb originally planned to migrate end of this year (probably next year though...). The reason is that sysadmins would like to eliminate the old "credit-card PCs that acts as interfaces and may not be upgraded to a newer OS, yet this is not extremely urgent as these ares still working fine
- for ATLAS a similar migration to Anangate is planned duing the LS3
- Luis and Pablo are working on this right now - we will inform about the progress (so far so good)
- LHCb afraid of being the first to adopt the new solution. Ben reassures that significant amount of testing will be done in the BE-ICS labs
Alarm Screen NG
NA62 already tried and it looks very well; still, the version that was tested did not allow to emit sound when an alarm comes.
Luis clarified that this feature will be available in the upcoming version as an "alarm action" in CTRL
LHCb has another solution for this, which does not rely on the fact that the alarm screen panel is displayed, but rather does an alarmConnect() to all alarms and then orders to machine that has loudspeakers connected to emit a sound.
Clarification for status in ATLAS: no outstanding issues pending to be implemented by BE-ICS. What is missing is resources in ATLAS necessary to develop on top customizations of NGAS. NGAS itself considered to be fine.