In the descent of Apollo 11 a famous alarm happened, the 1202 alarm.
In the descent of Apollo 11 a famous alarm happened, the 1202 alarm. |
 Initially the radar switch was on the LGC position, and, in this position, everything was OK, the AGC was receiving normal radar pulses. |
 But Buzz Aldrin would have put this radar switch on the "SLEW" position. The dialog says that it was because of an erroneous indication of the checklist, but he would have given an other explanation, suggesting that it would have been his own initiative. |
 In this position, the mission report says that two dephased signals of high frequency would have created artificial fast pulses which had nothing to do with the real radar input; as the creation of these fast radar pulse was internal, and not external, it could have been tested on earth, and so the engineers could not have ignored it, it could only be intentional. |
 The problem is that, unlike all the other computers, the processor of the AGC was counting itself these pulses, with what they call "hidden instructions", that is instructions which run independently of the current program, but which prevent an instruction of the current program to be executed each time that a "hidden" instruction is executed. |
 This means that the execution time of the periodical guidance task is not determined, it can vary according to the frequency of the hardware pulses that the AGC has to count. When the AGC receives normal pulses, the guidance task can still finish its work in time. |
 But, when the AGC started receiving the very fast radar pulses, it has started to take too much time to count these radar pulses, which means that the guidance routine was taking more time to finish its work, for being too much pertubed by these fast radar pulses. |
 The consequence is that the guidance task, because of these exaggerated perdubations, could no more finish its work in time, and there was an accumulation of guidance tasks waiting to be executed, as it was automatically started every two seconds. |
 The result was that there was a moment that all the available resources had been drained out, and, at that moment, the computer had to be restarted, with the light of the 1202 alarm going on. It is obvious that, with a computer working so erratically, it could no more do its normal work. |
 What's ironical is that this situation could perfectly have been avoided. Indeed, no normal processor counts itself hardware pulses. In all normal systems (including the one of the Saturn rocket), the hardware pulses are always counted by electronic counters, and an electronic counter is rather easy to do with transistors (as this schema shows), and even an electronician beginner can make one. |
 And the count of pulses of the electronic counter can be read by the processor with an IO read operation. |
 And precisely, the AGC had an IO read instruction, which means that it could perfectly have read the count of pulses from an electronic counter counting them. |
 So, instead of using the normal standard procedure, i.e. making an electronic counter count the pulses, and read the count of pulses from it with an IO operation, which would have ensured that the execution time of the guidance routine would have been constant, and would not have been increased by the radar pulses, whatever the frequency of these radar pulses... |
 ...The AGC was counting itself these radar pulses (with "hidden instructions", which was an unique specificity of the AGC), which means that, the faster the radar pulses, and the more the guidance routine was slowed down, which could have a critical effect when these radar pulses were very fast. |
 And the problem of the 1202 alarm could have immediately stopped if the ground had instructed the astronauts to put the radar switch back on "LGC"; but, no, the ground just told the astronauts to ignore the problem and proceed, with the consequence that the 1202 alarm (or 1201 alarm) could happen again. |
 In other words, as well in the Apollo 14 mission and the Apollo 11 mission, the engineers have created an insane situation which should never have happened, which was handled in an aberrant way, and never the engineers would have created this type of situation in normal missions, they would never have taken such insane ricks. |
 The only possible conclusion is that the engineers are sending us very clear signs that the missions were not real. |
