Minutes
- Digital twin
- NXCALS properties defined by Ralf via email (after meeting on the 24th of April) sufficient for Oda to continue with the development (pdf with email attached)
- question on publication of state violation boolean -> concluded to not log this in NXCALS, as this can be retrieved from set point and readout data later (if needed)
- optional: String with status message to be logged? Suggested by Ralf, concern raised by Cedric that this will be difficult as DB is not made to log strings
- FPGA in cRIO will allow for RealTime communication: Oda is working on implementing which will allow the system to run self sufficiently (even if PC connection is lost)
- code runs both on the digital twin and FPGA: this will allow the code to be included in continuous integration -> more easy to maintain longterm for the future
- sensor reading can be simulated/tested on digital twin before recompilation of FPGA -> testing should be fully achieved with minimal downtime for flashing the hardware
- timeline hardware purchases (consolidation of obsolete components)
- Cedric has quotes from early 2025 -> these should be updated
- timeline for update: Decision on laser system requirements (number of lasers -> flow meters, alcohol detectors, ...) to be defined by July
- purchase to start after this is well defined to make sure hardware is as up to date as possible at time of commission foreseen in Q2 2027
- cable inventory to be done from existing to see which cables need to be requested from service
- cRIO spare: lead times are "short" with some week BUT during operation failure will lead to critical downtime -> system requires options for hot swaps. Cedric comments that possibly the spares could be built directly into the system with an option to switch as soon as error state is observed -> decision should be made in time for purchase process
- status consolidation of existing software in LV2025
- decision has been made to use the obsolete code solely for checks of properties and decision trees
- LV2025 would not work with existing cRIO, so code would need more time investment to adapt to either new hardware or old one (which will be replaced anyway)
- test setup with circulator and flow meter?
- decision made that the digital twin SHOULD make this step obsolete
- test can be done during commissioning in the lab
- flow meter options (discussed briefly on the 24th of April) could be revisited -> externally clamped flowmeters to allow faster switches with less exposure to chemicals
- timeline/scheduling work on PE lab projects (consolidation of hardware and software)
- PE lab getting ready fro production run of photo cathodes
- most code and hardware does not need immediate replacement
- status and summaries of codes and requirements to be prepared by Ralf
- optionally: production software (relatively new code, prepared by MTA) is object oriented code, ANGARA can be considered for providing new code to have data logging up to current standards and better configuration
- Ralf will prepare an overview of his requests for the cathode production code for review with ANGARA to speed up this part of the PE lab CONS
- Next meeting:
- meeting for week of June 8th -> Kati will send an invite
- Oda will present digital twin status with first simulated inputs for review
related to BE-CEM cons contribution defined in EDMS 2254500
documentation provided by MTA on RMPS can be found in wiki