| 12/18/2004 |
|
|
|
|
|
|
|
|
| 2:02 |
|
ESC said they saw the error
messege on their data flow computer every few minutes. |
|
SO |
|
|
|
|
They asked us to reset our
computer. So we killed cdaq_cli and restarted. |
|
|
|
| 2:05 |
|
Data flow resumed |
|
|
|
| 3:00 |
|
warning : data file already open ; closing |
|
|
|
| 3:15 |
|
sent commands : SCI_SW_NOOP, SCI_SW_OPMODE 0 |
|
|
|
|
sent script : daq_restart.stol |
|
|
|
| 3:26 |
|
The problem was recured, so we
cleared the buffer and restarted the procedure |
|
|
|
|
SCI_SW_OPMODE 0 |
|
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
| 3:37 |
|
ESC said there will be switching
satellite soon. Data flow will be stopped for few minutes. |
|
YS |
|
|
| 3:38 |
|
>> cdaq_rstr : connection closed. Waiting for connection |
|
YS |
|
|
|
No Housekeeping update |
|
|
|
| 3:54 |
|
ESC said that now CREAM is out
of TDRSS covering area for 45 minutes. They are going to send us housekeeping
packet using Iridium frequently |
|
YS |
|
|
|
It stoped to uptadate at 8:51:41(NZT), 3:51:50(EST) |
|
|
|
| |
|
Acturally, ESC sent a packet to
us. But there was no housekeeping update. |
|
|
|
|
I thought, cdaq_rstr connection was closed, so we couldn't get
it. |
|
|
|
|
I asked ESC for a next packet
make connection to port 8003 first
and send the packet |
|
|
|
| 4:19 |
|
ESC said when they send a packet
from Iridium they have to send to PORT 8001, There was no option. For our side, PORT 8001 is CDPS3 and CDPS3
was not running cdaq_cli. That means, we were not ready for receiving the
packet. |
|
YS |
|
|
|
In 15 minutes later, TDRSS will
comes back. There will be no more Iridium packet this time. |
|
|
|
| 4:34 |
|
We got the data again |
|
YS |
|
|
|
So we restarted all procedure |
|
|
|
|
SCI_SW_OPMODE 0 |
|
SO |
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
| 4:52 |
|
warning : data file already open ; closing |
|
SO |
|
|
|
SCI_SW_OPMODE 0 |
|
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
|
However, due to out of
commanding window time, we couldn`t send CMDs |
|
|
|
| 5:22 |
|
We tried it again, so the CMDs were sent successfully |
|
SO |
|
|
|
SCI_SW_OPMODE 0 |
|
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
| 8:53 |
|
Data flow stopped. ESC said it
will be back in 16 minutes according to TDRSS schedule for data flow channel. |
|
YS |
|
|
| 9:53 |
|
data flow restarted |
|
JH |
|
|
| 9:56 |
|
PKTQ: 33%, CAL trigger rate: 30~40Hz |
|
JH |
|
|
|
|
sent
command script "cal_trig_threshold100.stol" |
|
|
|
| 10:08 |
|
SCI_SW_OPMODE 0 |
|
JH |
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
| 10:34 |
|
SCI_SW_OPMODE 0 |
|
HP |
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
| 10:35 |
|
sent command script "cal_trig_threshold80.stol" |
|
JH |
|
|
| 10:41 |
|
CAL trigger rate: 5~12%, Network rate: 86~89% |
|
JH |
|
|
|
sent command script "cal_trig_threshold85.stol" |
|
|
|
| 10:45 |
|
CAL trigger rate is 0.6% |
|
JH |
|
|
|
sent command script "cal_trig_threshold82.stol" |
|
|
|
|
CAL trigger rate: 1~2%, Network rate: 20~40% |
|
|
|
| 10:53 |
|
we got some play-back data until 11:07am |
|
JH |
|
|
| 11:34 |
|
we got some play-back data until 12:07am |
|
JH |
|
|
| 11:51 |
|
SCI_SW_OPMODE 0 |
|
HP |
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
| 12:00 |
|
SCI_SW_OPMODE 0 |
|
HP |
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
| 12:02 |
|
CAL trigger rate: over 10%, Network rate: over 50% |
|
JH |
|
|
|
sent command script "cal_trig_threshold85.stol" |
|
|
|
| 12:53 |
|
ESC is playing back the data about 4 hours ago |
|
HQ |
|
|
| 13:00 |
|
The satellite downlink quality is poor a few min ago |
|
HQ |
|
|
| 13:15 |
|
Restart the cream program
because there are too many error messages |
|
HQ |
|
|
| 13:20 |
|
Still the Satellite downlink quality is not stable |
|
HQ |
|
|
|
Get the Error message frequently |
|
|
|
| 13:35 |
|
Now the data streaming is stable and fine |
|
HQ |
|
|
| 13:37 |
|
SCI_SW_OPMODE 0 |
|
HQ |
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
| 13:43 |
|
CAL trigger rate: over 10%, Network rate: over 50% |
|
JH |
|
|
|
sent command script "cal_trig_threshold87.stol" |
|
|
|
| 14:20 |
|
CAL trigger rate is still over 5%, Network rate: over 51.4% |
|
JH |
|
|
|
sent command script "cal_trig_threshold90.stol" |
|
|
|
| 14:24 |
|
SCI_SW_OPMODE 0 |
|
HQ |
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
| 14:27 |
|
CAL trigger rate: under 1%, Network rate: under 20% |
|
JH |
|
|
|
sent command script "cal_trig_threshold87.stol" |
|
|
|
| 16:19 |
|
It
keeps getting error messages, ESC said something wrong about the |
HQ |
|
|
|
far end connection |
|
|
|
| 16:26 |
|
No data flow, ESC has problem to get data |
|
HQ |
|
|
| 16:55 |
|
ESC said we can not send command for a while |
|
HQ |
|
|
| 17:02 |
|
SCI_SW_OPMODE 0 |
|
JH |
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
| 17:05 |
|
No data til 17:15, need playback |
|
HQ |
|
|
| 17:28 |
|
SCI_SW_OPMODE 0 |
|
HQ |
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
| 17:48 |
|
SCI_SW_OPMODE 0 |
|
JH |
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
| 18:06 |
|
SCI_SW_OPMODE 0 |
|
HQ |
|
|
|
SCI_SNIO_CONTROL 21,0 |
|
|
|
|
Execute script daq_restart.stol |
|
|
|
| 19:35 |
|
The data flow was
stopped because of proper time |
|
SO |
|
|
| 19:57 |
|
It was restored again. |
|
SO |
|
|
| 22:09 |
|
Sending commands. (3:09 GMT) |
|
SO |
3:09 |
|
|
SCI_SNIO_CONTROL 12,0x4C |
|
|
|
|
SCI_SNIO_CONTROL 13,0x00 |
|
|
|
|
SCI_SW_LOGFILE_SEND |
|
|
|
| 22:20 |
|
Asked ESC to upload files of pmf010.000 ~pmf012.007 |
|
YS |
|
|
| 22:44 |
|
ESC started uploading 24 PMF files and playback data |
|
YS |
|
|
|
Simon said they finished uploading pmp010.000 and 010.001 |
|
|
|
|
They are going to continue at next command window. |
|
|
|
|
|
|
|
|
|
|
|
|
|