开云体育

I may lock this topic, since I want Zimo to read this and perhaps we can refine it over time. The goal is a list of tests to try to stop the seemingly never-ending "add a feature, break a feature" note all tests (except radio only) need to be bus-connected and wireless 1. Test for basic Radio response * look for gross lags in response * intermittent response, may not be radio * Put F2 (or whatever the horn is controlled with) to momentary and press repeatedly * #### Broken after 1.29.0415 ###### 2. Test service mode * test identify (TP key) * test that RailCom decoder is recognized 3. Test consisting * create consist from LoRcl * use at least 3 locos * check for one loco running in reversed direction (like US F series diesels) * Store to data base * check that other cabs can access as a real consist (not just one loco of the consist) * check that the consist number shows in other throttles * check that you can take over a consist from other throttles (more to come)

I just updated the software on my MS950 to 4.250 and it fried the decoder. Decoder had been working funny (A lot of the MS950s for me). The train will run and then all of a sudden the decoder will not respond to speed commands. Sometimes it happens when it is running and sometimes it happens when I try to start it up. Sound and light functions work, just no engine movement. If I reset the decoder with CV8 sometimes it will start working back again. I thought it was a software issue hence the upgrade to 4.250. I have been trying a few new items lately which may or may not affect the loss of speed control. I have recently set CV#57 to 60 as a way to limit the speed of the locomotives when my grandchildren run them. I have also begun utilizing the new script commands to change the sound volume to off, full, and half volume. None of these I felt should have caused any problems. Last night I updated my decoder in the Percy engine without taking it out of the engine. The speed control had stopped working but I did a CV8 rest using the MXULF and everything was working again. I then attempted to upgrade to 4.250 using the MXULF connected via the track and it did not even get to the clearing the flash, all of a sudden I smelled a burning sound and the MXULF shut down. I tried the train on the track and it was showing a short. I opened it up put the MS950 directly on the MXULF via the MSTAPG and it showed shorted. I just updated another MS950 on the MXULF via the MSTAPG and it updated fine. Not sure why the other MS950 fried. Hopefully it was just a weak circuit on the board. I will send it back to Zimo for warranty repair but it always takes so long to get it back that I hate doing that. Michael Carney G-Scale layouts

Gentlemen..... I have two engines set for DCC-only operation. DC is ignored. One engine has a Zimo decoder, the other Soundtraxx. When attempting to enable DC operation, the Soundtraxx decoder did the job without difficulty and now runs well on DC. The Zimo decoder, however, will not operate on DC at all. No motor movement or lights or anything with DC. But it continues to run well on DCC. I am wondering if there is a CV which I overlooked? Or, perhaps the decoder is bad? Or what? Would anyone have any suggestions? Thank you very much........Ed Loizeaux

anything beyond 1.29.0600 breaks service mode programing and identification

another waste of 1/2 hour. Consists cannot be created or deleted or modified, I did not bother to test if this has the same bug where the consist does not control all locos. Back to 1.29.0415

listed as 1.30.0002 on the site. MX10 is 1.30.0002 MX32 is 1.30.0004 RF response messed up yet again. I did not thoroughly test the 1.29.0600 but the bug is there, but 1.29.0415 works fine: Basically, I set F2 to momentary, to blow horn... pressing repeatedly shows led gets out of sync and horn often sticks on. I was told this is an old bug. BullS**t, new bug, completely unacceptable behavior. Also new unwanted bug, I leave the switch definitions in the 1, 2, 3, 4 mode... you set the default display mode but it did not stick. Paying attention, whenever you change display from switches to functions and back, you are back to the 1.0, 1.1, 1.2 numbering. Pressing and holding the shift key for about 1 second will leave it back, but of course it goes away again. Come on Zimo! You need to test this stuff before releasing and then fix what you break. Greg

this firmware still has the momentary issue when in wireless

I just installed this new release in my 2 wireless MX10/mx32fu systems. I only tried running an engine on my test track. No issues doing that.

There were some questions about the StEin Module, and the Man key and what it’s uses are on the Zimo system. the simple answer is the man key is an override key, to shift the control of a locomotive, from whatever is setup as automated control, via a track module and programing within the decoder. for example, if I have a decoder programed to stop, using ABC on an Asymmetrical DCC track segment, I can press the MAN key, to override that programing within the decoder. Ok, that’s great you might say, but you don’t use a Zimo system.. no problem, it’s very easy to assign the Manual override to any function key. You can use this in conjunction with your shunting key which then completely change the functional operation behavior of a locomotive. I want to sunt some cars around, on my automated system. The next fun term that Zimo likes to talk about, is Called by Zimo HLU this translates to Halt, Langsum and Ultralangsum, which basically means Stop, go slow, and go slower, this is an advanced from of ABC but was designed to work with Zimo Track modules such as the MX9. HLU is really neat, in that it actually works in conjunction with lights, turnout switches, and occupancy detection. However in the old days, when HLU was introduced you would need different track modules and different devices such as stationary decoders to control all of that. Enter the Stationary Equipment interface or, as spelled in American English, Stone module aka The StEin – this is the MX9 and all of the other stationary modules wrapped up into a single package. Allowing automation to be integrated using an XLM spread sheet loaded into the StEin while fully realizing and taking HLU in conjunction with railComm to the next level Allowing, the StEin to detect and identify a locomotives via it’s DCC address and then change the status of a light, or turnout interacting with that locomotive to tell it to Halt, go forward or reverse at a specified speed, if there is another locomotive in a occupying a section, it can change a light and tell other locomotives to wait or proceed slowly. So, this think is actually very exciting as far as automation goes. As Zimo releases new builds of firmware for the MX10 and StEin module more and more 3rd party software for automation becomes more viable. At present, however the StEin works primary either as a stand-alone module for automation or with the STP software Here’s an impromptu video showing the basic use of a StEin https://1drv.ms/u/s!Al3-KSpD64CYiMwUaNUwcReHagqHjg?e=ligbse regards Kristine McNary

buggy MX10 English menus I didn’t do anything special – I shifted the language to Deutsch - this gave me all the menu’s albeit in German I then ran the update for 1.29.0106 again After I waited for the minute of power down, and removing the USB I rebooted, then shifted the MX10 back to English The language setting is normally under the MX10 Config – you are menus are garbled you’ll just have to push buttons until find it – it’s normally 5 down from the top MX32FU updates I saw this on my MX32 When you insert the USB into the MX32 and the menu comes up, you may need to select Update The StEin module the Menus and their naming has been wrong for a few builds, I believe this was just another example of the menus being wrong Other notes – If you are having issues with updates, and you constantly reuse the same thumb drive etc. it is advisable to format it, copy a fresh version of the update onto the thumb drive, then be nice and eject from the computer. As an overall view, I’m happy with the performance and functionality of Build 1.29.0106 I'll post more findings with using 3rd party software

There have been several reports on issues applying this update, on the MX32 and surprisingly the MX10. Until there is more (positive) experience, I would recommend staying at 1.28.0400 which I have installed on 2 mx10 and 3 MX32FU. Remember that you may have to re-install fonts and/or symbols... Here's my page I have worked on to explain and give a procedure for updating, including the symbol and font files https://elmassian.com/index.php/dcc/specific-manufacturers/zimo-dcc-equipment/zimo-mx10/zimo-firmware-notes If you find it can be improved, by all means email me suggestions ( greg@... ). Greg

I used to determine battery charge state by using E + 0 and then info/statistics. It's no longer there, anyone find it with the current software? I am trying the 1.28.0200 software now, but I have one unit that does not seem to charge like the others. Greg

Tried the new release, I always update the MX10 first. Unlike all other previous releases, this one does not present the single choice to update the MX10, but it gives a whole host of choices like radio update, font update, programmer update, etc. NONE of these work at all, nothing happens. Anyone get the same or different experience on this release? Greg

There are several bugs, both visual and operational in the MX10 system. Since these have been there since at least the 1.27.xxxx and persist in the 1.28.xxxx releases, I will post here. I want this thread to be only on these bugs, other bugs let's start a new topic, since we want Zimo to read this and understand clearly. The new 1.28.xxxx releases show voltage and current. The current is off by 1 to 2 amps. I run my system pretty hard, and have a train that at full speed draws over 7 amps, that means peaks/spikes can get pretty close to the 12 amps. The 1.28.0005, and especially the 1.28.0001 releases would trip regularly even at moderate speeds. To be fair, this is a 7 locomotive consist, USA Trains F3's which have very high motor stall current, so they clearly can spike the current requirements. On the MX10, in English, the settings for max current are not in the boxes right and not in the right place on the screen. Zimo, this has been wrong for a long time, please fix! Also, in the current version, you can still set 12 amps for track 2. So when set for max current (12 amps) on track 1, I still get overloads. I put 2 separate RMS current reading meters on my track and got some numbers. The ranges are due to the train actually running, there are curves but this is a mostly dead flat loop. Speed is indicated speed on speedo, max 120, Rampmeter is the famous DCC specialities DCC RMS meter, and Merterk is an AC RMS clamp on meter, inexpensive and not as accurate Speed Zimo Rampmeter Meterk 60 4.51 3.4-3.7 2.7-3.11 80 6.73 4.3-4.4 3.5-3.8 100 7.4 6.1 4.7-5 120 8.5 6.7-7.4 5-6 So if nothing else, Zimo needs to give us the ability to calibrate the number, especially since I am sure the Zimo number is used to calculate going into overload. Greg

I installed this update in my MX10 and MX32FU (2nd unit) and ran an engine. I also saved the info from my other MX32 (1st system) and installed it in this one. No problems with just running an engine and looking at the engines I copied from the other system. Went ahead and did the other system (1st), experienced no issues but have not tried to run anything yet with this system.

Hello Group. I started this conversation late last year and stopped for the io conversion. I have an Athearn EMD 40 with a MX660 decoder. I want to hook up 2 sugar cube speakers. They are 8 ohm .5 W each. The sounds are fine on a standard 8 ohm Should I hook up the sugar cubes in series or parallel? Thanks, Lou

Just loading into my system today. I noticed that several throttles (I have 3) still had old consists in them after the update, and some were still consist #0, supposedly illegal, only consists 1-9 are supported. I deleted all the LoRcl locos in each throttle, except of course loco # 1 I proceeded to go to the MX10 database and delete all the locos I could find, except of course 16382, the reserved loco # for new locos (read the manual) One throttle, my #2 after updating did not have all 9 symbols when hitting the E key, reloading the symbol library fixed it The LoR button has been mislabeled on the main screen to RoL, but reverts to LoR when in the memory... (how do you screw that up?) I continued to try to delete the locos from the MX10, (E+6) especially since it still listed several consists. The TP button, when modifying consists, the A key is still in german, but was in english before, again, how do you screw this up if it was in English last time.

Since we now have the original Zimo Yahoo group migrated, I am reserving this group for discussion and listing of current firmware versions, features, workarounds and bugs. I have renamed this group as "Zimo-Buglist" as opposed to the more general "Zimo-DCC" group, which also exists. This group, Zimo-Buglist will be primarily targeted at the MX10 / MX32 products, which are still evolving and missing basic functionality. Posts on the programmers and decoder firmware are also welcome. What is not welcome is general discussions on Zimo, basic programming, whether or not we are bad guys for documenting bugs, etc. Posts like that will be deleted, and if it continues, users will be removed from the group. Feel free to leave this group if this area is not your interest, as this is for a very specific and complex purpose. I had intended making the bug list and documentation a sub group of the main Zimo group, but it appears that this would incur a yearly cost and the administration of access just got too complex also. Regards, Greg