12/27/2004
0:12		ramp down TRD HV3 @ address 9 value 1175, HV3 =0.01	HQ
		ramp up TRD HV3 @ address 9 value 1200, HV3=1.15
		the above two are required by Simon
0:14		after finished HV3 operation above, observed standby mode	HQ
		showing in the monitor window of CDAQ in cdps2.umd.edu
		2 dat files between 20041227-0511and 20041227-0524
		have small sizes
0:51		TRD latch-up (cal trigger is 0.2Hz)	HQ
0:54		TRD data flow resumes after the first ped run	HQ
1:25		TRD latch-up (cal trigger is 0.4Hz)	SO
1:29		TRD data flow resumes after the first ped run	SO
2:23		TRD latch-up (cal trigger is 0.4Hz)	JH
2:25		TRD data flow resumes after the first ped run	JH
2:33		TRD latch-up (cal trigger is 0.2Hz)	SO
2:35		TRD data flow resumes after the first ped run	SO
3:13		TRD latch-up (cal trigger is 0.4Hz)	JH
3:15		TRD data flow resumes after the first ped run	JH
5:01		data flow stopped for a while due to ESC satellite switch	JH
5:02		TRD latch-up (cal trigger is 0.2Hz)	JH
5:07		TRD data flow resumes after the first ped run	JH
5:18		TRD latch-up (cal trigger is 0Hz)	SO
5:22		TRD data flow resumes after the first ped run	SO
5:35		TRD latch-up (cal trigger is 0Hz)	SO
5:37		TRD data flow resumes after the first ped run	SO
6:03		Send "get_spi.stol"	JH
6:04		TRD latch-up (cal trigger is 0.4Hz)	JH
6:07		TRD data flow resumes after the first ped run	JH
6:25		TRD latch-up (cal trigger is 0.2Hz)	GR
6:28		TRD data flow resumes after data run	GR
6:57		TRD latch-up (cal trigger is 0.8Hz)	GR
6:58		TRD data flow resumes after data run	GR
7:15		TRD latch-up (cal trigger is 0.8Hz)	GR
7:18		TRD data flow resumes after data run	GR
7:22		TRD latch-up (cal trigger is 0.8Hz)	GR
7:23		TRD data flow resumes after data run	GR
7:27		TRD latch-up (cal trigger is 1.0Hz)	GR
7:33		TRD data flow resumes after data run	GR
7:38		data flow stopped for a while due to ESC satellite switch	TG
7:43		data flow resumed	TG
7:50		TRD latch-up (cal trigger is 0.2Hz)	GR
7:53		TRD data flow resumes after data run	GR
8:03		TRD latch-up (cal trigger is 0.2Hz)	GR
8:10		TRD data flow resumes after data run	GR
8:20		TRD latch-up (cal trigger is 0.8Hz)	GR
8:23		TRD data flow resumes after data run	GR
8:52		TRD latch-up (cal trigger is 0.8Hz)	GR
8:54		TRD data flow resumes after data run	GR
8:55		ZHI rate is too low (6.0-8.0) for twenty minutes	TG
		called MH, Sonny, Jim Beatty, sent email to them to ask to take care of it.
9:57		TRD latch-up (cal trigger is 1.2Hz)	GR
10:00		TRD data flow resumes after data run	GR
10:00		Tried to restart TCD and DAQ	TG
		But command window closed before command went through.
10:54		When command window opened, send commands for CAL trigger rate with 72 and send arc_start.stol and daq_restart.stol	TG
		Zhi trigger rate is still low around 7Hz.
12:30		recycling TCD required by Jim	TG
13:50		reset DAQ	HQ
14:25		TRD latch-up	HQ
		Zhi trigger rate is still low around 7Hz.
14:35		TRD data flow resumes after the first ped run	HQ
14:38		TRD latch-up	HQ
14:46		TRD data flow resumes after the first ped run	HQ
14:56		TRD latch-up	HQ
15:09		TRD data flow resumes after the first ped run	HQ
15:10		TRD latch-up	HQ
15:16		TRD data flow resumes after the first ped run	HQ
15:46		TRD latch-up (CAL trig rate 2.2Hz)	HQ
15:56		TRD data flow resumes after the first ped run	HQ
16:03		TRD latch-up (CAL trig rate 2.4Hz)	HQ
16:06		TRD data flow resumes after the first ped run	HQ
16:10		power cycling of TCD	HQ
		reset DAQ
17:04		send SCI_SW_CAL_CALIB_INTV 300 to reduce the ped run interval to 5 min	HQ
18:15		ESC said the 46minute commanding window is available from 02:20GMT	KC
19:40		from 18:50 to 19:40, the Zhi trigger ranged from 6.4 to 7.2Hz	HP
20:45		from 18:40 to 19:45, the Zhi trigger ranged from 6.3 to 7.3Hz	HP
		There's no TRD latch-up till now (from 19:40)
21:03		reboot the science flight computer	HP
	1	stop taking data by sending "SCI_SW_OPMODE 0)";
	2	stop archiving Z-Hi events by sending script "arc_stop.stol";
		verify command count;
	3	send script power_off_cpu.stol and wait for the HK heartbeat reaches 120;
		repeat the previous step;
	4	ask ESC to reset (not turn off) the science CPU;
	5	HK data begin to come again;
	6	reset DAQ, check connection to TCD. Everything is ok.
	7	check the bias and HV of CAL/HDS/SCD
	8	Mask out noise channels by sending "SCI_SPARE1 0", which will execute the
		following scripts stored in the science computer:
		cal_ch_coher.stol
		hds_ch_coher.stol
		scd_ch_coher.stol
		scd_ch_mask_dummy.stol
		scd_ch_mask_hot.stol
		scd_ch_mask_hot2.stol
		scd_ch_mask_hot3.stol
	9	set cal_trigger_threshold(72);
	#	start archiving Z_Hi event "arc_start.stol";
		the Z-Hi is still around 6.6~7.1
	#	send command "SCI_SPARE0 0" to prepare flight mode
	#	start DAQ in flight mode by executing script "daq_restart.stol"
21:40		reboot the science flight computer for the second time	HP
		in step 4, trun off the science CPU instead of resetting.
21:49		SCI_CAL_TRIG_THRESLD 8,13,72
		SCI_HV_LEVEL oxo1, 0
		SCI_SW_HV_LEVEL 0x01, 0
22:08		HV is not ramping down and no message show for HV ramping down	KC
		We tried by manually but not happened
		Because we rebooted the SFC, the computer HV values were set to '0',
		so we need put HV values and clock button for sync HV level first.
		After that, we should ramping down.
		Right now, we did sync to HDS but we did not sync to CAL.
		So CAL HV is down to 0 very fast and HDS is down slowly.
		The next command window is open 10:25pmEST.
22:39		MB3 in HDS is about 4.0kv and it reamped down by pushing ramping down button.	KC
		However, MB10 in HDS is still 9kv and we did sync to MB10 in HDS.
		Tried ramping down again and it works.
23:16		We sent commands for power off cal/hds/scd and notified to ESC.	KC
23:29		ESC is doing power off and on	KC