I've spent a couple hours trying to speed match a Kato (Soundtraxx decoder) and P2K (Digitrax decoder) locomotive so I can use them in a consist together. I had them almost perfectly matched through all speeds...until I put them in a consist together. The locomotive with the Digitrax decoder only ran at about half the speed it did prior to consisting.
Rather frustrating after a couple hours of work. Am I missing something?
I'm using an NCE Powercab, by the way.
Thanks in advance,
Acela
The timbers beneath the rails are not the only ties that bind on the railroad. --Robert S. McGonigal
Many cure this with a value of CV57=102 on the Digitrax decoder.
Jack W.
LOL! You're not missing anything. Most instructions tell you to speed match them "un-consisted", which I believe leads to your result.
I have a Digitrax DCS51 (Zephyr Xtra) with a DT402. I have 5 locos with Soundtraxx Tsunami (4 decoders I installed) and 1 with a Bachmann motor decoder. A few weeks ago, I bought an Intermountain loco with Sountraxx Tsunami already installed, none of these were speed matched or consisted.
Like you, I spent the better part of an hour speed matching an Athearn SD70ACe with a Tsunami to the Intermountain ES44AC with Tsunami, they were almost perfectly matched using CV66 and CV95. Once consisted (MU'ed), the Intermountain ran faster than the Athearn.
I broke the rules, consisted them together and then speed matched them. Took less than 10 minutes (I don't have JMRI) and they run fine together. From now on, I will MU my locos before speed matching and save lots of time and effort.
Inspired by Addiction
See more on my YouTube Channel
PennCentral99 LOL! You're not missing anything. Most instructions tell you to speed match them "un-consisted", which I believe leads to your result. I have a Digitrax DCS51 (Zephyr Xtra) with a DT402. I have 5 locos with Soundtraxx Tsunami (4 decoders I installed) and 1 with a Bachmann motor decoder. A few weeks ago, I bought an Intermountain loco with Sountraxx Tsunami already installed, none of these were speed matched or consisted. Like you, I spent the better part of an hour speed matching an Athearn SD70ACe with a Tsunami to the Intermountain ES44AC with Tsunami, they were almost perfectly matched using CV66 and CV95. Once consisted (MU'ed), the Intermountain ran faster than the Athearn. I broke the rules, consisted them together and then speed matched them. Took less than 10 minutes (I don't have JMRI) and they run fine together. From now on, I will MU my locos before speed matching and save lots of time and effort.
Interesting, I presume when you consist locos to speed match the locos are not actually coupled together.
Otherwise how would you know if either loco is running slower/faster than the other.
I have been speed matching locos for consist ops including sound decoders and non sound together with very good results for a few yrs.
Each loco is done seperately via Decoderpro using 28 step speed curve.
There was a time, before Decoderpro, that I laboriously did each speed step indavidually.
I must admit I have never used Tsunami's.
Cheers
Ian
The issue is the way Digitrax controle BEMF in their decoders. There are two seperate settings, for running alone and for running in consist. Of course, this only applies to CV19 consisting, so with a Digitrax system this generally does not come into play as by default they do not use CV19 consisting. Other systems do, and the default setting for BEMF turns it off in a CV19 consist, which greatly effects the running characteristics of the loco. Setting the CV noted above will set the same BEMF parameter for consisted and unconsisted, and will give consistent results.
Some will say, you need to turn off BEMF for consisting or the locos will fight each other. Hogwash. I have TCS decoders in all my non-sound lcos, with their automatic BEMF. I regualrly run them together, and also with sound locos, which are 1 QSI and the rest Loksound, also with BEMF. They always run great together, even for hours at a time during club shows, and do not overheat.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
Last year I tried my first speed match w/o DecoderPro, mating an AthearnTsunami GP9 and a Kato RS-2 with an added TCS motor decoder. This was done before making the consist with my NCE.
http://cs.trains.com/mrr/f/744/t/218127.aspx
This thread describes how I matched the top and mid speeds (only slightly successful at min speed), which you know is difficult given the Tsunami's lack of CV5 (top speed) and CV6 (mid speed) adjustments. I slowed the Tsunami loco top speed using forward and reverse trim, with its CVs 66 &95 to match the slower TCS loco. First I had to use the Tsunami CV29 & CV25 (respectively) to enable speed curves and select a straight line curve. With the top speeds matched, set the speed steps to 63 and adjusted the TCS CV6 mid speed to match the Tsunami. I could not get the slowest speeds matched (with CV2??). It was necessary to refer to the downloadable tsunami manuals, particularly about CV29 and 25. I then consisted them and they worked together as they had separately.
Not sure if this can work for your situation.
I've moved on to DecoderPro, which required a serial cable connection from my laptop to my NCE PowerPro. It works with Windows 8.1 as long as late version Java is downloaded to the PC. Much easier for consisting as speed curves (including for Tsunami) can be adjusted graphically.
Paul
Modeling HO with a transition era UP bent
Iansa Interesting, I presume when you consist locos to speed match the locos are not actually coupled together. Otherwise how would you know if either loco is running slower/faster than the other.
Your presumption is correct. I had the locos separated by about 6 inches during the speed matching. It's easy to tell when one is gaining on the other. After the speeds were matched, I did one complete loop (30 feet) around the layout and they were still approximately the same distance apart, so I MU'ed them. After MU' ing, I kept them separated because I wanted to make sure that when the speed was increased on the top loco, the second loco would move also, confirming my MU was performed successfully. This is when I noticed the second loco (Intermountain) was gaining on the first (took about 3 feet to catch up and couple itself).
Speed matching AFTER consisting them proved better, as the locos stayed the same distance apart. The wife was even impressed as I could get 2 (separated) locos to move simultaneously by turning 1 knob.
Iansa I have been speed matching locos for consist ops including sound decoders and non sound together with very good results for a few yrs. Each loco is done seperately via Decoderpro using 28 step speed curve. There was a time, before Decoderpro, that I laboriously did each speed step indavidually. I must admit I have never used Tsunami's. Cheers Ian
Maybe someday I'll catch up with the big boys and use JMRI/Decoder Pro. If you have any suggestions for speed matching, feel free. Like I said, this was my first speed match and MU, but I'm satisfied with the results as my consist runs flawlessly and trouble free.