| PROFIBUS Interface Center | SPC3 | | | |
| |
| | | | | | | |
| | | | | | | |
| Bit | Designation | Significance | | | | |
| 0 | Reserved | | | | | |
| 1 | Clear_Data | With this command, the output data is deleted in ‘D’ and is changed | |
| | | to ‘N.’ | | | | |
| 2 | Unfreeze | With „Unfreeze,“ freezing input data iscancelled. | |
| 3 | Freeze | The input data is fetched from ‘N’ to ‘D’and „frozen“. New input data | |
| | | is not fetched again until the master sends the next ‘Freeze’ | |
| | | command. | | | | |
| 4 | Unsync | The „Unsync“ command cancels the „Sync“ command. | |
| 5 | Sync | The output data transferred with a WRITE_READ_DATA telegram is | |
| | | changed from ‘D’ to ‘N.’ The following transferredoutput data is kept | |
| | | in ‘D’ until the next ‘Sync’ command is given. | |
| 6,7 | Reserved | The „Reserved“ designation specifies hat these bits are reserved for | |
| | | future function expansions. | |
Figure 6.15: Data Format for the Global_Control Telegram
If the Control_Comand byte changed at the last received Global_Control telegram, SPC3 additionally generates the ‘New_GC_Command’ interrupt. During nitialization, SPC3 presets the ‘R_GC_Command’ RAM cell with 00H. The user can read and evaluate this cell.
So that Sync and Freeze can be carried out, these functions must be enabled in the mode register.
6.2.7 Read_Inputs (SAP56)
SPC3 fetches the input data like it does for the Write_Read_Data Telegram. Prior to sending, ‘N’ is shifted to ‘D,’ if new input data are available in ‘N.’ For ‘Diag.Freeze_Mode = 1,’ there is no buffer change.
6.2.8 Read_Outputs (SAP57)
SPC3 fetches the output data from the Dout buffer in ‘U’. The user must preset the output data with 0’‘ during start-up so that no invalid data can be sent here. If there is a buffer change from ‘N’ to ‘U’(through the Next_Dout_Buffer_Cmd) between the first call-up and the repetition, the new output data is sent during the repetition.
6.2.9 Get_Config (SAP59)
The user makes the configuration data available in the Read_Cfg buffer. For a change in the configuration after the Check_Config telegram, the user writes the changed data in the Cfg buffer, sets ‘EN_Change_Cfg_buffer = 1’ (see Mode-Register1), and SPC3 then exchanges the Cfg buffer for the Read_Cfg buffer. (See Section 3.2.3.) If there is a change in the configuration data (for example, for the modular DP systems) during operation, the user must return with ‘Go Offline’ (see Mode Register1) to ‘Wait_Prm’ to SPC3.
Page 36 | V1.3 | SPC3 Hardware Description |
2003/04 | | Copyright (C) Siemens AG 2003. All rights reserved. |
Simatic NET
Page
SIM Atic NET
Profibus Interface Center
SPC3 Hardware Description
Versions
Release Date Changes
DPBuffer Structure Description of the DP Services
Mode Register
Status Register Interrupt Controller Watchdog Timer
Directory
Pin Assignment Example for the RS 485 Interface
11.3 Diagnostics Processing from the System View
Asic Test
SPC3
Introduction
Function Overview
Pin Description
Cmos
CPD Cmos with pull down TTLt Schmitt trigger V1.3
5FFH
Memory Allocation
Memory Area Distribution in the SPC3
Segment
Processor Parameters Latches/Register
0EH 0FH
Significance Write Access
OCH 0DH
Organizational Parameters RAM
1CH
1AH
1BH
1DH
Mode Register
Asic Interface
Disstartcontrol
Exiting the Offline state
Mode Register 1 Mode-REG1, writable
STARTSPC3
EOI
Status Register
Fdlindst
Status Register Bit15 . .readable
Interrupt Controller
SPC3 IRR IMR
Dxout
IMR
IAR
Baud Rate Monitoring
Watchdog Timer
Automatic Baud Rate Identification
Response Time Monitoring
PROFIBUS-DP Interface
DPBuffer Structure
Uart
RAM
Aux-Buffer Management
Sequence for the SetSlaveAddress Utility
Description of the DP Services
SetSlaveAddress SAP55
Parameter Data Processing Sequence
SetParam SAP61
Parameter Data Structure
CheckConfig SAP62
SPC3
SPC3
Diagnostics Processing Sequence
SlaveDiagnosis SAP60
Writing Outputs
Structure of the Diagnostics Buffer
WriteReadData / DataExchange DefaultSAP
Reading Inputs
UserWatchdogTimer
GlobalControl SAP58
ReadOutputs SAP57
GetConfig SAP59
ReadInputs SAP56
General Description
Hardware Interface
Universal Processor Bus Interface
Bus Interface Unit BIU
XINT/MO Mode
Bus Interface V1.3
Switching Diagram Principles
Low Cost System with 80C32
System X86-Mode
SPC3
Application with the 80 C
Application with th 80 C
Asic Test
Interface Signals
Uart
Permitted Operating Values
Technical Data
Maximum Limit Values
DC-Specifikation of the I/O- Drivers
Current Tabelle 8.5 Leakage current of the output drivers
AC-Specification for the Output Drivers
Tabel 8.3 DC-Specifikation of the I/O- Drivers
Clock pulse 48 Mhz
Timing Characteristics
SYS Bus Interface
Clock Pulse Timing
ST-Vers Min Max Unit
Reset
Timing in the Synchronous C32-Mode
TBD
Synchronous Intel-Mode, Processor-Read-Timing
Synchronous Intel-Mode, Processor-Write-Timing
Parameter Min Max
Timing in the Asynchronous Intel Mode X86 Mode
ST-Vers
Asynchronous Intel-Mode, Processor-Write-Timing
Asynchronous Intel-Mode, Processor-Read-Timing
XRD XCS Xready
XWR XCS
4.1 74.2
Synchronous Motorola-Mode, Processor-Read-Timing
Synchronous Motorola-Mode, Processor-Write-Timing
Timing in the Asynchronous Motorola-Mode for example, 68HC16
Asynchronous Motorola-Mode, Processor-Write-Timing
Asynchronous Motorola-Mode, Processor-Read-Timing
XCS Xdsack
Serial Bus Interface
Pulse 48 MHz
Housing PQFP-44 Housing SPC3 Hardware Description
13.90
Symbol Min Typ Max AMI-Vers
13.65
14.15
RTS
Profibus Interface
Pin Assignment
TXD
Example for the RS 485 Interface
SN65ALS1176
Profibus User Organisation
Appendix
Addresses
Technical contact person at ComDeC in Germany
10.3.1 SPC3 AMI
General Definition of Terms
Ordering of ASICs
10.3.2 SPC3 ST
Introduction
Appendix a Diagnostics Processing in Profibus DP
Diagnostics Bits and Expanded Diagnostics
Statdiag
Identifier Byte 7 has Etc Identifier Byte 0 has
Simatic S5 / COM ET
Diagnostics Processing from the System View
Single Diagnostics
Combi
Appendix B Useful Information
Data format in the Siemens PLC Simatic
Page
Siemens Aktiengesellschaft