{"id":252468,"date":"2024-10-19T16:40:08","date_gmt":"2024-10-19T16:40:08","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61800-7-3032016\/"},"modified":"2024-10-25T11:59:28","modified_gmt":"2024-10-25T11:59:28","slug":"bs-en-61800-7-3032016","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61800-7-3032016\/","title":{"rendered":"BS EN 61800-7-303:2016"},"content":{"rendered":"
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.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
6<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | INTRODUCTION 0.1 General <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 0.2 Patent declaration Figures Figure\u00a01 \u2013 Structure of IEC\u00a061800-7 <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 1 Scope 2 Normative references 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 3.2 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 4 Mapping to PROFIBUS DP 4.1 General 4.2 Mapping to PROFIBUS data types <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 4.3 Base Model at PROFIBUS DP 4.3.1 Communication devices Tables Table\u00a01 \u2013 Mapping of data types <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 4.3.2 Communication relationship Figure\u00a02 \u2013 PROFIBUS DP Devices in a PROFIdrive drive system <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 4.3.3 Communication network Figure\u00a03 \u2013 PROFIdrive Devices and their relationship for PROFIBUS DP <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 4.3.4 Communication services Figure\u00a04 \u2013 General Communication Model for PROFIdrive at PROFIBUS DP <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | Figure\u00a05 \u2013 PROFIBUS DP DXB communication designations <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 4.3.5 P-Device communication model Figure\u00a06 \u2013 Synchronous communication for PROFIdrive at PROFIBUS DP Figure\u00a07 \u2013 Overview about the P-Device communication model on PROFIBUS <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 4.3.6 Base Model State Machine <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 4.3.7 Definition of the CO 4.4 Drive Model at PROFIBUS DP 4.4.1 P-Device Figure\u00a08 \u2013 Mapping of the Base Model State Machine at PROFIBUS DP <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 4.4.2 Drive Unit 4.5 DO IO Data 4.5.1 COs for DO IO Data configuration Figure\u00a09 \u2013 PROFIBUS DP specific logical P-Device model (multi axis drive) <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | Figure\u00a010 \u2013 Mapping of PROFIBUS Slot to the PROFIdrive DO <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 4.5.2 Standard telegram configuration Table\u00a02 \u2013 DP IDs and PROFIdrive IDs of the standard telegrams <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Table\u00a03 \u2013 1 Drive Axis, standard telegram 3 Table\u00a04 \u2013 2 Drive Axes, standard telegram 3 <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 4.5.3 Cyclic Data Exchange between DP-Slaves (DXB) Table\u00a05 \u2013 2 Drive Axes, standard telegram 3, per axis one DXB link each with 2 words Table\u00a06 \u2013 1 Drive Axis, standard telegram 20 <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Figure\u00a011 \u2013 Application example of DXB communication <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Table\u00a07 \u2013 Slave No.11 (Publisher) Table\u00a08 \u2013 Slave No.12 (Publisher and Subscriber) <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | Table\u00a09 \u2013 Configuration of the DXB communication link of the coating drive Table\u00a010 \u2013 Slave No.10 (Subscriber) Table\u00a011 \u2013 Configuration of the DXB communication links of the unwinder <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure\u00a012 \u2013 Dataflow inside a Homogeneous P-Device with DXB relations <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Figure\u00a013 \u2013 Structure of a DXB Subscriber Table (inside a Prm-Block) <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Figure\u00a014 \u2013 Timing diagram of PROFIBUS with Cyclic Data Exchange between DP-slaves <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 4.6 Parameter Access 4.6.1 PAP for Parameter Access Table\u00a012 \u2013 Parameters (Set_Prm, GSD) for slave-to-slave communication (Data-eXchange Broadcast) <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Figure\u00a015 \u2013 PAP and Parameter Access mechanism for a PROFIBUS homogeneous P-Device <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | 4.6.2 Definition of the Base Mode Parameter Access mechanism Figure\u00a016 \u2013 PAP and Parameter Access mechanism for a PROFIBUS heterogeneous P-Device <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | Table\u00a013 \u2013 Services used for Parameter Access on PROFIBUS DP Table\u00a014 \u2013 Defined PAPs for Parameter Access <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Figure\u00a017 \u2013 Telegram sequence via MS1 AR or MS2 AR <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Table\u00a015 \u2013 State machine for DP-slave processing Table\u00a016 \u2013 MS1\/MS2 AR telegram frame, Write request <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Table\u00a017 \u2013 MS1\/MS2 AR telegram frame, Write response Table\u00a018 \u2013 MS1\/MS2 AR telegram frame, Read request Table\u00a019 \u2013 MS1\/MS2 AR telegram frame, Read response <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Table\u00a020 \u2013 Process data ASE telegram frame, Error response <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Table\u00a021 \u2013 Allocation of Error class and code for PROFIdrive Table\u00a022 \u2013 Data block lengths <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Table\u00a023 \u2013 Limits due to the Process data ASE data block length <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 4.7 P-Device configuration 4.7.1 P-Device configuration on PROFIBUS DP 4.7.2 Drive Unit configuration on PROFIBUS DP Table\u00a024 \u2013 GSD parameters for the MS1\/MS2 AR services <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Figure\u00a018 \u2013 Drive Unit Structure <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 4.7.3 Getting the Drive Object \u2013 ID (DO-ID) Figure\u00a019 \u2013 Configuration and communication channels for the Modular Drive Unit type at PROFIBUS DP <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Figure\u00a020 \u2013 Meaning of parameter PNU978 (list of all DO-IDs) for the DU at PROFIBUS\u00a0DP <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 4.8 Diagnosis 4.9 Clock Synchronous Operation 4.9.1 Sequence of an isochronous DP cycle Figure\u00a021 \u2013 Example of P978 for a complex Modular Drive Unit at PROFIBUS DP <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 4.9.2 Time settings Figure\u00a022 \u2013 Sequence of an isochronous DP cycle <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Figure\u00a023 \u2013 Time settings <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Figure\u00a024 \u2013 Example: Simplest DP cycle <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Figure\u00a025 \u2013 Example: Optimised DP cycle <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 4.9.3 Running-up, cyclic operation Figure\u00a026 \u2013 Example: Optimised DP cycle (TMAPC = 2 \u00d7 TDP) Table\u00a025 \u2013 DP services for running-up, cyclic operation <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | Figure\u00a027 \u2013 Running-up (sequence with respect to time) <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Figure\u00a028 \u2013 Phase 1: Slave parameterisation, configuration <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Figure\u00a029 \u2013 Phase 2: Synchronisation of the PLL to the Clock Global Control <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | Figure\u00a030 \u2013 Phase 3: Synchronisation of the slave application with the master’s Sign-Of-Life <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Figure\u00a031 \u2013 State diagram of Phases 2 and 3 of the run-up <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Figure\u00a032 \u2013 Phase 4: Synchronisation of the master application to the slave’s SignOfLife <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Figure\u00a033 \u2013 Example: Running-up to cyclic operation (Phase 1) (TMAPC\/TDP = 2\/1) <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Figure\u00a034 \u2013 Example: Running-up to cyclic operation (Phase 2) (TMAPC\/TDP = 2\/1) Figure\u00a035 \u2013 Example: Running-up to cyclic operation (Phase 3) (TMAPC\/TDP = 2\/1) <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | 4.9.4 Parameterisation, configuring (Set_Prm, GSD) Figure\u00a036 \u2013 Example: Running-up to cyclic operation (Phase 4) (TMAPC\/TDP = 2\/1) Figure\u00a037 \u2013 Example: Running-up to cyclic operation (Phase 5) (TMAPC\/TDP = 2\/1) <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Table\u00a026 \u2013 Parameters (Set_Prm, GSD) for “Clock Cycle Synchronous Drive Interface” <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | 4.9.5 Clock cycle generation (Global Control) and clock cycle save Table\u00a027 \u2013 Possible synchronisation type combinations <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Table\u00a028 \u2013 Conditions for Isochronous Mode <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Figure\u00a038 \u2013 PLL for clock regeneration in the slave Table\u00a029 \u2013 Input signals of the PLL <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table\u00a030 \u2013 Output signals of the PLL <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | 4.9.6 Monitoring mechanisms Figure\u00a039 \u2013 Run time compensation <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Figure\u00a040 \u2013 DP cycle violation <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | 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\u00a041 \u2013 Example: Clock failure (fault after 4 DP cycles) Table\u00a031 \u2013 Overview of the specific PROFIBUS DP parameters for \u201cCommunication system interfaces\u201d <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 4.11 Specified communication functions for the Application Classes Table\u00a032 \u2013 PROFIdrive specific parameter listed by number Table\u00a033 \u2013 Coding of the data rate in parameter 963 <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 5 Mapping to PROFINET IO 5.1 General 5.2 Mapping to PROFINET IO data types Table\u00a034 \u2013 Specified communication functions for the Application Classes <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 5.3 Base Model at PROFINET IO 5.3.1 Communication devices Table\u00a035 \u2013 Mapping of data types <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | 5.3.2 Communication relationship Figure\u00a042 \u2013 PROFINET IO Devices in a PROFIdrive drive system <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | 5.3.3 Communication network Figure\u00a043 \u2013 PROFIdrive Devices and their relationship for PROFINET IO <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | 5.3.4 Communication services Figure\u00a044 \u2013 General Communication Model for PROFIdrive at PROFINET IO <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | 5.3.5 P-Device communication model Figure\u00a045 \u2013 Synchronous communication for PROFIdrive at PROFINET IO Figure\u00a046 \u2013 Overview about the P-Device communication model on PROFINET IO <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Figure\u00a047 \u2013 Contents of IO AR and Supervisor AR <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | 5.3.6 Base Model State Machine Figure\u00a048 \u2013 M CR used for Cyclic Data Exchange between P-Devices <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | 5.3.7 Definition of the CO 5.4 Drive Model at PROFINET IO 5.4.1 P-Device Figure\u00a049 \u2013 Mapping of the Base Model State Machine at PROFINET IO <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | 5.4.2 Drive Unit 5.4.3 DO architecture Figure\u00a050 \u2013 PROFINET IO specific Logical P-Device model (multi axis drive) <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Figure\u00a051 \u2013 Representation of the PROFIdrive DO by PROFINET IO Submodules (CO) <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | 5.4.4 Definition of the Module Ident Number and API 5.4.5 Definition of the Submodule Ident Number Figure\u00a052 \u2013 Hierarchical model of the P-Device on PROFINET IO <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Table\u00a036 \u2013 Structure of the Submodule-ID Table\u00a037 \u2013 Definition of Submodule-Type Classes <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | 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\u00a053 \u2013 Modularity of the DO IO Data block (example) <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | 5.6.2 Base Mode Parameter Access Table\u00a038 \u2013 Definition of Parameter Access Modes (PAP) <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | 5.7 P-Device Configuration 5.7.1 P-Device Configuration on PROFINET IO Figure\u00a054 \u2013 Data flow for request and response for the Base Mode Parameter Access <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | 5.7.2 Drive Unit Configuration on PROFINET IO 5.7.3 Getting the Drive Object \u2013 ID (DO-ID) Figure\u00a055 \u2013 Configuration and communication channelsfor the Modular Drive Unit type at PROFINET IO <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | 5.8 Diagnosis 5.8.1 Use of PROFINET IO Diagnosis for PROFIdrive 5.8.2 Use of the Alarm ASE Figure\u00a056 \u2013 Meaning of parameter P978 “List of all DO-IDs” for the DU at PROFINET\u00a0IO <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | 5.8.3 Use of the ChannelDiagnosisData structure Table\u00a039 \u2013 Use of the AlarmNotification-PDU Table\u00a040 \u2013 Use of ChannelDiagnosisData <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | Figure\u00a057 \u2013 Generation of Diagnosis Data according to the fault classes mechanism <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | 5.8.4 Use of the ChannelErrorType 5.8.5 On demand access of Diagnosis Information Table\u00a041 \u2013 Use of ChannelErrorType Table\u00a042 \u2013 Use of the DiagnosisData <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | 5.9 Clock Synchronous Operation Figure\u00a058 \u2013 Sequence of an isochronous Data Cycle <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | 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\u00a043 \u2013 Overview of the specific PROFINET IO parameters for \u201cCommunication system interfaces\u201d <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | Table\u00a044 \u2013 PROFIdrive Specific Parameter listed by number <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | 5.11 Specified communication functions for the Application Classes 5.12 I&M data records Table\u00a045 \u2013 Specified communication functions for the Application Classes <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Adjustable speed electrical power drive systems – Generic interface and use of profiles for power drive systems. Mapping of profile type 3 to network technologies<\/b><\/p>\n |