A few millimeters after synchronizing with the slave in EtherCAT communication, the "Fault Reset" bit is automatically set to TRUE (see attached file). I want to disable this, is there any way?
The problem seems to occur when the axis reference (AXIS_REF) is initialized. The reason for this is that the "Fault Reset" bit is set when SMC3_ReinitDrive is executed.
It is no problem to reset the drive error explicitly by executing MC_Reset or SMC3_ReinitDrive. However, if the drive error that occurred before the establishment of EtherCAT communication is reset in a non-explicit way (this phenomenon), it may cause unexpected problems and should be avoided.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I understood that the problem is on the slave side.
Since this phenomenon can be avoided by the PLC program, we will try to program it according to the slave.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A few millimeters after synchronizing with the slave in EtherCAT communication, the "Fault Reset" bit is automatically set to TRUE (see attached file). I want to disable this, is there any way?
What does this error in the drive report?
I would try to solve the root cause..(DC sync problem?)
Last edit: eschwellinger 2021-02-18
There are no errors in the drive. "Fault Reset" bit is automatically set regardless of whether the drive is in error.
Only the MC_Reset FB set the bit in the Controlword...
In the project, there is no program, only the system configuration (see attached file).Why is the Controlword set?
hm..is this only on startup?
but how cares? Does this lead to any unwanted action?
The problem seems to occur when the axis reference (AXIS_REF) is initialized. The reason for this is that the "Fault Reset" bit is set when SMC3_ReinitDrive is executed.
It is no problem to reset the drive error explicitly by executing MC_Reset or SMC3_ReinitDrive. However, if the drive error that occurred before the establishment of EtherCAT communication is reset in a non-explicit way (this phenomenon), it may cause unexpected problems and should be avoided.
but isn't this a slave problem?
All these other drives could deal with this!?
I understood that the problem is on the slave side.
Since this phenomenon can be avoided by the PLC program, we will try to program it according to the slave.