The app works fine. The issue is not with your DCS. Most likely a layout wiring issue, DCS interference from TMCC/Legacy engines or defective equipment.
Regardless, it is not any kind of a DCS “bug”.
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 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.
What about swapping the outputs to track on Fixed 1 & 2. Does the condition follow the Fixed 2 output on the previous Fixed 1 track, or does the problem stay with the track powered previously by Fixed 2?
Barry Broskowitz posted:The app works fine. The issue is not with your DCS. Most likely a layout wiring issue, DCS interference from TMCC/Legacy engines or defective equipment.
Regardless, it is not any kind of a DCS “bug”.
Barry,
The app doesn't work fine. That's an easy remark for you to make without seeing what is going on first hand. I understand your stake in things with the book providing you some source of income, but please don't speak down to those of us (and there are many) who are having this issue. I find it interesting that when I reported back to you that my signal strength is fine, that you didn't reply, but as soon as I call out an issue with the app, you're quick to come to it's defense (within 30 minutes of my post). My wiring is fine, my signal strength is fine, the DCS is fine because it works with all engines on all tracks with the remote, all my equipment is fine, and there is no interference from Legacy equipment because I have none on the tracks. The only thing that does not work is track 2 with the app. It doesn't take a genius to single out that's the one and only issue. I'm a fairly handy and sharp guy, and usually can find a solution to something like this. Rather than cast blame on where you feel we aren't doing something right, why not try to help further? I've said my piece.
Vance I had a problem similar to what you described. Thought I had a channel 2 problem. Sent the TIU to MTH, they said it was fine and put in the new hardware while they had it. Same problem when it came back and I finally found the polarity of my 180W brick was reversed. Reversed polarity puts power to the track OK but messes up the signal.
H1000 posted: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 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.
What about swapping the outputs to track on Fixed 1 & 2. Does the condition follow the Fixed 2 output on the previous Fixed 1 track, or does the problem stay with the track powered previously by Fixed 2?
Hi,
I've switched outputs from 1 & 2. When I did that, everything ran great from the remote as it always does, but the same issue with track 2 occurs when I use the app, so that tells me it's not an issue with the DCS. I've tried different power sources, different engines, any variable I can think of and it still will not read track 2, and the remote ALWAYS finds engines on that track despite all the variables. I thought the app upgrade would have helped, but unfortunately it doesn't.
kgsouth posted:Vance I had a problem similar to what you described. Thought I had a channel 2 problem. Sent the TIU to MTH, they said it was fine and put in the new hardware while they had it. Same problem when it came back and I finally found the polarity of my 180W brick was reversed. Reversed polarity puts power to the track OK but messes up the signal.
KG,
Thanks. I have a separate brick on each output on my newer ZW and only use 135w bricks. Even if I put track 2 on a different ZW I have the same issue. If I have the tracks on separate ZW's, would the polarity on the brick I'm using for track 1 make a difference? If you think it would, what would you recommend as a fix?
There may be different ways to check phasing, but I take what I consider the common side of the transformer output connected together and then take the hot side wires and touch them together. If it doesn't short you are in phase. In the past there have been some problems with phasing from bricks where the ribbed wire and the smooth wire were wired backward. The ribbed wire should be common and the smooth wire hot.
What if you tried using the same powerhouse to provide power to both tracks, and eliminate a problem with using 2 powerhouses, or multiple transformers?
MrMoe50 posted:What if you tried using the same powerhouse to provide power to both tracks, and eliminate a problem with using 2 powerhouses, or multiple transformers?
I don't think that's an option. The powerhouses I use have specific plugs that fit into the ZW. I need one for each power source (handle). Is there a work-around for that?
kgsouth posted:There may be different ways to check phasing, but I take what I consider the common side of the transformer output connected together and then take the hot side wires and touch them together. If it doesn't short you are in phase. In the past there have been some problems with phasing from bricks where the ribbed wire and the smooth wire were wired backward. The ribbed wire should be common and the smooth wire hot.
Ok, I've checked for phasing and I'm all good there as well. I even tried powering the tracks from different transformers as well. I can' think of another variable. I just reset the entire thing and started from scratch as well. Same thing - the app finds anything on track 1 but nothing on track 2. I would slightly buy into the argument that it's something with wiring/power, but I've tried every variable imaginable and the results are the same. The remote works fine with everything, and it's just the app that won't find the 2nd track. I'm in a number of Facebook groups and I'm finding it's a very common problem and a lot of people are just giving up on it. MTH doesn't help either as their website doesn't offer any new support.
VanceG posted:Barry Broskowitz posted:The app works fine. The issue is not with your DCS. Most likely a layout wiring issue, DCS interference from TMCC/Legacy engines or defective equipment.
Regardless, it is not any kind of a DCS “bug”.
Barry,
The app doesn't work fine. That's an easy remark for you to make without seeing what is going on first hand. I understand your stake in things with the book providing you some source of income, but please don't speak down to those of us (and there are many) who are having this issue. I find it interesting that when I reported back to you that my signal strength is fine, that you didn't reply, but as soon as I call out an issue with the app, you're quick to come to it's defense (within 30 minutes of my post). My wiring is fine, my signal strength is fine, the DCS is fine because it works with all engines on all tracks with the remote, all my equipment is fine, and there is no interference from Legacy equipment because I have none on the tracks. The only thing that does not work is track 2 with the app. It doesn't take a genius to single out that's the one and only issue. I'm a fairly handy and sharp guy, and usually can find a solution to something like this. Rather than cast blame on where you feel we aren't doing something right, why not try to help further? I've said my piece.
Why would you even think that it has to be the app? Does the app know or care what track it is?
You seem like you'd rather defend your layout than try proper troubleshooting to get to the heart of the problem.
If we all leave, you are the one that still has the issue. Don't take it as casting blame, take it as where to look for possible issues. We are not there and have no idea what's wrong, other than any limited info that you provide.
VanceG posted:MrMoe50 posted:What if you tried using the same powerhouse to provide power to both tracks, and eliminate a problem with using 2 powerhouses, or multiple transformers?
I don't think that's an option. The powerhouses I use have specific plugs that fit into the ZW. I need one for each power source (handle). Is there a work-around for that?
Can’t you just power both TIU inputs for both tracks from the same ZW handle, thus being the same powerhouse?
Engineer-Joe posted:VanceG posted:Barry Broskowitz posted:The app works fine. The issue is not with your DCS. Most likely a layout wiring issue, DCS interference from TMCC/Legacy engines or defective equipment.
Regardless, it is not any kind of a DCS “bug”.
Barry,
The app doesn't work fine. That's an easy remark for you to make without seeing what is going on first hand. I understand your stake in things with the book providing you some source of income, but please don't speak down to those of us (and there are many) who are having this issue. I find it interesting that when I reported back to you that my signal strength is fine, that you didn't reply, but as soon as I call out an issue with the app, you're quick to come to it's defense (within 30 minutes of my post). My wiring is fine, my signal strength is fine, the DCS is fine because it works with all engines on all tracks with the remote, all my equipment is fine, and there is no interference from Legacy equipment because I have none on the tracks. The only thing that does not work is track 2 with the app. It doesn't take a genius to single out that's the one and only issue. I'm a fairly handy and sharp guy, and usually can find a solution to something like this. Rather than cast blame on where you feel we aren't doing something right, why not try to help further? I've said my piece.
Why would you even think that it has to be the app? Does the app know or care what track it is?
You seem like you'd rather defend your layout than try proper troubleshooting to get to the heart of the problem.
If we all leave, you are the one that still has the issue. Don't take it as casting blame, take it as where to look for possible issues. We are not there and have no idea what's wrong, other than any limited info that you provide.
You obviously haven't read through everything I've tried to remedy the situation before posting or you wouldn't make the comments you made. I've made exhaustive attempts at troubleshooting. Again - rather than throwing premature barbs at me, I'd appreciate any constructive feedback based on the things I've tried - and posted. I'm not trying to defend my layout by any means. I just want the app to work. If you told me to hang my layout from the ceiling I'd try it at this point. Read through what I've tried and let me know what possible variable there may be other than the one constant - which is the app. While you're at it, Google the issue and you'll find it's pretty common. I guess in your opinion none of us know what we're doing.
MrMoe50 posted:VanceG posted:MrMoe50 posted:What if you tried using the same powerhouse to provide power to both tracks, and eliminate a problem with using 2 powerhouses, or multiple transformers?
I don't think that's an option. The powerhouses I use have specific plugs that fit into the ZW. I need one for each power source (handle). Is there a work-around for that?
Can’t you just power both TIU inputs for both tracks from the same ZW handle, thus being the same powerhouse?
That's a good idea to see if I can isolate the issue. If that works, then I'll know it's something related to the power source. I'll give it a whirl now. Thanks for the suggestion.
You do have another variable here besides just the app....the WIU. Not sure how it would have any effect on your issue though, but it is a piece of the puzzle when using the app.
Have you tried switching the USB cable that coonects the WIU to the TIU?
Just tossing stuff out.
VanceG posted:Engineer-Joe posted:VanceG posted:Barry Broskowitz posted:The app works fine. The issue is not with your DCS. Most likely a layout wiring issue, DCS interference from TMCC/Legacy engines or defective equipment.
Regardless, it is not any kind of a DCS “bug”.
Barry,
The app doesn't work fine. Tha…..
Why would you even think that it has to be the app? Does the app know or care what track it is?
You seem like you'd rather defend your layout than try proper troubleshooting to get to the heart of the problem.
If we all leave, you are the one that still has the issue. Don't take it as casting blame, take it as where to look for possible issues. We are not there and have no idea what's wrong, other than any limited info that you provide.
You obviously haven't read through everything
Yes, unfortunately, I have wasted my time reading thru this and following it closely. But don't let that fool you. I read thru every post about DCS, not just yours.
You seem very defensive and would rather challenge than listen. So I'm out. You'll probably find patient people who will help you here. Good luck. Maybe lessen up on the jabs in the future for others trying to help. We are not punching at you. You seem to think we are.
That is the best language I can use here without getting reprimanded for bad taste against your post.
Wow...Talk about casting stones! 
Engineer-Joe posted:VanceG posted:Engineer-Joe posted:VanceG posted:Barry Broskowitz posted:The app works fine. The issue is not with your DCS. Most likely a layout wiring issue, DCS interference from TMCC/Legacy engines or defective equipment.
Regardless, it is not any kind of a DCS “bug”.
Barry,
The app doesn't work fine. Tha…..
Why would you even think that it has to be the app? Does the app know or care what track it is?
You seem like you'd rather defend your layout than try proper troubleshooting to get to the heart of the problem.
If we all leave, you are the one that still has the issue. Don't take it as casting blame, take it as where to look for possible issues. We are not there and have no idea what's wrong, other than any limited info that you provide.
You obviously haven't read through everything
Yes, unfortunately, I have wasted my time reading thru this and following it closely. But don't let that fool you. I read thru every post about DCS, not just yours.
You seem very defensive and would rather challenge than listen. So I'm out. You'll probably find patient people who will help you here. Good luck. Maybe lessen up on the jabs in the future for others trying to help. We are not punching at you. You seem to think we are.
That is the best language I can use here without getting reprimanded for bad taste against your post.
I would agree you've wasted your time going through this thread because by your own admission you know nothing about the newer stuff. I'm not defensive in any way, other than to make a point when I'm being criticized by someone with no knowledge on the subject. I'm more than eager and willing to listen to advice, but you haven't offered anything. When you have something to offer, I'll be glad to listen.
Just this week, feb, 2019- my wiu would not find my tiu until I added a wall wart ( about a 12 volt) to provide additional power to the tiu with its barrel connector. The tiu already had the red light on, since I was powering the tiu fixed 2 terminal in from the variable handle 2 out from on my z4000 transformer, setting it at 19 volts. Previously, I had run trains using the old remote from 2002 but when I bought the wifi unit & downloaded the $25 premium dcs app, the wiu would not find the tiu until I added the wall wart for additional power
Just like most everyone else I invested in this wifi nightmare and spent hundreds of dollars only to sit here with the same frustrated messages no TIU Found. I have basically just given up on the MTH WIFI system. It's really frustrating that people put that kind of money into a product and basically stuck with it. I think they call that the cost of conformance?
Hopefully someday they will come up with a real fix that works
I guess I am among the lucky ones. My Wi-Fi found the TIU right out of the box and has work great for years. The app works exactly as advertised with zero problems.
well here I am almost three years later. Wasted another day trying to get wifi to work and same old same old. Reluctant to throw more money at this as buying another wiu is the only option I can think of. Can’t believe in three years there’s been no software updates to address the problems many people have. Seems like no one has even pin pointed what the issue is.
