On May 9, 2023, at 7:37 PM, Bob Jacobsen <rgj1927@...> wrote:

?Thanks for checking that. I had forgotten about that log message. I could have asked for that instead of the individual CV values.

This thread is about somebody who can’t get identification out of "Soundtraxx, Esu and WOW decoders”. We know which CVs JMRI reads for each of those;. What we don’t know is what’s coming back from his decoders,. Either he’s extremely unlucky and _all_ his decoders are somehow either broken or too new to be recognized, or there’s something wrong with how his DCC system is reading them. Getting the values will help figure that out, so I hope he either reads them and sends them, or sees this post and sends in what that log message says.

I lean against added lots of extra info to the console log during normal operation. Although most people don’t have to look at the logs, when we do need to see them, it’s nice to have them short and to the point.. Adding the individual CV readout to _everybody’s_ log seems extra noise for little gain.

Bob

On May 9, 2023, at 4:08 PM, Phil G <phil@...> wrote:

Bob
This question seems to come up a lot and I notice that when you do a "read type from decoder" JMRI already dumps THIS to the console
decoderdefn.IdentifyDecoder INFO - Decoder returns mfgID:151;modelID:255;productID:33554588 [AWT-EventQueue-0]
I wonder if this would be even more helpful if IdentfyDecoder could also specify the cvs that it's read to get this info (the first two are obvious, but I guess the rest would be decoder specific. This example is a LokSound5 DCC)?
Happy to raise an issue to get this considered if t could be of value. And useful to see that some of the work has already been done it seems
Phil G
PS Just checked a Zimo MX600R and IT returns "decoderdefn.IdentifyDecoder INFO - Decoder returns mfgID:145;modelID:40;productID:199", so I suspect knowing which cvs each part of the cv identification is derived from would be helpful. Especially in the case of unknown or new decoders without having to do separate cv reading step(s)

On 09/05/2023 18:33, Bob Jacobsen via groups.io wrote:
Could you provide specific examples, please? For a Soundtraxx decoder, I’d like to know the values you read from CV7, CV8, CV253, CV254, CV255 and CV256 For a TCS decoder, I’d like to know the values you read from CV7, CV8, CV110, CV111, CV248 and CV249 Might be best to read these with JMRI’s Single CV Programmer or using your DCC system rather than the DecoderPro CV table. ESU is more complicated, and I’d like to try solve the other two first. Thanks! Bob

On May 7, 2023, at 10:59 PM, Dennis Bartholow <dennis@...> wrote: I'm having the same problem with Soundtraxx, Esu and WOW decoders. JMRI identifies the manufacture, but selects every model produced by the manufacture. This s new. I was running 5.2, updated to the latest test version 5,3,6. Running JAVE 11. This problem is new. Any ideas? Dennis at els train service.

— Bob Jacobsen rgj1927@...

—
Bob Jacobsen
rgj1927@...

I recently upgraded to DP 5.2 and I put my brand new Athearn Genesis GP38-2 on the track and I clicked New Loco and the option to read the decoder was not present.? What am I missing in the new version?? The manual says there should be an option to read the decoder, and it used to be there in older version!

Furthermore, I went ahead and created a manual entry for it, selecting Soundtraxx Tsunami 2 and changing address from 3 to 4056 (road number) and now loco will power up but will not respond to any throttle commands.? I swear all I did was change the address.? What did I do wrong?