CiA® 422 series: CANopen application profile for municipal vehicles
The CANopen application profile CiA 422 specifies the so-called CleANopen embedded body control network for refuse collection vehicles. It defines the CANopen communication interfaces of several functional units (virtual devices) required for the control of the refuse collection application. The virtual device Body Controller (BC) controls the overall embedded system, which consists of CANopen devices that can host one or more virtual devices. The following virtual devices are specified by CiA 422:
- Body controller (BC)
- Body controller input/output unit (IOU)
- Bin classification unit (BCU)
- Container change unit (CCU)
- Compaction unit (CU)
- Crane unit (CRU)
- Footstep unit (FSU)
- GPS unit (GPSU)
- Identification unit (IDU)
- Input/output unit (IOU)
- Lifter unit (LU)
- Measuring unit (MU)
- Truck gateway unit (TGU)
- Washing unit (WU)
- etc.
The supported addressing schemes for lifter units allow a wide range of use cases to be accommodated, including single-compartment front, rear, or side loaders, with or without a combi comb, two-compartment rear and side loaders, and side loaders with additional single lifters.
Communication with the truck’s in-vehicle networks is considered via a truck gateway provided by the truck manufacturer. Some truck manufacturers even provide truck gateways compliant with CiA 413 or CiA 422, which would greatly facilitate system integration.
To meet the requirements arising from WELMEC, the latest edition of CiA 422 also provides rules for generating a 32-bit signature value based on information such as the measured value, tare value, net value, identifier, and time.
CiA has submitted the CiA 422-series (version 2) to the CEN (Comité Européen de Normalisation) for European standardization. It is published as EN 16815 standard (CleANopen - Application profile for municipal vehicles) since 2019.
| Title | Details | Published Size |
Status Action |
|---|---|---|---|
|
|
ScopeThis part of the CANopen application profile for municipal vehicles provides some general definitions of CleANopen and specifies the CAN physical layer as well as the error handling. |
2026-06-29 790 KB | DSP Login |
|
|
ScopeThis part of the CANopen application profile for municipal vehicles specifies the general communication parameters. 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). |
2026-06-29 690 KB | DSP Login |
|
|
ScopeThis part of the CANopen application profile for municipal vehicles specifies the communication and mapping parameter sets of the pre-defined RPDOs. |
2026-06-29 5 MB | DSP Login |
|
|
ScopeThis part of the CANopen application profile for municipal vehicles specifies the pre-defined additional SDO clients and servers. |
2026-06-29 898 KB | DSP Login |
|
|
ScopeThis part of the CANopen application profile for municipal vehicles specifies the values and value range attribute of the application objects. It specifies also the object and data type attributes of the application objects. |
2026-06-29 3 MB | DSP Login |
|
|
ScopeThis part of the CANopen application profile for municipal vehicles specifies the communication and mapping parameter sets of the pre-defined TPDOs. |
2026-06-29 6 MB | DSP Login |