design_final_b

design_final_b - EMFFORCE OPS MANUAL B Space Systems...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
EMFFORCE OPS MANUAL Space Systems Product Development – Spring 2003 B Software Documentation The software in the EMFF system can be initially grouped by its physical location: avionics software on the avionics Tattletale, metrology software on the metrology Tattletale, and ground station software on the EMFF laptop. The avionics Tattletale (TT8) houses software for avionics, communication, and control; the ground station and metrology TT8 computers each hold the majority of their own subsystems’ software. However, in this appendix all software (SW) will be grouped by function, or subsystem: “avionics” (B.1) covers all SW on the avionics TT8 but does not address communication or the control test module in detail; “communications” SW (B.2) includes the communications modules on the avionics Tattletale and all ground station SW; “metrology” includes all SW on the metrology TT8; “control” (B.4) includes specific information on translating control test algorithms to C source code and integrating them into the avionics software. B.1 Avionics Software and Operating System Overview – MAS (p.1-15) “Avionics software” is the name for the software package loaded to the avionics Tattletale computer. The avionics software is composed of three parts: the initialization section, which establishes vehicle- or system-wide standards (e.g. number of vehicles), mathematical constants, hardware I/O interfaces, and global variables; the main() function, which contains the EMFF operating system (OS); and the many separate functions, or modules, which accomplish specific tasks relating to timing, control, communication, metrology, or computation. B.1.1 Initialization B.1.1.1 Version documentation The history of the code should be documented in the top section. CODE_VER is a string established here, available at any point in the code for printout during debugging. Under this are notes regarding sections of the avionics code currently undergoing revision. The version of code to which this document refers is “IT-2A test 3” – or version 3 of Integrated Test 2A. B.1.1.2 Constants B.1.1.2.1 System Constants and Data Sizes These constants are important at the entire system level. They set the identification of the local vehicle, the number of vehicles in the system, number of stages in the operating system cycle, buffer sizes for incoming communications and metrology data, and sizes of data-holding vectors (e.g. PVA, MSA). Table B-1 lists system and data size constants and where they are used. Massachusetts Institute of Technology 1 Dept of Aeronautics and Astronautics
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
EMFFORCE OPS MANUAL Space Systems Product Development – Spring 2003 Table B -1: Avionics System and Data Size Constants Identifier Name/Description Used in function Default value?
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 43

design_final_b - EMFFORCE OPS MANUAL B Space Systems...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online