Controls EN-ICE UNICOS – PVSS evolution Integration of JCOP devices in UNICOS Jonás Arroyo CERN EN-ICE-SCD 18 March 2010

Controls EN-ICE INDEX  INTRODUCTION  JCOP DEVICES  UNICOS DEVICES  MATCHING DEVICE CONCEPTS  PROXY MECHANISM  INTEGRATE JCOP DEVICES  SUMMARY OF FUNCTIONS  NEXT STEPS INDEXJ.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE INTRODUCTION  OBJECTIVE:  Integrate JCOP devices into UNICOS: reusing JCOP functionality on UNICOS environment and profit from its features (trending, import, graphical tools...).  PROFITS:  Broad range of JCOP devices and their functionality could be use in UNICOS.  These devices could be used as standard UNICOS devices.  “Easy” way to import devices (JCOP dev. – UNICOS dev. – OPC config file).  Easy way to: configure, manage or control them from UNICOS HMI.  Easy to add a lot of functionality in a new project: Faceplate, Widgets,...  DISADVANTAGES:  Effort from developer to integrate each family of devices.  Redundancy of DPs (UNICOS and JCOP DP must exist).  USERS:  Actually: NA62 DCS prototypes.  Potentially: Any UNICOS user. INTRODUCTION – 1J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE INDEX  INTRODUCTION  JCOP DEVICES  UNICOS DEVICES  MATCHING DEVICE CONCEPTS  PROXY MECHANISM  INTEGRATE JCOP DEVICES  SUMMARY OF FUNCTIONS  NEXT STEPS INDEX – 2J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE JCOP DEVICES  Concept of Framework Device  Reflect the architecture of the hardware:  Hierarchy: naming convention for DP names : Vendor/parent device/child device/...  Ex: CAEN/Crate01/Board00/Channel001  Separate DPs for each level in hierarchy:  The crate, the board, the channel  To create JCOP devices you should install its device component (Ex: fwCaen 2.3.XX) and:  Use device editor and navigator.  Use mass configurarion tool.  Use fwDevice functions to create from scripting. JCOP DEVICES – 3J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE JCOP DEVICES JCOP DEVICES – 4J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010  JCOP Framework offers components for the following devices:  CAEN power supplies  Wiener power supplies  Iseg power supplies  ELMB  LWDAQ (Long-Wire Data Acquisition)  Rack control  ELMB PSU (Power Supply Unit)

Controls EN-ICE JCOP DEVICES  Device Definition, “Inheritance” and reuse for device types.  JCOP recommends the use of standardised hardware device types, device families.  Allows to reuse information and functionality for whole family of similar devices.  Encapsulate this information in dedicated data-points: DEVICE DEFINITION.  Device Type: basic and common information for all device family.  Ex: all types of CAEN boards.  Device Model: specific information of one model from device family.  Ex: CAEN Board A230 for SY127 crate.  Device definition contains:  Allowed relations for hierarchy (CAEN board “can have” channels, it has a crate as parent).  Interface: list of dp-elements available for “public use”, with descriptions.  Definition of device-specific “hook” functions (Ex: create a device) and JCOP panels.  Rules for automated peripheral-address generation.  Defaults for configs (Ex: smoothing or dpfunction parameters)  Etc...  Some exceptions from JCOP device model standard: particularly ELMB. JCOP DEVICES – 5J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE INDEX  INTRODUCTION  JCOP DEVICES  UNICOS DEVICES  MATCHING DEVICE CONCEPTS  PROXY MECHANISM  INTEGRATE JCOP DEVICES  SUMMARY OF FUNCTIONS  NEXT STEPS INDEX – 6J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE UNICOS DEVICES  Architecture: NO HIERARCHY: separation into FRONT-END and DEVICE.  Adding new devices: IMPORT OF A CONFIG FILE, using Import Database Configuration Tool.  Device representation in UNICOS:  DP for meta-info or definition:  _UnFrontEnd DP: has front-end import functions.  _UnSystemIntegrity DP: is UNICOS System Integrity configuration data.  _UnObjects DP: has UNICOS DEVICE configuration data.  DP for device instances:  New DPT (eg._UnFwElmb) and its instance for front-end (stores real data).  Instance of _UnSystemAlarm : UNICOS system integrity alarm for this front-end.  New DPT (e.g. UnFwElmb_AI) and its instances for DEVICES (store real data).  UNICOS has been PLC-oriented: simplified model for devices and functions.  To implement more complex device types, UNICOS mechanisms had to be extended:  The PROXY mechanism. UNICOS DEVICES – 7J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE INDEX  INTRODUCTION  JCOP DEVICES  UNICOS DEVICES  MATCHING DEVICE CONCEPTS  PROXY MECHANISM  INTEGRATE JCOP DEVICES  SUMMARY OF FUNCTIONS  NEXT STEPS INDEX - 8J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE MATCHING DEVICE CONCEPTS MATCHING DEVICE CONCEPTS – 9J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010  Need to match conceptual models for devices in two frameworks:  UNICOS: Frontend + Device.  JCOP Framework: device hierarchies.  Establish device naming rules for a device in UNICOS:  Fw device naming/structure defines some constraints.  Define the splitting point between frontend and device.

Controls EN-ICE CASE: CAEN Power Supplies  CAEN/crate1/board01/channel000 CASE: CAEN – 10J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010 FRONT-ENDDEVICE  In JCOP Fw:  CAEN/crate1/  CAEN/crate1/board01/  CAEN/crate1/board01/channel00  CAEN/crate1/board01/channel01

Controls EN-ICE CASE: Iseg Power Supplies CASE: ISEG – 11J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010  Iseg/can0/crate1/ma01/ch00 FRONT-ENDDEVICE  In JCOP Fw:  ISEG/can0/  ISEG/can0/crate1  ISEG/can0/crate1/ma01  ISEG/can0/crate1/ma01/ch00

Controls EN-ICE CASE: ELMB CASE: ELMB – 12J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010  ELMB/can00/ELMB_NODE/AI/voltage_00 FRONT-ENDDEVICE  In JCOP Fw:  ELMB/can00  ELMB/can00/ELMB_NODE  ELMB/can00/ELMB_NODE/AI  ELMB/can00/ELMB_NODE/AI/voltage_00

Controls EN-ICE INDEX  INTRODUCTION  JCOP DEVICES  UNICOS DEVICES  MATCHING DEVICE CONCEPTS  PROXY MECHANISM  INTEGRATE JCOP DEVICES  SUMMARY OF FUNCTIONS  NEXT STEPS INDEX - 13J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICEPROXY MECHANISM  Try to minimize redundancy of DP and DPE:  Link between UNICOS and JCOP devices through a “PROXY” mechanism:  Store the mapping between the related datapoints in UNICOS and JCOP  Systematic use of this information throughout UNICOS, to access data (read/write) from UNICOS to all related JCOP datapoints  Proxy example: PROXY MECHANISM – 14J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010 UnExampleIO ExampleDeviceIO_1 UNICOS DEVICEJCOP DEVICE ExampleDeviceIO_1.proxy = “AnalogDigital/JCOP_EXAMPLE_DIG_IO”,(…) Later, operations on ExampleDeviceIO_1 (dpSet, dpGet, …): “AnalogDigital/JCOP_EXAMPLE_DIG_IO” + “.inValue” “AnalogDigital/JCOP_EXAMPLE_DIG_IO” + “.outValue”

Controls EN-ICE PROXY AND DEVICES… PROXY AND DEVICES... – 15J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010 UNICOS DEVICE.proxy ELMB/can01/ELMB_TEMP_LAV_1/AI/PT_4W_0_1 REMEMBER on JCOP: ELMB/can01/ELMB_TEMP_LAV_1/AI/PT_4W_0_1 FRONT-END REMEMBER on UNICOS: un-ELMB_PRESS_LAV_1-TEMP_LAV-UnFwElmb_AI DEVICE JCOP DEVICES UNICOS DEVICE un-ELMB_TEMP_LAV_1-TEMP_LAV-UnFwElmb_AI ELMB/can01/ ELMB_TEMP_LAV_1 /AI/PT_4W_0_1

Controls EN-ICEPROXY AND FRONTENDS… PROXY AND FRONTENDS... – 16J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010 REMEMBER on JCOP: ELMB/can01/ELMB_TEMP_LAV_1/AI FRONT-END REMEMBER on UNICOS: _UnFwElmb_FE_ELMB_TEMP_LAV_1 UNICOS FRONT-END.proxy ELMB/can01/ELMB_TEMP_LAV_1 ELMB/can01 ELMB/can01/ELMB_TEMP_LAV_1/AI JCOP DEVICES UNICOS DEVICE ELMB/can01/ELMB_TEMP_LAV_1/AI

Controls EN-ICE INDEX  INTRODUCTION  JCOP DEVICES  UNICOS DEVICES  MATCHING DEVICE CONCEPTS  PROXY MECHANISM  INTEGRATE JCOP DEVICES  SUMMARY OF FUNCTIONS  NEXT STEPS INDEX - 17J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE IMPORT JCOP DEVICES  Objective: Use UNICOS Import Dabase Config tool to create JCOP devices, UNICOS devices and their links, and additional config files (eg. For OPC Server),.  A single UNICOS Import Config file to do all.  A summary of task that UNICOS Import Database Config Tool would do:  Parse file and check input parameters: are enough and valid ones.  Check JCOP consistency: hierarchy and parameterization.  Check if JCOP and UNICOS devices could be created.  Ensure enough space in local archives  Create JCOP and UNICOS devices.  Configure JCOP devices (including e.g. a file for OPC server)  Configure UNICOS devices  Establish link between JCOP and UNICOS devices.  Setup system integrity for UNICOS front-end device. IMPORT JCOP DEVICES – 18J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICEINTEGRATE WITH UNICOS… Model behaviour of JCOP devices and front-end as standard UNICOS devices:  Buttons, panels, widgets, faceplates, right click, export, system integrity, diagnostic,...  UnFwDevice.ctl library for common code:  Common UNICOS functions used in graphical representations assume that the device is a PLC, interfaced through registers; Workarounds needed for more complex device.  Other functions used in the import process.  4 libraries specific to each new device family. INTEGRATE WITH UNICOS... – 19J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE INDEX  INTRODUCTION  JCOP DEVICES  UNICOS DEVICES  MATCHING DEVICE CONCEPTS  PROXY MECHANISM  INTEGRATE JCOP DEVICES  SUMMARY OF FUNCTIONS  NEXT STEPS INDEX - 20J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE SUMMARY OF FUNCTIONS: DB  Import Database configuration SUMMARY OF FUNCTIONS – 21J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE SUMMARY OF FUNCTIONS: DB  Export Database configuration SUMMARY OF FUNCTIONS – 22J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE SUMMARY OF FUNCTIONS: WIDGETS AND FACEPLATES  Widget  Right Click  Faceplate SUMMARY OF FUNCTIONS – 23J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010 FRONT-END AND DEVICES !!!

Controls EN-ICE SUMARY OF FUNCTIONS: TRENDING  Faceplate Trend  Dynamic trending SUMMARY OF FUNCTIONS – 24J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010 FRONT-END AND DEVICES !!!

Controls EN-ICE SUMMARY OF FUNCTIONS: TRENDING  Faceplate Config SUMMARY OF FUNCTIONS – 25J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010 FRONT-END AND DEVICES !!!

Controls EN-ICE SUMMARY OF FUNCTIONS: TRENDING  Faceplate Trend config SUMMARY OF FUNCTIONS – 26J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010 FRONT-END AND DEVICES !!!

Controls EN-ICE SUMARY OF FUNCTIONS: FRONTEND DIAGNOSTICS  Diagnostic panel SUMMARY OF FUNCTIONS – 27J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE SUMMARY OF FUNCTIONS: SYSTEM INTEGRITY  System Integrity SUMMARY OF FUNCTIONS – 28J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE STATUS OF INTEGRATED DEVICES  Integrated the following devices, as needed in NA62 DCS project:  ELMB: advanced prototype.  ISEG: advanced prototype.  CAEN: proof of concept STATUS OF INTEGRATED DEVICES – 29J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE INDEX  INTRODUCTION  JCOP DEVICES  UNICOS DEVICES  MATCHING DEVICE CONCEPTS  PROXY MECHANISM  INTEGRATE JCOP DEVICES  SUMMARY OF FUNCTIONS  NEXT STEPS INDEX - 30J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE NEXT STEPS  Complete the functionality for ELMB-UNICOS component  Graphical representation  Integrate all ELMB port types  Complete integration of other devices (ISEG, CAEN)  Integrate configuration of archive and alarm from import files  Improve/streamline internal checking engine of the import procedure. NEXT STEPS - 31J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE CONTACT, FEEDBACK CONTACT - 32  EN – ICE – SCD:  General: J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE

Controls EN-ICE

Controls EN-ICE

Controls EN-ICE JCOP DEVICES JCOP DEVICES – 4J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE UNICOS DEVICES UNICOS DEVICES – 8J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE INTEGRATE JCOP DEVICES  UNICOS Import Config file: # DELETE #Delete: Delete;UNICOS FE DPT; UNICOS FE DP; UNICOS FE APPLICATION; UNICOS DEVICE NAME; UNICOS DEVICE NUMBER; FORCE DELETE CHILDREN DEVICES(not available yet); Delete;_UnFwElmb_FE;ELMB_TEMP_LAV_1;TEMP_LAV;UnFwElmb_AI;*; # PLCCONFIG #FrontEnd: PLCCONFIG; _UnFwElmb_FE ; FRONTEND NAME ; FRONTEND APPLICATION ; NODE TYPE ; NODE MODEL ; NODE NAME ; CANBUS TYPE ; CANBUS MODEL ; CANBUS NAME ; FRONTEND TYPE ; FRONTEND MODEL ; FRONTEND NAME ; CANBUS COMMENTS ; CANBUS CARD ; CANBUS SPEED ; CANBUS ID ; FRONTEND COMMENTS ; FRONTEND ID; PLCCONFIG;_UnFwElmb_FE;ELMB_TEMP_LAV_1;TEMP_LAV;Node;ELMB;ELMB;ELMB CAN bus;Elmb CAN bus;can01;ELMB IO Node; Elmb Node;ELMB_TEMP_LAV_1;Node 1 CANBus;Kvaser;125000;1;ELMB NODE 1;1; # SystemAlarm # NOT USED # Device Analogic Input (Temperature) #DEVICES: UnFwElmb_AI; DEVICE NUMBER ; DEVICE ALIAS ; DEVICE DESCRIPTION ; DIAGNOSTIC PANEL ; WEBPAGE HELP ; DEFAULT PANEL ; DOMINIO ; NATURALEZA ; WIDGET NAME ; JCOP DEVICE TYPE ; JCOP DEVICE MODEL ; JCOP DEVICE FULL NAME ; JCOP FRONTEND FULL NAME ; SENSOR TYPE ; SENSOR PARAMETERS ; SENSOR COMMENTS ; [Boolean archive ; Analog archive ; Event archive;] UnFwElmb_AI;0;LAV_TEMP_4_0_0;TEMP-4-0-0;panel_diagnostico.pnl; UnFwElmb_AI;ELMB Analog Input;Elmb Analogic Input Channel;ELMB/can01/ELMB_TEMP_LAV_1/AI/PT_4W_0_1; ELMB/can01/ELMB_TEMP_LAV_1;Ptx 4-wire;100.0 | ; INTEGRATE JCOP DEVICES – 15J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE INTEGRATE JCOP DEVICES  UNICOS Import Config file: # DELETE #Delete: Delete; UNICOS FE DPT; UNICOS FE DP; UNICOS FE APPLICATION; UNICOS DEVICE NAME; UNICOS DEVICE NUMBER; FORCE DELETE CHILDREN DEVICES(not available yet); Delete;_UnFwElmb_FE;ELMB_TEMP_LAV_1;TEMP_LAV;UnFwElmb_AI;*; INTEGRATE JCOP DEVICES – 15J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE INTEGRATE JCOP DEVICES  UNICOS Import Config file: # PLCCONFIG #FrontEnd: PLCCONFIG; _UnFwElmb_FE ; FRONTEND NAME ; FRONTEND APPLICATION ; NODE TYPE ; NODE MODEL ; NODE NAME ; CANBUS TYPE ; CANBUS MODEL ; CANBUS NAME ; FRONTEND TYPE ; FRONTEND MODEL ; FRONTEND NAME ; CANBUS COMMENTS ; CANBUS CARD ; CANBUS SPEED ; CANBUS ID ; FRONTEND COMMENTS ; FRONTEND ID; PLCCONFIG;_UnFwElmb_FE;ELMB_TEMP_LAV_1;TEMP_LAV;Node;ELMB;ELMB; ELMB CAN bus;Elmb CAN bus;can01;ELMB IO Node;Elmb Node; ELMB_TEMP_LAV_1;Node 1 CANBus;Kvaser;125000;1;ELMB NODE 1;1; INTEGRATE JCOP DEVICES – 15J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE INTEGRATE JCOP DEVICES  UNICOS Import Config file: # Device Analogic Input (Temperature) #DEVICES: UnFwElmb_AI; DEVICE NUMBER ; DEVICE ALIAS ; DEVICE DESCRIPTION ; DIAGNOSTIC PANEL ; WEBPAGE HELP ; DEFAULT PANEL ; DOMINIO ; NATURALEZA ; WIDGET NAME ; JCOP DEVICE TYPE ; JCOP DEVICE MODEL ; JCOP DEVICE FULL NAME ; JCOP FRONTEND FULL NAME ; SENSOR TYPE ; SENSOR PARAMETERS ; SENSOR COMMENTS ; [Boolean archive ; Analog archive ; Event archive;] UnFwElmb_AI;0;LAV_TEMP_4_0_0;TEMP-4-0-0;panel_diagnostico.pnl; ELMB Analog Input;Elmb Analogic Input Channel; ELMB/can01/ELMB_TEMP_LAV_1/AI/PT_4W_0_1; ELMB/can01/ELMB_TEMP_LAV_1;Ptx 4-wire;100.0 | ; INTEGRATE JCOP DEVICES – 15J.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010

Controls EN-ICE.PROXY .proxy (DPE):  FRONT-END  DEVICE  Access to JCOP device from UNICOS world:  Unicos DEVICE DP ->.proxy -> JCOP DEVICE -> read / modify /check DPE  Unicos DEVICE DP ->.proxy -> JCOP DEVICE = get parents by DP name or fwDevice functions. REMEMBER on JCOP: ELMB/can00/ELMB_NODE/AI/voltage00.PROXYJ.Arroyo, P.Golonka – EN/ICE/SCD – JCOP devices. – 18 th March 2010 Main JCOP device Front End UNICOS device Sub JCOP device Front End UNICOS device Sub 2 JCOP device Front End UNICOS device Sub 3 JCOP device Front End UNICOS device … Front End UNICOS device Main JCOP device DEVICE UNICOS device Sub JCOP device DEVICE UNICOS device Sub 2 JCOP device DEVICE UNICOS device Sub 3 JCOP device DEVICE UNICOS device … DEVICE UNICOS device dyn_string FRONT-ENDDEVICE 1 item N item