Product Manual CANcockpit
TU00-0726-5111102 Technische Änderungen vorbehalten 0609 Technical details subject to change 5.2 - 12
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
Manufacturer Firmware Version (100Ah)
Contains the manufacturer firmware version description. For CANcockpit this is the firmware date, because this is relevant for
the configuration with WINgauge and is required to be checked before a new EEPROM configuration may be written into the
EEPROM via CANopen. Only, if the firmware version matches the firmware version included in the Intel-hex file, is it allowed
to write the configuration to EEPROM.
Example of the format: 31_12_2004
OBJECT DESCRIPTION
INEDX 100Ah
Name Manufacturer firmware version
Object Code VAR
Data Type Visible String
Category Optional
ENTRY DESCRIPTION
Access const
PDO Mapping No
Value Range No
Default Value No
Note: The CANopen standard refers to this object as the "Manufacturer Software Version" however to be consistent with the
terminology applied for CANcockpit this entry has been named "Manufacturer Firmware Version". For CANcockpit the
software is defined to be WINgauge, which is the configuration software running on a personal computer.
COB-ID Emergency Object (1014h)
Index 1014h defines the COB-ID of the Emergency Object (EMCY) as an unsigned 32bit value.
The value is read only and the COB-ID is fixed at 128+own Node ID.
OBJECT DESCRIPTION
Index 1014h
Name COB-ID Emergency message
Object Code VAR
Data Type UNSIGNED32
Category Conditional: Mandatory, if Emergency is supported.
ENTRY DESCRIPTION
Access ro
PDO Mapping No
Value Range UNSIGNED32
Default Value 80h + Node-ID
Consumer Heartbeat (1016h)
CANcockpit is a slave device on the CANopen network and therefore does not monitor the heartbeat of other devices. Hence
this object is not part of the CANcockpit object directory. However RPDO messages required for the gauges and displays are
continuously monitored with a configurable timeout function. If a message is not received within its configured timeout limit,
then this will be communicated to the operator. Affected gauge pointers will move to the error indication position and PVD will
show "------".
To Next Page
Loading...
Need help?
General
