Upthread: Results of the Apollo Spacecraft Software Configuration Control Board meeting of April 23 (Apr 26, 1968)
Downthread: Results of the June 25 Apollo Spacecraft Configuration Control Board (ASCCB) meeting (Jul 01, 1968)
See list belowJUN 12 196868-FM-T-123FM/Deputy ChiefResults of the June 11 Apollo Software Configuration Control Board (ASCCB) meeting
1. Today's meeting was short and sweet – nothing particularly controversial. It started out with a discussion of the Stage Verify discrete. As noted it my last memo on this subject, program changes have been approved for Luminary such that the LGC completely ignores the Stage Verify discrete. Apparently we have generated enough concern that some wiring changes may be made in the LM's using Sun- dance to make the circuit interrupt redundant. This should help insure getting this discrete which is needed and used by Sundance.
2. Although Dave Hoag (MIT) could not present a particularly strong argument for approving PCN-173, it seemed easier to leave this capability in Luminary and Colossus than to delete it. The capability I am referring to is an extended Verb which permits DSKY display of RMS position and velocity error computer from the W-matrix. We are assured that it has been coded in such a way that it can be easily removed if we find we need the 90 words of memory it consumes.
3. GCD personnel expressed a concern regarding the stroking test program. Specifically, they feel it highly desirable to provide a Verb to terminate the excitation and also want to change the restart protection such that in the event of a restart, the stroking test is terminated. The only alternative to this would be procedural, namely to switch from G&N to SCS and then back again if troubles are encountered. Of course, you could always turn off the engine, but that is considered undesirable if it could be avoided.
4. FCSD submitted a new PCR (No. 205), duplicating one the board dis- approved about three months ago which would have provided the DSKY display of raw rendezvous radar data. Of course, it's too late for Sundance, but MIT was requested to advise us of the Luminary impact if they implement this in the simplest possible way. That is, eliminate from the basic request the radar angle display, the automatic update feature, reduce the number of programs that can be operating during this display, etc. If the impact is unacceptable, this change will be considered further for Luminary #2.
5. PCR 203 is also an FCSD request to provide Saturn takeover at max-Q. MIT's estimate of schedule impact is five days on Colossus. Since it is not a mandatory requirement, this program change is also going in the post Colossus hopper.
6. As you already know, a meeting is scheduled for Monday, June 24 to discuss follow-on spacecraft programs. This is an important one if you have changes you want made. The recommendations coming from that meeting will be carried to the next ASCCB meeting currently scheduled for June 25. The next Joint MSC/MIT Program Development Planning meeting has apparently now slipped to the second week of July, if you are interested.