i have problem within a retrofit of old machine.
Theres a ned conveyorbelt with asynchronious motor configuared as “any induction” as we did several times before. Drive is Acoposmulti encoderless. It´s just a simple MoveVelocity.
(ACP motion 5.13.2 in AS 4.2.7)
Problem, i´m not able to get conveyor belt as fast as needed.
Parameters in attachement.
If i increase Basic.parameter.v_pos over 11600 i get Error 5027 Override.
Limit ist Set to 35000, Override ist 1 (100%)
Changing limits has no influence, Limit of 11600 makes no sense to me.
Has anyone idea how this Error 5027 is created or how i can make the drive speed up?
thats right, but it’s same problem, doesn’t matter if speed or accelaration.
Limits are way highter that movement parameters but i get error 5027 or 5026 if i change movement parameters.
I think you don´t understand the problem right.
I do overright parameters in init table. see attachment of first post.
But if i set for example Basis parameter v_pos for example from 11600 to 12000 while override is fixed at 1 (100%) i get error 5026. But Limit v_pos ist 35000, so why do i get this error beeing far below limit?
And why is limit for working exactly at 11600? makes no sense for me.
What Christoph means is: the only way that you can be sure what limits are currently active and what was written is, to check the Network Command Trace. In a support case that is the least we need to check your problem description against the reality and to see what happens between PLC and drives. If possible please provide the NCT and if possible the project.
In such a case I would also recommend that you contact your local support hotline! They should be able to help!
i have no updates on this topic. Machine is running with lower speed 24/7 at moment so i´m not able to provide NCT with startup section.
But as i wrote before, parameters are written to drive. If not,i wouldn´t get reaction to my changes. I still don´t understand why getting this error by setting speed/acc to value below limits.
I don´t have insight into running shedule of this machine to get NCT while startup.
The NCT is so important because you can see if other limits are written previously. The screenshot above only shows the init values of the limits. However, these could have been overwritten in the meantime. This is why the network command trace is so important. Without it, we will probably not make any progress in this case.
Due to about >1 month of inactivity, this post will be marked as solved. If you would still like assistance on this topic, please add a new reply with the latest status
