Scribd Logo
Upload

Welcome to Scribd!

  • 90 views

    Technical Description: Infi90/Symphony/Harmony - Controlway

    Uploaded by

    Yhony Gamarra Vargas
    This technical document identifies conditions that can contribute to errors and loading on the Controlway network. It provides recommendations to minimize these issues and create a stable Controlway environment. Specifically, it describes four main issues: viewing backup controller configurations, unresolved hard faults, bus saturation from excessive loading, and configuration errors. The document recommends ways to address each issue, such as offsetting exception report timeouts, monitoring Controlway status, reducing unnecessary data transfers, and validating module status tags and function code configurations. It also introduces a new Controlway version that enhances fault tolerance handling when certain module combinations are used.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Technical Description: Infi90/Symphony/Harmony - Controlway

    Uploaded by

    Yhony Gamarra Vargas
    90 views6 pages
    This technical document identifies conditions that can contribute to errors and loading on the Controlway network. It provides recommendations to minimize these issues and create a stable Controlway environment. Specifically, it describes four main issues: viewing backup controller configurations, unresolved hard faults, bus saturation from excessive loading, and configuration errors. The document recommends ways to address each issue, such as offsetting exception report timeouts, monitoring Controlway status, reducing unnecessary data transfers, and validating module status tags and function code configurations. It also introduces a new Controlway version that enhances fault tolerance handling when certain module combinations are used.

    Original Title

    Untitled

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This technical document identifies conditions that can contribute to errors and loading on the Controlway network. It provides recommendations to minimize these issues and create a stable Controlway environment. Specifically, it describes four main issues: viewing backup controller configurations, unresolved hard faults, bus saturation from excessive loading, and configuration errors. The document recommends ways to address each issue, such as offsetting exception report timeouts, monitoring Controlway status, reducing unnecessary data transfers, and validating module status tags and function code configurations. It also introduces a new Controlway version that enhances fault tolerance handling when certain module combinations are used.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    90 views6 pages

    Technical Description: Infi90/Symphony/Harmony - Controlway

    Uploaded by

    Yhony Gamarra Vargas
    This technical document identifies conditions that can contribute to errors and loading on the Controlway network. It provides recommendations to minimize these issues and create a stable Controlway environment. Specifically, it describes four main issues: viewing backup controller configurations, unresolved hard faults, bus saturation from excessive loading, and configuration errors. The document recommends ways to address each issue, such as offsetting exception report timeouts, monitoring Controlway status, reducing unnecessary data transfers, and validating module status tags and function code configurations. It also introduces a new Controlway version that enhances fault tolerance handling when certain module combinations are used.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 6

    Technical Description

    Infi90/Symphony/Harmony - Controlway

    Products Concerned: Infi90 / Symphony / Harmony

    Description: This document identifies several conditions that contribute to Controlway errors
    and loading that must be addressed to create the most stable Controlway environment possible.

    Controlway Communication Issues


    The following list describes conditions that contribute to Controlway loading and/or Controlway errors
    which can impact communications on the Controlway bus.

    Issue 1 – Viewing the backup controller configuration:


    Do not view the configuration in a back-up controller with the engineering tools (Composer or WCAD).
    This does not apply during online configuration but must be avoided under all other conditions.

    Issue 2 – Hard fault condition on Controlway:


    Always resolve Controlway status errors in a timely manner. Consider adding configuration to monitor
    the Controlway status and alert the operators when a problem is discovered.

    Issue 3 – Bus saturation:


    To operate correctly, Controlway always needs to have available free time on the bus. Instances where
    the bus load is saturated (even just momentarily) can cause missed data as well as introduce errors on
    the Controlway. Controlway loading can only be measured by ABB Field Service personnel, and only
    using a diagnostic that is performed by the field service organization.
    To minimize Controlway loading, the following configuration conditions should be reviewed.

    A. Maximum exception report timeout setting


    When multiple segments are used, offset the value of spec 8 in each FC82 so that the
    max time spike of exception reports for a given segment occurs at a different time than the
    other segments. In PCUs with multiple modules, consider including this offset concept in
    each module, so that each module’s max timeout occurs at different times. This
    technique is a good general practice to provide communications load-leveling within a
    system

    B. Significant change parameter


    This setting is in spec 9, function code 82 for all exception reporting function codes that do
    not have their own specification for this setting.
    This setting determines the minimum % of change for a given signal that will trigger an
    exception report. The smaller this number, the more frequently a given exception report is
    likely to send a new report. It may be appropriate for some exception reports to report on
    very small changes but it is unlikely that every single analog point in the system needs to
    be reporting at a 0.1% significant change. Consider the range of the input and the typical

    ABB Inc.

    Doc. Id. 3BUA001575R0001 Rev. A Date. 2010-Feb-03 1 (6)


    process conditions to determine an appropriate significant change % that provides
    meaningful indication to the operators while reducing unnecessary loading of the
    Controlway.

    C. Update rate of Controlway peer to peer communications


    Spec 2 of Function code 90 is the base Controlway update rate. Peer to peer updates will
    happen no faster than this setting. Spec 13 of function code 82 determines how often this
    particular segment samples peer to peer communications. Spec 13 of FC82 should be a
    multiple of spec 2 of FC90 (typically 4 times larger)
    Peer to peer communications use Function codes 25, 41, 63, and 64. Function codes 25
    and 41 will update at the rate set in spec 13 of FC82. Function codes 63 and 64 have
    specifications that would allow these blocks to update at a different rate than defined by
    spec 13 of FC82, but no faster than spec 2 of FC90. Function codes 25 and 41 are
    individual point transfers. Function codes 63 and 64 support up to 8 points per transfer.
    If you have multiple points being transferred, using FC63 and 64 is more efficient and will
    reduce Controlway loading.

    Issue 4 – Configuration error:


    The following configuration conditions can introduce errors on the Controlway, ultimately increasing
    Controlway loading and likely introducing communication problems on the Controlway.

    A. Module status tags configured for backup modules


    The module status tag type differs by console but will be one of the following tag types:
    N90STAT, MODSTAT, or Harmony Module Status

    Valid module status tag conditions:


     Both the primary and backup NPM (since NPMs actually have address zero and
    address one)
     ICI modules (always module address 2)
     Console nodes (ICI type module, always at module address 2)
     Only the primary module address for redundant pairs of controllers
     Both the primary and backup bridge/gateway nodes, but only the ‘local’ side of
    any bridge/gateway nodes (always module address 2).

    Invalid module status tag conditions

     Status tag for the backup controller address in a redundant pair.


     Status tag for the ‘remote’ or ‘backside’ of a bridge/gateway node. This concept of
    ‘backside’ is from the perspective of the console in question. For example, with a
    bridge node connecting loop 1 to loop 3, a console on loop 1 can have a status tag
    for the loop 1 side of the bridge node but must not have a status tag for the loop 3
    side of that same bridge. Conversely, a console on loop 3 can have a status tag
    for the loop 3 side of that bridge but must not have a status tag for the loop1 side
    of the bridge.

    ABB Inc.

    Doc. Id. 3BUA001575R0001 Rev. A Date. 2010-Feb-03 2 (6)


    Corrective action for invalid module status tags:
    If the system currently has module status tags for redundant controller addresses, the
    corrective action sequence is as follows:
    1. Delete the invalid tag from all console databases. Be thorough in checking all
    console databases including all non-ABB consoles on all rings. It only takes one
    instance of this invalid condition to introduce the potential for difficulties.
    2. Reset the console ICI for all consoles that had these tags deleted
    3. For any bridge nodes involved, halt those bridges (both if redundant). Consider
    also any bridges that are in the path of the invalid status tag entry. Those bridges
    must also be halted.
    4. Reset both the primary and backup NPM of the node with the controllers that had
    module status tags configured for the backup controller. Note: This will remove
    the PCU from the Infinet for approximately 30 seconds.
    5. Restart the bridges

    B. Function code 95 configured to point to the backup module address


    Spec 2 of Function code 95 is the target module address. This cannot be a backup
    controller address.

    C. FC63/64 configured to point to block 9999.


    In the BRC300 and BRC400, block 9999 is a user configurable block address. When
    using BRC300/400, do not leave the default value of 9999 for the source block address
    specification unless that is actually the proper block to be monitoring.

    The various conditions in this document can exist in any system and the system may not be exhibiting
    outward problems. However, these conditions are undesirable and known to be contributing factors
    when problems are observed. It is strongly encouraged that these conditions be avoided or addressed.

    Using Controlway assembly A_2 and implementing the above recommendations will provide a stable
    Controlway environment.

    Controlway Board Assembly A_3 and FPGA Revision E


    A new Controlway version with enhanced fault tolerance handling is now available from ABB. Providing
    certain module and Controlway combinations are employed (see table 1), Controlway assembly A_3 and
    the FPGA Revision E implementations will enhance the communication management of the Controlway
    (even if any of the four identified communication issues are present in the system). Controlway

    ABB Inc.

    Doc. Id. 3BUA001575R0001 Rev. A Date. 2010-Feb-03 3 (6)


    A_3/FPGA_E provides a stable Controlway environment when implemented per the requirements of this
    section.
    Note, while some improvement in fault tolerance handling will occur in Harmony PCUs with
    i modules containing a mix of A_2 and A_3 Controlway versions, to achieve the full benefit all
    modules within the Harmony PCU must contain version A_3/FPGA_E.

    Table 1 identifies the communication issue fault tolerance provided by various module and Controlway
    combinations.

    Table 1 – Communication Issue Fault Tolerance for various Harmony Module and Controlway
    Combinations
    Module Combinations within a Controlway Communication Issue Fault Tolerance
    Harmony PCU Assembly / FPGA Provided by the Combination
    Revision
    Combinations
    NPM rev BRC rev
    NPM22 + BRC300/400 FPGA_E FPGA_E Provides fault tolerance for all issues 1, 2,
    4A, 4B, and 4C
    Issue 3 must be resolved
    NPM12 + BRC300/400 A_3 FPGA_E Provides fault tolerance for all issues 1, 2,
    4A, 4B, and 4C
    Issue 3 must be resolved
    NPM22 + MFP12 FPGA_E A_3 Provides fault tolerance for issues 1, 2, 4B,
    and 4C.
    Issues 3 and 4A must be resolved
    NPM12 + MFP12 A_3 A_3 Provides fault tolerance for issues 1, 2, 4B,
    and 4C.
    Issues 3 and 4A must be resolved
    NPM12 + xxxx A_2 Any rev None - All issues 1 - 4C must be resolved
    xxxx + MFP12 Any rev A_2 None - All issues 1 - 4C must be resolved
    Notes:
    1. The Controlway improvements are available either as a daughterboard assembly (A_3) or as an
    integrated FPGA revision (FPGA_E). Not all module types accept the A_3 daughterboard or FPGA
    update. Contact ABB Service to determine which Controlway version is needed to update your
    system.
    2. Controlway should NEVER be fully saturated under any conditions, regardless of the version of
    Controlway that is installed.

    In addition to the fault tolerance improvements, support for modulebus for the MFP12 and BRC300/400
    controller modules has been added in Controlway A_3/FPGA_E.

    ABB Inc.

    Doc. Id. 3BUA001575R0001 Rev. A Date. 2010-Feb-03 4 (6)


    Firmware Compatibility Tables
    The following tables provide Controlway version and module firmware compatibility information.

    Table 2 – Controlway Assembly A_2 Module Firmware Requirements


    Module type Controlway assembly revision Minimum required firmware revision
    IMMFP12 A_2 G_A
    IMCPM02 A_2 B_0
    INNPM12 A_2 F_8
    Harmony BRC100/200 N/A (note 1) N/A
    Harmony BRC300/400 A_2 Any
    Notes:
    1. Controlway assembly A_2 is not approved for the BRC100/200. ABB recommends upgrading to
    BRC300/400 to take advantage of the most current Controlway enhancements.

    Table 3 – Controlway Assembly A_3 / FPGA_E Module Firmware Requirements


    Module type Controlway assembly revision Minimum required firmware revision
    IMMFP12 A_3 G_A
    IMCPM02 A_3 B_0
    INNPM12 A_3 F_8
    Harmony BRC100/200 N/A/ (note 1) N/A
    Harmony BRC300/400 A_3 (note 2) L_4
    Notes:
    1. Controlway assembly A_2 is not approved for the BRC100/200. ABB recommends upgrading to
    BRC300/400 to take advantage of the most current Controlway enhancements
    2. BRC300/400 modules that contain A_1 or A_2 Controlway assemblies cannot be upgraded to the
    A_3 Controlway assembly. These specific modules can be upgraded to have the Controlway
    assembly removed and revision E FPGA code installed, but the modules must be returned to the
    factory for this upgrade.

    ABB Inc.

    Doc. Id. 3BUA001575R0001 Rev. A Date. 2010-Feb-03 5 (6)


    REVISION

    Rev. ind.: Page (P) Description Date


    Chapt. (C) Dept.

    ABB Inc.

    Doc. Id. 3BUA001575R0001 Rev. A Date. 2010-Feb-03 6 (6)

    You might also like