24.10.2013 Views

Configuring Hardware and Communication Connections STEP 7.pdf

Configuring Hardware and Communication Connections STEP 7.pdf

Configuring Hardware and Communication Connections STEP 7.pdf

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3.10.3 Programming DPV1 Devices<br />

New Interrupt OBs for DPV1 Events<br />

<strong>Configuring</strong> the Distributed I/O (DP)<br />

DPV1 Slaves can trigger interrupts. You can use the respective OBs the S7 CPU<br />

operating system provides up to now for Diagnostic/System/Extraction/Insertion<br />

Interrupts.<br />

New are the OBs for the following interrupts:<br />

DPV1 Interrupt OB Explanation<br />

Status Interrupt OB 55 A Status Interrupt can be triggered by the operating<br />

state transition of a module, for example, from RUN<br />

to STOP mode.<br />

Refer to the respective DPV1 Slave manufacturer's<br />

documentation for detailed information on events<br />

that can trigger a Status Interrupt.<br />

Update Interrupt OB 56 An Update Interrupt can be triggered after a slot<br />

was reconfigured. For example, this might occur as<br />

a result of local or remote access to the parameters.<br />

Refer to the respective DPV1 Slave manufacturer's<br />

documentation for detailed information on events<br />

that can trigger an Update Interrupt.<br />

Manufacturer Specific<br />

Interrupt<br />

OB 57 The event triggering a Manufacturer Specific<br />

Interrupt can be specified by the manufacturer of a<br />

DPV1 Slave<br />

<strong>Configuring</strong> <strong>Hardware</strong> <strong>and</strong> <strong>Communication</strong> <strong>Connections</strong> with <strong>STEP</strong> 7<br />

A5E00706939-01 3-61

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!