1 / 8

Overview of the work : - MACS Column - IS + LLRF

A detailed look at the work conducted by Joze Dedic on behalf of CSL MA team Cosylab, covering responsibilities and progress made in projects like Ion Source, LLRF, C# development, and more in 2011.

ignaciog
Download Presentation

Overview of the work : - MACS Column - IS + LLRF

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. the best people make cosylab Overview of the work:- MACS Column- IS + LLRF Joze Dedic (joze.dedic@cosylab.com) … on behalf of CSL MA team

  2. Cosylab CWO-3 responsibilities • FECOS – Matej, Miha (31 PW) • PCC – Luka (79 PW) • REDNET – Rok (60 PW) • Ion Source – Tilen (18 PW) • LLRF – Klemen (24 PW) • TINE <-> LabVIEW – Miha • C# development – Sunil (20 PW) • STM/SIM/MAPS – Matej (13 PW) Cosylab 2011

  3. Ion Source – 1/2 (Tilen’s visit to Pantechnik) • Introduction to IS HW, operation and LabVIEW panels (part of standard solution) • Defined the interfaces for devices of the IS • Some devices for MA IS have not been defined yet • Pantechnik will provide a LabVIEW library of low-level VIs for device access. • Discussed operational procedures of IS • Start-up, shut-down • Regulation procedure • Until now IS was regulated manually by an operator • Apparently a complex procedure Cosylab 2011

  4. Ion Source – 2/2 (visit to HIT and further work) • Visit to HIT with Liviu • Further iterations on requirements from MA • How to fit the solution that Pantechnik provides to MA system • There is still some missing information • Next steps • EA model • Finishing the design • Implementation of FECOS classes • Integration visit to Pantechnik (end of June) • According to Pantechnik, IS will produce the first beam in July Cosylab 2011

  5. LLRF • Klemen joined the MA team, first round of requirements • tomorrow whole day on LLRF system; clarify picture • TINE <-> LabVIEW (Miha) (3 wk+) • 1) started building TINE DLL, to be called from LabVIEW • No code changed, only preprocessor defines (hint by Philip Duval, DESY). Result is a single DLL, to be used from LabVIEW on Win. • 2) started porting this single DLL to PXI Pharlap • Copying didn’t work, so we turned to NI for help and we got some suggestions. • Only "debug through logging" available. Still, we had problems, which we fixed with tech support. • 3) With debugging we made progress, modified the C and LabView code to get a "mostly working DLL". • The DLL works on PXI Pharlap, with occasional crashes. • Unfortunately crashes are now more random and we are investigating cause. Cosylab 2011

  6. C# development • chunks of C# development tasks • presently, one month of work is defined (mostly on PetriNet), the rest will probably change (time transferred to newly agreed tasks) • work goes smoothly • troubles: • different VMware images cause testing delays (dependencies…) • Sunil’s absence (illness) Cosylab 2011

  7. STM/SIM/MAPS • CWO-2 work reviewed • little minor things to be fixed • action plan • complete LV STM implementation • user manual and API to be documented • further actions to be defined and implemented • performance/stability tests • due date: until next MACS week • not much progress was done / low priority / Matej needs feedback • however, it is not a blocker for FECOS development Cosylab 2011

  8. PM • team of 13 people • rely on “NI-core” support, a lot of cases • two newcomers; Klemen and Tilen • up to speed with MA rules of work • CERN account • deliverables: • improved CWO report • ongoing acceptance • document modifications • clearly communicated to the team • requirement (= identified specific behavior, no matter how “low”) • proposed • impact evaluated • accepted • release deadline agreed Cosylab 2011

More Related