IG profiles

Scope

The Interest Group (IG) profiles coordinates its Special Interest Groups (SIGs) and related Task Forces (TF). It approves Draft Standard (DS) documents developed by SIGs and TFs. The group is responsible for the CiA 4XX series comprising device, application, and interface profiles as well as mappings to Classic CANopen, CANopen FD, and J1939.

Chairman

Holger Zeltwanger

Group meetings

DateTime (Berlin, Germany)GroupLocation
2020-09-16 10:00 - 17:00 IG profiles Nuremberg, Germany

Sub-group meetings

DateTime (Berlin, Germany)GroupLocation
2020-02-20 09:00 - 11:00 IG profiles SIG drives and motion control e-meeting
2020-03-03 10:00 - 12:00 IG profiles SIG weighing devices and systems e-meeting
2020-03-25 15:00 - 17:00 IG profiles SIG contrast media injector e-meeting
2020-03-26 09:00 - 17:00 JSIG CiA/EnergyBus: EMS Tannheim, Österreich
2020-04-23 10:00 - 17:00 IG profiles SIG municipal vehicles Nuremberg, Germany
2020-04-28 08:30 - 18:00 IG profiles Plugfest lift Nuremberg, Germany
2020-04-29 08:00 - 12:00 IG profiles Plugfest lift Nuremberg, Germany
2020-04-29 13:00 - 17:00 IG profiles SIG lift control Nuremberg, Germany

Minutes

Title Date Status Size Published Action
IG profiles2019-01-22Minutes1.2 MiB2019-01-24Login
IG profiles2019-04-24Minutes1.5 MiB2019-04-29Login
IG profiles2019-09-04Minutes2.0 MiB2019-09-11Login
SIG drives and motion control2019-10-25Minutes447 KiB2019-10-29Login
SIG weighing devices2019-10-29Minutes131 KiB2019-10-30Login
SIG generic IO modules2019-11-05Minutes170 KiB2019-11-13Login
SIG encoder and inclinometer2019-09-18Minutes799 KiB2019-09-27Login

Specifications

Title Details
Status
Size
Published
Action
CiA 401 version 3.0.0CANopen device profile for generic I/O modules
DescriptionThis specification represents the CANopen device profile for generic digital and analogue input and output modules. Devices compliant to this specification use communication techniques, which conform to those described in the CANopen application layer and communication profile specification. In addition, programmable I/O devices may use communication techniques, which conform to those described in the CANopen additional application layer functions. In the appendices, some specific I/O devices are defined.
Keywordsn/a
public1.0 MiB2008-06-03Login
CiA 401-1 version 3.1.0CANopen Profile for I/O devices – Part 1: Generic I/O modules
DescriptionThis CANopen profile specifies generic CANopen digital and analog input and output devices. Devices compliant to this specifications use communication techniques, which are conform to those described in the CANopen application layer and communication profile specification. In addition, programmable I/O devices may use communication techniques, which conform to those described in the CANopen additional application layer functions. This device profile specification consists of several parts: Part 1: Generic I/O devices, Part 2: Joysticks. This part of the device profile specifies the CANopen interface for modules with generic analog and digital inputs and outputs. The first default TPDO and RPDO support up to 64 digital inputs, respectively up to 64 digital outputs both grouped byte-wise. The remaining default PDOs transmit or receive up to 12 analog inputs respectively up to 12 analog outputs both with a 16-bit resolution. All TPDOs are triggered by change-of-state. Therefore, default TPDOs containing analog inputs are disabled. Besides the default byte-wise access to digital I/Os, optional bit-, word-, and double-word access may be supported. Besides the default 16-bit resolution for the analog I/Os, optional 8-bit, 32-bit, floating-point and manufacturer-specific resolutions may be supported. Several parameters are specified to configure the input and output behavior (e.g. trigger conditions for inputs, output behavior in case of internal device failures.
Keywordsn/a
DSP0.9 MiB2013-02-12Login
CiA 401-2 version 3.1.0CANopen profile for I/O devices – Part 2: Joysticks
DescriptionThis CANopen profile specifies generic CANopen digital and analog input and output devices. Devices compliant to this specifications use communication techniques, which conform to those described in the CANopen application layer and communication profile specification. In addition, programmable I/O devices may use communication techniques, which conform to those described in the CANopen additional application layer functions. This profile consists of several parts: Part 1: Generic I/O devices, Part 2: Joysticks. This part of the profile specifies the CANopen interface for joysticks and similar devices, e.g. foot-pedals.
Keywordsn/a
DSP219 KiB2013-02-12Login
CiA 401-B1 version 0.0.3Functional behavior and parameters for generic I/O devices
Descriptionn/a
Keywordsn/a
WD1.2 MiB2019-11-12Login
CiA 401-C1 version 0.0.1CANopen mapping for generic I/O modules
Descriptionn/a
Keywordsn/a
WD570 KiB2019-11-12Login
CiA 401-F1 version 0.0.3CANopen FD mapping for generic I/O devices
Descriptionn/a
Keywordsn/a
WD469 KiB2019-11-12Login
CiA 402-6 version 1.0.0CANopen device profile for drives and motion control – Part 6: CANopen FD PDO mapping
DescriptionThis series of profile specifies the CANopen interface of power drive systems. It is suitable for drive and motion controllers. It specifies several operating modes for frequency inverters, servocontrollers, and stepper motors. The series of profile is split in several parts: Part 1: General definitions, Part 2: Operation modes and application data, Part 3: PDO mapping, Part 4: Safety functionality, Part 5: PDO mapping superset, Part 6: CANopen FD PDO mapping. This part specifies the CANopen FD mapping for frequency converters, servo drives and stepper motors as well as for multiple-axes systems.
Keywordsn/a
DSP554 KiB2016-10-10Login
CiA 402-1 version 4.0.0CANopen device profile for drives and motion control – Part 1: General definitions
DescriptionThis series of profile specifies the CANopen interface of power drive systems. It is suitable for drive and motion controllers. It specifies several operating modes for frequency inverters, servocontrollers, and stepper motors. The series of profile is split in several parts: Part 1: General definitions, Part 2: Operation modes and application data, Part 3: PDO mapping, Part 4: Safety functionality, Part 5: PDO mapping superset. Part 1 specifies the mapping of the CiA 402 profile onto the generic power drive system (PDS) interface as defined in IEC 61800-7-1.
Keywordsn/a
DSP184 KiB2016-03-01Login
CiA 402-3 version 4.0.0CANopen device profile for drives and motion control – Part 3: PDO mapping
DescriptionThis series of profile specifies the CANopen interface of power drive systems. It is suitable for drive and motion controllers. It specifies several operating modes for frequency inverters, servocontrollers, and stepper motors. The series of profile is split in several parts: Part 1: General definitions, Part 2: Operation modes and application data, Part 3: PDO mapping, Part 4: Safety functionality, Part 5: PDO mapping superset. Part 3 specifies the CANopen PDO mapping as defined in IEC 61800-7-301. In particular, the process data object (PDO) communication and mapping parameters are defined. In addition, this specificaton defines the PDO mapping attribute for all objects defined in the CiA 402 drive profile.
Keywordsn/a
DSP592 KiB2016-03-01Login
CiA 402-4 version 1.0.0CANopen device profile for drives and motion control – Part 4: Safety functionality
DescriptionThis series of profile specifies the CANopen interface of power drive systems. It is suitable for drive and motion controllers. It specifies several operating modes for frequency inverters, servocontrollers, and stepper motors. The series of profile is split in several parts: Part 1: General definitions, Part 2: Operation modes and application data, Part 3: PDO mapping, Part 4: Safety functionality, Part 5: PDO mapping superset. Part 2 and part 3 are substituted by the international standards IEC 61800-7-201 respectively IEC 61800-7-301. This part specifies the safety functionality for electrical drives and motion controllers compliant with the CiA 402 profile. It specifies the safety-related process data, the safety-related configuration parameters, and the safety-related diagnostic information as well as the SRDO communication and mapping parameters. Safety devices compliant with this part consume SRDOs containing commands from a control device and produce SRDOs containing status information to be received by the control device. Safety devices compliant with this document provide typically local safety functions as well as safety inputs and outputs. The safety outputs can be used to assign safety status information or can be set by the command information of the safety logic. The document is based on the ETG.6100.2 Generic Safety Drive Profile by the Ethercat Technology Group (ETG), and it specifies the mapping to CANopen. NOTE: The naming and the assigned indices and sub-indices of the parameters are far as possible the same as in the ETG documents. But some ETG parameters are represented in CANopen by two parameters, consequently two names are used.
Keywordsn/a
DSP2.4 MiB2015-12-02Login
CiA 402-5 version 1.0.0CANopen device profile for drives and motion control – Part 5: PDO mapping superset
DescriptionThis series of profile specifies the CANopen interface of power drive systems. It is suitable for drive and motion controllers. It specifies several operating modes for frequency inverters, servocontrollers, and stepper motors. The series of profile is split in several parts: Part 1: General definitions, (Part 2: Operation modes and application data), (Part 3: PDO mapping), Part 4: Safety functionality, Part 5: PDO mapping superset. Part 2 and part 3 are substituted by the international standards IEC 61800-7-201 respectively IEC 61800-7-301. This part specifies the set of PDOs for CiA 402 compliant CANopen devices, which can control asynchronous and synchronous motors.
Keywordsn/a
DSP174 KiB2014-01-31Login
CiA 402-2 version 4.1.0CANopen device profile for drives and motion control – Part 2: Operation modes and application data
DescriptionThis series of profile specifies the CANopen interface of power drive systems. It is suitable for drive and motion controllers. It specifies several operating modes for frequency inverters, servocontrollers, and stepper motors. The series of profile is split in several parts: Part 1: General definitions, Part 2: Operation modes and application data, Part 3: PDO mapping, Part 4: Safety functionality, Part 5: PDO mapping superset. Part 2 specifies the basic drive and additional application functional elements as definedThis series of profile specifies the CANopen interface of power drive systems. It is suitable for drive and motion controllers. It specifies several operating modes for frequency inverters, servo-controllers, and stepper motors. The series of profile is split in several parts: Part 1: General definitions, Part 2: Operation modes and application data, Part 3: PDO mapping, Part 4: Safety functionality, Part 5: PDO mapping superset, Part 6: CANopen FD PDO mapping. Part 2 specifies the basic drive and additional application functional elements as defined in IEC 61800-7-201. This includes the specification of drive operation modes and application data for such power drive systems as frequency converters, servo controllers, or stepper motor controllers. It includes the definition of real-time control objects as well as of configuration, adjustment, identification and network management objects. There is also defined the PDS finite state automaton (FSA), which may be controlled externally by a control device communicating via a communication system to the drive device. in IEC 61800-7-201. This includes the specification of drive operation modes and application data for such power drive systems as frequency converters, servo controllers, or stepper motor controllers. It includes the definition of real-time control objects as well as of configuration, adjustment, identification and network management objects. There is also defined the PDS finite state automaton (FSA), which may be controlled externally by a control device communicating via a communication system to the drive device.
Keywordsn/a
DSP3.7 MiB2016-10-10Login
CiA 402-1 version 4.0.1CANopen drives and motion control device profile - Part 1: General definitions
Descriptionn/a
Keywordsn/a
WD282 KiB2019-08-19Login
CiA 402-2 version 4.1.1.CANopen drives and motion control device profile - Part 2: Operation modes and application data
Descriptionn/a
Keywordsn/a
WD4.6 MiB2019-08-19Login
CiA 402-3 version 4.0.1.CANopen drives and motion control device profile - Part 3: PDO mapping
Descriptionn/a
Keywordsn/a
WD1.3 MiB2019-08-19Login
CiA 402-2 version 4.1.3CANopen drives and motion control device profile - Part 2: Operation modes and application data
Descriptionn/a
Keywordsn/a
WD4.7 MiB2020-02-18Login
CiA 404-1 version 2.1.0CANopen device profile for measuring devices and closed-loop controllers – Part 1: Generic objects and generic PDO mapping
DescriptionThis document specifies the device profile for measuring devices and for universal controller devices for measuring or controlling of physical quantities such as temperature or pressure. The CANopen device profile for measuring devices and closed-loop controllers consists of two parts: Part 1 defines the generic objects and the generic PDO mapping. Part 2 defines the EUROMAP specific parameters. This part specifies the parameter for the digital input and output blocks resp. the analog input and output blocks. Additionally, it specifies the alarm and control as well as the device function block.
Keywordsn/a
DSP1.3 MiB2016-07-19Login
CiA 404-2 version 2.0.0CANopen device profile for measuring devices and closed-loop controllers – Part 2: EUROMAP implementation
DescriptionThis specification represents the device profile for measuring devices and for universal controller devices for measuring or controlling physical quantities like temperature or pressure. These devices use communication techniques which are conform to those described in /CiA301/. The CANopen device profile for measuring devices and closed-loop controllers consists of several parts. This part specifies the additional objects needed for EUROMAP 75 measuring amplifiers parameters and EUROMAP 66 heating/cooling device parameters.
Keywordsn/a
DSP175 KiB2013-08-01Login
CiA 404 version 1.2.0CANopen device profile for measuring devices and closed-loop controllers
DescriptionThis document represents the device profile for measuring devices and for universal controller devices for measuring or controlling physical quantities like temperature or pressure. These devices use communication techniques which are conform to those described in /2/. This document should be consulted in parallel to this profile.
Keywordsn/a
public1.7 MiB2002-05-15Login
CiA 406 version 3.2.0CANopen device profile for encoders
DescriptionThis document represents the CANopen device profile for incremental and absolute, linear and rotary encoders. Besides position, velocity, acceleration, and jerk output possibility complete cam functionality is covered. In addition, it is possible to handle multi-sensors through one CANopen device. All the above mentioned devices use communication techniques, which conform to those described in the CANopen application layer and communication profile specification /CiA301/. This document should be consulted in parallel to this profile.
Keywordsn/a
public533 KiB2006-12-18Login
CiA 406 version 4.0.5CANopen device profile for encoders
Descriptionn/a
Keywordsn/a
WD2.0 MiB2018-09-20Login
CiA 406 version 4.1.0CANopen device profile for encoders
DescriptionThis document specifies the communication and application parameters for different types of linear and rotary encoders such as incremental and absolute, normal, and high resolution, single and multi-sensor (linear only) encoders. The document provides also operating principles of the encoders and specifies encoder output process values such as position, speed, acceleration and jerk. The document specifies also encoder CAM parameters. This document also specifies CANopen Safety parameters such as Safety position and Safety speed for encoders with CANopen Safety functionality (see EN 50325-5).
Keywordsn/a
DSP1.6 MiB2019-06-01Login
CiA 406-B version 0.0.1Functional behavior and parameters for encoders
Descriptionn/a
Keywordsn/a
WD1.6 MiB2020-01-17Login
CiA 406-C version 0.0.1CANopen mapping for encoders
Descriptionn/a
Keywordsn/a
WD633 KiB2020-01-17Login
CiA 406-J version 0.0.0.1CiA device profile for encoders - J1939 mapping
Descriptionn/a
Keywordsn/a
WDP204 KiB2019-09-01Login
CiA 408 version 2.1.0CANopen device profile for fluid power technology proportional valves and hydrostatic transmissions
DescriptionThis CiA device profile describes the functionality of interconnectable proportional valves, hydrostatic pumps and hydrostatic transmissions. The specification is based on the profile “Fluid Power Technology”, version 1.6.3 designed by Verband Deutscher Maschinen- und Anlagenbau e.V. Frankfurt/Main, Germany (VDMA). The device profile specifies CANopen interface for hydraulic proportional valves, hydrostatic pumps and hydrostatic transmissions. This profile may as well be applied on pneumatic devices.
Keywordsn/a
DSP8.7 MiB2017-01-23Login
CiA 408 version 1.5.2CANopen device profile for fluid power technology proportional valves and hydrostatic transmissions
DescriptionThis profile describes the functionality of interconnectable proportional valves, hydrostatic pumps and hydrostatic transmissions. The document is based on the profile “Fluid Power Technology”, version 1.5 released by VDMA Verband Deutscher Maschinen- und Anlagenbau e.V. Frankfurt/Main, Germany/VDMAPROP/. The device profile has been defined for hydraulic proportional valves, hydrostatic pumps and hydrostatic transmissions. It can as well be applied on pneumatic devices.
Keywordsn/a
public2.8 MiB2005-01-01Login
CiA 410 version 1.3.0CANopen device profile for inclinometer
DescriptionThis specification represents the CANopen device profile for one- and two-axis inclinometers.
Keywordsn/a
public194 KiB2010-02-23Login
CiA 410 version 2.0.0CANopen device profile for inclinometer
DescriptionThis profile specifies the CANopen interface for one- and two-axis inclinometers. This sensor interface provides optionally also temperature, speed, acceleration, and jerk process values. The specification includes optional CANopen safety-communication interface compliant to safety integrity levels (SIL) as defined in IEC 61508.
Keywordsn/a
DSP0.9 MiB2014-03-25Login
CiA 412-1 version 1.0.0CANopen profiles for medical devices - Part 1: General definitions
DescriptionThe CANopen profiles for medical devices includes several parts: Part 1 describes general definitions. Part 2 defines the profile for automatic X-ray collimators. Part 3 defines the profile for X-ray generators. Part 4 defines the profile for patient tables. Part 5 defines the profile for X-ray stands. Devices compliant to these profiles use communication techniques, which conforms to those described in the CANopen communication profile (CiA Draft Standard DS-301, /2/). In addition, medical devices and sub-systems may use communication techniques, which conform to those described in the framework for programmable CANopen Devices (CiA Draft Standard Proposal DSP- 302). These specifications should be consulted in parallel to these device profile specifications.
Keywordsn/a
public159 KiB2005-12-31Login
CiA 412-2 version 1.0.0CANopen profiles for medical devices - Part 2: Automatic X-ray collimator
DescriptionThis document represents the CANopen device profile for generic X-ray collimators, and as such describes the generic subset of collimator functionality. A prerequisite for the conformity to this CANopen device profile is conformity with the CANopen communication profile (CiA Draft Standard DS 301). Additionally, in the case that the module is programmable it must conform to the Framework for programmable CANopen devices (CiA Draft Standard Proposal DSP 302). These specifications should be consulted in parallel to this device profile specification.
Keywordsn/a
public658 KiB2005-12-31Login
CiA 412-6 version 1.1.0CANopen profiles for medical devices - Part 6: Dose measurement system
DescriptionThis specification defines the CANopen device profile for dose measurement systems. A prerequisite for the conformity to this CANopen device profile is conformity with the CANopen communication profile. Additionally, in the case that the module is programmable conformance to the framework for programmable CANopen devices is required. It is recommended to consulted these specifications in parallel to this device profile specification.
Keywordsn/a
public0.9 MiB2008-08-27Login
CiA 413-1 version 3.0.0CANopen device profile for truck gateways – Part 1: General definitions
DescriptionThis set of profile specifications describes CANopen gateways to CAN-based in-vehicle networks using the SAE J1939-71 application profile, ISO 11992-2, -3, and -4 truck/trailer networks or other J1939-based networks, e.g. ISO 11783-based (ISOBUS) networks, NMEA2000 networks, or RV-CAN network systems. The CANopen device profile for truck gateways consists of several parts: Part 1 describes general definitions. Part 2 defines the application objects for braking and running gear. Part 3 defines the application objects for equipment other than brakes and running gear. Part 5 defines the application objects for superstructures. Part 6 defines the interface profile for J1939-to-CANopen gateways. Part 8 defines the framework for HMI control. This part specifies the physical layer including connectors, and some general communication parameters. There are no PDOs pre-defined.
Keywordsn/a
DSP138 KiB2011-11-24Login
CiA 413-2 version 3.0.0CANopen device profile for truck gateways – Part 2: Brake and running gear devices
DescriptionThis set of profile specifications describes CANopen gateways to CAN-based in-vehicle networks using the SAE J1939-71 application profile, ISO 11992-2, -3, and -4 truck/trailer networks or other J1939-based networks, e.g. ISO 11783-based (ISOBUS) networks, or NMEA2000 networks, or RV-CAN network systems. The CANopen device profile for truck gateways consists of several parts: Part 1 describes general definitions. Part 2 defines the application objects for braking and running gear. Part 3 defines the application objects for equipment other than brakes and running gear. Part 5 defines the application objects for superstructures. Part 6 defines the interface profile for J1939-to-CANopen gateways. Part 8 defines the framework for HMI control. This part specifies the application objects for brake and running gear equipment. These objects are equivalent to signals and parameters in /ISO11992-2/. This allows a directly forwarding of messages received from the in-vehicle network and a directly forwarding of CANopen application objects to the in-vehicle network.
Keywordsn/a
DSP857 KiB2011-11-24Login
CiA 413-3 version 3.0.0CANopen device profile for truck gateways – Part 3: Other than brake and running gear devices
DescriptionThis set of profile specifications describes CANopen gateways to CAN-based in-vehicle networks using the SAE J1939-71 application profile, ISO 11992-2, -3, and -4 truck/trailer networks or other J1939-based networks, e.g. ISO 11783-based (ISOBUS) networks, or NMEA2000 networks, or RV-CAN network systems. The CANopen device profile for truck gateways consists of several parts: Part 1 describes general definitions. Part 2 defines the application objects for braking and running gear. Part 3 defines the application objects for equipment other than brakes and running gear. Part 5 defines the application objects for superstructures. Part 6 defines the interface profile for J1939-to-CANopen gateways. Part 8 defines the framework for HMI control. This part specifies the application objects for other than brake and running gear equipment. These objects are equivalent to signals and parameters in /ISO11992-3/. This allows a directly forwarding of messages received from the in-vehicle network and a directly forwarding of CANopen application objects to the in-vehicle network.
Keywordsn/a
DSP1.2 MiB2011-11-24Login
CiA 413-5 version 1.0.0CANopen device profile for truck gateways – Part 5: Application objects for superstructure
DescriptionPart 5 of CANopen device profile for truck gateways defines the application objects for superstructure. The normative references, definitions, acronyms, and abbreviations given in part 1 applies to this part, too.
Keywordsn/a
DSP272 KiB2003-12-31Login
CiA 413-6 version 1.0.0CANopen device profile for truck gateways – Part 6: Framework for J1939-based networks
DescriptionPart 6 of the CANopen device profile for truck gateways defines a framework for J1939-based networks. The normative references, definitions, acronyms, and abbreviations given in part 1 applies to this part, too. The object value definitions shall be as given in SAE J1939-71. The gateway is usable in static systems, where ECU address changes do not apply. Using other protocols based on J1939, such as ISO 11783 or NMEA 2000 will require some extensions, that may be subject to later versions.
Keywordsn/a
DSP105 KiB2003-12-31Login
CiA 413-8 version 1.0.0CANopen device profile for truck gateways – Part 8: Framework for HMI control
DescriptionThis set of profile specifications describes CANopen gateways to CAN-based in-vehicle networks using the SAE J1939-71 application profile, ISO 11992-2, -3, and -4 truck/trailer networks or other J1939-based networks, e.g. ISO 11783-based (ISOBUS) networks, NMEA2000 networks, or RV-CAN network systems. This part of the set of profile specification specifies a generic I/O functionality that enables usage of the truck HMI device.
Keywordsn/a
DSP167 KiB2011-11-24Login
CiA 414-1 version 1.1.0CANopen device profiles for weaving machines - Part 1: General definitions
DescriptionThe device profile defines the CANopen interfaces for weaving machines. The specification comprises the following two parts: Part 1 : General definitions, Part 2 : Feeders. Part 1 defines the operating principles for the feeder sub-systems, the error handling and the general communication parameters.
Keywordsn/a
public92 KiB2007-06-18Login
CiA 414-2 version 1.1.0CANopen device profiles for weaving machines - Part 2: Feeders
DescriptionPart 2 of the CANopen device profile for weaving machines specifies the CANopen interface for feeders. This device profile for feeders covers ‘pre-measuring feeders’ as well as ‘weft feeders’.
Keywordsn/a
public243 KiB2007-06-18Login
CiA 415 version 2.2.0CANopen application profile for sensor systems – In road construction and earth moving machines
DescriptionThe CANopen sensor system application profile for road construction and earth moving machines specifies the communication interface for sensors as well as the sensor control unit. The profile is suitable for a broad range of machine types (e.g. paver, compactor, grader, dozer, mill, heater and truck). NOTE: The first version of this profile has been jointly developed with the OSYRIS (Open System for Road Information Support) consortium (www.osyris.org) and the European Asphalt Pavement Association (EAPA).
Keywordsn/a
DSP788 KiB2009-04-22Login
CiA 416-1 version 2.0.0CANopen application profile for building door control – Part 1: General definitions, start-up procedures and system security
DescriptionThe CANopen application profile for building door control consists of several parts: Part 1: General definitions, start-up procedures and system security, Part 2: Virtual devices overview, Part 3: Pre-defined communication objects and application object specification. These specifications represent the CANopen application profile for building door control. It describes the interaction of e.g. door locking status, key cylinder, handle, alarms, system parameters, keypads and many more. Each of those properties is realized as a single virtual device.
Keywordsn/a
DSP536 KiB2007-08-28Login
CiA 416-2 version 2.0.0CANopen application profile for building door control – Part 2: Virtual devices overview
DescriptionThis part of the application profile gives an overview of the virtual devices.
Keywordsn/a
DSP292 KiB2007-08-28Login
CiA 416-3 version 2.0.0CANopen application profile for building door control – Part 3: Pre-defined communication objects and application object specification
DescriptionThis part of the application profile pre-defines the application objects of the physical and virtual devices in detail.
Keywordsn/a
DSP1.5 MiB2007-08-28Login
CiA 417-1 version 2.0.0CANopen application profile for lift control systems – Part 1: General definitions
DescriptionThis set of CANopen application profile specifications describes the CANopen Lift control network system. It specifies the CANopen communication interfaces and the application functionality of several functional elements (virtual devices). This application profile specification consists of several parts. Besides some general definitions such as general virtual device descriptions, this part specifies the CAN physical layer as well as the error handling. Additionally some network architecture examples are given.
Keywordsn/a
public210 KiB2011-02-02Login
CiA 417-2 version 2.0.0CANopen application profile for lift control systems – Part 2: Virtual device definitions
DescriptionThis set of CANopen application profile specifications describes the CANopen Lift control network system. It specifies the CANopen communication interfaces and the application functionality of several functional elements (virtual devices). This application profile specification consists of several parts. This part specifies for a single lift application (lift 1) the general communication parameter. It specifies also for each virtual device the supported application objects including the category, access, and default value attributes. It describes the supported Process Data Objects (PDO). In addition, the PDOs for the other lift application 2 to 8 are assigned correspondingly.
Keywordsn/a
public340 KiB2011-02-02Login
CiA 417-3 version 2.0.0CANopen application profile for lift control systems – Part 3-1: Pre-defined PDOs for lift application 1
DescriptionThis set of CANopen application profile specifications describes the CANopen Lift control network system. It specifies the CANopen communication interfaces and the application functionality of several functional elements (virtual devices). This application profile specification consists of several parts. This part of the application profile specifies pre-definitions for communication objects. This sub-part specifies in detail the communication and mapping behavior of the PDOs for the lift 1 application.
Keywordsn/a
public818 KiB2011-02-02Login
CiA 417-4 version 2.0.0CANopen application profile for lift control systems – Part 4: Detailed application object specification
DescriptionThis set of CANopen application profile specifications describes the CANopen Lift control network system. It specifies the CANopen communication interfaces and the application functionality of several functional elements (virtual devices). This application profile specification consists of several parts. This part specifies in detail the used process data, configuration parameter, and diagnostic information represented in the object dictionary for the lift 1 application.
Keywordsn/a
public839 KiB2011-02-02Login
CiA 417-3-1 version 2.1.7CANopen application profile for lift control systems – Part 3-1: Pre-defined PDOs for lift application 1
Descriptionn/a
Keywordsn/a
WD1.2 MiB2018-09-20Login
CiA 417-1 version 2.3.0CANopen application profile for lift control systems – Part 1: General definitions
DescriptionThis set of CANopen application profile specifications specifies the CANopen Lift control network. It consists of several parts: Part 1 provides general definitions, Part 2 specifies the functionality of the virtual devices, Part 3 specifies the pre-defined PDOs, Part 4 specifies the application objects. This part specifies the general lift control network architecture and provides description and block diagrams for single and multi-shaft CANopen lift control network structures. It provides description of lift component functions in form of virtual devices and their functions in the lift control network. It specifies CANopen physical layer and node-ID assignment in single or multi-shaft control network. Furthermore, it specifies bootloader mode handling for firmware upload and application programs. Additionally, it specifies also network wide error handling, power management handling, power consumption measurements, and character encoding for VT-52 terminals.
Keywordsn/a
DSP639 KiB2018-12-10Login
CiA 417-2 version 2.3.0CANopen application profile for lift control systems – Part 2: Virtual device definitions
DescriptionThis set of CANopen application profile specifications specifies the CANopen Lift control network. It consists of several parts: Part 1 provides general definitions, Part 2 specifies the functionality of the virtual devices, Part 3 specifies the pre-defined PDOs, Part 4 specifies the application objects. This part specifies the general communication parameters, list of application parameters, including the category, access, and default value attributes, assigned to each virtual device in a single lift application as well as list of PDOs assigned to each virtual device in a lift application 1 to 8.
Keywordsn/a
DSP1.3 MiB2018-12-10Login
CiA 417-3-1 version 2.2.0CANopen application profile for lift control systems – Part 3-1: Pre-defined PDOs for lift application 1
DescriptionThis set of CANopen application profile specifications specifies the CANopen Lift control network. It consists of several parts: Part 1 provides general definitions, Part 2 specifies the functionality of the virtual devices, Part 3 specifies the pre-defined PDOs, Part 4 specifies the application objects. This part of the application profile specifies in detail the communication and mapping behavior of the PDOs for the lift 1 application. Additionally, the COB-ID assignment is specified for PDOs for the lift application 1 to 8.
Keywordsn/a
DSP1.8 MiB2018-12-02Login
CiA 417-4 version 2.3.0CANopen application profile for lift control systems – Part 4: Detailed application object specification
DescriptionThis set of CANopen application profile specifications specifies the CANopen Lift control network. It consists of several parts: Part 1 provides general definitions, Part 2 specifies the functionality of the virtual devices, Part 3 specifies the pre-defined PDOs, Part 4 specifies the application objects. This part specifies in detail the used process data, configuration parameters, and diagnostic information represented in the object dictionary for the lift 1 application.
Keywordsn/a
DSP4.0 MiB2018-11-22Login
CiA 417-1 version 2.3.1CANopen application profile for lift control systems – Part 1: General definitions
Descriptionn/a
Keywordsn/a
WD466 KiB2020-02-05Login
CiA 417-2 version 2.3.1CANopen application profile for lift control systems – Part 2: Virtual device definitions
Descriptionn/a
Keywordsn/a
WD702 KiB2020-02-05Login
CiA 417-4 version 2.3.1CANopen application profile for lift control systems – Part 4: Detailed application object specification
Descriptionn/a
Keywordsn/a
WD2.4 MiB2020-02-05Login
CiA 418 version 1.2.0CANopen device profile for battery modules
DescriptionThis device profile specifies a recommended practice for the communication link between a battery module and a battery charger. The required data messages are intended to be sufficient to allow a battery charge to be carried out. Optional data is a selection of data commonly used in the industry to provide enhanced features. Battery modules compliant to this standard shall use communication techniques, which conforms to those described in the CANopen application layer and communication profile.
Keywordsn/a
public289 KiB2012-04-27Login
CiA 419 version 1.2.0CANopen device profile for battery chargers
DescriptionThis device profile specifies the battery charger communication and application objects in order to obtain sufficient information from the battery module to allow a charge to be carried out. Optional data is a selection of data commonly used in the industry to provide enhanced features. Chargers compliant to this standard shall use communication techniques, which conforms to those described in the CANopen application layer and communication profile.
Keywordsn/a
public197 KiB2012-04-27Login
CiA 420-1 version 3.2.0CANopen profiles for extruder downstream devices – Part 1: General definitions
DescriptionThe CANopen application profile for extruder downstream devices includes several parts: Part 1 specifies general definitions, Part 2 specifies the device profile for the puller downstream device, Part 3 specifies the device profile for the corrugator downstream device, Part 4 specifies the device profile for the saw downstream device, Part 5 specifies the device profile for the co-extruder device, Part 6 specifies the device profile for the calibration-table downstream device. NOTE: All parts of this specification have been developed jointly with the European Committee of Machinery Manufacturers for the Plastics and Rubber Industries (Euromap) and is documented there as Euromap 27. This part specifies the physical layer and the common CANopen functions and common
Keywordsn/a
public525 KiB2015-05-07Login
CiA 420-2 version 3.1.0CANopen profiles for extruder downstream devices – Part 2: Puller
DescriptionThe CANopen application profile for extruder downstream devices includes several parts. NOTE. All parts of this specification have been developed jointly with the European Committee of Machinery Manufacturers for the Plastics and Rubber Industries (Euromap) and is documented there as Euromap 27. This part specifies the CANopen interface for the puller downstream device.
Keywordsn/a
public187 KiB2015-05-07Login
CiA 420-3 version 3.1.0CANopen profiles for extruder downstream devices – Part 3: Corrugator
DescriptionThe CANopen application profile for extruder downstream devices include several parts: Part 1 specifies general definitions, Part 2 specifies the device profile for the puller downstream device, Part 3 specifies the device profile for the corrugator downstream device, Part 4 specifies the device profile for the saw downstream device, Part 5 specifies the device profile for the co-extruder device, Part 6 specifies the device profile for the calibration-table downstream device. NOTE: All parts of this specification have been developed jointly with the European Committee of Machinery Manufacturers for the Plastics and Rubber Industries (Euromap) and is documented there as Euromap 27. This part specifies the CANopen interface for the corrugator downstream device.
Keywordsn/a
public175 KiB2015-05-07Login
CiA 420-4 version 3.1.0CANopen profiles for extruder downstream devices – Part 4: Saw
DescriptionThe CANopen application profile for extruder downstream devices includes several parts: Part 1 specifies general definitions, Part 2 specifies the device profile for the puller downstream device, Part 3 specifies the device profile for the corrugator downstream device, Part 4 specifies the device profile for the saw downstream device, Part 5 specifies the device profile for the co-extruder device, Part 6 specifies the device profile for the calibration-table downstream device. NOTE: All parts of this specification have been developed jointly with the European Committee of Machinery Manufacturers for the Plastics and Rubber Industries (Euromap) and is documented there as Euromap 27. This part specifies the CANopen interface for the saw downstream device.
Keywordsn/a
public179 KiB2015-05-07Login
CiA 420-5 version 2.1.0CANopen profiles for extruder downstream devices – Part 5: Simple and advanced co-extruder
DescriptionThe CANopen application profile for extruder downstream devices includes several parts: Part 1 specifies general definitions, Part 2 specifies the device profile for the puller downstream device, Part 3 specifies the device profile for the corrugator downstream device, Part 4 specifies the device profile for the saw downstream device, Part 5 specifies the device profile for the co-extruder device, Part 6 specifies the device profile for the calibration-table downstream device. NOTE: All parts of this specification have been developed jointly with the European Committee of Machinery Manufacturers for the Plastics and Rubber Industries (Euromap) and is documented there as Euromap 27. This part specifies the CANopen interface for simple and advanced co-extruder.
Keywordsn/a
public197 KiB2015-05-07Login
CiA 420-6 version 1.1.0CANopen profiles for extruder downstream devices – Part 6: Calibration-table
DescriptionThe CANopen application profile for extruder downstream devices include several parts: Part 1 specifies general definitions, Part 2 specifies the device profile for the puller downstream device, Part 3 specifies the device profile for the corrugator downstream device, Part 4 specifies the device profile for the saw downstream device, Part 5 specifies the device profile for the co-extruder device, Part 6 specifies the device profile for the calibration-table downstream device. NOTE_ All parts of this specification have been developed jointly with the European Committee of Machinery Manufacturers for the Plastics and Rubber Industries (Euromap) and is documented there as Euromap 27. This part specifies the CANopen interface for calibration-tables.
Keywordsn/a
public212 KiB2015-05-07Login
CiA 421-1 version 1.0.0CANopen application profile for train vehicle control networks – Part 1: General definitions
DescriptionThis application profile defines the communication between virtual devices within locomotives, power cars as well as coaches. It is intended to use the application profile for urban and regional rail vehicle transportation system as well as long-distance rail vehicle transportation systems including high-speed trains. But it is not limited to these railway applications, e.g. it is also used in cargo train locomotives and cargo train wagons as well as other railway transportation systems, such as commuter trains, subway trains, etc.
Keywordsn/a
DSP198 KiB2006-08-18Login
CiA 421-4 version 1.0.0CANopen application profile for train vehicle control networks – Part 4: Auxillary operating system
DescriptionThis part of the CANopen application profile for train control networks describes the CANopen interface of the virtual rail vehicle auxiliary operating system.
Keywordsn/a
DSP203 KiB2006-08-18Login
CiA 421-5 version 1.0.0CANopen application profile for train vehicle control networks – Part 5: Power (drive) system
DescriptionThis part of the CANopen application profile describes the CANopen interface of the virtual power drive system to the rail vehicle in-vehicle network.
Keywordsn/a
DSP1.2 MiB2006-08-18Login
CiA 421-9 version 1.0.0CANopen application profile for train vehicle control networks – Part 9: Vehicle linkage device
DescriptionThis part of the CANopen application profile for rail vehicles describes the CANopen interface of the vehicle linkage device. Via this interface all required data is exchanged that is relevant to control full automatic couplings. Full automatic couplings handle all connections between the rail vehicles such as e.g. electrically or electrical automatically, without human interaction.
Keywordsn/a
DSP139 KiB2008-04-17Login
CiA 421-10 version 1.0.0CANopen application profile for train vehicle control networks - Part 10: Exterior lighting system
DescriptionThis part of the CANopen application profile for rail vehicles describes the CANopen interface of the virtual exterior lighting system.
Keywordsn/a
DSP171 KiB2006-08-18Login
CiA 421-11 version 1.0.0CANopen application profile for train vehicle control networks – Part 11: Interior lighting system
DescriptionThis part of the CANopen application profile for rail vehicles describes the CANopen interface of the virtual interior lighting system.
Keywordsn/a
DSP135 KiB2006-08-18Login
CiA 421-12 version 1.0.0CANopen application profile for train vehicle control networks – Part 12: Door control system
DescriptionThis part of the CANopen application profile for rail vehicles describes the CANopen interface of the virtual door control system.
Keywordsn/a
DSP217 KiB2006-08-18Login
CiA 421 version 1.0.3CANopen Application profile for train vehicle control networks - Part 1: General definitions
Descriptionn/a
Keywordsn/a
WD690 KiB2008-01-29Login
CiA 422-3-3 version 2.0.4CANopen application profile for municipal vehicles – Part 3-3: Pre-defined SDOs
Descriptionn/a
Keywordsn/a
WD513 KiB2018-01-05Login
CiA 422-1 version 2.0.6CANopen application profile for municipal vehicles – Part 1: General definitions
Descriptionn/a
Keywordsn/a
WD774 KiB2018-02-23Login
CiA 422-2 version 2.0.5CANopen application profile for municipal vehicles – Part 2: Virtual device functionality
Descriptionn/a
Keywordsn/a
WD570 KiB2018-02-23Login
CiA 422-3-1 version 2.0.5CANopen application profile for municipal vehicles - Part 3-1: Pre-defined TPDOs
Descriptionn/a
Keywordsn/a
WD4.3 MiB2018-02-23Login
CiA 422-3-2 version 2.0.5CANopen application profile for municipal vehicles – Part 3-2: Pre-defined RPDOs
Descriptionn/a
Keywordsn/a
WD4.0 MiB2018-02-23Login
CiA 422-4 version 2.0.6CANopen application profile for municipal vehicles – Part 4: Application objects
Descriptionn/a
Keywordsn/a
WD3.8 MiB2018-02-23Login
CiA 422-1 version 2.1.0CANopen application profile for municipal vehicles – Part 1: General definitions
DescriptionThis set of CANopen application profile specifications describes the CleANopen embedded body control network of municipal vehicles, e.g. refuse collecting trucks. It specifies the CANopen communication interfaces and the application functionality of several functional elements (virtual devices). It does not specify CANopen devices. With special regard to functional safety, any device is responsible for a safe operation, by itself. Any measure that increases the probability for safe operation and utilizes the CAN communication is just on top. Therefore these measures are not safety-relevant in terms of functional safety. The CleANopen application profile specifications consists of several parts: Part 1 provides the general definitions, Part 2 specifies the functionality of the virtual devices, Part 3 specifies the pre-defined PDOs and SDOs, Part 4 specifies the application objects. This part provides some general definitions of CleANopen and specifies the CAN physical layer as well as the error handling.
Keywordsn/a
DSP778 KiB2018-12-20Login
CiA 422-2 version 2.1.0CANopen application profile for municipal vehicles – Part 2: Virtual device functionality
DescriptionThis set of CANopen application profile specifications describes the CleANopen embedded body control network of municipal vehicles, e.g. refuse collecting trucks. It specifies the CANopen communication interfaces and the application functionality of several functional elements (virtual devices). It does not specify CANopen devices. The CleANopen application profile specifications consists of several parts: Part 1 provides the general definitions, Part 2 specifies the functionality of the virtual devices, Part 3 specifies the pre-defined PDOs and SDOs, Part 4 specifies the application objects. This part specifies the general communication parameter. It specifies for each virtual device the supported application objects including the category, access, and default value attributes. It describes the supported Process Data Objects (PDO) and additional Service Data Objects (SDO).
Keywordsn/a
DSP0.9 MiB2018-12-20Login
CiA 422-3-1 version 2.1.0CANopen application profile for municipal vehicles – Part 3-1: Pre-defined TPDOs
DescriptionThis set of CANopen application profile specifications describes the CleANopen embedded body control network of municipal vehicles, e.g. refuse collecting trucks. It specifies the CANopen communication interfaces and the application functionality of several functional elements (virtual devices). It does not specify CANopen devices. The CleANopen application profile specifications consists of several parts: Part 1 provides the general definitions, Part 2 specifies the functionality of the virtual devices, Part 3 specifies the pre-defined PDOs and SDOs, Part 4 specifies the application objects. This sub-part of part 3 specifies the communication and mapping parameter sets of the pre-defined TPDOs.
Keywordsn/a
DSP5.9 MiB2018-12-20Login
CiA 422-3-2 version 2.1.0CANopen application profile for municipal vehicles – Part 3-2: Pre-defined RPDOs
DescriptionThis set of CANopen application profile specifications describes the CleANopen embedded body control network of municipal vehicles, e.g. refuse collecting trucks. It specifies the CANopen communication interfaces and the application functionality of several functional elements (virtual devices). It does not specify CANopen devices. The CleANopen application profile specifications consists of several parts: Part 1 provides the general definitions, Part 2 specifies the functionality of the virtual devices, Part 3 specifies the pre-defined PDOs and SDOs, Part 4 specifies the application objects. This sub-part of part 3 specifies the communication and mapping parameter sets of the predefined RPDOs
Keywordsn/a
DSP3.3 MiB2018-12-20Login
CiA 422-3-3 version 2.1.0CANopen application profile for municipal vehicles – Part 3-3: Pre-defined SDOs
DescriptionThis set of CANopen application profile specifications describes the CleANopen embedded body control network of municipal vehicles, e.g. refuse collecting trucks. It specifies the CANopen communication interfaces and the application functionality of several functional elements (virtual devices). It does not specify CANopen devices. The CleANopen application profile specifications consists of several parts: Part 1 provides the general definitions, Part 2 specifies the functionality of the virtual devices, Part 3 specifies the pre-defined PDOs and SDOs, Part 4 specifies the application objects. This sub-part of part 3 specifies the pre-defined additional SDO clients and servers.
Keywordsn/a
DSP0.9 MiB2018-12-20Login
CiA 422-4 version 2.1.0CANopen application profile for municipal vehicles – Part 4: Application objects
DescriptionThis set of CANopen application profile specifications describes the CleANopen embedded body control network of municipal vehicles, e.g. refuse collecting trucks. It specifies the CANopen communication interfaces and the application functionality of several functional elements (virtual devices). It does not specify CANopen devices. The CleANopen application profile specifications consists of several parts: Part 1 provides the general definitions, Part 2 specifies the functionality of the virtual devices, Part 3 specifies the pre-defined PDOs and SDOs, Part 4 specifies the application objects. This part specifies the values and value range attribute of the application objects. It specifies also the object and data type attributes of the application objects.
Keywordsn/a
DSP3.2 MiB2018-12-20Login
CiA 423-1 version 1.0.0CANopen application profile for rail vehicle power drive systems – Part 1: General definitions
DescriptionThis CANopen application profile defines the communication between virtual devices within a rail vehicle power drive system. The power drive system shall be connected via a gateway device to the logical CANopen-based train vehicle control network as defined in CiA 421.
Keywordsn/a
DSP89 KiB2006-08-18Login
CiA 423-2 version 1.0.0CANopen application profile for rail vehicle power drive systems – Part 2: Traction controller
DescriptionThis part of the CANopen application profile for rail vehicles power drive systems describes the traction controller.
Keywordsn/a
DSP545 KiB2006-08-18Login
CiA 423-3 version 1.0.0CANopen application profile for rail vehicle power drive systems – Part 3: Diesel engine control unit
DescriptionThis part of the CANopen application profile for rail vehicle power drive systems describes the diesel engine control unit.
Keywordsn/a
DSP404 KiB2006-08-18Login
CiA 423-4 version 1.0.0CANopen application profile for rail vehicle power drive systems – Part 4: Transmission control unit
DescriptionThis part of the CANopen application profile for rail vehicle power drive systems describes the transmission control unit.
Keywordsn/a
DSP165 KiB2006-08-18Login
CiA 423-5 version 1.0.0CANopen application profile for rail vehicle power drive systems – Part 5: Diesel engine safety control unit
DescriptionThis part of the CANopen application profile for rail vehicle power drive systems describes the diesel engine safety control unit.
Keywordsn/a
DSP119 KiB2006-08-18Login
CiA 423-6 version 1.0.0CANopen application profile for rail vehicle power drive systems – Part 6: Speed sensor unit
DescriptionThis part of the CANopen application profile for rail vehicle power drive systems describes the speed sensor unit.
Keywordsn/a
DSP113 KiB2006-08-18Login
CiA 423-7 version 1.0.0CANopen application profile for rail vehicle power drive systems – Part 7: Diesel engine signal unit
DescriptionThis part of the CANopen application profile for rail vehicle power drive systems describes the diesel engine signal unit. The diesel engine signal unit is the measuring unit, required for diesel engine control and monitoring.
Keywordsn/a
DSP250 KiB2006-08-18Login
CiA 423-10 version 1.0.0CANopen application profile for rail vehicle power drive systems – Part 10: Particle filters control unit
DescriptionThis part of the CANopen application profile for rail vehicle power drive systems describes the particle filters control unit. In addition this document describes the objects, required for controlling the selective catalytic reduction unit.
Keywordsn/a
DSP198 KiB2006-08-18Login
CiA 423-11 version 1.0.0CANopen application profile for rail vehicle power drive systems – Part 11: Starter unit
DescriptionThis part of the CANopen application profile for rail vehicle power drive systems describes the starter unit.
Keywordsn/a
DSP95 KiB2006-08-18Login
CiA 423-12 version 1.0.0CANopen application profile for rail vehicle power drive systems – Part 12: Oil refill unit
DescriptionThis part of the CANopen application profile for rail vehicle power drive systems describes the oil refill unit.
Keywordsn/a
DSP111 KiB2006-08-18Login
CiA 424-1 version 1.0.0CANopen application profile for rail vehicle door control systems - Part 1: General definitions
DescriptionThis CANopen application profile defines the communication between virtual devices within a rail vehicle door control system. The rail vehicle door control system may be connected via a gateway device to the logical CANopen-based rail vehicle in-vehicle network. The set of specifications is organized as follows: Part 1: General definitions, Part 2: Door controller, Part 3: Door unit. Devices compliant to this application profile shall use communication techniques, which conform to those described in the CiA Draft Standard 301.
Keywordsn/a
DSP114 KiB2006-08-18Login
CiA 424-2 version 1.0.0CANopen application profile for rail vehicle door control systems - Part 2: Door controller
DescriptionThis part of the CANopen application profile rail vehicle door control system describes the rail door controller.
Keywordsn/a
DSP304 KiB2006-08-18Login
CiA 424-3 version 1.0.0CANopen application profile for rail vehicle door control systems – Part 3: Door unit
DescriptionThis part of the CANopen application profile for rail vehicle door control systems describes the door unit.
Keywordsn/a
DSP182 KiB2006-08-18Login
CiA 425-1 version 2.1.0CANopen application profile for medical diagnostic add-on modules – Part 1: General definitions
DescriptionThe CANopen application profile for medical diagnostic add-on modules includes several parts: Part 1 describes general definitions. Part 2 defines the profile for injector devices. Devices compliant to these profiles use communication techniques, which conforms to those described in the CANopen application layer and communication profile (CiA 301). In addition, medical devices and sub-systems may use communication techniques, which conform to those described in the CANopen additional application layer functions specification (CiA 302). These specifications should be consulted in parallel to these device profile specifications.
Keywordsn/a
DS243 KiB2011-06-03Login
CiA 425-2 version 2.4.0CANopen application profile for medical diagnostic add-on modules – Part 2: Injector
DescriptionThis profile specifies the CANopen device profile for injector interface units. This profile covers injectors connected to a medical diagnostic system (angiography, computer tomography, and other medical diagnostic devices), which provide CANopen Manager functionality. If a safety-related communication is required, the injector device is compliant to the CANopen framework for safety-related communication (EN 50325-5). The definition of SRDOs (safety-related data objects) is not in the scope of this document. A prerequisite for the conformity to this CANopen device profile is conformity with the CANopen communication profile (CiA 301). Additionally, in the case that the module is programmable it shall conform to the framework for programmable CANopen devices (CiA 302). These specifications should be consulted in parallel to this device profile specification.
Keywordsn/a
DSP795 KiB2017-11-17Login
CiA 425-2 version 2.2.0CANopen application profile for medical diagnostic add-on modules – Part 2: Injector
DescriptionThis profile specifies the CANopen device profile for injector interface units. This profile covers injectors connected to a medical diagnostic system (angiography, computer tomography, and other medical diagnostic devices), which provide CANopen Manager functionality. If a safety-related communication is required, the injector device shall be compliant to the CANopen framework for safety-related communication (CiA 304). A prerequisite for the conformity to this CANopen device profile is conformity with the CANopen communication profile (CiA 301). Additionally, in the case that the module is programmable it shall conform to the framework for programmable CANopen devices (CiA 302). These specifications should be consulted in parallel to this device profile specification.
Keywordsn/a
DS1.4 MiB2011-06-03Login
CiA 425-2 version 2.4.1CANopen application profile for medical diagnostic add-on modules – Part 2: Injector
Descriptionn/a
Keywordsn/a
WD1.5 MiB2019-09-20Login
CiA 426-1 version 1.0.0CANopen application profile for rail vehicle exterior lighting control – Part 1: General definitions
DescriptionThis CANopen application profile defines the communication between virtual devices within a rail vehicle exterior lighting control system. The exterior lighting controller is optionally connected via a gateway device to the logical CANopen-based train vehicle control network as defined in CiA 421. The set of specifications is organized as follows: Part 1: General definitions, Part 2: Exterior lighting controller (ELC), Part 3: Exterior lighting unit (ELU). Devices compliant to this application profile uses communication techniques, which conform to those described in the CiA Draft Standard 301.
Keywordsn/a
DSP121 KiB2006-08-18Login
CiA 426-2 version 1.0.0CANopen application profile for rail vehicle exterior lighting control – Part 2: Exterior lighting controller
DescriptionThis part of the CANopen application profile rail vehicle exterior lighting describes the exterior lighting controller.
Keywordsn/a
DSP168 KiB2006-08-18Login
CiA 426-3 version 1.0.0CANopen application profile for rail vehicle exterior lighting control – Part 3: Exterior lighting unit
DescriptionThis part of the CANopen application profile for rail vehicle exterior lighting describes the exterior lighting unit.
Keywordsn/a
DSP280 KiB2006-08-18Login
CiA 430-1 version 1.0.0CANopen application profile for rail vehicle auxiliary operating systems – Part 1: General definitions
DescriptionThis CANopen application profile defines the communication between virtual devices within a rail vehicle auxiliary operating system. The auxiliary operating system shall be connected via a gateway device to the logical CANopen-based train vehicle control network as defined in /CiA421/. The set of specifications is organized as follows: Part 1: General definitions, Part 2: Auxiliary operating system controller, Part 3: Power train cooling unit, Part 4: Coolant expansion tank unit, Part 5: Power train cooling fan control unit, Part 6: Engine pre-heating unit, Part 7: Hydrostatic signal interface unit, Part 8: Battery charger unit, Part 9: Generator unit. Devices compliant to this application profile uses communication techniques, which conform to those described in the CiA Draft Standard 301.
Keywordsn/a
DSP106 KiB2006-08-18Login
CiA 430-2 version 1.0.0CANopen application profile for rail vehicle auxiliary operating systems – Part 2: Auxiliary operating system controller
DescriptionThis part of the CANopen application profile for rail vehicle auxiliary operating systems describes the auxiliary operating system controller.
Keywordsn/a
DSP198 KiB2006-08-18Login
CiA 430-3 version 1.0.0CANopen application profile for rail vehicle auxiliary operating systems – Part 3: Power train cooling control unit
DescriptionThis part of the CANopen application profile for rail vehicle auxiliary operating systems describes the power train cooling control unit.
Keywordsn/a
DSP146 KiB2006-08-18Login
CiA 430-4 version 1.0.0CANopen application profile for rail vehicle auxiliary operating systems – Part 4: Coolant expansion tank unit
DescriptionThis part of the CANopen application profile for rail vehicle auxiliary operating systems describes the coolant expansion tank unit.
Keywordsn/a
DSP103 KiB2006-08-18Login
CiA 430-5 version 1.0.0CANopen application profile for rail vehicle auxiliary operating systems – Part 5: Power train cooling fan control unit
DescriptionThis part of the CANopen application profile railway auxiliary operating system describes the power train cooling fan control unit.
Keywordsn/a
DSP115 KiB2006-08-18Login
CiA 430-6 version 1.0.0CANopen application profile for rail vehicle auxiliary operating systems – Part 6: Engine pre-heating unit
DescriptionThis part of the CANopen application profile for rail vehicle auxiliary operating systems describes the engine pre-heating unit.
Keywordsn/a
DSP118 KiB2006-08-18Login
CiA 430-7 version 1.0.0CANopen application profile for rail vehicle auxiliary operating systems – Part 7: Hydrostatic signal unit
DescriptionThis part of the CANopen application profile for rail vehicle auxiliary operating systems describes the hydrostatic signal interface unit.
Keywordsn/a
DSP124 KiB2006-08-18Login
CiA 430-9 version 1.0.0CANopen application profile for rail vehicle auxiliary operating systems – Part 9: Generator unit
DescriptionThis virtual device describes the generator unit, which is a part of the rail vehicle auxiliary operating system.
Keywordsn/a
DSP104 KiB2006-08-18Login
CiA 433-1 version 1.0.0CANopen application profile for rail vehicle interior lighting control - Part 1: General definitions
DescriptionThis CANopen application profile defines the communication between virtual devices within a rail vehicle interior lighting control system. The interior lighting controller is optionally connected via a gateway device to the logical CANopen-based train vehicle control network as defined in CiA 421. The set of specifications is organized as follows: Part 1: General definitions, Part 2: Interior lighting controller (ILC), Part 3: Interior lighting unit (ILU). Devices compliant to this application profile uses communication techniques, which conform to those described in the CiA Draft Standard 301.
Keywordsn/a
DSP96 KiB2006-08-18Login
CiA 433-2 version 1.0.0CANopen application profile for rail vehicle interior lighting control - Part 2: Interior lighting controller
DescriptionThis part of the CANopen application profile for rail vehicle interior lighting control describes the interior lighting controller.
Keywordsn/a
DSP129 KiB2006-08-18Login
CiA 433-3 version 1.0.0CANopen application profile for rail vehicle interior lighting control -Part 3: Interior lighting unit
DescriptionThis part of the CANopen application profile for rail vehicle interior lighting control describes the interior lighting unit.
Keywordsn/a
DSP235 KiB2006-08-18Login
CiA 434-1 version 2.0.0CANopen profiles for laboratory automation systems – Part 1: General definitions
DescriptionThis set of device profiles for laboratory automation systems describes a master/slave-based communication between a laboratory automation master and several laboratory automation slaves (units). In addition to the general system structure, this part of CiA 434 defines a finite state machine (FSA) that is supported by all laboratory units, following the specification CiA 434. In addition, this part specifies two predefined control structures for laboratory units. On the one hand, the laboratory automation master can control the laboratory units via single operating commands. On the other hand this part provides a generic structure for a “preconfigurable work plan” that enables a quasi-autonomous laboratory unit operation, which is monitored by the laboratory master. The set of CANopen profiles for laboratory automation systems includes several parts: Part 1 describes general definitions. Part 2 defines the device profile for dilutor/dispenser/pump units. Part 3 defines the heating, cooling and shaking unit. Part 4 defines the device profile for pipette control units. Part 5 defines the device profile for multi axis control units. Part 6 defines the device profile for drive units. Part 7 defines the device profile for washing units. Part 8 defines the device profile for centrifuge units. Part 9 defines the device profile for stacker units. Part 10 defines the device profile for detection units. Devices compliant to these profiles use communication techniques, which conform to those defined in the CANopen application layer and communication profile (CiA 301). In addition, they may use communication techniques, which conform to those described in the set of specifications for additional application layer functions (CiA 302). These specifications should be consulted in parallel to these device profile specifications.
Keywordsn/a
DSP579 KiB2009-04-22Login
CiA 434-2 version 1.0.0CANopen profiles for laboratory automation systems – Part 2: CANopen device profile for dilutor, dispenser and pump units
DescriptionThis part of the CANopen profiles for laboratory automation systems defines the CANopen interface for dilutor, dispenser and pump units. Based on the definitions given in CiA 434-1, this CANopen device profile specifies commands as well as parameters relevant for controlling dilutor, dispenser and pump units that are part of an automated laboratory system.
Keywordsn/a
DSP574 KiB2010-06-30Login
CiA 434-3 version 1.0.0CANopen profiles for laboratory automation systems – Part 3: CANopen device profile for heating, cooling and shaking units
DescriptionThis part of the CANopen device profiles for laboratory automation systems specifies the heating, cooling and shaking unit.
Keywordsn/a
DSP425 KiB2010-06-30Login
CiA 436-1 version 1.1.0CANopen application profile for construction machineries – Part 1: General definitions
DescriptionThis application profile provides general definition as well as recommendations for using CANopen control networks on construction machineries. In addition, this application profile introduces the virtual control architecture on construction machineries, integrating the engine control system, the drivers’ desk, the sensor control system, the transmission control system, the fleet management control system as well as the control system for the superstructure respectively implement.
Keywordsn/a
DSP392 KiB2010-06-30Login
CiA 437-1 version 1.0.0CANopen application profile for grid-based photovoltaic systems – Part 1: General definitions
DescriptionThis application profile defines the CANopen interfaces for photovoltaic control systems. This includes interfaces to photovoltaic controller, photovoltaic inverter, wind direction sensor, temperature sensor, radiation sensor, energy (Wh) sensor, power (W) sensor, solar panel tracking system, etc. The specification comprises the following parts: Part 1: General definitions, Part 2: Pre-defined communication objects, Part 3: Detailed process data specification. This part defines the physical layer, the general system architecture, and some common communication parameter objects. It also defines, which process data and parameters are used by the virtual devices.
Keywordsn/a
DSP541 KiB2008-01-10Login
CiA 437-2 version 1.0.0CANopen application profile for grid-based photovoltaic systems – Part 2: Pre-defined communication objects
DescriptionThis part of the application profile specifies the pre-defined communication objects.
Keywordsn/a
DSP124 KiB2008-01-10Login
CiA 437-3 version 2.0.0CANopen application profile for grid-based photovoltaic systems – Part 3: Detailed process data specification
DescriptionThis application profile defines the CANopen interfaces for photovoltaic control systems. This includes interfaces to photovoltaic controller, photovoltaic inverter, wind direction sensor, temperature sensor, radiation sensor, energy (Wh) sensor, power (W) sensor, solar panel tracking system, etc. The application profile specification consists of several parts: Part 1: General definitions, Part 2: Pre-defined communication objects, Part 3: Detailed process data specification. This part of the application profile specifies in detail the process data and parameters of the virtual devices.
Keywordsn/a
DSP1.8 MiB2012-06-15Login
CiA 442 version 1.0.0CANopen profile for IEC 61915-2 compatible motor starters
DescriptionThis document specifies the CANopen profile for a sub-section of low-voltage switchgear devices: motor starters, soft starter and motor management starters. The specification is functional compatible with the international standard /IEC61915-2/. NOTE: In order to understand this profile it is necessary to read in advance the international standard /IEC61915-2/.
Keywordsn/a
DSP196 KiB2012-03-23Login
CiA 443 version 3.0.1CANopen profile for SIIS level-2 devices
DescriptionThis device profile specifies instruments and actuators devices for subsea measurement systems. Subsea instruments include simple pressure and temperature sensors as well as complex multi-purpose instruments such as multiphase flow meter. Subsea actuators include simple valves and valve controller units. The specification of the SIIS level-2 application master is not in the scope of this device profile. NOTE: This specification has been jointly developed with the SIIS (Subsea Instruments Interface Standardization) group. SIIS level-2 devices make use of this device profile specification.
Keywordsn/a
DSP1.2 MiB2015-04-10Login
CiA 444-1 version 2.0.0CANopen profiles for container-handling machine add-on devices – Part 1: General definitions
DescriptionThis profile series specifies the CANopen interfaces for container-handling machine add-on devices such as spreaders for cranes and for straddle carriers. The specification comprisesthe following parts: Part 1: General definitions, Part 2: Spreader for crane, Part 3: Spreader for straddle carrier. Part 1 specifies the physical layer, and some common communication parameter objects.
Keywordsn/a
DSP132 KiB2008-12-17Login
CiA 444-2 version 2.0.0CANopen profiles for container-handling machine add-on devices – Part 2: Spreader for crane
DescriptionThis part specifies the device profile for crane spreaders including process data and process data objects.
Keywordsn/a
DSP444 KiB2012-06-14Login
CiA 444-3 version 2.0.0CANopen profiles for container-handling machine add-on devices – Part 3: Spreader for straddle carrier
DescriptionThis part specifies the device profile for straddle carrier spreaders including process data and process data objects.
Keywordsn/a
DSP396 KiB2012-06-14Login
CiA 445 version 1.0.0CANopen device profile for RFID devices
DescriptionThis device profile specifies the CANopen interface for simple and intelligent radio frequency identification devices.
Keywordsn/a
DSP0.9 MiB2007-08-23Login
CiA 446 version 1.0.0CANopen device profile for AS-Interface gateways
DescriptionThis profile defines the CANopen interface for gateways connecting AS-Interface circuits. One single CANopen logical device supports up to two AS-Interface circuits. The gateway implements AS-Interface master functionality.
Keywordsn/a
DSP477 KiB2006-11-06Login
CiA 447-1 version 2.1.0CANopen application profile for special-purpose car add-on devices – Part 1: General definitions
DescriptionThis CANopen application profile specifies the CAN physical layer as well as application, configuration and diagnostic parameters for the add-on devices used in special-purpose passenger cars such as taximeter, roof bar, etc. The specification comprises the following parts: Part 1: General definitions, Part 2: Virtual device definition, Part 3: Detailed process data specification, Part 4: Pre-defined CAN-IDs and communication objects. This part defines the physical layer, the general system architecture, and some common communication parameter objects.
Keywordsn/a
DSP0.9 MiB2015-12-14Login
CiA 447-4 version 2.1.0CANopen application profile for special-purpose car add-on devices – Part 4: Pre-defined CAN-IDs and communication objects
DescriptionThis CANopen application profile specifies the CAN physical layer as well as application, configuration and diagnostic parameters for the add-on devices used in special-purpose passenger cars such as taximeter, roof bar, etc. The specification comprises the following parts: Part 1: General definitions. Part 2: Virtual device definition. Part 3: Detailed process data specification. Part 4: Pre-defined CAN-IDs and communication objects. This part specifies the pre-defined CAN-IDs and communication objects.
Keywordsn/a
DSP234 KiB2015-12-14Login
CiA 447-2 version 2.1.3CANopen application profile for special-purpose car add-on devices – Part 2: Virtual device definition
DescriptionThis CANopen application profile specifies the physical layer as well as application, configuration and diagnostic parameters for the add-on devices used in special-purpose passenger cars such as taximeter, roof bar, etc. The specification comprises the following parts: Part 1: General definitions. Part 2: Virtual device definition. Part 3: Detailed process data specification. Part 4: Pre-defined CAN-IDs and communication objects. This part defines the virtual devices. It also defines, which process data and parameters are used by the virtual devices.
Keywordsn/a
DSP179 KiB2018-09-07Login
CiA 447-3 version 2.1.3CANopen application profile for special-purpose car add-on devices – Part 3: Detailed process data specification
DescriptionThis CANopen application profile specifies the physical layer as well as application, configuration and diagnostic parameters for the add-on devices used in special-purpose passenger cars such as taximeter, roof bar, etc. The specification comprises the following parts: Part 1: General definitions. Part 2: Virtual device definition. Part 3: Detailed process data specification. Part 4: Pre-defined CAN-IDs and communication objects. This part specifies in detail the process data and parameters of the virtual devices.
Keywordsn/a
DSP1.7 MiB2018-09-07Login
CiA 450 version 1.0.0CANopen device profile for pumps
DescriptionThis profile specifies the CANopen interfaces for pump devices. The specification is based on the bus-independent profile developed by VDMA (German association of machine builders). It specifies interfaces for the following pump types: Generic pump, Liquid pump. The VDMA profile for vacuum and liquid pumps should be consulted in parallel with this profile.
Keywordsn/a
DSP2.6 MiB2010-02-25Login
CiA 452 version 1.0.0CANopen device profile PLCopen motion control
DescriptionThis profile specifies the CANopen interface for drives controlled by programmable logic controllers (PLC) using PLCopen motion control. The main intention of this specification is to control the drive by means of one RPDO and one TPDO. The motion function block may be performed by the PLC or by the drive. This profile also specifies the CANopen interface for master-slave drive control according to PLCopen.
Keywordsn/a
DSP358 KiB2010-08-31Login
CiA 453 version 1.1.0CANopen device profile for power supply
DescriptionThe CANopen device profile power supply specifies the communication interface for AC/AC, DC/DC, AC/DC, and DC/AC converters. It is suitable for programmable and nonprogrammable power supply devices with single or multiple outputs that are voltage-, current-, or power-controlled.
Keywordsn/a
DSP1.3 MiB2010-07-20Login
CiA 453 version 1.1.3CANopen device profile power supply
Descriptionn/a
Keywordsn/a
WD1.7 MiB2018-02-23Login
CiA 454-1 version 2.0.0CANopen application profile for energy management systems – Part 1: General definitions
DescriptionThe CANopen application profile for EMSs specifies the communication interface for all virtual devices that may take part in energy management control application. Such energy management control applications may be implemented in e.g. light electric vehicles, robots, offshore parks, isolated farms, etc. The CANopen application profile for EMSs consists of the following parts: Part 1: General definitions, Part 2: Pre-defined communication parameters and general application objects, Part 3: Pre-defined PDO communication, Part 4: EMS controller, Part 5: Voltage converter unit, Part 6: Battery pack, Part 7: Motor control unit (under development), Part 8: Load monitoring unit (under development), Part 9: HMI unit (under development), Part 10: Security unit (under development), Part 11: Sensor unit (under development), Part 12: Gateway unit (under development), Part 13: Generator unit, Part 14: Load unit. This document represents the part 1 of the CANopen application profile for EMSs. Part 1 provides the general concept of the EMS.
Keywordsn/a
DSP1.2 MiB2014-06-17Login
CiA 454-2 version 2.0.0CANopen application profile for energy management systems – Part 2: Pre-defined communication parameters and general application objects
DescriptionThis document represents the part 2 of the CANopen application profile for EMSs. Part 2 provides additional specifications with regard to the pre-defined communication objects as well as the general communication objects.
Keywordsn/a
DSP817 KiB2014-06-17Login
CiA 454-3 version 2.0.0CANopen application profile for energy management systems – Part 3: PDO communication
DescriptionThis document represents the part 3 of the CANopen application profile for EMSs. Part 3 provides the PDO communication and mapping parameters.
Keywordsn/a
DSP533 KiB2014-06-17Login
CiA 454-4 version 2.0.0CANopen application profile for energy management systems – Part 4: EnergyBus controller (EBC)
DescriptionThis document represents the part 3 of the CANopen application profile for EMSs. Part 3 specifies the application objects provided by the virtual device Energy management system controller (EBC).
Keywordsn/a
DSP176 KiB2014-06-17Login
CiA 454-5 version 2.0.0CANopen application profile for energy management systems – Part 5: Voltage converter
DescriptionThis document represents the part 5 of the CANopen application profile for EMSs. Part 5 provides application objects provided by the AC-DC converter. The AC-DC converter may be implemented to realize a battery charger or a charger station.
Keywordsn/a
DSP859 KiB2014-06-17Login
CiA 454-6 version 2.0.0CANopen application profile for energy management systems – Part 6: Battery pack
DescriptionThis document represents the part 6 of the CANopen application profile for EMSs. Part 6 of the document specifies application objects provided by the battery pack.
Keywordsn/a
DSP518 KiB2014-06-17Login
CiA 454-13 version 1.0.0CANopen application profile for energy management systems – Part 13: - Generator unit
DescriptionThis document represents the part 13 of the CANopen application profile for EMSs. Part 13 of the document specifies generator units such as a diesel engine, photovoltaic generator, winds turbine, etc. Generators shall be divided into two classes: Controllable and stochastic generator.
Keywordsn/a
DSP383 KiB2014-06-17Login
CiA 454-14 version 1.0.0CANopen application profile for energy management systems – Part 14 - Load unit
DescriptionThis document represents the part 14 of the CANopen application profile for EMSs. Part 14 of the document specifies load units such as lighting, electrical motor, radio, refrigerator, washing machine, etc. Loads shall be divided into three classes: controllable loads, influenceable loads and non-controllable loads.
Keywordsn/a
DSP330 KiB2014-06-17Login
CiA 454-7 version 0.0.8CANopen application profile for energy management systems Part 7: Drive control unit
Descriptionn/a
Keywordsn/a
WD415 KiB2019-12-20Login
CiA 454-9 version 0.0.6CANopen application profile for energy management systems Part 9: Human machine interface
Descriptionn/a
Keywordsn/a
WD182 KiB2019-12-20Login
CiA 455 version 1.0.0CANopen application profile for drilling machines
DescriptionThis specification describes the control application for drilling machines with special regard on positioning and tool control.
Keywordsn/a
DSP806 KiB2010-06-30Login
CiA 456 version 1.0.0CANopen device profile for configurable network component
DescriptionThis document specifies the CANopen interface for configurable network components that provide CAN bridge functionality and have up to 16 CAN ports including one configurable CANopen port. Via this CANopen port, the CAN message routing between the remaining 15 CAN ports of such a device is configured. The properties of the higher layer protocols that are running on these 15 CAN ports are not in the scope of this specification. For such applications other specifications may apply and may be combined with this profile.
Keywordsn/a
DSP225 KiB2012-07-11Login
CiA 457 version 1.0.0CANopen device profile for wireless transmission media based CANopen devices
DescriptionThis specification represents the CANopen device profile for wireless transmission media based CANopen devices. Devices compliant to this specification use communication techniques, which conform to those described in the CANopen application layer and communication techniques, which conform to those described in the CANopen additional application layer functions. Such devices utilize a wireless transmission media instead of CAN.
Keywordsn/a
DSP369 KiB2011-08-09Login
CiA 458 version 1.0.0CANopen device profile for energy measurements
DescriptionThis document specifies the CANopen interface for energy measuring devices. This includes energy consumption as well as energy production, in particular for energy recovering.
Keywordsn/a
DSP306 KiB2013-09-09Login
CiA 459-1 version 1.0.0CANopen profile for on-board weighing devices – Part 1: General specification and functional overview
DescriptionThis profile specifies the CANopen interface for on-board weighing devices. These devices are usable on trucks, off-highway or off-road vehicles (including train coaches). This profile consists of several parts. This part of the profile describes the operating principles including the error handling. It specifies the CAN physical layer and the CAN data link layer. Additionally, it describes the CANopen application layer functionality.
Keywordsn/a
DSP423 KiB2012-10-02Login
CiA 459-2 version 1.0.0CANopen profile for on-board weighing devices – Part 2: Communication parameter specification
DescriptionThis profile specifies the CANopen interface for on-board weighing devices. These devices are usable on trucks, off-highway or off-road vehicles (including train coaches). This profile consists of several parts. This part of the profile specifies the mandatory and recommended communication parameters, including the parameter sets for PDO communication.
Keywordsn/a
DSP97 KiB2012-10-02Login
CiA 459-3 version 1.0.0CANopen profile for on-board weighing devices – Part 3: Application parameter specification
DescriptionThis profile specifies the CANopen interface for on-board weighing devices. These devices are usable on trucks, off-highway or off-road vehicles (including train coaches). This profile consists of several parts. This part of the profile specifies the application parameter as process data, the diagnostic parameters and configuration parameters.
Keywordsn/a
DSP379 KiB2012-10-02Login
CiA 460 version 1.0.0CANopen profile for service robot controller - Associated device and Device-RTC
DescriptionThis document specifies the CANopen interface of a service robot controller device, which is compliant to the Robotic technology component (RTC) specification. The profile specifies the NMT master application and its object dictionary with NMT master parameter as well as CANopen device proxies representing the connected CANopen devices in the service robot controller device.
Keywordsn/a
DSP249 KiB2012-02-10Login
CiA 461-3 version 1.0.0CANopen profile for weighing devices - Part 3: Device profile for scale
DescriptionThis profile specifies CANopen interface for electronic weighing instruments as scales and auxiliary devices as specific I/O modules like input panel or indicator. This profile consists of the following parts: Part 1: General definitions, Part 2: Device profile for load cells, Part 3: Device profile for scales, Part 4: Device profile for HMI or indicator. This part specifies the device profile for scales. This includes process data and configuration parameters as well as PDO communication and mapping parameters.
Keywordsn/a
DSP847 KiB2019-08-01Login
CiA 461-4 version 1.0.0CANopen profile for weighing devices - Part 4: Device profile for HMI or indicator
DescriptionThis profile specifies CANopen interface for electronic weighing instruments as indicators and auxiliary devices as specific I/O modules like input panel or indicator. This profile consists of the following parts: Part 1: General definitions, Part 2: Device profile for load cell, Part 3: Device profile for scale, Part 4: Device profile for HMI or indicator. This part specifies the device profile for an HMI or indicator. This includes process data and configuration parameters as well as PDO communication and mapping parameters.
Keywordsn/a
DSP364 KiB2019-08-01Login
CiA 461-1 version 1.1.0CANopen profile for weighing devices - Part 1: General definitions and PDO specifications
DescriptionThis profile shall specify the CANopen interface for electronic weighing instruments such as load cells, scales, and auxiliary devices as specific I/O modules like input panel or indicator. This profile consists of the following parts: Part 1: General definitions, Part 2: Device profile for load cells, Part 3: Device profile for scales, Part 4: Device profile for HMI or indicator. This part shall specify general definitions. This includes the lower-layer definitions as well as general communication parameters including PDO communication and mapping parameters and general application layer functionality.
Keywordsn/a
DSP613 KiB2019-08-01Login
CiA 461-2 version 1.1.0CANopen profile for weighing devices - Part 2: Device profile for load cells
DescriptionThis profile specifies CANopen interface for electronic weighing instruments as load cells scales and auxiliary devices as specific I/O modules like input panel or indicator. This profile consists of the following parts: Part 1: General definitions, Part 2: Device profile for load cells, Part 3: Device profile for scales, Part 4: Device profile for HMI or indicator. This part specifies the device profile for load cells. This part specifies the device profile for load cells. This includes process data and configuration parameters as well as PDO communication and mapping parameters.
Keywordsn/a
DSP671 KiB2019-08-01Login
CiA 461-C1 version 0.0.1CiA profile for weighing devices
Descriptionn/a
Keywordsn/a
WDP474 KiB2019-08-09Login
CiA 461-B1 version 0.0.1CiA profile for weighing devices
Descriptionn/a
Keywordsn/a
WDP3.2 MiB2019-08-09Login
CiA 461-4 version 1.0.2CANopen profile for weighing devices – Part 4: Device profile for indicator
Descriptionn/a
Keywordsn/a
1.6 MiB2020-01-14
CiA 461-4 version 1.0.3CANopen profile for weighing devices – Part 4: Device profile for indicator
Descriptionn/a
Keywordsn/a
WD1.6 MiB2020-02-05Login
CiA 461-3 version 1.0.5CANopen Profile for weighing devices - Part 3: Device profile for scale
Descriptionn/a
Keywordsn/a
WD3.4 MiB2020-02-05Login
CiA 461-1 version 1.1.3CANopen profile for weighing devices - Part 1: General definitions and PDO specifications
Descriptionn/a
Keywordsn/a
WD674 KiB2020-02-05Login
CiA 461-2 version 1.1.3CANopen profile for weighing devices – Part 2: Device profile for load cells
Descriptionn/a
Keywordsn/a
WD2.7 MiB2020-02-05Login
CiA 462 version 1.0.0CANopen device profile for item detection devices
DescriptionThis profile specifies the CANopen interface for devices that identify existence, dimension, orientation, or movement of items in their environment (e.g. optical camera (2D or 3D), laser device). Often those devices are called vision sensors or object detection devices.
Keywordsn/a
DSP0.9 MiB2016-05-30Login
CiA 463-C version 1.0.0CANopen device profile for IO-Link gateway – CANopen mapping
DescriptionThis document specifies the mapping of the IO-Link gateways to CANopen. This includes the specifications of the Classic CAN physical layer, data link layer, and the Classic CANopen communication parameters.
Keywordsn/a
DSP147 KiB2019-06-27Login
CiA 463-F version 1.0.0CANopen device profile for IO-Link gateway - CANopen FD mapping
DescriptionThis document specifies the mapping of the IO-Link gateways to CANopen FD. This includes the specifications of the CAN FD physical layer, data link layer, and the CANopen FD communication parameters.
Keywordsn/a
DSP150 KiB2019-06-27Login
CiA 463-B version 1.0.0CANopen device profile for IO-Link gateway - Functional behavior and parameters
DescriptionThis document specifies operating principles and the application data for IO-Link interface devices. This includes the functional behavior and general specifications of the application parameters.
Keywordsn/a
DSP463 KiB2019-06-27Login
CiA 312-1 version 1.0.0CANopen profile conformance test plan – Part 1: General definitions
DescriptionThe document contains additional lower-, dynamic- and upper tests for CANopen devices that shall be tested according to a certain device profile. The definitions of the generic lower-, dynamic- and upper tests do not fall in the scope of this document.
Keywordsn/a
DSP76 KiB2008-04-11Login
CiA 312-2 version 1.0.0CANopen profile conformance test plan – Part 2: Generic I/O modules
DescriptionThis part of CANopen device profile conformance test plan contains additional tests for generic I/O modules, which are tested for conformity according to CANopen device profile generic I/O modules. The additional tests verify entries in EDS and object dictionary, which are defined in CANopen device profile generic I/O modules. Furthermore additional test steps verify object coherences that are defined in that device profile. To achieve a certain level of conformity the CANopen device shall pass the corresponding tests defined in CANopen conformance test plan plus those defined in this part of the document series.
Keywordsn/a
DSP346 KiB2008-04-11Login
CiA 312-4 version 1.0.0CANopen profile conformance test plan – Part 4: Contrast media injectors
DescriptionThis part of the test plan specifies the additional tests for contrast media injectors, which shall be tested for conformity according to CANopen application profile for medical diagnostic addon modules (CiA 425-1 version 2.0. and CiA 425-2 version 2.0.2). The additional tests verify entries in EDS and object dictionary, which are defined in CANopen application profile for medical diagnostic add-on modules. Furthermore additional test steps verify the implementation of the device finite state automata and further object coherences, which are defined in application profile for medical diagnostic add-on modules. To achieve a certain level of conformity the DUT shall pass the corresponding tests defined in CANopen conformance test plan, CiA 312-1, plus those defined in this test plan.
Keywordsn/a
DSP0.9 MiB2009-01-16Login
CiA 312-4 version 1.0.1CANopen profile conformance test plan – Part 4: Contrast media injectors
Descriptionn/a
Keywordsn/a
WD1.5 MiB2012-05-20Login
CiA 312-5 version 0.0.4CANopen device profile conformance test plan - Part 5: Special purpose car add-on device
Descriptionn/a
Keywordsn/a
WD1.8 MiB2016-06-06Login
CiA 312-6 version 0.0.1CANopen device profile conformance test plan - Part 6: SIIS level-2 devices
Descriptionn/a
Keywordsn/a
WDP719 KiB2010-05-10Login
CiA 312-7 version 0.0.5CANopen conformance test plan - Part 7: Pedelec Profile 1
Descriptionn/a
Keywordsn/a
WD464 KiB2019-01-21Login