EPICS Base 3 14 Status DIAMOND June 2003
EPICS Base 3. 14 Status DIAMOND June 2003 Marty Kraimer APS/ANL DIAMOND EPICS Meeting, 2003 1
EPICS Base 3. 14 Status EPICS 3. 14. 2 is the latest release ●Sequencer and gpib. Core available for 3. 14. 2. gpib from APS, sequencer from SLAC ●Build rules changed between 3. 14. 1 and 3. 14. 2 ● ● Simplified Everything by default uses shared libraries Future 3. 14 releases ● ● ● Major emphasis is stability Only minor enhancements Major changes will go into 3. 15 3. 14 releases will be bug fix releases 3. 14 has been put on CVS branch DIAMOND EPICS Meeting, 2003 1
Base 3. 14 Overview ● EPICS Main Goal for 3. 14: port ioc. Core ● vx. Works - 5. 4 (Tornado 2) required ● RTEMS - Open Source Real Time Operating System ● Solaris ● Linux ● Win 32 - NT, win 2000 tested ● Darwin - Open Source for Mac OSX ● HPUX-11 ● Base software is organized to minimize porting effort ● Marty Kraimer, Jeff Hill, Janet Anderson, Eric Norum, and Ralph Lange primary developers. ● Hardware Support ● ● ● vx. Works support unbundled RTEMS at both CLS and SSRL Requires major changes for non VME/vx. Works platforms DIAMOND EPICS Meeting, 2003 1
3. 14 Channel Access Features ● Large Arrays ● ● ● ● Both client and server must be 3. 14 Set CA_MAX_ARRAY_BYTES on both client and server Transparent to existing clients Purpose is ease of use not performance PCAS also supports large arrays. Multipriority CA servers - available in beta 1 ● ● EPICS Client must request, i. e. not transparent to existing clients. Provides incremential improvement for performance degradatation. Purpose is to allow inter IOC communication to have higher priority than other clients. No other new features for 3. 14 CA reference manual available via 3. 14. 2 WWW page DIAMOND EPICS Meeting, 2003 1
Binding to IOC components Base now build as shared or static libraries But rec. Sup/dev. Sup/etc located at run time How to get from library? Four dbd statement refer to code EPICS Recordtype, device, driver, registrar Perl script reads <app>Include. dbd and generates <app>_register. Record. Device. Driver. cpp This generated file causes the desired support to load Code must use one of the following: epics. Export. Address(<type>, <object>) epics. Export. Registrar(<func>) DIAMOND EPICS Meeting, 2003 1
Binding Continued epics. Export. Address(rset, xxx. RSET) epics. Export. Address(dset, DSETxxx) epics. Export. Address(drvet, drv. XXX) epics. Export. Registrar(xxx) EPICS xxx must be void xxx(void) xxx normally calls various registry routines Xxx will be called via register. Record. Device. Driver Should be register. Record. Device. Driver. Registrar : -) db. Sub. Example. c gives an example for sub. Record DIAMOND EPICS Meeting, 2003 1
Big Item for 3. 14. 3 Increase the reliability of the PV Gateway Status of latest version of PVGateway+ PCAS + CA On heavily loaded Gateway at APS: EPICS The CPU usage of the latest version is 1/7 th of the 3. 13 version Still crashes occasionally One failure results in gateway not responding but does not automatically get restarted Jeff Hill and Ken Evans are working on known problems I believe that 3. 14 is now more reliable than 3. 13 APS has great interest in VERY reliable PV Gateway and Nameserver. DIAMOND EPICS Meeting, 2003 1
- Slides: 7