First there will be others that immediately respond ?they have never had to do what I am going to say and theres works just fine. Good for them! ?:)
My experience back 10 to 15 years when I started adding decoders and sound was with my PR3 I could not reliably read and write to anything other than basic Digitrax sound decoders. That was before I added a PTB100. Since then I
have not found a decoder I cannot program. Now some are a bit more stubborn due to their complex settings, ESU and BLI, but they due program with patience.?
From: 31001314520n behalf of
Sent: Monday, August 13, 2018 11:28 To:[email protected] Subject: Re: [jmriusers] Entering New Loco's in DEcoder Pro
?
I'm having a similar problem with reading Paragon 3 decoders. I use a 2' programming track with a Sprog II and a Digitrax PR3. They are isolated from each other with a rotary switch. I have DecoderPro 4.12 installed.? I recently bought a new BLI N scale F3
with a Paragon 3. I tried to go through the New Loco process using the Sprog to read it, but kept getting a 'No Locomotive detected' error using the automatic decoder reading function. I tried to manually tell it that it was a BLI Paragon 3 Rolling Thunder,
but got the same error. Thought there might be a problem with the Sprog so I switched over to the PR3 and got the same error. So then I thought I had a major problem with the loco and put it on the main, which uses a Digitrax DB150 (2' x 5' track) and the
Digitrax throttle. It read it fine and I was able to reprogram the loco address and move some functions around without a problem. I went through all of the various recent emails and made sure that DecoderPro was not set to Local, I was on the right programmer
and the Preferences Connections and Default,etc. were set correctly. I was able to run 3 other non-Paragon trains on the programming track using both the Sprog and the PR3.
My guess is after all of this is that neither the Sprog II or PR3 has enough power to run the Paragon 3 decoder. Any other thoughts?
