Siemens SPC3 manual SetParam SAP61, Parameter Data Structure, Parameter Data Processing Sequence

PROFIBUS Interface Center SPC3

6.2.2 Set_Param (SAP61)

6.2.2.1 Parameter Data Structure

SPC3 evaluates the first seven data bytes (without user prm data), or the first eight data bytes (with user prm data). The first seven bytes are specified according to the standard. The eighth byte is used for SPC3- specific characteristics. The additional bytes are available to the application.

Byte					Bit Position					Designation
	7		6	5	4	3	2	1	0
0	Lock		Unlo.	Sync	Free	WD	Res	Res	Res	Station status
	Req		Req	Req	Req	on
1										WD_Fact_1
2										WD_Fact_2
3										MinTSDR
4										Ident_Number_High
5										Ident_Number_Low
6										Group_Ident
7	0		0	0	0	0	WD_	Dis	Dis	Spec_User_Prm_Byte
							Base	Stop	Start
8-243										User_Prm_Data
Byte 7		Spec_User_Prm_Byte
Bit		Name			Significance						Default State
0		Dis_Startbit			The start bit monitoring in the						Dis_Startbit= 1 ,
					receiver is switched off with this bit.						that is, start bit monitoring is
											switched off.
1		Dis_Stopbit			Stop bit monitoring in the receiver is						Dis_Stopbit= 0,
					switched off with this bit.						that is, stop bit monitoring is not
											switched off.
2		WD_Base			This bit specifies the time base used						WD_Base= 0,
					to clock the watchdog.						that is, the time base is 10 ms
					WD_Base = 0: time base 10 ms
					WD_Base = 1: time base 1 ms
3-7		res			to be parameterized with 0						0

Figure 6.5: Data Format for the Set_Param_Telegram

6.2.2.2 Parameter Data Processing Sequence

In the case of a positive validatation for more than seven data bytes, SPC3 carries out the following reaction, among others:

SPC3 exchanges Aux-Puffer1/2 (all data bytes are input here) for the Prm buffer, stores the input data length in ‘R_Len_Prm_Data’, and triggers the ‘New_rmP_Data Interrupt’. The user must then check the

‘User_Prm_Data’ and either reply with the ‘User_PrmData_Okay_Cmd’ or with ‘User_Prm_Data_Not_Okay_Cmd.’ The entire telegramis input in the buffer, that is, application-specific parameter data are stored beginning with data byte 8 only.

The user response (User_Prm_Data_Okay_Cmd or User_Prm_Data_Not_Okay_Cmd) again takes back the ‘New_Prm_Data’ interrupt. The user may not acknowledge the ‘New_Prm_Data’ interrupt in the IAR register.

The relevant diagnostics bits are set with the ‘User_Prm_Data_Not_Okay_Cmd’ message and are branched to ‘Wait_Prm.’

The ‘User_Prm_Data_Okay’ and ‘User_Prm_Data_Not_Okay’ acknowledgements are reading accesses to defined registers with the relevant signals:

∙ ‘User_Prm_Finished’: No additional parameter telegram is present.

∙‘Prm_Conflict’ :An additional parameter telegramis present, processing again

∙ ‘Not_Allowed’,	Access not permitted in the current bus state
Page 30	V1.3	SPC3 Hardware Description
2003/04		Copyright (C) Siemens AG 2003. All rights reserved.