开云体育

Thanks for catching that! I've fixed the originals. That's an example of a "family" of decoders. Jim Scorse uses the same micro-code for his line of "Silent Running" decoders. They all contain the

the above needed category? Unfortunantly, I'm not a Java Developer. Actually, I don't get to develop code much at all these days - I've evolved into more of a "Professional Meeting Attendee" and

CV8 seems to be the most reliable data but I'm not sure what they do when a decoder is subcontracted like say Digitrax makes a decoder for Atlas or similar. One of the very large problems I see with

Bob, What about by Manufacturer, Scale, Model Example: Digitrax, N, DN142 or North Coast Engineering, HO, D13SR Al Silverstein

'Family' seems like a rather confusing category. Dividing the list by manufacturer is a good idea. In other words, I agree with Robin. Mike

I'm still getting my DCC system up and running; so, I'm not (yet) a JMRI user; but, I work in the software development industry, so I'll jump in and offer up my $0.02. Perhaps what is needed is a

Bob, I think I suggested a similar approach that was simpler. The dropdown decoder list just shows manufacturers, but then there are flyout menus for each manufacturer that list the models. If you

I don't have any real ideas about how to better identify decoders. I agree it's a mess, and will be happy to implement whatever you guys think is best. Mark Gurries made a suggestion a while back that

Because with some manufactures CV7 isn't going to always tell much maybe the DN14(x) concept would be good. The tabs (panes) for that group could then be asterisked with the comment, "not all of this

Ok, so how should the decoder name appear in the list when multiple decoders have the same CV07 value? My suggestion is that if the models have the same features, i.e. DN140, DN144, DN145, DN146,

Thanks Jon!

Jon, You are correct, I missed the DN140 in the decoder list. This was certainly operator error on my part, but that aside the sort order of the decoder list is another thing I've been meaning to

Bob, Jim Hanna found that IDENT didn't work for NCE decoder. Checking into this, I found that the NCE name is used differently in the decoderIndex and the decoder files. In decoderIndex.xml, it is

This just was posted on the Digitrax list, useful information! Out of production Digitrax decoders are listed at http://www.litchfieldstation.com/E/DccD/LD/OutOfProductionDecoders.PDF Jon Miller AT&SF

Robin, In my version I have a DN140 and a couple of DN142's. Looks like a little housecleaning is in order<G>. Jon Miller AT&SF For me time has stopped in 1941 Digitrax DCC owner, Chief system NMRA

Michael, Thanks. I don't see a DN140 in the DecoderPro set at this point. For reference, can you point me to where on the Digitrax site this is all spelled out? Robin

The DN-146A program wise is the same as a DN-140. The DN-142 has transponding and back emf that the 146 and 140 do not have. Program wise the DN-144K, 145K,146A,147A & 148K are like a DN-140. While

Did a DecoderPro install today for a friend, and he immediately ran into confusion on Digitrax and Lenz decoder models. He had a factory installed Digitrax DN146 decoder and a factory installed Lenz

Bob, Thanks for all your work. I'm sure you'll come up with something for the index files. I tried out the roster tools this morning and they looked good. Jim will try to keep an eye out for a repeat

That's a good idea. I played with it some last week, but wasn't able to make it really reliable. I'll keep working on it. (The problem is that the index can be in two places: The xml/ directory, where