Uploading SIMOTION Projects in TIA Portal: Options Explained

Overview

Uploading a SIMOTION controller project back to the programming device (PG/PC) is one of the most common service operations performed on SIMOTION D, SIMOTION P, and SIMOTION C platforms. Engineers routinely need to recover the current runtime configuration from the controller when the offline project on the engineering station is missing, corrupted, or out of date. In the TIA Portal / SIMOTION SCOUT TIA environment, the upload workflow exposes two check-box options that frequently cause confusion: Save before loading to PG and Overwrite available libraries. Selecting or unchecking these options has direct consequences for unsaved editor buffers, program source integrity, and the master copies of technology objects and libraries stored in the project.

This reference explains the semantics of every upload option, the exact sequence required to upload a SIMOTION D425 (and related D4xx/D410 platforms), the meaning of the red and green status icons in the project tree, and the consistency checks that must be performed before a project is considered safe to archive or hand over.

Prerequisites

Before initiating an upload, verify the following on the engineering station and the target SIMOTION device:

1. SIMOTION SCOUT TIA (V4.4 or higher) or the TIA Portal with the SIMOTION option package installed. The minimum version required depends on the firmware of the target SIMOTION device; consult the Siemens Industry Online Support for the compatibility matrix relevant to your firmware version.
2. A working PROFINET or PROFIBUS connection between the PG/PC and the SIMOTION controller, with the PG/PC interface correctly assigned in the TIA Portal (Online > Select online interfaces).
3. The SIMOTION device must be reachable. Test this with Accessible nodes in TIA Portal or Online > Accessible nodes in SCOUT TIA.
4. All unsaved program sources on the PG/PC side that the engineer wishes to retain must be closed and saved before starting the upload dialog. Open editors with unsaved modifications are handled differently depending on the option settings.
5. Rights to overwrite the master copy of the project on the engineering station (write access to the project directory).

Upload Methods Available in TIA Portal

TIA Portal distinguishes between two fundamentally different upload paths:

The recommended path for a SIMOTION upload is Online > Upload device as new station (hardware and software). This command is documented in the TIA Portal help under Loading project data > Uploading project data from a device (see TIA Portal V20 documentation).

The Upload Dialog: "Save Before Loading to PG"

When the upload operation detects one or more editors with unsaved modifications, TIA Portal raises a confirmation dialog that contains the check-box Save before loading to PG. The semantics are:

• Check-box enabled: All open editors are force-saved to the offline project before the upload proceeds. This protects the engineer from losing recent edits if the upload is interrupted or if the upload replaces the buffers.
• Check-box disabled: The upload proceeds immediately, the open editors are closed, and any unsaved modifications in those editors are discarded. The compiled program and configuration that come back from the device are not affected — only the local editor buffers are lost.

In practice, the option only matters if you have at least one program, unit, or watch table open and modified since the last save. If no editor is open or all open editors are clean, the check-box is grayed out and the choice is irrelevant. This is the condition under which it is "not necessary to activate this option" — the operation becomes a no-op when there is nothing to save.

The Upload Dialog: "Overwrite Available Libraries"

The second check-box in the upload confirmation dialog is Overwrite available libraries. SIMOTION projects can reference libraries (LAD/FBD, ST, MCC, technology objects). The master copy of these libraries lives in the project and is the source from which SIMOTION compiles the runtime image.

• Check-box enabled: If the upload finds a library on the device that is also present in the offline project, the offline master copy is replaced with the version coming from the controller. This is the correct behavior when the controller is the source of truth and the offline copy is suspected to be stale.
• Check-box disabled: Existing libraries in the offline project are preserved. New libraries present on the controller but not in the offline project are still added; only the master copies of common libraries are kept on the offline side.

The right choice depends on the trust model:

Upload Workflow: Step-by-Step

The following procedure uploads a SIMOTION device to a new station in the TIA Portal project tree.

1. Open the target TIA Portal project (or create a new empty project).
2. In the project tree, select the project root node.
3. Choose Online > Upload device as new station (hardware and software). TIA Portal opens the device selection dialog.
4. From the list of accessible nodes, select the target SIMOTION device. Confirm the PG/PC interface and the target subnet.
5. Click Load. TIA Portal scans the device and reads its configuration.
6. If open editors with unsaved changes are detected, the dialog asks whether to save them. Make the choice appropriate to your situation (see previous section) and confirm with Yes or No.
7. If libraries conflict, the dialog asks whether to overwrite the available libraries. Select the appropriate option (see previous section).
8. TIA Portal creates a new station in the project tree and copies the device configuration, the SIMOTION program sources, the technology objects, and the watch tables into it.
9. Wait for the upload to complete. The status bar reports progress; the Output Window logs every step.
10. After the upload, perform a consistency check (Project > Compile > All). Compilation must complete with zero errors before the project is considered usable.

Uploading SIMOTION D425 Hardware Configuration

The SIMOTION D425 is a SIMOTION D drive-based controller in the D4xx series (alongside the D410, D445, D455, and D445-1). It combines a SIMOTION controller with SINAMICS S120 drive control in a single device. The hardware configuration of a D425 consists of:

• The PROFINET / PROFIBUS interface parameters.
• The onboard I/O configuration (for D425 variants that have onboard I/O).
• The SINAMICS Integrated topology (DRIVE-CLiQ connections, line module, motor modules, encoders).
• The cross-project PROFIBUS or PROFINET connections to the distributed I/O.

Uploading the D425 hardware configuration is part of the Upload device as new station command. TIA Portal reads both the SIMOTION-side configuration and the SINAMICS Integrated configuration. The result is a new station whose device view shows the SINAMICS Integrated as a sub-module of the D425, and whose topology view reflects the actual DRIVE-CLiQ wiring found on the device.

There is no separate "upload SINAMICS configuration" command in SIMOTION SCOUT TIA — the drive data is uploaded together with the SIMOTION data. If the SINAMICS Integrated is shown as a separate node in the project tree, both nodes are populated in the same upload operation.

Connection Status: Red Versus Green Indicators

After the upload, the new station appears in the project tree with colored status indicators on the SIMOTION device and on auxiliary objects (HMIs, SINAMICS drives, distributed I/O):

• Green icon: The offline configuration in the project tree matches what was found on the device, or the device is reachable and consistent.
• Red icon: There is a mismatch between offline and online, the device is unreachable, or a consistency error was detected during the upload.

When a SIMOTION D425 shows red while other objects in the same project are green, the most common causes are:

1. Different online interface: The PROFINET interface used to reach the SIMOTION D425 is not the same as the one used for the other objects. Re-check Online > Select online interfaces.
2. Different subnet: The D425 sits on a different subnet than the rest of the project. The project navigation can show green for devices on a subnet that is online and red for the device whose subnet the PG/PC interface is not bound to.
3. Access rights / firewall: A Windows firewall rule on the PG/PC or a security configuration on the switch blocks the SIMOTION discovery packets.
4. Firmware / project version mismatch: The offline project was created for a different firmware version than the one running on the D425. The diagnostic detail is in the Output Window — expand the device and look for the red status reason.
5. Routing problem: A router is required to reach the D425 (for example, when the PG/PC and the D425 are on different VLANs). Configure the router in Devices & Networks > Topology or in the device properties.

Output Window Diagnostics

Whenever the upload status icon is red, the Output Window is the primary diagnostic surface. TIA Portal categorizes messages as follows:

Right-clicking a red status icon typically offers a Go to command that navigates directly to the object causing the error. This is the fastest path to a fix.

Verification and Consistency Checks

After the upload completes, perform the following verification before treating the project as authoritative:

1. Compile the project: Project > Compile > All (rebuild all). The build must complete with zero errors. Warnings are acceptable but should be reviewed.
2. Check the program sources: Open every unit and every program (ST, LAD, FBD, MCC). Verify the source matches the expected logic. SIMOTION uploads include the compiled program sources, not the interpreted ones — the engineer can still see the source.
3. Verify the technology objects: Open every TO (TO_Axis, TO_SpeedAxis, TO_PositioningAxis, TO_Cam, TO_CamTrack, TO_Interpolator, TO_Synchronism). Compare the configuration to the engineering documentation.
4. Verify the watch tables and the HMI tags: These are not always uploaded with the same fidelity as the program sources. Re-create any that are missing.
5. Verify the topology: Devices & Networks > Topology view. Check every DRIVE-CLiQ port against the physical wiring.
6. Compare the firmware versions: The Device properties > Online & Diagnostics view shows the firmware of every component. Compare against the project's intended target versions.
7. Perform a test download to a second station: If a second SIMOTION of the same type is available, download the uploaded project to it as a sanity check. The download must succeed without complaints about version or library differences.

Troubleshooting Matrix

Best Practices for SIMOTION Uploads

• Always close and save all editors before the upload. The dialog option is a safety net, not a workflow.
• Use Upload device as new station rather than the per-device context-menu upload. The "as new station" path produces a clean, named station that can be archived.
• Treat the controller as the source of truth only when no offline project exists or when the offline project is known to be stale.
• After every upload, perform a full project compile. This catches any cross-reference that the upload may have left unresolved.
• Archive the uploaded project immediately, with a clear name and timestamp. Field service uploads are often performed under time pressure and the resulting project is easy to lose track of.
• Document the firmware versions of every component in the project. A version mismatch between the offline project and the controller is the single most common cause of post-upload confusion.