Rockwell folds servo control right into the Logix program. You create a motion group and an axis tag, then command it with MAM/MAJ/MAS instructions over CIP Motion to a Kinetix drive. No separate motion controller — same tags, same scan. First rule, same as everywhere: enable the axis (MSO) before it moves.
A Kinetix-driven linear axis on a 400 mm rail. The motion instructions are greyed until you fire MSO (Motor Servo On) — an axis in the Stopped state ignores moves. Enable it, set a target, and fire MAM (Move Absolute): the velocity plot draws the trapezoid the drive generates. Hold MAJ to jog; MAS stops.
The axis tag is a rich structure — Axis_X.ActualPosition, .ActualVelocity, .ServoActionStatus — readable anywhere in your logic. CIP Motion syncs the drive over EtherNet/IP (Track 06), so the very network carrying your I/O also closes the servo loop. An S-curve profile just rounds the trapezoid's corners.
⚡ MSO / MSF — Motor Servo On / Off. The enable. Nothing moves until MSO puts the axis in the running state.
🎯 MAM — Move Absolute. Go to a position in the axis coordinate system, at a set speed/accel. Needs a home reference (MAH).
↔️ MAJ — Move Axis Jog. Run continuously while commanded — for setup and manual moves.
■ MAS / MAH — Stop, and Home. MAS decelerates to a halt; MAH establishes the reference absolute moves are measured from.
You fire MAM but the axis sits still and the instruction errors. The Kinetix drive is healthy and powered. What's missing?