Hi All,
I believe this is the same issue we discovered back in 2009.
It only happens when you enable HART and does not matter if you have AOUT or
not. When reported to GCS, this is the response we got:
CAR 1013207 -- Function Needed to Ignore Device Malfunction Status Bit
CAR 1013207 which you submitted is being put in REVIEW status, preparatory to
being CLOSED with the following proposed Response:
9 Dec 2009 (RH) - The described problem is Not a Product Defect (NPD) that can
be remedied within the 8.4.1 I/A system, because the I/A logic was purposely
designed to not override basic safety interlocks within its external devices.
With some devices, such as our SRD991 positioner, the allowable amount of
deviation (output setpoint minus actual position) before the "Device
Malfunction" status is set can be programmed/configured by users in the device
itself. The I/A system is purposely designed to never ignore a
Device-Malfunction status bit that is set by the device, even though it may not
be regarded seriously for this one case, because, it indicates any device
malfunction or failure of any sort, some of which could endanger personnel and
the process itself.
We had another go late 2015 with the latest firmware and tried all available
options: NOFAIL, NOALARM OCD, the same results. This is the new case (1289589)
we submitted, as PER this time:
Problem Description : ROUT connected to a HART device should not be frozen
and not having any other means to alter the output when "Device Malfunction"
bit is set.
Suggested Solution: Make this an option, just like with HART communication
failure or at least, make available a method to recover from the ''hold'' state
like switching block to manual before driving the output manually.
Expected Benefit: Provide more control to user rather than locking the
block in potentially unrecoverable state. For example, if you are trying to
open a damper but it is stuck closed and ''Device Malfunction'' is set. You
should be able to try to close the damper to reset ''Device Malfunction''. As
it is, the output will hold the last value before ''Device
Malfunction'' is set and there is nothing you can do from then on.
Regards
Jimmy Chan | Systems Engineer
Methanex New Zealand Ltd.
409 Main North Road, SH3, Motunui 4383
Private Bag 2011, New Plymouth 4342
T: +64 6 754 9808
E: jkchan@xxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Subbiah, Srinivasan
Sent: Thursday, 28 January 2016 7:28 a.m.
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AOUT Issue
We have got ROUTs after the AOUTs when we upgraded from 100 series FBMs to 200
series FBMs, for HART so we did not have any problems so far reported here. We
also have AOUTs however not connected using HART, use 4-20 Regards, Srini
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of G.Macdonald@xxxxxxxxx
Sent: Wednesday, January 27, 2016 11:12 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AOUT Issue
Not sure what you mean by OCD?
For a new installation, agreed you would tie the PIDA directly to the ROUT so
the propagation works correctly. For upgrading non-hart FBM's to hart FBM's,
replacing AOUT's with ROUT's becomes a significant amount of work (graphics,
config, testing, recomissioning each loop) making the justification difficult.
Much easier to just add the ROUT after the AOUT.
Having a hart malfunction cause the 4-20 to stop working makes the importance
of the propagation critical.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Landry, Scott
Sent: Tuesday, January 26, 2016 9:43 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AOUT Issue
Every project I've ever been involved in did not use AOUT blocks at all,
replaced with ROUT when ECB201 (hart FBMs) with 4-20 or Hart was involved
Have you tried OCD ?
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list:
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.freelists.org_list_foxboro&d=CwIDAg&c=zgHsTqBQkGAdNuoPRxUzSQ&r=k7AF9dsAUnHrqp5ddRhLBXpnci0j0uVlauIdM6flLFM&m=Ys-sM5XmTcvIw3pBo3HFTEisb1wszojSDo0Pyez6QW0&s=TO4qclIzFS-h2_J7bq5W2ZfXF0YychjrJLqXsYuqFsY&e=
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
For more information on Agrium’s E-Mail Policy or to unsubscribe, click here:
http://www.agrium.com/email_footer_en.jsp
Pour plus de renseignements sur la politique de courrier électronique d’Agrium
ou pour vous désabonnez, cliquez ici : http://www.agrium.com/email_footer_fr.jsp
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
This electronic mail transmission and any accompanying attachments
(collectively "E-mail") may contain confidential or privileged information
intended only for the use of the individual or entity to whom they are
addressed. If you have received this communication in error please immediately
delete the E-mail and notify the sender at the above email address. Any
dissemination, distribution, copying or action taken in reliance on the
contents of this communication by anyone other than the intended recipient is
strictly prohibited. No liability is accepted by the sender for any delay,
errors, omissions, want of security or viruses. Any views expressed in this
message are those of the individual sender, except where the sender specifies
and with authority, states them to be the views of Methanex.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
