In TIA, a positioning axis can be configured as a Technology Object and commanded through MC_ blocks. Your program requests power, a position, jogging or homing; the TO handles the configured motion profile. For example, you can request a move to 350 mm. Before issuing a move, check that the axis is ready: motion requires an enabled axis.
The simulation has a carriage on a 500 mm linear rail. Use the MC_ buttons to issue its motion commands. The move controls stay greyed out until you press MC_Power. This demonstrates the enable condition; it is a simplified model, not the complete controller state machine. Enable the axis, set a target and select MC_MoveAbsolute to watch the velocity trace accelerate, cruise and decelerate toward the target.
The trapezoidal trace shows acceleration, constant-speed travel and deceleration within the axis limits. The technology object calculates that profile from the move command and configuration, so the application does not need to calculate each point itself. An S7-1500T provides additional motion functions such as camming and gearing.
⚡ MC_Power enables or disables the axis. Check the enable status before issuing a motion job; pressing the button in this example makes that condition visible in the status panel.
🎯 MC_MoveAbsolute requests an absolute position in the axis coordinate system, for example 350 mm. The positioning axis must be homed before it can execute that absolute move.
🏠 MC_Home establishes the axis reference. That reference gives an absolute position its meaning within the configured coordinate system.
↔️ MC_MoveJog / MC_MoveRelative requests continuous jogging while the command is held, or a move through a fixed distance from the current position.
You call MC_MoveAbsolute(Position := 350), but the axis remains stationary and the block reports an error. The drive is healthy. Which required axis condition should you check first?