CiA® 459 series: CANopen profile for on-board weighing devices
On-board weighing and overload protection is used for trucks, off-highway, or off-road vehicles. The CiA 459 series specifies the CANopen CC interface for such devices. It distinguishes three classes:
- Class 1: Devices are capable of monitoring the loaded vehicle weight, might be capable of monitoring the loaded axle weight, and provide monitored weighing data.
- Class 2: Devices are capable of performing non-LFT (legal-for-trade) transaction weighing and provide non-LFT transaction weighing data
- Class 3: Devices are capable of being fully certified as LFT and of performing LFT transaction weighing. Class 3 devices might additionally support the capabilities provided by class 1 and class 2 devices. The LFT capable device must have at least one alibi component: either alibi memory or an alibi printer.
On-board weighing devices with load-monitoring capability observe the total vehicle or trailer load and weigh optionally the load on a single axle or a group of axles. Devices supporting non-LFT and LFT transaction weighing store optionally the weighing data in an internal or external data storage device (DSD).
The on-board weighing device can perform load monitoring and transaction weighing at the same time. In case, the on-board weighing devices require switching between load monitoring modes and transaction modes, the switch is performed by setting the mode in the operating mode object. The on-board weighing device can provide the status of the on-going transaction weighing, when switched into transaction weighing, depending on the configured PDO mapping. It is highly recommended that transaction weighing data is read from the DSD or alibi memory whilst the device is in the NMT state pre-operational. An on-board weighing device uses one or more load cells to do the weight measuring. These load cells are either connected by means of discrete ports or serial interfaces such as sub-layered CANopen CC networks.
The CiA 459 series and the CiA 413 series are only available for members. CiA 459-1 provides general specifications and an overview of the functions. CiA 459-2 specifies the communication parameters including PDO mapping. CiA 459-3 defines in detail all process data and application configuration parameters.
Title | Details | Published Size |
Status Action |
---|---|---|---|
CiA 459-1 version 1.0.1 CANopen profile for on-board weighing devices - Part 1: General specification and functional overview |
ScopeThis 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. |
2022-08-09 511 KB | DS Login |
CiA 459-2 version 1.0.1 CANopen profile for on-board weighing devices - Part 2: Communication parameters |
ScopeThis document specifies the mandatory and recommended communication parameters, as well as the parameter sets for the PDO communication. |
2022-08-09 250 KB | DS Login |
CiA 459-3 version 1.0.1 CANopen profile for on-board weighing devices - Part 3: Application data objects |
ScopeThis document specifies the application parameters (process, diagnostic, and configuration data) of the on-board weighing devices. It also specifies profile-specific data types. |
2022-08-09 1,007 KB | DS Login |
CiA 413-1 version 3.0.0 CANopen interface profile for truck gateways - Part 1: General definitions |
ScopeThis 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 |
2011-11-24 335 KB | DSP Login |
CiA 413-2 version 3.0.0 CANopen interface profile for truck gateways - Part 2: Brake and running gear devices |
ScopeThis 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. |
2011-11-24 2 MB | DSP Login |
CiA 413-3 version 3.0.0 CANopen interface profile for truck gateways - Part 3: Other than brake and running gear devices |
ScopeThis 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 |
2011-11-24 3 MB | DSP Login |
CiA 413-5 version 1.0.0 CANopen interface profile for truck gateways - Part 5: Application data objects for superstructure |
ScopePart 5 of CANopen device profile for truck gateways defines the application objects for auperstructure. The normative references, definitions, acronyms, and abbreviations given in part 1 applies to this part, too. |
2003-12-31 589 KB | DSP Login |
CiA 413-6 version 1.0.0 CANopen interface profile for truck gateways - Part 6: Framework for J1939 parameter groups |
ScopePart 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. |
2003-12-31 219 KB | DSP Login |
CiA 413-8 version 1.0.0 CANopen interface profile for truck gateways - Part 8: Framework for HMI control |
ScopeThis 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. |
2011-11-24 410 KB | DSP Login |
CiA 413-3 version 3.0.1 CANopen interface profile for commercial in-vehicle gateways - Part 3: Other than brake and running gear devices |
ScopeThis document specifies the CANopen interface of an IVN gateway providing process data for other than brake and running gear equipment compliant with suspect parameters specified in ISO 11992-3. The CANopen interface is configurable by means of parameters specified in this document, in order to optimize the communication with the CANopen-connectable body application units (BAU). This allows forwarding of parameter groups received from the J1939-based IVN network and forwarding of CANopen application objects to the IVN network. |
2023-01-04 3 MB | WD Login |
CiA 413-1 version 3.0.1 CANopen interface profile for commercial in- vehicle gateways - Part 1: General definitions |
ScopeThis document specifies the physical layer including connectors, and some general communication parameters. There are no PDOs pre-defined |
2023-01-04 239 KB | WD Login |
CiA 301 version 4.2.0 CANopen application layer and communication profile |
ScopeThis specification specifies the CANopen application layer. This includes the data types, encoding rules and object dictionary objects as well as the CANopen communication services and protocols. In addition, this specification specifies the CANopen network management services and protocols. This specification specifies the CANopen communication profile, e.g. the physical layer, the pre- defined communication object identifier connection set, and the content of the Emergency, Time- stamp, and Sync communication objects. |
2011-02-21 3 MB | PAS Login |