More on this issue: My cheap RCA Android tablet was having TIU not found issues again. Usually a shut down- restart would get it going again. So I added a brand new PS-3 engine and it found it Fine. Later I pulled out a PS-2 engine that had not been run for awhile, charged the battery and put it on the track. My RCA searched and searched but could not find New engine. Frustrated, I got My Samsung Galaxy Tab S-2 Android tablet which has the wifi app loaded and it found a new engine ok. I then turned the RCA tablet back on to see if could find the engine and I got TIU not found and on the S-2 it went to, TIU not found. Turned off the RCA and the S-2 worked fine again!. Today I deleted the DCS App on the RCA then reinstalled it and it's working great. I notice that it asked me if I was using TIU WIFI or Commander. Don't remember seeing that before. MY conclusion is that the APP got corrupted some how and started the problems. Maybe the quality of the RCA tablet isn't up to hard usage, so I will see how it stands up now. Haven,t tried both Android devices at the same time after the App reload on the RCA. A issue for another day
Today I deleted the DCS App on the RCA then reinstalled it and it's working great. I notice that it asked me if I was using TIU WIFI or Commander.
Based on that, I'm wondering if the release of the app (not its version) on the RCA device was older. If os, deleting and reinstalling the app yield the latest version.
I strongly suggest that you have autoupdate turned on for all smartphones and tablets that use the DCS App.
H1000 posted: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.
Hi H1000-
Not much progress unfortunately. I filed a formal ticket with MTH and was told I'd be given a call back within 3 business days... it's since been 5. So much for meeting their SLA.
In the interim, I did setup another device (LG G4 VS986) and completely reset the app on that device and did not import a config from another instance. It seemed to work reliably for the first couple of hours or so but then exhibited the same WIU/TIU connectivity issues as the other devices.
The issues persist and given the transient nature and the fact that it occurs across multiple devices and via different network configurations, I'm inclined to believe it may be the WIU itself. I'd love to test with another WIU but I don't really want to shell out another $150... I'll update this thread if/when I hear back from MTH.
Whelp I found a reliable (although not ideal) fix for my issues:
I broke down and purchased a DCS remote and sure enough it works consistently and reliably, which indicates the issue is north of the TIU. I'm still waiting on a call-back from MTH support, but given the performance of the DCS handheld, the issue must lie in either the app or the WIU. I'm inclined to say it's my WIU. Next time I have a friend over with an iPhone, I'll have them install the app and see if they experience the same issues I have with all of my Android devices.
I'll update this thread if I hear back from MTH support but for now at least I can run my trains consistently when I want.
Attachments
Images (1)
So I had some recent developments in my testing - had a friend come over last evening with a new iPhone, connect to my home's wireless network and download the Wi-Fi DCS App for a side-by-side comparison. Lo and behold his app connected immediately to my WIU while in my other hand my Android phone (Google Pixel) reported the same "No WIU/TIUs Found." I was able to discover all locomotives and run them a few times around with no issues whatsoever using the iPhone.
So it would appear the issue around WIU/TIU discovery is isolated to the Android port/version of the Wi-Fi DCS Application - given that I've only been testing with Android phones/OSes up to this point, it makes sense that the issue occurs irrespective of Android version, device type, or Wi-Fi connection (MTH or Home) - the root cause is the Android App itself. I still have yet to see or hear a response from MTH support on my earlier ticket, I will likely open another ticket this weekend to see if I can get a call back. Given the results of this latest test, I may procure an older iOS device and attempt further testing for more data, but I'm confident I've isolated it down to app/platform.
At the end of the day, however, a separate iOS device to run my trains defeats the raison d'etre of the DCS phone app - that is to use my everyday handheld device to run and control my trains. For now, I'll just continue to use the DCS remote I purchased and keep an eye for app updates.
I have a Note 9 and the App works fine everytime. but my Asus Android tablet will give me the "Not Found" message everytime. It's on a recent version of Android too. I just gave up using the tablet at this point
mattrain posted:Whelp I found a reliable (although not ideal) fix for my issues:
I broke down and purchased a DCS remote and sure enough it works consistently and reliably,
I've run my DCS trains with a variety of iOS and Android devices:
- iOS: iPhone 7, iPad mini, iPad mini 4
- Android: Best Buy 8" Flex Tablet; Amazon Kindle Fire Tablet
mattrain posted:So I had some recent developments in my testing
Matt,
I've had some developments in testing as well. A family friend with a Google Pixel phone came over on Sunday and I remember your troubles with the Google Pixel. His phone has worked in the past without issue but he was telling me how he had just upgraded the android version 9. I had him retry the MTH app that was still installed from a couple months ago and we had the same problems you were experiencing, on the same phone that worked perfectly before with an older version of android (I suspect 8.1).
I didn't have much time to test other settings. There are some reports that the WiFi power settings and IPv6 on android 9 can cause some significant issues for some users & apps. I still feel that there is a system setting someplace that is causing you problems.
Hi all,
I dug in a bit more today on this issue and was able to work past a few of the persistent problems I was seeing, where now I can consistently leverage the DCS WIFI app on my Android devices. To summarize the steps I took which seem to have significantly improved performance:
- Changed Network Configuration back from static to automatic (DHCP client) within the MTHDCS LuCI interface and set a DHCP reservation on my firewall/router using the eth0 MAC address of the WIU
- Switched out the power supply from a 5v/1000mA to a 5v/2000mA power supply
I've found after doing the above, the WIU is much more stable and I'm able to use the DCS WIFI app much more consistently. That being said, the WIU's network stack still appears to be buggy - I still see the network stack freeze up on occasion (can't ping internal or external IP addresses or resolve DNS names). And the fact that assigning the IP address statically within the LuCI interface appears to have broken routing, it would point to some firmware or software bugs within the WIU itself.
The key "tipoff" that there were networking issues with my WIU was the fact that it appeared the WIU was not getting NTP updates (running "date" from the WIU/BusyBox shell, I saw September 2018. Once I reconfigured my network to "statically" assign the IP via my firewall rather than the WIU itself, I was able to update ntp using ntp -p ip_of_NTP_Host)
I was able to troubleshoot my issues within the WIU since the OS is built on OpenWRT Linux and BusyBox:
It was definitely a bit of a learning curve and trial and error, as not having the full BASH shell makes things a bit more difficult.
Hopefully my trials and tribulations will help others if they experience issues. Perhaps @MTH RD can take a look at the WIU firmware for network stability improvements, and at least perhaps work on the static IP configuration settings within the LuCI AP Mode Wired Configuration :-)
To Summarize my environment:
Hardware:
Handheld Devices used (All Android):
1. Google Pixel, Android 9 (Pie - Build number PQ1A.190105.004) - connected to home WiFI (same subnet and layer 2 network as WIU)
2. LG G4, Android 6.0 (Build number MRA58K)
MTH DCS Components
1. DCS TIU Rev L (USB)
2. DCS WIU
Firmware/Software Versions:
- App: 3.2.1, build 53
- 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 Wireless AP disabled
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)
Attachments
Images (2)
I don't remember if this was discussed before, have you don a reset on your Wi Fi?
Matt,
This is odd as I have statically assigned IP addresses in my WIU's without issue. My only wild guess at this point is how your Network router handles ARP and RARP replies to ensure all devices on your network are aware of each other. I have run into routers in the past that didn't like wireless devices communicating to wired devices that had statically assigned IP addresses. The solution was to input static entries into the ARP table of the router.
I have used stripped down versions of OpenWRT (Chaos Calmer) on other projects and even a few basic needs wired routers without problems. The first version of the WIU firmware (1.0) was based on Barrier Breaker, the upgrade to Chaos Calmer was nice in firmware 1.1.
I have, use, and enjoy WiFi, Bluetooth, DCS, Legacy, and all the other whizbang stuff that's around in the hobby these days, but to tell you the truth, I think I still prefer the handheld remote for running my trains. I just bought another DCS remote a couple of weeks ago, and I'm thinking of buying another one or two as additional backups for the several I have now. I also have Lionel Legacy (Cab 1L) and several of their LionChief+ locomotives with Bluetooth. I must admit that for easy setup and running, the Lionel Bluetooth works pretty darn well. Bought their Universal Remote as well so I can control up to three of the Lionel locomotives with a single remote. Still, I also had great success running a couple of Lionel Christmas trains with my iPhone.
I'm no techo-geek. I just want to run trains with something close to consistent reliability.
H1000 posted:Matt,
This is odd as I have statically assigned IP addresses in my WIU's without issue. My only wild guess at this point is how your Network router handles ARP and RARP replies to ensure all devices on your network are aware of each other. I have run into routers in the past that didn't like wireless devices communicating to wired devices that had statically assigned IP addresses. The solution was to input static entries into the ARP table of the router.
I have used stripped down versions of OpenWRT (Chaos Calmer) on other projects and even a few basic needs wired routers without problems. The first version of the WIU firmware (1.0) was based on Barrier Breaker, the upgrade to Chaos Calmer was nice in firmware 1.1.
Interesting - yeah the oddest thing I'd see was from the WIU I could ping within my subnet no issue, but hitting anything beyond the gateway would hang completely, even with other devices on the same subnet having no issues routing out - also DNS lookups were not working using the gateway. I'm not sure about the ARP issue, I'm using PFSense as my router, I'll have a look around the ARP settings, but of all of my devices on my network, the WIU is the only one where I've seen this issue. I did confirm before changing the static setting on the WIU LuCI that the route tables were correct, which is why I think something isn't kosher between the LuCI web interface and the ethernet interface configurations. After changing back to DHCP config on the WIU and setting a DHCP reservation in PFSense, I have not seen the same routing issues.
I did find in the XML export from one device's DCS WIFI app that the IPv4 is stored, so I don't believe that AVAHI/mDNS is required every time the app is launched (although re-iping the WIU needed an app reset to rediscover and re-store the IPv4 info for the WIU, so there must have been some sort of AVAHI/multicast traffic to re-identify the WIU IPv4 address).
I'll continue my testing efforts to see if I can further isolate the issue. I did note that upgrade to Chaos Calmer which is good news! Thanks for your continued support!
This thread is well over a year old, and a lot of us are still having the issue of "tiu not found" with the MTH interface unit. I love MTH trains, but this has been extremely frustrating. One day it works, the next day it won't. My handheld remote is always reliable. For the money I put out for the Wifi unit and the money spent on upgrading the app to premium, I would expect better results. I've tried every remedy here yet I am experiencing the same issues many others are. I had hoped that running my trains through my iPad would have increased my 10 year old grandsons interest in the hobby, but it's done the exact opposite. I'm going to contact MTH and ask about a refund on my app upgrades. I'll try to return the interface unit to the hobby shop where I purchased it, but they are a mom and pop operation and may just tell me to use the warranty. It's really sad, because when it decides to work it's really nice.
Well? it works good for me. If you want to sell yours off, so be it. I think the usual suspects for the wifi not working are the devices dropping the connection, or poor signal which can be caused by a number of issues.
VanceG posted:This thread is well over a year old, and a lot of us are still having the issue of "tiu not found" with the MTH interface unit. I love MTH trains, but this has been extremely frustrating. One day it works, the next day it won't. My handheld remote is always reliable. For the money I put out for the Wifi unit and the money spent on upgrading the app to premium, I would expect better results. I've tried every remedy here yet I am experiencing the same issues many others are. I had hoped that running my trains through my iPad would have increased my 10 year old grandsons interest in the hobby, but it's done the exact opposite. I'm going to contact MTH and ask about a refund on my app upgrades. I'll try to return the interface unit to the hobby shop where I purchased it, but they are a mom and pop operation and may just tell me to use the warranty. It's really sad, because when it decides to work it's really nice.
You've only just joined the forum so I don't know much about you. If you stick with it there are plenty of people to help you here. I'm really getting to like the DCS app more and more over time.
I found that my old phone can cause me a lot of grief trying to run the app. It doesn't stay up to date and the software isn't current. Since I've added a couple of tablets, it makes it easier to figure out what is causing the issue. The tablets work when the phone doesn't, I know it's not the WIU or TIU causing the grief. I have had to reset the app on that phone, several times. I haven't had to yet, on my tablets that are more current in their software.
I also grab the remote first, and it's another good source for troubleshooting. Because I run a lot, when I get something new on the rails, it's easier to troubleshoot any changes.
A big thing to learn about DCS, is that the messages displayed are only hints about what's not working. They are generic messages and don't spell out why they are occurring. "No TIU found" for example, can mean many things. It doesn't (only) mean that there's no TIU connected.
I really hope that someday in the near future, the WIFI is built right into the TIU. Because you need a WIU for every TIU, it only makes sense to me. Otherwise you end up with a system like another manufacturer offers, that needs a separate piece for everything you do. I also wonder if the message "no TIU found" will still pop up! 
Engineer-Joe posted:Well? it works good for me. If you want to sell yours off, so be it. I think the usual suspects for the wifi not working are the devices dropping the connection, or poor signal which can be caused by a number of issues.
VanceG posted:This thread is well over a year old, and a lot of us are still having the issue of "tiu not found" with the MTH interface unit. I love MTH trains, but this has been extremely frustrating. One day it works, the next day it won't. My handheld remote is always reliable. For the money I put out for the Wifi unit and the money spent on upgrading the app to premium, I would expect better results. I've tried every remedy here yet I am experiencing the same issues many others are. I had hoped that running my trains through my iPad would have increased my 10 year old grandsons interest in the hobby, but it's done the exact opposite. I'm going to contact MTH and ask about a refund on my app upgrades. I'll try to return the interface unit to the hobby shop where I purchased it, but they are a mom and pop operation and may just tell me to use the warranty. It's really sad, because when it decides to work it's really nice.
You've only just joined the forum so I don't know much about you. If you stick with it there are plenty of people to help you here. I'm really getting to like the DCS app more and more over time.
I found that my old phone can cause me a lot of grief trying to run the app. It doesn't stay up to date and the software isn't current. Since I've added a couple of tablets, it makes it easier to figure out what is causing the issue. The tablets work when the phone doesn't, I know it's not the WIU or TIU causing the grief. I have had to reset the app on that phone, several times. I haven't had to yet, on my tablets that are more current in their software.
I also grab the remote first, and it's another good source for troubleshooting. Because I run a lot, when I get something new on the rails, it's easier to troubleshoot any changes.
A big thing to learn about DCS, is that the messages displayed are only hints about what's not working. They are generic messages and don't spell out why they are occurring. "No TIU found" for example, can mean many things. It doesn't (only) mean that there's no TIU connected.
I really hope that someday in the near future, the WIFI is built right into the TIU. Because you need a WIU for every TIU, it only makes sense to me. Otherwise you end up with a system like another manufacturer offers, that needs a separate piece for everything you do. I also wonder if the message "no TIU found" will still pop up!
Hi,
While I may be new to this forum, I'm far from new to model railroading and have dealt with the usual frustrations that can come along with tracks, switches, accessories, and trains themselves. 99 out of 100 times there is usually an easy an permanent solution to any issues I may have had, and I typically find my answers through a variety of groups I'm involved in.
So, while I'm experienced at model trains, the Wifi MTH unit is new to me, and as can happen I ran into some issues. I searched the internet and discovered this forum and thread. Before posting anything, I wanted to give an earnest attempt to fix my issue and I feel as if I've tried everything anyone has tried here to find a permanent solution to the issue.
MTH has obviously not found a fix for this issue, and I'm sure they have tried. Personally, I don't think they should be selling the units until they find a fix, but that's just my humble opinion.
I am somewhat confused by your reply, where you start out by saying it works well for you, but the last two or three paragraphs of your reply indicates to me you still have ongoing issues.
Either way, I only posted to voice my frustration in the hopes that it will help to continue to apply pressure to MTH so they keep trying to work on a fix. Right now the unit and app upgrades I bought are useless to me. It's money I could have spent on something else for my layout.
My reply was to say that my old phone was the main source of my issues. I may have rambled off topic a bit. The phone is not up to date on it's software. I tried to delete some stuff to make more storage room after I got a message saying it couldn't do an update because something was full?
I am not up to date myself on all this software stuff on current devices. Yet my DCS app works well for me on my tablets that are current. So my message to you was that I'm guessing it's either your device, or your layout's signal that just might be the problem. I'm just guessing here. You didn't give us anything to troubleshoot with.
I have not seen your name come up on other posts that went into detail on fixing these issues. I only see your conclusion here that you are giving up. It is good to show a company that there are issues. The problem here, may be that the issue is not this particular companies fault? When there's a layout with good signal and a device that's up to date, the usually app works. I think it's the exception, not the rule here, that it's not working for some. I still have a feeling it's the device that just maybe dropping the wifi for some reason.
There have been updates by MTH to fix some bugs that have popped up in older releases that did cause issues. It's not fair to dwell backwards on those, or to blame MTH when users have not updated these fixes. There are plenty of posts by users that are trying to run with old DCS releases that have been publicly stated won't run well with the latest app release.
So your public statement that you are giving up seems to point that's what others with issues should do? Just quit?
Do you know that when the phone or device is turned on (or left on) for example when the WIU is not powered, (some??) devices will revert to the house's router automatically? You may know that. I just haven't seen much info on where you were at when you decided to quit. You maybe far above my skill level on this stuff?
Vance,
MTH has obviously not found a fix for this issue, and I'm sure they have tried.
With all due respect, there is no "issue" as you've described. You're either:
- Doing something incorrectly (operator error)
- Have a software mismatch
- Have an anomaly in your layout wiring or track topology
- Have home WiFi issues or software issues with the device that you're using
- Are using a non-compatible router, possibly from a cable company
- Have defective DCS equipment.
While there certainly are a few bugs in the software, the process does, indeed, work properly.
 | Everything that you need to know about DCS WiFi is all in MTH’s “The DCS WiFi Companion 2nd Edition!" |
Barry,
Thanks for the reply.
Regarding the various possibilities you list that may be causing my troubles:
It was functioning perfectly for about a day. I spent the money for the app upgrades and it did not work after that point.
To me that indicates an "issue" with the app or hardware and nothing wrong on my end with my set up, tracks, etc. since I was able to set it up and use it.
I can't think of any other reason it stopped functioning.
Again, I loved using it when I bought it and then was a bit surprised I would have to pay additional fees to use all the functions. It was awesome while it lasted.
Not sure if this helps, but when I start up my layout everything gets powered on at the same time. Meaning the TIU and the WIU are both powered up at the same time. My WIU is on my home wireless network.
- I have a Note 9 and an iPhone and they both work with no issues.
- I usually don't touch the MTH WiFi app for about 2-3 minutes after the initial power on (This is the key step)
- I open the app, click run my trains, and hit the refresh button in the top left
- This process seems to work for me consistently
Have you done a reset on the WIU? Try it, worked for me. Also watch the WIU and wait till the blue Wi-Fi light is on steady, before you start the DCS App
BNSF-Matt posted:Not sure if this helps, but when I start up my layout everything gets powered on at the same time. Meaning the TIU and the WIU are both powered up at the same time. My WIU is on my home wireless network.
- I have a Note 9 and an iPhone and they both work with no issues.
- I usually don't touch the MTH WiFi app for about 2-3 minutes after the initial power on (This is the key step)
- I open the app, click run my trains, and hit the refresh button in the top left
- This process seems to work for me consistently
Me too
I have been using the DCS Wifi application on my layout for over a year and a half with no issues. More recently, I added Legacy successfully (following the instructions in Barry's book to the T).
In recent weeks, I have been running a lot of Post War locomotives, in conventional through the handles of my Post War ZW's (not through DCS). My android phone has had a couple of updates pushed to it in the meantime, so I thought, after reading this thread, I should check the DCS Wifi Ap to see if there were any issues.
I use the start up methodology cited by BNSF Matt, above, except that my DCS Wifi unit is not set to my home network.
I have a signal strength of "10" and very solid DCS operation at every point on my small, Super O layout.
I put my PS3 SP Cab Forward on the track and attempted to add it to the remote-it would not add. I tried this multiple times (at least 10 over a period of about a week) with the same result-the exception being that I would rarely, but occasionally, get the message that there was "no TIU." The locomotive would run in Command through the DCS Handheld with no problem. The locomotive still, by the way, had its factory default I.D. of "1."
I tried to add the Cab Forward again, three times this morning-no go.
I looked at the Ap in my phone, and noticed that I had a Legacy engine programmed in slot "1." The Legacy I.D. is something like 26 (the first two digits of the engine's number), but it is in slot 1 in the DCS Ap. I know from years with the DCS Handheld, that the DCS Slots are the engine numbers for PS2 and PS3 locomotives, but not for Legacy and TMCC engines. If I recall correctly, with the DCS Handheld, if a slot/number is used for a TMCC engine, when a DCS engine is added, it gets the next available number/slot, even though the slot/number of the Legacy/TMCC engine has not been assigned to a PS2/PS3 loco.
Thinking that the DCS Wifi Ap might behave differently, I changed the I.D. number of the Cab Forward from "1" to "6" in the DCS Handheld (slot 6 was not occupied in the DCS Wifi Ap by either a Legacy/TMCC locomotive or a PS2/PS3 locomotive).
When I went to add the Cab Forward to the DSC Wifi Ap, it added immediately as engine #6. This about 10 minutes after the last failed attempt, and from the same spot on the track where it sat all the other times I tried to add it unsuccessfully (I had not moved it from the last three failed attempts this morning). There have been no changes to the layout and no changes to the consist, etc.
I don't know if anyone has experienced exactly what I did, but because I got the "no TIU" message a few times, I thought it might be helpful.
RAK,
I don't know if anyone has experienced exactly what I did, but because I got the "no TIU" message a few times, I thought it might be helpful.
I strongly urge you to report this as a possible bug in the app via More.../App Settings/App Support
BNSF-Matt posted:Not sure if this helps, but when I start up my layout everything gets powered on at the same time. Meaning the TIU and the WIU are both powered up at the same time. My WIU is on my home wireless network.
- I have a Note 9 and an iPhone and they both work with no issues.
- I usually don't touch the MTH WiFi app for about 2-3 minutes after the initial power on (This is the key step)
- I open the app, click run my trains, and hit the refresh button in the top left
- This process seems to work for me consistently
Thanks - waiting to open the app until everything powers up seems to be working. I have two loops going through the DCS and was able to get them both working with the app, but now only one will work again. One loop always works when I wait to load the app, but the other won't now. Am I missing something there? Any advice is appreciated. Thanks!
When you say “two loops” are the two loops on separate TIU channels?
Are they both Fixed Voltage Channels?
Is the power applied to both simultaneously?
Is the TIU powered through the Auxiliary Port?”
My TIU is powered via the Auxiliary Power Port. When the main power switch is turned on to the layout, the TIU is powered up, as is the WIU. I have two loops, each powered by a different handle on a Post War ZW. Each loops goes through a different fixed voltage port on the TIU. DCS comes on both loops with no problem, but each must be powered up through its respective ZW handle in order to add, run, or identify PS2/PS3 locomotives on its loop.
RAK posted:When you say “two loops” are the two loops on separate TIU channels?
Are they both Fixed Voltage Channels?
Is the power applied to both simultaneously?
Is the TIU powered through the Auxiliary Port?”
My TIU is powered via the Auxiliary Power Port. When the main power switch is turned on to the layout, the TIU is powered up. I have two loops, each powered by a different handle on a Post War ZW. Each loops goes through a different fixed voltage port on the TIU. DCS comes on both loops with no problem, but each must be powered up through its respective ZW handle in order to add, run, or identify PS2/PS3 locomotives on its loop.
Ok, to answer your questions:
They are on separate fixed channels. through the same DCS (1 and 2)
I have tried them on separate power supplies (handles) on the same ZW transformer and on separate ZW's. I power up both handles before turning on the wifi and then loading the app.
The TIU is powered via the auxiliary input.
I've never been able to find any engines via the app on the 2nd loop, only the first. I was told in order for the DCS to find and engine initially, it has to be the only engine on the track. True or not?
As I said, both loops worked at one time via the app but now only one works. I run the 2nd loop via the hand held remote and it runs fine, I just prefer the additional options and ease of the app.
In addition, I had a TMCC base wired at one point and was able to discover and run a Lionel TMCC engine via the app, but that stopped working suddenly as well, so I disconnected it and no longer run TMCC (I don't have a Cab-1....yet....)
I didn't alter any wiring or tracks..the 2nd track and TMCC just stopped working.
Any thoughts or input is greatly appreciated.
"I've never been able to find any engines via the app on the 2nd loop, only the first. I was told in order for the DCS to find and engine initially, it has to be the only engine on the track. True or not?"
The first time you ADD an engine to DCS, it usually finds that engine much more easily if the engine is on the track by itself (people make separate programming tracks just for this purpose). Once you add the engine, you should be able to do a "Read" on the remote, or a "Refresh" on the Ap to find it, even with multiple PS2PS3 engines on the track (it should find all of them). This assumes that the engine had a good, charged battery/capacitor in it when it was originally added and so retained its new DCS identity (the number usually changes from the stock, factory "1" to the number of the next available slot in the remote).
"As I said, both loops worked at one time via the app but now only one works. I run the 2nd loop via the hand held remote and it runs fine, I just prefer the additional options and ease of the app."
I don't have enough knowledge to answer this one-perhaps Barry or one of the other Guru's will chime in. I wonder if the DCS signal is turned off on the second loop in the Ap, but is on in the Handheld.
Just out of curiosity, what happens if you roll the outputs of your DCS Fixed Channels so that the first loop is on Fixed 2 and the second loop is on Fixed 1? Do both still work with the Handheld? With the Ap, does the first loop stop working and the second one now work?
"In addition, I had a TMCC base wired at one point and was able to discover and run a Lionel TMCC engine via the app, but that stopped working suddenly as well, so I disconnected it and no longer run TMCC (I don't have a Cab-1....yet....)"
I don't, at present, even have a working Cab-1. I have had one for years, but rarely use it (almost always running TMCC through the DCS Handheld because, for me, it is easier than the Cab-1 and, more recently, through the Ap, which is easier still (for me)). There are some things, I understand, that are easier to do with the Cab-1, but I can't remember what they are.
You really shouldn't be able to "discover" a TMCC or Legacy engine via the DCS Ap. There is no two-way communication with TMCC/Legacy engines, so DCS, regardless of whether you are using the Ap or the Handheld, does not know there is a Legacy or TMCC engine on the track (unlike PS2 and PS3, where a Read/Refresh will tell you which engines are active). You have to either have left the Lionel engine on the active list, and not have done a Refresh, or use "Edit" to move it to the active list to run it in the Ap.
TMCC should not affect DCS operations (other than there are some TMCC electronics that can kill DCS signal strength-people used to put chokes in these TMCC locomotives to alleviate this). The connection is one wire to the outside rail of both loops. If you have a common ground on your layout, all you have to do is to run it there and TMCC will work. Your transformers have to be phased to do this.
The two ZW's on my layout are in phase and have common ground, so I only had to run the TMCC wire to one place to have TMCC on the entire layout.
"I didn't alter any wiring or tracks..the 2nd track and TMCC just stopped working."
It seems to me that there might be something interesting going on with that second loop. What happens if you move the TMCC locomotive to the Active List with the Edit command, can you run it then?
Have you consulted Barry's book regarding wiring and connecting both DCS and TMCC? It makes all of this very, very easy.
I'm going to try your suggestion about switching the tracks on the fixed outputs on the DCS. I'll give that a shot later tonight and hopefully they both work, or at the very least it helps me narrow down where the issue is. Thanks!
Well, I switched up the tracks with the same results. Anything on the 2nd loop is not recognized but will work with the hand held remote. It has to be something in the app. I may delete it, re-install it, reset it to it's original settings, and start over completely.
VanceG posted:Well, I switched up the tracks with the same results. Anything on the 2nd loop is not recognized but will work with the hand held remote. It has to be something in the app. I may delete it, re-install it, reset it to it's original settings, and start over completely.
can you report what the signal strength is on the 2nd loop to us?
"Well, I switched up the tracks with the same results. Anything on the 2nd loop is not recognized but will work with the hand held remote. It has to be something in the app. I may delete it, re-install it, reset it to it's original settings, and start over completely. "
Just to be clear, you swapped the wires only on the output side of the TIU, right?
I agree with ENGINEER-JOE's question-it would be interesting to know the signal strength of the second loop. It would be interesting to know what the signal strength is on both loops, and if it is different when you swap the output wires of the TIU.
Engineer-Joe posted:VanceG posted:Well, I switched up the tracks with the same results. Anything on the 2nd loop is not recognized but will work with the hand held remote. It has to be something in the app. I may delete it, re-install it, reset it to it's original settings, and start over completely.
can you report what the signal strength is on the 2nd loop to us?
Sure thing but I'm going to expose my newness here
How do I determine what the signal strength is? I can see a voltage amount on the app for the 1st loop, but as I said the app doesn't pick up the signal to the 2nd track so I'm not sure how to tell what the strength is.....
VANCEG,
"Sure thing but I'm going to expose my newness here How do I determine what the signal strength is? I can see a voltage amount on the app for the 1st loop, but as I said the app doesn't pick up the signal to the 2nd track so I'm not sure how to tell what the strength is....."
I think you stated that you DCS does work on the second track with the Handheld. If this is the case, use the "Track Signal" feature under the "More" soft key in the handheld.
RAK,
How do I determine what the signal strength is?
On the Engine Soft Keys Screen for the engine, scroll down to FUNCTIONS and tap on Track Signal.
| Everything that you need to know about DCS WiFi is all in MTH’s “The DCS WiFi Companion 2nd Edition!" |
Barry,
I was actually quoting VANCEG's question, then answering it.
My apologies for being confusing sir.
I edited my post to correct it.
Barry Broskowitz posted:RAK,
How do I determine what the signal strength is?
On the Engine Soft Keys Screen for the engine, scroll down to FUNCTIONS and tap on Track Signal.
Everything that you need to know about DCS WiFi is all in MTH’s “The DCS WiFi Companion 2nd Edition!"
This book is available from many fine OGR advertisers and forum sponsors, as an eBook or a printed book at MTH's web store!
Thanks for the instructions to determine signal strength. I followed the steps and for both tracks the signal strength is 10 on a scale of 1-10. I have 3 MTH engines and they all work on both tracks with the hand held remote. Any engine I put on track 2 will not work with the Wifi app. In fact, when I try to find it, and when I have both tracks powered up, I get the "can't find TIU" message. If I power down track 2 and refresh the app, it finds the TIU right away, but will only function with trains on track 1. I'm completely at a loss, especially since it did function with both tracks at one point.
“Any engine I put on track 2 will not work with the Wifi app. In fact, when I try to find it, and when I have both tracks powered up, I get the "can't find TIU" message. If I power down track 2 and refresh the app, it finds the TIU right away, but will only function with trains on track 1. I'm completely at a loss, especially since it did function with both tracks at one point.”
Vance, I have the exact same problem. I’ve tried all kinds of wiring combinations to no avail. The only advice I’ve received and tried was to crank up the power which did not work. I am going to fiddle with it some more later today and I’ll report back if I make progress.
bigtruckpete posted:“Any engine I put on track 2 will not work with the Wifi app. In fact, when I try to find it, and when I have both tracks powered up, I get the "can't find TIU" message. If I power down track 2 and refresh the app, it finds the TIU right away, but will only function with trains on track 1. I'm completely at a loss, especially since it did function with both tracks at one point.”
Vance, I have the exact same problem. I’ve tried all kinds of wiring combinations to no avail. The only advise I’ve received and tried was to crank up the power which did not work. I am going to fiddle with it some more later today and I’ll report back if I make progress.
Good luck. Let me know if you find a fix, but I don't think there is one. I think it's a flaw in the app. If everything works fine with the remote, it's nothing we are doing. I too have tried every possible combination of things that could possible be making a difference. The issue is in the app somewhere, and quite frankly I don't think we should be responsible for the fees we paid to upgrade. I'll change my opinion on that if anyone can provide a fix......
