Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Communication Drivers

Diagnostics and error tracing

  • Last UpdatedSep 05, 2024
  • 1 minute read

The GESRTP Communication Driver uses the standard diagnostic information provided by the Operations Integration Toolkit. Access to other internal diagnostic registers of the PLC is performed through reads and writes via the syntax used in item naming.

The GESRTP Communication Driver supports error messages, controller-specific error messages, and error codes. Use the Log Flag data to customize the type of messages logged to the Log Viewer.

Note: See the Log Viewer Help for more information about using log flags.

GESRTP Communication Driver Log Flags

The GESRTP Communication Driver supports the following server-specific log flags.

  • Errors
    General errors from the Communication Driver have the prefix "ERROR." They are highlighted in red so that you can find them quickly. Log flags for GESRTP-specific errors have the suffix "_ERROR." They include CONNECTION_ERROR, POLL_ERROR, and POKE_ERROR.

  • Trace
    General traces from the Communication Driver have the suffix "_TRACE." The sever-specific trace log flags include CONNECTION_TRACE, POLL_TRACE, and POKE_TRACE.

    The following table lists all the available logger flags and their meanings.

    Type

    Name

    Description

    Server Flag

    ERROR

    Shows general server errors.

    TRACE

    Shows general server traces.

    Transaction Flag

    CONNECTION_ERROR

    Shows connection errors.

    POLL_ERROR

    Shows errors of poll messages.

    POKE_ERROR

    Shows errors of poke messages.

    CONNECTION_TRACE

    Shows connection traces.

    POLL_TRACE

    Shows traces of poll messages.

    POKE_TRACE

    Shows traces of poke messages.

Related Links
TitleResults for “How to create a CRG?”Also Available in