Thanks!  

Thank you for a very great product and excellent support I and I hope everybody appreciates everthyning you guys and Gals do at MTH and make excellent products. keep up the good work and tech support issues, I recommend all your products to all my friends on and off the forum.

Thanks Again Alan

Thanks for being on top of things enjoying the wifi so far with limited problems . Need to try a couple of times to add a engine but it will come up . The 5 year old grandson has taken the pad and run the trains with no problem of course with a speed limit . Looking forward to much more .  Tom

Cool, great work MTH

I work for a software company and everybody's stuff has warts occasionally.  It's really great to see MTH admit to this and nice to know that you are actively working on a fix.

Thank you!

Thanks for the info.

Thanks for the update, the fix and for monitoring the forum.

Glad MTH RD and other manufacturers uses the forum for product improvements and that they appreciate input.

Kudo' not only to MTH, but Lionel, Atlas and others as well.

Kevin 

Thanks for the acknowledgement and information on what's coming.  I hope this will fix the Fixed 2 issue that's been noted in other threads.

thanks for listening

Clem k

As a new member I just want to thank those dedicated members on this forum who've been helping those in need for many many years without them who knows where we'd be but like my grandpa use to say "who asked you"

Thanks MTH. 

The bell shuts off when you press the horn on android. I think this is a bug.

Possible bug, I've found with my PS2 3v Mohawk with quilable whistle, sometimes you pull the whistle cord and you get nothing.  Have to get to the option page shut of the quilable option or change directions resets it.

Steve Kilmer posted:

Thanks MTH. 

The bell shuts off when you press the horn on android. I think this is a bug.

Steve, this is indeed a bug.  It's a simple fix and should be included in the next update.  If not, then the one after that.  There will be farily frequent updates as you guys find these quirks.  As someone said, this is the nature of the software beast.

superwarp1 posted:

Possible bug, I've found with my PS2 3v Mohawk with quilable whistle, sometimes you pull the whistle cord and you get nothing.  Have to get to the option page shut of the quilable option or change directions resets it.

Hey Gary, this is actually not a bug, just an issue that needs to be understood and handled better in the app.  Let me explain.  The quilable whistle feature is a temporary on/off in the engine.  Each time you shut down (or power down) the engine, the feature is turned off.  However, the "playable whistle" switch in the app remains on.  So, the app is sending quilable whistle commands when the feature is off in the engine.  The result is no whistle.  

Honestly, the playable whistle feature should have been persistent in the engine like so many other features.  Because the thumb wheel on the DCS remote is dual purpose, it had to be done this way.  

So, a change coming in the app is that when you shut down an engine or hard close your app, the playable whistle switch will revert back to off.  At least this way, it should be easier to keep in sync.  In the meantime, you have to sync the engine mode with the app settings.  A nuisance but, once you know what is going on, easy to deal with.

Perfect amount of  detail in explaining the issue.  Thank you, G

MTH RD posted:

superwarp1 posted:

Possible bug, I've found with my PS2 3v Mohawk with quilable whistle, sometimes you pull the whistle cord and you get nothing.  Have to get to the option page shut of the quilable option or change directions resets it.

Hey Gary, this is actually not a bug, just an issue that needs to be understood and handled better in the app.  Let me explain.  The quilable whistle feature is a temporary on/off in the engine.  Each time you shut down (or power down) the engine, the feature is turned off.  However, the "playable whistle" switch in the app remains on.  So, the app is sending quilable whistle commands when the feature is off in the engine.  The result is no whistle.  

Honestly, the playable whistle feature should have been persistent in the engine like so many other features.  Because the thumb wheel on the DCS remote is dual purpose, it had to be done this way.  

So, a change coming in the app is that when you shut down an engine or hard close your app, the playable whistle switch will revert back to off.  At least this way, it should be easier to keep in sync.  In the meantime, you have to sync the engine mode with the app settings.  A nuisance but, once you know what is going on, easy to deal with.

I'll have to play around a little bit but the issue I was having(I think) is when you select quilable whistle during a operation session, I would lose it during that session.   Not leaving it on, shutting everything down and coming back the next day.  Will advise if I turn it on, lose the whistle, and have to reset during the same operation session.

Nice work MTH.  I've seen a software exec smash an egg on his face during a VAR conference after an incredibly bad release.  They worked through the issues, made the corrections and didn't repeat the mistakes.  Turned out OK for them as they later sold to Microsoft for $1B.

I'm in the "sweet" spot with only four engines and the app is working great.

MTHRD,

The bell shuts off when you press the horn on android. I think this is a bug.

It's a simple fix and should be included in the next update.  If not, then the one after that.

Is this Android-specific or has some other selective criteria? I tried, with 3 different engines, to replicate this problem and could not. I even tried it with an engine that has a playable whistle, in both normal and playable modes, and the problem did not appear.

I'm using iOS 9.2 on an iPhone 6.

Hello Barry, I have a 4th Generation I-pad and a Android phone. Both devices have the standard app. The bell only shuts off when I activate the horn using my Android phone. I don't have this issue with my I-pad.............rogerw.

The APP is outstanding and very fast. The developer did an excellent job on the graphics and technical workings. The ADD engine is particularly fast; click click and each one goes in.    

I have my WIU coming soon (and a new TIU due to some hardware fault).  I cannot wait to try this out!  Thanks to MTH for this awesome product!  And in defense of the programmers, its nearly impossible to catch EVERY bug in the system!  The sign of a good programmer and company is the actions taken once a bug is discovered by the customers.  MTH is obviously keeping on top of these things and I truly appreciate that!

MTH RD, this post and your participation in the forum is the best public relations move MTH has ever made, and I've been dealing with MTH since Mike Wolf was selling Weaver locos over the counter in his little store in Columbia.  Don't know who made the decision to do it but they are to be congratulated.

Thanks to all for your compliments, understanding and patience.  Especially the compliments.  Just kidding.  It is all appreciated.  Yes, this is a complex system.  More so than most would imagine.  To further complicate things, we are interfacing with the TIU that is pretty much fully matured from a firmware standpoint.  We can't do much outside of what the TIU is capable of.  In time, this too will be addressed.

MTH RD, I'll pass on 3 items, for info (not complaint):

1. I use android.  Pressing horn shuts off bell.

2. I have the fixed 2 powerup problem, by which powering up fixed 2 with my Z4000 (w/ Z4k receiver) moves all locos to inactive list.  I have found this occurs even if I have nothing connected to the Fixed 2 red output terminal.

3. I've been told that pressing the E-stop button requires a long press.  FYI, mine acts immediately.

Hmm... Are you going to be able to fix the regular remote  feature reset at the same time. After 14 years it's changed,

RJR posted:

MTH RD, I'll pass on 3 items, for info (not complaint):

1. I use android.  Pressing horn shuts off bell.

2. I have the fixed 2 powerup problem, by which powering up fixed 2 with my Z4000 (w/ Z4k receiver) moves all locos to inactive list.  I have found this occurs even if I have nothing connected to the Fixed 2 red output terminal.

3. I've been told that pressing the E-stop button requires a long press.  FYI, mine acts immediately.

Thanks RJR.

Yes, the horn turning off the bell, but leaving the bell icon in the "on" state is a known Android bug.  No worries.  Easy to fix.  Will be fixed.

Regarding the fixed 2 power up problem, are you saying that with active engines on fixed 1 simply applying power to fixed 2 makes the engines go inactive or, are you saying once fixed 2 is powered and you hit refresh (read) the engines go inactive?  These are very different and if the latter, the bug fix I've talked about should resolve it.  If somehow just applying power to a channel initiates some communication with the app and makes engines inactive, I'm a little scared.  I just cannot see how that is even possible.  The TIU cannot initiate communication with the app.  Please let me know on this and thanks.

Initially, in beta testing, E-Stop had a longer delay.  I think it was 1 second.  This was done to avoid to avoid accidental E-Stops.  Marty pointed out it was too long and we dialed the delay back to about 250ms or, 1/4 of a second.  Just trying to avoid activating E-stop when a finger brushes it.  In the next release of the app, and I've already played with this, you will be able to turn the E-Stop on and off in the app settings screen.  We added a switch so, if you're a brave soul and want to run without E-stop, you simply turn it off and the red stop sign icon on the main engine control screen disappears.

I have one question for MTH, is there any chance this hot fix will be ready for the 23rd? 

This is interesting what MTH RD said about the TIU being at it's firmware limits " In time, this too will be addressed."

Tony_V posted:

I have one question for MTH, is there any chance this hot fix will be ready for the 23rd? 

Sorry, but no.  We just identified the problem and fix yesterday.  Now, we need to do some thorough testing and then, release.  While the app update has nothing to do with the read/add/inactive issues, we have some updates ready for that too.  We will coordinate the release and so, are also impacted by the iOS and Android reviews.  Hopefully, around the end of the month assuming all goes well.

superwarp1 posted:

This is interesting what MTH RD said about the TIU being at it's firmware limits " In time, this too will be addressed."

Please don't read too much into that.  Nothing will happen anytime soon.  The point is, eventually, we will have to address the TIU firmware maturity.  When we do, significant advancements are possible.

I've heard that Super TIU and Lash-ups are supposedly planned for the "Pro" release of the APP.

Our club has five TIU's that run in Super TIU mode on the remotes. We have a router that's connected to a Lionel WiFi and [for now] have five WIU's tied to it to allow members to connect to a single point rather than change WiFi access points when switching between TMCC and DCS. This is what we'd prefer to do as the router's transmission range is much higher.

The Manual says to "slave" the other WIU's to one WIU, but in testing, communication with the locomotive was lost when it moved from one TIU zone to another.

Matt,

The Manual says to "slave" the other WIU's to one WIU, but in testing, communication with the locomotive was lost when it moved from one TIU zone to another.

That should be expected. It works just like a remote in Normal TIU Mode.. The DCS engine is only associated with one TIU and, when it leaves that TIU's domain, just like with  the remote no other TIU is sent commands from the app.

MTH RD posted:

Tony_V posted:

I have one question for MTH, is there any chance this hot fix will be ready for the 23rd? 

Sorry, but no.  We just identified the problem and fix yesterday.  Now, we need to do some thorough testing and then, release.  While the app update has nothing to do with the read/add/inactive issues, we have some updates ready for that too.  We will coordinate the release and so, are also impacted by the iOS and Android reviews.  Hopefully, around the end of the month assuming all goes well.

Yup, the fix is always easier than the QA.  I was just asking as I am sure you know there will be a lot of updating going on that day.

Tony

Gregg posted:

Hmm... Are you going to be able to fix the regular remote  feature reset at the same time. After 14 years it's changed,

It's my understanding the feature reset  doesn't work as well with the App???  The custom name  disappears.  Id sticks though.   

I'm glad to see that MTH is working on the up-grade issues. But first I have to get it into my equipment. (See my DCS up grade post for help).

MTH RD, you asked:

Regarding the fixed 2 power up problem, are you saying that with active engines on fixed 1 simply applying power to fixed 2 makes the engines go inactive or, are you saying once fixed 2 is powered and you hit refresh (read) the engines go inactive?  These are very different and if the latter, the bug fix I've talked about should resolve it.

The answer is both.  With regard to the first, it also made locos on Variables 1 and 2, fed from a different transformer, go inactive.  In another thread, which you probably have followed, I posted in 3 posts as follows:

Dave Minarik said,  The app will not find any engines (time out error) with the Fixed 2 channel powered up. 

Now that I've gone back to the Rev G TIUs and can communicate through the wifi, I am experiencing the same thing.  In fact, powering it up and trying a read moves everything else to inactive list.  Tapping a l0oco in inactive list never does anything.  I'm inclined to agree with a statement made by another poster that there appears to be a bug in the app.  I'm going to enjoy my layout, using the remotes, until the bug is exterminated.

**********

FWIW:  I tried something different this morning.  I unplugged the wifi wallwart.  Turned on layout & powered up all 6 tracks (including roundhouse).  Some 15-18 locos powered up immediately, quietly since they all got the watchdog.  I then plugged in the wifi and lo:  all locos were found by the read, including one (of 4) on the TIU that isn't connected to the wifi.  All of these were controllable from the tablet.

**************

Did more experimenting tonight on the Fixed 2 issue Dave Minarik mentioned above, and came up with a weird situation:  If I disconnect the wire from the red output terminal on the TIU Fixed 2, the problem remains.  If I disconnect the input red, the problem goes away.

The last post in interesting and unexplainable. 

Today I tried again.  I now have 2 wifis hooked up.  Turning fixed 2 on or off did not appear to affect what was active or inactive.

Reading is still a problem, with several issues:

1. A Samsung tablet will not read the locos on TIU#2/slave wifi, but a Samsung S6 phone does. 

2. If read at all, loco ID numbers are always read correctly, but not names.  Sometimes names are on wrong locos or occasionally come up "no name" and occasionally have a question mark after them.

3. Locos in inactive are usually in numerical (by ID#) order, but locos in active never are.

You say that the TIU cannot "initiate" comms with the app.  But I assume, it can respond to the app or the read function won't work.  Is it possible that the app sends random queries, or that the TIU "holds" the inquiry and send repeated responses???????

I will update this with any further result I receive.

Great information = debugging = Comments and resolutions 

And then there is the fact that there's NO trolley mode....

MTH RD,

Thank you for all the information!

Perhaps you can let me know where I can seek assistance regarding the following situation.

About three years ago I embarked on an extensive project using DCS, and was being supported by a most knowledgeable DCS guru. Unfortunately, and even though I represented profitable business, about two years ago this person suddenly ceased to communicate with me. I have talked with a couple of other people who have very willingly volunteered to intercede on my behalf, but their efforts have been in vane.

Could you let me know who I can contact about my project, which involves DCS? You are welcome to email me (see my profile for my email address)

Thank You!

Alex

Alexander Müller

Thank you MTH RD! I have been able to successfully connect and use the wifi with a limited number of engines ( the rest are packed up).  I enjoy the interface, the features are easier to access. Thank you for communicating with us, and keeping us in the loop. 

Andy

I have ordered a Wi Fi module, but have just discovered that the app is not available from the Apple site in Australia. How can I get around this please? ( Obviously, I'm in Australia).

Dave Allen posted:

I have ordered a Wi Fi module, but have just discovered that the app is not available from the Apple site in Australia. How can I get around this please? ( Obviously, I'm in Australia).

Hang in there Dave, We're sending an aircraft to pick you up immediately and get you to the States!!! 

Big thanks to MTH for letting us know about the issue and the work being done to fix it.   

Ed

I'm having and issue controlling my TMCC engine's through DCS after the 5.0 update. Any ideas? It's like the remote is no longer communicating to the TMCC base unit anymore. The red light is not blinking anymore when commands are being sent. 

In anticipation of the software upgrade release for the WiFi, I did a dry run to see if I could handle accessing LuCI web interface.

Being just barely computer savvy, I found it to be straightforward and had no issues doing so. All set for the upgrade release.  Joe

I am having the same problem as 350IROC.  Since I went to 5.0, I have no control either with the remote or thru the WIU.  I have changed track sections,lock-ons, power supplies, locomotives, etc., and no joy.

Allscale

Since I went to 5.0, I have no control either with the remote or thru the WIU.  I have changed track sections,lock-ons, power supplies, locomotives, etc., and no joy.,

This could actually be two completely unrelated problems, one of which affects the remote and the other that affects the DCS App.

The remote problem could be due to the fact that, often, when one removes a TIU and/or a remote from the layout for the purposes of upgrading their software, it's possible through handling of the components to have one or both of the transceiver (radio) boards in the devices float up out of their sockets.

To test for this occurrence, connect the TIU and the remote with a (curly) 4-conductor telephone handset cable. If the problem goes away, it's very likely that one or both transceivers have floated up and out of their sockets.

The DCS App problems could have several potential causes, since prior to installing DCS 5.0 it would not have been possible to test use of the app. The exact nature of the problem depends upon what are the exact symptoms when the problem occurs. 

For example, do any of the following occur:

• Does the smart phone or tablet not connect to the WIU directly (if in MTH mode) or via the home network (if in Home mode? (If the device isn't connected to the WIU, nothing at all in the app will work)
• Does the app not find its connected TIU? (If the TIU is connected via a serial to USB cable, the cable might be incompatible. Try a different manufacturer's cable) 
• When the app is requested to find engines, are any found? (If not, they must be on powered tracks connected to the TIU to which the WIU is connected)

• Are engines found, however, they cannot be made Active? (If not, they must be on powered tracks connected to the TIU to which the WIU is connected)

• Are engines found, made active, started up and control is lost during operation? (If so, they cannot be allowed to travel onto tracks that are connected to a different TIU than the one to which the WIU is connected).

The above is not by any means a complete list.

350IROC, ALLSCALE,

"I'm having and issue controlling my TMCC engine's through DCS after the 5.0 update. Any ideas? It's like the remote is no longer communicating to the TMCC base unit anymore"

I think the key word here is TMCC engines.  I was told that the ability to control TMCC engines thru the WIU will be in the PRO ($24.99?) version, not yet available.

I updated my TIU to 5.0 a few days ago.  Today, just to verify your findings, I tried running my TMCC engines via the DCS remote (both remote and TIU are now 5.0).  They worked as usual.

Perhaps after the update, you forgot to re-plug in the serial wire to the TMCC unit at the TIU end?  IF you have an older TIU, you would have disconnected this wire to do the update.  I know it's a simple mistake, but hoping to narrow down the problem.

Ed

ps.  I'm guessing that your DCS engines are working, right?  You don't mention them in describing the TMCC issue.

Well I can assure everything is connected correctly. I've even removed the WIU from the scenario and just have the TMCC base unit plugged directly into the TIU via Serial port. All of my DCS engine's work as they should through the remote and app. To add to this I have two DCS remotes I'm working with and both of them will no longer communicate to the TMCC base unit. Additionally my Lionel legecy remote is still operating as it should. I guess what I've learned so far is it should work and I apparently have a problem. I do thank you for the info as it will push me further to resolve.

I have a question regarding the Wifi module.  If we have the current as delivered module and there is a firmware upgrade How is this done   Does the loader program upgrade a module similar to how we do TIU's now

Another question  Why does the Wifi Module have an Ethernet port?

bluelinec4 posted:

Another question  Why does the Wifi Module have an Ethernet port?

So you can hardwire it to your network rather than over WiFi. 

Blueliner, firmware upgrade is covered in the wifi manual, not the quick start in the box, but as downloaded from the MTH web site.  To save you search time, I'm attaching it.

Another NJ Hi-Railer's question.

We have 6 TIUs in super mode (2 TIUs as #5).

Page 5 on the WiFi manual says "Then, as many as 4 additional TIUs can be connected. "

Does this imply that you cannot have multiple TIU #5s are you can now?

If we have the current as delivered module and there is a firmware upgrade How is this done

One connects to the module via a web browser and uses the app LuCI, which is built-into the WIU itself. The directions for doing so are, as Robert (RJR) points out above, covered in the full instruction manual. It's available on MTH's web page for the WIU.

Why does the Wifi Module have an Ethernet port?

One can use the Ethernet port to connect the WIU to a LAN (home network) over Ethernet, rasher than via WiFi, if one so chooses.

Does this imply that you cannot have multiple TIU #5s are you can now?

I suspect that the architecture of the app may allow use of more than 5 TIUs. However, you'd have to try it to be sure.

OK a few things   Since MTh doesn't recommend more than 5 TIU's anyway I don't see any reason that the Wifi wouldn't work with six   That's a non point.  To further my question on Ethernet is WHY would I want to connect it hardwired to a home LAN when these are WiFi units   Doesn't make sense to me  Don't see any advantage   Thanks for the link to the manual   So I should be safe if I buy the units now  and will be able to upgrade  Correct???

I don't think you can assume that 6 WiFis will work.  Handheld to TIU comm is totally unrelated to App to WiFi comm.  I agree with Barry.  We need to try it.  

I was thinking about the ethernet and the only reason I would see to use the ethernet port would be if you couldn't get a good wifi signal to the wifi adapter.  The app would connect to the wifi router and then the signal would go over the wire to the wifi adapter. 

On the point of a ethernet jack, it is also worth noting that Wifi is SLOW compared to a hardwired connection.  if you have a lot of Wifi devices taking up bandwidth on your network the hardwired connection will allow for a much better connection to your home network.   From what I can see in the instruction manual it looks like the DCS Wifi device uses a b/g/n standard wireless adapter, which is actually pretty good with up to 300mbps data transfer.  What you have to take into consideration id=s that if you have a weak signal, or any interference on the 2.4GHz frequency, that speed can drop dramatically as the wifi must keep sending the same data back and forth until it gets a clear message.  Also worth noting that that speed depends on you having a higher end wireless router in the first place, capable of the higher speed.  A lot of folk have only the b/g standard router which caps at 54mbps.  When compared to the 1000mbps and (mostly) complete lack of interference of a wired connection, having the ethernet plug is a good call on MTH's part.   

Short version of this, taken from page 8 of the manual;  "The smart device typically connects to the router via Wi-Fi, so there is limited benefit to using this configuration. It may improve overall performance in an environment with unreliable Wi-Fi network signaling."

JGL

I'll just wait for this to work correctly before i get it I guess.

From a "Fully Authorized Dealer and Service Center"

After watching over a dozen public videos on You Tube as related to learning, MTH-DCS, Wi-Fi. This is the best as of January 11, 2016. As more You Tubers purchase Mike's Wi-Fi, this number will grow.  

This video is where the steel, meets the rails, with no sand.

I am working with a Model Railroading friend and we have the 5.0 up grade done, to the TIU & Controller, been to the Apple Store to get the APP.  We have followed these steps, on page 5 of the manual and have watched this video & we are up and running.

1. Attach the antenna to the WIU.

2. Set the MTH/HOME selector switch to MTH.

3. Connect the WIU to your TIU with a USB cable (included*).

4. Apply track power through the TIU.

5. Plug the WIU into an AC wall outlet. 

6. Wait 1 minute for the WIU to initialize. When ready, the PWR, WI-FI, and TIU LEDS will be lit.

7. If you haven’t already, go to the iOS App Store or Google Play Store and install the app on your smart device. Search for MTH DCS to quickly find the app in either app store.

8. In your smart device, navigate to Wi-Fi settings and connect to the MTH DCS network. The network name (SSID) and network key are printed on the label affixed to the bottom of the WIU.

9. Open the app and tap RUN MY TRAINS.

10. Tap CHOOSE OR ADD AND ENGINE near the top of the screen and follow the prompts. 11. After adding an engine(s), tap START UP and enjoy running your trains in Wi-Fi DCS.

Gary & Cheers from The Detroit and Mackinac Railway

Interesting part is that he already assumes in the video you've had it connected and functioning.  Many of these questions are related to setting it up and getting it started.

bluelinec4 posted:

OK a few things   Since MTh doesn't recommend more than 5 TIU's anyway I don't see any reason that the Wifi wouldn't work with six   That's a non point.  To further my question on Ethernet is WHY would I want to connect it hardwired to a home LAN when these are WiFi units   Doesn't make sense to me  Don't see any advantage   Thanks for the link to the manual   So I should be safe if I buy the units now  and will be able to upgrade  Correct???

Do you have a computer at home?  It kind of is a standard, hardware and wifi.  In fact, in most instructions if you have an issue connecting a device to a wifi unit due to your security setting, they recommend using the hardwire until set up is complete.  Also as stated hardwire is normally faster, and much more secure.

My computer and printers are hardwired to my router, and the wifi is for portable devices only.   If the access port bother you, you could cover it with electrical tape.  G

I have been using the MTH DCS WIFI for a couple of weeks now utilizing the Wired Ethernet Network.  I have a great WIFI signal in my train room but I was having problems accessing my Home WIFI.   I really didn't want to use the MTH Network because of the inability to access the internet while operating in that mode. My router is in a room on the other side of the house so it wasn't practical to run a Ethernet cable over that long distance.  I got around this by using a Cisco Wireless-N Gaming and Video Adapter, Model WET610N that I had originally purchased years ago to access my DirectTV receiver and was no longer using because of technology advances made by DirectTV since then. 

Just had to place the adapter under the table and plug the Ethernet cable into the adapter and plug the other end into the DCS WIFI Module and problem solved. The WET610N receives the wireless signal from my home router and transfers the signal to the DCS Module via the Ethernet port.

The Model 610 Adapter that I used is one of many that are available on the market.  There are also WIFI range extenders that are available.  Just make sure that they have an Ethernet port available.  Hope this helps others that  are having difficulties accessing their Home WIFI in their train room.

That's good information. 

Thanks, John

I'm adding this from a conversation in email with another user, because I think the info pertains to the conversation here about ethernet ports and why folks might want to use them when they have the option.  There is some un-related material at the start but I decided to leave the full email intact.  

JohnGaltLine said:

I'm unsure what equipment, and what provider you have for Internet. That said, I think Ethernet plug is probably more accurate than t-1. Ethernet is basically the hard-wired connection to your internet modem. T-1, on the other hand, is a very old term that basically means a telephone mainline. A t-1 line is exactly the same thing as having 24 phone lines. These connections became popular with folks that could afford them, in the early days of the Internet as having 24 phone lines let you download data 24 times faster than a single dial-up modem. Since the 1990's, however, broadband cable and DSL have virtually made dial-up extinct as they are faster and more reliable. A t-1 line tops out a little over 1 Mbps (million bits per second) where as many cable and other internet providers offer speeds of 300-2000 Mbps today. To judge what you need, to stream HD quality video requires a speed of 3 to 5 Mbps, if you are doing absolutely nothing else on the internet and have no other devices connected. 

 

Anyway, on to the wifi,  the higher end wifi devices out for the last few years transfer data plenty fast enough to not really be worth talking about right now.  However a lot of folks are running older equipment, or running inexpensive equipment that will limit wireless speed to 54 Mbps. This is still very fast for one device to download with, but a lot of folks don't understand that if their router is limited at this speed, every device connected takes away something.  

Think of your wifi connection like a bunch of hoses connected to a large bucket. The bucket holds 54 gallons of water.  Radio interference acts like poking some holes into each hose, forcing you to lose some water(data) on the way to your phone or computer. In addition wifi is a redundant system that self corrects errors.  In the bucket analogy, once the water gets to your phone, the phone has to pump it back to another bucket to make sure the phone got the right amount of water. All of this back and forth of water(data) takes time, and when all is said and done, that 54 gallons is down to 25-30 that can actually be used on your phone or computer. Then it has to be split up again to go to each device connected. Your train wifi app? 2 gallons. The train wifi base, another 2.  Your kids and other family members watching Netflix?  There goes 15 gallons. Soon enough the water starts flowing slower.  Not enough data can pass through the wifi to keep up with demand. 

To the question of why have, or use an Ethernet port on a wifi device,  the answer is simple.  You free up a bit of data flow for other devices that actually need a wireless connection, like your phone or tablet, and...  Going back to the bucket of water again, that plug is like replacing the 54 gallon bucket with one that holds thousands of gallons. The wired connection transfers data dozens, if not hundreds, of times faster than wifi.  

 

I got a bit off course here in my response  to you and more into my reply to the folk on the forum, so I'm going to post much of this there as well. Anyway, I hope there is something useful to you in my ramblings.  

The take away from this as it related to this conversation is, if it is not too much of a headache, always use a wired connection if you can.  Every device you use on wifi slows the rest down, so if you can plug something in, do it.  Wifi is convenient.  Hard wired ethernet is fast and secure.  

JGL

Bluelinec4, Ben I will use the ethernet port to connect my computer to each WIU to upgrade the firmware when MTH releases it... I generally upgrade my router firmware using the ethernet port and I find it to be more reliable than upgrading "over the air"...  That's one specific use for the ethernet port

Has anyone had the problem of being unable to get engines off the inactive list?  I have experienced all the issues with multiple engines and multiple TIUS and when engines get moved to the inactive list the touch screen for the inactive list does not respond... Is this also part of the upcoming fixes?

Only way I've found to get them onto active list is to do another read, and hope it doesn't drop a few off the active list.

Dave Allen posted:

I have ordered a Wi Fi module, but have just discovered that the app is not available from the Apple site in Australia. How can I get around this please? ( Obviously, I'm in Australia).

Barry Broskowitz, can you help on this one?

JimQ posted:

Has anyone had the problem of being unable to get engines off the inactive list?  I have experienced all the issues with multiple engines and multiple TIUS and when engines get moved to the inactive list the touch screen for the inactive list does not respond... Is this also part of the upcoming fixes?

Hi Jim - We are all going through a learning curve. The best is yet to come from MTH, with the Advance APP. Just hang in and it will all come together.

Dave,

Another member had a similar issue with the Canada App Store. The solution was to search using combinations of "DCS", "WiFi" and "MTH", 2 terms at a time.

It really should be there; it may just be tagged wrong.

Trainroomgary, thanks for the reply... I know it will work out in the end...  I have been working around the problems just by limiting the number of DCS locos I put on the layout... Seems to work out OK... also, I am only using the app to run steam engines since I never lash them up...  Peace and harmony reign in the Shire for now!!

Barry Broskowitz posted:

Dave,

Another member had a similar issue with the Canada App Store. The solution was to search using combinations of "DCS", "WiFi" and "MTH", 2 terms at a time.

It really should be there; it may just be tagged wrong.

Thankjs Barry, I'll try that.

I had problems finding app with instructions given by MTH. I tried 'wi-fi dcs', and it came up on Canada Apple store. Al

Guess I'll miss out on this one.  Don't see the value as I don't WiFi and upgrading my layout control system is always a huge PIA.

Someday the software may be stabilized, but based on past releases, re-releases, bug-fixes, etc, I don't see it happening in the near future.

Running the TMCC engines more these days as they are pretty much problem-free and have most all features now one finds in basic operations with DCS.  I did stop purchasing MTH locomotives a while ago, due to the frustrations.  And it's not just my own layout; two other friends with large layouts are continually having problems with DCS.

Maybe we in the Northwest are the only ones experiencing these type of problems?  I just went back to working on the track and scenery and quit running trains for a while until I figure out where to go from here.  Know of one guy on the forums who said enough and converted his DCS engines to the new TMCC software and is very happy he did, apparently.

Maybe the computers out here are not up to the task of the new upgrading protocols, where one almost needs a new PC with WIN10 to get anywhere?

Kerrian.  I have 2 wifi units running on my layout.  IMHO, the wifi is fine if you like to play with gadgets (I do), but if you want to run trains (I do), stick with the remote.

Dave Allen posted:

I have ordered a Wi Fi module, but have just discovered that the app is not available from the Apple site in Australia. How can I get around this please? ( Obviously, I'm in Australia).

Both apps have been released to Australia for several weeks.  I am not sure about the process or timing for availability but, we have released them.  I think it is now in the hands of Apple and Google.

350iroc posted:

I'm having and issue controlling my TMCC engine's through DCS after the 5.0 update. Any ideas? It's like the remote is no longer communicating to the TMCC base unit anymore. The red light is not blinking anymore when commands are being sent. 

I've seen a couple posts where people are having this issue while others are not.  Internally, we do not see it.  TIU code 5.0 shouldn't have any impact on TMCC operation under DCS.

Dave Allen posted:

I have ordered a Wi Fi module, but have just discovered that the app is not available from the Apple site in Australia. How can I get around this please? ( Obviously, I'm in Australia).

Dave,

Can you do this?  Switch to the USA Apple Store....

Change your iTunes Store country or region

JimQ posted:

Has anyone had the problem of being unable to get engines off the inactive list?  I have experienced all the issues with multiple engines and multiple TIUS and when engines get moved to the inactive list the touch screen for the inactive list does not respond... Is this also part of the upcoming fixes?

In the current version of the app, the only way to move engines from inactive to active, or visa-versa, is to do a refresh (read).  

Any engine the system  finds on the track(s) will become active.  Conversely, any engine not found is moved to the inactive list.  There is a bug in some configurations that cause the read process to be erratic.  This is explained in more detail elsewhere in this thread.

Going forward, we have plans to add the ability to selectively move a single engine to and from the active or inactive list.  I envision simply touching and holding an engine name in the list and dragging it up or down.  This is not a trivial change but, I think it would be a benefit.  It will allow users to keep their active list small and limited to engines you are running instead of all engines on powered track.

Thank you, Dave.  The selective movement would be a benefit. 

When using a remote, I find the presence of an inactive list to be a pain, and avoid a read like the plague.  To recover froma read (my grandson often hits the button), I do a restore from the PC.

I can understand your position on keeping the active list small, but if MTH gets the read function straightened out so there isn't always doubt about what's controllable by the app, I think I'd prefer not to have locos drop into inactive.  All in all, I wish the app would just keep everything active, like the remote.

Gregg posted:

Gregg posted:

Hmm... Are you going to be able to fix the regular remote  feature reset at the same time. After 14 years it's changed,

It's my understanding the feature reset  doesn't work as well with the App???  The custom name  disappears.  Id sticks though.   

Hello.... ??? 

Robert,

I wish the app would just keep everything active, like the remote.

FYI, in order to use the All Engines feature (remote only at present) one must clear the Active Engine List of all engines that will not be participating in the session. Otherwise, error messages will be abundant.

I wonder what percentage of DCS users use the all engines feature.

I will

RJR posted:

I wonder what percentage of DCS users use the all engines feature.

I use it occasionally and I think it's a pretty handy feature to have.

MTHRD, thanks for the info...  For a while I was thinking I was the only one having this trouble...  I await the new firmware and app...  Any updates on when they will be available?  End of January? First quarter 2016??

I just tried running my 2 wifis through the home network instead of the MTH.  The read function might work better????????

Two Model Railroaders • Two Train Rooms • Two Layouts &

One Photo Story

Gary: Cheers from The Detroit & Mackinac Railway

RJR posted:

Thank you, Dave.  The selective movement would be a benefit. 

When using a remote, I find the presence of an inactive list to be a pain, and avoid a read like the plague.  To recover froma read (my grandson often hits the button), I do a restore from the PC.

I can understand your position on keeping the active list small, but if MTH gets the read function straightened out so there isn't always doubt about what's controllable by the app, I think I'd prefer not to have locos drop into inactive.  All in all, I wish the app would just keep everything active, like the remote.

 

Snap ring on both of my remotes..and it is pressure proof.

Steve Kilmer posted:

Thanks MTH. 

The bell shuts off when you press the horn on android. I think this is a bug.

I have had this happening also!

Well-known bug.  Supposedly already cured in forthcoming revised firmware/app.

It's only a problem on Android. It doesn't happen on iOS.

Update on testing.  Tonight I started up my 2 wius on the home network after first powering up all tracks.  Tablet would not read locos on wiu#2 (tiu#2)  I shut down the layout, and moved outputs from TIU#2 to TIU #1, doubling up on fixed 1 & 2.  Turned off WIU#2.  Switched WIU1 to MTH mode.  Powered up, turned on wifis, and tablet read every lcoo on layout, all 24.  Turned layout off, moved wires back to TIU#2, whose wiu #2 was slaved to WIU#1, and all 24 locos were read and operable by tablet.   Tried smartphone, and that would not read all locos.

I haven't have any idea why problems above have not repeated.

I wonder if different versions of android software are yielding different results?????

I posted this in another thread.

Dave Minarik said,  The app will not find any engines (time out error) with the Fixed 2 channel powered up. 

I was getting this error on two different layouts on two out of three Rev L TIUs

It all seems to be working now.  I changed nothing.

Dave

You sound frustrated, Dave.  I know the feeling when things start working after one does nothing.  Could the app save data that helps on future reads?

Not frustrated.  I just want to figure it out.

MTH RD posted:

350iroc posted:

I'm having and issue controlling my TMCC engine's through DCS after the 5.0 update. Any ideas? It's like the remote is no longer communicating to the TMCC base unit anymore. The red light is not blinking anymore when commands are being sent. 

I've seen a couple posts where people are having this issue while others are not.  Internally, we do not see it.  TIU code 5.0 shouldn't have any impact on TMCC operation under DCS.

I still am unable to control my TMCC engine's through DCS after the 5.0 update. Still operates perfectly with the Lionel CAB1 remote. I have the MTH TIU/TMCC DB-9 connector cable in the correct direction with TMCC labeled on one end and TIU on the other.  I've added, deleted, reset, inner track, outer track, upper track, 5 different engines without success.  I only have 1 TIU and have disconnected the WIFI for trouble shooting. DB-9 cable tested strait to TIU and in a splitter scenario. My current setup positively worked as it should before the 5.0 update. The red light no longer flashes on the base unit when executing DCS commands to it. I have two DCS remotes to test with. Again the Lionel remote works perfectly. Is there a way to tell if the MTH TIU/TMCC DB-9 connector cable is MTH part# 50-1032 or 50-1018? Is there a difference in these two part numbers and if so could this possibly be causing my inability to no longer run TMCC through DCS? I reaching here but I'm close to stumped....

# 50-1032 or 50-1018? Is there a difference in these two part numbers and if so could this possibly be causing my inability to no longer run TMCC through DCS?

Either one will work with a TMCC Command Base although the 50-1018 will not work with a Legacy Command Base.

If the command base light doesn't blink when you enter MCC engine commands on the DCS Remote, then most likely the problem is one of the following:

• You have the wrong cable (unlikely, if it worked before the DCS update)
• The cable is reversed end-for-end
• The TIU has a different DCS ID# than what  you told DCS was the DCS ID# of the TIU to which the cable is connected, when you added the TMCC engines.

Wow!  Lots of problems with new app.  I appreciate you guys working to figure this stuff out.

Harold,

Wow!  Lots of problems with new app.

See my post above. This has nothing to do with the DCS App and, most likely, has nothing at all to do with DCS.

I'm starting to strongly suspect that there are differences in the operational characteristics of the android and apple apps, that problems show up on one and not the other.  Weird things happen.  This morning, on my android tablet, the softkey screen was a blank until I exited the app and restarted it.  I also have 1 of my 3 devices that turns off the wireless connection for no apparent (as of yet) reason while the other 2 devices continue to operate.

Allscale posted:

I am having the same problem as 350IROC.  Since I went to 5.0, I have no control either with the remote or thru the WIU.  I have changed track sections,lock-ons, power supplies, locomotives, etc., and no joy.

Allscale

Allscale did you ever find a solution to getting your DCS remote to start communicating to the TMCC base?

RJR posted:

I'm starting to strongly suspect that there are differences in the operational characteristics of the android and apple apps, that problems show up on one and not the other.  Weird things happen.  This morning, on my android tablet, the softkey screen was a blank until I exited the app and restarted it.  I also have 1 of my 3 devices that turns off the wireless connection for no apparent (as of yet) reason while the other 2 devices continue to operate.

I can attest that operational characteristics between Android and iOS apps are fundamentally different.  There are differences in how the two platforms deal with Wi-Fi connections, behavior on return from lock screens, and more that we, as app developers, have no control over.  Of course, we try to mitigate these differences the best we can in terms of the user experience but, some differences just cannot be worked around in a practical manner.

The Android app losing the softkey list on occasion is a known bug and was addressed in the current release under beta test.  I think we squashed that one.

hclarke posted:

Wow!  Lots of problems with new app.  I appreciate you guys working to figure this stuff out.

 

While I can see where someone reading this forum thread may have the impression there are lots of problems, however, there are really relatively few critical issues and we are working hard to correct them. 

Please don't take this as a cop out but, given the complexity of what is going on in the overall DCS system, we feel pretty good about how well the apps and WIU are holding up in the real world.  In our lab environment, we simply cannot replicate the diversity in your applications out there.  We expected issues and yes, there are some but, we've addressed the critical ones and soon, with the release of new WIU firmware and app updates, the majority of issues identified will be resolved.

Admittedly, to address each and every issue would delay the release longer than we are comfortable with.  So, let us get the critical items fixed over the next couple weeks and then we'll swing around and hit some of the nuisance issues.  After that, the real fun begins as we add new features and enhance the many we already have.  

The fun of running trains in this new and flexible way is only just beginning.  Stay tuned.

Thanks for the update, MTHRD.  That softkey list loss has only happened to me once in several weeks of testing.

My observations is that, not only is what you say about android vs apple true, but there are diffferences between different android devices running different versions of android.  I can appreciate that this presents problems to MTH.

FYI, I started another thread "Multiple wifi units," so we users could interchange information about any special problems when using multiple wifis.  It seems us android users are the minority.  I'm looking forward to the app and firmware updates to see what issues they cure.

MTH RD posted:

hclarke posted:

Wow!  Lots of problems with new app.  I appreciate you guys working to figure this stuff out.

 

While I can see where someone reading this forum thread may have the impression there are lots of problems, however, there are really relatively few critical issues and we are working hard to correct them. 

Please don't take this as a cop out but, given the complexity of what is going on in the overall DCS system, we feel pretty good about how well the apps and WIU are holding up in the real world.  In our lab environment, we simply cannot replicate the diversity in your applications out there.  We expected issues and yes, there are some but, we've addressed the critical ones and soon, with the release of new WIU firmware and app updates, the majority of issues identified will be resolved.

Admittedly, to address each and every issue would delay the release longer than we are comfortable with.  So, let us get the critical items fixed over the next couple weeks and then we'll swing around and hit some of the nuisance issues.  After that, the real fun begins as we add new features and enhance the many we already have.  

The fun of running trains in this new and flexible way is only just beginning.  Stay tuned.

 

Do you have a beta program?  I'd be interested in helping out.

MTH RD, your second post was made while I was writing the above.  I agree that there are relatively few critical items.  Maybe I encounter more than the average operator because my layout is a bit complex---2 tius, 6 channels, 75 blocks, 38'x16'---and I wring out the capabilities.  I recognize that MTH has now gone into areas, apple and android and networking, where it doesn't have control of the operational devices.  Recognizing that MTH had limited ability to perform real world testing, I've been posting issues so you're aware of them and, more importantly for me, to pick the brains and experience of others.

I will say that I am encountering very few problems when I use my tablet.

My layout operation is fairly simple and I have not experienced any of the issues others are having.

But I have  to say I am very impressed with the support and communication from MTH on the forum during the initial release of Wi-Fi.   Very helpful.

Ed

Todd, the short answer is that the app/wifi cannot operate the Z4k receiver.

I don't see how, unless they come up with a way to connect a wifi unit to the receiver, and since the receiver is no longer made, I doubt there's sufficient market.  Using the remote was handy, when I would correct aderailment on the far side of the layout, and could use the remote to reset the Z4000 breakers.  But until the $25 app is released, with the ability to control switches, the app is of limited usability..

willygee posted:

RJR posted:

Thank you, Dave.  The selective movement would be a benefit. 

When using a remote, I find the presence of an inactive list to be a pain, and avoid a read like the plague.  To recover froma read (my grandson often hits the button), I do a restore from the PC.

I can understand your position on keeping the active list small, but if MTH gets the read function straightened out so there isn't always doubt about what's controllable by the app, I think I'd prefer not to have locos drop into inactive.  All in all, I wish the app would just keep everything active, like the remote.

 

Snap ring on both of my remotes..and it is pressure proof.

That is funny!

Robert,

Actually, I have a way that I believe it could be accomplished without any additional hardware. However, I haven't yet discussed this with MTH to determine if it's doable.

Todd,

Happy New Year to you and your family, as well!

Unfortunately, I just this morning learned that my proposed solution will not work. It would require additional hardware in order to have the app control Z4K Tracks.

I'll be keeping a DCS Remote handy!  

1'st issue with MTH WiFi. I am using the MTH home network. Engines are now in the inactive list. My iPad mini is connected to the MTH network, all 3 lights are on solid but there is no wifi connection to the TIU. The refresh button indicates no TIU found and the roster icon slowly fades in and out but the iPad  indicates the network is connected. From the get go the engines would all go into the inactive list when I closed down. I could however bring them into the active list by tapping and I ran trains but not now obviously. The TIU and remote still work just fine. Would this be in part related to the 'bug' referred to earlier? My initial thought was with the serial to usb cable but it was working fine and hasn't been touched or jogged.  Suggestions appreciated. FYI, glitches aside this is a great app and I am looking forward to more developments down the road.

It sounds as if the WIU has become disconnected from your Home network. You can proceed in one of two ways.

One is to attempt to reconnect the WIU to your home network by repeating the original instructions to do so.

The other is to switch to MTH mode and connect to the network generated by the WIU itself.

Feedback. My issues do not reflect on the DCS hardware nor  the WiFi software.  Suggestion #1 didn't work. #2 did. Finally got hold of my 'IT' guy who knows and has worked on my stuff and indicated the problem was probably with my older style router. It would be prudent to upgrade and I will. The MTH mode works great but it is a little cumbersome as the DCS Companion says. A long overdue router will be in place next week. Barry thanks for giving your time and advice.

Jim,

I'm happy to have helped.

Can I have more than one phone or tablet connected to the WIU at a time for multiple throttles ? I  haven't received my yet , so I wanted to know. I did read the online manual but didn't see anything about it .

 Thanks in advance.

          Dave 

Yes.

MTH RMD, while trial running with One of possible Four TIUs in the future, I have 2 comments.  I'm practicing with an Android tablet. (10.1"

1.  The coupler needs to be in the same screen as the throttle for switching purposes.

2.  When running with the remote, my engines continue in the same condition if they momentarily lose the signal from the TIU.  Is the app designed the same?

Thank you

I concur with Susan's comment #1, but I don't think there's space enough to fit both couplers in.  Fat fingers is a problem when using a smartphone.

Susan, re comment 2, yes, unfortunately, including a failure of device-wifi/tiu connections (including the E-stop).  Having a remote fired up is something to consider.

Regarding RJR's note to MTH RD on 1/8/16:

MTH RD, you asked:

Regarding the fixed 2 power up problem, are you saying that with active engines on fixed 1 simply applying power to fixed 2 makes the engines go inactive or, are you saying once fixed 2 is powered and you hit refresh (read) the engines go inactive? These are very different and if the latter, the bug fix I've talked about should resolve it.

In my own testing today, I found that applying power to fixed 2 after applying power to fixed 1 and refreshing the read makes the engines go inactive and the same thing happens when applying power to fixed 2 first and then to fixed 1.  If only fixed 1 is powered or only fixed 2 is powered, I seem to have no trouble powering Var 1 or Var 2 (both set to fixed) and reading the engines on those tracks.  As long as fixed 1 and fixed 2 are not both powered at the same time, I believe anything on a powered track comes up active. For testing I had up to 5 engines on each fixed track and it not seem to matter.  I hope this assists the folks at MTH who have been working feverishly on all of this.  As they used to say on TV: "Film at 11."

I also felt the uncoupling feature along with coupler 'close' should be on the engine control screen. It is a bit awkward bouncing back and forth between the two screens for realistic switching procedures. As for spacing, move the speedo up or make it smaller. The three coupling icons could be placed beneath. Just musing, not meant as criticism.  I am quite taken with the app and my only issues were with a defective 'serial to usb' cable and router. Both have been corrected and there have been no problems with  the MTH hardware or app other than the known playable whistle issue.

Jim,

along with coupler 'close' 

AFAIK, that's not something that any engine can do, PS2 and PS3 engines included.

JIMRK, my android app only has 2 coupler icons, plus headlights, smoke, & engine sound.

Sorry for the confusion guys, due to my poor choice of words.  What I meant was the 'CCS' coupler-close sound, which does not of course have an icon. 'CCS' could be used or an icon showing two couplers linked to-gether or something else if it ever sees the light of day.  It's not a big issue, but only  something that I would prefer for switching operations.

I don't recall encountering a coupler close sound, labeled as such.  Is this only on some locos, and it might be one of the numbered sound keys, like SO2?

I believe that Jim is referring to the "Auto Coupler Slack" sound, which on a DCS Remote would be on a soft key.

On the app, it's on the engine settings screen under "SOUNDS". It appears to be off by default (at least on the beta app).

I was actually referring to SCC (not CCS as posted, sorry. I'm going back to bed and start over)) which appears as such on the DCS remote as SCC, and on page 227 of the DCS Companion-3, but appears as 'Coupler Close' under Soft-Key Sounds on the app. Personally, I use it pretty well every time I link up.

JimRK

MTH RD:  Just want to report that the updated app & firmware appears to correct all the problems that I have reported.  Good job in getting the deficiencies created.

RJR posted:

MTH RD:  Just want to report that the updated app & firmware appears to correct all the problems that I have reported.  Good job in getting the deficiencies created.

Thanks RJR!  And, yes, we did do a good job in creating the deficiencies.  Fortunately, also in correcting them.  Ha, ha...  I knew what you meant.  Too funny.

Very glad to hear the updates helped you.  In this case, we found the bug and squashed it.  So, improvements were expected.  Sometimes, you can't find the bug and just throw poison around never really knowing if you've killed it.  Those are the worst kind.

I apologize for the typo.  I meant "cured" or "corrected." 

DCS WIFI Guru's

We upgraded 4 WIFI units to the new version so they question is /are

1. After you wait the three (3) minutes and disconnect the unit - How do you know the WIFI unit was actually updated. Their isn't a confirmation.

2. Is their a way to validate the upgrade is on the WIFI unit. I have the base application on both my Iphone 6S and my Droid. 

3. I can see all 4 WIFI units, each one shows up as an independent SSID so eventually I want to be able to create a Super TIU, When is this software update going to be available? How many can you link? I need the maximum amount possible or at least the same number of TIU's. Is their a plan to accommodate the use of up to to 5, 7 or 10 WIFI units?

4. Is their a plan to allow more than 5 TIU's to be put in to the super mode?

Thanks,

Kevin

H1000,

That is what I thought. I will have to pull them off the layout and check. Thanks.

Their should be a way to see that the update was completed via the application once you access the application from the phone.

Or some sort of acknowledgement.

Kevin

I think MTH RD has commented that they will be incorporating a confirmation page in the future, but they compromised a bit and wanted to get the WIU out to us sooner.  A small trade off I can live with.

Kevin,

3. I can see all 4 WIFI units, each one shows up as an independent SSID so eventually I want to be able to create a Super TIU, When is this software update going to be available? How many can you link? I need the maximum amount possible or at least the same number of TIU's. Is their a plan to accommodate the use of up to to 5, 7 or 10 WIFI units?

Super TIU is slated to be included the Pro version of the app, due out later this year.

4. Is their a plan to allow more than 5 TIU's to be put in to the super mode?

To the best of my knowledge, no there is not. However, you can try to add additional TIUs by "cheating", although this is not supported. For more information, refer to page 122-123 of The DCS Companion 3rd Edition.

This and a whole lot more is all in “The DCS Companion 3rd Edition", available for purchase  from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book!

PSU1980 posted:

DCS WIFI Guru's

We upgraded 4 WIFI units to the new version so they question is /are

1. After you wait the three (3) minutes and disconnect the unit - How do you know the WIFI unit was actually updated. Their isn't a confirmation.

2. Is their a way to validate the upgrade is on the WIFI unit. I have the base application on both my Iphone 6S and my Droid. 

...

Thanks,

Kevin

1. The WIU will reboot when the upgrade is complete. That's similar to what WiFi routers do when you upgrade them.

2. About the only way (for now) is to log back in the WIU to verify the firmware version. Doesn't actually take long. Did the five at the club last Saturday.

Barry and Matt - Thanks for the answers - We need to pull all the WiFi's units off the NJ Hirailers layout each time we do an upgrade. It would be really nice to have a message pop up saying the upgrade complete much like  when you upgrade the remote or TIU. I realize MTH is putting a lot of resources behind the updates - but that is a huge miss for many reasons including the lack of documentation in the recently released WIFI manual. 

Barry, your tight with these folks - please see what you can do. Simple and easy documentation + next upgrade because they are coming needs have a window saying, after the 3 minute wait an automated pop up window should appear with ===> Upgrade complete - power down and disconnect. Or what ever term they want.

That's a must.

Kevin

Kevin,

We need to pull all the WiFi's units off the NJ Hirailers layout each time we do an upgrade.

There's no need to take the WIUs off the layout, or disconnect them from their respective TIUs, to do the firmware update.

I just updated my 3 WIUs by simply turning on the layout upstairs, walking back downstairs, waiting a couple of minutes for them to stabilize, and then just doing the firmware updates downstairs at my Mac.

please see what you can do. Simple and easy documentation + next upgrade because they are coming needs have a window saying, after the 3 minute wait an automated pop up window should appear with ===> Upgrade complete - power down and disconnect

There is already an indication that the firmware update is successful. The WIU reboots, with a message, and then a  minute or so later the login screen reappears. In any case, noting the firmware revision before updating, logging-in after the update and seeing the new firmware revision will give you the explicit confirmation that you desire.

Regardless, I'm sure that MTH is aware that most folks would like to see an explicit indication that the firmware update was successful.

Barry,

Thanks for the info. I will have to start bring a laptop - Old fashion desk top is there now.

K

Kevin,

 I will have to start bring a laptop - Old fashion desk top is there now.

That's unnecessary as long as the desktop PC has WiFi capability.

We didn't pull ours off the layout. Just go over to each WIU and switch it to "MTH" mode and they'll show up as WiFi hot spots to your laptop. Connect to each one and do the upgrade. While it's rebooting, connect to the next one and repeat the process. Afterward we switched them back to "Home". I'm not sure how we'll need to configure them when the "Pro" version of the App is released, so for now all of them, along with the Legacy WiFi are on the club's wireless

Matt,

so for now all of them, along with the Legacy WiFi are on the club's wireless

If you assign each a static IP address via your router, you won't even have to switch them to MTH mode to do firmware updates. In fact, you won't even have to touch them at all.

Thanks for the tip, Barry. I had already put the WIU's on reserved IP addresses when we got them. Hopefully the pro version of the software allows this configuration for Super TIU mode.

Unfortunately, the desk top PC is about 7 generations old - So no WIFI - In fact, I don't think WIFI was a thought at the time the ones we have were built. 

So, we will make due with what we have.

Matt,

Hopefully the pro version of the software allows this configuration for Super TIU mode.

At this time, I see no reason why it would not. 

Thanks for the tip Barry, static IP is the way to go. I really love the ease of use and reliability of this Apple router.

RJR posted:

I wonder what percentage of DCS users use the all engines feature.

Better reply late tahn never.

We at the club (20 members) frequently use the ALL feature specialy during Open House sessions.

PSU1980 posted:

Unfortunately, the desk top PC is about 7 generations old - So no WIFI - In fact, I don't think WIFI was a thought at the time the ones we have were built. 

So, we will make due with what we have.

If your old computer supports USB, Netgear makes and USB WiFi network adapter that works very well.

Will this app development stop now?

Will we get the rest of the features in the pro version?

How about the functions list for consists (lash-ups)?

ie. Track signal?

Could we get engine sounds list to have actual descriptions?

Etc.. Etc..

According to the App Store, the last update was 2 years ago. I wouldn’t count on any new updates for obvious reasons. But you never know.

I have the app installed on an old iPhone 6 which is dedicated to running trains. Because it is an older iPhone version, it does not receive any iOS updates which would potentially break the app. Fortunately, I only have a small fleet of MTH engines. Once the app quits working, I’m dumping them on EBay. Someone else can enjoy these engines with their thumbwheel remote or pay $$$ for ERR upgrades.

I think once the smoke clears from the current MTH closure we'll know more.  I would think if they are breaking up the PS / DCS part of the company to it's own entity it will take a little time for the dust to settle.  I wouldn't say just yet there won't be any updates.