50 likes | 179 Views
ESS PVSS software – status. ESS FSM actions and state flow diagram for SM : ERROR – if information is completely lost for one SM module ESS fw component:
E N D
ESS PVSS software – status • ESS FSM actions and state flow diagram for SM: ERROR – if information is completely lost for one SM module • ESS fw component: • “generic”: on fw component for any area, one selects the desired area in 30 sec (or MTCC configuration will be installed by default)… • …but it stores all configuration info in its .dpl files (not really generic); • supports “automatic” SM change in a SM “position”; • supports FSM panel(s) for 1 RU (4 SMs) instead of 12 Rus; • supports archiving to Oracle DB (…but some problems detected…)
ESS PVSS software – needs to be done In the (very) near future: • Communication “PVSS-to-PLC“ via PVSS S7 driver; • Similar component installation procedure with area and configuration info stored in ConfigurationDB; • Implement Access Control; • Implement RU mapping? RU in FSM? Higher level nodes for ESS?; • Hope that fwTranding problem will be solved • ESS panels for ESS commisioning (and maintenance) and SM power up procedures • Proposed “software safety” – should support SM granularity In the (not so) far future: • Test of redundant configuration and redundant (protected) “PVSS-PC.Ethernet-PLC.Ethernet-PLC.CPU” connection
ESS PLC software – status • Multipoint protocol for ESS ready and (partly) tested since beginning of November 2006. • ESS PLC and PIC software (RC1) under further development (by mid December 2006.) • Installation of 3 RU in 867 and 3 RU in H4&H2 (testing/debugging continuously) in December 2006. • Installation of the rest of hardware (6 RU + 9 IU)in Service/Experimental hall (mounting, cabling, mapping, checking etc.) in December • Configuration of ESS PLC as a complete redudant system during 2007.