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

Been having an issue with DCS wi-fi app at the club. We have 4 TIUs with corresponding WIUs set up as "Home" using the clubs wi-fi system. When a person first logs into the DCS app and checks to make sure all the TIUs are connected, we continuously have only 3 of the 4 TIUs listed. This happens on Apple & Android devices and the missing TIU is not always the same one. When we notice that one of the TIUs are not listed, we do a system refresh on the main screen of the DCS app and only then do all of the TIUs appear.

When there is multiple TIUs, is it necessary to do a DCS app refresh every time  you log in to capture all the TIUs or is there something else going on that I am not aware of.

Thanks,

Bob D

NJ-Hi Railers

Bob,

When there is multiple TIUs, is it necessary to do a DCS app refresh every time  you log in to capture all the TIUs or is there something else going on that I am not aware of.

I also have all 3 of my WIUs connected to my home network and I operate in Super TIU mode. When I first turn on the layout, everything except track power comes on at once.

I then typically wait a couple of minutes for the WIUs to connect to the network before launching the DCS App. When I tap "Run My Trains" and the Engine Control Screen appears, I tap refresh and, with few excapriuons, the app finds all of the TIUs. If I don't wait long enough for the network connections to "settle", I may have to tap refresh once more.

One thing that I've done that your club may have not have done is that I assigned each of my WIUs a static IP address based on the WIU's MAC ID. I do this out of habit since it ensures that each WIU is always assigned the same IP address every time they join the network. This makes it easy to update WIU firmware without removing the WIUs from the layout.

I don't know if signing static IP's will help the club.You could try it and see.

Another thing you could try is to connect the first WIU in MTH mode and then it can become a router to connect the remaining WIUs in Home mode, where the Home network is the first WIU in MTH mode.

when i set up my app onto my iPhone did i use a password ?

One thing that I've done that your club may have not have done is that I assigned each of my WIUs a static IP address based on the WIU's MAC ID. I do this out of habit since it ensures that each WIU is always assigned the same IP address every time they join the network. This makes it easy to update WIU firmware without removing the WIUs from the layout.

I don't know if signing static IP's will help the club.You could try it and see.

* For a faster boot up and available of the WIU:

My WIU's are all wired to a Wireless router and the Wireless on the WIU's are disabled. Assigning a static IP and disabling the Wireless radios shaved about 15 seconds off of the "Boot Up" time for my WIU.

* Think about it, the WIU doesn't have to wait on a DHCP request from a router for an IP address nor does it have to expend CPU time to turn on the Wireless software to drive the built in wireless functions on the WIU.

Barry's method is not exactly the same, I assume he is having his internet router assign an IP address based on the MAC address of the WIU.  The WIU is still having to wait for an IP to be assigned from the router via a DHCP request.  A static IP assigned to the WIU Using the LuCi interface is faster, no waiting for the router.

Using the above method does require you to know exactly how your home network is configured exactly. Automatic configuration is easy, but a little slower.

Edited portion marked with *

Barry Broskowitz posted:

Bob,

When there is multiple TIUs, is it necessary to do a DCS app refresh every time  you log in to capture all the TIUs or is there something else going on that I am not aware of.

I also have all 3 of my WIUs connected to my home network and I operate in Super TIU mode. When I first turn on the layout, everything except track power comes on at once.

I then typically wait a couple of minutes for the WIUs to connect to the network before launching the DCS App. When I tap "Run My Trains" and the Engine Control Screen appears, I tap refresh and, with few excapriuons, the app finds all of the TIUs. If I don't wait long enough for the network connections to "settle", I may have to tap refresh once more.

One thing that I've done that your club may have not have done is that I assigned each of my WIUs a static IP address based on the WIU's MAC ID. I do this out of habit since it ensures that each WIU is always assigned the same IP address every time they join the network. This makes it easy to update WIU firmware without removing the WIUs from the layout.

I don't know if signing static IP's will help the club.You could try it and see.

Another thing you could try is to connect the first WIU in MTH mode and then it can become a router to connect the remaining WIUs in Home mode, where the Home network is the first WIU in MTH mode.

Barry

Thanks for your thoughts.  We will try the static IP setup this week and see how that works.  As for using the WIU in the MTH mode, initially we tried that and we were having reception issues at the fringes of our layout which can be ~> than 150' from the MTH WIU.  If the static IP address doesn't work, we will try installing another WIFI access point per recommendations from our IP guru, Chris Lord.

We will let you know how the static IP works out.

Thanks,

Bob D

H1000 posted:

One thing that I've done that your club may have not have done is that I assigned each of my WIUs a static IP address based on the WIU's MAC ID. I do this out of habit since it ensures that each WIU is always assigned the same IP address every time they join the network. This makes it easy to update WIU firmware without removing the WIUs from the layout.

I don't know if signing static IP's will help the club.You could try it and see.

* For a faster boot up and available of the WIU:

My WIU's are all wired to a Wireless router and the Wireless on the WIU's are disabled. Assigning a static IP and disabling the Wireless radios shaved about 15 seconds off of the "Boot Up" time for my WIU.

* Think about it, the WIU doesn't have to wait on a DHCP request from a router for an IP address nor does it have to expend CPU time to turn on the Wireless software to drive the built in wireless functions on the WIU.

Barry's method is not exactly the same, I assume he is having his internet router assign an IP address based on the MAC address of the WIU.  The WIU is still having to wait for an IP to be assigned from the router via a DHCP request.  A static IP assigned to the WIU Using the LuCi interface is faster, no waiting for the router.

Using the above method does require you to know exactly how your home network is configured exactly. Automatic configuration is easy, but a little slower.

Edited portion marked with *

The issue we are having at the club is not that the initial boot up time is long, it is that even after 10-20 minutes the WIUs/Wi-FI network have been powered up and then someone opens the DCS app, we still run into the issue of not picking up all the TIU's.  Only after doing a DCS app refresh do we see all the TIU's.

Thanks,

Bob D

rad400 posted:

H1000 posted:

One thing that I've done that your club may have not have done is that I assigned each of my WIUs a static IP address based on the WIU's MAC ID. I do this out of habit since it ensures that each WIU is always assigned the same IP address every time they join the network. This makes it easy to update WIU firmware without removing the WIUs from the layout.

I don't know if signing static IP's will help the club.You could try it and see.

* For a faster boot up and available of the WIU:

My WIU's are all wired to a Wireless router and the Wireless on the WIU's are disabled. Assigning a static IP and disabling the Wireless radios shaved about 15 seconds off of the "Boot Up" time for my WIU.

* Think about it, the WIU doesn't have to wait on a DHCP request from a router for an IP address nor does it have to expend CPU time to turn on the Wireless software to drive the built in wireless functions on the WIU.

Barry's method is not exactly the same, I assume he is having his internet router assign an IP address based on the MAC address of the WIU.  The WIU is still having to wait for an IP to be assigned from the router via a DHCP request.  A static IP assigned to the WIU Using the LuCi interface is faster, no waiting for the router.

Using the above method does require you to know exactly how your home network is configured exactly. Automatic configuration is easy, but a little slower.

Edited portion marked with *

The issue we are having at the club is not that the initial boot up time is long, it is that even after 10-20 minutes the WIUs/Wi-FI network have been powered up and then someone opens the DCS app, we still run into the issue of not picking up all the TIU's.  Only after doing a DCS app refresh do we see all the TIU's.

Thanks,

Bob D

Yep, I get that. I just wanted to provide a tip to everyone else if they wanted to find a way to reduce the time it takes for the WIU to become available for use.

Bob,

we still run into the issue of not picking up all the TIU's.  Only after doing a DCS app refresh do we see all the TIU's.

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.

while setting up switches and accessories using the premium app, I noticed that the app is not picking up my second AIU.  All of my switches and accessories on the first AIU are loaded and work fine.  I go to: Add Switch, Select TIU (i only have one), Select an AIU on TIU 1.  Only AIU 1 is listed.  My second AIU is not there.

The second AIU is in another room, so I made a custom "crossover" type cable from CAT6.  The cable length is 20 feet.  However my remote had no problems picking it up and it has worked flawlessly.  Could that be a potential issue with the WIFI app?  

No, it wouldn't be an app issue, since it's the TIU that sees the AIU's, not the app.

If the remote sees it through the TIU, the app should as well.

Hi Barry,

I decided to check the remote to see if both AIU's still appear.  They don't.  My remote now only sees one AIU.  Oddly enough, I am still able to control the pre-loaded switches and accessories on AIU 2......I just can't add anything new because it's not available when I try to add a switch.  The last thing I did was upgrade to software version 6.0.  It's possible that it wasn't seeing the second AIU before that however, as all my switches and accessories still work on that AIU and I haven't had a reason to scan for it in some time.

The DCS Remote remembers the contents of AIUs even after they're no longer seen by the TIU, and will attempt to operate connected accessories and switch tracks.

Enabling Playable Whistle - works ok at first, then locks the whistle into non responsive. Only way out is to shut everything down, including Wfi modul. Two out of three engines so far. Got version 6.0 at York.

Bob,

Known bug.

I have an export/import question when using Android devices with the wifi. I backed up my handheld, got the .txt file and, after changing the .txt file to an .mth file, successfully imported it into the 2 android dedicated devices I plan to use with my system. One is an older Samsung tablet and the other is a brand new Asus tablet. They run different versions of android.

Now, having updated the program on one device I want to export it to the other device. So I go to the Export screen (having followed the advice in Barry's book) and prepare to send an e-mail to myself and attach the file. But I have no idea where the file is and cannot find it. Can anyone help with this? I am trying to export the entire app or just a data file? What am I looking for and where is it?

Gerry

Gerry, when you use the term "program," I assume you mean the app.  That doesn't  transfer between units.  Each must get it from app store, but you only pay once.

Thanks RJR. I bought the app and installed it on both devices. Then I backed up my handheld as a .txt file, changed it to a .mth file and imported it to both devices. Subsequently, I added engines to one device and want to keep both of them in sync. When I first did this with the file from the handheld, they were in sync. Now that I've updated one device, they are not in sync. So my question is, what file and where do I find it in order to export it from the updated device to the one which has not been updated?

Gerry 

Gerry,

Tap Export and then, on an iPhone (I don't have an Android device) I see "Share" which allows me to send the export file as an E-mail attachment.

From page 115 of The DCS WiFi Companion:

Exporting the DCS Application's Contents

To export a DCS Applications contents, proceed as follows:

• Tap the Export button. A message "Export Complete" will appear along with a Share button.

• Tap the Share button to display the sharing options for the iOS or Android device.

• Choose an appropriate transfer method. Then follow the device's instructions to transfer the file.

If you intend to send the exported file to a DCS Application as an E-mail attachment, ensure that the recipient

E-mail address is available to the E-mail program on the smart device that receives the file.

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 do have your book and I did read it (lucky me, a 5 hour airport delay out of Phoenix last Tuesday, and grateful I had my tablet and your book). I would encourage anyone who is using this app to get it.

You motivated me to play with this a bit more. As I said, one android tablet is quite old and the other is new. I had updated the engine roster on the old one yesterday and attempted to export. It does not obtain the file automatically. The new tablet does get the file automatically. For android users who are interested, the newer tablet (Asus Zenpad, which was $75 at Amazon a few weeks ago) is running android version 5.0.2 and the old tablet (Samsung GT-P6210) is running version 4.0.4. Both of these have been updated to the latest android version for the applicable tablet. And what this simply means, is that all updating of data should be done on the newer tablet and then exported to the older tablet. 

I use these tablets because I have children (my grandchildren and visitors age 10 and under) over and want to put something in their hands that I really don't care about (NOT my smartphone). When you think about it, the new tablet is substantially less expensive than a DCS handheld controller. Which is why the other post on the DCS controller can be easily answered.

Gerry

Barry Broskowitz posted:

Daniel,

Is there a known issue with the "All Engines Operation" when using multiple WIUs ?

Not as far as I know. However, I haven't tried the app with iOS 10.3.2, which came out last week.

Hi Barry,

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

Do you now consider it in the list of "known bug by MTH" ?

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.

Thanks

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.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.