i have been using DecoderPro for programming my DCC loco decoders (in all scales) for several years now, because the graphic interface is a lot easier to operate the trying to do programming adjustments with my NCE PowerCab. Recently however, I have come up against an issue that has me stumped trying to program a Hornby 4-4-0. Because this loco has an eight pin NMRA socket, but is also a tender-drive model, there is very little space inside the tender for a decoder. In fact, the only decoders I have on hand that could fit, both are used and refugees from my spare parts box, one is an Arnold/Rivarossi unit identified as mfg #173, decoder version #021. The other decoder is an old NCE/TTX DH102EU neither of which are able to be seen or communicate with DecoderPro when I try them on the program track. I have two computers set up with DecoderPro, an old HP Netbook with a Mac OS (a ¡°HackIntosh¡±) running DecoderPro 2.14, and a slightly newer Asus tablet/ notebook convertible running Windows 8 and DecoderPro version 3. Neither computer can see either decoder. Yet, if I put a known working DCC loco (Walthers Plymouth ML8) on the programming track everything works fine as expected. If I then add the Hornby loco equipped with the Arnold/Rivarossi decoder to the program track along with the working ML8 loco, all of a sudden DecoderPro can not see either loco. As soon as I remove the Hornby loco, DecoderPro immediately sees the Walthers loco again just fine. It¡¯s as if the Hornby loco isn¡¯t just unable to be seen, it prevents the other loco from being seen as well. I was able to set the short address on the Hornby loco using the NCE PowerCab with the instruction book in hand, but it took many attempts before I could get the new address to actually work. For a test, ?I just today took the loco down to my LHS, where they have a demo layout using an MRC Prodigy Squared System, and using that system, I was able to select the address of the Hornby 4-4-0 and it operated fine. Since the Hornby loco has no lights, the only feature needed from the decoder is motor control. I realize this is an old decoder, but it is the first time I have had trouble with DecoderPro detecting a loco. My question is, is there something wrong with my DecoderPro, my SPROG 3 interface, computers, decoders or what? I believe the Java on my two computers are probably limiting me to the JMRI versions they are using, and I can¡¯t foresee buying a new laptop and trying to learn how to work the latest version of DecoderPro. I have enough trouble trying to figure out the differences between DecoderPro v2 & V3!
Thanks,
Bill in FtL
