Motion callable has not reached "RUN"

Hi,

I'm having the same issue as listed above. I followed the links to the threads/topics you mentioned but it didn't solve my problem.

When i boot the CORE, the motion app is stuck in Configurating/Running and the axis states are OUTDATED. Setting the Motion app to Running doesn't work. The state changes to Booting but after a couple of minutes an error pops up and the state goes back to Configuration/Running.

When I set the main operating mode from partially operating to Operating the motion app does start and the state changes to Running (both the motion app and the main operating mode of the CORE)

The help provided says it could heve to do something with the scheduler, but i don't see any differences between the partially operating state and the running state of the core.

 

Best reply by CodeShepherd

It seems that your application code in the PLC is doing that requests. Do you use any EtherCat based drive access function blocks like IL_ECATSoeRead? These could be delayed to improve the behaviour.

View original
14 replies