IEEE C37.232-2011 IEEE Standard for Com mon Format for Naming Time Sequence Data Files (COMNAME).
I)uration: The duration is equal to the time difference between the first and the last samples in the file.
This time difference can be for up to I ms or up to a number of years. Two user fields are required in order
to support the duration value. The fields shall be formatted in the same way as the Start Date and the Start
Time fields. The duration can be specified to the needed precision and leading zeros are necessary.
For example, a file with I mm and 39 s (i.e., 99 s) of data will have a duration code of “000000. 000139”. A file with contents covering a period of 2 years, I day, I mm, and 39 s of periodic data measurements will have a duration code of “020001, 0001 39”.
Type: This field may be used to describe the type of originating event. For example, the code “AG” can be used to indicate that the file contains data for a Phase-A to Ground fault. Or the code “LOG” can be used to indicate that the file contains periodic readings of load and other data (such as temperature): the code “SEW’ can be used to identify a sequence of events file; the code ‘TST” can be used to specify that the file was created for relay testing and maintenance operations: and so on.
Geographic Position Coordinates: Two user fields are required in order to support position information. The first field is an expression of latitude in degrees, a comma delineator, and the second field is an expression of longitude in degrees. Leading zeros arc necessary. The two Geographic Position fields can be carried to the resolution desired as per the discussions on position information shown in 4.7.
User fields are not a problem to the originators of the TSD files because they obviously know which
field(s) they are using. Upon passing the files to another party, the other party may recognize the fields by a
quick inspection of the definition tile as shown in Clause 6.
4.5 Extension field
Extension: The exact field definition is up to the user. however, the extensions .DAT, .CFG, .IIDR, and .INF are reserved and used to indicate that the file is compatible with IEEE Sid C37.1 1 lTMl999 [B6]. There are no other reserved extensions; however, the previously noted restrictions shall be observed, Users shall avoid using .EXE. .BAT, .SYS, .COM. .DLL, or any other commonly known extension for naming TSD files.
4.6 Examples of the file naming convention
The following filename example uses only the required fields and contains a total of 42 characters. The Start Time field is given in millisecond resolution. It is an IEEE C37.lll configuration file:
000809,1 75215183,-4, sta80, ben 717, n yiso. cfg
The following filename example contains 58 characters. The Start Time field is given in a tenth of a second resolution, and there are three additional user fields being used for duration (95.9 s) and file type:
000809,1752 152,-4, s ta8O,benhl 7, n yiso, 000000,0001359, uf. cfg
IEEE C37.232 pdf download.