Product Manual CANcockpit
TU00-0726-5111102
Technische Änderungen vorbehalten
0609
Technical details subject to change
5.2 - 13
The reproduction, distribution and utilization of this document as well as the communication of its contents to others without express
authorization 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 CANcockpit
Producer 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. The
unsigned 16bit value has to be a multiple of 1ms.
OBJECT DESCRIPTION
Index 1017h
Name
Producer Heartbeat Time
Object Code
VAR
Data Type
UNSIGNED16
Category Conditional:
Mandatory, if guarding not supported.
ENTRY DESCRIPTION
Access rw
PDO Mapping
No
Value Range
UNSIGNED16
Default 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 unique
value allocated to each manufacturer. The manufacturer-specific Product code (sub-index 2h) identifies a specific device
version.
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 functionality
is expanded, the major revision has to be incremented.
The minor revision number identifies different versions with the same CANopen behavior. The administration of the minor
revision number is the responsibility of the party, who administers the configuration data for a given application (VDO or
OEM).
Rational:
The CANcockpit system of gauges is very flexible and can be adapted to many applications and requirements. The number
and kind of gauges connected will vary from application to application and therefore the mapping and interpretation of PDO
data will be different from configuration to configuration. A simple mechanism is required to prevent that a CANcockpit system
with 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 be
different, if the characteristics are different, which are relevant as seen from the CANopen perspective. For example, if the
configuration of the J1939 interface is changed, then this does not require a new minor revision number. However the minor
revision 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 or
belongs 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 major
revision number (EED_stCCopen.bMjRevNo) (only VDO) can be set with WINgauge during configuration. The high byte of the
major 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 DESCRIPTION
Index 1018h
Name Identity
Object
Object Code
RECORD
Data Type
Identity
Category Mandatory
Summary of Contents for CANcockpit Series
Page 53: ...June 2009 Training WinGauge Software page 1 ...
Page 54: ...Components and Concept June 2009 Training WinGauge Software page 2 ...
Page 55: ...Example of a fully configured Instrumentation June 2009 Training WinGauge Software page 3 ...
Page 66: ...June 2009 Training WinGauge Software page 14 ...
Page 67: ...June 2009 Training WinGauge Software page 15 ...
Page 80: ...Examples of new defined Symbols June 2009 Training WinGauge Software page 28 ...
Page 167: ......
Page 168: ......