Zimo firmware notes

Overview:

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.

Both the MX10 and the MX32 are on this page separately, since there can be some differences in the update procedures between the two. The MX32 is first since most of the functionality is there, and this is where the majority of the functions are accessed.

While some of this might be construed as negative, rememer that this is basically the most expensive DCC system made, and as such, is subject to a higher standard of quality and performance.

Click HERE to jump to the MX10 section following.

 

MX32 firmware updates:

My first updates were to version 15 or something, and the translators at Zimo confused the translation of the meaning of A and E.... normally A is execute, and E is our "escape" 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", but unless the release specifically states that the fonts are in the release, DO NOT do this. (Several of us have a "theory" that selecting this option on a release that does not include fonts actually wipes any existing fonts out). In any case, if you get the "tiny fonts" syndrome, load the last "fonts.zip" file... see my firmware list below to see which one for your release. N.B. 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.
  • (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.

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)

 

1.23.0001

My installation notes:

OK, so updating the MX10 is pretty standard, but the MX32 update is weird.... after plugging in the USB, the top item is in German and if you select it, it shows you a list of what's in the release... don't do this!

Instead, scroll down to "update found" and then to the line that says Execute.... Notice the "E" key is properly labelled "Escape", but the "A" key which should be labelled "Accept" is now labelled "Display" for some unknown reason.

Hit the "A" key, and hit it again on the next screen which likewise give you no direction.

the voltage and current limits are reset after the firmware update, you will need to readjust them all on the MX10.

New bug: updating switches (shift "W^") does not always work, in fact it normally does not work, any edits which must be saved with shift "W^" result in scrambled commands being sent to your accessory decoders, wrong addresses, and strange led behavior on the throttle, where 2 leds may come on from one button press.

Be sure save your changes, then shut down the throttle and reboot it.

 

Translation of general description of the release:

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.

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.

1.22.0150/0151

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

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!)

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.

Regards, Greg

 

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 - Works but unstable

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.

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

 

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

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.

 

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

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

 

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.

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

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. Extract the *.zsb file and make sure it is in the root of the flash drive.

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"

 

1.22.0001 - 2017.12.23

Installed ok, still testing. 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.

I want to start testing the JMRI compatability.

 

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

 

 

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

 

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

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

DO NOT INSTALL THIS YET, A LOT OF THINGS ARE BROKEN

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 -

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.

 

Weather Underground PWS KCACARLS78