Re: [foxboro] Hello from Fairbanks
- From: Kevin FitzGerrell <fitzgerrell@xxxxxxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 31 Jan 2006 15:24:16 +1300 (NZDT)
Hi Keith,
I just answered your post to the I/A users group when I saw this email.
I need to do some updating on my web site, I've just recently moved to a small
town in the middle of New Zealand's North Island to take a job with a large pulp
and paper mill. My new Foxboro I/A system has 45 workstations, and about 50
gateways and CPs. Fun stuff...
I've attached the quick fix text file that I think you need for the problem with
the AB Station you've noted. Let me know if you need a copy of the QF image,
I'm happy to send it. Installing the QF requires an AB-Station reboot, so is
best done during a shut. Email me if you need any more details.
Regards,
Kevin
Quoting Keith Palchikoff <Keith.Palchikoff@xxxxxxxxxxx>:
> Hello Kevin,
> Just saw your personal site with house pictures, etc. Looks nice
> considerin=
> g our cold winter nights.
>
> I am still keeping the old I/A system going - we have not done any major
> =
> upgrades but discontinued our service agreement a few years back. The =
> system has been mostly stable except for a lingering AB Station / Alarm
> =
> Manager issue. You may have seen the recent posting but since you are =
> familiar with our installation thought maybe could shed light.=20
>
> Here is the message I posted:
>
> We have an ongoing problem with AB Station (using image Ver. 6.2.1)
> block =
> level alarms not reporting to Alarm Manager application ( I/A System
> uses =
> Ver.4.3 software on AW51B station). The problem is identified when 1) =
> block detail indicates active unacknowledged alarm but alarm does not =
> sound or appear in Alarm Manager software or 2) operator notices a
> process =
> condition which normally generates alarm but no alarms appear or sound
> in =
> Alarm Manager. In this circumstance, alarm appears in AB Station block
> =
> detail. When these situations occur, the only fix has been to reboot the
> =
> AB Station. After a reboot, numerous stale or active alarms flood the =
> Alarm Manager and the AB Station / Alarm Manager system works again for
> a =
> week or month or more - problem is unpredictable.=20
>
> Does anyone know a fix or method to predict or "alarm" when the alarms
> are =
> not alarming? Is this a problem or configuration issue with AM software
> or =
> AB Station? I believe the AB Station image was installed with package =
> OS1AB4, Part Number K0175PR-A-2. Also, the problem appears limited to
> the =
> AB Stations. We do not have a similar problem with the CP stations.
>
> Appreciate any help.
>
>
> Keith Palchikoff
>
> Keith Palchikoff
> kpalchikoff@xxxxxxxxxxx
>
> >>> fitzgerrell@xxxxxxxxxxxxxxx 01/30/06 4:43 PM >>>
> In our case, we have a general guideline to build in 20% spare capacity
> =
> for
> minor additions and small projects. I've surveyed the site and tried to
> =
> bring
> spare capacity back to 20% for our main I/O types (ain, tc, rtd, aout,
> =
> cin,
> cout) by CP. =20
>
> After that, I anticipate that upgrades will provide ongoing spare I/O
> for =
> the
> plant. If we have a significant upgrade go ahead in any area we will
> look =
> at
> upgrading that area to current I/O, and any legacy I/O will be made =
> available
> for small projects.
>
> We'll continue to use the MEP program to repair modules that fail in =
> service.
>
> Regards,
>
> Kevin FitzGerrell
> Carter Holt Harvey, Ltd.
> +64 27 460 9994
>
> Quoting stan <stanb@xxxxxxxxx>:
>
> > I'm curios as to how other sites are planning on handling the end of
> > sales
> > life for 100 series FBM's.
> >
> > In our case, we have a ongoing requirement to add a loop here and
> there
> > to
> > existing systems, and have installed cabinets with extra space to
> allow
> > for
> > this. In addition most of our CP's are pre CP60. So, as these needs
> crop
> > up
> > down the road, we are going to have problems meting them.
> >=20
> > If it were as simple as installing a 200 series base, and adding that
> > to
> > the fieldbus, we could probably live with that, but the idea of
> > propagating
> > all the way back to a CP upgrade, just to add a few I/O points, is
> > neither
> > economically appealing, nor generally possible, since there are many
> > locations
> > where this CP upgrade can be done on either a unit, or a mill wide
> > shutdown.
> >=20
> > How are others planning on addressing this?
> >=20
> > --=20
> > U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite
> > Vietcong Terror=20
> > - New York Times 9/3/1967
> > =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
> > =20
> > foxboro mailing list: http://www.freelists.org/list/foxboro=20
> > to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin=20
> > to unsubscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave=20
> > =20
> > =20
>
> =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
> =20
> foxboro mailing list: http://www.freelists.org/list/foxboro=20
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin=
> =20
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave=
> =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
>
> 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
>
>
-- No attachments (even text) are allowed --
-- Type: text/plain
-- File: QF1005976.txt
_______________________________________________________________________
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
- Follow-Ups:
- Re: [foxboro] Hello from Fairbanks
- From: Kevin FitzGerrell
Other related posts:
- » Re: [foxboro] Hello from Fairbanks
- » Re: [foxboro] Hello from Fairbanks
- Re: [foxboro] Hello from Fairbanks
- From: Kevin FitzGerrell