Dear colleagues,
Here is a summary of today's activites at CSBF.
- The preparation of the hang test started at 6 AM (CDT).
- The weight of the payload w/o rotator and with the bottom solar panels added was measured as 3605 lbs before moving out for the hang test.
- After having the payload on the high dolly, it is found that the lift crane is too big to lift the payload with the bottom solar panels. So the bottom solar panels were removed and re-assembled at the outside for the hang test.
- The hang test in solar panel power mode was started around 9 AM (CDT).
- At the beginning of the hang test, the payload related function was tested with the instrument was in flight mode with the muon trigger.
After the function test, the instrument LPT was completed except the shutdown safe of the SFC1 at the end.
- The shutdown safe indicator light did not turned on either at the CDM monitor and the master trigger board.The SFC1 restarted with a power re-cycle by the CDM, but the connection did not establish maybe due to an incomplete rebooting of the SFC1 possibly asking the disk check and waiting for the keyboard return. Decided to power off to debug the problem inside the high bay area with keyboard and console monitor. But when the SFC1 was powered on at the bay, it booted fine with the server program running OK. So the problem has not reproduced inside. It maybe due to a hot temperature outside (~38 deg. C).
- In case if it was due to the disk check, the option to check disk should be off before the launch in order to avoid this problem in the flight when the SFC be rebooted and have the same situation. This is a part of the SFC CPT, I heard, so it should be off before the launch. It is only on when in debugging mode and when the disk s were bad as in the last year's integration.
- By the time, the instrument LPT was over except the SFC shutdown safe problem, it was about 1:40 PM.
- During the hang test, the data flow and commanding from/to the UMD either in TDRSS mode and in Iridium mode were tested by sending commands and receiving data. Also received data were checked by the Cplot program.
- During the LPT, the muon data in CER shows a unit of PMTs (16 each) with higher number of hits above sparsification threshold. It needs to be checked by the CER group. Will send an e-mail to them for checking after transferring data to the cdps3.
Here are things planned to be done.
- Pre-scaling of different trigger flag data are being coded and debugged by Prashant. This is necessary coding before the burn-in starts.
- The CDAQ code in SFC2 will be updated with the directory change code before the burn-in and tested if possible. Otherwise, it will be tested during or after the burn-in test.
- For the burn-in test, a client PC will be prepared with dual Ethernet card so that data flow can go to the UMD SOC for shift.
- Chercam HSK problem debugging after the burn-in test.
- TCD 12 V HSK attenuation circuit installation after the burn-in test.
- Update of manuals.
- Copying and backup of new integration data into cdps3 at UMD and client PCs at CSBF.
Here are updates related with the hang test, burn-in and packing.
- Burn-in will be between 9 AM (EDT) 2nd of Aug. and 9 AM (EDT) 5th of Aug. for 72 hours. It will have a Iridium mode between CSBF and UMD SOC for 2nd and 3rd. It will be TDRSS mode for the day time of the 4th. If possible, keep the Iridium mode on during the nights.
- MOR/MRR schedule is being arranged as the 6th of August.
- Shipping of the Instrument container is being arranged by Linda/Dave of WFF. Will see a plan on Monday.
- All other GSE crates will be sent via a usual sea shipping. It is going to be leave from CSBF on the 15th of August. All spares should be delivered before the date even if some can not be delivered before the 8th when UMD crew will leave CSBF if everything goes well.
Please let us know if you have any questions/comments/suggestions.
Cheers, MooHyun.
MooHyun, August 1, 2008
