contracting turn key systems with epics

Download Contracting Turn Key Systems with EPICS

If you can't read please download the document

Upload: rafiki

Post on 08-Jan-2016

35 views

Category:

Documents


0 download

DESCRIPTION

Contracting Turn Key Systems with EPICS. Mark Pleško. mark . plesko @cosylab.com. Contracting Turn Key Systems with EPICS. What is Cosylab Standards and EPICS Two sample turnkey systems Cosylab is subcontractor for CS Technical issues Organizational issues. Cosylab. - PowerPoint PPT Presentation

TRANSCRIPT

  • Contracting Turn Key Systems with EPICSMark [email protected]

  • Contracting Turn Key Systems with EPICSWhat is CosylabStandards and EPICSTwo sample turnkey systemsCosylab is subcontractor for CSTechnical issuesOrganizational issues

  • Cosylab1997-2000 ANKA CS: cheapPC, commercial fieldbus, own I/O2001 students finish, start companyProfessional: work to spec/wishes + documentationCS development and integrationDevelopment more fun, but difficult to sellVDCT, CAJ, Abeans, ACS (CORBA for astronomers)2004 10 employees, 10 external, 15 studentsAdd: GIS, Telecom, Automotive electronics

  • Cosylab Abeans Customer Base

  • // description of read-only double channel struct RODoubleDesc { double graphMin; // minimal value on graph double graphMax; // maximal value on graph double warningMin; // below this warning color is enabled double warningMax; // above this warning color is enabled double alarmMin; // below this alarm color is enabled double alarmMax; // above this alarm color is enabled string unit; // units string format; // format of value string description;// description of value double minStep; // minimal possible change in value };

    // description of read-only double channel struct RWDoubleDesc { double minValue; // minimal allowed value double maxValue; // maximal allowed value double graphMin; // minimal value on graph double graphMax; // maximal value on graph string unit; // units string format; // format of value string description;// description of value double minStep; // minimal possible change in value };

    /* Possible conditions of a physical device or its state. The names correspond to colours of typical LEDs. GREY corresponds to the LED being off. */ enum Condition { RED, YELLOW, GREEN, GREY }; typedef sequence ConditionSeq;

    typedef sequence stringSeq;

    // description of read-only status (pattern) channel struct ROPatternDesc { string description; // description of the status channel stringSeq bitDescription; // string description for each single bit in status ConditionSeq whenSet; // describes wich color has status bit when it is 1 ConditionSeq whenCleared; // describes wich color has status bit when it is 0 };

    /*------------------------*/ /* Power Supply Interface */ /*------------------------*/ interface PowerSupply : Device { // sets new setting on server long setCurrent(in double dCurrent); // reads teh setting on server long getCurrent(out double dCurrent); // returns description for current channel readonly attribute RWDoubleDesc currentDesc;

    short retPutOn(); short retPutOff(); short retPutReset();

    // Returns read-only status of device. Each bit has special meaning, which is described in description part long getStatus(out long status); // Returns description of the status. readonly attribute ROPatternDesc statusDesc;

    // Returns current readback measurement. long getReadback(out double ampVal); // Returns structure with description of read-only current readback. readonly attribute RODoubleDesc readbackDesc;

    };

  • Outsourcing, Turnkey and StandardsIn-house systems are proprietary and not openDoesnt matter if free or with source codeDifficult to outsource: extensive learning timeImpossible to buy turn-key: who is responsible for bugs?Example ANKA: turnkey booster, but without CSLessons from human history: need standards

  • EPICS as Standard (1/2)[whether EPICS is a de-facto standard is left as an exercise to the reader]Is sufficiently stable and known that labs can expect equipment vendors to know and support itHas sufficient market share that it is worthwhile for equipment vendors to considerHas cases of excellent documentation and courses so that anybody can learn itFortunately for Cosylab, EPICS is still not easy

  • EPICS as Standard (2/2)International tenders for equipment require EPICS, such as:Australian Synchrotron Project (ASP)Turnkey injector (linac+booster synchrotron) with control system (not necessarily EPICS) that integrates into ASP EPICS systemDiamond Light Source (DLS)EPICS required, DLS even free issues hardware and developing environment to ensure compatibilityClarificationsASP linac and RF including EPICS subcontracted to Accel and PPT, Cosylab makes only booster CS

  • Particularities of the Control System SubcontractFixed price contractTime management is a big problem: we have to sell our time but not oversellIf project is delayed for any reason, we cant just get a new project to fill the hole => we lose money!Commissioning included in price, additional help is extraContractor (our client) wants to control communication with the lab (end user)Understandable, but slows down progressGood direct relations with end user are essentialCosylab is lucky that it comes from the community

  • Status of ASP Booster and DLS Diffraction BeamlinesSlideshow.....

  • Technical IssuesEPICS community support much better than commercialasynDriver (in particular Marty and Eric)PLC S7 driver (Dirk) paid by PPT (on Danfysik contract)DG535 (delay generator) device support (Marty)autoSaveRestore (Tim Mooney) for bumpless rebootcaSR (John Winans, ?) channel access save/restore (snapshot)stream device (Dirk), given to us by DLSmotor record, transform record, sscan record, waveAnl record (Synapps package, APS beamlines)Lots of commercial devices with serial/GPIB interfacesUse our microIOC (embedded PC box with EPICS - see presentation on Friday) to integrated and decouple from the rest.

  • Organizational IssuesNeed each type of equipment at our premisesSoft records -> protocol simulator -> 1 device connectedPrefer to work at homeEarly visit to build trust in our competencesInstall at factory on all devices, first acceptanceParticipate in commissioning on site, final acceptanceDiplomacy is importantHow to be committed, but still get paid for all the extra work?Refering to specs and contract just doesnt workSometimes need to negotiate between contractor and end userWe usually deliver more than internal people, just because we know that we get only paid at the end!

  • ConclusionsWill equipment vendors provide EPICS inside? yesWill they still need integrators like Cosylab? Yes (I hope)Will EPICS become a monopoly? NoBut labs will have to decide on some standard, else they will pay a higher priceLabs can accelerate this development by requesting EPICS for each piece of equipment!Everyone will profit (wink, wink )