开云体育

  1. Jmriusers
  2. Topics

Locked TCS WOW 121 diesel decoder question #tcs

 

Hello group.
I have a question about this decoder. I have 2 GP38's that are consisted together. I have not run these 2 locos for a week or so.
--Today when I started to run this consist the locos ran for about 15 seconds and the one loco stopped moving. Before it stopped there was a beeping sound for about 5 seconds. When I turn the throttle to 0 and then turn the throttle up again the loco that beeps and stopped, now sounds like a brake release and starts moving again. Then about 15 seconds later it beeps and stops.
I use JMRI for programming and these two locos are programmed the same. They have been running together for 3 years.
Seems strange how this happened.
Any thoughts would be appreciated.

Thanks,
MARK TAYLOR
Tim Kelley
 

Good morning Mark,
I have 3 TCS WOW-121 Steam Decoders. I think they are very similar. Sometimes hickups can happen on the rails
and the decoders can sometimes interpret them as programming commands. I have been "LOCKING" all of my TCS WOW-121 Steam Decoders.
That way they are locked and will NOT accept any programming commands. When the time comes and you want to make programming changes
to the decoders you can then unlock them to make the CV changes. I know this doesn't exactly answer your question right now
but it might avoid some future problems down the road.



Good luck!
Tim
 

Since this is a decoder issue and not JMRI you should take your questions to the TCS group.
/g/TCS-Users

--
Peter Ulvestad

JMRI Users Group Moderator ( )
Tam Valley Group Moderator ( )
Sprog-DCC Group Moderator ( )
Edmonton Model Railroad Association ( )
 

Thanks Tim.
My decoders are not locked.
I will lock them when I figure it out.

Mark.

On Mon., May 1, 2023, 11:39 a.m. Tim Kelley, <tim.kelley@...> wrote:
Good morning Mark,
I have 3 TCS WOW-121 Steam Decoders. I think they are very similar. Sometimes hickups can happen on the rails
and the decoders can sometimes interpret them as programming commands. I have been "LOCKING" all of my TCS WOW-121 Steam Decoders.
That way they are locked and will NOT accept any programming commands. When the time comes and you want to make programming changes
to the decoders you can then unlock them to make the CV changes. I know this doesn't exactly answer your question right now
but it might avoid some future problems down the road.



Good luck!
Tim


--
MARK TAYLOR
 

Mark,
Read this and look at the Tsunami section. It' slightly different from the standard for locking:





On Mon, May 1, 2023 at 9:55?AM Mark Taylor <Malicotrains21@...> wrote:
Thanks Tim.
My decoders are not locked.
I will lock them when I figure it out.

Mark.

On Mon., May 1, 2023, 11:39 a.m. Tim Kelley, <tim.kelley@...> wrote:
Good morning Mark,
I have 3 TCS WOW-121 Steam Decoders. I think they are very similar. Sometimes hickups can happen on the rails
and the decoders can sometimes interpret them as programming commands. I have been "LOCKING" all of my TCS WOW-121 Steam Decoders.
That way they are locked and will NOT accept any programming commands. When the time comes and you want to make programming changes
to the decoders you can then unlock them to make the CV changes. I know this doesn't exactly answer your question right now
but it might avoid some future problems down the road.



Good luck!
Tim


--
MARK TAYLOR



--
John Griffin

Model Railroading Topics
 

开云体育

Read this and look at the Tsunami section. It' slightly different from the standard for locking:

John, nice write-up. Just one comment about the statement:

“Note: Although not specifically stated, legal values for CV16 are limited to 1 to 7. Even then, Digitrax mentions 0 as a legal value. The author cannot test this as he does not use Digitrax decoders.”

As you note, the NMRA standard does not give “legal values” for CV15 & 16. ESU, for example, gives 0-255 as allowed values for these CVs in the decoder manuals. As far as I know, all manufacturers allow 0. It has always been my understanding that the NMRA standard implies that 0 in CV16 means no lock. Most decoders come with 0 as default for both CVs. I’m sure you will find 0 to work just fine in whatever decoders you have.

Now I need to test a few decoders to see if CV16=0 results in no lock independent of CV15 value. It may be that the default for decoders is unlocked because both CV15 and CV16 are 0.

Mark Granville (different Mark)
Tim Kelley
 

PLEASE NOTE THAT MARK's ORIGINAL QUESTION / ISSUE IS NOT ABOUT LOCKING HIS DECODER!!!!

-=Tim

On Monday, May 1, 2023 at 01:04:13 PM CDT, Mark Granville <mfgranville@...> wrote:


Read this and look at the Tsunami section. It' slightly different from the standard for locking:

John, nice write-up. Just one comment about the statement:

“Note: Although not specifically stated, legal values for CV16 are limited to 1 to 7. Even then, Digitrax mentions 0 as a legal value. The author cannot test this as he does not use Digitrax decoders.”

As you note, the NMRA standard does not give “legal values” for CV15 & 16. ESU, for example, gives 0-255 as allowed values for these CVs in the decoder manuals. As far as I know, all manufacturers allow 0. It has always been my understanding that the NMRA standard implies that 0 in CV16 means no lock. Most decoders come with 0 as default for both CVs. I’m sure you will find 0 to work just fine in whatever decoders you have.

Now I need to test a few decoders to see if CV16=0 results in no lock independent of CV15 value. It may be that the default for decoders is unlocked because both CV15 and CV16 are 0.

Mark Granville (different Mark)
 

开云体育

Sounds like you have Crew Alert enabled on one of the locos.

In DP, it's on the Sound tab.
Michael Mosher Member SFRH&MS
On 5/1/2023 11:31 AM, Mark Taylor wrote:

Hello group.
I have a question about this decoder. I have 2 GP38's that are consisted together. I have not run these 2 locos for a week or so.
--Today when I started to run this consist the locos ran for about 15 seconds and the one loco stopped moving. Before it stopped there was a beeping sound for about 5 seconds. When I turn the throttle to 0 and then turn the throttle up again the loco that beeps and stopped, now sounds like a brake release and starts moving again. Then about 15 seconds later it beeps and stops.
I use JMRI for programming and these two locos are programmed the same. They have been running together for 3 years.
Seems strange how this happened.
Any thoughts would be appreciated.

Thanks,
MARK TAYLOR

1 - 8 of 8