Re: [foxboro] HART on I/A -- thoughts?

Terry,
Thanks for clearing the isolation 
issue up. I hate it when I get my 
marbles mixed up, but at least I 
haven't loss too many yet. Or so 
I think....


___________________________________
James J. H. Dykes
Tesoro Petroleum
Golden Eagle Refinery
Technical Services
Process Controls
150 Solano Way
Martinez Calif.
94553-1487

Phone:925.228.1220 Ext. 2930
E-mail:jdykes@xxxxxxxxxxx 

 


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
Behalf Of Doucet, Terrence
Sent: Monday, March 16, 2009 10:32 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] HART on I/A -- thoughts?

James,
The FBM215 and FBM218 HART modules provide galvanic isolation for all channels 
between each other and ground. Group isolation of channels to ground (not 
between channels) as seen in the FBM214 is usually only found to be deficient 
at installation and is a pain to fix.

Terry Doucet, Eng.


-----Message d'origine-----
De : foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] De la 
part de Dykes, John Envoyé : March 16, 2009 12:40 PM À : foxboro@xxxxxxxxxxxxx 
Objet : Re: [foxboro] HART on I/A -- thoughts?

The system alarm aspect is really a pain in the arse. 
I submitted a CAR about this last year and all I got was this lousy 
T-shirt....joshin'. The response was this is how the product is designed ...... 
this CAR is closed. I like the ability to "touch" most hart devices from afar 
and we had pretty good success with that and it did ease the startup of a new 
plant. The other issue I mentioned in the CAR was an observation. 
I seen a few occasions where a HART error would cause the downstream blocks to 
HOLD or TRACK with the setting of "NOFAIL". "NOFAIL" is not its descriptive 
function for sure. The 4-20mA was OK. Lack of descriptive errors and some type 
of logging is a hair puller.

As a side note and toward the decussion of FBM201 vs FBM214 The biggest thing 
to note is the issue of point to point isolation. You need to make sure this 
will not be an issue in your design.

Anyways....my two cents.

___________________________________
James J. H. Dykes
Tesoro Petroleum
Golden Eagle Refinery
Technical Services
Process Controls
150 Solano Way
Martinez Calif.
94553-1487

Phone:925.228.1220 Ext. 2930
E-mail:jdykes@xxxxxxxxxxx 

 


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Corey R Clingo
Sent: Thursday, March 12, 2009 11:59 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] HART on I/A -- thoughts?

I don't have Foxcom, either, but I have some observations and questions about 
HART on I/A, and I'm curious what other users have to say.

I first bought FBM214s on a project back in 2003.  I knew Foxboro didn't have 
any good tools for me to take full advantage of the HART data then, but I was 
looking toward the future, and I figured that at the least we would finally get 
the 250 ohms of loop resistance that should have been in the AI cards all along.


Well, it's now 2009, and I have since installed some more FBM214s in my other 
plant.  I've suffered quite a bit of pain, but haven't really seen the gain 
yet.  The RIN blocks are a joke (better in v8.4.something per AJ, but I don't 
have that).  I have resigned myself now to configuring all my 4-20mA input RINs 
as 0-65535 counts and then pointing AINs at them as if they were FBM201s (a 
helpful Foxboro gentleman down in Corpus Christi I think gave me that tip).  
Twice as many blocks for AIs -- whoopee.  And no copying from other RINs, 
because you can't change the IOM_ID (which includes the channel number, unlike 
standard AIN blocks) once the block is loaded (my techs just LOVE this).  
Really -- does anyone at Foxboro actually try to use this stuff before it 
ships?  All I can say is thank God for ICC driver task.


I've occasionally brought in SVs and TVs on the HART, and it appears to work OK 
in plant #1.  I've used IFDC in plant #1 to commission and verify transmitters, 
and it's drunken-dog slow, but it works.  Of course you can't get at the 
advanced parameters, but I'm not sure I'd want to, with it being as slow as it 
is [side note: I am told that this is because the FBM only makes one HART poll 
request per BPC, which makes it considerably slower than even HART's native 
1200 baud.]  They have FDT out now, but almost all my transmitters are 
Rosemounts (Emerson is solely in the DDL/EDDL camp), and another plant here 
where the FDT was tried couldn't get it to work.


In plant #2, I am not yet bringing in any additional HART data.  I can barely 
get IFDC to work at all.  It times out with errors almost all the time, on 
almost every transmitter.  I haven't called TAC yet, as I have higher-priority 
things going on right now, but any tips would be helpful.


System Management generates an alarm everytime a transmitter's status goes bad 
or HART comm is lost.  I have the ECBs set up as NOFAIL, so the 4-20mA doesn't 
go bad as well.  I would like this notification, except that System Management 
only tells me that "Device Failed" or some such
-- really friggin' helpful.  Makes it all but impossible to troubleshoot unless 
I just happen to have a 375 hooked up at the same time.  It makes me think that 
Foxboro and Microsoft were in bed together even before they went to Windows.  
Anyway, we usually end up inhibiting the alarms, as they drive the operators 
crazy.  Any advice here would he helpful as well.


So, what are other HART users doing with FBM214s/215s and their ilk?
Are you getting additional value out of them beyond the 250-ohm resistance? Is 
it worth the pain?


Corey Clingo
BASF Corp.





Rguercio@xxxxxxx
Sent by: foxboro-bounce@xxxxxxxxxxxxx
03/12/2009 10:04 AM
Please respond to
foxboro@xxxxxxxxxxxxx


To
foxboro@xxxxxxxxxxxxx
cc

Subject
Re: [foxboro] foxboro Digest V9 #98






What I "love" about Hart is it takes 6 blocks to configure our typical control 
loop instead of 3.
 
RGC
12803 Josey Creek Ct.
Cypress, TX 77433
713-805-8742  cell
281-256-1111 home office/FAX
281-256-1333 home  



 
 
_______________________________________________________________________
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
 
 
 
_______________________________________________________________________
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
 
 
 
_______________________________________________________________________
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
 
 
 
_______________________________________________________________________
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: