White sands missile range reagan test site yuma proving ground

Changes to this Edition iii

Additions and changes to this document are noted with the following icons: iii

Table of Contents v

LIST OF FIGURES xxxviii

list of appendix figures xl

List of Tables xliii

Preface xvii

Acronyms and Initialisms xix

Introduction 1

TRANSMITTER AND RECEIVER SYSTEMS 1

2.1 Radio Frequency Standards for Telemetry 1

2.2 Definitions 1

The definitions of the radio services that can be operated within certain frequency bands contained in the radio regulations as agreed to by the member nations of the International Telecommunications Union. This table is maintained in the United States by the Federal Communications Commission and the NTIA. 1

2.3 UHF Bands 2

A telemetry system as defined here is not critical to the operational (tactical) function of the system. 2

TABLE 2-1. TELEMETRY FREQUENCY ALLOCATIONS 2

The word used for remote control operations in this band is telecommand. 3

Reallocated as of 1 January 1990. 3

2.4 UHF Telemetry Transmitter Systems 4

5. An exemption from this power limit will be considered; however, systems with transmitter power levels greater than 25 watts will be considered nonstandard systems and will require additional coordination with affected test ranges.Telemetry systems with bandwidths greater than 10 MHz, operating on the standard telemetry bands, are highly discouraged. 4

An exemption from this EIRP limit will be considered; however, systems with EIRP levels greater than 25 watts will be considered nonstandard systems and will require additional coordination with affected test ranges. 5

TABLE 2-2. FQPSK-JR SHAPING FILTER DEFINITION 8

The FQPSK-JR definition does not include a specific interpolation method and a post-D/A filter design. However, it is known that benchmark performance will be difficult to achieve if the combined effects of interpolation and anti-alias filter produce more than .04 dB excess attenuation at 0.0833 times the input sample rate and more than 1.6 dB of additional attenuation at 0.166 times the sample rate where the input sample rate is referred to the input of the interpolator assuming 6 samples per second. 9

Table 2-3. FQPSK-B and FQPSK-JR phase map 10

TABLE 2-4. SOQPSK-TG PARAMETERS 12

TABLE 2-5. SOQPSK PRE-CODING TABLE FOR IRIG-106 COMPATIBILITY 13

TABLE 2-6. DIBIT TO IMPULSE AREA MAPPING 14

Any unwanted signal or emission is spurious whether or not it is related to the transmitter frequency (harmonic). 15

The intent is that fixed frequency transmitters can be used at different frequencies by changing crystals or other components. All applicable performance requirements will be met after component change. 16

These bandwidths are measured using a spectruma analyzer with the following settings: 30-kHz resolution bandwidth, 300-Hz video bandwidth, and no max hold detector or averaging. 16

2.5 UHF Telemetry Receiver Systems 17

In most instances, the output low-pass filter should not be used to “clean up” the receiver output prior to use with demultiplexing equipment. 18

‡ see note below 19

Frequency Division Multiplexing Telemetry Standards 1

3.1 General 1

3.2 FM Subcarrier Characteristics 1

3.3 FM Subcarrier Channel Characteristics 1

TABLE 3-1a. PROPORTIONAL-BANDWIDTH FM SUBCARRIER CHANNELS 2

7.5% CHANNELS 2

TABLE 3-1B. PROPORTIONAL-BANDWIDTH FM SUBCARRIER CHANNELS 3

15% CHANNELS 3

TABLE 3-1c. PROPORTIONAL-BANDWIDTH FM SUBCARRIER CHANNELS 4

30% CHANNELS 4

3.4 Tape Speed Control and Flutter Compensation 5

TABLE 3-2. CONSTANT-BANDWIDTH FM SUBCARRIER CHANNELS 6

TABLE 3-3. REFERENCE SIGNAL USAGE 7

Pulse Code Modulation Standards 1

4.1 General 1

4.2 Class Distinctions and Bit-Oriented Characteristics 1

4.3 Fixed Formats 2

Code Waveforms 3

4.4 Format Change (Class II) 6

4.5 Asynchronous Embedded Format (Class II) 7

4.6 Tagged Data Format (Class II) 7

Defined in MIL-HDBK-1553A(2), 1995, Multiplex Applications Handbook. 7

4.7 Time Words 8

4.8 Asynchronous Data Merge 10

Digitized Audio Telemetry Standard 1

5.1 General 1

5.2 Definitions 1

5.3 Signal Source 1

5.4 Encoding/Decoding Technique 1

5.5 CVSD Encoder Output Bit Rate (CVSD Bit Rate) 2

5.6 CVSD Word Structure 2

5.7 CVSD Word Sample Rate 3

5.8 CVSD Bit Rate Determination 3

MAGNETIC TAPE RECORDER AND REPRODUCER STANDARDS 1

6.1 Introduction 1

6.2 Definitions 1

6.3 General Considerations for Longitudinal Recording 6

6.4 Recorded Tape Format 7

TABLE 6-1. RECORD and REPRODUCE PARAMETERS 8

TABLE 6-2. DIMENSIONS – RECORDED TAPE FORMAT 9

TABLE 6-3. DIMENSIONS – RECORDED TAPE FORMAT 10

Notes: 10

(2) Track location and spacing are the same as the odd tracks of the 28-track interlaced format (see Table 6-4). Edge margin for track 1 is only 0.229 mm (0.009 in.). 10

TABLE 6-4. DIMENSIONS – RECORDED TAPE FORMAT 11

(2) Track location and spacing are the same as the odd tracks of the 28-track interlaced format (see Table 6-4). Edge margin for track 1 is only 0.229 mm (0.009 in.). 11

12

6.5 Head and Head Segment Mechanical Parameters 16

6.6 Head Polarity 17

6.7 Magnetic Tape and Reel Characteristics 18

6.8 Direct Record and Reproduce Systems 18

6.9 Timing, Predetection, and Tape Signature Recording 20

Timing code formats are found in IRIG standard 200-98, IRIG Serial Time Formats and IRIG standard 205-87, Parallel Binary and Parallel Binary Coded Decimal Time Code Formats. 20

TABLE 6‑5. CONSTANT‑AMPLITUDE SPEED‑CONTROL SIGNALS(1) 21

TABLE 6‑6. PREDETECTION CARRIER PARAMETERS 22

6.10 FM Record Systems 22

TABLE 6‑7. WIDE BAND AND DOUBLE DENSITY FM RECORD PARAMETERS 23

6.11 PCM Recording 24

TABLE 6‑8. MAXIMUM RECOMMENDED BIT RATES, POST- 25

DETECTION RECORDING(1) 25

TABLE 6-9. MAXIMUM RECOMMENDED BIT RATES 26

6.12 Preamble Recording for Automatic or Manual Recorder Alignment 29

6.13 19-mm Digital Cassette Helical Scan Recording Standards 29

Formerly ANSI -1990. Available from American National Standards Institute (webstore.ansi.org). 30

TABLE 6-10. RECORD LOCATION AND DIMENSIONS 31

TABLE 6-11. TAPE LENGTH AND NOMINAL PLAY RECORD/ 31

REPRODUCE TIME AT 240 MEGABITS/SECOND USER DATA RATE 31

6.14 Multiplex/Demultiplex (MUX/DEMUX) Standard for Multiple Data Channel Recording on 19-MM Digital Cassette Helical Scan Recorder/Reproducer Systems 32

requires less than 3 percent overhead to be added to user data; 32

accommodates multiple channel record/playback with each channel completely autonomous in sample rate and sample width; 32

stores all the necessary parameters for channel data reconstruction for either real-time playback, time-scaled playback, or computer processing; 32

preserves phase coherence between data channels; 32

provides channel source and timing information; and 32

accommodates 224 (over 16 million) blocks of data, each block having 2048 24-bit words (see Figure 6-7). 32

6.15 Submultiplex/Demultiplex Standards for Multiple Data Channels on a Primary Digital Multiplex/Demultiplex Channel 35

6.16 1/2 Inch Digital Cassette (S-VHS) Helical Scan Recording Standards 40

Formerly ANSI V98.33M. 40

See paragraph 6.16. 42

See paragraph 6.16. 54

6.17 Multiplex/Demultiplex (MUX/DEMUX) Standards for Multiple Data Channel Recording on ½ Inch Digital Cassette (S-VHS) Helical Scan Recorder/Reproducer Systems. 56

MIL-STD 1553B (1996), Digital Time Division Command/Response Multiplex Data Bus. 56

Part Number 199034-0002, available from CALCULEX, Inc., P.O. Box 339, Las Cruces, NM 88004 (505) 525-0131 or by email to info@calculex.com. 57

(or time Code) 57

TABLE 6-12. SCANLIST BUILD STEPS 58

TABLE 6-13. SAMPLE ARMOR FRAME 59

TABLE 6-14. 60

TIME CODE WORD FORMAT 60

BIT 60

LEGEND 60

Part Number 198007-0001 may be obtained from CALCULEX, Inc. P.O. Box 339, Las Cruces, NM 88004 (505) 525-0131 or by email request to info@calculex.com. 61

6.18 Recorder Command and Control Mnemonics (CCM) 62

a. The STARTING and STOPPING (ENDING) states may require zero (none) or more wait states, as necessary, for a particular recorder and command implementation. 62

b. Some recorders can record without playing, play without recording, or record and play at the same time. 62

c. For those recorders that require data clocks, the record clock is always external (provided by the source of the data). The playback clock, on the other hand, may be externally or internally supplied, and when externally supplied, may or may not be synchronous to (equal to or derived from) the record clock. 62

d. Some functions are implemented using multiple commands. For example, a conventional longitudinal recorder shuttle command is implemented as a .FIND command with the starting point identifier, followed by a .SHUTTLE command with the ending point identifier. Once the initial .SHUTTLE command is received, the recorder automatically initiates a FIND sequence when the end point is reached, and then automatically initiates a PLAY sequence when the start point is found. This is shown on the state transition diagram as the decision box “another command pending”. 62

e. Some recorders are physically able to record over existing data. This standard prevents recording over existing data by forcing the record point to the current end of data (EOD). An erase command is provided to enable reuse of the media by resetting the record point to the beginning of media (BOM). 62

f. Some recorders are physically able to replay data in either the forward sequence or reverse sequence. Forward is the sequence in which the data was recorded, whereas reverse is the opposite sequence. This standard only requires and supports replay in the forward sequence. 63

a. All recorder commands are simple ASCII character strings delimited by spaces. 63

b. All commands begin with an ASCII period (“.”) and, with the single exception of the .TMATS command, end with the first occurrence of a carriage return and line-feed terminator sequence. 63

c. Parameters are separated from the commands and from each other with ASCII space characters. 63

d. With one exception, command words and parameters may not include spaces. The one exception is the [text string] parameter for the .EVENT command. 63

e. Multiple consecutive terminators and extraneous space characters are ignored. 63

f. Each command is followed with either a simple response and an ASCII asterisk (“*”) response terminator or the asterisk response terminator only, indicating the recorder is ready for the next command. 63

g. All numeric parameters, with one exception, are decimal numbers. The one exception is the [mask] parameter for the .CRITICAL command, which is hexadecimal. 63

h. Three commands, .FIND, .REPLAY, and .SHUTTLE, have numeric parameters that required units of measure. The [mode] parameter is used to specify the unit of measure (time, feet, or blocks.) If the [mode] parameter is omitted, the recorder shall use the most recently entered [mode]. 63

i. A [time] parameter value has five parts: days, hours, minutes, seconds, and milliseconds. Any part not entered defaults to zero except days, which defaults to don’t care (current day.) A period (“.”) identifies the start of the millisecond part, a hyphen (“-” separates the day from the hours, and colon characters (“:”) separate the hours, minutes, and seconds. The following are valid times: 123- (day only), 17 (hours only), 17:30 (hours and minutes), 17:30:05 (hours, minutes, seconds), 17:0:05 (hours, minutes, seconds), 17:30:05.232 (hours, minutes, seconds, milliseconds), 123-17 (day, hours), 123-17:30 (day, hours, minutes), etc. 63

TABLE 6-15 COMMAND SUMMARY 65

TABLE 6-16. COMMAND ERROR CODES 66

Command does not exist 66

Parameter is out of range, or wrong alpha-numeric type 66

Command cannot be executed in the current state 66

Recording media is dismounted or not installed 66

Command cannot be executed because there is no free space available on the recording media 66

Command failed to execute for any reason other than those listed above 66

a. If no features are implemented, the response to a .HEALTH command is the response terminator asterisk. 72

b. Implemented features are numbered consecutively starting with 1 and displayed in ascending numerical order. 72

c. The description of a feature may not contain an asterisk character. 72

d. The feature list response (no feature number parameter supplied with the command) is a sequence of text strings, each containing the decimal feature number, the 8-character ASCII hexadecimal representation of the 32-bit status word for the feature, a text feature description, and a carriage return and line feed terminator. The value of the 32-bit status word for a “healthy” feature shall be all zeros. If a feature is disabled, the 8-character ASCII hexadecimal string shall be replaced with eight ASCII hyphen “-” characters. 72

e. The individual feature response (feature number parameter supplied with the command) is a sequence of descriptive text strings, one for each set bit in the feature status word. Each string is terminated with a carriage return and line feed. 72

TABLE 6-17. RECORDER STATES 76

* 80

* 80

TABLE 6-18. COMMAND VALIDITY MATRIX 81

TABLE 6-19. REQUIRED COMMANDS 82

Magnetic Tape Standards 1

7.1 General 1

Federal Specifications may be used to replace paragraphs contained in this chapter where applicable. High output and HDD tapes re not included in the Federal Specificaions. Other standards are referenced in paragraph 1.0, Appendix D. 1

7.2 Definitions 1

7.3 General Requirements for Standard Instrumentation Tapes and Reels 4

There are four W-T-1553 specifications relating to different coercivity and dropout rates. 5

7.4 General Characteristics of Instrumentation Tapes and Reels 5

TABLE 7‑1. TAPE DIMENSIONS 6

(1) Actual tape base material thickness slightly less because of manufacturing conventions. 6

(2) Original dimensions are in feet. Metric conversions are rounded for convenience. 6

(3) Tape-to-flange radial clearance (E-value) is 3.18 mm (0.125 in.). 6

Short Term: 0 to 45 C (32 to 115 F) and 10 to 70 percent RH noncondensing 7

Long Term: 1 to 30 oC (33 to 85 oF) and 30 to 60 percent RH noncondensing 7

7.5 Physical Characteristics of Instrumentation Tapes and Reels 8

7.6 Instrumentation Tape Magnetic and Electrical Characteristics 8

TABLE 7-2. MEASUREMENT WAVELENGTHS 8

TABLE 7-3. DURABILITY SIGNAL LOSSES 10

TABLE 7-4. SUGGESTED TAPE REQUIREMENT LIMITS 12

TABLE 7-4A. SUGGESTED WAVELENGTH RESPONSE REQUIREMENTS 12

7.7 General Requirements for 19-mm Digital Cassette Helical Scan Recording Tape and Cassettes 14

MML Document 94-1 is available from the Naval Air Warfare Center Aircraft Division, Warminster, Pennsylvania 18974-0591. 14

SMPTE 226M is available from the Society of Motion Picture and Tele-vision Engineers, 595 West Hartdale Avenue, White Plains, New York 10607. 14

7.8 General Requirements for 1/2-Inch Digital Cassette Helical Scan Recording Tape and Cassettes 14

MML Document 93-1 is available from the Naval Air Warfare Center, Aircraft Division, Warminster, Pennsylvania 18974-0591. 14

Formerly ANSI V98.33M-1983. 14

MIL-STD-1553 Acquisition Formatting Standard 1

8.1 General 1

8.2 Definitions 1

8.3 Source Signal 2

8.4 Word Structure 3

8.5 Time Words 5

8.6 Composite Output 5

8.7 Single Bus Track Spread Recording Format 6

Telemetry Attributes Transfer Standard 1

9.1 General 1

9.2 Scope 1

9.3 Purpose 1

9.4 Media and Data Structure 2

9.5 Telemetry Attributes 3

General Information - establishes the top-level program definition and identifies the data sources. 3

Transmission Attributes - define an RF link. There will be one group for each RF link identified in the General Information Group. 3

Tape/Storage Source Attributes - identify a tape or storage data source. 3

Multiplex/Modulation Attributes - describe the FM/FM, FM/PM, or PM/PM multiplex characteristics. Each multiplexed waveform must have a unique set of attributes. For the analog measurement, the tie to the engineering units conversion is made in this group. 3

Digital Data Attributes - are divided into three groups: the PCM Format Attributes, the PCM Measurement Description, and the Bus Data Attributes. 3

PCM Format Attributes - define the PCM data format characteristics, including subframes and embedded formats. Each PCM format will have a separate format attributes group. 4

PCM Measurement Descriptions - define each PCM measurand that ties the PCM measurement, format, and data conversion (calibration) together. 4

Bus Data Attributes - specify the PCM encoded MIL-STD-1553 or ARINC 429 bus format characteristics. 4

PAM Attributes - contain the definition of the PAM system. It includes the PAM format characteristics and measurement attributes. The tie to the engineering unit conversion is made for the measurands contained in the PAM format. 4

Data Conversion Attributes - contain the data conversion information for all measurements in this telemetry system. The calibration data and conversion definition of raw telemetry data to engineering units is included. The tie to the measurands of the telemetry systems defined in the previous groups is via the measurement name. 4

Airborne Hardware Attributes - define the configuration of airborne instrumentation hardware in use on the test item. 4

Vendor Specific Attributes - provide information that is specific to a vendor. 4

TABLE 9-1. general information GROUP (G) 8

G\SC 10

TABLE 9-2. TRANSMISSION ATTRIBUTES GROUP (T) 12

32 12

12 12

6 12

12 12

16 14

6 14

4 14

4 15

4 15

1600 15

(9-25) 18

(9-25) 18

*Heading Only - No Data Entry 18

TABLE 9-3. TAPE/STORAGE SOURCE ATTRIBUTES GROUP (R) 19

32 19

4 19

2 19

8 20

19 20

2 21

32 21

3 22

1 25

3200 26

*IRIG SUBCARRIERS 27

TABLE 9-4. MULTIPLEX/MODULATION GROUP (M) 28

32 28

7 28

3 28

32 29

32 29

2 29

2 29

6 30

32 30

32 30

1 30

6 30

3200 30

DATA LINK NAME 32

table 9-5. pcm format attributes group (P) 34

(D-x\DLN) 45

LOCATION DEFINITION 46

(D-x\FSF10-y-n-m-e) 46

TABLE 9-6. PCM MEASUREMENT DESCRIPTION GROUP (D) 47

PARAMETER 54

PARAMETER 55

DATA LINK NAME 57

*Heading Only – No Data Entry 58

table 9-7. bus data attributes group (B) 59

8 61

PARAMETER 62

2 62

PARAMETER 63

*Heading Only – No Data Entry 64

TABLE 9-8. PAM ATTRIBUTES GROUP (A) 65

PARAMETER 65

PARAMETER 67

LOW MEASUREMENT VALUE 69

OR 70

*Heading Only - No Data Entry 70

table 9-9. data conversion attributes group (c) 71

Test Item (code name H-x\TA) specifies the item under test and ties the H group to the G group. 79

Airborne System Type (code name H-x\ST-n) will distinguish which airborne systems are being described in the current file and will determine how the rest of the attributes in the H group are interpreted. 79

Solid State On-Board Recorder Standard 1

10.1 General 1

a. Data download and interface 1

b. One or more multiplexed data streams 1

c. One or more single data streams 1

d. Read-after-write and read-while-write options 1

e. Data format definitions 1

f. Recorder control 1

g. Solid-state media declassification 1

1. Data download and electrical interface, which is the physical interface for data access (defined in section 10.4). 3

2. Interface file structure, which defines the data access structure (defined in section 10.5). 3

3. Data format definition, which defines data types and packetization requirements (defined in section 10.6). 3

4. Solid-state recorder control and status, which defines command and control mnemonics, status, and their interfaces (defined in section 10.7). 3

10.2 Definitions 3

10.3 Operational Requirements 5

a. Download port 5

b. Control port 5

c. External power port 5

10.4 Data Download and Electrical Interface 6

Document published as ANSI INCITS TR19-1998. 6

The control protocol must support a number of data storage media types. Only the minimum set of SCSI commands needed to download mission data from a memory cartridge are defined as “required.” FC-PLDA SCSI commands, features, and parameters not defined as “required” for this standard are redefined as “allowed” and may be implemented as appropriate. Table 10-1 provides the four “required” SCSI commands and their features and parameter usage definitions. 6

Table 10-1. 7

“required” scsi commands, features, and parameters 7

Adapted from STANAG 4575, Table B-1. 7

INQUIRY 7

1 7

READ CAPACITY 7

TEST UNIT READY 7

10.5 Interface File Structure Definition 8

This interface file structure definition is adopted from STANAG 4575. This file structure was selected to facilitate host computing platform independence and commonality. By incorporating an independent file structure backward and forward compatibility is ensured for the life of the standard. 8

Annex B Protocol Interface Definitions, section 3, File Structure Definition. 8

a. Computer Generated Packet, Setup Record Format 1, in accordance with (IAW) paragraph 10.6.7.2.2 as the first packet in the recording. 8

b. Time Data Packet(s) IAW paragraph 10.6.3 as the first dynamic packet after the Computer Generated Packet Set Record. 8

c. One or more data format packets IAW section 10.6. 8

Multiple recordings may reside on the media, and each recording may contain one or more compliant files. 8

Table 10-2. Directory Block Format – Primary Block 11

8 11

32 11

Table 10-3. Directory ENTRY Format 12

56 12

ASCII 12

8 12

8 12

7 12

TABLE 10-3 (Cont’d). DIRECTORY ENTRY FORMAT 13

Assuming a 32-bit entry, composed of four 8-bit bytes, where the first and least significant byte is byte [0] and the last and most significant is byte [3], then the correspondence of bits to bytes, where bit [00] is the least significant bit, is as follows in Table 10-4. 13

table 10-4. correspondence of bits to bytes 14

Byte [3] 14

table 10-5. 14

prohibited characters hexidecimal representation 14

a. Filenames shall not be case sensitive. 15

b. Leading and trailing spaces are not permitted. 15

c. Leading periods are not permitted. 15

d. Names shall be left-justified in the field and are terminated with a null<00h>. The maximum length of the name is the length of the field minus one. 15

10.6 Data Format Definition 15

Packet Trailer 17

0x00 = Reserved. 19

0x01 = Initial Release Header Version. 19

0x02 thru 0xFF = Reserved for future releases. 19

0x00 = Computer Generated Data: Format 0 - (user defined) 20

0x01 = Computer Generated Data: Format 1 - (setup record) 20

0x09 = PCM Data: Format 1 20

0x11 = Time Data: Format 1 20

0x19 = MIL-STD-1553 Data: Format 1 20

0x21 = Analog Data: Format 1 20

0x29 = Discrete Data: Format 1 20

0x30 = Message Data: Format 0 20

0x38 = ARINC 429 Data: Format 0 20

0x40 = Video Data: Format 0 - (MPEG-2 Video) 20

0x48 = Image Data: Format 0 - (Image) 20

0x50 = UART Data: Format 0 20

a. keep all packets aligned on 32-bit boundaries (i.e., make all packet lengths a multiple of 4 bytes), and 22

b. optionally, keep all packets from a particular channel the same length. 22

The inclusion of the Data Checksum is optional as well and is indicated by the Packet Flags setting. When included, the packet trailer contains either an 8-bit, 16-bit or 32-bit Data Checksum. Depending on the Packet Flags option selected, the Data Checksum is the arithmetic sum of all of the bytes (8-bits), words (16-bits) or long words (32-bits) in the packet, excluding the 24 bytes of Packet Header Words, Packet Secondary Header (if enabled) and the Data Checksum word. Stated another way, the Data Checksum includes everything in the packet body plus all added Filler. 22

SYNCOFFSET 23

msb 26

0 26

PACKET HEADER 26

CHANNEL SPECIFIC DATA (BITS 15-0) 26

INTRA-PACKET TIME STAMP (BITS 15-0) 26

msb 27

0 27

PACKET HEADER 27

CHANNEL SPECIFIC DATA (BITS 15-0) 27

CHANNEL SPECIFIC DATA (BITS 31-16) 27

DATA BITS 0 to 16 27

Y FILLER BITS 27

msb 28

0 28

PACKET HEADER 28

PACKET TRAILER 28

THn 32

THn 32

PACKET HEADER 33

BLOCK STATUS WORD 34

PACKET HEADER 37

CHANNEL SPECIFIC DATA (BITS 15-0) 37

INTRA-PACKET TIME STAMP FOR MSG 1 (BITS 15-0) 37

DATA OR STATUS WORD 37

INTRA-PACKET TIME STAMP FOR MSG 2 (BITS 15-0) 37

DATA OR STATUS WORD 37

INTRA-PACKET TIME STAMP FOR MSG n (BITS 31-16) 37

PACKET HEADER 38

: 38

CHANNEL SPECIFIC DATA WORD, SUBCHANNEL M 38

SAMPLE 1 38

RESERVED 39

FACTOR 39

SUBCHAN 39

LENGTH 39

MODE 39

Directly following the Channel Specific Data word(s), at least one complete sampling schedule shall be inserted in the packet. The samples, within the sampling sequence, may be inserted either unpacked, MSB-Packed, or LSB-Packed as described in paragraph 10.6.5.2.1 and 10.6.5.2.2. In either case, one or more subchannels may be included in a single packet. When multiple subchannels are encapsulated into a single packet, the subchannel with the highest sampling rate requirement defines the primary simultaneous sampling rate. The rate at which the other subchannels are sampled is defined by the sampling factor (contained within the Channel Specific Data words). Sampling factors are defined as: 40

4-PAD BITS 43

PACKET HEADER 45

TIME (LSLW) 46

PACKET HEADER 47

PACKET TRAILER 47

PACKET HEADER 48

RESERVED 48

PACKET HEADER 49

PACKET TRAILER 49

PACKET HEADER 51

: 51

TYPE 51

TIME (LSLW) 53

Table 10-6. MP@ML algorithms 54

PACKET HEADER 55

a. 94 words per frame (includes sync) 56

b. 16 bits per word 56

c. 8 bit sync pattern, 01000111 (0x47) 56

TSF DATA BITS 15 TO 8 57

PACKET HEADER 57

: 58

TIME (LSLW) 59

: 60

TIME (LSLW) 61

10.7 Solid State Recorder Control and Status 62

RECORD 63

BIT 63

10.8 Declassification 65

A count of the number of bad blocks in the Failed Erase Table that have not been Secure Erased is returned as part of the Secure Erase results. A non-zero count indicates a Secure Erase failure of at least one block. A command will allow the user to retrieve the Failed Erase Table. A command will also allow a user to retrieve the data from such blocks and manually determine if these blocks can be designated as “Secure Erased.” In most cases a single stuck bit will not compromise any user data and the offending block can be manually declared to be Secure Erased. If the results of manual inspection are indeterminate, the chip containing the failed block must be removed and destroyed, and the Secure Erase procedure must be repeated. 67

Frequency Considerations for Telemetry 1

1.0 Purpose 1

2.0 Scope 1

 The definitions of the radio services that can be operated within certain frequency bands contained in the radio regulations as agreed to by the member nations of the International Telecommunications Union. This table is maintained in the United States by the Federal Communications Commission and the NTIA. 1

3.0 Authorization to Use a Telemetry System 3

4.0 Frequency Usage Guidance 4

B Table A-1. COEFFICIENTS FOR MINIMUM FREQUENCY SEPARATION CALCULATION 5

1.0* for receivers with RLC final Intermediate 5

*The minimum frequency separation for typical receivers with Resistor-Inductor-Capacitor (RLC) final IF filters and NRZ-L PCM/FM signals is the larger of 1.5 times the actual IF –3 dB bandwidth and the value calculated using the equation above. 5

5 Mb/s PCM/FM and 0.8 Mb/s PCM/FM using a receiver with 6 MHz IF bandwidth for the 5 Mb/s signal (this receiver has RLC IF filters) 7

1.0*5 + 1.2*0.8 = 5.96 MHz, 1.0*.8 + 1.2*5 = 6.8 MHz, 1.5*6= 9.0 MHz; 7

the largest value is 9 MHz and the frequencies are assigned in 1 MHz steps so the minimum spacing is 9 MHz 7

5 Mb/s PCM/FM and 5 Mb/s PCM/FM using a receiver with 6 MHz IF bandwidth for the 7

5 Mb/s signals (these receivers have RLC IF filters; see Figure A-2) 7

5 Mb/s PCM/FM and 5 Mb/s PCM/FM using a receiver with 6 MHz IF bandwidth for the 7

5 Mb/s signal (this receiver has RLC IF filters but a multi-symbol detector is used) 7

5 Mb/s PCM/FM and 5 Mb/s SOQPSK-TG using a receiver with 6 MHz IF bandwidth for the 5 Mb/s signals (this receiver has RLC IF filters but a multi-symbol detector is used) 7

7

5.0 Bandwidth 9

 I. Korn, Digital Communications, New York, Van Nostrand, 1985. 14

 M. G. Pelchat, "The Autocorrelation Function and Power Spectrum of PCM/FM with Random Binary Modulating Waveforms," IEEE Transactions, Vol. SET‑10, No. 1, pp. 39‑44, March 1964. 14

 W. M. Tey, and T. T. Tjhung, "Characteristics of Manchester‑Coded FSK," IEEE Transactions on Communications, Vol. COM‑27, pp. 209‑216, January 1979. 14

 A. D. Watt, V. J. Zurick, and R. M. Coon, "Reduction of Adjacent‑Channel Interference Components from Frequency‑Shift‑Keyed Carriers," IRE Transactions on Communication Systems, Vol. CS‑6, pp. 39‑47, December 1958. 14

 E. L. Law, "RF Spectral Characteristics of Random PCM/FM and PSK Signals," International Telemetering Conference Proceedings, pp. 71‑80, 1991. 14

Random Bi PCM/FM 14

6.0 Spectral Occupancy Limits 16

m = 2 for binary signals 17

7.0 Technical Characteristics of Digital Modulation Methods 20

* 1=Best, 2=Second Best, 3=Third Best, 4=Worst 20

8.0 FQPSK-B and FQPSK-JR Characteristics 21

9.0 SOQPSK-TG Characteristics. 25

Younes B., Brase J., Patel C., Wesdock J., “An Assessment of Shaped Offset QPSK for Use in NASA Space Network and Ground Network Systems”, Meetings of Consultative Committee for Space Data Systems, Toulouse, France, October, 2000. 25

Figure A-24 shows the measured bit error probability (BEP) versus signal energy per bit/noise power per Hz (Eb/N0) of two SOQPSK-TG modulator/demodulator combinations including non-linear amplification and differential encoding/decoding in an additive white Gaussian noise environment (AWGN) with no fading. Other combinations of equipment may have different performance. Phase noise levels higher than those recommended in Chapter 2 can significantly degrade the BEP performance. 26

10.0 Advanced Range Telemetry (ARTM) CPM Characteristics. 26

11.0 PCM/FM 27

Use Criteria for Frequency Division Multiplexing 1

1.0 General 1

2.0 FM Subcarrier Performance 1

3.0 FM Subcarrier Performance Tradeoffs 2

K.M. Uglow,. Noise and Bandwidth in FM/FM Radio Telemetry, “IRE Transaction on Telemetry and Remote Control,” (May 1957) pp 19-22. 2

4.0 FM System Component Considerations 3

5.0 Range Capability For FM Subcarrier Systems 4

PCM Standards (Additional Information and Recommendations) 1

1.0 Bit Rate Versus Receiver Intermediate‑Frequency Bandwidth 1

2.0 Recommended PCM Synchronization Patterns 2

A more detailed account of this investigation can be found in a paper by J. L. Maury, Jr. and J. Styles, "Development of Optimum Frame Synchronization Codes for Goddard Space Flight Center PCM Telemetry Standards," in Proceedings of the National Telemetering Conference, June 1964. 2

The recommended synchronization patterns for lengths 31 through 33 are discussed more fully in a paper by E. R. Hill, "Techniques for Synchronizing Pulse-Code Modulated Telemetry," in Proceedings of the National Telemetering Conference, May 1963. 2

3.0 Spectral and BEP Comparisons for NRZ and Bi 2

Material presented in paragraph 3.0 is taken from a study by W. C. Lindsey (University of Southern California), Bit Synchronization System Performance Characterization, Modeling and Tradeoff Study, Naval Missile Center Technical Publication. 2

TABLE C-1. OPTIMUM FRAME SYNCHRONIZATION PATTERNS FOR PCM TELEMETRY 3

4.0 PCM Frame Structure Examples 5

Magnetic Tape Recorder and Reproducer 1

Information and Use Criteria 1

1.0 Other Instrumentation Magnetic Tape Recorder Standards 1

2.0 Double-Density Longitudinal Recording 1

TABLE D-1. DIMENSIONS - RECORDED TAPE FORMAT 4

7 Tracks Interlaced on 12.7-mm (1/2 in.) Wide Tape 4

TABLE D-2. DIMENSIONS - RECORDED TAPE FORMAT 5

TABLE D-3. DIMENSIONS - RECORDED TAPE FORMAT 6

42 Tracks Interlaced on 25.4-mm (1-in.) Wide Tape 6

3.0 Serial HDDR 8

4.0 Head Parameters 15

5.0 Record Level 15

6.0 Tape Crossplay Considerations 16

7.0 Standard Tape Signature Procedures 16

8.0 Equipment Required for Swept-Frequency Procedures 19

9.0 Fixed-Frequency Plus White Noise Procedure 19

10.0 Signature Playback and Analysis 20

11.0 Recording and Playback Alignment Procedures 21

Appendix E Deleted 1

Available Transducer Documentation 1

Continuously Variable Slope Delta Modulation 1

1.0 General 1

2.0 General Descriptions 1

3.0 Detailed Descriptions 3

4.0 Reference Level 5

5.0 CVSD Characteristics 5

TABLE F-1. DECODER REFERENCE DIGITAL PATTERNS FOR CVSD 7

TABLE F-2. INSERTION LOSS LIMITS FOR CVSD 8

TABLE F-3. IDLE CHANNEL NOISE LIMITS FOR CVSD 11

ADARIO Data Block Field Definitions 1

1.0 Data Block Format and Timing 1

2.0 ADARIO Data Format Field Definitions Summary 4

If IE = 1, then the value of rate is carried by the 16 LSBs of the rate field. Using rate, the frequency of the internal channel clock can be found by internal sample clock = (MC/RATE) -1. 7

3.0 Submux Data Format Field Definitions 10

4.0 SubMux Data Format Field Definitions Summary 11

CHN #1 20

Application of the 1

Telemetry Attributes Transfer Standard 1

1.0 Elements of the Telemetry Attributes Transfer Process 1

Telemetry Attributes Transfer Standard 1

Cover Sheet 1

1.0 Cover Sheet 1

Telemetry Attributes Transfer Standard 1

Format Example 1

Pulse Amplitude Modulation Standards 1

1.0 General 1

2.0 Frame and Pulse Structure 1

3.0 Frame and Pulse Rate 3

4.0 Frequency Modulation 4

5.0 Premodulation Filtering 4

Asynchronous Recorder Multiplexer Output Re-constructor (ARMOR) 1

1.0 General 1

TABLE L-1. ARMOR SETUP PREAMBLE 1

An ARMOR setup is divided into three sections: the header section, the channel section, and the trailer section. The overall organization of a setup is summarized in Table L-2. 2

TABLE L-2. SETUP ORGANIZATION 2

TABLE L-3. HEADER SECTION FORMAT 3

TABLE L-4. CHANNEL ENTRY LENGTHS 4

TABLE L-5. PCM INPUT CHANNELS 5

TABLE L-6. ANALOG INPUT AND OUTPUT CHANNELS 6

TABLE L-7. ANALOG INPUT AND OUTPUT CHANNELS 7

TABLE L-8. PARALLEL INPUT CHANNELS 7

TABLE L-9. PARALLEL OUTPUT CHANNELS 8

TABLE L-10. TIME CODE INPUT CHANNELS 11

TABLE L-11. TIME CODE OUTPUT CHANNELS 12

TABLE L-12. VOICE INPUT CHANNEL 13

TABLE L-13. VOICE OUTPUT CHANNELS 14

TABLE L-14. BIT SYNC INPUT CHANNELS 15

TABLE L-15. TRAILER SECTION FORMAT 16

Setup Length: Count the total numbers of bytes in the created setup block and put the value here. 17

Setup Keys: Set bit 0 = 1 if the trailer contains a description. Leave other bits = 0. 17

Input Count: Enter the total number of input channel information entries, including both enabled and disabled entries. 17

Channel Type: Binary 8 17

Enabled: ASCII “Y” if enabled, “N” if disabled 17

Channel Number: Binary 0, 1, 2, or 3 as described in 2.5.2 above 17

Module ID: Hexadecimal 11 17

Requested Rate: Binary integer rate in bits per second 17

Channel Type: Binary 5 for LF (up to 1 megasample/sec), 6 for HF (up to 10 megasamples/sec) 17

Enabled: “Y” if enabled, “N” if disabled 17

Bits per Sample: 8 or 12 17

Channel Number: 0, 1, 2, or 3 as described in 2.5.2 above 18

Module ID: Hexadecimal 34 (LF) or 33 (HF) 18

Requested Rate: Binary integer 2K, 5K, 10K, 20K, 50K, 100K, 18

200K, 500K, 1M (LF, HF) 2.5M, 5M, 10M (HF only) 18

Channel Type: Decimal 13 18

Enabled: “Y” if enabled, “N” if disabled 18

Channel Number: 0, 1, 2, or 3 as described in 2.5.2 above 18

Module ID: Hexadecimal 92 18

Requested Rate: Binary integer 8-bit words (bytes) per second 18

Channel Type: Decimal 15 (1st entry) , 19 (2nd entry), 20 (3rd entry) 18

Enabled: “Y” if enabled, “N” if disabled, all three entries must be the same 18

Bits per Word: Decimal 24 (1st entry), 24 (2nd entry), 16 (3rd entry) 18

Channel Number: 0, 1, or 2 as described in 2.5.2 above 18

Module ID: Hexadecimal B1 18

Requested Rate: 1 18

Bits per Sample: Decimal 24 (1st entry), 24 (2nd entry), 16 (3rd entry) 18

Channel Type: Decimal 16 18

Enabled: “Y” if enabled, “N” if disabled 18

Bits per Word: 8 18

Channel Number: 3 as described in 2.5.2 above 18

Requested Rate: Integer 2K, 5K, 10K, 50K, 100K 18

Bits per Sample: 8 18

21

1.0 Introduction 21

FQPSK-B is a proprietary variation of “Offset” QPSK (OQPSK), Digcom Inc., El Macero, California. 21

See Chapter 2 and Appendix-A for details on SOQPSK-TG (formerly SOQPSK-A*). 21

FQPSK-JR is an FQPSK variant developed by Mr. Robert Jefferis, TYBRIN Corporation,and Mr. Rich Formeister, RF Networks, Inc. 21

2.0 The Need For Differential Encoding 21

The delay can be inserted into either channel. The IRIG-106 convention and most published literature regarding FQPSK and SOQPSK indicate the delay in the odd (or Q) channel. 22

The initial offset angle  is generally unknown and uncontrolled; it is tracked by the carrier recovery circuitry and the symbol timing circuits automatically ignore. 22

3.0 A Simple Solution To The Carrier Phase Ambiguity Problem 24

Rectangular I and Q baseband waveforms are used only for illustration. 24

Similarly, for the next bit interval the results are: 26

TABLE M-2. RESPONSE TO RUN OF 1s 27

FQPSK-B, FQPSK -JR and SOQPSK-TG modulations respond to a run of 1s with an S(t) that is ideally, a pure tone at frequency fc-rb/4 Hz. This is referred as “lower sideband” mode. Similarly, a run of zeroes will produce a constant anti-clockwise trajectory spin and a tone at fc+rb/4 Hz (“upper sideband” mode). 27

4.0 Immunity to Carrier Phase Rotation 27

The equations at (M-3) and (M-4) are invariant with respect to cardinal constellation rotation as shown in the following: 27

27

The =0 case is decoded correctly by definition according to equations (M-5) and (M-6). At Table M- 1, when  =  there is no axis swap but the decoder is presented with 27

5.0 Initial Values 29

6.0 Error Propagation 30

7.0 Recursive Processing and Code Memory 31

An alluring decoding function can be derived by inspection of equations (M-5) and (M-6). Equation (M-5) can be rearranged as follows: 31

Here are two instances of a seemingly identical recursive relationship, i.e., the current code symbol is the difference between the current bit, the previous bit, and the inverse of the most recent code symbol from the current channel. We can consolidate these equations by converting to post-multiplex bit rate indexing, i.e., 31

31

from which we can immediately write the decoding function 31

The interested reader is left to confirm that equation (10) is indeed rotation invariant. 32

. 32

. 32

8.0 Frequency Impulse Sequence Mapping for SOQPSK 32

The so-called ternary alphabet is actually 2 binary alphabets {-1,0} and {0,1}, the appropriate one chosen on a bit-by-bit basis according to certain state transition rules. 32

9.0 Summary 35

There is no doubt in the author’s mind that well trodden ground has been traveled in this investigation. These characteristics were probably validated in reference [5] and by RF Networks Inc. before it incorporated the encoder in its model 5450F FQPSK demodulator product. Unfortunately, none of this work is in the public domain. 35

SYSTEM LEVEL SOFTWARE REFERENCE IMPLEMENTATION OF DIFFERENTIAL ENCODER DEFINED IN IRIG STANDARD 106 FOR FQPSK AND SOQPSK MODULATIONS 36

1.0 Introduction 36

2.0 Matlab Workspace Operation 36

3.0 Script For Modules 37

INdEX 46

Directory: legacy -> osmhome
legacy -> Ivan Allen Jr. Civic Responsibility Essay Contest
legacy -> Issued by Office of International Student Services Revised January 2010 table of contents
legacy -> U. S. Department of Justice Civil Rights Division Selected Accomplishments, 2013
legacy -> Antitrust division
legacy -> -
legacy -> Scientific Software Group
legacy -> Appendix recalling a personal best leadership experience
legacy -> Seting up an ip sec vpn
legacy -> Latency adtran submission to ntia/rus 4-13-09 Introduction