Decoder MX620, MX62, MX63, MX64, MX64D, MX64P Page 1

EDITION
First common instruction manual for MX620 (SW version 3), MX62, MX63, MX64 (SW version 25) --- 2006 08 01
2006 09 20

INSTRUCTION MANUAL
2006 12 01
RailCom (MX63, MX64 from SW-Version 28) --- 2007 02 25
With loco programming examples in chapter 4 --- 2007 05 05
First delivery of MX64D with SW version 4, also new SW version 4 for MX620 --- 2007 08 01

Actual sizes shown

0. What’s new? from MX62 to MX620 or MX63, MX64 from SW version 25 ............................................................ 2
MINIATURE – DECODER – From 2006 . . . and what’s old? in the MX620, MX62, MX63 and MX64 . . . ...................................................................... 4

MX620, MX620N, MX620R, MX620F 1. Overview ........................................................................................................................................................................................ 5

2. Technical Information ..................................................................................................................................................................... 6
3. Addressing and Programming ...................................................................................................................................................... 10
4. Additional notes to Configuration Variables (CV’s)........................................................................................................................ 16
MINIATURE – DECODER – Until 2005 5. “Function mapping“ as per NMRA Standard; and ZIMO - Extensions .......................................................................................... 24

MX62, MX62N, MX62R, MX62F 6. “Bi-directional communication”...................................................................................................................................................... 27

7. Installation and wiring ................................................................................................................................................................... 27
8. The MX64D in a loco with a C-Sinus motor ................................................................................................................................... 32
HO – DECODER 9. ZIMO decoders and competitor systems ........................................................................................................................................... 32
10. Special - CV - Sets ..................................................................................................................................................................... 33
MX63, MX63R, MX63F, MX63T 11. Converting binary to decimal ...................................................................................................................................................... 34
12. MX620 with Märklin MOTOROLA systems ................................................................................................................................. 34
13. Software Update with MXDECUP ............................................................................................................................................... 35
HO – THIN DECODER
MX64, MX64R, MX64F, MX64T
HO – HIGH OUTPUT DECODER NOTE:

MX64H, MX64HR, MX64HF, MX64V ZIMO decoders contain an EPROM which stores software that determines its characteristics and functions. The software version can be read out
form CV #7.
The current version may not yet be capable of all the functions mentioned in this manual. As with other computer programs, it is also not possible
for the manufacturer to thoroughly test this software with all the numerous possible applications.
H0 – DECODER with 21-pin or PluX interface Installing new software versions later can add new functions or correct recognized errors. SW updates can be done by the end user for all ZIMO
decoders since production date October 2004, see chapter 12!
MX64D, MX64DV, MX64P Software updates are available at no charge if performed by the end user (except for the purchase of a programming module); Updates and/or up-
grades performed by ZIMO are not considered a warranty repair and are at the expense of the customer. The warranty covers hardware damage
MX64P won’t be available until locomotives exist with Plux socket! exclusively, provided such damage is not caused by the user or other equipment connected to the decoder. For update service, see www.zimo.at !
 Page 2 Decoder MX620, MX62, MX63, MX64, MX64D, MX64V

“SUSI” interface with socket (MX64H), others with solder pads,

0. What’s new? MX620, MX64D, and MX64P with first SW version; with SW version 25 for MX62, MX63 and MX64
from MX62 to MX620 or MX63, MX64 from SW version 25 The 4 SUSI pads serve primarily for the connection of sound modules but could equally well be employed
for other applications, such as: pantograph or uncoupler modules (See CV #124, Bit 7).
The MX620 family of decoders is superseding the MX62. The MX620 as well as the MX64D, MX64DV and
MX64V are derived from the MX69 in terms of functions and motor control using the same powerful proces-
sor, which is an even newer design than found in the MX62, MX63 and MX64! With a few exceptions, most
Stop on “asymmetrical DCC Signal” (Lenz „ABC“)
MX620, MX64D, MX64P with first SW version; with SW version 25 for MX62, MX63 and MX64; NOT avail-
of the MX620 capabilities will be added to the MX62, MX63 and MX64 from SW version 25 on.
able in MX62
This chapter is placed ahead of the actual instruction manual to outline the essential differences of the
MX620 to its predecessor. It is not meant to be a complete list of features because the MX62 was already This is actually a very old method developed by Umelec that allows direction dependent stop sections to be
well equipped (see chapter “and what’s old”). built at very little cost, with just 4 diodes.
The “asymmetrical DCC signal” offers nowhere near the functionality of ZIMO’s own “signal controlled
A key feature of all ZIMO DCC decoders since September 2004, including the MX62, is the speed influence” (neither does the “ABC” method with slow-down section, sold by Lenz), but is nevertheless
User-activated software-update an alternative for simple applications; Activation with Bit 0 or 1 in CV #27.
There will be a number of new features introduced to the world of DCC in the years to come (implementa- Unreliable operation is a common problem with asymmetrical working DCC command stations (especially
tion and further development of bi-directional communication, extended function mapping and much more). Intellibox) or an asymmetrical load on the track (diodes used in lighted coaches). For this reason, a special
Only if a decoder can be updated does it keep its value over time. variable (CV #134) is added to the MX620 with which the necessary signal asymmetry may be changed.
Updating ZIMO decoders, free of charge by the way, is done with the help of an update module MXDECUP Practical experiences will prove whether this adjustment is actually required.
at the track, without even opening up the engine. See last chapter in this manual.

Some of the following described features will likewise only be available with future software updates. Up-
Km/h or mph speed regulation
MX620, MX64D, MX64P with first SW version; planned for MX62, MX63, MX64 if enough interest
dates are also indispensable for fixing software bugs (that are unavoidable with software of such complex-
ity), to take our customers experiences and requests into consideration and to adapt the product to chang- For some time now a desire has been expressed to control train speeds by actual km/h or mph uniform for
ing industry standards. all locos (i.e. 40 mph) instead of the usual speed step method (1-126), which represents a fraction of the
loco-specific maximum speed. The MX620 offers this speed control as an alternative, activation with CV
Partly automated adjustments of control parameters #135 = 0.
MX620, MX64D, MX64P with first SW version; with SW version 25 for MX62, MX63 and MX64 During a calibration run, the loco travels at medium speed for a given distance (100 scale yards). Passing
the start and endpoint of this distance is registered by switching the headlights (semi-automatic procedure).
Optimizing the driving characteristics is now a lot simpler because the control parameters are being ad-
CV #135 determines the conversion factor between the speed step and the actual speed. For example: if
justed in part automatically. See description of CV’s #9 and #56. The individual adjustment of all values like
each speed step = 1km/h the speed range goes up to 126km/h; if each speed step = .5km/h the top speed
length and frequency of EMF sampling as well as proportional and integral values of the PID regulation is
is 63km/h (useful for secondary lines, trolleys, narrow gauge etc.).
still possible but is in most cases no longer required.
This kind of control is not just for visually pleasing driving characteristics. That is the job of the BEMF load
regulation. This is rather for the exact adherence to the desired speed in mph or km/h and/or the stop-
Special motor control for Faulhaber- and Maxxon motors ping distance. This new requirement is reached by constantly calculating, adjusting and recalculating the
MX620, MX64D, and MX64P with first SW version; with SW version 25 for MX62, MX63 and MX64 traveled distance. The necessary data (EMF values measured up to 200 times per second) and the com-
Programming CV #56 from 100 to 199 optimizes motor control for coreless motors; CV # 56 = 100 activates puting power are available in all current ZIMO decoders.
automatic fine-tuning (as described above for coreless motors). CV # 56 = 101 to 199 allows you to select The km/h or mph speed control offers a number of operational advantages; from the strict adherence to
the parameters manually (see description of CV’s #9 and #56)! speed limits (caution or 35mph …) to the trains’ precise estimated time of arrival in the next station. The ac-
curacy of this control should also bring big improvements in double or multi-traction (consisting) – although
Smart stop management this has to be confirmed by field tests.
MX620, MX64D, MX64P with first SW version; with SW version 25 for MX62, MX63 and MX64 Activating the km/h or mph speed regulation also has one disadvantage though: the graduations at very
low speeds are less sensitive since the speed steps from 0 to full speed are equidistant and not as denser
Operational only if power is provided by an external energy source (MXSPEIG or condenser with at least
in the low speed range, as is usually the case.
1000uF)!
If the decoder looses power while the engine is coming to a stop (dirty track, non-powered frogs etc), it en-
sures that the engine continues until power to the decoder is restored. Once power is restored, the engine
Distance-controlled stopping (constant stopping distance)
is allowed to stop. With the engine at a standstill, the decoder again checks for track power and if neces- MX620, MX64D, MX64P with first SW version; with SW version 25 for MX62, MX63 and MX64
sary moves the engine a bit further. Especially with simple automated stops (e.g. without any brake sections) like the “asymmetrical DCC signal”
(Lenz ABC) or the brake generator method, a train should come to a stop in front of a red signal after a
specific stopping distance (defined in CV #141), regardless of what the trains speed was before it entered
the stop section. This is especially important on above simple procedures that don’t use break sections
 Decoder MX620, MX62, MX63, MX64, MX64D, MX64P Page 3

ahead of stop sections but this method may also be useful in conjunction with ZIMO’s signal controlled “Location dependent function control”
speed influence or when stopping a train manually. added later with new SW versions
While normal deceleration (as well as acceleration) procedures are controlled by time (equal time intervals
Until now, this feature was only available with ZIMO function decoders; in the future it will also be available
between speed steps), the deceleration time in conjunction with a predetermined stop point has to be recal-
loco decoders.
culated for the remaining stopping distance.
With the help of the signal controlled speed influence (that is through a track section module without further
The ZIMO implementation of “constant stopping distance” does not just include a simple adjustment of the expenditure), this feature will automatically operate functions such as lights, horn/whistle, bell etc.
deceleration rate based on the speed when entering a stop section. The “distance-controlled stopping” fea-
The method described in the next section will be implemented at the same time.
ture as implemented by ZIMO differentiates itself from other manufacturers “constant stopping distance” by
the repeated recalculations of the already traveled and the remaining stopping distance with the required
adaptation in deceleration rate. Position-Codes – Evaluation
added later with new SW versions
“RailCom” = “bidirectional communication” as per NMRA 9.3.1 and 9.3.2 The MX9 track section module can send out position codes, also with the help of the “signal controlled
MX620 from SW version 4 | MX64D, MX64P with first SW version speed influence”, in order to inform the loco decoder of its actual position. With it, new methods of auto-
MX62, MX63, MX64 from SW version 28 | RailCom will be further developed over the years matic train protection (collision avoidance) and layout automations can be developed particularly when used
together with bidirectional communication as ZIMO intended under the designation “ARS” (also see com-
All current ZIMO decoders (MX62, MX620, MX63, MX64, MX69, MX690 and MX82) are already equipped
mand station and cab manuals).
with the necessary hardware for the NMRA bi-directional communication according to RP 9.3.1 and 9.3.2.
The actual data to be transmitted and its protocol will largely be decided within the scope of the NMRA-
DCC-standardization and in part within the “RailCom working group” (Lenz, Kühn, Tams and ZIMO). This Inputs to activate functions and operating sequences or the like
process started in 2006 and will continue in the years to come. Zimo will make the required software up- added later with new SW versions
dates available accordingly.
One of the SUSI pads can also be used as an input to actuate functions, such as an acoustic signal or to
- Loco-feedback of actual speed and motor load to a global RailCom detector (internal or external of the automatically trigger simple applications like shuttle train operations, automated station stops and emer-
command station), gency stops.
- On-the-main read-out of CV values by the global RailCom detector,
- Loco address transmitted in broadcast mode to local RailCom detectors (in order to identify the loco ad-
Note: Such simple operating procedures are primarily provided for the use with non-ZIMO systems.
dress in an isolated section of track). The ZIMO-DCC system provides “automated route sequences” (ARS), a much more powerful in-
strument for shuttle train operations and similar, stored and played back by the command station.
Note: ZIMO will first introduce a global detector for the command stations MX1, MX1HS, MX1EC (also for
retrofitting) and the MX31ZL (installed at the factory) in 2007, for applications like speed and load display on
the cab and CV-handling on-the-main, and later local detectors for track section modules. The LRC120 ad- LED output for Infrared-Routing
dress display (local RailCom detector from Lenz Elektronik) can be used with the MX1EC command station added later with new SW versions
beginning with the 2. quarter of 2007; a little later with the MX1 and MX1HS as well. With the help of an infrared-LED installed in the loco floor, the decoder can send information that can be re-
RailCom is a registered trade mark of Lenz Elektronik GmbH. ceived by a receiver-diode (sensor) installed in the track; the receiver diode is connected to an accessory
decoder MX82. The kind of information that can be transmitted may be a fixed routing code (stored in a de-
Completion of the “signal controlled speed influence” coder CV) or a variable dependent on the functions output state. Based on the information received, the
Planned for MX620, MX64D and MX64P; from SW version 25 on for MX62, MX63 and MX64 MX82 accessory decoder operates turnouts or other accessories.
The “signal controlled speed influence” (stop in front of a red signal and 5 speed limits) was implemented With the help of Infrared-Routing, a loco can select specific routes by itself (e.g. selection of a specific sid-
for ZIMO DCC systems in 1998; however, two intended characteristics were still missing. These have been ing); or the next turnout may be switched to the desired position using a loco function key on the cab, which
(will be) added: is a typical operating feature of streetcars.
- Directional control: this can alternatively be used to limit the speed influence for the direction the
signals are pointing (unlimited speed in opposite direction) or to prevent a train from starting up in CV-Sets – supplied or self-defined
the wrong direction after the signal turns green. partly available with initial SW version, will be expanded with future SW updates
- Emergency Stop: automated stops disregarding the momentum programmed to the appropriate A CV-set is stored in a decoder as a complete list of CV’s with their respective values. CV- sets may be
CV’s. supplied with the decoder software (e.g. CV-set for electric loco with Norwegian lighting rules) but can also
be defined by the user (e.g. Special acceleration and deceleration behavior for steam engines).
Automatic coupler detachment
A so-called pseudo programming of CV #8 is employed to replace currently operational CV’s with a stored
MX620 from SW version 4 | MX64D, MX64P with first version | MX62, MX63, MX64 from SW version 25
CV-set (regardless whether supplied or self defined). For example: CV #8 = 47 for Norwegian lighting rules;
In conjunction with the electric uncoupling (system Krois), it is possible to define the locomotive decoder so CV #8 contains the number 145, which is the ZIMO identification code and can not really be overwritten,
that it automatically pulls forward a specified distance away from the train while the coupler is disengaged, hence the name pseudo programming. Entering number 47 causes the decoder to load the stored CV-set
see CV #115. containing the above lighting rules for example.
 Page 4 Decoder MX620, MX62, MX63, MX64, MX64D, MX64V

Typical applications for CV-sets are: country specific lighting rules, motor specific data for best slow speed The MX64D can be switched to a special output configuration that is required for the interaction with the C-
behavior, engine specific acceleration, easy adaptation of an engine used in different trains (passenger, Sinus boards built into these locomotives. The decoder further supplies the 5V power the C-Sinus board
goods, consists) or between home layout and club operations. needs, which ordinary decoders cannot! See CV #112.

Virtual cam sensor for sound modules Control of C-Sinus motors (Märklin, Trix with 21-pin interface)
MX620, MX64D and MX64P with first SW version, MX62, MX63 and MX64 from SW-Version 25 MX64D with first SW version | not intended for other decoder types
Function output 2 (FO2) of the MX620, if desired, serves as the cam sensor input (via SUSI for example) to The MX64D can be switched to a special output configuration that is required for the interaction with
a sound module (e.g. Dietz reed-switch input) and thereby saves the installation of a real cam sensor. This the C-Sinus boards built into these locomotives. The decoder further supplies the 5V power the C-
simulation is of course not in a position to synchronize the steam chuffs to the exact piston position but Sinus board needs, which ordinary decoders cannot! See CV #112.
nevertheless offers a much improved wheel speed synchronization than is possible with the conventional
method of speed step synchronization (see chapter 7 as well as CV #133 in the CV table).
NMRA conformance test
is intended
New function mapping procedure with CV #61 = 98
MX620, MX64D and MX64P with first SW version, MX62, MX63, MX64 with future SW versions It is planned to have the current ZIMO decoders officially tested for conformance by the NMRA (National
Model Railroad Association), in order to get authorization for using the “conformance seal”. Such a seal at-
This procedure offers more flexibility in allocating function outputs (headlights and outputs F1 to F12) to tests that the relevant NMRA standards and recommended practices are adhered to, which ensures com-
function keys (F0 to F12), than is possible with fixed configuration values. patibility between DCC products of different manufacturers.
The execution of this assignment procedure however requires some extra time and a certain degree of at-
tention from the user. ZIMO users will get support from the cab in the near future!
It can be defined which function outputs should activate with each function-direction combination (as in F0
forward, F0 reverse, F1 forward, F1 reverse etc.); multiple selections are possible. It is further possible to
add the option of automated and timed turn-off (e.g. headlights), after the loco stopped and the pro-
grammed time has elapsed.
The function allocations can be combined with special effects such as US lighting, uncouplers etc. as well
as CV-sets.

Incremental CV programming
added later with SW updates
This will simplify the fine tuning of CV values (i.e. slow speed or acceleration and deceleration values): no
. . . and what’s old?
need to manually enter different decimal values, which is the case with conventional CV programming, but in the MX620, MX62, MX63 and MX64 . . .
rather increase or decrease the current value by simply pressing a function key.
The MX62, the predecessor to the MX620, as well as the MX63 and MX64 with earlier software versions
Diagnostic and statistics index were already equipped with many outstanding characteristics - all of them are of course still present:
added later with SW updates High frequency motor control (up to 40kHz), adjustable load regulation, fully compatible with core less mo-
tors, exponential acceleration, US lighting effects, uncoupler control (System Krois, System Roco), NMRA-
Operating hours, odometer readings, error reports (short circuits etc.) are continuously updated in “live” DCC function mapping, extended ZIMO function mapping, dimming, low beam, flasher, uninterrupted op-
CV’s and can be recalled and displayed at any time. eration during short power interruptions, over-voltage and thermal protection, Zimo signal controlled speed
influence, loco number recognition.... and much more.
Alternative data formats supported (Motorola, Selectrix, mfx)
MX620, MX64D and MX64P with first SW version, MX62, MX63, MX64 with future SW versions
Although DCC is far superior to Motorola or Selectrix, these two data formats are nevertheless very much in
use today. It is therefore being considered to develop the required software and make it available with a fu-
ture software update.
In addition to the normal MOTOROLA implementation, it will also be possible in this format to switch 8 (in-
stead of 4) functions by linking the next higher address to the first (see CV #112, Bit 3)!
It cannot be guaranteed from today’s perspective, whether the mfx format (now used by Märklin) can
actually be implemented.Control of C-Sinus motors (Märklin, Trix with 21-pin interface)
MX64D with first SW version | not intended for other decoder types
 Decoder MX620, MX62, MX63, MX64, MX64D, MX64P Page 5

1. Overview Compact design, double layer circuit board with back-EMF, high-frequency motor
control for DC and coreless motors and all other ZIMO features. Identical in function-
MX63 ality to the MX64 decoder!
The decoders described here are for the installation in N, HOe, HOm, TT, HO, OO, Om and O gauge en-
gines. They are equally suited for locos with standard as well as core less motors (Faulhaber, Maxxon, Es-
Family The MX63 decoder is wrapped with a shrink tube and well protected against possible
short circuits.
cap and others), for the latter the special settings in CV #56 = 100 and CV #9 = 12 are available (new in
MX620 and with SW version 25 in MX62, MX63 and MX64).

ZIMO decoders operate primarily according to the standardized NMRA-DCC data format and can there- Different versions according to their connections:
fore be used within a ZIMO digital system as well as DCC systems of other manufacturers, the MX620,
MX64D and MX64P can also operate with the MOTOROLA protocol within Märklin systems and other Version with 9 highly flexible wires (120 mm long) for power, motor, 4 function out-
MX63 puts. Solder pads are available for further outputs (logic level) and SUSI.
MOTOROLA command stations.

MX63R MX63 with 8-pin interface per NEM652 and NMRA RP 9.1.1 on 70mm wires.
Miniature-Decoder with BEMF and high frequency drive suitable for DC and core-
less motors and all other ZIMO features found in larger decoders.
MX63F MX63 with 6-pin interface per NEM651 and NMRA RP 9.1.1 on 70mm wires.
ATTENTION: Extra care is required during installation because the MX620, unlike
MX620 the MX63, is not protected by a shrink tube! MX63 with 21-pin interface for locomotives from Märklin, Trix, Brawa, Liliput and oth-
Family TYPICAL APPLICATION: for the installation in N, HOe, HOm but also HO engines MX63T ers.
with limited available space or because of features that have not yet been imple-
mented in the MX63/MX64 decoder (i.e. mph speed control).

Different versions according to their connections: Ultra thin decoder on single layer circuit board with back-EMF, adjustable frequency
from 50Hz to 40kHz (silent drive), DC and coreless motors and all other ZIMO fea-
Version with 7 highly flexible wires (120 mm long) for track, motor and 2 functions. MX64 tures. Identical in functionality to the MX63 decoder! The bottom of the circuit board
MX620 Solder pads are available for two additional functions and SUSI. is protected with a foil.
Family
TYPICAL APPLICATION: Locomotives in HO, OO….O.
MX620 with 6-pin interface per NEM651 and NMRA RP 9.1.1. Interface is mounted
MX620N on circuit board, no wires. Different versions according to their connections:

Version with 9 highly flexible wires (120 mm long) for power, motor, 4 function out-
MX620R MX620 with 8-pin interface per NEM652 and NMRA RP 9.1.1 on 70mm wires. MX64 puts. Solder pads are available for 4 more outputs (logic level) and SUSI.

MX620 with 6-pin interface per NEM651 and NMRA RP 9.1.1 on 70mm wires. MX64R MX64 with 8-pin interface per NEM652 and NMRA RP 9.1.1 on 70mm wires.
MX620F

MX64F MX64 with 6-pin interface per NEM651 and NMRA RP 9.1.1 on 70mm wires.

Miniature-Decoder of the previous generation (produced from 2002 to 2005). MX64 with 21-pin interface for locomotives from Märklin, Trix, Brawa, Liliput and oth-
MX64T ers.
MX62 Even though this decoder is no longer being produced, it is still covered in this man-
Family ual because future software updates will still be available.

High-output version of the MX64, double sided with SUSI socket. MX64H - is
Compact loco decoder, on double layer circuit board, with back-EMF, adjustable identical in function to MX64 but with more power and 8 amplified function outputs
frequency from 50Hz to 40kHz (silent drive), DC and coreless motors and all other MX64H,
(as compared to MX64 with 4 amplified and 4 logic outputs).
MX63 ZIMO features. Identical in functionality to the MX64 decoder! MX64V MX64V1 - comes with additional low voltage supply of 1.5V for functions.
The decoder is well protected in a transparent shrink tube against unwanted contact Families MX64V5 - is the same but with 5.0V supply.
Family with other metal parts.
TYPICAL APPLICATION: Locomotives in HO, OO….

Decoder with 21-pin plug (MX64D, MX64DV) or PluX plug (16-pin MX64P), both
MX64D, according to NMRA DCC RP 9.1.1.
 Page 6 Decoder MX620, MX62, MX63, MX64, MX64D, MX64V

MX64DV,
MX64D and MX64P are identical in functionality to the MX620 but are also suitable
2. Technical Information
MX64P16 for locomotives with C-Sinus motor and 21-pin socket (Märklin, Trix).
Allowable Track voltage ............................................................................................................... 12 - 22 V
MX64DV – is a MX64D with additional low voltage output of 1.5V (MX64, MX64H, MX64V, MX64D and MX64P can also be operated with 24 V.)
Maximum continuous motor output ....................................... MX620, MX62 ................................ 0.8 A
MX63, MX64 ...................................... 1 A
MX64H, MX64V .............................. 1.6 A
MX64D, MX64DV, MX64P ............... 1.2 A
Peak motor current ................................................................................................................................ 2 A
Maximum total function output, continuous *)……..……….. .. MX620, MX62 ................................. 0.3 A
MX63, MX64, MX64H, MX64V ......... 0.5 A
MX64D, MX64DV, MX64P ................... 1 A
Maximum continuous total current (motor and functions)…………. ...... MX620, MX62 .................... 0.8 A
MX63, MX64 ...................... 1.2 A
MX64H, MX64V ................. 1.8 A
MX64D, MX64P……….1.2A
Operating temperature ........................................................................................................ - 20 to 100 oC
Dimensions (L x W x H) … ............ MX620, MX620N excluding pins .............................. 14 x 9 x 2.5 mm
MX62, MX62N excluding pins ................................. 14 x 9 x 3 mm
MX63 ........................................................................ 20 x 12 x 4 mm
MX64 ........................................................................ 26 x 16 x 3 mm
MX64H, MX64V ........................................................ 26 x 16 x 5 mm
MX64D .............................................................. 20.5 x 15.5 x 4.5 mm
MX64DV ............................................................ 25.5 x 15.5 x 4.5 mm
MX64P ............................................................... 20.5 x 15.5 x 4.5 mm
*) The short circuit protection is carried out for the total current of all outputs. In the unlikely event that the
outputs are turned off due to cold-start problems of light bulbs (power surge at turn-on leading to a short),
the “soft-start” option can be utilized (see CV #125 = 52 etc.)!

DO–IT–YOURSELF SOFTWARE UPDATE !

Beginning with production date September 2004 (MX620 since introduction), ZIMO DCC decoders are
equipped to handle a software update by the user. A ZIMO decoder update module (e.g. MXDECUP or
MXDECUPU), a PC with Windows operating system, a serial port (or USB and converter) and the program
ZIMO Service Tool „ZST“ is required. An Internet connection is needed to download the latest software
version from ZIMO’s web site www.zimo.at. The update module is used independent of the command sta-
tion and can therefore be used with any DCC system!
There is no need to remove the decoder or to open up the locomotive. Just set the locomotive on a
section of track connected to the update module and start the update with the computer.
NOTE: Equipment inside the locomotive that is connected directly with the track (that is, not powered by the
decoder) can interfere with the update procedure. Also energy buffers installed without heeding the advice
in chapter 7 (no choke coil) may prevent a successful update.
See the last chapter in this manual for more information on updating decoders or www.zimo.at !
SW updates are of course still available for a small fee by sending decoders to ZIMO or your ZIMO dealer.
 Decoder MX620, MX62, MX63, MX64, MX64D, MX64P Page 7

OVERLOAD PROTECTION:
The motor and function outputs of the ZIMO large-scale decoders are designed with lots of reserve capaci-
ties and are additionally protected against excessive current draw and short circuits. The affected output is
turned off once an overload situation exists and subsequent load tests are performed by the decoder, which
is often recognized as flashing headlights

Even though the decoder is well protected, do not assume it is indestructible. Please pay attention to the following:
Faulty decoder hook-up, connecting the motor leads to track power for instance or an overlooked connection between the
motor brushes and rail pick-ups is not always recognized by the overload protection circuit and could lead to damage of the
motor end stage or even a total destruction of the decoder.
Unfit or defective motors (e.g. shorted windings or commentators) are not always recognized by their high current con-
sumption, because these are often just short current spikes. Nevertheless, they can lead to decoder damage including dam-
age to end stages due to long-term exposure.
The end stages of loco decoders (motor as well as function outputs) are not only at risk of high current but also voltage
spikes, which are generated by motors and other inductive consumers. Depending on track voltage, such spikes can
reach several hundred volts and are absorbed by special protection circuits inside the decoder. Since the capacity and
speed of such circuits is limited, the track voltage should not be selected unnecessarily high; that is not higher than recom-
mended for the rolling stock in question. The full adjustable range of a Zimo command station (up to 24V) should only be
utilized in special cases. Although ZIMO decoders are suitable for 24V operation, that may not be the case when interacting
with some other equipment.

THERMAL PROTECTION:
All ZIMO decoders have the ability to measure their own operating temperature. Power to the motor will be
turned off once that temperature exceeds 1000C. The headlights start flashing rapidly, at about 5 Hz, to
make this state visible to the operator. Motor control will resume automatically after a drop in temperature of
about 200C, typically in 30 to 60 seconds.
Page 8 Decoder MX620, MX62, MX63, MX64, MX64D, MX64V
Decoder MX620, MX62, MX63, MX64, MX64D, MX64P Page 9
 Page 10 Decoder MX620, MX62, MX63, MX64, MX64D, MX64V

THE CONFIGURATION VARAIBLES:

3. Addressing and Programming Configuration Variables can be defined within the programming procedures to improve the driving charac-
teristics of a locomotive and for many other application specific adjustments.
Every loco decoder requires a separate unique address with which the loco is controlled using a cab. All
NMRA-DCC compliant decoders have 3 as their factory default address (NMRA standardized decoder The meaning of Configuration Variables (CV’s) is in part standardized by the NMRA DCC RECOM-
address at delivery). MENDED PRACTICES, RP-9.2.2. There are however certain CV’s that are for Zimo decoders only, in
some cases exclusively for specific types of Zimo decoders.
Always use the specifications for the decoder in question, since the value range may differ between manu-
DECODER INSTALLATION: facturers, even with standardized CV’s; in this case use the table below.
After installing the new decoder in a locomotive (see chapter “Installation and wiring”), it can be tested with
address #3. As a minimum, either the motor or headlights need to be connected (better yet both), to enable
decoder acknowledgment during programming. Doing a complete installation before programming the de- CV Designation Range Default Description
coder is often more practical.
Primary “short” The “short” (1-byte) loco addresses; Is active when Bit 5
#1 1 – 127 3
address in CV #29 is 0.
THE ADDRESSING AND PROGRAMMING PROCEDURE:
Entered value = internal speed step assigned to lowest
The procedure for programming and reading of addresses and configuration variables is covered in detail cab speed step.
#2 Vstart 1 – 252 (See 2
in the instruction manual for the cab (MX21, MX31....). For other systems consult the appropriate man- add. notes) Bit 4 in CV # 29 has to be 0; otherwise individual speed
ual. table is active.

Programming a decoder with a PC and ADaPT software (by E.Sperrer, software developer) is a lot #3 Acceleration rate 0 - 255 1
Multiplied by 0.9 equals’ acceleration time in seconds
easier and more convenient! from stop to full speed.

Multiplied by 0.9 equals’ deceleration time in seconds

#4 Deceleration rate 0 - 255 1
from full speed to complete stop.
Technical note to decoder acknowledgments during programming:
When programming a decoder with a cab or computer, every successful programming step will be made visible by the de- Entered value = internal speed step assigned to highest
coder. The same acknowledgment method is used when reading the configuration variables. cab speed step, according to the number of speed steps
0 – 252 selected (14, 28 or 128).
The acknowledgment is based on short power pulses that the decoder generates by briefly turning the motor and headlights #5 Vhigh (See 1 (= 252)
0 and 1 = no effect.
chapter 4)
on, which the command station recognizes at the programming track. It follows that the acknowledgment and read out of a
Bit 4 in CV #29 has to be 0, otherwise speed table is ac-
decoder is only successful if the current consumption is high enough, which means that the motor and headlights have to be
tive.
connected or at least one of the two.
1, Entered value = internal speed step assigned to the
The decoder won’t use the headlights for acknowledgment if CV #60 is set to a value of 40 or less. This is to prevent dam-
¼ to ½ cabs center speed step (=step 7,14 or 63 according to
age to bulbs since this setting is often used in conjunction with low voltage bulbs. The motor is then the only load used for
of the value the number of speed steps selected: 14, 28 or128)
acknowledgments!
1
in “1" = default (is the same as entering a value of 85,
MX64D, MX64DV, MX64P – An alternative internal acknowledgement can be activated: #6 Vmid ( = about 1/3
CV #5 which is 1/3 of full speed with speed regulator in center -
of top speed)
These decoders have the capability to acknowledge programming steps without the normally required power consumption bent speed curve).
but instead by generating “internal high frequency short circuits”; See CV #112, Bit 1.
(See Bit 4 in CV #29 has to be 0, otherwise speed table is ac-
chapter 4) tive.

The following pages show the tables for configuration variables (CV’s). This CV normally displays the decoder software version.
For user of Lokmaus 2 :
Following the CV tables
Software version Pseudo-programming (because programmed value is
are SUPPLEMENTAL NOTES to the application of configuration variables (CV’s) not really stored) as an initial step for programming or
Read only
Having difficulties understanding Bits and Bytes when calculating single-bit CV values??? read-out of a higher CV (>99) and/or a higher value
and all additional
programming in (>99):
See NMRA function mapping calculator at www.zimo.at, follow the links “PRODUCTS” case of
Temporary register when CV # 7 = „01“, „02“, „10“, „11“, „12“ :
and “Decoder” or go to chapter 10 of this manual. #7
programming with a “Lok-
Lokmaus 2
is pseudo only Tens digit = 1: The entered CV value will be increased
maus 2” and similar low level
Within ZIMO systems: systems. by 100 during the actual programming.
See section “Operation within Tens digit = 2: ….increases by 200.
The MX21 cab (or newer) displays Bits in a graph and decimal format. The Bits can be other systems” in this man-
selected as “on” or “off” while the cab does the decimal conversion in the background! ual! Ones digit = 1: The entered CV value will be increased
by 100 during the actual programming.
Ones digit = 2: …increases by 200.
 Decoder MX620, MX62, MX63, MX64, MX64D, MX64P Page 11

CV Designation Range Default Description CV Designation Range Default Description

See section An additional address that is used to operate several

„Application with ROCO Lokmaus-2“! locos in a consist. If a consist address is assigned to
this CV, commands for the primary and extended ad-
NMRA assigned manufacturer ID for Zimo is: 145 #19 Consist address 0 - 127 0 dresses (CV’s #1 and #17/18) will be ignored by the de-
Manufacturer ID Read only (”10010001”) coder. This CV is seldom used within ZIMO systems,
and since it is more comfortable to build and control consists
Pseudo-Programming (”Pseudo” = programmed value is
with the cab (using the “normal” single addresses).
not really stored):
HARD RESET all additional
with CV # 8 = „8“)
programming is 145 ( = CV #8 = “8” -> HARD RESET (all CV’s reset to default Selected functions that should operate with the consist
#8 pseudo only; ZIMO) values). address.
read-out always
or shows “145”, CV #8 = “9” -> HARD RESET for LGB-operation (14 (Bit 0 for F1, Bit 1 for F2, Bit 2 for F3 etc.)
which is ZIMO’s
speed steps, pulse chain). Consist functions for Applicable Bits set to 0 = function controlled by
assigned num-
LOADING ber
#21 F1 - F8 0 - 255 0 single primary address.
of special CV sets CV #8 = “...” -> Loading of supplied or user-defined CV
sets (also see “Special-CV-Sets”). Applicable Bits set to 1 = function controlled by
consist address.
=0: Default motor control with high frequency (20 / 40 See page 31 for Bit value calculation!
0 kHz) and an EMF-sampling rate that automatically ad-
High 0 justs between 200Hz (low speed) and 50Hz. Select whether the headlights are controlled with consist
frequency, High Tens digit 1 - 4: Reduced sampling rate compared to address or single address (Bit 0 for front headlight, Bit 1
Motor frequency
mid-range frequency, default (less noise!) for rear headlight)
sampling mid-range
Tens digit 6 - 9: Increased sampling rate compared to Respective Bit = 0: function output controlled with single
and rate sampling Consist address 0-3 0
default (to improve low speed performance!) #22 address
rate active for headlights
Ones digit 1 – 4: EMF sampling time shorter than de- Respective Bit = 1: function output controlled with con-
EMF 1- 99 fault setting (good for coreless motors for less noise, sist address
sampling rate High Recom- more power) See page 31 for Bit value calculation!
#9 frequency, mendation
Ones digit 5 - 9: EMF sampling time longer than default
modified for core- To temporarily adapt the acceleration rate to a new load
ATTENTION: (may be needed for 3-pole motors or similar)
sampling less mo- or when used in a consist.
Description for rate tors, i.e. = 100: “Spread spectrum” – sampling rate for Acceleration Bit 0 - 6: entered value increases or decreases
MX62, MX63, MX64 MAXXON, reduced noise with medium sampling time. trimming
#23 acceleration time in CV #3.
is only valid for SW FAUL- = 255 - 176: Low frequency - PWM according to formula NOTE: This CV is seldom re- 0 - 255 0
255-176 HABER: quired.
Bit 7 = 0: value added.
version 22 or higher (131+ mantissa*4) *2exp. Bit 0-4 is “mantissa”; Bit 5-7 is = 1: value subtracted.
(earlier SW uses dif- Low CV #9 = “exp”. Motor frequency is the reciprocal of the PWM.
ferent definition) frequency 12 See page 31 for Bit value calculation!
Examples of low frequencies:
(See add. # 9 = 255: frequency of 30 Hz,
Notes, chapter To temporarily adapt deceleration rate to load or when
# 9 = 208: frequency of 80 Hz,
4)
Deceleration used in consist.
# 9 = 192: frequency of 120 Hz.
trimming Bit 0 - 6: entered value increases or decreases
EMF Feedback Assigns an internal speed step above which back EMF #24 0 - 255 0 deceleration time in CV #4.
NOTE: This CV is seldom re-
cut-off 0 – 252 intensity is reduced to the level defined in CV #113. CV quired. Bit 7 = 0: value added.
#10 NOTE: This CV is seldom re- (See add. 0 #10, #58 and #113 together define a back-EMF curve. = 1: value subtracted.
quired. notes) If either CV #10 or #113 is set to 0 a default curve is
valid. See page 31 for Bit value calculation!

Direction This CV activates the direction dependent stopping fea-

Selects function outputs, F1 to F8 that should be “on” in dependent stops ture with asymmetrical DCC signal (also known as Lenz
analog mode. Each bit equals one function; Bit 0 = F1, “ABC”).
Bit 1 = F2, Bit 6 = F7, Bit 7 = headlights. By default, only with asymmetrical
headlights and F7 (Bit 6) are on. DCC signal Bit 0 = 1: Stops are initiated if voltage in right rail is
#13 Analog functions 0 - 255 192 (Lenz “ABC” method higher than left rail (in direction of travel).
A side function of Bit 6: If Bit 6 = 1, the momentum de- THIS, CV #27 = 1, IS THE COMMON
fined in CV #3 and 4 is cancelled when operating in DC #27
0, 1, 2, 3 0 APPLICTION for this feature (provided the
mode. decoder is wired to the correct rail).
MX62: This feature is
See page 31 for Bit value calculation! not available and it will Bit 1 = 1: Stops are initiated if voltage in left rail is
not be possible to higher than right rail (in direction of travel).
#17 The long 5-digit primary address (>127). This address is add with future SW
128 - Stopping is directional if only one of the two bits is set.
+ Extended address 0 only active when Bit 5 in CV #29=1. Otherwise address versions.
10239 Traveling in the opposite direction will have no effect.
#18 entered in CV #1 is active (<127).
Use the other bit In case the train stops in the wrong di-
 Page 12 Decoder MX620, MX62, MX63, MX64, MX64D, MX64V

CV Designation Range Default Description CV Designation Range Default Description

MX63, MX64: rection! #37 2 switches with direction and can

Feature will be added Bit 0 and 1 = 1 (value = 3): Stops in both directions. #38 4 be turned on/off with F0 key
with SW-Version 25. #39 8 (Key #1 or L on Zimo cab).
NOTE: See CV #134 for setting the asymmetrical #40 16
MX620: threshold if problems are encountered (e.g. train won’t Special case MX620: Since the decoder only has 6
available with initial #41 4 function outputs, the registers from #37 up are moved to
stop with asymmetrical signal or stops without asym- #42 8
version. metrical signal present. the empty Bits on the right, which allows these outputs
#43 16 to be moved to higher function keys.
See page 31 for Bit value calculation! #44 32
#45 64 Also see NMRA function mapping and MX620 mapping
#46 128 table at the end of this chapter.
RailCom Configuration Use of RailCom channels (only active if RaiCom is
MX62, MX63, MX64: turned on with CV #29, Bit 3):
Entered value multiplied by .4 equals acceleration time
from SW-Version 28, Bit 0 = 1: Channel 1 for loco address broadcast in seconds from stop to full speed when:
#28 MX620 from SW- 0-7 3 Bit 1 = 1: Channel 2 for RailCom Data Signal controlled
acceleration “ZIMO signal controlled speed influence” (requires
Version 4. Bit 2 = 1: Channel 1 for acknowledgment of re- #49 0 - 255 0 ZIMO MX9 track section module or (TSE) track section
MX64D, MX64P with ceived packets ZIMO „HLU“ - encoder)
initial version Method
or “asymmetrical DCC signal” method (Lenz ABC) is
employed.
Bit 0 - Train direction:
Basic 0 = normal, 1 = reversed Entered value multiplied by .4 equals acceleration time
configuration Bit 1 - Number of speed steps: in seconds from full speed to complete stop when:
0 = 14, 1 = 28 Signal controlled
deceleration “ZIMO signal controlled speed influence” (requires
CV #29 is calculated by Note: 128 speed steps are always active if corresponding informa- #50 0 - 255 0 ZIMO MX9 track section module or (TSE) track section
adding the value of the in- tion is received! ZIMO „HLU“ - encoder)
dividual bits that are to be Bit 2 - DC operation (analog): *) Method
“on”: or “asymmetrical DCC signal” method (Lenz ABC) is
0 = off 1 = on employed.
Values to turn Bit “on”:
Bit 3 - RailCom („bidirectional communication“)
Bit 0: 1
Bit 1: 2 0 = deactivated Each of the 5 speed limits (CV’s #51 – 55) that can be
Bit 2: 4 1 = activated see CV #28! Signal dependent applied with the ZIMO “signal controlled speed influ-
#51 speed limits 20
Bit 3: 8
Bit 4 - Individual speed table: #52 40 (U) ence” can be defined with an internal speed step.
Bit 4: 16
Bit 5: 32 0 = off, CV # 2, 5, 6, are active. #53 #52 for “U”, 0 - 252 70 These CV’s are also intended for use with the “asym-
Bit 6: 64 1 = on, according to CV ‘s # 67 – 94 #54 #54 for “L”, 110 (L) metrical DCC signal stop” in case it’ll be further devel-
Bit 7: 128
#55 #51, 53, 55 180 oped for more speed limits.
Bit 5 - Decoder address: for intermediate steps
0 = primary address as per CV #1 ZIMO „HLU“: also see CV’s #137, 138, 139 !
#29 0 - 63 6 1 = ext. address as per CV #17+18
ZIMO MX21, MX31… cabs Back-EMF compensation is calculated by PID algorithm
also display the individual Bits 6 and 7 are to remain 0! 0
bits; ( = to 55, (Proportional/Integral - Differential); modifying these
Example: Back-EMF control values may improve the compensation characteristics in
calculating bit values is no mid-range)
longer necessary! #29 = 2: normal direction, 28 speed steps, DCC P and I value Recom- certain cases.
operation only, speed table according to CV mended 0 - 99: for „normal“ DC motors
#2, 5 and 6, primary address as in CV #1. for core- 100 - 199: for coreless (MAXXON, Faulhaber, etc...)
#29 = 6: as above, plus DC mode added. less mo-
Tens digit: Proportional (P) value; by default (0) is
ATTENTION: Descrip- 0 - 199 tors, i.e.
#29 = 22: DC mode and individual speed table set to mid value and automatic adjustment
#56 tion for (See add. MAXXON,
according to CVs #67 – 94 added. with the goal of jerk free running. Proportional
MX62, MX63, MX64 notes) FAUL-
#29 = 0: 14 (instead of 28) speed steps, necessary effect can be modified with settings of 1 – 4
is only valid for SW HABER:
for some older third party systems. and 6 – 10 (instead of the default 0 = 5).
version 22 or higher CV #56 =
*) For polarity dependent DC braking, set CV #29, Bit 2 (earlier SW uses dif- 100 Ones digit: Integral (I) value; is set by default to a
= “0” and CV 124, Bit 5 = “1”! ferent definition) (possibly mid value.
as starting The Integral effect can be modified with
*) For polarity independent DC braking (Märklin brake- point for settings of 1 – 9 instead of the default 0 = 5).
modules) set CV #29, Bit 2 = “0” and CV 124, Bit 5 = fine-tuning)
“1” and additionally CV #112, Bit 6 = 1!

#33 1 Function mapping according to NMRA: A value entered divided by ten is the peak voltage ap-
Function mapping 0 – 255 plied to the motor at full speed.
#34 (See add. 2
notes) #57 Voltage reference (See add. 0
#35 4 #33 - 46 = 1, 2, 4... Outputs are set to notes) #57 = 0: results in automatic adjustment to current track
#36 8 F0 - F12 by default. Headlight voltage (relative reference).
 Decoder MX620, MX62, MX63, MX64, MX64D, MX64P Page 13

CV Designation Range Default Description CV Designation Range Default Description

Intensity of back-EMF control for lowest speed step. Values to turn Bit “on”: MX64D high frequency shorts”, for C-Sinus motors
Bit 0: 1
Example: Bit 1: 2
Bit 4 Bit 2 = 0: Loco number recognition off
# 58 = 0: no back-EMF Bit 2: 4 from = 1: Loco number recognition on
0 – 255
Back-EMF # 58 = 150: medium compensation, Bit 3: 8 SW-Version (Turning the loco number recognition off prevents a
#58 (See add. 255 Bit 4: 16
intensity # 58 = 255: maximum Compensation. 25 possible ticking sound if this feature is not used).
notes) Bit 5: 32
If required, an “intensity curve” can be achieved using Bit 6: 64 also in
Bit 7: 128 MX62, Bit 3 = 0: reacts only to the (new) NMRA-
CV #10, 58 and 113 to reduce load regulation at higher MAN-Bit, 12 function mode
speeds. MX63,
MX64 ! = 1: also reacts to old MAN bit,
ZIMO MX21, MX31… cabs
also display the individual
8 function mode
This value divided by 10 is the time in seconds it takes
bits; Bit 4 = 0: Pulse chain recognition off
From SW to start a signal controlled acceleration after receiving a
version 13; calculating bit values is no = 1: Pulse chain recognition on (use with LGB sys-
higher speed limit command with: longer necessary!!
Signal dependent 5 tems)
#59 0 - 255 “ZIMO signal controlled speed influence” (requires
reaction time (older Bit 5 = 0: 20 kHz frequency
ZIMO MX9 track section module or (TSE) track section
versions de- = 1: 40 kHz frequency
fault value: 0)
encoder)
or “asymmetrical DCC signal” method (Lenz ABC). Bit 6 = 0: normal (also see CV #129 description)
= 1: non-directional DC braking („Märklin-
The actual function output voltage can be reduced by Brake mode)
PWM. Useful to dim headlights, for example. Bit 7 = 0: no pulse chain generation
Reduced function out-
#60 put voltage 0 - 255 0 Example values: = 1: Generates pulse chain commands for LGB
(Dimming) # 60 = 0 or 255: full voltage sound modules on function output FO1.
# 60 = 170: 2/3 of full voltage.
Only in MOTOROLA format:
# 60 = 204: 80% of full voltage.
Bit 3 = 0: normal, 4 functions for each address
For applications not covered by NMRA function map- = 1: next address is used to control 4 more
ping (CV #33 - #46), for example: “Swiss lighting”; see functions, for a total of 8 functions, which is
MX62 - 64: “function mapping – ZIMO extensions”. otherwise not possible within a MOTOROLA
1 to 6 MX62, MX63, MX64: system.
MX620 = 3, 4…. Special function mapping table for often used
Special ZIMO lighting variations. Intensity of back-EMF is reduced above the speed step
#61 MX64D, 0
function mapping EMF reduction 0 – 255 defined in CV #10, to the value entered here. Together,
MX64P: MX620:
#113 Note: This CV is rarely nec- (See add. 0 CV #10, #58 and #113 define a BEMF curve.
= 98: starts a flexible function mapping for directional
98, 99 essary notes) If set to 0, BEMF is totally cut-off above the speed step
function control, automated function turn-off after stop-
(See function defined in CV #10.
mapping)
ping and more.
See “ZIMO special function mapping” (at end of this Bit 0 to 5 for one function output each
chapter) ! (Bit 0 = front headlight, Bit 1 = rear headlight,
Bit 2 = function output F1, etc.)
User programmable speed table. Bits Bit value=0: Output dimmed to value defined
#114 Dimming mask 0
0-5 in CV #60.
0 – 252 Only active if Bit 4 in CV #29 is set to 1.
#67- Bit value=1: Output not dimmed.
Individual speed table (See add. **) Each CV corresponds to one internal speed step that
94
notes)
can be “mapped” to an external step (in-between speed See page 31 for Bit value calculation!
steps will be interpolated when using 128 speed steps).
Uncoupler control Active if “uncoupling” is selected (with value of 48) in CV
Multiplication of the current speed by “n/128” (n is the (KROIS and ROCO) #125......132:
#66 Directional 0 - 255 0 trim value in this CV) “Pull-in” time and Tens digit = 0 - 9, pull-in time in seconds of applied full
#95 speed trimming 0 - 255 0 #66: for forward direction “hold” voltage voltage:
#95: for reverse direction 0 – 99
#115 0 Value: 0 1 2 3 4 5 6 7 8 9
See chapter 4
CV # 115 Seconds: 0 .1 .2 .4 .8 1 2 3 4 5
#105 0 – 255 0 alternatively used for
User data Free memory space to store user supplied data. Ones digit = 0 to 9, hold power in percent of track volt-
#106 0 – 255 0 additional dim value
(0-90% according to ones
age, 0 - 90%. Applied after the pull-in time elapsed
Special ZIMO Bit 0 = 0: Normal application digit; set tens digit to 0) (ROCO uncoupler)
0 – 255
configuration bits = 1: For C-Sinus Motor application
#112 Bits 0,1 Automated 0 – 99 Tens digit (0 – 9): Length of time the loco should move
(C-Sinus) Bit 1 = 0: Normal „service mode“ Acknowledgement away from train; values as in CV #115.
4= #116 uncoupling procedure 100 – 199 0
only for 00000100 = 1: Special acknowledgement with “internal
MX62,MX63, MX64: See de- Ones digit (0 – 9) x 4 = Internal speed step applied
 Page 14 Decoder MX620, MX62, MX63, MX64, MX64D, MX64V

CV Designation Range Default Description CV Designation Range Default Description

from SW-Version 25 scription in to loco (Momentum per CV #3 etc.) Bit 0 = 0: no effect with above key’s
MX620: SW-Vers. 3 chapter 7 ! Hundredths digit = 0: No tension relieve. Shunting key = 1: removes momentum of CV #121+122
= 1: Tension relieve: loco moves functions: Bit 1 = 0: no effect,
toward coupler (to relieve tension) = 1: CV #3 + 4 reduced to ¼.
before moving away.
Momentum Bit 0 + Bit 1= 0: no effect
reduction or = 1 removes all momentum above.
Duty cycle for flasher function:
deactivation Bit 3 = 1: F7 as half speed key
#117 Flasher 0 – 99 0 Tens digit = on time (0 = 100msec…..9 = 1 sec) Bit 4 = 1: F3 as half speed key
Ones digit = off time (0 = 100msec…..9 = 1 sec) Bit 5 = 1: For “DC” stopping method *)
and Bit 6 = 1: F3 as shunting key (instead of F4
Bit 0 to 5 for one function output each as in Bit 2).
(Bit 0 = front headlight, Bit 1 = rear Bit 7 = 1: SUSI deactivated. Solder pads can be
headlight, Bit 2 = function output Low gear used as FO3 and FO4 instead.
F1, etc.) *) If polarity dependent “DC” stopping method is used
Bits
#118 Flashing mask 0 Bit values = 0: no flasher and (i.e. Märklin), set
0–7
Bit values = 1: output flashing CV #29, Bit 2 = 0 and CV #124, Bit 5 = 1 !
Bit 6 = 1: 4th output flashing inverse! See page 31 for Bit value calculation!
Bit 7 = 1: 6th output flashing inverse! SUSI assignment.
See page 31 for Bit value calculation!
Bits 0,1
Special effects value = 0: independent of direction
Bit 0 to 5 for one function output each =1:active in forward direction
(Bit 0 = front headlight, Bit 1 = rear Uncoupler, “soft start”
=2:active in reverse direction
headlight, Bit 2 = function output of function
ATTENTION: change CV’s #33, 34.... if direction is
F1, etc.) outputs at
wrong!
activation
Bits Bit values = 0: no low beam function Bits 2 - 7
#119 Low beam mask for F6 0 Bit values = 1: Low beam with key F6, brightness or
0-7 value = 4 Mars light
determined by value in CV #60. American lighting = 8 Random Flicker
Bit 7 = 0: normal effect of F6. effects for front head- = 12 Flashing headlight
= 1: effect of F6 inverted. lights. = 16 Single pulse strobe
See page 31 for Bit value calculation! = 20 Double pulse strobe
Operates with F0 in = 24 Rotary beacon simulation.
#125 1 forward direction by 0 = 28 Gyralite
#120 Low beam mask for F7 Bits 0 - 7 Same as in CV #119 but for F7 key. default, unless = 32 Ditch light type 1, right
assigned different = 36 Ditch light type 1, left
Acceleration time (momentum) can be stretched in the through function = 40 Ditch light type 2, right
0 – 99 lower speed range: mapping.
Exponential = 44 Ditch light type 2, left
#121 (See add. 00 Tens digit: Percentage of speed range to be = 48 Uncoupler as in CV#115
acceleration Effects can be further
notes) included (0 to 90). adjusted and modified = 52 Soft start up of function output
Ones digit: Exponential curve (0 to 9). with EXAMPLES
You want : Program CV #125 to:
Deceleration time (momentum) can be stretched in the CVs #62 - 64
Mars light forward only - 5
0 – 99 lower speed range: and Gyralite independent of direction - 28
Exponential
#122 (See add. 00 Tens digit: Percentage of speed range to be CV #115 Ditch type 1 left, only forward - 37
deceleration
notes) included (0 to 90). (for uncoupler). Uncoupler- 48
Ones digit: Exponential curve (0 to 9). Soft start of output- (i.e. headlights) 52

Raising or lowering the speed to the next internal step Special effects Bits 0,1
occurs only if the preceding step is nearly reached. The #126 0 value = 0: independent of direction
tolerance for reaching the preceding step can be de- For =1:active in forward direction
Adaptive 0 – 99 fined by this CV (the smaller this value the smoother the rear headlight
#123 acceleration and de- (See add. 0 acceleration/deceleration).
celeration notes)
Tens digit: 0 - 9 for acceleration
Ones digit: 0 - 9 for deceleration
Value 0 = no adaptive accel. or decel.
1
Note to ditch lights: Ditch lights are only active when headlights and function F2 (#3 on Zimo cab) are on, which is prototypical for North American
railroads. The ditch lights will only be working if the applicable bits in CV #33 and 34 are on (the definition in CV #125 - 128 in itself is not enough
(See add.
Bit 2 = 0: “MAN” key for shunting, but a necessary addition).
#124 notes) 0 = 1: F4 key for shunting (see Bit 6 for F3 Example: If ditch lights are defined for F1 and F2, the bits #2 and 3 in CV #33 and 34 have to be set accordingly (i.e. CV # 33 = 13 (00001101), CV
key instead of F4) # 34 = 14 (00001110).
 Decoder MX620, MX62, MX63, MX64, MX64D, MX64P Page 15

CV Designation Range Default Description CV Designation Range Default Description

(default F0 reverse) =2:active in reverse direction asymmetry, see chapter 4!

ATTENTION: change CV’s #33, 34.... if direction is
wrong! See CV #125 for details. = 0: km/h – Regulation turned off; the “normal” speed
regulation is in effect.
#127 Special effects 0 See CV #125 for details. Start with Pseudo-Programming („Pseudo“ = pro-
for FO1 (default F1) grammed value is not being stored):
CV #135 = 1 -> Initiates a calibration run
#128 Special effects 0 See CV #125 for details. (see chapter 4, „km/h – speed regulation“)
For FO2 (default F2) 2 – 20
0 Continue with “normal“ programming of CV #135 (pro-
km/h – grammed value will be stored):
Special effects MX62, Speed regulation -
MX63, = 2 to 20: speed steps / km/h – factor; e.g.:
for See CV #125 for details. #135
#129 - MX64: Activating, control and
FO3, FO4 0 See = 10: each step (1 to 126) represents
from SW- Only usable if outputs FO3 and FO4 are activated by range
#130 chapter 4, 1 km/h: that is step 1 = 1 km/h,
(default Version 22 deactivating the SUSI function definition
„km/h – step 2 = 2 km/h, step 3 = 3 km/h,
F3, F4) and up (CV #124, Bit 7 = 1).
speed = 20: each step represents 2 km/h;
Only MX620 ! regulation“! step 1 = 2 km/h, step 2 = 4 km/h,
Light effects
#62 0-9 0 Change of minimum dimming value (FX_MIN_DIM) last step 126 = 253 km/h.
modifications
= 5: each step represents .5 km/h;
Tens digit: sets cycle time (0 - 9, default 5), or start up step 1 = .5 km/h, step 2 = 1 km/h,
Light effects time during soft start (0 - 0,9s) last step 126 = 63 km/h.
#63 0 - 99 51
modifications
Ones digit: extends “off” time

Light effects
#64 0-9 5 Ditch light off-time modification A numeric value can be read-out after a successful cali-
modifications
km/h – See bration run, which was used to calculate the speed. This
Speed regulation - chapter 4, value is interesting because it is (almost) independent
The pulse rate selected here is the exhaust chuff rate #136
sent through function output 2 to the sound module, in Control number read- „km/h – - from the selected speed during the calibration run. The
place of an actual exhaust cam mounted at the wheel. out speed uniformity of the resulting values from several calibra-
0 Also see chapter 7! regulation“! tion runs may be an indication of the calibration quality.
Function output 2 as Only MX620 !
0 – 255 (= FO2 See chapter 4!
virtual = 40 (Default): Approximately 2 pulses per
#133 defined as
exhaust cam MX62 - 64: normal wheel revolution of a typical LGB loco;
The direction bits, added in 2006, are an extension of
for from function out- although the actual frequency depends
the ZIMO “signal controlled speed influence” (“HLU”
external SW 25 put, not as on the drive type and adjustments.
virtual ex- Deactivating the “HLU” method); the bits allow for direction dependent speed
sound modules Adjustments: a smaller value in CV #133 results in
haust cam) direction bits limit or stop section applications.
higher frequency, a higher value decreases frequency.
#137 Bits Explanations to “direction bits” are also found in
For example: CV #133 = 20 (instead of 40) generates 4 0
0-2 the MX9 track section module manual.
chuffs per wheel revolution (instead of 2). MX62, MX63, MX64:
from SW-Version 25; Bit 0 = 1: ignores the „first direction bit“
Hundredths digit: Sensitivity adjustment, changes the MX620 later Bit 1 = 1: ignores the „second direction bit“
speed with which the asymmetry is being recognized. Bit 2 = 1: accepts both direction bits.
Asymmetrical = 0: fast recognition (but higher risk of errors, i.e. See page 31 for Bit value calculation!
threshold for unreliable stopping.
stopping with asym- = 1: normal recognition (@ 0.5 sec.), pretty save Direction dependent A stop section H (=Halt) is interpreted as a “Go” section
metrical DCC signal 1 - 14, results (default). conversion of a stop in the opposite direction:
(Lenz ABC method). = 2: slow recognition (@ 1 sec.), very reliable. (H) section to a “Go” = 4: as „U“ = 5: Intermediate steps
101 - 114, #138
section. 0-8 0 = 6: as „L“ = 7: Intermediate steps
#134 Tenths and ones digit: Asymmetrical threshold in tenths
201 - 214 106 of a volt. MX62, MX63, MX64: = 8: as „F“
MX63, MX64: from SW-Version 25;
beginning with SW- This voltage difference between the half waves of the
= MX620 later
Version 25. 0,1 - 1,4 V
DCC signal is the minimum required to be recognized
as asymmetrical that starts the intended effect (usually
MX620: Direction dependent 0–8 . A speed setting F, L, or U (or intermediate steps) is to
braking and stopping of a train).
functional with first SW conversion of F, L, U. If ABC behavior is de- be interpreted as stop “H” (=Halt):
Also see CV #27! #139
version. MX62, MX63, MX64: sired but with HLU = 2 as „H“ = 4: as „U“ = 5: Intermediate steps
= 106 (Default) therefore means 0.6 V. This value has method: = 6: as „L“ = 7: Intermediate steps = 8: as „F“
from SW-Version 25;
proven itself to be appropriate under CV #138 and 139 = „8“
MX620 later
normal conditions; by using 4 diodes to generate the
 Page 16 Decoder MX620, MX62, MX63, MX64, MX64D, MX64V

CV Designation Range Default Description 4. Additional notes to Configuration Variables

Distance
Activates distance controlled stopping as per CV #141
in place of time-constant braking (CV’s)
according to CV #4.
controlled
stopping = 1: automatic stops with “signal controlled Optimal Control, Automated Stops, Effects . . .
(constant stopping speed influence” or “asymmetrical DCC
distance) signal”.
#140 0, = 2: manual stops using the cab. Two ways of programming speed curves:
Select start of braking 1, 2, 3, 0
= 3: automatic and manual stops. Programmable speed curves can often optimize the driving characteristics of an engine. These curves alter
and 11, 12, 13
The start of braking is delayed in above cases (= 1, 2, the relationship between the cab’s speed regulator settings and the engines speed (that is between 14, 28
braking process
3), if the train travels at less than full speed to prevent or 128 external speed steps of the cab and the 252 internal speed steps of the decoder).
an unnecessary long “creeping” (recommended).
Which one of the two speed curves the decoder applies is determined by Bit 4 of Configuration Variable #29: “0" assigns
MX62, MX63, MX64: On the other hand: the first type - Three Step Programming, defined by just three CV’s;
from SW-Version 25 ! ”1" assigns the second type - Programmable Speed Table, defined by 28 individual CV’s.
= 11, 12, 13 selection as above but braking starts al-
ways immediately after entering the brake section. Three step programming: by using the Configuration Variables #2 for Vstart, #5 for Vhigh and #6 for Vmid.
Vstart defines one internal speed step out of a total of 252 to the first speed step of the cab, Vhigh to the
Distance This CV defines the “constant stopping distance”. The
controlled right value for the existing stop sections has to be de- highest speed step and Vmid to the center speed step of the cab. In this way a simple bent acceleration
stopping termined by trial. curve can be achieved with an expanded lower speed range.
(constant stopping Use these figures as a starting point: A slightly bent curve is active by default (CV #6 = 1), that is the center speed step is limited to 1/3 of full
#141
distance)
0 - 255 0 CV #141=255 is about 1 scale-km (12m in H0), CV speed.
Distance calculation #141=50 about 200 m (2,4m in H0) Programmable speed table: with the help of the programmable speed table, free programming of all Con-
figuration Variables from #67 to 94 is possible. Each of the 28 external speed steps is assigned to one in-
MX62, MX63, MX64: ternal step (0 to 252). If 128 external speed steps are used, an interpolation algorithm is used to calculate
from SW-Version 25! the steps in between.

Distance The delayed recognition (see CV #134) but also unreli-

NOTE: The three step programming is in most cases entirely sufficient for good drivability; the relatively
controlled able electrical contact between rail and wheels has a complex procedure of defining a speed table is only recommended with the help of software like ADaPT
stopping larger effect on a stop point at higher speeds than at that graphically draws the speed curve and automatically sends the data to the decoder.
(constant stopping lower speeds. This effect is corrected with CV #142.
distance) 250 250

In tern al spe e d ste p

2 50
#142 0 - 255 12 = 12: Default. This setting usually works fine if CV #134 240 7 240 2 40
230 12 230 2 30
High-speed correction id=
220 220
is set to default also. 210 210
2 20
200 Vm 2 10
2,
200 2 00
using the ABC method 190
180 25
190
180
1 90

170 h= 170
1 80
hig
1 70
160 160
MX62, MX63, MX64: 150
External speed step
1,
V 150
1 60
1 50
140 = 140 1 40
from SW-Version 25! 130 art
st 130 1 30
-V
120 120 1 20
110 110 1 10
c
risit
100 Slightly bent 100 1 00
90 (default) characterisitc 90 90
80 c te 80
… compensation Since the HLU method is more reliable than the ABC 70 ara Vmid = 1 (equals 85) 70
80
70
60
r ch Vstart = 2 60 60
using the HLU method method, no recognition delay is usually required in CV 50
40 ea Vhigh = 1 50 Clipped linear speed curve 50
Lin
40 Vstart = 10, Vhigh = 165, 40
30 (equals 252) 30 30 Clipped and bent speed curve
#143 0 - 255 0 #134; therefore this CV can also remain at default set- 20
10 Center
20
10
Vmid = 90 20
10
Vstart = 15, Vhigh = 180, Vmid = 60
ting 0. 0
0 1 2 3 4 5 6 7 8 109 11 12 13 14 15 16 17 18 19
20 21 22 23 24 25 26 27 28
0
0 1 2 3 4 5 6 7 8 10
9 11 12 13 14 15 16 17 18 19
20 21 22 23 24 25 26 27 28
0
0 1 2 3 4 5 6 7 8 10
9 11 12 13 14 15 16 17 18 19
20 21 22 23 24 25 26 27 28
MX62, MX63, MX64: 0 9 18 27 36 45 54 63 72 81 90 99 108 117 1 26 0 9 18 27 36 45 54 63 72 81 90 99 108 117 1 26 0 9 18 27 36 45 54 63 72 81 90 99 108 117 1 26

from SW-Version 25! 25 0

24 0
23 0
22 0
21 0
20 0
19 0
18 0
17 0
16 0
15 0
14 0
13 0
12 0
11 0
10 0
90 Example of a freely
80
70
programmed speed
60 curve according to
50 the values entered
40
30 in to configuration
20 variables #67 - 94.
10
0
0 1 2 3 4 5 6 7 8 10
9 11 12 13 14 15 16 17 18 19
20 21 22 23 24 25 26 27 28
0 9 18 27 36 45 54 63 72 81 90 99 108 117 1 26
 Decoder MX620, MX62, MX63, MX64, MX64D, MX64P Page 17

The relative reference is suitable as long as a constant voltage is present (which is the case with all Zimo
Motor control frequency and EMF scanning rate: systems but not all competitor systems) and the resistance along the track is kept to a minimum.
In case of Faulhaber, Maxxon or similar motors (Coreless): The driving characteristic of an engine can further be optimized by adjusting the intensity of load
Start with special CV #56 = 100 programming !!! compensation with CV #58. The goal of load compensation, at least in theory, is to keep the
speed constant in all circumstances (only limited by available power). In reality though, a certain reduction
The motor is controlled by pulse with modulation that can take place at either low or high frequency. This in compensation is quite often preferred.
frequency is selected with configuration variable #9 (NMRA conforming formula, see CV table). 100% load compensation is useful within the low speed range to successfully prevent engines from stalling
High frequency control: The motor is controlled at 20kHz in default mode or whenever a value of “0” is en- or picking up speed under load. BEMF should rather be reduced as speed increases, so that at full speed
tered to CV #9, which can be raised to 40kHz with bit 5 in CV #112. The effect is comparable to operating the motor receives full power with little BEMF. A slight grade dependent speed change is often considered
with DC voltage and is likewise just as noiseless (no hum as with low frequency) and easy on the motor more prototypical. Consists also should never be operated with 100% BEMF because it causes the locomo-
(minimum thermal and mechanical stress). It is ideal for coreless motors (recommended by Faulhaber!) and tives to fight each other by compensating too hard and too fast, which could lead to derailments.
other high performance motors (most modern motors, including LGB). It is not recommended however, for The degree of load compensation can be defined with Configuration Variable #58 from no compensation
AC motors and some older motors. (value 0) to full compensation (value 255). This, in effect, is the amount of compensation applied to the low-
When operating at high frequency, power to the motor is interrupted periodically in order to determine the est speed step. Typical and proven values are in the range of 100 to 200.
current speed by measuring back-EMF (voltage generated by the motor). The more frequently this interrup- If an even more precise load compensation is required (though hardly ever necessary), configuration
tion takes place, that is the higher the EMF sampling frequency, the better the load compensation per- variable #10 and #113 presents a solution. CV #10 defines a speed step at which the load compensation
forms (see next page); but that also results in a certain loss of power. This sampling frequency varies is reduced to the level defined in CV #113. Both CV’s have to have a value other than 0. If either CV #10
automatically in the default mode (CV #9 = 0) between 200Hz at low speed and 50 Hz at maximum speed. or #113 is set to 0, BEMF is again solely based on CV #58.
CV #9 allows the adjustment of the sampling frequency as well as the sampling time. 250
250
240
R eg
CV e lun g
240 D 230
v ers # 10 = s kenn

Regl eungsei nfl uß

230 C ef 220
v V ault t ärk lin
* It is recommended in most cases where an improvement is still required for MAXXON, Faulhaber of simi- 220
210
200
a b olle # 58 -R e
si Au = g e
210
200
1
te A 26 , C ie
us re V #
190 11
n k s 2 lu mit glung 3 =
lar motors, to select a lower sample frequency such as CV #9 = 11, 12, 21, 22 etc after CV #56 was pro- 190
180
170
en re 55 ng
d g lu , C sk
bi n g V e
180
170
De
im 200
,
s 0 b # nn Int. Fahrstufe 160
160 fa
grammed to 100; this will in any case reduce motor noise! 150
140
Ke
n
be ei L 1 0 lin ie
iv a u
150
140 ult
-Re
CV n li oll n g n d 130 ge
130
120 re d # 5 n ie d er sa # 120 lun
* for older type motors use rather the opposite, e.g. CV #9 = 88. 110
100
Ge u zie 8 = es
s ch rte 18 0 Re g
F a mf 113
hr a h =
t . rt, 0
110
100
90
gs
ke
nn
90 win A u , C elu lin
Also see CV table and the following page! 80
70
dig sr e V # ng
ke glu 1 0 s e in
itsb n g u f
80
70
60
ie
60 e re in a nd #lu ss e
50 ich ll e s 50
40
Low frequency control: Entering a value between 176 and 255 to CV #9 drives the motor between 30 and 40
30
20
e n n 113 =
. 0 30
20
150 Hz. Most often used value is 208 for 80 Hz. This is rarely used today and is only suitable for AC motors 10
0
10
0
0 20 40 60 80 100 150 200 0 20 40 60 80 100 150 200 252
with field coils.
Regarding configurations variable #56 – if proportional and integral values are set to default
The load compensation: (zero) or “100” for coreless motors (Faulhaber, Maxxon etc) but drivability is not satisfactory:
See CV table and the following chapter on “Step by step…..)!
All Zimo decoders come equipped with load compensation, also known as BEMF to keep a constant
speed, regardless whether the engine is pulling a short or long train uphill, downhill or around a tight radius
(although the speed will not be held 100% constant, especially in the upper speed range). This is accom-
plished by constantly comparing the desired value (speed regulator setting) and the actual value at the mo- Acceleration and deceleration characteristics (momentum):
tor, determined with the EMF method (EMF stands for Electro Motive Force and is the force (power) pro- Configuration Variables #3 and #4 provide a way of setting a basic linear acceleration and decelera-
duced by the motor when it is turned without power applied to it). tion rate according to NMRA rules and regulations. That is, the speed is changed in equal time intervals
from one speed step to the next.
The Reference Voltage used for the BEMF algorithm can be defined by configuration variable #57
as either absolute or relative (default). To simply achieve smooth transitions during speed changes, a value between 1 and 3 is recommended.
The true slow starts and stops begin with a value of about 5. Programming a value higher than 30 is seldom
Absolute Reference:
practical!
A voltage value is defined in CV #57 as a base line for the BEMF calculation. For
example: if 14V is selected (CV value: 140), the decoder then tries to send the exact fraction of the voltage The momentum can be modified with Configuration Variables #121 and #122 to an exponential accel-
indicated by the speed regulator position to the motor, regardless of the voltage level at the track. As a re- eration and deceleration rate, independent from each other. This in effect expands the momentum in the
sult the speed remains constant even if the track voltage fluctuates, provided the track voltage (more pre- lower speed range. The area of this expansion (percentage of speed range) and its curvature can be de-
cisely, the rectified and processed voltage inside the decoder, which is about 2V lower) doesn’t fall below fined.
the absolute reference voltage. A typical and practical value is “25” (as starting point for further trials).
The "absolute reference" is to be preferred to the "relative reference" when using other vendors' systems The adaptive acceleration and deceleration procedure defined by configuration variable #123 will not
(particularly those that don’t keep the track voltage stabilized)! allow a change in speed until the previous target speed step of an acceleration/deceleration event is nearly
Relative Reference: The speed range is automatically adjusted to the available track voltage, if a 0 is en- reached.
tered to CV #57 (default). Therefore, the higher this voltage is set at the command station (adjustable be- Most often applied values are “22 or “11”, which can noticeably reduce a start-up jolt (the effect increases
tween 12V and 24V) the faster the train will be over its entire speed range. with smaller figures).
 Page 18 Decoder MX620, MX62, MX63, MX64, MX64D, MX64V

Step by step CV adjustment procedure to optimize engine per- * After increasing the value of CV #56, check that the engine is not running jerkily at mid speed level. Use
CV #58 to counteract that. Either reduce the value of CV #58 (default 250) down to between 150 and 200 to
formance: generally reduce the load compensation, or use CV #10 and #113 to cut the load compensation at a speed
It is recommended to systematically program a decoder since setting the CV’s for load compensation and just below the start of the jerky motion (the compensation is reduced to the level defined with CV #113 at
momentum can result in a certain interaction with each other (This guide applies to SW version 10 or the speed step defined with CV #10).
higher): * If after the above adjustments the engine’s speed is still fluctuating, CV #57 should be used for further
* To begin, select the highest possible number of speed steps the system can operate in, that would be 128 fine-tuning. With a default value of 0, load compensation is based on the measured track voltage. If this
for Zimo (select the number of speed steps at the cab for the decoder address in question). All Zimo de- voltage fluctuates, the speed will fluctuate also. The cause is usually a DCC system that can’t compensate
coders are set by default to 28 /128 speed steps. If used with systems that are restricted to 14 steps set Bit for voltage drops (other than Zimo systems) or dirty wheels or track. To prevent such fluctuations the cur-
1 in CV #29 to 0. rent track voltage x10 is entered to CV #57 (not idle track voltage, rather voltage under load). For example,
if an engine needs 14 V (measured under load) a value of 140 should be entered. Sometimes it’s even bet-
* Next set the engine to the lowest step, recognizable on the Zimo cab’s when the bottom LED next to the ter to keep this value about 20% lower to compensate for a slight internal voltage drop in the decoder.
speed slider changes color from red to green (change the cab to 128 speed steps first, it is set by default to
28 speed steps!) and/or the speed step displayed on the screen of the MX21/MX31 cabs. * Next, we check to see whether the loco’s initial start is smooth or abrupt. This can be seen well with some
momentum added. Temporarily, set some momentum with CV #3 and #4. Use CV #3 for acceleration and
If the engine is now running to slow or not at all, increase the value in CV #2 (default 2), if it runs too fast CV #4 for deceleration adjustments. Start with a value of 5.
decrease the value. If the individual speed table is used (CV #67 - 94, active if bit 4 of CV #29 is set), set
the lowest speed step with CV #67 instead and adjust the rest of the speed table CV’s accordingly. The adaptive acceleration/deceleration procedure can now be used to eliminate abrupt starts by changing
the value in CV #123. Start with a value of 30. The lower the value, the stronger the effect will be (e.g. 10
* The EMF sampling process is not only critical for smooth even low speed behavior but also for quiet motor results in the strongest effect for acceleration, 90 or 99 the weakest). The tens digit is for defining the adap-
performance (see previous page but also CV #56!), which can be modified with CV #9. This CV is also used tive acceleration and the ones digit for the adaptive deceleration. To achieve the same results for both ac-
to set the decoder to low frequency motor control, which is used only rarely with older AC motors. celeration and deceleration enter the same value in tens and ones, in this example 33. However, if used in
By default, CV #9 is set to high frequency at 20 kHz (can be raised to 40 kHz with Bit 5 of CV #112) and automated operations where precise stop points are required, set the ones digit to 0.
automatically adapts the EMF sample rate to the loco speed. If drivability is not flawless or too much motor * After changing the values in CV #123 the basic momentum may need to be readjusted to your prefer-
noise is audible, fine-tuning is possible with the help of CV #9 and CV #56. ences; first with CV’s #3 and #4 (basic momentum) and if desired with CV’s 121 and 122 (exponential mo-
In case of a coreless motor design such as Faulhaber, MAXXON or similar, start by setting mentum).
CV #56 = 100 (in place of the default value of 0 (zero) for “normal” motors); the “1”
in the hundred digit causes among others the mid-range setting to match high-efficient motors, which is
* If a locomotive starts up too fast or comes to a stop too quickly, which is often the case even though the
basic momentum is set to your liking, use CV #121 and #122 to add an exponential acceleration and de-
similar to a value of “11” but with further adjustment possibilities in both directions using the tens and ones
celeration curve. This in effect will stretch the time the locomotive spends in the lower speed range. Often
digit.
used values for these CV’s are in the range of 25 to 55. Tens digits define the percentage of the speed ta-
With CV #9 the frequency and the length of the EMF sampling, which interrupts power to the motor, can be ble to be included in this curve (20% - 50% in this example). Ones digits define the curvature.
adjusted independently: using the tens and ones digit of the configuration variable, each in the range of 1 –
9.
Notes on acceleration behavior versus speed steps:
In general: High-efficient motors such as Faulhaber, Maxxon, Escap etc can manage with fewer samples; An acceleration or deceleration sequence according to CV #3 and 4 that is the timely succession of speed steps is always
both values can therefore be set low (i.e. CV #9 = 11 or 22), which lowers the noise level and increases the based on the internal 252 steps which are spaced identical from 0 to full speed. Neither speed table (three steps nor individ-
available power. Especially the length of the sample time (ones digit) can often be set to a minimum (1). ual speed table) has any effect on the acceleration or deceleration behavior. The speed tables only define the target speed
for a particular speed dialed-in by the cab.
If an engine with an older motor design runs rough at low speeds, the sample frequency (tens digit) is usu-
ally the one that needs to be set to a larger value (>5), which often requires the sample time (ones digit) to This means that the acceleration or deceleration behavior can not be improved by a bent speed curve as defined by CV #2,
be set to a higher value as well (>5); i.e. CV #9 = 88. #5, #6 or the individual speed table CV’s #67 - 94. The exception to this could only be a cab or computer controlled accel-
eration or deceleration event. A decoder controlled acceleration or deceleration event can only be influenced by CV #121
If during acceleration with applied momentum (i.e. CV #3 = 10) the speed visibly rises in steps (which has and #122.
nothing to do with the actual speed steps), the sampling time (ones digit) should be increased above 5, e.g.
CV #9 = 58 - If applicable see section “Settings for the signal controlled speed influence“!
* If, after setting CV #9, the engine still doesn’t run smoothly enough at the lowest speed step, changing - If applicable see section “Setting for stopping with ...“!
the values of the ones and tens digit in CV #56 (default value 55) will often improve it. These values define - If applicable see section “Distance controlled stopping” (constant stopping distance)!
the proportional and integral portion of the PID control. By default (CV #56 = 0) or with the setting for core-
less motors such as Faulhaber, MAXXON etc (CV #56 = 100, see above), the proportional value adjusts it-
self automatically and the integral value is set to mid-value. Depending on the type of motor, other values
than the default value can be used, such as 77, 88 or 99 for older locos that run rough or 33, 22, or 11 for
newer locos with more efficient motors (Faulhaber, MAXXON etc). With the help of the integral value a pos-
sible overcompensation can be improved by moving the value of CV #56 (ones digit) away from the center
“5”).
 Decoder MX620, MX62, MX63, MX64, MX64D, MX64P Page 19

Case studies of practical CV programming: CV #57 = xx … See above („Roco Loc“) !

CV #3 = 2 (> 2) These recommendations are true here as in almost all other cases (see above
The fine-tuning of a locomotive is not difficult but represents uncharted territory for many users. The follow- CV #4 = 2 (> 2) “Roco Loc“).
ing is meant to assist you with actual programming cases, which were performed by ZIMO at cus- CV #121 = 11 (>)
tomer’s or locomotive manufacturer’s requests or by close ZIMO partners. CV #122 = 11 (>)

The tuning of a locomotive reflects in part the personal preferences of an individual but must also take into
account the special circumstances of its intended application; still valid suggestions can be drawn from it. NMJ Superline NSB Skd 2220c (small Norwegian switcher engine, built in
It must be pointed out that there can be significant mechanical deviations among mass-produced locomo- 2007)
tives even among identical models but even more so between different models, so that further fine-tuning Product of Norsk Modeljernbane, with Faulhaber-Motor,
can be of advantage (although it is often not really necessary). MX63, with SW based on the version 30, is being installed at the factory; this decoder contains
special software with a hard reset procedure that sets the decoder back to optimized CV values, similar
values as are listed here.
Roco loco of modern design (about 1995 and up) / Original-Roco-Motor This engine served in the development of the regulated analog control!
Such locomotives are operating very good even with the decoder’s default settings, which is also due to ZIMO decoders are very well suited for Faulhaber motors, even with the default settings. An even better
the fact that these locomotives are often used as reference during the ZIMO decoder software develop- result can be achieved with the special Faulhaber setting in CV #56.
ment.
CV#9 = 12 That means shorter EMF measuring time and smaller frequency, which leads to
The settings below Setting CV #57 to a specific value (i.e. CV #57 = 120) differs from the default set- reduced noise and extremely low crawling speed.
are recommended ting (CV #57 = 0) in as much as the top speed no longer depends on the current CV#56 = 155 That means Faulhaber typical measuring time (“1”), medium P/I regulation.
when used with track voltage, provided the track voltage is high enough. For example, if track
non-ZIMO com- voltage is >12V and CV #57 set to 120, the decoder regulates top motor speed to CV#57 = xx … See above under “Roco Loc“.
mand stations: 12V. CV#112 = 0 ZIMO loco number ID (Bit 2 = 0) turned off, which by default is turned on (Bit 2 =
CV #57 = xx, i.e. This is an advantage if the command station is not from ZIMO, because most of That is: Bit 2 = 0, 1, that’s why CV #112 = 4). This prevents small ticking sounds (audible in metal
= 120 (12 V) or them don’t regulate track voltage. There is no difference within a ZIMO system all other Bits are al- locomotives).
= 140 (14 V) or because the track voltage is kept constant (with the exception of voltage drops ready at 0 by de- This preventive step is only of significance in conjunction with a ZIMO DCC sys-
= 150 (15 V) etc. along the track, due to poor layout wiring). A disadvantage of using CV #57 with a fault. tem, because no loco number pulses are produced in other systems (and there-
as track voltage specific value is that the value used has to be in relation to the actual track volt- fore no ticking sounds can be heard).
under load, but not age, which is a manual intervention whereas CV #57 = 0 is self-regulating. If on the other hand the loco number identification within a ZIMO systems is being
higher than that. CV #57 is also suitable for limiting top speed, alternatively to CV #5 and can of used (MX9 modules with MX9AZN boards), the loco number pulses must of
course also be utilized with ZIMO systems. For example: CV #57 = 130 and a course not be turned off!
track voltage of 18V will reduce the overall speed (all speed steps) by about 25%. CV#3 = 2 (> 2) These recommendations are true here as in almost all other cases (see above,
CV #3 = 2 (> 2) A minimal value of “2” in CV #3 and #4 eliminates visible speed changes between CV#4 = 2 (> 2) “Roco Loc“).
CV #4 = 2 (> 2) speed steps but has not much to do with prototypical momentum, which requires CV#121 = 11 (>)
CV #121 = 11 (>) much higher values. Higher values (i.e. CV #3 and #4 = 6, CV #121 and #122 = CV # 122 = 11 (>)
CV #122 = 11 (>) 33), depending on operating situations and personal taste, are recommended.

Philotrain, 3-part multi unit (Built in 2007)

Product of Philotrain, with Faulhaber motor,
MX64V1, with SW based on the version 30, installed by the manufacturer.
Fleischmann locomotive with „Round motor“ Three part multi unit with low voltage headlight and interior light bulbs; for this reason a MX64V1 with
The “Round motor” has been Fleischmann’s standard motor until today (2007); a small readjustment of 1.5V low voltage supply for function outputs is being used. The train runs pretty well with a ZIMO decoder
the CV values is appropriate. as is; although a few changes are beneficial.
Furthermore … especially on these motors it is recommended to remove or bypass the built-in filter-
CV #9 = 13 Shorter EMF measuring time and smaller frequency, which leads to reduced noise
ing components such as choke coils and capacitors. Attention: often the “worst” capacitor is the one
and extremely low crawling speed.
that is least visible and/or accessible.
CV #56 = 133 That means Faulhaber typical measuring time (“1”), a little less than medium P/I
CV #56= 33, 44.... It has been demonstrated that reducing the P and I regulation of the BEMF func- regulation (both digits “3” instead of “5”) results in best drivability.
tion is beneficial for the “Round motor” (#56 < 55, which is lower than the default
value). CV #57 = xx … See above under “Roco Loc“).

There is no need to modify CV #9. CV #3 = 2 These settings largely correspond to the general recommendations (see above
 Page 20 Decoder MX620, MX62, MX63, MX64, MX64D, MX64V

CV #4 = 2 under “Roco Loc”; only the range of the “exponential braking” (CV #122) was in- CV #9 = 61 Increased EMF frequency, shortened EMF measuring time (typical coreless)
CV #121 = 11 creased, which together with CV #123 results in smooth stops.
CV #122 = 33 CV #56 = 141 Faulhaber-typical measuring time (“1”), low P regulation because the MX620 regu-
lates automatically, reduced I regulation.
CV #123 = 95 The “adaptive acceleration” (“9”) is used here very sparingly (to prevent a start-up
jolt), the “adaptive deceleration” (“5”) on the other hand a little stronger; this is - CV #57 = 120 Reduced speed range to about 12V motor voltage.
together with CV #122 (see line above) – practical, otherwise it could easily hap- CV #3 = 3 (> 3) Momentum in CV #3 and #4 should not be much smaller than “3” so that good
pen that the train, due to the motor’s momentum, at first isn’t slowed down fast CV #4 = 3 (> 3) starting and stopping behavior is still possible; the exponential accelera-
enough and then suddenly is stopped too fast. The adaptive deceleration adapts CV #121 = 11 (>) tion/deceleration improves starting and stopping further; still higher values for these
the brake response to the mechanical possibilities: The braking distance in- CV #122 = 11 (>) variables (i.e. CV #3, #4 = 6, CV #121, #122 = 33) according to operational circum-
creases and the locomotive comes to a smooth stop. stances and personal taste correspond to even more realistic operations.
CV #112 = 0 ZIMO loco number ID (Bit 2 = 0) turned off, which by default is turned on (Bit 2 = CV #123 = 52 Low intensity for adaptive acceleration (“5“) because start-up acceleration with val-
That is: Bit 2 = 0, 1, that’s why CV #112 = 4). This prevents small ticking sounds (audible in metal ues <5 may be hindered and uneven. Stronger intensity for adaptive deceleration
all other Bits are al- locomotives). (“2”) for smoother stops.
ready at 0 by de- This preventive step is only of significance in conjunction with a ZIMO DCC sys-
fault. tem, because no loco number pulses are produced in other systems (and there-
fore no ticking sounds can be heard).
If on the other hand the loco number identification within a ZIMO systems is being
used (MX9 modules with MX9AZN boards), the loco number pulses must of
course not be turned off!

Märklin 8350 / SBB Series 460 / Maxxon-Motor 25260

Märklin-Product, upgraded with Maxxon motor 25260 (13 mm diameter) by SB-Modellbau.
NOTE: the motor used in this heavy model is actually a little under powered and the flywheel is extremely
small. For this reason, this locomotive is one that is difficult to control and CV tuning is more important
than usual. Even after the fine tuning a certain problem persists during downhill runs, where the locomo-
tive tends to buck a little. Compared to other products, ZIMO decoders manage this locomotive with its
motorization quite well (whereby the MX620 is better than the MX64). It is likely that with future control al-
gorithm (SW versions in the coming month and years) a further perfection level may be achieved.
The attainable drivability especially in the extreme low speed range and the reaction to quick load
changes are marginally better with the MX620 than with the MX64. This seems astounding considering
the large and heavy engine, but might be due to the rather small motor (see above) with the characteris-
tics of an N rather than an HO motor (the MX620 is designed for N-scale motors). Furthermore, an innova-
tive automatic optimization of control parameters is in use, which has not (yet) been implemented in the
MX63/MX64.

Equipped with MX64, SW version 30 (March 2007), favorable CV values are:

CV #9 = 61 Increased EMF frequency, shortened EMF measuring time (typical coreless)

CV #56 = 199 Faulhaber-typical measuring time (“1”), full P/I regulation.
CV #57 = 130 Reduced speed range to about 12V motor voltage.
CV #3 = 3 (> 3) Momentum in CV #3 and #4 should not be much smaller than “3” so that good
CV #4 = 3 (> 3) starting and stopping behavior is still possible; the exponential accelera-
CV #121 = 11 (>) tion/deceleration improves starting and stopping further; still higher values for these
CV #122 = 11 (>) variables (i.e. CV #3, #4 = 6, CV #121, #122 = 33) according to operational circum-
stances and personal taste correspond to even more realistic operations.
CV #123 = 33 Adaptive acceleration and deceleration (medium application) reduces start-up jolt
and smoothes out stops.

Equipped with MX620, SW version 3.1 (Nov. 2006), favorable CV values are:
 Decoder MX620, MX62, MX63, MX64, MX64D, MX64P Page 21

The speed regulation in km/h is not just useful for direct cab control, but also in speed limits through the
Km/h – Speed regulation - MX620, MX64D “signal controlled speed influence” (CV’s 51 – 55). The values entered to those CV’s are also being inter-
CALIBRATION and operation and MX64V only! preted in km/h.
The km/h speed regulation is a new, alternative method of driving with prototypical speeds in all operat- Mph speed regulation:
ing situations: the cab’s speed steps (1 to 126 in the so-called “128 speed step mode”) will be directly inter- A mph speed regulation can be achieved by extending the calibration distance accordingly!
preted as km/h. Preferably all engines of a layout should be set to the same method. Engines equipped with
non-ZIMO decoders can be set up similarly through the programmable speed table (although with more ef- Note:
fort and less precise because there is no readjustment taking place by the decoder). Operating with the km/h speed regulation causes constant readjustments in order to keep the travel dis-
The ZIMO readjustment: the decoder is not limited to converting the speed steps to a km/h scale but tance to be covered as exact as possible. This is an innovative control system that has never been ap-
rather ensures that the desired speed is held, by recalculating the already traveled distance and automati- plied before by ZIMO or any other manufacturer and has undergone little testing. Some unplanned inconsis-
cally readjusts itself. tencies may very well pop up that may need to be corrected with a later software version (do-it-yourself up-
date of new software possible with MXDECUP module).
A CALIBRATION RUN; should be performed with each loco:
First, we need to determine the calibration track: a section of track that measures 100 scale meters (plus
the necessary length before and after, for acceleration and deceleration), of course without inclines, tight Settings for the
radii and other obstacles; for example, for HO (1:87) 115cm; for G-scale (1:22.5) 4.5m. Start and end
points of the calibration distance need to be marked. ZIMO ”signal controlled speed influence“ (HLU)
Start-Marker End-Marker ZIMO digital systems offer a second level of communication for transmitting data from the track sections to
engines that are in such sections. The most common application for this is the “signal controlled speed in-
Enter at steady speed Calibration distance fluence”, that is the stopping of trains and applying of speed limits in 5 stages issued to the track sections
as required with the help of MX9 track section modules or its successors. See ZIMO flyers at www.zimo.at
and MX9 instruction manual.
* Set the loco on the track, with the proper travel direction selected, about 1 to 2 meters before the start
marker and the function F0 (headlights) turned off. Acceleration times (momentum in CV #3 of the decoder The term “HLU” method was coined over the years after the speed limit designation “H” (=Halt or stop), “L”
as well as settings in the cab) should be set to 0 or a small value to prevent any speed changes inside the (=Low speed) and “U” (Ultra low speed). Beginning with SW version 25 (MX62, MX63, MX64) it will also
calibration distance. Otherwise, the length of track before the calibration marker needs to be increased ac- work independent of direction, which may be useful in many situations! See CV’s #137 – 139 in the CV ta-
cordingly. ble.
* The calibration mode is now activated by programming CV #135 = 1 (operational mode programming). * If the “signal controlled speed influence” is being used (only possible within a ZIMO system), the speed
This is a pseudo-programming because the value of 1 does not replace the value already stored in CV limits “U” and “L” (and the intermediate steps if need be) can be set with configuration variables #51 to #55
#135. as well as acceleration and deceleration values (momentum) with CV #49 and #50 (see CV table).
* Move the speed regulator to a medium speed position (1/3 to ½ of full speed); the loco accelerates to- Please note that the signal controlled acceleration and deceleration times are always added to the times
wards the start marker. and curves programmed to CV #3, 4, 121, 122 etc. Signal controlled accelerations and decelerations com-
pared to cab controlled momentum can therefore progress either at the same rate (if CV #49 and #50 is not
* When the engine passes the start marker, turn on the function F0 (headlights); turn F0 off again when
used) or slower (if CV #49 and/or #50 contain a value of >0), but never faster.
passing by the end marker. This ends the calibration run and the loco may be stopped.
It is of utmost importance for a flawlessly working train control system using the signal controlled speed in-
* CV #136 can now be read out for checking purposes. The calibration “result” stored in that CV doesn’t
fluence that the stop and related brake sections are arranged properly everywhere on the layout, especially
mean very much by itself. If however, several calibration runs are performed, the value in CV #136 should
in terms of their length and consistency. Please consult the MX9 instruction manual and the STP manual.
approximately be the same every time, even if the traveling speed is varied.
The braking characteristics should be set up on a suitable test track so that all locos come to a complete
Km/h speed regulation in operation:
stop within about 2/3 of the stop section, which is in HO typically about 15 to 20 cm before the end of a stop
CV #135 defines whether the “normal” or km/h operating mode is in use: section (deceleration rate adjusted with CV #4 and CV #50 as well as the reduced speed with CV #52 for
CV #135 = 0: The engine is controlled in “normal” mode; a possible km/h calibration run performed earlier “U”). Setting the loco up to stop precisely within the last centimeter of a stop section is not recommended
has no effect but the calibration results remain stored in CV #136. because such an exact stop point is, for various reasons, hardly repeatable every time.
CV #135 = 10: each speed step (1 to 126) becomes 1 km/h: that is step 1 = 1 km/h,
step2 = 2 km/h, step 3 = 3 km/h, ... to step 126 = 126 km/h
CV #135 = 5: each speed step (1 to 126) becomes 1/2 km/h: that is step 1 = .5 km/h,
step 2 = 1 km/h, step 3 = 1.5 km/h, ... to step 126 = 63 km/h (for local or
narrow gauge railways!)
CV #135 = 20: each speed step (1 to 126) becomes 2 km/h: that is step 1 = 2 km/h, step 2 =
4 km/h, step 3 = 6 km/h, .to step 126 = 252 km/h (High speed trains!)
 Page 22 Decoder MX620, MX62, MX63, MX64, MX64D, MX64V

Settings for stopping with Decele ra tion sta rts a t ful l spee d
”asymmetrical DCC signal“ (Lenz ABC) Decele ra tion sta rts a t less than ful l spe ed,
with “consta nt stopp ing distan ce ” pr ogr ammed as CV # 140 = 1, 2, 3

Speed
MX63, MX64 from SW version 25. - train stops at desired poi nt by au tomatically delayin g start of braking
follo wed b y “no rmal ” progression.
MX620, MX64D with first SW version.
Th e same with di sa bled constant stoppi ng d istance,
Not in MX62 ! train stops to early.

The “asymmetrical DCC signal” is an alternative method for stopping trains at a “red” signal, for example. All
that is required is a simple circuit made up of 4 or 5 commercially available diodes. Distance

3 diodes in series (4 when using Schottky di- Ente ri ng the stop secti on. Desired stop poi nt
odes) and one in opposite direction in (Or speed re gulator turned to stop)
Track power from
command station Note parallel is the usual arrangement.
3 diodes in series is the The different voltage drops across the di- Decele ra tion sta rts a t ful l spee d
Switch to minimum number of diodes
cancel stops required to stop ZIMO odes results in an asymmetry of about 1 to Decele ra tion sta rts a t less than ful l spe ed,
when signal with “consta nt stopp ing distan ce ” pr ogr ammed as CV # 140 = 11 ,12,13
decoders. 4 or more diodes 2V. The direction in which the diodes are - train stops at desired poin t by automatically re ducing the deceleration
tunrs green. are needed for decoders

Speed
from other manufacturers! mounted determines the polarity of the vaul es inspi te of immediately started stoppi ng sequ ence.
Silicium diodes, Because the diodes cause asymmetry and with it the driving direction
for example an unwanted voltage drop, Th e same with di sa bled constant stoppi ng d istance,
1N5400x use the minimum number a signal stop is initiated. train stops to early.
of diodes depending on
(3 A - Typen) decoder type. The asymmetrical DCC signal stop mode
Travel direction needs to be activated in the decoder with Distance
Red CV #27. Normally bit 1 is set, that is CV
Halt (stop) section #27 = 2, which results in the same direc- Ente ri ng the stop secti on. Desired stop poi nt
tional control as the “Gold” decoder from
Lenz.
The asymmetrical threshold can be modified with CV #134 if necessary, default is 0.4V. At the time of writ-
ing, the “asymmetrical DCC signal” has not been standardized and many DCC systems pay no attention to The distance controlled stopping can take place in two possible ways; see diagram above: The first is the
this feature! recommended method (CV #140 = 1, etc.), where the train entering at less than full speed continues at
first at the same speed before it starts braking at a “normal” deceleration rate (same rate as would be ap-
plied at full speed).
Distance controlled stopping – Constant stopping distance In the second method (CV #140 = 11, etc.), the train immediately starts with the braking procedure, which
may lead to an un-prototypical behavior. It may however be useful to use this method if used together with
MX62, MX63, MX64 from SW version 25. decoders from other manufacturers that do not have this capability in order to harmonize the brake se-
MX620, MX64D, MX64P with first SW version. quences.
Also, the second method may be the preferred method if distance controlled stopping is used manually (CV
When this feature is selected with CV #140 (= 1, 2, 3, 11, 12, 13) it keeps the stopping distance as close as #140 = 2 or 12), so that the train reacts immediately to speed changes.
possible to the one defined in CV #141, independent of the speed when entering the stop section.
This method is especially suitable in connection with automated stops in front of a red signal with the help
of the ZIMO signal controlled speed influence or the asymmetrical DCC-signal (see above). CV #140 is “Distance controlled stopping“, when activated, is exclusively applied to decelerations leading to a full stop. Reductions in
set for this purpose to 1 or 11 (see below for details). speed or acceleration events are not affected by this (still handled by CV #4 etc.).
Although of lesser practical value, the distance controlled stopping can also be activated directly by the cab
or computer when the speed is set to 0 (by programming CV #140 with appropriate values of 2, 3, 12 or
13). The traveled distance is constantly being recalculated in order to get as close as possible to the desired
stop point. The deceleration rate within distance controlled stopping is always applied exponentially, that is
the deceleration rate is high in the top speed range followed by gentle braking until the train comes to a full
stop; which is not controlled by CV #122! The application of CV #121 for exponential acceleration however
remains unchanged.
 Decoder MX620, MX62, MX63, MX64, MX64D, MX64P Page 23

Automated uncoupling procedure; Shunting and half-speed functions:

also see “connecting an electric coupler” in chapter 7: By defining the different Configuration Variables (#3, 4, 121, 122, 123), a prototypical acceleration and de-
celeration behavior is achieved that often makes shunting very difficult.
MX62, MX63, MX64 from SW-Version 25. With the help of CV #124, a shunting key can be defined (either the dedicated MAN key within a ZIMO sys-
MX620, MX64D, MX64P with first SW version. tem or the keys F4 or F3) with which the acceleration and deceleration rates may be reduced or eliminated
all together.
As described in chapter 7, the control of an electric coupler (System Krois) is defined by CV’s #127, 128
CV #124 may also be used to define either F7 or F3 as low gear key. With this function turned on, the throt-
etc. (function output effects) and CV #115 (timing).
tle is used for half the decoder’s full speed range, which is just like shifting down into low gear.
With the help of CV #116 the decoder can be programmed so that the uncoupling loco automatically moves
Example: The F7 key should act as low gear and the F4 key should reduce the momentum down to ¼. Ac-
away from the adjoining coupler without moving the speed regulator (which is sometimes inconvenient be-
cording to the CV table, the bits in CV #124 are to be set as follows: Bit 0 = 0, Bit 1 = 1, Bit 2 = 1 and Bit 3
cause the uncoupler key needs to be pressed at the same time).
= 1. The sum of the individual bit values (0+2+4+8 = 14) is entered as a decimal value.
The tens digit in CV #116 defines how long (0.1 to 5 sec) the loco should move away from the adjoining
coupler, the ones digit defines how fast (internal speed step 4 to 36) it should move away, see CV table.
The momentum used during this acceleration/deceleration event is governed as usual by the relevant CV’s
(#3, #4 etc.). The hundreds digit of CV #116 causes the loco to automatically push against the adjoining “On-the-fly” - programming (a.k.a. on-the-main):
coupler before the uncoupling process starts in order to relieve coupler tension (otherwise the couplers
can’t open). Configuration variables can also be changed on the main track as well as on the programming track, with-
out interfering with other trains operating on the layout.
Other hints: All CV’s, with the exception of address CV’s, can be modified on the main. Please note though that the veri-
- The procedure is activated if the tens digit in CV #166 is other than 0! fication and read-out of CV values will not be possible until the bidirectional communication is implemented
(in the course of 2006 with SW updates for the ZIMO command stations “model 2000” and MX1EC as well
- The procedure (acceleration) takes place at the moment the coupler is activated, although only if the loco as decoders).
is at rest at the time of coupler activation (speed regulator in 0 position). If no bidirectional communication is available, “on-the-fly” programming should primarily be used for CV’s
- When the procedure is activated (with the tens digit of CV #116), the coupler remains open during the de- where a change is immediately visible (e.g. Vstart, Vmax, signal controlled speed influence settings, etc).
fined time in CV #115 (not just for the duration the function key is pressed); it is therefore sufficient to press Don’t use it to program the 28 speed steps in the speed table for example, which is preferably done at the
the function key just briefly to start and execute the whole uncoupler procedure (the function key used for programming track (where programming can be confirmed through acknowledgments).
the uncoupler function should of course be set as momentary key). Consult the ZIMO cab instruction manual for on-the-fly programming steps!
- If the uncoupler key is pressed again during the uncoupling and disengagement process, the process is
stopped. This allows to correct directional errors but also to activate the coupler for testing purposes without
starting the disengagement process.
- If the speed is changed during an automated uncoupling procedure, the process is also stopped.
- The driving direction during coupler detachment is always according to the cab setting; directional settings
in the “Effects” definition for uncoupling (Bits 0 and 1 of CV #127, CV #128 etc.) will not be applied.

Programming examples . . .

to follow later !
 Page 24 Decoder MX620, MX62, MX63, MX64, MX64D, MX64V

The configuration variables CV #33 to #46 refer to the function keys (F..) of the cab; the single bits to the
5. “Function mapping“ function outputs (FO..) of the loco decoder. The function keys are matched to the function outputs by setting
the appropriate bits (indicated in the table below with ). Multiple assignments are permissible.
as per NMRA Standard; and ZIMO - Extensions
„Mapping“ according to NMRA standards with default assignment shown as :

The allocation of function outputs

Additional function outputs Function outputs;
(“function mapping”):

NMRA Function
Number key
Usually available on large- The number of available outputs depends

CV
Depending on decoder type, ZIMO decoders have between 4 and 14 function outputs (FO ..). The loads on ZIMO scale decoders only, but shown on the decoder type. Always available are
cabs here for the sake of complete- the outputs “Front light” and “Rear light”.
connected to these outputs, such as headlights, smoke generator etc. are switched on and off with the func-
tion keys (F..) of the cab. ness.
Which key (F..) controls which function output (FO..) can be specified by a series of Configuration Vari- FA12 FA11 FA10 FA9 FA8 FA7 FA6 FA5 FA4 FA3 FA2 FA1 Front Rear
ables. light light

The configuration variables #33 to #46 form the NMRA function mapping according to their rules and regu- F0 #33 1 (L) fw 7 6 5 4 3 2 1 0
lations, see table to the right.
F0 #34 1 (L) re 7 6 5 4 3 2 1 0
A slightly modified function mapping that still conforms to the NMRA standard is used in the MX620 making 4 3 2 1 0
F1 #35 2 7 6 5
use of the fact that the MX620 has a maximum of 6 function outputs (headlights, FO1, FO2 and with the
SUSI interface deactivated additionally the logic level outputs FO3 and FO4), see table on next page! F2 #36 3 7 6 5 4 3 2 1 0
In any case, the NMRA function mapping restricts the free allocation of function outputs and only the head- F3 #37 4 7 6 5 4 3 2 1 0
light function is intended for directional control F4 #38 5 7 6 5 4 3 1 0
Therefore: F5 #39 6 7 6 5 4 3 2 1 0
Extended flexibility and more directional controlled functions are offered by ZIMO through configu- F6 #40 7 7 6 5 4 3 2 1 0
ration variable #61: F7 #41 8 7 6 5 4 3 2 1 0
MX62, MX63, MX64: F8 #42 ( -) 9 7 6 5 4 3 2 1 0
A number of ZIMO special function allocations CV #61 = 1 … 6 allow among others directional taillights or F9 #43 -1 7 6 5 4 3 2 1 0
the special lighting for Swiss electric and diesel engines. See next page! F10 #44 -2 7 6 5 4 3 2 1 0
(Only) MX620: F11 #45 -3 7 6 5 4 3 2 1 0
With a special programming procedure CV #61 = 98 a procedure is started with which each func- F12 #46 -4 7 6 5 4 3 2 1 0
tion/direction command can be assigned to specific function outputs (e.g. F.. – forward/reverse). A future
addition is planned that allows the definition of an automated turn-off feature, which turns designated func- The above table shows the default settings; that is, the function key numbers correspond to the same num-
tion outputs off after the loco comes to a stop. bered outputs. Therefore the following values were written to the configuration variables:
See next page! CV # 33 = 1; CV # 34 = 2; CV # 35 = 4; CV # 36 = 8; CV # 37 = 2; CV # 38 = 4; and so on.

An alternative method for directional functions: EXAMPLE of changing CV’s for individual assignments ( ):
The directional bits (0,1) in CV #125 to 132 (special effects) allow a directional function to be split into two F2 # 36 3 7 6 5 4 3 2 1 0
direction specific functions, if at the same time bits 2 – 7 are set to “0”. F3 # 37 4 7 6 5 4 3 2 1 0
Example: In order to control both function output 1 and 2 with F1 and direction, proceed as follows: Set CV F4 # 38 5 7 6 5 4 3 2 1 0
#35 to “12” (bit 2 and 3 in CV #35), CV #127 to “1” and CV #128 to “2” - thus output 1 is turned on in for- EXAMPLE above: The output #5 (FO5) should be switched in addition to output #3 (FO3) with the F2 key
ward direction only and output 2 in reverse. Special effect codes in bit 2 - 7 all remain at 0. (ZIMO #3 key). Outputs #7 (FO7) and #8 (FO8) should be switched (not additionally but instead) with the
F3 and F4 keys, which results in the above configuration ( ).
The new values to be entered are as follows: CV36=40; #37=32; #38=64.
 Decoder MX620, MX62, MX63, MX64 Page 25

Alternative „function mapping“ without “left shift”, for MX63 and MX64: CV # 61 = ... overrides the NMRA mapping and assigns the outputs to fixed function keys with the ex-
CV #61 = 97 overrides the higher CV’s “left shift” (from CV #37) of the NMRA function mapping (see previ- ception of F1 whose assignment remains flexible with CV #35.
ous page), which allows to map higher function keys with lower function outputs (e.g.It is not possible with A specialty of the “ZIMO special assignments” is the directional bit, which is available for function out-
NMRA function mapping to map F4 to FO1 but it is possible this way). puts.
Headlight
Therefore: FA6 FA5 FA4 FA3 FA2 FA1 Fwd Rev ZIMO – special function assignments for MX62, MX63, MX64
F0 #33 1 (L) fwd 7 7 6 5 4 3 2 1 0 NOT for MX620 (see next page)! with CV #61 = 3 or 4
F0 #34 1 (L) rev 6 7 6 5 4 3 2 1 0
5 Number key

Func

CV
on ZIMO
F1 #35 2 7 7 6 5 4 3 2 1 0 cabs FA5 FA4 FA3 FA2 FA1 Front Rear
F2 #36 3 6 7 6 5 4 3 2 1 0 light light

F3 #37 4 5 7 6 5 4 3 2 1 0 F0 forward 7
7 1
F4 #38 5 7 6 5 4 3 2 1 0 F0 reverse 6
6 5
and so on and so on F1 #35 2 5 4 3 2 1 0
F1 per CV #35 !F17
F2 3 6
Modified NMRA function mapping for the MX620; F3 forward 4 Typical application for F3:
(the MX620 always uses the function mapping in this manner but it is not possible with the MX63/MX64) F3 reverse directional taillights !
F4 5 5
Because the miniature decoder MX620 has a maximum of 6 function outputs (headlights, FO1, FO2 and
with the SUSI interface deactivated additionally the logic level outputs FO3 and FO4), the “left over” bits of This line valid for CV #61 = 3
the NMRA conforming registers from #37 are moved “to the front” and allow the lower numbered outputs F7 8
(e.g. headlights) to be reached with higher numbered function keys (F3 to F12), which would be impossible Direction’s Bit This line valid for CV #61 = 4
with the NMRA function mapping.
Therefore: NMRA standard (dark grey fields) with “turned over” bits“ (light gray): CV #61 = 3 or 4 Typical application: for directional taillights.
NOTE: for an alternative method, use “Effects”, see CV table!
MX620 function outputs
NMRA Function

ZIMO – special function assignments for MX62, MX63, MX64

CV

Number key NOT for MX620 (see next page)! with CV #61 = 5 or 6
on ZIMO cabs FO3 and FO4 are only available
as function outputs if CV # 124, Bit 7 = 1,
otherwise SUSI ! Number key

Func

CV
on ZIMO
cabs FA5 FA4 FA3 FA2 FA1 Front Rear
FA4 FA3 FA2 FA1 Front Rear
light light
light light

F0 #33 1 (L) fwd 7 4 3 2 1 0 F0 forward 1 7

5
Swiss locos: headlights except
F0 #34 1 (L) rev 6 5 4 3 2 1 0 F0 reverse
left front!6
5 F0 fwd. & F3 off CV #61 = 6: Swiss locos: the left
F1 #35 2 7 5 4 3 2 1 0
front white light!
F2 #36 3 6 5 4 3 2 1 0 F0 rev. & F3 off
6
F3 #37 4 5 2 1 0 7 6 5 F1 #35 2 F1 flexible per CV #35!5 5 4 3 2 1 0
7 7
F4 #38 5 6 2 1 0 7 6 5
Swiss locos: F3 -
F5 #39 6 5 2 1 0 7 6 5 F3 forward 4 directional taillights!5
F6 #40 7 7 2 1 0 7 6 5 F3 reverse CV #61 = 5: F4 – directional
cab illumination!
F7 #41 8 6 7 6 5 4 3 2 F4 forward
5 F4 reverse 5
F8 #42 ( -) 9 7 6 5 4 3 2
4 4
F9 #43 -1 3 7 6 5 4 3 2
3
F10 #44 -2 2 7 6 5 4 3 2 Direction’s Bit
2
7
F11 #45 -3 7 6 5 4 3 2 CV #61 = 5 typical application: directional taillights and cab light.
6
F12 #46 -4 5 7 6 5 4 3 2 CV #61 = 6 typical application: Swiss electric and diesel engines.
 Page 26 Decoder MX620, MX62, MX63, MX64

For a better understanding, the function keys or, more accurately, the function-direction-combinations are listed
ZIMO – Special function mapping: here in the sequence in which they are defined:
Function mapping procedure with CV #61 = 98: 1. F0 forward
MX620, MX64D, MX64P only! 2. F0 reverse
3. F1 forward
This procedure allows free allocation of function outputs to function keys (on the cab) that is not possible by
4. F1 reverse
setting fixed values in configuration variables.
5. F2 forward
To carry out this procedure requires a bit more time and attention from the user. 6. F2 reverse
* Preparation: The loco must be on the main track (not on the programming track); the whole procedure is 7. F3 forward
performed with operations mode programming. Set the loco direction to “forward”, all functions off. 8. F3 reverse
9. F4 forward
* CV #61 = 98 Writing value “98” to CV #61 (in operations mode) starts the actual allocation 10. F4 reverse
procedure. 11. F5 forward
The decoder is now in a special programming mode, which will not end until the whole programming 12. F5 reverse
procedure is completed or the loco is lifted from the track for a few seconds. 13. F6 forward
* The decoder is now ready to accept the first function output allocation, starting with function output F0 14. F6 reverse
in forward direction. 15. F7 forward
16. F7 reverse
The function outputs (as many as desired) to be assigned to F0 in forward direction, are now actuated 17. F8 forward
with the corresponding function keys (i.e. FLf, FLr, F1…F12). 18. F8 reverse
Because only one function key (F0) is available for FLf and FLr (headlights), it is necessary to press 19. F9 forward
F0 repeatedly to select the desired configuration (which alternately actuates the front and rear head- 20. F9 reverse
lights). 21. F10 forward
The assignment must be confirmed by pressing the direction’s key. 22. F10 reverse
23. F11 forward
* The decoder is now ready to accept the next output assignment for F0 but now for “reverse“. 24. F11 reverse
Continue as above! 25. F12 forward
Again, once a selection is made press the direction’s key to apply. 26. F12 reverse
* Continue in the same fashion for all function keys (28 function-direction-combinations)!
* After the last function key (F12 “reverse”) has been assigned, the function outputs FLf and FLr (both
headlights) are turned on to indicate the end of this programming procedure.
Confirm again by actuating the direction key. In the fall of 2007 an easy to work with tool that replaces the “CV #61 = 98” procedure will become avail-
* After confirmation, the finished allocations are automatically activated and CV #61 is set to “99“. able as part of the “ZIMO Service Tool “ ZST, where the desired functions can be “mapped“ into a table
and the procedure described above will be carried out automatically!
Deactivation:
CV # 61 = 0 ... 97 (any value except 98 and 99) deactivates the function assignment
and again activates the function mapping according to CV #33 to #46 or
CV #61, if a value between 1and 7 is entered. The assignment defined
during this procedure though remains stored in the decoder.
Reactivating already stored data:
CV # 61 = 99 Reactivates the defined output allocations.

NOTES:
The special effects (US-lighting, uncoupler, soft-start etc) can also be assigned using above procedure. CV’s #125, 126 etc.
always refer to actual outputs!
It is possible to store and selectively re-activate several function output allocations with the help of the “CV-set” feature!
 Decoder MX620, MX62, MX63, MX64 Page 27

6. “Bi-directional communication” 7. Installation and wiring

The future oriented technology that has been installed (hardware) on all ZIMO decoders since 2004, can be General information:
activated since March 2007 with SW version 28 in the MX62, MX63 MX64 and MX64H, with SW version 4 in
all MX620 and with the first SW version in the MX64D and MX64P decoder. There has to be enough free space inside the engine so that the decoder can freely be mounted. Pay par-
ticular attention that no pressure is exerted on the decoder when the loco housing is being reinstalled and
“Bidirectional” means that the information transfer within the DCC protocol is not only flowing towards the
the wires can’t get caught by movable parts.
decoder but also in the opposite direction; that is not just driving, function and switch commands are being
sent to decoders but also messages such as acknowledgements and status information are being received All direct connections that are present in the original wiring configuration between the power pick-ups
from decoders. (wheels and wipers) and the motor must be isolated; otherwise the decoder end stage may get damaged at
power-up.
The NMRA RP’s 9.3.1 and 9.3.2 create a uniform platform for bidirectional communication. Note: Bidirec-
tional communication according to NMRA is identical to the method used by Lenz Elektronik, known as The same goes for the headlights and other additional accessories, which must be completely isolated.
“Railcom” (Trademark of Lenz Elektronik).
The functionality is based on short cut-outs (max. 500 micro seconds) introduced to the otherwise continu- Do noise suppression components on a locomotive motor have
ously sent DCC signal by the command station. These cut-outs provide the opportunity and enough time for
the decoders to send a few bytes of data to locally mounted detectors. a negative affect on motor regulation?

Yes, sometimes . . . (in modern engines more so than on older ones)

With the help of = bidirectional communication, it will Explanation: Motors of model railroad locomotives are often equipped with choke coils and capacitors, which
are supposed to suppress or filter out noise (poor TV reception etc.) caused by the sparks arcing across the
motor’s brushes.
be possible that
Such components impair the motor regulation. Compared to others, ZIMO decoder manage quite well, that
the decoder can acknowledge received commands
is there is hardly a difference in performance with or without those components in place. However, in recent
this increases operational reliability and the bandwidth of the DCC system because already acknowledged commands don’t years larger choke coils are being installed in many locomotives than was the case earlier – and these can
need to be sent repeatedly; noticeably compromise drivability.
“global” information from decoders is sent to the command station The potentially “harmful” choke coils are often recognizable by their shape of a resistor with color bands (in
e.g. “real” train speed, motor load, routing and position codes, “fuel reserves”, current CV values on demand from decoders contrast to a wire wound ferrite bar). That doesn’t mean though that these choke coils have a negative effect
to command station or more precisely, to a global detector in the command station; in all cases.
decoder addresses are recognized by “local” detectors Fleischmann locomotives with “Round motors” often have extremely bad filter components; especially
those capacitors that connect between the motor connections and the frame. These are often hard to see
the actual loco positions are determined by local detectors connected to individual track sections (integrated
and to get at.
in future MX9 track section modules). This however has been possible with ZIMO’s own loco number recog-
nition for over a decade without bidirectional communication but only with ZIMO components. Indications of an actual negative effect of such components, besides a general unsatisfactory motor control
(jerking…), are:
Starting in 2007, RailCom will be further developed over the coming years and will bring new applications,
which of course require new software updates in decoders and other equipment. In the first phase - March - weak control compensation: as a test, set the decoder to low frequency – CV #9 = 200 – and check to see
2007, SW version 28 – ZIMO decoders will be able to send their own loco address from an isolated section whether the control compensation becomes stronger. If that’s the case, the choke coils are most likely to
of track (with a so called broadcast method, very fast, although only for one loco inside that section) with blame for the weak compensation in the high frequency range.
some decoder data such as actual speed, load and decoder temperature. - if a difference in compensation is noticeable between 20 and 40 kHz (select in CV #112, Bit 5); if the com-
On the system side, a third party product is available from the beginning – the address display LRC120, pensation (further) diminishes at 40 kHz, it is very possible that the choke coils are the cause.
which is a “local” RaiCom detector displaying the loco address of one track section. In the course of 2007, Remedy: Bypass or remove choke coils! Capacitors are less likely to interfere with motor regulations but
the MX31ZL will become available with an integrated “global” RailCom detector and finally “global” RailCom cannot be ruled out (see “Round motor” above).
detectors for the installation into ZIMO command stations MX1EC, MX1, MX1HS as well as MX31 cabs.
The RailCom function is activated with CV #29, Bit 3 (see chapter 3, CV list and CV #28)
„RailCom“ is a trademark of Lenz Elektronik GmbH.
Locomotives with 6 or 8 pin NMRA interface . . .
. . . are easy to retrofit with the MX...R, MX...F, MX...N (e.g. MX63R or MX64F) etc. They come with the
appropriate 8 (R) or 6 (F, N) pin connector. There is usually enough room provided in such locos, at least for
the smaller MX62 or MX63 decoders. By removing the dummy plug from the loco, all damaging connections
mentioned above should be interrupted and the decoder can be plugged in instead. This is unfortunately not
always true with some loco manufacturers. It is advisable to use an ohmmeter to confirm this before plug-
ging in a decoder.
 Page 28 Decoder MX620, MX62, MX63, MX64

Headlights Cab light bulb

Hard-wiring a locomotive… Rear Front
Blue
Yellow
2 Diodes
… with a DC motor and headlights: White
1N4007

This probably represents the most common wiring diagram for HO installations. All other diagrams that
follow are modified or extended versions of this one.
Red
Right rail Headlights DC Motor
Black
Orange
Left rail Rear Front Connecting function outputs FO1 and FO2:
blue Right
Yellow The MX620 has solder pads available for function outputs FO1 and FO2, other types have wires and can be
White M connected in the same fashion as the headlight bulbs. The outputs can be used for different things such as
Gray
cab lighting, smoke generator or uncouplers (also see relevant section below). For mapping the outputs to
Left function keys, see chapter 5; the function outputs FO1 and FO2 are by default mapped with function keys F1
Lights connected as shown on this diagram are direction controlled and switched on/off by the F0 key (1 on and F2.
Zimo cab). The lights can also be controlled independently with F0 and F1 for example (1 and 2 on Zimo

Cab light
Red

E.g.
cab), using function mapping CV’s #33, 34, 35. Black
Right rail Headlights
Left rail Rear Front
PLEASE NOTE: Body mounted light bulbs that are hard to insulate can be left as is. The body acts as the
blue
power supply to the bulb. The blue lead from the decoder must not be connected to the bulbs in such cir- Yellow
cumstances. The white and yellow leads are connected to the other side of the bulbs. The brightness of the White

headlights will be reduced in such an application Solder pad FO1

. . . with an AC engine:
Two additional 1N4007 diodes (or equivalent) are required as shown in the diagram below. They can be ob-
tained at your local electronic store or from ZIMO. Using logic level outputs:
ZIMO decoders also have so called logic level outputs in addition to the normal function outputs, to which
AC-m otor current consuming devices may not be connected directly. Use a M4000A amplifier board or similar transis-
Red tor switching device, when connecting logic level outputs with a load.
Right rail Headlights Rotor
Black Field coils
Left rail Rear Front In addition to the 4 normal outputs, the MX620 offers the two connections “SUSI-CLOCK” and SUSI-DATA”
Orange
Blue as logic level outputs FO3 and FO4 by setting CV #124 Bit 7 = 1 (if SUSI is not required); see CV #124 in
Yellow
the CV table and function mapping in chapter 5!
White M
Gray This is similar with MX63 and MX64 decoders but for logic level outputs FO5 and FO6, alternative to “SUSI-
2 Diodes 1N4007
CLOCK” and SUSI-DATA”.
An amplifier module M4000Z is connected with its brown lead with the relevant logic level output solder
Most locomotives that run with an AC motor get the power supplied by a third rail, which doesn’t change pad of the decoder.
anything as far as the motor hook-up is concerned. The above schematic is therefore valid for AC locomo- e.g.
tives running on two or three rail track. Sm oke generator,
B row n B lue (+ )
Note: many locomotive manufacturers supply field magnets that can be used in place of the motor’s field M4000Z G re e n (-) uncoupler etc.
coil. Using a field magnet turns an AC motor into a DC motor, which is connected as such (see above) and C o n n e ct to S U S I-C L OC K o r S U S I-D ATA so ld e r
can also utilize the decoders BEMF feature (BEMF does not work with AC motors). p a d s o f th e M X 6 2 0 , co n ve rt th e o u tp u ts to fu n ctio n 2 x bla c k
o u tp u ts w ith C V # 1 2 4 , B it 7 .
To tra ck

Cab lighting controlled with F0 key:

This is no longer of much use today; it is a remainder from a time when decoders only had two function out- Connecting DIETZ sound modules / virtual cam sensor
puts, which were used for the headlights and the cab light. Cab lights connected this way can be switched
with the F0 key but in contrast to the headlights were non-directional. See Dietz instruction manual (MX65/MX66 decoder instructions may also be helpful). For sound boards with
SUSI, see below!
This is however a general schematic that can be used in cases where something is to be operated by sev-
eral different function outputs, but the same outputs used independent of each other. There are 2 diodes re- For a good acoustic impression of steam engines, it is important that the chuffs are synchronized to wheel
quired (type 1N4007 or equivalent) available from ZIMO or any electronic parts supply store. revolutions. Therefore a cam sensor should be installed and connected to the sound module (reed switch,
optical or hall-effect sensor), which sends exactly 2 or 4 pulses to the module (depending on loco type).
 Decoder MX620, MX62, MX63, MX64 Page 29

Sound modules can usually generate their own chuff rate based on speed information (e.g. coming from the MX620F, MX63F, MX64F with NMRA 6-pin interface (NEM 651):
SUSI interface of a decoder), if no cam sensor can be installed or installation proves too difficult. The result
is often poor with a chuff rate that is too fast at low speeds (the SUSI protocol is not precise enough in that The “F” designated decoders’ come with a 6-pin plug mounted to the end of its wires, which fits into the
socket of a DCC ready loco. Lvor (weiss)
respect).
Lrück (gelb)
To improve this situation, ZIMO decoders come with a “virtual cam sensor”. The MX620 uses the function The brightness of the headlight is reduced since the blue wire (common Motor (orange)
output FO2 for this, which is converted for the “virtual cam sensor” function with the help of CV #133 and supply) is not part of this interface. The light bulbs get their power direct Motor (grau)
connected with the cam sensor input of the sound module (e.g. Dietz, reed switch input); naturally in addition from the power pick up. Pluspol (blau)
to SUSI or other connections. Schiene (schwarz)
The blue wire is still available at the decoder and can be connected to Schiene (rot)
The virtual cam sensor is of course not capable of synchronizing chuff rates to wheel positions but rather to the bulb if more light is needed. The power supply from the track to the
wheel speed, which makes little difference to the viewer. bulb needs to be cut first, of course!
The chuff rate of the “virtual cam sensor” can be defined per wheel revolution with CV #133; consult CV ta-
ble in chapter 3.

MX620N plugs directly into the 6-pin interface (NEM 651):

The “SUSI” interface: Many N, HOe, HOm as well as some HO engines have this socket installed with the required minimum
The SUSI interface developed by Dietz is an NMRA standard and defines the connection between sound space of 14 x 9 mm to accept the decoder.
modules and loco decoders, provided the sound module is also equipped with such an interface.
Due to space restrictions on small decoder, the SUSI interface composed of 4 conductors (2 data, ground ATTENTION: Plug the decoder into the socket with the pins down and the micro processor visible!
and power) is not built as a plug-in connector but instead uses 4 solder pads. The larger MX64H and
MX64V do come with SUSI connectors! 6-pin
Speed and load information (e.g. to change sound intensity when going uphill, downhill, start up etc.), as well Loco socket
Decoder MX620N
as sound-configuration variables (CV’s #890…) are sent by SUSI from the decoder to the sound module.
Loco board
Accessing SUSI CV’s: These CV’s are in the 890 range, according to the standard (NMRA DCC Draft RP),
which is not accessible with many DCC systems (ZIMO cabs MX2 and MX21 were also limited to 255 - until
mid 2004). For this reason, ZIMO decoders allow access to these CV’s with numbers in the 190’s!

Connecting an electric uncoupler (System “Krois”):

In order to prevent damage to the delicate core of an uncoupler from continuous power, appropriate adjust-
ments can be made with special CV’s for one or several function outputs. MX64D, MX64DV – Decoders with 21-pin interface:
First, write the value “48” to the CV that is assigned to the same output the uncoupler is connected to (e.g.
CV #127 for output #1, CV #128 for output #2 etc.) These decoders have a 21-pin female plug on the circuit board (no wires), which allows the decoder to be
plugged directly in to the 21-pin male receptacle of locomotives equipped with such interfaces. There are ac-
Next define the uncoupler activation time limit in CV #115 (see CV-table): tually 22 pins present but one of those (#11, top right) pins serves as a key to prevent wrong installations.
With the “Krois uncouplers”, it is recommended to use a value of “60”, “70” or “80” for CV #115; this
means that the pull-in voltage (full track voltage) is limited to 2, 3 or 4 seconds. A reduced “hold” voltage is The meaning of the indi-
not required for Krois, that’s why the ones digit is left at 0. Other uncouplers may need a reduced hold volt- vidual pins is usually not
important to the user. The Left row
age though, like the ones from ROCO for example.
pins marked “n.c” are not
Regarding the “automated coupler detachment”, see CV #116, chapter 4. used, they are reserved
for special applications
(Hall-effect sensors).
MX620R, MX63R, MX64R with NMRA 8-pin interface (NEM 652):
The MX64D can be
The “R” designated decoders’ come with an 8-pin plug mounted to the Lfront (white)
plugged-in two ways;
end of its wires, which fits in to the socket of a DCC ready loco. Remove Lrear (yellow)
Motor (gray)
the board below the con-
the dummy connector from the socket and plug the decoder in its place, nector is perforated, so
Motor (orange)
that’s all. that depending on the locomotive, the decoder can be plugged in from the top or bottom end. The key pin
Power (blue)
All the necessary connections to power, motor and headlights are es- Rail (black) 11 prevents a wrong installation by not allowing the decoder to be pushed all the way down. This
tablished with this interface. Other outputs have to be hard wired. Rail (red) and/or the decoder not sitting level on the board indicate a wrong installment!
 Page 30 Decoder MX620, MX62, MX63, MX64

Connection and control of an external energy source (capacitor) for

MX64D plugged into TRIX loco board uninterrupted driving on dead track sections:
MX64D plugged in right side up, Pins of the loco board
penetrate through the decoder board into the socket. With the help of an electrolytic capacitor or a battery the
- driving performance on dirty track sections (or wheels) can be improved
Loco board - flickering of lights is reduced
- and stalling of trains, especially when crawling, can be eliminated

The energy storage increases with the capacity of a condenser and from 100uF (Microfarad) onwards an ef-
MX64D plugged into BRAWA loco board fect will be noticed. 1000uF to 10’000uF are recommended if the necessary space is available. The required
MX64D is plugged in upside down !
voltage strength of the capacitor is given by the track voltage; 25V is suitable for all cases. Smaller 16V ca-
pacitors should only be used if track voltage will never be higher than that.
The capacitor is connected between ground (available on all ZIMO decoders as solder pad) and power (blue
Loco board wire or SUSI-POWER) of the decoder. Note polarity!
Choke coil 100 uH (microHenry) is required,
if ZIMO loco number ID is employed.
M X6 2 0 C onne c tion s ide

220 uF
25 V
-
+
Motor (orange)
Motor (gray)
Rail (red)
Rail (black)
The MX64DV is largely identical to the MX64D but with the added hardware on the extended circuit board, it Lfwd (white)
is capabable of supplying low voltage for bulbs or other equipment. For more information go to the section Lrev (yellow)
„MX64V1, MX64V5, MX64DV“ in this chapter of the manual! Power (blue)

M X 6 3 B o tt om v ie w

220 uF
- GROUND
(= showing solder pads !)

25 V +
Power

MX64 B ot to m v ie w
(= showing solder pads !)

Alternatively, this wire can also be connected with

the blue wire on the other side of the decoder!

-
SUSI
Power

220 uF +
25 V

GROUND
When using a 220uF or possibly a 470uF capacitor no other parts are really required for “simple” loco con-
trol; although installing a choke coil (100 mH / 100 mA, available from ZIMO) is recommended in the posi-
tive wire to guarantee that the decoder can be updated with the update module MXDECUP and that the
ZIMO loco number identification works.
If larger capacitors are used, which is actually a good idea, extra circuitry is required. The condenser is re-
charged through the 100 ohm resistor. This is to prevent a shut down of the command station during start-
up. If a large number of loco’s so equipped are on the layout the command station could interpret the current
flow to these capacitors as a short circuit. The diode (e.g. 1N4007) is required to bypass the resistor when
power is needed by the decoder.
 Decoder MX620, MX62, MX63, MX64 Page 31

NOTE: If signal stops by “asymmetrical DCC signal” (= Lenz ABC, implemented in ZIMO decoders early MX64V1, MX64V5, MX64DV - The special MX64 or MX64D design with
2005) is employed, the resistor-diode combination is necessary in any case (even when using small capaci-
tors) to ensure that the decoder can detect the asymmetry of the signal!
built-in low voltage supply
MX620 Conn ection side
1N 4007
Motor (orange) The MX64V1 contains an efficient 1.2V voltage regulator, which can be directly connected to low voltage
+ Motor (gray)
bulbs. This facilitates the decoder installation considerably especially in high quality brass models (which are
Min. 1000 uF
3K3
Rail (red)

-
25 V Rail (black) often equipped with such bulbs), because it eliminates the installation of an external voltage regulator (that
100 E, 1/4 W Lfwd (white)
Lrev (yellow) often requires some sort of heat dissipation).
Choke coil 100 uH Power (blue) The MX64V5 is a variant of the MX64V1 with a 5V regulator, mostly for installations in large scale such as
O-scale or higher (LGB), where 5V bulbs are often found.
M X63 B o tto m view Otherwise, the MX64V1 and MX64V5 are identical to the MX64H (1.8A, SUSI connector etc.)!
Choke coil 100 uH (= showing solder pads !)

Min. 1000 uF
- 100 E, 1/4 W NOTE: The above voltage supply is to be preferred over the dimming function in CV #60. The dimming func-
3 K3

tion works with PWM at full voltage that can damage bulbs. An even higher risk is taken during programming
25 V
+ on the programming track with the accompanying acknowledgment pulses.
1N 4007

The MX64DV comes on a longer circuit board than the MX64D and contains a 1.5 voltage regulator for low
voltage light bulbs. As delivered, the low voltage is available at the common positive pins 16 and 17; meant
MX64 Bottom view for locomotives that use low voltage bulbs only. The usual full track voltage is not available.
(= showing solder pads !)

Alternatively, this wire can also be connected with

the blue wire on the other side of the decoder! Full track voltage will be provided on pin 16 after rearranging a jumper wire. This is practical for applications
SUSI that require full track voltage as well as low voltage.
1N 4007 Power
+
ab 1000 uF
3K 3

25 V
- 100 E, 1/4 W

Choke coil 100 uH GROUND

The purpose of the resistor 3K3 shown in the drawing above (not required in all cases) is:
even though a large condenser supplies the motor and lights for just a few tenths of a second (1000uF) or a
few seconds (e.g. 4700uF) the remaining power, although at a voltage level below what is required by the 16 16
17 17
motor and lights, is sufficient power to keep the decoders memory alive for quite some time (several min-
utes). This is sometimes a rather undesired effect. For example: If a running loco is taken from the track and
the speed then set to zero, the loco would briefly run at the previous speed when it is set back on the track
after about a minute. Using the above-mentioned resistor would erase the memory after just a few seconds.
ZIMO offers a collection of components under the term (order number) SPEIKOMP that are required for
building a do-it-yourself energy module to be connected to ZIMO decoders MX620, MX63 and MX64. The
set contains a diode, resistors, choke coil and a few capacitors (you can and should use larger capacitors if
space is available). A complete energy module (MXSPEIK) with above circuitry will be available from ZIMO
in the course of 2006!

Smart stop management on “dead” track sections

In cases where power to the decoder is interrupted due to dirty rails, wheels or insulated frogs, the decoder
automatically keeps the engine going even though a currently active brake application should bring the train
to a stop. Only when power to the decoder is restored is the loco allowed to stop, with subsequent testing to
ensure power to the decoder is still available after the engine stopped (if not, the engine is moved again a
short distance).
 Page 32 Decoder MX620, MX62, MX63, MX64

8. The MX64D in a loco with a C-Sinus motor 9. ZIMO decoders and competitor systems
The MX64D can be switched to a matching output configuration required for the control of the C-Sinus
boards found in many Märklin and Trix locomotives with C-Sinus motors, provided the locomotive comes All Zimo decoders comply with NMRA standards and recommended practices and can be used on layouts
with a 21-pin interface. The decoder also supplies the necessary 5V the C-Sinus board needs to operate with other brands of NMRA compliant systems.
(which „normal“ decoders are not capable of!). What most systems of other manufacturers have in common, in contrast to ZIMO systems, is that track
The MX64D is plugged into the pins of the loco board with the top side of the decoder pointing up, whereby power is not stabilized or only partly stabilized and often relatively weak (in regards to voltage but also am-
the pins are being pushed through the decoder board in order to make contact with the decoder socket. The perage). This can lead to uneven speeds and/or limited top speed because Zimo decoders are of course
position is given by the loco board and is also keyed by the missing pin 11 (on the loco board) and missing programmed by default to operate on stabilized and regulated track power of up to 24V from a Zimo com-
hole in the same location on the decoder board. mand station.
The picture below shows a sample layout; the loco board my however vary from case to case. It is recommended if required to:
- change CV #57 (reference voltage) from ”0” (where regulation is based on track voltage) to a fixed voltage.
L o c o b o a r d w ith 2 1 - p in in te r fa c e a n d M X 6 4 D p lu g g e d in F la t r ib b o n c a b le to C - S in u s - M o to r For example: “140” for a DCC system with a typical track voltage of 16 - 18V. In this case 14V will be used
as reference, which leaves a certain safety margin during voltage drops.
Note that the MX62 always uses a fixed voltage.

. . . with Lenz “DIGITAL plus” from software version 2.0

This system uses 28 speed steps beginning with version 2.0 and 128 steps with version 3.0 and up. It also
programs in direct mode according to NMRA DCC standards and is therefore fully compatible with Zimo de-
coders.
All Zimo decoders are set to 28 speed steps by default. Make sure the system is also set to 28 steps for the
The switch-over to the C-Sinus control takes place with CV #112, Bit 0 = 1. Because the acknowledgement decoder address in question. Incompatibility will be the result if the speed steps between decoder and sys-
method doesn’t work in most cases during service mode programming when the decoder communicates tem do not agree with each other; which is most often noticed by non working headlights. It would only make
with the C-Sinus board, Bit 1 of CV #112 must also be set in order to utilize the special „internal high fre- sense to switch the system from 14 steps to 28 or 128 speed steps rather then setting the decoder back to
quency shorts“ as acknowledgement pulses. That means for most cases 14 steps, which would result in unnecessary poor drivability.
CV #112 = 3 All configuration variables are accessible; see the manual for the cab in question. The address is located in
A MX64D equipped C-Sinus locomotive can be operated in the NMRA-DCC-data format as well as the the registry’s position #1.
MOTOROLA protocol but not in analog mode (DC)!
No motor regulation, known as BEMF, takes place when the decoder operates in the C-Sinus mode, since The configuration variables #49 to #54 will have no effect, since the signal controlled speed influence is only
the motor tries to keep the target speed precisely in all situations. The relevant configuration variables, supported by a Zimo system.
among them CV #9, #56 and #58, are without effect!

. . . with ROCO Lokmouse-2

Although the Lokmaus-2 allows CV programming, its display is limited to two digits only and therefore limits
the number of CV’s and their values to 99.
Zimo decoders offer a special pseudo-programming feature with CV #7 (that normally stores the software
version number) to allow unrestricted programming. It is called pseudo-programming because the perma-
nently stored value in CV #7 cannot be overwritten but rather holds a temporary value that allows the Lok-
mouse2 to be used for expanded programming capabilities (see CV table); the engine must not be running
during the programming procedure!
Example:
To enter a value of 160 (which is not possible with a Lokmouse-2 because value is >99) to CV #5 (max.
speed) proceed as follows:
First program CV #7 to 1, followed immediately by setting CV #5 to 60. No power interruptions between
those steps are allowed.
 Decoder MX620, MX62, MX63, MX64 Page 33

Explanation: The value 1 in CV #7 actually 01 (tens digit=0 and ones digit=1) causes the decoder to add 100
to the CV value that will be entered in the next programming step. Therefore, a value of 60 entered to CV #5 10. Special - CV - Sets
with the Lokmouse2 is stored as 160!
Example:
To program CV #122 (exponential deceleration), for example, with a value of 25 do the following: This feature allows easy programming of a group of predefined values to the decoder’s appropriate configu-
ration variables. Such “CV sets” may be part of the decoder software at delivery (as listed and described in
Again, go to CV #7 and enter a value of 10, then go to CV #22 and enter a value of 25.
the table below) or defined by the user.
Explanation: CV #7 = 10. The 1 in the tens digit causes the decoder to add 100 to the CV address in the fol-
Typical applications are: Railroad specific lighting, motor specific data for perfect slow speed behavior, pro-
lowing programming step. As a result, CV #122 will be programmed instead of CV #22!
totypical loco specific acceleration, easy switching between a passenger and goods train or single loco ver-
sus consist.
. . . with DIGITRAX Chief Programming of such CV-sets (either supplied or self defined) is accomplished by a pseudo-programming
No problems expected with this system! sequence of CV #8 (CV #8 contains “145”, the manufacturer code for ZIMO and cannot really be overwritten,
therefore the term pseudo-programming).
The Digitrax system usually operates at 28 or 128 speed steps. If for some reason the headlights don’t work,
confirm that indeed the system and the decoder are set to the same number of speed steps and if neces-
sary, change the speed steps at your cab to 28 or 128 steps. The first practical application that was introduced with software 11 is:
There have been some malfunctions in the past during system boot up. For example: locomotives would not CV #8 = 47. This special CV-set was introduced as original equipment for a series of Norwegian locomo-
start unless the power to the decoder was interrupted briefly (by tipping the locomotive off one rail). It is not tives and defines the lighting as well as the speed and acceleration characteristics of those engines.
quite clear whether the causes have ever been fully identified and eliminated; it may also depend on the
“Norwegian Default values”:
command station model (year of manufacture) and the software version in the Digitrax command station.
CV #13=207, CV #35=12, CV #61=35, CV #121=5, CV #122=13, CV #124 = 23. Beginning with software
version 12 also included are: CV #3=4, CV #4=2.
. . . with UHLENBROCK Intellibox
Operation, addressing and programming are possible without limitations! More such sets and the possibilities for self-definition are planned for a future software version.
Normally the speed step mode of the Intellibox and the ZIMO decoder are a match (by default in both cases
28 or 128 speed steps, which is fine either way). If the headlights don’t work even though the decoder is CV #8 = 8 as hard reset is of course still available as before. This will reset all configuration variables to de-
wired properly, make sure the decoder address is not set to 14 speed steps – this would need to be cor- fault values according to the CV-table in chapter 3.
rected on the cab to 28 or 128 speed steps.
On the other hand, the hard reset procedure initiated by programming the decoder to address 0 with a ZIMO
cab (MX2, MX21, MX31,…) will reset the decoder to the last defined special CV set. The Norwegian loco, in
the above example, will remain just that.
 Page 34 Decoder MX620, MX62, MX63, MX64

11. Converting binary to decimal 12. MX620 with Märklin MOTOROLA systems
At present (August 2007): MOTOROLA only for MX620, MX64D and MX64DV (not for MX63/MX64) !
If, according to the CV table, a CV calls for setting individual bits (which is the case with CV #29, 112 and Using the MX620 in MOTOROLA mode only makes sense if the system used is not capable of operating in
124, for example) proceed as follows: the DCC format. DCC is substantially more powerful and should to be the preferred protocol with a multi-
Each bit has a specific value: protocol system.
Bit 0 = 1 The MOTOROLA data format is recognized automatically by the decoder.
Bit 1 = 2 Addressing and CV programming is possible with a Märklin system, albeit very tedious (because this sys-
Bit 2 = 4 tem doesn’t provide much help):
Bit 3 = 8
Bit 4 = 16
Bit 5 = 32 TEMPORARY INSTRUCTIONS:
Bit 6 = 64 Programming CV's with Märklin 6021 central unit:
Bit 7 = 128
The decimal values of all bits of a CV that are supposed to be set are added up (Bit... = 1 in the CV- table).
All other bits (Bit....= 0) are ignored. Note that bits are numbered from right to left. Start the programming mode by:
Example: 1. selecting the address of the engine to be programmed
Bit 0, 2, 4 and 5 are supposed to be set (Bit...=1); but not the others 1, 3, 6 and 7 (Bit…=0). 2. press the "STOP" key at the central unit and wait a few seconds
This results in a bit-set of 00110101and a decimal value of: 3. Crank the speed regulator past the left stop and hold (direction switch)
4. press the "START" key
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 5. release the speed regulator

0 0 1 1 0 1 0 1
The front headlight of the engine should now be flashing once per second indicating that the decoder is in
the programming mode.
0 + 0 + 32 + 16 + 0 + 4 + 0 + 1 = 53 (decimal value)
You can now choose between two programming modes:
1. Short mode: programming is limited to CV’s 1 – 79 and a value range from 0 – 79
The calculation in reverse: 2. Long mode: the values to be used in each case are split and transmitted in two steps (CV 1-799, value
range 0-255)
A trial and error method is used to determine individual bits from a decimal figure: start with the largest The short mode is always active after entering the programming mode.
value. If a number is larger or equal to 128 then Bit 7 = 1. If the remaining number is larger or equal to 64
To change to the long mode write 80 to CV #80 (enter address 80 and change direction twice to change to
then Bit 6 = 1 and so on.
the long mode).
Example:
The decimal figure of 53 is neither larger or equal to 128, nor larger/equal to 64 but is larger than 32. There-
fore Bit 7 = 0, Bit 6 = 0 but Bit 5 = 1; the rest of 21 (53 - 32 = 21) is larger than 16 (Bit 4 = 1), the remaining 5 Short mode:
(21 - 16 = 5) is not larger than 8 but is larger than 4 (Bit 3 = 0, Bit 2 = 1), and finally 1 (5 - 4 = 1) is not lar- Enter the CV to be programmed in the central unit as an address and briefly operate the direction switch.
ger/equal to 2 but is equal to 1 (Bit 1 = 0, Bit 0 = 1).
The headlight now quickly flashes twice.
Now enter the desired value to the selected CV and again operate the direction switch briefly (enter 80 for a
value of 0).
The headlight flashes once indicating that you can program the next CV or end the programming by turning
power to the track off.

Long mode:
Remember to set address 80 to a value of 0!
Enter the hundreds and tens digit in the central unit of the CV you want to program (for example: for CV 123
enter 12) and operate the direction switch.
The headlight now quickly flashes twice.
 Decoder MX620, MX62, MX63, MX64 Page 35

Now enter the ones digit of the same CV (for example: for CV 123 enter 03) and operate the direction switch
again. 13. Software Update with MXDECUP
The headlight briefly flashes 3 times.
Enter the hundreds and tens digit in the central unit of the value you want to program and operate the direc-
tion switch. All MX62, MX620, MX63, MX64, MX64H, MX69, MX690, MX82 as well as all future ZIMO decoders can be
The headlight briefly flashes 4 times. updated with new firmware by the end user with the help of the update module MXDECUP or MXDECUPU
(with USB converter).
Now enter the ones digit of the value and operate the direction switch again.
Again, the headlight flashes once indicating that you can program the next CV or end the programming by New software versions can be downloaded at no charge from ZIMO’s web site: www.zimo.at (under “UP-
turning power to the track off. DATE”) and add new features, improvements and corrections to the decoder.
The ZIMO Service Tool (ZST from version 1.4) is also required for the update procedure. This software can
also be downloaded at no charge from www.zimo.at.
Note that the decoder update page of the current ZST program is still in German. Until a new ZST version is
released, a program extension can be downloaded with this page translated to English. Please download
both, the original ZST mentioned above and the ZST extension from www.zimo.at
Once both are installed on your PC, the extension can be started as a stand-alone program for decoder up-
dates.

RS-232 – SUBD-9-socket Connect to “update track”, connect to

control-LED’s power supply
behind socket

The update module comes with a power supply, an RS-232 connecting cable and a USB converter (in case
of MXDECUPU). Power supplies (12V DC, 300mA minimum, unregulated), serial cable with two 9-pin sub-D
connectors (1:1) and commercially available USB converters (USB to serial) can also be acquired locally if
necessary.

Implementation and operation:

A section of track is used as “update track” and connected to the 2-pin screw terminal of the MXDECUP.
Set the engine with the decoder that is to be updated on the track. The decoder can of course be connected
with its red and black wires directly to the track connector of the module instead.

In contrast to the CV-programming procedure, the update procedure with the corresponding acknowledg-
ment does not depend on the load connected to the decoder (such loads are neither necessary nor hinder-
ing).

Note ...
 Page 36 Decoder MX620, MX62, MX63, MX64

Electrical loads in the loco that are not connected to the decoder may potentially present a problem (since
the decoder cannot turn the load off), because of the 150mA power limit of the MXDECUP. The update
process may fail in such cases and the relevant loads must first be removed or remove the decoder from the
locomotive.
Make sure the choke coil recommended in chapter 17 is actually installed, if external buffer circuits (ca-
pacitors) are used to maintain power to the decoder on dirty track sections. Acknowledgments from the de-
coder to the MXDECUP are otherwise not possible.
Although there is a “blind update option” available in ZST that operates without acknowledgements, its use is
not really recommended.

First, plug-in the power supply at the MXDECUP. The green LED, visible in the connector recess, should
now be lit. Next, connect the MXDECUP with the computer using either the RS-232 cable or the RS-232
cable with USB converter. The green LED now turns off again (both LED’s are dark).

The actual update process is started and controlled with the “ZIMO Service Tool” (ZST, always use the lat-
est version. For English applications use the ZST extension, see explanation on previous page):

We can’t offer a detailed description here regarding the update process; since ZST will often be modified
and expanded (this software performs a number of other tasks within the ZIMO system). In any case, there
is a button on the original ZST main page named: “start with MXDECUP online”. English speaking users
should start the ZST extension, which opens the COM PORT selection page. All further steps, such as se-
lecting the right COM port, the update software file (one file contains all current software versions for all
ZIMO decoders), starting, control and terminating the update process are self-explanatory on screen or can
be obtained from the help file.

The two LED’s at the MXDECUP are flickering very rapidly

during the update process (red and green). This indicates
that data packets are sent to and acknowledgments
received from the decoder. The LED’s remain dark once
the update process is finished.

If for any reason the update is unsuccessful (indicated by

ZST), another update can be started after a waiting period
of 5 seconds!