1 / 7

Conversion to EPICS R3.14

Conversion to EPICS R3.14. Mark Rivers. Outline. New capabilities Progress in converting synApps/GSECARS Outstanding issues Work to be done. New Capabilities. Canberra AIM software runs on any system with libnet and libpcap (Linux tested, Solaris and even Windows should work)

ira
Télécharger la présentation

Conversion to EPICS R3.14

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. Conversion to EPICS R3.14 Mark Rivers

  2. Outline • New capabilities • Progress in converting synApps/GSECARS • Outstanding issues • Work to be done

  3. New Capabilities • Canberra AIM software runs on any system with libnet and libpcap (Linux tested, Solaris and even Windows should work) • DXP software runs on Linux with XIA’s Saturn model (uses EPP parallel port) • All synApps device-independent records run on Linux • mpfSerial runs on Linux, all serial support in synApps should work (e.g. Keithley 2000, serial motor controllers, etc.)

  4. What is synApps • motor (motor record and devices) • mca (multi-channel analyzer) • ip (serial devices) • ip330 (A/D IP module) • dac128V (D/A IP module) • ipUnidig (binary IP module) • camac (CAMAC support) • dxp (XIA DXP for CAMAC and parallel) • quadEM (APS quad electrometer VME/fiber) • std (everything not in above! New records, scaler, etc)

  5. Progress in Converting synApps to 3.14 • Goal: Convert all of GSECARS sector 13 to 3.14.3 during the current shutdown (September 03). • Philosophy to date • Convert all non-VME specific support to OSI • Convert VME-specific code to OSI system calls, except hardware communication • Convert VME hardware communication to devLib so it can work with RTEMS • Following applications are “complete” in steps 1-2 above • ip330, ipUnidig, dac128V, camac, dxp, mca, quadEM • motor • ip needs MPC • std needs conversion of some devices

  6. Outstanding issues • devLib API is not complete • Does not support the “fpp” context for saving/restoring floating point context in interrupt routines. Need to enhance? •  mpfSerial on vxWorks no longer supports setting parity, stop bits, etc. • Should change generic serial record to not set device parameters at initialization? • VXStats device support • Scaler record/device support sometimes crashing non-Joerger scalers • Issue with CA and sequencer (current tech-talk thread)

  7. Work to be Done • Complete std conversion • See Outstanding Issues • CCD detector support. I’ve started this. • I’ve started on this. Common EPICS interface for control of CCD (and image plate) detectors (Roper, Bruker, MAR). • Common database and multiple SNL programs. • SNL programs will automate manufacturer’s control program (WinView, marCCD, etc.). • Different approach from Brian Tieman’s CAS server, which goes to DLL layer, bypassing manufacturer’s control program. • Industry Pack on Linux? Would make Linux IOC a viable approach for “small” beamline or lab. • Documentation!!! • Distribution

More Related