开云体育

  1. Jmriusers
  2. Messages
Single Messages Topics Expanded Polls

Locked Re: Locomotive programming using Decoder Pro problems

 

Little information is supplied by the original poster about the decoder, the DCC system (if indeed there is one) and as you point out Thomas, version of JMRI.

The first red flag in this thread is "I've read", what have you read and how old is what you read.

Years ago pretty near all sound decoders needed a programming booster, not now.

An aside to this thread, I have a SPROG II, it has never ever failed to read/write any decoder it has been attached to, BLI, ESU, TCS, Digitrax, Hornby, Bachmann, QSI or Soundtraxx.

The only issue with ESU decoders is that if there is a firmware update or you want to change something in the sound files, you absolutely need the LokProgrammer, no getting around it.

So, if you want advice poster, please give us some information a bit more informative.

John


On Fri, May 5, 2023 at 5:26?PM thomasmclae via <mclae5-lists=[email protected]> wrote:
First off, sounds like you are just writing.
Put a Lok on the programming track, select new entry, then read type from decoder.
That should read something from the decoder.
If that does not work, the write will not either.
The issue could be one or more of the following:
JMRI connection flipped to simulator. AN old version had that issue, upgrade to newest version.
Loose wire
dirty track
wrong decoder type selected (See read type from decoder above)
booster dead.

All resolutions start with being able to read.


--

---
Thomas
DeSoto, TX

Join [email protected] to automatically receive all group messages.