Profibus interface center, Spc3 – Siemens SPC3 User Manual

Page 34

Advertising
background image

PROFIBUS Interface Center

SPC3

Page 32

V1.3

SPC3 Hardware Description

2003/04

Copyright (C) Siemens AG 2003. All rights reserved.

Address

Bit Position

Designation

Control
Register

7

6

5

4

3

2

1

0

10H

0

0

0

0

0

0

User_Cfg_Data_Okay

0

0

User_Cfg_Finished

0

1

Cfg_Conflict

1

1

Not_Allowed

Address

Bit Position

Designation

Control
Register

7

6

5

4

3

2

1

0

11H

0

0

0

0

0

0

User_Cfg_Data_Not_Okay

0

0

User_Cfg_Finished

0

1

Cfg_Conflict

1

1

Not_Allowed

Figure 6.7: Coding of the User_Cfg_Data_Not/_Okay_Cmd

6.2.4 Slave_Diagnosis (SAP60)

6.2.4.1 Diagnostics Processing Sequence

Two buffers are available for diagnostics. The two buffers can have varying lengths. SPC3 always has one
diagnostics buffer assigned to it, which is sent for a diagnostics call-up. The user can pre-process new
diagnostics data in parallel in the other buffer. If the new diagnostics data are to be sent now, the user uses
the ‘New_Diag_Cmd’ to make the request to exchange the diagnostics buffers. The user receives
confirmation of the exchange of the buffers with the ‘Diag_Puffer_Changed Interrupt.’

When the buffers are exchanged, the internal ‘Diag_Flag’ is also set. For an activated ‘Diag_Flag,’ SPC3
responds during the next Write_Read_Data with high-priority response data that signal the relevant master
that new diagnostics data are present at the slave. Then this master fetches the new diagnostics data with a
Slave_Diagnosis telegram. Then the ‘Diag_Flag” is reset again. If the user signals ‘Diag.Stat_Diag = 1,’
however (static diagnosis, see the structure of the diagnostics buffer), then ‘Diag_Flag’ still remains
activated after the relevant master has fetched the diagnosis. The user can poll the ‘Diag_Flag’ in the
status register to find out whether the master has already fetched the diagnostics data before the old data is
exchanged for the new data.

Status coding for the diagnostics buffers is stored in the‘Diag_bufferSM’ processor parameter. The user can
read this cell with the possible codings for both buffers: ‘User,’ ‘SPC3,’ or ‘SPC3_Send_Mode.’


Address

Bit Position

Designation

Control
Register

7

6

5

4

3

2

0

0CH

0

0

0

0

D_Puf2

D_Puf1

Diag_Puffer_SM

X1

X2

X1

X2 See below for coding.


X1

X2 Coding

0

0

Each for the D_Buf2 or D_Buf1

0

1

User

1

0

SPC3

1

1

SPC3_Send_Mode

Figure 6.8: Diag_Buffer Assignment

The ‘New_Diag_Cmd’ is also a read access to a defined processor parameter with the signal as to which
diagnostics buffer belongs to the user after the exchange, or whether both buffers are currently assigned to
SPC3 (‘no Puffer’, ‘Diag_Puf1’, ‘Diag_Puf2’).

Advertising