January 2008-01-07

How to avoid report control Revision: B

dataset overflow/duplicates in SA2007-001071
PCM 600
Instructions
Introduction

There are a couple of known issues when using the PCM 600 ver.1.5 for
application configuration of the 670 series products ver.1.1r04, related to the
impact of small changes in the application configuration on the report control
datasets.
· It was observed that small changes (like limited function blocks additions)
done in a rather large application configuration tend to generate more than
100 data points in a report control dataset. Although there’s no error message
or warning, the datapoints that are beyond no.100 are never reported.
· It was also observed that small changes (like limited function blocks
subtractions) done in a rather large application configuration tend to generate
duplicates of data points from another dataset to fill up the removed data
points in a report control dataset. These duplicates consume unnecessary
communication bandwidth.
· It was also observed that user defined datasets (not generated by the tool) are
not checked by the tool regarding number of data points. It is always up to the
communication engineer to make sure that these user defined datasets do not
exceed 100 data points.
This document describes a workaround to avoid these situations.

1. Export SCD file from the PCM 600 project. Right click on the Substation node
and select Export…, enter filename for your SCD file and save the file.

Figure1
 January 2008-01-07
How to avoid report control Revision: B
dataset overflow/duplicates in SA2007-001071
PCM 600
Instructions

Figure2
 January 2008-01-07
How to avoid report control Revision: B
dataset overflow/duplicates in SA2007-001071
PCM 600
Instructions

2. Open the SCD file in the CCT tool.

Figure3
 January 2008-01-07
How to avoid report control Revision: B
dataset overflow/duplicates in SA2007-001071
PCM 600
Instructions
3. Remove all tool generated (MeasFlt, StatNrml, StatUrg_x) report control
datasets in the IED, LD0 (see Figure 4, 5 and 6).

Figure4
 January 2008-01-07
How to avoid report control Revision: B
dataset overflow/duplicates in SA2007-001071
PCM 600
Instructions

Figure5
 January 2008-01-07
How to avoid report control Revision: B
dataset overflow/duplicates in SA2007-001071
PCM 600
Instructions

Figure6

4. Save the SCD file.

5. Import the SCD file to PCM 600 project. Right click on the Substation node and
select Import…, browse to the previously saved SCD file and select Open (see
Figure 7 and Figure 8).
 January 2008-01-07
How to avoid report control Revision: B
dataset overflow/duplicates in SA2007-001071
PCM 600
Instructions

Figure7

Figure8
 January 2008-01-07
How to avoid report control Revision: B
dataset overflow/duplicates in SA2007-001071
PCM 600
Instructions
6. Open the CAP531 tool, add or delete the desired functions in your worksheets,
compile and download to the IED.
Attention! The compilation in CAP531 is neccessary so that new report control
datasets can be created.

Figure9

7. Download SMT to IED

Figure10
 January 2008-01-07
How to avoid report control Revision: B
dataset overflow/duplicates in SA2007-001071
PCM 600
Instructions
8. Export SCD file from the PCM 600 project. Right click on the Substation node
and select Export…, enter filename for your SCD file and save the file.

Figure11

Figure12
 January 2008-01-07
How to avoid report control Revision: B
dataset overflow/duplicates in SA2007-001071
PCM 600
Instructions

9. Import SCD file to CET Communication Engineering Tool (to be used in

MicroSCADA).

Figure13

ABB AB
Substation Automation Products
SE-721 59 Västerås
Sweden
Telephone: +46 (0) 21 34 20 00
Facsimile: +46 (0) 21 14 69 18
www.abb.com/substationautomation