MTH DCS WIFI premium APP Questions or issues, post them here. VIDEOS ADDED

Daniel,

Unless mistake, I believe that an issue with the "All Engines Operation" when using multiple WIUs (Super TIU/WIU) has now been reproduced/identified.

The problem I found and reported was as follows:

When conducting an All Engines session on a layout where 3 TIUs have been setup as being in Super TIU mode, the following summarizes the behavior of the engines participating in the session:

• Engines on TIUs #1 and #2 were made active engines.
• All engines in the session started out on their "home" TIUs and all ran as expected while on tracks connected to their home TIUs.
• However, when an engine was driven onto tracks connected to a different TIU, all DCS control was lost.
• When the engine was driven back onto tracks connected to its home TIU, DCS control was re-established.

One other observation is that a TIU to use for the All Engines session was not requested by the app.

I am not sure if the observation below has been already identified as a "known bug", so here it is:

As per the screenshots 1-2-3 attached, the "Engine Features Reset" on the IOS App does not display any acknowledge message, and it also completes with an error message "Command Failed" when executed on a setup with multiple TIU/WIU (i.e. Super TIU Mode).

As per the video attached, the same "Engine Features Reset" works perfectly when executed from a remote handheld on exactly the same setup and the same engine.

Note: Our Club setup is: 4xWIU/TIU, Home-Mode via WiFi-Router, TIU DCS 6.0, WIU F/W v1.1,  Premium IOS App V2.0.0, Remote Handhelds and IOS Apps in Super-TIU mode for all 4xWIU/TIU.

Just got a new TIU Ver 6, and android app ver 2.0.0 build 37

Replaced old TIU, deleted old TIU from remote and added new TIU 3, added engine with handheld and it worked fine.  Note I lost all engine and started fresh.

Connected WIU to TIU, downloaded app (then upgraded to premium), connect android phone to MTH network and ran app and it connected.

Tried to add engines but it found none.  I have the same engine on the track that the handheld remote just found.  Reading did nothing.  Recycled power and still no engines.

Tried to add Legacy engine and that did not work either. 

Am I missing something.  It should work right?

Rich

Rich,

From an earlier post above:

I always do an app Refresh whenever starting up an app for the first time during an operating session. It's not apparent, to me, that the app will initiate a full Refresh on its own, and until it does, it has no real knowledge regarding what is the state of the layout, even assuming it's the same layout it to which it was connect when it last was used.

Rich:

You might want to consider doing a remote backup, change the file extension to .mth, then import it into the WiFi app.  As documented above by Barry you send an email with the *.mth file attached.  Open up the email on the device you want to run the trains.  When you select the attachment the WiFi app will process the file by importing it in.  Everything saved in the remote should then be accessible by the WiFi app.  

My experience was unbelievable.  Took less than 1 min to import and everything seems to be working.  92 switches, 55 engines, 25+ accessories, multiple routes.  Everything was imported and working great.  I was a little skeptical of the WiFi App but I am having a lot of fun running the trains with it on a IPAD.  This old man had too big of hands and fingers, constantly breaking the thumb wheels and having problems seeing the remote screen.  All in the past now!

Daniel,

As per the screenshots 1-2-3 attached, the "Engine Features Reset" on the IOS App does not display any acknowledge message, and it also completes with an error message "Command Failed" when executed on a setup with multiple TIU/WIU (i.e. Super TIU Mode).

I replicated the bug and reported my findings to MTH as follows:

Intermittently, when attempting a Feature Reset of a DCS engine, the reset is accomplished, however, an error message, "Command Failed", is displayed.

In attempting to reproduce the issue, I found that it appeared to most often occur just after the engine was started up. However, it could occur at other times, as well.

The good news is that the reset is always accomplished. I verified this by setting engine sounds to zero and they always came back on at 100% after the reset. This would classify it as non-operation affecting and therefore cosmetic.

Further, the problem is intermittent and may, or may not, occur at a particular time.

Thanks for reporting this issue.

Barry,

  Is it necessary to do the refresh as the very first thing after clicking "Run My Trains"?  Because I tried refresh many times and it still does not work.  I may not have tried it as the very first thing, but not likely.  I'll try again tonight.

Gary,

  Thanks but too late, my remote data is gone.  No problem though, I don't have that many switches and I was planning on renaming them anyway.  I'm glad your experience was easy, mine is not.  I'm trying to incorporate this in my next video and I need to be spending time on the video and not troubleshooting something that should be working.  I must have angered the DCS Gods.

Rich

I wish I could help.  But I am not knowledgeable or have any experience with an android.  Is the app finding the TIU?

Rich,

I may not have tried it as the very first thing, but not likely. 

You may have some other issue. More detail might help diagnose what's going on:

• Has it ever worked?
• What is the status of the LEDs on the WIU?
• How are you and the WIUs connected to the network?
• Etc.

Note that cycling power sets you back to waiting for network connections to happen..

Thanks anyway Gary.  The app must be finding the TIU because there is no error message like I get when the TIU is un-powered or the WiFi not on.  Also, I tried my sons new iPhone and that has a different problem, after refresh or trying to add engines it pops up an error message saying "connection timeout" or something about timeout can't exactly remember. 

Barry,

  Just got a new TIU and Wifi unit directly from Andy yesterday.  It has never worked.

Can't remember the exact state of the LED's but I do know several are on and some blinking.  I'll look tonight.

I am using the simple MTH network to connect to my phones wifi and not going through the home network.  Both my android and sons iPhone connect to the MTH wifi with no problems.

I am aware of the Wifi start up time. 

Rich,

I sent you an E-mail.

Barry Broskowitz posted:

Daniel,

As per the screenshots 1-2-3 attached, the "Engine Features Reset" on the IOS App does not display any acknowledge message, and it also completes with an error message "Command Failed" when executed on a setup with multiple TIU/WIU (i.e. Super TIU Mode).

I replicated the bug and reported my findings to MTH as follows:

Intermittently, when attempting a Feature Reset of a DCS engine, the reset is accomplished, however, an error message, "Command Failed", is displayed.

In attempting to reproduce the issue, I found that it appeared to most often occur just after the engine was started up. However, it could occur at other times, as well.

The good news is that the reset is always accomplished. I verified this by setting engine sounds to zero and they always came back on at 100% after the reset. This would classify it as non-operation affecting and therefore cosmetic.

Further, the problem is intermittent and may, or may not, occur at a particular time.

Thanks for reporting this issue.

Thanks to you for confirming so quickly and for following up to MTH !  

Daniel,

This morning I verified that the issue only occurs when doing a Feature Reset on an engine associated with a TIU that's in  Super TIU mode. When the engine is on a track belonging to a TIU in Normal TIU mode, Feature Reset works as expected.

I've updated my findings with MTH.

Barry Broskowitz posted:

Daniel,

This morning I verified that the issue only occurs when doing a Feature Reset on an engine associated with a TIU that's in  Super TIU mode. When the engine is on a track belonging to a TIU in Normal TIU mode, Feature Reset works as expected.

I've updated my findings with MTH.

Barry,

That is exactly what I have observed too.

Thanks!

At the request of Barry, since my layout is androidian, I fired up the layout this evening to see what happens when I try a feature reset on a loco with Super TIU on and using the WIU and premium app.  No problems or messages encountered. 

RJR posted:

At the request of Barry, since my layout is androidian, I fired up the layout this evening to see what happens when I try a feature reset on a loco with Super TIU on and using the WIU and premium app.  No problems or messages encountered. 

Hi RJR,

By curiosity, how many TIU/WIU did you use for your Android test ?  Home Mode ? MTH Mode ?

Remarks:

I did not observed any "Command Failed" on IOS App when using a setup with only 1 TIU/WIU (Super Mode or not).  

The "Command Failed" observed occurs when using multiple TIU/WIU : ref: "... completes with an error message "Command Failed" when executed on a setup with multiple TIU/WIU (i.e. Super TIU Mode)..." [ https://ogrforum.ogaugerr.com/...72#73087246196738772 ]

Our exact setup is : 4xWIU/TIU, Home-Mode via WiFi-Router, TIU DCS 6.0, WIU F/W v1.1,  Premium IOS App V2.0.0, Remote Handhelds and IOS Apps in Super-TIU mode for all 4xWIU/TIU.

Daniel,

Robert is an Android beta tester whereas I use iOS. He operates in Super TIU mode and has either 2 or 3 TIUs active, as do I. That's why I asked him to attempt to replicate the problem.

Since this now appears to be an iOS-only issue, I'll update my information with MTH appropriately.

Robert - thanks!

2 TIUs.  2 WIUs. MTH mode. Super mode.

Barry Broskowitz posted:

Daniel,

Robert is an Android beta tester whereas I use iOS. He operates in Super TIU mode and has either 2 or 3 TIUs active, as do I. That's why I asked him to attempt to replicate the problem.

Since this now appears to be an iOS-only issue, I'll update my information with MTH appropriately.

Robert - thanks!

Barry,

Just to confirm your comments, I have used an Android Premium App (V2.0.0 build 37) on our club`s 4xTIU/WIU layout tonight and I did NOT have any "Command Failed" message while doing an "Engine Features Reset".  I have used a Samsung Galaxy Note II loaded with Android Version 4.3.

During the same session and under exactly the same conditions, the "Command Failed" message was consistently occurring while doing an "Engine Features Reset" on the IOS Premium App (V2.0.0) on an iPhone 7 loaded with IOS 10.3.2

Note:  As a first impression of the Android App, I found that it was somehow slightly more responsive.  For example, moving an engine from the Inactive list to the Active list was faster on the Android App than on the IOS App.

I didn't get the book yet Barry, but everything is up to 6.0. Before I upgrade the app, I have a couple questions. If they we covered here previously, I apologize. I have 2 iPhone's and 2 iPad's in my home all in my name and sharing data. When I download the app I assume it will be on the 4 devices. But it can only be used on one device at a time. Is this correct? If I have a visitor with the free download app, I assume he can run some of the trains even though I have two tiu's in the super mode. I'll have to be careful to keep the visitor on the one tiu. Is this correct?

GHD posted:

... I I have 2 iPhone's and 2 iPad's in my home all in my name and sharing data. ... But it can only be used on one device at a time. Is this correct? ...

You can use many iPhone`s and iPad`s simultaneously. 

I use two iPad`s, two iPhone`s and a remote handheld often to do tests. (see image)

It is just like using multiple remote handhelds on a same system.

I assume you only paid once for downloading the app for all the devices?

GHD posted:

I assume you only paid once for downloading the app for all the devices?

Yes !

When I download the app I assume it will be on the 4 devices.

No, you have to download it once for each device.

But it can only be used on one device at a time. Is this correct?

No, it can be used on all devices at once, if you so choose.

If I have a visitor with the free download app, I asume he can run some of the trains even though I have two tiu's in the super mode

The visitor can run any train as long as he doesn't take it from one TIU's tracks to another TIUs tracks.

I'll have to be careful to keep the visitor on the one tiu. Is this correct?

Yes, that's correct. If he strays to another TIU's tracks, he'll loose control of the engine.

This and a whole lot more about DCS WiFi is all in MTH’s “The DCS WiFi Companion 1st Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store!

Thanks Barry. My Beta site has just started testing. Thanks to you, I got the banana plugs, moved the tiu's to a more convenient spot, had everything upgraded to 6.0, hooked up the wifi unit and ran some trains using it with my iPhone. My next test will be to use my mini iPad. I have my 4 Apple devices linked together to share data. When I downloaded the app last year, it showed up on all 4 devices and seemed to work ok. I'm guessing that when I return with the mini, I'll have to go through the find the engines again. I'll have to see if that info transferred from the phone to the mini. The jury is still out at this point on retiring the remotes.

I'll have to go through the find the engines again

Just export the file from the iPhone and import it into the iPad Mini. You can use AirDrop and it only takes a minute or two, total time. Then, refresh the iPad Mini.

This and a whole lot more about DCS WiFi is all in MTH’s “The DCS WiFi Companion 1st Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store!

Barry Broskowitz posted:

Just export the file from the iPhone and import it into the iPad Mini. You can use AirDrop and it only takes a minute or two, total time. Then, refresh the iPad Mini.

Wonder why the ability to share rosters among controllers isn't built in?

I guess the WIU/TIUs dont store this info - and its stored on each phone?

System is good for MTH engines. I 'm starting here with 2 tiu's in the super mode and one Wifi unit connected to tiu1. Seems good so far. But now I'm trying to add a tmcc engine and not having any luck. The wifi instruction book doesn't cover this that I saw. A little help here please. Thanks 

Wonder why the ability to share rosters among controllers isn't built in?

I guess the WIU/TIUs dont store this info - and its stored on each phone?

You answered your own question!  

The wifi instruction book doesn't cover this that I saw. A little help here please.

Help will be found in The DCS WiFi Companion 1st Edition, Part VII - Engine Operation Using the DCS Application, on pages 48-68.

This and a whole lot more about DCS WiFi is all in MTH’s “The DCS WiFi Companion 1st Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store!

I figured it out and all is well. Thanks Barry. Your book is next on my list,especially now that I'll be using the system. I haven't decided on digital or hard copy yet. I'm old fashioned and will probably go for the paper. Thanks again.

Barry Broskowitz posted:

Wonder why the ability to share rosters among controllers isn't built in?

I guess the WIU/TIUs dont store this info - and its stored on each phone?

You answered your own question!  

It explains it - but really doesn't answer "why?" - seems like an important missing feature - and forces a kludgy workaround.

Wonder this is something they can address with a software update?

Is it the same with Android?

Not only is it the same in both app platforms, IOS and Android, that's how it's always been when using the DCS Remote.

Regardless, using the app import/export feature makes it quick and easy to share engine rosters and everything else between apps.

For what it is worth, I have been using DCS wifi premium with IOS on an ipad (which I chose because of the larger screen) and have been able to set up a 4 locomotive TMCC lashup, run an MTH loco with quillable whistle, and have had few problems.  There do seem to be a few missing features in the TMCC operations, but I am not even sure of that.  I was able to rename the Aux sounds with the app, and also the MTH DCS added sounds, which is REALLY nice, especially with the large screen so I can actually read them.  I only have one TIU and had to learn to wait for the wifi to really get connected and running before trying to run trains.

Barry Broskowitz posted:

Not only is it the same in both app platforms, IOS and Android, that's how it's always been when using the DCS Remote.

Regardless, using the app import/export feature makes it quick and easy to share engine rosters and everything else between apps.

Right - but its not unrealistic to expect a "roster sync" function - given we're heading into a new generation of technology.

Consider it a feature request and not a complaint.

Need a little help here Barry with something you're very familiar with---your book. I went to the MTH site but it was not working. Maybe later?? I also looked at the O gage site thinking they might have the paper version. I didn't see anything there. I'm actually thinking about buying both. Do you know anyone that might be able to get a deal here? ��Thanks 

The following links each go to their respective eBook and print book.

Link for The DCS Companion 3rd Edition: http://mthtrains.com/DCS_Companion

Link for The DCS WiFi Companion 1st Edition: http://mthtrains.com/news/596

This links were fine a few minutes ago.

Thanks, the link worked and I ordered both paper and E. Now you can retire, but please don't. We'll need you more than ever now! I'm digging to see what happens when I buy the second wifi unit to install on the second tiu and get it working.

Thanks for buying the books!  

Barry Broskowitz posted:

Just export the file from the iPhone and import it into the iPad Mini. You can use AirDrop and it only takes a minute or two, total time. Then, refresh the iPad Mini.

I totally agree that using AirDrop between IOS devices is great for the Export/Import process.  Really simple and fast.

Question for the Android folks:  Is anyone using a good "equivalent" of AirDrop on Android ?  Since at our club we have users on both Android and IOS, ideally, something that works like AirDrop between Android and IOS would be best.

Dropbox Alternative:  While using Dropbox is an excellent alternative for both IOS and Android, for some reasons, the Export to Dropbox does not seems to work (on Android) or be available (on IOS).  See attached screenshots.  The Import function works fine from Dropbox on both Android and IOS.

Daniel Auger posted:

Barry Broskowitz posted:

Just export the file from the iPhone and import it into the iPad Mini. You can use AirDrop and it only takes a minute or two, total time. Then, refresh the iPad Mini.

I totally agree that using AirDrop between IOS devices is great for the Export/Import process.  Really simple and fast.

Question for the Android folks:  Is anyone using a good "equivalent" of AirDrop on Android ?  Since at our club we have users on both Android and IOS, ideally, something that works like AirDrop between Android and IOS would be best.

Dropbox Alternative:  While using Dropbox is an excellent alternative for both IOS and Android, for some reasons, the Export to Dropbox does not seems to work (on Android) or be available (on IOS).  See attached screenshots.  The Import function works fine from Dropbox on both Android and IOS.

 

Absolute nonsense that it should require an internet connection to make this happen.

Barry Broskowitz posted:

Absolute nonsense that it should require an internet connection to make this happen.

In the case of iOS, the Internet is not required to use Import/Export.

You only need an Internet connection if you're attempting to use the Internet as part of the transfer process, e.g., via E-mail. Using AirDrop on an iOS or MacOS platform does not require Internet availability.

Although I've heard that there's an AirDrop-like function for Android platforms, I know nothing about it.

Regardless, transferring data between devices is most certainly not a capability that's built into any app. Rather, it's a function of the platform's operating system. The app maker has to use the native iOS or Android capability.

Thanks for the clarification on the AirDrop - Is this a peer-to-peer process? i.e you don't need a active cell connection to make it happen?

Im a sound engineer...I use tablets to run my digital mixer - one for me (house mix) - and one for stage monitors.

Last night I had two guest musicians - and had to add them to the mix scene.

Well - I only have to add them once and all the other devices sync to those changes...doesnt matter if the tablets are IOS or Android - it would be ridiculous to have use an external process/program to do this.

I would have repeated the same thing 3 times!

Locomotives should be no different than musicians!

Is this a peer-to-peer process? i.e you don't need a active cell connection to make it happen?

That's correct.

If I understand you correctly, your music system automatically syncs devices. That's fine when all devices always need to be in sync. However, with DCS devices, be they DCS Remotes or smartphones/tablets running the DCS App, automatic syncing is not necessarily desirable. Each instance of DCS information may be unique, with different contents in each.

For example, I have multiple remotes:

• One has all of the 97 DCS engines in it that are run as individual engines. It also has all of my switch tracks, accessories, Routes, and Scenes.
• Another has those engines (12) that run only as lashups (6). In addition, this remote also contains all of my TMCC and Legacy engines (2) and a host of operating cars (20) that use TMCC via installed Electric Railroad Mini Commander boards. This second remote reuses DCS ID#s. It also has all of the same switch tracks, accessories, Routes, and Scenes that are in the first remote.
• A third remote is kept empty of engines and is used for test purposes.

Regarding the DCS App, I've made clone backups of the first two remotes and E-mailed them as attachments to myself on each of my 3 iOS devices. Now, I can load, in a minute or less, the contents of either one of these remotes simply by importing one of the attached files. No Internet or other connection is required, once the E-mails with their attachments are on the subject smartphone or tablet.

This whole scheme would be impossible if these devices automatically synced with each other.

On a related note, auto-syncing is what Legacy does, between all of the Cab-2 remotes, and the iCab and LCS apps. This has both pos and cons.

A pro is that when one goes to a club or some other Legacy layout, any Cab-2 or app that one brings is automatically loaded with the contents of that layout's Legacy command base.

The cons are twofold. A minor one is that in order to run an engine that one brings to another layout, one must add that engine to the layout's Legacy base first. Second, and much more importantly to me, I cannot use the method described above to have more than 100 engines available at al times.

This is by no means a knock on Legacy. Its simply a fundamental difference between the two systems that allows me to run my trains, my way.  

The scheme I described above is the subject of Appendix D: More Than 100 Command Control Engines, on pages 191-192 of The DCS WiFi Companion 1st Edition.

This and a whole lot more about DCS WiFi is all in MTH’s “The DCS WiFi Companion 1st Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store!

Barry, I want to compliment you on the book. It is a complete explanation of the system and very well done. I was expecting a focus on wifi and not the complete system. I highly recommend this to anyone using DCS. Don't miss out on features of DCS that you didn't know existed! Great job! Thanks 

Great job!

Thanks for the kind words - they're appreciated!

Ok, I knew things were going too well.  Three weeks or running trains after importing everything from my main remote.  Everything responding great.  Then:

Tried to add a new engine just purchased MTH 30-20355-1 R33 Subway.  No engines found interrogating engines timed out.  Picked up remote added no problem.  Went back to App and same as before.  Now I started checking the status of TIU's found.  All over the map.  Sometimes a refresh and using advanced features, System Settings, TIU Settings no TIU's found.  Other times found all 3 TIU's I have and other times 2 TIU's Found.

Brought up router Asus RC5300.  Saw all three MTH WiFi's running in DHHP mode and signal strength of 2 bars.  Clicked on IP Address to change to Static IP.  And while I find no documentation anywhere on password for WiFi device remembered in Barry's book one that was MTHDCSWiFi.  When that failed I was very frustrated but tried MTHDCS.  This worked, so everyone take note!  Found screen to change mode to Static IP and put in the same addresses that was found when I first brought up router.  Ignored Subnet Mask, or something like that.  Would verify but now I cannot reach the MTH WiFi's no matter what I have done or tried.  So, I found reset button on each of the three WiFi's and pressed them.  Based upon MTH Manual this sets the WiFi back to factory settings.  Maybe but doesn't seem to set the mode back.  I shut everything down, rebooted router, turned everything back on.  Router found MTH WiFi units, all three and showed them in "Static" mode, even though I had reset each MTH Wifi by pressing the reset button.  Tried to gain access by clicking on IP address and error message.  Tried the app and can't find any TIU's?

So I am dead in the water, and more than a little frustrated.  Since every common sense thing seems to have failed.  Granted I should have stopped when changing the IP Address to static and didn't know what to do with Subnet Mask of whatever that questions is?

Barry, I need your help with trying to gain access back to the MTH Wifi units (3) and why I cannot add engines in app even though I can with remote?

The problem is on the WiFi side of things.

I suggest that you connect the MTH WIUs in MTH mode rather than Home mode. In actuality, this connects the first WIU in MTH mode and then the remaining WIUs are set to Home mode, however, they connect to the first WIU as their router instead of your Home router. If this works, then the home router was somehow contributing to the problem.

Use the instructions on pages 44-45 of The DCS WiFi Companion to first setup one WIU in MTH mode and the remaining ones in Home mode, connected to the first WIU. The WIU's network password is, indeed, mthdcswifi (all lower case) unless you or someone else changed it.

After setting up all of the WIUs, ensure that you can access them from the app. Run the app from the initial startup screen (the "Run My Trains" screen) and do a refresh on the Engine Control screen after all of the WIUs are stable, as indicated by their LEDs.

If you'r connecting the WIUs to TIUs via the Rev. L TIU's USB port, make certain the the TIU does not have an unterminated cable hanging off its serial port. It's OK to have the serial port connected to another device, such as a Legacy or TMCC command base, or an SER2 module. Just don't have an unterminated cable hanging off the serial port.

Once you can see stable TIUs from the app, we can proceed further.

Ok, that was the next thing that I was going to do.
Shouldn't I still be able to enter a WiFi unit's ip address in a web browser and bring it up? This is where the login is set to root and the password is MTHDCS. Because right now I can't even do that?

gsn,

I read through your (longer) post and it sounds like your ASUS router is assigning the WIU's a static IP address as you instructed it to.

Saw all three MTH WiFi's running in DHHP mode and signal strength of 2 bars.  Clicked on IP Address to change to Static IP.

Resetting the WIU's to factory default will not change the automatic IP assignment setting in the ASUS router.  If you reset the WIU's to default settings, you will need to re-associate them with your ASUS router using the WPS button.

You can set the IP address statically in the WIU via the LuCi web interface but you must also set the Subnet Mask properly as well. In most cases this will be 255.255.255.0 on 99% of home networks.

Does anyone know what happened to the red  "Emergency Stop" icon that used to appear on the screen of the variable track power screen? Someone must have wrongly assumed it was unnecessary. It would be nice as a first line of defense for the many instances the TIU power suddenly surges to 20 volts with no explanation, or control is lost and the engine just rolls off somewhere. At least, it might make me feel better... kind of. Ultimately, I have to quickly pull the plug when I receive these random Wi-Fi disconnects that cause runaways and crashes. 

Barry,

Ok, switched WiFi (TIU 1) to MTH mode

APP found MTH_DCS-30A8 (30A8 being last four of Mac Address)

powered off WiFi #2 and back on

pressed WPS WiFi #1

pressed WPS WiFi #2

mode selected to Home

White light started blinking then solid

WiFi #3 repeated, white light never stopped blinking

App still reporting MTH_DCS-30A8 

IP Address 192.168.143.194

Subnet Mask 255.255.255.0

Router 192.168.143.1

DNS 192.168.143.1

APP didn't find any TIU's

??

Greg, it's still there, except that it's hidden by default.  Search back in settings and you can restore it.

H1000

How do I set subnet mask if I cannot access WiFi unit with web browser?

I still see the IP Address listed on devices for router but can't click on IP Address, as I did to change to static, doesn't even give me an option.

Not being all that tech savvy, I'm not enthusiastic over the demise of the handheld. It allows touch typing ergo eyes on trains. I don't want to be one of those zombie cellphone idolators mesmerized by the almighty screen. By the way, what happens when operating the dam phone rings? Sometimes I think progress is way overrated. And Barry, this is no knock on you. Your book is my bible and your forum tutorials are invaluable.

I want to retire my DCS remote and stick with the premium APP, but I use the MIC function (where you talk into the remote and it comes out the engine) a lot for station announcements and stuff.

I can't find the same function in the premium APP.  I guess it doesn't do this?

gsn1 posted:

H1000

How do I set subnet mask if I cannot access WiFi unit with web browser?

I still see the IP Address listed on devices for router but can't click on IP Address, as I did to change to static, doesn't even give me an option.

You can't click on the IP addresses on your router because the WIUs are no longer connected to your router via the wireless connection. Your router remebers the previous connection to the WIUs but also knows that the WIUs are not available anymore.

It sounds like the signal strength between your home internet router and the WIUs is a little on the low side. I would proceed as Barry suggested earlier. You will have to designate one of the WIU's as the "master" and set it to MTH mode. The master WIU will now send signals to an from your Phone / Tablet and be responsible for relaying signals to other (slave) WIUs when they are associated using the WPS button. 

Make sure the Master WIU is in MTH mode and the other (slave) WIUs are HOME mode when you proceed as Barry suggested.  This process is described in detail in his WIFI Companion on pages 44 & 45.

H1000

I followed Barry's recommendation and reported back, see above.  Haven't heard back from him on next steps.  To summarize the Master Wifi unit set to MTH mode was successful and showed up on Ipad.  2nd Wifi unit set to home appeared to have been successful in that the white light blinked and then shut off.  The 3rd Wifi unit set to home was not successful, white light never stopped blinking.  Even though the App showed the MTHWifi it never found any TIU's.

So, my question is since I screwed up when setting the IP address by not putting in the Subnet Mask, which I assume is the 255.255.255.0 how do correct that?

This morning I hooked Wifi unit directly to router with ethernet cable and it doesn't show up as a device.  Does a TIU have to be connected in order for it to show up?

Barry

I'm stuck Tried your suggestion setting Master to MTH and it seemed to work, accept for #3 Wifi unit.  But app, while seeing the MTH network didn't pick up any TIU's?

If the Subnet Mask on each Wifi unit was set to blank, due to my stupidity, how do I correct that?  Or does it need correcting?

You need to go back to "square 1".

My suggestion is that you call MTH and ask a tech to help you reset all 3 WIUs back to their true factory settings.

Then, set the WIUs up in a basic configuration without doing any fiddling with settings. That will establish a baseline before you modify anything that you shouldn't.

Further, unless you have a high confidence that you understand how things work, stay away from LuCI in the future, except for firmware updates. While adjusting settings may allow your WIUs to come online a bit faster, the down side is, as you

You've learned, the hard way, that by using LuCI to adjust WIU settings, you can cause serious self-inflicted problems.

Agreed, big mistake touching LuCI.  Because ever since I did that the Wifi units have not been reachable.

I will email you on contacting MTH

Any news about any future updates for the Premium app?

The system is not finding the TMCC engines on a refresh. I hope you don't have to readd them each time. What am I missing? I haven't memorized the book yet.

GHD posted:

The system is not finding the TMCC engines on a refresh. I hope you don't have to readd them each time. What am I missing? I haven't memorized the book yet.

The app does not "read" TMCC / Legacy engines into the active list. If you have already added them, they should appear in the inactive list. Click "edit" in the upper left corner, and then drag the desired locomotive up to the active category using the triple line symbol to the right of each engine. Once you have moved a loco up to the active category, press "Done" in the upper left corner.

Using the refresh button will send all TMCC / Legacy locos back to inactive status because they cannot be read and will not be found. Only DCS locos seem to be loaded automatically.

I see on page 62 that you can manually move an engine between active and inactive. Is this required for tmcc engines? 

Thanks. I guess I found the answer in the book too. Good thing I don't run many tmcc engines. I've been impressed so far with the system finding the engines on the layout. I knew I had quite a few engines on my layout, but not as many as the system found. That is a nice feature of the system, being able to see the complete list. Good thing the wife doesn't know how to use the system!

I see on page 62 that you can manually move an engine between active and inactive. Is this required for tmcc engines? 

Yes, and also for DCS and TMCC/Legacy lashups. Just like the DCS Remote after a READ.

This and a whole lot more about DCS WiFi is all in MTH’s “The DCS WiFi Companion 1st Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store!

Thanks Barry. I never use the read feature and that was one of my concerns with the new system (wifi) finding engines. But so far so good. It found over 40 engines on my layout. That number even surprised me!

I can not tell if the smoke is on or not without looking at the engine. The icon color does not seem to have a consistent pattern. The remote gives a clear indication if it's on or off. Am I missing something here?

I can not tell if the smoke is on or not without looking at the engine.

Look at the Engine Features Screen on page 52 of The DCS WiFi Companion 1st Edition. Just like the headlight and engine sound icons, the smoke icon gets dark (purple) when smoke is on and clear when smoke is off.

Thanks Barry, now that I know how it is supposed to work I checked it out on my MTH engines and it is fine. However, last night when I posted this question, I was operating my Lionel challenger. So I tested that tonight and can tell you that the color code doesn't hold true on it. So I guess this is a tmcc thing? I also found another interesting thing. I tested a tmcc diesel engine that I had upgraded using Trainamerica and ERR stuff before Lionel got involved. It worked correctly. Also interesting was the fact that the engine screen with the speed dial came up with numbers on it. The tmcc engines typically come up without numbers. I haven't touched a remote now in a couple of days.

I've read through this thread and the other thread and checked the wi-fi companion but encountered an issue adding a Legacy engine that I haven't seen discussed.  I have the latest firmware and correct cables.  When I added a Legacy engine that had an ID of "2" to the app, icons (speed, whistle, etc.) would move but nothing would respond.  The red light on the Legacy base did not blink.  I added the engine to the DCS remote and it worked fine.  I tried adding a different Legacy engine with an ID of "11" to the app and it worked fine.  I then reprogrammed the original engine to an ID of "12" and it worked.  I'm curious what type of conflict there might have been.  The original engine had already been programmed in Legacy with an ID of "2" and I simply wanted to continue using that in the App. 

Pretorius,

You need to read this thread from beginning to end.

Barry Broskowitz posted:

Pretorius,

You need to read this thread from beginning to end.

I read that thread before I posted, but didn't see the commensurate issue I experienced.  I didn't report that the  engine wouldn't work in Legacy mode - it didn't work at all in the app until I changed its ID.  Perhaps the issue is related to the thread you cited but it's not clear to me.  

I expect that it was the engine's TMCC ID# 2 that you changed.

If you could change it using the remote's Edit Engine command and the app's Engine Settings screen, and using the RUN/PROG switch, it must have been the TMCC ID#, and it was most likely either entered wrong in the app in the first place or the TIU Number to which the command base is connected was entered wrong. Since the command base's red LED didn't blink when a command was issued, I suspect it was the latter.

Regardless, it's now impossible to know what exactly was wrong.

Does anyone know how to get Lionel TMCC and Legacy loco prime mover sounds to rev up and down automatically in response to throttle movement? I have tested about 10 engines, and the sounds remain at a flat "idle" sound regardless of how fast I run them. It's like the MTH app forces all Lionel locos into manual RPM mode and there is no way out of it.  If I switch from the MTH app, to control my trains using  the CAB-1L or CAB-2, the RPM's go up and down just fine. So far, the only way I have found to accomplish this, is to make manual adjustments to rpm, which really isn't that great.

Back to the smoke on-off . I did a check with the engines on my layout, all MTH. None of the engines had the smoke turned on. The icon for more than half the engines indicated the smoke was on. This takes me back to I have to look at the engine to see if the smoke is on or off. I guess this is the way it is unless I'm missing something. 

The remote or the app device has no way to know the smoke setting if it was set from another device.  It only knows the last command it sent.  When I power up my layout, the device also has no way of know in which direction switches are set.

Not a new issue.  When using remotes, if I set a loco at 40, and then with another remote set it as 10, the first remote continues to show 40.

Thanks. This is what I gathered. I'm going through these exercises to make sure I understand what is happening and why. The "Book " is good but doesn't cover some of different things. I just did a record/playback session but used the remote. One little touch of the iPhone screen by mistake and the fun can begin. At this point I'm using both.

GHD, I think I have the same issue. I have an MTH F40PH that always powers up with smoke on. Even though the app says it's off. So, I have to press the smoke button twice to turn it off. 

I have another thing I need to check out. I was under the impression that when I had my tiu's updated I would lose my record/playback sessions. I don't think that is the case. I know that the beginning of a session is there,but I haven't played the whole session. When I started to record a new session using my iPhone, I had some funky stuff happen and that led me to suspect the existing sessions. The remote worked fine as always. More fun!

I was under the impression that when I had my tiu's updated I would lose my record/playback sessions. I don't think that is the case.

Whoever told you that, was mistaken. Your TIUs will not lose their Record/Playback sessions unless they are Factory (not Feature) Reset.

When I started to record a new session using my iPhone, I had some funky stuff happen and that led me to suspect the existing sessions.

What kind of "funky stuff" did you experience?

The only Record/Playback issue of which I'm aware is that of a bug in the app that only appears in Super TIU mode. The app only records switch track and accessory operation from the TIU that's selected when recording the session. When recording under Super TIU mode using the remote, even though it's required to select a TIU, the session uses all TIUs and is recorded in all TIUs.

This is on the list to be corrected in a future release of the app.

Barry the funky stuff that happened was my fault. My first attempt using the iPhone and I hit the play button instead of record. But this woke me up to suspect that sessions were still in the tiu. I was also pleasantly surprised to learn that the tiu's held their settings after the upgrade. I was planning on having to set them back up again. Since I use two tiu's in the super mode and only one aiu, I assume I won't be impacted by the bug?

Since I use two tiu's in the super mode and only one aiu, I assume I won't be impacted by the bug?

When we were beta testing, I did a recording with switch tracks on TIU #1, AIU #1 and TIU #2, AIU #1. On playback, only the switch track on TIU #1, AIU #1 played back.

While I know for a fact that only the first switch track was actually recorded (MTH confirmed this), what I don't know is if a recording that was made with a remote and that had both switch tracks, would have played back both.

If your single AIU is on TIU #1 and you select TIU #1 for the session, all should work well. However, if your AIU is on TIU #2 and you select TIU #1 for the session, you most likely wouldn't have either switch track work at all on playback.

Thanks. I should be ok. I assume this doesn't apply to using the remotes. It's an iPhone app bug and not a 6.0 problem?

I assume this doesn't apply to using the remotes. It's an iPhone app bug and not a 6.0 problem?

That's correct.

I really like the app and the abililty to export engine lists to other devices.  I would still like to have my dcs remotes available for running trains and have them match engine list modifications made with the app..  I could use the read function for loading Mth engines, but run lots of tmcc engines i would like to be able to add into the app and then export into the mth remote.

I have read through this entire post and saw a small mention of the mth app export cannot be used to import into the remote, are there any work arounds for this?

looking at the files themselves, the app file export looks to have structured text as the remote file doesnt.  I did notice in the app file there appeared to be a data section for each engine that looked like it might be the same info that the remote has?

thanks,

Mike

Mike,

I have read through this entire post and saw a small mention of the mth app export cannot be used to import into the remote, are there any work arounds for this?

No, there is not.

looking at the files themselves, the app file export looks to have structured text as the remote file doesnt.  I did notice in the app file there appeared to be a data section for each engine that looked like it might be the same info that the remote has?

The file structure for remote backup files and app export files are radically different. The app export files are much easier to read and understand. They also have settings that the remote cannot handle, e.g., Legacy engines.

Are there any plans to enhance the premium app to control Lionel wireless command-control switch tracks?  Apologies if this has already been asked.

I may have missed this in the previous messages but I am having an issue with blank engine names showing up when reading previously found engines.  It is an intermittent problem from what I can tell.  I am using the premium app on an android tablet running android version 6.0.1.  I do not own any apple products so I can't use that as a comparison.  My TIU, remote and dcs wifi unit are all updated to their respective latest versions. 

My sincere thanks to all who have worked on the MTH  Wifi DCS system.  I have had very few issues that were not caused by a carbon based user error.  I have read the MTH manuals, Barry's E-Book and this thread and other forum posts.

Again,

THANK YOU

GManning35 posted:

H1000 posted:

Here is a video of the problems I am having when creating a route:

H1000

This is exactly what I have. I've tried and tried to trick the app into getting all the switches right and it may work right once but then keeps changing what switches are thrown and what direction by itself. No way to get a route or scene set up. I now tried my old Motorola Droid and it has the same issues so it's not android software version specific.

 George 

What version of the Android app are you guys running.  We had this issue in the initial release however, it was supposed to have been corrected with the recent update we released a few weeks ago.

MTH RD posted:

GManning35 posted:

H1000 posted:

Here is a video of the problems I am having when creating a route:

H1000

This is exactly what I have. I've tried and tried to trick the app into getting all the switches right and it may work right once but then keeps changing what switches are thrown and what direction by itself. No way to get a route or scene set up. I now tried my old Motorola Droid and it has the same issues so it's not android software version specific.

 George 

What version of the Android app are you guys running.  We had this issue in the initial release however, it was supposed to have been corrected with the recent update we released a few weeks ago.

My issue with the routes have been resolved with the recent update to the Android app.

 And after all these months I can finally control my routes and scenes on my Android phone also. Since the recent updates I've really enjoyed my layout much more and haven't had any reliability issues either. 

GManning35 posted:

 And after all these months I can finally control my routes and scenes on my Android phone also. Since the recent updates I've really enjoyed my layout much more and haven't had any reliability issues either. 

Ahhhh.....music to my ears!!  Ha, ha...

As you all well know, the system has many capabilities and therefore, is complex.  We deal with legacy issues (in the sense of product evolution) as well as a host of variability in the field use cases.  That is, every layout is slightly different.  Our intention has always been, and will continue to be, making model railroading as simple as possible while providing feature rich products.  Our recent efforts to develop the WIU and now the Explorer and their supporting apps is just the beginning.  We can do so much more given the horse power of smart devices and some new hardware.  We just need some time and results in product sales to fuel the effort.  We can't wait to further refine and clean up issues that some of you may be experiencing.  Like I always say, almost everything is possible given time and money.

H1000 posted:

MTH RD posted:

GManning35 posted:

H1000 posted:

Here is a video of the problems I am having when creating a route:

H1000

This is exactly what I have. I've tried and tried to trick the app into getting all the switches right and it may work right once but then keeps changing what switches are thrown and what direction by itself. No way to get a route or scene set up. I now tried my old Motorola Droid and it has the same issues so it's not android software version specific.

 George 

What version of the Android app are you guys running.  We had this issue in the initial release however, it was supposed to have been corrected with the recent update we released a few weeks ago.

My issue with the routes have been resolved with the recent update to the Android app.

Great news.  You had me worried.

I have a few questions on the ap.  I am enjoying it tremendously right now for starters.

1. How do I adjust the startup speed and slow down speed of the  MTH engines?  I have them sitting on the tracks, and the ap has recognized them.  Do I need them to be on (powered up)?  I'd like have them operate more realistically when starting and stopping, yet I can't seem to get it right
2. For a TMCC Atlas engine, I have added it and after the initial running of the engine and the running session it goes to the inactive roster.  How do I get it active again?

thanks,

John