Skip to main content

Lionel scale T-1 only. Several other TMCC engines are ok. Legacy, TMCC and DCS setup w/ Z4000. Locks into conventional when power is applied. Have to shut off power several times before it recognizes TMCC signal. Once it does, it works fine and even it returns to command if power is briefly shut down. Does it with shell on or off on track.

 

How does TMCC recognition work? If the engine doesn't initially see a signal will it switch from conventional to command anytime later if it sees a signal?  Or is it locked into conventional until????

 

How does a engine determine what mode to operate in?

Original Post

Replies sorted oldest to newest

Originally Posted by Bob Shaw:

Thanks but I tried all that. Engine is immediately in conventional mode each time throttle is advanced. If I do it many times, it finally goes into command mode.

if like you said in your original post your other engines are Ok then there is something wrong with this engine.  from your explanation here there is a problem with a it receiving the command. 

Do the reset and let us know.

 

Bill, what are your thoughts on a bad trace somewhere on the motherboard?  If he has the antenna connection to pin 23 and has tried other R2LC boards?  I would like to see him try to connect with the body off. 

 

Bob, are you positive you have no continuity between your antenna and ground?  What happened when you did the reset?

 

One last thing, are both wires connected on your run/program switch?  Make sure the swithch is good.  I see that from time to time.

John, blown traces is not an uncommon thing.  I see this often. The Lionel scale T-1 was made many years ago.  The very first thing I always do is reprogram the R2LC board and check it in my Lionel board tester.  If the board tests good, I go to the next step.    Then I  start with the contacts on the run/program switch.  I check for continuity on this switch with pin 22 on the R2LC board.  Next  check for continuity between pin 23 and the antenna.  Next I check for continuity between the antenna and ground.  Hopefully, I do not get continuity.  If all the above checks show good, I go to the next check.    At this point, I am getting ready to search for a blown trace.  They are usually easy to spot on the board.  Every motherboard I replace, I keep the bad board and hard wire the traces so I have a spare. I will use a repaired board on my own trains but not one for a customer.   I have found Lionel to have almost every motherboard needed.

Last edited by Marty Fitzhenry

I've only run across a couple of cooked motherboards.  I know it can happen, but it's not the first thing I think of.  As you say, once you have the MB out, it's easy to see if a trace is cooked.  Usually, they get cooked when something else happens like a short to the pickup trace.  I never throw them away either, I fix them and return them to service.

 

When something is running normally and stops working, I usually work my way through the most obvious suspects.  Of course, we seem to have eliminated the antenna and the R2LC, so maybe we're there.

 

I think more details of exact symptoms and how this started would help in figuring out what is happening.

 

imediatley after power is added to track, I get sounds from the tender, there is no response from any TMCC commands and I'm in conventional operation. It doesn't start moving until I hit the direction control button. Otherwise I  get smoke,whistle and speed control as in normal conventional control. 

 

I don't know how to do a reset without using the remote.

 

Both wires on run/ program switch are and with continuity to J2 connector.

I don't think your problem is with the command bases, because your other engines are working normal. I believe your problem is in programming, the sounds are starting up because one of the IR tethers (engine or tender) is not working. If you have another tmcc tender try it with the T-1. I think the engine is the problem. You have switched the R2LC with the same results, was it a known good one? As Marty pointed out it could be a bad trace on the motherboard or the programming switch or ground. Put the engine run/program in program and apply track with out touching the remote, do the sounds still start up.

 

Bill

Post
×
×
×
×
Link copied to your clipboard.
×
×