Table of Contents
Advertisement
6 PROFIBUS DP Extensions
received in the meantime, the user receives the Cfg_Conflict signal during
the positive or negative acknowledgement of the first Chk_Cfg telegram.
Then the user must repeat the validation, because the VPC3+S have made
a new Config-Buffer available.
The User_Cfg_Data_Okay_Cmd and User_Cfg_Data_Not_Okay_Cmd
acknowledgements are read accesses to defined memory cells with the
relevant Not_Allowed, User_Cfg_Finished, or Cfg_Conflict signals.
If the New_Prm_Data and New_Cfg_Data are supposed to be present
simultaneously during start-up, the user must maintain the Set_Prm
and then the Chk_Cfg acknowledgement sequence.
Address
Address
Figure 6-8: Coding of User_Cfg_(Not)_Okay_Cmd
6.2.4
Slave_Diag (SAP 60)
Diagnosis Processing Sequence
Two buffers are available for diagnosis. These two buffers can have
different lengths. One Diagnosis-Buffer, which is sent on a diagnosis
request, is always assigned to the VPC3+S. The user can pre-process new
diagnosis data in the other buffer parallel. If the new diagnosis data are to
be sent, the user issues the New_Diag_Cmd to make the request to
exchange the Diagnosis-Buffers. The user receives confirmation of the
buffer exchange with the Diag_Buffer_Changed interrupt.
When the buffers are exchanged, the internal Diag_Flag is also set. For an
activated
50
7
6
5
10H
0
0
0
7
6
5
11H
0
0
0
Diag_Flag,
Revision 1.04
Bit Position
4
3
2
1
0
0
0
0
0
1
Bit Position
4
3
2
1
0
0
0
0
0
1
the
VPC3+S
responds
Designation
0
User_Cfg_
Data_Okay
0
User_Cfg_Finished
1
Cfg_Conflict
1
Not_Allowed
Designation
0
User_Cfg_
Data_Not_Okay
0
User_Cfg_Finished
1
Cfg_Conflict
1
Not_Allowed
during
the
VPC3+S User Manual
Copyright © profichip GmbH, 2012
next
Advertisement
Table of Contents
