120 likes | 134 Views
This meeting aims to review the current status, known issues, and new requirements/bugs for ISEG company. The objective is to define the strategy and new priorities, as well as prepare for a meeting with ISEG company representatives. Discussions will include support for new operating systems.
E N D
ISEG Users meeting Mateusz Lechman
The objectives of the meeting • Review the current status: • known issues • new requirements / bugs • Define the strategy and the new priorities for the ISEG company • Prepare for a meeting with the ISEG company representives • Discuss about support for the new operating systems 2
ISEG Users at CERN Review of the status: in progress CERN USER USER USER Contact person ISEG Contact person 3
Framework component (fwIseg) Current version : Any knownproblems / newrequirements as to fwIseg? 4
Known issues • MEMORY LEAK IN OPC SERVER (partiallysolvedin 5.01.00) • reduced a factor of four to five with a patch from Softing for the OPC Toolbox 4.10 • the problem is completelyremoved with the OPC Toolboxversion 4.22 • Significant effort for ISEG to implement the toolbox 4.22 • the classes of the toolkit 4.22 are not compatible to the classes of 4.10 • CERN wouldhave to particateincosts (ISEG contactedtheusers – status?) 5
Memory leak Possible solutions: • Participate in costs of upgrade from Softing 4.10 to Softing 4.22 • General upgrade of the OPC server (Softing 4.10) to OPC UA (Softing 5.0). • The effort is comparable • Exit Microsoft dependency • Maintenance contract between CERN and ISEG/ Softing. 6
Known issues • ATLAS- LIQUID ARGON: • OPC got stuck from time to time , unable to send commands to the periphery • Modules marked with a fake "not alive" flag , some items randomly marked as "invalid", fake readings (V,I, Status), maybe related to a module activity (channel ramp UP/DOWN) • New requirements : OPC server logfile for debugging, fully WindowsServer 2003 compliant • Next steps to be defined 7
Known issues • ALICE- PHOS: unstable work of OPC server5.00.00.28 loosing of communication, the new instance of server starts when a new connection from OPC client appears) • Status: internaltests, reported • ALICE – TPC: crate controler can not be used in this version with cache reading and user name space • Status: reported to the ISEG company • COMPASS: newrequirements - maintain backward compatibility to be able to keep the history in PVSS 8
Known issues • ALICE – SDD: PEAK USB performance problem • Status? • PEAK PCI isrecommended • support for newinterfaces • LHCb VELO: • SYSTEC not reliable • firmware upgradecaused the firmware to be corrupted and the module had to be returned to ISEG to be reloaded 9
Known issues • ATLAS – BCM: • temporary communication failures - failing read/write commands, typically solves itself after a few minutes, in few cases OPC server needed to be restarted. • Oncethecommunication gotcompletely stucked, restart of the PC needed 10
New operating systems support • ISEG performed some testing of OPC server 5.00 on 32 bit Windows7 with positiveresults • Any bugs found on the windows 7 platform will not betreated as enhancements (payable) • The test under Windows Server 2008 is not planned in the near future • CERN wouldhave to pay for the development and support • ALICE is not takingintoaccount Windows 7 • aimWindows 2008 R2 (64 bit) • Whatareyourexpectations /plans ? 11
General Information Contact person: Mateusz.Lechman@cern.ch Subscribe to the mailing list: iseg-users@cern.ch opc-users@cern.ch