JCOP FWWG 19 March 2019: fwQuasar
JCOP FWWG Meeting, 19 March 2019
News:
- JCOP Framework 8.3.1 released consolidating a few minor bugfixes/changes; new version of fwInstallation 8.3.1 is required and it regularizes the way the config-file snippets of components are inserted into the main config file
- WinCC OA 3.16 patch P007 released by ETM. Will be available for downloads shortly. Next 3.15 patch around and of this week. 3.16FeaturePatch expected at the end of April
- visit to ETM: reassuring news for WinCC OA contract renegotiation. Discussed 3.16 vs 3.17 choice: many of features of CERN interest will be backported to 3.16 anyway.
- following the CTRL++ workshop the list of requirements/wishes was transmitted to ETM and priorities and possibilities discussed. As agreed, features will be implemented in patches this Spring (3.16Feature Pack and later).
Q: What about direct-I/O? ETM is working on this in the scope of the future WinCC OA version; progress with OPC-UA driver being made now. Certainly not possible to backport to 3.16, hence it won't be able available for production earlier than for LS3.
New mechanisms for password encryption in the RDB Archiver:
see presentation from Rafal for details
It was acknowledged that the proposed mechanism to update the passwords would be welcome. The tool would recognize the format.
Q:How about a postInstall script for a component? Discarded - one needs to have control of when the migration happens.
Agreed that a function in fwRDBArchiver will be sufficient.
fwQuasar component
see presentation from Piotr N.
Q: Approach is opposite to what was typically applied in the JCOP Framework, whereby devices were modelled in a JCOP DeviceEditor&Navigator and then the configuration file for the OPC server was created.
=> the new OPC-UA servers often provide auto-discovery of the hardware, and then they produce the config files. Interfacing such auto-discovery into SCADA would be an additional effort. There are already numerous use cases in ATLAS where such approach for the new OPC-UA - based setups is taken.
=> Note that auto-discovery is not always suitable - what if the hardware is off and hence cannot be discovered? The use of config file then is a partial solution to the problem.
=> the approach is actually not in contradiction to JCOP, but rather complementary, provided that further integration into device model would be possible, and the user is still given a choice.
Q: Compatibility with the JCOP Device Model
=> noted lack of "vendor node" in the datapoint names in examples. Not a fundamental problem
=> integration with device definition - problems indicated in backup slides of it being too rigid; Piotr commented that there are concepts of extending the device definition to make this part much more flexible (discussion taken offline)
Q: Why SCADA could not simply browse the OPC-UA namespace to create instances?
=> The OPC-UA browsing mechanisms seem to be limited (?) To be followed up (reported to ETM?) One would need reference types, target addresses and attributes. No support for OPC-UA methods either.
Q: How to address the evolution of the DPType?
=> the idea is to provide a diff tool showing what change w.r.t original design, so that the developer would at least know this... Under discussion
Q: ATLAS have their own OPC-UA server for Wiener equipment, based on Quasar. It is used as an example in Piotr's presentation
=> ATLAS OPC UA Wiener is there due to historical - it was needed at some moment to migrate ATLAS to Linux, yet at the moment the official one is released, it will be adopted. The server should be compatible with the fwWiener component to some degree.