Siemens MICROMASTER 420 Not Starting (No Fault Code): A Practical Diagnostic Workflow

Oct 21, 2026

Leave a message

Chen Tuo
Chen Tuo
Chen Tuo, Senior Automation Engineer at Shenzhen Chentuo Technology, has 15+ years of hands-on PLC, HMI, and VFD experience with Siemens, ABB, Allen-Bradley, Mitsubishi, Omron, and Schneider, supporting automation projects in 80+ countries.

An industrial frequency drive with an operator keypad installed inside a control cabinet

A Siemens MICROMASTER 420 is powered on. Its Basic Operator Panel (BOP) displays information normally, and no fault code is visible. Yet the motor does not start when the machine controller requests operation. Where should maintenance begin?

 

A drive with no displayed fault is not necessarily ready to run. The selected command source, frequency reference and stop conditions must agree with the machine's control design. A normal display alone does not establish that those conditions are satisfied.

 

This guide follows the control signals, compares expected commands with observations and explains what to record before considering replacement.

 

Safety and scope: This article covers a powered MM420 with an accessible display and no obvious active F code. It is a diagnostic planning resource, not an electrical testing procedure. Only qualified personnel should inspect wiring, work inside cabinets, change settings or perform operational tests under the applicable Siemens instructions and site safety procedures.

 

Quick Triage: Which MM420 No Start Condition Are You Seeing?

Start with the observed drive state, not just the PLC program.

Observed condition

First investigation

Next step

BOP is blank

Supply, panel or hardware condition

Qualified electrical assessment

An F code or A warning is visible

Recorded fault or alarm

Existing fault code article

BOP is normal but the drive does not run

Command source and actual command

Run command checks

Command is recognized but frequency remains zero

Selected setpoint and scaling

Frequency reference checks

Command and reference appear valid, but output is inhibited

Stop and enable conditions

Stop and inhibit checks

Response changes between attempts

Event history and control states

Common scenarios

 

Drive Powered On but No Fault Displayed

A responsive BOP indicates that some drive electronics and display functions are operating. It does not prove that the inverter has accepted an ON command or enabled its output. Record the displayed state, control mode and whether the event occurs only in automatic operation.

 

BOP Is Blank or a Fault Code Appears

A completely blank panel is outside the main scope of this workflow. Likewise, an active F code needs a fault investigation. Our earlier Siemens MICROMASTER 420 fault codes and replacement guide covers fault meanings, alarms, evidence preservation and repair decisions. This guide instead focuses on no response without a displayed fault.

 

Display Is Normal but Output Frequency Remains Zero

First identify which frequency is being displayed. A selected reference, a ramped setpoint and the inverter's reported output frequency are not interchangeable readings. Zero on one display cannot, by itself, identify an analog input problem or a failed output stage.

 

Understand the Control Conditions Required to Start an MM420

RUN Command vs. Frequency Setpoint

A run command requests that the inverter operate. A frequency setpoint tells it the speed reference to use when operation is permitted. These are separate parts of the control process. A PLC can provide a valid analog reference while no effective ON command is present. Conversely, a run request may be recognized while the selected reference remains at zero.

 

Ask three questions: Is the command accepted? Is the reference selected? Is running permitted?

 

BOP, Terminal and Communication Control Are Different

The MM420 can receive commands through the operator panel, assigned terminals or supported communication arrangements. A PLC may control terminals or communicate through an installed interface, depending on the application. Therefore, a PLC output indicator alone cannot establish that the inverter is listening to that source.

 

Use the original commissioning record to identify the intended ON/OFF and speed sources.

 

Why a Drive Can Remain Stopped Without a Fault Code

A fault trip differs from a normal stop, an absent ON command or an inhibit. These states can prevent operation without an F code. Drive status information provides stronger evidence than a normal display.

 

Step 1: Check the Run Command and Its Selected Source

Review P0700 and P0719 Before Assuming Terminal Control

P0700 selects the command source in the standard configuration. P0719 can select command and frequency sources through an additional control selection arrangement. Their relationship matters, especially on machines with local and remote operating modes or previously customized parameter sets.

 

Compare settings with the intended mode. Serial control requests do not necessarily appear on digital inputs. Importantly, Siemens documentation notes that changing P0700 can reset associated input assignments to defaults in some configurations. Record the original settings and obtain authorization before any change.

 

Confirm Digital Input Assignment with P0701 to P0703

For terminal controlled installations, P0701, P0702 and P0703 define functions assigned to digital inputs. A signal arriving at an input does not necessarily represent ON/OFF1. It could have another configured function, and the actual arrangement may differ from factory defaults.

 

Compare the electrical drawing, configured function and expected PLC command. Never assume universal RUN or stop terminal assignments.

 

Use r0722 to Compare Input Status with PLC Commands

The read only parameter r0722 reports digital input states. It helps separate a command that the controller intends to send from a signal the drive actually registers. Use the applicable manual to interpret its bits.

 

Observation

What it may suggest

Evidence to examine next

PLC expects ON, but the corresponding input state does not change

Signal path or input interpretation differs from expectation

Drawings, interface state and approved electrical checks

Input state changes, but the motor remains stopped

Input may not be assigned as ON, or another condition prevents running

P0701 to P0703, status word and enable conditions

The PLC uses communication; the observed terminal remains unchanged

The terminal may not be the active command path

P0700, P0719 and configured interface

 

An active bit indicates input state, not an accepted motor start command.

 

Step 2: Check the Frequency Setpoint and Analog Input

Verify P1000 and the Active Frequency Reference

P1000 selects the frequency setpoint source in the applicable configuration. The reference may come from an analog input, a motor potentiometer function, a fixed frequency or communication. Related selections such as P0719 may also affect which source is effective.

 

Confirm that selection matches the control design. A PLC analog output is irrelevant if another reference is selected.

 

Check Analog Input Monitoring and Scaling

On versions documented with the MM420 voltage analog input, r0752 shows the smoothed input voltage before scaling, while r0754 shows the scaled analog value. P0757 to P0760 define the scaling points, and P2000 provides the reference frequency used in the normalization.

 

For example, a 0 to 10 V signal mapped to 0 to 100 percent differs from one mapped to a narrower range or deadband. The actual mapping matters.

 

Check P0756 against the correct manual and hardware version. Siemens' MM420 Version B1 parameter list describes unipolar voltage input options for this parameter. Do not copy a generic 4 to 20 mA setting from another inverter family or assume a current signal is directly supported without confirming the interface and signal conditioning.

 

Compare Setpoint and Actual Frequency

The displayed values must be interpreted individually. In Siemens' Version B1 documentation, r0020 is the frequency setpoint after the ramp function generator; r0021 is an actual frequency value excluding certain compensation effects; and r0024 reports actual inverter output frequency including those effects. They are related but not identical.

 

Read only value

Why it is useful

r0752

Observed voltage at the analog input before scaling

r0754

Analog value after scaling, as a percentage

r0020

Ramped frequency setpoint

r0021

Actual frequency without specified compensation effects

r0024

Reported inverter output frequency

 

A nonzero input with a zero selected setpoint suggests different checks from a nonzero reported output with a stationary motor. Neither proves hardware failure.

 

Step 3: Investigate Run Inhibit and Stop Conditions

Understand OFF1, OFF2 and OFF3

These commands have different stopping behaviors. OFF1 generally uses the selected ramp down process after the ON command is removed. OFF2 removes drive pulses and allows the motor to coast. OFF3 requests a rapid ramp down using its defined stopping behavior. The active command sources depend on configuration.

 

Do not treat OFF2 or OFF3 as universally wired to a particular terminal. Review how the machine was commissioned and which control paths are currently relevant.

 

Identify Active Inhibit or Enable Conditions

Where supported, r0052, the inverter status word, provides evidence about readiness, running state, active fault or warning indications, OFF2, OFF3 and ON inhibit. For advanced configurations, relevant source assignments may include P0844, P0848 and P0852. The appropriate parameter list explains how those functions interact.

 

A valid frequency reference and an expected ON command do not override a stop condition. Compare the observed status with the approved machine sequence before considering a parameter change.

 

Avoid Bypassing Machine Interlocks

Never bypass an emergency stop, interlock or pulse inhibit to test motor operation. Electrical work and controlled tests require qualified personnel following site procedures and the machine safety design.

 

Troubleshooting Common MM420 No Fault Scenarios

The scenarios below are illustrative and are not customer repair records.

 

Scenario A: BOP Control Works, but PLC Control Does Not

Suppose a machine has a documented history of operating correctly under authorized local control, but fails to respond in automatic mode. The contrast points toward the difference between the two control paths, not automatically toward a defective PLC.

 

Compare the intended command source, P0700 and P0719 configuration, input function assignments and whichever status information is available. If the PLC uses terminal control, r0722 can indicate whether the expected input changes. If communication is used, the investigation instead follows that interface and its configured command source. Avoid switching modes on an operating machine merely to recreate the symptom.

 

Scenario B: The Drive Stops Responding After Replacement

A new or spare MM420 may carry the same product family name without having the same complete order number or stored settings. A replacement may have power and a normal panel display while responding differently to the original machine signals.

 

Compare the old and replacement MLFB, motor and supply ratings, parameter backup, selected command source, setpoint source and input assignments. Also check any communication options or accessories. Record what changed rather than assuming a similar enclosure or kilowatt rating proves configuration equivalence. This comparison can establish whether further commissioning review is required before blaming the replacement unit.

 

Scenario C: The MM420 Starts Intermittently

When the machine sometimes starts normally, capture the circumstances of both successful and unsuccessful requests. Record the operating mode, time, commanded state, input or communication status, relevant drive status and recent maintenance activities.

 

A useful event log has columns for time, expected command, observed input, drive status and associated machine event. Look for consistent differences. For example, an input that follows the command during successful starts but not during unsuccessful requests deserves investigation of that signal path. Without records, blaming an aging component is speculation.

 

Scenario D: The Display Shows Frequency but the Motor Does Not Run

First establish whether the displayed frequency is a requested setpoint or an output related value. Compare r0020, r0021 and r0024 as available, alongside the drive running state. If the inverter reports an output condition yet the shaft remains stationary, the motor circuit, motor condition, mechanical system and reporting context may need specialist evaluation.

 

A frequency display neither proves shaft movement nor identifies a failed power stage.

 

How to Verify the Diagnosis and Know When to Escalate

Document the Before and After Observations

An equipment record should identify the symptom and the evidence supporting a conclusion. Capture original parameter values, operating mode, expected commands, observed status and any authorized changes. After corrective work, record the comparable observations again. A single successful start does not establish root cause.

 

Perform Controlled Verification After Authorized Corrections

Qualified personnel should verify the relevant operating sequence under approved site procedures. Depending on the application, that may include the intended start and stop behavior, response to frequency commands and operation of required protective functions. Use a procedure specific to the machine.

When Repeated Resetting Is the Wrong Approach

Fault acknowledgement, restoring factory defaults and correcting a control problem are three different actions. A factory reset may remove customized terminal assignments, control selections and motor settings. For a drive showing no active fault, resetting parameters before preserving the original configuration can make diagnosis harder, not easier.

 

Information to Prepare for Professional Assessment

Keep the complete MLFB, available parameter backup, firmware or manual version, relevant drawings, event log, motor information and evidence of recent changes together. These materials help an engineer decide which observations remain uncertain and whether further inspection is justified. Obtain photos only when doing so is safe.

 

If the MM420 Still Won't Start: Prepare for a Replacement Enquiry

Separate External Control Problems from Suspected Drive Problems

Replacement should follow evidence, not frustration. If commands are absent or configuration does not match the machine design, continue the appropriate control investigation. If qualified assessment leaves a suspected drive problem unresolved, consider repair and sourcing in parallel. Our MM420 fault code and replacement guide examines broader repair and replacement decisions without duplicating this signal focused workflow.

 

Identify the Exact Drive Before Discussing a Replacement

The Siemens order number, or MLFB, matters more than the family name alone. A buying request should include the full nameplate designation, input rating, output current, motor requirements and important control or communication interfaces. Similar power ratings do not guarantee an electrical, mechanical or software match.

 

Share the Configuration Needed for Model Matching

As an industrial automation product supplier, CHENTUO lists Siemens variable frequency drives and accepts equipment enquiries. Customers considering a replacement can submit the original model, intended control method, application, quantity and destination through the CHENTUO quotation form.

 

A SINAMICS G120 or another series may be an option for evaluation, but not an automatic direct replacement. Electrical ratings, terminals, communication, physical installation and commissioning requirements must be checked. Confirm availability, timing and suitability for the particular enquiry.

 

FAQ

 

 

Siemens MICROMASTER 420 Not Starting (No Fault Code): A Practical Diagnostic Workflow

Why is my MICROMASTER 420 not starting even though no fault is displayed?

The drive may not have received an effective run command, may be using a different frequency source or may have an active stop or inhibit state. Compare the configured control sources with the observed input and drive status before assuming hardware failure.

What is the difference between P0700 and P1000?

P0700 concerns the command source, whereas P1000 concerns the frequency setpoint source in the applicable configuration. P0719 and other advanced settings may also influence source selection. Confirm the actual arrangement using the manual for the installed drive.

Why does my MM420 run from the BOP but not from the PLC?

A difference between local and automatic operation suggests the command paths or their configuration may not match. Examine the source selection, assigned input functions and applicable status values. Prior local operation does not independently prove every part of the drive is healthy.

How can I tell whether the drive recognizes a digital input?

For applicable versions, r0722 reports digital input states. Compare the relevant state with the machine's expected command and the function assigned to that input. An active input is not necessarily an effective run command.

Why does an MM420 show zero frequency without a fault code?

It may be displaying a zero setpoint or a stopped output state. Identify the displayed parameter first, then compare the active reference and operating status. Zero frequency alone does not identify the defective component, if any.

What should I send when requesting an MM420 replacement quote?

Provide the complete Siemens MLFB, nameplate information when safely available, motor and application details, existing control interface, quantity and delivery destination. If considering a different drive series, include the relevant I/O, communication and installation requirements.

 

Final Checklist: Trace the Signal Before Replacing the Drive

When a MICROMASTER 420 is not starting with no fault code, follow the evidence in order: identify the displayed state, confirm the selected command source, compare expected RUN signals with actual inputs, check the frequency reference and inspect stop or inhibit status. Record the outcome before any authorized correction or further assessment.

 

A missing command calls for a different response than an unexplained output condition. If evidence points toward an equipment replacement, share the complete drive identification and application details with CHENTUO to discuss available Siemens VFD sourcing options.

 

Technical reference: Siemens MICROMASTER 420 Parameter List, Version B1. Parameter definitions and functions should always be verified against documentation for the actual installed drive and firmware version.

 

Free consultation

Send Inquiry