¿ªÔÆÌåÓý

Locked Re: Issue recognizing locomotive - Atlas N MP15DC


 

Improbable but possible is that you have actually got two decoders in there, on different addresses. Could be worth checking out.

Wouter


On Sat, 23 Nov 2019 at 01:08, Heiko Rosemann <heiko.rosemann@...> wrote:
On most decoders, you can't do readback if they don't have a working
motor connection. And programming on the programming track as well as
identifying your decoder _does_ require working readback, even if it's
just to acknowledge a write. Programming on main - as suggested earlier
- works without readback, but it's not going to help with a broken motor
connection...

The fact that you can control the lights on your loco but it won't move
indicates just that - no connection between decoder and motor (or broken
motor, but that's rare).

Readback and acknowledge work by the decoder creating little pulses in
the supply current, which are then detected by the programming track
circuitry. To do so, most decoders pulse the motor (which is also why
locos tend to wiggle forwards or backwards during programming).

Hope this helps,
Heiko

On 11/23/19 12:00 AM, Chuckaknuckle wrote:
> Hi Marc, thanks for the reply.
>
> I can give the LENZ decoder a shot in JMRI to see if there's any
> difference there.
>
> I might try the 1K resistor as you suggest, to see if there's any
> difference.
>
> Currently the engine is not working, only the lights are toggling
> (front/rear).
>


--
eMails verschl¨¹sseln mit PGP - privacy is your right!
Mein PGP-Key zur Verifizierung:





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