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

AVEVA Enterprise SCADA

TABLE OF CONTENTS

Software protocol analyzer topics

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedApr 24, 2025
  • 1 minute read

Software protocol analyzer topics are used to monitor the network traffic transmitted between Omnicomm and Remote Terminal Unit (RTU) devices. The Software Analyzer (SWANA) uses these topics to enable monitoring of the protocol traffic and to receive copies of the messages exchanged with the RTUs.

Topic

Description

<system>.realtime.swan a.request.connection.

<connectionName>

The Software Analyzer (SWANA) uses this topic to request Omnicomm to start publishing connection data.

Note: Only the connection name is supported and not the connection slot number. This message is a text string — but it is not interpreted Omnicomm.

<system>.realtime.swan a.connection.<connectionName>

Omnicomm publishes connection data to this topic. This message includes:

  • Unsigned integer <protocolSequenceNumber> - The sequence number is used by SWANA to detect lost messages. It is reset to zero upon startup, failover, and mode switch.

  • String <messageType> - One of the following character strings: "Q","R", "X", "M", "S", "D". A string is currently used because C# PubSub applications do not correctly receive character messages.

  • Unsigned integer <timestampSeconds> - timestamp in Greenwich Mean Time (GMT) seconds.

  • Unsigned integer <timestampMilliseconds> - milliseconds.

  • Binary Large Object (BLOB) <message data> text containing either ASCII or non–ASCII data depending on the messageType.

  • String <remoteName> - optional remote name that is published if the message is associated with a remote.