Nozomi in perspective, Revisiting the causes of failure Options

[pandaneko]

http://www.mext.go.jp/b_menu/shingi/uchuu/...ts/04061101.pdf

Above pdf file will be translated for aspiring students in aeronautics, control engineering etc. so that in future lay people like me will be able to enjoy planetary scenes and events without worrying about failures.

The overall title is "Looking into the causes of failure and trying to find the right measures to take for the future with respect to the 18th scientific satellite (PLANET-B ) not inserted into Mars orbit as planned" and it is dated 21 May 2004.

This file is very much detailed at 1.1 megabytes and the number of pages is about 40, I think. In addition, I will be translating 3 more files after this particular file. They will be;

1. ISAS file with views and comments on the failure
2. Another ISAS file, a newsletter written out in a series of 4 individual letters.
3. JAXA file, which is a press release and it is a very concise document with just sufficient details.

Re concise link making I tried a few times, but I simply failed and all the links will be fully pasted out as required.

Pandaneko

[pandaneko]

http://www.mext.go.jp/b_menu/shingi/uchuu/...ts/04061101.pdf

above for ease of reference

page 69

Fig. III-2-1 FTA relating to the cause candidates for "not being able to switch to telemetry mode"

(Here, I want to do a few things (experiments) to make sure that what I have been doing is not a waste in the sense of translation quality (?).)

(Here, if I am right, you should be looking at a table (please refer to the original PDF), not a proper table in the sense of it being square in shape, but still retaining its remote hope for being one. My only regret is that I have given R1 to the top header line's row number as you will see in my translation. Actual table elemtns (apart from header line) could have been named from R1 ( In my notation of what folows R1 is denoted as R2, I am afraind), instead of R2 against each column number) (I will also experiment with lines used for squaring off areas used for character strings)

C1R1: Tree top event

C2R1: Primary cause

C3R1: Secondary cause

C4R1: Tertiary cause

C5R1: Judgement reasons

(After this you must be seeing a thick horizontal line separating the header entries above it and the table contents which follows below the horizontal demarcation line)

C1R2: No reception desipite the satellite being in TLM ON mode

C2R2: X 100: Data processing unit mulfunction (X means negative, I think)

(This "X 100: Data processing unit mulfunction" is based on my onw notation and I will seek your comments on the reproduction quality of this particular entry (C2R2) as a member of the larger table. For instance, ":" is simply a short vetical line for seperation between 100 and what follows. For that matter, there is another vertical line in the original text between X and what follows it. Can you see all these features with your 8 bits OS codnig system)

(OMG!, I have lost what I had in mind for further explanation..., but let me continue anyway)

C2R3: X 200: TMX mulfunction

C2R4: X 300: TCI mulfunction

(row numerbs are effective numbers only, not corresponding to the finest row numbers on the extreme right column)

C3R2: (there is a horizontal connection from 100) X 110: Command autonmation sequence mulfunction

C3R3: X 120: Data bus mulfunction

C3R4: X 210: Command recption circuit mulfunction

(horizontal line connection from 200)

C3R5: X 220: Reley device mulfunction

C3R6: X 310: TCI itslef only going bad

C3R7: X 320: Power cut-off

(now we move on to the next column, which is long)

C4R2: X 111: autonomous (or automatic) sequence DISABLE

C4R3: X 112: Devices shrank back to IPL mode

C4R4: X 211: Device internaland +5V system mulfunction

C4R5: X 212 Responsible componetnts mulfunction

C4R6: X 221: Device internal and +V12 sytem mulfunction

C4R7: X 222: Responsible components mulfunction

C4R8: X 311: Responsible components mulfunction

(Herre after column 5 entries, only row numbers)

C5R2: We sent the same sequence of commands as REAL, but we could not confirmt its outome.

C5R3: after starting up the devices once again, we sent the same related sequence command, but we could not confirm its outcome.

C5R4: We were able to confirm that regular outcome of the command XPA ON and OFF and there was no reason why some other commands copuld not be accepted and executed acccordingly.

C5R6: Ditto

C5R7: Ditto

C5R8: Same as R5

C5R9: Same as R6

C5R10: Power source (CI-PSU) for TCI is the same and is commonly used for the heater control system. Therefore, it is accepted that the POWER OFF led to freezing of propulsive materials and further leading to inability of keeping the Earth in view.

Also, POWER OFF can explain all othe events.

C5R11: Analyses later showed that the time ellapse between POWER OFF and actual freezing was 2 hours at maximum, but this itself does not negate any of the operational sequence.

end of page 69

P