Re: [foxboro] Bad propagation
- From: "Joerg Wierz" <jwierz@xxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 20 Mar 2003 10:17:53 +0100
1.: Look at FoxDoc Document B0193AW, Chapter 6, "Connections to Source
Status" (very interesting document indeed!)
The problem is, you can't use this directly in visualisation, but I once
linked COMP:AIN.PNT..BOD to a boolean input of the PID (I used SPLRDY in a
PIDA, because I never saw that one used) and took that one for
visualisation. It's an somewaht weired solution, perhaps somebody else knows
a better way.
----- Original Message -----
From: "Andres Chianale M. (Inforsa)" <achianale@xxxxxxxxxxxxxxx>
To: <foxboro@xxxxxxxxxxxxx>
Sent: Wednesday, March 19, 2003 9:41 PM
Subject: [foxboro] Bad propagation
>
> Hi list,
>
> I have three different questions. (thanks in advance):
>
> 1. Is it possible to read the IOBAD, OOS and ERROR bits of an AIN, from =
> the
> PID where it is connected? Those bits are able to put the PID on HOLD, =
> but I
> can't find a way to read them from the PID. We need to do that because =
> we
> are incorporating animation of alarms and bad states in our =
> indications. As
> our indications are implemented with faceplates, and in the case of PID
> measurements the faceplate is based on the PID instead of the AIN, we =
> cannot
> display the AIN bad status on the PID faceplate. It would be nice if =
> those
> bits were propagated to the PID, but it seems that they only propagate =
> on
> AUTO mode and to the OUTPUT (PROPT), that's not what we need. (We use =
> mainly
> PIDXE blocks.)
>
> 2. We have communication watchdogs implemented with control blocks
> (particularly comm. with the QCS, implemented with DI50), which produce =
> a
> process alarm when the link is down. Is it possible to turn these =
> alarms
> into system alarms?
>
> 3. Have anyone implemented a watchdog for communication with PI system? =
> Any
> advice? We are mainly interested on alarming on the DCS side.
>
> we have 51 stations of 4.3 s/w version.
>
> Thanks a lot
> Andr=E9s Chianale
> Systems Engineer
> INFORSA
> Chile
> =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 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:
- » Re: [foxboro] Bad propagation
