Skip to main content

I know that the TIU finds engines not the WiFi unit, however I have a strange situation where the handheld can find and run an engine but when I try and add the engine with iPad and WiFi unit it fails to add the engine and returns a TIU not found error

If I reboot all is well with TMCC and some MTH engines but not all ? two of the engines that fail are a PS2 northern and a K4 PS2

Is it at all possible that the engine battery is marginal ? maybe but why would it work with handheld but not WiFi?

 

Original Post

Replies sorted oldest to newest

This should, probably, be in the DCS forum.  Having said that, from your description, the problem is that the Wi-Fi is not finding the TIU.  It is very likely that there is nothing wrong with the locomotive(s).

Check the connection between the TIU and the Wi-Fi.

Is your TIU powered through Fixed Channel 1 or an external power supply?  The fixed channel can be problematic since any disruption of power will disconnect it from the Wi-Fi.

Thanks for all your advice, I will post when I have sorted the problem

No I wont sell anything I have a big investment in MTH premier engines, however going forward my UK club and I are more attracted I must say to Lionel Legacy 

To be fair to MTH the DCS system does work with the handhelds for the most part, it does however suffer from its sophistication with its two way digital signal which is not forgiving when it comes to track condition, this is a user issue I know but it can be annoying with large layouts and getting to the track as cleaning systems do need some extra manual cleaning help occasionally. Lionel being a one way radio signal is definitely more robust but some will argue not as feature rich, but for me it is very satisfactory, and incidentally MTH WIFI works great with TMCC engines! particularly on the iPad with the grandchildren

Room for both systems in our UK club world 

Once again many thanks, I will improve maintenance and soldier on as 90% of it works.

 

 The app should find an engine faster than the remote does when everything is working correctly. The problem is again, the app doesn't tell you exactly what's wrong. You'll get a generic type message like "no TIU found" or something like that. It can be from poor signal, WIFI problems, etc.

 I have found that typical PS2 problems stem usually from poor signal or battery issues. At first, it was from the device running the app dropping the MTH WIU for various reasons.

 Lately it's from trying to run my different layouts, with just one WIU. I believe that the app gets messed up when I continuously switch to different TIUs controlling different layouts. If I stick with the main O scale 2 rail TIU #1, it's very dependable. If not, I have to reset the app in the device to clear conflicts. If I power down the main TIU, then the devices go back to the house's router by default, and I also have to reset the WIFI settings to MTH when powering back up.

Thanks guys

I agree part of the problem is with the app error routine, it doesn't actually tell you what it doesn't like, " No TIU found" is a useless message, because in actual fact it can be found because it runs the other engines !

As I said I am happy, I just posted in case there was something glaringly obviously amiss with my setup.

Having been in the IT business for a long time working with Networks it is true to say that adding an iPad to WIFI and a WIFI to TIU does add to the potential for handshaking problems which I think is what is going on ,the fact would appear to be that the error routine in the WIFI doesn't have the ability to recover from the error it gets presumably from the TIU,  it needs for me to switch it off and on again to clear the problem.

Just to be clear the MTH WIFI is for the most part is a cool option, and the iPad app is great to use, far easier to swap engine than with the handheld remote, also at my age easier to see with the large screen!  Ok so maybe the odd bug, but never the less for the price a value item.

As I said in my last post running most of it with WIFI and the odd engine by remote is not a big deal, so back to having fun with my O gauge buddies!

Cheers

Eric,

I agree part of the problem is with the app error routine, it doesn't actually tell you what it doesn't like, " No TIU found" is a useless message, because in actual fact it can be found because it runs the other engines !

No, that's not the problem at all. The problem is that the WIU simply cannot see a TIU, period. It's up to you, not the app, to find the cause.

Typically, this is due to one of the following:

  • The cable connecting the TIU and the WIU is defective or otherwise inappropriate.
  • The WIU and the service hosting the DCS App aren't properly connected via WiFi.
  • Mismatched software levels in the app, the TIU and the WIU.

Further, you haven't provided any information regarding your layout, including:

  • If the WIU is in Home or MTH Mode.
  • The model of the TIU and if you're connecting via its USB or serial port.
  • The type of the device hosting the DCS App and it's level of operating system
  • How you're connecting the device and the WIU via WiFi.
  • The software version of DCS in the TIU (it must be 6.1)
  • The firmware level of the WIU (it must be 1.1).
Last edited by Barry Broskowitz

Barry

I know you are trying to help but your message is a little patronizing, all is as it should be with the versions, cables etc.. I am an engineer I don't need a lecture on cables and software versions,  I just wondered if anybody had a similar issue, clearly two have observed this issue. I don't know how if your suggestion is correct how come I have 10 engines running with no problem!

Please read the thread, all I asked is why a couple of PS2 engines are found  with the handheld and not the WIFI, I thought it might be battery or weak signals which it probably is looking at the reply from SUPERWARP1

As I said I am not bothered , as we speak I have 10 engines running no problem under WiFi, just two old PS2 with a problem of not being found, they run with the handheld, so I am not worried

Lets close this thread !!!

Eric,

I am an engineer

An engineer you may be, however, a mind reader I am not.

your message is a little patronizing, all is as it should be with the versions, cables etc.

Yet something doesn't work and you don't know what's wrong.

I don't need a lecture on cables and software versions

What you need is to provide information so that a possible solution may be offered. How is anyone supposed to offer advice when you provide no information regarding your layout's configuration?

Regardless, life's too short for me to deal with fragile egos. Hopefully, someone more knowledgeable than I will come along with a less cloudy crystal ball and help you to sort out your problem.

I wish you the best of luck in resolving all of your issues.

Last edited by Barry Broskowitz

Eric,

 As A computer tech, you more than anyone should know answers are not possible without info. Sorry to read you felt tilted by an answer that I personal found very useful containing the limited information. He as well as everyone only ones to help not put any down. Sorry you took it that way.

I know, being a computer tech myself, that I personally sometimes have thought I did wiring one way to find a lot later that I was mistaken. The older I get the more it happens.

Enjoy the help and take life easy. If it isn't helpful, pass on it and keep going down the tracks. DON"T GET DERAILED!

Curtis

 

Eric,

you don't need a crystal ball just read it

Reading the post isn't the issue. Resolving your issue is what requires information.

If you want to "'surrender", that's fine.  Just realize that the real problem is your reluctance to provide any information to help others help you in the problems resolution.

To paraphrase an old homily, "...the OGR Forum helps those who help themselves."

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.
×
×