MTH Wifi Unit can't find TIUs

Today, I switched all the hook ups to my second TIU, but wifi unit still reads No TIUs Found. Could my wifi unit have gone bad? I still need help.

Do you have a dcs remote as well? Can it find the tiu?  

Is your device  set to MTH in your wifi settings?

Greg. Thanks for the reply. Yes, the remotes pick up the TIU no problem. 

Jeff, the WIU is set for MTH, not home. All I can think of is that the 9-pin serial to usb cable is bad, however, it is the same cable that I used to update the TIUs to 6.0.

Would love to know the answer as I'm having the same problem.  I've even changed the USB to serial cable and still no luck finding the TIU. 

I don't know if it matters for sure, but how is your TIU getting power? Don't go by the lights. Do you have it powered separately?

My TIU is powered via an external wall wart.   

I posted a week or two back on this issue. My I phone always finds the TIU.  My Android  started  TIU not found so I bought a @$50, 7in android tablet an it worked fine for  a week then started the TIU  not found.  There has to be a system issue somewhere, in all cases the setup of TIU, Wifi , aux power and track power were not changed. Just turned off and on for run sessions.

I had the same issue with my iPad.  I put an engine on the missing TIU track and started it with the remote.  The TIU magically appeared on the iPad after an application reboot.

Yeah but I don't have a remote any more. 

Sound dumb, not trying to insult anyone but make sure the device bluetooth is connected to the proper device. 

just like using your wifi on the phone. Seen people struggle with this and they simply overlooked connecting the device and application.

I have exactly the same problem with all my ipads and phones, my system is new so I didn't have to do any upgrades so I cant comment if the problem is in the upgrade

I have taken lots of screenshot pictures of the fault and I am in touch with MTH tech department

When I get the solution I will post it

I have had the wifi working months ago when I first got it. Just back to running locos and can't get wifi working. I have it set to mth. I connect on my iPad to the mth network using the default mthdcswifi password but it won't add engines. Connection times out and I think said no tiu found. Tiu is powered by. Z4000 and I see red light. My handheld works fine, sees TIU and all engines. I have a new TIU do I need to perhaps update the wifi software?the wifi unit is lit showing tiu connection but the app software under settings says no tiu connection. Tried on iPhone and iPad. 

do I need to perhaps update the wifi software?

I expect so, for two reasons:

• MTH says that you should.
• You're having problems that no one should even attempt to resolve until you're using the recommended TIU software.

I appreciate that but it’s frustrating  why something would work and then stop for no reason. The Wi-Fi  worked fine at one time. The TIU is new so I thought that was current with software. Anyway I’ll check the TIU and Wi-Fi to make sure both are current- the l process to update the Wi-Fi seems a bit more complicated but let’s see. 

I have been working on my layout for the last two months. Just this last weekend I finally get  a loop put together to run the Polar Express along with other engines. My wifi setup couldn't find the TIU either. My wife's son happened to be over and asked if I was hooked up to the network. I amused it would do this automatically but as it turns out I have to go into my settings on my iPhone (this is where yours and everyone's else's router in the neighborhood is viewed) every time I boot the system and select the MTH network to find my TIU. After that, train life is good.

I'm surprised so many of your are having such a fundamental issue.  We need to get to the bottom of it and get things resolved for all of you.  There is no reason we know of for you to be experiencing this issue given the current version of firmware in your system.  So, let's start with that.  Please be sure your gear is updated to the following revisions:

1. TIU -  v6.1
2. WIU - v1.1
3. App - v3.0.1

Once you are fully updated, if things still aren't working properly, reset each component.  I know it's a pain to reset the app if you have a lot of stuff loaded but, just export it and then import the image after the reset.  It's important to get your system to a point that is current and known.

TIU - Reset via the app or remote.  A feature reset should be adequate so you don't lose the TIU address.

WIU - Reset by holding down reset button (on top) for 10 seconds or more.

App - Reset by tapping "More > App Settings > App Reset"

There are some things you can try prior to the updates and reset that could be the issue but, given you guys are experienced, I doubt it.  Now, just because I said that, don't be embarrassed to come back and update us if it was a simple oversight.  I do it all the time.  The system is complex and has many elements.  It's really easy to miss a step.

Go to "More > App Settings" and make sure the app is set to DCS WIU.  (the latest version adds support for the Explorer and this setting may have gotten changed accidentally)

Go to "Settings > Wi-Fi" on your device and verify it is connected to the WIUs MTH network or your home network if you are in HOME mode.

Please report back here with your results.  Hopefully, we'll find the culprit in these steps but, have no doubt, the system is actually working fine and getting more and more stable with each app update.  We're working on a new update now with further enhancements .  It should be out in a couple of weeks.

mrmuggs posted:

Today, I switched all the hook ups to my second TIU, but wifi unit still reads No TIUs Found. Could my wifi unit have gone bad? I still need help.

In your case, 6.0 should be close enough.  So, if your other gear is up to date, try just resetting the WIU and cycle power on the TIU.  That is, power it down completely and then after resetting the WIU, power the TIU back up.  If you're connecting the WIU and TIU via USB cable remember TIU is powered by the USB so, unplug it as well.

I appreciate that but it’s frustrating  why something would work and then stop for no reason

What changed is that the app is a newer release than what you used previously.

One more thought.  There is a known bug wherein if you have multiple WIUs powered up but one of the connected TIUs is not powered up.  It causes timeouts and issues because the system doesn't get a response from the dead TIU.  

So, for testing purposes, make sure there is only one WIU powered up or, if there are multiple, be sure all TIUs  are powered up (red LED).

The update we're working on has this issue corrected.  In theory, user's wouldn't have WIUs powered without TIU power but, we ran into it here and so, we're modifying the app to ignore any unresponsive TIUs and just carry on with any that are alive. 

This is another example of how the system will keep improving.  If you kill all the weird corner cases and unusual bugs, the net result is a more robust and stable system.  We've not spent a lot of time polishing the premium app as we were busy developing the Explorer hardware and app.  So, now our attention is turned back on cleaning up some things on the power user side.

Firstly I must publicly thank Nicholas Jones of MTH who spent days with me trying to find the problem

We started by updating and resetting everything then removing all from track and adding engines one by one and testing, I got to 3 MTH engines to work then it failed again with the "no active TIU found" message, also TMCC engines failed to load same message. 

It did look like a problem with the handshaking between the WIU and the TIU because as previously stated the remotes were still working, it was just the WIU to TIU connection that was failing.

However here is the good news, as a last ditch effort this morning in order to minimize any problem with the connection between WIU and TIU I added a separate dedicated  power supply to the TIU via the  "power" socket

As of now all my TMCC and MTH engines are running

Well done Nicholas

masoner posted:

Firstly I must publicly thank Nicholas Jones of MTH who spent days with me trying to find the problem

We started by updating and resetting everything then removing all from track and adding engines one by one and testing, I got to 3 MTH engines to work then it failed again with the "no active TIU found" message, also TMCC engines failed to load same message. 

It did look like a problem with the handshaking between the WIU and the TIU because as previously stated the remotes were still working, it was just the WIU to TIU connection that was failing.

However here is the good news, as a last ditch effort this morning in order to minimize any problem with the connection between WIU and TIU I added a separate dedicated  power supply to the TIU via the  "power" socket

As of now all my TMCC and MTH engines are running

Well done Nicholas

 

I'm really glad you got your issue(s) worked out.  Thanks for your comments and I'll pass them on to Nicholas.  

Let me try to clarify some things that may have been contributing to your woes.  

First, if the TIU is connected to the WIU via USB then the TIU itself is powered however, the track may not be.  You cannot read engines on the track without track power.

If you power the TIU via fixed 1 input then, the track connected to fixed 1 only is powered.  In this case, there is no difference in terms of the TIU behavior.  Said differently, if you are having success powering the TIU with aux power then, powering the TIU using fixed 1 will produce the same results.  The TIU doesn't know the difference between these power sources.

Finally, TMCC engines cannot be "loaded" into the remote or app.  TMCC engines can only be communicated to and do not respond in any way.  There is no way for the system to load them or know if they are on the track or not.  The user must tell the remote or app that a TMCC engine is active.

Again, glad to hear things are working well now.  Even if the cause is unclear.  Maybe the track power supply you were using as input to fixed 1 has some noise or something.  What is the power supply you were using to power the TIU via fixed 1?  Is it operating on 50 Hz? 

Thanks for your thoughts, it could well be that the 50HZ 18V AC 10 amp supply to the TIU had some adverse effect on the TIU as you say cycles or even noise causing the TIU to lose its handshaking with the WIU, that might indeed be the case because it all works for the first few minutes of startup !  all I can say is that feeding the TIU directly with 18V DC has solved my problem.

( ps the input 1 and 2 are both permanently supplying power to the track hence my comment earlier that the remotes work fine, the TIU and the WIU were both powered up during the issues that I was having). 

It might be worth investigating in case some other overseas users are having issues with 50HZ, and unless its a fluke on my setup then the direct DC power to the TIU might solve it.

I understand your TMCC comment, my point was that I could not reconnect them because of the " no TIU found" message, but it works now !

Once again thanks for your efforts

Cheers and a Happy Holiday to all the OGR folks

For me I update the wifi software, I powered the TIU using three power sources, the wifi, the z-4000 in fixed one and another brick. The handheld works fine. The wifi tiu light blinks but the software says no tiu found. If I try to add engine it just times out obviously with no tiu found. I only have one wifi and one tiu  connected. I am connected to the mth router and I have tried reset a couple of times. Maybe just a bad wifi router?

Railmonkey,

What revision of TIU do you have? Are you using a USB cable or a USB to Serial adapter?

 A blinking TIU light on the WIU means the WIU can't connect to the TIU.

Something to also consider. The WIU can power the TIU via a USB connection but the WIU doesn't provide enough power to fully operate the TIU. You will want to make sure you have power to the FIXED 1 port or the AUX power port.

Its a new tiu region  version L how do I check the software version without a computer hookup? It's connected via USB and I have fixed 1 powered in addition to power to the aux power port. Only thing left I can possibly do is do an update to the tiu - I had already updated the handheld and a previous tiu so maybe something is out of sync assuming a new tiu has the latest version may be a wrong assumption 

Its a new tiu region  version L how do I check the software version without a computer hookup?

If you cannot see the app to see the TIU from the app, then you'll need to use a DCS Remote to learn the TIU's software version Menu/System/TIU Setup/TIU Version

assuming a new tiu has the latest version may be a wrong assumption 

It may well be that it has a version of software that's too old to work with a WIU. You should be using DCS 6.1, although it probably would find the TIU if using DCS 6.0. The Rev. L TIU's originally came with DCS 4.2, which would not connect with the WIU.

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!

My handheld is 6.0, TIU is 6.1 and the app is 3.0.2 which just updated today. On my iPhone I got a tiu connection but would not add engines. On my iPad I still get no tiu connection. At various times I've reset the tiu and the wifi, tried three different power sources, two tiu' s and even swearing but no luck !

Wanted to do show and tell with the grandkids today but luckily the handheld works. I think I'll set this aside until someone else has an issue or a solution is found. I even tried another older serial tiu I have but that didn't connect either. Last thing that crossed my mind is if the wifi update took? 

Thanks for everyone's help tho

Firstly two things, have a lovely time with the grandchildren I am glad the handhelds work, secondly I am not trying to cut across all the advice that you have been given.

With the help of MTH I have been successful after 2 weeks of frustration, the advice I was given was to go back to basics 

1. ensure all devices are the current REV 

2. remove all devices from the layout taking power off the track

3. because it worked for me , power the TIU directly into the power socket on the side, I used a Lionel starter set power pack 18V DC ( I know MTH and others have said no need, but I am not convinced)

4. power up and make sure all the 3 lights on the WIU are on and steady, no flashing except the Wi-FI when it is connecting

5. put just one MTH engine on the track

6. power up and start the handheld app, you should be able to fined the engine and run it

Good luck

If that works just keep adding engines

Good luck

Hey guys, I continue to experience issues with the DCS Wi-fi App and have attempted various troubleshooting attempts at no avail. It's become extremely frustrating in that I end up not running any trains when I'd like to out of frustration of the app connectivity issues and stop even trying - at the risk of sounding melodramatic, it's impacting my enjoyment of the hobby! I'm actually starting to scour Ebay looking for used DCS remotes to see if that gives me consistently better connectivity. Here's a log of my attempts to isolate and remediate, perhaps someone can review and ensure I'm not missing anything obvious - maybe @MTH RD or @Barry Broskowitz could review my attempts below or provide guidance? Happy to provide any logs out of the app or WIU if that will help

Full disclosure, I work in IT infrastructure, so I've been using some toolsets to assist in troubleshooting (e.g. VMware Fusion, Flame 2 for Mac for Avahi/Bonjour Snooping, PFsense Firewall). I have yet to whip out WireShark in earnest, but that's we're I'm heading next.

Problem Summary:

1. Frequently, DCS WiFi App is unable to connect to WIU/TIU, despite multiple refreshes of the app, rebooting the phone, rebooting the DCS components
2. When a connection is established to the WIU/TIU, frequently the App loses connectivity while performing operations, resulting in loss of control of trains, track, and accessories - I've had a number of occasions where a locomotive's horn or whistle "sticks on" when the app loses connectivity mid-command.  This seems particularly prevalent when addressing variable track power voltage

Despite multiple troubleshooting approaches and attempts to isolate the issue, I cannot find a reliable solution to allow me to consistently connect using the DCS WiFi Android App.

Hardware:

Handheld Devices used (All Android):
1. Google Pixel, Android 9 (Pie) - connected to home WiFI (same subnet and layer 2 network as WIU)
2. Samsung Galaxy SII, Android 7 (Jelly Bean) - Connected to MTH_DCS-365C (dedicated WIU network)
3. Virtual Machine (Android x86_64) Android 7.1 (Nougat) - NAT connectivity with the physical workstation, on same layer 2 network as WIU

MTH DCS Components
1. DCS TIU Rev L (USB)
2. DCS WIU

Firmware/Software Versions:

- App: 3.1.0 Build 49
- WIU: MTH WIFI DCS 20160107-1007 / LuCI mthdcs-v1.1rc1-1-gd26bd7d Release (git-15.205.28457-77acfe0)
- TIU: v6.10

Configuration:
TIU powered via an external 12v/2A Power Source
WIU Wifi switch set to "MTH"
WIU cabled to home network via CAT-5E cable, DHCP address set statically from router (pfsense) (note this wired configuration is outlined in the DCS WiFi user guide - set the WIU to "MTH" but cable the device to the network)
"Default" device is my Google Pixel phone, so ideally I'd be able to connect and us it for controlling the trains

With the above setup, I see transient connectivity issues, with successful connection rates only about 10% of the time when using a wireless android device

Troubleshooting Steps:

1. Ensure all Android devices with the DCS Wifi App installed are either powered off or not connected to local network other than the device being used to control the WIU
2. Attempt Refresh within the app using the refresh icon
3. Close DCS WiFi App on Phone
4. Reboot Phone
5. Reset the application and restore previous locomotive/track/accessory data via an exported configuration file
6. Connect with Samsung phone (direct connection via MTH_DCS-365C SSID)
7. Reboot WIU
8. Reboot TIU
9. Reboot both WIU and TIU
10. Reset the TIU
11. Confirm layer 3 connectivity via IPv4:
12. Verify Avahi/IPv6 Discovery:
13. Try "Home" wifi connection only on WIU (e.g. unplug the Cat5E and set the setting switch to "Home" rather than MTH)

Findings:

1. Greatest success rate is when using the Android VM on my laptop, although even that only has about a 70% successful connection rate
2. Greatest failure rate is when using my Google Pixel on my home Wifi network (~10% successful connection rate)
3. Despite confirming layer 2 and layer 3 connectivity, frequently the DCS WiFi app is unable to successfully connect to the WIU/TIU
4. The WIU System and Kernel logs aren't particularly illuminating - I see some generic warnings, but no red flags:

Fri Jun 29 14:10:20 2018 daemon.warn avahi-daemon[1151]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!

Fri Jun 29 14:10:24 2018 daemon.warn dnsmasq[1199]: no servers found in /tmp/resolv.conf.auto, will retry

Questions:

1. How does the DCS WiFi app "discover" the WIU? I assume it's via Avahi/IPv6 discovery or mDNS.
2. Can multiple DCS WiFi apps be connected to the same WIU at the same time? My testing indicates the answer is "No"
3. When establishing connectivity to the WIU, presumably there is a handshake to the TIU. Is there a way to reliably determine whether the DCS WiFi app is connected to the WIU, but the WIU is not communicating to the TIU?

mattrain posted:

Hey guys, I continue to experience issues with the DCS Wi-fi App and have attempted various troubleshooting attempts at no avail. It's become extremely frustrating in that I end up not running any trains when I'd like to out of frustration of the app connectivity issues and stop even trying - at the risk of sounding melodramatic, it's impacting my enjoyment of the hobby! I'm actually starting to scour Ebay looking for used DCS remotes to see if that gives me consistently better connectivity. Here's a log of my attempts to isolate and remediate, perhaps someone can review and ensure I'm not missing anything obvious - maybe @MTH RD or @Barry Broskowitz could review my attempts below or provide guidance? Happy to provide any logs out of the app or WIU if that will help

Full disclosure, I work in IT infrastructure, so I've been using some toolsets to assist in troubleshooting (e.g. VMware Fusion, Flame 2 for Mac for Avahi/Bonjour Snooping, PFsense Firewall). I have yet to whip out WireShark in earnest, but that's we're I'm heading next.

Problem Summary:

1. Frequently, DCS WiFi App is unable to connect to WIU/TIU, despite multiple refreshes of the app, rebooting the phone, rebooting the DCS components
2. When a connection is established to the WIU/TIU, frequently the App loses connectivity while performing operations, resulting in loss of control of trains, track, and accessories - I've had a number of occasions where a locomotive's horn or whistle "sticks on" when the app loses connectivity mid-command.  This seems particularly prevalent when addressing variable track power voltage

Despite multiple troubleshooting approaches and attempts to isolate the issue, I cannot find a reliable solution to allow me to consistently connect using the DCS WiFi Android App.

Hardware:

Handheld Devices used (All Android):
1. Google Pixel, Android 9 (Pie) - connected to home WiFI (same subnet and layer 2 network as WIU)
2. Samsung Galaxy SII, Android 7 (Jelly Bean) - Connected to MTH_DCS-365C (dedicated WIU network)
3. Virtual Machine (Android x86_64) Android 7.1 (Nougat) - NAT connectivity with the physical workstation, on same layer 2 network as WIU

MTH DCS Components
1. DCS TIU Rev L (USB)
2. DCS WIU

Firmware/Software Versions:

- App: 3.1.0 Build 49
- WIU: MTH WIFI DCS 20160107-1007 / LuCI mthdcs-v1.1rc1-1-gd26bd7d Release (git-15.205.28457-77acfe0)
- TIU: v6.10

Configuration:
TIU powered via an external 12v/2A Power Source
WIU Wifi switch set to "MTH"
WIU cabled to home network via CAT-5E cable, DHCP address set statically from router (pfsense) (note this wired configuration is outlined in the DCS WiFi user guide - set the WIU to "MTH" but cable the device to the network)
"Default" device is my Google Pixel phone, so ideally I'd be able to connect and us it for controlling the trains

With the above setup, I see transient connectivity issues, with successful connection rates only about 10% of the time when using a wireless android device

Troubleshooting Steps:

1. Ensure all Android devices with the DCS Wifi App installed are either powered off or not connected to local network other than the device being used to control the WIU
2. Attempt Refresh within the app using the refresh icon
3. Close DCS WiFi App on Phone
4. Reboot Phone
5. Reset the application and restore previous locomotive/track/accessory data via an exported configuration file
6. Connect with Samsung phone (direct connection via MTH_DCS-365C SSID)
7. Reboot WIU
8. Reboot TIU
9. Reboot both WIU and TIU
10. Reset the TIU
11. Confirm layer 3 connectivity via IPv4:
12. Verify Avahi/IPv6 Discovery:
13. Try "Home" wifi connection only on WIU (e.g. unplug the Cat5E and set the setting switch to "Home" rather than MTH)

 

Findings:

1. Greatest success rate is when using the Android VM on my laptop, although even that only has about a 70% successful connection rate
2. Greatest failure rate is when using my Google Pixel on my home Wifi network (~10% successful connection rate)
3. Despite confirming layer 2 and layer 3 connectivity, frequently the DCS WiFi app is unable to successfully connect to the WIU/TIU
4. The WIU System and Kernel logs aren't particularly illuminating - I see some generic warnings, but no red flags:

Fri Jun 29 14:10:20 2018 daemon.warn avahi-daemon[1151]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!

Fri Jun 29 14:10:24 2018 daemon.warn dnsmasq[1199]: no servers found in /tmp/resolv.conf.auto, will retry

 

Questions:

1. How does the DCS WiFi app "discover" the WIU? I assume it's via Avahi/IPv6 discovery or mDNS.
2. Can multiple DCS WiFi apps be connected to the same WIU at the same time? My testing indicates the answer is "No"
3. When establishing connectivity to the WIU, presumably there is a handshake to the TIU. Is there a way to reliably determine whether the DCS WiFi app is connected to the WIU, but the WIU is not communicating to the TIU?

 

 

we get that "no WIU/TIU found"  all the time too.  we just click ok and then it works for a while.

we do not even have our wiu hooked up to anything else but the tiu.

just not sure these wiu's are all that robust.

I'm guessing on this but I think you get that semi-generic message when there's poor track signal as well?

I get it too and I can't remember why right now. I do know that when the signal is strong and things are right, I don't get that message.

I also have to check my phones wifi settings regularly. If the phone is in stand-by and the WIU is powered down, the phone will switch to my house's router. It won't go back unless the phone's power is cycled with the DCS all powered up, or I make it change thru the phone's settings.

If that occurs, I get no TIU found message.

mattrain posted:

Try "Home" wifi connection only on WIU (e.g. unplug the Cat5E and set the setting switch to "Home" rather than MTH)

 

Questions:

1. How does the DCS WiFi app "discover" the WIU? I assume it's via Avahi/IPv6 discovery or mDNS.
2. Can multiple DCS WiFi apps be connected to the same WIU at the same time? My testing indicates the answer is "No"
3. When establishing connectivity to the WIU, presumably there is a handshake to the TIU. Is there a way to reliably determine whether the DCS WiFi app is connected to the WIU, but the WIU is not communicating to the TIU?

 

 

To clarify, the "HOME" mode is for wirelessly connecting the WIU to a home router / access point, not for connecting a device with the app installed.  As you stated earlier, the MTH mode is for the WIU to connect to a home network via a wired connection and/or connecting devices with that app installed directly to the WIU using the wireless signal from the WIU.

I use MTH mode with my WIU which is wired to my home router and connect devices through my router's wireless network and other devices directly to the WIU using the wireless signal from the WIU.

To answer your questions:

I have researched some of the discovery process and it appears to be a simple IP scan on a particular port. There has been some discussion in the past about how the WIU is discovered by the app. I have found it better to statically assign an IP address in the LuCi web console on the WIU vs. a static DHCP address assigned by the router.

I have had up to 6 devices connected to my WIU at one time. Two connected through my home wireless network to the WIU via a wired connection and 4 other tablets connected to the WIU (in MTH Mode) using the built in wireless from the WIU. Haven't had an issue yet with this configuration.

The WIU will indicate a connection to the TIU when the TIU light is solid purple. A flashing Purple light indicate no connection, or the WIU is searching for the TIU.

Okay, now some troubleshooting can happen directly on the WIU just by looking at the indicator lights. I have had the stuck horn issue you described and using the lights on top of the WIU I was able to diagnose the problem. In my case, when the Horn was stuck I would press the horn button on my phone app (connected to the WIU via wired) and could  not see the blue light flash indicating network activity.  Then I tried the horn on my tablet (connected via the WIU wireless) and saw the Wi-Fi light flash and the horn shut off. I can't recall if the TIU light also flickered to indicate that it received the command from the WIU (I think it did but will confirm that functionality this evening). It turned out to being a problem with my phone, I rebooted it, and it worked like a champ again. 

Are you using more than one WIU?

 

To clarify, the "HOME" mode is for wirelessly connecting the WIU to a home router / access point, not for connecting a device with the app installed.  As you stated earlier, the MTH mode is for the WIU to connect to a home network via a wired connection and/or connecting devices with that app installed directly to the WIU using the wireless signal from the WIU.

I use MTH mode with my WIU which is wired to my home router and connect devices through my router's wireless network and other devices directly to the WIU using the wireless signal from the WIU.

Thanks @H1000 for your reply and tips.  Yep, what you describe above is exactly my configuration - I actually ran CAT5E through the attic and down inside the wall so I could "hardwire" my WIU in the event that my connection issues could be attributed to the signal from the WIU to my AP. I keep the Samsung Galaxy connected directly to the WIU using the MTH SSID and my other devices are connected via my network.  What is odd is I can see the DHCP lease for the Samsung Phone on the WIU LuCi but I still see the transient "No WIUs/TIUs Found" message in the app on that device:

It does seem to be more reliable after a few refresh attempts within the app, but I'd expect if the phone has an active DHCP lease from the WIU, it should be able to discover on the first or second try.

 

I have researched some of the discovery process and it appears to be a simple IP scan on a particular port. There has been some discussion in the past about how the WIU is discovered by the app. I have found it better to statically assign an IP address in the LuCi web console on the WIU vs. a static DHCP address assigned by the router.

I set the IP statically for my WIU from the LuCI but am still seeing the "No WIUs/TIUs Found" when using my Google Pixel on my home network with no ability to discover after multiple refresh attempts.

 

Okay, now some troubleshooting can happen directly on the WIU just by looking at the indicator lights. I have had the stuck horn issue you described and using the lights on top of the WIU I was able to diagnose the problem. In my case, when the Horn was stuck I would press the horn button on my phone app (connected to the WIU via wired) and could  not see the blue light flash indicating network activity.  Then I tried the horn on my tablet (connected via the WIU wireless) and saw the Wi-Fi light flash and the horn shut off. I can't recall if the TIU light also flickered to indicate that it received the command from the WIU (I think it did but will confirm that functionality this evening). It turned out to being a problem with my phone, I rebooted it, and it worked like a champ again. 

Thanks for the tips regarding the LEDs - the behavior is consistent with my experience, I can "see" the WIU receiving my commands via the Blue LED and can confirm TIU connectivity is solid via the pink/purple LED. The problem is really establishing the initial connection with my preferred device (Google Pixel) to even get the Blue light to flicker :-)

 

Are you using more than one WIU?

Nope, just one WIU and one TIU

I think I am going to see if I can find a used DCS remote somewhere and give that a go. At the end of the day if that gives me a more reliable connection/experience, I'll just use that rather than the app. I do enjoy the "exercise" of troubleshooting the network/WIU/etc, but on the other hand sometimes I just want to run trains :-)

I will try a WireShark packet capture this weekend to see what I can find. I am interested to learn how discovery works, as it has to be leveraging some sort of multicast protocol (whether Avahi, mDNS, or something else). I do see the WIU listening on TCP 38715, which makes me think that once it is discovered, commands are sent via that port

Matt,

Just some extra info, when I exported my configuration file from the WiFi App I found some interesting tidbits near the end. The app stores (the last known good?) IP addresses of the WIU found and an associated port number, and in my case that port was 40588. Below is a sample portion from my file:

"name": "MTH TIU on mthdcs-xxxx ttyUSB0",
      "network_address": "192.168.1.251",
      "port": 40588

I too have had problem with Samsung devices, more specifically the S7 phone. It had a hard time connecting to the WIU wireless network and didn't like the fact that there wasn't an internet connection available on it.  Also the power saving features on Samsung devices in general would play some havoc with the DCS app. I've never really been able to get my Wife's S7 to work with the WIU connected to either wireless network. She didn't seem mind that problem...

How well does it work when you disconnect the wired connection and just run from the WiFi provided from the WIU?

BTW Matt, Checked out you website and layout. VERY NICE!!

Guys,

There are bugs in the import process when importing from a DCS Remote. The TIU identification may be hosed up.

Matt,

Just wanted to see how your progress is coming with your WIU connectivity? Were you able to pinpoint the problem?

I've tried the last couple of nights to simulate your problem without much success.