Product Manual CANcockpit
TU00-0726-5111102
Technische Änderungen vorbehalten
0609
Technical details subject to change
5.2 - 7
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
Minimum Capabilities
To enable devices, which do not support the complete DBT- (Distributor) and NMT (Network Management) Slave functionality,
to co-operate with full capability devices, the following minimal capabilities are required:
Module-ID,
Object dictionary, depending on the device functionality,
One SDO, supporting the mandatory entries (read only),
Support of the following services as NMT Slave:
Reset_Node,
Enter_Pre-Operational_State,
Start_Remote_Node,
Stop_Remote_Node,
Reset_Communication
Default profile ID-allocation scheme
Minimum capability devices enter the Pre-Operational state directly after finishing the device initialisation. ID-allocation is via
WINgauge. Then the nodes can be switched directly into the Operational state. By switching a device into the stopped state it
is forced to stop the communication altogether (except node guarding, if active). Furthermore, this state can be used to
achieve certain application behaviour. The definition of this behaviour falls into the scope of device profiles.
EEPROM Option for transition from pre-operational to operational state after KL.15
on.
It is possible to enable an option via EEPROM configuration, which lets CANcockpit move from pre-operational state to
operational state automatically after KL.15 is turned on. Also, if CANcockpit performs a reset, the operational state will be
entered without requiring an NMT-command. A reset for example can be caused by a low voltage condition or a watchdog
trigger.
However when an NMT-command is received to move from operational to another state, CANcockpit will perform the
requested transition without automatically re-entering the operational mode.
If the pre-operational state is entered, because of an error condition requiring this, then CANcockpit will remain in the pre-
operational state without automatically moving to operational state again.
Static allocation of the communication object identifiers (COB-ID's)
Static distribution means that the identifiers are fixed by the module suppliers and may be changed by the system integrator
through module specific means such as configuration with WINgauge.
Restore Defaults
If parameters in EEPROM can be changed via CANopen interface, then this option should be implemented.
Содержание CANcockpit Series
Страница 53: ...June 2009 Training WinGauge Software page 1 ...
Страница 54: ...Components and Concept June 2009 Training WinGauge Software page 2 ...
Страница 55: ...Example of a fully configured Instrumentation June 2009 Training WinGauge Software page 3 ...
Страница 56: ...Example of a fully configured Instrumentation cont June 2009 Training WinGauge Software page 4 ...
Страница 66: ...June 2009 Training WinGauge Software page 14 ...
Страница 67: ...June 2009 Training WinGauge Software page 15 ...
Страница 80: ...Examples of new defined Symbols June 2009 Training WinGauge Software page 28 ...
Страница 108: ...VDO A trademark of the Continental Corporation Product Information www vdo com CANcockpit CANopen Specification for ...
Страница 167: ......
Страница 168: ......