Participants

Topics

• Interface between rda-clients and the timing-receiver(TR)
  • The idea is, to have:
    • Some expert-properties to configure the timing-receiver remotely ( Diagnostic, Configuration, Firmware-Update, .. )
    • A value-item in the GSI-status-property of Equipment-classes to display the state of the timing-receiver
  • Alexander Schwinn presented some proposals (see attachment)
  • A missing use-case in the proposals was the usage of multible fesa-binaries (deploy-units) on the same FEC
  • This scenario would bring some naming-problems for proposal (A) and (C)
  • Proposal (B) would bring to much timing-details to usual equipment-classes.
  • After some discussion Dietrich Beck suggested to have a dedicated FESA-binary for the timing-receiver on each SCU. The FESA-class in that binary would provide all expert-properties for the timing-receiver. ( See picture attached )
  • The equipment-classes itself will only have two additional value-items in the status-property
    • e.g. "statusTR" which can be ok/warning/error/notAvailable
    • e.g. "deviceNameTR", device-name(nomenklature) of the timing-device (automatically filled by the framework if possible)
    • (Naming of the items will be discussed in next FE-Int meeting)

• Format of the timing-data, received by the TR
  • Is not yet known / ongoing discussion between CCT and timing-team

• Cosylab-class AI4s
  • Matthias Wiebel and Barbara Grasmück were a bit confused by the value-item "ai4sstatus", located in the GSI-Status-Property.
  • The bit's described in this items probably should be moved to the detailedStatus
  • Likely the class was implemented by the use of fesa v0.8.1. In 1.0.0 the updated detailed-status provides a label for each bit, so the client as well directly can obtain the meaning.
  • Matthias Wiebel and Udo Krause will first re-check how it was done for other classes and than talk to the cosylab-developers.

• FESA-Workshop November
  • At CERN
  • less participants, more like a real workshop this time
  • main topic so far: The transactional-service
  • if there is enough time, Udo proposed to as well take care for multi-language support of the FesaExceptions (see next bullet)

• The Message-Compiler
  • Ludwig Hechler presented the concept which currently is in discussion for the message-compiler. ( See linked wiki-page)
  • In the current concept, e.g. the error-messages of fesa-core would be an exceptional-case.
  • After some discussion different proposals were made which will be considered by the CCT.