2
CANopen [X4]
16
Festo – GDCP-CMMP-M3/-M0-C-CO-EN – 1510b – English
2.4
Configuration of CANopen participants on the CMMP-AS-...-M0
M0
This section is only applicable for the motor controller CMMP-AS-…
-M0
.
Several steps are required in order to produce an operational CANopen interface. Some of these set
tings should or must be carried out before the CANopen communication is activated. This section
provides an overview of the steps required by the slave for parameterisation and configuration.
Instructions on commissioning with the Festo Configuration Tool can be found in the Help
for the device-specific FCT plug-in.
When designing the CANopen interface, the user must therefore make these determinations. Only then
should parameterisation of the fieldbus connection take place on both pages. We recommend that
parameterisation of the slave should be executed first. Then the master should be configured.
The CAN-bus-specific parameters can be set on two paths. These paths are separated from one another
and are accessed via the option “Fieldbus parameterisation via DINs” on the “Application data” page in
the FCT.
The option “Fieldbus parameterisation via DINs” is active on delivery and after a reset to the factory
settings. Parameterisation with FCT for activation of the CAN bus is thus not absolutely necessary.
The following parameters can be set via the DINs or FCT:
Parameters
Setting via
DIN
FCT
Node number
0 … 3
1)
“Fieldbus” page, operating parameters.
Activation of the CAN bus is performed automatically by
FCT (dependent on device control):
–
Device control by FCT
}
CAN deactivated
–
Device control released
}
CAN activated
Transmission rate (bit rate)
12, 13
1)
Input/activation
8
Protocol (data profile)
9
2)
1)
Only transferred in the event of inactive CAN communication
2)
Only transferred after a device RESET
Tab. 2.6
Overview of settings for CAN parameters via DINs or FCT