Here are what have happened after the last report.
- The data/command flow errors in the connection through a serial ports were debugged.
- The software side was checked by looking at packets in a direct connection between the SFC1 and RESI (Remote Ethernet Serial Interface) PC. It confirmed working OK.
- The hard ware side was checked by looking at the data in a direct connection between computers through the switch. It confirmed working OK.
- At the end, it is found that an serial connector connected at the RESI side was a wrong type connector. Instead of a null type, it was a straight type.
- After changing the connector, the data/command flow were checked and confirmed working fine at about 87 kbps of data rate. Commands were also sent through both COMM1 and COMM2 w/o any problems. This was done through the real LOS antenna at the SIP and receiver at the TM building was tuned.
- Now the new serial ports switch has been confirmed as working properly in the same performance as in the CSBF. Also the receiver was tuned for the launch operation.
- The SIP power module was installed underneath the pallet.
- The CPT has started this afternoon and ended at the Master Trigger test in section 9-i-iii. Remaining test will be done tomorrow.
- CPT continue. (Thu.)
- TCD PMT6 work. (Thu.)
- TCD/CD housekeeping data long-term stability check.
- Local TDRSS/IRIDIUM test. (Thu.)
- Connection test with UMD SOC via TDRSS/IRIDIUM. (Fri.) For the TDRSS test, it can only start from 1 PM (NZT)/ 7 PM (EST) due to the satellite visibility at the Willie Field. For the IRIDIUM test, it can be done from 9 AM (NZT) / 3 PM (EST).
- Hang test. (Sat./Sun.?) Can UMD SOC support the hang test on Saturday (EST) ?
- Calorimeter SPAR noisy behavior study.
- Takes photos for the recovery plan manual update. (by Nov. 30th)
MooHyun



CREAM Flights 


