EPICS2ACNET

1
EPICS2ACNET

• EPICS Obscura (EO)

2
Implementation

• Process running on IOC
• like EPICS2TINE
• Use MOOC replacement framework
• Speak ACNET protocols to the outside world
• Speak dbXXX or caXXX protocols locally
• whichever makes the most sense

3
Advantages

• Distributed processing (scalable)
• Supports all ACNET protocols
• alarms, GETS32/SETS32, FTP, snapshot
• Supports low level IOC access
• Upper levels of the control system are unaffected
  (surgical implant)
• Could be implemented for other types of nodes as
  needed (extensible)
• Simplicity (e.g. device to node mapping)

4
Questions

• Should/can we block CA settings?
• Do we need to support embedded IOCs?

5
Implementation

• Create mapping database table(s)
• EPICS name, device index, property, order number
• Make DABBEL/D80 aware of these devices
• Download configuration information on boot

6
Conclusion

• Transparent access to EPICS parameters
• No high level overhead incurred
• database lookups, additional processing code
• Atomic solution
• everything handled at the IOC including alarms
• Its been done before