GOOSE Messaging Over LTE Network

- 1 -

GOOSE messaging over LTE network

GOOSE messaging over LTE network

Revision History

Abstract

This reportdescribes the test setup and results of GOOSE messaging over 4G / LTE mobile network.

Contents

Revision History

Abstract

1Preface

2Scope & introduction

3Horizontal GOOSE communication

3.1Analyzing the event list:

3.2How to change the value of the event list capacity?

1Preface

This report was done as a part of the Finnish national research project "Smart Grid and Energy Market" SGEM.

It was funded by Tekes – the Finnish Funding Agency for Technology and Innovation and the project partners.

2Scope & introduction

This report describes the test setup and results of GOOSE messaging over 4G / LTE mobile network. The testing was done in a laboratory environment at Nokia Siemens Networks, Espoo Säterinportti and the relays, station computer and the GOOSE test setup was provided by ABB.

Persons involved with the testing were Janne Starck (ABB), Timo Knuutila, Petteri Siren (NSN).

3Horizontal GOOSE communication

Our test setup is shown in Figure 1. The object was to measure the delay of GOOSE messages which travel from Intelligence Electronic Device (IED) REF615 A to another IED REF615 B. Both of the IEDs were supposed to use timestamps for messages sent. COM600 collected these GOOSE messages sent by IEDs, REF615 A and B.

Figure 1 Horizontal GOOSE communication, original configuration.

However, due to the processing time of COM600 the delay times varied a lot, depending on the event list capacity size of COM600, which we changed during our experiences due to the lack of events in the log at the beginning. After more measurements we noticed that due to other application running at COM600 delays between messages were not constant when having the same event list capacity. In addition of these not constant delays the event list notifies that the messages from BAY_10 (left router) had quality flag “BadTime.” Bad Time appeared because the GPS time source was only connected to REF615 B (BAY_12).

We tried to change the configuration the way that we could connect the GPS time source to both of the IEDs by adding a switch to the configuration and separating IEDs to different subnetworks. This operation was not possible at first because of the old IP addresses configured to COM600. We needed to change the IP addresses of the relays and update these new IP-addresses to COM600 using ABB’s Session Automation Builder (SAB) program and install this new configuration setup file to COM600. Some Event list logs are shown in tables 1-3. IP-addresses of the relays were changed in configuration menu. The relays had to be restarted before the new IP-addresses were in use.

In figure 2 the new configuration is shown. Now there are three different subnetworks. The first subnetwork 10.0.0.0/24 includes GPS time source and one port of the router C. The second subnetwork 10.1.0.0/24 includes IED relay REF 615 A and one port of router C. The third subnetwork 10.2.0.0/24 includes COM600, IED relay REF615 B and one port of router C. The default gateway of the hardwares is 10.x.0.1. With this configuration we were able to share the GPS time signal to both relays, resulting the absence of “BadTime”- flag. The event list log after the successful configuration is shown in table 4 and 5.

Figure 2 Second configuration with three different subnetworks

In figure 3 there is a screenshot taken from router B. The traffic in LTE modem and traffic in the tunnel between IEDs are shown.

Figure 3 Screenshot from router B

3.1Analyzing the event list:

In table 1 we can see that the delay between “Programmable LED 1”- messages is only < 20 ms.

Table 1 Event list (capacity 1000 events)

In table 2 the delay between “Programmable LED 1”- messages is ~70-80 ms during the whole 5000 events.

Table 2 Event list (capacity 5000 events)

In the table 3 we can see that the order of messages is different than in the previous tables. This might be because of the processing delay of COM600 due to running team viewer application in the same relay. Time difference between Programmable LED 1 messages is about 60 ms.

Table 3 Event list

In table 4 there is a log file after the successful configuration. Now there are no BadTime- flags in the Quality- column. The average delay for 1666 message pairs was 0.024 sec.

Table 4 Event list without "BadTime"

In the table 5 there is another event log. This time all the other programs, including team viewer were shut off. The average delay between 1666 Programmable LED 1 messages was 0.035 seconds.

Table 5 Event log without any other program on

In table 6 some ping statistics taken from ?. Minimum round trip time (rtt) has been almost the same in all of the cases contrary to a maximum round trip time which varies a lot. However the average rtt does not vary more than one millisecond from other each other.

Table 6 Ping statistics

Figure 4 Chart from table 6

3.2How to change the value of the event list capacity?

First install Station Automation Builder 600 (SAB600). Then install REF615 Connectivity Package 3.0.x

Open SAB600 and load the SGEM_GOOSE_Test- project. Click Gateway 3.4x.

Figure 5 Screenshot taken from SAB600

Now you see the Basic values in Object Properties (Event list capacity = 2000 in the figure below). The IP addresses of the IED relays can be changed under the IEC61850 OPC Server- menu.

Now, connect your pc to the COM600. Change the IP value in SAB (Remoting IP Address 10.0.0.1) to be the same as Local Area Connection of COM600 has. (or the other way around)

Then, right click the Gateway 3.4x field and press Management. Now you can save the new file to COM600 and after that the new event list capacity value is in use.

All of the softwares needed are installed to SGC-PC1.

Figure 6 Screenshot taken from SAB600

CLEEN OY Eteläranta 10, P.O. BOX 10, FI-00131 HELSINKI, FINLAND