Siemens MM440 I/O Board Compatibility with MM430 Drives

David Krause13 min read
SiemensTechnical ReferenceVFD / Drives
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview of the MICROMASTER 4 I/O Architecture

The Siemens MICROMASTER 4 (MM4) inverter family — covering the MM410, MM411, MM420, MM430, and MM440 — uses a common control board footprint that integrates digital and analog I/O, relay outputs, the PTC/KTY sensor input, and the RS485 serial interface. The MM430 (pump / fan / HVAC profile) and the MM440 (general-purpose vector control) are mechanically and electrically aligned so that the I/O printed-circuit board can physically mount in either inverter. The control board assembly is identified by Siemens spare-part number 6SE6400-7AA00-0BA0 and is referenced in the MICROMASTER 4 spare-parts documentation.

Cross-mounting is technically possible because the connector geometry, terminal pitch, and ribbon-cable pin-out to the power stack are identical. What differs between the two drives is the firmware interpretation of those terminals. Each parameter that is wired to a physical input is mapped through the drive's parameter tree, and the MM430 and MM440 parameter trees route the same hardware to different functions. Therefore, an I/O board that has been verified on an MM440 cannot be assumed to be functionally good on an MM430 — and vice-versa — without re-running the verification under the target drive's firmware.

Although the I/O PCB itself is hardware-compatible across the two models, a board that has been damaged by an external wiring fault, an over-voltage on the analog input, or a shorted relay contact can appear to pass a basic power-on test and still fail in service. Always combine a static check with at least one dynamic I/O exercise on the target firmware.

MM430 vs MM440 Terminal Map

The control board exposes the following user terminals on the front strip of the MM430 and MM440 inverters. Pin numbering and signal naming are identical on both drives; only the default function assigned to each pin is firmware-driven.

Terminal Signal MM440 default function MM430 default function
1 Digital input 1 (DIN1) ON / OFF1 (P0701[1] = 1) Fixed setpoint bit 0 (P0701[1] = 15)
2 Digital input 2 (DIN2) Reverse / ON reverse (P0702[1] = 12) Fixed setpoint bit 1 (P0702[1] = 16)
3 Digital input 3 (DIN3) Fault acknowledge (P0703[1] = 9) Fault acknowledge (P0703[1] = 9)
4 Digital input 4 (DIN4) Fixed frequency bit 0 (P0704[1] = 15) PID enable (P0704[1] = 6)
5 Digital input 5 (DIN5) Fixed frequency bit 1 (P0705[1] = 16) External trip (P0705[1] = 21)
6 Digital input 6 (DIN6) Fixed frequency bit 2 (P0706[1] = 17) Watchdog acknowledge (P0706[1] = 65)
7 Digital output 1 (DOUT1) Drive ready (P0731 = 52.3) Drive running (P0731 = 52.2)
8 Digital output 2 (DOUT2) Drive fault (P0732 = 52.6) Drive fault (P0732 = 52.6)
9 / 10 +24 V out / 0 V Auxiliary supply for DIN Auxiliary supply for DIN
11 Analog input 1+ (AIN1) Setpoint (P0756[0] = 0/1, 0–10 V or 0/4–20 mA) PID setpoint (P0756[0] = 0)
12 Analog input 2+ (AIN2) Actual value (P0756[1] = 2, 0–10 V) PID feedback (P0756[1] = 2)
13 / 14 +10 V ref / 0 V Potentiometer supply Potentiometer supply
15 Analog output 1 (AOUT1) Output frequency (P0771 = 21) Output frequency (P0771 = 21)
16 / 17 Analog output 2 / 0 V Output current (P0772 = 27) PID setpoint (P0772 = 229)
18 / 19 / 20 Relay 1 (NO/NC/COM) Drive fault (P0732 relay assignment) Drive fault (P0732 relay assignment)
21 / 22 Relay 2 (NO/COM) Drive running (P0733 = 52.2) Bypass active (P0733 = 52.7)
23 / 24 RS485 P+ / N- (USS) USS / Modbus RTU USS / Modbus RTU
25 / 26 PTC / KTY input Motor temperature Motor temperature (typically disabled)

Because the defaults diverge — particularly on DIN1, DIN2, DIN4, and the analog outputs — a board that is "known good" on an MM440 may still produce the wrong action on an MM430 if parameter factory reset is not performed before commissioning.

Spare-Part Identification: 6SE6400-7AA00-0BA0

The I/O board is released as a Siemens spare part under MLFB 6SE6400-7AA00-0BA0. This part is documented in the MICROMASTER 4 spare-parts list as a Vector Control I/O module board, and is listed as a serviceable assembly rather than a customer-replaceable field module in some regional catalogs. The spare-parts document, which exists only in the German edition, indexes the board under the vector-control family (MM420 / MM430 / MM440), confirming that the same PCB is shared across these three inverters.

Availability of the I/O board through the Siemens A&D Mall (Industry Mall) depends on regional stocking. Where it is not orderable as a discrete spare, the practical field remedy is to swap the entire drive and recover the I/O board from the failed unit for bench testing. Do not assume the board is non-replaceable in the field without first consulting the latest regional Industry Mall entry for MLFB 6SE6400-7AA00-0BA0.

Why the Boards Are Interchangeable but Not Identical in Function

The MM4 platform was designed around a single control-board footprint to keep manufacturing cost low and to make service training uniform. The hardware is identical because:

  1. The 26-position control terminal strip has the same pin-out on every MM4 model rated at 0.37 kW and above.
  2. The ribbon cable carrying the I/O logic to the power stack uses the same connector keying.
  3. The microcontroller on the control board is the same family; only the firmware image differs.

The firmware differs because the MM430 is a profile drive for pumps, fans, and HVAC (PI / PID-centric), while the MM440 is a general-purpose vector drive (speed / torque-centric). The parameter tree is loaded at production with defaults appropriate to the application, and most users never re-assign them. Consequently, swapping a board between an MM430 and MM440 without re-loading the parameter set will leave the inputs and outputs addressed to functions that may not be wired to the same external equipment.

Cross-Verification Procedure

Use this procedure when you have a suspect I/O board and want to determine whether the board is functional, independent of the drive in which it was originally installed.

Prerequisites

  • Known-good host drive of the target model (e.g., an MM440 to validate a board destined for another MM440).
  • 24 V isolated bench supply for digital-input pull-up verification.
  • 0–10 V source for analog-input check (potentiometer or laboratory reference).
  • 0–20 mA source for current-mode analog check.
  • Multimeter, oscilloscope (for PWM noise on analog outputs).
  • STARTER commissioning tool, DriveMonitor, or the basic operator panel (BOP / AOP) to inspect parameter r0722 (DI state) and r0752 (AI voltage).

Step-by-Step

  1. Power down the host drive. Wait at least five minutes after line disconnect so the DC-bulk capacitors fall below 50 V (verify at the DC+ and DC- test points). The I/O terminals themselves are at safe SELV levels, but do not hot-plug the control board.
  2. Remove the suspect I/O board from the source drive by releasing the two retaining screws on the front of the housing, disconnecting the 26-position terminal block, and lifting the ribbon-cable connector. Keep the ribbon cable seated on the host drive if you are only swapping the I/O PCB; the cable itself is part of the host assembly.
  3. Inspect the PCB under magnification for: burnt relay contacts, cracked solder joints on the terminal pins, electrolytic capacitor bulging near the 24 V regulator, and PCB discoloration around the analog-input op-amps. Any of these is grounds for rejection, not a candidate for cross-mounting.
  4. Install the suspect board on the host drive, re-seat the ribbon, and torque the retaining screws. Reconnect the terminal block.
  5. Power the host drive and reset it to factory defaults: set P0010 = 30, P0970 = 1 to trigger a full parameter reset. The drive will load the firmware-appropriate defaults for the host model.
  6. Verify each digital input by forcing +24 V on each of DIN1…DIN6 one at a time and reading r0722 (the DI status word) on the BOP. The corresponding bit must toggle.
  7. Verify each digital output by forcing P0731 to 53.0 (DOUT forced high) and measuring the DOUT1 voltage. Reset to the default after the test.
  8. Verify the analog inputs by applying 0 V, 5 V, and 10 V to AIN1+ and reading r0752[0]. A linearity check at three points is recommended; deviation > 2 % of full scale indicates an op-amp or ADC fault. Repeat for AIN2.
  9. Verify the analog outputs by commanding fixed values through P0771 and P0772 (forced = 1) and measuring AOUT1 and AOUT2 against the calibrated multimeter.
  10. Verify the relay outputs by commanding a state through the BOP and listening for the click, then measuring contact resistance with the multimeter on the bench supply.
  11. Verify the RS485 port by looping terminals 23 and 24 back to terminals 24 and 23 of a USS master and confirming echo with DriveMonitor.

What the Verification Tells You

Test result Interpretation Recommended action
All DI bits toggle, AI linear, relays click, RS485 echoes Board is functionally good Return to service, document the test on the maintenance record
One DI stuck Optocoupler failure on that input Replace the board; field repair not economical
AIN1 reads offset > 100 mV at 0 V Analog-front-end drift or ESD damage Replace the board
DOUT1 will not pull low (stuck high) Open-collector transistor short Replace the board
Relay chatters on power-up Coil driver or sense resistor fault Replace the board
RS485 echo garbled or absent Bus transceiver failure Replace the board
All tests pass but drive still faults F0001 / F0002 on the bench I/O not the root cause; check power stack Investigate the host drive, not the I/O PCB

Re-Commissioning the Target Drive After a Board Swap

After verifying the I/O board, install it into the destination inverter and run the following sequence so that the firmware mapping is consistent with the destination drive's function:

  1. Apply power and read the firmware version with r0018. Confirm that the firmware release supports all features the application needs (e.g., the MM430 firmware for HVAC must support PID auto-tune via P2350).
  2. Run a factory reset: P0010 = 30, P0970 = 1, and wait for the display to return to "ready."
  3. Re-enter the application-specific parameters (motor data P0300…P0311, command sources P0700, setpoint sources P1000, ramp times P1120 / P1121, PID setpoint P2200).
  4. Walk the terminal block with a multimeter and confirm that DIN and DOUT actions match the wiring diagram for the destination drive. Do not trust the previous drive's wiring record.
  5. Run an unloaded motor identification (P1910 = 1) on an MM440 vector application, or a PID auto-tune (P2350 = 1) on an MM430 pump application, before connecting the load.
  6. Document the final parameter set with STARTER / DriveMonitor and store the file alongside the maintenance record.

Common Faults After a Cross-Mount

Observed fault Most likely root cause Remedy
F0001 (overcurrent) on first run after swap Ramp time P1120 set for the wrong drive rating Re-enter ramp times from the application record
F0022 (PTC sensor) on a drive that does not use PTC MM440 default expects a PTC; MM430 default ignores it Set P0601 = 0 to disable PTC evaluation if no sensor is wired
Output frequency follows 4–20 mA but setpoint is supposed to be 0–10 V P0756[0] type mismatch Re-set P0756[0] to match the analog-input wiring of the destination drive
Digital input 4 has no effect on PID MM430 default maps DIN4 to PID enable; MM440 default maps it to fixed frequency Re-assign P0704 to match destination function
Drive reports "ready" but does not run ON command source P0700 not restored Set P0700 = 2 (terminals) or 1 (BOP) per the application
RS485 communication lost P2010 / P2011 baud rate or USS address changed during factory reset Restore P2010 = 6 (9600 baud) and P2011 = 1 (USS address 1) per the network plan

Field-Proven Caveats

  • ESD handling. The MM4 I/O board is not ESD-shielded on the terminal side. Use a wrist strap when handling the bare PCB, and never swap the board while the host drive is energized.
  • Parameter backups. Always read the current parameter set with DriveMonitor or STARTER before a swap, and again after the factory reset, so the delta is auditable.
  • Firmware pairing. Newer MM440 firmware versions add parameters (P2150 onwards) that an older I/O board's microcontroller mask may not support. Do not upgrade the firmware on a drive that hosts a suspect I/O board until the board is verified.
  • EMC filter. The internal EMC filter is on the power stack, not the I/O board. A noisy analog reading is therefore more likely a grounding or shielded-cable issue than an I/O board fault.
  • Power-stack damage. Many "I/O board" failures in service are actually caused by a shorted IGBT that back-feeds the control logic. Before condemning the I/O board, measure the bus voltage on a known-good drive to confirm the power section is healthy.

Decision Matrix: Replace the Board, Replace the Drive, or Swap and Verify

Condition Recommended action
Spare MLFB 6SE6400-7AA00-0BA0 in stock, identical host model, scheduled downtime available Replace the board, then verify and re-commission
Spare board in stock, host models differ (MM430 vs MM440) Cross-mount is possible; run the verification procedure on the destination drive firmware
No spare board in stock and not orderable Replace the drive; recover the I/O board from the failed unit for bench verification and stocking as a service spare
Drive > 10 years old with obsolete firmware and no backup Replace the drive and migrate to a current-platform inverter (SINAMICS V20 or G120C)

FAQ

Is the Siemens MM430 I/O board the same hardware as the MM440 I/O board?

Yes. The I/O printed-circuit board is mechanically and electrically identical and is shared with the MM420 and MM440 vector-control family. Siemens lists the board under spare-part number 6SE6400-7AA00-0BA0 in the MICROMASTER 4 spare-parts document. Firmware differences mean the same hardware is mapped to different default functions, so a known-good board must always be verified on the target drive's firmware before being placed in service.

Can I bench-test an MM430 I/O board on an MM440 inverter?

Yes, for hardware verification. Mount the suspect MM430 board on an MM440, run a factory reset (P0010 = 30, P0970 = 1), then exercise each digital input via r0722, each analog input via r0752, the digital outputs via P0731/P0732, the analog outputs via P0771/P0772, and the relays by forcing the contact state. The board is good if every reading falls within the published tolerance. This procedure is described in the MM440 Parameter List manual.

What parameters must be reset on an MM430 after swapping in an I/O board from an MM440?

Always run a factory reset (P0010 = 30, P0970 = 1) and re-enter the application set. The most commonly mis-mapped parameters are P0701 / P0702 / P0704 (digital input function), P0731 / P0732 / P0733 (output / relay function), P0756[0] / P0756[1] (analog input type), P0771 / P0772 (analog output function), and P2010 / P2011 (USS / Modbus baud and address). After the reset, walk the terminal strip with a multimeter to confirm the wiring record matches the new defaults.

If the I/O board is not available as a spare, must the entire drive be replaced?

In practice yes, unless the I/O board is recoverable from another failed unit. The MLFB 6SE6400-7AA00-0BA0 is listed in the German-language spare-parts document as a serviceable assembly, but regional Industry Mall availability varies. Where the board cannot be ordered, swap the entire inverter, recover the I/O PCB from the retired drive, and use it as a verified bench spare for future failures.

What faults point specifically to the I/O board rather than the power stack?

Look for F0022 (PTC sensor open / short) on a drive where the PTC input is wired, F0051 (parameter fault during EEPROM read), F0080 (analog input lost on P0756 = 1 or 2 with 4–20 mA), or a stuck digital-input bit that does not clear with a factory reset. These point to the control board. Power-stack faults F0001 (overcurrent), F0002 (overvoltage), F0003 (undervoltage), F0004 (inverter overtemperature), and F0011 (motor overtemperature via I²t) are unrelated to the I/O board and must be diagnosed on the power section.

Back to blog