Re: [foxboro] Foxboro I/A interface with PLC5/30's
- From: "Jaime Claramunt R. (Inforsa)" <jclaramunt@xxxxxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 24 May 2005 08:38:58 -0400
About the way to adress points... are you using MCIN/MCOUT, PACKIN/PACKOUT ?
and if it's so, how do you treat individual alarming in DCS for each signal
?
We have some similar AB-DCS comms (old ABStation, and INT30-KF2), but we are
usung CIN/COUT because of the alarm/acknowledge capacities...
Operator disliked those blocks with 8 alarms because the ack is for all 8,
not each one separatelly (BOOLALM).
So we cannot optimize loads and/or add more points.
Do you think using MCIN/MCOUT in integrators and MCIN+CIN in CP is a
feasible approach ? (more pear-to-pear, though)
Jaime Claramunt
Inforsa
-----Mensaje original-----
De: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]En
nombre de Jones, Charles R. (Chuck)
Enviado el: Lunes, 23 de Mayo de 2005 17:16
Para: 'foxboro@xxxxxxxxxxxxx'
Asunto: Re: [foxboro] Foxboro I/A interface with PLC5/30's
I recommend clearly defining the separation between the PLC and I/A very for
a couple of reasons. One reason is to lower the amount of information that
needs to pass between them to the smallest amount necessary. If you can
define the BMS down to a "black box" you may treat it similarly to a motor
-- Turn ON, Turn OFF, Let me know if there is a problem, etc.
The other reason is to comply with safety regulatory agencies. I recommend
keeping the BMS as self-contained as possible, but the regulations in your
area may be different than mine. (And, if the current BMS works, why fix
it?) Lowering the amount of communication between I/A and burner management
makes it easier to certify for safety--and to troubleshoot, later on.
Our equipment is older than you have to work with. We have redundant CP30s
and AP51As. We use an AB Gateway. The basic processing cycle is 2 seconds.
So, our BMSs have to be self-contained to be fast enough. But, the combined
system works just fine.
Once you have clearly defined what each processor will do, the communication
solution will depend on how much data you actually need to pass between I/A
and PLC (and to how many PLCs you must communicate).
Chuck Jones
Refinery Automation Technologist
Tate & Lyle -- Lafayette South Plant
765.477.5324 - Office | 877.536.9219 - Pager
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Baptiste, Nigel
Sent: Monday, May 23, 2005 3:21 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Foxboro I/A interface with PLC5/30's
Thanks Chuck.
The I/A system (Unix based) will be doing the boiler combustion controls =
and motor control as well as data acquisition.
The project is still in the planning stages so I am seeking advice on =
how to proceed. We can do either of your options but I would like to =
know which is your recommendation based on your experience.
NB.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Jones, Charles R.
(Chuck)
Sent: Monday, May 23, 2005 4:12 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] Foxboro I/A interface with PLC5/30's
I've done this and I'm sorry to hear about your troubles... But =
seriously,
now it's not as bad as it once was.
Before we can begin to send you advice, can you let us know whether you =
are
running on Unix or Windows? =20
And, will your I/A system primarily supply the user interface or will =
there
be controls as well? =20
Or, better yet (since the PLC is only for BMS), can you focus your I/A =
to AB
interface down to passing a few digital bits of information back and =
forth?
Is it good enough that the I/A can just say, "Turn ON (or OFF) the =
flame"
and is it okay if the I/A only has to know whether the flame is ON or =
OFF?
Chuck Jones
Refinery Automation Technologist
Tate & Lyle -- Lafayette South Plant
765.477.5324 - Office | 877.536.9219 - Pager
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
On
Behalf Of Baptiste, Nigel
Sent: Monday, May 23, 2005 2:59 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Foxboro I/A interface with PLC5/30's
Hello list,
Does anyone have experience interfacing I/A with AB PLC5/30's?
I have to integrate the two for combustion control & burner management =
=3D
on a steam turbine generator unit.
The combustion controls would be replaced with the I/A system but the =
=3D
budget does not permit the replacement of the PLC based BMS.
Hence I'm seeking the best way to interface the two systems.
Regards,
Nigel Baptiste.
=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: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
*************************************************************************=
****************************
This email and any files transmitted with it are confidential and =
intended solely for the=20
use of the individual or entity to whom they are addressed. If you are =
not the intended=20
recipient or the person responsible for delivering the email to the =
intended recipient, be=20
advised that you have received this email in error that any use, =
dissemination,=20
forwarding, printing, or copying of this email is strictly prohibited. =
If you have received=20
this email in error please notify the sender immediately. Please note =
that we reserve=20
the right to monitor and read any emails sent and received by the =
Company in=20
accordance with and to the extent permitted by applicable legal rules.
*************************************************************************=
****************************
=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: //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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
****************************************************************************
*************************
This email and any files transmitted with it are confidential and intended
solely for the
use of the individual or entity to whom they are addressed. If you are not
the intended
recipient or the person responsible for delivering the email to the intended
recipient, be
advised that you have received this email in error that any use,
dissemination,
forwarding, printing, or copying of this email is strictly prohibited. If
you have received
this email in error please notify the sender immediately. Please note that
we reserve
the right to monitor and read any emails sent and received by the Company in
accordance with and to the extent permitted by applicable legal rules.
****************************************************************************
*************************
_______________________________________________________________________
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:
