fwWiener-8.3.1-beta-01 with initial OPC-UA support.

From: Jonas Arroyo Garcia

Sent: 04 July 2019 3:01
To: Fernando Varela Rodriguez; Piotr Golonka
Subject: fwWiener-8.3.1-beta-01

I have ready a first beta for the fwWiener migration to OPC UA: native and migration from OPC DA.

Beta is available here: https://gitlab.cern.ch/jcopfw/devices/fwWiener/-/archive/fwWiener-8.3.1-beta-01/fwWiener-fwWiener-8.3.1-beta-01.zip

This beta has the following limitations:

-          Migration panel: all it is functional (migration, recovery, subscriptions creation, backup, etc...), except the button that allows you to unselect the crates to migrate “<---- Remove crate” (logic it is not straight forward, and I prefer to expend efforts in main functionality). As workaround you can close and open again the panel. Jira case: https://its.cern.ch/jira/browse/FWWIENER-189 

-          FwWienerDriver and FwWienerServer DPT I have migrated them natively, but are not migrated in the migration panel, as it is not clear, if obsolete structure (FwWienerDriver) needs to be maintained any longer. Also these addresses are not exposed by Wiener OPC UA server. Jira case: https://its.cern.ch/jira/browse/FWWIENER-194 and https://its.cern.ch/jira/browse/OPCWIENER-51

-          To be discussed in the JCOP WG if old device definitions and device models could be removed from fwWiener, including OPC DA/UA driver number 11. Jira case: https://its.cern.ch/jira/browse/FWWIENER-188

-          OPC UA managers 11 and 14 are not created automatically in the postinstall, until previous point will be clarified. Jira case: https://its.cern.ch/jira/browse/FWWIENER-192

-          Validation of native addressing: Jira case: https://its.cern.ch/jira/browse/FWWIENER-196  I have created a project called 316-Wiener-Test with the 3 crates configured from Ben in the lab, where I defined natively the crates and moved the connections to driver numbers 15,16,17. It is available here: https://cernbox.cern.ch/index.php/s/Mti1KosZ4Hys4d3 I have identify some issues in the OPC UA layer

-          After a fast look on the OPC UA items, I realized that some time counters were using float types to store second counts. As consequence these values are not readable by humans directly, also in supervision values needs to be decoded. I open a case to deal with these values on better way: https://its.cern.ch/jira/browse/OPCWIENER-52

Still missing:

-          Validation of migrated OPC DA setup, Jira case: https://its.cern.ch/jira/browse/FWWIENER-197

-          Validation of namespace and OPC item types between OPC DA and UA. Jira case: https://its.cern.ch/jira/browse/FWWIENER-191 It needs to be cross-checked the OPC items names, and value types between OPC DA and UA.

-          Validation of supported hardware in fwWiener component. We don’t have all equipment supported, it would be great to rent from pool or, connect to experiment equipment to validate the migration / conversions.

-          Review full component, looking for parts to deprecated, or upgrade due to the new middleware (UA). Jira case: https://its.cern.ch/jira/browse/FWWIENER-192

I feel sorry for delivery this on hurry, but the amount of work is really significant ( I was expecting around 3-4 weeks to do it properly) and it has been delivered in less of two weeks.

I don’t know if you want to release it as it is.

In my opinion, people could use it for testing and discover things that doesn’t work as expected, but not to configure new setups, as there are many things in the OPC UA layer that havent’ be tested enough to have a properly foundation.

Cheers,

     Jonas