Upgrade MTH wi-fi DCS system

Premium App

Scroll down for the downloads.

The Premium version of the DCS App is an in-app upgrade. You access it as follows:

• Open the DCS App
• Tap Run My Trains
• Tap the icon at the bottom-right for the More... Screen
• Tap Upgrade.

You'll have the option to purchase either the Standard app or the Premium app.

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!

Thanks

I just downloaded the wifi upgrade on my iPad and am having difficulty getting the Lash Up feature to work.  I go through the steps to create a lash up between two GG-1s.  I receive an error message saying "Command Failed, Lash Up initialization command failed".  I got the same error message when I tried to lash up two steamers.   Is there a bug in the software or might I be doing something wrong?

Thanks,

Tom

Tom,

There's no bug in the DCS App's lashup building process. In fact, it works very well.

However, make certain that you have the WIU using firmware version 1.1.

Thanks Barry I will check this out.  

A suggestion that you may or may not want to pass on to the MTH s/w developers ... it would seem that the s/w app should be able to automatically check the version of the WIU firmware and simply state that the firmware needs to be updated to version thus and so rather than reporting an error message that offers no diagnostic value.

Tom

Tom,

it would seem that the s/w app should be able to automatically check the version of the WIU firmware and simply state that the firmware needs to be updated to version thus and so

How do you propose that the app reaches that conclusion? The app doesn't necessarily know what software it requires.

rather than reporting an error message that offers no diagnostic value.

How does the app know that the cause of the error is due to a wrong version of software in the WIU, and not for some other reason? All the app can know is that it got an unexpected result that prevents it from executing a command.

Barry,

Glad that you asked.  I suspect that you have been involved with the developers of the app during beta testing (wish that I had been).  While I have never done real-time programming, I have programmed in Fortran, C++, and visual basic, not as a programmer per se, but for the purpose of doing engineering analysis.  Okay, with that as I background, I would suggest the following programming logic:

1.)  During the upgrade download process, I would have provided a message that states the required firmware for the app.

2.) Then, I would have programmed the upgraded app to check the currently installed WIU firmware version (this is available in the LuCI so it should also be available to the app, right?)

3.) Next, I would have the s/w check to see if the firmware meets the requirements.  If not, I would post an error message at this point.  Otherwise, after someone enters all of the information for a lash up, I would post the error message at this point (you need to upgrade to version 1.1 or higher) rather than stating that the command failed.

Does the above seem reasonable and implementable?

BTW, my WIU had version 1.1, but I reinstalled it and will check tomorrow to see if this fixes the lash up problem.

Thanks for what you do on the forum,

Tom

Tom,

I have programmed in Fortran, C++, and visual basic, not as a programmer per se, but for the purpose of doing engineering analysis.  Okay, with that as I background, I would suggest the following programming logic:

Regarding my background, I have made my career in the information systems and cellular industries, and have multiple degrees in the computer sciences, That said...

1.)  During the upgrade download process, I would have provided a message that states the required firmware for the app.

That's not possible, for 2 reasons:

• The download process is proprietary to Apple and Google, and cannot be modified by MTH.
• The app doesn't know what firmware has been developed, perhaps to accommodate correcting an app bug, since the app was developed.

2.) Then, I would have programmed the upgraded app to check the currently installed WIU firmware version (this is available in the LuCI so it should also be available to the app, right?)

Again, there are two issues:

• LuCi is accessed via a web browser in a manner that the app cannot emulate.
• The app doesn't know what version of WIU firmware has been developed since the latest version of the app was developed. The WIU firmware could have been modified because of an issue found in the app that was subsequently resolved by a change to the WIU's firmware.

3.) Next, I would have the s/w check to see if the firmware meets the requirements.  If not, I would post an error message at this point.  Otherwise, after someone enters all of the information for a lash up, I would post the error message at this point (you need to upgrade to version 1.1 or higher) rather than stating that the command failed.

Same reasons as above.

Does the above seem reasonable and implementable?

Not, it does not, as stated above.

While it may be possible to do something to accommodate your request, I wouldn't thing the possible, small amount of information (for the above reasons) would be worth expenditure of limited resources to do so.

I am still having problems getting the lash up feature to work on the WiFi controller.  I have attached two screen shots.  The first screen shot shows two options at the bottom of the screen - "add engine" and "build lash up".   I notice that both options are grayed out which in normal convention means that these options are not available.  Is this normal??

But, I am able to add engines and proceed down the lash up option.

However, when I try to lash up  engines (that also exist on the remote), I receive the following error message ... "Command Failed - Lash Up initialization command failed".  Is there an issue with having the lash up already defined on the remote??

Barry replied to my first request for help that firmware version 1.1 is required.  I checked the firmware on the wifi unit and it had version 1.1 installed, but to be sure, I reinstalled it.

Would appreciate any help that can to solve this problem.  I have some guests coming by on Saturday to see my layout and would love for things to be up and running.

Thanks,

Tom

Tom,

I am still having problems getting the lash up feature to work on the WiFi controller. I have attached two screen shots. The first screen shot shows two options at the bottom of the screen - "add engine" and "build lash up". I notice that both options are grayed out which in normal convention means that these options are not available. Is this normal??

This is normal because the two options are not "grayed-out". Rather, just select an option to proceed.

But, I am able to add engines and proceed down the lash up option.

Of course, since this is normal and they aren't "grayed-out".

However, when I try to lash up engines (that also exist on the remote), I receive the following error message ... "Command Failed - Lash Up initialization command failed". Is there an issue with having the lash up already defined on the remote??

No, there is no such issue. Each copy of the app in a smart device and each remote is completely unaware of every other device or remote.

Whatever is your problem, that most definitely is not it.

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!

Just in case this post would be useful:

https://ogrforum.com/...28#72805549399467128

Barry & Daniel thanks for your replies,

I am getting over whelmed with keeping track of the needed firmware and DCS versions for the system to work properly.

I've confirmed that I am using firmware version 1.1 in the wifi unit.

Daniel - apparently, I need to be using DCS version 6 (rather than 5) for lash ups to work properly.  How do I determine what version of DCS I am using?

Thanks,

Tom

I am sure glad I got this all done!

At the end of the day, MTH WiFi is the way to operate TMCC and MTH Locos.  I have the advanced APP on an Android & an iPhone 7 plus.  Good luck: Tom, it will all come together.

Gary

Tom Jasper posted:

...

Daniel - apparently, I need to be using DCS version 6 (rather than 5) for lash ups to work properly.  How do I determine what version of DCS I am using?

Thanks,

Tom

Tom, to know the TIU DCS version installed:

1) using the Remote Handheld:  Menu > System > TIU Setup > TIU Version > TIU #

2) using the WiFi DCS App:  Run My Trains > More >  Advance Features > System Settings > TIU Settings > TIU # > Read TIU Firmware Version

FYI, when Turing on the remote, the remote's DCS version is briefly displayed.

Thanks guys for your help.  As it turns out, I am running DCS version 5.0 and will spend time today updating it to version 6.0.  Hopefully, this operation will go smoothly as I have friends visiting tomorrow am and they want to see the trains operate.  Tom

I am happy to report that after installing DCS version 6.0, the DCS WiFi is working beautifully ... I installed two lash ups and they both were a breeze.  Daniel and Gary - thanks very much for the tip on DCS 6.  In a perfect world the DCS system would automatically inform the user that a new DCS version number needs to be installed.