|
IRIG 106-99 CHAPTER 9 - TELEMETRY ATTRIBUTES TRANSFER STANDARD 9.1 General 9.2 Scope 9.3 Purpose 9.4 Media and Data Structure 9.5 Telemetry Attributes 9.5.2 General Information (G) 9.5.3 Transmission Attributes (T) 9.5.4 Tape Source Attributes (R) 9.5.5 Multiplex/Modulation Attributes (M) 9.5.6.1 PCM Format Attributes (P) 9.5.6.2 PCM Measurement Description (D) 9.5.6.3 1553 Bus Data Attributes (B) 9.5.7 PAM Attributes (A) 9.5.8 Data Conversion Attributes (C) 9.5.9 Airborne Hardware Attributes (H) TELEMETRY ATTRIBUTES TRANSFER STANDARD 9.1 General Telemetry attributes are those parameters required by the receiving/ processing system to acquire, process, and display the telemetry data received from the test item/source. The Telemetry Attributes Transfer Standard (TMATS) provides a common definition and format to facilitate the transfer of information between the user and the test range and between ranges. The telemetry attributes are defined such that the information required to set up the telemetry receiving and processing equipment is provided. The format, while not necessarily compatible with any receiving/ processing system, will allow test ranges or other receiving systems to develop a computer conversion program to extract the information and to set up data required for their unique equipment configuration. Nonstandard parameter variations are not included in the attribute listings of choices but may be included by exception in the comments section of each group. The intent of this chapter is to cover primarily attributes and terminology included in or consistent with the other chapters in document 106. For example, PCM format attributes should comply with the PCM standards as given in chapter 4. Other attributes are included, at times, for service and utility, but should not be construed as endorsements apart from the other 106 chapters. 9.2 Scope The TMATS provides the definition of the telemetry attributes and specifies the media and data format necessary to permit the ready transfer of the information required to set up the telemetry receiving/processing functions at a test range. The standard does not conform to nor does it define existing or planned capabilities of any given test range. Only those parameters which are defined in this document are included by specific reference. Other nonstandard parameter values/definitions may be included in the comments section of each group. 9.3 Purpose The TMATS provides a common format for the transfer of information between the user and a test range or between ranges (see appendix H). This format will minimize the "station unique" activities that are necessary to support any test item. In addition, it is intended to relieve the labor intensive process currently required to reformat the information by providing the information on computer compatible media, thus reducing errors and requiring less preparation time for test support. 9.4 Media and Data Structure 9.4.1 Physical Format 9.4.2 Logical Format  A variety of physical and electronic media
are currently available for use in exchanging attribute information. The most
important factor in selecting which medium to use is that the parties involved
must agree to the specific medium of choice. If any data compression (such as
Backup/Restore or Zip/Unzip) will be used, both parties should agree to its
use.A cover sheet describing the system which produced the attribute medium should accompany the attribute information. A recommended format for the cover sheet is given in appendix I. 9.4.1 Physical Format. Attributes for each mission configuration are to be supplied in a single physical file with contents as 7-bit ASCII coded characters. Line feed (LF) and carriage return (CR) may be used to improve readability of the information. Nonprintable characters will be discarded by the destination agency prior to translating the attributes into telemetry system configuration information. For disks, multiple mission configurations
may be provided on a single disk; however, each configuration must be in a
separate file identified in the disk directory. File names should use the file
extensions .TXT to indicate a text file, or .TMT to indicate a TMATS file. A
stick-on label and the accompanying cover sheet identify the file names
corresponding to the mission configuration used for each mission.On magnetic tape, physical records may be any size up to 2048 bytes. A single end-of-file (EOF) mark indicates the end of a mission configuration. Additional mission configurations can be included in sequential files on a single tape. A double EOF is used to indicate the end of the last mission configuration on the tape. A stick-on label and an accompanying cover sheet identifying the missions for each configuration are required.
9.4.2 Logical Format. Each
attribute appears in the file as a unique code name and as a data item. The
code name appears first, delimited by a colon. The data item follows,
delimited by a semicolon. Thus an attribute is formatted as A:B;, where A is
the code name and B is the data item, in accordance with the tables in
paragraph 9.5. Numeric values for data items may be
either integer or decimal. Scientific notation (± d.ddddddE± ee) is allowed
only for the specific data items defined for its use in the tables in
paragraph 9.5. For alphanumeric data items, including
keywords, either upper or lower case is allowed; all defined keyword values
are shown as upper case and enclosed in quotes in the tables in
paragraph 9.5. Semi-colons are not allowed in any
data item (including comment items). Any number of attributes may be supplied
within a physical record subject to the maximum mentioned in
subparagraph 9.4.1. Attributes may appear in
any order.There are two basic types of attribute code names: single and multiple entry. Single-entry attributes are those for which there is only one data item. Multiple-entry attributes appear once in the definition tables in paragraph 9.5 but have multiple items; these items are assigned a number. The number appears in the code name preceded by a hyphen. For example, data source identifiers might have the following entries: The code name COMMENT may be used to
interject comments to improve readability. (Note that the comment data items,
such as G\COM, are intended to convey further details within the TMATS file
itself.) Comments must follow the attribute logical format, as shown below:
Refer to paragraph 9.5 for detailed definition of code names and attributes and appendix J for an example application of this standard. 9.5 Telemetry Attributes 9.5.1 Contents 9.5.1.1 Organization 9.5.1.2 Group Relationships 9.5.2 General Information (G) 9.5.3 Transmission Attributes (T) 9.5.4 Tape Source Attributes (R) 9.5.5 Multiplex/Modulation Attributes (M) 9.5.6 Digital Data Attributes 9.5.6.1 PCM Format Attributes (P) 9.5.6.2 PCM Measurement Description (D) 9.5.6.3 1553 Bus Data Attributes (B) 9.5.7 PAM Attributes (A) 9.5.8 Data Conversion Attributes (C) 9.5.9 Airborne Hardware Attributes (H) The description of the mission configuration includes all potential sources of data, RF links, pre- or post-detected analog tapes, or onboard recorded magnetic tapes. Each of these have unique characteristics which must be defined. Each source is given a unique identity and its characteristics are specifically defined in associated attributes fields. In multiplexed systems, each data stream is uniquely identified by a data link name, which, in turn, is related to the data source name. |
Only the information which is essential to define the attributes of a
system is required. Nonapplicable information does not need to be
included in the file. However, all attribute information given is to be
provided in the specified format.
|
The attributes defined in this section proceed from the general level to the
detailed level. The groups defined, in terms of data to be entered, are
described next.
9.5.1.1 Organization. Attribute information is organized according to a hierarchical structure in which related items are grouped and given a common heading. The number of levels varies within the overall structure and is a function of the logical association of the attributes. At the highest level, the telemetry attributes are defined for the following groups: |
| Title | |
| General Information | |
| Transmission Attributes | |
| Tape Source Attributes | |
| Multiplexing/Modulation Attributes | |
| PCM Format Attributes | |
| PCM Measurement Description | |
| 1553 Bus Data Attributes | |
| PAM Attributes | |
| Data Conversion Attributes | |
| Airborne Hardware Attributes |
|
Within the structure, a lower case letter, for example, n, p, or r, indicates
a multiple entry item with the index being the lower case letter. The range
of these counters is from one to the number indicated in another data entry,
usually with the appendage \N.Within the tables, the code name,
definition, and maximum field size are given for each individual attribute.
The maximum field size is intended to be a guideline indicating the intended
use of the attribute, and does not imply support of the maximum by any and
all ranges. For example, the fact that the Number of Data Sources attribute
is 2 characters long does not mean that 99 data sources are supported. Each
range should be consulted as to their specific capabilities. 9.5.1.2 Group Relationships. The interrelationships between the various groups are shown pictorially in figure 9-1. |
|
1. Data Source ID is unique within a General Information Group
(G). It ties the Transmission Group (T) or the Tape Group (R) or both to
the G group and to the Multiplex/ Modulation Group (M).
2. The tie from the M group to a PCM Group (P), a PAM Group (A) or
a 1553 Bus Group (B) is the Data Link Name. 3.
The tie from the P group to an embedded P group is another Data Link
Name. 4. The tie from the M group to the
Data Conversion Group (C) for an analog measurement is the Measurement
Name. 5. The tie from the P group to the
PCM Measurement Description Group (D) is the Data Link Name.
6. The tie from either the A, D, or B groups to the
Data Conversion group is the Measurement Name.
|
|
|