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 ?
________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of
G.Macdonald@xxxxxxxxx [G.Macdonald@xxxxxxxxx]
Sent: Tuesday, January 26, 2016 12:52 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AOUT Issue
We have tried both with no success.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Jared Wright
Sent: Tuesday, January 26, 2016 11:02 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AOUT Issue
Just curious, have you tried a DVOPTS of NOFAIL or NOALARM? I was just
wondering if disabling the Hart FBM's ability to mark a point OOS based on Hart
corrects any of these issues. NOALARM and NO FAIL still allow Hart
functionality.
-------- Original message --------
From: G.Macdonald@xxxxxxxxx
Date: 01/26/2016 12:29 PM (GMT-05:00)
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AOUT Issue
We are also experiencing a similar issue. We have recently installed a
significant number of Hart FBM's Input's and Outputs (214B's, 215's and 244's).
We have seen the issue on inputs as well as outputs, although the outputs are
more attention getting. From what we have diagnosed when the issue arises we
are getting SMON entry " malfunction retry count exceeded". We are running the
latest firmware 2.47C. From the testing we have done, we believe the issue is
being caused when the system detects a field device malfunction on the Hart
which then causes the primary variable on the ROUT/RIN 4-20 to fail/hold. The
AOUT does not hold / fail. Once the Hart malfunction resolves, the 4-20
start's functioning again (now there is a big bump). The only fix we have been
successful at is to turn off the Hart for the FBM Channel in the ECB (DVOPTS),
essentially turning it into a 4-20 only.
Grant
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Prakash I.G.
Sent: Monday, January 25, 2016 7:59 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AOUT Issue
Hi
In my previous mail I had mentioned that Hart Modules problem not repeated
after firmware upgradation but today one Hart module hanged. So anybody can
suggest about cause.
Prakash G
On 23 Jan 2016 8:20 am, "Prakash I.G." <prakashig.2011@xxxxxxxxx> wrote:
Hi
After firmware upgradation problem not repeated.
Prakash G
On 23 Jan 2016 2:37 am, "Brian Long" <blong@xxxxxxx> wrote:
Thanks, were you able to prove it was fixed with firmware?
Brian
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Prakash I.G.
Sent: Friday, January 22, 2016 8:04 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AOUT Issue
Hi
We had faced same problem in Hart Modules. Need to upgrade firmware.
Prakash G
On 21 Jan 2016 9:53 pm, "Brian Long" <blong@xxxxxxx> wrote:
We had an AOUT block go into HOLD for some unknown reason, causedcome out
us some down time. No matter what was tried (in SELECT) block
would not
of HOLD, nothing addressed to it, no SEQ code, etc. Going to ICC and//www.freelists.org/list/foxboro
doing a DONE fixed, did not have to do DELETE/UNDELETE. This was
not new config, no system changes or updates were done. This is a
CP270 lightly loaded.
Anyone else seen anything like this before? This actually has us
very concerned.
Thanks in advance,
Brian Long
___________________________________________________________________
___ ___ 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<http://www.thecassandra
project.org/disclaimer.html>
foxboro mailing list:
to subscribe:mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_____________________________________________________________________
____ 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<http://www.thecassandrapr
oject.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 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<http://www.thecassandrapr
oject.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
