So you're programming on the layout.

I do both. Initial install and programming of settings is at the workbench using my DCC test track ... and I’m talking sound decoders since that’s all I use now. There’s a lot of sound tweaks that I do, along with function remapping and setting CV29 and the loco address. But I don’t program motor speed settings at the workbench other than just very basic settings.

Then the loco goes to the layout for speed matching. I have a reference loco that I use to speed match with to get things in the ballpark. I use programming in the main, or OPs mode programming to adjust CV2, CV5, and CV6. Plus I set CV3 and CV4 to zero before I start speed matching, then I usually set CV3 and CV4 to some high value like 200 since I now rely on braking and running slow when I need to stop fast.

Using OPs mode programming to set a few CVs for speed matching is quick, easy, and quite safe.

I more or less do it that way, but will take more care in future and keep CVs 3 and 4 off until after the speed matching is done.

Tony in Gisborne, Australia

So when you are speed matching on the layout, Are you giving both locomotives the same address?

-Scott

So when you are speed matching on the layout, Are you giving both locomotives the same address?

Nope, read the detailed explanation I wrote back on page 1, https://model-railroad-hobbyist.com/node/41120#comment-452981 ...

Make sure both locos are warmed up first by running them for five minutes. Next I consist the two locos together but put them on separate tracks.

By consisting the locos, they keep their original addresses so I can use programming on the main with JMRI to tweak their respective speed CVs easy peasy. Most decoders have the locos make a slight jerk when writing CV values on the main, so it's very easy to tell if the CV updates took.

Yet since they're consisted, they run together when I use the throttle. But since they still have their original address, tweaking the CVs in DecoderPro only affects that specific loco sheet for that one loco number and not both.

Ok, I understand now. thanks Joe

Always speed match as if the unit is consisted,  I do not know about new decoders but at one point older decoders behaved differently when consisted vs not consisted.  You might be speed matching to a stop watch over distance, golden locomotive or speed traps etc.  make sure you consist the engine before you start (Yes you can have a one unit consist)

Years ago with some older decoders people would speed match with units not set as consisted,  but when it came time to put them into a consist they ran much much slower than the original speed matching when not consisted.  Then would break the consist and the unit would run fine.  I did not understand why consisting was so hard.

Basically some decoders behave differently when set to consist vs not set into a consist.

Also turn of BEMF...  It will give your problems and some decoders turn BEMF off when consisted anyway.  That adds to another odd behavior of engines that are consisted.  I have 3 decoders (No other manufacture makes them for this engine type) made for a set of 3 specific engines that you can not turn of BEMF.  The BEMF starts to fight each other tell one engine basically puts on the breaks and another is full speed and the 3rd has no clue,  it is rather funny to watch.  Separate the 3 engines a few inches apart and it looks perfect you would think that would work when coupled...No they start fighting each other.

Moment...Turn it off when speed matching...Why wait for the engine to ramp up to speed step 28 etc.  Turn momentum back on when you are done.

bonus points stop using 128 speed steps and use 28.   Real engines have 8 speed steps.  when in 128 speed steps the middle spots are some sort of calculation and probably not the same acorss different manufactures and behave the same for different models, engines and gearing.