Softing echolink one2PROFINET User manual

Instruction Manual
Universal Fieldbus Gateway
echolink one2PROFINET
Softing Industrial Automation GmbH | Richard-Reitzner-Allee 6 | 85540 Haar, Germany
Tel:[phone] | Fax: [phone] | http://industrial.softing.com |
E-Mail: [e-mail] | Support: [e-mail]

15.1.15 echolink one2PROFINET V. 1.0 2
Softing Industrial Automation GmbH
1 Information on CE marking of the module . . . . . . . . . . . . . . . 7
1.1 EU Directive EMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Scope of application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 Note installation guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 Installation of the unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.5 Working on switch cabinets . . . . . . . . . . . . . . . . . . . . . . . . . 7
2 Information for the machine manufacturers . . . . . . . . . . . . . . 8
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2 EU Machinery Directive . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1 echolink one software flow-chart . . . . . . . . . . . . . . . . . . . . . 10
3.2 echolink one application diagram . . . . . . . . . . . . . . . . . . . . . 11
4 Operation modes of the Gateway . . . . . . . . . . . . . . . . . . . 12
4.1 Configuration mode (config mode) . . . . . . . . . . . . . . . . . . . . 12
4.2 Test mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.3 Data exchange mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5 RS-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1 RS-interfaces at the echolink one . . . . . . . . . . . . . . . . . . . . . 13
5.2 Buffer sizes at the echolink one . . . . . . . . . . . . . . . . . . . . . . 13
5.3 Framing Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6 SSI-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.1 Initiation of the SSI-interface . . . . . . . . . . . . . . . . . . . . . . . 14
6.1.1 Parameter sample frequency (Clock stretch) . . . . . . . . . . . . . . . . . . 14
6.1.2 Parameter Encoder monitoring (Check Encoder) . . . . . . . . . . . . . . . . 14
6.2 Hardware-wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7 Mode of operation of the system . . . . . . . . . . . . . . . . . . . 16
7.1 General explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.2 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.3 Data exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.4 Possible data lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.5 Startup phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8 Implemented protocols in echolink one . . . . . . . . . . . . . . . . 17
8.1 Protocol: Transparent . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1.1 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.2 Protocol: Universal 232 . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.2.1 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.2.2 Fieldbus parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.2.3 RS232 parameter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.2.3.1 Start character (232 Start character) . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.2.3.2 Length 232 (232 Length) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.2.3.3 End character (232 End character) . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.2.4 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
8.3 Protocol: 3964(R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.3.1 Data structure 3964R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.3.2 Protocol definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Softing Industrial Automation GmbH
3 echolink one2PROFINET V. 1.0 15.1.15
8.3.3 Data communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
8.3.3.1 Initiation of data communication by the low-priority user . . . . . . . . . . . . . . . 19
8.3.3.2 Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.3.3.3 Timeout times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.3.3.4 Retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.3.3.5 Initiation of data communication by the high-priority user . . . . . . . . . . . . . . . 20
8.3.4 Protocol type 3964 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.4 Protocol: MODBUS-RTU . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.4.1 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.4.2 echolink one as MODBUS-Master . . . . . . . . . . . . . . . . . . . . . . . .20
8.4.2.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.4.2.2 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.4.2.3 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.4.3 echolink one as MODBUS-Slave . . . . . . . . . . . . . . . . . . . . . . . .21
8.4.3.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.4.3.2 Data structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
8.4.3.3 Communication sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.4.4 echolink one as Modbus-ASCII Master . . . . . . . . . . . . . . . . . . . . .22
8.5 The trigger byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.6 The length byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
8.7 Protocol „Universal Modbus RTU Slave“ . . . . . . . . . . . . . . . . . 22
8.7.1 Data structure on the fieldbus side e.g.: PROFIBUS . . . . . . . . . . . . . .23
8.7.1.1 Example: FC1 + FC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.7.1.2 Example: FC3 (Read Holding Register) + FC4 (Read Input Register) . . . . . . . . 24
8.7.1.3 Example: Write Single Coil FC5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8.7.1.4 Example: Write Single Register FC6 . . . . . . . . . . . . . . . . . . . . . . . . . 26
8.7.1.5 Example: Force multiple coils FC 15 . . . . . . . . . . . . . . . . . . . . . . . . . 26
8.7.1.6 Example: Preset multiple register FC16 . . . . . . . . . . . . . . . . . . . . . . . . 27
8.8 Protocol „Universal Modbus RTU Master“ . . . . . . . . . . . . . . . . 27
8.8.1 Data structure Fieldbus side (e.g. PROFIBUS): . . . . . . . . . . . . . . . . . 27
8.8.2 Data structure Application side: . . . . . . . . . . . . . . . . . . . . . . . . .28
8.8.3 Configuration: via Wingate since wcf Datei Version 396 . . . . . . . . . . . . .29
8.8.3.1 Example: Read coil status FC1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
8.8.3.2 Example: Read input status FC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
8.8.3.3 Example: Read multiple register FC3 . . . . . . . . . . . . . . . . . . . . . . . . . 32
8.8.3.4 Example: Read input registers FC4 . . . . . . . . . . . . . . . . . . . . . . . . . . 33
8.8.3.5 Example: Force single coil FC5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
8.8.3.6 Example: Preset single register FC6 . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.8.3.7 Example: Force multiple coils FC15 . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.8.3.8 Example: Preset multiple register FC16 . . . . . . . . . . . . . . . . . . . . . . . . 35
8.9 Protocol „Universal Modbus ASCII Master/Slave“ . . . . . . . . . . . . 36
8.9.1 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
8.9.1.1 Example Configuration 1: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.9.1.2 Swap Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
8.9.1.3 Example with Fast Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
9 Hardware ports, switches and LEDs . . . . . . . . . . . . . . . . . . 42
9.1 Device labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

15.1.15 echolink one2PROFINET V. 1.0 4
Softing Industrial Automation GmbH
9.2 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
9.2.1 Connector to the external device (RS-interface) . . . . . . . . . . . . . . . . 42
9.2.2 Connector supply voltage and Debug-interface . . . . . . . . . . . . . . . . 43
9.2.3 PROFINET-connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
9.2.4 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
9.3 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
9.3.1 LED "(PROFINET) Power" . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
9.3.2 LED "Link / Act. P1" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
9.3.3 LED "Link / Act. P2" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
9.3.4 LED "(PROFINET) State" . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
9.3.5 LED "Power" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
9.3.6 LED "State" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
9.3.7 LEDs 1 / 2 / 4 / 8 (Error No. / Select ID) . . . . . . . . . . . . . . . . . . . . 44
9.4 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
9.4.1 Termination Rx 422 + Tx 422 (serial interface) . . . . . . . . . . . . . . . . . 45
9.4.2 Rotary coding switches S4 + S5 (serial interface) . . . . . . . . . . . . . . . 45
10 Error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10.1 Error handling at echolink one . . . . . . . . . . . . . . . . . . . . . . 46
11 Installation guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.1 Installation of the module . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.1.1 Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.1.2 Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.2 Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.2.1 Connection systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.2.1.1 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.2.1.2 Equipotential bonding connection. . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.2.2 PROFINET-IO communication interface . . . . . . . . . . . . . . . . . . . . 49
11.2.3 Line routing, shield and measures to combat interference voltage . . . . . . . 49
11.2.4 General information on line routing . . . . . . . . . . . . . . . . . . . . . . . 49
11.2.4.1 Shielding of lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
12 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
12.1 Device data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
12.1.1 Interface data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
13 Commissioning guide . . . . . . . . . . . . . . . . . . . . . . . . . 53
13.1 Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
13.2 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
13.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
13.4 Dimensional drawing echolink one2PROFINET . . . . . . . . . . . . . 53
13.5 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
13.6 PROFINET address-assignment . . . . . . . . . . . . . . . . . . . . . 54
13.7 PROFINET device name . . . . . . . . . . . . . . . . . . . . . . . . . 54
13.8 PROFINET connection . . . . . . . . . . . . . . . . . . . . . . . . . . 54
13.9 Connection to the process device . . . . . . . . . . . . . . . . . . . . . 54
13.10 Shield connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
13.11 Connecting the supply voltage . . . . . . . . . . . . . . . . . . . . . . 54
13.12 Project planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Softing Industrial Automation GmbH
5 echolink one2PROFINET V. 1.0 15.1.15
13.13 Literature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
14 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
14.1 Hexadecimal table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

15.1.15 echolink one2PROFINET V. 1.0 6
Softing Industrial Automation GmbH
Disclaimer of liability
The information contained in these instructions corresponds to the technical status at the time of
printing of it and is passed on with the best of our knowledge. The information in these instruc-
tions is in no event a basis for warranty claims or contractual agreements concerning the
described products, and may especially not be deemed as warranty concerning the quality and
durability pursuant to Sec. 443 German Civil Code. We reserve the right to make any alterations
or improvements to these instructions without prior notice. The actual design of products may
deviate from the information contained in the instructions if technical alterations and product
improvements so require. It may not, in part or in its entirety, be reproduced, copied, or trans-
ferred into electronic media.














Softing Industrial Automation GmbH

Richard-Reitzner-Allee 685540 Haar / Germany
Tel: + 49 89 4 56 56-0
Fax: + 49 89 4 56 56-488
Internet: http://industrial.softing.com
Email: info.automa[email protected]
Support: support.auto[email protected]

The latest version of this manual is available in the Softing download area at: 
http://industrial.softing.com.

Information on CE marking of the module Softing Industrial Automation GmbH
7 echolink one2PROFINET V. 1.0 15.1.15
1Information on CE marking of the module
1.1 EU Directive EMC
The following applies to the module described in this User Manual:
Products which bear the CE mark comply with the requirements of EU Directive „Electromagnetic
Compatibility“ and the harmonized European Standards (EN) listed therein.
The EU Declarations of Conformity are availableat the following location for perusal by the
responsible authorities in accordance with the EU Directive, Article 10:
Softing Industrial Automation GmbH, Richard-Reitzner-Allee 6, 85540 Haar, Germany.
1.2 Scope of application
The modules are designed for use in the industrial sector and comply with the following
requirements.
Scope of application Requirement applicable to
Emitted interference Interference immunity
Industry EN 55011, cl. A (2007) EN 61000-6-2 (2005)
1.3 Note installation guidelines
The module complies with the requirements if you
1. comply with the installation guidelines described in the User Manual when installing and
operating the module.
2. also follow the rules below on installation of the equipment and on working on switch cabinets.
1.4 Installation of the unit
Modules must be installed in electrical equipment rooms/areas or in enclosed housings (e.g.
switch boxes made of metal or plastic). Moreover, you must earth the unit and the switch box
(metal box) or at least the top-hat rail (plastic box) onto which the module has been snapped.
1.5 Working on switch cabinets
In order to protect the modules against static electrical discharge, the personnel must discharge
themselves electrostatically before opening switch cabinets or switch boxes.

15.1.15 echolink one2PROFINET V. 1.0 8
Softing Industrial Automation GmbH Information for the machine manufacturers
2 Information for the machine manufacturers
2.1 Introduction
The echolink one module does not constitute a machine as defined by the EU "Machinery“
Directive. Consequently, the module does not have a Declaration of Conformity in relation to the
EU Machinery Directive.
2.2 EU Machinery Directive
The EU Machinery Directive stipulates the requirements applicable to a machine. The term
"machine" is taken to mean a totality of connected parts or fixtures (see also EN 292-1, Para-
graph 3.1)
The module is a part of the electrical equipment of the machine and must thus be included by the
machine manufacturer in the Declaration of Conformity process.

Introduction Softing Industrial Automation GmbH
9 echolink one2PROFINET V. 1.0 15.1.15
3 Introduction
The echolink one2PROFINET module serves to adapt a serial port to PROFINET networks. The
device features 2 PROFINET ports - one port can for instance be used as an outgoing
PROFINET port. Talking of PROFINET is automatically connected with the 100 Mb/s-version,
full-duplex and switched Ethernet. The terminal unit’s protocol is converted in the echolink one
via a Script.
The module echolink one2PROFINET essentially consists of the following hardware compo-
nents:
•Electrically isolated PROFINET-interface
•Processor
•RAM and FLASH
•Serial interface (RS232, RS485 and RS422) to the device connected externally

15.1.15 echolink one2PROFINET V. 1.0 10
Softing Industrial Automation GmbH Introduction
3.1 echolink one software flow-chart

Introduction Softing Industrial Automation GmbH
11 echolink one2PROFINET V. 1.0 15.1.15
3.2 echolink one application diagram
The following graph shows a typical connection scheme.

15.1.15 echolink one2PROFINET V. 1.0 12
Softing Industrial Automation GmbH Operation modes of the Gateway
4 Operation modes of the Gateway
4.1 Configuration mode (config mode)
The configuration mode serves to configure the Gateway. The following adjustments are possible
in this mode.
•Loading a Script
•Updating the firmware
The Gateway will be starting in this mode in case both switches S4 as well as S5 are set on posi-
tion "F" when switching on the Gateway. Right after switching on the Gateway in the configura-
tion mode it will be sending its starting message, that looks analog with the following message:
RS-PN-CL (232/422/485) V2.43[38] (c)dA[66,666MHz] Switch=0xFF
Script(C:10709/16320,V:8120/8192)="Universalscript" Author="G/S" Version="VI1.1"
Date=30.06.2014 SN=47110010 IP=0.0.0.0 MAC=00-14-11-15-19-8A Name=""
In the configuration mode the Gateway always operates with the settings 9600 Bauds, no Parity,
8 Databits and 1 Stopbit, the RS-State LED will always be flashing red, the "Error No/Select ID"
LEDs are of no account for the user. All software revisions contain the configuration mode.
4.2 Test mode
Setting of the test mode
The test mode is set by bringing the switches S4 and S5 in position "E". All other switches will not
be taken into consideration for the setting of the test mode. Now the Gateway has to be restarted
with these settings (by a short disconnection from the power supply).
In the test mode the Gateway always operates with the settings 9600 baud, no parity, 8 databits
and 1 stopbit.
The test mode may be helpful to integrate the Gateway in the relevant environment, for instance
to test the parameters of the RS-interfaces.
Mode of operation of the test mode
After the restart in the test mode the Gateway will be sending the values 0-15 in hexadecimal
representation ("0".."F") in ASCII-coding on the serial side every second. Simultaneously the
same values are issued binary on the fieldbus-interface.
In this mode the State-LED on the RS-side will be flashing red, the "Error No/Select ID" LEDs will
be displaying the value in a binary way, that is issued that moment. Additionally each character
that is received at one of the interfaces will also be output at the same interface as a local echo.
On the fieldbus-side only the first byte will be used for the local echo, that means on receiving as
well as on transmitting only the first byte of the bus data is looked at, the other bus data do not
change compared to the last data.
4.3 Data exchange mode
The Gateway has to be in the data exchange mode, so that a data exchange between the
RS-side of the Gateway and the fieldbus is possible. As long as the Gateway is not in the config-
uration mode or the test mode, the data exchange mode is active. In the data exchange mode
the Gateway will execute the downloaded Script.

RS-interface Softing Industrial Automation GmbH
13 echolink one2PROFINET V. 1.0 15.1.15
5 RS-interface
5.1 RS-interfaces at the echolink one
The echolink one2PROFINET has the interfaces RS232, RS422 and RS485 available.
5.2 Buffer sizes at the echolink one
echolink one features at the serial side a buffer with the size of 1024 bytes for input data and out-
put data each.
5.3 Framing Check
The length of the stop bit received by the Gateway is checked through the function "Framing
Check". Here the stop bit generated by the Gateway is always long enough, so that connected
participants can evaluate the stop bit.
Please be aware that the function "Framing Check" becomes effective only in case of 8 data bit
and the setting "No parity".
An error is detected and indicated by the Error LEDs in case the stop bit does not show the
length 1 bit during the activated check.
The fixed setting for the "Stop Bit Framing Check" is "enabled".

15.1.15 echolink one2PROFINET V. 1.0 14
Softing Industrial Automation GmbH SSI-interface
6 SSI-interface
The echolink one also supports the connection of applications or products, that communicate via
SSI.
6.1 Initiation of the SSI-interface
The configuration of the SSI-interface is executed in the config mode with the WINGATE soft-
ware, Protocol SSI. The encoder type and the sampling frequency are defined via the parameter
"Resolution" (1 bit..15 bit, 24 bit...25 bit), "SSI Encoder Type" (Binary or Gray code) and "Clock
stretch".
6.1.1 Parameter sample frequency (Clock stretch)
You can change the sampling frequency. For this purpose a "Stretch value" is passed that inserts
a waiting period after each clock edge.
If a 0 is passed, there is no waiting time.
Thus the following SSI sample frequencies may vary slightly:

Waiting time = 0 →SSI-Clock ~ 333kHz (No Stretch)
Waiting time = 1 →SSI-Clock ~ 185kHz
Waiting time = 2 →SSI-Clock ~ 150kHz
Waiting time = 3 →SSI-Clock ~ 125kHz
Waiting time = 4 →SSI-Clock ~ 110kHz
Waiting time = 5 →SSI-Clock ~ 100kHz
Waiting time = 6 →SSI-Clock ~ 88kHz
Waiting time = 7 →SSI-Clock ~ 80kHz
Waiting time = 8 →SSI-Clock ~ 72kHz
Waiting time = 9 →SSI-Clock ~ 67kHz
Waiting time = A →SSI-Clock ~ 62kHz
Waiting time = B →SSI-Clock ~ 58kHz
Waiting time = C →SSI-Clock ~ 54kHz
Waiting time = D →SSI-Clock ~ 50kHz
Waiting time = E →SSI-Clock ~ 48kHz
Waiting time = F →SSI-Clock ~ 45kHz
The bit time from which these frequencies were derived, calculate as follows:
t = 3μs + (2* (+ 0.6µs (n* 0.6µs))), where n corresponds to the "Stretch value" (1.. F).
Without clock extension (n = 0) remains at 3μs →333kHz!
The max. Bit length of 32 bits and the slowest clock this results in a total readout time of
32 * = 22μs ~ 700μs.
6.1.2 Parameter Encoder monitoring (Check Encoder)
An encoder monitoring can be activated via the parameter "Check encoder", as long as the used
SSI-encoder supports this function. After the last read encoder bit it is verified if the data line is
still at Low for at least one bit. If the echolink one does NOT detect this bit on Low, error 12 is
issued. For example it can detect a cable break or a not connected encoder. However, it can also
be a misconfigured bit length, or a too slow read out clock.

SSI-interface Softing Industrial Automation GmbH
15 echolink one2PROFINET V. 1.0 15.1.15
6.2 Hardware-wiring
The clock wires of the SSI-interface are placed onto the Tx-wires of the RS422-interface and the
data wires onto the Rx-wires at the echolink one.

X1 (3pin + 4pin screw-plug-connector):
Pin no. Name Function at SSI
1Rx 232 n. c.
2Tx 232 n. c.
3AP-GND n. c.
4Rx 422+ SSI DAT+
5Rx 422- SSI DAT-
6Tx 422+ SSI CLK+
7Tx 422- SSI CLK-

15.1.15 echolink one2PROFINET V. 1.0 16
Softing Industrial Automation GmbH Mode of operation of the system
7 Mode of operation of the system
7.1 General explanation
Communication can be split into seven layers, Layer 1 to Layer 7, in accordance with the
ISO/OSI model.
The Softing AG Gateways convert Layers 1 and 2 of the customized bus system (RS485 /
RS232 / RS422) to the corresponding Fieldbus system. Layers 3 and 4 are being covered by the
UDP/IP-protocol, TCP/IP-protocol. The Layers 5 and 6 are blank. Layer 7 is converted in accor-
dance with chapter 7.3.
The Gateway can be configured via the software WINGATE.
7.2 Interfaces
The Gateway features the RS232-, RS422- and RS485-interfaces. The switching of the inter-
faces is done via the configuration (Parameter 232 Interface).
7.3 Data exchange
All data is transferred by the Gateway in dependence of the configuration.
7.4 Possible data lengths
The table below shows the maximum transferable data:
Input data max. 1440 bytes variable: here maximum value
Output data max. 1440 bytes variable: here maximum value
7.5 Startup phase
The Gateway is parameterized and configured by the PROFINET-IO-controller during the startup
phase. Only after a correct termination of the startup phase the data exchange with external
devices will take place.

Implemented protocols in echolink one Softing Industrial Automation GmbH
17 echolink one2PROFINET V. 1.0 15.1.15
8 Implemented protocols in echolink one
Echolink one is supplied with the Script “Universal Script“. The configuration of the protocols is
carried out in the configuration mode (see chapter 4.1) with the software WINGATE.
Attention:
If a Reset Device is carried out it is possible that the "Universal Script"
will get lost and must be played in again.
8.1 Protocol: Transparent
The data is transferred bidirectional from the echolink one.
8.1.1 Data structure
On the RS-entry side the timeout time of 2 ms is firmly set. If no more data is received within the
timeout period, then the data that has been received so far is transferred to the bus.
If less data is received through Rx then configured by the GSDML-file (I/O-length), then the rest
is complemented with ZERO.
Too much data received will be cut off.
8.2 Protocol: Universal 232
The protocol designation "Universal 232" and the relation to the
"RS232-interface" in the description have eveloped over the years. The
protocol also works with RS422 and RS485 though!
8.2.1 Data structure
8.2.2 Fieldbus parameters
Trigger byte: See "The trigger byte", Chapter 8.5‚ on page 22
Length byte: See "The length byte", Chapter 8.6‚ on page 22

15.1.15 echolink one2PROFINET V. 1.0 18
Softing Industrial Automation GmbH Implemented protocols in echolink one
8.2.3 RS232 parameter table
8.2.3.1 Start character (232 Start character)
If this character is defined, the gateway evaluates only the data at the RS232 interface following
this start character. Each transmission from the gateway via the RS232 interface is initiated with
the start character in this case.
8.2.3.2 Length 232 (232 Length)
If this byte is activated, the gateway, at the receive end, awaits as many bytes of useful data as
specified in this byte by the RS232 transmitter. At the transmission end, the gateway then sets
this byte to the number of useful data items transmitted by it. If byte "Length232" is not defined,
the gateway, on reception at the RS232 interface, waits for the end criterion if this is defined. If no
end criterion is defined either, as many characters as can be transferred in the fieldbus transmit
buffer are read in via the RS232 interface.
As a special case for this parameter also a length byte with additional Timeout monitoring can be
set in WINGATE. In that case the received characters will be discarded at a Timeout.
Attention:
If "Timeout“ is selected as end character, then this byte has no significance.
8.2.3.3 End character (232 End character)
If this character is defined, the gateway receives data from the RS232 interface up to this charac-
ter. The "Timeout" criterion can be defined as a special case. In this case, the gateway continues
to receive characters until a defined pause occurs. In the special case "Timeout" the "Length
232-byte" has no significance. At the transmit end, the gateway inserts the end character, if
defined, as the last character of a transmission.
8.2.4 Communication sequence
The useful data (data area) arriving via the fieldbus is copied in accordance with chapter 8.2.1
transparently into the RS232 data field and transferred via the RS interface, whereby the protocol
is supplemented in accordance with the configuration (start character, end character...). NO
acknowledgement is issued !
If the "Trigger byte“ (see chapter 8.5) is active, data is sent only on a change of this byte. If the
"Length byte" (see chapter 8.6) is active, only as many of the following bytes as specified there
are transferred.
Receive data at the RS interface is evaluated in accordance with the configured protocol, and the
data field (data area (see chapter 8.2.1)) is sent to the fieldbus Master. If more characters have
been received than the fieldbus block length, the trailing bytes are truncated and an Rx Overrun
is indicated. If less have been received, padding with 0 occurs. If the "Length byte" is active, the
number of received useful data items is entered there. If the, "Trigger byte" is active, this is incre-
mented by one after each complete reception operation at the RS interface.

Implemented protocols in echolink one Softing Industrial Automation GmbH
19 echolink one2PROFINET V. 1.0 15.1.15
8.3 Protocol: 3964(R)
The 3964 protocol is used to transfer data between two serial devices. One partner must be a
high-priority partner and the other must be a low-priority partner in order to resolve initialisation
conflicts.
8.3.1 Data structure 3964R
8.3.2 Protocol definitions
STX Data DLE ETX BCC
The telegram format is as follows:
•The received net data is forwarded (transparently) in both directions unchanged.
Attention: The DLE-doubling is excluded from it; that means one DLE (10H) on the bus-side is
sent on the RS-side twice. A double DLE on the RS-side is only sent once to the bus-master.
•Data blocking is not scheduled.
•The net data length is restricted to 236 bytes per telegram.
•Communication always runs between high-priority and low-priority communication partners.
8.3.3 Data communication
8.3.3.1 Initiation of data communication by the low-priority user
If the low-priority user also receives an STX in response to a transmitted STX, it interrupts its
transmit request, reverts to Receive mode and acknowledges the received STX with DLE.
A DLE in the data string is duplicated and included in the checksum. The BCC is computed from
XORing all characters.
8.3.3.2 Conflicts
8.3.3.3 Timeout times
The timeout times are preset by the definition of the 3964R protocol and cannot be overwritten !!!
tq = acknowledgement timeout time (2 s).
The acknowledgement timeout time is started after transmission of control character STX. If no
positive acknowledgement arrives within the acknowledgement timeout time, the job is repeated
(max. 2 x). If it has not been possible to complete the job positively after two repetitions, the
high-priority device nevertheless attempts to establish contact with the low-priority partner by
transmitting STX (cycle corresponds to tq).
tz = character timeout time ( 200 ms)
If the 3964 R driver receives data, it monitors arrival of the individual characters within period tz.
If no character is received within the timeout time, the protocol terminates transfer. No
acknowledgement is sent to the coupling partner.

15.1.15 echolink one2PROFINET V. 1.0 20
Softing Industrial Automation GmbH Implemented protocols in echolink one
8.3.3.4 Retries
In the event of negative acknowledgement or timeout, a telegram transmitted by the high-priority
user is repeated twice. After this, the gateway signals communication as disturbed but still
attempts to re-establish the connection.
8.3.3.5 Initiation of data communication by the high-priority user
In the case of a negative acknowledgement or timeout, a telegram transmitted by the external
device is repeated twice before a fault is signalled.
8.3.4 Protocol type 3964
The difference to protocol type 3964R is:
1. tq = acknowledge monitoring time
2. The checksum byte BCC is missing.
8.4 Protocol: MODBUS-RTU
8.4.1 Notes
 For reasons of simplicity, "MODBUS-RTU“ is referred to as "MODBUS“ in the text below.
 The terms "input“ and "output“ are always viewed from the gateway’s point of view,
i.e. fieldbus input data is the data sent by the fieldbus Master to the gateway.
8.4.2 echolink one as MODBUS-Master
8.4.2.1 Preparation
Before data exchange is commenced, the parameters "Baud rate", "Parity", "Start bits",
"Stop bits" and "Data bits" and, if applicable, the "Trigger byte" and the "Length
byte" must be set.
In addition, a "Response time" which corresponds to the maximum time up to which the Mod-
bus Slave responds after a request must be set. echolink one multiplies the value entered in
WINGATE by 10 ms.
Since the Modbus operates with a variable data format - dependent on the required function and
data length - but since the fieldbus requires a fixed data length, this must be preset by means of
a selection in the GSDML file (input and output are identical). This length should be selected by
the user such that the longest Modbus request resp. response can be processed.
The user can choose whether the fieldbus requests are forwarded to the Modbus in case of a
change (On Change) or on request (On Trigger).
In "Change" mode, detection of a change is based on the fact that the fieldbus data is compared
with that of the last transmission, and a request is issued by the Modbus only in the case of a
change.
The mode "Modbus request on demand" necessitates the first byte in the fieldbus containing
a trigger byte (see chapter 8.5). This byte is not transferred to the Modbus and serves only to
start a Modbus transmission. For this purpose, the gateway constantly monitors this trigger byte
and sends data to the Modbus only when this byte has changed. In the reverse direction (to the
fieldbus), the gateway transfers the number of received Modbus data records in this byte, i.e. this
byte is incremented by the gateway after each data record.