Skip to main content

  After realizing that the support and fixes for the issues with the app running on my Galaxy 5 weren't going to come quickly I decided to buy an iPad and wow what a huge difference. Now this app is really working well. It along with the SER2 installed makes my layout being run by this app a  whole lot better. The issues with routes and scenes not working are gone and for the most part everything works quite well. The soft keys are still missing in a DCS lashup other than that I haven't found any obvious issues. I really think the Android version might have been better off not being released yet. By the way now I understand what some have posted regarding engine selection. In the Android version the page is laid out different.

  I now believe Barry's input during development has a lot to do with why the i version works so well and I'm sure he has a busy life like most of us and doesn't need more work but I wish he would have had an Android to work with too.

 

  George 

  I

George,

I agree completely. The Apple version of the app operates very well, and as far as I know  the only beta testers who have been posting & helping us on the forum have been using Apple devices.

The android version is buggy and needs some work. I'm sure it will get done, these things never get fixed as fast as we want them to.

Maybe we should start a go-fund-me page to buy Barry & Marty a nice pair of Android tablets!

H1000

Have updated 4 TIU's and handheld remotes to v6 and saved the data from one handheld with all engines sorted out and switches set up in the AIU so I saved this and loaded into the other hand held remotes so all the same.

Finally got the premium app loaded into the tablet. So is there a way to get the file from the the hand held remote into the tablet Wi Fi App?? I sent the file to the tablet. Hit advanced features / import - export / import but does not allow me to look for anything?

To import a remote backup file into a Premium DCS App:

  • Change the backup file's name extender from .txt to .mth
  • Send yourself an E-mail with the renamed backup file as an attachment
  • Receive the E-mail on the smart device
  • Click on the attachment and select the DCS App as its destination
  • Follow the instructions from the DCS App.

Before you are too critical of any of MTH's beta testers, consider that their layouts may be more (or less) perfect than yours, that no two layouts are electronically identical, that no two home environments are wifi-idectical, and that no two operators are equally competent.  Also realize that beta testers may spend their available time on working out a bug and not have been able to dig out all the rest.

I use Android, have 2 TIUs and have no real issues.  I personally do not like having to do a read so often---would prefer if engines could stay in active list as they do in remote. 

When I really want to run trains, and have 5-6 running at once in interconnecting routes, I use remotes, in fact 2 of them.  I find a smartphone screen to be too small for my fat finders to always hit precisely, and a tablet is too large to hold in one hand.  The remote is more anatomically friendly.

I can no longer control accessories.  I set them up on the 1st night and used them without any issue.   Now  app can longer find the AIU, so the accessories is not working I have tried several nights and still the AIU is not found.    I can control the accessories using the MTH remote without any issues.    I can control engines using the app without any issue.   

I tried this on a 2nd device which allowed me to add the accessories on the APP.   I will test this a 2nd night to see if it can still see the AIU.   Does any one have steps or idea on how to get my 1st device to read the AIU?

 

Last edited by PatapscoValleyRR

Today, I went to York and talked to the MTH techs about my issue with seeing the accessories on my iPhone app.   We set up the app to work with the accessories at the MTH Demo layout and it worked without issue.   I came home and added the accessories back on my iPhone on my layout.    I did read for the layout and did a refresh on the accessories.   I can now see both my TIU and AIUs.  I will do more testing tonight and post.   

Barry replied to my ? ; To import a remote backup file into a Premium DCS App:

  • Change the backup file's name extender from .txt to .mth
  • Send yourself an E-mail with the renamed backup file as an attachment
  • Receive the E-mail on the smart device
  • Click on the attachment and select the DCS App as its destination
  • Follow the instructions from the DCS App.

OK but where at what point do I change the "Change the backup file's name extender from .txt to .mth"

I have tried this in the files part of the computer but it does not let me add this extender? do I need to go back and hook up everything again to the TIU And remote and download it again? does it allow me to rename it .mth at this point?

Thanks for any help.

kj356 posted:

Barry replied to my ? ; To import a remote backup file into a Premium DCS App:

  • Change the backup file's name extender from .txt to .mth
  • Send yourself an E-mail with the renamed backup file as an attachment
  • Receive the E-mail on the smart device
  • Click on the attachment and select the DCS App as its destination
  • Follow the instructions from the DCS App.

OK but where at what point do I change the "Change the backup file's name extender from .txt to .mth"

I have tried this in the files part of the computer but it does not let me add this extender? do I need to go back and hook up everything again to the TIU And remote and download it again? does it allow me to rename it .mth at this point?

Thanks for any help.

   KJ356,

   To change the file extension in windows go to the folder you saved your remotes back up file then right click on the file and a small window will open to the right, look down the list and you will see "Rename". Left click on that then you will notice the file name will be highlighted at that point you can either rename the whole file or just the file extension. It doesn't matter what you call the file just make sure you end the file name with .mth so it could look like ( mybackup.mth) and it will be in the correct format. One last note the mth is case sensitive if you do it in caps the app will not recognize it, at least that has been my experience.

  George

I reviewed the entire string but did not find an answer to a connection/use question I have.  Currently I have a TIU and Legacy Command base.  I run both systems on my layout. I have not connected  the TIU to the Legacy base.    I have the LCS WiFi (which i like), a SER2 to run accessories,  and have now ordered the MTH WIU. My TIU does not have an USB port.  Since I will be able to run my Legacy and TMCC engines with the MTH App, I do not see a reason to connect the the TIU to the Legacy base.  I will connect the WIU directly to the SER2 via the DB9 port. I believe this hook up will allow me to run both MTH and Legacy/TMCC engines using the MTH App and use the Legacy and DCS handhelds as well. Am i correct? Any downsides to this arrangement?

 Thanks. 

ToledoEd posted:

I reviewed the entire string but did not find an answer to a connection/use question I have.  Currently I have a TIU and Legacy Command base.  I run both systems on my layout. I have not connected  the TIU to the Legacy base.    I have the LCS WiFi (which i like), a SER2 to run accessories,  and have now ordered the MTH WIU. My TIU does not have an USB port.  Since I will be able to run my Legacy and TMCC engines with the MTH App, I do not see a reason to connect the the TIU to the Legacy base.  I will connect the WIU directly to the SER2 via the DB9 port. I believe this hook up will allow me to run both MTH and Legacy/TMCC engines using the MTH App and use the Legacy and DCS handhelds as well. Am i correct? Any downsides to this arrangement?

 Thanks. 

 The WIU must be connected to the TIU.  The TIU and WIU are all part of the MTH WiFi app system.  The TIU must be connected to the Legacy base via the SER2.  This is the only way the App is able to push Legacy commands to the Legacy base and then to the Legacy engines.  A serial 9pin "Y" cable that Barry mentioned earlier 1M to 2F will allow both the WIU and the SER2(Legacy) to be connected to the TIU if it does not have the USB available.

Last edited by MartyE
Tom Schlotterbeck posted:

I  know I am late for this question but I have a problem with the accessories & switches

I have imported the remote file (twice) and all the switches & accessories are listed but not highlighted

which means I can't select any to operate - what do I need to do to fix?

thank you in advance for your help in this matter

  Tom,

  The only time refresh didn't  work for me is when a pop up window told me that I needed to purchase the premium app even after I thought I did. I'm going to assume that isn't your issue but have to ask if you are able to access everything from you remote. Obviously if you can't that has to get fixed first. Most likely that isn't the issue either but just the same I thought I would mention those things. 

  Lets say all at the remote is working well and you know you have the premium app. Can you add a switch in the app? That will tell you if it sees both your tiu and aiu. The reason I ask is I've had a lot of issues with my Android and this app doing what I expect however now that I have an ipad all has bee very good and I don't know what your using.

  I hope this helps or at least gives you some ideas.

Dave Zucal posted:

Is the  Cab 1 (TMCC) base capable of relaying the Legacy commands, from the MTH Premium app, to a Legacy engine, or do I need a Cab 1L base?

Dave,

   The if you have the tiu connected to the tmcc base you can control the legacy engine in tmcc mode only. To get the legacy features you need a legacy base along with a Lionel SER2 and the MTH adapter cable. A few times earlier in this thread the part numbers have been listed for the serial adapter and cable. 

 George

GManning35 posted:
Tom Schlotterbeck posted:

I  know I am late for this question but I have a problem with the accessories & switches

I have imported the remote file (twice) and all the switches & accessories are listed but not highlighted

which means I can't select any to operate - what do I need to do to fix?

thank you in advance for your help in this matter

  Tom,

  The only time refresh didn't  work for me is when a pop up window told me that I needed to purchase the premium app even after I thought I did. I'm going to assume that isn't your issue but have to ask if you are able to access everything from you remote. Obviously if you can't that has to get fixed first. Most likely that isn't the issue either but just the same I thought I would mention those things. 

  Lets say all at the remote is working well and you know you have the premium app. Can you add a switch in the app? That will tell you if it sees both your tiu and aiu. The reason I ask is I've had a lot of issues with my Android and this app doing what I expect however now that I have an ipad all has bee very good and I don't know what your using.

  I hope this helps or at least gives you some ideas.

I can add the switches and accessories manually -I am using an android tablet

Thanks for the help - I guess I will add all twenty items manually 

That is true, but one never knows when one will want to use the remote, and it should be same version as the TIU.  If for some reason the tablet/smartphone disconnects from the wifi, it's nice to have a remote handy.  Do be aware that the red E-stop button on the wifi system myst be pressed for a second or so, unlike the remote's.

You're welcome.  Glad to have been of help, Dude.

GManning35 posted:
Tom Schlotterbeck posted:

I  know I am late for this question but I have a problem with the accessories & switches

I have imported the remote file (twice) and all the switches & accessories are listed but not highlighted

which means I can't select any to operate - what do I need to do to fix?

thank you in advance for your help in this matter

  Tom,

  The only time refresh didn't  work for me is when a pop up window told me that I needed to purchase the premium app even after I thought I did. I'm going to assume that isn't your issue but have to ask if you are able to access everything from you remote. Obviously if you can't that has to get fixed first. Most likely that isn't the issue either but just the same I thought I would mention those things. 

  Lets say all at the remote is working well and you know you have the premium app. Can you add a switch in the app? That will tell you if it sees both your tiu and aiu. The reason I ask is I've had a lot of issues with my Android and this app doing what I expect however now that I have an ipad all has bee very good and I don't know what your using.

  I hope this helps or at least gives you some ideas.

well now I have all the switches & accessories programmed in the tablet and is working well

I noticed that the remote and the tablet do not update each other

Is this the way it is supposed to be?

I have a question on where are the TIU settings kept. Do they reside in the TIU or the handheld remote/smart phone?

The reason I am asking, is when I was setting up the TIU options on my first smart device when I was using the WI-FI app, I set the TIU options for Super TIU, all channels in fixed mode.  I noticed that when other smart phone is added, the added smart phone does not reflect the updated TIU settings and I need to add "super TIU & all fixed channel" in all additional smart devices being added.

Not sure if there is a bug where the smart device is not reading the TIU correctly or all the TIU options are stored in the individual handheld device.

 Thanks,

 Bob D

Last edited by rad400
RJR posted:

With the remote, after pressing TRK and selecting this track, does thumbwheel have any effect on the output voltage? 

Can you move the circuit over to VAR 2 and see what happens?   I'd set the wifi aside and check this out with the remote.

Changed Var to Fixed.  Remote working fine.  Will test wifi later.

I am having problems upgrading my remotes to 6.0.  I was able to upgrade my 3 TIUs no problem.  I have followed the directions but the program is seemingly not finding the TIU/remote when plugged in.  I have newer USB TIU's.  Do I need to use the plug I used when I updated the TIU?  Should the power on the remote be on or off?  He;p

John

John,

Do I need to use the plug I used when I updated the TIU?  Should the power on the remote be on or off? 

It works like this:

  • Do not have the 1/8" jumper installed
  • The remote's power should be off when you start the process.
  • When told to hold the remote's power button in, click Continue and continue to hold it down until told to release it or until the update is complete. If the remote powers up at any time in the process, the update has failed.
  • You'll typically be told to hold it down, release it and then hold it in again.
  • The last time you'll be told to hold it in, you'll be holding it for about 5 minutes.
  • After the process is completed, disconnect the remote from the TIU before powering it on.
  • Power cycle the TIU before updating another remote.

DCS Book CoverThis and a whole lot more is all in “The DCS Companion 3rd 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!

Hi, can someone explain exactly how to add a legacy engine in the mth dcs app? Do you still need the command base attached or does it work without? I put the switch on program, apply power, add legacy engine, select tiu, name it, select address 1, and hit done right? then I shut off power to the track let engine shut down, switch back to run and restart. Legacy engine doesn't respond to the mth wifi app commands and when I refresh the app the engine is moved to inactive. Am I missing something?

 

Michael

Michael,

In order to operate your Legacy engines in Legacy mode, with all Legacy Features, you'll need the following:

  • Legacy command base
  • Legacy SER2 module
  • Power/serial cable combination for the SER2.
  • MTH cable #50-1032.

Refer to this thread and read it all the way through.

If you are OK with operating your Legacy engines in TMCC mode, then all you need is any command base and the MTH cable. The reason for all of the extra stuff to operate Legacy engines in Legacy mode is because the Legacy command base cannot accept Legacy commands directly into its serial port.

enginEErjon posted:

I like the ability to export the app (remote) settings to a file and email that file to others. Options also exist to use messages or other means of file sharing. It appears that you can essentially clone one remote to another without any computer involved. 

Have you done that?

How are you going to clone a remote to another remote?  Remotes are not connected to the APP.

Hello Everyone,

I was using a USB Cable to Type B USB adapter to upgrade my TIU to 6.0.   I used the same cable to successfully upgrade to 5.0 when I purchased the WIFI app.   My problem is the TIU no longer powers up.  When I first tried to upgrade the loader said it could not find my TIU.   I had the  jumper cables in place, per Barry's book,  prior to powering on the TIU.   I removed everything and attempted to power the TIU back up to see if it would still work with 5.0 since I couldn't get it to recognize the TIU for the upgrade..  Unfortunately, the red light no longer comes on.   Is it possible something could have fried the TIU?  I'm unable to run any trains at this point. 

 

Sorry, I said Variable but I meant Fixed one.   I use the standard non-auxiliary input used for powering a TIU.  I have MTH bricks powering all four inputs to be honest.   I've had the TIU for about a year and I've upgraded it in the past.  I left the TIU powered through these channels during the upgrade.  I wasn't sure if that would be an issue.

Barry Broskowitz posted:

Gary,

1. How do you get tmcc engines out of the inactive list?

2. Why would a TMCC engine be put in the inactive list in the first place?=

Don't refresh the app unless you have to do so.

Refresh acts like a DCS Remote READ command. It sorts DCS engines into the Active and Inactive engine lists depending upon whether or not they're sitting on powered tracks. Also, just like the DCS Remote's READ command, all TMCC, Legacy and DCS lashups got to t he Inactive list.

The solution is to do the following from the Engine Roster Screen:

  • Tap Edit
  • Use the slider to the right of the TMCC or Legacy engine to move that engine up into the Active List.
  • Tap Done.
  • Tap the engine to select it.
  • Go back to the Engine Control Screen and operate the engine.

 

3. Why do you need to select the TIU each time you add a tmcc engine?

For the same reason you need to do it every time that you add a TMCC engine to the DCS Remote. DCS needs to know o which TIU the command base is connected.

This is all in The DCS WiFi Companion, coming soon!  

Barry, is the DCS WiFi companion something you did on your own, or is it sponsored by MTH.  The downloaded DCS WiFi manual is incomplete, in my opinion, and I wonder why we are expected to pay for a complete manual such as yours.  If you did it on your own, kudos to you for the effort!

Bob

Bob,

is the DCS WiFi companion something you did on your own, or is it sponsored by MTH.

I am the sole author of the book.

MTH is the distributor of The DCS Wifi Companion's eBook version, which is the only version available at present, as well the distributor for my first book, The DCS Companion, now in its 3rd edition.

MTH also provides the services of an outstanding graphic artist who assists me with the book's composition, formatting and appearance. Other contributors are my daughter, Stacey MacMillan, who is an excellent proofreader (and also a published writer herself), and fellow DCS beta testers Marty Fitzhenry and Jim Osborne, who provided a technical review of the book.

The downloaded DCS WiFi manual is incomplete, in my opinion,

The original documentation that MTH provides is adequate for learning and using DCS via the DCS Remote, and the documentation available for the WiFi system's WIU hardware is all that's necessary to install and configure the WIU.

Documentation for the DCS App is pretty much on a par with what's available for most smart phone and tablet apps of a similar price point. If you were to compare the DCS App's documentation to the available documentation for the competition's WiFi app, you would find that this is the case.

and I wonder why we are expected to pay for a complete manual such as yours.

You are under no obligation to purchase any other documentation, authored by myself or anyone else, to use the DCS Application, or for that matter, DCS via the remote. However, consider my books to be a method whereby one can go beyond what's normally documented in order to have the best DCS experience possible.

Further, if you were to add together the cost of the DCS Application's Premium version ($24.95) and the cost of The DCS WiFi Companion eBook ($13.95), the total of $38.90 is less than the cost of the competitor's WiFi app alone, which is $49.95.

The decision regarding whether or not to purchase either of my books is a personal one, not something that one has to do.

Last edited by Barry Broskowitz
Barry Broskowitz posted:

The devices that were used successfully include iPhone 7, iPhone 6, iPad Mini 2, and iPad Mini 4.

We've operated both in Normal and Super TIU modes. WiFi connections were both in MTH and Home modes.

Hi Barry,

We have setup our Club`s layout with 4 WIUs+TIUs in HOME mode + SUPER TIU mode.

Unless I missed it, I did not find in your new WiFi book anything saying that we can or can`t operate many WIUs, all of them being in HOME mode.

Could you confirm that a multiple "WIUs" setup in HOME mode is OK ?

Note: So far, everything seems to be working fine with that configuration, with the exception of the "All Engines" operation not the passing the DCS commands on TIU #2,3,4. (passing the DCS commands on TIU 1 only)

Thanks.

 

Barry Broskowitz posted:

Daniel,

Could you confirm that a multiple "WIUs" setup in HOME mode is OK ?

Yes, one can connect multiple WIUs in Home network mode.

Is there a known issue with the "All Engines Operation" when using multiple WIUs ? (ALL of our 4 WIUs are in HOME mode in our case) 

The problem: With the IOS Premium APP, when using the "All Engines Operation", we are losing control on the engines as soon as they leave the WIU-TIU section of the layout from where the "All Engines Operation" was first initiated.

Our setup: (pictures are attached)

We have 4 WIUs on our layout and ALL of them are in in HOME mode. 

All 4 WIU are at firmware 1.1

All 4 TIU are at DCS 6.0 and are properly numbered 1-2-3-4 and are properly set to "Super TIU"

IOS Premium APP is at v2.0.0

iPhone 7 (A1778) with IOS 10.3.2

Thanks

 

 

Attachments

Images (16)
  • File 2017-05-23, 11 20 11 PM
  • File 2017-05-23, 11 20 00 PM
  • File 2017-05-23, 11 19 50 PM
  • File 2017-05-23, 11 19 41 PM
  • File 2017-05-23, 11 19 29 PM
  • File 2017-05-23, 11 19 21 PM
  • File 2017-05-23, 11 19 13 PM
  • File 2017-05-23, 11 18 58 PM
  • File 2017-05-23, 11 18 45 PM
  • File 2017-05-23, 11 18 28 PM
  • File 2017-05-23, 11 18 05 PM
  • WIU 1 Firmware
  • WIU 2 Firmware
  • WIU 3 Firmware
  • WIU 4 Firmware
  • File 2017-05-24, 7 31 33 AM
Last edited by Daniel Auger

I am unable to operate in a Lashup with Dcs wifi. I'm trying to Lashup two identical proto 3 diesels. I am able to operate each engine independently with the WiFi premium app, and I am able to build the Lashup, but I can't power up, power down, or run the Lashup. The engines just sit on the track. 

I am able to run the same Lashup fine with the dcs remote.

I have tried both the home and mth WiFi options with the same result. 

I have two blocks running off of fixed one and fixed 2. Signal strength is 10 throughout layout. 

All functions on WiFi app seem to work with exception of Lashup. 

Any thoughts? 

Adam Fischer 

Adam,

I am able to operate each engine independently with the WiFi premium app, and I am able to build the Lashup, but I can't power up, power down, or run the Lashup. The engines just sit on the track. 

if you can describe exactly what you're doing and exactly what responses you're getting, we can try to see where is the problem.

I can attest that, during and since beta test, I and the other beta testers found that, aside from minor stuff that was either fixed prior to app release or that will be fixed in first app update, lashups work just fine.

Sorry for the fire drill everybody.  In my zeal to get the wifi module and app "up and running", I neglected to upload the DCS 6.0 software.  I was running 5.0, which I thought was sufficient.  Next time I will spend more time reading before rushing to install.  

NOTE: 6.0 is required for Lash-Ups, and probably other features as well.

Thank you to Barry who was instrumental in troubleshooting.  I wouldn't have figured this out, as my brain was already way past walking it back to square one.  Thanks again for the help.  I'm up and running.....although when running in lash-up the screen that controls the voice commands, coupler slack sounds, crossing horn etc. is blank.  I have literally been running successfully for 10 mins though, so I think i will spend some time with it before I cry wolf again.  Stay tuned.........

Adam 

 

 

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

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

Thanks,

Bob D

NJ-Hi Railers

Bob,

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

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

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

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

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

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

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

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

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

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

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

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

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

Edited portion marked with *

Last edited by H1000
Barry Broskowitz posted:

Bob,

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

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

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

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

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

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

Barry

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

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

Thanks,

Bob D

H1000 posted:

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

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

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

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

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

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

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

Edited portion marked with *

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

Thanks,

Bob D

rad400 posted:
H1000 posted:

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

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

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

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

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

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

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

Edited portion marked with *

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

Thanks,

Bob D

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

Bob,

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

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

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

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

Hi Barry,

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

 

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

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

Gerry

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

Gerry 

Gerry,

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

From page 115 of The DCS WiFi Companion:

Exporting the DCS Application's Contents

To export a DCS Applications contents, proceed as follows:

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

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

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

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

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


DCS Book CoverThis and a whole lot more about DCS WiFi is all in MTH’s “The DCS WiFi Companion 1st Edition!"

This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store!

Thanks Barry. I do have your book and I did read it (lucky me, a 5 hour airport delay out of Phoenix last Tuesday, and grateful I had my tablet and your book). I would encourage anyone who is using this app to get it.

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

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

Gerry

Last edited by gmorlitz
Barry Broskowitz posted:

Daniel,

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

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

Hi Barry,

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

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

Note: Our Club setup is: 4xWIU/TIU, Home-Mode via WiFi-Router, TIU DCS 6.0, WIU F/W v1.1,  Premium IOS App V2.0.0.

Thanks

 

Add Reply

Post
The DCS Forum is sponsored by

OGR Publishing, Inc., 1310 Eastside Centre Ct, Suite 6, Mountain Home, AR 72653
800-980-OGRR (6477)
www.ogaugerr.com

×
×
×
×
Link copied to your clipboard.
×
×