Re: [foxboro] RIN blocks and LASTGV
- From: "Johnson, David" <David.Johnson@xxxxxxxxxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 12 Jun 2014 20:22:31 +0000
Scott,
We installed QF1185258, the 214B to EEPROM show V2.46N. The RIN blocks act the
same.
We've tried all of the various DVOPTs, with no detectable change in behavior.
That is to say, HART always gives the last good value, regardless of the LASTGV
parameter.
"current" never gives the last good value, regardless of the LASTGV parameter.
We are getting good at installing QFs though.
We're still plugging away. Let me know if you think of something else.
Regards,
David
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Landry, Scott
Sent: Wednesday, June 11, 2014 11:42 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] RIN blocks and LASTGV
David,
Also install QF1185258 which will bring the FBM214/214B to V2.46N after
EEprom. See if that helps.
What is DVOPTS set to in the ECB201 ?
DVOPTS in the ECB201.
If the device is a HART device, one of the following four settings should be
used, depending on the desired OOS and system alarm handling. With any of these
settings the ECB201 block will collect HART status and diagnostic information
which may be used for asset management purposes. With all four settings, the
4-20 mA analog current signal is available for fast control by setting the
PNT_NO parameter of the DCI block such as an RIN or ROUT to the point address
of CURRENT. See Table 5-4 for valid DCI block point address settings.
HART - Enables HART communication to the device and if the communication is
interrupted for more than a few seconds, all points are marked OOS (Out of
Service).
NOFAIL - Enables HART communication; however, the current input or output will
always be OK regardless of the HART communication failure.
NOALARM - The same as NOFAIL with the exception that system alarms will also be
suppressed for HART communication failures.
OCD - (Open Circuit Detection) Enables HART communication similar to NOFAIL but
will mark the current input or output as OOS after 10 seconds of continuous
HART communication failure.
________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of
Johnson, David [David.Johnson@xxxxxxxxxxxxxxxxxx]
Sent: Wednesday, June 11, 2014 10:56 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] RIN blocks and LASTGV
Scott,
We loaded QF1212198 in the lab (I/A version 8.7). The CP image shows 900018,
the FBM214 is EEPROM rev ROM 2.41B.
We are still seeing the behavior I described yesterday when we disconnect a
HART pressure transmitter.
That is to say, HART always gives the last good value, regardless of the LASTGV
parameter.
"current" never gives the last good value, regardless of the LASTGV parameter.
Any additional guidance is appreciated.
Thanks,
David
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Landry, Scott
Sent: Tuesday, June 10, 2014 10:18 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] RIN blocks and LASTGV
David,
Are you using QF1212198 (V900018 FCP/ZCP image) ??
Regards,
Scott
________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of
Johnson, David [David.Johnson@xxxxxxxxxxxxxxxxxx]
Sent: Tuesday, June 10, 2014 9:51 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] RIN blocks and LASTGV
Hello all,
I have run across something that seems odd, and was wondering if I could get
some corroboration from another site.
When using a RIN block in I/A version 8.8 (ICC, FCP270) the LASTGV doesn't seem
to work properly.
The short summary is, if we setup a HART device, with a RIN to read PV, we
ALWAYS get a last good value, regardless of LASTGV.
If we setup a HART device, with a RIN to read the current, we ALWAYS go off
scale low when the device fails, regardless of LASTGV.
I'm pretty sure this is not the intended behavior, can anyone with a lab and a
co-op student verify this for me?
Thanks,
David
Boring Details:
HART SETUP 1
1. ECB201 setup for HART
2. RIN is reading the PV
3. RIN has BAO configured as a 3 (Alarm on High or Low Out of Range)
4. LASTGV = 0 (Do not hold last good value)
When the transmitter fails, the .MEAS parameter ALWAYS has the last good
reading. WRONG!?
HART SETUP 2
1. ECB201 setup for HART
2. RIN is reading the PV
3. RIN has BAO configured as a 3 (Alarm on High or Low Out of Range)
4. LASTGV = 1 (hold last good value)
When the transmitter fails, the .MEAS parameter has the last good reading as
expected. OK
Same Transmitter
HART SETUP 3
1. ECB201 setup for 4-20ma
2. RIN is reading current
3. RIN has BAO con configured as a 3 (Alarm on High or Low Out of Range)
4. LASTGV=0
When the transmitter fails, the .MEAS parameter goes off scale low as expected.
OK
HART SETUP 4
1. ECB201 setup for 4-20ma
2. RIN is reading current
3. RIN has BAO con configured as a 3 (Alarm on High or Low Out of Range)
4. LASTGV=1
When the transmitter fails, the .MEAS parameter goes off scale low. WRONG!?
David Johnson
PREMIER System Integrators, Inc.
Cell :(256) 318-9257
Work :(256) 355-1732
[Description: Description: cid:image001.jpg@01C7B8C8.7DB19AF0]
________________________________
Confidentiality Notice:
The information contained in this message is private and confidential. This
information is intended only for the individual or entity named above. If the
reader of this message is not the intended recipient, you are hereby notified
that any use, review, dissemination, distribution, copying or action taken
based on this message or its attachments, if any, is strictly prohibited. If
you are not the intended recipient, please contact the sender by reply email
and delete or destroy all copies of this message and any attachments. Thank you.
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person. This email comes from a division of the Invensys
Group, owned by Invensys Limited, which is a company registered in England and
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X
7AW (Registered number 166023). For a list of European legal entities within
the Invensys Group, please select the Legal Entities link at invensys.com.
Invensys Limited is owned by the Schneider-Electric Group.
You may contact Invensys Limited on +44 (0)20 3155 1200 or e-mail
reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be subject
to the terms of any agreements between Invensys (and/or its subsidiaries and
affiliates) and the recipient (and/or its subsidiaries and affiliates).
_______________________________________________________________________
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: //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 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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person. This email comes from a division of the Invensys
Group, owned by Invensys Limited, which is a company registered in England and
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X
7AW (Registered number 166023). For a list of European legal entities within
the Invensys Group, please select the Legal Entities link at invensys.com.
Invensys Limited is owned by the Schneider-Electric Group.
You may contact Invensys Limited on +44 (0)20 3155 1200 or e-mail
reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be subject
to the terms of any agreements between Invensys (and/or its subsidiaries and
affiliates) and the recipient (and/or its subsidiaries and affiliates).
_______________________________________________________________________
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: //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 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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
