SYNC EasyConnect Usermanual Rev4.7.0

EasyConnect
Software User Manual
www.kalkitech.com
Version 4.7.0, March 2017
EasyConnect Software User Manual 1

Copyright Notice
© 2017 Kalki Communication Technologies Pvt. Ltd. All Rights reserved.

This user manual is a publication of Kalki Communication Technologies Pvt. Ltd. and it is intended for
its customers use only. Content of this 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 manual is subject to change without any 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 Pvt. Ltd. makes no commitment to update or keep the current information in this manual.
Contact Information
Kalki Communication Technologies Pvt. Ltd.

The Address, 4th Floor,
# 17/1, Outer Ring Road,
Opposite to Prestige Cessna Business Park
Kadubeesanahalli, Bangalore - 560103, INDIA
Telephone: +91- 8067021900

Email: sales@kalkitech.com
Technical Support Contact Information
Online Technical Enquiry Support: www.kalkitech.com/support
E-mail Support: support@kalkitech.com

About the Document
Purpose
This user manual serves as a guide for using EasyConnect Configuration Utility to configure
SYNC200, SYNC 2000, SYNC2100, 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 EasyConnect, 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 EasyConnect
• Explains the user interface
• Provides step-by-step instructions to install and get started with EasyConnect
• Provides step-by-step instructions to configure and map protocols points

Table of Contents
1. Overview 14
1.1. EasyConnect 14
1.2. Environment 15
1.2.1. Software Requirements 15
1.2.1. Hardware Requirements 15
2. Getting Started 16
2.1. Installing EasyConnect 16
2.2. Removing EasyConnect 16
2.3. Starting EasyConnect 16
2.4. Exiting EasyConnect 17
2.5. Using the EasyConnect Interface 17
2.5.1. Menu 18
2.5.2. Toolbar 21
2.5.3. Workspace 21
3. EasyConnect Application Modes 22
3.1. Mode Switching 23
4. License Management 25
4.1. EasyConnect Licensing 25
4.2. SYNC Device Licensing 28
4.3. Installing Device License 29
4.4. Devices Up gradation 30
5. Device Settings 32
5.1. Download 32
5.2. Apply Configuration 37
5.3. Upload 39
5.4. Upload Modes 41
5.5. Restart Device 43
5.6. Stop Firmware 45
5.7. Start Firmware 46
5.8. Network Scanning 47
5.9. Version Information 48
5.10. Time Settings 50
5.11. Update Firmware 54
6. Traffic/Diagnostics Monitor 55
7. User Management 56
7.1. User Authentication 56
7.2. Configuring Users and Roles 56
7.2.1. Roles 57
7.2.2. Users 58
8. Audit Trail 59
9. SMS Based Configuration 61
9.1. SMS Port Settings For Workstation PC 61
9.2. SMS Settings for SYNC Device 62
9.3. Send Configuration SMS 65
9.4. Manage Admin Contact 66
10. Set Language 68

11. DB Delete 69
12. Device Logs 72
12.1. Device Log 73
12.2. Device Access Log 76
12.3. Application Logs 77
12.4. Communication Log 79
13. API Configuration 80
14. Gateway Configuration 85
14.1. Add Master Channel 86
14.2. Add Slave Channel and Node 93
14.3. Master to slave Mapping 93
14.3.1. Auto Mapping – Master to Slave 94
14.3.2. Auto Map Window 96
14.3.3. Slave to Slave Mapping 98
14.4. Ease of Configuration 99
14.4.1. Copy/Paste 99
14.4.2. Profile Row Options 100
14.4.3. Multiple Row Modify Option 100
14.4.4. Search Option in profile and mapping 101
14.4.5. Excel Import/Export 102
15. Configure Logging 104
16. Dialup Configuration 106
17. VPN Configuration 111
18. SNMP Configuration 120
19. Configuration File Management 121
19.1. Downloading configuration to device 121
19.2. Saving Configuration File 122
19.3. File Revision 124
19.3.1. Save to Revision 124
19.3.2. Load from Revision 125
20. Network Configuration 126
20.1. Setting device IP 126
20.2. Ethernet redundancy 126
20.3. Configuring Redundant Interfaces 129
20.4. NAT Policy Settings 130
20.4.1. To add NAT Rules 131
20.4.2. To edit NAT Rules 133
20.4.3. To delete a NAT Rule 133
20.4.4. To delete NAT Policy Settings 134
20.5. Routing Configuration 134
20.6. DNS Configuration 137
20.7. Ethernet Packet Capture 138
21. Redundancy Configuration 140
21.1. Types of Switch-over 140
21.1.1. External Trigger Switch-over 140
21.1.2. Self Switch-over 141
21.2. IP Switching Mechanisms 141
21.2.1. IP Swapping 141

21.2.2. No IP Switching 142
21.3. Redundancy Requirements 142
21.4. Device Redundancy Information and Control 143
21.5. Hot-Standby protocol 143
21.5.1. Configuration of Hot-Standby 143
21.5.2. Channel Configuration 144
21.5.3. Node Configuration 146
21.5.4. Redundancy Switch-over Details 151
21.5.5. HSB Configuration Easiness 151
22. NERC-CIP Support 152
23. File Transfer Support 154
24. Parameterization through Pass-Through (Transparent) Channel 157
25. Encryption Support 158
26. Data Monitoring 163
26.1. SYNC DB Monitor- Menu Items 164
26.1.1. View 164
26.1.2. Option 164
26.2. Function Keys 165
26.2.1. Start 165
26.2.2. Stop 165
26.2.3. Refresh 165
26.3. Supported Features 165
26.3.1. Channel Filtering 165
26.3.2. Data Type Filtering 165
26.3.3. Status Monitor 166
26.3.4. Alarm Window 166
26.3.5. Watch Window 166
26.3.6. Adding More Columns of Details 167
26.3.7. Quick Filter 167
27. Self Supervision 168
27.1. Device INFO 168
27.2. Hardware 169
27.3. Application 169
27.4. Channel Diagnostics 169
27.5. Node Diagnostics 170
27.6. Interface 170
28. Tag List 171
28.1 ‘All’ Tags 172
28.1.1. Settings 173
28.2 Logic Variables 175
28.3 Diagnostic Variables 176
28.4 Special Functions 191
29. IEC 61131 Logic engine 192
29.1. Exporting Logic Engine Variable List 193
30. Web HMI Support 194
31. Time Synchronization 195
31.1. Time Synch Configuration 195
31.2. IRIG Standard 198

31.3. IEEE 1588 Standard 198
31.4. NTP Support 199
31.4.1. Configuring NTP 199
32. DCCP Packaging 201
Appendix A – Special Case: IEC 61850 Server and ICCP Peer 205
Appendix B – SYNC Devices 206
Appendix C – Flag conversion in SYNC 207
Appendix D – HSR/PRP/IEEE1588 Interoperability 208
Appendix E – PRP implementations 210
Glossary 211

List of Figures
Figure 1: EasyConnect User Interface 17
Figure 2: User Interface 17
Figure 3: File Menu 18
Figure 4: View Menu 18
Figure 5: Configuration Menu 19
Figure 6: Settings Menu 19
Figure 7: Diagnostic Menu 20
Figure 8: Tool Menu 20
Figure 9: Help Menu 21
Figure 10: Toolbar 21
Figure 11: Edit Preferences 23
Figure 12: Mode switching from login screen 23
Figure 13: Login Screen of EasyConnect in Advance Mode 25
Figure 14: License Installation Screen 25
Figure 15: User License Installation Screen 26
Figure 16: License Information Window 26
Figure 17: Password Resetting Window 27
Figure 18: Installing Cloud License 27
Figure 19: Device Licensing 28
Figure 20: Installing Device License 29
Figure 21: Device License details 29
Figure 22: Kalki.io Connectivity License process 30
Figure 23: Device Upgradation 30
Figure 24: Installing License to Device 31
Figure 25: Download Menu 32
Figure 26: Download files selection 33
Figure 27: Redundant Device Download operation 33
Figure 28: Multiple Device Download 34
Figure 29: VPN setting download to multiple devices 35
Figure 30: Download in Advanced Cloud mode 35
Figure 31: Configuration revision 36
Figure 32: Download in Advanced Device Mode 36
Figure 33: Download Right Click Menu 37
Figure 34: Apply Configuration Menu 37
Figure 35: Select Device for Apply Configuration 38
Figure 36: Apply multiple device configuration 38
Figure 37: Apply configuration status 39
Figure 38: Upload 39
Figure 39: Upload Options 40
Figure 40: Upload by adding as new device 41
Figure 41: Upload by updating the device 42
Figure 42: Upload configuration file 42
Figure 43: Upload menu from tree view 43
Figure 44: Restart Menu 43
Figure 45: Restart Multiple device status 44
Figure 46: Stop Firmware Menu 45
Figure 47: Stop Firmware Command 45
Figure 48: Start Firmware Menu 46
Figure 49: Start Firmware 46
Figure 50: Scan Menu 47

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

Figure 103: Add Device 86
Figure 104: Modify Device 86
Figure 105: Delete device 87
Figure 106: Add Master Protocol 87
Figure 107: Delete Channel 88
Figure 108: Add Station 88
Figure 109: Delete Station 89
Figure 110: Add Profile 89
Figure 111: Export Profile 90
Figure 112: Import Profile 90
Figure 113: Delete Profile 91
Figure 114: Add Row 91
Figure 115: Modify Row 92
Figure 116: Delete Row 92
Figure 117: Add Map 93
Figure 118: Modify Map 93
Figure 119: Delete Map 94
Figure 120: Auto Map Entire Profile Points 95
Figure 121: Auto Map Selected Profile Points 95
Figure 122: Auto Map Window 96
Figure 123: Adding Slave Profile 98
Figure 124: Copy/Paste option on Right Click 99
Figure 125: Multiple Copies Form 99
Figure 126: Profile Row Option 100
Figure 127: Multiple Row Modify Window 100
Figure 128: Search Option in Profile and Mapping 101
Figure 129: Search Option in Profile Rows. 101
Figure 130: Search Option in Mapping 101
Figure 131: Excel Export and Import 102
Figure 132: Excel Profile 102
Figure 133: Excel Import Pop-up 103
Figure 134: Configure Logging 104
Figure 135: Add Dialup 106
Figure 136: Add Dialup Window 107
Figure 137: Download 109
Figure 138: Delete Dialup 109
Figure 139: Delete Dialup 110
Figure 140: VPN/GPRS Network With SYNC Devices 111
Figure 141: Add VPN 112
Figure 142: VPN Pop-Up 113
Figure 143: VPN parameters 114
Figure 144: Download VPN 115
Figure 145: Edit VPN 115
Figure 146: Edit VPN Pop-up 116
Figure 147: Delete VPN 116
Figure 148: Delete VPN 117
Figure 149: Export VPN Certificates 118
Figure 150: VPN Diagnostics 118
Figure 151: Import VPN Certificates 119
Figure 152: Import VPN Certificate File Selection Window 119
Figure 153: Download Configuration File 121
Figure 154: Export XML file 122

Figure 155: Import XML file 123
Figure 156: Save to Revision 124
Figure 157: Revision Name 124
Figure 158: Load from Revision 125
Figure 159: Revision List 125
Figure 160: IP configuration 126
Figure 161a: Network Bonding 127
Figure 116b: PRP network 128
Figure 116c: HSR network 128
Figure 162: IP configuration Window 129
Figure 163: Redundancy Configuration 129
Figure 164: Add NAT Policies 130
Figure 165: Add NAT Rule 131
Figure 166: Add NAT Rule pop-up 131
Figure 167: Download NAT settings 132
Figure 168: Edit NAT rules 133
Figure 169: Delete NAT rules 133
Figure 170: Delete NAT policy settings 134
Figure 171: Route Configuration Menu 135
Figure 172: Retrieve Route Configuration 135
Figure 173: Route Table 135
Figure 174: Add Route 136
Figure 175: Modify Route 136
Figure 176: Delete Route 137
Figure 177: DNS Configuration Menu 137
Figure 178: DNS Settings 138
Figure 179: Ethernet Packet Capture Menu of Configured Device 138
Figure 180: Ethernet Packet Capture For Non configured Device 139
Figure 181: Switch-over Due To External Trigger 140
Figure 182: Self Switch-over 141
Figure 183: Redundant Configuration with IP Swapping 142
Figure 184: Redundant Configuration with No IP Switching 142
Figure 185: Channel Configuration for Achieving Redundancy 144
Figure 186: General Node Configuration for HSB 146
Figure 187: IP Switching Configuration for HSB 148
Figure 188: Configure Individual Interface for IP Switching 148
Figure 189: Redundancy Switch-over Details 150
Figure 190: HSB Configuration Easiness Change in download window. 151
Figure 191: Login page 152
Figure 192: Home page 153
Figure 193: Add Schedule 154
Figure 194: Add Transfer Task 155
Figure 195: Add User 155
Figure 196: Add Schedule 156
Figure 197: Add Folder 156
Figure 198: Parameterization through Transparent Channel 157
Figure 199: Enabling Encryption in TCP Channels 158
Figure 200: Certificates Window 159
Figure 201: Import Window 160
Figure 202: Generate Certificates 161
Figure 203: Download TLS Settings 162
Figure 204: Enabling SYNC DB Monitor 163

Figure 205: SYNC DB Monitor Icon in EasyConnect Toolbar 163
Figure 206: SYNC DB Monitor Window 164
Figure 207: Point ID is shown in Profile Configuration 164
Figure 208: Data Type Filtering 165
Figure 209: Status monitor showing Offline status 166
Figure 210: Alarm window 166
Figure 211: Watch window 166
Figure 212: Adding point in watch window 167
Figure 213: Adding columns to DB Monitor 167
Figure 214: Quick Filter 167
Figure 215: Tag List View 171
Figure 216: All Tag Configuration 172
Figure 217: Generic Settings 173
Figure 218: Node Settings 174
Figure 219: Kalki.io Cloud Settings 174
Figure 220: Adding a Logic variable 175
Figure 221: Adding a Diagnostic variable 176
Figure 222: Adding Special functions 191
Figure 223: Enabling the use of a profile row in Logic Engine 192
Figure 224: Exporting logic variables 193
Figure 225: Device Settings 195
Figure 226: Enabling Check for Firmware Updates 201
Figure 227: Pop-up for Automatic Up gradation 201
Figure 228: Model name prompt for older DCCP versions 202
Figure 229: Automatic upgrade prompt for incompatible DCCP version 202
Figure 230: DCCP update Link in Version Info 203
Figure 231: Version Info for devices with older DCCP Versions 204

List of Tables
Table 1: Software Requirements 15
Table 2: Hardware Requirements 15
Table 3: Advanced settings of the device 24
Table 3: License file parameters 29
Table 5: Version Information General Tab 49
Table 6: Version Information Advanced Tab 49
Table 7: Converter Parameters 62
Table 8: Configurable Parameters 63
Table 4: Auto map window 97
Table 5: Logging Configuration Parameters 105
Table 6: Dialup Parameters 108
Table 7: VPN Pop-Up Details 113
Table 8: VPN Parameters 114
Table 9: NAT parameters 132
Table 7: Channel Configuration Parameters for Achieving Redundancy 145
Table 8: General Node Parameters 147
Table 9: IP Switching Configuration Parameters 149
Table 10: Profile Configuration Details for Redundancy 150
Table 11: Kalki.io specific actions 172
Table 12: Tag list Generic Settings 173
Table 13: Tag list Node Settings 174
Table 14: Tag list Kalki.io Cloud Settings 175
Table 15: Diagnostic Variables 190
Table 16: Special Function Tags 191
Table 17: Time Synchronization Parameters 198
Table 18: Channel Parameters 199
Table 19: Client node Parameters 200
Table 20: Server node Parameters 200
Table 21: Models supported in different SYNC series 206
Table 22: GPC, DCCP & EC Compatibility Table 206
Table 23: Flag Mapping 207
Table 24: IEC 62439-3 Interoperability Table 209
Table 25: List of abbreviations 211

1
1. Overview
SYNC 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 12-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 front-end via the SYNC configuration
tool EasyConnect.
1.1. EasyConnect
The SYNC 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 can be used for:

• Mapping data specific point from device data to standard protocol format
• Update Module Configurations & Settings
• Update Module Firmware
• Monitoring and Diagnostics
• Troubleshooting

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 7, 8, 8.1, 10 32/64 bit
.Net framework .Net framework 4.5 or higher
Table 1: Software Requirements
1.2.1. Hardware Requirements

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

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 Website/ server – please contact support@kalkitech.com for the link
to download the installation 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.

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 EasyConnect.
• 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

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

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.

To apply the configuration, to enable the newly downloaded
Apply Configuration
configuration.

To upload the device configuration file from the SYNC device to
Upload
EasyConnect.
Restart To restart the SYNC device.
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.
To scan all the SYNC devices in the network. Scan will detect a
Scan device only if the device is connected in the network through its 1st
interface (lan0) and if it is in the same subnet.
To get the version and protocol details of the firmware in the
Version Information
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.
To add multiple routes, networks, matrix settings and all
Routing Configuration other settings available with ‘route’ command of Linux from
EasyConnect.
5. Diagnostics Menu
The Diagnostics menu contains tools that provide diagnostic functions. The options available in
diagnostic menu are Traffic Monitoring, PDC Diagnostics SYNC DB Monitor, Gateway Log and
Ethernet Packet Capture.
Figure 7: Diagnostic Menu
6. Tools Menu
Tools menu contains options to set EasyConnect parameters like Time-out settings.
Figure 8: Tool Menu

7. Preference Menu
Preference settings contains options to set Display language and option to choose tool chain
path. Tool chain would be required for
8. 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. Toolbar 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.

3
3. EasyConnect Application Modes
EasyConnect can be operated in two modes. Default Mode and Advanced Mode.
1. Default Mode:
Default mode can be used by devices using ‘klib’ based licensing.
2. Advanced Mode:
Advanced mode can be used by devices having certificate based licensing. License files are
highly secured X.509 based certificates. Each device will be uniquely identified using its serial
number. Also these devices shall be able to access/control using centralized Kalki.io instance
through a secure communication link. The connection will be secured with X.509 certificates
which will be established only if kalki.io connectivity license is installed in the device. User
can remotely configure device, read/control data objects or update firmware from kalki.io, if
connectivity license is installed in the device.
Configuration of devices with certificate based licensed can be done from Easy connect only in
advanced mode. Easy connect tool also would require product license and user license to run
in advanced mode. Any critical operation from EC will be allowed to the device only if the user is
authorised for the particular operation for the particular device.
In advanced mode there are again two modes possible which are Advanced Device mode and
Advanced Cloud mode. In Device mode all the operations & user request shall be directly send
to the device by connecting to device using its IP Address similar to Default mode.
However in cloud mode; all operations & user request shall be sending to the device through
kalki.io. This mode shall be used when the device is not directly accessible by Easy Connect.
There will be limited operations possible in Advanced Cloud mode.
Note: EasyConnect version 5.1.1 or above can be used in both Default and advanced
mode.

3.1. Mode Switching
Mode of the configuration tool can be changed in ‘Preferences’ settings menu item. Preferences-
>Edit Preferences. Refer Figure below.
Figure 11: Edit Preferences
Note: Change mode and then click ‘Apply’ to make effect the changes. EasyConnect
tool will be restarted with new mode settings.
Mode Switching while Log in

Below figure shows the user login screen of EasyConnect advanced mode. User can also switch
to default mode directly from the user login of advance mode EasyConnect using mode switch
link marked in below screen shot.
Figure 12: Mode switching from login screen

Device Advanced Settings:
Advanced Tab in Easy Connect Device settings shall be enabled only in Advanced Cloud Mode.
Upon clicking Advanced Settings tab, parameters settings required for connecting to kalki.io can
be configured.
Parameter Name Range Default Value Description

Device Latitude 0.0 Specifies the device latitude.
Device Longitude 0.0 Specifies the device longitude.
Device Cloud Primary 0 – 65535 secs 100 This is the time taken by the
URL Connect gateway to connect and get the
client URL from kalki.io.
Device Cloud Primary 100 Specifies the number of retries,
URL Retry Count the gateway will try to connect to
kalki.io to get client URL.
Device Cloud Socket 1 – 300000 60000 Specifies the maximum
Connection Time-out msecs time allowed to complete
the handshake of kalki.io
connectivity. For slow network,
higher value should be
configured.
Device Cloud Socket 1 – 65535 secs 10 Specifies the time after which
Connection Retry Delay the web-socket in the Gateway
will again try to connect to kalki.
io.
Device Cloud TCP Keep 1 – 65535 secs 10 This is the time period after
Alive Period which a frame is sent to keep
connection with kalki.io.
Device Cloud Ping Pong 1 – 65535 secs 300 Specifies the time interval at
Period which the gateway will send a
web-socket ping to the kalki.io.
Device Cloud Ping Pong 1 – 3600 secs 60 Specifies the maximum time
Time-out allowed get a pong back in
response to a ping sent by
gateway.
Table 3: Advanced settings of the device

4
4. License Management
4.1. EasyConnect Licensing
EasyConnect tool requires three licenses to run in advance mode.
1. Product License
2. User License
3. Kalki.io Cloud License
Login Screen of EasyConnect in Advance mode is shown below:
Figure 13: Login Screen of EasyConnect in Advance Mode
All three licenses for EasyConnect can be downloaded from Kalki.io with a unique password.
User needs to provide the same password while installing these licenses.
Note: Refer Centralized Management of SYNC Devices User Manual for details on
login to kalki.io and downloading required license for tools and devices.
Installing EasyConnect Product License:

Install product license using Install/Update Product License option in EasyConnect Login screen.
After browsing the license file provide the password that was used while downloading license
file from Kalki.io. A window with license details as shown below shall appears after successful
installation of Product license.
Figure 14: License Installation Screen

Installing User License:
Install User license using the Install Product License option in EasyConnect Login screen.
After browsing the license file provide the password that was used while downloading license file
from Kalki.io and click Install.
Figure 15: User License Installation Screen
On successful installation of User license, a window as shown below will pop up.
Figure 16: License Information Window

User can login with the user name as shown in the window and the password which was used
for downloading the license.
Note: Login password can be changed any time using Reset Password option in
Preferences settings.
Figure 17: Password Resetting Window
Installing Kalki.io Connectivity License:

Install Kalki.io Connectivity license using the Add Cloud License option in EasyConnect
Preference Settings. After browsing the license file provide the password that was used while
downloading license file from Kalki.io and click Install.
In Advanced-cloud mode EC uses connectivity license to create a secure tunnel with kalki.io.
Cloud connectivity licenses are the credentials used to authenticate this tunnel. This is required
only when the EasyConnect is in Advanced-Cloud mode and want to store device configuration
file and settings in the kalki.io.
Figure 18: Installing Cloud License

4.2. SYNC Device Licensing
SYNC Device license can be managed/updated using EasyConnect Configuration tool. Once
device is added in the project file, click on the Device License Tab on right pane as shown in
below image. This option shall be enabled only in Advanced Mode.
Figure 19: Device Licensing
It is necessary to install licenses in the SYNC Devices and import same in EasyConnect to work
in Advance mode. There are two licenses which needs to be downloaded in the gateway to
connect to the corresponding kalki.io.
1. Device License: Device license is certificate base license which is generated from kalki trust
store for the device firmware.
2. Kalki.io Connectivity License: Connectivity License shall be installed in the SYNC device to
connect to kalki.io.
Device and Kalki.io license files can be downloaded from kalki.io and can be imported and
installed in the SYNC Device using the ‘Install License to Device’ and ‘Install Device Cloud
License’ options available in Device License tab respectively.
Refer below Table for the description of the parameters in a License file.
Parameter Name Description
Serial Number Specifies the serial number for the device
Licensed Serial Port Specifies the number of Licensed serial ports for the device
Licensed Ethernet Port Specifies the number of Licensed Ethernet ports for the
device
Licensed IRIG B Available IRIG B is a time synchronization parameter
Note: This feature is not applicable to the SYNC device till
now
Number of Tags Specifies the number of tags that can be added for the device
Licensed Master Protocols Specifies all the Licensed master protocols for the device
Licensed Slave Protocols Specifies all the Licensed slave protocols for the device
Licensed Peer Protocols Specifies all the Licensed peer protocols for the device
Note: It is not applicable to the SYNC Device till now
Licensed Add On Modules Specifies the number of Licensed Add On modules

MAC Address This specifies the mac address of eth0 port of the gateway
Old Serial Number This specifies the old serial number present in the gateway
Valid From Specifies the validity of the license issued by the authority. It
displays the date and time of the certificate is valid from
Valid Till Specifies the expiry date and time of the certificate
Issuer Specifies the Common Name, Organisation name and Place
of the authority which issued the certificate
Cloud URL This specifies the kalki.io URL with which device can connect
to
Table 3: License file parameters
4.3. Installing Device License

Import device license and kalki.io cloud license from the file browse option provided in the Device
License window in the In the Device License window. Select all required files and provide the
password that was used for downloading the license. Refer below Figure.
Figure 20: Installing Device License
All parameters are automatically imported from the license file. After importing both the license
files, details inside an Device license tab shall display the license files.
Figure 21: Device License details

On successful installation of Device License, device is restarted automatically.
Note: The license should match with the device serial number present in the gateway.
Installing Kalki.io Connectivity License:

Import the kalki.io connectivity license into EasyConnect project file and then install the same in
device using Install Device Cloud License menu. Need to provide password that was used for
downloading the license from Kalki.io.
Figure 22: Kalki.io Connectivity License process
4.4. Devices Up gradation

SYNC devices which have legacy klib based licensing can be upgraded to Kalki.io based device
certificate license using EasyConnect. Details of steps to be followed are explained below.
1. Update DCCP to latest version using EasyConnect running in default mode

2. Restart the device and switch EasyConnect to Advanced device mode
3. Import the device license, to EasyConnect configuration project Device License tab
Figure 23: Device Upgradation

4. Click on ‘Install License to Device’ to install product license to the device. This operation
shall prompt device to change to advance mode from default mode
Figure 24: Installing License to Device
5. Proceed for up gradation by clicking ‘Yes’. This operation shall install new license in the
device. The device will get reboot after the installation.
Note: If required, user can upgrade the imported license. On successful installation of
the License, Device shall restarted automatically.

5
5. Device Settings
5.1. Download
‘Download’ option can be used to download configuration and other necessary files to the SYNC
Device.
Figure 25: Download Menu
‘Download’ option can be used to download configuration files, license files, update packages,
dial-up settings, VPN settings, SMS Settings, SNMP Settings, TLS Credentials, NAT Policies
and WEBHMI Settings to the device. In the download window, select Device Name from the list
of names configured in the project (eg: SS1, SS2 etc.), provide IP address of the device to which
the download operation is carried out. Select type of files which need to be downloaded such as
Configuration file, License files etc. Browse required files from PC and press download button to
activate the process.
Note: For a device outside the project context, select Device Name as “Other Device”
type and select appropriate model name of the device.
Note: After configuration file or license file download, restart device or stop and start
firmware.

Figure 26: Download files selection
Special Handling
HSB Devices: If HSB is configured for a device, then a alternate IP Address type named HSB
IP can be provided in download operation, so that files configuration file shall be downloaded to
main and stand by IP address.
Note: only configuration file can be downloaded using this mechanism. Other files need
to be downloaded to devices individually.
Figure 27: Redundant Device Download operation

Package Versioning: This option facilitates the user to assign default version number (1.0.0) for
the update packages with no version information while performing download operations.
Multiple Device Download: When ‘Download’ operation is initiated after selecting ‘Devices’ or
‘Configuration’ Nodes in easy connect tree menu and project file having one or more devices
configured. List of all the devices configured in the project shall be displayed. Select the devices
to be downloaded and specify the IP address of the device. While initiating the process download
status of every device shall be “Ready”. Once the download operation is completed, the status
changes to “Completed” for the devices for which operation is successful and “Failed” in the case
the download operation is failed.
Figure 28: Multiple Device Download

VPN Settings: VPN settings can be downloaded to a device by selecting the Download’ option
which shows by right-click on the VPN tree node in the configuration window.
Figure 29: VPN setting download to multiple devices
Download in Advanced Cloud Mode

Download operation in Advanced cloud mode shall transfer configuration file to Kalki.io with
revision number and description. Configuration bundles after reaching Kalki.io shall be pushed
to corresponding SYNC device in field automatically by Kalki.io. This function can only be used
for the device inside the project context in Advance mode.
In the download window, select the Device Name from the list of names in the configuration
project (eg: SS1, SS2 etc.), Proceed by clicking OK, This will prompt a new window to provide
description for the configuration revision before storing in Kalki.io. Refer below figures. Enter the
description for the Configuration file and Click ‘Save’.
Figure 30: Download in Advanced Cloud mode

Figure 31: Configuration revision
Download in Advanced Device Mode

Download operation in Advanced device mode shall download configuration file to the SYNC
Device. This function can only be used for the device inside the project context in Advance mode
In the download window, change Device Name if required; enter IP address of the device to
which the configuration is to be downloaded. Refer Figure.
Figure 32: Download in Advanced Device Mode
Note: Download configuration for all the devices present inside the project context
feature is not available in Advanced Mode.

Alternatively configuration file 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 below.
Figure 33: Download Right Click Menu
Note: Product License should be present in the device to download the configuration.
5.2. Apply Configuration

Use ‘Apply Configuration’ button to apply configuration to a device
Figure 34: Apply Configuration Menu

Apply Configuration is used after the download operation. Once the configuration file is downloaded
to the device, Apply configuration operation is used to activate the newly downloaded files.
Specify the IP address and the device name (eg: SS1, SS2 etc.) form the project file Refer
following Figure.
Figure 35: Select Device for Apply Configuration
Multiple Devices Operation

In-case ‘Apply Configuration’ operation is initiated by selecting ‘Devices’ or ‘Configuration’ Nodes
in easy connect tree menu and project file shall have one or more devices have been configured.
List of all the devices configured in the project shall be displayed. Select the devices to be
configuration need to be applied and specify the corresponding IP address of the device. While
initiating the process download status of every device shall be “Ready”. Once the operation is
completed, the status changes to “Completed” for the devices for which operation is successful
and “Failed” in the case the operation is failed.
Figure 36: Apply multiple device configuration

Download in Advanced Mode
In the Apply Configuration window, list of previously downloaded configurations shall be shown.
Select a Configuration revision and proceed by clicking ‘Apply’. The status will be shown as
message afterwards.
Figure 37: Apply configuration status
Note 1: This feature is restricted to the devices inside the project context.
Note 2: Multiple device applying configurations in advanced mode is not available

Upload.
5.3. 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 38: Upload

• To get Configuration File, LAN Settings and Web HMI Files, tick Configuration file, LAN
Settings File and HMI Files respectively. Refer following figure.
Note: HMI Files option will be enabled only for SYNC3000/SYNC4000 Devices.
Figure 39: Upload Options

5.4. Upload Modes
Mode 1: Add a new device to an existing project after upload
This mode is used to add new uploaded configuration details as a new device with in the active
project. Steps to upload and create a new device in the project are explained below.
• Provide IP address of the device from which the configuration file is to be uploaded
• Select the option “Import to the Configurations [Add as a new Device]”. Click Upload
Device get added in the project as a new device. For details refer following figure
Figure 40: Upload by adding as new device
Mode 2: Update a device in an existing project

This mode is used to replace and update an existing device in the active project opened in the
Easy Connect. Steps to upload configuration to existing device are explained below.
1. Provide IP address of the device from which the configuration file is to be uploaded
2. Select the option “Update the Device”.
3. Select the relevant device (eg.SS1, SS2 etc.).
4. Click Upload
5. The files in the configuration window will get updated with the files from the device. For
details refer following figure.

Figure 41: Upload by updating the device
Mode 3: Upload configuration to local PC

This mode is used to save device configuration files to a folder in local PC. Steps to upload
configuration files are explained below.
1. Provide IP address of the device from which the configuration file is to be uploaded.
2. Select option Save In.
3. Browse location to which configuration file need to be uploaded to. Refer following figure.
Figure 42: Upload configuration file

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 43: Upload menu from tree view
5.5. Restart Device

‘Restart’ menu is used to force restarts a SYNC device.
Figure 44: Restart Menu

Specify the IP address and the device name (Example: SS1, SS2 etc.) of the device to be
restarted and proceed.
Restarting multiple devices

Restart All can be used to restart the devices at once. This feature is used to restart all devices
in the project using a single click.
1. ‘Restart’ button on the toolbar is clicked after selecting ‘Devices’ or ‘Configuration’ node
in the tree menu.
2. Tool shall list all the devices configured.
3. Select devices to be restarted and specify the corresponding IP Addresses
4. Status of restart operation is displayed in status column as show below. Initially the restart
status of every device is “Ready”. 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.
Figure 45: Restart Multiple device status
Note: Multiple device applying configurations in advanced mode is not available.

5.6. Stop Firmware
Stop Menu is used to stop the GPC firmware running the SYNC Device.
Figure 46: Stop Firmware Menu
Specify the IP address and the device name (eg: SS1, SS2 etc.) of the device in question. Click
“Stop” to stop the firmware
Figure 47: Stop Firmware Command
Note: Multiple device operation in advanced mode is not available.

5.7. Start Firmware
Start Menu is used to start the GPC firmware running the SYNC Device.
Figure 48: Start Firmware Menu
Specify the IP address and the device name (eg: SS1, SS2 etc.) of the device in question. Click
“Start” to stop the firmware
Figure 49: Start Firmware
Note: Multiple device operation in advanced mode is not available

5.8. Network Scanning
Network scanning option is used to scan the LAN network and identify SYNC devices connected
with in the network.
Figure 50: Scan Menu
The details of live gateways connected to the network can be viewed using ‘Scan’. The available
information of the gateways include Serial key, Model Name, Interface name, IP address of
interfaces of the gateways, Net Mask, MAC Address, Product Key, Status, Gateway Interface,
Gateway Address, Cloud Status and IPv6 address 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 Figure
below
Figure 51: SCAN result

5.9. Version Information
SYNC devices software/firmware version Information can be fetched from device using Version
Information tab.
Figure 52: Version Information: For a device in a project context
In the version information retrieval window Specify the IP address and the device name (Example:
SS1, SS2 etc.) of the device in question. Click “ck” to retrieve version information. Refer Figure.
Version information have two tabs; General Tab advanced Tab. Save Version to file.

The Version Information can be saved in text format using Save button the version retrieval
details.
Device model Device Model Name

EasyConnect version Name EasyConnect Version Name
DCCP version Name Version of DCCP firmware in the device.
DCCP version running in device is secure mode or
Secure DCCP
non secure mode
GPC version Name Version of GPC firmware in the device.
Number of Licensed Master Protocols 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 add-on 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 device firmware.
Table 5: Version Information General Tab
Content details in Advanced tab are detailed below table.
Device Application Information Application Information of the device

CPU Speed Speed at which CPU is operating
RAM Total usable RAM
Flash Total Usable Flash Memory
RTU Firmware version (applies only to SYNC2111
RTU Version
device
Available Packages List of available packages on the device.
Table 6: Version Information Advanced Tab

5.10. Time Settings
Time Settings menu can be used to get and set device Time as well as time zone manually to
the SYNC device.
Get Time:
Get Time menu is used to retrieve data and time from SYNC device. Follow below specified
steps to get time from devices. Specify the IP address and the device name (eg: SS1, SS2 etc.).
Click ‘Get‘ to retrieve Time Settings for the device. Refer following Figure
Figure 53: Get Time

Set Time zone
This is used to set time zone in the device. Specify the IP address and the device name as per
the configuration file (eg: SS1, SS2 etc.) question. Click the Time-zone tab, choose the required
time-zone from the combo list and click ‘Set Time-zone’ to change device Time-zone.
Figure 54: Get Time

Set Time Settings:
a) Using system settings:

Write time to SYNC device from local PC system time. Specify the IP address and the device
name as per the configuration (eg: SS1, SS2 etc.). Click the Time tab, select the button ‘Use
System Settings’ and click ‘Set Time’ to set the selected time into the device.
Figure 55: Set System Time

b) Using manual settings:
Write a time to SYNC device. Time can be manual set by configuration interface provided in
EasyConnect. Specify the IP address and the device name as per configuration (eg: SS1, SS2
etc.). 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.
Figure 56: Set manual Time
Note: SYNC devices considers the time below Year 2000 as invalid. Hence time setting
below year 2000 is not recommended.

5.11. Update Firmware
Firmware for the device can be updated using ‘Update’ option. This involves update of ‘GPC’,
‘DCCP’ and ‘Update Package’.
• ‘gpc’ firmware is protocol conversion engine.
• ‘dccp’ firmware is interface between configuration tool and device.
Both gpc and dccp files can be browsed using options provided as shown in below screen shot.
Both the files will get updated separately. For SYNC2111 and SYNC2101 devices, FRTU and
MRTU image can also be updated respectively using “Update Firmware” option.
Note: Only bundled firmware (in the format of tar.gz) can be updated in advanced
mode.
Specify the IP address and the device name as per the configuration (eg: SS1, SS2 etc.). Click
“OK” to update the changes. Refer following Figure.
Note: Restart required after ‘Update
Figure 57: Update firmware window

6
6. 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 58: Traffic/Diagnostics Monitor
Please note that traffic through TCP port number 2400 is not blocked by the workstation firewalls
or anti-virus applications. It is absolutely necessary for the proper working of this function

7
7. User Management
EasyConnect Inbuilt User Management is available only in Default mode
7.1. User Authentication

EasyConnect starts with a login window, as shown in the figure (EasyConnect Login) below:
Figure 59: 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.
7.2. Configuring Users and Roles

Default administrator can access the user management tool. The administrator has the permission
to create users, roles, change passwords and assign roles to them. Management of User can be
done using user management section as shown in the figure.
Figure 60: User management Menu

7.2.1. Roles
Roles shall be created before creating an 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 61: Role Creation/ Modification
To modify a role, select the particular role which needs to be modified and click on the Edit
button. The fields can then be edited.
To delete a role, select the role which need to be deleted from the role tree and click Delete.

7.2.2. Users
Management of user is done from 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.
Figure 62: User Creation/Modification
To modify a role, select the use which needs to be modified and click on the Edit button. In order
to change the password, check the ‘Change Password’ option.
To delete a role, select user which need to be removed and click Delete.

8
8. 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 63: Audit Trail
The log contains the user name, the activity the user performed and the timestamps at which it
was done as shown in Figure (EasyConnect Log).
Figure 64: EasyConnect Log

‘Advanced Filter’ option is available for filtering the log based on user name or timestamps.
Figure 65: Advanced Filter
The navigation buttons will be disabled when a filter is applied. Click ‘Remove Filter’ to remove
the filter options.

9
9. SMS Based Configuration
Some parameters of SYNC Device can be used configured over SMS (short message service)
if the device is connected to the cellular modem. Modem can also be used to send critical field
data as power outage indications.
Protocol Node Configuration is only available when IEC 1107 Master protocol Profile.
9.1. SMS Port Settings For Workstation PC

To configure SMS Settings for the Modem connected to configuration workstation PC (where
EasyConnect tool is installed).
• Configure SMS Port Settings by selecting it from the ‘Tool’ menu. Refer the following
figure.
Figure 66: Select SMS Port Settings.

• Save SMS Port settings.
To test the SMS port, click on ‘Test’ button. Refer the following figure.
Figure 67: Test SMS Port Settings
Converter Parameters shown below are to be filled.
Parameter name Range/Optional Default value Description

values
Location identification SYNC Device location
N/A
code Identification code
Location identification
N/A SYNC Device Location Name
Name
Table 7: Converter Parameters
9.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 SYNC device.
Figure 68: Add SMS Settings

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

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 SIM card
SIM Card Number N/A
used with SYNC device
Phone number of the modem
Admin 1 Mobile
N/A connected to Sync5000 (First
Number
redundant server)
Phone number of the modem
Admin 2 Mobile
N/A connected to Sync5000
Number
(Second redundant server)
Table 8: Configurable Parameters

• Check the ‘SMS settings’ box in the Download command window as shown in the following
figure and click ‘Download’.
Figure 69: SMS Settings Download
Note: Restart is required after downloading the settings for the changes to take effect.

9.3. Send Configuration SMS
Right click on ‘Devices’ or a particular device and select the option ‘Send SMS’.Refer the following
figure
Figure 70: Send SMS
Select the node for which configuration information has to be updated. Once its selected, click
on the button ‘Send SMS’ to send configuration information from EasyConnect to SYNC device
in field. Once configuration is successfully send from tool, device shall be highlighted in Green
colour otherwise it shall be Red.
Figure 71: Send SMS Window

9.4. Manage Admin Contact
SMS settings can be done only from the Administrator contact numbers. Maximum two
administrators are allowed per device.
Contact number of both administrator can be changed only directly from configuration tool. Menu
Change SMS Admin menu is used to change the Configuration administrator contact number
Figure 72: Change Admin

The Change Admin form appears through which we can change the admin and the corresponding
mobile number. Refer the following figure.
Figure 73: 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 74: Delete SMS Details
Then check the ‘SMS settings’ box in the Download command window as shown in Figure: SMS
Settings Download and click ‘Download’.

10
10. 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 75: 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.

11
11. 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 76: DB Delete: 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 gateway in which
the DB has to be deleted.

Figure 77: 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’.
Figure 78: Deleting Database File in multiple devices

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.
Figure 79: DB Delete window

12
12. Device Logs
Device Log facilitates an option to get the four different logging such a Device, Device Access
Log, Application Log and Communication Log.
Select Diagnostics->Device Logs for displaying the log window. Refer the Figure 1 for details:
Figure 80: Device Logs

12.1. Device Log
On clicking Retrieve Logs both Diagnostic logs and PDC logs are displayed in the same window.
User can filter the logs as per the requirement.
I. Retrieve Log
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: SYNC3000-M3). Click on Retrieve Log. Refer below
figure.
Figure 81: Retrieve Log Other Device
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.
Click on Retrieve Log. Refer below figure.
Figure 82: Retrieve Log Project Context

II. Filter Log
On selecting Retrieve Log both Diagnostics and PDC Logs are displayed. User has the option
to filter the Logs on the basis of Source and Message type. After selecting appropriate filter
mechanism user can retrieve the logs. Refer below figure
Figure 83: Filter Log
III. Delete Log File

User can delete the log file created from the device on clicking the Delete Log File button. Refer
below figure.
Figure 84: Delete Log File

IV. Export CSV
User can Export CSV file and save to a desired location by clicking Export CSV button. Refer
below figure.
Figure 85: Export CSV
V. Close
User can close the Device log window by clicking on Close button. Refer below figure.
Figure 86: Close

12.2. Device Access Log
Device Access Log can save to a location the profile of the EasyConnect commands performed
upon a particular converter up-to the past 90 days.

Specify the IP and select the device name as “Other Device”of the gateway in question. Specify
the appropriate model name (Example: SYNC3000). Specify the start and end date. Click on
Retrieve Log to obtain the log. Refer below figure.
Figure 87: Device Access Log Other Device

Specify the start and end date. Click on Retrieve Log to obtain the log. Refer below figure.
Figure 88: Device Access Log Project Context

12.3. Application Logs
Application Logs command can be used to retrieve the VPN and Dial-up logs. This can be used
to troubleshoot the VPN and Dial-up Functions. For starting the log, select the type of log (VPN or
Dial-up) and file to which the log has to be retrieved,Click the ‘Start’ button. For retrieving the log
click the ‘Retrieve Log’ button,this will stop the VPN or Dial-up 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 EasyConnect will show an error message “Cannot find the file”.

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 Dial-up or VPN. Click ‘Start’ button. Refer
below figure.
Figure 89: Application Log Other Device
Once this is done, click ‘Retrieve Log’ in the dialog box after the time you want to see the VPN/
Dial-up details.

Select the type of application whose log You wish to receive, Here the available options are Dial-
up or VPN. Click ‘Start’ button’. Refer below figure.
Figure 90: Application Log Project Context
Once this is done, click ‘Retrieve Log’ in the dialog box after the time you want to see the VPN/
Dial-up details.
• 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.

12.4. Communication Log
Communication Logging implementation is to view all protocol communication logs and diagnostic
logs.

Specify the IP address of the device and select the device name as “Other Device”. Then click
on the ‘Retrieve Log’ button in the dialog box so that you can retrieve log. Refer below figure.
Figure 91: Communication Log Other Device
1) For a device in the project context:

Specify the IP address of the device and the device name (Example: SS1, SS2 etc.) of the
gateway from which the log needs to be retrieved. Then click on the ‘Retrieve Log’ button in the
dialog box so that you can retrieve log. Refer below figure.
Figure 92: Communication Log Project Context

13
13. 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 93: 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 94: SYNC API: Add New Protocol

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 95: 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 96: SYNC API: Configure parameter

5.) The option under display control corresponding to the added parameter allows to choose the
display either to be a text box or Combo box. Similarly the option under Cell Editable allows to
choose between true or false. If true, tool shall have the provision to change the value range of
the parameter even after the protocol has been created, if false tool shall 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 97: 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 98: SYNC API: Node Parameters

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 99: 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 the system to make this protocol exclusive for that device. To delete
the added firmware click on Del (-) option.
Figure 100: SYNC API: Add Firmware Details

10.) Click on save option to save the changes made and then click on Save List to save the
protocol created. ‘Save List’ menu shall prompt to restart the tool with a warning dialog box.
Figure 101: SYNC API: Save Changes, Warning Message
11.) After the EasyConnect has been restarted this protocol will available in master protocols
under protocol configuration. Refer following figure
Figure 102: SYNC API: Protocol Configuration Window

14
14. Gateway Configuration
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
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.

14.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 103: 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 104: Modify Device

3. To delete the selected device, right click the selected device, and choose Delete as shown in
the Figure (Delete device) below:
Figure 105: Delete device
4. Add Master channels to the device model as shown in the Figure (Add Master Protocol) below:
Figure 106: Add Master Protocol

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 107: Delete Channel
6. Add Node or Station as shown in Figure (Add Station) below:
Figure 108: Add Station

7. Delete a station by selecting Delete from the menu displayed on right by clicking on selected
station.
Figure 109: Delete Station
8. To add Master Profile, right click on Node and select Add Profile.
Figure 110: Add Profile

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 111: 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 112: Import Profile

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

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 115: Modify Row
12. To delete rows, select rows from the profile grid and click Delete Row on the right pane.
Figure 116: Delete Row

14.2. Add Slave Channel and Node
To add a slave channel and node follow the procedures mentioned above section add master
channel and node.
14.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 117: 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 118: Modify Map

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 119: Delete Map
14.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):

Figure 120: 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 121: Auto Map Selected Profile Points

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 122: Auto Map Window
14.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.

Sl. No Parameter Details
Indicates the node number whose profile needs to be
1 Source Node
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 the mapping
2 Destination Node
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 carried
5 Source Types
out.
Indicates suggested destination data type for the specific
source type to which mapping is carried out. This is a
6 Destination Types
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
Destination Start can change the start address but it will again undergo
7
Address 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 4: 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.

14.3.3. 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 123: 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.

14.4. Ease of Configuration
14.4.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 124: 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 125: 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.

14.4.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 126: Profile Row Option
14.4.3. Multiple Row Modify Option

This feature allows user to modify properties of multiple rows together in profile and mapping.
User can select the multiple 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 127: Multiple Row Modify Window

14.4.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 128: Search Option in Profile and Mapping
Figure 129: Search Option in Profile Rows.
Figure 130: Search Option in Mapping

14.4.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 131: 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 132: Excel Profile

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 the
worksheet. 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 Pop-up) 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 133: Excel Import Pop-up

15
15. Configure Logging
In EasyConnect under Device Settings a node called Logging is added. On clicking Logging
a window for configuring the Logging appears. In the configuration window user can Enable/
Disable three types of logs namely:
• Communication Log
• Diagnostic Logging
• PDC Logging

Refer the below figure for configuring the logging parameters.
Figure 134: Configure Logging
Refer the table below for the Logging Configuration Details:
Parameter
Range Default Value Description
Name
Communication Enable/Disable Disable Enable/Disable Communication Log
Log Note: For details Device Logs ->
Internal Logging.
Internal Log /tmp/ The local folder in which the
Directory Communication logs are stored.
Diagnostic Enable/Disable Disable Enable/Disable the logging of
Logging Diagnostic variables.
Diagnostic Event/Periodic Event Event: In this mode the digital points
Logging Mode are logged when a value change
occurs for that point.
Periodic: In this mode all analog
points are logged periodically. The
period is configured in Diagnostic
Log Period

Parameter
Name
Diagnostic Log 1-1440 minutes 60 This parameter is configurable only
period if the Diagnostic Logging Mode
is Periodic. The period in which
analog points have to be logged is
configured here.
PDC Logging Enable/Disable Disable Enable/Disable PDC Logging
Log Entries 50-5000 200 Number of entries in the log created.
Table 5: Logging Configuration Parameters

16
16. Dialup Configuration
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 135: Add Dialup

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 136: 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

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
values.
Password Configure if provided by service
values.
Table 6: Dialup Parameters

3. Download the settings via File Download option and check the option Dialup Settings.
Figure 137: 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 138: Delete Dialup

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 139: Delete Dialup

17
17. VPN Configuration
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 140: VPN/GPRS Network With SYNC Devices

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 141: Add VPN

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 142: VPN Pop-Up
Parameter name Range/ Optional Default value Description

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.

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 143: 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/ Optional Default value Description

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

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 144: 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 145: Edit VPN

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 146: 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 147: Delete VPN

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 148: 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.

Figure 149: 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 150: VPN Diagnostics

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 151: Import VPN Certificates
User can select the certificates that need to be imported and then click on the Import button.
Figure 152: Import VPN Certificate File Selection Window

18
18. 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.

19
19. Configuration File Management
19.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 153: Download Configuration File

19.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 154: Export XML file

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 155: Import XML file

19.3. File Revision
19.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 156: Save to Revision
An option to enter a revision name is provided as shown in Figure (Revision Name) given
below.
Figure 157: Revision Name
Up to 10 versions of a file configuration can be saved.

19.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 158: 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 159: Revision List
The present configuration will be replaced with the selected version.

20
20. Network Configuration
20.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 160: 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.
20.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

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 161a: 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 switch-over 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.

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

20.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 162: IP configuration Window
Figure 163: Redundancy Configuration

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
20.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 164: Add NAT Policies
Note: On addition of NAT Policies, the Network node parameter ‘Enable IP Forwarding’ will be
set to True.

20.4.1. To add NAT Rules
Click on ‘Add Rule’ as shown in Figure (Add NAT Rule) below.
Figure 165: Add NAT Rule
A window appears as shown in Figure (Add NAT Rule pop-up) shown below. Enter the parameter
values.
Figure 166: Add NAT Rule pop-up

NAT Rule parameters are explained in table 7 (NAT Parameters) given below:
Parameter name Range/ Optional values Description

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 167: Download NAT settings

20.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 168: Edit NAT rules
20.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 169: Delete NAT rules

20.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 170: 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’.
20.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.

I) Get Current Routing Table:
• Click on settings->Routing Configuration.
Figure 171: 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 172: Retrieve Route Configuration
Figure 173: Route Table

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

• Get routing table as described in above section
• Click on Add (Refer Figure). Configure the parameters coming in the pop up window and
click on Save button
• Click on Save button
Figure 174: Add Route
III) Modify Routing Table
EasyConnect provides option to delete an already added route from the device.
• Click on Modify (Refer Figure)
Figure 175: Modify Route

IV) Delete Routing Table:
EasyConnect provides option to delete an already added route from the device
• Click on Delete (Refer Figure)
Figure 176: Delete Route
20.6. DNS Configuration

This option is available in the advance mode. DNS address of the SYNC device can be configured
using ‘DNS Configuration’ option provided. The DNS can only be configured for the devices
inside the project context. Refer Figure.
Figure 177: DNS Configuration Menu
1. Select a device
2. Click on ‘DNS Configuration’. DNS settings menu is also available in network Interface
configuration section
3. Enter the IP of the SYNC device which shall provide the list of DNS address already present
in the Device
4. Click on ‘+’ symbol to add or ‘-‘symbol to delete a DNS. Refer below figure
5. Make necessary changes and Click OK
6. The status of updation will be shown as message

Figure 178: DNS Settings
Note: Device Restart is required after setting the DNS configuration.
20.7. 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.

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 179: Ethernet Packet Capture Menu of Configured Device

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 180: 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 EasyConnect
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

21
21. Redundancy Configuration
This section describes how redundancy is implemented using the SYNC series of devices.
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.
21.1. Types of Switch-over

SYNC device support the following types of switch-over:
21.1.1. External Trigger Switch-over
Figure 181: Switch-over Due To External Trigger
In this mode, the device will not take a switch-over decision on its own. The switch-over 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.

21.1.2. Self Switch-over
Figure 182: Self Switch-over
Self switch-over mechanisms extend the functionality of external trigger switch-over by providing
for a switch-over 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.
21.2. IP Switching Mechanisms

The devices involved in a Hot-Standby configuration support the following IP switching
mechanisms during a switch-over. These mechanisms can be configured independently for each
of the available Ethernet interfaces device.
21.2.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.

Figure 183: Redundant Configuration with IP Swapping
21.2.2. No IP Switching
Figure 184: 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 switch-over.
21.3. 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 switch-over 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 switch-over
• Both devices should have the same hardware configuration. The software configuration

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 time-outs need to be adjusted to avoid unnecessary switch-over
• 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
switch-over 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.
21.4. 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 switch-over from an external Master.
External Trigger Point: this command point is used to give the switch-over command to the
device from an external Master.
21.5. 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.
21.5.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.

21.5.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 185: 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
6 provides a redundant link COM1-COM16 value from #5
COM Port Name
to #5
An integral Should be one of the
Serial communication value should be following recommended
7 Baud Rate
parameter provided as baud values:
rate

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 time-out for reading/
17 Select Time-out 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 time-out
Response in milliseconds for
19 500 - 5000
Time-out 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 time-out
Channel
in milliseconds for
21 Establishment 500 - 5000
HSB messages with
Time-out
acknowledgment.
Table 7: Channel Configuration Parameters for Achieving Redundancy

21.5.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 186: General Node Configuration for HSB
The following Table 9 (General Node Parameters) describes each of the configurable options for
the node parameters:
SL No: Name Description Range Required Value

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
Switch-over Switch-over type for the
2 triggered /
Type device
Self

SL No: Name Description Range Required Value
The switch-over
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 8: General Node Parameters

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 187: 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 188: Configure Individual Interface for IP Switching

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-
Address A/B/C IP address
warm.
Valid Subnet
Subnet mask for the
Warm range for
Subnet configured IP
warm
address
Table 9: 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 switch-over commands to the device. Any of these
points can be added under a HSB profile.
Sl No: Name Description Type Required Value

0 → Main Device
Used to determine
Binary Input / 1 → Standby
1 ID whether the device is
Analog Input Device
Main or Standby
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 Switch-over 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
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

Sl No: Name Description Type Required Value
Used to determine 0 → Warm
Binary Input /
6 State whether the other device 1 → Hot
Analog Input
is currently Hot or Warm
Table 10: Profile Configuration Details for Redundancy
Figure 189: Redundancy Switch-over Details

21.5.4. Redundancy Switch-over 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.
21.5.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 190: HSB Configuration Easiness Change in download window.

22
22. 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.
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.

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 191: 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 - Web-Server User Manual.

Figure 192: 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.

23
23. 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.
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 Time-out.
• 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 193: Add Schedule

Figure 194: Add Transfer Task
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 Roll-over Limit as
shown in Figure (Add Folder). The size of the specified folder will be checked and limited
to the roll-over limit in the scheduled interval.
Figure 195: Add User

Figure 196: Add Schedule
Figure 197: Add Folder

24
24. 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 198: Parameterization through Transparent Channel

25
25. 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 199: 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.

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 200: 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.

Import:
If Import option is selected, the following wizard appears as shown in Figure (Import Window),
where the required files can be imported.
Figure 201: 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.

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 202: Generate Certificates

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 203: Download TLS Settings

26
26. 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 204: 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 205: 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.

Figure 206: SYNC DB Monitor Window
Figure 207: Point ID is shown in Profile Configuration
26.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.
26.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.
26.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.

26.2. Function Keys
The following buttons are used in the SYNC DB Monitor to start, stop or refresh the Monitoring
window:
26.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
26.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.
26.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.
26.3. Supported Features

The SYNC DB Monitor provides various features such as Channel Filtering, Data Type Filtering,
Status Monitor, Alarm Window and Watch Window.
26.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.
26.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 208: Data Type Filtering

26.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 209: Status monitor showing Offline status
26.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 210: Alarm window
26.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 211: Watch window

Figure 212: Adding point in watch window
26.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 213: Adding columns to DB Monitor
26.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 214: Quick Filter

27
27. Self Supervision
Self Supervision feature provides the provision for detecting internal fault and monitor various
status points. If a fault condition is triggered, then the corresponding status point is set.
EasyConnect provides the option to configure these status points under the ‘Diagnostics’ Node
under ‘Tag List’.
In EasyConnect the diagnostic variables are grouped under different categories namely:
1. Device INFO
2. Hardware
3. Application
4. Channel Diagnostics
5. Node Diagnostics
6. Interface
27.1. Device INFO

The diagnostic variables coming under Device INFO and their definitions are listed below:
• CPU Usage: Provides information about percentage of CPU Used.
• CPU Alarm: If CPU Usage value goes above the Event Trigger Limit configured, the CPU
Alarm is updated with value ON, else it is updated with value OFF.
• RAM Usage: Provides information about RAM used.
• RAM Alarm: If percentage of RAM Used goes above the Event Trigger Limit configured,
the RAM Alarm is updated with value ON, else it is updated with value OFF.
• ROM Usage: Provides information about ROM used.
• ROM Alarm: If percentage of ROM Used goes above the Event Trigger Limit configured,
the ROM Alarm is updated with value ON, else it is updated with value OFF.
• File System Status: Provides information about the file system present in the device. If
file system is proper then File System Status is updated with ON, else it is updated with
value OFF.
• Restart Reason: To get the reason of last time restart of firmware.
• Last SYNC Time: The time at which last Synchronization has occurred.
• Time Since Last Sync Time: The time elapsed after last SYNC Time.
• Time Sync Status: Validity of current time.
• Device Healthiness: Healthiness of the device derived from the Node diagnostic points.
Is ‘Healthy’ if all the nodes connected, ‘Low warning’ if 50% or more nodes are connected,
‘High warning’ if less than 50% nodes are connected and ‘unhealthy’ if all the nodes are
disconnected. (Profile should be added for nodes. Only externally connecting master
nodes are considered)
• Last commissioning Date and Time: The time at which the device is configured using
EasyConnect recently.
• Last License update date and time: The time at which the device License is updated.
• Last User Access Date and Time: The time at which the device is accessed using
EasyConnect for any activity recently.
• Up Time: The time at which the firmware is UP.

27.2. Hardware
The diagnostic variables coming under Hardware and their definitions are listed below:
• RTC Status: Provides the status of the RTC chip present in the device. If battery is present,
then RTC Status is updated as ON, else OFF value is updated.
• Local Remote Status: To get the position of LR switch.
• Card Status (1-7): To get the status of the corresponding card in FRTU (SYNC2111
variants).
27.3. Application
The diagnostic variables coming under Application and their definitions are listed below:
• DIALUP Status: DIALUP Process is running or not running.
• NTP Status: NTP is running or not running.
• PTP Running Status: PTP is running or not running.
• SMS Status: If SMS can be sent successfully, then SMS Status is updated as On, else it
is updated as Off.
• SNMP Status: SNMP Process is running or not.
• SW Watchdog Status: If DCCP is running or not.
• VPN Status: VPN Process is running or not.
• Web HMI Station Control: Used for enabling /disabling control commands from HMI.
• Web HMI Control Status: Used to store the current status of Web HMI Station Control.
• Web HMI Status: Web HMI process is running or not.
27.4. Channel Diagnostics

• Channel Healthiness: Healthiness of the channel derived from the Node diagnostic
points. Is ‘Healthy’ if all the nodes connected, ‘Low warning’ if 50% or more nodes are
connected, ‘High warning’ if less than 50% nodes are connected and ‘unhealthy’ if all the
nodes are disconnected. (Profile should be added for nodes. Applicable for IEC101/104
and DNP3 Masters)
• Bad COT Counter: Is counted when master receives any bad COT (IEC101/104 Master)
• Fragment Received Counter: Count of Fragments Received. (DNP3 Master or Slave)
• Fragment Sent Counter: Count of Fragments Sent. (DNP3 Master or Slave)
• Frame Error Counter: This is the counter frame received with a wrong address, or an
invalid frame (frame not matching with header info)or an incomplete frame. (IEC101/104
master)
• Frame Received Counter: Count of the frame received. (IEC101/104 and DNP3 Master/
Slave)
• Frame Sent Counter: Count of the frame sent. (IEC101/104 and DNP3 Master/Slave)
• Remote Error Counter: This is the count of ASDUs received by a master channel with
COT remote error. (IEC101/104 Master only)
• Request Counter: Number of request. For a master any application frame sent is
considered as request. And for slave any application frame received will be counted as
request. (Applicable for IEC101/104 and DNP3 Masters/Slaves)
• Response Counter: Number of response. For a master any application frame received
is considered as response. And for slave any application frame sent will be counted as
response. (Applicable for IEC101/104 and DNP3 Masters/Slaves)
• Unknown Address Counter: This is the count of ASDUs received by a master channel
with COT unknown IOA (IEC101/104 Master only)

27.5. Node Diagnostics
• Buffer Overflow Status: Indicates if buffer of the slave node configured has overflowed
or not. Applicable for slave nodes of IEC 104, IEC 101, IEC 103 and DNP 3.
• Node Request Counter: Number of requests under a node. For a master any application
frame sent is considered as request. And for slave any application frame received will be
counted as request.
• Node Response Counter: Number of response under a node. For a master any application
frame received is considered as response. And for slave any application frame sent will be
counted as response.
• Node Remote Error Counter: This is the count of ASDUs received by a master channel
with COT remote error. (IEC101/104 Master only)
• Node bad COT Counter: Is counted when master receives any bad COT (IEC101/104
Master).
• Node Unknown Address Counter: This is the count of ASDUs received by a master
channel with COT unknown IOA (IEC101/104 Master only)
27.6. Interface
• Ethernet port status: Indicates which all ethernet ports are connected with cable.
• Serial Port Status: Port (1 – 12): Indicates if the configured Serial port is used or not.
Note: Refer ‘Tag list’ section for the details of Configuring Diagnostic Variables.

28
28. Tag List
In Tag List, EasyConnect provides user the option to Configure Alarms and Events under the ‘All’
node and add variables under ‘Logic’, ‘Diagnostics’, ‘Special Function’ nodes.
• All
Note: Please refer Web HMI user manual for more details.
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
• Diagnostic Variables
Figure 215: Tag List View

28.1 ‘All’ Tags
Special actions on tags created in configuration file are done in ‘All Tags’ Configuration section.
Configuration of Events, Alarms, Logging, and Enable push for Kalki.io and enable Event push
for all the points configured under each master protocol nodes. In the configuration, user can
also configure Periodic Push’, ‘Events Push’ and ‘Commands’ for the points configured.
It is necessary to click on ‘Save Changes’ before downloading a configuration in advance mode.

Refer Figure.
Figure 216: All Tag Configuration
The description of various Actions which can be configured in the Tag list under “All” are given
below:

Periodic Push The points configured for periodic push are pushed to kalki.io after
every 'Integrity push period' mentioned in the cloud settings parameters
under 'Settings' tab.
Push Events The points configured for 'events push' are pushed to kalki.io whenever
an event is generated from external slave.
Command Analog/Digital Output points shall be enabled for kalki.io as command
points from EasyConnect so that these points can be operated from
kalki.io. An output mapped to kalki.io will also be executable from any
other slave, if mapped.
Table 11: Kalki.io specific actions

28.1.1. Settings
Configuration of device and node specific settings relevant for TAG actions is available in Settings
Tab. The parameters are categorised under three headings i.e. General Settings, node settings
and Cloud Settings.
User can configure kalki.io specific parameters under ‘Cloud Settings’ for Periodic and Events
push configuration. These parameters will only be applicable to the gateway if the device is in
advanced mode.
Note: Events and Alarm Configuration will be available only in the ecc file. It cannot be
obtained while exporting/Importing the configuration file.
Generic Settings
Figure 217: Generic Settings
Details of Generic settings are explained in below table
Parameter name Range/Optional Default Description

values value
Instantaneous Data Enable/Disable Disable Enable/Disable Instantaneous Data
Logging Logging. This must be enabled for
viewing instantaneous data values in Web
HMI
Historic Data Enable/Disable Disable Enable/Disable Historic Data Logging.
Logging
Historic Data 300-100000 900 Specifies how often the instantaneous
Logging Interval data to be written to the database.
(300-100000sec)
Event Data Enable/Disable Disable Enable/Disable event data logging. This
Logging must be enabled for viewing/configuring
Events and Alarms.
Maximum Event 1 – 10000* 1000 Indicates maximum number of events that
Data Entries can be kept in flash. When the number of
entries exceeds this limit, earliest entries
will get deleted.
Flash Write Interval 1-86400 180 Specifies how often the entries in the data
(1-86400min) log table should be copied to the Flash.
Table 12: Tag list Generic Settings

Node Settings
Figure 218: Node Settings
Details of Node specific settings are explained in below table

values
Node Name All Master As Configured All the master protocol nodes
Protocol nodes
Maximum Historical 1 – 10000 1000 Indicates maximum number of
Data Entries (1- data entries in the Historic data
10000) log table. Total number of entries
in the historic data table will be
Maximum Historical Data Entries
*Total number of points enabled
for Historic data logging. When
the number of entries exceeds
earliest entries will get deleted.
Stations As Configured As Configured Station List for each node
Bays As Configured As Configured Baylist for each node
Table 13: Tag list Node Settings
Kalki.io Cloud Settings
Figure 219: Kalki.io Cloud Settings
Details of kalki.io settings are explained below
Parameter Name Range/Optional Default Value Description

Value
Event Queue Size 1 - 65535 256 Specifies the maximum number
of events which will be queued to
report to kalki.io if the connection
is not established or line is busy.

Event Push Retry 1 -300 secs 10 This specifies the time period
Period after which the events are
again pushed to kalki.io if
the acknowledgement is not
received from kalki.io for those
events.
Integrity Push 00:00:10 This specifies the period after
Period which all the points enabled
for Cloud periodic push in the
Configuration are pushed to
kalki.io.
Table 14: Tag list Kalki.io Cloud Settings
28.2 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.
The properties of the logic variable can be set as shown in the figure (Adding a Logic variable)
below.
Figure 220: Adding a Logic variable

28.3 Diagnostic Variables
For each SYNC device, there will be a pre-configured list of device-specific diagnostic 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. The Diagnostic variables are further classified
into Device INFO, Hardware,Application, Channel Diagnostics, Node Diagnostics and Interface.
A diagnostic variable is added by using the Add row button. The available device specific
variables are listed as shown in the figure (Adding a Diagnostic variable) below and any one can
be chosen. Unlike other profile points, a diagnostic variable’s properties cannot be edited. The
Diagnostic variable can also be used in the Logic Engine like all other protocol points.
Figure 221: Adding a Diagnostic variable
The system variables that are currently available are listed in below table
Supported
Variable Functionality Values Dependence
Models
Device INFO
CPU Usage Provides 0 - 100 All Models 1. Firmware should
information about support global master
percentage of 2. License of global
CPU Used. Master
3. DCCP Version
2.16.0 or higher
4. GPC Version 3.1.0
or higher
CPU Alarm If CPU Usage ON/OFF All Models 1. Firmware should
value goes support global master
above the Event 2. License of global
Trigger Limit Master
configured, the 3. DCCP Version
CPU Alarm is 2.16.0 or higher
updated with 4. GPC Version 3.1.0
value ON, else it or higher
is updated with
value OFF.

Supported
Models
RAM Usage Provides All Models 1. Firmware should
RAM used 2. License of global
Master
3. DCCP Version
2.16.0 or higher
or higher
RAM Alarm If percentage ON/OFF All Models 1. Firmware should

of RAM Used support global master
goes above the 2. License of global
Event Trigger Master
Limit configured, 3. DCCP Version
the RAM Alarm 2.16.0 or higher
is updated with 4. GPC Version 3.1.0
value ON, else it or higher
is updated with
value OFF.
ROM Usage Provides All Models 1. Firmware should
ROM used. 2. License of global
Master
3. DCCP Version 2.16.0
or higher
4. GPC Version 3.1.0 or
higher
ROM Alarm If percentage ON/OFF All Models 1. Firmware should
of ROM Used support global master
goes above the 2. License of global
Event Trigger Master
Limit configured, 3. DCCP Version 2.16.0
the ROM Alarm or higher
is updated with 4. GPC Version 3.1.0 or
value ON, else it is higher
updated with value
OFF.
File System Provides ON/OFF All Models 1. Firmware should
Status information about support global master
the file system 2. License of global
present in the Master
device. If file 3. DCCP Version 2.16.0
system is proper or higher
then File System 4. GPC Version 3.1.0 or
Status is updated higher
with ON, else it is
updated with value
OFF.

Supported
Models
Restart To get the reason 1 --> Putty/Terminal All Models 1. Firmware should
Reason of last time restart closed. support global master
of firmware 2 --> Ctrl C pressed. 2. License of global
3 --> Ctrl \ pressed. Master
4, 6, 8, 10, 11, 13, 15 3. DCCP Version 2.16.0
--> Internal error or higher
19 --> Power failure 4. GPC Version 3.1.0 or
23 --> Firmware higher
paused
24 --> Ctrl Z Pressed
31 --> File Size
exceeded
99 --> EasyConnect
Reboot
98 --> EasyConnect
stop
97 --> Power restart
96 --> Reboot
command
100 --> Other
reasons
Last SYNC The time at Time (in milliseconds SYNC3000 1. Firmware should
Time which last from epoch) in support global master
Synchronization HR:MIN:SEC:MSEC 2. License of global
has occurred. MM-DD-YYYY Master
format. 3. DCCP Version 2.16.0
or higher
higher
Time Since The time elapsed Time in seconds. SYNC3000 1. Firmware should
Last Sync after last SYNC support global master
Time Time. 2. License of global
Master
3. DCCP Version 2.16.0
or higher
higher

Supported
Models
Time Sync Validity of current GOOD: Time is Valid All Models 1. Firmware should
Status time support global master
INVALID: Time is 2. License of global
Invalid since Time Master
Valid Period is 3. DCCP Version 2.16.0
expired or Time or higher
synchronization 4. GPC Version 3.1.0 or
received in First higher
SYNC Wait Period. Note: Time Sync Status
will not be updated if
EXCVP: Exceeded the time sync source
Clock Valid Period. selected is IRIGB or
EXMOFT: Exceeded NTP.
Maximum Offset.
FSYNCWT: Time
SYNC in First SYNC
Wait Period.
OVLST: Overflow of
value of Time Since
Last Sync Time.
Device Healthiness of the 0(Healthy), All Models 1. Firmware should
Healthiness device derived 1(Low Warning), support global master
from the Node 2(High Warning), 2. License of global
diagnostic points. 3(Unhealthy). Master
Is ‘Healthy’ if 3. DCCP Version 2.16.0
all the nodes or higher
connected, ‘Low 4. GPC Version 3.1.0 or
warning’ if 50% or higher
more nodes are
connected, ‘High
warning’ if less
than 50% nodes
are connected
and ‘unhealthy’ if
all the nodes are
disconnected.
(Profile should be
added for nodes.
Only externally
connecting
master nodes are
considered)
Last The time at which Time (in milliseconds All Models 1. Firmware should
commissioning the device is from epoch). support global master
Date and Time configured using Timestamp of the 2. License of global
EasyConnect point also will be Master
recently. updated with the time 3. DCCP Version 2.16.0
corresponding to the or higher
epoch value. 4. GPC Version 3.1.0 or
higher

Supported
Models
Last License The time at which Time (in milliseconds All Models 1. Firmware should
update date the device License from epoch). support global master
and time is updated. Timestamp of the 2. License of global
point also will be Master
updated with the time 3. DCCP Version 2.16.0
corresponding to the or higher
epoch value. 4. GPC Version 3.1.0 or
higher
Last User The time at Time (in All Models 1. Firmware should
Access Date which the milliseconds from support global master
and Time device is epoch).Timestamp 2. License of global
accessed using of the point also will Master
EasyConnect be updated with the 3. DCCP Version
for any activity time corresponding 2.16.0 or higher
recently. to the epoch value. 4. GPC Version 3.1.0
or higher
Up Time The time at Time (in All Models 1. Firmware should
which the milliseconds from support global master
firmware is UP epoch).Timestamp 2. License of global
of the point also will Master
be updated with the 3. DCCP Version
time corresponding 2.16.0 or higher
to the epoch value. 4. GPC Version 3.1.0
or higher
Hardware
RTC Status Provides the ON/OFF All Models 1. Firmware should
status of the support global master
RTC chip 2. License of global
present in the Master
device. If battery 3. DCCP Version
is present, then 2.16.0 or higher
RTC Status is 4. GPC Version 3.1.0
updated as ON, or higher
else OFF value
is updated.
Local Remote To get the For SYNC2101: SYNC2101, 1. Firmware should
Status position of LR ON --> Remote SYNC2111 have support to
switch. OFF --> Local global master and
MRTU/FRTU Master
For SYNC2111 and (depends on the
SYNC 2121: model)
ON --> Local 2. License of global
OFF --> Remote Master and MRTU/
FRTU Master

Supported
Models
Card Status 1 To get the status Off --> Card not SYNC2111 1. Firmware should
of card 1 active have support to global
On --> Card active master and FRTU
Intermediate --> Master
Card mismatch 2. License of global
Master and FRTU
Master
Master and FRTU
Master
Master and FRTU
Master
Master and FRTU
Master
Master and FRTU
Master
Master and FRTU
Master

Supported
Models
Master and FRTU
Master
DIALUP DIALUP Process On/Off All Models 1. Firmware should
Status is running or not support global master
running. 2. License of global
Master
3. DCCP Version
2.16.0 or higher
or higher
NTP Status NTP is running On/Off All Models 1. Firmware should
or not running. support global master
2. License of global
Master
3. DCCP Version
2.16.0 or higher
or higher
PTP Running PTP is running or On/Off SYNC3000
Status not running.
SMS Status If SMS can be On/Off All Models 1. Firmware should
sent successfully, support global master
then SMS Status 2. License of global
is updated as Master
On, else it is 3. DCCP Version
updated as Off. 2.16.0 or higher
or higher
SNMP Status SNMP Process On/Off All Models 1. Firmware should
is running or not. support global master
Master
3. DCCP Version
2.16.0 or higher
or higher

Supported
Models
SW If DCCP is On/Off All Models 1. Firmware should
Watchdog running or not support global master
Status 2. License of global
Master
3. DCCP Version
2.16.0 or higher
or higher
VPN Status VPN Process is On/Off All Models 1. Firmware should
running or not support global master
Master
3. DCCP Version
2.16.0 or higher
or higher
Web HMI Used for - All Models 1. Firmware should
Station enabling / support global master
Control disabling control 2. License of global
commands from Master
HMI 3. DCCP Version
2.16.0 or higher
or higher
Web HMI Used to store the On/Off All Models 1. Firmware should
Control current status of support global master
Status Web HMI Station 2. License of global
Control Master
3. DCCP Version
2.16.0 or higher
or higher
Web HMI Web HMI On/Off All Models 1. Firmware should
Status process is support global master
running or not 2. License of global
Master
3. DCCP Version
2.16.0 or higher
or higher

Supported
Models
Channel Diagnostics
Channel Healthiness 0(Healthy), All Models 1. Firmware should
Healthiness of the channel 1(Low Warning), support global master
derived from 2(High Warning), 2. License of global
the Node 3(Unhealthy) Master
diagnostic points. 3. DCCP Version
Is 'Healthy' if 2.16.0 or higher
all the nodes 4. GPC Version 3.1.0
connected, 'Low or higher
warning' if 50%
or more nodes
are connected,
'High warning'
if less than
50% nodes are
connected and
'unhealthy' if all
the nodes are
disconnected.
(Profile should
be added
for nodes.
Applicable for
IEC101/104 and
DNP3 Masters)
Bad COT Is counted when 0- 4294967295 All Models 1. Firmware should
Counter master receives support global master
any bad COT 2. License of global
(IEC101/104 Master
Master) 3. DCCP Version
2.16.0 or higher
or higher
Fragment Count of 0- 4294967295 All Models 1. Firmware should
Received Fragments support global master
Counter Received. (DNP3 2. License of global
Master or Slave) Master
3. DCCP Version
2.16.0 or higher
or higher
Fragment Count of 0- 4294967295 All Models 1. Firmware should
Sent Counter Fragments Sent. support global master
(DNP3 Master or 2. License of global
Slave) Master
3. DCCP Version
2.16.0 or higher
or higher

Supported
Models
Frame Error This is the 0- 4294967295 All Models 1. Firmware should
Counter counter frame support global master
received with a 2. License of global
wrong address, Master
or an invalid 3. DCCP Version
frame (frame not 2.16.0 or higher
matching with 4. GPC Version 3.1.0
header info)or or higher
an incomplete
frame.
(IEC101/104
master)
Frame Count of the 0- 4294967295 All Models 1. Firmware should
Received frame received. support global master
Counter (IEC101/104 and 2. License of global
DNP3 Master/ Master
Slave) 3. DCCP Version
2.16.0 or higher
or higher
Frame Sent Count of the 0- 4294967295 All Models 1. Firmware should
Counter frame sent. support global master
(IEC101/104 and 2. License of global
DNP3 Master/ Master
Slave) 3. DCCP Version
2.16.0 or higher
or higher
Remote Error This is the 0- 4294967295 All Models 1. Firmware should
Counter count of ASDUs support global master
received by a 2. License of global
master channel Master
with COT 3. DCCP Version
remote error. 2.16.0 or higher
(IEC101/104 4. GPC Version 3.1.0
Master only) or higher

Supported
Models
Request Number of 0- 4294967295 All Models 1. Firmware should
Counter request. For support global master
a master any 2. License of global
application Master
frame sent is 3. DCCP Version
considered as 2.16.0 or higher
request. And 4. GPC Version 3.1.0
for slave any or higher
application
frame received
will be counted
as request.
(Applicable for
IEC101/104 and
DNP3 Masters/
Slaves)
Response Number of 0- 4294967295 All Models 1. Firmware should
Counter response. For support global master
a master any 2. License of global
application Master
frame received 3. DCCP Version
is considered 2.16.0 or higher
as response. 4. GPC Version 3.1.0
And for slave or higher
any application
frame sent will
be counted
as response.
(Applicable for
IEC101/104 and
DNP3 Masters/
Slaves)
Unknown This is the 0- 4294967295 All Models 1. Firmware should
Address count of ASDUs support global master
Counter received by a 2. License of global
unknown IOA 2.16.0 or higher

Supported
Models
Node Diagnostics
Buffer Indicates if buffer On/Off All Models 1. Firmware should
Overflow of the slave node support global master
configured has 2. License of global
overflowed or Master
not. Applicable 3. DCCP Version
for slave nodes 2.16.0 or higher
of IEC 104, IEC 4. GPC Version 3.1.0
101, IEC 103 or higher
and DNP 3
Node Number of 0- 4294967295 All Models 1. Firmware should
Request requests under support global master
Counter a node. For 2. License of global
a master any Master
application 3. DCCP Version
frame sent is 2.16.0 or higher
considered as 4. GPC Version 3.1.0
request. And or higher
for slave any
application frame
received will
be counted as
request
Node Number of 0- 4294967295 All Models 1. Firmware should
Response response under support global master
Counter a node. For 2. License of global
a master any Master
application 3. DCCP Version
frame received 2.16.0 or higher
is considered 4. GPC Version 3.1.0
as response. or higher
And for slave
any application
frame sent will
be counted as
response
Node Remote This is the 0-4294967295 All Models 1. Firmware should
Error Counter count of ASDUs support global master
received by a 2. License of global
remote error. 2.16.0 or higher

Supported
Models
Node bad Is counted when 0- 4294967295 All Models 1. Firmware should
COT Counter master receives support global master
any bad COT 2. License of global
(IEC101/104 Master
Master) 3. DCCP Version
2.16.0 or higher
or higher
Node This is the 0- 4294967295 All Models 1. Firmware should
Unknown count of ASDUs support global master
Address received by a 2. License of global
Counter master channel Master
unknown IOA 2.16.0 or higher
Interfaces
Ethernet port Indicates which All Models 1. Firmware should
status all ethernet ports support global master
are connected 2. License of global
with cable Master
3. DCCP Version
2.16.0 or higher
or higher
Serial Port Indicates if Serial On/Off Configurable 1. Firmware should
Status: Port1 port 1 is used or according support global master
not to device 2. License of global
Model Master
3. DCCP Version
2.16.0 or higher
or higher
Model Master
3. DCCP Version
2.16.0 or higher
or higher

Supported
Models
Model Master
3. DCCP Version
2.16.0 or higher
or higher
Model Master
3. DCCP Version
2.16.0 or higher
or higher
Model Master
3. DCCP Version
2.16.0 or higher
or higher
Model Master
3. DCCP Version
2.16.0 or higher
or higher
Model Master
3. DCCP Version
2.16.0 or higher
or higher
Model Master
3. DCCP Version
2.16.0 or higher
or higher

Supported
Models
Model Master
3. DCCP Version
2.16.0 or higher
or higher
Status: port 10 is used according support global master
Port10 or not to device 2. License of global
Model Master
3. DCCP Version
2.16.0 or higher
or higher
Status: port 11 is used or according support global master
Port11 not to device 2. License of global
Model Master
3. DCCP Version
2.16.0 or higher
or higher
Status: port 12 is used according support global master
Port12 or not to device 2. License of global
Model Master
3. DCCP Version
2.16.0 or higher
or higher
Table 15: Diagnostic Variables

28.4 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 222: Adding Special functions
The below table 14 (Special Functions) lists all the Special functions available in the device.
Special Data Type Functionality Values Supported

Models
Battery Digital This informs GPC ON → On All Models
Charging Input whether the DCU is Battery OFF
On/ Off status running on battery → On regular
(power is out or not supply
connected) or not
Table 16: Special Function Tags

29
29. 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 223: Enabling the use of a profile row in Logic Engine

29.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 224: Exporting logic variables

30
30. 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.

23
31. Time Synchronization
The following are three 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.
31.1. Time Synch Configuration

Configuration for time synchronisation can be found in Device settings with name Time
Synchronization as shown below in figure (Device Parameters).
Figure 225: Device Settings
When Time Synchronization is chosen, the following window is seen and parameters are
described in below table Time Synchronization Parameters.

Parameter
Range Default Description
Name
Time Sync All, NTP/ All Specify Time Synchronization
Source SNTP,Telemetry Source.
Protocol,IRIG B, All: Device time will be treated as
IEEE 1588 always good. Also Device will not
restrict any time synchronization
NTP/SNTP: The Time
synchronization will happen
through NTP/ SNTP only.
Telemetry Protocol: External
protocol master can time
synchronize the device through
protocol time synchronization.
IRIG B: Time synchronization
through IRIG B is enabled.
IEEE 1588: Time synchronization
through IEEE 1588 is enabled.
Notes:
1. If Time Sync Source selected
is Telemetry Protocol, set Clock
synchronization parameter in
Accept mode in the desired
protocol Slaves. Supporting slave
protocols in current version are
IEC101/IEC103/IEC104/DNP3.
2.Option IRIG B is relevant for
SYNC3000 -M1/M2/M3/M12
3. Option IEEE 1588 is relevant
for SYNC3000 -M1/M2/M3/M12
and SYNC261.
Clock Valid 1 - 71581 minutes 0 Specify how long the system clock
Period (1 - 71581 will remain valid after a clock
min) synchronization.
Note: This Parameter is effective
only if Time Sync Source selected
is Telemetry
Protocol or NTP/SNTP.
Append Device Enable/Disable Disable Specify whether to set the time
Time Quality quality of the points based on the
time synchronization of the device.
Note: If Disable, the points will
have the time quality obtained
from the downstream protocol.
This will be effective for all points
which takes device time.
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 Precision 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.
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 Tag- 0 – 65534 0 VLAN Tag value
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
31.2. 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.
31.3. 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.

31.4. NTP Support
Network Time Protocol (NTP) is a networking protocol for clock synchronization between computer
systems over packet-switched, variable-latency data networks. NTP is intended to synchronize
all participating computers to within a few milliseconds of Coordinated Universal Time (UTC).
NTP can usually maintain time to within tens of milliseconds over the public Internet, and can
achieve better than one millisecond accuracy in local area networks under ideal conditions.
The protocol is usually described in terms of a client-server model, but can as easily be used
in peer-to-peer relationships where both peers consider the other to be a potential time source.
31.4.1. Configuring NTP
The device that requires clock synchronization by NTP can either be configured as a client,
server or both.
The SNTP/NTP protocol should be chosen and the protocol type must be selected as NTP from
the following parameters:
Parameter Range/Optional
Default Value Description
Name Values
Protocol Type SNTP, NTP SNTP Specifies the type of protocol to be
used for time synchronization.
Port No Valid UDP Port failure Specifies UDP Port number used
Range for SNTP Client/Server.
Table 18: Channel Parameters
To configure NTP as a client the client node should be added and the following parameters need
to be configured based on the requirement.
Parameter
Name
NTP server IP - 0.0.0.0 This is the address of the server
address to which our device (client)
synchronizes.
Minpoll 4 to 6 6 This value specifies the polling
interval. i.e the interval at which
the client polls the server. If the
required polling interval is 64
seconds the configured value
should be 6 (2^6=64 secs)
Maxpoll 4 to 17 10 Maxpoll sets the maximum value
until the polling should go on in
case the server isn't reachable.
Enable NTP True (1) – False (0) False (0) Redundant servers can be
redundant provided for more accuracy.
servers
No of redundant 0-4 0 Specifies the no of redundant
servers servers that are to be listed in the
configuration file.

NTP redundant - 0.0.0.0 This is the address of the server
server 1 IP to which our system (client)
address synchronizes in case the primary
fails. They also play a part in
improving the accuracy.
Table 19: Client node Parameters
To configure NTP as a server the server node should be added and the following parameters
need to be configured based on the requirement.
Parameter Default
Range XML Tag Description
Name Value
Stratum level of 0-15 0 STRALVL Stratum level represents the
the server distance from the reference clock.
If the client of the same device
wants to synchronize with an
external server, the value of the
stratum level must be high (>=4).
As, the level also represents the
priority at which the client chooses
to connect to a server. Higher the
stratum number lower the priority.
Table 20: Server node Parameters
To configure NTP as client and server the client and the server node should be added and their
respective parameters need to be configured based on the requirement.

32
32. 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 226: 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 227: Pop-up for Automatic Up gradation

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 228: Model name prompt for older DCCP versions
Figure 229: 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.

Figure 230: 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.

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 231: Version Info for devices with older DCCP Versions

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 work-flow 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
configuration 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 other
channels. 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.

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 21: 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 22: GPC, DCCP & EC Compatibility Table

C
Appendix C – Flag conversion in SYNC
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 23: 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.

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
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
Supported SYNC LAN1-LAN5 (eth0, eth2, eth4)
Devices SYNC3000S12R2F2 Note: If eth4 is selected for HSR
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
SYNC3000S12R6 eth3)
Supported SYNC LAN1-LAN4 (eth0, eth2)

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

Table 24: 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 Mark-up 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 25: List of abbreviations

SYNC EasyConnect Usermanual Rev4.7.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SYNC EasyConnect Usermanual Rev4.7.0

Uploaded by

Copyright:

Available Formats

EasyConnect

Software User Manual

Version 4.7.0, March 2017

EasyConnect Software User Manual 1

© 2017 Kalki Communication Technologies Pvt. Ltd. All Rights reserved.

Kalki Communication Technologies Pvt. Ltd.

Telephone: +91- 8067021900

Technical Support Contact Information

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

E-mail Support: support@kalkitech.com

EasyConnect Software User Manual 2

EasyConnect Software User Manual 3

EasyConnect Software User Manual 4

EasyConnect Software User Manual 5

EasyConnect Software User Manual 6

EasyConnect Software User Manual 7

EasyConnect Software User Manual 8

EasyConnect Software User Manual 9

EasyConnect Software User Manual 10

EasyConnect Software User Manual 11

EasyConnect Software User Manual 12

EasyConnect Software User Manual 13

EasyConnect can be used for:

EasyConnect Software User Manual 14

1.2.1. Software Requirements

1.2.1. Hardware Requirements

EasyConnect Software User Manual 15

2.1. Installing EasyConnect

To install EasyConnect, do the following:

Note: Follow default options for installing EasyConnect

2.2. Removing EasyConnect

2.3. Starting EasyConnect

EasyConnect Software User Manual 16

Figure 1: EasyConnect User Interface

2.4. Exiting EasyConnect

To exit EasyConnect, do the following:

2.5. Using the EasyConnect Interface

Figure 2: User Interface

EasyConnect Software User Manual 17

Figure 3: File Menu

Figure 4: View Menu

EasyConnect Software User Manual 18

Figure 5: Configuration Menu

Figure 6: Settings Menu

Download To download the configuration file to the SYNC device.

EasyConnect Software User Manual 19

Figure 7: Diagnostic Menu

Figure 8: Tool Menu

EasyConnect Software User Manual 20

Figure 9: Help Menu

Figure 10: Toolbar

EasyConnect Software User Manual 21

EasyConnect Software User Manual 22

Figure 11: Edit Preferences

Mode Switching while Log in

Figure 12: Mode switching from login screen

EasyConnect Software User Manual 23

Parameter Name Range Default Value Description

EasyConnect Software User Manual 24

Login Screen of EasyConnect in Advance mode is shown below:

Figure 13: Login Screen of EasyConnect in Advance Mode

Installing EasyConnect Product License:

Figure 14: License Installation Screen

EasyConnect Software User Manual 25