ModelRailPro logo ModelRailPro NLENDE

DCC vs Motorola (MM) vs mfx: drive protocols compared

DCC is the open world standard, Motorola (MM) the classic Märklin standard and mfx its modern bidirectional evolution. This guide puts all three side by side — facts, comparison table and selection advice.

Three protocols on one layout

Digital model railways can involve three drive protocols: DCC, Motorola (MM) and mfx. All three control locos through the track signal, but they differ fundamentally in design. DCC is an open international standard, freely implementable by any manufacturer. Motorola is a closed Märklin protocol dating from the 1980s. mfx is Märklin's modern bidirectional drive protocol, also available via ESU hardware under the name M4. This guide compares all three on facts: addresses, speed steps, functions, feedback and command station compatibility.

DCC — the open NMRA standard

DCC (Digital Command Control) is defined in NMRA standard S-9.2.2 and is the most widely used digital drive standard in model railways worldwide. The protocol is brand-neutral: a DCC decoder from ESU, Zimo or Lenz runs on a DCC command station from Roco, DCC-EX, Lenz or any other manufacturer without modification. That is the fundamental strength of an open standard.

DCC supports three speed step modes: 14, 28 and 128 steps. The mode is set via bit 1 of CV29. In practice, 128 steps is the standard for smooth running behaviour; 14 steps only appears in older configurations.

DCC addresses come in two ranges. The short address (CV1) covers 1 to 127 and is active when CV29 bit 5 = 0. The long address (CV17 + CV18, CV29 bit 5 = 1) covers 1 to 10,239 — per NMRA S-9.2.2. The free DCC tools on this site calculate CV17 and CV18 automatically from a desired address.

Functions run from F0 to F28 as standard (F0 = headlight, direction-dependent); extended to F68 via S-9.2.1. Not all command stations forward F29 and above to the decoder — check your command station documentation.

DCC is strictly unidirectional by itself. Per-block loco identification requires RailCom (NMRA S-9.3.2), where the decoder briefly transmits back over the rails during a pause in the DCC signal. Occupancy detection without RailCom uses external feedback buses: s88, R-BUS or LocoNet. See the RailCom guide for a full explanation.

Motorola MM I and MM II

The Motorola protocol — known in the hobby as "MM" or "Märklin Motorola" — was developed by Märklin in the 1980s as a proprietary drive standard. No public open specification exists. Many classic Märklin locos are fitted with MM decoders and run exclusively on MM signals.

MM I offers 80 addresses (1–80), 14 speed steps and only F0 (headlight). The protocol is strictly unidirectional: no feedback or loco identification from the drive protocol itself.

MM II adds functions F1 to F4. The nominal address range remains 80 addresses. Some manufacturers have built non-standardised extensions that allow higher addresses, up to approximately 255. Those extensions are manufacturer-specific and not interoperable: whether a given decoder responds above address 80 depends on the specific command station and decoder combination and cannot be guaranteed from general documentation. To be confirmed on a layout

MM has no feedback capability in the drive protocol. Occupancy detection on an MM layout uses external current sensing — s88 or equivalent — independent of the drive protocol. Command stations that support MM: Roco Z21 black, DR5000, Märklin CS2/CS3 and ESU ECoS. DCC-EX does not support Motorola.

mfx and M4 — automatic registration

mfx is Märklin's modern drive protocol with bidirectional communication. The key difference from DCC and MM: an mfx decoder registers automatically with the command station as soon as it is placed on the layout. The command station assigns an address and reads the decoder's name, icon and full function list, which appear immediately in the interface. Manually entering addresses or programming CVs is not required for basic operation.

mfx offers 128 speed steps. Addresses are assigned automatically by the command station; there is no manual address limit in normal use. Märklin's marketing cites figures in the range of 65,000 devices per system, but no exact publicly published specification is available — treat that figure as a marketing indication, not a technical limit.

mfx works as a drive protocol only on command stations that support it: Märklin CS2 and CS3 and ESU ECoS (via M4). On any other command station, an mfx decoder runs as a DCC or MM decoder — automatic registration and the function list are not available. The decoder selects the active protocol based on the signal it receives.

RailComPlus (ESU/Lenz) offers comparable automatic loco registration via the open DCC protocol rather than a proprietary one. See the RailCom guide for a direct comparison.

Comparison table: DCC / MM I / MM II / mfx

FeatureDCCMM IMM IImfx / M4
StandardOpen (NMRA S-9.2.2)ProprietaryProprietaryProprietary
Address range1–127 (short) / 1–10,239 (long)1–801–80 (extensions to ±255 To be confirmed on a layout)Automatically assigned, no manual limit
Speed steps14 / 28 / 1281414128
FunctionsF0–F28 (extended to F68)F0F0–F4Decoder-dependent, extensive
FeedbackVia RailCom (optional)NoneNoneBidirectional (built-in)
Supported stationsZ21, DCC-EX, ECoS, CS3, DR5000, Lenz etc.Z21 black, DR5000, ECoS, CS3Z21 black, DR5000, ECoS, CS3CS2, CS3, ECoS (M4)

Multi-protocol: DCC and MM on one layout

DCC decoders respond only to DCC packets; MM decoders respond only to MM packets. Each ignores the other's signals. Command stations that transmit both protocols simultaneously — such as the Roco Z21 black, DR5000, ESU ECoS and Märklin CS3 — can independently control DCC and MM locos on the same track. Classic MM locos can therefore continue running alongside modern DCC locos without any modification to the locos themselves.

mfx-capable command stations (CS3, ECoS) typically transmit DCC, MM and mfx simultaneously. mfx decoders recognise the mfx signal and activate automatic registration; DCC and MM decoders ignore the mfx packets completely.

DCC-EX transmits DCC only. MM or mfx locos without DCC support will not run on DCC-EX. Modern multi-protocol decoders — such as the ESU LokPilot 5 (DCC + MM + M4) — remain compatible regardless of which command station you choose in the future.

Choosing the right protocol

Need to calculate CV values? Use the free DCC tools. Looking for decoder brands and connector types? See the loco decoder guide. Comparing command stations? See the Z21 vs Märklin CS3 comparison.

Related guides

Frequently asked questions

Can I run an old Märklin loco with an MM decoder on a modern command station?
Yes, provided the command station supports Motorola. The Roco Z21 black, DR5000, ESU ECoS and Märklin CS3 all transmit DCC and Motorola simultaneously. DCC-EX is DCC-only — for classic MM locos it is not a suitable choice.
What is the difference between mfx and RailComPlus?
Both provide automatic loco registration with the command station. mfx is Märklin's proprietary protocol and works only on CS2, CS3 and ECoS (via M4). RailComPlus is an ESU/Lenz extension of the open DCC protocol, working on ECoS, Lenz LZV200 and certain other stations.
Does mfx work on a Roco Z21?
No. mfx as a drive protocol works only on Märklin CS2/CS3 and ESU ECoS (via M4). An mfx decoder running on a Z21 operates as a DCC or MM decoder — automatic registration and the function list are not available in that case.
Download ModelRailPro Try free for 30 days

← Back to hardware · DCC-tools