rrinkerWhat DCC system are you using?
Trying not to hijack Tophias's thread, so I think I sent you a PM.
Mike
I forgot to mention that the notch down function, F6, works to bring the rpm's down, but I need to press it 3,4, or sometimes 5 times to bring it down to a level that is proper for the loco's speed.
Water Level Route rrinker Ok Loksound decoders anyway, once the physical speed of the loco catches up with the throttle setting, the prime mover settles down, like now you are at track speed so the engineer throttles back to maintain speed without continuing to acelerate. Boy my Loksounds sure don't work that way. The prime movers never slow back down on mine. In fact, I have CVs 5&6 turn down quite a bit, and the decoders notch up regularly as I throttle up, entering notch 8 on speed step 48 or 49 and never drops off as the train slowly makes its way along the tracks. Looks/sounds kind of stupid. I've also had instances where a quick throttle up and throttle down will briefly move the locomotive, bring it to a stop, and the prime mover notches all the way up and stays there for several seconds with the engine stopped.
rrinker Ok Loksound decoders anyway, once the physical speed of the loco catches up with the throttle setting, the prime mover settles down, like now you are at track speed so the engineer throttles back to maintain speed without continuing to acelerate.
Boy my Loksounds sure don't work that way. The prime movers never slow back down on mine. In fact, I have CVs 5&6 turn down quite a bit, and the decoders notch up regularly as I throttle up, entering notch 8 on speed step 48 or 49 and never drops off as the train slowly makes its way along the tracks. Looks/sounds kind of stupid. I've also had instances where a quick throttle up and throttle down will briefly move the locomotive, bring it to a stop, and the prime mover notches all the way up and stays there for several seconds with the engine stopped.
You've got something off with the speed step to notch mapping then. Or perhaps this was something dependent on firmware version and was fixed in the ones I have - none of mine have the Drive/Hold option, I dismantled my layout and put everything away before that firmware was released. They shouldn't be at notch 8 before even half throttle.
What DCC system are you using? With my Digitrax, if I crank the throttle, because I have CV 3 set relatively high, the prime mover revs up almost insntantly but the loco just starts creeping. If I turn the throttle back down to a reasonable speed (the ballastic track on the encoders of the DT402 make that quick spin take it close to 127) , the prime mover throttles back to match the loco speed. I haven't updated any for Drive/Hold yet, but at least for starting off, I can replicate that with the momentum and working the throttle. The only thing I can't do is run downhill with the prime mover idled like you can with Drive/Hold. Well, I can if I use the manual notching functions.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
If it's the same decoder then generally all the CVs should be the same. If the issue is controlled by a CV value, then matching them should fix it.
Mike, that's a good description of what this engine does at times
I have another BLI Paragon 2 decoder switcher that seems to operate the notching more correctly but it's a different prototype model. Might I try to clone this file into the subject loco?
rrinkerOk Loksound decoders anyway, once the physical speed of the loco catches up with the throttle setting, the prime mover settles down, like now you are at track speed so the engineer throttles back to maintain speed without continuing to acelerate.
No, that won't work. The Paragon 3 settings only wortk on a paragon 3 decoder, Paragon 2 only works with a Paragon 2. Just using a different roster entry in JMRI doesn't magically make one decoder into the other.
Does it stay in the high notch, or does it back down? If it backs down, it's actiung normally if you are immediately turning the throttle to some speed. If you want the loco to start moving without the prime mover jumping up, you need to incremement the throttle step by step, not just suddenly go to the speed you want.
If there is a significant amount of momentum set in CV3, you can reduce that which will reduce the effect, but I deliberately set my locos like that because it's actually the way they usually work, at least when I;ve had a cab ride. If yuo start off a light loco, click the speed up bit by bit and the prime mover won;t rev up. If you have a heavy train, crank it up, the loco won;t jack rabbit start because of the momentum, but the prime mover will rev up like the engineer opened the throttle. Ok Loksound decoders anyway, once the physical speed of the loco catches up with the throttle setting, the prime mover settles down, like now you are at track speed so the engineer throttles back to maintain speed without continuing to acelerate.
???you want to write the firmware from a paragon 3, to a paragon 2??
don't think so, not absolutely sure, but don't they have different pics ??
Long story short, I have a BLI switcher with a Paragon 2 decoder that continues to notch up the prime mover regardless of the throttle setting. That is, set the Digitrax throttle to 10 and the prime mover continues to notch up to notch 5 or 5. The speed is correctly represented. I have done a reset Without eliminating the odd behavior. So I was wondering, if using JMRI, if I could delete the engine from the roster and then add it again by writing the file from an existing BLI switcher that is a Paragon 3 decoder. That is, would the Paragon 2 accept the Paragon 3 information?