Re: [foxboro] Bad Value Status and HLBL
- From: "Moramarco, Leo" <leo.moramarco@xxxxxxxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 24 Apr 2006 17:07:30 -0400
The first option would be to connect the parameter that you are reading,
into one of the sequence block input and then use the status extension as
described bellow:
OPTION 1: This is straight out of the HLBL documentation (B0400DF)
--------------------------------------------------------------------------
Reference Format
The path specified in a reference must not contain any spaces or comments.
External references are case sensitive. All compound names, block names, and
parameters must be entered in uppercase.
Internal Reference Formats:
PARAM
PARAM.STATF
where:
. = Separates parameter and status field names
PARAM = User-labeled parameter name (one to ten characters).
STATF = ON, SECURED, BAD, OOS, ERROR, or QUALITY parameter status field.
Examples:
FILLFLAG
HEAT_F
LEVEL_F.SECURED
-------------------------------------------------------------------------
The other option is to use the Boolean extensions specification and connect
the Source Status to a Boolean input of the sequence block:
Example: BI0001=COMP:SWITCH1.INPUT1.ext
Where: ext = B,O,D,E (Bad,Out-of-Service,Disconnect,Error)
You can also OR these statuses bits as in:
Example: BI0001=COMP:SWITCH1.INPUT1.BOE (this Ors the Bad+OOS+ERROR)
For more details see BO193AW Connections section.
Leonardo Moramarco
Instructor, Lifetime Learning Center
Invensys Systems Canada Inc.
Foxboro Division
Phone: 514.421.8301
Fax:514.421.8301
Cell:514.942.4342
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Jerry Hidahl
Sent: Monday, April 24, 2006 4:09 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Bad Value Status and HLBL
Hi, Everyone.
I've got a problem where a sequence program (HLBL) is getting an external
real value from a SWCH block storing it to a dependent block parameter. The
value includes error status which is also being stored. That's okay, so
far. The problems occur when a host program, the IADriver task for FoxBatch
(original version) attempts to read the occasional bad value and fails. I
need to find a way to detect the error status of the value within the
sequence program, and either strip it off or just avoid assigning the
value.
I've looked through the documentation available to me and found no clues.
Does anyone out there have any ideas for detecting error status in real
values within a sequence program?
Jerry Hidahl
Huntsman Corp.
Port Neches, TX
_______________________________________________________________________
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:
