23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

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

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

46-6 Industrial Communication Systems<br />

Safety PLC<br />

Standard PLC<br />

FIGURE 46.8<br />

Split assignment of safety and standard tasks.<br />

standard tasks may also be assigned to different controllers and networks as shown in Figure 46.8.<br />

Any so-called acyclic <strong>communication</strong>s between devices and controllers or supervisors such as programming<br />

devices are intended for configuration, parameterization, diagnosis, and maintenance purposes.<br />

46.2.4 Cyclic Communication PDU<br />

DP-DP coupler<br />

The PDU (protocol data unit) structure of the Profibus I/O data exchange message is exactly the same<br />

whether or not there is any safety data in the message. This structure has separate data areas assigned<br />

to each module in a modular slave device, facilitating the intermixing of safety and standard modules<br />

as shown in Figure 46.9, where the safety modules map onto the Profisafe data areas in the PDU. Data<br />

associated with a safety module are contained within an area of the PDU assigned only to that safety<br />

module and affects no other data areas.<br />

As has been illustrated here, standard and safety devices may be intermixed on the same network and<br />

standard and safety modules may be intermixed within the same modular slave device. The only change<br />

required within the standard I/O data exchange PDU structure was to include error-detection information<br />

within the data area associated with a safety module. No changes were made to the data areas of<br />

standard modules. This isolated area of change allowed the same implementations of Profisafe across<br />

Profibus-DP, Profibus-PA, and Profinet (Figure 46.10).<br />

The detailed structure of the safety data and how it affects the desired error-detection solutions will<br />

be described in the following sections. The data structure supports the checks required to detect all the<br />

error types listed in Figure 46.5. Figure 46.11 shows the general format of the safety data while Figures<br />

46.12 and 46.13, respectively, show the details of the control byte sent in the safety data from the controller<br />

and the status byte in the safety data returned from the device/module.<br />

The mechanisms used for error detection, i.e., consecutive numbering, timeout with receipt, code<br />

name for sender/receiver, and data consistency check (cyclic redundancy check, CRC), will be briefly<br />

discussed in the following sections.<br />

Head<br />

module<br />

Safety<br />

module<br />

Normal<br />

module<br />

Normal<br />

module<br />

Safety<br />

module<br />

Safety<br />

module<br />

Normal<br />

module<br />

Safety<br />

module<br />

Data<br />

Safety<br />

data<br />

Normal<br />

data<br />

Normal<br />

data<br />

Safety<br />

data<br />

Safety<br />

data<br />

Normal<br />

data<br />

Safety<br />

data<br />

FIGURE 46.9<br />

Intermixed standard and safety I/O modules.<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

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

Saved successfully!

Ooh no, something went wrong!