Skip to content

Motion and PID

When a Studio 5000 project contains motion axes or PID loops, the migration creates the matching technology objects in TIA Portal and translates the instructions that use them. This page explains what is created, what is translated, and what stays your job.

Each axis in the project becomes one technology object in the PLC. The agent creates them with the TIA Portal tools, one at a time, before it imports the routines that use them.

Studio 5000 axis TIA Portal technology object
Position loop Positioning axis (TO_PositioningAxis)
Position loop that is the slave of a gearing instruction Synchronous axis (TO_SynchronousAxis)
Velocity loop or frequency control Speed axis (TO_SpeedAxis)
Virtual axis A positioning axis set up as a virtual axis (no drive)
Torque loop, feedback only, power supply Not migrated. They are listed in the report so you can decide

What is copied:

  • the type of motion (linear or rotary) and the unit system (millimetres, inches, or degrees);
  • for a rotary axis, the length after which the position wraps around;
  • the dynamic limits: maximum velocity, acceleration, deceleration, and jerk, and the default dynamics, which follow those limits;
  • the homing position and homing speeds;
  • the following error limit, the positioning window, and the standstill velocity threshold.

Units. A linear axis keeps its unit. TIA Portal offers degrees or radians for rotary axes, not revolutions, so an axis that is in revolutions in Studio 5000 becomes degrees and its values are multiplied by 360. An axis whose unit is not recognised is created in millimetres and the agent tells you to set the unit.

What you do yourself:

  • Connect each axis to its drive: configure the drive and the telegram in TIA Portal. The axes are not connected to hardware.
  • Servo gains and tuning, feedback and motor data, torque limits, and scaling constants are not copied. Set and tune them at commissioning.
  • Check the homing direction and sequence: they are chosen by the Mode input of the homing block, not by the axis.

The motion instructions are translated to the system blocks that do the same job. A block is called every scan, and the condition of the rung becomes its Execute input.

Studio 5000 TIA Portal block
Motion Servo On (MSO), Motion Servo Off (MSF) MC_Power
Motion Axis Stop (MAS) MC_Halt
Motion Axis Home (MAH), Motion Redefine Position (MRP) MC_Home
Motion Axis Move (MAM), absolute MC_MoveAbsolute
Motion Axis Move (MAM), relative MC_MoveRelative
Motion Axis Jog (MAJ) MC_MoveVelocity
Motion Axis Fault Reset (MAFR), Motion Axis Shutdown Reset (MASR) MC_Reset
Motion Axis Gear (MAG) MC_GearIn

Each translated call gets its own instance data block. Absolute and relative moves need a positioning axis, and gearing needs a synchronous slave axis; the agent chooses the axis type from what the instructions require.

Limits of the translation:

  • Only the common forms are translated (for example, speed and acceleration in units per second, with no merge). A form with other settings becomes a placeholder network that says why.
  • Jerk and the motion profile are not passed. The axis’ default applies.
  • Some reads of axis and motion-tag bits (status words, in-process bits) have no exact equivalent and are approximations. The agent gives you a motion review file that lists every one of them and where it is read. Read it before you trust the status logic around a move.
  • Per-axis dynamics changes and cam instructions are not translated.

Add-On Instructions that take an axis as a parameter become function blocks with an axis parameter of the right type.

Each Logix PID loop becomes a PID_Compact technology object, and the PID instruction becomes a call of it with the setpoint, process value, and output connected the same way.

What is copied:

  • the loop time;
  • the input range and the output limits (the substitute output value, which PID_Compact uses on an input error and which has no Logix counterpart, is set to the lower output limit: with its default of 0 outside the limits TIA Portal refuses to download the program);
  • the high and low process-value alarm levels, as the object’s warning limits;
  • the control direction (direct or reverse acting).

The object starts in automatic mode after start-up, and its manual output defaults to 0.0.

What is not copied: the gains. There are two reasons. PID_Compact does not allow its controller parameters to be set from outside TIA Portal, and the conversion between the gain definitions of the two controllers could not be confirmed. The object keeps its defaults. Tune it with TIA Portal’s tuning at commissioning. The agent gives you a PID review file that lists each loop, what was set, and the Logix gains for reference.

Other points to know:

  • The condition of the rung that held the PID instruction is not used to switch the loop on or off. Check how the loop is enabled.
  • The alarm dead band of the original has no equivalent in the translation.
  • No cyclic organization block is generated for the loops. A PID rung without a tieback is translated as a call that runs in the organization block of the routine that holds it, which for a continuous task has a varying cycle time. For a fixed sample time, move the call into a function that a cyclic organization block calls, with the loop time listed in the review file.
  • A PID rung with a tieback, feedforward, alarm-disable or hold operand is left as a placeholder of category pid: the object exists and is configured, but nothing calls it. The agent asks you whether to write the call, in which cyclic organization block, and whether you accept the call without the tieback (PID_Compact does bumpless transfer and anti-windup itself).
  • Enhanced PID (PIDE) and other PID variants are not translated.

The agent’s final report contains a Motion line (how many calls of each kind were translated, and that jerk and profile are not passed) and a PID line (which loops became objects). Read the review files it names, then continue with Reviewing migrated Ladder.