Data Structure On The Fieldbus Side E.g.: Profibus; Example: Fc1 + Fc2 - Softing echolink one2PROFINET Instruction Manual

Implemented protocols in echolink one
8.7.1

Data structure on the fieldbus side e.g.: PROFIBUS

Applies to In and Out
1. Byte: trigger byte, optional (see chapter 8.5, The trigger byte)
2. Byte: fieldbus length byte, optional (see chapter 8.6, The length byte)
3. Byte: process data
4. Byte: process data
....
Data structure
8.7.1.1

Example: FC1 + FC2

A Modbus Master (external device) sends a request with function code 1 or 2.
Note: 
Modbus Master Request Address (High + Low)
Address request 01 .. 08 will always be on address 01.
Address request 09 .. 16 will always be on address 09.
Address request 17 .. 24 will always be on 17.
...
Configuration:

Fieldbus sends to echolink one
08 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A...

Note: The 1. byte (0x08) is the fieldbus length byte. This means only the following 8 Bytes are
stored in the echolink one.
Connected Modbus Master sends request to the RS232/484 side of the echolink one:
Start-Address 0001, Length 56 (38h), FC1 (-Read Coil Status)
[01] [01] [00] [00] [00] [38] [3d] [d8]
echolink one sends response via RS232/485:
[01] [01] [07] [01] [02] [03] [04] [05] [06] [07] [6b] [c5]
23

echolink one2PROFINET V. 1.0
Softing Industrial Automation GmbH
15.1.15