├── README.DOC ├── README.md ├── SPOC-test.vbox ├── nasa-spoc.img └── spoc-fs ├── 4201.CPI ├── 5202.CPI ├── ANSI.SYS ├── APPEND.EXE ├── ASSIGN.COM ├── ATTRIB.EXE ├── BACKUP.COM ├── CHKDSK.COM ├── COMMAND.COM ├── COMP.COM ├── COUNTRY.SYS ├── DATACOPY.EXE ├── DEBUG.COM ├── DISKCOMP.COM ├── DISKCOPY.COM ├── DISPLAY.SYS ├── DRIVER.SYS ├── EDLIN.COM ├── EGA.CPI ├── EXE2BIN.EXE ├── FASTOPEN.EXE ├── FC.EXE ├── FDISK.COM ├── FIND.EXE ├── FORMAT.COM ├── GRAFTABL.COM ├── GRAPHICS.COM ├── GRID.EXE ├── GWBASIC.EXE ├── IO.SYS ├── JOIN.EXE ├── KEYB.COM ├── KEYBOARD.SYS ├── LABEL.COM ├── LINK.EXE ├── MCONFIG.COM ├── MODE.COM ├── MORE.COM ├── MSDOS.SYS ├── NLSFUNC.EXE ├── PRINT.COM ├── PRINTER.SYS ├── PROGRAMS ├── AEROH.TXT ├── AEROL.TXT ├── BKGROUND.RUN ├── CARGO.TXT ├── COMMON.SHR ├── CONSUM.TXT ├── CSITES.TXT ├── DAYMAP.RUN ├── EMULATOR.SHR ├── ESITES.TXT ├── GEXEC.RUN ├── LFORM.RUN ├── LSITES.TXT ├── LTIME.TXT ├── MAPINTEG.MAP ├── MET.RUN ├── PROP.TXT ├── PSAT.RUN ├── README.DOC ├── RNP.TXT ├── SCRINIT.SCR ├── SETTIME.RUN ├── SITEMGR.RUN ├── SPOC.RUN ├── SPOC_UP.DOC ├── STVEC.TXT ├── TG6X8.TYP ├── USER.PRO ├── VECFORM.RUN └── VEHWGHT.TXT ├── PROTO.SYS ├── RAMDRIVE.SYS ├── READPORT.COM ├── REBOOT.COM ├── RECOVER.COM ├── REPLACE.EXE ├── RESTORE.COM ├── SELECT.COM ├── SETCMOS.COM ├── SETPORT.COM ├── SETSPD.COM ├── SETUP.COM ├── SHARE.EXE ├── SORT.EXE ├── SUBST.EXE ├── SYS.COM ├── TREE.COM ├── UPDCFG.COM ├── XCOPY.EXE └── autoexec.BAT /README.DOC: -------------------------------------------------------------------------------- 1 | Shuttle Portable Computer Flight Procedures Handbook 2 | 3 | This is an edited version of the official Shuttle Portable Computer (SPoC) 4 | Flight Procedures Handbook. This document applies only to the version of 5 | SPoC available through NASA Spacelink. 6 | 7 | Orbital state vectors required for this program are available for each 8 | Shuttle mission from NASA Spacelink (Data line 205/895-0028). Use the 9 | "M50 Elements" figures. And remember that SPoC requires figures 10 | in thousands of feet. The M50 elements on NASA Spacelink are often 11 | given in feet. Don't forget to move the decimal three places to the 12 | left before entering the figures into SPoC. 13 | 14 | The following hardware is required for proper operation of this program: 15 | 16 | IBM PC or compatible with math co-processor installed 17 | Hard Drive at location C: 18 | Minimum 512K available memory NOTE: If you are running software 19 | (network software for example) that occupies enough memory to 20 | leave less than 512K for SPoC, SPoC will very likely crash. 21 | 22 | GRID.EXE, SPOC.BAT, and the PROGRAMS subdirectory, must be located in the 23 | Drive C: ROOT directory. 24 | 25 | To run the SPoC software type SPoC at the C> prompt. 26 | 27 | NOTE: The CODE key referred to in this document is the ALT key on IBM PC 28 | compatible computers. 29 | 30 | NOTE: As you will read in the following document, SPoC was written to 31 | run on a GRID computer--not an IBM-PC. Before making SPoC available 32 | through NASA Spacelink, we tested it on a variety of IBM-PC and 33 | compatible computer configurations with mixed results. For example, 34 | SPoC seemed to run properly on one computer, but its VGA display 35 | scrambled the screen making the program unreadable. Other VGA 36 | displays gave no problems. So if SPoC doesn't run on your 37 | particular setup, try it on another computer. 38 | 39 | 40 | 41 | 42 | 43 | SHUTTLE PORTABLE COMPUTER (SPoC) 44 | 45 | FLIGHT PROCEDURES HANDBOOK 46 | 47 | 48 | NATIONAL AERONAUTICS AND SPACE ADMINISTRATION 49 | LYNDON B. JOHNSON SPACE CENTER 50 | HOUSTON, TEXAS 51 | 52 | 53 | 54 | 55 | TABLE OF CONTENTS 56 | 57 | SECTION TITLE 58 | 59 | 1.0 INTRODUCTION 60 | 1.1 SPoC Mission Definition 61 | 1.2 How To Use This Handbook 62 | 63 | 2.0 HARDWARE 64 | 65 | 3.0 SPoC USER INTERFACE 66 | 3.1 Modifier and Command Keys 67 | 3.2 Special Key Combinations 68 | 3.3 The Selection Box 69 | 3.4 SPoC Menus 70 | 3.5 SPoC Forms 71 | 3.6 Messages 72 | 73 | 4.0 OVERVIEW OF SPoC PROGRAMS 74 | 75 | 5.0 BOOT UP SCREEN 76 | 77 | 6.0 LAUNCH TIME UPDATE 78 | 79 | 7.0 GMT UPDATE 80 | 81 | 8.0 STATE VECTOR UPDATE 82 | 83 | 9.0 SPoC MAIN MENU 84 | 85 | 10.0 WORLD MAP 86 | 10.1 World Map Help Menu 87 | 10.2 World Map Display 88 | 10.2.1 Current MET 89 | 10.2.2 AOS/LOS of TDRS Coverage 90 | 10.2.3 AOS/LOS of Ground Communication Site 91 | 10.2.4 Spacecraft Sunrise, Noon, Sunset 92 | 10.2.5 TDRS Coverage 93 | 10.2.6 Earth Day/Night 94 | 10.2.7 Earth Observation Area 95 | 10.2.8 Ground Communication Sites 96 | 10.2.9 Shuttle Bug 97 | 10.2.10 Enlarged F-Stop Display 98 | 10.2.11 Current and Two Predicted Ground Tracks 99 | 10.2.12 Tone Indicator 100 | 10.2.13 Latitude, Longitude and Current F-Stop 101 | 10.2.14 Ascending Node Time 102 | 10.2.15 Earth Observation Site 103 | 10.2.16 Longitude, MET, and Countdown Timer For Next Ascending Node 104 | 10.2.17 Longitude, MET, and Time Since Previous Ascending Node 105 | 10.2.18 Sun Glint Angle and Azimuth 106 | 10.2.19 Sun Glintpoint Area 107 | 10.3 PSAT 108 | 10.4 SITE MANAGER 109 | 10.4.1 SITE MANAGER Exit Options 110 | 10.4.1.1 CODE-D INVOKE DEFAULT COMMUNICATION SITES 111 | 10.4.1.2 CODE-S SAVE CHANGES PROCEED TO DAYMAP 112 | 10.4.1.3 CODE-ESC NO CHANGES PROCEED TO DAYMAP 113 | 10.4.2 SITE MANAGER Functions 114 | 10.4.2.1 CODE-N SELECT COMMUNICATION NETWORK 115 | 10.4.2.2 CODE-I SELECT INDIVIDUAL COMMUNICATION SITES 116 | 10.4.2.3 CODE-P ADD COMMUNICATION SITE 117 | 10.4.2.3.1 Adding a Ground Communications Site 118 | 10.4.2.3.2 Adding a TDRS 119 | 10.4.2.3.3 Editing User Input Ground Site Data 120 | 10.4.2.3.4 Editing User Input TDRS Data 121 | 10.4.2.4 CODE-X DELETE COMMUNICATION SITES 122 | 10.4.2.5 CODE-CTRL-SHIFT-P ADD EARTH OBSERVATION SITE 123 | 10.4.2.5.1 Adding An Earth Observation Site 124 | 10.4.2.5.2 Editing User Input Earth Observation Site Data 125 | 10.4.2.6 CODE-CTRL-SHIFT-X DELETE EARTH OBSERVATION SITES 126 | 127 | 128 | 129 | APPENDIX TITLE 130 | 131 | A INITIALIZING THE SPoC 132 | B WORLD MAP DEMONSTRATION 133 | E SPoC HISTORY 134 | F GLOSSARY 135 | 136 | 137 | 138 | 139 | SECTION 1.0 INTRODUCTION 140 | 141 | The concept of an independent computational capability aboard the Shuttle 142 | has been operational since STS-1. Originally the HP41 hand-held 143 | calculator was employed for this purpose, but it has significant 144 | limitations. The SPoC greatly augments HP41 capabilities. STS-9 was the 145 | first Shuttle mission manifested with a SPoC, and it proved to be such an 146 | asset for the crew that a SPoC has been manifested on every subsequent 147 | Shuttle mission. In its original role it was used as a situational 148 | awareness aid, depicting the Orbiter and its ground track over the earth's 149 | surface. The SPoC has evolved to provide a backup alternative means of 150 | obtaining landing opportunities, deorbit targets, and center of gravity 151 | management procedures. These targets and procedures are only utilized in 152 | the event of a total loss of communications with the ground or a time 153 | critical systems failure during a loss of communication period requiring 154 | an emergency deorbit before ground assistance can be provided. Nominally, 155 | the SPoC is unstowed and set up during the post insertion time frame and 156 | remains active until entry interface minus 20 minutes. 157 | 158 | The SPoC saves Mission Control Center (MCC) personnel time and resources 159 | by eliminating need to routinely transmit such data as Aquisition of 160 | Signal/Loss of Signal (AOS/LOS) times via voice or teleprinter. During 161 | the mission, the Flight Dynamics Officer (FDO) will take SPoC system 162 | questions in the MCC Mission Operations Control Room (MOCR) and pass them 163 | to the SPoC Team if necessary. 164 | 165 | 166 | 1.1 SPoC Mission Definition 167 | 168 | The SPoC is a portable "lap top" microcomputer providing the crew and 169 | mission operations personnel with an independent computational and display 170 | facility, enhancing productivity and reliability. This microcomputer is 171 | mandatory for flight because of the crew support it provides. The SPoC 172 | was designated as noncritical hardware by Configuration Control Board 173 | Directive 1253 in 1983. This classification was reaffirmed in 1987 by 174 | On-Orbit Flight Techniques Panel Meeting #82 [ref. NASA memo DA8-88-04 175 | (FT)]. Currently, there are four major roles for the SPoC. 176 | 177 | a) Provide automated cues for such events as upcoming ground communication 178 | times, earth observation site availability, sunrise and sunset times, 179 | nodal crossings, orbiter ground track, and location over the earth's 180 | surface. 181 | 182 | b) Provide a backup alternative means of obtaining landing opportunities, 183 | deorbit targets, and center of gravity management procedures in the event 184 | of a total loss of communications with the ground or a time-critical 185 | systems failure during a loss of communication period requiring an 186 | emergency deorbit before ground assistance can be provided. 187 | 188 | c) Provide computational and display support for special purpose 189 | applications on a flight-specific basis (e.g. the Orbit Refueling System 190 | {ORS} and the Gravity Gradient Free Drift programs). 191 | 192 | d) Provide mission status and contingency deorbit support in the Emergency 193 | Mission Control Center (EMCC). 194 | 195 | 196 | 1.2 How To Use This Handbook 197 | 198 | This handbook relates procedures and concepts associated with SPoC 199 | operation. Acronyms and other terms pertinent to this discussion, but 200 | whose definitions may not be apparent from context, are defined in 201 | APPENDIX F (GLOSSARY). As a convention, the names of SPoC applications 202 | will be in capitals. A brief history of the SPoC is presented in Appendix 203 | E. 204 | 205 | If you are interested in operating SPoC immediately, proceed to 206 | Appendix A, INITIALIZING THE SPoC, for your first SPoC session. 207 | Appendices A through D are designed to provide an introductory overview 208 | without exercising all SPoC capabilities. For the location of complete 209 | and detailed information, consult the Table of Contents. 210 | 211 | 212 | 213 | SECTION 2.0 HARDWARE 214 | 215 | The SPoC has 384k bytes of nonvolatile bubble memory for use in storing 216 | programs and data. Four Erasable Programmable Read Only Memory (EPROM) 217 | slots, located above the keyboard, are user-accessible. Each SPoC EPROM 218 | has a 64k byte capacity, providing 256k bytes of Read Only Memory (ROM). 219 | The SPoC directly accesses 512k bytes of Random Access Memory (RAM). The 220 | foldup display is a high resolution electroluminescent flat panel which 221 | measures 7-and-9/16 by 3-and-3/4 inches (512 pixels by 256 scanlines). 222 | 223 | There are four types of keys on the SPoC: alphabetic/numeric keys, 224 | modifier keys for issuing commands, arrow keys for positioning the cursor, 225 | and a return key for selection box control. The memory, display, and 226 | 57-character keyboard are in a magnesium case, which together weighs 227 | approximately 10 pounds. The unit will fit into one-half of a standard 228 | size briefcase. 229 | 230 | SPoC is hosted on a GRiD Compass computer purchased off-the-shelf and 231 | modified for flight. A standard lithium battery circuit that provides 232 | power for the internal clock is replaced by a silver oxide battery and 233 | equipped with diodes and a fuse to ensure fail-safe operation. The 234 | internal modem is removed. Flight displays are fitted with 235 | electromagnetic interference filters. This prevents electromagnetic 236 | interference generated by the electroluminescent display from harming the 237 | General Purpose Computers (GPCs) or other equipment onboard. When used 238 | onboard the Shuttle, SPoC runs on phase A ac power and uses a power cable 239 | which is compatible with the Orbiter's power outlets. Finally, the foot 240 | of a flight SPoC is milled to permit fan exhaust flow when folded up for 241 | flight operation. 242 | 243 | 244 | SECTION 3.0 SPoC USER INTERFACE 245 | 246 | SPoC applications have been designed for similarity in appearance and 247 | operation. Utilization of menus and forms allows the user to select, 248 | input, edit, and execute without unnecessary typing. Menus permit the 249 | user to select a single item for execution, while forms permit the user to 250 | input several data values on one display. Prompts appear at the bottom of 251 | the screen, as an aid to the user. When appropriate, error messages also 252 | appear at the bottom of the screen instructing the user how to correct 253 | erroneous inputs. 254 | 255 | NOTE: Messages are displayed on the screen in inverse video. In this 256 | document, messages displayed on screen images will appear as black 257 | characters against a white background. This is done for readability. 258 | 259 | 260 | "3.1 Modifier and Command Keys" 261 | 262 | Modifier keys include the "CODE" keys, "SHIFT" keys, and the "CONTROL" 263 | key. The "CODE" keys and "SHIFT" keys are located at the lower left and 264 | lower right of the keyboard. The "CONTROL" key is located at the lower 265 | left corner of the keyboard. The "RETURN" key, "ESCAPE" key, and any 266 | other keys that invoke a menu option are command keys. The most often 267 | used modifier keys are the "CODE" keys. To execute any menu option or to 268 | accept the settings in a form, the user must hold down a modifier key(s) 269 | and then press the appropriate command key. 270 | 271 | "CAUTION": SPoC EXPECTS THE COMMAND KEY "PRESS" ACTION TO BE BRIEF (NO 272 | MORE THAN 0.2 SECONDS). Pressing a command key for finite intervals may 273 | issue multiple instructions with unpredictable results. 274 | 275 | 276 | "3.2 Special Key Combinations" 277 | 278 | Throughout the remainder of this handbook, the following convention will 279 | be followed. "CODE-[key]" will indicate that the "CODE" key is held down 280 | until the "[key]" is pressed. As an example, "CODE-RETURN" indicates that 281 | the user holds down the "CODE" key until the "RETURN" key is pressed. 282 | "CODE-ESCAPE" indicates that the "CODE" key is held down until the 283 | "ESCAPE" key is pressed. "CODE-M" indicates that the "CODE" key is held 284 | down until ""M"" is pressed. "CODE-CTRL-SHIFT-N" indicates that the 285 | "CODE" key and the "CTRL" key are held down until ""N"" is pressed. A 286 | menu item will be executed or form settings will be accepted only if a 287 | "CODE-[key]" combination is pressed. The "CODE-RETURN" combination 288 | executes the menu option selected or accepts the form settings selected. 289 | The "CODE-ESCAPE" combination has a special function. To exit a menu 290 | without executing any of the displayed options or to exit a form without 291 | modifying the form settings, press "CODE-ESCAPE". If the user presses 292 | "CODE-ESCAPE", program control returns to the previously displayed screen. 293 | If "CODE-ESCAPE" is pressed at the main menu of a program, the program is 294 | exited and control returns to the SPoC Main Menu, which displays the 295 | available applications. A "CODE-ESC" from the SPoC Main Menu is ignored. 296 | 297 | 298 | "3.3 The Selection Box" 299 | 300 | The selection box is a moving rectangular outline that encloses the 301 | current option or setting. In a menu, the selection box identifies the 302 | option that will be executed when the user presses "CODE-RETURN". In a 303 | form, the selection box identifies data currently being modified. 304 | Movement of the selection box is controlled by the "RETURN" key. Each 305 | time the "RETURN" key is pressed, the selection box advances to the next 306 | option. If the "RETURN" key is pressed while the selection box is located 307 | on the last option of the menu, the selection box will advance to the 308 | first option on the menu. 309 | 310 | If the menu in receives a "CODE-RETURN" with the selection box located on 311 | the first option, the WORLD MAP application will be executed. Press the 312 | "RETURN" key once, and the selection box advances to the next option. 313 | 314 | If the menu receives a "CODE-RETURN" with the selection box located on the 315 | second option, STATE VECTOR UPDATE will be executed. 316 | 317 | "3.4 SPoC Menus" 318 | 319 | SPoC menus permit the user to select one option to be executed with a 320 | minimum of keystrokes. To select an option, press the "RETURN" key 321 | repeatedly until the selection box is located on the option to be 322 | executed. Press "CODE-RETURN" to execute the option. There is an 323 | alternate method of selecting and executing an option from a menu. Press 324 | "CODE-[key]", where "[key]" is the designated letter for the option to be 325 | executed. Using the SPoC Main Menu as an example, DEORBIT can be selected 326 | by pressing the "RETURN" key three times to locate the selection box on 327 | the menu option DEORBIT. DEORBIT is then executed by pressing 328 | "CODE-RETURN". Using the alternate method, DEORBIT can be selected and 329 | executed by pressing "CODE-D" regardless of where the selection box is 330 | currently located. 331 | 332 | 333 | "3.5 SPoC Forms" 334 | 335 | SPoC forms permit the user to enter or edit data for one or more items. 336 | Forms are different from menus for these reasons: 337 | 338 | a) Forms let users change the settings of several items. Menus let users 339 | select only one option. 340 | 341 | b) Users may input their own settings to forms. Many forms do not limit 342 | users 343 | to predefined choices. 344 | 345 | c) When users press "CODE-RETURN", they accept the settings of all form 346 | items, 347 | not just the outlined setting. 348 | 349 | A form consists of the following components. 350 | 351 | "Items": labels which identify data to be modified. Each item has a 352 | setting associated with it. 353 | 354 | "Settings": actual values the user has typed, chosen from the choice band, 355 | or received by default. These settings are either choice or editable 356 | fields, depending on the application. 357 | 358 | "Selection box": moving indicator that surrounds the setting currently 359 | being modified. "RETURN" moves it down and "SHIFT-UPARROW" moves it up. 360 | 361 | "Choice band": located at the top of the form, it may be configured in one 362 | of three ways. If there are choices for the current item, the choices are 363 | displayed there. If the item is an editable item, the choice band may be 364 | blank or contain pertinent information with the edit prompt. 365 | 366 | "Choices": predefined values for a setting, which appear in the choice 367 | band. The highlighted choice appears within the selection box 368 | automatically. 369 | 370 | "Highlighted box": indicates the choice that appears in the selection box, 371 | when choices are available. Pressing the arrow keys moves the highlighted 372 | box among choices. Horizontally grouped choices utilize the "LEFTARROW" 373 | and "RIGHTARROW" keys for movement, while vertically grouped choices are 374 | selected with the "UPARROW" and "DOWNARROW" keys. If the item is an 375 | editable item, the highlighted box, if displayed, will contain pertinent 376 | information and the edit prompt. 377 | 378 | A setting is editable if there are no choices listed in the choice band. 379 | In this case, the edit prompt appears in the selection box as a small 380 | flashing triangular field. A setting is a choice setting if there are 381 | choices listed in the choice band. 382 | 383 | To change data for an editable setting, use the "LEFTARROW" and 384 | "RIGHTARROW" keys to locate the flashing edit prompt. The following 385 | actions are possible on all data left of the prompt. 386 | 387 | 1) Press the "BACK SPACE" key to erase the rightmost character of data. 388 | 2) Press "CODE-BACK SPACE" to erase the rightmost word of data. 389 | 3) Press "CODE-SHIFT-BACK SPACE" to erase all data. 390 | 391 | Data may be inserted right of the flashing prompt by pressing the 392 | appropriate keys. Once satisfied with the settings, press "CODE-RETURN" 393 | to incorporate all settings and proceed to the next form or menu. To exit 394 | a form without accepting any new settings, press "CODE-ESC". Upon 395 | pressing "CODE-ESC", the former item settings are restored and the 396 | previous form or menu will be displayed. 397 | 398 | 399 | "3.6 Messages" 400 | 401 | There are three types of SPoC messages. 402 | 403 | 1) Prompts 404 | 2) Error messages 405 | 3) Informative messages 406 | 407 | As an aid to the user, each SPoC menu or form has prompts displayed at the 408 | bottom of the screen. Information provided by prompts will inform the 409 | user what action should be taken next. 410 | 411 | Error messages provide information for correcting erroneous user inputs. 412 | 413 | Informative messages provide status on what action is currently being 414 | taken. Informative messages require no user action. 415 | 416 | 417 | 418 | 419 | SECTION 4.0 OVERVIEW OF SPoC PROGRAMS 420 | 421 | In this section, a high level overview of SPoC software will be presented. 422 | There are five operating modes for SPoC software: InFlight, Debug, 423 | Development, SmartDemo, and DummyDemo. 424 | 425 | This document pertains only to the InFlight mode. 426 | 427 | 428 | "LAUNCH TIME UPDATE" 429 | 430 | During SPoC initialization, the actual launch Greenwich Mean Time (GMT) 431 | can be input to update the launch time expected premission. The launch 432 | time is stored in bubble memory and used to compute Mission Elapsed Time 433 | (MET). 434 | 435 | 436 | "GMT UPDATE" 437 | 438 | Current GMT can be updated in SPoC's internal clock. The internal clock 439 | is maintained by an internal battery during periods when SPoC power is 440 | OFF. 441 | 442 | 443 | "STATE VECTOR UPDATE" 444 | 445 | This program allows the user to input position and velocity vectors in the 446 | Mean of 50 (M50) coordinate system. These vectors are obtained from the 447 | GPC Memory Page and are written to bubble memory for access by other 448 | programs. 449 | 450 | 451 | "SPoC EXECUTIVE" 452 | 453 | The SPoC EXECUTIVE program displays the SPoC Main Menu from which the user 454 | may select the application desired. Upon exiting any program selected 455 | from the SPoC Main Menu, program control returns to the SPoC Main Menu. 456 | 457 | 458 | "WORLD MAP" 459 | 460 | The SPoC presently runs WORLD MAP as its primary program. A graphics 461 | display of a world map is overlaid by the Orbiter's current trajectory 462 | status. The following information/functions are available. 463 | 464 | Current MET 465 | Fixed coastline and Spaceflight Tracking and Data Network (STDN)/ 466 | Tracking and Data Relay Satellite (TDRS) coverage graphics 467 | Day and night areas on the earth's surface 468 | AOS/LOS and identification of next/current ground communication site 469 | AOS/LOS and identification of next/current TDRS coverage 470 | Current and two predicted ground tracks 471 | Current position of the Orbiter on the world map 472 | AOS of the next earth observation site 473 | AOS of future earth observation sites 474 | Current F-stop 475 | F-stop for the selected earth observation site 476 | Predicted Site Acquisition Table (PSAT) Display 477 | Table of TDRSS AOS/LOS 478 | Communication/Earth Observation site reconfiguration 479 | Latitude and longitude of the Orbiter 480 | Time to Orbiter sunrise, noon, or sunset 481 | Sun glint position on the world map 482 | Sun glint look angles 483 | Longitude and MET of the next/previous ascending node 484 | Time until/from the next/previous ascending node 485 | 486 | SECTION 5.0 BOOT UP SCREEN 487 | 488 | When SPoC is turned ON, the Boot Up Screen is displayed after several 489 | seconds. At the bottom center of this screen will be displayed the 490 | message: 491 | 492 | Boot in Progress 493 | Please Wait 494 | 495 | The contents of the rest of the screen will indicate: 496 | 497 | 1) Specific or Generic Flight Load 498 | 2) Flight or Training Load 499 | 3) Version Number 500 | 501 | After the operating system has been loaded, the Boot Up Screen will be 502 | erased. The following message will be displayed at the bottom of the 503 | screen while SPoC EXECUTIVE searches for the necessary applications. 504 | 505 | "Searching for all the necessary SPoC programs" 506 | 507 | Next, SPoC EXECUTIVE will search for necessary data files. The following 508 | message will be displayed. 509 | 510 | 511 | "Searching for all the necessary SPoC data files" 512 | 513 | 514 | Upon completion of the data file search, the LAUNCH TIME UPDATE form will 515 | be displayed. If this form does not appear, a fatal error has been 516 | detected in the current SPoC software configuration by SPoC EXECUTIVE. 517 | 518 | 519 | 520 | 521 | SECTION 6.0 LAUNCH TIME UPDATE 522 | 523 | This program allows the user to update the GMT of launch. Upon completion 524 | of the boot cycle, the LAUNCH TIME UPDATE form (FIGURE 6.1) is displayed. 525 | Initial settings displayed indicate nominal launch time. These settings 526 | can be updated by the user in the event of a launch delay. 527 | 528 | If the launch form settings are correct, press "CODE-RETURN". Otherwise, 529 | correct any erroneous data. 530 | 531 | Acceptable inputs for LAUNCH TIME UPDATE FORM: 532 | YEAR - 1983 through 1999 533 | DAY - 1 through 365 in common years, 1 through 366 in leap years 534 | HOUR - 0 through 23 535 | MINUTE - 0 through 59 536 | SECOND - 0 through 59 537 | 538 | Possible Error Messages: 539 | 1) "ERROR: Time parameter(s) input incorrectly" 540 | 541 | Problem: One or more of the settings are not within acceptable limits 542 | or are not formatted as integers. 543 | 544 | Solution: The symbol "->" will appear next to out-of-range or 545 | improperly formatted settings. Replace erroneous data with good data. 546 | 547 | 548 | 549 | 550 | SECTION 7.0 GMT UPDATE 551 | 552 | 553 | After pressing "CODE-RETURN" from the LAUNCH TIME UPDATE form, the GMT 554 | UPDATE form will automatically appear. This form can also be accessed 555 | from the SPoC Main Menu. The time displayed in this form is used to set 556 | the internal SPoC clock when "CODE-RETURN" is pressed. The GMT will have 557 | to be updated to correct internal clock drift. SPoC clock drift will 558 | average approximately five seconds per day. 559 | 560 | Acceptable inputs for GMT UPDATE form: 561 | DAY - 1 through 365 in common years, 1 through 366 in leap years 562 | HOUR - 1 through 23 563 | MINUTE - 1 through 59 564 | YEAR - 1980 through 1999 565 | 566 | Possible Error Messages: 567 | 1) "ERROR: Time parameter( s ) input incorrectly" 568 | 569 | Problem: The settings for the items listed in the error message are not 570 | within acceptable limits. 571 | 572 | Solution: The symbol "->" will appear next to out-of-range settings. 573 | Replace data that are not within acceptable limits. 574 | 575 | Possible Caution Messages: 576 | 1) "CAUTION: Vector more than 2 days old" 577 | 578 | Problem: SPoC GMT and the current SPoC state vector time tag are 579 | incompatible. The state vector time tag is two days older than 580 | current SPoC GMT. 581 | 582 | Solution: If GMT settings are incorrect, press "CODE-ESC" to 583 | reinitialize the form. Correct erroneous data. 584 | 585 | If GMT settings are correct, press "CODE-RETURN". The state 586 | vector time tag settings can be updated in the STATE VECTOR UPDATE 587 | form. 588 | 589 | 2) "CAUTION: Vector is in the future" 590 | 591 | Problem: SPoC GMT and the current SPoC state vector time tag are 592 | incompatible. The time tag for the current SPoC state vector is 593 | in the future. 594 | 595 | Solution: If GMT settings are incorrect, press "CODE-ESC" to 596 | reinitialize the form. Correct erroneous data. 597 | 598 | If GMT settings are correct, press "CODE-RETURN". The state 599 | vector time tag settings can be updated in the STATE VECTOR UPDATE 600 | form. 601 | 602 | 603 | 604 | SECTION 8.0 STATE VECTOR UPDATE 605 | 606 | The STATE VECTOR UPDATE form allows users to update the SPoC state vector. 607 | This form will automatically appear after pressing "CODE-RETURN" from the 608 | GMT UPDATE form during the SPoC initialization sequence. STATE VECTOR 609 | UPDATE can also be accessed from the SPoC Main Menu. 610 | 611 | Components of the previously input time tag and state vector are initially 612 | displayed in the STATE VECTOR UPDATE form. Prelaunch, a predicted nominal 613 | post-OMS-2 state vector is loaded into the SPoC. 614 | 615 | In OPS 2, components of the current state vector are provided by the GPCs 616 | using the GNC SPEC 34 Orbit Targeting display. Remember, values displayed 617 | on the CRT are continuously updated. Press SPEC to freeze the display. 618 | The time tag, along with position and velocity components, can now be 619 | entered into the SPoC STATE VECTOR UPDATE form. 620 | 621 | In OPS 3, components of the current state vector are provided by the GPCs 622 | using the GNC SPEC 0 GPC Memory display. SPEC 0 item entries are listed 623 | in the Reference Data Book Flight Supplement. After the six state vector 624 | components have been requested and displayed, press SPEC to freeze the 625 | display. The time tag, along with position and velocity components, can 626 | now be entered into the SPoC STATE VECTOR UPDATE form. Note: The GPC time 627 | tag displayed with the state vector may have up to a 1.8 second delta from 628 | the state vector's true time tag. This is due to differing update rates 629 | for these quantities on the GPC Memory display. 630 | 631 | When settings in the form reflect the frozen SPEC 34 (SPEC 0 in OPS 3), 632 | press "CODE-RETURN". The inclination, HA, and HP are displayed. This 633 | serves as a data check for state vector inputs. If values displayed are 634 | reasonable, press "CODE-RETURN" and the Main Menu will be displayed. 635 | 636 | If values are not reasonable, press "CODE-ESC" and the STATE VECTOR UPDATE 637 | form will be reinitialized. Correct any erroneous state vector settings 638 | and press "CODE-RETURN". Again the inclination, HA, and HP will be 639 | displayed. If the values displayed are reasonable, press "CODE-RETURN". 640 | Otherwise, press "CODE-ESC" to reinitialize the form. 641 | 642 | Acceptable inputs for STATE VECTOR UPDATE time tag: 643 | DAY (GMT) - 1 through 366 644 | HOUR (GMT) - 0 through 23 645 | MINUTE (GMT) - 0 through 59 646 | SECOND (GMT) - 0 through 59 647 | 648 | Possible error messages: 649 | 650 | 651 | 1) "ERROR: Time parameter( s ) input incorrectly" 652 | 653 | Problem: Settings for the GMT items listed in the error message are not 654 | within acceptable limits or are not formatted as integers. 655 | 656 | Solution: The symbol "->" will appear next to out-of-range settings. 657 | Replace data that are not within acceptable limits. 658 | 659 | Possible caution messages: 660 | 661 | 1) "CAUTION: VECTOR MORE THAN 2 DAYS OLD" 662 | 663 | Problem: The SPoC GMT and the current SPoC state vector time tag are 664 | incompatible. The time tag is more than two days old 665 | based on the current SPoC MET. 666 | 667 | Solution: If the state vector time tag settings are incorrect, press 668 | "CODE-ESC" to reinitialize the form. Correct erroneous data. 669 | 670 | If the state vector time tag settings are correct, press 671 | "CODE-RETURN". GMT settings can be updated in the GMT UPDATE 672 | form. 673 | 674 | 2) "VECTOR IS IN THE FUTURE" 675 | 676 | Problem: The SPoC GMT and the current SPoC state vector time tag are 677 | incompatible. The time tag is in the future based on 678 | the current SPoC MET. 679 | 680 | Solution: If the state vector time tag settings are incorrect, press 681 | "CODE-ESC" to reinitialize the form. Correct erroneous data. 682 | 683 | If the state vector time tag settings are correct, press 684 | "CODE-RETURN". GMT settings can be updated in the GMT UPDATE 685 | form. 686 | 687 | 688 | 689 | 690 | SECTION 9.0 SPoC MAIN MENU 691 | 692 | The Main Menu allows users to invoke SPoC applications. After the SPoC 693 | initialization sequence has been completed, the SPoC Main Menu will be 694 | displayed. This menu will also be displayed upon exiting any SPoC 695 | application. 696 | 697 | Once the user has executed a menu option to select an application, status 698 | messages will appear at the bottom of the screen. These messages provide 699 | status on files being loaded or any processing in progress. 700 | 701 | Possible error message: 702 | 703 | "STATE VECTOR TIME IS INCOMPATIBLE WITH GMT" 704 | 705 | Problem: SPoC current MET and the SPoC state vector MET time tag are 706 | incompatible. The time tag for the current SPoC state vector is 707 | either in the future, or two days older than the current SPoC MET. 708 | 709 | Solution: 710 | A) Press any key and return to the SPoC Main Menu. 711 | B) If the displayed MET is correct, select STATE VECTOR UPDATE 712 | from the SPoC Main Menu. Otherwise, proceed to Step D. 713 | C) Verify that state vector time tag settings are correct. 714 | 1) If time tag settings are incorrect, correct erroneous 715 | settings, press "CODE-RETURN", and return to the SPoC Main 716 | Menu. 717 | 2) If time tag settings are correct, press "CODE-ESC" to 718 | return to the SPoC Main Menu without changing form 719 | settings. 720 | 3) Proceed to Step F. 721 | D) Select SET GMT from the Main Menu. 722 | E) Verify that GMT settings are correct. 723 | 1) If GMT settings are incorrect, correct erroneous 724 | settings and return to the SPoC Main Menu. 725 | 2) If GMT settings are correct, press "CODE-ESC" to return 726 | to the SPoC Main Menu. 727 | F) Make selection from the Main Menu. 728 | 729 | SECTION 10.0 WORLD MAP 730 | 731 | 732 | SITE MANAGER Main Menu 733 | 734 | The first time WORLD MAP is selected from the SPoC Main Menu, the SITE 735 | MANAGER Main Menu will be displayed. SITE MANAGER is a WORLD MAP function 736 | which will be detailed in Section 10.4. For now, execute the first menu 737 | item "INVOKE DEFAULT COMMUNICATION SITES" and proceed to the WORLD MAP 738 | display. 739 | 740 | 741 | WORLD MAP serves as a crew aid which provides a situation display, various 742 | timers, and tables. The situation display includes a map with a longitude 743 | range from 180 degrees West to 180 degrees East, and a typical latitude 744 | range from 65 degrees North to 65 degrees South. A map with any valid 745 | latitude range can be provided by the SPoC Team upon request. 746 | 747 | 748 | 10.1 World Map Help Menu 749 | 750 | The WORLD MAP Help Menu may be invoked by pressing "CODE-?" with the WORLD 751 | MAP display active. This menu provides the "CODE-[key]" combinations 752 | associated with each WORLD MAP function. WORLD MAP functions may be 753 | invoked from the Help Menu, or may be invoked from the WORLD MAP display 754 | directly with the proper "CODE-[key]" input. To return to the WORLD MAP 755 | Display, press "CODE-ESC". 756 | 757 | 758 | 10.2 World Map Display 759 | 760 | The contents of the WORLD MAP Display are described in detail below. 761 | 762 | Following is a rough drawing of the World Map Display screen. The numbers in 763 | parentheses represent the ITEMS described in the text below. 764 | 765 | +==========================================================+ 766 | | (1) | | (2) | (3) | | (4) | 767 | |----------------------------------------------------------| 768 | | | 769 | | | 770 | | | 771 | | [Picture of earth showing day and night, | 772 | | orbital paths and current location of | 773 | | shuttle, earth-based tracking station | 774 | | locations and coverage areas, earth | 775 | | observation opportunities.] | 776 | | | 777 | | | 778 | | +-----+ | 779 | | | | | 780 | | | (10)| | 781 | |(12) | | | 782 | |----------------------------------------------------------| 783 | | (15) | | (13,16,17,18) | |(14,16,17)| 784 | +==========================================================+ 785 | 786 | 10.2.1 Current MET (Item 1) 787 | 788 | DD/HH:MM:SS fields will update approximately every second and are 789 | displayed continuously. These are calculated based on the current GMT and 790 | the GMT of launch. 791 | 792 | 10.2.2 AOS/LOS of TDRS Coverage (Item 2) 793 | 794 | The ID and countdown time to AOS or LOS of TDRS coverage is displayed in 795 | this window. If multiple satellites have overlapping coverage, the AOS 796 | countdown time to the first TDRS will be displayed. After AOS of the 797 | first TDRS, the ID and LOS of the last TDRS with overlapping coverage is 798 | displayed. "STAND BY" will be displayed in this window until AOS/LOS 799 | times have been calculated. 800 | 801 | 10.2.3 AOS/LOS of Ground Communication Site (Item 3) 802 | 803 | This window displays the ID, radio frequency band(s), and countdown time 804 | to AOS or LOS of a ground communication site. AOS and LOS are defined as 805 | an elevation of the Orbiter, viewed from the ground site, of 0.0 degrees. 806 | Neither terrain masking nor atmospheric refraction are considered in this 807 | calculation. If sites have overlapping coverage, the AOS countdown time 808 | of the first site will be displayed. After AOS of the first site, the ID 809 | and LOS of the last site in this overlapping coverage is displayed. Then 810 | the radio frequency band(s) displayed will be that of the currently 811 | acquisitioned site(s). "STAND BY" will be displayed in this window until 812 | AOS/LOS times have been calculated. 813 | 814 | 10.2.4 Spacecraft Sunrise, Noon, Sunset (Item 4) 815 | 816 | The countdown time to spacecraft sunrise ("SR"), noon ("SN"), or sunset 817 | ("SS") is displayed in this window. If the time to spacecraft 818 | sunrise/sunset or noon is greater than 100 minutes, the timer will 819 | countdown from 99:59 to 99:00 then cycle until 99:59 is the correct time. 820 | Shuttle sunrise and sunset are defined with respect to the upper limb of 821 | the sun with a fixed bias to offset the effects of refraction. Press 822 | "CODE-S" to toggle between spacecraft sunrise/sunset and noon. Spacecraft 823 | sunrise, noon, and sunset functions share this window on a mutually 824 | exclusive basis. 825 | 826 | 10.2.5 TDRS Coverage (Item 5) 827 | 828 | Limits of TDRS coverage are displayed assuming average nominal orbital 829 | altitude for a flight. 830 | 831 | 10.2.6 Earth Day/Night (Item 6) 832 | 833 | The sunlight terminator separates day/night regions on earth's surface and 834 | is updated in real time. The region in daylight is displayed with inverse 835 | video. 836 | 837 | 10.2.7 Earth Observation Area (Item 7) 838 | 839 | The flashing rectangle highlights an earth observation site. The area 840 | approximates extent of the site to be observed. A site is acquired when 841 | any part viewed from the Orbiter is within 40 degrees of the current 842 | nadir. The next available site will initially be displayed. Press 843 | "CODE-F" to move forward one available site at a time until the last 844 | predicted ground track point is encountered. To return to the next 845 | available site, press "CODE-R". The displayed site is shown until 846 | acquired, then the next site is highlighted with a flashing rectangle. 847 | 848 | 10.2.8 Ground Communication Sites (Item 8) 849 | 850 | Limits of selected ground communication sites, with terrain masking, are 851 | displayed assuming average nominal orbital altitude for a flight. 852 | 853 | 10.2.9 Shuttle Bug (Item 9) 854 | 855 | The nose of the flashing Shuttle Bug indicates current position of the 856 | Orbiter. Every thirty seconds, the Shuttle Bug's position is updated to 857 | the next predicted ground track point. 858 | 859 | 10.2.10 Enlarged F-Stop Display (Item 10) 860 | 861 | For ease of viewing, the current camera F-Stop is enlarged and displayed. 862 | This is the same camera F-Stop value described in Item 13. The enlarged 863 | F-Stop display may be toggled ON or OFF by pressing "CODE-CTRL-SHIFT-F". 864 | For high inclination orbits, position of the enlarged F-Stop display will 865 | vary slightly. This is done to avoid display conflicts with predicted 866 | ground tracks and the Shuttle Bug. 867 | 868 | 10.2.11 Current and Two Predicted Ground Tracks (Item 11) 869 | 870 | Predicted ground tracks are updated when the Shuttle Bug reaches the 871 | predicted ground track point 5400 seconds (90 minutes) from the first. 872 | The Shuttle Bug then occupies the first ground track point in a series 873 | extending 4.5 hours into the future. Adjacent ground track points are 874 | separated in time by 30 seconds. 875 | 876 | 10.2.12 Tone Indicator (Item 12) 877 | 878 | "ON" indicates a tone will be generated when the currently displayed earth 879 | observation site countdown timer reaches two minutes. "OFF" indicates no 880 | tone will be generated. The default setting is "ON". The tone indicator 881 | may be toggled "ON" and "OFF" by pressing "CODE-T". 882 | 883 | 10.2.13 Latitude, Longitude, and Current F-Stop (Item 13) 884 | 885 | The Orbiter's current latitude, longitude, and the camera F-Stop required 886 | for an average albedo target at the current spacecraft nadir are updated 887 | once every 30 seconds. "CODE-L" immediately updates this display and 888 | toggles it from dynamic to frozen. While frozen, the display will flash 889 | approximately once/second. This display window is shared, on a mutually 890 | exclusive basis, with items 16, 17, and 18. 891 | 892 | 10.2.14 Ascending Node Time (Item 14) 893 | 894 | This window displays elapsed time since previous ascending node or 895 | countdown to the next ascending node. The display is controlled in 896 | conjunction with items 16 and 17. 897 | 898 | 10.2.15 Earth Observation Site (Item 15) 899 | 900 | The site ID is displayed along with the countdown time to acquisition of 901 | the displayed earth observation site. The program searches for 902 | acquisition only. Once acquisition is achieved, the program will search 903 | for acquisition of the next available site. If no earth observation site 904 | has been found within the predicted ground tracks, "***** XX:XX" will be 905 | displayed. The F-Stop for this site is also displayed. This F-Stop is 906 | based on a predetermined albedo for the current site, a set film and 907 | shutter speed, and the computed sun angle. Since F-Stop values are 908 | computed in discrete 1/2 F-Stop steps, a difference of 1/2 F-Stop between 909 | the SPoC value and a premission value is not unusual. 910 | 911 | SPoC observation site F-Stops are computed for acquisition, but the 912 | premission albedos consider an average across the entire site. For sites 913 | with significant physical size, this can result in F-Stop differences of 914 | as much as 1 and 1/2 to 2 full F-Stops in extreme cases. 915 | 916 | 10.2.16 Longitude, MET, and Countdown Timer For Next Ascending Node (Item 917 | 16) 918 | 919 | A keyboard input of "CODE-N" will display the longitude and MET of the 920 | next ascending node in the bottom center window, replacing any data 921 | previously displayed there. Also the countdown time for this node will be 922 | displayed in the Ascending Node Time window (Item 14). This function 923 | shares the bottom middle window, on a mutually exclusive basis, with Items 924 | 13, 17, and 18. 925 | 926 | 10.2.17 Longitude, MET, and Time Since Previous Ascending Node (Item 17) 927 | 928 | A keyboard input of "CODE-CTRL-SHIFT-N" will display the longitude and MET 929 | of the previous ascending node in the bottom center window, replacing any 930 | data previously displayed there. Elapsed time since the previous 931 | ascending node will also be displayed in the Ascending Node Time window 932 | (Item 14). This function shares the bottom middle window, on a mutually 933 | exclusive basis, with Items 13, 16, and 18. 934 | 935 | 10.2.18 Sun Glint Angle and Azimuth (Item 18) 936 | 937 | A keyboard input of "CODE-G" will display the sun glintpoint 938 | angle-of-reflection and azimuth relative to the Orbiter. These data are 939 | displayed in the bottom center window, replacing any data previously 940 | displayed there. "GLINT ANGL" is the angle-of-reflection of the sun's 941 | image off the Earth's surface. "AZ" is the angle measured from the 942 | vehicle true heading in the Orbiter local horizontal plane to the 943 | glintpoint azimuth and accumulated in the direction "east of north". In 944 | other words, the difference "true azimuth of the sun glintpoint minus 945 | current Orbiter true heading" is "AZ". Sun glint data are displayed only 946 | if the "GLINT ANGL" is between 9.99 degrees and 80.21 degrees. Otherwise, 947 | Xs are displayed in place of the data. This function shares the bottom 948 | middle window, on a mutually exclusive basis, with Items 13, 16, and 17. 949 | 950 | 10.2.19 Sun Glintpoint Area (Item 18a) 951 | 952 | A "CODE-G" keyboard input will also graphically display the sun glintpoint 953 | relative to the Shuttle by flashing a small square on the WORLD MAP. 954 | 955 | 956 | 10.3 PSAT 957 | 958 | A Predicted Site Acquisition Table (PSAT) is available for the current and 959 | two predicted ground tracks. Press "CODE-P" to call up the PSAT Display. 960 | There are two windows for this display. The upper window displays TDRS 961 | data, while the lower window displays ground site data. Each window has a 962 | light bar which serves as an aid for reading data across a row. Press 963 | "UPARROW" and "DOWNARROW" to control light bar movement in the lower 964 | window. Press "SHIFT-UPARROW" and "SHIFT-DOWNARROW" to control light bar 965 | movement in the upper window. 966 | 967 | If there are more lines of data than can be displayed in a PSAT window at 968 | one time, only sites with LOS in the future will be visible when the 969 | display appears. Users may scroll up or down to view data not currently 970 | in the window. Small up/down arrows indicate if more data are available. 971 | Users may scroll in the direction of the arrows to view the additional 972 | data. When the bottom or top of the table is reached, the appropriate 973 | arrow will vanish. 974 | 975 | "More Data Arrows": Indicate that more data are available above or below 976 | those currently visible. 977 | 978 | "LOS Indicators": Indicate the site has an LOS in the past. 979 | 980 | "Light Bar": Visual aid in reading across a row. May be moved with the 981 | arrow keys as described above. 982 | 983 | "XX/XX:XX:XX XX:XX": Indicates the data are not currently available. 984 | 985 | To return to the WORLD MAP Display, press "CODE-ESC" 986 | 987 | 988 | 10.4 SITE MANAGER 989 | 990 | SITE MANAGER allows users to: 991 | 992 | * 1) Turn communication sites ON or OFF. 993 | * 2) Add/edit communications site data. 994 | * 3) Delete user input communications sites. 995 | * 4) Add/edit earth observation site data. 996 | * 5) Delete user input earth observation sites. 997 | 998 | 999 | On the first call to WORLD MAP from the SPoC Main Menu, the SITE MANAGER 1000 | Main Menu will be displayed. During subsequent calls to WORLD MAP, 1001 | control will pass directly to the WORLD MAP Display. SITE MANAGER may 1002 | also be invoked from the WORLD MAP Help Menu or by pressing "CODE-E" from 1003 | the WORLD MAP Display. 1004 | 1005 | The SITE MANAGER Main Menu is displayed on the first call to WORLD MAP as 1006 | a reminder that the previous user may have reconfigured communication or 1007 | earth observation sites. This allows users easy access to verify 1008 | configuration of the sites. 1009 | 1010 | If a communication site is ON, the site will be included in AOS/LOS 1011 | searches. If it is OFF, the site will not be included in AOS/LOS 1012 | searches. The AOS/LOS search drives the WORLD MAP AOS/LOS countdown 1013 | windows and PSAT Display. SPoC premission site data cannot be altered or 1014 | deleted by users. Only user input site data may be altered or deleted by 1015 | users. 1016 | 1017 | 10.4.1 SITE MANAGER Exit Options 1018 | 1019 | Three options on the SITE MANAGER Main Menu will exit SITE MANAGER and 1020 | proceed to the WORLD MAP program. 1021 | 1022 | 10.4.1.1 CODE-D INVOKE DEFAULT COMMUNICATION SITES 1023 | 1024 | The communication site list will revert to the premission default 1025 | configuration. Any user input sites marked for deletion will be deleted. 1026 | All other sites, including user input sites, will be turned OFF. SITE 1027 | MANAGER is exited and the WORLD MAP Display appears. 1028 | 1029 | 10.4.1.2 CODE-S SAVE CHANGES PROCEED TO DAYMAP 1030 | 1031 | Any changes made during this SITE MANAGER session will be saved. User 1032 | input sites marked for deletion will be deleted. SITE MANAGER is exited 1033 | and the WORLD MAP Display appears. 1034 | 1035 | 10.4.1.3 CODE-ESC NO CHANGES PROCEED TO DAYMAP 1036 | 1037 | Any changes made during this SITE MANAGER session will be ignored. SITE 1038 | MANAGER is exited and the WORLD MAP Display appears. "NOTE": If changes 1039 | were made, users will be warned with the following message: 1040 | 1041 | "PRESS CODE-RETURN TO EXIT SITE MANAGER WITHOUT SAVING CHANGES" 1042 | "PRESS CODE-ESC TO RETURN TO SITE MANAGER" 1043 | 1044 | This prevents users from inadvertently losing any changes that may have 1045 | been made during this SITE MANAGER session. 1046 | 1047 | 1048 | 10.4.2 SITE MANAGER Functions 1049 | 1050 | 10.4.2.1 CODE-N SELECT COMMUNICATION NETWORK 1051 | 1052 | This option displays the Network form which allows users to configure 1053 | entire communication networks "ON" or "OFF". If "ON" is selected, all 1054 | communications sites in that network will be turned "ON". Otherwise, all 1055 | sites for that network will be turned "OFF". 1056 | 1057 | 1058 | 10.4.2.2 CODE-I SELECT INDIVIDUAL COMMUNICATION SITES 1059 | 1060 | This option displays the Communication Site Selection form. Users may 1061 | configure each communication site "ON" or "OFF". Sites configured 1062 | premission as "ON" are indicated by "DEF" (default) in the fourth column 1063 | from the left. Sites are grouped by site type in alphabetical order. 1064 | TDRS satellites are at the top of the form, followed by STDN and Remote 1065 | Tracking Station (RTS) sites. If any user input sites have been added, 1066 | they will appear at the bottom of the form. 1067 | 1068 | 10.4.2.3 CODE-P ADD COMMUNICATION SITE 1069 | 1070 | This option allows users to add or edit user input site data. Site data 1071 | loaded premission can not be altered by users. Only user input site data 1072 | may be altered. 1073 | 1074 | The Site ID form appears after "CODE-P" is pressed. A site name composed 1075 | of three alpha characters is the first item to be entered on this form. 1076 | In the following examples, "ABC" will be used as the site name. The 1077 | characters entered may be either upper or lower case. 1078 | 1079 | The second Site ID form item allows users to select whether inputs pertain 1080 | to a ground site or TDRS. 1081 | 1082 | Acceptable inputs for the Site ID form: 1083 | 1084 | * Site Name : Exactly three alphabetic characters. 1085 | 1086 | Possible error messages: 1087 | 1088 | * 1) "IMPROPER COMMUNICATION SITE ID (REENTER ID)" 1089 | 1090 | * Problem: Three alphabetic characters were not entered for the site ID. 1091 | 1092 | * Solution: Enter three alphabetic characters. 1093 | 1094 | * 2) "DUPLICATE SITE ID" 1095 | * "IMPROPER COMMUNICATION SITE ID (REENTER ID)" 1096 | 1097 | * Problem: The site ID entered was used for a premission site. 1098 | 1099 | * Solution: Use a different site ID for the input site. 1100 | 1101 | 10.4.2.3.1 Adding a Ground Communications Site 1102 | 1103 | If "GROUND SITE" was selected from the Site ID form, the Site Data form 1104 | will appear. At the top of the form, "ENTERING ABC DATA" is displayed. 1105 | Also notice that the latitude and longitude settings are blank. Enter the 1106 | latitude and longitude (in decimal degrees). 1107 | 1108 | Select the correct frequency band for this input site with the "LEFTARROW" 1109 | and "RIGHTARROW" keys. 1110 | 1111 | 10.4.2.3.2 Adding a TDRS 1112 | 1113 | If "TDRSS" was selected from the Site ID form, the Site Data form will 1114 | appear as shown in. At the top of the form, "ENTERING ABC DATA" is 1115 | displayed. Notice that the longitude setting is blank. Enter the 1116 | longitude (in decimal degrees). 1117 | 1118 | 10.4.2.3.3 Editing User Input Ground Site Data 1119 | 1120 | If a site has previously been input and "GROUND SITE" was selected from 1121 | the Site ID form, the Site Data form will appear as shown in. At the top 1122 | of the form, "EDITING ABC DATA" is displayed. The form will display site 1123 | data for editing. 1124 | 1125 | 10.4.2.3.4 Editing User Input TDRS Data 1126 | 1127 | If a TDRS has previously been input and "TDRSS" was selected from the Site 1128 | ID form, the Site Data form will appear. At the top of the form, "EDITING 1129 | ABC DATA" is displayed. The TDRS longitude may then be updated. 1130 | 1131 | Acceptable inputs for the Site Data forms: 1132 | * Latitude: -90 through +90 (ground sites only) 1133 | * Longitude: -180 through +360 1134 | 1135 | Possible error messages: 1136 | * 1) "IMPROPER LONGITUDE ( REENTER LONGITUDE )" 1137 | * "IMPROPER LATITUDE ( REENTER LATITUDE )" 1138 | 1139 | * Problem: The inputs are out of range. 1140 | 1141 | * Solution: Correct erroneous inputs. 1142 | 1143 | 10.4.2.4 CODE-X DELETE COMMUNICATION SITES 1144 | 1145 | Only user input communication sites may be deleted. To mark one or more 1146 | sites for deletion, select "CODE-X DELETE COMMUNICATION SITES" from the 1147 | SITE MANAGER Main Menu. If there are currently any user input sites, the 1148 | Communication Site Deletion form will appear. If there are currently no 1149 | user input sites, this message will be displayed: 1150 | 1151 | 1152 | "THERE ARE NO "INPUT" SITES TO DELETE 1153 | PRESS ANY KEY TO CONTINUE 1154 | COMMUNICATION SITES" 1155 | 1156 | 1157 | Communication Sites Deletion Form 1158 | 1159 | Note that sites marked for deletion on this form will only be purged from 1160 | bubble memory when "CODE-D" or "CODE-S" is selected from the SITE MANAGER 1161 | Main Menu. Users may return to the Communication Site Deletion form and 1162 | mark or unmark sites for deletion on multiple occasions before they are 1163 | purged. 1164 | 1165 | User input sites marked for deletion will be accompanied by an asterisk 1166 | when displayed in the Site Selection form. 1167 | 1168 | 1169 | 1170 | 10.4.2.5 CODE-CTRL-SHIFT-P ADD EARTH OBSERVATION SITE 1171 | 1172 | This option allows users to add or edit a user input earth observation 1173 | site. All user input earth observation sites are point sites. A point 1174 | site is one point on the earth's surface defined by its latitude and 1175 | longitude. Sites that are loaded premission cannot be altered by users. 1176 | Only user input site data may be altered. 1177 | 1178 | To add or edit earth observation site data, select "CODE-CTRL-SHIFT-P 1179 | ADD EARTH OBSERVATION SITE" from the SITE MANAGER Main Menu. The 1180 | Observation Site ID form will be displayed. For the following examples, 1181 | "T104B" will be used as the site name. 1182 | 1183 | 1184 | After pressing "CODE-RETURN" in the Observation Site ID form, the 1185 | Observation Site Data form will appear. The format of the Observation 1186 | Site Data form will vary based on the inputs into the Observation Site ID 1187 | form. 1188 | 1189 | Acceptable inputs for the Observation Site ID form: 1190 | * Site Name : Maximum of five alpha-numeric characters. 1191 | 1192 | Possible error messages: 1193 | * 1) "IMPROPER EARTH OBSERVATION SITE ID (REENTER ID)" 1194 | 1195 | * Problem: Improper site name was entered. 1196 | 1197 | * Solution: Reenter site name. 1198 | 1199 | * 2) "DUPLICATE SITE NAME" 1200 | * "IMPROPER EARTH OBSERVATION SITE ID (REENTER ID)" 1201 | 1202 | * Problem: The site name entered was used for a premission site. 1203 | 1204 | * Solution: Use a different site name for the input site. 1205 | 1206 | 1207 | 10.4.2.5.1 Adding An Earth Observation Site 1208 | 1209 | If this is a new site to be added, "ENTERING T104B DATA" is displayed at 1210 | the top of the Observation Site Data form, indicating that data for the 1211 | new site "T104B" are being entered. Since this is a new site, the form 1212 | settings are blank. Enter the setting for each item. 1213 | 1214 | 10.4.2.5.2 Editing User Input Earth Observation Site Data 1215 | 1216 | If the site name entered into the Site ID form has previously been added, 1217 | the Observation Site Data form will be displayed with "EDITING T104B DATA" 1218 | at the top of the form. The data for this site will be displayed in the 1219 | form. Edit the necessary settings. 1220 | 1221 | Acceptable inputs for the Site Data form: 1222 | * Latitude: -90 through +90 1223 | * Longitude: -180 through +360 1224 | * Albedo: 6 through 18 1225 | 1226 | Possible error messages: 1227 | * 1) "IMPROPER LONGITUDE ( REENTER LONGITUDE )" 1228 | * "IMPROPER LATITUDE ( REENTER LATITUDE )" 1229 | * "IMPROPER ALBEDO (REENTER ALBEDO)" 1230 | 1231 | * Problem: The inputs are out of range. 1232 | 1233 | * Solution: Correct erroneous inputs. 1234 | 1235 | 10.4.2.6 CODE-CTRL-SHIFT-X DELETE EARTH OBSERVATION SITES 1236 | 1237 | Only user input earth observation sites may be deleted. To mark one or 1238 | more sites for deletion select "CODE-CTRL-SHIFT-X DELETE EARTH 1239 | OBSERVATION SITES" from the SITE MANAGER Main Menu. If there are 1240 | currently any user input sites, the Observation Site Deletion form will 1241 | appear. If there are currently no user input sites, this message will be 1242 | displayed: 1243 | 1244 | 1245 | "THERE ARE NO "INPUT" SITES TO DELETE 1246 | 1247 | PRESS ANY KEY TO CONTINUE 1248 | OBSERVATION SITES" 1249 | 1250 | 1251 | Note that sites marked for deletion on this form will only be purged from 1252 | bubble memory when "CODE-D" or "CODE-S" is selected from the SITE MANAGER 1253 | Main Menu. Users may return to the Earth Observation Site Deletion form 1254 | and mark or unmark sites for deletion on multiple occasions before they 1255 | are purged. 1256 | 1257 | 1258 | 1259 | 1260 | APPENDIX A--INITIALIZING THE SPoC 1261 | 1262 | 1263 | The following set of instructions leads a user through the procedures to 1264 | initialize the SPoC. After SPoC initialization is completed, the user may 1265 | proceed to APPENDIX B (WORLD MAP), C (DEORBIT), or D (CGMANAGER) for a 1266 | demonstration of SPoC applications. Familiarity with basic SPoC operation 1267 | is assumed. For the user unfamiliar with the SPoC, hardware setup 1268 | procedures for ground operation are found in Section 2.2. Details of 1269 | basic SPoC operations are contained in Section 3. 1270 | 1271 | When the SPoC is turned on, the Boot Up Screen is displayed after several 1272 | seconds. After the operating system has been loaded, the Boot Up Screen 1273 | will be erased. 1274 | 1275 | Messages will then be displayed informing users that the SPoC EXECUTIVE is 1276 | searching for programs and data files. 1277 | 1278 | Upon completion of the file search, the first initialization form will be 1279 | displayed (LAUNCH TIME UPDATE form). For this demo, follow the steps 1280 | below to enter the launch date/time, the current SGMT, and state vector. 1281 | 1282 | "LAUNCH TIME UPDATE Form" 1283 | 1284 | 1) Press "CODE-BACK SPACE" to erase old data. 1285 | YEAR: enter "1988" 1286 | press "RETURN". 1287 | 1288 | 2) Press "CODE-BACK SPACE" to erase old data. 1289 | DAY: enter "300" 1290 | press "RETURN". 1291 | 1292 | 3) Press "CODE-BACK SPACE" to erase old data. 1293 | HOUR: enter "0" 1294 | press "RETURN". 1295 | 1296 | 4) Press "CODE-BACK SPACE" to erase old data. 1297 | MINUTE: enter "0" 1298 | press "RETURN". 1299 | 1300 | 5) Press "CODE-BACK SPACE" to erase old data. 1301 | SECOND: enter "0" 1302 | press "CODE-RETURN". 1303 | 1304 | "GMT UPDATE Form" 1305 | 1306 | 6) Press "CODE-BACK SPACE" to erase old data. 1307 | DAY (GMT): enter "300" 1308 | press "RETURN". 1309 | 1310 | 7) Press "CODE-BACK SPACE" to erase old data. 1311 | HOUR (GMT): enter "0" 1312 | press "RETURN". 1313 | 1314 | 1315 | 8) Press "CODE-BACK SPACE" to erase old data. 1316 | MINUTE (GMT): enter "0" 1317 | press "RETURN". 1318 | 1319 | 9) Press "CODE-BACK SPACE" to erase old data. 1320 | YEAR: enter "1988" 1321 | press "CODE-RETURN". 1322 | 1323 | "NOTE:" If a warning message appears at this point, correct bad data and 1324 | press "CODE-RETURN". 1325 | 1326 | "STATE VECTOR UPDATE Form" 1327 | 1328 | 10) Press "CODE-BACK SPACE" to erase old data. 1329 | DAY (GMT): enter "300" 1330 | press "RETURN". 1331 | 1332 | 11) Press "CODE-BACK SPACE" to erase old data. 1333 | HOUR (GMT): enter "0" 1334 | press "RETURN". 1335 | 1336 | 12) Press "CODE-BACK SPACE" to erase old data. 1337 | MINUTE (GMT): enter "0" 1338 | press "RETURN". 1339 | 1340 | 13) Press "CODE-BACK SPACE" to erase old data. 1341 | SECOND (GMT): enter "0" 1342 | press "RETURN". 1343 | 1344 | 14) Press "CODE-BACK SPACE" to erase old data. 1345 | X POSITION (KFt): enter "-4065.5451" 1346 | press "RETURN". 1347 | 1348 | 15) Press "CODE-BACK SPACE" to erase old data. 1349 | Y POSITION (KFt): enter "19478.6516" 1350 | press "RETURN". 1351 | 1352 | 16) Press "CODE-BACK SPACE" to erase old data. 1353 | Z POSITION (KFt): enter "-9134.2843" 1354 | press "RETURN". 1355 | 1356 | 17) Press "CODE-BACK SPACE" to erase old data. 1357 | X VELOCITY (KFt/SEC): enter "-23.4998543" 1358 | press "RETURN". 1359 | 1360 | 18) Press "CODE-BACK SPACE" to erase old data. 1361 | Y VELOCITY (KFt/SEC): enter "-7.6119311" 1362 | press "RETURN". 1363 | 1364 | 19) Press "CODE-BACK SPACE" to erase old data. 1365 | Z VELOCITY (KFt/SEC): enter "-5.7686384" 1366 | press "CODE-RETURN". 1367 | 1368 | At the bottom of the screen the inclination, HA, and HP are displayed. 1369 | This serves as a data check for state vector inputs. For the above 1370 | inputs, the following values will be displayed. 1371 | 1372 | INCLINATION = 28.518 1373 | APPROX. ORBIT : HA=166; HP=159 1374 | 1375 | 1376 | 20) Press "CODE-RETURN". 1377 | 1378 | The SPoC Main Menu will now be displayed. The user may select SPoC 1379 | applications for execution. Step-by-step demos are available for WORLD 1380 | MAP (Appendix B), DEORBIT (Appendix C), and CGMANAGER (Appendix D). The 1381 | STATE VECTOR UPDATE and SET GMT programs are also available from the SPoC 1382 | Main Menu, and were demonstated during the initialization procedures. 1383 | 1384 | You are now ready to proceed to a SPoC demo of your choice. 1385 | 1386 | 1387 | APPENDIX B--WORLD MAP DEMONSTRATION 1388 | 1389 | 1390 | 1391 | Before exercising WORLD MAP demonstration procedures, the user should 1392 | complete procedures outlined in APPENDIX A (Initializing The SPoC). The 1393 | SPoC Main Menu should be currently displayed. The following instructions 1394 | will lead the user through a WORLD MAP demo. 1395 | 1396 | 1) Select "DISPLAY WORLD MAP" from the SPoC Main Menu. 1397 | 1398 | The first time WORLD MAP is selected from the SPoC Main Menu, the SITE 1399 | MANAGER Main Menu will be displayed. SITE MANAGER is a WORLD MAP function 1400 | which may be exercised later during this demo. For now, continue on to 1401 | the WORLD MAP display. 1402 | 1403 | 2) Select "INVOKE DEFAULT COMMUNICATION SITES" from the SITE MANAGER Main 1404 | Menu. 1405 | 1406 | After a few seconds, the WORLD MAP Display will appear. Notice that the 1407 | communication site AOS/LOS windows display the words "STAND BY". 1408 | 1409 | As soon as the AOS/LOS search has been completed, windows will display 1410 | AOS/LOS countdown times. 1411 | 1412 | 3) Press "CODE-?" to display the WORLD MAP Help Menu. 1413 | 1414 | This menu provides the "CODE-[key]" combinations associated with each 1415 | WORLD MAP function. WORLD MAP functions may be invoked from the Help 1416 | Menu. They may be invoked from the WORLD MAP display directly with the 1417 | proper "CODE-[key]" input. 1418 | 1419 | 4) To return to the WORLD MAP Display, press "CODE-ESC". 1420 | 1421 | At this time, you may want to explore various WORLD MAP functions. For a 1422 | detailed explanation of each WORLD MAP function, refer to Section 10.2. 1423 | Section 10.3 details the PSAT Display, and Section 10.4 details SITE 1424 | MANAGER functions. 1425 | 1426 | 5) When you are ready to exit WORLD MAP and return to the SPoC Main Menu, 1427 | press "CODE-ESC". 1428 | 1429 | 1430 | 1431 | 1432 | APPENDIX E--SPoC HISTORY 1433 | 1434 | 1435 | 1436 | The concept of an independent computational capability aboard the Shuttle 1437 | has been operational since STS-1. Originally, an HP41 calculator was 1438 | employed for this purpose. Data storage and manipulation capabilities, 1439 | absent from the GPC's because of core storage limitations, were provided 1440 | by this hand-held calculator. Also provided by the HP41 were capabilities 1441 | similar to existing ground-based processors in the event that the Shuttle 1442 | and crew were in a no-communication situation. As of April 5, 1983 the 1443 | HP41 flight programs included the following: 1444 | 1445 | 1446 | a) The CG program allowed the crew to track current X and Y-CG location as 1447 | a function of MET, OMS, and RCS propellant loadings, and whether payloads 1448 | were berthed or deployed. 1449 | 1450 | 1451 | b) The AOS program supplied the crew with information concerning the next 1452 | time the spacecraft would acquire a communications site. 1453 | 1454 | 1455 | c) The LANDTRACK program provided observation pass information for any 1456 | stored earth observation site. 1457 | 1458 | 1459 | d) The DEORBIT program provided the crew with deorbit maneuver targets in 1460 | the event of total loss of communications with the ground and a 1461 | time-critical systems failure requiring an emergency deorbit. 1462 | 1463 | 1464 | e) The ORBIT program provided the crew with data concerning attitudes and 1465 | rates involved in the star sighting function and with orbit sunrise and 1466 | sunset. 1467 | 1468 | 1469 | f) The ALARM program gave the crew a personalized reminder of upcoming 1470 | events of particular interest by having the calculator sound a tone and 1471 | display a pre-stored message. 1472 | 1473 | 1474 | g) The LANDING program computed data necessary for the approach and 1475 | landing phase of flight. 1476 | 1477 | 1478 | Although the HP41 has proven to be a useful tool, it has a very limited 1479 | memory capacity (only one of the above programs can be stored in memory at 1480 | a time), very limited text displays, and there is no graphics capability. 1481 | 1482 | As new requirements developed for independent computational capabilities 1483 | aboard the Shuttle, the HP41 became inadequate for the task. To augment 1484 | the hand-held calculator, the SPoC was introduced. SPoC is an expansion 1485 | of the HP41 calculator concept and enhances independent computation and 1486 | display capabilities by providing more memory, more mass storage, and 1487 | graphic displays. In 1983, the Ascent/Entry Procedures Section of the 1488 | Operations Branch began evaluating microcomputers for onboard 1489 | implementation. After evaluating several machines, a GRiD microcomputer 1490 | was selected because it met the hardware and software requirements and 1491 | constraints fully. A proposal was made to the Government Furnished 1492 | Equipment (GFE) Configuration Control Board (CCB) to obtain the necessary 1493 | funding for the project. The GFE CCB denied the request. To gain 1494 | necessary support for the project, presentations were made at the branch, 1495 | division, and directorate levels. After a SPoC presentation was made to 1496 | the Program Office Manager, Glynn Lunny, approval for the SPoC project was 1497 | given. Proposals were again made to the GFE CCB, and on 08/15/83 a Crew 1498 | Related GFE CCB Directive (#3D149) was issued authorizing purchase, 1499 | testing, certification, and preparation for flight of a GRiD Compass 1500 | Computer on STS-9. 1501 | 1502 | Purchased commercially and modified, the original SPoC was a GRiD Compass 1503 | 1101 lap top computer. The Compass 1101 has a 4.75 by 3.5 inch 1504 | electroluminescent screen, 384K bytes of non-volatile bubble memory and 1505 | 256K bytes of RAM. Modifications included replacing the internal modem 1506 | with a fan for cooling, since the standard Model 1101 computer uses 1507 | convective cooling. The lithium battery circuit, which provides power for 1508 | the internal clock while the Compass is not connected to an external power 1509 | supply, had supplemental diodes and a fuse installed to insure failsafe 1510 | operation. A power cable was designed for Orbiter power connector 1511 | compatibility. EMI tests showed the SPoC was out of specification. Since 1512 | the out-of-spec condition for SPoC would cause no problems for Orbiter 1513 | systems, communications, or payloads, the Space Shuttle Program 1514 | Requirements Control Board issued a directive (#S23562) to authorize a 1515 | waiver permitting the radiated EMI out-of-spec condition. 1516 | 1517 | SPoC was initially flown on STS-9 as a proof of concept engineering 1518 | evaluation. During this flight, it proved useful as an aid to crew 1519 | awareness and productivity. SPoC flight software for STS-9 included 1520 | programs that calculated and/or displayed the following data: 1521 | 1522 | MET 1523 | The world map (facsimile of the MCC world map) 1524 | Day and night areas on the earth's surface 1525 | AOS/LOS ID of the current/next ground communication site 1526 | AOS/LOS and ID of current/next TDRSS coverage 1527 | Current and two predicted ground tracks 1528 | Current position of the Orbiter on the world map 1529 | AOS of the next earth observation site 1530 | 1531 | Brewster Shaw, pilot for STS-9, stated "It's really a big asset to know 1532 | where we are all the time." Since SPoC was such an asset on STS-9, Flight 1533 | Equipment Project Office Configuration Control Board Directive #G1309 1534 | authorized one SPoC and power cord be manifested for STS-11 and subsequent 1535 | missions. 1536 | 1537 | An upgrade occurred in late 1984, with the Compass 1129 replacing the 1101 1538 | for STS-51C and subsequent missions. The GRiD Compass 1129 is the same 1539 | size as the 1101, with a 4.75 by 3.5 inch electroluminescent screen and 1540 | 384K bytes of non-volatile bubble memory. Improvements gained with the 1541 | 1129 include twice as much RAM (512K bytes) and four accessible slots for 1542 | PROM or EPROM chips. At this time, the necessary hardware and software 1543 | were purchased to develop EPROMs for flight. Use of socketed PROM and 1544 | EPROM chips was viewed as a possible interim solution for expanded mass 1545 | memory until a mass memory device was certified for flight. Compass 1129s 1546 | were purchased commercially and modified. The internal modem was replaced 1547 | with a fan for cooling and an EMI reducing "Tempest" screen was installed. 1548 | For crew safety, the lithium battery which provided power for the internal 1549 | clock was exchanged for a replaceable silver oxide battery and a clock 1550 | reset circuit. Also the foot was milled out to promote internal 1551 | ventilation while in the closed position for flight operation. 1552 | 1553 | In 1985, the SPoC was upgraded to a GRiD Compass 1139 for STS-51G and 1554 | subsequent missions. The GRiD Compass 1139 is similar to the 1129, having 1555 | the same memory capacity. It is an improvement over the 1129 because it 1556 | has a larger electroluminescent screen (7.5 by 3.5 inches) and a standard 1557 | internal fan for cooling. Like the 1129, this unit was purchased 1558 | commercially and modified for flight. Modifications include an 1559 | EMI-reducing "Tempest" screen, a replaceable silver oxide battery, a clock 1560 | reset circuit, a milled out foot, and the modem is removed. 1561 | 1562 | The original flight software configuration has been augmented since STS-9 1563 | to satisfy expanding functional requirements levied on the SPoC. The 1564 | flight software configuration now includes programs that calculate and/or 1565 | display the following data: 1566 | 1567 | Predicted Site Acquisition Table 1568 | Table of TDRSS AOS/LOS 1569 | Communication/Earth Obs site reconfiguration 1570 | Latitude and longitude of the Orbiter 1571 | AOS of future earth observation sites 1572 | Time to Orbiter sunrise, noon, sunset 1573 | Current F stop 1574 | F stop for the selected earth observation site 1575 | Sun glint position on the world map 1576 | Sun glint look angles 1577 | Longitude and MET of the next/previous ascending node 1578 | Time until/from the next/previous ascending node 1579 | Deorbit opportunities 1580 | Deorbit maneuver targeting 1581 | Orbiter CG and weight 1582 | CG management procedures 1583 | 1584 | The SPoC has also been used to provide computational support for special 1585 | purpose applications on a flight-specific basis. The Orbital Refueling 1586 | System (ORS) and the Gravity Gradient Free Drift experiments set a 1587 | precedent for using microprocessors to support payload experiments. 1588 | 1589 | Since 41-G, two SPoCs have been manifested for each Shuttle mission. The 1590 | primary unit is usually positioned on the forward flight deck above the 1591 | eyebrow panel, while the backup nominally supports middeck operations. 1592 | Even during emergency power-downs, one of these units remains running. 1593 | 1594 | 1595 | "NONCRITICAL BUT MANDATORY" 1596 | 1597 | Although the SPoC was classified as noncritical hardware by Configuration 1598 | Control Board Directive 1253, it is considered mandatory equipment. If 1599 | the SPoC fails, neither the crew nor the mission is threatened: thus the 1600 | noncritical classification. However, the SPoC is such an asset to the 1601 | crew and to MCC that it is mandatory equipment for flight. 1602 | 1603 | The following excerpts from reports and memos illustrate the importance of 1604 | the SPoC to Shuttle missions. 1605 | 1606 | "STS-9 Flight Crew Report" (Dec. 1983): "The SPoC proved to be a great 1607 | asset. It was unstowed and set up during the post insertion timeframe and 1608 | remained active until deorbit prep... The SPoC allowed the crew to see 1609 | where they were at all times and served as an accurate source of 1610 | communications coverage information. In light of the many dropouts of 1611 | TDRSS S-Band signal that were experienced, the SPoC AOS/LOS information 1612 | allowed the crew to manage the comm system in an efficient manner and 1613 | eliminated unnecessary trouble shooting. The SPoC appears to have great 1614 | potential that deserves further development for future Shuttle missions." 1615 | 1616 | "Memo from the Space Shuttle Earth Observations Project Manager" 1617 | (03/02/84, #SC5-84-32): "The GRiD SPoC has been of great value to the 1618 | Space Shuttle Earth Observations Project... Our contact with the crews 1619 | that have used the SPoC ...reflect extreme interest in its present 1620 | capabilities and proposed updates." 1621 | 1622 | The value of the SPoC in monitoring a payload was demonstrated for the 1623 | STS-41G ORS test: 1624 | 1625 | "Memo from John Young" (04/18/84, #CB-84-042): "The SPoC has been 1626 | determined by the crew to be not just useful, but mandatory for proper 1627 | crew monitoring of ORS hydrazine transfer operations. It provides the 1628 | proper displays that provide the crew their only insight into the 1629 | hydrazine heat transfer occurring during an ORS transfer operation for all 1630 | initial conditions. Using the SPoC information and the other ORS displays 1631 | and controls, timely and proper response can be made by the crew to any 1632 | ORS anomaly." 1633 | 1634 | "STS-41G Debrief Notes" (10/18/84): "[The SPoC was] very helpful because 1635 | no one had time to just sit by a window and watch for sites and 1636 | phenomena." 1637 | 1638 | "STS-51C Crew Report": "The presence of SPoC on our mission was a major 1639 | asset in helping us perform many of our tasks. Future capabilities for 1640 | SPoC will increase its utility even more...these computers have proven to 1641 | be very reliable..." 1642 | 1643 | "Memo from On-Orbit Flight Techniques Panel" (01/25/88, #DA8- 88-04): 1644 | "After reviewing the functions provided by the SPoC and assessing the 1645 | significant degree of support it provides for routine flight crew 1646 | operations, the FTP considers it to be a very important part of crew 1647 | equipment and recommends the Program consider it to be 'mandatory' for all 1648 | STS flights. 1649 | 1650 | "The FTP also recommends that the SPoC should continue to be classified as 1651 | criticality 3. These recommendations are based on two considerations. 1652 | 1653 | 1654 | 1655 | a) The primary SPoC function, that of an orbit trajectory status display, 1656 | does not jeopardize the crew, vehicle, or mission in the event of 1657 | malfunction. 1658 | 1659 | 1660 | b) The secondary SPoC function of providing a backup deorbit targeting 1661 | capability for emergency deorbit would only be used when the Mission 1662 | Control Center is unavailable for Orbiter support and an immediate deorbit 1663 | was required. The probability of this happening is extremely remote 1664 | because for every case except a large cabin leak, it takes multiple 1665 | failures before this capability would be needed, and most of those 1666 | combinations of failures, such as failure of both freon loops, are 1667 | considered non-credible. 1668 | 1669 | 1670 | "Retaining the SPoC's criticality 3 classification is highly desirable 1671 | because it allows a flexible and rapid response to new requirements. To 1672 | retain these desirable characteristics, functions considered inappropriate 1673 | for this classification should be integrated into other processors of an 1674 | appropriate classification." 1675 | 1676 | 1677 | 1678 | 1679 | APPENDIX F--GLOSSARY 1680 | 1681 | 1682 | AOS: Acquisition of Signal 1683 | 1684 | Boot Cycle: Period during which the computer is loading the operating 1685 | system and SPoC EXECUTIVE software. 1686 | 1687 | CG: Center of Gravity 1688 | 1689 | Choice Band: Rectangular area at the top of a form which will contain 1690 | choices or pertinent information. 1691 | 1692 | Choices: Predefined values for a setting. 1693 | 1694 | Command Key: RETURN key, ESCAPE key, and any other keys that select a menu 1695 | option. 1696 | 1697 | Confirm: Keyboard input of CODE-RETURN. 1698 | 1699 | Edit Prompt: A small triangular symbol which indicates a user input is 1700 | expected. 1701 | 1702 | EMCC: Emergency Mission Control Center 1703 | 1704 | EMI: Electromagnetic Interference 1705 | 1706 | EPROM: Erasable Programmable Read Only Memory 1707 | 1708 | FDO: Flight Dynamics Officer 1709 | 1710 | Form: User interface display which allows the user to enter or edit data 1711 | for one or more items. 1712 | 1713 | FRCS: Forward Reaction Control System 1714 | 1715 | GFE CCB: Government Furnished Equipment Configuration Control Board 1716 | 1717 | GMT: Greenwich Mean Time 1718 | 1719 | GNC: Guidance Navigation and Control 1720 | 1721 | GPC: General Purpose Computer 1722 | 1723 | Highlighted Box: If choices are available in the choice band, the 1724 | highlighted box indicates the current choice or highlights pertinent 1725 | information. 1726 | 1727 | ISP: Specific Impulse 1728 | 1729 | Item: Label which identifies the data to be modified in a form. 1730 | 1731 | LOS: Loss of Signal 1732 | 1733 | LOT: Landing Opportunities Table 1734 | 1735 | MCC: Mission Control Center 1736 | 1737 | Menu: User interface display which allows the user to select one of the 1738 | available options. 1739 | 1740 | MET: Mission Elapsed Time 1741 | 1742 | MOC: Mission Operations Computer 1743 | 1744 | MOCR: Mission Operations Control Room 1745 | 1746 | Modifier Keys: CODE keys, SHIFT key, and CONTROL key. 1747 | 1748 | Nadir: Projection of the Orbiter's position along the local vertical onto 1749 | the Earth's surface. 1750 | 1751 | OMS: Orbital Maneuvering System 1752 | 1753 | ORS: Orbital Refueling System 1754 | 1755 | PROM: Programmable Read Only Memory 1756 | 1757 | PSAT: Predicted Site Acquisition Table 1758 | 1759 | Prompt: Message informing the user what action should be taken next. 1760 | 1761 | PTI: Program Test Input 1762 | 1763 | RAM: Random Access Memory 1764 | 1765 | RCS: Reaction Control System 1766 | 1767 | RMS: Remote Manipulator System 1768 | 1769 | ROM: Read Only Memory 1770 | 1771 | RTS: Remote Tracking Station 1772 | 1773 | Selection Box: Rectangular outline enclosing the current item in a form or 1774 | the current option in a menu. 1775 | 1776 | Setting: Data value in a form. 1777 | 1778 | SGMT: Simulated GMT 1779 | 1780 | SPEC: GPC display used to view and modify parameters. 1781 | 1782 | SPoC: Shuttle Portable Computer 1783 | 1784 | STDN: Spaceflight Tracking and Data Network 1785 | 1786 | TDR: True of Date Rotating 1787 | 1788 | TDRS: Tracking and Data Relay Satellite 1789 | 1790 | TDRSS: Tracking and Data Relay Satellite System 1791 | 1792 | TIG: Time of Ignition 1793 | 1794 | 1795 | 1796 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # SPOC-VirtualBox 2 | 3 | VirtualBox configuration files for emulating Ian's bootable floppy (Tested on VirtualBox 5.1.4 on Windows 10) 4 | 5 | [![IMAGE ALT TEXT HERE](https://img.youtube.com/vi/quHlMiwTQZs/0.jpg)](https://www.youtube.com/watch?v=quHlMiwTQZs) 6 | 7 | Demo: https://www.youtube.com/watch?v=quHlMiwTQZs 8 | 9 | 10 | Instructions from Ian: https://groups.google.com/forum/#!topic/seattle-retrocomp/vN-gZYBUAb8 11 | ``` 12 | CODE key is mapped to Alt. 13 | CODE+Return to confirm. 14 | CODE+? For help. 15 | 16 | Make sure launch time < state vector time < current time, and all are less than Y2K. 17 | ``` 18 | 19 | 20 | -------------------------------------------------------------------------------- /SPOC-test.vbox: -------------------------------------------------------------------------------- 1 | 2 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | -------------------------------------------------------------------------------- /nasa-spoc.img: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/nasa-spoc.img -------------------------------------------------------------------------------- /spoc-fs/4201.CPI: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/4201.CPI -------------------------------------------------------------------------------- /spoc-fs/5202.CPI: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/5202.CPI -------------------------------------------------------------------------------- /spoc-fs/ANSI.SYS: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/ANSI.SYS -------------------------------------------------------------------------------- /spoc-fs/APPEND.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/APPEND.EXE -------------------------------------------------------------------------------- /spoc-fs/ASSIGN.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/ASSIGN.COM -------------------------------------------------------------------------------- /spoc-fs/ATTRIB.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/ATTRIB.EXE -------------------------------------------------------------------------------- /spoc-fs/BACKUP.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/BACKUP.COM -------------------------------------------------------------------------------- /spoc-fs/CHKDSK.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/CHKDSK.COM -------------------------------------------------------------------------------- /spoc-fs/COMMAND.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/COMMAND.COM -------------------------------------------------------------------------------- /spoc-fs/COMP.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/COMP.COM -------------------------------------------------------------------------------- /spoc-fs/COUNTRY.SYS: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/COUNTRY.SYS -------------------------------------------------------------------------------- /spoc-fs/DATACOPY.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/DATACOPY.EXE -------------------------------------------------------------------------------- /spoc-fs/DEBUG.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/DEBUG.COM -------------------------------------------------------------------------------- /spoc-fs/DISKCOMP.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/DISKCOMP.COM -------------------------------------------------------------------------------- /spoc-fs/DISKCOPY.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/DISKCOPY.COM -------------------------------------------------------------------------------- /spoc-fs/DISPLAY.SYS: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/DISPLAY.SYS -------------------------------------------------------------------------------- /spoc-fs/DRIVER.SYS: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/DRIVER.SYS -------------------------------------------------------------------------------- /spoc-fs/EDLIN.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/EDLIN.COM -------------------------------------------------------------------------------- /spoc-fs/EGA.CPI: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/EGA.CPI -------------------------------------------------------------------------------- /spoc-fs/EXE2BIN.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/EXE2BIN.EXE -------------------------------------------------------------------------------- /spoc-fs/FASTOPEN.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/FASTOPEN.EXE -------------------------------------------------------------------------------- /spoc-fs/FC.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/FC.EXE -------------------------------------------------------------------------------- /spoc-fs/FDISK.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/FDISK.COM -------------------------------------------------------------------------------- /spoc-fs/FIND.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/FIND.EXE -------------------------------------------------------------------------------- /spoc-fs/FORMAT.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/FORMAT.COM -------------------------------------------------------------------------------- /spoc-fs/GRAFTABL.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/GRAFTABL.COM -------------------------------------------------------------------------------- /spoc-fs/GRAPHICS.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/GRAPHICS.COM -------------------------------------------------------------------------------- /spoc-fs/GRID.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/GRID.EXE -------------------------------------------------------------------------------- /spoc-fs/GWBASIC.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/GWBASIC.EXE -------------------------------------------------------------------------------- /spoc-fs/IO.SYS: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/IO.SYS -------------------------------------------------------------------------------- /spoc-fs/JOIN.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/JOIN.EXE -------------------------------------------------------------------------------- /spoc-fs/KEYB.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/KEYB.COM -------------------------------------------------------------------------------- /spoc-fs/KEYBOARD.SYS: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/KEYBOARD.SYS -------------------------------------------------------------------------------- /spoc-fs/LABEL.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/LABEL.COM -------------------------------------------------------------------------------- /spoc-fs/LINK.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/LINK.EXE -------------------------------------------------------------------------------- /spoc-fs/MCONFIG.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/MCONFIG.COM -------------------------------------------------------------------------------- /spoc-fs/MODE.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/MODE.COM -------------------------------------------------------------------------------- /spoc-fs/MORE.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/MORE.COM -------------------------------------------------------------------------------- /spoc-fs/MSDOS.SYS: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/MSDOS.SYS -------------------------------------------------------------------------------- /spoc-fs/NLSFUNC.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/NLSFUNC.EXE -------------------------------------------------------------------------------- /spoc-fs/PRINT.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PRINT.COM -------------------------------------------------------------------------------- /spoc-fs/PRINTER.SYS: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PRINTER.SYS -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/AEROH.TXT: -------------------------------------------------------------------------------- 1 | 241659.00 250010.00 260210.00 269994.00 279653.00 290410.00 299967.00 309924.00 320191.00 329684.00 339280.00 350164.00 360110.00 370189.00 379253.00 389564.00 400000.00 2 | 0.000000104190000000 0.000000068513000000 0.000000040571000000 0.000000024827000000 0.000000015335000000 0.000000009058800000 0.000000005648900000 0.000000003344300000 0.000000001882100000 0.000000001089800000 0.000000000618420000 0.000000000335390000 0.000000000196350000 0.000000000121410000 0.000000000080135000 0.000000000052611000 0.000000000035735000 3 | 0.851500 0.847500 0.841700 0.834700 0.825900 0.813300 0.798900 0.787400 0.761100 0.727500 0.676200 0.606600 0.536800 0.469900 0.410600 0.350900 0.297900 4 | 0.811700 0.816400 0.824200 0.833600 0.845100 0.860900 0.879300 0.892100 0.917200 0.979700 1.068500 1.188700 1.309400 1.425200 1.527700 1.630700 1.722500 5 | 240016.00 250028.00 260201.00 270433.00 280086.00 289704.00 299829.00 310314.00 320084.00 330037.00 339126.00 349353.00 359700.00 369108.00 379661.00 389243.00 400000.00 6 | 0.000000077931000000 0.000000052110000000 0.000000033629000000 0.000000020867000000 0.000000013048000000 0.000000007966900000 0.000000004753900000 0.000000002841700000 0.000000001753600000 0.000000001059500000 0.000000000652190000 0.000000000376310000 0.000000000215680000 0.000000000137020000 0.000000000084090000 0.000000000056665000 0.000000000037879000 7 | 0.848800 0.844600 0.839200 0.831800 0.822400 0.809700 0.792800 0.782200 0.756100 0.725200 0.681600 0.620600 0.549300 0.486600 0.417000 0.360800 0.305200 8 | 0.814900 0.820200 0.827500 0.837400 0.849500 0.865400 0.887200 0.896700 0.922200 0.983700 1.059200 1.164600 1.287900 1.396200 1.516500 1.613600 1.709900 9 | 25.8 10 | 25.8 11 | 25.2 12 | 25.2 13 | 200000 14 | 13 15 | -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/AEROL.TXT: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/AEROL.TXT -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/BKGROUND.RUN: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/BKGROUND.RUN -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/CARGO.TXT: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/CARGO.TXT -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/COMMON.SHR: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/COMMON.SHR -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/CONSUM.TXT: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/CONSUM.TXT -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/CSITES.TXT: -------------------------------------------------------------------------------- 1 | TDE TDRSS K 1 1 104401979 -90755267 0 2 | TDW TDRSS K 1 1 -136630867 -21640191 0 3 | TDX TDRSS K 0 0 26395352 -135792404 0 4 | BDA STDN SU 1 1 7566468 -15976529 11197577 5 | BDX STDN SU 1 1 7566314 -15976618 11197555 6 | CAN STDN SU 0 0 -14617263 8788938 -12123401 7 | DFR STDN U 0 0 -8022535 -15160000 11987494 8 | DKR STDN S 1 1 19340840 -5960569 5318851 9 | GDX STDN SU 1 1 -7715829 -15226098 12104486 10 | MAX STDN SU 0 0 15884816 -1180836 13570737 11 | MIL STDN SU 1 1 2973726 -18146415 9987555 12 | MLX STDN SU 1 1 2973941 -18146372 9987568 13 | VAN STDN S 1 1 -8746225 -14847243 11872218 14 | GDS RTS SU 1 1 -7715717 -15226003 12104676 15 | GTS RTS SU 1 1 -16630106 11707236 4926141 16 | HTS RTS SU 1 1 -18076584 -7207332 7692731 17 | IOS RTS SU 1 1 11819792 17183549 -1704353 18 | NHS RTS SU 1 1 4827358 -14537342 14256540 19 | OTS RTS SU 1 1 13134992 -205211 16288540 20 | VTS RTS SU 1 1 -8719771 -14800092 11950295 21 | -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/DAYMAP.RUN: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/DAYMAP.RUN -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/EMULATOR.SHR: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/EMULATOR.SHR -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/ESITES.TXT: -------------------------------------------------------------------------------- 1 | T023 2 | -26.00 16.00 5 13 3 | -23.00 13.00 4 | -22.00 16.00 5 | -31.00 19.00 6 | -32.00 17.00 7 | -23.00 13.00 8 | T043 9 | -19.00 13.00 5 13 10 | -15.00 10.00 11 | -15.00 14.00 12 | -22.00 16.00 13 | -23.00 13.00 14 | -15.00 10.00 15 | T045 16 | -25.50 28.00 5 11 17 | -21.00 28.00 18 | -21.00 31.00 19 | -30.00 31.00 20 | -30.00 25.00 21 | -21.00 28.00 22 | T108 23 | 8.00 80.50 5 11 24 | 10.00 79.00 25 | 10.00 81.00 26 | 6.00 83.00 27 | 5.00 79.00 28 | 10.00 79.00 29 | T183 30 | -1.50 103.00 7 11 31 | 3.00 98.00 32 | 3.00 100.00 33 | -2.50 106.00 34 | -5.00 106.00 35 | -6.00 104.00 36 | -1.00 100.00 37 | 3.00 98.00 38 | T186 39 | -8.00 114.50 5 11 40 | -7.00 104.00 41 | -5.50 105.00 42 | -8.00 125.00 43 | -11.00 120.00 44 | -7.00 104.00 45 | T187 46 | 0.00 114.00 7 11 47 | 2.00 109.00 48 | 6.00 116.00 49 | 4.00 118.00 50 | 1.00 119.00 51 | -4.00 117.00 52 | -4.00 109.00 53 | 2.00 109.00 54 | T189 55 | -2.00 121.00 7 11 56 | -3.00 118.00 57 | 2.00 120.00 58 | 2.00 125.50 59 | -2.00 124.00 60 | -6.00 124.00 61 | -6.00 119.00 62 | -3.00 118.00 63 | T190 64 | 12.00 124.00 6 13 65 | 19.00 120.00 66 | 19.00 123.00 67 | 5.00 128.00 68 | 5.00 120.00 69 | 14.00 119.00 70 | 19.00 120.00 71 | T193 72 | -5.00 138.00 7 11 73 | 0.00 130.00 74 | 0.00 138.00 75 | -5.00 146.00 76 | -10.00 142.00 77 | -10.00 140.00 78 | -5.00 130.00 79 | 0.00 130.00 80 | T195 81 | -6.50 145.50 6 11 82 | -2.00 140.00 83 | -5.00 146.00 84 | -10.00 151.00 85 | -11.50 151.00 86 | -5.00 140.00 87 | -2.00 140.00 88 | T197 89 | 7.00 102.00 7 11 90 | 13.00 98.00 91 | 13.00 100.00 92 | 10.00 100.00 93 | 1.00 106.00 94 | 1.00 103.00 95 | 7.00 98.00 96 | 13.00 98.00 97 | T204 98 | -16.50 126.50 6 13 99 | -17.00 122.00 100 | -14.00 127.00 101 | -13.00 130.00 102 | -15.00 130.00 103 | -20.00 126.00 104 | -17.00 122.00 105 | T209 106 | -28.00 139.50 6 13 107 | -22.00 136.00 108 | -22.00 138.00 109 | -27.00 143.00 110 | -32.00 141.00 111 | -29.00 136.00 112 | -22.00 136.00 113 | T210 114 | -15.50 143.00 5 13 115 | -20.00 138.00 116 | -11.00 142.00 117 | -11.00 143.00 118 | -20.00 148.00 119 | -20.00 138.00 120 | T218 121 | -24.00 144.00 6 11 122 | -20.00 140.00 123 | -20.00 146.00 124 | -26.00 149.00 125 | -28.00 144.00 126 | -25.00 140.00 127 | -20.00 140.00 128 | T219 129 | -23.00 124.50 5 13 130 | -20.00 121.00 131 | -20.00 128.00 132 | -26.00 128.00 133 | -26.00 121.00 134 | -20.00 121.00 135 | T220 136 | -20.00 132.50 5 13 137 | -18.00 130.00 138 | -18.00 135.00 139 | -22.00 135.00 140 | -22.00 130.00 141 | -18.00 130.00 142 | T234 143 | -21.50 166.00 5 13 144 | -20.00 164.00 145 | -20.00 168.00 146 | -23.00 168.00 147 | -23.00 164.00 148 | -20.00 164.00 149 | T304 150 | 14.50 -88.50 5 13 151 | 16.00 -92.00 152 | 16.00 -84.00 153 | 13.00 -87.00 154 | 14.00 -92.00 155 | 16.00 -92.00 156 | T306 157 | 8.50 -80.00 6 13 158 | 10.00 -83.00 159 | 9.50 -79.00 160 | 9.00 -79.00 161 | 7.00 -77.00 162 | 7.00 -83.00 163 | 10.00 -83.00 164 | T313 165 | 11.50 -85.50 5 13 166 | 13.00 -88.00 167 | 15.00 -83.00 168 | 8.00 -83.00 169 | 10.00 -86.00 170 | 13.00 -88.00 171 | T316 172 | 1.50 -77.00 5 13 173 | -1.00 -79.50 174 | 5.00 -76.00 175 | 5.00 -75.00 176 | -2.00 -78.00 177 | -1.00 -79.50 178 | T323 179 | 4.00 -61.00 7 11 180 | 5.00 -68.00 181 | 8.00 -67.00 182 | 8.00 -60.00 183 | 5.00 -54.00 184 | 2.00 -54.00 185 | 0.00 -66.00 186 | 5.00 -68.00 187 | W042 188 | 10.50 95.00 5 13 189 | 15.00 92.00 190 | 15.00 98.00 191 | 6.00 98.00 192 | 5.00 92.00 193 | 15.00 92.00 194 | W047 195 | 10.00 114.00 8 13 196 | 21.00 107.00 197 | 20.00 120.00 198 | 5.00 125.00 199 | 2.00 112.00 200 | 2.00 104.00 201 | 12.00 100.00 202 | 10.00 108.00 203 | 21.00 107.00 204 | W052 205 | 26.50 127.50 5 13 206 | 23.00 123.00 207 | 30.00 128.00 208 | 30.00 132.00 209 | 23.00 127.00 210 | 23.00 123.00 211 | W057 212 | 25.50 142.00 5 13 213 | 28.00 140.00 214 | 28.00 144.00 215 | 23.00 144.00 216 | 23.00 140.00 217 | 28.00 140.00 218 | W058 219 | 17.00 145.50 5 13 220 | 21.00 144.00 221 | 21.00 147.00 222 | 13.00 147.00 223 | 13.00 144.00 224 | 21.00 144.00 225 | W064 226 | -20.00 158.00 5 13 227 | -10.00 145.00 228 | -10.00 167.00 229 | -30.00 167.00 230 | -30.00 153.00 231 | -10.00 145.00 232 | W065 233 | -4.00 150.50 5 13 234 | 0.00 142.00 235 | 0.00 152.00 236 | -8.00 160.00 237 | -8.00 148.00 238 | 0.00 142.00 239 | W066 240 | 7.50 151.50 5 13 241 | 9.00 149.00 242 | 9.00 154.00 243 | 6.00 154.00 244 | 6.00 149.00 245 | 9.00 149.00 246 | W069 247 | 5.50 169.50 5 13 248 | 13.00 163.00 249 | 13.00 172.00 250 | -4.00 178.00 251 | -1.00 165.00 252 | 13.00 163.00 253 | W073 254 | -17.50 -164.00 5 13 255 | -5.00 167.00 256 | -5.00 -135.00 257 | -30.00 -135.00 258 | -30.00 167.00 259 | -5.00 167.00 260 | W076 261 | 28.50 -177.50 5 13 262 | 30.00 -175.00 263 | 27.00 -175.00 264 | 27.00 180.00 265 | 30.00 180.00 266 | 30.00 -175.00 267 | -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/GEXEC.RUN: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/GEXEC.RUN -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/LFORM.RUN: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/LFORM.RUN -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/LSITES.TXT: -------------------------------------------------------------------------------- 1 | 770 2 | 832 3 | AML 0.2919015 5.8826032 177 0.0000000 4 | BDA 0.5648126 5.1545972 -241 4.9124655 5 | BEN 0.5604007 6.1456854 1285 6.2134493 6 | BYD 0.2326233 5.9927505 33 5.4210852 7 | DDN -0.2167601 2.2845414 295 5.1182295 8 | EDW 0.6096590 4.2265437 2086 3.3173432 9 | GDV 0.4873321 6.0146441 97 0.3515472 10 | GUA 0.2369233 2.5292078 447 1.1542870 11 | HAO -0.3152840 3.8230225 10 2.3596544 12 | HDS -0.4248286 0.5417415 1613 2.8967158 13 | HNL 0.3718727 3.5265080 -88 1.5698436 14 | JDG -0.1277836 1.2640625 9 5.2440677 15 | KIN -0.0763495 0.2699101 903 4.1657882 16 | KKI 0.4358224 0.8146322 2039 2.6172927 17 | KSC 0.4991150 4.8750074 -199 5.7596104 18 | MRN 0.6490908 6.1852879 597 3.4878904 19 | NOR 0.5752667 4.4258516 3771 3.2679945 20 | ROB 0.1085449 6.1021486 29 0.5732738 21 | -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/LTIME.TXT: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/LTIME.TXT -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/MAPINTEG.MAP: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/MAPINTEG.MAP -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/MET.RUN: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/MET.RUN -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/PROP.TXT: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/PROP.TXT -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/PSAT.RUN: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/PSAT.RUN -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/README.DOC: -------------------------------------------------------------------------------- 1 | Shuttle Portable Computer Flight Procedures Handbook 2 | 3 | This is an edited version of the official Shuttle Portable Computer (SPoC) 4 | Flight Procedures Handbook. This document applies only to the version of 5 | SPoC available through NASA Spacelink. 6 | 7 | Orbital state vectors required for this program are available for each 8 | Shuttle mission from NASA Spacelink (Data line 205/895-0028). Use the 9 | "M50 Elements" figures. And remember that SPoC requires figures 10 | in thousands of feet. The M50 elements on NASA Spacelink are often 11 | given in feet. Don't forget to move the decimal three places to the 12 | left before entering the figures into SPoC. 13 | 14 | The following hardware is required for proper operation of this program: 15 | 16 | IBM PC or compatible with math co-processor installed 17 | Hard Drive at location C: 18 | Minimum 512K available memory NOTE: If you are running software 19 | (network software for example) that occupies enough memory to 20 | leave less than 512K for SPoC, SPoC will very likely crash. 21 | 22 | GRID.EXE, SPOC.BAT, and the PROGRAMS subdirectory, must be located in the 23 | Drive C: ROOT directory. 24 | 25 | To run the SPoC software type SPoC at the C> prompt. 26 | 27 | NOTE: The CODE key referred to in this document is the ALT key on IBM PC 28 | compatible computers. 29 | 30 | NOTE: As you will read in the following document, SPoC was written to 31 | run on a GRID computer--not an IBM-PC. Before making SPoC available 32 | through NASA Spacelink, we tested it on a variety of IBM-PC and 33 | compatible computer configurations with mixed results. For example, 34 | SPoC seemed to run properly on one computer, but its VGA display 35 | scrambled the screen making the program unreadable. Other VGA 36 | displays gave no problems. So if SPoC doesn't run on your 37 | particular setup, try it on another computer. 38 | 39 | 40 | 41 | 42 | 43 | SHUTTLE PORTABLE COMPUTER (SPoC) 44 | 45 | FLIGHT PROCEDURES HANDBOOK 46 | 47 | 48 | NATIONAL AERONAUTICS AND SPACE ADMINISTRATION 49 | LYNDON B. JOHNSON SPACE CENTER 50 | HOUSTON, TEXAS 51 | 52 | 53 | 54 | 55 | TABLE OF CONTENTS 56 | 57 | SECTION TITLE 58 | 59 | 1.0 INTRODUCTION 60 | 1.1 SPoC Mission Definition 61 | 1.2 How To Use This Handbook 62 | 63 | 2.0 HARDWARE 64 | 65 | 3.0 SPoC USER INTERFACE 66 | 3.1 Modifier and Command Keys 67 | 3.2 Special Key Combinations 68 | 3.3 The Selection Box 69 | 3.4 SPoC Menus 70 | 3.5 SPoC Forms 71 | 3.6 Messages 72 | 73 | 4.0 OVERVIEW OF SPoC PROGRAMS 74 | 75 | 5.0 BOOT UP SCREEN 76 | 77 | 6.0 LAUNCH TIME UPDATE 78 | 79 | 7.0 GMT UPDATE 80 | 81 | 8.0 STATE VECTOR UPDATE 82 | 83 | 9.0 SPoC MAIN MENU 84 | 85 | 10.0 WORLD MAP 86 | 10.1 World Map Help Menu 87 | 10.2 World Map Display 88 | 10.2.1 Current MET 89 | 10.2.2 AOS/LOS of TDRS Coverage 90 | 10.2.3 AOS/LOS of Ground Communication Site 91 | 10.2.4 Spacecraft Sunrise, Noon, Sunset 92 | 10.2.5 TDRS Coverage 93 | 10.2.6 Earth Day/Night 94 | 10.2.7 Earth Observation Area 95 | 10.2.8 Ground Communication Sites 96 | 10.2.9 Shuttle Bug 97 | 10.2.10 Enlarged F-Stop Display 98 | 10.2.11 Current and Two Predicted Ground Tracks 99 | 10.2.12 Tone Indicator 100 | 10.2.13 Latitude, Longitude and Current F-Stop 101 | 10.2.14 Ascending Node Time 102 | 10.2.15 Earth Observation Site 103 | 10.2.16 Longitude, MET, and Countdown Timer For Next Ascending Node 104 | 10.2.17 Longitude, MET, and Time Since Previous Ascending Node 105 | 10.2.18 Sun Glint Angle and Azimuth 106 | 10.2.19 Sun Glintpoint Area 107 | 10.3 PSAT 108 | 10.4 SITE MANAGER 109 | 10.4.1 SITE MANAGER Exit Options 110 | 10.4.1.1 CODE-D INVOKE DEFAULT COMMUNICATION SITES 111 | 10.4.1.2 CODE-S SAVE CHANGES PROCEED TO DAYMAP 112 | 10.4.1.3 CODE-ESC NO CHANGES PROCEED TO DAYMAP 113 | 10.4.2 SITE MANAGER Functions 114 | 10.4.2.1 CODE-N SELECT COMMUNICATION NETWORK 115 | 10.4.2.2 CODE-I SELECT INDIVIDUAL COMMUNICATION SITES 116 | 10.4.2.3 CODE-P ADD COMMUNICATION SITE 117 | 10.4.2.3.1 Adding a Ground Communications Site 118 | 10.4.2.3.2 Adding a TDRS 119 | 10.4.2.3.3 Editing User Input Ground Site Data 120 | 10.4.2.3.4 Editing User Input TDRS Data 121 | 10.4.2.4 CODE-X DELETE COMMUNICATION SITES 122 | 10.4.2.5 CODE-CTRL-SHIFT-P ADD EARTH OBSERVATION SITE 123 | 10.4.2.5.1 Adding An Earth Observation Site 124 | 10.4.2.5.2 Editing User Input Earth Observation Site Data 125 | 10.4.2.6 CODE-CTRL-SHIFT-X DELETE EARTH OBSERVATION SITES 126 | 127 | 128 | 129 | APPENDIX TITLE 130 | 131 | A INITIALIZING THE SPoC 132 | B WORLD MAP DEMONSTRATION 133 | E SPoC HISTORY 134 | F GLOSSARY 135 | 136 | 137 | 138 | 139 | SECTION 1.0 INTRODUCTION 140 | 141 | The concept of an independent computational capability aboard the Shuttle 142 | has been operational since STS-1. Originally the HP41 hand-held 143 | calculator was employed for this purpose, but it has significant 144 | limitations. The SPoC greatly augments HP41 capabilities. STS-9 was the 145 | first Shuttle mission manifested with a SPoC, and it proved to be such an 146 | asset for the crew that a SPoC has been manifested on every subsequent 147 | Shuttle mission. In its original role it was used as a situational 148 | awareness aid, depicting the Orbiter and its ground track over the earth's 149 | surface. The SPoC has evolved to provide a backup alternative means of 150 | obtaining landing opportunities, deorbit targets, and center of gravity 151 | management procedures. These targets and procedures are only utilized in 152 | the event of a total loss of communications with the ground or a time 153 | critical systems failure during a loss of communication period requiring 154 | an emergency deorbit before ground assistance can be provided. Nominally, 155 | the SPoC is unstowed and set up during the post insertion time frame and 156 | remains active until entry interface minus 20 minutes. 157 | 158 | The SPoC saves Mission Control Center (MCC) personnel time and resources 159 | by eliminating need to routinely transmit such data as Aquisition of 160 | Signal/Loss of Signal (AOS/LOS) times via voice or teleprinter. During 161 | the mission, the Flight Dynamics Officer (FDO) will take SPoC system 162 | questions in the MCC Mission Operations Control Room (MOCR) and pass them 163 | to the SPoC Team if necessary. 164 | 165 | 166 | 1.1 SPoC Mission Definition 167 | 168 | The SPoC is a portable "lap top" microcomputer providing the crew and 169 | mission operations personnel with an independent computational and display 170 | facility, enhancing productivity and reliability. This microcomputer is 171 | mandatory for flight because of the crew support it provides. The SPoC 172 | was designated as noncritical hardware by Configuration Control Board 173 | Directive 1253 in 1983. This classification was reaffirmed in 1987 by 174 | On-Orbit Flight Techniques Panel Meeting #82 [ref. NASA memo DA8-88-04 175 | (FT)]. Currently, there are four major roles for the SPoC. 176 | 177 | a) Provide automated cues for such events as upcoming ground communication 178 | times, earth observation site availability, sunrise and sunset times, 179 | nodal crossings, orbiter ground track, and location over the earth's 180 | surface. 181 | 182 | b) Provide a backup alternative means of obtaining landing opportunities, 183 | deorbit targets, and center of gravity management procedures in the event 184 | of a total loss of communications with the ground or a time-critical 185 | systems failure during a loss of communication period requiring an 186 | emergency deorbit before ground assistance can be provided. 187 | 188 | c) Provide computational and display support for special purpose 189 | applications on a flight-specific basis (e.g. the Orbit Refueling System 190 | {ORS} and the Gravity Gradient Free Drift programs). 191 | 192 | d) Provide mission status and contingency deorbit support in the Emergency 193 | Mission Control Center (EMCC). 194 | 195 | 196 | 1.2 How To Use This Handbook 197 | 198 | This handbook relates procedures and concepts associated with SPoC 199 | operation. Acronyms and other terms pertinent to this discussion, but 200 | whose definitions may not be apparent from context, are defined in 201 | APPENDIX F (GLOSSARY). As a convention, the names of SPoC applications 202 | will be in capitals. A brief history of the SPoC is presented in Appendix 203 | E. 204 | 205 | If you are interested in operating SPoC immediately, proceed to 206 | Appendix A, INITIALIZING THE SPoC, for your first SPoC session. 207 | Appendices A through D are designed to provide an introductory overview 208 | without exercising all SPoC capabilities. For the location of complete 209 | and detailed information, consult the Table of Contents. 210 | 211 | 212 | 213 | SECTION 2.0 HARDWARE 214 | 215 | The SPoC has 384k bytes of nonvolatile bubble memory for use in storing 216 | programs and data. Four Erasable Programmable Read Only Memory (EPROM) 217 | slots, located above the keyboard, are user-accessible. Each SPoC EPROM 218 | has a 64k byte capacity, providing 256k bytes of Read Only Memory (ROM). 219 | The SPoC directly accesses 512k bytes of Random Access Memory (RAM). The 220 | foldup display is a high resolution electroluminescent flat panel which 221 | measures 7-and-9/16 by 3-and-3/4 inches (512 pixels by 256 scanlines). 222 | 223 | There are four types of keys on the SPoC: alphabetic/numeric keys, 224 | modifier keys for issuing commands, arrow keys for positioning the cursor, 225 | and a return key for selection box control. The memory, display, and 226 | 57-character keyboard are in a magnesium case, which together weighs 227 | approximately 10 pounds. The unit will fit into one-half of a standard 228 | size briefcase. 229 | 230 | SPoC is hosted on a GRiD Compass computer purchased off-the-shelf and 231 | modified for flight. A standard lithium battery circuit that provides 232 | power for the internal clock is replaced by a silver oxide battery and 233 | equipped with diodes and a fuse to ensure fail-safe operation. The 234 | internal modem is removed. Flight displays are fitted with 235 | electromagnetic interference filters. This prevents electromagnetic 236 | interference generated by the electroluminescent display from harming the 237 | General Purpose Computers (GPCs) or other equipment onboard. When used 238 | onboard the Shuttle, SPoC runs on phase A ac power and uses a power cable 239 | which is compatible with the Orbiter's power outlets. Finally, the foot 240 | of a flight SPoC is milled to permit fan exhaust flow when folded up for 241 | flight operation. 242 | 243 | 244 | SECTION 3.0 SPoC USER INTERFACE 245 | 246 | SPoC applications have been designed for similarity in appearance and 247 | operation. Utilization of menus and forms allows the user to select, 248 | input, edit, and execute without unnecessary typing. Menus permit the 249 | user to select a single item for execution, while forms permit the user to 250 | input several data values on one display. Prompts appear at the bottom of 251 | the screen, as an aid to the user. When appropriate, error messages also 252 | appear at the bottom of the screen instructing the user how to correct 253 | erroneous inputs. 254 | 255 | NOTE: Messages are displayed on the screen in inverse video. In this 256 | document, messages displayed on screen images will appear as black 257 | characters against a white background. This is done for readability. 258 | 259 | 260 | "3.1 Modifier and Command Keys" 261 | 262 | Modifier keys include the "CODE" keys, "SHIFT" keys, and the "CONTROL" 263 | key. The "CODE" keys and "SHIFT" keys are located at the lower left and 264 | lower right of the keyboard. The "CONTROL" key is located at the lower 265 | left corner of the keyboard. The "RETURN" key, "ESCAPE" key, and any 266 | other keys that invoke a menu option are command keys. The most often 267 | used modifier keys are the "CODE" keys. To execute any menu option or to 268 | accept the settings in a form, the user must hold down a modifier key(s) 269 | and then press the appropriate command key. 270 | 271 | "CAUTION": SPoC EXPECTS THE COMMAND KEY "PRESS" ACTION TO BE BRIEF (NO 272 | MORE THAN 0.2 SECONDS). Pressing a command key for finite intervals may 273 | issue multiple instructions with unpredictable results. 274 | 275 | 276 | "3.2 Special Key Combinations" 277 | 278 | Throughout the remainder of this handbook, the following convention will 279 | be followed. "CODE-[key]" will indicate that the "CODE" key is held down 280 | until the "[key]" is pressed. As an example, "CODE-RETURN" indicates that 281 | the user holds down the "CODE" key until the "RETURN" key is pressed. 282 | "CODE-ESCAPE" indicates that the "CODE" key is held down until the 283 | "ESCAPE" key is pressed. "CODE-M" indicates that the "CODE" key is held 284 | down until ""M"" is pressed. "CODE-CTRL-SHIFT-N" indicates that the 285 | "CODE" key and the "CTRL" key are held down until ""N"" is pressed. A 286 | menu item will be executed or form settings will be accepted only if a 287 | "CODE-[key]" combination is pressed. The "CODE-RETURN" combination 288 | executes the menu option selected or accepts the form settings selected. 289 | The "CODE-ESCAPE" combination has a special function. To exit a menu 290 | without executing any of the displayed options or to exit a form without 291 | modifying the form settings, press "CODE-ESCAPE". If the user presses 292 | "CODE-ESCAPE", program control returns to the previously displayed screen. 293 | If "CODE-ESCAPE" is pressed at the main menu of a program, the program is 294 | exited and control returns to the SPoC Main Menu, which displays the 295 | available applications. A "CODE-ESC" from the SPoC Main Menu is ignored. 296 | 297 | 298 | "3.3 The Selection Box" 299 | 300 | The selection box is a moving rectangular outline that encloses the 301 | current option or setting. In a menu, the selection box identifies the 302 | option that will be executed when the user presses "CODE-RETURN". In a 303 | form, the selection box identifies data currently being modified. 304 | Movement of the selection box is controlled by the "RETURN" key. Each 305 | time the "RETURN" key is pressed, the selection box advances to the next 306 | option. If the "RETURN" key is pressed while the selection box is located 307 | on the last option of the menu, the selection box will advance to the 308 | first option on the menu. 309 | 310 | If the menu in receives a "CODE-RETURN" with the selection box located on 311 | the first option, the WORLD MAP application will be executed. Press the 312 | "RETURN" key once, and the selection box advances to the next option. 313 | 314 | If the menu receives a "CODE-RETURN" with the selection box located on the 315 | second option, STATE VECTOR UPDATE will be executed. 316 | 317 | "3.4 SPoC Menus" 318 | 319 | SPoC menus permit the user to select one option to be executed with a 320 | minimum of keystrokes. To select an option, press the "RETURN" key 321 | repeatedly until the selection box is located on the option to be 322 | executed. Press "CODE-RETURN" to execute the option. There is an 323 | alternate method of selecting and executing an option from a menu. Press 324 | "CODE-[key]", where "[key]" is the designated letter for the option to be 325 | executed. Using the SPoC Main Menu as an example, DEORBIT can be selected 326 | by pressing the "RETURN" key three times to locate the selection box on 327 | the menu option DEORBIT. DEORBIT is then executed by pressing 328 | "CODE-RETURN". Using the alternate method, DEORBIT can be selected and 329 | executed by pressing "CODE-D" regardless of where the selection box is 330 | currently located. 331 | 332 | 333 | "3.5 SPoC Forms" 334 | 335 | SPoC forms permit the user to enter or edit data for one or more items. 336 | Forms are different from menus for these reasons: 337 | 338 | a) Forms let users change the settings of several items. Menus let users 339 | select only one option. 340 | 341 | b) Users may input their own settings to forms. Many forms do not limit 342 | users 343 | to predefined choices. 344 | 345 | c) When users press "CODE-RETURN", they accept the settings of all form 346 | items, 347 | not just the outlined setting. 348 | 349 | A form consists of the following components. 350 | 351 | "Items": labels which identify data to be modified. Each item has a 352 | setting associated with it. 353 | 354 | "Settings": actual values the user has typed, chosen from the choice band, 355 | or received by default. These settings are either choice or editable 356 | fields, depending on the application. 357 | 358 | "Selection box": moving indicator that surrounds the setting currently 359 | being modified. "RETURN" moves it down and "SHIFT-UPARROW" moves it up. 360 | 361 | "Choice band": located at the top of the form, it may be configured in one 362 | of three ways. If there are choices for the current item, the choices are 363 | displayed there. If the item is an editable item, the choice band may be 364 | blank or contain pertinent information with the edit prompt. 365 | 366 | "Choices": predefined values for a setting, which appear in the choice 367 | band. The highlighted choice appears within the selection box 368 | automatically. 369 | 370 | "Highlighted box": indicates the choice that appears in the selection box, 371 | when choices are available. Pressing the arrow keys moves the highlighted 372 | box among choices. Horizontally grouped choices utilize the "LEFTARROW" 373 | and "RIGHTARROW" keys for movement, while vertically grouped choices are 374 | selected with the "UPARROW" and "DOWNARROW" keys. If the item is an 375 | editable item, the highlighted box, if displayed, will contain pertinent 376 | information and the edit prompt. 377 | 378 | A setting is editable if there are no choices listed in the choice band. 379 | In this case, the edit prompt appears in the selection box as a small 380 | flashing triangular field. A setting is a choice setting if there are 381 | choices listed in the choice band. 382 | 383 | To change data for an editable setting, use the "LEFTARROW" and 384 | "RIGHTARROW" keys to locate the flashing edit prompt. The following 385 | actions are possible on all data left of the prompt. 386 | 387 | 1) Press the "BACK SPACE" key to erase the rightmost character of data. 388 | 2) Press "CODE-BACK SPACE" to erase the rightmost word of data. 389 | 3) Press "CODE-SHIFT-BACK SPACE" to erase all data. 390 | 391 | Data may be inserted right of the flashing prompt by pressing the 392 | appropriate keys. Once satisfied with the settings, press "CODE-RETURN" 393 | to incorporate all settings and proceed to the next form or menu. To exit 394 | a form without accepting any new settings, press "CODE-ESC". Upon 395 | pressing "CODE-ESC", the former item settings are restored and the 396 | previous form or menu will be displayed. 397 | 398 | 399 | "3.6 Messages" 400 | 401 | There are three types of SPoC messages. 402 | 403 | 1) Prompts 404 | 2) Error messages 405 | 3) Informative messages 406 | 407 | As an aid to the user, each SPoC menu or form has prompts displayed at the 408 | bottom of the screen. Information provided by prompts will inform the 409 | user what action should be taken next. 410 | 411 | Error messages provide information for correcting erroneous user inputs. 412 | 413 | Informative messages provide status on what action is currently being 414 | taken. Informative messages require no user action. 415 | 416 | 417 | 418 | 419 | SECTION 4.0 OVERVIEW OF SPoC PROGRAMS 420 | 421 | In this section, a high level overview of SPoC software will be presented. 422 | There are five operating modes for SPoC software: InFlight, Debug, 423 | Development, SmartDemo, and DummyDemo. 424 | 425 | This document pertains only to the InFlight mode. 426 | 427 | 428 | "LAUNCH TIME UPDATE" 429 | 430 | During SPoC initialization, the actual launch Greenwich Mean Time (GMT) 431 | can be input to update the launch time expected premission. The launch 432 | time is stored in bubble memory and used to compute Mission Elapsed Time 433 | (MET). 434 | 435 | 436 | "GMT UPDATE" 437 | 438 | Current GMT can be updated in SPoC's internal clock. The internal clock 439 | is maintained by an internal battery during periods when SPoC power is 440 | OFF. 441 | 442 | 443 | "STATE VECTOR UPDATE" 444 | 445 | This program allows the user to input position and velocity vectors in the 446 | Mean of 50 (M50) coordinate system. These vectors are obtained from the 447 | GPC Memory Page and are written to bubble memory for access by other 448 | programs. 449 | 450 | 451 | "SPoC EXECUTIVE" 452 | 453 | The SPoC EXECUTIVE program displays the SPoC Main Menu from which the user 454 | may select the application desired. Upon exiting any program selected 455 | from the SPoC Main Menu, program control returns to the SPoC Main Menu. 456 | 457 | 458 | "WORLD MAP" 459 | 460 | The SPoC presently runs WORLD MAP as its primary program. A graphics 461 | display of a world map is overlaid by the Orbiter's current trajectory 462 | status. The following information/functions are available. 463 | 464 | Current MET 465 | Fixed coastline and Spaceflight Tracking and Data Network (STDN)/ 466 | Tracking and Data Relay Satellite (TDRS) coverage graphics 467 | Day and night areas on the earth's surface 468 | AOS/LOS and identification of next/current ground communication site 469 | AOS/LOS and identification of next/current TDRS coverage 470 | Current and two predicted ground tracks 471 | Current position of the Orbiter on the world map 472 | AOS of the next earth observation site 473 | AOS of future earth observation sites 474 | Current F-stop 475 | F-stop for the selected earth observation site 476 | Predicted Site Acquisition Table (PSAT) Display 477 | Table of TDRSS AOS/LOS 478 | Communication/Earth Observation site reconfiguration 479 | Latitude and longitude of the Orbiter 480 | Time to Orbiter sunrise, noon, or sunset 481 | Sun glint position on the world map 482 | Sun glint look angles 483 | Longitude and MET of the next/previous ascending node 484 | Time until/from the next/previous ascending node 485 | 486 | SECTION 5.0 BOOT UP SCREEN 487 | 488 | When SPoC is turned ON, the Boot Up Screen is displayed after several 489 | seconds. At the bottom center of this screen will be displayed the 490 | message: 491 | 492 | Boot in Progress 493 | Please Wait 494 | 495 | The contents of the rest of the screen will indicate: 496 | 497 | 1) Specific or Generic Flight Load 498 | 2) Flight or Training Load 499 | 3) Version Number 500 | 501 | After the operating system has been loaded, the Boot Up Screen will be 502 | erased. The following message will be displayed at the bottom of the 503 | screen while SPoC EXECUTIVE searches for the necessary applications. 504 | 505 | "Searching for all the necessary SPoC programs" 506 | 507 | Next, SPoC EXECUTIVE will search for necessary data files. The following 508 | message will be displayed. 509 | 510 | 511 | "Searching for all the necessary SPoC data files" 512 | 513 | 514 | Upon completion of the data file search, the LAUNCH TIME UPDATE form will 515 | be displayed. If this form does not appear, a fatal error has been 516 | detected in the current SPoC software configuration by SPoC EXECUTIVE. 517 | 518 | 519 | 520 | 521 | SECTION 6.0 LAUNCH TIME UPDATE 522 | 523 | This program allows the user to update the GMT of launch. Upon completion 524 | of the boot cycle, the LAUNCH TIME UPDATE form (FIGURE 6.1) is displayed. 525 | Initial settings displayed indicate nominal launch time. These settings 526 | can be updated by the user in the event of a launch delay. 527 | 528 | If the launch form settings are correct, press "CODE-RETURN". Otherwise, 529 | correct any erroneous data. 530 | 531 | Acceptable inputs for LAUNCH TIME UPDATE FORM: 532 | YEAR - 1983 through 1999 533 | DAY - 1 through 365 in common years, 1 through 366 in leap years 534 | HOUR - 0 through 23 535 | MINUTE - 0 through 59 536 | SECOND - 0 through 59 537 | 538 | Possible Error Messages: 539 | 1) "ERROR: Time parameter(s) input incorrectly" 540 | 541 | Problem: One or more of the settings are not within acceptable limits 542 | or are not formatted as integers. 543 | 544 | Solution: The symbol "->" will appear next to out-of-range or 545 | improperly formatted settings. Replace erroneous data with good data. 546 | 547 | 548 | 549 | 550 | SECTION 7.0 GMT UPDATE 551 | 552 | 553 | After pressing "CODE-RETURN" from the LAUNCH TIME UPDATE form, the GMT 554 | UPDATE form will automatically appear. This form can also be accessed 555 | from the SPoC Main Menu. The time displayed in this form is used to set 556 | the internal SPoC clock when "CODE-RETURN" is pressed. The GMT will have 557 | to be updated to correct internal clock drift. SPoC clock drift will 558 | average approximately five seconds per day. 559 | 560 | Acceptable inputs for GMT UPDATE form: 561 | DAY - 1 through 365 in common years, 1 through 366 in leap years 562 | HOUR - 1 through 23 563 | MINUTE - 1 through 59 564 | YEAR - 1980 through 1999 565 | 566 | Possible Error Messages: 567 | 1) "ERROR: Time parameter( s ) input incorrectly" 568 | 569 | Problem: The settings for the items listed in the error message are not 570 | within acceptable limits. 571 | 572 | Solution: The symbol "->" will appear next to out-of-range settings. 573 | Replace data that are not within acceptable limits. 574 | 575 | Possible Caution Messages: 576 | 1) "CAUTION: Vector more than 2 days old" 577 | 578 | Problem: SPoC GMT and the current SPoC state vector time tag are 579 | incompatible. The state vector time tag is two days older than 580 | current SPoC GMT. 581 | 582 | Solution: If GMT settings are incorrect, press "CODE-ESC" to 583 | reinitialize the form. Correct erroneous data. 584 | 585 | If GMT settings are correct, press "CODE-RETURN". The state 586 | vector time tag settings can be updated in the STATE VECTOR UPDATE 587 | form. 588 | 589 | 2) "CAUTION: Vector is in the future" 590 | 591 | Problem: SPoC GMT and the current SPoC state vector time tag are 592 | incompatible. The time tag for the current SPoC state vector is 593 | in the future. 594 | 595 | Solution: If GMT settings are incorrect, press "CODE-ESC" to 596 | reinitialize the form. Correct erroneous data. 597 | 598 | If GMT settings are correct, press "CODE-RETURN". The state 599 | vector time tag settings can be updated in the STATE VECTOR UPDATE 600 | form. 601 | 602 | 603 | 604 | SECTION 8.0 STATE VECTOR UPDATE 605 | 606 | The STATE VECTOR UPDATE form allows users to update the SPoC state vector. 607 | This form will automatically appear after pressing "CODE-RETURN" from the 608 | GMT UPDATE form during the SPoC initialization sequence. STATE VECTOR 609 | UPDATE can also be accessed from the SPoC Main Menu. 610 | 611 | Components of the previously input time tag and state vector are initially 612 | displayed in the STATE VECTOR UPDATE form. Prelaunch, a predicted nominal 613 | post-OMS-2 state vector is loaded into the SPoC. 614 | 615 | In OPS 2, components of the current state vector are provided by the GPCs 616 | using the GNC SPEC 34 Orbit Targeting display. Remember, values displayed 617 | on the CRT are continuously updated. Press SPEC to freeze the display. 618 | The time tag, along with position and velocity components, can now be 619 | entered into the SPoC STATE VECTOR UPDATE form. 620 | 621 | In OPS 3, components of the current state vector are provided by the GPCs 622 | using the GNC SPEC 0 GPC Memory display. SPEC 0 item entries are listed 623 | in the Reference Data Book Flight Supplement. After the six state vector 624 | components have been requested and displayed, press SPEC to freeze the 625 | display. The time tag, along with position and velocity components, can 626 | now be entered into the SPoC STATE VECTOR UPDATE form. Note: The GPC time 627 | tag displayed with the state vector may have up to a 1.8 second delta from 628 | the state vector's true time tag. This is due to differing update rates 629 | for these quantities on the GPC Memory display. 630 | 631 | When settings in the form reflect the frozen SPEC 34 (SPEC 0 in OPS 3), 632 | press "CODE-RETURN". The inclination, HA, and HP are displayed. This 633 | serves as a data check for state vector inputs. If values displayed are 634 | reasonable, press "CODE-RETURN" and the Main Menu will be displayed. 635 | 636 | If values are not reasonable, press "CODE-ESC" and the STATE VECTOR UPDATE 637 | form will be reinitialized. Correct any erroneous state vector settings 638 | and press "CODE-RETURN". Again the inclination, HA, and HP will be 639 | displayed. If the values displayed are reasonable, press "CODE-RETURN". 640 | Otherwise, press "CODE-ESC" to reinitialize the form. 641 | 642 | Acceptable inputs for STATE VECTOR UPDATE time tag: 643 | DAY (GMT) - 1 through 366 644 | HOUR (GMT) - 0 through 23 645 | MINUTE (GMT) - 0 through 59 646 | SECOND (GMT) - 0 through 59 647 | 648 | Possible error messages: 649 | 650 | 651 | 1) "ERROR: Time parameter( s ) input incorrectly" 652 | 653 | Problem: Settings for the GMT items listed in the error message are not 654 | within acceptable limits or are not formatted as integers. 655 | 656 | Solution: The symbol "->" will appear next to out-of-range settings. 657 | Replace data that are not within acceptable limits. 658 | 659 | Possible caution messages: 660 | 661 | 1) "CAUTION: VECTOR MORE THAN 2 DAYS OLD" 662 | 663 | Problem: The SPoC GMT and the current SPoC state vector time tag are 664 | incompatible. The time tag is more than two days old 665 | based on the current SPoC MET. 666 | 667 | Solution: If the state vector time tag settings are incorrect, press 668 | "CODE-ESC" to reinitialize the form. Correct erroneous data. 669 | 670 | If the state vector time tag settings are correct, press 671 | "CODE-RETURN". GMT settings can be updated in the GMT UPDATE 672 | form. 673 | 674 | 2) "VECTOR IS IN THE FUTURE" 675 | 676 | Problem: The SPoC GMT and the current SPoC state vector time tag are 677 | incompatible. The time tag is in the future based on 678 | the current SPoC MET. 679 | 680 | Solution: If the state vector time tag settings are incorrect, press 681 | "CODE-ESC" to reinitialize the form. Correct erroneous data. 682 | 683 | If the state vector time tag settings are correct, press 684 | "CODE-RETURN". GMT settings can be updated in the GMT UPDATE 685 | form. 686 | 687 | 688 | 689 | 690 | SECTION 9.0 SPoC MAIN MENU 691 | 692 | The Main Menu allows users to invoke SPoC applications. After the SPoC 693 | initialization sequence has been completed, the SPoC Main Menu will be 694 | displayed. This menu will also be displayed upon exiting any SPoC 695 | application. 696 | 697 | Once the user has executed a menu option to select an application, status 698 | messages will appear at the bottom of the screen. These messages provide 699 | status on files being loaded or any processing in progress. 700 | 701 | Possible error message: 702 | 703 | "STATE VECTOR TIME IS INCOMPATIBLE WITH GMT" 704 | 705 | Problem: SPoC current MET and the SPoC state vector MET time tag are 706 | incompatible. The time tag for the current SPoC state vector is 707 | either in the future, or two days older than the current SPoC MET. 708 | 709 | Solution: 710 | A) Press any key and return to the SPoC Main Menu. 711 | B) If the displayed MET is correct, select STATE VECTOR UPDATE 712 | from the SPoC Main Menu. Otherwise, proceed to Step D. 713 | C) Verify that state vector time tag settings are correct. 714 | 1) If time tag settings are incorrect, correct erroneous 715 | settings, press "CODE-RETURN", and return to the SPoC Main 716 | Menu. 717 | 2) If time tag settings are correct, press "CODE-ESC" to 718 | return to the SPoC Main Menu without changing form 719 | settings. 720 | 3) Proceed to Step F. 721 | D) Select SET GMT from the Main Menu. 722 | E) Verify that GMT settings are correct. 723 | 1) If GMT settings are incorrect, correct erroneous 724 | settings and return to the SPoC Main Menu. 725 | 2) If GMT settings are correct, press "CODE-ESC" to return 726 | to the SPoC Main Menu. 727 | F) Make selection from the Main Menu. 728 | 729 | SECTION 10.0 WORLD MAP 730 | 731 | 732 | SITE MANAGER Main Menu 733 | 734 | The first time WORLD MAP is selected from the SPoC Main Menu, the SITE 735 | MANAGER Main Menu will be displayed. SITE MANAGER is a WORLD MAP function 736 | which will be detailed in Section 10.4. For now, execute the first menu 737 | item "INVOKE DEFAULT COMMUNICATION SITES" and proceed to the WORLD MAP 738 | display. 739 | 740 | 741 | WORLD MAP serves as a crew aid which provides a situation display, various 742 | timers, and tables. The situation display includes a map with a longitude 743 | range from 180 degrees West to 180 degrees East, and a typical latitude 744 | range from 65 degrees North to 65 degrees South. A map with any valid 745 | latitude range can be provided by the SPoC Team upon request. 746 | 747 | 748 | 10.1 World Map Help Menu 749 | 750 | The WORLD MAP Help Menu may be invoked by pressing "CODE-?" with the WORLD 751 | MAP display active. This menu provides the "CODE-[key]" combinations 752 | associated with each WORLD MAP function. WORLD MAP functions may be 753 | invoked from the Help Menu, or may be invoked from the WORLD MAP display 754 | directly with the proper "CODE-[key]" input. To return to the WORLD MAP 755 | Display, press "CODE-ESC". 756 | 757 | 758 | 10.2 World Map Display 759 | 760 | The contents of the WORLD MAP Display are described in detail below. 761 | 762 | Following is a rough drawing of the World Map Display screen. The numbers in 763 | parentheses represent the ITEMS described in the text below. 764 | 765 | +==========================================================+ 766 | | (1) | | (2) | (3) | | (4) | 767 | |----------------------------------------------------------| 768 | | | 769 | | | 770 | | | 771 | | [Picture of earth showing day and night, | 772 | | orbital paths and current location of | 773 | | shuttle, earth-based tracking station | 774 | | locations and coverage areas, earth | 775 | | observation opportunities.] | 776 | | | 777 | | | 778 | | +-----+ | 779 | | | | | 780 | | | (10)| | 781 | |(12) | | | 782 | |----------------------------------------------------------| 783 | | (15) | | (13,16,17,18) | |(14,16,17)| 784 | +==========================================================+ 785 | 786 | 10.2.1 Current MET (Item 1) 787 | 788 | DD/HH:MM:SS fields will update approximately every second and are 789 | displayed continuously. These are calculated based on the current GMT and 790 | the GMT of launch. 791 | 792 | 10.2.2 AOS/LOS of TDRS Coverage (Item 2) 793 | 794 | The ID and countdown time to AOS or LOS of TDRS coverage is displayed in 795 | this window. If multiple satellites have overlapping coverage, the AOS 796 | countdown time to the first TDRS will be displayed. After AOS of the 797 | first TDRS, the ID and LOS of the last TDRS with overlapping coverage is 798 | displayed. "STAND BY" will be displayed in this window until AOS/LOS 799 | times have been calculated. 800 | 801 | 10.2.3 AOS/LOS of Ground Communication Site (Item 3) 802 | 803 | This window displays the ID, radio frequency band(s), and countdown time 804 | to AOS or LOS of a ground communication site. AOS and LOS are defined as 805 | an elevation of the Orbiter, viewed from the ground site, of 0.0 degrees. 806 | Neither terrain masking nor atmospheric refraction are considered in this 807 | calculation. If sites have overlapping coverage, the AOS countdown time 808 | of the first site will be displayed. After AOS of the first site, the ID 809 | and LOS of the last site in this overlapping coverage is displayed. Then 810 | the radio frequency band(s) displayed will be that of the currently 811 | acquisitioned site(s). "STAND BY" will be displayed in this window until 812 | AOS/LOS times have been calculated. 813 | 814 | 10.2.4 Spacecraft Sunrise, Noon, Sunset (Item 4) 815 | 816 | The countdown time to spacecraft sunrise ("SR"), noon ("SN"), or sunset 817 | ("SS") is displayed in this window. If the time to spacecraft 818 | sunrise/sunset or noon is greater than 100 minutes, the timer will 819 | countdown from 99:59 to 99:00 then cycle until 99:59 is the correct time. 820 | Shuttle sunrise and sunset are defined with respect to the upper limb of 821 | the sun with a fixed bias to offset the effects of refraction. Press 822 | "CODE-S" to toggle between spacecraft sunrise/sunset and noon. Spacecraft 823 | sunrise, noon, and sunset functions share this window on a mutually 824 | exclusive basis. 825 | 826 | 10.2.5 TDRS Coverage (Item 5) 827 | 828 | Limits of TDRS coverage are displayed assuming average nominal orbital 829 | altitude for a flight. 830 | 831 | 10.2.6 Earth Day/Night (Item 6) 832 | 833 | The sunlight terminator separates day/night regions on earth's surface and 834 | is updated in real time. The region in daylight is displayed with inverse 835 | video. 836 | 837 | 10.2.7 Earth Observation Area (Item 7) 838 | 839 | The flashing rectangle highlights an earth observation site. The area 840 | approximates extent of the site to be observed. A site is acquired when 841 | any part viewed from the Orbiter is within 40 degrees of the current 842 | nadir. The next available site will initially be displayed. Press 843 | "CODE-F" to move forward one available site at a time until the last 844 | predicted ground track point is encountered. To return to the next 845 | available site, press "CODE-R". The displayed site is shown until 846 | acquired, then the next site is highlighted with a flashing rectangle. 847 | 848 | 10.2.8 Ground Communication Sites (Item 8) 849 | 850 | Limits of selected ground communication sites, with terrain masking, are 851 | displayed assuming average nominal orbital altitude for a flight. 852 | 853 | 10.2.9 Shuttle Bug (Item 9) 854 | 855 | The nose of the flashing Shuttle Bug indicates current position of the 856 | Orbiter. Every thirty seconds, the Shuttle Bug's position is updated to 857 | the next predicted ground track point. 858 | 859 | 10.2.10 Enlarged F-Stop Display (Item 10) 860 | 861 | For ease of viewing, the current camera F-Stop is enlarged and displayed. 862 | This is the same camera F-Stop value described in Item 13. The enlarged 863 | F-Stop display may be toggled ON or OFF by pressing "CODE-CTRL-SHIFT-F". 864 | For high inclination orbits, position of the enlarged F-Stop display will 865 | vary slightly. This is done to avoid display conflicts with predicted 866 | ground tracks and the Shuttle Bug. 867 | 868 | 10.2.11 Current and Two Predicted Ground Tracks (Item 11) 869 | 870 | Predicted ground tracks are updated when the Shuttle Bug reaches the 871 | predicted ground track point 5400 seconds (90 minutes) from the first. 872 | The Shuttle Bug then occupies the first ground track point in a series 873 | extending 4.5 hours into the future. Adjacent ground track points are 874 | separated in time by 30 seconds. 875 | 876 | 10.2.12 Tone Indicator (Item 12) 877 | 878 | "ON" indicates a tone will be generated when the currently displayed earth 879 | observation site countdown timer reaches two minutes. "OFF" indicates no 880 | tone will be generated. The default setting is "ON". The tone indicator 881 | may be toggled "ON" and "OFF" by pressing "CODE-T". 882 | 883 | 10.2.13 Latitude, Longitude, and Current F-Stop (Item 13) 884 | 885 | The Orbiter's current latitude, longitude, and the camera F-Stop required 886 | for an average albedo target at the current spacecraft nadir are updated 887 | once every 30 seconds. "CODE-L" immediately updates this display and 888 | toggles it from dynamic to frozen. While frozen, the display will flash 889 | approximately once/second. This display window is shared, on a mutually 890 | exclusive basis, with items 16, 17, and 18. 891 | 892 | 10.2.14 Ascending Node Time (Item 14) 893 | 894 | This window displays elapsed time since previous ascending node or 895 | countdown to the next ascending node. The display is controlled in 896 | conjunction with items 16 and 17. 897 | 898 | 10.2.15 Earth Observation Site (Item 15) 899 | 900 | The site ID is displayed along with the countdown time to acquisition of 901 | the displayed earth observation site. The program searches for 902 | acquisition only. Once acquisition is achieved, the program will search 903 | for acquisition of the next available site. If no earth observation site 904 | has been found within the predicted ground tracks, "***** XX:XX" will be 905 | displayed. The F-Stop for this site is also displayed. This F-Stop is 906 | based on a predetermined albedo for the current site, a set film and 907 | shutter speed, and the computed sun angle. Since F-Stop values are 908 | computed in discrete 1/2 F-Stop steps, a difference of 1/2 F-Stop between 909 | the SPoC value and a premission value is not unusual. 910 | 911 | SPoC observation site F-Stops are computed for acquisition, but the 912 | premission albedos consider an average across the entire site. For sites 913 | with significant physical size, this can result in F-Stop differences of 914 | as much as 1 and 1/2 to 2 full F-Stops in extreme cases. 915 | 916 | 10.2.16 Longitude, MET, and Countdown Timer For Next Ascending Node (Item 917 | 16) 918 | 919 | A keyboard input of "CODE-N" will display the longitude and MET of the 920 | next ascending node in the bottom center window, replacing any data 921 | previously displayed there. Also the countdown time for this node will be 922 | displayed in the Ascending Node Time window (Item 14). This function 923 | shares the bottom middle window, on a mutually exclusive basis, with Items 924 | 13, 17, and 18. 925 | 926 | 10.2.17 Longitude, MET, and Time Since Previous Ascending Node (Item 17) 927 | 928 | A keyboard input of "CODE-CTRL-SHIFT-N" will display the longitude and MET 929 | of the previous ascending node in the bottom center window, replacing any 930 | data previously displayed there. Elapsed time since the previous 931 | ascending node will also be displayed in the Ascending Node Time window 932 | (Item 14). This function shares the bottom middle window, on a mutually 933 | exclusive basis, with Items 13, 16, and 18. 934 | 935 | 10.2.18 Sun Glint Angle and Azimuth (Item 18) 936 | 937 | A keyboard input of "CODE-G" will display the sun glintpoint 938 | angle-of-reflection and azimuth relative to the Orbiter. These data are 939 | displayed in the bottom center window, replacing any data previously 940 | displayed there. "GLINT ANGL" is the angle-of-reflection of the sun's 941 | image off the Earth's surface. "AZ" is the angle measured from the 942 | vehicle true heading in the Orbiter local horizontal plane to the 943 | glintpoint azimuth and accumulated in the direction "east of north". In 944 | other words, the difference "true azimuth of the sun glintpoint minus 945 | current Orbiter true heading" is "AZ". Sun glint data are displayed only 946 | if the "GLINT ANGL" is between 9.99 degrees and 80.21 degrees. Otherwise, 947 | Xs are displayed in place of the data. This function shares the bottom 948 | middle window, on a mutually exclusive basis, with Items 13, 16, and 17. 949 | 950 | 10.2.19 Sun Glintpoint Area (Item 18a) 951 | 952 | A "CODE-G" keyboard input will also graphically display the sun glintpoint 953 | relative to the Shuttle by flashing a small square on the WORLD MAP. 954 | 955 | 956 | 10.3 PSAT 957 | 958 | A Predicted Site Acquisition Table (PSAT) is available for the current and 959 | two predicted ground tracks. Press "CODE-P" to call up the PSAT Display. 960 | There are two windows for this display. The upper window displays TDRS 961 | data, while the lower window displays ground site data. Each window has a 962 | light bar which serves as an aid for reading data across a row. Press 963 | "UPARROW" and "DOWNARROW" to control light bar movement in the lower 964 | window. Press "SHIFT-UPARROW" and "SHIFT-DOWNARROW" to control light bar 965 | movement in the upper window. 966 | 967 | If there are more lines of data than can be displayed in a PSAT window at 968 | one time, only sites with LOS in the future will be visible when the 969 | display appears. Users may scroll up or down to view data not currently 970 | in the window. Small up/down arrows indicate if more data are available. 971 | Users may scroll in the direction of the arrows to view the additional 972 | data. When the bottom or top of the table is reached, the appropriate 973 | arrow will vanish. 974 | 975 | "More Data Arrows": Indicate that more data are available above or below 976 | those currently visible. 977 | 978 | "LOS Indicators": Indicate the site has an LOS in the past. 979 | 980 | "Light Bar": Visual aid in reading across a row. May be moved with the 981 | arrow keys as described above. 982 | 983 | "XX/XX:XX:XX XX:XX": Indicates the data are not currently available. 984 | 985 | To return to the WORLD MAP Display, press "CODE-ESC" 986 | 987 | 988 | 10.4 SITE MANAGER 989 | 990 | SITE MANAGER allows users to: 991 | 992 | * 1) Turn communication sites ON or OFF. 993 | * 2) Add/edit communications site data. 994 | * 3) Delete user input communications sites. 995 | * 4) Add/edit earth observation site data. 996 | * 5) Delete user input earth observation sites. 997 | 998 | 999 | On the first call to WORLD MAP from the SPoC Main Menu, the SITE MANAGER 1000 | Main Menu will be displayed. During subsequent calls to WORLD MAP, 1001 | control will pass directly to the WORLD MAP Display. SITE MANAGER may 1002 | also be invoked from the WORLD MAP Help Menu or by pressing "CODE-E" from 1003 | the WORLD MAP Display. 1004 | 1005 | The SITE MANAGER Main Menu is displayed on the first call to WORLD MAP as 1006 | a reminder that the previous user may have reconfigured communication or 1007 | earth observation sites. This allows users easy access to verify 1008 | configuration of the sites. 1009 | 1010 | If a communication site is ON, the site will be included in AOS/LOS 1011 | searches. If it is OFF, the site will not be included in AOS/LOS 1012 | searches. The AOS/LOS search drives the WORLD MAP AOS/LOS countdown 1013 | windows and PSAT Display. SPoC premission site data cannot be altered or 1014 | deleted by users. Only user input site data may be altered or deleted by 1015 | users. 1016 | 1017 | 10.4.1 SITE MANAGER Exit Options 1018 | 1019 | Three options on the SITE MANAGER Main Menu will exit SITE MANAGER and 1020 | proceed to the WORLD MAP program. 1021 | 1022 | 10.4.1.1 CODE-D INVOKE DEFAULT COMMUNICATION SITES 1023 | 1024 | The communication site list will revert to the premission default 1025 | configuration. Any user input sites marked for deletion will be deleted. 1026 | All other sites, including user input sites, will be turned OFF. SITE 1027 | MANAGER is exited and the WORLD MAP Display appears. 1028 | 1029 | 10.4.1.2 CODE-S SAVE CHANGES PROCEED TO DAYMAP 1030 | 1031 | Any changes made during this SITE MANAGER session will be saved. User 1032 | input sites marked for deletion will be deleted. SITE MANAGER is exited 1033 | and the WORLD MAP Display appears. 1034 | 1035 | 10.4.1.3 CODE-ESC NO CHANGES PROCEED TO DAYMAP 1036 | 1037 | Any changes made during this SITE MANAGER session will be ignored. SITE 1038 | MANAGER is exited and the WORLD MAP Display appears. "NOTE": If changes 1039 | were made, users will be warned with the following message: 1040 | 1041 | "PRESS CODE-RETURN TO EXIT SITE MANAGER WITHOUT SAVING CHANGES" 1042 | "PRESS CODE-ESC TO RETURN TO SITE MANAGER" 1043 | 1044 | This prevents users from inadvertently losing any changes that may have 1045 | been made during this SITE MANAGER session. 1046 | 1047 | 1048 | 10.4.2 SITE MANAGER Functions 1049 | 1050 | 10.4.2.1 CODE-N SELECT COMMUNICATION NETWORK 1051 | 1052 | This option displays the Network form which allows users to configure 1053 | entire communication networks "ON" or "OFF". If "ON" is selected, all 1054 | communications sites in that network will be turned "ON". Otherwise, all 1055 | sites for that network will be turned "OFF". 1056 | 1057 | 1058 | 10.4.2.2 CODE-I SELECT INDIVIDUAL COMMUNICATION SITES 1059 | 1060 | This option displays the Communication Site Selection form. Users may 1061 | configure each communication site "ON" or "OFF". Sites configured 1062 | premission as "ON" are indicated by "DEF" (default) in the fourth column 1063 | from the left. Sites are grouped by site type in alphabetical order. 1064 | TDRS satellites are at the top of the form, followed by STDN and Remote 1065 | Tracking Station (RTS) sites. If any user input sites have been added, 1066 | they will appear at the bottom of the form. 1067 | 1068 | 10.4.2.3 CODE-P ADD COMMUNICATION SITE 1069 | 1070 | This option allows users to add or edit user input site data. Site data 1071 | loaded premission can not be altered by users. Only user input site data 1072 | may be altered. 1073 | 1074 | The Site ID form appears after "CODE-P" is pressed. A site name composed 1075 | of three alpha characters is the first item to be entered on this form. 1076 | In the following examples, "ABC" will be used as the site name. The 1077 | characters entered may be either upper or lower case. 1078 | 1079 | The second Site ID form item allows users to select whether inputs pertain 1080 | to a ground site or TDRS. 1081 | 1082 | Acceptable inputs for the Site ID form: 1083 | 1084 | * Site Name : Exactly three alphabetic characters. 1085 | 1086 | Possible error messages: 1087 | 1088 | * 1) "IMPROPER COMMUNICATION SITE ID (REENTER ID)" 1089 | 1090 | * Problem: Three alphabetic characters were not entered for the site ID. 1091 | 1092 | * Solution: Enter three alphabetic characters. 1093 | 1094 | * 2) "DUPLICATE SITE ID" 1095 | * "IMPROPER COMMUNICATION SITE ID (REENTER ID)" 1096 | 1097 | * Problem: The site ID entered was used for a premission site. 1098 | 1099 | * Solution: Use a different site ID for the input site. 1100 | 1101 | 10.4.2.3.1 Adding a Ground Communications Site 1102 | 1103 | If "GROUND SITE" was selected from the Site ID form, the Site Data form 1104 | will appear. At the top of the form, "ENTERING ABC DATA" is displayed. 1105 | Also notice that the latitude and longitude settings are blank. Enter the 1106 | latitude and longitude (in decimal degrees). 1107 | 1108 | Select the correct frequency band for this input site with the "LEFTARROW" 1109 | and "RIGHTARROW" keys. 1110 | 1111 | 10.4.2.3.2 Adding a TDRS 1112 | 1113 | If "TDRSS" was selected from the Site ID form, the Site Data form will 1114 | appear as shown in. At the top of the form, "ENTERING ABC DATA" is 1115 | displayed. Notice that the longitude setting is blank. Enter the 1116 | longitude (in decimal degrees). 1117 | 1118 | 10.4.2.3.3 Editing User Input Ground Site Data 1119 | 1120 | If a site has previously been input and "GROUND SITE" was selected from 1121 | the Site ID form, the Site Data form will appear as shown in. At the top 1122 | of the form, "EDITING ABC DATA" is displayed. The form will display site 1123 | data for editing. 1124 | 1125 | 10.4.2.3.4 Editing User Input TDRS Data 1126 | 1127 | If a TDRS has previously been input and "TDRSS" was selected from the Site 1128 | ID form, the Site Data form will appear. At the top of the form, "EDITING 1129 | ABC DATA" is displayed. The TDRS longitude may then be updated. 1130 | 1131 | Acceptable inputs for the Site Data forms: 1132 | * Latitude: -90 through +90 (ground sites only) 1133 | * Longitude: -180 through +360 1134 | 1135 | Possible error messages: 1136 | * 1) "IMPROPER LONGITUDE ( REENTER LONGITUDE )" 1137 | * "IMPROPER LATITUDE ( REENTER LATITUDE )" 1138 | 1139 | * Problem: The inputs are out of range. 1140 | 1141 | * Solution: Correct erroneous inputs. 1142 | 1143 | 10.4.2.4 CODE-X DELETE COMMUNICATION SITES 1144 | 1145 | Only user input communication sites may be deleted. To mark one or more 1146 | sites for deletion, select "CODE-X DELETE COMMUNICATION SITES" from the 1147 | SITE MANAGER Main Menu. If there are currently any user input sites, the 1148 | Communication Site Deletion form will appear. If there are currently no 1149 | user input sites, this message will be displayed: 1150 | 1151 | 1152 | "THERE ARE NO "INPUT" SITES TO DELETE 1153 | PRESS ANY KEY TO CONTINUE 1154 | COMMUNICATION SITES" 1155 | 1156 | 1157 | Communication Sites Deletion Form 1158 | 1159 | Note that sites marked for deletion on this form will only be purged from 1160 | bubble memory when "CODE-D" or "CODE-S" is selected from the SITE MANAGER 1161 | Main Menu. Users may return to the Communication Site Deletion form and 1162 | mark or unmark sites for deletion on multiple occasions before they are 1163 | purged. 1164 | 1165 | User input sites marked for deletion will be accompanied by an asterisk 1166 | when displayed in the Site Selection form. 1167 | 1168 | 1169 | 1170 | 10.4.2.5 CODE-CTRL-SHIFT-P ADD EARTH OBSERVATION SITE 1171 | 1172 | This option allows users to add or edit a user input earth observation 1173 | site. All user input earth observation sites are point sites. A point 1174 | site is one point on the earth's surface defined by its latitude and 1175 | longitude. Sites that are loaded premission cannot be altered by users. 1176 | Only user input site data may be altered. 1177 | 1178 | To add or edit earth observation site data, select "CODE-CTRL-SHIFT-P 1179 | ADD EARTH OBSERVATION SITE" from the SITE MANAGER Main Menu. The 1180 | Observation Site ID form will be displayed. For the following examples, 1181 | "T104B" will be used as the site name. 1182 | 1183 | 1184 | After pressing "CODE-RETURN" in the Observation Site ID form, the 1185 | Observation Site Data form will appear. The format of the Observation 1186 | Site Data form will vary based on the inputs into the Observation Site ID 1187 | form. 1188 | 1189 | Acceptable inputs for the Observation Site ID form: 1190 | * Site Name : Maximum of five alpha-numeric characters. 1191 | 1192 | Possible error messages: 1193 | * 1) "IMPROPER EARTH OBSERVATION SITE ID (REENTER ID)" 1194 | 1195 | * Problem: Improper site name was entered. 1196 | 1197 | * Solution: Reenter site name. 1198 | 1199 | * 2) "DUPLICATE SITE NAME" 1200 | * "IMPROPER EARTH OBSERVATION SITE ID (REENTER ID)" 1201 | 1202 | * Problem: The site name entered was used for a premission site. 1203 | 1204 | * Solution: Use a different site name for the input site. 1205 | 1206 | 1207 | 10.4.2.5.1 Adding An Earth Observation Site 1208 | 1209 | If this is a new site to be added, "ENTERING T104B DATA" is displayed at 1210 | the top of the Observation Site Data form, indicating that data for the 1211 | new site "T104B" are being entered. Since this is a new site, the form 1212 | settings are blank. Enter the setting for each item. 1213 | 1214 | 10.4.2.5.2 Editing User Input Earth Observation Site Data 1215 | 1216 | If the site name entered into the Site ID form has previously been added, 1217 | the Observation Site Data form will be displayed with "EDITING T104B DATA" 1218 | at the top of the form. The data for this site will be displayed in the 1219 | form. Edit the necessary settings. 1220 | 1221 | Acceptable inputs for the Site Data form: 1222 | * Latitude: -90 through +90 1223 | * Longitude: -180 through +360 1224 | * Albedo: 6 through 18 1225 | 1226 | Possible error messages: 1227 | * 1) "IMPROPER LONGITUDE ( REENTER LONGITUDE )" 1228 | * "IMPROPER LATITUDE ( REENTER LATITUDE )" 1229 | * "IMPROPER ALBEDO (REENTER ALBEDO)" 1230 | 1231 | * Problem: The inputs are out of range. 1232 | 1233 | * Solution: Correct erroneous inputs. 1234 | 1235 | 10.4.2.6 CODE-CTRL-SHIFT-X DELETE EARTH OBSERVATION SITES 1236 | 1237 | Only user input earth observation sites may be deleted. To mark one or 1238 | more sites for deletion select "CODE-CTRL-SHIFT-X DELETE EARTH 1239 | OBSERVATION SITES" from the SITE MANAGER Main Menu. If there are 1240 | currently any user input sites, the Observation Site Deletion form will 1241 | appear. If there are currently no user input sites, this message will be 1242 | displayed: 1243 | 1244 | 1245 | "THERE ARE NO "INPUT" SITES TO DELETE 1246 | 1247 | PRESS ANY KEY TO CONTINUE 1248 | OBSERVATION SITES" 1249 | 1250 | 1251 | Note that sites marked for deletion on this form will only be purged from 1252 | bubble memory when "CODE-D" or "CODE-S" is selected from the SITE MANAGER 1253 | Main Menu. Users may return to the Earth Observation Site Deletion form 1254 | and mark or unmark sites for deletion on multiple occasions before they 1255 | are purged. 1256 | 1257 | 1258 | 1259 | 1260 | APPENDIX A--INITIALIZING THE SPoC 1261 | 1262 | 1263 | The following set of instructions leads a user through the procedures to 1264 | initialize the SPoC. After SPoC initialization is completed, the user may 1265 | proceed to APPENDIX B (WORLD MAP), C (DEORBIT), or D (CGMANAGER) for a 1266 | demonstration of SPoC applications. Familiarity with basic SPoC operation 1267 | is assumed. For the user unfamiliar with the SPoC, hardware setup 1268 | procedures for ground operation are found in Section 2.2. Details of 1269 | basic SPoC operations are contained in Section 3. 1270 | 1271 | When the SPoC is turned on, the Boot Up Screen is displayed after several 1272 | seconds. After the operating system has been loaded, the Boot Up Screen 1273 | will be erased. 1274 | 1275 | Messages will then be displayed informing users that the SPoC EXECUTIVE is 1276 | searching for programs and data files. 1277 | 1278 | Upon completion of the file search, the first initialization form will be 1279 | displayed (LAUNCH TIME UPDATE form). For this demo, follow the steps 1280 | below to enter the launch date/time, the current SGMT, and state vector. 1281 | 1282 | "LAUNCH TIME UPDATE Form" 1283 | 1284 | 1) Press "CODE-BACK SPACE" to erase old data. 1285 | YEAR: enter "1988" 1286 | press "RETURN". 1287 | 1288 | 2) Press "CODE-BACK SPACE" to erase old data. 1289 | DAY: enter "300" 1290 | press "RETURN". 1291 | 1292 | 3) Press "CODE-BACK SPACE" to erase old data. 1293 | HOUR: enter "0" 1294 | press "RETURN". 1295 | 1296 | 4) Press "CODE-BACK SPACE" to erase old data. 1297 | MINUTE: enter "0" 1298 | press "RETURN". 1299 | 1300 | 5) Press "CODE-BACK SPACE" to erase old data. 1301 | SECOND: enter "0" 1302 | press "CODE-RETURN". 1303 | 1304 | "GMT UPDATE Form" 1305 | 1306 | 6) Press "CODE-BACK SPACE" to erase old data. 1307 | DAY (GMT): enter "300" 1308 | press "RETURN". 1309 | 1310 | 7) Press "CODE-BACK SPACE" to erase old data. 1311 | HOUR (GMT): enter "0" 1312 | press "RETURN". 1313 | 1314 | 1315 | 8) Press "CODE-BACK SPACE" to erase old data. 1316 | MINUTE (GMT): enter "0" 1317 | press "RETURN". 1318 | 1319 | 9) Press "CODE-BACK SPACE" to erase old data. 1320 | YEAR: enter "1988" 1321 | press "CODE-RETURN". 1322 | 1323 | "NOTE:" If a warning message appears at this point, correct bad data and 1324 | press "CODE-RETURN". 1325 | 1326 | "STATE VECTOR UPDATE Form" 1327 | 1328 | 10) Press "CODE-BACK SPACE" to erase old data. 1329 | DAY (GMT): enter "300" 1330 | press "RETURN". 1331 | 1332 | 11) Press "CODE-BACK SPACE" to erase old data. 1333 | HOUR (GMT): enter "0" 1334 | press "RETURN". 1335 | 1336 | 12) Press "CODE-BACK SPACE" to erase old data. 1337 | MINUTE (GMT): enter "0" 1338 | press "RETURN". 1339 | 1340 | 13) Press "CODE-BACK SPACE" to erase old data. 1341 | SECOND (GMT): enter "0" 1342 | press "RETURN". 1343 | 1344 | 14) Press "CODE-BACK SPACE" to erase old data. 1345 | X POSITION (KFt): enter "-4065.5451" 1346 | press "RETURN". 1347 | 1348 | 15) Press "CODE-BACK SPACE" to erase old data. 1349 | Y POSITION (KFt): enter "19478.6516" 1350 | press "RETURN". 1351 | 1352 | 16) Press "CODE-BACK SPACE" to erase old data. 1353 | Z POSITION (KFt): enter "-9134.2843" 1354 | press "RETURN". 1355 | 1356 | 17) Press "CODE-BACK SPACE" to erase old data. 1357 | X VELOCITY (KFt/SEC): enter "-23.4998543" 1358 | press "RETURN". 1359 | 1360 | 18) Press "CODE-BACK SPACE" to erase old data. 1361 | Y VELOCITY (KFt/SEC): enter "-7.6119311" 1362 | press "RETURN". 1363 | 1364 | 19) Press "CODE-BACK SPACE" to erase old data. 1365 | Z VELOCITY (KFt/SEC): enter "-5.7686384" 1366 | press "CODE-RETURN". 1367 | 1368 | At the bottom of the screen the inclination, HA, and HP are displayed. 1369 | This serves as a data check for state vector inputs. For the above 1370 | inputs, the following values will be displayed. 1371 | 1372 | INCLINATION = 28.518 1373 | APPROX. ORBIT : HA=166; HP=159 1374 | 1375 | 1376 | 20) Press "CODE-RETURN". 1377 | 1378 | The SPoC Main Menu will now be displayed. The user may select SPoC 1379 | applications for execution. Step-by-step demos are available for WORLD 1380 | MAP (Appendix B), DEORBIT (Appendix C), and CGMANAGER (Appendix D). The 1381 | STATE VECTOR UPDATE and SET GMT programs are also available from the SPoC 1382 | Main Menu, and were demonstated during the initialization procedures. 1383 | 1384 | You are now ready to proceed to a SPoC demo of your choice. 1385 | 1386 | 1387 | APPENDIX B--WORLD MAP DEMONSTRATION 1388 | 1389 | 1390 | 1391 | Before exercising WORLD MAP demonstration procedures, the user should 1392 | complete procedures outlined in APPENDIX A (Initializing The SPoC). The 1393 | SPoC Main Menu should be currently displayed. The following instructions 1394 | will lead the user through a WORLD MAP demo. 1395 | 1396 | 1) Select "DISPLAY WORLD MAP" from the SPoC Main Menu. 1397 | 1398 | The first time WORLD MAP is selected from the SPoC Main Menu, the SITE 1399 | MANAGER Main Menu will be displayed. SITE MANAGER is a WORLD MAP function 1400 | which may be exercised later during this demo. For now, continue on to 1401 | the WORLD MAP display. 1402 | 1403 | 2) Select "INVOKE DEFAULT COMMUNICATION SITES" from the SITE MANAGER Main 1404 | Menu. 1405 | 1406 | After a few seconds, the WORLD MAP Display will appear. Notice that the 1407 | communication site AOS/LOS windows display the words "STAND BY". 1408 | 1409 | As soon as the AOS/LOS search has been completed, windows will display 1410 | AOS/LOS countdown times. 1411 | 1412 | 3) Press "CODE-?" to display the WORLD MAP Help Menu. 1413 | 1414 | This menu provides the "CODE-[key]" combinations associated with each 1415 | WORLD MAP function. WORLD MAP functions may be invoked from the Help 1416 | Menu. They may be invoked from the WORLD MAP display directly with the 1417 | proper "CODE-[key]" input. 1418 | 1419 | 4) To return to the WORLD MAP Display, press "CODE-ESC". 1420 | 1421 | At this time, you may want to explore various WORLD MAP functions. For a 1422 | detailed explanation of each WORLD MAP function, refer to Section 10.2. 1423 | Section 10.3 details the PSAT Display, and Section 10.4 details SITE 1424 | MANAGER functions. 1425 | 1426 | 5) When you are ready to exit WORLD MAP and return to the SPoC Main Menu, 1427 | press "CODE-ESC". 1428 | 1429 | 1430 | 1431 | 1432 | APPENDIX E--SPoC HISTORY 1433 | 1434 | 1435 | 1436 | The concept of an independent computational capability aboard the Shuttle 1437 | has been operational since STS-1. Originally, an HP41 calculator was 1438 | employed for this purpose. Data storage and manipulation capabilities, 1439 | absent from the GPC's because of core storage limitations, were provided 1440 | by this hand-held calculator. Also provided by the HP41 were capabilities 1441 | similar to existing ground-based processors in the event that the Shuttle 1442 | and crew were in a no-communication situation. As of April 5, 1983 the 1443 | HP41 flight programs included the following: 1444 | 1445 | 1446 | a) The CG program allowed the crew to track current X and Y-CG location as 1447 | a function of MET, OMS, and RCS propellant loadings, and whether payloads 1448 | were berthed or deployed. 1449 | 1450 | 1451 | b) The AOS program supplied the crew with information concerning the next 1452 | time the spacecraft would acquire a communications site. 1453 | 1454 | 1455 | c) The LANDTRACK program provided observation pass information for any 1456 | stored earth observation site. 1457 | 1458 | 1459 | d) The DEORBIT program provided the crew with deorbit maneuver targets in 1460 | the event of total loss of communications with the ground and a 1461 | time-critical systems failure requiring an emergency deorbit. 1462 | 1463 | 1464 | e) The ORBIT program provided the crew with data concerning attitudes and 1465 | rates involved in the star sighting function and with orbit sunrise and 1466 | sunset. 1467 | 1468 | 1469 | f) The ALARM program gave the crew a personalized reminder of upcoming 1470 | events of particular interest by having the calculator sound a tone and 1471 | display a pre-stored message. 1472 | 1473 | 1474 | g) The LANDING program computed data necessary for the approach and 1475 | landing phase of flight. 1476 | 1477 | 1478 | Although the HP41 has proven to be a useful tool, it has a very limited 1479 | memory capacity (only one of the above programs can be stored in memory at 1480 | a time), very limited text displays, and there is no graphics capability. 1481 | 1482 | As new requirements developed for independent computational capabilities 1483 | aboard the Shuttle, the HP41 became inadequate for the task. To augment 1484 | the hand-held calculator, the SPoC was introduced. SPoC is an expansion 1485 | of the HP41 calculator concept and enhances independent computation and 1486 | display capabilities by providing more memory, more mass storage, and 1487 | graphic displays. In 1983, the Ascent/Entry Procedures Section of the 1488 | Operations Branch began evaluating microcomputers for onboard 1489 | implementation. After evaluating several machines, a GRiD microcomputer 1490 | was selected because it met the hardware and software requirements and 1491 | constraints fully. A proposal was made to the Government Furnished 1492 | Equipment (GFE) Configuration Control Board (CCB) to obtain the necessary 1493 | funding for the project. The GFE CCB denied the request. To gain 1494 | necessary support for the project, presentations were made at the branch, 1495 | division, and directorate levels. After a SPoC presentation was made to 1496 | the Program Office Manager, Glynn Lunny, approval for the SPoC project was 1497 | given. Proposals were again made to the GFE CCB, and on 08/15/83 a Crew 1498 | Related GFE CCB Directive (#3D149) was issued authorizing purchase, 1499 | testing, certification, and preparation for flight of a GRiD Compass 1500 | Computer on STS-9. 1501 | 1502 | Purchased commercially and modified, the original SPoC was a GRiD Compass 1503 | 1101 lap top computer. The Compass 1101 has a 4.75 by 3.5 inch 1504 | electroluminescent screen, 384K bytes of non-volatile bubble memory and 1505 | 256K bytes of RAM. Modifications included replacing the internal modem 1506 | with a fan for cooling, since the standard Model 1101 computer uses 1507 | convective cooling. The lithium battery circuit, which provides power for 1508 | the internal clock while the Compass is not connected to an external power 1509 | supply, had supplemental diodes and a fuse installed to insure failsafe 1510 | operation. A power cable was designed for Orbiter power connector 1511 | compatibility. EMI tests showed the SPoC was out of specification. Since 1512 | the out-of-spec condition for SPoC would cause no problems for Orbiter 1513 | systems, communications, or payloads, the Space Shuttle Program 1514 | Requirements Control Board issued a directive (#S23562) to authorize a 1515 | waiver permitting the radiated EMI out-of-spec condition. 1516 | 1517 | SPoC was initially flown on STS-9 as a proof of concept engineering 1518 | evaluation. During this flight, it proved useful as an aid to crew 1519 | awareness and productivity. SPoC flight software for STS-9 included 1520 | programs that calculated and/or displayed the following data: 1521 | 1522 | MET 1523 | The world map (facsimile of the MCC world map) 1524 | Day and night areas on the earth's surface 1525 | AOS/LOS ID of the current/next ground communication site 1526 | AOS/LOS and ID of current/next TDRSS coverage 1527 | Current and two predicted ground tracks 1528 | Current position of the Orbiter on the world map 1529 | AOS of the next earth observation site 1530 | 1531 | Brewster Shaw, pilot for STS-9, stated "It's really a big asset to know 1532 | where we are all the time." Since SPoC was such an asset on STS-9, Flight 1533 | Equipment Project Office Configuration Control Board Directive #G1309 1534 | authorized one SPoC and power cord be manifested for STS-11 and subsequent 1535 | missions. 1536 | 1537 | An upgrade occurred in late 1984, with the Compass 1129 replacing the 1101 1538 | for STS-51C and subsequent missions. The GRiD Compass 1129 is the same 1539 | size as the 1101, with a 4.75 by 3.5 inch electroluminescent screen and 1540 | 384K bytes of non-volatile bubble memory. Improvements gained with the 1541 | 1129 include twice as much RAM (512K bytes) and four accessible slots for 1542 | PROM or EPROM chips. At this time, the necessary hardware and software 1543 | were purchased to develop EPROMs for flight. Use of socketed PROM and 1544 | EPROM chips was viewed as a possible interim solution for expanded mass 1545 | memory until a mass memory device was certified for flight. Compass 1129s 1546 | were purchased commercially and modified. The internal modem was replaced 1547 | with a fan for cooling and an EMI reducing "Tempest" screen was installed. 1548 | For crew safety, the lithium battery which provided power for the internal 1549 | clock was exchanged for a replaceable silver oxide battery and a clock 1550 | reset circuit. Also the foot was milled out to promote internal 1551 | ventilation while in the closed position for flight operation. 1552 | 1553 | In 1985, the SPoC was upgraded to a GRiD Compass 1139 for STS-51G and 1554 | subsequent missions. The GRiD Compass 1139 is similar to the 1129, having 1555 | the same memory capacity. It is an improvement over the 1129 because it 1556 | has a larger electroluminescent screen (7.5 by 3.5 inches) and a standard 1557 | internal fan for cooling. Like the 1129, this unit was purchased 1558 | commercially and modified for flight. Modifications include an 1559 | EMI-reducing "Tempest" screen, a replaceable silver oxide battery, a clock 1560 | reset circuit, a milled out foot, and the modem is removed. 1561 | 1562 | The original flight software configuration has been augmented since STS-9 1563 | to satisfy expanding functional requirements levied on the SPoC. The 1564 | flight software configuration now includes programs that calculate and/or 1565 | display the following data: 1566 | 1567 | Predicted Site Acquisition Table 1568 | Table of TDRSS AOS/LOS 1569 | Communication/Earth Obs site reconfiguration 1570 | Latitude and longitude of the Orbiter 1571 | AOS of future earth observation sites 1572 | Time to Orbiter sunrise, noon, sunset 1573 | Current F stop 1574 | F stop for the selected earth observation site 1575 | Sun glint position on the world map 1576 | Sun glint look angles 1577 | Longitude and MET of the next/previous ascending node 1578 | Time until/from the next/previous ascending node 1579 | Deorbit opportunities 1580 | Deorbit maneuver targeting 1581 | Orbiter CG and weight 1582 | CG management procedures 1583 | 1584 | The SPoC has also been used to provide computational support for special 1585 | purpose applications on a flight-specific basis. The Orbital Refueling 1586 | System (ORS) and the Gravity Gradient Free Drift experiments set a 1587 | precedent for using microprocessors to support payload experiments. 1588 | 1589 | Since 41-G, two SPoCs have been manifested for each Shuttle mission. The 1590 | primary unit is usually positioned on the forward flight deck above the 1591 | eyebrow panel, while the backup nominally supports middeck operations. 1592 | Even during emergency power-downs, one of these units remains running. 1593 | 1594 | 1595 | "NONCRITICAL BUT MANDATORY" 1596 | 1597 | Although the SPoC was classified as noncritical hardware by Configuration 1598 | Control Board Directive 1253, it is considered mandatory equipment. If 1599 | the SPoC fails, neither the crew nor the mission is threatened: thus the 1600 | noncritical classification. However, the SPoC is such an asset to the 1601 | crew and to MCC that it is mandatory equipment for flight. 1602 | 1603 | The following excerpts from reports and memos illustrate the importance of 1604 | the SPoC to Shuttle missions. 1605 | 1606 | "STS-9 Flight Crew Report" (Dec. 1983): "The SPoC proved to be a great 1607 | asset. It was unstowed and set up during the post insertion timeframe and 1608 | remained active until deorbit prep... The SPoC allowed the crew to see 1609 | where they were at all times and served as an accurate source of 1610 | communications coverage information. In light of the many dropouts of 1611 | TDRSS S-Band signal that were experienced, the SPoC AOS/LOS information 1612 | allowed the crew to manage the comm system in an efficient manner and 1613 | eliminated unnecessary trouble shooting. The SPoC appears to have great 1614 | potential that deserves further development for future Shuttle missions." 1615 | 1616 | "Memo from the Space Shuttle Earth Observations Project Manager" 1617 | (03/02/84, #SC5-84-32): "The GRiD SPoC has been of great value to the 1618 | Space Shuttle Earth Observations Project... Our contact with the crews 1619 | that have used the SPoC ...reflect extreme interest in its present 1620 | capabilities and proposed updates." 1621 | 1622 | The value of the SPoC in monitoring a payload was demonstrated for the 1623 | STS-41G ORS test: 1624 | 1625 | "Memo from John Young" (04/18/84, #CB-84-042): "The SPoC has been 1626 | determined by the crew to be not just useful, but mandatory for proper 1627 | crew monitoring of ORS hydrazine transfer operations. It provides the 1628 | proper displays that provide the crew their only insight into the 1629 | hydrazine heat transfer occurring during an ORS transfer operation for all 1630 | initial conditions. Using the SPoC information and the other ORS displays 1631 | and controls, timely and proper response can be made by the crew to any 1632 | ORS anomaly." 1633 | 1634 | "STS-41G Debrief Notes" (10/18/84): "[The SPoC was] very helpful because 1635 | no one had time to just sit by a window and watch for sites and 1636 | phenomena." 1637 | 1638 | "STS-51C Crew Report": "The presence of SPoC on our mission was a major 1639 | asset in helping us perform many of our tasks. Future capabilities for 1640 | SPoC will increase its utility even more...these computers have proven to 1641 | be very reliable..." 1642 | 1643 | "Memo from On-Orbit Flight Techniques Panel" (01/25/88, #DA8- 88-04): 1644 | "After reviewing the functions provided by the SPoC and assessing the 1645 | significant degree of support it provides for routine flight crew 1646 | operations, the FTP considers it to be a very important part of crew 1647 | equipment and recommends the Program consider it to be 'mandatory' for all 1648 | STS flights. 1649 | 1650 | "The FTP also recommends that the SPoC should continue to be classified as 1651 | criticality 3. These recommendations are based on two considerations. 1652 | 1653 | 1654 | 1655 | a) The primary SPoC function, that of an orbit trajectory status display, 1656 | does not jeopardize the crew, vehicle, or mission in the event of 1657 | malfunction. 1658 | 1659 | 1660 | b) The secondary SPoC function of providing a backup deorbit targeting 1661 | capability for emergency deorbit would only be used when the Mission 1662 | Control Center is unavailable for Orbiter support and an immediate deorbit 1663 | was required. The probability of this happening is extremely remote 1664 | because for every case except a large cabin leak, it takes multiple 1665 | failures before this capability would be needed, and most of those 1666 | combinations of failures, such as failure of both freon loops, are 1667 | considered non-credible. 1668 | 1669 | 1670 | "Retaining the SPoC's criticality 3 classification is highly desirable 1671 | because it allows a flexible and rapid response to new requirements. To 1672 | retain these desirable characteristics, functions considered inappropriate 1673 | for this classification should be integrated into other processors of an 1674 | appropriate classification." 1675 | 1676 | 1677 | 1678 | 1679 | APPENDIX F--GLOSSARY 1680 | 1681 | 1682 | AOS: Acquisition of Signal 1683 | 1684 | Boot Cycle: Period during which the computer is loading the operating 1685 | system and SPoC EXECUTIVE software. 1686 | 1687 | CG: Center of Gravity 1688 | 1689 | Choice Band: Rectangular area at the top of a form which will contain 1690 | choices or pertinent information. 1691 | 1692 | Choices: Predefined values for a setting. 1693 | 1694 | Command Key: RETURN key, ESCAPE key, and any other keys that select a menu 1695 | option. 1696 | 1697 | Confirm: Keyboard input of CODE-RETURN. 1698 | 1699 | Edit Prompt: A small triangular symbol which indicates a user input is 1700 | expected. 1701 | 1702 | EMCC: Emergency Mission Control Center 1703 | 1704 | EMI: Electromagnetic Interference 1705 | 1706 | EPROM: Erasable Programmable Read Only Memory 1707 | 1708 | FDO: Flight Dynamics Officer 1709 | 1710 | Form: User interface display which allows the user to enter or edit data 1711 | for one or more items. 1712 | 1713 | FRCS: Forward Reaction Control System 1714 | 1715 | GFE CCB: Government Furnished Equipment Configuration Control Board 1716 | 1717 | GMT: Greenwich Mean Time 1718 | 1719 | GNC: Guidance Navigation and Control 1720 | 1721 | GPC: General Purpose Computer 1722 | 1723 | Highlighted Box: If choices are available in the choice band, the 1724 | highlighted box indicates the current choice or highlights pertinent 1725 | information. 1726 | 1727 | ISP: Specific Impulse 1728 | 1729 | Item: Label which identifies the data to be modified in a form. 1730 | 1731 | LOS: Loss of Signal 1732 | 1733 | LOT: Landing Opportunities Table 1734 | 1735 | MCC: Mission Control Center 1736 | 1737 | Menu: User interface display which allows the user to select one of the 1738 | available options. 1739 | 1740 | MET: Mission Elapsed Time 1741 | 1742 | MOC: Mission Operations Computer 1743 | 1744 | MOCR: Mission Operations Control Room 1745 | 1746 | Modifier Keys: CODE keys, SHIFT key, and CONTROL key. 1747 | 1748 | Nadir: Projection of the Orbiter's position along the local vertical onto 1749 | the Earth's surface. 1750 | 1751 | OMS: Orbital Maneuvering System 1752 | 1753 | ORS: Orbital Refueling System 1754 | 1755 | PROM: Programmable Read Only Memory 1756 | 1757 | PSAT: Predicted Site Acquisition Table 1758 | 1759 | Prompt: Message informing the user what action should be taken next. 1760 | 1761 | PTI: Program Test Input 1762 | 1763 | RAM: Random Access Memory 1764 | 1765 | RCS: Reaction Control System 1766 | 1767 | RMS: Remote Manipulator System 1768 | 1769 | ROM: Read Only Memory 1770 | 1771 | RTS: Remote Tracking Station 1772 | 1773 | Selection Box: Rectangular outline enclosing the current item in a form or 1774 | the current option in a menu. 1775 | 1776 | Setting: Data value in a form. 1777 | 1778 | SGMT: Simulated GMT 1779 | 1780 | SPEC: GPC display used to view and modify parameters. 1781 | 1782 | SPoC: Shuttle Portable Computer 1783 | 1784 | STDN: Spaceflight Tracking and Data Network 1785 | 1786 | TDR: True of Date Rotating 1787 | 1788 | TDRS: Tracking and Data Relay Satellite 1789 | 1790 | TDRSS: Tracking and Data Relay Satellite System 1791 | 1792 | TIG: Time of Ignition 1793 | 1794 | 1795 | 1796 | -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/RNP.TXT: -------------------------------------------------------------------------------- 1 | 30412800 2 | 0.068494059095900 0.997651484625898 -0.000281233548861 3 | -0.997643883881736 0.068494635063139 0.003894344737186 4 | 0.003904461797995 0.000013831451395 0.999992377464328 5 | 1.5112299 6 | -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/SCRINIT.SCR: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/SCRINIT.SCR -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/SETTIME.RUN: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/SETTIME.RUN -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/SITEMGR.RUN: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/SITEMGR.RUN -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/SPOC.RUN: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/SPOC.RUN -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/SPOC_UP.DOC: -------------------------------------------------------------------------------- 1 | Shuttle Portable Computer Software 2 | 3 | This is an edited version of the Shuttle ground track program used by 4 | the astronauts in flights aboard the Shuttle. More complete documentation 5 | is provided in the self-extracting ZIP file. If you don't have the hardware 6 | setup described below, it is likely that this program will not run for you. 7 | 8 | In keeping with the NASA Spacelink file naming convention, SPOCZIP.EXE is named 9 | 9_11_4_17_3.BIN on the system. Be sure to rename it SPOCZIP.EXE when you 10 | download it. Begin by placing it in your C> root directory. 11 | 12 | To "unzip" the file, enter the following in your hard drive ROOT 13 | directory at the C> prompt and then press return: 14 | 15 | C> SPOCZIP -d 16 | 17 | Adding -d will cause the ZIP program to create a subdirectory named PROGRAMS 18 | and fill it with files. 19 | 20 | Orbital state vectors required for this program are available from NASA 21 | Spacelink for each non-classified Shuttle mission. Use the "M50 Elements" 22 | figures. And remember that SPoC requires figures in thousands of feet. The 23 | M50 elements on NASA Spacelink are normally given in feet. Don't forget to 24 | move the decimal three places to the left before entering the figures into 25 | SPoC. 26 | 27 | The following hardware is required for proper operation of this program: 28 | 29 | IBM PC or compatible WITH MATH CO-PROCESSOR INSTALLED! 30 | Hard Drive at location C> 31 | Minimum 512K available memory NOTE: If you are running software 32 | (network software for example) that occupies enough memory to 33 | leave less than 512K for SPoC, SPoC will very likely crash. 34 | 35 | GRID.EXE, SPOC.BAT, and the PROGRAMS subdirectory, must be located in the 36 | Drive C> ROOT directory. 37 | 38 | To run the SPoC program type SPOC at the C> prompt and press return. 39 | 40 | NOTE: The CODE key referred to in the documentation for this document is the 41 | ALT key on IBM PC compatible computers. 42 | 43 | NOTE: SPoC was originally written for a GRID computer--not an IBM-PC. Before 44 | making SPoC available through NASA Spacelink, we tested it on a variety 45 | of IBM-PC and compatible computer configurations with mixed results. For 46 | example, SPoC seemed to be running OK on one computer, but its VGA 47 | display scrambled the screen making the program unreadable. We suspect 48 | that SPoC is incompatible with VGA. So if SPoC doesn't run on your 49 | particular setup, try it on another computer. We recommend CGA, but we 50 | have seen the program run properly on EGA setups. 51 | 52 | AND A LAST NOTE: Several people have reported receiving the error message 53 | "Can't find file EMULATOR.SHR" This is the error message you'll receive 54 | when you try to run the program without a math co-processor. 55 | 56 |  -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/STVEC.TXT: -------------------------------------------------------------------------------- 1 | -3614.4732069047 2 | 226.2593063992 3 | -291.7306924060 4 | -0.3694847664 5 | -3.3853178766 6 | 1.9575470086 7 | 0 8 | 1 9 | 13 10 | 35 11 | -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/TG6X8.TYP: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/TG6X8.TYP -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/USER.PRO: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/USER.PRO -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/VECFORM.RUN: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/PROGRAMS/VECFORM.RUN -------------------------------------------------------------------------------- /spoc-fs/PROGRAMS/VEHWGHT.TXT: -------------------------------------------------------------------------------- 1 | 245313.3 2 | 315.5 3 | -------------------------------------------------------------------------------- /spoc-fs/PROTO.SYS: -------------------------------------------------------------------------------- 1 | DEVICE=C:\VMM\VEMMSIME.SYS 2 | DEVICE=C:\VMM\VEMM.SYS 3 | -------------------------------------------------------------------------------- /spoc-fs/RAMDRIVE.SYS: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/RAMDRIVE.SYS -------------------------------------------------------------------------------- /spoc-fs/READPORT.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/READPORT.COM -------------------------------------------------------------------------------- /spoc-fs/REBOOT.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/REBOOT.COM -------------------------------------------------------------------------------- /spoc-fs/RECOVER.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/RECOVER.COM -------------------------------------------------------------------------------- /spoc-fs/REPLACE.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/REPLACE.EXE -------------------------------------------------------------------------------- /spoc-fs/RESTORE.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/RESTORE.COM -------------------------------------------------------------------------------- /spoc-fs/SELECT.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/SELECT.COM -------------------------------------------------------------------------------- /spoc-fs/SETCMOS.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/SETCMOS.COM -------------------------------------------------------------------------------- /spoc-fs/SETPORT.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/SETPORT.COM -------------------------------------------------------------------------------- /spoc-fs/SETSPD.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/SETSPD.COM -------------------------------------------------------------------------------- /spoc-fs/SETUP.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/SETUP.COM -------------------------------------------------------------------------------- /spoc-fs/SHARE.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/SHARE.EXE -------------------------------------------------------------------------------- /spoc-fs/SORT.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/SORT.EXE -------------------------------------------------------------------------------- /spoc-fs/SUBST.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/SUBST.EXE -------------------------------------------------------------------------------- /spoc-fs/SYS.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/SYS.COM -------------------------------------------------------------------------------- /spoc-fs/TREE.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/TREE.COM -------------------------------------------------------------------------------- /spoc-fs/UPDCFG.COM: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/UPDCFG.COM -------------------------------------------------------------------------------- /spoc-fs/XCOPY.EXE: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/robertely/SPOC-VirtualBox/1973a106f5a9c1943243027f32027a92fd0c52f3/spoc-fs/XCOPY.EXE -------------------------------------------------------------------------------- /spoc-fs/autoexec.BAT: -------------------------------------------------------------------------------- 1 | cd \ 2 | cls 3 | grid \programs\spoc.run 4 |  --------------------------------------------------------------------------------