Where are the limits defined for AI Status OPTS "BAD if Limited"

Greetings all

A quick look in Books Online for 'STATUS_OPTS'  and 'BAD if Limited' yields only - "Sets the output status to BAD if the sensor is at or beyond a high or low limit" -

Am I correct in assuming that OVERRANGE_PCT and UNDERRANGE_PCT at the AI channel are the limits for the 'BAD if Limited' parameter in the CM's AI block?

Second question -

Is there a real set of (configuration/engineering) reference manuals available for DeltaV?

Thanks in advance, and kudos for all the great help that is happening on EE365

  • Yes absolutely right that OVERRANGE_PCT and UNDERRANGE_PCT are the limits for Triggering Bad status when BAD if Limited is configured True.
    As far as CSLS We have Official documents TGNs which guides you for Engineering.
  • In reply to Sathishbabu.bv:

    Thank you for confirming.
    How can I access the TGN's?
  • Thank you for contributing great questions like this one, . We look forward to seeing more from you in the EE365 community.

    Best Regards,

    Rachelle McWright: Business Development Manager, Dynamic Simulation: U.S. Gulf Coast

  • In reply to SimHogan:

    You are saying that CSLR (LBP?) has technical configuration guides.. right?
    How can a sysadmin get the reference manuals?
  • In reply to SimHogan:

    Sorry, I am not sure are we allowed legally to distribute the Engineering Manuals in community

  • In reply to Sathishbabu.bv:

    Thanks again for the update.
  • In reply to SimHogan:

    Looks like PCSD Books Online contains the level of information I am needing.
    Thanks again EE365
  • In reply to SimHogan:

    SimHogan, Where did you find PCSD Books Online? That can be useful to us.
  • In reply to MPHymel:

    It was made available from LBP when we installed 12.3.1. I had forgotten we had not installed it on Pro or ProPlus.
    I recommend checking with LBP, and hopefully someone else here will advise
  • I wanted to add some additional info since I recently came across this question:

    OVERRANGE_PCT & UNDERRANGE_PCT are the limits at which a sensor reading is considered "limited".
    Built into each analog input are separate limits that determine when a sensor reading is BAD. For instance, an AI Charm automatically goes BAD when the I/O channel reaches its internal HARD coded limits (in the case of the Charm 0mA/-20% or 25mA/131.25%). The AI Charm will only go BAD outside the hard-coded limits, unless you check the STATUS_OPTS parameter to change the quality of the signal to BAD if Limited. Then it will go BAD based on the limits you define in the DST fields.
    This isn't really explicitly defined anywhere in BoL that I could find.


    For classic I/O if the channel value is outside the range of -20.12 to 116.6%, the channel input status is set to BAD by the input card.
    For CHARM I/O channel status depends on the configured CHARM functionality:
    For 4 - 20 mA CHARMs, the card sets the channel status to BAD when the channel value is greater than 131.25% (25 mA).
    For 0 - 20 mA CHARMs, the card sets the channel status to BAD when the channel value is greater than 125% (25 mA).

    The STATUS_OPTS parameter allows you to choose how the PV and OUT status are determined. There are three AI block status options:
    Uncertain if Man mode -- Sets the OUT status to Uncertain if the block's mode is Manual
    Bad if Limited -- Sets the PV status to Bad if the channel input status is limited.
    Uncertain if Limited -- Sets the PV status to Uncertain if the channel input status is limited.
  • In reply to Alex Lutz:

    Alex, That is a nice review. Thanks for posting. Just want to add that AI status can also be controlled by enabling NAMUR option. This sets the signal to BAD status if it exceeds the NAMUR limits of 21 mA or 3.6 mA for four seconds. The low limit is ignored if the signal is configured 0-20 mA.

    The Overrange/Underrange and NAMUR_ENA are set in the channel settings and set HI/LO Limit or BAD status, respectively on the CHANNEL.

    Note that the NAMUR limits are not configurable. They are intended to set the channel BAD if the field device is configured to drive its mA signal to a saturated value on transmitter faults. This saturated value will not trigger the absolute channel limits of the AI channel, which are used to detect an Open circuit or Short circuit condition.

    There are also the HART_ERRORS which can be used to effect channel status when the field device is a HART device.

    The AI block STATUS_OPTs (also the PID Block status options) can be used as described with the Limit status is used to set configurable limits for BAD status, as stated above.

    Andre Dicaire

  • In reply to Andre Dicaire:

    would you still need to set "Bad if Limited" in the controller status opts if the NAMUR Enable is set, and you are using a NAMUR capable transmitter?
  • In reply to MPHymel:

    NAMUR limits set Bad Status on the Channel when NAMUR limits are reached. If signal becomes limited for other reasons such as Over range limit set below NAMUR and you might want Status to go BAD, then yes. But once status is BAD, it doesn't get BADDER.

    Andre Dicaire