Pilz PNOZ mm0p 24VDC - Manual (Page 74)

Fieldbus modules
Operating Manual PNOZmulti communication interfaces
1001154-EN-13
74
Communication channels with the PNOZmulti
This chapter describes the communication channels between the sercos III Master and the
PNOZmulti, based on the sercos III communication phases (CP) and the selected connec-
tion configuration for input/output data and table data.
} NRT
The PNOZmulti input data is set to "0" in NRT status. Communication is only possible
via a web interface.
} Communication phase 0 and 1 (CP0, CP1)
The PNOZmulti input data is set to "0" in communication phase 0. No communication is
possible.
} Communication phase 2 and 3 (CP2, CP3)
Communication is only possible via the sercos service channel (SVC). Four Bytes of in-
put/output data can be written via IDN S-0-1502.0.5 (Digital PDOUT) and read via the
command S-0-1503.0.9 (Digital PDIN). 16 Bytes of table data can be written via the
command S-0-1507.0.5 (Complex PDOUT) and read via the command S-0-1507.0.9
(Complex PDIN).
The full object buffer can be accessed via the service channel SVC Complex transmit/
receive (S-0-1507.0.19 and S-0-1507.0.20).
} Communication phase 4 (CP4)
Communication is possible via the sercos service channel (SVC) and also via the re-
al-time channel (RT). It is possible to transmit input/output data only or additional table
data via the real-time channel (RT), depending on the configuration. Please note that
data disturbances may occur if the service channel and real-time channel are used at
the same time.
Diagnostics
The IDNs S-0-0095 (diagnostic message) and S-0-039 (diagnostic number) are supported
and are always set simultaneously by the PNOZmulti. The diagnostic classes are prioritised
in accordance with the sercos specification.
} sercos diagnostic numbers
Various pre-defined diagnostic numbers are used (see sercos specification)
} PNOZ diagnostic numbers
The 48 PNOZ error and status messages (ref.: Chapter 4.6.3.7) from S-0-1503.0.19 are
also shown in S-0-0095 and S-0-0390 as manufacturer-specified diagnostics in opera-
tional or error class.
Operational: 0x010A0000 to 0x010A002F
Error: 0x010F0000 to 0x010F002F
4.5.7.4
4.5.7.5