JCOP FWWG 30 Dec 2021: FSM

→ Europe/Zurich
Zoom Meeting ID
63803187812
Host
Piotr Golonka
Useful links
Join via phone
Zoom URL

JCOP Framework Working Group Meeting

30 November 2021

Main topic: new features in the fwFSM and SMI++

Participants: Boda Franek (Presenter), Clara Gaspar (Presenter), Ivan Atanasov, Geraldine Thomas, Lukasz Goralczyk, Wassef Karimeh, Piotr Golonka, Cristina Vazquez, Mariusz Suder, Juan Manuel Pablo Rodriguez, Frank Glege, Stefan Schlenker, Valeri Falaleev, Alexander Kurepin, Paris Moschovakos, Christophe Pires

INDICO Event: https://indico.cern.ch/event/1098718/

 

In the first part Boda presented a few of new features implemented in SMI.

Note: in the slides there are small blue circles next to items. Clicking them unveils additional explanations

Questions/comments

  • is there any use of having object param's name and action param's name the same? Well, for compatibility but these may be really pretty misleading;... Clara explains, with an example,
       StartRun(runType=runType)
  • the documentation improved a lot. There are links to it directly from the FwFSM web page .
  • allowing empty IF instruction block during the translation of FSM code: the reason for it was that sometimes the fwFSM was generating the code with such construct, and it was crashing the translator.. Now it  simply behaves like waiting.

 

In the second part of the presentation clara summarized the status of fwFSM and demo'ed the new features

  • Reminder: the code included in the libraries listed in slide 3 is kept backward-compatible (public API). This is NOT guaranteed for other libraries though...
  • The "SMI++" link in the fwFSM web page is "dead" => [already corrected by Clara]
  • The FwFSM panel for editing object types now allows to list/edit FUNCTIONS. Note that the "Action List" is now a combo box, rather than a button. Toggle it to "Functions List" and you will see the list of SMI functions
  • Note that some instructions in the combo box (e.g. "wait for") are still not displayed, even though they are valid
  • The new REPORT function of SMI is now integrated into fwFSM. It makes a dpSet to the ".userMessage" element of the internal DPs for Control Units (of _FwCtrlUnit DPType).
    • note that by default these messsages are NOT sent to the log and NOT integrated to UI
    • one can dpConnect to it and, for instance, use fwFsmUi_report() to send it to the "Messages" box in the FSM UI; double-clicking o the "Messages" shows them even better, coloured, in a popup window.
    • ... or send them to the log
    • there is also anothed DPElement ".smiMessage" that gets the messages generated by SMI itself.  
  • There is a feature to have some code executed when a user panel is closed (either using the "x" or the "Close" button). It is sufficient to declare a public function in the panel called fwFsmUser_close()  and it will be called. This allows to do various cleanups, etc.
  • You may want to declare how to allocate the devices into CTRL scripts. Go to the "Settings" of a Control Unit  and you have options to have a Ctrl manager per all, per subtree or even per DU. This allows to spread the load to many Ctrl managers if necessary.
    • what if this is declared also in a child item? Clara to check...
  • There is a  very new FwFsm v34r16 available on the FwFsm pages and it is based on the latest SMI code and contains these new features.  Note that this version is NEWER than the version included in the jcop-framework-8.4.2.
    • Upon request from CMS expressed during the discussion, there is also a link to the previous v34r15 to make it possible to separate the UI and SMI changes, etc.
    • Clara recommends that v34r16 should be tested before applying to production as the amoun of testing was limited. 
  • A note: the FSM Training Course materials should be updated to cover all these!
  • A suggestion from Frank: having SMI implemented as a library (API) rather than an executable. Like that it would be possible to implement things in C++ rather than have people learn the SMI-specific nomenclature. Could there be some callbacks exposed?
    • Clara explained that the SMI already has this constructs - the Device Units are "proxies" in SMI++, and their implementation may be done in C++: it is an API for object to receive commands... Extensing it (to have shared actions?) would be very complex to implement, and Clara would rather extend the functionality of logic (e.g. implementing LOOPs, etc). This may be discussed further: not impossible, but obviously a design choice in how one would implement the FSM.

 

Next FWWG: scheduled for 14 December 2021, covering the proposal of new CAN-Ethernet bridge, status update of CANModule and the requirements of fwOpcUaToolbox.

 

 

 

There are minutes attached to this event. Show them.