Professional Documents
Culture Documents
The text and screen shots in this document are compatible with Workbench Version 8.3.0 and subsequent releases. If you are running a previous
version, please contact Technical Support.
3
SOE Getting Started
Contents
CONTENTS ......................................................................................................................................................... 3
INTRODUCTION ................................................................................................................................................. 4
SOE COMPONENT OVERVIEW ........................................................................................................................ 4
SOE ADMINISTRATION CLIENT ............................................................................................................................ 4
SOE DATA RETRIEVAL CLIENT ........................................................................................................................... 4
SOE SERVICE MANAGER MONITOR .................................................................................................................... 5
SYSTEM REQUIREMENTS................................................................................................................................ 5
INSTALLING THE SOE SOFTWARE................................................................................................................. 6
SOE EXAMPLE................................................................................................................................................. 12
RECORDING DATA FROM AN SOE MODULE ....................................................................................................... 12
RECORDING DATA CHANGES FROM OTHER REGISTERS ..................................................................................... 13
SOE ADMINISTRATION CLIENT .......................................................................................................................... 16
SOE DATA RETRIEVAL CLIENT ......................................................................................................................... 19
SOE DATA FORMAT ......................................................................................................................................... 21
Introduction
Sequence of Events (SOE) data gives an accurate time for event occurrence, along with the event value and
other useful information. This data can then be used to help determine a specific order of occurrences or
"Sequence of Events." There are two different kinds of events that can be recorded: data change events from
SOE modules based on channel inputs or data change events from analog or digital registers found in the
controller. Data change events can be recorded no faster than the cycle time of the controller while SOE
module events are recorded in accord with times in the module’s data sheet (order of milliseconds).
The 8000 IO Configurator is used to configure the SOE channels from which data is captured. The Event
Recording Table for the controller is used to determine the analog and digital points from which data is
recorded.
After the controller is configured to generate events, it begins storing the events into its SOE buffer. If the SOE
buffer becomes full, then the oldest events are lost as new SOE events are generated. However, there is no
need to lose events, since they can be retrieved by the SOE Service Manager and recorded into a Microsoft
SQL Server database. In fact, the controller can support up to four SOE Service Manager clients.
System Requirements
• Operating System: Windows 2000 Service Pack 3 or Windows XP Professional Service Pack 2
• Processor: Pentium 3 or greater
• Memory: 256M Byte or greater
Note: If your computer already has version 8.3.0 or later of the Workbench, SOE was
installed by the Workbench installation utility. Otherwise, SOE can be installed as a
standalone utility according to the following instructions.
Note: The text and screen shots in this document are compatible with Workbench Version 8.3.0
and subsequent releases. Version x.x.x on the screen shots refers to the current version number of
the product that is being installed.
4. The Additional Programs screen appears. Select the Sequence of Events (Standalone Version)
option and click Go.
Note: If the Workbench is already installed on your computer, the following error occurs. If you
would like SOE only to be installed on this computer, uninstall the Workbench before installing
SOE. If you would like both SOE and the Workbench to be installed on this computer, the
Workbench installs both programs.
9. Select the Complete installation type from the Setup Type screen. Only advanced users should
utilize the Custom installation option. Click Next to continue.
10. The Ready to Install the Program screen appears. Click Install.
12. Following a successful installation, the InstallShield Wizard Completed screen appears. Click
Finish.
SOE Example
The following section is intended to provide an example of how SOE may be used. This example
demonstrates how data monitoring is set up for recording data from an SOE module and from other data
registers in a controller. The SOE module is part of the IO configuration. Additional points are tagged for SOE
monitoring using the Event Recording Table from the Workbench.
5. Save the configuration using either File | Save or the Save icon on the toolbar.
6. Download the configuration to the controller. To download, put the IO Configurator Online (Edit |
Mode | Auto or click the green traffic light on the toolbar) and then download the configuration
(Configuration | Download Controller).
7. Exit the IO Configurator (File | Exit).
4. The tag is added with default logging attributes. To change the logging attributes, double-click on the
tag and the following dialog is displayed:
In addition to selecting the Data Type of the tag, you can pick which events are to be recorded when
the data value for the analog tag changes by more than a specified value (DeadZone), when the data
reaches a certain value (Enter Lower Limit or Enter Upper Limit), or when the data changes from a
certain value (Leave Lower Limit or Leave Upper Limit). You can also choose whether to check for
the data values at the beginning of the cycle or at the end of the cycle. In this example, event
recording is enabled for this point when the data value for the analog tag changes by more than 100.
Note: The Beginning of Cycle and End of Cycle options allow you to timestamp events more
accurately. Use Beginning of Cycle for tags that are read from IO modules or received by
communications. The timestamps occur after the data is read but before the control strategies are
run. Use End of Cycle for tags whose data is modified by the control strategies. These are
timestamps after the control strategy is run.
Notice you can still choose whether data is to be logged at the beginning or end of cycle, but you can
now set the log on transitions to ON (select only the Digital On checkbox), OFF (select only the
Digital Off checkbox), or in either direction (select both the Digital On and Digital Off checkboxes).
Click Save on either edit box to apply the edits to the appropriate list box in the main panel and
enable the master Save button. Click Cancel to discard the edit. In this example, event recording is
enabled for ADD_DONE when the point transitions in either direction and is logged at the end of the
cycle.
6. After defining one of the points for which event recording is enabled, click Save on the Build Event
Recording Points panel to save the table.
7. Right-click the controller in the Project Explorer and choose Download Control Strategies to
download the project to the controller.
2. Fill in the Server, Username, and Password fields just as you would when logging onto the
Workbench. Click Connect.
3. If this is the first time you have connected, you are prompted to create an SOE database. Answer Yes
when so prompted.
4. Once the database generation is complete, you are asked to click Connect again. The SOE
Administration Client then shows all controllers from which SOE data can be retrieved, such as
follows:
5. In the Controller Monitoring Selection, pick the controllers for which SOE data is to be recorded.
You may also change Data Storage Options and Synchronization Database details at this time.
6. Once you have finished with these items, click Save. This causes the SOE service to stop and restart.
The bottom right of the SOE Administration Client now shows that the service is running as follows:
In this example, the Primary controller (Node 012) has been selected for event recording, the
information was saved, and the service is now running without errors. You may now exit the SOE
Administration Client.
2. The SOE Data Retrieval Client appears. In this example, the Data Retrieval Client shows Module 9
as well as ADD_1 and ADD_DONE as items from which events can be retrieved, which are the items
that were set up earlier for event recording. If Module 9 is expanded, Channel 1 (Slot9_DI1_Value)
and Channel 2 (Slot9_DI2_Value) are listed as well.
Note: The items only appear in the display client if the tag/register has caused an
event to be recorded in the database.
3. At this point we are ready to set the tags for which SOE data is to be displayed. Check the box(es)
next to the appropriate tags and then click Get SOE Data to retrieve the data from the database. For
this example, we will view data for Slot9_DI1_Value, as well as ADD_1. The event data for the
requested tags is displayed. The data for our example tags is as follows:
In this example, the events are ordered by descending time. Events may be ordered by ascending
time and a start time, as well as an ending time, may be entered to limit the number of events
displayed.