Changes between Version 10 and Version 11 of docs/CommissioningPlan

Timestamp:

09/04/20 12:32:49 (4 years ago)

Author:

kradhakrishnan

Comment:

--

docs/CommissioningPlan

@@ -153 +153 @@
 - all operation that should be supported by **control software** automated procedures should be defined by the responsible person with software person in copy or in accordance with software department (better) (e.g.: P1.8 and P1.9)
  
+===Kalyan
+
+8.2     Communications and SW related interfaces
+SHARK-NIR control software (SHINS) will be interfaced with the following LBT software (further details are reported in RD8):
+•       TCS: the availability, both nighttime and daytime, of all IIF methods reported  in RD11 is assumed. 
+SHINS will need from IIF additional functionalities related to AO:
+o       Set a waffle mode to the ASM, in closed-loop. This functionality will be used night-time before each observation, in order to correctly center the target on the coronagraphic mask (see SHARKNIR-SCI-08 in RD11). The maximum magnitude for the waffle is TBD.
+o       Set an offset shape to the ASM, in closed-loop, specified via a TBD number of Zernike coefficient, for NCPA characterization (see SHARKNIR-TEC-01  RD11). The mirror signals have to be subtracted to rightly correct for atmospheric distortion. This functionality will be used both night-time and day-time, depending on stability of NCPA (see SHARKNIR-TEC-01 in RD11), which will be assessed during commissioning. The rate of ASM offsets sent from SHINS is TBD, as well as the list of errors to be propagated from the AOS to SHINS through the IIF.
+o       Use the telescope “repoint mode” when the telescope is acquiring the AO reference star, so to position the star where the wave front sensor is expecting it to be.
+•       AOS through the engineering programmatic interface: 
+o       in order to offset the LBTI-WFS position (using X-Y-Z stages), so to align it to SHARK-NIR optical path. This will be needed during commissioning. TBD if the same interface will be used in day-time to adjust for changes.
+o       To set an offset shape to the ASM in closed-loop, in case the requested method from the IIF can apply offsets with a maximum rate lower than the TBD required.
+•       LBTO telemetry: SHINS telemetry will be written on HDF5 files as requested in RD12. SHINS will access telescope and AO telemetry using the TCS data dictionary via the IIF method GetParameter.
+•       Alarm system: using the INDI protocol, SHINS will publish its alarm signals and the statuses of all SHARK-NIR hardware devices and SHINS components, by providing the information required in RD13.
+•       Archive: observation frames in  the form of FITS files will be sent to the LBTO archive for ingestion using Unix utility rsync (see RD11).
+•       Queue/OT: the interface with SHINS will be an XML file, as specified in RD11. 
+
+•       Network (see Figure 5 as reference): 
+o       Network subnet dedicated to the instrument, to be associated to the instrument workstation and instrument electronics, as well as scientific camera workstation.
+o       On commissioning, support to connect the instrument to LBT network will be needed.
+o       On commissioning, support will be needed to connect scientific camera control electronics to scientific camera workstation in control room on level 2 (AD5).
+•       Workstation installation and instrument operation: 
+o       On commissioning, access to server room and support will be needed to install instrument workstation (1U Dell server) and to install scientific camera workstation in control room on level 2 (AD5).
+o       On commissioning, access to control room will be needed to operate the instrument.
+o       On commissioning, possibility to connect laptop to observatory network to troubleshoot the instrument.
+o       On commissioning, software support will be needed during instrument operation involving telescope and IIF.
+o       On commissioning, software support will be needed to build observation blocks with observatory observation preparation tool, which will be then run on the instrument.
+o       On commissioning, support will be needed with operation involving file archiving in the observatory archive. 
+
+ 
+Figure 5: Instrument control network
+8.3     Available volume and HW interfaces
+The instrument will connect to the existing outer ring of the Gregorian bearing at the central bent focal station, SX side.
+The identification of the maximum available volume will pass through some iterative steps:
+•       The SHARK-NIR mechanical design will be finalized by industry under INAF-Padova responsibility. INAF-Padova will provide the optical design (including full rays path).
+•       The design agreed with INAF-Padova shall be then iterated with LBTO to confirm the space availability.
+INAF-Padova will provide the proper mechanical drawings with the purpose to clarify both the available volume to design the SHARK-NIR instrument and the possible connection points.
+INAF-Padova will also ensure proper communication and exchange of information between LBTO, LBTI and the company in charge of the study for a proper interface definition.
+We consider as a reference for mechanical interfaces between SHARK-NIR and LBTI the CAD model “SHARK Installation Final.stp” (RD4), which is a merging of the CAD model LBTI_1_20_17 received by Manny Montoya, the CAD model of the gallery “513s Full Gallery Assy 2018 vs - Copy” received by Jim Wiese and the results of the laser tracking survey on SHARK-NIR area conducted by Mike Gardiner “SHARK IR volume measurement2”.
+
+8.4     Installation interfaces
+All the checks to verify the feasibility of the installation procedure of SHARK-NIR have been performed on the CAD model “SHARK Installation Final.stp”.  For installation purposes, the requirements to LBTO are:
+
+•       Remove the door of the Nystrom LBTI top hatch (SX side).
+•       Installation of the rotator work platform at the central bent focal station, SX side.
+•       Use of the dome crane, to lower the subsystems of SHARK-NIR (as described in AD6) through the hatch in the UIAP LBTI platform and from the M1 side.
+•       Operator to move the crane.
+•       General assistance during the mounting phases.
+
+8.5     Electrical interfaces
+SHARK-NIR electronics design is reported in AD5.
+-       Summary of required space in the rack (total space: 13U):
+o       The motor control unit dimensions are 483mm (width)  x  133,35mm (height)  x  525mm (depth)  (also indicated as 19‘‘ × 3U × 525 mm)
+o       The dimensions of the Lake Shore 336 temperature controller are 435 mm W × 89 mm H (2U) × 368 mm D (17 in × 3.5 in × 14.5 in)
+o       Custom realized box: (2U in height) may contain the 2 light sources and their power supply, a motorized linear stage (M-403.2DG  from Physik Instrumente), a small optical system consisting of 2 lenses and 1 filter to select the light to inject into the integrating sphere of SHARK-NIR (broadband or multi-narrow bands), the TT camera power supply and the power switches board (relais board)
+o       DM electronics is contained in a 19” × 4U
+o       WFC BCU housing: 19” × 2U (TBC)
+-       Power requirement (total Watt dissipation: 700W):
+o       The motor control unit maximum power consumptions is ~350W. 
+o       The Camera temperature controller maximum power consumption is of the order of ~100W. Its power requirement is 100, 120, 220, 240 VAC, ±10%, 50 or 60 Hz, 250 VA.
+o       The C-RED2 camera needs a 12V power supply and a commercial “relais” board controllable through Ethernet, is required, to power the power supply, which has a power dissipation of the order of 10W.
+       Custom box: power to be dissipated of the order of 100W
+o       DM electronics power consumption is 150W.
+o       WFC BCU: 24Vdc (48Vdc is also possible upon request) and the estimated power consumption is ~15W
+The agreed cabinet to allocate the above described electronics is rack 2, referring to Figure 6. The space reserved to SHARK-NIR electronics is the lowest area of the cabinet.
+
+ 
+Figure 6: the agreed cabinet for SHARK-NIR electronic is #2.
+8.6     Thermal interfaces
+-       Cooling:
+o       Daily refill of the cryostat: one LN2 refill per day is required (~10 liters). The camera LN2 hold time is of the order of 28 hours (computed in very conservative conditions, see AD7), giving a reasonable margin on the refilling time.
+o       Liquid cooling of the technical camera C-RED 2 from First Light (through LBTO glycol system, described in RD9):
+       Max temperature: 35°C 
+       Min Temperature: dew point
+       Pressure: 10 bar max  
+       Cooling capacity: 100W minimum
+       Flow rate: > 0.5 L/min 
+       Max 50% ethylen glycol aqueous solution ; 50% distilled water or deionized water
+
+8.7     Other interfaces
+-       Air Flow:
+o       A clean air flow with a maximum required flux of 0.5 m3/min to keep SHARK-NIR optical bench on a slight over-pressure with respect to the outer environment.   
+8.8     Logistics 
+8.8.1   Connections
+An Ethernet cable should reach the computer rooms located at level 2.
+8.8.2   Storage
+Space (TBD) for storage should be made available at 3L.