Skip to main content
  • Home
  • Development
  • Documentation
  • Donate
  • Operational login
  • Browse the archive

swh logo
SoftwareHeritage
Software
Heritage
Archive
Features
  • Search

  • Downloads

  • Save code now

  • Add forge now

  • Help

https://github.com/virtualagc/virtualagc
25 December 2018, 16:55:25 UTC
  • Code
  • Branches (14)
  • Releases (0)
  • Visits
    • Branches
    • Releases
    • HEAD
    • refs/heads/20080615
    • refs/heads/Fictitious-1201
    • refs/heads/block1
    • refs/heads/counters
    • refs/heads/empty
    • refs/heads/gh-pages
    • refs/heads/luminary130
    • refs/heads/master
    • refs/heads/scenarios
    • refs/heads/schematics
    • refs/heads/wiki
    • refs/import/raw
    • refs/tags/20100220
    No releases to show
  • 22dd35c
  • /
  • BasicsDSKY.md
Raw File Download
Take a new snapshot of a software origin

If the archived software origin currently browsed is not synchronized with its upstream version (for instance when new commits have been issued), you can explicitly request Software Heritage to take a new snapshot of it.

Use the form below to proceed. Once a request has been submitted and accepted, it will be processed as soon as possible. You can then check its processing state by visiting this dedicated page.
swh spinner

Processing "take a new snapshot" request ...

To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
Select below a type of object currently browsed in order to display its associated SWHID and permalink.

  • content
  • directory
  • revision
  • snapshot
origin badgecontent badge
swh:1:cnt:6d9acc52e5c39b88d3f7846957c23ea0e381063e
origin badgedirectory badge
swh:1:dir:22dd35ca3bdb6355d3f9c5b92c85d524e80082ce
origin badgerevision badge
swh:1:rev:689b58c51d2268e9fc3a5c61aa74c9321891ddea
origin badgesnapshot badge
swh:1:snp:cdcd2bc43331a436e8c659ba93175ef7d7eb339b

This interface enables to generate software citations, provided that the root directory of browsed objects contains a citation.cff or codemeta.json file.
Select below a type of object currently browsed in order to generate citations for them.

  • content
  • directory
  • revision
  • snapshot
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Tip revision: 689b58c51d2268e9fc3a5c61aa74c9321891ddea authored by Google Code Exporter on 07 April 2015, 19:26:57 UTC
Migrating wiki contents from Google Code
Tip revision: 689b58c
BasicsDSKY.md
![http://virtualagc.googlecode.com/svn/trunk/Apollo32.png](http://virtualagc.googlecode.com/svn/trunk/Apollo32.png)
# 1. DSKY Basics #
The DSKY is the "display/keyboard" used by the Apollo Guidance Computer (AGC).  The DSKY provided only a means to input keyboard data to the AGC, or to display visual information at command of the AGC, and therefore had little or no functionality of its own, when considered as a stand-alone device. The DSKY was used in both the Command Module and the Lunar Module.

> ![http://virtualagc.googlecode.com/svn/trunk/doc/images/DSKY.png](http://virtualagc.googlecode.com/svn/trunk/doc/images/DSKY.png)

## 1.1 Interacting with DSKY ##
The DSKY design used a pretty simple but smart interface to allow the user to interact with the AGC. A method of verbs and nouns were used to request an operation (i.e. the verb) and on what (i.e. noun) you wanted this operation to execute on. Each distinct verb was assigned a number and each noun was assigned a number. For example the verb "display" was assigned the number 16 and noun 36 was assigned to "ground elapsed time (GET)". So to display the current GET you would press "V" followed by the number 16 and then "N" followed by the numbers 36 thereafter executed when pressing Entr key. A shorthand notation in check lists was used to express the above sequence: V16N36E. In some cases just a simple verb was sufficient to execute a certain command.

Similarly if the AGC required the user to input certain values or ask to confirm (i.e the Pro(ceed) key ) it would display a flashing verb/noun combination to indicate that user input is requested.

To display output in response to a request or when punching input in the DSKY the registers [R1](https://code.google.com/p/virtualagc/source/detail?r=1) (top row), [R2](https://code.google.com/p/virtualagc/source/detail?r=2) (middle row) and [R3](https://code.google.com/p/virtualagc/source/detail?r=3) (bottom row) were used.

To show which program was running the right top 2 digits were used. Programs were applications that executed a specific task. For example program 64 (P64) was the high gate approach program where as P66 was the final landing phase program and P68 the post landing shutdown program to prevent inadvertent RCS firing. A program was typically started with the verb 37 followed by the program number. To start program 66 one would enter: V37E66E Notice that after V37E the DSKY starts flashing the Code 37 to ask the crew for the program input.

When entering numbers it was assumed that octal numbers where used unless the user would use the sign +/- symbol; in that case decimal numbers were assumed. Also when using decimal numbers leading zeros must be entered this is not the case for octal numbers. When input is requested in [R1](https://code.google.com/p/virtualagc/source/detail?r=1) the row for [R1](https://code.google.com/p/virtualagc/source/detail?r=1) would clear and the user can provide its input. To correct the input press the CLR key before pressing Entr.

## 1.2 Status Indicators ##
Also part of the DSKY are the status indicator lights. These are illuminated to indicate warnings or caution. The following is a list of the indicator lights with an explanation of when the light is illuminated.
  * UPLINK ACTY: Received a complete 16-bit digital uplink message
  * NO ATT: Inertial Subsystem is in coarse align
  * STBY: When AGC is in standby mode to preserve power
  * KEY REL: Crew pressing keys or Input requested (except PRO,RSET and ENTR)
  * OPR ERR: Incorrect sequence of keys pressed
  * TEMP: Inertial Subsystem temperature outside of nominal values
  * GIMBAL LOCK: Middle gimbal exceeds +/-70 degrees
  * PROG: Computational difficulty detected
  * RESTART: Temporary Hardware or Software failure detected (Reset)
  * TRACKER: Issue with the OCDU or rendezvous radar

## 1.3 Keyboard ##
The keyboard exist of a set of numerical buttons,sign buttons and command buttons. The numerical buttons aren't further explained since their purpose is just to enter digits. The sign buttons although straight forward immediately flag the AGC that a decimal number is being entered. The remaining set of Keys is enumerated below with a brief explanation.
  * VERB: Interpret the next 2 numerical as verb code
  * NOUN: Interpret the next 2 numerical as noun code
  * CLR: Clear the data display (1st the active, successive presses clears the other 2)
  * PRO: Proceed with entered data or go standby if power down program is started
  * KEY REL: Allow AGC to display data if you were entering data
  * ENTR: Requested Data Entered and start Execution
  * RSET: Extinguishes the illuminated caution indicators

Here is a short video demonstrating the lamp test followed by starting the idle program.

> <a href='http://www.youtube.com/watch?feature=player_embedded&v=PF-9SyWM1Mw' target='_blank'><img src='http://img.youtube.com/vi/PF-9SyWM1Mw/0.jpg' width='425' height=344 /></a>

In this demonstration you can see that VERB 35 is already displayed but the enter key has not been pressed yet. After the lamp test the idle program is started with V37E00E.

## 1.4 Some Basic Commands ##
The following is a list of some basic commands to demonstrate the interaction with the DSKY.

| **Verb Noun** | **Description**                                                     |
|:--------------|:--------------------------------------------------------------------|
| V35E        | Execute Lamp Test                                                 |
| V36E        | Fresh restart                                                     |
| V16N36E     | Display ground Elapsed Time (GET)                                 |
| V25N36E     | Set GET. [R1](https://code.google.com/p/virtualagc/source/detail?r=1) for hours, [R2](https://code.google.com/p/virtualagc/source/detail?r=2) for minutes and [R3](https://code.google.com/p/virtualagc/source/detail?r=3) for 1/100 of seconds |
| V01N02E     | Single shot peek at erasable memory address [R3](https://code.google.com/p/virtualagc/source/detail?r=3) in octal |
| V21N02E     | Poke value [R2](https://code.google.com/p/virtualagc/source/detail?r=2) into erasable memory address [R3](https://code.google.com/p/virtualagc/source/detail?r=3) in octal |
| V11N02E     | Continuous peek at erasable memory address [R3](https://code.google.com/p/virtualagc/source/detail?r=3) in octal |
| V05N09E     | Display Alarm Code |
| V05N08E     | Display Alarm Data |
| V37E00E     | Enter Idle program mode |

back to top

Software Heritage — Copyright (C) 2015–2025, The Software Heritage developers. License: GNU AGPLv3+.
The source code of Software Heritage itself is available on our development forge.
The source code files archived by Software Heritage are available under their own copyright and licenses.
Terms of use: Archive access, API— Content policy— Contact— JavaScript license information— Web API