VDO CANcockpit Series Product Manual

Product Manual CANcockpitTU00-0726-5111102 Technische Änderungen vorbehalten 0609 Technical details subject to change 5.2 - 13The 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 CANcockpitProducer Heartbeat Time (1017h)The producer heartbeat time defines the cycle time of the heartbeat. The producer heartbeat time is 0, if it is not used. Theunsigned 16bit value has to be a multiple of 1ms.OBJECT DESCRIPTIONIndex 1017hName Producer Heartbeat TimeObject Code VARData Type UNSIGNED16Category Conditional: Mandatory, if guarding not supported.ENTRY DESCRIPTIONAccess rwPDO Mapping NoValue Range UNSIGNED16Default Value As configured in EEPROM (WINgauge)Identity Object (1018h)The object at index 1018h contains general information about the device. The Vendor ID (sub-index 1h) contains a uniquevalue allocated to each manufacturer. The manufacturer-specific Product code (sub-index 2h) identifies a specific deviceversion.The manufacturer-specific revision number (sub-index 3h) consists of a major revision number and a minor revision number.The major revision number identifies a specific CANopen behavior and is administered by VDO. If the CANopen functionalityis expanded, the major revision has to be incremented.The minor revision number identifies different versions with the same CANopen behavior. The administration of the minorrevision number is the responsibility of the party, who administers the configuration data for a given application (VDO orOEM).Rational:The CANcockpit system of gauges is very flexible and can be adapted to many applications and requirements. The numberand kind of gauges connected will vary from application to application and therefore the mapping and interpretation of PDOdata will be different from configuration to configuration. A simple mechanism is required to prevent that a CANcockpit systemwith an inadequate configuration is connected to the CANopen network.Solution:The minor revision number will be utilized to distinguish between different CANcockpit configurations. The number will only bedifferent, if the characteristics are different, which are relevant as seen from the CANopen perspective. For example, if theconfiguration of the J1939 interface is changed, then this does not require a new minor revision number. However the minorrevision number needs to be changed, if another slave gauge is added, which is driven from CANopen data.This way it possible for the CANopen master to check, if the connected CANcockpit system has the correct configuration orbelongs to a list of compatible configurations.All information here is read only, but the minor revision number (EED_stCCopen.wMiRevNo) and the low byte of the majorrevision number (EED_stCCopen.bMjRevNo) (only VDO) can be set with WINgauge during configuration. The high byte of themajor revision number is stored in ROM and therefore fixed for a given firmware. For more detail for example the sub-indices,please refer to DS301 V4.02.OBJECT DESCRIPTIONIndex 1018hName Identity ObjectObject Code RECORDData Type IdentityCategory Mandatory