50 likes | 276 Vues
Introspection. Control System Group – Bob Dalesio presenting EPICS Meeting May 2, 2009. Requirements. Provide information to the operator without knowledge of the PV names
E N D
Introspection Control System Group – Bob Dalesio presenting EPICS Meeting May 2, 2009
Requirements • Provide information to the operator without knowledge of the PV names • Provide displays of information that covers functional subsystems such as vacuum, temperatures, beam position, state of health. • Provide the data in a meaningful order.
Search Using Name A Naming Standard Provides A Portion of This. But – the Naming Standard has to be good - and what about additional information Psy:PI-Ssy:SI-Tsy:TI<Dev:DI>Sg:SgI-SD System Device Signal
Name Mapping Mid Level Data Client/Server Application / Family Channel Access EPICS Client/Server Dipole Quad Sext. Corr. BPM RF Function Based Applications In IRMIS or some table, provide the mapping for specific fields of specific records for functions and attributes that are to be supported. Request By Function, Area, Subsystem Return list of channels and some location information in PVData Conversions Standard Channel Access Functions To get data Name Mapping Distributed IOC Process Databases Designed lattice & installed hardware seq
Final Comments • This idea is not new. Operators continue to recreate this sort of functionality. Sasha presented such an application for beam loss monitors. • This should be a straight forward extension to IRMIS. Most of this information is already planned. • A minimum number of PVData structures should support this. PVData is being supported over Channel Access V3 as well as JCA so the network communication should come free. • A set of applications for tables, bar charts, and waterfall plots are planned.