pauliebanger

Peter, CV 111 regulates the emergency stop deceleration rate. The default value used to be 0 but I think this may have changed in more recent FW versions. Compare the values with those which work to your preference. Paul

Glad you found your solution. I'm a little surprised that it was such a high numbered random generator, but that's decided by whoever created the project. Whilst that CV can only be guaranteed to be correct for this specific project, the range of CVs to experiment with will remain the same, so anyone with similar problems with random sounds can follow the same procedure to find the relevant volume CV. Paul

Try using values within the range I suggested. (1-255). Value 0 is not a valid sound attenuation value so has the same effect as using 255, max volume. That is to say, the lowest volume is achieved with value 1 in the volume CVs. When you have established which CV changes the volume of the sound you wish to change, come back with it and I or someone will be able to tell you how disable this particular sound altogether if that's what you would prefer. Paul

This is often caused by a combination of sound level high with poor electrical path between track and decoder. Clean wheels, pickups and track and/ or try lower volume by reducing CV 266 to a value around 50. Paul

Hi Tim, I'll try to help but I don't know this loco or the sound project. I can make some educated suggestions. The decoder is a ZIMO MX645P16. This is identical to the P22 decoder hardware and software but has reduced access to some function outputs due to the reduced pin count. One of the loudest sounds on a steam loco is when the safety valves are lifted, so this may be the sound you are hearing. The random sounds aren't listed in the Roco docs, so you'll need to experiment. The random sounds can be adjusted with CVs in the range 744 to 767, but this covers 8 possible random generator slots. Assuming the slots have been filled lowest number first, try these volume CVs in this order - 745, 748, 751, 754, 757, 760, 763 and 766. You may need to cycle power to the model between each attempt before you hear any change, depending on your equipment. The valid value range for these CVs is 1 to 255, lower value gives lower volume. Check out the existing values for these CVs and set lower values until you achieve your preferred level. Paul

Increase the value in CV282 to extend the duration of the loud chuffs. Or, increase the values in CVs 275 &276 to increase the volume of the quieter chuffs. Or use a mixture of the above. Paul

Hi Simon, You can avoid the issue you have by using F1 to start the sound before 1st movement and wait for the sound to settle into regular idling, as Southern Mafia suggested above. Note, if you follow my suggestions below this will only need to be done once per session. To have the sound off when not in use engage F 8, mute. When you wish to drive away, disengage F 8 the idling sound will fade in and the model can be driven immediately. If you prefer, drive off with mute still engaged, and disengage F 8 when it suits (great for tunnels or fiddle yards). In this case the appropriate engine power sound will play, according to status. Or, engage F 8 before F 1. The start sequence will run, but won't be audible so this is like starting the loco in 'stealth mode'. After a few seconds, operate throttle and F 8 as above. Mute can be used to advantage in other ways and by avoiding the use of F 1 for temporary sound breaks you will avoid inadvertently triggering an inappropriate freeze on motor movement. When entering tunnels, fiddle yard or just to stop the sound for any reason, engage F 8 to mute and it will be good to go as above. When the session is over for that loco, disengage F 1 to hear the shutdown sequence, or just turn power off. The increased complexity in sound projects is driven by requests from modellers for more features and greater realism, and manufacturers wishing to provide more 'added value' to compensate for the high cost of sound equipped models. This project can be simplified by CV837 = 1. In this case, only the F 2 brake key will inhibit movement. To get all complex features back again, CV837 = 0. Paul.

Though not very clear, it looks very much like a ZIMO MX644. The low volume may be the setting in CV266 but it could also be the way the speaker has been installed. Paul

Hi Dave, Not your sort of I know, but the facility to simulate this is included in a number of Bachmann/ Farish steam loco models, incorporating the accompanying squealing brakes. The 'pinned brakes' feature can only be enabled if the loco is stationary and disabled (at the foot of the gradient) also when stationary, when brakes are unpinned/released. Also, can't be enabled if in Light Engine mode, because that would just be silly! Lol Paul

A great explanation of inertia control by decoders on DCC and what useful effect that has. However, I would expect a factory sound fitted model sold as ' will operate on DC' to have CVs 3 and 4 automatically disabled when operating on DC. This is indeed the case with the Bachmann Class 150. (CV14 bit 6). Paul

Read the value in CV273 on the sound decoder. Enter this value at CV273 on the non sound decoder. You will also need to match CVs 3,4,5 and 6. Plus, you may need to add manual brakes. CVs 309 and 349 Paul

The last thing to do with a sound decoder is to reset to factory settings, the results will almost certainly be wrong. It would definitely produce incorrect and unexpected results in the Victory sound project. Follow the above, CV 8=8 to reset to sound project defaults. BTW, CV 8 is a read only CV so will always have a retained value of 145 in the case of ZIMO decoders. Paul Some versions of Multi Maus may not be capable of addressing CVs above 255, I don't know. ZIMO anticipated this and created a pseudo programming routine to enable higher CVs to be addressable with DCC controllers that are restricted in this way. Paul

The answer lies in a full understanding of how this feature works with ZIMO decoders. When the regulator is closed or partially closed the chuffs are replaced with coasting/ drifting sounds until the newly selected speed step is reached. If the reduction is very small, coasting sounds soon give way to moderated chuffing. The duration can therefore be increased by maximizing CV4 and either continuously reducing regulator opening or set speed steps to zero. This in itself might be inconvenient for the layout or operator's needs, so it is also possible to attach additional duration so that the reversion to chuffing is delayed beyond the point at which the new speed is attained. The value in CV 285 sets this additional duration, each unit equals 1/10 second, so value 20 will extend the coasting duration by 2 seconds. Each of the above options can be used concurrently so almost any scenario can be simulated. Paul I should add that whatever methods are employed to achieve coasting, the sound will immediately change to acceleration chuffing if at any time the regulator setting is increased.

Hi Jim, You're not going to be able to fix this without an MXULF, sorry. Either this is not the PI supplied decoder or the decoder firmware/sound project is corrupted. The CVs you show above 105, 106 and 255 are identifiers for the sound project and should be 23, 32 and 3 respectively. Also, CV29 should be value 7 not 14. They should all default to these values on successful reset so something is not right. I don't immediately recognise the whooshing sound demonstrated but it's definitely not the ejector sound which is on F19 in the project. Provided there's no damage to the decoder it should be an easy fix if you have access to an MXULF. Otherwise it's back to base to get sorted. (Sending the decoder alone should be fine). Best regards Paul

I suspect these may be the result of poor track to decoder connection. With any Next18 equipped model, after dirty wheels, track, contacts have been sorted, check that the decoder is seated correctly. The interface is small and it's possible to have the decoder inserted but not fully home as some rocking is possible. Looking from below you may be able to see if the decoder is parallel with the loco PCB. The model and sound will operate for testing without the body fitted, so 'body off' is the best way to check. If you successfully reset CV8 = 8, all will be as delivered and sound will operate when F1 is engaged. Inertia, brakes and all special features will be restored. You may need several attempts at resetting, try both POM and Service Mode programming. Poor decoder seating may give only partial reset. If still no success, read and post here the values in CVs 29, 105, 106, 254 and 255. Paul

If Albie is correct with the diagnosis, you should be able to use standard ZIMO CVs to either reduce volume level or remove the sound semi-permanently. Read CVs 575 and 576 and note the existing values (so you can undo the change if needed, though a reset will achieve the same undo) Then make: CV575=0 Will remove direction change sound Or CV576=1 will reduce volume to lowest level. Note, not 0 as this will give full volume! Paul

Many sound projects already have a down volume key and an up volume key, depends what Dapol specified. Mine usually have these on F 27 and F28 respectively. CV 395 sets max volume. Don't exceed 120 here. CV396 = 27 CV397 = 28 Sets the F keys You'll need to remove what is already on you chosen keys as they will still be active otherwise. Paul

The master volume CV on all ZIMO sound decoders is CV266. Typical value is around 64, useful up to say 120 but maybe some distortion. Paul

Temporary off, use F key 5 Semi-permanently disabled CV837 = 4 Paul

I should do. Lol CV 309 sets the operating key (default value 2) If the value is zero, the feature is not enabled. CV 349 sets the brake force, but if not enabled this value has no effect so can be left as is. This is also related to the value in CV 4 (momentum), which you will probably prefer to reduce to a much lower value and use your automation software control deceleration. Good luck, Paul.

Hi, Do you mean you operate manually but via a PC based cab? Or via PC automation software? The manual brake feature is set up for manual operation by default. As it's a progressive force, the way the control key is operated has a profound effect on the braking 'force' applied. The optimal way to operate is with momentary action on the brake key (F2) when an infinite variation on brake force can be produced by judicial use of the key. If using automation software, you may prefer to turn this feature off and use the auto program to set deceleration rates and braking distances. Note. The brake force is also automatically increased when in light engine mode, (F17), so a fixed duration will result in more rapid deceleration. Which is what you should expect given the reduced rolling mass. Paul

Have a serious look at what the various decoder brands offer. For versatility, ZIMO decoders are hard to beat. You would be able to set the decoder to slow down to a specified speed rather than slow to a halt. As this would be a decoder feature any recognisable trigger device could be used. Paul.

And, as I pointed out earlier, a rotating trigger mechanism is the route to perfect sync. For quality decoders, the approximation can be very close, but every model/motor/geartrain combination requires individual tweaking for optimisation, which few users seem to tackle. But, how wheel rotation is measured or calculated is not the issue with Hornby decoders. They have a perfectly reasonable BEMF measurement scheme but the basic software architecture actively prevents its use to provide continuously varying chuff rates absolutely necessary for any chuff/rotation sync. Bluntly, to make a silk purse one should start with some silk, not a pig's ear. Paul It's no more difficult to achieve 8 beats than 4 or 2 just that there are only a handful of UK mainline locos for which this would be correct. Wheel/chuff synchronisation is more common in 0 gauge and larger scales where exposed axels can carry a sync disc* or similar. Most decoder brands have the facility to use internal or external chuff triggers. * See EDM models website.

As far as I know, only Hornby have used this method for exhaust sounds (chuffs). It is, in effect the same way that diesel projects are usually constructed. All other sound decoders have a number of different individual chuffs, recorded under different conditions and speeds. The decoder then selects which of these to play, for how long and with what duration since the last individual chuff was played. So the decoder assembles the chuff sequences IN REAL TIME and plays the accordingly. By measuring motor rotation and internal calculations the rate can be adjusted to match wheel rotation. This is pretty close to sync chuffs with wheel rotation if the user/operator spends the effort to match these using the CVs provided. Some brands are better than others in this respect. No prizes for guessing my preference. For absolute sync at all speeds, a mechanical/electronic/optical trigger needs to be fitted to provide a pulse trigger 3/4/6/8 times per wheel revolution, depending upon the number of cylinders on the prototype. Real time calculations require a powerful processor on the decoder, maybe the Hornby spec is not up to the job? I've no idea why the original decision to abandon all hope of synchronising chuffs to wheel rotation was taken, but it means that until Hornby fundamentally change their approach, it will remain impossible to achieve sync, except like a broken watch shows the correct time twice a day, for lucky coincidence at certain road speeds. Paul

Try these CV changes 433=1 435=2 437=29 438=4 439=0 440=4 441=0 442=19 443=3 444=3 446=3 This should give F key 0=directional lighting F key 10=Shunting lighting (all on) F key 19=Cab light Paul