Locomotive Speed Matching Made Easy
Jim Betz, a retired from "IT" model railroader, makes Speed Matching much easier with his step by step detailed instructions. Thanks Jim!
The objective here is to get your locos to run in a consist - and have them all going at the same speed - i.e. to avoid having one or more of them becoming a “rail grinder” because the motor is running faster than the other(s). The following procedure will allow you to speed match them very well – and after you have done one or two of them you will be able to speed match your locomotives - in far less time that it will take you to read this document. Take a few minutes to read thru this one time, then take it with you to the layout and do the first one or two using it as a guide … and then “go for it”.
The basic approach is to get them speed matched first at the low end (slowest speed), then at the top end (fastest), and finally in the middle. Quite often you will be able to do this on the first pass – once in a while you might need to ‘go back and fine tune’. If you are speed matching highly similar locomotives – such as two Stewart FTs with the same decoder in each one – it is usually very easy. If the locomotives or the decoders (or both) are different then it can take more time – but it is still possible and even relatively easy. And the more times you do this the better you will get at doing it. Practice makes perfect.
I am going to assume certain ‘givens’ in the following … first that you are familiar with and using DecoderPro and second that there aren’t any problems in the drives of the locos such as a loco that has a ‘bind’ in the drive and won’t run well. You don’t –have- to use DecoderPro to use this procedure … but it does make it a lot easier and faster.
- Use DecoderPro to read all CVs and create a roster entry for both/all locomotives. If you aren’t using DecoderPro then read and record all of the relevant CVs (see below).
- OK - BEFORE - you start this exercise. CLEAN the Track -and- CLEAN the locomotive wheels. If you try to speed match locos with poor connectivity between the locos and the track it can quickly become an exercise in futility. Whatever track is used to test your speed matching should be "as immaculate as possible". (After they are properly speed matched you will even be able to use the way they run together as a measure of when you need to clean the track!)
- Turn OFF all momentum – it is the Motor sheet in DecoderPro and is aka CVs 3 and 4 – set both to zero in all locomotives you are going to match (you will put this back in later). Turn off BEMF if the decoders are not TCS or QSI. My experience is that you can leave the BEMF on for both of those brands. You may be able to leave it on for others – only you can judge this … later in the procedure.
- Set your throttle/command station and the decoder to run in 128 speed step mode. You can do this in 28 speed step mode … but it is a lot harder - most of the time. And locos that were speed matched in one mode won’t necessarily run well together in the other mode. Even if you normally run your layout in 28 step mode I recommend first matching them in 128 and then changing to 28 and “adjusting as necessary”. (I’m sorry I can’t tell you if this method will work for older 14 step mode decoders … I’ve never used a decoder that old!)
- Locomotives that were matched using the basic speed controls will not be matched if you change them to the speed tables. However you –can- match them with one using basic and the other using the speed tables. What you can’t do is to change them to a different motor control method after doing the speed matching. Similarly – if you are using a particular speed table method (user, or built in) then if you change the speed table … you have to redo the speed matching. You will find that if you have more than one locomotive using a pre-set speed table that you will have trouble matching them … so I recommend using “User Defined”.
- Set the top speed of both locos to 180 (VMax or CV 5 … or CV 94 of you are using the speed tables). If you are using the speed tables then use DecoderPro to do a “match ends” so that they have a straight line progression from the bottom to the top. I hear you asking “why 180?”. The particular number is arbitrary. What is important is that it –not- be 255 … because you need room to adjust one to the other. I have found that the speed increase above 180 is inconsequential … and that something close to 180 also provides a more realistic top speed. Some guys use a number that is as high as 225 – and I know one guy who uses something down around 150. I suggest you try first using my 180 and see if you like it.
- Get both/all locomotives running as good as you can get them to run at speed step one (SS1). This means that they should start moving at SS1 and move “smoothly and steadily”. It is not particularly important that you have them running at the slowest possible speed at SS1 … just that they are running at the speed you want them to at SS1. Do this one locomotive at a time. You are not trying to get them to run at the same speed at SS1 – just get them to run smoothly.
- Use a section of track on your layout that is 10 to 20 feet long – the longer the better … and if it is double track that is even better … whether or not it is on a grade doesn’t matter. And pick a section of track that you can see from where your DecoderPro computer is running so that you can use DecoderPro to make changes to the CVs.
- Consist the locos – but do not couple them to each other – and run them as SS1 to see which one is FASTEST at SS1. If any of them are sound locos this is a good time “Mute” them.
- Personally what I do is to use DecoderPro and before I go on to the following I bring up a DecoderPro entry for each of the locos – in Ops Mode – and use that to make all changes to the decoders. But I use a regular throttle to actually consist and run the locomotives during the speed matching. Using both of these ‘at the same time’ makes this quick and easy to do. The following becomes a repeated series of running the locos and observing them, making a change to the CVs using Ops Mode (and “Write Changes”), redoing the observing, etc., etc., etc. …until you get them running the way you want them to run in each phase.
Speed Match them at Speed Step 1
- Match the slower locomotive – at SS1 - to the fastest one. Change the Start Voltage (aka VMin or CV2 … or CV67 if you are using the speed tables) by adjusting it so that the Slower one matches the faster.
- Please note – in the prior phase we consisted the locos but didn’t couple them … you want to keep them that way in this step and all following steps - until you get to the “Final Verification” at the end.
- Keep running and adjusting until they match each other “perfectly”. Run them for at least 2 or 3 feet each time. Don’t pay any attention which one starts first – the goal here is to get them to run at the same speed at SS1 after they have “settled down”.
- When you have them running at the same speed – then reverse the direction and check that they run the same in both directions. If they do not run –very- close to each other in both directions you may have to use the “trim” CVs to adjust (CVs 66 and 95).
- Now run them up thru the first few speed steps – no more than as high as SS10 in 128 step mode and usually only up to about SS5 – and see that they match at all the lower speed steps.
- Repeat for additional locomotives if you are speed matching more than 2 locos. Although I will say that I usually do “one pair at a time” (check the end of this document for my thoughts on “fleet matching”).
Speed Match them at the Fastest Speed Step
- Depending upon your DCC system this will probably be either SS 100 or SS 128.
- Run the locos at the top speed and adjust the Faster one to match the Slower by using the Maximum Voltage (aka VMax or CV5 … or CV94 if you are using the speed tables). Again don’t pay attention to which one gets to its top speed first – you are trying to get them to run the same at their “steady state”.
- Check that they run at the same maximum speed in both directions and keep adjusting until they do. You may have to use the “trims”.
- If you are using the speed tables you can now use DecoderPro to redo the “match ends” so you have a straight line curve on both locos.
Speed Match them in the Middle
- Now that you have them running the same at the slowest speed and the top speed you need to match them “some where in the middle”. It is not important that you do this at exactly the mid point between SS1 and the top … anywhere close to that middle speed will work in my experience.
- Still consisted and still not coupled run both locos at the middle speed and change the faster one to match the slower. It actually doesn’t matter which loco you change or even if you change both of them. Use the Midpoint Voltage (aka VMid or CV6 … or CV80 if you are using the speed tables) to do this.
- Check both directions and adjust as necessary using the trims.
- If you are using the speed tables you can now use DecoderPro to create one straight line curve from the low to the middle and another one from the middle to the top (known as using ‘mid points’). Or you can just use the sliders to create a smooth curve. Making sure you leave the mid point where you set it!
- Now run them slowly up thru the full speed range to check that they are running the same speed thru out. This may involve first doing ‘the bottom half’ and then ‘the top half’ … depending upon how long the track is that you are using.
- What you are looking for is that they “track with each other” when you change the speed at a rate of about “1 click per every few seconds”. The rate you want to use is such that you can see that they have increased and settled down for each change. I’ve found that I can often do this by “stopping every 10 speed steps or so”. It doesn’t really matter how many speed steps between each stop you use.
- If there are any problems – if one is running faster/slower than the other – then go back thru the matching and adjust the speed ranges that need it.
Add back in the Momentum
- OK, now you get to add back in the momentum (CVs 3 and 4). Start by putting in what you normally use for each decoder brand you are matching.
- Run the locos at the slowest speed, the middle, and the top. Reverse them at each speed range and see that they coast to a stop and reverse ‘at the same time’ if you change direction while they are moving. A little bit of difference is usually not a problem. Adjust whichever one seems to have the amount of momentum you don’t like – i.e. match the one you don’t like the momentum on to the one you do.
Add back in the BEMF
- If you turned off the BEMF turn it back on now and see what happens. Many guys will tell you “you can’t use BEMF in consisted locomotives”. My own experience is that this is “only true for a few brands of decoders when matched to specific other decoders”. I have successfully matched TCS to TCS, TCS to QSI, QSI to QSI, TCS to Tsunami, QSI to Tsunami, and Tsunami to Tsunami … all with BEMF on!
- Some guys will leave the BEMF on in one loco and turn it off in all the others.
- If you are using BEMF “cut off” you will need to adjust them so that they cut off at the same speed step.
- This is a “your methods may vary” thing. You may find that you have to leave the BEMF off on all but one - or even all – of the locos in order to have them speed matched and running the way you want them to.
- Finally … couple them up (still consisted) and run them together. If any of them are sound put them on mute. Run them through the entire speed range. Run them in both directions.
- Look for “bucking” in the couplers. A certain amount of continuous/repeated slacking and stretching is OK (the slower/less frequent the better) … what you are looking for is not so much that they are “absolutely perfectly matched” as when they are “fighting each other”. Some guys refer to this as “surging” or “cogging”.
- LISTEN to them running (with sound muted). You should not hear any of them behaving like it is a rail grinder (spinning its wheels faster than the other). They should both/all be quiet thru out the speed range. If they are not properly matched you will not have any problem hearing it!
- Any problems in #2 or #3 means you need to go back and make adjustments. I usually do this “only for those speed ranges that need it”. You may find you have to turn off the BEMF - or you may not. You may or may not to readjust the momentum (usually not).
- Last but not least - save the updated DecoderPro roster entries with the final settings. Just to be absolutely certain - I often take the time to put them on the programming track and actually do a Read All Sheets before I save a roster entry … that way I know that what I saved is what is in the decoder.
Many guys just speed match sets of locos that will always be run together – by the individual set. Others have started to use a concept called “Fleeting”. By fleeting I’m referring to the practice of not only matching given sets of locos that will “always be run together” but also to the idea of wanting to “be able to run any loco with any other” – or any loco in a given class with any other.
There are two basic approaches to this – choose yours. Some guys want all the locos on their layout to be able to be consisted with any other loco. Other guys will divide their locos into classes and only match “within a class”. Examples of some classes that some guys use are Switchers, Road Switchers, Road Power, Steam Switchers, Heavy Steam, Logging Locos, 1st Generation -vs- 2nd Generation, by Make and Model, etc., etc., etc. – there are far too many variations on this theme to list them all but you get the idea. My recommendation is that you do “what makes sense for your layout”. Some of the clubs out there have their own methods of dividing up the locos into classes.
If you have divided up your locos into “speed classes” then you will not only have to match them “two at a time” but also “all the locos in the class”. This is usually done one locomotive at a time using the basics above – but note that when picking the slowest or fastest loco you need to pick the slowest or fastest loco in a speed class and match all the others to that one. Quite often you will end up using one loco for the standard for the ‘slowest’ - and a different loco for the ‘fastest’.
A special case of fleeting is when you are doing a group of locos such as an ABBA set of Fs – usually that will always be run together. Many guys choose to use the same DCC address for all locos in a consist of this type – if you are going to do that it is easier if you speed match them first with separate addresses … and then set the addresses when the speed matching is complete. When I do an ABBA set what I often prefer to do is to first get two of them matched, then match the third to those two, and finally match the fourth to the first three. By that I mean that I keep the ones that have already been matched consisted and coupled together and speed match the additional ones to them.
If they are going to have the same DCC address I will even change each one to the final address when it is speed matched so that I’m always working towards the final consist and checking it as I go.
Some guys are using ‘actual scale speed’ to match their locos. They purchase a device such as the one made by TrainSpeed and use that - or use some other method of measuring scale miles per hour and, usually in combination with the speed tables, set up their locos so that if the throttle is set to “30” then the loco runs at 30 smph (and the rest of the speeds as well). Some even adjust the top speed of the loco to match the prototype.
Personally I am not a fan of this approach. First, it takes a lot longer to do than the method I described above. More importantly, I’m just one of those guys who prefers to use the throttle to set the speed I want the train to be running at … by looking at it. I slow the train down some when climbing a grade, let it speed up first and then back off when starting down a grade, make adjustments based upon how long the train is, come to a stop just before coupling and then make the final move to couple, etc., etc., etc.
Again … this is one of those things you need to make your own decision about.
- Jim Betz (July 2010)
Using Quantum Programmer for programming on the main with an NCE DB3 Booster.
This is a confirmation of the results posted by Paul Turvill who used a Digitrax DB150 booster for speed matching.
We connected the QSI Programmer up to the NCE DB3A booster and ran an engine. We then followed the directions in the Paul Turvill's article and we were easily able to program speed changes while the engine was moving. We used some old track which we vacuumed but did not clean. Everything ran fine.
To be clear, we programmed totally bogus speed points - 1, 2, 60 - just so we could clearly see a difference. With the engine creeping along on notch 2, we programmed notch 2 to 60. When we hit Program, the engine took off like a shot! We did the reverse, and the engine went from careening down the track to a slow shuffle. It appears to work fine. So programming on the main while in motion using the Quantum Programmer and a DCC booster is confirmed and is a very useful speed matching tool.
Having said all that, you MUST set up the QSI Programmer (and decoder) properly. You need to set CV29, CV25 and CV56.4 (for QSI decoders) to tell the decoder to use the speed table. The QSI CV Manager has warning messages telling you to do this, so it is not hidden.