[foxboro] GDEV functionality - was Foxboro's programming
- From: brad.s.wilson@xxxxxxxxxxxxxx
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 26 Sep 2006 10:40:36 -0400
OK, I've never had the security coding kick in before ... here's try #2.
Replying to Joseph Wu's note that GDEV provides independent outputs ... the
2 GDEV outputs, COUT_1 & COUT_2, are NOT independent.
There are (potentially) 4 output states for a GDEV ... both COUTs on, both
COUTs off, or each COUT on while the other is off. However, the GDEV only
allows for 2 desired states ... MANDSR/AUTDSR = 0 or 1.
With PLSOPT = 0, the 2 outputs are always opposite to each other (unless
INVCO is set).
With PLSOPT = 1, the 2 outputs are momentarily the same during stroking,
but it's not a permanent state.
Because INVCO1 & INVCO2 are non-connectable & non-settable, they cannot be
used to modify either scheme.
Has Foxboro ever considered making COUT_1 & COUT_2 truly independent, so
the GDEV could have 4 output states ?
Brad Wilson
Process Control Engineer
ExxonMobil Chemical Co
Edison Synthetics Plant
732-321-6115
732-321-6177 fax
Brad.S.Wilson@xxxxxxxxxxxxxx
_______________________________________________________________________
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] GDEV functionality - was Foxboro's programming
- From: joseph wu
Other related posts:
- » [foxboro] GDEV functionality - was Foxboro's programming
- » [foxboro] GDEV functionality - was Foxboro's programming
- Re: [foxboro] GDEV functionality - was Foxboro's programming
- From: joseph wu