Using the Quantum Programmer as a Command Station
By Paul Turvill
Locomotive Speed Matching: Using the Quantum Programmer as a Command Station and Programming Multiple Locos “On The Fly”!
Introduction
Since the Quantum Programmer by QSI Solutions normally connects directly to an isolated section of track, and, with the help of appropriate software (i.e., Quantum CV Manager), is capable of not only programming, but also controlling model trains, it doesn’t take much of a logical leap to conclude that the Quantum Programmer is, in fact, a bona fide command station. In fact, by feeding the Quantum Programmer’s outputs to a DCC booster rather than directly to the rails, it can be used to simultaneously operate a variety of locomotives and other equipment consuming current up to the limit of the attached booster.
As a stand-alone command station, the Quantum Programmer can also operate single pieces and combinations of equipment up to the limits of its own throughput capability and the capacity of its own DC power supply. While the power supply that ships with the Quantum Programmer has a 300 ma (0.3 amp) capability, a somewhat larger supply may be used. Internal limitations of the Quantum Programmer require that this total value not exceed 800 ma (0.8 amp). This value should be sufficient to operate two typical HO scale engines, or perhaps as many as three or four N scale units. For larger combinations of equipment, and for larger scales, the addition of a DCC booster (with its own appropriate power supply) is highly recommended.
Connecting a Booster
Adding a booster to the Quantum Programmer is achieved by attaching its output to the “railsynch” inputs of nearly any make of DCC booster. My own installation uses a spare Digitrax DB150, and a simple homemade cable. The railsynch signals are carried on lines 1 and 6 of the standard LocoNet cable (the blue and white wires in standard 6-conductor telephone-style cable). To make a suitable cable, all that is needed is a length of 6-conductor cable with an RJ-12 connector on one end, and the blue and white wires (only) stripped and tinned on the other. The four center wires should be trimmed back even with the cable’s outer sheath, and care should be taken that they are trimmed cleanly to avoid any short circuits between the unused wires.
Install the blue and white leads into the connector on the Quantum Programmer, and plug the RJ-12 end into the A or B connector of the DB150. Since the DB150 must operate in its booster mode, it is also important to connect a jumper between the Config A terminal and Ground on the DB150’s front connector; this forces the DB150 into “slave” or “booster” mode on power up. Connect the factory-provided power supply to the Quantum Programmer, and a suitable power supply to the DB150. Connect the DB150’s Rail A and Rail B terminals to your test track. Be sure the USB cable is connected between the Quantum Programmer and your computer.
Finally, if you haven’t already done so, download and install the latest version of Quantum CV Manager, and you’re ready to go.
Test Track Recommendations
While any electrically isolated length of track may be used for general programming and testing, a closed loop or circle offers the greatest utility, especially when performing such tasks as speed matching locomotives. A typical small layout might be temporarily converted to a test track by simply disconnecting the original command station and substituting the Quantum Programmer/booster combination described above. However, those with larger layouts or who simply want to isolate testing and programming from their mainline operations may find it more desirable to construct a separate test loop. My HO scale test loop is a 30” radius circle of track mounted on a fold-away board that gets stored out of the way under my benchwork when it’s not in use.
Because the closed loop (or circle) permits continuous running in either direction, it is the ideal situation for such chores as speed matching of locomotives that will be used in consists. The “baseline” locomotive can be set in motion and followed by another locomotive which is to be speed-matched to the first. As the two engines follow each other around the track at discreet matching speed steps, the second one can have its speed curve adjusted in real time, and the effect of each adjustment can be monitored visually until a close or exact match is obtained. Details of this procedure will be covered later in this document.
Using Quantum CV Manager
While the use of Quantum CV Manager for programming mobile decoders and maintaining a library of settings may be obvious, the software also has a number of features that make it ideal for other chores as well.
For example, while working in Operations Mode, under the View menu, you will find options to Display (or Hide) up to four “Test Cabs.” These four Test Cabs are in addition to the Test Cab that appears with each engine programming file that is opened from the File Menu. Test Cabs are analogous to handheld throttles; that is, each Test Cab can have a separate engine address assigned, and therefore can run a locomotive on the test track independently of other Test Cabs. Using the various Test Cabs, it is possible to run as many as four or more engines on the test loop at the same time, thus making it a simple chore to evaluate, for example, the relative speeds of all units in a troublesome F7 ABBA consist.
Further, because Quantum CV Manager can program in Ops Mode while simultaneously running one or more engines, parameters of any of the operating units may be “tweaked” by selecting its decoder’s address, the appropriate CV, and clicking the Program button.
Speed Matching Setup
In this example, we will assume you have two locomotives you wish to speed match to run in a consist. To start, place them both on the test loop some distance apart. Start Quantum CV Manager; be sure that it’s in Operations Mode, then open two Test Cabs, and assign one to each of the two engines by selecting the appropriate addresses in the Cabs. Set the two Test Cabs to use the “28 step” speed control; this way each adjustment you make in either loco’s speed will correspond with a specific CV used in the decoder’s user-defined speed table. Using the coarse (+4 and –4) and fine (+1 and –1) speed adjustments, set both Cabs to the same speed, and observe the two engines to determine if one runs faster than the other. Do this at a variety of speeds, from speed step 1 to speed step 28. Typically, if they haven’t been previously speed matched, one of the two will probably run faster at most or all speed settings. Use one that runs slower at higher speed steps as your “base” unit (since it is always possible to adjust top speed downward). Leave the base unit assigned to its Test Cab, and close the Test Cab for the faster engine.
Open a file (either existing or New) for the second (faster) unit. If you have previously used Quantum CV Manager to set up this unit, then use that file; otherwise open a New file for the appropriate engine/decoder model, and set up the basic parameters (engine address, CV29 settings, etc.).
Step One: Minimum Speed
Be sure that the engine to be adjusted (“test” unit) is set up to use the user-defined speed table (CV25 = 1 for QSI sound decoders), and that the Test Cab is set to use 28 speed steps, just like the “base” engine’s Test Cab. In the window for this loco, click on the Speed Curve tab, and select “Exponential” from the dropdown list at the lower left corner. Finally, in the pulldown menu at the top center, select “All NMRA Speed Table CVs.” With these settings, whatever speed step is selected in the Test Cab will be represented by a vertical green bar on the speed table graphic, as in the following screen shot:
[for full size screen shot please click the picture]
Be sure that the address of your test loco appears in the box below the “Decoder Address…” button at the upper left corner of the screen. If it doesn’t, click the button and enter the correct address now.
Start the base loco running at speed step 1 (or the lowest value at which it moves reliably); click on the window for the second loco and set its speed step to the same value as the base unit. It should run slower than the base unit, or it may not move at all. With your mouse, or using the arrow keys, move the slider on the green bar up a small amount, and then click the “Program” button near the top of the screen. When Quantum CV Manager has written the new values to the test loco’s decoder, the CV numbers at the bottom of the Speed Curve window will turn green. This step should speed up the test unit (or start it moving). Repeat these steps, moving the slider up or down a small amount each time until the two locos are moving at the same speed on your test loop. For the moment, don’t worry about the other 27 CVs in the speed curve window.
Step Two: Maximum Speed
Once you’re happy with the minimum speed setting, set the throttles in both Test Cabs to their maximum values (speed step 28). Again, the test unit should now be running faster than the base unit. Click on the speed table window so that the vertical green bar appears on the slider for the right-most CV. Drag or move the slider down a bit, and again click the “Program” button; repeat as needed until both locos are running at the same (maximum) speed around your test loop. This may take a bit of patience, especially if the initial speed difference fairly great. If the test loco catches up to the base unit (and possibly couples to it), just stop the process, re-space the locos on the loop and try a lower value for the top speed (CV94) of the test unit.
[for full size screen shot please click the picture]
At this point you should have two locos that run at the same speeds at minimum and maximum throttle. The advantage of using the “Exponential” option in Quantum CV Manager is that adjusting any one of the values between minimum and maximum throttle will automatically adjust all intermediate values according to a built-in mathematical progression. In most cases, this means that a satisfactory speed match can be achieved with as few as three sets of trial runs: minimum, maximum, and mid-range.
Step Three: Mid-Range
Without changing the speed table values for minimum and maximum speeds, set both Test Cabs to speed step 14; this corresponds to CV80 in the speed table. Again, with both engines running on your test loop, proceed as before, adjusting the slider for CV80 up or down as needed, each time clicking the “Program” button to make the changes. As you move the slider for CV80, you will notice that the sliders on the other intermediate speed table settings “follow along” to maintain a smooth progression between the minimum and maximum values you set previously. This interpolation feature is the main reason for using the Exponential option, and normally will result in good speed tracking between the units throughout their speed ranges.
[for full size screen shot please click the picture]
When both locos are running at the same speed in the midrange setting, it would be a good time to save the file for the test loco. This way, if anything happens to disturb these settings in the future, you can always get back to this point in the procedure.
Further Refinement (If Needed)
Try running the two locos at a variety of speeds. With luck the test unit shouldn’t require any further adjustments to make a satisfactory consist. However, if there are large discrepancies at any of the intermediate speeds, further “tweaking” may be necessary. Make a note of any speed steps that result in speed discrepancies, and use this information in the following procedure.
To adjust the individual CVs in the speed table, you will need to switch to the “Unrestricted” mode in the pulldown at the lower left of the speed table window. This setting permits any of the sliders to be moved without disturbing the settings of any others. Also, set Quantum CV Manager to “Program Selected CV” in the upper center pulldown menu. Referring to your notes (above paragraph), set both Test Cabs to one of the troublesome values. In the speed table window, move the slider for that value up or down, depending on whether the test loco runs slower or faster than the base unit, respectively, then click the Program button to set that value in the decoder. Repeat until you have matched the speed of the test loco to that of the base at this speed step. Repeat the entire process for other speed steps as necessary to achieve the result you want.
[for full size screen shot please click the picture]
It is easy to see that speed matching could be achieved with great precision by adjusting each of the 28 CVs between 67 and 94 individually, but in most cases this should not be necessary.
Conclusion
By now it should be clear that the Quantum Programmer is an extremely useful tool, not only as a decoder programming device, but as a specialized command station as well. In combination with Quantum CV Manager, it can become in indispensable tool for a number of chores, especially for clubs and individual modelers with medium-to-large rosters of locomotives to program and maintain.
Using Quantum Programmer for programming on the main with an NCE DB3 Booster.
Added 5/12/2011
This is a confirmation of the results posted by Paul Turvill who used a Digitrax DB150 booster for speed matching.
Tony:
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.
Larry Maier
