Keyboard Shortcuts
Likes
Search
Difference Between Compare and Reset
#decoderpro
|
All,
?
Recently developed a problem with one of my older diesels, an N scale Bachmann with Econami factory installled. Def used is ECO-100 Diesel.
Sound was fine, loco would not move.
?
On the programming track, I loaded the loco's DecoderPro roster entry file and used the CVs tab to compare all values. No differences. Loco still not moving.
?
Did a Reset. Loco now moves. Rewrote all CVs from the loco's roster entry file. Loco now will again not move. To emphasize, these settings have worked fine for years.
?
Are there some settings somewhere that DecoderPro can not see or change, except by reset?
?
Regards |
开云体育Don, seeking help, inquires: ? “Recently developed a problem with one of my older diesels, an N scale Bachmann with Econami factory installled. Def used is ECO-100 Diesel. Sound was fine, loco would not move.” ? Can you blow horn, turn lights off/on, etc.? ? If so, the brake may be set in the decoder, and/or other settings that impact startup/shutdown/speed increase/decrease, etc.? ? My bet is on the brake function.? Refer to the instructions that came with the loco.? Check the Soundtraxx website for additional in depth information about the Soundtraxx decoder products. ? “On the programming track, I loaded the loco's DecoderPro roster entry file and used the CVs tab to compare all values. No differences. Loco still not moving.” ? The compare process will only show differences between what is currently in the decoder, and what Decoder Pro has on file for it.? Totally read only, plus display of differences where noticed. ? “Did a Reset. Loco now moves.” ? Not surprised. ? “Rewrote all CVs from the loco's roster entry file. Loco now will again not move. ?To emphasize, these settings have worked fine for years.” ? Works fine right after a reset, but once the record in DP is written back to the loco it no longer works, correct?? Sounds more and more like it could be related to having brakes applied. ? “Are there some settings somewhere that DecoderPro can not see or change, except by reset?” ? Decoder Pro doesn’t know what should be set/reset on any given decoder.?? Decoder Pro issues a “reset” command to the decoder; the decoder then performs its own reset according to whatever logic is built into _that_ decoder. ? Depending on what a decoder and its logic need to do to support certain functionality there very well could be memory of some type in the decoder other than CVs that the decoder uses to support the functionality offered.? Whether or not memory allocated for such a purpose is cleared/reset/initialized by a decoder reset would be a function of the decoder design. ? I’d dig into the decoder documentation and the manuals on the Soundraxx site.? If you don’t find something there, you might want to check with Soundtraxx Tech Support. ? Best Regards, ? Steve ? Steve Haas Snoqualmie, WA |
|
Tony,
?
Are you saying that CV 19 would somehow elude the Compare?
?
Steve,
?
You read the part where I say the settings had been working... for years in fact, right? No mysterious brake, BEMF, consist, or the like. And Econamies don't, to my knowledge, have Drive Hold, Reverser Centered, or such features that could even accidentally be activated.
?
Regards |
开云体育Don,?
On Digitrax, any "universal" consist is inside your command station, not the throttle.? Changing throttle doesn't alter it.??
Check the "slots" in the command station.? ?JMRI has a slot monitor for Digitrax, which may show something.?
- Nigel
------ Original Message ------
From "Don Shroyer via groups.io" <Donshroyer@...>
Date 31/03/2025 11:53:40
Subject Re: [jmriusers] Difference Between Compare and Reset #decoderpro
|
|
Steve,
I am just going by what I have seen with those symptoms before, Somehow a hiccup in the decoder, a spike on the track, someone miss typing while setting up a consist and the loco may have been consisted and the way to check that is to read CV 19, the consit address if it is 0 then that is not the problem so look elsewhere.
If CV 19 has any other number then it is in consist and will only respond to movement commands on that number.
Changing CV 19 to 0 will take it out of consist and allow it to run on it's normal number.
It only takes a few seconds to read one CV to find if that is the problem.
Tony |
|
But when you program the saved file into the decoder then it programs in CV19 as well, so the compare will show as all correctly programmed. On Mon, 31 Mar 2025 at 15:55, Don Shroyer via <Donshroyer=[email protected]> wrote:
|
开云体育Continuing the conversation, Don responds: ? “Are you saying that CV 19 would somehow elude the Compare?” Not likely – CV19 is just another location in the decoder to be compared to the data stored in the record in the Decoder Pro Decoder index. This could be tested by changing CV19 in either the decoder itself or in the record in Decoder Pro, then running the compare function on the CV page. “You read the part where I say the settings had been working... for years in fact, right? No mysterious brake, BEMF, consist, or the like. And Economies don't, to my knowledge, have Drive Hold, Reverser Centered, or such features that could even accidentally be activated.” Yes, I did. The symptoms are identical to those reported previously by others where the braking functionality _has_ been revealed to be the cause.? While you are adamant this is not the case (no reason to doubt you), the symptoms _do_ seem to match that possibility. So, if not braking related, what is left? From your description, a reset decoder works fine until the values stored in Decoder Pro are written to the decoder, at which time the decoder ceases to respond. I don’t recall the specifics;? Can you share the make and model of both your DCC system and the decoder again?? After you issue the decoder reset command, the loco/decoder responds at short address three, correct? And after that you write the data stored in Decoder Pro back to the decoder, correct? Does writing the settings from Decoder Pro back to the decoder itself result in the address being changed from short address 3 to some other address (short or long), and that is the address the decoder is not responding to? I’m starting to suspect some type of potential disconnect between data loaded into the decoder via the reset, and data the command station has stored in regard to the address that doesn’t work after the decoder data is written to the decoder. Various DCC systems store different pieces of data about a loco/decoder in their memory. I’m not a specialist on the internal workings of various command stations, so folks with knowledge of your specific system’s internal workings would have to chime in here. Hopefully this will give you some additional paths to explore. Keep us posted. Best regards, Steve Steve Haas Snoqualmie, WA ? Regards |
|
toggle quoted message
Show quoted text
On 3 Apr 2025, at 21:18, Steve Haas via groups.io <Goatfisher2@...> wrote:
|
|
The question should really be asked as: - what does jmri write to these cvs? - what is read back on the programming track? That would rule out another type of error. Wouter On Thu, 3 Apr 2025, 21:45 Phil G via , <phil=[email protected]> wrote:
|
开云体育Wouter comments: ? “The question should really be asked as: - what does jmri write to these cvs? - what is read back on the programming track? That would rule out another type of error.” ? JMRI _should_ be writing that which is displayed on the screen when whatever command to write to the decoders is executed.? Hopefully it is either “Write all . . . “. ? Reading back the values of the CVs _after_ the “Write .? . “ to the decoder would be a good idea, but I suspect the OP has done the equivalent by using the compare process on the CV’s tab. ? Anything that sheds further light on what is occurring is a good idea. ? Best regards, ? Steve ? Steve Haas Snoqualmie, WA |
|
Writing CVs back to a decoder will not magically turn a function, like
brakes, back on. I’d look at speed tables, inertia, stuff like that next if the OP is sure his addressing is correct. Mick Mick ______________________________________ Mick Moignard mick@... p:+44 7774 652504 The week may start M, T, but it always ends WTF! |
|
I was suggesting one step at a time. Small ones
toggle quoted message
Show quoted text
Phil G On 4 Apr 2025, at 07:44, Mick Moignard via groups.io <mick@...> wrote: |
Bob Jacobsen