IOC Operations at SNS Carl Lionberger

1. IOC Operations at SNS Carl Lionberger

2. Initialization of PV’s Status Reports Remote rebooting Non-vxWorks IOC’s IOC Ops issues

3. Initialization of PV’s

4. Asr = autoSaveRestore msr = manual save/restore Rb = readback db = init values in epics database Some PV Init Cases

5. PV init observations • It would be nice to be able to tell ioc to do cold start boot • This would be easy to implement • IOC can also declare cold-start if neither readback or saved value available. • This could be on record-by-record basis, depending on system interconnectedness • Difficulty telling if readback and save sets valid

6. PV init observations 2 • It would be nice if ioc’s could determine when readback is valid • This is difficult and seldom done • Example that works: PLC5 record • Only EPICS writes setpoints • EPICS writes checksum • Can look at them at boot time • PLC always skeptical • power-up bits may tell enough in some cases • Only IOC resets pu bit and • Only IOC writes setpoints

7. Status Reports • vxStats • New signals being added continuously • Read anywhere • Utility board – temperature, voltages • Ping checks • Network terminal servers for console logins

8. Remote Reboots • If EPICS is up, can be done through vxStats • If VME not too bad, can be done through utility board (sysreset) • We have remote-operated power controls, but no remote crate controls • Plan to have one screen that can do all three • Console login will stay manual

9. Non-vxWorks IOC’s • Non-vxWorks dependent vxStats package needed • We still haven’t gotten non-vxWorks-dependent asr working • We are dropping xcas and cas in favor of iocCore • Many use labview—various interface schemes used

10. Conclusion • It may be useful to categorize things as “IOC Operations” • Lots of work in going to non-vxWorks iocs