Speed Matching Locomotives
Summary: By matching speed between locomotives, consisting can be done easily without introducing problems
See the Video.
The goal: With the same throttle setting, each locomotive should travel the same speed (or the same distance at the same time). Think of method as distance/time matching rather than speed matching.
- Also read the article on Back-EMF for more details.
Read your documentation for the decoder as well, as it may have advice on speed matching, plus CVs needed. CV29 enables the speed table, if available.
This method involves running locomotives on a long section of track and timing how long a locomotive takes to travel that distance. For N scale, you'll need 15-20 feet, you'll have to adjust this method to your scale. Measure out a known distance on your layout, the longer the better. You'll also need a stopwatch. If you have a straight double track section this can be helpful as well. Clean the track and wheels beforehand to eliminate any pickup issues.
Ideally a double tracked section of mainline can be used to compare two locomotives simultaneously.
With this method, we determine a locomotive's speed by measuring the time it takes to travel a known distance. This will need to be completed twice for each locomotive, using different throttle settings (speeds). We need to determine which locomotive starts the slowest, and which locomotives run the fastest at a high throttle setting.
- Another possibility is to use a test stand with a speedometer, such as that which was offered by Bachrus. That allows you to adjust speeds on your workbench.
Before beginning determine which locomotive runs the slowest at a given speed step. Trying to match a slow locomotive to ones which are faster will be frustrating.
If you have DecoderPro available:
- Read the CVs from each locomotive
- If the locomotive is not in the roster, create a new entry and read the decoder's CVs.
If you do not have DecoderPro, read the CVs below in each locomotive and make note of them before altering any CV.
- Set CVs 02, 03, 04, 05, and 06 to 0 (zero). If these CVs are NOT zero, their effects will adversely influence your observations; thus these efforts will be fruitless.
- Turn off BEMF for now.
- Set the command station to use the 128-speed step mode. If you typically use the 28-step mode, the decoders can be fine-tuned in that mode later.
- Set the top speed
- This is CV5. Use a value of 180.
- If using a speed table, set CV94 to 180.
- If you are using DecoderPro, the easier method is to use the Match Ends command in the Speed Table tab.
- For each locomotive, determine which throttle setting gets the locomotive moving from a dead stop. Note this setting, and also the time it takes to travel the track section.
- Now run each loco at some ridiculously high throttle setting to determine which loco runs *faster* at that setting. (We can decrease top voltage on the faster one; we cannot increase the slow one.)
- Be sure to start the loco some distance before reaching the beginning of the measured distance, so that its speed stablizes before it begins the measured distance.
Let's start adjusting the start speed:
- Determine which loco starts the slowest, or lowest speed step, preferably speed step 1.
- In this step, we are only interested in what it takes to get the loco moving from a dead stop.
- Through decoder settings, we can adjust the startup voltage to get it to start moving at speed step 1.
- Once the reference locomotive has been found, match the other locomotives to that speed step.
- Slowly increase CV02 until it starts moving on that speed step.
- Consisting the locomotive to the fastest unit (but don't couple them) will visually indicate when the match is close. That way one throttle controls both units.
- If a double track is available, run them side by side to verify the results against the reference locomotive
- Repeat this step for each locomotive to get starting speeds matched.
- Verify the speeds match by increasing the speed up to speed step 10, for example.
- Slowly increase CV02 until it starts moving on that speed step.
- Repeat the process moving in reverse. They should be close. If not, adjustments to Forward Trim and Reverse Trim (CV66 and 95) will be necessary.
- Adjusting the Max Speed:
- Here, we will be adjusting the faster locomotives down to match the speed of the slower locomotives. Begin with one of the faster locomotives you wish to match. This is why a value of 180 was used in CV5.
- Keep adjusting CV05 (or CV95 if using the speed table) until the maximum speed matches that of the slowest locomotive you wish to match.
- Repeat the above step for each of the faster locomotives, remember, we are not changing this setting on the slowest locomotive.
- Mid-Range Speeds
After the Slowest and Fastest speeds have been matched, some adjustment in the middle will be needed.
- With a speed selected in the middle of the range, adjust the appropriate CV to match the faster unit to the slower one. Either locomotive can be tweaked, or both if needed.
- Again, verify the match is close in both directions, and make any adjustments needed.
- If using DecoderPro, the speed table can be adjusted using the mid point as a reference, to create a straight line from the middle to the top and bottom of the curve. Don't alter the mid point!
- Speed Tracking
This is to verify the locomotives have a good match, by slowing incrementing the throttle and observing their behaviour. If problems appear, repeat the process to match them.
- Momentum Adjustments
Using the notes made earlier, set the momentum via CVs 3 and 4 to their previous values. Run the units again, at various speeds, then change direction on the throttle to see how they slow to a stop and reverse. Make any adjustments deemed necessary.
Once you get the above working, you now start turning on special features such as BEMF if you feel the need. After doing that, again verify that they are matched.If the Decoder supports BEMF Cutout, adjustments may be needed to make the locomotives have a similar cutout.
Things to Keep in Mind:
- We cannot match the speed of every locomotive exactly. There are unadjustable differences in motors, drivetrains, etc. We can only get close.
- At a given throttle setting:
- Some locos will run at one speed going forward, and an entirely different speed going in reverse.
- Some locos will run at one speed running "light", and an entirely different speed under load.
- Some locos will run at one speed going uphill, and an entirely different speed going down...
You will not be able to eliminate these irregularities. You will not be able to match every speed perfectly. There is just no way. In time you may need to make adjustments again as the mechanism wears in.
Some decoders may have a Forward/Reverse Trim feature, which allows you to adjust the speed to match in both directions.
Consist the locomotives, and couple them together. Take them out onto the mainline to see how they behave at various speeds. Mute the sound (if equipped) so that odd noises, like wheel slippage can be heard. The consist should run smoothly with little surging or bucking. If so, the culprits may need additional tweaks to the speed ranges that require them.
If you used Decoder Pro, be sure to save the updated roster information.
- Speed tables are optional. This feature (if available) is only active when CV29 bit 4 is set to 1 (one)
Note: Speed tables must not have a a step set to a value lower than that of the previous step. Doing so will cause problems. Software such as JMRI DecoderPro or ESU's LokProgrammer will prevent this mistake from happening.
QSI multifunction decoders do likewise: The values in CVs 2 and 5 impact the speed table.
ESU V4 and Select multifunction decoders also have differences (excluding those with an early firmware version). Again, CVs 2 and 5 are used to modify the speed table (when active) by specifying the VStart and VHigh values. CVs 67 and 94 are fixed values. The advantage is that the bottom and top of the speed curve can be altered easily while avoid mathematical errors possible when using QSI's method. The decoder then determines the actual speed curve, so the speed curve always starts on the values found in VStart and VHigh. Both DecoderPro and the LokProgrammer are aware of this restriction.
- For more detailed information see the JMRI web page on Speed tables