Re: [foxboro] GDEV freezing problem

Don't forget the GDEV.USERL1 and GDEV.USEL2 parameters these are connectable
and would allow the graphic overlays to be configured with the GDEV block
only as before.

Justin 

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Michael Kessler
Sent: Wednesday, December 15, 2004 2:02 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] GDEV freezing problem

I can remember seeing deviant block behaviour. I removed connections to the
.MA parameter and the problem went away. There may be some conflict between
the AUTSW.0 and the MA.1.
To do what you want I would lock the block in AUTO using the AUTSW, and Set
up a separate BOOL block to store your data.

mk

> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Rick Rys
> Sent: Wednesday, December 15, 2004 12:13 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] GDEV freezing problem
>
>
> The GDEV blocks are not connected directly to I/O.  CIN blocks are 
> used = for limit switch inputs and COUT blocks are used for Open and 
> Close = commands.
> The I/O path is via a Gateway.  The block looks like this:
> NAME   =3D COMPOUND:XV
>   TYPE   =3D GDEV
>   DESCRP =3D=20
>   PERIOD =3D 1
>   PHASE  =3D 0
>   LOOPID =3D=20
>   IOM_ID =3D=20
>   IP_FBM =3D 0
>   LM1_PT =3D 0
>   LM2_PT =3D 0
>   OP_FBM =3D 0
>   CO1_PT =3D 0
>   CO2_PT =3D 0
>   AVLLM1 =3D 1
>   AVLLM2 =3D 1
>   TOC    =3D 2.0
>   DSRTRK =3D 1
>   ZDSOVR =3D 0
>   AUTDSR =3D 0
>   MANDSR =3D :XV.AUTDSR
>   INTDSR =3D :XZ.BO02
>   HLDDSR =3D 2
>   DSR_RB =3D 0
>   HLD    =3D 0
>   INTLCK =3D :XZ.BO01
>   DISABL =3D 0
>   MA     =3D :XV.MA.1
>   INITMA =3D 1
>   MANSW  =3D 0
>   AUTSW  =3D PATT:MCIN.CIN_14
>   MANFS  =3D 0
>   SDWNOP =3D 0
>   INHOPT =3D 3
>   INHIB  =3D SEQ.ACTIVE.~
>   INHALM =3D 0x0
>   ANM    =3D=20
>   BAT    =3D=20
>   BAP    =3D 5
>   BAG    =3D 4
>   SAP    =3D 5
>   SAG    =3D 8
>   IGNLM1 =3D 0
>   IGNLM2 =3D 0
>   DEVLM1 =3D :ZLC.CIN
>   DEVLM2 =3D :ZLO.CIN
>   INVLMT =3D 0
>   INVCO1 =3D 0
>   INVCO2 =3D 1
>   PLSOPT =3D 1
>   PLSTIM =3D 100
>   STAT1  =3D CLOSED
>   STAT2  =3D OPEN
>   STAT3  =3D CLOSING
>   STAT4  =3D OPENING
>   MM1    =3D FAIL TO CLOSE
>   MM2    =3D FAIL TO OPEN
>   MM3    =3D MISMATCH
>   MM4    =3D MISMATCH
>   MODE1  =3D DISABLE
>   MODE2  =3D INTERLOCK
>   MODE3  =3D MANUAL
>   MODE4  =3D HOLD
>   MODE5  =3D AUTO
>   USERL1 =3D 0
>   USERL2 =3D 0
> END
>
> The problem is reproducible by running a loadall on a test system.  
> Once = a GDEV was frozen, rebooting the CP would not unfreeze it.  It 
> may be = related to installation issues as the plant was shutdown and 
> the CP's = initialized and reloaded and I don't know the complete 
> history of the control = database, but suspect certain iccdrvr/FOXCAE 
> manipulations.  I am not at the plant site at the moment and need to 
> investigate the reports of recent GDEV = freeze up's, as I cannot 
> verify a spontaneous freeze, following the block re-installation via 
> "Delete and Undelete".  Maybe a CAR is in order = here.
> Perhaps we found a GDEV bug or more likely we have some type of CP = 
> database installation error.
>
> Thanks,
>
>
> Rick Rys P.E.
> www.R2Controls.com
> 508-369-5186 Cell
> 508-339-6633 Home Office
> =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
>
>

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