CHAPTER 10

DIGITAL ON-BOARD RECORDER STANDARD

2005

10.3 Operational Requirements

This section of the standard specifies the basic operation and required interfaces for the Data Storage and Download.

10.3.1 Required Configuration.

A recorder, as a minimum, shall provide the following functionality:

  1. Download port
  2. Control/Maintenance port
  3. External power port

The required download port interface shall be IAW section 10.4 This combination will allow data extraction and transfer from any recorder to any section 10.4 compliant intermediate storage unit.

10.3.2 Exclusions to Standard.

The physical size, configuration and form factor for the recorder and/or the RMM are not controlled by this standard. Due to the variation in capacity/rate/cost requirements of the users, this standard does not specify the technology to be used in the RMM or the recorder.

10.3.3 Internal System Management.

Any processing performed on the stored data by the ecorder (e.g. for the purposes of internal system management, error detection and correction (EDAC), physical frame formatting, etc.) shall be removed from the stored data when the stored data is downloaded or transferred from storage media.

10.3.4 Data Download.

The data acquisition recorder may have an RMM capability or the recorder can be removed from the acquisition platform and taken to a ground station for data download. Reference paragraph 10.4.1 for recorder electrical interface and paragraph 10.9 for RMM interface.

10.3.5 Data Download File Extension.

Upon data download to a host computing platform, all IRIG 106 Chapter 10 compliant recordings shall use the file extension *.ch10 (or *.c10 extension for use on systems with a 3 character extension limit). The use of this standard extension will indicate that any file on a ground computing or storage platform is in compliance with this standard (defined in section 10.6).

10.3.6 Data Download Structure and Naming.

Upon data download to a host computing platform all IRIG 106 Chapter 10 compliant recordings shall use the following structure and naming conventions unless host computing platform operating system imposes naming length limits. In this case the directory and file names are to be truncated after the last component, which completely fits within the name length limit:

  1. Data Recording Directory Name. Each directory block from a RMM to be downloaded to ground computing or storage platform shall use Section 10.5, Table 10-2 VolName as the directory name where the Data Files will be placed. The directory name shall use lower case alpha characters.

    Note: If the VolName is empty (0x00) a default name or user-defined name shall be used. If used, the default name shall be ch10dirnnn, where nnn is the sequential directory block count.

  2. Data File Name. Each Data File contained within a Directory Block on the RMM to be downloaded will be placed in the Directory identified in paragraph 10.3.6.1 and shall use the following naming convention. The data file name shall use lower case alpha characters:

    "filennnn"; where nnnn is the sequential RMM file count from each Directory Block File Entry (must be 8 alpha-numeric characters). Example "file0001", "file0002", …"file9999". If available "File Create Date", "File Create Time" and "File Close Time" from Section 10.5, Table 10-3, DDMMYYYY_HHMMSSss_HHMMSSss (8 numeric characters for File Create Date, 8 numeric characters for File Create Time separated by an underscore ASCII character code 0x5F, and 8 numeric characters for File Close Time). No spaces or other non-numeric characters allowed). Example 02092004_21302731_21451505. If the "File Create Date", "File Create Time" and "File Close Time" from Section 10.5, Table 10-3 values are not available and are filled with 0x30 then the system time from the host download platform will be used for "File Create Date" and "File Create Time" (DDMMYYYY_HHMMSS). "File Close Time" will not be used. "File Close Time" shall be replaced with "sys_time".

    A structure example follows:
    ...\VolName\FileName_FileCreateDate_FileCreateTime_FileCloseTime
    VolName not empty example:
    ...\\file0001_02092004_21302731_21451505.ch10
    VolName empty default example:
    ...\ch10dir001\file0001_02092004_21302731_21451505.ch10
    VolName empty user defined example:
    ...\\file0001_02092004_21302731_21451505.ch10
    Date/Time not available (0x30 fill) example:
    ...\file0001_02092004_213027_sys_time.ch10

The use of this standard recording and file naming convention will indicate that any file on a ground computing or storage platform is in compliance with this standard.

10.3.7 IEEE-1394b Interface to Recorder Media.

Serial Interface to recorder media shall be accomplished utilizing IEEE-1394b interface. A nine-pin IEEE-1394b interface shall be provided on the media to allow direct download of data to host computer or storage device.


Warning: Undefined variable $CommentsTitle in /web/irig106/comments/show.inc on line 37

add a note add a comment User Contributed Notes and Comments
No user comments yet
add a note add a comment  
Irig106.org Home