What is the Best Way or Ways to Run an Atlas Premier Engine With DCS

They're obviously compatible with MTH DCS, and you can also run them using DCC if your layout is so equipped.  I'm assuming since you have Legacy/DCS, run them with DCS, MTH supplies the standard PS/3 boards to Atlas, so they're run like MTH engines.

Thanks John for the reply- so if they are obviously compatible with MTH DCS, shouldn't the DCS system see them as an engine to add like other MTH engines?  I tried to add an Atlas Ferromex SD70 to the TIU and later the WTIU and had no success.  That's the main reason I bought the new Atlas engines-I assumed they would be plug and play with MTH DCS.  Maybe it relates to the other issue I'm having with using the WTIU with Lionel Legacy Base 3.

Jim

Should be seamless.  Make SURE the DCS/DCC switch is actually in DCS.

It is for sure in the DCS position.  Probably something to do with the other issue with the WTIU and ZW-L interference.  I may have to go back to the older transformer setup.

Jim

@Jim Duke posted:

It is for sure in the DCS position.  Probably something to do with the other issue with the WTIU and ZW-L interference.  I may have to go back to the older transformer setup.

Jim

I have read about compatibility issues with the WTIU and the ZW-L on other threads on this forum. Could this be your issue?

https://ogrforum.com/topic/wti...3#188663164424006033

Did the Atlas engines work with your old transformer setup?

I'm going to find out today if the ZW-L is the issue shortly. . . . .

Jim

I just did a test with an MTH power brick directly to the WTIU.  On my inside track with no Legacy engines, I got the Atlas programmed into the app, got it running.  When I combined the outer track that has the Lionel engines to the WTIU, everything started acting buggy, the Atlas sound went out (did a factory reset later!), and could not run a single MTH engine on the track with the Legacy engines (only 2 on that track!).  It's for sure an issue with DCS and Legacy operation.

Jim

The problem with Legacy & TMCC engines affecting DCS operation is well known.  The real cure is to add 22uh inductors in series with the center track power lead inside the TMCC or Legacy engines that are affecting the DCS.

That may be a solution, but it's not the ideal solution when you own about 150 legacy engines and only a couple dozen MTH engines.  I'll just have to run them isolated from each other for now or go back to my old setup with non-wifi TIU and analog transformers.  Too many other projects here at Ranburne Junction to spend time wiring inductors on all my Lionel engines. . . . Thanks for the input at any rate!

Jim

@Jim Duke posted:

That may be a solution, but it's not the ideal solution when you own about 150 legacy engines and only a couple dozen MTH engines.  I'll just have to run them isolated from each other for now or go back to my old setup with non-wifi TIU and analog transformers.  Too many other projects here at Ranburne Junction to spend time wiring inductors on all my Lionel engines. . . . Thanks for the input at any rate!

Well, I didn't say it was for everyone, but it's a known issue with some TMCC and Legacy engines, but not with all of them.  I've modified about a dozen of my Legacy engines, those that were really stinkers, but all the rest or stock and coexist with DCS just fine.

I'm still in the process of adding additional track loops to the layout, so for the foreseeable future with me, I'll plan on segregating the engines to keep from having the current issues.  I really like your power supply setup board the way it's laid out-I'm using it as a template for my setup!

Jim