116710_A.mdb
1167
System number
provided by ABB
10
File version index
This index is defined by the user, for example:
01 = 0.1 → preliminary setfile
10 = 1.0 → setfile version for commissioning
_A
Revision index
The file revision index (A, B, up to AY, AZ) should be defined
by the client engineer on site by using the HMI500 program.
.mdb
File extension
The extension .mdb, which is mandatory, is added
automatically
Remark: File version index and revision index are automatically added to the file name (see
4.1.2
Project directory structure
GUID-B616CBFE-40B7-4F81-8A2A-2986DBE85087 v1
A REB500 set file configured with the HMI500 Configurator mode has to be saved in a REB500
project structure. For ABB in-house configured systems, the following projects structure is used:
IEC18000565-IEC18000565-1-en.vsdx
IEC18000565 V1 EN-US
Figure 3:
Directory structure REB500 setfiles
1-File-configuration (draft version)
In this directory, the setfile is temporarily stored during the configuration phase. It has to be
moved to 2-File-Testing, after setfile configuration has finished.
2-File-testing (test version)
While testing/commissioning the system, the setfile is saved under this directory. After the
system tests/ commissioning have finished, the file has to be moved to 3-File definitive.
3-File-definitive
This is the place for a setfile of a REB500 in service. The directories 1-File-configuration and 2-File-
Testing should be empty now.
4-File-old-versions
If a system (setfile) is modified (re-configured), it is recommended to store the old version(s) of
the setfile under this directory. This folder contains the history of all versions, which had been
applied during the lifetime of a REB500/REB500sys system.
Section 4
1MRK 511 452-UUS Rev. A
Setfile (REB500 Configuration File)
14
Distributed busbar protection REB500
Engineering manual
© 2020 Hitachi Power Grids. All rights reserved