Product Manual CANcockpit
TU00-0726-5111102
Technische Änderungen vorbehalten
0609
Technical details subject to change
5.2 - 3
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
5.2.1 Summary of Features
NMT: Slave
Error Control:
Heartbeat
Node ID:
Configurable in EEPROM with WINgauge
No. of PDOs:
7 x RPDOs and 3 x TPDOs
PDO modes:
Manufacturer specific time-triggered with one configurable interval
for each TPDO with WINgauge.
PDO linking:
No, (PDO COB-Ids can be configured with WINgauge)
PDO mapping:
Static
No. of SDOs:
One server SDO
Emergency message:
Yes
CANopen version:
DS 301 V4.02
Framework: No
Certified:
Yes, or documented.
Device Profile:
DS 401 V2.1
5.2.2 Expressions
COB Communication
Object
COB-ID
CAN identifier of Communication Object
Device Profile
A standardised CANopen device profile specifies the CANopen characteristics of a type of
device, for example an I/O module. Some of the features are mandatory and others are
optional. A standardised CANopen device profile provides a basis for the development of a
CANopen device and creates a degree of exchangeability between different suppliers.
Framework
CANopen frameworks are specific extensions of the Application Layer and the standardised
communication 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 standardized
manner.
NMT
Network Management in CANopen
Node-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. PDO
communication and mapping parameters define it.
RPDO Receiving
PDO
SDO
Service Data Objects enable access to the CANopen object directory. An SDO consists of at
least two CAN messages with different identifiers. SDOs are always confirmed point-to-point
communication services.
TBD
To Be Defined -> is not yet specified
TPDO Transmitting
PDO
Содержание 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: ......