Overview
The Siemens SIMOCODE Pro C is a modular motor management and protection device that ordinarily sits on a Profibus DP or Profinet segment behind a SIMATIC controller. In retrofit or brownfield MCC applications, however, the same unit must sometimes operate in true standalone mode: no Profibus/PROFINET master, no operator panel, no PC connection, only a hard-wired start/stop pushbutton station, a reset pushbutton, and a fault indicator lamp. This configuration is sometimes called a "direct-on-line starter in a box" and it is the cleanest way to reuse an existing SIMOCODE Pro C as a spare unit in a withdrawable MCC bucket.
This reference walks through the exact parameter changes in SIMOCODE ES V20 (TIA Portal) required to make a SIMOCODE Pro C act as an autonomous motor starter, while keeping every standard SIMOCODE protection function active. The procedure assumes a SIMOCODE Pro C base unit (3UF7000-1A.0-0 or -1A.0-1, depending on Profibus/Profinet variant) paired with a 3UF7100-1AA00-0 current measuring module sized to the motor.
Prerequisites
- SIMOCODE Pro C base unit, 3UF7000 series, with current measuring module (3UF7100) matched to motor FLA.
- SIMOCODE ES V20 or later, installed and licensed. The TIA Portal variant is preferred for projects that also contain SIMATIC controllers; the classic SIMOCODE ES 2007 SP4 (PCS 7) variant is acceptable for standalone use.
- USB PC cable (3UF7940-0AA00-0) or Ethernet/Profinet for Pro V/PROFINET variants, to download the project to the device.
- 24 V DC control supply for the base unit and for the digital inputs.
- Hard-wired control station: Start (NO), Stop (NC), Reset (NO) pushbuttons, and a fault indicator lamp or stack-light.
- Motor nameplate data: rated current (Is1), service factor, trip class, and rated voltage.
SIMOCODE Pro C Hardware Architecture
The base unit is the only component that matters for standalone wiring. The relevant on-board I/O of a 3UF7000-1A base unit is summarized below.
| Channel | Function (default) | Standalone re-assignment |
|---|---|---|
| Input 1 (BU) | OFF command (NC) | Stop pushbutton (NC contact) |
| Input 2 (BU) | ON command (NO) | Start pushbutton (NO contact) |
| Input 3 (BU) | Reset | Reset pushbutton (NO contact) |
| Input 4 (BU) | Test/Ground fault (model dependent) | Spare or external trip input |
| Output 1 (relay, NO) | Contactor control, ON | Contactor control (unchanged) |
| Output 2 (relay, CO) | QLS (Fault) | Fault indicator lamp |
| Output 3 (relay, CO) | QAS (Operating state) | Run indication lamp (optional) |
The base unit also carries two 4-position rotary address switches S1 and S2 on the front. In bus mode these select the Profibus DP slave address (1–125). In standalone mode, S1 and S2 are repurposed by the SIMOCODE ES configuration to select the active control station, or they can be set to "fixed level" so the software override is in effect regardless of switch position.
Control Station Selection for Standalone Operation
SIMOCODE Pro offers four control stations. They determine which source is allowed to issue commands (ON, OFF, Reset) and to read status.
| Control station | Typical source | Standalone relevance |
|---|---|---|
| S7 / PROFIBUS-DP master | SIMATIC PLC cyclic PZD | Disabled in this procedure |
| Local 1 (PC) | SIMOCODE ES on RS-232/USB | Enabled for diagnostics only |
| Local 2 (DI/DO on the device) | Hard-wired inputs and operator panel | Enabled — this is the active station |
| Local 3 (Operator panel) | 3UF7200 operator panel | Disabled if no panel fitted |
For a fully autonomous starter, set the selector for S7/DP control station to PLC = inactive and select Local2 as the only issuing control station. In SIMOCODE ES this is done by opening the project, navigating to Control stations → Control function → Sources for commands, and checking the box for Local 2 while clearing the boxes for PLC/PROFIBUS and Local 3.
Two implementation choices exist for the S1/S2 selector on the base unit:
- Fixed level in software — Open the device properties, expand Control station selector, and set S1 = fixed level 0 and S2 = fixed level 1. The hardware switches are then ignored. This is the preferred approach for a stand-alone spare unit that may be inserted into any bucket.
- Hardware selector — Leave S1 and S2 at "not fixed" and document the required switch position on the bucket door. Acceptable when the SIMOCODE will never be moved.
Reset Input Configuration
By default the SIMOCODE ES V20 direct-starter template wires the Reset command to the Cyclic Receive, bit 0.7 from the Profibus master. In standalone mode that bit never toggles, so a latched fault can never be cleared. The Reset source must be re-pointed to a hard-wired input.
In the graphic editor, perform the following edits in this order:
- Delete the Cyclic Receive 0 function block from the program (right-click → Remove). This removes the wired Reset-from-PLC link.
- Insert a new Reset function block and connect its output to the SIMOCODE internal Reset signal.
- Source the Reset block from Input 3 (Base Unit). To do this, open the Reset block's properties and set the Signal source parameter to
DI Base Unit → Input 3. - Configure the input as normally open, 24 V DC, debounce time 20 ms (default).
When the operator presses the Reset pushbutton, Input 3 closes to 24 V, the SIMOCODE internal Reset bit sets for the duration of the press plus one scan, and any latched fault is cleared after the configured cooling time has elapsed.
Fault Output Configuration
By default, Cyclic Send 0 is wired to the QLS (Fault) flag so the PLC can display the fault. In standalone mode that bus is gone. Re-wire QLS to a base-unit output so a stack-light can indicate the fault.
- Delete the Cyclic Send 0 and any Cyclic Send 1 function blocks.
- Open the QLS ‒ Fault block and set Output target to
DO Base Unit → Output 2. - Output 2 is a changeover relay. Wire the normally-open contact of Output 2 to the fault lamp; the normally-closed contact can drive a healthy-run lamp or be left unused.
Optional: route the QAS (Operating state → ON) flag to Output 3 to indicate "motor running". This gives the operator both a green run light and a red fault light without any panel.
Motor Overload Protection Setup
The overload function is the reason SIMOCODE Pro is used in the first place. Three parameters are critical:
| Parameter | Path in SIMOCODE ES | Value to enter |
|---|---|---|
| Set current Is1 | Protection functions → Overload → Current setpoint | Motor FLA from nameplate, in amperes, e.g. Is1 = 12.5 A
|
| Trip class | Protection functions → Overload → Trip class | CLASS 10 for standard motors, CLASS 20 for high-inertia loads, CLASS 30 for very high inertia |
| Cooling time | Protection functions → Overload → Recovery time | Match motor thermal time constant; default 5 min for standard TEFC motors |
For a 400 V, 50 Hz, 11 kW motor with FLA 21 A the entries would be:
Set current Is1 = 21.0 A
Trip class = CLASS 10
Cooling time = 300 s
Phase failure prot. = ON (recommended for all three-phase motors)
Phase rotation = Indifferent (unless the application is unidirectional)
Unbalance detection = 30 % (default)
SIMOCODE Pro uses a thermal model: I²t is integrated continuously. After a trip the device blocks restart until the calculated thermal image has decayed below 75 % (or whatever the recovery threshold is set to). The Reset pushbutton is only effective after this cooling period has expired, which prevents an immediate re-trip from a hot motor.
Cyclic Data Block Handling
Once the Reset and QLS blocks have been redirected to base-unit I/O, all cyclic send and receive blocks should be removed. The TIA Portal will display warnings if you attempt to download a project that still references a Profibus slave that does not exist. The clean-up sequence is:
- Right-click each Cyclic Receive block and select Remove.
- Right-click each Cyclic Send block and select Remove.
- Open Device properties → Communication → PROFIBUS DP and uncheck Activate PROFIBUS DP. This removes the slave from the project entirely.
- Compile and download. SIMOCODE ES will report "Project does not contain a DP slave" — this is the expected result.
Fault Reset Behavior and Cooling Time
There are four reset modes in SIMOCODE Pro:
| Mode | Behavior | Standalone recommendation |
|---|---|---|
| Manual reset, edge triggered | One press of Reset clears the fault after cooling time | Recommended for unattended MCC buckets |
| Manual reset, level triggered | Reset button must be held until cooling time expires | Use only for very critical loads |
| Auto reset | Fault self-clears after cooling time | Avoid — defeats the purpose of a fault indicator |
| Remote reset via bus | Reset bit from PLC | Not applicable in standalone mode |
Set the reset mode in Protection functions → Overload → Reset to Manual, edge-triggered. Verify that the cooling time is long enough to let the motor cool — a typical 4-pole 11 kW TEFC motor needs about 5 minutes. If the operator can re-trip the motor within 10 seconds of a Reset, the cooling time is set too short.
Step-by-Step Configuration Procedure
- Open SIMOCODE ES V20 and create a new project for the device order number 3UF7000-1A.0-0 (or -1A.0-1 for PROFINET variant).
- Select the Direct starter (reversing starter disabled) function template.
- Open Control stations and set PLC/DP control station to Inactive. Enable Local 1 (PC) for diagnostics, Local 2 (DI on device) for commands, and Local 3 (operator panel) to Inactive.
- Open Control function → Sources for commands and confirm the ON/OFF source is the hard-wired inputs (Input 1 for Stop, Input 2 for Start).
- Open the graphic editor. Delete the Cyclic Receive 0 block. Re-wire Reset to Input 3 of the base unit.
- Delete the Cyclic Send 0 block. Re-wire QLS (Fault) to Output 2 of the base unit. Optionally re-wire QAS to Output 3.
- Open Protection functions → Overload. Enter Is1 from the motor nameplate, set trip class 10, cooling time 300 s, and select manual edge-triggered reset.
- Open Device properties → Communication → PROFIBUS DP and deactivate the slave. Compile the project.
- Connect the PC to the base unit with the USB cable (3UF7940-0AA00-0). In SIMOCODE ES, click Load to device and accept the default node address 0.
- Power-cycle the base unit to activate the new configuration.
Verification and Commissioning
After download, run a structured functional test before the unit is inserted into the live MCC.
- Power-on test: Apply 24 V DC control power. The green "Ready/On" LED on the base unit should illuminate within 1 second. The red fault LED should be OFF.
- No-load start: Briefly press the Stop pushbutton (verify it is wired NC, not NO). Press Start. The contactor should pull in. Output 3 (run light) should energize.
- Stop test: Release Start, then press Stop. The contactor should drop out immediately.
- Fault simulation — overload: With the motor stopped, open SIMOCODE ES → Test → Force fault → Overload. The fault LED should latch ON, Output 2 should energize, and the contactor should be blocked from re-starting.
- Reset during cooling: Press Reset immediately after the fault. The fault should remain latched (cooling time not yet elapsed).
- Reset after cooling: Wait 5 minutes (or the configured cooling time). Press Reset. The fault should clear. The fault LED should go OFF, Output 2 should de-energize, and a new Start command should be accepted.
- Power-loss test: Remove 24 V control power with the contactor pulled in. Restore power. The contactor must NOT restart automatically — SIMOCODE Pro C will be in the stopped state, requiring a fresh Start command. This is the correct fail-safe behavior.
Troubleshooting Matrix
| Symptom | Probable cause | Corrective action |
|---|---|---|
| Base unit green LED off, no response | 24 V DC missing or reversed | Verify polarity at terminals A1/A2; check 24 V supply under 5 % ripple |
| Fault LED latches immediately on power-up | Configuration mismatch with current measuring module rating | Check that the 3UF7100 module range matches motor FLA; re-load project |
| Reset pushbutton does not clear fault | Reset still wired to Cyclic Receive bit | Re-check graphic editor; ensure Cyclic Receive 0 is deleted and Reset block is bound to Input 3 |
| Reset clears fault but motor will not restart | Cooling time not yet expired, or ON command is still being routed from PLC source | Wait out cooling time; verify control station source for ON command is Local 2 |
| Contactor chatters or pulls in then drops out | Under-voltage, or contactor coil draws current on the same 24 V rail as the SIMOCODE outputs | Separate 24 V rails for SIMOCODE and contactor; add flyback diode across the contactor coil |
| SIMOCODE ES cannot connect to the device | USB driver not installed, or Local 1 control station disabled in project | Enable Local 1 in the project, re-download, or use the front service port with a driver that supports 3UF7940-0AA00-0 |
| Fault lamp lights but no fault code on operator panel | No operator panel fitted and Local 3 disabled — this is normal | Read the fault code from SIMOCODE ES via Local 1 / USB instead of the panel |
| Phase-failure trip on a healthy three-phase supply | One current measuring module phase wire loose | Tighten the three phase wires to the 3UF7100 module; verify torque per Siemens datasheet |
Spare-Unit Best Practices
When the SIMOCODE Pro C is held as a hot spare, observe the following field-proven rules:
- Store the unit with the 3UF7100 current measuring module already bolted to it, wired with short pigtails. The module range must match the bucket it is intended for.
- Keep the latest project file (the .zap17 or .zap20 export) in a labeled envelope on the spare. The same file is also stored in the project archive.
- Pre-set S1 and S2 to fixed levels in software so the spare can be installed without switch adjustment.
- Mark the bucket door with the required motor nameplate data. The maintenance crew must update Is1 in the project if the new motor has a different FLA.
- After every swap, repeat the full verification procedure from this article before re-energizing the feeder.
Field Commissioning Checklist
[ ] Motor nameplate data recorded: kW, V, A, rpm, cos phi, service factor
[ ] Current measuring module range matches motor FLA
[ ] SIMOCODE ES V20 project created, direct starter template
[ ] Control station S7/DP disabled, Local 2 enabled
[ ] Reset block wired to Input 3
[ ] QLS block wired to Output 2
[ ] Is1 entered, trip class selected, cooling time set
[ ] PROFIBUS slave deactivated in project
[ ] Project compiled and downloaded to device
[ ] Power-on LED check passed
[ ] No-load start/stop test passed
[ ] Forced overload fault latches
[ ] Reset after cooling time clears fault
[ ] Power-loss test confirms no auto-restart
[ ] Fault indicator lamp and run lamp wired and tested
[ ] Spare unit labeled with project filename and revision date
Why is the Reset pushbutton not clearing a latched fault in standalone mode?
The Reset block is still bound to the Cyclic Receive word from the (now absent) PROFIBUS master. In SIMOCODE ES delete the Cyclic Receive 0 block and re-wire the Reset function block to Input 3 (Base Unit). The fault will only clear after the configured cooling time has elapsed.
How do I select the Local 2 control station without using the S1/S2 hardware switches?
Open the device properties, expand Control station selector, and set S1 to fixed level 0 and S2 to fixed level 1. The hardware switches are then ignored and Local 2 is permanently active. This is the recommended approach for a stand-alone spare unit.
Can I leave PROFIBUS connected and just ignore the cyclic data?
No. The base unit's PROFIBES watchdog will expire within a few bus cycles and SIMOCODE will trip the motor with a "communication fault". The PROFIBUS slave must be deactivated in the project (Device properties → Communication → PROFIBUS DP → deactivate) before downloading to the device.
What is the correct trip class for a standard 4-pole induction motor?
CLASS 10 is the default and is correct for standard TEFC induction motors started direct-on-line. Use CLASS 20 for high-inertia loads such as large fans or centrifuges, and CLASS 30 for very long starting times (more than 30 s). Trip class sets the I²t curve used by the thermal model.
How long should the cooling time be set to?
Match the motor thermal time constant, which for a standard TEFC motor is roughly 3–5 minutes. The default 300 s (5 minutes) is appropriate for most applications. If the operator can re-trip the motor within seconds of a Reset, the cooling time is too short and the motor is being re-started hot.
Does this configuration work for SIMOCODE Pro V and PROFINET variants?
Yes. The same parameter changes apply. For a PROFINET variant, open Device properties → Communication → PROFINET instead of PROFIBUS DP and deactivate the PROFINET device. The base-unit wiring, the Reset block, the QLS block, and the overload settings are identical across all SIMOCODE Pro variants.