Rey Disp Manager User Guide
Rey Disp Manager User Guide
Protection
Devices
Reydisp Manager
Relay configuration software
Prefix
The copyright and other intellectual property rights in this document, and in any model or article produced from it (and including
any registered or unregistered design rights) are the property of Siemens Protection Devices Limited. No part of this document
shall be reproduced or modified or stored in another form, in any data retrieval system, without the permission of Siemens
Protection Devices Limited, nor shall any model or article be reproduced from this document unless Siemens Protection Devices
Limited consent.
While the information and guidance given in this document is believed to be correct, no liability shall be accepted for any loss or
damage caused by any error or omission, whether such error or omission is the result of negligence or any other cause. Any and
all such liability is disclaimed.
Revision History
Revision Date Description
1. October 29, 2010 First Issue.
2. November 2, 2010 Added chapter "Interacting With DIGSI" and chapter "Settings Editor".
3. April 13, 2011 Added the following sections:
Install System Configurator
Cut/Copy/Paste
Reload Firmware
Migrate Device
Glossary
Updated screenshots.
Updated various pages including Device Status and Synchronizing Devices.
Fixed various typos.
Reordered sections more logically.
4. May 06, 2011 Added sections: Copying Items, Reydisp Evolution and Comms Editor.
5. May 19, 2011 Re-arranged order of sections in "Importing & Exporting IEC 61850 Configuration."
Corrected screenshot in "Interacting with DIGSI" where "Export Device" was highlighted
instead of "Export ICD".
Added section "Importing & Exporting a Single Reyrolle Device".
6. July 02, 2012 Added new screenshots for Reydisp Manager v1.1.
Updated device selection screenshots/text due to application changes.
Added "Import Settings" and "Update Device from Template" chapters.
Updated "Migrate Device" due to application changes.
Updated "Installing System Configurator" with screenshots.
Added section "Adding a Legacy Device".
7. October 21, 2013 Reformatted for release with Reydisp Manager 1.20.
8. May 19, 2014 Updated for release with Reydisp Manager 1.30.
Added support for Siemens IEC 61850 System Configurator.
Added the following sections:
Converting Old Projects
System Configurator Installation to Use
Changing System Configurator Project Location
Exporting CID File
Table of Contents
1 Introduction .................................................................................................................................................................... 8
1.1 Installation ............................................................................................................................................................ 8
1.2 Install Reydisp Manager Templates....................................................................................................................... 12
1.2.1 Viewing Installed Templates............................................................................................................................. 15
1.3 Installing System Configurator ............................................................................................................................. 16
1.4 Configuration without the System Configurator ................................................................................................... 19
2 Reydisp Manager ........................................................................................................................................................... 20
2.1 Using Reydisp Manager ........................................................................................................................................ 20
2.1.1 Tree ................................................................................................................................................................. 20
2.1.2 Item Pane ........................................................................................................................................................ 21
2.1.3 Task Pane ......................................................................................................................................................... 21
2.1.4 Window Management...................................................................................................................................... 22
2.2 Reydisp Manager Projects .................................................................................................................................... 22
2.2.1 Creating a New Project .................................................................................................................................... 22
2.2.2 Opening a Project ............................................................................................................................................ 24
2.2.3 Exporting a Reydisp Manager Project ............................................................................................................... 25
2.2.4 Importing a Reydisp Manager Project ............................................................................................................... 26
2.2.5 Deleting a Reydisp Manager Project ................................................................................................................. 28
2.3 Adding Items to a Project ..................................................................................................................................... 29
2.3.1 Creating a Folder ............................................................................................................................................. 29
2.3.2 Adding a Reyrolle Device.................................................................................................................................. 32
2.3.3 Importing a Third Party ICD.............................................................................................................................. 36
2.3.4 Adding an SNTP Server .................................................................................................................................... 37
2.3.5 Adding a Station .............................................................................................................................................. 38
2.3.6 Adding a Legacy Device ................................................................................................................................... 39
2.3.7 Copying Items.................................................................................................................................................. 44
2.3.8 Cut, Copy & Paste ............................................................................................................................................ 44
2.3.9 Renaming Items ............................................................................................................................................... 45
2.3.10 Deleting Items ............................................................................................................................................. 45
2.4 Options ................................................................................................................................................................ 47
2.4.1 Store window positions on exit ........................................................................................................................ 47
2.4.2 Restore open projects on startup ..................................................................................................................... 47
2.4.3 Check for out-of-date IEC 61850 configuration when closing project ............................................................... 47
2.4.4 Automatically recompile EN100 binaries after closing System Configurator ..................................................... 47
2.4.5 Default Project Path ......................................................................................................................................... 48
2.4.6 Default Options ............................................................................................................................................... 48
2.5 Device Status ....................................................................................................................................................... 48
2.6 Properties Window ............................................................................................................................................... 49
2.6.1 Changing IED Names ....................................................................................................................................... 50
3 Reydisp Manager Tasks .................................................................................................................................................. 52
3.1 Importing & Exporting a Single Device ................................................................................................................. 52
3.1.1 Exporting a Single Device ................................................................................................................................ 52
3.1.2 Importing a Single Device ................................................................................................................................ 53
3.2 Synchronizing Devices ......................................................................................................................................... 56
3.2.1 Single Device Synchronization ......................................................................................................................... 57
3.2.2 Project Synchronization ................................................................................................................................... 57
3.2.3 Using the Synchronize Devices Window ........................................................................................................... 58
3.3 Communications Settings .................................................................................................................................... 63
3.3.1 Communication Type ....................................................................................................................................... 64
3.3.2 Serial Port Setup .............................................................................................................................................. 64
3.3.3 Ethernet Setup................................................................................................................................................. 64
3.3.4 Relay Settings .................................................................................................................................................. 65
3.3.5 Relay Password ................................................................................................................................................ 65
3.4 Configure Interface .............................................................................................................................................. 65
3.4.1 IP Address Tab.................................................................................................................................................. 65
3.4.2 Services Tab ..................................................................................................................................................... 66
3.4.3 Redundancy Tab .............................................................................................................................................. 67
3.4.4 SNTP Tab.......................................................................................................................................................... 68
3.5 Configure Time Zone ........................................................................................................................................... 68
1 Introduction
Reydisp Manager is a Windows based application which enables configuration of Reyrolle devices.
It is compatible with Microsoft Windows XP SP2 or later, Windows Vista and Windows 7.
1.1 Installation
Clicking on the setup file will install Reydisp Manager. Reydisp Manager requires that .NET 2.0 and .NET 3.5 frameworks are
installed prior to running Reydisp Manager setup.
Setup will detect if either of these are missing and will display an error message.
Note: The .NET 2.0 framework can be downloaded from the Microsoft website here:
http://www.microsoft.com/en-us/download/details.aspx?id=19
The .NET 3.5 framework can be downloaded from the Microsoft website here:
http://www.microsoft.com/en-us/download/details.aspx?id=21
Select whether to install for the current user or for all users of this computer and click Install.
Reydisp Manager installs a shortcut on the Desktop and to the Start Menu / Reydisp Manager folder.
Desktop Shortcut:
Reydisp Manager is installed and running. However, there are no Reyrolle device templates available to use.
Note: Reydisp Manager must be installed before the templates can be installed.
The templates are available by contacting Siemens Protection Devices Ltd or via the website.
Click the Finish button. The templates have now been installed.
To use the template, create a new project in Reydisp Manager and add a Reyrolle device. The list of available devices will be
displayed. Select the device to use and click Select.
See also:
2.2.1 Creating a New Project (page 22)
2.3.2 Adding a Reyrolle Device (page 32)
System Configurator is an application that configures how different IEC 61850 devices communicate with each other via GOOSE
messages. It is also used to setup IEC 61850 reports in devices. For more details, see the System Configurator user manual.
If DIGSI 4.83 or later is installed with the System Configurator option selected, the System Configurator will automatically be
made available inside Reydisp Manager. No further action is required.
Click Next.
By default, System Configurator will install to Program Files. Click Browse to change the installation directory. Click Next to
continue.
Note: Uninstalling the System Configurator will mean it is no longer available in Reydisp Manager!
The third party tool needs to be able to produce a CID or SCD file that can then be imported into Reydisp Manager.
2 Reydisp Manager
Reydisp Manager allows multiple Reyrolle devices to be configured in a single project.
It provides the following features:
A task based approach for configuring devices.
Easy synchronization of device configuration.
User configurable logic diagrams.
IEC 61850 specific configuration options
System Configurator (optional) to configure stations.
Time zone configuration.
IEC 61850 interface configuration.
Easy to use single file SCD/CID import.
2.1.1 Tree
This shows the name of the project, and the folder structure. The folder structure can be changed by dragging folders to move
them. The folder names and project name can also be renamed here. The project tree is used to organize your project into logical
folders and provides a quick way to navigate between folders.
All of the items can quickly be expanded or collapsed by clicking on the View menu.
The devices in the item pane can be viewed in one of three modes - Icons, List or Details, which can be selected by right
clicking and selecting the View from the context menu, clicking the View menu on the menu bar, or by clicking the Icons,
List and Details menu on the toolbar.
When in Details mode, there are various columns in the item pane. Clicking on a column header orders the item by that
column. Clicking on the column header again will reverse the sort order. The columns can be resized or reordered by dragging
the column headers with the mouse. The sorting can also be controlled by right clicking on the item pane and selecting the Sort
By from the context menu.
To see available tasks, select a device in the item pane. See 2.3 Adding Items to a Project (page 29) for instructions on how to do
this.
Select the Reyrolle device in the Item Pane, and a list of available actions will be displayed below in the Task Pane. The tasks
are organized into groups, such as Device Configuration, for configuring the device, and Utilities, for additional tasks.
For a list of the action performed by each task, see 3 Reydisp Manager Tasks (page 52).
Note: The file format of the Reydisp Manager Project (.rpf) file changed in Reydisp Manager 1.30. Projects created in Reydisp
Manager 1.30 and later are not compatible with versions 1.20 and earlier. However, projects created in Reydisp Manager 1.20
and earlier will be converted to the new file format when they are first opened in Reydisp Manager 1.30 or later.
Click the OK button to create the new project file and return to Reydisp Manager.
Clicking OK will convert the project to the new file format. Once the conversion is complete, the project will be opened. This
project will no longer be able to be used in Reydisp Manager 1.20 or earlier.
Clicking Cancel will cancel the conversion. The project will not be opened in Reydisp Manager and no changes will be made.
Note: Only one instance of Reydisp Manager can be opened at any one time and only one instance of each project may be
opened at any one time. Attempting to open a project that is already open in Reydisp Manager will give focus to that project
inside Reydisp Manager.
This will bring up a window where the name and location of the exported project file can be chosen.
Clicking Save will save the project with the specified file name.
Note: The project zip file exported can only be imported into Reydisp Manager 1.30 and later. The project file format is not
compatible with Reydisp Manager 1.20 and earlier.
This will bring up a window where the previously exported file can be selected.
The project consists of several files/folders. A folder must be selected where the project can be extracted to. The project file will
be extracted to the selected folder. It may be useful to click the Make New Folder button to create a new folder for the
project to be saved to.
Clicking OK will extract all of the required files/folders from the single-file project file and will open the project in Reydisp
Manager, ready to use.
To perform a delete, select the window for the project and click File Delete Project.
A confirmation dialog will appear. Clicking Yes will bring up a second confirmation dialog. Once the project is deleted, the
operation cannot be undone!
Clicking Yes will close the project and delete it from disk.
Item Description
Folder A folder used to logically organize the items in the project. Folders may be nested.
Device A Reyrolle device, selected from a list of installed device templates.
Third Party ICD File A third-party device imported from another manufacturer's ICD file.
SNTP Server A SNTP (Simple Network Time Protocol) server is a time server that other items can synchronize their
clocks with.
Station A station groups multiple IEC 61850 capable devices together into a logical group that can communicate
with each other via IEC 61850.
Legacy Device A legacy Reyrolle device that supports Reydisp Evolution.
Clicking the Add drop down button on the toolbar and selecting Folder.
Right clicking in the project window and selecting New Folder from the context menu.
The folder will be given a default name "New Folder" and will be selected to allow it to be renamed.
A folder cannot be given the same name as an existing item in the same folder. It's name must be unique.
The device selection window lists all of the installed device templates, organized by Device Family (e.g. 7SR210), Software
Version (e.g. R7c-7b) and Device Variant (e.g. 7SR2103-1[AB]A[78]7-0CA0). The full name of any template is the Device
Family\Software Version\Device MLFB (e.g. 7SR210\R7c7b\7SR2103-1AA77-0CA0).
Note: See 3.3 Communications Settings (page 63) for details on configuring the communications settings.
If a matching device template is installed for the device it will be selected, the full MLFB of the device will be populated in the
MLFB selection panel. A quick review of the MLFB documentation and clicking the Select button will add the device to Reydisp
Manager.
This is useful if a device has previously been synchronized and the user wishes to extract the configuration from the device. The
configuration can be edited just like any other Reydisp Manager device and then the changes can be synchronized with the
original device or even a new device, in the case of a replacement device or when a duplicate configuration is required.
Note: If the device was configured for IEC 61850 communication and used a station, the configuration will be downloaded and
can be synchronized to the device it was downloaded from or to another device. However, since the rest of the IEC 61850 station
configuration is not available, any changes made to the IEC 61850 configuration from Reydisp Manager will result in the IEC
61850 configuration that was downloaded being overwritten.
Tasks that will change the IEC61850 configuration when saving changes include Configure Interface and Configure
Time Zone tasks and Compile EN100 Binary.
Select the Copy from connected device checkbox. If the communication settings have not previously been set, you will be
prompted for them upon clicking Select. If the Copy from connected device checkbox is ticked, the connected device’s
configuration will be downloaded and used as the starting point for the new device.
To discover the MLFB, navigate to the SOFTWARE VERSION menu and press DOWN until the MLFB item is displayed.
To discover the Software Version, navigate to the SOFTWARE VERSION menu and press DOWN until the Product Art No item
is displayed. The software version is in the form Rxx-xx, for example R7b-7a.
If the device supports IEC 61850, the default IED name is TEMPLATE. If the device does not support IEC 61850, it does not have
an IED name.
The available tasks that can be performed on the device are listed below in the task pane.
The third party ICD file is a file that will either be produced by a third party vendor's tool, or provided directly by the third party
vendor. This ICD file should be saved to disk.
To import a third party device, click Insert Third Party ICD File. This will bring up a file dialog, where the ICD file can
be selected.
Click Open to import the third party ICD into the project. The ICD file will automatically be copied into the project directory and
added to the project. The IED name is read from the ICD file and is also used as the default name for the device.
In this example, an ICD file has been imported with an IED name of "TestIcd1", and "TestIcd1" has been used as the default item
name.
The third party device must be assigned to a station for it to be used. See 4.1 Assigning and Unsassigning Station Devices (page
108).
Note: This is useful when the device is assigned to a station. If the device is used as a standalone device, the address of an SNTP
server can be specified directly in the Configure Interface tool.
To add an SNTP server, click Insert SNTP Server. Alternatively, click the Add button on the toolbar or right click and select
Add SNTP Server.
By default, the name of this item is TEMPLATE, and the IED name is set to TEMPLATE.
See 2.3.9 Renaming Items (page 45) and 2.6.1 Changing IED Names (page 50) for details on how to change the item name or
IED name.
The SNTP server must be assigned to a station for it to be used. See 4.1 Assigning and Unsassigning Station Devices (page 108).
A new station is created and added to the project. By default, it is called "New Station".
This new station has no devices assigned to it. The next step is assigning some devices to it. See 4.1.1 Adding Devices to a
Station (page 108).
For more information about using stations, see 4 Stations (page 108).
The settings file can be in one of the following formats: .set, .SettingsTemplate, .RSF2 or .RSF3. If a settings file is not present,
but the device is connected, it is possible to create a legacy device by downloading a settings file from the device. This ensures
that the settings that are being edited match those on the device exactly.
Select From connected device then click Download Settings from Device.
This process may take a while to complete as all of the settings for each group are downloaded. Click Yes when informed that
the process may take a while.
Select the appropriate settings to communicate with the device. Click OK to begin downloading settings. This may take a minute
or so. See 3.3 Communications Settings (page 63) for more information about communication settings.
When this process completes, information about the settings is displayed, as shown in the above example. Click OK and the
legacy device will be added to the Reydisp Manager project.
Clicking Configure Communications Settings allows the default communication parameters for Reydisp Evolution to be
changed. These should be set to match the device that will be used.
Clicking on Reydisp Evolution task will launch Reydisp Evolution with the specified communication settings. After opening
Reydisp Evolution, click File Open Open... and select the settings file for the group to be edited. The settings will be
displayed in the Reydisp Evolution Settings Editor where they can be manipulated, saved, or sent to the device.
Moving Items
A project may have any number of folders. Any folder may contain any number of other folders or other items.
To move an item, hold down the left mouse button and drag it to its new location.
An item cannot be moved into a folder if there is already an item in that folder with the same name.
An item cannot be moved if any tasks are open for that item.
A folder cannot be moved or renamed if any items inside the folder have any tasks open, including all sub folders.
On releasing the mouse, the items will be copied. It is possible to copy multiple items in one operation. It is also possible to copy
folders this way - each item inside the folder will be copied recursively, including other folders.
Any new devices created by copying existing devices will not be assigned to a station, even if the original device was assigned
to a station.
Any stations created by copying an existing station will not have any devices assigned to them, even if the original station did.
If an item already exists in the destination folder with the same name as the item being copied, a confirmation prompt will be
displayed. Clicking Yes will overwrite the existing item with the new item.
It is also possible to copy items between different projects. To do this, open two projects and drag the item/items from one
project to the other. Dragging between projects always copies - it never removes the item from the original project. Again, when
copying devices, any station assignments will not be copied, and any stations will not have their device assignments copied.
Cut:
CTRL + X on the select item(s).
Right click and select Cut.
Edit Cut.
Copy:
CTRL + C on the selected item(s).
Right click and select Copy.
Edit Copy.
Paste:
CTRL + V where the item should be pasted.
Right click and select Paste.
Edit Paste.
Note:
Cutting an item will move it from its original location to the new location when it is pasted. However, If the item is cut then
pasted from another project, it will be copied, not removed, from the original project.
Any copied stations will not be assigned to any devices.
Any copied devices will not be assigned to a station.
Multiple items can be copied at a time.
Folders can be copied - everything inside the folder will be copied recursively, including other folders.
An item cannot be given the same name as another item in the same folder.
An item cannot be renamed if a task is open for that item. The task must be closed before renaming is allowed.
An item name must not be empty, or consist entirely of spaces.
A folder cannot be moved or renamed if any items inside the folder have any tasks open, including all child folders.
There is no restriction on the length of the item names, providing they observes the above rules.
A delete operation cannot be undone. For this reason, a confirmation message will appear before a deletion takes place.
Clicking Yes will remove the item from the project and from disk.
If there are any tasks that were launched from the task pane that are still active for the item, the deletion cannot be performed
and an error message will be displayed.
In this case, please close all of the tasks open for that item and try again.
Note:
Multiple items may be deleted at once.
A folder may also be deleted which will remove all of the items inside the folder too.
If a device is assigned to a station, and the station is removed, the device will no longer be assigned to a station.
If a device is assigned to a station and the device is removed, a Station Update will be required, if the System
Configurator is installed. This can be performed from the task pane and is required to update the SCD file to remove the
deleted device.
Physically deleting the folder from the disk may fail if any of the items in the folder are being accessed by other applications.
This will not affect the removal of the item from the project inside Reydisp Manager. A warning message will be displayed if the
deletion of the physical folder fails.
2.4 Options
To configure various options for Reydisp Manager, click Tools Options.
clicking the Compile EN100 Binary button on the toolbar and selecting all devices in the project or all devices associated
with the selected station (if a station is selected) from the Reydisp Manager toolbar or Project menu.
Once a station has been created using a version of System Configurator, it is not recommended to change to using an earlier
version of System Configurator.
The status of a device changes depending on the actions performed. The colour of the devices also gives quick information about
its state.
Required physical device. Perform a device synchronization to update the physical device to have the
same configuration as the device in the project. See 3.2 Synchronizing Devices (page 56).
Station Update A change has been made to a device that requires the System Configurator be run to update Blue
Required the SCD file. Clicking the Update Station task on the associated station will perform the
required update. If the System Configurator is not installed, an updated SCD reflecting the
changes made to the devices, should be reimported. See 4.4.3 Importing a Station SCD File
(page 115).
Recompile If something has changed that affects the IEC61850 configuration, the EN100 binary file Blue
EN100 Binary needs updating. This will be performed automatically when attempting to synchronize the
device. To do this manually, click the Compile EN100 Binary task.
Up to Date The device is up to date with the physical device. No further action is required. Black
Device Template The template used to create the device is not installed. This can occur if the project was Red
missing imported from another installation of Reydisp Manager that used a template that has not
been installed for this installation.
See 1.2 Install Reydisp Manager Templates (page 12) for details on how to install additional
templates.
Device Template The installed template version is older than the version of the device used in the project. A Red
Version older newer template version should be installed that matches the devices in the project.
than Device
Version
Device Template The installed template version is a newer version than the device in the project. The device in Red
Version newer the project should be upgraded to the installed template version. See 3.9 Update Device from
than Device Template (page 78).
Version
The tabs that are displayed vary depending on the item selected, but all items have the General tab. This displays information
about the physical folder, the device model (for Reyrolle devices) and the time the item was created, amongst other things.
The Author and Comment text boxes can have their contents changed. This text is displayed in the Author and Comment
columns of the Item Pane.
Type in the new IED name. If the new IED name is valid (see the above rules), clicking OK will return to the project window and
the IED name will be updated.
Select the Reyrolle device and select Export Device from the Task Pane.
Click Save to export the file to the selected location with the chosen filename. A message will be displayed to confirm the device
has been exported successfully.
To import the device, either to this project or a different project, click File Import Item.
The device has now been imported. It has been given a new name (DeviceA (1) in this case) because an item with the same
name already existed. The settings, logic and other configuration settings are copied. However, if the device that was exported
was assigned to a station, the device that has just been created following the Import Device will not be assigned to a station.
A single device may be synchronized on its own by selecting the device in the Task Pane and selecting Sync Device. The
device will be ticked, ready to sync.
Multiple devices can be synchronized simultaneously by clicking the Project Sync button on the toolbar or by clicking
Project Project Sync menu item.
If the System Configurator is installed, and any devices to be synchronized require a Station Update, a prompt will be
displayed asking if a Station Update should be performed. Clicking Yes will automatically perform a Station Update.
If there are any issues affecting devices in the project, those devices will be prevented from synchronizing until the issues are
corrected. Such issues include a mis-match of template versions, invalid IEC 61850 configuration etc.
If any IEC61850 devices that are not assigned to a station and have had changes made to their IEC61850 configuration since
their EN100 binary file was last compiled, the EN100 binary file will be recompiled automatically before displaying the
Synchronize Devices window. Any IEC61850 devices assigned to a station may need a station update to be performed
before the EN100 binary can be recompiled. A prompt will be shown, if required, to ask whether a station update should be
performed.
Once the device has finished updating any required configuration, the Synchronize Devices window is shown. The device
will be ticked by default.
Only devices that are ticked will be synchronized. Ticking a folder will tick all devices in that folder. If multiple devices have the
same communications settings, only one of them can be synchronized. For example, if two devices are set to communicate over
the USB port at the same time, it is impossible for them to both be connected at the same time, so only one device will be
allowed to synchronize; the other will be unticked and a warning message displayed.
Status Description
Device Needs Update The configuration files for this feature have been updated in the project but these changes have not yet
been sent to the device. Clicking Send Changes will send the configuration changes required for this
feature to the device.
Device Up To Date The configuration files for this feature are the same as the configuration on the device. No further
action is required.
When device synchronization is performed, the bottom pane will show a list of tasks that are being performed to synchronize the
device, along with a status bar which shows the progress of each task.
The actions Send and Check Status will be performed on all of the ticked devices. Comms Settings, Restart,
Compare/Merge Settings, Download Settings and Cancel will apply to the currently selected device.
During the initial synchronization, a reference to the project will be stored on the device. This is used to 'lock' the device to that
project, and prevent other projects from accidentally synchronizing with it and altering its configuration.
If a different project attempts to synchronize with this device via serial/USB, it will display a message box warning that the device
is assigned to a different project.
Clicking Yes will associate the device with the new project rather than the previous project.
Note: Any user files on the device will be removed when associating the device with a new project. When the device is
associated with a new project it will be synchronized to match the new project. Files left on the device from another project are
not part of this project so they are removed.
Each device can only be associated with a single project. If the previous project attempts to synchronize with this device via
serial/USB it will have to repeat the steps above to associate with the device.
Note: The device can only be associated with a new project via serial or USB. This is a security feature to prevent a device being
remotely configured over Ethernet. Once the device has been associated with the project, future communications via Ethernet is
permitted.
If No is pressed when the prompt is shown, the status of the Device Project Association task will read Device is
associated with a different project. Synchronization will not be possible if the device is assigned to another project.
3.2.3.2 Send
The Send button is split into four options – Send Changes, Send Changes without Settings, Send Entire Project
and Send Entire Project Without Settings.
The task pane at the bottom is populated with a list of tasks that are to be performed to bring the device up to date. Some of
these tasks are validation checks to ensure the files are compatible with the connected device. Each task turns green when it
completes, or red if there is an error.
Send Changes will send the settings specified in the Reydisp Manager project to the device.
Note: Any settings that have been changed outside of Reydisp Manager will be overridden.
This task will send the settings specified in the Reydisp Manager project to the device.
Note: Any settings that have been changed outside of Reydisp Manager will be overridden.
3.2.3.5 Restart
This is used to manually restart the device. Clicking Send Changes or Send Entire Project will perform a restart at the
end of sending all necessary files, if required, so this option should only be used to manually restart the device.
3.2.3.6 Cancel
This cancels the device synchronization after the current task/set of tasks has completed.
The settings from the device are shown in the left pane; the settings from Reydisp Manager in the centre pane; the final settings
that will be saved back to Reydisp Manager are shown in the right pane.
Setting differences are shown in blue or red. Blue indicates the setting is different between the device and Reydisp Manager
settings; red indicates the setting is only present on either the device or in the Reydisp Manager project but not both.
The differences in the above example have been highlighted. The setting values from Reydisp Manager for Favourite Meters
Timer and Operating Mode have been ticked so the values from the current Reydisp Manager project settings are copied to the
right pane, while the Trip Alert and Circuit Identifier settings have been left at the setting values used on the device.
Ticking the boxes in the centre pane will copy the setting values from the centre pane to the right pane. Unticking the boxes will
apply the setting values from the left pane instead. The settings in the right pane are the ones that will be saved into the Reydisp
Manager project, replacing the existing settings.
If Yes is selected, the settings file will replace the device settings in the Reydisp Manager project. Pressing No will reject all of the
changes and leave the Reydisp Manager settings unchanged. Pressing Cancel will return to the Settings Comparison form.
Note: If the setting values selected in the Reydisp Manager project and the setting values on the device are the same, the
Compare Settings form is not shown because there are no differences to show. There may still be differences in setting
values that are not selected, so the merge will automatically occur after downloading the settings.
Note: Do not attempt to overwrite an existing device settings file, Groups.rsf3. If you want to replace the existing settings inside
Reydisp Manager, try Compare/Merge settings instead.
The resulting settings file will be downloaded and saved. Once it is saved, the settings can be opened in the Settings Editor or
imported into Reydisp Manager.
See:
3.10 Import Settings (page 79)
3.14 Settings Editor (page 88)
The relay can be synchronized over the front USB port or rear communications port or Ethernet if the device supports IEC 61850
and has previously been configured via the USB or rear communications port with an IP address.
Clicking OK will close the Communication Settings window and save the settings.
Note: The first time the device is synchronized, it must be done via serial or USB. This is because the Ethernet port is not
configured with an IP address initially. Only after the device has been configured with an IP address and the device has restarted
can the device be synchronized over Ethernet by specifying the IP address.
IP Address: The IP address to use for communications. This is set by the Configure Interface or System Configurator tasks, but it
may be overridden temporarily for device synchronization to take place.
Note: The relay communication settings are visible on the relay by pressing ENTER, pressing RIGHT until SETTINGS MODE is
displayed, then pressing DOWN until COMMUNICATIONS is displayed. Press RIGHT to view the communication settings.
The relay comm port protocol must be set to IEC60870-5-103 for communications to work.
If a device is assigned to a station, then the device IP address is set by the station and the ability to configure it from the IP
Address tab is disabled to avoid conflicting IP addresses.
Interface Type: By default, all IEC 61850 Reyrolle devices are set to use IEC61850 Electrical RJ45. If a fibre optic interface
is present, this should be changed to IEC61850 Fibre. To do this, select IEC61850 Fibre from the Interface Type drop
down menu.
Operating Mode: Select between Line mode or Switch mode. Default is Line mode. (All further options are only enabled if
the operating mode is set to Switch).
Redundancy Type: When the Operating Mode is set to Switch, redundancy options are available to select. This can show RSTP,
OSM, PRP and HSR depending on the interface type.
Note: See for further information on IEC61850, PRP and HSR protocols and configuration.
3.4.3.1 RSTP
RSTP stands for Rapid Spanning Tree Protocol. This is a standard network redundancy protocol. When this option is selected, the
Advanced options are enabled. Each of the parameters is used to configure the RSTP settings to be compatible with the
switches/devices on the network. Clicking the Default button will revert parameters back to their default values. It is only
available for optical EN100 modules.
3.4.3.2 OSM
OSM is a Siemens legacy redundancy protocol. It is only available for optical EN100 modules.
3.4.3.3 PRP
PRP stands for Parallel Redundancy Protocol. It is available on both electrical (EN100+ only) and optical EN100 modules. See PRP
Mode for more information.
3.4.3.4 HSR
HSR stands for High-availability Seamless Redundancy. It is available on optical EN100 modules. See HSR Mode for more
information.
The SNTP tab allows an SNTP server to be specified for the device. Two SNTP servers can be specified, a primary and a secondary
server. If the device is assigned to a station, the SNTP servers will be visible in the SNTP tab, but will be read-only. This is because
the SNTP servers are set using the System Configurator (or the third party tool used to create the SCD file).
Clicking OK will apply the new interface settings to the device in the project.
By default, the relay is set to GMT, with no daylight saving offset specified.
Clicking OK will apply the new time zone to the device in the project.
Logical Nodes are grouped by Logical Device. A Logical Node that is checked (ticked) will be enabled; a Logical Node that is not
checked will be disabled. Clicking the OK button will save the SCL configuration for the current device. Clicking Cancel will
close the IEC 61850 SCL Configuration tool without saving any modifications.
Logical Nodes which have been disabled will not be visible in the IEC 61850 SCL tree of the device after the project has been
synchronized with the device.
To reload the firmware, the device should be connected via USB or serial. Reloading the firmware over the network is not
supported. The device selected in the project must be of the same variant as the physical device, otherwise loading the firmware
will be prevented.
Following the wizard will load the firmware and restore the device to its factory defaults.
Another use for Migrate Device is when multiple identical devices are copy/pasted, but one device needs changing to a
different variant, whilst maintaining the same (or similar) settings and logic and other configuration. It is often quicker to adapt
an existing device than to start with a new device and configure it.
For this example, a device has been created, 7SR2204-2AA77-0DA0. It will be migrated to 7SR2204-2AA11-0CA0.
Click Migrate Device from the Task Pane. The template of the current device is selected which partially fills in the MLFB.
The remainder of the MLFB should be filled in manually by either typing the correct MLFB in or selecting the options for each
character position until all characters are filled in. Only then will the Select button be made available.
Once a template or software version folder has been selected you will now need to complete the MLFB for the device.
The settings for the device will be compared to the default settings for the new variant. This will provide the opportunity for the
existing settings for the device to be copied to the new device variant.
The following steps occur when a device migrates to a new device template:
1. Migrate Logic
2. Migrate Settings
3. Migrate IEC61850 Configuration
Continue with
No
device migration.
Migration will Completed.
result in an invalid Fix logic manually
Yes
logic scheme, with Reylogic
continue anyway? Express.
Device migration
cancelled. No
No
changes will be
made
1. The logic migration was successful. The next synchronization will send the logic scheme to the device.
2. The logic migration was unsuccessful because some signals in the logic scheme that existed in the previous template do
not existing in the new template. A prompt is displayed asking whether the migration should continue.
a. Choosing to continue with the migration requires that the logic scheme is manually adjusted with Reylogic
Express before Reydisp Manager can synchronize with the device. Any signal names in the logic scheme that
have a different name in the new template will automatically be updated to use the new name.
b. Choosing not to continue with the migration results in the migration being cancelled. The device will remain
as it was before the migration and no device configuration changes will be made.
The settings are displayed in a tree. The setting name (and setting units, if the setting has any units associated with it - e.g. "min"
for minutes) and its value are displayed.
Settings that are group settings can be further expanded to show the value for each group. G1 represents Group 1 and so on:
Settings that are common have their value displayed in brackets next to the setting name:
If a setting is different between the current device and the new variant, it will be shown in blue.
If a setting is present on the current device, but not on the new variant, it will be prevented from going into the final settings file
and it will be shown in red. In the new variant settings and final settings panes it is shown with a cross icon it because the setting
does not exist in the settings for the new variant. The setting cannot be ticked because the setting is not present in the new
variant’s settings.
If a setting is present on the new variant but not on the current device, it will be shown in red and it will be used in the new
settings file with the default value. The setting cannot be ticked as it doesn’t exist in the current settings file, so there is no value
to copy.
Settings that are to be copied from the current device settings to the new variant's settings are copied by ticking the checkbox in
the centre pane. By default any settings that can be copied from the current device to the new variant are ticked if they differ to
the default settings for the new variant.
To copy the setting from the current device to the new variant, tick the box in the centre window. Ticking a parent folder will
apply all possible settings to the settings inside that folder recursively. Unticking a parent folder will untick all child items and use
the default settings.
Ensure any settings to be copied are ticked, otherwise the default values will be used. To continue with the migration, close the
Compare Settings window.
Clicking Cancel will return to the Compare Settings window. Clicking No will close the Compare Settings window and
will cancel the migration. Clicking Yes will continue with the migration.
Note: Take special care to check any differences in the INPUT CONFIG and OUTPUT CONFIG as different variants may have
different I/O configurations. For example, the initial device may have 8 LEDs and have settings set for each of the LEDs. Migrating
it to a device variant that has 16 LEDs will result in the first 8 LED settings being copied, but not the final 8 LED settings as they
don't have a matching setting in the original device, so these will be left as the default values.
Reydisp Manager attempts to maintain the selected IEC 61850 edition of the device during a migrate operation. For example, if
a device is in IEC 61850 edition 2 and the template being migrated to supports IEC 61850 edition 2, the device will remain in IEC
61850 edition 2. However, if the template being migrated to does not support the selected edition, IEC 61850 edition 1 will be
selected for the device. See 5 IEC 61850 Edition (page 134) for more information about IEC 61850 editions.
Every Reyrolle device in the project is originally created from a template. That template has a version number, e.g. 7SR220
R7a-7a R1. This version number is used to record the version of the template the device was created from.
If a newer template version is installed, the device must be updated to use the latest template before it is allowed to synchronize,
or an earlier template version installed that matches the devices in the project.
To change the device to use the latest version of the template, click Update Device from Template. This will bring up the
Compare Settings window so any differences between device settings and the default template settings for the new
template can be resolved. See 3.8 Migrate Device (page 72) for details of how to use the Compare Settings window.
When the selected settings to copy have been ticked, close the Compare Settings window and click Yes to save the settings.
Once the settings have been saved, the newer device template files will be copied to the device folder, allowing the device to
synchronize. The device has now been updated to use the newer template.
Note: The device may still be prevented from synchronizing if the installed firmware does not match the firmware included with
the template, in which case an upgrade of the firmware should be performed. See 3.6 IEC 61850 SCL Configuration
The IEC 1850 SCL Configuration tool, visible in the task pane when an IEC 61850 enabled Reyrolle device is selected, allows the
SCL tree for the device to be configured by enabling or disabling IEC 61850 Logical Nodes.
Logical Nodes are grouped by Logical Device. A Logical Node that is checked (ticked) will be enabled; a Logical Node that is not
checked will be disabled. Clicking the OK button will save the SCL configuration for the current device. Clicking Cancel will
close the IEC 61850 SCL Configuration tool without saving any modifications.
Logical Nodes which have been disabled will not be visible in the IEC 61850 SCL tree of the device after the project has been
synchronized with the device.
Reload Firmware (page 69).
Settings files from Reydisp Evolution 32 are saved with an RSF2 extension. These files contain the settings for a single settings
group. For example, Group 1 or Group 2.
The Settings Editor included with Reydisp Manager supports the newer RSF3 files which contain the settings for all groups.
For example, settings for Group 1, 2, 3, through to Group 8 for devices that provide 8 groups.
After clicking Import Settings, select an existing settings file to copy the settings from. The settings file can be the older
RSF2 file or the newer RSF3 settings file. An existing file created with Reydisp Evolution can be used, or an existing setting file
created by Reydisp Manager can also be used.
The Compare Settings window will be displayed. The current device settings are displayed on the left and the settings from
the selected file are displayed in the centre pane. The pane on the right is the list of settings that will be saved. This is a
combination of the current device settings, plus any settings to be applied from the selected file. To select a setting to copy, tick
the box. To prevent a setting from being copied, untick the box.
The differences have been highlighted in this example to show which settings will be copied from the settings file. By default, all
settings that are different are ticked, so those settings will be copied. For common settings, which are the same for all groups,
there are no sub-items. For group settings, clicking on the + sign shows the setting for each group.
When the settings are saved, the settings in the right pane will be the ones that are used. To save the setting changes to the
selected device, close the Compare Settings window and click Yes when prompted to save.
Selecting Apply settings to all groups will apply the same group specific settings to each group. Alternatively,
selecting Apply settings to a specific group allows a specific group to be selected that the RSF2 settings will be
applied to. Note that any common settings (non-group specific) will be applied to all groups irrespective of the selected option.
In the example below, a setting file has been imported that has the 81-1 Element setting set to Enabled and the 81-1
Setting set to 48Hz. When asked, Apply settings to all groups was selected, so the same setting value will be
applied to all groups.
If Apply settings to a specific group was selected instead of Apply settings to all groups with the group
set as Group 2 for example, then the remaining groups would display Disabled for each group setting for 81-1 Element
and 49.5Hz for the other 81-1 Setting. The settings for Group 2 would then be set to Enabled and 48Hz.
When the window is closed, a save confirmation is shown. Clicking Yes will save the settings, and clicking No will discard any
changes.
The EN100 binary needs recompiling whenever the station it is assigned to changes, the IED name is changed or the time zone or
interface options are modified. The status of the device in the Task Pane indicates whether the device needs recompiling. It
will automatically be recompiled prior to synchronizing, if required, but this option allows it to be manually recompiled.
A CID file can be exported from the System Configurator. See 4.4 Exporting a Device CID File (page 113) for more details about
exporting a CID file.
Assigning a station to a single device is called a "Local Station". A local station is only ever assigned to a single device therefore it
does not show up in the project as a station because its assignments cannot be changed.
Another vendor's tool is used to configure a station. The tool imports the Reyrolle device ICD and configures the station to use
the Reyrolle device. In this scenario, we need the station configuration to also be applied to the Reyrolle device in Reydisp
Manager so both the vendor's tool and Reydisp Manager are using the same device configurations to enable the devices to
communicate over the network.
1. A project is created in Reydisp Manager and a Reyrolle device is added. The ICD for this device is exported.
2. Another vendor's tool is used to configure the station (SCD file). To configure the station, the tool needs to import the
Reyrolle device before it can configure it.
3. The ICD is added to the station, and the station is configured, including IP configuration and GOOSE mappings.
4. The SCD (or CID) is exported from the vendor's tool.
5. The CID/SCD file is imported to the device in Reydisp Manager. This creates a local station using the configuration
information in the CID/SCD file. It's IP address has been set and any GOOSE messages have been setup. The device can now
by synchronized and it will be fully configured for IEC 61850 communications with the other devices in the station.
If a CID file is used, which only has a single device, the IED name of the device will be changed to match the IED name in the
CID file.
If an SCD file is used, the IED name of the device must match up with the IED name of the device in the SCD file.
If the device is already assigned to a local station, performing a CID/SCD import will replace the local station with a new local
station.
If the device is already assigned to another station, the import cannot be performed. Remove the device from the station first
and try the import again. See 4.1 Assigning and Unsassigning Station Devices (page 108 ).
Select the file to import. Use the drop down Files of type drop down list to select between CID and SCD files.
The import will automatically update the device's IEC 61850 configuration. This will take a few moments.
When this completes, the import has finished and the configuration files have been updated.
The station is not visible in the project because its device assignments cannot be changed. To view information about the
station, right click on the device and select Properties. This will bring up the properties window. Select the IEC 61850
tab.
Notice the station says Assigned to a local station instead of giving a station name.
To remove the device from this local station to allow it to be assigned to other stations, click the Remove Local Station
Assignment button.
Click Yes and then click OK to close the Properties window. The device is no longer assigned to a station.
It is launched by selecting the desired Reyrolle device and clicking Settings in the Task Pane.
Multiple logic diagrams can be created and text labels can be added to annotate diagrams to effectively organise more complex
logic schemes.
Reylogic Express is launched by selecting the desired Reyrolle device and clicking Logic in the task pane.
Reylogic Express consists of the following items, shown on the left side of the window.
Item Description
Logic Provides standard logic such as AND, OR, XOR, NOT as well as user inputs/outputs, counters and latches.
Logic Diagrams A diagram holds the user logic. A scheme can be made up of multiple diagrams.
Scheme Signals Shows a list of user outputs available in the current logic scheme from all diagrams.
Device Signals Inputs and output signals specific to the selected device.
The user manual for Reylogic Express is available by clicking Help Manual.
The Comms Editor is launched by clicking on a Reyrolle device and selecting Communications Protocol Editor from the
task pane. If the device variant does not support the Comms Editor, this option will not be visible.
Note: Not all options described in the Communications Protocol Editor are relevant when the Communications
Protocol Editor is launched from Reydisp Manager, such as saving files, sending files and retrieving files to and from the
device. This is all handled by Reydisp Manager when performing device synchronization.
To view the manual for Communications Protocol Editor, open it and click Help Help.
Note: The language file changes can be performed offline and then sent to the device on site. However, when a language file is
sent to the device an additional setting, Language Setting, is created to select between available languages. To be able to
see the Language Setting from the Setting Editor in Reydisp Manager, the language file must first be sent to the device,
and then the updated settings will automatically be downloaded into the Reydisp Manager project. Once this has been done, the
language file can be selected from the language setting in the Setting Editor.
Once the updated settings have been sent to the device, the device will switch into the specified language. The settings will
appear on the device in the new language. The settings will also automatically be downloaded into the Reydisp Manager project
and will then, and only then, be viewable in the specified user language.
Reyrolle Language Editor is launched by selecting the desired Reyrolle device and clicking Language Editor in the task
pane.
The user manual for Reyrolle Language Editor explains how to use the application in more detail. The user manual can be
accessed by clicking Help User Guide from the Language Editor main window.
Note: When launched from Reydisp Manager, certain features and menu items that are shown in the Reyrolle Language Editor
manual are not available. These additional features aren’t required when launching from Reydisp Manager because Reydisp
Manager automatically handles all the opening and saving of files. Sending language files to the device is handled as part of the
device synchronization.
Ensure the Enable User-Defined Language box is ticked on the toolbar in Reyrolle Language Editor.
When this box is ticked, the language file will be stored on the device during device sync.
If the box is unticked, the file will still be editable and will still be saved, but it will not be stored on the device.
If the language file is already present on the device, unticking this box will remove the language file next time the
device is synchronized.
The Language Name on Relay text box allows the name of the language file to be changed. This name can contain the
characters A-Z, a-z, 0-9 and spaces and can be a maximum length of 20 characters. The name entered here will be the name of
the setting visible on the device under Language Setting.
Note: If the language name is changed after the device has been synchronized using a previous language file with a different
name, the device language will revert to the default language (usually English) when the device is next synchronized. Follow the
steps below to change the settings to use the new language file name.
Change the text in Reyrolle Language Editor and close. In the basic example below, a number of settings have been
suffixed with 123 to demonstrate the process.
A save prompt will be displayed. Click Yes when asked whether the changes should be saved. The language file will now be
saved.
Note: For more information on how to use Reyrolle Language Editor, see the help manual by opening Reyrolle
Language Editor and clicking Help User Guide.
Select the SYSTEM CONFIG menu and the first setting in the SYSTEM CONFIG menu should be Language Setting. This will
be set to the default language (usually English). Change this to the new language (in the example above this was called User
Defined).
It will take a moment to send the updated settings to the device. Once the settings have been sent to the device, the device will
restart and will start up using the new language. The settings will then be downloaded from the device in the new language so
they can be viewed/edited in the Setting Editor in Reydisp Manager.
In the example below, SYSTEM CONFIG was changed to SYSTEM CONFIG123 and System Frequency was changed to
System Frequency123.
If the language file has already been stored on the device is in use, simply click Sync Device and then Send Send Changes
to Device. The updated language file will be stored on the device.
If the language file is stored on the device but the device is still using the default (English) language instead of the language file,
repeat the steps above to synchronize the device, set the language file as the active language in the Setting Editor and send
the updated settings to the device.
This will bring up the following warning dialog which warns that a language file will be removed from the device on the next
device sync:
Click OK to continue then close Reyrolle Language Editor, saving any changes.
Click Device Sync and then Send Send Changes which will remove the existing language file from the device. The device
will restart after removing the language file and will then download the updated settings. The device has been reverted to the
default language.
If any settings are set to values that have had their name changed by the Language Editor, the Compare Settings
window will be shown. Any setting names that had been changed in the Language Editor will now be reverted to their
original names. Close the Compare Settings window and click Yes to accept the changes.
To launch Reyrolle Curve Editor, click on one of the curve options (the actual curve modes available are device
dependent).
Give the curve a name. The name given here is the name that will be displayed on the device. Names must be a maximum of 20
characters, consisting of the characters A-Z, a-z, 0-9 and space. The curve cannot be given the same name as an existing curve
used on this device – although this is checked automatically when OK is clicked. Click OK to accept.
For this example, an existing template will be used rather than applying any grading or manually entering points or equations.
Click File Create Curve From...
For this example, Template ANSI Moderately Inverse is selected. Click OK.
The curve MyCurve is now visible in the list of current curves for this device.
The curve must now be stored on the device. Click Sync Device.
The item Curve Editor Current will indicate the device needs updating. Click Send Send Changes to send the changes.
After sending the curve file, the device will restart. After restarting, the updated settings from the device will be downloaded.
These settings include the new curve file, which will be selectable for the appropriate settings.
After sending a new current curve, the values available for the current IDMTL characteristic settings have changed because a new
user curve is available. The characteristic settings for all current IDMTL elements are defaulted. The same thing happens when
adding/deleting voltage curves – voltage IDMTL characteristic settings are defaulted, and when adding/deleting thermal curves
the 49 Thermal Overload Element setting will be defaulted.
In this example, the settings for 51-1 Char have been changed from the defaults for Group 1, Group 2 and Group 3 to
ANSI-MI, ANSI-VI and ANSI-EI respectively. After sending the curve file, the updated settings are downloaded. The
Compare Settings window is shown but the current IDMTL characteristic settings have been defaulted to IEC-NI. By ticking
the boxes in the centre pane, the ANSI-MI, ANSI-VI and ANSI-EI settings can be restored.
Close and accept the changes. The updated settings will be sent to the device.
Now the curve file has been stored on the device and the updated device settings have been downloaded to Reydisp Manager.
The curve can be selected in the IDMTL settings. Click Settings to open the Setting Editor.
For this example, a current curve is used, so Phase Overcurrent needs to be enabled from the FUNCTION CONFIG menu.
The CURRENT PROT’N/PHASE OVERCURRENT/51-1 Element is enabled for Group 1 and the 51-1 Char setting now has
an additional option – MyCurve – the user curve that was just sent to the device.
Select MyCurve and close the Setting Editor, clicking Yes when prompted to save changes.
Click on Sync Device again. Click Send Send Changes and the new settings will be applied, telling the device to use
MyCurve as the 51-1 curve characteristic. Once Send Changes completes, the curve is in use.
Make the required changes, close Reyrolle Curve Editor and save changes then click Exit to return to Reydisp
Manager.
Click Sync Device and then Send Send Changes. The updated curve will be stored on the device.
Click Sync Device then Send Send Changes. The curve file will be removed.
Once Send Changes has completed, the curve will be removed. The device will restart and the updated settings will be
downloaded now that the user curve isn’t selectable. The Compare Settings form will be shown.
Note: The settings available for the current IDMTL characteristic settings have changed because the current user curve is no
longer available. Therefore, the settings for all current IDMTL elements will be defaulted. The same thing happens for voltage
curves – voltage IDMTL characteristic settings are defaulted when removing a voltage user curve, and for thermal curves the 49
Thermal Overload Element will be defaulted when removing thermal use curves.
In the example below, the 51-1 Element had the 51-1 Char setting set to MyCurve for Group 1, ANSI-EI for Group 2,
ANSI-VI for Group 3 and Groups 4-8 as the default, IEC-NI. Removing MyCurve results in all of the current characteristic
settings being set to IEC-NI, the default. Ticking G2: ANSI-EI and G3: ANSI-VI will reapply those setting values.
Check the settings once the curve has been removed to confirm the settings are the desired value!
In the Compare Settings window, tick the setting values in the centre pane to apply the previously used values instead of the
defaults.
Close the Compare Settings form and click Yes to accept the changes. The settings have now been updated inside the
Reydisp Manager project.
The updated settings will be sent to the device. In the example above, this will change the setting values for 51-1 Char to
ANSI-EI for Group 1 and ANSI-VI for Group 2. The Synchronize Device window can now be closed.
To launch it, click Reydisp from the task pane. The Communications Settings that have been specified will be used to
communicate with the device.
Full details on the features Reydisp Evolution provides and how to use it can be found by opening Reydisp Evolution
and selecting Help Contents.
4 Stations
An IEC 61850 station is a substation in which all devices communicate with each other in accordance with IEC 61850.
A station may have multiple IEC 61850 capable devices connected to it.
1. Using the System Configurator. This is an optional component. If it is installed, it allows the IP address, subnet, gateway and
communication parameters of each device in the station to be defined. Additionally it allows GOOSE messages to be setup
between devices in the station and allows reports to be configured. See 4.2 System Configurator (page 110).
2. An SCD file can be created using another vendor's IEC 61850 tools, which is preconfigured with IP address, subnet, gateway
addresses etc. for each device. This can also have GOOSE messages defined in it. Importing this is read only, in that the
configuration cannot be changed by Reydisp Manager, unless the System Configurator is installed. If a change is made by
another vendor's tool, the SCD import should be run again to update the items in the project. See 3.12 Import CID/SCD
(page 83) and 4.4.3 Importing a Station SCD File (page 115).
This brings up the Properties window. Click on the Station Devices tab to view the station assignments.
All unassigned devices in the project are shown in the Unassigned Devices list. Select any devices to add to the station and
click Add to Station. The devices are added to the Assigned Devices list and will be added to the station when the OK
button is clicked.
Device assignment cannot be changed if the System Configurator is open for the station.
It is used to configure IEC 61850 stations and devices, configuring the devices on the network and adding GOOSE messages
between devices.
If the System Configurator is installed, it can be launched by selecting the station and clicking System Configurator in the
task pane or by double clicking the station.
The System Configurator displays different information depending on which view is selected. Devices View displays a list of
devices in the station. Network View displays a list of IED devices and their IP address and allows the default GOOSE MAC
address ranges to be defined. GOOSE View displays GOOSE messages and allows additional messages to be created.
Note: Not all of the features will be available in earlier versions of System Configurator.
In Devices, the devices that are associated with the station are shown. From here the CID file for each device can be exported,
see 4.4 Exporting a Device CID File (page 113). Devices can also be removed from the station here, although it is recommended
to remove the device from the station in Reydisp Manager rather than do it directly from within System Configurator.
In the Network View, the connection details, such as IP address, subnet mask, gateway and Baud rate can be set for each
device.
The Reports and Logs View allows reports to be created for datasets. This allows easy monitoring and reporting the status
of various IEC 61850 signals.
The System Configurator has its own user guide which documents how to use the System Configurator, accessed by going to
Help Help Topics in the System Configurator.
On closing the System Configurator, the configuration is updated for any devices assigned to that station.
Exporting a Station SCD
A station file (.SCD file) can be exported for use in another vendor's IEC 61850 configuration tool. Select the station to export and
click Export SCD from the task pane.
A window will pop up to select the location the file should be saved to and what it should be called.
Extension Description
ICD IEC 61850 file used for describing a device. Stands for IED (Intelligent Electronic Device) Capability Description Each
IEC 61850 capable device has a corresponding ICD file describing it.
CID This is a subset of an SCD file, which only has data concerning a single device rather than multiple devices like an
SCD file.
© 2010 – 2017 Siemens Protection Devices Limited 112
Stations
SCD A file that describes how multiple devices are configured and communicate together. This describes the IP
configuration, GOOSE messages etc. When multiple devices are assigned to a station, an SCD file is created for that
station that describes all of the devices in the station. SCD stands for Substation Configuration Description.
These tools configure the device by setting communication parameters (IP address, gateway address etc.) but cannot configure
Reyrolle devices themselves. If a Reyrolle device is exported as an ICD and imported into another tool to form part of a station,
that station file (SCD) file must be exported from the tool and imported into Reydisp Manager to fully configure the Reyrolle
device for IEC 61850 communications.
To configure a single Reyrolle device by importing an externally created SCD or CID, see 3.12 Import CID/SCD (page 83).
To configure one or more Reyrolle devices at a time by importing an externally created SCD, see 4.4.3 Importing a Station SCD
File (page 115).
Also see:
4.4.2 Importing a Device ICD (page 115)
2.3.3 Importing a Third Party ICD (page 36)
Note: If Reydisp Manager 1.30 or later and DIGSI 4.89 or later are being used together to create an IEC 61850 configuration that
contains a mixture or Reyrolle and Siprotec devices, then it is possible to link both Reydisp Manager and DIGSI 4.89 projects so
that they share the System Configurator project. This approach eliminates the need to import/export ICD and SCD files.
Right click on the device and select Export IEC 61850 device configuration
Click Station Export Export IEC 61850 device configuration
Click CTRL + G
This will bring up the Export IEC 61850 device configuration window. Select where to save the CID file and click
Save.
Also see:
A window will pop up to select the location the file should be saved to and what it should be called.
Select the required device and click Select. A save dialog will be displayed allowing the name and location of the ICD file to be
changed from the default. Click Save to export the ICD file. The ICD file will be saved with the default IED name of TEMPLATE.
An ICD file cannot be imported for a Reyrolle device. The ICD file exported for a Reyrolle device is intended to be used by a third
party tool to create an SCD or CID file.
Another vendor's tool is used to configure a station containing multiple devices. The tool imports one or more Reyrolle device ICD
files and configures the station to use the Reyrolle devices. In this scenario, we need the station configuration to also be applied
to the Reyrolle devices in Reydisp Manager so both the vendor's tool and Reydisp Manager are using the same device
configurations to enable the devices to be configured correctly to communicate over the network.
Note: Any devices assigned to the station that the import is being performed on in Reydisp Manager that are not in the SCD file
that is being imported will be unassigned from the station in Reydisp Manager.
This will bring up a file selection dialog. Select the exported SCD file.
During the import, if the System Configurator is installed, it will update the relevant files and will automatically close when
complete.
The Reyrolle device in the example already exists and is not assigned to a station. It will be assigned to the new station and
updated. The configuration is updated if required.
The third party devices are imported as third party devices and added to the station.
Right clicking on the station and selecting Properties brings up the Properties window. The Station Devices tab
shows the device assignment, which now has the third party devices added.
To configure a device for standalone access, select a device in the project and ensure it is not already assigned to a station. Select
Configure Interface from the task pane.
Configure the IP address, subnet mask and gateway to the required network settings. If you require an SNTP server to set the
device's clock, set the SNTP server IP address, Subnet Mask and Gateway in the SNTP tab. When you are finished, click OK.
Synchronize the device. The IEC 61850 configuration will be updated to incorporate the changes to the IP address. Now the
device logical node structure can be accessed over the network.
Note: If DIGSI 4.89 or later and System Configurator 5.00 or later are both installed, IEC 61850 communications between DIGSI
and Reydisp Manager devices should be done by pointing both projects at the same System Configurator project file. See 4.6.4
Changing System Configurator Project Location (page 132).
DIGSI 4.89 or later does not support importing third-party devices directly; they must be imported into the System Configurator
project instead or the same System Configurator project must be shared by both Reydisp Manager and DIGSI.
This walkthrough will use DIGSI to perform the 61850 configuration, using a mix of Siprotec and Reyrolle devices. The
configuration from DIGSI will be exported from DIGSI and imported into Reydisp Manager, showing the steps involved.
Once the devices have been added, configure the settings, logic, interface, and time zone as required before exporting the
devices.
See:
3.14 Settings Editor (page 88)
3.15 Reylogic Express (page 89)
3.4 Configure Interface (page 65)
3.5 Configure Time Zone (page 68)
Once the devices are configured, select the device and select Export ICD from the task pane.
Select where to save the file and select a suitable filename. By default, the device name is used as the file name.
Repeat this process for all devices that should be exported.
The two Reyrolle devices, R_7SR210 and R_7SR220 have been imported into DIGSI.
Select all of the devices and click Add to add them to the station.
7SR210:
Source Destination
R_7SR210/CTRL/SPo32GGIO1/Ind1 R_7SR220/CTRL/SPi64GGIO1/SPCSO1
R_7SR210/CTRL/SPo32GGIO1/Ind2 v4_7_624/CTRL/Input1GGIO1/SPCSO1
R_7SR210/CTRL/SPo32GGIO1/Ind3 v4_8_624/CTRL/Input1GGIO1/SPCSO1
v4_8_640/CTRL/Input1GGIO1/SPCSO1
7SR220:
Source Destination
R_7SR220/CTRL/SPo32GGIO1/Ind1 R_7SR10/CTRL/SPi64GGIO1/SPCSO1
R_7SR220/CTRL/SPo32GGIO1/Ind2 v4_7_624/CTRL/Input2GGIO1/SPCSO1
R_7SR220/CTRL/SPo32GGIO1/Ind3 v4_8_624/CTRL/Input2GGIO1/SPCSO1
v4_8_640/CTRL/Input2GGIO1/SPCSO1
7SJ624 v4.7:
Source Destination
v4_7_624/CTRL/O_P_1GGIO1/SPCSO1 R_7SR210/CTRL/SPi64GGIO1/SPCSO2
v4_7_624/CTRL/O_P_2GGIO1/SPCSO1 R_7SR220/CTRL/SPi64GGIO1/SPCSO2
v4_7_624/CTRL/O_P_3GGIO1/SPCSO1 v4_8_624/CTRL/Input3GGIO1/SPCSO1
v4_8_640/CTRL/Input3GGIO1/SPCSO1
7SJ624 v4.8:
Source Destination
v4_8_624/CTRL/O_P_1GGIO1/SPCSO1 R_7SR210/CTRL/SPi64GGIO1/SPCSO3
v4_8_624/CTRL/O_P_2GGIO1/SPCSO1 R_7SR220/CTRL/SPi64GGIO1/SPCSO3
v4_8_624/CTRL/O_P_3GGIO1/SPCSO1 v4_7_624/CTRL/Input3GGIO1/SPCSO1
v4_8_640/CTRL/Input4GGIO1/SPCSO1
Source Destination
v4_8_640/CTRL/O_P_1GGIO1/SPCSO1 R_7SR210/CTRL/SPi64GGIO1/SPCSO4
v4_8_640/CTRL/O_P_2GGIO1/SPCSO1 R_7SR220/CTRL/SPi64GGIO1/SPCSO4
v4_8_640/CTRL/O_P_3GGIO1/SPCSO1 v4_7_624/CTRL/Input3GGIO1/SPCSO1
v4_8_640/CTRL/Input4GGIO1/SPCSO1
Please Note:
Any changes made by the System Configurator in DIGSI will update the SCD file. This file should be exported from DIGSI and
imported into Reydisp Manager each time a change is made to ensure both DIGSI and Reydisp Manager are using the same
version of the SCD file.
If the System Configurator is opened from Reydisp Manager, any changes made affects the SCD file inside Reydisp Manager.
These changes will NOT be applied to the station inside DIGSI, only the station inside Reydisp Manager.
If a device is changed in Reydisp Manager (such as the IED name) it's ICD will need to be exported from Reydisp Manager and
the importing of the device into DIGSI repeated. The System Configurator must be run from DIGSI to update its SCD, and then
the SCD exported from DIGSI and reimported into Reydisp Manager.
Note: This approach is only suitable if using Reydisp Manager 1.30 or later and DIGSI 4.89 or later with Siemens IEC 61850
System Configurator version 5.00 or later. Previous versions do not support this work flow model and require the
importing/exporting of ICD and SCD files. See 4.3 Importing & Exporting IEC 61850 Configuration (page 112).
See Appendix A – Using a Common Station with Reydisp Manager and DIGSI (page 162) for a walkthrough on how to use this
approach.
Note: Support for IEC 61850 edition 2 stations requires System Configurator V5.01 or later.
Note: Support for IEC 61850 edition 2 Reyrolle devices requires a Reydisp Manager template with edition 2 enabled. If the
installed template does not support IEC 61850 edition 2, it may be possible to update the template to a newer version. See 1.2
Install Reydisp Manager Templates (page 12) for more information about Reydisp Manager templates.
Note: If an IED is updated to IEC 61850 edition 2 and the IED is assigned to a station in Reydisp Manager, the station will be
automatically converted to IEC 61850 edition 2 when the station is updated or opened in the System Configurator.
Note: Support for IEC 61850 edition 2 stations requires System Configurator V5.01 or later.
Note: Once an SCD has been generated for an IEC 61850 edition 2 station, it can no longer be converted back to edition 1.
6 EN100 Module
The EN100 module is used on Reyrolle devices to provide Ethernet/IEC 61850 functionality.
There are two models of EN100 module – EN100 (standard) and EN100+ (plus). Both have electrical or optical interface
arrangement.
All current devices use EN100+ and firmware 4.21 or later and offer the following functionality:
Interface Type EN100 Line Mode Switch Mode
Firmware RSTP OSM PRP HSR
Electrical RJ45 EN100+ 4.21and later
Optical EN100+ 4.21and later
Depending on the module type and firmware version installed, earlier device versions provide the following protocol options:
Interface Type EN100 Line Mode Switch Mode
Firmware RSTP OSM PRP HSR
Electrical RJ45 EN100 4.08 or earlier
Electrical RJ45 EN100 4.21 and later
Electrical RJ45 EN100+ 4.08 or earlier
Electrical RJ45 EN100+ 4.21and later
Optical EN100 4.08 or earlier
Optical EN1001 4.21 and later
Optical EN100+ 4.08 or earlier
Optical EN100+ 4.21and later
1The optical EN100 module requires firmware 4.2 and FPGA version 515 or later to support PRP/HSR. Firmware and FPGA can be
upgraded via Ethernet
EN100 and EN100+ are not interchangeable in Reyrolle devices and modules cannot be upgraded without return to the factory
for other hardware upgrades.
Siemens Scalance PRP/HSR RedBoxes have been used to test the PRP and HSR protocols.
Channel 1 is the closest to the front of the device; Channel 2 is at the back.
In line mode (the default mode) only one connection needs to be made. For redundancy protocols both ports should be
connected to allow the redundancy protocol to work.
To communicate with the device, the device needs to have an IP address set and needs to be synchronized after changing the IP
address. To do this, see 3.4 Configure Interface (page 65) for a standalone device or Stations if the device is assigned to a
station.
6.2 Homepage
The EN100 homepage provides diagnostic information, status information, error logging etc. It is accessible from a web browser
by adding /home to the web address – http://<ip address>/home
Note: For a device with an IP address of 192.168.0.1 the homepage would be http://192.168.0.1/home.
Each PRP capable device on the PRP network has two Ethernet interfaces which connect to two completely separate networks –
PRP-A and PRP-B.
Advantages:
Seamless redundancy
Two completely redundant networks
Disadvantages:
Each device must be connected to a PRP switch (resulting in more network equipment being required)
Devices without PRP support (SANs – Singularly Attached Nodes) can only connect to one side of the network without a
RedBox
To make a SANs visible from either network requires a RedBox
Both networks carry the same amount of traffic even though one network is only used if the other fails
Maximum of 512 PRP devices
HSR is generally used in a ring topology, with each device having two Ethernet ports.
Advantages:
Seamless redundancy
Simpler topology than PRP – requires no switches, therefore reduced cost
Disadvantages:
There are two fields, CorrectLanChan1/2 and WrongLanChan1/2 that display the correct and incorrect packets going
through each channel. When both ports are connected correctly, both channel 1 and 2 in CorrectLanChan1/2 will increment.
If the ports are connected the wrong way around, WrongLanChan1/2 will increment for both channels. If one channel is
connected to the wrong network but the other one is connected to the correct network, one channel will increment the
CorrectLanChan counter and one will increment the WrongLanChan counter.
This guide assumes the System Configurator is available to provide the station configuration.
The empty project has now been created and the main window is shown.
For this example, we will select 7SR220 then R7c-7b and then 7SR2204-2[AB]A[78]7-0CA0 and click Select. The device is
added to the project, and is given the variant name by default.
Select the device, right click and select Rename. Rename this to Reyrolle 7SR220 Device A.
Right click on the device and click Properties.
Rename the IED from TEMPLATE to Rey_DevA and click OK.
If the device is using a fibre optic interface rather than an electrical, select Configure Interface and set the interface type
to IEC61850 Fibre and click OK. See 3.4 Configure Interface (page 65) for further information.
Select both devices and click Add to Station then click the OK button.
Right click on Logic Diagrams and select New Diagram. A new diagram will be created named Diagram 1. Rename this
to Function Key Example.
Expand Device Signals item, then expand CONTROL and then GENERAL.
Select Function Key 1 under GENERAL.
Drag it onto the diagram with the mouse.
Repeat this and add Function Key 2.
Drag User Output 1 onto the diagram.
Drag Device Signals / CONTROL / IEC 61850 / SinglePoint Output (SPo) / SPo32GGIO1 Ind1 onto the
diagram.
Drag Logic / Set/Reset Latch onto the diagram.
Connect Function Key 1 to the Set (S) on the Set/Reset latch by dragging the mouse from the connector on the right of
Function Key 1 to the connector next to the S on the Set/Reset latch.
Connect Function Key 2 to the Reset (R) on the Set/Reset latch by dragging the mouse from the connector on the right
of Function Key 2 to the connector next to the R on the Set/Reset latch.
Connect the output from the Set/Reset latch (Q) to SPo32GGIO1 Ind1 and to User Output 1.
Note: In System Configurator 4.84 and earlier, ths GOOSE view is referred to as Link view.
Device A and Device B are now set to communicate with each other.
Close the System Configurator.
The devices have both been configured for IEC 61850 communications with each other. Both devices will be updated when
the System Configurator is closed.
Wait until both tasks have competed. Both devices have now been updated and are ready to sync.
A single device may be synchronized by selecting the device in the Task Pane and selecting Sync Device.
The first time a device is synchronized, it must be performed via the front port as the device has not yet been given an IP
address so the Ethernet port is unconfigured, and the device needs to be associated with the project.
If the device is not set to use the USB port (the port name/IP address is shown after the name – eg Reyrolle 7SR220
Device A (COM3)) then click on Comms Settings. The Communication Settings form will open.
The device must be physically connected via the USB port. Select the USB port from the drop down list for the Comm Port. In
this example it is COM3.
If the station address has been set in the Settings Editor, the value of the Station Address must be changed to match.
Press the OK button. The Communication Settings form will now close and save the communication parameters.
Tick the checkbox for Reyrolle 7SR220 Device A (COM3).
The IEC 61850 configuration, logic and settings have all been changed, so they have red icons indicating they are out of sync.
Click Send Changes to start the sync.
As each task is performed, it should turn green unless there are any problems.
When everything completes, the relay will automatically restart, if required.
It may take around 30 seconds before the Synchronize Devices window can be closed following a restart, if a restart was
performed.
Once all tasks have turned green, everything should be up to date on Device A.
Unplug the USB cable from Device A and connect it to Device B.
Untick Device A and tick Device B and repeat the same steps, setting up the Communication Settings and then click
Send Changes.
Now both devices are synchronized, pressing F1 on Device A should light LED 1 on Device A and Device B.
Pressing F2 on Device A should clear LED 1 on Device A and Device B.
8 Glossary
The following terms and abbreviations are used throughout this manual:
Abbreviation Description
CID Configured IED Description.
This is an ICD file that has been configured with for use, with additional configuration specified, such as an IP
address.
DAN Dually Attached Node. A device that is connected to two LANs in a redundant network, such as a PRP device.
Data Set A list of data objects that have been grouped together. Typically used to group commonly used data objects into
a single data set for easy retrieval.
Gateway The IP address of the network device that allows communications with another network.
GOOSE Generic Object Oriented Substation Events.
GOOSE is an IEC 61850 control mechanism for broadcasting data over Ethernet, such as status or values, which
are transmitted as data sets. A GOOSE message will be broadcast when a change of state occurs within the data
set. GOOSE messaging is designed for high speed trip signals to be transmitted with a high degree of reliability.
HSR High availability Seamless Redundancy. A type of redundancy that minimises the amount of network
connections required whilst still performing seamless redundancy switchover in the event of a failure.
ICD IED Capability Description.
This is the main file used to define each device (IED). The ICD file is written in SCL and details the logical devices
that the device exposes for IEC 61850 communications.
IEC 61850 An IEC standard for designing electrical substation automation.
IED Intelligent Electronic Device.
This represents a single device, such as a protection relay.
IED Name The name of the device that will be used to represent the device in IEC 61850 communications. By default,
unconfigured devices have the name TEMPLATE.
IP Address Internet Protocol address.
Each device on a network should be given a unique IP address to allow it to be uniquely identified.
PRP Parallel Redundancy Protocol. A type of redundancy where all switches are run in parallel – one active and one
acting as the backup.
RedBox A Redundancy Box. Used to allow Single Attached Nodes (SAN) to communicate with Dual Attached Nodes
(DAN) on a PRP/HSR network.
Report A set of data that is transmitted to a client at regular or specified time intervals, or on demand. Trigger
conditions may also generate a report - these may be pre-set or pre-defined by the client.
SAN Singularly Attached Node. A device that is connected to a single LAN, such as a PC with standard Ethernet port.
SCD Substation Configuration Description
SCL Substation Configuration Language.
This is the markup used in the SCL files such as CID, ICD and SCD files.
SNTP Simple Network Time Protocol.
A network protocol for synchronizing clocks of connected devices over a network.
Station A station is required in Reydisp Manager to allow multiple devices to communicate with each other via GOOSE
messages. Each station represents a single SCD file. Each station may have 0 or more devices assigned to it, but
each device must have a unique IED name and each device can only be assigned to a single station.
Subnet Mask An address that splits the network into logical subdivisions. The subnet mask can be used to determine which
traffic is transmitted to an external network via a gateway, and which traffic is only transmitted internally within
the local network. Gateways can connect subnetworks. The devices on a subnetwork can communicate directly
with each other without a router.
Third Party A device produced by another vendor. Only IEC 61850 third party devices are supported by Reydisp Manager,
Device and as such an ICD file is used to represent each third party device.
Creating the SCD in Reydisp Manager is the recommended approach. If the SCD has already been created in DIGSI however, it
may prove easier to link to it from Reydisp Manager.
The following steps are required. This replaces the importing and exporting of ICD and SCD files that was required previously:
3. Open System Configurator from Reydisp Manager and configure GOOSE messages (if required) and IP, subnet and
gateway addresses.
8. Double click on the station. Navigate to the Reydisp Manager station folder (the one that was just opened in Explorer).
9. Open System Configurator from DIGSI (this will add the DIGSI devices) and configure GOOSE messages (if required) and
IP, subnet and gateway addresses.
Steps 11-14 need repeating anytime a change is made to the devices in the station. This includes changing IED names, adding or
removing devices or changing the device configuration – IP address, subnet, gateway, GOOSE messages etc.
The following steps are required. This replaces the importing and exporting of ICD and SCD files that was required previously:
3. Double click on the station. Select a suitable place to store the SCD file. Take note of this location as it will be needed to
locate the System Configurator project from Reydisp Manager.
4. Open System Configurator from DIGSI (this will add the DIGSI devices) and configure the device IP address, subnet,
gateway address etc.
5. Close System Configurator.
6. Create and configure the required devices in Reydisp Manager.
7. Create a station and then assign the devices to the station.
8. Select Station Project Location in Reydisp Manager and select the KPF file. This will be in the same folder as the
SCD file that was created in DIGSI.
9. Open System Configurator from Reydisp Manager and configure GOOSE messages (if required) and IP, subnet and
gateway addresses.
10. Close System Configurator.
11. After adding/removing/changing the IED name of any devices in Reydisp Manager, perform a station update in Reydisp
Manager or open System Configurator then close it.
12. After adding/removing/changing the IED name of any devices in DIGSI, open System Configurator in DIGSI then close it.
13. Synchronize devices in Reydisp Manager.
14. Synchronize devices in DIGSI.
Steps 11-14 need repeating anytime a change is made to the devices in the station. This includes changing IED names, adding or
removing devices or changing the device configuration – IP address, subnet, gateway, GOOSE messages etc.
June 2016
www. siemens.com/energy
© 2010 – 2017 Siemens Protection Devices Limited 169