VDO CANcockpit Series Product Manual

Product Manual CANcockpitTU00-0726-5111102 Technische Änderungen vorbehalten 0609 Technical details subject to change 5.2 - 3The reproduction, distribution and utilization of this document as well as the communication of its contents to others without expressauthorization is prohibited. Offenders will be held liable for the payment of damages. All right reserved in the event of the grant of a patent,utility model or design .CANopen-Specification for CANcockpit5.2.1 Summary of FeaturesNMT: SlaveError Control: HeartbeatNode ID: Configurable in EEPROM with WINgaugeNo. of PDOs: 7 x RPDOs and 3 x TPDOsPDO modes: Manufacturer specific time-triggered with one configurable intervalfor each TPDO with WINgauge.PDO linking: No, (PDO COB-Ids can be configured with WINgauge)PDO mapping: StaticNo. of SDOs: One server SDOEmergency message: YesCANopen version: DS 301 V4.02Framework: NoCertified: Yes, or documented.Device Profile: DS 401 V2.15.2.2 ExpressionsCOB Communication ObjectCOB-ID CAN identifier of Communication ObjectDevice Profile A standardised CANopen device profile specifies the CANopen characteristics of a type ofdevice, for example an I/O module. Some of the features are mandatory and others areoptional. A standardised CANopen device profile provides a basis for the development of aCANopen device and creates a degree of exchangeability between different suppliers.Framework CANopen frameworks are specific extensions of the Application Layer and the standardisedcommunication profile. Examples are the framework for programmable CANopen devices(SPS), framework for safety relevant applications.EDS Electronic Data Sheet describes the functionality of a CANopen device in a standardizedmanner.NMT Network Management in CANopenNode-ID Address of CAN node (device)Object Directory Directory inside the CANopen device containing all CANopen objects.PDO Process Data Object is a CANopen communication object handling real-time data. PDOcommunication and mapping parameters define it.RPDO Receiving PDOSDO Service Data Objects enable access to the CANopen object directory. An SDO consists of atleast two CAN messages with different identifiers. SDOs are always confirmed point-to-pointcommunication services.TBD To Be Defined -> is not yet specifiedTPDO Transmitting PDO