Expert Workshop E143 Chapter 7

History

Extended Automation System 800xA

© ABB Consult IT - 1
Revision C
 History
Definitions Direct Log

1. OPC OBJECT Common information Stored on the hard disk

about the log of the Connectivity
2. TTD
Server

• Logs are circular oldest value will be overwritten of

newest
• Logs are stored in:
© ABB Consult IT - 2
Revision C
 History
Definitions Hierarchical Log

Aggregate defines the log

algorithm e.g. Time Average
© ABB Consult IT - 3
Revision C
 History
Presentation on Trend Display
In SV4 it takes 2 pixels for each log
point i. e. (1280-Frame)/2 ≈ 500 log
points
In SV5 it takes 1 pixel for each log
point → 1000 log points
All Treatments excepts
Momentary use a formula to
calculate the sample interval.
© ABB Consult IT - 4
Revision C
 History
Calculation of Sample Interval
10s in 10 Days → 86400
collected data points
Sample interval:
86400/500 ≈ 170s ≈ 3min
© ABB Consult IT - 5

3 min Time Average Value

Depending on the aggregate each point is calculated by the
Revision C

History Server from the historical data. In this case each point is
Time average value over a 3 min sample interval.
 History
Sample Interval for Time Average

”Copy / Paste”

Rows: 267
Sample Interval: 12 seconds
Scope (267 x 12) ~ 55 minutes
© ABB Consult IT - 6
Revision C
 History
Sample Interval for Momentary

Rows: 2325
Sample Interval: 1-2 seconds
Scope (2325 x 1-2) ~ 55 minutes
© ABB Consult IT - 7
Revision C
 History
© ABB Consult IT - 8
Revision C
Trend Keyboard shortcuts
 History
History Architecture
Workplace Application IM Applications
Aspect Directory Trend Display
Report
1 Hour Oil consumption in October ?
Value of 102-LC42 last week ?
720 pts Total fuel consumption each month ?

Log Config
Aspect OPC DA Handler OPC HDA Handler OPC/HDA Handler

External
History Servers
SCADA
AEH
Configuration Collector Link IM
Manager
Info about
History Server
configured logs

Tracking Updates

Configuration
Primary Log Secondary Log
Object Log
Change Manager 12 Hours 1 Week
notifications 8640 pts

Collection Manager Synchronizer

OPC Collector TTD

OPC/DA Handler
© ABB Consult IT - 9

History Service
Revision C

OnDataChange
Time stamped data from OPC DA Server
 History
Major Data Flow
Get Data
Request
Workplace Application
If no Log Exist, Trend Display
Aspect Directory History Data and
Get OPC/DA
1 Hour Subscribed Data
Data to Present
from History
a Trim Curve 720 pts
Server
Log Config
Aspect OPC DA Handler OPC HDA Handler

Get Presentation Attributes

If not specified, get them from External
the CCA History Servers
SCADA
AEH
Configuration Collector Link IM
Manager History Server
Info about
configured logs

If Log Exist

Tracking Updates Get History

Data
Configuration Log Manager
And Get Primary Log Secondary Log
Object
Change notifications
Subscribed + 12 Hours 1 Week
Data
8640 pts

Collection Manager Synchronizer

OPC Collector TTD

© ABB Consult IT - 10

OPC/DA Handler

History Service
Revision C

OnDataChange
Time stamped data from OPC DA Server
 History
Troubleshooting Log Configuration
A green indication Press the Read button
and you will get data with Data should be with quality
shows contact with Good. Data can either be
history service their quality read by the
OPC server Raw or extrapolated
© ABB Consult IT - 11
Revision C
 History
Troubleshooting Log Configuration (continued)

Number of data points

to be retrieved

Here you can set the

time scope
© ABB Consult IT - 12
Revision C
 History
© ABB Consult IT - 13
Revision C
Troubleshooting Log Configuration (continued)
 History
Reading History Data From File

Allows you to make an

offline investigation of data
© ABB Consult IT - 14
Revision C
 History
Collecting Statistics

1. Indicates the time from a request

and response from History Server.
That is how fast the disk response
for direct logs
2. The total number of logs gives an
indication how many logs need to be
synchronized
3. The disk storage invoked by history
© ABB Consult IT - 15
Revision C
 History
System Events generated by History
[Service Structure]Services:Service Event List
[Workplace Structure]Web System Workplace:System Event List

Event Suggested action

Service provider stopped Unexpected? Æ Examine cause for service stop
Service provider started History has started
Service provider reached service state History has become active (=is recording log data)
Service Provider … is Synchronized Synchronization of log data from a redundant server has completed
Error loading log I/O Error. Get details. Delete corrupt file. Restart/recreate log
Error retrieveing log configuration Get details. Examine Log Configuration. Restart/recreate log
Error retrieving data from log I/O Error. Get details. Examine Log Configuration. Restart/recreate log
OPC HDA read takes long time Triggered after 120s wait for log data Æ I/O problems (or SW deadlock)
Aspect Tracker Synchronization Lost Examine connection to Aspect Servers
Aspect Tracker In Sync History has recovered from the loss of the Aspect Directory connection
Failed to collect x logs via collector TTD Bad log* Æ Pull ListErrors or ListCollectorMap AppLog operation

Failed to collect x logs via collector OPC Bad log* Æ Pull ListErrors or ListCollectorMap AppLog operation
© ABB Consult IT - 16

*) In SV 5.0 SP1 the first 5 erroneous logs are listed in the event details.
Revision C
 History
Identifying History Files
C:\> afwuhop ssd IIT1\800xAAdmin
User IIT1\800xAAdmin added to group
Software Developers

C:\> afwuhop ssd IIT1\800xAAdmin

Removed IIT1\800xAAdmin from group
Software Developers
© ABB Consult IT - 17
Revision C
 History
OPC Collection When No Active History Client
Workplace Application
AdvHtOpcCollector
Trend Display
Application Logs
720 pts Primary Log Secondary Log
Basic and Logging 1 Week
12 Hours

8640 pts
The Basic log and the Logging OPC DA Handler OPC HDA Handler
log shows OPC Collector Events
and Data Flow
5
Open file, store data,
History Server and close file
Log Manager
4
Feed Log

1
Read Request
from Client

3
Push Data, if
data to push
Collection Manager
Synchronizer
2 PollTime
1
Flush Logs
OnDataChange
B OPC TTD Registry
CollectorPushPoints = 1200 pts
© ABB Consult IT - 18

OPC DA Handler CollectorPushPeriod = 20 min.

History Service
Revision C

A
Time stamped data
from OPC DA Server
© ABB Consult IT - 19
Revision C
History
Applog log
 History
Applog log How data is selected from 2 logs

2007-05-13 10:02:58:234, ABBIT13, AdvHtHistorySrv, PID: 2844, Thread: 2876

AdvHtHistorySrv(logs from all apartments), Server data, level = 1, Tag =
Compute log sectioning result:
Log Section:
LogId:{642A7E08-6199-4BC9-A477-2E4C58C831E1}
StartTime:05/13/07 10:01:00
EndTime:05/13/07 10:02:51
Resolution:1 Second
LogType: Direct
LogFit:0.100489
LogIndex:0
CollectorType:Internal
Log Section:
LogId:{3CBCBD99-B66D-402B-A27E-B0CE69CA904F}
StartTime:05/06/07 10:02:51
EndTime:05/13/07 10:01:00
Resolution:1 Minute
LogType: Hierarchical
© ABB Consult IT - 20

LogFit:0.129365
LogIndex:0
CollectorType:Internal
Revision C
 History
Applog log How data is selected from 2 logs

2007-05-13 10:02:58:234, ABBIT13, AdvHtHistorySrv, PID: 2844, Thread: 2876

AdvHtHistorySrv(logs from all apartments), Server data, level = 2, Tag =
CAdvHtHistoryServer::AddLogRequest():
logId = {642A7E08-6199-4BC9-A477-2E4C58C831E1}
objId = {9DDA5EF2-4C1B-4F80-BABC-077D976B85FC}
object = Utetemp:Control Module property = Out.Value
template = 1s1d
requestId = 2 mode = RR_Processed advise = 0
startTime = 05/13/07 10:01:00 endTime = 05/13/07 10:02:51
updateInterval = 0

2007-05-13 10:02:58:234, ABBIT13, AdvHtHistorySrv, PID: 2844, Thread: 2876

AdvHtHistorySrv(logs from all apartments), Server data, level = 2, Tag =
CAdvHtHistoryServer::AddLogRequest():
logId = {3CBCBD99-B66D-402B-A27E-B0CE69CA904F}
\OperateITData\History\…
objId = {9DDA5EF2-4C1B-4F80-BABC-077D976B85FC}
object = Utetemp:Control Module property = Out.Value
template = 1m3650d
requestId = 2 mode = RR_Processed advise = 0
startTime = 05/06/07 10:02:51 endTime = 05/13/07 10:01:00
updateInterval = 0
© ABB Consult IT - 21
Revision C
 History
Applog log Data raw response Before resample

2007-05-13 10:02:58:250, ABBIT13, AdvHtHistorySrv, PID: 2844, Thread: 2876

AdvHtHistorySrv(logs from all apartments), Server data, level = 2, Tag =
CAdvHtHistoryServer::DataRawResponse(): Before resample
logId = {642A7E08-6199-4BC9-A477-2E4C58C831E1}
objId = {9DDA5EF2-4C1B-4F80-BABC-077D976B85FC}
object = Utetemp:Control Module property = Out.Value
template = 1s1d
requestId = 2 mode = RR_Processed
count = 79 hr = 0
pnts[0]: time = 05/13/07 10:00:59 data = 9.17128 quality = 268435648
pnts[1]: time = 05/13/07 10:01:01 data = 9.17128 quality = 268435648
…
pnts[77]: time = 05/13/07 10:02:50 data = 9.22011 quality = 192
pnts[78]: time = 05/13/07 10:02:51 data = 9.24696 quality = 192

2007-05-13 10:02:58:609, ABBIT13, AdvHtHistorySrv, PID: 2844, Thread: 2876

AdvHtHistorySrv(logs from all apartments), Server data, level = 2, Tag =
CAdvHtHistoryServer::DataRawResponse(): Before resample
logId = {3CBCBD99-B66D-402B-A27E-B0CE69CA904F}
objId = {9DDA5EF2-4C1B-4F80-BABC-077D976B85FC}
object = Utetemp:Control Module property = Out.Value
template = 1m3650d
requestId = 2 mode = RR_Processed
count = 10080 hr = 0
pnts[0]: time = 05/06/07 10:02:00 data = 15.9451 quality = 524480
pnts[1]: time = 05/06/07 10:03:00 data = 15.92 quality = 524480
…
© ABB Consult IT - 22

pnts[10078]: time = 05/13/07 10:00:00 data = 9.17372 quality = 524480

pnts[10079]: time = 05/13/07 10:01:00 data = 9.19252 quality = 524480
Revision C
 History
Applog log Data raw response after resample
2007-05-13 10:02:58:890, ABBIT13, AdvHtHistorySrv, PID: 2844, Thread: 2876
AdvHtHistorySrv(logs from all apartments), Server data, level = 2, Tag =
CAdvHtHistoryServer::DataRawResponse(): After resample
logId = {3CBCBD99-B66D-402B-A27E-B0CE69CA904F}
objId = {9DDA5EF2-4C1B-4F80-BABC-077D976B85FC}
object = Utetemp:Control Module property = Out.Value
template = 1m3650d
requestId = 2 mode = RR_Processed
partial = 1count = 297 hr = 0
pnts[0]: time = 05/06/07 10:02:51 data = 16.4737 quality = 524480
pnts[1]: time = 05/06/07 10:36:54 data = 17.1811 quality = 524480
…
pnts[295]: time = 05/13/07 09:28:47 data = 8.94916 quality = 524480
pnts[296]: time = 05/13/07 10:02:51 data = 9.23354 quality = 16777408
© ABB Consult IT - 23
Revision C
 History
Synchronizing Logs

Workplace Application Workplace Application

Trend Display Trend Display

720 pts 720 pts

Primary Log Secondary Log Primary Log Secondary Log

12 Hours 1 Week 12 Hours 1 Week
OPC DA Handler OPC HDA Handler OPC DA Handler OPC HDA Handler
8640 pts 8640 pts

Log Manager History Server History Server Log Manager

Collection Manager Syncronizer Syncronizer Collection Manager

OPC TTD TTD OPC

OPC DA OPC DA
Handler Handler
History Service History Service

Time stamped Time stamped

© ABB Consult IT - 24

data from OPC data from OPC

DA Server DA Server
Revision C
 History
Summary of History Trend Problems

„ Log or trend configuration do not meet process

dynamics. Check Sampling intervals, Aggregate and
Treatments.
„ Data Access subscription problem. Check network, OPC
Server and MMS communication and Task offset and
load in controller.
„ Misuse of momentary treatment, time scope too long.
© ABB Consult IT - 25
Revision C
© ABB Consult IT - 26
Revision C
History
ABB Logo
Maintenenance Expert workshop

Exercise 7.1 History & Trend Examine Log Configuration

7.1.1 Description
This exercise deals with different type of Log Configurations. The student will
examine Trend and Log Configuration aspect upon different settings in the Log
configuration and Trend treatments.

7.1.2 Objectives
Upon completion of this exercise you will be able to:
• Collect data from the Log Configuration Aspect and make a proper analyze.

7.1.3 Reference documentation

• Documentation in workshop binder.
• Operator Workplace Configuration (3BSE030322)

1/4
 E143-07 Exercise 7.1 - RevC.doc

7.1.4 Exercise Steps

You will investigate how the configurations affects the trend presentation. The signals
you have changes very seldom.
1. Set no Max time on the Log Configuration aspect of objects
Persons using DCASCSx1 V1
Persons using DCASCSx2 V3
Persons using CLx: V4
2. Collect data from the Log Configuration aspect. Why don’t you get any new data
in the aspect?

3. Set treatment TimeAverage on the Trend Display of the concerning objects. You
find the trend display in the SupportSite object.
4. Operate the valve from the Graphic Display ProcessSimulation.
5. Is the opening times and close times what you expect?

2/4
Maintenenance Expert workshop

6. Change the registry key TraceKneeConstant to a value of 3. You find the key in
"HKEY_LOCAL_MACHINE /SOFTWARE / ABB / AFW /
SystemModules/HistoryServer/ Do you get any improvements?

3/4
 E143-07 Exercise 7.1 - RevC.doc

The impact of the treatment concerning the number of points is highlighted with this
exercise. You will notice the limitations of momentary values.
1. Make a Trend display for one of the objects Sig2, Sig3 or Sig4. Apply the
treatment momentary, extend the time scope to 3 days. Do you see data from the
start day of the workshop? Change the treatment to momentary extended. What
improvements do you get? What conclusions do you make using momentary?

2. Copy the data from the trend display when you are using the different treatments
“Time Average”, “Momentary” and “Extended Momentary” use Ctrl - C
and paste the result into Excel. What are the sample interval for the different
treatments?

4/4
Maintenenance Expert workshop

Exercise 7.2 Faulty history log item configuration

7.2.1 Description
This exercise covers how to find a log configuration where the Log item doesn’t exist
as a OPC property item of the object.

7.2.2 Objectives
Upon completion of this exercise you will be able to:

• Find the object with the faulty Log configuration by using the Applog viewer.

7.2.3 Reference documentation

• Documentation in workshop binder.
• Operator Workplace Configuration (3BSE030322)

1/2
 E143-07 Exercise 7.2 - RevB.doc

7.2.4 Exercise Steps

1. There are a number of faulty configured logs in the system.

2. The system produces collection message in the system event list. Imagine you
have more than 300 logs configured on a couple of them produce messages like
this. Can you find out which object causing the message from the system event
message? Can you use the log summary aspect. What does the detailed
information from System Event list reveal?

3. Start the Application Logging Tool (AfwAppLogViewer).

4. In the list of Applications, select the application AdvHtHistorySrv.

5. Select Operations, select the component AdvHtHistorySrv(collection

apartment operations) and the operation ListErrors.

6. Do you find the object with the faulty log configuration in the log? Can you also
determine in the log configuration aspect what is wrong?

2/2
Maintenenance Expert workshop

Exercise 7.3 History & Trend; Time setting changes

7.3.1 Description
This exercise deals with history & trend trouble shooting, when there has been a large
time change from future time to current time. The exercise shows the importance of
having a correct synchronized time in the system and how you can repair a log with a
faulty entry.

7.3.2 Objectives
Upon completion of this exercise you will be able to:
• Trace the interaction between a History Client and the
PPA History Server using the Application Log Protocol.

7.3.3 Reference documentation

• Documentation in workshop binder.
• Operator Workplace Configuration (3BSE030322)

1/2
 E143-07 Exercise 7.3 - RevB.doc

7.3.4 Exercise Steps

You get to a site where the time has been adjusted wrongly by mistake. The trend
curve doesn’t shows any new values.
1. Change the time in the system to a future time at least 4 hours in the future.

2. Let the log for object Sig2, Sig3 and Sig 4 produce values for a couple of minutes.

3. Change the time back to the correct time.

4. Check the log configuration and the trend curve. Do you get any values?

5. Export the log as a CSV file.

6. Now your task is to repair the log by removing the values for the future times. The
only way to get rid of the “bad” data is to delete the log files. Find the files by
searching on the identity in log configuration aspect. You need to be software
developer.

7. Import the file CSV file but include only the data where the time is not in the
future.

8. Call up the Trend Display aspect

2/2
Maintenenance Expert workshop

Exercise 7.4 History & Trend Log Manager Interaction

7.4.1 Description
This exercise covers how to trace the Synchronizer - History Server interaction when
synchronizing parallel PPA History Logs

7.4.2 Objectives
Upon completion of this exercise you will be able to:

• Trace the Synchronizer requests and the History Server responses when
synchronizing parallel PPA History Logs

7.4.3 Reference documentation

• Documentation in workshop binder.
• Operator Workplace Configuration (3BSE030322)

1/2
 E143-07 Exercise 7.4 - RevB.doc

7.4.4 Exercise Steps

1. Close all Trend Displays

2. Start the AdvHtHistorySrv(logs from all apartments), Server data log on the
History Server. Set the log level on 1.

3. Via the Service Provider Definition Aspect, stop History Service Provider 2.
Note the ClientGone message in the Server Data log.

4. Collapse in wait a couple of minutes so that the History Server that is down
looses some updates.

5. Start History Server 2 via the Service Provider Definition Aspect.

Wait until the Service Provider enters the Service state.

6. In the Server Data log, explore the Synchronizer requests and the History Server
responses when synchronizing the logs.

7. The Basic History metrics shows also how well the service providers are
synchronized.

2/2
Maintenenance Expert workshop

Exercise 7.5 History & Trend Log Recovery

7.5.1 Description
This exercise covers how restore a specific log from a backup of external services.

7.5.2 Objectives
Upon completion of this exercise you will be able to:

• Restore a specific log from a backup.

• Identify to log file from the GUID identifier.

7.5.3 Reference documentation

• Documentation in workshop binder.
• Operator Workplace Configuration (3BSE030322)

1/2
 E143-07 Exercise 7.5 - RevA.docA

7.5.4 Exercise Steps

1. Make a scheduled backup of External Services.

2. Find the Log file of objects Sig2, Sig3, and Sig4. You need to belong to the
Software developers group to get the GUID of the log file. Each person in the
group can make a restore of one log. Make an individual agreement.

3. Stop both Service Provider for Basic History.

4. Delete the log file.

5. Wait a couple minute, now you just get values from the last minutes.

6. Restore the log from the backup.

7. Check that you get log data which prior to the time after deleting the log files.

2/2