Siemens SIMOVERT MASTERDRIVES Manual page 621

Communication / CBC CANopen Communication Board
8.5.9 CANopen EDS
Description
Application
8.5-106
CAN-EDS (Electronic Data Sheet) passes the IDs of the objects that
are available in the device to a commissioning tool. These objects are
set to their defaults.
You need an EDS to be able to work with a CANopen network
configuring tool.
Using this EDS, you can inform the Commissioning Tool network which
objects and functions are made available by the connected CANopen
device.
The CANopen EDS for the MASTERDRIVES with technology option
F01 or B-Pos contains all the available objects of the device.
Not all EDS objects are always available in the device. Those which are
available are dependent on the PDO mapping via parameters P711 to
P718. Consequently, a DCF file needs to be generated from the EDS.
This DCF therefore contains the bus address setting, the baud rate and
the mapped objects.
To find out which objects are mapped, read the conventions for PDO
mapping in Subsection 8.5.2.4. Configure your DCF accordingly.
Example:
You have selected PDO 29 from the table of receive PDOs in
parameter 712.
This contains the following objects
60FFh target_velocity
3003h Free object 3003h / 16-bit
3004h Free object 3004h / 16-bit
Object 60FFh is always available in the device provided that the correct
interconnection is made in the MASTERDRIVES device. This object
has no effect on the EDS.
Objects 3003h and 3004h are not available if they have not been
mapped via parameters P712 - P714 in a premapped PDO to the
device.
This means that these objects need to be transferred to the DCF.
The three thousand objects that are not mapped to a PDO must not be
transferred to the DCF.
6SE7087-6QX70 (Version AD)
Compendium Motion Control
02.2004
Siemens AG
SIMOVERT MASTERDRIVES