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 71

(This page is even worse than page 70 in that the extent of photo-reduction is much larger as the number of rows in the last column is now 19, compared with 11 on page 70, making almost all of entries impossible to decipher, but I will do my best.

In the meantime, I forgot to mention something with page 69. There is an arrow pointing upward from C5R11 to C5R10.)

Fig. III-2-2 FTA relating to cause candidates for "CI-PSU not being put into ON as required" (part 2 of 2)

(This figure is effectively a 6C and 19 R matrix. Header entries from C2 to C6 are the same as on page 70. C1 header is continuation, I think and there is no entry in C1 column at all.)

C2R1: Circle: 500: CI-PSU XXX (here, XXX means impossible to recognise characters in this space)

(and entries in C3 all come from C2R1 and they are):

C3R1: Cross: 510: ?PS XXX (here, ? means there is something in this space which cannot be recognised)

C3R2: Cross: 520: S (or 5)PM?, XXX

C3R3: Cross: 530: EPT-SA XXX

C3R4: Triangle: 540: WS (or 5)-SA XXX

C3R6: Cross: 550: DR XXX

C3R7: Triangle: 560: TC XXX

C3R12: Triangle: 570: HCE XXX

C3R17: ***: 580: LVDT XXX Here, *** is a character string, not a circle nor triangle. I strained my eyes and I still could not recognise what it is)

C3R18: ***: 590: USO XXX

C3R19: ***: XXX: pressure sensor XXX

C4R1: Cross: 511: XXX ( and this XXX will be the same in all rows of this column)

C4R2: Cross: 521: XXX

C4R3: Cross: 531: XXX

C4R4: Cross: 541: XXX (and this and the next entry comes from Triangle: 540 in C3)

C4R5: Triangle: 542: single event upset

C4R6: Cross: 551: XXX

C4R7: Triangle: 561: XXX

C4R12: Triangle: 571: XXX

C4R17: ***:581: XXX

C4R18: ***: 591: XXX

C4R19: ***: 5A1?: XXX

C5R7: Triangle: 561A: total dose effect

C5R8: Triangle: 561B: single event latch up

C5R9: Triangle: 561C: latch up by discharge

C5R10: Triangle: 561D: accidental

C5R11: Cross: 561E: bad soldering job

C5R12: Triangle: 571A: total dose effect

C5R13: Triangle: 571B: single event latch up

C5R14: Triangle: 571C: latch up by discharge

C5R15: Triangle: 571D: accidental

C5R16: Cross: 571E: bad soldering job

(and the last column entries are all too bad. There are entries in R1 to R9, R11 to R14, and R16 to R19. It is possible to read a few characters in any of these entries, but this column, giving reasons, contains much larger number of character strings and it is no use to be able to read here and there and translation will be bound to be wrong)

end of page 71

This is perhaps a good time for me to mention the coding issue which has been tormenting me, a particularly acute problem if I am facing a table. I will try to be as succinct as possible.

My ancesters did not have characters and burrowed them from China (Thank you! China) Making the story brutally simplistic, Chinese characters are all pictures (hieroglyphic), made up with a lot of strokes. So, the usual 8 bit coding system cannot cope with the complexity. We therefore need 16 bits and I have no idea why they do it, but they here use the 16 bit system for coding (simpler) alphanumerics as well.

Result is confusing. 16 bit alphabets are OK as they are of the same shape, but simply "fatter" in appearance, but numbers look deceptively similar. My problem is tables. Are the numbers in the table 8 bit coded or 16 bit coded? For that matter, are the line elements, forming the frame of tables, are they what they look like, or not?

My assumption so far is that people who made these tables used 8 bit coding for alphanumeric entries. The only way to check is to copy a table (not a picture table, but text table) for experiment. I meant to do that yesterday, but faced with the picture table not wanting to be pasted here I did not managed to do it. I will try again when all of the translation work comes to an end.

Now, what follows is an extra for your Christmas conversations.

So, characters came from China and you want to write, say, "I eat an apple".

What my ancesters did was to put "I- like picture, Eat- like picture, Apple- like picture". They, however, made a fatal mistake in all this because "XXX-like pictures" were all chosen for their sounds, not understanding each is a picture. Chinese naturally pointed out that above sequence actually reads "You drive a cow". Here, of course, this is only by way of explanation.

So, my ancesters eventually allocated the right pictures in the right places. But, they did not like it at all. Too many strokes! So, they decomposed Chinese characters into components and came up with 2 phonetic sets of characters. Had they stayed with these two sets only my current problem should not be existing.

In reality they decided to retain a portion of these Chinese pictures as well. So, our current writing system is a mixture of phonetic and hieroglyphic characters. This is why 16 bit coding system is used here and how my dilemma started.

Merry Christmas from Pandaneko to all of my colleagues and all those space probes out there in deep space!