Profichip VPC3+C - Check Configuration (SAP 62)

To Next Page

To Previous Page

PROFIBUS DP Interface 6

If another Set_Prm telegram is supposed to be received in the meantime,

the signal Prm_Conflict is returned for the positive or negative

acknowledgement of the first Set_Prm telegram. Then the user must repeat

the validation because the VPC3+C has made a new Parameter-Buffer

available.

6.2.3 Chk_Cfg (SAP 62)

The user checks the correctness of the configuration data. After receiving

an error-free Chk_Cfg telegram, the VPC3+C exchanges the Aux-Buffer 1/2

(all data bytes are entered here) for the Config-Buffer, stores the input data

length in R_Len_Cfg_Data and generates the New_Cfg_Data interrupt.

Then the user has to check the User_Config_Data and either respond with

User_Cfg_Data_Okay_Cmd or with User_Cfg_Data_Not_Okay_Cmd. The

pure data is entered in the buffer in the format of the standard.

The user response (User_Cfg_Data_Okay_Cmd or the

User_Cfg_Data_Not_Okay_Cmd response) clears the New_Cfg_Data

interrupt. The user cannot acknowledge the New_Cfg_Data in the IAR

If an incorrect configuration is reported, several diagnosis bits are changed

and the VPC3+C branches to state WAIT-PRM.

For a correct configuration, the transition to DATA-EXCH takes place

immediately, if trigger counters for the parameter telegrams and

configuration telegrams are at 0. When entering into DATA-EXCH, the

VPC3+C also generates the Go/Leave_DATA-EXCH Interrupt.

If the received configuration data from the Config-Buffer is supposed to

result in a change to the Read_Config-Buffer (contains the data for the

Get_Cfg telegram), the user have to make the new Read_Config data

available in the Read_Config-Buffer before the User_Cfg_Data_Okay_Cmd

acknowledgement, that is the user has to copy the new configuration data

into the Read_Config-Buffer.

During acknowledgement, the user receives information about whether

there is a conflict or not. If another Chk_Cfg telegram was supposed to be

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+C 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.

VPC3+C User Manual

Revision 1.03 43