CANopen SIG generic I/O modules

Scope

Enhancement and maintenance of the CANopen profile for generic I/O modules.

Chairmen

vacant

Group meetings

No events found.

Minutes

Title Date Status Size Published Action
SIG generic I/O2016-01-21Minutes370 KiB2017-07-18Login

Specifications

Title Details
Status
Size
Published
Action
CiA 401 version 3.0.0CANopen device profile for generic I/O modules
DescriptionThis specification represents the CANopen device profile for generic digital and analogue input and output modules. Devices compliant to this specification use communication techniques, which conform to those described in the CANopen application layer and communication profile specification. In addition, programmable I/O devices may use communication techniques, which conform to those described in the CANopen additional application layer functions. In the appendices, some specific I/O devices are defined.
Keywordsn/a
public1.0 MiB2008-06-03Login
CiA 401-1 version 3.1.0CANopen Profile for I/O devices – Part 1: Generic I/O modules
DescriptionThis CANopen profile specifies generic CANopen digital and analog input and output devices. Devices compliant to this specifications use communication techniques, which are conform to those described in the CANopen application layer and communication profile specification. In addition, programmable I/O devices may use communication techniques, which conform to those described in the CANopen additional application layer functions. This device profile specification consists of several parts: Part 1: Generic I/O devices, Part 2: Joysticks. This part of the device profile specifies the CANopen interface for modules with generic analog and digital inputs and outputs. The first default TPDO and RPDO support up to 64 digital inputs, respectively up to 64 digital outputs both grouped byte-wise. The remaining default PDOs transmit or receive up to 12 analog inputs respectively up to 12 analog outputs both with a 16-bit resolution. All TPDOs are triggered by change-of-state. Therefore, default TPDOs containing analog inputs are disabled. Besides the default byte-wise access to digital I/Os, optional bit-, word-, and double-word access may be supported. Besides the default 16-bit resolution for the analog I/Os, optional 8-bit, 32-bit, floating-point and manufacturer-specific resolutions may be supported. Several parameters are specified to configure the input and output behavior (e.g. trigger conditions for inputs, output behavior in case of internal device failures.
Keywordsn/a
DSP0.9 MiB2013-02-12Login
CiA 401-2 version 3.1.0CANopen profile for I/O devices – Part 2: Joysticks
DescriptionThis CANopen profile specifies generic CANopen digital and analog input and output devices. Devices compliant to this specifications use communication techniques, which conform to those described in the CANopen application layer and communication profile specification. In addition, programmable I/O devices may use communication techniques, which conform to those described in the CANopen additional application layer functions. This profile consists of several parts: Part 1: Generic I/O devices, Part 2: Joysticks. This part of the profile specifies the CANopen interface for joysticks and similar devices, e.g. foot-pedals.
Keywordsn/a
DSP219 KiB2013-02-12Login
CiA 312-1 version 1.0.0CANopen profile conformance test plan – Part 1: General definitions
DescriptionThe document contains additional lower-, dynamic- and upper tests for CANopen devices that shall be tested according to a certain device profile. The definitions of the generic lower-, dynamic- and upper tests do not fall in the scope of this document.
Keywordsn/a
DSP76 KiB2008-04-11Login
CiA 312-2 version 1.0.0CANopen profile conformance test plan – Part 2: Generic I/O modules
DescriptionThis part of CANopen device profile conformance test plan contains additional tests for generic I/O modules, which are tested for conformity according to CANopen device profile generic I/O modules. The additional tests verify entries in EDS and object dictionary, which are defined in CANopen device profile generic I/O modules. Furthermore additional test steps verify object coherences that are defined in that device profile. To achieve a certain level of conformity the CANopen device shall pass the corresponding tests defined in CANopen conformance test plan plus those defined in this part of the document series.
Keywordsn/a
DSP346 KiB2008-04-11Login
CiA 312-4 version 1.0.0CANopen profile conformance test plan – Part 4: Contrast media injectors
DescriptionThis part of the test plan specifies the additional tests for contrast media injectors, which shall be tested for conformity according to CANopen application profile for medical diagnostic addon modules (CiA 425-1 version 2.0. and CiA 425-2 version 2.0.2). The additional tests verify entries in EDS and object dictionary, which are defined in CANopen application profile for medical diagnostic add-on modules. Furthermore additional test steps verify the implementation of the device finite state automata and further object coherences, which are defined in application profile for medical diagnostic add-on modules. To achieve a certain level of conformity the DUT shall pass the corresponding tests defined in CANopen conformance test plan, CiA 312-1, plus those defined in this test plan.
Keywordsn/a
DSP0.9 MiB2009-01-16Login
CiA 312-4 version 1.0.1CANopen profile conformance test plan – Part 4: Contrast media injectors
Descriptionn/a
Keywordsn/a
WD1.5 MiB2012-05-20Login
CiA 312-5 version 0.0.4CANopen device profile conformance test plan - Part 5: Special purpose car add-on device
Descriptionn/a
Keywordsn/a
WD1.8 MiB2016-06-06Login
CiA 312-6 version 0.0.1CANopen device profile conformance test plan - Part 6: SIIS level-2 devices
Descriptionn/a
Keywordsn/a
WDP719 KiB2010-05-10Login
CiA 312-7 version 0.0.3CANopen conformance test plan - Part 7: Pedelec Profile 1
Descriptionn/a
Keywordsn/a
WD468 KiB2018-08-30Login
CiA 852 version 1.0.0CANopen recommended practice for CiA 401-based operator environment sub-systems
DescriptionThis document specifies the CANopen interface for operator environments with humanmachine interface functionality. It is based on the CiA 401 CANopen profile for generic I/O modules. Operator environments are for example simple remote control units, operator seats with integrated joysticks, foot pedals, pushbuttons, indicators, etc., and complete operator cabins. They are dedicated but not limited for construction, mining, agriculture and forestry machines, for harbor cranes, for boats and vessels, for wheelchairs and any other kind of machines on wheels.
Keywordsn/a
public485 KiB2012-06-21Login