I'm running a demo program and using the motion interface to control my axes. They all follow a virtual master. I currently don't use any homing procedure. The axes run in synchronized_motion and the virtual master is running in discreet motion. When I go from state 'disabled' to motion I get the error "Error in axis command "Homing" - No support to check the homed status of the axis", but I'm not using any homing routine. I set the axis reference when setting up the drives. The error typically only pops up for about 4 to 6 axes, not all axes.
My question is, where would the motion app think the axis command for homing is coming from? Should I change something in how I implement the motion interface in the PLC? It's confusing because my axes are all configured and commanded the same way, but this error only appears for a few axes, and it is somewhat random, which axes get the error.
Here is a picture for reference:
