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

jbmccormick posted:

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 

  If you are still looking for these answers I’ll try to help. 1st while an MTH engine is active you can go through the adjustment page and will find the typical momentum adjustments MTH uses where 1 is the slowest acceleration and deceleration. It helps but if you are looking to get the type of adjustment available with that a Legacy engine can have it won’t happen. The MTH units won’t have as much momentum and although they operate closer to scale it will still be a bit fast.

  To get to the adjustment page there are three icons at the top above the throttle and it’s the third one on the right then once on that page scroll down.

  As for making a tmcc loco active again. Check your list of loco’s on the top right Touch the word edit then put your finger on the engine you would like and slide it up to the top. Touch done and now it’s in the active roster.

  I also think one of my devices has an arrow on the right side if my Lionel locos so all I have to do is touch that arrow however I’m away from my layout and can’t check that for a few more days. If the arrow is there Just touch it and the loco moves to the active list.

The previous poster's comments are correct. However, some nomenclature is in order:

• The reference to the "adjustment page" is more accurately the "DCS Engine Settings Screen". The acceleration and deceleration sliders are on the lower part of the screen so it may be necessary to scroll down the screen to see them.
• The "list of locos " is more correctly known as the "Engine Roster Screen". it's accessed by tapping the down arrow at the top-right of the "Engine Control Screen", Engine Settings Screen" or Engine Soft Keys Screen".
• Regarding "put your finger on the engine you would like and slide it up to the top". For iOS (Apple) devices such as iPad, iPhone or iPod Touch, "put your fingers on the sliders to the right of the engine's name and slide it up into the Active Engine List".
• Regarding "I also think one of my devices has an arrow on the right side if my Lionel locos so all I have to do is touch that arrow", that would be for an Android device. For Android devices, just touch an upward or downward arrow to the right of the engine's name to move it to the Active or Inactive Engine List, respectively.

Detailed  instructions and annotated screen shots are included in 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! Get the free TMCC & Legacy Addendum here!

gmanning35 & Barry,

Thank you guys that was helpful.  I was able to make the adjustment to the MTH engines and you are correct, its not like the Legacy engines but thats fine.  I was also able to slide the engine up but for some reason it didn't run when I moved it up.  It's a new Atlas F7.  Perhaps this is user error.  I will try again later today, and see if I get better results.

John 

I was running the app a little bit last night, I set up a lash up in the app and ran that for a bit, and that worked fine. I did find one problem in my set-up, it could have been just me or something slightly off. I was running a steam engine and a Diesel that were in a Lash-up together. when I wanted to break apart the Lash-up I was unable to use the Rear coupler activation on the Steam engine or the Front Coupler activation on the Diesel. It made the sound associated with the coupler, but they did not activate at all.

I don't know if that could be related to my Version on my TIU and Remote is 6.0 and not 6.1 as it looks like it was recently updated to, or if something else is going on.

when I wanted to break apart the Lash-up I was unable to use the Rear coupler activation on the Steam engine or the Front Coupler activation on the Diesel. It made the sound associated with the coupler, but they did not activate at all.

I suspect that you would have to start up each lashup member as an individual engine before you could activate the coupler that isn't active in the lashup.

Further, you should shut down the lashup before breaking it up.

I don't know if that could be related to my Version on my TIU and Remote is 6.0 and not 6.1 as it looks like it was recently updated to, or if something else is going on.

The version of DCS in the remote has absolutely no effect on anything that the app does. Also, I was advised by MTH that DCS 6.0 and DCS 6.1 in the remote are, except for their numbers on the power-on screen being different (6.0 vs. 6.1), the exact same code.

Has anyone had any issues with running a lashup with the new app version that came out on 11/13/2017?  I am running this app on 2 android devices and I can't start the engines up with sound.  I can move them on my layout without any sound.  I have tried resetting the app by clearing the cache and uninstalling.  I have the TIU on version 6.1.  Lashups work fine with the dcs remote but not with the app. 

Jason Smith posted:

Has anyone had any issues with running a lashup with the new app version that came out on 11/13/2017?  I am running this app on 2 android devices and I can't start the engines up with sound.  I can move them on my layout without any sound.  I have tried resetting the app by clearing the cache and uninstalling.  I have the TIU on version 6.1.  Lashups work fine with the dcs remote but not with the app. 

  Jason,

  I've not had that issue and it seems like you've tried hard to make it work for you so you may have already tried what I am going to suggest. Just the same in a couple of experiences I've had with lashup issues  I found by breaking the lashup apart running the locos on their own individually then reconstructing the lashup I've been able to get things back to normal. For the most part I've found the newest app and TIU software versions have been working well with all my MTH loco's and I've only had a couple of issues with Legacy loco's. 

I tried as you suggested and it did not work.  It actually messes up the 2 engines that I tried to lash up.  It changes the addresses and names of the locomotives.  All of my engines are protosound 2 and several are protosound 2 upgrade kit versions.  I do appreciate you trying to help out with this issue. 

After further testing it appears when I build a lashup with the app it reset the engines to default and assigns the same address as the lashup to both engines.  I have to use the dcs remote to correct the dual address problem. 

Jason Smith posted:

After further testing it appears when I build a lashup with the app it reset the engines to default and assigns the same address as the lashup to both engines.  I have to use the dcs remote to correct the dual address problem. 

  Jason,

  I am fairly confident after reading through all that you have posted about this that I know what happened and how to fix it. 

  First I would assume you've had the same experience as me with trying to transfer your programming from your DCS remote to your Android device and that is it doesn't work correctly if at all. I have tried with a Samsung G5, Motorola Droid Razr and Samsung tablet all with nothing  but issues trying to load the info from my DCS remote. Finally what I had to do was enter all the info one item at a time to each device. That means all my switches, routes, accessories, scenes and absolutely all my loco's.  So with that said if you had any success at all most likely it was still incorrect. I can say that on my ipad the transfer worked perfectly and even though the app tells you that the transfer was successful on the Android I truly doubt it.

  With that said if a loco is addressed on the remote differently than on the app or even on a different remote than a lot of issues happen including no sound with a lashup and many other running issues right down to both locos getting the same address. I could go on about how I learned this but you need a solution not my story.  

 I would suggest you do the following.

Using a programming track with nothing on it but the locos you are having all the issues with and using your DCS remote do a factory reset to default on each loco one at a time. (I'm not in front of my layout so my terminology may and will be off but I think you will get the idea). By doing the reset neither loco will have an address and will be just like they were when you took them out of the box for the first time.  Next really look at your DCS remote and if you only have one great but if you have more compare the info on both and figure out how to make them both the same. If there are locos with on both with different addresses I suggest removing them from the list. Also get rid of them on your Android devices. 

  Now add one to each remote and android device but make sure they all have the loco show up with the same address. 

 Next add the second loco and if it tries to come up with the same address use a different remote or one of the Android devices to add it instead then edit it and change the address to what you need it to be.  ( I've had to do this myself  but only if the two locos are the same model and road number) Once you have it in the second remote or Android device you will be able to add it to the remote and it will show up as a second loco the way you need it too.

 Now I suggest you take the Android device and start adding your loco's one at a time in the same order they are shown in your remote. It shouldn't matter but if you have any non MTH loco's and they are not entered in at the correct address point then you will have the type of conflict in addresses that most likely caused your issue. 

 Once all are added and both lists are exactly the same in all your remotes and android devices you can start to build lashups and again you will need to build them in each remote and android device making sure the address is the same for each.

   Most likely all your problems happened when you inadvertently had a difference in addresses between two remotes or a remote and the android device. It's extremely easy for this to happen. 

  Just remember that before you do anything more you have to reset the engines to default or you will only be digging a bigger hole. 

I appreciate the detailed reply but it still does not work.  I tested on an isolated track and followed what you suggested with 2 engines and it still will not work correctly.  I only have one dcs remote and do not have any issues with incorrect addressing.  I had absolutely no issues with lashups until the most recent update was installed so I know my setup was working and there seems to be a bug with this new update. 

I just received an email from Jason Wenzel at MTH stating that this is a known bug and they are working on a fix for this issue.  I just wanted to pass this along to all the other users that are probably having this same issue. 

Tryed to lashup two engines last night. No matter what two engines I chose ps2 3volt or ps3 types. The app would let me make the lashup and name it,but when you go to run it hitting the start button does not bring up the sounds. Also hitting extended start up the sounds do come on,but are acting very weird. One engines sound is full volume and can not be turned down while the other can be turned down with the volume bar at the bottom of the engine screen. Lashups using the remotes work just fine. 

Tryed again this morning also. I only have the two engines used in the lashup on the track no others. I hit the read button and it only reads one engine not the other and puts the one engine in the active list. When you tap edit,moving engines from the active to the inactive list is acting strange also. It will only let me move the one engine it read to the inactive roster thats all. Once all engines are in the inactive list you can not move any others back to active when you hit the edit button. Engines have no arrows to the right of them.  Also before these bugs started showing up in the app. When running the lashup last week with it when you go to the settings screen why no individual horn,bell,and prime mover sounds on the sceen to ajust like in the remote. If I recall only smoke volume and type of engine steam,diesel,ect could be changed. Is this normal? Should not a lashup have the same options as a regular engine in this screen? 

Seems its back to the remotes untill mth fixes all these bugs and gets it right.

Jason Smith posted:

I just received an email from Jason Wenzel at MTH stating that this is a known bug and they are working on a fix for this issue.  I just wanted to pass this along to all the other users that are probably having this same issue. 

good info.

Just wanted to pass along I also received another email from Kirsting at MTH.  Below are the details of the email.

Thank you for contacting MTH Electric Trains. We appreciate your interest in our products. This is a recently discovered issue with the most recent version of the app on the Android platform. We will be addressing this with the next update; As a work around until a an update can be created, you should be able to start the engines independently prior to activating the lash up.

My TIU was upgraded to 5.0 before I set up DCS & WiFi and I have been successfully operating my MTH engines using my ipad.   I recently upgraded to the premium WiFi app so I could run lash-ups.   The app is installed on my iPad.   The system works great until try to make a lash up.  I am running only DCS with photo 2 & 3 engines.  

I always use a programing track for adding engines to my system.    My lash up consists of one photo 2 engine and one photo 3 engine.   I can name the lash and select engines - forward and trailing locomotive and direction for each.    When I hit the done button I get this message:  Command Failed lash up initialization command failed with an OK.   What do I need to do next?    

If it's a TIU issue and I need to upgrade to the latest operating system, can I upgrade in the Apple environment?

Dave  

Dave,

The latest version of the DCS App, 3.2.1, requires DCS 6.1 in the TIU and firmware 1.1 in the WIU. As I recall, a forum member recently posted about lashup issue with DCS 5.0. Upgrading to DCS 6.1 cured the problem.

Everything that you need to know about DCS WiFi is all in MTH’s “The DCS WiFi Companion 2nd Edition!" This book is available from many fine OGR advertisers and forum sponsors, as an eBook or a printed book at MTH's web store!

My first lashup was with 4 Atlas O engines a year ago, and it worked fine.  It should be even easier with MTH engines.  The firmware update was the key.  The lashup works with the iPad and with the DCS remote.

Bob

Barry Broskowitz posted:

Dave,

The latest version of the DCS App, 3.2.1, requires DCS 6.1 in the TIU and firmware 1.1 in the WIU. As I recall, a forum member recently posted about lashup issue with DCS 5.0. Upgrading to DCS 6.1 cured the problem.

---

Everything that you need to know about DCS WiFi is all in MTH’s “The DCS WiFi Companion 2nd Edition!" This book is available from many fine OGR advertisers and forum sponsors, as an eBook or a printed book at MTH's web store!

Thanks for the reply Barry.   I was thinking the DCS would need to be upgraded to 6.1.  Can I do that in the Mac environment or must I use windows?

I do have your DCS O Gauge Companion, 2nd edition, and followed it religiously throughout my layout build.   I did not hook up the DCS until I was past ballasting and much of the scenery.   I know that was not very smart on my part, not to test along the way, but when I finally got around to installing the DCS, everything worked according to plan.   Your book was a great help in the process.    Thanks!

Dave 

Dave,

Can I do that in the Mac environment or must I use windows?

You need to have a Windows environment, however, you can establish one on a Mac using Boot Camp, VM Fusionware or Parallels.

Barry Broskowitz posted:

Dave,

Can I do that in the Mac environment or must I use windows?

You need to have a Windows environment, however, you can establish one on a Mac using Boot Camp, VM Fusionware or Parallels.

Hi Dave: Barry forgot to tell you that you will have to purchase Windows, which can cost from $98.00 to $178.00. Boot Camp is already on your Mac.  You may have to give up about 40% off your Mac's hard drive to make Windows work. I use my adult son who has a PC and he comes over to do my upgrades. You will also need the 3 special cables as indicated by MTH. He is an automotive engineer for one of the major car companies here in Detroit, this process keeps him interested in the hobby, Try to find a family member or high school kid with a PC.

Do not screw up you Mac just to do one process. 

Hope this helps: Gary

Dave,

Gary is correct in that you also need a licensed copy of Windows. However, I recommend Windows 7 rather than Windows 10. It's less expensive and I can attest that it's perfectly compatible with the DCS Loader Program and will install on a Mac in Boot Camp or Parallels environments.

Amazon has a copy available for $65.00 here. The DCS WiFi Companion discusses establishing a Windows environment on a Mac on pages155-157.

Why would you use Windows 7 when official support for it ends in 1 year?

Because it’s cheaper, easier to use with the Loader Program, takes less resources, and Microsoft support is unnecessary for using it solely with the Loader Program.

Why buy a product key in the first place? You can run Windows 10 just fine with no product key legally, you just wont have access to all of the operating system's features.

Please show us where Microsoft states that is the case and what states what features are excluded and included.

Barry Broskowitz posted:

Why buy a product key in the first place? You can run Windows 10 just fine with no product key legally, you just wont have access to all of the operating system's features.

Please show us where Microsoft states that is the case and what states what features are excluded and included.

MS offers a 90 day free trial of the enterprise version of windows 10.

https://www.pcmag.com/article/...for-free-for-90-days

Unactivated versions do run, and many of the features are disabled when running unactivated, but you should still be able to load the Consumer loader and update TIU firmware.

https://www.howtogeek.com/2446...-and-use-windows-10/

For those who needs MS windows for the extremely short amount of time to run the DCS firmware update, these option should do the job.

AmeenTrainGuy posted:

Dave,

If you would like help installing Windows on your Mac I would be glad to help you out. Just send me an email to my profile. I have already helped several forum members do that.

Thanks, Ayman

Ayman,  Thanks for the offer.   I think I will ask a train buddy of mine who lives in the Windows world to perform the upgrades.   I really don't see the need to crowd my computer with a Windows application that I would seldom use.  

I am surprised that MTH with all its ipad promotion for WiFi operations, don't offer downloads in the mac environment.   I am sure it is a cost factor.  

Thanks everyone for the information and suggestions.   

Dave

One other question, I bought my WiFi module in August of 2018.   Can I assume that its software is current and compatible with the new DCS 6.1?   Also, Barry mentioned firmware 1.1 in the WIU - is that the remote?   Will that also need to be updated?  This part of the hobby is totally outside my comfort zone!

Dave

Dave,

I bought my WiFi module in August of 2018.   Can I assume that its software is current and compatible with the new DCS 6.1?

While you cannot assume that it has firmware 1.1, it most likely has. Regardless, you need no special cables to update the WIU and you can use a web browser on just about any device. I recently did a WIU upgrade at York  using my iPhone, while standing in the common are Ain the Orange Hall.

firmware 1.1 in the WIU - is that the remote?   Will that also need to be updated?

If you use a DCS Remote as well as the DCS App, the remote must have the same DCS release as does the TIU, i.e., DCS 6.1.

Everything that you need to know about DCS WiFi is all in MTH’s “The DCS WiFi Companion 2nd Edition!" This book is available from many fine OGR advertisers and forum sponsors, as an eBook or a printed book at MTH's web store!

Barry Broskowitz posted:

For those who needs MS windows for the extremely short amount of time to run the DCS firmware update, these option should do the job.

What about performing future DCS software updates?

Again, what features are not present? Your linked page doesn't say, or I didn't see it.

This is only good until Microsoft changes its policy.

What about performing future DCS software updates?

Ummm.... install the trial copy again or keep running the unactivated version. Trust me, unless you are a business doing this for many computers, MS doesn't care. While negotiating our volume license for MS office, I told our sales rep about testing windows 10 on a laptop at home without a license and not being activated, they didn't mind as it would only give me more exposure to a product they want to sell to me as a consumer.

Again, what features are not present? Your linked page doesn't say, or I didn't see it.

Directly from the "How-To Geek" article posted above:

Initially, you won’t notice a difference. Eventually, Windows will start nagging you a tiny bit. First, you’ll notice a watermark in the bottom-right corner of your screen. You’ll also see a “Windows isn’t activated. Activate Windows now.” link at the bottom of the Settings app. This is the only form of nag you’ll see–there are no pop-up windows, for example.

Second, you’ll be unable to change your desktop wallpaper and from the Personalization > Background screen in the Settings app. You’ll see a “You need to activate Windows before you can personalize your PC” message at the top of this window, and the options for changing your wallpaper will be grayed out.

Aside from these basic limitations, your Windows 10 system will continue to work forever. There are no nag prompts aside from the watermark, you’ll get all the system updates, and everything else is completely functional. The only thing that could change this is a Windows 10 update, but Microsoft has become increasingly lenient since Windows 7.

The user experience is reduced but the core functionality of running programs is not crippled.

This is only good until Microsoft changes its policy.

In the days of Windows XP unactivated version would completely lock out until a valid license key was entered and the OS was activated via WGA. MS Policy more recently changed the other way with the release of Windows 7 in 2010 allowing you to run an unactivated OS for as long as you want but you have to be willing to deal with some nagging prompts.

Look at the current landscape of PC sales. I can buy a new "cheapo" laptop for around $300 with windows 10 home installed. The only folks left out are those with Chromebooks and Macs. If MS can get those people to install a boot camp with a (pirated or trial) version of Win 10, that a plus for a MS. It only helps them sell more product by directly advertising to those who currently use a competitive product.

The How-To Geek article was put up in 2017, if MS was really concerned about this don't you think they would have had a conversation with the folks at How-To Geek about removing this article for everyone to read? This article is pretty easy to find and How-To Geek is also a popular read website.

I initially thought this was about a new release of the app.  I love the app.  I looked up the release of the app and gladly on the right version.  I am fortunate that my work PC is a PC and that I can do the updates there.

John

I'm not able to get the "Export" function to work in the Android version of the premium app.  Nothing happens when I press the "export" button in the app. I am using the most recent software versions for everything (TIU, WIU, app). I have 2 Android devices, and both are running version 10.

I also have the iOS version of the app, and Export works fine on my Apple devices. I can even export a file and then import it on my Android devices.

Has anyone else had this problem? I emailed MTH support a couple of days ago but haven't received a response yet.

This issue is being discussed on another thread but I wanted to post it here because this thread seems like the main source for issues with the premium app.

Just wanted to give JohnF. some credence on his post, we have been part of a 2020 post, I think I started, that asks that very question.  A Forum member that goes by RJR has chimed in several times to report his Android tablet performs the Export without flaw, but his Android phone wasn't having any luck, correct me if I'm wrong RJR.  Sorry to drop your handle but it's important anyone who reads this know the full story of what we are experiencing.  A prior post of a few years ago talked about using Export and a Forum member posted pictures of each step and what to expect, great work by the way.  But when you read the steps, they are for an Iphone.  Would really like to know how to make this work on an Android, I don't want to have to re-create 38 routes on my phone one by one to update my smart phone copy of the App.  Thanks.

From an iPad or an iOS device where is the export feature?  Would love to be able to export from 1 iPad to another and also to an iPhone.

Happy Sunday.

Here is how you export:

1) Tap on "More..." in the bottom right of the main screen of the app

2) Tap "Advanced Features"  on the first line of the next screen

3) Tap "Import/Export" on the next screen

4) Tap "Export" on the next screen

You will then see a message that says "Export Complete"

5) Tap "Share" right below where it says Export Complete

6) You will then be presented with several options for sharing. I think the easiest way is by email. I just choose the name of the email program I use (Gmail) which is listed on the second line.

7) Fill in your email address to send the file to yourself

8) Send the email

9) Open the email on your second device

10) Click the attachment and it will automatically import to the DCS app on that device. The MTH app does not have to be open to do this.

Just wanted to state for the record that it is the step right after step 4 where it all stops.  Because of that steps 5 and beyond are not physically possible.  I've tried it with the house internet on and operationally attached to the WIU which permits me to talk to the TIU.  The only thing I haven't tried is flipping the mode switch from MTH, left to House mode, and pressing the WPS button.  One reason for that is that my house router doesn't have a WPS button and the instructions in the WIU's little owners pamphlet state clearly that I am supposed to press the WPS button on the WIU, then press the same button on the router.  Can't press what i don't have.  That being the case I figured that approach was not possible anyway so why bother trying?  My thought was, and try to see my thinking on this, how can my app export a file that is supposedly stored on the TIU, if I have that correct, if the App is unable to talk to the TIU because I don't have the Tablet attached to the WIU in a way that permits it to find my email via the net?  One would think, that to make this work, you would need to be able to talk to the TIU and access the net at the same time.  House mode supposedly, unless i have that wrong as well, allows you to run your trains and search the web at the same time.  That's how MTH gives us the ability to do all that shopping and searching it mentions in the MENU... menu.  Just my take on it.  But RJR has specifically stated that he has successfully exported using an android based tablet without beind connected to the WIU.  So that alone dispells this logic completely.

Johnf,

Thank you.  That was really easy.  I just ran through the steps on my iPhone.  No issues.  You can just airdrop it.  Simple.

Yardmaster, what Johnf is talking about deals with the app, not the TIU or the WIU.

John

Yardmaster,

The file that is being exported is stored by the app on your Android/Apple device. That is why it doesn't matter whether the TIU and WIU are on.

jb and johnF.

Thank you, thank you, thank you.  Finally, two people who were willing to explain to me HOW this feature works.  It's the App not the WIFI doing all the work.  Again, I don't connect to a lot of this stuff.  What you two just told me makes perfect sense.  I taught software applications like Excel, Lotus, Word, and Access.  I was retired by the time Apps came along.  But it all makes sense now.  Yet it still won't work on my Android devices, and like JohnF said, it's probably a release issue.  So it's up to MTH to send out an update.  Based on that information we can safely say this will never get fixed.  My kingdom for a fed up, angry, R&D employee from MTH to read this and fire back, "WE KNOW ABOUT THE ISSUE AND WE ARE WORKING ON IT!!!"  My reply to that, "well, at least we got your attention."

Yardmaster,

I feel your pain.  I can't help you.  I'm an Apple guy, not an Android guy.  Good luck.

John