EPICS: operating system independent device/driver support

Originally EPICS input/output controllers (IOCs) were only supported on VME-based systems running the vxWorks operating system. Now IOCs are supported on many systems: vxWorks, RTEMS, Solaris, HPUX, Linux, WIN32, and Darwin. A challenge is to provide operating-system-independent device and driver support. This paper presents some techniques for providing such support. EPICS (Experimental Physics and Industrial Control System) is a set of software tools, libraries, and applications developed collaboratively and used worldwide to create distributed, real-time control systems for scientific instruments such as particle accelerators, telescopes, and other large scientific experiments. An important component of all EPICS-based control systems is a collection of input/output controllers (IOCs). An IOC has three primary components: (1) a real-time database; (2) channel access, which provides network access to the database; and (3) device/driver support for interfacing to equipment. This paper describes some projects related to providing device/driver support on non-vxWorks systems. In order to support IOCs on platforms other than vxWorks, operating-system-independent (OSI) application program interfaces (APIs) were defined for threads, semaphores, timers, etc. Providing support for a new platform consists of providing an operating-system-dependent implementation of the OSI APIs.