Atlas / Loksound decoder will not run on Digitrax but ok on Lokprogramer

[bdennis]

I have a interesting problem with an N scale Atlas C420 with factory Loksound sound decoder installed.
Was running fine a few months ago. But now.. Nothing (on the layout).
I have a number of other Loksound loco's on the layout plus non sound loco's that run fine.
I have a Digitrax DCS100 command station and DT402D, DT602D throttles.

The problem loco runs perfectly on a test track when connected to a LokProgrammer using the Loksound software so I know the issue is not pick up or board install.

When I select the loco on the Layout I can see that it is listed in the "slot's" on the command station but will not respond to any command.
When I select the loco on the DT402D it usually says STAT 128 for the speed steps but for this loco it says STAT TRI suggesting that the system thinks it is set to Trinary mode.
On the command station in the slots table it lists the loco as 28 Step trinary.

I have turned off all the European such as motorola etc functions within the decoder to no avail. Same problem. Will run on the test track from the Lokprogrammer but not on the layout.

I can read back the loco address on the programming track from the DT402D and set it again. No issues.
If I turn on the sound on the Lokprogrammer test rack and move the loco to the layout the sound will start but the loco wont run and will not reply to any function on or off commands.

My next step is to do a CV reset on the loco..
I have tried a CV8=8. from the Digitrax command station. This did not fix it.
I have tried a reset from the Lokprogrammer. This did not fix it.
CV29 is set to 58

Any thoughts or bright ideas as to why the loco will not run or what mode it has got itself into?

[EL3632]

To rule this out, dump the address from the system and try reacquiring. Sometimes the system just thinks the address is doing something it shouldn't.
It seems like the problem is related to the DCC system somehow, if the decoder works fine on the programmer.

[bdennis]

Yep tried releasing the loco from the Slot table via JMRI No fix..

Tried a number of resets (per updated 1sxt post). No avail.

[bdennis]

If I set the address to 400 via the programmer and then test on the layout it works fine. If I go back to 410 (via the same process).. It does not...
May need to reset the DCS100 and re MU all my loco's....
Will keep testing

[EL3632]

I am thinking JMRI did not dump the address properly. Try selecting your engine, make sure it is in forward, with no functions active, not in a consist, and then dispatch its address from your throttle. That should force it out of the system. This is the only for sure way I have found to dispatch an address from a throttle and actually dispatch the address. Digitrax is very persnickety sometimes.
Sometimes, at least for me, when JMRI doesn't work, hard resetting the system (with the OpSw for Digitrax) is the only way to for sure dump the system.
I have seen this problem happen before as well, can't select your address no matter what, but reprogramming the address works. Usually when this happens I have hard reset the system and it works. It sucks, but sometimes that is necessary.

[bdennis]

I am thinking JMRI did not dump the address properly. Try selecting your engine, make sure it is in forward, with no functions active, not in a consist, and then dispatch its address from your throttle. That should force it out of the system. This is the only for sure way I have found to dispatch an address from a throttle and actually dispatch the address. Digitrax is very persnickety sometimes.
Sometimes, at least for me, when JMRI doesn't work, hard resetting the system (with the OpSw for Digitrax) is the only way to for sure dump the system.
I have seen this problem happen before as well, can't select your address no matter what, but reprogramming the address works. Usually when this happens I have hard reset the system and it works. It sucks, but sometimes that is necessary.

Yep have tried dispatching using both the DT402D and the DT602D with no luck.
the loco works fine if I change the address.
So the next step is to reset the DCS100.

[John]

you need to status edit the decoder out of trinary back to 128 steps .. do that using the throttle . .

https://www.digitrax.com/media/apps/products/throttles/dt400/documents/dt400.pdf

Section 15   page 54 .. status editing a decoder ..

This happens some times when you pick up some static ..

[reinhardtjh]

This happens some times when you pick up some static ..

Or it could have been the DT602D.  One of the early DT602D firmware defaulted to the Trinary mode and caused a number of people on the Digitrax IO mail list to complain about just such a thing where they could program a loco and use it via a programmer or a JMRI throttle but not with the DT602D. I don't recall if any also had other Digitrax throttles that didn't work.

You should probably note the DT602D's firmware date/version when it first turns on and check the Digitrax site to see if you're up to date.  There were somewhere in the range of 4 or 5 firmware releases over the first 6 months. or so.

[bdennis]

you need to status edit the decoder out of trinary back to 128 steps .. do that using the throttle . .
https://www.digitrax.com/media/apps/products/throttles/dt400/documents/dt400.pdf
Section 15   page 54 .. status editing a decoder ..

Thanks John.. Yep that fixed the problem.

I set the loco back to its correct address using the Lokprogrammer.
Then did a status edit via the DT402D and all is now working.
Thanks.