pauliebanger

ZIMO sound decoders aimed at the H0/00 scale models (and single motor 0 gauge) are equipped with 10 Function Outputs as standard. To put that into context, a single ZIMO decoder can, without additional adapter boards, illuminate by individual control, 10 separate lamps or 10 separate pairs of lamps. So, they can save the need to find money and space for additional decoders which might be needed to boost the abilities of other brands. Controlling such a large number of individual features would normally occupy many F keys, which may be needed for other duties. To bring some order to this, ZIMO created a function mapping technique which is so powerful and flexible that anyone with a DCC controller and a bit of knowledge can set up without needing to know how the project was originally created or which Function Outputs (FOs) were assigned to what F keys by the author. ZIMO call this Swiss Mapping since it was originally developed to make it easy to create authentic lighting patterns for Swiss locomotives which can be complex. Unfortunately, the name and the example used to in the decoder manual illustrate the method serve more to confuse than enlighten. I have given some of this information in other treads, but it tends to become buried over time. The purpose of this thread, therefore, is to provide a single resource, where explanations of what Swiss Mapping can be used for and how to use it can be gathered. What Swiss Mapping (SM) cannot do is rewire your loco. To be able to control any individual function in isolation it must be wired to a separate FO. Provided that the correct wiring has been put in place, SM gives a quick and intuitive way to assign FOs to any F key. Crucially, this extends to allowing multiple FOs to be assigned to a single F key, or multiple F keys to control a single FO, or a mixture of these, whilst any or all of them may be direction dependant . SM is, therefore, able to group functions which should act together in a given set of conditions, to the same F key, but it can also use FOs from different groups to create new groups suitable for changed circumstances. By the nature of our models, this will be used largely for lighting effects, but there is actually no restriction on what the FO can control, so, for instance it could be used to assign a smoke generator to a favoured F key, or determine which F key controls the roof fan. To keep things simple to start with I will avoid illustrations using F key 0 and FOs for forward and rear headlamps. (I will introduce them later, though,as they may still be required). Also for clarity, I will assume SM is the sole method in use (in reality, all types can be used simultaneously if required) The basic concept is straightforward: A Swiss Mapping 'Group' consists of 6 consecutive CVs, the first of which is CV430. Each CV in the group has a specific role which, respectively, remains the same in every group. i.e. the third CV in each group holds the number of the first FO to operate in the forward direction of travel. A simple example will help comprehension, I think. Say you wish to control a smoke generator which is connected to F01 by using F key 21 and you wish it to operate when the model is travelling in either direction. SM Group 1 CV430 = 21 (the number of the F key which controls this group) CV431 = 0 (Not required here) CV432 = 1 (the number of the first FO to operate in the forward direction of travel) CV433 = 0 (the number of the second FO to operate in the forward direction of travel, if there is a second one required, otherwise enter 0) CV434 = 1 (the number of the first FO to operate in the rearward direction of travel) CV435 = 0 (the number of the second FO to operate in the rearward direction of travel, if there is a second one required, otherwise enter 0) To create such a group, all that is required is that you know the CVs in the group and their purpose, plus which FO is connected to the function you wish to control. Here's something a little more complex, but very commonly required. Often called 4 function lighting, it allows the tail lamps to be illuminated with the front markers when 'light engine', but to be extinguished when there are other vehicles on the hook. I'll use F key 21 again to operate the lights In this case, the markers at each end are connected as a pair to a single FO and so are the tail lamps. Assuming No1 end whites use FO1, reds use FO2, No2 end white FO3 and reds FO4. There are several ways that this can be done. Here's one way. SM Group 1 (White Marker Lamps) CV430 = 21 CV431 = 0 CV432 = 1 CV433 = 0 CV434 = 3 CV435 = 0 SM Group 2 (Red Tail Lamps) CV436 = 22 CV437 = 0 CV438 = 4 CV439 = 0 CV440 = 2 CV441 = 0 If F21 is engaged, white markers at the 'front' will be illuminated, direction dependant. If F22 is engaged, red tail lamps at the 'rear' will be illuminated, direction dependant. So,for light engine, engage F21 and F22. For a loco at the head of train (including coupled light engines), engage F21 only For a loco at the rear of a train (including coupled light engines), engage F22 only I'll give other examples, including the use of the second CV in each group, later. SM was introduced with SW V32.0 with 10 groups available. The number of groups available increased to 13* with SW V34, which also introduced the ability to assign 'Rule 17' speed dependant dimmed/high beam headlights. You can check your SW version by reading the value in CV7 with the sub-version at CV65. It remains perfectly feasable to mix SM and normal NMRA mapping or other ZIMO Extended Function Mapping methods. It is worth noting, however, that from SW V34 many of the ZIMO extended mapping methods have been dropped as being redundant. I believe CV61 = 97 is still operational if required. Kind regards, Paul *from software version V35.27, the number of groups has been further increased to 17 on sound decoders.

Thanks Guys, I was intrigued by Heljan's claim that it was 'designed to accept an ESU 6-pin Micro sound decoder' but I have been unable to find any design feature or modification to justify this claim. No special provision for the decoder, a channel for cab location without sufficient room to accomodate the wiring (as noted by Chris), and a circular depression in the floor when the ESU Micro comes with a 16 x 12mm speaker in an enclosure. They seem to have inadvertantly overlooked the advantages of a ZIMO MX648. Lol I now have a ZIMO solution up and running. I did not replace the Heljan wiring and I did not modify the body or chassis in any way but I did fit the decoder within the engine room and improve on the lighting control offered by Heljan. Kind regards, Paul

Sorry everyone, my mistake. My original post began with a misconception. ESU don't appear to offer a direct-plug 6 pin Lok Micro. The connector is at the end of a harness, so my arithmetic is irrelevant. This strongly suggests that the decoder is not intended to fit in the engine room with the DCC connector, but to go inside the cab with the speaker. Kind regards, Paul

Hi Matt, I just wondered if there was any corroboration of the Tower Models 'list price'. It's a very straightforward installation; see Hornby Magazine for a step by step guide. At retail prices, plug-in ZIMO MX 644D sound decoder from Digitrains, £80 (no extra charge for the sounds), speaker £8.50 Fitting time, 15 minutes. Kind regards, Paul

Did he mention the price? I can only find a list price for the sound fitted version at £399 shown on Tower models ('reduced' to £335). Seems a bit pricey as mine cost less than £260 all-in. Kind regards, Paul Edited to correct my arithmetic.

Here's a taster of Digitrains' Terrier sound project in a Dapol 0 Gauge Terrier. https://youtu.be/BUSx7Ox5izM Kind regards, Paul

Just got around to making a short video of my sound fitted terrier 'Brighton'. ZIMO sound decoder from Digitrains. https://youtu.be/BUSx7Ox5izM Kind regards, Paul

Hi Everyone, Heljan's instructions say that their recently released Hunslet Class 05 model was designed to accept a Loksound Micro with 6 pins. This suggests the decoder should be plugged directly into the socket provided in the upper part of the engine room. Has anyone succeded in fitting a 6 pin Loksound Micro to this model? The length of the allocated space is 33.5mm. The loco PCB is 18mm long and a Lok Micro is 25mm or a tad longer. That gives a minimum overall length of 43mm. How do I get 43mm into a space 33.5mm long? Do I have to take Heljan's suggestion with a pinch of salt or is there a way to make this combo fit, please? Will I need to make any 'modifications' to the model in order to do so? Any help will be much appreciated as Heljan's instructions are silent on this matter. Kind regards, Paul

Hi Everyone, Heljan's instructions say that the Hunslet Class 05 was designed to accept a Loksound Micro with 6 pins. Has anyone succeded in fitting a 6 pin Lok Micro? The length of the allocated space is 33.5mm. The loco PCB is 18mm long and a Lok Micro is 25mm or a tad longer. That gives a minimum overall length of 43mm. How do I get 43mm into a space 33.5mm long? Do I have to take Heljan's suggestion with a pinch of salt or is there a way to make this combo fit, please? Kind regards, Paul

Who do you think Digitrains asked? Lol In the meantime, I've taken the one out in my model and it now works perfectly. Seems the other issues were red herrings. I've also just received an official response from my friend at ZIMO that this is the most likely cause of the issue we have observed, and confirming that the decoder provides better suppression than chokes and capacitors so it's OK to remove them. I think this will solve the problem for you. Kind regards, Paul

Having slept on this (the problem, not the loco) I remembered that there is a 'bolt-on' RF suppressor added between the decoder and motor terminals. (It's actually soldered, of course). It is situated below the main PCB with the 21 pin connector and just 'floats' on a scrap of insulation. There are bare connections close to the edge of this mini PCB. Could this be moved when the motor is reversed, creating a short? Suppressors are not normally required with decoder equipped models. If my earlier suggestions do not help, you could try removing this and wiring direct to the motor from the relevant solder pads on the main PCB. ZIMO decoders aren't often upset by RF supressors, but I've known the odd model to cause problems, maybe this is another. Inany event, I plan to remove the one in my model when I have a minute or two. Kind regards, Paul

Chris, Yes you will have had, you've just not noticed it. The problem is with the implementation of the feature by NCE. It's nothing to do with the decoder, European or otherwise, it's about what the momentum button does to your decoder. There is a degree of compounding of the issue with ESU since they have decided to use a different multiplier than everyone else, all other European sound decoders follow the NMRA standards in this respect. This can cause problems if consisting, since different momentum settings can ensue. Some sound projects only work correctly when a large amount of inertia and momentum are set; having NCE calculate a value then write it to your decoder whn you press the Momentum Button causes unpredictability in the sound operation. However, it is easilly rectified when you know what causes it. Kind regards, Paul

Not sure where the fantasy reference comes from, I'm trying to help you. The relevance of that question is that it will help me to ascertain which version of the sound project you have. Summing up the facts; The loco runs fine on DC, so it's reasonable to assume the loco motion is mechanically OK. The decoder runs fine on the ESU tester,so there's no obvious fault here. You have made physical checks on the loco and the DCC connector and not found a problem. Despite this, when the decoder is fitted to the loco you experience intermittant stalling whilst the sound remains on, so power is getting to the decoder and poor contacts, dirty track etc are therefore not causing the stalling. The only cause I could think of was that the decoder was becoming overheated and it was shutting down power to the motor. When it cooled sufficiently, the power to the motor resumed until it overheated again and so on. If that's the case, the areas to investigate are; Does the decoder get excessively hot? Too hot to hold a finger against it, that is? You may have tried this, but you haven't said. Does the problem occur if operated with the sound is turned off? Does it happen when the firebox flicker is not operating? In my case, I was unable to check these last two separately as F key 1 started the sound and the firebox flicker simultaneously. I reassigned Function Output 1 to another key to investigate, and the problem disappeared. The question still remains, what caused the overheating? (In my model). I don't know. It appeared to me that with the firebox flicker on 'permanently' the problem was evident, but with it used intermittantly, ie triggered by the random sound, things work fine. Just a thought. Have you turned the sound up? If so, try setting the default value for this project, CV266 = 50. Kind regards, Paul

Digitrains, that is a good source. Lol Yes, I am. Mine exhibited the same issues, though the reason could be different. Sorry to have to ask another question, but which F key operates the Firebox Glow effect? Kind regards, Paul

Depends. Where did you get your decoder and sound project from?. Not all ZIMO sound projects are created equal. This is one of those curious effects where neither the decoder nor the loco are in any way faulty, but put them together and strange things happen.

Marc, It's not my place to tell you how to run your business, but you have asked for feedback....... This may sound obvious, and will probably not be what you wish to hear, but if the name of your business is creating a barrier to successful marketing, and you say you have many experiences which support that view, then maybe it would be worth changing it? You might be proud of your region and you may feel that after 15 years you have become 'attached' to the name, but you have to face facts. Potential customers are telling you they do not not even get past the name to see what you have to offer. You can fix that. You may find it more difficult to change peoples attitudes. Kind regards, Paul

The firebox flicker operates whenever there is enough power during analogue operation, but, although available at any time during DCC operation it is switchable so it can be turned off if you don't like it. On my model with a ZIMO MX644D decoder and my own custom sound project fitted, it operates only when the coal shovelling sound is playing. (on analogue or DCC). If it really offends, the module which produces the effect is a separate small PCB with a couple of SMD red LEDs to provide the flicker. Just disconnect this from the main PCB to prevent it operating in all circumstances. Kind regards, Paul

You are right about the decoder being helpful to all, having no wires and being mechanically suported by the connector. (povided you don't want access to other function outputs which the manufacturer has not provided on the PCB, in which case it can be more awkward to resolve). In truth, for many people, there may be no practical difference in the end result. It depends upon how many features the maufacturer includes as standard and how many additional items you might want to fit yourself to 'improve' the model. Whether in this particular model there would be any great advantages is, perhaps, moot. I was really thinking of models in general, though as Dapol announced that they would be the first to use PluX 22 and that this model would be one of them, I was disappointed that they had not chosen to lead the way. That said, I (personal opinion) feel that manufacturers should fit the most versatile system at the outset, even if they do not utilise all the functionality. It would cost pennies at the design/production stage, but be hugely helpful for people who wish to customise their model further down the line. The PluX 22 connector is part a complete package of design criteria intended to overcome all of the shortcomings of the 21pinMTC, (which itself has not been, implemented fully/correctly by any UK based manufacturer). The NEM 658 specifications stipulate the physical design of the decoder and connector and the space which manufacturers must provide for the decoder to occupy. This prevents the ridiculous situation reported many times on this forum, of a manufacturer providing a DCC socket which is all but impossible to use for lack of space, even for theirown brand decoders. PluX decoders have a different, more logical, pin-out arrangement with the index pin in the centre. This allows smaller PluX decoders to be used where there is no requirement for a high number of Function Outputs, thus giving the consumer more choice whist maintaining basic functionality. Ther is a range of possible types which can be used: PluX8, PluX12, PluX16 and PluX22 PluX specs allow for up to 9 Function Outputs, all 'normal' full power - none of your 'logic level only' for Function Outputs (Aux) higher than 3 rubbish of the 21MTC that was designed to pander to Maerklin requirements. (this is the reason why Loksound decoders require a separate amplifing circuit or an additional adapter board to be able to use Aux 3 and Aux 4 on their 21MTC versions). In the PluX system, the decoders have the pins, not the loco connector as in 21MTC so there is no possibility of using the wrong type. The PluX decoder can only be fitted in the correct orientation, unlike a 21MTC which can be fitted, usually fatally, incorrectly. From a personal perspective as a ZIMO user, the stay-alive management circuit of a ZIMO MX645P (PluX 22) can cope as standard with a greater range of capacitor types and values than the MX644D (21MTC) - though to be fair what the MX644D has on-board is already superior to many other brands in this respect. So my post was made in sadness at an opportunity lost rather than as a serious criticism of this model, which I've already said I love. I suppose that as long as maufacturers can get by with providing just enough to make it work correctly as delivered, they will. Kind regards, Paul

It would have been more helpful if Dapol had fitted the PluX 22 connector they originally announced, or at least provided traces on the PCB to the unused (by Dapol) pins. Kind regards, Paul

Yes; current draw is around 150 - 250mA. Stall current I measured at 760 mA. On the basis that Dapol have fitted a 21 pin connector, and there's not enough space for a large scale decoder anyway, I think you can be reassured that a 00 decoder (whatever that is) will be fine. In fact, for the hell of it, I've run mine on an MX648, ZIMO's miniature sound decoder which is small enough for most N gauge models. Paul

Don't know about Dapol, but the one available from Digitrains (probably less expensive but the same decoder, ZIMO MX644D) definitely has exhaust beats recorded from a Terrier. Kind regards, Paul

Pete, You gone very quiet. Stop playing and fix that tap! Paul

My Brighton arrived yesterday morning, sound fitted by lunchtime. Quite an easy job, but the included speaker enclosure is the usual joke attempt - it has two huge holes which reduce it to 'cradle' staus rather then an enclosure. No sweat, fitted something better. The packaging from Hattons was good and showed no signs of damage. The Dapol box is unmarked externally. When I lifted the lid, the loco was at a 'jaunty angle' within the plastic insert. When I removed the loco, the reason for this was clear. The tray supporting the loco, similar to 00 gauge current practice, was broken. The mass of the loco, or the momentum when it may have been dropped, was too high for the packaging to remain intact. However, the loco was undamaged and nothing had fallen off. So, apart from not being able to re-box it satisfactorily, it can be said that the packaging worked. It's a shame that Dapol did not make provision for a PluX22 decoder as originally announced and have not provided traces on the loco PCB to access all the Function Outputs available on the decoder. These things are easily sorted at the design stage and cost a few pence only. This would save modellers' time, effort and apprehension in having to rectify this later. All this might seem a bit negative, but my overall experience is one of joy. The model is delightful, even my long suffering wife said so. There may be faults in certain authenticity aspects that experts will spot, but for me it is a triumph. A great loco in an iconic livery which runs very well and is very easy to fit DCC and straightforward to instal sound. With my own sound project on a ZIMO MX644D, the price of the loco and postage, the total cost came in at around £240. For an 0 gauge sound-fitted model. That would give many 00 gauge models a run for their money. Can't wait for the Minerva Peckett now. Kind regards, Paul

Another Topic, maybe?

Perhaps it needs more tuning?