Virtual AGC - Revision history

imported>Abr35 at 15:42, 7 July 2011

2011-07-07T15:42:42Z

← Older revision		Revision as of 15:42, 7 July 2011
Line 36:		Line 36:
	'''Program 06''': CMC Power down. When the CMC is powered down this program puts the AGC in standby. When in standby mode only the Mission clock is updated.		'''Program 06''': CMC Power down. When the CMC is powered down this program puts the AGC in standby. When in standby mode only the Mission clock is updated.

	==Boost Programs==		==[[Boost Programs]]==

	Programs 10-19 are used in the boost phase.		Programs 10-19 are used in the boost phase.
Line 44:		Line 44:
	'''Program 17''': TPI Search. This program is more associated with rendezvous then with boost though it is in the boost group. This program calculates the parameters for the transfer phase to intercept another spacecraft called "Transfer Phase Initiation".		'''Program 17''': TPI Search. This program is more associated with rendezvous then with boost though it is in the boost group. This program calculates the parameters for the transfer phase to intercept another spacecraft called "Transfer Phase Initiation".

	==Coast Programs==		==[[Coast Programs]]==

	Programs 20-29 are for navigation. Primarily for tracking other spacecraft, locating and tracking ground targets, and navigating during the transit to to and from the moon.		Programs 20-29 are for navigation. Primarily for tracking other spacecraft, locating and tracking ground targets, and navigating during the transit to to and from the moon.

imported>Irnenginer: /* Primary Functions */

2008-10-15T05:08:14Z

Primary Functions

← Older revision		Revision as of 05:08, 15 October 2008
Line 13:		Line 13:

	The AGC was designed to fulfill the following requirements:		The AGC was designed to fulfill the following requirements:

	Provide on-board Spacecraft navigation		Provide on-board Spacecraft navigation

	Provide digital autopilots for both orientation and powered flight		Provide digital autopilots for both orientation and powered flight

	Provide rendezvous navigation		Provide rendezvous navigation
	Provide Entry Navigation and Autopilot
			Provide Entry Navigation and Autopilot

	==Pre Launch and Service Programs==		==Pre Launch and Service Programs==

imported>Irnenginer at 05:07, 15 October 2008

2008-10-15T05:07:13Z

← Older revision		Revision as of 05:07, 15 October 2008
Line 9:		Line 9:
	* [http://www.hq.nasa.gov/alsj/a15/A15Delco.pdf Apollo 15 Delco Manual] -- with information on AGC usage.		* [http://www.hq.nasa.gov/alsj/a15/A15Delco.pdf Apollo 15 Delco Manual] -- with information on AGC usage.
	* [http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19730017161_1973017161.pdf Apollo experience report: Guidance and control systems - Digital autopilot design development]		* [http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19730017161_1973017161.pdf Apollo experience report: Guidance and control systems - Digital autopilot design development]

			==Primary Functions==

			The AGC was designed to fulfill the following requirements:
			Provide on-board Spacecraft navigation
			Provide digital autopilots for both orientation and powered flight
			Provide rendezvous navigation
			Provide Entry Navigation and Autopilot

	==Pre Launch and Service Programs==		==Pre Launch and Service Programs==

imported>PA-Ford: /* Pad Loads */

2008-03-18T07:51:22Z

Pad Loads

imported>Irnenginer: /* Pad Loads and Descriptions */

2008-02-15T20:59:42Z

Pad Loads and Descriptions

Show changes

imported>Irnenginer: /* Pad Loads */

2008-02-15T20:35:56Z

Pad Loads

Show changes

imported>Irnenginer at 20:25, 15 February 2008

2008-02-15T20:25:38Z

← Older revision		Revision as of 20:25, 15 February 2008
Line 77:		Line 77:
	When entering data into a register, remember to always enter it using the same scaling and precision that the register is displayed in. When entering scaled numbers always enter a +/- before the number, and always add leading zeros so that all digits are filled in the register. When entering octal numbers always omit the sign. Octal registers do not require leading zeros when entered.		When entering data into a register, remember to always enter it using the same scaling and precision that the register is displayed in. When entering scaled numbers always enter a +/- before the number, and always add leading zeros so that all digits are filled in the register. When entering octal numbers always omit the sign. Octal registers do not require leading zeros when entered.

			==Pad Loads==

	==External Links==		==External Links==

imported>Irnenginer at 01:13, 13 January 2008

2008-01-13T01:13:11Z

← Older revision		Revision as of 01:13, 13 January 2008
Line 45:		Line 45:

	'''Program 52''': [[IMU Realign checklist (Virtual AGC)\|IMU Realign]]		'''Program 52''': [[IMU Realign checklist (Virtual AGC)\|IMU Realign]]

			==Verb/Noun Basics==
			The Verb/Noun provides much of the command and parameter interface to the AGC. Astronaut commands and information about values in the display registers are given thru verbs and nouns.

			'''Verbs'''

			There are 40 normal verbs. These verbs correspond to simple actions. They are split into 4 groups display, monitor, load, and executives.

			Display verbs allow display of Noun fields. Typically they are used by programs for displaying information, using Verb 05 and 06. The astronaut can use these verbs to display a Noun at almost any time, but it is important to know that some noun may not be valid in all modes. Monitor verbs are the same as display verbs with the exception that monitor verbs continually update the registers every time step(about 1 per sec).

			Load verbs are used by the astronaut to load values into nouns. Load verbs are used to change values displayed during programs that require astronaut input.

			Executive Verbs are direct user interface and testing. Examples are Verb 37 for starting a program and Verb 35 for testing the panel lights.

			The remaining 60 verbs are called extended verbs. These verbs hold a wide range of actions, both actions requested by the astronaut and requested by the AGC. By this I mean that some verbs are entered by the astronaut to be performed by the AGC and other are displayed by the AGC for action by the astronaut. In addition, some verbs are only used during specific programs, most notably Program 20.

			There are also “flashing verbs”. This is when the Verb/Noun Line of the DSKY is flashing. This indicates to the astronaut that the AGC is waiting for a response. Flashing verbs occur during programs and some extended verbs.

			'''Nouns'''

			Like Verbs, nouns are split between two major types. The first 40 are normal nouns. These nouns contain information that is singular in nature. To out another way, the information contained in those nouns do not have different scaling, or display a single item. Two best examples are Noun 20, which contain the CDU angles all in .01 degrees, and Noun 36 containing the CMC mission time in hrs, min, secs.

			The remaining nouns are called mixed. Mixed nouns can contain information where each register contains related but independent information. All mixed nouns relate to programs and extended verbs and should not be edited outside of there programs. An example of a missed noun is Noun 40, used during burns. Register 1 shows time to/from ignition of burn/ Register 2 indicates velocity to be gained. And register 3 indicates velocity gained.

			'''Registers'''

			The registers are the three lines under the Verb/Noun Line. The data that is shown in the registers are determined from the current Noun. The registers show data in English units, such as feet/sec, Nautical miles. There are 29 scaling/units used in the registers through the nouns. One interesting aspect to the AGC is that while the display information is in English units the AGC math is all done in metric units. There are many nouns that display octal numbers. Most of these are used for setting DAP parameters, indicating star numbers, and other options. Octal numbers are indicated with the lack of a sign indication in the register.

			'''Entering Registers'''

			When entering data into a register, remember to always enter it using the same scaling and precision that the register is displayed in. When entering scaled numbers always enter a +/- before the number, and always add leading zeros so that all digits are filled in the register. When entering octal numbers always omit the sign. Octal registers do not require leading zeros when entered.


	==External Links==		==External Links==

imported>Tschachim: Added Alignment Programs

2007-02-04T20:23:09Z

Added Alignment Programs

← Older revision		Revision as of 20:23, 4 February 2007
Line 37:		Line 37:

	'''Program 20''': Rendezvous Navigation.		'''Program 20''': Rendezvous Navigation.

			==Alignment Programs==

			Programs 51-54 are used for [[IMU]] alignment.

			'''Program 51''': IMU Orientation

			'''Program 52''': [[IMU Realign checklist (Virtual AGC)\|IMU Realign]]

	==External Links==		==External Links==

imported>Mark Grant at 12:45, 14 December 2006

2006-12-14T12:45:09Z

← Older revision		Revision as of 12:45, 14 December 2006
Line 1:		Line 1:
	~~The~~ '''Virtual AGC''' code simulates the hardware of the real Apollo Guidance Computer, and can run the same software as was used on a real Apollo mission.		Ron Burkey's '''Virtual AGC''' code simulates the hardware of the real Apollo Guidance Computer, and can run the same software as was used on a real Apollo mission. This is a separate open source project which is linked into Project Apollo.

	The Virtual AGC or vAGC uses software that is believed to have flown on actual missions. Most missions in Project Apollo use '''Colossus 1A (rev249)''' otherwise known as '''Colossus249'''. It is believed that this software was used for the '''Apollo 9''' mission.		The Virtual AGC or vAGC uses software that is believed to have flown on actual missions. Most missions in Project Apollo use '''Colossus 1A (rev249)''' otherwise known as '''Colossus249'''. It is believed that this software was used for the '''Apollo 9''' mission.

← Older revision		Revision as of 07:51, 18 March 2008
Line 78:		Line 78:

	==Pad Loads==		==Pad Loads==
	Pad Loads refer to ~~paramters~~ loaded into ~~earsable~~ memory before launch or "on the pad". ~~Paramters~~ included mission specific ~~paramters~~ such as lunar landing site location, time of liftoff, and locations of ~~stelar~~ bodies used for navigation and orbital integration. the parameters also ~~inlcuded~~ digital autopilot ~~paramters~~ that are specific to the spacecraft. Currently there are 75 variables identified in Collosus 249 as pad loaded.		Pad Loads refer to parameters loaded into erasable memory before launch or "on the pad". Parameters included mission specific parameters such as lunar landing site location, time of liftoff, and locations of stellar bodies used for navigation and orbital integration. the parameters also included digital autopilot parameters that are specific to the spacecraft. Currently there are 75 variables identified in Collosus 249 as pad loaded.

	===Determining Pad Load values===		===Determining Pad Load values===
	Since no listing is currently known to ~~exsist~~ of CSM pad loads for any Collosus version, pad load ~~varibles~~ and values had to be determined through examination of the source code listing and ~~avalibel documenation~~. values are ~~detrmined~~ through calculations, from documentation, and in some cases, ~~emprical~~ testing.		Since no listing is currently known to exist of CSM pad loads for any Collosus version, pad load variables and values had to be determined through examination of the source code listing and available documentation. values are determined through calculations, from documentation, and in some cases, empirical testing.

	===Pad Loads and Descriptions===		===Pad Loads and Descriptions===
	TEPHEM: The time between July 1 and the launch. This variable is used as a ~~indepentent~~ time reference to all time based calculations. This ~~varivable~~ is ~~incrmented~~ at liftoff by adding the current AGC time to TEPHEM so, in practice the ~~varible~~ is precceds the actual liftoff time and the AGC clock is ~~incremeted~~ at AGC turn on to coincide with the launch time.		TEPHEM: The time between July 1 and the launch. This variable is used as a independent time reference to all time based calculations. This variable is incremented at liftoff by adding the current AGC time to TEPHEM so, in practice the variable is precceds the actual liftoff time and the AGC clock is incremented at AGC turn on to coincide with the launch time.

	AZO: The Earth Azimuth Defines the rotation of the Earth with respect to the Basic Coordinate system. It relates the Basic Coordinate system with the Earth coordinate system defined by the angle between the two on July 1. The AGC advances that angle to the mission time based on TEPHEM and MET		AZO: The Earth Azimuth Defines the rotation of the Earth with respect to the Basic Coordinate system. It relates the Basic Coordinate system with the Earth coordinate system defined by the angle between the two on July 1. The AGC advances that angle to the mission time based on TEPHEM and MET
Line 94:		Line 94:
	LAUNCHAZ: The launch azimuth from north. It is used to determine the orientation of the IMU in its launch position.		LAUNCHAZ: The launch azimuth from north. It is used to determine the orientation of the IMU in its launch position.

	CSMMASS: "Wet" weight of the CSM at launch. It is the Mass of all ~~cosumables~~ loaded into the CSM at launch. It is used mostly to determine how the CSM reacts to automatic RCS and TVC ~~movments~~.		CSMMASS: "Wet" weight of the CSM at launch. It is the Mass of all consumables loaded into the CSM at launch. It is used mostly to determine how the CSM reacts to automatic RCS and TVC movements.

	LEMMASS: Same as the CSMMASS except for it for the LEM for use when it is attached to the CSM.		LEMMASS: Same as the CSMMASS except for it for the LEM for use when it is attached to the CSM.

	EMSALT: The AGC reports in P61 initial ~~paramters~~ used to setup the EMS scroll. This ~~varible~~ sets the Altitude for which these parameters are determined. It is an estimate of the altitude where the spacecraft has a atmospheric drag of .05g		EMSALT: The AGC reports in P61 initial parameters used to setup the EMS scroll. This variable sets the Altitude for which these parameters are determined. It is an estimate of the altitude where the spacecraft has a atmospheric drag of .05g

	TIMEMO:Time between July 1 and a point midway through the mission such that there is a 14 day window in which the mission resides. This ~~varible~~ defines the 0 point for VECOEM, RESO, VESO, and OMEGAES.		TIMEMO:Time between July 1 and a point midway through the mission such that there is a 14 day window in which the mission resides. This variable defines the 0 point for VECOEM, RESO, VESO, and OMEGAES.

	VECOEM:defines a 3 ~~deminsion~~ 9 degree polynomial that defines the position of the moon in relation to the earth during the mission.		VECOEM:defines a 3 dimension 9 degree polynomial that defines the position of the moon in relation to the earth during the mission.

	RTED1:		RTED1:
Line 121:		Line 121:
	ETVCDT/2: Defines the Filter Bandwidth based on the sampling time of the CDU angles into the TVC DAP control Loop.		ETVCDT/2: Defines the Filter Bandwidth based on the sampling time of the CDU angles into the TVC DAP control Loop.

	ETSWITCH: Time between ~~inital~~ correction gain and nominal gain feined by ECOFRAC and EREFRAC. CSM/LM value is 6sec and ~~havled~~ for CSM only configuration		ETSWITCH: Time between initial correction gain and nominal gain feined by ECOFRAC and EREFRAC. CSM/LM value is 6sec and halved for CSM only configuration

	ECOFRAC: Gain used for initial correction of thrust misalignment. R-577 ~~qoutes~~ a ~~zalue~~ of 1 which is ~~doulbled~~ for the CSM only configuration		ECOFRAC: Gain used for initial correction of thrust misalignment. R-577 quotes a value of 1 which is doubled for the CSM only configuration

	EREPFRAC: Gain used after the ~~inital~~ correction for the CSM configuration. The transition defined by ETSWITCH. R-577 ~~qoutes~~ value of .250		EREPFRAC: Gain used after the initial correction for the CSM configuration. The transition defined by ETSWITCH. R-577 quotes value of .250

	EREPFRAC +1: Gain used after the ~~inital~~ correction for the CSM/LM configuration. The transition defined by ETSWITCH. R5-77 ~~qoutes~~ value of .0375		EREPFRAC +1: Gain used after the initial correction for the CSM/LM configuration. The transition defined by ETSWITCH. R5-77 quotes value of .0375

	AP0-BP3:		AP0-BP3:
Line 158:		Line 158:
	DVTHRESH: Determines value of velocity that defines a SPS thrust failure.		DVTHRESH: Determines value of velocity that defines a SPS thrust failure.

	POLYNUM: a seven degree polynomial defining the pitch of the ~~Staurn Lainch~~ vehicle during the early stage of boost. It is used to determine error needle deflection during launch, giving an indication to the astronaut the the ~~Lainch~~ Vehicle is on course.		POLYNUM: a seven degree polynomial defining the pitch of the Saturn Launch vehicle during the early stage of boost. It is used to determine error needle deflection during launch, giving an indication to the astronaut the the Launch Vehicle is on course.

	SATLRT: Roll rate during roll program at launch used like POLYNUM.		SATLRT: Roll rate during roll program at launch used like POLYNUM.
Line 164:		Line 164:
	RPSTART: Defines when the roll program starts after liftoff.		RPSTART: Defines when the roll program starts after liftoff.

	POLYSTOP:Defines when the POLYNUM ~~polynokmals~~ are valid.		POLYSTOP:Defines when the POLYNUM polynomials are valid.

	LADPAD:Nominal Lift/Drag ~~Coeffcient~~		LADPAD:Nominal Lift/Drag Coefficient

	LODPAD:Final Phase Nominal Lift/Drag		LODPAD:Final Phase Nominal Lift/Drag
Line 174:		Line 174:
	CDUCHKWD		CDUCHKWD

	HORIZALT:Because of atmospheric effects the actual ground horizon could be difficult to determine. This ~~vearible~~ sets a location above the horizon to use as the sighting horizon.		HORIZALT:Because of atmospheric effects the actual ground horizon could be difficult to determine. This variable sets a location above the horizon to use as the sighting horizon.
	ALTVAR: Alternate variance for alternate line of site. Adds a variance to the X-Matrix when using a alternate line of sight for marking. (See W-Matrix)		ALTVAR: Alternate variance for alternate line of site. Adds a variance to the X-Matrix when using a alternate line of sight for marking. (See W-Matrix)

	WRENPOS: Defines ~~Rendezous~~ positional variance using optical sighting marks (See W-Matrix)		WRENPOS: Defines Rendezvous positional variance using optical sighting marks (See W-Matrix)

	WRENVEL: Defines ~~Rendezous~~ velocity variance using optical sighting marks (See W-Matrix)		WRENVEL: Defines Rendezvous velocity variance using optical sighting marks (See W-Matrix)

	RMAX: Defines the maximum positional delta correction during ~~rendozous sightiung~~ marks		RMAX: Defines the maximum positional delta correction during rendezvous sighting marks

	VMAX: Defines the maximum velocity delta correction during ~~rendozous sightiung~~ marks		VMAX: Defines the maximum velocity delta correction during rendezvous sighting marks

	WORBPOS: Defines Orbital positional variance using optical sighting marks (See W-Matrix)		WORBPOS: Defines Orbital positional variance using optical sighting marks (See W-Matrix)
Line 203:		Line 203:
	VESO: Defines the velocity of the sun with respect to earth at the time determined by TIMEMO		VESO: Defines the velocity of the sun with respect to earth at the time determined by TIMEMO

	OMEGAS: Defines the ~~angluar~~ velocity of the sun		OMEGAS: Defines the angular velocity of the sun

	INTVAR:		INTVAR:
Line 211:		Line 211:
	WMIDVEL: Defines Cislunar velocity variance using optical sighting marks (See W-Matrix)		WMIDVEL: Defines Cislunar velocity variance using optical sighting marks (See W-Matrix)

	RVAR: Defines the variance of RADAR range for ~~rendozous~~ updates		RVAR: Defines the variance of RADAR range for rendezvous updates

	RVARMIN:		RVARMIN: