Fieldbus communication
Instruction handbook b maXX BM5500, BM5600, BM5700
Document No.: 5.13008.10 Baumüller Nürnberg GmbH
228
of 314
8.4
Process of
commissioning
The test-commissioning is divided into the following sections:
1 Configuration of the CANopen
®
slave
2 Testing of the CANopen
®
slave
Configuring the CANopen
®
slave
The CANopen
®
is configured at the running device with ProDrive and a NMT-Master.
1 Switch on BM5500, BM5600, BM5700 with CANopen
®
2 Start ProDrive
3 Ensure, that the CANopen
®
slave communicates with the NMT-Master (the slave re-
ports to the master with the boot-up telegram), i.e. CAN-telegrams can be send/re-
ceived.
Make the following settings:
4 ProDrive: Activate communication source (refer to Parameter Manual: Drive manager)
5 NMT-Master: Create PDO-Mapping
(refer to Programming Manual CANopen
®
“)
6 NMT-Master: with the NMT-command :=1 into the state „OPERATIONAL change“,
then the cyclic communication starts.
Testing of the CANopen
®
-Slave
The CANopen
®
slave is tested, by using the total CANopen
®
network.
ProDrive does not indicate errors, the CANopen
®
slave was commissioned.
Operation Avoid a reset of the BM5500, BM5600, BM5700 in the cyclical operation of the
CANopen
®
slave.
WARNING!
Risk of injury due to moving parts!
Rotating and/or linearly moving parts can causesevere injuries.
If a reset of the BM5500, BM5600, BM5700 device is released in the running cyclical
operation or if the communication source is switched off, this can cause unwanted
conditions in the active application.
Therefore:
m Ensure, that the NMT master does not execute a reset, as long as the BM5500,
BM5600, BM5700 device is in the cyclical operation
m Ensure, that the CANopen
®
communication source only is able to communicate
with the BM5500, BM5600, BM5700 device.
NOTE!
After a reset the booting data set is loaded in the controller. In addition the mapping
is set on the CANopen
®
, which was saved in the controller part before the reset was
executed.