Re: [foxboro] MDACT on ESSCOR simulator

Janet,
Thanks, this is exactly what I was looking for.  I will try it tomorrow
and let you know if it worked.

Cyrus

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Parker, Janet
Sent: Wednesday, May 14, 2003 12:45 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] MDACT on ESSCOR simulator

=20

Hi Cyrus,

I believe you are not referencing the block quite right.  It should
resemble
that listed below.

Cross Reference as <compound>:<block>.FBLIMDEC=20
                        <compound>:<block>.FBLIMINC

Please feel free to contact me directly so that I can help you through
this
problem.

Regards,


Janet Parker
Senior Applications Engineer
SimSci-Esscor
T (760) 268-7774
F (760) 268-7707

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Cyrus W. Taft
Sent: Wednesday, May 14, 2003 8:32 AM
To: Foxboro Mailing List
Subject: [foxboro] MDACT on ESSCOR simulator



I have a very early vintage ESSCOR power plant simulator that uses the
FS=3D
IM
software to handle the control system model.  The disk drive in the
maste=3D
r
simulation computer crashed a few months ago and through a comedy of
erro=3D
rs
there was no current backup.  ESSCOR has managed to reconstruct the
syste=3D
m
for me and I have worked through several bugs in getting the system
worki=3D
ng
again.  I have one last known problem with the MDACT block.  There are
tw=3D
o
drive limit switch inputs to the MDACT FBM which are linked to two
parameters, LIMINC and LIMDEC. The problem I have is that the LIMDEC
parameter is always true which prevents the MDACT block from pulsing the
drive in the decrease direction.  ESSCOR uses a cross reference file to
link process model variable names to Foxboro inputs and outputs. For
thes=3D
e
two inputs, the cross reference file links them both to logical
constants=3D

that are always false.  Obviously something is not right with the cross
referencing.  ESSCOR generally uses a slightly different parameter name
i=3D
n
the cross reference file than Foxboro. For example, to connect a model
variable to an AIN block, ESSCOR uses the parameter name .POINT instead
o=3D
f
.PNT.  But in the case of the these limit switch inputs, the parameter
na=3D
me
is the same, LIMINC and LIMDEC.  I wonder if someone else with an early
vintage ESSCOR simulator with an MDACT block could check their
CrossRef.t=3D
xt
file and tell me what parameter name is used for these two points. =3D


Thanks for your help.

Cyrus Taft
EPRI I&C Center
=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20


 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: