FECC/SAIOC/RTEMS Making Lemonade

FECC “Slow” Code (in PC) –Ported iRMX code –By Bob Sass and Tony –As little hand work as possible –EPICS OSI layer –Dual NIC Regular Feedback/Pnet –Coexists with SAIOC –Uses SAIOC core functions –Receives PNET via Ethernet –Point-to-Point fiber serial connection to FECC Fast (new HW) –PPC embedded in FPGA fabric –IP only (no TCP/UDP) –Fast (NMI) code –Does BPM data –Receives PNET via fast link –Proprietary RTS –No debugging capability –Drives several busses SLAC CAMAC Standard CAMAC Bitbus

FECC Work by Sass, Gromme, Siskind Target date June 2006 PC side has PCIL serial link driver Driver useable by ported iRMX and EPICS Feedback to run in PC Feedback to use UDP instead of KISNET Replaces multibus & micro

Current Micro Setup Multibus crate With Multibus Format Intel CPU Camac SLCNET to VMS CAMAC Branch Driver PNET broadcast

FECC Setup PC running in MCC Camac Ethernet to VMS PNET broadcast (Ethernet) FECC Running Camac control And BPM acq. Point-to-point fiber serial link Standard Camac Bitbus

Software Division “Slow” Message Database Magnet Stat Anlg Fast BPM, Timing (360 Hz int) “Slow” Message Database Magnet Stat Anlg Fast BPM, Timing (360 Hz int) iRMX Multibus Micro RTEMS or Linux PC FECC Camac commands PNET, BPM FECC Driver + PCI card The ethernet PNET broadcast means there are hard realtime requirements

SLC-Aware IOC (SAIOC) EPICS OSI as basis SLC part looks like micro EPICS part does I/O EPICS part is separable from SLC part Only BSAC (BPM) and Magnet support All analog/digital in EPICS only Used as basis for FECC iRMX port

SLC-Aware IOC Modified SLC-style Messaging Database Task dispatching Pure EPICS Implementation Communicating With rest of VME Crate and hardware Ethernet communication to VMS This code uses the EPICS OSI implementation. It is currently developed on a linux platform and run on RTEMS in a VME crate. It is designed such that VMS sees this aggregate as a micro but that it can run as an EPICS-only implementation later

SLC-Aware IOC with FECC Modified SLC-style Messaging Database Task dispatching Pure EPICS Implementation Communicating With Hardware By sharing the FECC driver with iRMX Ethernet communication to VMS Port of rest of iRMX Code. FECC Driver This runs in A PC, just like The pure FECC Idea. System is Linux or RTEMS. E Add EPICS record support for camac addressing via FECC Camac branch

FECC-PC to EPICS migration One driver for FECC works for both EPICS and ported iRMX code FECC-PC is a modified SAIOC Only fast part remains BPMs Treat FECC as CAMAC fieldbus for EPICS Add EPICS support for FECC –Move Analog/digital/etc. to SAIOC style –Or just move analogs/digitals/etc to EPICS

Where does this lead? EPICS can slowly take over all functionality FECC becomes CAMAC fieldbus only PCs running RTEMS allow slow migration to EPICS Application migration is totally separate

FECC MPG Old MPG uses PNET, no Ethernet capability FECC MPG will broadcast over Ethernet –MPS Supervisor is Ethernet; has shared memory with old MPG –SAIOC PNET card receives PNET broadcast; could rebroadcast on Ethernet –The BIC talks to the MPG via shared memory too –The Bitbus support capability of the FECC can be (trivially) modified to support PNET.