iLon Brad Webb, SNS

2Managed by UT-Battelle for the U.S. Department of Energy Presentation_name What Is iLon And What Is Its Purpose? EPICS Driver. Gateway, To “CF” type systems. Typical Systems (But not limited to) Chillers… Boilers… HVAC… Variable Frequency Drives (VFDs)… LonWorks Communication Protocol.

3Managed by UT-Battelle for the U.S. Department of Energy Presentation_name What Is LonWorks? LonTalk/LonWorks Acronym Communication Protocol Software Kinda like Modbus ANSI/CEA B protocol Local Operating Network Open platform One, configures all Yeah, but not really

4Managed by UT-Battelle for the U.S. Department of Energy Presentation_name Example Of LonWorks Network. hh

5Managed by UT-Battelle for the U.S. Department of Energy Presentation_name Example Of Communication… Devices speak directly to each other, using a standard of network variable types…

6Managed by UT-Battelle for the U.S. Department of Energy Presentation_name Who’s using Lon? Spallation Neutron Source…

7Managed by UT-Battelle for the U.S. Department of Energy Presentation_name Benefits of a LonWorks system? Your, choice of vendors. Use of third-party tools. Easy integration. Easy additions and changes. Reduced installation cost. Lower life-cycle cost.

8Managed by UT-Battelle for the U.S. Department of Energy Presentation_name How does EPICS interface to LonWorks? Echelon iLon Server. EPICS iLon Driver.( ) EPICS IOC.VxWorks || Linux EPICS IOC Network SOAP/XML

9Managed by UT-Battelle for the U.S. Department of Energy Presentation_name About the iLon server. Imbedded OS Flexibility Variable updates VxWorks Customizable with Eclipse Event driven or polled

10Managed by UT-Battelle for the U.S. Department of Energy Presentation_name Protocol Detail SOAP/XML EPICS reads and writes the servers internal data table using SOAP/XML. EPICS IOC Network SOAP/XML

11Managed by UT-Battelle for the U.S. Department of Energy Presentation_name EPICS Support Record Types: Analog In & Out. Binary In & Out. MBBO In & Out. String In & Out. Data Types: Elements of structure.

12Managed by UT-Battelle for the U.S. Department of Energy Presentation_name EPICS Startup Command File… (Example “st.cmd”) Define a server. o iLonDefineServer(“arbitraryName”, “i.p. address”, “port”) o iLonDefineServer(“iLon1”, “ ”, “80”) Define an alias that points to the variable in the server o iLonDefineFunctionBlock(“alias”, “networkName”, “channelName”, “serverName”, “functionBlockName”) o iLonDefineFunctionBlock(“FB1”, “SNS_BmLn”, “Channel_1”, “BmLnSmartServer”, “WebServer_0”) Define an alias to LonMark format string (Optional) o iLonDefineFormatString(“alias”, “lonMarkFormat”)Standard Network Variable Types o iLonDefineFormatString(“state”, “SNVT_switch.state”)ON/OFF o iLonDefineFormatString(“value”, “SNVT_switch.value”) %

13Managed by UT-Battelle for the U.S. Department of Energy Presentation_name Summary

14Managed by UT-Battelle for the U.S. Department of Energy Presentation_name EPICS Record Example (VFD/Pump Speed and Status…) nvoPumpSpd;(Structured SNVT, {value & state}) {55.5 1}; AI record, that reads pump speed from ABB VFD Record(ai, “PumpSpeed”) { field(DTYP, “iLon”) field(INP, FB1 ‘nviPumpSpd’ value”) BI record, that reads pump status from ABB VFD Record(bi, “PumpStatus”) { field(DTYP, “iLon”) field(INP, FB1 ‘nviPumpSpd’ state”)

15Managed by UT-Battelle for the U.S. Department of Energy Presentation_name Summary iLon is industrial protocol. There is an EPICS driver. Operational at SNS for 1 Year, 15 devices. For more, see: