User Oriented APIs for Timing System Jim Chen Hytec Electronics Ltd Timing Workshop – 5 th June 2014, Prague

The Problem Jim Chen Timing Workshop – 5 th June 2014, Prague Hytec Electronics Ltd MRF timing module now has many functionalities rather than purely trigger generation. These include timestamp, event FIFO, data transmit and even GPIO etc. This is excellent! Timing system also has many ways of generating signals – distributed bus, events, sequencer, prescaler etc. This is also good. Variety of outputs – TTL, LVPECL, CML, Univ I/O. Great! Many form factors. One of the problems – functions are not always to all platforms Not easy to configure – especially for new comers

What we end up Jim Chen Timing Workshop – 5 th June 2014, Prague Hytec Electronics Ltd MRF provides low level APIs for VxWorks/RTEMS and Linux Each lab has its own app implementation. mrfioc2 Cosylab Taiwan Light Source – TPS pciGeneral Device Support Hytec UDP for Orion, APIs for ELI, NUS …… Re-invent the wheel from time to time and it continues

What end-user needs Jim Chen Timing Workshop – 5 th June 2014, Prague Hytec Electronics Ltd Triggers!

What end-user needs Jim Chen Timing Workshop – 5 th June 2014, Prague Hytec Electronics Ltd Generate repetitive triggers in different frequencies Fire single shot Set delay/relative delay and width for each trigger Enable/disable triggers/modules Set up timestamp Transfer data Interrupt notification and callback etc…

What would be nice Jim Chen Timing Workshop – 5 th June 2014, Prague Hytec Electronics Ltd Trigger implementation transparent to the user – EvrSetPulseProperties, EvrSetPrescalerTrig, EvrUnivDlySetDelay, EvrSetFineDelay – hide all these! User function oriented rather than device function oriented A Generic API function set for all platforms – EPICS, TANGO, OPC, VxWorks, Linux and Windows Maintained by community or by Jukka?

How easy to achieve this Jim Chen Timing Workshop – 5 th June 2014, Prague Hytec Electronics Ltd Not easy given so many options Need well defined structures Need many branches to distinguish architecture differences, signal generation differences, trigger type differences, output type differences, jitter requirement and accuracy differences etc. Separate the OS specific from the generic APIs Proper interrupt mechanism and callback Endian issue

What we can do Jim Chen Timing Workshop – 5 th June 2014, Prague Hytec Electronics Ltd

The main entities Jim Chen Timing Workshop – 5 th June 2014, Prague Hytec Electronics Ltd OS resource wrapper – base address, interrupt, DMA if required Jukka’s low level APIs Trigger structure – need to cover all aspects Trigger – need to encapsulate all operations EVG – capable of defining trigger source or the combination EVR – simple class

The implementation Jim Chen Timing Workshop – 5 th June 2014, Prague Hytec Electronics Ltd Let’s discuss……