P2.3 TCS communication test

• Phase : 2
• Status : Draft
• Category : Daytime testing (functionality and operability) (C3)
• Recurrence : after instrument installation at telescope platform
• Duration : 2 days

Description

• Communication with the LBT TCS is tested to verify that the interface with TCS works as expected.

Prerequisites

• All electronics and services are up and running.

Procedure

• Test all the TCS functionality (sending preset, ADC trajectory, etc.) needed by SHARK-NIR, detailed in AD2.
• Check if the fits-writer is receiving all the right values from the LBT TCS.
• Check if the derotator trajectory is received from the LBT TCS. The trajectory verification with optical feedback will be done during the nighttime commissioning.
• Re-check if SOUL can access the SCICAM image from the agreed-upon folder.

Templates

Success criteria

• Connection to LBT TCS is working well. All the test results are successful.
• The fits-writer is receiving all the right values from LBT TCS.
• SOUL can retieve the SCICAM image.

Notes

• Arcetri Team remote support is required.
• LBTI-AO team support is required.
• Note that although the actual work needs roughly about 2 days, a lot of it can go in parallel with other activites. So, for the estimation of the total days, only 1 day from here is considered.

LBTO support

• Authorize SHARK-NIR
• Permission to use SX-ASM and LBTI-AO
• Permission to send preset, receiving LBT telemetry (inc. the derotator trajectory) and details for the Fitswriter.
• Support from the LBT SW team

Date performed and by whom