1 / 5

EPICS Release 3.15

EPICS Release 3.15. Bob Dalesio May 19, 2000. Features for 3.15. New Abstract Data Object Portable server replacement of rsrv Replace GDD Periodic Monitors Remove String Length Limitations (Put off until 3.16) Name Length String Length Replace dbStaticLib with new link support

bretw
Download Presentation

EPICS Release 3.15

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. EPICS Release 3.15 Bob Dalesio May 19, 2000

  2. Features for 3.15 • New Abstract Data Object • Portable server replacement of rsrv • Replace GDD • Periodic Monitors • Remove String Length Limitations (Put off until 3.16) • Name Length • String Length • Replace dbStaticLib with new link support • Extendible Link Support • Support Dynamic Link Modification

  3. The New Data Object Is Enabling Technology that has no Immediate Advantage to the Users • Currently there are two channel access servers to maintain: rsrv which serves the EPICS database and the portable server which serves all other data stores. This creates a problem for maintenance. • The new data object improves the situation for composite data in two ways: 1) by providing a mechanism for sending composite parameters only when they change. 2) by providing a method for defining new composite structues – like a statistics monitor which could be used to access data from an archiver or statistic records (refer to earlier talk) With the new data object and upgrades to the protocol, new event types – like monitor frequency deadbands and client specified deadbands, will be easily implemented.

  4. The New Data Object Is Enabling Technology that has no Immediate Advantage to the Users • Currently there are two channel access servers to maintain: rsrv which serves the EPICS database and the portable server which serves all other data stores. This creates a problem for maintenance. • The new data object improves the situation for composite data in two ways: 1) by providing a mechanism for sending composite parameters only when they change. 2) by providing a method for defining new composite structues – like a statistics monitor which could be used to access data from an archiver or statistic records (refer to earlier talk) With the new data object and upgrades to the protocol, new event types – like monitor frequency deadbands and client specified deadbands, will be easily implemented.

  5. Conclusions • With a sabbatical to Ralph Lange and the support of SNS for Jeff Hill, we were able to move forward on the abstract data class, measure and optimize the performance, and integrate it with the EPICS static database library • With the addition of Andrew Johnson at Argonne, we are able to assign someone full time to the solution of the link problem that we have lived with since the beginning of EPICS – in a more complete way than the ‘@’ hack. • We are making major structural changes in 3.15 that will break a log jam of over taxing of our original interface, code structure and protocol. • Having some dedicated resources to attend to these issues is alloowing us to move forward on difficult and costly structural changes.

More Related