Resolving S7-1200 Motion Control Missing in TIA Portal V13

Problem Details

When opening a project in TIA Portal V13 with an S7-1200 CPU and attempting to configure a positioning axis for stepper motor control, the S7-1200 Motion Control instruction set does not appear in the Instructions task card. Right-clicking Technology Objects in the project tree and selecting Add new object returns a dialog reporting the error:

No technological object installed for this CPU family

The same CPU and axis configuration compiled and ran correctly under TIA Portal V11, and the engineering workstation has TIA Portal V13 installed alongside the V11 license.

Observable symptoms

• The branch Instructions → Technology → Motion Control → S7-1200 Motion Control is absent or empty in the right-hand Instructions pane.
• The Motion Control function blocks (MC_Power, MC_MoveAbsolute, MC_Home, MC_Stop, MC_MoveRelative, MC_MoveVelocity, MC_Reset) cannot be inserted from any task card.
• Right-click Technology Objects → Add new object shows a dialog stating that no technological object is installed for the selected CPU family.
• Selecting the Help link from the dialog redirects to S7-1500 documentation rather than S7-1200 manuals.

Affected software and firmware

Root Cause

The error "No technological object installed for this CPU family" indicates that the S7-1200 Motion Control plug-in was either not installed with the original TIA Portal V13 image, was skipped during installation, or has become corrupted. Two independent factors typically combine to produce the symptom:

1. Incomplete initial installation: The TIA Portal V13 installer was terminated early, run from an account without local administrator rights, or installed on top of a prior partial uninstall that left stale registry entries. When the install completes in less than 30 minutes on a workstation that should require 60–90 minutes for V13, the Motion Control and PLC Simulation components are almost always the elements that were skipped.
2. Missing TIA Portal V13 Update: Support for the S7-1200 CPU firmware V4.x family within V13 requires TIA Portal V13 SP1 Update 6 or later. Without this update, the technology-object filter rejects the selected CPU as a "non-technology" device even when the plug-in is nominally installed.

Solution

Two resolution paths are documented; apply Path A first, and Path B if the repair does not restore the technology objects.

Path A — Repair the existing installation

1. Insert the original TIA Portal V13 installation DVD or mount the ISO.
2. Open Control Panel → Programs and Features, select SIMATIC STEP 7 Basic V13, and click Uninstall/Change.
3. Choose Repair (NOT Uninstall). Confirm the components to repair; do not deselect any Motion Control plug-ins if they appear in the list.
4. Allow the repair to run to completion. A full repair on TIA Portal V13 typically takes 60–90 minutes and must be performed with administrative rights.
5. Reboot the workstation.
6. Re-launch TIA Portal, open the project, and confirm that Instructions → Technology → Motion Control → S7-1200 Motion Control is now visible in the Instructions pane.

Path B — Install TIA Portal V13 SP1 Update 6 (or later)

1. Close all TIA Portal instances and stop the Siemens S7DOS and ALM automation services from services.msc.
2. Download the cumulative update from the Siemens Industry Online Support portal. Search order number 6ES7822-0AA03-0YA5 (TIA Portal V13 SP1 Update 6) or the applicable later update.
3. Right-click the executable → Run as administrator.
4. Accept the licensing terms and complete the wizard. The installer merges new device support and refreshed motion control libraries into the existing V13 tree without requiring a full reinstall.
5. Restart the PC when prompted.
6. Open the project. Verify under Instructions → Technology → Motion Control that the S7-1200 branch is now populated.

Verification

After the repair or update completes, run the following checklist before recompiling the project:

1. Launch TIA Portal V13 → Help → About → Installed software. Confirm the listed version contains V13 SP1 Update 6 or higher, and that STEP 7 Motion Control V13 is checked.
2. Open the affected project. In the project tree, expand PLC_1 → Technology Objects. The right-click menu Add new object must now list TO_PositioningAxis, TO_SpeedAxis, and TO_ExternalEncoder as selectable options for the S7-1200 CPU.
3. In the Instructions pane on the right, navigate to Instructions → Technology → Motion Control → S7-1200 Motion Control. Confirm the presence of:
   • MC_Power (FB 830)
   • MC_Home (FB 831)
   • MC_Stop (FB 832)
   • MC_MoveAbsolute (FB 833)
   • MC_MoveRelative (FB 834)
   • MC_MoveVelocity (FB 835)
   • MC_MoveJog (FB 836)
   • MC_Reset (FB 839)
4. Drag MC_Power into OB1. A new instance DB (e.g., MC_Power_DB) is auto-generated, confirming the libraries are registered.

Configuring the S7-1200 Motion Axis After Recovery

Once the technology objects are available, configure the stepper axis using the workflow below.

Hardware prerequisites

• S7-1200 CPU with firmware ≥ V4.0 (e.g., CPU 1214C DC/DC/DC, 6ES7 214-1AG31-0XB0).
• Stepper drive with PULSE/DIR inputs (sink/source, 24 V).
• PTO wiring: CPU outputs Q0.0 (PTO1 pulse) and Q0.1 (PTO1 direction). For PTO2 use Q0.2/Q0.3.
• 24 V DC supply referenced to the CPU's M terminal. Common ground between CPU M and drive GND is mandatory.

Axis configuration parameters

Program structure

A canonical motion program sequence is shown in Structured Text (SCL) and equivalent ladder logic.

OB1 — Cyclic motion control (SCL)

// Axis enable
MC_Power_DB(Axis        := TO_Axis_1,
            Enable      := bEnable,
            EnablePositive := TRUE,
            EnableNegative := TRUE,
            Status      => wStatus,
            Busy        => bBusy,
            Error       => bError);

// Homing (one-shot)
IF bHomeRequest THEN
    MC_Home_DB(Axis    := TO_Axis_1,
               Execute := bHomeRequest,
               Position := 0.0,
               Mode     := 3,    // absolute set
               Done    => bHomeDone,
               Busy    => bHomeBusy,
               Error   => bHomeError);
    bHomeRequest := FALSE;
END_IF;

// Absolute move
IF bMoveReq THEN
    MC_MoveAbsolute_DB(Axis         := TO_Axis_1,
                       Execute      := bMoveReq,
                       Position     := rTargetPos,
                       Velocity     := rVelocity,
                       Acceleration := rAccel,
                       Deceleration := rDecel,
                       Done         => bMoveDone,
                       Busy         => bMoveBusy,
                       Error        => bMoveError);
    bMoveReq := FALSE;
END_IF;

// Emergency stop
MC_Stop_DB(Axis         := TO_Axis_1,
           Execute      := bEStop,
           Deceleration := rEStopDecel,
           Done         => bEStopDone);

Ladder equivalent (key rung)

NETWORK 1   // Enable axis
|---[ bEnable ]---[ MC_Power_DB        ]---|
                  Axis           := TO_Axis_1
                  Enable         := TRUE
                  EnablePositive := TRUE
                  EnableNegative := TRUE

NETWORK 2   // Move to position
|---[ bMoveReq ]---[ MC_MoveAbsolute_DB ]---|
                  Axis         := TO_Axis_1
                  Execute      := TRUE
                  Position     := rTargetPos
                  Velocity     := rVelocity
                  Acceleration := rAccel
                  Deceleration := rDecel

PTO Wiring and Hardware Configuration

Enable the PTO channel on the CPU under Properties → Pulse generators (PTO/PWM):

1. Select PTO1/PWM1.
2. Set Use of the pulse generator to PTO (Pulse Train Output).
3. Map the output to a hardware output (Q0.0 for PTO1 pulse; Q0.1 for direction).
4. Set the base frequency (Hz). For example, 100 kHz enables high-speed stepping drives without exceeding the CPU's pulse-train ceiling.

Commissioning Checklist

Troubleshooting Matrix

Locating the Technology Object Library After Recovery

Once TIA Portal V13 is correctly installed, the library structure is consistent across projects:

• Instructions task card (right pane): Instructions → Technology → Motion Control → S7-1200 Motion Control
• Program blocks task card (left pane) after first use: Program blocks → System blocks → System resources
• Technology objects in project tree: PLC_1 → Technology objects → TO_PositioningAxis_1

You may move the auto-generated MC function-block instance DBs from System resources into a user-defined folder under Program blocks for project organization. The instance DBs remain tied to the technology object after the move; renaming does not break references.

Common Pitfalls

1. Mismatch between installed TIA Portal and CPU order number: A CPU 1212C (6ES7 212-1...) on firmware V4.x requires an S7-1200 update that the V13 base release did not include. Always cross-check the catalog version in Devices & Networks after creating the device.
2. Selecting PWM instead of PTO: PWM mode does not support the motion-control instruction set. The CPU will compile, but MC_Power reports ErrorID 16#8001 on enable.
3. Using the CPU relay outputs on AC/DC/RLY variants: Relay outputs cannot generate PTO. Use a DC/DC/DC or DC/DC/RLY variant with a separate signal board if PTO count is insufficient.
4. Sharing the PTO output with user code: If the same byte (e.g., Q0.0) is written by user logic, the motion controller detects a conflict and raises an axis error. Remove the user write or remap the PTO output.
5. Migrating a V11 project without a V13 SP1 Update 6 install: Migration creates empty technology objects and reuses the V11 instruction set, which will not compile under V13. Update the toolchain first.

Reference Documentation

• S7-1200 Motion Control V13 Function Manual
• S7-1200 Programmable Controller System Manual
• STEP 7 Basic V13 SP1 / Update 6 Release Notes
• Motion Control (general reference)

FAQ