Shopping Cart

No products in the cart.

BS EN 61800-7-303:2016

$215.11

Adjustable speed electrical power drive systems – Generic interface and use of profiles for power drive systems. Mapping of profile type 3 to network technologies

Published By Publication Date Number of Pages
BSI 2016 116
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

IEC 61800-7-303:2015 specifies the mapping of the profile type 3 (PROFIdrive) specified in IEC 61800-7-203 onto different network technologies. This edition includes the following significant technical changes with respect to the previous edition: – Enhanced definition of the using of PROFINET IO Diagnosis ASE and Alarm ASE; – Minor updates in the mapping of the Base Mode Parameter Access to PROFIBUS and PROFINET.

PDF Catalog

PDF Pages PDF Title
6 English
CONTENTS
11 FOREWORD
13 INTRODUCTION
0.1 General
16 0.2 Patent declaration
Figures
Figure 1 – Structure of IEC 61800-7
18 1 Scope
2 Normative references
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
23 3.2 Abbreviated terms
25 4 Mapping to PROFIBUS DP
4.1 General
4.2 Mapping to PROFIBUS data types
26 4.3 Base Model at PROFIBUS DP
4.3.1 Communication devices
Tables
Table 1 – Mapping of data types
27 4.3.2 Communication relationship
Figure 2 – PROFIBUS DP Devices in a PROFIdrive drive system
28 4.3.3 Communication network
Figure 3 – PROFIdrive Devices and their relationship for PROFIBUS DP
29 4.3.4 Communication services
Figure 4 – General Communication Model for PROFIdrive at PROFIBUS DP
30 Figure 5 – PROFIBUS DP DXB communication designations
31 4.3.5 P-Device communication model
Figure 6 – Synchronous communication for PROFIdrive at PROFIBUS DP
Figure 7 – Overview about the P-Device communication model on PROFIBUS
32 4.3.6 Base Model State Machine
33 4.3.7 Definition of the CO
4.4 Drive Model at PROFIBUS DP
4.4.1 P-Device
Figure 8 – Mapping of the Base Model State Machine at PROFIBUS DP
34 4.4.2 Drive Unit
4.5 DO IO Data
4.5.1 COs for DO IO Data configuration
Figure 9 – PROFIBUS DP specific logical P-Device model (multi axis drive)
35 Figure 10 – Mapping of PROFIBUS Slot to the PROFIdrive DO
36 4.5.2 Standard telegram configuration
Table 2 – DP IDs and PROFIdrive IDs of the standard telegrams
37 Table 3 – 1 Drive Axis, standard telegram 3
Table 4 – 2 Drive Axes, standard telegram 3
38 4.5.3 Cyclic Data Exchange between DP-Slaves (DXB)
Table 5 – 2 Drive Axes, standard telegram 3, per axis one DXB link each with 2 words
Table 6 – 1 Drive Axis, standard telegram 20
40 Figure 11 – Application example of DXB communication
41 Table 7 – Slave No.11 (Publisher)
Table 8 – Slave No.12 (Publisher and Subscriber)
42 Table 9 – Configuration of the DXB communication link of the coating drive
Table 10 – Slave No.10 (Subscriber)
Table 11 – Configuration of the DXB communication links of the unwinder
43 Figure 12 – Dataflow inside a Homogeneous P-Device with DXB relations
44 Figure 13 – Structure of a DXB Subscriber Table (inside a Prm-Block)
45 Figure 14 – Timing diagram of PROFIBUS with Cyclic Data Exchange between DP-slaves
47 4.6 Parameter Access
4.6.1 PAP for Parameter Access
Table 12 – Parameters (Set_Prm, GSD) for slave-to-slave communication (Data-eXchange Broadcast)
48 Figure 15 – PAP and Parameter Access mechanism for a PROFIBUS homogeneous P-Device
49 4.6.2 Definition of the Base Mode Parameter Access mechanism
Figure 16 – PAP and Parameter Access mechanism for a PROFIBUS heterogeneous P-Device
50 Table 13 – Services used for Parameter Access on PROFIBUS DP
Table 14 – Defined PAPs for Parameter Access
51 Figure 17 – Telegram sequence via MS1 AR or MS2 AR
52 Table 15 – State machine for DP-slave processing
Table 16 – MS1/MS2 AR telegram frame, Write request
53 Table 17 – MS1/MS2 AR telegram frame, Write response
Table 18 – MS1/MS2 AR telegram frame, Read request
Table 19 – MS1/MS2 AR telegram frame, Read response
54 Table 20 – Process data ASE telegram frame, Error response
55 Table 21 – Allocation of Error class and code for PROFIdrive
Table 22 – Data block lengths
56 Table 23 – Limits due to the Process data ASE data block length
57 4.7 P-Device configuration
4.7.1 P-Device configuration on PROFIBUS DP
4.7.2 Drive Unit configuration on PROFIBUS DP
Table 24 – GSD parameters for the MS1/MS2 AR services
58 Figure 18 – Drive Unit Structure
59 4.7.3 Getting the Drive Object – ID (DO-ID)
Figure 19 – Configuration and communication channels for the Modular Drive Unit type at PROFIBUS DP
60 Figure 20 – Meaning of parameter PNU978 (list of all DO-IDs) for the DU at PROFIBUS DP
61 4.8 Diagnosis
4.9 Clock Synchronous Operation
4.9.1 Sequence of an isochronous DP cycle
Figure 21 – Example of P978 for a complex Modular Drive Unit at PROFIBUS DP
62 4.9.2 Time settings
Figure 22 – Sequence of an isochronous DP cycle
63 Figure 23 – Time settings
65 Figure 24 – Example: Simplest DP cycle
66 Figure 25 – Example: Optimised DP cycle
67 4.9.3 Running-up, cyclic operation
Figure 26 – Example: Optimised DP cycle (TMAPC = 2 × TDP)
Table 25 – DP services for running-up, cyclic operation
68 Figure 27 – Running-up (sequence with respect to time)
69 Figure 28 – Phase 1: Slave parameterisation, configuration
70 Figure 29 – Phase 2: Synchronisation of the PLL to the Clock Global Control
72 Figure 30 – Phase 3: Synchronisation of the slave application with the master’s Sign-Of-Life
73 Figure 31 – State diagram of Phases 2 and 3 of the run-up
74 Figure 32 – Phase 4: Synchronisation of the master application to the slave’s SignOfLife
75 Figure 33 – Example: Running-up to cyclic operation (Phase 1) (TMAPC/TDP = 2/1)
76 Figure 34 – Example: Running-up to cyclic operation (Phase 2) (TMAPC/TDP = 2/1)
Figure 35 – Example: Running-up to cyclic operation (Phase 3) (TMAPC/TDP = 2/1)
77 4.9.4 Parameterisation, configuring (Set_Prm, GSD)
Figure 36 – Example: Running-up to cyclic operation (Phase 4) (TMAPC/TDP = 2/1)
Figure 37 – Example: Running-up to cyclic operation (Phase 5) (TMAPC/TDP = 2/1)
78 Table 26 – Parameters (Set_Prm, GSD) for “Clock Cycle Synchronous Drive Interface”
79 4.9.5 Clock cycle generation (Global Control) and clock cycle save
Table 27 – Possible synchronisation type combinations
80 Table 28 – Conditions for Isochronous Mode
81 Figure 38 – PLL for clock regeneration in the slave
Table 29 – Input signals of the PLL
82 Table 30 – Output signals of the PLL
83 4.9.6 Monitoring mechanisms
Figure 39 – Run time compensation
84 Figure 40 – DP cycle violation
85 4.10 PROFIBUS DP specific parameter
4.10.1 Overview of the communication interface related parameters
4.10.2 Definition of the specific parameters
Figure 41 – Example: Clock failure (fault after 4 DP cycles)
Table 31 – Overview of the specific PROFIBUS DP parameters for “Communication system interfaces”
86 4.11 Specified communication functions for the Application Classes
Table 32 – PROFIdrive specific parameter listed by number
Table 33 – Coding of the data rate in parameter 963
87 5 Mapping to PROFINET IO
5.1 General
5.2 Mapping to PROFINET IO data types
Table 34 – Specified communication functions for the Application Classes
88 5.3 Base Model at PROFINET IO
5.3.1 Communication devices
Table 35 – Mapping of data types
89 5.3.2 Communication relationship
Figure 42 – PROFINET IO Devices in a PROFIdrive drive system
90 5.3.3 Communication network
Figure 43 – PROFIdrive Devices and their relationship for PROFINET IO
91 5.3.4 Communication services
Figure 44 – General Communication Model for PROFIdrive at PROFINET IO
92 5.3.5 P-Device communication model
Figure 45 – Synchronous communication for PROFIdrive at PROFINET IO
Figure 46 – Overview about the P-Device communication model on PROFINET IO
93 Figure 47 – Contents of IO AR and Supervisor AR
94 5.3.6 Base Model State Machine
Figure 48 – M CR used for Cyclic Data Exchange between P-Devices
95 5.3.7 Definition of the CO
5.4 Drive Model at PROFINET IO
5.4.1 P-Device
Figure 49 – Mapping of the Base Model State Machine at PROFINET IO
96 5.4.2 Drive Unit
5.4.3 DO architecture
Figure 50 – PROFINET IO specific Logical P-Device model (multi axis drive)
97 Figure 51 – Representation of the PROFIdrive DO by PROFINET IO Submodules (CO)
98 5.4.4 Definition of the Module Ident Number and API
5.4.5 Definition of the Submodule Ident Number
Figure 52 – Hierarchical model of the P-Device on PROFINET IO
99 Table 36 – Structure of the Submodule-ID
Table 37 – Definition of Submodule-Type Classes
100 5.5 DO IO Data
5.5.1 COs for DO IO Data configuration
5.5.2 IO Data Producer and Consumer Status
5.6 Parameter Access
5.6.1 PAPs for Parameter Access
Figure 53 – Modularity of the DO IO Data block (example)
101 5.6.2 Base Mode Parameter Access
Table 38 – Definition of Parameter Access Modes (PAP)
103 5.7 P-Device Configuration
5.7.1 P-Device Configuration on PROFINET IO
Figure 54 – Data flow for request and response for the Base Mode Parameter Access
104 5.7.2 Drive Unit Configuration on PROFINET IO
5.7.3 Getting the Drive Object – ID (DO-ID)
Figure 55 – Configuration and communication channelsfor the Modular Drive Unit type at PROFINET IO
105 5.8 Diagnosis
5.8.1 Use of PROFINET IO Diagnosis for PROFIdrive
5.8.2 Use of the Alarm ASE
Figure 56 – Meaning of parameter P978 “List of all DO-IDs” for the DU at PROFINET IO
106 5.8.3 Use of the ChannelDiagnosisData structure
Table 39 – Use of the AlarmNotification-PDU
Table 40 – Use of ChannelDiagnosisData
107 Figure 57 – Generation of Diagnosis Data according to the fault classes mechanism
108 5.8.4 Use of the ChannelErrorType
5.8.5 On demand access of Diagnosis Information
Table 41 – Use of ChannelErrorType
Table 42 – Use of the DiagnosisData
109 5.9 Clock Synchronous Operation
Figure 58 – Sequence of an isochronous Data Cycle
110 5.10 PROFINET IO specific parameter
5.10.1 Overview about the communication interface related parameters
5.10.2 Definition of the specific parameters
Table 43 – Overview of the specific PROFINET IO parameters for “Communication system interfaces”
111 Table 44 – PROFIdrive Specific Parameter listed by number
112 5.11 Specified communication functions for the Application Classes
5.12 I&M data records
Table 45 – Specified communication functions for the Application Classes
113 Bibliography
BS EN 61800-7-303:2016
$215.11