1 / 13

FECOS

the best people make cosylab. FECOS. Matej Sekoranja (matej.sekoranja@cosylab.com) … on behalf of CSL MA team. WHAT is FECOS?. Google says… … well, MA FECOS is something else . WHAT is FECOS?. F ront E nd Co ntrol S ystem purpose built NI LabView Real-Time framework.

foster
Download Presentation

FECOS

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 FECOS Matej Sekoranja (matej.sekoranja@cosylab.com) … on behalf of CSL MA team

  2. WHAT is FECOS? • Google says… • … well, MA FECOS is something else 

  3. WHAT is FECOS? • Front End Control System • purpose built NI LabView Real-Time framework

  4. WHERE is FECOS? FECOS

  5. WHY FECOS? (1/3) • FECOS provides uniform communication: • communication protocol is completely hidden from the programmer • autonomously selected by the framework

  6. WHY FECOS? (2/3) • FECOS provides uniform operation: • each component implements general state machine

  7. WHY FECOS? (3/3) • FECOS provides standard “services” : • logging and error reporting • local to file and remote (via DIM) • timing system support • standard configuration services • local file, HTTP • watchdog and host health-status monitoring • … etc. … Programmer focuses on control logic

  8. Timing Receiver Component CERN DIM Component Vacuum Pump Controller Component Valve Controller Component Logging and Error Handling Component EXECUTIVE FECOS Architecture (1/2) • Modular, component based, event driven

  9. Architecture (2/2)

  10. OO design (LVOOP) (1/2) • Based on LVOOP • LV2009 needed to work on RT • Extensive use of “by reference” • We do not want to make “by value” copes of classes! … see next slide …

  11. OO design (LVOOP) (2/2)

  12. WHEN FECOS? • Design finalized until September • FECOS beta planned in October! Thank you!

More Related