GE F650 Manual

							APPENDIX B:  B.1 PRP AND HSR ETHERNET PROTOCOLS
GEK-113000-AFF650 DIGITAL BAY CONTROLLER b-5
PRP can be enabled in configuration through a setting available on the network configuration menu (Product Setup? 
Communication Settings? Network (Ethernet), REDUNDANCY,  which already has the capability of enabling Failover 
redundancy. When REDUNDANCY is set to PRP, the ports dedicated for PRP operate in redundant mode.
The rights associated with configuring PRP follow the security requirements for network configuration.
PRP management through SNMP MIB is not supported, as F650  doesn’t currently support SNMP for configuration. Settings 
and actual values are only available through the front panel and through EnerVista.
The PRP solution to implement must ensure that performance requirements stated in IEC 61850-5 Clause 13 are still met. It 
is specified under Clause 13 (Message performance requirements) that messages of type 1A must meet the performance 
class P2/3, which is 3ms (See 3.7.1.1).
B.1.2  HSR
HSR defines a redundancy protocol for high availability in  substation automation networks, based on PRP principles, 
provides the property of zero recovery time, typically used in ring topology but applicable to any topology.
In the F650 relay, HSR is implemented in devices with comm unication option number K (for Fiber; 100 Base Fx) and M (for 
cooper; Base 100 Tx). A frame is sent over both ports. A destination should receive, in the fault-free state, two identical 
frames within a certain time skew, forward the first frame to  the application and discard the second frame when (and if) it 
comes. A sequence number is used to recognize such duplicates.
In contrast to PRP (IEC 62439-3- Clause 4), with which it shares  the operating principle, HSR nodes are arranged into a ring, 
which allows the network to operate without dedicated switches , since every node is able to forward frames from port to 
port. HSR originally meant High-availability Seamless Ring, but HSR is not limited to a simple ring topology. 
Redundant connections to other HSR rings and to PRP networks are possible. 
						

							B-6F650 DIGITAL BAY CONTROLLER GEK-113000-AF
B.2 RSTP (IEEE 802.1D-2004) AND DAISY CHAIN APPENDIX B:  
B.2  RSTP (IEEE 802.1D-2004) and daisy chain
B.2.1  RSTP description
The Rapid Spanning Tree Protocol (RTSP), like STP, was designed to avoid loops in an Ethernet network. Rapid Spanning 
Tree Protocol (RSTP) (IEEE 802.1w) is an evolution of the Span ning Tree Protocol (STP) (802.1d standard) and provides for 
faster spanning tree convergence after a topology change.
B.2.2  RSTP concepts
The IEEE 802.1d Spanning Tree Protocol  (STP) was developed to allow the construc tion of robust networks that incorporate 
redundancy while pruning the active topology of the network to  prevent loops. While STP is effective, it requires that frame 
transfer must halt after a link outage until all bridges in the network are sure to be aware of the new topology.
Using STP (IEEE 802.1d) recommended values, this period lasts 30 seconds. The Rapid Spanning Tree Protocol (IEEE 802.1w) 
is a further evolution of the 802.1d Spanning Tree Protocol.  It replaces the settling period with an active handshake 
between switches (bridges) that guarantees topology inform ation to be rapidly propagated through the network. RSTP 
converges in less than one second. RSTP also offers a number of other significant innovations. These include:
• Topology changes in STP must be passed to the root bridge  before they can be propagated to the network. Topology 
changes in RSTP can be originated from and acted upon by  any designated switch (bridge), leading to more rapid 
propagation of address information
• STP recognizes one state - blocking for ports that should not for
 ward any data or information. RSTP explicitly 
recognizes two states or blocking roles - alternate and backup port including them in computations of when to learn 
and forward and when to block 
• STP relays conf iguration messages received on the root port  g
 oing out of its designated ports. If an STP switch (bridge) 
fails to receive a message from its neighbor it cannot be su re where along the path to the root a failure occurred. RSTP 
switches (bridges) generate their own co nfiguration messages, even if they fail to receive one from the root bridge. 
This leads to quicker failure detection
• RSTP offers edge port recognition, allowing ports at the edge of the network to forward frames immediately after  acti
 vation while at the same time protecting them against loops
• An improvement in RSTP allows conf iguration messages to age 
 more quickly preventing them from “going around in 
circles” in the event of a loop RSTP has three states. They are discarding, learning and forwarding.
The discarding state is entered when the port is first taken into  service. The port does not learn addresses in this state and 
does not participate in frame transfer. The port looks for STP tra ffic in order to determine its role in the network. When it is 
determined that the port plays an active part in the network,  the state changes to learning. The learning state is entered 
when the port is preparing to play an active member of the network. The port learns addresses in this state but does not 
participate in frame transfer. In a network of RSTP switches (bri dges) the time spent in this state is usually quite short. RSTP 
switches (bridges) operating in STP compatibility mode spend be tween 6 to 40 seconds in this state. After learning the 
bridge places the port in the forwarding state. While in this state the port both learn addresses and participates in frame 
transfer while in this state. The result of these enhanced states is that the IEEE 802.1d ve rsion of spanning tree (STP) can 
take a fairly long time to resolve all the possible paths and to  select the most efficient path through the network. The IEEE 
802.1w Rapid reconfiguration of Spanning Tree significantly reduces the amount of time it takes to establish the network 
path. The result is reduced network downtime and improv ed network robustness. In addition to faster network 
reconfiguration, RSTP also implements greater ranges for port path costs to accommodate the higher connection speeds 
that are being implemented.
Proper implementations of RSTP  (by switch vendors) is designed to be co mpatible with IEEE 802.1d STP. GE recommends 
that you employ RSTP or STP in your network.  
						

							APPENDIX B:  B.2 RSTP (IEEE 802.1D-2004) AND DAISY CHAIN
GEK-113000-AFF650 DIGITAL BAY CONTROLLER b-7
B.2.3  Use in meshed networks
One great strength of RSTP is its support for all kinds of meshed topologies. The resulting flexibility regarding the 
installation is a clear advantage over th e stringent restrictions that are imposed by ring protocols such as MRP and ring 
installations. However, this flexibility harbors one great disadvantage, namely the reconfiguration time, which for an 
interconnected network depends – among other things – on the complexity of the network topology and the location in 
the network at which the failure occurred. Since RSTP is a dece ntralized protocol, it may also provoke highly unpredictable 
race conditions in the establishment of new communications paths, particularly when choosing a new root bridge. This 
gives rise to network reconfiguration times that can be estimate d only very roughly, and this does restrict the use of RSTP, 
particularly in meshed networks. In the case of meshed networks with very little complexity (such as ring networks with 
two or three additional loops or subrings), a detailed analysis can make it possible to determine upper limits, but these 
always need to be worked out individually. Unlike with the prot ocols MRP, HSR and PRP, it is not possible to make a general 
statement. 
B.2.4  Daisy chain
A daisy chain is an interconnection of devices where each device is connected in series to the next.
With an Ethernet daisy-chain redundancy selected, the F650  has two Ethernet ports and it is working as an Ethernet 
unmanaged switch. The two Ethernet ports are used for conne cting each device to the ports of its two neighboring 
devices.
Each device in the daisy chain forwards the message until it reaches the destination.
Ports A and B use the same MAC (physical device) address an d operate by chaining one device with the next one. 
Note that it is important not to create a loop in this topology. Both ends of the chain can be connected to different 
networks. The device operates only with one IP address through these 2 ports. 
						

							B-8F650 DIGITAL BAY CONTROLLER GEK-113000-AF
B.3 LINK LOSS ALERT (LLA) APPENDIX B:  
B.3  Link loss alert (LLA)
B.3.1  LLA 
(Link Loss Alert) operation: The operation of ports A and B are as follows: 
Ports A and B use port A’s MAC and IP address settings while port B is in standby mode in that it does not actively 
communicate on the Ethernet network but monitors its link. 
B.3.2  LLA priority
If this setting is set to enabled, the port A has the priority. If PORTA’s LLA detects a problem with the link, communications is 
switched to Port B. Port B is, in effect, acting as a redundant or backup link to the network for port A. 
B.3.3  LLA timeout
This setting is active only when the LLA PRIORITY is set to EN ABLED. When the link on primary port is detected again after it 
fails, there is LLA TIMEOUT (ms) monitoring time for the health  of the network. During this time, the secondary port remains 
active. If primary network is healthy for more than LLA TOIMEOUT value, the switch over to primary port is automatic.
If the setting LLA PRIORITY is enabled:
• The primary port is port A while secondary (redundant) port is port B.
• The primary port is always used if available.
• If the link on primary port is lost switch over to secondary port occurs immediately. 
• When the link on primary port is detected again, there is a monitoring timeout (LLA TIMEOUT) for the health of the 
net
 work. After that period the communication switch over to primary port automatically.
If the setting LLA PRIORITY is disabled:
• There is no priority, therefore there is no primary port . The communication switch over from one Port to the other occurs when the link fails. 
• In this case the LLA TIMEOUT setting does not act . 
						

							GEK-113000-AFF650 DIGITAL BAY CONTROLLER C-1
F650 Digital Bay Controller
Appendix C:  
GE
Grid Solutions
FACTORY DEFAULT LOGIC 
						

							C-2F650 DIGITAL BAY CONTROLLER GEK-113000-AF
  APPENDIX C:  
  
						

							APPENDIX C:   
GEK-113000-AFF650 DIGITAL BAY CONTROLLER c-3 
						

							C-4F650 DIGITAL BAY CONTROLLER GEK-113000-AF
  APPENDIX C:   
						

							APPENDIX C:   
GEK-113000-AFF650 DIGITAL BAY CONTROLLER c-5
OR3
25
OR3
26
FREQUENCY
PICK UPS
VO_054_81O_PKP
45
inOR 1
VO_055_81U_PKP
inOR 2
46
inOR 3
VO_054_81O_PKP
out OR1
47
VO_055_81U_PK P
48
inOR 1
VO_056_ALL_FREQUENCY_PKP
49
inOR 2
inOR 3
out OR1
O VERFREQ 1 PK P
111
OVERFREQ2 PKP
112
O VERFREQ 3 PK P
113
UNDERF REQ 1 PKP
114
UNDERFREQ2 PK P
115
UNDERFREQ3 PK P
116
BRO KE N
CONDUCTOROR3
273
BROKEN CONDUCT1 PK P
274
BROKEN CONDUCT2 PK P
275
BROKEN CONDUCT3 PK P
276
VO_018_BRO KE N_CONDUCTOR_PK P
277inOR1
inOR2
inOR3
outOR1
OR6
346
FWD PWR1 STG1 PKP
347
FWD PWR1 STG2 PKP
348
FWDPWR2STG1PKP
349
FWD PWR2 STG2 PKP
350
inOR 1
FWDPWR3STG1PKP
inOR 2
351
inOR 3
FWDPWR3STG2PKP
inOR 4
inOR 5
352inOR 6
VO_023_FORWARD_PO W ER_PKPout OR1
353
FORWARD
PO W ER
DIRECTIONAL PO W ERVO_025_DIRECTIONAL_PO W ER_PKP
370
DIR PWR2 STG PKP
371
DIR PW R3 STG PK P
372
OR3
373inOR1
inOR2
inOR3
outOR1
DIR PWR1 STG PKP
390
OR3
409FREQ RATE1 PKP
410
FREQ RATE2 PKP
411
FREQ RATE3 PKP
412
VO_052_81DF-DT PKP
413
OR3
414VO_052_81DF-DT PKP
415
inOR1
inOR2
inOR 1
inOR3
outOR1
inOR 2
inOR 3
out OR1
WATTIMETRIC
GROUNDFAULT
OVERCURRE NTPK P
OR3
454
OR3
455
VO_094_32N_HIGH_OC_PKP
456
VO_095_32N_LOW_OC_PKP
457
32N1 HIGH OC PKP
458
32N2 HIGH OC PKP
459
32N3 HIG H OC P KP
460
32N1 LO W OC P KP
461
32N2 LO W OC P KP
462
32N3 LO W OC P KP
463
inOR1
inOR2
inOR3
out OR1
AUX ILIARY SIGNA LS (NOT INCLUDED IN GENE RAL POW ER P KP)
inOR1
inOR2
inOR3
outOR1 
						

							C-6F650 DIGITAL BAY CONTROLLER GEK-113000-AF
  APPENDIX C: