pauliebanger

ok

No, they have fitted these speaker connections to other models. I find them frustrating. Heljan don't normally supply the required plugs to fit, so the socket is often more of a hinderance than an asset. A pair of solder pads would be easier to access. Paul

ZIMO Brake Key feature: There is no problem that I am aware of with the latest MS firmware regarding the Brake Key feature - works fine on my models. CV390 = 20 is just wrong. This will produce a very strong change in Light Engine mode (see below) automatically creating a very sharp braking effect in this mode. Value of 100 or more is required. CV309 sets the Function key for the manual brake. (typically F key 2, but could be any) CV349 sets the 'efficiency' of the brake. Low numbers give harder braking. There is no need (and no separate way) to set different braking force for Light Engine as this is one of the functions of this mode. You can, however, adjust the global effect of this mode. CV390 sets a 'factor' of CV3 and CV4 when 'Solo' or 'Light Engine' mode is engaged, automatically changing the inertia/momentum simulation to match this mode. Low values temporarily reduce CV3 and CV4 significantly, high values give a less dramatically different effect. Since the braking force (CV349) is a factor of the current CV4, if Light Engine mode is engaged, CV4 will be reduced and a similar factor of a reduced figure will consequently be lower too. For after market purposes, the value in CV390 is usually set to a reasonable starting point, useful in a range of models in which this project might be fitted. Models have different characteristics from each other, and individual users will have their own special requirements. eg. on small point to point layouts, with slow running, a high value in CV390 may be better whilst on a high speed a med to low value may give a more realistic effect. A good starting point for this will be CV390 = 100 In the case of projects for R-T-R sound fitted models, the values in each of the above CVs will be decided by the manufacturer. But of course, these can still be customised as above to suit individuals' and layouts' needs. The way you operate this feature has a big impact on the results. So the following gives explanations and advice which some may find helpful. The braking simulation on these decoders is quite sophisticated, with several physical criteria modelled into the algorithm to simulate a closely as possible real llife characteristics. It's not a simple switch between CV4 values (As the designer of this feature, I can vouch). How realistic the braking simulation appears can also be heavily influenced by the way in which the Brake Key is operated. This is greatly assisted if the chosen operating key is set at 'momentary'. (available on most if not all DCC controllers at F key 2*, hence why I decided on this key as my default). The same considerations apply in either Heavy or Light Engine mode. The most important thing to remember is that the 'braking force' (CV349) is increased progressively over time. The feature only has an effect after the requested Speed Steps have been reduced. This can be to any slower speed (say for a speed restricted zone) or to zero. When the Brake Key is engaged, there is a short period, a few milliseconds, where there is no effect at all. This is to simulate the lag between the driver applying the brake and the brake mechanism starting to 'bite'. You can see, therefore, that a very quick 'dab' on the Brake Key will only produce a short brake application sound. (also possible if Brake Key is applied without reducing throttle beforehand). If the Brake Key is continously engaged (or latched, see later) the apparent brake force is applied exponentially. Retardation begins slowly but quickly increases in intensity so that eventually the road speed matches the requested speed steps (throttle position). In real life this would normally only be used for Emergency Braking. More typical use in fully manually controlled braking will be to throttle down and use a blend of gradual deceleration (coasting) and speed trimming using the brakes in short or longer applications to achieve the desired road speed. If the Brake Key is engaged for similar variable durations, the brake effect only happens during application time. Each release will reset the brake application sound and the brake force value is returned to it's starting position. (and coasting will continue as assigned but at the new speed). In simple terms, 3 dabs each of 0.5 seconds duration will not slow the model's road speed by the same amount as 1 application of 1.5 seconds. This allows the user full control to vary the simulation to suit different conditions. *Special note for PowerCab users. On these handsets, the F2 key is always 'latched', so if you use the button labelled '2' for braking, you will have to press once to engage and again to disengage. This is not optimal, given what I have explained above. However, the button labelled Whistle/Horn operates whatever is assigned to F2 but in this case it is operated as a 'momentary' key. If you are not already doing so, my strong recommendation would be to use only the 'Whistle/Horn' button for manual brake applications. Best regards, Paul

That's OK. Go for the sound fitted. It's a great decoder, top sounds and there is some fancy trickery which makes use of the two independently powered firebox LEDs from which you will only get the full benefit with a sound decoder. One of these features is that with the firebox door opened (for firing) you get a steady glow when stationary, but the fire 'pulses' in brightness in sync with the chuffs simulating what happens in real life as air is drawn through the fire by the draught of the chimney. Anyone not using the factory fitted sound decoder in this model will not get this experience or that of related features........... Again, ask John G if he has a stay alive solution. (He has, I've seen it, lol). Best regards, Paul

My experience is that the Bachmann Double Fairlie is a good and reliable runner and with so many wheels on an extended wheelbase you should not need to fit a stay alive if you keep wheels and pick-ups clean and in good contact. However, stay alive caps can be fitted if you wish. Note that it is not a simple task for several reasons. The loco PCB is not equipped with break out pads for direct connection of stay alive or indeed any feature not already fitted to the r-t-r model. There is not a great deal of free space in usable proportions to accomodate the stay alive capacitors. I would not recommend this as your first attempt at diy fitting as the loco PCB may need to be discarded and a Next18 adapter (which will come with breakout pads for all function outpts available from the decoder) fitted instead. Changing the decoder will not help as all the above would still apply and there's no other sound decoder which will fit the model. John G at Digitrains has installed stay alives in several B. Double Fairlies (and added working lamps, flickering firebox and more) so he will be able to give you a full run down of what's required and how to do it. He'll be able to advise, supply the parts you need or to install them for you, give him a call. Best regards, Paul

Yes, but please post the values in CVs 105 - 110. In the meantime, what happens if you only have one cab light on, F10? When direction changed, do head code/tails go off? Paul

This used to be 'pinned'. Before you start. It is vital to know the current position before any remapping is undertaken, but is especially imortant with Swiss Mapping since there are so many possibilities, some with knock-on effects whcih you might not anticipate. No need to panic, though. CV8 = 8 will reset all CVs back to sound project defaults. There have been developments and extensions to SM since this was written, but the basic principles still apply. Someone may be able to advise you if we know from where the sound project originated and which version you have. Please also let us know the current values in CV105 to CV110. Best regards, Paul

Yes, mine arrived today and also runs in the opposite direction to that indicated by my controller on DCC. Simple fix, read CV 29. if the value is even (most likely), then add 1 to that value and write (program) the new value to CV29. If however, the existing value is an odd number, deduct 1 and write the new value to CV29. I've added a sound decoder so I'll probably post a video shortly. Best regards, Paul

Here's couple of chances to get even more exited. Not my conversion and not my video clips but the sound project is one I created. Decoder is ZIMO (of course) and for those following the discussion above, it has the progressive acting manual brake function enabled. So it stops as well as it goes. a little more, Best regards, Paul

Whilst this is partly true, it's by no means 'the whole truth'. Do all decoders support a shunting function? It's worth noting that the outcome when the shunt function is engaged differs between manufacturers. Some only reduce road speed to a half of throttle setting, others only reduce CV4 to zero or low values and fully featured types can affect both simultaneously. So the results will differ depending upon manufacturer. Whilst it is tue that a crude version of manual braking can be approximated by having a high momentum in CV4 and the shunting function (on those decoders which support this feature) to reduce the speed or momentum, this does not in any realistic way resemble how a brake force slows a loco (or any moving body) in real life. That is, a given brake force will have little retardation immediately, followed by a period of increasingly progressive retardation until maximum effect just prior to stopping. In the days before I instigated and developed with ZIMO their manual brake simulation (which is progressive - a hyperbolic curve if plotted on a graph) I used to recommend using either ZIMO sunting mode, which can be either speed reduction, momentum reduction or both combined, or 'light engine mode' which was another of my creations which could also cause a retardation effect (by reducing CV4 values). Bearing in mind that all of those features were able to be adjusted and calibrated by users to hone the brake simuation, I knew that a separate manual brake could be modelled to simulate real physical effects more closely. When introduced, the ZIMO manual brake feature allowed users to have both a realistic braking feature and a highly configurable shunt mode in one decoder. Seems a nonsense to me to restrict users to an 'either/or' choice. Only one of the reasons why ZIMO decoders are prefered by so many. Why spoil the ship for a ha'p'orth of tar? Lol

If your Zephyr has restricted access to high range CVs I suggest that you download and read the ZIMO small decoder manual. http://www.zimo.at/web2010/documents/MX-small-decoders_EN.pdf You'll find all sorts of useful things you didn't know ZIMO decoders could do. One of them is the way that ZIMO high CV numbers can be accessed by even very lowly equipped DCC systems, or those with acces to only a restricted range of CVs. Yep, ZIMO have already provided a way in which their decoders can interpret low CV numbers (below CV245 for example) as much higher ones ( CV345 or CV445). In the version of the manual I linked to above you will find the 'how to' at section 9 on page 70 For your convenience, here's what it says Special procedures for DCC systems with limited CV range: Configuration variables #266 to #500 are used for the selection and allocation of sound samples as well as other settings. Programming CVs in this range is no problem for high-level systems (such as the current ZIMO DCC systems) both in “service mode” or “operations mode”. There are however many DCC systems in use (some still in production) that can only access CVs up to #255 or even worse to #127 or CV #99. For such applications, ZIMO decoders offer an alternative way of reaching higher CVs via lower numbers. This is done with an initial “Pseudo-Programming” of CV #7 = 110 or = 120 or = 130 which increases the CV numbers about to be accessed by 100 or 200. For example: If programming CV #266 = 45 is not possible, programming CV #7 = 110 followed by CV #166 = 45 executes the desired programming of CV #266 = 45 or if neither CV #266 = 45 nor CV #166 = 45 is possible, programming CV #7 = 120 followed by CV #66 = 45 also leads to the result of CV #266 = 45. The initial CV #7 – “Pseudo-Programming” state – remains active for further programming (which means CV #267 is entered as #167, CV #300 as #200 and so on) until the decoder is powered down. ATTENTION: After re-booting the system, the “Pseudo-Programming” is lost, that is programming CV #166 is indeed accessing CV #166 again. See below to prevent this! The “Pseudo-Programing” can also be stopped without power interruption with CV #7 = 0 which means that the programming reverts back to the original CV #166. Using as an initial “Pseudo-Programming” CV #7 = 210 or 220 achieves the same results as above but remains active even after the system is powered down. This state can only be cancelled with CV #7 = 0, which is important to remember in order to program lower CVs again. Best regards, Paul

Ian, Open the regulators as far as you wish. The gearing of the model and the structure of the sound project will produce a (generous) approximation of scale FR maximum line speed* at max speed steps. *You can adjust this easily with CV57. Default is 40, lower gives lower max, higher values give faster top speeds. Best regards, Paul

I could be wrong but I'm not sure that's correct. On the ZIMO website, the MX616 family is included in the list (as are the majority of ZIMO decoder families) which support firmware capable of operating the manual braking feature, though it may not (most likely will not) be enabled by default. To add manual brakes to most ZIMO decoders, CV309 = X (where X is the F key you wish to use for the manual brake, in the case of F key 2, X = 2) To set brake force CV349 = Y (where Y represents the force desired, values of 5 - 10 being useful starting points). To see the effect, however, the momentum or deceleration value (in CV4) needs to be high, in the region of, say, 80 -120) Best regards, Paul

Is it a 21 pn decoder? If so, it could be a logic level output to a circuit requiring full power. Details of the model and decoder would help diagnosis. Best regards, Paul

Bob, Hold on, we've only just put this Bit 6 feature into MS software. It's not even covered in the English language instructions yet. Lol. Your issue with the J72 project is probably 'induced' by the sound project loaded. For me, the clue is in the project default, CV267 = 147. The ZIMO default for CV267 is 70. This is just a starting point but is usually in the right ball park for 00 gauge models with 4 exhaust beats (2 or4 cylinders) or 6 beats (for 3 cylinder engines). The user should then adjust this value in relation to the actual model to which the decoder is fitted. That much is widely known. However, if the loco is driven at a constant speed (typical 'set a speed step and let the model run' - often witnessed at exhibitions) the same 4 chuffs endlessly repeating begins to sound just that - artificially repetetive. In real life, there is an environment, wind, embankments, cuttings and so on which tend to distort the sound heard so although the sounds at the chimney may indeed remain the same, buy the time they reach an observer's ears, there is a variety of subtle and not so subtle random changes over time. That's why I would recommend when driving at constant speed, operators should vary the chuffs by increasing or decreasing speed by 1 step (of 128) which does not noticably alter road speed, but will change the sounds between Full Gear, Cut-Off, and Coasting. Additionally, the heavy/light mode key can be toggled to further vary the engine sounds played. Similar effects are available by using Speed Lock. One trick I've used in my steam projects for many years is to double the number of chuffs in each set from 4 to 8 for 2 and 4 cylinder locos. Whilst this then produces 8 different chuffs per revolution it's only valid for Lord Nelson Class locos and any which have reduction gearing. So. in order to reduce chuff rate to 4 per revolution, CV267 must be set at twice the value which would be needed if using only sets of 4 chuffs. This results in the first revolution playing the first 4 of the 8 provided and the second the next 4. Using 8 different chuff recordings helps to reduce the monotony in what is heard. If you couple this trick with my recomendations for throttle and mode variations, long runs of identical 4 chuff repetitions can be avoided, providing a better overall simulation of how real steams loco exhausts sound. CV267 = 147 looks to me like this technique has been deployed in this project. Here's the problem with my 'trick'. If the wheel/gearing relationship is widely different in a particular model from the 00 norms, it may not be possible to set Cv267 at a high enough value to reduce the chuff rate sufficiently. This can be true of kit/scratchbuilt models or those of a different gauge (0 gauge, say). You don't say what values you have tried or the model/gauge in which the decoder is deployed but if CV267 = 255 still results in a too high chuff rate, then the only remedy is to reblow the decoder with a sound project having only 4 chuffs per set to bring the value in CV267 within adjustable range. However, if you are happy with all the other aspects of the sound project, there's no need to move to a different project. Your supplier will need to make only one simple amendment to the base project to use 4 instead of 8 chuffs before reloading the same project and your chuff rate should be within the adjustable range of CV267. Unfortunately, this is one of the few parameters which are fixed during creation. Best regards, Paul

Dave, Your first point, well more or less in it's outcome. Strictly CV267 (and CV354, for compensation at very low speeds) ) is still the cuff rate setting CV, and will still have some impact. However, because MS 'counts' differently from MX, there may not be a high enough value to bring the resulting chuffs into a usable rate for s particular model. I'll add more detail later when I have time but the MS decoder software is not that which is loaded to MX decoders (it's far more powerful). Whilst not strictly accurate, you can consider that currently, MS decoders are running MX projects in an 'emulation mode'. Whilst most MX features have been retained in more or less the same form when running on MS decoders/software there are some fundamental differences in some areas. The way chuff rate is calculated is one of these areas, recently revealed. CV393 has been used for other features for some time, but the Bit 6 assigned feature (4x multiplyer) has been added to remedy the issue. I believe that when truly 'native' MS projects are possible, there will be no need for setting Bit 6 in CV393. But that's for the future...... Best regards, Paul

Dave, Maybe this will help. Some CVs just set the parameters for one thing only. This means that the full range 0 - 255 can be used to adjust this one thing. eg CV3 - inertia (or acceleration as it sometimes called). CV3 = 0 gives no inertia, CV3 = 128 gives high inertia (loco accererates slowly like a heavy train) CV3 = 255 maximum inertia. Other value in between produce greater or lesser inertia. Some other CVs are used to set parameters for multiple features. The most well known of these is CV29. Using just one CV for multiple items means that the whole range is not available for any of them, in fact it is usually a specific value which sets the parameter one way when included and another when not included in the total value written to that CV. To you and I these are are set decimal values for each feature e.g. 1, 4,16 and so on. These values represent each of the 8 bits available in each CV. As follows for ZIMO (some others use slightly different terms for the same thing, range Bit 1-Bit 8 instead, but lowest Bit always has an 'On' value of 1) Bit 0 Off = 0, On =1 Bit 1 Off = 0, On = 2 Bit 2 Off = 0, On = 4 Bit 3 Off = 0, On = 8 Bit 4 Off = 0, On = 16 Bit 5 Off = 0, On = 32 Bit 6 Off = 0, On = 64 Bit 7 Off = 0, On = 128 One decdes which Bit or multiple Bits are required (eg. by referencing the decoder manual), then one takes the 'On' value of each of the Bits required and adds these values up to a total. That total is then the correct value for that CV enabling all the features you require it to. In this case we know that CV393 Bit 6 needs to be 'On' for the '4 x chuff rate' feature to be enabled. (there are other features controlled by other Bits in this CV, but none of them are needed, so we can concentrate on Bit 6 alone) From the list above, you can see that for Bit 6 to be 'On' the you will need to but the decimal value 64 into CV 393. You don't need to know the Binary Maths behind this to enable CV393 Bit 6, you just programme CV393 = 64 as you would with any other change using your DCC controller, following the table above. Best regards, Paul

Hi Ian, F20 Shunt Mode There are two separate control manipulations enabled on the same F key to produce the shunt mode as provided in this model. (this is a combination of the earlier respondents' suggestions). That is, the road speed is reduced by half relative to the speed steps in the throttle, plus all inertia and momentum are removed giving more precise close control. The shunt key may be engaged at any time and the road speed will reduce, throttle control will be instant (like a DC model) and any engine sounds playing will automatically adjust to the changed conditions. F14 Light Engine Mode. When F14 is not engaged (Heavy Train Mode) the chuffs will be at maximum volume so long as the road speed is actually accelerating plus a few seconds when the desired speed is reached. (I'll call this cruising - maintaining speed) to smooth the effect. In broad terms, at this point, a real driver would reduce the steam entering the cylinders by using the reverser to 'cut off' early in the cycle to improve efficiency. Less steam pressure, less 'bark' in the exhaust so an observer would hear the exhaust 'soften'. That's what happens to the exhaust sounds (chuffs) in this loco - the timbre changes and the volume is reduced to simulate this effect. When F14 is engaged, a different set of chuffs is substituted, these represent a solo engine (or one with a very light train). Similarly, the chuffs begin quite strongly and then reduce automatically a few seconds after cruising speed is achieved. Additionally, engaging F14 temporarilly reduces the values in CVs3 and 4 so, as you observed, a light engine or train will accelerate and decelerate more quickly than a heavy train. Since that's what happens in real life - happy days!! This differs from F20 shunt mode in this project, since the road speed is not affected whilst inertia and momentum are only partially reduced, not reduced to zero. In fact, you can change the amount by which CVs 3 and 4 are reduced when F14 is engaged, by amending the value in CV 390. (But since someone has obviously already set the value to suit the loco and this model why would you?) F10 Speed Lock. Put simply, when engaged, the throttle no longer changes the road speed but instead now temporarilly controls the engine sounds. On a diesel electric or hydraulic loco, if F10 is engaged when standing (the loco, not you, LOL) the engine can be 'revved up' without the model moving but since a steam engine's chuffs are directly related to wheel rotation this would be wrong (and does not happen in this project) if F10 is engaged at standing. I mention this difference between steam and diesel because it helps to explain the changes to sound you can expect from each type also when F10 is engaged whilst the loco is moving. On diesels, the engine rev's can be increased or reduced manually by manipulating the throttle without resultant speed changes. On steam locos, the chuff rate is directly related to road speed, so chuffs (analagous to revs) must not be more or less frequent at a given road speed. So, the only impact which can be simulated is the change in volume and timbre of each chuff. Now, refer back to what I said about light and heavy train modes earlier. There are, in essence, 5 groups of engine sounds. F14 off - Heavy 'Full Gear', then Heavy 'Cut Off', F14 on - Light Full Gear. then Light 'Cut Off'. In either case, there is a coasting sound during deceleration. With F10 engaged during movement, reducing the throttle by a small amount (5 -10 speed steps out of '128') will revert chuffs to coasting sounds, whilst raising by a small amount will change either coasting or 'cut off' (whatever is currently playing) to 'full gear' within the same mode (light or heavy). Larger throttle changes in one go will instead also change between modes. Note that since F10 Speed Lock is engaged the variation in values in CVs 3 and 4 is not applied (acceleration or deceration are impossible, so inertia and momentum are not relevant. Which all goes to show that there's a lot going on in the background to try to simulate how a real loco operates and sounds by the automatic application of the laws of physics. Best regards, Paul BTW, that list seems to suggest that F2 (Manual Brake) gives only brake sounds but in reality as well as the application sounds, if the regulator is reduced beforehand that key also reduces the road speed in a progressive (hyperbolic) retardation effect, depending upon how long F2 is engaged. This allow a high value in CV4 for realistic coasting durations, whilst enabling reliable stopping in shorter durations. (The braking effect is automatically more rapid when F14 is engaged, too)

This information may not be correct in all cases. It will depend upon the sound project. Always best to view the information provided by the supplier, often in the list of functions or however it is described. The volume down and volume up adjustment can be assigned to any key. I began using F27 (CV396) and F28 (CV397) as the defaults in my sound projects for Digitrains based on the frequency of need to adjust overall volume. Other creators have since either followed this, or assigned the same keys based on the same logic, so it has become something of a de facto normal setting. But there are ZIMO sound projects (some of which were created by me) which use different keys for overall volume adjustment (or omit the feature altogether). Manufacturers' and commissioners' requirements vary. As Ray H correctly pointed out - 'some ZIMO decoders use F27 and F28' Any creator worth their salt will avoid inadvertantly triggering dangerously high volume levels by fixing a 'Max overall volume' available via the assigned 'increase key'. This is done by setting CV395 at a 'safe' value. Of course, any operator is able to increase the value in CV395 to dangerously high levels, or use the actual maximal overall volume CV, which on ZIMO is CV266 to over-rule project defaults. The mute control is also freely assignable. (CV 313). I mainly assign this to F19 (because when I started creating ZIMO sound projects, this was the highest value F key available) but any key assignment is possible. Indeed, some projects do not have the feature enabled at all. The SLW Class 24 does not have the mute function as F27 and F28 can adjust volume in real time and the project is so packed with manufacturer's required features that there was simply no free F key available for it. Best regards, Paul

Since the sound is correctly following the simulated changes in 'regulator' and 'cut-off' (reverser) position I would be surprised if there was a hardware fault with the decoder. To eliminate any unintentional CV changes, first job (because it's simple to do) would be to reset the decoder. Reset using CV8 = 8 will put all CVs (including address '3') to sound project defaults. This will put all back to the 'as supplied' state and may fix this issue or help diagnose where the fault lies. Best regards, Paul

Dave, Sounds to me like the decder was not engaged correctly in the Next 18 socket. If it is not exactly 90 degrees to the fittting the decoder may a) touch the loco PCB - so an intermediary insulating layer is an excellent idea (I'd probably fit it to the decoder) or b) make poor contact with the sockect connections along one side which can cause erratic motor operation. (or both a and b) When inserting the decoder you should feel a soft but obvious click when fully home. It's some time since I had the EP model in my possession but I'm sure the pads marked V+ and GND are where you should connect the stay alive positive and negative respectively. Enjoy your model, buddy. Best regards, Paul

John G at Digitrains has fitted firebox glow and working lamps to his own Bachmann Double Fairlie. The normal Digitrains sound project needed to be 'modified' to enable this and there was a a lot of work required to the model. Looks and sounds great. Best regards, Paul

Dave, Yes it would. Any solution which does not use the factory fitted decoder would present the same problem as it is impossible to transfer a sound project from one decoder to another, even those of the same type. Digitrains have a very similar Class 08 sound project for ZIMO decoders. Best regards, Paul

Tim, All ZIMO sound decoders have onboard stay alive capacitors as standard, some capable of running the motor for a few seconds of power distruption, others sufficient to maintain only the sound for a few milleseconds. The MX659N18 fitted to your model is one of the latter types. There is simply no room on the decoder to fit larger capacitors. The fitted decoder is, however, capable of operating an external stay alive capacitor if you wish to connect one. The issue is whether there is any free space available to accomodate the stay alive componets. This is a very small model indeed, and the MX659N18 was especially developed by ZIMO for Bachmann for their 'limited free space' models. The MS580N18 has a significant stay alive on board which can run the motor (at 5V) and sound for around 1 second, usually enough to clear dirt on the track. However, this decoder is 5mm longer than the MX659N18. This may not sound a lot, but it could be sufficient to prevent fitment - you should confirm this before any purchase decision. If you already have a sound fitted Farish 08 and you vae confirmed that the MS decoder will fit, you can simply remove the fitted decoder, replace with the MS580N18, and sell on the MX658N18 (currently in very short supply and highly sought after). Probably will not cost you much overall. Best regards, Paul

Hi Andy, You'll have to ask John at Youchoos about his DMU project. I created all the other projects for Digitrains, so I may be able to help further. I'll get back to you tomorrow. Best regards, Paul