Some standard content:
ICS 75.180.10
Registration number: 8158—2001
Petroleum and natural gas industry standard of the People's Republic of China SY/T 6483--2000
Data record format for numerical control measuring instruments
Computerized logging system data record format2000-12～12 Issued
National Bureau of Petroleum and Chemical Industry
2001-06-01 Implementation
SY/T 6483—2000
1 Scope
Physical format
3 Logical format
4 File format
5 Direct format (EFLR)
6 Example format (IFLR)
7 Check and verify (CHECK Appendix A (Suggested Appendix)
Appendix B (Suggested Request)
Appendix ((Suggested Appendix)
Appendix I (Suggested Appendix)
Appendix E (Suggested Appendix)
Appendix F (Suggested Appendix)
Appendix G (Suggested Appendix)
Appendix H (Suggested Appendix)
Appendix (Suggested Appendix)
Appendix K (Suggested Appendix)
Rules for Using Indirect Format Logical Records··Rules for Using Indirect Format Logical Records
Glossary
Data Format
Logical Record Type Code
Replaceable Attributes
Characteristic Flags
Unit Symbol
Syntax Diagram of EFLR
Tape Physical Format
SY/T 6483—2000
This standard refers to the DLIS format issued by the Drilling and Production Applications Executive Committee under the Petroleum Exploration and Production Department of the American Petroleum Institute (API) to develop the data recording format for oil logging in my country. Appendix A, Appendix B, Appendix C, Appendix D, Appendix E, Appendix F, Appendix G, Appendix H, Appendix J, and Appendix K of this standard are all appendices.
This standard was proposed by China National Petroleum Corporation: This standard was issued by the Petroleum Instrumentation Professional Standardization Committee. The responsible drafting unit of this standard is Xi'an Petroleum Exploration Instrument Factory. The participating drafting unit of this standard is Daqing Measurement and Development Company. The main drafters of this standard are Luan Aofa, Zhang Yue, Chen Wenhui, Zhao Yangzhen, and the People's Republic of China Petroleum and Natural Gas Industry Standard CNC Logging Instrument Data Recording Format
Computerized logging system data recurd forinau This standard specifies the format for outputting and recording petroleum logging data. This standard is applicable to the data acquisition and exchange of CNC logging instruments during petroleum logging: 2 Physical format
SY/T 6483--2000
The physical format refers to a format for reading and writing data that can be recorded on a certain physical medium (tape, hard disk, CD, disk, etc.): Its basic structure is as follows:
Storage unit mark
Storage unit
2.1 Storage unit mark: Description of storage unit. It occupies 80 bytes, which are divided into: storage unit sequence number
version number
S bytes
storage unit structure
6 bytes
maximum record length
storage unit end
storage unit set identifier
60 bytes
2.1.1 Storage unit sequence number: the sequence number of the current storage unit. The first storage unit is 1, the second storage unit is 2, and so on: it occupies 4 bytes, represented by a 4-bit ASCII integer, right-aligned, and filled with zeros or blanks if it is not full. z.1.zVersion number: The version number of the record format: It occupies 5 bytes, expressed in the form of an ASC II string, and the version number is: Vn.in1, where; V is a fixed symbol;
n is the main version number;
nm is the modified version number, from 01 to .99.
2.1.3 Storage unit structure: It indicates the structure of the data record. It occupies G nodes, expressed in the form of an ASC II string. It is right-aligned and filled with zeros and blanks when it is not full.
2.1.4 Maximum record length: It indicates the maximum number of bytes occupied by the record: It is 5 bytes, expressed in integers, right-aligned, and filled with zeros and blanks when it is not full. It only indicates a range, and this value does not correspond to the actual length value. When the maximum record length value is equal to zero, it indicates that the record length is unclear; when the maximum record length value is a positive integer, it indicates the upper limit of the record length. 2.1.5 Storage unit set identifier: Description of the storage unit set, it is 60 bytes, expressed in ACⅡI characters, used to identify the storage unit set. It should meet the following requirements: the storage units in the storage unit set have the same structure; all storage unit marks in the storage unit set are the same; the serial number of the storage unit mark is from [; the storage unit set is a single logical format, and this storage unit set can be divided into several parts in sequence. If the th part is taken, it is included in the th storage unit. 2.2 Storage unit: Stores serial data, the number of serial record segments should be an integer, and the logical record length is unlimited. 2.3 Storage unit end: a mark of the end of data. For nine-track tapes, two consecutive tape labels are used to indicate the end. Approved by the State Administration of Petroleum and Chemical Industry on December 12, 2000, and implemented on June 1, 2001
3 Logical format
SY/T 6483—2000
The logical format can be divided into two record structures: direct format (EFLR) and indirect format (IFLR). 3.1 Structure of the logical format
Logical record segment,
Note: * is optional.
3.2 Segment Header
Segment Header
Logical Record Segment 2
Segment length, segment attributes and record type. The structure is as follows: Segment Length
2 bytes
Segment Attributes
1 section
Segment Tail
Logical Record Segment,
Logical Record Type
1 word
3.2.1 Segment Length: The total number of bytes in the record segment. It occupies 2 bytes and is unsigned. The value must be an even number to ensure the calculation of the 2-byte checksum; it does not limit the length of the logical record, but the length of the logical record segment must be no less than 16 bytes to simplify the mapping of the logical format to the physical format. 3.2.2 Segment attributes: Indicates the various characteristics of the logical record segment. It occupies one byte, and each bit is represented as follows: Bit name
0: Segment structure bit
Bit [: Segment before
Bit 2: Segment after
Bit 3: Segment Encryption bit
Bit 4: Segment rate packet bit
Bit 5: Segment checksum bit
Status and description
-==1, indicates indirect format logical record: when =1, indicates direct format reverse record
, this logical record segment is the first logical record segment; when =1, this logical record segment is not the first logical record segment; when =0, this logical record segment is the last logical record segment; when =1, this logical record segment is less than the last logical record segment logical record segment The record is not encrypted: when
is 0,
is 1, the logical record is encrypted. When
=U, this logical record has no encryption package; when
=1, this logical record has an encryption package.
The logical record is not checked. When
=1, the logical record has a checksum (the checksum value appears in the tail segment) Note
Bit name
Bit 6: Segment tail length bit
Bit 7: Segment filling bit
SY/T 6483-2000
(Continued)
Bit Status Description
Logical record has no segment tail length; when
=D,
=1, the logical record has segment tail length
=1, the logical record has no padding; when
=1, the padding byte appears in the segment tail
When the segment tail length bit=1, the logical record length value in the segment tail is displayed. The padding bit determines whether padding characters appear in the segment tail. The padding count and the padding count are checked first and then the length
3.2.3 Logical record type: Specifies the logical record type, which is 1 byte and is represented by an unsigned short integer [1.SHORT] Logical record type code See Appendix E (Reminder Appendix): 3.3 Segment Encryption Packet
Logical Record Segment Encryption Packet, if it exists, follows the Segment Header. Its structure is as follows: Encryption Packet Length
2 bytes
Company Code
2 bytes
Encrypted Information
N bytes
a) Encryption Packet Length: Encryption Packet Byte Length. It occupies 2 bytes and is represented by an unsigned integer (UNORM): It must be a number.
b) Company Code: Company Code: It occupies 2 bytes and is represented by an unsigned integer (UNORM)) Encrypted Information, the information that can be recognized by the manufacturer, can be any data format, it is composed of continuous sub-bytes, starting with the 5th byte, and is N bytes long, which is optional. 3.4 Segment Body
It is composed of logical records, composed of continuous bytes, and follows the Segment Encryption Packet directly. If the Segment Encryption Packet does not exist, it follows the Segment Header directly.
3.5 Segment tail
Logical record indicates the end of segment. It consists of padding, checksum of two consecutive bytes and a segment tail length group. 4 File format
Logical file consists of multiple logical records, starting with a file header logical record. When the second file header logical record is encountered or there is no other available logical record, this logical file ends. File header record is a special logical record in logical record. File header logical record must consist of a logical record segment, which mainly describes the relevant information of various records. The structure is as follows: No. 1 file header logical record
No. 2 file header logical record
Logical record
Logical record
Logical record
Logical record 2
Logical record 2
Logical record 2
Logical record.
Escape record y
Avoidance record,
5 Direct format (EFLR]
SY/T 6483—2000
The record body of EIR describes a single object device in the form of a component sequence: the direct format is a self-describing format that does not require other logical records to escape the line explanation period. The code table of the global and local records of the direct format can be found in Appendix F: (prompt record).
5,1EFLR structure (see Figure 1)
Direct format reverse record
Device class
Attributes,
Properties,
Attributes,
Properties.
Figure 1EFLR structure
EFLR layer variable length record body, which can be divided into multiple logical record segments. Each FFIR encapsulates an information table: and there can only be one device class. The template describes the attributes, order and default properties of various objects in the device class. The two templates allow multiple objects and each object has multiple attributes. And allow The attribute value of the object is zero or missing: 5.2 Component structure
FFLR is represented by components, and each component carries information describing the entity: a) The composition of the component is as follows:
Component type
3-bit
Component format
Component description) 1st byte
6 The component type is represented by a 3-bit unary number 0-2 bits, allocated as follows: 0-2 bytes
Component type name
Unrestricted attributes
Attribute component
Fixed attribute component
Object component
Operation determined by type and format
N bytes
TagbzxZ.net
ABSATR
AITRIB
INVAFK
OBJECT
0~-2 bits
SY/T 6483—2000
(Continued)
Component type name
Redundant device component
Replacement device component
Device component
Tag
c) The component format uses a 5-bit binary number to represent bits 3 to 7. If the component type is a redundant device component (101), a replacement bone component (110), or a device component (111), bits 3 to 7 are represented as follows: 3--7 bits
Bit 4 = 1
Type of object in the device
Feature representation code
If the component type is an object component (011), bits 3 to 7 are represented as follows 3--7 bits
Bit 3 = 1
Object name
Feature representation code
Global default feature value
Global default feature value
If the component type is an attribute component (001) or a fixed attribute component (010), bits 3 to 7 are represented as follows: 3--7 bits
Bit 3 = 1
Bit 4 = 1
Bit 5 = 1
Bit 6 = 1
Bit 7- 1
Identifier
Count and
Indicator
Feature indicator
VSHORT
Global missing feature value
Feature symbol
Feature symbol
Feature symbol
1) Function and use of components:
SY/T 6483—2000
1. Device component: indicates the beginning of a device. It must be the first component in the EFLR. In the device component, there must be a device type and a device name (the device type cannot be empty, and the device name can be arbitrary). Objects in the device share a set of common attributes. The order and default characteristics of these object attributes are defined in the template. Immediately after the template device component, the appearance of the object block indicates the end of the template. The template consists of attribute components and fixed attribute components, which define the structure of objects in the device. 1. Object component: indicates the beginning of a new object. The object component must have an object name. The sequence of attribute blocks and non-attribute components follows the object component. The appearance of other object components indicates the end of the object attribute component. 1. Attribute components: In the template, attribute components define the local default characteristics of all objects in the device. When the attribute component characteristics do not exist in the template, the global default values are used. 1. Fixed attribute components: Fixed attribute components only appear in the template, indicating that the attribute characteristics of all objects in the device are fixed: Therefore, these fixed attribute components do not need to appear after the object component. Non-attribute components: If the attribute block of an object is replaced with a non-attribute component, the object's extensibility does not exist. The attribute component does not provide any information and has no default meaning: 1. Redundant device component: represents the backup of the device. All contents in a device (device name, device type) are copied in advance to the same logical file. If the redundant device name is empty, all contents are copied to the same logical file of the same type (other redundant devices and pre-given redundant devices should be excluded) 2. Replacement device component: represents the replacement of the original device: the type, name (non-empty), template, object (no addition or deletion) and sequence of the replacement device should be the same as the replaced device, and written in the same logical file. The replacement device can be written anywhere in the logical file, but must be after the source device. The replacement device component provides the function of modifying the source device. A given source device can have any number of replacement devices.
All components in the template must have a clear non-empty tag. All attributes in the same "column" in the device class must have the same attribute flag. This flag is indicated by the attribute component in the template. Therefore, the attribute component following the object component does not need to be marked with the right attribute. The reserved features can be specified directly using the object attribute component. For features that do not appear, the local default value specified by the corresponding attribute component in the template is used. The absence of an attribute component block means that the corresponding attribute feature value uses the local default value. The order of attributes in a device is very important, and the only attribute component that can be omitted is the last attribute component: e) Component syntax:
Syntax: 'ax (indicates a character in IDENT format or ASC format) Where: "n" represents the number of characters from a to x; "" represents a separator;
"" represents IDENT format or ASCI format, Syntax 2: K&in'a\x (indicates copy) Where: "n" is the same as syntax 1;
"a...x" represents an identifier represented by ORNAME format; "K" represents the source reference number:
\" represents the number of copies;
"" represents a separator.
5.3 EFLR logical record classification
EFLR includes 12 types of logical records, including file header logical record, source logical record, axis logical record, long name logical record, path record, frame logical record, static data logical record, unformatted data description logical record, replacement logical record, specification logical record, dictionary logical record, and original information logical record. Among them, the header logical record must be defined. For the usage rules of various records, see Appendix A (suggestive appendix).
Indirect format [ITR]
SY/T 6483--2000
IFI.R includes frame data logical record, unformatted data record, unformatted data identification record, and data end record: For the usage rules of various indirect format logical records, see Appendix B (suggestive appendix). 7 Checksum (CHECK SUM)
The checksum is usually in the record segment, which contains each bit of the logical record segment before the checksum (checksum value, segment length is not included in the checksum. If encryption is used, the logical record segment body and padding bytes are encrypted before the checksum calculation. The checksum is represented by a 16-bit integer and is calculated using a cyclical checksum algorithm. SY/T6483—2000
Appendix A
(Suggested Appendix)
Direct format logical record usage rules
Direct format logical record usage rules are as follows A1 Header logical record FII.R| |tt||As the beginning of a file, it is the identification mark of a logical file, device type: FILE-HEALDER.
Object: File Header (FILE1AER).
Object properties: Description (ISCRIPTION), attribute extension (EXTE>DED: ATTRIBOTES), file sequence number (SEQLEVCE-NUMBER), identification (ID), storage device end (ENDOFSTORACESET), standard code (CONTENT-STANDARD-OIE), standard version (YONIENI-STANDARD-VISION) and other 7 attributes
A1.1 File Header Object FILE-HFAIFR ORIFCTS records the definition of various parameters:
LLSCRIPIION attribute: description of the file object: attribute value characteristic code: C-1, R-ASCⅡ
LXIENDLDATTRIBOIFS attribute: attribute extension of the file object. Attribute value characteristic code: R-ORRE.
SEQUJENCE-NUMIBER attribute: indicates the location of the logical file in the storage device: the file sequence number is represented by an ASCⅡ positive integer, the field width is 10 bytes, and it is right-aligned: if the left side is insufficient, it is filled with spaces. The current file sequence number must be greater than the previous file sequence number. The th file sequence number can be a meaningful positive integer. This attribute value must be meaningful. ID attribute: describes and identifies a file. Attribute value characteristic code: C-1, R-ASCⅡ
-END (FSIORACE·SFT extension: The end flag of the storage device. When the value is 1, it indicates that the storage device has ended. When it is 1, the legacy file may be empty, attribute feature code: C=1.R=STATUS.
CONTEVTSTANLIARDCODE attribute: agency standard code: attribute value feature code: R=ULONG:
ONTFVT-S[ANIARD-NAME attribute: agency standard name, related to the agency standard code: series of agency standard names
attribute value feature code: R=IFNT
(X)NTENT-STANDARD-EDITI)N attribute: related to the agency standard code - a series of agency standard versions, attribute value feature code: R=IDFNT,
A2 source logical record OLR
indicates the relevant original environment conditions required when generating logical files. It provides a method for identifying different entities in different environments.
Device type: ORIGIN.
Contains device type: WELLRE-ERENCE·IOINT object: source object (ORIGIN), well reference point object (WELL-REFERENCEPOIVT): 181
AZ.1 object ORIGIV
SY/T 6483—2006
Indicates the basic environment when the logical component is generated. Each logical file must have at least one source device and one or more source objects: The first object in the source device is the definition of the source: The corresponding logical file is called a file. It contains: description (IECRIP-T[ON), attribute extension (EXIENDED-ATTRIYIES), file identifier (FIE-IL), file device name (FILE-SFI-NAME), file device F (FLE-SF『-NUMIER). File number (FILENLIMHR), document type (FIEF-TYPH), product name (PROIJUJC), version (VERSI)N), program (PROXGRAMS), creation time (CRFATION-TIME), file count number (ORIER-TM), user allocation number (DSCENT-NMBER), run number (RUN-TMRER), well identifier (WELI- The following are the components of the system: ID) and name (WELL-NAME), well site (FIELI-NAMF), operator name (COMPANY), factory code (PRODUCER-YODE), manufacturer name (PRODUCER-NAME), version number (VISION), dictionary name (NAME-SPACE-NAME), dictionary version (NAME-SPACE-VLRSIO), organization code (SCHEMA-CDE), organization name (SCHEMA-ORGANZAT[ON), organization version (SIEMA-EDITIN), organization dictionary version (SIEMA-DICTIONARY-HITON), unit module code (UNITMOIHL-CODE), unit module name (LNITMCODELNAMF), unit symbol version (UNIT-SYMEOLS-EIITEON), dictionary code (NAMESPACE-NAME), dictionary version (NAMESPACE-VLRSIO), organization code (SCHEMA-CDE), organization name (SCHEMA-ORGANZAT[ON), organization version (SIEMA-EDITIN), organization dictionary version (SCHEMA-DICTIONARY-HITON), unit module code (UNITMOIHL-CODE), unit module name (LNITMCODELNAMF), unit symbol version (UNIT-SYMEOLS-EIITEON), dictionary code (NAMESPACE AGE (OIF), universe name (NAMFSPACE-NAMH), organization name (NAMESACE-OPGANIZATION), organization F code version number (NAMESPACE-FDIIION, source object flag, (REMARK), source object attribute definition (UNTEXT) and other 36 attributes. sRN attribute: description of the source object:
attribute value characteristic code: =1, R-AS,
-EXTENLEI)-ATTRILXYIFS attribute: attribute extension of the source object. Attribute value characteristic code R-OBIRE,
FILE-ID attribute: describes and identifies a file: attribute value characteristic: C-1, R=ASCI
-FILE: SET-NAM attribute: the name of the file device. The name of a file device cannot be repeated with the name of other file devices.
attribute value characteristic code: C=1, R= IDRVT. -FII.F-SET-NLCMHER attribute: the file device number: it is used to distinguish different file devices and logical files that are not in the file device. All the files in a file device are the same, this attribute must be defined: attribute value characteristic code: C=1, R-UVARI
FIIL,F-NLCMHER attribute: the file number of the parent file of the file device described by the file device name attribute: the file number must be expressed in numbers. The file numbers in the file device are preferably sorted in ascending order. Attribute value characteristic code: C-1, R-VARIIVARIFILE-TYPF attribute: the environment information when the file is delivered or the basic content of the parent file. It is defined by the manufacturer. Attribute value characteristic code: C=1, R-IFVT. -PROIUCT attribute: the name of the software product. Attribute value characteristic code: C-1, R=ASCII
-VERSON attribute: the version number of the software product: Attribute value characteristic code: CI, RA.
-PROGRAMS attribute: program name table. The software defined by the product attribute. The program name table should include operation procedures, maintenance procedures, etc.
Attribute value feature code: R=AS!
--CREATN-TIV positive attribute: the date and time attribute value of the parent file. Characteristic code: C-1, R=DTIM.
--ORDLRTIME attribute: the count value of the parent file when it was created.
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.