IG03 Profiles

Scope

The Interest Group (IG) profiles establishes and coordinates Special Interest Groups (SIGs). It approves Draft Specification (DS) documents developed by SIGs. The IG is responsible for the CiA 4XX series comprising device, application, and interface profiles as well as mappings to classic CANopen, CANopen FD, and other higher-layer protocols such as J1939.

Chairperson

Holger Zeltwanger, CiA

Meetings

Date Time* Group Location
2024-04-30 15:00 - 17:00 IG03 SIG15 Subsea e-meeting
2024-05-24 13:00 - 15:00 IG03 Profiles e-meeting
2024-06-04 10:00 - 12:00 IG03 SIG16 Energy management systems e-meeting
2024-06-06 10:00 - 12:00 IG03 SIG11 Municipal vehicles e-meeting
2024-10-17 13:00 - 15:00 IG03 SIG08 Contrast media injector e-meeting

* Local time at CiA office, 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 I/O modules2019-11-05Minutes170 KiB2019-11-13Login
IG profiles2020-09-21Minutes1.8 MiB2020-10-16Login
IG profiles2022-01-18Minutes404 KiB2022-01-24Login
Workshop: Configurable networks component2022-05-24Minutes11.2 MiB2022-05-25Login
IG profiles2022-12-01Minutes1.5 MiB2022-12-13Login
IG03 Profiles2023-12-06Minutes73 KiB2023-12-15Login
SIG encoder and inclinometer2019-09-18Minutes799 KiB2019-09-27Login
JTF CiA/EnergyBus: EMS2017-02-14Minutes2.0 MiB2017-07-17Login
JTF CiA/EnergyBus: EMS2017-06-09Minutes1.9 MiB2017-07-17Login
JTF CiA/EnergyBus: EMS2017-06-23Minutes1.7 MiB2017-07-17Login
JTF CiA/EnergyBus: EMS2016-12-21Minutes2.3 MiB2017-07-18Login
JTF CiA/EnergyBus: EMS2016-12-14Minutes2.9 MiB2017-07-18Login
JTF CiA/EnergyBus: EMS2016-06-29Minutes120 KiB2017-07-18Login
JTF CiA/EnergyBus: EMS2017-07-20Minutes132 KiB2017-08-01Login
JTF CiA/EnergyBus: EMS2018-05-22Minutes345 KiB2018-05-23Login
JTF CiA/EnergyBus: EMS2018-06-29Minutes135 KiB2018-07-03Login
JTF CiA/EnergyBus: EMS2018-09-06Minutes2.5 MiB2018-09-11Login
JTF CiA/EnergyBus: EMS2018-12-06Minutes3.4 MiB2019-01-22Login
JTF CiA/EnergyBus: EMS2019-04-03Minutes395 KiB2019-04-09Login
IG profiles JSIG CiA/EnergyBus: EMS2019-09-11Minutes1.5 MiB2019-09-23Login
IG profiles JSIG CiA/EnergyBus: EMS2019-10-14Minutes2.7 MiB2019-10-18Login
IG profiles JSIG CiA/EnergyBus: EMS2019-11-13Minutes1.8 MiB2019-12-17Login
IG profiles JSIG CiA/EnergyBus: EMS2019-12-19Minutes114 KiB2019-12-20Login
IG profiles JSIG CiA/EnergyBus: EMS2020-03-26Minutes125 KiB2020-04-22Login
IG profiles JSIG CiA/EnergyBus: EMS2020-04-30Minutes621 KiB2020-05-05Login
IG profiles: SIG EMS2020-06-04Minutes115 KiB2020-06-25Login
SIG subsea2021-05-18Minutes172 KiB2021-06-28Login
SIG subsea2021-04-19Minutes90 KiB2021-06-28Login
SIG subsea2021-01-26Minutes2.2 MiB2021-06-28Login
SIG subsea2021-06-15Minutes2.8 MiB2021-07-06Login
SIG subsea2021-07-06Minutes1.0 MiB2021-07-09Login
SIG subsea2021-09-24Minutes3.1 MiB2021-10-04Login
SIG subsea2021-11-12Minutes1.3 MiB2021-12-15Login
IG profiles SIG subsea2022-01-24Minutes1.0 MiB2022-01-28Login
SIG subsea 2022-02-18Minutes1.0 MiB2023-06-02Login
IG03 SIG15 Subsea2023-11-13Minutes0.9 MiB2023-11-29Login
IG03 SIG15 Subsea2024-01-22Minutes365 KiB2024-01-31Login
SIG contrast media injector2017-06-20Minutes116 KiB2017-07-14Login
SIG contrast media injector2017-05-05Minutes1.2 MiB2017-07-17Login
SIG contrast media injector2017-03-03Minutes4.6 MiB2017-07-17Login
SIG contrast media injector2017-02-09Minutes123 KiB2017-07-17Login
SIG contrast media injector2016-12-15Minutes118 KiB2017-07-18Login
SIG contrast media injector2016-11-03Minutes641 KiB2017-07-18Login
SIG contrast media injector2016-10-04Minutes112 KiB2017-07-18Login
SIG contrast media injector2016-07-01Minutes108 KiB2017-07-18Login
SIG contrast media injector2016-03-03Minutes4.1 MiB2017-07-18Login
SIG contrast media injector2016-02-18Minutes111 KiB2017-07-18Login
SIG contrast media injector2017-09-14Minutes566 KiB2017-09-18Login
SIG contrast media injector2017-10-06Minutes297 KiB2017-10-11Login
SIG contrast media injector2018-09-13Minutes292 KiB2018-09-17Login
SIG contrast media injector2018-10-24Minutes594 KiB2018-10-31Login
SIG contrast media injection 2018-12-11Minutes439 KiB2018-12-19Login
SIG contrat media injector2019-04-09Minutes0.9 MiB2019-04-11Login
SIG contrast media injector2019-02-19Minutes136 KiB2019-05-16Login
SIG contrast media injector2019-06-05Minutes140 KiB2019-06-24Login
SIG contrast media injector2019-07-16Minutes1.0 MiB2019-08-06Login
SIG contrast media injector2019-09-24Minutes570 KiB2019-10-15Login
SIG contrast media injector2019-12-12Minutes323 KiB2019-12-20Login
SIG contrast media injector2021-02-24Minutes852 KiB2021-03-02Login
SIG contrast media injector2021-11-04Minutes1.5 MiB2021-11-08Login
SIG contrast media injector2022-06-30Minutes668 KiB2022-07-06Login
SIG contrast media injector2022-11-30Minutes1.0 MiB2023-01-20Login
SIG contrast media injector2023-03-08Minutes460 KiB2023-03-17Login
IG03 SIG08 Contrast media injector2023-05-24Minutes297 KiB2023-06-01Login
IG03 SIG08 Contrast media injector2024-03-21Minutes21 MiB2024-03-22Login
SIG fluid power2014-09-09Minutes507 KiB2017-07-18Login
SIG fluid power2014-10-09Minutes132 KiB2017-07-18Login
SIG fluid power2014-11-11Minutes132 KiB2017-07-18Login
SIG fluid power2014-12-16Minutes133 KiB2017-07-18Login
SIG fluid power2015-03-17Minutes124 KiB2017-07-18Login
SIG fluid power2016-05-19Minutes123 KiB2017-07-18Login
SIG fluid power2016-06-21Minutes1.8 MiB2017-07-18Login
SIG fluid power2020-09-18Minutes654 KiB2020-10-05Login
SIG fluid power2020-11-09Minutes381 KiB2020-11-12Login
SIG fluid power2021-01-12Minutes59 KiB2021-01-15Login
SIG fluid power2021-02-23Minutes132 KiB2021-03-01Login
SIG fluid power2021-03-29Minutes100 KiB2021-03-31Login
SIG fluid power2021-04-01Minutes71 KiB2021-04-01Login
SIG fluid power2021-06-28Minutes162 KiB2021-06-29Login
SIG fluid power2021-07-27Minutes78 KiB2021-07-30Login
SIG fluid power2021-10-06Minutes278 KiB2021-10-19Login
SIG fluid power2021-11-15Minutes78 KiB2021-11-18Login
SIG fluid power2021-12-10Minutes451 KiB2021-12-15Login
IG profiles SIG fluid power2022-01-25Minutes145 KiB2022-01-27Login
SIG fluid power2022-02-21Minutes169 KiB2022-02-24Login
SIG generic I/O2016-01-21Minutes370 KiB2017-07-18Login
SIG generic I/O modules2019-02-18Minutes2.9 MiB2019-02-26Login
SIG generic I/O modules2019-03-13Minutes1.1 MiB2019-03-26Login
SIG generic I/O modules2019-11-05Minutes170 KiB2019-11-13Login
SIG generic I/O modules2019-12-06Minutes106 KiB2019-12-17Login
SIG generic I/O modules2020-01-22Minutes188 KiB2020-01-23Login
SIG generic I/O modules2020-03-30Minutes631 KiB2020-04-01Login
SIG generic I/O modules2020-05-20Minutes125 KiB2020-05-25Login
SIG generic I/O modules2020-06-29Minutes155 KiB2020-07-06Login
SIG generic I/O modules2020-07-22Minutes304 KiB2020-07-27Login
SIG generic I/O modules2020-09-02Minutes273 KiB2020-09-04Login
SIG generic I/O modules2020-09-22Minutes513 KiB2020-09-25Login
SIG generic I/O modules2020-10-27Minutes181 KiB2020-10-30Login
SIG generic I/O modules2021-01-19Minutes82 KiB2021-01-22Login
SIG generic I/O modules2021-02-16Minutes76 KiB2021-02-17Login
SIG generic I/O modules2021-03-16Minutes396 KiB2021-03-18Login
SIG generic I/O modules2021-04-21Minutes379 KiB2021-04-26Login
SIG generic I/O modules2021-05-06Minutes80 KiB2021-05-12Login
SIG generic I/O modules2021-06-08Minutes80 KiB2021-07-13Login
SIG generic I/O modules2021-10-18Minutes639 KiB2021-10-19Login
SIG generic I/O modules2021-11-15Minutes74 KiB2021-11-18Login
SIG generic I/O modules2021-12-10Minutes286 KiB2021-12-15Login
SIG generic I/O2022-01-11Minutes74 KiB2022-01-13Login
SIG generic I/O modules2022-01-21Minutes217 KiB2022-01-25Login
SIG IO-Link2017-02-13Minutes3.6 MiB2017-07-17Login
SIG IO-Link2017-03-17Minutes126 KiB2017-07-17Login
SIG IO-Link2017-05-19Minutes185 KiB2017-07-17Login
SIG IO-Link2017-06-19Minutes1.6 MiB2017-07-17Login
SIG IO-Link2017-08-24Minutes1.0 MiB2017-09-04Login
SIG IO-Link2017-09-14Minutes135 KiB2017-09-20Login
SIG IO-Link2017-10-13Minutes114 KiB2017-10-17Login
SIG IO-Link2017-10-27Minutes118 KiB2017-11-06Login
SIG IO Link2017-11-07Minutes106 KiB2017-11-08Login
SIG IO-Link2017-11-20Minutes3.5 MiB2017-11-21Login
SIG IO-Link2017-12-14Minutes131 KiB2018-01-03Login
SIG IO Link2018-10-25Minutes1.0 MiB2018-10-29Login
SIG lift control2017-04-26Minutes167 KiB2017-07-17Login
SIG lift control2016-09-07Minutes540 KiB2017-07-17Login
SIG lift control2016-04-13Minutes159 KiB2017-07-18Login
TF condition monitoring2017-07-18Minutes147 KiB2017-08-01Login
SIG lift control2017-09-05Minutes1.0 MiB2017-09-07Login
SIG lift control2017-12-19Minutes654 KiB2017-12-21Login
TF condition monitoring2018-01-29Minutes10.8 MiB2018-02-22Login
SIG lift control2018-03-13Minutes787 KiB2018-03-21Login
TF condition monitoring2018-03-21Minutes128 KiB2018-03-22Login
TF condition monitoring2018-05-16Minutes836 KiB2018-05-22Login
TF condition monitoring2018-06-20Minutes173 KiB2018-06-26Login
TF Condition monitoring2018-08-29Minutes1.7 MiB2018-09-03Login
SIG lift control2018-09-04Minutes7.2 MiB2018-09-07Login
SIG lift control2018-10-17Minutes1.3 MiB2018-10-18Login
SIG lift control2019-05-07Minutes2.2 MiB2019-05-16Login
TF Condition monitoring2019-11-15Minutes239 KiB2019-11-15Login
SIG lift control2020-04-29Minutes2.1 MiB2020-04-30Login
SIG lift control2020-10-29Minutes1.6 MiB2020-10-30Login
SIG lift control2020-11-05Minutes155 KiB2020-11-06Login
SIG lift control2021-04-19Minutes98 KiB2021-07-13Login
SIG lift control plugfest preparatory2021-08-26Minutes555 KiB2021-09-03Login
SIG lift control2021-11-10Minutes700 KiB2021-11-12Login
TF condition monitoring2022-01-20Minutes1.4 MiB2022-01-24Login
SIG lift control2022-02-16Minutes425 KiB2022-02-28Login
SIG lift control plugfest preparatory2022-08-25Minutes536 KiB2022-09-05Login
SIG lift plugfest2022-09-06Minutes76 KiB2022-09-08Login
SIG lift control + TF condition monitoring2022-10-18Minutes480 KiB2022-10-25Login
SIG lift plugfest2023-05-03Minutes79 KiB2023-05-09Login
SIG lift plugfest preparation2023-04-18Minutes752 KiB2023-05-10Login
SIG06 Lift control2023-05-04Minutes6.1 MiB2023-05-10Login
IG03 SIG06 Lift control2023-06-07Minutes566 KiB2023-06-21Login
IG03 SIG06 Lift control2024-03-20Minutes2.0 MiB2024-03-26Login
SIG measuring devices2016-05-09Minutes111 KiB2017-07-18Login
Workshop: Measuring devices and closed-loop controls2023-02-07Minutes14.9 MiB2023-04-25Login
IG03 SIG04 Measuring devices2023-05-25Minutes226 KiB2023-07-17Login
IG03 SIG04 Measuring devices2023-08-07Minutes124 KiB2023-08-24Login
IG03 SIG04 Measuring devices2023-10-12Minutes124 KiB2023-11-15Login
SIG motion control2016-01-20Minutes872 KiB2017-07-18Login
SIG motion control2016-06-08Minutes143 KiB2017-07-18Login
SIG motion control2016-07-12Minutes228 KiB2017-07-18Login
SIG motion control2018-04-16Minutes1.7 MiB2018-04-18Login
SIG drives and motion control2018-05-17Minutes150 KiB2018-05-23Login
SIG drives and motion control2018-06-18Minutes155 KiB2018-06-25Login
SIG drives and motion control2018-07-17Minutes698 KiB2018-07-23Login
SIG drives and motion control2018-10-09Minutes434 KiB2018-10-15Login
SIG drives and motion control2018-11-20Minutes1.0 MiB2018-11-21Login
SIG drives and motion control2019-01-17Minutes134 KiB2019-01-21Login
SIG drives and motion control2019-02-20Minutes134 KiB2019-02-25Login
SIG drives and motion control2019-03-25Minutes136 KiB2019-03-26Login
SIG drives and motion control2019-04-29Minutes147 KiB2019-04-30Login
SIG drives and motion control2019-05-10Minutes146 KiB2019-05-16Login
SIG drives and motion control2019-06-04Minutes3.2 MiB2019-06-11Login
SIG drives and motion control2019-07-11Minutes4.9 MiB2019-07-12Login
IG profiles SIG drives and motion control2019-08-13Minutes130 KiB2019-09-04Login
IG profiles SIG drives and motion control2019-09-24Minutes128 KiB2019-10-15Login
IG profiles SIG drives and motion control2019-10-11Minutes14.8 MiB2019-10-15Login
SIG drives and motion control2019-10-25Minutes447 KiB2019-10-29Login
SIG drives and motion control2019-11-05Minutes5.8 MiB2019-11-06Login
SIG drives and motion control2019-12-10Minutes189 KiB2019-12-17Login
SIG drives and motion control2020-01-21Minutes185 KiB2020-01-23Login
SIG drives and motion control2020-02-24Minutes115 KiB2020-02-24Login
SIG drives and motion control2020-04-03Minutes104 KiB2020-04-03Login
SIG drives and motion control2020-04-23Minutes234 KiB2020-04-27Login
SIG drives and motion control2020-05-27Minutes240 KiB2020-06-08Login
SIG drives and motion control2020-07-02Minutes271 KiB2020-07-03Login
SIG drives and motion control2020-07-27Minutes106 KiB2020-07-27Login
SIG drives and motion control2020-09-09Minutes421 KiB2020-09-10Login
SIG drives and motion control2020-09-15Minutes364 KiB2020-09-17Login
SIG drives and motion control2020-09-22Minutes601 KiB2020-09-23Login
SIG drives and motion control2020-09-29Minutes80 KiB2020-10-08Login
SIG drives and motion control2020-11-03Minutes1.2 MiB2020-11-05Login
SIG drives and motion control2020-12-02Minutes152 KiB2020-12-03Login
SIG drives and motion control2021-01-19Minutes535 KiB2021-01-26Login
SIG drives and motion control2021-03-09Minutes148 KiB2021-03-12Login
SIG drives and motion control2021-04-13Minutes76 KiB2021-04-14Login
SIG drives and motion control2021-05-10Minutes81 KiB2021-05-11Login
SIG drives and motion control2021-06-15Minutes1.0 MiB2021-06-18Login
SIG drives and motion control2021-07-15Minutes753 KiB2021-07-16Login
SIG drives and motion control2021-07-23Minutes207 KiB2021-08-06Login
SIG drives and motion control2021-09-14Minutes1.0 MiB2021-09-15Login
SIG drives and motion control2021-11-18Minutes182 KiB2021-11-19Login
SIG drives and motion control2022-01-24Minutes167 KiB2022-01-26Login
SIG drives and motion control2022-02-21Minutes668 KiB2022-02-22Login
SIG municipal vehicles2012-09-13Minutes106 KiB2017-09-22Login
SIG municipal vehicles2015-03-10Minutes6.7 MiB2017-09-22Login
SIG municipal vehicles2015-07-02Minutes1.1 MiB2017-09-22Login
SIG municipal vehicles2017-09-21Minutes280 KiB2017-09-22Login
SIG municipal vehicles2017-10-23Minutes1.7 MiB2017-10-30Login
SIG municipal vehicles2017-12-08Minutes137 KiB2017-12-12Login
SIG municipal vehicles2018-01-29Minutes558 KiB2018-02-21Login
SIG municipal vehicles2018-03-02Minutes208 KiB2018-03-05Login
SIG municipal vehicles2018-05-29Minutes107 KiB2018-06-29Login
SIG municipal vehicles2019-04-30Minutes8.6 MiB2019-05-02Login
SIG municipal vehicles2019-05-28Minutes124 KiB2019-06-11Login
SIG municipal vehicles2020-04-23Minutes120 KiB2020-10-01Login
SIG municipal vehicles2021-04-22Minutes757 KiB2021-04-30Login
SIG municipal vehicles2021-09-02Minutes710 KiB2021-09-08Login
SIG municipal vehicles2023-05-11Minutes484 KiB2023-05-17Login
IG03 SIG11 Municipal vehicles2023-05-30Minutes332 KiB2023-06-02Login
SIG power supply2009-12-14Minutes692 KiB2017-07-18Login
SIG special car add-on devices2016-11-29Minutes16.4 MiB2017-07-17Login
SIG special car add-on devices2016-09-13Minutes130 KiB2017-07-17Login
SIG special car add-on devices2016-03-08Minutes143 KiB2017-07-17Login
TF police2016-06-15Minutes135 KiB2017-07-17Login
TF taxi2016-07-28Minutes259 KiB2017-07-17Login
TF taxi2016-04-19Minutes124 KiB2017-07-17Login
SIG special car add-on devices2017-10-11Minutes130 KiB2018-04-09Login
SIG special car add-on devices2018-07-18Minutes310 KiB2018-07-19Login
SIG special car add-on devices2022-10-12Minutes8.6 MiB2022-11-15Login
SIG special car add-on2022-11-28Minutes7.1 MiB2022-12-15Login
SIG truck gateway2007-01-22Minutes82 KiB2017-07-18Login
SIG truck gateway2021-01-25Minutes1.7 MiB2021-02-03Login
SIG truck gateway2021-02-25Minutes1.0 MiB2021-03-01Login
SIG truck gateway2021-06-15Minutes4.3 MiB2021-06-25Login
IG profiles SIG truck gateway2021-10-05Minutes1.0 MiB2021-10-12Login
IG profiles SIG truck gateway2022-01-26Minutes103 KiB2022-02-04Login
IG profiles SIG truck gateway2022-10-12Minutes87 KiB2022-11-08Login
SIG truck gateway2023-01-11Minutes65 KiB2023-01-24Login
SIG weighing devices and systems2016-02-03Minutes138 KiB2017-07-17Login
SIG weighing devices and systems2016-03-15Minutes122 KiB2017-07-17Login
SIG weighing devices and systems2016-04-18Minutes118 KiB2017-07-17Login
SIG weighing devices and systems2016-07-13Minutes134 KiB2017-07-17Login
SIG weighing devices and systems2016-07-26Minutes518 KiB2017-07-17Login
SIG weighing devices and systems2016-08-31Minutes407 KiB2017-07-17Login
SIG weighing devices and systems2016-09-28Minutes121 KiB2017-07-17Login
SIG weighing devices and systems2016-12-14Minutes110 KiB2017-07-17Login
SIG weighing devices and systems2017-01-24Minutes118 KiB2017-07-17Login
SIG weighing devices and systems2018-05-03Minutes144 KiB2018-05-04Login
SIG weighing devices and systems2019-08-22Minutes341 KiB2019-09-09Login
SIG weighing devices and systems2019-09-25Minutes1.0 MiB2019-09-27Login
SIG weighing devices2019-10-29Minutes131 KiB2019-10-30Login
SIG weighing devices2019-11-12Minutes579 KiB2019-11-14Login
SIG weighing devices2019-12-03Minutes210 KiB2019-12-05Login
SIG weighing devices2020-01-17Minutes739 KiB2020-01-20Login
SIG weighing devices2020-02-10Minutes208 KiB2020-02-12Login
SIG weighing devices2020-03-03Minutes104 KiB2020-03-05Login
SIG weighing devices2021-11-11Minutes548 KiB2021-11-15Login

Specifications

Title Details
Status
Size
Published
Action
CiA 401-B version 1.0.0.I/O device profile - Part B: Functional behavior and parameters
DescriptionThis document specifies the functional behavior and parameters of generic analog and digital input and output devices. Additionally, AnnexA specifies the functional behavior and parameters of specific analog and digital input and output devices such as joysticks.
Keywordsn/a
DSP3.1 MiB2023-06-19Login
CiA 401-C version 1.0.0I/O device profile - Part C: Mapping to classic CANopen
Descriptionn/a
Keywordsn/a
DSP719 KiB2023-06-19Login
CiA 401-F version 1.0.0I/O device profile - Part F: Mapping to CANopen FD
Descriptionn/a
Keywordsn/a
DSP586 KiB2023-06-19Login
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
PAS1.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
PAS494 KiB2013-02-12Login
CiA 402-2 version 4.1.15CANopen device profile drives and motion control - Part 2: Operation modes and application data
Descriptionn/a
Keywordsn/a
WD4.1 MiB2022-04-13Login
CiA 402-4 version 1.0.3CANopen device profile for drives and motion control- Part 4: Safety functionality
Descriptionn/a
Keywordsn/a
WD3.2 MiB2022-04-13Login
CiA 402-5 version 1.0.3CANopen device profile for drives and motion control - Part 5: PDO mapping superset
Descriptionn/a
Keywordsn/a
WD434 KiB2022-04-13Login
CiA 402-6 version 1.0.7CANopen drives and motion control device profile - Part 6: CANopen FD PDO mapping
Descriptionn/a
Keywordsn/a
WD1.0 MiB2022-04-13Login
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
DSP783 KiB2016-10-10Login
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
DSP3.2 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
DSP395 KiB2014-01-31Login
CiA 402-1 version 5.0.0CANopen device profile for drives and motion control - Part 1: General definitions
DescriptionThis document provides general definitions on functional elements of power drive systems. It also defines application modes such as for torque, velocity, and position control.
Keywordsn/a
DSP365 KiB2023-12-05Login
CiA 402-2 version 5.0.0CANopen device profile drives and motion control - Part 2: Operation modes and application data
DescriptionThis document specifies the basic drive functional behavior and additional application functional elements as given in IEC 61800-7-201. This includes the specification of drive operation modes and application data for power drive systems such 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. The document specifies the PDS finite state automaton (FSA), which can be controlled externally by a control device communicating via a CAN-based network. NOTE This document specifies some differences compared with IEC 61800-7-201:2015, which are not yet introduced in the IEC standard.
Keywordsn/a
DSP4.0 MiB2024-02-06Login
CiA 402-3 version 5.0.0CANopen device profile for drives and motion control - Part 3: PDO mapping
DescriptionThis document specifies CANopen PDO communication and mapping parameters power drive devices. In addition, this document specifies the PDO mapping attributes for communication and application parameters.
Keywordsn/a
DSP1.3 MiB2024-02-06Login
CiA 404-2 version 2.0.0CANopen 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: • Part 1 defines the generic objects and the generic PDO mapping • Part 2 defines the EUROMAP specific parameters This part specifies the additional objects needed for EUROMAP 75 measuring amplifiers parameters and EUROMAP 66 heating/cooling device parameters.
Keywordsn/a
DSP441 KiB2013-08-01Login
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
DSP3.1 MiB2016-07-19Login
CiA 404-B version 0.0.1Profile for measuring devices and closed-loop controllers Part B: Functional behaviour and application parameters
Descriptionn/a
Keywordsn/a
WDP2.5 MiB2023-09-19Login
CiA 404-C version 0.0.1Profile for measuring devices and closed-loop controllers Part C: CANopen mapping
Descriptionn/a
Keywordsn/a
WDP312 KiB2023-09-19Login
CiA 404-F version 0.0.1Profile for measuring devices and closed-loop controllers Part F: CANopen FD mapping
Descriptionn/a
Keywordsn/a
WDP305 KiB2023-09-19Login
CiA 406-B version 1.0.0Encoder device profile - Part B: Functional behavior and parameters
DescriptionThis document specifies the functional behavior as well as 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. This includes encoder output process values such as position, speed, acceleration and jerk, and encoder CAM parameters. Additionally, safety-related parameters such as safety position and safety speed for encoders are specified. The mapping into Process Data Objects (PDO), Safety-related Data Objects (SRDO), and Parameter Groups (PG) is not in the scope of this document.
Keywordsn/a
DSP1.6 MiB2022-12-07Login
CiA 406-J version 1.2.0Encoder device profile - Part J: Mapping to J1939
DescriptionThis document specifies the mapping of CiA 406-B process data into J1939 parameter groups. This includes the specification of parameter groups and the configuration by means of the CAM11 and CAM21 parameter groups specified in the CiA 510 document.
Keywordsn/a
DSP263 KiB2022-12-07Login
CiA 406-C version 1.0.0Encoder device profile - Part C: CANopen mapping
DescriptionThis document specifies the CANopen communication and mapping parameters for encoders compliant with the CiA 406-B specification. This includes the PDO mapping and the optional SRDO mapping.
Keywordsn/a
DSP753 KiB2022-12-07Login
CiA 406-F version 1.0.0Encoder device profile - Part F: CANopen FD mapping
DescriptionThis document part specifies the CANopen FD communication and mapping parameters for encoders compliant with the CiA 406-B specification. This includes the PDO mapping.
Keywordsn/a
DSP492 KiB2022-12-07Login
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
DS2.1 MiB2022-12-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
PAS2.8 MiB2005-01-01Login
CiA 408 version 2.1.2CANopen device profile for fluid power technology proportional valves and hydrostatic transmissions
Descriptionn/a
Keywordsn/a
WD5.9 MiB2020-11-05Login
CiA 408-C version 2.1.6Fluid power technology device profile - Part C: CANopen mapping
Descriptionn/a
Keywordsn/a
WD432 KiB2022-01-27Login
CiA 408-B version 2.1.8Fluid power technology device profile - Part B: Functional device description and parameter
Descriptionn/a
Keywordsn/a
WD4.6 MiB2022-01-27Login
CiA 408 version 2.1.0CANopen device profile for fluid power technology
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
DSP5.9 MiB2021-01-23Login
Profile Fluid Power Technology version 1.6.3Proportional Valves and Hydrostatic Transmissions
Descriptionn/a
Keywordsn/a
DSP872 KiB2017-05-09Login
CiA 408-F version 1.0.0 Fluid power technology device profile - Part F: CANopen FD mapping
DescriptionThis document specifies the mapping of data objects specified in CiA 408-B to CANopen FD communication objects, especially PDO communication and mapping parameters. Additionally, this document provides requirements and recommendations for the implementation of the lower CAN layers.
Keywordsn/a
DSP845 KiB2024-03-19Login
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
PAS457 KiB2010-02-23Login
CiA 410-J version 1.1.0Inclinometer device profile - Part J: Mapping to J1939
DescriptionThis document specifies the mapping of CiA 410 process data into J1939 parameter groups. This includes the specification of parameter groups and the configuration by means of the CAM11 and CAM21 parameter groups specified in the CiA 510 specification.
Keywordsn/a
DSP214 KiB2020-12-01Login
CiA 410-B version 1.0.0Inclinometer device profile - Part B: Functional behavior and parameters
DescriptionThis document specifies the functional behavior as well as application parameters for inclinometers. The mapping into Process Data Objects (PDO), Safety-related Data Objects (SRDO), and Parameter Groups (PG) is not in the scope of this document.
Keywordsn/a
DSP709 KiB2024-01-16Login
CiA 410-C version 1.0.0Inclinometer device profile - Part C: CANopen CC mapping
DescriptionThis document specifies the CANopen CC communication and mapping parameters for inclinometers compliant with the CiA 410-B specification. This includes the PDO mapping and the optional SRDO mapping.
Keywordsn/a
DSP618 KiB2024-01-16Login
CiA 410-F version 1.0.0Inclinometer device profile - Part F: CANopen FD mapping
DescriptionThis document specifies the CANopen FD communication and mapping parameters for inclinometers compliant with the CiA 410-B specification. This includes the PDO mapping.
Keywordsn/a
DSP384 KiB2024-01-16Login
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
PAS167 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
PAS1.3 MiB2005-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
PAS2.0 MiB2008-08-27Login
CiA 413-3 version 3.0.1CANopen interface profile for truck gateways - Part 3: Other than brake and running gear devices
Descriptionn/a
Keywordsn/a
WD484 KiB2022-01-25Login
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
DSP335 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
DSP2.1 MiB2011-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
DSP3.0 MiB2011-11-24Login
CiA 413-5 version 1.0.0CANopen interface profile for truck gateways - Part 5: Application data 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
DSP589 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
DSP219 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
DSP410 KiB2011-11-24Login
CiA 413-1 version 3.0.0CANopen interface profile for commercial in- vehicle gateways Part 1: General definitions
Descriptionn/a
Keywordsn/a
WD239 KiB2023-01-04Login
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
PAS167 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
PAS518 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).
Keywordsn/a
DSP1.9 MiB2009-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
DSP670 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
DSP361 KiB2007-08-28Login
CiA 416-3 version 2.0.0CANopen application profile for building door control - Part 3: Pre-defined communication objects and application data objects
DescriptionThis part of the application profile pre-defines the application objects of the physical and virtual devices in detail
Keywordsn/a
DSP3.6 MiB2007-08-28Login
CiA 417-3 version 2.2.4CANopen application profile for lift control systems – Part 3-1: Pre-defined PDOs for lift application 1
Descriptionn/a
Keywordsn/a
WD1.6 MiB2022-02-25Login
CiA 417-2 version 2.3.4CANopen application profile for lift control systems – Part 2: Virtual device definitions
Descriptionn/a
Keywordsn/a
WD1.2 MiB2022-02-25Login
CiA 417-1 version 2.3.4CANopen application profile for lift control systems – Part 1: General definitions
Descriptionn/a
Keywordsn/a
WD372 KiB2022-02-25Login
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: • 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 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
PAS417 KiB2011-02-02Login
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
DSP423 KiB2018-12-10Login
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: • 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 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
PAS470 KiB2011-02-02Login
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.1 MiB2018-12-10Login
CiA 417-3-1 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: • 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 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
PAS1.3 MiB2011-02-02Login
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.1 MiB2018-02-02Login
CiA 417-4 version 2.0.0CANopen application profile for lift control systems - Part 4: Detailed application data objects
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: • 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 parameter, and diagnostic information represented in the object dictionary for the lift 1 application.
Keywordsn/a
PAS1.9 MiB2011-02-02Login
CiA 417-4 version 2.3.0CANopen application profile for lift control systems - Part 4: Detailed application data objects
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
DSP3.6 MiB2018-11-22Login
CiA 417-4 version 2.3.5CANopen application profile for lift control systems, Part 4: Detailed application object specification
Descriptionn/a
Keywordsn/a
WD3.9 MiB2023-06-07Login
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
PAS716 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
PAS474 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 communication objects. It also specifies the CANopen functions of the manager-extruder.
Keywordsn/a
PAS657 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: 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 puller downstream device.
Keywordsn/a
PAS475 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
PAS435 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
PAS438 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
PAS487 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
PAS556 KiB2015-05-07Login
CiA 421-1 version 1.0.3CANopen Application profile for train vehicle control networks - Part 1: General definitions
Descriptionn/a
Keywordsn/a
WD690 KiB2008-01-29Login
CiA 421-10 version 1.0.0CANopen application profile for train vehicle control systems - 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
DSP452 KiB2008-08-18Login
CiA 421-5 version 1.0.0CANopen application profile for train vehicle control systems - 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.8 MiB2006-08-18Login
CiA 421-12 version 1.0.0CANopen application profile for train vehicle control systems - 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
DSP549 KiB2006-08-18Login
CiA 421-11 version 1.0.0CANopen application profile for train vehicle control systems - 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
DSP350 KiB2006-08-18Login
CiA 421-9 version 1.0.0CANopen application profile for train vehicle control systems - Part 9: Vehicle linkage system
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
DSP354 KiB2008-04-17Login
CiA 421-4 version 1.0.0CANopen application profile for train vehicle control systems - 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
DSP504 KiB2006-08-18Login
CiA 421-1 version 1.0.0CANopen application profile for train vehicle control systems - 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
DSP409 KiB2006-08-18Login
CiA 422-4 version 2.1.1CANopen application profile for municipal vehicles - Part 4: Application objects
Descriptionn/a
Keywordsn/a
WD2.7 MiB2021-07-16Login
CiA 422-3-3 version 2.1.2CANopen application profile for municipal vehicles - Part 3-3: Pre-defined SDOs
Descriptionn/a
Keywordsn/a
WD0.9 MiB2021-07-16Login
CiA 422-3-2 version 2.1.1CANopen application profile for municipal vehicles - Part 3-2: Pre-defined RPDOs
Descriptionn/a
Keywordsn/a
WD4.8 MiB2021-07-16Login
CiA 422-3-1 version 2.1.1CANopen application profile for municipal vehicles - Part 3-1: Pre-defined TPDOs
Descriptionn/a
Keywordsn/a
WD5.1 MiB2021-07-16Login
CiA 422-2 version 2.1.1CANopen application profile for municipal vehicles - Part 2: Virtual device functionality
Descriptionn/a
Keywordsn/a
WD640 KiB2021-07-16Login
CiA 422-1 version 2.1.1CANopen application profile for municipal vehicles - Part 1: General definitions
Descriptionn/a
Keywordsn/a
WD567 KiB2021-07-16Login
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
DSP577 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
DSP641 KiB2018-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
DSP4.2 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.8 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
DSP2.2 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
DSP644 KiB2018-12-20Login
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
DSP242 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
DSP283 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
DSP508 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
DSP284 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
DSP1.3 MiB2006-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
DSP628 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
DSP413 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
DSP1.0 MiB2006-08-18Login
CiA 423-5 version 1.0.0CANopen application profile for rail vehicles 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
DSP313 KiB2006-08-18Login
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. The set of specifications is organized as follows: Part 1: General definitions, Part 2: Traction controller, Part 3: Diesel engine control unit, Part 4: Transmission control unit, Part 5: Speed sensor unit, Part 6: Diesel engine safety control unit, Part 7: Diesel engine signal control unit, Part 8: Clutch control unit, Part 9: Gear control unit, Part 10: Particle filter control unit, Part 11: Starter unit, Part 12: Oil refill tank unit. Devices compliant to this application profile uses communication techniques, which conform to those described in the CiA Draft Standard 301.
Keywordsn/a
DSP156 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
DSP470 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
DSP441 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.
Keywordsn/a
DSP353 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
DS447 KiB2011-06-03Login
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.6 MiB2011-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
DSP1.8 MiB2017-11-17Login
CiA 425-2 version 2.2.0 CANopen application profile for medical diagnostic add-on modules Part 2: Injector (Corrigendum 1)
Descriptionn/a
Keywordsn/a
DS157 KiB2012-05-02Login
CiA 425-2 version 2.4.3CANopen application profile for medical diagnostic add-on modules Part 2: Injector
Descriptionn/a
Keywordsn/a
WD1.6 MiB2023-05-24Login
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
DSP440 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
DSP429 KiB2006-08-18Login
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
DSP364 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
DSP268 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
DSP317 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
DSP294 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
DSP267 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
DSP366 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
DSP495 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
DSP304 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
DSP241 KiB2006-08-18Login
CiA 433-3 version 1.0.0CANopen application profile for rail vehicle interior lighting control - Part 3: Lighting unit
DescriptionThis part of the CANopen application profile for rail vehicle interior lighting control describes the interior lighting unit.
Keywordsn/a
DSP343 KiB2006-08-18Login
CiA 433-2 version 1.0.0CANopen application profile for rail vehicle interior lighting control - Part 2: Lighting controller
DescriptionThis part of the CANopen application profile for rail vehicle interior lighting control describes the interior lighting controller.
Keywordsn/a
DSP324 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
DSP213 KiB2006-08-18Login
CiA 434-3 version 1.0.0CANopen profiles for laboratory automation systems - Part 3: 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
DSP531 KiB2010-06-30Login
CiA 434-2 version 1.0.0CANopen profiles for laboratory automation systems - Part 2: 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
DSP1.1 MiB2010-06-30Login
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 commander/responder-based communication between a laboratory automation controller (LAC) and several laboratory automation unit(s) (LAU). 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 controller can control the laboratory units via single operating commands. On the other hand this part provides a generic structure for a “pre-configurable work plan” that enables a quasi-autonomous laboratory unit operation, which is monitored by the laboratory controller. 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
DSP1.1 MiB2009-04-22Login
CiA 436-1 version 1.1.0CANopen application profile for construction machines - 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
DSP530 KiB2010-06-30Login
CiA 437-1 version 1.1.0CANopen application profile for grid-based photovoltaic systems - Part 1: General definitions
DescriptionThis document specifies the CAN-related physical layer, the general system architecture, and some common CiA 301 communication parameter objects. It also defines, which process data and parameters are used by the virtual devices specified for grid-based photovoltaic systems
Keywordsn/a
DSP784 KiB2024-01-09Login
CiA 437-2 version 1.1.0CANopen application profile for grid-based photovoltaic systems - Part 2: Pre-defined communication objects
DescriptionThis document specifies default communication objects and general communication parameters for CANopen devices in grid-based photovoltaic systems.
Keywordsn/a
DSP305 KiB2024-01-09Login
CiA 437-3 version 2.0.1CANopen application profile for grid-based photovoltaic systems - Part 3: Profile data objects
DescriptionThis document specifies in detail the process data and parameters of the virtual devices defined for use in grid-based photovoltaic systems.
Keywordsn/a
DSP4.0 MiB2024-02-27Login
CiA 442 version 1.1.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 starters, and motor management starters. The specification is functional compatible with the international standard IEC 61915-2
Keywordsn/a
DS495 KiB2022-05-02Login
CiA 443 version 4.0.0CANopen profile for SIIS level-2 devices
DescriptionThis document specifies the CANopen interface for SIIS level-2 devices. This includes instruments and actuators for subsea measurement systems. The specification of the SIIS level-2 application manager is not in the scope of this document.
Keywordsn/a
DSP2.5 MiB2022-11-18Login
CiA 443 version 4.0.1CANopen profile for SIIS level-2 devices
Descriptionn/a
Keywordsn/a
WD2.5 MiB2024-01-18Login
CiA 444-1 version 2.0.2CANopen profiles for container-handling machine add-on devices - Part 1: General definitions
DescriptionThis document specifies the physical layer, and some general CANopen communication parameter objects.
Keywordsn/a
DS276 KiB2022-05-02Login
CiA 444-2 version 2.0.1CANopen profiles for container-handling machine add-on devices - Part 2: Spreader for crane
DescriptionThis document specifies the device profile for crane spreaders including process data and process data objects.
Keywordsn/a
DS1.0 MiB2022-05-02Login
CiA 444-3 version 2.0.1CANopen profile for container-handling machine add-on devices - Part 3: Spreader for straddle carrier
DescriptionThis document specifies the device profile for straddle carrier spreaders including process data and process data objects.
Keywordsn/a
DS1.0 MiB2022-04-12Login
CiA 445 version 1.1.0CANopen device profile for RFID devices
DescriptionThis document specifies the CANopen interface for simple and sophisticated radio frequency identification (RFID) devices. This includes the specification of the physical layer, the data link layer, and the application layer as well as the specification of process data, configuration parameters, and diagnostic information. This includes commands and possibilities to control an RFID reader via the CANopen network.
Keywordsn/a
DS1.3 MiB2022-04-29Login
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
DSP1.2 MiB2006-11-06Login
CiA 447-3 version 2.1.3CANopen application profile for special-purpose car add-on devices - Part 3: Application data objects
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
DSP4.1 MiB2018-09-07Login
CiA 447-5 version 1.0.0CANopen application profile for special-purpose car add-on devices - Part 5: Conformance test plan
DescriptionThis document specifies the application profile specific tests for CiA 447 devices. The tests include: Electronic data sheet-based verification of object dictionary entries; Application profile specific tests for power management, Layer Settings Services and Network Management States; Dynamic tests covering message timings and stress tests; Integration tests based on post analysis of trace recordings; Virtual device specific function tests. The document also references the test cases specified in the CiA 310 CANopen conformance test plan.
Keywordsn/a
DSP1.9 MiB2017-01-13Login
CiA 447-2 version 2.1.3CANopen application profile for special-purpose car add-on devices - Part 2: Virtual device definitions
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
DSP431 KiB2018-09-07Login
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
DSP1.2 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
DSP490 KiB2015-12-14Login
CiA 450 version 1.0.1CANopen 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
DS3.7 MiB2022-07-22Login
CiA 452 version 1.1.0CANopen device profile for PLCopen motion control
DescriptionThis document specifies the classic CANopen interface controlling PLCopen drives by means of one RPDO (receive process data object) and one TPDO (transmit process data object). This includes the parameter (objects) used for PLCopen-specific modes supporting gear, jog, and camming functions. Objects specified in IEC 61800-7-201 are referenced in the Annex A.
Keywordsn/a
DS828 KiB2022-08-10Login
CiA 453 version 1.1.3CANopen device profile power supply
Descriptionn/a
Keywordsn/a
WD1.7 MiB2018-02-23Login
CiA 453 version 1.1.4CANopen device profile for power supplies
Descriptionn/a
Keywordsn/a
WD2.1 MiB2021-06-30Login
CiA 453 version 2.0.0CANopen device profile for power supplies
DescriptionThis CiA profile specification is suitable for programmable and non-programmable power- supply devices with single or multiple outputs that are voltage-, current-, or power-controlled. It is intended for CANopen communication interfaces of AC/AC, DC/DC, AC/DC, and DC/AC converters.
Keywordsn/a
DS2.1 MiB2022-02-09Login
CiA 454-14 version 1.0.0CANopen application profile for energy management systems - Part 14: Load unit
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 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
DSP453 KiB2014-06-17Login
CiA 454-7 version 1.0.0CANopen application profile for energy management systems - Part 7: Drive control unit
DescriptionThis document specifies application objects provided by the drive control unit, as typically utilized in light electric vehicles.
Keywordsn/a
DSP665 KiB2021-04-06Login
CiA 454-2 version 2.0.0CANopen application profile for energy management systems - Part 2: Pre-defined communication parameters and general application objects
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 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
DSP2.0 MiB2014-06-17Login
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.5 MiB2014-06-17Login
CiA 454-13 version 1.0.0CANopen application profile for energy management systems - Part 13: Generator unit
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 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
DSP533 KiB2014-06-17Login
CiA 454-5 version 2.0.0CANopen application profile for energy management systems - Part 5: Voltage converter
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 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
DSP2.0 MiB2014-06-17Login
CiA 454-9 version 1.0.0CANopen application profile for energy management systems - Part 9: HMI unit
DescriptionThis document specifies application objects provided or indicated by human machine interface units, as typically utilized in light electric vehicles. This comprises human machine interface units, managing data for signalling, travelling, battery systems, inputs for energy management user condition and state, motion and diagnostics.
Keywordsn/a
DSP283 KiB2021-04-06Login
CiA 454-6 version 2.0.0CANopen application profile for energy management systems - Part 6: Battery pack
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 6 of the CANopen application profile for EMSs. Part 6 of the document specifies application objects provided by the battery pack.
Keywordsn/a
DSP1.3 MiB2014-06-17Login
CiA 454-3 version 3.0.0CANopen application profile for energy management systems - Part 3: PDO communication
DescriptionThis document specifies the PDO communication and mapping parameters.
Keywordsn/a
DSP1.0 MiB2021-04-06Login
CiA 454-4 version 2.0.0CANopen application profile for energy management systems - Part 4: EnergyBus controller
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 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
DSP337 KiB2014-06-17Login
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
DSP1.7 MiB2010-06-30Login
CiA 456 version 1.0.0CANopen interface profile for configurable network components
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
DSP457 KiB2012-07-11Login
CiA 457 version 1.1.0CANopen interface profile wireless transmission
DescriptionThis document specifies the CANopen interface profile for devices providing a gateway function to wireless transmission media ports.
Keywordsn/a
DS728 KiB2022-08-09Login
CiA 458 version 1.0.1CANopen 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
DS780 KiB2022-05-19Login
CiA 459-1 version 1.0.1CANopen profile for on-board weighing devices - Part 1: General specification and functional overview
DescriptionThis document provides general definitions and specifies the data link and the physical layer interface for on-board weighing devices. Additionally, it specifies the CANopen application layer functionality. It also describes the device’s operational principles and defines device classes.
Keywordsn/a
DS510 KiB2022-08-09Login
CiA 459-2 version 1.0.1CANopen profile for on-board weighing devices - Part 2: Communication parameters
DescriptionThis document specifies the mandatory and recommended communication parameters, as well as the parameter sets for the PDO communication.
Keywordsn/a
DS249 KiB2022-08-09Login
CiA 459-3 version 1.0.1CANopen profile for on-board weighing devices - Part 3: Application data objects
DescriptionThis document specifies the application parameters (process, diagnostic, and configuration data) of the on-board weighing devices. It also specifies profile-specific data types.
Keywordsn/a
DS1.0 MiB2022-08-09Login
CiA 460 version 1.0.0CANopen profile for service robot control systems
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
DSP321 KiB2012-02-10Login
CiA 462 version 1.1.0CANopen profile for item detection devices
DescriptionThis document 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
DS1.7 MiB2023-06-27Login
CiA 463-B version 1.0.0Device profile for IO-Link gateway - Part B: 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
DS719 KiB2019-06-27Login
CiA 463-C version 1.0.0Device profile for IO-Link gateway - Part C: 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
DS354 KiB2019-06-27Login
CiA 463-F version 1.0.0Device profile for IO-Link gateway — Part F: 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
DS335 KiB2019-06-26Login
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-4 version 1.0.0CANopen profile conformance test plans - Part 4: Contrast media injector
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 add-on 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
DSP2.0 MiB2009-01-16Login
CiA 312-7 version 1.0.0CANopen profile conformance test plans - Part 7: Pedelec Profile 1
DescriptionThis document provides the conformance test specification for devices implemented according to CiA 454, Part 1, 2, 3, 4, 5, and 6 version 2.0.
Keywordsn/a
DSP568 KiB2020-03-03Login
CiA 312-2 version 1.0.0CANopen profile conformance test plans - 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
DSP1.0 MiB2008-04-11Login
CiA 312-1 version 1.0.0CANopen profile conformance test plans - 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
DSP134 KiB2008-04-11Login