S
stem Confi
uration
Dec 2021
ATM60 / ATM90 / KHK53 37
8.2 Stipulations/Definitions
The term "octet", in the Profibus literature (profile definitions), designates a "BYTE" within a
Profibus DP data telegram. The following allocation applies:
Octet 1 2 3 ... n
BYTE 0 1 2 ... n-1
8.3 Parametrisation
In the 'Wait_Param' state, the parameterisation telegram generates an identification with the
master. The number and format of the telegram data result from the definition in the GSD file
and are checked by the slave, through the DP controller and the application software, resp.
The acknowledgement will be a response telegram to the master. The next state within the
'State Machine' is achieved only by recognising a valid telegram.
8.3.1 DP-Specific Standard Data
The DP-specific standard data (octet-1..7) is relevant to all DP slaves. This data is generated by
means of a projecting tool using the GSD file. The telegram data is checked directly in the DP
controller (ASIC) of the slave.
Service DDLM_SET_Prm
Octet Type Explanation Value (default)
1 BYTE DP protocol-specific allocations.
2 BYTE WD_Fact_1
(*n1)
3 BYTE WD_Fact_2
(*n1)
4 BYTE TSDR
(*n2)
5 BYTE Device ID, high byte
-- Device 'Ident_Number' (high)
(*n3)
6 BYTE Device ID, low byte
-- Device 'Ident_Number' (low)
(*n3)
7 BYTE Group ID -- 'Group_Ident' number
(*n1)
Defines the time of the Watchdog timer (10 ms based). The overall time results from:
{ 10 ms x WD_Fact_1 x WD_Fact_2 }.
(*n2)
Earliest slave response time in { TBit }. -- (11 x TBit <--> max. TSDR).
(*n3)
Ident. number of the slaves (2 bytes, allocated by PNO)
To Next Page
Loading...
Need help?
General
