Hallo,
most likely the content of the EEPROM is faulty or missing.
Please post the output of: ethercat -p 0 xml
If this is the case:
You have to contact Lenze because they have to fix this.
Meanwhile you can try to copy the EEPROM-content from the old module to
the new module using ethercat ssi_read and ssi_write, but there is NO
guaranty that this will work!
Regards Wilhelm.
Am 28.02.2014 11:41, schrieb pier:
Dear helper
We would like to use last version of Lenze ethercat module for Servo Drives
We have tried the last 1.5.2 etherlab version but something is not
accessible when
setup is done...
This is the states when it works with previus version :
Here is the config for the one that works (actually there 17 Lenze
servos and all work):
0 0:0 OP + Lenze 8400 Device
1 0:1 OP + Lenze 8400 Device
With the newer :
Here is the configuration with the Lenze drive having the EtherCAT
module that does not work:
0 0:0 PREOP E 0x0000003b:0x000cd156
1 0:1 OP + EK1100 EtherCAT-Koppler (2A E-Bus)
For this test I have only initialized ID 0, 1 . The unit at ID 0 has
an error because configuration failed. I have got the following
Warnings/Error for ID 0:
Feb 24 21:28:26 (none) kernel: [ 2251.893111] EtherCAT WARNING 0-0: PDOs
configured for SM2, but slave does not provide the sync manager information!
Feb 24 21:28:26 (none) kernel: [ 2251.893114] EtherCAT WARNING 0-0: PDOs
configured for SM3, but slave does not provide the sync manager information!
Feb 24 21:28:26 (none) kernel: [ 2251.893116] EtherCAT ERROR 0-0: Failed
to determine PDO sync manager for FMMU!
Any Idea what is possible to do ?
Best Regards
Pierfrancesco Tateo
--
Perlsoft GmbH
Sennereigasse 27
3900 Brig
Switzerland
Tel. +41977022933
_______________________________________________
etherlab-users mailing list
[email protected]
http://lists.etherlab.org/mailman/listinfo/etherlab-users
_______________________________________________
etherlab-users mailing list
[email protected]
http://lists.etherlab.org/mailman/listinfo/etherlab-users
