IG03 Profiles

Scope

This document specifies the mapping of the Robotic technology component (RTC) finite state automaton to the CANopen network management (NMT) finite state automaton as well as the mapping of the RTC data types to CANopen data types. In addition, it describes the RTC - CANopen manager and the ProxyRTCs system integration.

Scope

The 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.

Scope

This 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

Scope

This 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

Scope

Part 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.

Scope

This 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.

Scope

The 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.

Scope

The CANopen sensor system application profile for road construction and earth moving machines specifies the communication interface for sensors as well as the sensor control unit. The profile is suitable for a broad range of machine types (e.g. paver, compactor, grader, dozer, mill, heater and truck). NOTE The first version of this profile has been jointly developed with the OSYRIS (Open System for Road Information Support) consortium (www.osyris.org) and the European Asphalt Pa vement Association (EAPA).

Scope

This part of the application profile gives an overview of the virtual devices.

Scope

This 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.

Scope

The 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 extruder-master.

Scope

The 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.

Scope

The 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.

Scope

This 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. The set of specifications is organized as follows: Part 1: General definitions; Part 2: Train operating system (TOS); Part 3: Monitoring and safety system (MSS); Part 4: Auxiliary operating system (AUX): Part 5: Power (drive) system (PDS); Part 6: Running gear system (RGS); Part 7: Brake control system (BCS); art 8: Ancillary operating system (ANC); Part 9: Vehicle linkage system (VLS); Part 10: Exterior lighting system (ELS); Part 11: Interior lighting system (ILS); Part 12: Door control system (DCS); Part 13: HVAC system (HS); Part 14: Passenger information system (PIS); Part 15: Cargo superstructure system (CSS); Part 16: Diagnostic system (DS); Part 17: Train-to-ground communication system (TCS); Part 18: Slip/slide control system (SCS). CANopen devices compliant to this application profile use communication techniques, which conform to those described in the CiA Draft Standard 301.

Scope

This 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.

Scope

This part of the CANopen application profile for rail vehicles describes the CANopen interface of the virtual interior lighting system.

Scope

Scope

This 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.

Scope

This part of the CANopen application profile for rail vehicle power drive systems describes the diesel engine control unit.

Scope

This part of the CANopen application profile for rail vehicle power drive systems describes the diesel engine safety control unit.

Scope

This 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.

Scope

This part of the CANopen application profile for rail vehicle power drive systems describes the starter unit.

Scope

This CANopen application profile defines the communication between virtual devices within a rail vehicle door control system. The rail vehicle door control system may be connected via a gateway device to the logical CANopen-based rail vehicle in-vehicle network. The set of specifications is organized as follows: • Part 1: General definitions; • Part 2: Door controller; • Part 3: Door unit. Devices compliant to this application profile shall use communication techniques, which conform to those described in the CiA Draft Standard 301.

Scope

This part of the CANopen application profile rail vehicle door control system describes the rail door controller.

Scope

This 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.

Scope

This 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.

Scope

This part of the CANopen application profile for rail vehicle auxiliary operating systems describes the power train cooling control unit .

Scope

This part of the CANopen application profile railway auxiliary operating system describes the power train cooling fan control unit.

Scope

This part of the CANopen application profile for rail vehicle auxiliary operating systems describes the hydrostatic signal interface unit.

Scope

This 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.

Scope

This part of the CANopen application profile for rail vehicle interior lighting control describes the interior lighting unit

Scope

This 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.

Scope

This application profile provides general definition as well as recommendations for using CANopen control networks on construction machineries. In addition, this applicat ion 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 co ntrol system for the superstructure respectively implement.

Scope

This document specifies default communication objects and general communication parameters for CANopen devices in grid-based photovoltaic systems.

Scope

This 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.

Scope

This document specifies the device profile for crane spreaders including process data and process data objects.

Scope

This 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.

Scope

This document specifies the CANopen interfaces for pump devices of the following types, based on VDMA 24223 series: - Generic pump; - Rotodynamic (liquid) pump. It specifies the object dictionary entries and the PDO mapping for both pump types.

Scope

This document specifies the CANopen communication and application parameters as well as the PDO mapping for power supplies and power converters.

Scope

This 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.

Scope

This document specifies the CANopen interface for energy measuring devices. This includes energy consumption as well as energy production, in particular for energy recovering.

Scope

This document specifies the mandatory and recommended communication parameters, as well as the parameter sets for the PDO communication.

Scope

This 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.

Scope

This documents describes the recommended practice and gives application hints for implementing the connection of crane and spreader compliant with the CiA 444-1 and CiA 444-2 specifications.

Scope

This document recommends how to implement a CiA 413 gateway interface for truck-mounted cranes, multi-lifts, and aerial working platforms. Besides some general recommendations regarding the CANopen interface, it recommends Process Data Objects to be received and to be transmitted.