Eng.

Ahmed Essam

1
1
SOE recorder

• The Triconex Sequence of Events (SOE) Recorder

software allows you to retrieve event data from as many as
31 networked Triconex controllers.

• This event data can be used to identify the causes of

shutdowns, define corrective actions and procedures for
preventive maintenance, and solve other process-control
problems.

2
2
SOE Topology

3
3
SOE Functionality

• To enable event data to be detected by the controller,

you must define the event variables and SOE blocks in
the TriStation application.

• In addition, the application must include SOE function

blocks that start event collection.

• After you download an SOE-enabled project to the

controller, TriStation creates an SOE definition file that
contains the SOE block definitions.

4
4
Supported Hardware

• ACM . Advanced Communications Module

• NCM . Network Communications Module

• TCM . Triconex Communications Module

5
5
SOE Functionality

• To retrieve events with SOE Recorder, you must connect

the SOE workstation to a communication port on a Triconex
controller. (You can also retrieve events from a Triconex
controller with an SOE program on a non-Triconex external
device).

• You must use TriStation to set the IP address of the

controller and you must specify the address in SOE
Recorder.

6
6
SOE setup

7
7
SOE Block Types

• Historical
- Blocks 1 through 14 may be configured with any
combination of History, First Out, and External
block types.
- When the buffer is full, the MPs overwrite the
oldest event entries.

8
8
SOE Block Types

• First Out
- Blocks 1 through 14 may be configured
with any combination of History, First Out,
and External block types.
- When the buffer is full, the MPs change
the block status from collecting to stopped
and discard new events.

9
9
SOE Block Types

• External
- The External Block used by external devices,
such as a Foxboro or Honeywell DCS.
- Blocks 1 through 14 configured with any
combination of History, First Out, and External
block types.
- When the buffer is full, the MPs discard new
event entries.

10
10
SOE Block Types

• Modified External
- Applied to Blocks 15 and 16
- Used with the SMM only.
- When the buffer is full, the MPs discard new event
entries.

11
11
SOE Development in TriStation 1131

• SOESTRT (SOE Start)

Starts event collection for
a specified SOE block
(Required)

12
12
SOE Development in TriStation 1131

• SOESTOP (SOE Stop)

Stops event collection
for a specified SOE
block (Optional)

13
13
SOE Development in TriStation 1131

• SOECLR (SOE Clear)

Checks status of a
specified SOE block
(Optional)

14
14
SOE Development in TriStation 1131

• SOESTAT (SOE Statistics)

Clears a specified SOE
block (Optional)

15
15
SOE PC Implementation

• When you download an SOE-enabled TriStation project,

TriStation creates an SOE definition file in a TriStation
folder.

• Copy the SOE definition file from the TriStation project

folder to the SoeConfig folder for each controller from which
you want to retrieve data.

• The TriStation version of an application must match the

SOE Recorder version.

16
16
Warning !!!!

• The TriStation naming convention for the SOE definition

file includes the first eight characters of the TriStation
project name, the major version number, minor version
number, and time code.
An example is:
SOE_EX_9_0_33F4CE47.SOE

• CAUTION Do not rename the SOE definition file under any

circumstances. Renaming it prevents SOE Recorder from
retrieving event data.

17
17
Specifying Controllers for Retrieval

18
18
Specifying Automatic Export of Event
Data

19
19
Setting Up Event Retrieval

• The SOE definition file is copied from the TriStation

application folder to the SoeConfig folder.

• IP addresses are specified for the controllers from which

you are going to retrieve events.

• The options for event retrieval are set.

20
20
Retrieving Events

21
21