Skip to main content

I finally got another NEW MTH DCS REMOTE COMMANDER today.  Hooked it up and......

My New MTH RS 3 PS 2 came up in conventional again.

So, I took the Lionel TMCC engine # 6-28023 from 1999 OFF of the layout and, ...

The DCS Loco stayed dark like it should when receiving the DCS signal.

I then started it up with the remote and it ran perfectly fine. Everything functioned as it should.

I placed the Lionel engine back on the track, the DCS Engine ran in conventional again.

Now, a forum member you all know, mentioned to me that he heard of this problem with early TMCC engines. And I think this is an early TMCC engine. He said someone on here had a fix for this problem.

Can anyone help me???    My layout is 2 loops inter connected and wired as 1 track with one Z1000 transformer.

I don't want to isolate each loop and assign an engine to each separate loop, but be able to run them on the same loop, etc.

Layout 2 Loop FT -2.rrt Feb 10 001

Attachments

Images (1)
  • Layout 2 Loop FT -2.rrt Feb 10 001
Last edited by Larry3railtrains
Original Post

Replies sorted oldest to newest

Larry,

 

Unfortunately, any number of TMCC and Legacy engines, as well as some GGD passenger cars and cabooses from Atlas, have the effect if degrading the DCS signal. However, there is a documented fix for this.

 

From page 152 of The DCS O Gauge Companion 2nd Edition:

Some, but not all, TMCC engines will degrade the DCS signal of any PS2 engine with which they are in close proximity. This effect varies both by individual TMCC engine and by the distance between the TMCC and PS2 engines. In many cases, an RF choke inserted in the Hot wire between the pickup rollers and the TMCC engine's circuit board will correct this problem.

 

Some lighted cabooses, most notably those manufactured by Atlas O, may degrade the DCS signal, as may some engines or passenger cars with constant voltage (CV) lighting boards. Again, an RF choke inserted in the Hot wire between the pickup rollers and the circuit board in these cars will generally correct this problem. Although a number of different RF chokes may be effective in reducing interference from CV boards, one that has an electrical value of 22uh (micro henries) is known to work well.

 

This and a whole lot more is all in MTH’s “The DCS O Gauge Companion 2nd Edition", available for purchase as an eBook or a printed book at MTH's web store!

Last edited by Barry Broskowitz
Originally Posted by GGG:

Larry,  We were discussing this in another post that a TMCC Camel Back was causing issues.

 

If your willing to run a test, just place Tender on the track and see if the MTH engine works fine.  Then just try the engine.  On the Camel back, it was the engine causing issues.  G

Good suggestion!

larry, can you try this then we can go from there.

 

Rod

Larry,  As Barry Said you only need a choke in the engine.  But if Rod has a TMCC engine that doesn't cause issues, it would be nice to swap R2LC to see if that solves the issue.  If not it would than possibly be the DCDR.  No CV boards in your engine, so the only other item is the smoke unit.   This should be an easy issue to resolve, I was just trying to find out what part of the engine kills the DCS Signal.

 

Did you turn smoke off with the switch by chance when testing engine. G

Post
The DCS Forum is sponsored by
×
×
×
×
Link copied to your clipboard.
×
×