[foxboro] R: IND Block error

 R: [foxboro] IND Block error


I suggest you an IF THEN clause, checking is the = associated station is
alive. This event was discussed not later than one = year ago on this list.
There is also my contribution as we manage the = same problem: we check
quality bit of a variable defined on the station = and linked to a CP block.
It worked on 6.3 under Solaris as well as on = 8.4 under Infusion/Mesh. 
Ciao
Alessandro Ghiglione
Infineum Italia

----- Messaggio originale -----
Da: foxboro-bounce@xxxxxxxxxxxxx = <foxboro-bounce@xxxxxxxxxxxxx>
A: 'foxboro@xxxxxxxxxxxxx' <foxboro@xxxxxxxxxxxxx>
Inviato: Fri Nov 06 18:45:44 2009
Oggetto: [foxboro] IND Block error

Ok, I was surprised by a block error yesterday on a ind block = (46IND5325).
Basically the code loops through a sequence of checks and = events and
duringone check it will send the following command IF a = certain condition
exists.
:46AW03DMCMD :=3D "dmcmd = /OPT/MENUS/46AREA/PAPER_MACHINE/BROKE.FDF";

Normally the command will pull up a display (BROKE.FDF) on Foxview = 46AW03.
Here is where the catch comes into play. The station(46AW03) had = a
hardwareproblem and was not powered up or on the mesh and caused the = seq
block to go to manual. Since the MA parameter is set to "MA =3D =
:46IND5325.MA.1" The block would kick back into auto and fail = again,
etc....

So my question to all is how would you handle the block so it doesn't = fail
just because a workstation is not alive? Error handling routine? = IF/Then
check? Some other means? I was very surprised that the block = knew the
station was not reachable and the ind block went to manual!
Ronald G. Schafer
Distributed Controls System Administrator
White Birch Paper Company
Bear Island L.L.C. Division
10026 Old Ridge Road
Ashland VA, 23005
Phone 804-227-4034
Fax 804-227-4052
Email: rschafer@xxxxxxxxxxxxxxxxxxxxxx<mailto:rschafer@xxxxxxxxx=
irchpaper.com[1]>




_______________________________________________________________________ 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.th= ecassandraproject.org/disclaimer.html[2]

foxboro mailing = list:           &n= bsp; http://www.freelists.org/l=
ist/foxboro[3]
to subscribe:         mailto:foxbo=
ro-request@xxxxxxxxxxxxx?subject=3Djoin[4]
to unsubscribe:      mailto:foxb=
oro-request@xxxxxxxxxxxxx?subject=3Dleave[5]



--- Links ---
   1 3D"mailto:rschafer@xxxxxxxxxxxxxxxxxxxxxx";
   2 3D"http://www.thecassandraproject.org/disclaimer.html";
   3 3D"http://www.freelists.org/list/foxboro";
   4 3D"mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin";
   5 3D"mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave";
 
 
_______________________________________________________________________
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: