I have a General Purpose Diesel Hydraulic Locomotive 3374 (original) DB 216 that I have upgraded with a 60760 (Motor) and 60972 (Decoder) which I have been running successfully on Windigipet Small for several months. I recently upgraded WDP to 2018 Premium without problems (several weeks) with the running of the layout.
I am controlling the layout via a Intellibox (IB) 650 which also has been recently upgraded from 1.001 to 2.01 Software.
The 3374 Locomotive (One of my best runners), decided to not run any more – either via WDP or via the IB in isolation. The direction lights (F0) do not turn on in either direction or respond to Motor Controls.
I have a separate “Programing Track” on the IB that I use for Programing or Reading the locomotives. Placing the locomotive on the Programing track, I am able, using the WDP loco Decoder Utility or IB Controller to be able to read the full CV’s configuration into WDP. I am also able to write to the decoder – e.g via CV to change the Locomotive ID Address. However, I am not able to control the locomotive from IB (Isolated from WDP) or via WDP through the RS232 cable to the IB.
As the decoder (60972) supports Analog as an Alternative Format to drive the locomotive – I am able to operate the Locomotive Forward / Reverse together with the forward and Reverse Lights .
I have tried resetting the decoder (to factory defaults) via CV 8 and re-programing the previous CV parameters – however the Locomotive still fails to run digitally either via the IB or through WDP.
I have approx. 20 locomotives which I have upgraded with 60972 (decoders) and high propulsion (motors) which are running without problems on the same layout so I am perplexed why the decoder responds to all read/write commands and the motor and lights (via decoder) respond in Analogue mode.

I would appreciate any ideas what the problem could be and how to resolve this issue.

Thanks and Best Regards,

Andy Stacey

Turn off DCC on the decoder (CV 50 IIRC).

I have had this happen with a 60977 decoder with IB on version 1.5, but I haven't got around to turning off DCC to check that this is the problem yet. The impression I get is that because both MM and DCC are present the decoder gets confused, but haven't proven that hypothesis yet.