BS EN 61800-7-302:2016
$167.15
Adjustable speed electrical power drive systems – Generic interface and use of profiles for power drive systems. Mapping of profile type 2 to network technologies
Published By | Publication Date | Number of Pages |
BSI | 2016 | 38 |
IEC 61800-7-302:2015 specifies the mapping of the profile type 2 (CIP MotionTM) specified in IEC 61800-7-202 onto different network technologies. This edition includes the following significant technical changes with respect to the previous edition: – update of patent information; – updates to the Connection Format and connection points; – support of an additional object.
PDF Catalog
PDF Pages | PDF Title |
---|---|
6 | English CONTENTS |
8 | FOREWORD |
10 | INTRODUCTION 0.1 General |
13 | 0.2 Patent declaration Figures Figure 1 – Structure of IEC 618007 |
15 | 1 Scope 2 Normative references 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions |
22 | 3.2 Abbreviated terms |
23 | 4 Principles for mapping CIP Motion™ 4.1 General principles for mapping CIP Motion™ Figure 2 – Overview of CIP-based networks |
24 | 4.2 Mapping CIP Motion™ 4.3 Data types |
25 | 4.4 I/O connection interface 4.4.1 General 4.4.2 I/O Connection Formats Figure 3 – Connection Header Figure 4 – Connection Format Tables Table 1 – Data types |
26 | 4.4.3 Fixed I/O Connection Format |
27 | 4.4.4 Variable I/O Connection Format Figure 5 – Fixed Controller to Device I/O Connection Format (fixed size = 16 bytes) Figure 6 – Fixed Device to Controller I/O Connection Format (fixed size = 16 bytes) |
28 | Figure 7 – Controller-to-Device I/O Connection Format (variable size) |
29 | Figure 8 – Device-to-Controller I/O Connection Format (variable size) |
30 | 5 Mapping to DeviceNet™ 5.1 Adaptation of the device model Figure 9 – Object Model for a CIP Motion device on DeviceNet |
31 | 5.2 Use of I/O data formats 6 Mapping to ControlNet™ 6.1 Adaptation of the device model Table 2 – Object classes for a CIP Motion device type on DeviceNet |
32 | Figure 10 – Object Model for a CIP Motion device on ControlNet Table 3 – Object classes for a CIP Motion device type on ControlNet |
33 | 6.2 Use of I/O data formats 7 Mapping to EtherNet/IP™ 7.1 Adaptation of the device model Figure 11 – Object Model for a CIP Motion device on EtherNet/IP |
34 | 7.2 Use of I/O data formats Table 4 – Object classes for a CIP Motion device type on EtherNet/IP |
35 | Bibliography |