Zimo MX10 & MX32 updating & firmware notes

Overview:

There is a lot of information on this page, so look around.

Firmware bugs and issues:

I used to list all bugs and tests here, but I have moved this to a groups.io forum/group.

The main Zimo group with years of history is: https://groups.io/g/ZIMO-DCC (the original Yahoo groups moved intact to groups.io)

I have created a group for just firmware bugs: https://groups.io/g/Zimo

Messages are here: https://groups.io/g/Zimo/messages

In this group there is a database on firmware and bugs: https://groups.io/g/Zimo/database

There will be a table for each firmware release, and there is a table for tests I use.

While some of my comments might be construed as negative, remember that this is basically the most expensive DCC system made, and as such, is subject to a higher standard of quality and performance than other, lesser brands.

My MX10/MX32 running bug/want list

1. consisting - just keep adding features, and consistency. Thank you for putting the consists in the MX10 memory!
2. Not all locos in consist recall show, depending on which direction you scroll
3. Not implemented yet: restore of ACC and Panels and loco objects

Current firmware versions:

As of August 20, 2022:  1.29.1000

MX10 updates - how to, and tips:

I usually update the MX10 first, then the throttles

My first updates were to version 15 or something, and the translators at that time 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 (but why would you be using them?).

"Standard" MX10 firmware updating procedure:

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 make sure it is in the root of the flash drive.

Note: After the crazy 1.25.0001/0100/0101 update with flashing icons, erratic running, etc, I have been informed that you should delete some databases in the MX10 both before and AFTER updating. I deleted the vehicles and accessory databases, as well as the trains one (which I do not think is implemented). I recommend you DON'T do this unless you have issues.

Plug the usb memory stick into the MX10. It should read the stick and tell you there is an update.
Recently it has said: "System Upd&Data" and the triangle cursor is on that line.

If all goes well, then normally pressing the main rotary knob will advance you through the update procedure. Normally you will have to press it again.

At completion, it says remove USB and power, wait 1 minute, do so.

At the end of the update, normally it says "remove USB, and remove power". I prefer to remove power, THEN remove the memory stick, and then reapply power. Remember that memory sticks CAN get corrupted by removing when under power and the operating system is accessing it.

To check:

Use the menu: MX10 Config >> Version Info

Often the MX10 update changes settings like language, and voltage and current, be sure to check these after updating. Even after 4 years it still happens every so often!!

Notes:

the memory stick you use must be FAT32 and 4096 byte cluster size. I don't know what the upper limit on the flash memory is itself. It has been reported that 1 GB sticks do not work, and larger sticks won't (easily) format FAT32, so stick to 16 GB. I use 4 GB ones, same as the Zimo memory stick provided.

If your update scrambles the screen, you can rotate the knob "X" clicks, and then push in, this is for the "blind" update when the screen is garbled.

Originally, the system could accept the zip file, some time before version 17. If you opened the zip file, there were a ton of files inside, so that was probably the reason the system used to read the zip file directly. The "Zimo keine file gefunden" message means "Zimo file not found"

MX32 updates:

Note: you will see references on the Zimo site to " NICHT für MX32 Rev. 5" starting with firmware 1.21.xxxx. From my buddy Dan Pierce, it appears that MX32 serial numbers below 150 are revision 5 (or less).

Note the memory stick you use must be FAT32 and 4096 byte cluster size. I don't know what the upper limit on the flash memory is itself. It has been reported that 1 GB sticks do not work, and larger sticks won't (easily) format FAT32, so stick to 16 GB. I use 4 GB ones, same as the Zimo memory stick provided.

Big note:

Read ALL of this section first, since it is EASY to wipe out certain components in the MX32, and spend hours re-loading

"standard" MX32 firmware updating procedure:

• The firmware is normally on the Zimo site in zipped form.
• Unzip the .zsb file to the root of the memory stick
• Have cab plugged in to power 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 to continue, E to quit (ESCape) (escaping will reboot the MX32)
• Now you get a menu: (Which varies)
  
  • Save Data
  • upload from backup
  • export to USB stick
  • Auto update MX32
  • Sys. & function symbols
  • Instruments (speedo etc.)
  • Loco pics.
  • Database: Locos
  • Database: Access.
  • DB: dwitch board
  • DB: CV lists + sets
  • Decoder upd. coll. file
  • ZIMO tasks
  • Load all marked elements
  • Load fonts
  • Debug Data

Note: some items will be grayed out, they are either not implemented, or are gray because the required file is not on the memory stick, like a backup file to upload, or fonts.

The actual update:

• Normally you preform the "Auto update MX32" which is the full firmware update.
• Make sure the red cursor is on this line before you hit the A (execute) button
• Another warning, and hit A again to start the update process
• After completion, the unit will prompt you to remove the memory stick

Notes:

• Sometimes a second item is listed as "symbols and icons", but unless the release specifically states that the fonts are in the release, DO NOT do this.

I have a "theory" that selecting the fonts option on a release that does not include fonts and the fonts are not on the memory stick, actually wipes any existing fonts out.

In any case, if you get the "tiny fonts" syndrome, update the fonts (see below)

Also, note well: the words "full" on the release filename have NOTHING to do with whether the fonts are included or not. I assume "full" refers to a complete firmware for the cpu, rf, and fpga sections.

MX32 fonts updates:

Many times your fonts go "bye bye" with no notice. From experience with 3 different MX10 systems, my theory is that you can do something (see above) to wipe out the existing fonts/symbols. Not all Zimo "full" updates contain the fonts/symbols (in fact very few). You can read this on the site where you download the firmware:

Full version for MX10 and MX32. This "container file" contains the previously split files of the previous versions. In the .zip folder, therefore, there is only the update file without the fonts, these can be taken over from the earlier software version entries (01.20.0001) and reloaded if necessary. Whereby the fonts have not changed since 01.20.0001, therefore with an update from 01.20.0001, 01.20.0150, 01.21.0001 or 01.22.0150 / 151 to the version 01.23.0001 NO extra reloading of fonts is necessary.

What this means is that these other "full" versions are lacking all the fonts.

If you have had your system long, this is the dreaded "tiny font" syndrome. All the things that were larger, are now tiny, or don't even show up, i.e. blank.

Note that you can be missing some of the system symbols, and certain "characters" can be in either the fonts or the symbols files.

The fonts files are on the Zimo site. At this time the latest "fonts only file" is the 1.20.0001.

• First you need extract the fonts from the zip file and put them on the memory stick.They are all .ZSC files
• insert the memory stick, and scroll down to the fonts option
• now you can select the fonts update with the TP key and then hit A (this loads all fonts)

MX32 Symbols

This is another issue that comes up frequently, where the symbols disappear. The symbol file is not normally included in the firmware update, just like the fonts. The symptom at first appears like the "tiny fonts" issue, but what is missing is characters and pictures, the TP and F^ characters on the screen are really symbols. Also, when you hit the "E" key, you should see 3 rows of boxes with pictures inside (the last row has one blank). After a recent update, one MX32 had the top row missing.

It's a bit harder to find the symbol file on the Zimo website. The latest one I have has symbols from 2014.The latest Symbol file is on the Zimo firmware page, look at version 1.15.1120

The updating procedure is like fonts, but you need the single .ZSC file and the individual symbols ( .BMP) all in the root directory, BUT you cannot see the "update symbols" menu item UNLESS you also have a main firmware file present on the memory stick also.

(as an aside, this is a bad situation Zimo could fix, i.e. detect the symbol ZSC file, and make the menu item appear ONLY if it exists, right now the menu item exists if there is a main firmware file IRRESPECTIVE of ANY symbols available)

• Unzip the symbol files to your memory stick (the .ZSC file and the multiple .BMP files)
• also put a MX32 firmware file on the memory stick
• Now select the "Sys & Function symbols" option ONLY
• Hit the A key

My updates take about 3:10, but wait it out, there are some cases where it can take over 5 minutes.

Note: this EXACTLY how people wipe out their symbol files during an update, since the menu item will show even if you have NO symbols, and it effectively can wipe the existing ones out.

MX32 Locomotive pictures

This update requires correctly named and formatted picture files, and a "script file" that names and loads the pictures. I have a separate page on this, click here

An example file is under the firmware page, version 1.15.1120

Installing: ensure you have the relevant image files for the loco(s) you wish to load

insert the usb stick, scroll to "Loco pics.", Press "A" to select.

Now, it will list the ZSC files it finds, along with a number which looks like the version number in your ZSC file and some more numbers, and they are overlapped (BUG!)

Now press "A" to select the file you want, and be sure to wait until the display comes back, it might take a few seconds.

You should get a list of every loco called out in the ZSC file, it's ID number and Upd or New... Upd means it is already in the MX32 under the same id

As it loads the file, if there is an error, the text in the screen will go red..

Other MX32 files:

I'm proceeding to look into these files, as of January 2019, you can often save and reload other files, but few of them work properly. Eventually you will be able to backup and restore many components of the database.

Problem with icons:

I don't know if this will be solved with the symbols file, or the fonts file, or the main firmware, but will report back which fixed it. A big question is why did this happen?

The "A" after the Continue is also missing. The "A" was restored with the fonts file.

My "Acceptance Test" for new releases

I'll be expanding this, but will try to use this test on each new release

1. locomotive select from A key
2. locomotive select from LoRcl
3. locomotive select from Object DB
4. copy loco from Object DB to local handset
5. test programming of switch decoder, i.e. paired mode
6. test that switch symbols animate properly and display properly
7. consisting, test for ability to create consist
8. test that loco in consist can be reversed
9. test that loco consist persists through power up down of system (same throttle)
10. test consist handoff keeps reversed locos

1.29.1000

1.29.0101, .0105, .0106 (through March 17, 2021)

all these were "corrections" to .0001 and many update problems reported, as of March 22, I am loathe to change over, a couple of my cohorts have tried with mixed success, the .0106 seems almost ok, but still some systems will not update.

1.29.0001 (December 23, 2020)

- not good, had a lot of problems.

1.28.0400 (October 23, 2020)

Last good one I am currently using, most things improved,

1.28.0005 (May 22 2020)

2312/5000
Compared to 01.27.xxxx there are again numerous improvements, extensions and bug fixes with 01.28.xxxx (.0005 is the latest correction version of 01.28). The latter relate to on consist addressing (with CVs # 17,18), MX8, MX9 programming, background reader, tachometer smoothing, east / west u. PoM situations.

Bigger points are:

The collaboration with the STP interlocking program (by Ewald Sperrer) has been corrected in important matters, together with the latest STP version; however, there is still a lot to do (e.g. STP does not yet use the ZIMO east / west direction control)
The necessary precautions have been taken in the MX10 for the new versions of the "ZIMO-CV-Setting" program ZCS (by Matthias Manhart).
The radio communication between MX10 / MX10EC and MX32FU has been improved; however, further steps will follow in this regard.

A typical, luxurious-looking ZIMO feature is the "Decoder Info" that can be displayed in the FAHR operating state (in the picture on the right in magenta below the address). It has been expanded and made controllable through new menu lines. The display of the driving voltage, measured by the (ZIMO) decoder at the current vehicle position, can provide very useful information on defects in the system wiring. The track section (of a StEin or MX9 module) on which a vehicle is currently located and the HLU speed limit that is valid there are clearly often very helpful information.

The distinction between whether a remote is operated on your own "home system" or not is that in the second case the object database of the control center should not be changed because a temporarily connected "non-home remote" brings another locomotive with it ", which has the same address as one that already exists in the headquarters.

Usually, a new remote automatically adjusts itself to the control center as the "home system", where it is connected for the first time. In CONFIG (for "This desk") there is the possibility to replace the "Home System" originally recorded in the remote with the currently connected one.
Tractions can now be "moved" to the system center; this makes the restriction that only 9 tractions (T1 ... T9) can exist per control panel ineffective.

1.28.0002 (May 18 2020)

1.28.0001 (May 2020)

There's a note not really clear on the Zimo site about backing up the loco image files.

I sacved eht objdb, picture database, acc list, panels, and config just to be sure

1.27.350 (December 2019)

Full content (with regard to storage in MX10) from SW version 1.27.300 BASIC TO DOUBLE AND MULTIPLE RATIATIONS in the ZIMO SYSTEM (A guide to creating tractions follows on the following pages.) - Double or multiple traction, or "traction" for short, means Link between two or more vehicles (= addresses). Such causes the other vehicles to be automatically controlled in the control of one of the participating vehicles (addresses), in terms of speed, direction of travel, MN and RG conditions, but not with regard to the functions. A traction in the ZIMO System "resides" (= is founded, edited and stored primarily) NOT in the digital central unit, but in a "control unit", ie a MX32 (henceforth also MX33 or ZIMO App), where the vehicles (addresses) are traction marked with "Tx" ("x" is a number 1 .. 9 among the traits residing in the device, eg "T5", both in the main window and in the recall memory "RüF", (if visible) and in the object database. However, the traction residing in the consoles are "mapped" in the base unit, ie in the central unit (= there is a copy) .Thus, traction continues even if the "residence unit" has been removed from the system (or the radio connection is aborted).

 A vehicle (an address) that is in a traction residing in a particular console is marked in other drivers with "FT" ("foreign traction"); this means that it can not be activated immediately, but only after a take-over procedure for the whole traction, which automatically includes all vehicles contained in it. This takeover procedure consists of the window "external traction" and confirmation of the U-key to confirm -Attigung the acquisition of traction, including all participating vehicles, so the complete traction resides in the "new" driving desk.

 After taking over a traction in a new remote this becomes the residence device; there (and only there) the traction can now be resolved or modified (ie vehicles added or taken away). - All operations such as applying tractions or deleting and modifying are simultaneously "mapped" in the base unit so that it can take its place in the absence of the resident device.

 update of MX10 and MX32 went smoothly, (although it would be nice for the MX10 to use English for prompts if English has been set.

1.27.0200 (September 23, 2019)

1.27.0110

Consisting broken again!

1.27.0001 (August 2, 2019)

Updating notes:

The MX10 update will indicate it sees the USB, press the knob, then it will come to another screen, and it will have a little carriage return arrow and update after that, press the knob again... now wait, it looks like it does not do anything for a bit, but be patient (Zimo this could be improved with better text and status indications)

MX32 update went smoothly, with adequate prompts.

Regression testing / bug testing:

Bug 1 appears fixed, was not able to reproduce

Bug 2 appears fixed, was unable to reproduce

Bug 3 appears fixed, was unable to reproduce, and it failed very often in 1.26

Bug 4 appears fixed, the "normal DCC numbering" seems to stay and never go away, pressing TP does not switch to the alternate screen (THANKS Zimo!!)

Bug 5 is NEW, not fixed clearly

Bug 6 is NEW, not fixed clearly

1.26.0001 (April 19, 2019)

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

    Software for the main processors of the devices
    Software for the radio processors of the devices
    Operating languages ​​German and English
    Function, turnout, system symbols, tacho designs
    CV designations, function designations

After the actual update can be additionally imported:
  Vehicle pictures, object database, vehicles; Equipment; interlocking; CV lists and sets

Not affected by the update process and get stuck in MX10 or MX32:
  Vehicle images, object database, vehicles, list of accessory addresses and WEI panels.

Data backup NEW:
With this software version 01.26.0001, an automatic data backup of the vehicle database is performed on the same USB stick before the software update.
ATTENTION: This feature will of course only work AFTER the first update of the new SW version, so the next update! Before doing this, you should back up manually one last time:
This happens after plugging in a USB stick (expediently a separate one, ie not the one with the container file) by selecting the menu item "Save data to USB stick" and subsequently selecting the data to be backed up. See operating performance MX32!

 Innovations & improvements in MX32 (compared to version 01.25.0001)

    The deletion of vehicle images can now be carried out with the aid of filters (as they are also used in the assignment).
    The distinction between "home system" and "radio system" is now correct: the "radio system" is only about the registration at the control center (channel, code), the "home system" and others. to the automatic reuse of the GUI (vehicle pictures, Fu symbols).
    CV programming via scroll wheel: if marking on value field, pressing the rocker button; this acts as a switch between line scrolling in the programming list (as before) and incrementing and decrementing the value.
    Automatic data backup of the vehicle database before the SW update to the same USB stick

ERROR CORRECTIONS (compared to version 01.25.0001)

    Traction operation (according to MX32 operating manual chapter 14). corrections
    After reading the address in the SERV PROG, GUI is now automatically adopted
    Fixed a crash after deleting the last address
    Various Flacker avoidances (during programming, database, StEin)
    StEin display in the lower screen: operations as in full display
    GUI bug fix on switch panel: LEDs and switch position are correctly displayed / displayed again)

Known SOFTWARE BUGs in MX10 (EC) and / or MX32 (also in this version 01.26.0001)

    Display communication point, RailCom logo, "Quality of Service" not yet according to the description
    Traction operation: assumption of an existing traction does not function properly if current owner's driver is not connected.

NOT yet implemented functions (main focus MX10 / MX10EC):

    Track signals: Motorola data format, mfx not yet in operation,
    Loconet / S88 / Sniffer input not yet in operation,
    An automatic power balance of interconnected rail outputs to form an extra-strong driving circuit (up to 20A) is currently not available.
    ABAs not operational for operations (because RailManager is not yet operational with MX10),
    No "frequency hopping" for the radio channel yet. The radio channel can be set manually in the MX10 menu under "MX10 Config". It can lead to "radio collisions" with foreign products, e.g. Wireless mouse come.
    "BaseCab" functions (driving, CV programming, ...) not working; Alternatively, under the menu item "ObjectDB vehicles" speed, direction and functions can be controlled.
    Some of the monitoring and diagnostic functions are not fully functional yet.

NOT yet implemented functions (focus MX32):

    In the WEI panel no more detailed signals are realized.
    Track diagrams not yet available (only WEI panels and accessories list).
    SERV PROG and OP PROG: Handling of CV sets only partially realized
    Not all functions are completely available in the object database, e.g. Filter, ZACK, ...

1.25.0101 (January 25, 2019)

1.25.0100 (January 19, 2019)

1.25.0101 came out as a correction 1.25.0100 which was itself a correction to 1.25.0001

I am using 1.25.0001 and it works ok. Apparently there was a problem with 1.25.0001, and a month later the correction came out quickly as 1.25.0100. Then 6 days later the 1.25.0101 came out. I loaded it and had nothing but terrible issues, switch controls all screwed up, icons missing from the screen, just awful.

DON'T install either of these!

I never found out what was wrong with 1.25.0001.

MX10 & MX32:  SW-Version 1.25

Correction version 01.25.0100  NOW AVAILABLE (19. JAN 2019) as Download.   

Corrections in 01.25.0100 to the original version 01.25-0001 (DEC 2018):

• • SINGLE STOP (press S-key shortly)works again (in version 01.25.0001 error due to SW bug, again complete display of CV descriptions in OP PROG and SERV PROG
  • Various corrections in SERV PROG: wrong CV number "0" eliminated, displays "NO-RD" instead of "R...", if operation is aborted, prevents display of wrong values, warns of third-party load on programming track, e.g. by StEin modules on DC-S2 which are supplied at the same time.
  • Flashing of function symbols as note regarding commands which may not have come through, if acknowledgement from the digital central is not received due to bad radio connection, is now automatically stopped as soon as radio works again.
  • GUI takeover (from MX10 to MX32), elimination of the abbreviation to 4 letters
  • CV programming and operation of "old" accessory modules MX8 corrected
  • and many more

New features and improvements (already in SW version of December:

• • Radio controller MX32FU: if the battery is low the window "Battery below 10%" pops up and shows an estimated time for the remaining battery life, and gives you the choice between continuing operation or immediate power-down. This window pops up periodically with an updated estimate.
  • Visualisation of radio frequency interference (RFI) between controller and command station: if turning on/off functions is not received, the corresponding symbol in the function area flashes.
  • Cloning now as two separate procedures which are called up from LOCO: a cloning window with the corresponding header pops up: "Cloning an active address" or "Cloning from address in ObjDB": In the first case, the GUI (name, picture, function symbols, …) is copied from the active address to another one (enter this address in the window); in the second case it copies the GUI from an address in the ObjDB (enter this address in the window) to the active address.
  • Track-on search (former tilt-search): The found addresses are sorted by time; "usually" (only one address is found), this one found address can be activated with the F-key.
  • OP PROG: Assigning a Consist address (for the decoder-dependent consisting).
  • MAN function can now also be activated by assigning a function key on Lokmouse, WIFI-Lokmouse and other XPressNet devices. Settings in the MX10 menu "MX10 Config".
  • Additional and updated Help files in the MX32/MX32FU.
  • Various add-ons and adjustments concerning the interlocking programs ESTWGJ, STP, WinDigipet, iTrains.
  • Booster logic concerning short-circuit handling: the current solution (current SW-version) is the following: every overcurrent on track output 1 of the central command station or on one of the outputs on a booster leads to the shut-down of all outputs; this is not the final solution.
  • Adjustments (and partially new handling) of the East-West direction control.Together  with decoder SW version 38, see below; also see description in the manual for MX32 and MX32FU, chapter LOCO.
  • Adjustments concerning deleting addresses from the object database (in the MX32) and the system database (in the MX10).

1.25.0001 (December 21 2018)

A good release, I am using as of March, 2019

From the Zimo web site (google translation)

ERROR CORRECTIONS (compared to version 01.24.0001)
• Booster logic with regard to short-circuit handling: According to current logic (this software version), any overcurrent on the rail output S1 of the base unit or on one of the outputs of the booster units causes all outputs to switch off; this is not the final solution yet; see also "NOTE on the NEXT SW versions".
NOTE on booster mode: In the current SW version, the rail output (usually S1) of the control panel (MX10) should not be connected directly to a rail output of the booster unit (another MX10) (so that the load is evenly divided): a Resistance of approx. 0.1 ohms should be in between - as a rule the line, rail and wiper resistances are sufficient.
• Corrections (and partially renewed operation of the East-West direction control
• Fixed STOP & OFF on the MX10 screen
• Fixed communication issues regarding the StEin modules and MX31 ("old" remote)
• Elimination of the "red-green problem" (sticking direction arrows on the MX32 when changing direction).
• Elimination of errors in the display of switch positions of the MX8 accessory module.
• OP PROG: restore the correct displays "ACK" and "NO-RD".
• FAHR operating state: Restoration of the single-step control by the scroll wheel.
• GUI transfer between cabs (or from the central storage in the MX10) name and image restored.
• Display of the "communication point" (not yet the final execution)
• Restoration of the correct MAN status after restarting the system
• Corrections for delete operations from object database (in MX32) and the system database (in MX10)
• Various corrections related to interlocking programs ESTWGJ, STP, WinDigipet, iTrains.

Known SOFTWARE BUGs in MX10 and / or MX32 (also in this version 01.25.0001)
• Display communication point, RailCom logo, "Quality of Service" not yet as described
• Traction operation: Takeover of an existing traction does not function properly if the current owner's console is not connected.

NOTE ON NEXT SW Versions - Features to be implemented in the near future are listed below; in the approximate order of the planned realization in time:
• Extension of the reroute search by direct possibility of redirecting a found vehicle (especially important in case of address conflict, ie in the event that a found vehicle has the same address as an existing one, or that several vehicles with the same address are found) ,
• RailCom feedback of the current drive level and the current HLU speed limit
• Decoder software update and sound loading with the MX10 from the USB stick.
• Load GUI (Graphical User Interface for the MX32 console) from decoders (at least from sound decoders), i. the information about names, function symbols, image, and speedometer are integrated into the sound projects, and are then transferred to the system (MX32 cab) when the locomotive is put into service via RailCom.
• Include the new software versions for StEin and Roco busy modules in the software container file, where software for MX10 and MX32 is already released. These products will then also be able to update via the CAN bus, in the case of StEin as an alternative to the update via the USB stick.
• Further help files in the MX32 / FU
• Further expansion of the booster logic in the MX10, in particular configurable linkage of the circuits during short-circuit handling (which supply circuits should be switched off in the event of a short-circuit).
• Turnout cycle for decoders that need OFF and decoders that need multiple commands
• defining and switching multi-conceptual signals, most important types (especially: Q decoder signals) in the WEI panel,
• MX10 - "Voltage & Current - Setting": Commissioning "UES-Adaptive", the automatic adaptation of the cut-off threshold to the current power consumption (eg 2 A above it) for protection against "small short circuits" (which are not big enough for the MX10 set overcurrent threshold)
• Optimization of send cycle, delete functions;
• Traction (optimization) - automatic reduction of control influence, so that locomotives do not "work against each other"
(suitable - i.e. ZIMO - decoders should receive corresponding messages)
• Tractions - Consider the delayed startup due to sound start in a vehicle,
• various corrections in WEI operating state (gray, black fields, ...),
• commissioning of further MX10 menu items,
• Creation of a GUI backup memory in the MX10, where the current GUI or all GUIs can be stored from the object database of the Finder when requested on the MX32 (in the menu) and in which the data can no longer be destroyed, even during software changes , In this area there is NO possibility to change and only very secure deletion possibilities. Any number of vehicles can be stored, even under the same address, as long as anything differs in their GUI.

NOT yet implemented functions (main focus MX10):
• track signals: Motorola data format, mfx not yet in operation,
• Loconet / S88 / Sniffer input not yet in operation,
• An automatic current balance of interconnected rail outputs to form an extra-strong driving circuit (up to 20A) is currently not available.
• ABAs not operational for operations (because RailManager is not yet operational with MX10),
• No "frequency hopping" for the radio channel yet. The radio channel can be set manually in the MX10 menu under "MX10 Config". It can lead to "radio collisions" with foreign products such as Wireless mouse come.
• "BaseCab" functions (driving, CV programming, ...) not operational; Alternatively, speed, direction and functions can be controlled under the menu item "ObjectDB vehicles".
• Some of the monitoring and diagnostic functions are not fully functional yet.

NOT yet implemented functions (main focus MX32):
• In the WEI panel no more detailed signals are realized yet.
• Track diagram not yet available (only WEI panels and accessories list).
• SERV PROG languagOP PROG: Handling of CV sets only partially realized,
• Not all functions are completely available in the object database, e.g. Filter, ZACK, ...
• Delete individual locomotive images not yet possible (only all at the same time in PultConf -> Clear Data)

My notes on 1.25.0001:

MX10:

• • language changed back to German
  • voltages changed back to 16v
  • have not checked to see if current limits were changed

MX32:

• • boots faster wirelessly
  • objectdb filter (TP) does nothing
  • deleting objects marks them in red, buit they stay
  • consisting still removes one of the locos from the local recall

1.24.0001

Notes on installation:

when you insert the usb, you can back up things... and now you can mark the items and then backup marked items.

The backup images does not work, just sits there at 0%, whether you mark it and execute or execute it by itself.

the zip file must be unzipped to the zsb file...

Google translation of release notes on the Zimo site:

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 icons, switch icons, system icons, tacho designs
- CV designations, function names in German and English


After the actual update you can also import:

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

 

Not affected by the update process and get stuck in MX10 or MX32:

- Vehicle pictures that already existed before the update,
- Object database, vehicles
- List of accessory addresses and WEI panels.

Innovations & improvements in MX10 and MX32 (compared to version 01.23.0050 / 51)

"Abkippsuche", which is called now and in the future as "Aufgleissuche" (in agreement with the manufacturer's association "Railcommunity), was extended by the listing of further in the search period found addresses with same-side connection with the system already known vehicles.
    Addressing (changing the vehicle address in the decoder) now also in OP MODE (ie possible without programming track); only for decoders (or the software versions) that support this function (ZIMO decoder from 37.28, July 2018) and switched on RailCom. The addressing can be reached via the key sequence E + F + A (ie entry into OP MODE and then "A" for addressing or Shift-A for setting a Consist address).
    Overcurrent logic corrected: in the event of short circuits that are interrupted by brief non-short-circuit phases, the UES shutdown will still occur after the correct time (namely after the set shutdown time, previously there could be a premature shutdown).
    Via E + 0, CONFIG is called instead of PULT CONF; The list of setting topics now summarizes the two selectable sections "System Center" and "This Desk" (the previous PULT CONF), which has freed up a position on the E-screen for the "One List".
    E + 9 will not function until further notice (later: ABA).
    Via E + 8, the "StEin list" is called up, where all connected StEin modules can be listed, and the status of track sections, switches, signals, inputs, etc., over several display levels. monitored and changed. The Roco Z21 occupancy detectors as well as MX10 in booster mode are also displayed in the "StEin list".
    The function "Start from the console" (adjustable in the STOP & OFF menu of the MX10 base unit) causes both bus outputs to be set to "OFF" after the system is started and to be switched on via a control panel. This ensures (if desired) that only then comes tension on the rail, if at least one remote is up and operational.
    New settings for interconnections of the rail outputs and booster mode in the MX10 CONFIG menu of the MX10 base unit: There are now 3 settings in SYS MODE 3: "MASTER" (normal single unit or even master in arrangement with booster units), "SYNC" (for the Interconnection of the two outputs, see instructions in operating instructions, drive voltages, SSP and OFF, are switched in the same way, use of rail 2 as programming track blocked), "B1", ... "B16" (booster devices).
    Automatic deletion from the MX10 transmission cycle after 100 hours of operation, if all driving data of an address (speed and functions are switched off).
    Identification process (reading of the most important CVs for display in the OP MODE screen) accelerates and usually takes place in the background.

Known SOFTWARE BUGs - Malfunction or Operating Difficulties of MX10 and / or MX32:

    List still in progress

NOTE ON NEXT SW Versions - Features to be implemented in the near future are listed below; in the approximate order of the planned realization in time:

    Extension of the Aufgleis-Suche by direct possibility of redirecting a found vehicle
    (especially important in the event of an address conflict, ie in the event that a found vehicle has the same address as an existing one, or if several vehicles with the same address are found).
    Decoder software update and sound loading with the MX10 from the USB stick.
    GUI (Graphical User Interface for the MX32 console) from decoder (at least from sound decoders) load, i. the information about names, function symbols, image, and speedometer are integrated into the sound projects, and are then transferred to the system (MX32 cab) when the locomotive is put into service via RailCom.
    Include the new software versions for StEin and Roco occupancy reporting modules in the software container file, where software for MX10 and MX32 is already released. These products will then also be able to update via the CAN bus, in the case of StEin as an alternative to the update via the USB stick.
    Further help files in the MX32 / FU
    Further expansion of the booster logic in the MX10
    NOTE on the booster mode: In the current version, due to the not very exact synchronization of the rail output (usually S1) of the control panel (MX10) must not be connected directly to a rail outputs of the booster device (another MX10) (otherwise it comes to shutdown due to erroneously assumed short circuit); at least a resistance of 0.1 ohms must be in between - as a rule the line, rail and wiper resistances are sufficient. Incidentally, the outputs of one device in each case may very well be interconnected.
    Turnout cycle for decoders that need OFF and decoders that need multiple commands
    define and switch multi-conceptual signals, main types (especially: Q decoder signals) in the WEI panel,
    MX10 - "Voltage & Current - Setting": Commissioning "UES Adaptive", the automatic adaptation of the cut-off threshold to the current power consumption (eg 2 A above it) for protection against "small short circuits" (which are not big enough for the MX10 Overcurrent threshold)
    Optimization of sending cycle, deletion functions;
    Tractions (optimization) - automatic reduction of the control influence so that locomotives do not "work against each other"
    (suitable - i.e. ZIMO - decoders should receive corresponding messages)
    Tractions - Considering the delayed startup due to sound start in a vehicle,
    various corrections in the operating state WEI (gray, black fields, ...),
    Commissioning of further MX10 menu items,
    Creation of a GUI backup memory in the MX10, where at the request of the MX32 (in the menu) the current GUI or all GUIs from the object database of the Fahpultes can be stored, and in which the data can not be destroyed, even with software changes. In this area there is NO possibility to change and only very secure deletion possibilities. Any number of vehicles can be stored, even under the same address, as long as anything differs in their GUI.
    Control of radio link control by communication point

NOT yet implemented functions (main focus MX10):

• • Track signals: Motorola data format, mfx not yet in operation
  • Loconet / S88 / Sniffer input not yet in operation
  • An automatic current balance of interconnected rail outputs to form an extra-strong driving circuit (up to 20A) is currently not available.
  • ABAs not operational for operations (because RailManager is not yet operational with MX10),
  • No "frequency hopping" for the radio channel yet. The radio channel can be set manually in the MX10 menu under "MX10 Config". It can lead to "radio collisions" with foreign products such as Wireless mouse come.
  • "BaseCab" functions (driving, CV programming, ...) not operational; Alternatively, speed, direction and functions can be controlled under the menu item "ObjectDB vehicles".
  • Some of the monitoring and diagnostic functions are not fully functional yet.
    
    NOT yet implemented functions (main focus MX32):
  • In the WEI panel no more detailed signals are realized.
  • Track pictures not yet available (only WEI panels and accessories list).
  • SERV PROG and OP PROG: Handling of CV sets only partially realized
  • Not all functions are completely available in the object database, e.g. Filter, ZACK,
  • Delete individual locomotive images not yet possible (only all at the same time in PultConf -> Clear Data)

1.23.0050

My installation notes:

The accessory decoder edit and address bug problem is still there, so be sure to reboot after any change to any accessory decoder edit. The E + 3 settings can also affect this, make sure you have all green boxes, and make sure you are in paired mode not single.

ARGH!

Translation of general description of the release:

MX10_MX32_01.23.0050_full

Full version for MX10 and MX32. This "container file" contains the previously split files of the previous versions. In the .zip folder, therefore, there is only the update file without the fonts, these can be taken over from the earlier software version entries (01.20.0001) and reloaded if necessary. Whereby the fonts have not changed since 01.20.0001, therefore with an update from 01.20.0001, 01.20.0150, 01.21.0001 or 01.22.0150 / 151, 01.23.0001 to the version 01.23.0050 there is NO extra reloading of fonts necessary.

Translation from site: (file description)

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 icons, switch icons, system icons, tacho designs
- CV designations, function names in German and English
 
After the actual update you can also import:

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

 
Not affected by the update process and getting stuck in MX10 or MX32:

- Vehicle pictures that already existed before the update,
- Object database, vehicles
- List of accessory addresses and WEI panels.

Innovations & improvements in MX10 and MX32 (compared to version 01.23.0001)

     Operation logic with "stop balls" extended to booster mode: In the event of a short circuit on one of the booster circuits, the relevant one is now displayed, but both "rail 1" of the central unit and all booster circuits are switched off. Basically, all booster circuits are always the same as "track 1" of the central unit, which refers to SSP, OFF and ON. Individual switching on and off as well as definable links are only intended for a later SW version.

BUG FIXES

     Correction of SERVICE MODE in connection with P.F.u.Sch.
     Optimization of the SERVICE MODE (programming track) operating logic, in particular a warning if too much power is consumed on "Rail 2" to enable safe CV programming and reading. This is particularly the case when the DC circuit "S2" supplies StEin modules with accessory voltage.

Known SOFTWARE BUGs - Malfunction or Operating Difficulties of MX10 and / or MX32 :.

NOTE ON NEXT SW Versions - Features to be implemented in the near future are listed below; in the approximate order of the planned realization in time:

    Extension of the ABKIPP search by direct possibility of redirecting a found vehicle
    (especially important in the event of an address conflict, ie in the event that a found vehicle has the same address as an existing one, or if several vehicles with the same address are found).
    Decoder software update and sound loading with the MX10 from the USB stick.
    GUI (Graphical User Interface for the MX32 console) from decoder (at least from sound decoders) load, i. the information about names, function symbols, image, and speedometer are integrated into the sound projects, and are then transferred to the system (MX32 cab) when the locomotive is put into service via RailCom.
    Include the new software versions for StEin and Roco Busy Module 10808 in the software container file, where software for MX10 and MX32 is already released. These products will then also be updatable via the CAN bus, in the case of StEin as an alternative to the update via the USB stick.
    Further help files in the MX32 / FU
    Further expansion of the booster logic in the MX10
    NOTE on the booster mode: In the current version, due to the not very exact synchronization of the rail output (usually S1) of the control panel (MX10) must not be connected directly to a rail outputs of the booster device (another MX10) (otherwise it comes to shutdown due to erroneously assumed short circuit); at least a resistance of 0.1 ohms must be in between - as a rule the line, rail and wiper resistances are sufficient. Incidentally, the outputs of one device in each case may very well be interconnected.
    Turnout cycle for decoders that need OFF and decoders that need multiple commands
    define and switch multi-conceptual signals, main types (especially: Q decoder signals) in the WEI panel,

MX10 - "Voltage & Current - Setting": Commissioning "UES Adaptive", the automatic adaptation of the cut-off threshold to the current power consumption (eg 2 A above it) for protection against "small short circuits" (which are not big enough for the MX10 Overcurrent threshold)
Optimization of sending cycle, deletion functions;
Tractions (optimization) - automatic reduction of the control influence so that locomotives do not "work against each other"
(suitable - i.e. ZIMO - decoders should receive corresponding messages)
Tractions - Considering the delayed startup due to sound start in a vehicle,
various corrections in the operating state WEI (gray, black fields, ...),
Commissioning of further MX10 menu items,
Creation of a GUI backup memory in the MX10, where at the request of the MX32 (in the menu) the current GUI or all GUIs from the object database of the Fahpultes can be stored, and in which the data can not be destroyed, even with software changes. In this area there is NO possibility to change and only very secure deletion possibilities. Any number of vehicles can be stored, even under the same address, as long as anything differs in their GUI.
Control of radio link control by communication point

NOT yet implemented functions (main focus MX10):

    Track signals: Motorola data format, mfx not yet in operation,
    Loconet / S88 / Sniffer input not yet in operation,
    An automatic current balance of interconnected rail outputs to form an extra-strong driving circuit (up to 20A) is currently not available.
    ABAs not operational for operations (because RailManager is not yet operational with MX10),
    No "frequency hopping" for the radio channel yet. The radio channel can be set manually in the MX10 menu under "MX10 Config". It can lead to "radio collisions" with foreign products such as Wireless mouse come.
    "BaseCab" functions (driving, CV programming, ...) not operational; Alternatively, speed, direction and functions can be controlled under the menu item "ObjectDB vehicles".
    Some of the monitoring and diagnostic functions are not fully functional yet.

NOT yet implemented functions (main focus MX32):

    In the WEI panel no more detailed signals are realized.
    Track pictures not yet available (only WEI panels and accessories list).
    SERV PROG and OP PROG: Handling of CV sets only partially realized
    Not all functions are completely available in the object database, e.g. Filter, ZACK, ...
    Delete individual locomotive images not yet possible (only all at the same time in PultConf -> Clear Data)

Translation from site: (file description)

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 icons, switch icons, system icons, tacho designs
- CV designations, function names in German and English

After the actual update you can also import:
- Vehicle pictures
- object database, vehicles; Equipment; interlocking; CV lists and sets

Not affected by the update process and get stuck in MX10 or MX32:
- Vehicle pictures that already existed before the update,
- Object database, vehicles
- List of accessory addresses and WEI panels.

Innovations & improvements in MX10 and MX32 (compared to version 01.22.0150 / 151)

• New graphics and (tw.) Operating logic ("stop balls" with touch surfaces) for single stop, collective stop, OFF; new touch fields ("blue arrows") to hide and show the "balls", thus S-key always available for single stop. Including the switching on / off of booster devices (MX10 in booster mode) in the "left ball" and display of the causer (device, output) of an overcurrent state in this "ball", collective stop and restart all booster Circuits together via "SSP" or "ON" to "left ball"; "right ball" always stays for rail-2, programming track.
• Optional Power on "START FROM PULSE": When set in the "VOLT & AMPERE" menu of the MX10, the respective output (ie rail-1 and / or -2) is not switched on automatically when the MX10 starts up, but must first be manually switched off Remote console (MX32) are turned on, in which one is tapped on the "stop balls" appearing there. This has the advantage in some applications that the trains can not drive undesirably before the control panels are booted (which takes longer than the base unit MX10).
• FAHR: Elimination of the "fourth level" of the function tableau, switching back to level 1 by long-shift.
• Optimization of cooperation with STP and P.F.u.Sch (interlocking and programming software by E. Sperrer), especially with regard to Service Mode Programming and MX8.
• New operating state STEIN LI (= list): serves to list the existing stationary device modules "StEin"; the representation and operation of the StEin modules in the bar has been optimized and expanded. For each section of track: HLU, busy message, overcurrent and short circuit; in the representation for individual track section also found addresses. For each turnout: Right-left position (or straight-line branch) display and switch, display unrecognizable position by flashing, circulation. For the 16 inputs: Display of the active inputs.
• Operating status ZUB LIST: Removal of the stationary module "StEin" (because now in STEIN LISTE, see above),

BUG FIXES

• CAN bus utilization display on the MX10 display: so far, only CAN messages were included in this counter that are known and valid from the point of view of the MX10, but not those that are sent by other bus users without being intended for the MX10. Now all messages are displayed, allowing a better estimate of the load; The CAN bus can transport a maximum of 1000 messages / second (at the current speed of 125 bit / sec).
• Correction of various errors in the state WEI (panels for accessory articles).
• Corrections in the CAN protocol for Windigipet and iTrains
• UEP display (instead of UES) in the event of overcurrent during programming operations on the programming track (service mode)

NOTE ON NEXT SW Versions - Features to be implemented in the near future are listed below; in the approximate order of the planned realization in time:

• Extension of the ABKIPP search by direct possibility of redirecting a found vehicle (especially important in the event of an address conflict, ie in the event that a found vehicle has the same address as an existing one, or if several vehicles with the same address are found).
• Decoder software update and sound loading with the MX10 from the USB stick.
• GUI (Graphical User Interface for the MX32 console) from decoder (at least from sound decoders) load, i. the information about names, function symbols, image, and speedometer are integrated into the sound projects, and are then transferred to the system (MX32 cab) when the locomotive is put into service via RailCom.
• Optional switch-on procedure, activatable by menu: MX10 does not start with the ramp-up of the rail outputs until command from a remote control, i. when the consoles have started up, both ticket exits first turn OFF (also all boosters) and only after touch-actuation, ON drive up voltages.
• Further help files in the MX32 / FU
• Further expansion of the booster logic in the MX10
      NOTE on the booster mode: In the current version, due to the not very exact synchronization of the rail output (usually S1) of the control panel (MX10) must not be connected directly to a rail outputs of the booster device (another MX10) (otherwise it comes to shutdown due to erroneously assumed short circuit); At least a resistance of 0.1 ohms must be in between - as a rule the line, rail and wiper resistances are sufficient. Incidentally, the outputs of one device each other may very well be interconnected.
• Turnout cycle for decoders that need OFF and decoders that need multiple commands
• define and switch multi-conceptual signals, main types (especially: Q decoder signals) in the WEI panel,
• MX10 - "Voltage & Current - Setting": Commissioning "UES Adaptive", the automatic adaptation of the cut-off threshold to the current power consumption (eg 2 A above it) for protection against "small short circuits" (which are not big enough for the MX10 Overcurrent threshold)
• Optimization of sending cycle, deletion functions;
• Tractions (optimization) - automatic reduction of the control influence so that locomotives do not "work against each other"(suitable - i.e. ZIMO - decoders should receive corresponding messages)
• Tractions - Considering the delayed startup due to sound start in a vehicle,
• various corrections in the operating state WEI (gray, black fields, ...),
• Commissioning of further MX10 menu items,
• Creation of a GUI backup memory in the MX10, where at the request of the MX32 (in the menu) the current GUI or all GUIs from the object database of the Fahpultes can be stored, and in which the data can not be destroyed, even with software changes. In this area there is NO possibility to change and only very secure deletion possibilities. Any number of vehicles can be stored, even under the same address, as long as anything differs in their GUI.
• Control of radio link control by communication point

NOT yet implemented functions (main focus MX10):

• Track signals: Motorola data format, mfx not yet in operation,
• Loconet / S88 / Sniffer input not yet in operation,
• An automatic current balance of interconnected rail outputs to form an extra-strong driving circuit (up to 20A) is currently not available.
• ABAs not operational for operations (because RailManager is not yet operational with MX10),
• No "frequency hopping" for the radio channel yet. The radio channel can be set manually in the MX10 menu under "MX10 Config". It can lead to "radio collisions" with foreign products such as Wireless mouse come.
• "BaseCab" functions (driving, CV programming, ...) not operational; Alternatively, speed, direction and functions can be controlled under the menu item "ObjectDB vehicles".
• Some of the monitoring and diagnostic functions are not fully functional yet.

NOT yet implemented functions (main focus MX32):

• In the WEI panel no more detailed signals are realized.
• Track pictures not yet available (only WEI panels and accessories list).
• SERV PROG and OP PROG: Handling of CV sets only partially realized
• Not all functions are completely available in the object database, e.g. Filter, ZACK, ...
• Delete individual locomotive images not yet possible (only all at the same time in PultConf -> Clear Data)

Known SOFTWARE BUGs. which lead to misconduct or operating difficulties of MX10 and / or MX32

ATTENTION: When using boosters on the MX10, in case of a short circuit in the booster section there may be problems with the cancellation of the UES message (if then the cause of the short circuit has been removed) on the MX32 / FU. Here there will be a correction software version regarding the GUI (stop balls) on the MX32 / FU.

Results:

The "backwards step, found in the last release is still there, i.e. things that USED to be in English are back in German.

I've had a couple of lockups where the screen got stuck on one menu, on the "W" screen to control switches, buttons or touches did nothing.

Translation from site:

 Software update for MX10 and MX32 (FU)

Software update from the USB stick:

To make the software update as easy as possible, is in each product (ie base unit and control panels)

a USB host socket installed, on which a standard memory stick is plugged, on the

previously the new software version for the respective device or the container file for several products

(like MX10, MX32, StEin, ..) is copied from the ZIMO website.

The updatable single devices (first expansion stage "control panel and control panels):
MX32 remote, version for cable operation
MX32FU remote, for radio or cable operation
MX10 base unit (digital control unit, or as a booster) ...

ATTENTION: the USB stick to be used must be formatted in the file system FAT32 (not FAT16); that is the case for sticks. which were purchased at a later time, as well as for stick supplied by ZIMO.

Since August 2015, there are so-called container files, each containing the new software for MX10 AND MX32 (FU), along with other data such as symbols or fonts, in the future, the software of StEin modules. Therefore, only a single .zip file (from this page) needs to be downloaded. Unpacking creates das.zsb file (this is the eigtntliche container file), which is stored on a USB stick (see above).

This USB stick with the container file will then be inserted one after the other in EACH device (ie in the MX10, in each of the existing MX32 racks, and possibly also in the StEin modules) in order to carry out the respective software update. This happens during operation, i. the devices are on, but the trains on the system should be better stopped; the USB stick is recognized by the respective device, reported on the device display (with facts about the update, such as version designation, date, etc.), whereupon the update process can be initiated (or optionally a controlled abort can take place).

First, a list for selecting the desired activity will be displayed. The selection is made with the rotary knob (on the MX10) or the scroll wheel (MX32). Most of the time, however, only the first (already marked) point needs to be executed: "MX10 Update Everything" or "Automatic MX32 Update".

The start is done by turning the knob (MX10) or the A-button (MX32).

After the software update of the MX10, a cold start must be performed on the MX10. Therefore, the MX10 should be disconnected from the power supply for approximately 1 minute to ensure that the internal capacitor has been completely discharged.

During the update process (takes only a few seconds on the MX10, MX32 u.U. many minutes because of the many graphics and photos to be loaded) must of course not be removed from the USB stick or the power supply. At the end, a request is made, such as "remove USB stick". The device restarts automatically and is ready for use after the next startup.

Further information about the update: see operating instructions of the individual devices!

1.22.0001 - 2017.12.23

Finally installed it, and found some issues.

First, the good news, consisting (traction) finally works and works much more easily. The last version I used, you could not reverse the direction of a loco in a consist, which is really vital to follow prototype, and also from a practical point, keeps you from having to turn the locos at the end of the line.

So when you are creating the consist, TP and then a number for the consist number. It used to be that you needed some other keystroke combinations, to reverse a loco within a consist, but now when you hit TP, you get a popup menu that lets you add/remove a loco from the consist, and also reverse it's direction. I'll document this further as I explore it.

Throwing turnouts with accessory decoders: As many of you know, for some strange reason, Europe likes to group accessory decoder functions in groups of 4. So for an ordinary/standard/NMRA compliant accessory decoder, to choose address 1, 2, 3, etc you have this setup of major and sub addresses... I have a chart on my page, but 1,0 = address 1, 1,1 = address 2,  1,2 = address3, and 1,3 = address 4 and then you go to 2,0 for address 5 ....

Anyway, to program these addresses for the matching function keys, you need to enter the panel by holding the red shift key (up arrow) and then the W^ key...

This is as it was before.... but where you go to set up switches with the E and then the 3 key gives you a list of numbers with 4 colored boxes, red or green to the right. I found hitting the number keys toggles them from red to green... (ok, yawn)

But I deleted these and seemed to make no difference, then found could not do anything with accessories... and weirdly I found that you need an entry numbered for the NMRA accessory number, so I needed lines 1 through 28, each with it's block of 4, even though the numbering scheme elsewhere was this major and subaddress model.

So, the warning is if you go to the E + 3 setup menu, leave it alone. If you cannot address accessories above a certain number, be sure this list has enough entries. I'm not satisfied I understand this fully (and it does not change later ha ha!)

The radio connection and the boot speed seem a little better, not marked improvement.

There are some things broken, like menus that used to be shown in English, are now always in German. I'll be documenting this soon.

Note that some settings in the MX10 may change, specifically the output voltage will change back to 16 volts. Also I noticed when setting the output voltage to 24, it displayed 23.6... most of the issues I have found so far are in the MX32.

Here's the raw translation from Google, I have put notes in red on things I want to investigate or clarify.

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

<<< good to see a radio update, seeing this is normally a performance or reliability increase >>>

- Operating languages ​​German and English

- Function icons, switch icons, system icons, tacho designs

- CV designations, function names in German and English

After the actual update you can also import:

- Vehicle pictures

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

Not affected by the update process and get stuck in MX10 or MX32:

- Vehicle pictures that already existed before the update,

- Object database, vehicles

- List of accessory addresses and WEI panels.

Innovations & improvements in MX10 and MX32 (compared to version 01.21.0500)

    The "ABKIPSUCHE", trigger from MX32 ago in the operating state "DRIVE ON": the re-launched during the last minute (or just briefly "tilted" and re-attached vehicles) are displayed,
    Booster mode, the second (third, ...) MX10 is assigned a booster number in the menu item "MX10 Config"; via the 8-pin CAN connection with the MX10 acting as the control center, the booster devices (both rail outputs) form the DCC signal of the output "S1" of the control panel; The driving voltages as well as the SSP and OFF states are also switched to the same. In the event of a short circuit (overcurrent) on one of the booster outputs, all other rail outputs are also switched off. Regarding this short-circuit handling, there will be more options in future software versions.
    NOTE on the booster mode: in the current version, the rail output (usually S1) of the control panel (MX10) may not be connected directly to a rail output of the booster unit (MX10) due to incorrect synchronization (otherwise it will shut down due to erroneous assumptions) short circuit); at least a resistance of 0.1 ohms must be in between - as a rule the line, rail and wiper resistances are sufficient. Incidentally, booster outputs with each other may well be interconnected.
    Automatic deletion of addresses from the transmission cycle when speed and all functions are zero or off, and 10 operating hours have elapsed.
    Identifying vehicles (readout of data such as decoder type, software version, serial number, ..) now takes place in the background, so that a display without waiting time is possible when entering the OP MODE programming.
    The east-west direction is now also displayed in level 1 of the RüF (important for the overview especially for tractions); Actual application of "east-west" depends on the release of the corresponding decoder SW (38).
    The time can now be set on each control panel, the MX10 and all other consoles follow automatically.
    New "yellow bar" on the upper edge of the display of the MX32 when controlled by interlocking or other computer program, separated by speed direction "S" and functions "F".
    Tractions: MAN, RG are automatically adopted by all participants.

BUG FIXES

    WEI (Turnout Panel): eliminates sticking in certain situations, eliminates errors in configuration.
    ZUB LIST: Failed to reactivate the MX8 and MX9 modules
    Error during adjustment of the RailCom speedometer
    et al

NOTE on the SHORT-TERM PLANNED Correction Version:

    Addressing MX8 modules
    Control of radio link control by communication point
    Updated English texts for MX32 / FU

NOTE ON NEXT SW Versions - Features to be implemented in the near future are listed below; in the approximate order of the planned realization in time:

    Decoder software update and sound loading with the MX10 from the USB stick.
    GUI (Graphical User Interface for the MX32 console) from decoder (at least from sound decoders) load, i. the information about names, function symbols, image, and speedometer are integrated into the sound projects, and are then transferred to the system (MX32 cab) when the locomotive is put into service via RailCom.
    Further help files in the MX32 / FU
    New graphics ("ball design") and better usability for stop, collective stop, OFF
    Further expansion of the booster logic in the MX10
    Turnout cycle for decoders that need OFF and decoders that need multiple commands
    define and switch multi-conceptual signals, main types (especially: Q decoder signals) in the WEI panel,
    MX10 - "Voltage & Current - Setting": Commissioning "UES-Adaptive", the automatic adjustment of the cut-off threshold to the current power consumption (eg 2 A above this) for protection against "small, short circuits" (which are not big enough for the normal overcurrent threshold are)
    Optimization of send cycle, delete functions

1.21.0500 - 2017.10.11 - WORKS!

Released in October 2017, fixes the instability and crashing problems of the previous couple of releases. As in the previous release, wireless speed is improved, and booting is faster. the consisting procedure is changed. See my separate page on consisting by clicking HERE.

Still checking this release out.

Bugs so far:

1. registering a loco in a consist often requires you to perform this twice, and it seems that sometimes a loco falls out of a consist.
2. The yellow triangles that used to show the relative direction of a loco in a consist no longer show which locos are reversed, and it seems some other erratic displays.
3. The new popup when pressing TP on a loco already in a consist is in garbage characters, neither German nor English, adds to the confusion.
4. Manual states it is irrelevant of which loco address is used to control the consist, but that is wrong, only the loco address used will receive function commands, i.e. ONLY that loco will receive bell, horn, etc.
5. MX32 manual still states that TP button is held down until the triangle flashes to change direction. To change direction, you must make the consist first, then go to that loco after it is in the consist, hit TP and then you get a new popup window (you cannot read) to reverse the direction of the loco.
6. LAN settings (Ethernet on back), there should be a setting for the IP address, but there are settings different from the manual:
   1. Zimo Binary
   2. Zimo Ascii
   3. Zimo ZSP

   So, need to know what settings to use with Z21 phone app. Also there should be an IP address setting, but the only settings are mask and DHCP, so no way to set static.

Also no fonts in this file, so go back and get the 1.20.xxxx font files if your fonts are messed up. (fonts120.zip in the 1.20.0001 release timeframe)

1.21.0015 - fixed version of 1.21.0010 - 2017.07.26

Works but unstable

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

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

But it has the newer features, and if you don't mind rebooting often, it's the best so far.

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

1.21.0010 / 0012 - DON'T INSTALL THIS VERSION

Apparently this version was fraught with many issues, and an update was released in very short order.

this version had different versions for the MX10 and MX32, supposedly fixing the 1.21.0001 problems

1.21.0001 - July 2017 - DON'T INSTALL THIS VERSION

I had my layout inoperative due to work around the home. I did not install this version, but nothing but issues from all reports.

This version was recalled, and re-labeled 1.21.0010.

1.20.0150 - 2017.02.24

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.

no fonts in the file, you have to have to load the 1.20.0001 font file released before or load after doing this update if you fonts are messed up.

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.20.0100 - 2016.12.23

Some things fixed. Boots to wireless, wireless response better, 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 often do not update.

no fonts in the file, you have to have to load the 1.20.0001 font file released before or load after doing this update if you fonts are messed up.

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.0001- 2016.10.28 - DON'T INSTALL THIS VERSION

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.

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.

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

OK. the firmware file was recalled, not even on the site, but a new fonts file available fonts120..

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.19.0200 - 2016.05.20

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

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

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.

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.

update: no fonts in the file, you have to have th e 1.19.0001 loaded separately, or load after doing this update if you fonts are messed up.

1.19.0001 - 2016.04.20

The new SW version 1.19 (as already 1.18.0052) as a common container file for MX10 and MX32 can be used directly for all devices that already contain a software version as of 1.16.xx; i.e. for deliveries starting from April 2015. It is only suitable for MX32 of Rev. 7 (MX32 without reset contacts under the ventilation slots).

I believe this means is you can't use this on the older MX1's

Also note that a fonts.zip file is available separately that is just fonts.zip