IDOS schedules the <I>’s microprocessor tasks in order to support the operation, control and protection of the turbine and driven device. IDOS is priority-based and interrupt-driven with preemptive scheduling. Tasks are scheduled with a priority code of 0 to 15, with priority 0 as the lowest and priority 15 the highest. Because of its interrupt-driven, preemptive nature, an interrupt with a higher priority code takes precedence over other tasks being executed at the time the interrupt is received. MS-DOS, which runs under IDOS on the <I>, has a priority code of 4. Optimum priority scheduling is done by GEDS and cannot be configured by the user.
When invoked during the start-up (via the AUTOEXEC.BAT file), IDOS becomes the top-level operating system. Its main purpose is to enable real-time communications with the control panel(s), particularly for alarm annunciation purposes. Several precautions should be taken when loading and running other DOS-based programs on the <I>. The use of RAM disks is not recommended as the amount of extended memory available on a typical factory-configured <I> does not accommodate RAM disks. <I> operation is not increased by expanded or extended memory managers and they are not recommended.
The use of RAM disks, memory managers, and programs requiring expanded or extended memory may cause memory resource allocation problems when run under IDOS and is not recommended. Installation of
software not supplied or authorized by GEDS may adversely affect system performance.
3-2.1. Root Directory
The top level or root directory of the <I> system’s C: drive contains the following minimum files:
AUTOEXEC.BAT is the batch file executed automatically upon start-up to run the IDOS operating system and enable the menu and display system of <I>.
COMMAND.COM is the command processor that reads, analyzes and performs computer instructions entered from the keyboard at the DOS prompt ( > ).
MSMOUSE.COM is used to enable the mouse or trackball. CONFIG.SYS contains PC configuration commands.
NOTE
Modifying the AUTOEXEC.BAT file, the CONFIG.SYS file, or deleting, renaming or moving files or directories provided with the <I> without the consent of GEDS is not recommended.
3-2.1.1. DRIVE F: FILES. The top level of the pseudo drive F: contains the following site-specific configuration files: CONFIG.DAT is the master site configuration file. It specifies items such as how many units exist on the site and the
unit names and subdirectory names containing all the unit specific information. It also contains network information about what communication links exist out of the <I> and which units can be reached on those links.
ARCNET.DAT contains information necessary for configuring/enabling the ARCNET card for communication with the
Mark V through the Stage Link.
IO_PORTS.DAT contains information about the configuration of the parallel and serial ports of the <I> for communicating with printers and MODBUS communication links.
DYNAMIC.BIN contains dynamic system settings such as logging, passwords, etc.
3-2.1.2. DRIVE F: SUBDIRECTORIES. Subdirectories on the drive F: contain the following information/files:
\RUNTIME contains all the runtime data files created by programs running under IDOS. Programs check this directory for display-related data files (User Defined Displays, Main Menu, Logic Forcing recall points, Trip History data, etc.).
Configuration files in the F:\RUNTIME subdirectory include:
*.A0, A1, A2,...A8 contain specific code defining the animated displays.
A0 Generic
A1 Unit 1
A2 Unit 2
A8 Unit 8
MENU.DAT contains information defining the layout and the displays available from the Main Menu. DEMANDnn.BIN contains user-defined Display Menu definitions
\USER is the default subdirectory specified in the AUTOEXEC.BAT file run during start-up of the <I>. Some programs create data files in the current default directory such as screen copy programs. If the current default directory has not changed, the data files output by these programs could be found here.
\UNITn is created for each unit being controlled by an <I>, where n is equal to the unit designator number (up to a maximum of eight units/subdirectories). Files which make up the Data Dictionary and EEPROM images for a unit are stored in its unit- specific directory and should always be kept there.
The files in each unit-specific subdirectory which comprise the Data Dictionary for each unit are as follows:
SCLEDATA.DAT contains the pointname scaling data information used to convert signal data from raw binary units to
engineering units for display on the <I>.
UNITDATA.DAT contains basic information about each signal (logic or real) of the unit, including its name, memory location, point type, scale code, command information, and internal point number.
ENUMDATA.DAT contains the enumerated data strings for the enumerated data types. Enumerated data is used to "describe" the operational state of the unit such as OFF, SYNCHRONIZING, LOADING, COOLDOWN ON, etc. ALARM.DAT contains the text messages for each Process Alarm drop and for each Diagnostic Alarm drop.
\UNITn\PROM are Mark V Control Panel processor PROM-related files. They are used by IDOS programs such as the I/O Configurator, the CSP Documenter, the Control Sequence Editor, the Control Sequence Compiler, and others. The files in
CAUTION
this sub-directory must match the BBL and memory location information stored in the processor PROMs for proper configuration and operation of the Mark V Control Panel.
3-2.1.3. DRIVE G: SUBDIRECTORIES. Subdirectories on drive G: contain the following information/files: \EXEC contains all the executable files/programs that form the basic <I> and any batch files used during start-up or
execution.
\DATA contains any data files which programs require that are not site-specific. It also contains any generic data files which might be used before any site-specific data files are created. Programs using data files look for and use any files found in site-specific directories on drive F: first. They only use the generic data files if no site-specific files can be found.
\LOG contains the output from various programs which might be important for debugging or troubleshooting purposes. Error log files and normal start-up files are stored here.
\CONFIG contains the site and unit configuration files. See Section 3.2.1.1.
3-3. <I> HARD DISK BACK-UP
To prevent permanent loss of valuable data and work, backup the <I> hard disk drive routinely. There are three levels of back-up that are recommended:
• Complete hard disk drive. Backup all of the C: drive after installation is complete and if changes are made to the operating system with disks supplied from GEDS. Since the F: and G: drives are pseudo drives assigned as a subdirectory of C:, the data in these directories is saved at the same time. This back-up could be used to rebuild the system after a catastrophic loss of the hard disk.
• F:\UNITn Unit configuration files on the F: pseudo drive. This directory (or directories) should be backed-up after any configuration or sequencing changes, such as new I/O points added, Control Sequence Editor changes, or a control constant change.
• F:\RUNTIME and F:\USER should be routinely backed-up for display modifications and any screen images that were saved.
During the back-up or restoration of a hard disk, that specific <I> cannot be controlling the turbine(s). If it is necessary to run the turbine(s) during this time, other control systems such as other <I>s or <BOI>s must be utilized.
It is necessary to exit the IDOS operating system to perform any back-up. To exit IDOS, type IDOSEXIT at the DOS prompt. Once the back-up is complete, type RUN_IDP to return to the IDOS system or turn off the <I> momentarily. Before backing up the hard disk, it is recommended that a system disk is made. This disk can be made by typing
SYS A: at the DOS prompt with a new floppy disk in the A: drive. The system disk should include the following files:
COMMAND.COM, IO.SYS, MSDOS.SYS - these should be copied by the SYS command
Various methods are available to back-up the hard disk drive. For computers using versions of DOS before 6.0, the DOS
BACKUP command is available in the C:\DOS subdirectory. Consult the DOS documentation for details or type BACKUP /? at the DOS prompt.
The DOS RESTORE command is the complement to the BACKUP command; RESTORE rebuilds the C: drive to the
configuration that was saved using the BACKUP command. Consult the DOS documentation or type RESTORE /?
at the DOS prompt.
For computers using DOS version 6.0 or later, the equivalent command is MSBACKUP, which is available in the C:\DOS
subdirectory. For details, consult the DOS 6.0 documentation or type MSBACKUP at the DOS prompt.
The DOS backup utilities will not work with puesdo or substituted drives (F: or G:); remove the substitutations before doing a backup. The substitutions can be removed by entering SUBST /D at the C:> prompt.
File compression software reduces the size of some of the files and therefore, the number of disks needed to back-up the hard disk. See the manufacturer’s directions.
Although other methods, such as removable hard disk drives, magnetic tape units, and commercially available back-up software may also be used, none are supported by GEDS.