
You have an old Siemens SMC20 module, a motor nameplate, or an encoder specification, but can you confidently order a replacement? The answer depends on what those details actually prove.
The Siemens SMC20 is a SINAMICS sensor module used to evaluate supported encoder feedback signals from motors without a DRIVE-CLiQ interface. However, identifying the module is only the beginning. Correct selection depends on the encoder interface, electrical requirements, system configuration, and complete order number.
This guide helps maintenance engineers, automation specialists, and industrial buyers verify SMC20 encoder compatibility, assess replacement requirements, and prepare a useful quotation request before purchasing.
1. When Is an SMC20 the Right Choice?
What the SMC20 Does in a SINAMICS S120 System
The SMC20 Sensor Module Cabinet-Mounted evaluates supported encoder signals and communicates feedback information through DRIVE-CLiQ to a compatible drive control system.
In a typical SINAMICS S120 application, the functional relationship is:
Motor encoder → SMC20 sensor module → DRIVE-CLiQ → SINAMICS control system
This is a functional illustration, not a wiring diagram.
The SMC20 is neither a motor drive nor a power module. Its role is to provide an interface between supported encoder feedback and the drive system.
For a broader explanation of these components, read our Servo Drive Components Explained article.
SMC10 vs SMC20 vs SMC30: Match the Feedback Signal
The first selection criterion is the actual encoder signal, not the motor manufacturer or connector appearance.
|
Sensor module |
Initial feedback category |
Important verification |
|
SMC10 |
Resolver feedback |
Verify resolver specifications and system requirements |
|
SMC20 |
sin/cos 1 Vpp, EnDat 2.1, supported SSI combinations |
Confirm encoder signals, protocol conditions, and firmware |
|
SMC30 |
TTL/HTL incremental feedback and supported SSI encoders |
Confirm electrical levels, SSI configuration, and interface requirements |
According to Siemens documentation, SMC20 supports SSI encoders with incremental sin/cos 1 Vpp signals under specified firmware conditions. Therefore, an encoder described only as "SSI" cannot automatically be assigned to SMC20.
Similarly, SMC30 should not be classified as an incremental encoder module exclusively.
Important: This comparison identifies a possible module category. It does not establish compatibility with a particular encoder or project.
When the Available Information Is Insufficient
Three common descriptions cannot support a final selection:
- Motor brand only: Obtain the complete motor model and feedback specifications.
- Matching connector appearance: Obtain connector assignments and electrical interface documentation.
- Absolute encoder only: Identify the actual communication protocol and required signal combination.
If these details are missing, continue with a compatibility record rather than selecting a module by appearance.
2. Build an SMC20 Encoder Compatibility Record
A compatibility record should show what is known, which document supports it, and which requirements remain unverified.
Identify the Motor and Actual Encoder
Start with the complete motor identification, including its option codes.
The motor nameplate establishes the installed motor configuration, but it may not provide every detail required to identify the encoder interface.
Record the encoder model or feedback option from the applicable manufacturer documentation. If available, include the existing drive configuration and historical maintenance records.
Previous project drawings can help identify the original configuration. However, repairs and modifications may have changed the installed hardware.
For older machines, request accessible nameplate photographs and existing technical records instead of asking purchasing personnel to dismantle equipment to identify an encoder.
Verify Signals, Supply and Cable Requirements
Four technical areas deserve separate verification.
1. Encoder protocol and signal combination
Identify whether the encoder uses sin/cos 1 Vpp, EnDat 2.1, SSI, or another interface.
For SSI applications, determine whether the required incremental signals are available and whether the applicable SMC20 firmware supports the combination.
A matching protocol name alone is insufficient.
2. Encoder power requirements
Compare the encoder's supply voltage and current requirements with the applicable sensor module specifications.
Do not confuse the module's own power consumption with the power available to the connected encoder.
3. Connector and pin assignments
Compare the documented electrical assignments, including signal connections, supply connections, and shielding requirements.
Two connectors may physically fit while having different electrical assignments.
4. Encoder cable specifications
Identify the existing SMC20 encoder cable, cable documentation, shielding arrangement, and relevant installation requirements.
Cable length, condition, and routing must satisfy the applicable manufacturer documentation and project requirements.
Do not assume that a cable is suitable simply because it was previously used with another encoder.
Record the Control Unit and Versions
The compatibility record must also identify the system environment.
Collect the complete Control Unit model, relevant firmware information, sensor module identification, and available engineering project documentation.
Firmware information matters because certain interface capabilities have version requirements.
Do not treat the module hardware version, Control Unit firmware, and engineering software version as interchangeable information.
Use the following record to organize the evidence.
|
Verification item |
Customer information |
Evidence |
Status |
|
Motor model |
Full type code |
Nameplate/manual |
Confirmed / Pending |
|
Encoder model |
Feedback identification |
Encoder documentation |
Confirmed / Pending |
|
Signal interface |
Protocol and signal combination |
Encoder datasheet |
Confirmed / Pending |
|
Encoder supply |
Voltage and current |
Technical specifications |
Confirmed / Pending |
|
Connector and cable |
Pin assignments and cable details |
Wiring documentation |
Confirmed / Pending |
|
Control Unit |
Complete model |
System record |
Confirmed / Pending |
|
Relevant versions |
Firmware and project references |
Device/project records |
Confirmed / Pending |
A completed field is not necessarily a confirmed field. Record unresolved questions explicitly.
3. Rexroth MHD: Verify Feedback Before Assuming Compatibility
A frequent cross-brand question concerns SMC20 Rexroth MHD compatibility.
Can a Siemens SMC20 evaluate feedback from a Rexroth MHD motor?
The motor family alone cannot answer that question.
Read the MHD Motor Type Code Correctly
Bosch Rexroth MHD motors have configuration-dependent options, including feedback systems, shaft arrangements, and holding brakes.
For example, the MHD093 type-code structure in the Bosch Rexroth project planning documentation identifies these configuration elements separately.
In that documented structure, the shaft designation G and holding-brake designation 1 are not a combined encoder protocol identifier.
Reading these fields incorrectly could lead to an unsupported compatibility conclusion.
The complete motor type code must be interpreted using the documentation applicable to its specific model and revision.
Separate Known Facts From Assumptions
Consider this illustrative compatibility verification example.
|
Known information |
What remains uncertain |
Required evidence |
|
Rexroth MHD motor family |
Exact installed feedback interface |
Full type code and relevant motor documentation |
|
Absolute feedback capability |
Whether the interface meets SMC20 requirements |
Encoder protocol and signal specifications |
|
Existing encoder connector |
Electrical compatibility with SMC20 |
Connector assignments and cable documentation |
|
Proposed SINAMICS system |
Supported configuration and relevant versions |
Control Unit and Siemens technical documentation |
The critical distinction is between identifying an encoder feature and proving that another system can evaluate its signals.
For example, knowing that an encoder provides absolute position information does not prove that it supports EnDat 2.1 or a suitable SSI combination.
Decide the Next Verification Action
If the encoder interface remains unidentified, request the original motor feedback documentation from the machine manufacturer, Bosch Rexroth documentation, or the responsible engineering team.
Record the unresolved interface question, required document, and person responsible for obtaining confirmation.
Do not interpret incomplete documentation as proof of incompatibility. Equally, do not approve the integration until the relevant interface requirements have been verified.
Cross-brand integration should be treated as a technical configuration decision rather than an ordinary spare-part substitution.
4. Before Replacing the SMC20, Confirm the Failure
An encoder alarm or unusual module indication does not automatically mean that the SMC20 has failed.
Before ordering an SMC20 replacement, gather the evidence supporting the replacement decision.
Collect Diagnostic Information
Record the exact alarm code and message, observed LED designation and behavior, and operating conditions when the fault occurred.
For an SMC20 red LED, note whether the indication is steady or flashing and identify the specific device being observed.
Also collect recent maintenance activity, cable changes, configuration modifications, and relevant fault history.
A photograph showing the module identification and a screenshot showing the complete diagnostic message are more useful than a description such as "encoder problem."
Separate Possible Fault Areas
|
Investigation area |
Information to record |
Relevant evidence |
|
Sensor module |
Identification, indications, fault history |
Device documentation |
|
Encoder cable |
Condition, connector details, previous repairs |
Cable drawings and inspection record |
|
Supply |
Recorded supply-related diagnostics |
Electrical documentation |
|
Configuration |
Recent changes, project and firmware information |
Engineering records |
These categories guide technical investigation; they do not establish a failure diagnosis.
Qualified personnel should perform inspections and electrical work according to manufacturer instructions and site safety procedures.
For a broader maintenance approach, see our Servo Motor Maintenance Checklist.
Once the responsible engineer has established a replacement requirement, compare the old module with the proposed unit.
5. Replacing an Existing SMC20: What Must Match?
A replacement review begins with the complete Siemens SMC20 part number, not the shortened module name.
Compare the Complete Order Number
The Siemens SMC20 order number 6SL3055-0AA00-5BA3 is listed in the Siemens product catalog.
However, the presence of this number in the catalog does not establish that every differently labeled module is interchangeable.
Use the following SMC20 replacement checklist.
|
Comparison item |
Existing module |
Proposed module |
|
Complete order number |
Record actual label |
Record candidate number |
|
Product identification |
Record product details |
Compare manufacturer documentation |
|
Relevant version information |
Record if applicable |
Verify differences |
|
System configuration |
Existing project records |
Check applicability |
|
Cable and accessories |
Existing requirements |
Confirm supplied scope |
|
Replacement approval |
Engineering status |
Confirmed / Pending |
When the old label is unreadable, consult purchasing records, maintenance documentation, and existing project files.
The SZCT Siemens Model Library provides an additional Siemens product reference, although individual model availability and listings must be confirmed.
Review the Existing Project Requirements
Even when the complete order numbers match, installation requirements remain relevant.
The responsible engineer should review the existing Control Unit, project configuration, encoder connections, and applicable commissioning documentation.
Determine whether configuration restoration, encoder identification, or project-specific validation is required.
Avoid assuming that every replacement is immediately operational without checks. Conversely, not every replacement requires rebuilding the entire drive configuration.
The necessary work depends on the existing project and the actual replacement scope.
Distinguish Three Replacement Situations
|
Replacement situation |
Primary verification |
What cannot be assumed |
|
Same specified module |
Product identity and existing project requirements |
No verification required |
|
Different module or order number |
Documented substitution and system support |
Identical functions or connections |
|
Different encoder or motor |
Complete feedback and system compatibility |
Existing approval remains valid |
Changing the encoder or motor introduces a different technical question from replacing a failed sensor module.
For these changes, return to the compatibility record in Section 2.
If a planned modernization also involves changing the drive platform, our SINAMICS G120 vs G220 Guide addresses broader migration considerations.
6. What to Send for an Accurate SMC20 Quotation
A useful SMC20 quotation starts with accurate component identification and clear purchasing requirements.
For an existing replacement, provide the complete order number, quantity, destination country, and required delivery date.
If the order number is uncertain, include a readable nameplate photograph and explain the missing information.
For a new integration or changed configuration, attach the relevant motor and encoder details when available.
Separate Product Condition From Compatibility
Before accepting a quotation, confirm the proposed product condition, included accessories, packaging, and applicable warranty terms.
These are purchasing considerations, not evidence of encoder compatibility.
Also clarify whether the quotation covers only the specified module or includes other items.
Do not assume that a DRIVE-CLiQ cable, encoder cable, or other accessory is included unless explicitly stated.
Copyable SMC20 Enquiry Template
Use this template when contacting an industrial automation supplier.
Subject: Siemens SMC20 Quotation Request
Required part number:
Quantity:
Existing module details:
Motor / encoder model, if relevant:
Application: Replacement or new integration
Destination and required delivery date:
Photos or technical documents available:
Additional compatibility questions:
Mark unavailable information as "To be confirmed" rather than guessing.
At SZCT Automation, customers can submit component requirements through our Request a Quote page.
For supplementary details or documents, use our Contact Us page.
Submitting an enquiry allows the requirements to be communicated. Specific availability, commercial terms, and technical suitability still require confirmation.
7. What to Verify After an SMC20 Replacement
Purchasing and installing a replacement module do not automatically complete the maintenance task.
The responsible engineer should establish verification requirements using the applicable Siemens documentation and machine project records.
Define the Acceptance Checks
Depending on the project, verification may include:
- Recognition of the connected encoder and relevant configuration.
- Review of applicable diagnostics and fault status.
- Confirmation of expected position or speed feedback.
- Verification of relevant project settings and feedback behavior.
- Authorized functional testing against documented machine requirements.
The applicable checks depend on the drive configuration and replacement scope.
No universal motion instruction, test threshold, or parameter setting should be substituted for the approved commissioning procedure.
Personnel must also follow machine safety requirements before any functional testing.
Preserve a Replacement Record
Record the removed and installed module order numbers, relevant versions, project documentation references, verification results, and completion date.
Include the responsible engineer and any unresolved issues.
Retain appropriate identification photographs and diagnostic records so that future maintenance teams can trace what changed.
A clear replacement record can also reduce uncertainty during subsequent spare-part enquiries.
FAQ

What does a Siemens SMC20 module do?
How do I choose between SMC10, SMC20 and SMC30?
Can an SMC20 work with a Rexroth MHD motor encoder?
Are SMC20 modules with different order-number suffixes interchangeable?
Does a red SMC20 LED mean the module must be replaced?
Can I reuse the existing SMC20 encoder cable?
9. Make Your Next SMC20 Purchase Evidence-Based
If the required Siemens SMC20 order number and replacement requirements have already been confirmed, prepare the quantity and delivery details for a quotation.
If encoder compatibility, order-number differences, or project requirements remain unresolved, identify the missing evidence before approving the purchase.
Request a Quote for Your Confirmed SMC20 Part Number
For incomplete specifications or supplementary questions, contact SZCT Automation with the information currently available.

