Can any one tell me that from where i can find the purpose of each file / Directory in Mark-V Control System. e.g TC2KREPT what it is use for?
It is just for an example.

 

GEH-5980, Speedtronic Mark V Maintenance Manual, Sect. 4.4, 4.5, and 4.6 has some very good clues as to what many of the files do.

TC2KREPT.TXT is just an ASCII text file that was produced when the unit-specific software was written to list what inputs and outputs were connected to which I/O terminal boards and what CDB (Control Signal Database) names (points) were associated with each input an output. Another name for this file is the I/O Report. (In fact, the first characters in this file spell IO Report.)

It must be noted that this file is <b>***NOT***</b> linked to any other file by any application, not automatically, and not manually. It is simply a file that was produced when the I/O assignments were made during the original unit configuration. If inputs and/or outputs were added to the Mark V, deleted from the Mark V, or moved to other termination point(s) in the Mark V <b>this file was not automatically modified to reflect those changes.</b> Full Stop.

There was no application or executable which could be run to look at IO.ASG or any file on the operator interface to compare, modify, or produce TC2KREPT.TXT. If I/O was added, deleted, or moved <b>it was incumbent on the individual making the change(s) to manually edit TC2KREPT.TXT to reflect the changes.</b>

Now, this question has been asked before on control.com, however it was many years ago and I can't seem to locate it in the archives. So, here are some of the file descriptions:<pre>
IO.ASG I/O Assignment (<b>ABSOLUTE</b> definition of what signal name is assigned to what input or output)
FACTORY.ASG Factory Software Signal Name assignment (definition of non I/O-related software signal names made during the original configuration)

SITE.ASG Software Signal Name assignment (definition of non I/O-related software signal namess added in the field)
ALLOCSSP.ASG Structured Software Signal [Point] Name Allocation (definition of structured software signal names, including Process Alarms; structured software signals are signals which must reside in particular memory locations and are not free to be assigned to any spare memory location)

ENUMDATA.DAT Enumerated Data Display definition file (defines the text messages displayed for Enumerated Data signal names)
*.SCA Scale Code Definition Files (English, Metric, Hardware, Custom)

UNITDATA.DAT Unit Data Dictionary File ("Master" Signal definition file for unit configuration)

ALARM.DAT Process- and Diagnostic Alarm Messages

ALARM.LST List of Process Alarms and the logic signals which drive the annunciation of them

CSP.PRN Control Sequence Program ASCII Text Printout File

CSP_XREF.PRN Control Sequence Program Cross-reference file

ACALIB.DAT AutoCalibrate Configuration File

SYNC.DAT Synchronizing Display Configuration File

IO_CFG.LST ASCII Text file of I/O Configurator Displays and values

IO_CFG.PRM ASCII Text file of I/O Configuration Parameters

MODBUS.DAT MODBUS Data definition file

SCLEDATA.DAT As-running Scale Code File

MSTR_SEQ.CFG ASCII Text definition of CSP Segments to be compiled for use in CSP

SEQ_*.SRC ASCII Text source files for CSP segments

IOCFG_*.DAT Intel HEX Format I/O Configuration definition file

*.A or *.An Animated Display Definition ASCII Text definition files
</pre>
Those are the files I didn't see described very well in cited sections of the Maint. Manual. The rest of the files are Table Files, and they are described in the EEPROM Downloader section of the Maint. Manual.

On an <I>, the Table Files are compiled into files with a .DAT filename extension with the same filename.

On a GE Mark V HMI, the Table Files are compiled into files with a .AP1 filename extension with the same filename.

You may find other files in that directory, but the ones above (with the exception of the Animated Display Item List files) are required in F:\UNIT1 for proper operation and configuration of a Mark V that uses AutoCalibrate and can automatically synchronize a breaker.

Some Mark V panels use a processor-specific LVDT calibration method. In that case there may be some additional files which are required for operation, and they are usually IOCFG_AC.R, IOCFG_AC.S, and IOCFG_AC.T, which may be found in the directory. They are ASCII text files used by the I/O Configurator to obtain processor-specific LVDT calibration. Technicians calibrating LVDTs will enter the processor-specific LVDT calibration parameters in these files and the I/O Configurator will incorporate them into processor-specific I/O Configurator files for downloading.

The exception, and has been said before on control.com, there's always an exception (or two, or three, or four, or more) for a Speedtronic panel, is that TC2KREPT.TXT is not required for anything; it's just a file that is left over from configuration at the factory and was hopefully modified in the field by anyone making additions to or deleting or moving inputs and outputs of the Mark V turbine control panel.

A lot of people improperly leave troubleshooting files in this directory. Which can make it very large and difficult to compress to a single floppy.

If you have questions about any other files which weren't covered here, or more specific questions about any of the files above just let us know.