Zimo firmware notes


I intend this to be a place where the latest release notes on the firmware, and deviations, observations, and comments are incorporated in RED. This way I can be sure to explore te new features, check the problems fixed, and validate any bugs.


Warning! firmware updates!

MX32 updates:

My first updates were to version 15 or something, and the translators at Zimo seem to have confused the meaning of A and E.... normally A is execute, and E is our "escape" but during firmware updates, A says cancel, and E says accept...  so be careful with older updates.

The new versions have all the files in a *.zsb file, but normally this is compressed into a zip file. Extract the *.zsb file and copy it to the memory stick

"Standard" updating procedure:

  • Have cab plugged in and on (booted up), screen does not matter
  • Plug in the memory stick, a window will pop up with some info on the stick.
  • Press A for file list (stick content), E to quit (ESCape) (escaping will reboot the MX32)
  • The file list will show individual components, it is recommended to do the "Automatic" update, not all the separate stuff
  • Normally the first item listed is the "Automatic" or full update. Sometimes a second item is listed as "symbols and icons", these are included in the "full" update and you do not need to load them separately. (There are certain cases where this is useful but not usually).
  • (I have not found out how to mark multiple items, there is a menu selection to load all marked items)
  • A is accept as always ...  it will check the file a bit, tell you the version it found and warn you not to pull the power or usb stick,

The full update should prompt you to remove the stick, the function/symbols will not, so maybe it is meant to do those first and then the full/automatic update.



There is a single .zsb file in the zip file.

Just the zip file in the root directory of the memory stick, do not extract it.

I had trouble reverting to this version from a newer version. I noticed that the "full/automatic" update did not work on one unit, screens would come up missing 50% of the characters.

Re-installing the full update did nothing, but "succeeded", in that I got the "remove the USB stick" message (in German) at the end of the update.

I decided to do the "symbol/font" update, which is SUPPOSED to be included in the full update. On the "failing" cab, this terminated back at the initial "select the update" screen... which I thought was strange... doing it again eventually yielded the "remove the USB stick swinehund!" message in German, and after that terminated the cab was properly updated.

So what is learned is that the "full" update is not always "full" irrespective of successful termination messages, and if you do any update and do NOT get the successful termination (remove the USB stick), then you keep doing it.


Oh my God! Unbelievable problems, wireless will not boot at all, you can boot in wired mode and remove the cable, but response is sometimes ok, sometimes delayed by several seconds or does not happen at all, really not useable in wireless mode.

Worse, the arcane accessory decoder control is broken, it becomes impossible to enter subaddress "0" so decoder addresses 1, 5, 9, 13, etc. are IMPOSSIBLE to use. I could not run my trains at all, since I have all electric/pneumatic switch motors that cannot be locally overridden.



Some things fixed. Boots to wireless, wireless response better, but better than unuseable is not much of a positive statement. finally fixed enough that you can use it, still a number of bugs where the leds do not update on the throttle, slow response, screens do not update.


Trying now, as usual the Automatic update wiped out the fonts, so you have 2 issues, the first is that most of the characters are the dreaded "Tiny Font" and characters missing from a lot of screens. The issue is that without the proper fonts loaded, the system either defaults to the built in tiny font (80 characters per line) or you see nothing, because the font is missing. Of course the ACCEPT (A) and the ESCAPE (E) are missing from all screens, so you have to remember where they are...

New behavior: font install goes into infinite loop, USB led blinks, and install seems to go right, then most of the screen blanks and only "LOADING FONTS" shows, and finally that disappears. And you have 3 horizontal lines on the screen and the USB LED blinks. When this happens, your cab is hung... .unplug rom power and mess with the buttons, eventually it reboots. I don't know if it is a watchdog timeout or hitting the buttons. This does indeed suck.

MX10 updates:


All that is needed is the zip file in the root directory of the memory stick, do not extract it. There is a single .zsb file in the zip file

Make sure the MX10 is in normal operating mode, screen is blue. Insert the memory stick and then it will ask you to update all... press the rotary button, then it will check the file and then sit there until you hit the button again.

It will tell you the update is complete, and that pulling out the usb will restart the system, do so.

You normally have to set the language back to English.


Again, all that is needed is the zip file in the root directory of the memory stick, do not extract it. There is a single .zsb file in the zip file that is needed is the zip file


New with this update, it tells you to turn the unit off, take out the USB and wait 5 minutes.

After the update, I always have to set the language back to English, see above. I understand this is in the list to be done.






The new SW version 1.20.0100 (like all versions as of 1.18.0052) is available as a common container file for MX10 and MX32 / FU and can be used directly for all devices that already have a SW version as of 1.16.xx (Deliveries from April 2015 onwards). The update must be installed in all consoles and in the MX10 (therefore all devices (MX10, MX32, MX32FU) in a system must have the same software).
The update does NOT include the firmware for the MX32 Rev. 5 (first sold revision of the MX32).

>>> I installed it 2016.12.24

The system would not read the zip file, i.e. it found the file but it gave the error message: "Zimo keine file  gefunden: (Zimo file not found)

OK, extracted the single zsb file and just put that on the memory stick.

First time the MX10 said it was searching the zsb file, but sat there forever. Pulled it out, shut down the MX10, restarted it, and this time it found it. I picked what looked like the automatic update and it completed. This time it did tell me to turn off the system, pull out the memory stick and wait 1 minute.

The MX32FU's recognized the file right away, and based on my somewhat disastrous experience before, I installed the symbol/font file first... it completed and came back the the main menu and then I did the automatic update (which is the rest of the firmware), that completed fine.

No real testing yet, but no missing fonts or symbols, wireless response seemed to be what it used to be, and the switch controls did not flash like a bad LSD trip.



The container file contains all necessary update files for MX10 and MX32:

- software for the main processors of the devices

- Software for the radio processors of the devices
- in this update NOT: firmware for the XILINX gate arrays of the devices

- Operating languages German and English

- Function symbols, soft symbols, system symbols, tachodesigns

- CV designations and functional descriptions (EN)


After the actual update can be added additionally:

- Vehicle pictures

- database: vehicles; Accessories; Switchboard; CV lists and sets

- fonts (see previous software version entries)


Not affected by the update process and will remain in MX10 or MX32:

- Vehicle images, which already existed before the update,

- object database,

- List of accessories and WEI panels.



Improvements and error corrections in MX10 and MX32 versus version 1.20.0001:

     Correction and acceleration "Send GUI to MX10" and "Load from MX10".
     Correction of the automatic GUI transfer / transfer
     Small changes in the assignment of the function symbols ("ADR FUSY"),
     Better representation of the binary input (bit-by-bit) of CVs in SERV PROG and OP PROG,
     Radio mode: faster call up of the WEI panel and the "ZUB LIST",
>>> this was totally broken in the previous release, so something has been fixed, the subaddress 0 is not available in the display, but it shows ...  and that seems to work for the zero, this was also broken in the last release
     East-West direction in the "display mode" (for decoders without east-west function): by shift-key (leading)
     Ri key (when the shift is held) is assigned east-west arrow (3-cycle, east-west-dark),
     Note: The decoder software version with the East-West feature is not yet released, so the mapping is currently only virtual.
     MX9 addressing also from the basic state (address 900)



NOTE on the NEXT SW versions - The soon to be implemented not yet implemented features are:

    Decoder software update and sound loading with the MX10 from the USB stick.
Optimization of external cycle, erasure functions;
Automatic removal from external cycle, if address more than 10 operating hours,
With driving stage "zero" and all functions "off",
Railcom-Tacho-adjustment now by long-touch on speedometer (short touch is change of representation),
RailCom-Tacho is to be smoothed to prevent jumps,
UES Adaptive (overcurrent detection due to current jumps)
Tractions - Indicate the number of vehicles in Trakion in the traction number, ie "T .. (..)",
Trains (Second stage of development) - Takeover / surrender
Tractions (optimization) - automatic reduction of the control influence so that locomotives do not "work together"
Traction (optimization) - speed and direction adjustment,
Tractions - Considering the delayed start-up due to a sound start in a vehicle,
INC / DEC for selectable CVs (for example, volume) on scroll wheel, with simultaneous switching capability for several CVs at the same time
MX8 in the WEI panel,
Q decoder - Define and switch signals in the WEI panel,
Multi-fingered signals, most important types,
Various corrections in the operating condition WEI (gray, black fields, ..),
Startup of additional MX10 menu items,
MX10 - "Voltage & current adjustment": Start-up "UES-Adaptive", the automatic adaptation of the switch-off threshold to the current power consumption (eg 2 A over this) are),
Creation of a GUI backup memory in the MX10, where the current GUI or all GUIs from the database object database can be stored at the request of the MX32 (in the menu) and in which the data can not be destroyed, even with software modifications. In this area there is NO change possibility and only very secure delete possibilities. Any number of vehicles can be stored, even under the same address, as long as anything in the GUI differs.
Backup of the object and image databases to USB stick,
Help files in MX32


Functions that have not yet been implemented (focus on MX10):

  • An automatic balancing of interconnected rail outputs to form an extra strong traction circuit (up to 20A) is NOT available. (A manual adjustment is required at the moment, but it is not advisable to interconnect, since the reaction is uncertain in the event of a short circuit!)
    >>>> Jeeze over a year and we still cannot realize one of the big selling points??
  • Loconet / S88 / Sniffer input not yet in operation
  • Track signals: Motorola data format, mfx not yet in operation
  • ABAs can not be used for operations (because RailManager is not yet operational with MX10),
    >>> wonder what this means, I saw a reference to this on the MX10 menu
  • Scheduled booster operation of the MX10 is not yet operational. However, NMRA Control Bus for booster booster is set up and can be used. An MX1 can also be used as a booster, but this leads to incidents when an overcurrent occurs on the MX1 - therefore this constellation is still not advisable at this time.
  • There is no "frequency hopping" for the radio channel. The radio channel can be set manually in the MX10 menu under "MX10 Config". There may be "radio collisions" with foreign products, e.g. Funkmaus come out.
  • "BaseCab" functions (driving, CV programming, ...) not operational; Alternatively, the speed, direction and functions can be controlled under the menu item "ObjectDB Vehicles".
  • Decoder software update and sound loading are not yet possible with the MX10 (The MXULFA is available as before).
    >>>>> what?? when is this finally going to be available? Big selling point of the system
  • Some of the monitoring and diagnostic functions are not yet fully functional.


Functions that have not yet been implemented (focus on MX32):

  • Help screens are only partial and not up-to-date.
    >>>> why is this so? I heard it was because the help screens are graphics not just plain text.
  • Traction operation is currently only in the "first development stage" (not yet a transfer / transfer between train consoles, nor a permant storage in the base unit, if the console,where traction resides, is no longer connected).
  • No simplified adjustment of the speedometer display (currently editing the curve in "ADR TACHO").
  • Backup of the MX32 (locomotive database, pictures, ...) to USB-stick (before update or general backup and transfer not yet possible),
  • The WEI panel does not contain any multi-element signals.
  • Track diagrams not yet available (but only WEI panels and accessories list).
  • SERV PROG and OP PROG: handling of CV sets only partly realized (use not recommended),
  • OP PROG: Special configuration procedures for ZIMO decoders (Function Mapping, Swiss Mapping, Sound Config, ...) only partly correct.
  • In the object database, not all functions are fully available, e.g. Filter, ZACK, ...
  • Deletion of individual locomotive images not yet possible (only all at the same time in PultConf -> ClearData),
    >>> this is really nuts, shows the internal database is not properly designed or implemented yet
  • The local time can only be stored by the MX32 until the next time it is switched off. The MX10 start date and time information is retrieved from the MX10. If the time is to be set, this must be done via the MX10 menu under "MX10 Config". Thus all connected MX32 synonymous run.
    >>> need to test, but the MX32 should ALWAYS receive the time and data from the MX10


Known SOFTWARE BUGs. Which lead to malfunctions or operating difficulties of MX10 and / or MX32 :.

    High error rate for CV and address reading at the programming track (SERV PROG)
>>> what? basic CV programming has a high failure rate?
High error rate for "Identify" (the collective display of various decoder characteristics such as type, software version, serial number) after entering the main track (OP PROG, PoM).
Stand-alone corrections for single stop and STOP windows, e.g. The single stop window should be dimmed immediately when the controller is activated, but this does not happen.
LED indication of the MAN function ("MN") is lost when changing between vehicles (F and U in the reef or scrolling) and recall of the respective address; However, the MAN function itself remains.
In the collective stop condition (with the stop window shown, ie the bar display), functions and direction should still be switchable (only the speed is set to zero); Which works only for the functions, but not for the direction of travel.
(Eg for locomotive name): in the operating mode "digits" (1, 2, 3, ....) the digit "0" can not be written because the 0 key only makes blanks; Switch to character mode (abc) for entering the digit "0" necessary.
Minor inconsistencies in the assignment of function symbols (FUSY, E + 5): the LEDs should show the functional states (not D / M), the toolbar should remain rigid when switching to "M" .
Minor disagreements when programming in OP PROG and SERV PROG: When switching to "Fu switching" (formerly "Test mode"), the function panel should be displayed with symbols and INC / DEC should work with the rocker switch as in driving mode.
Sporadically (rather rarely) the LED driver in the MX32 terminates its function, i. The LEDs are no longer switched on and off (although the function itself functions in the display).
>>> need to watch for this
Sporadically (rather rarely) a function LED flashes to indicate that the transmission to the control center would not have been successful, although this is not the case.
>>> need to watch for this
Unclear situation regarding readings at the console of programs like ESTWGJ.
Here are NOT all bugs listed!
>>> so where the heck is a complete bug list? Come on, a $3,200 system and incomplete software and no overall bug list?

Weather Underground PWS KCACARLS78