SYNC 2000, 3000, 4000 Series

Software User Manual

www.kalkitech.com

Version 4.5, Dec 2015

SYNC 2000, 3000, 4000 Series Software User Manual 1

 Copyright Notice

© 2013 Kalki Communication Technologies Pvt. Ltd. All rights reserved.

This user manual is a publication of Kalki Communication Technologies Pvt. Ltd. and is provided for
use to its customers only. Content of the manual is copyrighted and reproduction in whole or in part, for
use other than in support of Kalkitech equipment, is prohibited without the specific written permission of
Kalkitech.

Disclaimer
Information in this document is subject to change without notice.
Information provided in this manual is intended to be accurate and reliable. However, Kalki
Communication Technologies assumes no responsibility for its use. Kalki Communication Technologies
makes no commitment to update or keep current the information contained in this manual.

Contact Information

Kalki Communication Technologies Private Limited

#147, 5th Main Road, HSR Layout Sector 7,
Bangalore 560102, India.
Phone: +91-80-40527900

Technical Support Contact Information

Online Technical Enquiry Support: www.kalkitech.com/support

E-mail Support: [email protected]

SYNC 2000, 3000, 4000 Series Software User Manual 2

About the Document
Purpose
This user manual serves as a guide for using SYNC gateway/ data concentrator/ front end processor
models - SYNC 2000, SYNC 3000 and SYNC 4000 series. This user manual describes the
configuration details of the SYNC devices. It also contains installation and configuration details for Easy
Connect, the configuration utility provided to configure the SYNC models. This is a comprehensive
guide providing details about all software support features including redundancy, NERC-CIP and
VPN. Please note that separate user manuals are available for each protocol which explain the
configuration and mapping in detail.

Intended Audience
This user manual is intended for the SYNC Data Concentrators, Protocol Gateways, Terminal
server users and:
• Introduces the user to SYNC and EasyConnect
• Explains the user interface
• Provides step-by-step instructions to install and get started with SYNC and EasyConnect
• Provides step-by-step instructions to configure and map protocols present inside the
SYNC devices and EasyConnect

SYNC 2000, 3000, 4000 Series Software User Manual 3

Table of Contents
1 Overview of SYNC 2000/3000/4000 13
1.1 EasyConnect  13
1.2 Environment 14
1.2.1 Software Requirements 14
1.2.2 Hardware Requirements 14
2 Getting Started 15
2.1 Installing EasyConnect 15
2.2 Removing EasyConnect 15
2.3 Starting EasyConnect 15
2.4 Exiting EasyConnect 16
2.5 Using the EasyConnect Interface 16
2.5.1 Menu 17
2.5.2 Toolbar  20
2.5.3 Workspace  20
3 Download 21
4 Apply Configuration 26
5 Upload 30
6 Restart Device 34
7 Stop Firmware 37
8 Start Firmware 39
9 Scan for connected Devices 41
10 Version Information 42
11 Time Settings 46
12 Update Firmware 54
13 Traffic/Diagnostics Monitor 56
14 User Management 57
14.1 User Authentication 57
14.2 Configuring Users and Roles 57
15 Audit Trail 60
16 Configure SMS 62
16.1 SMS Port Settings 62
16.2 SMS Settings for SYNC Device 63
17 Set Language 69
18 DB Delete 70
19 Gateway Log 73
20 API Configuration 79
21 Configuring Gateways 84
21.1 Add Master Channel 85
21.2 Add Slave Channel and Node 91
21.3 Master to slave Mapping 92
21.3.1 Auto Mapping – Master to Slave 93
21.3.2 Auto Map Window 95

SYNC 2000, 3000, 4000 Series Software User Manual 4

 21.4 Slave to Slave Mapping 97
21.5 Ease of Configuration 98
21.5.1 Copy/Paste 98
21.5.2 Profile Row Options 99
21.5.3 Multiple Row Modify Option 99
21.5.4 Search Option in profile and mapping 100
21.5.5 Excel Import/Export 101
22 Configuring Dialup  103
23 Configuring VPN  108
24 SNMP Configuration 117
25 Configuration File Management  118
25.1 Downloading configuration to device 118
25.2 Saving Configuration File 119
25.3 File Revision 121
25.3.1 Save to Revision 121
25.3.2 Load from Revision 122
26 Network Configuration 123
26.1 Setting device IP 123
26.2 Ethernet redundancy 123
26.3 Configuring Redundant Interfaces  126
26.4 NAT Policy Settings 127
26.4.1 To add NAT Rules 128
26.4.2 To edit NAT Rules 130
26.4.3 To delete a NAT Rule 130
26.4.4 To delete NAT Policy Settings 131
26.5 Routing Configuration 131
26.6 Ethernet Packet Capture 134
27 Redundancy Configuration 136
27.1 Introduction 136
27.2 Types of Switchover 136
27.2.1 External Trigger Switchover 136
27.2.2 Self Switchover 137
27.3 IP Switching mechanisms 137
27.3.1 IP Swapping 137
27.3.2 No IP Switching 138
27.4 Redundancy Requirements 138
27.5 Device Redundancy Information and Control 139
27.6 Hot-Standby protocol 139
27.6.1 Configuration of Hot-Standby 139
27.6.2 Channel Configuration 140
27.6.3 Node Configuration 142
27.6.4 Redundancy Switchover Details 147
27.6.5 HSB Configuration Easiness 147
28 NERC-CIP Support  148
29 File Transfer Support 150
29.1 Configuring File Transfer Client Channel 150
29.2 Configuring File Transfer Server Channel 151

SYNC 2000, 3000, 4000 Series Software User Manual 5

30 Parameterization through Pass-Through
(Transparent) Channel 153
31 Encryption Support 154
32 Data Monitoring 159
32.1 SYNC DB Monitor- Menu Items  160
32.1.1 View 160
32.1.2 Option 160
32.2 Function Keys 161
32.2.1 Start 161
32.2.2 Stop 161
32.2.3 Refresh 161
32.3 Supported Features 161
32.3.1 Channel Filtering 161
32.3.2 Data Type Filtering 161
32.3.3 Status Monitor 162
32.3.4 Alarm Window 162
32.3.5 Watch Window 162
32.3.6 Adding More Columns of Details 163
32.3.7 Quick Filter 163
33 Variables 164
33.1 Logic Variables 164
33.2 System Variables 165
33.3 Special Functions 169
34 IEC 61131 Logic engine 170
34.1 Exporting Logic Engine Variable List 171
35 Web HMI Support 172
36 Time Synchronization  173
36.1 IRIG Standard 173
36.2 IEEE 1588 Standard 173
36.3 Configuring Time Synchronization  174
36.3.1 Device Parameters 174
37 DCCP Packaging 177
Appendix A - Special Case: IEC 61850 Server and 181
ICCP Peer 181
Appendix B – SYNC Devices  182
Appendix C – Flag conversion in SYNC 183
Appendix D – HSR/PRP/IEEE1588 Interoperability  184
Appendix E – PRP implementations 186
Glossary 187

SYNC 2000, 3000, 4000 Series Software User Manual 6

List of Figures
Figure 1: EasyConnect User Interface 16
Figure 2: User Interface 16
Figure 3: File Menu 17
Figure 4: View Menu 17
Figure 5: Configuration Menu 18
Figure 6: Settings Menu 18
Figure 7: Diagnostic Menu 19
Figure 8: Tool Menu 19
Figure 9: Help Menu 20
Figure 10: Toolbar 20
Figure 11: Download 21
Figure 12: Download: For a device outside the project context 22
Figure 13: Download: For a device in a project context 22
Figure 14: Download: For a device in a project context 23
Figure 15: Download: Pop Up window 23
Figure 16: Downloading various files to multiple devices 24
Figure 17: Downloading various files to multiple devices – Pop UP Window 25
Figure 18: Apply Configuration 26
Figure 19: Apply Configuration: For a device outside the project context 27
Figure 20: Apply Configuration: For a device in a project context 27
Figure 21: Apply Configuration: For apply configuration to multiple devices 28
Figure 22: Apply Configuration: Pop UP Window 29
Figure 23: Upload 30
Figure 24: Upload Options 31
Figure 25: Add a new device to an existing project 31
Figure 26: Update a device in an existing project 32
Figure 27: Update a device in an existing project 32
Figure 28: Update a device - Pop up window 33
Figure 29: Upload configuration to a particular folder 33
Figure 30: Restart 34
Figure 31: Restart Device - For a device outside the project context 34
Figure 32: Restart Device - For a device in a project context: 35
Figure 33: Restart Multiple Devices 35
Figure 34: Restart Multiple Devices – Pop Up 36
Figure 35: Stop Firmware: For a device outside the project context 37
Figure 36: Stop Firmware: For a device in a project context 38
Figure 37: Start Firmware 39
Figure 38: Start Firmware: For a device outside the project context 39
Figure 39: Start Firmware: For a device in a project context 40
Figure 40: Download 40
Figure 41: Scan 41
Figure 42: Scan Window 41
Figure 43: Version Information 42
Figure 44: Version Information: For a device outside the project context 43
Figure 45: Version Information: For a device in a project context 44
Figure 46: Save Version Information 45
Figure 47: Get Time: For a device outside the project context 46
Figure 48: Get Time: For a device in the project context 47
Figure 49: Set Timezone: For a device outside the project context 48
Figure 50: Set Timezone: For a device in the project context 49

SYNC 2000, 3000, 4000 Series Software User Manual 7

Figure 51: Set System Time: For a device outside the project context 50
Figure 52: Set System Time: For a device in the project context 51
Figure 53: Set Manual Time: For a device outside the project context 52
Figure 54: Set Manual Time: For a device in the project context 53
Figure 55: Update: For a device outside the project context 54
Figure 56: Update: For a device in a project context 55
Figure 57: Traffic/Diagnostics Monitor 56
Figure 58: EasyConnect Login 57
Figure 59: User Management 58
Figure 60: Adding a Role 58
Figure 61: Adding a User 59
Figure 62: Audit Trail 60
Figure 63: EasyConnect Log 60
Figure 64: Advanced Filter 61
Figure 65: Select SMS Port Settings. 62
Figure 66: Test SMS Port Settings 63
Figure 67: Add SMS Settings 63
Figure 68: SMS Settings Download 65
Figure 69: Send SMS 66
Figure 70: Send SMS Window 66
Figure 71: Change Admin 67
Figure 72: Change Admin Window 68
Figure 73: Delete SMS Details 68
Figure 74: Set Language 69
Figure 75: DB Delete: For a device outside the project context 70
Figure 76: DB Delete: For a device in the project context 71
Figure 77: Deleting Database File in multiple devices 71
Figure 78: DB Delete window 72
Figure 79: Gateway Log 73
Figure 80: Gateway Access Log: For a device outside the project context 74
Figure 81: Gateway Access Log: For a device in the project context 75
Figure 82: Application Logs: For a device outside the project context 76
Figure 83: Application Logs: For a device in the project context 77
Figure 84: Internal Log 78
Figure 85: SYNC API: API Configuration 79
Figure 86: SYNC API: Add New Protocol 79
Figure 87: SYNC API: Add new parameter 80
Figure 88: SYNC API: Configure parameter 80
Figure 89: SYNC API : Add Value Range 81
Figure 90: SYNC API: Node Parameters 81
Figure 91: SYNC API: Data Profile Parameters 82
Figure 92: SYNC API: Add Firmware Details 82
Figure 93: SYNC API: Save Changes, Warning Message 83
Figure 94: SYNC API: Protocol Configuration Window 83
Figure 95: Add Device  85
Figure 96: Modify Device 85
Figure 97: Delete device  86
Figure 98: Add Master Protocol 86
Figure 99: Delete Channel  87
Figure 100: Add Station 87
Figure 101: Delete Station  88
Figure 102: Add Profile 88

SYNC 2000, 3000, 4000 Series Software User Manual 8

Figure 103: Export Profile 89
Figure 104: Import Profile  89
Figure 105: Delete Profile 90
Figure 106: Add Row 90
Figure 107: Modify Row  91
Figure 108: Delete Row 91
Figure 109: Add Map 92
Figure 110: Modify Map 92
Figure 111: Delete Map  93
Figure 112: Auto Map Entire Profile Points 94
Figure 113: Auto Map Selected Profile Points  94
Figure 114: Auto Map Window 95
Figure 115: Adding Slave Profile 97
Figure 116: Copy/Paste option on Right Click 98
Figure 117: Multiple Copies Form  98
Figure 118: Profile Row Option 99
Figure 119: Multiple Row Modify Window 99
Figure 120: Search Option in Profile and Mapping 100
Figure 121: Earch Option in Profile Rows. 100
Figure 122: Search Option in Mapping 100
Figure 123: Excel Export and Import  101
Figure 124: Excel Profile 101
Figure 125: Excel Import Popup 102
Figure 126: Add Dialup  103
Figure 127: Add Dialup Window 104
Figure 128: Download  106
Figure 129: Delete Dialup 106
Figure 130: Delete Dialup  107
Figure 131: VPN/ GPRS Network With SYNC Devices  108
Figure 132: Add VPN  109
Figure 133: VPN Pop-Up 110
Figure 134: VPN parameters 111
Figure 135: Download VPN 112
Figure 136: Edit VPN  112
Figure 137: Edit VPN Pop-up 113
Figure 138: Delete VPN  113
Figure 139: Delete VPN 114
Figure 140: Export VPN Certificates 115
Figure 141: VPN Diagnostics 115
Figure 142: Import VPN Certificates 116
Figure 143: Import VPN Certificate File Selection Window 116
Figure 144: Download Configuration File 118
Figure 145: Export XML file 119
Figure 146: Import XML file 120
Figure 147: Save to Revision 121
Figure 148: Revision Name 121
Figure 149: Load from Revision 122
Figure 150: Revision List 122
Figure 151: IP configuration 123
Figure 152a: Network Bonding 124
Figure 116b: PRP network 125
Figure 116c: HSR network 125

SYNC 2000, 3000, 4000 Series Software User Manual 9

Figure 153: IP configuration Window 126
Figure 154: Redundancy Configuration 126
Figure 155: Add NAT Policies 127
Figure 156: Add NAT Rule 128
Figure 157: Add NAT Rule pop-up  128
Figure 158: Download NAT settings  129
Figure 159: Edit NAT rules 130
Figure 160: Delete NAT rules  130
Figure 161: Delete NAT policy settings 131
Figure 162: Route Configuration Menu 132
Figure 163: Retrieve Route Configuration 132
Figure 164: Route Table 132
Figure 165: Add Route 133
Figure 166: Modify Route 133
Figure 167: Delete Route 134
Figure 168: Ethernet Packet Capture Menu of Configured Device 134
Figure 169: Ethernet Packet Capture For Non configured Device 135
Figure 170: Switchover Due To External Trigger 136
Figure 171: Self Switchover 137
Figure 172: Redundant Configuration with IP Swapping 138
Figure 173: Redundant Configuration with No IP Switching 138
Figure 174: Channel Configuration for Achieving Redundancy 140
Figure 175: General Node Configuration for HSB 142
Figure 176: IP Switching Configuration for HSB 144
Figure 177: Configure Individual Interface for IP Switching 144
Figure 178: HSB Configuration Easiness Change in download window. 147
Figure 179: Login page 148
Figure 180: Home page 149
Figure 181: Add Schedule 150
Figure 182: Add Transfer Task 151
Figure 183: Add User 151
Figure 184: Add Schedule 152
Figure 185: Add Folder 152
Figure 186: Parameterization through Transparent Channel 153
Figure 187: Enabling Encryption in TCP Channels 154
Figure 188: Certificates Window 155
Figure 189: Import Window 156
Figure 190: Generate Certificates 157
Figure 191: Download TLS Settings 158
Figure 192: Enabling SYNC DB Monitor 159
Figure 193: SYNC DB Monitor Icon in EasyConnect Toolbar 159
Figure 194: SYNC DB Monitor Window 160
Figure 195: Point ID is shown in Profile Configuration 160
Figure 196: Data Type Filtering 161
Figure 197: Status monitor showing Offline status 162
Figure 198: Alarm window 162
Figure 199: Watch window 162
Figure 200: Adding point in watch window 163
Figure 201: Adding columns to DB Monitor 163
Figure 202: Quick Filter 163
Figure 203: Add variables 164
Figure 204: Adding a Logic variable 165

SYNC 2000, 3000, 4000 Series Software User Manual 10

Figure 205: Adding a System variable 165
Figure 206: Adding Special functions  169
Figure 207: Enabling the use of a profile row in Logic Engine 170
Figure 208: Exporting logic variables 171
Figure 209: Device Parameters 174
Figure 210: Time Synchronization Window 174
Figure 211: Enabling Check for Firmware Updates 177
Figure 212: Pop-up for Automatic Up gradation 177
Figure 213: Model name prompt for older DCCP versions 178
Figure 214: Automatic upgrade prompt for incompatible DCCP version 178
Figure 215: DCCP update Link in Version Info 179
Figure 216: Version Info for devices with older DCCP Versions 180

SYNC 2000, 3000, 4000 Series Software User Manual 11

List of Tables
Table 1: Software Requirements 14
Table 2: Hardware Requirements 14
Table 3: Converter Parameters 63
Table 4: Configurable Parameters 64
Table 5: Auto map window 96
Table 6: Dialup Parameters 105
Table 7: VPN Pop-Up Details 110
Table 8: VPN Parameters  111
Table 9: NAT parameters 129
Table 10: Channel Configuration Parameters for Achieving Redundancy 141
Table 11: General Node Parameters 143
Table 12: IP Switching Configuration Parameters 145
Table 13: Profile Configuration Details for Redundancy 146
Table 14: Redundancy Switchover Details 146
Table 15: System Variables 168
Table 16: Special Functions 169
Table 17: Time Synchronization Parameters 176
Table 18: Models supported in different SYNC series 182
Table 19: GPC, DCCP & EC Compatibility Table 182
Table 20: Flag Mapping 183
Table 21: IEC 62439-3 Interoperability Table  185
Table 22: List of abbreviations 187

SYNC 2000, 3000, 4000 Series Software User Manual 12

 1
1 Overview of SYNC 2000/3000/4000
SYNC 2000/3000/4000 series of products is a family of hardware solutions that
provide any-to-any protocol conversions. SYNC products are available for a wide range of
rugged substation hardware configurations, to suit every requirement from a simple one modem
channel and limited I/O, to a 16-channel multi-protocol data concentrator/converter. The different
product models vary in processing power, storage capabilities, number of channels and types of
channels to suit different requirements. However, they present a singular frontend via the SYNC
configuration tool EasyConnect.

1.1 EasyConnect
The SYNC 2000/3000/4000 series of products can be fully configured using a software
configuration utility called EasyConnect., This includes defining protocol attributes, mapping data,
updating firmware, setting IP and viewing diagnostics. EasyConnect generates a configuration
file in Extensible Markup Language (XML) format as output. Download this configuration file
using the Download function in EasyConnect to configure the device.

EasyConnect can be used for:

• Updating firmware configuration file
• Resetting SYNC
• Configuring and mapping the protocols supported by the SYNC device
• Managing different profiles on the user’s hard disk for different protocol conversions when
using SYNC. The configuration is simple to carry out on its own.
• Viewing packet diagnostics of the various channels

SYNC 2000, 3000, 4000 Series Software User Manual 13

 1.2 Environment
This section specifies the software and hardware requirements to install and use the EasyConnect
configuration utility.

1.2.1 Software Requirements

The software requirements are given in table 1 (Software Requirements) shown below:
Requirement Description
Operating System Windows XP/ Vista/Windows 7 32/64 bit
.Net framework .Net framework 3.5 or higher
Table 1: Software Requirements

1.2.2 Hardware Requirements

The hardware requirements are given in table 2 (Hardware Requirements) shown below:
Requirement Description
RAM 128 MB or more
Hard Disk Space 1.5 GB or more
DPI Setting 96 DPI
Table 2: Hardware Requirements

SYNC 2000, 3000, 4000 Series Software User Manual 14

 2
2 Getting Started
This section covers the following topics:
• Installing EasyConnect
• Removing EasyConnect
• Starting EasyConnect
• Exiting EasyConnect
• Using the EasyConnect interface

2.1 Installing EasyConnect

The EasyConnect installation files can be obtained in two ways:
• CD supplied along with the SYNC device
• Downloaded from an FTP server – please contact [email protected] for the link to
download the file

To install EasyConnect, do the following:

1. Double-click the EasyConnect icon.
The Welcome window appears.
2. Click Next.
The Choose Destination Location window appears.
3. Click Next.
The Setup Complete window appears.

Note: Follow default options for installing EasyConnect

2.2 Removing EasyConnect

To remove all the installed components of EasyConnect from the user’s system, do the following:
1. From Start menu, choose Settings, the corresponding window will get displayed
2. Choose Control Panel from the window, the Control Panel window gets displayed
3. Select Add or Remove program.
4. From the program list in the Add or Remove Programs window, choose EasyConnect.
5. Click Change/Remove.
6. The Confirm File Deletion window appears.
7. On the Confirm File Deletion window, click Yes.
8. The uninstall shield wizard removes all components from the user’s system.
9. On the uninstall shield wizard, Click OK.

2.3 Starting EasyConnect

EasyConnect helps the user to configure the files needed for the SYNC devices to work.
Download the configured file to the SYNC device before running it.

SYNC 2000, 3000, 4000 Series Software User Manual 15

To start EasyConnect in order to access it, do the following:

1. From Start menu, choose Programs named EasyConnect. The EasyConnect user interface
appears as given in the Figure (EasyConnect User Interface) below:

Figure 1: EasyConnect User Interface

2.4 Exiting EasyConnect

EasyConnect can be closed at any point during the running of the application.

To exit EasyConnect, do the following:

• From File menu, choose Exit. If any configuration is open, a warning window will appear
to confirm whether the user would like to save the configuration before closing Easy
Connect.
• Click Yes to save the configuration at the desired location before exiting EasyConnect.
Click No, not to save the configuration and to continue with exiting EasyConnect. Click
Cancel to cancel exiting EasyConnect.

2.5 Using the EasyConnect Interface

This section provides an overview of the elements and menus available in the EasyConnect
user interface. The components in the EasyConnect user interface are shown in the figure (User
Interface) below and each one is described in detail below:

Figure 2: User Interface

SYNC 2000, 3000, 4000 Series Software User Manual 16

The components are:
• Menu
• Toolbar
• Workspace

2.5.1 Menu
The Menu contains options to execute all the actions that can be done using EasyConnect. The
different menus are:

1.File Menu
Start new configuration, open a saved configuration file or save the configuration, are the options
available in the File menu. A few of these actions are also made available in the toolbar.

Figure 3: File Menu

2.View Menu
The View Menu contains the option to enable or disable the toolbar buttons.

Figure 4: View Menu

SYNC 2000, 3000, 4000 Series Software User Manual 17

3.Configuration Menu
The Configuration menu contains options that correspond to the node in the Tree-View that
has been selected. Depending on the node selected, the options available in the Configuration
menu vary. These actions can also be availed by clicking the right mouse button on the node.
This menu is extensively used in configuring the SYNC and is well explained in the respective
sections.

Figure 5: Configuration Menu

4.Settings Menu
The Settings menu contains some generic actions which are listed below:

Figure 6: Settings Menu

Download: to download the configuration file to the SYNC device.

Apply Configuration: To apply the configuration, to enable the newly downloaded configuration.
Upload: To upload the device configuration file from the SYNC device to EasyConnect.
Restart: To restart the SYNC device.

SYNC 2000, 3000, 4000 Series Software User Manual 18

IP configuration: To configure the IP address of the SYNC device.
Stop: To stop the firmware in the SYNC device.
Start: To start the firmware in the SYNC device.
Scan: To scan all the SYNC devices in the network. Scan will detect a device only if the device
is connected in the network through its 1st interface (lan0) and if it is in the same subnet.
Version Information: To get the version and protocol details of the firmware in the device.
Time Settings: To get or set the time and time zone of the device.
Update: To update the firmware in the device.
DB Delete: To delete database files which exists in the device
Routing Configuration: To add multiple routes, networks, matrix settings and all other settings
available with ‘route’ command of linux from EasyConnect.

5.Diagnostics Menu
The Diagnostics menu contains action items that provide diagnostic functions. The options
available in diagnostic menu are Traffic Monitoring, PDC Diagnostics and device Access Log.

Figure 7: Diagnostic Menu

6.Tools Menu
Tools menu contains options to set EasyConnect parameters like Timeout settings.

Figure 8: Tool Menu

SYNC 2000, 3000, 4000 Series Software User Manual 19

7.Help Menu
The Help menu contains options for EasyConnect Help documentation and Information about
EasyConnect.

Figure 9: Help Menu

2.5.2 Toolbar
The toolbar provides easy access buttons to menu options and they are:
1. File
2. Settings
3. Diagnostics
4. Help
These are selected options from the toolbar menus. They can be enabled or disabled in the View
Menu. Tool tips are available for each toolbar button, describing the functionality associated with
each of them.

Figure 10: Toolbar

2.5.3 Workspace
The workspace section is where all the configurations regarding the different channels, nodes
and stations are done. Depending on the node selected in the Tree-view, the options available in
the Workspace may vary. These are described in detail in the configuration of each item.

SYNC 2000, 3000, 4000 Series Software User Manual 20

 3
3 Download
‘Download’ option can be used to download various files to the device.

Figure 11: Download

1) For a device outside the project context:

In this case, ‘Download’ option can be used to download configuration files, license files and
update packages to the device. In the download window, select Device Name as “Other Device”
if not already selected by default, enter IP address of the device to which the configuration is to
be downloaded. Check the appropriate box against which file you are going to download such
as Configuration file, License files. From the file browse option provided in the download window,
select the required file. Refer following Figure.

Note: After configuration file or license file download, restart device or stop and start
firmware.

SYNC 2000, 3000, 4000 Series Software User Manual 21

 Figure 12: Download: For a device outside the project context

2) For a device in a project context:

In this case, ‘Download’ option can be used to download configuration files, license files, update
packages, dialup settings,VPN settings, SMS Settings, SNMP Settings, TLS Credentials, NAT
Policies and WEBHMI Settings to the device. In the download window, select Device Name
as the name of the relevant configuration (Eg:SS1, SS2 etc), enter IP address of the device
to which the configuration is to be downloaded. Check the appropriate box against which file
you are going to download such as Configuration file, License files. From the file browse option
provided in the download window, select the appropriate file. Refer following Figure.

Note: After configuration file or license file download, restart device or stop and start
firmware. After update package, dialup settings or VPN settings download, restart the
device.

Figure 13: Download: For a device in a project context

SYNC 2000, 3000, 4000 Series Software User Manual 22

Alternatively configuration files, license files, update packages, dialup settings,VPN settings,
SMS Settings, SNMP Settings, TLS Credentials, NAT Policies and WEBHMI Settings can be
downloaded to a device by selecting the ‘Download’ option which shows by right-click on the
device name in the tree node in the configuration window as shown in the figure following below.

Figure 14: Download: For a device in a project context

On selecting ‘Download’ the menu given in following figure will pop-up. Check the relevant boxes
and download.

Figure 15: Download: Pop Up window

SYNC 2000, 3000, 4000 Series Software User Manual 23

There are some features that are available in the download window for single device.
• HSB Configuration Easiness - If user configure the HSB master in the configuration,
then a new IP Address type named HSB IP can be selected and user can download the
configuration to main and stand by IP address.
• Update Package Versioning - This option facilitates the user to assign default version
(1.0.0) for the update packages having no version information when user try to download
the update package.

3) For downloading various files to multiple devices:

This feature can be obtained only when ‘Download’ button on the toolbar is clicked after selecting
‘Devices’ or ‘Configuration’ on the tree menu when one or more devices have been added in the
project.

In the ‘Download’ window, list of all the devices added on the Configuration will be displayed.

Check the devices to be downloaded and specify the corresponding IP address of the device to
which the file is to be downloaded.

Initially the download status of every device is “Ready”. Refer following figure.

Figure 16: Downloading various files to multiple devices

SYNC 2000, 3000, 4000 Series Software User Manual 24

Once the download operation has been done, the status changes to “Completed” for the devices
for which download was successful and “Failed” in the case the download has failed. Refer
following figure.

Figure 17: Downloading various files to multiple devices – Pop UP Window

Alternatively VPN settings can be downloaded to a converter by selecting the ‘Download’ option
which shows by right-click on the VPN tree node in the configuration window.

SYNC 2000, 3000, 4000 Series Software User Manual 25

 4
4 Apply Configuration
Use ‘Apply Configuration’ button to apply configuration to a device.

Figure 18: Apply Configuration

Apply Configuration is used after the download operation. Once the configuration file has been
downloaded to the device, apply configuration is required inorder that the file is made available
in the device.

SYNC 2000, 3000, 4000 Series Software User Manual 26

1) For a device outside the project context:
Specify the IP address and select the device name as “Other Device”of the device for which
apply configuration is to be done. Specify the appropriate device type (Example: SYNC2000).
Refer following Figure.

Figure 19: Apply Configuration: For a device outside the project context

2) For a device in a project context:

Specify the IP address and the device name (Example: SS1, SS2 etc.) of the device to which
apply configuration has to be done. Refer following Figure.

Figure 20: Apply Configuration: For a device in a project context

SYNC 2000, 3000, 4000 Series Software User Manual 27

2) For apply configuration to multiple devices:
Apply All can be used to apply configuration to the devices at once.

This feature can be obtained only when the ‘Apply Configuration’ button on the toolbar is clicked
after selecting ‘Devices’ or ‘Configuration’ on the tree menu.

List of all the devices added on the Configuration will be displayed. Check the devices for which
apply configuration has to be done and specify the corresponding IP Addresses of the devices
for which apply configuration has to be done.

Initially the apply configuration status of every device is “Ready”. Refer following Figure.

Figure 21: Apply Configuration: For apply configuration to multiple devices

SYNC 2000, 3000, 4000 Series Software User Manual 28

Once the apply configuration operation has been done, the status changes to “Completed” for the
devices for which apply configuration was successful and “Failed” in the case apply configuration
has failed. Refer following Figure.

Figure 22: Apply Configuration: Pop UP Window

SYNC 2000, 3000, 4000 Series Software User Manual 29

 5
5 Upload
‘Upload’ option is used to fetch configuration data from the device. Using this option user can
upload Configuration file, Device Lan Settings and WEB HMI Files.

Figure 23: Upload

• To get Configuration File, Lan Settings and Web HMI Files, tick Configuration file, Lan
Settings File and HMI Files respectevely. Refer following figure.

Note: HMI Files option will be enabled only for SYNC3000/SYNC4000 Devices.

SYNC 2000, 3000, 4000 Series Software User Manual 30

 Figure 24: Upload Options

Upload command has three modes:

1) Add a new device to an existing project:

This mode is used to add a new device to a project opened in the Easy Connect configuration
window. In the upload window, enter IP address of the device from which the configuration file
is to be uploaded. Select the option “Import to the Configuration [Add as a new Device]”. Click
Upload. The data will get uploaded to the configuration window as a new device. For details refer
following figure.

Figure 25: Add a new device to an existing project

SYNC 2000, 3000, 4000 Series Software User Manual 31

2) Update a device in an existing project:
This mode is used to update an existing device in a project opened in the Easy Connect
configuration window with configuration data from a device. In the upload window, enter IP
address of the device from which the configuration data is to be uploaded. Select the option
“Update the Device”. Select the relevant device(Eg.SS1, SS2 etc). Click Upload. The files in the
configuration window will get updated with the files from the device. For details refer following
figure.

Figure 26: Update a device in an existing project

Alternatively existing devices can be updated by selecting the ‘Update Device’ option which
shows by right-click on the device name in the tree node in the configuration window as shown
in the figure below.

Figure 27: Update a device in an existing project

SYNC 2000, 3000, 4000 Series Software User Manual 32

On clicking ‘Update Device’, the following pop-up in following figure will be displayed. Enter the
relevant IP address and click ‘Upload’.

Figure 28: Update a device - Pop up window

3) Upload configuration to a particular folder:

This mode is used to save converter configuration files to a local folder. In the upload window,
enter IP address of the device from which the configuration file is to be uploaded. Select this
option”Save in”. From the file browse option provided in the upload window, select destination file.
Refer following figure.To view the uploaded file open the file from the Easy Connect application.

Figure 29: Upload configuration to a particular folder

SYNC 2000, 3000, 4000 Series Software User Manual 33

 6
6 Restart Device
Use ‘Restart’ button to restart a device.

Figure 30: Restart

1) For a device outside the project context:

Specify the IP address and select the device name as “Other Device” of the device to be restarted.
Specify the appropriate device type (Example: SYNC2000) Refer following Figure.

Figure 31: Restart Device - For a device outside the project context

SYNC 2000, 3000, 4000 Series Software User Manual 34

2) For a device in a project context:
Specify the IP address and the device name (Example: SS1, SS2 etc) of the device to be
restarted. Refer following Figure.

Figure 32: Restart Device - For a device in a project context:

3) For restarting multiple devices:

Restart All can be used to restart the devices at once. This feature can be obtained only when
the ‘Restart’ button on the toolbar is clicked after selecting ‘Devices’ or ‘Configuration’ on the tree
menu. List of all the devices added on the Configuration will be displayed. Check devices to be
restarted and specify the corresponding IP Addresses. Initially the restart status of every device
is “Ready”. Refer following Figure.

Figure 33: Restart Multiple Devices

SYNC 2000, 3000, 4000 Series Software User Manual 35

Once the restart operation has been done, the status changes to “Completed” for the devices for
which restart was successful and “Failed” in the case restart has failed. Refer following Figure.

Figure 34: Restart Multiple Devices – Pop Up

SYNC 2000, 3000, 4000 Series Software User Manual 36

 7
7 Stop Firmware
Use Stop option to stop firmware.

1) For a device outside the project context:

Specify the IP address and select the device name as “Other Device”of the device in question.
Give the appropriate model name (Example:SYNC2000). Click “Stop” to stop the firmware.

Refer following Figure.

Figure 35: Stop Firmware: For a device outside the project context

2) For a device in a project context:

Specify the IP address and the device name according to the configuration (Example: SS1, SS2
etc) of the device in question. Click “Stop” to stop the firmware.

Refer following Figure.

SYNC 2000, 3000, 4000 Series Software User Manual 37

 Figure 36: Stop Firmware: For a device in a project context

SYNC 2000, 3000, 4000 Series Software User Manual 38

 8
8 Start Firmware
Use Start option to start firmware.

Figure 37: Start Firmware

1) For a device outside the project context:

Specify the IP and select the device name as “Other Device”of the device in question. Give the
appropriate model name (Example:SYNC2000). Click “Start” to start the firmware.

Refer following Figure.

Figure 38: Start Firmware: For a device outside the project context

SYNC 2000, 3000, 4000 Series Software User Manual 39

2) For a device in a project context:
Specify the IP and the device name according to the configuration (Example: SS1, SS2 etc) of
the device in question. Click “Start” to start the firmware.

Refer following Figure.

Figure 39: Start Firmware: For a device in a project context

Figure 40: Download

SYNC 2000, 3000, 4000 Series Software User Manual 40

 9
9 Scan for connected Devices
The details of live SYNC Devices connected to the network can be viewed using ‘Scan’.

Figure 41: Scan

The available information of the devices include Model Name, Interface name, IP Address of
interfaces of the devices, Net Mask, MAC Address, Product Key,etc. The result can be filtered
using the search option. The ‘Refresh’ button can be used to refresh the list at any point of time.
Refer following Figure.

Figure 42: Scan Window

SYNC 2000, 3000, 4000 Series Software User Manual 41

 10
10 Version Information
Version Information details are displayed in General tab and Advanced Tab.

Figure 43: Version Information

The General tab contains following informations

• Device model - Device Model Name
• EasyConnect version Name - EasyConnect Version Name
• DCCP version Name - Version of DCCP Firmware in the device.
• Secure DCCP - SYNC Device Contains Secure DCCP or not.
• GPC version Name - Version of GPC firmware in the device.
• Number of Licensed Masters - Number of licensed masters in the device
• Licensed Masters - List of licensed masters in the device
• Number of Licensed Slaves - Number of licensed slaves in the device
• Licensed slaves - List of licensed slaves in the device
• Number of Licensed Modules -Number of licensed modules in the device
• Licensed Modules - List of licensed modules in the device
• Build Date - Firmware Build Date
• Number of Licensed Com Ports - Number of licensed Com Ports in the device
• Supporting Customizations - Customizations supported by firmware in the device.
• The Advanced tab contains following informations
• Device Application Information - Device Application Information
• CPU Speed - CPU Speed
• RAM – Total Usable RAM memory
• Flash – Total Usable Flash Memory
• RTU Version – RTU Version (Applicable for RTUs only)
• Available Packages – List of available packages on the device.

SYNC 2000, 3000, 4000 Series Software User Manual 42

1) For a device outside the project context:
Specify the IP address and select the device name as “Other Device”of the device in question.
Specify the appropriate model name (Example: SYNC2000). Click”OK” to retrieve version
information. Refer following Figure.

Figure 44: Version Information: For a device outside the project context

SYNC 2000, 3000, 4000 Series Software User Manual 43

2) For a device in a project context:
Specify the IP address and the device name (Example: SS1, SS2 etc.) of the device in question.
Click”OK” to retrieve version information. Refer Figure.

Figure 45: Version Information: For a device in a project context

SYNC 2000, 3000, 4000 Series Software User Manual 44

3) Save Version Information
The Version Information can be saved in text format using Save button. Refer Following Fifure

Figure 46: Save Version Information

SYNC 2000, 3000, 4000 Series Software User Manual 45

 11
11 Time Settings
Time as well as timezone can be get as well as set for all devices.

Get Time Settings:

1) For a device outside the project context:

Specify the IP address and select the device name as “Other Device”of the device in question.
Give the appropriate model name (Example: SYNC2000). Click ‘Get ‘ to get the Time Settings
for the device.

Refer following Figure.

Figure 47: Get Time: For a device outside the project context

SYNC 2000, 3000, 4000 Series Software User Manual 46

2) For a device in a project context:
Specify the IP address and the device name according to the configuration (Example: SS1, SS2
etc) of the device in question. Click ‘Get ‘ to get the Time Settings for the device.

Refer following Figure.

Figure 48: Get Time: For a device in the project context

SYNC 2000, 3000, 4000 Series Software User Manual 47

II) Timezone Set
1) For device outside the project context:
Specify the IP address and select the device name as “Other Device”of the device in question.
Give the appropriate model name (Example:SYNC2000). Click the Timezone tab, choose the
required timezone from the combo list and click ‘Set Timezone’ to set the selected Timezone for
device.

Refer following Figure

Figure 49: Set Timezone: For a device outside the project context

SYNC 2000, 3000, 4000 Series Software User Manual 48

2) For Device in the project context:
Specify the IP address and the device name according to the configuration (Example: SS1, SS2
etc) of the device in question. Click the Timezone tab, choose the required timezone from the
combo list and click ‘Set Timezone’ to set the selected Timezone for device.

Refer following Figure

Figure 50: Set Timezone: For a device in the project context

SYNC 2000, 3000, 4000 Series Software User Manual 49

III) Set Time Settings:
a) Using system settings:
Using system settings will configure the the converter with a time relative to the corresponding
system settings of the Easy Connect client on the converter.

1) For device outside the project context:

Specify the IP address and select the device name as “Other Device”of the device in question.
Give the appropriate model name (Example:SYNC2000S6R1). Click the Time tab, select the
button ‘Use System Settings’ and click ‘Set Time’ to set the selected time settings for the device.

Refer following Figure.

Figure 51: Set System Time: For a device outside the project context

SYNC 2000, 3000, 4000 Series Software User Manual 50

1) For device in the project context:
Specify the IP address and the device name according to the configuration (Example: SS1, SS2
etc) of the device in question. Click the Time tab, select the button ‘Use System Settings’ and
click ‘Set Time’ to set the selected time settings for the device.

Refer following Figure

Figure 52: Set System Time: For a device in the project context

SYNC 2000, 3000, 4000 Series Software User Manual 51

b) Using manual settings:
Manual settings will set the time settings entered as the local time in the converter.

1) For device outside the project context:

Specify the IP address and select the device name as “Other Device”of the device in question.
Give the appropriate model name (Example:SYNC2000S6R1). Click the Time tab, select the
button ‘Manual Settings’, enter the time settings required and click ‘Set Time’ to set the selected
time settings for the device.

Refer following Figure.

Figure 53: Set Manual Time: For a device outside the project context

SYNC 2000, 3000, 4000 Series Software User Manual 52

1) For device in the project context:
Specify the IP address and the device name according to the configuration (Example: SS1, SS2
etc) of the device in question. Click the Time tab, select the button ‘Manual Settings’, enter the
time settings required and click ‘Set Time’ to set the selected time settings for the device.

Refer following Figure.

Figure 54: Set Manual Time: For a device in the project context

Note: SYNC Device is considering the time below Year 2000 as invalid. Hence time setting below
year 2000 is not recommended.

SYNC 2000, 3000, 4000 Series Software User Manual 53

 12
12 Update Firmware
Firmware for the device can be updated using ‘Update’ option. this involves update of ‘gpc’ and
‘dccp’.

‘gpc’ file contains the software used for protocol conversion in the device.

‘dccp’ contains the program required for the interface between configuration tool and device.

Both gpc and dccp files can be browsed using options provided. Both the files will get updated
separately and current status of updating will be shown as message.

1) For a device outside the project context:

Specify the IP address and select the device name as “Other Device”of the device in question.
Give the appropriate model name (Example:SYNC2000). Click “OK” to update the changes.

Refer following Figure.

Note: Restart required after ‘Update’

Figure 55: Update: For a device outside the project context

SYNC 2000, 3000, 4000 Series Software User Manual 54

2) For a device in a project context:
Specify the IP address and the device name according to the configuration (Example: SS1, SS2
etc) of the device in question. Click “OK” to update the changes.
Refer following Figure.

Note: Restart required after ‘Update’

Figure 56: Update: For a device in a project context

SYNC 2000, 3000, 4000 Series Software User Manual 55

 13
13 Traffic/Diagnostics Monitor
Packet communication log corresponding to the selected channel is displayed in the diagnostic
window, once the configuration of the converter in question is opened in the Easy Connect
configuration window. We can select maximum two channels at a time for diagnostics.

IP address of the device where the firmware is running has to be specified. There are options
to save diagnostic log, pause the log and clear the diagnostic window corresponding to each
channel. Refer following Figure.

Figure 57: Traffic/Diagnostics Monitor

Please note that traffic through TCP port number 2400 is not blocked by your workstation firewalls
or antivirus applications. It is absolutely necessary for the proper working of this function.

SYNC 2000, 3000, 4000 Series Software User Manual 56

 14
14 User Management
14.1 User Authentication
EasyConnect starts with a login window, as shown in the figure (EasyConnect Login) below:

Figure 58: EasyConnect Login

By default, the user “Admin” with the password “Admin” has administrative privileges. This user can
perform every device related operation and can create/edit a configuration. Admin has the privilege
to add users, roles, change passwords and to assign privileges using ‘User Management’. Every
change made in the EasyConnect configuration is logged and can be viewed under the ‘Audit
Trail’ option.

14.2 Configuring Users and Roles

Only the default administrator can access the user management tool. The administrator has the
permission to create users, roles, change passwords and assign roles to them.

SYNC 2000, 3000, 4000 Series Software User Manual 57

Select Manage option in User Management as shown in the figure (User Management):

Figure 59: User Management

Roles
Define roles before creating a user. To add a role, select the Role tab and click on the ‘Role’ node
in the tree view panel as shown in Figure (Adding a role). Check the privileges to be assigned,
enter the Role name and description. Click ‘Add Role’ to add the role.

Figure 60: Adding a Role

To modify a role, select it and click on the Edit button. The fields can then be edited.

To delete a role, select it and click Delete.

SYNC 2000, 3000, 4000 Series Software User Manual 58

Users
To add a user, select the user tab and click the User node in the tree view. Fill the new user
details in the right panel. Click Add User as shown in Figure (Adding a User).

Figure 61: Adding a User

To modify a role, select it and click on the Edit button. In order to change the password, check
the ‘Change Password’ option.

The navigation buttons will be disabled when a filter is applied. Click ‘Remove Filter’ to remove
the filter options.

To delete a role, select it and click Delete.

SYNC 2000, 3000, 4000 Series Software User Manual 59

 15
15 Audit Trail
Every activity performed by a user is logged and can be viewed using the ‘Audit Trail’ option in
‘Tools’ as shown in Figure (Audit Trail).

Figure 62: Audit Trail

The log contains the user name, the activity the user performed and the timestamp at which it
was done as shown in Figure (EasyConnect Log).

Figure 63: EasyConnect Log

‘Advanced Filter’ option is available for filtering the log based on user name or timestamp.

SYNC 2000, 3000, 4000 Series Software User Manual 60

 Figure 64: Advanced Filter

The navigation buttons will be disabled when a filter is applied. Click ‘Remove Filter’ to remove
the filter options.

SYNC 2000, 3000, 4000 Series Software User Manual 61

 16
16 Configure SMS
DCU will communicate with Sync5000 server through GPRS/PSTN modem. Through Easy
connect we can configure all the DCU in the field .Some parameter configurations through SMS
and some SMS alert features are available. The features available are, power outage of DCU
indication to Sync5000 server. Configuration of polling interval and VPN server IP of DCU.

This feature is only available when IEC 1107 Master protocol Profile has been added.

16.1 SMS Port Settings

To configure SMS Settings for the Modem connected to your system.
• Configure SMS Port Settings by selecting it from the ‘Tool’ menu. Refer the following
figure.

Figure 65: Select SMS Port Settings.

SYNC 2000, 3000, 4000 Series Software User Manual 62

 • Save SMS Port settings.
To test the SMS port, click on ‘Test’ button. Refer the following figure.

Figure 66: Test SMS Port Settings

Converter Parameters shown below are to be filled.

Parameter name Range/Optional Default value Description

values
DCU location Location identification code for
N/A
identification code identification of DCU only
DCU location Location identification name for
N/A
identification Name identification of DCU only
Table 3: Converter Parameters

16.2 SMS Settings for SYNC Device

• Right click on the ‘Settings’ and choose ‘Add SMS Settings’. Refer the following figure.
This SMS settings is the settings configured for the DCU.

Figure 67: Add SMS Settings

SYNC 2000, 3000, 4000 Series Software User Manual 63

 • Fill the common configurable parameters.The parameters are explained below.

Parameter name Range/Optional Default value Description

values
Depending
on the input/ Name of serial port to be
Port Com1 to Com16
output/serial configured for this channel.
channels added
Baud rate for serial
Baud Rate 200 to 115200 115200 communication in Bits per
second
Number of data bits for serial
Data Bits N/A 8
communication
Number of stop bits for serial
Stop Bits N/A 1
communication
Parity N/A None Parity for serial communication
Phone number of the modem
DCU Number N/A
connected to specified DCU
Phone number of of the
Admin 1 Mobile modem connected to
N/A
Number Sync5000 (First redundant
server)
Phone number of of the
Admin 2 Mobile modem connected to
N/A
Number Sync5000 (Second redundant
server)
Table 4: Configurable Parameters

• Check the ‘SMS settings’ box in the Download command window as shown in the following
figure and click ‘Download’.

SYNC 2000, 3000, 4000 Series Software User Manual 64

 Figure 68: SMS Settings Download

Note: Restart is required after downloading the settings for the changes to take effect.

Send SMS
Right click on ‘Devices’ or a particular device and select the option ‘Send Sms’.Refer the following
figure

SYNC 2000, 3000, 4000 Series Software User Manual 65

 Figure 69: Send SMS

Tick the node whose information has to be send. Check VPN IP in case it too has to be included
in the information. Refer the following figure. Click ‘Send SMS’.Incase the Sms has been sent
succesfully, the Device will be highlighted green and in case of a failure ,it will be red.

Figure 70: Send SMS Window

SYNC 2000, 3000, 4000 Series Software User Manual 66

Change Admin
For preventing unauthorized use of features two level of security has been added, DCU level
and modem level. Right click on ‘Devices’ or a particular device and select the option ‘Change
Admin’.Refer the following figure.

For changing the admin number of DCU , first we have to download new SMS setting to DCU(for
changing admin number in side DCU) and then send change admin SMS to DCU(change admin
number inside modem). If changed both the admin numbers you have to send change admin
SMS to DCU separately for admin 1 and admin 2.If you are changing admin mobile number from
first Sync5000 server ,first send change admin 2 SMS first and if you are changing admin from
second Sync5000 server ,first send change admin 1 SMS first. Other wise you cant change other
admin number.

Figure 71: Change Admin

SYNC 2000, 3000, 4000 Series Software User Manual 67

The Change Admin form appears through which we can change the admin and the corresponding
mobile number. Refer the following figure.

Figure 72: Change Admin Window

Delete SMS Details

To delete the ‘SMS Settings’ settings from the gateway. Right click on the ‘SMS Settings’ and
choose ‘Delete’ . Refer the following figure.

Figure 73: Delete SMS Details

Then check the ‘SMS settings’ box in the Download command window as shown in Figure : SMS
Settings Download and click ‘Download’.

SYNC 2000, 3000, 4000 Series Software User Manual 68

 17
17 Set Language
In EasyConnect, there is an option to set the language of the Configuration tool. This can be
done by selecting ‘Set Language’ in the menu items, Tools ->Set Language.

Figure 74: Set Language

Users can select any of the *supported languages, then click ‘OK’ and reopen EasyConnect to
see the configuration tool in the selected language.

*Supported Languages - English and Spanish.

SYNC 2000, 3000, 4000 Series Software User Manual 69

 18
18 DB Delete
‘DB Delete’ button can be used to delete a database file which exists in the gateway.For gateways
which support DB configuration, in case a DB file already exists in the gateway, user is prompted
to delete the old database before the configuration is applied. The gateway is automatically
restarted after this function.

1) For a device outside the project context:

Specify the IP address and select the device name as “Other Device”of the gateway for which
apply configuration is to be done. Specify the appropriate converter type (Example: SYNC2111).
Refer the following figure.

Figure 75: DB Delete: For a device outside the project context

SYNC 2000, 3000, 4000 Series Software User Manual 70

2) For a device in a project context:

Specify the IP address and the device name (Example: SS1, SS2 etc) of the gateway in which
the DB has to be deleted.

Refer the following figure.

Figure 76: DB Delete: For a device in the project context

3) For deleting Database File in multiple devices:

DB Delete All can be used to delete already existing database files in different devices at once.
This feature can be obtained only when the ‘DB Delete’ button on the toolbar is clicked after
selecting ‘Devices’ or ‘Configuration’ on the tree menu. List of all the devices added on the
Configuration will be displayed. Check the gateways of devices for which the Database file has
to be deleted and specify the corresponding IP Addresses. Initially the DB delete status of every
device is ‘Ready’.

Refer the following figure.

Figure 77: Deleting Database File in multiple devices

SYNC 2000, 3000, 4000 Series Software User Manual 71

Once the DB delete operation has been done, the status changes to ‘Completed’ for the gateways
for which DB delete was successful and ‘Failed’ in the case DB delete operation has failed.
Refer the following figure .

Figure 78: DB Delete window

SYNC 2000, 3000, 4000 Series Software User Manual 72

 19
19 Gateway Log
Gateway Log facilitates an option to get the three different logging such a Gateway Access Log,
Application Log and Internal Logging.

Inorder to select Gateway Log ,select Diagnostics from Easy connect, under the Diagnostics tab
there is an option to select Gateway Log.

Refer the following figure.

Figure 79: Gateway Log

SYNC 2000, 3000, 4000 Series Software User Manual 73

1. Gateway Access Log
Event logging is provided in devices for all user actions through EasyConnect and web-server.
These logs are kept for at least 90 days and can be retrieved using EasyConnect. Older logs will
be automatically deleted from the device. Gateway Access Log can be used to retrieve these
logs.

1) For a device outside the project context:

Specify the IP and select the device name as “Other Device”of the gateway in question. Specify
the appropriate model name (Example: SYNC2000). Specify the start and end date. Also give
the location to which the files must be saved to.

Refer the following figure.

Figure 80: Gateway Access Log: For a device outside the project context

SYNC 2000, 3000, 4000 Series Software User Manual 74

2) For a device in a project context:
Specify the IP address and the device name (Example: SS1, SS2 etc) of the gateway in question.
Specify the start and end date. Also give the location to which the files must be saved to.

Refer the following figure.

Figure 81: Gateway Access Log: For a device in the project context

SYNC 2000, 3000, 4000 Series Software User Manual 75

2. Application Logs
Applcation Logs command can be used to retrieve the VPN and Dialup logs . This can be used
to troubleshoot the VPN and Dialup Functions . For starting the log, select the type of log (VPN
or Dialup) and file to which the log has to be retrieved,Click the ‘Start’ button .For retrieving the
log click the ‘Get log’ button,this will stop the VPN or Dialup functionality and gets the current
log .The user can restart the logging by clicking on ‘Start’.After completing the troubleshooting
procedure with logs ,please ensure that Gateway is restarted .If the user tries to get a log without
starting the log ,The Easy Connect will show an error message “Cannot find the file”.

1) For a device outside the project context:

Specify the IP address and select the device name as “Other Device”of the gateway in question.
Specify the appropriate model name (Example: SYNC2000).Select the type of application
whose log You wish to receive, Here the available options are Dialup or VPN . Using the browse
button,select the file to which the log must be retrieved. Click ‘Start’ button.

Refer the following figure.

Figure 82: Application Logs: For a device outside the project context

Once this is done, click ‘Get Log’ in the dialog box after the time you want to see the VPN/Dialup
details. The log details will be saved to the selected file and can be viewed with a suitable text
editor.*

SYNC 2000, 3000, 4000 Series Software User Manual 76

2) For a device in a project context:
Specify the IP address and the device name (Example: SS1, SS2 etc) of the gateway in question.
Select the type of application whose log You wish to receive, Here the available options are
Dialup or VPN . Using the browse button, select the file to which the log must be retrieved. Click
‘Get Log’.

Refer the following figure.

Figure 83: Application Logs: For a device in the project context

Once this is done, click ‘Get Log’ in the dialog box after the time you want to see the VPN/Dialup
details. The log details will be saved to the selected file and can be viewed with a suitable text
editor.*

* Make sure that you retrieve the log after a finite time.(time necessary to get suitable diagnostics
log messages. In most cases 2-3 minutes of log messages would be sufficient). Failing to do
so could affect system performance. Always restart the gateway after you have finished the log
retrieval.

SYNC 2000, 3000, 4000 Series Software User Manual 77

3. Internal Log
Internal Logging implementation is to store all protocol communication logs and diagnostic logs
internally. EasyConnect provides an option for saving Internal Log as well as Diagnostic Log.
Specify the IP address of the device from which the log need to be retrieved and select a folder
path where the log need to be saved. Then click on the ‘Get Log’ button in the dialog box so that
you can retrieve the internal log files into the selected folder.

Refer the following figure.

Figure 84: Internal Log

Note: If C37118 master is configured, SYNC will log the C37118 errors (Typically STAT Word
Errors) to PDCErrorLog.txt . This internal log will be obtained using the Get Log option.

SYNC 2000, 3000, 4000 Series Software User Manual 78

 20
20 API Configuration
Custom build applications can be interfaced in SYNC. Custom build application can be any
protocol drivers/ optimization engine, calculation and algorithm engine etc. This section explains
the configuration details of SYNC - API.

Note: The Custom build Application can use SYNC APIs for control and communication using
SYNC hardware. For details refer SYNC-API User Manual

Configure SYNC API:

1) Click on tools → API Configuration, API Configuration window will appear

Figure 85: SYNC API: API Configuration

2) Click on add new protocol, a new protocol with predefined configurable parameters appear.
Click on Type drop down menu to select the protocol to be master or slave .

Figure 86: SYNC API: Add New Protocol

SYNC 2000, 3000, 4000 Series Software User Manual 79

3.)Other than the predefined generic parameters, to add a new parameter click on Add(+). A
new row will be added with the options to add xml attributes and value range. To add more
parameters repeat the process. To delete any of the added parameters click on Del(-) option.

Figure 87: SYNC API: Add new parameter

4.)To configure the added parameter click on Add option corresponding to the parameter under
XML Attributes, xml attribute window appears with a default row with attribute name as Type, the
required attribute value can be entered. To add more attributes click on Add(+) option in the XML
Attribute window and then enter the attribute name and attribute value. Click on save to save the
changes.

Figure 88: SYNC API: Configure parameter

SYNC 2000, 3000, 4000 Series Software User Manual 80

5.) The option under display control corresponding to the added parameter allows you to choose
the display either to be a text box or Combo box. Similarly the option under Cell Editable allows
you to choose between true or false. If true, you will have the provision to change the value range
of the parameter even after the protocol has been created, if false you will not have the provision
to change the values.

6.) To add a value range click on Add option under Value Range option a window will appear.
Select the data type to be either integer or string. If integer is chosen option to enter the range
will be enabled. If string is chosen option to enter the string length will be enabled. Refer following
figure

Note: The default XML value entered must be within the range specified.

Figure 89: SYNC API : Add Value Range

7.) Click on the master node/Slave node tab to view the predefined node parameters and to add
node parameters, click on Add(+) option click on the master node /Slave node tab . A new row
with a configurable parameter will be added, and to configure the added node parameter follow
steps 4, 5 and 6.To delete any of the added parameters click on Del(-) option.

Figure 90: SYNC API: Node Parameters

SYNC 2000, 3000, 4000 Series Software User Manual 81

8.) Click on the data Profile tab to view the predefined profile parameters and to add profile
parameters, click on Add(+) option. A new row with a configurable parameter will be added, and
to configure the added node parameter follow steps 4, 5 and 6. An additional option under XML
tag name can be configured by clicking on the displayed tag name(KEY4) and by changing it to
the required name. To delete any of the added parameters click on Del(-) option.

Figure 91: SYNC API: Data Profile Parameters

NOTE: For all the above mentioned parameters, the name of the added parameter can be
changed by clicking on it and renaming it.

9.) Click on firmware tab, click on Add(+) option, add the device from the drop down list and
select the firmware file from your system to make this protocol exclusive for that device. To
delete the added firmware click on Del(-) option.

Figure 92: SYNC API: Add Firmware Details

SYNC 2000, 3000, 4000 Series Software User Manual 82

10.) Click on save option to save the changes made and then click on Save List to save the
protocol created. When you click on save list a warning dialog box appears asking you to restart
Easy Connect.

Figure 93: SYNC API: Save Changes, Warning Message

11.) After the Easy Connect has been restarted this protocol will available in master protocols
under protocol configuration. Refer following figure

Figure 94: SYNC API: Protocol Configuration Window

SYNC 2000, 3000, 4000 Series Software User Manual 83

 21
21 Configuring Gateways
The SYNC device has to be first configured before it can be run. The configuration of any protocol
interface module in SYNC can be done using the EasyConnect configuration utility.

The configuration for any protocol conversion function can be divided into a few logical steps.
Master protocol configuration will be divided into the following sections, namely: Channel, Node,
Profile and Row addition. For a slave; Profile, Channel and Node are configured. A master and
slave can be mapped by the Add Map option. The following steps explain how to configure
protocol modules for any SYNC model.

Steps to configure a gateway:

• Add Master channels
• Add Slave Channels
• Add Master to Slave Map
• Slave to Slave Mapping
• Dial up Support
• VPN Support
• NAT policies
• SNMP Support
• Configure Teaming or LAN port redundancy
• DCCP packaging
• IEC 61131 Logic Interface support
• Variables

Steps 1, 2 and 3 explain the protocol conversion function of the gateways. The remaining
steps elaborate additional/optional communication features of the device. For normal protocol
conversion requirements, users can stop at step 3. Proceed to further steps when any of the
features mentioned above are used.

SYNC 2000, 3000, 4000 Series Software User Manual 84

 21.1 Add Master Channel
1. Add Device either by selecting a model from Device configuration section or by right clicking
on Devices in the left hand side tree view pane, as shown in Figure (Add Device) below:

Figure 95: Add Device

2. To modify, an already created device model, right click the selected device model in the left
pane of the application, choose the model from the sub menu of Modify device as shown in
Figure (Modify Device) below.

Figure 96: Modify Device

SYNC 2000, 3000, 4000 Series Software User Manual 85

3. To delete the selected device, right click the selected device, and choose Delete as shown in
the Figure (Delete device) below:

Figure 97: Delete device

4. Add Master channels to the device model as shown in the Figure (Add Master Protocol) below:

Figure 98: Add Master Protocol

SYNC 2000, 3000, 4000 Series Software User Manual 86

5. To delete a protocol specific communication channel, select the Delete option from the menu
on right clicking on the selected channel as shown in Figure (Delete Channel) below:

Figure 99: Delete Channel

6. Add Node or Station as shown in Figure (Add Station) below:

Figure 100: Add Station

SYNC 2000, 3000, 4000 Series Software User Manual 87

7. Delete a station by selecting Delete from the menu displayed on right by clicking on selected
station.

Figure 101: Delete Station

8. To add Master Profile, right click on Node and select Add Profile.

Figure 102: Add Profile

SYNC 2000, 3000, 4000 Series Software User Manual 88

Profiles can be saved for reusing the same address configuration for different masters. To save
a profile, right click a Profile tree node and select Export Profile. A Save File window will pop up.
Save the profile with desired name in the desired location.

Figure 103: Export Profile

Instead of adding a new profile, a user can import a profile from previously saved profile data.
Right click on a master station and select Import Profile option. An Open File window will pop up.
Open a saved profile file. Refer to Figure (Import Profile) below:

Figure 104: Import Profile

SYNC 2000, 3000, 4000 Series Software User Manual 89

9. To delete a Profile, right click on the Profile and select Delete.

Figure 105: Delete Profile

10. To add Master Row, right click on Profile and select Add Points as shown in the Figure (Add
Row) below:

Figure 106: Add Row

SYNC 2000, 3000, 4000 Series Software User Manual 90

11. To modify a row, select a row from the profile grid. Click on Modify Row button. A new window
will pop up with values of selected row.

Figure 107: Modify Row

12. To delete rows, select rows from the profile grid and click Delete Row on the right pane.

Figure 108: Delete Row

21.2 Add Slave Channel and Node

To add a slave channel and node follow the procedures mentioned above section add master
channel and node.

SYNC 2000, 3000, 4000 Series Software User Manual 91

 21.3 Master to slave Mapping
To add a Map, select the required row and the desired slave node and then click on Add Map.

Figure 109: Add Map

Note: To Enable Master-to-Master mapping, select Show Master Nodes (Master-to-Master

mapping is used when input data from an external device is translated to a command/ output
and sent to an external device).

To modify a mapped row, select a row from the destination unit and click on Modify Map button.
A new window will open with added mapped values. Edit the parameter values. Click on Save to
update the modified mapped point. Refer to Figure (Modify Map) below:

Figure 110: Modify Map

SYNC 2000, 3000, 4000 Series Software User Manual 92

To delete a mapped row or group of rows from the conversion, select mapped row from the
destination unit and click Delete Map. To delete destination unit profile, right click on mapping
tree node under destination unit, select Delete. Refer to Figure (Delete Map):

Figure 111: Delete Map

21.3.1 Auto Mapping – Master to Slave

EasyConnect provides options for mapping the master points automatically to a selected slave
node. Users can either auto map the entire row or some selected rows that are configured in the
master profile. The steps for automatic mapping are given below:
• Select the slave protocol to which the points are to be mapped.
• For mapping the entire rows in a profile, Right click on the corresponding profile and click
the option Auto Map as shown in Figure (Auto Map Entire Profile Points):

SYNC 2000, 3000, 4000 Series Software User Manual 93

 Figure 112: Auto Map Entire Profile Points

3. For mapping the selected rows in a profile, select the needed rows in the profile for which the
automatic mapping is required. Click on Auto Map (slave/destination mapping part) as shown in
the Figure (Auto Map Selected Profile Points):

Figure 113: Auto Map Selected Profile Points

SYNC 2000, 3000, 4000 Series Software User Manual 94

Step 2 or 3 will pop up the Auto Map window as shown in Figure (Auto Map Window) below. User
can configure the details in the Auto Map window and generate auto mapping.

Figure 114: Auto Map Window

21.3.2 Auto Map Window

Auto Map window shows the master (source) types that are considered for automatic mapping,
corresponding slave types automatically considered as mapping type (user can change using
combo options) and corresponding start address in the slave. The parameter details of Auto Map
window are given in table 3 (Auto map window) shown below.

SYNC 2000, 3000, 4000 Series Software User Manual 95

 Sl. No Parameter Details
Indicates the node number whose profile needs to
1 Source Node
be mapped. This parameter is not editable.
Indicates the node to which the mapping needs to
be done. The default will be the node selected in
2 Destination Node the mapping window. User will be able to change
the same to any other node available in the
configuration system.
Protocol of the source node.
3 Source Protocol
This parameter is not editable.
Protocol of the destination node.
4 Destination Protocol
This parameter is not editable.
Indicates source data types from which mapping is
5 Source Types
carried out.
Indicates suggested destination data type for the
specific source type to which mapping is carried
6 Destination Types out. This is a default suggestion and can be
changed to any of the allowed types available in
the combo box.
This indicates the destination start address for
the specific destination type. This is generated
after evaluating all the existing addresses, and
last address + 1 of the already existing address is
considered as default. User can change the start
7 Destination Start Address address but it will again undergo evaluation.
There will be multiple address parameters
based on the protocol used. For example, if it is
IEC101/104, the same will have IOA but if it is IEC
103, it will have ftype and inumber as address
parameters.
Table 5: Auto map window

The following points will be applicable to the Auto Mapping Window:

• Only data types that have at least a point available for mapping to the current slave shall
be displayed in the auto-mapping window.
• Similar source types will be grouped and displayed as a single row in the Auto Map window.
For each protocol, the groupings of source types differ.
• All the types under the Basic type of the source type will be available as combo box
options of Destination Types.
• In cases where destination address range is not sufficient to map all the points, an error
• message would be displayed in the validation stage after the ‘OK’ button is clicked
• Points will not be split and mapped for numerical address based protocols. A continuous
address space large enough to hold the points in a single row (source) is found and the
points are mapped to that range.
• Auto-map shall be provided for all Master protocols except ‘HSB Master’ and ‘Logic
Master’.
• On pressing OK from Auto-map window, points that can be successfully mapped are
processed and an error message is displayed for those that could not be mapped.

Note: All the other profile parameters will be their default values when auto mapped. User can
modify the row if required.

SYNC 2000, 3000, 4000 Series Software User Manual 96

 21.4 Slave to Slave Mapping
The Slave to Slave mapping feature allows transfer of critical information between two master
stations.

To enable communication between masters, the corresponding source slave should be mapped
to the destination slave. The source slave is the slave which transacts with the master from
which data has to be transferred. The destination slave is the slave which transacts with the
master to which the data has to be transferred. User can add profile and configure command
points under the source slave nodes. These command points can be mapped to input points. A
command received on the source slave will be sent as an event to the mapped destination slave.
Depending on the command type and protocol, a positive acknowledgment will be sent back
to the source slave after sending the event notification. If the command point is not mapped, a
negative acknowledgment will be sent back. For the protocols and specific data types which do
not support event notifications, the data can be retrieved by polling.

Note: Slave-to-Slave mapping does not allow multiple mapping. In addition to this, a single row
can only be mapped to a single node. For example, consider a row with three points. Each of
these three points should be mapped to a single node. Splitting and mapping to different nodes
is not permissible. The quality of the points configured will always be good. The time stamp of
the event will be the time taken from the device when the command is processed.

1. Add slave channels and nodes (source and destination).

2. Add Profile under source Slave and configure Points as shown in Figure (Adding Slave Profile)
below:

Figure 115: Adding Slave Profile

3. Select destination Slave and click on Add Map to add the mapping as shown in Figure (Adding
Slave Profile) above. Modify Map and Delete Map functions are identical to their master-to-slave
mapping counterparts.

SYNC 2000, 3000, 4000 Series Software User Manual 97

 21.5 Ease of Configuration
21.5.1 Copy/Paste
EasyConnect allows the user to copy and paste a device, a channel or a node. Depending on the
protocol, the number of channels/nodes up to which it can be copied varies.

The Copy option is available by right clicking on a device, channel or a node. Consider the case
of copying a node. In order to paste multiple copies of the node under a channel, right click on
the channel and click Paste. Refer to Figure (Copy/Paste option on Right Click) given below:

Figure 116: Copy/Paste option on Right Click

While choosing the paste option by right clicking on device, channel or node, a form pops up
which gives the user an option to enter the number of copies required, as shown in Figure
(Multiple Copies Form) below:

Figure 117: Multiple Copies Form

Copying a device copies all the information under that device including mapping and serial port
settings. Dial up Settings, LAN Settings and SNMP Settings will not be copied.

SYNC 2000, 3000, 4000 Series Software User Manual 98

 21.5.2 Profile Row Options
EasyConnect allows the user to modify, delete a particular row by selecting the corresponding
option by right clicking on that selected row.

A row can only be modified one at a time. The Delete row option is available for multiple selected
rows. A single row or multiple rows can be exported to Excel by selecting single or multiple rows
and right clicking the Export Row/ Rows to Excel option. The Export All to Excel option exports
all the rows in the profile. Refer to Figure (Profile Row Option) given below:

Figure 118: Profile Row Option

21.5.3 Multiple Row Modify Option

This feature allows user to modify properties of multiple rows together in profile and mapping.
User can select the mutliple rows of same basic type in the Profile/Mapping and click on the
“Modify Row/Modify Map” option. In the pop up window, user can tick on the parameters, that
need to be modified and change the values and then click on the “Save” button. This feature
is only applicable to selected parameters in selected protocols. Refer to Figure (Multiple Row
Modify Window) given below.

Figure 119: Multiple Row Modify Window

SYNC 2000, 3000, 4000 Series Software User Manual 99

 21.5.4 Search Option in profile and mapping
It provides an option to search the rows in profile and mapping. There are separate search boxes
for profile and mapping. User can filter the displayed rows by providing a search key word in the
specific search box.

Figure 120: Search Option in Profile and Mapping

Figure 121: Earch Option in Profile Rows.

Figure 122: Search Option in Mapping

SYNC 2000, 3000, 4000 Series Software User Manual 100

 21.5.5 Excel Import/Export
Adding a large number of points to a profile using Add Row button in EasyConnect can be time
consuming. EasyConnect configuration utility allows the user to export profile rows to an Excel
worksheet and import the points from an Excel worksheet to the profile rows. The required points
can be configured in an Excel worksheet and can be imported to the required profile.

Excel export
After adding the required rows in the profile, select Excel Export from the context menu as shown
in Figure (Excel Export and Import) below:

Figure 123: Excel Export and Import

The exported Excel worksheet format is shown in Figure (Excel Profile) below. The worksheet
will contain the protocol name. All the configurable parameters in the Profile Row window of
the specified protocol form individual columns. All the available options for a parameter will be
available in the combo box independent of the type of point selected.

Note: Excel export feature is not supported for communication diagnostic point and 61131 logic
settings.

Figure 124: Excel Profile

SYNC 2000, 3000, 4000 Series Software User Manual 101

 Excel Import:
Select Excel Import from the context menu of profile and choose the Excel worksheet to import.
Refer to Figure (Excel Export and Import).

Certain conditions apply to the Excel Import functionality. Only worksheets previously exported
from EasyConnect can be imported. User should add at least one point (other than communication
diagnostic point) in the profile and use Excel Export to generate an Excel worksheet template.
Configure required points in this file and save. Note that EasyConnect expects a specific format
for the worksheet. Therefore, the user should refrain from modifying the format of the sheet in
any manner. Only the contents may be changed. The protocol name in the Excel worksheet
should match with the protocol of the profile to which it is imported. For example, an Excel
worksheet exported from IEC104 Master can only be imported to a profile under an IEC104
Master Channel. EasyConnect validates all the parameters configured in the Excel worksheet
before importing and will provide an error message if the validation fails. All the available options
for a parameter will be available in the worksheet cells independent of the type of point selected.
For example, in Modbus Master, Function Type ‘Read Coil status’ is not applicable for object type
‘Analog Input’. But this option will be available in the Excel worksheet cell. User should select
valid options while editing the worksheet. Any failure in validation will terminate Excel import.

• After validation, all the existing profile rows will be replaced by the points configured in
theworksheet. For points that are already mapped to a destination protocol.
• For all the rows where the address parameters are not modified, the other parameter
values are read in from the worksheet.
• If the address parameters are changed in the worksheet, EasyConnect will display
a message as shown in the Figure (Excel Import Popup) below. On selecting Yes, the
mapping will be deleted and the points in the worksheet will be imported. On selecting No,
the Excel worksheet will not be imported.

Figure 125: Excel Import Popup

SYNC 2000, 3000, 4000 Series Software User Manual 102

 22
22 Configuring Dialup
The SYNC devices with built-in-modems can be ordered separately. SYNC series can also be
used with external modems.

Configuring Dialup/ Modem:

To configure Dialup/ Modem settings for a device whose configuration has been uploaded in the
configuration window, do the following:

1. Right-click on the Settings node to get the option Add Dialup settings.

Figure 126: Add Dialup

SYNC 2000, 3000, 4000 Series Software User Manual 103

2. Click on Add Dialup. Add Dialup window will be displayed as shown in Figure (Add Dialup
Window). Enter the relevant changes. Refer to below table for parameter names and descriptions.

Figure 127: Add Dialup Window

Parameter Range/Optional Default value Description

name values
Port Com1-Com16 Com1 Gives the valid com port to
which the modem will be
connected
Baud Rate 200,600,1200, 2400, 115200 To set the baud rate according
4800, 9600, 19200, to the modem baud rate
38400, 57600,
115200
Channel Type NA RS -232 Not Editable. Type of channel
used
Data Bits NA 8 Not Editable. Number of data
bits
Stop Bits NA 1 Not Editable. Number of stop
bits

SYNC 2000, 3000, 4000 Series Software User Manual 104

 Parameter Range/Optional Default value Description
name values
Parity NA None Not Editable. Number of parity
bits
Flow Control NA Hardware Not Editable. To prevent
overflow of modem buffer
Channel Mode NA Full-Duplex Not Editable.
Link Type NA GPRS Specifies the link type to be
used
Service *99#, *99***1# *99***1# Universal dialling Number for
Number the given link type
APN Name Depends upon www Access Point Name for a given
service provider service provider
LCP Echo Depends upon 20 Depends upon support from
Interval service provider service provider
LCP Echo Depends upon 3 Depends upon support from
Failure service provider service provider
Packet Enable/Disable Disable Depends upon support from
Compression service provider
Authentication PAP, CHAP, None PAP Type of authentication protocol
type used
Client Name Configure if provided by service
provider. Else use default
values.
Server Name Configure if provided by service
provider. Else use default
values.
Password Configure if provided by service
provider. Else use default
values.
Table 6: Dialup Parameters

SYNC 2000, 3000, 4000 Series Software User Manual 105

3. Download the settings via File Download option and check the option Dialup Settings.

Figure 128: Download

To delete the dialup settings from the configuration window, right click on the Dialup node to get
the Delete option as shown in Figure (Delete Dialup) below. Click on Delete option.

Figure 129: Delete Dialup

SYNC 2000, 3000, 4000 Series Software User Manual 106

To delete the dialup settings from the device, delete the dialup settings from the configuration
window as explained above. Then check the option Dialup settings box in the Download command
window as shown in Figure (Delete Dialup) below and click on Download.

Figure 130: Delete Dialup

SYNC 2000, 3000, 4000 Series Software User Manual 107

 23
23 Configuring VPN
SYNC devices have the option of loading GPRS/ EDGE units (need to be ordered separately)
which allow users to extend the Ethernet over wireless networks. This allows users to connect
and integrate the device to remote locations without any distance limitations. M2M device can
be used with the SYNC devices to enable secure communication and data transfer via public
networks using a Virtual Private Network (VPN) formed by the SYNC device. VPN provides
secure communication between SYNC devices present at different site locations to the single
M2M Gateway present at the central location having fixed public IP. Data between the two nodes
are encrypted before transmission making it highly secure.

The SYNC devices will act as VPN clients and connect to the VPN server (M2M Gateway) using its
public IP. The client and server use secret keys and encryption to establish a secure connection.
Both client and server will validate the supplied credentials before accepting a connection. After
establishing a successful connection, the M2M gateway will assign an IP address to each client
device. The IP address given to the client device can be pre-configured using the EasyConnect
configuration utility. The client can securely communicate with the server using this IP address.
A typical network configuration is shown in Figure (VPN/ GPRS Network With SYNC Devices)
below:

Figure 131: VPN/ GPRS Network With SYNC Devices

SYNC 2000, 3000, 4000 Series Software User Manual 108

Any SYNC device can be part of a VPN network. A private sub-network behind each device can
be accessed through VPN by configuring the private sub-net mask in VPN configuration. There
is also an option to provide multiple servers’ IP addresses for redundancy. Please refer to details
below and in the EasyConnect’s help files.

Configuration:
To configure VPN settings for a device whose configuration has been uploaded in the configuration
window, do the following:

1. Right-click on the Network Design node to get the option Add VPN settings.

Figure 132: Add VPN

SYNC 2000, 3000, 4000 Series Software User Manual 109

2. Click on Add VPN link. A new dialog box will appear as shown in Figure (VPN Pop-Up) below.
Refer to table 5 (VPN Pop-Up) given below for parameter details.

Figure 133: VPN Pop-Up

Parameter Range/ Optional Default value Description

name values
A drop down menu provides
AU, BH, BR, CA, CN,
Country Code IN various country codes. Select the
IN, JP, PK, US
required country code
name of state/
State/Province This field is for entering the state.
province
This field is for entering the city
City city name
location.
This field is for entering the name
Organization Company Name of the
organization.
support@ This field is for entering the e-mail
E-mail ID
kalkitech.com address
Table 7: VPN Pop-Up Details

These parameters are used for certificate generation purposes only and have no other function.

SYNC 2000, 3000, 4000 Series Software User Manual 110

3. Click OK once this is done. A new dialog box will appear as shown in Figure (VNP parameters)
given below. Fill in the required parameters and click Save. Parameter details are explained in
below table Table 6 (VPN Parameters).

Figure 134: VPN parameters

Note: For any VPN configuration, one of the devices is configured as server and the rest of the
devices operate in client mode.

Parameter name Range/ Default value Description

Optional values
It signifies the IP address
Network Address: 10.8.0.0 template/range over which the
VPN IPs can be configured
Subnet Mask 255.255.255.0 A valid subnet address
The UDP port used to establish
Port NA 1194
the VPN connection
Choose the device to set as the
Server Device SS1 Device
VPN Server Device
The LAN/WAN IP of the VPN
Server LAN/WAN IP 0.0.0.0
server chosen above
The VPN IP of the server
Server VPN IP NA 10.8.0.1
allocated by the system.
IP Address of the VPN clients.
This can be generated by
Client VPN IP NA
clicking the button ‘ Auto
Generate VPN IP’.
Table 8: VPN Parameters

SYNC 2000, 3000, 4000 Series Software User Manual 111

4. The VPN settings are saved to the configuration. To download, right-click the VPN node and
click the Download link that appears as shown in Figure (Download VPN) below:

Figure 135: Download VPN

To edit the VPN settings from the configuration window, right click on the VPN node to get the
Edit link as shown in Figure (Edit VPN) below. Click on Edit.

Figure 136: Edit VPN

SYNC 2000, 3000, 4000 Series Software User Manual 112

A Config VPN window appears as shown in Figure (Edit VPN Pop-up)shown below. Make the
required changes and click Save button at the bottom of the window.

Figure 137: Edit VPN Pop-up

To delete the VPN settings from the configuration window, right click on the VPN node to get the
Delete link and then click the Delete button.

Figure 138: Delete VPN

SYNC 2000, 3000, 4000 Series Software User Manual 113

To delete the VPN settings from the devices, delete the VPN settings from the configuration
window as explained above. Then check the VPN settings box in the Download command
window as shown in Figure (Delete VPN) below and click Download.

Figure 139: Delete VPN

Note: If necessary, repeat for each devices configured for the VPN network in the project.

• The SYNC device configured in the VPN network become part of a private encrypted
network. Access to the network is restricted. Under normal circumstances, access to the
VPN network from the workstation in which EasyConnect is installed is not necessary.
So the steps mentioned below are not necessary for normal operation. To access device
that are part of a VPN network, certain system setup procedures need to be completed.
To make EasyConnect a part of the VPN network, install OpenVPN on the workstation in
which EasyConnect is installed. Now right click on the VPN node to get the Export EC cert
files link as shown in Figure (Export VPN Certificates) below. Click on the link and save
the files. Use these files to connect to the VPN network.

Note: Refer to the OpenVPN documentation for more information.

SYNC 2000, 3000, 4000 Series Software User Manual 114

 Figure 140: Export VPN Certificates

• The set of EasyConnect certificates can be used to configure only one instance of Open
VPN client at a time. The EasyConnect workstation and the SYNC device must be time-
synchronized.

Once EasyConnect is a part of the VPN network, the ping status of the devices in VPN mode
can be obtained using the Get Device Status button as shown in Figure (VPN Diagnostics)
below.

Figure 141: VPN Diagnostics

SYNC 2000, 3000, 4000 Series Software User Manual 115

Also there is an option provided in EasyConnect to import VPN certificates to a device by right
click on the VPN Settings on a device as shown in the Figure (Import VPN Certificates) below.

Figure 142: Import VPN Certificates

User can select the certificates that need to be imported and then click on the Import button.

Figure 143: Import VPN Certificate File Selection Window

SYNC 2000, 3000, 4000 Series Software User Manual 116

 24
24 SNMP Configuration
Simple Network Management Protocol (SNMP) is a User Datagram Protocol (UDP) based
network protocol. It helps to manage network-attached devices and ensures that they are not
only up and running but also performing optimally. SNMP exposes management data in the form
of variables on the managed systems. These variables can then be queried or set by managing
applications.

SYNC specific objects managed by SNMP are Model Name, Hardware Information such as
Ethernet Interfaces details, Serial Port details, Memory Usage and Software Information such as
GPC health and DCCP health. Additionally, it is possible to monitor the device database points
by mapping those points to an SNMP Slave channel.

For more details about configuration and features, please refer to the SYNC SNMP slave user
manual.

SYNC 2000, 3000, 4000 Series Software User Manual 117

 25
25 Configuration File Management
25.1 Downloading configuration to device
After creating or editing the configuration file, it has to be downloaded to the SYNC device.
Whenever the configuration file is edited, the firmware has to be stopped and started for the
changes to take effect.

To download the configured and mapped file, do the following steps:

• On the EasyConnect user interface, click Download. The EasyConnect-Download
window will appear.
• Click Download. The file is downloaded to the SYNC device and an appropriate success
message is displayed.

Figure 144: Download Configuration File

SYNC 2000, 3000, 4000 Series Software User Manual 118

 25.2 Saving Configuration File
Click on the Save button or File → Save to save the configured file. The saved file will be in .ecc
format.

The configuration details can be exported and saved in XML format. To do this, right click on
‘Protocol configuration’ in the work space and select ‘Export device config file’ to export the file
as shown in Figure (Export XML file) below. The Save or export option can be used for keeping
the file for future use.

Figure 145: Export XML file

SYNC 2000, 3000, 4000 Series Software User Manual 119

The .ecc file format can be opened directly while using the EasyConnect application. But the
xml file has to be imported into EasyConnect to be used again. To import, right click on Devices
in the work space, and select Import device config file to import the file as shown in the Figure
(Import XML file) given below:

Figure 146: Import XML file

SYNC 2000, 3000, 4000 Series Software User Manual 120

 25.3 File Revision
25.3.1 Save to Revision
The current working configuration version of a particular SYNC device can be saved and stored
to an internal repository. This allows the user to revert the device configuration back to the saved
revision if needed at a later point of time.

To do this, right click on Protocol configuration in the work space, and select Save to Revision to
save the configuration as shown in Figure (Save to Revision) given below.

Figure 147: Save to Revision

An option to enter a revision name is provided as shown in Figure (Revision Name) given
below.

Figure 148: Revision Name

Up to 10 versions of a file configuration can be saved.

SYNC 2000, 3000, 4000 Series Software User Manual 121

 25.3.2 Load from Revision
To load a saved device configuration, right click on Protocol configuration in the work space and
select Load from Revision to load the configuration as shown in the Figure (Load From Revision)
below.

Figure 149: Load from Revision

A list of all the saved revisions is displayed as shown in Figure (Revision List) and the revision
to be loaded can be selected.

Figure 150: Revision List

The present configuration will be replaced with the selected version.

SYNC 2000, 3000, 4000 Series Software User Manual 122

 26
26 Network Configuration
26.1 Setting device IP
To change the IP address settings of a SYNC device, create the device by right clicking on
Devices in the tree-view, then click ‘Add device’, and select the required device. This can also be
done by selecting the device from the Device configuration window.

Click on the device name that appears and then click the icon called ‘IP configuration’ as shown
in Figure (IP configuration) below:

Figure 151: IP configuration

A device specific pop-up appears, based on the number of interfaces available, where the current
IP address of the device to connect to, is entered. Enter the new IP configuration and click OK. If
the device supports Ethernet port redundancy, a ‘Teaming Configuration’ will appear in the LAN
settings window.

26.2 Ethernet redundancy

To protect against a network failure while using Industrial Ethernet, users are seeking cabling
topologies that remain functional under a single cable loss. There are three popular redundancy
schemes for Ethernet: Network Bonding (Trunking/Teaming/Bonding), Parallel Redundancy
Protocol (PRP) and High availability seamless redundancy (HSR) [Both PRP and HSR are
Standardized by the International Electrotechnical Commission, Geneva, as IEC 62439-3, PRP
& HSR are also included under Edition-2 of IEC61850 standard as a way to achieve network
redundancy]. All the three methodologies work on the principle of how quickly an alternative

SYNC 2000, 3000, 4000 Series Software User Manual 123

network can be deployed to recover from the network failures. As Parallel Redundancy Protocol
(PRP) and High availability seamless redundancy (HSR), continuously send packets on through
alternate networks, it offers zero millisecond network recovery. Protocols such as Modbus/
TCP,IEC61850 rely upon the TCP/IP suite of transport-layer protocols and above redundancy
mechanisms works on MAC layer, and so independent of application layer protocol This feature
is device specific and supported by SYNC3000S12R6, SYNC3000S12R4, SYNC3000S12R2,
SYNC3000S12R2F2 and SYNC3000S12R4F1.

• Teaming or Network Bonding

This redundancy approach can be used in any network topology but instead of having one path
between switches, two or more parallel paths are used. These multiple paths are called a trunk
group and function as one redundant channel. SYNC device supports Active-Passive method of
NIC bonding in which only one NIC will be active while another NIC is asleep. If the active NIC
goes down, another NIC becomes active. Trunk groups are not restricted to just two paths and
more can be added to increase redundancy. It is very easy to understand and to configure SYNC
devices for trunking. Recovery time from a cable fault is extremely fast as the switches divert
traffic to functioning link.

Figure 152a: Network Bonding

The disadvantage of using trunking is that it requires the installation of additional cable. Depending
upon the size of the trunk group, cable requirements can double or could force the purchase of
larger switches. Also this type of redundancy only provides link redundancy and will not ensure
complete path redundancy.

• Parallel Redundancy Protocol (PRP)

The Parallel Redundancy Protocol (PRP) follows a different approach from the well-known
reconfiguration protocols like M RP, RSTP etc. It makes use of two independent Ethernet networks.
Frames are replicated by the sending node and transmitted over both networks. Duplicates are
discarded by the receiving node. There is no distinction between a working and a backup path.
This scheme works without explicit reconfiguration and therefore switchover does not show a
period of unavailability (zero millisecond network recovery). PRP redundant node is attached to
two similar LANs of arbitrary topology, which are disjoint and operated in parallel. The LANs must
be laid out so that the two LANs fail independently e.g. redundant LANs must not be powered
out of the same source. No direct connection can be made between the two LANs. These two
networks may have the identical structure or may differ in their topology and/or performance.

SYNC 2000, 3000, 4000 Series Software User Manual 124

 Figure 116b: PRP network

• High-availability seamless redundancy (HSR)

High availability seamless redundancy (HSR) is a further development of the PRP approach.
While retaining the PRP property of zero recovery time, that is applicable to any topology. HSR in
particular is applicable only to rings and rings of rings topology. It makes use of two independent
Ethernet networks as in PRP. Frames are replicated by the sending node and transmitted over
both networks. Duplicates are discarded by the receiving node, but this is limited to rings and
rings of rings network topology and reduces overall cost of wiring.

Figure 116c: HSR network

SYNC 2000, 3000, 4000 Series Software User Manual 125

 26.3 Configuring Redundant Interfaces
Redundant Ethernet interface can be configured for Ethernet port redundancy. Two or more
physical network interfaces are aggregated, which then presents a virtual interface (teaming or
bonding interface, HSR,PRP interface) to the operating system. Click on Configure Redundancy
as shown in Figure (IP configuration Window) below.

Select the interfaces that should be included in the redundant interface and right click on selected
interfaces and then click on either ‘Add HSR/Add PRP / Add Teaming’ as shown in Figure
(Redundancy Configuration) shown below. A new interface called ‘bondX/prpX/hsrX’ will appear
under ‘Redundant Interfaces’ view. Enter the IP address, the subnet mask and the default device
required for the new interface and then click OK.

Figure 153: IP configuration Window

Figure 154: Redundancy Configuration

SYNC 2000, 3000, 4000 Series Software User Manual 126

When the IP configuration is applied and the device is restarted, the new IP configuration will
take effect. For example, in the above case, eth2 ((port 1) and eth3 (port 2) of the device are
bonded as prp0. Now individual interface IP addresses involved in teaming, eth2 and eth3 in this
case, will not be reachable. Instead, the device is reachable through either physical interface
or by a common prp0 IP address. The MAC address of link aggregated interface will be MAC
address of first selected interface in redundant configuration window.

So both port 1 and port 2 will have the same IP address, and the device can communicate using
this IP address if at least one of these ports is connected to the network.

Note:
• The NIC Teaming/Bonding, HSR, PRP interface configured with eth4 will not detect the
HSB link failure in eth4.
• If eth0 is involved in HSR redundancy, the HSR interface MAC address will be of eth0
• If eth0 is involved in PRP redundancy, the PRP interface MAC address will be of other
interface

26.4 NAT Policy Settings

Network Address Translation (NAT) is the process of modifying IP address information in IPv4
headers while in transit across a traffic routing device. Translation options provided include SNAT
(Source Network Address Translation) and DNAT (Destination Network Address Translation).
This feature is device specific and not all devices may support it.

To configure NAT Policy settings for a device whose configuration has been uploaded in the
configuration window, right-click on the ‘Network’ node under ‘Settings’ to get the link for adding
NAT Policy settings as shown in Figure (Add NAT Policies) below. Click on the ‘Add NAT Policies’
link.

Figure 155: Add NAT Policies

Note: On addition of NAT Policies, the Network node parameter ‘Enable IP Forwarding’ will be
set to True.

SYNC 2000, 3000, 4000 Series Software User Manual 127

 26.4.1 To add NAT Rules
Click on ‘Add Rule’ as shown in Figure (Add NAT Rule) below.

Figure 156: Add NAT Rule

A window appears as shown in Figure (Add NAT Rule pop-up) shown below. Enter the parameter
values.

Figure 157: Add NAT Rule pop-up

SYNC 2000, 3000, 4000 Series Software User Manual 128

NAT Rule parameters are explained in table 7 (NAT Parameters) given below:

Parameter name Range/ Optional Description

values
Source Translation, Type of
Type Destination Translation
Translation
Represents the IP address of
the source, if Type is ‘Source
Translation’.
IP Address 0.0.0.0
Represents the IP address of the
destination, if Type is ‘Destination
Translation’.
Represents the IP address to
which the source is translated, if
Type is ‘Source Translation’.
Translated IP Address 0.0.0.0
Represents the IP address to
which the destination is translated,
if Type is ‘Destination Translation’.
Table 9: NAT parameters

Check the ‘NAT Policies’ settings box in the Download window as shown in Figure (Download
NAT settings) given below and then click ‘Download’ button.

Figure 158: Download NAT settings

SYNC 2000, 3000, 4000 Series Software User Manual 129

 26.4.2 To edit NAT Rules
Select a Rule and click on Modify Rules button as shown in Figure (Edit NAT rule) given below.
The Modify Rules window will be displayed. The parameter values can be modified. Click OK to
save Rule.

Figure 159: Edit NAT rules

26.4.3 To delete a NAT Rule

Select the Rule to be deleted and click on the Delete Rule button as shown in Figure (Delete NAT
Rules) given below.

Figure 160: Delete NAT rules

SYNC 2000, 3000, 4000 Series Software User Manual 130

 26.4.4 To delete NAT Policy Settings
To delete the NAT Policies settings from the configuration window, right click on the “NAT Policies”
node to get the Delete link as shown in Figure (Delete NAT policy settings) given below. Click on
the Delete link.

Figure 161: Delete NAT policy settings

To delete the NAT Policies settings from the device, delete the NAT Policies settings from the
configuration window as explained above. Then check the NAT Policies settings box in the
Download window as shown in figure (Delete NAT policy settings) and click ‘Delete’.

26.5 Routing Configuration

Provision to add multiple routes in the device. User can configure networks, gateway, matrix
settings and all other settings available with ‘route’ command of linux from EasyConnect

Parameter Name Range Default Value Description

Target Host / Network Host The destination is
network or host
Host IP Configurable IP 0.0.0.0 Host IP, if the "Target"is
Range a host.
Netmask Configurable network 0.0.0.0 The "Netmask "to be
Range for configured used when adding a
IP network route.
Gateway Configurable IP 0.0.0.0 The "Gateway"
Range through which packets
are routed.
Metric 0 - 255 0 To set the metric field
in the routing table
Device Available interfaces NA The specified device
are listed. to which the route is
associated.
Reject Yes/No No Install a blocking
route, which will force
a route lookup to fail.

SYNC 2000, 3000, 4000 Series Software User Manual 131

I) Get Current Routing Table:
• Click on settings->Routing Configuration.

Figure 162: Route Configuration Menu

• A pop up window as shown in figure will be displayed. Specify the ip address of the device
of which Routing table is to be obtained.
• Click on OK

Figure 163: Retrieve Route Configuration

Figure 164: Route Table

SYNC 2000, 3000, 4000 Series Software User Manual 132

II) Add/Modify Routing Table:
Easyconnect provides option to Add / Modify Routing table.

Add Routing Table

• Get routing table as described in section1.
• Click on Add (Refer Figure). Configure the parameters coming in the pop up window and
click on Save button.
• Click on Save button

Figure 165: Add Route

III) Modify Routing Table

Easyconnect provides option to delete an already added route from the device.
• Get routing table as described in section1
• Click on Modify (Refer Figure)
• Click on Save button

Figure 166: Modify Route

SYNC 2000, 3000, 4000 Series Software User Manual 133

IV) Delete Routing Table:
Easyconnect provides option to delete an already added route from the device
• Get routing table as described in section1
• Click on Delete (Refer Figure)
• Click on Save button

Figure 167: Delete Route

26.6 Ethernet Packet Capture

Ethernet Packet Capture is used to capture the ethernet packets on SYNC Ethernet ports which
can be analyzed using packet analyzer tools like Wireshark. The capture will be stored in a
volatile memory.

1) For a device outside the project context:

Specify the IP address and select the device name as “Other Device”of the gateway for which
Ethernet Packet Capture is to be applied. Specify the appropriate device type (Example:
SYNC3000).Refer Figure.

Figure 168: Ethernet Packet Capture Menu of Configured Device

SYNC 2000, 3000, 4000 Series Software User Manual 134

2) For a device in a project context:
Specify the IP address and the device name (Example: SS1, SS2 etc) of the gateway in which
the Ethernet Packet Capture is to be applied. Refer Figure.

Figure 169: Ethernet Packet Capture For Non configured Device

Supported Options
----------------------
• Start Capture
Start Capture is used to configure and start packet capturing on a particular ethernet port of
SYNC device. The size of the file (in KB) and the capture period (in Seconds) needs to be
provided while enabling packet capture. If the packet capture size exceeds the limit, the older
packets will be discarded and the new packets will be added to the capture file.There are two
modes available for start capture.

Auto Mode: This mode enables to capture the packets automatically from the start up of the
SYNC device. Capture period is not relevant in this mode.

Manual Mode: This mode enabled to start the packet capture on demand. Ie, the capture will
not be started after a restart of the device. The capture has to be started manually from Easy
Connect when required. The capture will be stopped after the capture period is expired.

• Stop Capture
Stop Capture is used to stop the current running packet capture of SYNC for the selected ethernet
port. The capture can be stopped irrespective of the capture mode configured.

• Retrieve File.
Using Retrieve File, user can collect the capture file from the device and save it to the desired
location in PC. The capture must be stopped in order to retrieve the capture file for the particular
ethernet port.

Note: Firmware version Requirement: GPC (3.0.0 or above) and DCCP (3.0.0 or above).Time
Synchronization Parameters

SYNC 2000, 3000, 4000 Series Software User Manual 135

 27
27 Redundancy Configuration
This section describes how redundancy is implemented using the SYNC series of devices.

27.1 Introduction
The SYNC 2000-3000-4011 series offers several options that provide redundancy support. This
section outlines these options one by one. Usage will be described with the help of diagrams and
use cases will show how a combination of options can be used to create reliable communication
systems.

The redundancy mechanism consists of a hot device and a warm device. The hot device polls
the devices and communicates with the control center as if it is a stand-alone system. The
hot and warm devices communicate with each other through an integrated link. Integrated link
options supported by SYNC devices include Serial, TCP, Serial / TCP and Dual TCP links. Out of
these integrated link mechanisms, the latter two provide redundancy support for the integrated
link as well.

27.2 Types of Switchover

SYNC device support the following types of switchover:
27.2.1 External Trigger Switchover

Figure 170: Switchover Due To External Trigger

In this mode, the device will not take a switchover decision on its own. The switchover is triggered
by an explicit command received from an external master. To assist in making a decision, the
external master can monitor the device status via some default status points. Based on this
information, the external master can change the state of the device.

SYNC 2000, 3000, 4000 Series Software User Manual 136

 27.2.2 Self Switchover

Figure 171: Self Switchover

Self switchover mechanisms extend the functionality of external trigger switchover by providing
for a switchover decision to be made from the device itself. Device monitors the status of all
the connected channels, as well as the status of the other device (via an integrated link). In
this mode, when the warm device detects a failure of the hot device, it changes its state to hot.
Moreover, a communication failure in active channels of the hot device will result in the warm
device switching to hot.

Note: In the case of serial communication channels, the channel is declared as inactive when all
the nodes under a channel are found to be not working when scanned from first node.

27.3 IP Switching mechanisms

The devices involved in a Hot-Standby configuration support the following IP switching
mechanisms during a switchover. These mechanisms can be configured independently for each
of the available Ethernet interfaces device.
27.3.1 IP Swapping
In this mode, besides the normal IP address, the hot and warm devices share two public IP
addresses on an alias interface. At any specific time, the address which is assigned on the
alias interface depends on the state of the device. Due to this, the control center can connect
to the hot device using a fixed address. This ensures that no special network configuration is
needed at the control center. When the control center connects to the hot IP-address, it will always
connect to the hot device. The warm device can also be accessed with its public IP address for
maintenance purposes.

SYNC 2000, 3000, 4000 Series Software User Manual 137

 Figure 172: Redundant Configuration with IP Swapping

27.3.2 No IP Switching

Figure 173: Redundant Configuration with No IP Switching

In this configuration, each device has its own private IP address only. This will require a special
network configuration on the part of the control center. The control center needs to detect the hot
device and ensure that the correct device is being connected after a switchover.

27.4 Redundancy Requirements

To support redundancy, one of the devices must be configured to have the higher priority. This
will ensure that the device with the higher priority is hot when:
a. There are no error conditions
b. Both the devices have the same channel health.

In all other cases, the hot device is determined based on the health of each device.
• Basic switchover condition is indicated when the hot device has a hardware/software
failure
• All serial links are made through Y-cables
• It is possible to force a switchover
• Both devices should have the same hardware configuration. The software configuration

SYNC 2000, 3000, 4000 Series Software User Manual 138

 should be the same with minor changes in configuration file.
• It is mandatory to have a dedicated link between the two devices involved in redundant
configuration. It is preferable to select an Ethernet link as the dedicated link between the
two devices because of the speed offered by the medium.
• Protocol timeouts need to be adjusted to avoid unnecessary switchover
• If more than one TCP channel is configured in one interface, and if both devices are not
able to communicate through that interface (Ethernet cable removal), then an additional
switchover will happen.
• Starting/stopping firmware is not recommended for the proper functioning of Hot Standby
(HSB) protocol. Therefore, if there is any configuration change, both devices need to be
restarted, and in this case, the Main device needs to be restarted first.

27.5 Device Redundancy Information and Control

When the SYNC devices are placed in a redundant configuration, status information is added to
the device database. This information can be accessed by the control center.

The following information is provided for devices in a redundancy configuration:

• ID: The ID of the connected device. This shows whether the device is configured as Main
or Standby.
• Status: The Status of the connected device. This shows whether the device is currently
working as hot or standby.
• IL Communication Status: The current communication status of the integrated link. It
shows whether or not the remote device is communicating via the integrated link.
• Health: Shows the health information of different channels of the device.
• Remote status: The status of the remote device. This shows whether the
remote device is currently working as hot or standby. This information is only valid if the IL
communication status indicates that the device is on-line.

Besides the above, the SYNC device with redundancy support has the following
command point for triggering switchover from an external Master.

External Trigger Point: this command point is used to give the switchover command to the
device from an external Master.

27.6 Hot-Standby protocol

The Hot-Standby (HSB) protocol is used to maintain complete up-to-date database information
on the warm device. This feature will copy the internal database of the hot device to the warm
device. Also, all the events received by the hot device are mirrored in the warm device.

The following points should be noted while implementing a redundant configuration with SYNC
devices using HSB protocol:
• Not all masters currently support this feature.
• Not all slaves currently support this feature.
• Not all automation functions currently support this feature.
27.6.1 Configuration of Hot-Standby
Redundancy can be configured for the SYNC 2000-3000-4011 product series by adding a “HSB
Master” channel using EasyConnect. One of the devices is configured as Main, and the other as
Standby.

SYNC 2000, 3000, 4000 Series Software User Manual 139

 27.6.2 Channel Configuration
When the user adds a new HSB channel to the configuration using EasyConnect, the window as
shown in Figure (Channel Configuration for Achieving Redundancy) is displayed when the user clicks
on “Channel-n HSB Master”. This corresponds to the channel parameters of HSB Master.

Figure 174: Channel Configuration for Achieving Redundancy

The following Table 8 describes each of the configurable options for the Channel parameters:

SL Name Description Range Required Value

No:
Used to enable or disable Should be configured as
1 Channel State Enable/ Disable
the channel “Enable”
Serial / TCP-IP
Used to configure the type
/ Dual / Dual Dual Serial mode is
2 Physical Link of link used for integrated
Ethernet / Dual currently not supported.
link.
Serial
RS 232 / RS 485 /
3 Serial Type Serial port type
RS 422
Mode in which the serial Full Duplex / Half
4 Serial Mode
port communicates Duplex
Name of the port
5 Com Port Name through which serial COM1 - COM16
communication happens
Name of the port which Should have a different
Redundant Com
6 provides a redundant link COM1-COM16 value from #5
Port Name
to #5
An integral value Should be one of the
Serial communication should be following recommended
7 Baud Rate
parameter provided as baud values:
rate

SYNC 2000, 3000, 4000 Series Software User Manual 140

 SL Name Description Range Required Value
No:
Odd / Even /
8 Parity “
None
9 Data Bits “ 7 or 8
10 Stop Bits “ 1 or 2
None / Software/
11 Flow Control “
Hardware
IP address of the other
Any valid class-
12 IP Address device for TCP-IP/Dual/
A/B/C IP address
Dual-Ethernet links
IP address of the
Redundant IP redundant TCP link of Any valid class-
13
Address other device for A/B/C IP address
Dual-Ether-net link
IP address of the Main
device’s integrity link
Integrated IP interface. Any valid class-
14
Address – Main A/B/C IP address
Note: Valid if Physical Link
selected is TCP-IP
IP address of the Standby
device’s integrity link
Integrated IP
interface. Any valid class-
15 Address –
A/B/C IP address
Standby
Note: Valid if Physical Link
selected is TCP-IP
Port number used for Recommended value is
accepting incoming TCP Any valid port 3000
16 Port Number
connections on Main number
device
The timeout for reading/
17 Select Timeout 1 - 10000
writing to the TCP port
Number of times a HSB Default value 2
link packet is re-sent, in
18 Channel Retry 1 - 10
case of failure to get an
acknowledgement
Response timeout
Response in milliseconds for
19 500 - 5000
Timeout HSB messages with
acknowledgment.
Time interval in
seconds in which a non-
Offline Poll
20 communicating device is 0 - 60
Period
probed to check whether it
is alive or not
Response timeout
Channel
in milliseconds for
21 Establishment 500 - 5000
HSB messages with
Timeout
acknowledgment.
Table 10: Channel Configuration Parameters for Achieving Redundancy

SYNC 2000, 3000, 4000 Series Software User Manual 141

 27.6.3 Node Configuration
After the HSB channel is configured, a node needs to be added under that channel. The window
shown in Figure (General Node Configuration for HSB) is displayed when the user clicks on
“Node_1”. This corresponds to the general node parameters of HSB Master.

Figure 175: General Node Configuration for HSB

The following Table 9 (General Node Parameters) describes each of the configurable options for
the node parameters:

SL Name Description Range Required Value

No:
One device should
be Main and the
Used to determine whether other device should
Main /
1 HSB Type the device is Main or be Standby always.
Standby
Standby Failure to do so will
result in redundancy
not working properly.
External
Switchover Switchover type for the
2 triggered /
Type device
Self

SYNC 2000, 3000, 4000 Series Software User Manual 142

 SL Name Description Range Required Value
No:
The switchover
time in case of an
integrated link failure
Time interval in seconds, in is determined by
Heartbeat which each device sends (Heartbeat Interval *
3 1 - 60
Interval a keep-alive message to (Maximum Heartbeat
other one. Failure + 1)). So, these
values should be
designed optimally to
suit the application.
The maximum number of
heartbeat failures which
Maximum Recommended values:
are tolerated by each
4 Heartbeat 1-5 TCP-IP/Serial – 1 Dual
device, before changing
Failure links – 2
the other device's status to
offline
If configured, HSB
will set the configured
alias interface as the
Default
No change, default device. If not
5 Gateway No change
eth0:0- ethx:0 configured, change
Interface
HSB will not do
anything on default
device
Default
Configure the address
6 Gateway NA 0.0.0.0
of default device
Address
Diagnostic Enable diagnostic point Enable /
7
Point Event events Disable
Status
Enable status change Enable /
8 Change
events Disable
Event
ARP Interval ARP messages will be
9 10 0-1000
(0 - 1000sec) sent in this interval.
Table 11: General Node Parameters

SYNC 2000, 3000, 4000 Series Software User Manual 143

The IP switching parameters have to be configured under the “IP Switching” tab. Clicking on this
tab, will display the following window as shown in Figure (IP Switching Configuration for HSB)
given below:

Figure 176: IP Switching Configuration for HSB

Each interface can be configured independently for IP switching. Select the interface and click the
“Edit Interface” button to bring up the following window as shown in Figure (Configure Individual
Interface for IP Switching) below. If the device supports teaming interfaces, those interfaces will
also be listed in this window. If IP switching is enabled for a teamed interface, IP switch-over is
considered if all individual ports included in the teaming interface fail.

Figure 177: Configure Individual Interface for IP Switching

SYNC 2000, 3000, 4000 Series Software User Manual 144

The following Table 10 (IP Switching Configuration Parameters) describes each of the configurable
options inside the IP switching configuration window:

SL No: Name Description Range Required

Value
Interface name for which the
1 Interface - Non-editable
configuration is applicable
Used to enable the IP
2 IP Switching switching mechanism for the Enable/ Disable
interface
Alias IP address of the
Hot IP Any valid class-
3 interface when the device is
Address A/B/C IP address
hot.
Valid Subnet
Subnet mask for the
range for
4 Hot Subnet interface when the device is
configured IP
hot.
address
Alias IP address of the
Warm IP Any valid class-
5 interface when the device is
Address A/B/C IP address
warm.
Valid Subnet
Subnet mask for the
Warm range for
6 interface when the device is
Subnet configured IP
warm
address
Table 12: IP Switching Configuration Parameters

The following Table 11 (Profile Configuration Details for Redundancy) lists the status points and
command points supported by the HSB master. With these points, the user can monitor the status
of both devices and issue external switchover commands to the device. Any of these points can
be added under a HSB profile.

Sl No: Name Description Type Required

Value
0 → Main
Used to determine Device
Binary Input /
1 ID whether the device is 1 → Standby
Analog Input
Main or Standby Device

Used to determine 0 → Warm

Binary Input /
2 State whether the device is 1 → Hot
Analog Input
currently Hot or Warm
0 → Switch to
External Trigger Used to give Switchover Binary Output / Warm
3
Point command to the device Analog Output 1 → Switch to Hot

Status point showing 0 → Offline

IL Communication Binary Input /
4 whether the other device 1 → Online
Status Analog Input
is Online or Offline

SYNC 2000, 3000, 4000 Series Software User Manual 145

 Sl No: Name Description Type Required
Value
Bit 0 → Unused
Shows the health of the Bit 1 → Channel 1
5 Health channels running inside Analog Input ….
the device. Bit 15 →
Channel 15
Used to determine 0 → Warm
Binary Input /
6 State whether the other device 1 → Hot
Analog Input
is currently Hot or Warm
Table 13: Profile Configuration Details for Redundancy

Table 14: Redundancy Switchover Details

SYNC 2000, 3000, 4000 Series Software User Manual 146

 27.6.4 Redundancy Switchover Details
The below table describes failure possibilities and subsequent operations performed by the two
devices configured in a redundancy network. G/W A and G/W B describes the status of the two
devices on failure annunciation.
27.6.5 HSB Configuration Easiness
An option is provided in the configuration download window to download the hsb HSB configuration
to both main and stand by IP at the same time. The configuration gets downloaded in to the main
device with hsb HSB type in the HSB node configured as “Main” and the same gets downloaded
in to the standby device with hsb HSB type in the HSB node configured as “Standby”.

Figure 178: HSB Configuration Easiness Change in download window.

SYNC 2000, 3000, 4000 Series Software User Manual 147

 28
28 NERC-CIP Support
NERC-CIP compliance is available as an option with SYNC 2000 and, SYNC 3000
series of devices. For NERC CIP Compliant devices, only the ports and services
essential for normal and emergency operations are enabled by default. Event logging is provided
in devices for all user actions through EasyConnect and web-server. These logs are kept for at
least 90 days and can be retrieved using EasyConnect. Older logs will be automatically deleted
from the device.

Note: Gateway Access Logs can be retrieved using EasyConenct. For details, refer section
18.Gateway Log ->Gateway Access Log.

A web server is available along with the NERC-CIP feature through which it is possible to access
and perform basic EasyConnect functions through a web client, as long as it is connected to the
network. Using Web Server, the user can control the SYNC series of protocol gateways.

A client, commonly a web browser such as Mozilla Firefox, initiates communication by making a
request for a specific resource using HTTP. The server responds with the login page shown in
figure (Login page) given below. To login, type the username and password in the fields provided
and then click the Login button. The default username and password will be ‘root’ and ‘pass123’
respectively.

Figure 179: Login page

After the login is validated, the Home page as shown in figure (Home Page) appears. Functions
supported by the Web Server will be listed on the left hand side pane of the home page. For
more details, please refer the SYNC - WebServer User Manual.

SYNC 2000, 3000, 4000 Series Software User Manual 148

 Figure 180: Home page

Note: To access SYNC configuration through a web browser, cookies must be enabled in the
web browser and the browser should support Java Script.

SYNC 2000, 3000, 4000 Series Software User Manual 149

 29
29 File Transfer Support
SYNC2000 and SYNC3000 series devices support uploading and downloading of files through
File Transfer channel if they are supported by the firmware.

File transfer is done by configuring a File Transfer Master/Slave channel through EasyConnect.
File transfer master channel is able to connect with FTP/SFTP server programs running on a given
remote system and can upload/download files and folders.

File transfer master configuration includes a schedule and file/folder details.

File transfer slave will setup FTP/SFTP sever inside the device to which FTP/SFTP clients can
connect. There is a folder size limiting functionality implemented for these protocols which helps
in keeping the folders to a maximum size limit.

Following is a brief description of the steps involved in configuring a File Transfer Master/Slave
channel in EasyConnect.

29.1 Configuring File Transfer Client Channel

The steps for configuring File Transfer Master channel are as follows:
• Choose File Transfer Client from Add Channel menu in Protocol Configuration
• Type Remote IP Address in which FTP/SFTP server is running
• Select Protocol Supported and type Port No in the corresponding fields.
• Now right click on the File Transfer Client channel and choose the option Add Station.
• In the General tab of node parameters, select Authentication Scheme, type user name,
password and type the Connection Timeout.
• In Scheduled Transfer tab, add a schedule by specifying the time period for the scheduled
transfer to run, as shown in Figure (Add Schedule). As many schedules as required can
be added.
• Now click on the schedule under which a transfer task is to be added. Add a new transfer
by specifying the transfer details as shown in Figure (Add transfer task).

Figure 181: Add Schedule

SYNC 2000, 3000, 4000 Series Software User Manual 150

 Figure 182: Add Transfer Task

29.2 Configuring File Transfer Server Channel

The steps for configuring file transfer slave are as follows:
• Choose File Transfer Server from Add Channel menu in Protocol Configuration
• Select Protocol Supported, type Listen Port and Inactivity Time Period in the corresponding
fields.
• Now right click on the File Transfer Server channel and choose the option Add Station.
• In the General tab of node parameters, select Authentication Scheme.
• In the Users List tab, add users by specifying User name and Password as shown in
Figure (Add User). The remote clients can use them for password authentication.
• In the Size Limit tab, add a schedule for running size limiter by specifying the time period
as shown in Figure (Add Schedule). As many schedules as required can be added. Now
click on the schedule and add folder by specifying the Folder Name and Rollover Limit as
shown in Figure (Add Folder). The size of the specified folder will be checked and limited
to the rollover limit in the scheduled interval.

Figure 183: Add User

SYNC 2000, 3000, 4000 Series Software User Manual 151

 Figure 184: Add Schedule

Figure 185: Add Folder

SYNC 2000, 3000, 4000 Series Software User Manual 152

 30
30 Parameterization through Pass-Through
(Transparent) Channel
This module in the SYNC devices enables parameterization of the relays or IEDs with the
respective configuration software. The transparent channel (pass-through) routes the frames
directly from the input (server) port to the output (client) port and in the reverse direction. The
Transparent Peer protocol can be associated with, any of the serial communication ports of the
SYNC device or a TCP/IP client port. The SYNC models must be loaded with the license and
firmware supporting Transparent Peer interface module, and the configuration file containing
all the specific information for the communication. The detailed block diagram is shown in the
Figure (Parameterization through Transparent Channel) below:

Figure 186: Parameterization through Transparent Channel

SYNC 2000, 3000, 4000 Series Software User Manual 153

 31
31 Encryption Support
Encryption is used to secure data and to protect the integrity and authenticity of a message. The
communication channels used by a master or a slave device can be secured, provided the end
device also supports the encryption method.

Encryption support is provided in the SYNC 2000 and SYNC 3000 S4R2, S16R4, S16R4I
models. To enable encryption, the parameter ‘Enable Encryption’ has to be set to ‘True’ under
the channel or node where communication is being established, as shown in Figure (Enabling
Encryption in TCP Channels) given below.

Figure 187: Enabling Encryption in TCP Channels

Encryption is supported for TCP channels only. Currently the following protocols are
supported:
• IEC 104 Master and Slave
• DNP TCP Master and Slave
• Modbus TCP Master and Slave

In the case of master protocols, the option to enable or disable encryption is available under
its node parameters if the configuration type is ‘TCP’ in its corresponding channel. For the
configuration type ‘TCP_MULTIDROP’, the encryption option will be available under channel
parameters. Please refer to protocol help documents for more information on configuration type.

SYNC 2000, 3000, 4000 Series Software User Manual 154

 Certificates Window
When Enable Encryption parameter in channel/ node is selected as True, the window as shown
in Figure (Certificates Window) appears, in which the cipher suite is selected and certificates
used for communication are loaded. If the parameter was already ‘True’, then this window can be
accessed by right clicking on the channel/ node and selecting Modify TLS settings.

Figure 188: Certificates Window

Cipher Suites
A cipher suite can be selected which determines the algorithms used for server/client authentication,
key-exchange, encryption and message authentication. Both client and server should have the
same cipher suite selected. Currently the following cipher suites are supported:
• TLS_RSA_WITH_3DES_EDE_CBC_SHA
• TLS_RSA_WITH_RC4_128_SHA
• TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
• TLS_DH_ANON_WITH_AES_256_CBC_SHA

Note: Default encryption can be chosen for the server/client in which the best cipher available
and supported by the connection is selected. This option will not work if the corresponding
client/server is using an anonymous Diffie-Hellman cipher suite like TLS_DH_ANON_WITH_
AES_256_CBC_SHA.

SSL certificates
For SSL based communication, the end devices should have SSL certificates loaded, which are
signed by a third-party Certificate Authority(CA). The required certificates can be imported to the
device configuration using the Import wizard.

The other option is to generate SSL certificates for both the devices. EasyConnect will generate
two sets of certificates (certificate + private key pairs) signed by a local CA.

SYNC 2000, 3000, 4000 Series Software User Manual 155

 Import:
If Import option is selected, the following wizard appears as shown in Figure (Import Window),
where the required files can be imported.

Figure 189: Import Window

Note: Depending on the cipher suite selected, it may not be necessary to import all four files. For
example, only DH Parameters file is required to communicate with an anonymous cipher using
Diffie-Hellman key exchange.

SYNC 2000, 3000, 4000 Series Software User Manual 156

 Generate:
The certificates can be generated using the generate wizard as shown in Figure (Generate
Certificates) given below. In this case, two sets of certificates are generated -, one for the device
and another set of certificates for the device it is communicating with. After generation, the
certificates for the external device can be exported using the Export wizard. Multiple external
device certificates can be exported at once by right clicking on ‘Protocol Configuration’ and
selecting Export TLS certificates.

A unique common name field should be specified. Once generated, two sets of the following files
are created: CA, certificate, private key and DH parameters file. Optionally, the private key to be
generated can be encrypted by specifying a password. Then this password will be required for
using the key.

Figure 190: Generate Certificates

SYNC 2000, 3000, 4000 Series Software User Manual 157

 Downloading TLS settings:
Finally the certificates are downloaded to the SYNC device, along with other protocol
configuration details, by selecting the TLS Credentials option in the download window as shown
in Figure (Download LTS Settings) given below

Figure 191: Download TLS Settings

SYNC 2000, 3000, 4000 Series Software User Manual 158

 32
32 Data Monitoring
SYNC Database Monitor is an option to view the internal data of the SYNC devices. It is provided
as an online database monitoring facility within EasyConnect. It displays the data along with its
value, quality and time stamp.

Note: The TCP port number 64727 is used for SYNC DB communication.

The firmware recommended for SYNC DB is GPC (2.19.0 or above) and DCCP (2.13.0 or above).

To enable SYNC DB Monitor, set the Enable SYNC DB Monitor option to True in device
configuration and download the configuration to the SYNC device. Refer Figure (Enabling SYNC
DB Monitor) given below:

Figure 192: Enabling SYNC DB Monitor

Then select a SYNC device and launch the SYNC DB Monitor by clicking the SYNC DB Monitor
button provided on the toolbar as shown in Figure (SYNC DB Monitor Icon in EasyConnect
Toolbar) below:

Figure 193: SYNC DB Monitor Icon in EasyConnect Toolbar

The SYNC DB Monitor window will appear on the screen as shown in the following Figure
(SYNC DB Monitor Window). This window displays the details of device Point IDs configured for
the internal master channels.

Each configured point in the profile has a unique row number and the device Point ID is same
as the unique row number. The starting Point ID of each row will be displayed in the profile view
itself, as shown in Figure (Point ID is shown in Profile Configuration) given below. The status of
each point can be monitored using its Point ID.

SYNC 2000, 3000, 4000 Series Software User Manual 159

 Figure 194: SYNC DB Monitor Window

Figure 195: Point ID is shown in Profile Configuration

32.1 SYNC DB Monitor- Menu Items

The SYNC DB Monitor contains menu items such as View and Option to add or remove various
options and values in the DB window’s menu bar as required.
32.1.1 View
The View item in the menu bar enables the user to include the type and tag name in the DB
monitor window. This is done by selecting or deselecting type and tag name from the View item.
32.1.2 Option
The Option item in the menu bar allows the user to add or remove Alarm window from the DB
Monitor Window. This is done by selecting or deselecting Alarm window from Option menu.

SYNC 2000, 3000, 4000 Series Software User Manual 160

 32.2 Function Keys
The following buttons are used in the SYNC DB Monitor to start, stop or refresh the Monitoring
window:
32.2.1 Start
The DB Monitor can be started after entering the IP of the configured SYNC Device in the space
provided for IP address. It displays an error if:
• The firmware is not running
• IP address is not valid or empty
• Current configuration does not match device configuration
• Unable to start communication
32.2.2 Stop
The DB monitor can be stopped at any time by clicking the Stop button. It displays an error if it
is unable to stop communication.
32.2.3 Refresh
The DB monitor is automatically updated every 5 minutes. A Refresh button is provided to
enable the user to refresh manually the data populated on the DB window whenever required. It
will then display latest values of all database points.

32.3 Supported Features

The SYNC DB Monitor provides various features such as Channel Filtering, Data Type Filtering,
Status Monitor, Alarm Window and Watch Window.
32.3.1 Channel Filtering
Channel filtering allows the user to monitor the Point IDs of the specified channels. This
can be done by selecting or deselecting the required channels. Only the data points of
selected channels will be displayed on the right hand side of DB Monitor. This filtering is possible
even in the middle of communication.
32.3.2 Data Type Filtering
This enables the user to filter the Analog and Digital points separately so that only the points of
the selected type will be displayed on the form. User must select the required type in the tree
view as shown in Figure (Data Type Filtering) below:

Figure 196: Data Type Filtering

SYNC 2000, 3000, 4000 Series Software User Manual 161

 32.3.3 Status Monitor
The SYNC DB Monitor notifies the user whenever a communication failure occurs. An indicator
is provided on the bottom right of the DB Window. When the communication session is online,
the indicator is green in color with the status as Online. When a communication failure occurs,
it is red in color with the status as Offline as shown in Figure (Status monitor showing Offline
status) given below. This helps the user to monitor easily the communication status in SYNC DB
Monitor.

Figure 197: Status monitor showing Offline status

32.3.4 Alarm Window

Within the SYNC DB monitor, an Alarm window is provided to display the events occurring at the
digital input points, as shown in Figure (Alarm window). It allows the user to check for changes
occurring at the data points very easily along with the event time stamp. The user can also
remove events from the Alarm window by right clicking on the mouse button on the event row.

Figure 198: Alarm window

32.3.5 Watch Window

This is an important feature available in the SYNC DB monitor. This enables the user to add
critical/important points to the Watch window and to monitor points from the window easily. See
Figure (Watch window). There is also an option to remove the points from the Watch window by
right clicking on the mouse button within the Watch window.

To add points to be monitored in the Watch window, right click on the mouse button as shown in
Figure (Adding point in watch window). It is also possible to select multiple points to add to the
Watch window.

Figure 199: Watch window

SYNC 2000, 3000, 4000 Series Software User Manual 162

 Figure 200: Adding point in watch window

32.3.6 Adding More Columns of Details

User can add more columns to the SYNC DB for providing the description of the points displayed
in the window. This can be done by right click on the corresponding channel in the channel list
and check on the required parameters whose values need to be displayed in the SYNC DB
monitor window. Refer Figure (Adding columns to DB Monitor).

Figure 201: Adding columns to DB Monitor

32.3.7 Quick Filter

This is one of the major feature included in SYNC DB Monitor. It helps user to filter the points
displayed in the window based on the search key. User can also filter the points based on the
Alias name, Node Alias Name or point id. This can be done by selecting the filter columns
displayed in quick Filter window. Refer Figure (Quick Filter).

Figure 202: Quick Filter

SYNC 2000, 3000, 4000 Series Software User Manual 163

 33
33 Variables

It is possible to add Variables as Profile points. They can be used for mapping against other
protocols or variables. Variables are of three different types:
• Logic Variables
• System Variables
• Special functions

To add Variables, do the following:

• Right -click on the Protocol Configuration
• Click on Add Variables

Figure 203: Add variables

33.1 Logic Variables

Apart from the protocol profile points, variables can be added to be used in the logic engine.
These variables will also be available to the ISaGraf Work Bench upon export. Logic variables
can also be mapped to other protocol points. This helps the user to store the result of a logic
program into this variable and simultaneously map the result to a protocol point.

Adding a logic variable is similar to adding a profile row in a protocol. The Add row button is used
to add the logic variable.

SYNC 2000, 3000, 4000 Series Software User Manual 164

The properties of the logic variable can be set as shown in the figure (Adding a Logic variable)
below.

Figure 204: Adding a Logic variable

33.2 System Variables

For each SYNC device, there will be a pre-configured list of device-specific system variables.
These variables reflect different device-specific parameters or statuses such as Input/ Output
card status, device restart reason etc. These variables can be mapped and used to monitor the
device status remotely using different protocols.

A system variable is added by using the Add row button. The available device specific variables
are listed as shown in the figure (Adding a System variable) below and any one can be chosen.
Unlike other profile points, a system variable’s properties cannot be edited.

The System variable can also be used in the Logic Engine like all other protocol points.

Figure 205: Adding a System variable

SYNC 2000, 3000, 4000 Series Software User Manual 165

The system variables that are currently available are listed in below table 13 (System Variables).

Supported
Variable Functionality Values Dependence
Models
Restart Toget the reason 1 → Putty/TerminalAll Models 1. firmware should
Reason forthe most closed. support global
recent re- startof 2 → Ctrl C pressed. master
firmware 3 → Ctrl \ pressed. 2. License of
4 → Internal error global Master
6 → Internal error 3. DCCPVersion
8 → Internal error 16.0 or higher
10 → Internal error
11 → Internal error
13 → Internal error
15 → Internal error
19 → Power failure
23 → Firmware
paused
24 → Ctrl Z Pressed
31 → File Size ex-
ceeded
99 → EasyConnect
Reboot
98 → EasyConnect
stop
97 → Power restart
96 → Reboot com-
mand
100 → Other
reasons
Local Remote Toget the For SYNC2101/ SYNC2101, 1.Firmware should
Status position ofLR SYNC2111: ON → SYNC2111 have support to
switch Remote OFF → glob- al master
Local and MRTU/FRTU
Master(depends
on the model)
2.License of global
Master
and MRTU/FRTU
Master

Card Toget the status 0 → Card not active SYNC2111 1.Firmware should
Status1 ofcard 1 1 → card active have support to
2 → card mismatch glob- al master
and FRTU Master
2.License of global
Master and FRTU
Master

SYNC 2000, 3000, 4000 Series Software User Manual 166

 Supported
Variable Functionality Values Dependence
Models
Card Status2 Toget the status 0 → Card not active SYNC2111 1.Firmware should
ofcard 2 1 → card active have support to
2 → card mismatch glob- al master
and FRTU Master
2.License of global
Master and FRTU
Master
Card Status3 Toget the status 0 → Card not active SYNC2111 1.Firmware should
ofcard 3 1 → card active have support to
2 → card mismatch glob- al master
and FRTU Master
2.License of global
Master and FRTU
Mas- ter
Card Status4 Toget the status 0 → Card not active SYNC2111 1.Firmware should
ofcard 4 1 → card active have support to
2 → card mismatch glob- al master
and FRTU Master
2.License of global
Master and FRTU
Mas- ter
Card Status5 Toget the status 0 → Card not active SYNC2111 1.Firmware should
ofcard 5 1 → card active have support to
2 → card mismatch glob- al master
and FRTU Master
2.License of global
Master and FRTU
Mas- ter
Card Status6 Toget the status 0 → Card not active SYNC2111 1.Firmware should
ofcard 6 1 → card active have support to
2 → card mismatch glob- al master
and FRTU Master
2.License of global
Master and FRTU
Mas- ter

Card Status7 Toget the status 0 → Card not active SYNC2111 1.Firmware should
ofcard 7 1 → card active have support to
2 → card mismatch glob- al master
and FRTU Master
Last SYNC The time at which Time (in milliseconds SYNC3000 1.Firmware should
Time last Sync has from epoch) have support to
occurred. global master
2. Time SYNC
method is IEEE1588

Time Since Last The time elapsed Time in seconds SYNC3000 1.Firmware should
Sync Time after last SYNC have support to
Time global master
2. Time SYNC
method is IEEE1588

SYNC 2000, 3000, 4000 Series Software User Manual 167

 Supported
Variable Functionality Values Dependence
Models
Time Validity Validity of current GOOD: Time is Valid SYNC3000 1.Firmware should
SYNC time have support to
global master
INVALID: Time is 2. Time SYNC
Invalid since Time method is IEEE1588
Valid Period is
expired or Time
synchronization
message not received
after First SYNC
Wait Period (Refer
time synchronization
parameters)

EXCVP: Exceeded
Clock Valid
Period (refer time
synchronization
parameters)

EXMOFT: Exceeded
Maximum Offset (refer
time synchronization
parameters)

FSYNCWT: Time
synchronization in
‘First SYNC Wait
Period’ (refer time
synchronization
parameters)

OVLST: Overflow of
Time Since Last Sync
Time
PTP Running PTP is running or 0 ->Not Running SYNC3000 1.Firmware should
Status not running 1 ->Running have support to
global master
2. Time SYNC
method is IEEE1588
Table 15: System Variables

SYNC 2000, 3000, 4000 Series Software User Manual 168

 33.3 Special Functions
Special functions are a set of actions/methods predefined in the device. Each of these functions
can be triggered in many different ways. One option would be on a value change at a point.
For example, a DI point can be configured as the ‘Battery Charging On/Off status’. When the
DI changes, all actions defined/configured to battery charging, will be triggered. Below figure
(Adding Special functions) shows how to add Special Functions.

Figure 206: Adding Special functions

The below table 14 (Special Functions) lists all the Special functions available in the device.

Supported
Special Data Type Functionality Values
Models
Battery Digital This informs GPC ON → On All Models
Charging Input whether the DCU Battery OFF
On/ Off status is running on bat- → On regu- lar
tery(power is out or not supply
connected) or not
Table 16: Special Functions

SYNC 2000, 3000, 4000 Series Software User Manual 169

 34
34 IEC 61131 Logic engine
IEC 61131 is an IEC standard for programmable controllers. Part 3 of the IEC 61131 standard
deals with programming languages and defines two graphical and two textual PLC programming
language standards.

The graphical ones are the Ladder Diagram (LD) and Functional Block Diagram (FBD). The
textual ones are Structured Text (ST) and Instruction List (IL).

Sequential Functional Chart (SFC) has elements to organize programs for sequential and parallel
Control Processing.

The Logic Interface settings in EasyConnect enable the user to use the data from different
protocol points and to create a programming logic in 61131 using IsaGraf Work bench. For each
profile row of the protocol, there will be an option to enable or disable the support for that point
in logic engine. Enabling that option, enables the Logic Settings tab to enter configuration details
as shown in the figure (Enabling the use of a profile row in Logic Engine) below.

Figure 207: Enabling the use of a profile row in Logic Engine

SYNC 2000, 3000, 4000 Series Software User Manual 170

 34.1 Exporting Logic Engine Variable List
Once the configuration is completed, the variables can be exported to Logic WorkBench by
following the following steps:
• Right-click on the “Protocol Configuration” tree
• Select “Export Logic Variable List” from the menu
• Enter the file name and “Save”

The variable list in Excel format is then exported. This can then be imported to ISaGraf WorkBench
and can be used in creating programming logic.

Note: The details of import variables, logic creation and download are explained in
SYNC-IEC 61131 Interface User Manual.

Figure 208: Exporting logic variables

SYNC 2000, 3000, 4000 Series Software User Manual 171

 35
35 Web HMI Support
Web HMI provides a web based user interface for SYNC field devices including Substation
Gateways, RTUs and Data Concentrators. It can be accessed locally and remotely through a
built-in web-server. Key features are the following.
• Single Line Diagram
• Multiple Protocol Support
• Events List Management
• Alarm Management
• Excel Export of Events and Alarms
• Instantaneous Data Monitoring
• Secure Connection Through SSL/TLS
• User Management

Note: Please refer Web HMI user manual for more details.

SYNC 2000, 3000, 4000 Series Software User Manual 172

 36
36 Time Synchronization
The following are two methods of time synchronization supported in SYNC Devices apart from
other protocol based (SNTP, IEC61850, IEC104 etc.) time synchronization. This feature is device
specific and supported by SYNC3000S12R6, SYNC3000S12R2F2.

36.1 IRIG Standard

The term IRIG signals is frequently used to refer to a whole group of serial time codes, which
use a continuous stream of binary data to transmit information on date and time. The individual
time code formats can be distinguished by the signal characteristics, e.g. modulated versus
unmodulated, which require different ways of signal transmission, by the data rate, and by the
kind of information included in the transmitted data. Among which IRIG time code ‘B’ (IRIG-B) is
widely used in the electrical power industry to synchronize time.

The device will accept unmodulated DC Level Shift (TTL Level) codes without carrier.

36.2 IEEE 1588 Standard

IEEE 1588 is a protocol designed to synchronize real-time clocks in the nodes of a distributed
system that communicate using an ethernet network. For the industrial automation network,
IEEE 1588 supported Data Concentrator which work as the ordinary clock that connects with
Ethernet switches to receive and synchronize timekeeping data. This timekeeping can be precise
and considerably enhancing the reliability of power substation systems. In power substation
networks, precise timekeeping allows the system to keep time-stamped event logs that are highly
accurate. This prevents power blackouts by helping operators accurately identify problems and
perform precise failure analysis

In order to build a completely IEEE 1588v2-compliant network, the Ethernet switches, end devices,
and industrial computers must all support IEEE 1588v2. By deploying IEEE 1588v2-complaint
IED’s now system operators can create a system where the switches, IEDs, and computers all
work seamlessly together for highly accurate time synchronization. In recent years, an increasing
number of electrical power systems have been utilizing a more distributed architecture and less
stringent timing specifications. IEEE 1588 establishes a master-slave relationship between the
clocks, and enforces the specific timing requirements. All devices ultimately derive their time
from a clock known as the grandmaster clock. In its basic form, the protocol is intended to be
administration free.

SYNC 2000, 3000, 4000 Series Software User Manual 173

 36.3 Configuring Time Synchronization
36.3.1 Device Parameters
Configuration for time synchronisation can be found in device configuration window with name
Time Synchronization as shown below in figure (Device Parameters).

Figure 209: Device Parameters

When Time Synchronization is chosen, the following window is seen and parameters are
described in Table 16: Time Synchronization Parameters.

Figure 210: Time Synchronization Window

SYNC 2000, 3000, 4000 Series Software User Manual 174

 Parameter
Range Default Description
Name
Time Disable, IRIG B, Disable If disabled then time
synchronization* IEEE 1588 synchronization won’t happen
through any mechanisms.

If IRIG B is chosen then time

synchronization through IRIG B is
enabled.

If IEEE 1588 is chosen then time

synchronization through IEEE
1588 is enabled

IRIG Standard B B Currently only IRIG -B standard is

supported.
IRIG Format B000 (with IEEE B000 (with IEEE Currently only B000 (with
C37.118 CF C37.118 CF IEEE C37.118 CF extensions)
extensions) extensions) supported.
IRIG Time Sync 01/01/40 10 1-1440 minutes: Device will try
interval(min) to synchronize time on every
configured interval.
IRIG Time offset Local/ UTC Local Time offset can be Local or UTC.

Local: IRIGB time will be treated

as local time and offset specified
in time zone
field will be subtracted to obtain
UTC time.

UTC: The input signal will treat

as UTC time independent of time
zone field

IEEE 1588 eth0, eth1, eth2, eth0 The Precison Time Protocol is
Interface * eth3, bond0, bond1, bound to the chosen interface.
hsr0, hsr1, prp0,
prp1
UTC Offset * -43200 to 43200 0 Master clock offset from UTC time
in seconds.
Transport Ethernet, ipv4 Ethernet Transport type for PTP packets

Ip Mode multicast,unicast - IP transmission mode

Note: hybrid mode uses
multicast for sync and
announce, and unicast for
delay request and response.
Unicast mode uses unicast for
all transmission.
Configurable if configured value
for Transport is Ethernet.

SYNC 2000, 3000, 4000 Series Software User Manual 175

 Unicast IP Address - When unicast mode is
Address selected, destination IP must
be configured. Or else not
configurable.
Delay E2E, P2P P2P Delay detection mode used
Mechanism E2E: End to end delay
detection
P2P: Peer to peer delay
detection
VLAN Tagvalue 0 – 65534 0 Vlan Tag value

Note: Configure zero if VLAN

Tag is not to be considered.
Maximum 0 - 999999999 3600 Do not reset the clock if offset
Offset from master is less than this
value (seconds).

Note:Configure zero if
Maximum Offset configuration
is not to be considered.

Time valid 0 – 65534 300 s This indicates time valid

interval interval in seconds. If no SYNC
is received within this time from
the last SYNC
Table 17: Time Synchronization Parameters

SYNC 2000, 3000, 4000 Series Software User Manual 176

 37
37 DCCP Packaging
DCCP Packaging allows the user to update the DCCP firmware in the device with the latest
EasyConnect compatible DCCP firmware.

From version 4.6.0 of EasyConnect onwards, the latest version of DCCP firmware is provided
in the EasyConnect application folder. If the device has an older DCCP version, EasyConnect
provides an option to automatically upgrade the DCCP firmware.

During various operations such as ‘Download’, ‘Upload’, ‘Stop firmware’ and ‘Start firmware’,
EasyConnect l checks the DCCP firmware version in the device, and then prompts the user to
download the latest version, if the DCCP version in the device is older.

To enable this DCCP version check, the ‘Check for firmware updates’ box in the Option window
found under Tools must be checked as shown in the figure below. Then click Save.

Figure 211: Enabling Check for Firmware Updates

To disable the version check, uncheck the Check for firmware updates box and click Save.

If the device has an older DCCP version, EasyConnect prompts the user to upgrade the DCCP
firmware as shown in the figure (Pop-up for Automatic Up gradation) below. On clicking Yes, the
device gets upgraded to the latest DCCP.

Figure 212: Pop-up for Automatic Up gradation

SYNC 2000, 3000, 4000 Series Software User Manual 177

Note: On checking the ‘Don’t ask this again’ box, the version check will be disabled for that
EasyConnect instance even if the ‘Check for firmware updates’ box in the Option window under
Tools is checked.

For DCCP versions older than 2.9, EasyConnect prompts the user to upgrade to a compatible
DCCP version, as shown in the figure (Model name prompt for older DCCP versions) below. On
clicking Yes, the user is prompted to browse for the model name from the combo box, as shown
in the second figure (Automatic upgrade prompt for incompatible DCCP version) below. On
clicking OK, the DCCP firmware in the device gets automatically upgraded to the EasyConnect
DCCP firmware version.

Figure 213: Model name prompt for older DCCP versions

Figure 214: Automatic upgrade prompt for incompatible DCCP version

In the Version Information window, an option Click here to update is provided to update the
DCCP version if the device uses an older DCCP version than the EasyConnect DCCP version,
as shown in the figure (DCCP update Link in Version Info) below. This feature is available only
for devices that support DCCP Packaging.

SYNC 2000, 3000, 4000 Series Software User Manual 178

 Figure 215: DCCP update Link in Version Info

Note: This option is not available if the ‘Check for firmware updates’ box in the Option window
found under Tools is unchecked.

SYNC 2000, 3000, 4000 Series Software User Manual 179

In case of older DCCP versions that have no version information (DCCP versions older than
v2.9.0), the following message will be displayed on checking the version information as shown
in the figure (Version Info for devices with older DCCP Versions) below.

Note: The DCCP Packaging feature is supported for all the devices listed in the SYNC tab in the
devices list in EasyConnect.

Figure 216: Version Info for devices with older DCCP Versions

SYNC 2000, 3000, 4000 Series Software User Manual 180

 A
Appendix A - Special Case: IEC 61850 Server and
ICCP Peer

IEC61850 server ICCP peer protocol configuration follows different approach compared to other
protocols specified in this document. High level workflow is detailed below. Refer corresponding
user manual for details.

IEC61850 Server Configuration

Configuration of IEC 61850 Server using EasyConnect is a little different from configuration of
other channels. The following procedure has to be followed. Refer IEC61850 server configu-
ration manual for details.

• Add IEC 61850 server channel in EasyConnect.

• The ICD file is created using SCL Manager and is saved in a file location.
• User can select the configured ICD file from EasyConnect and add it to the profile.
• Generate MMS tags for mapping.
• Add stations and channels as described in the document.
• Download the configured file to SYNC.

ICCP Peer configuration

Configuration of ICCP Peer using EasyConnect is a little different from configuration of
otherchannels. The following procedure has to be followed. Refer ICCP Peer configuration
manual for details.

• Add ICCP Peer channel in EasyConnect.

• To configure ICCP, right-click and select Configure ICCP Utility.
• The ICCP configuration file with local control center and remote control center with its
association and bilateral table information is created using ICCP Configuration utility and
is saved in a file location.
• User can select the configured ICCP file from EasyConnect and add it to the profile.
• To generate Nodes, right-clicking on the channel will create the client and server nodes
• automatically by reading the ICCP Configuration file.
• Download the configured file to SYNC.

SYNC 2000, 3000, 4000 Series Software User Manual 181

 B
Appendix B – SYNC Devices

The following table 16 (Models supported in different SYNC series) details the models supported
in different SYNC series.

SYNC Series Models Supported

SYNC 2000 SYNC2000-M1 (S2R1), SYNC2000-M2 (S6R1), SYNC2000-M4 (S6F1),
SYNC2000-M3 (S4R2)
SYNC 3000 SYNC3000-M1 (S12R2), SYNC3000-M2 (S12R4), SYNC3000-M3 (S12R6),
SYNC3000-M12 (S12R2F2)
SYNC4000 SYNC4000-M1
Table 18: Models supported in different SYNC series

GPC, DCCP & EC compatibility table

The following table 17 (GPC, DCCP & EC Compatibility Table) provides the details of DCCP and
EasyConnect versions released/ used with the corresponding GPC release.

GPC Version DCCP Version EC Version Date of GPC

Release
GPC_V3.0 DCCP_V3.0 Easy connect V 5.0 Dec 2015
GPC_V2.24.0 DCCP_V2.18.0 EasyConnect_V4.10.0 March 2015
GPC_V2.23.0 DCCP_V2.17.0 EasyConnect_V4.9.0 June 2014
GPC_V2.22.0 DCCP_V2.16.0 EasyConnect_V4.8.0 October 2013
GPC_V2.21.0 DCCP_V2.15.0 EasyConnect_V4.7.0 June 2013
GPC_V2.20.0 DCCP_V2.14.0 EasyConnect_V4.6.0 March 20, 2012
GPC_V2.19.0 DCCP_V2.13.0 EasyConnect_V4.5.0 May 16, 2011
GPC_V2.18.0 DCCP_V2.12.0 EasyConnect_V4.4.0 December 30, 2010
GPC_V2.17.0 DCCP_V2.11.0 EasyConnect_V4.3.0 September 28, 2010
GPC_V2.16.0 DCCP_V2.10.0 EasyConnect_V4.2.0 July 02, 2010
GPC_V2.15.0 DCCP_V2.9.0 EasyConnect_V4.1.0 March 11, 2010
GPC_V2.14.0 DCCP_V2.9.0 EasyConnect_V4.0.0 February 8, 2010
GPC_V2.13.0 DCCP_V2.8.1 EasyConnect_V3.3.0 November 30, 2009
GPC_V2.12.0 DCCP_V2.8.0 EasyConnect_V3.2.0 October 8, 2009
GPC_V2.11.0 DCCP_V2.7.0 EasyConnect_V3.1.0 July 17, 2009
GPC_V2.10.0 DCCP_V2.7.0 EasyConnect_V3.0.0 June 3, 2009
Table 19: GPC, DCCP & EC Compatibility Table

SYNC 2000, 3000, 4000 Series Software User Manual 182

Appendix C – Flag conversion in SYNC
C
When a protocol conversion is achieved using SYNC, the quality flag conversion between the protocols has to be defined. The table 18 (Flag Mapping) below is used to explain the quality flag translation between
protocols inside SYNC. The flags received in any of the SYNC-Master Protocol (SYNC Master) will be translated to a specific flag of SYNC-Slave Protocol (SYNC Slave) as described in the table 18 shown below.
SYNC-Master Protocol
IEC 101/104 DNP 3.0 IEC 103 Modbus IEC 61850
Validity
On link Validity = Validity Validity Validity = Validity = Validity Validity
SYNC-Slave Protocol failure
Roll-over2
On link failure
On link On link
Questionable = invalid = invalid
= invalid
Questionable Questionable = invalid = invalid On link failure
(Counter)/ Local forced Communication Remote Chatter Reference ER3 (MVAL failure (Not failure (Not & Detail Source =
OV1 BL1 SB1 NT1 IV1 EI1 (Not On-line2 = 0 Restart2 (Not protocol OV3 & Detail & Detail & Detail & Detail & Detail Blocked4 & Detail & Detail (Not protocol
Over-range2 data2 lost2 forced data2 filter2 check2 invalid) protocol protocol quality Substituted4
protocol flag) quality = Old quality = quality = quality = quality = quality = quality = Out flag)
(Analog) flag) flag) = Bad
flag) data4 Oscillatory4 Failure4 Inaccurate4 Inconsistent4 Overflow4 of Range4
Reference4
OV1 X X X X X
BL1 X X
IEC SB1 X X X X
101/104 NT1 X X X X X X X X
IV1 X X X X X X X X X
EI1 X
Roll-over2
(Counter)/ Over- X X X X X
range2 (Analog)
Local forced
X X X
data2
Communication
X X X X X X X
DNP 3.0 lost2
On-line2 = 0 X X X X X X X X
Restart2 X
Remote forced
X
data2
Chatter filter2 X X
Reference check2 X X
OV3 X X X
IEC 103 ER3 (MVAL
X X X X X X X X X X X X X X X
invalid)
Validity =
Questionable &
X X X X X X X X
Detail quality =
Old data4
Validity = invalid
& Detail quality = X X
Oscillatory4
Validity = invalid
& Detail quality = X X X X X X X X X
Failure4
Validity = invalid
& Detail quality = X X
Bad Reference4
IEC 61850 Validity =
Questionable &
X X
Detail quality =
Inaccurate4
Validity =
Questionable &
X
Detail quality =
Inconsistent4
Source =
X X X X
Substituted4
Blocked4 X X
Validity = invalid
& Detail quality = X X X X X
Out of Range4

Table 20: Flag Mapping

All flags described in the table are considered set and follow the applicable translation unless specified otherwise
• See quality description details in section 7.2.6.3 and 7.2.6.4 of IEC 60870-5-101.
• See DNP V3.00 Data Object Library – FLAG details given in each objects
• See details in section 7.2.6.8 of IEC 60870-5-103

See details in section 6.2 of IEC 61850-7-3.

SYNC 2000, 3000, 4000 Series Software User Manual 183

 D
Appendix D – HSR/PRP/IEEE1588 Interoperability

IEC 62439-3 Interoperability Table

Standard IEC 62439-3:2012 March 20, 2012
Mode H: HSR-tagged
Mode of operation
forwarding
SNMP_MIB Not supported
Time
synchronization IEC 61588 (PTP)
support
Supported Ethernet ports
LAN1-LAN5 (eth0, eth1, eth2,
eth3, eth4)
HSR SYNC3000S12R6 Note:if eth4 is selected for HSR
redundancy, eth5 will be unavailable
for any other communication.
Supported SYNC LAN1-LAN5 (eth0, eth2, eth4)
Devices SYNC3000S12R2F2 Note:if eth4 is selected for HSR
redundancy, eth5 will be unavailable
for any other communication.
LAN1-LAN5 (eth0, eth1, eth2,
SYNC3000S12R4 eth3)

SYNC3000S12R2 LAN1-LAN5 (eth0, eth1)

 Standard IEC 62439-3:2012 March 20, 2012
Mode of operation Duplicate Discard
SNMP_MIB Not supported
Time
synchronization IEC 61588 (PTP)
support
Supported Ethernet ports
LAN1-LAN5
(eth0,eth1,eth2,eth3,eth4)
PRP SYNC3000S12R6 Note:if eth4 is selected for HSR
redundancy, eth5 will be unavailable
for any other communication.
Supported SYNC LAN1-LAN5 (eth0, eth2, eth4)
Devices SYNC3000S12R2F2 Note:if eth4 is selected for HSR
redundancy, eth5 will be unavailable
for any other communication.
LAN1-LAN5 (eth0, eth1, eth2,
SYNC3000S12R4 eth3)

SYNC3000S12R2 LAN1-LAN5 (eth0,eth1)

IEEE 1588 PTP version

Version March 20, 2012
2.0
Path delay Delay request-response
mechanism mechanism
Ordinary clock (Slave
PTP device type
only clock)
Transport
UDP/IPv4
Mechanism
HSR/PRP support Yes
PTP/ IEC Supported Ethernet ports
61588
LAN1-LAN4 (eth0, eth1, eth2,
SYNC3000S12R6 eth3)

Supported SYNC LAN1-LAN4 (eth0, eth2)

SYNC3000S12R2F2
Devices
LAN1-LAN4 (eth0, eth1, eth2,
SYNC3000S12R4 eth3)

SYNC3000S12R2 LAN1-LAN4 (eth0, eth1)

Table 21: IEC 62439-3 Interoperability Table
 E
Appendix E – PRP implementations

PRP Software
Copyright (c) 2007, Institute of Embedded Systems at Zurich University of Applied Sciences
(http://ines.zhaw.ch)

All rights reserved.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS

IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITYAND FITNESS FORAPARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Glossary
List of Abbreviations
The following table 20 (List of abbreviations) shows the acronyms/abbreviations used in this
document

Acronyms/Abbreviations Description
CHAP Challenge-Handshake Authentication Protocol
DCCP Diagnostic and Converter Configuration
Protocol Enhanced Data rates for Global Evolution
DPI Dots Per Inch
EDGE Enhanced Data rates for Global Evolution
GPC Generic Protocol Conversion
GPRS General Packet Radio Service
HSB Hot-Standby
IP Internet Protocol
KSGL Kalki Substation Gateway Lite
PPP Point to Point Protocol
RAM Random Access Memory
UDP User Datagram Protocol
VPN Virtual Private Network
SNMP Simple Network Management Protocol
XML Extensible Markup Language
RSA Rivest - Shamir - Adleman
DES Data Encryption Standard
AES Advanced Encryption Standard
SHA Secure Hash Algorithm
CBC Cipher-block chaining
DHE Diffie-Hellman ephemeral
RC4 Rivest Cipher 4
CA Certificate Authority
ARP Address Resolution Protocol
NAT Network Address Translation
RSTP Rapid Spanning Tree Protocol
MRP Media Redundancy Protocol
PRP Parallel Redundancy Protocol
HSR High Availability Seamless Redundancy
Table 22: List of abbreviations

SYNC 2000, 3000, 4000 Series Software User Manual 187