Use the hyperlinks below to quickly navigate through this document
Running an OPCGatewayEngine with GEMarkVEngine(s)
Changes to Configuration Files
Setting up a GEMarkVEngine [ return to Top of the Document]
After the GEMarkVEngine is installed, a few steps must be followed to ensure that it is set up properly.
If it is not already there, add a GEMarkVEngine to your SIM4ME simulation.
NOTE TO DEVELOPMENT ENGINEERS: If you are manually editing the config_file.dat, the GEMarkV engine header is [GEMarkV]. See sample config_file.dat entry below for details. If the install shield worked correctly, however, you should not need to manually edit the config_file.dat.
The GEMarkVEngine reads in the following 9 data files upon initialization:
ALLOCSSP.ASG
CONST_B.SRC
CONST_Q.SRC
FACTORY.ASG
IO.ASG
MSTR_SEQ.LST
SCLEDATA.DAT (may not be required for all installations)
SITE.ASG
Unitdata.dat
You should receive these files from the plant you are working with. Several changes will likely need to be made to these files before they will work properly with the GEMarkV emulation. Please see the Changes to Configuration Files section of this document for more information. It is also possible that the controls from the plant use control blocks that ESSCOR has not yet coded into its emulation. Please consult the software group if you suspect this to be the case. This is something that should be determined in the bidding/design plan stage of the project.
Place the configuration files (modified as necessary) in a ‘working’ directory such as:
C:\Program Files\SIMSCI\SIM4ME2X\Engines\GEMarkV\Working
If the project requires more than one GEMarkVEngine, the GEMarkV configuration files for each engine will need to be in separate directories. For example, if GEMarkV is used to control both the main and boiler feed pump turbines, one will need two sets of configuration files; one for the main turbine and one for the boiler feed pump turbines. The two sets of configuration files will be different and should be placed in different directories. One option is to create two working directories as follows:
C:\Program Files\SIMSCI\SIM4ME2X\Engines\GEMarkV\Working_main
C:\Program Files\SIMSCI\SIM4ME2X\Engines\GEMarkV\Working_BFPT
Specify the appropriate path for the configuration files with the –mv_dir command line option. This option must be set correctly for each GEMarkVEngine. If you are using he SIM4ME GUI (Graphical User Interface) the –mv_dir option is set in the ‘Simulation Configuration’ dialogue box. Enter the directory path for the configuration files in the field labeled: “Directory Path for MarkV Configuration Files”.
Make sure the IC and Backtrack paths are set appropriately.
Make sure delt and sync_period are compatible with the plant’s controls, other engines, and the SimExecutive. The ‘delt’ command line option should be set to the cycle time of the GEMarkV controls. Consult your plant contact if you are unsure of the appropriate cycle time.
‘Ignore Tolerance Checking while Cross Referencing’ can be left as ‘no’
Running an OPCGatewayEngine with GEMarkVEngine(s) [ return to Top of the Document]
Make sure the OPCGatewayEngine does not finish starting up before all the GEMarkVEngines have completed there initialization. GEMarkVEngine initialization is complete when the “GEMarkVEngine Initialization Complete” message appears in the dos window (or message window of Dynsim). The OPCGatewayEngine “OPC Gateway I/O started” indicates that the OPCGateway initialization is complete. If the “OPC Gateway I/O started” message appears in the dos window before the “GEMarkVEngine Initialization Complete” message appears, any GEMarkVEngine points initialized after the “OPC Gateway I/O started” message will not be available to Cimplicity. The way to fix this problem is to increase the “wait_time” for the OPCGatewayEngine. This can be done through the ‘Simulation Configuration” dialogue box of the OPCGatewayEngine. See OPCGatewayEngine documentation for more details.
If the GEMarkVEngine values are bad in the SIM4ME glossary as well, then it means the points in question are not being initialized properly in the GEMarkVEngine. It may be that the point type is incorrect. Point types for the GEMarkVEngine are specified in the second column of Unitdata.dat. See Mark5UnitDatalexer.l for how ESSCOR handles each point type. You will need the assistance of a software engineer to access this file.
If values are not being transferred to Cimplicity (or another OPC client) correctly, make sure the point types in the Unitdata.dat file and the OPCGatewayEngine.tree file are compatible. If a point is specified as a bool in one file and a real, the point will not be transferred across the OPC protocol correctly. Figure out which is correct (the GEMarkV unitdata.dat file is more than likely the correct type) and make changes accordingly.
Changes to Configuration Files [ return to Top of the Document]
These notes are based on configuration file changes that had to be made to the Wansley configuration files for the Wansley 2005 upgrade. If you are working on the Wansley project and have received new GEMarkV configuration files, make sure you address all of the issues outlined below. If you are working on another project, you will likely have to use these notes as a general guide for changes that may need to be made. DO NOT assume that your project is exactly like the Wansley project. Look for similarities and differences and make changes as appropriate and necessary.
The following is a list of changes that needed to be made to get the configuration files working properly (for Wansley Upgrade 2005).
ALLOCSSP.ASG minor changes – replaced Q_ALM_SP_333 & 334 with L30SEF_FOX and L30SEF_MAN
CONST_B.SRC no changes
CONST_Q.SRC minor constant changes plus a few additions near end
Manual changes: increase indexes on KEXP_BLEND, KRE1_TRANS, KDE1_TRANS, and KDE2_TRANS by one.
(0->1 and 1->2 as needed … see MSTR_SEQ.LST notes below)
FACTORY.ASG no changes
IO.ASG minor changes + Manual change: enilssen uncommented out TNH1 – this change was manually made in the new file – TNH1 is the turbine speed probe. Also, made the following changes:
Changed: (in IO.ASG)
C_CD_CO57TMR C_CD_CO57TMR LOG ;C1 TMR INTERFACE FOR C_CD_CO57
C_CD_CO58TMR C_CD_CO58TMR LOG ;C1 TMR INTERFACE FOR C_CD_CO58
C_CD_CO59TMR C_CD_CO59TMR LOG ;C1 TMR INTERFACE FOR C_CD_CO59
C_CD_CO60TMR C_CD_CO60TMR LOG ;C1 TMR INTERFACE FOR C_CD_CO60
To:
C_CD_CO61 C_CD_CO57TMR LOG ;C1 TMR INTERFACE FOR C_CD_CO57
C_CD_CO62 C_CD_CO58TMR LOG ;C1 TMR INTERFACE FOR C_CD_CO58
C_CD_CO63 C_CD_CO59TMR LOG ;C1 TMR INTERFACE FOR C_CD_CO59
C_CD_CO64 C_CD_CO60TMR LOG ;C1 TMR INTERFACE FOR C_CD_CO60
MSTR_SEQ.LST massive changes everywhere – this is how the rungs seems to be configured. A lot of the changes seem to be a result of renumbering the rungs. Manual change: fixed top so that it does not have garbage on top. Also, around line 1003, got rid of F:\UNIT1\ as well as garbage on line 1002. Same thing at 2123/2124, 4003/4004, 4042/4043, 5257/5258, 6239/6240, 6272/6273. On these last two, B and Q are different. Change to B to Q at lines 6240 and 6273 as per ‘File Modification Notes.doc’ file in J:\Wansley\GE MarkV\Main Turbine.
Also, search on _TRANS and change indexes from 0 to 1.
KRE1_TRANS0 -> KRE1_TRANS1
KEXP_BLEND0 -> KEXP_BLEND1
KDE1_TRANS0 -> KDE1_TRANS1
KEXP_BLEND0 -> KEXP_BLEND1
KDE2_TRANS0 -> KDE2_TRANS1
KEXP_BLEND0 -> KEXP_BLEND1
Also, update CONST_Q.SRC accordingly.
http://www.cadfamily.com/html/Article/Running%20a%20GEMarkVEngine_998_1.htm
No comments:
Post a Comment