Skip to main content

Alright I'm going to try to explain this the best way I can and I wasn't sure if this goes to the Lionel Legacy area or this one. I have the Lionel Cab1 hooked up to a MTH DCS system. I had 2 Lionel Legacy engines which were the WM F-7 and the WM GP35. I never had any problems running them together with the DCS remote. Last week I purchased and programmed a Erie gp-7. It works great with the DCS. Last night I ran my WM GP-35 with the Erie on my layout. When I started the Erie the WM GP35 responded to the same radio signal. Has anyone had this problem? Did I do something wrong on the programming of the engines?

Original Post

Replies sorted oldest to newest

Could the problem be that I'm supposed to program the Erie engine first with the CAB1 remote?

No, not at all.

 

Most likely, this isn't a Legacy or DCS issue. Odds are that both engines have different DCS ID#s but the same TMCC ID#.

 

All TMCC engines come new with TMCC ID#1. If you purchased these engines new, the both most likely have TMCC ID#1.

 

Also, when you entered them into the DCS Remote, what did you enter as each engine's TMCC ID#?

 

Whether using a Cab-a or a DCS Remote, when you operate a TMCC engine, all engines with the TMCC ID# that is being addressed will respond.

 

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
I think that's where my problem is that on the DCS remote I programmed both with TMCC ID#1. Like I said I programmed the WM about a year ago and just forgot. When I get home tonight I'll give the Erie TMCC id#3. I think the WM F unit has #2 which I also programmed a year ago. Am I on the right track now?
 
Originally Posted by Barry Broskowitz:

Could the problem be that I'm supposed to program the Erie engine first with the CAB1 remote?

No, not at all.

 

Most likely, this isn't a Legacy or DCS issue. Odds are that both engines have different DCS ID#s but the same TMCC ID#.

 

All TMCC engines come new with TMCC ID#1. If you purchased these engines new, the both most likely have TMCC ID#1.

 

Also, when you entered them into the DCS Remote, what did you enter as each engine's TMCC ID#?

 

Whether using a Cab-a or a DCS Remote, when you operate a TMCC engine, all engines with the TMCC ID# that is being addressed will respond.

 

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!

 

Come to think of it I did program the Erie engine to TMCC id#1
 
Originally Posted by Barry Broskowitz:

Could the problem be that I'm supposed to program the Erie engine first with the CAB1 remote?

No, not at all.

 

Most likely, this isn't a Legacy or DCS issue. Odds are that both engines have different DCS ID#s but the same TMCC ID#.

 

All TMCC engines come new with TMCC ID#1. If you purchased these engines new, the both most likely have TMCC ID#1.

 

Also, when you entered them into the DCS Remote, what did you enter as each engine's TMCC ID#?

 

Whether using a Cab-a or a DCS Remote, when you operate a TMCC engine, all engines with the TMCC ID# that is being addressed will respond.

 

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!

 

Add Reply

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