30 likes | 144 Vues
This document outlines the connection of the HVGEM module located in Barrack D3 to a control PC via CANbus. The OpenCAN server operates on a Windows PC, but since all muon Windows PCs are in D2, solutions include installing a new PC in D3 with a Kvaser interface, using an existing D2 PC with SYSTEC interface, or purchasing additional equipment. Hardware and software implications are discussed, particularly regarding the A- and C-side separation of the HV system. Two potential implementation paths are proposed.
E N D
How to connect the HVGEM module to the control PC and other thoughts... Ale
Hardware issues LNF HVGEM module is located in barrack D3 and should be connected via CANbus to a PC. The OpenCAN server runs on a Windows PC. There are no muon windows PCs in D3, they are all installed in D2. In D2 there are also spare SYSTEC ports that could be used to get a CANbus. The solutions I can see are the following: • We install a new windows PC in D3, together with a Kvaser interface, to communicate with the HVGEM • Independent system, easy to use and mantain • An extra muon PC, we need to purchase it, we also need a Kvaser CAN interface • We use one of the PC already located in D2 with its SYSTEC interface, and we bring the CANbus cable from the SYSTEC in D3 up to D2 • All the hardware is there, no need to buy a new PC, we only need a long CANbus cable • We need to install a new project on a PC where other PVSS projects are already running so we might get some conflicts A. Cardini / CERN & INFN
Software issues • The HVGEM module powers both A and C GEM chambers (6 per side), so from the hardware point of view it does not respect the clear A- and C-side separation available on the other HV systems. Here also I can see 2 solutions: • The A- and C-side separation will only be implemented at the software level • We do not care about A- and C-side separation and we consider the GEM Hv system an independent system A. Cardini / CERN & INFN