COMOC-III Technical Reference - corelab.com · COMOC-III Technical Reference Guide T-EIOM.8191-1 August 10, 1995 Revision 00 Table of Contents 1.0 Document Description ..... 1

T-EIOM.8191-1 August 10, 1995 Revision 00

COMOC III

TECHNICAL REFERENCEGUIDE


AMENDMENT LOG

Manual approved by: STP

Any amendment to this manual shall be recorded on this AMENDMENT LOG PAGE. Supersededpages shall be removed, destroyed, and replaced by the amended pages including the updatedAMENDMENT LOG PAGE.

AMENDMENT AMENDMENTNUMBER DATE DETAIL

COMOC-III Technical Reference Guide


Table of Contents

1.0 Document Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2.0 COMOC Required Hardware and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

3.0 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.1 COMOC Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.2 COMOC Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3.2.1 Application Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.2.2 COMOC Calculation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.2.3 DAC Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.2.4 DAC_ACQ Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.2.5 Inter-Process Communication . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.3 COMOC Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4.0 COMOC Terminal Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64.1 COMOC Manager Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64.2 Engine Room or Operator Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74.3 Inquiry Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

5.0 COMOC Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95.1 Command Files (Com Directory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95.2 Configuration Files (Config Directory) . . . . . . . . . . . . . . . . . . . . . . . . . . 115.3 History Files (Hsfils Directory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.4 Executable Files (Exe Directory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125.5 Library Files (Lib Directory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135.6 Forms Files (Forms Directory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6.0 COMOC DCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146.1 Logical Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146.2 COMOC_MGR Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

6.2.1 Start COMOC System - 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186.2.2 Start CALC and DAC - 02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.2.3 Start CALC - 03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.2.4 Start DAC - 04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.2.5 Stop CALC and DAC - 05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.2.6 Stop CALC - 06 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.2.7 Stop DAC - 07 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.2.8 MMP Program -16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206.2.9 SYSMGR Program - 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206.2.10 Clear Slot Utility - 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20



6.2.11 Exit to DCL - 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206.2.12 Logout - 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206.2.13 I/O Cabinet Test -21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

7.0 COMOC Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217.1 COMOC Configuration Program (CCNFG) . . . . . . . . . . . . . . . . . . . . . . 21

7.1.1 CCNFG Parameters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227.1.2 CCNFG Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

7.2 System Status Display Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 247.2.1 System Status File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247.2.2 Display Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257.2.3 Signal Identifiers (System Status) . . . . . . . . . . . . . . . . . . . . . . . 26

7.3 Blend Detail & Logging Report Configuration . . . . . . . . . . . . . . . . . . . . 287.3.1 Blend Report File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

7.4 Current Blend Information Display Configuration . . . . . . . . . . . . . . . . . 297.4.1 Current Blend Information Display File Format . . . . . . . . . . . . . 29

7.5 Signal Identifiers for Blend Detail & Current Blend Information . . . . . . 307.6 Hidden Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

7.6.1 Input/Output Signal Configuration . . . . . . . . . . . . . . . . . . . . . . . 327.6.2. System Status Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

8.0 System Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338.1 BLCOMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

8.1.1 BLCOMM Communication Protocol (RS-232 only) . . . . . . . . . . . 338.1.2 BLCOMM Data Message Format . . . . . . . . . . . . . . . . . . . . . . . . 348.1.3 Signal Data Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . 34

8.2 Connecting a Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358.2.1 VAX Terminal/Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . 358.2.2 Modem Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36


T-EIOM.8191-1 1 Core Lab Refinery Systems

1.0 Document DescriptionThis document is intended for COMOC system administrator's to use as a guide

when configuring COMOC for use by COMOC operators. This document is not intendedfor COMOC operators to use and does not describe COMOC functionality and CFR knocktest engine operation. The COMOC extended I/O interfacing software version is coveredin this document, and previous COMOC versions may not be accurately addressed.

2.0 COMOC Required Hardware and SoftwareCOMOC requires a Digital Equipment Corporation (DEC) MicroVax computer

running VMS Version 5.0 or later with at least one VT type terminal. COMOC uses eitherRS-232 or RS-422 to communicate to the CFR engines via the COMOC I/O box. Therecommended DEC hardware is listed below.

DEC Equipment Specifications

HardwareVAX Model 3100-30 or higherMemory Minimum of 12 Megabyte for the COMOC

ApplicationCommunication Minimum of 4 DEC-423 ports for 1 blender.

Additional ports required for additionalblenders.1 Modem port recommended for remotedialup support.

Terminals Minimum of 1 Terminal; 3 recommendedHard Drive Minimum of 80 Megabyte; 200 MB

recommendedTape Drive TK50 or TK70 required for installation and

updates.Network Optional

SoftwareOperating System VMS Version 5.0 or later.Compiler DEC-Fortran Version 5.0 or later.Forms DEC-FMS Version 2.0 or later. (run-time)



3.0 System Overview

3.1 COMOC Hardware ComponentsA block diagram of the COMOC III system is shown in the following pages. The

system includes engine equipment for each CFR engine, and computer equipment,normally located in the blender control room.

The major components of the system are:



Engine Equipment • Fuel Handling Systems including carburetor with automatic F/A (fuel/air)

adjustment, fuel junction box, and fuel cooling system

• Engine-mounted Control Console with Detonation Meter, KI recorder, F/Asetting display, fuel system controls, and test signal generator

• Engine Trouble Sensors and Alarms with display panel

Control Room Equipment • COMOC III Computer with internal data storage disk, memory, and

communication interfaces

• Measurement and Control Subsystem with analog and digital input/output(I/O) interface to engines, blender control systems, and volatility analyzers

• Operator Command Terminal (CRT) with auxiliary printer for screen copy

• Line printer for hard copy blend data reports

Optional CommunicationCOMOC III also provides optional communication links to a variety of

additional terminals, computer systems, etc. These include:

• Transmission of COMOC III data to a remote refinery computer • Remote problem diagnosis facility via telephone modem • Remote terminals in the engine room, laboratory, supervisor's office, etc. • Supervisory control of blender control system

The functions of the components of the COMOC III system are described inmore detail in the following sections.

COMOC Application Overview

MMPMaster Menu Process

CALCCalculation Process

DACData Acquisition &Control Calculations

DAC_ACQData Acquisition &Control Communications

COMOC_EMAShared Image

COMOC_DACShared Image

VMS Mailbox

COMOC_CALC

COMOC_DAC

COMOC_DAC_ACQ



3.2 COMOC Application

3.2.1 Application OverviewThe COMOC application consists of three detached processes and two shared

images. In addition, other processes are spawned off as required, usually from thecalculation process. The operator has full access to all control and data via the MasterMenu process (MMP).



3.2.2 COMOC Calculation ProcessThe COMOC calculation process is considered the "brains" behind the COMOC

application. COMOC_CALC processes operator commands, sends data to the operator,and stores all reported data for later retrieval. COMOC_CALC is started upon booting theVAX and remains running forever until stopped by the manager or prematurely halted byerror. During normal operation CALC will cycle between COM, HIB, and occasionallychange to the LEF state. Refer to the COMOC Application Overview diagram to see howCALC communicates to the other processes.

3.2.3 DAC ProcessThe COMOC data acquisition process is where the data acquisition and control

calculations take place. CALC writes control data into the shared image where DAC readsthe data, performs calculations, and sends I/O commands to the DAC_ACQ process viathe VMS mailbox. During normal operation DAC will cycle between COM, HIB, andoccasionally change to the LEF state. When DAC is started it spawns the DAC_ACQprocess. Refer to the COMOC Application Overview diagram to see how DACcommunicates to the other processes.

3.2.4 DAC_ACQ ProcessThe COMOC data acquisition communication process maintains serial

communication between the VAX and the COMOC I/O cabinet. DAC_ACQ communicatesto the I/O cabinet by polling it on 1 second intervals. The analog input channels aresampled at 1 second intervals, whereas the analog output channels are updated at 10second intervals. The digital input channels are sampled at 10 second intervals and theoutput channels are updated at 1 second intervals. A digital output channel is used as acommunication watchdog which opens if no communication is received from the VAX overa 10 second period. The output will open if there is a break in the communication wiringor if there is a VAX failure.

3.2.5 Inter-Process CommunicationThe COMOC processes communicate through shared memory and the VMS

mailbox system.

VMS Mailbox The DAC and DAC_ACQ processes communicate through theVMS mailbox. When DAC is started it creates a systemmailbox which DAC and DAC_ACQ use to exchange data.

Shared Image There are two shared images (COMOC_EMA andCOMOC_DAC) which require installation during the COMOC



startup process. The images are installed using the VMSinstall command utility. For diagnostic purposes, the COMOCutility Prtema.exe can be used to display the contents in theCOMOC_EMA memory.

3.3 COMOC FormsCOMOC uses a DEC forms run-time library called FMS. The COMOC forms are

located in a library called COMOC_FLB.FLB which resides in the logical directoryCOMOC_FORMS. The form access routines can be loaded at run-time which requires nospecial startup commands. To achieve greater form loading speeds the command:

@sys$startup:fms_startup.com

can be loaded to the system startup file sys$startup_vms.com. This will load the FMSshareable image into available memory to increase form data access times.

4.0 COMOC Terminal Types

When the COMOC III system is equipped with more than one terminal, theadditional terminals may be configured so as to provide access to only those COMOC IIIfunctions pertaining to the intended operator usage. The three types of accountconfigurations are; Manager, Operator or Engine, and Inquiry.

All COMOC III terminals will display the Log On screen and the System StatusDisplay screen. Access to the various reports and command functions depends upon thetype of configuration selected for each user account in the COMOC III User Definition file.Configurations can be modified only by the system manager. Additional accounts may beused by other terminals in other areas such as the supervisor's office, refinery laboratory,etc. These terminals may also be configured for full control access, or they may beconfigured for limited access as outlined in the following sections.

There are many different models of CRT terminals that can be used with theCOMOC III system. These terminals must be DEC-VT series compatible so as to ensureproper functionality. There are also many commercial PC programs available whichprovide VT terminal emulation.

4.1 COMOC Manager AccountA COMOC III system will have at least one account configured as the COMOC



Manager account. This account is normally used to Start/Stop the COMOC system andfor diagnostics purposes.

Typically the VMS user account name for this type of terminal is COMOC_MGR.Upon logging in to this account with the correct password, the user manager will beprompted with the COMOC Manager Menu. At this point, the manager has a variety ofoptions from starting or stopping COMOC to viewing data or reports in the Master MenuProgram (MMP).

Note: To terminate the MMP program and exit to DCL, press the numeric 7 key followedby a password of 728.

4.2 Engine Room or Operator AccountEngine room or operator accounts provide access to all the same reports,

configurations, and command menus as the manager terminal. With the exception thatthere is no access to starting and stopping the COMOC processes which reside on thehost computer.

Typically the VMS user account name for this type of terminal is COMOC_OPR orCOMOC_ENG. Upon logging in to this account with the correct password, the usermanager will be prompted with the COMOC logon screen. At this point, the operator mustlog into the Master Menu Process (MMP) so as to view the current statuses of COMOC.

Note: To terminate the MMP program and end the VMS session, press the numeric 7 keyfollowed by a password of 728.

4.3 Inquiry TerminalInquiry account configuration provides access to the report and configuration

menus. There is no access to the engine command and blender command menus, or thealarm review function. As usual, the System Status Display allows the user to check statusof the engines and blenders.

Typically the VMS user account name for this type of terminal is COMOC_INQ.Upon logging in to this account with the correct password, the user manager will beprompted with the COMOC logon screen. At this point, the operator must log into theMaster Menu Process (MMP) so as to view the current statuses of COMOC.

4.4 Account Access ConfigurationAccount access is added or changed by modifying the comoc_user.def file located



in the comoc_command directory. A one line entry in this file is required for each VMSuser account wishing to gain access to the COMOC MMP program. This format is asfollows:

USER=<VMS Name> TYPE=<Access> TT_PTR="ATTACHED" LP=<LogFileName>

where:USER = VMS Login Account NameTYPE = Operator, Engine or InquiryTT_PTR = always "ATTACHED"LP = any valid file name

If an entry is not found for a VMS user name, COMOC will display the errormessage:

"No Match in COMOC_COMMAND:USER.DAT file".

This error message will also appear if a user is logged in on more than one terminal. Thisoccurs because the process name changes to the port device name instead of the username.



5.0 COMOC Directory Structure

5.1 Command Files (Com Directory)

File Name Description

blcomm_232_link.com blcomm link file for RS-232 communication

blcomm_link.com blcomm link file for network communication

bldtrp_bat_link.com link file for batch blend detail report program

bldtrp_link.com link for the blend detail report program

calc_link.com calc program link file

calc_run.com run file for calc program

ccnfg_link.com comoc configuration program link file

clear_slot_link.com comoc clear slot utility program link file




comoc_bld.com link batch file for all COMOC exe's

comoc_dac.opt optional parameter file for shared image linking

comoc_dac_ext_link.com link file for comoc_dac shared image

comoc_def.com comoc port and logical definition file

comoc_ema.opt optional parameter file for shared image linking

comoc_ema_link.com link file for comoc_ema shared image

comoc_extio_for.com compile batch file for compiling all comoc sourcecode

comoc_lib.com build file for comoc subroutine library

comoc_login.com comoc default login file

comoc_mgr_login.com comoc login file for the comoc_mgr account

comoc_read_file.com DCL login verification procedure for COMOC loginaccounts - reads comoc_user.def

comoc_startup.com comoc startup command procedure

comoc_user.def comoc user login data file

convert_link.com link file for the convert utility program

cycle_link.com link file for the fuel cycle program

dac_link.com link file for the dac program

dac_run.com run file for the dac program

dac_lib.com build file for the comoc dac library

inital_extio_link.com link file for the comoc_ema shared image

mmp_link.com link file for the master menu program

prtdr_link.com link file for the print data record utility

prtema_link.com link file for the print shared image ema utility

prtsig_link.com link file for the print signal file utility

remove_emas.com command file to remove the comoc sharedimages

sysmgr_link.com link file for the system manager program

testop_link.com link file for the testop program




comoc_bldtrp_bat.com run file for the blend detail report program

trace_link.com link file for the dac mailbox trace utility

5.2 Configuration Files (Config Directory)


bldt_confg.dat Blend detail report configuration file. (ascii)

cubl_confg.dat Cumulative blend information display configurationfile. (ascii)

stau_confg.dat System status display configuration file. (ascii)

cbicfg.dat Signal configuration file for blender inputs. (binary)

cbocfg.dat Signal configuration file for blender outputs.(binary)

cecnfg.dat Engine calibration and configuration. (binary)

ceicfg.dat Signal configuration file for engine inputs. (binary)

ceocfg.dat Signal configuration file for engine outputs.(binary)

cpocfg.dat Blend product configuration file. (binary)

cycle.dat Cycle timing configuration file. (binary)

m15cfg.dat COMOC system configuration file. (binary)

5.3 History Files (Hsfils Directory)


cblhsa.dat Blend history audit file listing. (binary)

m10000.dat Engine 1 search history file. (binary)








Pxyz.dat Proto Certification history file. (binary)x = engine number (1 char)y = number of certification that day (1 char)z = julian day of the year (3 char)

Cxyz.dat Engine Calibration history file. (binary)x = engine number (1 char)y = number of certification that day (1 char)z = julian day of the year (3 char)

Bxyz.dat Blend History File. (binary)x = blender number (1 char A,B, or C)y = number of certification that day (1 char)z = julian day of the year (3 char)

*.log files Contain run-time error logs for COMOCprocesses. (ASCII)

5.4 Executable Files (Exe Directory)


blcomm.exe Blend communication program.

bldtrp.exe Blend detail report program.

bldtrp_bat.exe Blend detail report host program.

calc.exe Calculation program.

ccnfg.exe Configuration program.

clear_slot.exe Clear Slot Utility program.

comoc_dac.exe Shared Image.

comoc_ema.exe Shared Image.

convert.exe HP/VMS File Conversion Utility



cycle.exe Fuel Cycle time configuration program.

dac.exe Data Acquisition & Calculation program.

dacsm.run Data Acquisition simulation program.

dac_acq.exe Data Acquisition Communication program.

inital.exe Initialization program for COMOC_EMA sharedimage.

mmp.exe Master menu interactive program.

prtdr.exe History file printing utility.

prtema.exe Print utility for the COMOC_EMA shared image.

prtsig.exe Print utility for printing binary signal files.

shutdown.exe COMOC shutdown utility.

sysmgr.exe System manager utility.

testop.exe COMOC I/O Cabinet testing utility.

trace.exe DAC process mailbox testing program.

5.5 Library Files (Lib Directory)


comoc.olb COMOC subroutine object library.

dac.olb COMOC data acquisition subroutine library.

opto22.obj Opto22 subroutine object library.

opto22msg.obj Opto22 subroutine object library.



5.6 Forms Files (Forms Directory)


comoc.flb.flb COMOC FMS Forms library.

6.0 COMOC DCL

6.1 Logical Names

The COMOC definition file defines all the devices and logical names which arerequired for normal COMOC operation. This file is usually changed for each COMOCinstallation. Below is an example file with the different commands and definitionsdescribed.

Logical Name Definition Description(defined in the systemtable unless otherwisespecified)

comoc_term_type Set to Operator, Engine, or Inquiry(process table) depending on the entry in the

comoc_user.dat file. This logical is setby the comoc_read_file.com file andinvoked by the COMOC login commandprocedure.

comoc_brc defines the optional blend ratio controllerexecutable

comoc_ema defines the ema shared image

comoc_emacr defines the ema shared image (cr method only)

comoc_dac defines the dac shared image

comoc_daccr defines the dac shared image (cr method only)

comoc_backup defines where history files are copied to when theyare manually deleted from comoc audit file




comoc_cfgbck not implemented

comoc_config defines the comoc configuration directory

comoc_hsfils defines the comoc history file directory

comoc_doc not implemented

comoc_exec defines the comoc executables directory

comoc_execr defines the comoc executables directory (crmethod only)

comoc_forms defines the comoc forms directory

comoc_command defines the comoc command procedures direcotry

comoc_kit not implemented

comoc_library defines the comoc subroutine library

comoc_lists defines the source file listing directory

comoc_objects defines the object code directory

comoc_objectscr define the object code directory (cr method only)

comoc_sources defines the source code directory

comoc_sourcescr defines the source code directory (cr method only)

comoc_opto_port defines the device to communicate to the comoci/o cabinet

opto22_terminal_01 not implemented

comoc_blcomm_port defines the device for the blend communicationprogram (blcomm) to communicate to a remotesystem

comoc_backup_device not implemented

comoc_blnd_a not implemented

comoc_engn_1 not implemented

comoc_log used for optional brc interface logging

comoc_diag not implemented




comoc_brc_log used for optional brc interface logging

comoc_remote_a blender a optional network logging file-used byblcomm

comoc_remote_b blender b optional network logging file-used byblcomm

comoc_remote_c blender c optional network logging file-used byblcomm

comoc_comm_index enables or disables the blcomm program

comoc_blc_downld enables or disables the blcomm program

comoc_blc_input sys$input to the blcomm program at startup

comoc_blc_output sys$output from the blcomm program at programtermination

comoc_blc_error error output file from the blcomm program ifabnormally terminated

comoc_dac_acq_input sys$input to the comoc_dac_acq process whendac spawns the program

comoc_dac_acq_output sys$output from the comoc_dac_acq processwhen dac terminates

comoc_dac_acq_error error output file from the comoc_dac_acq processwhen dac abnormally terminates

comoc_dac_downld disables or enables the comoc_dac_acq process

comoc_dac_log_lu fortran unit number for dac logging

comoc_dac_diag_lu fortran unit number for dac diagnostics

comoc_secio_input optional for secondary i/o cabinet

comoc_secio_output optional for secondary i/o cabinet

comoc_secio_error optional for secondary i/o cabinet

comoc_secio optional for secondary i/o cabinet

for040 not implemented




for041 usually used as the blender a blend loggingdevice - defined by the ccnfg programTo disable blend logging set this logical nameequal to the null device (nla0:).

for042 usually used as the blender b blend loggingdevice - defined by the ccnfg programTo disable blend logging set this logical nameequal to the null device (nla0:).

for043 usually used as the blender c blend logging device- defined by the ccnfg programTo disable blend logging set this logical nameequal to the null device (nla0:).





comoc_hisdisk optional disk shadowing

comoc_hisdir optional disk shadowing



-------------------------- Menu Options ------------------------------------ 01 - Start COMOC System 02 - Start CALC and DAC 05 - Stop CALC and DAC 03 - Start CALC 06 - Stop CALC 04 - Start DAC 07 - Stop DAC

16 - MMP Program 19 - Exit to DCL 17 - SYSMGR Utility 20 - Logout 18 - CLEAR_SLOT Utility 21 - I/O Cabinet Test ---------------------------------------------------------------------------------

Enter Option:

6.2 COMOC_MGR Menu

6.2.1 Start COMOC System - 01This option is used to start the COMOC system, including all processes and

allocating all required memory. If the COMOC system is already running, all functions willbe terminated and COMOC will be initialized. The system manager program can be usedto determine if COMOC is active.

Startup-Up Sequence (comoc_command:comoc_startup.com)1. comoc_def.com is invoked2. shared images installed3. inital.exe reads the configuration files4. inital.exe initializes the shared images5. calc.exe is started6. dac.exe is started7. dac_acq.exe is spawned from dac



6.2.2 Start CALC and DAC - 02This command is used if CALC and DAC have been shutdown or abnormally

terminated and you wish to retain the data in the shared images.

6.2.3 Start CALC - 03This command is used if CALC has been shutdown or abnormally terminated and

you wish to retain the data in the shared images.

6.2.4 Start DAC - 04This command is used if DAC has been shutdown or abnormally terminated and you

wish to retain the data in the shared images.

6.2.5 Stop CALC and DAC - 05This command is used to stop the COMOC processes. This command will not stop

the comoc_dac simulation program. This program must be manually stopped from the DCLcommand line with the Stop command. After this command completes the shared imageswill still be installed. Remove the shared images by typing the command:

@comoc_command:remove_emas

6.2.6 Stop CALC - 06This command is used to stop the CALC process. All functions will be halted.

6.2.7 Stop DAC - 07This command is used to stop the DAC process. All functions will be halted. This

command will not stop the comoc_dac simulation program. This program must be manuallystopped from the DCL command line with Stop command.

6.2.8 MMP Program -16This command will invoke the COMOC interactive Master Menu Process. See the

operations guide for additional information.

6.2.9 SYSMGR Program - 17This command will start the System Manager program. The system manager



program display's data about the status of the COMOC system.

6.2.10 Clear Slot Utility - 18This command will invoke the COMOC clear slot utility. This command should be

used when the it's not possible to log into the COMOC MMP program. If the number ofterminals logged into MMP exceeds the maximum number of terminals allowed, MMPdisplays the message "No Terminal or Slot".

6.2.11 Exit to DCL - 19This command exits the command procedure and provides the DCL $ prompt.

6.2.12 Logout - 20This command logs the interactive account out of VMS.

6.2.13 I/O Cabinet Test -21This command invokes the I/O Cabinet TESTOP utility. This program is menu driven

and displays the status of digital and analog inputs. All control outputs can be tested. Thisprogram is used primarily for installation and diagnostic purposes.



7.0 COMOC Configuration Options

7.1 COMOC Configuration Program (CCNFG)

The COMOC configuration program is generally used by the system administratorto define different options in the COMOC system. The options are usually set up atinstallation time and changed very infrequently. However if changes are made, COMOCmust be restarted for the changes to take affect.



7.1.1 CCNFG Parameters Table

The configurable parameters are listed below in a table for easy reference. Anychanges to the COMOC configuration file will not take affect until COMOC is restarted.

Configuration DescriptionParameter

Number Blenders Set to the number of blenders installed for this site. If changed,additional software is required to support this change.

Number Engines Set to the number of engines installed for this site. If changed,additional software is required to support this change.

Blend Log Dev (by blender) Fields A, B, & C are set to the Fortran unit logical devicenumber. (eg. 41 stands for FOR041, the logical name FOR041must point to a valid device). This logical definition should beadded to the comoc_command:comoc_def.com file.

Engine Cycles: Cal The number of cycles required for an engine calibration.Should be set to the ASTM requirement.

Engine Cycles: Cert The number of cycles required for an engine prototypecertification. Should be set to the ASTM requirement.

Engine Cycles: Chkout The number of cycles required for a system checkoutprocedure. Should be set to the ASTM requirement.

Search Param Defines the effect of the remote fuel air search commandinitiated from a remote system via a digital input.

1 = fuel air search command initiates a proto fuel airseach initially; any subsequent commands during theblend will initiate a product fuel search

2 = fuel air search command initiates a product fuel airsearch only - QuickSearch

Blend Log Param Not Implemented.

HF Auto Delete Not Implemented.


Configuration DescriptionParameter


Engine Status Maps an engine status to a digital output module. There is atotal of 7 engine statuses and four available digital outputmodules. The 7 statuses are:1 - Engine Running2 - Engine in Automatic Mode3 - Engine Low Knock Intensity Alarm4 - Engine High Knock Intensity Alarm5 - Engine Prototype Repeatability Alarm6 - Engine Fuel Status7 - Engine Fuel Air Search

The output module locations are defined in order from left toright Engine Status Module #1 - #4.

Proto Diff Alarm These two parameters (RON and MON) define the protorepeatability alarm tolerance for all the engines installed.

Terminal # These terminal parameters must be unique non-zero numbersto allow COMOC interactive logins. A maximum of 6 interactiveCOMOC logins are allowed.

Term. Type These fields should always be set to control. Theseparameters are used internally by MMP.

Communication This optional parameter enables the Blcomm program. Whenset to 0, blcomm is disabled. If set to 1 blcomm is active. Seesection Blcomm for additional information.

7.1.2 CCNFG Operation

The CCNFG program is invoked from the COMOC_MGR account at the DCLprompt with the following command:

RUN COMOC_EXEC:CCNFG

The configuration form will be displayed with the current values located in the COMOCconfiguration file. To move forward from field to field press the tab key, to move backwardpress the f12 key. Upon completion of all changes, press the numeric <4> key twice tosave your changes to the configuration file. At this time, it is necessary to stop and startCOMOC for the changes to take affect.



7.2 System Status Display Configuration

The system status display configuration file is used to specify the data to bedisplayed in the blender and engine data columns of the System Status display. Once thefile is changed and saved correctly any subsequent accesses to the System Statusdisplay will be changed.

7.2.1 System Status File FormatRecords one (1) through seven (7) correspond to the Blender data columns and

records eight (8) through thirteen (13) correspond to six (6) configurable Engine datacolumns. The signal id's are defined in section 7.2.3 Signal Identifiers (System Status). Theliteral text can be set to any valid characters for use as titles. This file is maintained usingany VMS editor. However, it is necessary to maintain the version 1 specifier for this file.If the file does not exist COMOC will create a default file to use.

File Format Example (comoc_config:stau_confg.dat;1)

Record # Signal ID Space Literal Text1-7 Blender (columns 1-5) (col 6) (columns 7-13)8-13 Engine leading zeros req'd

1 00206 BARRELS

2 01501 PRODUCT

3 02501 COBI

4 00501 AVGPROD

5 06501 TARGET

6 01203 RVP

7 00203 AVGRVP

8 01601 PRODUCT

9 02601 COBI

10 00601 AVGPROD

11 06601 TARGET



12 00606 KMU

13 00604 MV

IMPORTANT NOTE: The COMOC MMP application will only access the version1 file. After editing the file, it must be renamed with theversion 1 specifier.

7.2.2 Display Logic

Blender Data

Only Blender ID and Status will be displayed if Status is STOP or WAIT.

Engine ID's will be displayed if Status is RUN, HOLD or STBY.

For Signal ID's 501, 1501, 2501, 3501, 4501 or 6501 selection of Road, Researchor Motor data will be determined by the type(s) of engines assigned to the blend.

If a volatility is not assigned a target at Start/Resume blend fields selected will bedisplayed as space characters.

Engine Data

Only Engine ID, Status, Fuel Type and Alarms will be displayed if Status is STRT.

Only Engine ID, and Status will be displayed if Status is STOP.

Display Blender ID only when assigned to blend.

For Signal ID's 00601, 01601, 02601, 03601, 04601 or 06601 the Engine type willdetermine whether to display Research or Motor data.

For Signal ID 00606, if engine status is SRCH or Q SRCH then the last KMUcorresponding to the current fuel type will be displayed else the last KMU oppositeto the current fuel type is displayed.



7.2.3 Signal Identifiers (System Status)

Signal Identifier for DescriptionSystem Status only

00206 Product barrel count

00501 Road/RON/MON Average

01501 Road/RON/MON Cycle

02501 Road/RON/MON Cumulative Delta

03501 Road/RON/MON Cycle Delta

04501 Road/RON/MON Delta Error

06501 Road/RON/MON Target

00203 Volatility #1 Average

01203 Volatility #1 Cycle

02203 Volatility #1 Cumulative Delta

03203 Volatility #1 Cycle Delta

04203 Volatility #1 Delta Error

06203 Volatility #1 Target












Signal Identifier for DescriptionSystem Status only










00601 RON/MON Average

01601 RON/MON Cycle

02601 RON/MON Cumulative Delta

03601 RON/MON Cycle Delta

04601 RON/MON Delta Error

06601 RON/MON Target

00602 Proto Microvalve Setting

00603 Line Microvalve Setting

00604 Actual Microvalve Setting

00606 Last Cycle Average Knock

00609 Proto Octane Value

00610 Line Octane Value



7.3 Blend Detail & Logging Report ConfigurationThe blend detail report configuration file is used to specify the data to be printed on

the hardcopy blend report and log report. After this file is changed, COMOC must berestarted for the changes to take affect.

7.3.1 Blend Report File FormatThis file contains the signal id and two text titles which are printed to the printer at

the top of each page below the header. This report format is used during blend loggingand by the Blend Detail Report option from the MMP reports menu. The header (above thetitles) cannot be changed and the first column of data will always contain the data timestamp. The signal id's are defined in section 7.5 Signal Identifiers. The literal text can beset to any valid characters for use as titles. This file is maintained using any VMS editor.However, it is necessary to maintain the version 1 specifier for this file. If the file does notexist COMOC will create a default file to use.

File Format Example (comoc_config:bldt_confg.dat;1)

Record # Signal ID (columns Space Literal Text Space Literal Text1-5) (col 6) (Columns 7-16) (Col 17) (columns 7-13)leading zeros req'd Title 1 Title 2

1 00206 SP PRODUCT SP BARRELS

2 00201 SP ROAD SP AVERAGE

3 01201 SP ROAD SP CYCLE

4 04201 SP ROAD SP DELTA

5 00001 SP RON SP AVERAGE

6 01001 SP RON SP CYCLE

7 04001 SP RON SP DELTA

8 00002 SP MON SP AVERAGE

9 01002 SP MON SP CYCLE

10 04002 SP MON SP DELTA

11 00203 SP RVP SP AVERAGE



12 04203 SP RVP SP DELTA

7.4 Current Blend Information Display ConfigurationThe current blend information display configuration is used to define the data

displayed when report #5 is selected from the reports display. This display has two pages(left/right) and only side of the report can be displayed on the terminal at one time. Whenthis file is changed and saved correctly, any subsequent accesses to the Current BlendInformation display will be changed.

7.4.1 Current Blend Information Display File FormatThis file contains the signal id and a text titles which is displayed at the top of each

display page below the header. The header (above the titles) cannot be changed and thefirst column of data will always contain the data time stamp. The signal id's are defined insection 7.5 Signal Identifiers. The literal text can be set to any valid characters for use astitles. Records 1-8 define the left page of the display, whereas records 9-16 define the rightpage of the display. This file is maintained using any VMS editor. However, it is necessaryto maintain the version 1 specifier for this file. If the file does not exist COMOC will createa default file to use.

File Format Example (comoc_config:cubl_confg.dat;1)

Record # Signal ID (columns Space Literal Text1-5) (col 6) (Columns 7-16)leading zeros req'd Title 1

Left Page

1 00206 SP BARRELS

2 00201 SP ROADAVG

3 01201 SP ROADCYCLE

4 04201 SP ROADDELTA

5 00001 SP RONAVG

6 01001 SP RONCYCLE

7 04001 SP RONDELTA



8 00002 SP MONAVG

RightPage

9 01002 SP MONCYCLE

10 04002 SP MONDELTA

11 00203 SP RVPAVG

12 04203 SP RVPDELTA

13 00401 SP RONKMU

14 00411 SP RONFUEL

15 00402 SP MONKMU

16 00412 SP MONFUEL

7.5 Signal Identifiers for Blend Detail & Current Blend Information

Signal Identifier for DescriptionBlend Detail Reportor Current BlendInformation

00206 Product barrel count

00201 Road Average

01201 Road Cycle

02201 Road Cumulative Delta

03201 Road Cycle Delta

04201 Road Delta Error

00001 RON Average

01001 RON Cycle

02001 RON Cumulative Delta

03001 RON Cycle Delta




04001 RON Delta Error

00002 MON Average

01002 MON Cycle

02002 MON Cumulative Delta

03002 MON Cycle Delta

04002 MON Delta Error
























00401 RON Engine Average KI

00411 RON Engine Fuel Type

00402 MON Engine Average KI

00412 MON Engine Fuel Type

7.6 Hidden Options

7.6.1 Input/Output Signal ConfigurationThe MMP program offers a signal configuration utility for defining the analog input

and output signals. However, from the configuration menu, choosing option 3 - SignalConfiguration will only allow viewing the signals and not changing them.

To access the add, modify, and save options; from the configuration menu, type -12and the signal configuration display will be provided with the additional options forchanging signal data (modify, add, save).

7.6.2. System Status LogoutWhen logged into the MMP program pressing the numeric keypad 2 key (i.e. done)

will only exit until the login screen. To exit the login screen, press the number 7 keyfollowed by the password 728 from the alphanumeric keys.



8.0 System Options

8.1 BLCOMMThe blend communication program (BLCOMM) is used for sending blend history

data real-time to an external device. The BLCOMM program is available in two versions,network ASCII file transmission or RS-232 line transmission. The COMOC system isdelivered with the RS-232 version of BLCOMM unless otherwise specified.

8.1.1 BLCOMM Communication Protocol (RS-232 only)

COMOC will initiate sending of Blend Data or a Blend Message by first sending tothe Remote System a two character sequence as shown. Before transmitting theData/Message COMOC expects a two character acknowledgement from the remote systemIf after one second no response is detected, COMOC will initiate this same sequenceagain for up to the number of retries defined in the communication parameter located inthe COMOC configuration file. If a negative response is received, COMOC will abort thecurrent message sequence.

COMOC Transmission Remote System Response

<ENQ><CR> <ACK><CR> or <NACK><CR>

COMOC will initiate sending of the Blend Message/Data string upon receiving apositive response to the transmit initiation sequence as depicted above. COMOC expectsa two character acknowledgement from the Remote System If no response, after onesecond, is detected COMOC will initiate this same sequence again for up to the numberof retries defined in the communication parameter located in the COMOC configuration file.If a negative response is received COMOC will abort the current message sequence.



COMOC Transmission Remote System Response

Blend Message/Data <ACK><CR> or <NACK><CR>

8.1.2 BLCOMM Data Message Format

COMOC will format the data as defined in the BLCOMM signal configuration file intoan ASCII data record before transmission. The format for this record is as follows.

Blend Data/Message Format

<SOH>wxxxxxxxx<STX>yzzzzzzzzzzzzzzzzzzzzzdddddddddd...dddd<ETX><BCC<CR>

Character Table:<SOH> = ASCII 1 characterw = 1 character displayed as '1', '2', or '3' specifying the blender number.x = 8 characters (left justified) which define the product configuration

name which was selected at the start of blend monitoring<STX> = ASCII 2 characterz = 21 character string representing the date and time the message was

sentd = variable number of arguments containing blend data or a blend

message.If d is a blend message then it contains an informational alarmmessage.If d is blend data then it contains ten character fields, right justified, withdata as defined in the BLCOMM signal configuration file.

<ETX> = ASCII 3 character<BCC> = 1 character depicting the exclusive or off all characters from the

<SOH> character through the <ETX> character.<CR> = ASCII 13 character

8.1.3 Signal Data Configuration File

The number and content of the data elements transmitted are determined by theconfiguration file COMOC_CONFIG:COMM_CONFG.DAT;1. This file must maintain the'1' version specifier in order for BLCOMM to function properly. The first line of the filecontains a code for BLCOMM. This code determines whether message records, datarecords, or both type of records are transmitted.



00000 = Date and Message Records00001 = Data Records Only00002 = Message Records Only

Lines 2..n and columns 1..5 of the file contain valid signal identifiers as listed inSection 7.5 Blend Detail and Current Blend Information of this document. Up to 30 signalidentifiers are allowed in this file. Following each signal identifier in column 7 is a formatspecifier 1, 2, 3, or 4 specifying the format of the data fields.

1 = F10.2 (10 character field carried to 2 decimal places)2 = F10.0 (10 character field carried to 0 decimal places)3 = F9.2 (9 character field carried to 9 decimal places)4 = F9.0 (9 character field carried to 0 decimal places)

8.2 Connecting a ModemVMS has built in functionality for connecting a modem and allowing remote

interactive login access. It is recommended to have a telephone line and modem availablefor the COMOC VAX system for remote support when needed. This allows a supportrepresentative to diagnose and correct any problems that may occur without requiring aservice call. In the following sections the commands are illustrated to connect andconfigure the VAX to a modem.

8.2.1 VAX Terminal/Port ConfigurationA port must be selected which has modem control lines. There is at least one of

these ports located on the VAX. The port usually has a DB-25 connector. Once locatedyou can connect the port to the external modem with a modem cable (DEC #BC22E-10).Once connected, configure the port with the Set command.

Configure Terminal Command

$set terminal tta2: /perm/modem/noautobaud/speed=9600



8.2.2 Modem ConfigurationGenerally any external modem will work with the VAX that supports the Hayes

compatible command set. The modem will require configuring to communicate with VMSand must support XON/XOFF flow control. The following commands can be issued to themodem by using the VMS host utility.

Configure Modem Commands

$set host /dte tta2: <Enter>

{ You should now be on-line with the modem. When pressing the <Enter> key youshould see the RD light flicker on the modem window. If the modem is configured toecho, when you type AT <Enter> you should receive an OK on the terminal.Proceed with the modem configuration commands. }

atq1 { disable response codes }at&s1 { no DSR signal used } at&d2 { use DTR from VMS }at&c1 { do not force data carrier detect }at&k4 { use xon/xoff flow control }ats0=1 { enable auto answer on 1 ring }

{ If no errors occur, the modem is configured and ready for dial in access. }

<Ctrl> / \ { This control key combination gets you back to DCL. }

Documents

COMOC-III Technical Reference - corelab.com · COMOC-III Technical Reference Guide T-EIOM.8191-1 August 10, 1995 Revision 00 Table of Contents 1.0 Document Description ..... 1