Skip to main content

This weekend I hooked up my Legacy and DCS to operate from the DCS App.  While I have little interest to run trains this way I do love the technology.  After installing the WIU last week along with my LCS devices I bought the cables needed to operate the Legacy engines from the DCS WiFi app.  So far it seems everything is functioning as it should.  I have added a router to the basement without internet connectivity to merge all the various WiFi devices from Lionel and MTH so I can still run iCAB and LCS with the MTH App.  I will add my Caboose cams and maybe an Apple TV device as well.

Here is a video of one of the test runs last evening...

 

Original Post

Replies sorted oldest to newest

I also have also combined both LCS and MTH Wi-Fi into one system on my layout. The MTH app does a very good job at running Legacy equipment. You'll notice a few differences regarding how RPM's and other features respond in ways that are different than using the Legacy remotes. The last MTH app update squashed a bunch of bugs. My only gripe is MTH's implementation of TMCC & Legacy lashups. When you build a lashup in the MTH app, it doesn't upload the lashup as a train to the Legacy Base. It stays local to the MTH app. However, if you build a train with iCab, it will write it to the Legacy base, making the train available in the event you decide to switch to a CAB-1L or CAB-2 remote. An issue occurs when you build a train using iCab, CAB-1L, or the CAB-2, and then switch back to the MTH DCS app. Your lashup will no longer work. And there is no feature in the MTH app to "Build" a lashup that has already been created and may just require a reset. It is a PITA to rebuild everything.  On the other hand, the CAB-2 lets you re-build a lashup that has come undone using the build command. From a practical standpoint, you really  have to decide to keep lashups on either the MTH app or Lionel system, but not both.

Last edited by GregR

I have noticed that also. I like how the iCab app and CAB-2 will coordinate their speed graphs.

Marty, what are you using to control your track power? I control track power using a Legacy 360W Powermaster, set up in the MTH app. I don't run any power through my TIU - it's in passive mode.  For operation of my conventional locos,  I have found that the MTH DCS app does a much better job handling variable voltage control than the iCab app. Voltage changes occur much more smoothly without lurching in increments. You will also notice that you can adjust speed while blowing your horn, using the MTH app. If you try changing speed on the iCab app, while blowing a horn/whistle, the sounds will cut out until you remove your finger from the speed graph.

Just be careful that you don't accidentally hit 200mph when you are adjusting your speed in the MTH app. The "+" button is dangerously close to 200 mph!

Last edited by GregR
GregR posted:

I have noticed that also. I like how the iCab app and CAB-2 will coordinate their speed graphs.

Marty, what are you using to control your track power? I control track power using a Legacy 360W Powermaster, set up in the MTH app. I don't run any power through my TIU - it's in passive mode.  For operation of my conventional locos,  I have found that the MTH DCS app does a much better job handling variable voltage control than the iCab app. Voltage changes occur much more smoothly without lurching in increments. You will also notice that you can adjust speed while blowing your horn, using the MTH app. If you try changing speed on the iCab app, while blowing a horn/whistle, the sounds will cut out until you remove your finger from the speed graph.

Just be careful that you don't accidentally hit 200mph when you are adjusting your speed in the MTH app. The "+" button is dangerously close to 200 mph!

I am using a ZW-L for power.  The TIU is powered off of fixed 1 currently but am going to get an external supply soon.

Add Reply

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