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" MX32 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.


1.21.0001 or 1.21.0010 - DO NOT INSTALL, you will be sorry.


1.21.0015 - fixed version of the above - 2017.07.26


Note: this release is bundled with 1.21.0010 MX10 version. This version is very buggy and the MX32 locks up often. Don't switch screens a lot, don't try any of the US outline locomotive pictures, and if you pick a different speedo, the US speedo with the white background and black letters is fairly stable.

If you are running your system all the time, or have people over to run, DON'T use this version, go back to 1.20.0150 ...


Sample of locked up screen:

screen fail


When it works looks nice, but every time I used the US F7 picture it crashed, so my F units look like this:

no us locos


Release notes:


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

- Operating languages ​​German and English

- Function symbols, soft symbols, system symbols, tachodesigns

- CV designations, functional descriptions in German and English

After the actual update can be added additionally:

- Vehicle pictures

- object database, vehicles; Equipment; interlocking; CV lists and sets

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

- Vehicle images, which already existed before the update,

- Object database, vehicles

- List of accessories and WEI panels.

Corrections in the correction version 01.21.0010 (compared to the main version 01.21.0001)

    Cooperation with WinDigipet Stellwerksoftware (basic functions tested),
Compatibility of the MX32 with the "old" basic devices MX1 restored,
Optimization of the GUI override when calling new addresses,
the update sequence is arbitrary;
(lastly, however, the new software always had to be loaded first in MX32, then only in MX10)
Presentation of the Roco Z21 Busy modules in ZUB LIST,
Improvement of the "E + 2" procedure (tacho parameters),
Completion of (lost, already existing soft symbols in the WEI panel),
MX9 Functions: Hard reset, ALA outputs, avoiding the display of old addresses.

new graphics and improved usability for stop, collective stop, OFF;
East-west direction with decoders.

Improvements and error corrections in version 01.21.0001 (MX10 and MX32 / FU) compared to 1.20.0150:

    Cooperation with iTrain software (tested: driving mode, Op Mode Programming, accessory switching.
English operating language integrated.
Data backup / reload to / from USB stick (so far finished for object database vehicles, vehicle images).
New reprocessing of the representations in operating mode FAHR of name, address, picture, speedometer.
Maintaining the selected display mode when changing between vehicles (with F-, U-key, rolling on the rudder, etc.)
Corrections in operating condition ZUB LIST, optical and functional.
Transfer / transfer of tractions between the scooters: Marking of the vehicles with FT (..) if traction is integrated in another scooter (but not actively controlled), with FS (..) if this traction in other scooter is in traction and straight actively controlled (one of the locomotives of this traction in the foreground). When a traction is taken (U-key in the traction or external control window), all the addresses involved are transferred to the new control console.
Adjustment of the RailCom speedometer display, accessible by E + 2; the desired km / h value to be displayed is entered there and the CV # 136 (RailCom factor) responsible for the decoder is automatically reprogrammed.
The start-up time of the MX32 (power-on) is shortened to approx. 15 sec, while a part of the charging processes from the control center are done in the background, while device is already operable .-> Disadvantage: It takes up all accessories in E + 3 after the ramp (therefore the configuration or switching of this can take place only after a few minutes).
GUI transfer (image, speedometer, function symbols) now faster, because partially done in the background (i.e., locomotive can already be controlled before function symbols are fully displayed).
Editing, upgrading, updating the OP PROG special screens for ZIMO decoders, accessible via E + F + U + SoftKey M (Menu): ZIMO Swiss mapping, NMRA Mapping, ZIMO input mapping, volume, loops, sample number - settings for function sounds.
MX8, MX9 modules: Addressing also from the zero state (new modules are delivered with the address 800 (MX8) or 900 (MX9)); in ZUB LIST via SoftKey III

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"
Smoothing the RailCom tacho dough to prevent unsightly jumps,
Tractions (optimization) - automatic reduction of the control influence so that locomotives do not "work together"
(suitable - i.e., ZIMO decoders should receive corresponding messages)
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 multiple CVs at the same time
multi-key signals, most important types, especially: Q-decoders - Define and switch signals in the WEI panel,
various corrections


MX10 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.


"Standard" MX10 updating procedure:

The new versions have all the files in a *.zsb file, but normally this is compressed into a zip file.

The standard states that you just leave the zip file in the root directory. This does not always work. If you get the: " "Zimo keine file gefunden" message (Zimo file not found), then extract the *.zsb file and copy it to the memory stick

1.19.0200 - 2016.05.20

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.


1.20.0001 - 2016.10.28

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.

 1.20.0100 - 2016.12.23

 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.

1.20.0150 - 2017.02.24

Fixed a few things, worked ok, but still missing some features I wanted. My significant update is that I finally got my throttle that always had problems and was "repaired" once, has been replaced, and now it updates and works fine... since it is brand new!


1.21.0001 - this was released sometime in July 2017 I believe

Luckily I did not install this version, just by chance, since apparently it had some problems.


1.21.0015 - fixed version of the above - 2017.07.26

Installed. The zip file would not be recognized, had to do extract the ZSB file

Insert stick, it prompts to update... select to update... updated, but it says remove power and stick and wait a minute. After applying power again, certain menu items were just a couple of letters liie "se", a whole bunch of them. Do the update again and it came back in english and the menus looked right.

Note: the 1.21.0015 zip file has 1.21.0015 for the MX32, but the MX10 version is 1.21.0012




Weather Underground PWS KCACARLS78