01/2007
8.6 DP slave: MCP 310
8-205
© Siemens AG 2007 All Rights Reserved
SINUMERIK 840Di sl Manual (HBIsl) – 01/2007 Edition
Notice
Function blocks FC 19, FC 24 and FC 25 are part of the PLC basic program. It
is the user’s (machine manufacturer’s) responsibility to call the block correctly
and/or assign the interface the appropriate parameters.
References
A detailed description of the function blocks for transferring machine control
panel signals to the VDI interface can be found in:
/FB1/ Description of Functions, Basic Functions: P3, PLC Basic Program
Section: FC 19: MCP_IFM ...
Section: FC 24: MCP_IFM2 ...
Section: FC 25: MCP_IFT ...
The following example shows the communication parameter settings for func-
tion block FB 1 for an MCP:
MCPNum := 1 // Number of MCPs
MCP1In := P#E0.0 // Address: Input data
MCP1Out := P#A0.0 // Address: Output data
MCP1StatRec := P#A8190.0 // Configured diagnostic address
MCP1BusAdr := 5 // PROFIBUS address of the DP slave MCP
MCP1Timeout := S5T#700MS // Default setting
MCPMPI := FALSE // No MPI bus
MCP1Stop := FALSE // Deactivation of the DP slave MCP
MCPSDB210 := FALSE // No SDB210 for MCP
MCPCopyDB77 := FALSE // No copying to DB 77
MCPBusTyp := B#16#33 // PROFIBUS
If an MCP is connected via PROFIBUS DP, the basic PLC program does not
check for module failure.
In this case the MCP is monitored by a standard mechanism to monitor the ac-
tive DP slave:
S PLC operating system
S PROFIBUS controller
If the failure of DP slave: MCP 310 is detected the PLC goes into the STOP
status as default.
to allow the user to intervene when a DP slave: MCP 310, the following orga-
nization blocks are inserted in the PLC user program:
S OB 82: Diagnostic alarm
S OB 86: Rack failure
Please refer to the corresponding SIMATIC literature for details of linking orga-
nization blocks and evaluating diagnostic data.
Example
PLC user program
Customized
response
8 PROFIBUS DP Communication
To Next Page
Loading...
